Re: [openstack-dev] [all] -1 due to line length violation in commit messages

+1 for <=80 chars. It will be uniform with the existing coding style. On Fri, Sep 25, 2015 at 8:22 PM, Dmitry Tantsur wrote: > On 09/25/2015 04:44 PM, Ihar Hrachyshka wrote: > >> Hi all, >> >> releases are approaching, so it’s the right time to start some bike >> shedding

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

git tools such as git log and git show indent the commit message in their output, so you don't actually have the full 79/80 character width to work with. That's where the 72 comes from. Doug Excerpts from Vikram Choudhary's message of 2015-09-25 20:25:41 +0530: > +1 for <=80 chars. It will be

Re: [openstack-dev] [nova] Servicegroup refactoring for the Control Plane - Mitaka

On Wed, 2015-09-23 at 11:11 -0700, Vilobh Meshram wrote: > Accepted in Liberty [1] [2] : > [1] Services information be stored in respective backend configured > by CONF.servicegroup_driver and all the interfaces which plan to > access service information go through servicegroup layer. > [2] Add

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On Fri, Sep 25, 2015 at 04:44:59PM +0200, Ihar Hrachyshka wrote: > Hi all, > > releases are approaching, so it’s the right time to start some bike shedding > on the mailing list. > > Recently I got pointed out several times [1][2] that I violate our commit > message requirement [3] for the

Re: [openstack-dev] [oslo.messaging][devstack] Pika RabbitMQ driver implementation

Dmitriy Ukhlov wrote: Hello stackers, I'm working on new olso.messaging RabbitMQ driver implementation which uses pika client library instead of kombu. It related to https://blueprints.launchpad.net/oslo.messaging/+spec/rabbit-pika. In this letter I want to share current results and probably

[openstack-dev] [puppet] should puppet-neutron manage third party software?

In our last meeting [1], we were discussing about whether managing or not external packaging repositories for Neutron plugin dependencies. Current situation: puppet-neutron is installing (packages like neutron-plugin-*) & configure Neutron plugins (configuration files like

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On Sep 25, 2015, at 12:00 PM, Chris Hoge wrote: > >> >> On Sep 25, 2015, at 6:59 AM, Doug Hellmann wrote: >> >> Excerpts from Mark Voelker's message of 2015-09-25 01:20:04 +: On Sep 24, 2015, at 5:55 PM, Sabari Murugesan

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

> On Sep 25, 2015, at 6:59 AM, Doug Hellmann wrote: > > Excerpts from Mark Voelker's message of 2015-09-25 01:20:04 +: >>> >>> On Sep 24, 2015, at 5:55 PM, Sabari Murugesan wrote: >>> >>> Hi Melanie >>> >>> In general, images created by

Re: [openstack-dev] Apache2 vs uWSGI vs ...

On 09/25/2015 07:09 AM, Sergii Golovatiuk wrote: Hi, Morgan gave the perfect case why operators want to use uWSGI. Let's imagine a future when all openstack services will work as mod_wsgi processes under apache. It's like to put all eggs in one basket. If you need to reconfigure one service

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 09/25/2015 04:44 PM, Ihar Hrachyshka wrote: Hi all, releases are approaching, so it’s the right time to start some bike shedding on the mailing list. Recently I got pointed out several times [1][2] that I violate our commit message requirement [3] for the message lines that says:

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 09/25/2015 10:44 AM, Ihar Hrachyshka wrote: Hi all, releases are approaching, so it’s the right time to start some bike shedding on the mailing list. Recently I got pointed out several times [1][2] that I violate our commit message requirement [3] for the message lines that says:

Re: [openstack-dev] [puppet] service default value functions

On 09/23/2015 02:17 AM, Cody Herriges wrote: > Alex Schultz wrote: >> Hey puppet folks, >> >> Based on the meeting yesterday[0], I had proposed creating a parser >> function called is_service_default[1] to validate if a variable matched >> our agreed upon value of ''. This got me thinking >>

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 2015-09-25 16:44:59 +0200 (+0200), Ihar Hrachyshka wrote: [...] > I believe commit message lines of <=80 chars are absolutely fine > and should not get -1 treatment. I propose to raise the limit for > the guideline on wiki accordingly. [...] As one of those traditionalists who still does all

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On Fri, Sep 25, 2015 at 11:05:09AM -0400, Doug Hellmann wrote: > git tools such as git log and git show indent the commit message in > their output, so you don't actually have the full 79/80 character width > to work with. That's where the 72 comes from. It is also commonly done because so that

Re: [openstack-dev] CephFS native driver

I think having a native cephfs driver without nfs in the cloud is a very compelling feature. nfs is nearly impossible to make both HA and Scalable without adding really expensive dedicated hardware. Ceph on the other hand scales very nicely and its very fault tollerent out of the box. Thanks,

Re: [openstack-dev] [TripleO] tripleo.org theme

On 25/09/15 13:34, Dan Prince wrote: It has come to my attention that we aren't making great use of our tripleo.org domain. One thing that would be useful would be to have the new tripleo-docs content displayed there. It would also be nice to have quick links to some of our useful resources,

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

Yeah, and worse, since I never can remember the exact number(72 I guess), I always just round down to 70-1 to be safe. Its silly. Thanks, Kevin From: Ihar Hrachyshka [ihrac...@redhat.com] Sent: Friday, September 25, 2015 7:44 AM To: OpenStack Development

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On Fri, Sep 25 2015, Ihar Hrachyshka wrote: > I agree that very long commit message lines can be bad, f.e. if they > are 200+ chars. But <= 79 chars?.. Don’t think so. Especially since we > have 79 chars limit for the code. Agreed. <= 80 chars should be a rule of thumb and applied in a smart

Re: [openstack-dev] [oslo.messaging][devstack] Pika RabbitMQ driver implementation

Also a side question, that someone might know, Whatever happened to the folks from rabbitmq (incorporated? pivotal?) who were going to get involved in oslo.messaging, did that ever happen; if anyone knows? They might be a good bunch of people to review such a pika driver (since I think they

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

Another option... why are we wasting time on something that a computer can handle? Why not just let the line length be infinite in the commit message and have gerrit wrap it to length lines on merge? Thanks, Kevin From: Jim Rollenhagen

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On 09/25/15 at 09:59am, Doug Hellmann wrote: Excerpts from Mark Voelker's message of 2015-09-25 01:20:04 +: > > On Sep 24, 2015, at 5:55 PM, Sabari Murugesan wrote: > > Hi Melanie > > In general, images created by glance v1 API should be accessible using v2 and >

[openstack-dev] [all] -1 due to line length violation in commit messages

Hi all, releases are approaching, so it’s the right time to start some bike shedding on the mailing list. Recently I got pointed out several times [1][2] that I violate our commit message requirement [3] for the message lines that says: "Subsequent lines should be wrapped at 72 characters.”

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On Sep 25, 2015, at 10:42 AM, Andrew Laski wrote: > > On 09/25/15 at 09:59am, Doug Hellmann wrote: >> Excerpts from Mark Voelker's message of 2015-09-25 01:20:04 +: >>> > >>> > On Sep 24, 2015, at 5:55 PM, Sabari Murugesan >>> > wrote: >>> > >>> >

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

+1 for <=80 chars. 72 characters sometimes are not enough Regards, Ivan Kolodyazhny On Fri, Sep 25, 2015 at 6:05 PM, Doug Hellmann wrote: > git tools such as git log and git show indent the commit message in > their output, so you don't actually have the full 79/80

Re: [openstack-dev] [murano] [app-catalog] versions for murano assets in the catalog

To clarify a bit, We're unsure that running glance without keystone as a distribution mechanism for apps.openstack.org assets is a good idea/fit. Having assets stored in the local cloud all in one place (In glance) seems like a very good idea to me. We need closer communications between

Re: [openstack-dev] [oslo] nominating Brant Knudson for Oslo core

Not sure if my vote still counts, but +1. :-) On 09/24/2015 12:12 PM, Doug Hellmann wrote: > Oslo team, > > I am nominating Brant Knudson for Oslo core. > > As liaison from the Keystone team Brant has participated in meetings, > summit sessions, and other discussions at a level higher than some

Re: [openstack-dev] [puppet] should puppet-neutron manage third party software?

Hi There, I just added my comment on the review. I do agree with Emilien. There should be specific repos for plugins and drivers. BTW. I love the sdnmagic name ;-) Edgar On 9/25/15, 9:02 AM, "Emilien Macchi" wrote: >In our last meeting [1], we were discussing about

[openstack-dev] [release][ironic] Ironic 4.2.0 release

Hi all, I'm proud to announce the release of Ironic 4.2.0! This follows quickly on our 4.1.0 release with 21 bug fixes, and marks the completion of four blueprints. It is also the basis for our stable/Liberty branch, and will be included in the coordinated OpenStack Liberty release. Major

Re: [openstack-dev] [Large Deployments Team][Performance Team] New informal working group suggestion

On Tue, Sep 22, 2015 at 6:27 PM, Dina Belova wrote: > Hey, OpenStackers! > > I'm writing to propose to organise new informal team to work specifically > on the OpenStack performance issues. This will be a sub team in already > existing Large Deployments Team, and I suppose

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

That sounds like the right solution Andreas. thanks! -- Dims On Fri, Sep 25, 2015 at 1:42 AM, Andreas Jaeger wrote: > On 09/20/2015 03:06 PM, Andreas Jaeger wrote: > >> On 09/20/2015 02:16 PM, Duncan Thomas wrote: >> >>> Certainly for cinder, and I suspect many other project,

Re: [openstack-dev] Apache2 vs uWSGI vs ...

Hi, Morgan gave the perfect case why operators want to use uWSGI. Let's imagine a future when all openstack services will work as mod_wsgi processes under apache. It's like to put all eggs in one basket. If you need to reconfigure one service on controller it may affect another service. For

[openstack-dev] [Rally][Meeting][Agenda]

Hi, its a friendly reminder that if you what to discuss some topics at Rally meetings, please add you topic to our Meeting agenda https://wiki.openstack.org/wiki/Meetings/Rally#Agenda. Don't forget to specify who will lead topic discusion. Add some information about topic(links, etc.) Thank you

Re: [openstack-dev] Apache2 vs uWSGI vs ...

Alexandr, oauth, shibboleth & openid support are very keystone specific features. Many other openstack projects don't need these modules at all but they may require faster HTTP server (lighthttp/nginx). For all projects we may use "HTTP server -> uwsgi" model and leave apache for keystone as "

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

On 09/24/2015 04:21 PM, Chris Friesen wrote: On 09/24/2015 12:18 PM, Chris Friesen wrote: I think what happened is that we took the SIGTERM after the open() call in create_iscsi_target(), but before writing anything to the file. f = open(volume_path, 'w+')

[openstack-dev] [Cinder] Late Liberty patches should now be unblocked ...

All, Now that Mitaka is open I have done my best to go through and remove all the -2's that I had given to block Liberty patches that needed to wait for Mitaka. If you have a patch that I missed please ping me on IRC. Happy Mitaka merging! Thanks, Jay

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 09/25/2015 12:15 PM, Fox, Kevin M wrote: > Another option... why are we wasting time on something that a > computer can handle? Why not just let the line length be infinite in > the commit message and have gerrit wrap it to here> length lines on merge? I don't think gerrit should mess with

[openstack-dev] [neutron][horizon] Nice new Network Topology panel in Horizon

It has been about three years in the making but now it is finally here. A screenshot doesn't do it justice, so here is a short video overview: https://youtu.be/PxFd-lJV0e4 Isn't that neat? I am sure you can see that it is a great improvement, especially for larger topologies. This new view will

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On 09/25/15 at 07:44pm, Rochelle Grober wrote: Doug Hellmann wrote: Excerpts from Mark Voelker's message of 2015-09-25 17:42:24 +: On Sep 25, 2015, at 1:24 PM, Brian Rosmaita wrote: > > I'd like to clarify something. > > On 9/25/15, 12:16 PM, "Mark Voelker"

Re: [openstack-dev] [oslo.messaging][devstack] Pika RabbitMQ driver implementation

Hello Joshua, thank you for your feedback. This will end up on review.openstack.org right so that it can be properly > reviewed (it will likely take a while since it looks to be ~1000+ lines of > code)? Yes, sure I will send this patch to review.openstack.org, but first of all I need to get

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On Sep 25, 2015, at 1:56 PM, Doug Hellmann wrote: > > Excerpts from Mark Voelker's message of 2015-09-25 17:42:24 +: >> On Sep 25, 2015, at 1:24 PM, Brian Rosmaita >> wrote: >>> >>> I'd like to clarify something. >>> >>> On 9/25/15,

Re: [openstack-dev] Apache2 vs uWSGI vs ...

There is no reason why the wsgi app container matters. This is simply a "we should document use if uwsgi and/or gunicorn as an alternative to mod_wsgi". If one solution is better for the gate it will be used there and each deployment will make the determination of what they want to use. Adam's

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On 09/25/15 at 03:09pm, Mark Voelker wrote: On Sep 25, 2015, at 10:42 AM, Andrew Laski wrote: On 09/25/15 at 09:59am, Doug Hellmann wrote: Excerpts from Mark Voelker's message of 2015-09-25 01:20:04 +: > > On Sep 24, 2015, at 5:55 PM, Sabari Murugesan

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On Sep 25, 2015, at 1:24 PM, Brian Rosmaita wrote: > > I'd like to clarify something. > > On 9/25/15, 12:16 PM, "Mark Voelker" wrote: > [big snip] >> Also worth pointing out here: when we talk about ³doing the same thing² >> from a DefCore

Re: [openstack-dev] [Cinder] Late Liberty patches should now be unblocked ...

Thanks, Jay. I've removed my -2's last night. If I missed something, please ping me via e-mail or IRC (e0ne). Regards, Ivan Kolodyazhny On Fri, Sep 25, 2015 at 7:59 PM, Jay S. Bryant < jsbry...@electronicjungle.net> wrote: > All, > > Now that Mitaka is open I have done my best to go through

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

> -Original Message- > From: Eric Harney [mailto:ehar...@redhat.com] > Sent: Friday, September 25, 2015 2:56 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [cinder] should we use fsync when writing iscsi > config file? > > On

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

> -Original Message- > From: Chris Friesen [mailto:chris.frie...@windriver.com] > Sent: Friday, September 25, 2015 3:04 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [cinder] should we use fsync when writing iscsi > config file? > > On 09/25/2015 12:30 PM,

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

Doug Hellmann wrote: Excerpts from Mark Voelker's message of 2015-09-25 17:42:24 +: > On Sep 25, 2015, at 1:24 PM, Brian Rosmaita > wrote: > > > > I'd like to clarify something. > > > > On 9/25/15, 12:16 PM, "Mark Voelker" wrote: > >

Re: [openstack-dev] [Heat] Assumptions regarding extensions to OpenStack api's

On 09/25/2015 02:32 PM, Pratik Mallya wrote: Hello Heat Team, I was wondering if OpenStack Heat assumes that the Nova extensions api would always exist in a cloud? My impression was that since these features are extensions, they may or may not be implemented by the cloud provider and hence Heat

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

On 09/25/2015 12:30 PM, Mitsuhiro Tanino wrote: On 09/22/2015 06:43 PM, Robert Collins wrote: On 23 September 2015 at 09:52, Chris Friesen wrote: Hi, I recently had an issue with one file out of a dozen or so in "/opt/cgcs/cinder/data/volumes/" being present but

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 2015-09-25 16:15:15 + (+), Fox, Kevin M wrote: > Another option... why are we wasting time on something that a > computer can handle? Why not just let the line length be infinite > in the commit message and have gerrit wrap it to number here> length lines on merge? The commit message

[openstack-dev] [OpenStack-Dev] Recent proposal to remove NetApp drivers

Hey Everyone, So I've been kinda busy on IRC today with conversations about some patches I proposed yesterday [1], [2]. I thought maybe I should try and explain my actions a bit, because it seems that some think I just arbitrarily flew off the handle and proposed something drastic, or that I had

[openstack-dev] [Heat] Assumptions regarding extensions to OpenStack api's

Hello Heat Team, I was wondering if OpenStack Heat assumes that the Nova extensions api would always exist in a cloud? My impression was that since these features are extensions, they may or may not be implemented by the cloud provider and hence Heat must not rely on it being present. My

Re: [openstack-dev] [neutron][horizon] Nice new Network Topology panel in Horizon

Great job Henry ! On Fri, Sep 25, 2015 at 6:47 PM, Henry Gessau wrote: > It has been about three years in the making but now it is finally here. > A screenshot doesn't do it justice, so here is a short video overview: > https://youtu.be/PxFd-lJV0e4 > > Isn't that neat? I am

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

On 09/25/2015 02:30 PM, Mitsuhiro Tanino wrote: > On 09/22/2015 06:43 PM, Robert Collins wrote: >> On 23 September 2015 at 09:52, Chris Friesen >> wrote: >>> Hi, >>> >>> I recently had an issue with one file out of a dozen or so in >>>

Re: [openstack-dev] [OpenStack-Dev] Recent proposal to remove NetApp drivers

On 09/25/2015 03:15 PM, John Griffith wrote: > Hey Everyone, > > So I've been kinda busy on IRC today with conversations about some patches > I proposed yesterday [1], [2]. > > I thought maybe I should try and explain my actions a bit, because it seems > that some think I just arbitrarily flew

Re: [openstack-dev] [OpenStack-Dev] Recent proposal to remove NetApp drivers

On 2015-09-25 13:15:24 -0600 (-0600), John Griffith wrote: [...] > It seems that there are folks that have taken quite a bit of offense to > this, and are more than mildly upset with me. To them I apologize if this > upset you. I will say however that given the same situation and timing, I >

Re: [openstack-dev] [OpenStack-Dev] Recent proposal to remove NetApp drivers

On Fri, Sep 25, 2015 at 1:15 PM, John Griffith wrote: > Hey Everyone, > > So I've been kinda busy on IRC today with conversations about some patches > I proposed yesterday [1], [2]. > > I thought maybe I should try and explain my actions a bit, because it > seems that

Re: [openstack-dev] [neutron][horizon] Nice new Network Topology panel in Horizon

On Fri, Sep 25, 2015, Daniel Comnea wrote: > Great job Henry ! I had nothing to do with it! (See below.) > On Fri, Sep 25, 2015 at 6:47 PM, Henry Gessau > wrote: > > It has been about three years in the making but now it

Re: [openstack-dev] [Openstack-operators] [puppet] feedback request about puppet-keystone

On 09/21/2015 12:20 PM, Emilien Macchi wrote: > Hi, > > Puppet OpenStack group would like to know your feedback about using > puppet-keystone module. > > Please take two minutes and feel the form [1] that contains a few > questions. The answers will help us to define our roadmap for the next >

Re: [openstack-dev] [TripleO] tripleo.org theme

On 09/25/2015 07:34 AM, Dan Prince wrote: > It has come to my attention that we aren't making great use of our > tripleo.org domain. One thing that would be useful would be to have the > new tripleo-docs content displayed there. It would also be nice to have > quick links to some of our useful

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

Excerpts from Mark Voelker's message of 2015-09-25 17:42:24 +: > On Sep 25, 2015, at 1:24 PM, Brian Rosmaita > wrote: > > > > I'd like to clarify something. > > > > On 9/25/15, 12:16 PM, "Mark Voelker" wrote: > > [big snip] > >> Also

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

I'd like to clarify something. On 9/25/15, 12:16 PM, "Mark Voelker" wrote: [big snip] >Also worth pointing out here: when we talk about ³doing the same thing² >from a DefCore perspective, we¹re essentially talking about what¹s >exposed to the end user, not how that¹s

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

On 09/22/2015 06:43 PM, Robert Collins wrote: > On 23 September 2015 at 09:52, Chris Friesen > wrote: >> Hi, >> >> I recently had an issue with one file out of a dozen or so in >> "/opt/cgcs/cinder/data/volumes/" being present but of size zero. I'm >> running

Re: [openstack-dev] [puppet] should puppet-neutron manage third party software?

On 09/25/2015 12:14 PM, Edgar Magana wrote: > Hi There, > > I just added my comment on the review. I do agree with Emilien. There should > be specific repos for plugins and drivers. > > BTW. I love the sdnmagic name ;-) > > Edgar > > > > > On 9/25/15, 9:02 AM, "Emilien Macchi"

Re: [openstack-dev] [Glance][Solum] Using os-auth-token and os-image-url with glance client

Steve, Similar to other OpenStack services, Solum client uses the provided/configured username and password of a user to get a token, and sends it to Solum API service in a http header. On the API side, we use keystonemiddleware to validate the token. Upon successful authentication, we store

Re: [openstack-dev] [Glance][Solum] Using os-auth-token and os-image-url with glance client

Nikhil, Flavio, Thank you for giving immediate attention to this issue. Regards, Devdatta From: Flavio Percoco Sent: Friday, September 25, 2015 4:02 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re:

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

I think there's a place for yet another service breakout from nova - some sort of like-weight platform orchestration piece, nothing as complicated or complete as heat, nothing that touches the inside of a VM, just something that can talk to cinder, nova and neutron (plus I guess ironic and

Re: [openstack-dev] [Congress] Congress Usecases VM

Thanks Alex, Zhou, I get errors from congress when I do a re-join. These errors seem to due to the order in which the services are coming up. Hence I still depend on running stack.sh after the VM is up and running. Please try out the new VM - also advise if you need to add any of your use

[openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

In November, the OpenStack Foundation will start requiring vendors requesting new "OpenStack Compatible" storage driver licenses to start passing the Cinder third-party integration tests. The new program was approved by the Board at the July meeting in Austin and follows the improvement of the

[openstack-dev] Murano code flow for custom development and combining murano with horizon in devstack

Hello, Could anyone let me know if the changes in murano dashboard and horizon's openstackdashboard, both be combined and showed under one tab. i.e. say under Murano tab on the side left panel all the changes done in horizon and murano both appear. If anyone could point me to a link explaining

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

> On Sep 25, 2015, at 10:12 AM, Andrew Laski wrote: > > I understand that reasoning, but still am unsure on a few things. > > The direction seems to be moving towards having a requirement that the same > functionality is offered in two places, Nova API and Glance V2 API.

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On 09/25/2015 06:37 PM, Chris Hoge wrote: On Sep 25, 2015, at 10:12 AM, Andrew Laski > wrote: I understand that reasoning, but still am unsure on a few things. The direction seems to be moving towards having a requirement that the same

Re: [openstack-dev] [Manila] CephFS native driver

On 09/24/2015 09:49 AM, John Spray wrote: Hi all, I've recently started work on a CephFS driver for Manila. The (early) code is here: https://github.com/openstack/manila/compare/master...jcsp:ceph Awesome! This is something that's been talking about for quite some time and I'm pleased to

Re: [openstack-dev] CephFS native driver

> nfs is nearly impossible to make both HA and Scalable without adding really > expensive dedicated hardware. I don't think we need quite expensive hardware for this purpose. What I'm thinking now is: [Controller] [Compute1] ... [ComputeN] [ RADOS ] Controller

Re: [openstack-dev] [lbaas] [octavia] Proposing new meeting time Wednesday 16:00 UTC

All, In our last meeting [1] we discussed moving the meeting earlier to accommodate participants from the EMEA region. I am therefore proposing to move the meeting to 16:00 UTC on Wednesday. Please respond to this e-mail if you have alternate suggestions. I will send out another e-mail announcing

[openstack-dev] [neutron] congrats to armax!

First, congratulations to armax on being elected PTL for Mitaka. Looking forward to Neutron improving over the next six months. Second thanks to everybody that voted in the election. Hopefully we had something close to 100% turnout, because that is an important responsibility of the population.

[openstack-dev] [all][elections] PTL Election Conclusion and Results

Thank you to the electorate, to all those who voted and to all candidates who put their name forward for PTL for this election. A healthy, open process breeds trust in our decision making capability thank you to all those who make this process possible. Now for the results of the PTL election

Re: [openstack-dev] [all][elections] PTL Election Conclusion and Results

Congratulations to our PTLs! Let's make Mitaka a great release. As Neutron core I want to congratulate to Rosella, Ryan and Armando for volunteering. It is a huge responsibility and we all going to help. Armando, Next round of beers on you! Cheers, Edgar Sent from my iPhone > On Sep

Re: [openstack-dev] [lbaas] [octavia] Proposing new meeting time Wednesday 16:00 UTC

Works for me. Doug > On Sep 25, 2015, at 5:58 PM, Eichberger, German > wrote: > > All, > > In our last meeting [1] we discussed moving the meeting earlier to > accommodate participants from the EMEA region. I am therefore proposing to > move the meeting to 16:00

Re: [openstack-dev] [all][elections] PTL Election Conclusion and Results

Congrats Armando! On Sep 26, 2015 5:57 AM, "Edgar Magana" wrote: > Congratulations to our PTLs! > > Let's make Mitaka a great release. > > As Neutron core I want to congratulate to Rosella, Ryan and Armando for > volunteering. It is a huge responsibility and we all

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

+1 from me, although I thought heat was supposed to be this thing? Maybe there should be a 'warm' project or something ;) Or we can call it 'bbs' for 'building block service' (obviously not bulletin board system); ask said service to build a set of blocks into well defined structures and let

Re: [openstack-dev] [OPNFV] [Functest] Tempest & Rally

Morgan, You should add at least: sla: failure_rate: max: 0 Otherwise rally will pass 100% no matter what is happening. Best regards, Boris Pavlovic On Thu, Sep 24, 2015 at 10:29 PM, Tikkanen, Viktor (Nokia - FI/Espoo) < viktor.tikka...@nokia.com> wrote: > Hi Morgan > > and thank you

[openstack-dev] [all][elections] Candidate proposals for TC (Technical Committee) positions are now open

Candidate proposals for the Technical Committee positions (6 positions) are now open and will remain open until October 1, 05:59 UTC. All candidacies must be submitted as a text file to the openstack/election repository as explained on the wiki[0]. Candidates for the Technical Committee

Re: [openstack-dev] [mistral] Define better terms for WAITING and DELAYED states

Thank you Robert for the explanation in details! >- RUNNING_DELAYED - a substate of RUNNING and it has exactly this >meaning: it’s generally running but delayed till some later time. >- WAITING - it is not a substate of RUNNING and hence it means a task >has not started yet > >

Re: [openstack-dev] [openstack-operators][Rally] Rally plugins reference is available

Cool! On Fri, Sep 25, 2015 at 3:05 AM, Boris Pavlovic wrote: > Hi stackers, > > As far as you know Rally test cases are created as a mix of plugins. > > At this point of time we have more than 200 plugins for almost all > OpenStack projects. > Before you had to analyze code

[openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

Hi everyone, (TL;DR: we would like an L2 agent extension to be able to call methods on the agent class, e.g. OVSAgent) In the networking-bgpvpn project, we need the reference driver to interact with the ML2 openvswitch agent with new RPCs to allow exchanging information with the BGP VPN

Re: [openstack-dev] [ironic] Ironic is open for Mitaka development

Jim Rollenhagen wrote: > I've proposed a patch to release Ironic 4.2.0, and we will be cutting > the stable/liberty branch from the same SHA: > https://review.openstack.org/#/c/227582/ It's now released at: https://launchpad.net/ironic/liberty/4.2.0 and the Liberty release branch was cut at:

Re: [openstack-dev] [Manila] CephFS native driver

On Fri, Sep 25, 2015 at 8:04 AM, Shinobu Kinjo wrote: > So here are questions from my side. > Just question. > > > 1.What is the biggest advantage comparing others such as RDB? > We should be able to implement what you are going to do in > existing module, shouldn't we? I

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

I think the 4th of the options you proposed would be the best. We don't want to give agents direct access to the agent object or else we will run the risk of breaking extensions all of the time during any kind of reorganization or refactoring. Having a well defined API in between will give us

[openstack-dev] [Neutron] [Ceilometer] Liberty RC1 available

Hello everyone, Ceilometer and Neutron just produced their first release candidate for the end of the Liberty cycle. The RC1 tarballs, as well as a list of last-minute features and fixed bugs since liberty-1 are available at: https://launchpad.net/ceilometer/liberty/liberty-rc1

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

Sorry, that should have said, "We don't want to give extensions direct access to the agent object..." On Fri, Sep 25, 2015 at 1:57 AM, Kevin Benton wrote: > I think the 4th of the options you proposed would be the best. We don't > want to give agents direct access to the

Re: [openstack-dev] [OPNFV] [Functest] Tempest & Rally

Jose, Rally community provides official docker images here: https://hub.docker.com/r/rallyforge/rally/ So I would suggest to use them. Best regards, Boris Pavlovic On Fri, Sep 25, 2015 at 5:07 AM, Jose Lausuch wrote: > Hi, > > > > Thanks for the hint Boris. > >

[openstack-dev] VDI questions

Hi guys, I am new to OpenStack, so I want to ask is there a project that works on VDI(Virtual Desktop Infrastructure) based OpenStack? I want to dig into it, please help. Sincerely, Zhao -- Best regards Junwang Zhao Department of Computer Science Peking University Beijing, 100871, PRC

[openstack-dev] [TripleO] tripleo.org theme

It has come to my attention that we aren't making great use of our tripleo.org domain. One thing that would be useful would be to have the new tripleo-docs content displayed there. It would also be nice to have quick links to some of our useful resources, perhaps Derek's CI report [1], a custom

Re: [openstack-dev] Apache2 vs uWSGI vs ...

Are we discussing mod_wsgi and Keystone or OpenStack as a general? If Keystone specific use case, then probably Apache provides broadest choice of tested external authenticators. I'm not against uwsgi at all, but to be honest expectation that nginx could substitute Apache in terms of

[openstack-dev] [mistral] Mistral Liberty RC1 available

Hi, Mistral Liberty RC1 release is available. The exact version name is 1.0.0.0rc1. Look at the release page in order to see a list of bugs fixed during RC1 cycle: https://launchpad.net/mistral/liberty/liberty-rc1 Thanks! Renat Akhmerov @

[openstack-dev] [oslo.messaging][devstack] Pika RabbitMQ driver implementation

Hello stackers, I'm working on new olso.messaging RabbitMQ driver implementation which uses pika client library instead of kombu. It related to https://blueprints.launchpad.net/oslo.messaging/+spec/rabbit-pika. In this letter I want to share current results and probably get first feedack from

Re: [openstack-dev] [Manila] CephFS native driver

Thanks! Keep me in the loop. Shinobu - Original Message - From: "John Spray" To: "Shinobu Kinjo" Cc: "OpenStack Development Mailing List (not for usage questions)" Sent: Friday, September 25, 2015 6:54:09 PM

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

Kevin, Miguel, I agree that (4) is what makes most sense. (more below) Miguel Angel Ajo : Do you have a rough idea of what operations you may need to do? Right now, what bagpipe driver for networking-bgpvpn needs to interact with is: - int_br OVSBridge (read-only) - tun_br OVSBridge (add

Re: [openstack-dev] Apache2 vs uWSGI vs ...

On Fri, Sep 25, 2015 at 8:25 AM Adam Heczko wrote: > Are we discussing mod_wsgi and Keystone or OpenStack as a general? > If Keystone specific use case, then probably Apache provides broadest > choice of tested external authenticators. > I'm not against uwsgi at all, but to

  1   2   >