Re: [openstack-dev] [Ceilometer][SUSE] SUSE OpenStack Havana distribution is different with upstream

Hi, Le jeudi 27 février 2014, à 09:12 +0800, ZhiQiang Fan a écrit : > thanks, Vincent > > I already noticed that the critical bug is caused by a wrong backport, just > in the > 0001-enable-sql-metadata-query.patch

[openstack-dev] [Mistral] a question about Mistral

Hi, Mistral members I am very interesting in the project Mistral. About the wiki of the Mistral, I have a question about the use case description as the follow. "Live migration A user specifies tasks for VM live migration triggered upon an event from Ceilometer (CPU consumption 100%)." Is th

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

Hi Eugene, Thanks for the provided detail. See my comments below. The point is to be able to share IP address, it really means that two VIPs(as we understand them in current model) need to reside within same backend (technically they need to share neutron port). Aren't we leaking some implemen

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

+1 From: Youcef Laribi [mailto:youcef.lar...@citrix.com] Sent: Thursday, February 27, 2014 10:11 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion Hi Eugene, Thanks for the provided detail. See my comments be

[openstack-dev] does exception need localize or not?

refer to : https://wiki.openstack.org/wiki/Translations now some exception use _ and some not. the wiki suggest do not to do that. but i'm not sure. what's the correct way? F.Y.I What To Translate At present the convention is to translate/all/user-facing strings. This means API m

Re: [openstack-dev] [TripleO][Tuskar] JSON output values from Tuskar API

On 26/02/14 18:38, Petr Blaho wrote: I am wondering what is the OpenStack way of returning json from apiclient. Good question, I think its important for us to be as consistent as possible. By looking at API docs at http://api.openstack.org/ I can say that projects use both ways, altought what

Re: [openstack-dev] [Neutron] Does l2-pop sync fdb on agent start ?

Hi, As agent rebuilds br-tun at startup, l2pop MD is supposed to provide agent with the whole list of fdb entries when it boots. You may hit this bug [1] that can prevent some flows to be appended to OVS? [1] https://bugs.launchpad.net/neutron/+bug/1263866 2014-02-27 4:53 GMT+01:00 Zang MingJi

Re: [openstack-dev] [Neutron] Does l2-pop sync fdb on agent start ?

Yes, the agent sync fdb on startup thanks to the flag 'agent_boot_time' (default 180 seconds). Plugin compares it with time agent is started (diff between the agent start (agent.started.at) and its last heartbeat timestamp) and if it less, the plugin send all fdb entries of the network. Édoaurd.

Re: [openstack-dev] [TripleO][Tuskar] JSON output values from Tuskar API

On 26/02/14 19:17, Jay Dobies wrote: This is a new concept to me in JSON, I've never heard of a wrapper element like that being called a namespace. It's certainly not in the spec AFAIK, but I've seen this approach before in various places. My first impression is that is looks like cruft. If

Re: [openstack-dev] [Mistral] a question about Mistral

Hey, Can you please provide more details on what you’re interested in? What do you mean by DRS? If you mean VMware Distributed Resource Scheduler then yes and no. It’s not the major goal of Mistral but Mistral is a more generic tool that could be used to build something like this. The primary

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

> > > > The point is to be able to share IP address, it really means that two > VIPs(as we understand them in current model) need to reside within same > backend (technically they need to share neutron port). > > > > Aren't we leaking some implementation detail here? > I see IP address sharing as u

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 26/02/14 19:43, Jay Dobies wrote: * Even at this level, it exposes the underlying guts. There are calls to nova baremetal listed in there, but eventually those will turn into ironic calls. It doesn't give us a ton of flexibility in terms of underlying technology if that knowledge bubbles up to

Re: [openstack-dev] How to implement and configure a new Neutron vpnaas driver from scratch?

I'm following the change you pointed a week ago. It seems that it is working now, and will be eventually approved soon. I will be happy when it is approved. Anyway, I need more information about how to develop a service driver and a device driver for VPN plugin. I realize doing reverse-engineering

Re: [openstack-dev] [nova] why doesn't _rollback_live_migration() always call rollback_live_migration_at_destination()?

On 25 February 2014 15:44, Chris Friesen wrote: > On 02/25/2014 05:15 AM, John Garbutt wrote: >> >> On 24 February 2014 22:14, Chris Friesen >> wrote: > > > >>> What happens if we have a shared-storage instance that we try to migrate >>> and >>> fail and end up rolling back? Are we going to end

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

From: Eugene Nikanorov [mailto:enikano...@mirantis.com] Sent: Thursday, February 27, 2014 11:12 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion The point is to be able to share IP address, it really means

Re: [openstack-dev] How to implement and configure a new Neutron vpnaas driver from scratch?

Hi Julio, You can take https://review.openstack.org/#/c/74156/ and https://review.openstack.org/#/c/74144/ as examples to write your own vpnaas driver. More info about service type framework, you can also refer to neutron/services/loadbalancer codes. - Original Message - From: "Julio

Re: [openstack-dev] How do I mark one option as deprecating another one ?

Hi Denis, Thanks for the pointer, but I looked at that and I my understanding is that it only allows me to retrieve a value by an old name, but doesn't let me know that the old name has been used. So If all I wanted to do was change the name/group of the config value it would be fine. But in

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 26/02/14 13:34, Jiří Stránský wrote: Hello, i went through the CLI way of deploying overcloud, so if you're interested what's the workflow, here it is: https://gist.github.com/jistr/9228638 This is great, thanks for taking the time to put it together. Another thing to add to my list of stu

Re: [openstack-dev] [Tripleo] tripleo-cd-admins team update / contact info question

On 25/02/14 22:30, Robert Collins wrote: > In the tripleo meeting today we re-affirmed that the tripleo-cd-admins > team is aimed at delivering production-availability clouds - thats how > we know the the tripleo program is succeeding (or not !). > > So if you're a member of that team, you're on t

Re: [openstack-dev] [nova] New Websockify Release

Solly Ross wrote: > We (the websockify/noVNC team) have released a new version of websockify > (0.6.0). It contains several fixes and features relating to OpenStack (a > couple of bugs were fixed, and native support for the `logging` module was > added). Unfortunately, to integrate it into Ope

Re: [openstack-dev] [glance] Switching from sql_connection to [database] connection ?

On 27/02/14 12:12 +0800, Tom Fifield wrote: Hi, As best I can tell, all other services now use this syntax for configuring database connections: [database] connection = sqlite:///etc,omg whereas glance appears to still use [DEFAULT] ... sql_connection = sqlite:///etc,omg Is there a plan

Re: [openstack-dev] [nova] New Websockify Release

On 02/27/2014 11:22 AM, Thierry Carrez wrote: > Solly Ross wrote: >> We (the websockify/noVNC team) have released a new version of websockify >> (0.6.0). It contains several fixes and features relating to OpenStack (a >> couple of bugs were fixed, and native support for the `logging` module was

Re: [openstack-dev] [TripleO][Tuskar] JSON output values from Tuskar API

On Wed, Feb 26, 2014 at 02:17:53PM -0500, Jay Dobies wrote: > This is a new concept to me in JSON, I've never heard of a wrapper > element like that being called a namespace. I named it "namespace" in my email. It is not any kind of formal or standard naming. "Wrapper element" is better name for

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 26.2.2014 20:43, Jay Dobies wrote: I'd say it's still an open question whether we'll want to give better UX than that ^^ and at what cost (this is very much tied to the benefits and drawbacks of various solutions we discussed in December [1]). All in all it's not as bad as i expected it to be

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

> > I see IP address sharing as user intent, not an implementation detail. > Same backend could be not only the only obstacle here. > > The backend is not exposed anyhow by the API, by the way. > > When you create root object with flavor - you really can't control to > which driver it will be sched

Re: [openstack-dev] [nova] [glance] [heat] bug 1203680 - fix requires doc

On 02/27/2014 12:52 AM, Mike Spreitzer wrote: > Dean Troyer wrote on 02/26/2014 03:28:04 PM: > >> On Wed, Feb 26, 2014 at 1:09 PM, Mike Spreitzer > wrote: >>> Thanks for the further updates. I have just one question about >>> those. One way to do both unit testing and system (integration) >>>

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 27.2.2014 10:16, Dougal Matthews wrote: On 26/02/14 13:34, Jiří Stránský wrote: get Tuskar UI a bit closer back to the fact that Undercloud is OpenStack too, and keep the name "Flavors" instead of changing it to "Node Profiles". I wonder if that would be unwelcome to the Tuskar UI UX, though.

Re: [openstack-dev] How do I mark one option as deprecating another one ?

Phil, Correct. We don't have this functionality in oslo.config. Please create a new feature/enhancement request against oslo thanks, dims On Thu, Feb 27, 2014 at 4:47 AM, Day, Phil wrote: > Hi Denis, > > > > Thanks for the pointer, but I looked at that and I my understanding is that > it only a

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 26.2.2014 21:34, Dean Troyer wrote: On Wed, Feb 26, 2014 at 1:43 PM, Jay Dobies wrote: I like the notion of OpenStackClient. I'll talk ideals for a second. If we had a standard framework and each project provided a command abstraction that plugged in, we could pick and choose what we includ

[openstack-dev] [neutron]the discussion about traffic storm protection in network virtualization environment

Hi everyone: A traffic storm occurs when broadcast, unknown unicast, or multicast (BUM) packets flood the LAN, creating excessive traffic and degrading network performance. So physical switch or router offer traffic storm protection, these approaches: 1.Storm suppression, which

Re: [openstack-dev] WSME / Pecan and only supporting JSON?

On Thu, Feb 27, 2014 at 12:48 AM, Michael Davies wrote: > Hi everyone, > > Over in "Ironic Land" we're looking at removing XML support from > ironic-api (i.e. https://bugs.launchpad.net/ironic/+bug/1271317) > > I've been looking, but I can't seem to find an easy way to modify the > accepted conten

Re: [openstack-dev] WSME / Pecan and only supporting JSON?

Le 27/02/2014 14:13, Doug Hellmann a écrit : WSME supports both protocols without the API developer having to do any extra work. Doug Just one comment about WSGI middlewares that we could create for Pecan, we still need to handle both XML and JSON by hand. I do agree this is not WSME relat

Re: [openstack-dev] WSME / Pecan and only supporting JSON?

On Thu, Feb 27, 2014 at 2:00 AM, Noorul Islam K M wrote: > Michael Davies writes: > > > Hi everyone, > > > > Over in "Ironic Land" we're looking at removing XML support from > ironic-api > > (i.e. https://bugs.launchpad.net/ironic/+bug/1271317) > > > > I've been looking, but I can't seem to find

Re: [openstack-dev] WSME / Pecan and only supporting JSON?

On 02/27/2014 08:13 AM, Doug Hellmann wrote: > > > > On Thu, Feb 27, 2014 at 12:48 AM, Michael Davies > wrote: > > Hi everyone, > > Over in "Ironic Land" we're looking at removing XML support from > ironic-api (i.e. https://bugs.launchpad.net/ironic/

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On Thu, Feb 27, 2014 at 6:36 AM, Jiří Stránský wrote: > Thanks for bringing this up. It looks really interesting. Is it possible > to not only add commands to the OpenStackClient, but also purposefully > blacklist some from appearing? As Jay mentioned in his reply, we don't make > use of many com

[openstack-dev] heads up, set -o errexit on devstack - things will fail earlier now

This patch is coming through the gate this morning - https://review.openstack.org/#/c/71996/ The point being to actually make devstack stop when it hits an error, instead of only once these compound to the point where there is no moving forward and some service call fails. This should *dramaticall

Re: [openstack-dev] WSME / Pecan and only supporting JSON?

On Thu, Feb 27, 2014 at 8:28 AM, Sean Dague wrote: > On 02/27/2014 08:13 AM, Doug Hellmann wrote: > > > > > > > > On Thu, Feb 27, 2014 at 12:48 AM, Michael Davies > > wrote: > > > > Hi everyone, > > > > Over in "Ironic Land" we're looking at removing XML su

Re: [openstack-dev] [Neutron][IPv6] BP:Store both IPv6 LLA and GUA address on router interface port

Hi Xuhan, Thank you for your summary. see comments inline. --Robert On 2/27/14 12:49 AM, "Xuhan Peng" mailto:pengxu...@gmail.com>> wrote: As the follow up action of IPv6 sub-team meeting [1], I created a new blueprint [2] to store both IPv6 LLA and GUA address on router interface port. Here

Re: [openstack-dev] Hacking and PEP 257: Extra blank line at end of multi-line docstring

On Feb 26, 2014, at 11:47 AM, Joe Gordon wrote: > On Wed, Feb 26, 2014 at 9:05 AM, David Ripton wrote: >> On 02/26/2014 11:40 AM, Joe Gordon wrote: >> >>> This is missing the point about manually enforcing style. If you pass >>> the 'pep8' job there is no need to change any style. >> >> >> I

Re: [openstack-dev] [TripleO] Tuskar CLI UX

Yeah. This is a double bladed axe but i'm leaning towards naming flavors consistently a bit more too. Here's an attempt at +/- summary: "node profile" + a bit more descriptive for a newcomer imho - CLI renaming/reimplementing mentioned before - inconsistency dangers lurking in the deep - e.g.

[openstack-dev] [gantt] How to change jenkins to run tempest to run tests against the gantt scheduler

For a significant transition period gantt (the separated out scheduler) will be an optional component that requires extra configuration options when setting up devstack to use it. As such we need to create the Jenkins jobs to do this configuration when running the tempest tests. Note that give

[openstack-dev] [rally] [smart-scenario-args]

Hello, Problem: what about deployment specific parts Template string in config? %imageid% or similar? Image name regex, rather than image name? so can work with multiple deployments, eg ^cirros$ so we have a few solutions for today: function, vars, and "special args". FUNCTION a

Re: [openstack-dev] WSME / Pecan and only supporting JSON?

Doug, On Feb 27, 2014, at 7:23 AM, Doug Hellmann mailto:doug.hellm...@dreamhost.com>> wrote: On Thu, Feb 27, 2014 at 2:00 AM, Noorul Islam K M mailto:noo...@noorul.com>> wrote: Michael Davies mailto:mich...@the-davies.net>> writes: > Hi everyone, > > Over in "Ironic Land" we're looking at remo

Re: [openstack-dev] [nova] Future of the Nova API

> So I think once we start returning different response codes, or > completely different structures (such as the tasks change will be), it > doesn't matter if we make the change in effect by invoking /v2 prefix > or /v3 prefix or we look for a header. Its a major api revision. I > don't think we sh

[openstack-dev] [Neutron][LBaaS] Weekly meeting

Thanks everyone for joining, meeting logs: Meeting ended Thu Feb 27 15:00:42 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Minutes: http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-02-27-14.00.html Minutes (text): http://eavesdro

Re: [openstack-dev] [TripleO] Tuskar CLI UX

Hello, I think if we will use Openstack CLI, it has to be something like this https://github.com/dtroyer/python-oscplugin. Otherwise we are not Openstack on Openstack. Btw. abstracting it all to one big CLI will be just more confusing when people will debug issues. So it would have to be don

Re: [openstack-dev] [devstack] Bug in is_*_enabled functions?

On 02/26/2014 05:18 PM, Carl Baldwin wrote: > Brian, > > In shell it is correct to return 0 for success and non-zero for failure. But, at least in lib/neutron, there is a check like this: if is_service_enabled neutron; then ... fi Which will fail with a 0 return code and miss some config. It s

Re: [openstack-dev] heads up, set -o errexit on devstack - things will fail earlier now

On Thu, Feb 27, 2014 at 08:38:22AM -0500, Sean Dague wrote: > This patch is coming through the gate this morning - > https://review.openstack.org/#/c/71996/ > > The point being to actually make devstack stop when it hits an error, > instead of only once these compound to the point where there is n

Re: [openstack-dev] [nova] Future of the Nova API

On 02/27/2014 08:43 AM, Dan Smith wrote: So I think once we start returning different response codes, or completely different structures (such as the tasks change will be), it doesn't matter if we make the change in effect by invoking /v2 prefix or /v3 prefix or we look for a header. Its a major

Re: [openstack-dev] [TripleO] Tuskar CLI UX

> Hello, > > I think if we will use Openstack CLI, it has to be something like this > https://github.com/dtroyer/python-oscplugin. > Otherwise we are not Openstack on Openstack. > > Btw. abstracting it all to one big CLI will be just more confusing when > people will debug issues. So it would > h

Re: [openstack-dev] WSME / Pecan and only supporting JSON?

On Thu, Feb 27, 2014 at 5:28 AM, Sean Dague wrote: > On 02/27/2014 08:13 AM, Doug Hellmann wrote: > > > > > > > > On Thu, Feb 27, 2014 at 12:48 AM, Michael Davies > > wrote: > > > > Hi everyone, > > > > Over in "Ironic Land" we're looking at removing XML su

[openstack-dev] Help oslo-incubator team == Help your project - some advices

Hi Stackers, Intro: It goes without saying words that we have the same code in different projects: RPC, DB, Python clients, and a lot of other parts. In case of fast growing OpenStack there were some issues in evolving and instead of doing libs and new projects from the blank page on top of these

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 02/27/2014 04:41 PM, Tzu-Mainn Chen wrote: Hello, I think if we will use Openstack CLI, it has to be something like this https://github.com/dtroyer/python-oscplugin. Otherwise we are not Openstack on Openstack. Btw. abstracting it all to one big CLI will be just more confusing when people w

Re: [openstack-dev] [nova] Future of the Nova API

> Sure, but that's still functionally equivalent to using the /v2 prefix. > So we could chuck the current /v3 code and do: > > /v2: Current thing > /v3: invalid, not supported > /v4: added simple task return for server create > /v5: added the event extension > /v6: added a new event for cinder to

[openstack-dev] [oslo][productivity] Help oslo-incubator team == Help your project - some advices

Hi Stackers, Intro: It goes without saying words that we have the same code in different projects: RPC, DB, Python clients, and a lot of other parts. In case of fast growing OpenStack there were some issues in evolving and instead of doing libs and new projects from the blank page on top of these

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 27/02/14 15:08, Ladislav Smola wrote: Hello, I think if we will use Openstack CLI, it has to be something like this https://github.com/dtroyer/python-oscplugin. Otherwise we are not Openstack on Openstack. Btw. abstracting it all to one big CLI will be just more confusing when people will de

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

So a couple of things about this: 1) Today (and also true for Grizzly and Havana), the user can chose what LDAP attribute should be returned as the user or group ID. So it is NOT a safe assumption today (ignoring any support for domain-specific LDAP support) that the format of a user or group

Re: [openstack-dev] WSME / Pecan and only supporting JSON?

On Thu, Feb 27, 2014 at 9:33 AM, Adrian Otto wrote: > Doug, > > On Feb 27, 2014, at 7:23 AM, Doug Hellmann > wrote: > > On Thu, Feb 27, 2014 at 2:00 AM, Noorul Islam K M wrote: > >> Michael Davies writes: >> >> > Hi everyone, >> > >> > Over in "Ironic Land" we're looking at removing XML supp

[openstack-dev] [TROVE] Trove replication meeting

Good day, DBaaS community. Yesterday, at meeting was mentioned that some one (maybe from core team) going to schedule hangout meeting related replication implementation. Would be better if the person who's going to schedule and organize meeting will send the notification to openstack-dev to let

Re: [openstack-dev] [Mistral] std:repeat action

Thanks Manas! This is one of the important things we need to get done within the next couple of weeks. Since it’s going to affect engine I think we need to wait for a couple of days with the implementation till we merge the changes that are being worked on and that also affect engine significan

Re: [openstack-dev] [QA] The future of nosetests with Tempest

On Tue, Feb 25, 2014 at 07:46:23PM -0600, Matt Riedemann wrote: > > > On 2/12/2014 1:57 PM, Matthew Treinish wrote: > >On Wed, Feb 12, 2014 at 11:32:39AM -0700, Matt Riedemann wrote: > >> > >> > >>On 1/17/2014 8:34 AM, Matthew Treinish wrote: > >>>On Fri, Jan 17, 2014 at 08:32:19AM -0500, David K

Re: [openstack-dev] [devstack] Bug in is_*_enabled functions?

On 02/26/2014 04:23 PM, Brian Haley wrote: > On 02/26/2014 01:36 PM, Dean Troyer wrote: >> On Wed, Feb 26, 2014 at 11:51 AM, Brian Haley > > wrote: >> >> While trying to track down why Jenkins was handing out -1's in a >> Neutron patch, >> I was seeing errors

Re: [openstack-dev] [Mistral] Defining term DSL

I looked at the review prior to looking at the discussion and even I was confused by names like DSL*. The way I see it DSL is largely syntatic sugar and therefore it will be good to have a clear separation between DSL and model. The fact that something is defined in a DSL is irrelevant once it cros

Re: [openstack-dev] [QA] The future of nosetests with Tempest

This is another example of achieving the same result (exclusion from a list): https://git.openstack.org/cgit/openstack/tripleo-image-elements/tree/element s/tempest/tests2skip.py https://git.openstack.org/cgit/openstack/tripleo-image-elements/tree/element s/tempest/tests2skip.txt andrea -Orig

Re: [openstack-dev] [Mistral] Renaming action types

How about ... invoke_http & invoke_mistral to fit the verb_noun pattern. On Wed, Feb 26, 2014 at 6:04 AM, Renat Akhmerov wrote: > Ooh, I was wrong. Sorry. We use dash naming. We have "on-success", > "on-error" and so forth. > > Please let us know if you see other inconsistencies. > > Thanks > >

Re: [openstack-dev] [Mistral] Renaming "events" to "triggers" and move them out of "Workflow"

Agreed on both event -> trigger & moving triggers out of workflow. Lets get the blueprint started. /manas On Wed, Feb 26, 2014 at 8:51 PM, Renat Akhmerov wrote: > Hi team, > > When I tell peopleI about Mistral I always have a hard time explaining why > we use term "event" for declaring ways to

Re: [openstack-dev] [devstack] Bug in is_*_enabled functions?

On Thu, Feb 27, 2014 at 10:34 AM, Brian Haley wrote: > Ok, part of this is my kernel background, where true=1 like it should be :) > So there's a -EUSERERROR there. > Right. This is Bourne/POSIX shell, forget everything logical. ;) > That call to 'ip netns exec...' should be: > > sudo /usr/lo

Re: [openstack-dev] [nova] Future of the Nova API

On 02/27/2014 11:05 AM, Dan Smith wrote: >> Sure, but that's still functionally equivalent to using the /v2 prefix. >> So we could chuck the current /v3 code and do: >> >> /v2: Current thing >> /v3: invalid, not supported >> /v4: added simple task return for server create >> /v5: added the event e

Re: [openstack-dev] [devstack] Bug in is_*_enabled functions?

On 02/27/2014 11:55 AM, Dean Troyer wrote: > On Thu, Feb 27, 2014 at 10:34 AM, Brian Haley > wrote: > > Ok, part of this is my kernel background, where true=1 like it should be > :) > So there's a -EUSERERROR there. > > > Right. This is Bourne/POSIX shell, f

Re: [openstack-dev] packstack support for DRBD based installation

On 2014-02-26 16:52, Curious Human wrote: > Hi , > > We are using packstack based openstack installation. I am working on > providing HA support for Openstack services and dependent 3rd part services > like mysql etc . I will be using DRBD and pacemaker based HA functionality. > Is there

Re: [openstack-dev] [nova] Future of the Nova API

> I do think client headers instead of urls have some pragmatic > approach here that is very attractive. Will definitely need a good > chunk of plumbing to support that in a sane way in the tree that > keeps the overhead from a review perspective low. Aside from some helper functions to make this

Re: [openstack-dev] heads up, set -o errexit on devstack - things will fail earlier now

On 2014-02-27 09:23, Daniel P. Berrange wrote: On Thu, Feb 27, 2014 at 08:38:22AM -0500, Sean Dague wrote: This patch is coming through the gate this morning - https://review.openstack.org/#/c/71996/ The point being to actually make devstack stop when it hits an error, instead of only once thes

Re: [openstack-dev] Hacking and PEP 257: Extra blank line at end of multi-line docstring

On 2014-02-27 08:05, Ziad Sawalha wrote: On Feb 26, 2014, at 11:47 AM, Joe Gordon wrote: On Wed, Feb 26, 2014 at 9:05 AM, David Ripton wrote: On 02/26/2014 11:40 AM, Joe Gordon wrote: This is missing the point about manually enforcing style. If you pass the 'pep8' job there is no need to

Re: [openstack-dev] Devstack Error

The role add sounds like a problem where a variable didn't get initialized correctly, but that's about all I can guess from this, and I don't know anything about devstack-gate so I'm afraid I can't help with that. Sean's devstack errexit change (which just merged) might help you track this dow

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

On Thu, 2014-02-27 at 16:13 +, Henry Nash wrote: > So a couple of things about this: > > > 1) Today (and also true for Grizzly and Havana), the user can chose > what LDAP attribute should be returned as the user or group ID. So it > is NOT a safe assumption today (ignoring any support for >

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

On 27 Feb 2014, at 17:52, Jay Pipes wrote: > On Thu, 2014-02-27 at 16:13 +, Henry Nash wrote: >> So a couple of things about this: >> >> >> 1) Today (and also true for Grizzly and Havana), the user can chose >> what LDAP attribute should be returned as the user or group ID. So it >> is NO

Re: [openstack-dev] How do I mark one option as deprecating another one ?

On 2/27/2014 6:32 AM, Davanum Srinivas wrote: Phil, Correct. We don't have this functionality in oslo.config. Please create a new feature/enhancement request against oslo thanks, dims Done: https://bugs.launchpad.net/oslo/+bug/1285768 On Thu, Feb 27, 2014 at 4:47 AM, Day, Phil wrote: H

[openstack-dev] [Nova] why force_config_drive is a per comptue node config

Greeting, I have some questions on the force_config_drive configuration options and hope get some hints. a) Why do we want this? Per my understanding, if the user want to use the config drive, they need specify it in the nova boot. Or is it because possibly user have no idea of the

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

On Thu, Feb 27, 2014 at 11:52 AM, Jay Pipes wrote: > On Thu, 2014-02-27 at 16:13 +, Henry Nash wrote: > > So a couple of things about this: > > > > > > 1) Today (and also true for Grizzly and Havana), the user can chose > > what LDAP attribute should be returned as the user or group ID. So i

Re: [openstack-dev] [Neutron][IPv6] tox error

Shixiong Shang and I ran into this problem with Tox today while we were pair programming, and I've also seen similar barfs on my DevStack lab boxes - it's quite a mess. Frankly I've moved to using nosetests as a workaround, and have added it to the developer docs. We really do need to figure out

[openstack-dev] [Congress] Design doc for Data sources

Updated the Neutron tables based on the example. It will be great if we have similar file for keystone and nova as well https://docs.google.com/document/d/1K9RkQuBSPN7Z2TmKfok7mw3E24otEGo8Pnsemxd5544/edit Thanks Rajdeep ___ OpenStack-dev mailing list Op

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

On Thursday, February 27, 2014, Dolph Mathews wrote: > > On Thu, Feb 27, 2014 at 11:52 AM, Jay Pipes > > > wrote: > >> On Thu, 2014-02-27 at 16:13 +, Henry Nash wrote: >> > So a couple of things about this: >> > >> > >> > 1) Today (and also true for Grizzly and Havana), the user can chose >

Re: [openstack-dev] [Neutron][IPv6] tox error

On Thu, Feb 27, 2014 at 11:39 AM, Collins, Sean wrote: > Shixiong Shang and I ran into this problem with Tox today while we were > pair programming, and I've also seen similar barfs on my DevStack lab > boxes - it's quite a mess. Frankly I've moved to using nosetests as a > workaround, and have ad

Re: [openstack-dev] heads up, set -o errexit on devstack - things will fail earlier now

Thu, Feb 27, 2014 at 9:34 AM, Ben Nemec wrote: > On 2014-02-27 09:23, Daniel P. Berrange wrote: > >> On Thu, Feb 27, 2014 at 08:38:22AM -0500, Sean Dague wrote: >> >>> This patch is coming through the gate this morning - >>> https://review.openstack.org/#/c/71996/ >>> >>> The point being to actu

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

I agree about not needing extra identity information outside of the user's UUID, but what about the role/project/domain information stored in the PKI token? Does it remain or go away? From: Morgan Fainberg [mailto:m...@metacloud.com] Sent: Thursday, February 27, 2014 12:11 PM To: OpenStack Devel

[openstack-dev] asymmetric gating and stable vs unstable tests

Hi all, I'd like to point out how asymmetric gating is challenging for incubated projects, and propose that there may be a way to make it less so. For reference, incubated projects aren't allowed to have symmetric gating with integrated projects. This is why our devstack and tempest tests are "*-

Re: [openstack-dev] [Nova] why force_config_drive is a per comptue node config

On Fri, Feb 28, 2014 at 6:34 AM, yunhong jiang wrote: > Greeting, > I have some questions on the force_config_drive configuration options > and hope get some hints. > a) Why do we want this? Per my understanding, if the user want to use > the config drive, they need specify it in t

Re: [openstack-dev] [nova] Future of the Nova API

On Thu, 27 Feb 2014 09:41:45 -0800 Dan Smith wrote: > > Aside from some helper functions to make this consistent, and some > things to say "here's the code I want to return, but compat clients > need /this/ code", I think this actually gets us most of the way > there: > > http://paste.openstack.

Re: [openstack-dev] [nova] Future of the Nova API

On Thu, 27 Feb 2014 12:02:45 -0500 Sean Dague wrote: > > I do think client headers instead of urls have some pragmatic approach > here that is very attractive. Will definitely need a good chunk of > plumbing to support that in a sane way in the tree that keeps the > overhead from a review perspec

Re: [openstack-dev] [OpenStack-Infra] [third-party-ci] Proposing a regular workshop/meeting to help folks set up CI environments

On Wed, 2014-02-26 at 12:09 +, trinath.soman...@freescale.com wrote: > Hi Jay- > > Rather than March 3rd > > Can you kindly make it on Feb 28th if possible. Unfortunately, Trinath, I can't make it tomorrow during that time. I can try and be on IRC earlier in the day, though, to help you? >

Re: [openstack-dev] [nova] Future of the Nova API

> So whilst we still have extensions (and that's a separate debate) we > need versioning on a per extension basis. Otherwise people are forced > to upgrade their extensions in lockstep with each other. I think that some people would argue that requiring the extensions to go together linearly is

Re: [openstack-dev] heads up, set -o errexit on devstack - things will fail earlier now

And a big +1 from me too. It's really useful. On Fri, Feb 28, 2014 at 12:15 AM, Devananda van der Veen wrote: > Thu, Feb 27, 2014 at 9:34 AM, Ben Nemec wrote: >> >> On 2014-02-27 09:23, Daniel P. Berrange wrote: >>> >>> On Thu, Feb 27, 2014 at 08:38:22AM -0500, Sean Dague wrote: This

Re: [openstack-dev] Hacking and PEP 257: Extra blank line at end of multi-line docstring

On Thu, Feb 27, 2014 at 6:05 AM, Ziad Sawalha wrote: > > On Feb 26, 2014, at 11:47 AM, Joe Gordon wrote: > >> On Wed, Feb 26, 2014 at 9:05 AM, David Ripton wrote: >>> On 02/26/2014 11:40 AM, Joe Gordon wrote: >>> This is missing the point about manually enforcing style. If you pass the

Re: [openstack-dev] Hacking and PEP 257: Extra blank line at end of multi-line docstring

On Thu, Feb 27, 2014 at 9:29 AM, Ben Nemec wrote: > On 2014-02-27 08:05, Ziad Sawalha wrote: >> >> On Feb 26, 2014, at 11:47 AM, Joe Gordon wrote: >> >>> On Wed, Feb 26, 2014 at 9:05 AM, David Ripton wrote: On 02/26/2014 11:40 AM, Joe Gordon wrote: > This is missing the point

[openstack-dev] [savanna] team meeting minutes Feb 27

Thanks everyone who have joined Savanna meeting. Here are the logs from the meeting: Minutes: http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-27-18.01.html Log: http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-27-18.01.log.html -- Sincerely yours, Serg

Re: [openstack-dev] [Nova] why force_config_drive is a per comptue node config

> -Original Message- > From: Michael Still [mailto:mi...@stillhq.com] > Sent: Thursday, February 27, 2014 1:04 PM > To: yunhong jiang > Cc: OpenStack Development Mailing List > Subject: Re: [openstack-dev] [Nova] why force_config_drive is a per > comptue node config > > On Fri, Feb 28, 2

Re: [openstack-dev] [Nova] why force_config_drive is a per comptue node config

Hi, Michael, I created a bug at https://bugs.launchpad.net/nova/+bug/1285880 and please have a look. Thanks --jyh > -Original Message- > From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com] > Sent: Thursday, February 27, 2014 1:35 PM > To: OpenStack Development Mailing List (not for usa

[openstack-dev] Status of Docker CI

We have a Jenkins server and slave configuration that has been tested and integrated into upstream OpenStack CI. We do not yet trigger on rechecks due to limitations of the Gerrit Jenkins trigger plugin. However, Arista has published a patch for this that we may be able to test. Reporting into

Re: [openstack-dev] [Neutron] Flavor Framework

On Thu, 2014-02-27 at 02:11 +0400, Eugene Nikanorov wrote: > Hi neutron folks, > > I know that there are patches on gerrit for VPN, FWaaS and L3 services > that are leveraging Provider Framework. > Recently we've been discussing more comprehensive approach that will > allow user to choose service

Re: [openstack-dev] Status of Docker CI

Thanks for the update. On 02/27/2014 05:18 PM, Eric Windisch wrote: > We have a Jenkins server and slave configuration that has been tested > and integrated into upstream OpenStack CI. We do not yet trigger on > rechecks due to limitations of the Gerrit Jenkins trigger plugin. > However, Arista

  1   2   >