[openstack-dev] [nova] nova networking API and CLI are poorly documented and buggy

I am not even sure what is the intent, but some of the behavior looks like it is clearly unintended and not useful (i.e., buggy). IMHO, the API and CLI documentation should explain these calls/commands in enough detail that the reader can tell the difference. And the difference should be us

[openstack-dev] [3rd Party] Log retention with 3rd party testing

Hi Stackers- I have a doubt on what is the timeline for log retention. From the discussion (irc), I learnt that time for log retention is ONE month. I have two scenarios to deal with. [1] A change takes two months or more to get merged into the master branch. Here, if CI's, delete the log

Re: [openstack-dev] [nova][qa] Do all turbo-hipster jobs fail in stable/havana?

Hi there, Very sorry for the mishap. I manually enqueued our zuul to run tests on changes that turbo-hipster had recently missed and did not pay attention to the branch they were for. Turbo-Hipster doesn't run tests on stable or non-master branches so it should have never attempted to. Becau

Re: [openstack-dev] [nova][cinder] Refactor ISCSIDriver to support other iSCSI transports besides TCP

Hello, Shlomi. On Tue, Mar 25, 2014 at 7:07 PM, Shlomi Sasson wrote: > > I want to share with the community the following challenge: > > Currently, Vendors who have their iSCSI driver, and want to add RDMA > transport (iSER), cannot leverage their existing plug-in which inherit from > iSCSI > >

Re: [openstack-dev] [Neutron] - Location for common third-party libs?

Right Armando. Brocade’s mech driver problem is due to NETCONF templates - would also prefer to see a common area for such templates – not just common code. Sort of like: common/brocade/templates common/bigswitch/* -Shiv From: "Armando M." mailto:arma...@gmail.com>> Reply-To: "OpenStack Develo

Re: [openstack-dev] [Mistral] Cleaning up configuration settings

I don’t think we have them. You can write them I think as a part of what you’re doing. Renat Akhmerov @ Mirantis Inc. On 31 May 2014, at 04:26, W Chan wrote: > Is there an existing unit test for testing enabling keystone middleware in > pecan (setting cfg.CONF.pecan.auth_enable = True)? I

[openstack-dev] [gantt] scheduler group meeting agenda

1) Forklift (tasks & status) 2) Policy-based scheduler 3) Opens -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailma

Re: [openstack-dev] [Fuel] Bug squashing day on June, 17

Current count: New - 56 Incomplete - 48 Confirmed/Triaged/In progress for 5.1 - 331

[openstack-dev] [barbican] Juno Mid-cycle Meetup

Hi Everyone, Just wanted to send a reminder that the Barbican Juno meetup is coming up in a few weeks. We’ll be meeting at the new Geekdom location in San Antonio, TX on July 7-9 (Monday-Wednesday). This meetup will overlap with the Keystone Juno Hackathon being held July 9-11 at the same locat

[openstack-dev] [nova] tomorrow's PCI passthrough IRC meeting

Hi, I’m taking tomorrow off, and therefore I won’t be present in the IRC meeting. We made a lot of progress last week. We’ve got the first +2 for our spec, and therefore it’s a big step forward toward getting approval. A lot of progress on the coding front as well, and more patches will be comi

Re: [openstack-dev] [qa] Clarification of policy for qa-specs around adding new tests

> -Original Message- > From: Matthew Treinish [mailto:mtrein...@kortar.org] > Sent: Monday, June 16, 2014 11:58 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [qa] Clarification of policy for qa-specs around > adding new tests > > On

[openstack-dev] [nova][qa] Do all turbo-hipster jobs fail in stable/havana?

Hi all, Is turbo-hipster OK for stable/havana? I found all turbo-hipster jobs after 06/09 failed in stable/havana [1]. And the 'recheck migrations' command didn't trigger the re-examination of turbo-hipster, but Jenkins recheck work.. Thanks. WingWJ --- [1] https://review.open

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

Excerpts from Carlos Garza's message of 2014-06-16 16:25:10 -0700: > > On Jun 16, 2014, at 4:06 PM, Clint Byrum wrote: > > > Excerpts from Doug Wiegley's message of 2014-06-16 13:22:26 -0700: > >>> nobody is calling Barbican "a database". It is a place to store > >> > >> Š did you at least feel

Re: [openstack-dev] [Neutron] - Location for common third-party libs?

That could be a possible workaround. In this particular deployment the nodes no longer had access to the Internet though to install additional packages. -- Kevin Benton On Mon, Jun 16, 2014 at 3:59 PM, Armando M. wrote: > I believe the Brocade's mech driver might have the same problem. > > Tha

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

> Look, I'm talking a lot and not showing up with code, so I'm squelching myself. Noted, and ditto. Thanks for the dialog. Doug On 6/16/14, 5:54 PM, "Clint Byrum" wrote: >Excerpts from Doug Wiegley's message of 2014-06-16 16:10:51 -0700: >> Hi Clint, >> >> Comments below. >> >> On 6/16/1

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

Excerpts from Doug Wiegley's message of 2014-06-16 16:10:51 -0700: > Hi Clint, > > Comments below. > > On 6/16/14, 3:06 PM, "Clint Byrum" wrote: > > >Excerpts from Doug Wiegley's message of 2014-06-16 13:22:26 -0700: > >> > nobody is calling Barbican "a database". It is a place to store > >> >

Re: [openstack-dev] revert hacking to 0.8 series

Another idea I had: It appears like a lot of the current hacking issues can be automatically fixed. So it would be really nice if the hacking tool included a fix for most of the problems it finds. I started https://review.openstack.org/#/c/68988/ but don't have the time to do a full tool, but it

Re: [openstack-dev] [nova] Distributed locking

So this is a reader/write lock then? I have seen https://github.com/python-zk/kazoo/pull/141 come up in the kazoo (zookeeper python library) but there was a lack of a maintainer for that 'recipe', perhaps if we really find this needed we can help get that pull request 'sponsored' so that it can be

Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora

On 06/16/2014 06:18 PM, Ryan Brady wrote: > > > - Original Message - >> From: "Gregory Haynes" >> To: "openstack-dev" >> Sent: Monday, June 16, 2014 5:49:25 PM >> Subject: Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora >> Id also like to propose that if we decide ag

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

On Jun 16, 2014, at 4:06 PM, Clint Byrum wrote: > Excerpts from Doug Wiegley's message of 2014-06-16 13:22:26 -0700: >>> nobody is calling Barbican "a database". It is a place to store >> >> Š did you at least feel a heavy sense of irony as you typed those two >> statements? ³It¹s not a databa

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

On Jun 16, 2014, at 3:22 PM, Doug Wiegley wrote: >> nobody is calling Barbican "a database". It is a place to store > > Š did you at least feel a heavy sense of irony as you typed those two > statements? ³It¹s not a database, it just stores things!² :-) > > The real irony here is that in thi

Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora

- Original Message - > From: "Gregory Haynes" > To: "openstack-dev" > Sent: Monday, June 16, 2014 5:49:25 PM > Subject: Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora > > > > Id also like to propose that if we decide against doing this then these > > > elements should n

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

Sorry for responding so late but I don't think we should be doing ref counting at all. In a closed system its hard enough to guarantee they are correct but in an open distributed system I really doubt every service will bother decrementing and incrementing the counters properly. On Jun 16,

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

Hi Clint, Comments below. On 6/16/14, 3:06 PM, "Clint Byrum" wrote: >Excerpts from Doug Wiegley's message of 2014-06-16 13:22:26 -0700: >> > nobody is calling Barbican "a database". It is a place to store >> >> Š did you at least feel a heavy sense of irony as you typed those two >> statements

[openstack-dev] [Fuel][Nova][vmware] Multiple vCenter backends support in Fuel

Hi, All. In next Fuel release we want to implement a support of multiple vCenters under one OpenStack. Practically it means that we need to set up multiple instances of Nova-Compute each connected to its own vCenter. In Fuel 5.0 we already have support of one vCenter, but it's implemented by runnin

Re: [openstack-dev] revert hacking to 0.8 series

On Mon, Jun 16, 2014 at 2:54 PM, Angus Salkeld wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 17/06/14 02:46, Ben Nemec wrote: > > On 06/16/2014 08:37 AM, Thierry Carrez wrote: > >> Sean Dague wrote: > >>> Hacking 0.9 series was released pretty late for Juno. The entire > >>> che

Re: [openstack-dev] [Neutron] - Location for common third-party libs?

This approach would work but my only concern is then getting an external package added as a dependency to Neutron. Or would you just forgo that entirely and mock out all of the library calls? -- Kevin Benton On Mon, Jun 16, 2014 at 3:29 PM, Salvatore Orlando wrote: > I think there's is no suit

Re: [openstack-dev] [Neutron] - Location for common third-party libs?

I believe the Brocade's mech driver might have the same problem. That said, if the content of the rpm that installs the BigSwitch plugin is just the sub-tree for bigswitch (plus the config files, perhaps), you might get away with this issue by just installing the bigswitch-plugin package. I assume

Re: [openstack-dev] revert hacking to 0.8 series

On Mon, Jun 16, 2014 at 2:56 PM, Doug Hellmann wrote: > On Mon, Jun 16, 2014 at 2:23 PM, Joe Gordon wrote: > > > > On Jun 16, 2014 9:44 AM, "Ben Nemec" wrote: > >> > >> -BEGIN PGP SIGNED MESSAGE- > >> Hash: SHA1 > >> > >> On 06/16/2014 08:37 AM, Thierry Carrez wrote: > >> > Sean Dague w

Re: [openstack-dev] [Neutron] - Location for common third-party libs?

Hi, It doesn't make sense to move the Big Switch ML2 driver into the Big Switch Plugin. This isn't how the other ML2 drivers are handled and it doesn't really solve the problem since someone installing the ML2 package couldn't use one of the ML2 drivers. I will report a bug; however, it won't be

Re: [openstack-dev] revert hacking to 0.8 series

On 06/16/2014 05:46 PM, Ben Nemec wrote: > On 06/16/2014 04:46 PM, Joe Gordon wrote: >> On Mon, Jun 16, 2014 at 2:33 PM, Sean Dague wrote: >> >>> On 06/16/2014 05:06 PM, Ben Nemec wrote: On 06/16/2014 12:01 PM, Sean Dague wrote: > On 06/16/2014 12:44 PM, Ben Nemec wrote: >> On 06/16/2

Re: [openstack-dev] revert hacking to 0.8 series

On 06/16/2014 04:46 PM, Joe Gordon wrote: > On Mon, Jun 16, 2014 at 2:33 PM, Sean Dague wrote: > >> On 06/16/2014 05:06 PM, Ben Nemec wrote: >>> On 06/16/2014 12:01 PM, Sean Dague wrote: On 06/16/2014 12:44 PM, Ben Nemec wrote: > On 06/16/2014 08:37 AM, Thierry Carrez wrote: >> Sean

Re: [openstack-dev] [Neutron] - Location for common third-party libs?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 17/06/14 00:10, Anita Kuno wrote: > On 06/16/2014 06:02 PM, Kevin Benton wrote: >> Hello, >> >> In the Big Switch ML2 driver, we rely on quite a bit of code from >> the Big Switch plugin. This works fine for distributions that >> include the enti

Re: [openstack-dev] [Fuel] ML2 support in Fuel deployment risks

Correction/clarification: call tomorrow is about multiple-cluster-networks, and it was a bad idea on my part to try to hijack that with neutron-ml2 discussion. Lets not do that and continue discussing the blueprint spec in gerrit, and hopefully by Thursday Andrew will have enough code out there to

Re: [openstack-dev] [Neutron] - Location for common third-party libs?

I think there's is no suitable place at the moment in the source code tree. "common" and "plugin specific" indeed are semantically a bit at odds too! I am considering moving all "library" code for the vmware plugins outside of the source code tree, into their own package, maintained separately and

Re: [openstack-dev] [Neutron] - Location for common third-party libs?

On 06/16/2014 06:02 PM, Kevin Benton wrote: > Hello, > > In the Big Switch ML2 driver, we rely on quite a bit of code from the Big > Switch plugin. This works fine for distributions that include the entire > neutron code base. However, some break apart the neutron code base into > separate package

Re: [openstack-dev] [Fuel] ML2 support in Fuel deployment risks

Mike, We discussed this in our team syncup meeting earlier today. The agreement was that HA is the biggest risk with the current approach. However, keeping our current state of divergence from upstream (and even exagerrating it further) leaves us with a huge technical debt, so the tradeoff between

[openstack-dev] [Neutron] - Location for common third-party libs?

Hello, In the Big Switch ML2 driver, we rely on quite a bit of code from the Big Switch plugin. This works fine for distributions that include the entire neutron code base. However, some break apart the neutron code base into separate packages. For example, in CentOS I can't use the Big Switch ML2

Re: [openstack-dev] revert hacking to 0.8 series

On Mon, Jun 16, 2014 at 2:23 PM, Joe Gordon wrote: > > On Jun 16, 2014 9:44 AM, "Ben Nemec" wrote: >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 06/16/2014 08:37 AM, Thierry Carrez wrote: >> > Sean Dague wrote: >> >> Hacking 0.9 series was released pretty late for Juno. The enti

Re: [openstack-dev] revert hacking to 0.8 series

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/06/14 02:46, Ben Nemec wrote: > On 06/16/2014 08:37 AM, Thierry Carrez wrote: >> Sean Dague wrote: >>> Hacking 0.9 series was released pretty late for Juno. The entire >>> check queue was flooded this morning with requirements proposals >>> faili

Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora

> > Id also like to propose that if we decide against doing this then these > > elements should not live in tripleo-image-elements. > > I'm not so sure I agree. We have lio and tgt because lio is on RHEL but > everywhere else is still using tgt IIRC. Looks like we do have a cinder-tgt and a cinde

Re: [openstack-dev] revert hacking to 0.8 series

On Mon, Jun 16, 2014 at 2:33 PM, Sean Dague wrote: > On 06/16/2014 05:06 PM, Ben Nemec wrote: > > On 06/16/2014 12:01 PM, Sean Dague wrote: > >> On 06/16/2014 12:44 PM, Ben Nemec wrote: > >>> On 06/16/2014 08:37 AM, Thierry Carrez wrote: > Sean Dague wrote: > > Hacking 0.9 series was rel

Re: [openstack-dev] revert hacking to 0.8 series

On 06/16/2014 05:06 PM, Ben Nemec wrote: > On 06/16/2014 12:01 PM, Sean Dague wrote: >> On 06/16/2014 12:44 PM, Ben Nemec wrote: >>> On 06/16/2014 08:37 AM, Thierry Carrez wrote: Sean Dague wrote: > Hacking 0.9 series was released pretty late for Juno. The > entire check queue was floo

Re: [openstack-dev] [openstack-sdk-php] Use of final and private keywords to limit extending

Before I dig into the meat of my response, something occurred to me that's contextually significant. PHP is a flexible language. There are numerous ways to do the same thing and the language is open enough that those who have differing opinions on style and patterns can implement projects their wa

Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora

Excerpts from Gregory Haynes's message of 2014-06-16 14:04:19 -0700: > Excerpts from Jan Provazník's message of 2014-06-16 20:28:29 +: > > Hi, > > MariaDB is now included in Fedora repositories, this makes it easier to > > install and more stable option for Fedora installations. Currently > >

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

Excerpts from Doug Wiegley's message of 2014-06-16 13:22:26 -0700: > > nobody is calling Barbican "a database". It is a place to store > > Š did you at least feel a heavy sense of irony as you typed those two > statements? ³It¹s not a database, it just stores things!² :-) > Not at all, though

Re: [openstack-dev] revert hacking to 0.8 series

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/16/2014 12:01 PM, Sean Dague wrote: > On 06/16/2014 12:44 PM, Ben Nemec wrote: >> On 06/16/2014 08:37 AM, Thierry Carrez wrote: >>> Sean Dague wrote: Hacking 0.9 series was released pretty late for Juno. The entire check queue was flood

Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora

Excerpts from Jan Provazník's message of 2014-06-16 20:28:29 +: > Hi, > MariaDB is now included in Fedora repositories, this makes it easier to > install and more stable option for Fedora installations. Currently > MariaDB can be used by including mariadb (use mariadb.org pkgs) or > mariadb-

Re: [openstack-dev] [nova] locked instances and snaphot

On Tue, Jun 17, 2014 at 5:28 AM, melanie witt wrote: > Hi all, > > Recently a nova bug [1] was opened where the user describes a scenario where > an instance that is locked is still able to be snapshotted (create image and > backup). In the case of Trove, instances are locked "...to ensure integ

Re: [openstack-dev] [Cinder] Mid-cycle meetup for Cinder devs

On 06/16/2014 04:16 PM, D'Angelo, Scott wrote: > The HP site is available Aug 11 -15th. I’m getting some help from our admin > to book the room. Some questions she had and my tentative answers: > > • Is wireless ok? # Wireless should be fine, everyone will be using > laptops > > •

Re: [openstack-dev] [Cinder] Mid-cycle meetup for Cinder devs

On Mon, Jun 16, 2014 at 2:16 PM, D'Angelo, Scott wrote: > The HP site is available Aug 11 -15th. I’m getting some help from our > admin to book the room. Some questions she had and my tentative answers: > > · Is wireless ok? # Wireless should be fine, everyone will be > using laptops >

Re: [openstack-dev] [Neutron] [FWaaS] [sequritygroup] [Development]

Inline... ~Sumit. On Sun, Jun 15, 2014 at 9:25 AM, Salvatore Orlando wrote: > Hi Israel, > > please find my answers inline. > I'm not really an expert in this area, but I hope these answers are helpful, > and, hopefully, correct! > > Salvatore > > > On 15 June 2014 14:55, Israel Ziv wrote: >> >

[openstack-dev] [TripleO] Use MariaDB by default on Fedora

Hi, MariaDB is now included in Fedora repositories, this makes it easier to install and more stable option for Fedora installations. Currently MariaDB can be used by including mariadb (use mariadb.org pkgs) or mariadb-rdo (use redhat RDO pkgs) element when building an image. What do you think

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

> nobody is calling Barbican "a database". It is a place to store Š did you at least feel a heavy sense of irony as you typed those two statements? ³It¹s not a database, it just stores things!² :-) The real irony here is that in this rather firm stand of keeping the user in control of their sec

Re: [openstack-dev] [oslo][messaging] messaging vs. messagingv2

Hi Ihar, On Mon, 2014-06-16 at 15:28 +0200, Ihar Hrachyshka wrote: > Hi all, > > I'm currently pushing Neutron to oslo.messaging, and while at it, a > question popped up. > > So in oslo-rpc, we have the following notification drivers available: > neutron.openstack.common.notifier.log_notifier >

Re: [openstack-dev] [Cinder] Mid-cycle meetup for Cinder devs

The HP site is available Aug 11 -15th. I’m getting some help from our admin to book the room. Some questions she had and my tentative answers: • Is wireless ok? # Wireless should be fine, everyone will be using laptops • Do you need a speaker phone and projector? # Projector

Re: [openstack-dev] [Nova] Review guidelines for API patches

On Fri, Jun 13, 2014 at 4:18 AM, Christopher Yeoh wrote: > Hi Phil, > > On Fri, 13 Jun 2014 09:28:30 + > "Day, Phil" wrote: > > > > >The documentation is NOT the canonical source for the behaviour of > > >the API, currently the code should be seen as the reference. We've > > >run into issues

Re: [openstack-dev] [Nova] Nominating Ken'ichi Ohmichi for nova-core

On Sat, 2014-06-14 at 08:40 +1000, Michael Still wrote: > Greetings, > > I would like to nominate Ken'ichi Ohmichi for the nova-core team. > > Ken'ichi has been involved with nova for a long time now. His reviews > on API changes are excellent, and he's been part of the team that has > driven th

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

On Mon, Jun 16, 2014 at 12:19 PM, Tomas Sedovic wrote: > All, > > After having proposed some changes[1][2] to tripleo-heat-templates[3], > reviewers suggested adding a deprecation period for the merge.py script. > > While TripleO is an official OpenStack program, none of the projects > under its u

Re: [openstack-dev] [NFV] Specific example NFV use case for a data plane app

- Original Message - > From: "Calum Loudon" > To: "OpenStack Development Mailing List (not for usage questions)" > > > Hello all > > At Wednesday's meeting I promised to supply specific examples to help > illustrate the NFV use cases and also show how they map to some of the > blueprin

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

Excerpts from Doug Wiegley's message of 2014-06-10 14:41:29 -0700: > Of what use is a database that randomly delete rows? That is, in effect, > what you’re allowing. > > The secrets are only useful when paired with a service. And unless I’m > mistaken, there’s no undo. So you’re letting users

Re: [openstack-dev] [nova][ceilometer] FloatingIp pollster spamming n-api logs (bug 1328694)

On Sat, Jun 14, 2014 at 7:33 AM, Eoghan Glynn wrote: > > > - Original Message - > > On 11 June 2014 20:07, Joe Gordon wrote: > > > On Wed, Jun 11, 2014 at 11:38 AM, Matt Riedemann > > > wrote: > > >> On 6/11/2014 10:01 AM, Eoghan Glynn wrote: > > >>> Thanks for bringing this to the list

Re: [openstack-dev] [Cinder] Mid-cycle meetup for Cinder devs

On Thu, Jun 12, 2014 at 3:58 PM, John Griffith wrote: > > > > On Wed, Jun 11, 2014 at 3:16 PM, D'Angelo, Scott > wrote: > >> During the June 11 #openstack-cinder meeting we discussed a mid-cycle >> meetup. The agenda is To be Determined. >> >> I have inquired and HP in Fort Collins, CO has room

[openstack-dev] [nova] locked instances and snaphot

Hi all, Recently a nova bug [1] was opened where the user describes a scenario where an instance that is locked is still able to be snapshotted (create image and backup). In the case of Trove, instances are locked "...to ensure integrity and protect secrets which are needed by the resident Trov

Re: [openstack-dev] [metrics] How to group activity in git/gerrit repositories

Let me explain how Stackalytics grouping works. Most of groups are created from the official programs .yaml. Every program turns into item in the module list (colored in violet), for example 'Nova Compute' is a group containing 'nova', 'python-novaclient' and 'nova-specs'. E

Re: [openstack-dev] [nova] Do any hyperviors allow disk reduction as part of resize ?

This is a fix in flight for the vmware driver. It also throws an exception on disk size reduction. https://review.openstack.org/#/c/85804/ On Jun 13, 2014, at 3:02 AM, "Day, Phil" wrote: > Hi Folks, > > I was looking at the resize code in libvirt, and it has checks which raise an > exce

[openstack-dev] [nova][vmwareapi] Spawn Refactor progress

Our phase 1 of spawn refactor merged a week or 2 ago and we are hard at work on phase 2 and 3. The patch set has been posted. Here is the list in order to review for your convenience not a refactor by a trivial fix to clean up some code before the refactor https://review.openstack.org/#/c/9923

Re: [openstack-dev] [Horizon] [UX] Design for Alarming and Alarm Management

> On Jun 16, 2014, at 10:56 AM, Eoghan Glynn wrote: > > > > > Apologies for the top-posting, but just wanted to call out some > > potential confusion that arose on the #os-ceilometer channel earlier > > today. > > > > TL;DR: the UI shouldn't assume a 1:1 mapping between alarms and > > r

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On Jun 14, 2014 11:12 AM, "Robert Collins" wrote: > > You know its bad when you can't sleep because you're redesigning gate > workflows in your head so I apologise that this email is perhaps > not as rational, nor as organised, as usual - but , . :) > > Obviously this is very important to

Re: [openstack-dev] [Neutron][LBaaS] Barbican Neutron LBaaS Integration Ideas

I would like to see something more sophisticated than a simple counter (it's so easy for a counter to get off when dealing with non-atomic asynchronous commands). But a counter is a good place to start. On Jun 13, 2014 6:54 AM, "Jain, Vivek" wrote: > +2. I totally agree with your comments Doug.

Re: [openstack-dev] [Horizon] [UX] Design for Alarming and Alarm Management

On Jun 16, 2014, at 10:56 AM, Eoghan Glynn wrote: > > Apologies for the top-posting, but just wanted to call out some > potential confusion that arose on the #os-ceilometer channel earlier > today. > > TL;DR: the UI shouldn't assume a 1:1 mapping between alarms and > resources, since thi

Re: [openstack-dev] [Trove] Heat integration

On 16/06/14 13:56, Nikhil Manchanda wrote: Denis Makogon writes: Because Trove should not do what it does now (cloud service orchestration is not the part of the OS Database Program). Trove should delegate all tasks to Cloud Orchestration Service (Heat). Agreed that Trove should delegate pro

Re: [openstack-dev] Rethink how we manage projects? (was Gate proposal - drop Postgresql configurations in the gate)

On 06/16/2014 03:33 AM, Thierry Carrez wrote: David Kranz wrote: [...] There is a different way to do this. We could adopt the same methodology we have now around gating, but applied to each project on its own branch. These project branches would be integrated into master at some frequency or wh

Re: [openstack-dev] revert hacking to 0.8 series

On Jun 16, 2014 10:02 AM, "Sean Dague" wrote: > > On 06/16/2014 12:44 PM, Ben Nemec wrote: > > On 06/16/2014 08:37 AM, Thierry Carrez wrote: > >> Sean Dague wrote: > >>> Hacking 0.9 series was released pretty late for Juno. The entire > >>> check queue was flooded this morning with requirements pr

Re: [openstack-dev] revert hacking to 0.8 series

On Jun 16, 2014 9:44 AM, "Ben Nemec" wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 06/16/2014 08:37 AM, Thierry Carrez wrote: > > Sean Dague wrote: > >> Hacking 0.9 series was released pretty late for Juno. The entire > >> check queue was flooded this morning with requirements

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

Excerpts from Duncan Thomas's message of 2014-06-16 10:46:12 -0700: > Hi Clint > > This looks like a special pleading here - all OpenStack projects (or > 'program' if you prefer - I'm honestly not seeing a difference) have > bits that they've written quickly and would rather not have to > maintain

Re: [openstack-dev] how to install fuel on a esxi vm

Hi, Wang. Could you provide a network topology of your installation (incliding hardware and virtual L2/L3 parts of it)? Also, please, check this instruction http://vbyron.com/blog/deploy-openstack-on-vsphere-with-fuel/ On Thu, Jun 12, 2014 at 8:20 AM, Wang Liming wrote: > hi all: > I install

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On 16 Jun 2014 22:33, "Sean Dague" wrote: > > On 06/16/2014 04:33 AM, Thierry Carrez wrote: > > Robert Collins wrote: > >> [...] > >> C - If we can't make it harder to get races in, perhaps we can make it > >> easier to get races out. We have pretty solid emergent statistics from > >> every gate j

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On Mon, Jun 16, 2014 at 11:38 AM, Joe Gordon wrote: > > > > On Sat, Jun 14, 2014 at 3:46 AM, Sean Dague wrote: >> >> On 06/13/2014 06:47 PM, Joe Gordon wrote: >> > >> > >> > >> > On Thu, Jun 12, 2014 at 7:18 PM, Dan Prince > > > wrote: >> > >> > On Thu, 2014-06-12 a

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On 16 Jun 2014 20:33, "Thierry Carrez" wrote: > > Robert Collins wrote: > > [...] > > C - If we can't make it harder to get races in, perhaps we can make it > > easier to get races out. We have pretty solid emergent statistics from > > every gate job that is run as check. What if set a policy that

Re: [openstack-dev] [Fuel] Using saltstack as orchestrator for fuel

Mistral doesn't have to be married to RabbitMQ, there's a ZeroMQ driver in oslo.messaging, so in theory Mistral should be able to make use of that. On Mon, Jun 16, 2014 at 1:42 AM, Vladimir Kozhukalov wrote: > Guys, > > First of all we need to agree about what orchestration is. In terms of Fuel >

Re: [openstack-dev] [metrics] How to group activity in git/gerrit repositories

On Fri 13 Jun 2014 10:51:24 AM PDT, Stangel, Dan wrote: > You can also refer to the example of Stackalytics, who have created > their own hierarchy and groupings for metrics reporting: > https://github.com/stackforge/stackalytics/blob/master/etc/default_data.json It's a very neat grouping. It seem

Re: [openstack-dev] [Trove] Heat integration

Denis Makogon writes: > Good day, Stackers, Trove community. > > > I'd like to start thread related to orchestration based resource > management. At current state Heat support in Trove is nothing else than > experimental. Trove should be able to fully support Trove as resource > management driver

Re: [openstack-dev] revert hacking to 0.8 series

This sounds totally reasonable. +1 to keeping style-specific changes consistent across a release. — Morgan Fainberg From: Clint Byrum cl...@fewbar.com Reply: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: June 16, 2014 at 10:51:31 To: openst

Re: [openstack-dev] revert hacking to 0.8 series

Excerpts from Sean Dague's message of 2014-06-16 05:15:54 -0700: > Hacking 0.9 series was released pretty late for Juno. The entire check > queue was flooded this morning with requirements proposals failing pep8 > because of it (so at 6am EST we were waiting 1.5 hrs for a check node). > > The prev

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

Hi Clint This looks like a special pleading here - all OpenStack projects (or 'program' if you prefer - I'm honestly not seeing a difference) have bits that they've written quickly and would rather not have to maintain, but in order to allow people to make use of them downstream have to do that wo

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On Thu, 2014-06-12 at 11:36 -0400, Sean Dague wrote: > If someone can point me to a case where we've actually found this kind > of bug with tempest / devstack, that would be great. I've just *never* > seen it. I was the one that did most of the fixing for pg support in > Nova, and have helped other

[openstack-dev] [Manila] GenericDriver cinder volume error during manila create

I am trying devstack on F20 setup with Manila sources. When i am trying to do *manila create --name cinder_vol_share_using_nfs2 --share-network-id 36ec5a17-cef6-44a8-a518-457a6f36faa0 NFS 2 * I see the below error in c-vol due to which even tho' my service VM is started, manila create errors out

Re: [openstack-dev] revert hacking to 0.8 series

On 06/16/2014 12:44 PM, Ben Nemec wrote: > On 06/16/2014 08:37 AM, Thierry Carrez wrote: >> Sean Dague wrote: >>> Hacking 0.9 series was released pretty late for Juno. The entire >>> check queue was flooded this morning with requirements proposals >>> failing pep8 because of it (so at 6am EST we we

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

Excerpts from Duncan Thomas's message of 2014-06-16 09:41:49 -0700: > On 16 June 2014 17:30, Jason Rist wrote: > > I'm going to have to agree with Tomas here. There doesn't seem to be > > any reasonable expectation of backwards compatibility for the reasons > > he outlined, despite some downstrea

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

Excerpts from Tomas Sedovic's message of 2014-06-16 09:19:40 -0700: > All, > > After having proposed some changes[1][2] to tripleo-heat-templates[3], > reviewers suggested adding a deprecation period for the merge.py script. > > While TripleO is an official OpenStack program, none of the projects

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

Why is OOO being singled out for backwards compatibility? -Original Message- From: Duncan Thomas [mailto:duncan.tho...@gmail.com] Sent: Monday, June 16, 2014 11:42 AM To: jr...@redhat.com; OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [TripleO]

Re: [openstack-dev] revert hacking to 0.8 series

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/16/2014 08:37 AM, Thierry Carrez wrote: > Sean Dague wrote: >> Hacking 0.9 series was released pretty late for Juno. The entire >> check queue was flooded this morning with requirements proposals >> failing pep8 because of it (so at 6am EST we we

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

On 16 June 2014 17:30, Jason Rist wrote: > I'm going to have to agree with Tomas here. There doesn't seem to be > any reasonable expectation of backwards compatibility for the reasons > he outlined, despite some downstream releases that may be impacted. Backward compatibility is a hard habit to

Re: [openstack-dev] [nova][cinder] Refactor ISCSIDriver to support other iSCSI transports besides TCP

On Thu, Mar 27, 2014 at 10:45 AM, Shlomi Sasson wrote: > Of course I’m aware of that.. I’m the one who pushed it there in the > first place J > > But it was not the best way to handle this.. I think that the right/better > approach is as suggested. > > > > I’m planning to remove the existing ISE

Re: [openstack-dev] Gate proposal - drop Postgresql configurations in the gate

On Sat, Jun 14, 2014 at 3:46 AM, Sean Dague wrote: > On 06/13/2014 06:47 PM, Joe Gordon wrote: > > > > > > > > On Thu, Jun 12, 2014 at 7:18 PM, Dan Prince > > wrote: > > > > On Thu, 2014-06-12 at 09:24 -0700, Joe Gordon wrote: > > > > > > On Jun 12, 2014 8:

Re: [openstack-dev] [TripleO] Backwards compatibility policy for our projects

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon 16 Jun 2014 10:19:40 AM MDT, Tomas Sedovic wrote: > All, > > After having proposed some changes[1][2] to > tripleo-heat-templates[3], reviewers suggested adding a deprecation > period for the merge.py script. > > While TripleO is an official O

[openstack-dev] [FWD] KVM Forum 2014 Call for Participation

- Forwarded message from Paolo Bonzini - > Date: Mon, 16 Jun 2014 18:08:17 +0200 > From: Paolo Bonzini > To: qemu-devel > Subject: [Qemu-devel] KVM Forum 2014 Call for Participation = KVM Forum 2014: Call For Participation

[openstack-dev] [TripleO] Backwards compatibility policy for our projects

All, After having proposed some changes[1][2] to tripleo-heat-templates[3], reviewers suggested adding a deprecation period for the merge.py script. While TripleO is an official OpenStack program, none of the projects under its umbrella (including tripleo-heat-templates) have gone through incubat

[openstack-dev] [barbican] Meeting Monday June 16 at 20:00 UTC

Hi Everyone, The Barbican team is hosting our weekly meeting today, Monday June 16nd, at 20:00 UTC in #openstack-meeting-alt Meeting agenda is available here https://wiki.openstack.org/wiki/Meetings/Barbican and everyone is welcomed to add agenda items. You can check this link http://time.is/080

  1   2   >