Re: [openstack-dev] [savanna] floating ip pool by name

Andrew, This change was needed to heat engine. In case when heat engine and neutron env are used Heat stacks fails with ‘Bad network UUID error’. This happen because neutron client can’t work with networks by names. So checking network IDs at the validation stage prevents from stack fails and c

[openstack-dev] [Heat] Thoughts on adding a '--progress' option?

The creation a stack is usually a time costly process, considering that there are cases where software packages need to be installed and configured. There are also cases where a stack consists of more than one VM instance and the dependency between instances. The instances may have to be created

Re: [openstack-dev] [horizon] Use unminified javascript files patch needs review

On 02/28/2014 03:10 PM, Thomas Goirand wrote: > On 02/28/2014 01:18 PM, Thomas Goirand wrote: >> Hi, >> >> It's been now more than 40 days that this patch needs review: >> https://review.openstack.org/#/c/67096/ >> >> Could some core reviewers have a look, and eventually approve the patch? >> It's

Re: [openstack-dev] [horizon] Use unminified javascript files patch needs review

On 02/28/2014 01:18 PM, Thomas Goirand wrote: > Hi, > > It's been now more than 40 days that this patch needs review: > https://review.openstack.org/#/c/67096/ > > Could some core reviewers have a look, and eventually approve the patch? > It's very important to me, since Horizon is currently cons

[openstack-dev] [Nova] Question about concurrent access of multiple API server

According to this bug https://bugs.launchpad.net/nova/+bug/1268569 I am wondering someone can help me in understanding the concurrent access prevention on api layer? if we have more than 1 nova-api server, let's say 2(thread A and thread B) ,so both of them should be able to handle request from

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

Hi Jay, Thanks for looking into this. > 1) I'm not entirely sure that a provider attribute is even necessary to > expose in any API. What is important is for a scheduler to know which > drivers are capable of servicing a set of attributes that are grouped > into a "flavor". > Well, provider beco

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

Hi, Are you going to file new blueprint or log a bug in Launchpad to encounter this change. Thanks, Abhishek -Original Message- From: Nikola Đipanov [mailto:ndipa...@redhat.com] Sent: Thursday, February 27, 2014 4:17 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev

[openstack-dev] Need unique ID for every Network Service

Hi- In the existing Neutron, we have FWaaS, LBaaS, VPNaaS ...etc. In FWaaS, each Firewall has its own UUID. It is good to have a unique ID [UUID] for LBaaS also. Please share your comments on the above. Regards, Srikanth. ___ OpenStack-dev mailing list

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

On 02/27/2014 06:00 PM, Alex Xu wrote: Does mean our code looks like as below? if client_version > 2: elif client_version > 3 ... elif client_version > 4: ... elif client_version > 5: ... elif client_version > 6: .. And we need test each version... That looks bad... I d

[openstack-dev] [horizon] Use unminified javascript files patch needs review

Hi, It's been now more than 40 days that this patch needs review: https://review.openstack.org/#/c/67096/ Could some core reviewers have a look, and eventually approve the patch? It's very important to me, since Horizon is currently considered non-free in Debian, due to the minified javascript fi

[openstack-dev] [nova][neutron][keystone] getting keystone endpoints

Hi, Dan Smith and I have been working on the integration between nova and neutron to have neutron issue callbacks into nova to trigger certain events. One of the things I'm trying to figure out is how to support multiple nova regions with this kind of interaction since neutron would now needs to k

Re: [openstack-dev] [nova] pci device hotplug

On 2014年02月22日 07:52, yunhong jiang wrote: On Mon, 2014-02-17 at 06:43 +, Gouzongmei wrote: Hello, In current PCI passthrough implementation, a pci device is only allowed to be assigned to a instance while the instance is being created, it is not allowed to be assigned or removed from

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

Ok, thanks guys! https://blueprints.launchpad.net/mistral/+spec/mistral-rename-event-to-trigger Renat Akhmerov @ Mirantis Inc. On 28 Feb 2014, at 07:41, Dmitri Zimine wrote: > Agree on both. > > > On Feb 26, 2014, at 8:51 PM, Renat Akhmerov wrote: > >> Hi team, >> >> When I tell people

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

You’re welcome! Please let us know if you need more info. Renat Akhmerov @ Mirantis Inc. On 28 Feb 2014, at 09:48, Liuji (Jeremy) wrote: > Hi, > > Yes. I mean the feature like VMware Distributed Resource Scheduler. > Now I am totally clear about the question. Thanks for your explanations. >

Re: [openstack-dev] [Neutron][LBaaS] Enterprise Ready Features

On Wed, 2014-02-26 at 18:46 +, Brandon Logan wrote: > TL;DR: Are enterprise needed features (HA, scalability, resource > management, etc) on this project's roadmap. Yes. Although, due to my disdain for the term "enterprise", I'd point out that all of those features are things that most everyon

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

Hi, Yes. I mean the feature like VMware Distributed Resource Scheduler. Now I am totally clear about the question. Thanks for your explanations. Thanks, Jeremy Liu > -Original Message- > From: Renat Akhmerov [mailto:rakhme...@mirantis.com] > Sent: Thursday, February 27, 2014 5:03 PM > To

Re: [openstack-dev] [Neutron] tox run forever

Hi, Clark: Thanks a lot for the prompt response! I added the OS_TEST_TIMEOUT value (300 sec) and was tailing the tmp file. It turned out that the TOX run stopped at the following point. My machine was tossed so badly that it became unresponsive and I had to hard reboot it….I am pulling my teeth

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

Hi, Randy: Try this command to install pyudev library…. sudo pip install pyudev Let me know whether it works or not. Good luck! Shixiong Shixiong Shang !--- Stay Hungry, Stay Foolish ---! On Feb 27, 2014, at 9:09 PM, Randy Tuttle wrote: > Clark/Sean/Shixiong... > > I have the same err

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

Clark/Sean/Shixiong... I have the same error, and tried to import neutron.tests.unit.linuxbridge.test_lb_neutron_agent (no error4 prefix). I get the following (py27)rantuttl-mac:bin rtuttle$ python Python 2.7.5 (v2.7.5:ab05e7dd2788, May 13 2013, 13:18:45) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3

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

On Thu, 2014-02-27 at 17:23 -0800, Joe Gordon wrote: > On Thu, Feb 27, 2014 at 5:05 PM, Jay Pipes wrote: > > On Thu, 2014-02-27 at 15:12 -0800, Joe Gordon wrote: > >> On Thu, Feb 27, 2014 at 2:37 PM, Jay Pipes wrote: > >> > On Thu, 2014-02-27 at 02:11 +0400, Eugene Nikanorov wrote: > >> >> Hi neu

Re: [openstack-dev] [Neutron] tox run forever

On Thu, Feb 27, 2014 at 4:43 PM, Shixiong Shang wrote: > Hi, guys: > > I created a fresh local repository and pulled the most recent Neutron code. > Before I put in my own code, I did TOX run. However, seems like it is stuck > to the following condition for over a hour and didn't go any further.

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

On Thu, Feb 27, 2014 at 5:05 PM, Jay Pipes wrote: > On Thu, 2014-02-27 at 15:12 -0800, Joe Gordon wrote: >> On Thu, Feb 27, 2014 at 2:37 PM, Jay Pipes wrote: >> > On Thu, 2014-02-27 at 02:11 +0400, Eugene Nikanorov wrote: >> >> Hi neutron folks, >> >> >> >> I know that there are patches on gerrit

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

On Fri, 2014-02-28 at 00:30 +0100, Monty Taylor wrote: > Sorry for the top post. I was asked to look at this thread and toss in > my €0.02 but I do not believe I could possibly read this whole thread - > I'm too jet lagged. So... > > As a current large-scale production consumer of the API, I don

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

On Thu, 2014-02-27 at 17:02 -0500, Adam Young wrote: > On 02/27/2014 12:52 PM, 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

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

On Thu, 2014-02-27 at 15:12 -0800, Joe Gordon wrote: > On Thu, Feb 27, 2014 at 2:37 PM, Jay Pipes wrote: > > 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 P

[openstack-dev] [Neutron][IPv6] tox run forever

In case you have filter set up on your mail client…….. Begin forwarded message: > From: Shixiong Shang > Subject: [openstack-dev] [Neutron] tox run forever > Date: February 27, 2014 at 7:43:03 PM EST > To: "OpenStack Development Mailing List (not for usage questions)" > > > Hi, guys: > > I

[openstack-dev] [Neutron] tox run forever

Hi, guys: I created a fresh local repository and pulled the most recent Neutron code. Before I put in my own code, I did TOX run. However, seems like it is stuck to the following condition for over a hour and didn’t go any further. Yesterday, the TOX had been running with a fresh copy of Neutro

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

Agree on both. On 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 start workflows. For example, take a > look at the following snippet: > > Workflow: > ..

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

+1 I'd rather have good and supported clients that satisfy peoples needs rather than nit-pick or remove v3 or something else... Forward progress is good so I'll throw my hat for v3, but I doubt many people that use the API's care (as long as their friendly client library still works). Make it di

[openstack-dev] [savanna] floating ip pool by name

Hi Team, I was always using <"floating_ip_pool": "net04_ext"> construction and it worked fine. Now it responds with validation error "Floating IP pool net04_ext for node group 'manager' not found" because https://bugs.launchpad.net/savanna/+bug/1282027 was merged and savanna expects only ID here.

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

On 2014?02?28? 00:05, 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 extension /v6: added

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

Sorry for the top post. I was asked to look at this thread and toss in my €0.02 but I do not believe I could possibly read this whole thread - I'm too jet lagged. So... As a current large-scale production consumer of the API, I don't care at all as long as python-novaclient keeps working at th

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

On Thu, Feb 27, 2014 at 2:37 PM, Jay Pipes wrote: > 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 compreh

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

On 02/27/2014 12:52 PM, 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 NOT a safe assumption to

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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

[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

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.

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

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

  1   2   >