The Airship working committee is in the process of establishing a
vulnerability management process. This change adds two mailing lists,
airship-security and embargo-notice, which will provide public and
private advisories related to reported security vulnerabilities.
Change-Id: I1aa4d35cb12e4f3f45665688908af7e2cd5041a1
Signed-off-by: Drew Walters <andrew.walters@att.com>
The elections-committee and openstack-content mailing lists have
been defunct for years. They receive no new posts and their
moderators have stopped watching them. The stakeholders in the
OpenStack Foundation have given the okay to have them closed down so
only their archives remain for historical reference.
Change-Id: Ie8230265518f4b114a34849b8b1d48b6a3675700
This way we can send a single email that our users can see if subscribed
to this list instead of sending emails to all of their discuss lists.
Change-Id: I3b978a3c4e7888f14e3986628cb29a6c86bbcf61
There is a new group forming around open source design and development
activities in the area of Network Based Media Processing (NBMP). This
patch creates a mailing list for the group to start openly collaborate.
https://wiki.openstack.org/wiki/NBMP_Working_Group
Change-Id: I8a55d6f1ddec5b7eeebf8e955582edcad8fa8470
Adding a new mailing list for collaboration around
implementing the Kubernetes API in Rust. For more details on
the group, see:
https://www.cloudatomiclab.com/rustyk8s/
Change-Id: Ifb7c20725b07cb96ef69425ceb69ecff5f41da67
A group of interested developers for crosvm and Firecracker are
seeking a neutral location to host a discussion list for
collaboration around secure/special-purpose virtual machine monitors
implemented in the Rust programming language, and asked for the list
name to be rust-vmm. This request came to us via OSF staff who they
approached earlier this week.
Change-Id: I2003e3ae7a352b12d213a553f7ee0cd4f4e5d4f1
Depends-On: https://review.openstack.org/625241
Set up the initial boilerplate to enable addition of new
project-neutral Mailman mailing lists on lists.opendev.org.
Change-Id: I8cad4149bdd7b51d10f43b928cdb9362d4bde835
This list's owners have asked for it to be shut down, as they will
be using an [interop-wg] tag on the new openstack-discuss ML for
future communication. Once this merges (so that Puppet won't
recreate it), the list can be removed with the `rmlist` utility
(this will still leave the archives available but will remove it
from the list index and no longer accept subscriptions/posts).
Set the old list address as an alias for the new openstack-discuss
ML so that replies to previous messages from the list will be routed
there for the foreseeable future.
Change-Id: Ib5fd5aece2465d569e0e7c180ee14ba94882f2b7
The general openstack, openstack-dev, openstack-operators and
openstack-sigs mailing lists have been deprecated since November 19
and are slated to be removed on December 3. Merging this on that
date will ensure any further replies to messages from those lists
are rerouted to the new openstack-discuss mailing list for the
foreseeable future.
The openstack-tc list is included in this batch as it has already
been closed down with a recommendation to send further such
communications to the openstack-discuss ML.
Additionally remove the Puppet mailman resource for the
openstack-sigs ML so it won't be automatically recreated after it
gets deleted (the other lists predate our use of Puppet for this
purpose).
Clean up the corresponding -owner spam rejection aliases since these
addresses will no longer be accepting E-mail anyway.
Change-Id: I9a7fae465c3f6bdcf3ebbadb8926eb4feb8fad79
This list is basically unused, and its owners/moderators have asked
for it to be shut down. Once this merges (so that Puppet won't
recreate it), the list can be removed with the `rmlist` utility
(this will still leave the archives available but will remove it
from the list index and no longer accept subscriptions/posts).
Change-Id: Ieaf35b1e6875b26b6c20da8a9e9c2eedf200eaf8
In order to bring the operator/user/developer-focused segments of
our community together, we need a new discussion mailing list which
subsumes the topics of the current general, -dev, -operator and
-sigs mailing lists. This list will begin with configuration to
reject messages sent to it, but as we get closer to sunsetting the
original lists we'll subscribe it to them for a transitional period
and open it for discussion at that time.
I've set my E-mail address as the initial owner, but will coordinate
to find a team of list admins willing to take it on before it's
opened for posting.
Change-Id: I7dd62482229035c9b304573a3d93ef397cf43749
Now that we've got base server stuff rewritten in ansible, remove the
old puppet versions.
Depends-On: https://review.openstack.org/588326
Change-Id: I5c82fe6fd25b9ddaa77747db377ffa7e8bf23c7b
The current owner for openstack-qa is getting a lot of spame
specifically from discard notifications. Instead of this going to a
personal address, create a newer owner alias and have it go to spam.
Change-Id: I2dbccccc6418811854badf6cda04aa94243e7e51
The ambassadors-owner alias on lists.openstack.org has started to
receive a flood of spam E-mails. Reject messages to this address
with our usual response about the onslaught.
Change-Id: Ia2bb59eb29f608558ad154269c6c5510d8a7e36a
Creates mailing lists for the StarlingX project that is focused
under the edge computing focus area of the OSF.
Change-Id: I7b20fc749a8d92b44eb3e669fb6c1fecbb165aaf
The product-wg-owner alias on lists.openstack.org has started to
receive a flood of spam E-mails. Reject messages to this address
with our usual response about the onslaught.
Change-Id: I07ee094cd82f97323cd78fcca6895a2aafa9e347
The foundation-board-confidential-owner alias on lists.openstack.org
has started to receive a flood of spam E-mails. Reject messages to
this address with our usual response about the onslaught.
Change-Id: Id716761542a0b927ba011100dfa83b8a97348b22
This imports the openstack-specific branding from puppet-mailman
and stages it in the new per-site template directory. It won't
be used until puppet-mailman switches to using that directory.
Change-Id: I8f1a724022727cfa4b52327dfc2260fbd9a6336b
Depends-On: https://review.openstack.org/535848
This additional step is required for adding a new list domain.
Also, remove the "mm_domains" hostlist from the local domains
list -- it is no longer defined in the exim config file, and is
instead defined and expanded into the exim config here in puppet.
Change-Id: Ieb630cd9397414bee53ebb427e97024e0bc1ac56
This adds the lists.zuul-ci.org mailman site and two mailing lists
for zuul (along with the required mailman site list).
Change-Id: I187dd046ca69faca397abd7262568a8b0d84c5dc
At the request of the list owner who is being spammed black hole mail
sent to foundation-board-owner@lists.openstack.org.
Change-Id: I0429f42608b66fabe79e385cabaa82ba92005cae
At the request of the list owner who is being spammed black hole mail
sent to superuser-owner@lists.openstack.org.
Change-Id: I80eebc5df733e97ed97e9967e14cef2564fe916d
This switches the configuration of lists.openstack.org to use the
new multi-site support in the mailman puppet module.
Existing lists will need to be manually copied into the new location.
Story: 2001382
Task: 6091
Depends-On: Ic92726dc341af5802ad803d239bd547ef5068043
Depends-On: I090070308785d4b55bac12806a05e2896306c0a3
Depends-On: I3a31465882ec95d822d590045216ec751c7cd22e
Change-Id: I5670bb9e10eb6d8cd3d7b15ebfdf62335fb0a82f
For a few months we've been under a massive flood of spam targeting
the *-owner addresses of a number of our public mailing lists. As an
interim workaround, reject messages to the ones getting targeted
providing a custom rejection message explaining the situation.
Change-Id: I3f26963ce25875f1330a5be2447977a56a5ce84e
Migrate backups to new backup01.ord.rax.ci.openstack.org
We decided to start fresh backups on the new server, so this is ready
to go. I have performed an initial backup on each server so it has
accepted the host key of the new server and been tested (I also fixed
up review-dev.o.o, which was rebuilt but keys not updated ... todo:
add this to puppet, but since it changes so infrequently not high
priority).
Change-Id: I0872f9fcf4a334d32f632b3cb04801deefab4fd1
This new mailing list, for discussions related to the edge-computing
focus area, has been requested by Claire Massey on behalf of the
OpenStack Foundation.
Change-Id: Ifdbe5761697a75c17fb38c8a103c426b2afdd7fd
Increase Exim's smtp_accept_max on the listserv from its default 20
to allow handling more concurrent inbound delivery connections, but
also set a reasonably low per-host max to avoid any one sender
performing a denial of service.
Change-Id: I6691e8ddf8ce9911344359d65bb2f812cd85c4c9
Depends-On: I5519f6c28c81a6f40c78551ac318b91cacfc04fb
SIGs are a new construct aimed at replacing dev-centric
and ops-centric workgroups, introduced in [1]. For those
SIGs to have discussions without picking between openstack-dev
and openstack-ops (or worse, cross-posting between those),
create a new common SIG mailing-list (with one topic per SIG).
Yet another mailing-list... Trust me, I hear you... But this
avoids creating one mailing-list per SIG. We should also be
able to discontinue a number of workgroup-specific MLs, as
they migrate to become SIGs. Candidates include interop-wg,
enterprise-wg, product-wg, Openstack-security, OpenStack-HPC...
So this might be a net win !
This is the first step in this transition. Once the list is
set up, we'll prime the pump by creating a "meta" SIG (a SIG
about improving communication between ops and devs in general,
and SIGs in particular), and the meta SIG will then promote
the list and reach out to workgroups to transition them one
by one.
[1]
http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html
Change-Id: Icf6b91ac4d65b43cd1ab8c6b41a2a31aa5270066
As part of the effort of collecting all of the external SDK communities
who have OpenStack support, it became clear that we need a forum to talk
about things. Asking people who are not day-to-day developers inside of
OpenStack to join openstack-dev@ is a bit too much, since the majority
of the people in this group are actually not already working on the
OpenStack project itself. (we're talking about people working on things
like fog, jclouds, gophercloud, openstack4j, php-opencloud and the like)
Similarly, because of a wide variety of community norms in real-time
communication, an IRC channel seems like not the right choice. The goal
here isn't to make them join our dev community- but just a place where we
can be assured of being able to talk amongst each other.
Make a mailing list, which is a reasonable lowest-common-denominator and
a reasonable thing to ask arbitrary humans to add themselves to. Keeping
it specifically scoped should keep it at a traffic level that should not
cause people to shy away from joining it.
Change-Id: Id267f93cbc3e244af37de66cb76835d1852c4780
As we move configuration for zuul worker nodes out of puppet and into
DIB elements, we should keep track of what is being managed by puppet
for long-lived servers and what no longer needs to be managed for single
use workers. The openstack_project::server class wraps the
openstack_server::template class which stores configuration that is
common to both types of machines. This patch updates the backup_server
and lists class to use the openstack_project::server class, updating
class parameters where they differ between o_p:server and o_p::template.
This way we can chop down the template class and move bits into the
server class until eventually we can entirely remove the
openstack_project::single_use_slave and openstack_project::template
classes.
Change-Id: Ief997d608a3a1632ec34da34ec46a237ead761f5
On mandate from board, the DefCore Committee is changing its
name to the Interop Working Group. This change creates a new
mailing list with the updated name. Once the Interop Working
Group mailing list is created, the DefCore mailing list will
be shut down and left in place as an archive of previous
communication.
Change-Id: Iaf750d1887307c2686f20028368fd8eaa3534882
Create a separate release-announce list for all official
OpenStack releases announcement. As explained in [1] this
should allow to cut the noise generated on openstack-dev
and openstack-announce by release automation now that it is
supporting all official OpenStack projects.
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-November/106579.html
Change-Id: I97e7233a97e80ddf3d383556dd41c20b1c6ad056
Add an embargo-notice@lists.openstack.org mailing list for private
advance notification of embargoed security vulnerabilities to
downstream stakeholders. Subscribers will be manually added by the
OpenStack Vulnerability Management Team, and all posts to this list
from non-VMT members will be moderated by the VMT. This is intended
as a very low-volume ML for announcements only, and followup replies
will be directed to use comments in corresponding private bugs
instead of the embargo-notice list.
Change-Id: I9a31fd5151e45644c9fb2209b69250b108b04889
The release team would like a mailing list to use for notifications for
failures for release-related jobs that run after patches merge.
Change-Id: I8f4713025ae04af41b50ba2af94c804ea25daec6
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Some recently-ish added mailing lists copied and pasted inconsistent
first-line indentation. Make them consistent with other entries in
the file.
Change-Id: I49b900cd58380a3e672a1289a947fa47b29f6af3
