Parameter | Description | Default |
---|
-f <flavor size> [dev | std] | Use this parameter to specify the flavor size for the deployment. For customer deployments, use the option std . | all sizes |
-h <ha type> [simplex | ha | n_1_ha] | Use this parameter to specify an HA model for the deployment. The options are: ha - to specify 1:1 HA redundancy.n_1_ha - to specify an N:1 HA deployment. N can be up to 4 for S-SBC and M-SBC deployments. Use this parameter with the --num_instances parameter which specifies the number of instances in the deployment.simplex - to specify a standalone instance for a test environment.
| all HA models |
-i <interface type> [virtio | sriov | provider] | Use this parameter to specify the network interface type for your deployment. The options are: provider - to specify a provider network.sriov - to specify an SR-IOV (single root input/output virtualization) network.virtio - to specify a virtio network.
| all interface types |
-p <prod_version> | Use this parameter to specify the SBC product version number. This parameter is required. Provide the full release number within quote marks. For example: -p "8.00.00" | n/a |
-q <qcow_image_file> | Include this parameter to specify that you want to include the SBC software .qcow2 image file within the CSAR package. Including the image file greatly increases the size of the CSAR file and is not required by VNFM. If you use this option, specify the name of the image file following the -q parameter. | no image file |
-s <subversion> | Use this parameter to specify the SBC release number. This parameter is required. Provide the release number within quote marks. For example: -s "R000" | n/a |
-v <vnfd_template> | Include this parameter to specify the full path and the name of the VNFD template file. If the template file resides in the same directory as the script, the -v parameter is not needed. | current directory |
--affinity [AntiAffinity | Affinity |None] | Use this parameter to specify on which hosts VMs are placed. The options are: AntiAffinity - to specify that each VM is placed on a separate physical host.
Affinity - to specify that all VMS are placed on the same physical host.
None - to not specify a preference and allow the OpenStack environment to determine the placement of VMs.
| AntiAffinity |
--cinder_boot | Include this parameter to specify that you want to allocate a bootable cinder volume and copy the boot image (the .qcow2 image) to that volume before starting the VM. By default no cinder boot volume is created. Activating this option causes the initial boot time to increase significantly. | no cinder boot volume |
--cinder_log | Include this parameter to specify that you want to allocate a cinder volume to use for /var/log. By default no cinder log volume is created. This option may be used to re-associate the /var/log directory tree from a previous orchestration to a new orchestration, by specifying that boot volume during orchestration. | No cinder log volume |
--ipv6 | Include this parameter to specify that you want to use IPv6 addressing for the networks in your deployment. | IPv4 |
--num_oam_instances <num_oam_instances> | Include this parameter to specify the number of OAM node instances to create within an N:1 HA deployment that will use the OAM configuration model. For example, specify 2 to create a 1:1 HA pair of OAM nodes. For deployments that will use the Direct Single configuration model (standalone or 1:1 HA deployments), the default value of 0 applies because OAM nodes are not required. Refer to SBC SWe Configuration Management for descriptions of both models. | 0 |
--num_instances <number> | Use this parameter to specify the number of instances to create within an N:1 HA deployment. The default value is 5 which creates a 4:1 HA deployment. | 5 |
--no_dhcp_ha | Include this parameter to specify that you do not want to use Dynamic Host Configuration Protocol (DHCP) on the internal HA network. | DHCP is enabled on the internal HA network |
--personality [isbc | msbc | ssbc | tsbc | mrfp | slb ] | Use the parameter to specify the type of SBC deployment to create. The options are: isbc - integrated SBC deploymentmsbc - media SBC component of a distributed SBC deploymentssbc - signaling SBC component of a distributed SBC deploymenttsbc - media/transcoding SBC component of a distributed SBC deploymentmrfp - media resource function processor (MRFP) nodeslb - SIP-aware front-end load-balancer node
| all types |
--proprietary_vnfd_format | Include this parameter to specify to use a proprietary format for the VNFD file rather than the SOL001 standard format. | not enabled |
--prov_mgmt_virtio | If you specify to use the provider network type, include this parameter to specify that you want to override that choice for the management interface and use a virtio network instead. | not enabled |
--private_key_file <file> | Use these options to specify the path and name of a private key file and a certificate file to use to generate a signature for the CSAR file. A signature is not currently required by VNFM.
| ~/certs/key.pem |
--certificate_file <file> | ~/certs/certificate.pem |
--sbc_public_key <file> | Include this parameter to specify a path and name for a file containing a default public key to provide in the Cloud Config Init Data section on the Environment tab in the VNF Deployment Wizard. This section identifies the public key required to SSH to the deployed SBC. Specifying a key file with this parameter makes the key available as the default when a user deploys a VNF using this CSAR file. A user can still override the default with a different key when deploying. | Example: id_rsa.pub |