Re: [openstack-dev] [nova]

On 12/11/13 12:43 AM, "Matt Riedemann" wrote: > > >On Tuesday, December 10, 2013 4:17:45 PM, Maithem Munshed 71510 wrote: >> Hello, >> >> I was wondering, what is the reason behind having nova audit resources >> as opposed to using usage stats directly from what is reported by the >> compute dr

Re: [openstack-dev] [Gating-Failures] Docs creation is failing

Hi, Saw that this was dealt with in most projects. I have posted the Nova review - https://review.openstack.org/61329 Thanks Gary From: Administrator mailto:gkot...@vmware.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Da

Re: [openstack-dev] [Gating-Failures] Docs creation is failing

On 12/11/2013 08:22 AM, Gary Kotton wrote: > Hi, > An example for this > is: > http://logs.openstack.org/94/59994/10/check/gate-nova-docs/b0f3910/console.html > Any ideas? > Thanks > Gary > There is a thread about this: http://lists.openstack.org/pipermail/openstack-dev/2013-December/021863.html

[openstack-dev] [Ceilometer] RFC: blueprint monitoring-network

Hi, Ceilometer team. We have posted 2 blueprints.[1][2] This feature collects the network information(device, link status, statistics) via NorthBound API from SDN Controller. The purpose of this feature is testing network route, resource optimization based on network proximity and etc. In part

[openstack-dev] [Gating-Failures] Docs creation is failing

Hi, An example for this is: http://logs.openstack.org/94/59994/10/check/gate-nova-docs/b0f3910/console.html Any ideas? Thanks Gary ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openst

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

Please take guys and girls from Israel into account ☺. From: Yongsheng Gong [mailto:gong...@unitedstack.com] Sent: Wednesday, December 11, 2013 5:20 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeti

Re: [openstack-dev] [neutron] Third party Neutron plugin testingmeeting

+1 Will join the IRC too -Original Message- From: Kyle Mestery [mailto:mest...@siliconloons.com] Sent: Tuesday, December 10, 2013 10:48 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] Third party Neutron plugin testingmeeting OK,

Re: [openstack-dev] [Scheduler] about scheduler-as-a-service

On Tue, Dec 10, 2013 at 5:30 PM, Lingxian Kong wrote: > we know that there is a scheduler-as-a-service[1] working in progress now, > aiming at smart resource placement and also providing the instance group > API work for nova. > > But what I wonder is does it include the feature of DRS(Distribute

[openstack-dev] [Solum] Git workgroup meeting 8AM PST Wednesday

Hello, As a reminder, the next git workgroup meeting is tomorrow at 8 AM PST (http://www.worldtimebuddy.com/?qm=1&lid=8,524901,2158177,100&h=8&date=2013-12-11&sln=8-9) Agenda: * Topics: * Monty to present idea/diagram about using Zuul for git workflow * Q

Re: [openstack-dev] {opestack][Neutron - FWaaS] CLI Firewall-Policy-Update Bug

Hi- Thanks a lot for the reply. Can you kindly also add the help guideline in the FWaaS Documentation too.. This might be helpful. Thanking you. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Yongsheng Gong [mailto:gong...@unitedstack.com] Sent: Wednesday, De

Re: [openstack-dev] {opestack][Neutron - FWaaS] CLI Firewall-Policy-Update Bug

try to use: neutron firewall-policy-update dd2c7d33-2c36-4200-b1f8-daaa1ab202d5 --firewall-rules list=true rule1 On Wed, Dec 11, 2013 at 1:37 PM, trinath.soman...@freescale.com < trinath.soman...@freescale.com> wrote: > Hi – > > > > I found this issue with FWaaS CLI commands. > > > > When I is

[openstack-dev] {opestack][Neutron - FWaaS] CLI Firewall-Policy-Update Bug

Hi - I found this issue with FWaaS CLI commands. When I issue the command, $> neutron firewall-policy-update dd2c7d33-2c36-4200-b1f8-daaa1ab202d5 --firewall-rules "rule1" 404-{u'NeutronError': {u'message': u'Firewall Rule r could not be found.', u'type': u'FirewallRuleNotFound', u'detail': u'

Re: [openstack-dev] [Solum] Plan files and resources

Devdatta, On Dec 10, 2013, at 12:37 PM, devdatta kulkarni wrote: > Hi Adrian, > > Thanks for creating https://etherpad.openstack.org/p/solum-demystified > > I am really excited to see the examples. Especially cool is how > examples 2 and 3 demonstrate using a component ("solum_glance_id") cre

Re: [openstack-dev] [openstack-qa] [qa][nova] The document for the changes from Nova v2 api to v3

yeah, that's good idea. That can keep the doc update with code. I will try to convert the wiki to rst format, then submit to gerrit. On 2013?12?07? 00:12, Anne Gentle wrote: Hi all, Now that you've got a decent start, how about checking it in as a doc/source/ document in the nova repository? S

Re: [openstack-dev] [keystone] domain admin role query

Using the default policies it will simply check for the admin role and not care about the domain that admin is limited to. This is partially a left over from the V2 api when there wasn't domains to worry about. A better example of policies are in the file etc/policy.v3cloudsample.json. In there

Re: [openstack-dev] [Neutron] DHCP Agent Reliability

On Dec 11, 2013, at 8:39 AM, Isaku Yamahata wrote: > On Wed, Dec 11, 2013 at 01:23:36AM +0900, > Maru Newby wrote: > >> >> On Dec 10, 2013, at 6:36 PM, Isaku Yamahata wrote: >> >>> On Mon, Dec 09, 2013 at 08:43:59AM +1300, >>> Robert Collins wrote: >>> >> listening: when an agent conn

Re: [openstack-dev] [Neutron] ML2 improvement, more extensible and more modular

On 12/04/2013 05:37 AM, Zang MingJie wrote: > Hi, all: > > I have already written a patch[1] which makes ml2 segment more > extensible, where segments can contains more fields other than physical > network and segmentation id, but there is still a lot of work to do to > make the ml2 more extensibl

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

UTC 22:00+, which is 6:am beijing time，but if there are guys from Israel alike, I can get up one hour earlier, just like what I do for neutron meeting. On Wed, Dec 11, 2013 at 11:08 AM, Kyle Mestery wrote: > I suspect we'll need another meeting next week, I propose we have it > at a time friendl

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

I suspect we'll need another meeting next week, I propose we have it at a time friendly to those in Asian timezones. Yong and Akihiro, can you guys propose a timeslot which works for you guys and I'll see about setting the followup meeting up. Thanks, Kyle On Dec 10, 2013, at 8:14 PM, Yongsheng G

Re: [openstack-dev] ml2 and vxlan configurations, neutron-server fails to start

On 11/28/2013 07:01 AM, Gopi Krishna B wrote: > > Hi > I am configuring Havana on fedora 19. Observing the below errors in case > of neutron. > Please help me resolve this issue. > copied only few lines from the server.log, in case full log is > required, let me know. You may have resolved this

Re: [openstack-dev] Sphinx 1.2 incompatibility (failing -docs jobs)

On 12/10/2013 6:32 PM, Angus Salkeld wrote: On 10/12/13 14:57 -0800, James E. Blair wrote: Hi, Sphinx 1.2 was just released and it is incompatible with distutils in python 2.7. See these links for more info: https://bitbucket.org/birkenfeld/sphinx/pull-request/193/builddoc-shouldnt-fail-o

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

It is 1am beijing time, so I am afraid I will not join. On Wed, Dec 11, 2013 at 10:10 AM, Akihiro Motoki wrote: > Thanks Kyle for coordinating the meeting. > > The time is midnight to me, but it fits everyone except me. I'll try the > time but not sure. Anyway I will follow the log. > > 2013年12

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

Thanks Kyle for coordinating the meeting. The time is midnight to me, but it fits everyone except me. I'll try the time but not sure. Anyway I will follow the log. 2013年12月11日水曜日 Shiv Haris sha...@brocade.com: > +1 > > > > Will join via IRC or voice call > > > > > > > > *From:* Gary Duan [mailto

[openstack-dev] Fwd: [OpenStack-dev] How to modify a bug across multiple repo?

Hi Chris & Rob, Thanks for your reply ,and sorry for my late response.. - I tested again. The modification won't effect tempest test because it's an optional argument, so I can commit it later in tempest. Lucky. - But the bug in Cinder exists at the API layer, so the modification will effect th

Re: [openstack-dev] [ironic][qa] How will ironic tests run in tempest?

Tue, Dec 10, 2013 at 12:43 PM, David Kranz wrote: > On 12/09/2013 01:37 PM, Devananda van der Veen wrote: > > On Fri, Dec 6, 2013 at 2:13 PM, Clark Boylan wrote: > >> On Fri, Dec 6, 2013 at 1:53 PM, David Kranz wrote: >> > It's great that tempest tests for ironic have been submitted! I was >

Re: [openstack-dev] [ironic][qa] How will ironic tests run in tempest?

On 12/10/2013 07:05 PM, Robert Collins wrote: > On 11 December 2013 09:43, David Kranz wrote: > >> So it seems that the code in the submitted tempest tests can run in a >> regular job if devstack is configured to enable ironic, but that this cannot >> be the default. So I propose that we create a

[openstack-dev] [keystone] domain admin role query

Hi, I am trying out Keystone V3 APIs and domains. I created an domain, created a project in that domain, created an user in that domain and project. Next, gave an admin role for that user in that domain. I am assuming that user is now admin to that domain. Now, I got a scoped token with that use

Re: [openstack-dev] Sphinx 1.2 incompatibility (failing -docs jobs)

On 12/10/2013 07:32 PM, Angus Salkeld wrote: > On 10/12/13 14:57 -0800, James E. Blair wrote: >> Hi, >> >> Sphinx 1.2 was just released and it is incompatible with distutils in >> python 2.7. See these links for more info: >> >> >> https://bitbucket.org/birkenfeld/sphinx/pull-request/193/builddo

Re: [openstack-dev] [qa] [Solum] [tempest] Use of pecan test framework in functional tests

On Dec 10, 2013, at 3:12 PM, Russell Bryant wrote: > On 12/10/2013 04:10 PM, Georgy Okrokvertskhov wrote: >> Hi, >> >> In Solum project we are currently creating tests environments for future >> test. We split unit tests and functional tests in order to use tempest >> framework from the beginni

Re: [openstack-dev] Sphinx 1.2 incompatibility (failing -docs jobs)

On 10/12/13 14:57 -0800, James E. Blair wrote: Hi, Sphinx 1.2 was just released and it is incompatible with distutils in python 2.7. See these links for more info: https://bitbucket.org/birkenfeld/sphinx/pull-request/193/builddoc-shouldnt-fail-on-unicode-paths/diff http://bugs.python.org/is

[openstack-dev] [Ironic] cleaning up our core reviewer list

Hi all, It's about time that I look at the ironic review stats to see who should be added / removed again. There are several non-core folks doing reviews during the last month [1] -- thanks! These have been very helpful. I am also looking at the folks who are contributing code [3] to get another

Re: [openstack-dev] [ironic][qa] How will ironic tests run in tempest?

On 11 December 2013 09:43, David Kranz wrote: > So it seems that the code in the submitted tempest tests can run in a > regular job if devstack is configured to enable ironic, but that this cannot > be the default. So I propose that we create a regular devstack+ironic job > that will run in the i

Re: [openstack-dev] Sphinx 1.2 incompatibility (failing -docs jobs)

On Tue, Dec 10, 2013 at 5:57 PM, James E. Blair wrote: > Hi, > > Sphinx 1.2 was just released and it is incompatible with distutils in > python 2.7. See these links for more info: > > > https://bitbucket.org/birkenfeld/sphinx/pull-request/193/builddoc-shouldnt-fail-on-unicode-paths/diff > http:

Re: [openstack-dev] Unified Guest Agent proposal

Yeah. Its likely that the metadata server stuff will get more scalable/hardened over time. If it isn't enough now, lets fix it rather then coming up with a new system to work around it. I like the idea of using the network since all the hypervisors have to support network drivers already. They

Re: [openstack-dev] [Neutron] DHCP Agent Reliability

On Wed, Dec 11, 2013 at 01:23:36AM +0900, Maru Newby wrote: > > On Dec 10, 2013, at 6:36 PM, Isaku Yamahata wrote: > > > On Mon, Dec 09, 2013 at 08:43:59AM +1300, > > Robert Collins wrote: > > > listening: when an agent connects after an outage, it first starts > listening, then do

Re: [openstack-dev] [Nova][Cells] compute api and objects

On Dec 9, 2013, at 2:58 PM, Sam Morrison wrote: > Hi, > > I’m trying to fix up some cells issues related to objects. Do all compute api > methods take objects now? > cells is still sending DB objects for most methods (except start and stop) > and I know there are more than that. > > Eg. I kno

[openstack-dev] [Neutron] Does any plugin require hairpinning to be enabled?

Hi, We currently have a bug for IPv6 work, which is to disable hairpinning on the bridge that Nova creates. By default, it is always turned on, which prevents instances from configuring IPv6 SLAAC addresses https://launchpad.net/bugs/1251235 https://review.openstack.org/#/c/56381/ Daniel Berran

Re: [openstack-dev] Unified Guest Agent proposal

Maybe it will be useful to use Ovirt guest agent as a base. http://www.ovirt.org/Guest_Agent https://github.com/oVirt/ovirt-guest-agent It is already working well on linux and windows and has a lot of functionality. However, currently it is using virtio-serial for communication, but I think it

[openstack-dev] Sphinx 1.2 incompatibility (failing -docs jobs)

Hi, Sphinx 1.2 was just released and it is incompatible with distutils in python 2.7. See these links for more info: https://bitbucket.org/birkenfeld/sphinx/pull-request/193/builddoc-shouldnt-fail-on-unicode-paths/diff http://bugs.python.org/issue19570 This has caused all -docs jobs to fai

Re: [openstack-dev] [qa] [Solum] [tempest] Use of pecan test framework in functional tests

Thanks everyone for feedback. Will follow the standard approach with HTTP requests in tempest tests. Thanks Georgy On Tue, Dec 10, 2013 at 2:47 PM, Sean Dague wrote: > Pretty much 100% agree with Russell and Ryan. > > Webtest is interesting for in tree testing with Solum, because it's > specif

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

+1 on Tatiana Mazur, she's been doing a bunch of good work lately. I'm fine with me being removed from core provided you have someone else qualified to address security issues as they come up. My contributions have lately been reviewing and responding to security issues, vetting fixes for those

Re: [openstack-dev] [qa] [Solum] [tempest] Use of pecan test framework in functional tests

Pretty much 100% agree with Russell and Ryan. Webtest is interesting for in tree testing with Solum, because it's specifically *not* bringing up the full stack. When it comes to Tempest, you are hitting a live OpenStack cloud, most likely not on the same machine as Tempest is on (not true in the

Re: [openstack-dev] [nova]

On Tuesday, December 10, 2013 4:17:45 PM, Maithem Munshed 71510 wrote: Hello, I was wondering, what is the reason behind having nova audit resources as opposed to using usage stats directly from what is reported by the compute driver. The available resources reported from the audit can be inco

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

"David Lyle" wrote: > I would like to nominate Tatiana Mazur to Horizon Core. Tatiana has been a > significant code contributor in the last two releases, understands the code > base well and has been doing a significant number of reviews for the last to > milestones. +1 > Additionally, I'd like

Re: [openstack-dev] [keystone] Service scoped role definition

My Comments in line. Arvind -Original Message- From: Adam Young [mailto:ayo...@redhat.com] Sent: Tuesday, December 10, 2013 2:54 PM To: David Chadwick; Tiwari, Arvind; OpenStack Development Mailing List (not for usage questions) Cc: Henry Nash; dolph.math...@gmail.com; Yee, Guang Subjec

Re: [openstack-dev] Neutron Distributed Virtual Router

Hi Nachi/Akihiro motoki, I am not clear. Today the L3 Service Plugin does not support the "service_type" attribute to define the provider option. Are we suggesting that we need to include the service_type for the L3 Service Plugin and then we can make use of the "service_type" attribute to d

[openstack-dev] [nova]

Hello, I was wondering, what is the reason behind having nova audit resources as opposed to using usage stats directly from what is reported by the compute driver. The available resources reported from the audit can be incorrect in some cases. Also, in many cases the reported usage stats from t

[openstack-dev] Neutron Distributed Virtual Router

Hi Nachi, Yes you are right, NSX deals with (local or distributed) routers and Service Routers. Thanks Swami >Hi Yong >NSX have two kind of router. >Edge and distributed router. >Edge node will work as some VPN services and advanced service nodes. >Actually, VPNaaS OSS impl is running

Re: [openstack-dev] [TripleO][Tuskar] Icehouse Requirements

On 11 December 2013 05:42, Jaromir Coufal wrote: > On 2013/09/12 23:38, Tzu-Mainn Chen wrote: >> The disagreement comes from whether we need manual node assignment or not. >> I would argue that we >> need to step back and take a look at the real use case: heterogeneous >> nodes. If there are lite

Re: [openstack-dev] FW: [Bug 1257788] Re: nova-network doesn't handle large amount of concurrent booting instances well

On Dec 10, 2013 7:38 PM, "Joshua Harlow" wrote: > > Yup, IMHO this is where the rally[1] project, and others that attempt to > push the boundaries are really helping openstack become much better around > these types of issues. At yahoo! in a short-time it will not be that > uncommon to boot 100+ V

Re: [openstack-dev] [keystone] Service scoped role definition

Yes, it is required to address one of public cloud use case where we want regional service admins and to support https://blueprints.launchpad.net/keystone/+spec/service-scoped-tokens BP. Based on our discussion I am going to start API specs and submit for review. { "role": { "id": "

Re: [openstack-dev] [keystone] Service scoped role definition

On 12/10/2013 04:26 PM, David Chadwick wrote: Hi Arvind the granularity in naming can be as fine as required i.e. a naming hierarchy can be as deep as required. So if there is a requirement for individual endpoints to name their own roles, then the addition of endpoint_id to the naming structure

Re: [openstack-dev] [Nova][Cells] compute api and objects

On Monday, December 09, 2013 4:58:31 PM, Sam Morrison wrote: Hi, I’m trying to fix up some cells issues related to objects. Do all compute api methods take objects now? cells is still sending DB objects for most methods (except start and stop) and I know there are more than that. Eg. I know

Re: [openstack-dev] [nova] ExtraSpecs format bug

On Thursday, December 05, 2013 1:38:45 PM, Costantino, Leandro I wrote: Hi! i am working on the Horizon 'side' of https://bugs.launchpad.net/nova/+bug/1256119 , where basically if you create a ExtraSpec key containing '/', then it cannot be deleted anymore. Is there any restriction about this

Re: [openstack-dev] [heat] Stack preview

On 10/12/13 15:10, Randall Burt wrote: On Dec 10, 2013, at 1:27 PM, Zane Bitter wrote: On 10/12/13 12:46, Richard Lee wrote: Hey all, We're working on a blueprint that adds the ability to preview what a given template+parameters w

Re: [openstack-dev] OK to Use Flufl.enum

On 12/10/2013 11:43 AM, Jay Pipes wrote: On 12/10/2013 11:26 AM, Alex Gaynor wrote: >>> from flufl.enum import IntEnum >>> class A(IntEnum): ... a = 3 ... >>> A.a If the __repr__ is *really* the only value of IntEnum, I'm less than impressed. -jay On Tue, Dec 10, 2013 at 8:23 AM, Ja

Re: [openstack-dev] [Horizon] Less compiler dependency

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/10/2013 07:04 PM, Jordan OMara wrote: > > I'm a bit newer to this conversation than some, but I'm not sure > what exactly the "NodeJS packaging nightmare" is? Isn't it already > packaged for many major distributions? > I might speak for Fedora

Re: [openstack-dev] [qa] [Solum] [tempest] Use of pecan test framework in functional tests

On 12/10/2013 04:12 PM, Russell Bryant wrote: On 12/10/2013 04:10 PM, Georgy Okrokvertskhov wrote: Hi, In Solum project we are currently creating tests environments for future test. We split unit tests and functional tests in order to use tempest framework from the beginning. Tempest framework

Re: [openstack-dev] [keystone] Service scoped role definition

Hi Arvind the granularity in naming can be as fine as required i.e. a naming hierarchy can be as deep as required. So if there is a requirement for individual endpoints to name their own roles, then the addition of endpoint_id to the naming structure is fine. regards David On 10/12/2013 16:42,

Re: [openstack-dev] [qa] [Solum] [tempest] Use of pecan test framework in functional tests

My opinion is that there’s value in both. Writing functional tests for Solum’s test suite using WebTest can be pretty useful for testing the API’s logic without having to involve HTTP (to e.g., call API endpoints with certain POST arguments and assert that certain mocked functions end up being

Re: [openstack-dev] [Horizon] Less compiler dependency

On 12/10/2013 06:06 PM, Thomas Goirand wrote: > On 12/10/2013 11:41 PM, Jiri Tomasek wrote: >> On 12/09/2013 12:47 PM, Jaromir Coufal wrote: >>> So I would like to ask everybody, if we can reconsider this dependency >>> and find some other alternative. I know we moved from nodejs, because >>> it is

Re: [openstack-dev] [qa] [Solum] [tempest] Use of pecan test framework in functional tests

On 12/10/2013 04:10 PM, Georgy Okrokvertskhov wrote: > Hi, > > In Solum project we are currently creating tests environments for future > test. We split unit tests and functional tests in order to use tempest > framework from the beginning. > > Tempest framework assumes that you run your service

[openstack-dev] [qa] [Solum] [tempest] Use of pecan test framework in functional tests

Hi, In Solum project we are currently creating tests environments for future test. We split unit tests and functional tests in order to use tempest framework from the beginning. Tempest framework assumes that you run your service and test APi endpoints by sending HTTP requests. Solum uses Pecan W

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

+1 on Tatiana Mazur being added to Core. I'm also okay with cleaning out the Core list. I considered doing it myself last cycle since none of those folks are involved anymore, but figured I'd leave them as a posthumous honor. ;-) I think now's a good time to trim it down. Glad I didn't make the

Re: [openstack-dev] [heat] Stack preview

On 12/11/2013 06:46 AM, Richard Lee wrote: > Hey all, > > We're working on a blueprint > that adds > the ability to preview what a given template+parameters would create > in terms of resources. We think this would provide significant val

Re: [openstack-dev] Unified Guest Agent proposal

Excerpts from Dmitry Mescheryakov's message of 2013-12-10 12:37:37 -0800: > >> What is the exact scenario you're trying to avoid? > > It is DDoS attack on either transport (AMQP / ZeroMQ provider) or server > (Salt / Our own self-written server). Looking at the design, it doesn't > look like the a

Re: [openstack-dev] Unified Guest Agent proposal

On 10 December 2013 20:55, Clint Byrum wrote: > If it is just a network API, it works the same for everybody. This > makes it simpler, and thus easier to scale out independently of compute > hosts. It is also something we already support and can very easily expand > by just adding a tiny bit of f

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

On 12/10/2013 09:24 PM, Lyle, David wrote: > I would like to nominate Tatiana Mazur to Horizon Core. Tatiana has been a > significant code contributor in the last two releases, understands the code > base well and has been doing a significant number of reviews for the last to > milestones. > >

Re: [openstack-dev] [neutron] Third party Neutron plugin testingmeeting

+1 Will join via IRC or voice call From: Gary Duan [mailto:gd...@varmour.com] Sent: Tuesday, December 10, 2013 10:59 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] Third party Neutron plugin testingmeeting I will be joining IRC too.

Re: [openstack-dev] [ironic][qa] How will ironic tests run in tempest?

On 12/09/2013 01:37 PM, Devananda van der Veen wrote: On Fri, Dec 6, 2013 at 2:13 PM, Clark Boylan > wrote: On Fri, Dec 6, 2013 at 1:53 PM, David Kranz mailto:dkr...@redhat.com>> wrote: > It's great that tempest tests for ironic have been submitted! I was

Re: [openstack-dev] [neutron] Third party Neutron plugin testingmeeting

OK, looks like we've reached consensus. I've set the time and channel to 12-12-2013 (Thursday), 1700UTC, on #openstack-meeting-alt. Thanks! Kyle On Dec 10, 2013, at 12:59 PM, Gary Duan wrote: > I will be joining IRC too. > > Thanks, > Gary > > > On Tue, Dec 10, 2013 at 10:33 AM, Edgar Magana

Re: [openstack-dev] Unified Guest Agent proposal

>> What is the exact scenario you're trying to avoid? It is DDoS attack on either transport (AMQP / ZeroMQ provider) or server (Salt / Our own self-written server). Looking at the design, it doesn't look like the attack could be somehow contained within a tenant it is coming from. In the current

Re: [openstack-dev] [Horizon] Nominations to Horizon Core

+1 for Tatiana. On Tue, Dec 10, 2013 at 10:24 PM, Lyle, David wrote: > I would like to nominate Tatiana Mazur to Horizon Core. Tatiana has been > a significant code contributor in the last two releases, understands the > code base well and has been doing a significant number of reviews for the

[openstack-dev] [Horizon] Nominations to Horizon Core

I would like to nominate Tatiana Mazur to Horizon Core. Tatiana has been a significant code contributor in the last two releases, understands the code base well and has been doing a significant number of reviews for the last to milestones. Additionally, I'd like to remove some inactive member

Re: [openstack-dev] [heat] Stack convergence first steps

On Dec 10, 2013, at 1:03 PM, Anderson Mesquita mailto:anderson...@thoughtworks.com>> wrote: To try and keep this conversation moving forward, is it safe to say that we at least need to change the current status attribute to something like action_status? And the same with status_reason being ch

[openstack-dev] Recruiting developers for Neutron API tests in Tempest

For the Icehouse cycle, the OpenStack community is undertaking a focused effort to strengthen the suite of Tempest API tests for Neutron. If you are interested on contributing to this effort, please go to https://etherpad.openstack.org/p/icehouse-summit-qa-neutron. Please scroll down to the "API te

Re: [openstack-dev] [infra] Meeting Tuesday December 10th at 19:00 UTC

On Mon, Dec 9, 2013 at 10:30 AM, Elizabeth Krumbach Joseph wrote: > The OpenStack Infrastructure (Infra) team is hosting our weekly > meeting tomorrow, Tuesday December 10th, at 19:00 UTC in > #openstack-meeting Meeting minutes and log: Minutes: http://eavesdrop.openstack.org/meetings/infra/201

Re: [openstack-dev] [heat] Stack preview

On Dec 10, 2013, at 1:27 PM, Zane Bitter wrote: > On 10/12/13 12:46, Richard Lee wrote: >> Hey all, >> >> We're working on a blueprint >> that adds >> the ability to preview what a given template+parameters would create in >> terms of

Re: [openstack-dev] Unified Guest Agent proposal

Excerpts from Dmitry Mescheryakov's message of 2013-12-10 11:08:58 -0800: > 2013/12/10 Clint Byrum > > > Excerpts from Dmitry Mescheryakov's message of 2013-12-10 08:25:26 -0800: > > > And one more thing, > > > > > > Sandy Walsh pointed to the client Rackspace developed and use - [1], [2]. > > >

Re: [openstack-dev] Unified Guest Agent proposal

On Dec 10, 2013 7:00 PM, "Clint Byrum" wrote: > > Excerpts from Dmitry Mescheryakov's message of 2013-12-10 08:15:15 -0800: > > Guys, > > > > I see two major trends in the thread: > > > > * use Salt > > * write our own solution with architecture similar to Salt or MCollective > > > > There were

Re: [openstack-dev] [Heat] workflow for fixes involving numerous changes

On 10/12/13 13:34, Clint Byrum wrote: Excerpts from Steven Hardy's message of 2013-12-10 03:00:26 -0800: On Tue, Dec 10, 2013 at 11:45:11AM +0200, Pavlo Shchelokovskyy wrote: - wouldn't it be better to keep all these changes in one bug and fix all misuses per file basis (with one file per patch

Re: [openstack-dev] [heat] Stack preview

On 10/12/13 12:46, Richard Lee wrote: Hey all, We're working on a blueprint that adds the ability to preview what a given template+parameters would create in terms of resources. We think this would provide significant value for bluepri

[openstack-dev] [Nova] icehouse-2 blueprint deadline

Greetings, We have a lot of blueprints targeted to icehouse-2 [1] that are still under review. The blueprints that do not have a priority are still under review. We need a deadline for blueprints to be finalized for this milestone. I propose that deadline to be Thursday, December 19. Any bluep

Re: [openstack-dev] Unified Guest Agent proposal

2013/12/10 Clint Byrum > Excerpts from Dmitry Mescheryakov's message of 2013-12-10 08:25:26 -0800: > > And one more thing, > > > > Sandy Walsh pointed to the client Rackspace developed and use - [1], [2]. > > Its design is somewhat different and can be expressed by the following > > formulae: > >

Re: [openstack-dev] [heat] Stack convergence first steps

To try and keep this conversation moving forward, is it safe to say that we at least need to change the current status attribute to something like action_status? And the same with status_reason being changed to action_status_reason? Does anybody see a reason why we shouldn't go this way, since it's

Re: [openstack-dev] [neutron] Third party Neutron plugin testingmeeting

I will be joining IRC too. Thanks, Gary On Tue, Dec 10, 2013 at 10:33 AM, Edgar Magana wrote: > Also joining! > Looking forward to hearing your ideas folks! > > Edgar > > On 12/10/13 10:16 AM, "Nachi Ueno" wrote: > > >+1 ! I'll join. > >I'm also working on investigating how to use openstack g

Re: [openstack-dev] [TripleO][Tuskar] Icehouse Requirements

Thanks for the explanation! I'm going to claim that the thread revolves around two main areas of disagreement. Then I'm going to propose a way through: a) Manual Node Assignment I think that everyone is agreed that automated node assignment through nova-scheduler is by far the most ideal cas

Re: [openstack-dev] [keystone] Service scoped role definition

On 12/10/2013 11:42 AM, Tiwari, Arvind wrote: Hi David, I am cool with the proposal, just wanted to grad you attention on may question which I asked in my last email (which is below) Q. what if two (or more) endpoints want to have same role_name for a service (nova.east.admin, nova.west.admin

Re: [openstack-dev] [TripleO][Tuskar] Icehouse Requirements

Thanks for the reply! Comments in-line: > > The disagreement comes from whether we need manual node assignment or not. > > I would argue that we > > need to step back and take a look at the real use case: heterogeneous > > nodes. If there are literally > > no characteristics that differentiate n

[openstack-dev] [Solum] [Plan]

Hi Adrian, Thanks for creating https://etherpad.openstack.org/p/solum-demystified I am really excited to see the examples. Especially cool is how examples 2 and 3 demonstrate using a component ("solum_glance_id") created as part of example 1. Some questions/comments: 1) Summarizing the sequenc

Re: [openstack-dev] FW: [Bug 1257788] Re: nova-network doesn't handle large amount of concurrent booting instances well

Yup, IMHO this is where the rally[1] project, and others that attempt to push the boundaries are really helping openstack become much better around these types of issues. At yahoo! in a short-time it will not be that uncommon to boot 100+ VMs concurrently (traffic spikes, other random QA testing th

Re: [openstack-dev] [Heat] workflow for fixes involving numerous changes

Excerpts from Steven Hardy's message of 2013-12-10 03:00:26 -0800: > On Tue, Dec 10, 2013 at 11:45:11AM +0200, Pavlo Shchelokovskyy wrote: > > - wouldn't it be better to keep all these changes in one bug and fix all > > misuses per file basis (with one file per patch-set for example)? It seems > >

Re: [openstack-dev] [neutron] Third party Neutron plugin testingmeeting

Also joining! Looking forward to hearing your ideas folks! Edgar On 12/10/13 10:16 AM, "Nachi Ueno" wrote: >+1 ! I'll join. >I'm also working on investigating how to use openstack gating system. >(This document is still draft version) >https://docs.google.com/presentation/d/1WJInaSt_H2kVkjnhtPm

Re: [openstack-dev] [neutron] Third party Neutron plugin testingmeeting

+1 for the meeting time. On Dec 10, 2013, at 10:16 AM, Nachi Ueno wrote: > +1 ! I'll join. > I'm also working on investigating how to use openstack gating system. > (This document is still draft version) > https://docs.google.com/presentation/d/1WJInaSt_H2kVkjnhtPmiATP1F-0BVbuk1eefQalL5Q0/edit#s

[openstack-dev] [Neutron][LBaaS] Loadbalancer instance

Hi Neutron and LBaaS folks, Initial version of blueprint lbaas-service-instance is on review: https://review.openstack.org/#/c/60207/ This patch is one of few major features that we've planned for LBaaS in Icehouse and is a basis for other important features like L7 rules, multiple vips/pools. Th

Re: [openstack-dev] [heat] Stack preview

It's still sparse cause we're brainstorming what it'll look like, but if anybody has suggestions, we more than welcome them! More updates to the spec are coming soon! =) 2013/12/10 Clint Byrum > Excerpts from Richard Lee's message of 2013-12-10 09:46:49 -0800: > > Hey all, > > > > We're working

Re: [openstack-dev] [Nova] New API requirements, review of GCE

On 12/10/2013 10:47 AM, Alexandre Levine wrote: > Does nova actually have add-ons infrastructure in which our GCE API can > fit? I see the plugins with xen-server only and have found this link: > http://docs.openstack.org/developer/nova/api/nova.openstack.common.plugin.plugin.html. > Is it the thin

[openstack-dev] FW: [Bug 1257788] Re: nova-network doesn't handle large amount of concurrent booting instances well

FYI. Concurrent calls are a problem all around in OpenStack! Edgar On 12/10/13 8:47 AM, "Abhishek Chanda" wrote: >** Changed in: nova > Status: New => Triaged > >-- >You received this bug notification because you are subscribed to >neutron. >https://bugs.launchpad.net/bugs/1257788 > >Tit

Re: [openstack-dev] [neutron] Third party Neutron plugin testingmeeting

+1 ! I'll join. I'm also working on investigating how to use openstack gating system. (This document is still draft version) https://docs.google.com/presentation/d/1WJInaSt_H2kVkjnhtPmiATP1F-0BVbuk1eefQalL5Q0/edit#slide=id.p 2013/12/10 Ivar Lazzaro : > +1 for 1700UTC Thursday on IRC > > -Origi

Re: [openstack-dev] [Nova] New API requirements, review of GCE

On 12/10/2013 11:13 AM, Alexandre Levine wrote: > Yes, I understand it perfectly, Cristopher, and cannot agree more. It's > just more work to reach this right now than use what's present. Still in > my opinion even in a mid-run just till IceHouse release it might be less > work overall. > I'm going

  1   2   >