- openstack-discuss - lists.openstack.org

[API SIG] holiday office hours
by Michael McCune 19 Dec '19

19 Dec '19

the API SIG will be closing it's office hours until the new year. have a peaceful and joyous holiday season and new years =) peace o/

1 0

[blazar] IRC meetings cancelled during the holidays
by Pierre Riteau 19 Dec '19

19 Dec '19

Hello, The Blazar IRC meetings of December 24, December 31, and January 2 are cancelled. The next meeting will be on Tuesday, January 7. Have a great holiday, Pierre

1 0

[manila] no weekly meeting 26 December 2019
by Tom Barron 19 Dec '19

19 Dec '19

Just noting that there will be no weekly Manila meeting 26 December. We'll next meet at the scheduled time, 1500 UTC, on freenode #openstack-meeting-alt, on 2 January 2020. [1] See you in the New Year, or in #openstack-manila in the mean time! -- Tom Barron [1] https://wiki.openstack.org/wiki/Manila/Meetings

1 0

CfP VHPC20: HPC Containers-Kubernetes
by VHPC 20 19 Dec '19

19 Dec '19

==================================================================== CALL FOR PAPERSa 15th Workshop on Virtualization in High-Performance Cloud Computing (VHPC 20) held in conjunction with the International Supercomputing Conference - High Performance, June 21-25, 2020, Frankfurt, Germany. (Springer LNCS Proceedings) ==================================================================== Date: June 25, 2020 Workshop URL: vhpc[dot]org Abstract registration Deadline: Jan 31st, 2020 Paper Submission Deadline: Apr 05th, 2020 Springer LNCS Call for Papers Containers and virtualization technologies constitute key enabling factors for flexible resource management in modern data centers, and particularly in cloud environments. Cloud providers need to manage complex infrastructures in a seamless fashion to support the highly dynamic and heterogeneous workloads and hosted applications customers deploy. Similarly, HPC environments have been increasingly adopting techniques that enable flexible management of vast computing and networking resources, close to marginal provisioning cost, which is unprecedented in the history of scientific and commercial computing. Most recently, Function as a Service (Faas) and Serverless computing, utilizing lightweight VMs-containers widens the spectrum of applications that can be deployed in a cloud environment, especially in an HPC context. Here, HPC-provided services can be become accessible to distributed workloads outside of large cluster environments. Various virtualization-containerization technologies contribute to the overall picture in different ways: machine virtualization, with its capability to enable consolidation of multiple underutilized servers with heterogeneous software and operating systems (OSes), and its capability to live-migrate a fully operating virtual machine (VM) with a very short downtime, enables novel and dynamic ways to manage physical servers; OS-level virtualization (i.e., containerization), with its capability to isolate multiple user-space environments and to allow for their coexistence within the same OS kernel, promises to provide many of the advantages of machine virtualization with high levels of responsiveness and performance; lastly, unikernels provide for many virtualization benefits with a minimized OS/library surface. I/O Virtualization in turn allows physical network interfaces to take traffic from multiple VMs or containers; network virtualization, with its capability to create logical network overlays that are independent of the underlying physical topology is furthermore enabling virtualization of HPC infrastructures. Publication Accepted papers will be published in a Springer LNCS proceedings volume. Topics of Interest The VHPC program committee solicits original, high-quality submissions related to virtualization across the entire software stack with a special focus on the intersection of HPC, containers-virtualization and the cloud. Major Topics: - HPC workload orchestration (Kubernetes) - Kubernetes HPC batch - HPC Container Environments Landscape - HW Heterogeneity - Container ecosystem (Docker alternatives) - Networking - Lightweight Virtualization - Unikernels / LibOS - State-of-the-art processor virtualization (RISC-V, EPI) - Containerizing HPC Stacks/Apps/Codes: Climate model containers each major topic encompassing design/architecture, management, performance management, modeling and configuration/tooling. Specifically, we invite papers that deal with the following topics: - HPC orchestration (Kubernetes) - Virtualizing Kubernetes for HPC - Deployment paradigms - Multitenancy - Serverless - Declerative data center integration - Network provisioning - Storage - OCI i.a. images - Isolation/security - HW Accelerators, including GPUs, FPGAs, AI, and others - State-of-practice/art, including transition to cloud - Frameworks, system software - Programming models, runtime systems, and APIs to facilitate cloud adoption - Edge use-cases - Application adaptation, success stories - Kubernetes Batch - Scheduling, job management - Execution paradigm - workflow - Data management - Deployment paradigm - Multi-cluster/scalability - Performance improvement - Workflow / execution paradigm - Podman: end-to-end Docker alternative container environment & use-cases - Creating, Running containers as non-root (rootless) - Running rootless containers with MPI - Container live migration - Running containers in restricted environments without setuid - Networking - Software defined networks and network virtualization - New virtualization NICs/Nitro alike ASICs for the data center? - Kubernetes SDN policy (Calico i.a.) - Kubernetes network provisioning (Flannel i.a.) - Lightweight Virtualization - Micro VMMs (Rust-VMM, Firecracker, solo5) - Xen - Nitro hypervisor (KVM) - RVirt - Cloud Hypervisor - Unikernels / LibOS - HPC Storage in Virtualization - HPC container storage - Cloud-native storage - Hypervisors in storage virtualization - Processor Virtualization - RISC-V hypervisor extensions - RISC-V Hypervisor ports - EPI - Composable HPC microservices - Containerizing Scientific Codes - Building - Deploying - Securing - Storage - Monitoring - Use case for containerizing HPC codes: Climate model containers for portability, reproducibility, traceability, immutability, provenance, data & software preservation The Workshop on Virtualization in High-Performance Cloud Computing (VHPC) aims to bring together researchers and industrial practitioners facing the challenges posed by virtualization in order to foster discussion, collaboration, mutual exchange of knowledge and experience, enabling research to ultimately provide novel solutions for virtualized computing systems of tomorrow. The workshop will be one day in length, composed of 20 min paper presentations, each followed by 10 min discussion sections, plus lightning talks that are limited to 5 minutes. Presentations may be accompanied by interactive demonstrations. Important Dates Jan 31st, 2020 - Abstract Apr 5th, 2020 - Paper submission deadline (Springer LNCS) Apr 26th, 2020 - Acceptance notification June 25th, 2020 - Workshop Day July 10th, 2020 - Camera-ready version due Chair Michael Alexander (chair), BOKU, Vienna, Austria Anastassios Nanos (co-chair), Sunlight.io, UK Program committee Stergios Anastasiadis, University of Ioannina, Greece Paolo Bonzini, Redhat, Italy Jakob Blomer, CERN, Europe Eduardo César, Universidad Autonoma de Barcelona, Spain Taylor Childers, Argonne National Laboratory, USA Stephen Crago, USC ISI, USA Tommaso Cucinotta, St. Anna School of Advanced Studies, Italy François Diakhaté CEA DAM Ile de France, France Kyle Hale, Northwestern University, USA Brian Kocoloski, Washington University, USA John Lange, University of Pittsburgh, USA Giuseppe Lettieri, University of Pisa, Italy Klaus Ma, Huawei, China Alberto Madonna, Swiss National Supercomputing Center, Switzerland Nikos Parlavantzas, IRISA, France Anup Patel, Western Digital, USA Kevin Pedretti, Sandia National Laboratories, USA Amer Qouneh, Western New England University, USA Carlos Reaño, Queen’s University Belfast, UK Adrian Reber, Redhat, Germany Riccardo Rocha, CERN, Europe Borja Sotomayor, University of Chicago, USA Jonathan Sparks, Cray, USA Kurt Tutschku, Blekinge Institute of Technology, Sweden John Walters, USC ISI, USA Yasuhiro Watashiba, Osaka University, Japan Chao-Tung Yang, Tunghai University, Taiwan Paper Submission-Publication Papers submitted to the workshop will be reviewed by at least two members of the program committee and external reviewers. Submissions should include abstract, keywords, the e-mail address of the corresponding author, and must not exceed 10 pages, including tables and figures at a main font size no smaller than 11 point. Submission of a paper should be regarded as a commitment that, should the paper be accepted, at least one of the authors will register and attend the conference to present the work. Accepted papers will be published in a Springer LNCS volume. The format must be according to the Springer LNCS Style. Initial submissions are in PDF; authors of accepted papers will be requested to provide source files. Abstract, Paper Submission Link: edas[dot]info/newPaper.php?c=26973 Lightning Talks Lightning Talks are non-paper track, synoptical in nature and are strictly limited to 5 minutes. They can be used to gain early feedback on ongoing research, for demonstrations, to present research results, early research ideas, perspectives and positions of interest to the community. Submit abstract via the main submission link. General Information The workshop is one day in length and will be held in conjunction with the International Supercomputing Conference - High Performance (ISC) 2019, June 21-25, Frankfurt, Germany.

1 0

[neutron] PTL on PTO
by Slawek Kaplonski 19 Dec '19

19 Dec '19

Hi, I will be on PTO from Friday 20.12.2019 up to 6.01.2020. I will probably not be available on IRC for most of the time but I will be checking emails from time to time. So if You have anything important, please email me. — Slawek Kaplonski Senior software engineer Red Hat

1 0

[neutron]CI meeting cancelled
by Slawek Kaplonski 19 Dec '19

19 Dec '19

Hi, Our Neutron CI meetings which should be on 24.12.2019 and 31.12.2019 will be cancelled. See You all in new year :) Have a great holiday time. — Slawek Kaplonski Senior software engineer Red Hat

1 0

[neutron] Team meeting cancelled
by Slawek Kaplonski 19 Dec '19

19 Dec '19

Hi, Our Neutron team meetings which should be on 23.12.2019 and 31.12.2019 will be cancelled. See You all in new year :) Have a great holiday time. — Slawek Kaplonski Senior software engineer Red Hat

1 0

[keystone] No meetings over the holidays
by Colleen Murphy 18 Dec '19

18 Dec '19

As discussed at yesterday's meeting, we'll cancel keystone team meetings for the next two weeks for the winter holidays. The next keystone meeting will be Tuesday, January 7 (17:00 UTC, #openstack-meeting-alt). Colleen

1 0

[resource-management-sig] Status of the "Resource Management" SIG
by Thierry Carrez 18 Dec '19

18 Dec '19

Hi, I was wondering about the status of the Resource Management SIG... It's been "forming" according to https://wiki.openstack.org/wiki/Res_Mgmt_SIG since January 2018... And I could'nt find a reference or log to any meeting after that. Does anyone have updated status on this one? Should it be removed from the list of active SIGs at https://governance.openstack.org/sigs/ ? -- Thierry Carrez (ttx)

5 6

[bifrost][ironic][kayobe][kolla][requirements] Kayobe CI breakage following ironic-lib release
by Pierre Riteau 18 Dec '19

18 Dec '19

Hello, I have been looking into CI failures that started impacting Kayobe today on the master branch, just as we're planning to branch stable/train this week (Kayobe is cycle trailing). Our seed jobs are failing because ironic doesn't start correctly [1]. The traceback shows that it is using code from the latest ironic-lib (3.0.0) which was released just last week [2] and dropped Python 2 compatibility. We're using Kolla Train images [3], but the latest kolla/centos-source-bifrost-deploy:train includes Bifrost 7.0.0 which fetches all its dependencies using Git master branches [4]. This only got changed later on stable/train [5], but there is no newer 7.x release. One of these dependencies is the requirements repo, which has just bumped the upper constraint for ironic-lib to 3.0.0 [6]. I believe this is what caused our jobs to start failing today. So I think we need: - a 7.0.1 release of Bifrost - an update of Kolla to use this release instead of 7.0.0 Would the ironic and kolla project teams be willing to help with this to fix our gate? Thanks a lot. [1] https://dafcf7323a7c828b67e0-814491f7a8e968b50eeaf14b0c7f115f.ssl.cf1.rackc… [2] https://review.opendev.org/#/c/698500/ [3] https://dafcf7323a7c828b67e0-814491f7a8e968b50eeaf14b0c7f115f.ssl.cf1.rackc… [4] https://opendev.org/openstack/bifrost/src/tag/7.0.0/playbooks/roles/bifrost… [5] https://review.opendev.org/#/q/I3005fc59d6c5e1f5000874342f956977d9929907 [6] https://review.opendev.org/#/c/698981/

2 4

[ironic] ibmc driver
by Julia Kreger 18 Dec '19

18 Dec '19

Greetings fellow ironicans and stackers! I'd like some thoughts on the `ibmc` driver[1] that was added early this year. Specifically it merged into ironic with an operating Third-Party CI, however soon after a series of unfortunate events occurred where the Third-Party CI stopped reporting sometime in early May, and shortly their after restrictions were put into place[2]. With that being said, I feel like we should go ahead and remove this driver since it does not seem to be maintained nor tested. -Julia [1]: https://review.opendev.org/#/c/639288/ [2]: https://www.federalregister.gov/documents/2019/05/21/2019-10616/addition-of…

3 4

[fuel] fuel-plugins, x/network-checker, x/fuel-noop-fixtures retirement
by Andreas Jaeger 18 Dec '19

18 Dec '19

Since we have now the fuel repositories retired, I propose to retire the fuel repos in the x/ namespace as well: all the plugins, network-checker and fuel-noop-fixuters There was no single merge to them since October 2017 (with exception of Ian's force-merge of URL replacements), see https://review.opendev.org/#/q/(projects:x/fuel-plugin+OR+project:x/network… I will push changes to repositories and would appreciate if teams merge them and abandon all open reviews. If anybody wants to keep the repos, please speak up here and/or -1 my changes. I'll use topic retire-x-fuel, https://review.opendev.org/#/q/topic:retire-x-fuel I'll just propose changes for now, we'll force-merge them in January 2020, Andreas -- Andreas Jaeger aj(a)suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB

1 0

[cinder] next meeting 8 January 2020
by Brian Rosmaita 18 Dec '19

18 Dec '19

As discussed during today's meeting, we will *not* hold the Cinder weekly meeting over the next 2 weeks. The next meeting will be on 8 January 2020. https://etherpad.openstack.org/p/cinder-ussuri-meetings cheers, brian

1 0

[tripleo] Gate is unstable, do not recheck/approve anything now
by Emilien Macchi 18 Dec '19

18 Dec '19

We're encountering a bug in TripleO, see https://bugs.launchpad.net/tripleo/+bug/1856864 In the meantime please do not recheck or approve a patch, the gate is already fully loaded; we'll purge it, fix the bug and recheck what needs to be done. You can follow the progress of that work on our IRC channel #tripleo. Thanks for your patience. -- Emilien Macchi

1 0

[neutron] Cancle neutron L3 meeting
by LIU Yulong 18 Dec '19

18 Dec '19

Hi all, Due to some local reasons, I'm not be able to host the L3 meeting today. So let's cancel it. And also because contributors from most countries will have the Christmas and new year's holidays in the next two weeks, let's also cancel the following two L3 meetings. So the next L3 meeting will be raised on 8th Jan, 2020. OK, see you guys then.  And happy new year! Regards, LIU Yulong

1 0

[kolla][horizon] Get 503 Service unavailable after set RETRIEVE_PASSWORD.
by Eddie Yen 18 Dec '19

18 Dec '19

Hi, Below is the information about this environment. Openstack release: Rocky Kolla container source type: binary OS distro: Ubuntu 18.04 We tried to set OPENSTACK_ENABLE_PASSWORD_RETRIEVE to True in local_settings, but the dashboard got "503 Service Unavailable" after restart the Horizon container. And there's no error log or something in horizon.log Is there anyway to see what's going on? - Eddie

2 2

[openstack-dev][kuryr] Unable to connect to kube-apiserver
by Veera.reddy B 18 Dec '19

18 Dec '19

Hi , I install Kubernetes using "kubeadm init". Followed below link to install "kuryr-kubernetes". https://docs.openstack.org/kuryr-kubernetes/latest/installation/manual.html… Kube api configuration : /etc/kubernetes/manifests/kube-apiserver.yaml http://paste.openstack.org/show/787704/ kuryr config file : /etc/kuryr/kuryr.conf http://paste.openstack.org/show/787705/ Error while starting kuryr : #> kuryr-k8s-controller --config-file /etc/kuryr/kuryr.conf http://paste.openstack.org/show/787706/ Let me what I am missing in "/etc/kuryr/kuryr.conf" Thanks, Veera.

2 1

[openstack-dev][kuryr] Unable to connect to kube-apiserver
by VeeraReddy 18 Dec '19

18 Dec '19

Hi , I install Kubernetes using “kubeadm init”. Followed below link to install “kuryr-kubernetes”. https://docs.openstack.org/kuryr-kubernetes/latest/installation/manual.html… Kube api configuration : /etc/kubernetes/manifests/kube-apiserver.yaml http://paste.openstack.org/show/787704/ kuryr config file : /etc/kuryr/kuryr.conf http://paste.openstack.org/show/787705/ Error while starting kuryr : #> kuryr-k8s-controller--config-file /etc/kuryr/kuryr.conf http://paste.openstack.org/show/787706/ Let me what I am missing in “/etc/kuryr/kuryr.conf” Thanks, Veera.

1 0

[scientific-sig] No IRC meeting today
by Stig Telfer 18 Dec '19

18 Dec '19

Hi All - Apologies, in the rush to end of year we have no agenda items for today. Given the season, I suggest we reconvene with a fresh start on Tuesday 7th January 2020. Cheers, Stig

1 0

[Watcher]IRC meeting at 8:00 UTC today
by licanwei 17 Dec '19

17 Dec '19

1 0

[nova][ironic] need help understanding 'cpu_arch' in nova ironic driver
by melanie witt 17 Dec '19

17 Dec '19

Hey all, Recently I'm trying to figure out how to fulfill a use case in the nova ironic driver around treating an ironic node's 'cpu_arch' as optional. This is coming up as a result of a downstream issue [1] and recent change on the ironic side [2] to make cpu_arch optional for iscsi deployments. The change makes it so that ironic will _not_ include a 'cpu_arch' attribute as part of a node's properties if iscsi. On the nova side, we have a filter scheduler ImagePropertiesFilter which will only match a node if the architecture, hypervisor_type, and vm_mode in the glance image properties match the cpu_arch of the node. We have always pulled the cpu_arch of the from the ironic node properties since the original ironic driver code was added to nova. Now, the use case I'm trying to solve today [3] is where an iscsi ironic deployment has no cpu_arch specified on the ironic side and the deployer wants to use glance images with architecture specified in their image properties. Today (and historically always) the request to create an instance in this situation will fail with NoValidHost because the nova ironic driver could not determine a cpu_arch from the ironic node. My questions are: * Is this a valid thing to want to do? * If if is valid, what is the correct way that we should handle missing cpu_arch in the nova ironic driver? Should we guess at a default cpu_arch? If so, how? Or should we add a new config option where a default cpu_arch can be specified? Or, other? Thanks in advance for any input you can offer. Cheers, -melanie [1] https://bugzilla.redhat.com/show_bug.cgi?id=1653788 [2] https://review.opendev.org/620634 [3] https://bugzilla.redhat.com/show_bug.cgi?id=1688838

3 3

[TC] 'V' Technical Elections
by Kendall Nelson 17 Dec '19

17 Dec '19

Hello! /me takes TC hat off and puts election official hat on Having run our handy dandy tool to project dates[1] for the elections, we have some decisions to make again. At this point we have threeish options: 1. Run the elections with a week in between with the TC election happening BEFORE the PTL election like the script generated. The TC election would run March 10 to March 31 and the PTL Election would run April 7 to April 21. The primary concern here is that it might lead to some election burnout. 2. Run the elections back to back with the PTL election first (closer to the historic norm). This would be tweaking the generated dates by pulling the PTL election three weeks up and pushing back the TC dates by two weeks. The PTL election would run March 3 to March 17 and the PTL Election would run March 17 to April 7. Both elections would be concluded by milestone 3. Similar concerns with this option to the first with election burnout. 3. Run the elections in parallel as a combined election, similar to how we did for the Train elections. This is much easier for election officials because we only need to generate one electorate. The two elections would start March 10 and be done by March 31 following the TC election model with a nominations period, a campaigning period (optional for PTL elections), and then a polling period (assuming we need a runoff). Other info to keep in mind when formulating your opinions: - Extra ATC deadline currently is March 23-27 which will likely need to get bumped earlier for any of these options - RC1 is the week of April 20-24 - Milestone 3 is April 9 - Release schedule for reference[2] - For TC member terms, those closing in on their ~1 year terms would be closer to 13 months since the train elections concluded March 5th of last year -Kendall (diablo_rojo) & the Election Officials [1]http://paste.openstack.org/show/787114/ [2]https://releases.openstack.org/ussuri/schedule.html

9 24

[searchlight] Elasticsearch 5 and latest support
by Mathieu Gagné 17 Dec '19

17 Dec '19

Hi, I'm reading the documentation for Searchlight and it's recommending ElasticSearch 5.x: https://docs.openstack.org/searchlight/latest/install/elasticsearch.html I installed and tried to use Elasticsearch 5 and it doesn't work. The queries sent by Searchlight aren't accepted by Elasticsearch. For examples: When listing facets: TransportError(400, u'parsing_exception', u'[terms] failed to parse field [size]'): RequestError: TransportError(400, u'parsing_exception', u'[terms] failed to parse field [size]') When searching for images: No registered plugin for type owner: Exception: No registered plugin for type owner Is there any work in progress to add support for Elasticsearch 5? In fact, Elasticsearch 5 is EOL. Are there plans to support later versions? Thanks -- Mathieu

2 4

[OSH][Infra] Open UDP port 111 on test nodes
by Clark Boylan 17 Dec '19

17 Dec '19

Hello, One of our contributing test node clouds has discovered that occasionally one of our test nodes will have udp port 111 open. The concern with this is that the RPC portmap service can be used in reflection DDoS attacks. Upon further investigation we've discovered that this seems to happen in OSH jobs (like openstack-helm-multinode-temp-ubuntu) [0] that run OSH's setup-firewall role [1]. These jobs do indeed disable the host firewall which would leave any running port mapper service exposed. It looks like these jobs run with multiple nodes in their nodeset, but do not use the multinode base job. I point this out because the multinode base job aims to set up networking and firewalls such that the nodes can talk freely among themselves while still blocking out the outside world. If we need to enable network communicate between hosts in these jobs this seems like a good place to start. That said there is a good chance that kubernetes may need additional open traffic. Additionally, I expect those specific depend on the CNI plugin that has been chosen? >From an infrastructure perspective we'd like to be good stewards of the resources donated to us and in this case that means preventing unwanted network traffic. We are more than happy to help set up more appropriate firewall rules if we can get details on what is needed. I expect the Zuul project is also interested and we can bake some of these common network needs for kubernetes into Zuul's zuul-job standard library. Can the OSH project work with us to fix this problem? Perhaps other kubernetes users/devs/operators can chime in on how they have reconciled host firewalls with kubernetes network needs? Any help that can be provided here would be much appreciated. [0] http://zuul.opendev.org/t/openstack/build/6fc5285fdb76484b894f0d288facdbb2/… [1] https://opendev.org/openstack/openstack-helm-infra/src/branch/master/roles/… Thank you, Clark

2 1

[all] Volunteer mailing list administrators
by Jeremy Stanley 17 Dec '19

17 Dec '19

This is a long-overdue request. It's been more than a year since we combined openstack, openstack-dev, openstack-ops, openstack-sigs, openstack-tc and a number of other lower-traffic mailing lists into this new openstack-discuss mailing list. In that time, I've been serving as the sole administrator and moderator for the combined list. As I'm about to take an extended vacation away from regular Internet access for the first time since the list migration, I will be unable to check the moderation queue on a daily basis, and so would appreciate a bit of help from some of you. If there's anyone interested in helping out as additional administrators for the openstack-discuss mailing list, please reply to this message on-list (so other subscribers know who is volunteering) and I'll help bring you up to speed. In the immediate term I need at least one person willing to check the moderation queue a few times in the second half of December while I'm unavailable (daily would be awesome but a couple times a week is probably fine really). If you're expecting to be around and able to help with that, please respond on Monday or Tuesday of this week and I'll sync up to get you a copy of the Mailman administrator password for it and a quick walk-through of the moderator interface (if you already moderate other Mailman lists, all the better!). Moderation queue volume is typically on the order of twenty to fifty messages a day, most of which are spam of course, but one or two a day on average are legitimate messages either from non-subscribers with a question or sometimes slightly over the size limit because of attached logs. The spam and non-spam are pretty easy to tell apart if you've been around our community for a while: if the subject of the message has a recognizable topic tag in it or mentions the name of some OpenStack project then it's quite likely legitimate and can be approved. Spam on the other had usually either has a subject which is not in English (the required language for messages to this list) or is clearly someone selling something or running a scam. When in doubt though, you can quickly check the message body to be sure. I tend to spend at most 5 minutes a day looking through the moderation queue (and usually far less). Longer term, I'd like to see anywhere between 3-5 admins for the openstack-discuss list. No need to coordinate workload or vacations that way, we can just each check the queue when we think about it and that should be plenty often. Also while keeping on top of the moderation queue is the primary need, it would be great for these folks to know/learn a bit about how Mailman mailing lists are configured and how to troubleshoot them from the WebUI and message headers. Better still, if anyone wants to get even more involved, the OpenDev sysadmins would always welcome new recruits willing to help manage and run our mailing list servers and our infrastructure overall, I'm happy to make introductions! -- Jeremy Stanley

8 14