In this section:

Add additional VMs using the Stack Template Update

To commission a VM that is waiting to be deployed, use the sonus_dsc_hot_generator.py script to regenerate YAML with small changes. This script file is included in the dsc_swe_<rel>_<nb>_HOT.tgz that can be downloaded from the Global Support Portal (refer to Downloading Software Files).

Generate a New YAML File for Adding Extra VMs

Start
  1. Log in to OpenStack dashboard. 
  2. Click Project.
  3. Click Orchestration.
  4. Click Stacks.
  5. Click the stack on which you want to add the extra VM.
  6. Click Overview.
    The arguments are listed in the Description.

     

  7. Generate a new YAML file by executing the sonus_dsc_hot_generator.py with the original arguments but a different vm-count.
    For example, if the current vm-count is 2, then change it to 3.

    sonus_dsc_hot_generator.py --av-zones "" --config-drive true --flavour "" --ha0 None --image "" --imf0 None --imf1 None --mgt askaddr: --no-prompt --pkt0 askaddr: --pkt1 askaddr: --pkt2 None --pkt3 None --sec-group None --shared-mgt "" --ssh-key ""
--ver-str 16_1_0_nb20170914 --vm-count 3 --vm-role None extraDSCVMs.yaml


    The newly generated YAML file extraDSCVMs.yaml has 3 VMs enabled.

  8. Go to Update the Stack Template.

Update the Stack Template

Start
  1. Log in to the OpenStack dashboard.
  2. Click Project.
  3. Click Orchestration.
  4. Click Stacks.
  5. Click the required stack.
  6. Click the drop-down menu on the far-right side and select Select Template.


  7. Click Choose File and select the YAML file created in Generate a New YAML File for Adding Extra VMs (extraDSCVMs.yaml).


  8. Click Next.

    On the Update Stack Parameters page, the original values should be entered or there will be unexpected changes.  For the new VM, new IP addresses can be assigned. 



     

  9. Click Update.
  10. You will notice that the update is in progress.


    When the update is done, the Status will be changed to Update Complete.


    The new VMs will be booted up automatically while the existing VMs are not impacted.
  11. Go to Commission a Routing VM.

Commission a Routing VM

Use this procedure to commission a VM that has been deployed already such as the extra VMs are deployed when the stack is created.

Start

  1. SSH to one of the Routing and Management VMs on the DSC SWe using this VM‘s IP address.

    ssh root@<ip address of the DSC SWe>

  2. Log onto the system.

    User ID: <root> 
password: <root password>
  3. At the CLI prompt, enter startmenu, and press ENTER.
  4. From the Main Menu, select System, and press ENTER.
  5. Select Software Revisions, and press ENTER.
  6. Select Versions, Commission, Decommission, and press ENTER.


  7. Enter the VM slot to be commissioned and press ENTER (in this example, slot 3).


  8. Type y, and press ENTER.


  9. Do one of the following:

    1. If the software load on the new VM is the same as the software load on the existing VM, go to step 10.

    2. If the software load on the new VM is NOT the same as the software load on the existing VM, go to step 12.

  10. Enter the required VM type, and press ENTER (in this example, 1 for Routing VM).   



  11. Press ENTER. The system installs the load on the Routing VM in slot 3. Go to step 13.

  12.  Enter the required VM type, and press ENTER (in this example, 1 for Routing VM).  

    The system installs the load on the new Routing VM which is the same software load that is currently running on the existing Routing and Management VM.

  13. Enter y and press ENTER.

  14. Press c to continue.

  15. If you are prompted to enter a license key(s), do one of the following:

    1. If you are using the Legacy method to configure licensing for this VM, refer to Legacy Licensing Description and perform the licensing task as required.

    2. If you are using the Local Licensing method, refer to Local Licensing Description and perform the licensing task as required.

  16. Repeat this procedure with any additional VMs that should be commissioned.
  17. Navigate to the Available Software Versions screen and confirm the VM(s) has been commissioned.
  18. You may consider doing a Complete Configuration Backup (refer to Complete System Backup and Restore for the DSC SWe).

  • No labels