[rdo-list] OVS 2.7 on rdo
by Numan Siddique
I wanted to know what is the plan for moving OpenvSwitch packages to
In order to deploy OVN in tripleo, we need OVS 2.7
- for deploying all the ovn services successfully
- for having the floating ip/gateway functionality to work
Is it possible to consider moving to OVS 2.7 sooner ?
5 years, 6 months
[rdo-list] RDO Mitaka with Ceph Jewel ?
by Marianne Lombard
I have an Openstack Mitaka cloud with Ceph Hammer at work
We are planning to upgrade ceph to jewel soon but we need to wait a bit
before upgrading to Newton (or superior)
Does any of you run Mitaka with Jewel ? (especially for nova, cinder and
5 years, 7 months
[rdo-list] Verify Signature on old rpms
by Will McKeon
I know that RDO no longer supports RHEL6, but I have to use RHEL 6 and I need to use some of the packages provided by RDO. However, I also need to be able to verify those rpms were signed by RDO. Where can I find the public keys that those packages were signed with?
5 years, 7 months
[rdo-list] [Meeting] RDO meeting (2017-08-23) Minutes
by Jakub Ruzicka
#rdo: RDO meeting - 2017-08-23
Meeting started by jruzicka at 15:00:10 UTC. The full logs are
* hello everyone (jruzicka, 15:00:49)
* Pike release notes (jruzicka, 15:05:08)
* ACTION: everyone to help with Pike release notes:
* PTG video interviews (jruzicka, 15:10:08)
* quick status on pike branching (jruzicka, 15:12:59)
* We still haven't done any work towards shipping stable release of
containers (jruzicka, 15:43:02)
* The question is "who/how/where must create and publish container
images using cloudsig RPMS usable for tripleo"? (jruzicka,
* Everything .rdoproject.org (except planet?) migrated to RDO Cloud
* Chair for next meeting (jruzicka, 15:56:15)
* jpena to chair next RDO meeting (jruzicka, 15:58:20)
* open floor (jruzicka, 15:58:27)
Meeting ended at 16:01:42 UTC.
Action items, by person
* everyone to help with Pike release notes:
People present (lines said)
* jruzicka (60)
* amoralej (45)
* dmsimard (36)
* rbowen (27)
* number80 (18)
* jpena (13)
* apevec (12)
* rdogerrit (10)
* openstack (7)
* chandankumar (4)
* trown (2)
* rlandy (2)
* dprince (2)
* PagliaccisCloud (1)
* ykarel (1)
* mwhahaha (1)
* Duck (1)
* ihrachys (1)
* sfbender (1)
* openstackgerrit (1)
* adarazs (1)
Generated by `MeetBot`_ 0.1.4
5 years, 7 months
[rdo-list] [TripleO] What's the plan for shipping Pike TripleO containers ?
by David Moreau Simard
At the the last few RDO meetings , we brought up that no one
had stepped up to do the work to build and ship what ends up being
stable TripleO containers for Pike.
There was different mentions that we should bring this to the MLs but
we never did, so here it is.
TL;DR, Do we want stable TripleO containers ? Who's going to be
building and shipping them ? Where ?
>From my perspective, RDO is in kind of a weird spot:
- Technically speaking, the RDO project and community provides
packages for installers (such as TripleO) to consume
- The container images are only consumable by the TripleO project
- The tooling to build containers are included in Kolla and TripleO
which are packaged by RDO
- There has been resistance in TripleO to adopt containers that have
been built by RDO during the Pike development cycle because TripleO
should be the upstream
- Upstream projects, such as TripleO and Kolla, are already producing
and shipping containers derived from RDO to DockerHub and
The definition of done for shipping RDO releases  includes
successful testing coverage of different Packstack and TripleO
scenarios, the same scenarios that continuously run throughout the
I'll concede that the current definition of done (strangely) doesn't
include bits around packaging -- how packages are built and shipped.
It probably should and maybe this should be part of the discussion.
With my RDO community hat on, I can't help but feel that it's
important to keep RDO as agnostic, neutral and open as possible.
We have to be careful about any bias and direct or indirect special
treatment RDO might be providing to TripleO.
This ensures a fair and level playing field for other projects that
are interested in either using/consuming RDO or want to be included in
the packaging distribution.
This is what makes it easier for RDO to "grow": not just in terms of
packages and contributors but in mind and market share.
RDO allows operators deploy their OpenStack clouds with vanilla
packages for Red Hat based distributions, no matter their software,
hardware, hypervisor, drivers, backends and installer preferences.
Now, back with my TripleO hat on, someone has to do the work.
If we want to build and ship containers to DockerHub, we can do that
already and automatically through periodic builds.
The role that we have been using to build containers in RDO supports
pushing to any registry, including DockerHub.
If we want to build and ship containers to the CentOS official
registry, "registry.centos.org", it's more work .
The container pipeline runs from Jenkins and builds Dockerfiles out of
pseudo dist-git repositories.
We would need to:
- Adapt the tooling that we have to generate only Dockerfiles (~trivial)
- Push them out in an organized fashion
- Explicitly define the dependency and build order of the containers
It's probably also worth asking if we want to be shipping stable
containers at all ? Who will be the users of those stable containers ?
The tooling to build containers is included in (stable) packages
provided by RDO, we have packages for Kolla and TripleO.
Users will already be pushing containers to the TripleO undercloud
registry, perhaps they could be expected to build the containers as
Let's discuss and figure out the plan moving forward.
David Moreau Simard
Senior Software Engineer | OpenStack RDO
dmsimard = [irc, github, twitter]
5 years, 7 months
[rdo-list] [TrileO] Overcloud is stuck at network deployment step
by Tong Liu
My overcloud deployment is stuck at NetworkDeployment step. I login to the overcloud controller and watch the /var/log/messages. It seems os-refresh config is running a loop after failure. Does any one see similar issue?
Setup: OpenStack Platform 10 + Rhel 7.3
/var/log/messages log on controller
Aug 29 23:38:54 overcloud-controller-0 os-collect-config: [2017-08-29 23:38:54,875] (os-refresh-config) [ERROR] during configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/configur e.d']' returned non-zero exit status 1] Aug 29 23:38:54 overcloud-controller-0 os-collect-config: [2017-08-29 23:38:54,876] (os-refresh-config) [ERROR] Aborting... Aug 29 23:38:54 overcloud-controller-0 os-collect-config: Command failed, will not cache new data. Command 'os-refresh-config --timeout 14400' returned non-zero exit status 1 Aug 29 23:38:54 overcloud-controller-0 os-collect-config: Sleeping 1.00 seconds before re-exec. Aug 29 23:38:56 overcloud-controller-0 os-collect-config: /var/lib/os-collect-config/local-data not found. Skipping Aug 29 23:38:56 overcloud-controller-0 os-collect-config: No local metadata found (['/var/lib/os-collect-config/local-data']) Aug 29 23:38:57 overcloud-controller-0 os-collect-config: [2017-08-29 23:38:57,053] (os-refresh-config) [INFO] Starting phase pre-configure Aug 29 23:38:57 overcloud-controller-0 os-collect-config: dib-run-parts Tue Aug 29 23:38:57 EDT 2017 Running /usr/libexec/os-refresh-config/pre-configure.d/06-rhel-registration Aug 29 23:39:00 overcloud-controller-0 os-collect-config: WARNING: Support for registering with a username and password is deprecated. Aug 29 23:39:00 overcloud-controller-0 os-collect-config: Please use activation keys instead. See the README for more information. Aug 29 23:39:00 overcloud-controller-0 os-collect-config: WARNING: only 'portal', 'satellite', and 'disable' are valid values for REG_METHOD. Aug 29 23:39:00 overcloud-controller-0 os-collect-config: dib-run-parts Tue Aug 29 23:39:00 EDT 2017 06-rhel-registration completed
5 years, 7 months