As you're probably aware, there is an OpenStack rpm-packaging project , where the RDO community has been collaborating with people from other rpm-based distributions. We have been successful in reusing some tools created by that project , but we've never been able to reuse the spec file templates generated by the project, besides openstack-macros and some python 3 tests done during the Rocky cycle.
As a community, we need to decide what we want our involvement in the project to be:
- Only get involved in the tooling side, if we have no plans to reuse the spec templates in the future.
- Try a deeper integration with the specs.
- Other alternatives?
Each option will carry its own consequences, e.g. if we stop contributing to the spec templates we should stop the 3rd party CI jobs and VMs that support them.
Please contribute to the discussion on this thread. We will vote for a final decision during the next RDO Community meeting on September 5th.
 - https://github.com/openstack/rpm-packaging
 - https://github.com/openstack/pymod2pkg
 - https://github.com/openstack/renderspec
#rdo: RDO meeting - 2018-08-29
Meeting started by jpena at 15:01:17 UTC. The full logs are available
* roll call (jpena, 15:01:31)
* Policy for abandoning packages proposal (jpena, 15:03:03)
* ACTION: number80 create a thread about abandoning packages policy on
the rdo-dev list (number80, 15:07:51)
* Release preparations (jpena, 15:21:02)
* LINK: https://www.rdoproject.org/rdo/release-checklist/
* LINK: https://etherpad.openstack.org/p/rdo-rocky-release
* ACTION: all help with the release announcement (number80, 15:25:33)
* We have repositories ready (all 3 platforms) and same for
centos-release-openstack-rocky (leanderthal, 15:27:02)
* LINK: https://releases.openstack.org/rocky/schedule.html#r-release
* Relationship with rpm-packaging project (jpena, 15:40:00)
* ACTION: jpena will start discussion on rdo-dev list about
rpm-packaging involvement, with a deadline to decide (jpena,
* Patch for introducing job for ppc64le container builds (jpena,
* LINK: https://review.rdoproject.org/r/#/c/15978/ (baha, 15:50:24)
* ACTION: CI reviewers to check
https://review.rdoproject.org/r/#/c/15978/ (jpena, 15:52:18)
* Hardware for building octavia-tempest-test-golang package (jpena,
thread here for those curious (mjturek, 15:55:52)
* ACTION: jpena to extract octavia-tempest-test-golang to a separate
dep (jpena, 16:04:02)
* propose to shift test days to M1 / M3 instead of M2 / GA (jpena,
* AGREED: test on M1 / M3 instead and cancel rocky test days GA next
week (jpena, 16:09:12)
* open floor (jpena, 16:09:21)
Meeting ended at 16:11:05 UTC.
Action items, by person
* jpena will start discussion on rdo-dev list about rpm-packaging
involvement, with a deadline to decide
* jpena to extract octavia-tempest-test-golang to a separate dep
* number80 create a thread about abandoning packages policy on the
* all help with the release announcement
* CI reviewers to check https://review.rdoproject.org/r/#/c/15978/
People present (lines said)
* apevec (61)
* jpena (57)
* number80 (38)
* leanderthal (38)
* ykarel (20)
* mjturek (19)
* jruzicka (9)
* openstack (7)
* baha (5)
* rdogerrit (4)
Generated by `MeetBot`_ 0.1.4
According to the information provided by Swift maintainers, package
openstack-swift-plugin-swift3 (upstream repo swift3) is being retired from
RDO and will not be in repositories since Rocky release .
According to upstream info swift3 has been imported into Swift's codebase
as the "s3api" middleware. Swift3 development is now frozen and all new
patches should go to s3api middleware .
Users using swift3 may need to adapt their configuration to this change as
documented in upstream swift documentation.
I've been working alongside Mike Turek to try to get Triple O containers
building on ppc64le. We're currently hung up on the
python-octavia-tests-tempest-golang package from the delorean repo. If
you go take a look at the repo itself , you'll see that the only
packages being published exclusively for x86 are the octavia ones.
The openstack-queens repo  offers all of the octavia packages built
for ppc64le, so there's definitely not an x86 requirement, but their
version does not match that required for the Triple O containers. We
need someone to build the octavia packages (especially
python-octavia-tests-tempest-golang) for ppc64le in the delorean
repository to stop versioning conflicts.
 - http://mirror.centos.org/altarch/7/cloud/ppc64le/openstack-queens/
I'm working on an article/tutorial to explain how to use InfraRed with
Distributed-CI. I focus on OSP13 for this first version, but the content
is definitely relevant for RDO since DCI support both.
Any objection if I use https://blogs.rdoproject.org/ to publish it? I
tried to reset my password but I end-ed up with the following error:
The email could not be sent.
Possible reason: your host may have disabled the mail() function.
Can someone reset it for me?
Gonéri Le Bouder