4.2.2 Create OpenStack Parameter File for Signaling

This procedure manually creates the input parameters file to be provided while deploying signaling stacks.
Prerequisites:

All the respective infrastructures have to be up and running.

  1. Log in to the OpenStack CLI.
  2. Create the parameter file.
    1. Go to the folder created in Prepare OpenStack Template and Environment Files for storing the templates.
    2. Create an empty signaling parameter file in this folder following this naming convention to identify the purpose of the file.

      <DSR Name>_<Site Name>_SignalingNode_Params.yaml

      Example:

      dsrCloudInit_Site00_SignalingNode_Params.yaml

    Note:

    • Refer to Example Template File for a sample file with values.
    • It is important to keep the example file ready since this helps you understand the use of each key value pair described in the next step while creating the parameter file.

    Note:

    • Refer to Example Template File to create the parameter file in YAML format.
    • Follow these guidelines while working with the YAML files.
      • The file must end with .yaml extension.
      • YAML must be case-sensitive and indentation-sensitive.
      • YAML does not support the use of tabs. Instead of tabs, it uses spaces.
      • This file is in YAML format and it contains key:value pairs.
      • The first key should be parameters: and then the remaining required key/value pairs for the topology.
    This table lists all required key:value pairs.

    Table 4-3 Signaling key:value pairs

    Key Name Type Description
    numSoams number The number of SOAMs at this signaling node
    soamImage string The VM image for an SOAM
    soamFlavor string The flavor that defines the VM size for an SOAM
    soamVmNames comma_delimited_list List of SOAM VM names
    soamAZ string The availability zone into which SOAM servers should be placed

    Note: In DSR 8.6.0.0.0, all SOAM servers are placed in the same availability zone.

    soamSG string Server group for the SOAM VMs
    numDas number The number of DAs at this signaling node
    daImage string The VM image for a DA
    daFlavor string The flavor that defines the VM size for a DA
    daVmNames comma_delimited_list List of DA VM names
    daAZ string The availability zone into which DA servers should be placed

    Note: In DSR 8.6.0.0.0, all DA-MP servers are placed in the same availability zone.

    daSG string Server group for the DA VMs
    daProfileName string The MP profile to be applied to all DAs. Possible values are: VM_Relay, VM_Database, VM_6K_Mps, VM_8K_Mps, VM_10K_Mps, VM_12K_Mps, VM_14K_Mps, VM_16K_Mps, VM_18K_Mps, VM_21K_Mps, VM_24K_Mps, VM_27K_Mps, VM_30K_Mps
    numIpfes number The number of IPFEs at this signaling node
    ipfeImage string The VM image for an IPFE
    ipfeFlavor string The flavor that defines the VM size for an IPFE
    ipfeVmNames comma_delimited_list List of IPFE VM names
    ipfeAZ string The availability zone into which IPFE servers should be placed

    Note: In DSR 8.6.0.0.0, all IPFE servers are placed in the same availability zone.

    ipfeSGs comma_delimited_list Server group for each IPFE VM
    numStps number The number of STPs at this signaling node
    stpImage string The VM image for an STP
    stpFlavor string The flavor that defines the VM size for an STP
    stpVmNames comma_delimited_list List of STP VM names
    stpAZ string The availability zone into which STP servers should be placed

    Note: In DSR 8.6.0.0.0, all STP servers are placed in the same availability zone.

    stpSG string Server group for the STP VMs
    xmiPublicNetwork string External management interface
    imiPrivateNetwork string Internal management interface
    imiPrivateSubnet string Name of the IMI network
    imiPrivateSubnetCidr string The address range for the subnet
    xsiPublicNetwork string The address range for the subnet
    primaryNoamVmName string Name of NOAM VM that the config XML was loaded onto

    Note: Not used in 8.6.0.0.0

    In DSR 8.6.0.0.0, user should not provide any value to this key.
    noamXmiIps comma_delimited_list The XMI IPs for all NOAM servers, excluding VIPs

    Note: Not used in 8.6.0.0.0

    In DSR 8.6.0.0.0, user should not provide any value to this key.
    ntpServer string IP of the NTP server
    Note: The below keys are ONLY applicable for fixed IP scenario, with or without IDIH nodes.
    soamXmiIps comma_delimited_list Previously reserved IP for non-primary SOAMs to talk to external devices
    soamVip string VIP for SOAMs
    daXmiIps comma_delimited_list Previously reserved IP for DA MP to talk to external devices
    daXsiIps comma_delimited_list Previously reserved IP for DA MP to talk to signaling devices
    ipfeXmiIps comma_delimited_list Previously reserved IP for IPFE to talk to external devices
    ipfeXsiIps comma_delimited_list Previously reserved IP for IPFE to talk to signaling devices
    stpXmiIps comma_delimited_list Previously reserved IP for STP to talk to external devices
    stpXsiIps comma_delimited_list Previously reserved IP for STP to talk to signaling devices
    ipfeXsiPublicIp string Reserved single IP address on signaling network to which remote diameter hosts route packets for load balancing over set of message processors
    stpSctpPorts comma_delimited_list The SCTP ports to be associated with STP

    Note: If there is no STP in topology. then provide empty list, for example, []

    Note: Open these ports beforehand on which STP connections are going to be created while doing configuration.

    These two parameters are applicable for TCP/SCTP to use with the Diameter connection.

    Note: Open these ports beforehand on which Diameter connections are going to be created while doing Diameter configuration.

    diameterTcpPorts comma_delimited_list The TCP ports to be associated with. If this parameter is not provided, then default ports are assigned.
    diameterSctpPorts comma_delimited_list The SCTP ports to be associated with. If this parameter is not provided, then default ports are assigned.
    The below keys are applicable only for scenarios which include IDIH nodes.
    idihAppImage string The VM image for the IDIH Application VM
    idihAppFlavor string The flavor that defines the size for the IDIH Application VM
    idihAppVmName string The IDIH Mediation VM name
    idihMedImage string The flavor that defines the size for the IDIH Mediation VM
    idihMedVmName string The IDIH Mediation VM name
    idihDbImage string The VM image for the IDIH Database VM
    idihDbFlavor string The flavor that defines the size for the IDIH Database VM
    idihDbVmName string The IDIH Database VM name
    idihAZ string The availability zone into which IDIH VMs should be placed
    idihIntPrivateNetwork string Name of the internal tenant network (that will be created) for communication between IDIH VMs
    idihIntPrivateSubnet string Name of the subnet (that will be created) on the IDIH internal tenant network (idihIntPrivateNetwork)