Login
Contents x
Assigning the Profile in Docker
  • 12 Sep 2024
  • 9 Minutes to read
  • Contributors
  • Print
  • PDF
Contents

Assigning the Profile in Docker

  • Updated on 12 Sep 2024
  • 9 Minutes to read
  • Contributors
  • Print
  • PDF
Article summary

Requirements

You must ensure you have the following items before starting the procedure. If you are missing anything, contact Technical Support.

A. SSH client (such as PuTTY).

B. The username and password for the skylight account for all appliances that are running Legacy orchestrator software.

C. The Docker host must have been allotted the required CPU, disk data, and memory. Target Docker host must have been configured for the desired profile.

D. From Legacy orchestrator 23.12 or later, mediation(s) volumes configuration must be followed as per table below:

Profile NameTotal mediation(s) / additional disk(s)Mapping mediation(s) per additional disk(s)(IOPS@6KB)*
5K1 mediation / 0 diskMediation 1 on OS of docker host disk5K
15k2 mediations / 1 diskMediation 1 and 2 on additional disk 115k
30K3 mediations / 2 disksMediation 1 on additional disk 110K
30K3 mediations / 2 disksMediation 2 and 3 on additional disk 220K
60K6 mediations / 4 disksMediation 1 on additional disk 110K
60K6 mediations / 4 disksMediation 2 and 3 on additional disk 220K
60K6 mediations / 4 disksMediation 4 on additional disk 310K
60K6 mediations / 4 disksMediation 5 and 6 on additional disk 420K

*For 15K, 30K and 60K profiles, disk I/O must be split over distinct mount points. Average latency must remain under 5ms.

E. The Docker host configuration must meet the requirement for target profile. Configure disk (format, mount, etc.) first, and then set volume location data for new mediation via socli, as seen in the procedure below.

F. The target Docker host must have network connectivity to the network elements.

G. Services must be started when deploying the profile.

Back up the Data Store

The profile configuration will perform database modifications. As a precaution, it is recommended to take a database backup.

Requirement: Legacy orchestrator services must be started.

To back up the MySQL database

  1. Open an SSH terminal session to Legacy orchestrator CLI on port 2200.

  2. Log in as the skylight user.

  3. Create a backup of the data store by entering:

database backup

Notes:

On the Hot Standby system, the backup must be taken from the active site. The backup file is stored in /home/skylight/so/mysql-ha/backups folder.

On the Non-Hot Standby system, the backup is generated as a tar.gz file in the ${volume-location so-mysql}/backups folder.

By default: /home/skylight/so/mysql/backups folder.

Check the med-ip Configuration

Note: This step is to show the med-ip(s) configuration on the Legacy orchestrator Docker. This med-ip(s) information will be used if you want to reconfigure after assigning the configuration profile.

  1. Open an SSH terminal session to Legacy orchestrator CLI on port 2200.

  2. Log in as the skylight user.

  3. Check med-ip configuration by entering:

config show

Example:

Skylight: config show 

network subnet = ["172.18.0.0/24" "fd00:1::/80" ] - ipv6enabled = "true"
network core-ip = 
network core-http-port = 80
network core-https-port = 443
network medn1-ip = 10.220.199.234
network medn2-ip = 10.220.199.234
network medn3-ip = 10.220.199.234
network medn4-ip = 10.220.199.234
network medn5-ip = 10.220.199.234
network medn6-ip = 10.220.199.234
network med-snmp-port = 1163
volume-location so-config = /home/skylight/so/config
volume-location so-mysql = /home/skylight/so/mysql
volume-location so-data = /home/additional-disk/sdb/mediation1
volume-location so-logs = /home/skylight/so/logs
volume-location so-data-medn2instance = /home/additional-disk/sdc/mediation2
volume-location so-data-medn3instance = /home/additional-disk/sdc/mediation3
volume-location so-data-medn4instance = /home/additional-disk/sdd/mediation4
volume-location so-data-medn5instance = /home/additional-disk/sde/mediation5
volume-location so-data-medn6instance = /home/additional-disk/sde/mediation6

Assign the Profile

With the disk configuration, the deployment profile can now be assigned to the virtual machine.

Starting the Application

This procedure will start the Legacy orchestrator services.

Starting the application for Hot Standby configuration

  1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
  2. Log in as the skylight user.
  3. Stop redundancy by entering:
redundancy control stop
  1. After redundancy stopped you can start services by entering:
services start
  1. When prompted enter: y
Proceed? (y/N)

Note: Step 4 and step 5 must be done on both sites via socli (SSH port 2200) of the redundant pair.

Starting the application for Non-Hot Standby configuration

  1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
  2. Log in as the skylight user.
  3. Start services by entering:
services start
  1. When prompted enter: y
Proceed? (y/N)

Assigning the Configuration Profile

Assigning the profile for a Hot Standby configuration

  1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
  2. Log in as the skylight user.
  3. Assign a profile by entering:
deployment edit profile <profile_name>  user-profile <number of users>  session-profile <number of sessions>
  1. When prompted appear: Enter: y
Proceed? (y/N)
y
Configuring deployment profile…

Note: These steps must be run on both sites of the redundant pairs.

For a more detailed command description, see the Deployment Edit Command section in the Docker CLI Reference article.

Assigning the profile for a Non-Hot Standby configuration

  1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
  2. Log in as the skylight user.
  3. Assign a profile by entering:
deployment edit profile <profile_name>  user-profile <number of users>  session-profile <number of sessions>
  1. When prompted appear: Enter: y
Proceed? (y/N)
y
Configuring deployment profile…

Note: For a more detailed command description, see the Deployment Edit Command section in the Docker CLI Reference article.

Reconfiguring the med-ip(s)

Note: This procedure to reconfigure the med-ip(s) as before upgrading. This procedure can be skipped if the user does not want a specific configuration.

Reconfiguring the med-ip(s) for a Hot Standby configuration

  1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

  2. Log in as the skylight user.

  3. Reconfigure the med-ip(s) for the Legacy orchestrator Docker:

config set network med-ip mediation <Y> <Z>

Where:

  • Y is a mediation number from 1-6
  • Z is the IP address in IPv4 or IPv6 format (the IPs must exist on the Docker host)

Example:

Skylight: config set network med-ip mediation 2 10.220.199.234
Removing existing Skylight orchestrator containers ...
IP address has been set to: [10.220.199.234]
  1. Verify med-ip configuration by entering:
config show

Example:

Skylight: config show 

network subnet = ["172.18.0.0/24" "fd00:1::/80" ] - ipv6enabled = "true"
network core-ip = 
network core-http-port = 80
network core-https-port = 443
network medn1-ip = 10.220.199.234
network medn2-ip = 10.220.199.234
network medn3-ip = 10.220.199.234
network medn4-ip = 10.220.199.234
network medn5-ip = 10.220.199.234
network medn6-ip = 10.220.199.234
network med-snmp-port = 1163
volume-location so-config = /home/skylight/so/config
volume-location so-mysql = /home/skylight/so/mysql
volume-location so-data = /home/additional-disk/sdb/mediation1
volume-location so-logs = /home/skylight/so/logs
volume-location so-data-medn2instance = /home/additional-disk/sdc/mediation2
volume-location so-data-medn3instance = /home/additional-disk/sdc/mediation3
volume-location so-data-medn4instance = /home/additional-disk/sdd/mediation4
volume-location so-data-medn5instance = /home/additional-disk/sde/mediation5
volume-location so-data-medn6instance = /home/additional-disk/sde/mediation6

Note: These steps must be run on both sites of the redundant pairs.

Reconfiguring the med-ip(s) for a Non-Hot Standby configuration

  1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.

  2. Log in as the skylight user.

  3. Reconfigure the med-ip(s) for the Legacy orchestrator Docker:

config set network med-ip mediation <Y> <Z>

Where:

  • Y is a mediation number from 1-6
  • Z is the IP address in IPv4 or IPv6 format (the IPs must exist on the Docker host)

Example:

Skylight: config set network med-ip mediation 2 10.220.199.234
Removing existing Skylight orchestrator containers ...
IP address has been set to: [10.220.199.234]
  1. Verify med-ip configuration by entering:
config show

Example:

Skylight: config show 

network subnet = ["172.18.0.0/24" "fd00:1::/80" ] - ipv6enabled = "true"
network core-ip = 
network core-http-port = 80
network core-https-port = 443
network medn1-ip = 10.220.199.234
network medn2-ip = 10.220.199.234
network medn3-ip = 10.220.199.234
network medn4-ip = 10.220.199.234
network medn5-ip = 10.220.199.234
network medn6-ip = 10.220.199.234
network med-snmp-port = 1163
volume-location so-config = /home/skylight/so/config
volume-location so-mysql = /home/skylight/so/mysql
volume-location so-data = /home/additional-disk/sdb/mediation1
volume-location so-logs = /home/skylight/so/logs
volume-location so-data-medn2instance = /home/additional-disk/sdc/mediation2
volume-location so-data-medn3instance = /home/additional-disk/sdc/mediation3
volume-location so-data-medn4instance = /home/additional-disk/sdd/mediation4
volume-location so-data-medn5instance = /home/additional-disk/sde/mediation5
volume-location so-data-medn6instance = /home/additional-disk/sde/mediation6

Configuring Mediation Volumes

Configure mediation volumes for a Hot Standby configuration

For Mediation 1

  1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
  2. Log in as the skylight user.
  3. Configure volume data for new mediation by entering:
config set volume-location data so-data <X>

Where:

  • X is an absolute path for the location created for data volume.
    Example:
config set volume-location data so-data /home/additional-disk/sdb/mediation1

Note: These steps must be run on both sites of the redundant pairs.

For other mediations

  1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
  2. Log in as the skylight user.
  3. Configure volume data for new mediation by entering:
config set volume-location data mediation <Y> <Z>

Where:

  • Y is a mediation number from:
    • 2-12 with Legacy orchestrator Docker version 23.04.1 or prior
    • 2-6 with Legacy orchestrator Docker version 23.12 or later
  • Z is an absolute path for the location created for data volume.
    Example:
config set volume-location data mediation 2 /home/additional-disk/sdb/mediation2
config set volume-location data mediation 3 /home/additional-disk/sdc/mediation3
config set volume-location data mediation 4 /home/additional-disk/sdd/mediation4
config set volume-location data mediation 5 /home/additional-disk/sde/mediation5
config set volume-location data mediation 6 /home/additional-disk/sdf/mediation6

Note: These steps must be run on both sites of the redundant pairs.

Configure mediation volumes for a Non-Hot Standby configuration

For Mediation 1

  1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
  2. Log in as the skylight user.
  3. Configure volume data for new mediation by entering:
config set volume-location data so-data <X>

Where:

  • X is an absolute path for the location created for data volume.
    Example:
config set volume-location data so-data /home/additional-disk/sdb/mediation1

For other mediations

  1. Open an SSH terminal session to the Legacy orchestrator CLI on port 2200.
  2. Log in as the skylight user.
  3. Configure volume data for new mediation by entering:
config set volume-location data mediation <Y> <Z>

Where:

  • Y is a mediation number from:
    • 2-12 with Legacy orchestrator Docker version 23.04.1 or prior
    • 2-6 with Legacy orchestrator Docker version 23.12 or later
  • Z is an absolute path for the location created for data volume.
    Example:
config set volume-location data mediation 2 /home/additional-disk/sdb/mediation2
config set volume-location data mediation 3 /home/additional-disk/sdc/mediation3
config set volume-location data mediation 4 /home/additional-disk/sdd/mediation4
config set volume-location data mediation 5 /home/additional-disk/sde/mediation5
config set volume-location data mediation 6 /home/additional-disk/sdf/mediation6

Starting the Application

This procedure will start the application with the new deployment profile.

Starting the application for a Hot Standby configuration

  1. Open an SSH terminal session to the Legacy orchestrator designated as the preferred active site on port 2200.
  2. Log in as the skylight user.
  3. Start the Hot Standby process by entering:
redundancy control start

Note: It may take up to 10 minutes for the Legacy orchestrator services to be healthy.

Starting the application for a Non-Hot Standby configuration

  1. Open an SSH terminal session to the Legacy orchestrator on port 2200.
  2. Log in as the skylight user.
  3. Start the application by entering:
services start

Note: It may take up to 10 minutes for the Legacy orchestrator services to be healthy.

Confirm the Changing Profile

To confirm the changing profile

  1. Open an SSH terminal session to the Legacy orchestrator designated as the preferred active site on port 2200.
  2. Log in as the skylight user.
  3. Confirm the change by entering:
deployment show configuration

An output similar to the following is displayed:

Skylight: deployment show configuration 
[ Deployment configuration ]

  Deployment type   : multi-node
  Profile name      : <profile_name>
  User profile name : user-20
     Max user session   : 20
  Session profile name: 52k  
Cluster configuration : 
     Cluster type       : medcluster
     Node Configuration : 
         Node name       : medn1
         Total instances : 1
         Node name       : medn2
         Total instances : 1
         Node name       : medn3
         Total instances : 1

© 2024 Cisco and/or its affiliates. All rights reserved.
 
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks


Was this article helpful?
What's Next
© 2024 Cisco Privacy Statement Cookies Legal
Change password!
Changing your password will log you out immediately. Use the new password to log back in.
Change profile
Success!
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
Logout