Re: [openstack-dev] [blazar] currectly status

Le 11/02/2015 04:24, Jin, Yuntong a écrit : Hello, May I ask the currently status of blazar project, it’s been very quiet there for past half year, part of reason could be related to Gantt project? The way I see this project is very usefully for NFV use case, and I really like to know the sta

[openstack-dev] [CINDER] discussion about Volume Delete API

In http://developer.openstack.org/api-ref-blockstorage-v2.html, delete volume preconditions: Preconditions · Volume status must be available, in-use, error, or error_restoring. I think we may change to following statements: Preconditions · Volume status must be creating,

Re: [openstack-dev] [blazar] currectly status

Hi, I'm agree with Sylvain. Also, if you want to contribute to Blazar ping me in IRC, I can tell you where you can start with it. Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2015-02-11 11:18 GMT+03:00 Sylvain Bauza : > > Le 11/02/2015 04:24, Jin, Yuntong a

[openstack-dev] [nova] Flavor extra-spec and image metadata documentation

Hello I am working on a little patch that introduce a new flavor extra-spec and image metadata key-value pair https://review.openstack.org/#/c/153607/ I am wondering how an openstack admin can be aware that a specific value of a flavor extra-spec or image metadata provides a feature he may desire

Re: [openstack-dev] [CINDER] discussion about Volume Delete API

Depending on what progress the backend has made during the create, this can race witht the create such that you can end up: a) No volume on the backend but a volume in cinder (this is ok) b) With no volume on the backend but the volume manager putting the volume in state available (delete flag woul

Re: [openstack-dev] [NOVA] security group fails to attach to an instance if port-id is specified during boot.

You could rise an exception if ports are specified for all nics. [1] I'm not sure that logging of this case is helpful, because only admins can access to logs. Probably the better way to warn a user is to do it at client side by nova cli (i.e. no any modification of nova server is needed). [1] It

Re: [openstack-dev] [OpenStack-Infra] Cross-Repo Dependencies in Zuul

James E. Blair wrote: > We have added support for cross-repo dependencies (CRD) in Zuul. The > important bits: > > * To use them, include "Depends-On: " in the footer of > your commit message. Use the full Change-ID ('I' + 40 characters). Thanks for that! I know that should make some StoryBoa

[openstack-dev] [all][tc] Lets keep our community open, lets fight for it

Greetings all, During the last two cycles, I've had the feeling that some of the things I love the most about this community are degrading and moving to a state that I personally disagree with. With the hope of seeing these things improve, I'm taking the time today to share one of my concerns. S

Re: [openstack-dev] Cross-Repo Dependencies in Zuul

OH MY GOD! I'll throw a party! Thanks to everyone involved in making this happen. Flavio On 10/02/15 14:26 -0800, James E. Blair wrote: Hi, We have added support for cross-repo dependencies (CRD) in Zuul. The important bits: * To use them, include "Depends-On: " in the footer of your commi

Re: [openstack-dev] [nova] Flavor extra-spec and image metadata documentation

On Wed, Feb 11, 2015 at 10:23:54AM +0100, Pasquale Porreca wrote: > Hello > > I am working on a little patch that introduce a new flavor extra-spec > and image metadata key-value pair https://review.openstack.org/#/c/153607/ > > I am wondering how an openstack admin can be aware that a specific v

Re: [openstack-dev] [nova] Flavor extra-spec and image metadata documentation

On Wed, Feb 11, 2015 at 10:23:54AM +0100, Pasquale Porreca wrote: > Hello > > I am working on a little patch that introduce a new flavor extra-spec > and image metadata key-value pair https://review.openstack.org/#/c/153607/ > > I am wondering how an openstack admin can be aware that a specific v

Re: [openstack-dev] [cinder] Question about the plan of L

Our driver have been merged into Kilo before K-1 and have implemented many features, so I think our driver is not a new driver. For these drivers aleady merged in Kilo and if they want add some new features, does they should be merged before L-1 too? Thanks, Liu Yes, assume NEW drivers ha

Re: [openstack-dev] [nova] Flavor extra-spec and image metadata documentation

Pasquale Porreca, The flexibility/ freedom to create meta data tags for images and Nova flavor extra specs can be confusing. Even allows one to make typographical errors that may be hard to detect. As Daniel mentions, some tags have a definite meaning/semantics, others can be totally random. Tag

Re: [openstack-dev] [Keystone] Proposing Marek Denis for the Keystone Core Team

+1 Well done! On Tue, Feb 10, 2015 at 09:51:14AM -0800, Morgan Fainberg wrote: > Hi everyone! > > I wanted to propose Marek Denis (marekd on IRC) as a new member of the > Keystone Core team. Marek has been instrumental in the implementation of > Federated Identity. His work on Keystone and fir

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

Flavio Percoco wrote: > During the last two cycles, I've had the feeling that some of the > things I love the most about this community are degrading and moving > to a state that I personally disagree with. With the hope of seeing > these things improve, I'm taking the time today to share one of my

Re: [openstack-dev] [Keystone] Proposing Marek Denis for the Keystone Core Team

+1 > On 10 Feb 2015, at 18:04, Dolph Mathews > wrote: > > +1 > > On Tue, Feb 10, 2015 at 11:51 AM, Morgan Fainberg > wrote: > Hi everyone! > > I wanted to propose Marek Denis (marekd on IRC) as a new member of the > Keystone C

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Wed, Feb 11, 2015 at 10:55:18AM +0100, Flavio Percoco wrote: > Greetings all, > > During the last two cycles, I've had the feeling that some of the > things I love the most about this community are degrading and moving > to a state that I personally disagree with. With the hope of seeing > thes

Re: [openstack-dev] [nova] Flavor extra-spec and image metadata documentation

Thank you for all answers. I know that meta data tags are "free" to use with any key/value, still there are some specific values that triggers pieces of code in nova (or maybe even in other components). In particular I am working on one of these key/value, in my case it should enable the paramet

Re: [openstack-dev] [nova] Flavor extra-spec and image metadata documentation

On Wed, Feb 11, 2015 at 12:03:58PM +0100, Pasquale Porreca wrote: > Thank you for all answers. > I know that meta data tags are "free" to use with any key/value, still > there are some specific values that triggers pieces of code in nova (or > maybe even in other components). In particular I am wor

[openstack-dev] [QA] Question about EC2 Tempest tests

Hello everyone, I have some question about EC2 Tempest tests. When I run these tests, I regularly have the same error for all tests: EC2ResponseError: EC2ResponseError: 400 Bad Request AuthFailureSignature not provided My environment is OpenStack (the Juno release) deployed by Fuel 6.0. Tempest

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Wed, 11 Feb 2015, Flavio Percoco wrote: During the last two cycles, I've had the feeling that some of the things I love the most about this community are degrading and moving to a state that I personally disagree with. With the hope of seeing these things improve, I'm taking the time today to

Re: [openstack-dev] [nova] Flavor extra-spec and image metadata documentation

Thank you very much for the clarification :) On 02/11/15 12:15, Daniel P. Berrange wrote: > On Wed, Feb 11, 2015 at 12:03:58PM +0100, Pasquale Porreca wrote: >> Thank you for all answers. >> I know that meta data tags are "free" to use with any key/value, still >> there are some specific values th

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

> -Original Message- > From: Flavio Percoco [mailto:fla...@redhat.com] > Sent: Wednesday, February 11, 2015 9:55 AM > To: openstack-dev@lists.openstack.org > Subject: [openstack-dev] [all][tc] Lets keep our community open, lets fight > for it > > Greetings all, > > During the last two cyc

Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody should know about Galera

- Original Message - > From: "Jay Pipes" > To: "Attila Fazekas" > Cc: "OpenStack Development Mailing List (not for usage questions)" > , "Pavel > Kholkin" > Sent: Tuesday, February 10, 2015 7:32:11 PM > Subject: Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody > sho

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

+ Inf for writing this Flavio! Only some observations below. On 02/11/2015 10:55 AM, Flavio Percoco wrote: > Greetings all, > > During the last two cycles, I've had the feeling that some of the > things I love the most about this community are degrading and moving > to a state that I personally

Re: [openstack-dev] [QA] Question about EC2 Tempest tests

Yaroslav, The bug: https://bugs.launchpad.net/nova/+bug/1410622 And the review: https://review.openstack.org/#/c/152112/ It's recently fixed. Best regards, Alex Levine On 2/11/15 2:23 PM, Yaroslav Lobankov wrote: Hello everyone, I have some question about EC2 Tempest tests. When I run the

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Wed, Feb 11, 2015 at 12:53:24PM +0100, Nikola Đipanov wrote: > + Inf for writing this Flavio! Absolutely! I never even knew such things existed in this community. > Only some observations below. [. . .] > > ## Mailing List vs IRC Channel > > > > I get it, our mailing list is freaking busy,

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 11/02/15 11:31 +, Kuvaja, Erno wrote: ## Mailing List vs IRC Channel I get it, our mailing list is freaking busy, keeping up with it is hard and time consuming and that leads to lots of IRC discussions. I don't think there's anything wrong with that but I believe it's wrong to expect *EVE

[openstack-dev] [nova] Feature Freeze Exception for "Add config drive support for PCS containers"

Hello, I'd like to request a feature freeze exception for the change [1] This change implements configuration drive support in Parallels containers. It does not change existing Nova behaviour. It's a last patch in parallels series, that implements blueprint pcs-support [2]. Previous patches of t

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Wed, 11 Feb 2015, Chris Dent wrote: I think it is time we recognize and act on the fact that the corporate landlords that pay many of us to farm on this land need to provide more resources. In case it wasn't clear, by this I don't mean project managers and other styles of enterprisey hoopaa

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 02/11/2015 04:55 AM, Flavio Percoco wrote: > Greetings all, > > During the last two cycles, I've had the feeling that some of the > things I love the most about this community are degrading and moving > to a state that I personally disagree with. With the hope of seeing > these things improve,

Re: [openstack-dev] [QA] Question about EC2 Tempest tests

Thanks, Alexandre! Regards, Yaroslav Lobankov. On Wed, Feb 11, 2015 at 2:58 PM, Alexandre Levine wrote: > Yaroslav, > > The bug: > https://bugs.launchpad.net/nova/+bug/1410622 > > And the review: > https://review.openstack.org/#/c/152112/ > > It's recently fixed. > > Best regards, > Alex Lev

Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody should know about Galera

On 10/02/15 18:29, Jay Pipes wrote: > On 02/10/2015 09:47 AM, Matthew Booth wrote: >> On 09/02/15 18:15, Jay Pipes wrote: >>> On 02/09/2015 01:02 PM, Attila Fazekas wrote: I do not see why not to use `FOR UPDATE` even with multi-writer or Is the retry/swap way really solves anything here.

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 02/11/2015 05:52 AM, Daniel P. Berrange wrote: > On Wed, Feb 11, 2015 at 10:55:18AM +0100, Flavio Percoco wrote: >> Greetings all, >> >> During the last two cycles, I've had the feeling that some of the >> things I love the most about this community are degrading and moving >> to a state that I

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 02/11/2015 02:13 PM, Sean Dague wrote: > > If core team members start dropping off external IRC where they are > communicating across corporate boundaries, then the local tribal effects > start taking over. You get people start talking about the upstream as > "them". The moment we get into us v

Re: [openstack-dev] [Manila]Question about gateway-mediated-with-ganesha

On Tue, Feb 10, 2015 at 1:51 AM, Li, Chen wrote: > Hi list, > > > > I’m trying to understand how manila use NFS-Ganesha, and hope to figure > out what I need to do to use it if all patches been merged (only one patch > is under reviewing, right ?). > > > > I have read: > > https://wiki.openstac

[openstack-dev] [Openstack] [Heat][convergence] Formal model for SyncPoints

Oops, sent this to openstack@ not openstack-dev@. On 02/10/2015 04:52 PM, Ryan Brown wrote: > Heat team, > > After looking at Zane's prototype[1] and the ML threads on SyncPoint, I > thought it'd be helpful to make a model of *just* the logic around > resource locking. Hopefully, it'll help durin

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 2/11/15, 3:26 PM, "Nikola Đipanov" wrote: >On 02/11/2015 02:13 PM, Sean Dague wrote: >> >> If core team members start dropping off external IRC where they are >> communicating across corporate boundaries, then the local tribal effects >> start taking over. You get people start talking about

Re: [openstack-dev] Testing NUMA, CPU pinning and large pages

> -Original Message- > From: Vladik Romanovsky [mailto:vladik.romanov...@enovance.com] > Sent: Wednesday, January 28, 2015 4:10 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [nova][NFV][qa] Testing NUMA, CPU pinning > and large pages >

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Wed, Feb 11, 2015 at 08:13:05AM -0500, Sean Dague wrote: > On 02/11/2015 05:52 AM, Daniel P. Berrange wrote: > >> ## Mailing List vs IRC Channel > >> > >> I get it, our mailing list is freaking busy, keeping up with it is > >> hard and time consuming and that leads to lots of IRC discussions. I

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Wed, 2015-02-11 at 10:55 +0100, Flavio Percoco wrote: > This email is dedicated to the openness of our community/project. It's good to have a reminder every now and then. Thank you Flavio for caring enough to notice bad patterns and for raising a flag. > ## Keep discussions open > > I don't

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 02/11/2015 09:02 AM, Daniel P. Berrange wrote: > On Wed, Feb 11, 2015 at 08:13:05AM -0500, Sean Dague wrote: >> On 02/11/2015 05:52 AM, Daniel P. Berrange wrote: ## Mailing List vs IRC Channel I get it, our mailing list is freaking busy, keeping up with it is hard and time co

Re: [openstack-dev] [cinder] Question about the plan of L

Currently for updates to existing drivers, there isn't currently a fixed date for updates, however you should aim to have any changes up as early as possible. Keep an eye on the mailing list for more announcements as plans become more firm. On 11 February 2015 at 12:21, liuxinguo wrote: > Our d

Re: [openstack-dev] Cross-Repo Dependencies in Zuul

Firstly, this is a great feature - thanks for getting it implemented! > -Original Message- > From: James E. Blair [mailto:cor...@inaugust.com] > Sent: 10 February 2015 22:26 > To: OpenStack Development Mailing List > Cc: openstack-in...@lists.openstack.org > Subject: [openstack-dev] Cross-

Re: [openstack-dev] [api] Optional Properties in an Entity

On 2/9/15, 8:44 PM, "Joe Gordon" mailto:joe.gord...@gmail.com>> wrote: On Mon, Feb 9, 2015 at 1:22 PM, Jay Pipes mailto:jaypi...@gmail.com>> wrote: On 01/20/2015 10:54 AM, Brian Rosmaita wrote: From: Kevin L. Mitchell [kevin.mitch...@rackspace.com] Sent: Mon

[openstack-dev] [vmware][nova] Prevent HA configuration with different hostnames

I just posted this: https://review.openstack.org/#/c/154907/ as an alternative fix for critical bug: https://bugs.launchpad.net/nova/+bug/1419785 I've just knocked this up quickly for illustration: it obviously needs plenty of cleanup. I have confirmed that it works, though. Before I take it a

Re: [openstack-dev] [vmware][nova] Prevent HA configuration with different hostnames

Hi, I do not think that that is a healthy solution. That effectively would render a cluster down if the compute node goes down. That would be a real disaster. The ugly work around is setting the host names to be the same value. This is something that we should discuss at the next summit and I would

[openstack-dev] [keystone] [nova]

Hi ! I investigated trust's use cases and encountered the problem: When I use auth_token obtained from keystoneclient using trust, I get *403* Forbidden error: *You are not authorized to perform the requested action.* Steps to reproduce: - Import v3 keystoneclient (used keystone and keystonecli

Re: [openstack-dev] [all][PTLs] Stop releasing libraries/clients without capping stable global requirements

On Tue, Feb 10, 2015, at 07:12 PM, Joe Gordon wrote: > Hi, > > As you know a few of us have been spending way too much time digging > stable/juno out of the ditch its currently in. And just when we thought > we > were in the clear a new library was released without a requirements cap > in > stab

Re: [openstack-dev] [vmware][nova] Prevent HA configuration with different hostnames

On 11/02/15 15:49, Gary Kotton wrote: > Hi, > I do not think that that is a healthy solution. That effectively would > render a cluster down if the compute node goes down. That would be a real > disaster. The ugly work around is setting the host names to be the same > value. I don't think that's a

Re: [openstack-dev] Cross-Repo Dependencies in Zuul

This is awesome news! If I understand correctly, your description of "multiple changes" describes cases where a single change depends on multiple changes. My question is related to one-to-one dependencies in the form A -> B -> C. I'm assuming that this is supported as well in the case where, fo

Re: [openstack-dev] [vmware][nova] Prevent HA configuration with different hostnames

I posted a fix that does not break things and supports HA. https://review.openstack.org/154029 On 2/11/15, 5:55 PM, "Matthew Booth" wrote: >On 11/02/15 15:49, Gary Kotton wrote: >> Hi, >> I do not think that that is a healthy solution. That effectively would >> render a cluster down if the compu

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Wed, Feb 11, 2015, at 09:14 AM, Stefano Maffulli wrote: > On Wed, 2015-02-11 at 10:55 +0100, Flavio Percoco wrote: > > This email is dedicated to the openness of our community/project. > > It's good to have a reminder every now and then. Thank you Flavio for > caring enough to notice bad patt

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Wed, 2015-02-11 at 09:32 -0500, Sean Dague wrote: > Definitely true, to each his/her own. I still consider it unfortunate. > I've also heard core developers state that they stopped reading the > mailing list months ago. Which I also find unfortunate. That's terrible: do you know why they don't

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 2015-02-11 11:31:13 + (+), Kuvaja, Erno wrote: [...] > If you don't belong to the group of privileged living in the area > and receiving free ticket somehow or company paying your > participation you're not included. $600 + travel + accommodation > is quite hefty premium to be included,

[openstack-dev] [devstack] Compute-node-only installation fails

Hi Daniel, with your recent change[1] to error handling in stack.sh, compute node only installations via devstack fail because there is no database selected. A database should not be required on compute nodes. Was this done intentionally? lib/database explicitly says: # If ``DATABASE_TYPE`` is u

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Wed, Feb 11, 2015, at 09:32 AM, Sean Dague wrote: > On 02/11/2015 09:02 AM, Daniel P. Berrange wrote: > > On Wed, Feb 11, 2015 at 08:13:05AM -0500, Sean Dague wrote: > >> On 02/11/2015 05:52 AM, Daniel P. Berrange wrote: > ## Mailing List vs IRC Channel > > I get it, our mailing

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Wed, Feb 11, 2015, at 11:15 AM, Jeremy Stanley wrote: > On 2015-02-11 11:31:13 + (+), Kuvaja, Erno wrote: > [...] > > If you don't belong to the group of privileged living in the area > > and receiving free ticket somehow or company paying your > > participation you're not included. $6

Re: [openstack-dev] Cross-Repo Dependencies in Zuul

Amrith Kumar writes: > This is awesome news! > > If I understand correctly, your description of "multiple changes" > describes cases where a single change depends on multiple changes. My > question is related to one-to-one dependencies in the form A -> B -> > C. > > I'm assuming that this is supp

Re: [openstack-dev] [devstack] Compute-node-only installation fails

On Wed, Feb 11, 2015 at 05:18:35PM +0100, Alexander Schmidt wrote: > Hi Daniel, > > with your recent change[1] to error handling in stack.sh, compute > node only installations via devstack fail because there is > no database selected. A database should not be required on > compute nodes. > > Was

Re: [openstack-dev] [devstack] Compute-node-only installation fails

On Wed, Feb 11, 2015, at 08:18 AM, Alexander Schmidt wrote: > Hi Daniel, > > with your recent change[1] to error handling in stack.sh, compute > node only installations via devstack fail because there is > no database selected. A database should not be required on > compute nodes. > > Was this do

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

> On Feb 11, 2015, at 11:15 AM, Jeremy Stanley wrote: > > On 2015-02-11 11:31:13 + (+), Kuvaja, Erno wrote: > [...] >> If you don't belong to the group of privileged living in the area >> and receiving free ticket somehow or company paying your >> participation you're not included. $600

Re: [openstack-dev] [vmware][nova] Prevent HA configuration with different hostnames

Le 11/02/2015 17:04, Gary Kotton a écrit : I posted a fix that does not break things and supports HA. https://review.openstack.org/154029 Just let's be clear, HA is *not* supported by Nova now. The main reason is that compute *nodes* are considered given by the hypervisor (ie. the virt driv

Re: [openstack-dev] Cross-Repo Dependencies in Zuul

Thanks, most awesome. Alas, if this was around three weeks ago, I'd still have a full head of hair. Now all I have is a lifetime of savings on hairdressing. -amrith | -Original Message- | From: James E. Blair [mailto:cor...@inaugust.com] | Sent: Wednesday, February 11, 2015 11:33 AM | To

Re: [openstack-dev] Cross-Repo Dependencies in Zuul

"Sullivan, Jon Paul" writes: >> A change may depend on more than one Gerrit change ID as well. So it is >> possible for a change in tempest to depend on a change in devstack and a >> change in nova. Simply add more "Depends-On:" lines to the footer. > > Have you considered a case where changes

Re: [openstack-dev] [vmware][nova] Prevent HA configuration with different hostnames

On 2/11/15, 6:35 PM, "Sylvain Bauza" wrote: > >Le 11/02/2015 17:04, Gary Kotton a écrit : >> I posted a fix that does not break things and supports HA. >> https://review.openstack.org/154029 > > >Just let's be clear, HA is *not* supported by Nova now. That is not correct. It is actually suppor

Re: [openstack-dev] [devstack] [third-party] how to use a devstack external plugin in gate testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, I'm working in the same job as Kyle for the midonet plugin, but first I need to do some changes in devstack. (Sean's review on my patch[1] has lead me to this conversation). After talking with Lucas, (Midokura's responsible of Third-party te

Re: [openstack-dev] [devstack] [third-party] how to use a devstack external plugin in gate testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, I'm working in the same job as Kyle for the midonet plugin, but first I need to do some changes in devstack. (Sean's review on my patch[1] has lead me to this conversation). After talking with Lucas, (Midokura's responsible of Third-party te

[openstack-dev] [cinder] CURD operation for storage pools in Cinder

Hello, Does Cinder already have a blue-print/planned-schedule for supporting (at least in API level - may not be python-client/Horizon levels) the create/edit/delete operation on the storage pools? It is understood that the "read" part 'get_pools' is already there. If it is already planned/sc

Re: [openstack-dev] [keystone] [nova]

On 02/11/2015 10:52 AM, Nikolay Makhotkin wrote: Hi ! I investigated trust's use cases and encountered the problem: When I use auth_token obtained from keystoneclient using trust, I get *403* Forbidden error: *You are not authorized to perform the requested action.* Steps to reproduce: - Im

[openstack-dev] [congress][Policy][Copper]Collaboration between OpenStack Congress and OPNFV Copper

Hi Congress Team, As you might already knew, we had a project in OPNFV covering deployment policy called Copper , in which we identify Congress as one of the upstream projects that we need to put our requirement to. Our team has been working on setting up a simple op

[openstack-dev] [Congress][Delegation] Google doc for working notes

Hi all, A (growing) group of folks are interested in working on the problem of delegating policy from Congress to domain-specific policy engines. We started looking at an NFV use case: migrating VMs to reduce energy consumption. In particular we’re looking into building a VM-placement policy

[openstack-dev] [TripleO] update on Puppet integration in Kilo

I wanted to take a few minutes to go over the progress we've made with TripleO Puppet in Kilo so far. For those unfamilar with the efforts our initial goal was to be able to use Puppet as the configuration tool for a TripleO deployment stack. This is largely built around a Heat capability added in

[openstack-dev] [oslo] liberty summit planning

As I mentioned at the meeting Monday, we need to start thinking about the number and types of rooms we will need for the summit. I’ve started an etherpad to collect topics, just like we did for the kilo summit [1]. Please add your ideas to the list there so we can review them. Thanks, Doug [1

Re: [openstack-dev] [vmware][nova] Prevent HA configuration with different hostnames

On 11/02/15 16:40, Gary Kotton wrote: > > > On 2/11/15, 6:35 PM, "Sylvain Bauza" wrote: > >> >> Le 11/02/2015 17:04, Gary Kotton a écrit : >>> I posted a fix that does not break things and supports HA. >>> https://review.openstack.org/154029 >> >> >> Just let's be clear, HA is *not* supported b

Re: [openstack-dev] [glance] Metadef-tags create api change request.

Hello, I would like to change the metadef-tags create API which was checked into Kilo (cycle 1). The python-glanceclient that would support metadef-tags has not been released yet and I would like to make this change before doing so. The details are here: https://review.openstack.org/#/c/154229/

Re: [openstack-dev] [keystone] [nova]

No, I just checked it. Nova receives trust token and raise this error. In my script, I see: http://paste.openstack.org/show/171452/ And as you can see, token from trust differs from direct user's token. On Wed, Feb 11, 2015 at 7:55 PM, Adam Young wrote: > On 02/11/2015 10:52 AM, Nikolay Makh

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

Stefano, You write: | This is seriously disturbing. | | If you're one of those core reviewers hanging out on a private channel, | please contact me privately: I'd love to hear from you why we failed as a | community at convincing you that an open channel is the place to be. | | No public shamin

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

Excerpts from Nikola Đipanov's message of 2015-02-11 05:26:47 -0800: > On 02/11/2015 02:13 PM, Sean Dague wrote: > > > > If core team members start dropping off external IRC where they are > > communicating across corporate boundaries, then the local tribal effects > > start taking over. You get p

Re: [openstack-dev] [nova] Flavor extra-spec and image metadata documentation

On Wed, Feb 11, 2015 at 5:15 AM, Daniel P. Berrange wrote: > On Wed, Feb 11, 2015 at 12:03:58PM +0100, Pasquale Porreca wrote: > > Thank you for all answers. > > I know that meta data tags are "free" to use with any key/value, still > > there are some specific values that triggers pieces of code

Re: [openstack-dev] [devstack] Compute-node-only installation fails

On Wed, Feb 11, 2015 at 08:32:31AM -0800, Clark Boylan wrote: > On Wed, Feb 11, 2015, at 08:18 AM, Alexander Schmidt wrote: > > Hi Daniel, > > > > with your recent change[1] to error handling in stack.sh, compute > > node only installations via devstack fail because there is > > no database select

[openstack-dev] [nova] Feature Freeze Exception Request

Hello, I'd like to request a feature freeze exception for the change, https://review.openstack.org/#/c/149828/ This change implements NestedQuotaDriver that does the quota management in nested projects. The specs has been merged : https://review.openst

[openstack-dev] openstack/requirements failure

Hi In horizon I am trying to increase the python-heatclient>=0.3.0 as part of the review https://review.openstack.org/#/c/154952/ and its failed with following error: "Requirement python-heatclient>=0.3.0 does not match openstack/requirements value python-heatclient>=0.2.9" More details at h

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

Excerpts from Stefano Maffulli's message of 2015-02-11 06:14:39 -0800: > On Wed, 2015-02-11 at 10:55 +0100, Flavio Percoco wrote: > > This email is dedicated to the openness of our community/project. > > It's good to have a reminder every now and then. Thank you Flavio for > caring enough to notic

Re: [openstack-dev] [cinder] CURD operation for storage pools in Cinder

As far as I know, this has not been looked at - you need to use whatever management tools your backend provides to do this. There was somebody from Intel IIRC in Paris with some interest in maybe starting something about this, but I don't know that it came to much. Duncan Thomas On Feb 11, 2015 6

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

Stefano, I was informed (in a private message on IRC) that where I said "Twenty First amendment" I should have said "Eighteenth Amendment". The former repealed the latter. My apologies to all who were trying to figure out what I may have meant. -amrith P.S. Why I got that in a private message

[openstack-dev] [nova][vmware] FFE request for ephemeral disk support

Hi, The support for the feature has been in flight for over a year now. There is one outstanding patch - the resize of ephemeral disks [I]. The patch is based on a series of patches that address critical issues when resizing (which were exposed when we were testing this feature). I really hope th

Re: [openstack-dev] openstack/requirements failure

On 02/11/2015 11:33 AM, Manickam, Kanagaraj wrote: > Hi > > In horizon I am trying to increase the python-heatclient>=0.3.0 as part of > the review https://review.openstack.org/#/c/154952/ and its failed with > following error: > > > "Requirement python-heatclient>=0.3.0 does not match opensta

Re: [openstack-dev] [devstack] Compute-node-only installation fails

On 02/11/2015 11:32 AM, Clark Boylan wrote: > On Wed, Feb 11, 2015, at 08:18 AM, Alexander Schmidt wrote: >> Hi Daniel, >> >> with your recent change[1] to error handling in stack.sh, compute >> node only installations via devstack fail because there is >> no database selected. A database should no

[openstack-dev] [nova][horizon] Inter-project issue : redundant hyperviosr_hostname

Hi, Nova provides following REST API to get the details of instances provisioned in the given hypervisor. REST API: /v2/​{tenant_id}​/os-hypervisors/​{hypervisor_hostname}​/servers Ref: http://developer.openstack.org/api-ref-compute-v2-ext.html This API is consumed in horizon to report hyperviso

Re: [openstack-dev] [keystone] [nova]

On 02/11/2015 12:16 PM, Nikolay Makhotkin wrote: No, I just checked it. Nova receives trust token and raise this error. In my script, I see: http://paste.openstack.org/show/171452/ And as you can see, token from trust differs from direct user's token. The original user needs to have the appr

Re: [openstack-dev] [neutron] DVR and l2_population

L2pop is a requirement. With the existing agent-based architecture, L2pop is used to update the FDB tables on the compute hosts to make east/west traffic possible whenever a new port is created or existing one is updated. Cheers, Armando On 10 February 2015 at 23:07, Itzik Brown wrote: > Hi, >

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 02/11/2015 11:19 AM, Amrith Kumar wrote: > Stefano, > > You write: > > | This is seriously disturbing. > | > | If you're one of those core reviewers hanging out on a private channel, > | please contact me privately: I'd love to hear from you why we failed as a > | community at convincing you

Re: [openstack-dev] [congress][Policy][Copper]Collaboration between OpenStack Congress and OPNFV Copper

Hi Zhipeng, We’d be happy to meet. Sounds like fun! I don’t know of anyone on the Congress team who is planning to attend the LF collaboration summit. But we might be able to send a couple of people if it’s the only real chance to have a face-to-face. Otherwise, there are a bunch of us in a

Re: [openstack-dev] [nova] Feature Freeze Exception Request

+1 The specs has been merged through FFE request, doesn't that mean the BP is already approved? Maybe the status of the BP just need to be updated to reflect the current state. -Lin On Wed, Feb 11, 2015 at 9:26 AM, Sajeesh Cimson Sasi wrote: > Hello, >I'd like to request a featur

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 02/11/2015 04:52 AM, Daniel P. Berrange wrote: > On Wed, Feb 11, 2015 at 10:55:18AM +0100, Flavio Percoco wrote: >> Greetings all, >> >> During the last two cycles, I've had the feeling that some of the >> things I love the most about this community are degrading and moving >> to a state that I

[openstack-dev] debtcollector 0.2.0 released

The Oslo team is pleased to announce the release of: debtcollector 0.2.0: A collection of python patterns that help you collect your technical debt in a non-destructive manner. For more details, please see the git log history below and: http://launchpad.net/debtcollector/+milestone/0.2 Ple

Re: [openstack-dev] [neutron] DVR and l2_population

Thanks Armando. Another question: Every compute node that hosts instances with floating IPs has an IP from the external network pool. If the SNAT is done by the Network Node what is the reason for the compute node to have an external IP? BR, Itzik On 02/11/2015 08:13 PM, Armando M. wrote: L

Re: [openstack-dev] [cinder] CURD operation for storage pools in Cinder

Hi Duncan and Pradip, It was Reddy, a colleague of mine at Intel, that expressed interest with managing storage pools in Cinder. We haven’t put a BP out yet, but we definitely think it would be useful and we should get a BP in the works. - Curt From: Duncan Thomas mailto:duncan.tho...@gmail.c

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

Ping. Chris, Alex, Ken, do we have an answer to Claudiu's questions below? On 02/02/2015 05:51 PM, Claudiu Belu wrote: 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 i

  1   2   >