jgroom33.blueplanet_solution_deploy

Blue Planet Solution Deployment

=========

This is an Ansible role that helps set up solutions for a Blue Planet server.

Requirements

Blue Planet
A lineup.yml file

Role Variables

Variable	Default	Comments (type)
`blueplanet_solution_docker_type`	gitlab	Type of docker registry
`blueplanet_solution_docker_url`	registry.blueplanet.com	URL of the registry
`blueplanet_solution_docker_username`	none	Username for the registry
`blueplanet_solution_docker_password`	none	Password for the registry
`blueplanet_solution_lineup_file`	./lineup.yml	Location of the lineup file
`blueplanet_solution_purge`	false	Remove old solutions

NOTE: Creating a Gitlab Registry Access Token
To use the Gitlab registry, you need an Access Token.

Go to the Gitlab website and log in.

Go to "User Settings" -> "Access Tokens".

Select the read_registry permission.

Click "Create personal access token".

Copy the generated token for the site's registry setup.

Dependencies

None

Example Playbook

- hosts: mdso
  gather_facts: false
  vars:
    blueplanet_solution_docker_username: "{{ lookup('env','BP_GIT_USERNAME') }}"
    blueplanet_solution_docker_password: "{{ lookup('env','BP_GIT_TOKEN') }}"
    blueplanet_solution_lineup_file: lineup.yml
  roles:
      - blueplanet-solution-deploy

Example `lineup.yml`

docker_registry:
  url: registry.blueplanet.com

platform_solution:
  name: platform
  vendor: blueplanet/bpps
  version: 19.06.01
application_solution:
  name: orchestrate
  vendor: mdso/19.06
  version: 19.06.3-87
additional_solutions:
  orchestrate_ui:
    name: orchestrate_ui
    vendor: mdso/19.06
    version: 19.06.1-322
  junipermxra:
    name: junipermxra
    vendor: blueplanet/resourceadapters/junipermx_yang_ra/master
    version: 1.0.0.1910