Hi,
I've served on the TC for a while now and enjoyed it. However, I feel
I've reached a point where I need to step back and take a break. I
will therefore not be running this time around. I'm sure I'll return
just as soon as my righteous anger builds up again.
Cheers,
Michael
--
Rackspace Aust
On 4/23/15 1:16 PM, Dan Smith wrote:
If I selected all the instance_type_id's from the system-metadata table
and used those uuid's to load the object with something like:
instance = objects.Instance.get_by_uuid(
context, instance_uuid,
expected_attrs=['system_me
I would like to announce my candidacy for the OpenStack Technical Committee
Many of you many not know me, because I am not a very active contributor.
First a bit about myself. I am a Platform Architect working for Cisco in
Israel and have been involved with OpenStack for the past two years. I
Hello Folks,
Just a kind reminder! I would like to invite all available contributors to help
us to complete the OpenStack Networking Guide.
We are having a Networking Doc Day on April 23rd in order to review the current
guide and make a big push on its content.
We will use the following IRC cha
Thanks a lot John for your response.
I appreciate for your time and effort in answering the queries and also
pointing to the latest changes which you been always doing :)
Thanks and Regards,
Asha Seshagiri
On Wed, Apr 22, 2015 at 6:09 PM, John Wood wrote:
> Hello Asha,
>
> The barbican.sh sc
Announcing my candidacy for the TC.
I would bring an operator's perspective (ie, operator, user, super-user and
dev) to the Technical Committee.
I've been involved in OpenStack for four years. I gave talks at San Diego,
Atlanta, Paris, and soon Vancouver as a contributor, community organizer,
and
> If I selected all the instance_type_id's from the system-metadata table
> and used those uuid's to load the object with something like:
> instance = objects.Instance.get_by_uuid(
> context, instance_uuid,
> expected_attrs=['system_metadata', 'flavor'])
>
> The tes
2015-04-23 6:55 GMT+08:00 Matt Riedemann :
>
>
> On 4/22/2015 8:32 AM, Sylvain Bauza wrote:
>
>> Hi,
>>
>> By discussing on a specific bug [1], I just discovered that the admin
>> context check which was done at the DB level has been moved to the API
>> level thanks to the api-policy-v3 blueprint
>
>
> Could you please also pay some attention on Cons of this ultimate
> splitting Kyle? I'm afraid it would hurt the user experiences.
>
> On the position of Dev, A naked Neutron without "official" built-in
> reference implementation probably has a more clear architecture. On
> the other side, us
>
>
>> Would it make sense to capture these projects as simply 'affiliated', ie.
>> with a loose relationship to Neutron, because they use/integrate with
>> Neutron in some form or another (e.g. having 3rd-party, extending-api,
>> integrating-via-plugin-model, etc)? Then we could simply consider ex
Hi all,
I would like to announce my non-candidacy for the TC this term.
To be clear, I'm not running for a seat on the TC right now, but I hope you
will read this anyway.
Background
=
I ran for a seat on the Technical Committee twelve months ago, on a
platform that consisted of two poin
On Thu, Apr 23, 2015 at 3:30 AM, Kyle Mestery wrote:
> On Wed, Apr 22, 2015 at 1:19 PM, Russell Bryant wrote:
>>
>> Hello!
>>
>> A couple of things I've been working on lately are project governance
>> issues as a TC member and also implementation of a new virtual
>> networking alternative with a
On 04/22/2015 09:46 PM, Kyle Mestery wrote:
> On Wed, Apr 22, 2015 at 7:44 PM, Armando M. wrote:
>
>>
>>
>> On 22 April 2015 at 11:19, Russell Bryant wrote:
>>
>>> Hello!
>>>
>>> A couple of things I've been working on lately are project governance
>>> issues as a TC member and also implementati
All-
I'd like to announce my candidacy to continue serving on the Technical
Committee.
Platform
—
OpenStack is a growing community comprised of many parts and we we must view
ourselves as one unit. As a TC member, I will continue to place the interests
of the larger community over those o
On 4/23/15 1:31 AM, Dan Smith wrote:
Sure, but for people doing continuous deployment, they clearly haven't
ran the migrate_flavor_data (or if they have, they haven't filed any
bugs about it not working[0]).
Hence the usefulness of T-H here, right? The point of the migration
check is to make su
On Wed, Apr 22, 2015 at 7:44 PM, Armando M. wrote:
>
>
> On 22 April 2015 at 11:19, Russell Bryant wrote:
>
>> Hello!
>>
>> A couple of things I've been working on lately are project governance
>> issues as a TC member and also implementation of a new virtual
>> networking alternative with a Neu
Hi everyone!
I'd like to announce my own candidacy for the OpenStack Technical
Committee. My TL/DR platform is: "Represent Front-End Engineering". It's
what I do, it's what I love, it's what I've been doing for the last 15
years, and it's what I want to keep doing for years to come.
Would you lik
Hi Victoria,
Count me in also. I'll go ahead and subscribe myself to the mailing list as
well.
From: Victoria Martínez de la Cruz
To: "OpenStack Development Mailing List (not for usage questions)"
Date: 04/22/2015 06:10 PM
Subject:Re: [openstack-dev] [Horizon] Out
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, April 23rd at 17:00 UTC in the #openstack-meeting channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to a
Hi David,
Thanks a lot for your quick response! I'll give you more details about the
applicant in a follow up email or in IRC.
Certainly having separate wikis is not practical sometimes, so Stefano has
been working on centralize all the information wrt internships and
mentoring opportunities in O
confirmed
On Wed, Apr 22, 2015 at 5:56 PM, David Lyle wrote:
> I'm announcing my candidacy for the Technical Committee elections.
>
> I have been contributing to OpenStack since Grizzly primarily in Horizon. I
> have also had the privilege to serve as Horizon PTL since Icehouse.
>
> Why I'm runn
> That is correct -- these are icehouse datasets which have been
> upgraded, but never had an juno run against them. It would be hard for
> turbo hipster to do anything else, as it doesn't actually run a cloud.
> We can explore ideas around how to run live upgrade code, but its
> probably a project
I'm announcing my candidacy for the Technical Committee elections.
I have been contributing to OpenStack since Grizzly primarily in Horizon. I
have also had the privilege to serve as Horizon PTL since Icehouse.
Why I'm running:
I believe there should be broader representation on the TC. We are g
I added my name to an openstack wiki page for this express purpose some
time ago, apparently the wrong one, which I can find no reference to now.
That said, I am willing to be a mentor for a Horizon focused intern, if
inability to find the correct wiki pages isn't a limiting factor.
David
On Wed
On 22 April 2015 at 11:19, Russell Bryant wrote:
> Hello!
>
> A couple of things I've been working on lately are project governance
> issues as a TC member and also implementation of a new virtual
> networking alternative with a Neutron driver. So, naturally I started
> thinking about how the Ne
On Thu, Apr 23, 2015 at 1:31 AM, Dan Smith wrote:
>> Sure, but for people doing continuous deployment, they clearly haven't
>> ran the migrate_flavor_data (or if they have, they haven't filed any
>> bugs about it not working[0]).
>
> Hence the usefulness of T-H here, right? The point of the migrat
Hi all,
Horizon folks, we have a really good Outreachy candidate interested in
working with you. The internship is from May 25th to August 25th, and
interns are expected to work full time on their projects. Being a mentor
should not be time consuming, we expect interns to be able to do their
tasks
confirmed
On Wed, Apr 22, 2015 at 4:17 PM, Maru Newby wrote:
> My name is Maru Newby, and I am announcing my candidacy for the
> Technical Committee (TC) election.
>
> tl;dr;
>
> I'm a relative unknown outside of Neutron, but I've been helping to drive
> high-level change in that project. I woul
confirmed
On Wed, Apr 22, 2015 at 5:05 PM, Sergey Lukjanov wrote:
> Hi folks,
>
> I'd like to announce my candidacy for the TC elections.
>
> Here is a list of the main directions I would like to concentrate on as a TC
> member:
>
> * Continue to grow the OpenStack long-term vision and inclusive
+1 for the idea though not sure on priority of this since we have so many
way more important things to implement in Kilo. I'd say that would be a
great contribution if we find someone willing to contribute it :)
Sincerely yours,
Stan Lagun
Principal Software Engineer @ Mirantis
On Thu, Apr 23,
Hi folks,
I’d like to announce my candidacy for the TC elections.
Here is a list of the main directions I would like to concentrate on as a
TC member:
* Continue to grow the OpenStack long-term vision and inclusive approach
that comes with "The Big Tent". We should not just be more inclusive, bu
On 22 April 2015 at 06:02, Miguel Angel Ajo Pelayo
wrote:
>
> Hi everybody,
>
>In the latest QoS meeting, one of the topics was a discussion about how
> to implement
> QoS [1] either as in core, or as a service plugin, in, or out-tree.
>
My apologies if I was unable to join, the meeting clas
My name is Maru Newby, and I am announcing my candidacy for the
Technical Committee (TC) election.
tl;dr;
I'm a relative unknown outside of Neutron, but I've been helping to drive
high-level change in that project. I would welcome the opportunity to bring my
energy and dedication to OpenStack-wid
Hello Asha,
The barbican.sh script was originally intended to be a convenient way to boot
up a Barbican instance locally to quickly start evaluating its API and
functionality.
It was not intended to be used as a production script, deferring instead to
deployments utilizing packages such as RDO
On Wednesday, April 22, 2015, Matt Riedemann
wrote:
>
>
> On 4/22/2015 8:32 AM, Sylvain Bauza wrote:
>
>> Hi,
>>
>> By discussing on a specific bug [1], I just discovered that the admin
>> context check which was done at the DB level has been moved to the API
>> level thanks to the api-policy-v3
On 4/22/2015 8:32 AM, Sylvain Bauza wrote:
Hi,
By discussing on a specific bug [1], I just discovered that the admin
context check which was done at the DB level has been moved to the API
level thanks to the api-policy-v3 blueprint [2]
That behaviour still leads to a bug if the operator wants
Since python-openstackclient is now a part of openstack — I guess it would be a
good idea to support it in murano. It has setuptools-based plugin system, and
it should be fairly easy to add murano commands as plugins to it.
BTW, It’s based on cliff and has a terrific completion support (which is
On 04/22/2015 04:33 PM, Kyle Mestery wrote:
On Wed, Apr 22, 2015 at 3:28 PM, Sean M. Collins mailto:s...@coreitpro.com>> wrote:
Hi,
Kyle Mestery has asked me to serve as a cross-project liaison between
Neutron and Nova. So, I'd like to say hello, and
direct everyone towards an e
Excerpts from Salvatore Orlando's message of 2015-04-22 23:10:01 +0200:
> On 22 April 2015 at 14:49, Doug Hellmann wrote:
>
> > Excerpts from Ihar Hrachyshka's message of 2015-04-22 12:33:52 +0200:
> > > On 04/22/2015 05:01 AM, Doug Hellmann wrote:
> > > > Excerpts from Ihar Hrachyshka's message
Hi All,
I would like to know the reason behind the dependency of the pyenv virtual
environment and pyenv in the barbican.sh script.
Ideally in the production environment , barbican would run on standalone
virtual box with a particular python version .I feel that their dependecies
needs to be remo
I prefer option a) as well. It does seem like most of the projects would
really see no change at all other than being officially sanctioned as an
Openstack project with some kind of tag. There's also the possibility the PTL
may request some changes to improve the bigger picture of the
Networki
confirmed
On Wed, Apr 22, 2015 at 1:13 PM, Armando M. wrote:
> I would like to announce my candidacy for the OpenStack Technical Committee.
>
> I will try to be brief and to the point: I have been involved in OpenStack
> since the early days of the Austin release; I have worked on (perhaps) the
On 22 April 2015 at 14:49, Doug Hellmann wrote:
> Excerpts from Ihar Hrachyshka's message of 2015-04-22 12:33:52 +0200:
> > On 04/22/2015 05:01 AM, Doug Hellmann wrote:
> > > Excerpts from Ihar Hrachyshka's message of 2015-04-17 14:45:58
> > > +0200:
> > >> Hi,
> > >>
> > >> tl;dr neutron has spe
+1 to both.
From: Ben Swartzlander [mailto:b...@swartzlander.org]
Sent: Wednesday, April 22, 2015 2:23 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Manila] Two nominations for Manila Core Reviewer Team
I would like to nominate Thomas Bechtold to jo
The python-glanceclient release management team is pleased to announce:
Release of python-glanceclient version 0.17.1
Please find the details related to the release at:
https://launchpad.net/python-glanceclient/+milestone/0.17.1
Please report the issues through launchpad:
https:/
On Wed, Apr 22, 2015 at 3:28 PM, Sean M. Collins wrote:
> Hi,
>
> Kyle Mestery has asked me to serve as a cross-project liaison between
> Neutron and Nova. So, I'd like to say hello, and
> direct everyone towards an etherpad that I have created.
>
> https://etherpad.openstack.org/p/nova-neutron
>
On Wed, Apr 22, 2015 at 11:49 PM, Sean Dague wrote:
> On 04/22/2015 07:07 AM, Sean Dague wrote:
> > On 04/22/2015 04:09 AM, Angus Salkeld wrote:
> >> Hi
> >>
> >> Can we please have a new release of novaclient (after the below fix)?
> >>
> >> Heat's unit tests pass fine with:
> >> python-novaclie
Hi,
Kyle Mestery has asked me to serve as a cross-project liaison between
Neutron and Nova. So, I'd like to say hello, and
direct everyone towards an etherpad that I have created.
https://etherpad.openstack.org/p/nova-neutron
The etherpad can serve as a way to collect items that should be
discu
I would like to announce my candidacy for the OpenStack Technical Committee.
I will try to be brief and to the point: I have been involved in OpenStack
since the early days of the Austin release; I have worked on (perhaps) the
two most prolific projects in OpenStack (Nova, and Neutron) and a few
o
On 04/22/2015 10:51 AM, Emilien Macchi wrote:
Hi,
Some important work is being done on Keystone v3 API support in
puppet-keystone.
We've clearly seen there is a lack of review and I think we all worry
about breaking something.
Spencer & I are working on beaker tests lately and the jobs are
non-v
+1
I was in the middle of writing an email asking about the possibility of
splitting out the reference implementation. you beat me to it. :)
I also like the idea of having the PTL on top to help pass up/down ideas where
code can be shared, benefiting everyone.
Thanks,
Kevin
___
On Wed, Apr 22, 2015 at 1:19 PM, Russell Bryant wrote:
> Hello!
>
> A couple of things I've been working on lately are project governance
> issues as a TC member and also implementation of a new virtual
> networking alternative with a Neutron driver. So, naturally I started
> thinking about how
Hello, Manila-philes.
Back in Paris we started talking about Manila mount automation, whereby file
shares could be automatically mounted on clients, and this will likely be a
topic in Vancouver. So in order to have an informed discussion at the summit,
I'd like to explore a few things beforeha
Hello everyone,
Swift was last to RC1, but they are first in the RC2 race :) Due to
release-critical issues spotted in RC1 testing, a new release candidate
was created for Kilo. The 2.3.0 RC2 tarball is available for download at:
https://launchpad.net/swift/kilo/2.3.0-rc2
Unless release-critical
On Wed, Apr 22, 2015 at 02:03:13PM -0400, Emilien Macchi wrote:
>
>
> On 04/22/2015 11:53 AM, Spencer Krum wrote:
> > Emillen,
> >
> > Do you see shelling out to openstackclient in the keystone test to
> > verify that the keystone resources have been created? Do you see trying
> > to hit the api
Hi All,
We have 3 API Guidelines that are ready for a final review.
1. Metadata guidelines document
https://review.openstack.org/#/c/141229/
2. Tagging guidelines
https://review.openstack.org/#/c/155620/
3. Guidelines on using date and time format
https://review.openstack.org/#/c/159892/
If th
On Wed, Apr 22, 2015 at 3:15 AM, Victor Stinner wrote:
> Hi,
>
> It's moving fast. I'm currently working on porting remaining libraries to
> prepare my spec for nova.
>
Great, I did't realize how close all the dependencies were.
>
> > oslo.db -- looks like it is almost there
>
> I don't know t
On Apr 16, 2015 3:58 PM, "Geoff Arnold" wrote:
>
> Joe: you have identified many of the challenges of trying to work with
multiple OpenStack clouds from different providers with different
configurations, resources, etc. Nevertheless, people are doing it, and
doing so successfully. (I know several
confirmed
On Wed, Apr 22, 2015 at 11:19 AM, Zane Bitter wrote:
> Hello Stackists,
> I'd like to announce my candidacy for the OpenStack Technical Committee.
>
> I'm running because I don't think that the diversity of perspectives amongst
> TC members reflects the diversity of our community. We'r
Hi everyone!
In Kilo we made some very nice progress with adopting AngularJS in
Horizon. The launch instance workflow is available as a beta level feature
that can be optionally enabled now in Kilo [1]. Together with the identity
panel, detail pages, and magic search workstreams we were able to
en
+1
Clinton Knight
From: Ben Swartzlander mailto:b...@swartzlander.org>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, April 22, 2015 at 2:23 PM
To: "OpenStack Development Mailing List (not for usage questions)
On Wed, 2015-04-22 at 08:49 -0400, Doug Hellmann wrote:
> That feature sounds like it could be useful outside of neutron, so let's
> see if we can come up with a new syntax to make it portable. Bonus
> points if the new syntax results in a proper DSL.
I have been thinking that I should point peopl
I would like to nominate Thomas Bechtold to join the Manila core
reviewer team. Thomas has been contributing to Manila for close to 6
months and has provided a good number of quality code reviews in
addition to a substantial amount of contributions. Thomas brings both
Oslo experience as well as
I intend to introduce a requirement for 3rd party CI for Manila during
the Liberty release. This shouldn't be a surprise to anyone because I've
been talking about it, but in case anyone didn't hear about it, now you
have.
I expect that by the Liberty release date, every driver in the tree
sho
Hello!
A couple of things I've been working on lately are project governance
issues as a TC member and also implementation of a new virtual
networking alternative with a Neutron driver. So, naturally I started
thinking about how the Neutron driver code fits in to OpenStack governance.
There are
Hello Stackists,
I'd like to announce my candidacy for the OpenStack Technical Committee.
I'm running because I don't think that the diversity of perspectives
amongst TC members reflects the diversity of our community. We're
fortunate to have a few people whose brilliance often transcends the
On 04/22/2015 11:53 AM, Spencer Krum wrote:
> Emillen,
>
> Do you see shelling out to openstackclient in the keystone test to
> verify that the keystone resources have been created? Do you see trying
> to hit the api from something like aviator? Ultimately I'd like to see
> us spin up an entire
At first glance it seems like you're trying to run these tests with a
neutron repo which is not up to date.
Recently Neutron unit tests were reorganized [1]. Have you tried pulling
again from git the neutron repo?
Salvatore
[1] https://review.openstack.org/#/c/158811/
On 22 April 2015 at 19:38,
Hi,
We had some issues with tox lately,
The fix was removing ~/.pip and some other packages from this folder that were
used as cache for pip
And reinstalling devstack.
Lenny Verkhovsky
From: Shane McGough [mailto:smcgo...@kemptechnologies.com]
Sent: Wednesday, April 22, 2015 1:30 PM
To: OpenSt
confirmed
On Wed, Apr 22, 2015 at 5:24 AM, Ed Leafe wrote:
> Greetings Stackers!
>
> I'm announcing my candidacy for the Technical Comitee Elections.
>
> Those of you who have been around OpenStack for a while know me, as I was one
> of the original developers involved since the inception of Op
confirmed
On Wed, Apr 22, 2015 at 9:43 AM, Dean Troyer wrote:
> Hello OpenStack world! My name is Dean Troyer and I am running for the
> OpenStack Technical Committee.
>
> I have been part of the OpenStack community for a long time and heavily
> involved in three projects: I was an early contrib
confirmed
On Wed, Apr 22, 2015 at 9:46 AM, Anita Kuno wrote:
> Please consider my candidacy for membership on the technical committee.
>
> My name is Anita Kuno. I consider my home project to be Infra but I tend
> to move around wherever I feel the need is greatest.
>
> I have worked on OpenStac
Please consider my candidacy for membership on the technical committee.
My name is Anita Kuno. I consider my home project to be Infra but I tend
to move around wherever I feel the need is greatest.
I have worked on OpenStack since mid-grizzly starting as an intern with
the GNOME Outreach Program
Hello OpenStack world! My name is Dean Troyer and I am running for the
OpenStack Technical Committee.
I have been part of the OpenStack community for a long time and heavily
involved in three projects: I was an early contributor to DevStack and
served as its PTL during its short tenure as a stand-
And for another recent one that came out yesterday:
Interesting to read for those who are using mongodb + openstack...
https://aphyr.com/posts/322-call-me-maybe-mongodb-stale-reads
-Josh
Joshua Harlow wrote:
Joshua Harlow wrote:
Kevin Benton wrote:
>Timestamps are just one way (and likely t
Emillen,
Do you see shelling out to openstackclient in the keystone test to verify
that the keystone resources have been created? Do you see trying to hit the
api from something like aviator? Ultimately I'd like to see us spin up an
entire openstack in one test then hit it with tempest.
It may be
> Sure, but for people doing continuous deployment, they clearly haven't
> ran the migrate_flavor_data (or if they have, they haven't filed any
> bugs about it not working[0]).
Hence the usefulness of T-H here, right? The point of the migration
check is to make sure that people _do_ run it before
Congratulations Phil!
Thank you for your work so far.
-Sam.
-Original Message-
From: Doug Wiegley [mailto:doug...@parksidesoftware.com]
Sent: Tuesday, April 21, 2015 7:55 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron][lbaas] add
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/22/2015 05:02 PM, INADA Naoki wrote:
>
> Hi, All,
>
> My 2c are:
>
> - yes, oslo.db supports python 3 (unittests passes, at least :) ) -
> MySQL-python still default MySQL DB driver in OpenStack, but at
> the moment the only DB driver for My
David,
1. It will either lead to people doing things to game the system or overuse
> of the #no-coverage-check tag you mentioned.
Job doesn't force people to increase coverage, it just checks that it was
not decreased.
Btw according to the latest refactoring, we are using absolute values
miss
> Hi, All,
>
> My 2c are:
>
> - yes, oslo.db supports python 3 (unittests passes, at least :) )
> - MySQL-python still default MySQL DB driver in OpenStack, but at the
> moment the only DB driver for MySQL in python3 environment is PyMySQL, so I
> think, it's ok to use it with python 3.
>
>
>
Hi.
Hi,
Some important work is being done on Keystone v3 API support in
puppet-keystone.
We've clearly seen there is a lack of review and I think we all worry
about breaking something.
Spencer & I are working on beaker tests lately and the jobs are
non-voting for now.
I propose:
* to review (and even
may be not quite - please advice how it works in these cases
1) if break-on expression contains the reference to task result, like
break-on: <% $.my_task.foo.bar = true %>
but action returns ERROR and task payload is None (desired behavior: don’t
puke, evaluate to false and don’t break)
2) if
On 4/22/15 7:19 AM, Victor Sergeyev wrote:
Hi, All,
My 2c are:
- yes, oslo.db supports python 3 (unittests passes, at least :) )
- MySQL-python still default MySQL DB driver in OpenStack, but at the
moment the only DB driver for MySQL in python3 environment is PyMySQL,
so I think, it's ok t
(sorry for cross-post, but this is appropriate to both audiences)
Hey y'all!
For those of you that don't know, StackTach is a notification-based debugging,
monitoring and usage tool for OpenStack.
We're happy to announce that we've recently rolled StackTach.v3 into production
at one of the Rax
Hi,
Puppet OpenStack is now part of the big tent [1] and we would like to
move our repositories from Stackforge to OpenStack namespace.
How we are going to proceed
* Patch project-config: https://review.openstack.org/#/c/176326/ (WIP
for now)
* Github: Repositories will be t
On Sat, Apr 18, 2015 at 9:30 PM, Boris Pavlovic wrote:
> Code coverage is one of the very important metric of overall code quality
> especially in case of Python. It's quite important to ensure that code is
> covered fully with well written unit tests.
>
> One of the nice thing is coverage job.
>
On Wed, 2015-04-22 at 12:36 +, Chen, Ken wrote:
> o more complex workflows (job dependencies, DAGs, etc. Do we rely on
> Oozie, or something else?
> >> Huichun is now figuring this. I am not whether you guys already have
> some detail ideas about this? If needed we can contribute some
So, in this case I guess 'break-on' will work correctly now:
https://github.com/stackforge/mistral/blob/master/mistral/engine/policies.py#L295-L296
On Wed, Apr 22, 2015 at 2:58 PM, Renat Akhmerov
wrote:
> Lingxian, yes, that’s basically what I suggest too.
>
> Renat Akhmerov
> @ Mirantis Inc.
>
On 4/22/15 1:20 AM, Dan Smith wrote:
The migrate_flavor_data command didn't actually work on the CLI (unless
I'm missing something or did something odd). See
https://review.openstack.org/#/c/175890/ where I fix the requirement of
max_number. This likely means that operators have not bothered to d
On 04/22/2015 07:07 AM, Sean Dague wrote:
> On 04/22/2015 04:09 AM, Angus Salkeld wrote:
>> Hi
>>
>> Can we please have a new release of novaclient (after the below fix)?
>>
>> Heat's unit tests pass fine with:
>> python-novaclient (2.23.0)
>>
>> but python-novaclient 2.24.0 introduces this bug:
>>
Hi Ken,
responses inline
On Wed, 2015-04-22 at 12:36 +, Chen, Ken wrote:
> Hi Trevor,
> I saw below items in Proposed Sprint Topics of sahara liberty.
> https://etherpad.openstack.org/p/sahara-liberty-proposed-sessions. I
> guess these are the EDP ideas we want to discuss on Vancouver desi
Hi,
By discussing on a specific bug [1], I just discovered that the admin
context check which was done at the DB level has been moved to the API
level thanks to the api-policy-v3 blueprint [2]
That behaviour still leads to a bug if the operator wants to change an
endpoint policy by leaving i
Hi everybody,
In the latest QoS meeting, one of the topics was a discussion about how to
implement
QoS [1] either as in core, or as a service plugin, in, or out-tree.
It’s my feeling, and Mathieu’s that it looks more like a core feature, as
we’re talking of
port properties that we define
Excerpts from Ihar Hrachyshka's message of 2015-04-22 12:33:52 +0200:
> On 04/22/2015 05:01 AM, Doug Hellmann wrote:
> > Excerpts from Ihar Hrachyshka's message of 2015-04-17 14:45:58
> > +0200:
> >> Hi,
> >>
> >> tl;dr neutron has special semantics for policy targets that
> >> relies on private s
Thierry Carrez wrote:
> Ben Swartzlander wrote:
>> My main request was that the Manila sessions didn't overlap with the
>> Cinder sessions, since there are some key people who are involved in
>> both projects. It looks like some attempt was made to avoid overlaps
>> (the fishbowl sessions at least)
Hi Trevor,
I saw below items in Proposed Sprint Topics of sahara liberty.
https://etherpad.openstack.org/p/sahara-liberty-proposed-sessions. I guess
these are the EDP ideas we want to discuss on Vancouver design summit. We have
some comments as below:
• EDP Priorities in Liberty - At the
Greetings Stackers!
I'm announcing my candidacy for the Technical Comitee Elections.
Those of you who have been around OpenStack for a while know me, as I was one
of the original developers involved since the inception of OpenStack back in
2010, when I worked for Rackspace's Cloud Server team.
confirmed
On 04/22/2015 05:26 AM, Julien Danjou wrote:
> Hey fellow developers,
>
> I'd like to announce my candidacy for the Technical Committee election
> that's happening.
>
>
> TL;DR: Vote for me to bring back the fun and raise the bar! :)
>
>
> As you might know, I've been a member of th
confirmed
On 04/22/2015 03:52 AM, James E. Blair wrote:
> Hi,
>
> I'd like to announce my candidacy for re-election to the TC.
>
> About Me
>
>
> I am the PTL for the OpenStack Infrastructure Program, which I have
> been helping to build for nearly four years. I have also served on
>
1 - 100 of 125 matches
Mail list logo
