RE: [tosca] Groups - VNF_DF_instantiationLevels_policy_type.docx uploaded

Chris,

 

Thank you for the response.  Our proposal is in line with the tosca.capabilities.Endpoint, which has string property e.g. network_name which targets node template on Endpoint capability.

Please share your views.

 

Regards,

Priya

 

From: Chris Lauwers [mailto:]

Sent: Monday, April 30, 2018 5:10 AM

To: Priya T G; 

Cc: Nguyenphu, Thinh (Nokia - US/Irving)

Subject: RE: [tosca] Groups - VNF_DF_instantiationLevels_policy_type.docx uploaded

 

[External Email] 

 

Hi Priya,

 

It sounds like you’re trying to create “relationships” between entities without using TOSCA relationships, but instead by somehow expecting an orchestrator to interpret some properties (of type string) as “entity names” that point to some
 other entity in a topology. This sounds again like we’re trying to associate semantics with properties.  I believe that all semantics in TOSCA should be expressed by the language, not by property values.

 

Chris

 

 

From: Priya T G <> 

Sent: Monday, April 23, 2018 6:41 AM

To: Chris Lauwers <>; 

Cc: Nguyenphu, Thinh (Nokia - US/Irving) <>

Subject: RE: [tosca] Groups - VNF_DF_instantiationLevels_policy_type.docx uploaded

 

Chris,

 

My apologies for multiple emails – just to clarify, this proposal is not restricted to properties of node type, it can be extended to properties of TOSCA normative types.

 

Regards,

Priya

 

From: Priya T G

Sent: Sunday, April 22, 2018 7:36 PM

To: 'Chris Lauwers'; 

Cc: 'Nguyenphu, Thinh (Nokia - US/Irving)'

Subject: RE: [tosca] Groups - VNF_DF_instantiationLevels_policy_type.docx uploaded

 

Chris,

 

Thank you for the follow up.

The proposal is to enhance the TOSCA grammar to allow referring  a node template through string property.

 

#1:

node_types:

  node_type_a:

     properties:

       target_node:

          type: string

             constraints:

                - target: [ NODE_TEMPLATE, NODE_INSTANCE, GROUP, POLICY]

 

#2: 

 node_type_b:

   properties:

      some_map:

         type: map

         entry_schema: 

           type: string

           constraints:

             - target: [ NODE_TEMPLATE ]

 

#1 allows a string property to point to a node_template, node_instance, group or policy through target constraints.

#2 allows an entry of complex data structure to point to node_template

 

Example:

 

node_template:

  node_a:

    type: node_type_a

 

node_b:

   type: node_type_b

    properties: 

      target_node: node_a

 

With this enhancement , the string property of vduLevel structure (see slide 10 of attached slide deck which describes VNF Instantiation Level as a policy) can  point to a node template.

Hope this clarifies.

Please let me know your views.

 

Regards,

Priya

 

 

From: Chris Lauwers [mailto:]

Sent: Thursday, April 19, 2018 10:15 AM

To: Priya T G; Nguyenphu, Thinh (Nokia - US/Irving)

Cc: 

Subject: RE: [tosca] Groups - VNF_DF_instantiationLevels_policy_type.docx uploaded

 

[External Email] 

 

I don’t understand the concept of a “target” constraint on a string property. What is the target of a string?

 

Thanks,

 

Chris

 

From: Priya T G <>

Sent: Monday, April 02, 2018 11:38 PM

To: Chris Lauwers <>; Nguyenphu, Thinh (Nokia - US/Irving) <>

Cc: 

Subject: RE: [tosca] Groups - VNF_DF_instantiationLevels_policy_type.docx uploaded

 

Chris, Thinh,

 

The issue we face with respect to Instantiation Level is referencing a node template through a string property.

By declaring the target constraint for the node type, we intend to restrict the node type to be a NODE_TEMPLATE.  

With this,  it should be possible to reference this node template through a string property in vdulevels structure.

Of course, this needs enhancements to Simple Profile grammar, but with this approach, we retain the structure as proposed in the ETSI Information Model.

 

Regards,

Priya

 

node_types:

  some_type:

     properties:

       
target_node:

         type: string

            constraints:

              - target: [ NODE_TEMPLATE, NODE_INSTANCE, POLICY, GROUP]

 

Then, describe Instantiation Level as a policy –

 

- InstantiationLevel1:

    type: tosca.policies.nfv.instantiationlevel        

     properties:          

       description: 

       isDefault: true          

       vduLevels:            

         vdu_1:

           numberOfInstances: 1

         vdu_2:

           numberOfInstances: 1

         
vdu_3:              

           numberOfInstances: 1

          

      scaleInfo:                   

         vdu_1_scaleAspect:

            scaleLevel: 1

          vdu_2_scaleAspect:

            scaleLevel: 0

          vdu_3_scaleAspect:

            scaleLevel: 0

 

 

 

From: Chris Lauwers [mailto:]

Sent: Monday, April 02, 2018 11:44 PM

To: Priya T G; Nguyenphu, Thinh (Nokia - US/Irving); 

Subject: RE: [tosca] Groups - VNF_DF_instantiationLevels_policy_type.docx uploaded

 

[External Email] 

 

Hi Priya,

 

I’m not sure what you mean by a “target” constraint? Could you explain this concept?

 

Thanks,

 

Chris

 

From: Priya T G <>

Sent: Monday, April 02, 2018 8:57 AM

To: Chris Lauwers <>; Nguyenphu, Thinh (Nokia - US/Irving) <>;


Subject: RE: [tosca] Groups - VNF_DF_instantiationLevels_policy_type.docx uploaded

 

Chris, All,

 

To simplify the Instantiation Level issue, can we have an enhancement in the definition of node type grammar as below?

 

node_types:

  some_type:

     properties:

       
target_node:

         type: string

            constraints:

              - target: [ NODE_TEMPLATE, NODE_INSTANCE, POLICY, GROUP]

 

Then, describe Instantiation Level as a policy –

 

- InstantiationLevel1:

    type: tosca.policies.nfv.instantiationlevel        

     properties:          

       description: 

       isDefault: true          

       vduLevels:            

         vdu_1:

           numberOfInstances: 1

         vdu_2:

           numberOfInstances: 1

         
vdu_3:              

           numberOfInstances: 1

          

      scaleInfo:                   

         vdu_1_scaleAspect:

            scaleLevel: 1

          vdu_2_scaleAspect:

            scaleLevel: 0

          vdu_3_scaleAspect:

            scaleLevel: 0

 

Since vdu_1, vdu_2 etc. are node templates declared through the constraints of target_node property, it should be OK if they are described under vduLevels as above, complying with ETSI IFA 11 IM?

What are your thoughts?

Please comment.

 

Regards,

Priya 

 

From:
 [mailto:]
On Behalf Of Chris Lauwers

Sent: Friday, March 30, 2018 8:54 AM

To: Thinh Nguyenphu; 

Subject: RE: [tosca] Groups - VNF_DF_instantiationLevels_policy_type.docx uploaded

 

[External Email] 

 

Hi Thinh,

 

Thanks for posting this. I have the same question I posed on Tuesday during the YAML meeting: your proposal defines a number of data structures, but I don’t see where the semantics are defined that are associated with these data structures.
 Policies in TOSCA currently are imperative policies (meaning they use the Event/Condition/Action pattern). If a TOSCA orchestrator is supposed to be able to process your policies, then I would expect to see TOSCA triggers defined that specify the necessary
 events, conditions, and actions. Are you planning on providing those as well?

 

Thanks,

 

Chris

 

From:  <>
On Behalf Of Thinh Nguyenphu

Sent: Thursday, March 29, 2018 5:01 PM

To: 

Subject: [tosca] Groups - VNF_DF_instantiationLevels_policy_type.docx uploaded

 

Document Name:
VNF_DF_instantiationLevels_policy_type.docx

No description provided.

Download Latest Revision

Public Download Link

Submitter: Thinh Nguyenphu

Group: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC

Folder: Working Documents

Date submitted: 2018-03-29 17:00:38

 

 

The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged
 material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender
 and delete the material from any computer.   

 

The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged
 material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender
 and delete the material from any computer.   

 

The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged
 material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender
 and delete the material from any computer.   

 

The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in
 reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.