Developing a Heat Template

SBC SWe Cloud deployments can be instantiated in an OpenStack environment using standard Heat templates.  A Heat template is a .yaml file that provides essential information to OpenStack that enables creating the VM resources the SBC requires during the orchestration process. An SBC template also includes parameters needed to customize the deployment and to configure essential networking. Parameters can be populated with default values directly in the template or parameter values can be specified when an instance is deployed through user input or in an environment file. Refer to OpenStack documentation, or documentation from your OpenStack provider, for information on using Heat templates.

Ribbon provides a variety of example Heat templates for different types of SBC deployments. Use these example templates as reference to identify parameter input that is required for different SBC deployment characteristics. For example, different examples determine whether the SBC deployment is HA or standalone, whether the deployment uses DHCP, whether the deployment supports dual stack (IPv4 and IPv6), and other deployment variations. One approach is to select the example template that is most similar to your intended deployment and then customize it as needed. It could be necessary to combine sections from more than one example template to develop a template that instantiates the specific deployment you want.

Comment statements within the examples explain how to implement customizations for optional features such as adding additional IP addresses to ports, enabling SR-IOV on an interface, adding a second management port, or implementing packet port redundancy. Refer to the SBC Core release notes for information on how to download the example template files.

Template Parameters

The exact contents required in a template file differs based on the specific characteristics of the intended deployment, but the following parameter categories appear in SBC templates:

• System Settings – these parameters include general system setting such as the flavor, image, SBC personality type, SBC system name, and a security_group name.
• Instance-specific Settings – these parameters are specific to the instance being instantiated such as the node name (ceName), role (ceRole), and cluster configuration mode (ceMode).
• External and Private Network Settings – these parameters provide information on the external and private networks the SBC will use, such as the names of the networks and settings for the private network subnets.
• EMS settings – these parameters identify the IP address and login credentials for accessing the EMS system that will be used to manage the SBC.  
• OAM settings – if an SBC node is going to be part of a cluster that will use OAM node configuration mode, these parameters identify the IP addresses of the OAM nodes. Refer to SBC SWe Configuration Management.
• Node login credentials – These parameters specify login details such as the public key for the admin and linuxadmin users and optional passwords for these accounts.

Refer to the template file examples for more details on the parameters that can be included in a template file.  

Metadata and Userdata

The user data and metadata sections of the template contain essential configuration information that the SBC VM requires to initialize. Metadata consists primarily of information related to the SBC interfaces such as IP addresses and gateways. Userdata is comprised of user-specified data such as the system name, instance name, and whether the instance should take the active or standby role.The data is stored by the metadata service and retrieved when the instance boots up.

The values in these sections must be provided in a specific format and syntax. Formatting or syntax errors in the template can prevent the VM from booting properly. Refer to Metadata and Userdata Format for the required metadata and userdata formats and descriptions of the parameters. If necessary after instantiation, metadata and userdata can be updated using nova APIs. However any such changes do not take effect until the instance is rebooted. 

Environment Files

OpenStack allows you to specify an environment file along with a template when launching an instance. When included, an environment file provides parameter values that are called for by the template and override defaults specified within the template file. If you want to reuse a template file to deploy multiple instances, an environment file can provide some specific parameter values for the specific instance while the template remains generic. An environment file cannot be used to provide metadata or userdata. Refer to OpenStack documentation for more information on using environment files.