Inside the world of Red Hat, and other open source-oriented companies, there is a recurring metaphor to try to help explain the relationship between the projects where our source software is created and the commercially available software we ship with support, training, and other value-adds.
The metaphor used is "upstream" and "downstream," where upstream code is the "source" project code and "downstream" is the refined product code. Thus, Fedora is the upstream to Red Hat Enterprise Linux’s downstream, to pick one example.
But increasingly we have been noticing a certain problem with this metaphor: very few people outside Red Hat and companies in this sector of IT really understood what the whole "stream" metaphor meant. Worse, when we really looked at the upstream/downstream metaphor ourselves, we realized that it has a fairly big flaw on its own.
Zaqar (formerly called Marconi) is the messaging service in OpenStack. I recently had an opportunity to interview Flavio Percoc, who is the PTL (Project Technical Lead) of that project, about what’s new in Kilo, and what’s coming in Liberty.
The recording is here, and the transcript follows after the break.
(If the player below doesn’t work for you, you can listen HERE)
Continuing in the series about the RDO Meetup in Vancouver, in this recording we have Karsten Wade, of the CentOS project, talking about CentOS’s relationship with RDO, and with OpenStack in general. He talks about the CentOS build infrastructure, CI, package repos, and the CentOS Cloud SIG.
(If the player below doesn’t work for you, you can listen HERE
Last month at the RDO meetup in Vancouver, a number of topics were discussed. Jarda talked about RDO-Manager, the installation and management tool based on TripleO. Here’s just that part of the meeting.
If the embedded player below doesn’t work for you, you can listen HERE.