* Update devstack-vagrant from branch 'master'
to b3acef86f3e80d3390f1a9fa90aa19c01d80ee4c
- Merge "Add IP_VERSION in template, set default as ipv4 only"
- Add IP_VERSION in template, set default as ipv4 only
For some environments (include mine), ipv6 instructions in stack.sh does not work.
Change-Id: I4b5c69f57191628664450330a08248aae05c2813
* Update devstack-vagrant from branch 'master'
to 8b300b8c440e082dd1d3bdd37b76b474d20401df
- Update vagrant box version
Devstack master(Victoria) has dropped xenial distro, switch base box
version to bionic.
Bionic has puppet5 as default puppet version, which has faster puppet
class running in parallel, so devstack and grenade repos were being
checked out while /home/stack dir were still being created, impose puppet
class ordering.
Change-Id: I89af65ca8c53aa41407ed7e4ca0edef88daae3b9
* Update devstack-vagrant from branch 'master'
- Change to use --remote-ip with security group rules
--src-ip was deprecated in 2016, change to use --remote-ip.
Related to https://review.opendev.org/#/c/613644/
Change-Id: I6b9f17c94bdf9de070d5f2e32e97dff600a3545a
- OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.htmlhttp://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
- Update APT before installing puppet
Installing puppet would fail in with some base boxes. A simple 'apt-get
update' will fix that situation.
Change-Id: I53bc8fc72700a165471a19882d64506d7180dfc0
Project: openstack-dev/devstack-vagrant b4365bed49ba6de89211d08d6ba5fc2631ab2b01
update default box to ubuntu/xenial64; add puppet
since Change-Id: I6617283afd798af37e64913b7865cea3c8a62aba the devstack installer
no longer supports trusty and xenial does not have puppet installed by
default
Related-Bug: 1599531
Change-Id: Ic59a768983430149e3f3a4de65606d649bb17693
Project: openstack-dev/devstack-vagrant 20b2965fd9772c951630e2a11c13974a9a40da74
make vagrant user configurable from config.yaml
RELATED_BUG: 1569237
RELATED_BUG: 1589721
Change-Id: I57b5c9ea124b071c6d31b8c825c9cb1d2e89a8ce
Project: openstack-dev/devstack-vagrant c109cd09a9f60af36a53b2746935a18d1a0abd9a
Replace obsolete vanity openstack.org URLs
Project specific URLs are obsolete, use docs.openstack.org - and use
https for that site.
Change-Id: I7e65282448974f1c72a0ac8eca3b97a29432ac28
Project: openstack-dev/devstack-vagrant e7b036709ef353c3038e06889a11f55c2cefe3d1
Add manager_extra_services to config.yaml and local.erb
Specify the additional services to enable on the manager node
Change-Id: I3154f0ca7ab4489a2510fe4f302f8a9fbfb87bd1
Project: openstack-dev/devstack-vagrant cbedf6bcf494c7fb9f724e7bf05745ada94f7a8a
Add use_ip_resolver to config.yaml
In order to use vagrant-hostmanager's ip_resolver even when
use_bridge is not false.
Change-Id: I7f09e26318d177fca4cdca6577b927f923dd7a1b
Project: openstack-dev/devstack-vagrant ad67271514d2a0a9fd8c90865d110d90ffae3fec
Work around invalid public key issue
I've faced with inability of keystone to recognize a public key
inside of `~stack/.ssh/autorized_keys` file. This happened because
of puppet writing three-line comment stating it was generated
automatically. With this fix it works fine.
Changes, I've done:
- Move public key path into separate variable
- Write public key into tmp file and pass it to `nova keypair-add`
Change-Id: I827b7e1695f61ef2742137195866cb2deb4a390f
Project: openstack-dev/devstack-vagrant e15d17e0ed1bcf72752cc07a76cfd5f1edabcb8c
Use git.openstack.org everywhere
Our official git master is at git.openstack.org, update places
that use github instead.
Change-Id: I21deb1246c4d83c6c8baaeb4dc45d78f2157460a
Project: openstack-dev/devstack-vagrant 262398f2c601e044f55abd7f91f1f5de452500f1
Advise about vagrant-cachier in the README
Change-Id: Id3857481cac17540e02420849f0b5fc83339a2ab
Project: openstack-dev/devstack-vagrant 8485e2c0bdef9d0f4bc43748a1e239ea600ef666
Remove Cirros URL from IMAGE_URLS
Devstack introduced DOWNLOAD_DEFAULT_IMAGES setting which
by default is True and extends IMAGE_URLS variable with
some default images, including Cirros. devstack-vagrant
also extends IMAGE_URLS with Cirros URL. This results in
error about duplicate entries in this variable.
Change-Id: I86f1ca5b9bef73e41657ce6fec17dd378d9e33ef
Closes-Bug: #1497533
Project: openstack-dev/devstack-vagrant 2fb1e4e8ea30ba982fc82dcd5d33fefb169afa5f
update cirros version
- update cirros to recent 0.3.4 as same version as devstack
- README: explain extra_images puppet config
Change-Id: Idc275d19a6e54212500b860bf4a0e476b60d4c69
Signed-off-by: Hiroshi Miura <miurahr@nttdata.co.jp>
Project: openstack-dev/devstack-vagrant f748559f8f554b8f80c9f74486bc8a2008e5411b
Fix hostmanger ip resolver exception when guest is not really up
The bug is discussed here:
https://github.com/smdahlen/vagrant-hostmanager/issues/121
so use the suggested workaround in ip resolver to catch the error.
Change-Id: Ibac510ca9aef57b508036266987b136d95771074
Project: openstack-dev/devstack-vagrant eab558e288f016aff79674afc5fbb8a0e42f6e9b
read ip from eth1 if using host-only network
If the the vms are using host-only network, then eth1 would be the
proper interface to retrieve ip of the vm. Without these lines, the
host manager will only add 127.0.0.1 to /etc/hosts file.
Change-Id: If2f825ebb9d6f7f096ce55e1bf070e5af91f5d45
Zuul