A while ago there was a discussion around python-shade library and
getting it into RDO. 
It's been a few months since then, and shade is now successfully
packaged and shipped as part of Fedora  which is great, but now I
wanted to restart the conversation about how to make it available to
users of CentOS/RDO.
While it was suggested to get it into EPEL, I don't feel that is the
best course of action simply because of the restrictive update policies
of EPEL not allowing us to update it as frequently as needed, and also
because python-shade depends on the python openstack clients, which are
not a part of EPEL (as my understanding).
The best place for us to make this package available is in RDO itself,
as shade is an official Openstack big tent project, and RDOs aims to be
a distribution providing packages for Openstack projects.
So I just wanted to confirm with everyone and get some feedback, but
unless there is any major objections, I was going to start looking at
the process to get a new package into RDO, which I assume means putting
a review request in to the project https://github.com/rdo-packages
(though I assume a new repo needs to be created for it first).
Principal Systems Administrator
Red Hat Australia
As you no doubt know by now ... well, I'll just quote from another list:
As you probably already know, the OpenStack Foundation is restructuring
its events in 2017, splitting the activities that traditionally occurred
at the Design Summit event into work sessions (at the "Project Teams
Gathering" at the start of the cycle) and open community discussions
("Forum" at the OpenStack Summit in the middle of the cycle). You can
learn more about this at http://www.openstack.org/ptg
At the last several OpenStack Summits, the RDO community has hosted some
kind of meetup, and of course last week, we had an evening gathering
that we shared with the Ceph community, where we had 215 people in
With OpenStack Summit splitting in two, I'm left uncertain what, if
anything, I should be planning for 2017. Will most of the RDO community
attend the PTG, or OpenStack Summit? At which one of these does it make
the most sense to try to do an RDO gathering, if at all?
I can see good arguments for each, including my personal travel plans
;-) but I would like to hear from the rest of you - if I try to do
another event like what we did Tuesday evening in Barcelona, which event
makes more sense?
Rich Bowen - rbowen(a)redhat.com
RDO Community Liaison
A reminder - we are running an RDO survey at http://tm3.org/rdo-survey/
which will hopefully show us how people are using RDO, ways that the
community thinks that RDO can improve, and ways that people want to get
So far, we have a very small number of responses (30). I'm hoping that
the many people I gave the URL to at OpenStack Summmit will in fact come
to fill out the survey. Please pass the URL on to people that you know
are using RDO.
I intend to close the survey after another week or two. I'd like to have
a lot more responses, but I also want to be able to share the results
with the community without having to wait too much longer.
Rich Bowen - rbowen(a)redhat.com
RDO Community Liaison
FYI, this is the schedule of talks at the Ceph/RDO event in Barcelona on
-------- Forwarded Message --------
Subject: An Evening of Ceph and RDO (schedule)
Date: Thu, 13 Oct 2016 11:38:10 -0400
From: Patrick McGarry <pmcgarry(a)redhat.com>
These are all 5-10m lightning talks. Let me know if there are any
0. Welcome and Intro (Patrick/Rich)
1. Jack Zhang, Intel -- 3D Xpoint & 3D NAND with OpenStack and Ceph
2. Haïkel Guémar - RDO release status (aarch64, repos, workflow)
3. George Mihaiescu, Bioinformatics -- Openstack and Ceph used in
large scale cancer research projects
4. Javier Peña - RDO repos overview (CBS vs Trunk, and what goes where)
5. Lars Marowsky Bree, SUSE -- Ceph at SUSE
6. Gulio Fidente: RDO and Ceph
7. Allen Samuels, Sandisk -- Bluestore Teaser
8. Jeff Chu, ARM -- Ceph on ARM
9. Jakub Ruzicka - quick look at new rpmfactory workflow with rdopkg
10. Dan van der Ster, CERN -- How to replace several petabytes of
Ceph hardware without downtime
11. Alfredo Moralej - CI in RDO - what are we testing?
12. Sage Weil, Red Hat - Project Update
with newton, manually installed, when I start the neutron agent for
openvswitch (on network node and/or compute nodes), the service fails, only
saying "uncaught exception".
We spent weeks to diagnos this problem. yes weeks...
If I override LANG to C in systemd unit files it works !!!
Seems a subcommand in some python librairies is waiting for "Exit code" in
stdout, but on my system we have "Code de sortie" instead (french here). Is
that a known bug ?
Here's the more formal announcement with more details.
---------- Forwarded message ----------
From: "Brian Proffitt" <bproffit(a)redhat.com>
Date: Oct 21, 2016 21:24
Subject: CfP Announcement: Virtualization and IaaS Devroom
To: <fosdem(a)lists.fosdem.org>, <iaas-virt-devroom(a)lists.fosdem.org>
On behalf of oVirt and the Xen Project, we are excited to announce that the
call for proposals is now open for the Virtualization & IaaS devroom at the
upcoming FOSDEM 2017, to be hosted on February 4, 2017.
This year will mark FOSDEM’s 17th anniversary as one of the longest-running
free and open source software developer events, attracting thousands of
developers and users from all over the world. FOSDEM will be held once
again in Brussels, Belgium, on February 4 & 5, 2017.
This devroom is a collaborative effort, and is organized by dedicated folks
from projects such as OpenStack, Xen Project, Mesos, oVirt, and Foreman. We
would like to invite all those who are involved in these fields to submit
your proposals by November 18th, 2016.
About the Devroom
The Virtualization & IaaS devroom will feature session topics such as open
source hypervisors and virtual machine managers such as Xen Project, KVM,
bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as
Apache CloudStack, OpenStack, oVirt, OpenNebula, and Ganeti.
This devroom will host presentations that focus on topics of shared
interest, such as KVM; libvirt; shared storage; virtualized networking;
cloud security; clustering and high availability; interfacing with multiple
hypervisors; hyperconverged deployments; and scaling across hundreds or
thousands of servers.
Presentations in this devroom will be aimed at developers working on these
platforms who are looking to collaborate and improve shared infrastructure
or solve common problems. We seek topics that encourage dialog between
projects and continued work post-FOSDEM.
Submission deadline: 18 November 2016
Acceptance notifications: 04 December 2016
Final schedule announcement: 11 December 2016
Devroom: 04 February 2017 (one day)
Submit Your Proposal
All submissions must be made via the Pentabarf event planning site. If
you have not used Pentabarf before, you will need to create an account. If
you submitted proposals for FOSDEM in previous years, you can use your
After creating the account, select Create Event to start the submission
process. Make sure to select Virtualisation and IaaS devroom from the Track
list. Please fill out all the required fields, and provide a meaningful
abstract and description of your proposed session.
We expect more proposals than we can possibly accept, so it is vitally
important that you submit your proposal on or before the deadline. Late
submissions are unlikely to be considered.
All presentation slots are 45 minutes, with 35 minutes planned for
presentations, and 10 minutes for Q&A.
All presentations will be recorded and made available under Creative
Commons licenses. In the Submission notes field, please indicate that you
agree that your presentation will be licensed under the CC-By-SA-4.0 or
CC-By-4.0 license and that you agree to have your presentation recorded.
"If my presentation is accepted for FOSDEM, I hereby agree to license all
recordings, slides, and other associated materials under the Creative
Commons Attribution Share-Alike 4.0 International License. Sincerely,
In the Submission notes field, please also confirm that if your talk is
accepted, you will be able to attend FOSDEM and deliver your presentation.
We will not consider proposals from prospective speakers who are unsure
whether they will be able to secure funds for travel and lodging to attend
FOSDEM. (Sadly, we are not able to offer travel funding for prospective
Speaker Mentoring Program
As a part of the rising efforts to grow our communities and encourage a
diverse and inclusive conference ecosystem, we're happy to announce that
we'll be offering mentoring for new speakers. Our mentors can help you with
tasks such as reviewing your abstract, reviewing your presentation outline
or slides, or practicing your talk with you.
You may apply to the mentoring program as a newcomer speaker if you:
Never presented before or
Presented only lightning talks or
Presented full-length talks at small meetups (<50 ppl)
Mentored presentations will have 25-minute slots, where 20 minutes will
include the presentation and 5 minutes will be reserved for questions.
The number of newcomer session slots is limited, so we will probably not be
able to accept all applications.
You must submit your talk and abstract to apply for the mentoring program,
our mentors are volunteering their time and will happily provide feedback
but won't write your presentation for you!
If you are experiencing problems with Pentabarf, the proposal submission
interface, or have other questions, you can email our devroom mailing
list and we will try to help you.
How to Apply
In addition to agreeing to video recording and confirming that you can
attend FOSDEM in case your session is accepted, please write "speaker
mentoring program application" in the "Submission notes" field, and list
any prior speaking experience or other relevant information for your
Call for Mentors
Interested in mentoring newcomer speakers? We'd love to have your help!
Please email iaas-virt-devroom at lists.fosdem.org with a short speaker
biography and any specific fields of expertise (for example, KVM,
OpenStack, storage, etc.) so that we can match you with a newcomer speaker
from a similar field. Estimated time investment can be as low as a 5-10
hours in total, usually distributed weekly or bi-weekly.
Never mentored a newcomer speaker but interested to try? As the mentoring
program coordinator, I will be happy to answer your questions and give you
tips on how to optimize the mentoring process. Email Brian Proffitt and
he will be happy to answer your questions!
Code of Conduct
Following the release of the updated code of conduct for FOSDEM, we'd like
to remind all speakers and attendees that all of the presentations and
discussions in our devroom are held under the guidelines set in the CoC and
we expect attendees, speakers, and volunteers to follow the CoC at all
If you submit a proposal and it is accepted, you will be required to
confirm that you accept the FOSDEM CoC. If you have any questions about the
CoC or wish to have one of the devroom organizers review your presentation
slides or any other content for CoC compliance, please email us and we will
do our best to assist you.
Call for Volunteers
We are also looking for volunteers to help run the devroom. We need
assistance watching time for the speakers, and helping with video for the
devroom. Please contact me, Brian Proffitt, for more information.
If you have any questions about this devroom, please send your questions to
our devroom mailing list. You can also subscribe to the list to receive
updates about important dates, session announcements, and to connect with
See you all at FOSDEM!
Principal Community Analyst
Open Source and Standards
iaas-virt-devroom mailing list