VNF-Info with ephemeral Openstack networks

[akaliwod@cisco.com]

Hey, I would like to create test deployment in NSO where some networks are ephemeral.

When VNF-Info contains vnfd-connection-point references, like in the example below, then NSO expects that all network-id are pre-existing in Openstack. I would like to create MyCSR-1-ext and myCSR-2-ext networks in Openstack. How I can define this in VNF-Info?

Thanks!

Kali

                                <vnfd-connection-point>

                                        <id>management-ext</id>

                                        <network-name>os-management-net-0</network-name>

                                </vnfd-connection-point>

                                <vnfd-connection-point>

                                        <id>MyCSR-1-ext</id>

                                        <network-name>orch-inside-net-0</network-name>

                                </vnfd-connection-point>

                                <vnfd-connection-point>

                                        <id>MyCSR-2-ext</id>

                                        <network-name>orch-outside-net-0</network-name>

                                </vnfd-connection-point>

[frjansso · Accepted solution]

Yes, checkout additional-network in VNF info. Specify the network parameters there, and refer to the name in the vnfd-connection point:

...

    vnfd-connection-point left {

        network-name volvo-MyDeployment-inside-net;

    }

...

additional-network volvo-MyDeployment-inside-net {

    subnet {

        network 192.168.1.0/30;

    }

}

...

[akaliwod@cisco.com]

Thank you very much! Works like charm.

Btw. is there any way to configure the dhcp allocation range for the subnet? Similar to ESC XML?