From apevec at gmail.com Wed Oct 1 07:57:53 2014 From: apevec at gmail.com (Alan Pevec) Date: Wed, 1 Oct 2014 09:57:53 +0200 Subject: [Rdo-list] python-sqlalchemy is removed in epel In-Reply-To: <1412099316.50059.YahooMailNeo@web192406.mail.sg3.yahoo.com> References: <316691786CCAEE44AE90482264E3AB8206BCF768@xmb-rcd-x08.cisco.com> <1412012174.39151.YahooMailNeo@web192405.mail.sg3.yahoo.com> <1412076070.72722.YahooMailNeo@web192403.mail.sg3.yahoo.com> <1412099316.50059.YahooMailNeo@web192406.mail.sg3.yahoo.com> Message-ID: > The latest python-sqlalchemy-0.9.7 has been pushed to epel7 testing repositories, and shall soon be available via -stable too. Thanks a bunch for resolving this! Cheers, Alan From yeylon at redhat.com Wed Oct 1 10:14:00 2014 From: yeylon at redhat.com (Yaniv Eylon) Date: Wed, 1 Oct 2014 06:14:00 -0400 (EDT) Subject: [Rdo-list] [rhos-qe-dept] RDO testing In-Reply-To: <272936956.39185936.1412153730373.JavaMail.zimbra@redhat.com> References: <1630711274.39132500.1412144719915.JavaMail.zimbra@redhat.com> <542BB8BC.4080702@redhat.com> <272936956.39185936.1412153730373.JavaMail.zimbra@redhat.com> Message-ID: <1863191962.15060345.1412158440010.JavaMail.zimbra@redhat.com> lets keep our communication during the test day on rdo-list@, specially if you come across workarounds. it looks like AIO deployment is broken Bug 1148346 - provision glance not able to work Bug 1148348 - packstack on CentOS 7 fails because python-anyjson requires Python 2.6 ----- Original Message ----- > From: "Udi Kalifon" > To: "rhos-qe-dept" > Sent: Wednesday, October 1, 2014 11:55:30 AM > Subject: Re: [rhos-qe-dept] RDO testing > > I failed to install on CentOS 7. I opened a bug on it: > https://bugzilla.redhat.com/show_bug.cgi?id=1148348 > > I ran packstack --allinone and got: > > 10.35.160.13_amqp.pp: [ DONE ] > 10.35.160.13_mysql.pp: [ DONE ] > Applying 10.35.160.13_keystone.pp > Applying 10.35.160.13_glance.pp > Applying 10.35.160.13_cinder.pp > 10.35.160.13_keystone.pp: [ ERROR ] > Applying Puppet manifests [ ERROR ] > > ERROR : Error appeared during Puppet run: 10.35.160.13_keystone.pp > Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list openstack-keystone' > returned 1: Traceback (most recent call last): > You will find full trace in log > /var/tmp/packstack/20141001-103703-gbTJFP/manifests/10.35.160.13_keystone.pp.log > Please check log file > /var/tmp/packstack/20141001-103703-gbTJFP/openstack-setup.log for more > information > > > In the keystone.pp.log file you see: > ^[[1;31mError: Execution of '/usr/bin/yum -d 0 -e 0 -y install > openstack-keystone' returned 1: Error: Package: > python-anyjson-0.3.3-1.el6.noarch (epel) > Requires: python(abi) = 2.6 > Installed: python-2.7.5-16.el7.x86_64 (@anaconda) > python(abi) = 2.7 > python(abi) = 2.7 > > ... and many more dependency errors > > > Regards, > Udi. > > ----- Original Message ----- > From: "Dafna Ron" > To: "Nathan Levinkind" , "rhos-qe-dept" > > Sent: Wednesday, October 1, 2014 11:18:04 AM > Subject: Re: [rhos-qe-dept] RDO testing > > RDO in Bugzilla: > > https://bugzilla.redhat.com/enter_bug.cgi?product=RDO > > RDO page: > > https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases > > > On 10/01/2014 07:25 AM, Nathan Levinkind wrote: > > Hi, > > bugs that you do find today please report on RDO project in Bugzila and > > also add to the RDO wiki page. > > IRC =rdo in freenode server > > Thanks > > Nathan > > > > > -- > Dafna Ron > > From Yaniv.Kaul at emc.com Wed Oct 1 10:18:10 2014 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Wed, 1 Oct 2014 06:18:10 -0400 Subject: [Rdo-list] RDO testing In-Reply-To: <1863191962.15060345.1412158440010.JavaMail.zimbra@redhat.com> References: <1630711274.39132500.1412144719915.JavaMail.zimbra@redhat.com> <542BB8BC.4080702@redhat.com> <272936956.39185936.1412153730373.JavaMail.zimbra@redhat.com> <1863191962.15060345.1412158440010.JavaMail.zimbra@redhat.com> Message-ID: <648473255763364B961A02AC3BE1060D03C5B118D4@MX19A.corp.emc.com> > -----Original Message----- > From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On > Behalf Of Yaniv Eylon > Sent: Wednesday, October 01, 2014 1:14 PM > To: rdo-list at redhat.com > Cc: rhos-qe-dept > Subject: Re: [Rdo-list] [rhos-qe-dept] RDO testing > > lets keep our communication during the test day on rdo-list@, specially if you > come across workarounds. > > it looks like AIO deployment is broken Worked yesterday for me (on CentOS 7): [root at lgdrm403 ~]# rpm -q python-anyjson python-anyjson-0.3.3-3.el7.noarch Y. > > Bug 1148346 - provision glance not able to work Bug 1148348 - packstack on > CentOS 7 fails because python-anyjson requires Python 2.6 > > ----- Original Message ----- > > From: "Udi Kalifon" > > To: "rhos-qe-dept" > > Sent: Wednesday, October 1, 2014 11:55:30 AM > > Subject: Re: [rhos-qe-dept] RDO testing > > > > I failed to install on CentOS 7. I opened a bug on it: > > https://bugzilla.redhat.com/show_bug.cgi?id=1148348 > > > > I ran packstack --allinone and got: > > > > 10.35.160.13_amqp.pp: [ DONE ] > > 10.35.160.13_mysql.pp: [ DONE ] > > Applying 10.35.160.13_keystone.pp > > Applying 10.35.160.13_glance.pp > > Applying 10.35.160.13_cinder.pp > > 10.35.160.13_keystone.pp: [ ERROR ] > > Applying Puppet manifests [ ERROR ] > > > > ERROR : Error appeared during Puppet run: 10.35.160.13_keystone.pp > > Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list openstack-keystone' > > returned 1: Traceback (most recent call last): > > You will find full trace in log > > /var/tmp/packstack/20141001-103703-gbTJFP/manifests/10.35.160.13_keyst > > one.pp.log > > Please check log file > > /var/tmp/packstack/20141001-103703-gbTJFP/openstack-setup.log for more > > information > > > > > > In the keystone.pp.log file you see: > > ^[[1;31mError: Execution of '/usr/bin/yum -d 0 -e 0 -y install > > openstack-keystone' returned 1: Error: Package: > > python-anyjson-0.3.3-1.el6.noarch (epel) > > Requires: python(abi) = 2.6 > > Installed: python-2.7.5-16.el7.x86_64 (@anaconda) > > python(abi) = 2.7 > > python(abi) = 2.7 > > > > ... and many more dependency errors > > > > > > Regards, > > Udi. > > > > ----- Original Message ----- > > From: "Dafna Ron" > > To: "Nathan Levinkind" , "rhos-qe-dept" > > > > Sent: Wednesday, October 1, 2014 11:18:04 AM > > Subject: Re: [rhos-qe-dept] RDO testing > > > > RDO in Bugzilla: > > > > https://bugzilla.redhat.com/enter_bug.cgi?product=RDO > > > > RDO page: > > > > https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases > > > > > > On 10/01/2014 07:25 AM, Nathan Levinkind wrote: > > > Hi, > > > bugs that you do find today please report on RDO project in Bugzila > > > and also add to the RDO wiki page. > > > IRC =rdo in freenode server > > > Thanks > > > Nathan > > > > > > > > > -- > > Dafna Ron > > > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list From tshefi at redhat.com Wed Oct 1 10:20:02 2014 From: tshefi at redhat.com (Tzach Shefi) Date: Wed, 1 Oct 2014 06:20:02 -0400 (EDT) Subject: [Rdo-list] [rhos-qe-dept] RDO testing In-Reply-To: <1863191962.15060345.1412158440010.JavaMail.zimbra@redhat.com> References: <1630711274.39132500.1412144719915.JavaMail.zimbra@redhat.com> <542BB8BC.4080702@redhat.com> <272936956.39185936.1412153730373.JavaMail.zimbra@redhat.com> <1863191962.15060345.1412158440010.JavaMail.zimbra@redhat.com> Message-ID: <62284803.39215532.1412158802539.JavaMail.zimbra@redhat.com> Don't forget to check workarounds https://openstack.redhat.com/Workarounds Glance issue, -> Set CONFIG_PROVISION_DEMO=n worked for me. 10.0.0.1_provision_glance.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 10.0.0.1_provision_glance.pp Error: Could not prefetch glance_image provider 'glance': Execution of '/usr/bin/glance -T services -I glance -K 86f175e8c0884d77 -N http://10.0.0.1:35357/v2.0/ index' returned 2: usage: glance [--version] [-d] [-v] [--get-schema] [--timeout TIMEOUT] You will find full trace in log /var/tmp/packstack/20141001-091112-m6iWqu/manifests/10.0.0.1_provision_glance.pp.log Please check log file /var/tmp/packstack/20141001-091112-m6iWqu/openstack-setup.log for more information workaround -> Set CONFIG_PROVISION_DEMO=n in packstack config file Rerun packstack again. ----- Original Message ----- From: "Yaniv Eylon" To: rdo-list at redhat.com Cc: "rhos-qe-dept" Sent: Wednesday, October 1, 2014 1:14:00 PM Subject: Re: [Rdo-list] [rhos-qe-dept] RDO testing lets keep our communication during the test day on rdo-list@, specially if you come across workarounds. it looks like AIO deployment is broken Bug 1148346 - provision glance not able to work Bug 1148348 - packstack on CentOS 7 fails because python-anyjson requires Python 2.6 ----- Original Message ----- > From: "Udi Kalifon" > To: "rhos-qe-dept" > Sent: Wednesday, October 1, 2014 11:55:30 AM > Subject: Re: [rhos-qe-dept] RDO testing > > I failed to install on CentOS 7. I opened a bug on it: > https://bugzilla.redhat.com/show_bug.cgi?id=1148348 > > I ran packstack --allinone and got: > > 10.35.160.13_amqp.pp: [ DONE ] > 10.35.160.13_mysql.pp: [ DONE ] > Applying 10.35.160.13_keystone.pp > Applying 10.35.160.13_glance.pp > Applying 10.35.160.13_cinder.pp > 10.35.160.13_keystone.pp: [ ERROR ] > Applying Puppet manifests [ ERROR ] > > ERROR : Error appeared during Puppet run: 10.35.160.13_keystone.pp > Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list openstack-keystone' > returned 1: Traceback (most recent call last): > You will find full trace in log > /var/tmp/packstack/20141001-103703-gbTJFP/manifests/10.35.160.13_keystone.pp.log > Please check log file > /var/tmp/packstack/20141001-103703-gbTJFP/openstack-setup.log for more > information > > > In the keystone.pp.log file you see: > ^[[1;31mError: Execution of '/usr/bin/yum -d 0 -e 0 -y install > openstack-keystone' returned 1: Error: Package: > python-anyjson-0.3.3-1.el6.noarch (epel) > Requires: python(abi) = 2.6 > Installed: python-2.7.5-16.el7.x86_64 (@anaconda) > python(abi) = 2.7 > python(abi) = 2.7 > > ... and many more dependency errors > > > Regards, > Udi. > > ----- Original Message ----- > From: "Dafna Ron" > To: "Nathan Levinkind" , "rhos-qe-dept" > > Sent: Wednesday, October 1, 2014 11:18:04 AM > Subject: Re: [rhos-qe-dept] RDO testing > > RDO in Bugzilla: > > https://bugzilla.redhat.com/enter_bug.cgi?product=RDO > > RDO page: > > https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases > > > On 10/01/2014 07:25 AM, Nathan Levinkind wrote: > > Hi, > > bugs that you do find today please report on RDO project in Bugzila and > > also add to the RDO wiki page. > > IRC =rdo in freenode server > > Thanks > > Nathan > > > > > -- > Dafna Ron > > _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list From dron at redhat.com Wed Oct 1 10:21:03 2014 From: dron at redhat.com (Dafna Ron) Date: Wed, 01 Oct 2014 11:21:03 +0100 Subject: [Rdo-list] cannot create volume group Message-ID: <542BD58F.304@redhat.com> Hi, I am failing install on centos7 with the below: grep cinder-volumes /etc/rc.d/rc.local || echo "losetup -f /var/lib/cinder/cinder-volumes && vgchange -a y cinder-volumes && systemctl restart openstack-cinder-volume.service" >> /etc/rc.d/rc.local grep "#!" /etc/rc.d/rc.local || sed -i '1i#!/bin/sh' /etc/rc.d/rc.local chmod +x /etc/rc.d/rc.local vgdisplay cinder-volumes 2014-10-01 13:13:39::INFO::shell::81::root:: [10.35.117.32] Executing script: losetup -d $(losetup -j /var/lib/cinder/cinder-volumes | cut -d : -f 1) 2014-10-01 13:13:39::ERROR::run_setup::921::root:: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 916, in main _main(confFile) File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 605, in _main runSequences() File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 584, in runSequences controller.runAllSequences() File "/usr/lib/python2.7/site-packages/packstack/installer/setup_controller.py", line 68, in runAllSequences sequence.run(config=self.CONF, messages=self.MESSAGES) File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 98, in run step.run(config=config, messages=messages) File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 44, in run raise SequenceError(str(ex)) SequenceError: Cinder's volume group 'cinder-volumes' could not be created 2014-10-01 13:13:39::INFO::shell::81::root:: [10.35.117.32] Executing script: rm -rf /var/tmp/packstack/ae1d0d8546684ca28743cb4bcfe9857f From dron at redhat.com Wed Oct 1 10:38:46 2014 From: dron at redhat.com (Dafna Ron) Date: Wed, 01 Oct 2014 11:38:46 +0100 Subject: [Rdo-list] cannot create volume group In-Reply-To: <542BD58F.304@redhat.com> References: <542BD58F.304@redhat.com> Message-ID: <542BD9B6.1020000@redhat.com> This was solved by changing EPEL=n in answer file. On 10/01/2014 11:21 AM, Dafna Ron wrote: > Hi, > > I am failing install on centos7 with the below: > > grep cinder-volumes /etc/rc.d/rc.local || echo "losetup -f > /var/lib/cinder/cinder-volumes && vgchange -a y cinder-volumes && > systemctl restart openstack-cinder-volume.service" >> /etc/rc.d/rc.local > grep "#!" /etc/rc.d/rc.local || sed -i '1i#!/bin/sh' /etc/rc.d/rc.local > chmod +x /etc/rc.d/rc.local > vgdisplay cinder-volumes > 2014-10-01 13:13:39::INFO::shell::81::root:: [10.35.117.32] Executing > script: > losetup -d $(losetup -j /var/lib/cinder/cinder-volumes | cut -d : -f 1) > 2014-10-01 13:13:39::ERROR::run_setup::921::root:: Traceback (most > recent call last): > File > "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", > line 916, in main > _main(confFile) > File > "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", > line 605, in _main > runSequences() > File > "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", > line 584, in runSequences > controller.runAllSequences() > File > "/usr/lib/python2.7/site-packages/packstack/installer/setup_controller.py", > line 68, in runAllSequences > sequence.run(config=self.CONF, messages=self.MESSAGES) > File > "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", > line 98, in run > step.run(config=config, messages=messages) > File > "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", > line 44, in run > raise SequenceError(str(ex)) > SequenceError: Cinder's volume group 'cinder-volumes' could not be > created > > 2014-10-01 13:13:39::INFO::shell::81::root:: [10.35.117.32] Executing > script: > rm -rf /var/tmp/packstack/ae1d0d8546684ca28743cb4bcfe9857f > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list -- Dafna Ron From nmagnezi at redhat.com Wed Oct 1 11:24:19 2014 From: nmagnezi at redhat.com (Nir Magnezi) Date: Wed, 1 Oct 2014 07:24:19 -0400 (EDT) Subject: [Rdo-list] RDO testing In-Reply-To: <648473255763364B961A02AC3BE1060D03C5B118D4@MX19A.corp.emc.com> References: <1630711274.39132500.1412144719915.JavaMail.zimbra@redhat.com> <542BB8BC.4080702@redhat.com> <272936956.39185936.1412153730373.JavaMail.zimbra@redhat.com> <1863191962.15060345.1412158440010.JavaMail.zimbra@redhat.com> <648473255763364B961A02AC3BE1060D03C5B118D4@MX19A.corp.emc.com> Message-ID: <91458648.59631589.1412162659974.JavaMail.zimbra@redhat.com> Udi, Try: sed -i s/epel-6/epel-7/g /etc/yum.repos.d/epel.repo Nir ----- Original Message ----- > From: "Yaniv Kaul" > To: "Yaniv Eylon" , rdo-list at redhat.com > Cc: "rhos-qe-dept" > Sent: Wednesday, October 1, 2014 1:18:10 PM > Subject: Re: [Rdo-list] RDO testing > > > -----Original Message----- > > From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On > > Behalf Of Yaniv Eylon > > Sent: Wednesday, October 01, 2014 1:14 PM > > To: rdo-list at redhat.com > > Cc: rhos-qe-dept > > Subject: Re: [Rdo-list] [rhos-qe-dept] RDO testing > > > > lets keep our communication during the test day on rdo-list@, specially if > > you > > come across workarounds. > > > > it looks like AIO deployment is broken > > Worked yesterday for me (on CentOS 7): > [root at lgdrm403 ~]# rpm -q python-anyjson > python-anyjson-0.3.3-3.el7.noarch > > Y. > > > > > Bug 1148346 - provision glance not able to work Bug 1148348 - packstack on > > CentOS 7 fails because python-anyjson requires Python 2.6 > > > > ----- Original Message ----- > > > From: "Udi Kalifon" > > > To: "rhos-qe-dept" > > > Sent: Wednesday, October 1, 2014 11:55:30 AM > > > Subject: Re: [rhos-qe-dept] RDO testing > > > > > > I failed to install on CentOS 7. I opened a bug on it: > > > https://bugzilla.redhat.com/show_bug.cgi?id=1148348 > > > > > > I ran packstack --allinone and got: > > > > > > 10.35.160.13_amqp.pp: [ DONE ] > > > 10.35.160.13_mysql.pp: [ DONE ] > > > Applying 10.35.160.13_keystone.pp > > > Applying 10.35.160.13_glance.pp > > > Applying 10.35.160.13_cinder.pp > > > 10.35.160.13_keystone.pp: [ ERROR ] > > > Applying Puppet manifests [ ERROR ] > > > > > > ERROR : Error appeared during Puppet run: 10.35.160.13_keystone.pp > > > Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list openstack-keystone' > > > returned 1: Traceback (most recent call last): > > > You will find full trace in log > > > /var/tmp/packstack/20141001-103703-gbTJFP/manifests/10.35.160.13_keyst > > > one.pp.log > > > Please check log file > > > /var/tmp/packstack/20141001-103703-gbTJFP/openstack-setup.log for more > > > information > > > > > > > > > In the keystone.pp.log file you see: > > > ^[[1;31mError: Execution of '/usr/bin/yum -d 0 -e 0 -y install > > > openstack-keystone' returned 1: Error: Package: > > > python-anyjson-0.3.3-1.el6.noarch (epel) > > > Requires: python(abi) = 2.6 > > > Installed: python-2.7.5-16.el7.x86_64 (@anaconda) > > > python(abi) = 2.7 > > > python(abi) = 2.7 > > > > > > ... and many more dependency errors > > > > > > > > > Regards, > > > Udi. > > > > > > ----- Original Message ----- > > > From: "Dafna Ron" > > > To: "Nathan Levinkind" , "rhos-qe-dept" > > > > > > Sent: Wednesday, October 1, 2014 11:18:04 AM > > > Subject: Re: [rhos-qe-dept] RDO testing > > > > > > RDO in Bugzilla: > > > > > > https://bugzilla.redhat.com/enter_bug.cgi?product=RDO > > > > > > RDO page: > > > > > > https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases > > > > > > > > > On 10/01/2014 07:25 AM, Nathan Levinkind wrote: > > > > Hi, > > > > bugs that you do find today please report on RDO project in Bugzila > > > > and also add to the RDO wiki page. > > > > IRC =rdo in freenode server > > > > Thanks > > > > Nathan > > > > > > > > > > > > > -- > > > Dafna Ron > > > > > > > > > > _______________________________________________ > > Rdo-list mailing list > > Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > From dron at redhat.com Wed Oct 1 11:25:29 2014 From: dron at redhat.com (Dafna Ron) Date: Wed, 01 Oct 2014 12:25:29 +0100 Subject: [Rdo-list] regression for Minimal erlang for RabbitMQ? Message-ID: <542BE4A9.5040407@redhat.com> Hi, I am failing installation on erlang ERROR : Error appeared during Puppet run: 10.35.117.32_amqp.pp Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list erlang' returned 1: Error: No matching Packages to list http://fpaste.org/138087/41216136/ we had a bug on this in the past and it seems to be related to the epel (bug is on fedora epel) please note that I had to disable epel to workaround a cinder issue (cinder cannot create cinder-volume). old bug: https://bugzilla.redhat.com/show_bug.cgi?id=1083637 New bug opened: https://bugzilla.redhat.com/show_bug.cgi?id=1148389 Dafna From augol at redhat.com Wed Oct 1 11:30:17 2014 From: augol at redhat.com (Amit Ugol) Date: Wed, 1 Oct 2014 14:30:17 +0300 Subject: [Rdo-list] regression for Minimal erlang for RabbitMQ? In-Reply-To: <542BE4A9.5040407@redhat.com> References: <542BE4A9.5040407@redhat.com> Message-ID: <20141001143017.5800c12a@augol-pc.redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 01 Oct 2014 12:25:29 +0100 Dafna Ron wrote: > Hi, > > I am failing installation on erlang > > ERROR : Error appeared during Puppet run: 10.35.117.32_amqp.pp > Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list erlang' returned > 1: Error: No matching Packages to list > > > http://fpaste.org/138087/41216136/ > > we had a bug on this in the past and it seems to be related to the > epel (bug is on fedora epel) please note that I had to disable epel > to workaround a cinder issue (cinder cannot create cinder-volume). > > old bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=1083637 > > New bug opened: > > https://bugzilla.redhat.com/show_bug.cgi?id=1148389 > > Dafna > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list This is a repo issue, make sure that epel is enabled if you enabled it and are using packstack, make sure that the answer file does not have epel=n because this will disable epel while running. - -- Best Regards, Amit. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUK+XJAAoJEJl/s+KmzM9p27sH/3eRIPZl5OGJ0Mi5zj/7l9T5 7V6oaW4mwDF+QD7Wgeb4c0bjKIFWTlUHDhw/jlISbG1MsZzMVAFpfIgFDavFF1K8 vqB+6UqA/bJcrL1b4jHvXptrKccwqT1141x3Y+e01GMDUqK1TNkin0eK8ew+Zf7x wivh/VP3sGuNOnXgDrtNIUIQngWKwL2Zko3fnkB9JpwXu6YHyxpZ5psN92vpVGhY BohZrP2TmRccV+9podSz5ZRRtNP1UtgeowHqeXKKiQ3kx9ak2V3nIO3lv79N0pYb pqL2EUFc8fgIttyaGg/h5mgCTYzqhRSaGIWYp6AGJDbEMFsRNcZEmrMToIz8fYU= =ASm2 -----END PGP SIGNATURE----- From Jan.van.Eldik at cern.ch Wed Oct 1 11:32:49 2014 From: Jan.van.Eldik at cern.ch (Jan van Eldik) Date: Wed, 1 Oct 2014 13:32:49 +0200 Subject: [Rdo-list] regression for Minimal erlang for RabbitMQ? In-Reply-To: <542BE4A9.5040407@redhat.com> References: <542BE4A9.5040407@redhat.com> Message-ID: <542BE661.1090607@cern.ch> Hi, I struggled with Epel dependencies on puppet, erlang, rabbitmq-server, ... until I learned to run packstack --allinone --use-epel=y Hope this is helpful for you, cheers, Jan On 10/01/2014 01:25 PM, Dafna Ron wrote: > Hi, > > I am failing installation on erlang > > ERROR : Error appeared during Puppet run: 10.35.117.32_amqp.pp > Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list erlang' returned 1: > Error: No matching Packages to list > > > http://fpaste.org/138087/41216136/ > > we had a bug on this in the past and it seems to be related to the epel > (bug is on fedora epel) please note that I had to disable epel to > workaround a cinder issue (cinder cannot create cinder-volume). > > old bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=1083637 > > New bug opened: > > https://bugzilla.redhat.com/show_bug.cgi?id=1148389 > > Dafna > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list From dron at redhat.com Wed Oct 1 11:33:47 2014 From: dron at redhat.com (Dafna Ron) Date: Wed, 01 Oct 2014 12:33:47 +0100 Subject: [Rdo-list] regression for Minimal erlang for RabbitMQ? In-Reply-To: <542BE661.1090607@cern.ch> References: <542BE4A9.5040407@redhat.com> <542BE661.1090607@cern.ch> Message-ID: <542BE69B.8040607@redhat.com> I had to disable epel because of a different bug for cinder. On 10/01/2014 12:32 PM, Jan van Eldik wrote: > Hi, > > I struggled with Epel dependencies on puppet, erlang, rabbitmq-server, > ... until I learned to run > > packstack --allinone --use-epel=y > > Hope this is helpful for you, > > cheers, Jan > > > On 10/01/2014 01:25 PM, Dafna Ron wrote: >> Hi, >> >> I am failing installation on erlang >> >> ERROR : Error appeared during Puppet run: 10.35.117.32_amqp.pp >> Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list erlang' returned 1: >> Error: No matching Packages to list >> >> >> http://fpaste.org/138087/41216136/ >> >> we had a bug on this in the past and it seems to be related to the epel >> (bug is on fedora epel) please note that I had to disable epel to >> workaround a cinder issue (cinder cannot create cinder-volume). >> >> old bug: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1083637 >> >> New bug opened: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1148389 >> >> Dafna >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list -- Dafna Ron From pj.pandit at yahoo.co.in Wed Oct 1 11:46:40 2014 From: pj.pandit at yahoo.co.in (P J P) Date: Wed, 1 Oct 2014 19:46:40 +0800 Subject: [Rdo-list] python-sqlalchemy is removed in epel In-Reply-To: References: <316691786CCAEE44AE90482264E3AB8206BCF768@xmb-rcd-x08.cisco.com> <1412012174.39151.YahooMailNeo@web192405.mail.sg3.yahoo.com> <1412076070.72722.YahooMailNeo@web192403.mail.sg3.yahoo.com> <1412099316.50059.YahooMailNeo@web192406.mail.sg3.yahoo.com> Message-ID: <1412164000.93969.YahooMailNeo@web192403.mail.sg3.yahoo.com> Hello Alan, > On Wednesday, 1 October 2014 1:27 PM, Alan Pevec wrote: > Thanks a bunch for resolving this! You are welcome! :) --- Regards -Prasad http://feedmug.com From nmagnezi at redhat.com Wed Oct 1 12:00:46 2014 From: nmagnezi at redhat.com (Nir Magnezi) Date: Wed, 1 Oct 2014 08:00:46 -0400 (EDT) Subject: [Rdo-list] regression for Minimal erlang for RabbitMQ? In-Reply-To: <542BE4A9.5040407@redhat.com> References: <542BE4A9.5040407@redhat.com> Message-ID: <776123848.59650994.1412164846284.JavaMail.zimbra@redhat.com> Hi Dafna, eglang should be installed from epel. Please verity you answer file is set with: CONFIG_USE_EPEL=y Nir ----- Original Message ----- > From: "Dafna Ron" > To: rdo-list at redhat.com > Sent: Wednesday, October 1, 2014 2:25:29 PM > Subject: [Rdo-list] regression for Minimal erlang for RabbitMQ? > > Hi, > > I am failing installation on erlang > > ERROR : Error appeared during Puppet run: 10.35.117.32_amqp.pp > Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list erlang' returned 1: > Error: No matching Packages to list > > > http://fpaste.org/138087/41216136/ > > we had a bug on this in the past and it seems to be related to the epel > (bug is on fedora epel) please note that I had to disable epel to > workaround a cinder issue (cinder cannot create cinder-volume). > > old bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=1083637 > > New bug opened: > > https://bugzilla.redhat.com/show_bug.cgi?id=1148389 > > Dafna > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > From tshefi at redhat.com Wed Oct 1 12:44:22 2014 From: tshefi at redhat.com (Tzach Shefi) Date: Wed, 1 Oct 2014 08:44:22 -0400 (EDT) Subject: [Rdo-list] Cinder gluster driver problem In-Reply-To: <1679339859.39262809.1412167235974.JavaMail.zimbra@redhat.com> Message-ID: <406170977.39264402.1412167462041.JavaMail.zimbra@redhat.com> Any one testing Juno with Gluster? Create volume fails with this in Cinder volume.log: 2014-10-01 15:23:07.187 1445 ERROR cinder.volume.drivers.glusterfs [req-eaa7910d-19b6-4d74-93d3-c0de59723e05 - - - - -] Exception during mounting 'ascii' codec can't decode byte 0xe2 in position 36: ordinal not in range(128) Tired on two separate Gluster volumes types replicated / distributed, both fail with same error. Maybe missing some needed volume option? Gluster volume info [root at dhcp163-130 bricks]# gluster volume info tshefi-cinder Volume Name: tshefi-cinder Type: Distribute Volume ID: f4e4c576-ec81-4500-88aa-39b8aa583ae5 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.35.163.139:/export/tshefi-cinder Options Reconfigured: auth.allow: 10.35.160.137 storage.owner-gid: 165 storage.owner-uid: 165 server.root-squash: enable [root at dhcp163-130 bricks]# gluster volume info tshefi-cin-rep Volume Name: tshefi-cin-rep Type: Replicate Volume ID: 702f7ffe-b34b-40d7-b40c-0a07cf4d4ac6 Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: 10.35.163.139:/export/tshefi-cin-rep Brick2: 10.35.163.79:/export/tshefi-cin-rep Options Reconfigured: auth.allow: 10.35.160.137 storage.owner-gid: 165 storage.owner-uid: 165 server.root-squash: enable Tshefi From stoner at redhat.com Wed Oct 1 13:07:21 2014 From: stoner at redhat.com (Sean Toner) Date: Wed, 1 Oct 2014 09:07:21 -0400 (EDT) Subject: [Rdo-list] Unable to edit https://openstack.redhat.com/Workarounds Message-ID: <378388523.39294384.1412168841970.JavaMail.zimbra@redhat.com> Hi, I tried to add a new workaround to the page at https://openstack.redhat.com/Workarounds. I can click the Edit button in the upper left hand corner, but when I click to Save Page, it doesn't actually save. I needed to put a new workaround item on that page. Thanks, Sean From rbowen at redhat.com Wed Oct 1 14:42:30 2014 From: rbowen at redhat.com (Rich Bowen) Date: Wed, 01 Oct 2014 10:42:30 -0400 Subject: [Rdo-list] Unable to edit https://openstack.redhat.com/Workarounds In-Reply-To: <378388523.39294384.1412168841970.JavaMail.zimbra@redhat.com> References: <378388523.39294384.1412168841970.JavaMail.zimbra@redhat.com> Message-ID: <542C12D6.2040908@redhat.com> On 10/01/2014 09:07 AM, Sean Toner wrote: > Hi, > > I tried to add a new workaround to the page at https://openstack.redhat.com/Workarounds. I can click the Edit button in the upper left hand corner, but when I click to Save Page, it doesn't actually save. I needed to put a new workaround item on that page. > Checking into it right away. I don't *think* it's an access controlled page ... -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From dron at redhat.com Wed Oct 1 16:08:35 2014 From: dron at redhat.com (Dafna Ron) Date: Wed, 01 Oct 2014 17:08:35 +0100 Subject: [Rdo-list] fail to modify quota's with nova error Message-ID: <542C2703.1010509@redhat.com> Hi, I tried to modify admin's quota and failing with errors from nova. Bug opened: https://bugzilla.redhat.com/show_bug.cgi?id=1148526 2014-10-01 18:56:01.676 29330 ERROR nova.api.openstack [req-788ef675-d8a1-40bb-8353-1c79bec7470a None] Caught error: (DataError) (1264, "Out of range value for column 'hard_limit' at row 1") 'INSERT INTO quotas (created_at, updated_at, deleted_at, deleted, project_id, resource, hard_limit) VALUES (%s, %s, %s, %s, %s, %s, %s)' (datetime.datetime(2014, 10, 1, 15, 56, 1, 672909), None, None, 0, 'a2a577cbc9a142b69ecaaed20b99a165', 'metadata_items', 12800000000000000) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack Traceback (most recent call last): 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/api/openstack/__init__.py", line 124, in __call__ 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack return req.get_response(self.application) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/webob/request.py", line 1296, in send 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack application, catch_exc_info=False) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/webob/request.py", line 1260, in call_application 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack app_iter = application(self.environ, start_response) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/webob/dec.py", line 144, in __call__ 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack return resp(environ, start_response) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/keystonemiddleware/auth_token.py", line 661, in __call__ 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack return self._app(env, start_response) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/webob/dec.py", line 144, in __call__ 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack return resp(environ, start_response) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/webob/dec.py", line 144, in __call__ 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack return resp(environ, start_response) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/routes/middleware.py", line 131, in __call__ 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack response = self.app(environ, start_response) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/webob/dec.py", line 144, in __call__ 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack return resp(environ, start_response) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/webob/dec.py", line 130, in __call__ 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack resp = self.call_func(req, *args, **self.kwargs) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/webob/dec.py", line 195, in call_func 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack return self.func(req, *args, **kwargs) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py", line 908, in __call__ 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack content_type, body, accept) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py", line 974, in _process_stack 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack action_result = self.dispatch(meth, request, action_args) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py", line 1058, in dispatch 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack return method(req=request, **action_args) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/contrib/quotas.py", line 200, in update 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack key, value, user_id=user_id) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/objects/base.py", line 155, in wrapper 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack result = fn(cls, context, *args, **kwargs) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/objects/quotas.py", line 119, in create_limit 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack db.quota_create(context, project_id, resource, limit, user_id=user_id) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/db/api.py", line 1073, in quota_create 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack user_id=user_id) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 149, in wrapper 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack return f(*args, **kwargs) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 2933, in quota_create 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack quota_ref.save() 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/models.py", line 52, in save 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack super(NovaBase, self).save(session=session) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/openstack/common/db/sqlalchemy/models.py", line 49, in save 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack session.flush() 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack File "/usr/lib/python2.7/site-packages/nova/openstack/common/db/sqlalchemy/session.py", line 461, in _wrap 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack raise exception.DBError(e) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack DBError: (DataError) (1264, "Out of range value for column 'hard_limit' at row 1") 'INSERT INTO quotas (created_at, updated_at, deleted_at, deleted, project_id, resource, hard_limit ) VALUES (%s, %s, %s, %s, %s, %s, %s)' (datetime.datetime(2014, 10, 1, 15, 56, 1, 672909), None, None, 0, 'a2a577cbc9a142b69ecaaed20b99a165', 'metadata_items', 12800000000000000) 2014-10-01 18:56:01.676 29330 TRACE nova.api.openstack 2014-10-01 18:56:01.679 29330 INFO nova.api.openstack [req-788ef675-d8a1-40bb-8353-1c79bec7470a None] http://10.35.117.32:8774/v2/a2a577cbc9a142b69ecaaed20b99a165/os-quota-sets/a2a577cbc9a142b69ecaaed20b99a165 returned with HTTP 500 : From oblaut at redhat.com Wed Oct 1 16:53:41 2014 From: oblaut at redhat.com (Ofer Blaut) Date: Wed, 1 Oct 2014 12:53:41 -0400 (EDT) Subject: [Rdo-list] [Net] IPV6 doesn't allocate IPv6 address - RDO In-Reply-To: <413016999.57148403.1412182172509.JavaMail.zimbra@redhat.com> Message-ID: <68640299.57149409.1412182421684.JavaMail.zimbra@redhat.com> Hi I configured setup with IPV6 to support IPv6 Full DHCP [1] Seems like the RADVD is not configure by neutron to publish required prefix Known issue ? Thanks Ofer [1] - http://pastebin.test.redhat.com/237502 From sasha at redhat.com Wed Oct 1 19:54:24 2014 From: sasha at redhat.com (Sasha Chuzhoy) Date: Wed, 1 Oct 2014 15:54:24 -0400 (EDT) Subject: [Rdo-list] Unable to edit https://openstack.redhat.com/Workarounds In-Reply-To: <378388523.39294384.1412168841970.JavaMail.zimbra@redhat.com> References: <378388523.39294384.1412168841970.JavaMail.zimbra@redhat.com> Message-ID: <326244067.39485522.1412193264211.JavaMail.zimbra@redhat.com> Hey Sean, Once you click on save - you have to complete some simple math calculation - see at the top. This is to "To protect the wiki against automated spam". Best regards, Sasha Chuzhoy. ----- Original Message ----- > From: "Sean Toner" > To: rdo-list at redhat.com > Sent: Wednesday, October 1, 2014 9:07:21 AM > Subject: [Rdo-list] Unable to edit https://openstack.redhat.com/Workarounds > > Hi, > > I tried to add a new workaround to the page at > https://openstack.redhat.com/Workarounds. I can click the Edit button in > the upper left hand corner, but when I click to Save Page, it doesn't > actually save. I needed to put a new workaround item on that page. > > Thanks, > Sean > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > From yeylon at redhat.com Thu Oct 2 06:14:40 2014 From: yeylon at redhat.com (Yaniv Eylon) Date: Thu, 2 Oct 2014 02:14:40 -0400 (EDT) Subject: [Rdo-list] [rhos-qe-dept] Juno testing day storage automation results for rhel-7 In-Reply-To: <118077517.13843356.1412229123688.JavaMail.zimbra@redhat.com> References: <118077517.13843356.1412229123688.JavaMail.zimbra@redhat.com> Message-ID: <353386495.15729126.1412230480947.JavaMail.zimbra@redhat.com> Benny thanks. sharing with rdo-list. although the links to the results will not be visible outside of RH it can help give a high level status regarding Glance and Cinder backend status. ----- Original Message ----- > From: "Benny Kopilov" > To: "rhos-qe-dept" > Sent: Thursday, October 2, 2014 8:52:03 AM > Subject: [rhos-qe-dept] Juno testing day storage automation results for rhel-7 > > Hi , > > Openstack - AIO setup > Installer - packstack + neutron(default) > > Storage reaults : > > ***Glance*** > > # localfs / all passed > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-glance-localfs/4/ > > # swift / all passed > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-glance-swift/3/ > > # s3 / all passed > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-glance-s3/3/ > > # ceph / all passed > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-glance-ceph/3/ > > > ***Cinder*** > > # lvm / (volume snapshot is broken) - BZ 1148251 > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-lvm/31/ > > # thinlvm - 1 Fails > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-thinlvm/8/ > > # gluster+fuse / 8 (4 onBZ 1069157) checking - backend configuration was > restored > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-gluster/3/ > > # gluster+libgfapi / 8 (4 on BZ 1069157) checking - backend configuration > was restored > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-gluster_libgfapi/3/ > > # nfs / pass (except unsupported by the driver -CHECKING ) > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-nfs/3/ > > # emc_iscsi / - (backend is not configured ) > > # netapp_nfs_7mode / pass > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-netapp_nfs_7mode/6/ > > # netapp_iscsi_7mode / pass > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-netapp_iscsi_7mode/14/ > > # ceph / all passed > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-ceph/3/ > > # xtreamio / (Waiting for backend upgrade ) > > *Swift* > > - localfs / all passed > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/RHOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-swift-localfs/4/ > > Thanks , > Benny > > From Yaniv.Kaul at emc.com Thu Oct 2 07:36:14 2014 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Thu, 2 Oct 2014 03:36:14 -0400 Subject: [Rdo-list] [rhos-qe-dept] Juno testing day storage automation results for rhel-7 In-Reply-To: <353386495.15729126.1412230480947.JavaMail.zimbra@redhat.com> References: <118077517.13843356.1412229123688.JavaMail.zimbra@redhat.com> <353386495.15729126.1412230480947.JavaMail.zimbra@redhat.com> Message-ID: <648473255763364B961A02AC3BE1060D03C5B119EA@MX19A.corp.emc.com> Adding XtremIO Cinder driver tests for Juno, on CentOS 7: Our results are OK on FC and iSCSI, as well as multi-backend (which isn't really multi, Tempest picks the first only). We have a problem with iSCSI+CHAP. I believe a bug on our side, as it happens on IceHouse as well. Current failures (which I'm not sure are real, we are investigating): Test Result 4 failures (?0) , 1 skipped (?0) 242 tests (?0) Took 8 min 59 sec. All Failed Tests Test Name Duration Age tempest.api.volume.admin.test_volumes_actions.VolumesActionsTest.test_volume_begin_detaching[gate] (Failed 2 times in the last 7 runs. Stability: 71 %) 0.35 sec 1 tempest.api.volume.admin.test_volumes_actions.VolumesActionsTest.test_volume_roll_detaching[gate] (Failed 2 times in the last 7 runs. Stability: 71 %) 0.1 sec 1 tempest.api.volume.admin.test_volumes_actions.VolumesActionsTestXML.test_volume_begin_detaching[gate] (Failed 2 times in the last 7 runs. Stability: 71 %) 0.33 sec 1 tempest.api.volume.admin.test_volumes_actions.VolumesActionsTestXML.test_volume_roll_detaching[gate] (Failed 2 times in the last 7 runs. Stability: 71 %) 0.1 sec 1 Thanks, Y. > -----Original Message----- > From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On > Behalf Of Yaniv Eylon > Sent: Thursday, October 02, 2014 9:15 AM > To: Benny Kopilov; rdo-list at redhat.com > Cc: rhos-qe-dept > Subject: Re: [Rdo-list] [rhos-qe-dept] Juno testing day storage automation > results for rhel-7 > > Benny thanks. > sharing with rdo-list. > although the links to the results will not be visible outside of RH it can help give > a high level status regarding Glance and Cinder backend status. > > > ----- Original Message ----- > > From: "Benny Kopilov" > > To: "rhos-qe-dept" > > Sent: Thursday, October 2, 2014 8:52:03 AM > > Subject: [rhos-qe-dept] Juno testing day storage automation results for rhel-7 > > > > Hi , > > > > Openstack - AIO setup > > Installer - packstack + neutron(default) > > > > Storage reaults : > > > > ***Glance*** > > > > # localfs / all passed > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-glance-localfs/4/ > > > > # swift / all passed > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-glance-swift/3/ > > > > # s3 / all passed > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-glance-s3/3/ > > > > # ceph / all passed > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-glance-ceph/3/ > > > > > > ***Cinder*** > > > > # lvm / (volume snapshot is broken) - BZ 1148251 > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-lvm/31/ > > > > # thinlvm - 1 Fails > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-thinlvm/8/ > > > > # gluster+fuse / 8 (4 onBZ 1069157) checking - backend configuration was > > restored > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-gluster/3/ > > > > # gluster+libgfapi / 8 (4 on BZ 1069157) checking - backend configuration > > was restored > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-gluster_libgfapi/3 > > / > > > > # nfs / pass (except unsupported by the driver -CHECKING ) > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-nfs/3/ > > > > # emc_iscsi / - (backend is not configured ) > > > > # netapp_nfs_7mode / pass > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-netapp_nfs_7mode/6 > > / > > > > # netapp_iscsi_7mode / pass > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-netapp_iscsi_7mode > > /14/ > > > > # ceph / all passed > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-cinder-ceph/3/ > > > > # xtreamio / (Waiting for backend upgrade ) > > > > *Swift* > > > > - localfs / all passed > > http://jenkins.rhev.lab.eng.brq.redhat.com/view/RHOS-STORAGE-QE/view/R > > HOS-6.0-RDO-RHEL-7.0/job/rhos-6-rdo-rhel-7.0-swift-localfs/4/ > > > > Thanks , > > Benny > > > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list From Yaniv.Kaul at emc.com Thu Oct 2 12:01:46 2014 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Thu, 2 Oct 2014 08:01:46 -0400 Subject: [Rdo-list] Tempest IceHouse broken? Message-ID: <648473255763364B961A02AC3BE1060D03C5B11A82@MX19A.corp.emc.com> On CentOS 6.5 (Python 2.6!) git init /var/jenkins/workspace/Tempest # timeout=10 Fetching upstream changes from https://github.com/redhat-openstack/tempest.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/redhat-openstack/tempest.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://github.com/redhat-openstack/tempest.git # timeout=10 > git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/redhat-openstack/tempest.git # timeout=10 Fetching upstream changes from https://github.com/redhat-openstack/tempest.git > git fetch --tags --progress https://github.com/redhat-openstack/tempest.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/icehouse^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/icehouse^{commit} # timeout=10 Checking out Revision fe12b3d0e2fb713efe923a44393880b0d4d9b0ba (refs/remotes/origin/icehouse) ... TEMPEST_CONF=/var/jenkins/workspace/Tempest/etc/tempest.conf + tools/config_tempest.py --create identity.uri http://10.103.234.141:5000/v2.0/ identity.admin_username admin identity.admin_password secret identity.admin_tenant_name admin /usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using libgmp >= 5 to avoid timing attack vulnerability. _warn("Not using mpz_powm_sec. You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning) Traceback (most recent call last): File "tools/config_tempest.py", line 654, in main() File "tools/config_tempest.py", line 141, in main configure_cli(conf) File "tools/config_tempest.py", line 528, in configure_cli cli_dir = get_program_dir("nova") File "tools/config_tempest.py", line 595, in get_program_dir path = subprocess.check_output(["which", program], stderr=devnull) AttributeError: 'module' object has no attribute 'check_output' Looks similar to https://bugs.launchpad.net/nova/+bug/1029014 ? Seems to be added in: commit 76ca1350749ea5e3c877813c6e7268122b5214ce Author: Martina Kollarova Date: Wed Sep 3 18:53:05 2014 +0200 Refactored cli_dir setting And possibly because of: +def get_program_dir(program): + """Get directory path of the external program. + + :param program: name of program, e.g. 'ls' or 'cat' + :returns: None if it wasn't found, '/path/to/it/' if found + """ + devnull = open(os.devnull, 'w') + try: + path = subprocess.check_output(["which", program], stderr=devnull) + return os.path.dirname(path.strip()) + except subprocess.CalledProcessError: + return None + Y. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkranz at redhat.com Thu Oct 2 12:29:01 2014 From: dkranz at redhat.com (David Kranz) Date: Thu, 02 Oct 2014 08:29:01 -0400 Subject: [Rdo-list] Tempest IceHouse broken? In-Reply-To: <648473255763364B961A02AC3BE1060D03C5B11A82@MX19A.corp.emc.com> References: <648473255763364B961A02AC3BE1060D03C5B11A82@MX19A.corp.emc.com> Message-ID: <542D450D.3030705@redhat.com> I believe some recent improvements introduced an external dependency on 'which' so that needs to be installed. This is taken care of if you install via the tempest rpm. Tempest has never had clear documentation about what external (non-python) packages are needed. In the upstream gate jobs this is handled by devstack. -David On 10/02/2014 08:01 AM, Kaul, Yaniv wrote: > > On CentOS 6.5 (Python 2.6!) > > git init /var/jenkins/workspace/Tempest # timeout=10 > > Fetching upstream changes from > https://github.com/redhat-openstack/tempest.git > > > git --version # timeout=10 > > > git fetch --tags --progress > https://github.com/redhat-openstack/tempest.git > +refs/heads/*:refs/remotes/origin/* > > > git config remote.origin.url > https://github.com/redhat-openstack/tempest.git # timeout=10 > > > git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # > timeout=10 > > > git config remote.origin.url > https://github.com/redhat-openstack/tempest.git # timeout=10 > > Fetching upstream changes from > https://github.com/redhat-openstack/tempest.git > > > git fetch --tags --progress > https://github.com/redhat-openstack/tempest.git > +refs/heads/*:refs/remotes/origin/* > > > git rev-parse refs/remotes/origin/icehouse^{commit} # timeout=10 > > > git rev-parse refs/remotes/origin/origin/icehouse^{commit} # timeout=10 > > Checking out Revision fe12b3d0e2fb713efe923a44393880b0d4d9b0ba > (refs/remotes/origin/icehouse) > > ... > > TEMPEST_CONF=/var/jenkins/workspace/Tempest/etc/tempest.conf > > + tools/config_tempest.py --create identity.uri > http://10.103.234.141:5000/v2.0/ identity.admin_username admin > identity.admin_password secret identity.admin_tenant_name admin > > /usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57: > PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using > libgmp >= 5 to avoid timing attack vulnerability. > > _warn("Not using mpz_powm_sec. You should rebuild using libgmp >= 5 > to avoid timing attack vulnerability.", PowmInsecureWarning) > > Traceback (most recent call last): > > File "tools/config_tempest.py", line 654, in > > main() > > File "tools/config_tempest.py", line 141, in main > > configure_cli(conf) > > File "tools/config_tempest.py", line 528, in configure_cli > > cli_dir = get_program_dir("nova") > > File "tools/config_tempest.py", line 595, in get_program_dir > > path = subprocess.check_output(["which", program], stderr=devnull) > > AttributeError: 'module' object has no attribute 'check_output' > > Looks similar to https://bugs.launchpad.net/nova/+bug/1029014 ? > > Seems to be added in: > > commit 76ca1350749ea5e3c877813c6e7268122b5214ce > > Author: Martina Kollarova > > Date: Wed Sep 3 18:53:05 2014 +0200 > > Refactored cli_dir setting > > And possibly because of: > > +def get_program_dir(program): > > + """Get directory path of the external program. > > + > > + :param program: name of program, e.g. 'ls' or 'cat' > > + :returns: None if it wasn't found, '/path/to/it/' if found > > + """ > > + devnull = open(os.devnull, 'w') > > + try: > > + path = subprocess.check_output(["which", program], > stderr=devnull) > > + return os.path.dirname(path.strip()) > > + except subprocess.CalledProcessError: > > + return None > > + > > Y. > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihrachys at redhat.com Thu Oct 2 12:38:18 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Thu, 02 Oct 2014 14:38:18 +0200 Subject: [Rdo-list] Tempest IceHouse broken? In-Reply-To: <542D450D.3030705@redhat.com> References: <648473255763364B961A02AC3BE1060D03C5B11A82@MX19A.corp.emc.com> <542D450D.3030705@redhat.com> Message-ID: <542D473A.2020904@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 It's not about 'which'... The problem is that subprocess.check_output was introduced in Python 2.7 only, and not available in Python 2.6. We should not use the method for the code that is expected to be portable between those python versions. On 02/10/14 14:29, David Kranz wrote: > I believe some recent improvements introduced an external > dependency on 'which' so that needs to be installed. This is taken > care of if you install via the tempest rpm. Tempest has never had > clear documentation about what external (non-python) packages are > needed. In the upstream gate jobs this is handled by devstack. > > -David > > On 10/02/2014 08:01 AM, Kaul, Yaniv wrote: >> >> On CentOS 6.5 (Python 2.6!) >> >> >> >> git init /var/jenkins/workspace/Tempest # timeout=10 >> >> Fetching upstream changes from >> https://github.com/redhat-openstack/tempest.git >> >>> git --version # timeout=10 >> >>> git fetch --tags --progress >> https://github.com/redhat-openstack/tempest.git >> +refs/heads/*:refs/remotes/origin/* >> >>> git config remote.origin.url >> https://github.com/redhat-openstack/tempest.git # timeout=10 >> >>> git config remote.origin.fetch >>> +refs/heads/*:refs/remotes/origin/* # >> timeout=10 >> >>> git config remote.origin.url >> https://github.com/redhat-openstack/tempest.git # timeout=10 >> >> Fetching upstream changes from >> https://github.com/redhat-openstack/tempest.git >> >>> git fetch --tags --progress >> https://github.com/redhat-openstack/tempest.git >> +refs/heads/*:refs/remotes/origin/* >> >>> git rev-parse refs/remotes/origin/icehouse^{commit} # >>> timeout=10 >> >>> git rev-parse refs/remotes/origin/origin/icehouse^{commit} # >>> timeout=10 >> >> Checking out Revision fe12b3d0e2fb713efe923a44393880b0d4d9b0ba >> (refs/remotes/origin/icehouse) >> >> >> >> ? >> >> >> >> TEMPEST_CONF=/var/jenkins/workspace/Tempest/etc/tempest.conf >> >> + tools/config_tempest.py --create identity.uri >> http://10.103.234.141:5000/v2.0/ identity.admin_username admin >> identity.admin_password secret identity.admin_tenant_name admin >> >> /usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57: >> PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild >> using libgmp >= 5 to avoid timing attack vulnerability. >> >> _warn("Not using mpz_powm_sec. You should rebuild using libgmp >> >= 5 to avoid timing attack vulnerability.", >> PowmInsecureWarning) >> >> Traceback (most recent call last): >> >> File "tools/config_tempest.py", line 654, in >> >> main() >> >> File "tools/config_tempest.py", line 141, in main >> >> configure_cli(conf) >> >> File "tools/config_tempest.py", line 528, in configure_cli >> >> cli_dir = get_program_dir("nova") >> >> File "tools/config_tempest.py", line 595, in get_program_dir >> >> path = subprocess.check_output(["which", program], >> stderr=devnull) >> >> AttributeError: 'module' object has no attribute 'check_output' >> >> >> >> >> >> >> >> Looks similar to https://bugs.launchpad.net/nova/+bug/1029014 ? >> >> Seems to be added in: >> >> commit 76ca1350749ea5e3c877813c6e7268122b5214ce >> >> Author: Martina Kollarova >> >> Date: Wed Sep 3 18:53:05 2014 +0200 >> >> >> >> Refactored cli_dir setting >> >> >> >> >> >> And possibly because of: >> >> +def get_program_dir(program): >> >> + """Get directory path of the external program. >> >> + >> >> + :param program: name of program, e.g. 'ls' or 'cat' >> >> + :returns: None if it wasn't found, '/path/to/it/' if found >> >> + """ >> >> + devnull = open(os.devnull, 'w') >> >> + try: >> >> + path = subprocess.check_output(["which", program], >> stderr=devnull) >> >> + return os.path.dirname(path.strip()) >> >> + except subprocess.CalledProcessError: >> >> + return None >> >> + >> >> >> >> >> >> Y. >> >> >> >> _______________________________________________ Rdo-list mailing >> list Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list > > > > _______________________________________________ Rdo-list mailing > list Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJULUc6AAoJEC5aWaUY1u57mWkH/3+cs714eE0Ol2CAUmB+nR5O uyabUwQHG94ETLWorSG+TwVBNEBtJL54tcyajecJVlfeZRYful2bqncCNMfzB9XV 4SFWRsCLqAB3tAHiaIpUaTWtUYMG2cFjssd6eXIehXoCJbUxtfulittoH1GDwpfT acbmOlggkbU+eIdkFZ3oaZsAgz5S8+6vc0fR0Ew1s5z9aknWAHE8eJ5YUMjZuxo7 hIC3vBHl+3OIAZuefUxdWnLQG0zqEmeQKqmQuvvzR3AE9UCwnYR/J3audj/rDZmz DjTL/Z5jTG1AzJ0hVIVVezANbmOsXiNCNzAeP6bfR5sF9S5sNEGlwRAtNwcNtQI= =XZk0 -----END PGP SIGNATURE----- From Yaniv.Kaul at emc.com Thu Oct 2 13:30:30 2014 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Thu, 2 Oct 2014 09:30:30 -0400 Subject: [Rdo-list] Tempest IceHouse broken? In-Reply-To: <542D473A.2020904@redhat.com> References: <648473255763364B961A02AC3BE1060D03C5B11A82@MX19A.corp.emc.com> <542D450D.3030705@redhat.com> <542D473A.2020904@redhat.com> Message-ID: <648473255763364B961A02AC3BE1060D03C5B11AC1@MX19A.corp.emc.com> > -----Original Message----- > From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On > Behalf Of Ihar Hrachyshka > Sent: Thursday, October 02, 2014 3:38 PM > To: rdo-list at redhat.com > Subject: Re: [Rdo-list] Tempest IceHouse broken? > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > It's not about 'which'... The problem is that subprocess.check_output was > introduced in Python 2.7 only, and not available in Python 2.6. We should not > use the method for the code that is expected to be portable between those > python versions. That's what I thought. > > On 02/10/14 14:29, David Kranz wrote: > > I believe some recent improvements introduced an external dependency > > on 'which' so that needs to be installed. This is taken care of if you > > install via the tempest rpm. Tempest has never had clear documentation > > about what external (non-python) packages are needed. In the upstream > > gate jobs this is handled by devstack. How do I get the Tempest RPM? Currently my Jenkins job is pulling from Red Hat's fork on Github. Y. > > > > -David > > > > On 10/02/2014 08:01 AM, Kaul, Yaniv wrote: > >> > >> On CentOS 6.5 (Python 2.6!) > >> > >> > >> > >> git init /var/jenkins/workspace/Tempest # timeout=10 > >> > >> Fetching upstream changes from > >> https://github.com/redhat-openstack/tempest.git > >> > >>> git --version # timeout=10 > >> > >>> git fetch --tags --progress > >> https://github.com/redhat-openstack/tempest.git > >> +refs/heads/*:refs/remotes/origin/* > >> > >>> git config remote.origin.url > >> https://github.com/redhat-openstack/tempest.git # timeout=10 > >> > >>> git config remote.origin.fetch > >>> +refs/heads/*:refs/remotes/origin/* # > >> timeout=10 > >> > >>> git config remote.origin.url > >> https://github.com/redhat-openstack/tempest.git # timeout=10 > >> > >> Fetching upstream changes from > >> https://github.com/redhat-openstack/tempest.git > >> > >>> git fetch --tags --progress > >> https://github.com/redhat-openstack/tempest.git > >> +refs/heads/*:refs/remotes/origin/* > >> > >>> git rev-parse refs/remotes/origin/icehouse^{commit} # > >>> timeout=10 > >> > >>> git rev-parse refs/remotes/origin/origin/icehouse^{commit} # > >>> timeout=10 > >> > >> Checking out Revision fe12b3d0e2fb713efe923a44393880b0d4d9b0ba > >> (refs/remotes/origin/icehouse) > >> > >> > >> > >> ? > >> > >> > >> > >> TEMPEST_CONF=/var/jenkins/workspace/Tempest/etc/tempest.conf > >> > >> + tools/config_tempest.py --create identity.uri > >> http://10.103.234.141:5000/v2.0/ identity.admin_username admin > >> identity.admin_password secret identity.admin_tenant_name admin > >> > >> /usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57: > >> PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild > >> using libgmp >= 5 to avoid timing attack vulnerability. > >> > >> _warn("Not using mpz_powm_sec. You should rebuild using libgmp > >> >= 5 to avoid timing attack vulnerability.", > >> PowmInsecureWarning) > >> > >> Traceback (most recent call last): > >> > >> File "tools/config_tempest.py", line 654, in > >> > >> main() > >> > >> File "tools/config_tempest.py", line 141, in main > >> > >> configure_cli(conf) > >> > >> File "tools/config_tempest.py", line 528, in configure_cli > >> > >> cli_dir = get_program_dir("nova") > >> > >> File "tools/config_tempest.py", line 595, in get_program_dir > >> > >> path = subprocess.check_output(["which", program], > >> stderr=devnull) > >> > >> AttributeError: 'module' object has no attribute 'check_output' > >> > >> > >> > >> > >> > >> > >> > >> Looks similar to https://bugs.launchpad.net/nova/+bug/1029014 ? > >> > >> Seems to be added in: > >> > >> commit 76ca1350749ea5e3c877813c6e7268122b5214ce > >> > >> Author: Martina Kollarova > >> > >> Date: Wed Sep 3 18:53:05 2014 +0200 > >> > >> > >> > >> Refactored cli_dir setting > >> > >> > >> > >> > >> > >> And possibly because of: > >> > >> +def get_program_dir(program): > >> > >> + """Get directory path of the external program. > >> > >> + > >> > >> + :param program: name of program, e.g. 'ls' or 'cat' > >> > >> + :returns: None if it wasn't found, '/path/to/it/' if found > >> > >> + """ > >> > >> + devnull = open(os.devnull, 'w') > >> > >> + try: > >> > >> + path = subprocess.check_output(["which", program], > >> stderr=devnull) > >> > >> + return os.path.dirname(path.strip()) > >> > >> + except subprocess.CalledProcessError: > >> > >> + return None > >> > >> + > >> > >> > >> > >> > >> > >> Y. > >> > >> > >> > >> _______________________________________________ Rdo-list mailing > list > >> Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list > > > > > > > > _______________________________________________ Rdo-list mailing > > list Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > > iQEcBAEBCgAGBQJULUc6AAoJEC5aWaUY1u57mWkH/3+cs714eE0Ol2CAUmB+ > nR5O > uyabUwQHG94ETLWorSG+TwVBNEBtJL54tcyajecJVlfeZRYful2bqncCNMfzB9XV > 4SFWRsCLqAB3tAHiaIpUaTWtUYMG2cFjssd6eXIehXoCJbUxtfulittoH1GDwpfT > acbmOlggkbU+eIdkFZ3oaZsAgz5S8+6vc0fR0Ew1s5z9aknWAHE8eJ5YUMjZuxo7 > hIC3vBHl+3OIAZuefUxdWnLQG0zqEmeQKqmQuvvzR3AE9UCwnYR/J3audj/rDZ > mz > DjTL/Z5jTG1AzJ0hVIVVezANbmOsXiNCNzAeP6bfR5sF9S5sNEGlwRAtNwcNtQI= > =XZk0 > -----END PGP SIGNATURE----- > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list From tkammer at redhat.com Thu Oct 2 14:18:27 2014 From: tkammer at redhat.com (Tal Kammer) Date: Thu, 2 Oct 2014 10:18:27 -0400 (EDT) Subject: [Rdo-list] Tempest IceHouse broken? In-Reply-To: <648473255763364B961A02AC3BE1060D03C5B11AC1@MX19A.corp.emc.com> References: <648473255763364B961A02AC3BE1060D03C5B11A82@MX19A.corp.emc.com> <542D450D.3030705@redhat.com> <542D473A.2020904@redhat.com> <648473255763364B961A02AC3BE1060D03C5B11AC1@MX19A.corp.emc.com> Message-ID: <1166528140.57628835.1412259507521.JavaMail.zimbra@redhat.com> ----- Original Message ----- > > -----Original Message----- > > From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On > > Behalf Of Ihar Hrachyshka > > Sent: Thursday, October 02, 2014 3:38 PM > > To: rdo-list at redhat.com > > Subject: Re: [Rdo-list] Tempest IceHouse broken? > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA512 > > > > It's not about 'which'... The problem is that subprocess.check_output was > > introduced in Python 2.7 only, and not available in Python 2.6. We should > > not > > use the method for the code that is expected to be portable between those > > python versions. Indeed, that specific function is the problem and will be removed in the next commit. I will push a fix as I am already doing some refactoring to the code. Please note that this code is meant to be part of tempest, it is suppose to have the same base requirements tempest has and since the upstream tempest decided to move from python 2.6 to 2.7, the problem here lies in the choice of running tempest from a machine using python 2.6. (again, tempest requirement[1], not ours.. please note the first two lines :) [1] - https://github.com/openstack/tempest#python-26 > > That's what I thought. > > > > > On 02/10/14 14:29, David Kranz wrote: > > > I believe some recent improvements introduced an external dependency > > > on 'which' so that needs to be installed. This is taken care of if you > > > install via the tempest rpm. Tempest has never had clear documentation > > > about what external (non-python) packages are needed. In the upstream > > > gate jobs this is handled by devstack. > > How do I get the Tempest RPM? Currently my Jenkins job is pulling from Red > Hat's fork on Github. > Y. There is no real need for the tempest RPM in your case, you can (and probably should as per tempest requirements) simply install tempest on any machine that have python 2.7 (I run it from a fedora 20 machine for example) and it will work just fine. You do not need tempest running from one of the Openstack instances. > > > > > > > -David > > > > > > On 10/02/2014 08:01 AM, Kaul, Yaniv wrote: > > >> > > >> On CentOS 6.5 (Python 2.6!) > > >> > > >> > > >> > > >> git init /var/jenkins/workspace/Tempest # timeout=10 > > >> > > >> Fetching upstream changes from > > >> https://github.com/redhat-openstack/tempest.git > > >> > > >>> git --version # timeout=10 > > >> > > >>> git fetch --tags --progress > > >> https://github.com/redhat-openstack/tempest.git > > >> +refs/heads/*:refs/remotes/origin/* > > >> > > >>> git config remote.origin.url > > >> https://github.com/redhat-openstack/tempest.git # timeout=10 > > >> > > >>> git config remote.origin.fetch > > >>> +refs/heads/*:refs/remotes/origin/* # > > >> timeout=10 > > >> > > >>> git config remote.origin.url > > >> https://github.com/redhat-openstack/tempest.git # timeout=10 > > >> > > >> Fetching upstream changes from > > >> https://github.com/redhat-openstack/tempest.git > > >> > > >>> git fetch --tags --progress > > >> https://github.com/redhat-openstack/tempest.git > > >> +refs/heads/*:refs/remotes/origin/* > > >> > > >>> git rev-parse refs/remotes/origin/icehouse^{commit} # > > >>> timeout=10 > > >> > > >>> git rev-parse refs/remotes/origin/origin/icehouse^{commit} # > > >>> timeout=10 > > >> > > >> Checking out Revision fe12b3d0e2fb713efe923a44393880b0d4d9b0ba > > >> (refs/remotes/origin/icehouse) > > >> > > >> > > >> > > >> ? > > >> > > >> > > >> > > >> TEMPEST_CONF=/var/jenkins/workspace/Tempest/etc/tempest.conf > > >> > > >> + tools/config_tempest.py --create identity.uri > > >> http://10.103.234.141:5000/v2.0/ identity.admin_username admin > > >> identity.admin_password secret identity.admin_tenant_name admin > > >> > > >> /usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57: > > >> PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild > > >> using libgmp >= 5 to avoid timing attack vulnerability. > > >> > > >> _warn("Not using mpz_powm_sec. You should rebuild using libgmp > > >> >= 5 to avoid timing attack vulnerability.", > > >> PowmInsecureWarning) > > >> > > >> Traceback (most recent call last): > > >> > > >> File "tools/config_tempest.py", line 654, in > > >> > > >> main() > > >> > > >> File "tools/config_tempest.py", line 141, in main > > >> > > >> configure_cli(conf) > > >> > > >> File "tools/config_tempest.py", line 528, in configure_cli > > >> > > >> cli_dir = get_program_dir("nova") > > >> > > >> File "tools/config_tempest.py", line 595, in get_program_dir > > >> > > >> path = subprocess.check_output(["which", program], > > >> stderr=devnull) > > >> > > >> AttributeError: 'module' object has no attribute 'check_output' > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> Looks similar to https://bugs.launchpad.net/nova/+bug/1029014 ? > > >> > > >> Seems to be added in: > > >> > > >> commit 76ca1350749ea5e3c877813c6e7268122b5214ce > > >> > > >> Author: Martina Kollarova > > >> > > >> Date: Wed Sep 3 18:53:05 2014 +0200 > > >> > > >> > > >> > > >> Refactored cli_dir setting > > >> > > >> > > >> > > >> > > >> > > >> And possibly because of: > > >> > > >> +def get_program_dir(program): > > >> > > >> + """Get directory path of the external program. > > >> > > >> + > > >> > > >> + :param program: name of program, e.g. 'ls' or 'cat' > > >> > > >> + :returns: None if it wasn't found, '/path/to/it/' if found > > >> > > >> + """ > > >> > > >> + devnull = open(os.devnull, 'w') > > >> > > >> + try: > > >> > > >> + path = subprocess.check_output(["which", program], > > >> stderr=devnull) > > >> > > >> + return os.path.dirname(path.strip()) > > >> > > >> + except subprocess.CalledProcessError: > > >> > > >> + return None > > >> > > >> + > > >> > > >> > > >> > > >> > > >> > > >> Y. > > >> > > >> > > >> > > >> _______________________________________________ Rdo-list mailing > > list > > >> Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list > > > > > > > > > > > > _______________________________________________ Rdo-list mailing > > > list Rdo-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > > > > iQEcBAEBCgAGBQJULUc6AAoJEC5aWaUY1u57mWkH/3+cs714eE0Ol2CAUmB+ > > nR5O > > uyabUwQHG94ETLWorSG+TwVBNEBtJL54tcyajecJVlfeZRYful2bqncCNMfzB9XV > > 4SFWRsCLqAB3tAHiaIpUaTWtUYMG2cFjssd6eXIehXoCJbUxtfulittoH1GDwpfT > > acbmOlggkbU+eIdkFZ3oaZsAgz5S8+6vc0fR0Ew1s5z9aknWAHE8eJ5YUMjZuxo7 > > hIC3vBHl+3OIAZuefUxdWnLQG0zqEmeQKqmQuvvzR3AE9UCwnYR/J3audj/rDZ > > mz > > DjTL/Z5jTG1AzJ0hVIVVezANbmOsXiNCNzAeP6bfR5sF9S5sNEGlwRAtNwcNtQI= > > =XZk0 > > -----END PGP SIGNATURE----- > > > > _______________________________________________ > > Rdo-list mailing list > > Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -- Tal Kammer Automation and infra Team Lead, Openstack platform. Red Hat Israel From Yaniv.Kaul at emc.com Thu Oct 2 14:22:31 2014 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Thu, 2 Oct 2014 10:22:31 -0400 Subject: [Rdo-list] Tempest IceHouse broken? In-Reply-To: <1166528140.57628835.1412259507521.JavaMail.zimbra@redhat.com> References: <648473255763364B961A02AC3BE1060D03C5B11A82@MX19A.corp.emc.com> <542D450D.3030705@redhat.com> <542D473A.2020904@redhat.com> <648473255763364B961A02AC3BE1060D03C5B11AC1@MX19A.corp.emc.com> <1166528140.57628835.1412259507521.JavaMail.zimbra@redhat.com> Message-ID: <648473255763364B961A02AC3BE1060D03C5B11AE3@MX19A.corp.emc.com> > -----Original Message----- > From: Tal Kammer [mailto:tkammer at redhat.com] > Sent: Thursday, October 02, 2014 5:18 PM > To: Kaul, Yaniv > Cc: Ihar Hrachyshka; rdo-list at redhat.com > Subject: Re: [Rdo-list] Tempest IceHouse broken? > > ----- Original Message ----- > > > -----Original Message----- > > > From: rdo-list-bounces at redhat.com > > > [mailto:rdo-list-bounces at redhat.com] On Behalf Of Ihar Hrachyshka > > > Sent: Thursday, October 02, 2014 3:38 PM > > > To: rdo-list at redhat.com > > > Subject: Re: [Rdo-list] Tempest IceHouse broken? > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA512 > > > > > > It's not about 'which'... The problem is that > > > subprocess.check_output was introduced in Python 2.7 only, and not > > > available in Python 2.6. We should not use the method for the code > > > that is expected to be portable between those python versions. > > Indeed, that specific function is the problem and will be removed in the next > commit. > I will push a fix as I am already doing some refactoring to the code. > Please note that this code is meant to be part of tempest, it is suppose to have > the same base requirements tempest has and since the upstream tempest > decided to move from python 2.6 to 2.7, the problem here lies in the choice of > running tempest from a machine using python 2.6. (again, tempest > requirement[1], not ours.. please note the first two lines :) > > [1] - https://github.com/openstack/tempest#python-26 Indeed, I'm already patching the discover module. I don't mind throwing away CentOS 6.x, if I know IceHouse is well supported on CentOS 7. Y. > > > > > That's what I thought. > > > > > > > > On 02/10/14 14:29, David Kranz wrote: > > > > I believe some recent improvements introduced an external > > > > dependency on 'which' so that needs to be installed. This is taken > > > > care of if you install via the tempest rpm. Tempest has never had > > > > clear documentation about what external (non-python) packages are > > > > needed. In the upstream gate jobs this is handled by devstack. > > > > How do I get the Tempest RPM? Currently my Jenkins job is pulling from > > Red Hat's fork on Github. > > Y. > > There is no real need for the tempest RPM in your case, you can (and probably > should as per tempest requirements) simply install tempest on any machine > that have python 2.7 (I run it from a fedora 20 machine for example) and it will > work just fine. > You do not need tempest running from one of the Openstack instances. > > > > > > > > > > > -David > > > > > > > > On 10/02/2014 08:01 AM, Kaul, Yaniv wrote: > > > >> > > > >> On CentOS 6.5 (Python 2.6!) > > > >> > > > >> > > > >> > > > >> git init /var/jenkins/workspace/Tempest # timeout=10 > > > >> > > > >> Fetching upstream changes from > > > >> https://github.com/redhat-openstack/tempest.git > > > >> > > > >>> git --version # timeout=10 > > > >> > > > >>> git fetch --tags --progress > > > >> https://github.com/redhat-openstack/tempest.git > > > >> +refs/heads/*:refs/remotes/origin/* > > > >> > > > >>> git config remote.origin.url > > > >> https://github.com/redhat-openstack/tempest.git # timeout=10 > > > >> > > > >>> git config remote.origin.fetch > > > >>> +refs/heads/*:refs/remotes/origin/* # > > > >> timeout=10 > > > >> > > > >>> git config remote.origin.url > > > >> https://github.com/redhat-openstack/tempest.git # timeout=10 > > > >> > > > >> Fetching upstream changes from > > > >> https://github.com/redhat-openstack/tempest.git > > > >> > > > >>> git fetch --tags --progress > > > >> https://github.com/redhat-openstack/tempest.git > > > >> +refs/heads/*:refs/remotes/origin/* > > > >> > > > >>> git rev-parse refs/remotes/origin/icehouse^{commit} # > > > >>> timeout=10 > > > >> > > > >>> git rev-parse refs/remotes/origin/origin/icehouse^{commit} # > > > >>> timeout=10 > > > >> > > > >> Checking out Revision fe12b3d0e2fb713efe923a44393880b0d4d9b0ba > > > >> (refs/remotes/origin/icehouse) > > > >> > > > >> > > > >> > > > >> ? > > > >> > > > >> > > > >> > > > >> TEMPEST_CONF=/var/jenkins/workspace/Tempest/etc/tempest.conf > > > >> > > > >> + tools/config_tempest.py --create identity.uri > > > >> http://10.103.234.141:5000/v2.0/ identity.admin_username admin > > > >> identity.admin_password secret identity.admin_tenant_name admin > > > >> > > > >> /usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57: > > > >> PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild > > > >> using libgmp >= 5 to avoid timing attack vulnerability. > > > >> > > > >> _warn("Not using mpz_powm_sec. You should rebuild using libgmp > > > >> >= 5 to avoid timing attack vulnerability.", > > > >> PowmInsecureWarning) > > > >> > > > >> Traceback (most recent call last): > > > >> > > > >> File "tools/config_tempest.py", line 654, in > > > >> > > > >> main() > > > >> > > > >> File "tools/config_tempest.py", line 141, in main > > > >> > > > >> configure_cli(conf) > > > >> > > > >> File "tools/config_tempest.py", line 528, in configure_cli > > > >> > > > >> cli_dir = get_program_dir("nova") > > > >> > > > >> File "tools/config_tempest.py", line 595, in get_program_dir > > > >> > > > >> path = subprocess.check_output(["which", program], > > > >> stderr=devnull) > > > >> > > > >> AttributeError: 'module' object has no attribute 'check_output' > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> Looks similar to https://bugs.launchpad.net/nova/+bug/1029014 ? > > > >> > > > >> Seems to be added in: > > > >> > > > >> commit 76ca1350749ea5e3c877813c6e7268122b5214ce > > > >> > > > >> Author: Martina Kollarova > > > >> > > > >> Date: Wed Sep 3 18:53:05 2014 +0200 > > > >> > > > >> > > > >> > > > >> Refactored cli_dir setting > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> And possibly because of: > > > >> > > > >> +def get_program_dir(program): > > > >> > > > >> + """Get directory path of the external program. > > > >> > > > >> + > > > >> > > > >> + :param program: name of program, e.g. 'ls' or 'cat' > > > >> > > > >> + :returns: None if it wasn't found, '/path/to/it/' if found > > > >> > > > >> + """ > > > >> > > > >> + devnull = open(os.devnull, 'w') > > > >> > > > >> + try: > > > >> > > > >> + path = subprocess.check_output(["which", program], > > > >> stderr=devnull) > > > >> > > > >> + return os.path.dirname(path.strip()) > > > >> > > > >> + except subprocess.CalledProcessError: > > > >> > > > >> + return None > > > >> > > > >> + > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> Y. > > > >> > > > >> > > > >> > > > >> _______________________________________________ Rdo-list > mailing > > > list > > > >> Rdo-list at redhat.com > > > >> https://www.redhat.com/mailman/listinfo/rdo-list > > > > > > > > > > > > > > > > _______________________________________________ Rdo-list mailing > > > > list Rdo-list at redhat.com > > > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > > > > -----BEGIN PGP SIGNATURE----- > > > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > > > > > > > iQEcBAEBCgAGBQJULUc6AAoJEC5aWaUY1u57mWkH/3+cs714eE0Ol2CAUmB+ > > > nR5O > > > > uyabUwQHG94ETLWorSG+TwVBNEBtJL54tcyajecJVlfeZRYful2bqncCNMfzB9XV > > > 4SFWRsCLqAB3tAHiaIpUaTWtUYMG2cFjssd6eXIehXoCJbUxtfulittoH1GDwpfT > > > > acbmOlggkbU+eIdkFZ3oaZsAgz5S8+6vc0fR0Ew1s5z9aknWAHE8eJ5YUMjZuxo7 > > > > hIC3vBHl+3OIAZuefUxdWnLQG0zqEmeQKqmQuvvzR3AE9UCwnYR/J3audj/rDZ > > > mz > > > > DjTL/Z5jTG1AzJ0hVIVVezANbmOsXiNCNzAeP6bfR5sF9S5sNEGlwRAtNwcNtQI= > > > =XZk0 > > > -----END PGP SIGNATURE----- > > > > > > _______________________________________________ > > > Rdo-list mailing list > > > Rdo-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > _______________________________________________ > > Rdo-list mailing list > > Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > -- > Tal Kammer > Automation and infra Team Lead, Openstack platform. > Red Hat Israel From ihrachys at redhat.com Thu Oct 2 14:38:08 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Thu, 02 Oct 2014 16:38:08 +0200 Subject: [Rdo-list] Tempest IceHouse broken? In-Reply-To: <1166528140.57628835.1412259507521.JavaMail.zimbra@redhat.com> References: <648473255763364B961A02AC3BE1060D03C5B11A82@MX19A.corp.emc.com> <542D450D.3030705@redhat.com> <542D473A.2020904@redhat.com> <648473255763364B961A02AC3BE1060D03C5B11AC1@MX19A.corp.emc.com> <1166528140.57628835.1412259507521.JavaMail.zimbra@redhat.com> Message-ID: <542D6350.9090300@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 02/10/14 16:18, Tal Kammer wrote: > ----- Original Message ----- >>> -----Original Message----- From: rdo-list-bounces at redhat.com >>> [mailto:rdo-list-bounces at redhat.com] On Behalf Of Ihar >>> Hrachyshka Sent: Thursday, October 02, 2014 3:38 PM To: >>> rdo-list at redhat.com Subject: Re: [Rdo-list] Tempest IceHouse >>> broken? >>> > It's not about 'which'... The problem is that > subprocess.check_output was introduced in Python 2.7 only, and not > available in Python 2.6. We should not use the method for the code > that is expected to be portable between those python versions. > >> Indeed, that specific function is the problem and will be removed >> in the next commit. I will push a fix as I am already doing some >> refactoring to the code. Please note that this code is meant to >> be part of tempest, it is suppose to have the same base >> requirements tempest has and since the upstream tempest decided >> to move from python 2.6 to 2.7, the problem here lies in the >> choice of running tempest from a machine using python 2.6. >> (again, tempest requirement[1], not ours.. please note the first >> two lines :) Upstream is going to drop python 2.6 support in Kilo only. So in theory all Icehouse/Juno code produced by Red Hat for Openstack should work on EL6 (at least for Icehouse for which we produce EL6 RDO repos). > >> [1] - https://github.com/openstack/tempest#python-26 > >>> >>> That's what I thought. >>> > > On 02/10/14 14:29, David Kranz wrote: >>>>> I believe some recent improvements introduced an external >>>>> dependency on 'which' so that needs to be installed. This >>>>> is taken care of if you install via the tempest rpm. >>>>> Tempest has never had clear documentation about what >>>>> external (non-python) packages are needed. In the upstream >>>>> gate jobs this is handled by devstack. >>> >>> How do I get the Tempest RPM? Currently my Jenkins job is >>> pulling from Red Hat's fork on Github. Y. > >> There is no real need for the tempest RPM in your case, you can >> (and probably should as per tempest requirements) simply install >> tempest on any machine that have python 2.7 (I run it from a >> fedora 20 machine for example) and it will work just fine. You do >> not need tempest running from one of the Openstack instances. > >>> >>>>> >>>>> -David >>>>> >>>>> On 10/02/2014 08:01 AM, Kaul, Yaniv wrote: >>>>>> >>>>>> On CentOS 6.5 (Python 2.6!) >>>>>> >>>>>> >>>>>> >>>>>> git init /var/jenkins/workspace/Tempest # timeout=10 >>>>>> >>>>>> Fetching upstream changes from >>>>>> https://github.com/redhat-openstack/tempest.git >>>>>> >>>>>>> git --version # timeout=10 >>>>>> >>>>>>> git fetch --tags --progress >>>>>> https://github.com/redhat-openstack/tempest.git >>>>>> +refs/heads/*:refs/remotes/origin/* >>>>>> >>>>>>> git config remote.origin.url >>>>>> https://github.com/redhat-openstack/tempest.git # >>>>>> timeout=10 >>>>>> >>>>>>> git config remote.origin.fetch >>>>>>> +refs/heads/*:refs/remotes/origin/* # >>>>>> timeout=10 >>>>>> >>>>>>> git config remote.origin.url >>>>>> https://github.com/redhat-openstack/tempest.git # >>>>>> timeout=10 >>>>>> >>>>>> Fetching upstream changes from >>>>>> https://github.com/redhat-openstack/tempest.git >>>>>> >>>>>>> git fetch --tags --progress >>>>>> https://github.com/redhat-openstack/tempest.git >>>>>> +refs/heads/*:refs/remotes/origin/* >>>>>> >>>>>>> git rev-parse refs/remotes/origin/icehouse^{commit} # >>>>>>> timeout=10 >>>>>> >>>>>>> git rev-parse >>>>>>> refs/remotes/origin/origin/icehouse^{commit} # >>>>>>> timeout=10 >>>>>> >>>>>> Checking out Revision >>>>>> fe12b3d0e2fb713efe923a44393880b0d4d9b0ba >>>>>> (refs/remotes/origin/icehouse) >>>>>> >>>>>> >>>>>> >>>>>> ? >>>>>> >>>>>> >>>>>> >>>>>> TEMPEST_CONF=/var/jenkins/workspace/Tempest/etc/tempest.conf >>>>>> >>>>>> >>>>>> + tools/config_tempest.py --create identity.uri >>>>>> http://10.103.234.141:5000/v2.0/ identity.admin_username >>>>>> admin identity.admin_password secret >>>>>> identity.admin_tenant_name admin >>>>>> >>>>>> /usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57: >>>>>> >>>>>> PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild >>>>>> using libgmp >= 5 to avoid timing attack vulnerability. >>>>>> >>>>>> _warn("Not using mpz_powm_sec. You should rebuild using >>>>>> libgmp >>>>>>> = 5 to avoid timing attack vulnerability.", >>>>>> PowmInsecureWarning) >>>>>> >>>>>> Traceback (most recent call last): >>>>>> >>>>>> File "tools/config_tempest.py", line 654, in >>>>>> >>>>>> main() >>>>>> >>>>>> File "tools/config_tempest.py", line 141, in main >>>>>> >>>>>> configure_cli(conf) >>>>>> >>>>>> File "tools/config_tempest.py", line 528, in >>>>>> configure_cli >>>>>> >>>>>> cli_dir = get_program_dir("nova") >>>>>> >>>>>> File "tools/config_tempest.py", line 595, in >>>>>> get_program_dir >>>>>> >>>>>> path = subprocess.check_output(["which", program], >>>>>> stderr=devnull) >>>>>> >>>>>> AttributeError: 'module' object has no attribute >>>>>> 'check_output' >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Looks similar to >>>>>> https://bugs.launchpad.net/nova/+bug/1029014 ? >>>>>> >>>>>> Seems to be added in: >>>>>> >>>>>> commit 76ca1350749ea5e3c877813c6e7268122b5214ce >>>>>> >>>>>> Author: Martina Kollarova >>>>>> >>>>>> Date: Wed Sep 3 18:53:05 2014 +0200 >>>>>> >>>>>> >>>>>> >>>>>> Refactored cli_dir setting >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> And possibly because of: >>>>>> >>>>>> +def get_program_dir(program): >>>>>> >>>>>> + """Get directory path of the external program. >>>>>> >>>>>> + >>>>>> >>>>>> + :param program: name of program, e.g. 'ls' or 'cat' >>>>>> >>>>>> + :returns: None if it wasn't found, '/path/to/it/' if >>>>>> found >>>>>> >>>>>> + """ >>>>>> >>>>>> + devnull = open(os.devnull, 'w') >>>>>> >>>>>> + try: >>>>>> >>>>>> + path = subprocess.check_output(["which", >>>>>> program], stderr=devnull) >>>>>> >>>>>> + return os.path.dirname(path.strip()) >>>>>> >>>>>> + except subprocess.CalledProcessError: >>>>>> >>>>>> + return None >>>>>> >>>>>> + >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Y. >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ Rdo-list >>>>>> mailing > list >>>>>> Rdo-list at redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>>> >>>>> >>>>> >>>>> _______________________________________________ Rdo-list >>>>> mailing list Rdo-list at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/rdo-list >>>>> >>> >>> _______________________________________________ Rdo-list >>> mailing list Rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >> >> _______________________________________________ Rdo-list mailing >> list Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJULWNQAAoJEC5aWaUY1u579IsH/1I/tHxo+bi+vZL74hrbVGj7 EUaA+LaaVUDKTgWa7I6wktaSiVAtXWEg9LPJKBdzoWU2EZ+8Gcu5iSiSGDCNWBLN Rkj+6bRRk3lNxrWSMufpodyhLx5DW5Xvbv7KOVe8mKtFK/MTljXQ6rC4uy2Pb5Ny tMDqanAhSjf2jh5Igrx7KZMs5CpoCC6X5Ul49D2zITm6qBa/15tEOtpa4R+GTydh ZPbMzvYJlZNYXLxI+xcGD7kP1ktFc8LCHT3QDAhQyaZCs3OA1hxeTjsXhiFLK6m8 qnFFLG8WuoQsxDnwIDe9IPRoeAf7bBItxOwQwdJkAKWjdzAq62pmWyXDrFfkN90= =s6F1 -----END PGP SIGNATURE----- From dustymabe at gmail.com Fri Oct 3 04:01:46 2014 From: dustymabe at gmail.com (Dusty Mabe) Date: Fri, 3 Oct 2014 00:01:46 -0400 Subject: [Rdo-list] mariadb/neutron-server timing on boot Message-ID: <20141003040146.GA1375@localhost.localdomain> Hi all, Testing F21 and Juno today I saw an error where neutron-server came up before mariadb was fully ready to accept connections. See [1]. Starting neutron-server again (after mariadb was up) worked fine. Should we be spelling out dependencies like this in our systemd unit files or in some other way handling this race condition? Thanks, Dusty [1] - http://paste.fedoraproject.org/138670/14122804/raw/ From apevec at gmail.com Fri Oct 3 09:03:32 2014 From: apevec at gmail.com (Alan Pevec) Date: Fri, 3 Oct 2014 11:03:32 +0200 Subject: [Rdo-list] mariadb/neutron-server timing on boot In-Reply-To: <20141003040146.GA1375@localhost.localdomain> References: <20141003040146.GA1375@localhost.localdomain> Message-ID: > Testing F21 and Juno today I saw an error where neutron-server came up > before mariadb was fully ready to accept connections. See [1]. Starting > neutron-server again (after mariadb was up) worked fine. https://bugzilla.redhat.com/show_bug.cgi?id=1144181 There is an upstream patch in progress for oslo.db which I'll include in RDO rpm until oslo.db release with the fix is available. Cheers, Alan From ihrachys at redhat.com Fri Oct 3 09:07:31 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Fri, 03 Oct 2014 11:07:31 +0200 Subject: [Rdo-list] mariadb/neutron-server timing on boot In-Reply-To: References: <20141003040146.GA1375@localhost.localdomain> Message-ID: <542E6753.4000805@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 We still need to reach MariaDB maintainers on why it takes so long for MariaDB to start up with a tiny database. Even with the upstream patch applied, I saw neutron-server service being killed due to systemd timeout (90 secs) because for some reason MariaDB was able to successfully start up in > 100 secs only. I think the problem is worth a separate bug. On 03/10/14 11:03, Alan Pevec wrote: >> Testing F21 and Juno today I saw an error where neutron-server >> came up before mariadb was fully ready to accept connections. See >> [1]. Starting neutron-server again (after mariadb was up) worked >> fine. > > https://bugzilla.redhat.com/show_bug.cgi?id=1144181 There is an > upstream patch in progress for oslo.db which I'll include in RDO > rpm until oslo.db release with the fix is available. > > Cheers, Alan > > _______________________________________________ Rdo-list mailing > list Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJULmdTAAoJEC5aWaUY1u57HDYH/AxmvoDgXjTzFr4tfN8tBgcC 7QYvQAIJ6QTdXfhyuV2nraGS4TD3DOURsWVW5f/aJqsZwfII94BQ6SMM1o7vpiVF B8NlRZOZ40PWqNnVlfmS5d3B8Nl+PwAPRqGOJsXYUEtR9VIABVYtnS0tXeamRe2y RXtcnpfMalv6NnznWwwGUT+/u7z5imlvLzay63bvlubovB3iIS5GhpnjF4AKUm+q m3bpQnrjkUh4kZo+nZXRwQ6rLmC4+auv57qq6lfD6v2ry4IBMn5ElyxddnKA71tU iI2nVdOl4ALONbz3Mtcz5ElZSYcBxvJua3R2fkpG8kPonpFX+WU0zInAszskWBo= =DZbB -----END PGP SIGNATURE----- From rbowen at redhat.com Fri Oct 3 13:56:33 2014 From: rbowen at redhat.com (Rich Bowen) Date: Fri, 03 Oct 2014 09:56:33 -0400 Subject: [Rdo-list] Notes from test days Message-ID: <542EAB11.6080904@redhat.com> The raw IRC transcripts from the RDO test day are available at http://meetbot.fedoraproject.org/rdo/2014-09-30/ Of particular interest, probably are the links that are enumerated in http://meetbot.fedoraproject.org/rdo/2014-09-30/rdo.2014-09-30-20.59.html which show many of the bugs that were encountered or opened during the course of testing. There's also some listed on https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases Thank you all so much for participating in testing, and helping find these things. Thanks also for the people that answered questions all day long on IRC and on this mailing list. You're making OpenStack better. If you participated in testing, and haven't shared your notes or results, please take a moment today to do that, while the memory is fresh. You can write these up anywhere - please link to them from the Test Cases, and please open tickets if you encountered problems. It's always better to open a ticket, if you're not sure if the issue has been raised before. Start here: https://bugzilla.redhat.com/enter_bug.cgi?product=RDO Finally, a reminder that, although test day is over, you're always encouraged to test the latest builds, and report your findings here - on this list - and on IRC, so that together we can continue to make OpenStack better. * Test day details - https://openstack.redhat.com/RDO_test_day_Juno_milestone_3 * Tests and results - https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From rbowen at redhat.com Fri Oct 3 15:08:54 2014 From: rbowen at redhat.com (Rich Bowen) Date: Fri, 03 Oct 2014 11:08:54 -0400 Subject: [Rdo-list] Fwd: [OpenStack Marketing] May 2015 OpenStack Summit - Save the Date In-Reply-To: <61B77158-3252-4E2D-97B6-D8471354C23A@openstack.org> References: <61B77158-3252-4E2D-97B6-D8471354C23A@openstack.org> Message-ID: <542EBC06.3030604@redhat.com> FYI -------- Forwarded Message -------- Subject: [OpenStack Marketing] May 2015 OpenStack Summit - Save the Date Date: Fri, 3 Oct 2014 09:57:52 -0500 From: Claire Massey To: marketing at lists.openstack.org Save the Date! The next OpenStack Summit will be held in Vancouver, BC: May 18-22, 2015. Stay tuned for details! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 417283 bytes Desc: not available URL: -------------- next part -------------- _______________________________________________ Marketing mailing list Marketing at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/marketing From ihrachys at redhat.com Fri Oct 3 16:31:02 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Fri, 03 Oct 2014 18:31:02 +0200 Subject: [Rdo-list] [Net] IPV6 doesn't allocate IPv6 address - RDO In-Reply-To: <68640299.57149409.1412182421684.JavaMail.zimbra@redhat.com> References: <68640299.57149409.1412182421684.JavaMail.zimbra@redhat.com> Message-ID: <542ECF46.5090405@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I'm going to look at IPv6 stateful deployment more closely the next week. It seems IPv6 deployment is not quite clear. AFAIK radvd should not send a prefix in stateful mode, it should only advertise itself and set M and O flags to 1. /Ihar On 01/10/14 18:53, Ofer Blaut wrote: > Hi > > I configured setup with IPV6 to support IPv6 Full DHCP [1] > > Seems like the RADVD is not configure by neutron to publish > required prefix Known issue ? > > Thanks > > Ofer > > [1] - http://pastebin.test.redhat.com/237502 > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJULs9FAAoJEC5aWaUY1u575RgH/3xqWew6ZxcQ8nUuy7HN/8kb qh7Q4xD+ixRC+50i5POU3WS3Kmmfvkleh+gxPj6AMgzRWQze2uF88LA32a+sUjPQ kbh0+GsrAzY5WbOuAuGO6bIboIgaXN3dLu4AyLXaTnWZKviEz8hc3ze5mVvr90YL O9+3AfDk/TdJBbOto9i10IKKb4IEHFIecEf+t3AHIZViXFCN1CRfqFo+DhK0T1mH dDPXin0kPwlHAq4bvmPnZ4jPOXbpedNnTzG6Sgkvml369jYTYBbv/FjRehkiX7PC wucxgLx0p0KMQiiVbIho09pTlFr7TH/zjwPYki1xiC8MwwyAIwWRDCFWKHcTU4M= =zfkX -----END PGP SIGNATURE----- From harm at weites.com Sat Oct 4 17:44:24 2014 From: harm at weites.com (Harm Weites) Date: Sat, 04 Oct 2014 19:44:24 +0200 Subject: [Rdo-list] Juno EL6 packages Message-ID: <543031F8.7000203@weites.com> Hi, The Icehouse and earlier releases of RDO/OpenStack were packaged for EL6, though at [1] there is no epel-6 corner for Juno. Only epel-7 is available. Will there even be an RDO for EL6 based platforms, like CentOS 6.5? [1] https://repos.fedorapeople.org/repos/openstack/ From mail at arif-ali.co.uk Sat Oct 4 22:20:18 2014 From: mail at arif-ali.co.uk (Arif Ali) Date: Sat, 4 Oct 2014 23:20:18 +0100 Subject: [Rdo-list] Heat in RDO Juno M3 Message-ID: Hi all, I have been trying a few things in heat on Juno over the last few days, and thanks to larsks on IRC, I managed to get really far. I have encountered 2 problems 1) The package heat-cfntools is no longer available in either of the rdo repository or epel for el7, It was available for el6. How best can we get hold of this package for CentOS 7. Or in-fact do we do the cfn-signal in a different way, and we no longer need to use this command? 2) I have been trying to to give unique names/numbers to hosts that are created through the "OS::Heat::ResourceGroup" resource, this supposedly has a feature where we can use %index% to add unique numbers to any of the variables. But this fails to work with the following error. Error parsing template file:///root/hpc.yaml while scanning for the next token found character that cannot start any token in "", line 207, column 23 I have pasted the contents of hpc.yaml that gives the error here -> http://fpaste.org/139239/, this is an amended template from that larsks pointed me to. Any insight on any of the above would be great -- Arif Ali IRC: arif-ali at freenode LinkedIn: http://uk.linkedin.com/in/arifali -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrunge at redhat.com Sun Oct 5 08:50:17 2014 From: mrunge at redhat.com (Matthias Runge) Date: Sun, 05 Oct 2014 10:50:17 +0200 Subject: [Rdo-list] Juno EL6 packages In-Reply-To: <543031F8.7000203@weites.com> References: <543031F8.7000203@weites.com> Message-ID: <54310649.90804@redhat.com> On 04/10/14 19:44, Harm Weites wrote: > Hi, > > The Icehouse and earlier releases of RDO/OpenStack were packaged for > EL6, though at [1] there is no epel-6 corner for Juno. Only epel-7 is > available. Will there even be an RDO for EL6 based platforms, like > CentOS 6.5? > > [1] https://repos.fedorapeople.org/repos/openstack/ > tl;dr no plans to build Juno for EL6. This was already discussed at https://www.redhat.com/archives/rdo-list/2014-September/msg00122.html and later mails, for background information, you'll likely want to read https://www.redhat.com/archives/rdo-list/2014-September/msg00128.html Best, Matthias From nyechiel at redhat.com Sun Oct 5 08:59:55 2014 From: nyechiel at redhat.com (Nir Yechiel) Date: Sun, 5 Oct 2014 04:59:55 -0400 (EDT) Subject: [Rdo-list] [Net] IPV6 doesn't allocate IPv6 address - RDO In-Reply-To: <542ECF46.5090405@redhat.com> References: <68640299.57149409.1412182421684.JavaMail.zimbra@redhat.com> <542ECF46.5090405@redhat.com> Message-ID: <496811869.40761440.1412499595883.JavaMail.zimbra@redhat.com> ----- Original Message ----- > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > I'm going to look at IPv6 stateful deployment more closely the next > week. It seems IPv6 deployment is not quite clear. > > AFAIK radvd should not send a prefix in stateful mode, it should only > advertise itself and set M and O flags to 1. > > /Ihar > In both stateless auto configuration and DHCPv6 cases, receipt of Router Advertisement should cause VM to install default route pointing to the link-local address of the port by which the Neutron router uses to send out Router Advertisement. -Nir > On 01/10/14 18:53, Ofer Blaut wrote: > > Hi > > > > I configured setup with IPV6 to support IPv6 Full DHCP [1] > > > > Seems like the RADVD is not configure by neutron to publish > > required prefix Known issue ? > > > > Thanks > > > > Ofer > > > > [1] - http://pastebin.test.redhat.com/237502 > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > > iQEcBAEBCgAGBQJULs9FAAoJEC5aWaUY1u575RgH/3xqWew6ZxcQ8nUuy7HN/8kb > qh7Q4xD+ixRC+50i5POU3WS3Kmmfvkleh+gxPj6AMgzRWQze2uF88LA32a+sUjPQ > kbh0+GsrAzY5WbOuAuGO6bIboIgaXN3dLu4AyLXaTnWZKviEz8hc3ze5mVvr90YL > O9+3AfDk/TdJBbOto9i10IKKb4IEHFIecEf+t3AHIZViXFCN1CRfqFo+DhK0T1mH > dDPXin0kPwlHAq4bvmPnZ4jPOXbpedNnTzG6Sgkvml369jYTYBbv/FjRehkiX7PC > wucxgLx0p0KMQiiVbIho09pTlFr7TH/zjwPYki1xiC8MwwyAIwWRDCFWKHcTU4M= > =zfkX > -----END PGP SIGNATURE----- > From ak at cloudssky.com Sun Oct 5 11:57:39 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Sun, 5 Oct 2014 13:57:39 +0200 Subject: [Rdo-list] Notes from test days In-Reply-To: References: <542EAB11.6080904@redhat.com> Message-ID: Sorry Rich, I posted the my previous email inadvertently only to you. The answer to my own question regarding vxlan support for Juno is: Yes, it works like a charm, what I was missing was the proper network configuration for ovs and the br-ex interface on CentOS 7 and some additional steps by creating the networks after deployment and the right settings in the answer-file I'll write a step by step how to for ML2 VXLAN OpenStack Juno deployment with Packstack and post the link on this list in few hours. Thanks! - Arash On Sat, Oct 4, 2014 at 8:41 PM, Arash Kaffamanesh wrote: > Hi Rich, > hello together, > > Many thanks to you and all of you for your effort testing the Juno release. > > I'm trying to get a 2 node RDO Juno installation working with > Packstack (1 controller and 1 compute, each with 2 nics on CentOS 7) and > it seems that the vxlan is the default networking mode now. But after the > initial installation and creating a tenant, user and networks (internal and > external) and spawning instances, the instances show up in the console > properly, and I can associate floating IPs to the instances, but I can't > ping or ssh into them. > > On CentOS 7, the reason for me seems to be openvswitch related and if I > try to create the ifcfg-br-ex bridge by hand and plug the external > interface vis ovs into it, then I'm not able to login to the controller > host. > > So my question is, does vxlan work on Juno at this time at all :-) > And if yes, could someone provide any hint about how to create the br-ex > and create the interfaces properly on CentOS 7 for this 2 node installation? > > Thanks! > Arash > > > On Fri, Oct 3, 2014 at 3:56 PM, Rich Bowen wrote: > >> The raw IRC transcripts from the RDO test day are available at >> http://meetbot.fedoraproject.org/rdo/2014-09-30/ >> >> Of particular interest, probably are the links that are enumerated in >> http://meetbot.fedoraproject.org/rdo/2014-09-30/rdo.2014-09-30-20.59.html >> which show many of the bugs that were encountered or opened during the >> course of testing. >> >> There's also some listed on https://openstack.redhat.com/ >> RDO_test_day_Juno_milestone_3_test_cases >> >> Thank you all so much for participating in testing, and helping find >> these things. Thanks also for the people that answered questions all day >> long on IRC and on this mailing list. You're making OpenStack better. >> >> If you participated in testing, and haven't shared your notes or results, >> please take a moment today to do that, while the memory is fresh. You can >> write these up anywhere - please link to them from the Test Cases, and >> please open tickets if you encountered problems. It's always better to open >> a ticket, if you're not sure if the issue has been raised before. Start >> here: https://bugzilla.redhat.com/enter_bug.cgi?product=RDO >> >> Finally, a reminder that, although test day is over, you're always >> encouraged to test the latest builds, and report your findings here - on >> this list - and on IRC, so that together we can continue to make OpenStack >> better. >> >> * Test day details - https://openstack.redhat.com/ >> RDO_test_day_Juno_milestone_3 >> * Tests and results - https://openstack.redhat.com/ >> RDO_test_day_Juno_milestone_3_test_cases >> >> -- >> Rich Bowen - rbowen at redhat.com >> OpenStack Community Liaison >> http://openstack.redhat.com/ >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From whayutin at redhat.com Sun Oct 5 12:42:14 2014 From: whayutin at redhat.com (whayutin) Date: Sun, 05 Oct 2014 08:42:14 -0400 Subject: [Rdo-list] Notes from test days In-Reply-To: References: <542EAB11.6080904@redhat.com> Message-ID: <1412512934.5016.3.camel@localhost.localdomain> On Sun, 2014-10-05 at 13:57 +0200, Arash Kaffamanesh wrote: > Sorry Rich, I posted the my previous email inadvertently only to you. > > The answer to my own question regarding vxlan support for Juno is: > Yes, it works like a charm, what I was missing was the proper network > configuration for ovs and the br-ex interface on CentOS 7 and some > additional steps by creating the networks after deployment and the > right settings in the answer-file > I'll write a step by step how to for ML2 VXLAN OpenStack Juno > deployment with Packstack and post the link on this list in few hours. > > > Thanks! > - Arash Our internal testing shows this should work for you, however our public facing 2 node ml2-vxlan is failing to launch instances so there may be some configuration error there. https://prod-rdojenkins.rhcloud.com/job/khaleesi-rdo-juno-production-centos-7.0-multinode-packstack-neutron-ml2-vxlan-rabbitmq/ > > > > > > > > On Sat, Oct 4, 2014 at 8:41 PM, Arash Kaffamanesh > wrote: > Hi Rich, > hello together, > > > Many thanks to you and all of you for your effort testing the > Juno release. > > > I'm trying to get a 2 node RDO Juno installation working with > Packstack (1 controller and 1 compute, each with 2 nics on > CentOS 7) and it seems that the vxlan is the default > networking mode now. But after the initial installation and > creating a tenant, user and networks (internal and external) > and spawning instances, the instances show up in the console > properly, and I can associate floating IPs to the instances, > but I can't ping or ssh into them. > > > On CentOS 7, the reason for me seems to be openvswitch related > and if I try to create the ifcfg-br-ex bridge by hand and plug > the external interface vis ovs into it, then I'm not able to > login to the controller host. > > > So my question is, does vxlan work on Juno at this time at > all :-) > And if yes, could someone provide any hint about how to create > the br-ex and create the interfaces properly on CentOS 7 for > this 2 node installation? > > > Thanks! > Arash > > > > On Fri, Oct 3, 2014 at 3:56 PM, Rich Bowen > wrote: > The raw IRC transcripts from the RDO test day are > available at > http://meetbot.fedoraproject.org/rdo/2014-09-30/ > > Of particular interest, probably are the links that > are enumerated in > http://meetbot.fedoraproject.org/rdo/2014-09-30/rdo.2014-09-30-20.59.html which show many of the bugs that were encountered or opened during the course of testing. > > There's also some listed on > https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases > > Thank you all so much for participating in testing, > and helping find these things. Thanks also for the > people that answered questions all day long on IRC and > on this mailing list. You're making OpenStack better. > > If you participated in testing, and haven't shared > your notes or results, please take a moment today to > do that, while the memory is fresh. You can write > these up anywhere - please link to them from the Test > Cases, and please open tickets if you encountered > problems. It's always better to open a ticket, if > you're not sure if the issue has been raised before. > Start here: > https://bugzilla.redhat.com/enter_bug.cgi?product=RDO > > Finally, a reminder that, although test day is over, > you're always encouraged to test the latest builds, > and report your findings here - on this list - and on > IRC, so that together we can continue to make > OpenStack better. > > * Test day details - > https://openstack.redhat.com/RDO_test_day_Juno_milestone_3 > * Tests and results - > https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > From ak at cloudssky.com Sun Oct 5 20:54:14 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Sun, 5 Oct 2014 22:54:14 +0200 Subject: [Rdo-list] Notes from test days In-Reply-To: <1412512934.5016.3.camel@localhost.localdomain> References: <542EAB11.6080904@redhat.com> <1412512934.5016.3.camel@localhost.localdomain> Message-ID: Here is an initial blog writing and my configs for "RDO OpenStack Juno ML2 VXLAN 2 Node Deployment On CentOS 7 With Packstack" http://cloudssky.com/en/blog/RDO-OpenStack-Juno-ML2-VXLAN-2-Node-Deployment-On-CentOS-7-With-Packstack/ and I know the post needs a lot of improvements and I'll be thankful for your feedback. Thanks again to all of you which made the RDO test days happen and so successful. -Arash On Sun, Oct 5, 2014 at 2:42 PM, whayutin wrote: > On Sun, 2014-10-05 at 13:57 +0200, Arash Kaffamanesh wrote: > > Sorry Rich, I posted the my previous email inadvertently only to you. > > > > The answer to my own question regarding vxlan support for Juno is: > > Yes, it works like a charm, what I was missing was the proper network > > configuration for ovs and the br-ex interface on CentOS 7 and some > > additional steps by creating the networks after deployment and the > > right settings in the answer-file > > I'll write a step by step how to for ML2 VXLAN OpenStack Juno > > deployment with Packstack and post the link on this list in few hours. > > > > > > Thanks! > > - Arash > > Our internal testing shows this should work for you, however our public > facing 2 node ml2-vxlan is failing to launch instances so there may be > some configuration error there. > > > https://prod-rdojenkins.rhcloud.com/job/khaleesi-rdo-juno-production-centos-7.0-multinode-packstack-neutron-ml2-vxlan-rabbitmq/ > > > > > > > > > > > > > > > > > On Sat, Oct 4, 2014 at 8:41 PM, Arash Kaffamanesh > > wrote: > > Hi Rich, > > hello together, > > > > > > Many thanks to you and all of you for your effort testing the > > Juno release. > > > > > > I'm trying to get a 2 node RDO Juno installation working with > > Packstack (1 controller and 1 compute, each with 2 nics on > > CentOS 7) and it seems that the vxlan is the default > > networking mode now. But after the initial installation and > > creating a tenant, user and networks (internal and external) > > and spawning instances, the instances show up in the console > > properly, and I can associate floating IPs to the instances, > > but I can't ping or ssh into them. > > > > > > On CentOS 7, the reason for me seems to be openvswitch related > > and if I try to create the ifcfg-br-ex bridge by hand and plug > > the external interface vis ovs into it, then I'm not able to > > login to the controller host. > > > > > > So my question is, does vxlan work on Juno at this time at > > all :-) > > And if yes, could someone provide any hint about how to create > > the br-ex and create the interfaces properly on CentOS 7 for > > this 2 node installation? > > > > > > Thanks! > > Arash > > > > > > > > On Fri, Oct 3, 2014 at 3:56 PM, Rich Bowen > > wrote: > > The raw IRC transcripts from the RDO test day are > > available at > > http://meetbot.fedoraproject.org/rdo/2014-09-30/ > > > > Of particular interest, probably are the links that > > are enumerated in > > > http://meetbot.fedoraproject.org/rdo/2014-09-30/rdo.2014-09-30-20.59.html > which show many of the bugs that were encountered or opened during the > course of testing. > > > > There's also some listed on > > > https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases > > > > Thank you all so much for participating in testing, > > and helping find these things. Thanks also for the > > people that answered questions all day long on IRC and > > on this mailing list. You're making OpenStack better. > > > > If you participated in testing, and haven't shared > > your notes or results, please take a moment today to > > do that, while the memory is fresh. You can write > > these up anywhere - please link to them from the Test > > Cases, and please open tickets if you encountered > > problems. It's always better to open a ticket, if > > you're not sure if the issue has been raised before. > > Start here: > > https://bugzilla.redhat.com/enter_bug.cgi?product=RDO > > > > Finally, a reminder that, although test day is over, > > you're always encouraged to test the latest builds, > > and report your findings here - on this list - and on > > IRC, so that together we can continue to make > > OpenStack better. > > > > * Test day details - > > > https://openstack.redhat.com/RDO_test_day_Juno_milestone_3 > > * Tests and results - > > > https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases > > > > _______________________________________________ > > Rdo-list mailing list > > Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From augol at redhat.com Mon Oct 6 03:40:11 2014 From: augol at redhat.com (Amit Ugol) Date: Mon, 6 Oct 2014 06:40:11 +0300 Subject: [Rdo-list] Heat in RDO Juno M3 In-Reply-To: References: Message-ID: <20141006064011.15122768@augol-pc.redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 4 Oct 2014 23:20:18 +0100 Arif Ali wrote: > Hi all, > > I have been trying a few things in heat on Juno over the last few > days, and thanks to larsks on IRC, I managed to get really far. I > have encountered 2 problems > > 1) The package heat-cfntools is no longer available in either of the > rdo repository or epel for el7, It was available for el6. How best > can we get hold of this package for CentOS 7. Or in-fact do we do the > cfn-signal in a different way, and we no longer need to use this > command? > > 2) I have been trying to to give unique names/numbers to hosts that > are created through the "OS::Heat::ResourceGroup" resource, this > supposedly has a feature where we can use %index% to add unique > numbers to any of the variables. But this fails to work with the > following error. > > Error parsing template file:///root/hpc.yaml while scanning for the > next token > found character that cannot start any token > in "", line 207, column 23 > > I have pasted the contents of hpc.yaml that gives the error here -> > http://fpaste.org/139239/, this is an amended template from that > larsks pointed me to. > > Any insight on any of the above would be great > > -- > Arif Ali > > IRC: arif-ali at freenode > LinkedIn: http://uk.linkedin.com/in/arifali Hi, If you can see the example here: http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::ResourceGroup If you give it a static name as a prefix it will pass validation. - -- Best Regards, Amit. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUMg8bAAoJEJl/s+KmzM9pYdcH/2wpjxYRaHI0KsTyLyFVDtR+ ca+s56z7svRCrul01tKLczNVwHgRO5BMT3VnWbzD2ABWy41O7BosfCCQZjRF5SjL UeqgEWtAWfUyZbYez2av8cwf/J19sgE4FhvY88SC9mjR2JlB+krqWV/3EXxRiGDS WfAikniAmmuhfRgTLpPBbguClHPdfHMHjCJcr+DmDzke5kuQc2uwLjcrMrqKOy/q z/IyyafG6UOxxEWdkv9eYG7A9jHGCf9as0Mv8kelhTac+r3hS9fXUFM4vNBBSj7E Ygd5QPjytpjaTq7mm6JHypfYi/lGKlVJAkQoSKtohjTSspon1yEYJNxoxXNtKAk= =Hx4a -----END PGP SIGNATURE----- From mail at arif-ali.co.uk Mon Oct 6 13:40:43 2014 From: mail at arif-ali.co.uk (Arif Ali) Date: Mon, 06 Oct 2014 14:40:43 +0100 Subject: [Rdo-list] Heat in RDO Juno M3 In-Reply-To: <20141006064011.15122768@augol-pc.redhat.com> References: <20141006064011.15122768@augol-pc.redhat.com> Message-ID: <54329BDB.70301@arif-ali.co.uk> On 06/10/14 04:40, Amit Ugol wrote: > On Sat, 4 Oct 2014 23:20:18 +0100 > Arif Ali wrote: > >> Hi all, >> >> I have been trying a few things in heat on Juno over the last few >> days, and thanks to larsks on IRC, I managed to get really far. I >> have encountered 2 problems >> >> 1) The package heat-cfntools is no longer available in either of the >> rdo repository or epel for el7, It was available for el6. How best >> can we get hold of this package for CentOS 7. Or in-fact do we do the >> cfn-signal in a different way, and we no longer need to use this >> command? >> >> 2) I have been trying to to give unique names/numbers to hosts that >> are created through the "OS::Heat::ResourceGroup" resource, this >> supposedly has a feature where we can use %index% to add unique >> numbers to any of the variables. But this fails to work with the >> following error. >> >> Error parsing template file:///root/hpc.yaml while scanning for the >> next token >> found character that cannot start any token >> in "", line 207, column 23 >> >> I have pasted the contents of hpc.yaml that gives the error here -> >> http://fpaste.org/139239/, this is an amended template from that >> larsks pointed me to. >> >> Any insight on any of the above would be great >> >> -- >> Arif Ali >> >> IRC: arif-ali at freenode >> LinkedIn: http://uk.linkedin.com/in/arifali > Hi, > If you can see the example here: http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Heat::ResourceGroup > If you give it a static name as a prefix it will pass validation. > > - -- > Best Regards, > > Amit. > Thanks Amit, I did look at that example numerous times, but maybe I was approaching it incorrectly by forwarding the index name as a parameter to the resource I just took a slightly different approach now, where I am now giving the hostname to the resource, rather than forwarding the index itself. Is it possible do to regular expressions similar to perl, such that I can name them compute01 instead of compute1, which is what is being done. i.e. also be able to some kind of mathematical calculations according to the index Also pointers on point 1 would be great as well if anyone has any? thanks in advance Arif Ali IRC: arif-ali at freenode LinkedIn: http://uk.linkedin.com/in/arifali From lars at redhat.com Mon Oct 6 14:37:13 2014 From: lars at redhat.com (Lars Kellogg-Stedman) Date: Mon, 6 Oct 2014 10:37:13 -0400 Subject: [Rdo-list] Heat in RDO Juno M3 In-Reply-To: References: Message-ID: <20141006143713.GB7311@redhat.com> On Sat, Oct 04, 2014 at 11:20:18PM +0100, Arif Ali wrote: > 1) The package heat-cfntools is no longer available in either of the rdo > repository or epel for el7, It was available for el6. How best can we get > hold of this package for CentOS 7. Or in-fact do we do the cfn-signal in a > different way, and we no longer need to use this command? You have always been able to use `curl` instead of `cfn-signal`. There are examples of that in the documentation. > Error parsing template file:///root/hpc.yaml while scanning for the next > token > found character that cannot start any token > in "", line 207, column 23 I think that may suggest that you need to quote that value: index_name: "%index%" The '%' sign introduces a YAML "directive" if used outside of quotes. -- Lars Kellogg-Stedman | larsks @ {freenode,twitter,github} Cloud Engineering / OpenStack | http://blog.oddbit.com/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From rbowen at redhat.com Mon Oct 6 14:54:04 2014 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 06 Oct 2014 10:54:04 -0400 Subject: [Rdo-list] [Rdo-newsletter] October 2014 RDO Community Newsletter Message-ID: <5432AD0C.3010206@redhat.com> Thanks again for being part of the RDO community. Here's some of what's been happening in RDO, and OpenStack in general, over the last month. OpenStack User Survey Today is the very last day to participate in the OpenStack User Survey. This survey is conducted twice a year, immediately before the OpenStack Summit, which judges statistics about deployments of OpenStack - what storage back ends are being used, what platforms are deployed on, the size of clouds running on OpenStack, and so on. It's important that you take the survey, as it influences the direction of the project, as well as how corporations shape their product offerings around OpenStack. Take the survey at openstack.org/user-survey The deadline for participation is tomorrow - Tuesday, October 7th. Hangouts On September 5th, Lars Kellogg-Stedman gave an excellent hangout on deploying services with Heat. You can watch this on YouTube at https://plus.google.com/events/c9u4sjn7ksb8jrmma7vd25aok94 The #openstack-heat channel, on Freenode, is the right place to go if you have questions about Heat. And, #RDO is a good place for other questions related to OpenStack on CentOS, RHEL, or Fedora. We expect to have another hangout later this month, but the details are still being worked out. Watch the rdo-list mailing list, and http://openstack.redhat.com/Hangouts for details as they become available. Meetups Each week, we post a list of upcoming Meetups to the RDO-list mailing list - http://www.redhat.com/mailman/listinfo/rdo-list - and they also get added to the Events page - https://openstack.redhat.com/Events If you're speaking at a meetup or hangout of some kind, please let me know (rbowen at redhat.com) so that we can help you get the word out. If you're interested in starting a meetup in an area that doesn't have any kind of user group, there's some suggestions on the new page at https://openstack.redhat.com/Organize-a-meetup And if you attend an OpenStack meetup, please consider writing it up in a blog post or mailing list post, so that we can help get the word out about these meetups, and continue to build the OpenStack user community. Conferences There's several big events coming up where you can learn more about OpenStack and RDO, particularly if you're in Europe. Next week, LinuxCon/CloudOpen will be held in Dusseldorf, Germany, featuring a number of talks about OpenStack: What's now in OpenStack Juno - http://sched.co/1xnFhZc Hands On Trove - http://sched.co/1yFfJDc Open Storage in the Enterprise with GlusterFS and Ceph - http://sched.co/Xnt6wB KVM, OpenStack, and the Open Cloud - http://sched.co/1yGhznn NFV for Beginners - http://sched.co/Xn5ZlL Location-Aware Distributed Virtual Disk Storage For OpenStack - http://sched.co/1sXUnl4 ... and many others. This conference is just going to be packed with great OpenStack content, and we'll be there at the Red Hat booth if you have any questions about RDO. We look forward to seeing you there. Register at http://events.linuxfoundation.org/events/linuxcon-europe/attend/register And next month, in Paris, is the OpenStack Kilo Summit. This is *the* place to go for OpenStack content, with a whole week of technical sessions, and the design summit for the next iteration of the OpenStack software. You can find out more about the OpenStack Summit at http://openstack.org/summit If you're in North America, you may want to wait for the OpenStack Summit North America, which was just announced last week. It will be held in Vancouver, B.C., Canada, May 18-22. Details are not yet available, but you can watch the page at https://www.openstack.org/summit/vancouver-2015/ to find out details as they become available. Blog posts With OpenStack Juno in Feature Freeze, coming up to the release on October 16th - https://wiki.openstack.org/wiki/Juno_Release_Schedule - the OpenStack engineers at Red Hat have been writing fairly prolifically, and you can see some of those recent blog posts on the RDO blog: Week of September 1 - https://openstack.redhat.com/forum/discussion/983/rdo-blog-roundup-week-of-september-1 Week of September 8 - https://openstack.redhat.com/forum/discussion/984/blog-roundup-week-of-september-8-2014 Week of September 15 - https://openstack.redhat.com/forum/discussion/986/blog-roundup-week-of-september-15-2014 Week of September 22 - https://openstack.redhat.com/forum/discussion/987/blog-roundup-week-of-september-22-2014 For the latest blog posts about OpenStack, don't forget to follow the OpenStack Planet at http://planet.openstack.org/ I'd particularly like to recommend Thierry Carrez's excellent article "#1 OpenStack Contributor: All of Us" at http://ttx.re/largest-openstack-contributor.html More than anything, we want *you* to participate in OpenStack, and to do what's necessary to help you do that. Please join us on this exciting journey. In Closing ... Once again, you can always keep up to date a variety of ways: * Follow us on Twitter - http://twitter.com/rdocommunity * Google+ - http://tm3.org/rdogplus * Facebook - http://facebook.com/rdocommunity * rdo-list mailing list - http://www.redhat.com/mailman/listinfo/rdo-list * This newsletter - http://www.redhat.com/mailman/listinfo/rdo-newsletter * RDO Q&A - http://ask.openstack.org/ * IRC - #rdo on Freenode.irc.net Thanks again for being part of the RDO community! -- Rich Bowen, OpenStack Community Liaison rbowen at redhat.com http://openstack.redhat.com _______________________________________________ Rdo-newsletter mailing list Rdo-newsletter at redhat.com https://www.redhat.com/mailman/listinfo/rdo-newsletter From zbitter at redhat.com Mon Oct 6 15:55:15 2014 From: zbitter at redhat.com (Zane Bitter) Date: Mon, 06 Oct 2014 11:55:15 -0400 Subject: [Rdo-list] Heat in RDO Juno M3 In-Reply-To: References: Message-ID: <5432BB63.2020602@redhat.com> On 04/10/14 18:20, Arif Ali wrote: > Hi all, > > I have been trying a few things in heat on Juno over the last few days, and > thanks to larsks on IRC, I managed to get really far. I have encountered 2 > problems > > 1) The package heat-cfntools is no longer available in either of the rdo > repository or epel for el7, It was available for el6. How best can we get > hold of this package for CentOS 7. Or in-fact do we do the cfn-signal in a > different way, and we no longer need to use this command? > > 2) I have been trying to to give unique names/numbers to hosts that are > created through the "OS::Heat::ResourceGroup" resource, this supposedly has > a feature where we can use %index% to add unique numbers to any of the > variables. But this fails to work with the following error. > > Error parsing template file:///root/hpc.yaml while scanning for the next > token > found character that cannot start any token > in "", line 207, column 23 > > I have pasted the contents of hpc.yaml that gives the error here -> > http://fpaste.org/139239/, this is an amended template from that larsks > pointed me to. Basically, for what are no doubt boring technical reasons, that's not valid YAML. The problem, as the error message says, is the initial %. Enclose it in quotes and it will do what you want: index_name: "%index%" cheers, Zane. > Any insight on any of the above would be great > > -- > Arif Ali > > IRC: arif-ali at freenode > LinkedIn: http://uk.linkedin.com/in/arifali > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > From rdo-info at redhat.com Mon Oct 6 16:48:43 2014 From: rdo-info at redhat.com (RDO Forum) Date: Mon, 6 Oct 2014 16:48:43 +0000 Subject: [Rdo-list] [RDO] Blog Roundup, week of September 29, 2014 Message-ID: <00000148e65cee62-a5721b24-e720-48da-96fe-35b5401efb4a-000000@email.amazonses.com> rbowen started a discussion. Blog Roundup, week of September 29, 2014 --- Follow the link below to check it out: https://openstack.redhat.com/forum/discussion/988/blog-roundup-week-of-september-29-2014 Have a great day! From rbowen at redhat.com Mon Oct 6 16:50:07 2014 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 06 Oct 2014 12:50:07 -0400 Subject: [Rdo-list] Final reminder: The deadline for the OpenStack User Survey is tomorrow Message-ID: <5432C83F.2000606@redhat.com> Final reminder: The deadline for the OpenStack User Survey is tomorrow. http://openstack.org/user-survey Please consider setting aside 10 minutes to do this today if you haven't already done so. Thanks! --Rich -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From ak at cloudssky.com Mon Oct 6 18:37:21 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Mon, 6 Oct 2014 20:37:21 +0200 Subject: [Rdo-list] Heat Docker Plugin configuration on Juno Message-ID: Hello together, I'm trying to discover how to get the Heat Docker plugin configured on Juno with some inspirations from Lars blogs about Docker Plugin for OpenStack Heat . What I did was (on CentOS 7): cloned the proposed/juno branch from github: $ git clone -b proposed/juno https://github.com/openstack/heat.git $ cd heat $ mkdir /usr/lib/heat $ cp -r contrib/heat_docker/heat_docker/ /usr/lib/heat/ $ vi /etc/heat/heat.conf and set: plugin_dirs=/var/lib/heat/heat_docker $ systemctl restart openstack-heat-engine but by running: $ heat resource-type-list | grep Docker it doesn't give me the desired output: DockerInc::Docker::Container Any ideas? Thanks! -Arash -------------- next part -------------- An HTML attachment was scrubbed... URL: From jpeeler at redhat.com Mon Oct 6 18:51:51 2014 From: jpeeler at redhat.com (Jeff Peeler) Date: Mon, 06 Oct 2014 14:51:51 -0400 Subject: [Rdo-list] Heat in RDO Juno M3 In-Reply-To: References: Message-ID: <5432E4C7.1090000@redhat.com> On 10/04/2014 06:20 PM, Arif Ali wrote: > Hi all, > > I have been trying a few things in heat on Juno over the last few days, and > thanks to larsks on IRC, I managed to get really far. I have encountered 2 > problems > > 1) The package heat-cfntools is no longer available in either of the rdo > repository or epel for el7, It was available for el6. How best can we get > hold of this package for CentOS 7. Or in-fact do we do the cfn-signal in a > different way, and we no longer need to use this command? This is on its way to being corrected. You can in the meantime grab the packages here: https://copr.fedoraproject.org/coprs/jruzicka/rdo-juno-epel-7/build/51644/ For informational purposes, having heat-cfntools in el6 was a mistake. So for epel-7 the mistake was corrected and heat-cfntools is shipped in RDO. Note as mentioned elsewhere in the thread that curl can be used as a substitute. Jeff From rbowen at rcbowen.com Mon Oct 6 20:55:46 2014 From: rbowen at rcbowen.com (Rich Bowen) Date: Mon, 06 Oct 2014 16:55:46 -0400 Subject: [Rdo-list] RDO-related Meetups in the coming week (October 6, 2014) Message-ID: <543301D2.8030400@rcbowen.com> The following are the meetups I'm aware of in the coming week where RDO enthusiasts will be gathering. If you know of others, please let me know, and/or add them to http://openstack.redhat.com/Events If you attend any of these meetups, please take pictures, and send me some. If you blog about the events (and you should), please send me that, too. * Tuesday, October 7th, OpenStack 101@ Geekdom, San Antonio, TX - http://www.meetup.com/SA-Open-Stackers/events/207829552/ * Wednesday, October 8th, IBM OpenStack Lightning Talks, New York, NY - http://www.meetup.com/OpenStack-New-York-Meetup/events/206618432/ * Wednesday, October 8th, From Nova-Network to Neutron and Beyond: A Look at OpenStack Networking, Austin, TX - http://www.meetup.com/OpenStack-Austin/events/207255882/ * Wednesday, October 8th, Project Atomic, Clayton, MO - http://www.meetup.com/Docker-St-Louis/events/210326372/ * Wednesday, October 8th, Oct Meetup - Serving Big Data Applications with an OpenStack environment, Cambridge, MA - http://www.meetup.com/Openstack-Boston/events/207266652/ * Tuesday, October 14th, What is Ceph and why do I care? Fort Collins, CO - http://www.meetup.com/OpenStack-Colorado/events/210326972/ * October 13-15, LinuxCon Europe, Dusseldorf, Germany - http://events.linuxfoundation.org/events/linuxcon-europe -- Rich Bowen - rbowen at rcbowen.com - @rbowen http://apachecon.com/ - @apachecon -------------- next part -------------- An HTML attachment was scrubbed... URL: From mail at arif-ali.co.uk Mon Oct 6 21:08:49 2014 From: mail at arif-ali.co.uk (Arif Ali) Date: Mon, 06 Oct 2014 22:08:49 +0100 Subject: [Rdo-list] Heat in RDO Juno M3 In-Reply-To: <20141006143713.GB7311@redhat.com> References: <20141006143713.GB7311@redhat.com> Message-ID: <543304E1.4000205@arif-ali.co.uk> On 06/10/14 15:37, Lars Kellogg-Stedman wrote: > On Sat, Oct 04, 2014 at 11:20:18PM +0100, Arif Ali wrote: >> 1) The package heat-cfntools is no longer available in either of the rdo >> repository or epel for el7, It was available for el6. How best can we get >> hold of this package for CentOS 7. Or in-fact do we do the cfn-signal in a >> different way, and we no longer need to use this command? > You have always been able to use `curl` instead of `cfn-signal`. > There are examples of that in the documentation. hmm, I think that's a RTFM for me, as I was looking at your example; thanks for the pointers again ;) I will look that up >> Error parsing template file:///root/hpc.yaml while scanning for the next >> token >> found character that cannot start any token >> in "", line 207, column 23 > I think that may suggest that you need to quote that value: > > index_name: "%index%" > > The '%' sign introduces a YAML "directive" if used outside of quotes. > Perfect, that works. I tried this earlier, but I was doing something wrong in the template that was included as part of the hpc.yaml. need to test 1 thing at a time ;) As a side question, is there a better way than doing the following to concatenate a string with a paramater? {"Fn::Join" : ["",["compute", { get_param: index_name }]]} Arif Ali IRC: arif-ali at freenode LinkedIn: http://uk.linkedin.com/in/arifali From lars at redhat.com Tue Oct 7 00:21:32 2014 From: lars at redhat.com (Lars Kellogg-Stedman) Date: Mon, 6 Oct 2014 20:21:32 -0400 Subject: [Rdo-list] Heat in RDO Juno M3 In-Reply-To: <543304E1.4000205@arif-ali.co.uk> References: <20141006143713.GB7311@redhat.com> <543304E1.4000205@arif-ali.co.uk> Message-ID: <20141007002132.GB21633@redhat.com> On Mon, Oct 06, 2014 at 10:08:49PM +0100, Arif Ali wrote: > As a side question, is there a better way than doing the following to > concatenate a string with a paramater? > > {"Fn::Join" : ["",["compute", { get_param: index_name }]]} I don't think so. Newer versions of heat support a list_join function, but it works pretty much the same way: http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#list-join -- Lars Kellogg-Stedman | larsks @ {freenode,twitter,github} Cloud Engineering / OpenStack | http://blog.oddbit.com/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From ak at cloudssky.com Tue Oct 7 20:51:27 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Tue, 7 Oct 2014 22:51:27 +0200 Subject: [Rdo-list] Heat Docker Plugin configuration on Juno In-Reply-To: References: Message-ID: Moved /var/lib/heat/heat_docker to /var/lib/heat/docker/docker and changed the plugin_dirs=/var/lib/heat/docker/ and restarted openstack-heat-engine and it works now: [root at controller heat(keystone_admin)]# heat resource-type-list | grep Docker | DockerInc::Docker::Container | But still don't understand why my first config didn't work. On Mon, Oct 6, 2014 at 8:37 PM, Arash Kaffamanesh wrote: > Hello together, > > I'm trying to discover how to get the Heat Docker plugin configured on > Juno with some inspirations from Lars blogs about Docker Plugin for > OpenStack Heat > . > What I did was (on CentOS 7): > > cloned the proposed/juno branch from github: > > $ git clone -b proposed/juno https://github.com/openstack/heat.git > $ cd heat > $ mkdir /usr/lib/heat > $ cp -r contrib/heat_docker/heat_docker/ /usr/lib/heat/ > $ vi /etc/heat/heat.conf > > and set: > > plugin_dirs=/var/lib/heat/heat_docker > > $ systemctl restart openstack-heat-engine > > but by running: > > $ heat resource-type-list | grep Docker > > it doesn't give me the desired output: > > DockerInc::Docker::Container > > Any ideas? > > Thanks! > -Arash > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ak at cloudssky.com Thu Oct 9 11:50:15 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Thu, 9 Oct 2014 13:50:15 +0200 Subject: [Rdo-list] RDO-related Meetups in the coming week (October 6, 2014) In-Reply-To: <543301D2.8030400@rcbowen.com> References: <543301D2.8030400@rcbowen.com> Message-ID: Hi Rich, On October 20th there is this OpenStack Meetup in Frankfurt / Germany: http://www.meetup.com/OpenStack-MeetUp-Frankfurt/events/194344152/ And I'm going to have a talk about Docker On OpenStack (RDO Juno M3 Release) and its eCosystem. The final agenda will be announced next week. There is another OpenStack Meetup in Cologne which is organized by me, the OpenStack X Cologne Meetup Group: http://www.meetup.com/OpenStack-X/ Our next meetup will be in December and the agenda is being discussed on our meetup page and I'm planing to provide an hands on workshop for RDO Packstack and Foreman and possibly live stream the session as an hangout. Thanks, -Arash On Mon, Oct 6, 2014 at 10:55 PM, Rich Bowen wrote: > The following are the meetups I'm aware of in the coming week where RDO > enthusiasts will be gathering. If you know of others, please let me know, > and/or add them to http://openstack.redhat.com/Events > > If you attend any of these meetups, please take pictures, and send me > some. If you blog about the events (and you should), please send me that, > too. > > * Tuesday, October 7th, OpenStack 101@ Geekdom, San Antonio, TX - > http://www.meetup.com/SA-Open-Stackers/events/207829552/ > > * Wednesday, October 8th, IBM OpenStack Lightning Talks, New York, NY - > http://www.meetup.com/OpenStack-New-York-Meetup/events/206618432/ > > * Wednesday, October 8th, From Nova-Network to Neutron and Beyond: A Look > at OpenStack Networking, Austin, TX - > http://www.meetup.com/OpenStack-Austin/events/207255882/ > > * Wednesday, October 8th, Project Atomic, Clayton, MO - > http://www.meetup.com/Docker-St-Louis/events/210326372/ > > * Wednesday, October 8th, Oct Meetup - Serving Big Data Applications with > an OpenStack environment, Cambridge, MA - > http://www.meetup.com/Openstack-Boston/events/207266652/ > > * Tuesday, October 14th, What is Ceph and why do I care? Fort Collins, CO > - http://www.meetup.com/OpenStack-Colorado/events/210326972/ > > * October 13-15, LinuxCon Europe, Dusseldorf, Germany - > http://events.linuxfoundation.org/events/linuxcon-europe > > > -- > Rich Bowen - rbowen at rcbowen.com - @rbowenhttp://apachecon.com/ - @apachecon > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonas.hagberg at scilifelab.se Thu Oct 9 13:19:26 2014 From: jonas.hagberg at scilifelab.se (Jonas Hagberg) Date: Thu, 9 Oct 2014 15:19:26 +0200 Subject: [Rdo-list] RDO-related Meetups in the coming week (October 6, 2014) In-Reply-To: References: <543301D2.8030400@rcbowen.com> Message-ID: Any meetup around the Openstack Summit in Paris? -- Jonas Hagberg BILS - Bioinformatics Infrastructure for Life Sciences - http://bils.se e-mail: jonas.hagberg at bils.se, jonas.hagberg at scilifelab.se phone: +46-(0)70 6683869 address: SciLifeLab, Box 1031, 171 21 Solna, Sweden On 9 October 2014 13:50, Arash Kaffamanesh wrote: > Hi Rich, > > On October 20th there is this OpenStack Meetup in Frankfurt / Germany: > http://www.meetup.com/OpenStack-MeetUp-Frankfurt/events/194344152/ > And I'm going to have a talk about Docker On OpenStack (RDO Juno M3 > Release) and its eCosystem. > The final agenda will be announced next week. > > There is another OpenStack Meetup in Cologne which is organized by me, the > OpenStack X Cologne Meetup Group: > http://www.meetup.com/OpenStack-X/ > > Our next meetup will be in December and the agenda is being discussed on > our meetup page and I'm planing to provide an hands on workshop for RDO > Packstack and Foreman and possibly live stream the session as an hangout. > > Thanks, > -Arash > > > On Mon, Oct 6, 2014 at 10:55 PM, Rich Bowen wrote: > >> The following are the meetups I'm aware of in the coming week where RDO >> enthusiasts will be gathering. If you know of others, please let me know, >> and/or add them to http://openstack.redhat.com/Events >> >> If you attend any of these meetups, please take pictures, and send me >> some. If you blog about the events (and you should), please send me that, >> too. >> >> * Tuesday, October 7th, OpenStack 101@ Geekdom, San Antonio, TX - >> http://www.meetup.com/SA-Open-Stackers/events/207829552/ >> >> * Wednesday, October 8th, IBM OpenStack Lightning Talks, New York, NY - >> http://www.meetup.com/OpenStack-New-York-Meetup/events/206618432/ >> >> * Wednesday, October 8th, From Nova-Network to Neutron and Beyond: A Look >> at OpenStack Networking, Austin, TX - >> http://www.meetup.com/OpenStack-Austin/events/207255882/ >> >> * Wednesday, October 8th, Project Atomic, Clayton, MO - >> http://www.meetup.com/Docker-St-Louis/events/210326372/ >> >> * Wednesday, October 8th, Oct Meetup - Serving Big Data Applications with >> an OpenStack environment, Cambridge, MA - >> http://www.meetup.com/Openstack-Boston/events/207266652/ >> >> * Tuesday, October 14th, What is Ceph and why do I care? Fort Collins, CO >> - http://www.meetup.com/OpenStack-Colorado/events/210326972/ >> >> * October 13-15, LinuxCon Europe, Dusseldorf, Germany - >> http://events.linuxfoundation.org/events/linuxcon-europe >> >> >> -- >> Rich Bowen - rbowen at rcbowen.com - @rbowenhttp://apachecon.com/ - @apachecon >> >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> >> > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at rcbowen.com Thu Oct 9 13:20:28 2014 From: rbowen at rcbowen.com (Rich Bowen) Date: Thu, 09 Oct 2014 09:20:28 -0400 Subject: [Rdo-list] RDO-related Meetups in the coming week (October 6, 2014) In-Reply-To: References: <543301D2.8030400@rcbowen.com> Message-ID: <54368B9C.3030307@rcbowen.com> On 10/09/2014 07:50 AM, Arash Kaffamanesh wrote: > Hi Rich, > > On October 20th there is this OpenStack Meetup in Frankfurt / Germany: > http://www.meetup.com/OpenStack-MeetUp-Frankfurt/events/194344152/ > And I'm going to have a talk about Docker On OpenStack (RDO Juno M3 > Release) and its eCosystem. > The final agenda will be announced next week. > > There is another OpenStack Meetup in Cologne which is organized by me, > the OpenStack X Cologne Meetup Group: > http://www.meetup.com/OpenStack-X/ > > Our next meetup will be in December and the agenda is being discussed > on our meetup page and I'm planing to provide an hands on workshop for > RDO Packstack and Foreman and possibly live stream the session as an > hangout. Thanks. I'm adding these to the events page, and look forward to more information about the December event. -- Rich Bowen - rbowen at rcbowen.com - @rbowen http://apachecon.com/ - @apachecon From sgordon at redhat.com Thu Oct 9 15:49:21 2014 From: sgordon at redhat.com (Steve Gordon) Date: Thu, 9 Oct 2014 11:49:21 -0400 (EDT) Subject: [Rdo-list] RDO-related Meetups in the coming week (October 6, 2014) In-Reply-To: References: <543301D2.8030400@rcbowen.com> Message-ID: <65808721.35812767.1412869761612.JavaMail.zimbra@redhat.com> I think there was some discussion about having an RDO BoF session in Paris in an earlier thread? ----- Original Message ----- > From: "Jonas Hagberg" > To: "Arash Kaffamanesh" > Cc: "Rich Bowen" , rdo-list at redhat.com > Sent: Thursday, October 9, 2014 9:19:26 AM > Subject: Re: [Rdo-list] RDO-related Meetups in the coming week (October 6, 2014) > > Any meetup around the Openstack Summit in Paris? > > -- > Jonas Hagberg > BILS - Bioinformatics Infrastructure for Life Sciences - http://bils.se > e-mail: jonas.hagberg at bils.se, jonas.hagberg at scilifelab.se > phone: +46-(0)70 6683869 > address: SciLifeLab, Box 1031, 171 21 Solna, Sweden > > On 9 October 2014 13:50, Arash Kaffamanesh wrote: > > > Hi Rich, > > > > On October 20th there is this OpenStack Meetup in Frankfurt / Germany: > > http://www.meetup.com/OpenStack-MeetUp-Frankfurt/events/194344152/ > > And I'm going to have a talk about Docker On OpenStack (RDO Juno M3 > > Release) and its eCosystem. > > The final agenda will be announced next week. > > > > There is another OpenStack Meetup in Cologne which is organized by me, the > > OpenStack X Cologne Meetup Group: > > http://www.meetup.com/OpenStack-X/ > > > > Our next meetup will be in December and the agenda is being discussed on > > our meetup page and I'm planing to provide an hands on workshop for RDO > > Packstack and Foreman and possibly live stream the session as an hangout. > > > > Thanks, > > -Arash > > > > > > On Mon, Oct 6, 2014 at 10:55 PM, Rich Bowen wrote: > > > >> The following are the meetups I'm aware of in the coming week where RDO > >> enthusiasts will be gathering. If you know of others, please let me know, > >> and/or add them to http://openstack.redhat.com/Events > >> > >> If you attend any of these meetups, please take pictures, and send me > >> some. If you blog about the events (and you should), please send me that, > >> too. > >> > >> * Tuesday, October 7th, OpenStack 101@ Geekdom, San Antonio, TX - > >> http://www.meetup.com/SA-Open-Stackers/events/207829552/ > >> > >> * Wednesday, October 8th, IBM OpenStack Lightning Talks, New York, NY - > >> http://www.meetup.com/OpenStack-New-York-Meetup/events/206618432/ > >> > >> * Wednesday, October 8th, From Nova-Network to Neutron and Beyond: A Look > >> at OpenStack Networking, Austin, TX - > >> http://www.meetup.com/OpenStack-Austin/events/207255882/ > >> > >> * Wednesday, October 8th, Project Atomic, Clayton, MO - > >> http://www.meetup.com/Docker-St-Louis/events/210326372/ > >> > >> * Wednesday, October 8th, Oct Meetup - Serving Big Data Applications with > >> an OpenStack environment, Cambridge, MA - > >> http://www.meetup.com/Openstack-Boston/events/207266652/ > >> > >> * Tuesday, October 14th, What is Ceph and why do I care? Fort Collins, CO > >> - http://www.meetup.com/OpenStack-Colorado/events/210326972/ > >> > >> * October 13-15, LinuxCon Europe, Dusseldorf, Germany - > >> http://events.linuxfoundation.org/events/linuxcon-europe > >> > >> > >> -- > >> Rich Bowen - rbowen at rcbowen.com - @rbowenhttp://apachecon.com/ - > >> @apachecon > >> > >> > >> _______________________________________________ > >> Rdo-list mailing list > >> Rdo-list at redhat.com > >> https://www.redhat.com/mailman/listinfo/rdo-list > >> > >> > > > > _______________________________________________ > > Rdo-list mailing list > > Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -- Steve Gordon, RHCE Sr. Technical Product Manager, Red Hat Enterprise Linux OpenStack Platform From kchamart at redhat.com Thu Oct 9 16:43:31 2014 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Thu, 9 Oct 2014 18:43:31 +0200 Subject: [Rdo-list] RDO-related Meetups in the coming week (October 6, 2014) In-Reply-To: <65808721.35812767.1412869761612.JavaMail.zimbra@redhat.com> References: <543301D2.8030400@rcbowen.com> <65808721.35812767.1412869761612.JavaMail.zimbra@redhat.com> Message-ID: <20141009164331.GE18872@tesla.redhat.com> On Thu, Oct 09, 2014 at 11:49:21AM -0400, Steve Gordon wrote: > I think there was some discussion about having an RDO BoF session in > Paris in an earlier thread? Yes, started by Tim Bell on this thread - https://www.redhat.com/archives/rdo-list/2014-September/msg00141.html where he mentioned CERN would be interested in having EL6 support for Juno and was trying to understand the work involved. Also, here's Perry's response to that thread https://www.redhat.com/archives/rdo-list/2014-September/msg00142.html -- /kashyap > ----- Original Message ----- > > From: "Jonas Hagberg" > > To: "Arash Kaffamanesh" > > Cc: "Rich Bowen" , rdo-list at redhat.com > > Sent: Thursday, October 9, 2014 9:19:26 AM > > Subject: Re: [Rdo-list] RDO-related Meetups in the coming week (October 6, 2014) > > > > Any meetup around the Openstack Summit in Paris? > > > > -- > > Jonas Hagberg > > BILS - Bioinformatics Infrastructure for Life Sciences - http://bils.se > > e-mail: jonas.hagberg at bils.se, jonas.hagberg at scilifelab.se > > phone: +46-(0)70 6683869 > > address: SciLifeLab, Box 1031, 171 21 Solna, Sweden > > > > On 9 October 2014 13:50, Arash Kaffamanesh wrote: > > > > > Hi Rich, > > > > > > On October 20th there is this OpenStack Meetup in Frankfurt / Germany: > > > http://www.meetup.com/OpenStack-MeetUp-Frankfurt/events/194344152/ > > > And I'm going to have a talk about Docker On OpenStack (RDO Juno M3 > > > Release) and its eCosystem. > > > The final agenda will be announced next week. > > > > > > There is another OpenStack Meetup in Cologne which is organized by me, the > > > OpenStack X Cologne Meetup Group: > > > http://www.meetup.com/OpenStack-X/ > > > > > > Our next meetup will be in December and the agenda is being discussed on > > > our meetup page and I'm planing to provide an hands on workshop for RDO > > > Packstack and Foreman and possibly live stream the session as an hangout. > > > > > > Thanks, > > > -Arash > > > > > > > > > On Mon, Oct 6, 2014 at 10:55 PM, Rich Bowen wrote: > > > > > >> The following are the meetups I'm aware of in the coming week where RDO > > >> enthusiasts will be gathering. If you know of others, please let me know, > > >> and/or add them to http://openstack.redhat.com/Events > > >> > > >> If you attend any of these meetups, please take pictures, and send me > > >> some. If you blog about the events (and you should), please send me that, > > >> too. > > >> > > >> * Tuesday, October 7th, OpenStack 101@ Geekdom, San Antonio, TX - > > >> http://www.meetup.com/SA-Open-Stackers/events/207829552/ > > >> > > >> * Wednesday, October 8th, IBM OpenStack Lightning Talks, New York, NY - > > >> http://www.meetup.com/OpenStack-New-York-Meetup/events/206618432/ > > >> > > >> * Wednesday, October 8th, From Nova-Network to Neutron and Beyond: A Look > > >> at OpenStack Networking, Austin, TX - > > >> http://www.meetup.com/OpenStack-Austin/events/207255882/ > > >> > > >> * Wednesday, October 8th, Project Atomic, Clayton, MO - > > >> http://www.meetup.com/Docker-St-Louis/events/210326372/ > > >> > > >> * Wednesday, October 8th, Oct Meetup - Serving Big Data Applications with > > >> an OpenStack environment, Cambridge, MA - > > >> http://www.meetup.com/Openstack-Boston/events/207266652/ > > >> > > >> * Tuesday, October 14th, What is Ceph and why do I care? Fort Collins, CO > > >> - http://www.meetup.com/OpenStack-Colorado/events/210326972/ > > >> > > >> * October 13-15, LinuxCon Europe, Dusseldorf, Germany - > > >> http://events.linuxfoundation.org/events/linuxcon-europe > > >> From rbowen at rcbowen.com Thu Oct 9 17:44:16 2014 From: rbowen at rcbowen.com (Rich Bowen) Date: Thu, 09 Oct 2014 13:44:16 -0400 Subject: [Rdo-list] RDO-related Meetups in the coming week (October 6, 2014) In-Reply-To: <20141009164331.GE18872@tesla.redhat.com> References: <543301D2.8030400@rcbowen.com> <65808721.35812767.1412869761612.JavaMail.zimbra@redhat.com> <20141009164331.GE18872@tesla.redhat.com> Message-ID: <5436C970.9060908@rcbowen.com> On 10/09/2014 12:43 PM, Kashyap Chamarthy wrote: > On Thu, Oct 09, 2014 at 11:49:21AM -0400, Steve Gordon wrote: >> I think there was some discussion about having an RDO BoF session in >> Paris in an earlier thread? > Yes, started by Tim Bell on this thread - > > https://www.redhat.com/archives/rdo-list/2014-September/msg00141.html > > where he mentioned CERN would be interested in having EL6 support for > Juno and was trying to understand the work involved. > > Also, here's Perry's response to that thread > > https://www.redhat.com/archives/rdo-list/2014-September/msg00142.html Yeah ... I made a note to find out what's involved in organizing a BOF, and kind of dropped that. I'll go do that now. -- Rich Bowen - rbowen at rcbowen.com - @rbowen http://apachecon.com/ - @apachecon From jkirby at redhat.com Thu Oct 9 17:57:26 2014 From: jkirby at redhat.com (Joe Kirby) Date: Thu, 09 Oct 2014 13:57:26 -0400 Subject: [Rdo-list] Install using instructions at https://openstack.redhat.com/Deploying_RDO_using_Foreman Message-ID: <5436CC86.8080508@redhat.com> I am trying to follow the instructions listed in the subject and can't get past the dependencies associated with 'yum install openstack-foreman-installer'. yum repolist _looks_ like it includes all the required stuff: base epel foreman foreman-plugins openstack-havana puppetlabs-deps puppetlabs-products rhel-x86_64-server-6 rhel-x86_64-server-6-rhscl-1 Any suggestions??? -- From rbowen at redhat.com Fri Oct 10 19:59:31 2014 From: rbowen at redhat.com (Rich Bowen) Date: Fri, 10 Oct 2014 15:59:31 -0400 Subject: [Rdo-list] RDO-related Meetups in the coming week (October 6, 2014) In-Reply-To: <5436C970.9060908@rcbowen.com> References: <543301D2.8030400@rcbowen.com> <65808721.35812767.1412869761612.JavaMail.zimbra@redhat.com> <20141009164331.GE18872@tesla.redhat.com> <5436C970.9060908@rcbowen.com> Message-ID: <54383AA3.2080505@redhat.com> On 10/09/2014 01:44 PM, Rich Bowen wrote: > > On 10/09/2014 12:43 PM, Kashyap Chamarthy wrote: >> On Thu, Oct 09, 2014 at 11:49:21AM -0400, Steve Gordon wrote: >>> I think there was some discussion about having an RDO BoF session in >>> Paris in an earlier thread? >> Yes, started by Tim Bell on this thread - >> >> https://www.redhat.com/archives/rdo-list/2014-September/msg00141.html >> >> where he mentioned CERN would be interested in having EL6 support for >> Juno and was trying to understand the work involved. >> >> Also, here's Perry's response to that thread >> >> https://www.redhat.com/archives/rdo-list/2014-September/msg00142.html > > Yeah ... I made a note to find out what's involved in organizing a > BOF, and kind of dropped that. I'll go do that now. So, the short answer is that there's not space/time for BOFs in the schedule. The longer answer is at http://lists.openstack.org/pipermail/community/2014-October/000909.html and looks more like "we're trying to figure out how to fit these into the schedule, but probably not this time." So if we can find a venue near the conference venue, that would be great. Finding a time when there's not something else going on would also be a challenge. -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From Arkady_Kanevsky at dell.com Fri Oct 10 21:00:03 2014 From: Arkady_Kanevsky at dell.com (Arkady_Kanevsky at dell.com) Date: Fri, 10 Oct 2014 16:00:03 -0500 Subject: [Rdo-list] RDO-related Meetups in the coming week (October 6, 2014) In-Reply-To: <54383AA3.2080505@redhat.com> References: <543301D2.8030400@rcbowen.com> <65808721.35812767.1412869761612.JavaMail.zimbra@redhat.com> <20141009164331.GE18872@tesla.redhat.com> <5436C970.9060908@rcbowen.com> <54383AA3.2080505@redhat.com> Message-ID: <336424C1A5A44044B29030055527AA7504A6DA3C77@AUSX7MCPS301.AMER.DELL.COM> So no meeting of RDO community in Paris? -----Original Message----- From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Rich Bowen Sent: Friday, October 10, 2014 3:00 PM To: rdo-list at redhat.com Subject: Re: [Rdo-list] RDO-related Meetups in the coming week (October 6, 2014) On 10/09/2014 01:44 PM, Rich Bowen wrote: > > On 10/09/2014 12:43 PM, Kashyap Chamarthy wrote: >> On Thu, Oct 09, 2014 at 11:49:21AM -0400, Steve Gordon wrote: >>> I think there was some discussion about having an RDO BoF session in >>> Paris in an earlier thread? >> Yes, started by Tim Bell on this thread - >> >> https://www.redhat.com/archives/rdo-list/2014-September/msg00141.html >> >> where he mentioned CERN would be interested in having EL6 support for >> Juno and was trying to understand the work involved. >> >> Also, here's Perry's response to that thread >> >> https://www.redhat.com/archives/rdo-list/2014-September/msg00142.html > > Yeah ... I made a note to find out what's involved in organizing a > BOF, and kind of dropped that. I'll go do that now. So, the short answer is that there's not space/time for BOFs in the schedule. The longer answer is at http://lists.openstack.org/pipermail/community/2014-October/000909.html and looks more like "we're trying to figure out how to fit these into the schedule, but probably not this time." So if we can find a venue near the conference venue, that would be great. Finding a time when there's not something else going on would also be a challenge. -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list From samsong8610 at gmail.com Sat Oct 11 03:58:14 2014 From: samsong8610 at gmail.com (sam song) Date: Sat, 11 Oct 2014 11:58:14 +0800 Subject: [Rdo-list] How does RDO package OpenStack RPM package? Message-ID: <5438AAD6.3030105@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, all: Our company want to provide a customized OpenStack platform, so we need to package some OpenStack components, and we want to keep the RPMs' name unique to ones in RDO release. Now we use python setup.py bdist_rpm to build the package, which is poor in packaging the same project into several RPMs. So, my question is belowing: 1, What method does RDO use to package OpenStack RPMs? python setup.py or rpmbuild 2, Are the packaging configurations open source? Where can I get them? Thanks Sam Song -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJUOKrWAAoJEPDWvv0r0XeRvnAH/iquU1l3FgyHm4aCsE7xG2P7 hAoH4E/+WDhlvT+cCiK20gCOUK3SKRQuZ0UkJhDiGKj0iTWmntCpQh91+Q9zRa3+ Z9kyUgEfZ9n+InxZB2krxAGx2tfz4pEgVStA3ORFaQttrPQvqJ7T88Nyrg1EzzUU hr57cGKqnh4vzThXtOMsRj16r6Zze5DfCJXBY2o6uwr9B5khrLBc11+KyITOymas U2VRQpfRKVjqiofkj5XwzpkKmL8L+m/Zc8Wu4JeF2fyXAoyLNmJD4Mkqv+RNQ1ML fPGuYFMl6wROyhX7q7f3SqGBqLEXK1YUJTOSCmgLM15iaJn/WkGtCGsk9agO/dU= =hrGg -----END PGP SIGNATURE----- From ihrachys at redhat.com Sat Oct 11 18:12:03 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Sat, 11 Oct 2014 20:12:03 +0200 Subject: [Rdo-list] How does RDO package OpenStack RPM package? In-Reply-To: <5438AAD6.3030105@gmail.com> References: <5438AAD6.3030105@gmail.com> Message-ID: <543972F3.6040508@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 11/10/14 05:58, sam song wrote: > > Hi, all: > > Our company want to provide a customized OpenStack platform, so we > need to package some OpenStack components, and we want to keep the > RPMs' name unique to ones in RDO release. Now we use python > setup.py bdist_rpm to build the package, which is poor in packaging > the same project into several RPMs. I wonder whether your needs can be solved as part of RDO. Do you need to apply some specific patches that are not included in upstream releases? > > So, my question is belowing: 1, What method does RDO use to package > OpenStack RPMs? python setup.py or rpmbuild RDO utilizes Koji and COPR services to build its packages. Meaning, we don't use bdist_rpm. > 2, Are the packaging configurations open source? Where can I get > them? Of course: that's Red Hat. Have you heard about Oracle Openstack Icehouse commercial offering? That one is based on top of RDO [0]. ;) Both packaging configuration [1] and repositories with downstream patches included on top of upstream releases [2] are available for anyone. Fork, reuse, contribute. BTW some of your questions are already answered in RDO FAQ [3]. [0]: https://openstack.redhat.com/forum/discussion/985/red-hat-welcomes-oracle-to-the-rdo-community [1]: http://pkgs.fedoraproject.org/cgit/openstack-neutron.git/ [2]: https://github.com/redhat-openstack [3]: https://openstack.redhat.com/Frequently_Asked_Questions I hope that helps, /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUOXLzAAoJEC5aWaUY1u57O0wH/AyFdTD/ELUeiDt3yj5o4N7+ Ce9ClSR/mFVHPhOwb+mrN7A2lwd7rX8+Znju6DgYEacBO/SRam4ueHjrWkdTxsxR Iox+QwpCNnlp1gz5hBWRwX23RWkmZQB5dblYK4T/0/+OlEEw1q5UCvpgTFQHzDL3 SqfhZcIb0AWJB0UjowMhNo4RBscWkTGAe3vmGmsAwLSUU36hhW3fvXeVZsLCTpx4 l9bcGQaI2RZswSsfIiveBRr4xOzO3j+SGdzaGfevBxW5XSZBsFgwddm1x9m1/G6k 1OJP+AMI9VWs1WSrSv8l1EhIMb8BR71bmhTAISifPDxmiyF0GbVtxIHmdjAp8xQ= =z2s7 -----END PGP SIGNATURE----- From samsong8610 at gmail.com Mon Oct 13 01:56:49 2014 From: samsong8610 at gmail.com (sam song) Date: Mon, 13 Oct 2014 09:56:49 +0800 Subject: [Rdo-list] How does RDO package OpenStack RPM package? In-Reply-To: <543972F3.6040508@redhat.com> References: <5438AAD6.3030105@gmail.com> <543972F3.6040508@redhat.com> Message-ID: <543B3161.2070003@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/12/2014 02:12 AM, Ihar Hrachyshka wrote: > On 11/10/14 05:58, sam song wrote: > >> Hi, all: > >> Our company want to provide a customized OpenStack platform, so >> we need to package some OpenStack components, and we want to keep >> the RPMs' name unique to ones in RDO release. Now we use python >> setup.py bdist_rpm to build the package, which is poor in >> packaging the same project into several RPMs. > > I wonder whether your needs can be solved as part of RDO. Do you > need to apply some specific patches that are not included in > upstream releases? > Yes, what I want to do is the same to RDO does, except the patches are different. > >> So, my question is belowing: 1, What method does RDO use to >> package OpenStack RPMs? python setup.py or rpmbuild > > RDO utilizes Koji and COPR services to build its packages. Meaning, > we don't use bdist_rpm. > >> 2, Are the packaging configurations open source? Where can I get >> them? > > Of course: that's Red Hat. Have you heard about Oracle Openstack > Icehouse commercial offering? That one is based on top of RDO [0]. > ;) > > Both packaging configuration [1] and repositories with downstream > patches included on top of upstream releases [2] are available for > anyone. Fork, reuse, contribute. > > BTW some of your questions are already answered in RDO FAQ [3]. > > [0]: > https://openstack.redhat.com/forum/discussion/985/red-hat-welcomes-oracle-to-the-rdo-community > > [1]: http://pkgs.fedoraproject.org/cgit/openstack-neutron.git/ > [2]: https://github.com/redhat-openstack [3]: > https://openstack.redhat.com/Frequently_Asked_Questions > > I hope that helps, /Ihar > > _______________________________________________ Rdo-list mailing > list Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > That's all information I want! Thank you very much. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJUOzFhAAoJEPDWvv0r0XeR6g0IAJ8/cptLkiG9tLORA7WO+Lld zW2Wilrrz4MyKOIsfqcyFxD8w8pKEdWpHaIt+IoG0LV4zY5h2Kw90MqN6Dmtv+pb oIslY1OqbN2c005bWpAn0CGuqnfhyQWMlWTfvj+CMxMMjd9VCbc0JtKRT/z3H7oT D89lhrd8iNE1fim4JC96l1AKs6ZEUYVGS/NMcEg5uAZMNnQlFgh14r/zZJabMCFz 7+FO/5/PTsMq9HpeRN0FiGgYYcOcW7injRw5AunlNLiR4ArQoHq+dFnmgnn62nGb GtcIDQXX8ot9q9NT86qYhDcrW9E5IuhlUNsG4egNOJNyGShIIlZX9uzEfMgEKlg= =BDjn -----END PGP SIGNATURE----- From apevec at gmail.com Mon Oct 13 08:41:17 2014 From: apevec at gmail.com (Alan Pevec) Date: Mon, 13 Oct 2014 10:41:17 +0200 Subject: [Rdo-list] How does RDO package OpenStack RPM package? In-Reply-To: <543B3161.2070003@gmail.com> References: <5438AAD6.3030105@gmail.com> <543972F3.6040508@redhat.com> <543B3161.2070003@gmail.com> Message-ID: > Yes, what I want to do is the same to RDO does, except the patches are > different. Which patches do you want to backport? Please be aware of the cost creating effectively a fork! We add only patches to help packaging, security fixes and total blockers. Otherwise it's vanilla upstream stable releases. It always pays off in the long run to work upstream and help merge patches there first. Cheers, Alan From rdo-info at redhat.com Mon Oct 13 10:35:04 2014 From: rdo-info at redhat.com (RDO Forum) Date: Mon, 13 Oct 2014 10:35:04 +0000 Subject: [Rdo-list] [RDO] Blog Roundup, week of October 6, 2014 Message-ID: <0000014909135dde-3493e802-87e8-43e4-9e3d-65c24193293b-000000@email.amazonses.com> rbowen started a discussion. Blog Roundup, week of October 6, 2014 --- Follow the link below to check it out: https://openstack.redhat.com/forum/discussion/989/blog-roundup-week-of-october-6-2014 Have a great day! From priteau at uchicago.edu Mon Oct 13 23:22:04 2014 From: priteau at uchicago.edu (Pierre Riteau) Date: Mon, 13 Oct 2014 18:22:04 -0500 Subject: [Rdo-list] How does RDO package OpenStack RPM package? In-Reply-To: <543972F3.6040508@redhat.com> References: <5438AAD6.3030105@gmail.com> <543972F3.6040508@redhat.com> Message-ID: I have noticed that the el6-havana branch of Nova [4] is 6-month old, while there were new OpenStack packages released last week (openstack-nova-2013.2.4-1.el6.src.rpm). Is [1] the source for the package build system or is there actually another repository internal to Red Hat? [4] http://pkgs.fedoraproject.org/cgit/openstack-nova.git/log/?h=el6-havana On 11 Oct 2014, at 13:12, Ihar Hrachyshka wrote: > Of course: that's Red Hat. Have you heard about Oracle Openstack > Icehouse commercial offering? That one is based on top of RDO [0]. ;) > > Both packaging configuration [1] and repositories with downstream > patches included on top of upstream releases [2] are available for > anyone. Fork, reuse, contribute. > > BTW some of your questions are already answered in RDO FAQ [3]. > > [0]: > https://openstack.redhat.com/forum/discussion/985/red-hat-welcomes-oracle-to-the-rdo-community > [1]: http://pkgs.fedoraproject.org/cgit/openstack-neutron.git/ > [2]: https://github.com/redhat-openstack > [3]: https://openstack.redhat.com/Frequently_Asked_Questions > > I hope that helps, > /Ihar -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihrachys at redhat.com Tue Oct 14 08:28:18 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Tue, 14 Oct 2014 10:28:18 +0200 Subject: [Rdo-list] How does RDO package OpenStack RPM package? In-Reply-To: References: <5438AAD6.3030105@gmail.com> <543972F3.6040508@redhat.com> Message-ID: <543CDEA2.4060301@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 14/10/14 01:22, Pierre Riteau wrote: > I have noticed that the el6-havana branch of Nova [4] is 6-month old, > while there were new OpenStack packages released last week > (openstack-nova-2013.2.4-1.el6.src.rpm). > Is [1] the source for the package build system or is there actually > another repository internal to Red Hat? > > [4] http://pkgs.fedoraproject.org/cgit/openstack-nova.git/log/?h=el6-havana I'm not a Nova guy, but AFAIK el6-* branches were retired and replaced by compound builds from f2* branches (f20 is Havana for fedora20, fedora19, and el6; f21 is Icehouse for fedora20, el6, and el7; and master for Juno for fedora-rawhide, fedora20, and el7). For Fedoras, we build packages in Koji, and we use COPR for EL[67]. AFAIK there are no internal Red Hat repositories for RDO. Obviously, we have internal repositories for RHOSP where we diverge a bit from upstream releases. /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUPN6iAAoJEC5aWaUY1u57pv4IAKv3VexvSDlbzy0b9KVSBk6n omJfFp7R3Yw6pKTrqImO2tgNQZR6vKJKr754bqqTI03ZtY32J/0UATc8c3rwoj7Z dBOJxiMEKQOcYqD+iva3pC5wnQw5BVLZ6WSsa2NV90zEN2PcNB2cFN77PBeAvia3 gYUKbt6PKc8nHsmXMbJwNLtkqQcY+QDd4J7yPhx6GOl6xhd8NVtVE79/zUyykzVi 3eAiALT2teIUcUCDByi4wrGrwwwtLfF3S9RArSZLdZxCxv6lw8PDnPyMsEW9B6qI jXWTA8zykg1zcCOoWiZMs/bxfE1RHcpLxLJyRnCdr6CEv6+tGvhDvgh1jL7msFY= =eWwc -----END PGP SIGNATURE----- From ihrachys at redhat.com Tue Oct 14 08:28:19 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Tue, 14 Oct 2014 10:28:19 +0200 Subject: [Rdo-list] How does RDO package OpenStack RPM package? In-Reply-To: References: <5438AAD6.3030105@gmail.com> <543972F3.6040508@redhat.com> Message-ID: <543CDEA3.6010709@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 14/10/14 01:22, Pierre Riteau wrote: > I have noticed that the el6-havana branch of Nova [4] is 6-month old, > while there were new OpenStack packages released last week > (openstack-nova-2013.2.4-1.el6.src.rpm). > Is [1] the source for the package build system or is there actually > another repository internal to Red Hat? > > [4] http://pkgs.fedoraproject.org/cgit/openstack-nova.git/log/?h=el6-havana I'm not a Nova guy, but AFAIK el6-* branches were retired and replaced by compound builds from f2* branches (f20 is Havana for fedora20, fedora19, and el6; f21 is Icehouse for fedora20, el6, and el7; and master for Juno for fedora-rawhide, fedora20, and el7). For Fedoras, we build packages in Koji, and we use COPR for EL[67]. AFAIK there are no internal Red Hat repositories for RDO. Obviously, we have internal repositories for RHOSP where we diverge a bit from upstream releases. /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUPN6iAAoJEC5aWaUY1u57pv4IAKv3VexvSDlbzy0b9KVSBk6n omJfFp7R3Yw6pKTrqImO2tgNQZR6vKJKr754bqqTI03ZtY32J/0UATc8c3rwoj7Z dBOJxiMEKQOcYqD+iva3pC5wnQw5BVLZ6WSsa2NV90zEN2PcNB2cFN77PBeAvia3 gYUKbt6PKc8nHsmXMbJwNLtkqQcY+QDd4J7yPhx6GOl6xhd8NVtVE79/zUyykzVi 3eAiALT2teIUcUCDByi4wrGrwwwtLfF3S9RArSZLdZxCxv6lw8PDnPyMsEW9B6qI jXWTA8zykg1zcCOoWiZMs/bxfE1RHcpLxLJyRnCdr6CEv6+tGvhDvgh1jL7msFY= =eWwc -----END PGP SIGNATURE----- From berendt at b1-systems.de Tue Oct 14 09:23:22 2014 From: berendt at b1-systems.de (Christian Berendt) Date: Tue, 14 Oct 2014 11:23:22 +0200 Subject: [Rdo-list] Default keystone token provider in Juno packages Message-ID: <543CEB8A.8050900@b1-systems.de> We have to clarify for a documentation change (https://review.openstack.org/#/c/127494/) if the default keystone token provider will change in the RDO packages. According to https://blueprints.launchpad.net/keystone/+spec/uuid-as-default-token-provider the default token provider changed from PKI back to UUID. Because of that it is not longer necessary to setup the PKI certificates and keys. Christian. -- Christian Berendt Cloud Solution Architect Mail: berendt at b1-systems.de B1 Systems GmbH Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 From priteau at uchicago.edu Tue Oct 14 13:07:43 2014 From: priteau at uchicago.edu (Pierre Riteau) Date: Tue, 14 Oct 2014 08:07:43 -0500 Subject: [Rdo-list] How does RDO package OpenStack RPM package? In-Reply-To: <543CDEA2.4060301@redhat.com> References: <5438AAD6.3030105@gmail.com> <543972F3.6040508@redhat.com> <543CDEA2.4060301@redhat.com> Message-ID: <718132CF-38A0-4496-A4E6-6D1B73EB8D8C@uchicago.edu> Indeed, I see that the f20 branch has the corresponding code. The spec file has control flow to select different patches and configurations depending on the platform. Thanks Ihar! On 14 Oct 2014, at 03:28, Ihar Hrachyshka wrote: > I'm not a Nova guy, but AFAIK el6-* branches were retired and replaced > by compound builds from f2* branches (f20 is Havana for fedora20, > fedora19, and el6; f21 is Icehouse for fedora20, el6, and el7; and > master for Juno for fedora-rawhide, fedora20, and el7). > > For Fedoras, we build packages in Koji, and we use COPR for EL[67]. > > AFAIK there are no internal Red Hat repositories for RDO. Obviously, we > have internal repositories for RHOSP where we diverge a bit from > upstream releases. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryanmoffett1 at gmail.com Tue Oct 14 14:42:28 2014 From: ryanmoffett1 at gmail.com (Ryan Moffett) Date: Tue, 14 Oct 2014 10:42:28 -0400 Subject: [Rdo-list] Ran packstack --allinone, nothing installed, but says it completed successfully Message-ID: I ran the packstack --allinone installer yesterday (and today) and it says it's completed, but nothing occurs. [ryan at centos ~]$ packstack --allinone Welcome to Installer setup utility Packstack changed given value to required value /home/ryan/.ssh/id_rsa.pub Installing: Clean Up [ DONE ] root at 192.168.56.11's password: Setting up ssh keys [ DONE ] Discovering hosts' details [ DONE ] Adding pre install manifest entries [ DONE ] Preparing servers [ DONE ] Adding AMQP manifest entries [ DONE ] Adding MariaDB manifest entries [ DONE ] Adding Keystone manifest entries [ DONE ] Adding Glance Keystone manifest entries [ DONE ] Adding Glance manifest entries [ DONE ] Adding Cinder Keystone manifest entries [ DONE ] Adding Cinder manifest entries [ DONE ] Checking if the Cinder server has a cinder-volumes vg[ DONE ] Adding Nova API manifest entries [ DONE ] Adding Nova Keystone manifest entries [ DONE ] Adding Nova Cert manifest entries [ DONE ] Adding Nova Conductor manifest entries [ DONE ] Creating ssh keys for Nova migration [ DONE ] Gathering ssh host keys for Nova migration [ DONE ] Adding Nova Compute manifest entries [ DONE ] Adding Nova Scheduler manifest entries [ DONE ] Adding Nova VNC Proxy manifest entries [ DONE ] Adding Openstack Network-related Nova manifest entries[ DONE ] Adding Nova Common manifest entries [ DONE ] Adding Neutron API manifest entries [ DONE ] Adding Neutron Keystone manifest entries [ DONE ] Adding Neutron L3 manifest entries [ DONE ] Adding Neutron L2 Agent manifest entries [ DONE ] Adding Neutron DHCP Agent manifest entries [ DONE ] Adding Neutron LBaaS Agent manifest entries [ DONE ] Adding Neutron Metering Agent manifest entries [ DONE ] Adding Neutron Metadata Agent manifest entries [ DONE ] Checking if NetworkManager is enabled and running [ DONE ] Adding OpenStack Client manifest entries [ DONE ] Adding Horizon manifest entries [ DONE ] Adding Swift Keystone manifest entries [ DONE ] Adding Swift builder manifest entries [ DONE ] Adding Swift proxy manifest entries [ DONE ] Adding Swift storage manifest entries [ DONE ] Adding Swift common manifest entries [ DONE ] Adding Provisioning Demo manifest entries [ DONE ] Adding Provisioning Glance manifest entries [ DONE ] Adding MongoDB manifest entries [ DONE ] Adding Ceilometer manifest entries [ DONE ] Adding Ceilometer Keystone manifest entries [ DONE ] Adding Nagios server manifest entries [ DONE ] Adding Nagios host manifest entries [ DONE ] Adding post install manifest entries [ DONE ] Installing Dependencies [ DONE ] Copying Puppet modules and manifests [ DONE ] Applying 192.168.56.11_prescript.pp 192.168.56.11_prescript.pp: [ DONE ] Applying 192.168.56.11_amqp.pp Applying 192.168.56.11_mariadb.pp 192.168.56.11_amqp.pp: [ DONE ] 192.168.56.11_mariadb.pp: [ DONE ] Applying 192.168.56.11_keystone.pp Applying 192.168.56.11_glance.pp Applying 192.168.56.11_cinder.pp 192.168.56.11_keystone.pp: [ DONE ] 192.168.56.11_cinder.pp: [ DONE ] 192.168.56.11_glance.pp: [ DONE ] Applying 192.168.56.11_api_nova.pp 192.168.56.11_api_nova.pp: [ DONE ] Applying 192.168.56.11_nova.pp 192.168.56.11_nova.pp: [ DONE ] Applying 192.168.56.11_neutron.pp 192.168.56.11_neutron.pp: [ DONE ] Applying 192.168.56.11_neutron_fwaas.pp Applying 192.168.56.11_osclient.pp Applying 192.168.56.11_horizon.pp 192.168.56.11_neutron_fwaas.pp: [ DONE ] 192.168.56.11_horizon.pp: [ DONE ] 192.168.56.11_osclient.pp: [ DONE ] Applying 192.168.56.11_ring_swift.pp 192.168.56.11_ring_swift.pp: [ DONE ] Applying 192.168.56.11_swift.pp Applying 192.168.56.11_provision_demo.pp Applying 192.168.56.11_provision_glance.pp 192.168.56.11_swift.pp: [ DONE ] 192.168.56.11_provision_glance.pp: [ DONE ] 192.168.56.11_provision_demo.pp: [ DONE ] Applying 192.168.56.11_mongodb.pp 192.168.56.11_mongodb.pp: [ DONE ] Applying 192.168.56.11_ceilometer.pp Applying 192.168.56.11_nagios.pp Applying 192.168.56.11_nagios_nrpe.pp 192.168.56.11_ceilometer.pp: [ DONE ] 192.168.56.11_nagios_nrpe.pp: [ DONE ] 192.168.56.11_nagios.pp: [ DONE ] Applying 192.168.56.11_postscript.pp 192.168.56.11_postscript.pp: [ DONE ] Applying Puppet manifests [ DONE ] Finalizing [ DONE ] **** Installation completed successfully ****** Additional information: * A new answerfile was created in: /home/ryan/packstack-answers-20141014-091325.txt * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components. * File /root/keystonerc_admin has been created on OpenStack client host 192.168.56.11. To use the command line tools you need to source the file. * Copy of keystonerc_admin file has been created for non-root user in /home/ryan. * To access the OpenStack Dashboard browse to http://192.168.56.11/dashboard . Please, find your login credentials stored in the keystonerc_admin in your home directory. * To use Nagios, browse to http://192.168.56.11/nagios username: nagiosadmin, password: a6581c13ecd146dd * The installation log file is available at: /var/tmp/packstack/20141014-091325-i020mT/openstack-setup.log * The generated manifests are available at: /var/tmp/packstack/20141014-091325-i020mT/manifests [ryan at centos ~]$ ls packstack-answers-20141014-091325.txt [ryan at centos ~]$ There is no keystone_rc file created, in fact the entire application of all of the puppet manifests took about 5 seconds. I noticed that puppet isn't even installed and based on reading, it should be. It looks like no openstack components are actually installed or configured. The version of packstack is: [ryan at centos ~]$ packstack --version packstack Icehouse 2014.1.1dev1251 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ak at cloudssky.com Tue Oct 14 15:27:21 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Tue, 14 Oct 2014 17:27:21 +0200 Subject: [Rdo-list] Ran packstack --allinone, nothing installed, but says it completed successfully In-Reply-To: References: Message-ID: Ryan, Try to run packstack as root or at least with "sudo packstack --allinone". HTH, -Arash On Tue, Oct 14, 2014 at 4:42 PM, Ryan Moffett wrote: > I ran the packstack --allinone installer yesterday (and today) and it says > it's completed, but nothing occurs. > > [ryan at centos ~]$ packstack --allinone > Welcome to Installer setup utility > Packstack changed given value to required value /home/ryan/.ssh/id_rsa.pub > > Installing: > Clean Up [ DONE ] > root at 192.168.56.11's password: > Setting up ssh keys [ DONE ] > Discovering hosts' details [ DONE ] > Adding pre install manifest entries [ DONE ] > Preparing servers [ DONE ] > Adding AMQP manifest entries [ DONE ] > Adding MariaDB manifest entries [ DONE ] > Adding Keystone manifest entries [ DONE ] > Adding Glance Keystone manifest entries [ DONE ] > Adding Glance manifest entries [ DONE ] > Adding Cinder Keystone manifest entries [ DONE ] > Adding Cinder manifest entries [ DONE ] > Checking if the Cinder server has a cinder-volumes vg[ DONE ] > Adding Nova API manifest entries [ DONE ] > Adding Nova Keystone manifest entries [ DONE ] > Adding Nova Cert manifest entries [ DONE ] > Adding Nova Conductor manifest entries [ DONE ] > Creating ssh keys for Nova migration [ DONE ] > Gathering ssh host keys for Nova migration [ DONE ] > Adding Nova Compute manifest entries [ DONE ] > Adding Nova Scheduler manifest entries [ DONE ] > Adding Nova VNC Proxy manifest entries [ DONE ] > Adding Openstack Network-related Nova manifest entries[ DONE ] > Adding Nova Common manifest entries [ DONE ] > Adding Neutron API manifest entries [ DONE ] > Adding Neutron Keystone manifest entries [ DONE ] > Adding Neutron L3 manifest entries [ DONE ] > Adding Neutron L2 Agent manifest entries [ DONE ] > Adding Neutron DHCP Agent manifest entries [ DONE ] > Adding Neutron LBaaS Agent manifest entries [ DONE ] > Adding Neutron Metering Agent manifest entries [ DONE ] > Adding Neutron Metadata Agent manifest entries [ DONE ] > Checking if NetworkManager is enabled and running [ DONE ] > Adding OpenStack Client manifest entries [ DONE ] > Adding Horizon manifest entries [ DONE ] > Adding Swift Keystone manifest entries [ DONE ] > Adding Swift builder manifest entries [ DONE ] > Adding Swift proxy manifest entries [ DONE ] > Adding Swift storage manifest entries [ DONE ] > Adding Swift common manifest entries [ DONE ] > Adding Provisioning Demo manifest entries [ DONE ] > Adding Provisioning Glance manifest entries [ DONE ] > Adding MongoDB manifest entries [ DONE ] > Adding Ceilometer manifest entries [ DONE ] > Adding Ceilometer Keystone manifest entries [ DONE ] > Adding Nagios server manifest entries [ DONE ] > Adding Nagios host manifest entries [ DONE ] > Adding post install manifest entries [ DONE ] > Installing Dependencies [ DONE ] > Copying Puppet modules and manifests [ DONE ] > Applying 192.168.56.11_prescript.pp > 192.168.56.11_prescript.pp: [ DONE ] > Applying 192.168.56.11_amqp.pp > Applying 192.168.56.11_mariadb.pp > 192.168.56.11_amqp.pp: [ DONE ] > 192.168.56.11_mariadb.pp: [ DONE ] > Applying 192.168.56.11_keystone.pp > Applying 192.168.56.11_glance.pp > Applying 192.168.56.11_cinder.pp > 192.168.56.11_keystone.pp: [ DONE ] > 192.168.56.11_cinder.pp: [ DONE ] > 192.168.56.11_glance.pp: [ DONE ] > Applying 192.168.56.11_api_nova.pp > 192.168.56.11_api_nova.pp: [ DONE ] > Applying 192.168.56.11_nova.pp > 192.168.56.11_nova.pp: [ DONE ] > Applying 192.168.56.11_neutron.pp > 192.168.56.11_neutron.pp: [ DONE ] > Applying 192.168.56.11_neutron_fwaas.pp > Applying 192.168.56.11_osclient.pp > Applying 192.168.56.11_horizon.pp > 192.168.56.11_neutron_fwaas.pp: [ DONE ] > 192.168.56.11_horizon.pp: [ DONE ] > 192.168.56.11_osclient.pp: [ DONE ] > Applying 192.168.56.11_ring_swift.pp > 192.168.56.11_ring_swift.pp: [ DONE ] > Applying 192.168.56.11_swift.pp > Applying 192.168.56.11_provision_demo.pp > Applying 192.168.56.11_provision_glance.pp > 192.168.56.11_swift.pp: [ DONE ] > 192.168.56.11_provision_glance.pp: [ DONE ] > > 192.168.56.11_provision_demo.pp: [ DONE ] > > Applying 192.168.56.11_mongodb.pp > 192.168.56.11_mongodb.pp: [ DONE ] > Applying 192.168.56.11_ceilometer.pp > Applying 192.168.56.11_nagios.pp > Applying 192.168.56.11_nagios_nrpe.pp > 192.168.56.11_ceilometer.pp: [ DONE ] > 192.168.56.11_nagios_nrpe.pp: [ DONE ] > 192.168.56.11_nagios.pp: [ DONE ] > Applying 192.168.56.11_postscript.pp > 192.168.56.11_postscript.pp: [ DONE ] > Applying Puppet manifests [ DONE ] > Finalizing [ DONE ] > > **** Installation completed successfully ****** > > > Additional information: > * A new answerfile was created in: > /home/ryan/packstack-answers-20141014-091325.txt > * Time synchronization installation was skipped. Please note that > unsynchronized time on server instances might be problem for some OpenStack > components. > * File /root/keystonerc_admin has been created on OpenStack client host > 192.168.56.11. To use the command line tools you need to source the file. > * Copy of keystonerc_admin file has been created for non-root user in > /home/ryan. > * To access the OpenStack Dashboard browse to > http://192.168.56.11/dashboard . > Please, find your login credentials stored in the keystonerc_admin in your > home directory. > * To use Nagios, browse to http://192.168.56.11/nagios username: > nagiosadmin, password: a6581c13ecd146dd > * The installation log file is available at: > /var/tmp/packstack/20141014-091325-i020mT/openstack-setup.log > * The generated manifests are available at: > /var/tmp/packstack/20141014-091325-i020mT/manifests > [ryan at centos ~]$ ls > packstack-answers-20141014-091325.txt > [ryan at centos ~]$ > > There is no keystone_rc file created, in fact the entire application of > all of the puppet manifests took about 5 seconds. I noticed that puppet > isn't even installed and based on reading, it should be. It looks like no > openstack components are actually installed or configured. > > The version of packstack is: > [ryan at centos ~]$ packstack --version > packstack Icehouse 2014.1.1dev1251 > > > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From xzhao at bnl.gov Tue Oct 14 20:48:17 2014 From: xzhao at bnl.gov (Zhao, Xin) Date: Tue, 14 Oct 2014 16:48:17 -0400 Subject: [Rdo-list] intermittent dhcp problem Message-ID: <543D8C11.90308@bnl.gov> Hello, I have a multi-node icehouse deployment (one controller, one network and one compute node), using neutron ML2 and openvswitch/VLAN networking, based on RDO on RHEL6. Everything seems to work fine. But once in a while, new instances can't get IP anymore, the syslog shows errors like "DHCPDISCOVER .... no address available", neutron DB shows the IP is allocated, but the DHCP conf file (eg. /var/lib/neutron/dhcp/XXXXXX/host) doesn't have it. No particular error messages from the dhcp agent log file. Restarting dhcp agent doesn't fix it. I have to restart all neutron services, including openvswitch daemon, to get the system back. Another issue I notice is, on the network node, dmesg shows the following errors repeatedly, even when the networking services appear to be working fine : "...... tap84e6f9d1-c2: hw csum failure. Pid: 0, comm: swapper Not tainted 2.6.32-431.5.1.el6.x86_64 #1 Call Trace: [] ? netdev_rx_csum_fault+0x42/0x50 [] ? __skb_checksum_complete_head+0x60/0x70 ...... " Below after my signature are some system information of the network node. Any ideas on what's going on and how to debug it? Thanks a lot, Xin # uname -a Linux cldnet02.cloud.local 2.6.32-431.5.1.el6.x86_64 #1 SMP Tue Feb 11 13:30:01 CST 2014 x86_64 x86_64 x86_64 GNU/Linux # rpm -qa | grep neutron python-neutronclient-2.3.4-4.el6.noarch openstack-neutron-2014.1.2-1.el6.noarch openstack-neutron-ml2-2014.1.2-1.el6.noarch python-neutron-2014.1.2-1.el6.noarch openstack-neutron-openvswitch-2014.1.2-1.el6.noarch # rpm -qa | grep openvswitch openvswitch-1.11.0_8ce28d-1.el6ost.x86_64 openstack-neutron-openvswitch-2014.1.2-1.el6.noarch the NIC for the VM network: # ethtool -i p1p2 driver: myri10ge version: 1.5.1-1.451 firmware-version: 1.4.52 -- 2010/10/28 21:27:06 m bus-info: 0000:06:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no the NIC for the management network: # ethtool -i em1 driver: bnx2 version: 2.2.3 firmware-version: 4.6.8 bc 4.6.4 NCSI 1.0.6 bus-info: 0000:01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no the NIC for the external network: # ethtool -i p1p1 driver: myri10ge version: 1.5.1-1.451 firmware-version: 1.4.52 -- 2010/10/28 21:27:06 m bus-info: 0000:05:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no From apevec at gmail.com Tue Oct 14 22:25:43 2014 From: apevec at gmail.com (Alan Pevec) Date: Wed, 15 Oct 2014 00:25:43 +0200 Subject: [Rdo-list] Default keystone token provider in Juno packages In-Reply-To: <543CEB8A.8050900@b1-systems.de> References: <543CEB8A.8050900@b1-systems.de> Message-ID: > We have to clarify for a documentation change > (https://review.openstack.org/#/c/127494/) if the default keystone token > provider will change in the RDO packages. I've replied in the review, repeating here for the archive: openstack-keystone RPM does not modify upstream default i.e. [token] provider is not set in http://pkgs.fedoraproject.org/cgit/openstack-keystone.git/tree/keystone-dist.conf puppet-keystone modules was setting this to pki earlier but that was changed to match Juno: https://github.com/stackforge/puppet-keystone/commit/611d9649f21c304af3c34475b42e3b04822c8639 This is included in the latest RDO Juno build openstack-puppet-modules-2014.2.1-0.4 I also double-checked that packstack is not setting token_provider parameter. So all good for RDO Juno! Cheers, Alan From apevec at gmail.com Tue Oct 14 22:51:32 2014 From: apevec at gmail.com (Alan Pevec) Date: Wed, 15 Oct 2014 00:51:32 +0200 Subject: [Rdo-list] Default keystone token provider in Juno packages In-Reply-To: References: <543CEB8A.8050900@b1-systems.de> Message-ID: > So all good for RDO Juno! Please note later -1 review from Nathan, I jumped to the conclusion! "We still need to perform the PKI certificate setup, even if UUID tokens are being used. The reason is that the token revocation list is signed regardless of the token format. If the keys/cert are not created, then an attempt to fetch the revocation list will result in signing errors due to an underlying ENOENT." From nkinder at redhat.com Tue Oct 14 23:16:30 2014 From: nkinder at redhat.com (Nathan Kinder) Date: Tue, 14 Oct 2014 16:16:30 -0700 Subject: [Rdo-list] Default keystone token provider in Juno packages In-Reply-To: References: <543CEB8A.8050900@b1-systems.de> Message-ID: <543DAECE.6090409@redhat.com> On 10/14/2014 03:51 PM, Alan Pevec wrote: >> So all good for RDO Juno! > > Please note later -1 review from Nathan, I jumped to the conclusion! > > "We still need to perform the PKI certificate setup, even if UUID > tokens are being used. The reason is that the token revocation list is > signed regardless of the token format. If the keys/cert are not > created, then an attempt to fetch the revocation list will result in > signing errors due to an underlying ENOENT." The puppet-keystone module handles this properly now too, so things will be set up correctly when using packstack. The documentation should still mention that PKI setup is needed even when using the UUID token format. This is true for all platforms/distributions, not just RDO. Thanks, -NGK > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > From Arkady_Kanevsky at dell.com Tue Oct 14 23:20:22 2014 From: Arkady_Kanevsky at dell.com (Arkady_Kanevsky at dell.com) Date: Tue, 14 Oct 2014 18:20:22 -0500 Subject: [Rdo-list] deployment tools in RDO Message-ID: <336424C1A5A44044B29030055527AA7504A6DA42CD@AUSX7MCPS301.AMER.DELL.COM> For Juno release, which deployment tools will come in each RDO release? Packstack, Foreman, Staypuft? Thanks, Arkady Arkady Kanevsky, Ph.D. Director of SW development Dell ESG Dell Inc. One Dell Way, MS PS2-47 Round Rock, TX 78682, USA Phone: 512 723 5264 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmyers at redhat.com Wed Oct 15 06:41:12 2014 From: pmyers at redhat.com (Perry Myers) Date: Wed, 15 Oct 2014 08:41:12 +0200 Subject: [Rdo-list] deployment tools in RDO In-Reply-To: <336424C1A5A44044B29030055527AA7504A6DA42CD@AUSX7MCPS301.AMER.DELL.COM> References: <336424C1A5A44044B29030055527AA7504A6DA42CD@AUSX7MCPS301.AMER.DELL.COM> Message-ID: <543E1708.2020901@redhat.com> On 10/15/2014 01:20 AM, Arkady_Kanevsky at dell.com wrote: > For Juno release, which deployment tools will come in each RDO release? > > Packstack, Foreman, Staypuft? Packstack and RDO Installer which uses Foreman as a component. RDO Installer will be like RHEL OSP Installer which is based on the Staypuft plugin that is part of the Foreman project Mike, you were looking at the initial dependency resolution for putting RDO Installer into Juno right? From ak at cloudssky.com Wed Oct 15 21:37:44 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Wed, 15 Oct 2014 23:37:44 +0200 Subject: [Rdo-list] Ironic for RDO Juno Message-ID: Hi, Is there any guide how to install and try Ironic on RDO Juno? Thanks! -Arash -------------- next part -------------- An HTML attachment was scrubbed... URL: From mail at arif-ali.co.uk Wed Oct 15 23:14:27 2014 From: mail at arif-ali.co.uk (Arif Ali) Date: Thu, 16 Oct 2014 00:14:27 +0100 Subject: [Rdo-list] Ironic for RDO Juno In-Reply-To: References: Message-ID: <543EFFD3.9080508@arif-ali.co.uk> On 15/10/14 22:37, Arash Kaffamanesh wrote: > Hi, > > Is there any guide how to install and try Ironic on RDO Juno? > > Thanks! > -Arash > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list Hi Arash, I had a first attempt at it last week, after rc1 was release of ironic, and I did everything through source. My success was that I was able to power machines on and off through ironic. So both the openstack-ironic, and python-ironic were compiled from source in my test Firstly the openstack-nova in RDO didn't have the right libraries to have ironic working, but I think the new openstack-nova in the RDO repository since then should enable you to get working. Fortunately, I found the copr builds, which had the relevant material. This was able to help me advance to the stage I mention above. Looking thtough the copr builds, there is now an RPM for openstack-ironic, which I haven't tested yet, but would be interesting to see what stage that is at, but even then we would need to recompile python-ironicclient to get the ironic commands to work I used the howto in http://docs.openstack.org/developer/ironic/deploy/install-guide.html to get to where I did, and I was reasonably happy with the progress. I will probably look back at this again once I have finished with my current work on Heat templates and Controller HA setup I hope that helps Arif Ali IRC: arif-ali at freenode LinkedIn: http://uk.linkedin.com/in/arifali -------------- next part -------------- An HTML attachment was scrubbed... URL: From 18661640013 at 163.com Thu Oct 16 08:42:06 2014 From: 18661640013 at 163.com (=?GBK?B?wO7Wvse/?=) Date: Thu, 16 Oct 2014 16:42:06 +0800 (CST) Subject: [Rdo-list] When will RDO for Juno release be officially available? Message-ID: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> Hi, When will RDO for Juno release be officially available? Can anybody tell me an exact date? I am using RDO to setup Openstack environment. Just want to know when I can use it to setup Juno. Thanks. Lester -------------- next part -------------- An HTML attachment was scrubbed... URL: From ak at cloudssky.com Thu Oct 16 08:59:27 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Thu, 16 Oct 2014 10:59:27 +0200 Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> Message-ID: Hi Lester, The milestone 3 release is already available and I installed it 2 weeks ago and I'm very lucky with it, it works like a charm :-) Here is a short blog post about a 2 node deployment: http://ow.ly/Clrq5 And I guess the final RDO Juno 1.0 release will be released before Juno Summit and if you have the milestone 3 installed, you might be able to easily update it. @RDO Gurus: right? HTH, -Arash On Thu, Oct 16, 2014 at 10:42 AM, ??? <18661640013 at 163.com> wrote: > Hi, > > When will RDO for Juno release be officially available? Can anybody tell > me an exact date? I am using RDO to setup Openstack environment. Just want > to know when I can use it to setup Juno. > > Thanks. > Lester > > > ?????????????? > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihrachys at redhat.com Thu Oct 16 10:20:10 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Thu, 16 Oct 2014 12:20:10 +0200 Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> Message-ID: <543F9BDA.5020307@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 16/10/14 10:42, ??? wrote: > Hi, > > When will RDO for Juno release be officially available? Can anybody > tell me an exact date? I am using RDO to setup Openstack > environment. Just want to know when I can use it to setup Juno. We tightly track upstream releases. Currently we have multiple components built for RC2 milestone in our Juno repository. At the moment the latest Neutron Juno release is RC3, and it was built and pushed to CI system that gates new packages for RDO repo. So you already can try Juno bits and say what you think. ;) The final upstream Juno release is expected today, so once we get final tarballs built, RDO team will update packages in meaningful time. I think it's a matter of a week or so for all the updates to reach the production repo. /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUP5vaAAoJEC5aWaUY1u57hQ0H/0RsYiXF/SvODmCXsSoRw9Uc OfkmNBd30RdTNcPi21j4u3wCyXWq+GyRG+Io5iPAknl8yYV0ycPx1RPsZCNbKYgI v/j/BlcIbJmGm+WNS5S1kaJNpfXPO4H5phubp7VMfFral8y+L/AxsKoSB8kB2nc8 WYMh8Xmw24ApT340QKtDtSN2PDy0f9YqxW4Cb0j7jFpBy10tYL1TwOpE7k2pP7Za U9O4IPsEacGBW1rsEggusN6SiF8mkVZ5zWXQMPlBytyxayT37u2wZDyy/PG3wzWu J97iGR+86GoGLGuGzjUhHj2CXKDU7MoDNiMBHcoPfbgBEVtX0M3LgxG0yVx832E= =YmkX -----END PGP SIGNATURE----- From 18661640013 at 163.com Thu Oct 16 10:26:16 2014 From: 18661640013 at 163.com (Lester Li) Date: Thu, 16 Oct 2014 18:26:16 +0800 (CST) Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: <543F9BDA.5020307@redhat.com> References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> <543F9BDA.5020307@redhat.com> Message-ID: <18690743.21da2.149187e63f8.Coremail.18661640013@163.com> That's great. Thanks for your effort. Is the procedure changed for RDO of Juno release? https://openstack.redhat.com/Main_Page will be updated accordingly once RDO for Juno is ready. Right? At 2014-10-16 18:20:10, "Ihar Hrachyshka" wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA512 > >On 16/10/14 10:42, ??? wrote: >> Hi, >> >> When will RDO for Juno release be officially available? Can anybody >> tell me an exact date? I am using RDO to setup Openstack >> environment. Just want to know when I can use it to setup Juno. > >We tightly track upstream releases. Currently we have multiple >components built for RC2 milestone in our Juno repository. At the >moment the latest Neutron Juno release is RC3, and it was built and >pushed to CI system that gates new packages for RDO repo. > >So you already can try Juno bits and say what you think. ;) > >The final upstream Juno release is expected today, so once we get >final tarballs built, RDO team will update packages in meaningful >time. I think it's a matter of a week or so for all the updates to >reach the production repo. > >/Ihar >-----BEGIN PGP SIGNATURE----- >Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > >iQEcBAEBCgAGBQJUP5vaAAoJEC5aWaUY1u57hQ0H/0RsYiXF/SvODmCXsSoRw9Uc >OfkmNBd30RdTNcPi21j4u3wCyXWq+GyRG+Io5iPAknl8yYV0ycPx1RPsZCNbKYgI >v/j/BlcIbJmGm+WNS5S1kaJNpfXPO4H5phubp7VMfFral8y+L/AxsKoSB8kB2nc8 >WYMh8Xmw24ApT340QKtDtSN2PDy0f9YqxW4Cb0j7jFpBy10tYL1TwOpE7k2pP7Za >U9O4IPsEacGBW1rsEggusN6SiF8mkVZ5zWXQMPlBytyxayT37u2wZDyy/PG3wzWu >J97iGR+86GoGLGuGzjUhHj2CXKDU7MoDNiMBHcoPfbgBEVtX0M3LgxG0yVx832E= >=YmkX >-----END PGP SIGNATURE----- > >_______________________________________________ >Rdo-list mailing list >Rdo-list at redhat.com >https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihrachys at redhat.com Thu Oct 16 10:31:57 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Thu, 16 Oct 2014 12:31:57 +0200 Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: <18690743.21da2.149187e63f8.Coremail.18661640013@163.com> References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> <543F9BDA.5020307@redhat.com> <18690743.21da2.149187e63f8.Coremail.18661640013@163.com> Message-ID: <543F9E9D.1050803@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 16/10/14 12:26, Lester Li wrote: > That's great. Thanks for your effort. Is the procedure changed for > RDO of Juno release? https://openstack.redhat.com/Main_Page will be > updated accordingly once RDO for Juno is ready. Right? Juno is not considered production ready yet, so it's not on Main Page. If you're keen to try Juno right now, the basics should be the same, just install the appropriate rdo-release package: sudo yum install http://rdo.fedorapeople.org/openstack-juno/rdo-release-juno.rpm /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUP56dAAoJEC5aWaUY1u57yikIANoqjGj8DwzzX9eaZbn7wyGU nB4Psy79HDqZ/CTQmSQ3lPJDXkr7Hyu02obYQXxUPIE13rCsJjF1/2PElAFSGtdu 58goRdsuTtiAtBvBZyC1grZiFXYgH0F+FiDRQ4Q4bfUfenaE8rZAxKTb039HX/Zm 1afD/SwOL4gPkoHX2furR3CdJ7hrdhGyLe+ZuOjhdqbO/OERN7qof1FEaZ201Azz coRiBdct7UWn/l1C7P4VVwEOQ31Z5bjTkprkybB0OQOxPQfUlWYVoSHSytvOLbGY njq1J22anGR1R72ym472kOGgzqA/NzMsdBfWBQkMbiqSWGaWMg/IICOeUuVVCac= =A6vy -----END PGP SIGNATURE----- From ak at cloudssky.com Thu Oct 16 16:12:00 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Thu, 16 Oct 2014 18:12:00 +0200 Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: <543F9E9D.1050803@redhat.com> References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> <543F9BDA.5020307@redhat.com> <18690743.21da2.149187e63f8.Coremail.18661640013@163.com> <543F9E9D.1050803@redhat.com> Message-ID: Just let you know, I did a yum upgrade on controller and compute nodes and the packages was upgraded to rc2 and rc3 packages, after that neutron didn't work on controller and I'd only to re-run packstack and reboot my instances and I was more than lucky :-) On Thu, Oct 16, 2014 at 12:31 PM, Ihar Hrachyshka wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 16/10/14 12:26, Lester Li wrote: > > That's great. Thanks for your effort. Is the procedure changed for > > RDO of Juno release? https://openstack.redhat.com/Main_Page will be > > updated accordingly once RDO for Juno is ready. Right? > > Juno is not considered production ready yet, so it's not on Main Page. > > If you're keen to try Juno right now, the basics should be the same, > just install the appropriate rdo-release package: > > sudo yum install > http://rdo.fedorapeople.org/openstack-juno/rdo-release-juno.rpm > > /Ihar > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > > iQEcBAEBCgAGBQJUP56dAAoJEC5aWaUY1u57yikIANoqjGj8DwzzX9eaZbn7wyGU > nB4Psy79HDqZ/CTQmSQ3lPJDXkr7Hyu02obYQXxUPIE13rCsJjF1/2PElAFSGtdu > 58goRdsuTtiAtBvBZyC1grZiFXYgH0F+FiDRQ4Q4bfUfenaE8rZAxKTb039HX/Zm > 1afD/SwOL4gPkoHX2furR3CdJ7hrdhGyLe+ZuOjhdqbO/OERN7qof1FEaZ201Azz > coRiBdct7UWn/l1C7P4VVwEOQ31Z5bjTkprkybB0OQOxPQfUlWYVoSHSytvOLbGY > njq1J22anGR1R72ym472kOGgzqA/NzMsdBfWBQkMbiqSWGaWMg/IICOeUuVVCac= > =A6vy > -----END PGP SIGNATURE----- > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkinder at redhat.com Thu Oct 16 19:07:39 2014 From: nkinder at redhat.com (Nathan Kinder) Date: Thu, 16 Oct 2014 12:07:39 -0700 Subject: [Rdo-list] Default keystone token provider in Juno packages In-Reply-To: References: <543CEB8A.8050900@b1-systems.de> Message-ID: <5440177B.6020507@redhat.com> On 10/14/2014 03:25 PM, Alan Pevec wrote: >> We have to clarify for a documentation change >> (https://review.openstack.org/#/c/127494/) if the default keystone token >> provider will change in the RDO packages. > > I've replied in the review, repeating here for the archive: > > openstack-keystone RPM does not modify upstream default i.e. [token] > provider is not set in > http://pkgs.fedoraproject.org/cgit/openstack-keystone.git/tree/keystone-dist.conf > > puppet-keystone modules was setting this to pki earlier but that was > changed to match Juno: > https://github.com/stackforge/puppet-keystone/commit/611d9649f21c304af3c34475b42e3b04822c8639 > This is included in the latest RDO Juno build > openstack-puppet-modules-2014.2.1-0.4 > > I also double-checked that packstack is not setting token_provider parameter. This is sadly not true. Packstack is still defaulting to PKI: https://bugs.launchpad.net/packstack/+bug/1382160 I've proposed a fix here: https://review.openstack.org/#/c/129018/ Thanks, -NGK > > So all good for RDO Juno! > > Cheers, > Alan > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > From kincljc at ornl.gov Thu Oct 16 19:48:30 2014 From: kincljc at ornl.gov (Kincl, Jason C.) Date: Thu, 16 Oct 2014 19:48:30 +0000 Subject: [Rdo-list] Ironic for RDO Juno In-Reply-To: <543EFFD3.9080508@arif-ali.co.uk> References: <543EFFD3.9080508@arif-ali.co.uk> Message-ID: <0638495B-0122-49A7-A6D3-259943E1AA57@ornl.gov> On Oct 15, 2014, at 7:14 PM, Arif Ali > wrote: On 15/10/14 22:37, Arash Kaffamanesh wrote: Hi, Is there any guide how to install and try Ironic on RDO Juno? Thanks! -Arash _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list Hi Arash, I had a first attempt at it last week, after rc1 was release of ironic, and I did everything through source. My success was that I was able to power machines on and off through ironic. So both the openstack-ironic, and python-ironic were compiled from source in my test Firstly the openstack-nova in RDO didn't have the right libraries to have ironic working, but I think the new openstack-nova in the RDO repository since then should enable you to get working. Fortunately, I found the copr builds, which had the relevant material. This was able to help me advance to the stage I mention above. Looking thtough the copr builds, there is now an RPM for openstack-ironic, which I haven't tested yet, but would be interesting to see what stage that is at, but even then we would need to recompile python-ironicclient to get the ironic commands to work I used the howto in http://docs.openstack.org/developer/ironic/deploy/install-guide.html to get to where I did, and I was reasonably happy with the progress. I will probably look back at this again once I have finished with my current work on Heat templates and Controller HA setup I hope that helps Arif Ali IRC: arif-ali at freenode LinkedIn: http://uk.linkedin.com/in/arifali _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list Hi Arash, So I am also looking at Ironic for Juno as well and the documentation has been hard to come by but I have found a few things: https://etherpad.openstack.org/p/IronicWhiteBoard https://etherpad.openstack.org/p/Using_Ironic_to_launch_instances_on_real_hardware Note that since the Ironic project is moving at such a high velocity, documentation seems to almost be obsolete after it is written. These etherpads are where the Ironic devs are staging documentation and general project information and is probably the best place I have found to get information on the project. Now that RDO has juno-rc1 and rc2 RPMs, you should be able to run Juno in RDO with Ironic. I have been tracking the progress of the Ironic integration into Nova and other OS projects and with rc1 all of the integration should be complete. But I am neither a Ironic developer or a Juno tester so YMMV :) Thanks, Jason Kincl HPC Systems Administrator National Center for Computational Sciences Oak Ridge National Laboratory From ihrachys at redhat.com Fri Oct 17 08:13:16 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Fri, 17 Oct 2014 10:13:16 +0200 Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> <543F9BDA.5020307@redhat.com> <18690743.21da2.149187e63f8.Coremail.18661640013@163.com> <543F9E9D.1050803@redhat.com> Message-ID: <5440CF9C.7050601@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 16/10/14 18:12, Arash Kaffamanesh wrote: > Just let you know, I did a yum upgrade on controller and compute > nodes and the packages was upgraded to rc2 and rc3 packages, after > that neutron didn't work on controller and I'd only to re-run > packstack and reboot my instances and I was more than lucky :-) I suspect this is because you need to run db migration steps after each update till the final release, otherwise you loose some db migration steps, and service crashes. # neutron-db-manage \ - --config-file /etc/neutron/neutron.conf \ - --config-file /etc/neutron/plugin.ini upgrade head /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUQM+cAAoJEC5aWaUY1u57tKIIAIeaNVDTv/8OsJUZLcn8khQW j8GlugwvvqjO0uJ+43WCtpO9r4VgeaCGRGgeLrFuhXi0DxMQXwF0tpihYBmPPvyo Dp8f6LXWJ61O9D3UCSF8YVv0Nhx+Gv9za5QdOw6gAso+ZwdKfyxnIHtZf6HYivv8 5IMPt+kWuYrX/AdwMgsDYDaldKiaCqX8+5mdI1u3K4cg+Sm9eGuwWmIms8XMcQya HAtJUo5kK3cNHvdPJbY4CbcAmtrHqRk6OMh/i6kuI3ybmgVhDyMq0XCtPpxf8yGK kIoX/gEjRkMeWonkbfjcRP3mGFiGoWd5UWhPh/KoAfcZgLhE8cAsRL6IDkLCWRk= =zOH7 -----END PGP SIGNATURE----- From Sam.Wan at emc.com Fri Oct 17 08:30:23 2014 From: Sam.Wan at emc.com (Wan, Sam) Date: Fri, 17 Oct 2014 04:30:23 -0400 Subject: [Rdo-list] how to add repository for the cerfitication test suite Message-ID: <2766FDEB4D6EC647B5ED0A96096A2C370FCF3D0BAC@MX10A.corp.emc.com> Dear all, I'm engaged in redhat openstack test. When I read the user guide, it says to enable the test suite repository with below commands: subscription-manager repos --enable=rhel-7-server-openstack-5.0-cts-rpms Seems this does not work on my system: [root at redhat1 ~]# subscription-manager repos --enable=rhel-7-server-openstack-5.0-cts-rpms Error: rhel-7-server-openstack-5.0-cts-rpms is not a valid repo ID. Use --list option to see valid repos. [root at redhat1 ~]# There's no cts in the repository [root at redhat1 yum.repos.d]# grep -i cts redhat.repo [root at redhat1 yum.repos.d]# Could you please tell me how to add the repository? Thanks and regards Sam -------------- next part -------------- An HTML attachment was scrubbed... URL: From ak at cloudssky.com Fri Oct 17 08:34:48 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Fri, 17 Oct 2014 10:34:48 +0200 Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: <5440CF9C.7050601@redhat.com> References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> <543F9BDA.5020307@redhat.com> <18690743.21da2.149187e63f8.Coremail.18661640013@163.com> <543F9E9D.1050803@redhat.com> <5440CF9C.7050601@redhat.com> Message-ID: Ihar, thanks, much appreciated. When I run: On Fri, Oct 17, 2014 at 10:13 AM, Ihar Hrachyshka wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 16/10/14 18:12, Arash Kaffamanesh wrote: > > Just let you know, I did a yum upgrade on controller and compute > > nodes and the packages was upgraded to rc2 and rc3 packages, after > > that neutron didn't work on controller and I'd only to re-run > > packstack and reboot my instances and I was more than lucky :-) > > I suspect this is because you need to run db migration steps after > each update till the final release, otherwise you loose some db > migration steps, and service crashes. > > # neutron-db-manage \ > - --config-file /etc/neutron/neutron.conf \ > - --config-file /etc/neutron/plugin.ini upgrade head > > /Ihar > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > > iQEcBAEBCgAGBQJUQM+cAAoJEC5aWaUY1u57tKIIAIeaNVDTv/8OsJUZLcn8khQW > j8GlugwvvqjO0uJ+43WCtpO9r4VgeaCGRGgeLrFuhXi0DxMQXwF0tpihYBmPPvyo > Dp8f6LXWJ61O9D3UCSF8YVv0Nhx+Gv9za5QdOw6gAso+ZwdKfyxnIHtZf6HYivv8 > 5IMPt+kWuYrX/AdwMgsDYDaldKiaCqX8+5mdI1u3K4cg+Sm9eGuwWmIms8XMcQya > HAtJUo5kK3cNHvdPJbY4CbcAmtrHqRk6OMh/i6kuI3ybmgVhDyMq0XCtPpxf8yGK > kIoX/gEjRkMeWonkbfjcRP3mGFiGoWd5UWhPh/KoAfcZgLhE8cAsRL6IDkLCWRk= > =zOH7 > -----END PGP SIGNATURE----- > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ak at cloudssky.com Fri Oct 17 08:36:36 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Fri, 17 Oct 2014 10:36:36 +0200 Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> <543F9BDA.5020307@redhat.com> <18690743.21da2.149187e63f8.Coremail.18661640013@163.com> <543F9E9D.1050803@redhat.com> <5440CF9C.7050601@redhat.com> Message-ID: .. wenn I run: [root at controller~(keystone_admin)]# neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini upgrade I'm getting: You must provide a revision or relative delta any ideas? Thx -Arash On Fri, Oct 17, 2014 at 10:34 AM, Arash Kaffamanesh wrote: > Ihar, thanks, much appreciated. > When I run: > > > On Fri, Oct 17, 2014 at 10:13 AM, Ihar Hrachyshka > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA512 >> >> On 16/10/14 18:12, Arash Kaffamanesh wrote: >> > Just let you know, I did a yum upgrade on controller and compute >> > nodes and the packages was upgraded to rc2 and rc3 packages, after >> > that neutron didn't work on controller and I'd only to re-run >> > packstack and reboot my instances and I was more than lucky :-) >> >> I suspect this is because you need to run db migration steps after >> each update till the final release, otherwise you loose some db >> migration steps, and service crashes. >> >> # neutron-db-manage \ >> - --config-file /etc/neutron/neutron.conf \ >> - --config-file /etc/neutron/plugin.ini upgrade head >> >> /Ihar >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG/MacGPG2 v2.0.22 (Darwin) >> >> iQEcBAEBCgAGBQJUQM+cAAoJEC5aWaUY1u57tKIIAIeaNVDTv/8OsJUZLcn8khQW >> j8GlugwvvqjO0uJ+43WCtpO9r4VgeaCGRGgeLrFuhXi0DxMQXwF0tpihYBmPPvyo >> Dp8f6LXWJ61O9D3UCSF8YVv0Nhx+Gv9za5QdOw6gAso+ZwdKfyxnIHtZf6HYivv8 >> 5IMPt+kWuYrX/AdwMgsDYDaldKiaCqX8+5mdI1u3K4cg+Sm9eGuwWmIms8XMcQya >> HAtJUo5kK3cNHvdPJbY4CbcAmtrHqRk6OMh/i6kuI3ybmgVhDyMq0XCtPpxf8yGK >> kIoX/gEjRkMeWonkbfjcRP3mGFiGoWd5UWhPh/KoAfcZgLhE8cAsRL6IDkLCWRk= >> =zOH7 >> -----END PGP SIGNATURE----- >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihrachys at redhat.com Fri Oct 17 08:38:21 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Fri, 17 Oct 2014 10:38:21 +0200 Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> <543F9BDA.5020307@redhat.com> <18690743.21da2.149187e63f8.Coremail.18661640013@163.com> <543F9E9D.1050803@redhat.com> <5440CF9C.7050601@redhat.com> Message-ID: <5440D57D.6060002@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 You've missed 'head' at the end of the command. On 17/10/14 10:36, Arash Kaffamanesh wrote: > .. wenn I run: [root at controller~(keystone_admin)]# > neutron-db-manage --config-file /etc/neutron/neutron.conf > --config-file /etc/neutron/plugin.ini upgrade > > I'm getting: > > You must provide a revision or relative delta > > any ideas? > > Thx -Arash > > On Fri, Oct 17, 2014 at 10:34 AM, Arash Kaffamanesh > > wrote: > > Ihar, thanks, much appreciated. When I run: > > > On Fri, Oct 17, 2014 at 10:13 AM, Ihar Hrachyshka > > wrote: > > On 16/10/14 18:12, Arash Kaffamanesh wrote: >> Just let you know, I did a yum upgrade on controller and compute >> nodes and the packages was upgraded to rc2 and rc3 packages, >> after that neutron didn't work on controller and I'd only to >> re-run packstack and reboot my instances and I was more than >> lucky :-) > > I suspect this is because you need to run db migration steps after > each update till the final release, otherwise you loose some db > migration steps, and service crashes. > > # neutron-db-manage \ --config-file /etc/neutron/neutron.conf \ > --config-file /etc/neutron/plugin.ini upgrade head > > /Ihar > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUQNV9AAoJEC5aWaUY1u57PHkH/0CdZGaGL0KFuAoA1Wp85JvO TD43ZfCgfhx4P9UxT96FpIOw7X4/QrD0Z/vrKn27+8yF1yHZTUZhG4zBZibgyjEu kEFeu+w43+0Ckfe/m1Wz0KI/SLkHcfgsiCXp6kfqvQEdjrriFrY3k1gD++dGzgEI MfMTNcliXimdZ1RR5EE9SdtvviZW8xLLmBpFClEzTKA9mPVaTQOlSu/SSVXv2v5Z ALWsshnN7X1Fb/Za8/VsJKQORO4EhZUB4zbL2jXd96tGgs7XoJeYpqrJUqAiUNVl nKVqGQHz5F8QnSzLkos8T3fWo7N0SMDP7EHqY9Ed2f8ZQrXYsngeD2zWcd8hhkw= =NheQ -----END PGP SIGNATURE----- From ihrachys at redhat.com Fri Oct 17 09:07:18 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Fri, 17 Oct 2014 11:07:18 +0200 Subject: [Rdo-list] how to add repository for the cerfitication test suite In-Reply-To: <2766FDEB4D6EC647B5ED0A96096A2C370FCF3D0BAC@MX10A.corp.emc.com> References: <2766FDEB4D6EC647B5ED0A96096A2C370FCF3D0BAC@MX10A.corp.emc.com> Message-ID: <5440DC46.5000504@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 This list is about RDO. Seems you use RHOSP5. I think it will be better for you to contact official Red Hat support to resolve your issues. I hope it helps, /Ihar On 17/10/14 10:30, Wan, Sam wrote: > Dear all, > > > > I?m engaged in redhat openstack test. > > When I read the user guide, it says to enable the test suite > repository with below commands: > > > > subscription-manager repos > --enable=rhel-7-server-openstack-5.0-cts-rpms > > > > Seems this does not work on my system: > > [root at redhat1 ~]# subscription-manager repos > --enable=rhel-7-server-openstack-5.0-cts-rpms > > Error: rhel-7-server-openstack-5.0-cts-rpms is not a valid repo ID. > Use --list option to see valid repos. > > [root at redhat1 ~]# > > > > There?s no cts in the repository > > [root at redhat1 yum.repos.d]# grep -i cts redhat.repo > > [root at redhat1 yum.repos.d]# > > > > Could you please tell me how to add the repository? > > > > Thanks and regards > > > Sam > > > > _______________________________________________ Rdo-list mailing > list Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUQNxGAAoJEC5aWaUY1u57tqoH/2Zf8d6Nk4i8QKg6D2BkzjnV MoI3dv3d1RYZ4FgBJ40zmAf3WAW+zL0IO5NmuaZCk+ZSNGKMF97ZCzCxxg2a+KwY xyQEtrnBNo972aGshS1IhBcGl1O8/kBe3FGjEcIUorwX0Sh6bv4MMJDLMOrXNG3S f8/nbMU7f+SPcXdMg/U3QjEN+ffgKptPMEWFuFdKaiFZfYEYvo6tY6Py9sNQHfWx bsAaOu/A66kYrdl8z1LFiCmpAm+lHsD91UohXoN7vuWyTrYuHcINOX82rV9rIUqr z3nNNr01u7zgJotytwi7hFHPDteJuMPRn4EasYoChuXXztN1Nz3U9XChu6dTNbw= =C94p -----END PGP SIGNATURE----- From Sam.Wan at emc.com Fri Oct 17 09:30:36 2014 From: Sam.Wan at emc.com (Wan, Sam) Date: Fri, 17 Oct 2014 05:30:36 -0400 Subject: [Rdo-list] how to add repository for the cerfitication test suite In-Reply-To: <5440DC46.5000504@redhat.com> References: <2766FDEB4D6EC647B5ED0A96096A2C370FCF3D0BAC@MX10A.corp.emc.com> <5440DC46.5000504@redhat.com> Message-ID: <2766FDEB4D6EC647B5ED0A96096A2C370FCF3D0BB2@MX10A.corp.emc.com> Hi Ihar, Thanks and regards Sam -----Original Message----- From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Ihar Hrachyshka Sent: Friday, October 17, 2014 5:07 PM To: rdo-list at redhat.com Subject: Re: [Rdo-list] how to add repository for the cerfitication test suite -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 This list is about RDO. Seems you use RHOSP5. I think it will be better for you to contact official Red Hat support to resolve your issues. I hope it helps, /Ihar On 17/10/14 10:30, Wan, Sam wrote: > Dear all, > > > > I?m engaged in redhat openstack test. > > When I read the user guide, it says to enable the test suite > repository with below commands: > > > > subscription-manager repos > --enable=rhel-7-server-openstack-5.0-cts-rpms > > > > Seems this does not work on my system: > > [root at redhat1 ~]# subscription-manager repos > --enable=rhel-7-server-openstack-5.0-cts-rpms > > Error: rhel-7-server-openstack-5.0-cts-rpms is not a valid repo ID. > Use --list option to see valid repos. > > [root at redhat1 ~]# > > > > There?s no cts in the repository > > [root at redhat1 yum.repos.d]# grep -i cts redhat.repo > > [root at redhat1 yum.repos.d]# > > > > Could you please tell me how to add the repository? > > > > Thanks and regards > > > Sam > > > > _______________________________________________ Rdo-list mailing list > Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUQNxGAAoJEC5aWaUY1u57tqoH/2Zf8d6Nk4i8QKg6D2BkzjnV MoI3dv3d1RYZ4FgBJ40zmAf3WAW+zL0IO5NmuaZCk+ZSNGKMF97ZCzCxxg2a+KwY xyQEtrnBNo972aGshS1IhBcGl1O8/kBe3FGjEcIUorwX0Sh6bv4MMJDLMOrXNG3S f8/nbMU7f+SPcXdMg/U3QjEN+ffgKptPMEWFuFdKaiFZfYEYvo6tY6Py9sNQHfWx bsAaOu/A66kYrdl8z1LFiCmpAm+lHsD91UohXoN7vuWyTrYuHcINOX82rV9rIUqr z3nNNr01u7zgJotytwi7hFHPDteJuMPRn4EasYoChuXXztN1Nz3U9XChu6dTNbw= =C94p -----END PGP SIGNATURE----- _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list From bbartlett at gmail.com Fri Oct 17 09:36:57 2014 From: bbartlett at gmail.com (Bill Bartlett) Date: Fri, 17 Oct 2014 02:36:57 -0700 Subject: [Rdo-list] RHEL OSP 5 neutron controller Message-ID: disclaimer: Both openstack on redhat and Foreman are new to me. I've got the cluster to a state where I'm able to launch instances, but all of the openstack-related packages are not installing correctly. When dealing with the neutron-controller, I am having difficulty getting swift to start. Many other services are up and running, but swift-proxy is complaining about log handlers which doesn't make much sense to me. Has anyone seen this and can point me to proper documentation on how to resolve it? Thanks, Bill My error log looks like this: Oct 17 09:06:16 mac60eb69edd808 puppet-agent[2056]: (/Stage[main]/Swift::Proxy/Service[swift-proxy]/ensure) ensure changed 'stopped' to 'running' Oct 17 09:06:16 mac60eb69edd808 proxy-server: Adding required filter dlo to pipeline at position 3 Oct 17 09:06:16 mac60eb69edd808 proxy-server: Adding required filter gatekeeper to pipeline at position 0 Oct 17 09:06:16 mac60eb69edd808 proxy-server: Adding required filter catch_errors to pipeline at position 0 Oct 17 09:06:16 mac60eb69edd808 proxy-server: Pipeline was modified. New pipeline is "catch_errors gatekeeper healthcheck memcache proxy_logging dlo keystoneclient.middleware.auth_token:filter_factory keystoneauth proxy_logging proxy". Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: No handlers could be found for logger "swift" Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: Traceback (most recent call last): Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: File "/usr/bin/swift-proxy-server", line 23, in Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: sys.exit(run_wsgi(conf_file, 'proxy-server', default_port=8080, **options)) Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line 389, in run_wsgi Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: loadapp(conf_path, global_conf=global_conf) Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line 323, in loadapp Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: return ctx.create() Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: File "/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 710, in create Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: return self.object_type.invoke(self) Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: File "/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 207, in invoke Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: app = filter(app) Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: File "/usr/lib/python2.7/site-packages/keystoneclient/middleware/auth_token.py", line 1516, in auth_filter Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: return AuthProtocol(app, conf) Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: File "/usr/lib/python2.7/site-packages/keystoneclient/middleware/auth_token.py", line 486, in __init__ Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: if netaddr.valid_ipv6(auth_host): Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: File "/usr/lib/python2.7/site-packages/netaddr/strategy/ipv6.py", line 126, in valid_str Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: raise AddrFormatError('Empty strings are not supported!') Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: netaddr.core.AddrFormatError: Empty strings are not supported! Oct 17 09:06:16 mac60eb69edd808 systemd: openstack-swift-proxy.service: main process exited, code=exited, status=1/FAILURE Oct 17 09:06:16 mac60eb69edd808 systemd: Unit openstack-swift-proxy.service entered failed state. proxy-server.conf # This file is managed by puppet. Do not edit # [DEFAULT] bind_port = 8080 bind_ip = 0.0.0.0 #bind_ip = workers = 4 user = swift log_name = swift log_facility = LOG_LOCAL1 log_level = INFO log_headers = False log_address = /dev/log [pipeline:main] pipeline = healthcheck cache proxy-logging authtoken keystone proxy-logging proxy-server [app:proxy-server] use = egg:swift#proxy set log_name = proxy-server set log_facility = LOG_LOCAL1 set log_level = INFO set log_address = /dev/log log_handoffs = true allow_account_management = true account_autocreate = true [filter:authtoken] log_name = swift signing_dir = /var/cache/swift paste.filter_factory = keystoneclient.middleware.auth_token:filter_factory auth_host = auth_port = 35357 auth_protocol = http auth_uri = http://:5000 # if its defined admin_tenant_name = services admin_user = swift admin_password = r3dapt delay_auth_decision = 1 cache = swift.cache include_service_catalog = False [filter:cache] use = egg:swift#memcache memcache_servers = 127.0.0.1:11211 [filter:catch_errors] use = egg:swift#catch_errors [filter:healthcheck] use = egg:swift#healthcheck [filter:ratelimit] use = egg:swift#ratelimit clock_accuracy = 1000 max_sleep_time_seconds = 60 log_sleep_time_seconds = 0 rate_buffer_seconds = 5 account_ratelimit = 0 [filter:proxy-logging] use = egg:swift#proxy_logging [filter:keystone] use = egg:swift#keystoneauth operator_roles = admin, SwiftOperator is_admin = true -------------- next part -------------- An HTML attachment was scrubbed... URL: From ak at cloudssky.com Fri Oct 17 09:48:58 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Fri, 17 Oct 2014 11:48:58 +0200 Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: <5440D57D.6060002@redhat.com> References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> <543F9BDA.5020307@redhat.com> <18690743.21da2.149187e63f8.Coremail.18661640013@163.com> <543F9E9D.1050803@redhat.com> <5440CF9C.7050601@redhat.com> <5440D57D.6060002@redhat.com> Message-ID: upps :-) thx again. So, as conclusion after any yum upgrade we need to run packstack again and do a neutron-db-manage like: [root at controller ~(keystone_admin)]# neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini upgrade head INFO [alembic.migration] Context impl MySQLImpl. INFO [alembic.migration] Will assume non-transactional DDL. INFO [alembic.migration] Running upgrade juno -> c00e3802ef7, empty message and openstack-service restart right? Now I've a small problem with the vnc console, it doesn't work anymore, in the vnc proxy log I see: 2014-10-12 06:08:46.583 23108 INFO nova.console.websocketproxy [req-83b79c9e-9f2f-467e-87fe-b73d589b9532 None] connecting to: :5900 2014-10-12 06:08:56.170 23106 INFO nova.console.websocketproxy [-] : ignoring empty handshake cirros needs a long time to come up, due to "failed to get instance-id of datasource": ??? cirros-ds 'net' up at 60.74 checking http://169.254.169.254/2009-04-04/instance-id failed 1/20: up 60.75. request failed failed 2/20: up 65.76. request failed .... failed 19/20: up 122.76. request failed failed 20/20: up 125.76. request failed failed to read iid from metadata. tried 20 no results found for mode=net. up 128.76. searched: nocloud configdrive ec2 failed to get instance-id of datasource Starting dropbear sshd: generating rsa key... generating dsa key... OK === system information === Platform: Fedora Project OpenStack Nova Tested that with CentOS image too, it seems to be a routing problem: cloud-init[778]: 2014-10-17 09:39:57,539 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: request error [[Errno 113] No route to host] cloud-init[778]: 2014-10-17 09:40:02,544 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 124 seconds cloud-init[778]: 2014-10-17 09:40:05,552 - url_helper.py[WARNING]: Calling 'http://20.0.0.1//latest/meta-data/instance-id' failed [3/120s]: request error [[Errno 113] No route to host] loud-init[778]: 2014-10-17 09:42:00,666 - url_helper.py[WARNING]: Calling 'http://20.0.0.1//latest/meta-data/instance-id' failed [118/120s]: request error [[Errno 113] No route to host] cloud-init[778]: 2014-10-17 09:42:05,672 - DataSourceCloudStack.py[CRITICAL]: Giving up on waiting for the metadata from ['http://20.0.0.1//latest/meta-data/instance-id'] after 123 seconds cloud-init[960]: Cloud-init v. 0.7.5 running 'modules:config' at Fri, 17 Oct 2014 09:42:07 +0000. Up 323.40 seconds. Thanks! -Arash On Fri, Oct 17, 2014 at 10:38 AM, Ihar Hrachyshka wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > You've missed 'head' at the end of the command. > > On 17/10/14 10:36, Arash Kaffamanesh wrote: > > .. wenn I run: [root at controller~(keystone_admin)]# > > neutron-db-manage --config-file /etc/neutron/neutron.conf > > --config-file /etc/neutron/plugin.ini upgrade > > > > I'm getting: > > > > You must provide a revision or relative delta > > > > any ideas? > > > > Thx -Arash > > > > On Fri, Oct 17, 2014 at 10:34 AM, Arash Kaffamanesh > > > wrote: > > > > Ihar, thanks, much appreciated. When I run: > > > > > > On Fri, Oct 17, 2014 at 10:13 AM, Ihar Hrachyshka > > > wrote: > > > > On 16/10/14 18:12, Arash Kaffamanesh wrote: > >> Just let you know, I did a yum upgrade on controller and compute > >> nodes and the packages was upgraded to rc2 and rc3 packages, > >> after that neutron didn't work on controller and I'd only to > >> re-run packstack and reboot my instances and I was more than > >> lucky :-) > >" > > I suspect this is because you need to run db migration steps after > > each update till the final release, otherwise you loose some db > > migration steps, and service crashes. > > > > # neutron-db-manage \ --config-file /etc/neutron/neutron.conf \ > > --config-file /etc/neutron/plugin.ini upgrade head > > > > /Ihar > > > > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > > iQEcBAEBCgAGBQJUQNV9AAoJEC5aWaUY1u57PHkH/0CdZGaGL0KFuAoA1Wp85JvO > TD43ZfCgfhx4P9UxT96FpIOw7X4/QrD0Z/vrKn27+8yF1yHZTUZhG4zBZibgyjEu > kEFeu+w43+0Ckfe/m1Wz0KI/SLkHcfgsiCXp6kfqvQEdjrriFrY3k1gD++dGzgEI > MfMTNcliXimdZ1RR5EE9SdtvviZW8xLLmBpFClEzTKA9mPVaTQOlSu/SSVXv2v5Z > ALWsshnN7X1Fb/Za8/VsJKQORO4EhZUB4zbL2jXd96tGgs7XoJeYpqrJUqAiUNVl > nKVqGQHz5F8QnSzLkos8T3fWo7N0SMDP7EHqY9Ed2f8ZQrXYsngeD2zWcd8hhkw= > =NheQ > -----END PGP SIGNATURE----- > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihrachys at redhat.com Fri Oct 17 09:53:55 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Fri, 17 Oct 2014 11:53:55 +0200 Subject: [Rdo-list] RHEL OSP 5 neutron controller In-Reply-To: References: Message-ID: <5440E733.6000204@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, I'm not a Swift guy, to say the least, but it seems your [filter-authtoken] is not configured properly [1] (missing auth_host). That said, you better ask official Red Hat support on why the file is not configured properly. This list is for RDO (community supported Openstack distribution) and not RHOSP (commercial version of Openstack from Red Hat). [1]: http://docs.openstack.org/trunk/config-reference/content/proxy-server-configuration.html Cheers, /Ihar On 17/10/14 11:36, Bill Bartlett wrote: > disclaimer: Both openstack on redhat and Foreman are new to me. > > I've got the cluster to a state where I'm able to launch instances, > but all of the openstack-related packages are not installing > correctly. When dealing with the neutron-controller, I am having > difficulty getting swift to start. Many other services are up and > running, but swift-proxy is complaining about log handlers which > doesn't make much sense to me. Has anyone seen this and can point > me to proper documentation on how to resolve it? > > Thanks, Bill > > My error log looks like this: > > > > Oct 17 09:06:16 mac60eb69edd808 puppet-agent[2056]: > (/Stage[main]/Swift::Proxy/Service[swift-proxy]/ensure) ensure > changed 'stopped' to 'running' Oct 17 09:06:16 mac60eb69edd808 > proxy-server: Adding required filter dlo to pipeline at position 3 > Oct 17 09:06:16 mac60eb69edd808 proxy-server: Adding required > filter gatekeeper to pipeline at position 0 Oct 17 09:06:16 > mac60eb69edd808 proxy-server: Adding required filter catch_errors > to pipeline at position 0 Oct 17 09:06:16 mac60eb69edd808 > proxy-server: Pipeline was modified. New pipeline is "catch_errors > gatekeeper healthcheck memcache proxy_logging dlo > keystoneclient.middleware.auth_token:filter_factory keystoneauth > proxy_logging proxy". Oct 17 09:06:16 mac60eb69edd808 > swift-proxy-server: No handlers could be found for logger "swift" > Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: Traceback > (most recent call last): Oct 17 09:06:16 mac60eb69edd808 > swift-proxy-server: File "/usr/bin/swift-proxy-server", line 23, in > Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: > sys.exit(run_wsgi(conf_file, 'proxy-server', default_port=8080, > **options)) Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: > File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line > 389, in run_wsgi Oct 17 09:06:16 mac60eb69edd808 > swift-proxy-server: loadapp(conf_path, global_conf=global_conf) Oct > 17 09:06:16 mac60eb69edd808 swift-proxy-server: File > "/usr/lib/python2.7/site-packages/swift/common/wsgi.py", line 323, > in loadapp Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: > return ctx.create() Oct 17 09:06:16 mac60eb69edd808 > swift-proxy-server: File > "/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line > 710, in create Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: > return self.object_type.invoke(self) Oct 17 09:06:16 > mac60eb69edd808 swift-proxy-server: File > "/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line > 207, in invoke Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: > app = filter(app) Oct 17 09:06:16 mac60eb69edd808 > swift-proxy-server: File > "/usr/lib/python2.7/site-packages/keystoneclient/middleware/auth_token.py", > > line 1516, in auth_filter > Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: return > AuthProtocol(app, conf) Oct 17 09:06:16 mac60eb69edd808 > swift-proxy-server: File > "/usr/lib/python2.7/site-packages/keystoneclient/middleware/auth_token.py", > > line 486, in __init__ > Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: if > netaddr.valid_ipv6(auth_host): Oct 17 09:06:16 mac60eb69edd808 > swift-proxy-server: File > "/usr/lib/python2.7/site-packages/netaddr/strategy/ipv6.py", line > 126, in valid_str Oct 17 09:06:16 mac60eb69edd808 > swift-proxy-server: raise AddrFormatError('Empty strings are not > supported!') Oct 17 09:06:16 mac60eb69edd808 swift-proxy-server: > netaddr.core.AddrFormatError: Empty strings are not supported! Oct > 17 09:06:16 mac60eb69edd808 systemd: > openstack-swift-proxy.service: main process exited, code=exited, > status=1/FAILURE Oct 17 09:06:16 mac60eb69edd808 systemd: Unit > openstack-swift-proxy.service entered failed state. > > > > > proxy-server.conf > > > > # This file is managed by puppet. Do not edit # [DEFAULT] > bind_port = 8080 > > bind_ip = 0.0.0.0 #bind_ip = > > workers = 4 user = swift log_name = swift log_facility = > LOG_LOCAL1 log_level = INFO log_headers = False log_address = > /dev/log > > > > [pipeline:main] pipeline = healthcheck cache proxy-logging > authtoken keystone proxy-logging proxy-server > > [app:proxy-server] use = egg:swift#proxy set log_name = > proxy-server set log_facility = LOG_LOCAL1 set log_level = INFO set > log_address = /dev/log log_handoffs = true allow_account_management > = true account_autocreate = true > > > > [filter:authtoken] log_name = swift signing_dir = /var/cache/swift > paste.filter_factory = > keystoneclient.middleware.auth_token:filter_factory auth_host = > auth_port = 35357 auth_protocol = http auth_uri = http://:5000 # if > its defined admin_tenant_name = services admin_user = swift > admin_password = r3dapt delay_auth_decision = 1 cache = > swift.cache include_service_catalog = False [filter:cache] use = > egg:swift#memcache memcache_servers = 127.0.0.1:11211 > [filter:catch_errors] use = > egg:swift#catch_errors > > > [filter:healthcheck] use = egg:swift#healthcheck > > [filter:ratelimit] use = egg:swift#ratelimit clock_accuracy = 1000 > max_sleep_time_seconds = 60 log_sleep_time_seconds = 0 > rate_buffer_seconds = 5 account_ratelimit = 0 > > [filter:proxy-logging] use = egg:swift#proxy_logging > > > [filter:keystone] use = egg:swift#keystoneauth operator_roles = > admin, SwiftOperator is_admin = true > > > > > > _______________________________________________ Rdo-list mailing > list Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUQOczAAoJEC5aWaUY1u57L38H/0FYu7NotUxzTtojrZaKs8u8 joIzoXBuUvBy8R3HJ9AxX4Fp6mYQE7swcMbI8NZAfVcIiuzD0OtD0EILkp0hulU1 GSEbjI3SV+oaSU46s7sMQ0OS5b1/hzUwrlqMZ6fbKz75hO/85pwKLULJ9xVwCDPn XUpzHcK/L7B0ig5aBhm3N5DaAoRglJfKxWsyEi9/hh2Yw6NTK51Xeo5m0oYRlx1V sBTi522WXkNBPh84319ukE2POZSnCF9rV6E2f8mDpnDrB6BMx+uFL0feRLd+QURr h7ew/ttTdZyxpBozxAGUlSr3W+tfsFBreD89JItI8DMvNocdX7a010o1+N819mA= =lSWo -----END PGP SIGNATURE----- From ak at cloudssky.com Fri Oct 17 10:13:14 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Fri, 17 Oct 2014 12:13:14 +0200 Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> <543F9BDA.5020307@redhat.com> <18690743.21da2.149187e63f8.Coremail.18661640013@163.com> <543F9E9D.1050803@redhat.com> <5440CF9C.7050601@redhat.com> <5440D57D.6060002@redhat.com> Message-ID: a reboot of the controller solved the routing problem and I can associate floating ips and CentOS comes up very quickly, only the console issue still exists. Now I'll try to do an AIO install on a CentOS VM with the latest packages and see if the console issue appears by the fresh install. On Fri, Oct 17, 2014 at 11:48 AM, Arash Kaffamanesh wrote: > upps :-) thx again. > > So, as conclusion after any yum upgrade we need to run packstack again > and do a neutron-db-manage like: > > [root at controller ~(keystone_admin)]# neutron-db-manage --config-file > /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini upgrade head > INFO [alembic.migration] Context impl MySQLImpl. > INFO [alembic.migration] Will assume non-transactional DDL. > INFO [alembic.migration] Running upgrade juno -> c00e3802ef7, empty > message > > and openstack-service restart > > right? > > Now I've a small problem with the vnc console, it doesn't work anymore, in > the vnc proxy log I see: > > 2014-10-12 06:08:46.583 23108 INFO nova.console.websocketproxy > [req-83b79c9e-9f2f-467e-87fe-b73d589b9532 None] connecting to: > :5900 > 2014-10-12 06:08:56.170 23106 INFO nova.console.websocketproxy [-] > : ignoring empty handshake > > cirros needs a long time to come up, due to "failed to get instance-id of > datasource": ??? > > cirros-ds 'net' up at 60.74 > > checking http://169.254.169.254/2009-04-04/instance-id > failed 1/20: up 60.75. request failed > failed 2/20: up 65.76. request failed > .... > > failed 19/20: up 122.76. request failed > failed 20/20: up 125.76. request failed > failed to read iid from metadata. tried 20 > no results found for mode=net. up 128.76. searched: nocloud configdrive ec2 > failed to get instance-id of datasource > Starting dropbear sshd: generating rsa key... generating dsa key... OK > === system information === > Platform: Fedora Project OpenStack Nova > > > Tested that with CentOS image too, it seems to be a routing problem: > > cloud-init[778]: 2014-10-17 09:39:57,539 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: request error [[Errno 113] No route to host] > cloud-init[778]: 2014-10-17 09:40:02,544 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 124 seconds > cloud-init[778]: 2014-10-17 09:40:05,552 - url_helper.py[WARNING]: Calling 'http://20.0.0.1//latest/meta-data/instance-id' failed [3/120s]: request error [[Errno 113] No route to host] > > loud-init[778]: 2014-10-17 09:42:00,666 - url_helper.py[WARNING]: Calling 'http://20.0.0.1//latest/meta-data/instance-id' failed [118/120s]: request error [[Errno 113] No route to host] > cloud-init[778]: 2014-10-17 09:42:05,672 - DataSourceCloudStack.py[CRITICAL]: Giving up on waiting for the metadata from ['http://20.0.0.1//latest/meta-data/instance-id'] after 123 seconds > cloud-init[960]: Cloud-init v. 0.7.5 running 'modules:config' at Fri, 17 Oct 2014 09:42:07 +0000. Up 323.40 seconds. > > Thanks! > -Arash > > On Fri, Oct 17, 2014 at 10:38 AM, Ihar Hrachyshka > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA512 >> >> You've missed 'head' at the end of the command. >> >> On 17/10/14 10:36, Arash Kaffamanesh wrote: >> > .. wenn I run: [root at controller~(keystone_admin)]# >> > neutron-db-manage --config-file /etc/neutron/neutron.conf >> > --config-file /etc/neutron/plugin.ini upgrade >> > >> > I'm getting: >> > >> > You must provide a revision or relative delta >> > >> > any ideas? >> > >> > Thx -Arash >> > >> > On Fri, Oct 17, 2014 at 10:34 AM, Arash Kaffamanesh >> > > wrote: >> > >> > Ihar, thanks, much appreciated. When I run: >> > >> > >> > On Fri, Oct 17, 2014 at 10:13 AM, Ihar Hrachyshka >> > > wrote: >> > >> > On 16/10/14 18:12, Arash Kaffamanesh wrote: >> >> Just let you know, I did a yum upgrade on controller and compute >> >> nodes and the packages was upgraded to rc2 and rc3 packages, >> >> after that neutron didn't work on controller and I'd only to >> >> re-run packstack and reboot my instances and I was more than >> >> lucky :-) >> >" >> > I suspect this is because you need to run db migration steps after >> > each update till the final release, otherwise you loose some db >> > migration steps, and service crashes. >> > >> > # neutron-db-manage \ --config-file /etc/neutron/neutron.conf \ >> > --config-file /etc/neutron/plugin.ini upgrade head >> > >> > /Ihar >> > >> > >> > >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG/MacGPG2 v2.0.22 (Darwin) >> >> iQEcBAEBCgAGBQJUQNV9AAoJEC5aWaUY1u57PHkH/0CdZGaGL0KFuAoA1Wp85JvO >> TD43ZfCgfhx4P9UxT96FpIOw7X4/QrD0Z/vrKn27+8yF1yHZTUZhG4zBZibgyjEu >> kEFeu+w43+0Ckfe/m1Wz0KI/SLkHcfgsiCXp6kfqvQEdjrriFrY3k1gD++dGzgEI >> MfMTNcliXimdZ1RR5EE9SdtvviZW8xLLmBpFClEzTKA9mPVaTQOlSu/SSVXv2v5Z >> ALWsshnN7X1Fb/Za8/VsJKQORO4EhZUB4zbL2jXd96tGgs7XoJeYpqrJUqAiUNVl >> nKVqGQHz5F8QnSzLkos8T3fWo7N0SMDP7EHqY9Ed2f8ZQrXYsngeD2zWcd8hhkw= >> =NheQ >> -----END PGP SIGNATURE----- >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihrachys at redhat.com Fri Oct 17 10:13:13 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Fri, 17 Oct 2014 12:13:13 +0200 Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> <543F9BDA.5020307@redhat.com> <18690743.21da2.149187e63f8.Coremail.18661640013@163.com> <543F9E9D.1050803@redhat.com> <5440CF9C.7050601@redhat.com> <5440D57D.6060002@redhat.com> Message-ID: <5440EBB9.10202@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 17/10/14 11:48, Arash Kaffamanesh wrote: > upps :-) thx again. > > ** > > So, as conclusion after any yum upgrade we need to run packstack > again and do a neutron-db-manage like: > > [root at controller ~(keystone_admin)]# neutron-db-manage > --config-file /etc/neutron/neutron.conf --config-file > /etc/neutron/plugin.ini upgrade head INFO [alembic.migration] > Context impl MySQLImpl. INFO [alembic.migration] Will assume > non-transactional DDL. INFO [alembic.migration] Running upgrade > juno -> c00e3802ef7, empty message > > and openstack-service restart > > right? Yes, though it's valid only for pre-release updates. Once Juno is settled, you should not run migrations after each update because it's guaranteed there are no such updates that touch database schema in stable branches. /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUQOu5AAoJEC5aWaUY1u57aHQIALrfVveqVWu996mjyuIFtFZ4 LcM0nXDQbM/DUC52r+6kltaKVtucrURFBCUMZh5kGjyMvNMJulG0pLA3F7Qj0pMx O+konHe9E1coCJCxJN+STNiUwjf/3pquoUt31gQ8vJKRyYZkzQnAvyyzOCb39ZfC fKQ8Q8Q/OkO6kC67vPTfu9NLIlXlMqVKMAeDcf/qs8JG5o2FRNCMeeNk4snMsYnS q4a0x2k3hKKfAMNBLabplY/UqAmK/l0NH+hRxd7c0Od1LjcEgeVmaY94tnMqU3O9 tw/Crrvz3mLI5M/8g4r+s1C8CnGS3NMcFkt0etfcHOgFTBGRGHP7r986Xl3TUiM= =KHXr -----END PGP SIGNATURE----- From apevec at gmail.com Fri Oct 17 11:01:20 2014 From: apevec at gmail.com (Alan Pevec) Date: Fri, 17 Oct 2014 13:01:20 +0200 Subject: [Rdo-list] When will RDO for Juno release be officially available? In-Reply-To: <5440EBB9.10202@redhat.com> References: <69cc2062.1923d.149181f0578.Coremail.18661640013@163.com> <543F9BDA.5020307@redhat.com> <18690743.21da2.149187e63f8.Coremail.18661640013@163.com> <543F9E9D.1050803@redhat.com> <5440CF9C.7050601@redhat.com> <5440D57D.6060002@redhat.com> <5440EBB9.10202@redhat.com> Message-ID: >> So, as conclusion after any yum upgrade we need to run packstack >> again and do a neutron-db-manage like: There's handy shortcut with openstack-utils: openstack-db --service --update >> and openstack-service restart >> >> right? > > Yes, though it's valid only for pre-release updates. Once Juno is > settled, you should not run migrations after each update because it's > guaranteed there are no such updates that touch database schema in > stable branches. Correct that would be a regression and should fail CI tests. Cheers, Alan From Yaniv.Kaul at emc.com Sun Oct 19 14:36:11 2014 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Sun, 19 Oct 2014 10:36:11 -0400 Subject: [Rdo-list] Tempest_config failure (RDO, Juno, CentOS 7 - heat related?) Message-ID: <648473255763364B961A02AC3BE1060D03C79414FD@MX19A.corp.emc.com> Running: [root at lgdrm989 etc]# source ~/keystonerc_admin [root at lgdrm989 etc(keystone_admin)]# nova list +----+------+--------+------------+-------------+----------+ | ID | Name | Status | Task State | Power State | Networks | +----+------+--------+------------+-------------+----------+ +----+------+--------+------------+-------------+----------+ And then: [root at lgdrm989 tempest(keystone_admin)]# tools/config_tempest.py --create identity.uri $OS_AUTH_URL identity.admin_username $OS_USERNAME identity.admin_password $OS_PASSWORD identity.admin_tenant_name $OS_TENANT_NAME Traceback (most recent call last): File "tools/config_tempest.py", line 639, in main() File "tools/config_tempest.py", line 132, in main create_tempest_users(clients.identity, conf) File "tools/config_tempest.py", line 334, in create_tempest_users role_name='heat_stack_owner') File "tools/config_tempest.py", line 346, in give_role_to_user role_id = identity_client.roles.find(name=role_name) File "/usr/lib/python2.7/site-packages/keystoneclient/base.py", line 247, in find raise exceptions.NotFound(404, msg) keystoneclient.openstack.common.apiclient.exceptions.NotFound: 404 (HTTP 404) I do NOT install Heat, perhaps it's related? [root at lgdrm989 tempest(keystone_admin)]# keystone role-list +----------------------------------+----------+ | id | name | +----------------------------------+----------+ | 9fe2ff9ee4384b1894a90878d3e92bab | _member_ | | 8fa13b71c3254144b49f1c499524be0c | admin | +----------------------------------+----------+ [root at lgdrm989 tempest(keystone_admin)]# keystone user-list +----------------------------------+--------+---------+------------------+ | id | name | enabled | email | +----------------------------------+--------+---------+------------------+ | 806cd3634fa94581ac8d20919a86f710 | admin | True | test at test.com | | 79c6083783584fada7332a6f693e1774 | cinder | True | cinder at localhost | | 82daa98d0daa425c909497f9d32c8a07 | demo | True | | | 7e079b6e4efc4769bc9648c658780c59 | glance | True | glance at localhost | | 7d1a0e4fcd364ca082d2e597c0a34c1a | nova | True | nova at localhost | +----------------------------------+--------+---------+------------------+ root at lgdrm989 tempest(keystone_admin)]# keystone service-list +----------------------------------+-----------+-----------+------------------------------+ | id | name | type | description | +----------------------------------+-----------+-----------+------------------------------+ | 14190e80d56c4176a1d4c60e8563650d | cinder | volume | Cinder Service | | fc14c944de514eb88b591ce7ff8bb826 | cinder_v2 | volumev2 | Cinder Service v2 | | 9ac090072dc646af8b261239780aa7c0 | cinderv2 | volumev2 | Cinder Service v2 | | 2ec4393131904ff3a8cafa5e279f179c | glance | image | Openstack Image Service | | 8a3a0ac642114f31b0887c128638b3e9 | keystone | identity | OpenStack Identity Service | | f7ddf444e0a3403ab3f4eede18896191 | nova | compute | Openstack Compute Service | | 2ce4889813334843ad1c8b3b981d4caf | nova_ec2 | ec2 | EC2 Service | | 7710317d65724318a364cd93cc6d51b2 | novav3 | computev3 | Openstack Compute Service v3 | +----------------------------------+-----------+-----------+------------------------------+ From Yaniv.Kaul at emc.com Mon Oct 20 11:36:02 2014 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Mon, 20 Oct 2014 07:36:02 -0400 Subject: [Rdo-list] Tempest_config failure (RDO, Juno, CentOS 7 - heat related?) Message-ID: <648473255763364B961A02AC3BE1060D03C79415F5@MX19A.corp.emc.com> Opened https://bugzilla.redhat.com/show_bug.cgi?id=1154633 on the issue. Y. > -----Original Message----- > From: Kaul, Yaniv > Sent: Sunday, October 19, 2014 5:36 PM > To: rdo-list at redhat.com > Subject: Tempest_config failure (RDO, Juno, CentOS 7 - heat related?) > > Running: > > > [root at lgdrm989 etc]# source ~/keystonerc_admin > [root at lgdrm989 etc(keystone_admin)]# nova list > +----+------+--------+------------+-------------+----------+ > | ID | Name | Status | Task State | Power State | Networks | > +----+------+--------+------------+-------------+----------+ > +----+------+--------+------------+-------------+----------+ > > > And then: > > [root at lgdrm989 tempest(keystone_admin)]# tools/config_tempest.py --create > identity.uri $OS_AUTH_URL identity.admin_username $OS_USERNAME > identity.admin_password $OS_PASSWORD identity.admin_tenant_name > $OS_TENANT_NAME Traceback (most recent call last): > File "tools/config_tempest.py", line 639, in > main() > File "tools/config_tempest.py", line 132, in main > create_tempest_users(clients.identity, conf) > File "tools/config_tempest.py", line 334, in create_tempest_users > role_name='heat_stack_owner') > File "tools/config_tempest.py", line 346, in give_role_to_user > role_id = identity_client.roles.find(name=role_name) > File "/usr/lib/python2.7/site-packages/keystoneclient/base.py", line 247, in > find > raise exceptions.NotFound(404, msg) > keystoneclient.openstack.common.apiclient.exceptions.NotFound: 404 (HTTP > 404) > > > > I do NOT install Heat, perhaps it's related? > > [root at lgdrm989 tempest(keystone_admin)]# keystone role-list > +----------------------------------+----------+ > | id | name | > +----------------------------------+----------+ > | 9fe2ff9ee4384b1894a90878d3e92bab | _member_ | > | 8fa13b71c3254144b49f1c499524be0c | admin | > +----------------------------------+----------+ > [root at lgdrm989 tempest(keystone_admin)]# keystone user-list > +----------------------------------+--------+---------+------------------+ > | id | name | enabled | email | > +----------------------------------+--------+---------+------------------+ > | 806cd3634fa94581ac8d20919a86f710 | admin | True | test at test.com | > | 79c6083783584fada7332a6f693e1774 | cinder | True | cinder at localhost | > | 82daa98d0daa425c909497f9d32c8a07 | demo | True | | > | 7e079b6e4efc4769bc9648c658780c59 | glance | True | glance at localhost | > | 7d1a0e4fcd364ca082d2e597c0a34c1a | nova | True | nova at localhost | > +----------------------------------+--------+---------+------------------+ > root at lgdrm989 tempest(keystone_admin)]# keystone service-list > +----------------------------------+-----------+-----------+------------------------------+ > | id | name | type | description | > +----------------------------------+-----------+-----------+------------------------------+ > | 14190e80d56c4176a1d4c60e8563650d | cinder | volume | Cinder > Service | > | fc14c944de514eb88b591ce7ff8bb826 | cinder_v2 | volumev2 | Cinder > Service v2 | > | 9ac090072dc646af8b261239780aa7c0 | cinderv2 | volumev2 | Cinder > Service v2 | > | 2ec4393131904ff3a8cafa5e279f179c | glance | image | Openstack > Image Service | > | 8a3a0ac642114f31b0887c128638b3e9 | keystone | identity | OpenStack > Identity Service | > | f7ddf444e0a3403ab3f4eede18896191 | nova | compute | Openstack > Compute Service | > | 2ce4889813334843ad1c8b3b981d4caf | nova_ec2 | ec2 | EC2 > Service | > | 7710317d65724318a364cd93cc6d51b2 | novav3 | computev3 | Openstack > Compute Service v3 | > +----------------------------------+-----------+-----------+------------------------------+ From rdo-info at redhat.com Mon Oct 20 14:31:54 2014 From: rdo-info at redhat.com (RDO Forum) Date: Mon, 20 Oct 2014 14:31:54 +0000 Subject: [Rdo-list] [RDO] Blog roundup, week of October 13 Message-ID: <000001492df8b3ec-bcbb47e7-ac80-4682-bf1c-0b5ee395d35b-000000@email.amazonses.com> rbowen started a discussion. Blog roundup, week of October 13 --- Follow the link below to check it out: https://openstack.redhat.com/forum/discussion/990/blog-roundup-week-of-october-13 Have a great day! From rbowen at redhat.com Mon Oct 20 17:07:43 2014 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 20 Oct 2014 13:07:43 -0400 Subject: [Rdo-list] RDO-related Meetups in the coming week (October 20, 2014) Message-ID: <5445415F.2040901@redhat.com> The following are the meetups I'm aware of in the coming week where RDO enthusiasts will be gathering. If you know of others, please let me know, and/or add them to http://openstack.redhat.com/Events If you attend any of these meetups, please take pictures, and send me some. If you blog about the events (and you should), please send me that, too. * Tuesday, October 21 - Sydney - http://www.meetup.com/Australian-OpenStack-User-Group/events/210190072/ Sydney OpenStack Meetup * Thursday, October 23 - Helsinki - http://www.meetup.com/OpenStack-Finland-User-Group/events/203219072/ 3rd OpenStackFin User Group meetup * Thursday, October 23 - Seattle - http://www.meetup.com/OpenStack-Seattle/events/198405682/ OpenStack Seattle Meetup * Thursday, October 23 - Pasadena, CA - http://www.meetup.com/OpenStack-LA/events/211212902/ Under the Hood with Nova, Libvirt, and KVM * Thursday, October 23 - Lindon, UT - http://www.meetup.com/openstack-utah/events/212292712/ OpenStack Utah Meetup * Friday, October 24 - Pittsburgh, PA - http://www.meetup.com/openstack-pittsburgh/events/210499422/ OpenStack 101 * Monday, October 27 - Brisbane, Queensland - http://www.meetup.com/qldjvm/events/213724692/ Red Hat Open Day And, of course, don't forget that the OpenStack Summit, in Paris, is just two weeks away! http://openstack.org/summit -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From unke at b1-systems.de Mon Oct 20 19:00:34 2014 From: unke at b1-systems.de (Michael Unke) Date: Mon, 20 Oct 2014 21:00:34 +0200 Subject: [Rdo-list] http URL to RDO-repository Message-ID: <54455BD2.9060009@b1-systems.de> Dear all, is there an alternative URL to the RDO repos other than https://repos.fedorapeople.org/repos/openstack/... ? We currently (since last week) have problems syncing this https repository, so a http mirror would be fine. Thanks in advance, Mike -- Michael Unke Mail: unke at b1-systems.de B1 Systems GmbH Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 From dkranz at redhat.com Mon Oct 20 20:17:30 2014 From: dkranz at redhat.com (David Kranz) Date: Mon, 20 Oct 2014 16:17:30 -0400 Subject: [Rdo-list] Tempest_config failure (RDO, Juno, CentOS 7 - heat related?) In-Reply-To: <648473255763364B961A02AC3BE1060D03C79415F5@MX19A.corp.emc.com> References: <648473255763364B961A02AC3BE1060D03C79415F5@MX19A.corp.emc.com> Message-ID: <54456DDA.3060201@redhat.com> On 10/20/2014 07:36 AM, Kaul, Yaniv wrote: > Opened https://bugzilla.redhat.com/show_bug.cgi?id=1154633 on the issue. > Y. This should be fixed now. -David >> -----Original Message----- >> From: Kaul, Yaniv >> Sent: Sunday, October 19, 2014 5:36 PM >> To: rdo-list at redhat.com >> Subject: Tempest_config failure (RDO, Juno, CentOS 7 - heat related?) >> >> Running: >> >> >> [root at lgdrm989 etc]# source ~/keystonerc_admin >> [root at lgdrm989 etc(keystone_admin)]# nova list >> +----+------+--------+------------+-------------+----------+ >> | ID | Name | Status | Task State | Power State | Networks | >> +----+------+--------+------------+-------------+----------+ >> +----+------+--------+------------+-------------+----------+ >> >> >> And then: >> >> [root at lgdrm989 tempest(keystone_admin)]# tools/config_tempest.py --create >> identity.uri $OS_AUTH_URL identity.admin_username $OS_USERNAME >> identity.admin_password $OS_PASSWORD identity.admin_tenant_name >> $OS_TENANT_NAME Traceback (most recent call last): >> File "tools/config_tempest.py", line 639, in >> main() >> File "tools/config_tempest.py", line 132, in main >> create_tempest_users(clients.identity, conf) >> File "tools/config_tempest.py", line 334, in create_tempest_users >> role_name='heat_stack_owner') >> File "tools/config_tempest.py", line 346, in give_role_to_user >> role_id = identity_client.roles.find(name=role_name) >> File "/usr/lib/python2.7/site-packages/keystoneclient/base.py", line 247, in >> find >> raise exceptions.NotFound(404, msg) >> keystoneclient.openstack.common.apiclient.exceptions.NotFound: 404 (HTTP >> 404) >> >> >> >> I do NOT install Heat, perhaps it's related? >> >> [root at lgdrm989 tempest(keystone_admin)]# keystone role-list >> +----------------------------------+----------+ >> | id | name | >> +----------------------------------+----------+ >> | 9fe2ff9ee4384b1894a90878d3e92bab | _member_ | >> | 8fa13b71c3254144b49f1c499524be0c | admin | >> +----------------------------------+----------+ >> [root at lgdrm989 tempest(keystone_admin)]# keystone user-list >> +----------------------------------+--------+---------+------------------+ >> | id | name | enabled | email | >> +----------------------------------+--------+---------+------------------+ >> | 806cd3634fa94581ac8d20919a86f710 | admin | True | test at test.com | >> | 79c6083783584fada7332a6f693e1774 | cinder | True | cinder at localhost | >> | 82daa98d0daa425c909497f9d32c8a07 | demo | True | | >> | 7e079b6e4efc4769bc9648c658780c59 | glance | True | glance at localhost | >> | 7d1a0e4fcd364ca082d2e597c0a34c1a | nova | True | nova at localhost | >> +----------------------------------+--------+---------+------------------+ >> root at lgdrm989 tempest(keystone_admin)]# keystone service-list >> +----------------------------------+-----------+-----------+------------------------------+ >> | id | name | type | description | >> +----------------------------------+-----------+-----------+------------------------------+ >> | 14190e80d56c4176a1d4c60e8563650d | cinder | volume | Cinder >> Service | >> | fc14c944de514eb88b591ce7ff8bb826 | cinder_v2 | volumev2 | Cinder >> Service v2 | >> | 9ac090072dc646af8b261239780aa7c0 | cinderv2 | volumev2 | Cinder >> Service v2 | >> | 2ec4393131904ff3a8cafa5e279f179c | glance | image | Openstack >> Image Service | >> | 8a3a0ac642114f31b0887c128638b3e9 | keystone | identity | OpenStack >> Identity Service | >> | f7ddf444e0a3403ab3f4eede18896191 | nova | compute | Openstack >> Compute Service | >> | 2ce4889813334843ad1c8b3b981d4caf | nova_ec2 | ec2 | EC2 >> Service | >> | 7710317d65724318a364cd93cc6d51b2 | novav3 | computev3 | Openstack >> Compute Service v3 | >> +----------------------------------+-----------+-----------+------------------------------+ > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list From Yaniv.Kaul at emc.com Mon Oct 20 20:28:51 2014 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Mon, 20 Oct 2014 16:28:51 -0400 Subject: [Rdo-list] Tempest_config failure (RDO, Juno, CentOS 7 - heat related?) In-Reply-To: <54456DDA.3060201@redhat.com> References: <648473255763364B961A02AC3BE1060D03C79415F5@MX19A.corp.emc.com> <54456DDA.3060201@redhat.com> Message-ID: <648473255763364B961A02AC3BE1060D03C79416E3@MX19A.corp.emc.com> > -----Original Message----- > From: David Kranz [mailto:dkranz at redhat.com] > Sent: Monday, October 20, 2014 11:18 PM > To: Kaul, Yaniv; rdo-list at redhat.com > Subject: Re: [Rdo-list] Tempest_config failure (RDO, Juno, CentOS 7 - heat > related?) > > On 10/20/2014 07:36 AM, Kaul, Yaniv wrote: > > Opened https://bugzilla.redhat.com/show_bug.cgi?id=1154633 on the issue. > > Y. > This should be fixed now. I assume by https://github.com/redhat-openstack/tempest/commit/decba3e4238f8716e3f16e54478e18b1cf88e1ee - but that's not on the Juno branch? Y. > > -David > >> -----Original Message----- > >> From: Kaul, Yaniv > >> Sent: Sunday, October 19, 2014 5:36 PM > >> To: rdo-list at redhat.com > >> Subject: Tempest_config failure (RDO, Juno, CentOS 7 - heat related?) > >> > >> Running: > >> > >> > >> [root at lgdrm989 etc]# source ~/keystonerc_admin > >> [root at lgdrm989 etc(keystone_admin)]# nova list > >> +----+------+--------+------------+-------------+----------+ > >> | ID | Name | Status | Task State | Power State | Networks | > >> +----+------+--------+------------+-------------+----------+ > >> +----+------+--------+------------+-------------+----------+ > >> > >> > >> And then: > >> > >> [root at lgdrm989 tempest(keystone_admin)]# tools/config_tempest.py > >> --create identity.uri $OS_AUTH_URL identity.admin_username > >> $OS_USERNAME identity.admin_password $OS_PASSWORD > >> identity.admin_tenant_name $OS_TENANT_NAME Traceback (most recent > call last): > >> File "tools/config_tempest.py", line 639, in > >> main() > >> File "tools/config_tempest.py", line 132, in main > >> create_tempest_users(clients.identity, conf) > >> File "tools/config_tempest.py", line 334, in create_tempest_users > >> role_name='heat_stack_owner') > >> File "tools/config_tempest.py", line 346, in give_role_to_user > >> role_id = identity_client.roles.find(name=role_name) > >> File "/usr/lib/python2.7/site-packages/keystoneclient/base.py", > >> line 247, in find > >> raise exceptions.NotFound(404, msg) > >> keystoneclient.openstack.common.apiclient.exceptions.NotFound: 404 > >> (HTTP > >> 404) > >> > >> > >> > >> I do NOT install Heat, perhaps it's related? > >> > >> [root at lgdrm989 tempest(keystone_admin)]# keystone role-list > >> +----------------------------------+----------+ > >> | id | name | > >> +----------------------------------+----------+ > >> | 9fe2ff9ee4384b1894a90878d3e92bab | _member_ | > >> | 8fa13b71c3254144b49f1c499524be0c | admin | > >> +----------------------------------+----------+ > >> [root at lgdrm989 tempest(keystone_admin)]# keystone user-list > >> +----------------------------------+--------+---------+------------------+ > >> | id | name | enabled | email | > >> +----------------------------------+--------+---------+------------------+ > >> | 806cd3634fa94581ac8d20919a86f710 | admin | True | test at test.com > | > >> | 79c6083783584fada7332a6f693e1774 | cinder | True | > cinder at localhost | > >> | 82daa98d0daa425c909497f9d32c8a07 | demo | True | | > >> | 7e079b6e4efc4769bc9648c658780c59 | glance | True | > glance at localhost | > >> | 7d1a0e4fcd364ca082d2e597c0a34c1a | nova | True | nova at localhost > | > >> +----------------------------------+--------+---------+------------------+ > >> root at lgdrm989 tempest(keystone_admin)]# keystone service-list > >> +----------------------------------+-----------+-----------+------------------------------+ > >> | id | name | type | description | > >> +----------------------------------+-----------+-----------+------------------------------+ > >> | 14190e80d56c4176a1d4c60e8563650d | cinder | volume | Cinder > >> Service | > >> | fc14c944de514eb88b591ce7ff8bb826 | cinder_v2 | volumev2 | Cinder > >> Service v2 | > >> | 9ac090072dc646af8b261239780aa7c0 | cinderv2 | volumev2 | Cinder > >> Service v2 | > >> | 2ec4393131904ff3a8cafa5e279f179c | glance | image | Openstack > >> Image Service | > >> | 8a3a0ac642114f31b0887c128638b3e9 | keystone | identity | > >> | OpenStack > >> Identity Service | > >> | f7ddf444e0a3403ab3f4eede18896191 | nova | compute | Openstack > >> Compute Service | > >> | 2ce4889813334843ad1c8b3b981d4caf | nova_ec2 | ec2 | EC2 > >> Service | > >> | 7710317d65724318a364cd93cc6d51b2 | novav3 | computev3 | > Openstack > >> Compute Service v3 | > >> +----------------------------------+-----------+-----------+------------------------------+ > > _______________________________________________ > > Rdo-list mailing list > > Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list From pbrady at redhat.com Tue Oct 21 11:41:59 2014 From: pbrady at redhat.com (=?ISO-8859-15?Q?P=E1draig_Brady?=) Date: Tue, 21 Oct 2014 12:41:59 +0100 Subject: [Rdo-list] http URL to RDO-repository In-Reply-To: <54455BD2.9060009@b1-systems.de> References: <54455BD2.9060009@b1-systems.de> Message-ID: <54464687.9050401@redhat.com> On 10/20/2014 08:00 PM, Michael Unke wrote: > Dear all, > > is there an alternative URL to the RDO repos other than > https://repos.fedorapeople.org/repos/openstack/... ? > > We currently (since last week) have problems syncing this https repository, so a http mirror would be fine. Yes the fedorapeople SSL settings were recently updated in response to poodle etc. What platform are you having issue with? I tried platforms to see where this hits, using: curl -LIv http://rdo.fedorapeople.org/ I get good connections on Fedora20, RHEL6 and Centos7 with: SSL connection using TLS_DHE_RSA_WITH_AES_128_CBC_SHA Going back to an Fedora 15 VM I get: SSL connect error, NSS error -8092 Now it's the negotiation and fallback logic that was affected in the recent poodle issue, so you may be able to specify the cipher directly to avoid the issue on older plaforms. For example on the problematic Fedora 15 VM above we can still get a connection using the appropriate NSS cipher name: curl -LIv --ciphers rsa_aes_128_sha http://rdo.fedorapeople.org/ P?draig. From rbowen at redhat.com Tue Oct 21 18:14:29 2014 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 21 Oct 2014 14:14:29 -0400 Subject: [Rdo-list] Speakers wanted for OpenStack Live Conference (April 13-14, 2015, Santa Clara, CA) Message-ID: <5446A285.80603@redhat.com> I've been asked to spread the word about an event upcoming in April, in Santa Clara, CA, USA, which is looking for speakers on a variety of OpenStack topics. They're looking for technology-focused (ie, vendor-neutral) presentations, and specific topics are suggested on the CFP page. Conference site: https://www.percona.com/live/openstack-live-2015/ CFP: https://www.percona.com/live/openstack-live-2015/user/register The CFP closes November 17th. They're looking for: Tutorial tracks: -Deploying OpenStack -Trove -High Availability -OpenStack Upgrades -Operations: Management and Monitoring OpenStack -Tuning Optimization and benchmarking of OpenStack Breakout tracks: -Operations -High Availability -Performance Optimization -Replication and Backup -Trove -Monitoring and Tools -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From rohara at redhat.com Wed Oct 22 03:38:17 2014 From: rohara at redhat.com (Ryan O'Hara) Date: Tue, 21 Oct 2014 22:38:17 -0500 Subject: [Rdo-list] Speakers wanted for OpenStack Live Conference (April 13-14, 2015, Santa Clara, CA) In-Reply-To: <5446A285.80603@redhat.com> References: <5446A285.80603@redhat.com> Message-ID: <20141022033817.GA20777@redhat.com> On Tue, Oct 21, 2014 at 02:14:29PM -0400, Rich Bowen wrote: > I've been asked to spread the word about an event upcoming in April, > in Santa Clara, CA, USA, which is looking for speakers on a variety > of OpenStack topics. They're looking for technology-focused (ie, > vendor-neutral) presentations, and specific topics are suggested on > the CFP page. > > Conference site: https://www.percona.com/live/openstack-live-2015/ > CFP: https://www.percona.com/live/openstack-live-2015/user/register > > The CFP closes November 17th. > > They're looking for: > > > Tutorial tracks: > > -Deploying OpenStack > -Trove > -High Availability > -OpenStack Upgrades > -Operations: Management and Monitoring OpenStack > -Tuning Optimization and benchmarking of OpenStack > > Breakout tracks: > > -Operations > -High Availability > -Performance Optimization > -Replication and Backup > -Trove > -Monitoring and Tools Interesting. Would this be about 1-2 weeks before OpenStack Summit? I might be interested in presenting on OpenStack HA. Thanks for the information. Ryan From sayganesha at gmail.com Wed Oct 22 17:26:31 2014 From: sayganesha at gmail.com (Ganesh Sangle) Date: Wed, 22 Oct 2014 10:26:31 -0700 Subject: [Rdo-list] New to openStack Message-ID: Hi guys, I am new to openstack and I am trying to install the cinder package on Scientific Linux release 6.5 (Carbon) ran the following commands: yum install openstack-cinder I am unable to figure which version of openstack was installed. Is there a way to figure it out easily ? >From the documentation, it seems that the version of openstack that was Folsom. How to I get the latest supported version ? Thanks for helping! Ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeworrel at cisco.com Wed Oct 22 17:34:55 2014 From: jeworrel at cisco.com (Jesse Worrell -X (jeworrel - APEX SYSTEMS INC at Cisco)) Date: Wed, 22 Oct 2014 17:34:55 +0000 Subject: [Rdo-list] New to openStack In-Reply-To: References: Message-ID: Hi Ganesh, I am sending you a link that might be helpful. http://www.openstack.org/software/juno/ Hopefully this will help? I believe you can also use Regards, Jesse From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Ganesh Sangle Sent: Wednesday, October 22, 2014 1:27 PM To: rdo-list at redhat.com Subject: [Rdo-list] New to openStack Hi guys, I am new to openstack and I am trying to install the cinder package on Scientific Linux release 6.5 (Carbon) ran the following commands: yum install openstack-cinder I am unable to figure which version of openstack was installed. Is there a way to figure it out easily ? From the documentation, it seems that the version of openstack that was Folsom. How to I get the latest supported version ? Thanks for helping! Ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tim.Bell at cern.ch Wed Oct 22 17:35:52 2014 From: Tim.Bell at cern.ch (Tim Bell) Date: Wed, 22 Oct 2014 17:35:52 +0000 Subject: [Rdo-list] New to openStack In-Reply-To: References: Message-ID: <5D7F9996EA547448BC6C54C8C5AAF4E50102464622@CERNXCHG42.cern.ch> I?d recommend to follow the installation at https://openstack.redhat.com/Quickstart. This works great on Scientific Linux. The packstack tool will do all the set ups etc. Tim From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Ganesh Sangle Sent: 22 October 2014 19:27 To: rdo-list at redhat.com Subject: [Rdo-list] New to openStack Hi guys, I am new to openstack and I am trying to install the cinder package on Scientific Linux release 6.5 (Carbon) ran the following commands: yum install openstack-cinder I am unable to figure which version of openstack was installed. Is there a way to figure it out easily ? From the documentation, it seems that the version of openstack that was Folsom. How to I get the latest supported version ? Thanks for helping! Ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsneddon at redhat.com Wed Oct 22 19:08:01 2014 From: dsneddon at redhat.com (Dan Sneddon) Date: Wed, 22 Oct 2014 12:08:01 -0700 Subject: [Rdo-list] New to openStack In-Reply-To: References: Message-ID: <54480091.3000201@redhat.com> On 10/22/2014 10:26 AM, Ganesh Sangle wrote: > Hi guys, > I am new to openstack and I am trying to install the cinder package on > Scientific Linux release 6.5 (Carbon) > > ran the following commands: > yum install openstack-cinder > > I am unable to figure which version of openstack was installed. Is there > a way to figure it out easily ? > From the documentation, it seems that the version of openstack that was > Folsom. > How to I get the latest supported version ? > > Thanks for helping! > Ganesh > That's quite an old version you have installed. Unfortunately there is no upgrade path from the Folsom version that will allow you to keep your existing cloud. You will have to rebuild OpenStack, create new VMs, and migrate your data manually. The URL that Tim Bell posted will help you get up to speed with a newer version (based on Icehouse) that works on Scientific Linux 6.5. Once you are there, however, it won't be possible to upgrade much further while still using Scientific Linux 6.5. Juno will be the end of the road. The Kilo release requires Python 2.7 and other packages that aren't available on 6.5. Since you would need to start with a new cloud, you might want to consider using Scientific Linux 7, which will give you a clear upgrade path for future versions in the coming years. -- Dan Sneddon | Principal OpenStack Engineer dsneddon at redhat.com | redhat.com/openstack 650.254.4025 | @dxs on twitter -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From dsneddon at redhat.com Wed Oct 22 19:16:06 2014 From: dsneddon at redhat.com (Dan Sneddon) Date: Wed, 22 Oct 2014 12:16:06 -0700 Subject: [Rdo-list] New to openStack In-Reply-To: <54480091.3000201@redhat.com> References: <54480091.3000201@redhat.com> Message-ID: <54480276.5050701@redhat.com> On 10/22/2014 12:08 PM, Dan Sneddon wrote: > On 10/22/2014 10:26 AM, Ganesh Sangle wrote: >> Hi guys, >> I am new to openstack and I am trying to install the cinder package on >> Scientific Linux release 6.5 (Carbon) >> >> ran the following commands: >> yum install openstack-cinder >> >> I am unable to figure which version of openstack was installed. Is there >> a way to figure it out easily ? >> From the documentation, it seems that the version of openstack that was >> Folsom. >> How to I get the latest supported version ? >> >> Thanks for helping! >> Ganesh >> > > That's quite an old version you have installed. Unfortunately there is > no upgrade path from the Folsom version that will allow you to keep your > existing cloud. You will have to rebuild OpenStack, create new VMs, and > migrate your data manually. > > The URL that Tim Bell posted will help you get up to speed with a newer > version (based on Icehouse) that works on Scientific Linux 6.5. Once you > are there, however, it won't be possible to upgrade much further while > still using Scientific Linux 6.5. Juno will be the end of the road. The > Kilo release requires Python 2.7 and other packages that aren't > available on 6.5. > > Since you would need to start with a new cloud, you might want to > consider using Scientific Linux 7, which will give you a clear upgrade > path for future versions in the coming years. > One more addendum. I just noticed you asked for the "latest supported version." For that, you will want Red Hat Enterprise Linux OpenStack Platform, instead of RDO, which is the community version of OpenStack that Tim Bell pointed to. The supported version based on Juno will be available on Scientific Linux 6.5 as soon as it's released. The community version based on Juno will require 7, unless significant community effort is put in to make it work on 6.5 (which may not happen). Here is the URL for the supported version: http://www.redhat.com/en/technologies/linux-platforms/openstack-platform -- Dan Sneddon | Principal OpenStack Engineer dsneddon at redhat.com | redhat.com/openstack 650.254.4025 | @dxs on twitter -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From rnishtal at cisco.com Wed Oct 22 20:25:23 2014 From: rnishtal at cisco.com (Ramakrishna Nishtala (rnishtal)) Date: Wed, 22 Oct 2014 20:25:23 +0000 Subject: [Rdo-list] New to openStack In-Reply-To: <54480276.5050701@redhat.com> References: <54480091.3000201@redhat.com> <54480276.5050701@redhat.com> Message-ID: <828C71EED0ECDB4E9DBFAB28FDE743A00B54BCDD@xmb-aln-x14.cisco.com> Hi, Sorry if its bit off-topic. Once I install from fedora community site, is there any upgrade path available for Juno later with Red Hat supported stack ( ves 6? ). Regards, Rama -----Original Message----- From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Dan Sneddon Sent: Wednesday, October 22, 2014 12:16 PM To: rdo-list at redhat.com Subject: Re: [Rdo-list] New to openStack On 10/22/2014 12:08 PM, Dan Sneddon wrote: > On 10/22/2014 10:26 AM, Ganesh Sangle wrote: >> Hi guys, >> I am new to openstack and I am trying to install the cinder package >> on Scientific Linux release 6.5 (Carbon) >> >> ran the following commands: >> yum install openstack-cinder >> >> I am unable to figure which version of openstack was installed. Is >> there a way to figure it out easily ? >> From the documentation, it seems that the version of openstack that >> was Folsom. >> How to I get the latest supported version ? >> >> Thanks for helping! >> Ganesh >> > > That's quite an old version you have installed. Unfortunately there is > no upgrade path from the Folsom version that will allow you to keep > your existing cloud. You will have to rebuild OpenStack, create new > VMs, and migrate your data manually. > > The URL that Tim Bell posted will help you get up to speed with a > newer version (based on Icehouse) that works on Scientific Linux 6.5. > Once you are there, however, it won't be possible to upgrade much > further while still using Scientific Linux 6.5. Juno will be the end > of the road. The Kilo release requires Python 2.7 and other packages > that aren't available on 6.5. > > Since you would need to start with a new cloud, you might want to > consider using Scientific Linux 7, which will give you a clear upgrade > path for future versions in the coming years. > One more addendum. I just noticed you asked for the "latest supported version." For that, you will want Red Hat Enterprise Linux OpenStack Platform, instead of RDO, which is the community version of OpenStack that Tim Bell pointed to. The supported version based on Juno will be available on Scientific Linux 6.5 as soon as it's released. The community version based on Juno will require 7, unless significant community effort is put in to make it work on 6.5 (which may not happen). Here is the URL for the supported version: http://www.redhat.com/en/technologies/linux-platforms/openstack-platform -- Dan Sneddon | Principal OpenStack Engineer dsneddon at redhat.com | redhat.com/openstack 650.254.4025 | @dxs on twitter -------------- next part -------------- An HTML attachment was scrubbed... URL: From sayganesha at gmail.com Wed Oct 22 20:27:21 2014 From: sayganesha at gmail.com (Ganesh Sangle) Date: Wed, 22 Oct 2014 13:27:21 -0700 Subject: [Rdo-list] New to openStack In-Reply-To: <54480276.5050701@redhat.com> References: <54480091.3000201@redhat.com> <54480276.5050701@redhat.com> Message-ID: Thank you all for your replies. I am a developer trying to setup a dev-environment, and I was just looking to get the latest version available so that I can take advantage of the new drivers available with cinder. Followed the steps mentioned above and I could get the installed openstack/cinder packages upgraded to Icehouse, which seems to work fine for my purposes. On Wed, Oct 22, 2014 at 12:16 PM, Dan Sneddon wrote: > On 10/22/2014 12:08 PM, Dan Sneddon wrote: > > On 10/22/2014 10:26 AM, Ganesh Sangle wrote: > >> Hi guys, > >> I am new to openstack and I am trying to install the cinder package on > >> Scientific Linux release 6.5 (Carbon) > >> > >> ran the following commands: > >> yum install openstack-cinder > >> > >> I am unable to figure which version of openstack was installed. Is there > >> a way to figure it out easily ? > >> From the documentation, it seems that the version of openstack that was > >> Folsom. > >> How to I get the latest supported version ? > >> > >> Thanks for helping! > >> Ganesh > >> > > > > That's quite an old version you have installed. Unfortunately there is > > no upgrade path from the Folsom version that will allow you to keep your > > existing cloud. You will have to rebuild OpenStack, create new VMs, and > > migrate your data manually. > > > > The URL that Tim Bell posted will help you get up to speed with a newer > > version (based on Icehouse) that works on Scientific Linux 6.5. Once you > > are there, however, it won't be possible to upgrade much further while > > still using Scientific Linux 6.5. Juno will be the end of the road. The > > Kilo release requires Python 2.7 and other packages that aren't > > available on 6.5. > > > > Since you would need to start with a new cloud, you might want to > > consider using Scientific Linux 7, which will give you a clear upgrade > > path for future versions in the coming years. > > > > One more addendum. I just noticed you asked for the "latest supported > version." For that, you will want Red Hat Enterprise Linux OpenStack > Platform, instead of RDO, which is the community version of OpenStack > that Tim Bell pointed to. > > The supported version based on Juno will be available on Scientific > Linux 6.5 as soon as it's released. The community version based on Juno > will require 7, unless significant community effort is put in to make it > work on 6.5 (which may not happen). > > Here is the URL for the supported version: > http://www.redhat.com/en/technologies/linux-platforms/openstack-platform > > -- > Dan Sneddon | Principal OpenStack Engineer > dsneddon at redhat.com | redhat.com/openstack > 650.254.4025 | @dxs on twitter > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bbartlett at gmail.com Wed Oct 22 21:09:21 2014 From: bbartlett at gmail.com (Bill Bartlett) Date: Wed, 22 Oct 2014 14:09:21 -0700 Subject: [Rdo-list] public endpoints incorrect Message-ID: I've been unsuccessful in tracking down why all of my public endpoints have a null entry for the hostname/ip address section of their URL. [root at mac60eb69edd808 ~(openstack_admin)]# keystone endpoint-list | awk '{print $6}' publicurl http://:9696/ http://:8004/v1/%(tenant_id)s http://:8776/v1/%(tenant_id)s http://:9292 http://:8773/services/Cloud http://:8774/v2/%(tenant_id)s http://:8777 http://:8000/v1/ http://:8776/v2/%(tenant_id)s http://:8080/v1/AUTH_%(tenant_id)s http://:8080 http://:5000/v2.0 If we compare that to the internalurl, for example, it's easy to see there's an obvious problem: [root at mac60eb69edd808 ~(openstack_admin)]# keystone endpoint-list | awk '{print $8}' internalurl http://10.200.11.50:9696/ http://10.200.11.50:8004/v1/%(tenant_id)s http://10.200.11.50:8776/v1/%(tenant_id)s http://10.200.11.50:9292 http://10.200.11.50:8773/services/Cloud http://10.200.11.50:8774/v2/%(tenant_id)s http://10.200.11.50:8777 http://10.200.11.50:8000/v1/ http://10.200.11.50:8776/v2/%(tenant_id)s http://10.200.11.50:8080/v1/AUTH_%(tenant_id)s http://10.200.11.50:8080 http://10.200.11.50:5000/v2.0 Has anyone seen this before? I'd greatly appreciate any help in tracking down the cause. Cheers, Bill -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrunge at redhat.com Thu Oct 23 11:30:51 2014 From: mrunge at redhat.com (Matthias Runge) Date: Thu, 23 Oct 2014 13:30:51 +0200 Subject: [Rdo-list] New to openStack In-Reply-To: <828C71EED0ECDB4E9DBFAB28FDE743A00B54BCDD@xmb-aln-x14.cisco.com> References: <54480091.3000201@redhat.com> <54480276.5050701@redhat.com> <828C71EED0ECDB4E9DBFAB28FDE743A00B54BCDD@xmb-aln-x14.cisco.com> Message-ID: <5448E6EB.30401@redhat.com> On 22/10/14 22:25, Ramakrishna Nishtala (rnishtal) wrote: > Hi, > > Sorry if its bit off-topic. Once I install from fedora community site, > is there any upgrade path available for Juno later with Red Hat > supported stack ( ves 6? ). > > Do I understand you right, you're asking for Red Hat support of a Juno version on Scientific Linux 6? IIRC, there won't be a Juno version on top of a RHEL6 based Linux distro. See https://www.redhat.com/archives/rdo-list/2014-September/msg00122.html and following, esp. https://www.redhat.com/archives/rdo-list/2014-September/msg00128.html Matthias From rnishtal at cisco.com Thu Oct 23 15:40:50 2014 From: rnishtal at cisco.com (Ramakrishna Nishtala (rnishtal)) Date: Thu, 23 Oct 2014 15:40:50 +0000 Subject: [Rdo-list] New to openStack In-Reply-To: <5448E6EB.30401@redhat.com> References: <54480091.3000201@redhat.com> <54480276.5050701@redhat.com> <828C71EED0ECDB4E9DBFAB28FDE743A00B54BCDD@xmb-aln-x14.cisco.com> <5448E6EB.30401@redhat.com> Message-ID: <828C71EED0ECDB4E9DBFAB28FDE743A00B54CE92@xmb-aln-x14.cisco.com> Yep, should have been clearer. It's for rhel EL7, sorry not on scientific. Install Juno from yum install http://rdo.fedorapeople.org/openstack-juno/rdo-release-juno.rpm (https://openstack.redhat.com/RDO_test_day_Juno_milestone_3) Later would like to have Red Hat Open Stack version ( supported open stack version ) . Is there an upgrade path or do I have to install everything from ground zero. Appreciate your help. Regards, Rama -----Original Message----- From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Matthias Runge Sent: Thursday, October 23, 2014 4:31 AM To: rdo-list at redhat.com Subject: Re: [Rdo-list] New to openStack On 22/10/14 22:25, Ramakrishna Nishtala (rnishtal) wrote: > Hi, > > Sorry if its bit off-topic. Once I install from fedora community site, > is there any upgrade path available for Juno later with Red Hat > supported stack ( ves 6? ). > > Do I understand you right, you're asking for Red Hat support of a Juno version on Scientific Linux 6? IIRC, there won't be a Juno version on top of a RHEL6 based Linux distro. See https://www.redhat.com/archives/rdo-list/2014-September/msg00122.html and following, esp. https://www.redhat.com/archives/rdo-list/2014-September/msg00128.html Matthias _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Fri Oct 24 14:59:30 2014 From: rbowen at redhat.com (Rich Bowen) Date: Fri, 24 Oct 2014 10:59:30 -0400 Subject: [Rdo-list] Speakers wanted for OpenStack Live Conference (April 13-14, 2015, Santa Clara, CA) In-Reply-To: <20141022033817.GA20777@redhat.com> References: <5446A285.80603@redhat.com> <20141022033817.GA20777@redhat.com> Message-ID: <544A6952.70006@redhat.com> On 10/21/2014 11:38 PM, Ryan O'Hara wrote: > On Tue, Oct 21, 2014 at 02:14:29PM -0400, Rich Bowen wrote: >> I've been asked to spread the word about an event upcoming in April, >> in Santa Clara, CA, USA, which is looking for speakers on a variety >> of OpenStack topics. They're looking for technology-focused (ie, >> vendor-neutral) presentations, and specific topics are suggested on >> the CFP page. >> >> Conference site: https://www.percona.com/live/openstack-live-2015/ >> CFP: https://www.percona.com/live/openstack-live-2015/user/register >> >> The CFP closes November 17th. >> >> They're looking for: >> >> >> Tutorial tracks: >> >> -Deploying OpenStack >> -Trove >> -High Availability >> -OpenStack Upgrades >> -Operations: Management and Monitoring OpenStack >> -Tuning Optimization and benchmarking of OpenStack >> >> Breakout tracks: >> >> -Operations >> -High Availability >> -Performance Optimization >> -Replication and Backup >> -Trove >> -Monitoring and Tools > Interesting. Would this be about 1-2 weeks before OpenStack Summit? I > might be interested in presenting on OpenStack HA. Thanks for the > information. Yeah, I think that's right. Also, it conflicts with another event I'm attending, so I won't be there. -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ From Yaniv.Kaul at emc.com Fri Oct 24 20:04:21 2014 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Fri, 24 Oct 2014 16:04:21 -0400 Subject: [Rdo-list] packstack and updates of additional compute nodes Message-ID: <648473255763364B961A02AC3BE1060D03C7B57B58@MX19A.corp.emc.com> I've used packstack to install a {controller+compute} node and another compute-only node. It seems that the other compute node is a bit neglected: 1. It did not have openstack-status and friends installed, making tasks such as restarting the openstack services different than the other one. 2. It did not configure anything that allowed me to 'yum update' the OpenStack RPMs. /etc/yum.repos.d/rdo-release.repo is not enough, as the signing keys are from rdo-release-juno-1.rpm Thoughts? (yeh, I'll move to Foreman some day). Y. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ak at cloudssky.com Fri Oct 24 20:23:52 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Fri, 24 Oct 2014 22:23:52 +0200 Subject: [Rdo-list] packstack and updates of additional compute nodes In-Reply-To: <648473255763364B961A02AC3BE1060D03C7B57B58@MX19A.corp.emc.com> References: <648473255763364B961A02AC3BE1060D03C7B57B58@MX19A.corp.emc.com> Message-ID: Hi Yaniv, The most important thing by OpenStack deployments is the proper configuration of networking and your answer-file before you start packstack. For the latest Juno release I've written a short blog post for a 2 node deployment here: http://ow.ly/Clrq5 -Arash On Fri, Oct 24, 2014 at 10:04 PM, Kaul, Yaniv wrote: > I?ve used packstack to install a {controller+compute} node and another > compute-only node. > > It seems that the other compute node is a bit neglected: > > 1. It did not have openstack-status and friends installed, making > tasks such as restarting the openstack services different than the other > one. > > 2. It did not configure anything that allowed me to ?yum update? > the OpenStack RPMs. /etc/yum.repos.d/rdo-release.repo is not enough, as the > signing keys are from rdo-release-juno-1.rpm > > > > Thoughts? (yeh, I?ll move to Foreman some day). > > Y. > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Yaniv.Kaul at emc.com Fri Oct 24 20:27:44 2014 From: Yaniv.Kaul at emc.com (Kaul, Yaniv) Date: Fri, 24 Oct 2014 16:27:44 -0400 Subject: [Rdo-list] packstack and updates of additional compute nodes In-Reply-To: References: <648473255763364B961A02AC3BE1060D03C7B57B58@MX19A.corp.emc.com> Message-ID: <648473255763364B961A02AC3BE1060D03C7B57B5B@MX19A.corp.emc.com> Thanks ? while I?m mainly testing Cinder, perhaps it?s time I stop being lazy/scared and move away from Nova-Network! Y. From: Arash Kaffamanesh [mailto:ak at cloudssky.com] Sent: Friday, October 24, 2014 11:24 PM To: Kaul, Yaniv Cc: rdo-list at redhat.com Subject: Re: [Rdo-list] packstack and updates of additional compute nodes Hi Yaniv, The most important thing by OpenStack deployments is the proper configuration of networking and your answer-file before you start packstack. For the latest Juno release I've written a short blog post for a 2 node deployment here: http://ow.ly/Clrq5 -Arash On Fri, Oct 24, 2014 at 10:04 PM, Kaul, Yaniv > wrote: I?ve used packstack to install a {controller+compute} node and another compute-only node. It seems that the other compute node is a bit neglected: 1. It did not have openstack-status and friends installed, making tasks such as restarting the openstack services different than the other one. 2. It did not configure anything that allowed me to ?yum update? the OpenStack RPMs. /etc/yum.repos.d/rdo-release.repo is not enough, as the signing keys are from rdo-release-juno-1.rpm Thoughts? (yeh, I?ll move to Foreman some day). Y. _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From kchamart at redhat.com Sat Oct 25 09:04:53 2014 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Sat, 25 Oct 2014 11:04:53 +0200 Subject: [Rdo-list] packstack and updates of additional compute nodes In-Reply-To: <648473255763364B961A02AC3BE1060D03C7B57B5B@MX19A.corp.emc.com> References: <648473255763364B961A02AC3BE1060D03C7B57B58@MX19A.corp.emc.com> <648473255763364B961A02AC3BE1060D03C7B57B5B@MX19A.corp.emc.com> Message-ID: <20141025090453.GE3316@tesla.redhat.com> On Fri, Oct 24, 2014 at 04:27:44PM -0400, Kaul, Yaniv wrote: > Thanks ? while I?m mainly testing Cinder, perhaps it?s time I stop > being lazy/scared and move away from Nova-Network! Yes, do give Neutron a good try, I felt it was worth it. For the last 2 releases my primary testing has been with Neutron, fwiw, and it is becoming incrementally easier to debug. :-) My configs for a 2-node Neutron+GRE+OVS+ML2 setup: https://kashyapc.fedorapeople.org/virt/openstack/rdo/IceHouse-Nova-Neutron-ML2-GRE-OVS.txt /me needs to update these for Juno, though (been traveling, couldn't get to it yet). -- /kashyap From rbowen at redhat.com Mon Oct 27 18:15:57 2014 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 27 Oct 2014 14:15:57 -0400 Subject: [Rdo-list] RDO Juno packages available Message-ID: <544E8BDD.9050100@redhat.com> We're pleased to announce the availability of RDO packages for OpenStack Juno, for EL7 (RHEL7 and CentOS7) and Fedora 20. Fedora 21 is still in development and running RDO Juno on Fedora 21 is not recommended at this time. A separate announcement will be made when RDO Juno on Fedora 21 is ready. You can get started with RDO Juno via the process described in the Quickstart - http://openstack.redhat.com/Quickstart - and the various packages are available at https://rdo.fedorapeople.org/openstack-juno/ As always, if you have questions, you can bring them here, to the rdo-list mailing list, or to the IRC channel - #rdo on freenode.irc.net. Thanks for being part of the RDO community! -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rdo-info at redhat.com Mon Oct 27 19:50:11 2014 From: rdo-info at redhat.com (RDO Forum) Date: Mon, 27 Oct 2014 19:50:11 +0000 Subject: [Rdo-list] [RDO] Blog Roundup, week of October 20th Message-ID: <0000014953289ff0-f27cd325-f618-438f-953f-0a87b9fb5a56-000000@email.amazonses.com> rbowen started a discussion. Blog Roundup, week of October 20th --- Follow the link below to check it out: https://openstack.redhat.com/forum/discussion/991/blog-roundup-week-of-october-20th Have a great day! From rdo-info at redhat.com Mon Oct 27 19:53:21 2014 From: rdo-info at redhat.com (RDO Forum) Date: Mon, 27 Oct 2014 19:53:21 +0000 Subject: [Rdo-list] [RDO] RDO Juno packages available Message-ID: <00000149532b85eb-cbaf1989-503f-4be1-9589-d5a634445020-000000@email.amazonses.com> rbowen started a discussion. RDO Juno packages available --- Follow the link below to check it out: https://openstack.redhat.com/forum/discussion/992/rdo-juno-packages-available Have a great day! From mail-lists at karan.org Tue Oct 28 00:21:28 2014 From: mail-lists at karan.org (Karanbir Singh) Date: Tue, 28 Oct 2014 00:21:28 +0000 Subject: [Rdo-list] RDO Juno packages available In-Reply-To: <544E8BDD.9050100@redhat.com> References: <544E8BDD.9050100@redhat.com> Message-ID: <544EE188.3000407@karan.org> On 27/10/14 18:15, Rich Bowen wrote: > We're pleased to announce the availability of RDO packages for OpenStack Juno, for EL7 (RHEL7 and CentOS7) and Fedora 20. > > Fedora 21 is still in development and running RDO Juno on Fedora 21 is not recommended at this time. A separate announcement will be made when RDO Juno on Fedora 21 is ready. > > You can get started with RDO Juno via the process described in the Quickstart - http://openstack.redhat.com/Quickstart - and the various packages are available at https://rdo.fedorapeople.org/openstack-juno/ > > As always, if you have questions, you can bring them here, to the rdo-list mailing list, or to the IRC channel - #rdo on freenode.irc.net. > > Thanks for being part of the RDO community! the nightly installer on centos7 was still failing so I went had a look, turns out that if the root account already has a authorized_keys setup the packstack allinone operation fails with a permissions denied. just manually copying id_rsa.pub into the root's auth keys allows it to go past that bit. this was a problem here since the nighly installer test runs in a VM that is itself contexualised with cloud-init, running under a cloud setup. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From whayutin at redhat.com Tue Oct 28 00:41:02 2014 From: whayutin at redhat.com (whayutin) Date: Mon, 27 Oct 2014 20:41:02 -0400 Subject: [Rdo-list] RDO Juno packages available In-Reply-To: <544EE188.3000407@karan.org> References: <544E8BDD.9050100@redhat.com> <544EE188.3000407@karan.org> Message-ID: <1414456862.4936.2.camel@localhost.localdomain> On Tue, 2014-10-28 at 00:21 +0000, Karanbir Singh wrote: > On 27/10/14 18:15, Rich Bowen wrote: > > We're pleased to announce the availability of RDO packages for OpenStack Juno, for EL7 (RHEL7 and CentOS7) and Fedora 20. > > > > Fedora 21 is still in development and running RDO Juno on Fedora 21 is not recommended at this time. A separate announcement will be made when RDO Juno on Fedora 21 is ready. > > > > You can get started with RDO Juno via the process described in the Quickstart - http://openstack.redhat.com/Quickstart - and the various packages are available at https://rdo.fedorapeople.org/openstack-juno/ > > > > As always, if you have questions, you can bring them here, to the rdo-list mailing list, or to the IRC channel - #rdo on freenode.irc.net. > > > > Thanks for being part of the RDO community! > > the nightly installer on centos7 was still failing so I went had a look, > turns out that if the root account already has a authorized_keys setup > the packstack allinone operation fails with a permissions denied. > > just manually copying id_rsa.pub into the root's auth keys allows it to > go past that bit. > > this was a problem here since the nighly installer test runs in a VM > that is itself contexualised with cloud-init, running under a cloud setup. > > Karanbir, A freshly provisioned CentOS machine would not have an id_rsa key created right? It's good to know of course, but afaict not something that needs to be added to the instructions. From rbowen at redhat.com Tue Oct 28 17:24:17 2014 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 28 Oct 2014 13:24:17 -0400 Subject: [Rdo-list] RDO/OpenStack meeups in the coming week (October 28, 2014) Message-ID: <544FD141.1040803@redhat.com> The following are the meetups I'm aware of in the coming week where RDO enthusiasts will be gathering. If you know of others, please let me know, and/or add them to http://openstack.redhat.com/Events If you attend any of these meetups, please take pictures, and send me some. If you blog about the events (and you should), please send me that, too. * Tuesday, October 28 - Denver, Colorado - http://www.meetup.com/OpenStack-Denver/events/213229672/ - Getting the Most out of Cinder * Tuesday, October 28 - Santiago, Chile - http://www.meetup.com/DevOps-Culture/events/197237532/ - Primer reuni?n del grupo * Wednesday, October 29 - Denver, Colorado - http://www.meetup.com/Distributed-Computing-Denver/events/206469162/ - Ceph- Architecture of an Open Source, Distributed Storage System * Wednesday, October 29 - Columbia, Maryland - http://www.meetup.com/opensourcecloud/events/201114332/ - Open Source Cloud Meetup * Thursday, October 30 is Docker Global Hack Day, and there are meetups *everywhere*. Find one near you - http://tm3.org/dockerhack * And, starting Sunday, the OpenStack "Kilo" Summit will be held in Paris - http://openstack.org/summit/ Hope to see you there! -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From danofsatx at gmail.com Tue Oct 28 18:37:03 2014 From: danofsatx at gmail.com (Dan Mossor) Date: Tue, 28 Oct 2014 13:37:03 -0500 Subject: [Rdo-list] Neutron networking and public facing VLANs Message-ID: <544FE24F.5020700@gmail.com> Good Day, folks. I need help setting up what I thought to be a rather simple configuration. Let me lay out the setup: System NIC controller: on-board node3: on-board Intel PCIe Intel PCIe node4: on-board Intel PCIe Intel PCIe The onboard NIC on all three systems is the management interface. Before I ran packstack, I bonded the two PCIe NICs on the two compute nodes in 802.3ad mode, and set the bridges up to the VLANs on the bond. The switch is set to trunk VLANs 100-105 to those two systems on the bonded interfaces. So, before packstack, this is what I had: Controller: enp0s25 br0 br0.100 br0.101 Node3 + Node4: enp0s25 bond0 br0 br0.100 br0.101 In my answers file for packstack, I had these lines: CONFIG_NOVA_COMPUTE_PRIVIF=br0.101 CONFIG_NOVA_NETWORK_PUBIF=br0.100 CONFIG_NOVA_NETWORK_PRIVIF=br0.101 CONFIG_NOVA_NETWORK_FIXEDRANGE=10.1.128.0/20 CONFIG_NOVA_NETWORK_FLOATRANGE=10.1.224.0/20 CONFIG_NOVA_NETWORK_VLAN_START=101 CONFIG_NOVA_NETWORK_NUMBER=5 CONFIG_NOVA_NETWORK_SIZE=255 CONFIG_NEUTRON_L3_EXT_BRIDGE=br0 I want VLAN 100 to be my public facing interface. Packstack deployed the compute services to the controller system, and consequently set up a bridge on it's management interface [1,2]. The deployment did not honor the settings in the answer file, and set up new bridge interfaces on all of the systems, virbr0, that are not tied to any other interface, as well as the ovs-system plus two interfaces under that, br-int and br-ext [3,4]. While researching for this question, I stumbled upon ovs-vsctl, so I ran ovs-vsctl on the controller [5] and one of the nodes [6]. [1] http://paste.fedoraproject.org/145893/14519808 [2] http://paste.fedoraproject.org/145898/45199181 [3] http://paste.fedoraproject.org/145895/14519844 [4] http://paste.fedoraproject.org/145899/51998114 [5] http://paste.fedoraproject.org/145909/14520567 [6] http://paste.fedoraproject.org/145910/14520606 So, my starting point is this - how do I get the ovs-system talking to the bond? Next, how do I get the VLANs passed through to neutron, and eventually to the instances? -- Dan Mossor, RHCSA Systems Engineer at Large Fedora Plasma Product WG | Fedora QA Team | Fedora Server SIG Fedora Infrastructure Apprentice FAS: dmossor IRC: danofsatx San Antonio, Texas, USA From contact at progbau.de Wed Oct 29 08:33:16 2014 From: contact at progbau.de (Chris) Date: Wed, 29 Oct 2014 15:33:16 +0700 Subject: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge Message-ID: <006b01cff352$fddada80$f9908f80$@progbau.de> Hello I'm looking for a way to disable any firewall feature in one of our compute nodes and prevent the creation of the Linux bridge in the data path inside of this compute node. We using the RDO Icehouse release. Here is the configuration in the compute node: #/etc/neutron/plugin.ini [securitygroup] #firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver firewall_driver = neutron.agent.firewall.NoopFirewall # enable_security_group = True enable_security_group = False #/etc/nova/nova.conf firewall_driver = nova.virt.firewall.NoopFirewallDriver #security_group_api = neutron #/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini [securitygroup] firewall_driver = neutron.agent.firewall.NoopFirewallDriver enable_security_group = False The firewall seems to be disabled but the bridge and the interfaces are being still created. I found an older post about it: http://lists.openstack.org/pipermail/openstack/2014-May/007079.html But changing "portbindings.OVS_HYBRID_PLUG" from a hard-coded "True" to "False" didn't change anything. Please advise! Cheers Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihrachys at redhat.com Wed Oct 29 09:51:25 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Wed, 29 Oct 2014 10:51:25 +0100 Subject: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge In-Reply-To: <006b01cff352$fddada80$f9908f80$@progbau.de> References: <006b01cff352$fddada80$f9908f80$@progbau.de> Message-ID: <5450B89D.9000604@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 29/10/14 09:33, Chris wrote: > Hello > > > > I?m looking for a way to disable any firewall feature in one of > our compute nodes and prevent the creation of the Linux bridge in > the data path inside of this compute node. Can you elaborate on reasons to disable it? Of course it sounds a bit not optimal, but do you have any performance concerns that you try to address in this way? > > We using the RDO Icehouse release. > > > > Here is the configuration in the compute node: > > #/etc/neutron/plugin.ini > > [securitygroup] > > #firewall_driver = > neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver > > firewall_driver = neutron.agent.firewall.NoopFirewall > > # enable_security_group = True > > enable_security_group = False > > > > #/etc/nova/nova.conf > > firewall_driver = nova.virt.firewall.NoopFirewallDriver > > #security_group_api = neutron > > > > #/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini > > [securitygroup] > > firewall_driver = neutron.agent.firewall.NoopFirewallDriver > > enable_security_group = False > > > > The firewall seems to be disabled but the bridge and the interfaces > are being still created. > > I found an older post about it: > http://lists.openstack.org/pipermail/openstack/2014-May/007079.html > > But changing ?portbindings.OVS_HYBRID_PLUG" from a hard-coded > "True" to "False" didn?t change anything. > > > > Please advise! > > > > Cheers > > Chris > > > > > > _______________________________________________ Rdo-list mailing > list Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUULidAAoJEC5aWaUY1u57NhEIAJQ4GP+SdJ9TJOQ3AeyMhhit itqXiwunBQBD5Y5NXtXHzYPxA7r5+nj/ZJLkz8lWXEgf6e7vl5RbOTLxrA1B3pqU vWppW/jK5RHbMxNqoV0pL/z+HVhxrHeXRO/hbFzQxIyLO1IPkOlENzA5oBuOJtoF t/cvA0LUfc8uDE21MTS0XFjpwAoLIYj244J6+vCwv2AmwxvU+34D04YvGzfIoXm1 wVDXFItGjT52Lp2+ASdc38lzGOxc/5jXwE4XT4ZXWRTTx6iG8yJ6VXLrZf+915hF 8AJT0MIlTB+LYZ/YntTUtoVxYyJEIfvcblR6l8JTo1iGwSlDpVGvo4h4C82iQu4= =MoUk -----END PGP SIGNATURE----- From contact at progbau.de Wed Oct 29 10:26:15 2014 From: contact at progbau.de (Chris) Date: Wed, 29 Oct 2014 17:26:15 +0700 Subject: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge In-Reply-To: <5450B89D.9000604@redhat.com> References: <006b01cff352$fddada80$f9908f80$@progbau.de> <5450B89D.9000604@redhat.com> Message-ID: <007501cff362$c7642f50$562c8df0$@progbau.de> Hello, 1) we just don't need it, we are using the provider network which includes hardware firewalls. 2) We have huge performance problems regarding TCP_CRR / TCP_RR. The OpenStack VMs can deal just half of TCP connections per second compared to our bare metal installations. Throughput (10Gbit NIC) is fine though. Specs VMs and bare metal are of course equal (RAM, Cores, etc.) Did a lot of testing regarding the performance issues, it happens "after" the both (br-int/br-ex) openvswitches. Upgraded ovs to version 2.3 just fyi. Cheers Chris -----Original Message----- From: rdo-list-bounces at redhat.com [mailto:rdo-list-bounces at redhat.com] On Behalf Of Ihar Hrachyshka Sent: Wednesday, October 29, 2014 16:51 To: rdo-list at redhat.com Subject: Re: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 29/10/14 09:33, Chris wrote: > Hello > > > > I?m looking for a way to disable any firewall feature in one of our > compute nodes and prevent the creation of the Linux bridge in the data > path inside of this compute node. Can you elaborate on reasons to disable it? Of course it sounds a bit not optimal, but do you have any performance concerns that you try to address in this way? > > We using the RDO Icehouse release. > > > > Here is the configuration in the compute node: > > #/etc/neutron/plugin.ini > > [securitygroup] > > #firewall_driver = > neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver > > firewall_driver = neutron.agent.firewall.NoopFirewall > > # enable_security_group = True > > enable_security_group = False > > > > #/etc/nova/nova.conf > > firewall_driver = nova.virt.firewall.NoopFirewallDriver > > #security_group_api = neutron > > > > #/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini > > [securitygroup] > > firewall_driver = neutron.agent.firewall.NoopFirewallDriver > > enable_security_group = False > > > > The firewall seems to be disabled but the bridge and the interfaces > are being still created. > > I found an older post about it: > http://lists.openstack.org/pipermail/openstack/2014-May/007079.html > > But changing ?portbindings.OVS_HYBRID_PLUG" from a hard-coded "True" > to "False" didn?t change anything. > > > > Please advise! > > > > Cheers > > Chris > > > > > > _______________________________________________ Rdo-list mailing list > Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUULidAAoJEC5aWaUY1u57NhEIAJQ4GP+SdJ9TJOQ3AeyMhhit itqXiwunBQBD5Y5NXtXHzYPxA7r5+nj/ZJLkz8lWXEgf6e7vl5RbOTLxrA1B3pqU vWppW/jK5RHbMxNqoV0pL/z+HVhxrHeXRO/hbFzQxIyLO1IPkOlENzA5oBuOJtoF t/cvA0LUfc8uDE21MTS0XFjpwAoLIYj244J6+vCwv2AmwxvU+34D04YvGzfIoXm1 wVDXFItGjT52Lp2+ASdc38lzGOxc/5jXwE4XT4ZXWRTTx6iG8yJ6VXLrZf+915hF 8AJT0MIlTB+LYZ/YntTUtoVxYyJEIfvcblR6l8JTo1iGwSlDpVGvo4h4C82iQu4= =MoUk -----END PGP SIGNATURE----- _______________________________________________ Rdo-list mailing list Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list From ihrachys at redhat.com Wed Oct 29 17:04:11 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Wed, 29 Oct 2014 18:04:11 +0100 Subject: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge In-Reply-To: <007501cff362$c7642f50$562c8df0$@progbau.de> References: <006b01cff352$fddada80$f9908f80$@progbau.de> <5450B89D.9000604@redhat.com> <007501cff362$c7642f50$562c8df0$@progbau.de> Message-ID: <54511E0B.60604@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Have you replugged your instances? VIF objects are persisted in db, I guess with flags including the one that control whether a bridge should be created. Do you still see those bridges created for new instances? /Ihar On 29/10/14 11:26, Chris wrote: > Hello, > > 1) we just don't need it, we are using the provider network which > includes hardware firewalls. 2) We have huge performance problems > regarding TCP_CRR / TCP_RR. The OpenStack VMs can deal just half of > TCP connections per second compared to our bare metal > installations. Throughput (10Gbit NIC) is fine though. Specs VMs > and bare metal are of course equal (RAM, Cores, etc.) > > Did a lot of testing regarding the performance issues, it happens > "after" the both (br-int/br-ex) openvswitches. Upgraded ovs to > version 2.3 just fyi. > > Cheers Chris > > > -----Original Message----- From: rdo-list-bounces at redhat.com > [mailto:rdo-list-bounces at redhat.com] On Behalf Of Ihar Hrachyshka > Sent: Wednesday, October 29, 2014 16:51 To: rdo-list at redhat.com > Subject: Re: [Rdo-list] Compute Node without firewall (iptables) > and Linux bridge > > On 29/10/14 09:33, Chris wrote: >> Hello > > > >> I?m looking for a way to disable any firewall feature in one of >> our compute nodes and prevent the creation of the Linux bridge in >> the data path inside of this compute node. > > Can you elaborate on reasons to disable it? Of course it sounds a > bit not optimal, but do you have any performance concerns that you > try to address in this way? > > >> We using the RDO Icehouse release. > > > >> Here is the configuration in the compute node: > >> #/etc/neutron/plugin.ini > >> [securitygroup] > >> #firewall_driver = >> neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver > >> firewall_driver = neutron.agent.firewall.NoopFirewall > >> # enable_security_group = True > >> enable_security_group = False > > > >> #/etc/nova/nova.conf > >> firewall_driver = nova.virt.firewall.NoopFirewallDriver > >> #security_group_api = neutron > > > >> #/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini > >> [securitygroup] > >> firewall_driver = neutron.agent.firewall.NoopFirewallDriver > >> enable_security_group = False > > > >> The firewall seems to be disabled but the bridge and the >> interfaces are being still created. > >> I found an older post about it: >> http://lists.openstack.org/pipermail/openstack/2014-May/007079.html > >> But changing ?portbindings.OVS_HYBRID_PLUG" from a hard-coded >> "True" to "False" didn?t change anything. > > > >> Please advise! > > > >> Cheers > >> Chris > > > > > >> _______________________________________________ Rdo-list mailing >> list Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list > > > _______________________________________________ Rdo-list mailing > list Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUUR4LAAoJEC5aWaUY1u57uQgIAIUWQaBW9HshqnJiUSgsuH/5 9a7p0fZJW2JwhZ00TFq6K4njjPV2xnHKQrae1MbEduOD0SwpcXlzR2dXbOXLx8Mm swWJim87X4uKNnK2c6MD1WB7wB1d3yVS4SurgS7/DFPyQD1ysHq4FM/XyWSNGcy/ n2GW5TMNokFe6gLXU9r/yDQlsnQsARmK5wnZ63VXHl3S9qnH2gnLPsuZh7X3FUV8 RAsiA9IR2RqiBamS3oGssgP0zIxkNRUwS+muZx//dwRr1NkqZMBNrkdN2t/PZLnD MBwTX5e8uwJ1Jn5mQB7Wy9n1NdkNTPxZT2R5fBU70UVn8qJbXVzzyif7h4we0zU= =VUIE -----END PGP SIGNATURE----- From contact at progbau.de Wed Oct 29 18:27:51 2014 From: contact at progbau.de (Chris) Date: Thu, 30 Oct 2014 01:27:51 +0700 Subject: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge In-Reply-To: <54511E0B.60604@redhat.com> References: <006b01cff352$fddada80$f9908f80$@progbau.de> <5450B89D.9000604@redhat.com> <007501cff362$c7642f50$562c8df0$@progbau.de> <54511E0B.60604@redhat.com> Message-ID: <000b01cff3a6$172a90e0$457fb2a0$@progbau.de> What do you mean with re-plugged? During my testing I always delete and create new Instances and every time the Linux bridge+interfaces gets deleted and created as well. Cheers Chris -----Original Message----- From: Ihar Hrachyshka [mailto:ihrachys at redhat.com] Sent: Thursday, October 30, 2014 00:04 To: Chris; rdo-list at redhat.com Subject: Re: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Have you replugged your instances? VIF objects are persisted in db, I guess with flags including the one that control whether a bridge should be created. Do you still see those bridges created for new instances? /Ihar On 29/10/14 11:26, Chris wrote: > Hello, > > 1) we just don't need it, we are using the provider network which > includes hardware firewalls. 2) We have huge performance problems > regarding TCP_CRR / TCP_RR. The OpenStack VMs can deal just half of > TCP connections per second compared to our bare metal installations. > Throughput (10Gbit NIC) is fine though. Specs VMs and bare metal are > of course equal (RAM, Cores, etc.) > > Did a lot of testing regarding the performance issues, it happens > "after" the both (br-int/br-ex) openvswitches. Upgraded ovs to version > 2.3 just fyi. > > Cheers Chris > > > -----Original Message----- From: rdo-list-bounces at redhat.com > [mailto:rdo-list-bounces at redhat.com] On Behalf Of Ihar Hrachyshka > Sent: Wednesday, October 29, 2014 16:51 To: rdo-list at redhat.com > Subject: Re: [Rdo-list] Compute Node without firewall (iptables) and > Linux bridge > > On 29/10/14 09:33, Chris wrote: >> Hello > > > >> I?m looking for a way to disable any firewall feature in one of our >> compute nodes and prevent the creation of the Linux bridge in the >> data path inside of this compute node. > > Can you elaborate on reasons to disable it? Of course it sounds a bit > not optimal, but do you have any performance concerns that you try to > address in this way? > > >> We using the RDO Icehouse release. > > > >> Here is the configuration in the compute node: > >> #/etc/neutron/plugin.ini > >> [securitygroup] > >> #firewall_driver = >> neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver > >> firewall_driver = neutron.agent.firewall.NoopFirewall > >> # enable_security_group = True > >> enable_security_group = False > > > >> #/etc/nova/nova.conf > >> firewall_driver = nova.virt.firewall.NoopFirewallDriver > >> #security_group_api = neutron > > > >> #/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini > >> [securitygroup] > >> firewall_driver = neutron.agent.firewall.NoopFirewallDriver > >> enable_security_group = False > > > >> The firewall seems to be disabled but the bridge and the interfaces >> are being still created. > >> I found an older post about it: >> http://lists.openstack.org/pipermail/openstack/2014-May/007079.html > >> But changing ?portbindings.OVS_HYBRID_PLUG" from a hard-coded "True" >> to "False" didn?t change anything. > > > >> Please advise! > > > >> Cheers > >> Chris > > > > > >> _______________________________________________ Rdo-list mailing list >> Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list > > > _______________________________________________ Rdo-list mailing list > Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list > > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUUR4LAAoJEC5aWaUY1u57uQgIAIUWQaBW9HshqnJiUSgsuH/5 9a7p0fZJW2JwhZ00TFq6K4njjPV2xnHKQrae1MbEduOD0SwpcXlzR2dXbOXLx8Mm swWJim87X4uKNnK2c6MD1WB7wB1d3yVS4SurgS7/DFPyQD1ysHq4FM/XyWSNGcy/ n2GW5TMNokFe6gLXU9r/yDQlsnQsARmK5wnZ63VXHl3S9qnH2gnLPsuZh7X3FUV8 RAsiA9IR2RqiBamS3oGssgP0zIxkNRUwS+muZx//dwRr1NkqZMBNrkdN2t/PZLnD MBwTX5e8uwJ1Jn5mQB7Wy9n1NdkNTPxZT2R5fBU70UVn8qJbXVzzyif7h4we0zU= =VUIE -----END PGP SIGNATURE----- From fredlhsu at arista.com Wed Oct 29 21:09:19 2014 From: fredlhsu at arista.com (Fred Hsu) Date: Wed, 29 Oct 2014 14:09:19 -0700 Subject: [Rdo-list] Neutron validate method error installing RDO Juno on Fedora 20 Message-ID: Hi, I'm trying to use packstack to install Juno on a fedora20 server and I'm getting the following error: ERROR : Error appeared during Puppet run: 172.28.171.168_neutron.pp Error: Validate method failed for class sleep: implicit argument passing of super from method defined by define_method() is not supported. Specify all arguments explicitly. I'm using VLAN as the ML2 type. Attached is my answers file. Any help would be appreciated! Thanks Fred -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- [general] # Path to a Public key to install on servers. If a usable key has not # been installed on the remote servers the user will be prompted for a # password and this key will be installed so the password will not be # required again CONFIG_SSH_KEY=/root/.ssh/id_rsa.pub # Set to 'y' if you would like Packstack to install MySQL CONFIG_MYSQL_INSTALL=y # Set to 'y' if you would like Packstack to install OpenStack Image # Service (Glance) CONFIG_GLANCE_INSTALL=y # Set to 'y' if you would like Packstack to install OpenStack Block # Storage (Cinder) CONFIG_CINDER_INSTALL=y # Set to 'y' if you would like Packstack to install OpenStack Compute # (Nova) CONFIG_NOVA_INSTALL=y # Set to 'y' if you would like Packstack to install OpenStack # Networking (Neutron) CONFIG_NEUTRON_INSTALL=y # Set to 'y' if you would like Packstack to install OpenStack # Dashboard (Horizon) CONFIG_HORIZON_INSTALL=y # Set to 'y' if you would like Packstack to install OpenStack Object # Storage (Swift) CONFIG_SWIFT_INSTALL=y # Set to 'y' if you would like Packstack to install OpenStack # Metering (Ceilometer) CONFIG_CEILOMETER_INSTALL=y # Set to 'y' if you would like Packstack to install OpenStack # Orchestration (Heat) CONFIG_HEAT_INSTALL=y # Set to 'y' if you would like Packstack to install the OpenStack # Client packages. An admin "rc" file will also be installed CONFIG_CLIENT_INSTALL=y # Comma separated list of NTP servers. Leave plain if Packstack # should not install ntpd on instances. CONFIG_NTP_SERVERS=172.28.170.129 # Set to 'y' if you would like Packstack to install Nagios to monitor # OpenStack hosts CONFIG_NAGIOS_INSTALL=y # Comma separated list of servers to be excluded from installation in # case you are running Packstack the second time with the same answer # file and don't want Packstack to touch these servers. Leave plain if # you don't need to exclude any server. EXCLUDE_SERVERS= # Set to 'y' if you want to run OpenStack services in debug mode. # Otherwise set to 'n'. CONFIG_DEBUG_MODE=y # Set to 'y' if you want to use VMware vCenter as hypervisor and # storageOtherwise set to 'n'. CONFIG_VMWARE_BACKEND=n # The IP address of the server on which to install MySQL CONFIG_MYSQL_HOST=172.28.171.168 # Username for the MySQL admin user CONFIG_MYSQL_USER=root # Password for the MySQL admin user CONFIG_MYSQL_PW=password # The IP address of the server on which to install the QPID service CONFIG_QPID_HOST=172.28.171.168 # Enable SSL for the QPID service CONFIG_QPID_ENABLE_SSL=n # Enable Authentication for the QPID service CONFIG_QPID_ENABLE_AUTH=n # The password for the NSS certificate database of the QPID service CONFIG_QPID_NSS_CERTDB_PW=643fe285e9524e6baa96b887e8c1642c # The port in which the QPID service listens to SSL connections CONFIG_QPID_SSL_PORT=5671 # The filename of the certificate that the QPID service is going to # use CONFIG_QPID_SSL_CERT_FILE=/etc/pki/tls/certs/qpid_selfcert.pem # The filename of the private key that the QPID service is going to # use CONFIG_QPID_SSL_KEY_FILE=/etc/pki/tls/private/qpid_selfkey.pem # Auto Generates self signed SSL certificate and key CONFIG_QPID_SSL_SELF_SIGNED=y # User for qpid authentication CONFIG_QPID_AUTH_USER=qpid_user # Password for user authentication CONFIG_QPID_AUTH_PASSWORD=220f453e5bd94661 # The IP address of the server on which to install Keystone CONFIG_KEYSTONE_HOST=172.28.171.168 # The password to use for the Keystone to access DB CONFIG_KEYSTONE_DB_PW=b792dfec41804070 # The token to use for the Keystone service api CONFIG_KEYSTONE_ADMIN_TOKEN=cffc60232abd47409c8cde8e3943e7c9 # The password to use for the Keystone admin user CONFIG_KEYSTONE_ADMIN_PW=admin # The password to use for the Keystone demo user CONFIG_KEYSTONE_DEMO_PW=demo # Kestone token format. Use either UUID or PKI CONFIG_KEYSTONE_TOKEN_FORMAT=PKI # The IP address of the server on which to install Glance CONFIG_GLANCE_HOST=172.28.171.168 # The password to use for the Glance to access DB CONFIG_GLANCE_DB_PW=0b56fe189b4146d1 # The password to use for the Glance to authenticate with Keystone CONFIG_GLANCE_KS_PW=d1a81716186b4595 # The IP address of the server on which to install Cinder CONFIG_CINDER_HOST=172.28.171.168 # The password to use for the Cinder to access DB CONFIG_CINDER_DB_PW=4ab1c000421a4152 # The password to use for the Cinder to authenticate with Keystone CONFIG_CINDER_KS_PW=263668309a064a2c # The Cinder backend to use, valid options are: lvm, gluster, nfs, # vmdk CONFIG_CINDER_BACKEND=lvm # Create Cinder's volumes group. This should only be done for testing # on a proof-of-concept installation of Cinder. This will create a # file-backed volume group and is not suitable for production usage. CONFIG_CINDER_VOLUMES_CREATE=y # Cinder's volumes group size. Note that actual volume size will be # extended with 3% more space for VG metadata. CONFIG_CINDER_VOLUMES_SIZE=20G # A single or comma separated list of gluster volume shares to mount, # eg: ip-address:/vol-name, domain:/vol-name CONFIG_CINDER_GLUSTER_MOUNTS= # A single or comma seprated list of NFS exports to mount, eg: ip- # address:/export-name CONFIG_CINDER_NFS_MOUNTS= # The IP address of the VMware vCenter datastore CONFIG_VCENTER_HOST= # The username to authenticate to VMware vCenter datastore CONFIG_VCENTER_USER= # The password to authenticate to VMware vCenter datastore CONFIG_VCENTER_PASSWORD= # The IP address of the server on which to install the Nova API # service CONFIG_NOVA_API_HOST=172.28.171.168 # The IP address of the server on which to install the Nova Cert # service CONFIG_NOVA_CERT_HOST=172.28.171.168 # The IP address of the server on which to install the Nova VNC proxy CONFIG_NOVA_VNCPROXY_HOST=172.28.171.168 # A comma separated list of IP addresses on which to install the Nova # Compute services CONFIG_NOVA_COMPUTE_HOSTS=172.28.171.168 # The IP address of the server on which to install the Nova Conductor # service CONFIG_NOVA_CONDUCTOR_HOST=172.28.171.168 # The password to use for the Nova to access DB CONFIG_NOVA_DB_PW=789e4699cfd84b00 # The password to use for the Nova to authenticate with Keystone CONFIG_NOVA_KS_PW=3383400a8f5e4950 # The IP address of the server on which to install the Nova Scheduler # service CONFIG_NOVA_SCHED_HOST=172.28.171.168 # The overcommitment ratio for virtual to physical CPUs. Set to 1.0 # to disable CPU overcommitment CONFIG_NOVA_SCHED_CPU_ALLOC_RATIO=16.0 # The overcommitment ratio for virtual to physical RAM. Set to 1.0 to # disable RAM overcommitment CONFIG_NOVA_SCHED_RAM_ALLOC_RATIO=1.5 # Private interface for Flat DHCP on the Nova compute servers CONFIG_NOVA_COMPUTE_PRIVIF=em2 # The list of IP addresses of the server on which to install the Nova # Network service CONFIG_NOVA_NETWORK_HOSTS=172.28.171.168 # Nova network manager CONFIG_NOVA_NETWORK_MANAGER=nova.network.manager.FlatDHCPManager # Public interface on the Nova network server CONFIG_NOVA_NETWORK_PUBIF=em1 # Private interface for network manager on the Nova network server CONFIG_NOVA_NETWORK_PRIVIF=em2 # IP Range for network manager CONFIG_NOVA_NETWORK_FIXEDRANGE=192.168.32.0/22 # IP Range for Floating IP's CONFIG_NOVA_NETWORK_FLOATRANGE=10.3.4.0/22 # Name of the default floating pool to which the specified floating # ranges are added to CONFIG_NOVA_NETWORK_DEFAULTFLOATINGPOOL=nova # Automatically assign a floating IP to new instances CONFIG_NOVA_NETWORK_AUTOASSIGNFLOATINGIP=n # First VLAN for private networks CONFIG_NOVA_NETWORK_VLAN_START=100 # Number of networks to support CONFIG_NOVA_NETWORK_NUMBER=1 # Number of addresses in each private subnet CONFIG_NOVA_NETWORK_SIZE=255 # The IP address of the VMware vCenter server CONFIG_VCENTER_HOST= # The username to authenticate to VMware vCenter server CONFIG_VCENTER_USER= # The password to authenticate to VMware vCenter server CONFIG_VCENTER_PASSWORD= # The name of the vCenter cluster CONFIG_VCENTER_CLUSTER_NAME= # The IP addresses of the server on which to install the Neutron # server CONFIG_NEUTRON_SERVER_HOST=172.28.171.168 # The password to use for Neutron to authenticate with Keystone CONFIG_NEUTRON_KS_PW=bd503795e2a1465d # The password to use for Neutron to access DB CONFIG_NEUTRON_DB_PW=217d2224bec54a9d # A comma separated list of IP addresses on which to install Neutron # L3 agent CONFIG_NEUTRON_L3_HOSTS=172.28.171.168 # The name of the bridge that the Neutron L3 agent will use for # external traffic, or 'provider' if using provider networks CONFIG_NEUTRON_L3_EXT_BRIDGE=br-ex # A comma separated list of IP addresses on which to install Neutron # DHCP agent CONFIG_NEUTRON_DHCP_HOSTS=172.28.171.168 # A comma separated list of IP addresses on which to install Neutron # LBaaS agent CONFIG_NEUTRON_LBAAS_HOSTS= # The name of the L2 plugin to be used with Neutron CONFIG_NEUTRON_L2_PLUGIN=ml2 # A comma separated list of IP addresses on which to install Neutron # metadata agent CONFIG_NEUTRON_METADATA_HOSTS=172.28.171.168 # A comma separated list of IP addresses on which to install Neutron # metadata agent CONFIG_NEUTRON_METADATA_PW=07415955c703411e # A comma separated list of network type driver entrypoints to be # loaded from the neutron.ml2.type_drivers namespace. CONFIG_NEUTRON_ML2_TYPE_DRIVERS=vlan # A comma separated ordered list of network_types to allocate as # tenant networks. The value 'local' is only useful for single-box # testing but provides no connectivity between hosts. CONFIG_NEUTRON_ML2_TENANT_NETWORK_TYPES=vlan # A comma separated ordered list of networking mechanism driver # entrypoints to be loaded from the neutron.ml2.mechanism_drivers # namespace. CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS=openvswitch # A comma separated list of physical_network names with which flat # networks can be created. Use * to allow flat networks with arbitrary # physical_network names. CONFIG_NEUTRON_ML2_FLAT_NETWORKS=* # A comma separated list of :: # or specifying physical_network names usable for # VLAN provider and tenant networks, as well as ranges of VLAN tags on # each available for allocation to tenant networks. CONFIG_NEUTRON_ML2_VLAN_RANGES=inter-vlan:1200:1300 # A comma separated list of : tuples enumerating # ranges of GRE tunnel IDs that are available for tenant network # allocation. Should be an array with tun_max +1 - tun_min > 1000000 CONFIG_NEUTRON_ML2_TUNNEL_ID_RANGES= # Multicast group for VXLAN. If unset, disables VXLAN enable sending # allocate broadcast traffic to this multicast group. When left # unconfigured, will disable multicast VXLAN mode. Should be an # Multicast IP (v4 or v6) address. CONFIG_NEUTRON_ML2_VXLAN_GROUP= # A comma separated list of : tuples enumerating # ranges of VXLAN VNI IDs that are available for tenant network # allocation. Min value is 0 and Max value is 16777215. CONFIG_NEUTRON_ML2_VNI_RANGES= # The name of the L2 agent to be used with Neutron CONFIG_NEUTRON_L2_AGENT=openvswitch # The type of network to allocate for tenant networks (eg. vlan, # local) CONFIG_NEUTRON_LB_TENANT_NETWORK_TYPE=local # A comma separated list of VLAN ranges for the Neutron linuxbridge # plugin (eg. physnet1:1:4094,physnet2,physnet3:3000:3999) CONFIG_NEUTRON_LB_VLAN_RANGES= # A comma separated list of interface mappings for the Neutron # linuxbridge plugin (eg. physnet1:br-eth1,physnet2:br-eth2,physnet3 # :br-eth3) CONFIG_NEUTRON_LB_INTERFACE_MAPPINGS= # Type of network to allocate for tenant networks (eg. vlan, local, # gre, vxlan) CONFIG_NEUTRON_OVS_TENANT_NETWORK_TYPE=vlan # A comma separated list of VLAN ranges for the Neutron openvswitch # plugin (eg. physnet1:1:4094,physnet2,physnet3:3000:3999) CONFIG_NEUTRON_OVS_VLAN_RANGES=inter-vlan:1200:1300 # A comma separated list of bridge mappings for the Neutron # openvswitch plugin (eg. physnet1:br-eth1,physnet2:br-eth2,physnet3 # :br-eth3) CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=inter-vlan:br-inst # A comma separated list of colon-separated OVS bridge:interface # pairs. The interface will be added to the associated bridge. CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-inst:p1p1 # A comma separated list of tunnel ranges for the Neutron openvswitch # plugin (eg. 1:1000) CONFIG_NEUTRON_OVS_TUNNEL_RANGES= # The interface for the OVS tunnel. Packstack will override the IP # address used for tunnels on this hypervisor to the IP found on the # specified interface. (eg. eth1) CONFIG_NEUTRON_OVS_TUNNEL_IF= # VXLAN UDP port CONFIG_NEUTRON_OVS_VXLAN_UDP_PORT=4789 # The IP address of the server on which to install the OpenStack # client packages. An admin "rc" file will also be installed CONFIG_OSCLIENT_HOST=172.28.171.168 # The IP address of the server on which to install Horizon CONFIG_HORIZON_HOST=172.28.171.168 # To set up Horizon communication over https set this to "y" CONFIG_HORIZON_SSL=n # PEM encoded certificate to be used for ssl on the https server, # leave blank if one should be generated, this certificate should not # require a passphrase CONFIG_SSL_CERT= # Keyfile corresponding to the certificate if one was entered CONFIG_SSL_KEY= # The IP address on which to install the Swift proxy service # (currently only single proxy is supported) CONFIG_SWIFT_PROXY_HOSTS=172.28.171.168 # The password to use for the Swift to authenticate with Keystone CONFIG_SWIFT_KS_PW=d516512c575d4b80 # A comma separated list of IP addresses on which to install the # Swift Storage services, each entry should take the format # [/dev], for example 127.0.0.1/vdb will install /dev/vdb # on 127.0.0.1 as a swift storage device(packstack does not create the # filesystem, you must do this first), if /dev is omitted Packstack # will create a loopback device for a test setup CONFIG_SWIFT_STORAGE_HOSTS=172.28.171.168 # Number of swift storage zones, this number MUST be no bigger than # the number of storage devices configured CONFIG_SWIFT_STORAGE_ZONES=1 # Number of swift storage replicas, this number MUST be no bigger # than the number of storage zones configured CONFIG_SWIFT_STORAGE_REPLICAS=1 # FileSystem type for storage nodes CONFIG_SWIFT_STORAGE_FSTYPE=ext4 # Shared secret for Swift CONFIG_SWIFT_HASH=319a5ec926594b9d # Size of the swift loopback file storage device CONFIG_SWIFT_STORAGE_SIZE=2G # Whether to provision for demo usage and testing. Note that # provisioning is only supported for all-in-one installations. CONFIG_PROVISION_DEMO=y # Whether to configure tempest for testing. Note that provisioning is # only supported for all-in-one installations. CONFIG_PROVISION_TEMPEST=n # The CIDR network address for the floating IP subnet CONFIG_PROVISION_DEMO_FLOATRANGE=172.24.4.224/28 # The uri of the tempest git repository to use CONFIG_PROVISION_TEMPEST_REPO_URI=https://github.com/openstack/tempest.git # The revision of the tempest git repository to use CONFIG_PROVISION_TEMPEST_REPO_REVISION=stable/havana # Whether to configure the ovs external bridge in an all-in-one # deployment CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE=n # The IP address of the server on which to install Heat service CONFIG_HEAT_HOST=172.28.171.168 # The password used by Heat user to authenticate against MySQL CONFIG_HEAT_DB_PW=e7bf3476b24c4bf9 # The encryption key to use for authentication info in database CONFIG_HEAT_AUTH_ENC_KEY=0ccecf3492174594 # The password to use for the Heat to authenticate with Keystone CONFIG_HEAT_KS_PW=390aa4df4c1a4fac # Set to 'y' if you would like Packstack to install Heat CloudWatch # API CONFIG_HEAT_CLOUDWATCH_INSTALL=n # Set to 'y' if you would like Packstack to install Heat # CloudFormation API CONFIG_HEAT_CFN_INSTALL=n # The IP address of the server on which to install Heat CloudWatch # API service CONFIG_HEAT_CLOUDWATCH_HOST=172.28.171.168 # The IP address of the server on which to install Heat # CloudFormation API service CONFIG_HEAT_CFN_HOST=172.28.171.168 # The IP address of the server on which to install Ceilometer CONFIG_CEILOMETER_HOST=172.28.171.168 # Secret key for signing metering messages. CONFIG_CEILOMETER_SECRET=8aac048972f64f75 # The password to use for Ceilometer to authenticate with Keystone CONFIG_CEILOMETER_KS_PW=2ed686af198844f6 # The IP address of the server on which to install the Nagios server CONFIG_NAGIOS_HOST=172.28.171.168 # The password of the nagiosadmin user on the Nagios server CONFIG_NAGIOS_PW=d1303f59f8854232 # To subscribe each server to EPEL enter "y" CONFIG_USE_EPEL=n # A comma separated list of URLs to any additional yum repositories # to install CONFIG_REPO= # To subscribe each server with Red Hat subscription manager, include # this with CONFIG_RH_PW CONFIG_RH_USER= # To subscribe each server with Red Hat subscription manager, include # this with CONFIG_RH_USER CONFIG_RH_PW= # To subscribe each server to Red Hat Enterprise Linux 6 Server Beta # channel (only needed for Preview versions of RHOS) enter "y" CONFIG_RH_BETA_REPO=n # To subscribe each server with RHN Satellite,fill Satellite's URL # here. Note that either satellite's username/password or activation # key has to be provided CONFIG_SATELLITE_URL= # Username to access RHN Satellite CONFIG_SATELLITE_USER= # Password to access RHN Satellite CONFIG_SATELLITE_PW= # Activation key for subscription to RHN Satellite CONFIG_SATELLITE_AKEY= # Specify a path or URL to a SSL CA certificate to use CONFIG_SATELLITE_CACERT= # If required specify the profile name that should be used as an # identifier for the system in RHN Satellite CONFIG_SATELLITE_PROFILE= # Comma separated list of flags passed to rhnreg_ks. Valid flags are: # novirtinfo, norhnsd, nopackages CONFIG_SATELLITE_FLAGS= # Specify a HTTP proxy to use with RHN Satellite CONFIG_SATELLITE_PROXY= # Specify a username to use with an authenticated HTTP proxy CONFIG_SATELLITE_PROXY_USER= # Specify a password to use with an authenticated HTTP proxy. CONFIG_SATELLITE_PROXY_PW= From contact at progbau.de Thu Oct 30 10:56:56 2014 From: contact at progbau.de (Chris) Date: Thu, 30 Oct 2014 17:56:56 +0700 Subject: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge References: <006b01cff352$fddada80$f9908f80$@progbau.de> <5450B89D.9000604@redhat.com> <007501cff362$c7642f50$562c8df0$@progbau.de> <54511E0B.60604@redhat.com> Message-ID: <002d01cff430$3b2a01d0$b17e0570$@progbau.de> I just found out that the file in the compute node: /usr/lib/python2.6/site-packages/neutron/plugins/openvswitch/ovs_neutron_plu gin.py where I edit the portbindings.OVS_HYBRID_PLUG doesn't has any effect. I even can delete the whole file, the bridge is still being created and everything works normal. Where I can edit the code to prevent the bridge creation? Cheers Chris -----Original Message----- From: Chris [mailto:contact at progbau.de] Sent: Thursday, October 30, 2014 01:28 To: 'Ihar Hrachyshka'; 'rdo-list at redhat.com' Subject: RE: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge What do you mean with re-plugged? During my testing I always delete and create new Instances and every time the Linux bridge+interfaces gets deleted and created as well. Cheers Chris -----Original Message----- From: Ihar Hrachyshka [mailto:ihrachys at redhat.com] Sent: Thursday, October 30, 2014 00:04 To: Chris; rdo-list at redhat.com Subject: Re: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Have you replugged your instances? VIF objects are persisted in db, I guess with flags including the one that control whether a bridge should be created. Do you still see those bridges created for new instances? /Ihar On 29/10/14 11:26, Chris wrote: > Hello, > > 1) we just don't need it, we are using the provider network which > includes hardware firewalls. 2) We have huge performance problems > regarding TCP_CRR / TCP_RR. The OpenStack VMs can deal just half of > TCP connections per second compared to our bare metal installations. > Throughput (10Gbit NIC) is fine though. Specs VMs and bare metal are > of course equal (RAM, Cores, etc.) > > Did a lot of testing regarding the performance issues, it happens > "after" the both (br-int/br-ex) openvswitches. Upgraded ovs to version > 2.3 just fyi. > > Cheers Chris > > > -----Original Message----- From: rdo-list-bounces at redhat.com > [mailto:rdo-list-bounces at redhat.com] On Behalf Of Ihar Hrachyshka > Sent: Wednesday, October 29, 2014 16:51 To: rdo-list at redhat.com > Subject: Re: [Rdo-list] Compute Node without firewall (iptables) and > Linux bridge > > On 29/10/14 09:33, Chris wrote: >> Hello > > > >> I?m looking for a way to disable any firewall feature in one of our >> compute nodes and prevent the creation of the Linux bridge in the >> data path inside of this compute node. > > Can you elaborate on reasons to disable it? Of course it sounds a bit > not optimal, but do you have any performance concerns that you try to > address in this way? > > >> We using the RDO Icehouse release. > > > >> Here is the configuration in the compute node: > >> #/etc/neutron/plugin.ini > >> [securitygroup] > >> #firewall_driver = >> neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver > >> firewall_driver = neutron.agent.firewall.NoopFirewall > >> # enable_security_group = True > >> enable_security_group = False > > > >> #/etc/nova/nova.conf > >> firewall_driver = nova.virt.firewall.NoopFirewallDriver > >> #security_group_api = neutron > > > >> #/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini > >> [securitygroup] > >> firewall_driver = neutron.agent.firewall.NoopFirewallDriver > >> enable_security_group = False > > > >> The firewall seems to be disabled but the bridge and the interfaces >> are being still created. > >> I found an older post about it: >> http://lists.openstack.org/pipermail/openstack/2014-May/007079.html > >> But changing ?portbindings.OVS_HYBRID_PLUG" from a hard-coded "True" >> to "False" didn?t change anything. > > > >> Please advise! > > > >> Cheers > >> Chris > > > > > >> _______________________________________________ Rdo-list mailing list >> Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list > > > _______________________________________________ Rdo-list mailing list > Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list > > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUUR4LAAoJEC5aWaUY1u57uQgIAIUWQaBW9HshqnJiUSgsuH/5 9a7p0fZJW2JwhZ00TFq6K4njjPV2xnHKQrae1MbEduOD0SwpcXlzR2dXbOXLx8Mm swWJim87X4uKNnK2c6MD1WB7wB1d3yVS4SurgS7/DFPyQD1ysHq4FM/XyWSNGcy/ n2GW5TMNokFe6gLXU9r/yDQlsnQsARmK5wnZ63VXHl3S9qnH2gnLPsuZh7X3FUV8 RAsiA9IR2RqiBamS3oGssgP0zIxkNRUwS+muZx//dwRr1NkqZMBNrkdN2t/PZLnD MBwTX5e8uwJ1Jn5mQB7Wy9n1NdkNTPxZT2R5fBU70UVn8qJbXVzzyif7h4we0zU= =VUIE -----END PGP SIGNATURE----- From sgordon at redhat.com Thu Oct 30 11:53:24 2014 From: sgordon at redhat.com (Steve Gordon) Date: Thu, 30 Oct 2014 07:53:24 -0400 (EDT) Subject: [Rdo-list] Does PackStack still auto-enable EPEL? In-Reply-To: <1308944473.3261406.1414669933191.JavaMail.zimbra@redhat.com> Message-ID: <51259318.3261898.1414670004851.JavaMail.zimbra@redhat.com> Hi all, Following up on a user question from ask.o.o: https://ask.openstack.org/en/question/51619/rdo-quickstart-packstack-failure-files-not-installed/ Does PackStack still auto-enable EPEL as suggested here: https://openstack.redhat.com/Repositories#EPEL Also it seems some silent failures were encountered when required packages failed to install? Thanks, Steve From ihrachys at redhat.com Thu Oct 30 12:32:26 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Thu, 30 Oct 2014 13:32:26 +0100 Subject: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge In-Reply-To: <002d01cff430$3b2a01d0$b17e0570$@progbau.de> References: <006b01cff352$fddada80$f9908f80$@progbau.de> <5450B89D.9000604@redhat.com> <007501cff362$c7642f50$562c8df0$@progbau.de> <54511E0B.60604@redhat.com> <002d01cff430$3b2a01d0$b17e0570$@progbau.de> Message-ID: <54522FDA.7020002@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Do you use monolithic OVS plugin or ML2 mechanism? If the latter, then the file is not involved, and you should instead try to change the value in: /usr/lib/python2.6/site-packages/neutron/plugins/ml2/drivers/mech_openvswitch.py That said, removal of .py file is not enough to make sure it's not involved since .pyc file is still there and is used when there is no .py counterpart. On 30/10/14 11:56, Chris wrote: > I just found out that the file in the compute node: > /usr/lib/python2.6/site-packages/neutron/plugins/openvswitch/ovs_neutron_plu > > gin.py > where I edit the portbindings.OVS_HYBRID_PLUG doesn't has any > effect. I even can delete the whole file, the bridge is still being > created and everything works normal. > > Where I can edit the code to prevent the bridge creation? > > Cheers Chris > > -----Original Message----- From: Chris [mailto:contact at progbau.de] > Sent: Thursday, October 30, 2014 01:28 To: 'Ihar Hrachyshka'; > 'rdo-list at redhat.com' Subject: RE: [Rdo-list] Compute Node without > firewall (iptables) and Linux bridge > > What do you mean with re-plugged? During my testing I always delete > and create new Instances and every time the Linux bridge+interfaces > gets deleted and created as well. > > Cheers Chris > > -----Original Message----- From: Ihar Hrachyshka > [mailto:ihrachys at redhat.com] Sent: Thursday, October 30, 2014 > 00:04 To: Chris; rdo-list at redhat.com Subject: Re: [Rdo-list] > Compute Node without firewall (iptables) and Linux bridge > > Have you replugged your instances? VIF objects are persisted in db, > I guess with flags including the one that control whether a bridge > should be created. > > Do you still see those bridges created for new instances? > > /Ihar > > On 29/10/14 11:26, Chris wrote: >> Hello, > >> 1) we just don't need it, we are using the provider network which >> includes hardware firewalls. 2) We have huge performance >> problems regarding TCP_CRR / TCP_RR. The OpenStack VMs can deal >> just half of TCP connections per second compared to our bare >> metal installations. Throughput (10Gbit NIC) is fine though. >> Specs VMs and bare metal are of course equal (RAM, Cores, etc.) > >> Did a lot of testing regarding the performance issues, it happens >> "after" the both (br-int/br-ex) openvswitches. Upgraded ovs to >> version 2.3 just fyi. > >> Cheers Chris > > >> -----Original Message----- From: rdo-list-bounces at redhat.com >> [mailto:rdo-list-bounces at redhat.com] On Behalf Of Ihar >> Hrachyshka Sent: Wednesday, October 29, 2014 16:51 To: >> rdo-list at redhat.com Subject: Re: [Rdo-list] Compute Node without >> firewall (iptables) and Linux bridge > >> On 29/10/14 09:33, Chris wrote: >>> Hello > > > >>> I?m looking for a way to disable any firewall feature in one of >>> our compute nodes and prevent the creation of the Linux bridge >>> in the data path inside of this compute node. > >> Can you elaborate on reasons to disable it? Of course it sounds a >> bit not optimal, but do you have any performance concerns that >> you try to address in this way? > > >>> We using the RDO Icehouse release. > > > >>> Here is the configuration in the compute node: > >>> #/etc/neutron/plugin.ini > >>> [securitygroup] > >>> #firewall_driver = >>> neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver > >>> firewall_driver = neutron.agent.firewall.NoopFirewall > >>> # enable_security_group = True > >>> enable_security_group = False > > > >>> #/etc/nova/nova.conf > >>> firewall_driver = nova.virt.firewall.NoopFirewallDriver > >>> #security_group_api = neutron > > > >>> #/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini > >>> [securitygroup] > >>> firewall_driver = neutron.agent.firewall.NoopFirewallDriver > >>> enable_security_group = False > > > >>> The firewall seems to be disabled but the bridge and the >>> interfaces are being still created. > >>> I found an older post about it: >>> http://lists.openstack.org/pipermail/openstack/2014-May/007079.html > >>> But changing ?portbindings.OVS_HYBRID_PLUG" from a hard-coded >>> "True" to "False" didn?t change anything. > > > >>> Please advise! > > > >>> Cheers > >>> Chris > > > > > >>> _______________________________________________ Rdo-list >>> mailing list Rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list > > >> _______________________________________________ Rdo-list mailing >> list Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list > > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUUi/aAAoJEC5aWaUY1u57yAcH/1fMcyEdAUm9xE+cKtPbCcTu A1N1dEE2ndCL+xbOYB6jCRCnsf1wpCkjSFhacNUdRrJYm77/3Yn75uFsw0CVPro7 FZu0oXjQWaAVTShduyvvVa0KPamjneL2QiNZsGoVbmHt2FzeYD7fmU6iC7FWy/aK s5flbfYHekTwxBQnp+CjVz7JT+plx8YFkZOq6sog342SIWzw6Zfu0CcdGP6WRg47 ltUMnqp5o8SD03960EwfL8/tfZ4T3/GlQ2s+Me+i1rlPQ82Knruemn1eAXWf83Kg 4CCBcQIpf3PCqC+/k+Ac2R5ifoHFlS/F4ma1ErYWsldjD+Gc5NmYWMOoQqrNUiw= =Xhb+ -----END PGP SIGNATURE----- From nikeshmahalka at vedams.com Thu Oct 30 13:19:19 2014 From: nikeshmahalka at vedams.com (Nikesh Kumar Mahalka) Date: Thu, 30 Oct 2014 18:49:19 +0530 Subject: [Rdo-list] Will RDO support Juno on CentOS6? Message-ID: Hi, there is also one discussion on this https://www.redhat.com/archives/rdo-list/2014-September/msg00128.html but i have one doubt: if we install python2.7 on rhel6.5,then will openstack juno support in rhel6.5? Regards Nikesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Thu Oct 30 13:45:51 2014 From: rbowen at redhat.com (Rich Bowen) Date: Thu, 30 Oct 2014 09:45:51 -0400 Subject: [Rdo-list] Community meetup at OpenStack Summit Message-ID: <5452410F.80602@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There have been a number of conversations going on about having an informal RDO community meetup at OpenStack Summit next week in Paris. You may have seen the conversation about doing a BOF, and that there are no plans to have BOF rooms available at the venue. Two alternate plans have been discussed. We're currently planning to have a conversation over lunch on Wednesday, which is when some people are able to attend. We're also investigating getting a meeting room at the Meriden, across the street from the conference venue, for Wednesday evening, after the last session (ends 18:10) and before the Red Hat/eNovance party (starts 20:00). Topics to discuss include getting more non-Red Hat people involved in RDO packaging, and the steps to get to that reality. How many people would be interested in attending such a meetup? If you are, please make a note on https://etherpad.openstack.org/p/RDO_Meetup_Summit We're still investigating evening meeting room options, so that's still tentative at this point, and we'll probably keep the Lunch gathering either way. - --Rich - -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRSQQ8ACgkQXP03+sx4yJPwnQCg3tqC6dnXoY5jzboa9cDviU/g KoMAn1D/8n8xLmDTiroHurgheo7+Qjyu =uQfP -----END PGP SIGNATURE----- From rbowen at redhat.com Thu Oct 30 14:28:19 2014 From: rbowen at redhat.com (Rich Bowen) Date: Thu, 30 Oct 2014 10:28:19 -0400 Subject: [Rdo-list] Clouds, Containers, and Orchestration Miniconf (Linux.conf.au 2015) Message-ID: <54524B03.4070508@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If you're going to be at Linux.conf.au, consider submitting a talk for the Clouds, Containers, and Orchestration Miniconf Details are at http://dissociatedpress.net/miniconf/ - -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRSSwMACgkQXP03+sx4yJNergCcCPay44zAwzuVH0eJBoRzxTvo pMAAn0Fl8QvkCvl4YW0+5SIPLOa19ytY =wI7s -----END PGP SIGNATURE----- From mail-lists at karan.org Thu Oct 30 14:36:56 2014 From: mail-lists at karan.org (Karanbir Singh) Date: Thu, 30 Oct 2014 14:36:56 +0000 Subject: [Rdo-list] RDO Juno packages available In-Reply-To: <1414456862.4936.2.camel@localhost.localdomain> References: <544E8BDD.9050100@redhat.com> <544EE188.3000407@karan.org> <1414456862.4936.2.camel@localhost.localdomain> Message-ID: <54524D08.6010504@karan.org> On 28/10/14 00:41, whayutin wrote: > On Tue, 2014-10-28 at 00:21 +0000, Karanbir Singh wrote: >> On 27/10/14 18:15, Rich Bowen wrote: >>> We're pleased to announce the availability of RDO packages for OpenStack Juno, for EL7 (RHEL7 and CentOS7) and Fedora 20. >>> >>> Fedora 21 is still in development and running RDO Juno on Fedora 21 is not recommended at this time. A separate announcement will be made when RDO Juno on Fedora 21 is ready. >>> >>> You can get started with RDO Juno via the process described in the Quickstart - http://openstack.redhat.com/Quickstart - and the various packages are available at https://rdo.fedorapeople.org/openstack-juno/ >>> >>> As always, if you have questions, you can bring them here, to the rdo-list mailing list, or to the IRC channel - #rdo on freenode.irc.net. >>> >>> Thanks for being part of the RDO community! >> >> the nightly installer on centos7 was still failing so I went had a look, >> turns out that if the root account already has a authorized_keys setup >> the packstack allinone operation fails with a permissions denied. >> >> just manually copying id_rsa.pub into the root's auth keys allows it to >> go past that bit. >> >> this was a problem here since the nighly installer test runs in a VM >> that is itself contexualised with cloud-init, running under a cloud setup. >> >> > > Karanbir, > A freshly provisioned CentOS machine would not have an id_rsa key > created right? It's good to know of course, but afaict not something > that needs to be added to the instructions. I agree, a typical machine would not have a key there already. However for the automated tests, we need a way for the script to instantiate and then get into the instance ( in this case, a physical machine ) - so a key was being setup. is it possible to have packstack add a key rather, if there already was one present ? havent put this on bz since I'm not sure if its bz worthy a conversation as yet. - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From kchamart at redhat.com Thu Oct 30 15:25:05 2014 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Thu, 30 Oct 2014 16:25:05 +0100 Subject: [Rdo-list] Community meetup at OpenStack Summit In-Reply-To: <5452410F.80602@redhat.com> References: <5452410F.80602@redhat.com> Message-ID: <20141030152505.GA20708@tesla.redhat.com> On Thu, Oct 30, 2014 at 09:45:51AM -0400, Rich Bowen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > There have been a number of conversations going on about having an > informal RDO community meetup at OpenStack Summit next week in Paris. > You may have seen the conversation about doing a BOF, and that there > are no plans to have BOF rooms available at the venue. > > Two alternate plans have been discussed. We're currently planning to > have a conversation over lunch on Wednesday, which is when some people > are able to attend. > > We're also investigating getting a meeting room at the Meriden, across > the street from the conference venue, for Wednesday evening, after the > last session (ends 18:10) and before the Red Hat/eNovance party > (starts 20:00). > > Topics to discuss include getting more non-Red Hat people involved in > RDO packaging, and the steps to get to that reality. > > How many people would be interested in attending such a meetup? If you > are, please make a note on > https://etherpad.openstack.org/p/RDO_Meetup_Summit It would also help save time and have a productive discussion, if people already start adding Agenda items there. As a starter, I added a topic for bug triage (if anyone wants to discuss), with the current status of RDO bugs: https://kashyapc.fedorapeople.org/virt/openstack/bugzilla/rdo-bug-status/all-rdo-bugs-30-10-2014.txt > > We're still investigating evening meeting room options, so that's > still tentative at this point, and we'll probably keep the Lunch > gathering either way. -- /kashyap From aortega at redhat.com Thu Oct 30 18:18:38 2014 From: aortega at redhat.com (Alvaro Lopez Ortega) Date: Thu, 30 Oct 2014 19:18:38 +0100 Subject: [Rdo-list] Concerning Rabbits In-Reply-To: References: <871tzihjnk.fsf@redhat.com> <20140204174420.GB19248@redhat.com> <20140206162016.GW19248@redhat.com> <52F43035.1050100@redhat.com> <52F4315A.7000408@redhat.com> <20140207051525.GB11378@redhat.com> <631192AF-C773-43E3-BB70-1718BA95E1F2@redhat.com> Message-ID: <545280FE.6050404@redhat.com> On 02/07/2014 03:27 PM, Shake Chen wrote: > I just want to know how long the packstack can support RabbitMQ? Packstack supports RabbitMQ since May. Moreover, it's been the default AMQP since then. The CONFIG_AMQP_BACKEND configuration option, and the --amqp-backend parameter allow to choose between qpid and rabbitmq. Best, Alvaro From ak at cloudssky.com Thu Oct 30 20:41:20 2014 From: ak at cloudssky.com (Arash Kaffamanesh) Date: Thu, 30 Oct 2014 21:41:20 +0100 Subject: [Rdo-list] RDO Juno with Foreman on CentOS or Fedora Message-ID: Hello everyone, Has anyone tried to deploy Juno with Foreman on CentOS 7 or Fedora 20? As I can see, staypuft supports currently CentOS 6.5 and Fedora 19: https://github.com/theforeman/staypuft If Juno is currently not supported by foreman, can I go with staypuft for Icehouse? Thanks! -Arash -------------- next part -------------- An HTML attachment was scrubbed... URL: From mburns at redhat.com Thu Oct 30 21:35:49 2014 From: mburns at redhat.com (Mike Burns) Date: Thu, 30 Oct 2014 17:35:49 -0400 Subject: [Rdo-list] RDO Juno with Foreman on CentOS or Fedora In-Reply-To: References: Message-ID: <5452AF35.6090308@redhat.com> Hi Arash On 10/30/2014 04:41 PM, Arash Kaffamanesh wrote: > Hello everyone, > > Has anyone tried to deploy Juno with Foreman on CentOS 7 or Fedora 20? > As I can see, staypuft supports currently CentOS 6.5 and Fedora 19: > https://github.com/theforeman/staypuft AFAIK, there has been very little testing with either Foreman (assuming you mean the astapor/openstack-foreman-installer stuff here) or Staypuft on top of Juno. There is a fair amount of work ongoing to update all the puppet classes to support Juno, but I don't know that it's all 100% complete yet. As for Staypuft, you can deploy it on CentOS 6.5 and then use it to deploy OpenStack to CentOS 7. There has been minimal/no testing done against Fedora for either the OFI or Staypuft deployment methods. > > If Juno is currently not supported by foreman, can I go with staypuft > for Icehouse? > This should work for you. I know there have been others who have done this with some success. If you do run into issues, please raise them either here on rdo-list, or on Freenode in the #staypuft or #rdo channels. Thanks Mike > Thanks! > -Arash > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > From sayganesha at gmail.com Thu Oct 30 23:24:12 2014 From: sayganesha at gmail.com (Ganesh Sangle) Date: Thu, 30 Oct 2014 16:24:12 -0700 Subject: [Rdo-list] cinder install Message-ID: trying to install openstack-cinder on rhel fails. Any ideas what could be the issue ? (Redhat verison: Scientific Linux release 6.1 (Carbon)) > sudo yum install -y openstack-cinder Loaded plugins: security http://repos.fedorapeople.org/repos/openstack/openstack-juno/epel-6/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found" Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: openstack-juno. Please verify its path and try again -------------- next part -------------- An HTML attachment was scrubbed... URL: From contact at progbau.de Fri Oct 31 04:02:42 2014 From: contact at progbau.de (Chris) Date: Fri, 31 Oct 2014 11:02:42 +0700 Subject: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge In-Reply-To: <54522FDA.7020002@redhat.com> References: <006b01cff352$fddada80$f9908f80$@progbau.de> <5450B89D.9000604@redhat.com> <007501cff362$c7642f50$562c8df0$@progbau.de> <54511E0B.60604@redhat.com> <002d01cff430$3b2a01d0$b17e0570$@progbau.de> <54522FDA.7020002@redhat.com> Message-ID: <002e01cff4bf$87579ab0$9606d010$@progbau.de> We use the ML2 openvswitch driver. Renamed (pyc/pyo)/edited(py) the following files, nothing changed at all, it seems like none of this files is involved. Just to clarify all the changes I do are in one particular test compute node, I didn't change anything in the network node: /usr/lib/python2.6/site-packages/neutron/plugins/openvswitch/ovs_neutron_plu gin.py /usr/lib/python2.6/site-packages/neutron/plugins/openvswitch/ovs_neutron_plu gin.pyc /usr/lib/python2.6/site-packages/neutron/plugins/openvswitch/ovs_neutron_plu gin.pyo /usr/lib/python2.6/site-packages/neutron/plugins/ml2/drivers/mech_openvswitc h.py /usr/lib/python2.6/site-packages/neutron/plugins/ml2/drivers/mech_openvswitc h.pyc /usr/lib/python2.6/site-packages/neutron/plugins/ml2/drivers/mech_openvswitc h.pyo Cheers Chris -----Original Message----- From: Ihar Hrachyshka [mailto:ihrachys at redhat.com] Sent: Thursday, October 30, 2014 19:32 To: Chris; rdo-list at redhat.com Cc: randy.krenz at overturenetworks.com Subject: Re: [Rdo-list] Compute Node without firewall (iptables) and Linux bridge -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Do you use monolithic OVS plugin or ML2 mechanism? If the latter, then the file is not involved, and you should instead try to change the value in: /usr/lib/python2.6/site-packages/neutron/plugins/ml2/drivers/mech_openvswitc h.py That said, removal of .py file is not enough to make sure it's not involved since .pyc file is still there and is used when there is no .py counterpart. On 30/10/14 11:56, Chris wrote: > I just found out that the file in the compute node: > /usr/lib/python2.6/site-packages/neutron/plugins/openvswitch/ovs_neutr > on_plu > > gin.py > where I edit the portbindings.OVS_HYBRID_PLUG doesn't has any effect. > I even can delete the whole file, the bridge is still being created > and everything works normal. > > Where I can edit the code to prevent the bridge creation? > > Cheers Chris > > -----Original Message----- From: Chris [mailto:contact at progbau.de] > Sent: Thursday, October 30, 2014 01:28 To: 'Ihar Hrachyshka'; > 'rdo-list at redhat.com' Subject: RE: [Rdo-list] Compute Node without > firewall (iptables) and Linux bridge > > What do you mean with re-plugged? During my testing I always delete > and create new Instances and every time the Linux bridge+interfaces > gets deleted and created as well. > > Cheers Chris > > -----Original Message----- From: Ihar Hrachyshka > [mailto:ihrachys at redhat.com] Sent: Thursday, October 30, 2014 > 00:04 To: Chris; rdo-list at redhat.com Subject: Re: [Rdo-list] Compute > Node without firewall (iptables) and Linux bridge > > Have you replugged your instances? VIF objects are persisted in db, I > guess with flags including the one that control whether a bridge > should be created. > > Do you still see those bridges created for new instances? > > /Ihar > > On 29/10/14 11:26, Chris wrote: >> Hello, > >> 1) we just don't need it, we are using the provider network which >> includes hardware firewalls. 2) We have huge performance problems >> regarding TCP_CRR / TCP_RR. The OpenStack VMs can deal just half of >> TCP connections per second compared to our bare metal installations. >> Throughput (10Gbit NIC) is fine though. >> Specs VMs and bare metal are of course equal (RAM, Cores, etc.) > >> Did a lot of testing regarding the performance issues, it happens >> "after" the both (br-int/br-ex) openvswitches. Upgraded ovs to >> version 2.3 just fyi. > >> Cheers Chris > > >> -----Original Message----- From: rdo-list-bounces at redhat.com >> [mailto:rdo-list-bounces at redhat.com] On Behalf Of Ihar Hrachyshka >> Sent: Wednesday, October 29, 2014 16:51 To: >> rdo-list at redhat.com Subject: Re: [Rdo-list] Compute Node without >> firewall (iptables) and Linux bridge > >> On 29/10/14 09:33, Chris wrote: >>> Hello > > > >>> I?m looking for a way to disable any firewall feature in one of our >>> compute nodes and prevent the creation of the Linux bridge in the >>> data path inside of this compute node. > >> Can you elaborate on reasons to disable it? Of course it sounds a bit >> not optimal, but do you have any performance concerns that you try to >> address in this way? > > >>> We using the RDO Icehouse release. > > > >>> Here is the configuration in the compute node: > >>> #/etc/neutron/plugin.ini > >>> [securitygroup] > >>> #firewall_driver = >>> neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDrive >>> r > >>> firewall_driver = neutron.agent.firewall.NoopFirewall > >>> # enable_security_group = True > >>> enable_security_group = False > > > >>> #/etc/nova/nova.conf > >>> firewall_driver = nova.virt.firewall.NoopFirewallDriver > >>> #security_group_api = neutron > > > >>> #/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini > >>> [securitygroup] > >>> firewall_driver = neutron.agent.firewall.NoopFirewallDriver > >>> enable_security_group = False > > > >>> The firewall seems to be disabled but the bridge and the interfaces >>> are being still created. > >>> I found an older post about it: >>> http://lists.openstack.org/pipermail/openstack/2014-May/007079.html > >>> But changing ?portbindings.OVS_HYBRID_PLUG" from a hard-coded >>> "True" to "False" didn?t change anything. > > > >>> Please advise! > > > >>> Cheers > >>> Chris > > > > > >>> _______________________________________________ Rdo-list mailing >>> list Rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list > > >> _______________________________________________ Rdo-list mailing list >> Rdo-list at redhat.com https://www.redhat.com/mailman/listinfo/rdo-list > > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUUi/aAAoJEC5aWaUY1u57yAcH/1fMcyEdAUm9xE+cKtPbCcTu A1N1dEE2ndCL+xbOYB6jCRCnsf1wpCkjSFhacNUdRrJYm77/3Yn75uFsw0CVPro7 FZu0oXjQWaAVTShduyvvVa0KPamjneL2QiNZsGoVbmHt2FzeYD7fmU6iC7FWy/aK s5flbfYHekTwxBQnp+CjVz7JT+plx8YFkZOq6sog342SIWzw6Zfu0CcdGP6WRg47 ltUMnqp5o8SD03960EwfL8/tfZ4T3/GlQ2s+Me+i1rlPQ82Knruemn1eAXWf83Kg 4CCBcQIpf3PCqC+/k+Ac2R5ifoHFlS/F4ma1ErYWsldjD+Gc5NmYWMOoQqrNUiw= =Xhb+ -----END PGP SIGNATURE----- From ihrachys at redhat.com Fri Oct 31 10:30:16 2014 From: ihrachys at redhat.com (Ihar Hrachyshka) Date: Fri, 31 Oct 2014 11:30:16 +0100 Subject: [Rdo-list] cinder install In-Reply-To: References: Message-ID: <545364B8.3070902@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 As was already discussed multiple times before, there is no RDO Juno release for EL6 platform. If you want to use RDO Juno, you will need to run it on top of either EL7 or Fedora 20+. On 31/10/14 00:24, Ganesh Sangle wrote: > trying to install openstack-cinder on rhel fails. Any ideas what > could be the issue ? > > (Redhat verison: Scientific Linux release 6.1 (Carbon)) > >> sudo yum install -y openstack-cinder > Loaded plugins: security > http://repos.fedorapeople.org/repos/openstack/openstack-juno/epel-6/repodata/repomd.xml: > > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not > Found" Trying other mirror. Error: Cannot retrieve repository > metadata (repomd.xml) for repository: openstack-juno. Please verify > its path and try again > > > _______________________________________________ Rdo-list mailing > list Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUU2S4AAoJEC5aWaUY1u57aTYIAKsLvp7WC0HdSMuH+R2nEaMF CZpxTlbgTXno4zu1ivgiy87C++HymSZspoENFqoeDLEQFJPWLQKgZ7oPsEX2HCg1 3NNZVccxFUrWcOygJvA6VT97ox9KugBRFwk/8Rt+WFNFoLnywpNviPyiAgC0MW5a 78Z+xkUWhHMauPupOszmHHTzPxTBFbJ5CqH6qKPlBi9DUyNy5zEP5XsaYRyf58oC /Z+h2Hfeu8HeHmqDl2GpEj1+ITnnA3IEQMenPjPkqDpO3Owj9gXocEudulNsqQ4e dgHKoroXCAi09o7ekQAiPBxp3uIBsK4fll33tgHe0nnm4+o1GAa2UFhZv/9Arh4= =vCXU -----END PGP SIGNATURE----- From rbowen at redhat.com Fri Oct 31 18:07:34 2014 From: rbowen at redhat.com (Rich Bowen) Date: Fri, 31 Oct 2014 14:07:34 -0400 Subject: [Rdo-list] Community meetup at OpenStack Summit In-Reply-To: <5452410F.80602@redhat.com> References: <5452410F.80602@redhat.com> Message-ID: <5453CFE6.1010204@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 So, it appears that a lunch meeting is difficult. Lauren's response about commandeering a table at lunch can be seen at http://lists.openstack.org/pipermail/community/2014-October/000930.html but the summary is that, since the summit is sold out, they don't want us to take any more time than necessary at lunch tables, but just eat and free it up for the next people. Remaining options include: * Meet at nearby restaurant. We're investigating the possibility of reserving seating for 20-30 somewhere in walking distance. * Obtain a BoF room, since this is a community event, which happens *during* conference sessions. This means that people would have to choose between this event and a session, which is unfortunate. * Evening event, which is also difficult due to how packed every evening of the event is. All three of these are possible, but each has problems. Getting a room at the Meridien or the Hyatt has proved to be very expensive. So, in summary, we're still going to try really hard to do this meetup, but we're still unsure where and when it's going to happen. Thanks for your patience, and I'll be sure to let you know as soon as we have something more definite. - --Rich On 10/30/2014 09:45 AM, Rich Bowen wrote: > There have been a number of conversations going on about having an > informal RDO community meetup at OpenStack Summit next week in > Paris. You may have seen the conversation about doing a BOF, and > that there are no plans to have BOF rooms available at the venue. > > Two alternate plans have been discussed. We're currently planning > to have a conversation over lunch on Wednesday, which is when some > people are able to attend. > > We're also investigating getting a meeting room at the Meriden, > across the street from the conference venue, for Wednesday evening, > after the last session (ends 18:10) and before the Red Hat/eNovance > party (starts 20:00). > > Topics to discuss include getting more non-Red Hat people involved > in RDO packaging, and the steps to get to that reality. > > How many people would be interested in attending such a meetup? If > you are, please make a note on > https://etherpad.openstack.org/p/RDO_Meetup_Summit > > We're still investigating evening meeting room options, so that's > still tentative at this point, and we'll probably keep the Lunch > gathering either way. > > --Rich > > > > > _______________________________________________ Rdo-list mailing > list Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > - -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRTz+YACgkQXP03+sx4yJNUpACggkCfRhmdM2MwIrGt/Rfe2cnW SkAAn1EqTFMJQfUmsbCvof6UyZGYA1Yv =TXnI -----END PGP SIGNATURE----- From kchamart at redhat.com Fri Oct 31 18:37:36 2014 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Fri, 31 Oct 2014 19:37:36 +0100 Subject: [Rdo-list] Community meetup at OpenStack Summit In-Reply-To: <5453CFE6.1010204@redhat.com> References: <5452410F.80602@redhat.com> <5453CFE6.1010204@redhat.com> Message-ID: <20141031183736.GB18647@tesla.redhat.com> On Fri, Oct 31, 2014 at 02:07:34PM -0400, Rich Bowen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > So, it appears that a lunch meeting is difficult. Lauren's response > about commandeering a table at lunch can be seen at > http://lists.openstack.org/pipermail/community/2014-October/000930.html but > the summary is that, since the summit is sold out, they don't want us > to take any more time than necessary at lunch tables, but just eat and > free it up for the next people. > > Remaining options include: > > * Meet at nearby restaurant. We're investigating the possibility of > reserving seating for 20-30 somewhere in walking distance. > > * Obtain a BoF room, since this is a community event, which happens > *during* conference sessions. This means that people would have to > choose between this event and a session, which is unfortunate. > > * Evening event, which is also difficult due to how packed every > evening of the event is. > > All three of these are possible, but each has problems. Getting a room > at the Meridien or the Hyatt has proved to be very expensive. > > So, in summary, we're still going to try really hard to do this > meetup, but we're still unsure where and when it's going to happen. > Thanks for your patience, and I'll be sure to let you know as soon as > we have something more definite. As discussed on #rdo, as a worst case - since this is a public, open meeting, we can just meetup in the hallway somewhere (probably near the RDO booth, if space works out). -- /kashyap From rbowen at redhat.com Fri Oct 31 18:45:43 2014 From: rbowen at redhat.com (Rich Bowen) Date: Fri, 31 Oct 2014 14:45:43 -0400 Subject: [Rdo-list] Community meetup at OpenStack Summit In-Reply-To: <20141031183736.GB18647@tesla.redhat.com> References: <5452410F.80602@redhat.com> <5453CFE6.1010204@redhat.com> <20141031183736.GB18647@tesla.redhat.com> Message-ID: <5453D8D7.5040403@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/31/2014 02:37 PM, Kashyap Chamarthy wrote: > On Fri, Oct 31, 2014 at 02:07:34PM -0400, Rich Bowen wrote: >> So, in summary, we're still going to try really hard to do this >> meetup, but we're still unsure where and when it's going to >> happen. Thanks for your patience, and I'll be sure to let you >> know as soon as we have something more definite. > > As discussed on #rdo, as a worst case - since this is a public, > open meeting, we can just meetup in the hallway somewhere (probably > near the RDO booth, if space works out). > You can see a venue map at https://www.openstack.org/assets/paris-summit/OS14ParisMapLevel01.pdf and RDO is in the Red Hat booth at the top left. I can't really tell what the Parc du Marche is - whether that's a space that we can actually use for this kind of thing or not - but I suspect that we'd be more likely to find room in one of the lounge areas over in H?tel Le M?ridien, across the street, where the design summit is being held. We'll scope it out when we get there, and make a sign to put up at the booth. And I'm also waiting to hear back from Lauren as to what rooms might be available. - -- Rich Bowen - rbowen at redhat.com OpenStack Community Liaison http://openstack.redhat.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRT2NYACgkQXP03+sx4yJNEvwCeLbA7C1j3wND5MjnV0rqq6mAi +48An2s13JEuHuokS/jYZQ2S6hnYn5Ug =tD3w -----END PGP SIGNATURE----- From apevec at gmail.com Fri Oct 31 22:52:57 2014 From: apevec at gmail.com (Alan Pevec) Date: Fri, 31 Oct 2014 23:52:57 +0100 Subject: [Rdo-list] RDO Juno packages available In-Reply-To: <54524D08.6010504@karan.org> References: <544E8BDD.9050100@redhat.com> <544EE188.3000407@karan.org> <1414456862.4936.2.camel@localhost.localdomain> <54524D08.6010504@karan.org> Message-ID: 2014-10-30 15:36 GMT+01:00 Karanbir Singh : > is it possible to have packstack add a key rather, if there already was > one present ? > > havent put this on bz since I'm not sure if its bz worthy a conversation > as yet. Definitely upstream bug report worthy, I've filed https://bugs.launchpad.net/packstack/+bug/1388280 BZ would be for packaging issues only. Cheers, Alan From apevec at gmail.com Fri Oct 31 23:47:12 2014 From: apevec at gmail.com (Alan Pevec) Date: Sat, 1 Nov 2014 00:47:12 +0100 Subject: [Rdo-list] Will RDO support Juno on CentOS6? In-Reply-To: References: Message-ID: 2014-10-30 14:19 GMT+01:00 Nikesh Kumar Mahalka : > there is also one discussion on this > https://www.redhat.com/archives/rdo-list/2014-September/msg00128.html > > but i have one doubt: > if we install python2.7 on rhel6.5,then will openstack juno support in > rhel6.5? I know about python26 for RHEL5 http://koji.fedoraproject.org/koji/packageinfo?packageID=10196 haven't seen python27 for RHEL6... Anyway, why not just upgrade to EL7 instead of creating unsupportable monster on EL6 ? It will be more work, there's at least systemd / initscripts difference and too old python libraries on EL6, also need to review what libvirt/qemu/kernel features are actually available on EL6, e.g. nova/virt/libvirt/driver.py is checking libvirt version while EL6 libvirt might have backported features in the lower version. Cheers, Alan From apevec at gmail.com Fri Oct 31 23:56:13 2014 From: apevec at gmail.com (Alan Pevec) Date: Sat, 1 Nov 2014 00:56:13 +0100 Subject: [Rdo-list] Does PackStack still auto-enable EPEL? In-Reply-To: <51259318.3261898.1414670004851.JavaMail.zimbra@redhat.com> References: <1308944473.3261406.1414669933191.JavaMail.zimbra@redhat.com> <51259318.3261898.1414670004851.JavaMail.zimbra@redhat.com> Message-ID: > Does PackStack still auto-enable EPEL as suggested here: enable-epel patch was lost in openstack-packstack-2014.1.1-0.29.dev1251 fixed in openstack-packstack-2014.1.1-0.29.1.dev1251 which is now in RDO Icehouse repo There was a better fix done upstream, so it doesn't get lost on the next rebase: https://review.openstack.org/131175 > Also it seems some silent failures were encountered when required packages failed to install? Also fixed upstream https://review.openstack.org/131217 Cheers, Alan