Skip to content

Instantly share code, notes, and snippets.

@sodar
Last active July 31, 2018 11:23
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save sodar/a4754538b3bd10a5dabbde9c7f6ee605 to your computer and use it in GitHub Desktop.
Save sodar/a4754538b3bd10a5dabbde9c7f6ee605 to your computer and use it in GitHub Desktop.
Run contrail-ansible-deployer

Controller deployment instructions

This document describes the steps necessary to deploy w Contrail Controller for Contrail Windows demo setup. Documents serves as an appendinx to Contrail Windows Demo instructions.

Prerequisites

  • Linux development laptop serving as an Ansible control node
  • CentOS Linux VM for Contrail Controller

Steps

  1. Install required packages on Linux development:

    git clone https://github.com/Juniper/contrail-windows-ci
    cd contrail-windows-ci/ansible
    pip install -r python-requirements.txt
  2. Pull contrail-ansible-deployer repository and checkout commit used in Contrail Windows CI

    • Contrail Windows CI currently uses: 6b86bcd7056e20c6d36d3808d2750b1395528b11
    git clone https://github.com/Juniper/contrail-ansible-deployer
    cd contrail-ansible-deployer
    git checkout 6b86bcd7056e20c6d36d3808d2750b1395528b11
  3. Create a config/instances.yaml file based on instances.yaml from this gist

  4. Replace variables in config/instances.yaml with the following values:

    • CONTROLLER_ROOT_PASSWORD - root password for Controller VM
    • CONTROLLER_IP - IP address of the Controller VM
    • CONTROLLER_IP_GATEWAY - IP gateway for Controller VM
    • CONTROLLER_INTERFACE_NAME - interface reported by CentOS
  5. Run ansible playbooks

    ansible-playbook -i inventory/ playbooks/configure_instances.yml
    ansible-playbook -e orchestrator=openstack -i inventory/ playbooks/install_contrail.yml
CONTAINER_REGISTRY: "opencontrailnightly"
REGISTRY_PRIVATE_INSECURE: True
provider_config:
bms:
ssh_user: root
ssh_pwd: CONTROLLER_ROOT_PASSWORD
instances:
bms1:
provider: bms
ip: CONTROLLER_IP
roles:
config_database:
config:
control:
analytics_database:
analytics:
webui:
vrouter:
openstack:
openstack_compute:
contrail_configuration:
CLOUD_ORCHESTRATOR: "openstack"
CONTAINER_REGISTRY: "opencontrailnightly"
CONTRAIL_VERSION: "ocata-master-91"
CONTROLLER_NODES: CONTROLLER_IP
LOG_LEVEL: SYS_DEBUG
PHYSICAL_INTERFACE: CONTROLLER_INTERFACE_NAME
VROUTER_GATEWAY: CONTROLLER_IP_GATEWAY
AUTH_MODE: keystone
KEYSTONE_AUTH_ADMIN_PASSWORD: c0ntrail123
KEYSTONE_AUTH_HOST: CONTROLLER_IP
KEYSTONE_AUTH_URL_VERSION: "/v3"
RABBITMQ_NODE_PORT: 5673
kolla_config:
kolla_globals:
network_interface: "CONTROLLER_INTERFACE_NAME"
api_interface: "CONTROLLER_INTERFACE_NAME"
neutron_external_interface: "CONTROLLER_INTERFACE_NAME"
kolla_external_vip_interface: "CONTROLLER_INTERFACE_NAME"
kolla_internal_vip_address: CONTROLLER_IP
contrail_api_interface_address: CONTROLLER_IP
enable_haproxy: no
enable_ironic: 'no'
enable_ironic_notifications: 'no'
openstack_service_workers: 1
openstack_release: "ocata"
contrail_docker_registry: "opencontrailnightly"
neutron_opencontrail_init_image_full: "opencontrailnightly/contrail-openstack-neutron-init:{{ contrail_version }}"
nova_compute_opencontrail_init_image_full: "opencontrailnightly/contrail-openstack-compute-init:{{ contrail_version }}"
kolla_passwords:
keystone_admin_password: c0ntrail123
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment