On this page : https://onap.readthedocs.io/en/latest/submodules/optf/has.git/docs/sections/homingspecification.html

 

I have detected about 15 problems

 

point 1 : there is that sentence :  Support for this schema is deferred.

please remove or update to Dublin

 

point 2 :there is a question :What geocoder can we use to convert placemarks to a latitude/longitude?

please, provide the answer and remove the question from the documentation.

 

point 3: there is a question : Currently, candidates are either service instances or cloud regions. As new services are on-boarded, this can be evolved to represent different types of resources.

please : answer

 

point 4 : there is question :  Do we need to support cost as a function ?

please answer or remove or update for Dublin

 

point 5 : there is that text :

Note: Constraint names marked “Deferred” *will not be supported in the initial release of HAS.*

please update for Dublin

 

point 6 : there is that text : For ONAP Beijing release the REQUEST_DICT is of the following format as defined by the policy for vim_fit. The REQUEST_DICT is an opaque request object defined through policy, so it is not restricted to this format. In ONAP Beijing release MultiCloud supports the check_vim_capacity using the following grammar.

please update for Dublin

 

point 7: there is that text :

Note: Only pair-wise groups are supported at this time. If three or more demands are specified, only the first two will be used.

please update for Dublin

 

point 8 : there is that text : License

Constrain demands according to license availability.

Support for this constraint is deferred.

please update for Dublin

 

point 9 : there is that text : Network Between Demands

Constrain each pairwise combination of two or more demands by network requirements.

Support for this constraint is deferred.

Please update for Dublin

 

point 10 : there is that text : Network To Location

Constrain one or more demands by network requirements relative to a specific location.

Support for this constraint is deferred.

Please update for Dublin

 

point 11 : there is that text : Capabilities

Constrain each demand by its cluster capability requirements. For example, as described by an OpenStack Heat template and operational environment.

Support for this constraint is deferred.

Please update for Dublin

 

point 12 : there is that text :

Template Restriction

While the template format supports any number of arrangements of numbers, operators, and functions, HAS’s solver presently expects a very specific arrangement.

Until further notice:

please update for Dublin : is it still applicable ?

 

point 13 : there is that text :

Notes

• In the first version, we do not support more than one dimension in the optimization (e.g., Minimize distance and cost). For supporting multiple dimensions we would need a function the normalize the unit across dimensions.

please update for Dublin : : what means "in the first version" : is it still relevant ?

 

point 14 : there is that text :

• If Homing will only be accessed over DMaaP, files will need to be embedded using the Homing API request format.

please update for Dublin : answer

 

point 15 : rst formating problem : after text Candidate Schema, there is a block of bad formatted text.