rh1 is physically moving location soon, to prevent an outage we
intend to run a subset to tripleo jobs on rh2.
Change-Id: I6026c6a814faa089788ccdf7a0d6622283cb691d
This bring tripleo-test-cloud-rh1 inline with other cloud settings.
Change-Id: Ia85731d6c7988efa502b234d61d210e19b4845da
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This is in prep work for launching a tripleo AFS mirror. We use the
region name part of the DNS address of the server.
Change-Id: Id9765e60dc7b881c7086d242a4d0bf4885f8bb59
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
It's not possible to determine which networks are public and private at
internap. But we can configure them.
Change-Id: Ica0d271188261c96e03a6e8af9b664b1031ab945
The TripleO cloud does not work when the neutron-based floating ip
logic creates a floating ip directly on a server port. The problem is
that the floating IP is correctly created and correctly associated with
the server, but Nova has no clue that this has happened, so GET calls to
/server do not show that the server has the floating IP. As that's the
way we track success, we can't use it. However, if a floating IP is
created using the nova proxy, it all works - so just configure the cloud
with "has_network: False" so that direct neutron interactions are not
attempted.
Change-Id: Idb90cad36feb99bc5aa19da4874ce97f868681c7
Here we are removing devstack-trusty and adding ubuntu-xenial logs.
Change-Id: Ia4e2b3426442849efa02fe932d86d8ce5a1df48f
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The default of shade is not to cache server or port lists. However, we
would like to do so in nodepool - so configure that behavior.
Change-Id: Ic6a64b67a429910396dd801a4ef7577496e40fbf
We can use textwrap to break up the ridiculously long lines in the
logging configuration (with less images, it's less ridiculous than it
used to be, but it's still easier to parse). Only trick is to put
spaces between the arguments to give it somewhere to split (and better
for readability) and stop it splitting on words/hyphens.
Change-Id: I04840e98b0564dc531b74b96e8595f9d18b284af
This adds the centos7, debian-jessie and removes devstack-centos7-dib.
Change-Id: Ifcc8390b32713601fae98c96b761e313b7d2d6f3
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Due to the possibility for multiple OSIC clouds we need to distinguish
between them in our clouds.yaml. Do that now before it becomes a problem
later and refer to the current cloud as osic-cloud1.
Change-Id: I3f35db2911a44200f0486e71fc215d021aa7c227
Add vexxhost account credentials to our various clouds.yaml files. This
covers the all clouds, ansible, and nodepool clouds.yaml files. With
this in place we can work to deploying tests onto vexxhost.
Change-Id: I42101e9acc9f62897a3f63b85dd34a14adcf2394
Project names are easier for humans to deal with use the project_name
key in clouds.yaml for OSIC not the project_id key.
Change-Id: I15b6424e355c711941a43e78116ffb71f6647cb7
This adds clouds.yaml information to our three clouds.yaml files for our
two users in the OSIC cloud. This will let us manage the OSIC cloud
resources and start deploying tests to OSIC with nodepool.
Change-Id: I5a392d165fb6db2e70036008a55cd99eed237ab4
The infra-cloud-west is currently unavailable due to being relocated
causing the inventory for ansible to not be generated:
Inventory script (/etc/ansible/hosts/openstack) had an execution error: Error fetching server list on openstackci-infracloud-west:RegionOne:
This means ansible and hence puppet fail to run.
For now remove infra-cloud-west from clouds.yaml. This should be added back
in one the cloud is turned back on.
Change-Id: I16fe54c3c040c273977b0cb2e51bf7f804832380
We are installing a cert to trust the infracloud but were trying to put
it in a dir that does not exist. Put it next to the clouds.yaml in
~nodepool/.config/openstack as that will exist because nodepool consumes
clouds.yaml from there.
Change-Id: I27e1a1d340e9864308c89c660ae014d7110fbe9f
This uses the correct infra domain name, changes domain keys from id to
name, a fixes indentation for various keys.
Change-Id: Ic8a8f67bc2586ca640b8c3e500f6cdad1abf0ebd
This adds the omfracloud jenkins account credentials to nodepool.
I'm not pleased with the file resource in the node definition, but that
node definiton grew huge and needs a refactor anyways so we can do that
when we do it.
I have verified that the correct keys are in hiera.
Change-Id: Iafca5e86f72321c6aa7bef748ac2b1942539d15f
Update nodepool logging for Fedora 23 image builds. There are also a
lot of other images that have been removed in the mean time.
Depends-On: I6ff6d684e17b0581ae6fbb310af29dd1be0e54d7
Change-Id: I5ffe9098a6bcf0e565ccc5b556b943d02eae26cd
Now that the nodepool builder is running as a separate daemon it needs
its own log config file. Move the auto generated nodepool logging config
stuff over to the new builder logging config as we can manage the main
daemon's logging config by hand trivially now.
Depends-On: I013835621dfbc311a0f7bd7c957b7d4656dfa628
Change-Id: Ic1da30eab949876e5bd6c88e83979bdedc6dd50a
Manage nodepool configurations using the common-ci solution
in puppet-openstackci
Remove nodepool.yaml.erb from this repo as openstackci::nodepool
will pull it in from project-config/nodepool/nodepool.yaml
Remove the tox nodepool environment and test dependency as it
has been migrated to project-config
The nodepool logging template file and associated tool that generates the file
will remain in this repo. In the short term, updates to nodepool.yaml in
project-config repo may require a related change in this repo to update the logging
configuration. In the longer term, nodepool will be updated to automatically
log image creations without needing a customized logging configuration.
Depends-on: I89207d100eb4b6bbb502a6ed38831f49e4b29096
Depends-on: I473a1b78acdb035eb379394a7ed5f771434dc942
Depends-on: I6b01ab7260a41927fff34b9b81b631ea2c933f22
Change-Id: I2b45a7145805368b1598d3a3e8a94f0e4eb8cf2d
Switch Fedora 22 nodes to fedora-minimal builds. The changes from
Icc98fe30c34cb941aed4b987647ab67ac34af15a support this, and these are
in the 1.2.0 release [1]
[1] https://git.openstack.org/cgit/openstack/diskimage-builder/tag/?h=1.2.0
Change-Id: I63b6a30ba96f687ec6b59e0e5e1f7a0e1072f82f
We will soon be switching our f21 based jobs to f22, so adding a small number
of nodes to test an initial periodic job on, prepare_node.sh has been tested
and works on these nodes.
Change-Id: Ide20099eb181382b792112cbfb06ef20aa358f9c
Both tripleo-f20 and tripleo-precise are no longer in use, remove them
and with the extra capacity increase the number of tripleo-f21 nodes we
keep ready.
Change-Id: I3c603677a5425a8d073df4e6927ccce4d5bb2da3
Now that we are putting the sensitive jenkins and nodepool database
credentials in the new secure.conf file, let's remove the sensitive
information from nodepool.yaml.
Depends-On: Ifa4d500c52974b9fd3a0b7fd9c28cf8f52899ca9
Change-Id: Ib045c104daac15360e62f46e3e5683c7a387bc96