Re: [openstack-dev] [Ironic] review days

> What time would work for you? How about Thursdays at 8am PST? Works for me! Ghe Rivero ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Interested in attracting new contributors?

Hello, I would like to explain my experience like a newbie in OpenStack due to be one of this people who used OpenHatch to contribute an opensource project. I won't talk about the quality or clarity of the documentation (true that are a lot and maybe some can improve) but about all the importance

Re: [openstack-dev] [Neutron] Interest in discussing vendor plugins for L3 services?

I'm interested in the discussion. UTC-8. Gary On Wed, Feb 12, 2014 at 10:22 AM, Mandeep Dhami wrote: > > I would be interested as well (UTC-8). > > Regards, > Mandeep > > > > On Wed, Feb 12, 2014 at 8:18 AM, Eugene Nikanorov > wrote: > >> I'd be interested too. >> >> Thanks, >> Eugene. >> >> >

[openstack-dev] multiple external networks not working

I have a multiple external networks environment: | 6fd43d02-221a-44fe-8088-dc5915512c14 | Ext-Net-2 | 1a530334-9dd7-45f3-aa6a-2bb1a5dad562 192.168.1.0/24 | | a2946b29-6be5-4285-9eb9-99625ec2a283 |Ext-Net | dfbc7f6c-c3dd-4c56-a142-48964e2e474c 192.168.2.0/24 | Each of the external ne

Re: [openstack-dev] Gamification and on-boarding ...

I am new to open stack and python. But I really liked the live community here and great suggestions that crop up. This one is seriously good and helps new people stay motivated. I installed dev stack on my sluggish laptop and that's all. Could not move any further. Looking forward to taking the nex

[openstack-dev] [Cinder] How to run pylint locally?

I have a quick question on how to run the cinder-gate-pylint locally. I am trying to reproduce the pylint errors reported by the gate pylint build here (https://review.openstack.org/#/c/62217/) locally. Here is what I tried: /opt/stack/cinder $ ./tools/lintstack.sh But this does not report any er

Re: [openstack-dev] Gamification and on-boarding ...

+1. This looks very interesting. :) On Thu, Feb 13, 2014 at 2:09 PM, Russell Bryant wrote: > On 02/12/2014 11:35 AM, Ben Nemec wrote: > > On 2014-02-12 12:00, Sandy Walsh wrote: > >> At the Nova mid-cycle meetup we've been talking about the problem of > >> helping new contributors. It got into

Re: [openstack-dev] Gamification and on-boarding ...

On 02/12/2014 11:35 AM, Ben Nemec wrote: > On 2014-02-12 12:00, Sandy Walsh wrote: >> At the Nova mid-cycle meetup we've been talking about the problem of >> helping new contributors. It got into a discussion of karma, code >> reviews, bug fixes and establishing a name for yourself before >> scream

Re: [openstack-dev] [Solum] Question about Zuul's role in Solum

On Wed, Feb 12, 2014 at 7:25 PM, Noorul Islam K M wrote: > "devdatta kulkarni" writes: > >> Hi, >> >> I have been looking at Zuul for last few days and had a question >> about its intended role within Solum. >> >> From what I understand, Zuul is a code gating system. >> >> I have been wondering i

Re: [openstack-dev] [Solum] Question about Zuul's role in Solum

> On Feb 12, 2014, at 5:45 PM, "Angus Salkeld" > wrote: > > Excuse top post (web mail :() > > Can't we change our proposed workflow to match what Gerrit/Zuul are > doing? So endorse the gating workflow as "the official solum workflow". That's my preference so far. > Pros: > - we just use the

Re: [openstack-dev] [All]Optional dependencies and requirements.txt

Interesting, is that supported in pbr (since this is whats being used in this situation at least for requirements). -Original Message- From: David Koo Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, February 12, 2014 at 7:35 PM To: "openstack-dev

[openstack-dev] [Neutron] ARP Proxy in l2-population Mechanism Driver for OVS

Hi all, I'm running a OpenStack Havana cloud on pre-production stage using Neutron ML2 VxLAN. I'd like to incorporate l2-population to get rid of tunnel broadcast. However, it seems that ARP Proxy has NOT been implemented yet for Open vSwitch for Havana and also the latest master branch. I find

Re: [openstack-dev] [All]Optional dependencies and requirements.txt

> Most of the reason for the #2 there is for plugins that taskflow can > use (but which are not required for all users). Ideally there would be > more dynamic way to list requirements of libraries and projects, one > that actually changes depends on the features used/desired to be used. Disclaime

Re: [openstack-dev] [Nova] modify_image_attribute() in ec2_api is broken in Nova

Hi Vish, thanks for your reply. I've already registered it on launchpad: https://bugs.launchpad.net/nova/+bug/1272844 Thanks~ On Thu, Feb 13, 2014 at 2:18 AM, Vishvananda Ishaya wrote: > This looks like a bug to me. It would be great if you could report it on > launchpad. > > Vish > > On Feb

Re: [openstack-dev] [Solum] Question about Zuul's role in Solum

"devdatta kulkarni" writes: > Hi, > > I have been looking at Zuul for last few days and had a question > about its intended role within Solum. > > From what I understand, Zuul is a code gating system. > > I have been wondering if code gating is something we are considering as a > feature > to be

Re: [openstack-dev] [All]Optional dependencies and requirements.txt

In taskflow we've done something like the following. Its not perfect, but it is what currently works (willing to take suggestions on better). We have three different requirements files. 1. Required to work in any manner @ https://github.com/openstack/taskflow/blob/master/requirements.txt 2. Op

Re: [openstack-dev] [openstack-qa] Unit Tests for Cinder and Swift

Hi Oscar, I'm sorry for my delayed reply. I think this is a development topic. I added openstack-dev ML to CC this time. Actually, I'm not familiar with Swift unit tests. So I just CCed and I'm expecting answers from Swift people. -- Masayuki Igawa Thank you Masayuki for everything. I woud like

[openstack-dev] [Neutron][nova] Neutron plugin authors: Does port status indicate liveness?

Booting a Nova instance when Neutron is enabled is often unreliable due to the lack of coordination between Nova and Neutron apart from port allocation. Aaron Rosen and I have been talking about fixing this by having Nova perform a check for port 'liveness' after vif plug and before vm boot. T

Re: [openstack-dev] [Ironic] review days

On Wed, Feb 12, 2014 at 2:18 PM, Maksym Lobur wrote: > Also, I think 3 hours might be too much > I'm happy to start with 2 hours and see how it goes. On Wed, Feb 12, 2014 at 2:35 PM, Roman Prykhodchenko < rprikhodche...@mirantis.com> wrote: > Since there are two core-subteams located in differ

Re: [openstack-dev] [Neutron][LBaaS] Proposal for model change - Logging configuration

Hi Roger and Sam! Sam-- Could you please alter the permissions on that google doc so that people can add comments (at least)? Right now, it appears I have a read-only view. Roger: What you're describing seems to me like it isn't something that would apply to ceilometer integration so much as lo

[openstack-dev] [OpenStack][Nova][VCDriver] VMWare VCDriver problems

Greetings, I was now doing some integration with VMWare VCDriver and have some questions during the integration work. 1) In Hong Kong Summit, it was mentioned that ESXDriver will be dropped, so do we have any plan when to drop this driver? 2) There are many good features in VMWare was not support

Re: [openstack-dev] [Solum] Question about Zuul's role in Solum

Excuse top post (web mail :() Can't we change our proposed workflow to match what Gerrit/Zuul are doing? So endorse the gating workflow as "the official solum workflow". Pros: - we just use the current Gerrit/Zuul as-is. - great gating system for little effort - lots of people already helping mai

Re: [openstack-dev] [Neutron][LBaaS] Proposal for model change - Loadbalancer Instance feedback

Hi y'all! I've been reading through the LoadBalancerInsance description as outlined here and have some feedback: https://wiki.openstack.org/wiki/Neutron/LBaaS/LoadbalancerInstance First off, I agree that we need a container object and that the pool shouldn't be the object root. This container obj

Re: [openstack-dev] [All]Optional dependencies and requirements.txt

On Wed, Feb 12, 2014 at 4:22 PM, David Koo wrote: > > If we're going to have more than one requirement file then may I propose > something like a requirements.d directory and putting the files in that > directory (and no need for a -requirements suffix)? > > requirements.d/ > global >

Re: [openstack-dev] healthnmon and devstack

On Wed, Feb 12, 2014 at 6:13 PM, Paulo Rômulo wrote: > My name is Paulo, I'm a software engineer from Brazil and just getting > started with OpenStack development using *devstack*. I'm working on a > project which one the goals is to monitor resource usage (at first > *cpu_util*), considering bot

Re: [openstack-dev] [All]Optional dependencies and requirements.txt

> We could use a separate requirements file for each driver, following a naming > convention to let installation tools pick up the right file. For example, > oslo.messaging might include amqp-requirements.txt, qpid-requirements.txt, > zmq-requirements.txt, etc. If we're going to have more than o

Re: [openstack-dev] [Solum] Question about Zuul's role in Solum

Paul, On Feb 12, 2014, at 3:44 PM, Paul Czarkowski wrote: > > > On 2/12/14 5:16 PM, "Roshan Agrawal" wrote: > >> >>> -Original Message- >>> From: devdatta kulkarni [mailto:devdatta.kulka...@rackspace.com] >>> Sent: Wednesday, February 12, 2014 3:26 PM >>> To: OpenStack Development

[openstack-dev] healthnmon and devstack

Hello everyone, My name is Paulo, I'm a software engineer from Brazil and just getting started with OpenStack development using *devstack*. I'm working on a project which one the goals is to monitor resource usage (at first *cpu_util*), considering both VM instances and their hosts. In order to g

Re: [openstack-dev] [Neutron][LBaaS] Proposal for model change - Multiple services per floating IP

Hello! This e-mail is concerning the "Multiple load balanced services per floating IP" feature: Sam, I think you said: On Tue, Feb 11, 2014 at 5:26 AM, Samuel Bercovici wrote: > > · Multiple load balanced services per floating IP - You can > already multiple VIPs using the same IP

Re: [openstack-dev] [Solum] Question about Zuul's role in Solum

Dev, Thanks for raising this discussion. This is an important decision point for us. On Feb 12, 2014, at 1:25 PM, devdatta kulkarni wrote: > Hi, > > I have been looking at Zuul for last few days and had a question > about its intended role within Solum. > > From what I understand, Zuul is a

Re: [openstack-dev] [Solum] Question about Zuul's role in Solum

On 2/12/14 5:16 PM, "Roshan Agrawal" wrote: > >> -Original Message- >> From: devdatta kulkarni [mailto:devdatta.kulka...@rackspace.com] >> Sent: Wednesday, February 12, 2014 3:26 PM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: [openstack-dev] [Solum] Q

[openstack-dev] [OpenStack-Dev] [Cinder] Cinder driver verification

Hey, So we've talked about this a bit and had a number of ideas regarding how to test and show compatibility for third-party drivers in Cinder. This has been an eye opening experience (the number of folks that have NEVER run tempest before, as well as the problems uncovered now that they're trying

Re: [openstack-dev] [qa][tempest][rally] Rally & Tempest integration: tempest.conf autogeneration

On 02/12/2014 05:55 PM, Sean Dague wrote: On 02/12/2014 05:08 PM, Boris Pavlovic wrote: Hi all, It goes without saying words that actually tempest[1] is only one public known tool that could fully verify deployments and ensure dthat they work. In Rally[2] we would like to use it as a cloud ver

Re: [openstack-dev] [Ironic] review days

Roman: *Since there are two core-subteams located in different time zones I propose making two sessions:* *- One in the morning in Europe. Let's say at 10 GMT* *- One in the morning in the US at a convenient time.* I like this but it might be confusing to the devs, at least initially. I wo

Re: [openstack-dev] [Solum] Question about Zuul's role in Solum

> -Original Message- > From: devdatta kulkarni [mailto:devdatta.kulka...@rackspace.com] > Sent: Wednesday, February 12, 2014 3:26 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] [Solum] Question about Zuul's role in Solum > > Hi, > > I hav

Re: [openstack-dev] [qa][tempest][rally] Rally & Tempest integration: tempest.conf autogeneration

On 02/12/2014 05:08 PM, Boris Pavlovic wrote: > Hi all, > > It goes without saying words that actually tempest[1] is only one public > known tool that could fully verify deployments and ensure dthat they work. > > In Rally[2] we would like to use it as a cloud verifier (before > benchmarking it

Re: [openstack-dev] [Neutron][LBaaS] Subteam meeting 13.02.2014 at 14-00UTC

Sounds good! I'll be sure to be there. Also, I'm going to shift my focus today to the analysis of the LoadBalancerInstance resource as I think my proposals actually have more to do with how that's implemented than L7 or SSL. Thanks, Stephen On Wed, Feb 12, 2014 at 2:15 PM, Eugene Nikanorov wrote

Re: [openstack-dev] [Ironic] review days

Since there are two core-subteams located in different time zones I propose making two sessions: - One in the morning in Europe. Let's say at 10 GMT - One in the morning in the US at a convenient time. This approach might be useful for the submitters located in different time zones. -

Re: [openstack-dev] [Ironic] review days

Also, I think 3 hours might be too much, maybe to have 2 sessions of 2 hours. It might be hard to concentrate on review for 3 hours in a line.. Best regards, Max Lobur, Python Developer, Mirantis, Inc. Mobile: +38 (093) 665 14 28 Skype: max_lobur 38, Lenina ave. Kharkov, Ukraine www.mirantis.com

Re: [openstack-dev] [qa][neutron] API tests in the Neutron tree

On Feb 12, 2014, at 1:59 PM, Sean Dague wrote: > On 02/12/2014 04:25 PM, Maru Newby wrote: >> >> On Feb 12, 2014, at 12:36 PM, Sean Dague wrote: >> >>> On 02/12/2014 01:48 PM, Maru Newby wrote: At the last 2 summits, I've suggested that API tests could be maintained in the Neutron

Re: [openstack-dev] [Ironic] review days

+1 > What time would work for you? How about Thursdays at 8am PST? > Works for me ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Neutron][LBaaS] Subteam meeting 13.02.2014 at 14-00UTC

Hi folks, Lets gather as usual on #openstack-meeting on Thursday, 13 at 14-00 UTC The updated agenda for our regular meeting is here: https://wiki.openstack.org/wiki/Network/LBaaS In addition to that I'd like to discuss some ideas that Stephen Balukoff has proposed. Thanks, Eugene. _

[openstack-dev] [qa][tempest][rally] Rally & Tempest integration: tempest.conf autogeneration

Hi all, It goes without saying words that actually tempest[1] is only one public known tool that could fully verify deployments and ensure dthat they work. In Rally[2] we would like to use it as a cloud verifier (before benchmarking it is actually very useful;) to ensure that cloud work). We are

Re: [openstack-dev] [qa][neutron] API tests in the Neutron tree

On 02/12/2014 04:25 PM, Maru Newby wrote: > > On Feb 12, 2014, at 12:36 PM, Sean Dague wrote: > >> On 02/12/2014 01:48 PM, Maru Newby wrote: >>> At the last 2 summits, I've suggested that API tests could be maintained in >>> the Neutron tree and reused by Tempest. I've finally submitted some

Re: [openstack-dev] [Neutron] Support for multiple provider networks with same VLAN segmentation id

Hi Vinay, On Tue, Feb 11, 2014 at 4:20 PM, Vinay Bannai wrote: > One way to look at the VLANs is that it identifies a security zone that > meets some regulatory compliance standards. The VLANs on each rack are > separated from other VLANs by using VRF. Tenants in our case map to > applications.

Re: [openstack-dev] [All]Optional dependencies and requirements.txt

On Wed, Feb 12, 2014 at 3:58 PM, Ben Nemec wrote: > Hi all, > > This is an issue that has come up recently in tripleo as we try to support > more varied configurations. Currently qpid-python is not listed in > requirements.txt for many of the OpenStack projects, even though they > support using

Re: [openstack-dev] Interested in attracting new contributors?

On Feb 12, 2014, at 12:41 PM, Ben Nemec wrote: > On 2014-02-12 13:48, Adrian Otto wrote: >> On Feb 12, 2014, at 10:13 AM, Ben Nemec >> wrote: >>> On 2014-02-12 09:51, Jesse Noller wrote: On Feb 12, 2014, at 8:30 AM, Julie Pichon wrote: > Hi folks, > Stefano's post on how to make

Re: [openstack-dev] [Ironic] review days

Hi All, I like the idea! I'm comfortable to reserve about 3 hours for this, Thursdays 8am (4pm GMT +0) sounds good. I assume we'll pick and merge as much patches as possible during that time, and if the last one doesn't fit to the time - we're increasing the time until the patch merged (in reasona

Re: [openstack-dev] [oslo] instructions for creating a new oslo library

On Wed, Feb 12, 2014 at 4:12 PM, Ben Nemec wrote: > On 2014-02-12 13:28, Doug Hellmann wrote: > > I have been working on instructions for creating new Oslo libraries, > either from scratch or by graduating code from the incubator. I would > appreciate any feedback about whether I have all of th

Re: [openstack-dev] [qa][neutron] API tests in the Neutron tree

On Feb 12, 2014, at 12:36 PM, Sean Dague wrote: > On 02/12/2014 01:48 PM, Maru Newby wrote: >> At the last 2 summits, I've suggested that API tests could be maintained in >> the Neutron tree and reused by Tempest. I've finally submitted some patches >> that demonstrate this concept: >> >> ht

[openstack-dev] [Solum] Question about Zuul's role in Solum

Hi, I have been looking at Zuul for last few days and had a question about its intended role within Solum. >From what I understand, Zuul is a code gating system. I have been wondering if code gating is something we are considering as a feature to be provided in Solum? If yes, then Zuul is a per

Re: [openstack-dev] [oslo] instructions for creating a new oslo library

On 2014-02-12 13:28, Doug Hellmann wrote: > I have been working on instructions for creating new Oslo libraries, either > from scratch or by graduating code from the incubator. I would appreciate any > feedback about whether I have all of the necessary details included in > https://wiki.ope

Re: [openstack-dev] [Ironic] review days

I think that's a nice idea. During the last two days using this approach we managed to find several problems in an important patch which is now waiting to be merged. I bet it would take much longer, if we didn't do that. How about picking a particular time every day for performing this kind of

[openstack-dev] [Ironic] review days

Hi again! I promise this will be a much shorter email than my last one ... :) I'd like to propose that we find regular day/time to have a recurring code jam. Here's what it looks like in my head: - we get at least three core reviewers together - as many non-core folks as show up are welcome, too

[openstack-dev] [All]Optional dependencies and requirements.txt

Hi all, This is an issue that has come up recently in tripleo as we try to support more varied configurations. Currently qpid-python is not listed in requirements.txt for many of the OpenStack projects, even though they support using Qpid as a messaging broker. This means that when we insta

[openstack-dev] [QA] Meeting Thursday February 13th at 17:00UTC

Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, February 13th at 17:00 UTC in the #openstack-meeting channel. The agenda for tomorrow's meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to add an item

[openstack-dev] [nova][network] Gateway in network_info seems not to be correct

Hi All, I'm currently trying out the docker in FlatDHCPManager multi_host mode. I figured out that my instance are not pingable. The reason for that is that they get the wrong gateway assigned. Currently we use the "gateway" field provided by the network_info object. That works great in a single

Re: [openstack-dev] Interested in attracting new contributors?

On 2014-02-12 13:48, Adrian Otto wrote: On Feb 12, 2014, at 10:13 AM, Ben Nemec wrote: On 2014-02-12 09:51, Jesse Noller wrote: On Feb 12, 2014, at 8:30 AM, Julie Pichon wrote: Hi folks, Stefano's post on how to make contributions to OpenStack easier [1] finally stirred me into writing abo

Re: [openstack-dev] Interested in attracting new contributors?

On Wed, Feb 12, 2014 at 8:30 AM, Julie Pichon wrote: > > I can definitely sympathise with the comment in Stefano's article that > there are not enough easy tasks / simple issues for newcomers. There's > a lot to learn already when you're starting out (git, gerrit, python, > devstack, ...) and sim

Re: [openstack-dev] [Neutron][LBaaS] Proposal for model change - Layer 7 support

Hi Stephen, See embedded response bellow. Regards, -Sam. From: Stephen Balukoff [mailto:sbaluk...@bluebox.net] Sent: Wednesday, February 12, 2014 8:46 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS] Proposal for mo

Re: [openstack-dev] [qa][neutron] API tests in the Neutron tree

On 02/12/2014 01:48 PM, Maru Newby wrote: > At the last 2 summits, I've suggested that API tests could be maintained in > the Neutron tree and reused by Tempest. I've finally submitted some patches > that demonstrate this concept: > > https://review.openstack.org/#/c/72585/ (implements a unit

Re: [openstack-dev] [Ironic] [TripleO] Goal setting // progress towards integration

On Wed Feb 12 14:40:27 2014, Devananda van der Veen wrote: > https://blueprints.launchpad.net/ironic/+spec/serial-console-access > I believe some folks are using this, even though the TripleO team is > not, and I personally never used the feature in Nova baremetal. > IBM contributed code to

Re: [openstack-dev] [Ironic] [TripleO] Goal setting // progress towards integration

On Wed, Feb 12, 2014 at 12:40 PM, Devananda van der Veen wrote: [snip] > Additionally, the TC has laid out some (draft) graduation requirements [2] > for projects that duplicate functionality in a pre-existing project -- that > means us, since we're supplanting the old Nova "baremetal" driver. F

[openstack-dev] help the oslo team help you

If you have a change in your project that is blocked waiting for a patch to land in oslo (in the incubator, or any of the libraries we manage) *please* either open a blueprint or mark the associated bug as also affecting the relevant oslo project, then let me know about it so I can put it on our re

Re: [openstack-dev] [QA] The future of nosetests with Tempest

On Wed, Feb 12, 2014 at 11:32:39AM -0700, Matt Riedemann wrote: > > > On 1/17/2014 8:34 AM, Matthew Treinish wrote: > >On Fri, Jan 17, 2014 at 08:32:19AM -0500, David Kranz wrote: > >>On 01/16/2014 10:56 PM, Matthew Treinish wrote: > >>>Hi everyone, > >>> > >>>With some recent changes made to Tem

Re: [openstack-dev] [oslo-incubator] update.py copies more modules than expected

I would vote for option #2 : move to oslo.messaging, that could be a quick win. 2014-02-12 20:34 GMT+01:00 Doug Hellmann : > The update script tries to be smart about the dependencies between > modules, based on cross-module imports. > > It looks like the notifier middleware will need to move ou

Re: [openstack-dev] [oslo-incubator] update.py copies more modules than expected

I think variant with using oslo.messaging is nice here - cause now it looks strange when openstack.common.middleware asks to use openstack.common.notifier.api - and that leads to two unused really dirs downloaded by update.py script. Anyway, we should go further and begin using oslo.messaging wher

Re: [openstack-dev] Interested in attracting new contributors?

On Feb 12, 2014, at 10:13 AM, Ben Nemec wrote: > On 2014-02-12 09:51, Jesse Noller wrote: >> On Feb 12, 2014, at 8:30 AM, Julie Pichon wrote: >>> Hi folks, >>> Stefano's post on how to make contributions to OpenStack easier [1] >>> finally stirred me into writing about something that vkmc and

[openstack-dev] [Ironic] [TripleO] Goal setting // progress towards integration

Hello ironic developers, tripleo folks, and interested third-parties! The Icehouse graduation deadline is fast approaching and I think we all need to take a good look at where Ironic is, compare that to the requirements that have been laid out by the TC [1] for all Integrated projects, and priorit

Re: [openstack-dev] [oslo-incubator] update.py copies more modules than expected

The update script tries to be smart about the dependencies between modules, based on cross-module imports. It looks like the notifier middleware will need to move out of the incubator, or be updated to use oslo.messaging or the rpc code from the incubator. Doug On Wed, Feb 12, 2014 at 2:23 PM,

[openstack-dev] [oslo] instructions for creating a new oslo library

I have been working on instructions for creating new Oslo libraries, either from scratch or by graduating code from the incubator. I would appreciate any feedback about whether I have all of the necessary details included in https://wiki.openstack.org/wiki/Oslo/CreatingANewLibrary Thanks, Doug ___

Re: [openstack-dev] [oslo-incubator] update.py copies more modules than expected

Cause it seems that such thing is not working: http://paste.openstack.org/show/64740/ It still downloads all directories for notifier and roc, although is only module=notifier.api in conf file. Thanks Dina On Wed, Feb 12, 2014 at 11:13 PM, Dina Belova wrote: > May we use smth like: > > module=

Re: [openstack-dev] [oslo-incubator] update.py copies more modules than expected

May we use smth like: module=notifier.api only to copy needed for middleware notifier? On Wed, Feb 12, 2014 at 10:55 PM, Chris Buccella < bucce...@linux.vnet.ibm.com> wrote: > On 02/12/2014 11:50 AM, Sanchez, Cristian A wrote: > >> Hi, >> We've modified the openstack-commons.conf file for clim

Re: [openstack-dev] [oslo-incubator] update.py copies more modules than expected

On 02/12/2014 11:50 AM, Sanchez, Cristian A wrote: Hi, We’ve modified the openstack-commons.conf file for climate remove rpc and notifier modules. But when the update.py is executed, the notifier and rpc modules are still copied. Do you know what could be wrong? Here you can see a log showing

[openstack-dev] [qa][neutron] API tests in the Neutron tree

At the last 2 summits, I've suggested that API tests could be maintained in the Neutron tree and reused by Tempest. I've finally submitted some patches that demonstrate this concept: https://review.openstack.org/#/c/72585/ (implements a unit test for the lifecycle of the network resource) htt

Re: [openstack-dev] [Neutron][LBaaS] Proposal for model change - Layer 7 support

Howdy, Sam! Thanks also for your speedy response. Comments / additional questions are in-line below: On Wed, Feb 12, 2014 at 2:51 AM, Samuel Bercovici wrote: > We have reviewed this based on capabilities that we belive could > be supported by HA proxy and all commercial vendors. > > What is

Re: [openstack-dev] Gamification and on-boarding ...

On 2014-02-12 12:00, Sandy Walsh wrote: At the Nova mid-cycle meetup we've been talking about the problem of helping new contributors. It got into a discussion of karma, code reviews, bug fixes and establishing a name for yourself before screaming in a chat room "can someone look at my branch". W

Re: [openstack-dev] [QA] The future of nosetests with Tempest

On 1/17/2014 8:34 AM, Matthew Treinish wrote: On Fri, Jan 17, 2014 at 08:32:19AM -0500, David Kranz wrote: On 01/16/2014 10:56 PM, Matthew Treinish wrote: Hi everyone, With some recent changes made to Tempest compatibility with nosetests is going away. We've started using newer features that

Re: [openstack-dev] [Nova] modify_image_attribute() in ec2_api is broken in Nova

This looks like a bug to me. It would be great if you could report it on launchpad. Vish On Feb 11, 2014, at 7:49 PM, wu jiang wrote: > Hi all, > > I met some problems when testing an ec2_api:'modify_image_attribute()' in > Nova. > I found the params send to Nova, are not suitable to match i

Re: [openstack-dev] [Nova] Putting nova-network support into the V3 API

Hi Chris, Thanks for your info, I got it. That is a quick response and enough for me:-) Thanks Ken'ichi Ohmichi --- 2014-02-13 Christopher Yeoh : > Hi Kenichi, > > Ah yes, it was decided at the mid cycle meetup to delay the nova network > changes > until Juno. Sorry I should have told you soone

Re: [openstack-dev] [Neutron] Interest in discussing vendor plugins for L3 services?

I would be interested as well (UTC-8). Regards, Mandeep On Wed, Feb 12, 2014 at 8:18 AM, Eugene Nikanorov wrote: > I'd be interested too. > > Thanks, > Eugene. > > > On Wed, Feb 12, 2014 at 7:51 PM, Carl Baldwin wrote: > >> Paul, >> >> I'm interesting in joining the discussion. UTC-7. Any w

Re: [openstack-dev] [Neutron] Group Policy questions

Hi Carlos, On Wed, Feb 12, 2014 at 9:37 AM, Carlos Gonçalves wrote: > Hi, > > I've a couple of questions regarding the ongoing work on Neutron Group > Policy proposed in [1]. > > 1. One of the described actions is redirection to a service chain. How do > you see BPs [2] and [3] addressing servic

Re: [openstack-dev] Interested in attracting new contributors?

On 2014-02-12 09:51, Jesse Noller wrote: On Feb 12, 2014, at 8:30 AM, Julie Pichon wrote: Hi folks, Stefano's post on how to make contributions to OpenStack easier [1] finally stirred me into writing about something that vkmc and myself have been doing on the side for a few months to help new

Re: [openstack-dev] Gamification and on-boarding ...

I¹m kind of new in Openstack. +1 to this On 12/02/14 15:00, "Sandy Walsh" wrote: >At the Nova mid-cycle meetup we've been talking about the problem of >helping new contributors. It got into a discussion of karma, code >reviews, bug fixes and establishing a name for yourself before screaming >i

Re: [openstack-dev] [python-openstacksdk] First meeting scheduled

On Wed, Feb 12, 2014 at 10:36 AM, Matthew Farina wrote: > I would like to point out that the unified SDK has a different target > audience from the existing clients. Application developers who want to work > with OpenStack APIs are far different from those who are trying to build > OpenStack. The

[openstack-dev] Gamification and on-boarding ...

At the Nova mid-cycle meetup we've been talking about the problem of helping new contributors. It got into a discussion of karma, code reviews, bug fixes and establishing a name for yourself before screaming in a chat room "can someone look at my branch". We want this experience to be positive,

Re: [openstack-dev] [Heat] [TripleO] in-instance update hooks

Excerpts from James Slagle's message of 2014-02-12 05:18:31 -0800: > On Tue, Feb 11, 2014 at 12:22 AM, Clint Byrum wrote: > > Hi, so in the previous thread about rolling updates it became clear that > > having in-instance control over updates is a more fundamental idea than > > I had previously be

[openstack-dev] [Neutron] Group Policy questions

Hi, I’ve a couple of questions regarding the ongoing work on Neutron Group Policy proposed in [1]. 1. One of the described actions is redirection to a service chain. How do you see BPs [2] and [3] addressing service chaining? Will this BP implement its own service chaining mechanism enforcing

Re: [openstack-dev] [python-openstacksdk] First meeting scheduled

I would like to point out that the unified SDK has a different target audience from the existing clients. Application developers who want to work with OpenStack APIs are far different from those who are trying to build OpenStack. For example, application developers don't know what keystone, nova,

Re: [openstack-dev] [Nova][Neutron] Neutron network in Nova V3 API

On 2014?02?12? 17:15, Alex Xu wrote: Hi, guys, I'm working neutron network stuff in nova V3 API. We will only pass port ids when create server, and Nova won't proxy any neutron call in the future. I plan to add new v3 network extension, that only accept port ids as parameters. And it will pass

[openstack-dev] [oslo-incubator] update.py copies more modules than expected

Hi, We’ve modified the openstack-commons.conf file for climate remove rpc and notifier modules. But when the update.py is executed, the notifier and rpc modules are still copied. Do you know what could be wrong? Here you can see a log showing this situation: http://paste.openstack.org/show/6467

Re: [openstack-dev] [Neutron] Interest in discussing vendor plugins for L3 services?

I'd be interested too. Thanks, Eugene. On Wed, Feb 12, 2014 at 7:51 PM, Carl Baldwin wrote: > Paul, > > I'm interesting in joining the discussion. UTC-7. Any word on when > this will take place? > > Carl > > On Mon, Feb 3, 2014 at 3:19 PM, Paul Michali wrote: > > I'd like to see if there is

Re: [openstack-dev] [Nova] Putting nova-network support into the V3 API

Hi Kenichi, Ah yes, it was decided at the mid cycle meetup to delay the nova network changes until Juno. Sorry I should have told you sooner. Regards, Chris On Wed, Feb 12, 2014 at 1:35 AM, Kenichi Oomichi wrote: > > Hi Chris, > > Is it OK to postpone nova-network v3 APIs until Juno release?

Re: [openstack-dev] [requirements] problems with non overlapping requirements changes

On Tue, Feb 11, 2014 at 4:31 PM, Sean Dague wrote: > A few weeks ago we realized one of the wrecking balls in the gate were > non overlapping requirements changes, like this - > https://review.openstack.org/#/c/72475/ > > Regular jobs in the gate have to use the OpenStack mirror. Requirements > r

Re: [openstack-dev] Interested in attracting new contributors?

On Feb 12, 2014, at 8:30 AM, Julie Pichon wrote: > Hi folks, > > Stefano's post on how to make contributions to OpenStack easier [1] > finally stirred me into writing about something that vkmc and myself > have been doing on the side for a few months to help new contributors > to get involved.

Re: [openstack-dev] [Neutron] Interest in discussing vendor plugins for L3 services?

Paul, I'm interesting in joining the discussion. UTC-7. Any word on when this will take place? Carl On Mon, Feb 3, 2014 at 3:19 PM, Paul Michali wrote: > I'd like to see if there is interest in discussing vendor plugins for L3 > services. The goal is to strive for consistency across vendor >

Re: [openstack-dev] [python-openstacksdk] First meeting scheduled

On Feb 12, 2014, at 9:07 AM, Ed Leafe wrote: > On Feb 11, 2014, at 3:30 PM, Jesse Noller wrote: > >> I did propose in the original thread that we join efforts: in fact, we >> already have a fully functioning, unified SDK that *could* be checked in >> today - but without discussing the APIs,

[openstack-dev] [nova][neutron] SRIOV: Recap of Feb 12th and agenda on Feb 13th

Hi Folks, I put the recap in here:2 Feb. 12th, 2014 Recap. Please take a look at and see if everything is fine and correct any misunderstandings. I also put together an Agenda for tomorrow in here:1 Agenda on Feb. 13

Re: [openstack-dev] [python-openstacksdk] First meeting scheduled

On Feb 11, 2014, at 3:30 PM, Jesse Noller wrote: > I did propose in the original thread that we join efforts: in fact, we > already have a fully functioning, unified SDK that *could* be checked in > today - but without discussing the APIs, design and other items with the > community at large,

[openstack-dev] Interested in attracting new contributors?

Hi folks, Stefano's post on how to make contributions to OpenStack easier [1] finally stirred me into writing about something that vkmc and myself have been doing on the side for a few months to help new contributors to get involved. Some of you may be aware of OpenHatch [2], a non-profit dedicat

  1   2   >