From agamal at itsyn.com Mon Jun 3 12:41:31 2013 From: agamal at itsyn.com (Ali Gamal) Date: Mon, 3 Jun 2013 14:41:31 +0200 Subject: [Rdo-list] (no subject) Message-ID: Regards, Ali Gamal. Linux System Engineer , CTI Department. Cell: +20 1000559217. -------------- next part -------------- An HTML attachment was scrubbed... URL: From agamal at itsyn.com Mon Jun 3 12:42:57 2013 From: agamal at itsyn.com (Ali Gamal) Date: Mon, 3 Jun 2013 14:42:57 +0200 Subject: [Rdo-list] (no subject) Message-ID: Regards, Ali Gamal. Linux System Engineer , CTI Department. Cell: +20 1000559217. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pbrady at redhat.com Wed Jun 5 12:18:01 2013 From: pbrady at redhat.com (=?ISO-8859-1?Q?P=E1draig_Brady?=) Date: Wed, 05 Jun 2013 13:18:01 +0100 Subject: [Rdo-list] [package announce] packstack updated Message-ID: <51AF2C79.9040906@redhat.com> update: openstack-packstack-2013.1.1-0.9.dev605.el6 * Wed Jun 05 2013 Martin M?gr - 2013.1.1-0.9.dev605 - Added whitespace filter to Nova and Quantum plugins (rhbz#970674) - Removed RDO repo installation procedure * Tue Jun 04 2013 Martin M?gr - 2013.1.1-0.8.dev601 - rhbz#953157, rhbz#966560, rhbz#967291, rhbz#967306, rhbz#967307, rhbz#967344, rhbz#967348, rhbz#969975, rhbz#965787 From pbrady at redhat.com Wed Jun 5 12:22:18 2013 From: pbrady at redhat.com (=?ISO-8859-1?Q?P=E1draig_Brady?=) Date: Wed, 05 Jun 2013 13:22:18 +0100 Subject: [Rdo-list] [package announce] keystoneclient updated Message-ID: <51AF2D7A.2060105@redhat.com> update: python-keystoneclient-0.2.3-4.el6 * Tue May 28 2013 Jakub Ruzicka 0.2.3-4 - Check token expiry. (CVE-2013-2104) * Thu May 02 2013 Jakub Ruzicka 0.2.3-3 - Config value for revocation list timeout. (#923519) From pbrady at redhat.com Wed Jun 5 12:24:20 2013 From: pbrady at redhat.com (=?ISO-8859-1?Q?P=E1draig_Brady?=) Date: Wed, 05 Jun 2013 13:24:20 +0100 Subject: [Rdo-list] [package announce] quantum updated Message-ID: <51AF2DF4.8060704@redhat.com> update: openstack-quantum-2013.1.1-6.el6 * Sun May 26 2013 Gary Kotton - 2013.1.1-6 - Fixes rootwrap path * Fri May 24 2013 P?draig Brady

- 2013.1.1-5 - Fix inclusion of db migrations * Wed May 22 2013 Gary Kotton - 2013.1.1-3 - Updates to work with namespaces - Fix kill-metadata rootwrap filter * Mon May 13 2013 Gary Kotton - 2013.1.1-2 - Update to grizzly stable release 2013.1.1 - Update install scripts to configure security groups - Update install scripts to remove virtual interface configurations From dennisml at conversis.de Thu Jun 6 00:20:12 2013 From: dennisml at conversis.de (Dennis Jacobfeuerborn) Date: Thu, 06 Jun 2013 02:20:12 +0200 Subject: [Rdo-list] consoleauth package? Message-ID: <51AFD5BC.4070405@conversis.de> Hi, I'm trying to get the console tab in horizon working but right now I only see "loading..." which times out after a while. According to the documentation novncproxy needs the consoleauth service and I found various pages on the web describing the installation of the openstack-nova-consoleauth rpm yet this doesn't seem to be available in the RDO repo. Is this no longer required or is it now part of another package? Regards, Dennis From pbrady at redhat.com Thu Jun 6 01:29:10 2013 From: pbrady at redhat.com (=?ISO-8859-1?Q?P=E1draig_Brady?=) Date: Thu, 06 Jun 2013 02:29:10 +0100 Subject: [Rdo-list] consoleauth package? In-Reply-To: <51AFD5BC.4070405@conversis.de> References: <51AFD5BC.4070405@conversis.de> Message-ID: <51AFE5E6.6080100@redhat.com> On 06/06/2013 01:20 AM, Dennis Jacobfeuerborn wrote: > Hi, > I'm trying to get the console tab in horizon working but right now I only see "loading..." which times out after a while. According to the documentation novncproxy needs the consoleauth service and I found various pages on the web describing the installation of the openstack-nova-consoleauth rpm yet this doesn't seem to be available in the RDO repo. > Is this no longer required or is it now part of another package? $ repoquery --file /usr/bin/nova-consoleauth openstack-nova-console thanks, P?draig. From dennisml at conversis.de Thu Jun 6 11:54:05 2013 From: dennisml at conversis.de (Dennis Jacobfeuerborn) Date: Thu, 06 Jun 2013 13:54:05 +0200 Subject: [Rdo-list] consoleauth package? In-Reply-To: <51AFE5E6.6080100@redhat.com> References: <51AFD5BC.4070405@conversis.de> <51AFE5E6.6080100@redhat.com> Message-ID: <51B0785D.40600@conversis.de> On 06.06.2013 03:29, P?draig Brady wrote: > On 06/06/2013 01:20 AM, Dennis Jacobfeuerborn wrote: >> Hi, >> I'm trying to get the console tab in horizon working but right now I only see "loading..." which times out after a while. According to the documentation novncproxy needs the consoleauth service and I found various pages on the web describing the installation of the openstack-nova-consoleauth rpm yet this doesn't seem to be available in the RDO repo. >> Is this no longer required or is it now part of another package? > > $ repoquery --file /usr/bin/nova-consoleauth > openstack-nova-console Ah, I wasn't paying attention to that package because the documentation describes nova-console as XenAPI specific and not to be confused with the separate nova-consoleauth. Thanks for the pointer. I now get the "shell" in the console tab but the vnc console itself doesn't work. What I found in the debug log is this: 2013-06-06 13:32:55.122 DEBUG nova.openstack.common.rpc.amqp [req-fba2d928-0c8b-4584-815a-17779cd96e2e None None] Making synchronous call on conductor ... multicall /usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py:583 This call then times out after a while. The issue is that I disabled the conductor in nova.conf: ... [conductor] use_local=true ... I followed this page: http://cloudystuffhappens.blogspot.de/2013/04/understanding-nova-conductor-in.html So I'm not sure why vnc still tries to contact the conductor. Is the conductor service now a hard requirement for novncproxy? Regards, Dennis From pbrady at redhat.com Thu Jun 6 12:55:04 2013 From: pbrady at redhat.com (=?ISO-8859-1?Q?P=E1draig_Brady?=) Date: Thu, 06 Jun 2013 13:55:04 +0100 Subject: [Rdo-list] consoleauth package? In-Reply-To: <51B0785D.40600@conversis.de> References: <51AFD5BC.4070405@conversis.de> <51AFE5E6.6080100@redhat.com> <51B0785D.40600@conversis.de> Message-ID: <51B086A8.6040806@redhat.com> On 06/06/2013 12:54 PM, Dennis Jacobfeuerborn wrote: > On 06.06.2013 03:29, P?draig Brady wrote: >> On 06/06/2013 01:20 AM, Dennis Jacobfeuerborn wrote: >>> Hi, >>> I'm trying to get the console tab in horizon working but right now I only see "loading..." which times out after a while. According to the documentation novncproxy needs the consoleauth service and I found various pages on the web describing the installation of the openstack-nova-consoleauth rpm yet this doesn't seem to be available in the RDO repo. >>> Is this no longer required or is it now part of another package? >> >> $ repoquery --file /usr/bin/nova-consoleauth >> openstack-nova-console > > Ah, I wasn't paying attention to that package because the documentation describes nova-console as XenAPI specific and not to be confused with the separate nova-consoleauth. Thanks for the pointer. > > I now get the "shell" in the console tab but the vnc console itself doesn't work. What I found in the debug log is this: > > 2013-06-06 13:32:55.122 DEBUG nova.openstack.common.rpc.amqp [req-fba2d928-0c8b-4584-815a-17779cd96e2e None None] Making synchronous call on conductor ... multicall /usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py:583 > > This call then times out after a while. > > The issue is that I disabled the conductor in nova.conf: > ... > [conductor] > use_local=true > ... > > I followed this page: http://cloudystuffhappens.blogspot.de/2013/04/understanding-nova-conductor-in.html > > So I'm not sure why vnc still tries to contact the conductor. Is the conductor service now a hard requirement for novncproxy? What might be happening here is that we're using novncproxy from the "novnc" project rather than "nova", and things might have gotten a little out of sync. Nikola do you know about this specific case, or a way to quickly test the "nova" version of novncproxy? thanks, P?draig. From mail-lists at karan.org Sun Jun 9 14:29:04 2013 From: mail-lists at karan.org (Karanbir Singh) Date: Sun, 09 Jun 2013 15:29:04 +0100 Subject: [Rdo-list] [package announce] network namespace support In-Reply-To: <51A8811C.8090603@redhat.com> References: <51A8811C.8090603@redhat.com> Message-ID: <51B49130.4060001@karan.org> On 05/31/2013 11:53 AM, P?draig Brady wrote: > update: iputils-20071127-17.el6_4 > add: kernel-2.6.32-358.6.2.openstack.el6 are these going to be maintained inline with the distro packages ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From dneary at redhat.com Sun Jun 9 21:51:44 2013 From: dneary at redhat.com (Dave Neary) Date: Sun, 9 Jun 2013 17:51:44 -0400 (EDT) Subject: [Rdo-list] [package announce] network namespace support In-Reply-To: <51B49130.4060001@karan.org> References: <51A8811C.8090603@redhat.com> <51B49130.4060001@karan.org> Message-ID: <833778422.7981234.1370814704382.JavaMail.root@redhat.com> Hi, ----- Original Message ----- > On 05/31/2013 11:53 AM, P?draig Brady wrote: > > update: iputils-20071127-17.el6_4 > > add: kernel-2.6.32-358.6.2.openstack.el6 > > are these going to be maintained inline with the distro packages ? That's the plan. We do not want to deviate too far from the Red Hat Enterprise Linux kernel, but netns seemed important enough to make an exception. Cheers, Dave. From ndipanov at redhat.com Mon Jun 10 16:15:00 2013 From: ndipanov at redhat.com (=?UTF-8?B?Tmlrb2xhIMSQaXBhbm92?=) Date: Mon, 10 Jun 2013 18:15:00 +0200 Subject: [Rdo-list] consoleauth package? In-Reply-To: <51B086A8.6040806@redhat.com> References: <51AFD5BC.4070405@conversis.de> <51AFE5E6.6080100@redhat.com> <51B0785D.40600@conversis.de> <51B086A8.6040806@redhat.com> Message-ID: <51B5FB84.7000101@redhat.com> On 06/06/13 14:55, P?draig Brady wrote: > On 06/06/2013 12:54 PM, Dennis Jacobfeuerborn wrote: >> On 06.06.2013 03:29, P?draig Brady wrote: >>> On 06/06/2013 01:20 AM, Dennis Jacobfeuerborn wrote: >>>> Hi, >>>> I'm trying to get the console tab in horizon working but right now I only see "loading..." which times out after a while. According to the documentation novncproxy needs the consoleauth service and I found various pages on the web describing the installation of the openstack-nova-consoleauth rpm yet this doesn't seem to be available in the RDO repo. >>>> Is this no longer required or is it now part of another package? >>> >>> $ repoquery --file /usr/bin/nova-consoleauth >>> openstack-nova-console >> >> Ah, I wasn't paying attention to that package because the documentation describes nova-console as XenAPI specific and not to be confused with the separate nova-consoleauth. Thanks for the pointer. >> >> I now get the "shell" in the console tab but the vnc console itself doesn't work. What I found in the debug log is this: >> >> 2013-06-06 13:32:55.122 DEBUG nova.openstack.common.rpc.amqp [req-fba2d928-0c8b-4584-815a-17779cd96e2e None None] Making synchronous call on conductor ... multicall /usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py:583 >> >> This call then times out after a while. >> >> The issue is that I disabled the conductor in nova.conf: >> ... >> [conductor] >> use_local=true >> ... >> >> I followed this page: http://cloudystuffhappens.blogspot.de/2013/04/understanding-nova-conductor-in.html >> >> So I'm not sure why vnc still tries to contact the conductor. Is the conductor service now a hard requirement for novncproxy? > > What might be happening here is that we're using novncproxy from > the "novnc" project rather than "nova", and things might have > gotten a little out of sync. > > Nikola do you know about this specific case, > or a way to quickly test the "nova" version of novncproxy? > Hey, I took a look at the code - and the situation is like this: * We do ship a slightly outdated nova-novncproxy service that what is currently in the stable grizzly branch but the changes are purely cosmetic (moving code around, no functional changes). * Both versions will try to use rpc only to talk to the consoleauth service and *never* try to talk to the conductor, so I am pretty sure that the multicall in the logs is not from the openstack-nova-novncproxy service (it should log to /var/log/nova/novncproxy.log - maybe try checking there if you haven't been already). I would guess that some answers could be found in the log file mentioned above. Alternatively make sure that the nova-consoleauth service is up-and-running as novncproxy will need to check creds with it. Let me know if any of this helped. Thanks, Nikola > thanks, > P?draig. > From dennisml at conversis.de Tue Jun 11 11:38:06 2013 From: dennisml at conversis.de (Dennis Jacobfeuerborn) Date: Tue, 11 Jun 2013 13:38:06 +0200 Subject: [Rdo-list] consoleauth package? In-Reply-To: <51B5FB84.7000101@redhat.com> References: <51AFD5BC.4070405@conversis.de> <51AFE5E6.6080100@redhat.com> <51B0785D.40600@conversis.de> <51B086A8.6040806@redhat.com> <51B5FB84.7000101@redhat.com> Message-ID: <51B70C1E.7050007@conversis.de> On 10.06.2013 18:15, Nikola ?ipanov wrote: > On 06/06/13 14:55, P?draig Brady wrote: >> On 06/06/2013 12:54 PM, Dennis Jacobfeuerborn wrote: >>> On 06.06.2013 03:29, P?draig Brady wrote: >>>> On 06/06/2013 01:20 AM, Dennis Jacobfeuerborn wrote: >>>>> Hi, >>>>> I'm trying to get the console tab in horizon working but right now I only see "loading..." which times out after a while. According to the documentation novncproxy needs the consoleauth service and I found various pages on the web describing the installation of the openstack-nova-consoleauth rpm yet this doesn't seem to be available in the RDO repo. >>>>> Is this no longer required or is it now part of another package? >>>> >>>> $ repoquery --file /usr/bin/nova-consoleauth >>>> openstack-nova-console >>> >>> Ah, I wasn't paying attention to that package because the documentation describes nova-console as XenAPI specific and not to be confused with the separate nova-consoleauth. Thanks for the pointer. >>> >>> I now get the "shell" in the console tab but the vnc console itself doesn't work. What I found in the debug log is this: >>> >>> 2013-06-06 13:32:55.122 DEBUG nova.openstack.common.rpc.amqp [req-fba2d928-0c8b-4584-815a-17779cd96e2e None None] Making synchronous call on conductor ... multicall /usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py:583 >>> >>> This call then times out after a while. >>> >>> The issue is that I disabled the conductor in nova.conf: >>> ... >>> [conductor] >>> use_local=true >>> ... >>> >>> I followed this page: http://cloudystuffhappens.blogspot.de/2013/04/understanding-nova-conductor-in.html >>> >>> So I'm not sure why vnc still tries to contact the conductor. Is the conductor service now a hard requirement for novncproxy? >> >> What might be happening here is that we're using novncproxy from >> the "novnc" project rather than "nova", and things might have >> gotten a little out of sync. >> >> Nikola do you know about this specific case, >> or a way to quickly test the "nova" version of novncproxy? >> > > Hey, > > I took a look at the code - and the situation is like this: > > * We do ship a slightly outdated nova-novncproxy service that what is > currently in the stable grizzly branch but the changes are purely > cosmetic (moving code around, no functional changes). > > * Both versions will try to use rpc only to talk to the consoleauth > service and *never* try to talk to the conductor, so I am pretty sure > that the multicall in the logs is not from the openstack-nova-novncproxy > service (it should log to /var/log/nova/novncproxy.log - maybe try > checking there if you haven't been already). > > I would guess that some answers could be found in the log file mentioned > above. Alternatively make sure that the nova-consoleauth service is > up-and-running as novncproxy will need to check creds with it. > > Let me know if any of this helped. After bringing up nova-conductor (but keeping the "use_local=true" in place for the moment) the console started working (except that the keymap config doesn't seem to work and I get a "weird" key mapping). So the conductor service does indeed seem to be necessary for the console work. Does the vnc code maybe rely on something else that pulls in this dependency? Regards, Dennis From pbrady at redhat.com Tue Jun 11 13:00:17 2013 From: pbrady at redhat.com (=?ISO-8859-1?Q?P=E1draig_Brady?=) Date: Tue, 11 Jun 2013 14:00:17 +0100 Subject: [Rdo-list] [package announce] Stable Grizzly 2013.1.2 update Message-ID: <51B71F61.3090505@redhat.com> The RDO Grizzly repositories were updated with the latest stable 2013.1.2 update Details of the changes can be drilled down to from: https://launchpad.net/nova/grizzly/2013.1.2 https://launchpad.net/glance/grizzly/2013.1.2 https://launchpad.net/horizon/grizzly/2013.1.2 https://launchpad.net/keystone/grizzly/2013.1.2 https://launchpad.net/cinder/grizzly/2013.1.2 https://launchpad.net/quantum/grizzly/2013.1.2 https://launchpad.net/ceilometer/grizzly/2013.1.2 https://launchpad.net/heat/grizzly/2013.1.2 thanks, P?draig. From ndipanov at redhat.com Tue Jun 11 16:53:19 2013 From: ndipanov at redhat.com (=?UTF-8?B?Tmlrb2xhIMSQaXBhbm92?=) Date: Tue, 11 Jun 2013 18:53:19 +0200 Subject: [Rdo-list] consoleauth package? In-Reply-To: <51B70C1E.7050007@conversis.de> References: <51AFD5BC.4070405@conversis.de> <51AFE5E6.6080100@redhat.com> <51B0785D.40600@conversis.de> <51B086A8.6040806@redhat.com> <51B5FB84.7000101@redhat.com> <51B70C1E.7050007@conversis.de> Message-ID: <51B755FF.9040801@redhat.com> On 11/06/13 13:38, Dennis Jacobfeuerborn wrote: > On 10.06.2013 18:15, Nikola ?ipanov wrote: >> On 06/06/13 14:55, P?draig Brady wrote: >>> On 06/06/2013 12:54 PM, Dennis Jacobfeuerborn wrote: >>>> On 06.06.2013 03:29, P?draig Brady wrote: >>>>> On 06/06/2013 01:20 AM, Dennis Jacobfeuerborn wrote: >>>>>> Hi, >>>>>> I'm trying to get the console tab in horizon working but right now >>>>>> I only see "loading..." which times out after a while. According >>>>>> to the documentation novncproxy needs the consoleauth service and >>>>>> I found various pages on the web describing the installation of >>>>>> the openstack-nova-consoleauth rpm yet this doesn't seem to be >>>>>> available in the RDO repo. >>>>>> Is this no longer required or is it now part of another package? >>>>> >>>>> $ repoquery --file /usr/bin/nova-consoleauth >>>>> openstack-nova-console >>>> >>>> Ah, I wasn't paying attention to that package because the >>>> documentation describes nova-console as XenAPI specific and not to >>>> be confused with the separate nova-consoleauth. Thanks for the pointer. >>>> >>>> I now get the "shell" in the console tab but the vnc console itself >>>> doesn't work. What I found in the debug log is this: >>>> >>>> 2013-06-06 13:32:55.122 DEBUG nova.openstack.common.rpc.amqp >>>> [req-fba2d928-0c8b-4584-815a-17779cd96e2e None None] Making >>>> synchronous call on conductor ... multicall >>>> /usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py:583 >>>> >>>> This call then times out after a while. >>>> >>>> The issue is that I disabled the conductor in nova.conf: >>>> ... >>>> [conductor] >>>> use_local=true >>>> ... >>>> >>>> I followed this page: >>>> http://cloudystuffhappens.blogspot.de/2013/04/understanding-nova-conductor-in.html >>>> >>>> >>>> So I'm not sure why vnc still tries to contact the conductor. Is the >>>> conductor service now a hard requirement for novncproxy? >>> >>> What might be happening here is that we're using novncproxy from >>> the "novnc" project rather than "nova", and things might have >>> gotten a little out of sync. >>> >>> Nikola do you know about this specific case, >>> or a way to quickly test the "nova" version of novncproxy? >>> >> >> Hey, >> >> I took a look at the code - and the situation is like this: >> >> * We do ship a slightly outdated nova-novncproxy service that what is >> currently in the stable grizzly branch but the changes are purely >> cosmetic (moving code around, no functional changes). >> >> * Both versions will try to use rpc only to talk to the consoleauth >> service and *never* try to talk to the conductor, so I am pretty sure >> that the multicall in the logs is not from the openstack-nova-novncproxy >> service (it should log to /var/log/nova/novncproxy.log - maybe try >> checking there if you haven't been already). >> >> I would guess that some answers could be found in the log file mentioned >> above. Alternatively make sure that the nova-consoleauth service is >> up-and-running as novncproxy will need to check creds with it. >> >> Let me know if any of this helped. > > After bringing up nova-conductor (but keeping the "use_local=true" in > place for the moment) the console started working (except that the > keymap config doesn't seem to work and I get a "weird" key mapping). > So the conductor service does indeed seem to be necessary for the > console work. Does the vnc code maybe rely on something else that pulls > in this dependency? > As I suspected, I think you've hit a known bug. See https://bugs.launchpad.net/nova/+bug/1186123. You can apply the linked patch - and it will be in the next grizzly release we do by default. Thanks, N. > Regards, > Dennis > From pmyers at redhat.com Wed Jun 12 03:04:36 2013 From: pmyers at redhat.com (Perry Myers) Date: Tue, 11 Jun 2013 23:04:36 -0400 Subject: [Rdo-list] [rhos-list] I think I found something missing in iproute2 In-Reply-To: <51A21873.4080509@redhat.com> References: <518BD6F2.6090600@redhat.com> <20130509174502.GM4016@x200.localdomain> <20130509181644.GN4016@x200.localdomain> <15554A73-0676-406D-A66C-8277845025CB@gmail.com> <51A21873.4080509@redhat.com> Message-ID: <51B7E544.6080009@redhat.com> On 05/26/2013 10:13 AM, Perry Myers wrote: > Just so folks know... > > We're working to get a kernel out on RDO based on the latest RHEL 6.4.z > kernel that contains the netns functionality. > > Hopefully in the next week or two we should be able to put this on the > RDO repos. > > We are just working out the minimal patch set required to backport the > functionality from upstream into the RHEL 6 kernel line, and validating > that netns works well enough to satisfy the use cases that OpenStack > Networking needs it for. > > More info as we get it Sorry for the delayed notification here, but just to let folks know. We do have a kernel in the RDO repos right now, that is based on the same base kernel as RHEL 6.4.z 2.6.32-358.6.2 kernel. This kernel is basically 358.6.2 + netns patches, and should work well for using Quantum in RDO. http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/epel-6/kernel-2.6.32-358.6.2.openstack.el6.x86_64.rpm One note is that Red Hat has released to RHN the next 6.4.z update of the kernel (358.11.1), and we are working to get an updated netns enabled kernel based on this latest z-stream. An additional note is that this RDO kernel is specifically for the community. It is not a RHEL kernel and is not officially supported in any way. Installing this kernel on RHEL systems will impact the support of the baseOS and Red Hat support will need you to revert to a fully supported kernel in order to get support for any kernel issues you encounter. Cheers, Perry From msolberg at redhat.com Thu Jun 13 19:27:38 2013 From: msolberg at redhat.com (Michael Solberg) Date: Thu, 13 Jun 2013 15:27:38 -0400 Subject: [Rdo-list] Fwd: RDO with Red Hat IDM In-Reply-To: <51A8AAF9.5080305@redhat.com> References: <51A7C117.6060100@redhat.com> <51A7CB8F.7030501@redhat.com> <51A7E8FC.6070601@redhat.com> <51A8AAF9.5080305@redhat.com> Message-ID: <51BA1D2A.5050800@redhat.com> On 05/31/2013 09:51 AM, Michael Solberg wrote: > On 05/30/2013 08:04 PM, Adam Young wrote: >> On 05/30/2013 05:58 PM, Dave Neary wrote: >>> Hi Adam, >>> >>> Can you have a look at this post on rdo-list and see if you can figure >>> out what's going wrong, please? >>> >>> Thanks! >>> Dave. >>> >>> >>> >>> -------- Original Message -------- >>> Subject: [Rdo-list] RDO with Red Hat IDM >>> Date: Thu, 30 May 2013 17:13:59 -0400 >>> From: Michael Solberg >>> To: rdo-list at redhat.com >>> >>> Hi list. >>> >>> I've spent a day or two now trying to use Red Hat IDM as a backing store >>> for Keystone in RDO and I'm about to pull my hair out. >>> >>> I started with Adam Young's blog post here: >>> http://adam.younglogic.com/2012/02/freeipa-keystone-ldap/ >>> >>> Then I watched his Summit video here: >>> http://www.openstack.org/summit/portland-2013/session-videos/presentation/securing-openstack-with-freeipa >>> >>> >>> >>> Then I tried to follow this document: >>> http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-keystone-for-ldap-backend.html >>> >>> >>> >>> I definitely ran into the domain_id problem described here: >>> https://lists.launchpad.net/openstack/msg23387.html >>> >>> I also ran into the issue around the RFC 4519 schema not allowing a >>> "enabled" attribute. I think I've mitigated this by setting the >>> "attribute_ignore" settings in keystone.conf. >>> >>> I've tried tackling the architecture from a few different directions and >>> I've gotten to the point where I can create roles, create tenants, and >>> list users in my IDM domain, but not assign roles to users. I think >>> this is because I'm trying to separate out the tenants and roles from >>> the users in the directory tree. I don't mind keystone creating objects >>> in it's own tree, but I don't want it updating user accounts from IDM. >> >> So, you have put projects into their own subtree? Can the LDAP user >> from Keystone modify that tree? > > Yes - for right now, I'm just using the cn=Directory Manager account. I > figured I'd work on the ACLs once I got the mappings correct. All of my > issues so far have been around Keystone trying to create or read objects > in the tree that don't conform to the standard directory types that we > ship in IDM (groupOfNames, posixaccount, etc). That's why I was curious > if someone had a working configuration that I could look at. It looks > like we've documented using AD upstream, but not IDM. I figured it out. Is there a good place for me to document this? Thanks. Michael. From dneary at redhat.com Thu Jun 13 20:20:54 2013 From: dneary at redhat.com (Dave Neary) Date: Thu, 13 Jun 2013 16:20:54 -0400 Subject: [Rdo-list] Fwd: RDO with Red Hat IDM In-Reply-To: <51BA1D2A.5050800@redhat.com> References: <51A7C117.6060100@redhat.com> <51A7CB8F.7030501@redhat.com> <51A7E8FC.6070601@redhat.com> <51A8AAF9.5080305@redhat.com> <51BA1D2A.5050800@redhat.com> Message-ID: <51BA29A6.6010005@redhat.com> Hi, Yes! Please create a page in the wiki and link to it from http://openstack.redhat.com/Troubleshooting please. Thanks! Dave. On 06/13/2013 03:27 PM, Michael Solberg wrote: > On 05/31/2013 09:51 AM, Michael Solberg wrote: >> On 05/30/2013 08:04 PM, Adam Young wrote: >>> On 05/30/2013 05:58 PM, Dave Neary wrote: >>>> Hi Adam, >>>> >>>> Can you have a look at this post on rdo-list and see if you can figure >>>> out what's going wrong, please? >>>> >>>> Thanks! >>>> Dave. >>>> >>>> >>>> >>>> -------- Original Message -------- >>>> Subject: [Rdo-list] RDO with Red Hat IDM >>>> Date: Thu, 30 May 2013 17:13:59 -0400 >>>> From: Michael Solberg >>>> To: rdo-list at redhat.com >>>> >>>> Hi list. >>>> >>>> I've spent a day or two now trying to use Red Hat IDM as a backing >>>> store >>>> for Keystone in RDO and I'm about to pull my hair out. >>>> >>>> I started with Adam Young's blog post here: >>>> http://adam.younglogic.com/2012/02/freeipa-keystone-ldap/ >>>> >>>> Then I watched his Summit video here: >>>> http://www.openstack.org/summit/portland-2013/session-videos/presentation/securing-openstack-with-freeipa >>>> >>>> >>>> >>>> >>>> Then I tried to follow this document: >>>> http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-keystone-for-ldap-backend.html >>>> >>>> >>>> >>>> >>>> I definitely ran into the domain_id problem described here: >>>> https://lists.launchpad.net/openstack/msg23387.html >>>> >>>> I also ran into the issue around the RFC 4519 schema not allowing a >>>> "enabled" attribute. I think I've mitigated this by setting the >>>> "attribute_ignore" settings in keystone.conf. >>>> >>>> I've tried tackling the architecture from a few different directions >>>> and >>>> I've gotten to the point where I can create roles, create tenants, and >>>> list users in my IDM domain, but not assign roles to users. I think >>>> this is because I'm trying to separate out the tenants and roles from >>>> the users in the directory tree. I don't mind keystone creating >>>> objects >>>> in it's own tree, but I don't want it updating user accounts from IDM. >>> >>> So, you have put projects into their own subtree? Can the LDAP user >>> from Keystone modify that tree? >> >> Yes - for right now, I'm just using the cn=Directory Manager account. I >> figured I'd work on the ACLs once I got the mappings correct. All of my >> issues so far have been around Keystone trying to create or read objects >> in the tree that don't conform to the standard directory types that we >> ship in IDM (groupOfNames, posixaccount, etc). That's why I was curious >> if someone had a working configuration that I could look at. It looks >> like we've documented using AD upstream, but not IDM. > > I figured it out. Is there a good place for me to document this? > > Thanks. > > Michael. > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From msolberg at redhat.com Fri Jun 14 02:57:12 2013 From: msolberg at redhat.com (Michael Solberg) Date: Thu, 13 Jun 2013 22:57:12 -0400 Subject: [Rdo-list] Fwd: RDO with Red Hat IDM In-Reply-To: <51BA29A6.6010005@redhat.com> References: <51A7C117.6060100@redhat.com> <51A7CB8F.7030501@redhat.com> <51A7E8FC.6070601@redhat.com> <51A8AAF9.5080305@redhat.com> <51BA1D2A.5050800@redhat.com> <51BA29A6.6010005@redhat.com> Message-ID: <51BA8688.2020607@redhat.com> On 06/13/2013 04:20 PM, Dave Neary wrote: > Hi, > > Yes! Please create a page in the wiki and link to it from > http://openstack.redhat.com/Troubleshooting please. It could probably use some editing, but it's a start: http://openstack.redhat.com/KeystoneIDMIntegration It'd be nice to go into how to set up SSL and PKI for the various services. Michael. From dneary at redhat.com Fri Jun 14 18:40:57 2013 From: dneary at redhat.com (Dave Neary) Date: Fri, 14 Jun 2013 14:40:57 -0400 Subject: [Rdo-list] Fwd: RDO with Red Hat IDM In-Reply-To: <51BA8688.2020607@redhat.com> References: <51A7C117.6060100@redhat.com> <51A7CB8F.7030501@redhat.com> <51A7E8FC.6070601@redhat.com> <51A8AAF9.5080305@redhat.com> <51BA1D2A.5050800@redhat.com> <51BA29A6.6010005@redhat.com> <51BA8688.2020607@redhat.com> Message-ID: <51BB63B9.7040800@redhat.com> Hi Michael, How is IDM integration different from FreeIPA integrations? Thanks! Dave. On 06/13/2013 10:57 PM, Michael Solberg wrote: > On 06/13/2013 04:20 PM, Dave Neary wrote: >> Hi, >> >> Yes! Please create a page in the wiki and link to it from >> http://openstack.redhat.com/Troubleshooting please. > > It could probably use some editing, but it's a start: > > http://openstack.redhat.com/KeystoneIDMIntegration > > It'd be nice to go into how to set up SSL and PKI for the various services. > > Michael. > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From msolberg at redhat.com Fri Jun 14 22:23:32 2013 From: msolberg at redhat.com (Michael Solberg) Date: Fri, 14 Jun 2013 18:23:32 -0400 Subject: [Rdo-list] Fwd: RDO with Red Hat IDM In-Reply-To: <51BB63B9.7040800@redhat.com> References: <51A7C117.6060100@redhat.com> <51A7CB8F.7030501@redhat.com> <51A7E8FC.6070601@redhat.com> <51A8AAF9.5080305@redhat.com> <51BA1D2A.5050800@redhat.com> <51BA29A6.6010005@redhat.com> <51BA8688.2020607@redhat.com> <51BB63B9.7040800@redhat.com> Message-ID: <51BB97E4.7000200@redhat.com> On 06/14/2013 02:40 PM, Dave Neary wrote: > Hi Michael, > > How is IDM integration different from FreeIPA integrations? I don't have a lot of experience with FreeIPA, but I'd imagine that they're very similar - perhaps identical, depending on how far IdM lags upstream. Michael. > On 06/13/2013 10:57 PM, Michael Solberg wrote: >> On 06/13/2013 04:20 PM, Dave Neary wrote: >>> Hi, >>> >>> Yes! Please create a page in the wiki and link to it from >>> http://openstack.redhat.com/Troubleshooting please. >> >> It could probably use some editing, but it's a start: >> >> http://openstack.redhat.com/KeystoneIDMIntegration >> >> It'd be nice to go into how to set up SSL and PKI for the various services. >> >> Michael. >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list > From sgordon at redhat.com Fri Jun 14 22:29:21 2013 From: sgordon at redhat.com (Steve Gordon) Date: Fri, 14 Jun 2013 18:29:21 -0400 (EDT) Subject: [Rdo-list] Missing python-httplib2 package in RDO? In-Reply-To: <222642686.19757770.1371248943653.JavaMail.root@redhat.com> Message-ID: <640540472.19757774.1371248961090.JavaMail.root@redhat.com> I've just raised a bug [1] for this but wanting to highlight it and confirm that python-httplib2 should be in the RDO repository? Thanks, Steve [1] https://bugzilla.redhat.com/show_bug.cgi?id=974710 From sgordon at redhat.com Fri Jun 14 22:41:09 2013 From: sgordon at redhat.com (Steve Gordon) Date: Fri, 14 Jun 2013 18:41:09 -0400 (EDT) Subject: [Rdo-list] Missing python-httplib2 package in RDO? In-Reply-To: <640540472.19757774.1371248961090.JavaMail.root@redhat.com> References: <640540472.19757774.1371248961090.JavaMail.root@redhat.com> Message-ID: <2112776536.19759399.1371249669459.JavaMail.root@redhat.com> OK seems it is in EPEL6: http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/python-httplib2.html Is it expected that EPEL be enabled? Currently it isn't if you follow the Quick Start (and I don't remember it being required previously?). Thanks, Steve ----- Original Message ----- > From: "Steve Gordon" > To: rdo-list at redhat.com > Sent: Friday, June 14, 2013 6:29:21 PM > Subject: [Rdo-list] Missing python-httplib2 package in RDO? > > I've just raised a bug [1] for this but wanting to highlight it and confirm > that python-httplib2 should be in the RDO repository? > > Thanks, > > Steve > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=974710 > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -- Steve Gordon, RHCE Documentation Lead, Red Hat OpenStack Engineering Content Services Red Hat Canada (Toronto, Ontario) From dneary at redhat.com Fri Jun 14 23:27:23 2013 From: dneary at redhat.com (Dave Neary) Date: Fri, 14 Jun 2013 19:27:23 -0400 Subject: [Rdo-list] Missing python-httplib2 package in RDO? In-Reply-To: <2112776536.19759399.1371249669459.JavaMail.root@redhat.com> References: <640540472.19757774.1371248961090.JavaMail.root@redhat.com> <2112776536.19759399.1371249669459.JavaMail.root@redhat.com> Message-ID: <51BBA6DB.1000505@redhat.com> Hi, Yes, EPEL is required. It was in the initial install instructions, and I seem to recall a discussion about how installing the repo file enabled EPEL. P?draig, am I mis-remembering? Thanks, Dave. On 06/14/2013 06:41 PM, Steve Gordon wrote: > OK seems it is in EPEL6: > > http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/python-httplib2.html > > Is it expected that EPEL be enabled? Currently it isn't if you follow the Quick Start (and I don't remember it being required previously?). > > Thanks, > > Steve > > ----- Original Message ----- >> From: "Steve Gordon" >> To: rdo-list at redhat.com >> Sent: Friday, June 14, 2013 6:29:21 PM >> Subject: [Rdo-list] Missing python-httplib2 package in RDO? >> >> I've just raised a bug [1] for this but wanting to highlight it and confirm >> that python-httplib2 should be in the RDO repository? >> >> Thanks, >> >> Steve >> >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=974710 >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> > -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From sgordon at redhat.com Sat Jun 15 12:53:38 2013 From: sgordon at redhat.com (Steve Gordon) Date: Sat, 15 Jun 2013 08:53:38 -0400 (EDT) Subject: [Rdo-list] Missing python-httplib2 package in RDO? In-Reply-To: <51BBA6DB.1000505@redhat.com> References: <640540472.19757774.1371248961090.JavaMail.root@redhat.com> <2112776536.19759399.1371249669459.JavaMail.root@redhat.com> <51BBA6DB.1000505@redhat.com> Message-ID: <1244518214.19805188.1371300818876.JavaMail.root@redhat.com> ----- Original Message ----- > From: "Dave Neary" > To: "Steve Gordon" > Cc: rdo-list at redhat.com > Sent: Friday, June 14, 2013 7:27:23 PM > Subject: Re: [Rdo-list] Missing python-httplib2 package in RDO? > > Hi, > > Yes, EPEL is required. It was in the initial install instructions, and I > seem to recall a discussion about how installing the repo file enabled EPEL. > > P?draig, am I mis-remembering? > > Thanks, > Dave. As Alan alluded to on the bug packstack should, and probably is, enabling EPEL by default on EL6-based distributions (will do a run later today to confirm hopefully). I suspect the user in question had installed the RDO release RPM and was following the manual installation path, we probably need a note somewhere to highlight that EPEL is assumed/required in this case? Thanks, Steve From fdc at fcami.net Sat Jun 15 14:31:57 2013 From: fdc at fcami.net (=?UTF-8?B?IkZyYW7Dp29pcyBDYW1pIg==?=) Date: Sat, 15 Jun 2013 16:31:57 +0200 Subject: [Rdo-list] Missing python-httplib2 package in RDO? In-Reply-To: <1244518214.19805188.1371300818876.JavaMail.root@redhat.com> References: <640540472.19757774.1371248961090.JavaMail.root@redhat.com> <2112776536.19759399.1371249669459.JavaMail.root@redhat.com> <51BBA6DB.1000505@redhat.com> <1244518214.19805188.1371300818876.JavaMail.root@redhat.com> Message-ID: On Sat, Jun 15, 2013 at 2:53 PM, Steve Gordon wrote: > ----- Original Message ----- >> From: "Dave Neary" >> To: "Steve Gordon" >> Cc: rdo-list at redhat.com >> Sent: Friday, June 14, 2013 7:27:23 PM >> Subject: Re: [Rdo-list] Missing python-httplib2 package in RDO? >> >> Hi, >> >> Yes, EPEL is required. It was in the initial install instructions, and I >> seem to recall a discussion about how installing the repo file enabled EPEL. >> >> P?draig, am I mis-remembering? >> >> Thanks, >> Dave. > > As Alan alluded to on the bug packstack should, and probably is, enabling EPEL by default on EL6-based distributions (will do a run later today to confirm hopefully). I suspect the user in question had installed the RDO release RPM and was following the manual installation path, we probably need a note somewhere to highlight that EPEL is assumed/required in this case? What about adding Requires: epel-release to rdo-release.spec? We could even put the epel-release rpm in the rdo repository to make things simpler. Cheers Fran?ois From SVerma at yamaha-motor-india.com Mon Jun 17 08:14:15 2013 From: SVerma at yamaha-motor-india.com (Shilpi Verma) Date: Mon, 17 Jun 2013 13:44:15 +0530 Subject: [Rdo-list] problem in openstack installation Message-ID: Hello, I am trying to install openstack tool in CentOS 6.4. Step 1: Software repositories Run the following command: sudo yum install -y http://rdo.fedorapeople.org/openstack/openstack-grizzly/rdo-release-grizzly.rpm Step 2: Install Packstack Installer sudo yum install -y openstack-packstack Step 3: Run Packstack to install OpenStack Packstack takes the work out of manually setting up OpenStack.For a single node OpenStack deployment, run the following command. packstack --allinone In the 3rd step I am facing the following error.I am sending the output of command: packstack --allinone -bash-4.1# packstack --allinone Installing: Clean Up... [ DONE ] Adding pre install manifest entries... [ DONE ] Installing time synchronization via NTP... [ DONE ] Setting up ssh keys... [ DONE ] Adding MySQL manifest entries... [ DONE ] Adding QPID 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 ] Installing dependencies for Cinder... [ DONE ] Checking if the Cinder server has a cinder-volumes vg... [ DONE ] Adding Cinder manifest entries... [ DONE ] Adding Nova API manifest entries... [ DONE ] Adding Nova Keystone manifest entries... [ DONE ] Adding Nova Cert manifest entries... [ DONE ] Adding Nova Compute manifest entries... [ DONE ] Adding Nova Network manifest entries... [ DONE ] Adding Nova Scheduler manifest entries... [ DONE ] Adding Nova VNC Proxy manifest entries... [ DONE ] Adding Nova Common manifest entries... [ DONE ] Adding OpenStack Client manifest entries... [ DONE ] Adding Horizon manifest entries... [ DONE ] Preparing servers... [ DONE ] Adding post install manifest entries... [ DONE ] Installing Dependencies... [ DONE ] Copying Puppet modules and manifests... [ DONE ] Applying Puppet manifests... Applying 14.98.122.82_prescript.pp 14.98.122.82_prescript.pp : [ DONE ] Applying 14.98.122.82_ntpd.pp 14.98.122.82_ntpd.pp : [ DONE ] Applying 14.98.122.82_mysql.pp Applying 14.98.122.82_qpid.pp 14.98.122.82_mysql.pp : [ DONE ] 14.98.122.82_qpid.pp : [ DONE ] Applying 14.98.122.82_keystone.pp Applying 14.98.122.82_glance.pp Applying 14.98.122.82_cinder.pp ERROR : Error during puppet run : err: /Stage[main]/Keystone/Package [keystone]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install openstack-keystone' returned 1: Error: Nothing to do Please check log file /var/tmp/packstack/20130617-123123-MQM3JN/openstack-setup.log for more information Additional information: * A new answerfile was created in: /root/packstack-answers-20130617-123243.txt * To use the command line tools you need to source the file /root/keystonerc_admin created on 14.98.122.82 * To use the console, browse to http://14.98.122.82/dashboard Warm Regards, Shilpi Verma From pbrady at redhat.com Mon Jun 17 09:48:16 2013 From: pbrady at redhat.com (=?UTF-8?B?UMOhZHJhaWcgQnJhZHk=?=) Date: Mon, 17 Jun 2013 10:48:16 +0100 Subject: [Rdo-list] Missing python-httplib2 package in RDO? In-Reply-To: References: <640540472.19757774.1371248961090.JavaMail.root@redhat.com> <2112776536.19759399.1371249669459.JavaMail.root@redhat.com> <51BBA6DB.1000505@redhat.com> <1244518214.19805188.1371300818876.JavaMail.root@redhat.com> Message-ID: <51BEDB60.3050200@redhat.com> On 06/15/2013 03:31 PM, "Fran?ois Cami" wrote: > On Sat, Jun 15, 2013 at 2:53 PM, Steve Gordon wrote: >> ----- Original Message ----- >>> From: "Dave Neary" >>> To: "Steve Gordon" >>> Cc: rdo-list at redhat.com >>> Sent: Friday, June 14, 2013 7:27:23 PM >>> Subject: Re: [Rdo-list] Missing python-httplib2 package in RDO? >>> >>> Hi, >>> >>> Yes, EPEL is required. It was in the initial install instructions, and I >>> seem to recall a discussion about how installing the repo file enabled EPEL. >>> >>> P?draig, am I mis-remembering? >>> >>> Thanks, >>> Dave. >> >> As Alan alluded to on the bug packstack should, and probably is, enabling EPEL by default on EL6-based distributions (will do a run later today to confirm hopefully). I suspect the user in question had installed the RDO release RPM and was following the manual installation path, we probably need a note somewhere to highlight that EPEL is assumed/required in this case? yes > What about adding > Requires: epel-release > to rdo-release.spec? > > We could even put the epel-release rpm in the rdo repository to make > things simpler. Though a little less flexible. packstack is used to manage this dependency at a higher level, allowing the RDO repo to be used without EPEL if desired. Though that's not the common case. Also the edge case of avoiding EPEL is handled with yum --disablerepo=epel ... So this is a good suggestion and would avoid docs. However this may involve a little packstack work to handle an EPEL repo that was now installed by default. I've logged https://bugzilla.redhat.com/974971 to discuss that. thanks, P?draig. From pmyers at redhat.com Mon Jun 17 12:49:53 2013 From: pmyers at redhat.com (Perry Myers) Date: Mon, 17 Jun 2013 08:49:53 -0400 Subject: [Rdo-list] problem in openstack installation In-Reply-To: References: Message-ID: <51BF05F1.3050805@redhat.com> On 06/17/2013 04:14 AM, Shilpi Verma wrote: > > Hello, > > I am trying to install openstack tool in CentOS 6.4. > ERROR : Error during puppet run : err: /Stage[main]/Keystone/Package > [keystone]/ensure: change from absent to present failed: Execution of > '/usr/bin/yum -d 0 -e 0 -y install openstack-keystone' returned 1: Error: > Nothing to do > Please check log > file /var/tmp/packstack/20130617-123123-MQM3JN/openstack-setup.log for more > information Providing this log, or at least a snippet from it with the actual error would help. Thanks, Perry From dneary at redhat.com Mon Jun 17 13:32:38 2013 From: dneary at redhat.com (Dave Neary) Date: Mon, 17 Jun 2013 15:32:38 +0200 Subject: [Rdo-list] Suggestion: Notify this list of new forum threads Message-ID: <51BF0FF6.6060506@redhat.com> Hi, A number of people have suggested that it would be a good idea to have notifications sent by the forum to the rdo-list mailing list when new forum discussions are started. Is this something that list members would be OK with? There would be no way to reply to these messages, you would have to go to the forum to add a comment - but it would address the issue of forum threads going unnoticed by list subscribers. Thanks, Dave. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From pmyers at redhat.com Mon Jun 17 13:58:57 2013 From: pmyers at redhat.com (Perry Myers) Date: Mon, 17 Jun 2013 09:58:57 -0400 Subject: [Rdo-list] Suggestion: Notify this list of new forum threads In-Reply-To: <51BF0FF6.6060506@redhat.com> References: <51BF0FF6.6060506@redhat.com> Message-ID: <51BF1621.6030504@redhat.com> On 06/17/2013 09:32 AM, Dave Neary wrote: > Hi, > > A number of people have suggested that it would be a good idea to have > notifications sent by the forum to the rdo-list mailing list when new > forum discussions are started. > > Is this something that list members would be OK with? There would be no > way to reply to these messages, you would have to go to the forum to add > a comment - but it would address the issue of forum threads going > unnoticed by list subscribers. +1 from me We could reply and discuss the message on list, but it just means that in order to update the thread on forum, it would require manually doing so. But that might not be a bad mode of operation anyhow... * forum post question * email sent to rdo-list * some discussion and back/forth on list * resolution/answer posted to the forum (maybe with a link to the discussion details in rdo-list archives) Perry From kchamart at redhat.com Tue Jun 18 04:35:32 2013 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Tue, 18 Jun 2013 10:05:32 +0530 Subject: [Rdo-list] Suggestion: Notify this list of new forum threads In-Reply-To: <51BF1621.6030504@redhat.com> References: <51BF0FF6.6060506@redhat.com> <51BF1621.6030504@redhat.com> Message-ID: <51BFE394.4020102@redhat.com> On 06/17/2013 07:28 PM, Perry Myers wrote: > On 06/17/2013 09:32 AM, Dave Neary wrote: >> Hi, >> >> A number of people have suggested that it would be a good idea to have >> notifications sent by the forum to the rdo-list mailing list when new >> forum discussions are started. >> >> Is this something that list members would be OK with? Yes, please, it'd avoid a bit of less 'switching' around. >> There would be no >> way to reply to these messages, you would have to go to the forum to add >> a comment - but it would address the issue of forum threads going >> unnoticed by list subscribers. > > +1 from me > > We could reply and discuss the message on list, but it just means that > in order to update the thread on forum, it would require manually doing so. > > But that might not be a bad mode of operation anyhow... > > * forum post question > * email sent to rdo-list > * some discussion and back/forth on list > * resolution/answer posted to the forum (maybe with a link to the > discussion details in rdo-list archives) The above sounds pretty good till we figure a way to reply to those messages ( I don't know how hard it is, just wishful thinking from me). Thanks for bringing this up. -- /kashyap From oblaut at redhat.com Tue Jun 18 05:35:55 2013 From: oblaut at redhat.com (Ofer Blaut) Date: Tue, 18 Jun 2013 01:35:55 -0400 (EDT) Subject: [Rdo-list] Quantum and lack of connections In-Reply-To: <1149153613.95740.1371533613597.JavaMail.root@redhat.com> Message-ID: <1381169160.95951.1371533755325.JavaMail.root@redhat.com> Hi I wonder how can i configure quantum network /subnets/ports when L3/DHCP fails to connect to quantum server. I expect that user will have CLI/API errors upon DHCP not connected , and new IPs will not be allocated See errors attached http://paste.openstack.org/show/38836/ Ofer From kchamart at redhat.com Tue Jun 18 05:52:51 2013 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Tue, 18 Jun 2013 11:22:51 +0530 Subject: [Rdo-list] [For testing] Fedora 19 (Test Compose) cloud images Message-ID: <51BFF5B3.80305@redhat.com> Heya, Fedora release-engineering prepared a cloud-consumable image of F19 Test Compose 5, https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/ Get it: $ wget -c https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/Fedora-x86_64-19-TC5-20130617-sda.qcow2 Import it into your Glance service: $ glance image-create --name fedora19-tc5 --is-public true \ --disk-format qcow2 --container-format bare \ < Fedora-x86_64-19-TC5-20130617-sda.qcow2 Add a key pair (if you already have one, disregard this step): $ nova keypair-add testkey1 > testkey1.priv $ chmod 600 testkey1.priv Launch a guest: $ nova boot --flavor 2 --key_name oskey1 --image \ $UUID fedora19-test1 And all the further testing you prefer.. Please report any problems here. Happy testing. PS: Fedora-19 releases around 1st week of July. -- /kashyap From gkotton at redhat.com Tue Jun 18 05:58:05 2013 From: gkotton at redhat.com (Gary Kotton) Date: Tue, 18 Jun 2013 08:58:05 +0300 Subject: [Rdo-list] Quantum and lack of connections In-Reply-To: <1381169160.95951.1371533755325.JavaMail.root@redhat.com> References: <1381169160.95951.1371533755325.JavaMail.root@redhat.com> Message-ID: <51BFF6ED.703@redhat.com> On 06/18/2013 08:35 AM, Ofer Blaut wrote: > Hi > > I wonder how can i configure quantum network /subnets/ports when L3/DHCP fails to connect to quantum server. These are not related. The Quantum service enables the user to configure the network configuration. The DHCP agent provides the IPAM implementation and the L3 agent provides the floating IP and routing support. > > I expect that user will have CLI/API errors upon DHCP not connected , and new IPs will not be allocated Yes, it would be nice if the user was able to know if there was a problem, but it is not related at all to the Quantum API. In actual fact the administrator is able to invoke the command: "quantum agent-list" to determine if there are any issues with the backiend implementation of the Quantum API's. The administrator would in turn need to address the issues. > > See errors attached http://paste.openstack.org/show/38836/ From the traces it looks like the l3 agent has successfully connected to the message broker. The DHCP agent is unable to connect to the message broker. This may be during the boot process where it may take up to a minute (this is due to the qpid timeouts) > > Ofer > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list From oblaut at redhat.com Tue Jun 18 06:02:39 2013 From: oblaut at redhat.com (Ofer Blaut) Date: Tue, 18 Jun 2013 02:02:39 -0400 (EDT) Subject: [Rdo-list] Quantum and lack of connections In-Reply-To: <51BFF6ED.703@redhat.com> References: <1381169160.95951.1371533755325.JavaMail.root@redhat.com> <51BFF6ED.703@redhat.com> Message-ID: <963474632.99489.1371535359323.JavaMail.root@redhat.com> ----- Original Message ----- > From: "Gary Kotton" > To: "Ofer Blaut" > Cc: rdo-list at redhat.com > Sent: Tuesday, June 18, 2013 8:58:05 AM > Subject: Re: [Rdo-list] Quantum and lack of connections > > On 06/18/2013 08:35 AM, Ofer Blaut wrote: > > Hi > > > > I wonder how can i configure quantum network /subnets/ports when L3/DHCP > > fails to connect to quantum server. > > These are not related. The Quantum service enables the user to configure > the network configuration. The DHCP agent provides the IPAM > implementation and the L3 agent provides the floating IP and routing > support. > > > > > I expect that user will have CLI/API errors upon DHCP not connected , and > > new IPs will not be allocated > > Yes, it would be nice if the user was able to know if there was a > problem, but it is not related at all to the Quantum API. In actual fact > the administrator is able to invoke the command: "quantum agent-list" to > determine if there are any issues with the backiend implementation of > the Quantum API's. The administrator would in turn need to address the > issues. I don't expect user to check quantum agent-list all the time. In case DHCP/L3 fails , i think new commands should alert about it Can it be DHCP will miss it info about restart ? Ofer > > > > > See errors attached http://paste.openstack.org/show/38836/ > > From the traces it looks like the l3 agent has successfully connected > to the message broker. The DHCP agent is unable to connect to the > message broker. This may be during the boot process where it may take up > to a minute (this is due to the qpid timeouts) > > > > > Ofer > > > > _______________________________________________ > > Rdo-list mailing list > > Rdo-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rdo-list > > From gkotton at redhat.com Tue Jun 18 06:11:57 2013 From: gkotton at redhat.com (Gary Kotton) Date: Tue, 18 Jun 2013 09:11:57 +0300 Subject: [Rdo-list] Quantum and lack of connections In-Reply-To: <963474632.99489.1371535359323.JavaMail.root@redhat.com> References: <1381169160.95951.1371533755325.JavaMail.root@redhat.com> <51BFF6ED.703@redhat.com> <963474632.99489.1371535359323.JavaMail.root@redhat.com> Message-ID: <51BFFA2D.8030303@redhat.com> On 06/18/2013 09:02 AM, Ofer Blaut wrote: > > ----- Original Message ----- >> From: "Gary Kotton" >> To: "Ofer Blaut" >> Cc: rdo-list at redhat.com >> Sent: Tuesday, June 18, 2013 8:58:05 AM >> Subject: Re: [Rdo-list] Quantum and lack of connections >> >> On 06/18/2013 08:35 AM, Ofer Blaut wrote: >>> Hi >>> >>> I wonder how can i configure quantum network /subnets/ports when L3/DHCP >>> fails to connect to quantum server. >> These are not related. The Quantum service enables the user to configure >> the network configuration. The DHCP agent provides the IPAM >> implementation and the L3 agent provides the floating IP and routing >> support. >> >>> I expect that user will have CLI/API errors upon DHCP not connected , and >>> new IPs will not be allocated >> Yes, it would be nice if the user was able to know if there was a >> problem, but it is not related at all to the Quantum API. In actual fact >> the administrator is able to invoke the command: "quantum agent-list" to >> determine if there are any issues with the backiend implementation of >> the Quantum API's. The administrator would in turn need to address the >> issues. > I don't expect user to check quantum agent-list all the time. > In case DHCP/L3 fails , i think new commands should alert about it > Can it be DHCP will miss it info about restart ? Please differentiate between a user and an administrator. The user will be able to configure ports, subnets and networks. The administrator is responsible to ensure that the service is up and running. Anyone who will be running a cloud service will need to ensure that they have highly available and redundant dhcp and l3 agents. The way of monitoring this is via the aforementioned command. You are welcome to check out http://docs.openstack.org/trunk/openstack-network/admin/content/ch_high_avail.html > > Ofer > > >>> See errors attached http://paste.openstack.org/show/38836/ >> From the traces it looks like the l3 agent has successfully connected >> to the message broker. The DHCP agent is unable to connect to the >> message broker. This may be during the boot process where it may take up >> to a minute (this is due to the qpid timeouts) >> >>> Ofer >>> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >> From red at fedoraproject.org Tue Jun 18 06:12:42 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Tue, 18 Jun 2013 08:12:42 +0200 Subject: [Rdo-list] [For testing] Fedora 19 (Test Compose) cloud images In-Reply-To: <51BFF5B3.80305@redhat.com> References: <51BFF5B3.80305@redhat.com> Message-ID: On Tue, Jun 18, 2013 at 7:52 AM, Kashyap Chamarthy wrote: > Heya, > > Fedora release-engineering prepared a cloud-consumable image of F19 Test > Compose 5, > > https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/ Nice! Do we know what kickstart file and what version of it they are compiled with? > > > Get it: > > $ wget -c > > https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/Fedora-x86_64-19-TC5-20130617-sda.qcow2 > > > Import it into your Glance service: > > $ glance image-create --name fedora19-tc5 --is-public true \ > --disk-format qcow2 --container-format bare \ > < Fedora-x86_64-19-TC5-20130617-sda.qcow2 > FWIW, the above two steps can also be combined into one: $ glance image-create --name fedora19-tc5 --is-public true \ --disk-format qcow2 --container-format bare --copy-from \ https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/Fedora-x86_64-19-TC5-20130617-sda.qcow2 ...the downside being that you can't verify the checksum between downloading the image and pushing it into glance. > > Add a key pair (if you already have one, disregard this step): > > $ nova keypair-add testkey1 > testkey1.priv > $ chmod 600 testkey1.priv > > > Launch a guest: > > $ nova boot --flavor 2 --key_name oskey1 --image \ > $UUID fedora19-test1 > > > And all the further testing you prefer.. > > Please report any problems here. > > Happy testing. > > PS: Fedora-19 releases around 1st week of July. > > -- > /kashyap > > _______________________________________________ > 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 dneary at redhat.com Tue Jun 18 08:10:13 2013 From: dneary at redhat.com (Dave Neary) Date: Tue, 18 Jun 2013 10:10:13 +0200 Subject: [Rdo-list] Suggestion: Notify this list of new forum threads In-Reply-To: <51BF1621.6030504@redhat.com> References: <51BF0FF6.6060506@redhat.com> <51BF1621.6030504@redhat.com> Message-ID: <51C015E5.9090101@redhat.com> Hi, On 06/17/2013 03:58 PM, Perry Myers wrote: > We could reply and discuss the message on list, but it just means that > in order to update the thread on forum, it would require manually doing so. I think I'd prefer to see discussion happen on the forum rather than have it split across two places - of course if people reply here that's up to them, but I'd like to see the forum take priority. Cheers, Dave. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From kchamart at redhat.com Tue Jun 18 08:23:05 2013 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Tue, 18 Jun 2013 13:53:05 +0530 Subject: [Rdo-list] [For testing] Fedora 19 (Test Compose) cloud images In-Reply-To: References: <51BFF5B3.80305@redhat.com> Message-ID: <51C018E9.5030109@redhat.com> On 06/18/2013 11:42 AM, Sandro "red" Mathys wrote: > On Tue, Jun 18, 2013 at 7:52 AM, Kashyap Chamarthy wrote: > >> Heya, >> >> Fedora release-engineering prepared a cloud-consumable image of F19 Test >> Compose 5, >> >> https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/ > > > Nice! Do we know what kickstart file and what version of it they are > compiled with? Not sure. But yes - the above directory should also contain its kickstart file it's created with. It should mostly be this: https://git.fedorahosted.org/cgit/cloud-kickstarts.git/tree/generic/fedora-19-x86_64-cloud.ks Dennis Gilmore/Matthew Miller might confirm(CC'ed them). [...] > > FWIW, the above two steps can also be combined into one: > > $ glance image-create --name fedora19-tc5 --is-public true \ > --disk-format qcow2 --container-format bare --copy-from \ > > https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/Fedora-x86_64-19-TC5-20130617-sda.qcow2 > > ...the downside being that you can't verify the checksum between > downloading the image and pushing it into glance. Nice, thank you. -- /kashyap From red at fedoraproject.org Tue Jun 18 09:44:14 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Tue, 18 Jun 2013 11:44:14 +0200 Subject: [Rdo-list] [For testing] Fedora 19 (Test Compose) cloud images In-Reply-To: <51C018E9.5030109@redhat.com> References: <51BFF5B3.80305@redhat.com> <51C018E9.5030109@redhat.com> Message-ID: On Tue, Jun 18, 2013 at 10:23 AM, Kashyap Chamarthy wrote: > On 06/18/2013 11:42 AM, Sandro "red" Mathys wrote: > > On Tue, Jun 18, 2013 at 7:52 AM, Kashyap Chamarthy >wrote: > > > >> Heya, > >> > >> Fedora release-engineering prepared a cloud-consumable image of F19 Test > >> Compose 5, > >> > >> https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/ > > > > > > Nice! Do we know what kickstart file and what version of it they are > > compiled with? > > Not sure. But yes - the above directory should also contain its kickstart > file it's > created with. > > It should mostly be this: > > > > https://git.fedorahosted.org/cgit/cloud-kickstarts.git/tree/generic/fedora-19-x86_64-cloud.ks > > Dennis Gilmore/Matthew Miller might confirm(CC'ed them). > Yea, I was pretty sure if must be that but wasn't sure of the version. But the user in the image is called "fedora" and that was only just the last change (from ec2-user), so it's current trunk. > [...] > > > > FWIW, the above two steps can also be combined into one: > > > > $ glance image-create --name fedora19-tc5 --is-public true \ > > --disk-format qcow2 --container-format bare --copy-from \ > > > > > https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/Fedora-x86_64-19-TC5-20130617-sda.qcow2 > > > > ...the downside being that you can't verify the checksum between > > downloading the image and pushing it into glance. > > Nice, thank you. > > > -- > /kashyap > -------------- next part -------------- An HTML attachment was scrubbed... URL: From red at fedoraproject.org Tue Jun 18 09:51:26 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Tue, 18 Jun 2013 11:51:26 +0200 Subject: [Rdo-list] Suggestion: Notify this list of new forum threads In-Reply-To: <51C015E5.9090101@redhat.com> References: <51BF0FF6.6060506@redhat.com> <51BF1621.6030504@redhat.com> <51C015E5.9090101@redhat.com> Message-ID: First, +1 to the basic idea. That'd be a huge step forward to form a valuable community here. On Tue, Jun 18, 2013 at 10:10 AM, Dave Neary wrote: > Hi, > > On 06/17/2013 03:58 PM, Perry Myers wrote: > > We could reply and discuss the message on list, but it just means that > > in order to update the thread on forum, it would require manually doing > so. > > I think I'd prefer to see discussion happen on the forum rather than > have it split across two places - of course if people reply here that's > up to them, but I'd like to see the forum take priority. > +1 to that. Splitting discussions is mostly harming productivity and effectiveness. It's much like cross-posting on mailing lists. -------------- next part -------------- An HTML attachment was scrubbed... URL: From red at fedoraproject.org Tue Jun 18 10:11:28 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Tue, 18 Jun 2013 12:11:28 +0200 Subject: [Rdo-list] [For testing] Fedora 19 (Test Compose) cloud images In-Reply-To: <51BFF5B3.80305@redhat.com> References: <51BFF5B3.80305@redhat.com> Message-ID: On Tue, Jun 18, 2013 at 7:52 AM, Kashyap Chamarthy wrote: > Please report any problems here. > As has been pointed out on the Fedora Cloud SIG mailing list, the image is currently affected by this bug: https://bugzilla.redhat.com/show_bug.cgi?id=964006 Long story short: The minor issue is that the hostname is not set properly, the major issue though is that booting the system is delayed by a minute or so and a systemd unit will fail. People are working on a solution already and it will be in place before F19 is going to be released (i.e. the issue is considered a release blocker). Note that it should not have any other impact and seems to work very well otherwise. That said, further testing would be much appreciated. -- Sandro -------------- next part -------------- An HTML attachment was scrubbed... URL: From rdo-info at redhat.com Tue Jun 18 12:01:14 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 12:01:14 +0000 Subject: [Rdo-list] [RDO] Welcome Aboard! Message-ID: <0000013f5729075b-2fca7cd8-fdf4-4dc2-93a9-b6c24e975fcb-000000@email.amazonses.com> Hello rdo-list! dneary has created an account for you at RDO. Your login credentials are: Email: rdo-list at redhat.com Password: corn hair mule Url: http://openstack.redhat.com/forum/ Have a great day! From rdo-info at redhat.com Tue Jun 18 12:21:08 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 12:21:08 +0000 Subject: [Rdo-list] [RDO] pixelbeat commented on a discussion. Message-ID: <0000013f573b41e7-1eaa131e-e441-4adb-8f64-39976433a93a-000000@email.amazonses.com> pixelbeat commented on a discussion. What version of openstack-nova-compute are you using? (rpm q openstack-nova-compute). The invalid key is probably a side effect of the real problem, the side effect that abrtd can't load the package key for some reason. Is there anything in /var/log/nova/compute.log to indicate the real problem? --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/comment/657#Comment_657 Have a great day! From rdo-info at redhat.com Tue Jun 18 12:39:43 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 12:39:43 +0000 Subject: [Rdo-list] [RDO] dneary started a discussion. Message-ID: <0000013f574c443e-416ba248-9eef-4016-8cc0-8351ce8b4be4-000000@email.amazonses.com> dneary started a discussion. RDO Draw day 2: Congratulations to Jean-Francois Saucier! --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/220/rdo-draw-day-2-congratulations-to-jean-francois-saucier Have a great day! From pmyers at redhat.com Tue Jun 18 13:14:05 2013 From: pmyers at redhat.com (Perry Myers) Date: Tue, 18 Jun 2013 09:14:05 -0400 Subject: [Rdo-list] #rdo on freenode irc Message-ID: <51C05D1D.7080806@redhat.com> For folks who want to participate in the RDO community via more direct medium (vs. email and forums), we now have #rdo channel on freenode irc. So, please join us on #rdo, and ask questions or help others. Complete oversight that we didn't create this channel sooner! Cheers, Perry From rdo-info at redhat.com Tue Jun 18 13:19:01 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 13:19:01 +0000 Subject: [Rdo-list] [RDO] pmyers started a discussion. Message-ID: <0000013f5770409d-166d0b57-27ee-4a2b-aecf-4bb327e3e424-000000@email.amazonses.com> pmyers started a discussion. #rdo channel on Freenode irc --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/221/rdo-channel-on-freenode-irc Have a great day! From mattdm at fedoraproject.org Tue Jun 18 14:43:13 2013 From: mattdm at fedoraproject.org (Matthew Miller) Date: Tue, 18 Jun 2013 10:43:13 -0400 Subject: [Rdo-list] [For testing] Fedora 19 (Test Compose) cloud images In-Reply-To: <51C018E9.5030109@redhat.com> References: <51BFF5B3.80305@redhat.com> <51C018E9.5030109@redhat.com> Message-ID: <20130618144313.GA5496@disco.bu.edu> On Tue, Jun 18, 2013 at 01:53:05PM +0530, Kashyap Chamarthy wrote: > >> https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/ > > Nice! Do we know what kickstart file and what version of it they are > > compiled with? > Not sure. But yes - the above directory should also contain its kickstart file it's > created with. > It should mostly be this: > https://git.fedorahosted.org/cgit/cloud-kickstarts.git/tree/generic/fedora-19-x86_64-cloud.ks > Dennis Gilmore/Matthew Miller might confirm(CC'ed them). Yep, confirmed. Dennis sometimes makes minor tweaks required to get the somewhat arcane buildsystem to work -- part of the process verifies the kickstart files under RHEL 6, so the kickstart needs to parse as valid for both the current kickstart _and_ for that release. > > --disk-format qcow2 --container-format bare --copy-from \ > > https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/Fedora-x86_64-19-TC5-20130617-sda.qcow2 > > ...the downside being that you can't verify the checksum between > > downloading the image and pushing it into glance. > Nice, thank you. Feedback appreciated! Because of an outstanding bug with SE Linux and cloud-init, there will be a one-minute delay before you can log in unless you boot with user-data like this: #cloud-config cloud_init_modules: - bootcmd - write-files - growpart - resizefs - rsyslog - users-groups - ssh -- Matthew Miller ??? Fedora Cloud Architect ??? From rdo-info at redhat.com Tue Jun 18 16:11:41 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 16:11:41 +0000 Subject: [Rdo-list] [RDO] dneary commented on a discussion. Message-ID: <0000013f580e53cf-3431e256-1deb-4d5a-99dd-b4984bde4540-000000@email.amazonses.com> dneary commented on a discussion. Thanks @bv_arvind! The nova user should be created by the installer, though. Sounds like something went wrong somewhere... Dave. --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/comment/658#Comment_658 Have a great day! From rdo-info at redhat.com Tue Jun 18 16:16:53 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 16:16:53 +0000 Subject: [Rdo-list] [RDO] pixelbeat commented on a discussion. Message-ID: <0000013f58131593-a4d9158a-bfbc-4e32-9dab-24771d6d385f-000000@email.amazonses.com> pixelbeat commented on a discussion. Yes the nova user should be created when the openstack-nova-common package is installed. Seems like that package wasn't even installed. Do you perhaps have other vestiges of a nova install on the system, which is blocking normal installation of the packages? --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/comment/659#Comment_659 Have a great day! From mmilan.2006 at gmail.com Tue Jun 18 16:24:29 2013 From: mmilan.2006 at gmail.com (Milan M) Date: Tue, 18 Jun 2013 21:54:29 +0530 Subject: [Rdo-list] Swift client for Linux Message-ID: Hi, Can anybody suggest a good graphical Client for Swift. I can find cyberduck for windows, but no such utility for linux, DragonDisk doesn't works on my system. Regards, Vaibhav -------------- next part -------------- An HTML attachment was scrubbed... URL: From dneary at redhat.com Tue Jun 18 17:10:55 2013 From: dneary at redhat.com (Dave Neary) Date: Tue, 18 Jun 2013 19:10:55 +0200 Subject: [Rdo-list] [RDO] dneary commented on a discussion. In-Reply-To: <0000013f580e53cf-3431e256-1deb-4d5a-99dd-b4984bde4540-000000@email.amazonses.com> References: <0000013f580e53cf-3431e256-1deb-4d5a-99dd-b4984bde4540-000000@email.amazonses.com> Message-ID: <51C0949F.7010208@redhat.com> OK - these are teething problems - I intended to disable email notification for comments, which is not very useful for the list. I will figure it out. Cheers, Dave. On 06/18/2013 06:11 PM, RDO Forum wrote: > dneary commented on a discussion. > > Thanks @bv_arvind! > > > > The nova user should be created by the installer, though. Sounds like something went wrong somewhere... > > > > Dave. > > --- > Follow the link below to check it out: > http://openstack.redhat.com/forum/discussion/comment/658#Comment_658 > > Have a great day! > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From oblaut at redhat.com Tue Jun 18 18:03:24 2013 From: oblaut at redhat.com (Ofer Blaut) Date: Tue, 18 Jun 2013 14:03:24 -0400 (EDT) Subject: [Rdo-list] Quantum and lack of connections In-Reply-To: <51BFFA2D.8030303@redhat.com> References: <1381169160.95951.1371533755325.JavaMail.root@redhat.com> <51BFF6ED.703@redhat.com> <963474632.99489.1371535359323.JavaMail.root@redhat.com> <51BFFA2D.8030303@redhat.com> Message-ID: <823807352.443292.1371578604648.JavaMail.root@redhat.com> ----- Original Message ----- > From: "Gary Kotton" > To: "Ofer Blaut" > Cc: rdo-list at redhat.com > Sent: Tuesday, June 18, 2013 9:11:57 AM > Subject: Re: [Rdo-list] Quantum and lack of connections > > On 06/18/2013 09:02 AM, Ofer Blaut wrote: > > > > ----- Original Message ----- > >> From: "Gary Kotton" > >> To: "Ofer Blaut" > >> Cc: rdo-list at redhat.com > >> Sent: Tuesday, June 18, 2013 8:58:05 AM > >> Subject: Re: [Rdo-list] Quantum and lack of connections > >> > >> On 06/18/2013 08:35 AM, Ofer Blaut wrote: > >>> Hi > >>> > >>> I wonder how can i configure quantum network /subnets/ports when L3/DHCP > >>> fails to connect to quantum server. > >> These are not related. The Quantum service enables the user to configure > >> the network configuration. The DHCP agent provides the IPAM > >> implementation and the L3 agent provides the floating IP and routing > >> support. > >> > >>> I expect that user will have CLI/API errors upon DHCP not connected , and > >>> new IPs will not be allocated > >> Yes, it would be nice if the user was able to know if there was a > >> problem, but it is not related at all to the Quantum API. In actual fact > >> the administrator is able to invoke the command: "quantum agent-list" to > >> determine if there are any issues with the backiend implementation of > >> the Quantum API's. The administrator would in turn need to address the > >> issues. > > I don't expect user to check quantum agent-list all the time. > > In case DHCP/L3 fails , i think new commands should alert about it > > Can it be DHCP will miss it info about restart ? > > Please differentiate between a user and an administrator. The user will > be able to configure ports, subnets and networks. The administrator is > responsible to ensure that the service is up and running. Anyone who > will be running a cloud service will need to ensure that they have > highly available and redundant dhcp and l3 agents. The way of monitoring > this is via the aforementioned command. Thinking on it again, usually when there is a bug in a service like malformed packet cause it to crash both HA services might fail. >From system point of view, i think that when a DHCP/L3 service is down, NEW config should NOT accepted , until service is back online user should be alerted ad well as admin Ofer > > You are welcome to check out > http://docs.openstack.org/trunk/openstack-network/admin/content/ch_high_avail.html > > > > > Ofer > > > > > >>> See errors attached http://paste.openstack.org/show/38836/ > >> From the traces it looks like the l3 agent has successfully connected > >> to the message broker. The DHCP agent is unable to connect to the > >> message broker. This may be during the boot process where it may take up > >> to a minute (this is due to the qpid timeouts) > >> > >>> Ofer > >>> > >>> _______________________________________________ > >>> Rdo-list mailing list > >>> Rdo-list at redhat.com > >>> https://www.redhat.com/mailman/listinfo/rdo-list > >> > > From rdo-info at redhat.com Tue Jun 18 18:36:22 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 18:36:22 +0000 Subject: [Rdo-list] [RDO] pmyers started a discussion. Message-ID: <0000013f5892c86c-fe451829-6877-4e66-9f99-cd8c68797a14-000000@email.amazonses.com> pmyers started a discussion. Red Hat Summit 2013: OpenStack Keynotes, Videos & Presentations --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/222/red-hat-summit-2013-openstack-keynotes-videos-presentations Have a great day! From rdo-info at redhat.com Tue Jun 18 19:25:28 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 19:25:28 +0000 Subject: [Rdo-list] [RDO] rkukura commented on a discussion. Message-ID: <0000013f58bfbc86-d9aa559d-6450-46ab-9a20-9b889ef1e5d8-000000@email.amazonses.com> rkukura commented on a discussion. Hi Steven, The VLAN tags are being modified by OVS flow rules as packets cross the veth connecting the bridges. These flows can be displayed using ovs-ofctl as follows: ovs-ofctl dump-flows br-int NXST_FLOW reply (xid=0x4): cookie=0x0, duration=947602.247s, table=0, n_packets=150980, n_bytes=37605726, idle_age=1, hard_age=65534, priority=1 actions=NORMAL cookie=0x0, duration=947598.9s, table=0, n_packets=16652192, n_bytes=1367674080, idle_age=0, hard_age=65534, priority=2,in_port=2 actions=drop cookie=0x0, duration=110.96s, table=0, n_packets=4, n_bytes=1158, idle_age=48, priority=3,in_port=2,dl_vlan=1000 actions=mod_vlan_vid:2,NORMAL ovs-ofctl dump-flows br-eth2 NXST_FLOW reply (xid=0x4): cookie=0x0, duration=947604.202s, table=0, n_packets=17266871, n_bytes=1429653351, idle_age=0, hard_age=65534, priority=1 actions=NORMAL cookie=0x0, duration=947601.253s, table=0, n_packets=31, n_bytes=2318, idle_age=113, hard_age=65534, priority=2,in_port=4 actions=drop cookie=0x0, duration=113.882s, table=0, n_packets=107, n_bytes=6118, idle_age=1, priority=4,in_port=4,dl_vlan=2 actions=mod_vlan_vid:1000,NORMAL [root at rachel ~(keystone_bob)]# In this case, the local VLAN tag on br-int is 2, and the VLAN tag on the physical network (br-eth2) is 1000. Whether you need to enable VLAN splinters depends on what NIC driver you are using. I have not needed to run commands such as "ovs-vsctl set port eth2 trunks-81,82". We will be working to characterize any performance overhead from using multiple bridges connected by veths, and may explore a single-bridge solution if justified. Hope this helps, -Bob --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/comment/660#Comment_660 Have a great day! From rdo-info at redhat.com Tue Jun 18 20:40:01 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 20:40:01 +0000 Subject: [Rdo-list] [RDO] mikey10123 commented on a discussion. Message-ID: <0000013f5903fec1-66599af9-4397-4bd0-8f87-99c46144b206-000000@email.amazonses.com> mikey10123 commented on a discussion. I was hitting the same thing. I disabled selinux, and lo and behold, it ran to completion. --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/comment/661#Comment_661 Have a great day! From rdo-info at redhat.com Tue Jun 18 20:48:07 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 20:48:07 +0000 Subject: [Rdo-list] [RDO] mattdm commented on a discussion. Message-ID: <0000013f590b67fa-4f4182ef-f5a9-43a2-9b35-97a318d6d1b5-000000@email.amazonses.com> mattdm commented on a discussion. Please file a bug against this, because that's hitting the problem with a very big hammer. (Fine for diagnosing, bad for real use!) --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/comment/662#Comment_662 Have a great day! From pmyers at redhat.com Tue Jun 18 21:30:13 2013 From: pmyers at redhat.com (Perry Myers) Date: Tue, 18 Jun 2013 17:30:13 -0400 Subject: [Rdo-list] Quantum in Packstack In-Reply-To: <1371589433.6670.1838.camel@papa.taylor.lan> References: <1371589433.6670.1838.camel@papa.taylor.lan> Message-ID: <51C0D165.3060208@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/18/2013 05:03 PM, Forrest Taylor wrote: > Perry, > > I was playing with the 2013-06-18.1 puddle and I noticed when I > run packstack, OpenStack Networking is used by default. However, > there are no routers, networks or subnets configured. Are there > plans to enable a router, network and/or subnet in packstack? That's a good question and one that we've been discussing a bit... Packstack installs the services, and gets things set up so that an admin can then start creating tenants. But, since Packstack doesn't know how many tenants you want to set up, or anything, it can't really know what networks and subnets you want created. Typically the task of creating a tenant network/subnet/router would be done by a cloud administrator at the point at which they create a new tenant. Right now, that would involve a sequence of manual steps. It could be that an OpenStack management solution of some sort could help to automate those tasks (since they do span multiple components), or a simple script could help. There has been talk about giving Packstack an option to create a single tenant, network, subnet by default. This would be useful for both testing environments as well as allinone or demo installs. I believe Maru (cc'd) has been working on changes to puppet modules to support this, and Terry/Ryan (cc'd) are working on integrating this into Packstack. But this doesn't solve the more general issue of "after Packstack deployment, I create 10 new tenants... who/how does the network/subnet creation happen?" Right now, it's just documentation, but perhaps in the future there is a better solution. Brent (cc'd) is helping to chase this down. I've cc'd some folks that might be able to weigh in on this Perry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlHA0WUACgkQxdKLkeZeTz0YDQCcCTg9I7CsWEvqi9M20/3ALhAW xIcAnRpa4qTDIB2SEN7XA0iuANJoIUoQ =7pcz -----END PGP SIGNATURE----- From rdo-info at redhat.com Tue Jun 18 23:50:47 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 23:50:47 +0000 Subject: [Rdo-list] [RDO] bv_arvind commented on a discussion. Message-ID: <0000013f59b2a693-c278f3c0-7a06-4041-9926-f5606ba052f9-000000@email.amazonses.com> bv_arvind commented on a discussion. yes a restart did make everything bootup fine. --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/comment/664#Comment_664 Have a great day! From rdo-info at redhat.com Tue Jun 18 23:55:46 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 23:55:46 +0000 Subject: [Rdo-list] [RDO] bv_arvind commented on a discussion. Message-ID: <0000013f59b73400-ed4eef7a-2cc8-46e8-ac18-b7811c1b06a2-000000@email.amazonses.com> bv_arvind commented on a discussion. hi, I tried building it using the src rpm. I expected that it would create the required sources in BUILD folder. However it just seems to install yum repository location and expects the installation to take place during boot time by fetching from the yum repository Here is the spec file that I got after making build : %description This package contains the RDO repository %install install -p -D -m 644 %{SOURCE0} %{buildroot}%{_sysconfdir}/yum.repos.d/rdo-release.repo GPG Key install -Dpm 644 %{SOURCE1} %{buildroot}%{_sysconfdir}/pki/rpm-gpg/RPM-GPG-KEY-RDO-Grizzly %files %{_sysconfdir}/yum.repos.d/rdo-release.repo %{_sysconfdir}/pki/rpm-gpg/RPM-GPG-KEY-RDO-Grizzly I was hoping to get a complete src package rpm so that the image can boot up with the src installed ;( --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/comment/665#Comment_665 Have a great day! From rdo-info at redhat.com Tue Jun 18 23:50:12 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 18 Jun 2013 23:50:12 +0000 Subject: [Rdo-list] [RDO] bv_arvind commented on a discussion. Message-ID: <0000013f59b21df8-f4f3a8f0-5a83-48e6-a522-a238fd1881a5-000000@email.amazonses.com> bv_arvind commented on a discussion. Yes I guess its because of my previous trails I had this failure. A clean install works! --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/comment/663#Comment_663 Have a great day! From rdo-info at redhat.com Wed Jun 19 00:27:27 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 19 Jun 2013 00:27:27 +0000 Subject: [Rdo-list] [RDO] mikey10123 commented on a discussion. Message-ID: <0000013f59d43716-ca0e2626-0a04-45c7-9270-c4ab104675a6-000000@email.amazonses.com> mikey10123 commented on a discussion. I'm actually not sure this is a workaround. I'm on a second round of my test install, and even after disabling selinux this is hung on this manifest. I'll continue to investigate. --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/comment/666#Comment_666 Have a great day! From rdo-info at redhat.com Wed Jun 19 02:25:00 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 19 Jun 2013 02:25:00 +0000 Subject: [Rdo-list] [RDO] liuchao started a discussion. Message-ID: <0000013f5a3fd653-4f8a2a9f-bd5a-4d09-9ceb-e341f6cd2772-000000@email.amazonses.com> liuchao started a discussion. timeout on x86_64 CentOS release 6.4 --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/223/timeout-on-x86_64-centos-release-6-4 Have a great day! From rdo-info at redhat.com Wed Jun 19 02:25:05 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 19 Jun 2013 02:25:05 +0000 Subject: [Rdo-list] [RDO] liuchao started a discussion. Message-ID: <0000013f5a3fe9f6-80818712-6e90-4ee5-90c3-ef88edc1993c-000000@email.amazonses.com> liuchao started a discussion. timeout on x86_64 CentOS release 6.4 --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/224/timeout-on-x86_64-centos-release-6-4 Have a great day! From rdo-info at redhat.com Wed Jun 19 02:48:55 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 19 Jun 2013 02:48:55 +0000 Subject: [Rdo-list] [RDO] sgordon commented on a discussion. Message-ID: <0000013f5a55bc21-35740297-fa1c-4396-9a76-5a23c5443289-000000@email.amazonses.com> sgordon commented on a discussion. @bv_arvind: As per my answers to your questions on ask.openstack.org, if you use the SRPM for nova (openstack-nova-2013.1.2-1.el6.src.rpm) as suggested by @pixelbeat above then you will get what you are after. From the output you pasted it looks like you rebuilt rdo-release-grizzly-3.src.rpm instead. --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/comment/667#Comment_667 Have a great day! From gkotton at redhat.com Wed Jun 19 06:07:35 2013 From: gkotton at redhat.com (Gary Kotton) Date: Wed, 19 Jun 2013 09:07:35 +0300 Subject: [Rdo-list] Quantum in Packstack In-Reply-To: <51C0D165.3060208@redhat.com> References: <1371589433.6670.1838.camel@papa.taylor.lan> <51C0D165.3060208@redhat.com> Message-ID: <51C14AA7.9060707@redhat.com> On 06/19/2013 12:30 AM, Perry Myers wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 06/18/2013 05:03 PM, Forrest Taylor wrote: >> Perry, >> >> I was playing with the 2013-06-18.1 puddle and I noticed when I >> run packstack, OpenStack Networking is used by default. However, >> there are no routers, networks or subnets configured. Are there >> plans to enable a router, network and/or subnet in packstack? > That's a good question and one that we've been discussing a bit... > > Packstack installs the services, and gets things set up so that an > admin can then start creating tenants. > > But, since Packstack doesn't know how many tenants you want to set up, > or anything, it can't really know what networks and subnets you want > created. > > Typically the task of creating a tenant network/subnet/router would be > done by a cloud administrator at the point at which they create a new > tenant. Right now, that would involve a sequence of manual steps. An important thing to note here is that only an administrator can create a provider network. > It could be that an OpenStack management solution of some sort could > help to automate those tasks (since they do span multiple components), > or a simple script could help. > > There has been talk about giving Packstack an option to create a > single tenant, network, subnet by default. This would be useful for > both testing environments as well as allinone or demo installs. I > believe Maru (cc'd) has been working on changes to puppet modules to > support this, and Terry/Ryan (cc'd) are working on integrating this > into Packstack. > > But this doesn't solve the more general issue of "after Packstack > deployment, I create 10 new tenants... who/how does the network/subnet > creation happen?" > > Right now, it's just documentation, but perhaps in the future there is > a better solution. Brent (cc'd) is helping to chase this down. > > I've cc'd some folks that might be able to weigh in on this > > Perry > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.13 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEARECAAYFAlHA0WUACgkQxdKLkeZeTz0YDQCcCTg9I7CsWEvqi9M20/3ALhAW > xIcAnRpa4qTDIB2SEN7XA0iuANJoIUoQ > =7pcz > -----END PGP SIGNATURE----- From rdo-info at redhat.com Wed Jun 19 06:59:30 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 19 Jun 2013 06:59:30 +0000 Subject: [Rdo-list] [RDO] konkas commented on a discussion. Message-ID: <0000013f5b3b278b-93d2dcae-23ce-4bd5-ac4f-7b0fa8497e6c-000000@email.amazonses.com> konkas commented on a discussion. I have a similar setup with Centos 6.4 I have added a pool with the following command: nova-manage floating create --pool=nova --ip_range=192.168.1.120/27 Still the web interface says: "No floating ip pools available" when I try to associate a floating ip with an instance. The same problem occurs when I try to allocate ip to project in the menu Access & Security/Floating IPs. Above is executed as the admin user in the web interface. Any suggestions? --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/comment/668#Comment_668 Have a great day! From red at fedoraproject.org Wed Jun 19 07:50:06 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Wed, 19 Jun 2013 09:50:06 +0200 Subject: [Rdo-list] Suggestion: Notify this list of new forum threads In-Reply-To: References: <51BF0FF6.6060506@redhat.com> <51BF1621.6030504@redhat.com> <51C015E5.9090101@redhat.com> Message-ID: Is it somehow possible to reflect the thread topic in the subject, though? Lots of mails that just say "s.o. commented on a discussion" are most likely just being ignored (if not considered spam). -------------- next part -------------- An HTML attachment was scrubbed... URL: From dneary at redhat.com Wed Jun 19 10:33:47 2013 From: dneary at redhat.com (Dave Neary) Date: Wed, 19 Jun 2013 12:33:47 +0200 Subject: [Rdo-list] Suggestion: Notify this list of new forum threads In-Reply-To: References: <51BF0FF6.6060506@redhat.com> <51BF1621.6030504@redhat.com> <51C015E5.9090101@redhat.com> Message-ID: <51C1890B.1020807@redhat.com> Hi, Threading on topics would be awesome. Vanilla doesn't do it right now, but I'll open a ticket for it. Cheers, Dave. On 06/19/2013 09:50 AM, Sandro "red" Mathys wrote: > Is it somehow possible to reflect the thread topic in the subject, > though? Lots of mails that just say "s.o. commented on a discussion" are > most likely just being ignored (if not considered spam). > > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From dneary at redhat.com Wed Jun 19 10:46:02 2013 From: dneary at redhat.com (Dave Neary) Date: Wed, 19 Jun 2013 12:46:02 +0200 Subject: [Rdo-list] [RDO] dneary commented on a discussion. In-Reply-To: <51C0949F.7010208@redhat.com> References: <0000013f580e53cf-3431e256-1deb-4d5a-99dd-b4984bde4540-000000@email.amazonses.com> <51C0949F.7010208@redhat.com> Message-ID: <51C18BEA.3080503@redhat.com> Hi, I have resolved this issue. It was not incorrectly set preferences, it was a bug in the forum software (since fixed in the latest branch). Cheers, Dave. On 06/18/2013 07:10 PM, Dave Neary wrote: > OK - these are teething problems - I intended to disable email > notification for comments, which is not very useful for the list. > > I will figure it out. > > Cheers, > Dave. > > On 06/18/2013 06:11 PM, RDO Forum wrote: >> dneary commented on a discussion. >> >> Thanks @bv_arvind! >> >> >> >> The nova user should be created by the installer, though. Sounds like something went wrong somewhere... >> >> >> >> Dave. >> >> --- >> Follow the link below to check it out: >> http://openstack.redhat.com/forum/discussion/comment/658#Comment_658 >> >> Have a great day! >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> > -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From pmyers at redhat.com Wed Jun 19 14:25:33 2013 From: pmyers at redhat.com (Perry Myers) Date: Wed, 19 Jun 2013 10:25:33 -0400 Subject: [Rdo-list] [Quantum] Provider networks for floating IP's In-Reply-To: <51C1B76C.80605@redhat.com> References: <51C1B76C.80605@redhat.com> Message-ID: <51C1BF5D.80302@redhat.com> On 06/19/2013 09:51 AM, Gary Kotton wrote: > Hi, > Can you please explain how we can use the provider networks on for > floating IP's on the br-int instead of br-ex. I recall that i the past > you sent a mail but was unable to find it. Ofer has been trying to get > this to work with no avail. > Thanks > Gary From rdo-info at redhat.com Wed Jun 19 14:55:24 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 19 Jun 2013 14:55:24 +0000 Subject: [Rdo-list] [RDO] Lashik started a discussion. Message-ID: <0000013f5ceedabc-9c6c124f-244c-411e-8f34-79b373447ae1-000000@email.amazonses.com> Lashik started a discussion. RDO kernel and GRE support --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/225/rdo-kernel-and-gre-support Have a great day! From rdo-info at redhat.com Wed Jun 19 16:20:41 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 19 Jun 2013 16:20:41 +0000 Subject: [Rdo-list] [RDO] murakawa started a discussion. Message-ID: <0000013f5d3cec12-447f1038-85e9-468d-925a-f1bc3ade3422-000000@email.amazonses.com> murakawa started a discussion. Can't create instance using F18 image --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/226/cant-create-instance-using-f18-image Have a great day! From rcritten at redhat.com Wed Jun 19 17:10:40 2013 From: rcritten at redhat.com (Rob Crittenden) Date: Wed, 19 Jun 2013 13:10:40 -0400 Subject: [Rdo-list] securing services Message-ID: <51C1E610.9040302@redhat.com> I'm looking at adding security to some of the system services using Red Hat Identity Management (FreeIPA upstream). This is initially going to be SSL for some, Kerberos for others. For a first round effort this won't include using Kerberos to authenticate users to Keystone (a much bigger hammer is needed for that). I'm looking at adding SSL to Apache and Kerberos to qpid. What about the database? I can add SSL to mysql and Kerberos to postgres, should I support both? What is the preferred SQL database for RHOS? rob From rdo-info at redhat.com Wed Jun 19 17:36:00 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 19 Jun 2013 17:36:00 +0000 Subject: [Rdo-list] [RDO] mjames14 started a discussion. Message-ID: <0000013f5d81e32c-7040edc1-9de8-40c0-9839-efff7ccde997-000000@email.amazonses.com> mjames14 started a discussion. Migrating instances across openstack deployments --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/227/migrating-instances-across-openstack-deployments Have a great day! From rdo-info at redhat.com Wed Jun 19 19:18:03 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 19 Jun 2013 19:18:03 +0000 Subject: [Rdo-list] [RDO] M4rc0 started a discussion. Message-ID: <0000013f5ddf51a1-d6d4b768-7d85-47c8-a81b-e7bba3e635be-000000@email.amazonses.com> M4rc0 started a discussion. Installing RDO over Fedora 18 stops because some bugs --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/228/installing-rdo-over-fedora-18-stops-because-some-bugs Have a great day! From rkukura at redhat.com Wed Jun 19 19:39:15 2013 From: rkukura at redhat.com (Robert Kukura) Date: Wed, 19 Jun 2013 15:39:15 -0400 Subject: [Rdo-list] [Quantum] Provider networks for floating IP's In-Reply-To: <51C1BF5D.80302@redhat.com> References: <51C1B76C.80605@redhat.com> <51C1BF5D.80302@redhat.com> Message-ID: <51C208E3.2000801@redhat.com> On 06/19/2013 10:25 AM, Perry Myers wrote: > On 06/19/2013 09:51 AM, Gary Kotton wrote: >> Hi, >> Can you please explain how we can use the provider networks on for >> floating IP's on the br-int instead of br-ex. I recall that i the past >> you sent a mail but was unable to find it. Ofer has been trying to get >> this to work with no avail. No problem. Basically, if external_bridge is unset, then the router's gateway network is treated exactly like other (private) networks added to the router as interfaces. The router's configured interface_driver is used, so quantum.agent.linux.interface.OVSInterfaceDriver plugs the router into the network using br-int, and openvswitch-agent sets up the flow rules for it. To use this approach, change the l3-agent config to unset external_bridge (overriding the default of br-ex). Then, when creating the external network, specify the provider attributes describing it. The current upstream admin guide says to set provider:network_type to local for the external network, so set it to flat or vlan instead, set provider:physical_network appropriately and also set provider:segmentation_id for a VLAN external network. Note that the physical_network must be listed in network_vlan_ranges even if no tenant VLANs are being used on that network, and must be mapped via bridge_mappings on the network nodes and have the network interface added to OVS bridge (typically br-ethX) as usual. Then create the subnet, create the router, and set the router's gateway to be the external network, all as usual. Advantages of the provider external network approach: * Works with linuxbridge in addition to openvswitch * External network can be flat or on a VLAN * External network can be on the same network interface as tenant VLANs * Should be possible for different routers in the same l3-agent to use different external networks (not sure if tested) Advantages of the external_bridge approach: * Possible slight performance advantage using single br-ex instead of br-int->veth->br-ethX * Better documentation -Bob >> Thanks >> Gary > > From rdo-info at redhat.com Wed Jun 19 22:47:59 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 19 Jun 2013 22:47:59 +0000 Subject: [Rdo-list] [RDO] Rextetriory started a discussion. Message-ID: <0000013f5e9f849e-167096b9-59d6-4ec2-baf0-aa586c1b7509-000000@email.amazonses.com> Rextetriory started a discussion. chwilowki oo --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/229/chwilowki-oo Have a great day! From rdo-info at redhat.com Thu Jun 20 03:00:44 2013 From: rdo-info at redhat.com (RDO Forum) Date: Thu, 20 Jun 2013 03:00:44 +0000 Subject: [Rdo-list] [RDO] ppyy started a discussion. Message-ID: <0000013f5f86eb17-23bc1b15-8dc6-4385-aba3-521e078e93cf-000000@email.amazonses.com> ppyy started a discussion. WARNING [quantum.db.agentschedulers_db] Fail scheduling network --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/230/warning-quantum-db-agentschedulers_db-fail-scheduling-network Have a great day! From rdo-info at redhat.com Thu Jun 20 06:44:23 2013 From: rdo-info at redhat.com (RDO Forum) Date: Thu, 20 Jun 2013 06:44:23 +0000 Subject: [Rdo-list] [RDO] ixara started a discussion. Message-ID: <0000013f6053aa78-89bae897-9292-4895-8c98-df7305baa9f7-000000@email.amazonses.com> ixara started a discussion. Instance cant get ip --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/231/instance-cant-get-ip Have a great day! From red at fedoraproject.org Thu Jun 20 08:30:05 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Thu, 20 Jun 2013 10:30:05 +0200 Subject: [Rdo-list] Why use yum priority in rdo-release repo file? Message-ID: Even though RDO is supposed to always being ahead of RHEL and EPEL, it enforces a higher priority (lower priority=N) than the default. Why? Enforcing priorities should really only ever happen if absolutely necessary and will often cause pain to users. For example I'm trying to manage my RDO installation with Puppet but EPEL and RDO only have Puppet 2.6 which is EOL and it has been decided that puppet-openstack will no longer support it effective immediately. But to install puppet 3.2 from puppetlabs' repo, I first have to scrap the priority from RDO's repo file manually. As a (former) developer for Packstack I understand it requires a specific Puppet version but I think we all agree most (non proof of concept) installations are not using Packstack to set up or maintain their OpenStack cloud. -- Sandro -------------- next part -------------- An HTML attachment was scrubbed... URL: From pbrady at redhat.com Thu Jun 20 11:03:16 2013 From: pbrady at redhat.com (=?ISO-8859-1?Q?P=E1draig_Brady?=) Date: Thu, 20 Jun 2013 12:03:16 +0100 Subject: [Rdo-list] Why use yum priority in rdo-release repo file? In-Reply-To: References: Message-ID: <51C2E174.9060400@redhat.com> On 06/20/2013 09:30 AM, Sandro "red" Mathys wrote: > Even though RDO is supposed to always being ahead of RHEL and EPEL, it enforces a higher priority (lower priority=N) than the default. Why? So yes this is debatable. y-p-p is used with the RHOS product to give precedence over EPEL. I.E. even though EPEL is not required there, con existence is supported. Now RDO requires EPEL so again y-p-p gives us the flexibility for RDO to override EPEL. Now whether this is actually required at present is not obvious. We could retain the flexiblity while avoiding problems with y-p-p by keeping the overlapping set as small as possible. wrt puppet, I'm not sure why it's there TBH. EPEL has 2.6.18-3 while puppet-2.6.18-2 is in the RDO repo. I've asked around a little and will probably just remove puppet from the RDO repo, which will fix your immediate problem. I also see django14 in the RDO grizzly repos. IIRC there were issues with the provides and requires in horizon and django that required this package be present in RDO with y-p-p giving precedence to it. Now there are recent changes in EPEL with Django14 being pushed there. Matthias could you remove Django14 from the RDO repo if possible thus not having to worry about y-p-p for it at least? > Enforcing priorities should really only ever happen if absolutely necessary and will often cause pain to users. > > For example I'm trying to manage my RDO installation with Puppet but EPEL and RDO only have Puppet 2.6 which is EOL and it has been decided that puppet-openstack will no longer support it effective immediately. But to install puppet 3.2 from puppetlabs' repo, I first have to scrap the priority from RDO's repo file manually. > > As a (former) developer for Packstack I understand it requires a specific Puppet version but I think we all agree most (non proof of concept) installations are not using Packstack to set up or maintain their OpenStack cloud. Looking at packstack, it installs y-p-p if epel-release is installed (which it will be by default for RDO). Again the intention here is to allow these "openstack" repos to override EPEL. Maybe we should change that logic to only installing y-p-p if RHOS, as opposed to RDO was being used? Also we'd have packstack setting the priority in the repo files to actually enable y-p-p (which could already have been installed). Anyway given the package removals mentioned about, I don't see an immediate need to adjust packstack. thanks, P?draig. From rdo-info at redhat.com Thu Jun 20 11:34:49 2013 From: rdo-info at redhat.com (RDO Forum) Date: Thu, 20 Jun 2013 11:34:49 +0000 Subject: [Rdo-list] [RDO] suvendu started a discussion. Message-ID: <0000013f615d912a-95b5aca0-f71f-4ef4-a1aa-dab9dce76bca-000000@email.amazonses.com> suvendu started a discussion. Not Able to run openstack-packstack --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/232/not-able-to-run-openstack-packstack Have a great day! From pbrady at redhat.com Thu Jun 20 11:35:09 2013 From: pbrady at redhat.com (=?ISO-8859-1?Q?P=E1draig_Brady?=) Date: Thu, 20 Jun 2013 12:35:09 +0100 Subject: [Rdo-list] Why use yum priority in rdo-release repo file? In-Reply-To: <51C2E174.9060400@redhat.com> References: <51C2E174.9060400@redhat.com> Message-ID: <51C2E8ED.2000806@redhat.com> On 06/20/2013 12:03 PM, P?draig Brady wrote: > On 06/20/2013 09:30 AM, Sandro "red" Mathys wrote: >> Even though RDO is supposed to always being ahead of RHEL and EPEL, it enforces a higher priority (lower priority=N) than the default. Why? > > So yes this is debatable. > y-p-p is used with the RHOS product to give precedence over EPEL. > I.E. even though EPEL is not required there, con existence is supported. > > Now RDO requires EPEL so again y-p-p gives us the flexibility for RDO to override EPEL. > Now whether this is actually required at present is not obvious. > > We could retain the flexiblity while avoiding problems with y-p-p > by keeping the overlapping set as small as possible. > > wrt puppet, I'm not sure why it's there TBH. > EPEL has 2.6.18-3 while puppet-2.6.18-2 is in the RDO repo. > I've asked around a little and will probably just remove > puppet from the RDO repo, which will fix your immediate problem. So I found the reason that puppet was in RDO from the following commit. It was a temp workaround I made in the rush to get a working RDO out the door, and completely forgot about. Now the update in epel should fix this issue, so the plan above to remove puppet from RDO should work, and I've now done that. thanks, P?draig. commit 18a8667ad0ce3046b5a83edfb3df2f85c1ba2c3d Author: P?draig Brady

Date: Tue Apr 9 16:34:17 2013 +0100 bump release to supersede problematic EPEL package Avoid https://bugzilla.redhat.com/show_bug.cgi?id=949549 diff --git a/puppet.spec b/puppet.spec index f7eb4cc..8468e7b 100644 --- a/puppet.spec +++ b/puppet.spec @@ -13,7 +13,7 @@ Name: puppet Version: 2.6.18 -Release: 1%{?dist} +Release: 2.1%{?dist} Summary: A network tool for managing many disparate systems License: GPLv2 URL: http://puppetlabs.com @@ -290,7 +290,7 @@ fi rm -rf %{buildroot} %changelog -* Mon Mar 11 2013 Michael Stahnke - 2.6.18-1 +* Mon Mar 11 2013 Michael Stahnke - 2.6.18-2.1 From red at fedoraproject.org Thu Jun 20 11:50:01 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Thu, 20 Jun 2013 13:50:01 +0200 Subject: [Rdo-list] Why use yum priority in rdo-release repo file? In-Reply-To: <51C2E8ED.2000806@redhat.com> References: <51C2E174.9060400@redhat.com> <51C2E8ED.2000806@redhat.com> Message-ID: Great, thanks for the quick reply and the quick fix. Still thinking yum priorities are bad and should be removed completely from RDO (RHOS is a different story) but if only directly openstack related packages remain in the repo, it shouldn't matter anyway. -- Sandro -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmyers at redhat.com Thu Jun 20 11:56:08 2013 From: pmyers at redhat.com (Perry Myers) Date: Thu, 20 Jun 2013 07:56:08 -0400 Subject: [Rdo-list] securing services In-Reply-To: <51C1E610.9040302@redhat.com> References: <51C1E610.9040302@redhat.com> Message-ID: <51C2EDD8.2030503@redhat.com> On 06/19/2013 01:10 PM, Rob Crittenden wrote: > I'm looking at adding security to some of the system services using Red > Hat Identity Management (FreeIPA upstream). This is initially going to > be SSL for some, Kerberos for others. For a first round effort this > won't include using Kerberos to authenticate users to Keystone (a much > bigger hammer is needed for that). > > I'm looking at adding SSL to Apache and Kerberos to qpid. Sounds good :) > What about the database? I can add SSL to mysql and Kerberos to > postgres, should I support both? What is the preferred SQL database for > RHOS? Upstream OpenStack is mostly using mysql. Postgres should work, but is largely untested. >From an RDO perspective, I would focus on mysql initially as that is what most people are using and what is working 'out of the box' RHOS is in a similar situation because of the upstream bias towards mysql. So ditto for RHOS as well. In fact, mysql is the only officially supported database in RHOS as of right now (and for the foreseeable future) Of course, mariadb will be the natural successor to mysql in Fedora soon, and we'll support that upstream and in RDO as well. In RHOS it will take a bit longer for mariadb to get into RHEL, so that may stay on mysql a bit longer. Hope that helps :) Perry From mrunge at redhat.com Thu Jun 20 11:56:58 2013 From: mrunge at redhat.com (Matthias Runge) Date: Thu, 20 Jun 2013 13:56:58 +0200 Subject: [Rdo-list] Why use yum priority in rdo-release repo file? In-Reply-To: References: <51C2E174.9060400@redhat.com> <51C2E8ED.2000806@redhat.com> Message-ID: <51C2EE0A.3050405@redhat.com> On 20/06/13 13:50, Sandro "red" Mathys wrote: > Great, thanks for the quick reply and the quick fix. Still thinking > yum priorities are bad and should be removed completely from RDO > (RHOS is a different story) but if only directly openstack related > packages remain in the repo, it shouldn't matter anyway. -- Sandro > Why do you think priorities are bad? They give us the freedom to directly steer combinations of packages, thus as overriding packages from elsewhere. Please keep in mind, this won't happen that often, but still there might be cases where this is desired. Matthias From red at fedoraproject.org Thu Jun 20 12:15:16 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Thu, 20 Jun 2013 14:15:16 +0200 Subject: [Rdo-list] Why use yum priority in rdo-release repo file? In-Reply-To: <51C2EE0A.3050405@redhat.com> References: <51C2E174.9060400@redhat.com> <51C2E8ED.2000806@redhat.com> <51C2EE0A.3050405@redhat.com> Message-ID: On Thu, Jun 20, 2013 at 1:56 PM, Matthias Runge wrote: > On 20/06/13 13:50, Sandro "red" Mathys wrote: > > Great, thanks for the quick reply and the quick fix. Still thinking > > yum priorities are bad and should be removed completely from RDO > > (RHOS is a different story) but if only directly openstack related > > packages remain in the repo, it shouldn't matter anyway. -- Sandro > > > Why do you think priorities are bad? > Because they are patronizing the user, relatively hard to overcome and situations where they seem necessary should be avoided in general. > They give us the freedom to > directly steer combinations of packages, thus as overriding packages > from elsewhere. > As written in the first post in this thread: since RDO strives to always be (equal to or more likely) ahead of RHEL and EPEL, such an override should never be necessary. And overriding "packages from _elsewhere_" should not be considered necessary as no other repos are (nor should they be) supported. > Please keep in mind, this won't happen that often, but still there might > be cases where this is desired. > Like in what case? When will RDO ever want an older version of something than what is in RHEL / EPEL? The only thing I can possibly come up with right now are the kernel and other tools where new networking stuff (netns, maybe more) was enabled ahead of time but I sure hope those changes make it back into RHEL with the next kernel update there. Or if not, that new RHEL kernels are again re-built with those patches for RDO as well to avoid security holes. -- Sandro -------------- next part -------------- An HTML attachment was scrubbed... URL: From red at fedoraproject.org Thu Jun 20 13:14:55 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Thu, 20 Jun 2013 15:14:55 +0200 Subject: [Rdo-list] Why use yum priority in rdo-release repo file? In-Reply-To: <1775080400.22416851.1371732785494.JavaMail.root@redhat.com> References: <51C2E174.9060400@redhat.com> <51C2E8ED.2000806@redhat.com> <1775080400.22416851.1371732785494.JavaMail.root@redhat.com> Message-ID: On Thu, Jun 20, 2013 at 2:53 PM, Steve Gordon wrote: > > If puppet is removed from the RDO repo will the Quick Start need to be > updated to explicitly state the EPEL requirement (it does not at the > moment)? Currently my understanding is users only need to explicitly > enable/install the RDO repository, then PackStack (as you say) enables EPEL > if it detects that you are on an EL system...I'm wondering if it is still > able to do this without access to puppet from the RDO repository (chicken > and egg situation)? > Packstack uses pure Python code to enable EPEL. See packstack/plugins/serverprep_901.py:418 -- Sandro -------------- next part -------------- An HTML attachment was scrubbed... URL: From pbrady at redhat.com Thu Jun 20 13:25:52 2013 From: pbrady at redhat.com (=?UTF-8?B?UMOhZHJhaWcgQnJhZHk=?=) Date: Thu, 20 Jun 2013 14:25:52 +0100 Subject: [Rdo-list] Why use yum priority in rdo-release repo file? In-Reply-To: <1775080400.22416851.1371732785494.JavaMail.root@redhat.com> References: <51C2E174.9060400@redhat.com> <51C2E8ED.2000806@redhat.com> <1775080400.22416851.1371732785494.JavaMail.root@redhat.com> Message-ID: <51C302E0.8040104@redhat.com> On 06/20/2013 01:53 PM, Steve Gordon wrote: > ----- Original Message ----- >> From: "P?draig Brady" >> To: "Sandro \"red\" Mathys" >> Cc: rdo-list at redhat.com >> Sent: Thursday, June 20, 2013 7:35:09 AM >> Subject: Re: [Rdo-list] Why use yum priority in rdo-release repo file? >> >> On 06/20/2013 12:03 PM, P?draig Brady wrote: >>> On 06/20/2013 09:30 AM, Sandro "red" Mathys wrote: >>>> Even though RDO is supposed to always being ahead of RHEL and EPEL, it >>>> enforces a higher priority (lower priority=N) than the default. Why? >>> >>> So yes this is debatable. >>> y-p-p is used with the RHOS product to give precedence over EPEL. >>> I.E. even though EPEL is not required there, con existence is supported. >>> >>> Now RDO requires EPEL so again y-p-p gives us the flexibility for RDO to >>> override EPEL. >>> Now whether this is actually required at present is not obvious. >>> >>> We could retain the flexiblity while avoiding problems with y-p-p >>> by keeping the overlapping set as small as possible. >>> >>> wrt puppet, I'm not sure why it's there TBH. >>> EPEL has 2.6.18-3 while puppet-2.6.18-2 is in the RDO repo. >>> I've asked around a little and will probably just remove >>> puppet from the RDO repo, which will fix your immediate problem. >> >> So I found the reason that puppet was in RDO from the following commit. >> It was a temp workaround I made in the rush to get a working RDO out the >> door, >> and completely forgot about. Now the update in epel should fix this issue, >> so the plan above to remove puppet from RDO should work, and I've now done >> that. >> >> thanks, >> P?draig. > > If puppet is removed from the RDO repo will the Quick Start need to be updated to explicitly state the EPEL requirement (it does not at the moment)? Currently my understanding is users only need to explicitly enable/install the RDO repository, then PackStack (as you say) enables EPEL if it detects that you are on an EL system...I'm wondering if it is still able to do this without access to puppet from the RDO repository (chicken and egg situation)? > > If not then removing it would necessitate some updates to the instructions (not that this is necessarily a bad thing in and of itself, there are other issues with the Quick Start thanks to the introduction of Quantum support in PackStack but the page is locked to edits). Very good point. But the packstack package doesn't depend on puppet, and instead explicitly installs puppet after the appropriate repos are enabled. If it didn't do that, then rather than updating the docs, it would probably best to add the epel-release rpm to the RDO repo and have rdo-release depend on it. That would obviate the need for docs and packstack logic. Caveat with that is we'd then need separate rdo-release rpms for RHEL (derivatives) and Fedora. So I'm leaving as is until the need arises to change this. cheers, P?draig. From sgordon at redhat.com Thu Jun 20 12:53:05 2013 From: sgordon at redhat.com (Steve Gordon) Date: Thu, 20 Jun 2013 08:53:05 -0400 (EDT) Subject: [Rdo-list] Why use yum priority in rdo-release repo file? In-Reply-To: <51C2E8ED.2000806@redhat.com> References: <51C2E174.9060400@redhat.com> <51C2E8ED.2000806@redhat.com> Message-ID: <1775080400.22416851.1371732785494.JavaMail.root@redhat.com> ----- Original Message ----- > From: "P?draig Brady" > To: "Sandro \"red\" Mathys" > Cc: rdo-list at redhat.com > Sent: Thursday, June 20, 2013 7:35:09 AM > Subject: Re: [Rdo-list] Why use yum priority in rdo-release repo file? > > On 06/20/2013 12:03 PM, P?draig Brady wrote: > > On 06/20/2013 09:30 AM, Sandro "red" Mathys wrote: > >> Even though RDO is supposed to always being ahead of RHEL and EPEL, it > >> enforces a higher priority (lower priority=N) than the default. Why? > > > > So yes this is debatable. > > y-p-p is used with the RHOS product to give precedence over EPEL. > > I.E. even though EPEL is not required there, con existence is supported. > > > > Now RDO requires EPEL so again y-p-p gives us the flexibility for RDO to > > override EPEL. > > Now whether this is actually required at present is not obvious. > > > > We could retain the flexiblity while avoiding problems with y-p-p > > by keeping the overlapping set as small as possible. > > > > wrt puppet, I'm not sure why it's there TBH. > > EPEL has 2.6.18-3 while puppet-2.6.18-2 is in the RDO repo. > > I've asked around a little and will probably just remove > > puppet from the RDO repo, which will fix your immediate problem. > > So I found the reason that puppet was in RDO from the following commit. > It was a temp workaround I made in the rush to get a working RDO out the > door, > and completely forgot about. Now the update in epel should fix this issue, > so the plan above to remove puppet from RDO should work, and I've now done > that. > > thanks, > P?draig. If puppet is removed from the RDO repo will the Quick Start need to be updated to explicitly state the EPEL requirement (it does not at the moment)? Currently my understanding is users only need to explicitly enable/install the RDO repository, then PackStack (as you say) enables EPEL if it detects that you are on an EL system...I'm wondering if it is still able to do this without access to puppet from the RDO repository (chicken and egg situation)? If not then removing it would necessitate some updates to the instructions (not that this is necessarily a bad thing in and of itself, there are other issues with the Quick Start thanks to the introduction of Quantum support in PackStack but the page is locked to edits). Thanks, Steve From dneary at redhat.com Thu Jun 20 13:37:55 2013 From: dneary at redhat.com (Dave Neary) Date: Thu, 20 Jun 2013 15:37:55 +0200 Subject: [Rdo-list] securing services In-Reply-To: <51C1E610.9040302@redhat.com> References: <51C1E610.9040302@redhat.com> Message-ID: <51C305B3.20905@redhat.com> Hi, You might be interested in this presentation from Adam Young during the last OpenStack Summit - it addresses many of your questions, I think: https://www.youtube.com/watch?v=ueYUsYky_UI Cheers, Dave. On 06/19/2013 07:10 PM, Rob Crittenden wrote: > I'm looking at adding security to some of the system services using Red > Hat Identity Management (FreeIPA upstream). This is initially going to > be SSL for some, Kerberos for others. For a first round effort this > won't include using Kerberos to authenticate users to Keystone (a much > bigger hammer is needed for that). > > I'm looking at adding SSL to Apache and Kerberos to qpid. > > What about the database? I can add SSL to mysql and Kerberos to > postgres, should I support both? What is the preferred SQL database for > RHOS? > > rob > > _______________________________________________ > Rdo-list mailing list > Rdo-list at redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From rdo-info at redhat.com Thu Jun 20 14:50:22 2013 From: rdo-info at redhat.com (RDO Forum) Date: Thu, 20 Jun 2013 14:50:22 +0000 Subject: [Rdo-list] [RDO] ppyy started a discussion. Message-ID: <0000013f62109abc-8b15de97-cf8c-41e0-aba0-f820b70ba602-000000@email.amazonses.com> ppyy started a discussion. kernel 2.6.32-358.111.1 crashed --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/233/kernel-2-6-32-358-111-1-crashed Have a great day! From mrunge at redhat.com Thu Jun 20 15:01:52 2013 From: mrunge at redhat.com (Matthias Runge) Date: Thu, 20 Jun 2013 17:01:52 +0200 Subject: [Rdo-list] Why use yum priority in rdo-release repo file? In-Reply-To: References: <51C2E174.9060400@redhat.com> <51C2E8ED.2000806@redhat.com> <51C2EE0A.3050405@redhat.com> Message-ID: <51C31960.5030307@redhat.com> On 20/06/13 14:15, Sandro "red" Mathys wrote: > On Thu, Jun 20, 2013 at 1:56 PM, Matthias Runge > wrote: > > On 20/06/13 13:50, Sandro "red" Mathys wrote: > > Great, thanks for the quick reply and the quick fix. Still thinking > > yum priorities are bad and should be removed completely from RDO > > (RHOS is a different story) but if only directly openstack related > > packages remain in the repo, it shouldn't matter anyway. -- Sandro > > > Why do you think priorities are bad? > > > Because they are patronizing the user, relatively hard to overcome and > situations where they seem necessary should be avoided in general. > Yum does not resolve dependencies very well, when it comes to ambiguities. Simple example: we're using Django14 in RDO, whereas EPEL has both, and the same versions. yum prioritizes packages with shorter names, thus would install Django instead of Django14. (version 1.3 vs. 1.4). Other example: You could have a version of a software which is just a plain "community" version, whereas you could have in RDO a more "supported" version, e.g expressed by other logos etc, but still the same package version. > > Like in what case? When will RDO ever want an older version of something > than what is in RHEL / EPEL? Good question: what will be priorized? Higher prio repo or higher package version? > > The only thing I can possibly come up with right now are the kernel and > other tools where new networking stuff (netns, maybe more) was enabled > ahead of time but I sure hope those changes make it back into RHEL with > the next kernel update there. Or if not, that new RHEL kernels are again > re-built with those patches for RDO as well to avoid security holes. Good to see, you have found a use-case. Matthias From mail-lists at karan.org Thu Jun 20 15:06:33 2013 From: mail-lists at karan.org (Karanbir Singh) Date: Thu, 20 Jun 2013 16:06:33 +0100 Subject: [Rdo-list] Why use yum priority in rdo-release repo file? In-Reply-To: <51C31960.5030307@redhat.com> References: <51C2E174.9060400@redhat.com> <51C2E8ED.2000806@redhat.com> <51C2EE0A.3050405@redhat.com> <51C31960.5030307@redhat.com> Message-ID: <51C31A79.6060205@karan.org> On 06/20/2013 04:01 PM, Matthias Runge wrote: > Simple example: we're using Django14 in RDO, whereas EPEL has both, and > the same versions. > > yum prioritizes packages with shorter names, thus would install Django > instead of Django14. (version 1.3 vs. 1.4). > This looks like a bad Requires: line in the RDO packaging. Yum wont install Django 1.3 when your baseline Requires: >= 1.4 and Django14 should provide Django = 1.4 priorities are harsh in the way it handles and removes stuff from the pkgsack, but dont blame it for bad packaging. - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From rcritten at redhat.com Thu Jun 20 15:22:06 2013 From: rcritten at redhat.com (Rob Crittenden) Date: Thu, 20 Jun 2013 11:22:06 -0400 Subject: [Rdo-list] securing services In-Reply-To: <51C305B3.20905@redhat.com> References: <51C1E610.9040302@redhat.com> <51C305B3.20905@redhat.com> Message-ID: <51C31E1E.50204@redhat.com> Dave Neary wrote: > Hi, > > You might be interested in this presentation from Adam Young during the > last OpenStack Summit - it addresses many of your questions, I think: > https://www.youtube.com/watch?v=ueYUsYky_UI I've seen it, thanks. My question was really postgres vs mysql. It seem that most Fedora Openstack docs recommend using postgres and yet most upstream and RDO use mysql, so I was just trying to target my initial efforts appropriately. I think Adam would prefer I work on postgres first. The ultimate goal is to come up with some puppet scripts that can be run after enrolling an Openstack host into IPA that will secure its services. This is going to be fairly simple in the one-host environment I'm starting on, more complex when services are running on separate machines. This will be my first foray into puppet. thanks rob > > Cheers, > Dave. > > On 06/19/2013 07:10 PM, Rob Crittenden wrote: >> I'm looking at adding security to some of the system services using Red >> Hat Identity Management (FreeIPA upstream). This is initially going to >> be SSL for some, Kerberos for others. For a first round effort this >> won't include using Kerberos to authenticate users to Keystone (a much >> bigger hammer is needed for that). >> >> I'm looking at adding SSL to Apache and Kerberos to qpid. >> >> What about the database? I can add SSL to mysql and Kerberos to >> postgres, should I support both? What is the preferred SQL database for >> RHOS? >> >> rob >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list > From red at fedoraproject.org Thu Jun 20 15:23:52 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Thu, 20 Jun 2013 17:23:52 +0200 Subject: [Rdo-list] Why use yum priority in rdo-release repo file? In-Reply-To: <51C31960.5030307@redhat.com> References: <51C2E174.9060400@redhat.com> <51C2E8ED.2000806@redhat.com> <51C2EE0A.3050405@redhat.com> <51C31960.5030307@redhat.com> Message-ID: On Thu, Jun 20, 2013 at 5:01 PM, Matthias Runge wrote: > On 20/06/13 14:15, Sandro "red" Mathys wrote: > > On Thu, Jun 20, 2013 at 1:56 PM, Matthias Runge > > wrote: > > > > On 20/06/13 13:50, Sandro "red" Mathys wrote: > > > Great, thanks for the quick reply and the quick fix. Still thinking > > > yum priorities are bad and should be removed completely from RDO > > > (RHOS is a different story) but if only directly openstack related > > > packages remain in the repo, it shouldn't matter anyway. -- Sandro > > > > > Why do you think priorities are bad? > > > > > > Because they are patronizing the user, relatively hard to overcome and > > situations where they seem necessary should be avoided in general. > > > Yum does not resolve dependencies very well, when it comes to ambiguities. > True. If there are ambiguities which is to be avoided (as said before). > Simple example: we're using Django14 in RDO, whereas EPEL has both, and > the same versions. > > yum prioritizes packages with shorter names, thus would install Django > instead of Django14. (version 1.3 vs. 1.4). > Yum itself does not prioritize anything based on package names. If you install django, it will install django. If you install django14, it will install django14. Doesn't matter to yum whether django is 1.3, 1.4 or 1.5 in either case. ...unless you Require django and hope django14 does Provide django and that that's good enough. It isn't. Requiring something like django >= 1.4 should be in that case, though. Other example: You could have a version of a software which is just a > plain "community" version, whereas you could have in RDO a more > "supported" version, e.g expressed by other logos etc, but still the > same package version. > You could do a lot of things, but lets stick to actual use cases. Even if you change the logo, openstack-horizon in RDO should still be newer than the one in EPEL. > > > > Like in what case? When will RDO ever want an older version of something > > than what is in RHEL / EPEL? > > Good question: what will be priorized? Higher prio repo or higher > package version? > Well, that's the point of y-p-p: only the higher repo prio counts. Like the case I mentioned before. RDO had Puppet 2.6 and puppetlabs Puppet 3.2. Puppet from RDO, having a higher repo prio than default, would always win. > > The only thing I can possibly come up with right now are the kernel and > > other tools where new networking stuff (netns, maybe more) was enabled > > ahead of time but I sure hope those changes make it back into RHEL with > > the next kernel update there. Or if not, that new RHEL kernels are again > > re-built with those patches for RDO as well to avoid security holes. > > Good to see, you have found a use-case. > And I also explained why the use case must be discarded. -- Sandro -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbryant at redhat.com Thu Jun 20 17:19:26 2013 From: rbryant at redhat.com (Russell Bryant) Date: Thu, 20 Jun 2013 13:19:26 -0400 Subject: [Rdo-list] Suggestion: Notify this list of new forum threads In-Reply-To: <51C1890B.1020807@redhat.com> References: <51BF0FF6.6060506@redhat.com> <51BF1621.6030504@redhat.com> <51C015E5.9090101@redhat.com> <51C1890B.1020807@redhat.com> Message-ID: <51C3399E.6050701@redhat.com> On 06/19/2013 06:33 AM, Dave Neary wrote: > Hi, > > Threading on topics would be awesome. Vanilla doesn't do it right now, > but I'll open a ticket for it. Threading would be nice, too, but: > On 06/19/2013 09:50 AM, Sandro "red" Mathys wrote: >> Is it somehow possible to reflect the thread topic in the subject, >> though? Lots of mails that just say "s.o. commented on a discussion" are >> most likely just being ignored (if not considered spam). This suggestion of just a different subject that matches the forum topic would be *really* useful. Otherwise, you can't scan subjects for important or relevant topics that you might want to look deeper into. -- Russell Bryant From rohara at redhat.com Thu Jun 20 18:32:11 2013 From: rohara at redhat.com (Ryan O'Hara) Date: Thu, 20 Jun 2013 13:32:11 -0500 Subject: [Rdo-list] Multiple quantum API servers Message-ID: <20130620183211.GA1104@redhat.com> I've been told on more than one occasion that it is not possible to have multiple quantum API servers (active/active). Is this true? If so, what is the cause of this limitation? The other API services do not have such a limitation AFAIK. Ryan From red at fedoraproject.org Thu Jun 20 19:44:40 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Thu, 20 Jun 2013 21:44:40 +0200 Subject: [Rdo-list] [For testing] Fedora 19 (Test Compose) cloud images In-Reply-To: <20130618144313.GA5496@disco.bu.edu> References: <51BFF5B3.80305@redhat.com> <51C018E9.5030109@redhat.com> <20130618144313.GA5496@disco.bu.edu> Message-ID: There's a new F19 test compose available, Final TC6, which should have a working fix for the previously mentioned (SELinux related) bug. Also, I think there's currently no other bug known to affect the cloud image (directly). So please report any bugs you find immediately (best to open a bug and send us the rhbz#). https://dl.fedoraproject.org/pub/alt/stage/19-TC6/Images/ -- Sandro On Tue, Jun 18, 2013 at 4:43 PM, Matthew Miller wrote: > On Tue, Jun 18, 2013 at 01:53:05PM +0530, Kashyap Chamarthy wrote: > > >> https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/ > > > Nice! Do we know what kickstart file and what version of it they are > > > compiled with? > > Not sure. But yes - the above directory should also contain its > kickstart file it's > > created with. > > It should mostly be this: > > > https://git.fedorahosted.org/cgit/cloud-kickstarts.git/tree/generic/fedora-19-x86_64-cloud.ks > > Dennis Gilmore/Matthew Miller might confirm(CC'ed them). > > Yep, confirmed. Dennis sometimes makes minor tweaks required to get the > somewhat arcane buildsystem to work -- part of the process verifies the > kickstart files under RHEL 6, so the kickstart needs to parse as valid for > both the current kickstart _and_ for that release. > > > > --disk-format qcow2 --container-format bare --copy-from \ > > > > https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/x86_64/Fedora-x86_64-19-TC5-20130617-sda.qcow2 > > > ...the downside being that you can't verify the checksum between > > > downloading the image and pushing it into glance. > > Nice, thank you. > > Feedback appreciated! Because of an outstanding bug with SE Linux and > cloud-init, there will be a one-minute delay before you can log in unless > you boot with user-data like this: > > #cloud-config > cloud_init_modules: > - bootcmd > - write-files > - growpart > - resizefs > - rsyslog > - users-groups > - ssh > > > -- > Matthew Miller ??? Fedora Cloud Architect ??? < > mattdm at fedoraproject.org> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rdo-info at redhat.com Fri Jun 21 00:01:48 2013 From: rdo-info at redhat.com (RDO Forum) Date: Fri, 21 Jun 2013 00:01:48 +0000 Subject: [Rdo-list] [RDO] mattdm started a discussion. Message-ID: <0000013f640974c1-9ed926a6-8a9c-453e-aeae-76f37d334891-000000@email.amazonses.com> mattdm started a discussion. Fedora 19 TC6 guest images now available!f --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/234/fedora-19-tc6-guest-images-now-availablef Have a great day! From kchamart at redhat.com Fri Jun 21 04:55:10 2013 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Fri, 21 Jun 2013 10:25:10 +0530 Subject: [Rdo-list] [For testing] Fedora 19 (Test Compose) cloud images In-Reply-To: References: <51BFF5B3.80305@redhat.com> <51C018E9.5030109@redhat.com> <20130618144313.GA5496@disco.bu.edu> Message-ID: <51C3DCAE.6080101@redhat.com> On 06/21/2013 01:14 AM, Sandro "red" Mathys wrote: > There's a new F19 test compose available, Final TC6, which should have a > working fix for the previously mentioned (SELinux related) bug. Also, I > think there's currently no other bug known to affect the cloud image > (directly). So please report any bugs you find immediately (best to open a > bug and send us the rhbz#). > > https://dl.fedoraproject.org/pub/alt/stage/19-TC6/Images/ > Heya, thanks for the pointer. Just a friendly note - for new composes like these, better to write a new email (folks might not be following old threads). Thanks. -- /kashyap From mrunge at redhat.com Fri Jun 21 06:38:59 2013 From: mrunge at redhat.com (Matthias Runge) Date: Fri, 21 Jun 2013 08:38:59 +0200 Subject: [Rdo-list] Why use yum priority in rdo-release repo file? In-Reply-To: <51C31A79.6060205@karan.org> References: <51C2E174.9060400@redhat.com> <51C2E8ED.2000806@redhat.com> <51C2EE0A.3050405@redhat.com> <51C31960.5030307@redhat.com> <51C31A79.6060205@karan.org> Message-ID: <51C3F503.2050708@redhat.com> On 20/06/13 17:06, Karanbir Singh wrote: >> >> yum prioritizes packages with shorter names, thus would install >> Django instead of Django14. (version 1.3 vs. 1.4). >> > > This looks like a bad Requires: line in the RDO packaging. Yum wont > install Django 1.3 when your baseline Requires: >= 1.4 and Django14 > should provide Django = 1.4 > No. Django14 provides: Provides: Django = %{version}-%{release} Horizon requires %if 0%{?rhel}==6 Requires: Django14 So, it is like you requested. The problem here is: Horizon requires e.g python-django-compressor, which also works on Django 1.3. So you just can put there requires: Django, when requiring there Django14 or Django >= 1.4, you'll break other installations. In this case, yum tries to install both, Django14 and Django, which produces a conflict. Having both, does not make sense at all. So, parallel installable versions don't help here. Matthias From rdo-info at redhat.com Fri Jun 21 07:49:04 2013 From: rdo-info at redhat.com (RDO Forum) Date: Fri, 21 Jun 2013 07:49:04 +0000 Subject: [Rdo-list] [RDO] Lashik started a discussion. Message-ID: <0000013f65b53d7b-20d409a4-0792-43c4-aa67-512f80f2774e-000000@email.amazonses.com> Lashik started a discussion. CEPH in production --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/235/ceph-in-production Have a great day! From rdo-info at redhat.com Fri Jun 21 08:50:20 2013 From: rdo-info at redhat.com (RDO Forum) Date: Fri, 21 Jun 2013 08:50:20 +0000 Subject: [Rdo-list] [RDO] iLikeIT started a discussion. Message-ID: <0000013f65ed572a-d60301d2-2cd6-40e4-b598-ea7f478b7206-000000@email.amazonses.com> iLikeIT started a discussion. How to Setup Networking for single node installation with 3 NICs --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/236/how-to-setup-networking-for-single-node-installation-with-3-nics Have a great day! From rdo-info at redhat.com Fri Jun 21 08:53:29 2013 From: rdo-info at redhat.com (RDO Forum) Date: Fri, 21 Jun 2013 08:53:29 +0000 Subject: [Rdo-list] [RDO] iLikeIT started a discussion. Message-ID: <0000013f65f03a5e-74e950eb-7b8a-40db-9f72-8841a2f60641-000000@email.amazonses.com> iLikeIT started a discussion. How to Setup NFS Storage to store all Instances and templates --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/237/how-to-setup-nfs-storage-to-store-all-instances-and-templates Have a great day! From nearyd at gmail.com Fri Jun 21 09:14:33 2013 From: nearyd at gmail.com (Dave Neary) Date: Fri, 21 Jun 2013 11:14:33 +0200 Subject: [Rdo-list] Fwd: RDO installation In-Reply-To: References: Message-ID: <51C41979.7020901@gmail.com> Hi Ahmed, I can't really answer questions through personal email - not only because it doesn't scale, but because your email is going to get lost, and also because (as in this case) I often don't know the answer. Theer are many experts on rdo-list (CCed) and on the forum. I suggest you ask your question there. Thanks, Dave. -------- Original Message -------- Subject: RDO installation Date: Thu, 20 Jun 2013 16:31:31 +0200 From: ahmed ali To: nearyd at gmail.com Hi dneary , I want your help , while installing RDO openstack this error appear can you help me please .Inline image 1 -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled.png Type: image/png Size: 18132 bytes Desc: not available URL: From kchamart at redhat.com Fri Jun 21 12:14:02 2013 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Fri, 21 Jun 2013 17:44:02 +0530 Subject: [Rdo-list] Notes for setting up NFS share to store nova instances Message-ID: <51C4438A.9080308@redhat.com> Heya, I just saw a question on RDO forum related to $subject. Just posting some notes here, as this was in my drafts anyhow. (Will point a link to this on the Forum. Also, thanks to Giulio Fidente for reminding me on the qemu.conf bit below). NFS share to store nova instances --------------------------------- If you have an NFS share to store images, you could add it the below way. The default location where instances are stored -- `/var/lib/nova/instances` First, on the NFS server side : $ cat /etc/exports /home/kashyap *(rw,syn,no_root_squash) Mount an nfs share w/ nova specific SELinux context : $ mount --verbose -t nfs xx.yy.www.zzz:/home/kashyap \ /mnt -o "context=unconfined_u:object_r:nova_var_lib_t:s0" # Set correct permissions on mount point $ chown -R nova: /mnt/nova/ $ chgrp -R qemu /mnt/nova/instances/ $ chmod -R g+w /mnt/nova/instances Ensure to have nova own the QEMU instances invoked by : $ grep nova /etc/libvirt/qemu.conf user = "nova" group = "nova" Restart all 'running' OpenStack services : $ for j in `for i in $(ls -1 /etc/init.d/openstack-*) ; \ do $i status | grep running ; done | awk '{print $1}'`; \ do service $j restart ; done Later, ensure, your instances are indeed owned by nova :: $ ps -ef | grep -i qemu-kvm | grep -i nova -- /kashyap From rdo-info at redhat.com Fri Jun 21 12:57:28 2013 From: rdo-info at redhat.com (RDO Forum) Date: Fri, 21 Jun 2013 12:57:28 +0000 Subject: [Rdo-list] [RDO] PT_C started a discussion. Message-ID: <0000013f66cf97b8-d155e140-a761-4fa2-bd1f-b8a97ece7967-000000@email.amazonses.com> PT_C started a discussion. Error during packstack install --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/239/error-during-packstack-install Have a great day! From pmyers at redhat.com Fri Jun 21 13:16:52 2013 From: pmyers at redhat.com (Perry Myers) Date: Fri, 21 Jun 2013 09:16:52 -0400 Subject: [Rdo-list] Fwd: RDO installation In-Reply-To: <51C41979.7020901@gmail.com> References: <51C41979.7020901@gmail.com> Message-ID: <51C45244.400@redhat.com> On 06/21/2013 05:14 AM, Dave Neary wrote: > Hi Ahmed, > > I can't really answer questions through personal email - not only > because it doesn't scale, but because your email is going to get lost, > and also because (as in this case) I often don't know the answer. > > Theer are many experts on rdo-list (CCed) and on the forum. I suggest > you ask your question there. Thanks Dave for taking this to list :) > Hi dneary , > I want your help , while installing RDO openstack this error appear can > you help me please .Inline image 1 Hi Ahmed, It's difficult to tell what the issue might be with just that screen shot snippet, but it looks like it failed on checking for netns support? Can you provide more detail about what your base os is, what channels you have enabled, etc? And if you can provide the logs that would be good too (there are likely more details in logs like openstack-setup.log as mentioned in the packstack output) Perry From rbowen at redhat.com Fri Jun 21 13:17:02 2013 From: rbowen at redhat.com (Rich Bowen) Date: Fri, 21 Jun 2013 09:17:02 -0400 Subject: [Rdo-list] RDO forum unanswered posts Message-ID: <51C4524E.2080107@redhat.com> Hi, folks. I was hoping to solicit some help in addressing several posts on the RDO forum that have been unanswered for some time. (There's more than these, but these are the oldest ten. I didn't want to overwhelm you with my first post.) Over the coming weeks I'm going to be trying to get us all caught up, and then provide a weekly "unanswered posts" report. Could you please take a look and see if any of these posts are in your area of expertise, or if perhaps they're about something that has already been addressed. Thanks! ========================================== SPICE support in RDO Grizzly (2013-04-27) : http://openstack.redhat.com/forum/discussion/67 Is there any way that I can use vncviewer to access instance instead of noVnc in web? (2013-04-29) : http://openstack.redhat.com/forum/discussion/73 Whether support spices? (2013-05-06) : http://openstack.redhat.com/forum/discussion/92 Create server returns 404 (2013-05-07) : http://openstack.redhat.com/forum/discussion/96 Quantum startup script packaging on FC18 (2013-05-08) : http://openstack.redhat.com/forum/discussion/105 live migration & block migration (2013-05-12) : http://openstack.redhat.com/forum/discussion/108 Error with instances with volumes after reboot (2013-05-12) : http://openstack.redhat.com/forum/discussion/110 RDO + non Fixed IPs (2013-05-13) : http://openstack.redhat.com/forum/discussion/112 packstack install - keystone : 'NoneType' object is unsubscriptable (2013-05-13) : http://openstack.redhat.com/forum/discussion/113 AoE + Cinder Setup? (2013-05-14) : http://openstack.redhat.com/forum/discussion/117 -- Rich Bowen RDO Community Liaison http://openstack.redhat.com/ From pmyers at redhat.com Fri Jun 21 13:28:51 2013 From: pmyers at redhat.com (Perry Myers) Date: Fri, 21 Jun 2013 09:28:51 -0400 Subject: [Rdo-list] RDO forum unanswered posts In-Reply-To: <51C4524E.2080107@redhat.com> References: <51C4524E.2080107@redhat.com> Message-ID: <51C45513.4000508@redhat.com> On 06/21/2013 09:17 AM, Rich Bowen wrote: > Hi, folks. I was hoping to solicit some help in addressing several posts > on the RDO forum that have been unanswered for some time. (There's more > than these, but these are the oldest ten. I didn't want to overwhelm you > with my first post.) > > Over the coming weeks I'm going to be trying to get us all caught up, > and then provide a weekly "unanswered posts" report. > > Could you please take a look and see if any of these posts are in your > area of expertise, or if perhaps they're about something that has > already been addressed. > > Thanks! > > ========================================== > > > SPICE support in RDO Grizzly (2013-04-27) : > http://openstack.redhat.com/forum/discussion/67 > > Is there any way that I can use vncviewer to access instance instead of > noVnc in web? (2013-04-29) : > http://openstack.redhat.com/forum/discussion/73 > > Whether support spices? (2013-05-06) : > http://openstack.redhat.com/forum/discussion/92 danpb, can you address the above three questions? > Create server returns 404 (2013-05-07) : > http://openstack.redhat.com/forum/discussion/96 russell? > Quantum startup script packaging on FC18 (2013-05-08) : > http://openstack.redhat.com/forum/discussion/105 twilson or someone else on the quantum team? > live migration & block migration (2013-05-12) : > http://openstack.redhat.com/forum/discussion/108 ndipanov? > Error with instances with volumes after reboot (2013-05-12) : > http://openstack.redhat.com/forum/discussion/110 eharney? > RDO + non Fixed IPs (2013-05-13) : > http://openstack.redhat.com/forum/discussion/112 beagles? > packstack install - keystone : 'NoneType' object is unsubscriptable > (2013-05-13) : http://openstack.redhat.com/forum/discussion/113 mmagr? > AoE + Cinder Setup? (2013-05-14) : > http://openstack.redhat.com/forum/discussion/117 eharney? From rdo-info at redhat.com Fri Jun 21 12:31:19 2013 From: rdo-info at redhat.com (RDO Forum) Date: Fri, 21 Jun 2013 12:31:19 +0000 Subject: [Rdo-list] [RDO] PT_C started a discussion. Message-ID: <0000013f66b7a75d-e3555aab-b7d4-437b-b6bb-e404a6fed09d-000000@email.amazonses.com> PT_C started a discussion. Install error with Nagios --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/238/install-error-with-nagios Have a great day! From nearyd at gmail.com Fri Jun 21 16:19:53 2013 From: nearyd at gmail.com (Dave Neary) Date: Fri, 21 Jun 2013 18:19:53 +0200 Subject: [Rdo-list] Fwd: RDO installation In-Reply-To: <51C45244.400@redhat.com> References: <51C41979.7020901@gmail.com> <51C45244.400@redhat.com> Message-ID: <51C47D29.60503@gmail.com> Hi, Actually, I think this is a duplicate of http://openstack.redhat.com/forum/discussion/224/timeout-on-x86_64-centos-release-6-4 Cheers, Dave. On 06/21/2013 03:16 PM, Perry Myers wrote: > On 06/21/2013 05:14 AM, Dave Neary wrote: >> Hi Ahmed, >> >> I can't really answer questions through personal email - not only >> because it doesn't scale, but because your email is going to get lost, >> and also because (as in this case) I often don't know the answer. >> >> Theer are many experts on rdo-list (CCed) and on the forum. I suggest >> you ask your question there. > > Thanks Dave for taking this to list :) > >> Hi dneary , >> I want your help , while installing RDO openstack this error appear can >> you help me please .Inline image 1 > > Hi Ahmed, > > It's difficult to tell what the issue might be with just that screen > shot snippet, but it looks like it failed on checking for netns support? > > Can you provide more detail about what your base os is, what channels > you have enabled, etc? > > And if you can provide the logs that would be good too (there are likely > more details in logs like openstack-setup.log as mentioned in the > packstack output) > > Perry > -- Dave Neary, Lyon, France Email: dneary at gnome.org / Jabber: nearyd at gmail.com Ph: +33 950 71 55 62 / Cell: +33 6 77 01 92 13 From rdo-info at redhat.com Sat Jun 22 09:31:51 2013 From: rdo-info at redhat.com (RDO Forum) Date: Sat, 22 Jun 2013 09:31:51 +0000 Subject: [Rdo-list] [RDO] ramil_kh started a discussion. Message-ID: <0000013f6b39b435-cde972a2-1de3-45d1-ae3c-d2e8461b9219-000000@email.amazonses.com> ramil_kh started a discussion. RDO fails to install since yesterday. RHEL 6.4 and Fedora. --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/240/rdo-fails-to-install-since-yesterday-rhel-6-4-and-fedora- Have a great day! From rdo-info at redhat.com Sun Jun 23 11:51:11 2013 From: rdo-info at redhat.com (RDO Forum) Date: Sun, 23 Jun 2013 11:51:11 +0000 Subject: [Rdo-list] [RDO] silentaug started a discussion. Message-ID: <0000013f70dfa105-fc21702a-f5dc-40c9-ad19-5d22f0e7efa4-000000@email.amazonses.com> silentaug started a discussion. what hardware are people running RDO on for home lab? --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/241/what-hardware-are-people-running-rdo-on-for-home-lab Have a great day! From rdo-info at redhat.com Mon Jun 24 04:22:20 2013 From: rdo-info at redhat.com (RDO Forum) Date: Mon, 24 Jun 2013 04:22:20 +0000 Subject: [Rdo-list] [RDO] ggillies started a discussion. Message-ID: <0000013f746b0d9e-c6994f7c-78f9-4799-90f9-77ed74187357-000000@email.amazonses.com> ggillies started a discussion. nova.conf compute_driver setting --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/242/nova-conf-compute_driver-setting Have a great day! From pmyers at redhat.com Mon Jun 24 16:44:55 2013 From: pmyers at redhat.com (Perry Myers) Date: Mon, 24 Jun 2013 12:44:55 -0400 Subject: [Rdo-list] RDO installation failed on keystone In-Reply-To: <948884155.2599840.1372089428790.JavaMail.root@redhat.com> References: <948884155.2599840.1372089428790.JavaMail.root@redhat.com> Message-ID: <51C87787.2080506@redhat.com> (moving thread to rdo-list) On 06/24/2013 11:57 AM, Tal Kammer wrote: > I just tried to install a fresh copy of the RDO on a machine using packstack (followed: http://openstack.redhat.com/Quickstart) when it failed on the keystone component saying that there is a dependency issue with python-sqlalchemy. > After checking the subject, it seems that the repo has sqlalchemy version 0.5 where the keystone component requires version 0.7+ > > Can someone confirm this? > > (to reproduce this, just follow the installation procedure on the link above) EPEL should have sqlalchemy 0.7 as far as I can see: http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/python-sqlalchemy0.7.html What repos do you have enabled on your RDO install machine? Base RHEL does indeed have an older version of sqlalchemy, which is why RHOS repos contain a newer version and RDO requires EPEL version of the package > python-sqlalchemy.noarch 0.5.5-3.el6_2 rhel-released > python-sqlalchemy0.7.x86_64 0.7.8-1.el6 epel > python-sqlalchemy0.7.x86_64 0.7.8-1.el6ost rhos3 Perry From rdo-info at redhat.com Mon Jun 24 20:04:01 2013 From: rdo-info at redhat.com (RDO Forum) Date: Mon, 24 Jun 2013 20:04:01 +0000 Subject: [Rdo-list] [RDO] ptc61891 started a discussion. Message-ID: <0000013f77c931cf-be9de0b1-c372-41f2-b961-091536428c9b-000000@email.amazonses.com> ptc61891 started a discussion. Creating first instance --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/243/creating-first-instance Have a great day! From red at fedoraproject.org Tue Jun 25 14:00:17 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Tue, 25 Jun 2013 16:00:17 +0200 Subject: [Rdo-list] FYI: F19 RC1 cloud images available in EC2 and for download Message-ID: So as you can see below, the first release candidate for the F19 cloud images is ready to be tested. To make F19 RC1 available in your OpenStack, simply do something like: glance image-create --name "Fedora 19 RC1" --disk-format qcow2 --container-format bare --is-public true --copy-from https://dl.fedoraproject.org/pub/alt/stage/19-RC1/Images/x86_64/Fedora-x86_64-19-20130624-sda.qcow2 -- Sandro ---------- Forwarded message ---------- From: Matthew Miller Date: Tue, Jun 25, 2013 at 3:41 PM Subject: [Test-Announce] F19 RC1 cloud images available in EC2 and for download To: test-announce at lists.fedoraproject.org Fedora 19 Release Candidate 1 cloud images are now available from: http://dl.fedoraproject.org/pub/alt/stage/19-RC1/Images/ in either qcow2 or raw.xz format. You should be able to use Glance in OpenStack to just import the qcow2 images directly and go. They're also in Amazon EC2 in the US East region (us-east-1): ami-79196a10 for x86_64 ami-ef1b6886 for i386 Thanks to Dennis Gilmore in Fedora Release Engineering for the extra work to make this happen. The images are configured with "fedora" as the default user with passwordless sudo. You can change this behavior by passing different configuration data via the user-data in either OpenStack or EC2. For example, to allow direct root login and to suppress the creation of the 'fedora' user, use #cloud-config users: disable_root: 0 (The first line is identifying the userdata type, not a comment.) -- Matthew Miller ??? Fedora Cloud Architect ??? _______________________________________________ test-announce mailing list test-announce at lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Tue Jun 25 14:51:33 2013 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 25 Jun 2013 10:51:33 -0400 Subject: [Rdo-list] RDO forum unanswered posts In-Reply-To: <51C4524E.2080107@redhat.com> References: <51C4524E.2080107@redhat.com> Message-ID: <51C9AE75.8020101@redhat.com> On 06/21/2013 09:17 AM, Rich Bowen wrote: > Hi, folks. I was hoping to solicit some help in addressing several > posts on the RDO forum that have been unanswered for some time. ... Thank you all so much for your help in addressing the unanswered posts on the RDO forum. I've put an "unanswered posts" page up at http://openstack.redhat.com/forum/unanswered.php that'll show the full list on demand, for those of you who are inclined to bookmark that and check it every day. Thanks again. -- Rich Bowen OpenStack Community Liaison http://openstack.redhat.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rdo-info at redhat.com Tue Jun 25 14:53:30 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 25 Jun 2013 14:53:30 +0000 Subject: [Rdo-list] [RDO] mattdm started a discussion. Message-ID: <0000013f7bd3432b-525c65a6-1201-4375-ad7e-cd9379ab2810-000000@email.amazonses.com> mattdm started a discussion. Fedora 19 Release Candidate 1 images now available --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/244/fedora-19-release-candidate-1-images-now-available Have a great day! From pmyers at redhat.com Tue Jun 25 15:02:05 2013 From: pmyers at redhat.com (Perry Myers) Date: Tue, 25 Jun 2013 11:02:05 -0400 Subject: [Rdo-list] RDO forum unanswered posts In-Reply-To: <51C9AE75.8020101@redhat.com> References: <51C4524E.2080107@redhat.com> <51C9AE75.8020101@redhat.com> Message-ID: <51C9B0ED.6090207@redhat.com> On 06/25/2013 10:51 AM, Rich Bowen wrote: > On 06/21/2013 09:17 AM, Rich Bowen wrote: >> Hi, folks. I was hoping to solicit some help in addressing several >> posts on the RDO forum that have been unanswered for some time. > ... > > Thank you all so much for your help in addressing the unanswered posts > on the RDO forum. > > I've put an "unanswered posts" page up at > http://openstack.redhat.com/forum/unanswered.php that'll show the full > list on demand, for those of you who are inclined to bookmark that and > check it every day. Likewise, any chance we could get an 'unresolved' list? That way we could see posts that have been answered (at least once) but are still pending some resolution? Cheers, Perry From dneary at redhat.com Tue Jun 25 15:32:28 2013 From: dneary at redhat.com (Dave Neary) Date: Tue, 25 Jun 2013 17:32:28 +0200 Subject: [Rdo-list] RDO forum unanswered posts In-Reply-To: <51C9B0ED.6090207@redhat.com> References: <51C4524E.2080107@redhat.com> <51C9AE75.8020101@redhat.com> <51C9B0ED.6090207@redhat.com> Message-ID: <51C9B80C.7080500@redhat.com> Hi, On 06/25/2013 05:02 PM, Perry Myers wrote: > Likewise, any chance we could get an 'unresolved' list? That way we > could see posts that have been answered (at least once) but are still > pending some resolution? Marking discussions "RESOLVED" in the title, or with a resolved label, has not scaled. I don't know how else to measure whether a thread is resolved or not. Are you suggesting we retroactively resolve all the threads which have been resolved to date? There are a great many where the original poster hasn't let us know one way or another. Thanks, Dave. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From pmyers at redhat.com Tue Jun 25 16:55:00 2013 From: pmyers at redhat.com (Perry Myers) Date: Tue, 25 Jun 2013 12:55:00 -0400 Subject: [Rdo-list] RDO forum unanswered posts In-Reply-To: <51C9B80C.7080500@redhat.com> References: <51C4524E.2080107@redhat.com> <51C9AE75.8020101@redhat.com> <51C9B0ED.6090207@redhat.com> <51C9B80C.7080500@redhat.com> Message-ID: <51C9CB64.2000105@redhat.com> On 06/25/2013 11:32 AM, Dave Neary wrote: > Hi, > > On 06/25/2013 05:02 PM, Perry Myers wrote: >> Likewise, any chance we could get an 'unresolved' list? That way we >> could see posts that have been answered (at least once) but are still >> pending some resolution? > > Marking discussions "RESOLVED" in the title, or with a resolved label, > has not scaled. I don't know how else to measure whether a thread is > resolved or not. Are you suggesting we retroactively resolve all the > threads which have been resolved to date? There are a great many where > the original poster hasn't let us know one way or another. Not sure how to handle this. Same problem exists with email threads I suppose. :) From rbowen at redhat.com Tue Jun 25 17:34:35 2013 From: rbowen at redhat.com (Rich Bowen) Date: Tue, 25 Jun 2013 13:34:35 -0400 Subject: [Rdo-list] RDO forum unanswered posts In-Reply-To: <51C9B80C.7080500@redhat.com> References: <51C4524E.2080107@redhat.com> <51C9AE75.8020101@redhat.com> <51C9B0ED.6090207@redhat.com> <51C9B80C.7080500@redhat.com> Message-ID: <51C9D4AB.1050406@redhat.com> On 06/25/2013 11:32 AM, Dave Neary wrote: > Hi, > > On 06/25/2013 05:02 PM, Perry Myers wrote: >> Likewise, any chance we could get an 'unresolved' list? That way we >> could see posts that have been answered (at least once) but are still >> pending some resolution? > Marking discussions "RESOLVED" in the title, or with a resolved label, > has not scaled. I don't know how else to measure whether a thread is > resolved or not. Are you suggesting we retroactively resolve all the > threads which have been resolved to date? There are a great many where > the original poster hasn't let us know one way or another. Yeah, I wanted to do something like that, but there's simply no reliable way to tell whether a given post has reached resolution. There's also a lot of posts that have had a response, but no answer. Like, the response was a 'me too' or was a 'is anyone out there', and now it doesn't show up in the 'unanswered' query. So, this is a very rough estimate. -- Rich Bowen OpenStack Community Liaison http://openstack.redhat.com/ From rdo-info at redhat.com Tue Jun 25 18:46:42 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 25 Jun 2013 18:46:42 +0000 Subject: [Rdo-list] [RDO] PT_C started a discussion. Message-ID: <0000013f7ca8c4e8-c4fe8600-7845-4068-8619-d304db32f7f3-000000@email.amazonses.com> PT_C started a discussion. Nova Credentials --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/245/nova-credentials Have a great day! From rdo-info at redhat.com Tue Jun 25 18:54:23 2013 From: rdo-info at redhat.com (RDO Forum) Date: Tue, 25 Jun 2013 18:54:23 +0000 Subject: [Rdo-list] [RDO] A_V started a discussion. Message-ID: <0000013f7cafcc1b-31117d4a-c181-4cdc-a8d1-3d1ce1fd18d3-000000@email.amazonses.com> A_V started a discussion. nova CLI issues --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/246/nova-cli-issues Have a great day! From red at fedoraproject.org Wed Jun 26 07:15:58 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Wed, 26 Jun 2013 09:15:58 +0200 Subject: [Rdo-list] RDO forum unanswered posts In-Reply-To: <51C9D4AB.1050406@redhat.com> References: <51C4524E.2080107@redhat.com> <51C9AE75.8020101@redhat.com> <51C9B0ED.6090207@redhat.com> <51C9B80C.7080500@redhat.com> <51C9D4AB.1050406@redhat.com> Message-ID: Nice list, but making it necessary to know the link is not going to scale well. Is it possible to add a button to the forum page next to "All Discussions"? And maybe apply the RDO (forum) design to it? On Tue, Jun 25, 2013 at 7:34 PM, Rich Bowen wrote: > On 06/25/2013 11:32 AM, Dave Neary wrote: > >> Hi, >> >> On 06/25/2013 05:02 PM, Perry Myers wrote: >> >>> Likewise, any chance we could get an 'unresolved' list? That way we >>> could see posts that have been answered (at least once) but are still >>> pending some resolution? >>> >> Marking discussions "RESOLVED" in the title, or with a resolved label, >> has not scaled. I don't know how else to measure whether a thread is >> resolved or not. Are you suggesting we retroactively resolve all the >> threads which have been resolved to date? There are a great many where >> the original poster hasn't let us know one way or another. >> > > > Yeah, I wanted to do something like that, but there's simply no reliable > way to tell whether a given post has reached resolution. There's also a lot > of posts that have had a response, but no answer. Like, the response was a > 'me too' or was a 'is anyone out there', and now it doesn't show up in the > 'unanswered' query. > > So, this is a very rough estimate. Well, maybe do the same that works with bugs (e.g. done with bugs that affect a Fedora release that's going EOL, or with Fedora package review requests that go stale): After it's been "answered" (i.e. has any kind of response), wait , then post a please-let-us-know-if-this-is-still-an-issue note and if nothing follows, again after , mark as resolved. I imagine that can be automated with some scripting-fu. Note that it should ideally be possible to un-resolve a thread again. If you do have the email address, you could also post the note to the OP directly instead of spamming the forum (to avoid the notes bumping the stale thread to the front page again and drowning newer threads by doing so). -- Sandro -------------- next part -------------- An HTML attachment was scrubbed... URL: From red at fedoraproject.org Wed Jun 26 07:17:30 2013 From: red at fedoraproject.org (Sandro "red" Mathys) Date: Wed, 26 Jun 2013 09:17:30 +0200 Subject: [Rdo-list] FYI: F19 RC1 cloud images available in EC2 and for download In-Reply-To: References: Message-ID: FWIW: F19 RC2 has been released but there should be absolutely no change to the cloud images. But just for the sake of completeness, you can now find them at: https://dl.fedoraproject.org/pub/alt/stage/19-RC2/Images/ Since there's currently no release blocking bugs left and the change between RC1 and RC2 (which affected live media only) is very minimal, this might very well be the last RC and be declared gold later this week (that is, in some 36h). IMHO. -- Sandro On Tue, Jun 25, 2013 at 4:00 PM, Sandro "red" Mathys wrote: > So as you can see below, the first release candidate for the F19 cloud > images is ready to be tested. To make F19 RC1 available in your OpenStack, > simply do something like: > > glance image-create --name "Fedora 19 RC1" --disk-format qcow2 > --container-format bare --is-public true --copy-from > https://dl.fedoraproject.org/pub/alt/stage/19-RC1/Images/x86_64/Fedora-x86_64-19-20130624-sda.qcow2 > > -- Sandro > > ---------- Forwarded message ---------- > From: Matthew Miller > Date: Tue, Jun 25, 2013 at 3:41 PM > Subject: [Test-Announce] F19 RC1 cloud images available in EC2 and for > download > To: test-announce at lists.fedoraproject.org > > > Fedora 19 Release Candidate 1 cloud images are now available from: > > http://dl.fedoraproject.org/pub/alt/stage/19-RC1/Images/ > > in either qcow2 or raw.xz format. You should be able to use Glance in > OpenStack to just import the qcow2 images directly and go. > > They're also in Amazon EC2 in the US East region (us-east-1): > > ami-79196a10 for x86_64 > ami-ef1b6886 for i386 > > Thanks to Dennis Gilmore in Fedora Release Engineering for the extra work > to > make this happen. > > The images are configured with "fedora" as the default user with > passwordless sudo. You can change this behavior by passing different > configuration data via the user-data in either OpenStack or EC2. For > example, to allow direct root login and to suppress the creation of the > 'fedora' user, use > > #cloud-config > users: > disable_root: 0 > > (The first line is identifying the userdata type, not a comment.) > > > > -- > Matthew Miller ??? Fedora Cloud Architect ??? < > mattdm at fedoraproject.org> > _______________________________________________ > test-announce mailing list > test-announce at lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/test-announce > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rdo-info at redhat.com Wed Jun 26 08:56:52 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 26 Jun 2013 08:56:52 +0000 Subject: [Rdo-list] [RDO] petreski started a discussion. Message-ID: <0000013f7fb31c01-ee34c7ab-7ccf-41ed-ad37-264ec441e3c8-000000@email.amazonses.com> petreski started a discussion. Error during puppet run: Max retries exceeded with url: /v2.0/OS-KSADM/services --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/247/error-during-puppet-run-max-retries-exceeded-with-url-v2-0os-ksadmservices Have a great day! From rdo-info at redhat.com Wed Jun 26 14:08:03 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 26 Jun 2013 14:08:03 +0000 Subject: [Rdo-list] [RDO] M4rc0 started a discussion. Message-ID: <0000013f80d004df-797c06ef-fa57-48f7-8987-fce219fe0c74-000000@email.amazonses.com> M4rc0 started a discussion. Some Help to install RDO over Fedora 18 --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/248/some-help-to-install-rdo-over-fedora-18 Have a great day! From rdo-info at redhat.com Wed Jun 26 14:25:56 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 26 Jun 2013 14:25:56 +0000 Subject: [Rdo-list] [RDO] PT_C started a discussion. Message-ID: <0000013f80e061e9-1bf86745-a56a-4316-a21e-917d3e1351f5-000000@email.amazonses.com> PT_C started a discussion. Dashboard networks --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/249/dashboard-networks Have a great day! From rdo-info at redhat.com Wed Jun 26 15:54:20 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 26 Jun 2013 15:54:20 +0000 Subject: [Rdo-list] [RDO] aero started a discussion. Message-ID: <0000013f81314fe2-f4b5b572-7f76-40da-b6ca-82e678a3b28d-000000@email.amazonses.com> aero started a discussion. Libvirt error on nova-compute start --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/250/libvirt-error-on-nova-compute-start Have a great day! From rdo-info at redhat.com Wed Jun 26 17:27:14 2013 From: rdo-info at redhat.com (RDO Forum) Date: Wed, 26 Jun 2013 17:27:14 +0000 Subject: [Rdo-list] [RDO] ptc61891 started a discussion. Message-ID: <0000013f81865f82-78e628a8-3af5-4b0a-8e0b-84b71463b420-000000@email.amazonses.com> ptc61891 started a discussion. Can't run any commands from keystonerc_admin --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/251/cant-run-any-commands-from-keystonerc_admin Have a great day! From rbowen at redhat.com Wed Jun 26 17:32:18 2013 From: rbowen at redhat.com (Rich Bowen) Date: Wed, 26 Jun 2013 13:32:18 -0400 Subject: [Rdo-list] RDO forum unanswered posts In-Reply-To: References: <51C4524E.2080107@redhat.com> <51C9AE75.8020101@redhat.com> <51C9B0ED.6090207@redhat.com> <51C9B80C.7080500@redhat.com> <51C9D4AB.1050406@redhat.com> Message-ID: <51CB25A2.8040204@redhat.com> On 06/26/2013 03:15 AM, Sandro "red" Mathys wrote: > > Well, maybe do the same that works with bugs (e.g. done with bugs that > affect a Fedora release that's going EOL, or with Fedora package > review requests that go stale): After it's been "answered" (i.e. has > any kind of response), wait , then post a > please-let-us-know-if-this-is-still-an-issue note and if nothing > follows, again after , mark as resolved. I > imagine that can be automated with some scripting-fu. Note that it > should ideally be possible to un-resolve a thread again. > > If you do have the email address, you could also post the note to the > OP directly instead of spamming the forum (to avoid the notes bumping > the stale thread to the front page again and drowning newer threads by > doing so). > I'll poke around to see if there's a forum (Vanilla) plugin that already does this, or similar, before attempting to implement this myself. -- Rich Bowen OpenStack Community Liaison http://openstack.redhat.com/ From rdo-info at redhat.com Thu Jun 27 01:10:16 2013 From: rdo-info at redhat.com (RDO Forum) Date: Thu, 27 Jun 2013 01:10:16 +0000 Subject: [Rdo-list] [RDO] gfidente started a discussion. Message-ID: <0000013f832e4963-64d63d59-6c20-4212-a733-f239c00e4b19-000000@email.amazonses.com> gfidente started a discussion. Use Swift as backend for Glance --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/252/use-swift-as-backend-for-glance Have a great day! From msolberg at redhat.com Thu Jun 27 03:58:27 2013 From: msolberg at redhat.com (Michael Solberg) Date: Wed, 26 Jun 2013 23:58:27 -0400 Subject: [Rdo-list] Outbound packet traffic with nova-network Message-ID: <51CBB863.1080101@redhat.com> Hi list. I'm having some trouble with my network setup and I thought maybe the group could help. I have three compute nodes with two network interfaces. There's a private 192.168.32.0/24 network (fixed range) on eth1 and a 10.17.12.128/25 network (floating range) on eth0 on these nodes. Networking works as expected. Connectivity is good on the 192 network and traffic is forwarded from the floating range inbound to the fixed range correctly. That is, I can ssh into an instance from the outside world using the floating address. However, when traffic is leaving the instance, it doesn't seem to get translated. Here's a concrete example: Instance has a fixed address of 192.168.32.4. Instance is assigned a floating address of 10.17.12.139. Instance is running on a hypervisor with the address 10.17.12.12. Pings from the instance to 10.17.12.12 return fine, but pings from the instance out to the internet don't work. When I run a tcpdump, I see that the pings reach the destination with the source address set to 192.168.32.4: [root at 10.17.12.11 ~]# tcpdump -n -i eth0 icmp tcpdump: WARNING: eth0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 23:55:38.238739 IP 192.168.32.4 > 10.17.12.11: ICMP echo request, id 45321, seq 1, length 64 23:55:38.238774 IP 10.17.12.11 > 192.168.32.4: ICMP echo reply, id 45321, seq 1, length 64 Is this expected? If so, is there any way to get nova-network to translate the outbound traffic so that it looks like it's coming from 10.17.12.139 instead of 192.168.32.4? Thanks. Michael. -- Michael Solberg Principal Architect, Red Hat, Inc. From rdo-info at redhat.com Thu Jun 27 14:05:30 2013 From: rdo-info at redhat.com (RDO Forum) Date: Thu, 27 Jun 2013 14:05:30 +0000 Subject: [Rdo-list] [RDO] ptc61891 started a discussion. Message-ID: <0000013f85f4089e-3731e52a-1a5e-405d-9871-5920ea25e709-000000@email.amazonses.com> ptc61891 started a discussion. Network Topology --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/253/network-topology Have a great day! From rbryant at redhat.com Thu Jun 27 17:13:33 2013 From: rbryant at redhat.com (Russell Bryant) Date: Thu, 27 Jun 2013 13:13:33 -0400 Subject: [Rdo-list] Outbound packet traffic with nova-network In-Reply-To: <51CBB863.1080101@redhat.com> References: <51CBB863.1080101@redhat.com> Message-ID: <51CC72BD.7060502@redhat.com> On 06/26/2013 11:58 PM, Michael Solberg wrote: > Hi list. > > I'm having some trouble with my network setup and I thought maybe the > group could help. I have three compute nodes with two network > interfaces. There's a private 192.168.32.0/24 network (fixed range) on > eth1 and a 10.17.12.128/25 network (floating range) on eth0 on these nodes. > > Networking works as expected. Connectivity is good on the 192 network > and traffic is forwarded from the floating range inbound to the fixed > range correctly. That is, I can ssh into an instance from the outside > world using the floating address. However, when traffic is leaving the > instance, it doesn't seem to get translated. Here's a concrete example: > > Instance has a fixed address of 192.168.32.4. > Instance is assigned a floating address of 10.17.12.139. > Instance is running on a hypervisor with the address 10.17.12.12. > > Pings from the instance to 10.17.12.12 return fine, but pings from the > instance out to the internet don't work. When I run a tcpdump, I see > that the pings reach the destination with the source address set to > 192.168.32.4: > > [root at 10.17.12.11 ~]# tcpdump -n -i eth0 icmp > tcpdump: WARNING: eth0: no IPv4 address assigned > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes > 23:55:38.238739 IP 192.168.32.4 > 10.17.12.11: ICMP echo request, id > 45321, seq 1, length 64 > 23:55:38.238774 IP 10.17.12.11 > 192.168.32.4: ICMP echo reply, id > 45321, seq 1, length 64 > > Is this expected? If so, is there any way to get nova-network to > translate the outbound traffic so that it looks like it's coming from > 10.17.12.139 instead of 192.168.32.4? Can you provide more information on your network topology? What nova-network mode are you using? Your example is for "pings from the instance out to the internet", but you're pinging an address (10.17.12.11) that's on the same private network as the compute node (10.17.12.12). My guess is that is confusing things. -- Russell Bryant From kchamart at redhat.com Fri Jun 28 06:05:28 2013 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Fri, 28 Jun 2013 11:35:28 +0530 Subject: [Rdo-list] FYI - Fedora 19 RC3 images are available Message-ID: <51CD27A8.2020905@redhat.com> Heya, Here are the images QCOW2: wget -c https://dl.fedoraproject.org/pub/alt/stage/19-RC3/Images/x86_64/Fedora-x86_64-19-20130627-sda.qcow2 RAW: wget -c https://dl.fedoraproject.org/pub/alt/stage/19-RC3/Images/x86_64/Fedora-x86_64-19-20130627-sda.raw.xz PS: GA on July 02, 2013 -- https://lists.fedoraproject.org/pipermail/devel-announce/2013-June/001163.html -- /kashyap From kchamart at redhat.com Fri Jun 28 06:08:25 2013 From: kchamart at redhat.com (Kashyap Chamarthy) Date: Fri, 28 Jun 2013 11:38:25 +0530 Subject: [Rdo-list] FYI - Fedora 19 RC3 images are available In-Reply-To: <51CD27A8.2020905@redhat.com> References: <51CD27A8.2020905@redhat.com> Message-ID: <51CD2859.7010501@redhat.com> On 06/28/2013 11:35 AM, Kashyap Chamarthy wrote: > Heya, > > Here are the images > > QCOW2: > > wget -c > https://dl.fedoraproject.org/pub/alt/stage/19-RC3/Images/x86_64/Fedora-x86_64-19-20130627-sda.qcow2 > > > RAW: > > wget -c > https://dl.fedoraproject.org/pub/alt/stage/19-RC3/Images/x86_64/Fedora-x86_64-19-20130627-sda.raw.xz Just noting - the above images should be the last for F19 (unless there's anything critical that's found), and not be any different than GA that's coming soon. > > PS: GA on July 02, 2013 -- > https://lists.fedoraproject.org/pipermail/devel-announce/2013-June/001163.html > -- /kashyap From rdo-info at redhat.com Fri Jun 28 10:57:15 2013 From: rdo-info at redhat.com (RDO Forum) Date: Fri, 28 Jun 2013 10:57:15 +0000 Subject: [Rdo-list] [RDO] aero started a discussion. Message-ID: <0000013f8a6e0d45-0cf2a400-078e-476f-b9dd-fafeeab01f70-000000@email.amazonses.com> aero started a discussion. Network issue (allinone, single NIC) --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/254/network-issue-allinone-single-nic Have a great day! From rdo-info at redhat.com Fri Jun 28 11:28:26 2013 From: rdo-info at redhat.com (RDO Forum) Date: Fri, 28 Jun 2013 11:28:26 +0000 Subject: [Rdo-list] [RDO] ptc61891 started a discussion. Message-ID: <0000013f8a8a9869-83fc9e8d-f976-44bd-aeba-7882aa1f40d9-000000@email.amazonses.com> ptc61891 started a discussion. Unable to associate floating IPs --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/255/unable-to-associate-floating-ips Have a great day! From msolberg at redhat.com Fri Jun 28 13:00:05 2013 From: msolberg at redhat.com (Michael Solberg) Date: Fri, 28 Jun 2013 09:00:05 -0400 Subject: [Rdo-list] Outbound packet traffic with nova-network In-Reply-To: <51CC72BD.7060502@redhat.com> References: <51CBB863.1080101@redhat.com> <51CC72BD.7060502@redhat.com> Message-ID: <51CD88D5.6040407@redhat.com> On 06/27/2013 01:13 PM, Russell Bryant wrote: > On 06/26/2013 11:58 PM, Michael Solberg wrote: >> Hi list. >> >> I'm having some trouble with my network setup and I thought maybe the >> group could help. I have three compute nodes with two network >> interfaces. There's a private 192.168.32.0/24 network (fixed range) on >> eth1 and a 10.17.12.128/25 network (floating range) on eth0 on these nodes. >> >> Networking works as expected. Connectivity is good on the 192 network >> and traffic is forwarded from the floating range inbound to the fixed >> range correctly. That is, I can ssh into an instance from the outside >> world using the floating address. However, when traffic is leaving the >> instance, it doesn't seem to get translated. Here's a concrete example: >> >> Instance has a fixed address of 192.168.32.4. >> Instance is assigned a floating address of 10.17.12.139. >> Instance is running on a hypervisor with the address 10.17.12.12. >> >> Pings from the instance to 10.17.12.12 return fine, but pings from the >> instance out to the internet don't work. When I run a tcpdump, I see >> that the pings reach the destination with the source address set to >> 192.168.32.4: >> >> [root at 10.17.12.11 ~]# tcpdump -n -i eth0 icmp >> tcpdump: WARNING: eth0: no IPv4 address assigned >> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode >> listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes >> 23:55:38.238739 IP 192.168.32.4 > 10.17.12.11: ICMP echo request, id >> 45321, seq 1, length 64 >> 23:55:38.238774 IP 10.17.12.11 > 192.168.32.4: ICMP echo reply, id >> 45321, seq 1, length 64 >> >> Is this expected? If so, is there any way to get nova-network to >> translate the outbound traffic so that it looks like it's coming from >> 10.17.12.139 instead of 192.168.32.4? > > Can you provide more information on your network topology? What > nova-network mode are you using? I'm using single-host FlatDHCPManager. Here's a crude diagram of the traffic flow: (eth0 in VM) 192.168.32.4 -> (on hypervisor) vnet0 -> br100 -> (eth0 10.17.12.12) -> (across switch to other host) 10.17.12.11 (eth0). The host at 10.17.12.11 didn't have a route back to 192.168.32.4, so the reply packets were just dropped. > Your example is for "pings from the instance out to the internet", but > you're pinging an address (10.17.12.11) that's on the same private > network as the compute node (10.17.12.12). My guess is that is > confusing things. I was able to get the behavior I wanted by adding a masquerade rule to the POSTROUTING table: iptables -t nat -I POSTROUTING 1 -s 192.168.32.0/22 ! -d 192.168.32.0/22 -j MASQUERADE Now all traffic out from the virtual machine gets NAT'd when it leaves the nova network host: [root at virt-two ~]# tcpdump -n -i eth0 icmp tcpdump: WARNING: eth0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 08:39:30.685952 IP 10.17.12.12 > 10.17.12.11: ICMP echo request, id 45596, seq 1, length 64 08:39:30.686007 IP 10.17.12.11 > 10.17.12.12: ICMP echo reply, id 45596, seq 1, length 64 10.17.12.12 routes the packets back to 192.168.32.4. Michael. From rdo-info at redhat.com Fri Jun 28 13:33:08 2013 From: rdo-info at redhat.com (RDO Forum) Date: Fri, 28 Jun 2013 13:33:08 +0000 Subject: [Rdo-list] [RDO] PT_C started a discussion. Message-ID: <0000013f8afcc5d1-200726f2-5941-47db-8552-122cd7d0c969-000000@email.amazonses.com> PT_C started a discussion. Can't SSH/Ping --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/256/cant-sshping Have a great day! From rdo-info at redhat.com Fri Jun 28 14:43:26 2013 From: rdo-info at redhat.com (RDO Forum) Date: Fri, 28 Jun 2013 14:43:26 +0000 Subject: [Rdo-list] [RDO] mjames14 started a discussion. Message-ID: <0000013f8b3d2025-46931def-a405-468c-82d0-93223c3deca9-000000@email.amazonses.com> mjames14 started a discussion. Migrating volumes --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/257/migrating-volumes Have a great day! From rdo-info at redhat.com Fri Jun 28 15:36:01 2013 From: rdo-info at redhat.com (RDO Forum) Date: Fri, 28 Jun 2013 15:36:01 +0000 Subject: [Rdo-list] [RDO] PT_C started a discussion. Message-ID: <0000013f8b6d45f5-34b26fd2-1c80-4a35-98e3-91651227c8c1-000000@email.amazonses.com> PT_C started a discussion. Default Network --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/258/default-network Have a great day! From rdo-info at redhat.com Fri Jun 28 16:04:00 2013 From: rdo-info at redhat.com (RDO Forum) Date: Fri, 28 Jun 2013 16:04:00 +0000 Subject: [Rdo-list] [RDO] PT_C started a discussion. Message-ID: <0000013f8b86e173-fc14036b-054e-4bcc-b8a5-ad1bb36aa134-000000@email.amazonses.com> PT_C started a discussion. Nova-network dead --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/259/nova-network-dead Have a great day! From rbowen at redhat.com Fri Jun 28 16:07:18 2013 From: rbowen at redhat.com (Rich Bowen) Date: Fri, 28 Jun 2013 12:07:18 -0400 Subject: [Rdo-list] RDO forum unanswered posts In-Reply-To: References: <51C4524E.2080107@redhat.com> <51C9AE75.8020101@redhat.com> <51C9B0ED.6090207@redhat.com> <51C9B80C.7080500@redhat.com> <51C9D4AB.1050406@redhat.com> Message-ID: <51CDB4B6.3040801@redhat.com> On 06/26/2013 03:15 AM, Sandro "red" Mathys wrote: > Nice list, but making it necessary to know the link is not going to > scale well. Is it possible to add a button to the forum page next to > "All Discussions"? Done > And maybe apply the RDO (forum) design to it? Working on it. CSS is not my super power. ;-) -- Rich Bowen OpenStack Community Liaison http://openstack.redhat.com/ From rbowen at redhat.com Fri Jun 28 16:07:27 2013 From: rbowen at redhat.com (Rich Bowen) Date: Fri, 28 Jun 2013 12:07:27 -0400 Subject: [Rdo-list] Unanswered RDO forum posts (6/28 edition) Message-ID: <51CDB4BF.8010303@redhat.com> It's Friday, and here's the week's list of oldest unanswered questions. If you want to track the list realtime, see http://openstack.redhat.com/forum/unanswered.php (linked from the right sidebar in the forum). This week we're down from 35 to 26, and I really appreciate those of you who have endured me bugging you in private email about getting some answered. I've attempted to call individual's attention to specific issues based on the OpenStackTeam list, but it would be great if anyone else steps up for these. Please forgive me if I misdirect anything. ------ Error with instances with volumes after reboot (2013-05-12) : http://openstack.redhat.com/forum/discussion/110 -- eharney, can you triage this please? RDO + non Fixed IPs (2013-05-13) : http://openstack.redhat.com/forum/discussion/112 -- garyk or rkukura? Firewalld and bridge-device rules? (2013-05-21) : http://openstack.redhat.com/forum/discussion/133 -- marun or rohara? output of ovs with quantum (2013-05-24) : http://openstack.redhat.com/forum/discussion/140 -- otherwiseguy or cdub? packstack installation error (2013-05-27) : http://openstack.redhat.com/forum/discussion/149 -- derekh? Glance problem: "not enough disk space on the image media" (2013-06-04) : http://openstack.redhat.com/forum/discussion/171 -- jpeeler? Packstack --allinone doesn't add Physical NIC to br-ex (2013-06-05) : http://openstack.redhat.com/forum/discussion/174 -- mmagr? heat-engine error (2013-06-05) : http://openstack.redhat.com/forum/discussion/175 -- stevebaker or someone else from the Heat team? Vlan Network Create Fails With Unknown Error (2013-06-06) : http://openstack.redhat.com/forum/discussion/181 -- Someone working on Neutron? Mysql issues with centos 6.4 install (2013-06-11) : http://openstack.redhat.com/forum/discussion/195 -- Looks like that's an "update the docs" thing. I'll take it. -- Rich Bowen OpenStack Community Liaison http://openstack.redhat.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rdo-info at redhat.com Sat Jun 29 09:27:15 2013 From: rdo-info at redhat.com (RDO Forum) Date: Sat, 29 Jun 2013 09:27:15 +0000 Subject: [Rdo-list] [RDO] ppyy started a discussion. Message-ID: <0000013f8f420274-86f2deac-dd6a-43e9-943b-05f1fa8371b1-000000@email.amazonses.com> ppyy started a discussion. debug option always on in init files of openstack-glance --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/260/debug-option-always-on-in-init-files-of-openstack-glance Have a great day! From rdo-info at redhat.com Sat Jun 29 18:52:34 2013 From: rdo-info at redhat.com (RDO Forum) Date: Sat, 29 Jun 2013 18:52:34 +0000 Subject: [Rdo-list] [RDO] mkomarinski started a discussion. Message-ID: <0000013f9147925d-ba9c96d6-0466-44d4-b777-5e624e260d8b-000000@email.amazonses.com> mkomarinski started a discussion. Unable to add new cinder server --- Follow the link below to check it out: http://openstack.redhat.com/forum/discussion/261/unable-to-add-new-cinder-server Have a great day!