Upstream stack.sh again changed its output slightly, so autostack.sh
needs a corresponding change so that it knows when stack.sh completes.
Change-Id: If10c17392af98e4ac6c814df145fe2d2e9f6bc6c
The output of stack.sh changed slightly in the past three months,
necessitating a slight change to the part of the ds-build script
that waits for stack.sh to complete.
Change-Id: Idc35b3ab921f423d8f4ba0c6a8a048cc6f3303eb
I don't know about anyone else, but whenever I kick off the
ds-build role on a fresh VM, I see a high rate of failure with
git clone operations ("git call failed" is the error), which kills
off stack.sh and results in a failed build. This happens about 50%
of the time for me, so I modified the devstack build script to
automatically retry if it encounters this error.
Change-Id: If91577707ed76b1ec566af9189e30bbdcd81c37d
- Increase memory of devstack server from 5GB to 7GB
- Update autostack script to reflect upstream changes
(remove ceilometer hack)
- Disable Neutron, which was preventing VM from provisioning images
- Remove Glance from local.conf; it's already installed by default
- Added instance pre-creation steps to documentation
Change-Id: Ia3259cf440e5f16b194d8339a176f2d919b23bc4
Add two changes from the main Vagrantfile also to the Vagrantfiles
in ds-build and split.
* Id3aeaa16e062f764412bd6c5fd9460b5867333a9 (vagrant-cachier)
* Ie615cf81be40b8395d8e7672e59407cc4925b410 (vagrant-berkshelf)
Change-Id: I2309db433c547736732217ffcd1e1f440d1684ab
David Schroeder