...
SO will get pciVendorId, pciDeviceId and interfaceType from CSAR file, then call to OOF. OOF will response homing information to SO, SO don't interpret it and pass through it to Multi-cloud.
HOT template that uses parameter to be filled up based on OOF output
parameters:
oof_returned_vnic_type_for_firewall:
type:string
description:This parameter value is determined by OOF. If OOF selects the region and flavor that support SRIOV-NICs, then OOF returns 'direct'. If not, it returns 'normal'
resources:
network_protected:
type: OS::Neutron::Net
properties:
name: mynetwork_protected
network_type: vlan
physical_network: physnet1
segmentation_id: 100
network_unprotected:
properties:
name: mynetwork_unprotected
network_type: vlan
physical_network: physnet2
segmentation_id: 200
/** Subnet details are not provided for brevity**/
protected_interface:
type: OS::Neutron::Port
properties:
name: protected_port
network_id : { get_resource: network_protected }
binding:vnic_type: {get_param: oof_returned_vnic_type_for_firewall}
unprotected_interface:
type: OS::Neutron::Port
properties:
name: unprotected_port
network_id : { get_resource: network_unprotected }
binding:vnic_type: {get_param: oof_returned_vnic_type_for_firewall}
virtual_firewall_appliance:
type: OS::Nova::Server
image: ....
networks:
- port: {get_resource: protected_interface}
- port: {get_resource: unprotected_interface}
|
1.4 VF-C call OOF
VF-C will get pciVendorId, pciDeviceId and interfaceType from CSAR file, then call to OOF. OOF will response homing information to VF-C.
VF-C get OOF response, It will create network of SRIOV-NIC using physical network.
Then, It will create port based on network using interface type.
1.5 OOF Response
OOF just check /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}/hpa-capabilities
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.
...