From ayoung at redhat.com Thu Sep 1 01:51:34 2016 From: ayoung at redhat.com (Adam Young) Date: Wed, 31 Aug 2016 21:51:34 -0400 Subject: [rdo-list] Is Keystone/Identity-v3 supported by RDO Packstack? Multi-node swift --answer-file? In-Reply-To: References: <187458073.6327797.1472229179556.JavaMail.zimbra@redhat.com> Message-ID: <89e654f1-261f-3967-a998-5ee92b69c273@redhat.com> On 08/31/2016 02:03 PM, Boris Derzhavets wrote: > > Please, see detailed instructions here :- > > > Backport upstream commits to stable RDO Mitaka release && > Deployments with Keystone API V3 > > http://bderzhavets.blogspot.ru/2016/05/backport-upstream-commits-to-stable-rdo.html > > > > Xen Virtualization on Linux and Solaris: Backport upstream commits to > stable RDO Mitaka release && Deployments with Keystone API V3 > > bderzhavets.blogspot.ru > > > Boris. > ------------------------------------------------------------------------ > *From:* rdo-list-bounces at redhat.com on > behalf of Taisto Qvist > *Sent:* Wednesday, August 31, 2016 6:51:55 PM > *To:* Javier Pena > *Cc:* rdo-list > *Subject:* Re: [rdo-list] Is Keystone/Identity-v3 supported by RDO > Packstack? Multi-node swift --answer-file? > Thanks for the tips everyone. > > I found > https://www.linux.com/blog/attempt-set-rdo-mitaka-any-given-time-delorean-trunks, > and but that also failed with idv3, but on heat issues instead. > > I am unfortunately completely lost/confused/overwhelmed with all the > different git/repository information found in different places, and > building my own RPMs feels way to complicated as someone linked to. > > So I'll just clearly demonstrate my NooB-ness, by asking: > > If I follow the instructions on > "https://www.rdoproject.org/install/quickstart/", how do I modify them > to update my packstack-* to use the newer modules mentioned below? > > Regards > Taisto We did an Anisble based Proof of concept with it last summer: https://github.com/admiyo/rippowam/tree/master/roles/packstack Went far beyond just V3, to include Kerberos and TLS everywhere. But it is do-able. > > > > 2016-08-26 18:32 GMT+02:00 Javier Pena >: > > > > ----- Original Message ----- > > Fairly certain Cinder is a known problem against v3 in Packstack [1] > > but I don't have the details. > > > > [1]: > > > https://github.com/openstack/packstack/blob/master/releasenotes/notes/keystone-v3-note-065b6302b49285f3.yaml > > > > > We had a patch to fix that merged in Mitaka some time ago [1], > which depended on a puppet-cinder patch [2]. We have not yet > released a new package to the CBS repos, but you could try > updating your openstack-packstack, openstack-packstack-puppet and > openstack-puppet-modules using the packages from RDO stable/mitaka > Trunk [3]. > > Regards, > Javier > > [1] - https://review.openstack.org/323690 > > [2] - https://review.openstack.org/320956 > > [3] - > http://buildlogs.centos.org/centos/7/cloud/x86_64/rdo-trunk-mitaka-tested/ > > > > > David Moreau Simard > > Senior Software Engineer | Openstack RDO > > > > dmsimard = [irc, github, twitter] > > > > > > On Fri, Aug 26, 2016 at 11:57 AM, Taisto Qvist > > > > wrote: > > > Hi folks, > > > > > > I've managed to create a fairly well working packstack-answer > file, that I > > > used for liberty installations, with a 4-multi-node setup, > eventually > > > handling nested kvm, live-migration, LBAAS, etc, so I am quite > happy with > > > that. > > > > > > Now, my aim is Identity v3. From the packstack answer-file, it > seems > > > supported, but I cant get it to work. I couldnt get it to work > with > > > liberty, > > > and now testing with Mitaka, it still doesnt work, failing on: > > > > > > ERROR : Error appeared during Puppet run: 10.9.24.100_cinder.pp > > > Error: Could not prefetch cinder_type provider 'openstack': > Execution of > > > '/usr/bin/openstack volume type list --quiet --format csv > --long' returned > > > 1: Expecting to find domain in project - the server could not > comply with > > > the request since it is either malformed or otherwise > incorrect. The client > > > is assumed to be in error. (HTTP 400) (Request-ID: > > > req-d8cccfb9-c060-4cdd-867d-603bf70ebf24) > > > > > > > > > > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at hotmail.com Thu Sep 1 08:07:50 2016 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Thu, 1 Sep 2016 08:07:50 +0000 Subject: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI In-Reply-To: References: <0c25e0c3-5d51-05fb-f628-173010314285@redhat.com> , Message-ID: Looking at quickstart.sh I see :- : ${OPT_BOOTSTRAP:=0} : ${OPT_CLEAN:=0} : ${OPT_PLAYBOOK:=quickstart.yml} : ${OPT_RELEASE:=mitaka} : ${OPT_RETAIN_INVENTORY_FILE:=0} : ${OPT_SYSTEM_PACKAGES:=0} : ${OPT_TAGS:=$DEFAULT_OPT_TAGS} : ${OPT_TEARDOWN:=nodes} : ${OPT_WORKDIR:=$HOME/.quickstart} . . . . . echo " -R, --release OpenStack release to deploy (default=$OPT_RELEASE)" <== line 147 It clearly shows that default release is Mitaka Would you like to test Newton then command line should look like :- $ bash quickstart.sh --config ./ha.yml --release newton $VIRTHOST Boris. ________________________________ From: Raoul Scarazzini Sent: Wednesday, August 24, 2016 5:25 PM To: Boris Derzhavets; Wesley Hayutin; Attila Darazs Cc: rdo-list Subject: Re: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI On 24/08/2016 14:21, Boris Derzhavets wrote: [...] > ======================================================================== > Addressing your requests > ======================================================================== > [boris at fedora24wks tripleo-quickstart]$ cat ./config/general_config/ha.yml [...] > $ bash quickstart.sh --config ./config/general_config/ha.yml $VIRTHOST > EXIT ( undrecloud has been built ) Not only. At this point everything should be built. [...] > [root at undercloud stack]# cd /etc/yum.repos.d > [root at undercloud yum.repos.d]# cat delorean-deps.repo > [delorean-mitaka-testing] > name=dlrn-mitaka-testing > baseurl=http://buildlogs.centos.org/centos/7/cloud/$basearch/openstack-mitaka/ > enabled=1 > gpgcheck=0 > priority=2 > [root at undercloud yum.repos.d]# cat delorean.repo > [delorean] > name=delorean-openstack-rally-3909299306233247d547bad265a1adb78adfb3d4 > baseurl=http://trunk.rdoproject.org/centos7-mitaka/39/09/3909299306233247d547bad265a1adb78adfb3d4_4e6dfa3c > enabled=1 > gpgcheck=0 This sounds really strange, since you should get master repo (so Newton, not Mitaka) while using quickstart without specifying --release. How long ago did you downloaded the quickstart git repo? Can you redeploy everything from scratch with the latest pull from quickstart's git repo? -- Raoul Scarazzini rasca at redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at hotmail.com Thu Sep 1 08:50:40 2016 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Thu, 1 Sep 2016 08:50:40 +0000 Subject: [rdo-list] Is Keystone/Identity-v3 supported by RDO Packstack? Multi-node swift --answer-file? In-Reply-To: <89e654f1-261f-3967-a998-5ee92b69c273@redhat.com> References: <187458073.6327797.1472229179556.JavaMail.zimbra@redhat.com> , <89e654f1-261f-3967-a998-5ee92b69c273@redhat.com> Message-ID: ________________________________ From: rdo-list-bounces at redhat.com on behalf of Adam Young Sent: Thursday, September 1, 2016 4:51 AM To: rdo-list at redhat.com Subject: Re: [rdo-list] Is Keystone/Identity-v3 supported by RDO Packstack? Multi-node swift --answer-file? On 08/31/2016 02:03 PM, Boris Derzhavets wrote: Please, see detailed instructions here :- Backport upstream commits to stable RDO Mitaka release && Deployments with Keystone API V3 http://bderzhavets.blogspot.ru/2016/05/backport-upstream-commits-to-stable-rdo.html [https://4.bp.blogspot.com/-8KYSnMrQGmo/V0LYnpQFOkI/AAAAAAAAGrE/0WGJJh8kLeQfmCh4QsLnGKgJ7WfN_4-EQCLcB/w1200-h630-p-nu/Screenshot%2Bfrom%2B2016-05-23%2B12-48-25.png] Xen Virtualization on Linux and Solaris: Backport upstream commits to stable RDO Mitaka release && Deployments with Keystone API V3 bderzhavets.blogspot.ru > Would you like to see moderated version of post above :- https://www.linux.com/blog/backport-upstream-commits-stable-rdo-mitaka-release-deployments-keystone-api-v3 Backport upstream commits to stable RDO Mitaka release ... www.linux.com Posting bellow is written with intend to avoid waiting until "koji" build will appear in updates repo of stable RDO Mitaka release, what might take a couple of months ... I believe that RDO package maintainers are supposed to perform patching (done locally in my posting to Linux.com) and make this back ports to official RDO Mitaka repos, to avoid compromising RDO QuickStart Page. By some reasons it didn't happen. > Boris. ________________________________ From: rdo-list-bounces at redhat.com on behalf of Taisto Qvist Sent: Wednesday, August 31, 2016 6:51:55 PM To: Javier Pena Cc: rdo-list Subject: Re: [rdo-list] Is Keystone/Identity-v3 supported by RDO Packstack? Multi-node swift --answer-file? Thanks for the tips everyone. I found https://www.linux.com/blog/attempt-set-rdo-mitaka-any-given-time-delorean-trunks, and but that also failed with idv3, but on heat issues instead. I am unfortunately completely lost/confused/overwhelmed with all the different git/repository information found in different places, and building my own RPMs feels way to complicated as someone linked to. So I'll just clearly demonstrate my NooB-ness, by asking: If I follow the instructions on "https://www.rdoproject.org/install/quickstart/", how do I modify them to update my packstack-* to use the newer modules mentioned below? Regards Taisto We did an Anisble based Proof of concept with it last summer: https://github.com/admiyo/rippowam/tree/master/roles/packstack Went far beyond just V3, to include Kerberos and TLS everywhere. But it is do-able. 2016-08-26 18:32 GMT+02:00 Javier Pena >: ----- Original Message ----- > Fairly certain Cinder is a known problem against v3 in Packstack [1] > but I don't have the details. > > [1]: > https://github.com/openstack/packstack/blob/master/releasenotes/notes/keystone-v3-note-065b6302b49285f3.yaml > We had a patch to fix that merged in Mitaka some time ago [1], which depended on a puppet-cinder patch [2]. We have not yet released a new package to the CBS repos, but you could try updating your openstack-packstack, openstack-packstack-puppet and openstack-puppet-modules using the packages from RDO stable/mitaka Trunk [3]. Regards, Javier [1] - https://review.openstack.org/323690 [2] - https://review.openstack.org/320956 [3] - http://buildlogs.centos.org/centos/7/cloud/x86_64/rdo-trunk-mitaka-tested/ > David Moreau Simard > Senior Software Engineer | Openstack RDO > > dmsimard = [irc, github, twitter] > > > On Fri, Aug 26, 2016 at 11:57 AM, Taisto Qvist > > wrote: > > Hi folks, > > > > I've managed to create a fairly well working packstack-answer file, that I > > used for liberty installations, with a 4-multi-node setup, eventually > > handling nested kvm, live-migration, LBAAS, etc, so I am quite happy with > > that. > > > > Now, my aim is Identity v3. From the packstack answer-file, it seems > > supported, but I cant get it to work. I couldnt get it to work with > > liberty, > > and now testing with Mitaka, it still doesnt work, failing on: > > > > ERROR : Error appeared during Puppet run: 10.9.24.100_cinder.pp > > Error: Could not prefetch cinder_type provider 'openstack': Execution of > > '/usr/bin/openstack volume type list --quiet --format csv --long' returned > > 1: Expecting to find domain in project - the server could not comply with > > the request since it is either malformed or otherwise incorrect. The client > > is assumed to be in error. (HTTP 400) (Request-ID: > > req-d8cccfb9-c060-4cdd-867d-603bf70ebf24) > > > > _______________________________________________ rdo-list mailing list rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscribe at redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at hotmail.com Thu Sep 1 11:11:21 2016 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Thu, 1 Sep 2016 11:11:21 +0000 Subject: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI In-Reply-To: References: <0c25e0c3-5d51-05fb-f628-173010314285@redhat.com> , , Message-ID: I belive four options are available at the moment [boris at fedora24wks tripleo-quickstart]$ cd ./config/release/ [boris at fedora24wks release]$ ls -l total 16 -rw-rw-r--. 1 boris boris 363 Sep 1 13:13 liberty.yml -rw-rw-r--. 1 boris boris 248 Sep 1 13:13 master-tripleo.yml -rw-rw-r--. 1 boris boris 562 Sep 1 13:13 master.yml -rw-rw-r--. 1 boris boris 359 Sep 1 13:13 mitaka.yml [boris at fedora24wks release]$ cat mitaka.yml release: mitaka undercloud_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/mitaka/delorean/stable/undercloud.qcow2 overcloud_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/mitaka/delorean/stable/overcloud-full.tar ipa_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/mitaka/delorean/stable/ironic-python-agent.tar [boris at fedora24wks release]$ cat master.yml release: master undercloud_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/master/delorean/stable/undercloud.qcow2 overcloud_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/master/delorean/stable/overcloud-full.tar ipa_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/master/delorean/stable/ironic-python-agent.tar I have no any doubts any more that by default images are taken from mitaka.yml Testing "master" requires " --release master" in command line and would perform downloads via master.yml's URLs which are different from default ones Boris. ________________________________ From: rdo-list-bounces at redhat.com on behalf of Boris Derzhavets Sent: Thursday, September 1, 2016 11:07 AM To: Raoul Scarazzini; Wesley Hayutin; Attila Darazs Cc: rdo-list Subject: Re: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI Looking at quickstart.sh I see :- : ${OPT_BOOTSTRAP:=0} : ${OPT_CLEAN:=0} : ${OPT_PLAYBOOK:=quickstart.yml} : ${OPT_RELEASE:=mitaka} : ${OPT_RETAIN_INVENTORY_FILE:=0} : ${OPT_SYSTEM_PACKAGES:=0} : ${OPT_TAGS:=$DEFAULT_OPT_TAGS} : ${OPT_TEARDOWN:=nodes} : ${OPT_WORKDIR:=$HOME/.quickstart} . . . . . echo " -R, --release OpenStack release to deploy (default=$OPT_RELEASE)" <== line 147 It clearly shows that default release is Mitaka Would you like to test Newton then command line should look like :- $ bash quickstart.sh --config ./ha.yml --release newton $VIRTHOST Boris. ________________________________ From: Raoul Scarazzini Sent: Wednesday, August 24, 2016 5:25 PM To: Boris Derzhavets; Wesley Hayutin; Attila Darazs Cc: rdo-list Subject: Re: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI On 24/08/2016 14:21, Boris Derzhavets wrote: [...] > ======================================================================== > Addressing your requests > ======================================================================== > [boris at fedora24wks tripleo-quickstart]$ cat ./config/general_config/ha.yml [...] > $ bash quickstart.sh --config ./config/general_config/ha.yml $VIRTHOST > EXIT ( undrecloud has been built ) Not only. At this point everything should be built. [...] > [root at undercloud stack]# cd /etc/yum.repos.d > [root at undercloud yum.repos.d]# cat delorean-deps.repo > [delorean-mitaka-testing] > name=dlrn-mitaka-testing > baseurl=http://buildlogs.centos.org/centos/7/cloud/$basearch/openstack-mitaka/ > enabled=1 > gpgcheck=0 > priority=2 > [root at undercloud yum.repos.d]# cat delorean.repo > [delorean] > name=delorean-openstack-rally-3909299306233247d547bad265a1adb78adfb3d4 > baseurl=http://trunk.rdoproject.org/centos7-mitaka/39/09/3909299306233247d547bad265a1adb78adfb3d4_4e6dfa3c > enabled=1 > gpgcheck=0 This sounds really strange, since you should get master repo (so Newton, not Mitaka) while using quickstart without specifying --release. How long ago did you downloaded the quickstart git repo? Can you redeploy everything from scratch with the latest pull from quickstart's git repo? -- Raoul Scarazzini rasca at redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Thu Sep 1 18:10:32 2016 From: rbowen at redhat.com (Rich Bowen) Date: Thu, 1 Sep 2016 14:10:32 -0400 Subject: [rdo-list] BoF at OpenStack Summit Message-ID: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit this year. We're pursuing an off-site restaurant venue. Would you come? At the last few OpenStack Summit venues, we were able to secure a BoF (Birds of a Feather) meetup room during the main conference schedule for an RDO community meetup. This is not an option at this event. Due to space limitations, all BoF slots went to core projects. We are investigating an evening reservation at a nearby (hopefully one of the conference hotels) venue, in a bar/restaurant. We are sharing this with the Ceph community to limit costs. What I need to know is an idea of how many of you would attend an evening (like, right after the last conference talk session?) event at a nearby (walking distance) venue, with light snacks/beverages, where we did an hour-long RDO Community meetup, just to get an idea if this is worth the expense. Thanks. -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From me at gbraad.nl Thu Sep 1 20:58:25 2016 From: me at gbraad.nl (Gerard Braad) Date: Fri, 2 Sep 2016 04:58:25 +0800 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: On Friday, September 2, 2016, Rich Bowen wrote: > TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit > this year. We're pursuing an off-site restaurant venue. Would you come? Yes -- Gerard Braad | http://gbraad.nl [ Doing Open Source Matters ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From whayutin at redhat.com Thu Sep 1 21:42:15 2016 From: whayutin at redhat.com (Wesley Hayutin) Date: Thu, 1 Sep 2016 17:42:15 -0400 Subject: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI In-Reply-To: References: <0c25e0c3-5d51-05fb-f628-173010314285@redhat.com> Message-ID: On Thu, Sep 1, 2016 at 7:11 AM, Boris Derzhavets wrote: > I belive four options are available at the moment > > > [boris at fedora24wks tripleo-quickstart]$ cd ./config/release/ > [boris at fedora24wks release]$ ls -l > total 16 > -rw-rw-r--. 1 boris boris 363 Sep 1 13:13 liberty.yml > -rw-rw-r--. 1 boris boris 248 Sep 1 13:13 master-tripleo.yml > -rw-rw-r--. 1 boris boris 562 Sep 1 13:13 master.yml > -rw-rw-r--. 1 boris boris 359 Sep 1 13:13 mitaka.yml > > [boris at fedora24wks release]$ cat mitaka.yml > release: mitaka > undercloud_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/ > mitaka/delorean/stable/undercloud.qcow2 > overcloud_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/ > mitaka/delorean/stable/overcloud-full.tar > ipa_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/ > mitaka/delorean/stable/ironic-python-agent.tar > > [boris at fedora24wks release]$ cat master.yml > release: master > undercloud_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/ > master/delorean/stable/undercloud.qcow2 > overcloud_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/ > master/delorean/stable/overcloud-full.tar > ipa_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/ > master/delorean/stable/ironic-python-agent.tar > > I have no any doubts any more that by default images are taken from > mitaka.yml > > Testing "master" requires " --release master" in command line and would > perform > > downloads via master.yml's URLs which are different from default ones > Boris, you are correct. The default release is mitaka. https://github.com/openstack/tripleo-quickstart/blob/master/quickstart.sh#L8 To get master/newton one must specify the release as you have w/ either --release or -R ./quickstart.sh -R master The delorean repo used is here [2], obtained by looking at [3] Note that the RDO packaging folks are starting to branch master -> newton and we'll end up w/ two distinct repos soon. I'm not sure how far along that is. Is that the question or am I missing the issue here? If I did miss the issue and if email is not helping I encourage you to open a bug here [1]. Thanks [1] https://bugs.launchpad.net/tripleo-quickstart [2] https://trunk.rdoproject.org/centos7/report.html [3] https://ci.centos.org/artifacts/rdo/jenkins-tripleo-quickstart-periodic-master-delorean-full-deploy-ha-84/undercloud/etc/yum.repos.d/delorean.repo.gz > > Boris. > > ------------------------------ > *From:* rdo-list-bounces at redhat.com on > behalf of Boris Derzhavets > *Sent:* Thursday, September 1, 2016 11:07 AM > *To:* Raoul Scarazzini; Wesley Hayutin; Attila Darazs > > *Cc:* rdo-list > *Subject:* Re: [rdo-list] Instack-virt-setup vs TripleO QuickStart in > regards of managing HA PCS/Corosync cluster via pcs CLI > > > Looking at quickstart.sh I see :- > > > : ${OPT_BOOTSTRAP:=0} > : ${OPT_CLEAN:=0} > : ${OPT_PLAYBOOK:=quickstart.yml} > : ${OPT_RELEASE:=mitaka} > : ${OPT_RETAIN_INVENTORY_FILE:=0} > : ${OPT_SYSTEM_PACKAGES:=0} > : ${OPT_TAGS:=$DEFAULT_OPT_TAGS} > : ${OPT_TEARDOWN:=nodes} > : ${OPT_WORKDIR:=$HOME/.quickstart} > . . . . . > > echo " -R, --release OpenStack release to deploy (default=$OPT_RELEASE)" > <== line 147 > > > It clearly shows that default release is Mitaka > > Would you like to test Newton then command line should look like :- > > > $ bash quickstart.sh --config ./ha.yml --release newton $VIRTHOST > > > Boris. > > > > > ------------------------------ > *From:* Raoul Scarazzini > *Sent:* Wednesday, August 24, 2016 5:25 PM > *To:* Boris Derzhavets; Wesley Hayutin; Attila Darazs > *Cc:* rdo-list > *Subject:* Re: [rdo-list] Instack-virt-setup vs TripleO QuickStart in > regards of managing HA PCS/Corosync cluster via pcs CLI > > On 24/08/2016 14:21, Boris Derzhavets wrote: > [...] > > ======================================================================== > > Addressing your requests > > ======================================================================== > > [boris at fedora24wks tripleo-quickstart]$ cat > ./config/general_config/ha.yml > [...] > > $ bash quickstart.sh --config ./config/general_config/ha.yml $VIRTHOST > > EXIT ( undrecloud has been built ) > > Not only. At this point everything should be built. > > [...] > > [root at undercloud stack]# cd /etc/yum.repos.d > > [root at undercloud yum.repos.d]# cat delorean-deps.repo > > [delorean-mitaka-testing] > > name=dlrn-mitaka-testing > > baseurl=http://buildlogs.centos.org/centos/7/cloud/$ > basearch/openstack-mitaka/ > > enabled=1 > > gpgcheck=0 > > priority=2 > > [root at undercloud yum.repos.d]# cat delorean.repo > > [delorean] > > name=delorean-openstack-rally-3909299306233247d547bad265a1adb78adfb3d4 > > baseurl=http://trunk.rdoproject.org/centos7-mitaka/39/09/ > 3909299306233247d547bad265a1adb78adfb3d4_4e6dfa3c > > enabled=1 > > gpgcheck=0 > > This sounds really strange, since you should get master repo (so Newton, > not Mitaka) while using quickstart without specifying --release. > > How long ago did you downloaded the quickstart git repo? Can you > redeploy everything from scratch with the latest pull from quickstart's > git repo? > > -- > Raoul Scarazzini > rasca at redhat.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmyers at redhat.com Thu Sep 1 22:44:36 2016 From: pmyers at redhat.com (Perry Myers) Date: Thu, 1 Sep 2016 18:44:36 -0400 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: On Thu, Sep 1, 2016 at 4:58 PM, Gerard Braad wrote: > On Friday, September 2, 2016, Rich Bowen wrote: >> TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit >> this year. We're pursuing an off-site restaurant venue. Would you come? > > Yes +1 +2 if I can be drinking a beer during the meetup ;) From ggillies at redhat.com Thu Sep 1 22:45:57 2016 From: ggillies at redhat.com (Graeme Gillies) Date: Fri, 2 Sep 2016 08:45:57 +1000 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: On 02/09/16 04:10, Rich Bowen wrote: > TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit > this year. We're pursuing an off-site restaurant venue. Would you come? > > At the last few OpenStack Summit venues, we were able to secure a BoF > (Birds of a Feather) meetup room during the main conference schedule for > an RDO community meetup. This is not an option at this event. Due to > space limitations, all BoF slots went to core projects. > > We are investigating an evening reservation at a nearby (hopefully one > of the conference hotels) venue, in a bar/restaurant. We are sharing > this with the Ceph community to limit costs. > > What I need to know is an idea of how many of you would attend an > evening (like, right after the last conference talk session?) event at a > nearby (walking distance) venue, with light snacks/beverages, where we > did an hour-long RDO Community meetup, just to get an idea if this is > worth the expense. > > Thanks. > I'll be there for sure -- Graeme Gillies Principal Systems Administrator Openstack Infrastructure Red Hat Australia From emilien at redhat.com Fri Sep 2 01:18:57 2016 From: emilien at redhat.com (Emilien Macchi) Date: Thu, 1 Sep 2016 21:18:57 -0400 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: On Thu, Sep 1, 2016 at 6:44 PM, Perry Myers wrote: > On Thu, Sep 1, 2016 at 4:58 PM, Gerard Braad wrote: >> On Friday, September 2, 2016, Rich Bowen wrote: >>> TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit >>> this year. We're pursuing an off-site restaurant venue. Would you come? >> >> Yes > > +1 > +2 if I can be drinking a beer during the meetup ;) only one? :-) I'll come too of course. > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com -- Emilien Macchi From bderzhavets at hotmail.com Fri Sep 2 05:44:19 2016 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Fri, 2 Sep 2016 05:44:19 +0000 Subject: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI In-Reply-To: References: <0c25e0c3-5d51-05fb-f628-173010314285@redhat.com> , Message-ID: ________________________________ From: Wesley Hayutin Sent: Friday, September 2, 2016 12:42 AM To: Boris Derzhavets Cc: Raoul Scarazzini; Attila Darazs; rdo-list Subject: Re: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI On Thu, Sep 1, 2016 at 7:11 AM, Boris Derzhavets > wrote: I belive four options are available at the moment [boris at fedora24wks tripleo-quickstart]$ cd ./config/release/ [boris at fedora24wks release]$ ls -l total 16 -rw-rw-r--. 1 boris boris 363 Sep 1 13:13 liberty.yml -rw-rw-r--. 1 boris boris 248 Sep 1 13:13 master-tripleo.yml -rw-rw-r--. 1 boris boris 562 Sep 1 13:13 master.yml -rw-rw-r--. 1 boris boris 359 Sep 1 13:13 mitaka.yml [boris at fedora24wks release]$ cat mitaka.yml release: mitaka undercloud_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/mitaka/delorean/stable/undercloud.qcow2 overcloud_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/mitaka/delorean/stable/overcloud-full.tar ipa_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/mitaka/delorean/stable/ironic-python-agent.tar [boris at fedora24wks release]$ cat master.yml release: master undercloud_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/master/delorean/stable/undercloud.qcow2 overcloud_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/master/delorean/stable/overcloud-full.tar ipa_image_url: http://artifacts.ci.centos.org/artifacts/rdo/images/master/delorean/stable/ironic-python-agent.tar I have no any doubts any more that by default images are taken from mitaka.yml Testing "master" requires " --release master" in command line and would perform downloads via master.yml's URLs which are different from default ones Boris, you are correct. The default release is mitaka. https://github.com/openstack/tripleo-quickstart/blob/master/quickstart.sh#L8 To get master/newton one must specify the release as you have w/ either --release or -R ./quickstart.sh -R master The delorean repo used is here [2], obtained by looking at [3] Note that the RDO packaging folks are starting to branch master -> newton and we'll end up w/ two distinct repos soon. I'm not sure how far along that is. Is that the question or am I missing the issue here? If I did miss the issue and if email is not helping I encourage you to open a bug here [1]. >>> You are not missing anything However, I have already tested :- $ bash quickstart.sh --config ./ha.yml -R master $VIRTHOST It does build undercloud and performs overcloud deploy . Unfortunately, I have to report that status of PCS Controller's cluster at the moment is very far for work-able. Just looks as the work in progress. I am not sure how much sense has filing bug regarding this misbehavior right now. If branching stable "newton" will give me same results, then I will open bug's record. Thank you very much for responding. Boris >>> Thanks [1] https://bugs.launchpad.net/tripleo-quickstart [2] https://trunk.rdoproject.org/centos7/report.html [3] https://ci.centos.org/artifacts/rdo/jenkins-tripleo-quickstart-periodic-master-delorean-full-deploy-ha-84/undercloud/etc/yum.repos.d/delorean.repo.gz Boris. ________________________________ From: rdo-list-bounces at redhat.com > on behalf of Boris Derzhavets > Sent: Thursday, September 1, 2016 11:07 AM To: Raoul Scarazzini; Wesley Hayutin; Attila Darazs Cc: rdo-list Subject: Re: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI Looking at quickstart.sh I see :- : ${OPT_BOOTSTRAP:=0} : ${OPT_CLEAN:=0} : ${OPT_PLAYBOOK:=quickstart.yml} : ${OPT_RELEASE:=mitaka} : ${OPT_RETAIN_INVENTORY_FILE:=0} : ${OPT_SYSTEM_PACKAGES:=0} : ${OPT_TAGS:=$DEFAULT_OPT_TAGS} : ${OPT_TEARDOWN:=nodes} : ${OPT_WORKDIR:=$HOME/.quickstart} . . . . . echo " -R, --release OpenStack release to deploy (default=$OPT_RELEASE)" <== line 147 It clearly shows that default release is Mitaka Would you like to test Newton then command line should look like :- $ bash quickstart.sh --config ./ha.yml --release newton $VIRTHOST Boris. ________________________________ From: Raoul Scarazzini > Sent: Wednesday, August 24, 2016 5:25 PM To: Boris Derzhavets; Wesley Hayutin; Attila Darazs Cc: rdo-list Subject: Re: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI On 24/08/2016 14:21, Boris Derzhavets wrote: [...] > ======================================================================== > Addressing your requests > ======================================================================== > [boris at fedora24wks tripleo-quickstart]$ cat ./config/general_config/ha.yml [...] > $ bash quickstart.sh --config ./config/general_config/ha.yml $VIRTHOST > EXIT ( undrecloud has been built ) Not only. At this point everything should be built. [...] > [root at undercloud stack]# cd /etc/yum.repos.d > [root at undercloud yum.repos.d]# cat delorean-deps.repo > [delorean-mitaka-testing] > name=dlrn-mitaka-testing > baseurl=http://buildlogs.centos.org/centos/7/cloud/$basearch/openstack-mitaka/ > enabled=1 > gpgcheck=0 > priority=2 > [root at undercloud yum.repos.d]# cat delorean.repo > [delorean] > name=delorean-openstack-rally-3909299306233247d547bad265a1adb78adfb3d4 > baseurl=http://trunk.rdoproject.org/centos7-mitaka/39/09/3909299306233247d547bad265a1adb78adfb3d4_4e6dfa3c > enabled=1 > gpgcheck=0 This sounds really strange, since you should get master repo (so Newton, not Mitaka) while using quickstart without specifying --release. How long ago did you downloaded the quickstart git repo? Can you redeploy everything from scratch with the latest pull from quickstart's git repo? -- Raoul Scarazzini rasca at redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmellado at redhat.com Fri Sep 2 06:57:19 2016 From: dmellado at redhat.com (Daniel Mellado) Date: Fri, 2 Sep 2016 08:57:19 +0200 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: <5b02ea38-c7de-4ded-73f0-7662d8392000@redhat.com> Count me in, I guess most of the red hat guys attending the event would attend ;) El 02/09/16 a las 00:45, Graeme Gillies escribi?: > On 02/09/16 04:10, Rich Bowen wrote: >> TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit >> this year. We're pursuing an off-site restaurant venue. Would you come? >> >> At the last few OpenStack Summit venues, we were able to secure a BoF >> (Birds of a Feather) meetup room during the main conference schedule for >> an RDO community meetup. This is not an option at this event. Due to >> space limitations, all BoF slots went to core projects. >> >> We are investigating an evening reservation at a nearby (hopefully one >> of the conference hotels) venue, in a bar/restaurant. We are sharing >> this with the Ceph community to limit costs. >> >> What I need to know is an idea of how many of you would attend an >> evening (like, right after the last conference talk session?) event at a >> nearby (walking distance) venue, with light snacks/beverages, where we >> did an hour-long RDO Community meetup, just to get an idea if this is >> worth the expense. >> >> Thanks. >> > > I'll be there for sure > From me at coolsvap.net Fri Sep 2 06:59:11 2016 From: me at coolsvap.net (Swapnil Kulkarni (coolsvap)) Date: Fri, 2 Sep 2016 12:29:11 +0530 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: On Thu, Sep 1, 2016 at 11:40 PM, Rich Bowen wrote: > TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit > this year. We're pursuing an off-site restaurant venue. Would you come? > > At the last few OpenStack Summit venues, we were able to secure a BoF > (Birds of a Feather) meetup room during the main conference schedule for > an RDO community meetup. This is not an option at this event. Due to > space limitations, all BoF slots went to core projects. > > We are investigating an evening reservation at a nearby (hopefully one > of the conference hotels) venue, in a bar/restaurant. We are sharing > this with the Ceph community to limit costs. > > What I need to know is an idea of how many of you would attend an > evening (like, right after the last conference talk session?) event at a > nearby (walking distance) venue, with light snacks/beverages, where we > did an hour-long RDO Community meetup, just to get an idea if this is > worth the expense. > > Thanks. > > -- > Rich Bowen - rbowen at redhat.com > RDO Community Liaison > http://rdoproject.org > @RDOCommunity > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com +1 From mrunge at redhat.com Fri Sep 2 07:00:27 2016 From: mrunge at redhat.com (Matthias Runge) Date: Fri, 2 Sep 2016 09:00:27 +0200 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: <89548b0e-1c79-fa55-4adc-698c488e4e32@redhat.com> On 02/09/16 03:18, Emilien Macchi wrote: > On Thu, Sep 1, 2016 at 6:44 PM, Perry Myers wrote: >> On Thu, Sep 1, 2016 at 4:58 PM, Gerard Braad wrote: >>> On Friday, September 2, 2016, Rich Bowen wrote: >>>> TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit >>>> this year. We're pursuing an off-site restaurant venue. Would you come? >>> >>> Yes >> >> +1 >> +2 if I can be drinking a beer during the meetup ;) > > only one? :-) > > I'll come too of course. > Yes, I would come. I'm not even sure if we really need a beamer/presentation? Matthias -- Matthias Runge From javier.pena at redhat.com Fri Sep 2 09:25:12 2016 From: javier.pena at redhat.com (Javier Pena) Date: Fri, 2 Sep 2016 05:25:12 -0400 (EDT) Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: <528836082.8317322.1472808312507.JavaMail.zimbra@redhat.com> ----- Original Message ----- > TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit > this year. We're pursuing an off-site restaurant venue. Would you come? > > At the last few OpenStack Summit venues, we were able to secure a BoF > (Birds of a Feather) meetup room during the main conference schedule for > an RDO community meetup. This is not an option at this event. Due to > space limitations, all BoF slots went to core projects. > > We are investigating an evening reservation at a nearby (hopefully one > of the conference hotels) venue, in a bar/restaurant. We are sharing > this with the Ceph community to limit costs. > > What I need to know is an idea of how many of you would attend an > evening (like, right after the last conference talk session?) event at a > nearby (walking distance) venue, with light snacks/beverages, where we > did an hour-long RDO Community meetup, just to get an idea if this is > worth the expense. > /me raises his hand :) > Thanks. > > -- > Rich Bowen - rbowen at redhat.com > RDO Community Liaison > http://rdoproject.org > @RDOCommunity > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > From hguemar at fedoraproject.org Fri Sep 2 09:55:44 2016 From: hguemar at fedoraproject.org (=?UTF-8?Q?Ha=C3=AFkel?=) Date: Fri, 2 Sep 2016 11:55:44 +0200 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: 2016-09-01 20:10 GMT+02:00 Rich Bowen : > TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit > this year. We're pursuing an off-site restaurant venue. Would you come? > > At the last few OpenStack Summit venues, we were able to secure a BoF > (Birds of a Feather) meetup room during the main conference schedule for > an RDO community meetup. This is not an option at this event. Due to > space limitations, all BoF slots went to core projects. > > We are investigating an evening reservation at a nearby (hopefully one > of the conference hotels) venue, in a bar/restaurant. We are sharing > this with the Ceph community to limit costs. > > What I need to know is an idea of how many of you would attend an > evening (like, right after the last conference talk session?) event at a > nearby (walking distance) venue, with light snacks/beverages, where we > did an hour-long RDO Community meetup, just to get an idea if this is > worth the expense. > > Thanks. > Si, se?or! > -- > Rich Bowen - rbowen at redhat.com > RDO Community Liaison > http://rdoproject.org > @RDOCommunity > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From dtantsur at redhat.com Fri Sep 2 09:58:58 2016 From: dtantsur at redhat.com (Dmitry Tantsur) Date: Fri, 2 Sep 2016 11:58:58 +0200 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: <8006b9ef-0fc6-96f0-cf45-fd470854116a@redhat.com> On 09/01/2016 08:10 PM, Rich Bowen wrote: > TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit > this year. We're pursuing an off-site restaurant venue. Would you come? > > At the last few OpenStack Summit venues, we were able to secure a BoF > (Birds of a Feather) meetup room during the main conference schedule for > an RDO community meetup. This is not an option at this event. Due to > space limitations, all BoF slots went to core projects. > > We are investigating an evening reservation at a nearby (hopefully one > of the conference hotels) venue, in a bar/restaurant. We are sharing > this with the Ceph community to limit costs. > > What I need to know is an idea of how many of you would attend an > evening (like, right after the last conference talk session?) event at a > nearby (walking distance) venue, with light snacks/beverages, where we > did an hour-long RDO Community meetup, just to get an idea if this is > worth the expense. > > Thanks. > Depends on other evening events, but likely +1 From trown at redhat.com Fri Sep 2 13:00:00 2016 From: trown at redhat.com (John Trowbridge) Date: Fri, 2 Sep 2016 09:00:00 -0400 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: On 09/01/2016 02:10 PM, Rich Bowen wrote: > TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit > this year. We're pursuing an off-site restaurant venue. Would you come? > > At the last few OpenStack Summit venues, we were able to secure a BoF > (Birds of a Feather) meetup room during the main conference schedule for > an RDO community meetup. This is not an option at this event. Due to > space limitations, all BoF slots went to core projects. > > We are investigating an evening reservation at a nearby (hopefully one > of the conference hotels) venue, in a bar/restaurant. We are sharing > this with the Ceph community to limit costs. > > What I need to know is an idea of how many of you would attend an > evening (like, right after the last conference talk session?) event at a > nearby (walking distance) venue, with light snacks/beverages, where we > did an hour-long RDO Community meetup, just to get an idea if this is > worth the expense. > > Thanks. > +1 From morazi at redhat.com Fri Sep 2 13:57:07 2016 From: morazi at redhat.com (Michael Orazi) Date: Fri, 2 Sep 2016 09:57:07 -0400 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: +1 - Mike On Thu, Sep 1, 2016 at 2:10 PM, Rich Bowen wrote: > TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit > this year. We're pursuing an off-site restaurant venue. Would you come? > > At the last few OpenStack Summit venues, we were able to secure a BoF > (Birds of a Feather) meetup room during the main conference schedule for > an RDO community meetup. This is not an option at this event. Due to > space limitations, all BoF slots went to core projects. > > We are investigating an evening reservation at a nearby (hopefully one > of the conference hotels) venue, in a bar/restaurant. We are sharing > this with the Ceph community to limit costs. > > What I need to know is an idea of how many of you would attend an > evening (like, right after the last conference talk session?) event at a > nearby (walking distance) venue, with light snacks/beverages, where we > did an hour-long RDO Community meetup, just to get an idea if this is > worth the expense. > > Thanks. > > -- > Rich Bowen - rbowen at redhat.com > RDO Community Liaison > http://rdoproject.org > @RDOCommunity > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > > From prad at redhat.com Fri Sep 2 14:38:39 2016 From: prad at redhat.com (Pradeep Kilambi) Date: Fri, 2 Sep 2016 10:38:39 -0400 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: On Fri, Sep 2, 2016 at 9:57 AM, Michael Orazi wrote: > +1 > > - Mike > > On Thu, Sep 1, 2016 at 2:10 PM, Rich Bowen wrote: > > TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit > > this year. We're pursuing an off-site restaurant venue. Would you come? > > > +1 Count me in :) > > At the last few OpenStack Summit venues, we were able to secure a BoF > > (Birds of a Feather) meetup room during the main conference schedule for > > an RDO community meetup. This is not an option at this event. Due to > > space limitations, all BoF slots went to core projects. > > > > We are investigating an evening reservation at a nearby (hopefully one > > of the conference hotels) venue, in a bar/restaurant. We are sharing > > this with the Ceph community to limit costs. > > > > What I need to know is an idea of how many of you would attend an > > evening (like, right after the last conference talk session?) event at a > > nearby (walking distance) venue, with light snacks/beverages, where we > > did an hour-long RDO Community meetup, just to get an idea if this is > > worth the expense. > > > > Thanks. > > > > -- > > Rich Bowen - rbowen at redhat.com > > RDO Community Liaison > > http://rdoproject.org > > @RDOCommunity > > > > _______________________________________________ > > rdo-list mailing list > > rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > To unsubscribe: rdo-list-unsubscribe at redhat.com > > > > > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mburns at redhat.com Fri Sep 2 16:55:05 2016 From: mburns at redhat.com (Mike Burns) Date: Fri, 2 Sep 2016 12:55:05 -0400 Subject: [rdo-list] Adding backwards compatible tripleo-heat-templates packaging Message-ID: I've posted a WIP patch[1] based on what we've done in the downstream OSP releases with tripleo-heat-templates to provide backwards compatible heat templates for managing older versions. The base requirements are: * Package the latest tripleo-heat-templates from the previous release (in this case mitaka) * Must be installable side-by-side with the the current version heat-templates * A single srpm if at all possible The patch essentially mimics what has been done downstream previously and has generally worked. Getting it to work with DLRN is more difficult and sub-optimal due to having to track multiple upstream branches. I'm open to suggestions for how to deal with this challenge and am certainly not stuck on the this being the solution. Thanks Mike [1] http://review.rdoproject.org/r/2042 From aortega at redhat.com Fri Sep 2 17:47:49 2016 From: aortega at redhat.com (Alvaro Lopez Ortega) Date: Fri, 2 Sep 2016 13:47:49 -0400 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: On Thu, Sep 1, 2016 at 2:10 PM, Rich Bowen wrote: > TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit > this year. We're pursuing an off-site restaurant venue. Would you come? > Most certainly, yes :) +1 Best, Alvaro -------------- next part -------------- An HTML attachment was scrubbed... URL: From apevec at redhat.com Fri Sep 2 21:54:45 2016 From: apevec at redhat.com (Alan Pevec) Date: Fri, 2 Sep 2016 23:54:45 +0200 Subject: [rdo-list] BoF at OpenStack Summit In-Reply-To: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> References: <34d3c6f8-df38-6961-76f7-994ac2d9a0ac@redhat.com> Message-ID: On Thu, Sep 1, 2016 at 8:10 PM, Rich Bowen wrote: > TL;DR. There are no BoF (Meetup) slots available at OpenStack Summit > this year. We're pursuing an off-site restaurant venue. Would you come? yes! > We are investigating an evening reservation at a nearby (hopefully one > of the conference hotels) venue, in a bar/restaurant. We are sharing > this with the Ceph community to limit costs. +1 for sharing with Ceph, not just for costs but also to get some cross-pollination going, how KB likes to say :) Like lure them into working within centos storage SIG. Alan From apevec at redhat.com Fri Sep 2 22:04:09 2016 From: apevec at redhat.com (Alan Pevec) Date: Sat, 3 Sep 2016 00:04:09 +0200 Subject: [rdo-list] Adding backwards compatible tripleo-heat-templates packaging In-Reply-To: References: Message-ID: > * A single srpm if at all possible Why is that a requirement? Usually in rpm world you create separate parallel installable compat package by adding version to the package name e.g. we had python-webob1.2 in the past. THT mitaka is 2.x so what about creating a new package openstack-tripleo-heat-templates2 ? Alan From mburns at redhat.com Sat Sep 3 00:50:51 2016 From: mburns at redhat.com (Mike Burns) Date: Fri, 2 Sep 2016 20:50:51 -0400 Subject: [rdo-list] Adding backwards compatible tripleo-heat-templates packaging In-Reply-To: References: Message-ID: On Fri, Sep 2, 2016 at 6:04 PM, Alan Pevec wrote: >> * A single srpm if at all possible > > Why is that a requirement? Usually in rpm world you create separate > parallel installable compat package by adding version to the package > name e.g. we had python-webob1.2 in the past. > THT mitaka is 2.x so what about creating a new package > openstack-tripleo-heat-templates2 ? We could do that and it's ok, really. It just means a new package process for every release of OpenStack. There is no real clean mapping historically of THT version to OpenStack version. How does someone know that tht2 is mitaka? When we reach ocata and have to have a BC package, it's tht5 which is newton. (We could simply name it openstack-tripleo-heat-templates-mitaka). The proposal currently means that we have to change 1 spec file value per release rather than go through a totally new package each release. Mike > > Alan From ggillies at redhat.com Mon Sep 5 04:37:13 2016 From: ggillies at redhat.com (Graeme Gillies) Date: Mon, 5 Sep 2016 14:37:13 +1000 Subject: [rdo-list] Python-shade in RDO In-Reply-To: References: <9f38876e-eec8-b4b1-11fd-68d14f7c471d@redhat.com> <3cdfa6fc-6ca7-b99c-b2c2-2f0a59719ab8@redhat.com> <4ee88a00-980a-8e01-c25e-3fdf4a3ba28c@redhat.com> <1a036e38-1126-1a01-5ebe-1c198432e516@redhat.com> Message-ID: <9b66c5f1-9667-14c9-1b1e-e06cf9b34ca7@redhat.com> Apologies for not replying sooner. I'm still not 100% convinced that splitting up and fracturing RDO into more repos is worthwhile, but I am happy to wait and see. If it's possible for the RDO team to put together a clear piece of documentation outlining what all the proposed and existing repos are, their names, their purposes, and some examples and criteria of what type of Openstack (and non-openstack, like openvswitch) packages land, that might make it clearer for us to understand. Regards, Graeme On 30/08/16 23:19, Ha?kel wrote: > 2016-08-30 8:23 GMT+02:00 Graeme Gillies : >> >> I would really implore you to think very carefully about splitting out >> release:independant projects into a separate repo, especially one with >> the name "extras". >> > > Naming is easy to change, could be RDO clients and SDK, RDO Cloud > users or whatever > >> Fracturing the repo setup only reduces usability, causes confusion, and >> for those projects that choose an independent release model, it makes >> them feel like second class citizens and less likely to want to care or >> be part of the RDO community. >> > > As Alan explained, we can't. > > Actually, forcing release-independent projects like shade in > release-specific repositories would make them more of a second-class > citizen. Let's say that shade requires a newer version of clients than > we can ship in Mitaka, that would force us to pin shade to an older > release and maybe fork it to backport security updates. > A separate repository would give us the flexibility to ship the latest > and greatest of those projects without worrying to break stuff that > will be installed in our cloud nodes. > >> As I've already mentioned, we already ship a release:independant project >> in the normal repo, and I fail to see from a technical level why others >> can't do the same. Simply ship their latest stable release in the >> current stable repo. >> > > That's poor workaround because we didn't have the flexibility to do otherwise. > As for shade, stable releases requirements don't match > release-dependent projects requirements and we do have a precedent: > gnocchi. > Gnocchi follows its own branching model and because of requirements, > we have to collaborate with upstream devs to map specific gnocchi > branches to an OpenStack release, though if you install gnocchi nodes > in separated nodes, it does not matter. > > >> A lot of the projects that choose release:independant are smaller, >> perhaps a bit newer, and still in a growth phase. If RDO is able to show >> that those projects can be a part of RDO like everything else, it means >> they are more likely to participate in the community, as it makes their >> software more accessible. >> > > We can provide flexibility like we did with gnocchi but here I'd > rather think of how could we provide better fits to our community by > adding a new repository to fit the needs of cloud user > >> Remember the goal here is to grow the community and have as many >> projects participating in RDO as possible. Encouraging the smaller >> projects to do so is a great way to help that. >> >> Regards, >> >> Graeme >> > > *nods* > > Regards, > H. > >>> >>>> Regards, >>>> >>>> Graeme >>>> >>>> [1] https://governance.openstack.org/reference/tags/ >>>> >>>> -- >>>> Graeme Gillies >>>> Principal Systems Administrator >>>> Openstack Infrastructure >>>> Red Hat Australia >> >> >> -- >> Graeme Gillies >> Principal Systems Administrator >> Openstack Infrastructure >> Red Hat Australia -- Graeme Gillies Principal Systems Administrator Openstack Infrastructure Red Hat Australia From javier.pena at redhat.com Mon Sep 5 14:47:50 2016 From: javier.pena at redhat.com (Javier Pena) Date: Mon, 5 Sep 2016 10:47:50 -0400 (EDT) Subject: [rdo-list] Adding backwards compatible tripleo-heat-templates packaging In-Reply-To: References: Message-ID: <376215178.9458025.1473086870132.JavaMail.zimbra@redhat.com> ----- Original Message ----- > On Fri, Sep 2, 2016 at 6:04 PM, Alan Pevec wrote: > >> * A single srpm if at all possible > > > > Why is that a requirement? Usually in rpm world you create separate > > parallel installable compat package by adding version to the package > > name e.g. we had python-webob1.2 in the past. > > THT mitaka is 2.x so what about creating a new package > > openstack-tripleo-heat-templates2 ? > > We could do that and it's ok, really. It just means a new package > process for every release of OpenStack. There is no real clean > mapping historically of THT version to OpenStack version. How does > someone know that tht2 is mitaka? When we reach ocata and have to > have a BC package, it's tht5 which is newton. (We could simply name > it openstack-tripleo-heat-templates-mitaka). I think something like this (having an openstack-tripleo-heat-templates-compat-mitaka package or similar) would work best. This would also allow us to decide when to drop support for older releases. Newton will have a mitaka-compat package, but we'll sure drop it in a later release, won't we? We could then just control which packages are built for each release using rdoinfo. Javier > > The proposal currently means that we have to change 1 spec file value > per release rather than go through a totally new package each release. > > Mike > > > > > > Alan > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > From hguemar at fedoraproject.org Mon Sep 5 15:00:03 2016 From: hguemar at fedoraproject.org (hguemar at fedoraproject.org) Date: Mon, 5 Sep 2016 15:00:03 +0000 (UTC) Subject: [rdo-list] [Fedocal] Reminder meeting : RDO meeting Message-ID: <20160905150003.9634860A4003@fedocal02.phx2.fedoraproject.org> Dear all, You are kindly invited to the meeting: RDO meeting on 2016-09-07 from 15:00:00 to 16:00:00 UTC At rdo at 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/ From rbowen at redhat.com Tue Sep 6 14:07:19 2016 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 6 Sep 2016 10:07:19 -0400 Subject: [rdo-list] Unanswered "RDO" questions, ask.openstack.org Message-ID: <0a4f9aed-722a-a7f5-fe0b-acf9da808db9@redhat.com> 25 unanswered questions: Error during LBAAS installation (Load Balancer) I can't install it. https://ask.openstack.org/en/question/96511/error-during-lbaas-installation-load-balancer-i-cant-install-it/ Tags: rdo, lbaasv2, mitaka-neutron, centos7, loadbalancer quota show is different from horizon in RDO after update quota with command https://ask.openstack.org/en/question/96244/quota-show-is-different-from-horizon-in-rdo-after-update-quota-with-command/ Tags: rdo how to set quota with python https://ask.openstack.org/en/question/96231/how-to-set-quota-with-python/ Tags: quota "Parameter outiface failed on Firewall" during installation of openstack rdo on centos 7 https://ask.openstack.org/en/question/95657/parameter-outiface-failed-on-firewall-during-installation-of-openstack-rdo-on-centos-7/ Tags: rdo, devstack#mitaka multi nodes provider network ovs config https://ask.openstack.org/en/question/95423/multi-nodes-provider-network-ovs-config/ Tags: rdo, liberty-neutron Adding additional packages to an RDO installation https://ask.openstack.org/en/question/95380/adding-additional-packages-to-an-rdo-installation/ Tags: rdo, mistral RDO TripleO Mitaka HA Overcloud Failing https://ask.openstack.org/en/question/95249/rdo-tripleo-mitaka-ha-overcloud-failing/ Tags: mitaka, tripleo, overcloud, centos7 RDO - is there any fedora package newer than puppet-4.2.1-3.fc24.noarch.rpm https://ask.openstack.org/en/question/94969/rdo-is-there-any-fedora-package-newer-than-puppet-421-3fc24noarchrpm/ Tags: rdo, puppet, install-openstack OpenStack RDO mysqld 100% cpu https://ask.openstack.org/en/question/94961/openstack-rdo-mysqld-100-cpu/ Tags: openstack, mysqld, cpu Failed to set RDO repo on host-packstack-centOS-7 https://ask.openstack.org/en/question/94828/failed-to-set-rdo-repo-on-host-packstack-centos-7/ Tags: openstack-packstack, centos7, rdo how to deploy haskell-distributed in RDO? https://ask.openstack.org/en/question/94785/how-to-deploy-haskell-distributed-in-rdo/ Tags: rdo rdo tripleO liberty undercloud install failing https://ask.openstack.org/en/question/94023/rdo-tripleo-liberty-undercloud-install-failing/ Tags: rdo, rdo-manager, liberty, undercloud, instack Liberty RDO: stack resource topology icons are pink https://ask.openstack.org/en/question/91347/liberty-rdo-stack-resource-topology-icons-are-pink/ Tags: resource, topology, dashboard, horizon, pink No handlers could be found for logger "oslo_config.cfg" while syncing the glance database https://ask.openstack.org/en/question/91169/no-handlers-could-be-found-for-logger-oslo_configcfg-while-syncing-the-glance-database/ Tags: liberty, glance, install-openstack CentOS OpenStack - compute node can't talk https://ask.openstack.org/en/question/88989/centos-openstack-compute-node-cant-talk/ Tags: rdo How to setup SWIFT_PROXY_NODE and SWIFT_STORAGE_NODEs separately on RDO Liberty ? https://ask.openstack.org/en/question/88897/how-to-setup-swift_proxy_node-and-swift_storage_nodes-separately-on-rdo-liberty/ Tags: rdo, liberty, swift, ha VM and container can't download anything from internet https://ask.openstack.org/en/question/88338/vm-and-container-cant-download-anything-from-internet/ Tags: rdo, neutron, network, connectivity Fedora22, Liberty, horizon VNC console and keymap=sv with ; and/ https://ask.openstack.org/en/question/87451/fedora22-liberty-horizon-vnc-console-and-keymapsv-with-and/ Tags: keyboard, map, keymap, vncproxy, novnc OpenStack-Docker driver failed https://ask.openstack.org/en/question/87243/openstack-docker-driver-failed/ Tags: docker, openstack, liberty Routing between two tenants https://ask.openstack.org/en/question/84645/routing-between-two-tenants/ Tags: kilo, fuel, rdo, routing openstack baremetal introspection internal server error https://ask.openstack.org/en/question/82790/openstack-baremetal-introspection-internal-server-error/ Tags: rdo, ironic-inspector, tripleo Installing openstack using packstack (rdo) failed https://ask.openstack.org/en/question/82473/installing-openstack-using-packstack-rdo-failed/ Tags: rdo, packstack, installation-error, keystone VMware Host Backend causes No valid host was found. Bug ??? https://ask.openstack.org/en/question/79738/vmware-host-backend-causes-no-valid-host-was-found-bug/ Tags: vmware, rdo Mutlinode Devstack with two interfaces https://ask.openstack.org/en/question/78615/mutlinode-devstack-with-two-interfaces/ Tags: devstack, vlan, openstack Overcloud deployment on VM fails as IP address from DHCP is not assigned https://ask.openstack.org/en/question/66272/overcloud-deployment-on-vm-fails-as-ip-address-from-dhcp-is-not-assigned/ Tags: overcloud_in_vm -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From dms at redhat.com Tue Sep 6 14:20:13 2016 From: dms at redhat.com (David Moreau Simard) Date: Tue, 6 Sep 2016 10:20:13 -0400 Subject: [rdo-list] Tempest Packaging in RDO In-Reply-To: <731736690.7134214.1472544177263.JavaMail.zimbra@redhat.com> References: <731736690.7134214.1472544177263.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Aug 30, 2016 at 4:02 AM, Javier Pena wrote: > I'd really like to remove the tempest dependency for designate-tests and horizon-tests soon, at least to unblock part of the issues (not being able to properly test designate/horizon without pulling the whole Tempest lot with it). Yes, please. I would love the review for designate-tests [1] to land so we can unblock designate testing and be confident to ship a tested and working designate for Newton. [1]: https://review.rdoproject.org/r/#/c/1820/ David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] From rbowen at redhat.com Tue Sep 6 15:52:43 2016 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 6 Sep 2016 11:52:43 -0400 Subject: [rdo-list] Upcoming OpenStack meetups Message-ID: The following are the meetups I'm aware of in the coming week where OpenStack and/or RDO enthusiasts are likely to be present. If you know of others, please let me know, and/or add them to http://rdoproject.org/events If there's a meetup in your area, please consider attending. If you attend, please consider taking a few photos, and possibly even writing up a brief summary of what was covered. --Rich * Wednesday September 07 in Richardson, TX, US: ETSI NFV-SEC - best practices - http://www.meetup.com/OpenStack-DFW/events/233744324/ * Wednesday September 07 in San Francisco, CA, US: Containers and OpenStack - http://www.meetup.com/openstack/events/233227736/ * Thursday September 08 in Pittsburgh, PA, US: The Red Hat OpenStack Platform - http://www.meetup.com/Pittsburgh-Red-Hat-User-Group/events/233282275/ * Thursday September 08 in Reston, VA, US: OpenStack meetup on contributions in the OpenStack community! - http://www.meetup.com/OpenStack-Nova/events/232971596/ * Friday September 09 in Guadalajara, MX: Hackathon de Aplicaciones en OpenStack - http://www.meetup.com/OpenStack-GDL/events/232288032/ * Saturday September 10 in North York, ON, CA: OpenStack Administration - Success & Failures of the Cloud Adoption - http://www.meetup.com/StackDocker-TO/events/232473294/ -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From pmyers at redhat.com Tue Sep 6 15:56:34 2016 From: pmyers at redhat.com (Perry Myers) Date: Tue, 6 Sep 2016 11:56:34 -0400 Subject: [rdo-list] Upcoming OpenStack meetups In-Reply-To: References: Message-ID: On Tue, Sep 6, 2016 at 11:52 AM, Rich Bowen wrote: > The following are the meetups I'm aware of in the coming week where > OpenStack and/or RDO enthusiasts are likely to be present. If you know > of others, please let me know, and/or add them to > http://rdoproject.org/events > > If there's a meetup in your area, please consider attending. If you > attend, please consider taking a few photos, and possibly even writing > up a brief summary of what was covered. > > --Rich > > * Wednesday September 07 in Richardson, TX, US: ETSI NFV-SEC - best > practices - http://www.meetup.com/OpenStack-DFW/events/233744324/ > > * Wednesday September 07 in San Francisco, CA, US: Containers and > OpenStack - http://www.meetup.com/openstack/events/233227736/ > > * Thursday September 08 in Pittsburgh, PA, US: The Red Hat OpenStack > Platform - > http://www.meetup.com/Pittsburgh-Red-Hat-User-Group/events/233282275/ I'll be popping in a this one, if anyone in the area wants to stop by and say hello :) Perry From rbowen at redhat.com Tue Sep 6 17:22:58 2016 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 6 Sep 2016 13:22:58 -0400 Subject: [rdo-list] LinuxDays Prague Message-ID: We plan to have an RDO presence at LinuxDays Prague https://www.linuxdays.cz/2016/ https://www.linuxdays.cz/2016/en/ in English The event is free. The event is primarily held in the Czech language, although there will be talks in English as well. We expect to have an RDO banner, and RDO stickers. Eliska will be present to manage our presence and our message there. If you expect to be at that event, we (Eliska and I) would love to hear from you. In particular, if you're already planning to attend, or if you get a talk accepted, would you also be willing to volunteer some time to answer questions at the RDO table? -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From smonderer at vasonanetworks.com Wed Sep 7 06:20:02 2016 From: smonderer at vasonanetworks.com (Samuel Monderer) Date: Wed, 7 Sep 2016 09:20:02 +0300 Subject: [rdo-list] [TripleO] ControllerLoadBalancerDeployment_Step1 resource failed Message-ID: Hi, I have one controller and one compute node both with 3 NICs: IPMI,net1 and net2 I've based my overcloud configuration on the bond with vlans but I removed the bond and just used a single NIC instead. For the moment I don't need storage as my setup is a NFV cloud, so I removed the storage network and storage-management network. Network configuration per node - controller: - IPMI - NIC1: - Provioning Network - NIC2 - Internal Network - Tenant Network - Management Network - External Network - compute - IPMI - NIC1: - Provioning Network - NIC2 - Internal Network - Tenant Network - Management Network By the way what is the management netwrok for? Is it for accesssing the nodes without going through the director? I ran the deployment but the following resources failed overcloud-ControllerNodesPostDeployment-4lpz4z4msgzz- ControllerLoadBalancerDeployment_Step1-nc4sfpp34a57 overcloud-ControllerNodesPostDeployment-4lpz4z4msgzz overcloud-ComputeNodesPostDeployment-ougcodme2eo2 When I checked the os-collect-config log on the controller I found that It wasn't able to reach the mysql server (attached is the log file) Any Idea what could be the issue? Attached are also the configuration files Regards, Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jrnl.log Type: application/octet-stream Size: 527712 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: compute.yaml Type: application/octet-stream Size: 4277 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: controller.yaml Type: application/octet-stream Size: 4823 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: network-environment.yaml Type: application/octet-stream Size: 3254 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: network-isolation.yaml Type: application/octet-stream Size: 5632 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: timezone.yaml Type: application/octet-stream Size: 41 bytes Desc: not available URL: From smonderer at vasonanetworks.com Wed Sep 7 07:32:37 2016 From: smonderer at vasonanetworks.com (Samuel Monderer) Date: Wed, 07 Sep 2016 07:32:37 +0000 Subject: [rdo-list] [TripleO] ControllerLoadBalancerDeployment_Step1 resource failed In-Reply-To: References: Message-ID: [heat-admin at overcloud-controller-0 ~]$ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # HEAT_HOSTS_START - Do not edit manually within this section! 172.16.0.12 overcloud-compute-0.localdomain overcloud-compute-0 192.0.2.13 overcloud-compute-0-external 172.16.0.12 overcloud-compute-0-internalapi 192.0.2.13 overcloud-compute-0-storage 192.0.2.13 overcloud-compute-0-storagemgmt 172.17.0.10 overcloud-compute-0-tenant 172.20.0.10 overcloud-compute-0-management 172.16.0.13 overcloud-controller-0.localdomain overcloud-controller-0 192.168.40.137 overcloud-controller-0-external 172.16.0.13 overcloud-controller-0-internalapi 192.0.2.14 overcloud-controller-0-storage 192.0.2.14 overcloud-controller-0-storagemgmt 172.17.0.11 overcloud-controller-0-tenant 172.20.0.11 overcloud-controller-0-management # HEAT_HOSTS_END On Wed, Sep 7, 2016 at 10:19 AM Luca 'remix_tj' Lorenzetto < lorenzetto.luca at gmail.com> wrote: > On Wed, Sep 7, 2016 at 8:20 AM, Samuel Monderer > wrote: > > Hi, > [cut] > > Hi, > > > NIC2 > > > > Internal Network > > Tenant Network > > Management Network > > > > By the way what is the management netwrok for? Is it for accesssing the > > nodes without going through the director? > > Yes, i have the horizon dashboard exposed through one ip of management > network. > > > > > I ran the deployment but the following resources failed > > > overcloud-ControllerNodesPostDeployment-4lpz4z4msgzz-ControllerLoadBalancerDeployment_Step1-nc4sfpp34a57 > > overcloud-ControllerNodesPostDeployment-4lpz4z4msgzz > > overcloud-ComputeNodesPostDeployment-ougcodme2eo2 > > > > When I checked the os-collect-config log on the controller I found > that It > > wasn't able to reach the mysql server (attached is the log file) > > > > Any Idea what could be the issue? > > I had a similar issue. I see this on your logs: > > Sep 07 00:24:58 overcloud-controller-0.localdomain > os-collect-config[4781]: Error: > /Stage[main]/Pacemaker::Corosync/Exec[reauthenticate-across-all-nodes]: > Failed to call refresh: /sbin/pcs cluster auth overcloud-controller-0 > -u hacluster -p u33uizaZhyaVGXRX --force returned 1 instead of one of > [0] > Sep 07 00:24:58 overcloud-controller-0.localdomain > os-collect-config[4781]: Error: > /Stage[main]/Pacemaker::Corosync/Exec[reauthenticate-across-all-nodes]: > /sbin/pcs cluster auth overcloud-controller-0 -u hacluster -p > u33uizaZhyaVGXRX --force returned 1 instead of one of [0] > Sep 07 00:24:58 overcloud-controller-0.localdomain > os-collect-config[4781]: Error: /sbin/pcs cluster setup --name > tripleo_cluster overcloud-controller-0 returned 1 instead of one of > [0] > Sep 07 00:24:58 overcloud-controller-0.localdomain > os-collect-config[4781]: Error: > /Stage[main]/Pacemaker::Corosync/Exec[Create Cluster > tripleo_cluster]/returns: change from notrun to 0 failed: /sbin/pcs > cluster setup --name tripleo_cluster overcloud-controller-0 returned > 1 instead of one of [0] > Sep 07 00:24:58 overcloud-controller-0.localdomain > os-collect-config[4781]: Warning: > /Stage[main]/Pacemaker::Corosync/Exec[Start Cluster tripleo_cluster]: > Skipping because of failed dependencies > > This means that the cluster is not being set up correctly. > > Could you please check in /etc/hosts what is the content? > > I had a similar issue, but only on multi controller setup. > > > > -- > "E' assurdo impiegare gli uomini di intelligenza eccellente per fare > calcoli che potrebbero essere affidati a chiunque se si usassero delle > macchine" > Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) > > "Internet ? la pi? grande biblioteca del mondo. > Ma il problema ? che i libri sono tutti sparsi sul pavimento" > John Allen Paulos, Matematico (1945-vivente) > > Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , < > lorenzetto.luca at gmail.com> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorenzetto.luca at gmail.com Wed Sep 7 07:37:43 2016 From: lorenzetto.luca at gmail.com (Luca 'remix_tj' Lorenzetto) Date: Wed, 7 Sep 2016 09:37:43 +0200 Subject: [rdo-list] [TripleO] ControllerLoadBalancerDeployment_Step1 resource failed In-Reply-To: References: Message-ID: On Wed, Sep 7, 2016 at 9:32 AM, Samuel Monderer wrote: > [heat-admin at overcloud-controller-0 ~]$ cat /etc/hosts [cut] Seems ok. Try stracing (with -f ) this command on overcloud-controller-0: /sbin/pcs cluster auth overcloud-controller-0 -u hacluster -p u33uizaZhyaVGXRX --force And check what's the cause of returning 1 instead of going well. -- "E' assurdo impiegare gli uomini di intelligenza eccellente per fare calcoli che potrebbero essere affidati a chiunque se si usassero delle macchine" Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) "Internet ? la pi? grande biblioteca del mondo. Ma il problema ? che i libri sono tutti sparsi sul pavimento" John Allen Paulos, Matematico (1945-vivente) Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , From marius at remote-lab.net Wed Sep 7 12:11:12 2016 From: marius at remote-lab.net (Marius Cornea) Date: Wed, 7 Sep 2016 14:11:12 +0200 Subject: [rdo-list] [TripleO] ControllerLoadBalancerDeployment_Step1 resource failed In-Reply-To: References: Message-ID: On Wed, Sep 7, 2016 at 8:20 AM, Samuel Monderer wrote: > Hi, > > I have one controller and one compute node both with 3 NICs: IPMI,net1 and > net2 > I've based my overcloud configuration on the bond with vlans but I removed > the bond and just used a single NIC instead. > For the moment I don't need storage as my setup is a NFV cloud, so I removed > the storage network and storage-management network. The storage network is also used for the Glance API so by default it is used even though you're not deploying any storage nodes. I recommend section 6.2.4 of these docs which explains how to choose which networks to deploy: https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/paged/director-installation-and-usage/chapter-6-configuring-advanced-customizations-for-the-overcloud > Network configuration per node > > controller: > > IPMI > NIC1: > > Provioning Network > > NIC2 > > Internal Network > Tenant Network > Management Network > External Network > > compute > > IPMI > NIC1: > > Provioning Network > > NIC2 > > Internal Network > Tenant Network > Management Network Checking the attached network templates I see that you're setting the vlan interfaces as members of the physical interface. I'm not sure that works. I usually create a bridge and make the interface and the vlans members of it, e.g: http://paste.openstack.org/show/567426/ > By the way what is the management netwrok for? Is it for accesssing the > nodes without going through the director? The management network is typically used for providing external connectivity for non controller nodes. > I ran the deployment but the following resources failed > overcloud-ControllerNodesPostDeployment-4lpz4z4msgzz-ControllerLoadBalancerDeployment_Step1-nc4sfpp34a57 > overcloud-ControllerNodesPostDeployment-4lpz4z4msgzz > overcloud-ComputeNodesPostDeployment-ougcodme2eo2 > > When I checked the os-collect-config log on the controller I found that It > wasn't able to reach the mysql server (attached is the log file) > > Any Idea what could be the issue? First thing I'd check is if the network setting got applied by running 'ip a; ip r' > Attached are also the configuration files > > Regards, > Samuel > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From trown at redhat.com Wed Sep 7 15:44:43 2016 From: trown at redhat.com (John Trowbridge) Date: Wed, 7 Sep 2016 11:44:43 -0400 Subject: [rdo-list] [Cloud SIG][RDO] RDO meeting minutes - 2016-09-07 Message-ID: <45868214-0bd1-51ea-ee31-d770249312ad@redhat.com> ============================== #rdo: RDO meeting - 2016-09-07 ============================== Meeting started by number80 at 15:02:30 UTC. The full logs are available at https://meetbot.fedoraproject.org/rdo/2016-09-07/rdo_meeting_-_2016-09-07.2016-09-07-15.02.log.html . Meeting summary --------------- * roll call (number80, 15:02:35) * Test day readiness (trown, 15:05:22) * Moving redhat-openstack/tempest reviews from gerrithub to r.o.o (chandankumar) (trown, 15:09:37) * AGREED: leave tempest fork where it is and deprecate as soon as possible (trown, 15:15:44) * Adding repo files for CI-tested repos in buildlogs CDN (trown, 15:17:12) * Background: https://bugs.centos.org/view.php?id=11090 (trown, 15:17:37) * LINK: http://buildlogs.centos.org/centos/7/cloud/x86_64/rdo-trunk-master-tested/delorean.repo (number80, 15:20:55) * LINK: https://github.com/redhat-openstack/rdo-release/blob/newton/rdo-testing.repo (apevec, 15:21:43) * ACTION: jpena to create cart for CI part of using CDN, assign to weshay (jpena, 15:24:25) * newton-rdo branching status [hguemar] (trown, 15:26:38) * oslo libs are getting forked for newton (number80, 15:27:48) * everybody take over RDO-NEWTON reviews (apevec, 15:28:49) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=RDO-NEWTON (apevec, 15:29:01) * ACTION: apevec to report RDO-NEWTON progress for the next meeting (apevec, 15:29:57) * anouncements (trown, 15:31:05) * Newton milestone 3 test day is this Thursday and Friday. Please participate.https://www.rdoproject.org/testday/newton/milestone3/ (trown, 15:31:20) * Demos/Q&A at RDO booth at OpenStack Summit Barcelonad - signup at https://etherpad.openstack.org/p/rdo-barcelona-summit-booth (trown, 15:31:39) * Ping me (rbowen) ASAP if there's anything you want in the newsletter (going out later today) - https://github.com/rbowen/rdo-website/blob/master/source/newsletter/2016-september.html.md (trown, 15:31:54) * open floor (trown, 15:34:32) * next chair (trown, 15:39:57) * chandankumar to chair next meeting (trown, 15:41:49) Meeting ended at 15:42:00 UTC. Action Items ------------ * jpena to create cart for CI part of using CDN, assign to weshay * apevec to report RDO-NEWTON progress for the next meeting Action Items, by person ----------------------- * apevec * apevec to report RDO-NEWTON progress for the next meeting * jpena * jpena to create cart for CI part of using CDN, assign to weshay * weshay * jpena to create cart for CI part of using CDN, assign to weshay * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * apevec (59) * trown (42) * number80 (26) * dmellado (19) * zodbot (10) * chandankumar (10) * weshay (9) * jpena (8) * openstack (6) * social_ (4) * rbowen (3) * imcsk8 (3) * snarwade (2) * jruzicka (2) * atarakt (2) * coolsvap (1) * flepied (1) * myoung (1) * Duck (1) * jschlueter (1) * afazekas (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From dms at redhat.com Wed Sep 7 18:58:58 2016 From: dms at redhat.com (David Moreau Simard) Date: Wed, 7 Sep 2016 14:58:58 -0400 Subject: [rdo-list] Upcoming OpenStack meetups In-Reply-To: References: Message-ID: There's an OpenStack Montreal meetup next week September 13th. Eventbrite: https://www.eventbrite.ca/e/12th-openstack-montreal-meeting-tickets-27534202541 David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Tue, Sep 6, 2016 at 11:52 AM, Rich Bowen wrote: > The following are the meetups I'm aware of in the coming week where > OpenStack and/or RDO enthusiasts are likely to be present. If you know > of others, please let me know, and/or add them to > http://rdoproject.org/events > > If there's a meetup in your area, please consider attending. If you > attend, please consider taking a few photos, and possibly even writing > up a brief summary of what was covered. > > --Rich > > * Wednesday September 07 in Richardson, TX, US: ETSI NFV-SEC - best > practices - http://www.meetup.com/OpenStack-DFW/events/233744324/ > > * Wednesday September 07 in San Francisco, CA, US: Containers and > OpenStack - http://www.meetup.com/openstack/events/233227736/ > > * Thursday September 08 in Pittsburgh, PA, US: The Red Hat OpenStack > Platform - > http://www.meetup.com/Pittsburgh-Red-Hat-User-Group/events/233282275/ > > * Thursday September 08 in Reston, VA, US: OpenStack meetup on > contributions in the OpenStack community! - > http://www.meetup.com/OpenStack-Nova/events/232971596/ > > * Friday September 09 in Guadalajara, MX: Hackathon de Aplicaciones en > OpenStack - http://www.meetup.com/OpenStack-GDL/events/232288032/ > > * Saturday September 10 in North York, ON, CA: OpenStack Administration > - Success & Failures of the Cloud Adoption - > http://www.meetup.com/StackDocker-TO/events/232473294/ > > > > -- > Rich Bowen - rbowen at redhat.com > RDO Community Liaison > http://rdoproject.org > @RDOCommunity > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From bderzhavets at hotmail.com Thu Sep 8 06:48:04 2016 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Thu, 8 Sep 2016 06:48:04 +0000 Subject: [rdo-list] Failure to build minimal Kubernetes cluster on top of RDO Mitaka CentOS 7.2 In-Reply-To: <45868214-0bd1-51ea-ee31-d770249312ad@redhat.com> References: <45868214-0bd1-51ea-ee31-d770249312ad@redhat.com> Message-ID: Here is tutorial working for RHEL 7 http://alesnosek.com/blog/2016/06/26/deploying-kubernetes-on-openstack-using-heat/ Attempt to reproduce on CentOS 7.2 generates heat-engine.log http://textuploader.com/58zzu what amazingly results stack kubernetes to be successfully deployed , but Kub-Master cloud VM launches without any httpd daemon running in SSL mode .All details described here :- http://bderzhavets.blogspot.ru/2016/08/attempt-to-reproduce-deploying.html My question is :- Are following openstack clients python-senlinclient python-zaqarclient python-magnumclient python-mistralclient supposed to be packaged for RDO Newton I am aware of https://bugzilla.redhat.com/show_bug.cgi?id=1294489 and also pretty sure that RHOSP 9 has all this clients packaged due to successful reproducing (not by myself) mentioned Howto by Ales Nosek . Thank you. Boris. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at hotmail.com Thu Sep 8 08:18:07 2016 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Thu, 8 Sep 2016 08:18:07 +0000 Subject: [rdo-list] Failure to build minimal Kubernetes cluster on top of RDO Mitaka CentOS 7.2 In-Reply-To: References: <45868214-0bd1-51ea-ee31-d770249312ad@redhat.com>, Message-ID: Bug opened https://bugzilla.redhat.com/show_bug.cgi?id=1374183 ________________________________ From: rdo-list-bounces at redhat.com on behalf of Boris Derzhavets Sent: Thursday, September 8, 2016 9:48 AM To: Alan Pevec; 'rdo-list' Subject: [rdo-list] Failure to build minimal Kubernetes cluster on top of RDO Mitaka CentOS 7.2 Here is tutorial working for RHEL 7 http://alesnosek.com/blog/2016/06/26/deploying-kubernetes-on-openstack-using-heat/ Attempt to reproduce on CentOS 7.2 generates heat-engine.log http://textuploader.com/58zzu what amazingly results stack kubernetes to be successfully deployed , but Kub-Master cloud VM launches without any httpd daemon running in SSL mode .All details described here :- http://bderzhavets.blogspot.ru/2016/08/attempt-to-reproduce-deploying.html My question is :- Are following openstack clients python-senlinclient python-zaqarclient python-magnumclient python-mistralclient supposed to be packaged for RDO Newton I am aware of https://bugzilla.redhat.com/show_bug.cgi?id=1294489 and also pretty sure that RHOSP 9 has all this clients packaged due to successful reproducing (not by myself) mentioned Howto by Ales Nosek . Thank you. Boris. -------------- next part -------------- An HTML attachment was scrubbed... URL: From javier.pena at redhat.com Thu Sep 8 10:59:08 2016 From: javier.pena at redhat.com (Javier Pena) Date: Thu, 8 Sep 2016 06:59:08 -0400 (EDT) Subject: [rdo-list] [CI] [TripleO] rdo-promote-upload-master job times out In-Reply-To: <571772680.10337830.1473331735149.JavaMail.zimbra@redhat.com> Message-ID: <1265638015.10340540.1473332348748.JavaMail.zimbra@redhat.com> Hi all, Just a quick FYI, the rdo-promote-upload-master job is now timing out. It looks like the 15-minute timeout is not enough now that we are uploading the images to images.rdoproject.org I've proposed https://review.gerrithub.io/290587. Please give it a deep look, I'm not too familiar with jjb and may have made a dumb mistake. Thanks, Javier From rbowen at redhat.com Thu Sep 8 12:06:34 2016 From: rbowen at redhat.com (Rich Bowen) Date: Thu, 8 Sep 2016 08:06:34 -0400 Subject: [rdo-list] [Rdo-newsletter] RDO Community Newsletter, September 2016 Message-ID: <32ed93b8-dfc9-1471-ac32-c2aa9403793c@redhat.com> If you have trouble with the formatting, this newsletter may also be found at http://rdoproject.org//newsletter/2016-september September 2016 RDO Community Newsletter Quick links: * Quick Start * Mailing Lists * RDO release packages * Review.RDOProject.org * RDO blog * Q&A * Open Tickets * Twitter * Newton release schedule Thanks for being part of the RDO community! Newton milestone 3 test day Please join us on Thursday and Friday of this week to test the RDO packages of the Newton milestone 3 release. Milestone 3 released upstream last week, and we've been packaging and running CI on that since then. We think Newton is going to be the best release of OpenStack yet, and we need your help to ensure that this is the case. We'll be gathering on the #rdo channel on the Freenode IRC network, as well as posting our findings to the rdo-list mailing list. For more information about this test day, see the test day web page . And we're just a few weeks out from the scheduled Newton release , on the week of October 3rd. OpenStack Summit coming soon OpenStack Summit is just a few weeks away - October 25-29 in Barcelona, Spain - and we would love to see you there. We'll be in the expo hall, in booth D1, on the right, just inside the main entrance. If there's something interesting that you've done with RDO that you'd like to demo at our pod, or if you just want to help answer RDO questions, please let me know - we'd love to have you as part of our demo schedule. We also expect to have a community meetup at the Summit, as we usually do. Details are still being worked out. We'll notify the rdo-list mailing list as soon we we have a time and place confirmed. You can register for the summit at openstack.org/summit . Upcoming events In addition to OpenStack Summit, RDO will have a presence at a number of other upcoming events. Each week, upcoming meetups are posted to rdo-list, and also to the RDO events calendar . In particular, you will want to mark your calendar for the following events: * The Red Hat OpenStack Platform , September 8th in Pittsburgh. * MAD for OpenStack , Madrid. September 14th. * PyCon India , September 24th and 25th in New Delhi. * LinuxDays Prague , October 8th and 9th. Contributing to the documentation With the Newton release just around the corner, it's a good time to refresh the website and the documentation. If you'd like to help with this effort, here's what you need to get started. Clone the Git repository at https://github.com/redhat-openstack/website and follow the instructions in the README to get a local version of the website running. Look through the site, and identify documents that are outdated, incorrect, or anything that you feel is missing. You can either correct these yourself, and send pull requests, or open tickets athttps://github.com/redhat-openstack/website/issues. Where we particularly need help is identifying documents that need to be written. To this end, we need the help of beginners, to go through the website, and see what information you need, which isn't readily available. Community meeting Ever Wednesday at 15:00 UTC, we have the weekly RDO community meeting on the #RDO channel on Freenode IRC. And at 15:00 UTC Thursdays, we have the CentOS Cloud SIG Meeting on #centos-devel. The agendas, and minutes, from these meetings, may be found in the rdo-list mail archives each week. The meeting typically covers everything from project status, to upcoming event participation, to discussion of technical decisions. Major decisions are always taken back to the mailing list for consideration by the wider community. Keep in touch There's lots of ways to stay in in touch with what's going on in the RDO community. The best ways are ? WWW * RDO * Project Status * OpenStack Q&A Mailing Lists: * rdo-list mailing list * This newsletter IRC * IRC - #rdo on Freenode.irc.net * Puppet module development - #rdo-puppet Social Media * Follow us on Twitter * Google+ * Facebook Thanks again for being part of the RDO community! -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Rdo-newsletter mailing list Rdo-newsletter at redhat.com https://www.redhat.com/mailman/listinfo/rdo-newsletter From mburns at redhat.com Fri Sep 9 12:29:09 2016 From: mburns at redhat.com (Mike Burns) Date: Fri, 9 Sep 2016 08:29:09 -0400 Subject: [rdo-list] Adding backwards compatible tripleo-heat-templates packaging In-Reply-To: <376215178.9458025.1473086870132.JavaMail.zimbra@redhat.com> References: <376215178.9458025.1473086870132.JavaMail.zimbra@redhat.com> Message-ID: On Mon, Sep 5, 2016 at 10:47 AM, Javier Pena wrote: > > > ----- Original Message ----- >> On Fri, Sep 2, 2016 at 6:04 PM, Alan Pevec wrote: >> >> * A single srpm if at all possible >> > >> > Why is that a requirement? Usually in rpm world you create separate >> > parallel installable compat package by adding version to the package >> > name e.g. we had python-webob1.2 in the past. >> > THT mitaka is 2.x so what about creating a new package >> > openstack-tripleo-heat-templates2 ? >> >> We could do that and it's ok, really. It just means a new package >> process for every release of OpenStack. There is no real clean >> mapping historically of THT version to OpenStack version. How does >> someone know that tht2 is mitaka? When we reach ocata and have to >> have a BC package, it's tht5 which is newton. (We could simply name >> it openstack-tripleo-heat-templates-mitaka). > > I think something like this (having an openstack-tripleo-heat-templates-compat-mitaka package or similar) would work best. > > This would also allow us to decide when to drop support for older releases. Newton will have a mitaka-compat package, but we'll sure drop it in a later release, won't we? We could then just control which packages are built for each release using rdoinfo. > > Javier If we do this, *every* release will drop a package and add a package. The tripleo team won't commit to supporting more than 1 version back currently, so -mitaka would only be included with the newton release. In Ocata, we'd drop mitaka and add -newton. This is part of the reason that a single tarball made things easier. Just get the right source tarball for old release and build it in a single package. An update per release in a single spec file is generally easier than a new package. Mike >> >> The proposal currently means that we have to change 1 spec file value >> per release rather than go through a totally new package each release. >> >> Mike >> >> >> > >> > Alan >> >> _______________________________________________ >> rdo-list mailing list >> rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> To unsubscribe: rdo-list-unsubscribe at redhat.com >> From chkumar246 at gmail.com Fri Sep 9 14:23:39 2016 From: chkumar246 at gmail.com (Chandan kumar) Date: Fri, 9 Sep 2016 19:53:39 +0530 Subject: [rdo-list] Tempest Packaging in RDO In-Reply-To: References: <731736690.7134214.1472544177263.JavaMail.zimbra@redhat.com> Message-ID: Hello, On Tue, Sep 6, 2016 at 7:50 PM, David Moreau Simard wrote: > On Tue, Aug 30, 2016 at 4:02 AM, Javier Pena wrote: >> Updates on tempest packaging: * https://review.rdoproject.org/r/#/c/2136/ got merged. The above review provides python-tempest, python-tempest-tests and openstack-tempest-all subpackage. * In order to use tempest as a library, python-tempest subpackage is added. * To install all the tempest plugins in one go, openstack-tempest-all subpackage is added. * openstack-tempest package will install only tempest library and its executables The current tempest packages can be pulled from this dlrn repo : https://trunk.rdoproject.org/centos7-master/consistent/delorean.repo >I'd really like to remove the tempest dependency for designate-tests and horizon-tests soon, at least to unblock part of the issues (not being able to properly test designate/horizon without pulling the whole Tempest lot with it). > > Yes, please. I would love the review for designate-tests [1] to land > so we can unblock designate testing and be confident to ship a tested > and working designate for Newton. > > [1]: https://review.rdoproject.org/r/#/c/1820/ > Python-tempest subpackage solves the above problem. Since it can be used a tempest library. Thanks, Chandan Kumar From alon.dotan at hpe.com Mon Sep 12 11:37:53 2016 From: alon.dotan at hpe.com (Dotan, Alon) Date: Mon, 12 Sep 2016 11:37:53 +0000 Subject: [rdo-list] sriov in mitaka / newton Message-ID: Someone tried to use SRIOV in mitaka, newton? I can't make it work with the exact same configuration that working under kilo / liberty I saw a lot of code changes in the area of pci passthrough in neutron Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Mon Sep 12 14:58:17 2016 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 12 Sep 2016 10:58:17 -0400 Subject: [rdo-list] Tuesday night at OpenStack Summit: RDO Community Meetup! (Speakers needed) Message-ID: <61f445e0-ce64-b89d-a38d-586ad9c5598f@redhat.com> On Tuesday night at OpenStack Summit, we will be sharing a lovely space with the Ceph community for our RDO community meetup. (This is still roughly 75% confirmed. Details still being worked out.) Date: Tuesday, October 25th Time: (Tentatively) 5pm - 8pm, between the day sessions and the various scheduled evening events Where: Less than 2 minutes walk from the venue, at the Barcelona Princess: http://en.hotelbarcelonaprincess.com/restaurants/the-gym-bar/ What: Light hors d'oeuvres and drinks, and the Ceph/RDO community meetup Because we're sharing space with another project, we need to be more careful about our schedule than we have been in the past. The plan at the moment is to do this lightning-talk style. To that end, I need to identify 5-7 people who will be willing to present very briefly on the various items of interest to our community. Please indicate your availability, and the topic you are willing to cover in around 5 minutes, on this etherpad: https://etherpad.openstack.org/p/rdo-barcelona-meetup-schedule We will have a mic and a projector/screen, so if you need to present something for us to see, you'll be able to do that. Patrick and I will then make a schedule alternating the RDO stuff and the Ceph stuff, and these presentations will be followed by light refreshments, drinks, and the opportunity to have informal discussions to dive deeper into any topics that were covered in the first half. For reference and ideas of topics, here's our schedule from Austin. https://etherpad.openstack.org/p/rdo-austin-bof Hoping to see you in Barcelona, Rich -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From hguemar at fedoraproject.org Mon Sep 12 15:00:03 2016 From: hguemar at fedoraproject.org (hguemar at fedoraproject.org) Date: Mon, 12 Sep 2016 15:00:03 +0000 (UTC) Subject: [rdo-list] [Fedocal] Reminder meeting : RDO meeting Message-ID: <20160912150003.DF92560A4003@fedocal02.phx2.fedoraproject.org> Dear all, You are kindly invited to the meeting: RDO meeting on 2016-09-14 from 15:00:00 to 16:00:00 UTC At rdo at 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/ From dms at redhat.com Mon Sep 12 15:19:47 2016 From: dms at redhat.com (David Moreau Simard) Date: Mon, 12 Sep 2016 11:19:47 -0400 Subject: [rdo-list] Tuesday night at OpenStack Summit: RDO Community Meetup! (Speakers needed) In-Reply-To: <61f445e0-ce64-b89d-a38d-586ad9c5598f@redhat.com> References: <61f445e0-ce64-b89d-a38d-586ad9c5598f@redhat.com> Message-ID: Do we know yet if there are sponsored summit events on tuesday evening ? I could see that having an impact on the attendance. David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Mon, Sep 12, 2016 at 10:58 AM, Rich Bowen wrote: > On Tuesday night at OpenStack Summit, we will be sharing a lovely space > with the Ceph community for our RDO community meetup. (This is still > roughly 75% confirmed. Details still being worked out.) > > Date: Tuesday, October 25th > Time: (Tentatively) 5pm - 8pm, between the day sessions and the various > scheduled evening events > Where: Less than 2 minutes walk from the venue, at the Barcelona > Princess: http://en.hotelbarcelonaprincess.com/restaurants/the-gym-bar/ > What: Light hors d'oeuvres and drinks, and the Ceph/RDO community meetup > > Because we're sharing space with another project, we need to be more > careful about our schedule than we have been in the past. The plan at > the moment is to do this lightning-talk style. To that end, I need to > identify 5-7 people who will be willing to present very briefly on the > various items of interest to our community. > > Please indicate your availability, and the topic you are willing to > cover in around 5 minutes, on this etherpad: > https://etherpad.openstack.org/p/rdo-barcelona-meetup-schedule > We will have a mic and a projector/screen, so if you need to present > something for us to see, you'll be able to do that. > > Patrick and I will then make a schedule alternating the RDO stuff and > the Ceph stuff, and these presentations will be followed by light > refreshments, drinks, and the opportunity to have informal discussions > to dive deeper into any topics that were covered in the first half. > > For reference and ideas of topics, here's our schedule from Austin. > https://etherpad.openstack.org/p/rdo-austin-bof > > Hoping to see you in Barcelona, > Rich > > -- > Rich Bowen - rbowen at redhat.com > RDO Community Liaison > http://rdoproject.org > @RDOCommunity > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From rbowen at redhat.com Mon Sep 12 16:18:49 2016 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 12 Sep 2016 12:18:49 -0400 Subject: [rdo-list] ask.openstack unanswered 'RDO' questions 2016-09-12 Message-ID: <2e048860-9d23-d5a9-c734-c3dd80292862@redhat.com> 28 unanswered questions: After adding multiple compute nodes using packstack unable to see the nodes in dashboard https://ask.openstack.org/en/question/96732/after-adding-multiple-compute-nodes-using-packstack-unable-to-see-the-nodes-in-dashboard/ Tags: rdo Error: Unable to get the Swift container listing https://ask.openstack.org/en/question/96658/error-unable-to-get-the-swift-container-listing/ Tags: swift, containers, rdo [trove] mongodb cluster-grow failed https://ask.openstack.org/en/question/96571/trove-mongodb-cluster-grow-failed/ Tags: trove, mongodb, cluster, grow Error during LBAAS installation (Load Balancer) https://ask.openstack.org/en/question/96511/error-during-lbaas-installation-load-balancer/ Tags: rdo, lbaasv2, mitaka-neutron, centos7, loadbalancer quota show is different from horizon in RDO after update quota with command https://ask.openstack.org/en/question/96244/quota-show-is-different-from-horizon-in-rdo-after-update-quota-with-command/ Tags: rdo how to set quota with python https://ask.openstack.org/en/question/96231/how-to-set-quota-with-python/ Tags: quota "Parameter outiface failed on Firewall" during installation of openstack rdo on centos 7 https://ask.openstack.org/en/question/95657/parameter-outiface-failed-on-firewall-during-installation-of-openstack-rdo-on-centos-7/ Tags: rdo, devstack#mitaka multi nodes provider network ovs config https://ask.openstack.org/en/question/95423/multi-nodes-provider-network-ovs-config/ Tags: rdo, liberty-neutron Adding additional packages to an RDO installation https://ask.openstack.org/en/question/95380/adding-additional-packages-to-an-rdo-installation/ Tags: rdo, mistral RDO TripleO Mitaka HA Overcloud Failing https://ask.openstack.org/en/question/95249/rdo-tripleo-mitaka-ha-overcloud-failing/ Tags: mitaka, tripleo, overcloud, centos7 RDO - is there any fedora package newer than puppet-4.2.1-3.fc24.noarch.rpm https://ask.openstack.org/en/question/94969/rdo-is-there-any-fedora-package-newer-than-puppet-421-3fc24noarchrpm/ Tags: rdo, puppet, install-openstack OpenStack RDO mysqld 100% cpu https://ask.openstack.org/en/question/94961/openstack-rdo-mysqld-100-cpu/ Tags: openstack, mysqld, cpu Failed to set RDO repo on host-packstack-centOS-7 https://ask.openstack.org/en/question/94828/failed-to-set-rdo-repo-on-host-packstack-centos-7/ Tags: openstack-packstack, centos7, rdo how to deploy haskell-distributed in RDO? https://ask.openstack.org/en/question/94785/how-to-deploy-haskell-distributed-in-rdo/ Tags: rdo rdo tripleO liberty undercloud install failing https://ask.openstack.org/en/question/94023/rdo-tripleo-liberty-undercloud-install-failing/ Tags: rdo, rdo-manager, liberty, undercloud, instack Liberty RDO: stack resource topology icons are pink https://ask.openstack.org/en/question/91347/liberty-rdo-stack-resource-topology-icons-are-pink/ Tags: resource, topology, dashboard, horizon, pink No handlers could be found for logger "oslo_config.cfg" while syncing the glance database https://ask.openstack.org/en/question/91169/no-handlers-could-be-found-for-logger-oslo_configcfg-while-syncing-the-glance-database/ Tags: liberty, glance, install-openstack CentOS OpenStack - compute node can't talk https://ask.openstack.org/en/question/88989/centos-openstack-compute-node-cant-talk/ Tags: rdo How to setup SWIFT_PROXY_NODE and SWIFT_STORAGE_NODEs separately on RDO Liberty ? https://ask.openstack.org/en/question/88897/how-to-setup-swift_proxy_node-and-swift_storage_nodes-separately-on-rdo-liberty/ Tags: rdo, liberty, swift, ha VM and container can't download anything from internet https://ask.openstack.org/en/question/88338/vm-and-container-cant-download-anything-from-internet/ Tags: rdo, neutron, network, connectivity Fedora22, Liberty, horizon VNC console and keymap=sv with ; and/ https://ask.openstack.org/en/question/87451/fedora22-liberty-horizon-vnc-console-and-keymapsv-with-and/ Tags: keyboard, map, keymap, vncproxy, novnc OpenStack-Docker driver failed https://ask.openstack.org/en/question/87243/openstack-docker-driver-failed/ Tags: docker, openstack, liberty Routing between two tenants https://ask.openstack.org/en/question/84645/routing-between-two-tenants/ Tags: kilo, fuel, rdo, routing openstack baremetal introspection internal server error https://ask.openstack.org/en/question/82790/openstack-baremetal-introspection-internal-server-error/ Tags: rdo, ironic-inspector, tripleo Installing openstack using packstack (rdo) failed https://ask.openstack.org/en/question/82473/installing-openstack-using-packstack-rdo-failed/ Tags: rdo, packstack, installation-error, keystone VMware Host Backend causes No valid host was found. Bug ??? https://ask.openstack.org/en/question/79738/vmware-host-backend-causes-no-valid-host-was-found-bug/ Tags: vmware, rdo Mutlinode Devstack with two interfaces https://ask.openstack.org/en/question/78615/mutlinode-devstack-with-two-interfaces/ Tags: devstack, vlan, openstack Overcloud deployment on VM fails as IP address from DHCP is not assigned https://ask.openstack.org/en/question/66272/overcloud-deployment-on-vm-fails-as-ip-address-from-dhcp-is-not-assigned/ Tags: overcloud_in_vm -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From alejandro at midokura.com Mon Sep 12 16:27:33 2016 From: alejandro at midokura.com (Alejandro Andreu) Date: Mon, 12 Sep 2016 18:27:33 +0200 Subject: [rdo-list] [TripleO] How to build disk images? Message-ID: <1925011c-70e2-401e-fcf0-1046493fd8ee@midokura.com> Hi all, I need to update an image in the tripleo-puppet-elements repository[0]. More precisely, I need to update "overcloud-network-midonet". Before pushing changes upstream I would like to build and test the images locally, but I'm having issues finding documentation to do so. I found a tripleo-incubator doc[1], but I'm not sure this is what I'm looking for, or if it is indeed outdated. Or is there another way to build the images? Also, the README in [0] does not work. Can you please point me in the right direction here? Best regards, Alejandro Andreu [0]: https://github.com/openstack/tripleo-puppet-elements [1]: http://docs.openstack.org/developer/tripleo-incubator/puppet.html From rbowen at redhat.com Mon Sep 12 16:46:31 2016 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 12 Sep 2016 12:46:31 -0400 Subject: [rdo-list] Tuesday night at OpenStack Summit: RDO Community Meetup! (Speakers needed) In-Reply-To: References: <61f445e0-ce64-b89d-a38d-586ad9c5598f@redhat.com> Message-ID: On 09/12/2016 11:19 AM, David Moreau Simard wrote: > Do we know yet if there are sponsored summit events on tuesday evening ? > > I could see that having an impact on the attendance. There are not any published yet, but there are *always* events, and they typically start sometime around 7 or 8. So We're trying to get into that gap between sessions and the evening activities, and also have a little party of our own to try to hold onto a few of you a little longer into the evening. --Rich > > On Mon, Sep 12, 2016 at 10:58 AM, Rich Bowen wrote: >> On Tuesday night at OpenStack Summit, we will be sharing a lovely space >> with the Ceph community for our RDO community meetup. (This is still >> roughly 75% confirmed. Details still being worked out.) >> >> Date: Tuesday, October 25th >> Time: (Tentatively) 5pm - 8pm, between the day sessions and the various >> scheduled evening events >> Where: Less than 2 minutes walk from the venue, at the Barcelona >> Princess: http://en.hotelbarcelonaprincess.com/restaurants/the-gym-bar/ >> What: Light hors d'oeuvres and drinks, and the Ceph/RDO community meetup >> >> Because we're sharing space with another project, we need to be more >> careful about our schedule than we have been in the past. The plan at >> the moment is to do this lightning-talk style. To that end, I need to >> identify 5-7 people who will be willing to present very briefly on the >> various items of interest to our community. >> >> Please indicate your availability, and the topic you are willing to >> cover in around 5 minutes, on this etherpad: >> https://etherpad.openstack.org/p/rdo-barcelona-meetup-schedule >> We will have a mic and a projector/screen, so if you need to present >> something for us to see, you'll be able to do that. >> >> Patrick and I will then make a schedule alternating the RDO stuff and >> the Ceph stuff, and these presentations will be followed by light >> refreshments, drinks, and the opportunity to have informal discussions >> to dive deeper into any topics that were covered in the first half. >> >> For reference and ideas of topics, here's our schedule from Austin. >> https://etherpad.openstack.org/p/rdo-austin-bof >> >> Hoping to see you in Barcelona, >> Rich >> >> -- >> Rich Bowen - rbowen at redhat.com >> RDO Community Liaison >> http://rdoproject.org >> @RDOCommunity >> >> _______________________________________________ >> rdo-list mailing list >> rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> To unsubscribe: rdo-list-unsubscribe at redhat.com -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From rbowen at redhat.com Mon Sep 12 17:56:48 2016 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 12 Sep 2016 13:56:48 -0400 Subject: [rdo-list] Upcoming OpenStack/RDO meetups Message-ID: <18b0cf15-b894-e945-eb22-196f79674992@redhat.com> The following are the meetups I'm aware of in the coming week where OpenStack and/or RDO enthusiasts are likely to be present. If you know of others, please let me know, and/or add them to http://rdoproject.org/events If there's a meetup in your area, please consider attending. If you attend, please consider taking a few photos, and possibly even writing up a brief summary of what was covered. --Rich * Tuesday September 13 in Tokyo, JP: ??OpenStack???? ?29???? - http://www.meetup.com/Japan-OpenStack-User-Group/events/234055784/ * Tuesday September 13 in Montreal, CA: 12th Openstack Montreal Meeting - https://www.eventbrite.ca/e/12th-openstack-montreal-meeting-tickets-27534202541 * Wednesday September 14 in Stuttgart, DE: Meet [IBM] OpenStack Experts - http://www.meetup.com/OpenStack-Baden-Wuerttemberg/events/232734769/ * Wednesday September 14 in Madrid, ES: Mad for OpenStack, el regreso - http://www.meetup.com/MAD-for-OpenStack/events/233790123/ * Thursday September 15 in Oslo, NO: OpenStack Forum #4 - http://www.meetup.com/Oslo-OpenStack-Forum/events/231795306/ * Thursday September 15 in Boston, MA, US: Containers in OpenStack: An Overview - http://www.meetup.com/Openstack-Boston/events/233939844/ * Thursday September 15 in Portland, OR, US: OpenStack PDX Meetup - http://www.meetup.com/openstack-pdx/events/232271957/ * Thursday September 15 in Chicago, IL, US: Dude, where's my control plane? - http://www.meetup.com/meetup-group-NjZdcegA/events/233952974/ * Thursday September 15 in Austin, TX, US: OpenStack and Lean Coffee!! - http://www.meetup.com/OpenStack-Austin/events/233958722/ * Thursday September 15 in San Francisco, CA, US: Stacki, Ansible, & OpenStack with Flex - http://www.meetup.com/openstack/events/233946117/ * Thursday September 15 in San Francisco, CA, US: San Jose Meetup: Stacki, Ansible, & OpenStack with Flex - http://www.meetup.com/Stacki-San-Francisco/events/233796796/ * Thursday September 15 in Atlanta, GA, US: OpenStack Meetup - Deployment - http://www.meetup.com/openstack-atlanta/events/233303136/ * Thursday September 15 in Antwerpen, BE: 6th Birthday meetup + Speaker: Alan Clark - Chairman of the Openstack Foundation - http://www.meetup.com/OpenStack-Belgium-Meetup/events/232028068/ * Friday September 16 in Abidjan, CI: Anniversaire 6 ans Openstack, Presentation du Cloud Openstack - http://www.meetup.com/Openstack-Cote-divoire/events/233876577/ -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From apevec at redhat.com Mon Sep 12 21:30:00 2016 From: apevec at redhat.com (Alan Pevec) Date: Mon, 12 Sep 2016 23:30:00 +0200 Subject: [rdo-list] Is Keystone/Identity-v3 supported by RDO Packstack? Multi-node swift --answer-file? In-Reply-To: References: <187458073.6327797.1472229179556.JavaMail.zimbra@redhat.com> <89e654f1-261f-3967-a998-5ee92b69c273@redhat.com> Message-ID: > I believe that RDO package maintainers are supposed to perform patching > (done locally in my posting to Linux.com) and make this back ports to official RDO > Mitaka repos, to avoid compromising RDO QuickStart Page. By some reasons it didn't happen. We've been busy wrapping up Newton release, but in the meantime until we have next round of minor updates pushed to Mitaka stable repos, you can use rdo-trunk-mitaka-tested repo with "nightlies" which passed CI, it is available in rdo-release-mitaka-5 (yum install https://rdoproject.org/repos/openstack-mitaka/rdo-release-mitaka.rpm to update): https://github.com/redhat-openstack/rdo-release/blob/mitaka/rdo-testing.repo#L7-L11 Those are RPMs built from stable/mitaka branches so they have all backports merged upstream, you don't need to patch manually. Alan From apevec at redhat.com Mon Sep 12 21:32:54 2016 From: apevec at redhat.com (Alan Pevec) Date: Mon, 12 Sep 2016 23:32:54 +0200 Subject: [rdo-list] Is Keystone/Identity-v3 supported by RDO Packstack? Multi-node swift --answer-file? In-Reply-To: References: <187458073.6327797.1472229179556.JavaMail.zimbra@redhat.com> <89e654f1-261f-3967-a998-5ee92b69c273@redhat.com> Message-ID: > can use rdo-trunk-mitaka-tested repo with "nightlies" which passed CI, > it is available in rdo-release-mitaka-5 (yum install > https://rdoproject.org/repos/openstack-mitaka/rdo-release-mitaka.rpm > to update): Forgot to mention, it is not enabled by default, so after updating rdo-release-mitaka you need to enable it: # yum-config-manager --enable rdo-trunk-mitaka-tested From whayutin at redhat.com Mon Sep 12 21:37:21 2016 From: whayutin at redhat.com (Wesley Hayutin) Date: Mon, 12 Sep 2016 17:37:21 -0400 Subject: [rdo-list] [ci] FYI all rdo promotion jobs have been disabled Message-ID: Greetings, I have disabled all the RDO promotion jobs until such time we have confirmed that images are published directly from the virthost to the ci.centos artifacts server. This work is being lead by Matt Young and tested and refined by John Trowbridge and myself. If there are any requirements for promotion while this work is done we will utilize the internal pipeline. Thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: From dms at redhat.com Mon Sep 12 21:52:38 2016 From: dms at redhat.com (David Moreau Simard) Date: Mon, 12 Sep 2016 17:52:38 -0400 Subject: [rdo-list] [ci] FYI all rdo promotion jobs have been disabled In-Reply-To: References: Message-ID: Can we keep the promotion jobs enabled and just disable the jobs that actually upload the images ? We need visibility on ongoing issues, if there are any, and the jobs have already been disabled since test day last week. David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Mon, Sep 12, 2016 at 5:37 PM, Wesley Hayutin wrote: > Greetings, > > I have disabled all the RDO promotion jobs until such time we have confirmed > that images are published directly from the virthost to the ci.centos > artifacts server. > > This work is being lead by Matt Young and tested and refined by John > Trowbridge and myself. If there are any requirements for promotion while > this work is done we will utilize the internal pipeline. > > Thank you > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From whayutin at redhat.com Mon Sep 12 21:54:04 2016 From: whayutin at redhat.com (Wesley Hayutin) Date: Mon, 12 Sep 2016 17:54:04 -0400 Subject: [rdo-list] [ci] FYI all rdo promotion jobs have been disabled In-Reply-To: References: Message-ID: On Mon, Sep 12, 2016 at 5:52 PM, David Moreau Simard wrote: > Can we keep the promotion jobs enabled and just disable the jobs that > actually upload the images ? > > We need visibility on ongoing issues, if there are any, and the jobs > have already been disabled since test day last week. > Ya.. that is a better idea.. will adjust them. Thanks > > David Moreau Simard > Senior Software Engineer | Openstack RDO > > dmsimard = [irc, github, twitter] > > > On Mon, Sep 12, 2016 at 5:37 PM, Wesley Hayutin > wrote: > > Greetings, > > > > I have disabled all the RDO promotion jobs until such time we have > confirmed > > that images are published directly from the virthost to the ci.centos > > artifacts server. > > > > This work is being lead by Matt Young and tested and refined by John > > Trowbridge and myself. If there are any requirements for promotion while > > this work is done we will utilize the internal pipeline. > > > > Thank you > > > > _______________________________________________ > > rdo-list mailing list > > rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > To unsubscribe: rdo-list-unsubscribe at redhat.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From apevec at redhat.com Wed Sep 14 08:59:21 2016 From: apevec at redhat.com (Alan Pevec) Date: Wed, 14 Sep 2016 10:59:21 +0200 Subject: [rdo-list] Adding backwards compatible tripleo-heat-templates packaging In-Reply-To: References: <376215178.9458025.1473086870132.JavaMail.zimbra@redhat.com> Message-ID: >> I think something like this (having an openstack-tripleo-heat-templates-compat-mitaka package or similar) would work best. >> >> This would also allow us to decide when to drop support for older releases. Newton will have a mitaka-compat package, but we'll sure drop it in a later release, won't we? We could then just control which packages are built for each release using rdoinfo. > > If we do this, *every* release will drop a package and add a package. > The tripleo team won't commit to supporting more than 1 version back > currently, so -mitaka would only be included with the newton release. If that's defined in a tripleo spec, please provide a link. > In Ocata, we'd drop mitaka and add -newton. This is part of the > reason that a single tarball made things easier. Just get the right > source tarball for old release and build it in a single package. An > update per release in a single spec file is generally easier than a > new package. How is that done in upstream tripleoci jobs which is testing upgrade? Is that just checking out stable branch? Link please :) Problmem with the proposed change is how to supply Source1 to Trunk builders, currently it handles only single Source0 by replacing it with the tarball generated from the git checkout. We would have to keep full Source1 tarball in the distgit and manually keep it in sync with the stable source branch. While this might look like a nail-hammer tool deficiency, tracking two branches in the same package is really adding unnecessary complexity. What about adding a new package openstack-tripleo-heat-templates-compat which would be configured in rdoinfo to take Source0 from the previous stable branch and only that metadata would get updated for the new release e.g. - project: tripleo-heat-templates-compat tags: newton-uc: source-branch: stable/mitaka newton: source-branch: stable/mitaka mitaka: source-branch: stable/liberty conf: rpmfactory-core maintainers: - mburns at redhat.com It would install into {_datadir}/%{name}/%{old_name} and openstack-tripleo-heat-templates could have Requires: openstack-tripleo-heat-templates-compat so that no changes are required in the installer. Cheers, Alan From bderzhavets at hotmail.com Wed Sep 14 12:29:01 2016 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Wed, 14 Sep 2016 12:29:01 +0000 Subject: [rdo-list] Fedora: running RDO (openstack-mitaka) In-Reply-To: References: , Message-ID: ________________________________ From: Nir Levy Sent: Wednesday, September 14, 2016 2:19 PM To: Boris Derzhavets Subject: RE: [rdo-list] Fedora: running RDO (openstack-mitaka) Hi Boris, could not get your answer to be yes or no, regards You don't have generated by RH repos and dependencies required even for AIO RDO Mitaka install on F24. If your skill's set is strong enough to commit this task , then you are free to go [?] Personally , I would consider this task just worthless , even would be forced to perform it. Boris. BTW . You would better check QuickStart page for Mitaka, it installs $ sudo yum install -y centos-release-openstack-mitaka $ sudo yum update -y $ sudo yum install -y openstack-packstack $ packstack --allinone in other words qemu-kvm-ev-2.3 gets installed on CentOS 7.2 to run your libvirt cloud guests. Same will be a must for RDO Newton release Fedora is currently wiped out from RDO development cycle by Red Hat Inc. If I am wrong about that somebody on rdo mailing list will correct me. From: Boris Derzhavets [mailto:bderzhavets at hotmail.com] Sent: Wednesday, August 17, 2016 1:24 PM To: Nir Levy ; rdo-list ; Javier Pena Cc: Yan Fridland Subject: Re: [rdo-list] Fedora: running RDO (openstack-mitaka) ________________________________ From: rdo-list-bounces at redhat.com > on behalf of Nir Levy > Sent: Wednesday, August 17, 2016 4:15 AM To: rdo-list; Javier Pena Cc: Yan Fridland Subject: Re: [rdo-list] Fedora: running RDO (openstack-mitaka) Hi everybody, Any scheduled items regarding this issue? regards, Nir. From: Nir Levy Sent: Tuesday, August 9, 2016 2:50 PM To: rdo-list >; Javier Pena > Subject: Fedora: running RDO (openstack-mitaka) Main goal: installing any RDO over Fedora 24, starting with all in one. according to: https://www.rdoproject.org/install/quickstart/ and https://www.rdoproject.org/documentation/packstack-all-in-one-diy-configuration/ Packstack quickstart ? RDO www.rdoproject.org Packstack quickstart: Proof of concept for single node. Packstack is an installation utility that lets you spin up a proof of concept cloud on one node. sudo yum install https://www.rdoproject.org/repos/rdo-release.rpm sudo yum update -y sudo yum install -y openstack-packstack You are installing stuff supposed to provide packstack and all other openstack packages for RHEL 7.X Schedule rebuild all of them for F24 at least. I am not talking about CI implementation for F24. RDO IS NOT SUPPORTED on Fedora, unless all patching and builds would be done by Community members. It was stated officially . Boris. packstack --allinone --gen-answer_file=answer.txt and afterwords. setting my interfaces: CONFIG_NOVA_NETWORK_PUBIF --novanetwork-pubif CONFIG_NOVA_COMPUTE_PRIVIF --novacompute-privif CONFIG_NOVA_NETWORK_PRIVIF --novanetwork-privif setting additional settings: CONFIG_PROVISION_DEMO --provision-demo n (y for allinone) CONFIG_SWIFT_INSTALL --os-swift-install (y for allinone) n Set to y if you would like PackStack to install Object Storage. CONFIG_NAGIOS_INSTALL --nagios-install n (y for allinone) Set to y if you would like to install Nagios. Nagios provides additional tools for monitoring the OpenStack environment. CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE --provision-all-in-one-ovs-bridge n (y for allinone) packstack --answer-file=answer.txt 1) first issue I?ve encountered is : Error: Parameter mode failed on File[rabbitmq.config]: The file mode specification must be a string, not 'Fixnum' at ? occurs, I have to verify: /usr/lib/python2.7/site-packages/packstack/puppet/templates/amqp.pp /usr/share/openstack-puppet/modules/module-collectd/manifests/plugin/amqp.pp and modify the following: https://review.openstack.org/349908 2) second issue I?ve encountered is : https://bugs.launchpad.net/packstack/+bug/1597951 after modifying SELinux /usr/sbin/getenforce Enforcing setenforce permissive /usr/sbin/getenforce Permissive seems to resolve it: 3) third issue is the current issue. 192.168.13.85_amqp.pp: [ DONE ] <-> previously failed. 192.168.13.85_mariadb.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] 192.168.13.85_mariadb.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 192.168.13.85_mariadb.pp Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install mariadb-galera-server' returned 1: Yum command has been deprecated, redirecting to '/usr/bin/dnf -d 0 -e 0 -y install mariadb-galera-server'. You will find full trace in log /var/tmp/packstack/20160802-193240-sGLWV3/manifests/192.168.13.85_mariadb.pp.log Please check log file /var/tmp/packstack/20160802-193240-sGLWV3/openstack-setup.log for more information Nir Levy SW Engineer Web: www.asocstech.com | [cid:image001.jpg at 01D1B599.5A2C9530] Nir Levy SW Engineer Web: www.asocstech.com | [cid:image001.jpg at 01D1B599.5A2C9530] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 2704 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OutlookEmoji-?.png Type: image/png Size: 488 bytes Desc: OutlookEmoji-?.png URL: From nirl at asocsnetworks.com Wed Sep 14 12:38:57 2016 From: nirl at asocsnetworks.com (Nir Levy) Date: Wed, 14 Sep 2016 12:38:57 +0000 Subject: [rdo-list] Fedora: running RDO (openstack-mitaka) In-Reply-To: References: , Message-ID: Boris, Thank you. I wish I could have done that by myself, that is not exactly the case (: Yaniv: we have a relatively formal answer that seals the case of implementing RDO over fedora issue as not likely to happen in the foreseeable future. Regards, Nir. From: Boris Derzhavets [mailto:bderzhavets at hotmail.com] Sent: Wednesday, September 14, 2016 3:29 PM To: Nir Levy Cc: rdo-list Subject: Re: [rdo-list] Fedora: running RDO (openstack-mitaka) ________________________________ From: Nir Levy > Sent: Wednesday, September 14, 2016 2:19 PM To: Boris Derzhavets Subject: RE: [rdo-list] Fedora: running RDO (openstack-mitaka) Hi Boris, could not get your answer to be yes or no, regards You don't have generated by RH repos and dependencies required even for AIO RDO Mitaka install on F24. If your skill's set is strong enough to commit this task , then you are free to go [?] Personally , I would consider this task just worthless , even would be forced to perform it. Boris. BTW . You would better check QuickStart page for Mitaka, it installs $ sudo yum install -y centos-release-openstack-mitaka $ sudo yum update -y $ sudo yum install -y openstack-packstack $ packstack --allinone in other words qemu-kvm-ev-2.3 gets installed on CentOS 7.2 to run your libvirt cloud guests. Same will be a must for RDO Newton release Fedora is currently wiped out from RDO development cycle by Red Hat Inc. If I am wrong about that somebody on rdo mailing list will correct me. From: Boris Derzhavets [mailto:bderzhavets at hotmail.com] Sent: Wednesday, August 17, 2016 1:24 PM To: Nir Levy >; rdo-list >; Javier Pena > Cc: Yan Fridland > Subject: Re: [rdo-list] Fedora: running RDO (openstack-mitaka) ________________________________ From: rdo-list-bounces at redhat.com > on behalf of Nir Levy > Sent: Wednesday, August 17, 2016 4:15 AM To: rdo-list; Javier Pena Cc: Yan Fridland Subject: Re: [rdo-list] Fedora: running RDO (openstack-mitaka) Hi everybody, Any scheduled items regarding this issue? regards, Nir. From: Nir Levy Sent: Tuesday, August 9, 2016 2:50 PM To: rdo-list >; Javier Pena > Subject: Fedora: running RDO (openstack-mitaka) Main goal: installing any RDO over Fedora 24, starting with all in one. according to: https://www.rdoproject.org/install/quickstart/ and https://www.rdoproject.org/documentation/packstack-all-in-one-diy-configuration/ Packstack quickstart ? RDO www.rdoproject.org Packstack quickstart: Proof of concept for single node. Packstack is an installation utility that lets you spin up a proof of concept cloud on one node. sudo yum install https://www.rdoproject.org/repos/rdo-release.rpm sudo yum update -y sudo yum install -y openstack-packstack You are installing stuff supposed to provide packstack and all other openstack packages for RHEL 7.X Schedule rebuild all of them for F24 at least. I am not talking about CI implementation for F24. RDO IS NOT SUPPORTED on Fedora, unless all patching and builds would be done by Community members. It was stated officially . Boris. packstack --allinone --gen-answer_file=answer.txt and afterwords. setting my interfaces: CONFIG_NOVA_NETWORK_PUBIF --novanetwork-pubif CONFIG_NOVA_COMPUTE_PRIVIF --novacompute-privif CONFIG_NOVA_NETWORK_PRIVIF --novanetwork-privif setting additional settings: CONFIG_PROVISION_DEMO --provision-demo n (y for allinone) CONFIG_SWIFT_INSTALL --os-swift-install (y for allinone) n Set to y if you would like PackStack to install Object Storage. CONFIG_NAGIOS_INSTALL --nagios-install n (y for allinone) Set to y if you would like to install Nagios. Nagios provides additional tools for monitoring the OpenStack environment. CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE --provision-all-in-one-ovs-bridge n (y for allinone) packstack --answer-file=answer.txt 1) first issue I?ve encountered is : Error: Parameter mode failed on File[rabbitmq.config]: The file mode specification must be a string, not 'Fixnum' at ? occurs, I have to verify: /usr/lib/python2.7/site-packages/packstack/puppet/templates/amqp.pp /usr/share/openstack-puppet/modules/module-collectd/manifests/plugin/amqp.pp and modify the following: https://review.openstack.org/349908 2) second issue I?ve encountered is : https://bugs.launchpad.net/packstack/+bug/1597951 after modifying SELinux /usr/sbin/getenforce Enforcing setenforce permissive /usr/sbin/getenforce Permissive seems to resolve it: 3) third issue is the current issue. 192.168.13.85_amqp.pp: [ DONE ] <-> previously failed. 192.168.13.85_mariadb.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] 192.168.13.85_mariadb.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 192.168.13.85_mariadb.pp Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install mariadb-galera-server' returned 1: Yum command has been deprecated, redirecting to '/usr/bin/dnf -d 0 -e 0 -y install mariadb-galera-server'. You will find full trace in log /var/tmp/packstack/20160802-193240-sGLWV3/manifests/192.168.13.85_mariadb.pp.log Please check log file /var/tmp/packstack/20160802-193240-sGLWV3/openstack-setup.log for more information Nir Levy SW Engineer Web: www.asocstech.com | [cid:image001.jpg at 01D1B599.5A2C9530] Nir Levy SW Engineer Web: www.asocstech.com | [cid:image001.jpg at 01D1B599.5A2C9530] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 488 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 2704 bytes Desc: image003.jpg URL: From apevec at redhat.com Wed Sep 14 12:43:35 2016 From: apevec at redhat.com (Alan Pevec) Date: Wed, 14 Sep 2016 14:43:35 +0200 Subject: [rdo-list] Fedora: running RDO (openstack-mitaka) In-Reply-To: References: Message-ID: > Fedora is currently wiped out from RDO development cycle by Red Hat Inc. I'll have to correct this :) Red Hat Inc. is not an entity participating in the RDO community, we discuss decisions openly on the rdo-list and RDO meetings. There was an open discussion what to do about Fedora as a base for RDO last year, documented in https://trello.com/c/wzdl1IlZ/52-openstack-in-fedora Fedora is not wiped out, we take care to keep OpenStack clients and Oslo libs updated there and keep then in sync with RDO packaging, but since we could not justify a use-case for running _production_ OpenStack on Fedora, decision was to focus our efforts on EL7 base. We are also keeping untested RDO Trunk repo built on Fedora Rawhide as a place to test features like Python3 not available in EL7. Cheers, Alan From trown at redhat.com Wed Sep 14 13:37:17 2016 From: trown at redhat.com (John Trowbridge) Date: Wed, 14 Sep 2016 09:37:17 -0400 Subject: [rdo-list] [TripleO] How to build disk images? In-Reply-To: <1925011c-70e2-401e-fcf0-1046493fd8ee@midokura.com> References: <1925011c-70e2-401e-fcf0-1046493fd8ee@midokura.com> Message-ID: On 09/12/2016 12:27 PM, Alejandro Andreu wrote: > Hi all, > > I need to update an image in the tripleo-puppet-elements repository[0]. > More precisely, I need to update "overcloud-network-midonet". > > Before pushing changes upstream I would like to build and test the > images locally, but I'm having issues finding documentation to do so. > > I found a tripleo-incubator doc[1], but I'm not sure this is what I'm > looking for, or if it is indeed outdated. Or is there another way to > build the images? Also, the README in [0] does not work. > > Can you please point me in the right direction here? > > Best regards, > Alejandro Andreu > > [0]: https://github.com/openstack/tripleo-puppet-elements > [1]: http://docs.openstack.org/developer/tripleo-incubator/puppet.html There are instructions for building overcloud images in the tripleo docs[1], and if these are not working the repo for them is here[2]. That said, it is often much easier to use virt-customize[3] on a existing image to test changes. [1] http://tripleo.org/basic_deployment/basic_deployment_cli.html#get-images [2] https://github.com/openstack/tripleo-docs [3] http://libguestfs.org/virt-customize.1.html From chkumar246 at gmail.com Wed Sep 14 16:13:32 2016 From: chkumar246 at gmail.com (Chandan kumar) Date: Wed, 14 Sep 2016 21:43:32 +0530 Subject: [rdo-list] [Cloud SIG][RDO] RDO meeting minutes - 2016-09-14 Message-ID: ============================== #rdo: RDO meeting - 2016-09-14 ============================== Meeting started by chandankumar at 15:00:48 UTC. The full logs are available at https://meetbot.fedoraproject.org/rdo/2016-09-14/rdo_meeting_-_2016-09-14.2016-09-14-15.00.log.html . Meeting summary --------------- * roll call (chandankumar, 15:00:57) * Infrastructure concerns (chandankumar, 15:03:37) * LINK: https://www.redhat.com/archives/rdo-list/2016-August/msg00237.html (dmsimard, 15:08:36) * ACTION: rbowen to update https://www.rdoproject.org/infra/ with services and responsibilities, then hand off to jpena for crosscheck. (rbowen, 15:17:39) * ACTION: Schedule a work session for RDO Infrastructure somewhere monday afternoon (dmsimard, 15:20:32) * phase out rpm-xxx branches (chandankumar, 15:21:15) * do not merge any rdoinfo review removing rpm-RELEASE branches before checking w/ jpena (number80, 15:25:19) * LINK: https://trello.com/c/zT4BghsV/366-branching-newton-rdo (apevec, 15:26:53) * ACTION: apevec to check branching permissions for amoralej (apevec, 15:28:27) * number80 is checking Mitaka in parallel of newton branching (apevec, 15:30:55) * python-shade packaging (chandankumar, 15:31:16) * ACTION: apevec to request CBS tags for rdo-tools repo (apevec, 15:33:38) * [Ci-users] [Infra] - Major outage for several services (chandankumar, 15:35:14) * LINK: https://lists.centos.org/pipermail/ci-users/2016-September/000392.html (chandankumar, 15:35:24) * ACTION: dmsimard and jpena to start working towards moving dlrn package building to review.rdoproject.org (nodepool) on post-commit upstream pipeline (dmsimard, 15:46:50) * exceptions for upper-constraints based repo for tripleo gated projects (chandankumar, 15:50:35) * What should we improve for test days? (chandankumar, 15:52:12) * ACTION: rbowen to raise topic of improving test day experience on rdo-list (rbowen, 15:57:57) * Announcements (chandankumar, 15:58:05) * Demos/Q&A at RDO booth at OpenStack Summit Barcelona - signup at https://etherpad.openstack.org/p/rdo-barcelona-summit-booth (chandankumar, 15:58:20) * We are planning an RDO Community Meetup, in conjunction with the Ceph community, at OpenStack Summit. Tuesday night, October 25th, 5pm-8pm. Agenda is at https://etherpad.openstack.org/p/rdo-barcelona-meetup-schedule (chandankumar, 15:58:34) * Newton RC1 test day September 22, 23 - Details coming soon to https://www.rdoproject.org/testday/ (chandankumar, 15:58:45) * New tempest rpms are available now here https://trunk.rdoproject.org/centos7-master/consistent/ Feel free to try out (chandankumar, 15:59:16) * openstack-sahara-tests is available in RDO now https://review.rdoproject.org/r/#/q/topic:add-sahara-tests (chandankumar, 15:59:37) * chair for next meeting (chandankumar, 15:59:51) * ACTION: imcsk8 will chair for next meeting (chandankumar, 16:00:13) * open floor (chandankumar, 16:00:19) Meeting ended at 16:02:50 UTC. Action Items ------------ * rbowen to update https://www.rdoproject.org/infra/ with services and responsibilities, then hand off to jpena for crosscheck. * Schedule a work session for RDO Infrastructure somewhere monday afternoon * apevec to check branching permissions for amoralej * apevec to request CBS tags for rdo-tools repo * dmsimard and jpena to start working towards moving dlrn package building to review.rdoproject.org (nodepool) on post-commit upstream pipeline * rbowen to raise topic of improving test day experience on rdo-list * imcsk8 will chair for next meeting Action Items, by person ----------------------- * amoralej * apevec to check branching permissions for amoralej * apevec * apevec to check branching permissions for amoralej * apevec to request CBS tags for rdo-tools repo * dmsimard * dmsimard and jpena to start working towards moving dlrn package building to review.rdoproject.org (nodepool) on post-commit upstream pipeline * imcsk8 * imcsk8 will chair for next meeting * jpena * rbowen to update https://www.rdoproject.org/infra/ with services and responsibilities, then hand off to jpena for crosscheck. * dmsimard and jpena to start working towards moving dlrn package building to review.rdoproject.org (nodepool) on post-commit upstream pipeline * rbowen * rbowen to update https://www.rdoproject.org/infra/ with services and responsibilities, then hand off to jpena for crosscheck. * rbowen to raise topic of improving test day experience on rdo-list * **UNASSIGNED** * Schedule a work session for RDO Infrastructure somewhere monday afternoon People Present (lines said) --------------------------- * apevec (68) * chandankumar (67) * dmsimard (41) * number80 (31) * Duck (29) * jpena (20) * rbowen (18) * Arrfab (18) * misc (16) * zodbot (15) * trown (14) * amoralej (12) * imcsk8 (9) * DrBacchus (9) * rdogerrit (8) * flepied (5) * EmilienM (4) * openstack (3) * jschlueter (2) * quaid (1) * hrybacki (1) * jruzicka (1) * coolsvap (1) * jrist (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Thanks, Chandan Kumar From dms at redhat.com Wed Sep 14 18:11:46 2016 From: dms at redhat.com (David Moreau Simard) Date: Wed, 14 Sep 2016 14:11:46 -0400 Subject: [rdo-list] Etherpad for "DLRN on Nodepool" Message-ID: Hi, I created an etherpad to get us started on what we need, what are the unknowns and other discussion around what is involved in moving DLRN package building to a Zuul/Nodepool architecture. It's still very much a draft/work in progress but feel free to contribute, even if it's just questions/comments. Thanks, https://review.rdoproject.org/etherpad/p/dlrn-on-nodepool David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] From mburns at redhat.com Wed Sep 14 21:43:32 2016 From: mburns at redhat.com (Mike Burns) Date: Wed, 14 Sep 2016 17:43:32 -0400 Subject: [rdo-list] Adding backwards compatible tripleo-heat-templates packaging In-Reply-To: References: <376215178.9458025.1473086870132.JavaMail.zimbra@redhat.com> Message-ID: On Wed, Sep 14, 2016 at 4:59 AM, Alan Pevec wrote: >>> I think something like this (having an openstack-tripleo-heat-templates-compat-mitaka package or similar) would work best. >>> >>> This would also allow us to decide when to drop support for older releases. Newton will have a mitaka-compat package, but we'll sure drop it in a later release, won't we? We could then just control which packages are built for each release using rdoinfo. >> >> If we do this, *every* release will drop a package and add a package. >> The tripleo team won't commit to supporting more than 1 version back >> currently, so -mitaka would only be included with the newton release. > > If that's defined in a tripleo spec, please provide a link. > >> In Ocata, we'd drop mitaka and add -newton. This is part of the >> reason that a single tarball made things easier. Just get the right >> source tarball for old release and build it in a single package. An >> update per release in a single spec file is generally easier than a >> new package. > > How is that done in upstream tripleoci jobs which is testing upgrade? This isn't upgrade, it's old version support. Managing a Mitaka overcloud with a Newton undercloud. AFAIK, there is no support for this in CI today due to the lack of this compat package existing in RDO. > Is that just checking out stable branch? Link please :) > Problmem with the proposed change is how to supply Source1 to Trunk > builders, currently it handles only single Source0 by replacing it > with the tarball generated from the git checkout. We would have to > keep full Source1 tarball in the distgit and manually keep it in sync > with the stable source branch. > While this might look like a nail-hammer tool deficiency, tracking two > branches in the same package is really adding unnecessary complexity. > What about adding a new package > openstack-tripleo-heat-templates-compat which would be configured in > rdoinfo to take Source0 from the previous stable branch and only that > metadata would get updated for the new release e.g. > - project: tripleo-heat-templates-compat > tags: > newton-uc: > source-branch: stable/mitaka > newton: > source-branch: stable/mitaka > mitaka: > source-branch: stable/liberty > conf: rpmfactory-core > maintainers: > - mburns at redhat.com I'm fine with this (except I shouldn't be the long term owner, but we'll solve that later). > > It would install into {_datadir}/%{name}/%{old_name} and > openstack-tripleo-heat-templates could have Requires: > openstack-tripleo-heat-templates-compat so that no changes are > required in the installer. I've posted an initial spec here: https://github.com/mburns72h/openstack-tripleo-heat-templates-compat-distgit Mike > > Cheers, > Alan From rbowen at redhat.com Thu Sep 15 14:00:31 2016 From: rbowen at redhat.com (Rich Bowen) Date: Thu, 15 Sep 2016 10:00:31 -0400 Subject: [rdo-list] RDO Infra meeting at OpenStack Summit, Barcelona Message-ID: <35bd7394-5d85-0e5d-4c39-6f69f62d42c9@redhat.com> In yesterday's RDO Community Meeting, we discussed the possibility of having an in-person meeting, in Barcelona, at OpenStack Summit, to discuss our infrastructure needs, how we can support/maintain those needs long term, and other infra-related stuff. I am looking into meeting rooms near the venue, for Monday afternoon. Everything *at* the venue is taken on Monday, and while there is a Red Hat office in BCN, it's a 50 minute bus ride from the conference venue, so I'd like something closer. If you are planning to attend that meeting, please let me know (off-list) what your arrival plans are, as I don't want to exclude anybody. At the moment, we're looking in the 1-3pm time frame. If your presence at the meeting is critical, and you will miss that window, please tell me ASAP before we book a room. Thanks! --Rich -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From rbowen at redhat.com Thu Sep 15 15:53:03 2016 From: rbowen at redhat.com (Rich Bowen) Date: Thu, 15 Sep 2016 11:53:03 -0400 Subject: [rdo-list] An Evening of Ceph and RDO, Tuesday, OpenStack Summit In-Reply-To: <001a1144007a4f5b39053c8c5e52@google.com> References: <001a1144007a4f5b39053c8c5e52@google.com> Message-ID: <4f17d7f6-3584-3a3d-eee6-8df6a0835c3f@redhat.com> Here's the details on the evening gathering Tuesday night at OpenStack Summit, and a handy invite so you can add it to your calendar. --Rich -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 4595 bytes Desc: not available URL: From whayutin at redhat.com Thu Sep 15 16:19:37 2016 From: whayutin at redhat.com (Wesley Hayutin) Date: Thu, 15 Sep 2016 12:19:37 -0400 Subject: [rdo-list] [ci] FYI all rdo promotion jobs have been disabled In-Reply-To: References: Message-ID: On Mon, Sep 12, 2016 at 5:54 PM, Wesley Hayutin wrote: > > > On Mon, Sep 12, 2016 at 5:52 PM, David Moreau Simard > wrote: > >> Can we keep the promotion jobs enabled and just disable the jobs that >> actually upload the images ? >> >> We need visibility on ongoing issues, if there are any, and the jobs >> have already been disabled since test day last week. >> > > Ya.. that is a better idea.. will adjust them. > Thanks > > >> >> David Moreau Simard >> Senior Software Engineer | Openstack RDO >> >> dmsimard = [irc, github, twitter] >> >> >> On Mon, Sep 12, 2016 at 5:37 PM, Wesley Hayutin >> wrote: >> > Greetings, >> > >> > I have disabled all the RDO promotion jobs until such time we have >> confirmed >> > that images are published directly from the virthost to the ci.centos >> > artifacts server. >> > >> > This work is being lead by Matt Young and tested and refined by John >> > Trowbridge and myself. If there are any requirements for promotion while >> > this work is done we will utilize the internal pipeline. >> > >> > Thank you >> > >> > _______________________________________________ >> > rdo-list mailing list >> > rdo-list at redhat.com >> > https://www.redhat.com/mailman/listinfo/rdo-list >> > >> > To unsubscribe: rdo-list-unsubscribe at redhat.com >> > > Greetings, TLDR: There are unique properties to the infra at ci.centos that make it difficult to work with qcow2 images. Transferring images across the ci.centos infra can cause instability in the ci.centos infrastructure itself. The nature of this process is slow and difficult to test however we now believe we have resolved the issue. Details: I wanted to send an update to the community regarding the promotion status of RDO via CI. The issue at hand was syncing and promoting tripleo undercloud and overcloud images to the ci.centos artifacts server. Originally these images were synced in two steps, first synced to the jenkins slave and then to the artifacts server. Syncing the images to the slave was causing instability in the ci.centos infra and also causing network and filesystem issues on the ci.centos slave. Quite simply, image syncs were disrupting the infrastructure and causing failures throughout ci.centos. Through a series of patches [1-8] we have streamlined the image creation and promotion process to only sync the image once. The artifact server *only* has rsync available, there is no ssh service available. It was a complicated problem to solve, but we think we have the code required merged and tests are running. Apologies for the outtage however, we had to choose between an outage and bringing down ci.centos infra. We chose to take an outtage immediately after newton milestone 3 was promoted and the internal beta was imported. Thank you and we appreciate your patience. [1] https://review.gerrithub.io/#/c/290337/ [2] https://review.gerrithub.io/#/c/290344/ [3] https://review.gerrithub.io/#/c/290432/ [4] https://review.gerrithub.io/#/c/290433/ [5] https://review.gerrithub.io/#/c/294590/ [6] https://review.gerrithub.io/#/c/294663/ [7] https://review.gerrithub.io/#/c/294672/ [8] https://review.gerrithub.io/#/c/294694/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Thu Sep 15 19:59:22 2016 From: rbowen at redhat.com (Rich Bowen) Date: Thu, 15 Sep 2016 15:59:22 -0400 Subject: [rdo-list] Improving the test day experience Message-ID: In our RDO Community Meeting (on IRC) yesterday, the topic of improving test day was brought up. Test day is, for the most part, about getting people to beat on the latest packages and find problems. However, since most of these problems are being found in CI, it's time to make test day also about giving people an opportunity to see what's coming in future releases. To that end, user experience is pretty important on test day. Several suggestions were made to improve the test day experience for folks that aren't already experts: * Test setup matrix cleanup? Remove tests that are no longer relevant. * More detailed, beginner-friendly instructions for testing. (Test day as product preview for potential users, or existing users who are not deep experts.) * Ask other teams to provide use cases they want to validate. * Tracking the tests on an etherpad with instructions, and registering people to use cases, so that we're sure that everything is being covered. While these are all great suggestions, each requires that someone actually step up and make it happen. Each test day, for example, we talk about better instructions for the test scenarios, and everyone agrees that it's a good idea. Anyways, as we start looking towards Ocata, are there other suggestions as to how we can make the test day more welcoming to folks trying out RDO for the first time, and existing OpenStack users looking for a preview of the next release, as well as the usual suspects? And, as importantly, people who are able to make some of these things happen? Thanks. --Rich -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From rbowen at redhat.com Thu Sep 15 20:49:52 2016 From: rbowen at redhat.com (Rich Bowen) Date: Thu, 15 Sep 2016 16:49:52 -0400 Subject: [rdo-list] [Cloud SIG] CentOS Cloud Sig minutes Message-ID: <9bac2698-6ca8-3e4d-2c1d-720115b9270a@redhat.com> We had a very brief meeting today. The transcript from that meeting is here: https://www.centos.org/minutes/2016/september/centos-devel.2016-09-15-15.00.log.html In particular, I want to draw attention to one item: CBS (the CentOS community build system) is undergoing planned maintenance on October 10th, and so there will be downtime that day. -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From whayutin at redhat.com Fri Sep 16 06:01:16 2016 From: whayutin at redhat.com (Wesley Hayutin) Date: Fri, 16 Sep 2016 02:01:16 -0400 Subject: [rdo-list] [CI] TripleO-Quickstart doc on full deployments Message-ID: Greetings, A recent change [1] to TripleO-Quickstart requires that you run a different playbook for full deployments. See the following doc change [2] for details on how to run a full deployment of TripleO. Thanks [1] https://review.openstack.org/#/c/358089/ [2] https://review.openstack.org/#/c/369659/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jperrin at centos.org Fri Sep 16 17:08:28 2016 From: jperrin at centos.org (Jim Perrin) Date: Fri, 16 Sep 2016 12:08:28 -0500 Subject: [rdo-list] [Arm-dev] next steps for altarch with ceph and openstack In-Reply-To: <666856ae-24cc-cb00-21b4-5eec4c191532@codeaurora.org> References: <577BC402.6020308@centos.org> <6cfab514-db91-5ce5-bcfd-0799a72fb584@linaro.org> <743b47ac-f15d-d6a1-6861-b410cc5b0916@linaro.org> <577E7831.4030007@centos.org> <577FA3C1.2060100@centos.org> <666856ae-24cc-cb00-21b4-5eec4c191532@codeaurora.org> Message-ID: <6d9e867a-8387-7f91-f3ec-f6adf15dd932@centos.org> On 09/16/2016 09:36 AM, Christopher Covington wrote: > If one wanted to install openstack on AArch64 CentOS 7.2 AltArch, are > Marcin's repositories at Linaro still fresh? Or is there something on > centos.org now? Yes, that's still the proper place for now. The current plan is to have aarch64 be natively supported in RDO when Newton comes out in a couple weeks. There are no plans to do anything with mitaka for aarch64 since newton is so close. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 From bderzhavets at hotmail.com Sat Sep 17 22:06:00 2016 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Sat, 17 Sep 2016 22:06:00 +0000 Subject: [rdo-list] Regarding Launchpad Bugs "Updating plans breaks deployment" 1622683 && "Deploying an overcloud a second time after a failure, doesn't find overcloud.yaml" 1622720 In-Reply-To: References: Message-ID: Please , see https://bugs.launchpad.net/tripleo/+bug/1622683/comments/7 Thank you. Boris. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Mon Sep 19 13:11:38 2016 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 19 Sep 2016 09:11:38 -0400 Subject: [rdo-list] OpenStack Meetups this week (19 Sep 2016) Message-ID: <2b603f9f-8a2f-f330-cb16-618a28dceb0c@redhat.com> The following are the meetups I'm aware of in the coming week where OpenStack and/or RDO enthusiasts are likely to be present. If you know of others, please let me know, and/or add them to http://rdoproject.org/events If there's a meetup in your area, please consider attending. If you attend, please consider taking a few photos, and possibly even writing up a brief summary of what was covered. --Rich * Monday September 19 in Paris, FR: Discutons OpenStack et containers - http://www.meetup.com/Meetup-SUSE-Linux-Paris/events/233636337/ * Tuesday September 20 in Raleigh, NC, US: Webinar:Why OpenStack is better with Rackspace and Red Hat - http://www.meetup.com/Raleigh-Red-Hat-User-Group/events/233763649/ * Tuesday September 20 in Washington, DC, US: Swift Encryption, OpenStack Tools & Best Practices, BotFactory - http://www.meetup.com/OpenStackDC/events/233808380/ * Wednesday September 21 in Reston, VA, US: A Detailed Look at Encryption in OpenStack Swift - http://www.meetup.com/OpenStack-Nova/events/234073230/ * Wednesday September 21 in San Francisco, CA, US: Troubleshooting OpenStack Clouds: From Detecting Black Holes to Micro-bursts - http://www.meetup.com/openstack/events/233981912/ * Wednesday September 21 in Houston, TX, US: The Joining of the Open Source Minds! - http://www.meetup.com/openstackhoustonmeetup/events/234149124/ * Wednesday September 21 in Phoenix, AZ, US: Vladimir Ulogov from Zabbix will talk Openstack + Zabbix - http://www.meetup.com/OpenStack-Phoenix/events/234065881/ * Thursday September 22 in Stockholm, SE: OpenStack Days Nordic - http://www.meetup.com/OpenStack-User-Group-Sweden/events/230564258/ * Thursday September 22 in Helsinki, FI: Are you going to OpenStack Days Nordic 22 Sep, in Stockholm? - http://www.meetup.com/OpenStack-Finland-User-Group/events/231710721/ * Thursday September 22 in Durham, NC, US: September Meetup: Conjure-up and Master to Metal with OpenStack Charms - http://www.meetup.com/Triangle-OpenStack-Meetup/events/233464791/ * Thursday September 22 in Herriman, UT, US: High Performance Ceph at Adobe - http://www.meetup.com/openstack-utah/events/233386228/ * Saturday September 24 in Tambaram, IN: Want to Loud in cloud to shape your career ? - http://www.meetup.com/CloudnLoud-Openstack-Cloud-RedHat-Opensource/events/233897589/ -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From rbowen at redhat.com Mon Sep 19 14:05:38 2016 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 19 Sep 2016 10:05:38 -0400 Subject: [rdo-list] ask.openstack.org Unanswered RDO questions Message-ID: <278a6972-3cbe-89a4-152e-e0f0f7e6550d@redhat.com> 30 unanswered questions: Murano Requirements https://ask.openstack.org/en/question/96986/murano-requirements/ Tags: murano cinder migrate fails when migrating attached volumes https://ask.openstack.org/en/question/96982/cinder-migrate-fails-when-migrating-attached-volumes/ Tags: rdo, liberty, cinder, volume-migration No valid host was found. There are not enough hosts available. https://ask.openstack.org/en/question/96976/no-valid-host-was-found-there-are-not-enough-hosts-available/ Tags: rdo can not ping internet when launch instance cirros on mitaka https://ask.openstack.org/en/question/96949/can-not-ping-internet-when-launch-instance-cirros-on-mitaka/ Tags: cirros, security-groups, mitaka, mitaka-neutron After adding multiple compute nodes using packstack unable to see the nodes in dashboard https://ask.openstack.org/en/question/96732/after-adding-multiple-compute-nodes-using-packstack-unable-to-see-the-nodes-in-dashboard/ Tags: rdo Error: Unable to get the Swift container listing https://ask.openstack.org/en/question/96658/error-unable-to-get-the-swift-container-listing/ Tags: swift, containers, rdo [trove] mongodb cluster-grow failed https://ask.openstack.org/en/question/96571/trove-mongodb-cluster-grow-failed/ Tags: trove, mongodb, cluster, grow quota show is different from horizon in RDO after update quota with command https://ask.openstack.org/en/question/96244/quota-show-is-different-from-horizon-in-rdo-after-update-quota-with-command/ Tags: rdo "Parameter outiface failed on Firewall" during installation of openstack rdo on centos 7 https://ask.openstack.org/en/question/95657/parameter-outiface-failed-on-firewall-during-installation-of-openstack-rdo-on-centos-7/ Tags: rdo, devstack#mitaka multi nodes provider network ovs config https://ask.openstack.org/en/question/95423/multi-nodes-provider-network-ovs-config/ Tags: rdo, liberty-neutron Adding additional packages to an RDO installation https://ask.openstack.org/en/question/95380/adding-additional-packages-to-an-rdo-installation/ Tags: rdo, mistral RDO TripleO Mitaka HA Overcloud Failing https://ask.openstack.org/en/question/95249/rdo-tripleo-mitaka-ha-overcloud-failing/ Tags: mitaka, tripleo, overcloud, centos7 RDO - is there any fedora package newer than puppet-4.2.1-3.fc24.noarch.rpm https://ask.openstack.org/en/question/94969/rdo-is-there-any-fedora-package-newer-than-puppet-421-3fc24noarchrpm/ Tags: rdo, puppet, install-openstack OpenStack RDO mysqld 100% cpu https://ask.openstack.org/en/question/94961/openstack-rdo-mysqld-100-cpu/ Tags: openstack, mysqld, cpu Failed to set RDO repo on host-packstack-centOS-7 https://ask.openstack.org/en/question/94828/failed-to-set-rdo-repo-on-host-packstack-centos-7/ Tags: openstack-packstack, centos7, rdo how to deploy haskell-distributed in RDO? https://ask.openstack.org/en/question/94785/how-to-deploy-haskell-distributed-in-rdo/ Tags: rdo rdo tripleO liberty undercloud install failing https://ask.openstack.org/en/question/94023/rdo-tripleo-liberty-undercloud-install-failing/ Tags: rdo, rdo-manager, liberty, undercloud, instack Liberty RDO: stack resource topology icons are pink https://ask.openstack.org/en/question/91347/liberty-rdo-stack-resource-topology-icons-are-pink/ Tags: resource, topology, dashboard, horizon, pink No handlers could be found for logger "oslo_config.cfg" while syncing the glance database https://ask.openstack.org/en/question/91169/no-handlers-could-be-found-for-logger-oslo_configcfg-while-syncing-the-glance-database/ Tags: liberty, glance, install-openstack CentOS OpenStack - compute node can't talk https://ask.openstack.org/en/question/88989/centos-openstack-compute-node-cant-talk/ Tags: rdo How to setup SWIFT_PROXY_NODE and SWIFT_STORAGE_NODEs separately on RDO Liberty ? https://ask.openstack.org/en/question/88897/how-to-setup-swift_proxy_node-and-swift_storage_nodes-separately-on-rdo-liberty/ Tags: rdo, liberty, swift, ha VM and container can't download anything from internet https://ask.openstack.org/en/question/88338/vm-and-container-cant-download-anything-from-internet/ Tags: rdo, neutron, network, connectivity Fedora22, Liberty, horizon VNC console and keymap=sv with ; and/ https://ask.openstack.org/en/question/87451/fedora22-liberty-horizon-vnc-console-and-keymapsv-with-and/ Tags: keyboard, map, keymap, vncproxy, novnc OpenStack-Docker driver failed https://ask.openstack.org/en/question/87243/openstack-docker-driver-failed/ Tags: docker, openstack, liberty Routing between two tenants https://ask.openstack.org/en/question/84645/routing-between-two-tenants/ Tags: kilo, fuel, rdo, routing openstack baremetal introspection internal server error https://ask.openstack.org/en/question/82790/openstack-baremetal-introspection-internal-server-error/ Tags: rdo, ironic-inspector, tripleo Installing openstack using packstack (rdo) failed https://ask.openstack.org/en/question/82473/installing-openstack-using-packstack-rdo-failed/ Tags: rdo, packstack, installation-error, keystone VMware Host Backend causes No valid host was found. Bug ??? https://ask.openstack.org/en/question/79738/vmware-host-backend-causes-no-valid-host-was-found-bug/ Tags: vmware, rdo Mutlinode Devstack with two interfaces https://ask.openstack.org/en/question/78615/mutlinode-devstack-with-two-interfaces/ Tags: devstack, vlan, openstack Overcloud deployment on VM fails as IP address from DHCP is not assigned https://ask.openstack.org/en/question/66272/overcloud-deployment-on-vm-fails-as-ip-address-from-dhcp-is-not-assigned/ Tags: overcloud_in_vm -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From hguemar at fedoraproject.org Mon Sep 19 15:00:03 2016 From: hguemar at fedoraproject.org (hguemar at fedoraproject.org) Date: Mon, 19 Sep 2016 15:00:03 +0000 (UTC) Subject: [rdo-list] [Fedocal] Reminder meeting : RDO meeting Message-ID: <20160919150003.EEC9560A4003@fedocal02.phx2.fedoraproject.org> Dear all, You are kindly invited to the meeting: RDO meeting on 2016-09-21 from 15:00:00 to 16:00:00 UTC At rdo at 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/ From mnaser at vexxhost.com Tue Sep 20 13:33:49 2016 From: mnaser at vexxhost.com (Mohammed Naser) Date: Tue, 20 Sep 2016 09:33:49 -0400 Subject: [rdo-list] RabbitMQ version in RDO Message-ID: Hi everyone, I'm wondering what is the current status on the supporting packages for OpenStack in RDO and how they are handled? I personally think it's really nice that everything comes packaged from one repository and we don't have to go to upstream (in the exception of -ev packages). In this case, I'm wondering if it is possible to get a newer version of RabbitMQ in the Mitaka RDO repos, the reason behind this is that there is a bug affecting us which results in RabbitMQ nodes crashing. The details of the bug are here: https://github.com/rabbitmq/rabbitmq-management/issues/245 This issue is resolved in 3.6.4, but 3.6.2 is what is included in the RDO repos. We could just start using the upstream packages however I think it's far more productive for everyone in the community to have updated packages so they don't run into the same surprises that we ran into and RDO maintains a working out-of-the-box set of packages for OpenStack without having to resort to other package sources. I guess all this summarizes to two questions: What's the policy on the supporting packages in OpenStack and could we work to get an update RabbitMQ version? Thanks! Mohammed -- Mohammed Naser From apevec at redhat.com Tue Sep 20 14:12:44 2016 From: apevec at redhat.com (Alan Pevec) Date: Tue, 20 Sep 2016 16:12:44 +0200 Subject: [rdo-list] RabbitMQ version in RDO In-Reply-To: References: Message-ID: > In this case, I'm wondering if it is possible to get a newer version > of RabbitMQ in the Mitaka RDO repos, the reason behind this is that > there is a bug affecting us which results in RabbitMQ nodes crashing. > The details of the bug are here: > > https://github.com/rabbitmq/rabbitmq-management/issues/245 > > This issue is resolved in 3.6.4, but 3.6.2 is what is included in the > RDO repos. There is 3.6.5 update in the pending repo: http://cbs.centos.org/repos/cloud7-openstack-common-pending/x86_64/os/Packages/ Please test it and report here. Cheers, Alan From dms at redhat.com Tue Sep 20 14:29:48 2016 From: dms at redhat.com (David Moreau Simard) Date: Tue, 20 Sep 2016 10:29:48 -0400 Subject: [rdo-list] RabbitMQ version in RDO In-Reply-To: References: Message-ID: So I think what's the underlying question here is how do we define when to update non-OpenStack components that RDO carries in it's repositories. I think with OpenStack components it's easier, there's branches and we build/test them throughout the lifecycle. Once we have the proper testing in place, we can update those more frequently. This isn't limited to RabbitMQ, there's other things like mariadb/galera, puppet and so on. Should we try to always have the most up-to-date version (given we are confident enough in our testing?) ? Should we only update on a need/request basis ? Only when there's a known critical bug or CVE ? We should agree on something and document that somewhere. David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Tue, Sep 20, 2016 at 10:12 AM, Alan Pevec wrote: >> In this case, I'm wondering if it is possible to get a newer version >> of RabbitMQ in the Mitaka RDO repos, the reason behind this is that >> there is a bug affecting us which results in RabbitMQ nodes crashing. >> The details of the bug are here: >> >> https://github.com/rabbitmq/rabbitmq-management/issues/245 >> >> This issue is resolved in 3.6.4, but 3.6.2 is what is included in the >> RDO repos. > > There is 3.6.5 update in the pending repo: > http://cbs.centos.org/repos/cloud7-openstack-common-pending/x86_64/os/Packages/ > > Please test it and report here. > > Cheers, > Alan > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From apevec at redhat.com Tue Sep 20 15:05:03 2016 From: apevec at redhat.com (Alan Pevec) Date: Tue, 20 Sep 2016 17:05:03 +0200 Subject: [rdo-list] RabbitMQ version in RDO In-Reply-To: References: Message-ID: On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard wrote: > I think with OpenStack components it's easier, there's branches and we > build/test them throughout the lifecycle. > Once we have the proper testing in place, we can update those more frequently. Ideally same would apply for dependencies like rabbitmq, mariadb, we'd update frequently and release after testing but also vetted by package maintainers. Let's start by this last part: I'll check that components in RDO bugzilla have correct default owner then we setup nagging like https://fedoraproject.org/wiki/Upstream_release_monitoring for few critical dependencies. Alan From pkovar at redhat.com Tue Sep 20 15:11:35 2016 From: pkovar at redhat.com (Petr Kovar) Date: Tue, 20 Sep 2016 17:11:35 +0200 Subject: [rdo-list] Improving the test day experience In-Reply-To: References: Message-ID: <20160920171135.567e01e85a31c18a8ede1ba0@redhat.com> On Thu, 15 Sep 2016 15:59:22 -0400 Rich Bowen wrote: > In our RDO Community Meeting (on IRC) yesterday, the topic of improving > test day was brought up. > > Test day is, for the most part, about getting people to beat on the > latest packages and find problems. However, since most of these problems > are being found in CI, it's time to make test day also about giving > people an opportunity to see what's coming in future releases. To that > end, user experience is pretty important on test day. > > Several suggestions were made to improve the test day experience for > folks that aren't already experts: > > > * Test setup matrix cleanup? Remove tests that are no longer relevant. > > * More detailed, beginner-friendly instructions for testing. (Test day > as product preview for potential users, or existing users who are not > deep experts.) I can start working on this but would probably need more input wrt the required scope of the instructions. Like, say, besides setting up a VM with CentOS/RHEL for running packstack, are there other steps we want to cover as part of preparing your environment? Who wants to share their knowledge? Go to https://github.com/redhat-openstack/website/issues/699 Thanks, pk From mnaser at vexxhost.com Tue Sep 20 15:50:43 2016 From: mnaser at vexxhost.com (Mohammed Naser) Date: Tue, 20 Sep 2016 11:50:43 -0400 Subject: [rdo-list] RabbitMQ version in RDO In-Reply-To: References: Message-ID: Hi Alan: Thanks for pointing me to the RabbitMQ packages, we're going to test those internally and report if we run into the issue again. I do agree with what David has pointed out in that there should be a process setup in order to make sure that the shipped packages that come with RDO (at least the supporting ones such as MariaDB/Galera, etc) should be good-to-go. I imagine this might make things a bit more difficult in terms of testing them, so I'm not sure what would be the best path to take in this case. Thanks Mohammed On Tue, Sep 20, 2016 at 11:05 AM, Alan Pevec wrote: > On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard wrote: >> I think with OpenStack components it's easier, there's branches and we >> build/test them throughout the lifecycle. >> Once we have the proper testing in place, we can update those more frequently. > > Ideally same would apply for dependencies like rabbitmq, mariadb, we'd > update frequently and release after testing but also vetted by package > maintainers. > Let's start by this last part: I'll check that components in RDO > bugzilla have correct default owner then we setup nagging like > https://fedoraproject.org/wiki/Upstream_release_monitoring for few > critical dependencies. > > Alan > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From rbowen at redhat.com Tue Sep 20 15:52:03 2016 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 20 Sep 2016 11:52:03 -0400 Subject: [rdo-list] Improving the test day experience In-Reply-To: <20160920171135.567e01e85a31c18a8ede1ba0@redhat.com> References: <20160920171135.567e01e85a31c18a8ede1ba0@redhat.com> Message-ID: <95c9fad4-9430-44bc-8e99-88f13c5be153@redhat.com> On 09/20/2016 11:11 AM, Petr Kovar wrote: > On Thu, 15 Sep 2016 15:59:22 -0400 > Rich Bowen wrote: > >> In our RDO Community Meeting (on IRC) yesterday, the topic of improving >> test day was brought up. >> >> Test day is, for the most part, about getting people to beat on the >> latest packages and find problems. However, since most of these problems >> are being found in CI, it's time to make test day also about giving >> people an opportunity to see what's coming in future releases. To that >> end, user experience is pretty important on test day. >> >> Several suggestions were made to improve the test day experience for >> folks that aren't already experts: >> >> >> * Test setup matrix cleanup? Remove tests that are no longer relevant. >> >> * More detailed, beginner-friendly instructions for testing. (Test day >> as product preview for potential users, or existing users who are not >> deep experts.) > > I can start working on this but would probably need more input wrt the > required scope of the instructions. Like, say, besides setting up a VM with > CentOS/RHEL for running packstack, are there other steps we want to cover as > part of preparing your environment? On the test day instructions page - https://www.rdoproject.org/testday/newton/testedsetups_rc - each test has a HOWTO link, and almost all of these link to the Quickstart or nothing at all. As a beginner, that's baffling. How are these separate tests if they all have exactly the same instructions? If I want to participate in testing, what am I actually supposed to do? What I'd like to see, eventually, is a HowTo page (or script, or ... something) for every one of these test scenarios, showing what steps need to be taken to exercise the specified functionality. I presume that in many cases, there are in fact scripts that can be pointed at. These instructions provide multiple purposes - they also show someone how to set up these scenarios for production, and explain what the difference scenarios are good for. -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From hguemar at fedoraproject.org Tue Sep 20 16:55:33 2016 From: hguemar at fedoraproject.org (=?UTF-8?Q?Ha=C3=AFkel?=) Date: Tue, 20 Sep 2016 18:55:33 +0200 Subject: [rdo-list] RabbitMQ version in RDO In-Reply-To: References: Message-ID: 2016-09-20 17:50 GMT+02:00 Mohammed Naser : > Hi Alan: > > Thanks for pointing me to the RabbitMQ packages, we're going to test > those internally and report if we run into the issue again. > > I do agree with what David has pointed out in that there should be a > process setup in order to make sure that the shipped packages that > come with RDO (at least the supporting ones such as MariaDB/Galera, > etc) should be good-to-go. I imagine this might make things a bit > more difficult in terms of testing them, so I'm not sure what would be > the best path to take in this case. > > Thanks > Mohammed > These are already tested in our CI + upstream CI. And get immediate feedback when pushing broken versions of these components in -testing (AFAIK, -release is safe) > On Tue, Sep 20, 2016 at 11:05 AM, Alan Pevec wrote: >> On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard wrote: >>> I think with OpenStack components it's easier, there's branches and we >>> build/test them throughout the lifecycle. >>> Once we have the proper testing in place, we can update those more frequently. >> >> Ideally same would apply for dependencies like rabbitmq, mariadb, we'd >> update frequently and release after testing but also vetted by package >> maintainers. >> Let's start by this last part: I'll check that components in RDO >> bugzilla have correct default owner then we setup nagging like >> https://fedoraproject.org/wiki/Upstream_release_monitoring for few >> critical dependencies. >> >> Alan >> >> _______________________________________________ >> rdo-list mailing list >> rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> To unsubscribe: rdo-list-unsubscribe at redhat.com > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From imaslov at dispersivegroup.com Tue Sep 20 20:39:31 2016 From: imaslov at dispersivegroup.com (Ilja Maslov) Date: Tue, 20 Sep 2016 20:39:31 +0000 Subject: [rdo-list] Improving the test day experience In-Reply-To: <95c9fad4-9430-44bc-8e99-88f13c5be153@redhat.com> References: <20160920171135.567e01e85a31c18a8ede1ba0@redhat.com> <95c9fad4-9430-44bc-8e99-88f13c5be153@redhat.com> Message-ID: <6117f7f636e44481ae846c05d0dd3b5e@svr2-disp-exch.dispersive.local> Hi, I'd like to see realistic production baremetal scenarios tested, i.e. with network isolation, Ceph storage, firstboot hooks that set correct tuned profile. Thanks, Ilja -----Original Message----- From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Rich Bowen Sent: Tuesday, September 20, 2016 11:52 AM To: Petr Kovar Cc: rdo-list at redhat.com Subject: Re: [rdo-list] Improving the test day experience On 09/20/2016 11:11 AM, Petr Kovar wrote: > On Thu, 15 Sep 2016 15:59:22 -0400 > Rich Bowen wrote: > >> In our RDO Community Meeting (on IRC) yesterday, the topic of >> improving test day was brought up. >> >> Test day is, for the most part, about getting people to beat on the >> latest packages and find problems. However, since most of these >> problems are being found in CI, it's time to make test day also about >> giving people an opportunity to see what's coming in future releases. >> To that end, user experience is pretty important on test day. >> >> Several suggestions were made to improve the test day experience for >> folks that aren't already experts: >> >> >> * Test setup matrix cleanup? Remove tests that are no longer relevant. >> >> * More detailed, beginner-friendly instructions for testing. (Test >> day as product preview for potential users, or existing users who are >> not deep experts.) > > I can start working on this but would probably need more input wrt the > required scope of the instructions. Like, say, besides setting up a VM > with CentOS/RHEL for running packstack, are there other steps we want > to cover as part of preparing your environment? On the test day instructions page - https://www.rdoproject.org/testday/newton/testedsetups_rc - each test has a HOWTO link, and almost all of these link to the Quickstart or nothing at all. As a beginner, that's baffling. How are these separate tests if they all have exactly the same instructions? If I want to participate in testing, what am I actually supposed to do? What I'd like to see, eventually, is a HowTo page (or script, or ... something) for every one of these test scenarios, showing what steps need to be taken to exercise the specified functionality. I presume that in many cases, there are in fact scripts that can be pointed at. These instructions provide multiple purposes - they also show someone how to set up these scenarios for production, and explain what the difference scenarios are good for. -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity _______________________________________________ rdo-list mailing list rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscribe at redhat.com From rbowen at redhat.com Wed Sep 21 13:43:06 2016 From: rbowen at redhat.com (Rich Bowen) Date: Wed, 21 Sep 2016 09:43:06 -0400 Subject: [rdo-list] RDO Infrastructure meeting in Barcelona (OpenStack Summit) Message-ID: <14c3b7b7-7d14-833c-01e9-c438d9d79587@redhat.com> As previously discussed on the list - we've booked a meeting room to discuss RDO infrastructure on the Monday of OpenStack Summit. The details are: Location: Princess Hotel, right across from the venue. Date & time: Monday, October 24th, 2-4pm Room name: "Estrella de Mar" The room is not huge, so definitely come if you're willing/able to contribute to the discussion, but don't feel obliged to attend if it's not really your area. -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From dms at redhat.com Wed Sep 21 13:55:48 2016 From: dms at redhat.com (David Moreau Simard) Date: Wed, 21 Sep 2016 09:55:48 -0400 Subject: [rdo-list] RDO Infrastructure meeting in Barcelona (OpenStack Summit) In-Reply-To: <14c3b7b7-7d14-833c-01e9-c438d9d79587@redhat.com> References: <14c3b7b7-7d14-833c-01e9-c438d9d79587@redhat.com> Message-ID: Thanks Rich. I've gone ahead and created an etherpad: https://review.rdoproject.org/etherpad/p/barcelona-rdo-infra-meetup David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Wed, Sep 21, 2016 at 9:43 AM, Rich Bowen wrote: > As previously discussed on the list - we've booked a meeting room to > discuss RDO infrastructure on the Monday of OpenStack Summit. The > details are: > > Location: Princess Hotel, right across from the venue. > Date & time: Monday, October 24th, 2-4pm > Room name: "Estrella de Mar" > > The room is not huge, so definitely come if you're willing/able to > contribute to the discussion, but don't feel obliged to attend if it's > not really your area. > > > -- > Rich Bowen - rbowen at redhat.com > RDO Community Liaison > http://rdoproject.org > @RDOCommunity > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From rbowen at redhat.com Wed Sep 21 15:36:35 2016 From: rbowen at redhat.com (Rich Bowen) Date: Wed, 21 Sep 2016 11:36:35 -0400 Subject: [rdo-list] New mailing list: rdo-infra-list Message-ID: As discussed in today's IRC meeting, we have created a new mailing list - rdo-infra-list at redhat.com - for the purpose of automated infra messages, outage notifications, and the like. Details about this list may be found at https://www.redhat.com/mailman/listinfo/rdo-infra-list Note that some day we will be moving mailing lists over to the @rdoproject.org hostname instead of @redhat.com but that infrastructure isn't in place yet. -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From ichavero at redhat.com Wed Sep 21 15:51:28 2016 From: ichavero at redhat.com (Ivan Chavero) Date: Wed, 21 Sep 2016 11:51:28 -0400 (EDT) Subject: [rdo-list] [Meeting] RDO meeting (2016-09-21) Minutes Message-ID: <813148634.611400.1474473088988.JavaMail.zimbra@redhat.com> ============================== #rdo: RDO meeting - 2016-09-21 ============================== Meeting started by imcsk8 at 15:00:15 UTC. The full logs are available at https://meetbot.fedoraproject.org/rdo/2016-09-21/rdo_meeting_-_2016-09-21.2016-09-21-15.00.log.html . Meeting summary --------------- * roll call (imcsk8, 15:00:24) * Need volunteers/topics to speak at the RDO/Ceph meetup in Barcelona - https://etherpad.openstack.org/p/rdo-barcelona-meetup-schedule We need to finalize the schedule soon so that we can start event promotion. (imcsk8, 15:01:56) * Updates on tempest/rally (imcsk8, 15:05:05) * LINK: https://github.com/redhat-openstack/website/pull/702 (chandankumar, 15:05:35) * LINK: https://review.gerrithub.io/#/c/295082/ (chandankumar, 15:06:42) * rdo-infra-list mailing list (imcsk8, 15:08:14) * ACTION: rbowen to request rdo-infra-list at redhat.com creation. (rbowen, 15:13:21) * RC testday Sep29/30 (imcsk8, 15:14:15) * Announcements (imcsk8, 15:24:53) * Chair for next meeting (imcsk8, 15:31:16) * Open Floor (imcsk8, 15:31:49) Meeting ended at 15:45:01 UTC. Action Items ------------ * rbowen to request rdo-infra-list at redhat.com creation. Action Items, by person ----------------------- * rbowen * rbowen to request rdo-infra-list at redhat.com creation. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * rbowen (49) * dmsimard (36) * imcsk8 (33) * apevec (26) * zodbot (15) * number80 (11) * weshay (10) * adarazs (9) * chandankumar (9) * jruzicka (8) * gfidente (7) * Duck (6) * amoralej (5) * jpena (5) * hrybacki (5) * wfoster (5) * leifmadsen (2) * trown (2) * openstackgerrit (2) * EmilienM (1) * coolsvap (1) * rdogerrit (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From javier.pena at redhat.com Wed Sep 21 16:12:07 2016 From: javier.pena at redhat.com (Javier Pena) Date: Wed, 21 Sep 2016 12:12:07 -0400 (EDT) Subject: [rdo-list] Improving the test day experience In-Reply-To: References: Message-ID: <1621043656.2618104.1474474327305.JavaMail.zimbra@redhat.com> ----- Original Message ----- > In our RDO Community Meeting (on IRC) yesterday, the topic of improving > test day was brought up. > > Test day is, for the most part, about getting people to beat on the > latest packages and find problems. However, since most of these problems > are being found in CI, it's time to make test day also about giving > people an opportunity to see what's coming in future releases. To that > end, user experience is pretty important on test day. > > Several suggestions were made to improve the test day experience for > folks that aren't already experts: > > > * Test setup matrix cleanup? Remove tests that are no longer relevant. > > * More detailed, beginner-friendly instructions for testing. (Test day > as product preview for potential users, or existing users who are not > deep experts.) > > * Ask other teams to provide use cases they want to validate. > > * Tracking the tests on an etherpad with instructions, and registering > people to use cases, so that we're sure that everything is being covered. > > > While these are all great suggestions, each requires that someone > actually step up and make it happen. Each test day, for example, we talk > about better instructions for the test scenarios, and everyone agrees > that it's a good idea. > > Anyways, as we start looking towards Ocata, are there other suggestions > as to how we can make the test day more welcoming to folks trying out > RDO for the first time, and existing OpenStack users looking for a > preview of the next release, as well as the usual suspects? And, as > importantly, people who are able to make some of these things happen? > During today's RDO meeting, I had the idea of having a pre-baked image with the basic setup (base CentOS + configured repos, maybe some documentation included) in TryStack or a cloud provider that would like to help us during the test day. Then, each tester could create a VM in that environment and run their own test scenario. Thinking of it, it requires: - A prepared image (not a big deal, we could do it) - A public cloud with enough resources for the test days, and enough security measures to prevent abuse - Anything else? Regards, Javier > Thanks. > > --Rich > > > -- > Rich Bowen - rbowen at redhat.com > RDO Community Liaison > http://rdoproject.org > @RDOCommunity > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > From jslagle at redhat.com Wed Sep 21 16:42:18 2016 From: jslagle at redhat.com (James Slagle) Date: Wed, 21 Sep 2016 12:42:18 -0400 Subject: [rdo-list] Maintaining os-*-config in Fedora Message-ID: <20160921164218.GD31467@localhost.localdomain> os-*-config (apply, cloud, collect, refresh, net) are still maintained in Fedora (despite that the maintainers, myself included, have not been doing regular builds). I've been asked by a couple people from Fedora to update these packages to build python 3 packages, and some other things like removing outdated Requires on python libraries that are now in the stdlib (argparse, etc). This raised the question for me though if we still want to maintain these packages in Fedora at all. Aiui, they were not retired when the rest of the core OpenStack packages were retired because os-*-config is useful when using Fedora as an instance orchestarted via Heat on OpenStack. However, we haven't been properly maintaining these packages in Fedora by doing updated builds to pick up new releases, not to mention that these packages and use case are entirely untested on Fedora to the best of my knowledge. os-cloud-config I think we can retire from Fedora without any concern since it is specific to TripleO. For the others, is there anyone who wants to take them over to continue to work on the "Fedora as an instance orchestrated via Heat" use case? If not, I propose to retire the others as well. Note that diskimage-builder and dib-utls are also still in Fedora but it appears that pabelanger has been keeping those updated, so is likely using them. -- -- James Slagle -- From hguemar at fedoraproject.org Wed Sep 21 17:00:36 2016 From: hguemar at fedoraproject.org (=?UTF-8?Q?Ha=C3=AFkel?=) Date: Wed, 21 Sep 2016 19:00:36 +0200 Subject: [rdo-list] Maintaining os-*-config in Fedora In-Reply-To: <20160921164218.GD31467@localhost.localdomain> References: <20160921164218.GD31467@localhost.localdomain> Message-ID: 2016-09-21 18:42 GMT+02:00 James Slagle : > os-*-config (apply, cloud, collect, refresh, net) are still maintained in > Fedora (despite that the maintainers, myself included, have not been doing > regular builds). > > I've been asked by a couple people from Fedora to update these packages to > build python 3 packages, and some other things like removing outdated Requires > on python libraries that are now in the stdlib (argparse, etc). > > This raised the question for me though if we still want to maintain these > packages in Fedora at all. Aiui, they were not retired when the rest of the > core OpenStack packages were retired because os-*-config is useful when using > Fedora as an instance orchestarted via Heat on OpenStack. > > However, we haven't been properly maintaining these packages in Fedora by doing > updated builds to pick up new releases, not to mention that these packages and > use case are entirely untested on Fedora to the best of my knowledge. > > os-cloud-config I think we can retire from Fedora without any concern since it > is specific to TripleO. > > For the others, is there anyone who wants to take them over to continue to work > on the "Fedora as an instance orchestrated via Heat" use case? If not, I > propose to retire the others as well. > > Note that diskimage-builder and dib-utls are also still in Fedora but it > appears that pabelanger has been keeping those updated, so is likely using > them. > Well as a matter of fact, we can just sync them like we do with clients. If they're useful to orchestrate Fedora instances with Heat, then I'd rather keep them around. H. > -- > -- James Slagle > -- > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From apevec at redhat.com Wed Sep 21 17:48:23 2016 From: apevec at redhat.com (Alan Pevec) Date: Wed, 21 Sep 2016 19:48:23 +0200 Subject: [rdo-list] Maintaining os-*-config in Fedora In-Reply-To: References: <20160921164218.GD31467@localhost.localdomain> Message-ID: > Well as a matter of fact, we can just sync them like we do with clients. > If they're useful to orchestrate Fedora instances with Heat, then I'd > rather keep them around. But that's the question I asked when doing last round of retirements in Fedora: is anyone actually using Fedora instances with Heat?? Should we run quick user survey on rdo/fedora/openstack lists? Alan From hrybacki at redhat.com Wed Sep 21 17:54:30 2016 From: hrybacki at redhat.com (Harry Rybacki) Date: Wed, 21 Sep 2016 13:54:30 -0400 Subject: [rdo-list] Improving the test day experience In-Reply-To: <1621043656.2618104.1474474327305.JavaMail.zimbra@redhat.com> References: <1621043656.2618104.1474474327305.JavaMail.zimbra@redhat.com> Message-ID: I would also like to throw out that we are in the process of expanding coverage for TripleO-Quickstart post-build generated documentation. For the last test day, we had three sets of example docs available[1]: - minimal - baremetal - ovb Hopefully there will be docs for updates and upgrades to follow shortly. As discussed with rbowen in today's RDO meeting, we will have these docs linked in the test matrix for the next test day for increased visibility. [1] - http://images.rdoproject.org/docs/ /R Harry On Wed, Sep 21, 2016 at 12:12 PM, Javier Pena wrote: > > > ----- Original Message ----- >> In our RDO Community Meeting (on IRC) yesterday, the topic of improving >> test day was brought up. >> >> Test day is, for the most part, about getting people to beat on the >> latest packages and find problems. However, since most of these problems >> are being found in CI, it's time to make test day also about giving >> people an opportunity to see what's coming in future releases. To that >> end, user experience is pretty important on test day. >> >> Several suggestions were made to improve the test day experience for >> folks that aren't already experts: >> >> >> * Test setup matrix cleanup? Remove tests that are no longer relevant. >> >> * More detailed, beginner-friendly instructions for testing. (Test day >> as product preview for potential users, or existing users who are not >> deep experts.) >> >> * Ask other teams to provide use cases they want to validate. >> >> * Tracking the tests on an etherpad with instructions, and registering >> people to use cases, so that we're sure that everything is being covered. >> >> >> While these are all great suggestions, each requires that someone >> actually step up and make it happen. Each test day, for example, we talk >> about better instructions for the test scenarios, and everyone agrees >> that it's a good idea. >> >> Anyways, as we start looking towards Ocata, are there other suggestions >> as to how we can make the test day more welcoming to folks trying out >> RDO for the first time, and existing OpenStack users looking for a >> preview of the next release, as well as the usual suspects? And, as >> importantly, people who are able to make some of these things happen? >> > > During today's RDO meeting, I had the idea of having a pre-baked image with the basic setup (base CentOS + configured repos, maybe some documentation included) in TryStack or a cloud provider that would like to help us during the test day. Then, each tester could create a VM in that environment and run their own test scenario. > > Thinking of it, it requires: > > - A prepared image (not a big deal, we could do it) > - A public cloud with enough resources for the test days, and enough security measures to prevent abuse > - Anything else? > > Regards, > Javier > >> Thanks. >> >> --Rich >> >> >> -- >> Rich Bowen - rbowen at redhat.com >> RDO Community Liaison >> http://rdoproject.org >> @RDOCommunity >> >> _______________________________________________ >> rdo-list mailing list >> rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> To unsubscribe: rdo-list-unsubscribe at redhat.com >> > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From nhicher at redhat.com Thu Sep 22 15:35:18 2016 From: nhicher at redhat.com (Nicolas Hicher) Date: Thu, 22 Sep 2016 11:35:18 -0400 Subject: [rdo-list] Scheduled maintenance of review.rdoproject.org: 2016-10-10 13:00 UTC Message-ID: Hello folks, We plan to upgrade review.rdoproject.org on 2016-10-10 13:00 UTC. The downtime will be about 1 hour approximately. This is a maintenance upgrade to the next stable version of Software Factory 2.2.5. Regards, Software Factory Team, on behalf of rdo-infra From lorenzetto.luca at gmail.com Fri Sep 23 12:56:56 2016 From: lorenzetto.luca at gmail.com (Luca 'remix_tj' Lorenzetto) Date: Fri, 23 Sep 2016 14:56:56 +0200 Subject: [rdo-list] Manila and TripleO Message-ID: Hello, i see on docs [0] that there is a support (even if WIP) for Manila in TripleO in Mitaka. This requires an heat template, which seems to be missing. I've seen a previous email on this list that reported that this will be implemented with Newton since Composable Services will be available. Does anyone has further informations about Mitaka status? If is not possible to configure through tripleo in an automated way, is there a way have the service anyway? Luca [0] http://docs.openstack.org/developer/tripleo-docs/advanced_deployment/deploy_manila.html -- "E' assurdo impiegare gli uomini di intelligenza eccellente per fare calcoli che potrebbero essere affidati a chiunque se si usassero delle macchine" Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) "Internet ? la pi? grande biblioteca del mondo. Ma il problema ? che i libri sono tutti sparsi sul pavimento" John Allen Paulos, Matematico (1945-vivente) Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , From dms at redhat.com Fri Sep 23 13:40:03 2016 From: dms at redhat.com (David Moreau Simard) Date: Fri, 23 Sep 2016 09:40:03 -0400 Subject: [rdo-list] A note about the new rdo-infra-list mailing list (tl; dr, please set filters) Message-ID: Hi, I posted this to rdo-infra-list already but I felt like it needed to be cross-posted here so it's not missed by new subscribers. I'm seeing some subscriptions on this mailing list and before we officially started using it, I wanted to make it's intent clear. This new mailing list's purpose is largely for automated emails generated by CI or Monitoring. As per discussed in the RDO meeting [1] this week we needed a mechanism to distribute these notifications in order to allow interested parties to subscribe to them. Discussions will always take place on rdo-list, there should not be any discussion on that list and in fact, the reply-to is set to rdo-list. If you attempt to get a human's attention by posting to rdo-infra-list, it will largely be in vain as it is expected that people will have heavy filters in place. It doesn't mean this won't change in the future but that's the expected purpose for the time being. Notifications have already started, you can see an example here [2]. Please set up filters if you are subscribed, I shall not be held responsible for the state of your inbox if you don't :) Thanks, [1]: https://meetbot.fedoraproject.org/rdo/2016-09-21/rdo_meeting_-_2016-09-21.2016-09-21-15.00.log.html [2]: https://www.redhat.com/archives/rdo-infra-list/2016-September/msg00004.html David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] From adam.huffman at gmail.com Sun Sep 25 20:11:00 2016 From: adam.huffman at gmail.com (Adam Huffman) Date: Sun, 25 Sep 2016 21:11:00 +0100 Subject: [rdo-list] Improving the test day experience In-Reply-To: References: <1621043656.2618104.1474474327305.JavaMail.zimbra@redhat.com> Message-ID: Hi Harry, Where ought I to report bugs found in testing those docs? Cheers, Adam On 21 Sep 2016 6:55 pm, "Harry Rybacki" wrote: > I would also like to throw out that we are in the process of expanding > coverage for TripleO-Quickstart post-build generated documentation. > > For the last test day, we had three sets of example docs available[1]: > - minimal > - baremetal > - ovb > > Hopefully there will be docs for updates and upgrades to follow > shortly. As discussed with rbowen in today's RDO meeting, we will have > these docs linked in the test matrix for the next test day for > increased visibility. > > [1] - http://images.rdoproject.org/docs/ > > > /R > > Harry > > On Wed, Sep 21, 2016 at 12:12 PM, Javier Pena > wrote: > > > > > > ----- Original Message ----- > >> In our RDO Community Meeting (on IRC) yesterday, the topic of improving > >> test day was brought up. > >> > >> Test day is, for the most part, about getting people to beat on the > >> latest packages and find problems. However, since most of these problems > >> are being found in CI, it's time to make test day also about giving > >> people an opportunity to see what's coming in future releases. To that > >> end, user experience is pretty important on test day. > >> > >> Several suggestions were made to improve the test day experience for > >> folks that aren't already experts: > >> > >> > >> * Test setup matrix cleanup? Remove tests that are no longer relevant. > >> > >> * More detailed, beginner-friendly instructions for testing. (Test day > >> as product preview for potential users, or existing users who are not > >> deep experts.) > >> > >> * Ask other teams to provide use cases they want to validate. > >> > >> * Tracking the tests on an etherpad with instructions, and registering > >> people to use cases, so that we're sure that everything is being > covered. > >> > >> > >> While these are all great suggestions, each requires that someone > >> actually step up and make it happen. Each test day, for example, we talk > >> about better instructions for the test scenarios, and everyone agrees > >> that it's a good idea. > >> > >> Anyways, as we start looking towards Ocata, are there other suggestions > >> as to how we can make the test day more welcoming to folks trying out > >> RDO for the first time, and existing OpenStack users looking for a > >> preview of the next release, as well as the usual suspects? And, as > >> importantly, people who are able to make some of these things happen? > >> > > > > During today's RDO meeting, I had the idea of having a pre-baked image > with the basic setup (base CentOS + configured repos, maybe some > documentation included) in TryStack or a cloud provider that would like to > help us during the test day. Then, each tester could create a VM in that > environment and run their own test scenario. > > > > Thinking of it, it requires: > > > > - A prepared image (not a big deal, we could do it) > > - A public cloud with enough resources for the test days, and enough > security measures to prevent abuse > > - Anything else? > > > > Regards, > > Javier > > > >> Thanks. > >> > >> --Rich > >> > >> > >> -- > >> Rich Bowen - rbowen at redhat.com > >> RDO Community Liaison > >> http://rdoproject.org > >> @RDOCommunity > >> > >> _______________________________________________ > >> rdo-list mailing list > >> rdo-list at redhat.com > >> https://www.redhat.com/mailman/listinfo/rdo-list > >> > >> To unsubscribe: rdo-list-unsubscribe at redhat.com > >> > > > > _______________________________________________ > > rdo-list mailing list > > rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > To unsubscribe: rdo-list-unsubscribe at redhat.com > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ak at cloudssky.com Mon Sep 26 00:03:05 2016 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Mon, 26 Sep 2016 02:03:05 +0200 Subject: [rdo-list] Improving the test day experience In-Reply-To: References: <1621043656.2618104.1474474327305.JavaMail.zimbra@redhat.com> Message-ID: Hi, e.g. the link on this page is dead: https://images.rdoproject.org/docs/baremetal/customizing-external-network-vlan.html 404 link: https://github.com/openstack/tripleo-quickstart/blob/master/roles/tripleo/undercloud/templates/undercloud-install-post.sh.j2#L88 Cheers, Arash On Sun, Sep 25, 2016 at 10:11 PM, Adam Huffman wrote: > Hi Harry, > > Where ought I to report bugs found in testing those docs? > > Cheers, > Adam > > On 21 Sep 2016 6:55 pm, "Harry Rybacki" wrote: > >> I would also like to throw out that we are in the process of expanding >> coverage for TripleO-Quickstart post-build generated documentation. >> >> For the last test day, we had three sets of example docs available[1]: >> - minimal >> - baremetal >> - ovb >> >> Hopefully there will be docs for updates and upgrades to follow >> shortly. As discussed with rbowen in today's RDO meeting, we will have >> these docs linked in the test matrix for the next test day for >> increased visibility. >> >> [1] - http://images.rdoproject.org/docs/ >> >> >> /R >> >> Harry >> >> On Wed, Sep 21, 2016 at 12:12 PM, Javier Pena >> wrote: >> > >> > >> > ----- Original Message ----- >> >> In our RDO Community Meeting (on IRC) yesterday, the topic of improving >> >> test day was brought up. >> >> >> >> Test day is, for the most part, about getting people to beat on the >> >> latest packages and find problems. However, since most of these >> problems >> >> are being found in CI, it's time to make test day also about giving >> >> people an opportunity to see what's coming in future releases. To that >> >> end, user experience is pretty important on test day. >> >> >> >> Several suggestions were made to improve the test day experience for >> >> folks that aren't already experts: >> >> >> >> >> >> * Test setup matrix cleanup? Remove tests that are no longer relevant. >> >> >> >> * More detailed, beginner-friendly instructions for testing. (Test day >> >> as product preview for potential users, or existing users who are not >> >> deep experts.) >> >> >> >> * Ask other teams to provide use cases they want to validate. >> >> >> >> * Tracking the tests on an etherpad with instructions, and registering >> >> people to use cases, so that we're sure that everything is being >> covered. >> >> >> >> >> >> While these are all great suggestions, each requires that someone >> >> actually step up and make it happen. Each test day, for example, we >> talk >> >> about better instructions for the test scenarios, and everyone agrees >> >> that it's a good idea. >> >> >> >> Anyways, as we start looking towards Ocata, are there other suggestions >> >> as to how we can make the test day more welcoming to folks trying out >> >> RDO for the first time, and existing OpenStack users looking for a >> >> preview of the next release, as well as the usual suspects? And, as >> >> importantly, people who are able to make some of these things happen? >> >> >> > >> > During today's RDO meeting, I had the idea of having a pre-baked image >> with the basic setup (base CentOS + configured repos, maybe some >> documentation included) in TryStack or a cloud provider that would like to >> help us during the test day. Then, each tester could create a VM in that >> environment and run their own test scenario. >> > >> > Thinking of it, it requires: >> > >> > - A prepared image (not a big deal, we could do it) >> > - A public cloud with enough resources for the test days, and enough >> security measures to prevent abuse >> > - Anything else? >> > >> > Regards, >> > Javier >> > >> >> Thanks. >> >> >> >> --Rich >> >> >> >> >> >> -- >> >> Rich Bowen - rbowen at redhat.com >> >> RDO Community Liaison >> >> http://rdoproject.org >> >> @RDOCommunity >> >> >> >> _______________________________________________ >> >> rdo-list mailing list >> >> rdo-list at redhat.com >> >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> >> >> To unsubscribe: rdo-list-unsubscribe at redhat.com >> >> >> > >> > _______________________________________________ >> > rdo-list mailing list >> > rdo-list at redhat.com >> > https://www.redhat.com/mailman/listinfo/rdo-list >> > >> > To unsubscribe: rdo-list-unsubscribe at redhat.com >> >> _______________________________________________ >> rdo-list mailing list >> rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> To unsubscribe: rdo-list-unsubscribe at redhat.com >> > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hrybacki at redhat.com Mon Sep 26 12:52:47 2016 From: hrybacki at redhat.com (Harry Rybacki) Date: Mon, 26 Sep 2016 08:52:47 -0400 Subject: [rdo-list] Improving the test day experience In-Reply-To: References: <1621043656.2618104.1474474327305.JavaMail.zimbra@redhat.com> Message-ID: Yay for bug reports! The best way to submit reports would either be through the tripleo-collect-logs GH issue tracker[1] or to my email directly (less preferred). [1] - https://github.com/redhat-openstack/ansible-role-tripleo-collect-logs/issues /R Harry On Sun, Sep 25, 2016 at 8:03 PM, Arash Kaffamanesh wrote: > Hi, > > e.g. the link on this page is dead: > > https://images.rdoproject.org/docs/baremetal/customizing-external-network-vlan.html > > 404 link: > https://github.com/openstack/tripleo-quickstart/blob/master/roles/tripleo/undercloud/templates/undercloud-install-post.sh.j2#L88 > > Cheers, > Arash > > > On Sun, Sep 25, 2016 at 10:11 PM, Adam Huffman > wrote: >> >> Hi Harry, >> >> Where ought I to report bugs found in testing those docs? >> >> Cheers, >> Adam >> >> >> On 21 Sep 2016 6:55 pm, "Harry Rybacki" wrote: >>> >>> I would also like to throw out that we are in the process of expanding >>> coverage for TripleO-Quickstart post-build generated documentation. >>> >>> For the last test day, we had three sets of example docs available[1]: >>> - minimal >>> - baremetal >>> - ovb >>> >>> Hopefully there will be docs for updates and upgrades to follow >>> shortly. As discussed with rbowen in today's RDO meeting, we will have >>> these docs linked in the test matrix for the next test day for >>> increased visibility. >>> >>> [1] - http://images.rdoproject.org/docs/ >>> >>> >>> /R >>> >>> Harry >>> >>> On Wed, Sep 21, 2016 at 12:12 PM, Javier Pena >>> wrote: >>> > >>> > >>> > ----- Original Message ----- >>> >> In our RDO Community Meeting (on IRC) yesterday, the topic of >>> >> improving >>> >> test day was brought up. >>> >> >>> >> Test day is, for the most part, about getting people to beat on the >>> >> latest packages and find problems. However, since most of these >>> >> problems >>> >> are being found in CI, it's time to make test day also about giving >>> >> people an opportunity to see what's coming in future releases. To that >>> >> end, user experience is pretty important on test day. >>> >> >>> >> Several suggestions were made to improve the test day experience for >>> >> folks that aren't already experts: >>> >> >>> >> >>> >> * Test setup matrix cleanup? Remove tests that are no longer relevant. >>> >> >>> >> * More detailed, beginner-friendly instructions for testing. (Test day >>> >> as product preview for potential users, or existing users who are not >>> >> deep experts.) >>> >> >>> >> * Ask other teams to provide use cases they want to validate. >>> >> >>> >> * Tracking the tests on an etherpad with instructions, and registering >>> >> people to use cases, so that we're sure that everything is being >>> >> covered. >>> >> >>> >> >>> >> While these are all great suggestions, each requires that someone >>> >> actually step up and make it happen. Each test day, for example, we >>> >> talk >>> >> about better instructions for the test scenarios, and everyone agrees >>> >> that it's a good idea. >>> >> >>> >> Anyways, as we start looking towards Ocata, are there other >>> >> suggestions >>> >> as to how we can make the test day more welcoming to folks trying out >>> >> RDO for the first time, and existing OpenStack users looking for a >>> >> preview of the next release, as well as the usual suspects? And, as >>> >> importantly, people who are able to make some of these things happen? >>> >> >>> > >>> > During today's RDO meeting, I had the idea of having a pre-baked image >>> > with the basic setup (base CentOS + configured repos, maybe some >>> > documentation included) in TryStack or a cloud provider that would like to >>> > help us during the test day. Then, each tester could create a VM in that >>> > environment and run their own test scenario. >>> > >>> > Thinking of it, it requires: >>> > >>> > - A prepared image (not a big deal, we could do it) >>> > - A public cloud with enough resources for the test days, and enough >>> > security measures to prevent abuse >>> > - Anything else? >>> > >>> > Regards, >>> > Javier >>> > >>> >> Thanks. >>> >> >>> >> --Rich >>> >> >>> >> >>> >> -- >>> >> Rich Bowen - rbowen at redhat.com >>> >> RDO Community Liaison >>> >> http://rdoproject.org >>> >> @RDOCommunity >>> >> >>> >> _______________________________________________ >>> >> rdo-list mailing list >>> >> rdo-list at redhat.com >>> >> https://www.redhat.com/mailman/listinfo/rdo-list >>> >> >>> >> To unsubscribe: rdo-list-unsubscribe at redhat.com >>> >> >>> > >>> > _______________________________________________ >>> > rdo-list mailing list >>> > rdo-list at redhat.com >>> > https://www.redhat.com/mailman/listinfo/rdo-list >>> > >>> > To unsubscribe: rdo-list-unsubscribe at redhat.com >>> >>> _______________________________________________ >>> rdo-list mailing list >>> rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >>> To unsubscribe: rdo-list-unsubscribe at redhat.com >> >> >> _______________________________________________ >> rdo-list mailing list >> rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> To unsubscribe: rdo-list-unsubscribe at redhat.com > > From hguemar at fedoraproject.org Mon Sep 26 15:00:04 2016 From: hguemar at fedoraproject.org (hguemar at fedoraproject.org) Date: Mon, 26 Sep 2016 15:00:04 +0000 (UTC) Subject: [rdo-list] [Fedocal] Reminder meeting : RDO meeting Message-ID: <20160926150004.4138F60A3FDC@fedocal02.phx2.fedoraproject.org> Dear all, You are kindly invited to the meeting: RDO meeting on 2016-09-28 from 15:00:00 to 16:00:00 UTC At rdo at 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/ From rbowen at redhat.com Tue Sep 27 11:05:24 2016 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 27 Sep 2016 07:05:24 -0400 Subject: [rdo-list] Improving the test day experience In-Reply-To: References: <1621043656.2618104.1474474327305.JavaMail.zimbra@redhat.com> Message-ID: The preferred place to report bugs in the website is https://github.com/redhat-openstack/website/issues On Sep 25, 2016 16:11, "Adam Huffman" wrote: > Hi Harry, > > Where ought I to report bugs found in testing those docs? > > Cheers, > Adam > > On 21 Sep 2016 6:55 pm, "Harry Rybacki" wrote: > >> I would also like to throw out that we are in the process of expanding >> coverage for TripleO-Quickstart post-build generated documentation. >> >> For the last test day, we had three sets of example docs available[1]: >> - minimal >> - baremetal >> - ovb >> >> Hopefully there will be docs for updates and upgrades to follow >> shortly. As discussed with rbowen in today's RDO meeting, we will have >> these docs linked in the test matrix for the next test day for >> increased visibility. >> >> [1] - http://images.rdoproject.org/docs/ >> >> >> /R >> >> Harry >> >> On Wed, Sep 21, 2016 at 12:12 PM, Javier Pena >> wrote: >> > >> > >> > ----- Original Message ----- >> >> In our RDO Community Meeting (on IRC) yesterday, the topic of improving >> >> test day was brought up. >> >> >> >> Test day is, for the most part, about getting people to beat on the >> >> latest packages and find problems. However, since most of these >> problems >> >> are being found in CI, it's time to make test day also about giving >> >> people an opportunity to see what's coming in future releases. To that >> >> end, user experience is pretty important on test day. >> >> >> >> Several suggestions were made to improve the test day experience for >> >> folks that aren't already experts: >> >> >> >> >> >> * Test setup matrix cleanup? Remove tests that are no longer relevant. >> >> >> >> * More detailed, beginner-friendly instructions for testing. (Test day >> >> as product preview for potential users, or existing users who are not >> >> deep experts.) >> >> >> >> * Ask other teams to provide use cases they want to validate. >> >> >> >> * Tracking the tests on an etherpad with instructions, and registering >> >> people to use cases, so that we're sure that everything is being >> covered. >> >> >> >> >> >> While these are all great suggestions, each requires that someone >> >> actually step up and make it happen. Each test day, for example, we >> talk >> >> about better instructions for the test scenarios, and everyone agrees >> >> that it's a good idea. >> >> >> >> Anyways, as we start looking towards Ocata, are there other suggestions >> >> as to how we can make the test day more welcoming to folks trying out >> >> RDO for the first time, and existing OpenStack users looking for a >> >> preview of the next release, as well as the usual suspects? And, as >> >> importantly, people who are able to make some of these things happen? >> >> >> > >> > During today's RDO meeting, I had the idea of having a pre-baked image >> with the basic setup (base CentOS + configured repos, maybe some >> documentation included) in TryStack or a cloud provider that would like to >> help us during the test day. Then, each tester could create a VM in that >> environment and run their own test scenario. >> > >> > Thinking of it, it requires: >> > >> > - A prepared image (not a big deal, we could do it) >> > - A public cloud with enough resources for the test days, and enough >> security measures to prevent abuse >> > - Anything else? >> > >> > Regards, >> > Javier >> > >> >> Thanks. >> >> >> >> --Rich >> >> >> >> >> >> -- >> >> Rich Bowen - rbowen at redhat.com >> >> RDO Community Liaison >> >> http://rdoproject.org >> >> @RDOCommunity >> >> >> >> _______________________________________________ >> >> rdo-list mailing list >> >> rdo-list at redhat.com >> >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> >> >> To unsubscribe: rdo-list-unsubscribe at redhat.com >> >> >> > >> > _______________________________________________ >> > rdo-list mailing list >> > rdo-list at redhat.com >> > https://www.redhat.com/mailman/listinfo/rdo-list >> > >> > To unsubscribe: rdo-list-unsubscribe at redhat.com >> >> _______________________________________________ >> rdo-list mailing list >> rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> To unsubscribe: rdo-list-unsubscribe at redhat.com >> > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mnaser at vexxhost.com Tue Sep 27 15:22:47 2016 From: mnaser at vexxhost.com (Mohammed Naser) Date: Tue, 27 Sep 2016 11:22:47 -0400 Subject: [rdo-list] RabbitMQ version in RDO In-Reply-To: References: Message-ID: On Tue, Sep 20, 2016 at 12:55 PM, Ha?kel wrote: > 2016-09-20 17:50 GMT+02:00 Mohammed Naser : >> Hi Alan: >> >> Thanks for pointing me to the RabbitMQ packages, we're going to test >> those internally and report if we run into the issue again. >> >> I do agree with what David has pointed out in that there should be a >> process setup in order to make sure that the shipped packages that >> come with RDO (at least the supporting ones such as MariaDB/Galera, >> etc) should be good-to-go. I imagine this might make things a bit >> more difficult in terms of testing them, so I'm not sure what would be >> the best path to take in this case. >> >> Thanks >> Mohammed >> > > These are already tested in our CI + upstream CI. > And get immediate feedback when pushing broken versions of these > components in -testing (AFAIK, -release is safe) > Hi everyone: We've been running this for a few days now with no reported issues. We don't seem to be running into that issue anymore that was crashing nodes. Would it be possible to look into promoting this packages so that other RDO users are not affected this issue? Thanks! Mohammed >> On Tue, Sep 20, 2016 at 11:05 AM, Alan Pevec wrote: >>> On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard wrote: >>>> I think with OpenStack components it's easier, there's branches and we >>>> build/test them throughout the lifecycle. >>>> Once we have the proper testing in place, we can update those more frequently. >>> >>> Ideally same would apply for dependencies like rabbitmq, mariadb, we'd >>> update frequently and release after testing but also vetted by package >>> maintainers. >>> Let's start by this last part: I'll check that components in RDO >>> bugzilla have correct default owner then we setup nagging like >>> https://fedoraproject.org/wiki/Upstream_release_monitoring for few >>> critical dependencies. >>> >>> Alan >>> >>> _______________________________________________ >>> rdo-list mailing list >>> rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >>> To unsubscribe: rdo-list-unsubscribe at redhat.com >> >> _______________________________________________ >> rdo-list mailing list >> rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> To unsubscribe: rdo-list-unsubscribe at redhat.com From rbowen at redhat.com Tue Sep 27 15:26:42 2016 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 27 Sep 2016 11:26:42 -0400 Subject: [rdo-list] OpenStack Days (Seattle|Paris|Motreal) Message-ID: If you will be attending OpenStack Days in Seattle, Paris, or Montreal, in the coming weeks, I would very much like to hear from you. Thanks. -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From mnaser at vexxhost.com Tue Sep 27 15:38:40 2016 From: mnaser at vexxhost.com (Mohammed Naser) Date: Tue, 27 Sep 2016 11:38:40 -0400 Subject: [rdo-list] OpenStack Days (Seattle|Paris|Motreal) In-Reply-To: References: Message-ID: Hi Rich, I'm part of the organizing commitee for the Montreal day. Please let me know if would like to get in touch. Thanks, Mohammed On Tue, Sep 27, 2016 at 11:26 AM, Rich Bowen wrote: > If you will be attending OpenStack Days in Seattle, Paris, or Montreal, > in the coming weeks, I would very much like to hear from you. > > Thanks. > > > -- > Rich Bowen - rbowen at redhat.com > RDO Community Liaison > http://rdoproject.org > @RDOCommunity > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From pabelanger at redhat.com Tue Sep 27 15:39:02 2016 From: pabelanger at redhat.com (Paul Belanger) Date: Tue, 27 Sep 2016 11:39:02 -0400 Subject: [rdo-list] OpenStack Days (Seattle|Paris|Motreal) In-Reply-To: References: Message-ID: <20160927153902.GA24019@localhost.localdomain> On Tue, Sep 27, 2016 at 11:26:42AM -0400, Rich Bowen wrote: > If you will be attending OpenStack Days in Seattle, Paris, or Montreal, > in the coming weeks, I would very much like to hear from you. > I've submitted a talk for Montreal, still waiting to hear back. > Thanks. > > > -- > Rich Bowen - rbowen at redhat.com > RDO Community Liaison > http://rdoproject.org > @RDOCommunity > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From mnaser at vexxhost.com Tue Sep 27 15:48:50 2016 From: mnaser at vexxhost.com (Mohammed Naser) Date: Tue, 27 Sep 2016 11:48:50 -0400 Subject: [rdo-list] OpenStack Days (Seattle|Paris|Motreal) In-Reply-To: <20160927153902.GA24019@localhost.localdomain> References: <20160927153902.GA24019@localhost.localdomain> Message-ID: On Tue, Sep 27, 2016 at 11:39 AM, Paul Belanger wrote: > On Tue, Sep 27, 2016 at 11:26:42AM -0400, Rich Bowen wrote: >> If you will be attending OpenStack Days in Seattle, Paris, or Montreal, >> in the coming weeks, I would very much like to hear from you. >> > I've submitted a talk for Montreal, still waiting to hear back. > Hi Paul, We'll be starting to go through those shortly, probably sometime this week or next week Thanks Mohammed >> Thanks. >> >> >> -- >> Rich Bowen - rbowen at redhat.com >> RDO Community Liaison >> http://rdoproject.org >> @RDOCommunity >> >> _______________________________________________ >> rdo-list mailing list >> rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> To unsubscribe: rdo-list-unsubscribe at redhat.com > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com From rbowen at redhat.com Tue Sep 27 17:58:15 2016 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 27 Sep 2016 13:58:15 -0400 Subject: [rdo-list] Unanswered 'RDO' questions on ask.openstack.org Message-ID: 28 unanswered questions: is there a safe method of installing identity v3 properly with Liberty or Mitaka? https://ask.openstack.org/en/question/97137/is-there-a-safe-method-of-installing-identity-v3-properly-with-liberty-or-mitaka/ Tags: identity, liberty, mitaka, rdo Murano Requirements https://ask.openstack.org/en/question/96986/murano-requirements/ Tags: murano can not ping internet when launch instance cirros on mitaka https://ask.openstack.org/en/question/96949/can-not-ping-internet-when-launch-instance-cirros-on-mitaka/ Tags: cirros, security-groups, mitaka, mitaka-neutron After adding multiple compute nodes using packstack unable to see the nodes in dashboard https://ask.openstack.org/en/question/96732/after-adding-multiple-compute-nodes-using-packstack-unable-to-see-the-nodes-in-dashboard/ Tags: rdo [trove] mongodb cluster-grow failed https://ask.openstack.org/en/question/96571/trove-mongodb-cluster-grow-failed/ Tags: trove, mongodb, cluster, grow quota show is different from horizon in RDO after update quota with command https://ask.openstack.org/en/question/96244/quota-show-is-different-from-horizon-in-rdo-after-update-quota-with-command/ Tags: rdo "Parameter outiface failed on Firewall" during installation of openstack rdo on centos 7 https://ask.openstack.org/en/question/95657/parameter-outiface-failed-on-firewall-during-installation-of-openstack-rdo-on-centos-7/ Tags: rdo, devstack#mitaka multi nodes provider network ovs config https://ask.openstack.org/en/question/95423/multi-nodes-provider-network-ovs-config/ Tags: rdo, liberty-neutron Adding additional packages to an RDO installation https://ask.openstack.org/en/question/95380/adding-additional-packages-to-an-rdo-installation/ Tags: rdo, mistral RDO TripleO Mitaka HA Overcloud Failing https://ask.openstack.org/en/question/95249/rdo-tripleo-mitaka-ha-overcloud-failing/ Tags: mitaka, tripleo, overcloud, centos7 RDO - is there any fedora package newer than puppet-4.2.1-3.fc24.noarch.rpm https://ask.openstack.org/en/question/94969/rdo-is-there-any-fedora-package-newer-than-puppet-421-3fc24noarchrpm/ Tags: rdo, puppet, install-openstack OpenStack RDO mysqld 100% cpu https://ask.openstack.org/en/question/94961/openstack-rdo-mysqld-100-cpu/ Tags: openstack, mysqld, cpu Failed to set RDO repo on host-packstack-centOS-7 https://ask.openstack.org/en/question/94828/failed-to-set-rdo-repo-on-host-packstack-centos-7/ Tags: openstack-packstack, centos7, rdo how to deploy haskell-distributed in RDO? https://ask.openstack.org/en/question/94785/how-to-deploy-haskell-distributed-in-rdo/ Tags: rdo rdo tripleO liberty undercloud install failing https://ask.openstack.org/en/question/94023/rdo-tripleo-liberty-undercloud-install-failing/ Tags: rdo, rdo-manager, liberty, undercloud, instack Liberty RDO: stack resource topology icons are pink https://ask.openstack.org/en/question/91347/liberty-rdo-stack-resource-topology-icons-are-pink/ Tags: resource, topology, dashboard, horizon, pink No handlers could be found for logger "oslo_config.cfg" while syncing the glance database https://ask.openstack.org/en/question/91169/no-handlers-could-be-found-for-logger-oslo_configcfg-while-syncing-the-glance-database/ Tags: liberty, glance, install-openstack CentOS OpenStack - compute node can't talk https://ask.openstack.org/en/question/88989/centos-openstack-compute-node-cant-talk/ Tags: rdo How to setup SWIFT_PROXY_NODE and SWIFT_STORAGE_NODEs separately on RDO Liberty ? https://ask.openstack.org/en/question/88897/how-to-setup-swift_proxy_node-and-swift_storage_nodes-separately-on-rdo-liberty/ Tags: rdo, liberty, swift, ha VM and container can't download anything from internet https://ask.openstack.org/en/question/88338/vm-and-container-cant-download-anything-from-internet/ Tags: rdo, neutron, network, connectivity Fedora22, Liberty, horizon VNC console and keymap=sv with ; and/ https://ask.openstack.org/en/question/87451/fedora22-liberty-horizon-vnc-console-and-keymapsv-with-and/ Tags: keyboard, map, keymap, vncproxy, novnc OpenStack-Docker driver failed https://ask.openstack.org/en/question/87243/openstack-docker-driver-failed/ Tags: docker, openstack, liberty Routing between two tenants https://ask.openstack.org/en/question/84645/routing-between-two-tenants/ Tags: kilo, fuel, rdo, routing openstack baremetal introspection internal server error https://ask.openstack.org/en/question/82790/openstack-baremetal-introspection-internal-server-error/ Tags: rdo, ironic-inspector, tripleo Installing openstack using packstack (rdo) failed https://ask.openstack.org/en/question/82473/installing-openstack-using-packstack-rdo-failed/ Tags: rdo, packstack, installation-error, keystone VMware Host Backend causes No valid host was found. Bug ??? https://ask.openstack.org/en/question/79738/vmware-host-backend-causes-no-valid-host-was-found-bug/ Tags: vmware, rdo Mutlinode Devstack with two interfaces https://ask.openstack.org/en/question/78615/mutlinode-devstack-with-two-interfaces/ Tags: devstack, vlan, openstack Overcloud deployment on VM fails as IP address from DHCP is not assigned https://ask.openstack.org/en/question/66272/overcloud-deployment-on-vm-fails-as-ip-address-from-dhcp-is-not-assigned/ Tags: overcloud_in_vm -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From rbowen at redhat.com Tue Sep 27 19:09:58 2016 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 27 Sep 2016 15:09:58 -0400 Subject: [rdo-list] Reminder: test day this week (Sept 29, 30) Message-ID: <5d4bb0a3-83c4-222b-a745-824fef6d4d19@redhat.com> Reminder: This Thursday and Friday we will be testing the Newton RC - https://www.rdoproject.org/testday/newton/rc/ Please try to find a few hours on Thursday and/or Friday to drop by #rdo on the Freenode IRC network, and give RDO a spin, to help make this the best version of RDO OpenStack yet. --Rich -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity From rbowen at redhat.com Tue Sep 27 19:56:55 2016 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 27 Sep 2016 15:56:55 -0400 Subject: [rdo-list] Recent RDO blog posts Message-ID: <9cf713e3-ea55-af6b-f6e4-763dd50a9448@redhat.com> Here's what RDO enthusiasts have been blogging about: *LinuxCon talk slides: ?A Practical Look at QEMU?s Block Layer Primitives?* by Kashyap Chamarthy Last week I spent time at LinuxCon (and the co-located KVM Forum) Toronto. I presented a talk on QEMU?s block layer primitives. Specifically, the QMP primitives block-commit, drive-mirror, drive-backup, and QEMU?s built-in NBD (Network Block Device) server. ? read more at http://tm3.org/9x *Complex data transformations with nested Heat intrinsic functions* by Steve Hardy Disclaimer, what follows is either pretty neat, or pure-evil depending your your viewpoint ;) But it's based on a real use-case and it works, so I'm posting this to document the approach, why it's needed, and hopefully stimulate some discussion around optimizations leading to a improved/simplified implementation in the future. ? read more at http://tm3.org/9y *Red Hat OpenStack Platform 9 is here! So what?s new?* by Marcos Garcia This week we released the latest version of our OpenStack product, Red Hat OpenStack Platform 9. This release contains more than 500 downstream enhancements, bug fixes, documentation changes, and security updates. It?s based on the upstream OpenStack Mitaka release. We have worked hard to reduce the time to release new versions and have successfully done so with this release! Red Hat OpenStack Platform 9 contains new Mitaka features and functionality, as well as the additional hardening, stability, and certifications Red Hat is known for. Of course, there continues to be tight integration with other key portfolio products, as well as comprehensive documentation. ? read more at http://tm3.org/9z *Deploying Server on Ironic Node Baseline* by Adam Young My team is working on the ability to automatically enroll servers launched from Nova in FreeIPA. Debugging the process has proven challenging; when things fail, the node does not come up, and there is little error reporting. This article posts a baseline of what things look like prior to any changes, so we can better see what we are breaking. ? read more at http://tm3.org/9- *A retrospective of the OpenStack Telemetry project Newton cycle* by Julien Danjou A few weeks ago, I recorded an interview with Krishnan Raghuram about what was discussed for this development cycle for OpenStack Telemetry at the Austin summit. ? read more at http://tm3.org/a0 *Deploying Fernet on the Overcloud* by Adam Young Here is a proof of concept of deploying an OpenStack Tripleo Overcloud using the Fernet token Provider. ? read more at http://tm3.org/a1 *OpenStack Infra: Understanding Zuul* by Arie Bregman Recently I had the time to explore Zuul. I decided to gather everything I learned here in this post. Perhaps you?ll find it useful for your understanding of Zuul. ? read more at http://tm3.org/a2 *OpenStack Infra: How to deploy Zuul* by Arie Bregman This is the second post on Zuul, which focuses on deploying it and its services. To learn what is Zuul and how it works, I recommend to read the previous post. ? read more at http://tm3.org/a3 *Scaling-up TripleO CI coverage with scenarios* by Emilien Macchi When the project OpenStack started, it was ?just? a set of services with the goal to spawn a VM. I remember you run everything on your laptop and test things really quickly. The project has now grown, and thousands of features have been implemented, more backends / drivers are supported and new projects joined the party. It makes testing very challenging because everything can?t be tested in CI environment. ? read more at http://tm3.org/a4 *Introducing patches to RDO CloudSIG packages* by Jakub Ruzicka RDO infrastructure and tooling has been changing/improving with each OpenStack release and we now have our own packaging workflow powered by RPM factory at review.rdoproject.org, designed to keep up with supersonic speed of upstream development. ? read more at http://tm3.org/a5 *From decimal to timestamp with MySQL* by Julien Danjou When working with timestamps, one question that often arises is the precision of those timestamps. Most software is good enough with a precision up to the second, and that's easy. But in some cases, like working on metering, a finer precision is required. ? read more at http://tm3.org/a6 *Generating Token Request JSON from Environment Variables* by Adam Young When working with New APIS we need to test them with curl prior to writing the python client. I?ve often had to hand create the JSON used for the token request, as I wrote about way back here. Here is a simple bash script to convert the V3 environment variables into the JSON for a token request. ? read more at http://tm3.org/a7 *Actionable CI* by Assaf Muller I?ve observed a persistent theme across valuable and successful CI systems, and that is actionable results. A CI system for a project as complicated as OpenStack requires a staggering amount of energy to maintain and improve. Often times the responsible parties are focused on keeping it green and are buried under a mountain of continuous failures, legit or otherwise. So much so that they don?t have time to focus on the following questions: ? read more at http://tm3.org/a8 *Thoughts on Red Hat OpenStack Platform and certification of Tesora Database as a Service Platform* by Ken Rugg, Chief Executive Officer, Tesora When I think about open source software, Red Hat is first name that comes to mind. At Tesora, we?ve been working to make our Database as a Service Platform available to Red Hat OpenStack Platform users, and now it is a Red Hat certified solution. Officially collaborating with Red Hat in the context of OpenStack, one of the fastest growing open source projects ever, is a tremendous opportunity. ? read more at http://tm3.org/a9 -- Rich Bowen - rbowen at redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorenzetto.luca at gmail.com Tue Sep 27 20:33:34 2016 From: lorenzetto.luca at gmail.com (Luca 'remix_tj' Lorenzetto) Date: Tue, 27 Sep 2016 22:33:34 +0200 Subject: [rdo-list] Adding drivers to overcloud-full In-Reply-To: References: Message-ID: Hello, We are deploying rdo with tripleo on some hp blades using custom built images based on rhel 7. Since we encountered some issues (one of them is a kernel bug confirmed by red hat), we are planning to add hp suggested drivers (be2net and hpsa in our case) to our overcloud-full, which are newer than the redhat provided ones. Is this a common practice? Which is the best way to do it? Should I install rpm with virt-customize or add a dib module? Thank you very much for suggestions Luca -------------- next part -------------- An HTML attachment was scrubbed... URL: From hguemar at fedoraproject.org Tue Sep 27 20:38:40 2016 From: hguemar at fedoraproject.org (=?UTF-8?Q?Ha=C3=AFkel?=) Date: Tue, 27 Sep 2016 22:38:40 +0200 Subject: [rdo-list] RabbitMQ version in RDO In-Reply-To: References: Message-ID: 2016-09-27 17:22 GMT+02:00 Mohammed Naser : > On Tue, Sep 20, 2016 at 12:55 PM, Ha?kel wrote: >> 2016-09-20 17:50 GMT+02:00 Mohammed Naser : >>> Hi Alan: >>> >>> Thanks for pointing me to the RabbitMQ packages, we're going to test >>> those internally and report if we run into the issue again. >>> >>> I do agree with what David has pointed out in that there should be a >>> process setup in order to make sure that the shipped packages that >>> come with RDO (at least the supporting ones such as MariaDB/Galera, >>> etc) should be good-to-go. I imagine this might make things a bit >>> more difficult in terms of testing them, so I'm not sure what would be >>> the best path to take in this case. >>> >>> Thanks >>> Mohammed >>> >> >> These are already tested in our CI + upstream CI. >> And get immediate feedback when pushing broken versions of these >> components in -testing (AFAIK, -release is safe) >> > > Hi everyone: > > We've been running this for a few days now with no reported issues. > We don't seem to be running into that issue anymore that was crashing > nodes. > > Would it be possible to look into promoting this packages so that > other RDO users are not affected this issue? > > Thanks! > Mohammed > If you mean the following build: rabbitmq-server-3.6.5-1.el7 , it's coming, I'm looking to upgrade erlang at the same time. Regards, H. >>> On Tue, Sep 20, 2016 at 11:05 AM, Alan Pevec wrote: >>>> On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard wrote: >>>>> I think with OpenStack components it's easier, there's branches and we >>>>> build/test them throughout the lifecycle. >>>>> Once we have the proper testing in place, we can update those more frequently. >>>> >>>> Ideally same would apply for dependencies like rabbitmq, mariadb, we'd >>>> update frequently and release after testing but also vetted by package >>>> maintainers. >>>> Let's start by this last part: I'll check that components in RDO >>>> bugzilla have correct default owner then we setup nagging like >>>> https://fedoraproject.org/wiki/Upstream_release_monitoring for few >>>> critical dependencies. >>>> >>>> Alan >>>> >>>> _______________________________________________ >>>> rdo-list mailing list >>>> rdo-list at redhat.com >>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>> >>>> To unsubscribe: rdo-list-unsubscribe at redhat.com >>> >>> _______________________________________________ >>> rdo-list mailing list >>> rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >>> To unsubscribe: rdo-list-unsubscribe at redhat.com From mnaser at vexxhost.com Tue Sep 27 22:16:05 2016 From: mnaser at vexxhost.com (Mohammed Naser) Date: Tue, 27 Sep 2016 18:16:05 -0400 Subject: [rdo-list] RabbitMQ version in RDO In-Reply-To: References: Message-ID: Hi Haikel, Please let me know if you need any testing of those packages at our side as well. Thanks, Mohammed On Tue, Sep 27, 2016 at 4:38 PM, Ha?kel wrote: > 2016-09-27 17:22 GMT+02:00 Mohammed Naser : >> On Tue, Sep 20, 2016 at 12:55 PM, Ha?kel wrote: >>> 2016-09-20 17:50 GMT+02:00 Mohammed Naser : >>>> Hi Alan: >>>> >>>> Thanks for pointing me to the RabbitMQ packages, we're going to test >>>> those internally and report if we run into the issue again. >>>> >>>> I do agree with what David has pointed out in that there should be a >>>> process setup in order to make sure that the shipped packages that >>>> come with RDO (at least the supporting ones such as MariaDB/Galera, >>>> etc) should be good-to-go. I imagine this might make things a bit >>>> more difficult in terms of testing them, so I'm not sure what would be >>>> the best path to take in this case. >>>> >>>> Thanks >>>> Mohammed >>>> >>> >>> These are already tested in our CI + upstream CI. >>> And get immediate feedback when pushing broken versions of these >>> components in -testing (AFAIK, -release is safe) >>> >> >> Hi everyone: >> >> We've been running this for a few days now with no reported issues. >> We don't seem to be running into that issue anymore that was crashing >> nodes. >> >> Would it be possible to look into promoting this packages so that >> other RDO users are not affected this issue? >> >> Thanks! >> Mohammed >> > > If you mean the following build: rabbitmq-server-3.6.5-1.el7 , it's > coming, I'm looking to upgrade erlang at the same time. > > Regards, > H. > > > >>>> On Tue, Sep 20, 2016 at 11:05 AM, Alan Pevec wrote: >>>>> On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard wrote: >>>>>> I think with OpenStack components it's easier, there's branches and we >>>>>> build/test them throughout the lifecycle. >>>>>> Once we have the proper testing in place, we can update those more frequently. >>>>> >>>>> Ideally same would apply for dependencies like rabbitmq, mariadb, we'd >>>>> update frequently and release after testing but also vetted by package >>>>> maintainers. >>>>> Let's start by this last part: I'll check that components in RDO >>>>> bugzilla have correct default owner then we setup nagging like >>>>> https://fedoraproject.org/wiki/Upstream_release_monitoring for few >>>>> critical dependencies. >>>>> >>>>> Alan >>>>> >>>>> _______________________________________________ >>>>> rdo-list mailing list >>>>> rdo-list at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>>> >>>>> To unsubscribe: rdo-list-unsubscribe at redhat.com >>>> >>>> _______________________________________________ >>>> rdo-list mailing list >>>> rdo-list at redhat.com >>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>> >>>> To unsubscribe: rdo-list-unsubscribe at redhat.com From bderzhavets at hotmail.com Wed Sep 28 06:40:49 2016 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Wed, 28 Sep 2016 06:40:49 +0000 Subject: [rdo-list] Adding drivers to overcloud-full In-Reply-To: References: , Message-ID: Check with http://jaormx.github.io//2016/adding-packages-to-overcloud-images/ same at http://tripleo.org/planet.html September 20, 2016 Juan Antonio Osorio Adding packages to overcloud images Boris. ________________________________ From: rdo-list-bounces at redhat.com on behalf of Luca 'remix_tj' Lorenzetto Sent: Tuesday, September 27, 2016 11:33:34 PM To: rdo-list Subject: [rdo-list] Adding drivers to overcloud-full Hello, We are deploying rdo with tripleo on some hp blades using custom built images based on rhel 7. Since we encountered some issues (one of them is a kernel bug confirmed by red hat), we are planning to add hp suggested drivers (be2net and hpsa in our case) to our overcloud-full, which are newer than the redhat provided ones. Is this a common practice? Which is the best way to do it? Should I install rpm with virt-customize or add a dib module? Thank you very much for suggestions Luca -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorenzetto.luca at gmail.com Wed Sep 28 07:09:47 2016 From: lorenzetto.luca at gmail.com (Luca 'remix_tj' Lorenzetto) Date: Wed, 28 Sep 2016 09:09:47 +0200 Subject: [rdo-list] Adding drivers to overcloud-full In-Reply-To: References: Message-ID: On Wed, Sep 28, 2016 at 8:40 AM, Boris Derzhavets wrote: > Check with > > http://jaormx.github.io//2016/adding-packages-to-overcloud-images/ [cut] That's exactly what we're already doing. I'd like to have better integration with build system without the need of manual intervention after the image create command. Thank you anyway for the link, Luca -- "E' assurdo impiegare gli uomini di intelligenza eccellente per fare calcoli che potrebbero essere affidati a chiunque se si usassero delle macchine" Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) "Internet ? la pi? grande biblioteca del mondo. Ma il problema ? che i libri sono tutti sparsi sul pavimento" John Allen Paulos, Matematico (1945-vivente) Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , From lorenzetto.luca at gmail.com Wed Sep 28 07:14:51 2016 From: lorenzetto.luca at gmail.com (Luca 'remix_tj' Lorenzetto) Date: Wed, 28 Sep 2016 09:14:51 +0200 Subject: [rdo-list] Reminder: test day this week (Sept 29, 30) In-Reply-To: <7cd7d16e-39ef-5a5c-49cc-47505ee6f6ad@redhat.com> References: <5d4bb0a3-83c4-222b-a745-824fef6d4d19@redhat.com> <7cd7d16e-39ef-5a5c-49cc-47505ee6f6ad@redhat.com> Message-ID: On Tue, Sep 27, 2016 at 10:29 PM, Rich Bowen wrote: > On 09/27/2016 04:21 PM, Luca 'remix_tj' Lorenzetto wrote: >> >> Hi, >> >> This could be interesting for our team. Is there any existing test plan? >> We have a cluster were we are now experimenting mitaka tripleo >> deployment and is redeployed daily (more or less) for testing. >> >> We could also test building images based on rhel 7 and testing. > > > There's a test plan, of sorts, at the URL above - > https://www.rdoproject.org/testday/newton/testedsetups_rc/ - However, we > really need help making that test plan both more comprehensive, and more > accessible - that is, make it so that beginners can come help test, as > well as experts. The link reported for the howto is returning 404 (https://www.rdoproject.org/testday/newton/milestone_rc#how-to-test) Which is the right one? > > We would love to hear from you on rdo-list about scenarios that you'd > like to see tested, as well as scenarios you are already testing. We're mainly working on deployment with TripleO. Could be interesting for tests? I see only packstack related tests... Luca -- "E' assurdo impiegare gli uomini di intelligenza eccellente per fare calcoli che potrebbero essere affidati a chiunque se si usassero delle macchine" Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) "Internet ? la pi? grande biblioteca del mondo. Ma il problema ? che i libri sono tutti sparsi sul pavimento" John Allen Paulos, Matematico (1945-vivente) Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , From smonderer at vasonanetworks.com Wed Sep 28 10:35:07 2016 From: smonderer at vasonanetworks.com (Samuel Monderer) Date: Wed, 28 Sep 2016 13:35:07 +0300 Subject: [rdo-list] [TripleO] Accessing undcloud dashboard from external network Message-ID: Hi, I've installed the undercloud with the configuration below but are unable to access the dashboard from the external network. Is there an additional configuration needed?? Samuel undercloud_hostname = edge-rhos-director.vasonanetworks.com local_ip = 192.0.2.1/24 network_gateway = 192.0.2.1 undercloud_public_vip = 192.0.2.2 undercloud_admin_vip = 192.0.2.3 local_interface = eth0 network_cidr = 192.0.2.0/24 undercloud_hostname = edge-rhos-director.vasonanetworks.com local_ip = 192.0.2.1/24 network_gateway = 192.0.2.1 undercloud_public_vip = 192.0.2.2 undercloud_admin_vip = 192.0.2.3 local_interface = eth0 network_cidr = 192.0.2.0/24 ipxe_deploy = true enable_monitoring = false store_events = false scheduler_max_attempts = 30 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at hotmail.com Wed Sep 28 11:20:34 2016 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Wed, 28 Sep 2016 11:20:34 +0000 Subject: [rdo-list] [TripleO] Accessing undcloud dashboard from external network In-Reply-To: References: Message-ID: As far as I know conversion ctlplane to rout-able network is scheduled Ocata M2. For now just sshutle ( of-course it doesn't provide external available FIPS, just VPN via existing ssh connection to undercloud ) Details here :- https://www.linux.com/blog/access-tripleo-quickstart-overcloud-sshuttle-running-f24-workstation Access to TripleO QuickStart overcloud via sshuttle ... www.linux.com Sshuttle may be installed on Fedora 24 via straight forward `dnf -y install sshutle` [1]. So, when F24 has been set up as WKS for TripleO QuickStart deployment to ... ________________________________ From: rdo-list-bounces at redhat.com on behalf of Samuel Monderer Sent: Wednesday, September 28, 2016 1:35 PM To: rdo-list at redhat.com Subject: [rdo-list] [TripleO] Accessing undcloud dashboard from external network Hi, I've installed the undercloud with the configuration below but are unable to access the dashboard from the external network. Is there an additional configuration needed?? Samuel undercloud_hostname = edge-rhos-director.vasonanetworks.com local_ip = 192.0.2.1/24 network_gateway = 192.0.2.1 undercloud_public_vip = 192.0.2.2 undercloud_admin_vip = 192.0.2.3 local_interface = eth0 network_cidr = 192.0.2.0/24 undercloud_hostname = edge-rhos-director.vasonanetworks.com Vasona Networks edge-rhos-director.vasonanetworks.com An innovative team of experienced leaders, building a company with the vision of improving mobile networking. Backed by world class financial partners. Vasona Networks is committed to developing solutions that bring the greatest value to our customers, the mobile carriers. local_ip = 192.0.2.1/24 network_gateway = 192.0.2.1 undercloud_public_vip = 192.0.2.2 undercloud_admin_vip = 192.0.2.3 local_interface = eth0 network_cidr = 192.0.2.0/24 ipxe_deploy = true enable_monitoring = false store_events = false scheduler_max_attempts = 30 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dba477 at list.ru Wed Sep 28 11:34:14 2016 From: dba477 at list.ru (=?UTF-8?B?Qm9yaXM=?=) Date: Wed, 28 Sep 2016 14:34:14 +0300 Subject: [rdo-list] =?utf-8?q?=5BTripleO=5D_Accessing_undcloud_dashboard_f?= =?utf-8?q?rom_external=09network?= In-Reply-To: References: Message-ID: <1475062454.926851091@f385.i.mail.ru> Sorry, I meant? overcloud dashboard access , not undercloud. The last one is disabled by default Using backup e-mail due to local issues with access to hotmail.com Boris. >?????, 28 ???????? 2016, 14:20 +03:00 ?? Boris Derzhavets : > >As far as I know conversion ctlplane to rout-able network is scheduled Ocata M2. >For now just sshutle ( of-course it doesn't provide external available FIPS, just >VPN via existing ssh connection to undercloud ) >Details here :- > >https://www.linux.com/blog/access-tripleo-quickstart-overcloud-sshuttle-running-f24-workstation >Access to TripleO QuickStart overcloud via sshuttle ... >www.linux.com >Sshuttle may be installed on Fedora 24 via straight forward `dnf -y install sshutle` [1]. So, when F24 has been set up as WKS for TripleO QuickStart deployment to ... > >---------------------------------------------------------------------- >From: rdo-list-bounces at redhat.com < rdo-list-bounces at redhat.com > on behalf of Samuel Monderer < smonderer at vasonanetworks.com > >Sent: Wednesday, September 28, 2016 1:35 PM >To: rdo-list at redhat.com >Subject: [rdo-list] [TripleO] Accessing undcloud dashboard from external network >? >Hi, > >I've installed the undercloud with the configuration below but are unable to access the dashboard from the external network. >Is there an additional configuration needed?? > >Samuel > >undercloud_hostname = edge-rhos-director.vasonanetworks.com > >local_ip = 192.0.2.1/24 > >network_gateway = 192.0.2.1 > >undercloud_public_vip = 192.0.2.2 > >undercloud_admin_vip = 192.0.2.3 > >local_interface = eth0 > >network_cidr = 192.0.2.0/24 > >undercloud_hostname = edge-rhos-director.vasonanetworks.com >Vasona Networks >edge-rhos-director.vasonanetworks.com >An innovative team of experienced leaders, building a company with the vision of improving mobile networking. Backed by world class financial partners. Vasona Networks is committed to developing solutions that bring the greatest value to our customers, the mobile carriers. > >local_ip = 192.0.2.1/24 > >network_gateway = 192.0.2.1 > >undercloud_public_vip = 192.0.2.2 > >undercloud_admin_vip = 192.0.2.3 > >local_interface = eth0 > >network_cidr = 192.0.2.0/24 > >ipxe_deploy = true > >enable_monitoring = false > >store_events = false > >scheduler_max_attempts = 30 > >_______________________________________________ >rdo-list mailing list >rdo-list at redhat.com >https://www.redhat.com/mailman/listinfo/rdo-list > >To unsubscribe: rdo-list-unsubscribe at redhat.com ? ?????????, Boris Derzhavets dba477 at list.ru -------------- next part -------------- An HTML attachment was scrubbed... URL: From smonderer at vasonanetworks.com Wed Sep 28 11:36:26 2016 From: smonderer at vasonanetworks.com (Samuel Monderer) Date: Wed, 28 Sep 2016 14:36:26 +0300 Subject: [rdo-list] [TripleO] Accessing undcloud dashboard from external network In-Reply-To: <1475062454.926851091@f385.i.mail.ru> References: <1475062454.926851091@f385.i.mail.ru> Message-ID: How do I enable the undercloud dashboard?? On Wed, Sep 28, 2016 at 2:34 PM, Boris wrote: > Sorry, I meant overcloud dashboard access , not undercloud. The last one > is disabled by default > Using backup e-mail due to local issues with access to hotmail.com > > Boris. > > > ?????, 28 ???????? 2016, 14:20 +03:00 ?? Boris Derzhavets < > bderzhavets at hotmail.com>: > > As far as I know conversion ctlplane to rout-able network is scheduled > Ocata M2. > > For now just sshutle ( of-course it doesn't provide external available > FIPS, just > > VPN via existing ssh connection to undercloud ) > > Details here :- > > > https://www.linux.com/blog/access-tripleo-quickstart- > overcloud-sshuttle-running-f24-workstation > Access to TripleO QuickStart overcloud via sshuttle ... > > www.linux.com > Sshuttle may be installed on Fedora 24 via straight forward `dnf -y > install sshutle` [1]. So, when F24 has been set up as WKS for TripleO > QuickStart deployment to ... > > > ------------------------------ > *From:* rdo-list-bounces at redhat.com on > behalf of Samuel Monderer > *Sent:* Wednesday, September 28, 2016 1:35 PM > *To:* rdo-list at redhat.com > *Subject:* [rdo-list] [TripleO] Accessing undcloud dashboard from > external network > > Hi, > > I've installed the undercloud with the configuration below but are unable > to access the dashboard from the external network. > Is there an additional configuration needed?? > > Samuel > > undercloud_hostname = edge-rhos-director.vasonanetworks.com > > local_ip = 192.0.2.1/24 > > network_gateway = 192.0.2.1 > > undercloud_public_vip = 192.0.2.2 > > undercloud_admin_vip = 192.0.2.3 > > local_interface = eth0 > > network_cidr = 192.0.2.0/24 > > undercloud_hostname = edge-rhos-director.vasonanetworks.com > Vasona Networks > edge-rhos-director.vasonanetworks.com > An innovative team of experienced leaders, building a company with the > vision of improving mobile networking. Backed by world class financial > partners. Vasona Networks is committed to developing solutions that bring > the greatest value to our customers, the mobile carriers. > > local_ip = 192.0.2.1/24 > > network_gateway = 192.0.2.1 > > undercloud_public_vip = 192.0.2.2 > > undercloud_admin_vip = 192.0.2.3 > > local_interface = eth0 > > network_cidr = 192.0.2.0/24 > > ipxe_deploy = true > > enable_monitoring = false > > store_events = false > > scheduler_max_attempts = 30 > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com > > > > ? ?????????, > Boris Derzhavets > dba477 at list.ru > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at hotmail.com Wed Sep 28 11:46:15 2016 From: bderzhavets at hotmail.com (Boris Derzhavets) Date: Wed, 28 Sep 2016 11:46:15 +0000 Subject: [rdo-list] [TripleO] Accessing undcloud dashboard from external network In-Reply-To: References: <1475062454.926851091@f385.i.mail.ru>, Message-ID: I never do that just `source stackrc` and use nova/neutron/openstack/ CLI You will see overcloud nodes :- [stack at instack ~]$ nova list +--------------------------------------+-------------------------+--------+------------+-------------+---------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+-------------------------+--------+------------+-------------+---------------------+ | e67b7987-11ae-49aa-8ed2-1de2ef96d825 | overcloud-controller-0 | ACTIVE | - | Running | ctlplane=192.0.2.9 | | e4010150-5201-4b98-8736-b301db777198 | overcloud-novacompute-0 | ACTIVE | - | Running | ctlplane=192.0.2.18 | | c5c7a265-882b-4edd-8ad8-d61637b6e3af | overcloud-novacompute-1 | ACTIVE | - | Running | ctlplane=192.0.2.12 | +--------------------------------------+-------------------------+--------+------------+-------------+---------------------+ $ ssh heat-admin at 192.0.2.9 (18,12) will log you in overcloud nodes. ________________________________ From: Samuel Monderer Sent: Wednesday, September 28, 2016 2:36 PM To: Boris Cc: Boris Derzhavets; rdo-list at redhat.com Subject: Re: Re[2]: [rdo-list] [TripleO] Accessing undcloud dashboard from external network How do I enable the undercloud dashboard?? On Wed, Sep 28, 2016 at 2:34 PM, Boris > wrote: Sorry, I meant overcloud dashboard access , not undercloud. The last one is disabled by default Using backup e-mail due to local issues with access to hotmail.com Boris. ?????, 28 ???????? 2016, 14:20 +03:00 ?? Boris Derzhavets >: As far as I know conversion ctlplane to rout-able network is scheduled Ocata M2. For now just sshutle ( of-course it doesn't provide external available FIPS, just VPN via existing ssh connection to undercloud ) Details here :- https://www.linux.com/blog/access-tripleo-quickstart-overcloud-sshuttle-running-f24-workstation Access to TripleO QuickStart overcloud via sshuttle ... www.linux.com Sshuttle may be installed on Fedora 24 via straight forward `dnf -y install sshutle` [1]. So, when F24 has been set up as WKS for TripleO QuickStart deployment to ... ________________________________ From: rdo-list-bounces at redhat.com > on behalf of Samuel Monderer > Sent: Wednesday, September 28, 2016 1:35 PM To: rdo-list at redhat.com Subject: [rdo-list] [TripleO] Accessing undcloud dashboard from external network Hi, I've installed the undercloud with the configuration below but are unable to access the dashboard from the external network. Is there an additional configuration needed?? Samuel undercloud_hostname = edge-rhos-director.vasonanetworks.com local_ip = 192.0.2.1/24 network_gateway = 192.0.2.1 undercloud_public_vip = 192.0.2.2 undercloud_admin_vip = 192.0.2.3 local_interface = eth0 network_cidr = 192.0.2.0/24 undercloud_hostname = edge-rhos-director.vasonanetworks.com Vasona Networks edge-rhos-director.vasonanetworks.com An innovative team of experienced leaders, building a company with the vision of improving mobile networking. Backed by world class financial partners. Vasona Networks is committed to developing solutions that bring the greatest value to our customers, the mobile carriers. local_ip = 192.0.2.1/24 network_gateway = 192.0.2.1 undercloud_public_vip = 192.0.2.2 undercloud_admin_vip = 192.0.2.3 local_interface = eth0 network_cidr = 192.0.2.0/24 ipxe_deploy = true enable_monitoring = false store_events = false scheduler_max_attempts = 30 _______________________________________________ rdo-list mailing list rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscribe at redhat.com ? ?????????, Boris Derzhavets dba477 at list.ru -------------- next part -------------- An HTML attachment was scrubbed... URL: From amoralej at redhat.com Wed Sep 28 18:25:38 2016 From: amoralej at redhat.com (Alfredo Moralejo Alonso) Date: Wed, 28 Sep 2016 20:25:38 +0200 Subject: [rdo-list] [Meeting] RDO meeting (2016-09-28) Message-ID: ============================== #rdo: RDO meeting - 2016-09-28 ============================== Meeting started by amoralej at 15:02:13 UTC. The full logs are available at https://meetbot.fedoraproject.org/rdo/2016-09-28/rdo_meeting_-_2016-09-28.2016-09-28-15.02.log.html . Meeting summary --------------- * DLRN Ocata branch preparation (amoralej, 15:04:04) * ocata will be open and u-c pins will be maintained in newton tag until newton GA (amoralej, 15:14:43) * ACTION: number80 will check with centos team about why openstack-ocata doesn't exist yet in buildlogs (amoralej, 15:19:45) * Announcements (amoralej, 15:19:56) * Test day, tomorrow and Friday - https://www.rdoproject.org/testday/newton/rc/ (amoralej, 15:20:15) * LINK: https://raw.githubusercontent.com/redhat-openstack/tempest/master/tools/install_test_packages.py (chandankumar, 15:22:43) * Important dates (amoralej, 15:26:50) * CentOS outage October 10th: https://lists.centos.org/pipermail/ci-users/2016-September/000392.html (amoralej, 15:27:22) * rcip-dev (review.rdoproject.org) outage >= October 15th (not announced yet) (amoralej, 15:27:58) * review.rdoproject.org maintenance 2016-10-10 13:00 UTC: https://www.redhat.com/archives/rdo-list/2016-September/msg00095.html (amoralej, 15:28:15) * Newton release: October 6th: https://releases.openstack.org/newton/index.html (amoralej, 15:28:29) * LINK: https://etherpad.openstack.org/p/rdo-barcelona-meetup-schedule (rbowen, 15:29:03) * open floor (amoralej, 15:34:08) Meeting ended at 15:43:33 UTC. Action Items ------------ * number80 will check with centos team about why openstack-ocata doesn't exist yet in buildlogs Action Items, by person ----------------------- * number80 * number80 will check with centos team about why openstack-ocata doesn't exist yet in buildlogs * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * amoralej (60) * jpena (17) * rbowen (12) * dmsimard (11) * chandankumar (11) * zodbot (9) * number80 (8) * EmilienM (5) * bandini (3) * trown (2) * panda (2) * myoung (1) * Duck (1) * jschlueter (1) * imcsk8 (1) * gchamoul (1) * rdogerrit (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From ckdwibedy at gmail.com Thu Sep 29 11:57:27 2016 From: ckdwibedy at gmail.com (Chinmaya Dwibedy) Date: Thu, 29 Sep 2016 17:27:27 +0530 Subject: [rdo-list] Nova scheduler tries to assign an already-in-use SRIOV QAT VF to a new instance (openstack-mitaka) Message-ID: Hi, Upon trying to create VM instance (Say A) with one QAT VF, it fails with the following error i.e., ?Requested operation is not valid: PCI device 0000:88:04.7 is in use by driver QEMU, domain instance-00000081?. Please note that, PCI device 0000:88:04.7 is already being assigned to another VM (Say B) . We have installed openstack-mitaka release on CentO7 system. It has two Intel QAT devices. There are 32 VF devices available per QAT Device/DH895xCC device Out of 64 VFs, only 8 VFs are allocated (to VM instances) and rest should be available. But the nova scheduler tries to assign an already-in-use SRIOV VF to a new instance and instance fails. It appears that the nova database is not tracking which VF's have already been taken. But if I shut down VM B instance, then other instance VM A boots up and vice-versa. Note that, both the VM instances cannot run simultaneously because of the aforesaid issue. We should always be able to create as many instances with the requested PCI devices as there are available VFs. Please feel free to let me know if additional information is needed. Can anyone please suggest why it tries to assign same PCI device which has been assigned already? Is there any way to resolve this issue? Thank you in advance for your support and help. [root at localhost ~(keystone_admin)]# lspci -d:435 83:00.0 Co-processor: Intel Corporation DH895XCC Series QAT 88:00.0 Co-processor: Intel Corporation DH895XCC Series QAT [root at localhost ~(keystone_admin)]# [root at localhost ~(keystone_admin)]# lspci -d:443 | grep "QAT Virtual Function" | wc -l 64 [root at localhost ~(keystone_admin)]# [root at localhost ~(keystone_admin)]# mysql -u root nova -e "SELECT hypervisor_hostname, address, instance_uuid, status FROM pci_devices JOIN compute_nodes oncompute_nodes.id=compute_node_id" | grep 0000:88:04.7 localhost 0000:88:04.7 e10a76f3-e58e-4071-a4dd-7a545e8000de allocated localhost 0000:88:04.7 c3dbac90-198d-4150-ba0f-a80b912d8021 allocated localhost 0000:88:04.7 c7f6adad-83f0-4881-b68f-6d154d565ce3 allocated localhost.nfv.benunets.com 0000:88:04.7 0c3c11a5-f9a4-4f0d-b120-40e4dde843d4 allocated [root at localhost ~(keystone_admin)]# [root at localhost ~(keystone_admin)]# grep -r e10a76f3-e58e-4071-a4dd-7a545e8000de /etc/libvirt/qemu /etc/libvirt/qemu/instance-00000081.xml: e10a76f3-e58e-4071-a4dd- 7a545e8000de /etc/libvirt/qemu/instance-00000081.xml: e10a76f3-e58e-4071-a4dd-7a545e8000de /etc/libvirt/qemu/instance-00000081.xml: /etc/libvirt/qemu/instance-00000081.xml: /etc/libvirt/qemu/instance-00000081.xml: [root at localhost ~(keystone_admin)]# [root at localhost ~(keystone_admin)]# grep -r 0c3c11a5-f9a4-4f0d-b120-40e4dde843d4 /etc/libvirt/qemu /etc/libvirt/qemu/instance-000000ab.xml: 0c3c11a5-f9a4-4f0d-b120- 40e4dde843d4 /etc/libvirt/qemu/instance-000000ab.xml: 0c3c11a5-f9a4-4f0d-b120-40e4dde843d4 /etc/libvirt/qemu/instance-000000ab.xml: /etc/libvirt/qemu/instance-000000ab.xml: /etc/libvirt/qemu/instance-000000ab.xml: [root at localhost ~(keystone_admin)]# On the controller, , it appears there are duplicate PCI device entries in the Database: MariaDB [nova]> select hypervisor_hostname,address,count(*) from pci_devices JOIN compute_nodes on compute_nodes.id=compute_node_id group by hypervisor_hostname,address having count(*) > 1; +---------------------+--------------+----------+ | hypervisor_hostname | address | count(*) | +---------------------+--------------+----------+ | localhost | 0000:05:00.0 | 3 | | localhost | 0000:05:00.1 | 3 | | localhost | 0000:83:01.0 | 3 | | localhost | 0000:83:01.1 | 3 | | localhost | 0000:83:01.2 | 3 | | localhost | 0000:83:01.3 | 3 | | localhost | 0000:83:01.4 | 3 | | localhost | 0000:83:01.5 | 3 | | localhost | 0000:83:01.6 | 3 | | localhost | 0000:83:01.7 | 3 | | localhost | 0000:83:02.0 | 3 | | localhost | 0000:83:02.1 | 3 | | localhost | 0000:83:02.2 | 3 | | localhost | 0000:83:02.3 | 3 | | localhost | 0000:83:02.4 | 3 | | localhost | 0000:83:02.5 | 3 | | localhost | 0000:83:02.6 | 3 | | localhost | 0000:83:02.7 | 3 | | localhost | 0000:83:03.0 | 3 | | localhost | 0000:83:03.1 | 3 | | localhost | 0000:83:03.2 | 3 | | localhost | 0000:83:03.3 | 3 | | localhost | 0000:83:03.4 | 3 | | localhost | 0000:83:03.5 | 3 | | localhost | 0000:83:03.6 | 3 | | localhost | 0000:83:03.7 | 3 | | localhost | 0000:83:04.0 | 3 | | localhost | 0000:83:04.1 | 3 | | localhost | 0000:83:04.2 | 3 | | localhost | 0000:83:04.3 | 3 | | localhost | 0000:83:04.4 | 3 | | localhost | 0000:83:04.5 | 3 | | localhost | 0000:83:04.6 | 3 | | localhost | 0000:83:04.7 | 3 | | localhost | 0000:88:01.0 | 3 | | localhost | 0000:88:01.1 | 3 | | localhost | 0000:88:01.2 | 3 | | localhost | 0000:88:01.3 | 3 | | localhost | 0000:88:01.4 | 3 | | localhost | 0000:88:01.5 | 3 | | localhost | 0000:88:01.6 | 3 | | localhost | 0000:88:01.7 | 3 | | localhost | 0000:88:02.0 | 3 | | localhost | 0000:88:02.1 | 3 | | localhost | 0000:88:02.2 | 3 | | localhost | 0000:88:02.3 | 3 | | localhost | 0000:88:02.4 | 3 | | localhost | 0000:88:02.5 | 3 | | localhost | 0000:88:02.6 | 3 | | localhost | 0000:88:02.7 | 3 | | localhost | 0000:88:03.0 | 3 | | localhost | 0000:88:03.1 | 3 | | localhost | 0000:88:03.2 | 3 | | localhost | 0000:88:03.3 | 3 | | localhost | 0000:88:03.4 | 3 | | localhost | 0000:88:03.5 | 3 | | localhost | 0000:88:03.6 | 3 | | localhost | 0000:88:03.7 | 3 | | localhost | 0000:88:04.0 | 3 | | localhost | 0000:88:04.1 | 3 | | localhost | 0000:88:04.2 | 3 | | localhost | 0000:88:04.3 | 3 | | localhost | 0000:88:04.4 | 3 | | localhost | 0000:88:04.5 | 3 | | localhost | 0000:88:04.6 | 3 | | localhost | 0000:88:04.7 | 3 | +---------------------+--------------+----------+ 66 rows in set (0.00 sec) MariaDB [nova]> Regards, Chinmaya -------------- next part -------------- An HTML attachment was scrubbed... URL: From smonderer at vasonanetworks.com Thu Sep 29 12:50:34 2016 From: smonderer at vasonanetworks.com (Samuel Monderer) Date: Thu, 29 Sep 2016 15:50:34 +0300 Subject: [rdo-list] [TripleO] undercloud dashboard installation Message-ID: Hi, Is undercloud dashboard installed together with the undercloud, i.e.: will the dashboard be installed after running "openstack undercloud install"??? If that is the case how can I access it from the external network? Regards, Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdmarks75080 at gmail.com Fri Sep 30 04:11:04 2016 From: jdmarks75080 at gmail.com (John Marks) Date: Thu, 29 Sep 2016 23:11:04 -0500 Subject: [rdo-list] [TripleO] TripleO behind a proxy with a pyPi mirrir Message-ID: I am having issues installing tripleo behind a proxy/mirror environment. I am using the USB key for the underclound install at it always breaks installing the "pbr" package into the virtual env. It simple will not pull the files from my mirror. Since I can't modify the USB key (read only) I can't pass parameters to "python setup.py" to use the mirror. I have tried defining pip.conf in the users home directory but it is not used. (By hand, pip will use it just fine). Any hints would be appreciated. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ecozzi at cray.com Fri Sep 30 22:02:07 2016 From: ecozzi at cray.com (Eric Cozzi) Date: Fri, 30 Sep 2016 22:02:07 +0000 Subject: [rdo-list] CentOS Build System Message-ID: I am interested in understanding what comprises your release build system, as described on https://www.rdoproject.org/documentation/rdo-packaging/. I understand that DLRN is used for per-commit builds. But, I cannot find any description of your ?CentOS Build System? which builds your release RPMs. Any information would be very helpful. Thanks, Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From apevec at redhat.com Fri Sep 30 22:31:34 2016 From: apevec at redhat.com (Alan Pevec) Date: Sat, 1 Oct 2016 00:31:34 +0200 Subject: [rdo-list] CentOS Build System In-Reply-To: References: Message-ID: > description of your ?CentOS Build System? which builds your release RPMs. > Any information would be very helpful. RDO participates in CentOS CloudSIG which provides CBS, an instance of Koji. For more details you can check [1] but CBS is now connected to review.rdoproject.org and will become transparent for contributors. Stable release RPM builds are being automated [2], part of that work was used to build Newton RC builds [3]. Cheers, Alan [1] https://wiki.centos.org/SIGGuide/CommunityBuildsystem [2] https://trello.com/c/URAtrhLU/86-automate-stable-packages-releases [3] https://review.rdoproject.org/r/#/q/topic:newton-rc2 From dms at redhat.com Fri Sep 30 22:33:29 2016 From: dms at redhat.com (David Moreau Simard) Date: Fri, 30 Sep 2016 18:33:29 -0400 Subject: [rdo-list] CentOS Build System In-Reply-To: References: Message-ID: In a nutshell, DLRN builds packages from git source on every commit. It scans project git repositories and when a new commit is detected, it builds a new package for the project. The CentOS Build System [1] is a Koji instance (same build software as Fedora). Builds on CBS are triggered through Koji and then tagged as appropriate to push to different repositories. For example, you can see a build of openstack-designate here [2]. The other main difference between DLRN and CBS is that builds that are done through CBS are from released/tagged upstream tarballs from tarballs.opentack.org. [1]: https://cbs.centos.org/koji/ [2]: https://cbs.centos.org/koji/buildinfo?buildID=12644 David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Fri, Sep 30, 2016 at 6:02 PM, Eric Cozzi wrote: > I am interested in understanding what comprises your release build system, > as described on https://www.rdoproject.org/documentation/rdo-packaging/. I > understand that DLRN is used for per-commit builds. But, I cannot find any > description of your ?CentOS Build System? which builds your release RPMs. > Any information would be very helpful. > > > > Thanks, > > Eric > > > _______________________________________________ > rdo-list mailing list > rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe at redhat.com