Versions Compared

Old Version 32

changes.mady.by.user ruoyu.ying

Saved on

compared with

New Version 33

changes.mady.by.user ruoyu.ying

Saved on

Key

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

...

OOF will match the SRIOV information along with the constraint provided by Policy and add extra attributes inside the assignmentInfo data block when returning the response to SO and VF-C.

Sample looks like below.

"assignmentInfo": [ 
    { "key":"locationId",
      "value":"DLLSTX1A" },
    { "key":"locationType",
      "value":"openstack-cloud" },
    { "key":"vimId",
      "value":"rackspace_DLLSTX1A" },
    { "key":"oofDirectives",
      "value":{
        "directives":[
          { "vnfc_directives":[
               {
                  "vnfc_id":"
<ID of 
<ID of VNFC>",
                  "directives":[
                     {
                        "directive_name":"
<Name of 
<Name of directive,example flavor_directive>",
                        "attributes":[
                           {
                              "attribute_name":"
<name of 
<name of attribute, such as flavor label>",
                              "attribute_value":"
<value such as cloud specific 
<value such as cloud specific flavor>"
                           }
                        ]
                     },
                     {
                        "directive_name":"
<Name of 
<Name of directive,example vnic-info>",
                        "attributes":[
                           {
                              "attribute_name":"
<name of 
<name of attribute, such as vnic-type>",
                              "attribute_value":"
<value such as 
<value such as direct/normal>"
                           },
                           {
                              "attribute_name":"
<name of 
<name of attribute, such as provider netweork>",
                              "attribute_value":"
<value such as 
<value such as physnet>"
                           }
                        ]
                     }
                  ]
               }
            ]
         },
         {
            "vnf_directives":{
               "directives":[
                  {
                     "directive_name":"
<Name of 
<Name of directive>",
                     "attributes":[
                        {
                           "attribute_name":"
<name of 
<name of attribute>",
                           "attribute_value":"
<value>
<value>"
                        }
                     ]
                  },
                  {
                     "directive_name":"
<Name of 
<Name of directive>",
                     "attributes":[
                        {
                           "attribute_name":"
<name of 
<name of attribute>",
                           "attribute_value":"
<value >
<value >"
                        },
                        {
                           "attribute_name":"
<name of 
<name of attribute>",
                           "attribute_value":"
<value >
<value >"
                        }
                     ]
                  }
               ]
            }
         }
      ]
   }
}
]    


For the newly added oofDirectives, we only return the vnfc part. For example: 

"vnfc_directives": [
   {   "vnfc_id":"",
       "directives":[
           {  "directive_name": "flavor_directive",
              "attributes": [
                    {"attribute_name": "flavor_label_1", "attribute_value":"HPA.flavor"}
                           ]
           },
          {   "directive_name": "vnic-info",
                "attributes": [
                    {"attribute_name": "vnic-type", "attribute_value":"direct"},
                    {"attribute_name": "provider_network", "attribute_value":"physnet2"}
                ]
          }
               ]
}       
    }       
]
It is worth noting that the vnic-type is converted from interfaceType in OOF.

...