August 2017 - dev - Rdo List Archives

by Numan Siddique

Hello Everyone, I wanted to know what is the plan for moving OpenvSwitch packages to version 2.7. 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 ? Thanks Numan

8 years, 1 month

2
15
0 / 0

[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 glance) Thanks Marianne

8 years, 1 month

4
5
0 / 0

[rdo-list] Verify Signature on old rpms

by Will McKeon

Hello, 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? Thanks, Will William McKeon wmckeon(a)circadence.com

8 years, 1 month

2
1
0 / 0

[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 available athttp://eavesdrop.openstack.org/meetings/rdo_meeting___2017_08_23/2017/r... . Meeting summary --------------- * hello everyone (jruzicka, 15:00:49) * Pike release notes (jruzicka, 15:05:08) * LINK: https://github.com/redhat-openstack/website/blob/master/source/blog/2017-... (rbowen, 15:05:12) * ACTION: everyone to help with Pike release notes: https://github.com/redhat-openstack/website/blob/master/source/blog/2017-... (jruzicka, 15:07:01) * PTG video interviews (jruzicka, 15:10:08) * LINK: https://docs.google.com/spreadsheets/d/1KNHuo9Yb5kbjZAYGQ_PAo-YFndD8QTdaK... (rbowen, 15:10:24) * quick status on pike branching (jruzicka, 15:12:59) * LINK: https://review.rdoproject.org/r/#/q/topic:pike-branching+status:open (apevec, 15:13:49) * LINK: https://review.rdoproject.org/etherpad/p/pike-release-preparation (amoralej, 15:14:04) * 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, 15:47:31) * Everything .rdoproject.org (except planet?) migrated to RDO Cloud (jruzicka, 15:50:19) * 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 ----------------------- * openstack * everyone to help with Pike release notes: https://github.com/redhat-openstack/website/blob/master/source/blog/2017-... 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

8 years, 1 month

1
0
0 / 0

[rdo-list] [TripleO] Two bare metal machines for the control and compute

by Mark Hamzy

I'm trying to configure TripleO for an environment using two bare metal machines for the control and compute. What is the correct way to do this? https://fedoraproject.org/wiki/User:Hamzy/TripleO_mixed_undercloud_overcl... I'm guessing that network_gateway and 192.168.24.0 needs to be connected somehow... -- Mark You must be the change you wish to see in the world. -- Mahatma Gandhi Never let the future disturb you. You will meet it, if you have to, with the same weapons of reason which today arm you against the present. -- Marcus Aurelius

8 years, 1 month

2
6
0 / 0

[rdo-list] [TripleO] What's the plan for shipping Pike TripleO containers ?

by David Moreau Simard

Hi, At the the last few RDO meetings [1][2][3], 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 tarballs.openstack.org The definition of done for shipping RDO releases [4] includes successful testing coverage of different Packstack and TripleO scenarios, the same scenarios that continuously run throughout the development cycle. 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 [5]. 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 (complicated) 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 well ? Let's discuss and figure out the plan moving forward. Thanks, [1]: http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_08_09/2017/rdo... [2]: http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_08_16/2017/rdo... [3]: http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_08_23/2017/rdo... [4]: https://www.rdoproject.org/blog/2016/05/technical-definition-of-done/ [5]: https://wiki.centos.org/ContainerPipeline David Moreau Simard Senior Software Engineer | OpenStack RDO dmsimard = [irc, github, twitter]

8 years, 1 month

2
1
0 / 0

[rdo-list] [TrileO] Overcloud is stuck at network deployment step

by Tong Liu

Hi, 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 Thanks, Tong

8 years, 1 month

1
0
0 / 0

[rdo-list] [Minutes] RDO Office Hour - 2017-08-29

by Chandan kumar

================================== #rdo: RDO Office Hour - 2017-08-29 ================================== Meeting started by chandankumar at 13:31:05 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_office_hour___2017_08_29/2017... . Meeting summary --------------- * Roll Call (chandankumar, 13:31:32) * LINK: https://copr.fedorainfracloud.org/coprs/hguemar/rdo-packager/package/mock... (number80, 14:25:37) * LINK: https://review.rdoproject.org/r/#/c/9051/2 (number80, 14:27:54) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1435191 (chandankumar, 14:48:59) * we have cleanup RDO-Pike package review queue https://bugzilla.redhat.com/show_bug.cgi?id=1427510 (chandankumar, 15:01:53) * next week [05-09-2017] Newton RDO Bugs Training (chandankumar, 15:04:09) * RDO Pike New package list created https://etherpad.openstack.org/p/RDO-Pike-New-Packages (chandankumar, 15:31:20) Meeting ended at 15:31:28 UTC. People present (lines said) --------------------------- * chandankumar (63) * number80 (36) * dmsimard (22) * rdogerrit (19) * openstack (15) * rbowen (10) * apevec (6) * jpena (5) * bnemec (3) * pradk (3) * sshnaidm (2) * jrist (2) * mfedosin (2) * egonzalez (1) * ykarel (1) * trown (1) * adarazs (1) Generated by `MeetBot`_ 0.1.4

8 years, 2 months

1
0
0 / 0

[rdo-list] New packages in RDO Pike (writing release notes)

by Rich Bowen

As part of writing the RDO Pike release announcement, we're compiling a list of new packages. That list is here: https://etherpad.openstack.org/p/RDO-Pike-New-Packages If you know of new packages/libraries/whatever that will be in this release, please have a look at that list and check to see if anything is missing or inaccurate. Thanks. -- Rich Bowen - rbowen(a)redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity

8 years, 2 months

1
0
0 / 0

[rdo-list] RDO-Infra Weekly Scrum Recap:

by Arx Cruz

Greetings All, Links to the RDO-Infra team scrum [1] and recording [2] from this week's meeting are below. Highlights: - Current known issues affecting CI - Cirros website was down - Use pip to install delorean instead of git clone - 3 node status - All patches merged and running on quickstart - multinic status - Reviews still in merge conflict (trown) [3] - tempest status - scenario001 - Almost all the patches are merged to have it working with the ceilometer integration tests [4] - scenario004 - Need to find a test that doesn't relay on cinder - OVB devmode status [5] - Promotion status - http://rhos-release.virt.bos.redhat.com:3030/rhosp RED - Master seems to be affected by [6] - Pike (and probably the rest) is affected by the Cirros bug Announcements: - Internal (rh) approval granted for creation of RDO Cloud tenant for OSP puddles, WIP (dates TBD), mburns driving. \o/ happy days [1] - https://review.rdoproject.org/etherpad/p/rdo-infra-scrum [2] - https://bluejeans.com/s/Ek_qr/ [3] - https://review.openstack.org/#/c/476704/ - https://review.openstack.org/#/c/476708/ - https://review.openstack.org/#/c/480697/ [4] - https://trello.com/c/ezKfRO7v/313-debug-and-identify-why-telemetry-integr... [5] - Caching container registry is not working - https://review.openstack.org/#/c/498139/ - Add DockerPuppetProcessCount defaults to 3 - https://bugs.launchpad.net/tripleo/+bug/1689556 - https://review.openstack.org/#/c/493695/ [6] - https://bugs.launchpad.net/tripleo/+bug/1669110 Kind regards, Arx Cruz

8 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

dev August 2017