Fedora-28 is the next version of fedora, start mirroring it.
Change-Id: Id53f66d1efc9356436fe63ef82125384e8d96242
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We no longer support fedora-26, so we can stop mirroring it.
Change-Id: I5a954e2a4c00c67e1a6c8db7e8d2626d0e8f3986
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We no longer support debian-jessie nodes, we can stop mirroring it
into AFS.
Once this lands, I'll manually remove jessie from reprepro.
Change-Id: I4cb3e5521d3e4042f56c023df40d6ccba25215af
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
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
There are some assumptions made about the puppet config paths that
aren't applicable for puppet 4. Configuration, including modules,
belongs under /etc/puppetlabs. It's also no longer necessary to fix up
the templatedir or server configs in puppet.conf.
Change-Id: I3b544b6ce4a96a7a2478522a78402f77ff86a5a5
As we're trying to add a gate for Debian in puppet-openstack,
we also need puppetlabs repository for Stretch to be mirrored.
Change-Id: I8f7156f00db97deae6ad3500a5108d6ddb7420b1
In order to provide useful URLs in E-mail notifications, set the
default_url for the openstack_project::storyboard class.
Change-Id: I70cc33e73b3cff6855270d46e1dd40940221b0d1
Depends-On: https://review.openstack.org/555237
Currently this is broken on mirror-update.o.o, the reason seems to be
upstream security.debian.org is a separate pool, but we are trying to
add it into a single pool.
This is causing checksum issues on files we download.
For now, remove debian-security and update jobs to pull directly from
security.debian.org. A follow up patch will move this into its own
pool for reprepro creating mirror.debian-security.
Change-Id: Id918597aecc5114791811c7f30b6109da6a8d0af
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
These packages are huge, almost 1GB per day are being produced. Stop
mirroring them to control the growth of our pypi mirrors.
Change-Id: Ia2a5d4c75f50e20de59a54e9acf61bfdb38bc4a6
Depends-On: https://review.openstack.org/561692
Our previous patch didn't work as expected, this is because the repo
data for security is not in the toplevel directory. This was the
reason for using suite.
This then means we need 2 stanza's for jessie and stretch, since the
suite field only supports a single entry.
Change-Id: I29944191beff261c79f819e434da35e2848877cb
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This will enable use to use new bandersnatch features like package
blacklists.
Depends-On: https://review.openstack.org/561691
Change-Id: Ibd3109aaab927109ccca93e523a16b126b4edde8
With $DIB_DISTRIBUTION_MIRROR being set, it expects an update
channel for tumbleweed distribution as well. Given that there
is an emergency update channel (that is usually empty), we
can use that one to resolve issues with the nodepool image
building.
Change-Id: I5f786d16f26bfb836d37a740f8490d81076cdfbb
Since we re-enabled the websockets port in change
Id9bb77ef9a2ac70eec74db4ea64423b5d6351a06 things having quite stable.
Connections to mosquitto over websockets hasn't crashed. Since things
have been stable this commit unblocks the tls websockets port for
firehose.o.o and switches it to the standard 443 for https instead of
the default 8080 we were using before. This should enable websites
trying to use the firehose over websockets from https server.
Change-Id: I1b08eabf22f5345a9b4ebfae5d3dab08270efbf9
Configure the its-storyboard Gerrit plugin to leave comments with
hyperlinks on stories mentioned in a change's commit message footer
whenever that change gets a new patchset, or is abandoned or merged.
This now must be explicitly configured for the version of the plugin
used with newer Gerrit (circa 2.13).
Change-Id: I14dea61a906c4b267145dce6911a10d8075b4ba9
Stop filtering on jessie, we also need stretch security updates.
Change-Id: Ib425881877d02f7c30f4dcaf88952540b3aba886
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Etherpad releases 1.6.4 and 1.6.5 include some security updates as
well as a number of bug fixes over the random post-1.5.0 commit
we've pinned to for a while. Since it appears upstream is now
tagging releases with some regularity we can try pinning to specific
tags again.
Note that the vulnerabilities fixed in 1.6.4+ are either too new or
otherwise non-impacting for the version, configuration and use case
under which we're deploying in production, but this update is good
hygiene anyway.
Change-Id: Idc0e0c3a6d298aad2e41772e249c1a167c88559a
In order to upgrade to current versions of the Etherpad service, we
need newer nodejs than is available on Ubuntu Trusty. Switch to 6.x
which is the current default for the puppet-etherpad_lite module and
is also what we've tested on etherpad-dev.openstack.org. Switching
between Ubuntu and Nodesource package sources does not result in an
immediate package upgrade, so this must be performed manually before
we change the eplite_version parameter to something newer.
Change-Id: Ied9e5bd7ffa16f1832d3e1e26d0886de67f98f72
Enable logs and add statusbot for oooq channel in IRC which is
used for tripleo-quickstart discussions.
Change-Id: I8409ae810982bb1199a8ee6d2b6097e0293657cb
Latest versions of Etherpad no longer start under nodejs 0.10 and
need a minimum of 6.x, so start installing and using the newer
non-system-packaged version.
Change-Id: I2d7804cd5e53603e40fc7d821effb74cc334e78e
In discussions at the last PTG[1] and in subsequent First Contact
SIG meetings[2] we've decided that the #openstack-101 channel
should be removed and rolled into the #openstack-dev channel.
Why? Good qustion:
- No one is good at sitting in and watching the #openstack-101
channel outside of OUI training periods.
- It would be better for new contributors to ask questions in
a channel that people with the answers already activly monitor.
- 101 is an American-ism, that not everyone in the world would
understand.
This means that during OUI trainings there will be more noise in
openstack-dev. However, trainings mostly happen the weekend
before a summit, so at a very quiet time. And would mean trainees
would already have practice and now where to come for questions.
There is another patch[3] which will remove openstack-101 from
the accessbot.
Finally, as per renaming instructions[4], once these patches
land, a redirect will need to be created, the topic updated and
current residents of the channel will need to be informed to
relocate.
[1] https://etherpad.openstack.org/p/FC_SIG_Rocky_PTG
[2] https://wiki.openstack.org/wiki/First_Contact_SIG#Meeting_Agenda
[3] https://review.openstack.org/559250
[4] https://docs.openstack.org/infra/system-config/irc.html#renaming-an-irc-channel
Change-Id: I24710f24e7e640aabbf22353c25c24d2a8af9287
The dns.py file uses openstack.connect to make the Connection but
launch_node.py was still using shade.OpenStackCloud, so when the
connection was passed to dns.py it was trying to use an SDK property but
getting a Shade object.
This is because while sdk has been updated with all of the shade objects,
we haven't updated shade yet to provide the sdk version of the object, so
shade objects from sdk have things shade objects from shade don't yet have.
Update launch_node.py to use the same Connection construction that
dns.py does.
Change-Id: I1c6bfe54f94effe0e592280ba179f61a6d983e7a
If two reprepro mirrors share the same volume (as in mariadb) they end
up possibly using the same $UNREF_FILE, which gets things mighty
confused.
Add the config filename as a key into the unreferenced file list to
differentiate.
Change-Id: I9f0df9bcf651438fee600091f631543260e40a01
To prevent all these jobs firing simultaneously, offset their minute
to start randomly between 0 - 45 minutes past the hour.
Change-Id: Ib9edbe4f144222ab038147f36ac6b5341d1401e0
