Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TOPICDISCUSSION
DEVELOPMENT OF LOCATION MODEL for PLACE OBJECT in ONPA PLATFORM INFORMATION MODEL

Development of Location Model for Place object in ONAP Platform Information Model. Place has been introduced as Experimental

Wiki page for root: Root (Root Model object)

ACTION: Information Model &PLACE Object proposal Start with "as built" model / Bob PapaSALVATORE RICCI 

ACTION: R7 need & application? VNF will likely need the address/location info/complex before PNF. (1) Containerization (2) multi-cloud 3rd party clouds & (3) attributes missing or extended A&AI schema update (4) support globalization. / VNF verizon ETSI alignment R7 Use Case "Onboard ETSI SOL004  compliant VNF packages"

ACTION: Generic Information Template page for Generic Information Element Definition for Geolocation Model: Generic Information Element Definition for Geolocation Model

PROPOSED LOCATION MODEL:

Proposed Location Model

INTEGRATION OF COMPLEX OBJECT & PLACE OBJECT

How do we associate in the model and execute in A&AI code - the inter-dependencies between the Place object and complex

Refactoring code, A&AI data model, may need to refactor code.

These part of place object implemented as part of the complex object.

The complex object is in the addendum at the bottom of this Wiki

ACTION: How would this tie into the complex object or link/associate with the complex object.

CONTACT: Jimmy Forsyth

ACTION: (OPEN) (Oct 3) - Jimmy (A&AI PTL) said that Complex Object is entwined in the code; hard to redact it; smarter to evolve. Tie place object into the complex object; maybe complex could be subobject of place. Jimmy also mentioned that the Place & complex could be linked together. Maybe complex would be a subobject to place if there is overlap in fields & concepts.  output of Graphgraph need UML model

ACTION: Complex object reverse engineering - Mapping of Place & A&AI Complex Object / Do an analysis on the Complex object / Reverse engineer of Complex / logical model vs grounding in current implementation → evolution / who will consume changes & use cases - downstream system / Standards → Needs Use Cases → Information Model → Objects & Data Model  / Subject Modeling S/C. Globalization of location information / simple things we can do wo/ breaking the complex object e.g. changing behavior applied to multiple countries are we missing attributes evolving location info for other U/C needs.

NEXT STEPS (R8)
  1. Go A&AI and socialize the Place Model Proposed Location Model
  2. Need to make Schema Update in A&AI for R8 Create a Release Requirement. ACTION: go to A&AI to socialize
  3. Model Requirement for Schema Definition.
  4. Transition of complex to Place Object, who is consumer? SO creates the A&AI instance and "links" A&AI to Complex (Seshu). AssignpnfBB. ACTION: ask about AssignpnfBB.
  5. Who knows how to populate it?
  6. Who uses it? VID-GUI

MAJOR TOPIC #1b - GEOLOCATION BASE INFO (Standards) / (Closed)

...

RECORDING

ADDENDUM