Re: [openstack-dev] [nova] Do we need new nova configuration option to show compute nodes with shared_storage or not ?

长波， 你对oslo比较熟，能帮我看看这个问题吗， https://answers.launchpad.net/oslo.config/+question/261550 On Tue, Jan 27, 2015 at 12:13 PM, ChangBo Guo wrote: > Hi ALL, > > I have been working on bug 1414432 [1] recently, I would like do more > discussion before further work. > > I'm talking about libvirt dri

Re: [openstack-dev] [nova] Do we need new nova configuration option to show compute nodes with shared_storage or not ?

I'm sorry, my mistake due to my negligence, pls ignore my above reply. sorry. On Mon, Feb 2, 2015 at 4:04 PM, Joshua Zhang wrote: > 长波， > 你对oslo比较熟，能帮我看看这个问题吗， > https://answers.launchpad.net/oslo.config/+question/261550 > > On Tue, Jan 27, 2015 at 12:13 PM, ChangBo Guo wrote: > >> Hi ALL

Re: [openstack-dev] [neutron][ml2] How to get compute host details

ML2 makes the hostname available in the context it passes to the drivers via the 'host' attribute.[1] This is the only thing Neutron knows about the compute node using the port. 1. https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/driver_api.py#L776 On Sun, Feb 1, 2015 at 10:11

Re: [openstack-dev] [oslo.db] PyMySQL review

On Fri, Jan 30 2015, Yuriy Taraday wrote: > That's a great research! Under its impression I've spent most of last > evening reading PyMySQL sources. It looks like it not as much need C > speedups currently as plain old Python optimizations. Protocol parsing code > seems very inefficient (chained s

Re: [openstack-dev] [neutron][ml2] How to get compute host details

Thanks Kevin for reply. But 'host' attribute returns me the controller hostname and not compute host name. I am having multi node setup, and I want to know compute host where the VM get launch. On Mon, Feb 2, 2015 at 2:19 PM, Kevin Benton wrote: > ML2 makes the hostname available in the context

[openstack-dev] [Ironic] mid cycle etherpad

Hi folks! I've tossed up an etherpad for folks at (or not at) the mid cycle sprints to share ideas and such. This might seem last-minute (and it is). I don't have a specific agenda -- aside from what's on launchpad, what's on gerrit, and what's on your mind. Really, I'd like us to make progress t

[openstack-dev] Fwd: Image Upload error while installing devstack on CI slave machine.

Hi all, For the past few days I have been facing the problem of getting the image upload error while installation of devstack in my CI. The devstack installation is triggered in CI when someone does the checkin, and the failure cause comes out to be the same. Below is the log for the error: *201

Re: [openstack-dev] [Fuel] Logs format on UI (High/6.0)

Hello, (resurrecting this old thread because I think I found the root cause) The problem affects all OpenStack environments using Syslog, not only Fuel-based installations: when use_syslog is true, the logging_context_format_string and logging_default_format_string parameters aren't taken into acc

Re: [openstack-dev] Fwd: Image Upload error while installing devstack on CI slave machine.

Hi Abhishek, This is bug https://launchpad.net/bugs/1415795 introduced by https://review.openstack.org/#/c/142967/ because Swift doesn't use olso.config. The fix is at https://review.openstack.org/#/c/151506/ which has not yet been approved, but if you can cherry-pick it for your CI it should g

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

On Fri, Jan 30, 2015 at 04:38:44PM -0600, Matt Riedemann wrote: > > > On 1/30/2015 3:16 PM, Soren Hansen wrote: > >As I've said a couple of times in the past, I think the > >architecturally sound approach is to keep this inside Nova. > > > >The two main reasons are: > > * Having multiple fronten

Re: [openstack-dev] Fwd: Image Upload error while installing devstack on CI slave machine.

Hi Bob, Thanks for the reply, this is really a great help for me. On Mon, Feb 2, 2015 at 3:11 PM, Bob Ball wrote: > Hi Abhishek, > > > > This is bug https://launchpad.net/bugs/1415795 introduced by > https://review.openstack.org/#/c/142967/ because Swift doesn't use > olso.config. > > > > The

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

On Fri, Jan 30, 2015 at 07:57:08PM +, Tim Bell wrote: > Alex, > > > > Many thanks for the constructive approach. I've added an item to the list for > the Ops meetup in March to see who would be interested to help. > > > > As discussed on the change, it is likely that there would need to

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

On 30/01/15 19:06, Mike Bayer wrote: > > > Matthew Booth wrote: > >> At some point in the near future, hopefully early in L, we're intending >> to update Nova to use the new database transaction management in >> oslo.db's enginefacade. >> >> Spec: >> http://git.openstack.org/cgit/openstack/oslo

Re: [openstack-dev] [neutron][ml2] How to get compute host details

Your VM must be launched on the controller node then. In a multi-node setup the controller will also act as a compute node unless you have disabled the n-cpu service. The 'host' attribute is specifically to indicate where a port is being used. It's not for anything else. On Mon, Feb 2, 2015 at 1:1

Re: [openstack-dev] [Cinder][nova] Cinder backend for ephemeral disks?

Hi, It was not re-proposed for Kilo as there is basic work ongoing in Cinder to create a common library Brick that can be used by Cinder and Nova. There might be a chance in L* to get it in. Would be nice to get some people together working on it /Tobi -Original Message- From: Michael St

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

On Sat, Jan 31, 2015 at 03:55:23AM +0100, Vladik Romanovsky wrote: > > > - Original Message - > > From: "Daniel P. Berrange" > > To: openstack-dev@lists.openstack.org, > > openstack-operat...@lists.openstack.org > > Sent: Friday, 30 January, 2015 11:47:16 AM > > Subject: [openstack-dev]

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

On Mon, Feb 02, 2015 at 08:24:20AM +1300, Robert Collins wrote: > On 31 January 2015 at 05:47, Daniel P. Berrange wrote: > > In working on a recent Nova migration bug > > > > https://bugs.launchpad.net/nova/+bug/1414065 > > > > I had cause to refactor the way the nova libvirt driver monitors liv

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

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 long-running process. For example, there's > no

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

On Sun, Feb 01, 2015 at 03:03:45PM -0700, David Medberry wrote: > I'll second much of what Rob said: > API that indicated how many live-migrations (l-m) were going would be good. > API that told you what progress (and start time) a given l-m had made would > be great. > API to cancel a given l-m wo

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

Hi Ken, 1 imageRef isn't the only attribute, which could receive an image id. There are kernelId, ramdiskId, and even bdm v2 as well. So we couldn't guess which attribute has the invalid value. 2 Besides NotFound case, other mixed cases are there. Such as attaching of a volume. A mountpoint can b

Re: [openstack-dev] [oslo.db] PyMySQL review

On Mon Feb 02 2015 at 11:49:31 AM Julien Danjou wrote: > On Fri, Jan 30 2015, Yuriy Taraday wrote: > > > That's a great research! Under its impression I've spent most of last > > evening reading PyMySQL sources. It looks like it not as much need C > > speedups currently as plain old Python optimi

Re: [openstack-dev] [python-novaclient][nova] future of --os-compute-api-version option and whole api versioning

On Sat, Jan 31, 2015 at 4:09 AM, Andrey Kurilin wrote: > Thanks for the answer. Can I help with implementation of novaclient part? > Sure! Do you think its something you can get proposed into Gerrit by the end of the week or very soon after? Its the sort of timeframe we're looking for to get mic

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

Daniel, On 2/2/15 12:58 PM, Daniel P. Berrange wrote: On Fri, Jan 30, 2015 at 07:57:08PM +, Tim Bell wrote: Alex, Many thanks for the constructive approach. I've added an item to the list for the Ops meetup in March to see who would be interested to help. As discussed on the change,

Re: [openstack-dev] [cinder] K-2 Review-a-thon

Hi Mike, There is 2 features[1][2][3] of HNAS driver that still are not approved/targeted. Is there anything missing to then to be approved? Erlon [1] https://blueprints.launchpad.net/cinder/+spec/hds-hnas-ssh-backend [2] https://blueprints.launchpad.net/cinder/+spec/hds-hnas-pool-aware-sched [

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

On Mon, Feb 02, 2015 at 02:45:53PM +0300, Alexandre Levine wrote: > Daniel, > > On 2/2/15 12:58 PM, Daniel P. Berrange wrote: > >On Fri, Jan 30, 2015 at 07:57:08PM +, Tim Bell wrote: > >>Alex, > >> > >> > >> > >>Many thanks for the constructive approach. I've added an item to the list > >>for

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

>The only thing this discussion has convinced me of is that allowing users to change the fixed IP address on a neutron port leads to a bad user-experience. Not as bad as having to delete a port and create another one on the same network just to change addresses though... >Even with an 8-minute re

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

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? From my team 3 persons are involved. From the technical point of

Re: [openstack-dev] [python-novaclient][nova] future of --os-compute-api-version option and whole api versioning

Thanks for the summary, I'll try to send first patch(maybe WIP) in few days. On Mon, Feb 2, 2015 at 1:43 PM, Christopher Yeoh wrote: > > > On Sat, Jan 31, 2015 at 4:09 AM, Andrey Kurilin > wrote: > >> Thanks for the answer. Can I help with implementation of novaclient part? >> > > Sure! Do you

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

I believe this will start somewhere after Kilo. > On 28 Jan 2015, at 22:59, Valeriy Ponomaryov wrote: > > Hello Jake, > > Main thing, that should be mentioned, is that blueprint has no assignee. > Also, It is created long time ago without any activity after it. > I did not hear any intentions

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

On 01/30/2015 06:18 PM, Dean Troyer wrote: > On Fri, Jan 30, 2015 at 4:57 PM, Everett Toews > mailto:everett.to...@rackspace.com>> wrote: > > What is the API WG mission statement? > > > It's more of a mantra than a Mission Statement(TM): > > Identify existing and future best practices in Op

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

On Fri, 30 Jan 2015, 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 future versions of e

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

> >> But why to add another interface when there is one already (rest api)? > > I'm ok if we decide to use REST API, but of course there is a problem which > we should solve, like versioning, which is much harder to support, than > versioning > in core-serializers. Also do you have any ideas how it

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

- Original Message - > From: "Daniel P. Berrange" > To: "Robert Collins" > Cc: "OpenStack Development Mailing List (not for usage questions)" > , > openstack-operat...@lists.openstack.org > Sent: Monday, 2 February, 2015 5:56:56 AM > Subject: Re: [openstack-dev] [nova][libvirt] RFC: en

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

Daniel P. Berrange wrote: > On Fri, Jan 30, 2015 at 04:38:44PM -0600, Matt Riedemann wrote: >> Deprecation isn't a one-way street really, nova-network was deprecated for a >> couple of releases and then undeprecated and opened up again for feature >> development (at least for a short while until t

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

On Thu, 29 Jan 2015, michael mccune wrote: in a similar vein, i started to work on marking up the sahara and barbican code bases to produce swagger. for sahara this was a little easier as flask makes it simple to query the paths. for barbican i started a pecan-swagger[1] project to aid in mark

[openstack-dev] [neutron] Team meeting today

Just a reminder, we'll have the weekly Neutron meeting [1] at 2100UTC in #openstack-meeting today. We'll likely spend the majority of the time going over any critical bugs, as well as covering BPs for Kilo-2 which have yet to land this week. The other two standing items we'll discuss are the nova-n

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

> 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 there wasn't a stackforge project, what would we do? Nova's in-tree EC2 support has been rotting for years now, and despit

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

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 you keep in mind? From my tea

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

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 there wasn't a stackforge project, what > would we do?

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

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 you keep in mind? From my tea

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

On 02/02/2015 12:54 AM, Christopher Yeoh wrote: > > > On Sun, Feb 1, 2015 at 2:57 AM, Sean Dague > wrote: > > On 01/31/2015 05:24 AM, Duncan Thomas wrote: > > Hi > > > > This discussion came up at the cinder mid-cycle last week too, > > specifically in

[openstack-dev] Python 3 is dead, long live Python 3

After a long wait and much testing, we've merged a change[1] which moves the remainder of Python 3.3 based jobs to Python 3.4. This is primarily in service of getting rid of the custom workers we implemented to perform 3.3 testing more than a year ago, since we can now run 3.4 tests on normal Ubunt

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

On 02/01/2015 06:20 PM, Morgan Fainberg wrote: > Putting on my "sorry-but-it-is-my-job-to-get-in-your-way" hat (aka security), > let's be careful how generous we are with the user and data we hand back. It > should give enough information to be useful but no more. I don't want to see > us opened

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

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] 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] [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] [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] 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] [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] [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] [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] [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

[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] [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

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] [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

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] [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 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

[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] [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

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 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

[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 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] 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] 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

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 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?

[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 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

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

[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] [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] 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] [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] [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] 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

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

[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:

[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

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

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] [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

[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] 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

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] 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] [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] [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] 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

[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

[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

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 ___

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] [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 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] [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

  1   2   >