Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

Hi folks, my comments inlined: On Thu, Mar 20, 2014 at 6:13 AM, Youcef Laribi wrote: > Jorge, > > > > Thanks for taking the time to put up a requirements list. Some comments > below: > >- Static IP Addresses > - Our current Cloud Load Balancing (CLB) offering utilizes static > I

[openstack-dev] [nova] Nova API meeting

Hi, Just a reminder that the weekly Nova API meeting is being held tomorrow Friday UTC . We encourage cloud operators and those who use the REST API such as SDK developers and others who and are interested in the future of the API to participate. In other timezones the meeting is at: EST

Re: [openstack-dev] [openstack][Mistral] Adding new core reviewers

Thanks, guys! Done. On 20 Mar 2014, at 02:28, Timur Nurlygayanov wrote: > Also, in the future, we can join Kirill Izotov to the core team too. Absolutely, once in a while we’ll be reviewing everyone’s progress and update the core team. ___ OpenStack

Re: [openstack-dev] [Nova][Heat] How to reliably detect VM failures?

On Wed, Mar 19, 2014 at 01:04:55PM +, WICKES, ROGER wrote: > > On 03/18/2014 07:54 AM, Qiming Teng wrote: > >> Hi, Folks, > >> > >>I have been trying to implement a HACluster resource type in Heat. I > >> haven't created a BluePrint for this because I am not sure everything > >> will work a

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

Ianal, but I know there are some lawyers out there who are concerned that the mechanism of attachment is vague. If there is an issue (I'm not saying there is) I don't think mongodb's view is relevant, as they are quite likely to be bought by someone, say Oracle, who might not share and would not

Re: [openstack-dev] [Nova][Heat] How to reliably detect VM failures?

On 03/19/2014 08:38 PM, Qiming Teng wrote: I don't think it a good idea to rely on some external monitoring systems to do a VM failure detection. It means additional steps to set up, additional software to upgrade, additional chapter in the Operator's Guide, etc. We are evaluating whether Ceilo

Re: [openstack-dev] [Nova][Heat] How to reliably detect VM failures?

On Wed, Mar 19, 2014 at 12:08:30PM -0400, Zane Bitter wrote: > On 19/03/14 02:07, Chris Friesen wrote: > >On 03/18/2014 11:18 AM, Zane Bitter wrote: > >>On 18/03/14 12:42, Steven Dake wrote: > > > >>>You should be able to use the HARestarter resource and functionality to > >>>do healthchecking of a

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

Jorge, Thanks for taking the time to put up a requirements list. Some comments below: * Static IP Addresses * Our current Cloud Load Balancing (CLB) offering utilizes static IP addresses which is something our customers really like, especially when setting up DNS. AWS for example, gi

Re: [openstack-dev] Updating libvirt in gate jobs

Excerpts from Joe Gordon's message of 2014-03-18 17:15:59 -0700: > On Tue, Mar 18, 2014 at 8:12 AM, Sean Dague wrote: > > > On 03/18/2014 10:11 AM, Daniel P. Berrange wrote: > > > On Tue, Mar 18, 2014 at 07:50:15AM -0400, Davanum Srinivas wrote: > > >> Hi Team, > > >> > > >> We have 2 choices > >

Re: [openstack-dev] [openstack][Mistral] Adding new core reviewers

Sure, +1 for both. -- Kirill Izotov четверг, 20 марта 2014 г. в 3:52, Dmitri Zimine написал: > +1 for Nikolay - he's indeed the most involved in all aspect. > and yes I am up to doing it. > > DZ. > > On Mar 19, 2014, at 4:35 AM, Renat Akhmerov (mailto:rakhme...@mirantis.com)> wrote:

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

Proxying from yahoo's open source director (since he wasn't initially subscribed to this list, afaik he now is) on his behalf. >From Gil Yehuda (Yahoo’s Open Source director). I would urge you to avoid creating a dependency between Openstack code and any AGPL project, including MongoDB. MongoDB

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On Wed, Mar 19, 2014 at 12:37 PM, Devananda van der Veen < devananda@gmail.com> wrote: > Let me start by saying that I want there to be a constructive discussion > around all this. I've done my best to keep my tone as non-snarky as I could > while still clearly stating my concerns. I've also s

[openstack-dev] [nova] Backwards incompatible API changes

Hi, So it turns out that we have made a backwards incompatible change to the V2 API in Icehouse. Previously when creating a private flavor access was not automatically given to the tenant, now it is. The documentation has always said that it was, but we lied. https://review.openstack.org/#/c/408

Re: [openstack-dev] [TripleO] Alternating meeting time for more TZ friendliness

I think we need a timezone to cover the current impossible regions: - Australia - China / Japan - India Early evening for the UK - the current meeting time - is ok (sure, its not work hours, but its also not 5am :)) The further west it goes, the better for those regions. I suspect if we aim i

Re: [openstack-dev] [Neutron][LBaaS] Mini-summit Interest?

If a mini-summit is held (no matter when), I'll try to make it in person. Failing that, if a google hangout is set up, I ought to be able to attend that way. (And... it's good to be back, eh!) Stephen On Thu, Mar 13, 2014 at 2:17 PM, Edgar Magana wrote: > That sounds like a good idea Mark! >

Re: [openstack-dev] [TripleO] Alternating meeting time for more TZ friendliness

On 19/03/14 06:57, James Slagle wrote: > Our current meeting time is Tuesdays at 19:00 UTC. I think this works > ok for most folks in and around North America. > > It was proposed during today's meeting to see if there is interest is > an alternating meeting time every other week so that we can b

Re: [openstack-dev] [Congress] Policy types

I went ahead and made an editing pass over our design doc to reflect the changes described below. (I moved most of the old content into the final section focused on future work.) Overall, I'd say it simplifies the story and implementation considerably. We can always revert if anyone has serio

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

On 03/19/2014 06:09 PM, Doug Hellmann wrote: > The ceilometer collector is meant to scale horizontally. Have you tried > configuring the test environment to run more than one copy, to process > the notifications more quickly? The ceilometer collector is already one of the top running processes on

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

On Wed, Mar 19, 2014 at 3:09 PM, Doug Hellmann wrote: > The ceilometer collector is meant to scale horizontally. Have you tried > configuring the test environment to run more than one copy, to process the > notifications more quickly? > FYI: http://logs.openstack.org/82/79182/1/check/check-tempes

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-19 22:38 GMT+01:00 Fox, Kevin M : > Its my understanding that the only case the A in the AGPL would kick in is > if the cloud provider made a change to MongoDB and exposed the MongoDB > instance to users. Then the users would have to be able to download the > changed code. Since Marconi's

Re: [openstack-dev] Pecan Evaluation for Marconi

On Mar 19, 2014, at 12:27 PM, Julien Danjou wrote: > On Wed, Mar 19 2014, Kurt Griffiths wrote: > >> That begs the question, *why* is that unlikely to change? > > Because that project is Swift. If you look at the Swift code, you'll see that swob is not a replacement for either Pecan or Falcon

[openstack-dev] [QA] Meeting Thursday March 20th at 22:00UTC

Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, March 20th at 22: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 add an item to

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

The ceilometer collector is meant to scale horizontally. Have you tried configuring the test environment to run more than one copy, to process the notifications more quickly? Doug On Tue, Mar 18, 2014 at 8:09 AM, Nadya Privalova wrote: > Hi folks, > > I'd like to discuss Ceilometer's tempest si

Re: [openstack-dev] [Ceilometer][QA][Tempest][Infra] Ceilometer tempest testing in gate

On Wed, Mar 19, 2014 at 1:52 AM, Nadya Privalova wrote: > Ok, so we don't want to switch to UCA, let's consider this variant. > What options do we have to make possible to run Ceilometer jobs with Mongo > backend? > I see only https://review.openstack.org/#/c/81001/ or making Ceilometer > able to

Re: [openstack-dev] Updating libvirt in gate jobs

On Wed, Mar 19, 2014 at 3:43 AM, Sean Dague wrote: > On 03/18/2014 08:15 PM, Joe Gordon wrote: > > > > > > > > On Tue, Mar 18, 2014 at 8:12 AM, Sean Dague > > wrote: > > > > On 03/18/2014 10:11 AM, Daniel P. Berrange wrote: > > > On Tue, Mar 18, 2014 at 07:50:15AM

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

On Wed, Mar 19, 2014 at 9:25 AM, Miguel Angel Ajo wrote: > > > An advance on the changes that it's requiring to have a > py->c++ compiled rootwrap as a mitigation POC for havana/icehouse. > > https://github.com/mangelajo/shedskin.rootwrap/commit/ > e4167a6491dfbc71e2d0f6e28ba93bc8a1dd66c0 > > The

Re: [openstack-dev] [TripleO] Alternating meeting time for more TZ friendliness

On Thu, Mar 20, 2014 at 7:00 AM, James Polley wrote: > > > On 20 Mar 2014, at 5:44 am, Clint Byrum wrote: > > Excerpts from Sullivan, Jon Paul's message of 2014-03-19 09:26:44 -0700: > > From: James Slagle [mailto:james.sla...@gmail.com > ] > > Sent: 18 March 2014 19:58 > > Subject: [openstack-

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On 03/19/2014 02:24 PM, Fox, Kevin M wrote: Can someone please give more detail into why MongoDB being AGPL is a problem? The drivers that Marconi uses are Apache2 licensed, MongoDB is separated by the network stack and MongoDB is not exposed to the Marconi users so I don't think the 'A' part of

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

Its my understanding that the only case the A in the AGPL would kick in is if the cloud provider made a change to MongoDB and exposed the MongoDB instance to users. Then the users would have to be able to download the changed code. Since Marconi's in front, the user is Marconi, and wouldn't ever

Re: [openstack-dev] [Murano][Heat] MuranoPL questions?

Ability to hook up to application deployment is indeed a good thing. And it can be done both in HOT and MuranoPL. And Mistral is a good candidate to handle those hooks. But this is not a replacement for MuranoPL but an addition to it. The problem with hooks is that you cannot hoot just into arbitr

Re: [openstack-dev] [Murano][Heat] MuranoPL questions?

Hi, I think notification mechanism proposed in Heat will work fine for integration with external workflows. The approach which uses workflows outside of Heat engine sounds consistent with our current approach in Murano. I am looking into new TOSCA yaml format and I also ask Mirantis management to

Re: [openstack-dev] [Murano][Heat] MuranoPL questions?

On Wed, Mar 19, 2014 at 11:57 PM, Steven Dake wrote: > > > Now because DSL provides not only a way to write sandboxed isolated code > but also a lot of declarations (classes, properties, parameters, > inheritance and contracts) that are mostly not present in Python we don't > need Parameters or

Re: [openstack-dev] [openstack][Mistral] Adding new core reviewers

+1 for Nikolay - he's indeed the most involved in all aspect. and yes I am up to doing it. DZ. On Mar 19, 2014, at 4:35 AM, Renat Akhmerov wrote: > Team, > > So far I’ve been just the only one core member of the team. I started feeling > lonely :) Since the project team and the project itsel

Re: [openstack-dev] Pecan Evaluation for Marconi

On Wed, Mar 19, 2014 at 10:00 AM, Doug Hellmann wrote: > > > > On Wed, Mar 19, 2014 at 7:31 AM, Thierry Carrez wrote: > >> Kurt Griffiths wrote: >> > Kudos to Balaji for working so hard on this. I really appreciate his >> candid feedback on both frameworks. >> >> Indeed, that analysis is very muc

Re: [openstack-dev] [Murano][Heat] MuranoPL questions?

Excerpts from Zane Bitter's message on 19/03/2014 18:18:34: > From: Zane Bitter > To: openstack-dev@lists.openstack.org > Date: 19/03/2014 18:21 > Subject: Re: [openstack-dev] [Murano][Heat] MuranoPL questions? > > On 19/03/14 05:00, Stan Lagun wrote: > > Steven, > > > > Agree with your opinion o

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

Can someone please give more detail into why MongoDB being AGPL is a problem? The drivers that Marconi uses are Apache2 licensed, MongoDB is separated by the network stack and MongoDB is not exposed to the Marconi users so I don't think the 'A' part of the GPL really kicks in at all since the Mo

Re: [openstack-dev] [Murano][Heat] MuranoPL questions?

On 03/19/2014 02:00 AM, Stan Lagun wrote: Steven, Agree with your opinion on HOT expansion. I see that inclusion of imperative workflows and ALM would require major Heat redesign and probably would be impossible without loosing compatibility with previous HOT syntax. It would blur Heat missio

Re: [openstack-dev] [TripleO] Alternating meeting time for more TZ friendliness

> On 20 Mar 2014, at 5:44 am, Clint Byrum wrote: > > Excerpts from Sullivan, Jon Paul's message of 2014-03-19 09:26:44 -0700: >>> From: James Slagle [mailto:james.sla...@gmail.com] >>> Sent: 18 March 2014 19:58 >>> Subject: [openstack-dev] [TripleO] Alternating meeting time for more TZ >>> frie

Re: [openstack-dev] Pecan Evaluation for Marconi

On 03/19/2014 01:47 PM, Mike Perez wrote: > On 03/19/2014 08:20 AM, Doug Hellmann wrote: >> As I understand it, all of the integrated projects have looked at Pecan, >> and are anticipating the transition. Most have no reason to create a new >> API version, and therefore build a new API service to a

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

Let me start by saying that I want there to be a constructive discussion around all this. I've done my best to keep my tone as non-snarky as I could while still clearly stating my concerns. I've also spent a few hours reviewing the current code and docs. Hopefully this contribution will be benefici

Re: [openstack-dev] Pecan Evaluation for Marconi

On Wed, Mar 19 2014, Kurt Griffiths wrote: > That begs the question, *why* is that unlikely to change? Because that project is Swift. -- Julien Danjou // Free Software hacker // http://julien.danjou.info signature.asc Description: PGP signature ___

Re: [openstack-dev] [openstack][Mistral] Adding new core reviewers

+1 from me. Also, in the future, we can join Kirill Izotov to the core team too. On Wed, Mar 19, 2014 at 9:46 PM, Manas Kelshikar wrote: > +1 > > > On Wed, Mar 19, 2014 at 5:33 AM, Stan Lagun wrote: > >> +1 for both >> >> >> On Wed, Mar 19, 2014 at 3:35 PM, Renat Akhmerov >> wrote: >> >>> Team

Re: [openstack-dev] [Solum] Proposed Core Reviewer Changes

Solum Cores, Thanks for your input. The proposed changes have been applied. Thanks, Adrian On Mar 17, 2014, at 10:13 PM, Adrian Otto wrote: > Solum Cores, > > I propose the following changes to the Solum core reviewer team: > > +gokrokve > +julienvey > +devdatta-kulkarni > -kgriffs (inactiv

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On 20 March 2014 01:06, Mark McLoughlin wrote: > I think we need a slight reset on this discussion. The way this email > was phrased gives a strong sense of "Marconi is a dumb idea, it's going > to take a lot to persuade me otherwise". Thanks Mark, thats a great point to make. I don't think Marc

Re: [openstack-dev] Pecan Evaluation for Marconi

On Wed, Mar 19 2014, Donald Stufft wrote: > I’m not sure that “number of dependencies” is a useful metric at all tbh. At > the > very least it’s not a very telling metric in the way it was presented in the > review. […] +1000 Seriously, this in itself just discredits any value in this analysi

Re: [openstack-dev] [TripleO] Alternating meeting time for more TZ friendliness

Excerpts from Sullivan, Jon Paul's message of 2014-03-19 09:26:44 -0700: > > From: James Slagle [mailto:james.sla...@gmail.com] > > Sent: 18 March 2014 19:58 > > Subject: [openstack-dev] [TripleO] Alternating meeting time for more TZ > > friendliness > > > > Our current meeting time is Tuesdays at

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

Oleg, thanks for the updates. Eugene, High/Medium/Low is fine with me. I really just wanted to find a way to rank even amongst all of 'X' priorities. As people start adding more items we may need more columns to add things such as this, links to blueprints (per Ryan's idea), etc. In terms of th

Re: [openstack-dev] Pecan Evaluation for Marconi

> Only one project is using swob, and it is unlikely that will change. That begs the question, *why* is that unlikely to change? Is it because there are fundamental needs that are not met by Pecan? If I understand the original charter for Oslo, it was to consolidate code already in use by projects

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

+1 -Original Message- From: Ryan O'Hara [mailto:roh...@redhat.com] Sent: Wednesday, March 19, 2014 2:37 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki On Tue, Mar 18, 2014 at 10:57:15PM +, Jorge Mira

Re: [openstack-dev] Storing license information in openstack/requirements

I started the following. https://review.openstack.org/#/c/81589 Please feel free to check it out, most of this information we can get from pypi itself via its apis. -Josh From: David Koo mailto:kpublicm...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" ma

Re: [openstack-dev] [Nova][Heat] How to reliably detect VM failures?

On 19/03/14 02:07, Chris Friesen wrote: On 03/18/2014 11:18 AM, Zane Bitter wrote: On 18/03/14 12:42, Steven Dake wrote: You should be able to use the HARestarter resource and functionality to do healthchecking of a vm. HARestarter is actually pretty problematic, both in a "causes major arc

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

An advance on the changes that it's requiring to have a py->c++ compiled rootwrap as a mitigation POC for havana/icehouse. https://github.com/mangelajo/shedskin.rootwrap/commit/e4167a6491dfbc71e2d0f6e28ba93bc8a1dd66c0 The current translation output is included. It looks like doable (almost ki

Re: [openstack-dev] [openstack][Mistral] Adding new core reviewers

+1 On Wed, Mar 19, 2014 at 5:33 AM, Stan Lagun wrote: > +1 for both > > > On Wed, Mar 19, 2014 at 3:35 PM, Renat Akhmerov wrote: > >> Team, >> >> So far I've been just the only one core member of the team. I started >> feeling lonely :) Since the project team and the project itself has now >> g

Re: [openstack-dev] WSGI and Python paste

On 03/19/2014 09:25 PM, victor stinner wrote: > Hi, > > According to the following table, paste is blocking many OpenStack servers to > be ported to Python 3: > >https://wiki.openstack.org/wiki/Python3 I had a look to this, and found it weird that ironicclient is marked as supporting Python

Re: [openstack-dev] Pecan Evaluation for Marconi

On 03/19/2014 08:20 AM, Doug Hellmann wrote: As I understand it, all of the integrated projects have looked at Pecan, and are anticipating the transition. Most have no reason to create a new API version, and therefore build a new API service to avoid introducing incompatibilities by rebuilding th

Re: [openstack-dev] [neutron][policy] Integrating network policies and network services

On Wed, Mar 19, 2014 at 12:23 PM, Louis.Fourie wrote: > Mohammad, > > Agree, the information models for these two proposals are very similar. > > > > It appears that the ODL model offers some additional flexibility in that > direction attributes are > > attached to Classifiers and Directives ra

Re: [openstack-dev] [Murano][Heat] MuranoPL questions?

On 19/03/14 05:00, Stan Lagun wrote: Steven, Agree with your opinion on HOT expansion. I see that inclusion of imperative workflows and ALM would require major Heat redesign and probably would be impossible without loosing compatibility with previous HOT syntax. It would blur Heat mission, confu

Re: [openstack-dev] [neutron][policy] Integrating network policies and network services

Mohammad, Agree, the information models for these two proposals are very similar. It appears that the ODL model offers some additional flexibility in that direction attributes are attached to Classifiers and Directives rather than Policies in the Openstack model. Maybe the authors can comment

Re: [openstack-dev] [Neutron] advanced servicevm framework: meeting time slot proposal 5:00UTC (Tue) and minutes (was Re: [Neutron] advanced servicevm framework IRC meeting March 18(Tuesday) 23:00 UTC

Hi Mohammad, I am sorry to say that the new schedule is indeed 1am EST... - Stephen On Wed, Mar 19, 2014 at 9:04 AM, Mohammad Banikazemi wrote: > Isaku Yamahata wrote on 03/19/2014 04:38:34 AM: > > > From: Isaku Yamahata > > To: OpenStack Development Mailing List < > openstack-dev@lists

[openstack-dev] [php-sdk] Action items from today's meeting

Thanks for the great meeting today. Here are the action items that came out of it: - [Shaunak] Look into mailing list for user support. How do other OpenStack projects do this? - [Shaunak] Make trivial change to repo to learn OpenStack contribution process - [Jamie] Look into PHPSpec vs. PHPUnit

Re: [openstack-dev] [TripleO] Alternating meeting time for more TZ friendliness

> From: James Slagle [mailto:james.sla...@gmail.com] > Sent: 18 March 2014 19:58 > Subject: [openstack-dev] [TripleO] Alternating meeting time for more TZ > friendliness > > Our current meeting time is Tuesdays at 19:00 UTC. I think this works > ok for most folks in and around North America. > >

Re: [openstack-dev] [Neutron] advanced servicevm framework: meeting time slot proposal 5:00UTC (Tue) and minutes (was Re: [Neutron] advanced servicevm framework IRC meeting March 18(Tuesday) 23:00 UTC

Isaku Yamahata wrote on 03/19/2014 04:38:34 AM: > From: Isaku Yamahata > To: OpenStack Development Mailing List , > Cc: isaku.yamah...@gmail.com > Date: 03/19/2014 04:48 AM > Subject: [openstack-dev] [Neutron] advanced servicevm framework: > meeting time slot proposal 5:00UTC (Tue) and minute

Re: [openstack-dev] [Congress] Policy types

Inline. Tim - Original Message - | From: "prabhakar Kudva" | To: "OpenStack Development Mailing List (not for usage questions)" | Sent: Wednesday, March 19, 2014 7:09:24 AM | Subject: Re: [openstack-dev] [Congress] Policy types | | Hi Tim, | | I am good with starting or own the Pyth

Re: [openstack-dev] [Neutron] Docs for new plugins

I opened this bug Edgar: https://bugs.launchpad.net/openstack-manuals/+bug/1294726 On Wed, Mar 19, 2014 at 10:17 AM, Edgar Magana wrote: > Thanks for the input Anne! > > Kyle, > > Please file the proper bugs in the manual projects to be able to track the > progress of this topic. > > Thanks, >

Re: [openstack-dev] Pecan Evaluation for Marconi

On 19/03/14 11:20 -0400, Doug Hellmann wrote: On Wed, Mar 19, 2014 at 10:11 AM, Flavio Percoco wrote: My only concern in this case - I'm not sure if this has been discussed or written somewhere - is to define what the boundaries of that divergence are. For instance, and I know this w

Re: [openstack-dev] [Neutron][OVS Agent]

Thanks Mathieu for your reply and info. On Tue, Mar 18, 2014 at 3:35 AM, Mathieu Rohon wrote: > Hi nader, > > The easiest way would be to register a new RPC callback in the current > ovs agent. This is what we have done for the l2-pop MD, with fdb_add > and fdb_remove callbacks. > However, it co

Re: [openstack-dev] [nova] Getting close to RC1....

Please don't send review requests to the list: http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html Thanks. -Ben On 2014-03-18 22:46, wu jiang wrote: > Hi Tracy, > > I've already updated the patch for bug/1195947 on > https://review.openstack.org/#/c/38073/ [1

Re: [openstack-dev] Pecan Evaluation for Marconi

On Wed, Mar 19, 2014 at 10:11 AM, Flavio Percoco wrote: > On 19/03/14 12:31 +0100, Thierry Carrez wrote: > >> Kurt Griffiths wrote: >> >>> Kudos to Balaji for working so hard on this. I really appreciate his >>> candid feedback on both frameworks. >>> >> >> Indeed, that analysis is very much appr

Re: [openstack-dev] [Neutron] Docs for new plugins

Thanks for the input Anne! Kyle, Please file the proper bugs in the manual projects to be able to track the progress of this topic. Thanks, Edgar From: Anne Gentle Date: Wednesday, March 19, 2014 4:54 AM To: Edgar Magana Cc: OpenStack List Subject: Re: [openstack-dev] [Neutron] Docs fo

Re: [openstack-dev] [Openstack-dev] [Nova] use Keystone V3 token to volume attachment

On Wed, Mar 19, 2014 at 09:35:34AM -0500, Matt Riedemann wrote: > > > On 3/19/2014 2:48 AM, Shao Kai SK Li wrote: > >Hello: > > > > I am working on this > >patch(https://review.openstack.org/#/c/77524/) to fix bugs about volume > >attach failure with keystone V3 token. > > > > Just wond

[openstack-dev] [sahara] Canceling team meeting Mar 20 [savanna]

Hi team, I'm canceling team meeting tomorrow, Mar 20, because there will be no quorum - Mirantis team will be unavailable due to the internal company event, Matt F. said that he'll be unavailable too. Thanks. -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing)

Re: [openstack-dev] [Nova] First time contributing to some project

On Wed, 2014-03-19 at 17:33 +0530, Dharmit Shah wrote: > Hello Stackers, > > This is the first time I am mailing some dev mailing list and first > time I am trying to contribute on some open source project. Welcome, Dharmit, nice to have you in our community! :) > I am working on a low-hanging-f

Re: [openstack-dev] Pecan Evaluation for Marconi

On Wed, Mar 19, 2014 at 7:31 AM, Thierry Carrez wrote: > Kurt Griffiths wrote: > > Kudos to Balaji for working so hard on this. I really appreciate his > candid feedback on both frameworks. > > Indeed, that analysis is very much appreciated. > > From the Technical Committee perspective, we put a h

[openstack-dev] Timeline for upcoming PTL and TC elections

Election season is coming up. In the next weeks we'll renew our PTLs (one for each OpenStack program) and 7 Technical Committee members. The timeline for those elections is as follows: * March 28 - April 4, 05:59 UTC: Open candidacy to PTL positions * April 4 - April 11: PTL elections * April 11

Re: [openstack-dev] [Openstack-dev] [Nova] use Keystone V3 token to volume attachment

On 3/19/2014 2:48 AM, Shao Kai SK Li wrote: Hello: I am working on this patch(https://review.openstack.org/#/c/77524/) to fix bugs about volume attach failure with keystone V3 token. Just wonder, is there some blue prints or plans in Juno to address keystone V3 support in nova ?

Re: [openstack-dev] Pecan Evaluation for Marconi

On Mar 19, 2014, at 10:18 AM, Kurt Griffiths wrote: > Thierry Carrez wrote: > >> There was historically a lot of deviation, but as we add more projects >> that deviation is becoming more costly. > > I totally understand the benefits of reducing the variance between > projects, and to be sure,

Re: [openstack-dev] Pecan Evaluation for Marconi

Thierry Carrez wrote: > There was historically a lot of deviation, but as we add more projects >that deviation is becoming more costly. I totally understand the benefits of reducing the variance between projects, and to be sure, I am not suggesting we have 10 different libraries to do X. However

Re: [openstack-dev] Pecan Evaluation for Marconi

On 19/03/14 12:31 +0100, Thierry Carrez wrote: Kurt Griffiths wrote: Kudos to Balaji for working so hard on this. I really appreciate his candid feedback on both frameworks. Indeed, that analysis is very much appreciated. From the Technical Committee perspective, we put a high weight on a fa

Re: [openstack-dev] WSGI and Python paste

On Wed, 2014-03-19 at 14:25 +0100, victor stinner wrote: > Hi, > > According to the following table, paste is blocking many OpenStack servers to > be ported to Python 3: > >https://wiki.openstack.org/wiki/Python3#Core_OpenStack_projects > > The author of paste, Ian Bicking, gave me the comm

Re: [openstack-dev] [Nova] First time contributing to some project

Hi Dharmit, You can't remove those from Nova. If you remove them, attach volume won't work anymore. Attach volume still goes through Nova. Thanks, Xing -Original Message- From: Dharmit Shah [mailto:dharmit@gmail.com] Sent: Wednesday, March 19, 2014 8:03 AM To: openstack-dev@list

Re: [openstack-dev] Automatic version creation in PBR

On Tue, Mar 18, 2014 at 5:30 PM, Monty Taylor wrote: > On 03/18/2014 04:25 AM, Thierry Carrez wrote: > >> Robert Collins wrote: >> >>> If you set 'version' in setup.cfg, pbr's behaviour will not change at >>> all. >>> >>> If you do not set 'version' in setup.cfg then: >>> - for tagged commits,

Re: [openstack-dev] [magnetodb] Using gevent in MagnetoDB. OpenStack standards and approaches

On Tue, Mar 18, 2014 at 2:51 PM, Dmitriy Ukhlov wrote: > Hello openstackers, > > We are working on MagnetoDB project and trying our best to follow > OpenStack standards. > > So, MagnetoDB is aimed to be high performance scalable OpenStack based > WSGI application which provide interface to high

Re: [openstack-dev] [magnetodb] Using gevent in MagnetoDB. OpenStack standards and approaches

Dmitriy, Gunicorn + gevent + pecan play nicely together, and they’re a combination I’ve used to good success in the past. Pecan even comes with some helpers for integrating with gunicorn: $ gunicorn_pecan pecan_config.py -k gevent -w4 http://pecan.readthedocs.org/en/latest/deployment.html?high

[openstack-dev] WSGI and Python paste

Hi, According to the following table, paste is blocking many OpenStack servers to be ported to Python 3: https://wiki.openstack.org/wiki/Python3#Core_OpenStack_projects The author of paste, Ian Bicking, gave me the commit permission to paste. I integrated patches from Debian and my colleagu

[openstack-dev] [Nova][Heat] How to reliably detect VM failures? (Zane Bitter)

> On 03/18/2014 07:54 AM, Qiming Teng wrote: >> Hi, Folks, >> >>I have been trying to implement a HACluster resource type in Heat. I >> haven't created a BluePrint for this because I am not sure everything >> will work as expected. ... >>The most difficult issue here is to come up with a re

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

Hi Jorge, Thanks for taking care of the page. I've added priorities, although I'm not sure we need precise priority weights. Those features that still have '?' need further clarification. Thanks, Eugene. On Wed, Mar 19, 2014 at 11:18 AM, Oleg Bondarev wrote: > Hi Jorge, > > Thanks for taking

Re: [openstack-dev] [Neutron][LBaaS] Requirements Wiki

On Tue, Mar 18, 2014 at 10:57:15PM +, Jorge Miramontes wrote: > Hey Neutron LBaaS folks, > > Per last week's IRC meeting I have created a preliminary requirements & > use case wiki page. I requested adding such a page since there appears to > be a lot of new interest in load balancing and feel

Re: [openstack-dev] [openstack][Mistral] Adding new core reviewers

+1 for both On Wed, Mar 19, 2014 at 3:35 PM, Renat Akhmerov wrote: > Team, > > So far I've been just the only one core member of the team. I started > feeling lonely :) Since the project team and the project itself has now > grown (thanks to StackStorm and Intel) I think it's time to think about

[openstack-dev] [QA] Bug Day kickoff

Morning QA Team, I hope everybody can help on this effort so we can release icehouse with less bugs as possible. So this morning, March, 19th, 12:00 UTC the current tempest's bug picture is Current picture of Tempest's bugs: * 166 Open Bugs https://bugs.launchpad.net/tempest/+bugs - 17 cl

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On 03/19/2014 07:49 AM, Thierry Carrez wrote: > Flavio Percoco wrote: >> On 19/03/14 10:17 +1300, Robert Collins wrote: >>> My desires around Marconi are: - to make sure the queue we have >>> is suitable for use by OpenStack itself: we have a very strong >>> culture around consolidating technology

[openstack-dev] [Neutron][LBaaS] Subteam meeting Thursday, 14-00 UTC

Hi neutron and lbaas folks, Let's keep our regular meeting on Thursday, at 14-00 UTC at #openstack-meeting Jorge Miramontes has made a nice wiki page capturing service requirements: https://wiki.openstack.org/wiki/Neutron/LBaaS/requirements Please check it out as this will help us to get on the s

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

On Wed, 2014-03-19 at 10:17 +1300, Robert Collins wrote: > So this came up briefly at the tripleo sprint, and since I can't seem > to find a /why/ document > (https://wiki.openstack.org/wiki/Marconi/Incubation#Raised_Questions_.2B_Answers > and https://wiki.openstack.org/wiki/Marconi#Design don't s

Re: [openstack-dev] [Nova][Cinder] Feature about Raw Device Mapping

After second thought, it will be more meaningful to just add virtio-SCSI bus type support to block-device-mapping. RDM can then be used or not, depend on the bus type and device type of bdm specified by user. And user can also just use virtio-SCSI bus for performance other than pass through.

[openstack-dev] [Nova] First time contributing to some project

Hello Stackers, This is the first time I am mailing some dev mailing list and first time I am trying to contribute on some open source project. I am working on a low-hanging-fruit bug (https://bugs.launchpad.net/nova/+bug/1261909). It's about removing hba specific code from nova as cinder manages

Re: [openstack-dev] [Neutron] Docs for new plugins

On Wed, Mar 19, 2014 at 12:45 AM, Edgar Magana wrote: > Including Anne in this thread. > > Anne, > > Can your provide your input here? > > Thanks, > > Edgar > > From: Mohammad Banikazemi > Reply-To: OpenStack List > Date: Monday, March 17, 2014 8:02 AM > To: OpenStack List > > Subject: Re: [op

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

Flavio Percoco wrote: > On 19/03/14 10:17 +1300, Robert Collins wrote: >> My desires around Marconi are: >> - to make sure the queue we have is suitable for use by OpenStack >> itself: we have a very strong culture around consolidating technology >> choices, and it would be extremely odd to have Ma

[openstack-dev] [Nova][SDK] What Nova APIs are used by SDKs

Hi, We need to know what Nova APIs are used by each SDK. Could SDK developers/users/someone write them on the below spreadsheet? https://docs.google.com/spreadsheet/ccc?key=0AvimqlvxcSGGdGxYSVJQb2tic25wUmFkcDJFV25OSUE#gid=2 I have written SDK names on the spreadsheet from https://wiki.open

[openstack-dev] [openstack][Mistral] Adding new core reviewers

Team, So far I’ve been just the only one core member of the team. I started feeling lonely :) Since the project team and the project itself has now grown (thanks to StackStorm and Intel) I think it’s time to think about extending the core team. I would propose: Nikolay Makhotkin (nmakhotkin at

Re: [openstack-dev] Pecan Evaluation for Marconi

Kurt Griffiths wrote: > Kudos to Balaji for working so hard on this. I really appreciate his candid > feedback on both frameworks. Indeed, that analysis is very much appreciated. >From the Technical Committee perspective, we put a high weight on a factor that was not included in the report resul

Re: [openstack-dev] Updating libvirt in gate jobs

On 03/18/2014 08:15 PM, Joe Gordon wrote: > > > > On Tue, Mar 18, 2014 at 8:12 AM, Sean Dague > wrote: > > On 03/18/2014 10:11 AM, Daniel P. Berrange wrote: > > On Tue, Mar 18, 2014 at 07:50:15AM -0400, Davanum Srinivas wrote: > >> Hi Team, > >> > >>

  1   2   >