Re: [openstack-dev] Help needed

This is the full log :- python update.py /opt/stack/keystone Traceback (most recent call last): File "update.py", line 274, in main(options, args) File "update.py", line 259, in main _copy_requires(options.suffix, options.softupdate, args[0]) File "update.py", line 219, in _copy_req

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 08/04/15 20:23 -0700, Joshua Harlow wrote: Hope this helps: 'Let's do away with' == 'remove it/no longer use it' vs 'let's use RPC-over-AMQP' which means continue using it/use it more. a-ha... That explains it. My, obviously, non-native english translation failed to parse that. Thanks for

[openstack-dev] [neutron] New version of python-neutronclient release for Kilo: 2.4.0

The Neutron team is proud to announce the release of the latest version of python-neutronclient. This release includes the following bug fixes and improvements: aa1215a Merge "Fix one remaining E125 error and remove it from ignore list" cdfcf3c Fix one remaining E125 error and remove it from ignor

Re: [openstack-dev] Help needed

You can get the logs in /opt/stack/logs folder as stack.sh.log On Thu, Apr 9, 2015 at 3:03 PM, Abhishek Shrivastava wrote: > Can you give the full log. > > > On Thu, Apr 9, 2015 at 2:57 PM, Deepika Agrawal > wrote: > >> hi guys! >> i am geting attribute error "nonetype has no attribute URL" in

Re: [openstack-dev] Advice on a Neutron ACL kludge

I think that people often mean different things by ACLs, so can you be more precise? Thanks, Neil From: Rich Wellner Sent: 09 April 2015 01:29 To: openstack-dev@lists.openstack.org Subject: [openstack-dev] Advice on a Neutron ACL kludge We are pursu

[openstack-dev] [Neutron] The specs process, effective operators feedback and product management

The Neutron specs process was introduced during the Juno timecycle. At the time it was mostly a bureaucratic bottleneck (The ability to say no) to ease the pain of cores and manage workloads throughout a cycle. Perhaps this is a somewhat naive outlook, but I see other positives, such as more upf

Re: [openstack-dev] [Glance] PTL Candidacy

confirmed On 04/09/2015 12:55 AM, Nikhil Komawar wrote: > Hello everyone, > > I would like to announce my candidacy as PTL for Glance for Liberty cycle. > > I have been part of the Glance program since Folsom release and have seen it > grow and get better over the years. As the PTL for Kilo, I

[openstack-dev] [puppet] Adding the Puppet modules to OpenStack

It has been quite some time now that Puppet OpenStack contributors have wanted to be part of the big tent so we would become an official project. We talked about that over our last IRC meetings and decided to elect a PTL so we would fit OpenStack requirements. Today, we officially ask to the Open

[openstack-dev] [Cinder] [Sahara] Kilo RC1 available

Hello everyone, Next to each the release candidate stage, we have Cinder and Sahara. Their RC1 tarballs, as well as a lists of last-minute features and fixed bugs since kilo-3 are available at: https://launchpad.net/cinder/kilo/kilo-rc1 https://launchpad.net/sahara/kilo/kilo-rc1 Unless release-c

Re: [openstack-dev] Fwd: [stable] Request stable freeze exception: 162112 and 162113 libvirt live migration progress & loop

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This one is very suspicious for a last minute merge. Also, no nova cores, neither nova-stable-maint cores commented on the backport. Without it, there is no way it will be merged at all. Please reach nova folks on the matter. On 04/06/2015 11:44 PM, D

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Doug Hellmann wrote: > Excerpts from Dean Troyer's message of 2015-04-08 09:42:31 -0500: >> On Wed, Apr 8, 2015 at 8:55 AM, Thierry Carrez >> wrote: >> >>> The question is, how should we proceed there ? This is new procedure, so >>> I'm a bit unclear on the best way forward and would like to pick

[openstack-dev] [oslo.messaging][zeromq] Some backports to stable/kilo

Hi oslo all, Currently devstack master relies on 1.8.1 release due to requirements frozen (>=1.8.0 < 1.9.0), however, ZeroMQ driver is able to run on 1.9.0 release. The result is that you cannot deploy ZeroMQ driver using devstack master now due to some incompatibility between oslo.messaging 1.8.1

Re: [openstack-dev] [Horizon] [all] django_openstack_auth potential release

David Lyle wrote: > So we have a couple of options. First, leave django_openstack_auth at > 1.1.9 and let deployers and distros rationalize which version of Django > they want to use and negotiate the dependency issues independently. Or > second, release a new version of django_openstack_auth and d

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

Thanks for your work on this! :) On Thu, Apr 9, 2015 at 7:25 PM, Victor Stinner wrote: > Hi, > > During the last OpenStack Summit at Paris, we discussed how we can port > OpenStack to Python 3, because eventlet was not compatible with Python 3. > There are multiple approaches: port eventlet to P

Re: [openstack-dev] [Nova] RC1 state of play

Le 09/04/2015 08:01, Michael Still a écrit : There are a few bugs still outstanding for nova's RC1. Here's a quick summary. For each of these we need to either merge the fix, or bump the bug from being release blocking. - https://bugs.launchpad.net/nova/+bug/1427351 "cells: hypervisor API

Re: [openstack-dev] [oslo.messaging][zeromq] Some backports to stable/kilo

Mehdi, +2, let's do it. -- dims On Thu, Apr 9, 2015 at 11:04 AM, Mehdi Abaakouk wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > Hi, > > All of these patches are only bug fixes, so that's good for me. > > So if others agreed, I can release 1.8.2 with these changes once they ar

[openstack-dev] [neutron][lbaas][barbican] default certificate manager

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi lbaas folks, I've realized recently that the default certificate manager for lbaas advanced service is now barbican based. Does it mean that to make default configuration working as is, users will need to deploy barbican service? If that's really t

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Excerpts from Sean Dague's message of 2015-04-08 10:49:15 -0400: > On 04/08/2015 10:42 AM, Dean Troyer wrote: > > On Wed, Apr 8, 2015 at 8:55 AM, Thierry Carrez > > wrote: > > > > The question is, how should we proceed there ? This is new procedure, so > > I'

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Excerpts from Devananda van der Veen's message of 2015-04-08 14:37:26 +: > Thierry, > > You left out python-ironicclient, which isn't a surprise as it isn't > actually listed in Nova's requirements.txt file. I don't have a link handy > to cite the previous discussions, but Nova felt that it wa

Re: [openstack-dev] [Openstack-operators] [Neutron] The specs process, effective operators feedback and product management

On 9 April 2015 at 17:04, Kyle Mestery wrote: > On Thu, Apr 9, 2015 at 9:52 AM, Assaf Muller wrote: > >> The Neutron specs process was introduced during the Juno timecycle. At >> the time it >> was mostly a bureaucratic bottleneck (The ability to say no) to ease the >> pain of cores >> and manag

[openstack-dev] [Nova] [Horizon] Insufficient (?) features in current Nova API

Hello! While analyzing Horizon behavior on a large scale we faced some performance issues which are most probably caused by inefficient calls to Nova API from Horizon, more specifically described at https://bugs.launchpad.net/nova/+bug/1442310 Since my knowledge of Nova existing APIs is not very

Re: [openstack-dev] [release] oslo.messaging 1.9.0

Hi Doug, In the global requirements.txt, oslo.messaging version is still >= 1.8.0 but < 1.9.0. As a result, some bugs fixed in 1.9.0 are still there when I deploy with devstack master branch. I submitted a review for the update. On Wed, Mar 25, 2015 at 10:22 PM, Doug Hellmann wrote: > We are co

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Excerpts from Dean Troyer's message of 2015-04-08 09:42:31 -0500: > On Wed, Apr 8, 2015 at 8:55 AM, Thierry Carrez > wrote: > > > The question is, how should we proceed there ? This is new procedure, so > > I'm a bit unclear on the best way forward and would like to pick our > > collective brain.

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Keystonemiddleware is pending a minor fix to sync g-r in a sane way to match the rest of kilo (what we have for keystone et al). However we are blocked because there is no stable Juno and icehouse branches. I'd like to release the Python-keystone client with the requirements update for kilo. So k

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

The Barbican Team also has a plan to release a new version of barbican client for Kilo. The planned version is 3.1.0. [1] and it will include features landed during FFE. Thanks, -Douglas Mendizabal [1] https://launchpad.net/python-barbicanclient/+milestone/3.1.0

Re: [openstack-dev] [nova][ec2-api] Need advice about running Tempest against stackforge/ec2-api

Hi. As you can see adjusted Tempest (https://review.openstack.org/#/c/171222/) runs well against both Nova EC2 and ec2api ( https://review.openstack.org/#/c/172059). On Tue, Apr 7, 2015 at 5:50 PM, Feodor Tersin wrote: > Hi Sean > > > On Mon, Apr 6, 2015 at 7:34 PM, Sean Dague wrote: > >> On

Re: [openstack-dev] [oslo.messaging][zeromq] Some backports to stable/kilo

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, All of these patches are only bug fixes, so that's good for me. So if others agreed, I can release 1.8.2 with these changes once they are landed. We don't have any other changes pending in kilo branch for now. Le 2015-04-09 16:12, Li Ma a

Re: [openstack-dev] [Neutron] - Joining the team - interested in a Debian Developer and experienced Python and Network programmer?

On Thu, Apr 9, 2015 at 2:13 AM, Matt Grant wrote: > Hi! > > I am just wondering what the story is about joining the neutron team. > Could you tell me if you are looking for new contributors? > > We're always looking for someone new to participate! Thanks for reaching out! > Previously I have pr

Re: [openstack-dev] [stable] [Cinder] FFE for "Clear migration_status from a destination volume if migration fails"

Hi Jay, Thank you for your cooperation. This fix was merged successfully today. Regards, Mitsuhiro Tanino HITACHI DATA SYSTEMS > -Original Message- > From: Jay S. Bryant [mailto:jsbry...@electronicjungle.net] > Sent: Tuesday, April 07, 2015 11:08 AM > To: OpenStack Development Mailing

Re: [openstack-dev] Neutron and ACLs

Hey, as a matter of fact in Barbican we are also in need of proper ACLs and there is currently work on-going on implementing them: http://specs.openstack.org/openstack/barbican-specs/specs/kilo/add-creator-only-option.html On Wed, Apr 8, 2015 at 7:58 PM, Rich Wellner wrote: > Yeah, sounds lik

Re: [openstack-dev] [neutron] Neutron scaling datapoints?

Hi Joe, Many thanks for your reply! On 09/04/15 03:34, joehuang wrote: Hi, Neil, From theoretic, Neutron is like a "broadcast" domain, for example, enforcement of DVR and security group has to touch each regarding host where there is VM of this project resides. Even using SDN controller, th

Re: [openstack-dev] [infra] request to disable xenserver CI account

On 4/9/2015 4:27 PM, Jeremy Stanley wrote: On 2015-04-09 16:13:13 -0500 (-0500), Matt Riedemann wrote: The XenServer/XenProject third party CI job has been voting -1 on nova changes for over 24 hours without a response from the maintainers so I'd like to request that we disable for now while i

[openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work]

On Wed, Apr 01, 2015 at 01:37:28AM EDT, Dr. Jens Rosenboom wrote: > FWIW, I think I made some progress in getting [1] to work, though if someone > could jump in and make a proper patch from my hack, that would be great. > > [1] https://review.openstack.org/168423 Hi, Just wanted to write a quick

[openstack-dev] [Ironic] Weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. (I apologize for sending this out late this week.) Drivers == IPA (jroll/JayF/JoshNang) -- IPA now has documentation. (jayf) Ch

Re: [openstack-dev] [neutron] Neutron scaling datapoints?

Hi Mike, Many thanks for your reply! On 08/04/15 17:56, Mike Spreitzer wrote: Are you looking at scaling the numbers of tenants, Neutron routers, and tenant networks as you scale hosts and guests? I think this is a plausible way to grow. The compartmentalizations that comes with growing those

Re: [openstack-dev] [heat] autoscaling and load balancers

On 08/04/15 21:51, Miguel Grinberg wrote: Hi Angus, Regarding this: > As Zane suggested, you should think of autoscaling as been in a different service. It's not that I can't see your point of view. I can imagine an autoscaling service. I agree with you guys that if we had that, then none of

Re: [openstack-dev] [neutron] [QoS] QoS weekly meeting

I prefer Timeslot B, thanks for coordinating. I would be interested in helping out in any way with the design session let me know! From: "Sandhya Dasu (sadasu)" mailto:sad...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstac

[openstack-dev] [Neutron] [Ceilometer] Kilo RC1 available

Hello everyone, It's Neutron and Ceilometer's turn to reach the release candidate stage. Their RC1 tarballs, as well as a lists of last-minute features and fixed bugs since kilo-3 are available at: https://launchpad.net/neutron/kilo/kilo-rc1 https://launchpad.net/ceilometer/kilo/kilo-rc1 Unless

Re: [openstack-dev] [Openstack-operators] [Openstack-dev] resource quotas limit per stacks within a project

Thanks for your reply Kris. I'd love to but we're forced to by an in-house app we built (in the same space with Murano to offer a Service catalogue for various services) deployment. IT must be a different path to corss the bridge given the circumstances. Dani On Wed, Apr 8, 2015 at 3:54 PM, Kri

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Neutron team has a plan to release a new version of neutornclient for Kilo. We waited the new release until all granted FFE patches land, and now we are almost ready to go. (waiting one patch in the gate) The planned new version is 2.4.0. It is because neutronclient uses 2.3.x version for a long t

[openstack-dev] [infra] request to disable xenserver CI account

The XenServer/XenProject third party CI job has been voting -1 on nova changes for over 24 hours without a response from the maintainers so I'd like to request that we disable for now while it's being worked since it's a voting job and causing noise at kind of a hairy point in the release. --

Re: [openstack-dev] cinder[stable/juno] Fix the eqlx driver to retry on ssh timeout(Backport)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am fine with the change itself, but please split into proper pieces. Squashing patches is the last resort. On 04/06/2015 11:33 PM, rajini_...@dell.com wrote: > *Dell - Internal Use - Confidential * > > Hi > > Can we have a freeze exception on thi

Re: [openstack-dev] [heat] suggestion for lock/protect stack blueprint

Hey everyone, Regarding the lock-stack blueprint, Following Steve and Pavlo's suggestions, I created the following blueprint in heat-specs. This is the launchpad link: https://blueprints.launchpad.net/heat/+spec/lock-stack on Wed, Apr 8, 2015 at 4:54 PM Steve Hardy wrote: >We might consider ma

Re: [openstack-dev] [Nova] Things to tackle in Liberty

On 04/08/2015 05:07 PM, Michael Still wrote: > There are still a few idle cores, particularly people who haven’t done > less than ten reviews in the last 90 days. We should drop those people > from core and thank them for their work in the past noting once again > that this is a natural part of the

Re: [openstack-dev] [barbican] Utilizing the KMIP plugin

Hey John. Thanks for letting me know about the error. But I think my configuration is not seeing the kmip_plugin selection. In my barbican-api.conf file in /etc/barbican I have set enabled_secretstore_plugins = kmip_plugin However, I don't think it is creating a KMIPSecretStore instance. I edited

Re: [openstack-dev] [Nova] Things to tackle in Liberty

Le 08/04/2015 23:07, Michael Still a écrit : I just wanted to send a note about John running in the PTL election for Nova. I want to make it clear that I think having more than one candidate is a good thing -- its a healthy part of a functional democracy, and it also means regardless of the ou

Re: [openstack-dev] [release] oslo.messaging 1.9.0

https://review.openstack.org/172045 On Thu, Apr 9, 2015 at 9:21 PM, Li Ma wrote: > Hi Doug, > > In the global requirements.txt, oslo.messaging version is still >= > 1.8.0 but < 1.9.0. As a result, some bugs fixed in 1.9.0 are still > there when I deploy with devstack master branch. > > I submitte

Re: [openstack-dev] [release] oslo.messaging 1.9.0

Excerpts from Li Ma's message of 2015-04-09 21:21:40 +0800: > Hi Doug, > > In the global requirements.txt, oslo.messaging version is still >= > 1.8.0 but < 1.9.0. As a result, some bugs fixed in 1.9.0 are still > there when I deploy with devstack master branch. > > I submitted a review for the up

Re: [openstack-dev] [release] oslo.messaging 1.9.0

OK. I didn't notice because requirements project doesn't have stable/kilo yet. Thanks for explanation. On Thu, Apr 9, 2015 at 9:37 PM, Doug Hellmann wrote: > Excerpts from Li Ma's message of 2015-04-09 21:21:40 +0800: >> Hi Doug, >> >> In the global requirements.txt, oslo.messaging version is sti

Re: [openstack-dev] [Nova] Things to tackle in Liberty

On 08/04/15 22:07, Michael Still wrote: priorities and specs === I think the current spec process is starting to work well for us, and that priorities was a success. We should continue with specs, but with an attempt to analyse why so many approved specs don’t land [...] nova-net

[openstack-dev] Help needed

hi guys! i am geting attribute error "nonetype has no attribute URL" in python update.py /opt/stack/keystone when i am going to run stack.sh. Please help! -- Deepika Agrawal __ OpenStack Development Mailing List (not for usag

Re: [openstack-dev] [infra] request to disable xenserver CI account

On 2015-04-09 16:13:13 -0500 (-0500), Matt Riedemann wrote: > The XenServer/XenProject third party CI job has been voting -1 on > nova changes for over 24 hours without a response from the > maintainers so I'd like to request that we disable for now while > it's being worked since it's a voting job

Re: [openstack-dev] [all] how to send messages (and events) to our users

I would agree that the reason monasca had to roll their own notification system is likely because one wasn't available, but whether that should be a separate (stand alone separate project) vs integrated service (part of something like monasca) is, to some extent, debatable. No argument on the fact

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

I am also looking at a python-keystoneclient release still pending as well. This is being added to the ML topic based on the IRC conversation we just had. On Thu, Apr 9, 2015 at 8:20 AM, Morgan Fainberg wrote: > Keystonemiddleware is pending a minor fix to sync g-r in a sane way to > match the r

Re: [openstack-dev] [nova] [stringfreeze] request for SFE for live-migration on system z (review 166130)

Without the mentioned qemu change the live migration is still fully functional with volume backed instances just like on x86 hosts, with the following caveat: The safety check whether the target host CPU is compatible with the source host CPU is not performed. Therefore, it is a responsibility of t

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 06/04/15 22:55, Angus Salkeld wrote: Hi all For quite some time we (Heat team) have wanted to be able to send messages to our users (by user I do not mean the Operator, but the User that is interacting with the client). What do I mean by "user messages", and how do they differ from our curre

Re: [openstack-dev] [all] Design Summit - Cross-project track - Session suggestions

Thanks Thierry. I really like the Google Docs form to submit new proposals. Now if someone could please fix the form so that the Topic fields in new entries are word-wrapped correctly… ;-) Geoff > On Apr 9, 2015, at 7:33 AM, Thierry Carrez wrote: > > Hi everyone, > > If you have ideas for

Re: [openstack-dev] [libvirt] [nova] The risk of hanging when shutdown instance.

On Tue, Mar 31, 2015 at 11:37:04AM +0800, zhang bo wrote: > On 2015/3/31 4:36, Eric Blake wrote: > > > On 03/30/2015 06:08 AM, Michal Privoznik wrote: > >> On 30.03.2015 11:28, zhang bo wrote: > >>> On 2015/3/28 18:06, Rui Chen wrote: > >>> > > >>> > >>> The API virDomainShutdown's descrip

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

On Thu, Apr 9, 2015 at 11:23 AM, Akihiro Motoki wrote: > Neutron team has a plan to release a new version of neutornclient for Kilo. > We waited the new release until all granted FFE patches land, > and now we are almost ready to go. (waiting one patch in the gate) > > The planned new version is

Re: [openstack-dev] [Openstack-operators] [Neutron] The specs process, effective operators feedback and product management

On Thu, Apr 9, 2015 at 9:52 AM, Assaf Muller wrote: > The Neutron specs process was introduced during the Juno timecycle. At the > time it > was mostly a bureaucratic bottleneck (The ability to say no) to ease the > pain of cores > and manage workloads throughout a cycle. Perhaps this is a somewh

Re: [openstack-dev] [Neutron] - Joining the team - interested in a Debian Developer and experienced Python and Network programmer?

Hi Matt, Jaume did an awesome work at proposing and implementing a framework for announcing public IP with a BGP speaker [1]. Unfortunately, the spec hasn't been merged in kilo. Hope it will be resubmitted in L. Your proposal seems to be a mix of Jaume proposal and HA router design? We also play

[openstack-dev] [Neutron] - Joining the team - interested in a Debian Developer and experienced Python and Network programmer?

Hi! I am just wondering what the story is about joining the neutron team. Could you tell me if you are looking for new contributors? Previously I have programmed OSPFv2 in Zebra/Quagga, and worked as a router developer for Allied Telesyn. I also have extensive Python programming experience, havi

Re: [openstack-dev] [all] how to send messages (and events) to our users

>From: Angus Salkeld >Sent: Wednesday, April 8, 2015 8:24 PM >To: OpenStack Development Mailing List (not for usage questions) >Subject: Re: [openstack-dev] [all] how to send messages (and events) to our >users > > >I also want to point out that what I'd actually rather see is that all >of the se

Re: [openstack-dev] [Nova] PTL Candidacy

On 8 April 2015 at 21:19, Anita Kuno wrote: > On 04/08/2015 02:25 PM, John Garbutt wrote: >> Hi, >> >> I am johnthetubaguy on IRC. >> >> I would like to run for the OpenStack Compute (Nova) PTL position. >> >> I currently work as a Principal Engineer at Rackspace, focusing on >> software developme

Re: [openstack-dev] [stable] [nova] FFE for "libvirt: proper monitoring of live migration progress"

On Tue, Apr 07, 2015 at 12:57:40PM +0200, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > +344 new lines of code for an exception patch? No way. Let's take time > to consider the patch outside the very next release. Agreed, I think it needs a little more time to soak

Re: [openstack-dev] [neutron] New version of python-neutronclient release for Kilo: 2.4.0

On Thu, Apr 9, 2015 at 4:00 PM, Matt Riedemann wrote: > > > On 4/9/2015 3:14 PM, Kyle Mestery wrote: > >> The Neutron team is proud to announce the release of the latest version >> of python-neutronclient. This release includes the following bug fixes >> and improvements: >> >> aa1215a Merge "Fix

[openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

Hi, During the last OpenStack Summit at Paris, we discussed how we can port OpenStack to Python 3, because eventlet was not compatible with Python 3. There are multiple approaches: port eventlet to Python 3, replace eventlet with asyncio, replace eventlet with threads, etc. We decided to not ta

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

On Thu, Apr 9, 2015 at 9:25 AM, Victor Stinner wrote: > Hi, > > During the last OpenStack Summit at Paris, we discussed how we can port > OpenStack to Python 3, because eventlet was not compatible with Python 3. > There are multiple approaches: port eventlet to Python 3, replace eventlet > with a

Re: [openstack-dev] Advice on a Neutron ACL kludge

On 4/9/15 8:08 AM, Neil Jerram wrote: I think that people often mean different things by ACLs, so can you be more precise? Yeah, you're absolutely right. What we are trying to do is really simple. We run an HPC facility and some of our workload needs port mapping and some needs public IP rou

Re: [openstack-dev] [Nova] Regarding deleting snapshot when instance is OFF

On Wed, Apr 08, 2015 at 11:31:40PM +0530, Deepak Shetty wrote: > Hi, > Cinder w/ GlusterFS backend is hitting the below error as part of > test_volume_boot_pattern tempest testcase [Meta comment: Since main components that are triggering this errors are Cinder with GlusterFS, adding "Cinder" t

Re: [openstack-dev] [Nova] [Cinder] [Tempest] Regarding deleting snapshot when instance is OFF

On 04/08/2015 11:22 PM, Deepak Shetty wrote: > + [Cinder] and [Tempest] in the $subject since this affects them too > > On Thu, Apr 9, 2015 at 4:22 AM, Eric Blake wrote: > >> On 04/08/2015 12:01 PM, Deepak Shetty wrote: >>> >>> Questions: >>> >>> 1) Is this a valid scenario being tested ? Some s

Re: [openstack-dev] [release] oslo.messaging 1.9.0

Excerpts from Li Ma's message of 2015-04-09 21:53:03 +0800: > OK. I didn't notice because requirements project doesn't have stable/kilo yet. > Thanks for explanation. > No problem, this is a somewhat new process. The stable branch for the requirements repository should be created pretty soon when

[openstack-dev] [Security] Meeting agenda

Reminder to all, our meeting is today at 1700 UTC on Freenode #openstack-meeting-alt The agenda can be found here: https://wiki.openstack.org/wiki/Meetings/OpenStackSecurity#Agenda_for_next_meeting * Roll Call * Reminder that the agenda exists * Update on project status * security.openstack.org

Re: [openstack-dev] [neutron] New version of python-neutronclient release for Kilo: 2.4.0

On 4/9/2015 3:14 PM, Kyle Mestery wrote: The Neutron team is proud to announce the release of the latest version of python-neutronclient. This release includes the following bug fixes and improvements: aa1215a Merge "Fix one remaining E125 error and remove it from ignore list" cdfcf3c Fix one

Re: [openstack-dev] [puppet][tc] Adding the Puppet modules to OpenStack

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just adding the tc tag so this doesn't get overlooked by the relevant people. On 04/09/2015 10:33 AM, Emilien Macchi wrote: > It has been quite some time now that Puppet OpenStack contributors > have wanted to be part of the big tent so we would becom

Re: [openstack-dev] Help needed

*CAUSE:* This error has happened because of new pip 6.1.1 release. In this release they have remove the attribute "*url*" and used "*link*" in that place, so, devstack guys who were using "*url*" in the "*openstack/requirements*" project also need to change the variable. And I think you don't have

Re: [openstack-dev] [neutron][lbaas][barbican] default certificate manager

Hi Ihar, So that decision was indeed hastily done but I still think it was the right one. Let me break down the reasons: 1) To use the local cert manager, the API would have to accept the raw secrets (certificate, private key, etc). We'd have to store that some place, but it would have been e

Re: [openstack-dev] Help needed

Can you give the full log. On Thu, Apr 9, 2015 at 2:57 PM, Deepika Agrawal wrote: > hi guys! > i am geting attribute error "nonetype has no attribute URL" in python > update.py /opt/stack/keystone when i am going to run stack.sh. > Please help! > -- > Deepika Agrawal > > >

[openstack-dev] [all] Design Summit - Cross-project track - Session suggestions

Hi everyone, If you have ideas for nice cross-project topics to discuss at the Design Summit in Vancouver, now is the time to propose them. Given the number of people involved, the etherpad last time ended up as a pile of unusable junk that took a while for the track lead to process, so for this