$ sudo vim /etc/bp2/solutionmanager/registry url: bpdr.io <or local registry name> username: xxxxx password: xxxxx Repeat this step on each host.
Performing high-level maintenance
This section describes:
Updating registry information
Blue Planet requires use of a software registry to download their Ciena software. There are many requirements to ensure your registry can download successfully, such as ensuring firewall ports are open. Blue Planet uses code in the /etc/bp2/solutionmanager/registry file to specify the URL, username, and password required to download this software.
There may be instances when your registry information may need to be changed. This may be as a result of a Ciena change or a change to your local repositories to control software distribution. Follow the steps below to change the docker registry file and ensure your single or multi-server deployment is aware of that change.
-
Use the Vim editor to access the Blue Planet Docker registry file and update the URL and username and password provided by Ciena Customer Support or your local registry administrator.
-
Save the registry file and exit vim.
By updating the registry information, solutionmanager can use the information to find the accurate registry. In order to deploy the core platform, the login credentials should be saved in "/home/bpadmin/.docker/config.json".
-
Ciena recommends you update the repository credentials on each host by running the following command on each Blue Planet server (single or clusters).
docker login -u <username> -p <password> -e "<email> <repository name>
This command updates the /home/bpadmin/docker/config.json file with the appropriate registry information and helps to ensure the success of future installations or upgrades.
Downloading Blue Planet platform or solution software updates
You can download optional software or upgrade to a more current version of software. Before downloading files, see the Blue Planet Orchestrate Upgrade document and ensure you have the prerequisite software and understand the proper upgrade workflow.
If your software registry location has changed, be sure to see Updating registry information for required and recommended steps.
Upgrading the Blue Planet platform or solution software
There are several steps and prerequisites depending on your upgrade needs. For a workflow summary or step-by-step instructions, see the Blue Planet Orchestrate Upgrade document specific to your release.
If your software registry location has changed, be sure to see Updating registry information for required and recommended steps.
|
|
If you purge and deploy the orchestration solution, other solutions such as alarms and RAs may not be synchronized with the newly deployed instance. Use the best practice of restarting the existing deployed solutions after orchestration redeployment using solman solution_app_restart.
|
Verifying Blue Planet applications and resource adapter software
You can verify the Blue Planet application software versions you installed on your server using the user interface or the command line.
UI verification
To verify the installed versions of the platform, orchestration solutions, and RAs:
-
Select your user account name (in the top right-hand corner) and click About.
The following details display on a separate pop-up window:
-
Installed sofware versions (repository.info.solution_filename:version_number)
-
Copyright and end user license agreement (EULA)
-
-
To close, click X.
Command line verification
To verify the platform and solutionmanager versions, for example, to prepare for an upgrade or download optional software solutions, use the File verification commands. The software versions below are examples only and may be different than your software versions.
| Commands | Verify |
|---|---|
docker ps | grep petcd | awk '{print $2}' |
petcd:0.1.1-2.2.0 |
docker ps | grep solutionmanager | awk '{print $2}' |
solutionmanager: 0.4.9-605.ec1189c.17.02 |
docker ps | grep swarm | awk '{print $2}' |
swarm: 0.1.1-0.4.0-1858.cd213b9 |
docker ps | grep pzk | awk '{print $2}' |
pzk: 0.1.3-z3.4.6-ciena6-58.6c0da1a |
solman sps |
Lists all the deployed docker containers including the platform solution: 17.01.02 |