When I talk about Red Hat's involvement in RDO (http://openstack.redhat.com/) the question I often get is, "doesn't that undermine sales of RHEL OSP (Red Hat's paid OpenStack offering)?"
Well, it's complicated.
When I talk about Red Hat's involvement in RDO (http://openstack.redhat.com/) the question I often get is, "doesn't that undermine sales of RHEL OSP (Red Hat's paid OpenStack offering)?"
Well, it's complicated.
For the first year and a half, RDO has been largely an effort run by Red Hatters, with some of the work going on behind the firewall. In our community meetup in Paris, at the OpenStack Summit, as I mentioned in my earlier post, we got a lot of feedback from people saying that they wanted greater insight into what we were doing, as well as the opportunity to play along.
So I wanted to quickly update with some of the things that we're doing in RDO to "swim upstream" a little more.
The CentOS Cloud SIG is moving along, although officially still in the "getting started" phase. We've started having weekly meetings on IRC, on the #centos-devel channel on Freenode. Those meetings are at 15:00 UTC every Thursday. (date -d "15:00 UTC"
in your favorite shell will translate that to local time for you.) Have a look at the [minutes fro
Yesterday, Eoghan Glynn led a Hangout to discuss the work around rebooting the OpenStack Ceilometer project, using the new approaches of the Gnocci project.
As you may remember, we talked about some of these ideas back in July in a podcast with Eoghan, and a lot of progress has been made towards those goals since then.
In the hangout, Eoghan talks about the Gnocci work, and how it restructures Ceilometer's internal data store, and provides a more lightweight API for retrieving current and historical data about your OpenStack implementation. Gnocci attempts to correct what is seen as a design misstep in the early days of Ceilometer, in which a great deal of static, or almost-static, data, is included in each data sample, resulting in poor performance and more storage space usage than necessary.
You can watch the hangout on YouTube and bring yo
Over the last few months, the RDO project - http://rdoproject.org/ - has been working with the CentOS project - http://centos.org/ - to provide packages and CI around OpenStack for people running CentOS, Red Hat Enterprise Linux, and Fedora, as part of the Cloud SIG effort - http://wiki.centos.org/SpecialInterestGroup/Cloud
This talk will cover what we're doing with the CentOS packaging effort, what remains to be done, and where you can get involved in this work.
RDO is a community of OpenStack developers and users on CentOS, Fedora, and Red Hat Enterprise Linux. The CentOS Linux distribution is a stable, predictable, manageable and reproduceable platform derived from the sources of Red Hat Enterprise Linux (RHEL).
Abstract for Infra.next, SCALE edition
OpenStack is "Open source software for creating private and public clouds." As with most Open Source projects, they release source code, and leave it to third parties to provide packages and distributions. Also, since OpenStack is a complicated stack of components, deployment can be tricky, and there's a number of third-party solutions for that, too.
RDO is a community effort to provide OpenStack packages for CentOS (and other RPM-based distros, like Fedora and RHEL), and a deployment tool to make it easier to use. In this talk, Rich Bowen, RDO OpenStack Community Liaison, will talk about that effort, the progress so far, and where you can help out in this effort. Along the way, CentOS board member and developer Jim Perrin will help answer difficult questions about CentOS and some of the details of packaging.
Neutron - port doesnt actually come up, until state is toggled - https://ask.openstack.org/en/question/33203/neutron-port-doesnt-actually-come-up-until-state-is-toggled/
Problem attaching a second interface into a VM - https://ask.openstack.org/en/question/44793/problem-attaching-a-second-interface-into-a-vm/
issue while deploying openstack on a public cloud VM - https://ask.openstack.org/en/question/45729/issue-while-deploying-openstack-on-a-public-cloud-vm/
icehouse with ML2 : VMs not able to get DHCP on Centos 6.5 - https://ask.openstack.org/en/question/45849/icehouse-with-ml2-vms-not-able-to-get-dhcp-on-centos-65/ (Issue appears abandoned. Will probably close unless someone has some insight that they'd like to share.)
The Apache Software Foundation is excited to invite you to ApacheCon North America, which we'll be holding in Austin, Texas, April 13th - 16th.
TL;DR: Register today!
This event marks a couple of important anniversaries for us.
It's been 15 years since the first official ApacheCon, which we held in Orlando in march of 2000. (There was an earlier ApacheCon, but the Apache Software Foundation hadn't been incorporated at that point.)
It's also been 20 years since the initial release of the Apache HTTP Server, the project that started it all, and one of the most influential projects in all of the Open Source landscape. We'll be celebrating that by having Brian Behlendorf, the instigator of Apache httpd, keynote. But although he might spend some time nostalgically looking back, he'll be setting the tone for the rest of the event by mostly
My primary job as EVP has been ApacheCon. Since the last members meeting we have produced ApacheCon Europe in Budapest and we're about to do ApacheCon North America Austin, April 13-17. These are the second and third events that we have done under the Linux Foundation contract.
A major goal of the Linux Foundation contract was to move all logistical support and financial risk to an organization that does these things as their main mission. To this end, we have licensed our brands to LF, and various volunteers have been the ASF liaisons for the CFP process, and various other community-related things.
We are pleased to report that LF continues to take more ownership of these shows, making decisions that are conducive to the financial success of these events, and deferring to us only on matters of brand and content. We continue to discuss what might be the effective ways to fairly represent 200+ projects into this event. Options under consideration include breaking out ApacheCon into topic-specific events (Apa
Apachecon mailing list - populate with registrants? (Ask CCR) What apachecon mailing lists do we still have, and what are the subscriber counts?
Local folks who can make connections with Universities, Govt, or companies willing to donate space.
Documentation for successful barcamp? (Ask Nick)
Definition: RTFM - Read The F'ing Manual. Occasionally it is ironically rendered as Read The Fine Manual. A phrase uttered at people who have asked a question that we, the enlightened, feel is beneath our dignity to answer, but not beneath our dignity to use as an opportunity to squish a newbie's ego.
Have you noticed that the more frequently a particular open source community tells you to RTFM, the worse the FM is likely to be? I've been contemplating this for years, and have concluded that this is because patience and empathy are the basis of good documentation, much as they are the basis for being a decent person.
First, some disclaimers.
Although I've been doing open source documentation for almost 20 years, I have no actual training. There are some people that do, and there are some amazing books out there that you should read if you care about this stuff.
First, I'd recommend [Conversation and Community](http://www.amazon.com/Conversation-Community-Social-Web-Documentation-ebook/dp/B00C7CC