[Rdo-list] [rdo-manager] Moving some rdo-manager components to git.openstack.org
by James Slagle
Recently, folks have been working on moving the rdo-manager based workflow
upstream into the TripleO project directly.
This has been discussed on openstack-dev as part of this thread:
http://lists.openstack.org/pipermail/openstack-dev/2015-July/070140.html
Note that the thread spans into August as well.
As part of this move, a patch has been proposed to move the following repos out
from under github.com/rdo-management to git.openstack.org:
instack
instack-undercloud
python-rdomanager-oscplugin (will be renamed in the process, probably
to python-tripleoclient)
The patch is here: https://review.openstack.org/#/c/215186
I wanted to give everyone a heads up about this move. We don't have a firm
timeline nailed down as it depends on when OpenStack infra accepts the patch.
At that point, I'll send out another mail here.
As there are some reviews still on review.gerrithub.io for these projects,
we'll need to handle that as well. We can either ask folks to repropose to
review.openstack.org after the move, or have 1 or 2 volunteers go through the
list and repropose everything themself (I'm happy to do it for
instack-undercloud). This has the downside of losing the previous review
history from gerrithub. I'm not sure if there is an elegant solution to this.
I've been trying to push forward many of the reviews against instack-undercloud
the last day or 2 to try and get as much committed as possible before the
import to git.openstack.org, but the CI on ci.centos.org has had quite a few
sporadic failures (mostly network hiccups causing yum download or git
clone errors).
--
-- James Slagle
--
8 years, 7 months
[Rdo-list] [meeting] RDO packaging meeting (2015-09-09)
by Chandan kumar
========================================
#rdo: RDO packaging meeting (2015-09-09)
========================================
Meeting started by chandankumar at 15:01:03 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/rdo/2015-09-09/rdo.2015-09-09-15.01.log....
.
Meeting summary
---------------
* roll call (chandankumar, 15:01:11)
* status of python3 subpackages for python-oslo-* and python-* packages
(chandankumar, 15:03:11)
* LINK: https://etherpad.openstack.org/p/RDO-Packaging (number80,
15:03:17)
* for now it py3 porting is in lower priority (chandankumar,
15:04:37)
* Updating RDO docs from older openstack releases to latest openstack
releases. (chandankumar, 15:06:59)
* ACTION: rbowen organize doc hack day (number80, 15:08:27)
* ACTION: jruzicka to update https://www.rdoproject.org/Clients
(chandankumar, 15:08:50)
* New Package SCM requests (chandankumar, 15:19:06)
* I may steal some core reviews later (number80, 15:20:55)
* add apevec as owners in core deps and jruwicka for clients
(chandankumar, 15:21:24)
* New packages under review (chandankumar, 15:22:47)
* LINK: python-django-formtools
https://bugzilla.redhat.com/show_bug.cgi?id=1261134 (chandankumar,
15:23:28)
* LINK: python-tosca-parser
https://bugzilla.redhat.com/show_bug.cgi?id=1261119 (chandankumar,
15:23:39)
* package rename (chandankumar, 15:29:43)
* ACTION: number80 work with trown on renamed packages (number80,
15:32:46)
* python-qpid status (chandankumar, 15:35:29)
* LINK: python-quid https://fedorahosted.org/rel-eng/ticket/6218
(chandankumar, 15:36:32)
* python-qpid is still blocked in f24 (apevec, 15:37:19)
* ACTION: apevec to rebuild oslo.messaging without qpid dep (apevec,
15:42:29)
* ACTION: number80 to finish python-futurist review
https://bugzilla.redhat.com/show_bug.cgi?id=1243052 (apevec,
15:45:17)
* delorean CI (chandankumar, 15:45:42)
* LINK:
https://prod-rdojenkins.rhcloud.com/view/RDO-Liberty-Delorean-Trunk/
(chandankumar, 15:46:08)
* ACTION: apevec to switch Delorean Trunk to use
http://cbs.centos.org/repos/cloud7-openstack-liberty-testing/ +
http://cbs.centos.org/repos/cloud7-openstack-common-testing/
(apevec, 15:48:28)
* xstatic bundles javascript libs which have bundling exception (not
fonts!) and all of them do not license file (please file tickets
upstream) (chandankumar, 15:50:14)
* RDO Test day (chandankumar, 15:51:20)
* objective is to have no failing builds in delorean by the end of the
week (number80, 15:51:56)
* RDO test day is on sep 23/24, 2015 (chandankumar, 15:52:46)
* Oct 15/16, 2015 for testing release candidate (chandankumar,
15:54:20)
* ACTION: number80 reviwing midonet packages (number80, 15:56:15)
* Murano (server and client) and EC2-API RPMs (chandankumar, 15:58:08)
* LINK: openststack-dev mailing list
http://lists.openstack.org/pipermail/openstack-dev/2015-September/073820....
(mflobo, 15:59:47)
* open floor (chandankumar, 16:01:38)
Meeting ended at 16:04:32 UTC.
Action Items
------------
* rbowen organize doc hack day
* jruzicka to update https://www.rdoproject.org/Clients
* number80 work with trown on renamed packages
* apevec to rebuild oslo.messaging without qpid dep
* number80 to finish python-futurist review
https://bugzilla.redhat.com/show_bug.cgi?id=1243052
* apevec to switch Delorean Trunk to use
http://cbs.centos.org/repos/cloud7-openstack-liberty-testing/ +
http://cbs.centos.org/repos/cloud7-openstack-common-testing/
* number80 reviwing midonet packages
Action Items, by person
-----------------------
* apevec
* apevec to rebuild oslo.messaging without qpid dep
* apevec to switch Delorean Trunk to use
http://cbs.centos.org/repos/cloud7-openstack-liberty-testing/ +
http://cbs.centos.org/repos/cloud7-openstack-common-testing/
* jruzicka
* jruzicka to update https://www.rdoproject.org/Clients
* number80
* number80 work with trown on renamed packages
* number80 to finish python-futurist review
https://bugzilla.redhat.com/show_bug.cgi?id=1243052
* number80 reviwing midonet packages
* rbowen
* rbowen organize doc hack day
* trown
* number80 work with trown on renamed packages
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* chandankumar (87)
* number80 (46)
* jruzicka (31)
* apevec (29)
* rbowen (15)
* mflobo (15)
* trown (13)
* dtantsur (13)
* zodbot (9)
* dmsimard (8)
* jpena (7)
* derekh (6)
* mburned (1)
* xinwu_ (1)
* social (1)
* imcsk8 (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
8 years, 7 months
[Rdo-list] RDO test days
by Rich Bowen
We'd like to do a couple of test days leading up to the Liberty release,
to make sure we're in good shape.
We were thinking maybe one in the latter half of September - say, Sep 23
or 24? - to test a Delorean snapshot that has passed CI.
And then another test day on October 15th/16th for GA. The GA release is
to be on the 15th, so we'd be testing with what will be in that release.
(I'm reluctant to do this the week after GA, simply because it's the
week before Summit, and people will be distracted and traveling.)
Thoughts?
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://rdoproject.org/
8 years, 7 months
[Rdo-list] The week in RDO blogs: September 8
by Rich Bowen
Here's what RDO enthusiasts have been writing about over the past week.
If you're writing about RDO, or about OpenStack on CentOS, Fedora or
RHEL, and you're not on my list, please let me know!
How Red Hat’s OpenStack partner Networking Solutions Offer Choice and
Performance, by Jonathan Gershater
Successfully implementing an OpenStack cloud is more than just choosing
an OpenStack distribution. With its community approach and rich
ecosystem of vendors, OpenStack represents a viable option for cloud
administrators who want to offer public-cloud-like infrastructure
services in their own datacenter. Red Hat Enterprise Linux OpenStack
Platform offers pluggable storage and networking options. This open
approach is contrary to closed solutions such as VMware Integrated
OpenStack (VIO) which only supports VMware NSX for L4-L7 networking or
VMware Distributed switch for basic L2 networking
... read more at http://tm3.org/27
Analyzing awareness of MidoNet globally, by Sandro Mathys
One thing that is hard to measure in open source projects is just how
aware people are of your community or its software. It's even harder to
find out where in the world people have heard about you so far. You
might have a rough feeling, probably based on some facts like the
country-specific TLDs of email addresses on your mailing lists. But
that's very vague and only includes people actively participating (and
there's more and less vocal people, too).
... read more at http://tm3.org/28
Kyle Mestery and the future of Neutron, by Rich Bowen
At LinuxCon two weeks ago I had the privilege of chatting with Kyle
about the future of Neutron. Kyle was a delight to interview, because
he's obviously so passionate about his project
.
... read (and listen) at http://tm3.org/29
RDO Juno DVR Deployment (Controller/Network)+Compute+Compute
(ML2&OVS&VXLAN) on CentOS 7.1 by Boris Derzhavets
Neutron DVR implements the fip-namespace on every Compute Node where the
VMs are running. Thus VMs with FloatingIPs can forward the traffic to
the External Network without routing it via Network Node. (North-South
Routing).
... read more at http://tm3.org/2a
Managing OpenStack: Integration Matters! by Matt Hicks
With so many advantages an Infrastructure-as-a-Service (IaaS) cloud
provides businesses, it’s great to see a transformation of IT happening
across nearly all industries and markets. Nearly every enterprise is
taking advantage of an “as-a-service” cloud in some form or another. And
with this new infrastructure, it’s now more important than ever to
remember the critical role that management plays within this mix. Oddly
enough, it is sometimes considered a second priority when customers
begin investigating the benefits of an IaaS cloud, but quickly becomes
your first priority when running one.
... read more at http://tm3.org/2b
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://rdoproject.org/
8 years, 7 months
[Rdo-list] [packaging] heads-ups about python packaging guidelines
by Haïkel
Hi,
Fedora python guidelines have been updated with newer macros, affecting some of
our base dependencies.
To keep our packaging consistent and avoid error-prone workarounds to support
both Fedora and CentOS, I collected these in a rdo-rpm-macros.
https://github.com/hguemar/rdo-rpm-macros/
>From now onwards, we'll maintain macros in this package to ensure compatibility
between targets and simplify OpenStack packaging.
It has been added to CBS buildroot by alphacc
(search for rdo-rpm-macros:
http://cbs.centos.org/kojifiles/work/tasks/2021/32021/root.log)
Some recommendations:
* drop all the workarounds
* if you're updating an existing package (ie: python-xxx)
python2-xxx should obsolete python-xxx to avoid upgrade issues
Obsoletes: python-xxx <= <last version in fedora rawhide or CBS>
* new package: take care that we provides the proper name of the package
and not python-%{pypi_name}
Looks like pyp2rpm does not fix it for you.
* for new dependencies: prefer using python2-xxx instead of python-xxx as
default version of python may change in the future.
Please do *not* rush in changing all deps, keep existing requires!
Our priority should be stabilizing RDO Liberty now. This will be done
in Mitaka cycle.
Regards,
H.
8 years, 7 months
[Rdo-list] [RFC] RDO Big Tent projects acceptance guidelines
by Haïkel
Hi,
RDO is growing, and with upstream Big Tent initiative, many people offered
to integrate more projects into RDO.
As a truly open community, we need to set proper guidelines to define
which projects should be accepted or not in RDO.
Below, you'll find a draft for such guidelines, and I would like to receive your
feedback
Projects have to
1. be part of the OpenStack upstream ecosysem (e.g licenses)
2. have an identified downstream maintainer
Maintainers have to
1. provides packages that complies with Fedora packaging guidelines minus
exceptions granted by the RDO team [1]
2. commit to fix tickets reported on RDO bug tracker
3. fix FTBFS[2] in stable and master branches
4. commit to integrate and maintain their project in RDO CI
5. agree to license packaging under the MIT license (default) or any approved
license by Fedora Legal.
As long as all these conditions are respected, any project is welcome under
RDO :)
If everyone agrees, we will publish these guidelines on our website.
Regards,
H.
[1] RDO team to be understood as the community behind the maintenance of RDO,
not RDO Engineering which is an internal team from Red Hat.
[2] Fail to Build From Source
8 years, 7 months
[Rdo-list] Proposal: switch delorean to f22
by Matthias Runge
Hello,
this was discussed briefly on irc today. The question was mainly, under
the light of python3 sub-packages coming in, we'd need either to
backport patches to f21 or to do something else.
With f23 in sight, we should switch from f21 to f22 as base distro for
delorean.
Thoughts on that? We shipped kilo via RDO on top of f22, and liberty
will probably be shipped as additional repo to f23.
IMHO it would be honest and catch most issues, if we would be basing on
f23, but that might be a bit adventurous?
Matthias
8 years, 7 months
