Re: [openstack-dev] [magnum] Schedule for rest of Kilo

On Tue, Jan 27, 2015 at 04:27:21AM +, Adrian Otto wrote: > Tony, > > That would be terrific. Which iCal feed were you thinking of? I was planning > on making something similar to this: Sorry Adrian I was a little off topic. I was thinking that when you settle on a schedule for your regular

[openstack-dev] [gantt] Scheduler sub-group meeting agenda 2/3

Meeting on #openstack-meeting at 1500 UTC (8:00AM MST) 1) Remove direct nova DB/API access by Scheduler Filters - https://review.opernstack.org/138444/ 2) Status on cleanup work - https://wiki.openstack.org/wiki/Gantt/kilo -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D.

Re: [openstack-dev] [heat] operators vs users for choosing convergence engine

I think incremental adoption is a great principle to have and this will enable that. So +1 -Rob On 3 February 2015 at 13:52, Steve Baker wrote: > A spec has been raised to add a config option to allow operators to choose > whether to use the new convergence engine for stack operations. For some

Re: [openstack-dev] [Heat] Talk on Jinja Metatemplates for upcoming summit

Hey Pavlov, The main aim of this effort is to allow a more efficient template catalog management, not unlike what is given in [2]. As a service to our customers, Rackspace maintains a catalog of useful templates[3] which are also exposed to the user through the UI. The template authors of these

Re: [openstack-dev] [trove]how to enable trove in dashboard?

Sorry, i find it. -- Best Li Tianqing At 2015-02-03 10:48:06, "Li Tianqing" wrote: Hello, I first install devstack, then install trove from source code. After seraching on the net, i do not find how to enable trove in dashboard... Can someone help to point out how to? -- Be

[openstack-dev] [trove]how to enable trove in dashboard?

Hello, I first install devstack, then install trove from source code. After seraching on the net, i do not find how to enable trove in dashboard... Can someone help to point out how to? -- Best Li Tianqing__ Open

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

On Feb 2, 2015, at 7:24 PM, Sean Dague mailto:s...@dague.net>> wrote: On 02/02/2015 05:35 PM, Jay Pipes wrote: On 01/29/2015 12:41 PM, Sean Dague wrote: Correct. This actually came up at the Nova mid cycle in a side conversation with Ironic and Neutron folks. HTTP error codes are not sufficientl

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

Agree with Sean. A short error name in response body would be better for applications who consume OpenStack. To my understand, the X-OpenStack-Error-Help-URI proposed by jpipes will be a uri to error resolution method. Usually, a consumer application needn't to load its content. On Feb 3, 2015 9:28

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

On Mon, Feb 2, 2015 at 4:35 PM, Jay Pipes wrote: > On 01/29/2015 12:41 PM, Sean Dague wrote: > >> Correct. This actually came up at the Nova mid cycle in a side >> conversation with Ironic and Neutron folks. >> >> HTTP error codes are not sufficiently granular to describe what happens >> when a R

Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

Sean Dague wrote: > On 02/02/2015 06:06 PM, Mike Bayer wrote: >> Sean Dague wrote: >> >>> On 02/02/2015 04:20 PM, Mark McClain wrote: You’re right that the Mako dependency is really a side effect from Alembic. We used jinja for tempting radvd because it is used by the projec

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

On 02/02/2015 05:35 PM, Jay Pipes wrote: > On 01/29/2015 12:41 PM, Sean Dague wrote: >> Correct. This actually came up at the Nova mid cycle in a side >> conversation with Ironic and Neutron folks. >> >> HTTP error codes are not sufficiently granular to describe what happens >> when a REST service

Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

On 02/02/2015 06:06 PM, Mike Bayer wrote: > > > Sean Dague wrote: > >> On 02/02/2015 04:20 PM, Mark McClain wrote: >>> You’re right that the Mako dependency is really a side effect from Alembic. >>> We used jinja for tempting radvd because it is used by the projects within >>> the OpenStack

Re: [openstack-dev] [Neutron] unable to reproduce bug 1317363‏

Yeah sure From: blak...@gmail.com Date: Mon, 2 Feb 2015 11:09:08 -0800 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev][Neutron] unable to reproduce bug 1317363‏ The mailing list isn't a great place to discuss reproducing a bug. Post this comment on the bug report instead o

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

On Tue, Feb 3, 2015 at 9:05 AM, Jay Pipes wrote: > On 01/29/2015 12:41 PM, Sean Dague wrote: > >> Correct. This actually came up at the Nova mid cycle in a side >> conversation with Ironic and Neutron folks. >> >> HTTP error codes are not sufficiently granular to describe what happens >> when a R

[openstack-dev] [heat] operators vs users for choosing convergence engine

A spec has been raised to add a config option to allow operators to choose whether to use the new convergence engine for stack operations. For some context you should read the spec first [1] Rather than doing this, I would like to propose the following: * Users can (optionally) choose which eng

[openstack-dev] [openstack-operators] UpgradeImpact: Replacing swift_enable_net with swift_store_endpoint

+ openstack-operators On 2/2/15, 12:24 PM, "Jesse Cook" mailto:jesse.c...@rackspace.com>> wrote: Configuration options will change (https://review.openstack.org/#/c/146972/4): - Removed config option: "swift_enable_snet". The default value of "swift_enable_snet" was False [1]. The comments in

Re: [openstack-dev] TaskFlow 0.7.0 released

Thanks for that! Much appreciated :-) Joe Gordon wrote: This broke grenade on stable/juno, here is the fix. https://review.openstack.org/#/c/152333/ On Mon, Feb 2, 2015 at 10:56 AM, Joshua Harlow mailto:harlo...@outlook.com>> wrote: The Oslo team is pleased to announce the release of:

[openstack-dev] UpgradeImpact: Replacing swift_enable_net with swift_store_endpoint

+openstack-operators On 2/2/15, 12:24 PM, "Jesse Cook" mailto:jesse.c...@rackspace.com>> wrote: Configuration options will change (https://review.openstack.org/#/c/146972/4): - Removed config option: "swift_enable_snet". The default value of "swift_enable_snet" was False [1]. The comments ind

Re: [openstack-dev] TaskFlow 0.7.0 released

This broke grenade on stable/juno, here is the fix. https://review.openstack.org/#/c/152333/ On Mon, Feb 2, 2015 at 10:56 AM, Joshua Harlow wrote: > The Oslo team is pleased to announce the release of: > > TaskFlow 0.7.0: taskflow structured state management library. > > For more details, pleas

Re: [openstack-dev] [oslo.db][nova] Use of asynchronous slaves in Nova (was: Deprecating use_slave in Nova)

Matthew Booth wrote: > > Based on my current (and still sketchy) understanding, I think we can > define 3 classes of database node: > > 1. Read/write > 2. Synchronous read-only > 3. Asynchronous read-only > > and 3 code annotations: > > * Writer (must use class 1) > * Reader (prefer class 2

Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

Sean Dague wrote: > On 02/02/2015 04:20 PM, Mark McClain wrote: >> You’re right that the Mako dependency is really a side effect from Alembic. >> We used jinja for tempting radvd because it is used by the projects within >> the OpenStack ecosystem and also used in VPNaaS. > > Jinja is far m

Re: [openstack-dev] [Heat] Convergence Phase 1 implementation plan

On 26/01/15 19:04, Angus Salkeld wrote: On Sat, Jan 24, 2015 at 7:00 AM, Zane Bitter mailto:zbit...@redhat.com>> wrote: I'm also prepared to propose specs for all of these _if_ people think that would be helpful. I see three options here: - Propose 18 fairly minimal specs (maybe in

Re: [openstack-dev] [Keystone] PowerKVM CI reporting

On Mon, Feb 2, 2015 at 4:07 PM, Matt Riedemann wrote: > > > On 2/2/2015 3:52 PM, Kurt Taylor wrote: > >> Thanks Morgan, That's why I wanted to email. We will gladly come to a >> meeting and formally request to comment and will turn off commenting on >> Keystone until then. >> >> Thanks, >> Kurt T

[openstack-dev] [nova][api] How to handle API changes in contrib/*.py

Hello! There have been some discussion on what nova-api should return after a change in the API itself. So, the change that generated this discussion is an API change to 2.2 is: https://review.openstack.org/#/c/140313/23 - **2.2** Added Keypair type. A user can request the creation of a c

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

Sigh... hit send too soon and forgot to sign... +1 to that idea... Ryan Jay Pipes wrote on 02/02/2015 04:35:36 PM: > > What about having a separate HTTP header that indicates the "OpenStack > Error Code", along with a generated URI for finding more information > about the error? > > Something

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

+1 to that idea... Jay Pipes wrote on 02/02/2015 04:35:36 PM: > > What about having a separate HTTP header that indicates the "OpenStack > Error Code", along with a generated URI for finding more information > about the error? > > Something like: > > X-OpenStack-Error-Code: 1234 > X-OpenStack-Er

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

On 01/29/2015 12:41 PM, Sean Dague wrote: Correct. This actually came up at the Nova mid cycle in a side conversation with Ironic and Neutron folks. HTTP error codes are not sufficiently granular to describe what happens when a REST service goes wrong, especially if it goes wrong in a way that w

Re: [openstack-dev] [Heat][Keystone] Native keystone resources in Heat

On 30/01/15 02:19, Thomas Spatzier wrote: From: Zane Bitter To: openstack Development Mailing List Date: 29/01/2015 17:47 Subject: [openstack-dev] [Heat][Keystone] Native keystone resources in Heat I got a question today about creating keystone users/roles/tenants in Heat templates. We cur

Re: [openstack-dev] [Keystone] PowerKVM CI reporting

On 2/2/2015 3:52 PM, Kurt Taylor wrote: Thanks Morgan, That's why I wanted to email. We will gladly come to a meeting and formally request to comment and will turn off commenting on Keystone until then. Thanks, Kurt Taylor (krtaylor) On Mon, Feb 2, 2015 at 3:43 PM, Morgan Fainberg mailto:morg

Re: [openstack-dev] [Keystone] PowerKVM CI reporting

On 02/02/2015 02:52 PM, Kurt Taylor wrote: > Thanks Morgan, That's why I wanted to email. And since we have over 100 third party CI accounts this is why this sort of conversation can take place in channel rather than the mail list. Everyone can attend meetings: https://wiki.openstack.org/wiki/Meet

Re: [openstack-dev] Deprecation of in tree EC2 API in Nova for Kilo release

On 2 February 2015 at 16:29, Sean Dague wrote: > It's really easy to say "someone should do this", but the problem is > that none of the core team is interested, neither is anyone else. Most > of the people that once were interested have left being active in > OpenStack. > > EC2 compatibility doe

Re: [openstack-dev] [oslo] oslo.versionedobjects repository is ready for pre-import review

On Mon, Feb 2, 2015, at 04:33 PM, Doug Hellmann wrote: > I’ve prepared a copy of nova.objects as oslo_versionedobjects in > https://github.com/dhellmann/oslo.versionedobjects-import. The script to > create the repository is part of the update to the spec in > https://review.openstack.org/15.

Re: [openstack-dev] [Keystone] PowerKVM CI reporting

Thanks Morgan, That's why I wanted to email. We will gladly come to a meeting and formally request to comment and will turn off commenting on Keystone until then. Thanks, Kurt Taylor (krtaylor) On Mon, Feb 2, 2015 at 3:43 PM, Morgan Fainberg wrote: > I assumed [my mistake] this was not commenti

Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

On 02/02/2015 04:20 PM, Mark McClain wrote: > You’re right that the Mako dependency is really a side effect from Alembic. > We used jinja for tempting radvd because it is used by the projects within > the OpenStack ecosystem and also used in VPNaaS. Jinja is far more used in other parts of Open

Re: [openstack-dev] [Keystone] PowerKVM CI reporting

I assumed [my mistake] this was not commenting/reporting, just running against Keystone. I expect a more specific request to comment rather than a “hey we’re doing this” if commenting is what is desired. Please come to our weekly meeting if you’re planning on commenting/scoring on keystone patc

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

On February 2, 2015 at 1:31:14 PM, Joe Gordon (joe.gord...@gmail.com) wrote: On Mon, Feb 2, 2015 at 10:28 AM, Morgan Fainberg wrote: I think the simple answer is "yes". We (keystone) should emit notifications. And yes other projects should listen. The only thing really in discussion should be

Re: [openstack-dev] [Keystone] PowerKVM CI reporting

On 02/02/2015 02:16 PM, Morgan Fainberg wrote: > Thank you for the heads up. > > —Morgan > > -- > Morgan Fainberg > > On February 2, 2015 at 1:15:49 PM, Kurt Taylor (kurt.r.tay...@gmail.com) > wrote: > > Just FYI, in case there was any questions, > > In addition to testing and reporting on

Re: [openstack-dev] [Product] [all][log] Openstack HTTP error codes

What I see in this conversation is that we are talking about multiple different user classes. Infra-operator needs as much info as possible, so if it is a vendor driver that is erring out, the dev-ops can see it in the log. Tenant-operator is a totally different class of user. These guys need

[openstack-dev] [oslo] oslo.versionedobjects repository is ready for pre-import review

I’ve prepared a copy of nova.objects as oslo_versionedobjects in https://github.com/dhellmann/oslo.versionedobjects-import. The script to create the repository is part of the update to the spec in https://review.openstack.org/15. Please look over the code so you are familiar with it. Dan an

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

On Mon, Feb 2, 2015 at 10:28 AM, Morgan Fainberg wrote: > I think the simple answer is "yes". We (keystone) should emit > notifications. And yes other projects should listen. > > The only thing really in discussion should be: > > 1: soft delete or hard delete? Does the service mark it as orphaned

Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

You’re right that the Mako dependency is really a side effect from Alembic. We used jinja for tempting radvd because it is used by the projects within the OpenStack ecosystem and also used in VPNaaS. mark > On Feb 2, 2015, at 3:13 PM, Sean M. Collins wrote: > > Sorry, I should have done a b

Re: [openstack-dev] [Keystone] PowerKVM CI reporting

Thank you for the heads up.  —Morgan --  Morgan Fainberg On February 2, 2015 at 1:15:49 PM, Kurt Taylor (kurt.r.tay...@gmail.com) wrote: Just FYI, in case there was any questions, In addition to testing and reporting on Nova, the IBM PowerKVM CI system is now also testing against Keystone pat

[openstack-dev] [Keystone] PowerKVM CI reporting

Just FYI, in case there was any questions, In addition to testing and reporting on Nova, the IBM PowerKVM CI system is now also testing against Keystone patches. We are happy to also be testing keystone patches on PowerKVM, and will be adding other projects soon. Regards, Kurt Taylor (krtaylor)

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On 2015-02-02 23:29:55 +0300 (+0300), Alexandre Levine wrote: > I'll do that when I've got myself acquainted with the weekly meetings > procedure (haven't actually bumped into it before) :) [...] Start from the https://wiki.openstack.org/wiki/Meetings page preamble and follow the instructions link

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On 2/2/15 11:15 PM, Michael Still wrote: On Mon, Feb 2, 2015 at 11:01 PM, Alexandre Levine wrote: Michael, I'm rather new here, especially in regard to communication matters, so I'd also be glad to understand how it's done and then I can drive it if it's ok with everybody. By saying EC2 sub t

Re: [openstack-dev] [nova][libvirt] RFC: ensuring live migration ends

On Mon, Feb 02, 2015 at 01:21:31PM -0500, Andrew Laski wrote: > > On 02/02/2015 11:26 AM, Daniel P. Berrange wrote: > >On Mon, Feb 02, 2015 at 11:19:45AM -0500, Andrew Laski wrote: > >>On 02/02/2015 05:58 AM, Daniel P. Berrange wrote: > >>>On Sun, Feb 01, 2015 at 11:20:08AM -0800, Noel Burton-Krah

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On Mon, Feb 2, 2015 at 11:01 PM, Alexandre Levine wrote: > Michael, > > I'm rather new here, especially in regard to communication matters, so I'd > also be glad to understand how it's done and then I can drive it if it's ok > with everybody. > By saying EC2 sub team - who did you keep in mind? Fr

Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

Sorry, I should have done a bit more grepping before I sent the e-mail, since it appears that Mako is being used by alembic. http://alembic.readthedocs.org/en/latest/tutorial.html So, should we switch the radvd templating over to Mako instead? -- Sean M. Collins ___

[openstack-dev] [Neutron] Multiple template libraries being used in tree - Switch to using only Jinja2?

Hi, During my review of the full-stack tests framework[1], I noticed that Mako was being added as an explicit dependency. I know that in the code for creating radvd configs for IPv6, we use Jinja, but I did a quick git grep and see that we have one file[2] that uses Mako for templating. My intent

[openstack-dev] [Trove] Schedule for Trove Mid-Cycle Sprint

Hi folks: I've updated the schedule for the Trove Mid-Cycle Sprint at https://wiki.openstack.org/wiki/Sprints/TroveKiloSprint#Schedule and have linked the slots on the time-table to the etherpads that we're planning on using to track the discussion. I've also updated the page with some more infor

Re: [openstack-dev] The API WG mission statement

On Fri, 2015-01-30 at 23:05 +, Everett Toews wrote: > To converge the OpenStack APIs to a consistent and pragmatic RESTful > design by creating guidelines that the projects should follow. The > intent is not to create backwards incompatible changes in existing > APIs, but to have new APIs and f

Re: [openstack-dev] [Manila] Manila driver for CephFS

OK, thanks Sebastien and Valeriy. Jake Sebastien Han wrote on 02/02/2015 06:51:10 AM: > From: Sebastien Han > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 02/02/2015 06:54 AM > Subject: Re: [openstack-dev] [Manila] Manila driver for CephFS > > I believe thi

Re: [openstack-dev] [Heat] Talk on Jinja Metatemplates for upcoming summit

Hi Pratik, what would be the aim for this templating? I ask since we in Heat try to keep the imperative logic like e.g. if-else out of heat templates, leaving it to other services. Plus there is already a spec for a heat template function to repeat pieces of template structure [1]. I can definite

Re: [openstack-dev] problems with instance consoles and novnc

On 02/02/2015 01:27 PM, Mathieu Gagné wrote: On 2015-02-02 11:36 AM, Chris Friesen wrote: On 01/30/2015 06:26 AM, Jesse Pretorius wrote: Have you tried manually updating the NoVNC and websockify files to later versions from source? We were already using a fairly recent version of websockify,

Re: [openstack-dev] problems with instance consoles and novnc

On 2015-02-02 11:36 AM, Chris Friesen wrote: On 01/30/2015 06:26 AM, Jesse Pretorius wrote: Have you tried manually updating the NoVNC and websockify files to later versions from source? We were already using a fairly recent version of websockify, but it turns out that we needed to upversion

Re: [openstack-dev] About Sahara Oozie plan

Answers to other questions: 2) (first part) Yes, I think Oozie shell actions are a great idea. I can help work on a spec for this. In general, Sahara should be able to support any kind of Oozie action. Each will require a new job type, changes to the Oozie engine, and a UI form to handle submissi

[openstack-dev] [Infra] Meeting Tuesday February 3rd at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday February 3rd, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone intere

Re: [openstack-dev] [Neutron] unable to reproduce bug 1317363‏

The mailing list isn't a great place to discuss reproducing a bug. Post this comment on the bug report instead of the mailing list. That way the person who reported it and the ones who triaged it can see this information and respond. They might not be watching the dev mailing list as closely. On

Re: [openstack-dev] problems with huge pages and libvirt

- Original Message - > From: "Ian Wells" > To: "OpenStack Development Mailing List (not for usage questions)" > > > On 2 February 2015 at 09:49, Chris Friesen > wrote: > > > On 02/02/2015 10:51 AM, Jay Pipes wrote: > > > >> This is a bug that I discovered when fixing some of the NUMA r

Re: [openstack-dev] About Sahara Oozie plan

Hi, Thanks for your patience. I have been consumed with spark-swift, but I can start to address these questions now :) On (1) (a) below, I will try to reproduce and look at how we can better support classpath in EDP. I'll let you know what I find. We may need to add some configuration options

[openstack-dev] TaskFlow 0.7.0 released

The Oslo team is pleased to announce the release of: TaskFlow 0.7.0: taskflow structured state management library. For more details, please see the git log history below and: http://launchpad.net/taskflow/+milestone/0.7.0 Please report issues through launchpad: http://bugs.launchpad.net/taskf

[openstack-dev] [Keystone] Sample Config Update (until final decision by larger thread occurs)

I am making a quick change in how Keystone is handling updates to the sample config files until all of those discussion points are addressed in the big thread of “how do we handle sample configs". These changes are just to help limit rebase issues and make contributions a bit easier to manage:

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On 2/2/15 8:30 PM, Matthew Treinish wrote: On Mon, Feb 02, 2015 at 07:35:46PM +0300, Alexandre Levine wrote: Thank you Sean. We'll be tons of EC2 Tempest tests for your attention shortly. How would you prefer them? In several reviews, I believe. Not in one, right? Let's take a step back for a

Re: [openstack-dev] problems with huge pages and libvirt

On 02/02/2015 12:13 PM, Ian Wells wrote: On 2 February 2015 at 09:49, Chris Friesen Indeed. Does tempest support hugepages/NUMA/pinning? This is a running discussion, but largely no - because this is ited to the capabilities of the host, there's no guarantee for a given scenario what re

[openstack-dev] [Heat] Talk on Jinja Metatemplates for upcoming summit

Hello Heat Developers, As part of an internal development project at Rackspace, I implemented a mechanism to allow using Jinja templating system in heat templates. I was hoping to give a talk on the same for the upcoming summit (which will be the first summit after I started working on openstac

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

I think the simple answer is "yes". We (keystone) should emit notifications. And yes other projects should listen. The only thing really in discussion should be: 1: soft delete or hard delete? Does the service mark it as orphaned, or just delete (leave this to nova, cinder, etc to discuss) 2:

[openstack-dev] UpgradeImpact: Replacing swift_enable_net with swift_store_endpoint

Configuration options will change (https://review.openstack.org/#/c/146972/4): - Removed config option: "swift_enable_snet". The default value of "swift_enable_snet" was False [1]. The comments indicated not to change this default value unless you are Rackspace [2]. - Added config option "swi

Re: [openstack-dev] [nova][libvirt] RFC: ensuring live migration ends

On 02/02/2015 11:26 AM, Daniel P. Berrange wrote: On Mon, Feb 02, 2015 at 11:19:45AM -0500, Andrew Laski wrote: On 02/02/2015 05:58 AM, Daniel P. Berrange wrote: On Sun, Feb 01, 2015 at 11:20:08AM -0800, Noel Burton-Krahn wrote: Thanks for bringing this up, Daniel. I don't think it makes sen

[openstack-dev] [Neutron] unable to reproduce bug 1317363‏

Hi, I am Bharath Thiruveedula. I am new to openstack neutron and networking. I am trying to solve the bug 1317363. But I am unable to reproduce that bug. The steps I have done to reproduce: 1)I have created with network with external = True2)Created a subnet for the above network with CIDR=172.2

Re: [openstack-dev] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

On Mon, Feb 02, 2015 at 11:46:53AM -0600, Matt Riedemann wrote: > This came up in the operators mailing list back in June [1] but given the > subject probably didn't get much attention. > > Basically there is a really old bug [2] from Grizzly that is still a problem > and affects multiple projects

Re: [openstack-dev] problems with huge pages and libvirt

On 2 February 2015 at 09:49, Chris Friesen wrote: > On 02/02/2015 10:51 AM, Jay Pipes wrote: > >> This is a bug that I discovered when fixing some of the NUMA related nova >> objects. I have a patch that should fix it up shortly. >> > > Any chance you could point me at it or send it to me? > > T

[openstack-dev] [sahara] Spark CDH followup and questions related to DIB

Hello all, I tried a Spark image with the cdh5 element Daniele describes below, but it did not fix the jackson version issue. The spark assembly still depends on inconsistent versions. Looking into the spark git a little bit more, I discovered that in the cdh5-1.2.0_5.3.0 branch the jackson v

Re: [openstack-dev] problems with huge pages and libvirt

On Mon, Feb 02, 2015 at 11:49:26AM -0600, Chris Friesen wrote: > On 02/02/2015 10:51 AM, Jay Pipes wrote: > >This is a bug that I discovered when fixing some of the NUMA related nova > >objects. I have a patch that should fix it up shortly. > > Any chance you could point me at it or send it to me?

Re: [openstack-dev] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

On 2/2/2015 11:46 AM, Matt Riedemann wrote: This came up in the operators mailing list back in June [1] but given the subject probably didn't get much attention. Basically there is a really old bug [2] from Grizzly that is still a problem and affects multiple projects. A tenant can be deleted

Re: [openstack-dev] problems with huge pages and libvirt

On 02/02/2015 10:51 AM, Jay Pipes wrote: This is a bug that I discovered when fixing some of the NUMA related nova objects. I have a patch that should fix it up shortly. Any chance you could point me at it or send it to me? This is what happens when we don't have any functional testing of stu

[openstack-dev] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

This came up in the operators mailing list back in June [1] but given the subject probably didn't get much attention. Basically there is a really old bug [2] from Grizzly that is still a problem and affects multiple projects. A tenant can be deleted in Keystone even though other resources in

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On Mon, Feb 02, 2015 at 08:07:27PM +0300, Alexandre Levine wrote: > > On 2/2/15 7:39 PM, Sean Dague wrote: > >On 02/02/2015 11:35 AM, Alexandre Levine wrote: > >>Thank you Sean. > >> > >>We'll be tons of EC2 Tempest tests for your attention shortly. > >>How would you prefer them? In several review

Re: [openstack-dev] problems with huge pages and libvirt

On 02/02/2015 11:00 AM, Sahid Orentino Ferdjaoui wrote: On Mon, Feb 02, 2015 at 10:44:09AM -0600, Chris Friesen wrote: Hi, I'm trying to make use of huge pages as described in "http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/virt-driver-large-pages.html";. I'm running kil

[openstack-dev] [Swift] Swift 2.2.2 released today

Everyone, I'm happy to announce that today we have release Swift 2.2.2. (Yes, that's 2.2.2 on 2/2.) This release has a few very important features that came directly from production clusters. I recommend that you upgrade so you can take advantage of the new goodness. As always, you can upgrade to

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On Mon, Feb 02, 2015 at 07:35:46PM +0300, Alexandre Levine wrote: > Thank you Sean. > > We'll be tons of EC2 Tempest tests for your attention shortly. > How would you prefer them? In several reviews, I believe. Not in one, right? Let's take a step back for a sec. How many tests and what kind are

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On 2/2/15 7:04 PM, Sean Dague wrote: On 02/02/2015 07:01 AM, Alexandre Levine wrote: Michael, I'm rather new here, especially in regard to communication matters, so I'd also be glad to understand how it's done and then I can drive it if it's ok with everybody. By saying EC2 sub team - who did

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On 2/2/15 7:39 PM, Sean Dague wrote: On 02/02/2015 11:35 AM, Alexandre Levine wrote: Thank you Sean. We'll be tons of EC2 Tempest tests for your attention shortly. How would you prefer them? In several reviews, I believe. Not in one, right? Best regards, Alex Levine So, honestly, I think

[openstack-dev] [mistral] Team meeting minutes/log - 02/02/2014

Thanks for joining us today for team meeting! Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-02-02-16.00.html Full log: http://eavesdrop.openstack.org/meetings/mistral/201

Re: [openstack-dev] problems with huge pages and libvirt

On Mon, Feb 02, 2015 at 11:51:47AM -0500, Jay Pipes wrote: > This is a bug that I discovered when fixing some of the NUMA related nova > objects. I have a patch that should fix it up shortly. Never seen this issue, could be great to have a bug repported. > This is what happens when we don't have

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On 02/02/2015 11:35 AM, Alexandre Levine wrote: > Thank you Sean. > > We'll be tons of EC2 Tempest tests for your attention shortly. > How would you prefer them? In several reviews, I believe. Not in one, > right? > > Best regards, > Alex Levine So, honestly, I think that we should probably look

Re: [openstack-dev] problems with huge pages and libvirt

On Mon, Feb 02, 2015 at 10:44:09AM -0600, Chris Friesen wrote: > Hi, > > I'm trying to make use of huge pages as described in > "http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/virt-driver-large-pages.html";. > I'm running kilo as of Jan 27th. > I've allocated 1 2MB page

Re: [openstack-dev] [neutron] high dhcp lease times in neutron deployments considered harmful (or not???)

Kevin, I think we are finally converging. One of the points I've been trying to make is that users are playing with fire when they start playing with some of these port attributes, and given the tool we have to work with (DHCP), the instantiation of these changes cannot be made seamlessly to a VM

Re: [openstack-dev] problems with huge pages and libvirt

This is a bug that I discovered when fixing some of the NUMA related nova objects. I have a patch that should fix it up shortly. This is what happens when we don't have any functional testing of stuff that is merged into master... Best, -jay On 02/02/2015 11:44 AM, Chris Friesen wrote: Hi,

Re: [openstack-dev] [Heat][Keystone] Native keystone resources in Heat

On 01/30/2015 02:19 AM, Thomas Spatzier wrote: From: Zane Bitter To: openstack Development Mailing List Date: 29/01/2015 17:47 Subject: [openstack-dev] [Heat][Keystone] Native keystone resources in Heat I got a question today about creating keystone users/roles/tenants in Heat templates. We

[openstack-dev] problems with huge pages and libvirt

Hi, I'm trying to make use of huge pages as described in "http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/virt-driver-large-pages.html";. I'm running kilo as of Jan 27th. I've allocated 1 2MB pages on a compute node. "virsh capabilities" on that node contains:

Re: [openstack-dev] [all][tc] SQL Schema Downgrades and Related Issues

On 01/29/2015 03:11 PM, Mike Bayer wrote: Morgan Fainberg wrote: Are downward migrations really a good idea for us to support? Is this downward migration path a sane expectation? In the real world, would any one really trust the data after migrating downwards? It’s a good idea for a migrat

Re: [openstack-dev] [Fuel] Cluster replaced deployment of provisioning information

Hi Dmitry, I've read about inventories and I'm not sure if it's what we really need, inventory provides you a way to have some kind of nodes discovery mechanism, but what we need is to get some abstract data and convert the data to more tasks friendly format. In another thread I've mentioned Vari

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On 02/02/2015 11:35 AM, Alexandre Levine wrote: > Thank you Sean. > > We'll be tons of EC2 Tempest tests for your attention shortly. > How would you prefer them? In several reviews, I believe. Not in one, > right? > > Best regards, > Alex Levine So, honestly, I think that we should probably lo

Re: [openstack-dev] [all][tc] SQL Schema Downgrades and Related Issues

On 01/30/2015 07:23 AM, Sandy Walsh wrote: From: Johannes Erdfelt [johan...@erdfelt.com] Sent: Thursday, January 29, 2015 9:18 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all][tc] SQL Schema Downgrades

Re: [openstack-dev] problems with instance consoles and novnc

On 01/30/2015 06:26 AM, Jesse Pretorius wrote: On 29 January 2015 at 04:57, Chris Friesen mailto:chris.frie...@windriver.com>> wrote: On 01/28/2015 10:33 PM, Mathieu Gagné wrote: On 2015-01-28 11:13 PM, Chris Friesen wrote: Anyone have any suggestions on where to start

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

Thank you Sean. We'll be tons of EC2 Tempest tests for your attention shortly. How would you prefer them? In several reviews, I believe. Not in one, right? Best regards, Alex Levine On 2/2/15 6:55 PM, Sean Dague wrote: On 02/02/2015 07:01 AM, Alexandre Levine wrote: Michael, I'm rather new

Re: [openstack-dev] [api] API Definition Formats

On 02/02/2015 10:26 AM, Chris Dent wrote: pecan-swagger looks cool but presumably pecan has most of the info you're putting in the decorators in itself already? So, given an undecorated pecan app, would it be possible to provide it to a function and have that function output all the paths? you

Re: [openstack-dev] Deprecation of in tree EC2 API in Nova for Kilo release

On 02/02/2015 10:55 AM, Daniel P. Berrange wrote: > On Mon, Feb 02, 2015 at 07:44:24AM -0800, Dan Smith wrote: >>> I'm with Daniel on that one. We shouldn't "deprecate" until we are 100% >>> sure that the replacement is up to the task and that strategy is solid. >> >> My problem with this is: If th

Re: [openstack-dev] [nova][libvirt] RFC: ensuring live migration ends

On Mon, Feb 02, 2015 at 11:19:45AM -0500, Andrew Laski wrote: > > On 02/02/2015 05:58 AM, Daniel P. Berrange wrote: > >On Sun, Feb 01, 2015 at 11:20:08AM -0800, Noel Burton-Krahn wrote: > >>Thanks for bringing this up, Daniel. I don't think it makes sense to have > >>a timeout on live migration,

Re: [openstack-dev] [nova][libvirt] RFC: ensuring live migration ends

On 02/02/2015 05:58 AM, Daniel P. Berrange wrote: On Sun, Feb 01, 2015 at 11:20:08AM -0800, Noel Burton-Krahn wrote: Thanks for bringing this up, Daniel. I don't think it makes sense to have a timeout on live migration, but operators should be able to cancel it, just like any other unbounded l

  1   2   >