You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
tacker/vagrant/devstack
Yasufumi Ogawa 77ecc2a7b3
Fix Vagrantfile for no_proxy is empty
4 months ago
..
group_vars Update config in tacker installer 7 months ago
helper Introduce vagrant for devstack 11 months ago
lib Update config in tacker installer 7 months ago
roles Introduce vagrant for devstack 11 months ago
samples Update config in tacker installer 7 months ago
.gitignore Introduce vagrant for devstack 11 months ago
README.md Update config in tacker installer 7 months ago
Vagrantfile Fix Vagrantfile for no_proxy is empty 4 months ago
ansible.cfg Introduce vagrant for devstack 11 months ago
hosts Update config in tacker installer 7 months ago
site.yaml Introduce vagrant for devstack 11 months ago

README.md

Devstack Installer for Tacker

What is this

Deployment tool for devstack for testing multi-VM OpenStack environment, consists of vagrant and ansible.

It only supports Ubuntu on VirtualBox currently.

How to use

Requirements

You need to install required software before running this tool. Please follow instructions on official sites for installation.

Before launching your VMs, you should should install plugin vagrant-disksize for expanding size of volume of VM. It is because the default size of box provided from Ubuntu, 10GB or so, is not enough for deploying devstack environment. It's required for expanding the volume size.

$ vagrant plugin install vagrant-disksize

Configure and Fire Up VMs

Before launching VMs with vagrant, configure machines.yml, which defines parameters of each VM you deploy. It should be placed at project root, or failed to run vagrant up. You can use template files in samples directory.

$ cp samples/machines.yml .
$ YOUR_FAVORITE_EDITOR machines.yml

You should take care about private_ips which is used in hosts for ansible-playbook as explained later.

You should confirm you have a SSH public key before you run vagrant. If your key is different from ~/.ssh/id_rsa.pub, update ssh_pub_key in machines.yml.

Run vagrant up after configurations are done. It launches VMs and create a user stack on them.

$ vagrant up

If vagrant up is completed successfully, you are ready to login to VMs as stack user with your SSH public key.

Setup Devstack

This tool provides ansible playbooks for setting up devstack. You should update entries of IP addresses in hosts as you defined private_ips in machines.yml.

There are some parameters in group_vars/all.yml such as password on devstack or optional configurations. You don't need to update it usually.

$ ansible-playbook -i hosts site.yaml

After finished ansible's tasks, you can login to launched VMs with hostname you defined in machines.yml. So, let's login to controller node and OpenStack. You will find that two examples of local.conf are prepared in $HOME/devstack for your environment.

  • local.conf.example
  • local.conf.kubernetes
$ ssh stack@192.168.56.11
$ cd devstack
$ cp local.conf.kubernetes local.conf
$ ./stack.sh

See instruction how to configure local.conf described in DevStack Quick Start.