Re: [openstack-dev] [Nova] Concerns around the Extensible Resource Tracker design - revert maybe?

On 08/14/2014 10:25 PM, Sylvain Bauza wrote: > Hi mikal, > > Le 14 août 2014 01:49, "Michael Still" > a écrit : >> >> So, there's been a lot of email in the last few days and I feel I am >> not keeping up. >> >> Sylvain, can you summarise for me what the plan is here? Ca

[openstack-dev] [Octavia] Object Model and DB Structure

So I've been assuming that the Octavia object model would be an exact copy of the neutron lbaas one with additional information for Octavia. However, after thinking about it I'm not sure this is the right way to go because the object model in neutron lbaas may change in the future, and Octavia can'

Re: [openstack-dev] [Neutron][DevStack] How to increase developer usage of Neutron

"CARVER, PAUL" wrote on 08/14/2014 09:35:17 AM: > Mike Spreitzer [mailto:mspre...@us.ibm.com] wrote: > > >I'll bet I am not the only developer who is not highly competent with > >bridges and tunnels, Open VSwitch, Neutron configuration, and how DevStack > >transmutes all those. My bet is that

[openstack-dev] [OpenStack-Dev] [Cinder] Summer 2014 meetup summary

Hey Everyone, I wanted to send out a quick message regarding the Cinder Mid-Cycle (kinda) Meetup we just finished up at the Fort Collins HP Site. First off, I want to thank everyone who attended for a great and very productive three days!! Not only did we have a strong physical turn-out (16 par

Re: [openstack-dev] [neutron][ml2] Mech driver as out-of-tree add-on

>I also feel like the drivers/plugins are currently BEYOND a tipping point, and are in fact dragging down velocity of the core project in many ways. Can you elaborate on the ways that they are slowing down the velocity? I know they take up reviewer time, but are there other ways that you think the

Re: [openstack-dev] [neutron][ml2] Mech driver as out-of-tree add-on

On Thu, Aug 14, 2014 at 9:07 PM, Kyle Mestery wrote: > I also feel like the drivers/plugins are currently BEYOND a tipping > point, and are in fact dragging down velocity of the core project in > many ways. I'm working on a proposal for Kilo where we move all > drivers/plugins out of the main Neu

[openstack-dev] [TripleO] Python 3 support in os-*-config

Hai, I've been poking at Python 3 support in os-*-config recently, and here's what is going on with it: * os-apply-config This one looks to be the hardest one to port. Multiple test failures, hard coded use of '#!/usr/bin/env python' which is unhappy in a only Python 3 environment, ma

[openstack-dev] [Sahara] Swift authentication and backwards compatibility

hello Sahara folks, I am working to get the revamped spec[1] finalized and I'd like to know the group's thoughts on the idea of backward compatibility. It is possible to implement the new authentication method and remain backward compatible, but we will need to keep the username and password in

Re: [openstack-dev] [Neutron] Simple proposal for stabilizing new features in-tree

Hi Sridar, Yes I know this is only for phase 1, while I'm also thinking about how it should be in next phase. At least, zone concept should be introduced, we may use it to replace SG, to eliminate potential conflicts of defining ACL in two different places. Fro

Re: [openstack-dev] Is there a way to let nova schedule plugin fetch glance image metadata

Dugger, Sylvain, thanks for your replies. On Fri, Aug 15, 2014 at 3:55 AM, Sylvain Bauza wrote: > Mmm... I can understand that you perhaps need an external scheduler for > your own purposes, but I think you can't expect your plugin merged upstream > for two reasons : > - during Icehouse, there

[openstack-dev] [congress] Policy mid cycle summit

We are getting together to discuss the state of policy. RSVP at https://www.eventbrite.com/e/openstack-policy-summit-tickets-12642081807. The meeting will be over two days at the VMware campus in Palo Alto. Join us! Help us develop the agenda here https://etherpad.openstack.org/p/juno-midcycle-

Re: [openstack-dev] [all] The future of the integrated release

On 08/13/2014 06:42 AM, Daniel P. Berrange wrote: On Thu, Aug 07, 2014 at 03:56:04AM -0700, Jay Pipes wrote: On 08/07/2014 02:12 AM, Kashyap Chamarthy wrote: On Thu, Aug 07, 2014 at 07:10:23AM +1000, Michael Still wrote: On Wed, Aug 6, 2014 at 2:03 AM, Thierry Carrez wrote: We seem to be un

Re: [openstack-dev] [Congress] Help in understanding API Flow

Hi Madhu, If you are trying to expose data from a new service, you need to add a new data-source driver (examples from nova and neutron are in the tree.) Once a data-source driver is registered, data from the data source will be exposed through the API automatically, and you will also be able

Re: [openstack-dev] [all] The future of the integrated release

> > Additional cross-project resources can be ponied up by the large > > contributor companies, and existing cross-project resources are not > > necessarily divertable on command. > > Sure additional cross-project resources can and need to be ponied up, but I > am doubtful that will be enough. O

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On 08/14/2014 02:48 PM, Dugger, Donald D wrote: My experience with mics, no matter how good, In conference rooms is not good. You are always working hard to hear the soft spoken person who is drowned by the background noise. It’s always a strain and I don’t want to even think about doing it

Re: [openstack-dev] Which program for Rally

Matt, One thing did just occur to me while writing this though it's probably worth > investigating splitting out the stress test framework as an external > tool/project after we start work on the tempest library. [3] I fully agree with the fact that stress testing doesn't belong to Tempest. Th

Re: [openstack-dev] [nova] Review priorities as we approach juno-3

I have also been reminded that http://54.201.139.117/nova-bugs.html tracks bugs with outstanding code reviews (click on "ready for review"). There are 179 at the moment, so it sure would be cool to land some bug fixes. Thanks, Michael On Fri, Aug 15, 2014 at 5:57 AM, Michael Still wrote: > Hi. >

Re: [openstack-dev] [all] The future of the integrated release

On Aug 14, 2014, at 4:41 PM, Joe Gordon wrote: > > > > On Wed, Aug 13, 2014 at 12:24 PM, Doug Hellmann wrote: > > On Aug 13, 2014, at 3:05 PM, Eoghan Glynn wrote: > > > > >>> At the end of the day, that's probably going to mean saying No to more > >>> things. Everytime I turn around every

Re: [openstack-dev] [nova] Review priorities as we approach juno-3

Le 14 août 2014 22:02, "Michael Still" a écrit : > > Hi. > > We're rapidly approaching j-3, so I want to remind people of the > current reviews that are high priority. The definition of high > priority I am using here is blueprints that are marked high priority > in launchpad that have outstanding

Re: [openstack-dev] [Cinder] 3'rd party CI systems: Not Whitelisted Volume type with name * could not be found.

They need to be manually added. -Original Message- From: Asselin, Ramy Sent: Thursday, August 14, 2014 2:17 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Cinder] 3'rd party CI systems: Not Whitelisted Volume type with name * could not

[openstack-dev] [Nova] [Containers] Containers Service for OpenStack

OpenStack Devs, In accordance with guidance from the Nova team at the Midcycle meeting, I have drafted the following proposal for a new OpenStack service to fit into the Compute program: https://blueprints.launchpad.net/nova/+spec/containers-service https://review.openstack.org/114044 Please t

Re: [openstack-dev] [Cinder] 3'rd party CI systems: Not Whitelisted Volume type with name * could not be found.

Both configurations have that set as you described. [1][2] Who actually creates that volume type? Is that supposed to be added manually to local.sh, or is this a bug in devstack? [1] http://publiclogs.emc.com/vnx_ostack/EMC_VNX_FC/212/logs/etc/cinder/cinder.conf.txt.gz [DEFAULT] default_volume_

Re: [openstack-dev] [Ceilometer] Way to get wrapped method's name/class using Pecan secure decorators?

On Aug 14, 2014, at 12:38 PM, Pendergrass, Eric wrote: > Sure, Doug. We want the ability to selectively apply policies to certain > Ceilometer > API methods based on user/tenant roles. > > For example, we want to restrict the ability to execute Alarm deletes to > admins and user/tenants who ha

Re: [openstack-dev] Which program for Rally

On Wed, Aug 13, 2014 at 03:48:59PM -0600, Duncan Thomas wrote: > On 13 August 2014 13:57, Matthew Treinish wrote: > > On Tue, Aug 12, 2014 at 01:45:17AM +0400, Boris Pavlovic wrote: > >> Keystone, Glance, Cinder, Neutron and Heat are running rally performance > >> jobs, that can be used for perfor

Re: [openstack-dev] [neutron] Which changes need accompanying bugs?

On Aug 13, 2014, at 11:11 AM, Kevin Benton wrote: > Is the pylint static analysis that caught that error prone to false > positives? If not, I agree that it would be really nice if that were made > part of the tox check so these don't have to be fixed after the fact. > > To me that particular p

Re: [openstack-dev] [Cinder] 3'rd party CI systems: Not Whitelisted Volume type with name * could not be found.

Cinder.conf needs to have a default_volume_type entry set under the [Default] group and a volume type that is valid, for example, default_volume_type=bronze. This allows for a volume to be created when a volume type is not selected, the default 'None' type. This feature has been available for

Re: [openstack-dev] [nova][core] Expectations of core reviewers

Le 14 août 2014 21:56, "Joe Gordon" a écrit : > > > > > On Thu, Aug 14, 2014 at 1:47 AM, Daniel P. Berrange wrote: >> >> On Thu, Aug 14, 2014 at 09:24:36AM +1000, Michael Still wrote: >> > On Thu, Aug 14, 2014 at 3:09 AM, Dan Smith wrote: >> > >> I'm not questioning the value of f2f - I'm questi

Re: [openstack-dev] [nova] Review priorities as we approach juno-3

On Fri, Aug 15, 2014 at 6:37 AM, Dan Smith wrote: >> == Move Virt Drivers to use Objects (Juno Work) == >> >> I couldn't actually find any code out for review for this one apart >> from https://review.openstack.org/#/c/94477/, is there more out there? > > This was an umbrella one to cover a bunch

Re: [openstack-dev] [all] The future of the integrated release

On Wed, Aug 13, 2014 at 12:24 PM, Doug Hellmann wrote: > > On Aug 13, 2014, at 3:05 PM, Eoghan Glynn wrote: > > > > >>> At the end of the day, that's probably going to mean saying No to more > >>> things. Everytime I turn around everyone wants the TC to say No to > >>> things, just not to their

Re: [openstack-dev] [neutron] [third-party] What tests are required to be run

Hi- I'm hitting bugs for (basic/advanced)_server_ops testing. https://bugs.launchpad.net/nova/+bug/1232303 Kindly help me with a fix to this. Thanking you. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Kyle Mestery [mailto:mest..

[openstack-dev] [sahara] python-saharaclient 0.7.1 released

Hi folks, python-saharaclient 0.7.1 released. The prev. released 0.7.0 has been released about a half of year ago. The 0.7.1 release contains a bunch of bug fixes and improvements, update requirements to Juno ones and etc. Tarball: http://tarballs.openstack.org/python-saharaclient/python-sahar

Re: [openstack-dev] [nova] Review priorities as we approach juno-3

> == Move Virt Drivers to use Objects (Juno Work) == > > I couldn't actually find any code out for review for this one apart > from https://review.openstack.org/#/c/94477/, is there more out there? This was an umbrella one to cover a bunch of virt driver objects work done early in the cycle. Much

Re: [openstack-dev] [Nova] Concerns around the Extensible Resource Tracker design - revert maybe?

Hi mikal, Le 14 août 2014 01:49, "Michael Still" a écrit : > > So, there's been a lot of email in the last few days and I feel I am > not keeping up. > > Sylvain, can you summarise for me what the plan is here? Can we roll > forward or do we need to revert? Well, as we agreed with Nikola, the pr

Re: [openstack-dev] [OpenStack-Infra] [infra] Third Party CI naming and contact (action required)

On 2014-08-14 20:50:21 +0200 (+0200), Lucas Eznarriaga wrote: [...] > We have a problem with zuul-merger when the host id of > review.openstack.org changes. In this case, the new rsa key has to > be added manually [...] If so, you were broken a while... the last (and effectively only in recent his

[openstack-dev] [sahara] team meeting minutes Aug 14

Thanks everyone who have joined Sahara meeting. Here are the logs from the meeting: http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-08-14-18.00.html http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-08-14-18.00.log.html -- Sincerely yours, Sergey Lukjanov Sahara Te

[openstack-dev] [nova] Review priorities as we approach juno-3

Hi. We're rapidly approaching j-3, so I want to remind people of the current reviews that are high priority. The definition of high priority I am using here is blueprints that are marked high priority in launchpad that have outstanding code for review -- I am sure there are other reviews that are

Re: [openstack-dev] Is there a way to let nova schedule plugin fetch glance image metadata

Mmm... I can understand that you perhaps need an external scheduler for your own purposes, but I think you can't expect your plugin merged upstream for two reasons : - during Icehouse, there was an effort for not having the scheduler proxying to the compute nodes - Call for scheduler needs to go th

Re: [openstack-dev] [Neutron][DevStack] How to increase developer usage of Neutron

"CARVER, PAUL" wrote on 08/14/2014 09:35:17 AM: > Mike Spreitzer [mailto:mspre...@us.ibm.com] wrote: > > >I'll bet I am not the only developer who is not highly competent with > >bridges and tunnels, Open VSwitch, Neutron configuration, and how DevStack > >transmutes all those. My bet is that

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Thu, Aug 14, 2014 at 1:47 AM, Daniel P. Berrange wrote: > On Thu, Aug 14, 2014 at 09:24:36AM +1000, Michael Still wrote: > > On Thu, Aug 14, 2014 at 3:09 AM, Dan Smith wrote: > > >> I'm not questioning the value of f2f - I'm questioning the idea of > > >> doing f2f meetings sooo many times a

Re: [openstack-dev] [OpenStack-Dev][Cinder] Cinder Core nomination

Great nomination Walt. Thank you! +1 Thank you Xing for your contributions! Jay On Thu, 2014-08-14 at 06:55 +, Boring, Walter wrote: > Hey guys, >I wanted to pose a nomination for Cinder core. > > Xing Yang. > She has been active in the cinder community for many releases and has worke

Re: [openstack-dev] [OpenStack-Dev][Cinder] Cinder Core nomination

On Thu, Aug 14, 2014 at 10:29 AM, Mike Perez wrote: > On 06:55 Thu 14 Aug , Boring, Walter wrote: > > Hey guys, > >I wanted to pose a nomination for Cinder core. > > > > Xing Yang. > > She has been active in the cinder community for many releases and has > worked on several drivers as wel

Re: [openstack-dev] [OpenStack-Infra] [infra] Third Party CI naming and contact (action required)

Hi, Midokura CI should be up to date now too. We have a problem with zuul-merger when the host id of review.openstack.org changes. In this case, the new rsa key has to be added manually otherwise the build will fail with a: Merge Failed. This change was unable to be automatically merged with the

Re: [openstack-dev] [nova][core] Expectations of core reviewers

My experience with mics, no matter how good, In conference rooms is not good. You are always working hard to hear the soft spoken person who is drowned by the background noise. It’s always a strain and I don’t want to even think about doing it for a full 8 hrs. It’s better than nothing so I a

[openstack-dev] [oslo] Issues with POSIX semaphores and other locks in lockutils

Hello. It started (for me) with a bug [1] that stated one problem with POSIX semaphores. I started implementing fix for that [2] and it appeared that there are other issues with lockutils. Discussion got spread over bug [1] and Gerrit [2] and got limited to those who get notifications on them. I'd

Re: [openstack-dev] Is there a way to let nova schedule plugin fetch glance image metadata

Indeed, no REST API yet, but that's one of the things we will be considering for Gantt. I wonder if this is yet another argument for Gantt and, if you can wait until the Kilo cycle, maybe we can provide an appropriate service for Heat. -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D.

Re: [openstack-dev] Using gerrymander, a client API and command line tool for gerrit

This simple but effective tool went straight into my personal list of daily most used utilities since Daniel suggested it to me some weeks ago. I’m using it mostly on OS X and it works smoothly. Dan sorted out very quicly a couple of minor bugs that came up during initial testing. It proved to be

Re: [openstack-dev] [vmware] Canonical list of os types

On 08/14/2014 05:32 AM, Matthew Booth wrote: > I've just spent the best part of a day tracking down why instance > creation was failing on a particular setup. The error message from > CreateVM_Task was: 'A specified parameter was not correct'. > > After discounting a great many possibilities, I fi

[openstack-dev] [Cinder] 3'rd party CI systems: Not Whitelisted Volume type with name * could not be found.

Hi, Does anyone know how to configure cinder ci tests to not have these errors? 12:32:11 *** Not Whitelisted *** 2014-08-14 12:23:56.179 18021 ERROR cinder.volume.volume_types [req-c9ec92ab-132b-4167-a467-15bd213659e8 bd1f54a867ce47acb4097cd94149efa0 d15dcf4cb3c7495389799ec849e9036d - - -] Def

[openstack-dev] Using gerrymander, a client API and command line tool for gerrit

Over the past couple of months I've worked on creating a python library and command line tool for dealing with gerrit. I've blogged about this a number of times on http://planet.openstack.org, but I figure there are quite a few people who won't be reading the blogs there or easily miss some posts h

Re: [openstack-dev] [Ceilometer] Way to get wrapped method's name/class using Pecan secure decorators?

Sure, Doug. We want the ability to selectively apply policies to certain Ceilometer API methods based on user/tenant roles. For example, we want to restrict the ability to execute Alarm deletes to admins and user/tenants who have a special role, say "domainadmin". The policy file might look like

Re: [openstack-dev] [neutron] requirements.txt: explicit vs. implicit

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/14/2014 08:37 AM, Ihar Hrachyshka wrote: > Hi all, > > some plugins depend on modules that are not mentioned in > requirements.txt. Among them, Cisco Nexus (ncclient), Brocade > (ncclient), Embrane (heleosapi)... Some other plugins put their

Re: [openstack-dev] [OpenStack-Dev][Cinder] Cinder Core nomination

On 06:55 Thu 14 Aug , Boring, Walter wrote: > Hey guys, >I wanted to pose a nomination for Cinder core. > > Xing Yang. > She has been active in the cinder community for many releases and has worked > on several drivers as well as other features for cinder itself. She has > been doing a

Re: [openstack-dev] [all] The future of the integrated release

On Aug 13, 2014, at 5:07 AM, Daniel P. Berrange wrote: > On Wed, Aug 13, 2014 at 12:55:48PM +0100, Steven Hardy wrote: >> On Wed, Aug 13, 2014 at 11:42:52AM +0100, Daniel P. Berrange wrote: >>> On Thu, Aug 07, 2014 at 03:56:04AM -0700, Jay Pipes wrote: >>> By ignoring stable branches, leaving it

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On 08/14/2014 11:40 AM, David Kranz wrote: > On 08/14/2014 10:54 AM, Matt Riedemann wrote: >> >> >> On 8/14/2014 3:47 AM, Daniel P. Berrange wrote: >>> On Thu, Aug 14, 2014 at 09:24:36AM +1000, Michael Still wrote: On Thu, Aug 14, 2014 at 3:09 AM, Dan Smith wrote: >> I'm not questioning t

Re: [openstack-dev] [Ironic] [Infra] [QA] Devstack and Testing for ironic-python-agent``

Hi friends, The two devstack patches mentioned below have had the latest patchset up for a week now, and still only have one +2 on them. The other patches (and the ultimate goal of getting CI running on this driver) are blocked these patches. Could a devstack core please review these soon? Than

Re: [openstack-dev] [infra] Gerrit downtime on August 16 for project renames

Adding Kite move from stack forge to openstack org: stackforge/kite -> openstack/kite stackforge/python-kiteclient -> openstack/python-kiteclient On Thu, Aug 14, 2014 at 1:25 AM, Sergey Lukjanov wrote: > Hi, > > On Saturday, August 16 at 16:00 UTC Gerrit will be unavailable for > about 20 minute

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On 08/14/2014 10:54 AM, Matt Riedemann wrote: On 8/14/2014 3:47 AM, Daniel P. Berrange wrote: On Thu, Aug 14, 2014 at 09:24:36AM +1000, Michael Still wrote: On Thu, Aug 14, 2014 at 3:09 AM, Dan Smith wrote: I'm not questioning the value of f2f - I'm questioning the idea of doing f2f meeting

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Thu, Aug 14, 2014 at 10:31 AM, CARVER, PAUL wrote: > Russell Bryant [mailto:rbry...@redhat.com] wrote: > >>An ideal solution would allow attendees to join as individuals from >>anywhere. A lot of contributors work from home. Is that sort of thing >>compatible with your system? > > In principl

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Thu, Aug 14, 2014 at 10:30:59AM -0500, Kyle Mestery wrote: > On Thu, Aug 14, 2014 at 10:13 AM, Sandy Walsh > wrote: > > On 8/14/2014 11:28 AM, Russell Bryant wrote: > >> On 08/14/2014 10:04 AM, CARVER, PAUL wrote: > >>> Daniel P. Berrange [mailto:berra...@redhat.com] wrote: > >>> > Depend

Re: [openstack-dev] [nova][core] Expectations of core reviewers

Russell Bryant [mailto:rbry...@redhat.com] wrote: >An ideal solution would allow attendees to join as individuals from >anywhere. A lot of contributors work from home. Is that sort of thing >compatible with your system? In principle, yes, but that loses the immersive telepresence aspect which i

Re: [openstack-dev] [OpenStack-Dev][Cinder] Cinder Core nomination

+1, Xing is very active in the community, provides valuable reviews and currently developing cinder core features. ~Kurt -Original Message- From: Boring, Walter Sent: Wednesday, August 13, 2014 11:56 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [OpenStack-Dev][Cin

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Thu, Aug 14, 2014 at 10:13 AM, Sandy Walsh wrote: > On 8/14/2014 11:28 AM, Russell Bryant wrote: >> On 08/14/2014 10:04 AM, CARVER, PAUL wrote: >>> Daniel P. Berrange [mailto:berra...@redhat.com] wrote: >>> Depending on the usage needs, I think Google hangouts is a quite useful techno

[openstack-dev] [neutron] [third-party] What tests are required to be run

Folks, I'm not sure if all CI accounts are running sufficient tests. Per the requirements wiki page here [1], everyone needs to be running more than just Tempest API tests, which I still see most neutron third-party CI setups doing. I'd like to ask everyone who operates a third-party CI account for

Re: [openstack-dev] [sahara] new client release (0.7.1)

There are no additional proposals and, so, I'll push tag to client later today. Target commit is https://github.com/openstack/python-saharaclient/commit/1625d6851efbb3545b5915b4a87ef4948e405534 On Mon, Aug 11, 2014 at 5:37 PM, Sergey Lukjanov wrote: > Hey sahara folks, > > the latest sahara clien

[openstack-dev] [sahara] team meeting Aug 14 1800 UTC

Hi folks, We'll be having the Sahara team meeting as usual in #openstack-meeting-alt channel. Agenda: https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meeting&iso=20140814T18 -- Sincerely yours, Sergey Lukjanov

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Thu, Aug 14, 2014 at 10:13 AM, Sandy Walsh wrote: > On 8/14/2014 11:28 AM, Russell Bryant wrote: > > On 08/14/2014 10:04 AM, CARVER, PAUL wrote: > >> Daniel P. Berrange [mailto:berra...@redhat.com] wrote: > >> > >>> Depending on the usage needs, I think Google hangouts is a quite useful > >>>

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On 8/14/2014 11:28 AM, Russell Bryant wrote: > On 08/14/2014 10:04 AM, CARVER, PAUL wrote: >> Daniel P. Berrange [mailto:berra...@redhat.com] wrote: >> >>> Depending on the usage needs, I think Google hangouts is a quite useful >>> technology. For many-to-many session its limit of 10 participants c

Re: [openstack-dev] use of compute node as a storage

You run cinder-volume on compute node which you want to convert to storage. Configure LVM driver of compute node as storage backend for cinder-volume. On Fri, Aug 8, 2014 at 1:54 PM, shailendra acharya < acharyashailend...@gmail.com> wrote: > i made 4 vm 1 controller, 1 network and 2 compute and

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On 8/14/2014 3:47 AM, Daniel P. Berrange wrote: On Thu, Aug 14, 2014 at 09:24:36AM +1000, Michael Still wrote: On Thu, Aug 14, 2014 at 3:09 AM, Dan Smith wrote: I'm not questioning the value of f2f - I'm questioning the idea of doing f2f meetings sooo many times a year. OpenStack is very muc

Re: [openstack-dev] [Neutron] Simple proposal for stabilizing new features in-tree

Hi Wuhongning: Yes u are correct – this is phase 1 to at least get basic perimeter firewall support working with DVR before looking for an optimal way to address E – W traffic. Thanks Sridar From: Wuhongning mailto:wuhongn...@huawei.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.o

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On 08/14/2014 10:04 AM, CARVER, PAUL wrote: > Daniel P. Berrange [mailto:berra...@redhat.com] wrote: > >> Depending on the usage needs, I think Google hangouts is a quite useful >> technology. For many-to-many session its limit of 10 participants can be >> an issue, but for a few-to-many broadcast

Re: [openstack-dev] [OpenStack-Dev][Cinder] Cinder Core nomination

+1 On 14 August 2014 00:55, Boring, Walter wrote: > Hey guys, >I wanted to pose a nomination for Cinder core. > > Xing Yang. > She has been active in the cinder community for many releases and has worked > on several drivers as well as other features for cinder itself. She has > been doin

Re: [openstack-dev] [nova][core] Expectations of core reviewers

Daniel P. Berrange [mailto:berra...@redhat.com] wrote: >Depending on the usage needs, I think Google hangouts is a quite useful >technology. For many-to-many session its limit of 10 participants can be >an issue, but for a few-to-many broadcast it could be practical. What I >find particularly appe

Re: [openstack-dev] [Devstack] [Cinder] Registering 3rd party driver as default

Thanks a lot. This worked out like a charm. Regards, Amit *CloudByte Inc.* On Thu, Aug 14, 2014 at 7:02 PM, Kerr, Andrew wrote: > You either need to comment out the enabled_backends line, or you'll want > to put something similar to this in your cinder.conf file: >

Re: [openstack-dev] [heat] heat docker multi host scheduling support

On 14/08/14 03:21, Malawade, Abhijeet wrote: Hi all, I am trying to use heat to create docker containers. I have configured heat-docker plugin. I am also able to create stack using heat successfully. To start container on different host we need to provide 'docker_endpoint' in template. For th

Re: [openstack-dev] [all] The future of the integrated release

On 08/14/2014 09:21 AM, Devananda van der Veen wrote: > > On Aug 14, 2014 2:04 AM, "Eoghan Glynn" > wrote: >> >> >> > >> Letting the industry field-test a project and feed their experience >> > >> back into the community is a slow process, but that is the best >> > >> me

[openstack-dev] [neutron] requirements.txt: explicit vs. implicit

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi all, some plugins depend on modules that are not mentioned in requirements.txt. Among them, Cisco Nexus (ncclient), Brocade (ncclient), Embrane (heleosapi)... Some other plugins put their dependencies in requirements.txt though (like Arista depen

Re: [openstack-dev] [Neutron][DevStack] How to increase developer usage of Neutron

Mike Spreitzer [mailto:mspre...@us.ibm.com] wrote: >I'll bet I am not the only developer who is not highly competent with >bridges and tunnels, Open VSwitch, Neutron configuration, and how DevStack >transmutes all those. My bet is that you would have more developers using >Neutron if there were a

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On 08/14/2014 09:14 AM, Daniel P. Berrange wrote: > On Thu, Aug 14, 2014 at 08:31:48AM -0400, Russell Bryant wrote: >> On 08/13/2014 11:31 PM, Michael Still wrote: >>> On Thu, Aug 14, 2014 at 1:24 PM, Jay Pipes wrote: >>> Just wanted to quickly weigh in with my thoughts on this important topi

Re: [openstack-dev] [Devstack] [Cinder] Registering 3rd party driver as default

You either need to comment out the enabled_backends line, or you'll want to put something similar to this in your cinder.conf file: [DEFAULT] ... enabled_backends = cloudbyte ... [cloudbyte] volume_driver = volume_driver = cinder.volume.drivers.cloudbyte.cloudbyte.ElasticenterISCSIDriver SAN_IP=20

[openstack-dev] [Neutron][DevStack] How to increase developer usage of Neutron

I'll bet I am not the only developer who is not highly competent with bridges and tunnels, Open VSwitch, Neutron configuration, and how DevStack transmutes all those. My bet is that you would have more developers using Neutron if there were an easy-to-find and easy-to-follow recipe to use, to

Re: [openstack-dev] [all] The future of the integrated release

On Aug 14, 2014 2:04 AM, "Eoghan Glynn" wrote: > > > > >> Letting the industry field-test a project and feed their experience > > >> back into the community is a slow process, but that is the best > > >> measure of a project's success. I seem to recall this being an > > >> implicit expectation a f

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Thu, Aug 14, 2014 at 08:31:48AM -0400, Russell Bryant wrote: > On 08/13/2014 11:31 PM, Michael Still wrote: > > On Thu, Aug 14, 2014 at 1:24 PM, Jay Pipes wrote: > > > >> Just wanted to quickly weigh in with my thoughts on this important topic. I > >> very much valued the face-to-face interact

Re: [openstack-dev] [neutron][ml2] Mech driver as out-of-tree add-on

I also feel like the drivers/plugins are currently BEYOND a tipping point, and are in fact dragging down velocity of the core project in many ways. I'm working on a proposal for Kilo where we move all drivers/plugins out of the main Neutron tree and into a separate git repository under the networki

Re: [openstack-dev] Annoucing CloudKitty : an OpenSource Rating-as-a-Service project for OpenStack

Sounds very interesting. We're currently collecting detailed (and verified) usage information in StackTach and are keen to see what CloudKitty is able to offer. My one wish is that you keep the components as small pip redistributables with low coupling to promote reuse with other projects. Many

[openstack-dev] [OpenStack][Docker] Run OpenStack Service in Docker Container

I see a few mentions of OpenStack services themselves being containerized in Docker. Is this a serious trend in the community? http://allthingsopen.com/2014/02/12/why-containers-for-openstack-services/ -- Thanks, Jay ___ OpenStack-dev mailing list Ope

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On 08/13/2014 07:27 PM, Michael Still wrote: > The etherpad for the meetup has extensive notes. Any summary I write > will basically be those notes in prose. What are you looking for in a > summary that isn't in the etherpad? There also wasn't a summary of the > Icehouse midcycle produced that I ca

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On 08/13/2014 11:31 PM, Michael Still wrote: > On Thu, Aug 14, 2014 at 1:24 PM, Jay Pipes wrote: > >> Just wanted to quickly weigh in with my thoughts on this important topic. I >> very much valued the face-to-face interaction that came from the mid-cycle >> meetup in Beaverton (it was the only o

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On 08/13/2014 07:27 PM, Michael Still wrote: > On Thu, Aug 14, 2014 at 3:44 AM, Russell Bryant wrote: >> On 08/13/2014 01:09 PM, Dan Smith wrote: >>> Expecting cores to be at these sorts of things seems pretty reasonable >>> to me, given the usefulness (and gravity) of the discussions we've been >

Re: [openstack-dev] [neutron][cisco] Cisco Nexus requires patched ncclient

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 FYI: I've uploaded a review for openstack/requirements to add the upstream module into the list of potential dependencies [1]. Once it's merged, I'm going to introduce this new requirement for Neutron. [1]: https://review.openstack.org/114213 /Ihar

Re: [openstack-dev] [vmware] Canonical list of os types

- Original Message - > From: "Matthew Booth" > To: "OpenStack Development Mailing List (not for usage questions)" > > > I've just spent the best part of a day tracking down why instance > creation was failing on a particular setup. The error message from > CreateVM_Task was: 'A specifie

Re: [openstack-dev] [Devstack] [Cinder] Registering 3rd party driver as default

With further debugging, i find that none of the configuration options present in /etc/cinder/cinder.conf are getting applied. Regards, Amit *CloudByte Inc.* On Thu, Aug 14, 2014 at 11:40 AM, Amit Das wrote: > Hi folks, > > I have been trying to run devstack with my

[openstack-dev] [vmware] Canonical list of os types

I've just spent the best part of a day tracking down why instance creation was failing on a particular setup. The error message from CreateVM_Task was: 'A specified parameter was not correct'. After discounting a great many possibilities, I finally discovered that the problem was guestId, which wa

Re: [openstack-dev] Annoucing CloudKitty : an OpenSource Rating-as-a-Service project for OpenStack

Glad to see there is another group interested in rating/billing. I'm thinking if I should announce our rating service to join the fun :-) You know, I'm kidding. The more groups join the rating service discussion, the better. But IMHO, we just need one rating service for OpenStack. So let's coll

Re: [openstack-dev] [OpenStack-Infra] [infra] Third Party CI naming and contact (action required)

Hi Franck - Thanks for the update. I too have that re-order in mind. :) Here after CI owners may add their CI names in appropriate alphabetical order. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Franck Yelles [mailto:franck...@gmail.

Re: [openstack-dev] [nova] Retrospective veto revert policy

On Tue, 2014-08-12 at 15:56 +0100, Mark McLoughlin wrote: > Hey > > (Terrible name for a policy, I know) > > From the version_cap saga here: > > https://review.openstack.org/110754 > > I think we need a better understanding of how to approach situations > like this. > > Here's my attempt at

Re: [openstack-dev] [neutron][ml2] Mech driver as out-of-tree add-on

I think there will soon be a discussion regarding what the appropriate location for plugin and drivers should be. My personal feeling is that Neutron has simply reached the tipping point where the high number of drivers and plugins is causing unnecessary load for the core team and frustration for t

Re: [openstack-dev] [ceilometer] gate-ceilometer-python33 failed because of wrong setup.py in happybase

Hisashi Osanai, np :) You're welcome :) On Thu, Aug 14, 2014 at 5:13 AM, Osanai, Hisashi < osanai.hisa...@jp.fujitsu.com> wrote: > > On Wed, Aug 13, 2014 at 2:35 PM, Julien Danjou wrote: > >> Means the py33 needs to execute on stable/icehouse. Here I > misunderstand something... > > Not it does

Re: [openstack-dev] [OpenStack-Infra] [infra] Third Party CI naming and contact (action required)

Hi James, I have added the Nuage CI system to the list; I also took the liberty to reorder alphabetically the list Franck Franck On Wed, Aug 13, 2014 at 11:23 AM, James E. Blair wrote: > Hi, > > We've updated the registration requirements for third-party CI systems > here: > > http://ci.open

[openstack-dev] [Congress] Help in understanding API Flow

Hi, Can some one help me understand how an API is exposed to the clients from Congress server ? I see that a cage service ('api-policy') is created in congress_server.py. I believe this is implemented in policy_model. I tried to send a json_request from my client on the server. I tried sending "

  1   2   >