Installing an optional Blue Planet solution

You may need to add optional solutions to your platform if you did not add them during your installation process. For example, the logging solution is an optional solution and is therefore not included in the orchestration software in this release. For a list of optional solutions, see the Blue Planet MDSO and NFVO Solutions Release Notes.

 In multi-host clusters you only need to complete the steps on one host.

To add optional solutions after installation:

  1. Connect to your Blue Planet server using a secure shell terminal such as PuTTY or Tera Term.

  2. From any directory on the server, enter the solutionmanager container: solman

    Once you enter the solman command, you are in the solutionmanager.

  3. Update available solutions:

    (Cmd) check_available_solution

    If you previously performed this command, you must use the show_solutions command to display available solutions.

  4. Deploy using the appropriate commands based on your situation:

    1. To deploy a new optional solution:

      (Cmd) solution_deploy <solution_name>

      For example, to add the optional logging solution:

      (Cmd) solution_deploy bpdr.io.blueplanet.logging:x.x.x

      Replace with your repository, solution name, and version. For the previous example, if you use Orchestrate 17.02.01, replace x.x.x with version 4.0.1 for the logging solution and ensure you also add the elasticsearch solution as documented in the release notes.

      		 Be sure to check the Blue Planet MDSO and NFV Solutions Release Notes to ensure you install all required optional solutions, as some solutions have dependencies on others.

    2. To undeploy and deploy an optional solution that previously existed on the server enter:

      (Cmd) solution_undeploy <old_solution_name:version_number> --purge-host-vols -y
      (Cmd) solution_deploy <new_solution_name:version_number>
      		 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.

    3. For multi-host installations, scale any optional solutions that require it. For example, orchestration-ui or use case solutions:

      (Cmd) solution_scale <new_ui_or_use_case_solution:version_number> <# of hosts, typically 3>

  5. To exit Solution Manager: exit

  6. Wait a few minutes to allow all upgrade activities to complete, then open Nagios in your web browser:

    https://<bpadmin>:<bpadminpw>@${BP2_SITE_IP}/nagios

  7. Verify that all applications are green.

results matching ""

    No results matching ""