Re: [openstack-dev] [mistral][yaql] Addressing task result using YAQL function

Yes meant to ask for consistency of referencing to task results. So it’s task(task_name) regardless of where. One use case in favor of this is tooling: I refactor workflow with an automated tool which wants to automatically rename the task name EVERYWHERE. You guys know well by now that

[openstack-dev] [security][bandit] Looking to the future

Hey Bandit Folks, Thanks for all the great work done during the recent security mid cycle, we have made some really solid progress on key areas like documentation, testing, and code quality. It was also great to see people in person! This email follows on from various conversations with the

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

On Fri, Sep 4, 2015 at 8:04 AM, Monty Taylor wrote: > mordred@camelot:~$ neutron net-create test-net-mt > Policy doesn't allow create_network to be performed. > > Thank you neutron. Excellent job. > > Here's what that looks like at the REST layer: > > DEBUG:

[openstack-dev] [nova-scheduler] Scheduler sub-group meeting - Cancel for 9/8?

It belatedly occurred to me that it's a US holiday this week (Labor Day) so most of us will gone so we should probably cancel the meeting this week. The IRC channel will be there but many of us won't. -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786

Re: [openstack-dev] [Neutron] Port forwarding

Hi, Gal Thank you for bringing this up. But I have some suggestions for the API. An operator or some other component wants to reach several VMs related NOT only one or one by one. Here, RELATED means that the VMs are in one subnet or network or a host(similar to reaching dockers on a host). Via

[openstack-dev] [oslo] Oslo meeting - Cancel for Sept 7th, 2015

Team, Just realized that 9/8 is a holiday for some of us. Let's meet again the next week. Thanks, Dims -- Davanum Srinivas :: https://twitter.com/dims __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [magnum]keystone version

Keystone v2 will soon be deprecated. It makes sense for Magnum to use v3. -- Adrian On Sep 5, 2015, at 6:57 PM, ?? > wrote: any comments on this? On Fri, Sep 4, 2015 at 9:43 AM, ??

Re: [openstack-dev] [Congress] bugs for liberty release

I have taken two, thanks. https://bugs.launchpad.net/congress/+bug/1492308 https://bugs.launchpad.net/congress/+bug/1492354 BR Zhou Zhenzan From: Tim Hinrichs [mailto:t...@styra.com] Sent: Friday, September 4, 2015 23:40 To: OpenStack Development Mailing List (not for usage questions) Subject:

Re: [openstack-dev] [magnum]keystone version

any comments on this? On Fri, Sep 4, 2015 at 9:43 AM, 王华 wrote: > Hi all, > > Now the keystoneclient in magnum only support keystone v3. Is is necessary > to support keystone v2? Keystone v2 don't support trust. > > Regards, > Wanghua >

[openstack-dev] OpenStack support for Amazon Concepts - was Re: cloud-init IPv6 support

On Fri, Sep 04, 2015 at 04:20:23PM EDT, Kevin Benton wrote: > Right, it depends on your perspective of who 'owns' the API. Is it > cloud-init or EC2? > > At this point I would argue that cloud-init is in control because it would > be a large undertaking to switch all of the AMI's on Amazon to

Re: [openstack-dev] 9/4 state of the gate

On Fri, Sep 4, 2015 at 6:43 PM, Matt Riedemann wrote: > > > On 9/4/2015 3:13 PM, Matt Riedemann wrote: > >> There are a few things blowing up in the last 24 hours so might as well >> make people aware. >> >> 1. gate-tempest-dsvm-large-ops was failing at a decent rate:

Re: [openstack-dev] [Neutron] Port forwarding

Hi Germy, I am not sure i understand what you mean, can you please explain it further? Thanks Gal. On Sun, Sep 6, 2015 at 5:39 AM, Germy Lure wrote: > Hi, Gal > > Thank you for bringing this up. But I have some suggestions for the API. > > An operator or some other

Re: [openstack-dev] [keystone] FFE Request for Reseller

I suspect we'll vote on this topic during the next meeting on Tuesday, but this seems like a huge amount of code to land. Thanks, Steve Martinelli OpenStack Keystone Core From: Henrique Truta To: "OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [magnum]keystone version

+1, we're trying to deprecate the v2 API as soon as is sanely possible. Plus, there's no reason to not use v3 since you can achieve everything you could in v2, plus more goodness. Thanks, Steve Martinelli OpenStack Keystone Core From: Adrian Otto To:

Re: [openstack-dev] [nova][i18n] Is there any point in using _() inpython-novaclient?

Isn't this just a matter of setting up novaclient for translation? IIRC using _() is harmless if there's no translation bits set up for the project. Thanks, Steve Martinelli OpenStack Keystone Core From: Matt Riedemann To: "OpenStack Development Mailing

Re: [openstack-dev] [Glance] Feature Freeze Exception proposal

Thank you Nikhil and Glance team on the FFE consideration. We are committed to making the revisions per suggestion and separately seek help from the Flavio, Sabari, and Harsh. Regards Malini, Kent, and Jakub -Original Message- From: Nikhil Komawar [mailto:nik.koma...@gmail.com] Sent: