ENV["no_proxy"] is nil if the environment variable is empty, but expected as empty string "" wrongly. This update is to fix the mistake. Closes-Bug: #1991327 Signed-off-by: Yasufumi Ogawa <email@example.com> Change-Id: I84c4631eed2eb56448077eb51ff4b2341f08ac2b
|4 months ago|
|group_vars||7 months ago|
|helper||11 months ago|
|lib||7 months ago|
|roles||11 months ago|
|samples||7 months ago|
|.gitignore||11 months ago|
|README.md||7 months ago|
|Vagrantfile||4 months ago|
|ansible.cfg||11 months ago|
|hosts||7 months ago|
|site.yaml||11 months ago|
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
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
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
vagrant up. You can use template files in
$ cp samples/machines.yml . $ YOUR_FAVORITE_EDITOR machines.yml
You should take care about
private_ips which is used in
ansible-playbook as explained later.
You should confirm you have a SSH public key before you run vagrant. If your key
is different from
vagrant up after configurations are done. It launches VMs and create a
stack on them.
$ vagrant up
vagrant up is completed successfully, you are ready to login to VMs as
stack user with your SSH public key.
This tool provides ansible playbooks for setting up devstack. You should update
entries of IP addresses in
hosts as you defined
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
So, let's login to controller node and OpenStack. You will find that two
local.conf are prepared in
$HOME/devstack for your environment.
$ ssh firstname.lastname@example.org $ cd devstack $ cp local.conf.kubernetes local.conf $ ./stack.sh
See instruction how to configure
local.conf described in
DevStack Quick Start.