Re: [openstack-dev] [PKG-Openstack-devel][horizon][xstatic] XStatic-Angular-Bootstrap in violation of the MIT/Expat license (forwarded from: python-xstatic-angular-bootstrap_0.11.0.2-1_amd64.changes R

On 05/05/2015 05:05 PM, Michael Krotscheck wrote: The real question seems to be whether packagers have a disproportionate amount of power to set development goals, tools, and policy. This is a common theme that I've encountered frequently, and it leads to no small amount of tension. This tensi

Re: [openstack-dev] How to turn tempest CLI tests into python-*client in-tree functional tests

On 14 February 2015 at 10:26, Joe Gordon wrote: > Digging through the logs this originated from this bug: > https://bugs.launchpad.net/tempest/+bug/1260710 > > Its probably not needed everywhere and in all the clients. So I've looked more closely at this. Its actually an antipattern. It tells te

Re: [openstack-dev] [TripleO] Core reviewer update proposal

On 05/05/2015 01:57 PM, James Slagle wrote: Hi, I'd like to propose adding Giulio Fidente and Steve Hardy to TripleO Core. Giulio has been an active member of our community for a while. He worked on the HA implementation in the elements and recently has been making a lot of valuable contribution

Re: [openstack-dev] [Nova][Ironic] Large number of ironic driver bugs in nova

Hi > I noticed last night that there are 23 bugs currently filed in nova > tagged as ironic related. Whilst some of those are scheduler issues, a > lot of them seem like things in the ironic driver itself. > > Does the ironic team have someone assigned to work on these bugs and > generally keep an

Re: [openstack-dev] [Fuel] Transaction scheme

Hi! The refactoring of transactions management in Nailgun is critically required for scaling. First of all I propose to wrap HTTP handlers by begin/commit/rollback decorator. After that we should introduce transactions wrapping decorator into Task execute/message calls. And the last one is the wr

Re: [openstack-dev] How to turn tempest CLI tests into python-*client in-tree functional tests

On Wed, 6 May 2015, Robert Collins wrote: Its actually an antipattern. It tells testr that tests are appearing and disappearing depending on what test entry point a user runs each time. testr expects the set of tests to only change when code changes. So, I fully expect that this pattern is goi

Re: [openstack-dev] [Fuel] Transaction scheme

On Wed, May 6, 2015 at 10:51 AM, Alexander Kislitsky wrote: > Hi! > > The refactoring of transactions management in Nailgun is critically required > for scaling. > > First of all I propose to wrap HTTP handlers by begin/commit/rollback > decorator. > After that we should introduce transactions wra

Re: [openstack-dev] How to turn tempest CLI tests into python-*client in-tree functional tests

On 05/06/2015 04:57 AM, Chris Dent wrote: > On Wed, 6 May 2015, Robert Collins wrote: > >> Its actually an antipattern. It tells testr that tests are appearing >> and disappearing depending on what test entry point a user runs each >> time. >> >> testr expects the set of tests to only change when

Re: [openstack-dev] [all] cross project communication: periodic developer newsletter?

Hugh Blemings wrote: > +2 > > I think asking LWN if they have the bandwidth and interest to do this > would be ideal - they've credibility in the Free/Open Source space and a > proven track record. Nice people too. On the bandwidth side, as a regular reader I was under the impression that they s

Re: [openstack-dev] [Nova][Ironic] Large number of ironic driver bugs in nova

On 6 May 2015 at 09:39, Lucas Alvares Gomes wrote: > Hi > >> I noticed last night that there are 23 bugs currently filed in nova >> tagged as ironic related. Whilst some of those are scheduler issues, a >> lot of them seem like things in the ironic driver itself. >> >> Does the ironic team have so

Re: [openstack-dev] [Fuel] Transaction scheme

> First of all I propose to wrap HTTP handlers by begin/commit/rollback I don't know what you are talking about, but we do wrap handlers in transaction for a long time. Here's the code https://github.com/stackforge/fuel-web/blob/2de3806128f398d192d7e31f4ca3af571afeb0b2/nailgun/nailgun/api/v1/handl

Re: [openstack-dev] [all] cross project communication: periodic developer newsletter?

Joe Gordon wrote: > On Tue, May 5, 2015 at 9:53 AM, James Bottomley wrote: > On Tue, 2015-05-05 at 10:45 +0200, Thierry Carrez wrote: > > The issue is, who can write such content ? It is a full-time job to > > produce authored content, you can't just copy (or link to) content > > pr

Re: [openstack-dev] [Fuel] Transaction scheme

I mean, that we should have explicitly wrapped http handlers. For example: @transaction def PUT(...): ... We don't need transactions, for example, in GET methods. I propose to rid of complex data flows in our code. Code with 'commit' call inside the the method should be split into independent

Re: [openstack-dev] [nova] Which error code should we return when OverQuota

It does, however I looked through the history of that repo, and that's just in one of Jay's documents that predates the group. I'm a little cautious to give it a lot of weight without rationale. Honestly, there is this obsession of assuming that there *are* good fits for HTTP status codes for non

[openstack-dev] [Fuel][Plugin] Contributor license agreement for fuel plugin code?

If fuel plugin code is checked into a stackforge repository (as suggested in the fuel plugin wiki https://wiki.openstack.org/wiki/Fuel/Plugins#Repo), who owns that code? Is there a contributor license agreement to sign? (For example, contributors to OpenStack would sign this https://review.open

Re: [openstack-dev] [nova] Which error code should we return when OverQuota

On Wed, 6 May 2015, Sean Dague wrote: All other client errors, just be a 400. And use the emerging error reporting json to actually tell the client what's going on. Please do not do this. Please use the 4xx codes as best as you possibly can. Yes, they don't always match, but there are several

[openstack-dev] [Fuel] LBaaS in version 5.1

HI all, Recently i used Fuel 5.1 to deploy Openstack Icehouse on a Lab (PoC) and a request came with enabling Neutron LBaaS. I have looked up on Fuel doc to see if this is supported in the version i'm running but failed ot find anything. Anyone can point me to any docs which mentioned a) yes it

Re: [openstack-dev] [TripleO] Core reviewer update proposal

On Tue, 2015-05-05 at 07:57 -0400, James Slagle wrote: > Hi, I'd like to propose adding Giulio Fidente and Steve Hardy to TripleO Core. > > Giulio has been an active member of our community for a while. He > worked on the HA implementation in the elements and recently has been > making a lot of va

Re: [openstack-dev] [Fuel][Plugin] Contributor license agreement for fuel plugin code?

On 2015-05-06 11:02:42 + (+), Emma Gordon (projectcalico.org) wrote: > If fuel plugin code is checked into a stackforge repository (as > suggested in the fuel plugin wiki > https://wiki.openstack.org/wiki/Fuel/Plugins#Repo), who owns that > code? I am not a lawyer, but my understanding is

Re: [openstack-dev] [nova] Which error code should we return when OverQuota

On 05/06/2015 07:11 AM, Chris Dent wrote: > On Wed, 6 May 2015, Sean Dague wrote: > >> All other client errors, just be a 400. And use the emerging error >> reporting json to actually tell the client what's going on. > > Please do not do this. Please use the 4xx codes as best as you > possibly ca

[openstack-dev] [cinder][nova] Question on Cinder client exception handling

Hi In order to work on [1] , nova need to know what kind of exception are raised when using cinderclient so that it can handle like [2] did? In this case, we don't need to distinguish the error case based on string compare , it's more accurate and less error leading

[openstack-dev] [heat][ceilometer] autoscaling

hey there, Please I wanna know if their is anyway I can have cpu, ram and network meters for each VM returned by ceilometer to heat for autoscaling tasks? In advance, thank you for your response, Sara __ OpenStack Development

Re: [openstack-dev] Fuel][Plugin] Contributor license agreement for fuel plugin code?

provisions above is to minimize the impact of such > > extensions on API portability. > > > > Thanks for reading and thanks in advance for your feedback, > > Salvatore > > > > The title of this post has been inspired by [2] (the m

[openstack-dev] [oslo.config] MultiStrOpt VS. ListOpt

Hi, devs I come across a problem that crudini cannot handle MultiStrOpt[1], I don't know why such type configuration option is needed. It seems ListOpt is a better choice. Currently I find lots of MultiStrOpt options in both Nova and Ceilometer, and I think other projects have too. Here are my qu

Re: [openstack-dev] [neutron][api] Extensions out, Micro-versions in

Hi Salvatore, Two questions/remarks below. From: Salvatore Orlando mailto:sorla...@nicira.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: onsdag 6 maj 2015 00:13 To: OpenStack Development Mailing List mailto:opensta

Re: [openstack-dev] [heat][ceilometer] autoscaling

On 06/05/15 08:25, ICHIBA Sara wrote: hey there, Please I wanna know if their is anyway I can have cpu, ram and network meters for each VM returned by ceilometer to heat for autoscaling tasks? In advance, thank you for your response, Sara The openstack-dev list is for discussing future develo

[openstack-dev] [all] TC Communications planning

Hi all, In the interest of communicating sooner rather than later, I wanted to write a new thread to say that Flavio Percoco and I are going to work on a TC communications plan as co-chairs of a TC communications working group. I think we can find a happy medium amongst meeting minutes, gerrit re

Re: [openstack-dev] [oslo.config] MultiStrOpt VS. ListOpt

On Wed, May 06 2015, ZhiQiang Fan wrote: > I come across a problem that crudini cannot handle MultiStrOpt[1], I don't > know why such type configuration option is needed. It seems ListOpt is a > better choice. Currently I find lots of MultiStrOpt options in both Nova > and Ceilometer, and I think

Re: [openstack-dev] [all] cross project communication: periodic developer newsletter?

On Wed, 2015-05-06 at 11:54 +0200, Thierry Carrez wrote: > Hugh Blemings wrote: > > +2 > > > > I think asking LWN if they have the bandwidth and interest to do this > > would be ideal - they've credibility in the Free/Open Source space and a > > proven track record. Nice people too. > > On the b

Re: [openstack-dev] [Neutron][IPAM] Do we need migrate script for neutron IPAM now?

I agree, we should amend it to not run pluggable IPAM as the default for now. When we decide to make it the default, the migration scripts will be needed. John On 5/5/15, 1:47 PM, "Salvatore Orlando" mailto:sorla...@nicira.com>> wrote: Patch #153236 is introducing pluggable IPAM in the db bas

Re: [openstack-dev] [Fuel] LBaaS in version 5.1

Hi Daniel, Unfortunately, we never supported LBaaS until Fuel 6.0 when plugin system was introduced and LBaaS plugin was created. So, I think than docs about it never existed for 5.1. But as I know, you can easily install LBaaS in 5.1 (it should be shipped in our repos) and configure it with accor

Re: [openstack-dev] [oslo.config] MultiStrOpt VS. ListOpt

ZhiQiang, Please log a bug and we can try to do what jd suggested. -- dims On Wed, May 6, 2015 at 9:21 AM, Julien Danjou wrote: > On Wed, May 06 2015, ZhiQiang Fan wrote: > >> I come across a problem that crudini cannot handle MultiStrOpt[1], I don't >> know why such type configuration option i

[openstack-dev] [fuel] Some changes in build script

Dear colleagues, Please, be informed that I've made some changes in our build script in order to support priorities for rpm repositories. I've also removed some unnecessary variables (EXTRA_RPM_REPOS and EXTRA_DEB_REPOS) and renamed some others. We don't need EXTRA_DEB_REPOS any more because it i

Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings

Tony, many thanks for noticing it, I didn't see it for some reason while looking at the iCal file / checking the wiki. We will use another time then. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Wed, May 6, 2015 at 5:15 AM, Tony Breeds

Re: [openstack-dev] [all] TC Communications planning

On 05/06/15 16:13, Anne Gentle wrote: Hi all, In the interest of communicating sooner rather than later, I wanted to write a new thread to say that Flavio Percoco and I are going to work on a TC communications plan as co-chairs of a TC communications working group. I think we can find a hap

[openstack-dev] ?????? [heat][ceilometer] autoscaling

I don't understand what you mean. Firstly, ceilometer doesn't return meters or samples to heat. In fact, heat configures an alarm in ceilometer and the action of this alarm is to send a REST to heat. When heat gets this REST, it triggers autoscalling. Besides, you can use #ceilometer alarm-lis

[openstack-dev] [RefStackl] - http://refstack.org/ - does not resolve

What are we doing to have name resolved? Meanwhile what is IP address to reach it? Do we really expect people to submit results to that web site? Thanks, Arkady __ OpenStack Development Mailing List (not for usage questions) Un

Re: [openstack-dev] [neutron][api] Extensions out, Micro-versions in

Thanks Bob. Two answers/comments below. On 6 May 2015 at 14:59, Bob Melander (bmelande) wrote: > Hi Salvatore, > > Two questions/remarks below. > > From: Salvatore Orlando > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Da

Re: [openstack-dev] [oslo.config] MultiStrOpt VS. ListOpt

One key difference about this is that AFAIR ListOpt is delimited by commas? Whereas MultiStrOpt is specified multiple times. In the case of Keystone, we include LDAP values which often include commas. Also for longer values, it is easier to read MultiStrOpt instead of ListOpt Thanks, Steve

Re: [openstack-dev] [RefStackl] - http://refstack.org/ - does not resolve

On 2015-05-06 09:37:26 -0500 (-0500), arkady_kanev...@dell.com wrote: > What are we doing to have name resolved? > Meanwhile what is IP address to reach it? > Do we really expect people to submit results to that web site? It looks like I can add that domain and whatever records we want for it... I

Re: [openstack-dev] [all] TC Communications planning

On Wed, 6 May 2015, Anne Gentle wrote: Please answer these questions on the list if you're interested in shaping the communications plan: (In case it isn't clear, answering just with regard to what I've experienced over the last year since joining the scene.) Audience considerations: Is the

[openstack-dev] [Ceilometer][Gnocchi] How to try ceilometer with gnocchi ?

Hi guys, I want to try using ceilometer with gnocchi, but I didn't any docs about how to configure it. I have check the master branch of ceilometer and didn't see how ceilometer interact with gnocchi neither (I think there should be something like a gnocchi-dispatcher?) Any hints?

Re: [openstack-dev] [Neutron][IPAM] Do we need migrate script for neutron IPAM now?

Ok, sounds good to me. I'll switch #153236 to built-in IPAM implementation by default, and pay additional attention on testing pluggable IPAM routines in this case. - Pavel On 06.05.2015 16:50, John Belamaric wrote: > I agree, we should amend it to not run pluggable IPAM as the default for > now

Re: [openstack-dev] [Ceilometer][Gnocchi] How to try ceilometer with gnocchi ?

On Wed, May 06 2015, Luo Gangyi wrote: Hi Luo, > I want to try using ceilometer with gnocchi, but I didn't any docs > about how to configure it. Everything should be documented at: http://docs.openstack.org/developer/gnocchi/ The devstack installation should be pretty straighforward:

Re: [openstack-dev] [oslo.config] MultiStrOpt VS. ListOpt

On Wed, May 06 2015, Steve Martinelli wrote: > One key difference about this is that AFAIR ListOpt is delimited by > commas? Whereas MultiStrOpt is specified multiple times. In the case of > Keystone, we include LDAP values which often include commas. Also for > longer values, it is easier

Re: [openstack-dev] [Fuel] Transaction scheme

> We don't need transactions, for example, in GET methods. It doesn't matter whether want we or not. The SQLAlchemy implicitly starts transaction on first "select" query and it's ok. I mean, perhaps it's not ok, but definitely it won't lead to great performance degradation. A large number of proje

[openstack-dev] [Murano] [Mistral] SSH workflow action

Hello We are considering implementing actions on services of a murano environment via mistral workflows. We are considering whether mistral std.ssh action could be used to run some command on an instance. Example of such action in murano could be restart action on Mysql DB service. Mistral w

Re: [openstack-dev] [all] cross project communication: periodic developer newsletter?

James Bottomley wrote: >> Anyone having a personal connection that we could leverage to pursue >> that option further ? > > Sure, be glad to. > > I've added Jon to the cc list (if his openstack mail sorting scripts > operate like mine, that will get his attention). > > I already had a preliminar

Re: [openstack-dev] [Neutron] Success of the IPv6 Subteam - Proposal to disband

On Mon, May 4, 2015 at 7:51 PM, Kyle Mestery wrote: > Sean and team, thanks for all your awesome work on IPv6 in Neutron over the > past two cycles! And thanks for volunteering to disband and go out on top, > integrating back into the broader team. It's a good move and would make > sense to cover

Re: [openstack-dev] [Murano] [Mistral] SSH workflow action

Hello, I think that the generic question is - can be O~S services also accessible on Neutron networks, so VM (created by Nova) can access it? We (I and Filip) were discussing this today and we were not make a final decision. Another example is Murano agent running on VMs - it connects to Rabbit

Re: [openstack-dev] [Murano] [Mistral] SSH workflow action

If your Mistral engine is on the same host as the network node hosting the router for the tenant, then it would probably work there are a lot of conditions in that statement though... Too many for my tastes. :/ While I dislike agents running in the vm's, this still might be a good use case

[openstack-dev] [neutron][lbaas][octavia] No Octavia meeting today

All, In order to work on the demo for Vancouver we will be skipping todays, 5/6/15 meeting. We will have another meeting on 5/13 to finalize for the summit -- If you have questions you can find us in the channel — and again please keep up the good work with reviews! Thanks, German __

Re: [openstack-dev] [Murano] [Mistral] SSH workflow action

Hi, >From Murano experience I can tell you that ssh to VM in general case will not work. In order to have an ssh access you will have to assign floating IPs so that Mistral service will be able to connect to VM. That is exactly the reason why Murano uses agent and MQ mechanism when client on VM in

[openstack-dev] [Gnocchi] Gnocchi 1.0.0 released

Hi fellows, I'm please to announce that Gnocchi 1.0.0 has been released today. https://bugs.launchpad.net/gnocchi/1.0/1.0.0 https://pypi.python.org/pypi/gnocchi The full documentation is online at: http://docs.openstack.org/developer/gnocchi Happy hacking! Cheers, -- Julien Danjo

Re: [openstack-dev] [Murano] [Mistral] SSH workflow action

On Wed, May 6, 2015 at 9:26 AM, Fox, Kevin M wrote: > If your Mistral engine is on the same host as the network node hosting the > router for the tenant, then it would probably work there are a lot of > conditions in that statement though... Too many for my tastes. :/ > > While I dislike agen

Re: [openstack-dev] [Murano] [Mistral] SSH workflow action

Hello one more note on that. There is difference in direction who initiates connection. In case of murano agent --> rabbit MQ is connection initiated from VM to openstack service(rabbit). In case of std.ssh mistral action is direction opposite from openstack service (mistral) to ssh server on

Re: [openstack-dev] [Neutron][IPAM] Do we need migrate script for neutron IPAM now?

On Tue, May 5, 2015 at 11:47 AM, Salvatore Orlando wrote: > I suggest to not enable it by default, and then consider in L-3 whether we > should do this switch. I agree. At the least, the switch should be decoupled from that patch. I think decoupling them before merging the patch was the plan al

Re: [openstack-dev] [Murano] [Mistral] SSH workflow action

Connection direction here is important only in the frame of networking connectivity problem solving. The networking in OpenStack in general works in such a way so that connections from VM are allowed to almost anywhere. In Murano production deployment we use separate MQ instance so that VMs have no

Re: [openstack-dev] [Neutron] Success of the IPv6 Subteam - Proposal to disband

On 05/04/2015 09:51 PM, Kyle Mestery wrote: > On Mon, May 4, 2015 at 7:37 PM, Sean M. Collins wrote: > >> It is a bittersweet moment - I am proposing that due to the amazing >> success that we have had as a subteam, that because we have >> accomplished so much, that it makes sense for our team to

Re: [openstack-dev] [Fuel] Nominate Julia Aranovich for fuel-web core

So, there is no objections and Julia is now a core reviewer for fuel-web. Congratulations! 2015-05-05 16:17 GMT+03:00 Vitaly Kramskikh : > Thanks for voting. If nobody has objections by tomorrow, Julia will get +2 > rights for fuel-web. > > 2015-05-05 15:30 GMT+03:00 Dmitry Pyzhov : > >> +1 >> >>

Re: [openstack-dev] [RefStackl] - http://refstack.org/ - does not resolve

- Original Message - > From: "Jeremy Stanley" > To: "OpenStack Development Mailing List (not for usage questions)" > > > On 2015-05-06 09:37:26 -0500 (-0500), arkady_kanev...@dell.com wrote: > > What are we doing to have name resolved? > > Meanwhile what is IP address to reach it? > > D

Re: [openstack-dev] [neutron] IPv4 transition/interoperation with IPv6

On Wed, May 6, 2015 at 12:46 AM, Mike Spreitzer wrote: > While I am a Neutron operator, I am also a customer of a lower layer network > provider. That network provider will happily give me a few /64. How do I > serve IPv6 subnets to lots of my tenants? In the bad old v4 days this would > be eas

Re: [openstack-dev] [Neutron] Success of the IPv6 Subteam - Proposal to disband

On 05/04/2015 08:37 PM, Sean M. Collins wrote: It is a bittersweet moment - I am proposing that due to the amazing success that we have had as a subteam, that because we have accomplished so much, that it makes sense for our team to disband and re-integrate with other subteams (the L3 subteam com

[openstack-dev] [chef] Feedback to move IRC Monday meeting and time.

Hey everyone! As we move forward with our big tent move[1] Jan suggested we move from our traditional IRC meeting in our main channel #openstack-chef to one of the official OpenStack meeting channels[2]. This has actually caused a situation that I’d like to make public. In the documentation th

Re: [openstack-dev] [neutron] Are routed TAP interfaces (and DHCP for them) in scope for Neutron?

This brings up something I'd like to discuss. We have a config option called "allow_overlapping_ips" which actually defaults to False. It has been suggested [1] that this should be removed from Neutron and I've just started playing around with ripping it out [2] to see what the consequences are.

Re: [openstack-dev] [chef] Feedback to move IRC Monday meeting and time.

Hi, for me (i live in Germany) the full hour (so 15:00 UTC) is fine. Cheers, Jan > On May 6, 2015, at 7:11 PM, JJ Asghar wrote: > > Hey everyone! > > As we move forward with our big tent move[1] Jan suggested we move from our > traditional IRC meeting in our main channel #openstack-chef to

Re: [openstack-dev] [oslo] Adding Joshua Harlow to oslo-core

Not a core but definitely a +1 from my side. Has great technical insights and is someone who is always happy to help others. -Vilobh On Tue, May 5, 2015 at 12:55 PM, David Medberry wrote: > Not a voting member, but +1 from me. He's core in my book. > > On Tue, May 5, 2015 at 11:27 AM, Ben Nemec

Re: [openstack-dev] [Ceilometer][Gnocchi] How to try ceilometer with gnocchi ?

Julien, Has anyone started on the RPMs and/or Puppet modules ? We'd be interested in trying this out. Thanks Tim > -Original Message- > From: Julien Danjou [mailto:jul...@danjou.info] > Sent: 06 May 2015 17:24 > To: Luo Gangyi > Cc: OpenStack Development Mailing L > Subject: Re: [openst

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

Not a core but definitely a +1. She is very helpful. On Fri, May 1, 2015 at 9:43 PM, Gary Kotton wrote: > +1 > > From: Alex Xu > Reply-To: OpenStack List > Date: Friday, May 1, 2015 at 6:30 AM > To: OpenStack List > Subject: Re: [openstack-dev] [nova] Proposal to add Melanie Witt to > nova

Re: [openstack-dev] [Fuel] LBaaS in version 5.1

Thanks Stanislaw for reply. sure i can do that the only unknown question i have is related to the Fuel HA controllers. I assume i can easily ignore the controller HA (LBaaS doesn't support HA :) ) and just go the standard LBaaS? On Wed, May 6, 2015 at 2:55 PM, Stanislaw Bogatkin wrote: > Hi D

Re: [openstack-dev] [Ceilometer][Gnocchi] How to try ceilometer with gnocchi ?

Sorry to add another question, can Gnocchi be installed on a Juno cloud or do we need to be running Kilo ? Tim > -Original Message- > From: Tim Bell [mailto:tim.b...@cern.ch] > Sent: 06 May 2015 19:36 > To: OpenStack Development Mailing List (not for usage questions); Luo Gangyi > Subjec

Re: [openstack-dev] [Nova][Ironic] Large number of ironic driver bugs in nova

JohnG, I work on Ironic and would be willing to be a cross project liaison for Nova and Ironic. I would just need a little info on what to do from the Nova side. Meetings to attend, web pages to monitor, etc... I assume I would start with this page: https://bugs.launchpad.net/nova/+bugs?field.t

[openstack-dev] [api] Changing 403 Forbidden to 400 Bad Request for OverQuota was: [nova] Which error code should we return when OverQuota

Adding [api] topic. API WG members, please do comment. On 05/06/2015 08:01 AM, Sean Dague wrote: On 05/06/2015 07:11 AM, Chris Dent wrote: On Wed, 6 May 2015, Sean Dague wrote: All other client errors, just be a 400. And use the emerging error reporting json to actually tell the client what's

Re: [openstack-dev] [api] Changing 403 Forbidden to 400 Bad Request for OverQuota was: [nova] Which error code should we return when OverQuota

On 05/06/2015 02:07 PM, Jay Pipes wrote: > Adding [api] topic. API WG members, please do comment. > > On 05/06/2015 08:01 AM, Sean Dague wrote: >> On 05/06/2015 07:11 AM, Chris Dent wrote: >>> On Wed, 6 May 2015, Sean Dague wrote: >>> All other client errors, just be a 400. And use the emergi

Re: [openstack-dev] Gerrit downtime and upgrade on Saturday 2015-05-09 at 1600 UTC

On Tue, Apr 14, 2015 at 2:57 PM, James E. Blair wrote: > On Saturday, May 9 at 16:00 UTC Gerrit will be unavailable for about 4 > hours while we upgrade to the latest release of Gerrit: version 2.10. > > We are currently running Gerrit 2.8 so this is an upgrade across two > major releases of Gerri

Re: [openstack-dev] [api] Changing 403 Forbidden to 400 Bad Request for OverQuota was: [nova] Which error code should we return when OverQuota

On 05/06/2015 02:07 PM, Jay Pipes wrote: Adding [api] topic. API WG members, please do comment. On 05/06/2015 08:01 AM, Sean Dague wrote: On 05/06/2015 07:11 AM, Chris Dent wrote: On Wed, 6 May 2015, Sean Dague wrote: All other client errors, just be a 400. And use the emerging error reporti

[openstack-dev] [Cinder] Static Ceph mon connection info prevents VM restart

Hi, As we swapped a fraction of our Ceph mon servers between the pre-production and production cluster — something we considered to be transparent as the Ceph config points to the mon alias—, we ended up in a situation where VMs with volumes attached were not able to boot (with a probability th

Re: [openstack-dev] [api] Changing 403 Forbidden to 400 Bad Request for OverQuota was: [nova] Which error code should we return when OverQuota

On Wed, 6 May 2015, Jay Pipes wrote: I think Sean makes an excellent point that if you have >1 condition that results in a 403 Forbidden, it actually does not make things more expressive. It actually just means both humans and clients need to now delve deeper into the error context to determin

[openstack-dev] [QA] Meeting Thursday May 7th at 17:00 UTC

Hi everyone, Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, May 7th at 17:00 UTC in the #openstack-meeting channel. The agenda for tomorrow's meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to add

Re: [openstack-dev] [api] Changing 403 Forbidden to 400 Bad Request for OverQuota was: [nova] Which error code should we return when OverQuota

On 05/06/2015 03:15 PM, Chris Dent wrote: > On Wed, 6 May 2015, Jay Pipes wrote: > >> I think Sean makes an excellent point that if you have >1 condition >> that results in a 403 Forbidden, it actually does not make things more >> expressive. It actually just means both humans and clients need to

Re: [openstack-dev] [Cinder] Static Ceph mon connection info prevents VM restart

Hi Arne, We've had this EXACT same issue. I don't know of a way to force an update as you are basically pulling the rug out from under a running instance. I don't know if it is possible/feasible to update the virsh xml in place and then migrate to get it to actually use that data. (I think we tri

Re: [openstack-dev] [RefStackl] - http://refstack.org/ - does not resolve

The Refstack team is working with Infra to get refstack.org up in a vm under Infra's purview. Right now, the demo is on refstack.net refstack.net will go away once refstack.org is up and managed. --rocky -Original Message- From: Jeremy Stanley [mailto:fu...@yuggoth.org] Sent: Wednesd

Re: [openstack-dev] [Ceilometer][Gnocchi] How to try ceilometer with gnocchi ?

On 05/06/2015 01:36 PM, Tim Bell wrote: > Julien, > > Has anyone started on the RPMs and/or Puppet modules ? We'd be interested in > trying this out. We wrote https://github.com/stackforge/puppet-gnocchi But we have to wait for packaging. I know it's WIP in RDO, no clue for Debian/Ubuntu. >

Re: [openstack-dev] [keystone] On dynamic policy, role hierarchies/groups/sets etc.

Hi all, Inline. From: Adam Young mailto:ayo...@redhat.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, May 5, 2015 at 8:34 PM To: "openstack-dev@lists.openstack.org"

Re: [openstack-dev] [RefStackl] - http://refstack.org/ - does not resolve

On 2015-05-06 19:53:44 + (+), Rochelle Grober wrote: > The Refstack team is working with Infra to get refstack.org up in > a vm under Infra's purview. Right now, the demo is on refstack.net > refstack.net will go away once refstack.org is up and managed. Yep, I recall the discussion. I sim

Re: [openstack-dev] [all] TC Communications planning

Excerpts from Maish Saidel-Keesing's message of 2015-05-06 17:11:23 +0300: > On 05/06/15 16:13, Anne Gentle wrote: > > Hi all, > > > > In the interest of communicating sooner rather than later, I wanted to > > write a new thread to say that Flavio Percoco and I are going to work > > on a TC commu

[openstack-dev] [neutron] Neutron meeting for the next few weeks is cancelled

Hi folks! Given most of us will be in Vancouver for the Summit and we've finished planning out the design summit, we'll go ahead and cancel the Neutron meeting for the next 3 weeks. We'll resume the week after the Summit, which is 6/2/2015 at 1400UTC [1]. Thanks! Kyle [1] https://wiki.openstack.

Re: [openstack-dev] [api] Changing 403 Forbidden to 400 Bad Request for OverQuota was: [nova] Which error code should we return when OverQuota

On May 6, 2015, at 1:58 PM, David Kranz mailto:dkr...@redhat.com>> wrote: +1 The basic problem is we are trying to fit a square (generic api) peg in a round (HTTP request/response) hole. But if we do say we are recognizing "sub-error-codes", it might be good to actually give them numbers somewh

Re: [openstack-dev] [all] TC Communications planning

On 06/05/15 09:13, Anne Gentle wrote: Hi all, In the interest of communicating sooner rather than later, I wanted to write a new thread to say that Flavio Percoco and I are going to work on a TC communications plan as co-chairs of a TC communications working group. I think we can find a happy m

Re: [openstack-dev] [keystone] On dynamic policy, role hierarchies/groups/sets etc.

Nice summary Henry. My comments in brown. From: Adam Young [mailto:ayo...@redhat.com] Sent: Tuesday, May 5, 2015 8:35 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [keystone] On dynamic policy, role hierarchies/groups/sets etc. On 05/05/2015 07:05 AM, Henry Nash wrote:

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

We also run all masterless/puppet apply. And we just populate a bare bones keystone.conf on any box that does not have keystone installed, but Puppet needs to be able to create keystone resources. Also agreed on avoiding puppetdb, for the same reasons. (Something to note for those of us doing

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

On Wed, May 6, 2015 at 4:26 PM, Mike Dorman wrote: > We also run all masterless/puppet apply. And we just populate a bare > bones keystone.conf on any box that does not have keystone installed, but > Puppet needs to be able to create keystone resources. > > Also agreed on avoiding puppetdb, for

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

Cool, fair enough. Pretty glad to hear that actually! From: Colleen Murphy Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, May 6, 2015 at 5:31 PM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [puppet][ope

Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings

On Wed, May 06, 2015 at 05:09:07PM +0300, Mikhail Dubov wrote: > many thanks for noticing it, I didn't see it for some reason while looking > at the iCal file / checking the wiki. No problem. Seeing conflicts is non-trivial. with 90+meetings in 4+ IRC channels. > We will use another time then

Re: [openstack-dev] [chef] Feedback to move IRC Monday meeting and time.

On Wed, May 06, 2015 at 12:11:16PM -0500, JJ Asghar wrote: > Hey everyone! > > As we move forward with our big tent move[1] Jan suggested we move from our > traditional IRC meeting in our main channel #openstack-chef to one of the > official OpenStack meeting channels[2]. Sounds like a good idea

[openstack-dev] [Swift] HEAD Object API status code

Hello Swift developers, I would like to ask you on a Swift API specification. Swift returns 204 status code to a valid HEAD Object request with a Content-Length header, whereas the latest HTTP/1.1 specification (RFC7230) states that you must not send the header with a 204 status code. > 3.3.2.

Re: [openstack-dev] [all] cross project communication: periodic developer newsletter?

On 6/05/2015 23:34, James Bottomley wrote: On Wed, 2015-05-06 at 11:54 +0200, Thierry Carrez wrote: Hugh Blemings wrote: +2 I think asking LWN if they have the bandwidth and interest to do this would be ideal - they've credibility in the Free/Open Source space and a proven track record. Nice

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

It seems ~/.openrc is the only default, so just replacing the RC file default: Workflow to find credentials details: 1. From environment (ENV[] or ENV[] in short) 2. From a RC file located by convention in current user homedir: ~/.openrc 3. From an openstack configuration file such as keystone.

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

On Wed, May 6, 2015 at 6:26 PM, Gilles Dubreuil wrote: > It seems ~/.openrc is the only default [...] > The extras module places it at '/root/openrc' [1], so either the extras module should be changed or the providers should look in /root/openrc, either way it should be consistent. Colleen [1]

Re: [openstack-dev] [heat]: stack stays interminably under the status create in progress

BTW, you may want to post your questions on using Heat to openst...@lists.openstack.org and/or https://ask.openstack.org, instead of this mailinglist. - QM On Tue, May 05, 2015 at 03:02:59PM +0200, ICHIBA Sara wrote: > Hello there, > > I started a project where I need to deploy stacks and orcha

  1   2   >