April 2018 - dev - Rdo List Archives

Re: [rdo-dev] Strategy on packaging external dependencies in RDO + include Ansible in RDO

by Alan Pevec

On Fri, Mar 30, 2018 at 4:31 AM, Sam Doran <sdoran(a)redhat.com> wrote: >> Ansible RPMs are already there >> http://releases.ansible.com/ansible/rpm/release/epel-7-x86_64/ but they >> depend on EPEL for additional deps. > > Ansible RPMs have always been there. I don't believe they depend on anything > in EPEL. You are correct, I had some stale info or mixed it up with something else. Here is yum install output on an empty CentOS7 machine: Installing: ansible noarch 2.4.3.0-1.el7.ans /ansible-2.4.3.0-1.el7.ans.noarch Installing for dependencies: PyYAML x86_64 3.10-11.el7 base libyaml x86_64 0.1.4-11.el7_0 base python-babel noarch 0.9.6-8.el7 base python-cffi x86_64 1.6.0-5.el7 base python-enum34 noarch 1.0.4-1.el7 base python-idna noarch 2.4-1.el7 base python-ipaddress noarch 1.0.16-2.el7 base python-jinja2 noarch 2.7.2-2.el7 base python-markupsafe x86_64 0.11-10.el7 base python-paramiko noarch 2.1.1-4.el7 extras python-ply noarch 3.4-11.el7 base python-pycparser noarch 2.14-1.el7 base python-setuptools noarch 0.9.8-7.el7 base python2-cryptography x86_64 1.7.2-1.el7_4.1 updates python2-pyasn1 noarch 0.1.9-7.el7 base sshpass x86_64 1.06-2.el7 extras > sshpass and paramiko come from Extras, python2-cryptography comes from > updates. My concern is that if those were included in Extras for Ansible, they would be removed from Extras together with ansible. > I'm not sure if any of that is helpful since you mentioned it would need to > be built by the appropriate SIG anyway. Yes, ideally we would be able to get ConfigMgmt SIG going, in the meantime other SIGs are rebuilding on their own e.g. Virt SIG/oVirt did 2.4.3 http://cbs.centos.org/koji/buildinfo?buildID=21591 As a quickfix, we could also temporarily push this to RDO deps repo, until we have rest of the plan ready. >> BTW ideal approach would be to insert OpenStack use-cases into Ansible >> upstream CI and make it voting, this could become reality with cross-project >> CI efforts lead by openstack-infra. With that, Ansible master would never >> break us! > > I don't entirely follow this, but I think it sounds like what I proposed > above: having OpenStack test the devel branch of Ansible so Ansible > Engineering can get feedback quickly if things are broken prior to a > release. I know some of the OpenStack infra folks, and the networking team > within Ansible has been doing a lot of work with them with Zuul for > distributed CI. Myself and Ricardo Cruz on the Ansible side are very > interested in hooking up more testing of Ansible as it relates to OpenStack > using Zuul run by OpenStack Infra. Ricki and I talked about this a bunch at > the PTG but have been working on other things since we got back. Yes, above was forward-looking CD world where, given infinite CI resources, everything is tested pre-commit across collaborating projects. Definitely trunk RPMs from devel branch are the step in that direction, progression scale is: no testing, push the latest release, hope for the best -> CI with latest release -> CI with devel branch -> CI pre-commit Cheers, Alan

3 years, 10 months

3
2
0 / 0

RDO Rocky Test Days Milestone ONE Next Week

by Rain Leander

Hello everyone! Bust out your spoons because we're about to test the first batch of Rocky [road] ice cream! Or, y'know, the first Rocky OpenStack milestone. On 03 and 04 May, next week Thursday and Friday, we'll have our first milestone test days for Rocky OpenStack. We would love to get as wide participation in the RDO Test Days from our global team as possible! We're looking for developers, users, operators, quality engineers, writers, and, yes, YOU. If you're reading this, we want your help! Let's set new records on the amount of participants! The amount of tickets! The amount of feedback and questions and NOTES! Oh, my. But, seriously. I know that everyone has Important Stuff To Do but taking a few hours or a day to give things a run through at various points in the RDO cycle will benefit everyone. Not only will this help identify issues early in the development process, but you can be the one of the first to cut your teeth on the latest versions of your favorite deployment methods like TripleO, PackStack, and Kolla. So, please consider taking a break from your normal duties and spending at least a few hours with us in #rdo on Freenode. See you NEXT WEEK! -- K Rain Leander OpenStack Community Liaison Open Source and Standards Team https://www.rdoproject.org/ http://community.redhat.com

4 years

1
3
0 / 0

[Fedocal] Reminder meeting : RDO meeting

by hguemar＠fedoraproject.org

Dear all, You are kindly invited to the meeting: RDO meeting on 2018-05-02 from 15:00:00 to 16:00:00 UTC At rdo(a)irc.freenode.net The meeting will be about: RDO IRC meeting [Agenda at https://etherpad.openstack.org/p/RDO-Meeting ](https://etherpad.openstack.org/p/RDO-Meeting) Every Wednesday on #rdo on Freenode IRC Source: https://apps.fedoraproject.org/calendar/meeting/2017/

4 years

1
0
0 / 0

[Fedocal] Reminder meeting : RDO meeting

by hguemar＠fedoraproject.org

Dear all, You are kindly invited to the meeting: RDO meeting on 2018-05-02 from 15:00:00 to 16:00:00 UTC At rdo(a)irc.freenode.net The meeting will be about: RDO IRC meeting [Agenda at https://etherpad.openstack.org/p/RDO-Meeting ](https://etherpad.openstack.org/p/RDO-Meeting) Every Wednesday on #rdo on Freenode IRC Source: https://apps.fedoraproject.org/calendar/meeting/8759/

4 years

1
0
0 / 0

[Fedocal] Reminder meeting : RDO Office Hours

by chkumar246＠gmail.com

Dear all, You are kindly invited to the meeting: RDO Office Hours on 2018-05-01 from 13:30:00 to 14:30:00 UTC The meeting will be about: The meeting will be about RDO Office Hour. Aim: To keep up with increasing participation, we'll host office hours to add more easy fixes and provide mentoring to newcomers. [Agenda at RDO Office Hour easyfixes](https://review.rdoproject.org/etherpad/p/rdo-office-hour-easyf... Source: https://apps.fedoraproject.org/calendar/meeting/6374/

4 years

1
0
0 / 0

[Meeting] RDO meeting - 2018-04-25

by Chandan kumar

============================== #rdo: RDO meeting - 2018-04-25 ============================== Meeting started by chandankumar at 15:04:54 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_04_25/2018/rdo... . Meeting summary --------------- * Test day preparation status (chandankumar, 15:06:12) * LINK: https://dashboards.rdoproject.org/rdo-dev (chandankumar, 15:09:13) * Rocky M1 RDO test day on May 03-04, 2018 (chandankumar, 15:11:17) * ACTION: chandankumar to post a blog post for M1 ROcky test day (chandankumar, 15:20:47) * backup volunteers as well as demo volunteers for Red Hat Summit and OpenStack Summit (chandankumar, 15:22:01) * LINK: https://etherpad.openstack.org/p/rdo-manageIQ-ceph-rhSummit2018 (leanderthal, 15:25:55) * LINK: https://etherpad.openstack.org/p/rdo-vancouver-summit-booth (leanderthal, 15:26:10) * stemming from tripleo-ci community meeting (chandankumar, 15:29:11) * chair for next meeting (chandankumar, 15:43:40) * ACTION: leanderthal to chair for next meeting (chandankumar, 15:44:26) * open floor (chandankumar, 15:44:41) Meeting ended at 15:48:50 UTC. Action items, by person ----------------------- * chandankumar * chandankumar to post a blog post for M1 ROcky test day * leanderthal * leanderthal to chair for next meeting People present (lines said) --------------------------- * chandankumar (51) * leanderthal (40) * myoung (14) * dmsimard (11) * amoralej (10) * openstack (9) * kashyap (7) * jpena (6) * PagliaccisCloud (2) * rdogerrit (2) * mollyk (2) * ykarel (1) * panda|ruck (1) * mjturek (1) * Duck (0) Generated by `MeetBot`_ 0.1.4 Thanks, Chandan Kumar

4 years

1
0
0 / 0

Announcing Our OSAS Ambassadors!

by Rain Leander

While I am back to work almost full time after the birth of my super sweet twinsess, I'm not QUITE travelling across the pond YET and therefore have recruited Haïkel Guémar and Molly Kepley to be the OSAS Ambassadors at OpenStack Summit Vancouver and Red Hat Summit respectively. I and the rest of the RDO community will be available on #rdo the weeks that they're covering the booths to answer any questions, concerns, and snarky comments they may have in the call of duty. However, if you're also attending one of these summits, please consider joining Haïkel [0] or Molly [1] for a shift or two and / or to demo something you've recently done. Please join me in thanking them offline for their awesomeness! [0] https://etherpad.openstack.org/p/rdo-vancouver-summit-booth [1] https://etherpad.openstack.org/p/rdo-manageIQ-ceph-rhSummit2018 -- K Rain Leander OpenStack Community Liaison Open Source and Standards Team https://www.rdoproject.org/ http://community.redhat.com

4 years

1
0
0 / 0

Attempt to reproduce Carlos Camacho simplest deployment (controller+compute) now fails as well.

by Boris Derzhavets

Follow https://www.anstack.com/blog/2018/01/05/tripleo-quickstart-cheatsheet.html <https://www.anstack.com/blog/2018/01/05/tripleo-quickstart-cheatsheet.html> just via remote connection to VIRTHOST (32 GB) from F27 wks . Overcloud deployment fails with error :- ---------------------------- overcloud_deploy.log ---------------------------- 2018-02-16 19:02:51 | 2018-02-16 19:02:39Z [overcloud.Compute.0]: CREATE_COMPLETE Stack CREATE completed successfully 2018-02-16 19:02:51 | 2018-02-16 19:02:40Z [overcloud.Compute.0]: CREATE_COMPLETE state changed 2018-02-16 19:02:51 | 2018-02-16 19:02:40Z [overcloud.Compute]: UPDATE_COMPLETE Stack UPDATE completed successfully 2018-02-16 19:02:51 | 2018-02-16 19:02:40Z [overcloud.Controller.0.ControllerExtraConfigPre]: CREATE_COMPLETE state changed 2018-02-16 19:02:51 | 2018-02-16 19:02:40Z [overcloud.Controller.0.NodeExtraConfig]: CREATE_IN_PROGRESS state changed 2018-02-16 19:02:51 | 2018-02-16 19:02:41Z [overcloud.Compute]: CREATE_COMPLETE state changed 2018-02-16 19:02:51 | 2018-02-16 19:02:42Z [overcloud.ComputeServers]: CREATE_IN_PROGRESS state changed 2018-02-16 19:02:51 | 2018-02-16 19:02:42Z [overcloud.ComputeServers]: CREATE_COMPLETE state changed 2018-02-16 19:02:51 | 2018-02-16 19:02:42Z [overcloud]: CREATE_FAILED list index out of range 2018-02-16 19:02:51 | 2018-02-16 19:02:42Z [overcloud.Controller.0.NodeExtraConfig]: CREATE_COMPLETE state changed 2018-02-16 19:02:51 | 2018-02-16 19:02:51 | Stack overcloud CREATE_FAILED 2018-02-16 19:02:51 | 2018-02-16 19:02:51 | + status_code=1 2018-02-16 19:02:51 | + openstack stack list 2018-02-16 19:02:51 | + grep -q overcloud 2018-02-16 19:02:55 | + openstack stack list 2018-02-16 19:02:55 | + grep -Eq '(CREATE|UPDATE)_COMPLETE' 2018-02-16 19:02:57 | + openstack stack failures list overcloud --long 2018-02-16 19:03:01 | ++ openstack stack resource list --nested-depth 5 overcloud 2018-02-16 19:03:01 | ++ grep FAILED 2018-02-16 19:03:01 | ++ grep 'StructuredDeployment ' 2018-02-16 19:03:01 | ++ cut -d '|' -f3 2018-02-16 19:03:16 | + exit 1 Thanks Boris.

4 years

5
9
0 / 0

[Fedocal] Reminder meeting : RDO meeting

by hguemar＠fedoraproject.org

Dear all, You are kindly invited to the meeting: RDO meeting on 2018-04-25 from 15:00:00 to 16:00:00 UTC At rdo(a)irc.freenode.net The meeting will be about: RDO IRC meeting [Agenda at https://etherpad.openstack.org/p/RDO-Meeting ](https://etherpad.openstack.org/p/RDO-Meeting) Every Wednesday on #rdo on Freenode IRC Source: https://apps.fedoraproject.org/calendar/meeting/8759/

4 years

1
0
0 / 0

[Fedocal] Reminder meeting : RDO meeting

by hguemar＠fedoraproject.org

Dear all, You are kindly invited to the meeting: RDO meeting on 2018-04-25 from 15:00:00 to 16:00:00 UTC At rdo(a)irc.freenode.net The meeting will be about: RDO IRC meeting [Agenda at https://etherpad.openstack.org/p/RDO-Meeting ](https://etherpad.openstack.org/p/RDO-Meeting) Every Wednesday on #rdo on Freenode IRC Source: https://apps.fedoraproject.org/calendar/meeting/2017/

4 years

1
0
0 / 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

dev April 2018