Various SBC cloud components and resources are identified using customer-generated naming conventions. The SBC VNF or Heat Orchestration facilitates providing these customized names for most resources. The SBC cloud naming conventions are enhanced to fill the gap by supporting additional cloud components. SBC cloud naming conventions enhancements include:

  • NOVA Name and Hostname conventions
    • Hostname used in External Communications – All customer tools for the Hostnames of individual VMs (VNFCs) are required to convey in any performance data, CDRs, or alarms (SNMP or flat files) to exactly match that instance's NOVA instance name. Consequently, the Hostname must also support the format and dashes required for the NOVA name.
    • Hostname at CLI and OS prompts – The name of the system reported at any command line (application CLI or OS Shell) must match the NOVA Instance name for cases where tools use login information to compare it to the information from NOVA as a mechanism to verify the connection to the correct target instance.
  • Mixed case support – In addition to supporting dashes, the individual Hostnames described described previously must also support mixed case (upper and lower case) alphanumeric characters in system naming (Hostname and name presented at command lines).
  • Character Limit for NOVA and Hostname
    • With the current version of VNF naming conventions, the NOVA name used by some instances require no less than 36 characters (including dashes). To provide some buffer against the NOVA name (and Hostname) increase, the supported Hostname length of 26 characters is increased to no less than 63 characters.
    • The current design for the SBC registration and PM stats is to append the HA address to the hostname/CE name. Since it is not guaranteed that this IP address is unique, which can create an illegal hostname, you must refrain from appending the IP address to the hostname/CE name.
    • Any internal application tables that reference other Ribbon nodes also support these expanded hostnames.
  • Dashes in OpenStack resource names – All resources (created manually in OpenStack , using HEAT orchestration, and using VFNM orchestration) must include dashes between the key components that make the name for that resource. 
  • Acceptable characters – Alphabetical (upper- and lower-case), numerical (0-9) and any of the following special characters: +,-,.,(,), with characters up to 63 characters.