Versions Compared

Old Version 3

changes.mady.by.user Jessie S Jewitt

Saved on

compared with

New Version 4

changes.mady.by.user Jessie S Jewitt

Saved on

Key

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

...

Stereotypes, like classes, may contain a set of attributes, or properties. Here is an example of how the IISOMI "OpenModelAttribute" stereotype is defined in Papyrus. Note the icon with a little "s" to indicate that OpenModelAttribute is a stereotype. 

...

This attribute implies that the UML artifact has been deprecated in the model. In the wiki it would not be correct to say "support=DEPRECATED", as DEPRECATED is not one of the values that the support qualifier can have. The correct way to define this in the "Applied Stereotypes" column on the wiki would be:

OpenModelAttribute.support = MANDATORY

Deprecated

 

Applying Stereotypes

ONAP Stereotypes

...

One and only one lifecycle state has to be associated to every UML artifact. It is recommended that every new UML artifact is initially annotated with the “Experimental” lifecycle stereotype.

Wiki constraints:

  • The IISOMI lifecycle state is not currently being used in the wiki, or is not being used as intended. For example, saying "support=DEPRECATED" would not be correct, because DEPRECATED is not one of the values the "support" takes. The correct usage in the "Applied Stereotypes" column would be to add the stereotype "Deprecated" as one of the stereotypes being applied. The correct way to define this in the "Applied Stereotypes" column on the wiki would be:

    OpenModelAttribute.support = MANDATORY

    Deprecated

  • Note also the meanings provided above for "Deprecated" and "Obsolete". In both cases it is noted that the entity should be kept in the model for at least one further release. If one wants to actually deprecate an attribute it should go to the "Deprecated" state, then the "Obsolete" state, and THEN eventually be deleted from the model, per the state diagram below.

The associated state machine is as follows:

...

Homing selects what cloud selection strategy will be used.  HomingGroup is used to determine where VNF's within a given group are placed with respect to a service component.  Homing strategy is as follows: Colocation - members of the group share the same cloud region (VIM Domain) isolation - members of the group do not share the same cloud region. 


Applied stereotypes:

  • OnapModelLifecycle
    •  state: INPUT
  • OpenModelClass
    • support: MANDATORY
  • Experimental

 

...



Attribute Name

Type

Mult.

Stereotypes

Description

homingStrategy

HomingStrategy

1

OpenModelAttribute

  •  isInvariant: false
  • valueRange: no range constraint
  • support:  MANDATORY

OnapModelLifecycle

  • state:  INPUT

The homing strategy can be one of the following:  Exclusivity - Resources within the cloud region are exclusive to the group  Inclusively - Resources are co-located in the same cloud-region. Diversity - Resources are geo-diverse ( cannot be co-located).

 

 





.