| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The parameter "NUMBER_OF_MONITOR_NODES" is needed when run
bootstrap.sh[0], but it's missing, this ps to add it.
[0]: https://github.com/openstack/kolla-ansible/blob/master/contrib/dev/vagrant/bootstrap.sh#L206
Change-Id: If83620bbdeaf8c4805e021242ca44da069e43922
|
|
When bootstrapping the vagrant dev environment run commands on the
operator node to set up the kolla-cli, and to set up the host
inventory as appropriate for either multinode or aio deployment.
Change-Id: I7765d5302329919dce6317d78b84af1c7bf572b3
|
|
Updated the vagrant dev environment to include support
for development and testing of the kolla-cli
Change-Id: I1d8f66cced7f0a9cc37e3b296c5ae10ab989f736
|
|
- Updated Ubuntu image to use 16.04.
- VirtualBox provider to use centos/7 image + vagrant-vbguest plugin.
- Improved docs so it is clear that vagrant-vbguest plugin is only
required with VirtualBox.
- Clarified comment and made it independent of the release.
- Refactored the kolla and kolla-ansible paths to be based on the
username used by Vagrant, that can change depending on the image.
Change-Id: I23d84dcc3297c43eb12eff9c443d282281fc6c82
|
|
After the repo split into kolla and kolla-ansible the Vagrant
development environment was broken.
With this change Vagrant will run from kolla-ansible and kolla
repo is expected to be in the same directory level so the
bootstrap can include it inside the VM.
- Modified the bootstrap code to copy both repos into the VM.
- Added one configuration token to specify kolla-ansible location
inside the VM.
- Updated the docs.
Change-Id: I6b56822d50472f8eda6fc60f69196d3c9b8b6cf8
Closes-Bug: 1693847
|
|
Correct relative path of kolla root directory after vagrant environment was
moved from dev/vagrant to contrib/dev/vagrant.
Closes-Bug: #1635329
Change-Id: Ib13a6123f34d69884e27029f5144ff1ad165e73e
|
|
TrivialFix
Change-Id: Ifb8f19afa1514488bd288670d08b96f84982a4e1
|
