This patch adds AFS, and the admin keytab, to our release slave,
so that we may execute `vos release` when a mirror update
is requested.
Change-Id: I9c8531304fb74b9bafca85d58b5e9c1c0bc21f6a
This adds a hiera-loaded keytab for the wheel slaves. It may
be used when writing wheels to the AFS share directory.
Note: This will require the creation of a keytab for the
wheel mirror, as well as appropriate folders and access rights
on AFS.
Change-Id: I81c39d420d8ac70def57949ea0d4c323b8797086
This removes the SSH keys from the wheel mirror slaves, and
replaces them with the AFS share. It does not yet add afs
credentials. As we have not yet provisioned our wheel slaves,
no manual updates of the servers should be required.
Hiera keys for the previous approach should be removed.
Change-Id: Ifebf5d53d80e934674704078f7dd675f77aef5aa
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
This patch creates a new manifest for unified infra mirrors,
which will act as read-only AFS nodes that host our mirror
data. These mirrors will, once validated and provisioned, replace
the existing pypi mirrors in infra under a new, more generic,
hostname.
This patch is only intended to create the AFS read-only slave.
Apache hosting will be added in subsequent patches.
Change-Id: I9a2bf596cf47bffad5d6a5fd0da3c571fa266013
The wheel-mirror workers share a common set of hiera keys, and so
keeping them in a group together reduces significant duplication in
our hiera files.
Change-Id: I67b717943eb19404c87b2a3b571f681a0a15b7b4
This is a machine that will drive centralized mirror updates for
mirrors that are in AFS.
Change-Id: I33eed90c21a2e57a26349be83ee69e968b18d2f8
Depends-On: I56bb3ce2237be1179724f7a2bdcf9d5b04bdecd2
Depends-On: I704c8bf395d83adea0f9a0db6fd3d3814ad7660a
The openstack_project::server class declares things we want to be
true of our long-lived servers, so use it instead of
openstack_project::template (which it then indirectly uses).
Change-Id: Ie4bc41ec0b333ad9151e5df458e2762835672e6c
We want to start building wheels for as many of our dependencies as
possible in order to speed up test runs. Resurrecting parts of the old
pypi-mirror code.
We have pre-seeded this with a group of common packages, taken roughly
from the bindep output from global-requirements.
Change-Id: Ie33861dbcb413c34012820fda76f8be94fb1d151
Currently openstack-meeting-cp is not in statusbot's reach. The
other meeting channels have access to statusbot's services. This
patch adds openstack-meeting-cp to statusbot's list of channels.
Change-Id: Id4a12de1bea8fd48f3d234f54e95c23697e83c97
Remove the local database management on paste.openstack.org now that
it's back to running with a remote Trove database again.
This reverts commit b7e352cc86bb850fa1c4d6b74253e5450165afa2.
Change-Id: I7b8513b427395f610b23e3f226109ea954ee210b
Now that we've determined how to adjust Trove configuration
parameters to override extremely short default connection timeouts
imposed by our provider, switch back to using a remote database for
the loggeit installation on paste.openstack.org.
This reverts commit 8cad8d737f3a53650159ab7c00cb8e3b4649e2fb.
Change-Id: I7f172b2b4f09703f1360aff0b1fef902fc935067
The release status page no longer makes sense and is discontinued
starting with the Mitaka cycle. Temporary ensure that directories
and user/group are cleaned up.
Replace its entry in the status header by a (currently missing)
openstack-health entry.
Change-Id: I9f61c4bb1f5634df0b0da909466b4c1b1b149ba5
Openstack-zephyr channel is open for any comments
and/or discussion on the Zephyr Neutron Testing
Framework
Change-Id: I39d4e6c4fd0669e5f1dfd178ef37c80a8a58dfc3
Centos6 is being deprecated so we need to move to something newer.
This will require pbx.o.o to be rebuilt.
Change-Id: Id3fc74bf58ba5febac79674e6fd23d6ade3e4bd1
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
For launch_node and for ansible-inventory we need a functioning
clouds.yaml file. The file should really just contain the entries we
actually need, becuase we don't want to be listing all the hosts
in nodepool. However, we do want ALL of the entries available, so the
all-clouds template has them all there. Not sure where we want that file
to go though.
Change-Id: Ibee80f9a4d8f159a626e2b4c2e9639134a559ae4
