Re: [openstack-dev] [Neutron] Service VM: irc discussion?

Hi everyone, Is there anyone can kindly tell me how to join your conference? ^^ -邮件原件- 发件人: balaj...@freescale.com [mailto:balaj...@freescale.com] 发送时间: 2014年2月10日 15:11 收件人: Isaku Yamahata; OpenStack Development Mailing List (not for usage questions) 主题: Re: [openstack-dev] [Neutron]

Re: [openstack-dev] [heat] Nominate Jason Dunsmore for heat-core

+1 On 02/09/2014 11:38 PM, Steve Baker wrote: I would like to nominate Jason Dunsmore for heat-core. His reviews are valuable and prolific, his code contributions have demonstrated a good knowledge of heat internals, and he has endured a sound hazing to get multi-engine into heat. http://russe

Re: [openstack-dev] [Neutron] Service VM: irc discussion?

Hi Isaku Yamahata, We are at UTC+5.30.[IST] Regards, Balaji.P > -Original Message- > From: i y [mailto:yamahat...@gmail.com] On Behalf Of Isaku Yamahata > Sent: Monday, February 10, 2014 12:36 PM > To: P Balaji-B37839; OpenStack Development Mailing List (not for usage > questions) > Cc:

Re: [openstack-dev] [Neutron] Service VM: irc discussion?

What's your timezone? 18.00UTC doesn't work for me because my timezone is UTC+9 and it's 3:00AM. thanks, On Mon, Feb 10, 2014 at 06:43:05AM +, "balaj...@freescale.com" wrote: > Hi Isaku Yamahata, > > Is it possible to move the below time slot a little earlier like 18.00UTC? > > Regards, >

Re: [openstack-dev] [Neutron] Service VM: irc discussion?

Hi Isaku Yamahata, Is it possible to move the below time slot a little earlier like 18.00UTC? Regards, Balaji.P > -Original Message- > From: i y [mailto:yamahat...@gmail.com] On Behalf Of Isaku Yamahata > Sent: Monday, February 10, 2014 11:42 AM > To: openstack-dev@lists.openstack.org >

Re: [openstack-dev] How to write a new neutron L2 plugin using ML2 framework?

On Sat, Feb 08, 2014 at 03:49:46AM +, "Yang, Yi Y" wrote: > Hi, All Hi. > I want to write a new neutron L2 plugin using ML2 framework, I noticed > openvswitch and linxubridge have been ported into ML2 framework, but it seems > many code is removed compared to standalone L2 plugin, I gues

[openstack-dev] [Neutron] Service VM: irc discussion?

As the first patch for service vm framework is ready for review[1][2], it would be a good idea to have IRC meeting. Anyone interested in it? How about schedule? Schedule candidate Monday 22:00UTC-, 23:00UTC- Tuesday 22:00UTC-, 23:00UTC- (Although the slot of servanced service vm[3] can be resuled

Re: [openstack-dev] [glance][nova]improvement-of-accessing-to-glance

Hi, all, Thanks for your comment. Please let me re-explain. The main purpose of our blueprint is to use network resources more efficiently. To complete this purpose, we suggested the method of using 2 lists. We think, as I wrote before, by listing near glance API servers and using them, the tot

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

I'm interested in it. My timezone is JST(UTC+9). thanks, On Mon, Feb 03, 2014 at 05:19:35PM -0500, 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 plugins/drivers > and across servic

Re: [openstack-dev] [Neutron] Using Python-Neutronclient from Python - docstrings needed?

Yes, We would be interested in doing that. Please let me know which is the right group/ team for this? On Monday, February 10, 2014 10:34 AM, "Collins, Sean" wrote: Do you have plans to submit these back upstream? It would be a great first start, perhaps we could add these as examples und

Re: [openstack-dev] [Neutron] Using Python-Neutronclient from Python - docstrings needed?

Do you have plans to submit these back upstream? It would be a great first start, perhaps we could add these as examples underneath the JSON request/reponse in http://api.openstack.org/api-ref-networking.html Sean M. Collins From: Rajdeep Dua [dua_rajd...@yahoo.c

[openstack-dev] [gantt] Scheduler sub-group meeting 2/11 - Cancel this week

Let's cancel the meeting this week, some of us (me for sure) will be tied up at the Icehouse mid-cycle meetup. -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstac

[openstack-dev] [Ceilometer] Policy Issue

Hi, I noticed that the Ceilometer project has no strict policy control, the /etc/ceilometer/policy.json only has one single rule 'context_is_admin', and for each specific resource operation, it will invoke acl.get_limit_to and v2._verify_query_segregation to forbid non-admin role operate other ten

Re: [openstack-dev] [neutron][ml2] Maintaining support for the Tail-f NCS mech driver in Icehouse

On 02/06/2014 09:52 AM, Luke Gorrie wrote: > Howdy! > > My name is Luke and I'm helping my friends at Tail-f Systems to > support Neutron with their NCS [1] product. This went really smoothly > for us on the Havana cycle, but lately we're having a harder time with > Icehouse. In particular, our at

Re: [openstack-dev] [nova] Possible Hyper-V false CI failures

Hi guys, On 10 Feb 2014, at 03:59 , Jay Pipes wrote: > On Sun, 2014-02-09 at 18:17 -0700, Christopher Yeoh wrote: >> Hi, >> >> >> I think the hyper-v CI system is sometimes failing with this message >> incorrectly: >> >> "This change was unable to be automatically merged with the current >

Re: [openstack-dev] [nova] Possible Hyper-V false CI failures

On Sun, 2014-02-09 at 18:17 -0700, Christopher Yeoh wrote: > Hi, > > > I think the hyper-v CI system is sometimes failing with this message > incorrectly: > > "This change was unable to be automatically merged with the current > state of the repository. Please rebase your change and upload a

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

On 02/09/2014 12:56 PM, Kyle Mestery wrote: > On Feb 6, 2014, at 5:24 PM, Vinay Bannai wrote: > >> Hello Folks, >> >> We are running into a situation where we are not able to create multiple >> provider networks with the same VLAN id. We would like to propose a solution >> to remove this restr

[openstack-dev] Call for Testing: PetiteCloud's support for linux as a Cloud Foundation Layer

PetiteCloud is a Free Open Source and Open Knowledge Cloud Foundation Layer Tool that is designed to make OpenStack more stable and robust. See http://www.petitecloud.org for more details. We have recently added support for Linux (Ubuntu 12.04.3 LTS) as a host, we have had a FreeBSD production m

[openstack-dev] [nova] Possible Hyper-V false CI failures

Hi, I think the hyper-v CI system is sometimes failing with this message incorrectly: "This change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset." I only mention it because its the second time I've seen it.

Re: [openstack-dev] [heat] Nominate Jason Dunsmore for heat-core

+1 From: Steve Baker [sba...@redhat.com] Sent: Monday, February 10, 2014 8:38 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [heat] Nominate Jason Dunsmore for heat-core I would like to nominate Jason Dunsmore for heat-core. His reviews

Re: [openstack-dev] [neutron][ml2] Maintaining support for the Tail-f NCS mech driver in Icehouse

On Mon, Feb 10, 2014 at 9:10 AM, CARVER, PAUL wrote: > Kyle Mestery wrote: > >>So, in general I don't think this will fly because it's my understanding the >>OpenStack servers only test fully open source code. Allowing a third party >>vendor system to run on the OpenStack servers as part of any fu

Re: [openstack-dev] [neutron][ml2] Maintaining support for the Tail-f NCS mech driver in Icehouse

On Feb 9, 2014, at 4:10 PM, CARVER, PAUL wrote: > Kyle Mestery wrote: > >> So, in general I don't think this will fly because it's my understanding the >> OpenStack servers only test fully open source code. Allowing a third party >> vendor system to run on the OpenStack servers as part of any

Re: [openstack-dev] [heat] Nominate Jason Dunsmore for heat-core

Curse you Randall for taking first post! +1 Excerpts from Randall Burt's message of 2014-02-09 14:47:39 -0800: > Very +1 > > Original message > From: Steve Baker > Date:02/09/2014 4:41 PM (GMT-06:00) > To: OpenStack Development Mailing List > Subject: [openstack-dev] [heat] Nom

Re: [openstack-dev] [heat] Nominate Jason Dunsmore for heat-core

Very +1 Original message From: Steve Baker Date:02/09/2014 4:41 PM (GMT-06:00) To: OpenStack Development Mailing List Subject: [openstack-dev] [heat] Nominate Jason Dunsmore for heat-core I would like to nominate Jason Dunsmore for heat-core. His reviews are valuable and prolif

[openstack-dev] [heat] Nominate Jason Dunsmore for heat-core

I would like to nominate Jason Dunsmore for heat-core. His reviews are valuable and prolific, his code contributions have demonstrated a good knowledge of heat internals, and he has endured a sound hazing to get multi-engine into heat. http://russellbryant.net/openstack-stats/heat-reviewers-60.tx

Re: [openstack-dev] [neutron][ml2] Maintaining support for the Tail-f NCS mech driver in Icehouse

Kyle Mestery wrote: >So, in general I don't think this will fly because it's my understanding the >OpenStack servers only test fully open source code. Allowing a third party >vendor system to run on the OpenStack servers as part of any functional >testing would open an entirely new can of worms h

Re: [openstack-dev] [Horizon] User Signup

I've just taken a look at the feedback in the whiteboard. If it's ok, I'd like to take this discussion back to the mailing list. I find the whiteboards somewhat clumsy for discussions. Akihiro Motoki points out that all services should work without the dashboard. Keystone already exposes an API to

Re: [openstack-dev] [nova][ceilometer] Removing simple_tenant_usage and os-instance_usage_audit_log from V3 API

On 02/09/2014 01:39 PM, Christopher Yeoh wrote: > On Fri, Feb 7, 2014 at 3:10 PM, Joe Gordon > wrote: > > Hi All, > > I would like to propose removing the simple_tenant_usage and > os-instance_usage_audit_log extensions from the nova V3 API (while >

Re: [openstack-dev] question about storage policies for Swift

Hi Gil, Thanks for the question. I'll start with a quick status update and encourage anyone interested to participate in the activates listed below as well. IRC is a great place to bring up questions/discussion topics as well: -We're currently tracking outstanding activates on a Trel

Re: [openstack-dev] [nova][ceilometer] Removing simple_tenant_usage and os-instance_usage_audit_log from V3 API

On Fri, Feb 7, 2014 at 3:10 PM, Joe Gordon wrote: > Hi All, > > I would like to propose removing the simple_tenant_usage and > os-instance_usage_audit_log extensions from the nova V3 API (while > keeping them in V2). Both of these are pre ceilometer extensions to > generate rudimentary usage info

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

On Feb 6, 2014, at 5:24 PM, Vinay Bannai wrote: > Hello Folks, > > We are running into a situation where we are not able to create multiple > provider networks with the same VLAN id. We would like to propose a solution > to remove this restriction through a configuration option. This approach

Re: [openstack-dev] [neutron][ml2] Maintaining support for the Tail-f NCS mech driver in Icehouse

On Feb 6, 2014, at 8:52 AM, Luke Gorrie wrote: > Howdy! > > My name is Luke and I'm helping my friends at Tail-f Systems to > support Neutron with their NCS [1] product. This went really smoothly > for us on the Havana cycle, but lately we're having a harder time with > Icehouse. In particular,

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

Hi Paul Yes I would be interested in this as I believe its an area we have not got around to so far in Neutron. /Alan From: Paul Michali [mailto:p...@cisco.com] Sent: February-03-14 5:20 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Neutron] Inter

Re: [openstack-dev] [heat] Can heat automatically create a flavor as part of stack creation?

Heat template orchestrates user actions, while management of flavors is typically admin's job (due to their tight link to the physical hardware configuration, unknown to a regular user). Regards, Alex From: "ELISHA, Moshe (Moshe)" To: "openstack-dev@lists.openstack.org" , Date: 09

Re: [openstack-dev] [Nova] Gate broken

Thanks for fixing this. From: Qiu Yu mailto:unic...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Saturday, February 8, 2014 9:44 AM To: "OpenStack Development Mailing List (not for usage questions)" mailto:o

Re: [openstack-dev] [heat] Can heat automatically create a flavor as part of stack creation?

In principle yes. You need: - to write a module to orchestrate the nova flavor API. - to configure your policy rules in the cloud in question to let the heat engine user create flavors -Rob On 9 February 2014 20:49, ELISHA, Moshe (Moshe) wrote: > Hello, > > > > I am wondering if instead of be