This manages the clouds.yaml files in ansible so that we can get them
updated automatically on bridge.openstack.org (which does not puppet).
Co-Authored-By: James E. Blair <jeblair@redhat.com>
Depends-On: https://review.openstack.org/598378
Change-Id: I2071f2593f57024bc985e18eaf1ffbf6f3d38140
This is just a zookeeper server now, so doesn't need all these
passwords, a cloud.yaml file or a launcher-esque deployment.
Change-Id: I3cb20d9c8af150ecdc1fb0a16208a774e3fb530f
Generating a openstack-infra specific version of this file was
deprecated with change I6fdc3b622454b069f3ad2cf42da584d8df23a110 when
build logs was moved out of Python logging.
This means (post the depends-on) the file is exactly as kept in
puppet-nodepool. Remove the system-config template and just use that.
Depends-On: https://review.openstack.org/586231
Change-Id: I2db37868be12c146678f1c8934db80050c788540
To avoid the cost of converting nodepool image from qcow2 to raw on
compute nodes, just upload raw images (not qcow2).
Change-Id: I325af734f843fc618a40ca992a0086ffb1c21cfd
Depends-On: https://review.openstack.org/585838
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
There is a bug in sdk that is being fixed that causes auth discovery to
work improperly. Setting auth_type to password works around it.
Change-Id: Id8e8fe82827987660c4dc64bd9cf3d65ffd20cf4
Nodepool is switching away from using shade to using openstacksdk.
The adds the logging for openstacksdk, but does not yet remove
shade in case we need to revert nodepool. The next review should
remove shade logging entirely.
Change-Id: I7e6820c2f8ea044cc97c322ae9b91fe0bee559db
This reverts commit 6baef98ed6.
Letting nodes without working IPv6 but with IPv6 global routes into
the pool does nothing but cause jobs which attempt to run on them to
fail.
Change-Id: I8921936dd5fdcb4565669f34ea49006ced40e996
Ipv6 is currently having routing issues to vexxhost IPs. Force ipv4
temporarily until this is corrected.
Change-Id: Ib935e10edd8285f7f42f7091fb47f6d872dbc57a
Every "openstack" cli operation gives
Ignoring domain related config project_domain_name because identity API version is 2.0
Ignoring domain related config user_domain_name because identity API version is 2.0
I feel like this should be auto-detected to v3 but not sure how. Add
the identity_api_version as done in the other clouds.
(I proposed making that message clearer in
https://review.openstack.org/577324)
Change-Id: I22f8d342968c9084d05d841d6e3ab660a62c3262
It's actually "default_interface", not just "default". I must have
tested with it correct, then copied it in wrong to system-config :/
Change-Id: I38a76c2d162a9ef35ebaa87080d6986af1a3daa2
For ... reasons ... it seems we can't detect the default network on
packethost. Override it in clouds.yaml, while we possibly figure out
what is going wrong.
Change-Id: I88ccdca80477fa06d33e5785d764a546e88a76a5
Packet Host and Platform 9 have generously agreed to donate some
compute resources to our testing efforts. Add Nodepool and
Puppetmaster credentials for them.
Change-Id: I705c4204abca060c35a1a417791a67229b78cd02
Infracloud is sadly deceased. The upside is we can delete a lot of code
we don't need anymore. This patch removes infracloud nodes from
site.pp so that the puppet-apply test no longer bothers to validate
them, removes the infracloud modules from modules.env so that we don't
bother to install those modules in puppet-apply and puppet functional
tests, and removes the infracloud-specific data from the public hiera.
Additionally stop the puppetmaster from trying to run the infracloud
ansible playbook and finally remove the chocolate region from nodepool's
clouds.yaml (vanilla was already done).
This patch leaves the run_infracloud.sh script and the
infracloud-specific ansible playbooks as well as the infracloud
manifests in the openstack_project puppet module. It's possible those
tools could come in handy in the future if we ever have another
infracloud, and leaving those tools in place doesn't add confusion about
which hosts are actually active nor does it leave cruft that gets
unnecessarily tested.
Change-Id: Ic760cc55f8e17fa7f39f2dd0433f5560aa8e2d65
Because of ipv6 support in limestone-region one, we don't actually
need to ask for FIPs. Stop doing this so we can bring more servers
online.
Change-Id: I48fe176c4a78683834246f59850276133c26e19f
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Copy/pasta from puppetmaster.o.o meant that we tried to put and use
the certificate in /etc/openstack/ which is not a thing on nodepool
nodes.
Fix that to be the right location and update the nodepool clouds.yaml.
Change-Id: Ib9c17a58fc2aa9ad5eb9091a6a3fd23ff5825731
This makes the credentials available so nodepool launcher and builder
can use them.
The limestone credentials have been added to hiera for the nodepool
group.
Change-Id: Idb56db19110e6b30f6231869ff278b90caf99f4b
A request from mnaser to use raw images for the provider. There is
also a proposed change to os-client-config to add this, but will need
to be tagged as a new release.
See: https://review.openstack.org/554351
We can revert once os-client-config has been released to pypi.
Change-Id: Ifc3d5656b7b972d5978b4d806c41bf2cc3443842
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Change Ia7415d2fbbb320f8eddc4e46c3a055414df5f997 removed per-image
logging from nodepool; it now keeps a series of named log files. The
"image" logger is removed, along with all the specific build logs.
I972a66f9c153f52df934d25ab2f77596bb2e5429 removed the
image_log_document_root argument; which wasn't doing anything in
nodepool::builder, but was actually being used to fill-out the
builder-logging.conf file. Thus we need this to not have a bad path
in the config file.
Change-Id: I6fdc3b622454b069f3ad2cf42da584d8df23a110
We longer have any jobs or need to manage VMs in
tripleo-test-cloud-rh(1|2). This hardware still eventually be removed
so lets also remove it from our configuration.
Change-Id: I588ae945df15beceaf7a60bf6a65b1615b2074f0
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We no longer have infracloud or tripleo-test-cloud-rh1 online, we can
remove them from nodepool-builder logging.
Change-Id: Ie71b5bd1ee56417846b2a62c40dbd2fd4fa8221e
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Update our nodepool_log_config.py script and remove support for
snapshots.
Generate latest version of nodepool-builder logging.
Change-Id: Ib87e8c352b56f63ca44668f43fa440645fab9f37
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The controller for infracloud-vanilla is no longer working, remove
access to it from our services.
Change-Id: Ic2a44f74493d3f328398b67262ae93253714bf67
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
It seems api_timeout has moved out of nodepool into clouds.yaml. So
add the settings here.
Change-Id: I01613df6d64e7af635018ad3837a50487ecd5950
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Remove Fedora 25 from the mirror script and add Fedora 27. Update the
nodepool builder logging conf file, as the builds were removed
in I1fae6458402d6afe97069c3a17bbbf563afff20b.
Change-Id: Ib8d1b4bb3069cf48d1abc7c6fccd56d16bf54739
OVH instances are getting ipv6 addresses now. This is great except that
the only info on these addresses seems to be in the nova/neutron api and
not via ipv6 router advertisements or config drive metadata. Until we
sort out a programmatic way to configure ipv6 on the instances at boot
lets not attempt to use ipv6 when connecting to OVH instances.
Change-Id: I48e773b9f29fae9a15f6c95fc64831ab0749cc60
We don't support v6 for centos in glean, and we need glean for
networking in rackspace. Turn off v6 until we support it.
Change-Id: I0b1f6bd0a699f85e84a4414bc72c3aaaf1672555
We currently are not using these in production, remove them to help
clean up our clouds.yaml files.
Change-Id: I81b4de2fda50b61a17e99c30cfe4ec44c55df343
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Clean up our clouds.yaml files and remove any clouds we are not using
in production.
Change-Id: Ib13f394126d44187d170ebfd976c34087305c835
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This removes remaining references to internap (renamed to inap).
It also updates some items (cacti/nodepool logging) that were missed
in the rename.
Change-Id: Ibafd416e9e55aa458a50eb71922065a35e3d99f4
We don't actually use this region any more, remove it so we don't
attempt to access it with dynamic inventory with ansible.
Change-Id: Ic6d4474a61ee32d198f4d70800fd79b8bd80623f
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Regenerate file with current data.
This adds:
dib_fedora-26
This removes:
osic-cloud1-s3500_upload
osic-cloud1-s3700_upload
Change-Id: I3d87c67c0a8d1399c3595858497028a5af25c2b9
openSUSE 42.3 is currently in feature freeze so it will become
the default stable release. Prepare infrastructure to handle
42.3 nodepool image builds.
Change-Id: I50cf826c13e40dd191ad62298d94dbf32a11e518
Pull in opensuse DIBs and citycloud provider.
Change-Id: Ic9148d0333a8f991d9d5ee1dc10999bd99a61b83
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Sadly the domain name osic.org has gone away, this change adjusts the
domain name to "cloud1.osic.xyz".
Change-Id: If697dfc9ba005ab8ea0eb54eff5dee21ca27158a
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
Bluebox keystone v3 api isn't properly discoverable which causes
problems when attempting to perform actions like creating new projects.
Address this by explicitly setting the endpoint location using a config
override.
Change-Id: I57c6a6733ee520fb074c72f0a3e15f7c45468730
The way we got quotas assigned we need to flip the projects assigned to
users around so that the zuul user gets to run 50 instances per region
and the ci user has just enough to boot the region local mirrors.
Change-Id: I053cf630e513fbb795f8039672a8073a354bf9b6
This updates our citycloud clouds.yaml info to non demo accounts. Step
zero into taking citycloud to production.
Change-Id: Id7b1c739fffc7973c27eca6c5066dc3143611cb8
There aren't that many cloud interactions that the builders do - but
tracking the interactions would be nice in terms of tracing issues that
arise.
Change-Id: I6a0e8afb3c1334195d7b74b55d727e5d05975b3f