Skip to content

Latest commit

 

History

History
237 lines (187 loc) · 7.71 KB

First_OSP_Env_walkthrough.adoc

File metadata and controls

237 lines (187 loc) · 7.71 KB
Raw

Config on OpenStack

In this document we will explain how one could setup their laptop for AgnosticD deployment with OpenStack.

If you are a Red Hatter, you can use rhpds.redhat.com to request access to our OpenStack cluster. . Log in to https://rhpds.redhat.com using your opentlc user. . Go to Services → Catalogs → Events Development → Summit DEV OSP Sandbox. . Click Order → Submit

Note
 You will receive three emails indicating the status of the environment and instructions for accessing the environment. In the third email you receive all information you need to login to the client machine that would have the rest of required information.
Note
 You can use the VM as your ansible host or copy the files over to your laptop and work locally.

Configure your environment for running OpenStack Ansible

Note
 on Fedora dnf install python3-openstacksdk python3-openstackclient python-openstackclient-doc python-openstackclient-lang python3-heatclient python-heatclient-doc python3-dns will do the job (you may choose to skip doc and lang packages).

  1. Please make sure the file /etc/ansible/hosts doesn’t exist or is empty, otherwise this default inventory file will cause problems later.

  2. Install virtualenv and pip3 (On your laptop or on the clientVM):

    # on Linux
$ sudo yum install python3-pip python-virtualenv -y
# on Mac
$ brew install python pyenv-virtualenv

  3. Create virtualenv environment and download python requirements:

    1. Create virtualenv and activate

      $ virtualenv openstack-ansible-2.9

##In Mac
$ pyenv virtualenv openstack-ansible-2.9


## In Mac, if you find the error " the error: error: pyenv: pip: command not found]", it could because you need pip3, in that case please do:
$ alias pip=pip3
$ pip install --upgrade pip

$ source openstack-ansible-2.9/bin/activate

## In Mac
$ source /Users/[USER]/.pyenv/versions/openstack-ansible-2.9/bin/activate

## ^replace [USER] with your username or the proper path

    2. Install the python modules inside that virtualenv

      • On Mac

        $ pip3 install -r https://raw.githubusercontent.com/redhat-cop/agnosticd/development/ansible/configs/ocp4-disconnected-osp-lab/files/macos_requirements.txt

      • On Linux with Python 2

        (openstack-ansible-2.9) $ pip install -r https://raw.githubusercontent.com/redhat-cop/agnosticd/development/tools/virtualenvs/openstack-ansible-2.9-python2.txt

      • On Linux with python 3:

        (openstack-ansible-2.9) $ pip install -r https://raw.githubusercontent.com/redhat-cop/agnosticd/development/tools/virtualenvs/openstack-ansible-2.9-python3.txt

      • Multi-platform, latest modules (should work for all with both python2 and python3)

        (openstack-ansible-2.9) $ pip install -r https://raw.githubusercontent.com/redhat-cop/agnosticd/development/tools/virtualenvs/openstack-ansible-latest.txt
# Install python modules needed by ansible
sudo pip install openstacksdk

# Install openstack CLIs
sudo pip install python-openstackclient python-heatclient

Getting your OpenStack Credentials

  1. Create the ~/.config/openstack/clouds.yaml file on your laptop using the information provided in the final email.

    $ mkdir -p ~/.config/openstack
$ vim ~/.config/openstack/clouds.yaml

  2. Review your ~/.config/openstack/clouds.yaml:

    cat ~/.config/openstack/clouds.yaml
clouds:
  35eb-project:
    auth:
      auth_url: "http://169.47.17.15:5000/v3"
      username: "35eb-user"
      project_name: "35eb-project"
      project_id: "1a79cf800ff94754bb495e2c1fd9d433"
      user_domain_name: "Default"
      password: "YOUR_TEMP_PASSWORD"
    region_name: "regionOne"
    interface: "public"
    identity_api_version: 3

  3. Check that your credentials are working:

    $ openstack --os-cloud=GUID-project server list
+--------------------------------------+-----------+--------+------------------------------------------------+-------+---------+
| ID                                   | Name      | Status | Networks                                       | Image | Flavor  |
+--------------------------------------+-----------+--------+------------------------------------------------+-------+---------+
| 653fb842-6ce8-4eb0-a51a-dc0f3d5fb103 | bastion   | ACTIVE | 35eb-ocp-network=192.168.47.33, 169.47.183.214 |       | 2c2g30d |
+--------------------------------------+-----------+--------+------------------------------------------------+-------+---------+

  4. Try to login to OpenStack UI: http://horizon.red.osp.opentlc.com/dashboard/auth/login/. You must use the credentials from .config/openstack/clouds.yaml to login to the UI.

Setting up AgnosticD and your development environment

  1. Clone the AgnosticD repository:

    git clone https://github.com/redhat-cop/agnosticd

  2. Create your secret.yml file oustide the repository, and edit it using the correct credentials based on your clouds.yml file:

    cat << EOF >> ~/secret.yml
# Authenication for OpenStack in order to create the things
# RED
osp_auth_username: CHANGEME
osp_auth_password: CHANGEME
osp_project_name: CHANGEME
osp_project_id: CHANGEME


osp_auth_url: http://169.47.188.15:5000/v3
osp_auth_project_domain: default
osp_auth_user_domain: default

# DNS

osp_cluster_dns_server: ddns01.opentlc.com
osp_cluster_dns_zone: students.osp.opentlc.com
ddns_key_name: PROVIDED_BY_ADMIN          # default value is set to "hmac-dm5"
ddns_key_secret: PROVIDED_BY_ADMIN

# Repo

own_repo_path: PROVIDED_BY_ADMIN

# Do not create PROJECT, we already have one and want to use it

osp_project_create: false

EOF

  3. First checkpoint, make sure this secret file is correct by running the test-empty-config.

    cd agnosticd/ansible

ansible-playbook main.yml \
  -e @configs/test-empty-config/sample_vars_osp.yml \
  -e @~/secret.yml

  4. Copy the sample_vars.yml file and call it my_vars.yml

    cp configs/just-some-nodes-example/sample_vars_osp.yml \
  configs/just-some-nodes-example/my_vars.yml

  5. Edit the my_vars.yml and change the guid value to something short and unique.

    Warning
    		 Do not pick the same GUID as the one you got for access to the OSP cluster.

  6. Second checkpoint, Run the ansible-playbook command to deploy just-some-nodes-example

    ansible-playbook main.yml \
  -e @configs/just-some-nodes-example/my_vars.yml \
  -e @~/secret.yml
    Note
    		 If you are having python2 Vs. Python3 issues, Add /usr/bin/python3.6 before the ansible-playbook command. For example: /usr/bin/python3.6 ansible-playbook ansible/main.yml -e @configs/just-some-nodes-example/my_vars.yml -e@~/secret.yml

  7. Check that the VM was installed and ssh into the box using the created key

    openstack --os-cloud=35eb-project server list
ssh -i /tmp/output_dir/${GUID}_infra_ssh_key.pem [email protected]

  8. You can now adapt my_vars.yml to your needs. Create different kind of instances, more security groups, etc.

Clean up

  1. Destroy the deployment:

    ansible-playbook destroy.yml \
  -e @configs/just-some-nodes-example/my_vars.yml \
  -e @~/secret.yml

What’s next ?