By default the ubuntu-minimal element also include restricted. Because
we don't use restricted in our AFS mirrors we can drop this at
diskimage build time.
Change-Id: I64248182bab7ec46bbdfcb01b097133a6aa28a5b
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We currently re-run all the grub setup in 99-fix-grub-timeout which
shouldn't really be necessary (actually a little problematic; although
this is dib's fault, see Ibaaa81124098f3c6febe48e455d3e1cd0a5f1761)
Use the new timeout flag to set this in the bootloader element
directly.
I think it is also an advantage that if you build a testing image with
./tools/build_image.sh this is configurable now ... having to fiddle
the bootloader for debugging is something that happens more than you'd
like.
This is supported since dib 1.26.0
Change-Id: Iafc660a9a8c072af6bf1fd5e51c419abccef4d54
This reverts commit a86849cede41b101ab1fec4b5ef59eccd9568699.
Yes this is getting silly :) But the latest dib release (1.25.2)
includes the dracut fix I5d203f2abe743cb23a44d449850e692a948e7871
which has been tested and gets this booting again.
Change-Id: Ic83d44d5bf14657cf204cf51297d7db06b28a5f8
We have a new release of diskimage-builder to fix this. Turned out to
be an issue with dracut.
This reverts commit 8fa2c4ddb6209d0cf6f80d3dfd3dde1e8baddc17.
Change-Id: Ib98c9b04d19a29c95be47d45b3ed1a99ca7754a1
Depends-On: Iaf2a1e8470f642bfaaaad3f9b7f26cfc8cc445c9
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Our current build of centos-7 is broken, currently still trying to
understand the failure. Pause diskimage builds so we can roll back to
a working version.
Change-Id: I5369c39b40a4700663587039b9f06d126d1c0977
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
After talking with clarkb, we decided it might be time to also stop
caching packages for devstack. Like the cache-bindep patch before, we
have a robust mirror infra in place right now, and believe we are
ready to start using it more.
Change-Id: I249f21a98fea3b963b7ffb8e3d0fce02cc540d46
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Now that our migration to ubuntu-xenial for jobs is finished, we can
now reduce ubuntu-trusty to 1. I know this is a little agressive, but
since our time to ready for nodes is 30seconds on most clouds, its
something I wouldn't mind test driving to see how nodepool reacts to
the demand.
Change-Id: I3d0cdbba06a265729670ada6c541b46838f448a5
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Looks like this was skipped in:
Iaaa83a8b3352ea25384f5e8926d152069b7e6bc7
Change-Id: Ifb9743178e65f33f0c215dbb6244398a9aebba5b
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We've been uploading images to ovh-bhs1 for a while now, and things
looks to be working correctly. Bring the region back online so we can
use it.
Change-Id: I9c52cc56536031289b79ebf17181f082ead10a1a
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
It looks like the upload issue we are having with OVH are not related
to image type. So, switch back to qcow2 to save some bandwidth.
Change-Id: I58df7622b2f3dfd98786db111d68df9df2bf22f7
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Today each mirror region has an AFS mirror cache of packaging, as a
result lets try having jobs use it over caching bindep.txt
dependencies on our images.
This should save us about 27mins in diskimage build times for
ubuntu-trusty and ubuntu-xenial.
Change-Id: I74ad0fdbd939948d9285dcd7ef839bdbe299319f
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Adding a three node label to nodepool as we need a three node
setup to test DVR+HA with tempest.
Existing Devstack gate will set agent_mode to 'dvr' in both compute
nodes. So it is still a DVR only multinode setup with 3 nodes.
Change[1] in devstack gate submitted to change one compute node's
agent_mode to dvr_snat, to make it DVR+HA.
[1] https://review.openstack.org/#/c/383827/
Change-Id: I370643277a3b23e7f47e413cf880daa9af1eb831
This is needed as part of our zuulv3 effort. Specifically, nb01.o.o
will use them. This will be a noop for zuulv2.
Change-Id: Iabd54fedc8c12bcd3a0fd76b9fc48a93c941bad5
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
node-devstack element is not referenced anymore.
It was planned to remove this element when prepare-node was moved
out of node-devstack
See: https://review.openstack.org/#/c/319030/
Change-Id: Ife1c6849d0d1430215e7dc5e1f8a774b3af8d113
Adding the ability to selectively cache only some git repos in
nodepool slave.
This is useful in some environments where it is needless to cache
all the git repos that appear in gerrit.
For example, in a 3rd party CI environment, each nodepool slave
needs only few openstack projects in order to check commits to
a specific project. So it is needless to cache > 1500 projects
currently in gerrit
Change-Id: Ie7302594b24d2bdcc157d3cf64b1f219e7ef0205
Use the openssh-server element to install the SSH server.
Depends-On: Ide15ee04f5de123dbc8ce4bb56d638d8a167c341
Change-Id: Ie8d81f488f8421d4b2ed227c6f7c6779cca96a9d
os-client-config and shade have contained this as default values for
rackspace for quite some time. There is no need for us to set them
directly on every image in nodepool.yaml.
Change-Id: I134831daa7880778a1f4b9a2acbaed14a0a1d06a
According to Kevin (cloudnull) in IRC, osic-cloud8 has been
decommisioned. Currently uploads to it fail with 500 errors, so it is
not getting new images. Remove from nodepool.
Change-Id: Idf87ca142ae549204fa281da1c94727f1b2e4a6d
Image uploads are a thing we struggle with getting done reliably. Reduce
the overhead by removing the BCN keynote demo clouds as we are not using
them in production currently. Hopefully we can readd these clouds in the
future but for now simplify nodepool and remove them.
Change-Id: I0e099bdf9b4e95efd9837b3acb99292239c1a281
This seems to have been here since the beginning of time (with time
being the project-config split).
However, since then, Openstack_project::Slave_common as acquired the
ability to install this same environment
(I290a695c697fb456bee6f8212ba50b6c1b4533fc).
The difference was that this file installed zuul from git, while
puppet was installing from pip. However, that changed in
If07b31f3a735cf7bcf6bfb8591ed37577f5ae201 and puppet is now installing
zuul from git. Thus since this now duplicates what's happening in
puppet, I do not believe want or need this.
This element is now breaking the Fedora 24 build when it tries to
overwrite the existing virtualenv already created by puppet.
python::virtualenv creates the virtualenv with a "-p python" argument,
while the second call doesn't, which creates issues with the symlink
layout (see [1] for details).
[1] https://github.com/pypa/virtualenv/issues/976
Change-Id: I7963630c699eaa4984adc6a155bea8f74280cd80
We incorrectly setup our mirrors for UCA. Now we support 3 openstack
releases.
Change-Id: Ie3a05398d9fdc7a7f7c0c74366a7c4dd70200a2b
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
No need to override /etc/resolv.conf if "NODEPOOL_STATIC_NAMESERVER_V4"
enviroment variable is not set.
Change-Id: Idf74d394f5a025b885b830d3afdcbad12655101a
This review cleanup scripts that were exclusively used by
snapshot scripts for nodepool which were removed in:
https://review.openstack.org/#/c/331494/
Change-Id: I37900a5d698a43bc0d510100289a5a7ec527021d
For complex deployments (eg: High Availability, Network Isolation, etc),
2 nodes are not enough for TripleO as we deploy overcloud on a single
node. We would like to extend our testing to test more realistic
deployments with one more node for the overcloud.
This patch does 2 things:
- Create centos-7-3-node in nodepool, that will run 2 subnodes.
- Implement experimental (non-voting) TripleO centos-7-3nodes-multinode
Change-Id: Ie204431d9a50dd8247d6393e916c5033ba0499d3
These quota changes were only for demo purposes, so put
configuration back to our pre-demo state for now. A subsequent
change will add proper quotas for some of these providers again in
the near future.
This reverts commit ed35b7f0b00ea46c5086977d0981eeda3352634e.
Change-Id: I4db1dbab5e1a65cff3108413e259a1bfce4beff0
