Re: [openstack-dev] [nova] blueprint about multiple workers supported in nova-scheduler

We will face the same issue in multiple nova-scheduler process case, like Sylvain say, right? Two processes/workers can actually consume two distinct resources on the same HostState. 2015-03-05 13:26 GMT+08:00 Alex Xu : > Rui, you still can run multiple nova-scheduler process now. > > > 2015-

Re: [openstack-dev] [mistral] Break_on in Retry policy

Ok, we will proceed with error-on and success-on. Thanks for the reply! -- Best Regards, Nikolay __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:

Re: [openstack-dev] [nova] Question about boot-from-volume instance and flavor

The option1 is a bad idea, IMO. Think about so many extra_specs in the flavor today, you really don't want create another dozen of flavor with root_gb=0 just for booting from volume. For the billing concern, it really should be taken into account, but it's not the business of OpenStack, IMHO. I a

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

+100Š.000 Very long overdue! On 3/4/15, 10:23 PM, "Maru Newby" wrote: >+1 from me, Ihar has been doing great work and it will be great to have >him finally able to merge! > >> On Mar 4, 2015, at 11:42 AM, Kyle Mestery wrote: >> >> I'd like to propose that we add Ihar Hrachyshka to the

Re: [openstack-dev] [nova] Question about boot-from-volume instance and flavor

2015-03-04 4:45 GMT+08:00 Jay Pipes : > On 03/03/2015 01:10 AM, Rui Chen wrote: > >> Hi all, >> >> When we boot instance from volume, we find some ambiguous description >> about flavor root_gb in operations guide, >> http://docs.openstack.org/openstack-ops/content/flavors.html >> >> /Virtual root

Re: [openstack-dev] [nova] blueprint about multiple workers supported in nova-scheduler

Rui, you still can run multiple nova-scheduler process now. 2015-03-05 10:55 GMT+08:00 Rui Chen : > Looks like it's a complicated problem, and nova-scheduler can't scale-out > horizontally in active/active mode. > > Maybe we should illustrate the problem in the HA docs. > > http://docs.openstack.

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

+1 From: Armando M. [mailto:arma...@gmail.com] Sent: 05 March 2015 03:12 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer +1! On 4 March 2015 at 22:29, Kevin Benton mailto:blak...@

[openstack-dev] [Glance] [all] python-glanceclient release 0.16.1

The python-glanceclient release management team is pleased to announce: python-glanceclient version 0.16.1 has been released on Thursday, Mar 5th around 04:56 UTC. For more information, please find the details at: https://launchpad.net/python-glanceclient/+milestone/v0.16.1

Re: [openstack-dev] [nova] blueprint about multiple workers supported in nova-scheduler

Looks like it's a complicated problem, and nova-scheduler can't scale-out horizontally in active/active mode. Maybe we should illustrate the problem in the HA docs. http://docs.openstack.org/high-availability-guide/content/_schedulers.html Thanks for everybody's attention. 2015-03-05 5:38 GMT+0

Re: [openstack-dev] [Neutron] Behavior of default security group

Thank you for your response. > That's a fair point. But I think it's because you're not expected to > run as admin, and having a way to drop the group as admin can be of > value for e.g. debugging or cleaning up after some bugs [1]. You’re right. Regenerate logic seems strange to me. But I’m not

Re: [openstack-dev] [neutron][vpnaas] VPNaaS Subteam meetings

Hi Paul. I'd vote for (C) and a slightly later time-slot on Tuesdays - 1630 UTC (or later). The meetings so far was indeed quite useful. I guess the current busy Kilo cycle is also contributing to the low turnout. As we pick up things going forward this forum will be quite useful to discuss edge-

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

On Wed, 2015-03-04 at 11:19 +0100, Thierry Carrez wrote: > James Bottomley wrote: > > On Tue, 2015-03-03 at 11:59 +0100, Thierry Carrez wrote: > >> Second it's at a very different evolution/maturity point (20 years old > >> vs. 0-4 years old for OpenStack projects). > > > > Yes, but I thought I co

Re: [openstack-dev] [oslo.policy] guraduation status

Doug, Thank you for the response and sorry to respond you late. Recently I could not receive e-mails from this list and your e-mail was one of them. I don't know the reason but I found out your response in archive. On Mon, 02 Mar 2015 12:28:06 -0800, Doug Hellmann wrote: > We're making good pro

Re: [openstack-dev] removal of v3 in tree testing

Hi Sean, Yes having V3 directory/file names is very confusing now. But current v3 sample tests cases tests v2.1 plugins. As /v3 url is redirected to v21 plugins, v3 sample tests make call through v3 url and test v2.1 plugins. I think we can start cleaning up the *v3* from everywhere and change i

Re: [openstack-dev] [nova] what's the merge plan for current proposed microversions?

Christopher, If I'm not mistaken about what you mean I understand the point with the small changes, but what's wrong with already approved, tested and ready changes to be added as one version? Alternatively you risk getting rather quickly to high version numbers like 2.25, 2.37 It'll lead

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

- Original Message - > From: "Thierry Carrez" > To: "James Bottomley" > > It's certainly a lot less than you, but we have the entire system > > call > > man pages. It's an official project of the kernel: > > > > https://www.kernel.org/doc/man-pages/ > > > > And we maintain translatio

Re: [openstack-dev] [nova] what's the merge plan for current proposed microversions?

On Wed, Mar 4, 2015 at 9:51 PM, Alexandre Levine wrote: > Christopher, > > Does this > > "So the plan for assignment of microversion api numbers is the same as > what we currently do for db migration changes - take the next one > knowing that you may need to rebase if someone else merges before y

Re: [openstack-dev] [API] #openstack-api created

huzzah! thanks Ian =) mike __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/opens

[openstack-dev] [mistral] Break_on in Retry policy

Hi, I like the idea of explicit checks by success-on and error-on: success-on to break retry and get SUCCESS state. error-on to break retry but get ERROR state. A single break-on seems confusing to me too. Regards, Thomas Hsiao HP Cloud Nikolay, thanks for sharing this… I think that we re

[openstack-dev] [openstack-operators] [nova] Nova options as instance metadata

Hi, in nova there are several options that can be defined in the flavor (extra specs) and/or as image properties. This is great, however to deploy some of these options we will need offer the same image with different properties or let the users upload the same image with the right properties. It

Re: [openstack-dev] [all] SQLAlchemy performance suite and upcoming features (was: [nova] blueprint about multiple workers)

Mike Bayer wrote: > > > Attila Fazekas wrote: > >> Hi, >> >> I wonder what is the planned future of the scheduling. >> >> The scheduler does a lot of high field number query, >> which is CPU expensive when you are using sqlalchemy-orm. >> Does anyone tried to switch those operations to sq

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

+1! On 4 March 2015 at 22:29, Kevin Benton wrote: > +1 > On Mar 4, 2015 12:25 PM, "Maru Newby" wrote: > >> +1 from me, Ihar has been doing great work and it will be great to have >> him finally able to merge! >> >> > On Mar 4, 2015, at 11:42 AM, Kyle Mestery wrote: >> > >> > I'd like to propos

[openstack-dev] [oslo] reminder of feature freeze on 12 Mar

We’re about 1 week out from the Oslo feature freeze, which is 1 week earlier than the app freeze at the third milestone. If you have features you were expecting to land for this cycle, please make sure the core review teams are aware so we can prioritize those reviews. Doug __

Re: [openstack-dev] [nova] blueprint about multiple workers supported in nova-scheduler

Attila Fazekas wrote: > Hi, > > I wonder what is the planned future of the scheduling. > > The scheduler does a lot of high field number query, > which is CPU expensive when you are using sqlalchemy-orm. > Does anyone tried to switch those operations to sqlalchemy-core ? An upcoming feature

Re: [openstack-dev] Testing NUMA, CPU pinning and large pages

- Original Message - > From: "Adrian Hoban" > To: "OpenStack Development Mailing List (not for usage questions)" > > > > -Original Message- > > From: Steve Gordon [mailto:sgor...@redhat.com] > > Sent: Wednesday, February 11, 2015 8:49 PM > > To: OpenStack Development Mailing Lis

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

+1 On Mar 4, 2015 12:25 PM, "Maru Newby" wrote: > +1 from me, Ihar has been doing great work and it will be great to have > him finally able to merge! > > > On Mar 4, 2015, at 11:42 AM, Kyle Mestery wrote: > > > > I'd like to propose that we add Ihar Hrachyshka to the Neutron core > reviewer tea

[openstack-dev] [cinder] [Third-party-announce] Cinder Merged patch broke HDS driver

Hi folks, This weekend, the patch "Snapshot and volume objects" ( https://review.openstack.org/#/c/133566) was merged and this one broke our HDS HBSD driver and the respective CI. When CI tries to run tempest.api.volume.admin.test_snapshots_actions the following error is shown: 2015-03-04 14:00:

[openstack-dev] [os-ansible-deployment] Addition of channel logging

Hey everyone, I just wanted to make the list aware that the stackforge/os-ansible-deployment project has submitted a change to start logging its channel (#openstack-ansible). Please vote on the proposal https://review.openstack.org/#/c/161412/ Cheers, Ian

Re: [openstack-dev] [nova] blueprint about multiple workers supported in nova-scheduler

On 03/04/2015 01:51 AM, Attila Fazekas wrote: Hi, I wonder what is the planned future of the scheduling. The scheduler does a lot of high field number query, which is CPU expensive when you are using sqlalchemy-orm. Does anyone tried to switch those operations to sqlalchemy-core ? Actually, t

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

+1 from me, Ihar has been doing great work and it will be great to have him finally able to merge! > On Mar 4, 2015, at 11:42 AM, Kyle Mestery wrote: > > I'd like to propose that we add Ihar Hrachyshka to the Neutron core reviewer > team. Ihar has been doing a great job reviewing in Neutron as

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

Ihar has proved in several circumstances that he knows neutron source trees way better than me, his reviews are more frequent, thorough, and useful than those of the average core team member. Summarising, in my opinion it is a nonsense that I am part of this team and he's not. So I am obviously ha

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

+1 !!! On Wed, Mar 04, 2015, Kyle Mestery wrote: > I'd like to propose that we add Ihar Hrachyshka to the Neutron core reviewer > team. Ihar has been doing a great job reviewing in Neutron as evidence by his > stats [1]. Ihar is the Oslo liaison for Neutron, he's been doing a great job > keeping

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

+1 > On Mar 4, 2015, at 12:42 PM, Kyle Mestery wrote: > > I'd like to propose that we add Ihar Hrachyshka to the Neutron core reviewer > team. Ihar has been doing a great job reviewing in Neutron as evidence by his > stats [1]. Ihar is the Oslo liaison for Neutron, he's been doing a great job

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

+1 On Mar 4, 2015 12:44 PM, "Kyle Mestery" wrote: > I'd like to propose that we add Ihar Hrachyshka to the Neutron core > reviewer team. Ihar has been doing a great job reviewing in Neutron as > evidence by his stats [1]. Ihar is the Oslo liaison for Neutron, he's been > doing a great job keeping

Re: [openstack-dev] [keystone] Output on stderr

Here's the link to the code review: https://review.openstack.org/#/c/147399/ On Wed, Mar 4, 2015 at 7:17 AM, Dolph Mathews wrote: > > > On Wednesday, March 4, 2015, David Stanek wrote: > >> >> On Wed, Mar 4, 2015 at 6:50 AM, Abhishek Talwar/HYD/TCS < >> abhishek.tal...@tcs.com> wrote: >> >>> Wh

[openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

I'd like to propose that we add Ihar Hrachyshka to the Neutron core reviewer team. Ihar has been doing a great job reviewing in Neutron as evidence by his stats [1]. Ihar is the Oslo liaison for Neutron, he's been doing a great job keeping Neutron current there. He's already a critical reviewer for

[openstack-dev] [Trove] request to backport the fix for bug 1333852 to juno

There has been a request to backport the fix for bug 1333852 (https://bugs.launchpad.net/trove/+bug/1333852) which was fixed in Kilo into the Juno release. The change includes a database change and a small change to the Trove API. The change also requires a change to the trove client and the tr

[openstack-dev] [ceilometer] checking on odds that spec will be approved for K

Hello Ceilometer, I would like to check on the chances that spec https://review.openstack.org/#/c/130359 will land in the K cycle. We in Ironic have specs that are dependent on the above spec and are checking to see if we need to bump them to L? Any information regarding this would be helpful. Th

Re: [openstack-dev] [Glance] Core nominations.

Flavio, I concur, for a lively committee need active core reviewers. Core status is an honor and responsibility. I agree it’s a good idea to replace inactive cores, no offense, priorities and focus of developers change, and should they want to return, can be fast pathed then. Regards Malini ---

[openstack-dev] [API] #openstack-api created

At (or maybe after) the last API-WG meeting, the idea to create an API-WG specific channel came up again and there was consensus that it would be beneficial to have. I registered the channel and have submitted the appropriate changes to system-config and project-config to enable logging of the chan

[openstack-dev] [all] oslo.config 1.9.0 release

We are pumped to announce the release of: oslo.config 1.9.0: Oslo Configuration API For more details, please see the git log history below and: http://launchpad.net/oslo.config/+milestone/1.9.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.config Changes in /h

Re: [openstack-dev] [OpenStack-Infra] [infra][all] CI Check Queue stuck

On 03/04/2015 09:27 AM, Andreas Jaeger wrote: > There has been a maintenance window in one of our providers cloud and it > seems that some of the OpenStack CI infrastructure is not working as is. > You will notice that Jenkins is not commenting on any changes submitted > to review.openstack.org, th

Re: [openstack-dev] [oslo][messaging][zmq] Discussion on zmq driver design issues

Thanks for pulling this list together, Oleksii. More comments inline. - Doug On Wed, Mar 4, 2015, at 12:10 PM, ozamiatin wrote: > Hi, > > By this e-mail I'd like to start a discussion about current zmq driver > internal design problems I've found out. > I wish to collect here all proposals and k

[openstack-dev] [OpenStackClient] Weekly meeting time change

Per the results from the Doodle set up by dhellmann [0] we are moving the scheduled OpenStackClient team meeting back to 1900 UTC starting tomorrow, 05 Mar 2014, still in freenode #openstack-meeting. The agenda for the meeting can be found at https://wiki.openstack.org/wiki/Meetings/OpenStackClien

Re: [openstack-dev] [nova][libvirt] The None and 'none' for CONF.libvirt.cpu_mode

On Wed, Mar 04, 2015 at 05:24:53PM +, Jiang, Yunhong wrote: > Daniel, thanks for your clarification. > > Another related question is, what will be the guest's real cpu model > is the cpu_model is None? This is about a reported regression at The guest CPU will be unspecified - it will be some

Re: [openstack-dev] [Manila] Ceph native driver for manila

On Wed, Mar 4, 2015 at 7:03 AM, Csaba Henk wrote: > > > - Original Message - >> From: "Danny Al-Gaaf" >> To: "Csaba Henk" , "OpenStack Development Mailing List >> (not for usage questions)" >> >> Cc: ceph-de...@vger.kernel.org >> Sent: Wednesday, March 4, 2015 3:26:52 PM >> Subject: Re:

Re: [openstack-dev] [openstackclient] doodle for meeting time selection

+1, lets do this! Lin Hua Cheng wrote on 03/04/2015 12:13:22 PM: > From: Lin Hua Cheng > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 03/04/2015 12:21 PM > Subject: Re: [openstack-dev] [openstackclient] doodle for meeting > time selection > > +1 > > Thanks D

Re: [openstack-dev] [neutron][vpnaas] devstack vpnaas and l3 router

Hi Andreas, vpnaas (i.e. its agent) is a superset of l3-router and it includes the functionality of the later. Hence you just need to configure either one of them. q-l3 if you don't need vpnaas and q-vpn if you need both vpnaas and l3. Hope this helps. - Sridhar On Wed, Mar 4, 2015 at 9:18 AM,

Re: [openstack-dev] [TC][Magnum][Containers] Magnum - OpenStack Containers Service

+TC topic to subject line in accordance with astute suggestions. On Mar 4, 2015, at 8:53 AM, Adrian Otto wrote: > OpenStack Devs, > > There is an item [1] on the 2015-03-10 TC meeting agenda [2] that I would > like to highlight so discussion can commence prior to voting. Magnum’s > contributo

[openstack-dev] [Congress] murano-driver review

Hi core reviewers, I have a review for murano-driver improvement that's waiting for approval from core reviewers. Please take a look at your convenience. I just want to remind so it won't slip your attention. https://review.openstack.org/#/c/158924/ Thanks, -Steven _

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

Excerpts from Thierry Carrez's message of 2015-03-04 02:19:48 -0800: > James Bottomley wrote: > > On Tue, 2015-03-03 at 11:59 +0100, Thierry Carrez wrote: > >> James Bottomley wrote: > >>> Actually, this is possible: look at Linux, it freezes for 10 weeks of a > >>> 12 month release cycle (or 6 wee

Re: [openstack-dev] [cinder]Request to to revisit this patch

Since the Nova side isn't in, and won't land for Kilo, then there is no reason for Cinder to have it for Kilo, as it will simply not work. We can revisit this for the L release if you like. Also, make sure you have 3rd Party CI setup for this driver, or it won't be accepted in the L release ei

Re: [openstack-dev] [nova][libvirt] The None and 'none' for CONF.libvirt.cpu_mode

Daniel, thanks for your clarification. Another related question is, what will be the guest's real cpu model is the cpu_model is None? This is about a reported regression at https://bugs.launchpad.net/nova/+bug/1082414 . When the instance.vcpu_model.mode is None, we should compare the source/tar

Re: [openstack-dev] [nova] Plans to fix numa_topology related issues with migration/resize/evacuate

On 03/04/2015 03:17 PM, Wensley, Barton wrote: > Hi, > > I have been exercising the numa topology related features in kilo (cpu > pinning, numa topology, huge pages) and have seen that there are issues > when an operation moves an instance between compute nodes. In summary, > the numa_topology is

[openstack-dev] [neutron][vpnaas] devstack vpnaas and l3 router

Hello everybody, is there a reason why devstack is only able to either deploy vpnaas or l3-router? Nevertheless both services are enabled in the local.conf on the HowToInstall Page [1]. But the code says it's a either or [2] (line 725). if is_service_enabled q-vpn; then run_process q-vpn "$

[openstack-dev] [oslo][messaging][zmq] Discussion on zmq driver design issues

Hi, By this e-mail I'd like to start a discussion about current zmq driver internal design problems I've found out. I wish to collect here all proposals and known issues. I hope this discussion will be continued on Liberty design summit. And hope it will drive our further zmq driver developmen

Re: [openstack-dev] [openstackclient] doodle for meeting time selection

+1 Thanks Doug for setting up the Doodle. On Wed, Mar 4, 2015 at 8:55 AM, Ian Cordasco wrote: > +1 > > On 3/4/15, 08:01, "Doug Hellmann" wrote: > > > > > > >On Tue, Mar 3, 2015, at 06:17 PM, Dean Troyer wrote: > >> On Thu, Feb 26, 2015 at 3:32 PM, Doug Hellmann > >> wrote: > >> > >> > As we d

Re: [openstack-dev] [openstackclient] doodle for meeting time selection

+1 On 3/4/15, 08:01, "Doug Hellmann" wrote: > > >On Tue, Mar 3, 2015, at 06:17 PM, Dean Troyer wrote: >> On Thu, Feb 26, 2015 at 3:32 PM, Doug Hellmann >> wrote: >> >> > As we discussed in the meeting today, I’ve created a Doodle to >>coordinate >> > a good day and time for future meetings. I

[openstack-dev] [Magnum][Containers] Magnum - OpenStack Containers Service

OpenStack Devs, There is an item [1] on the 2015-03-10 TC meeting agenda [2] that I would like to highlight so discussion can commence prior to voting. Magnum’s contributors have indicated our intent to join the OpenStack namespace in accordance with our new governance requirements [3]. I will

Re: [openstack-dev] [devstack]Specific Juno version

On Tue, 2015-03-03 at 17:42 +0200, Eduard Matei wrote: > Is there a way to specify the Juno version to be installed using > devstack. Let's please reserve this list for discussions about the *future* of OpenStack development, not questions about using its tools. Please, everybody, help us stay

Re: [openstack-dev] [Neutron] Issue when upgrading from Juno to Kilo due to agent report_state RPC namespace patch

To put in another way I think we might say that change 154670 broke backward compatibility on the RPC interface. To be fair this probably happened because RPC interfaces were organised in a way such that this kind of breakage was unavoidable. I think the strategy proposed by Assaf is a viable one.

Re: [openstack-dev] [Neutron] Issue when upgrading from Juno to Kilo due to agent report_state RPC namespace patch

I agree with Assaf, this is an issue across updates, and we may want (if that’s technically possible) to provide access to those functions with/without namespace. Or otherwise think about reverting for now until we find a migration strategy https://review.openstack.org/#/q/status:merged+project

[openstack-dev] [sahara] team meeting Mar 5 1800 UTC

Hi folks, We'll be having the Sahara team meeting 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=20150305T18 -- Sincerely yours, Sergey Lukjanov Sahara Te

Re: [openstack-dev] Python 3 is dead, long live Python 3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2015 03:37 PM, Doug Hellmann wrote: > > > On Tue, Mar 3, 2015, at 07:56 AM, Ihar Hrachyshka wrote: On > 02/02/2015 05:15 PM, Jeremy Stanley wrote: After a long wait and much testing, we've merged a change[1] which moves the remaind

Re: [openstack-dev] [nova][libvirt] The None and 'none' for CONF.libvirt.cpu_mode

On Wed, Mar 04, 2015 at 02:52:06PM +, Jiang, Yunhong wrote: > Hi, Daniel > I'm a bit confused of the None/'none' for CONF.libvirt.cpu_mode. Per my > understanding, None means there is no configuration provided and libvirt will > select the default value based on the virt_type, none mean

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

On Wed, Mar 4, 2015, at 07:24 AM, Alexis Lee wrote: > John Griffith writes: > > ​Should we just rename this thread to "Sensitivity training for > > contributors"? > > Culture plays a role in shaping ones expectations here. I was lucky > enough to grow up in open source culture, so I can identif

[openstack-dev] [Neutron] Issue when upgrading from Juno to Kilo due to agent report_state RPC namespace patch

Hello everyone, I'd like to highlight an issue with: https://review.openstack.org/#/c/154670/ According to my understanding, most deployments upgrade the controllers first and compute/network nodes later. During that time period, all agents will fail to report state as they're sending the report_

Re: [openstack-dev] [Policy][Group-based-policy] SFC USe Case

Venkat, Service Function chaining ("redirect" action) is not supported right now. Yapeng From: groupbasedpolicy-dev-boun...@lists.opendaylight.org [mailto:groupbasedpolicy-dev-boun...@lists.opendaylight.org] On Behalf Of Venkatrangan G - ERS, HCL Tech Sent: Wednesday, March 04, 2015 4:38 AM T

[openstack-dev] [Cinder] scheduler_default_filters are assumed to be work with 'create' only?

Hello Experts, What we're trying to do is that: passing volume-type in get_pools() and filter out the pools matching (well, string matching) with the extra-specs k,v pair that may be present in the volume-type. So we were looking into the create_volume flow. Inside the filter_scheduler's *sched

[openstack-dev] [nova] Plans to fix numa_topology related issues with migration/resize/evacuate

Hi, I have been exercising the numa topology related features in kilo (cpu pinning, numa topology, huge pages) and have seen that there are issues when an operation moves an instance between compute nodes. In summary, the numa_topology is not recalculated for the destination node, which results

Re: [openstack-dev] [keystone] Output on stderr

On Wednesday, March 4, 2015, David Stanek wrote: > > On Wed, Mar 4, 2015 at 6:50 AM, Abhishek Talwar/HYD/TCS < > abhishek.tal...@tcs.com > > wrote: > >> While working on a bug for keystoneclient I have replaced sys.exit with >> return. However, the code reviewers want that the output should be on

[openstack-dev] XenAPI meeting cancelled this week

Sorry for the late notice but due to travel we're cancelling this week's meeting. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

Re: [openstack-dev] [Manila] Ceph native driver for manila

- Original Message - > From: "Danny Al-Gaaf" > To: "Csaba Henk" , "OpenStack Development Mailing List (not > for usage questions)" > > Cc: ceph-de...@vger.kernel.org > Sent: Wednesday, March 4, 2015 3:26:52 PM > Subject: Re: [openstack-dev] [Manila] Ceph native driver for manila > > A

Re: [openstack-dev] [devstack]Specific Juno version

On Wed, Mar 04, 2015 at 02:41:53PM +0200, Eduard Matei wrote: > Hi Ihar, > This is the error i see in c-vol screen: > 2015-03-03 18:39:34.060 DEBUG taskflow.engines.action_engine.runner > [req-87db2771-5c25-4c9b-a3bc-f7a504468315 4af0a30fe2c14deb9f9cf341a97daa9f > 1fbab1e235ff414abf249c741fb3c6c9]

Re: [openstack-dev] [devstack]Specific Juno version

Hi, Indeed CINDER_BRANCH=2014.2.2 did the trick. Will properly report the issues once we start testing on 2014.2.3. Eduard __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@list

[openstack-dev] [nova][libvirt] The None and 'none' for CONF.libvirt.cpu_mode

Hi, Daniel I'm a bit confused of the None/'none' for CONF.libvirt.cpu_mode. Per my understanding, None means there is no configuration provided and libvirt will select the default value based on the virt_type, none means no cpu_mode information should be provided. For the guest, am I rig

Re: [openstack-dev] [Manila] Ceph native driver for manila

Am 04.03.2015 um 15:12 schrieb Csaba Henk: > Hi Danny, > > - Original Message - >> From: "Danny Al-Gaaf" To: "OpenStack >> Development Mailing List (not for usage questions)" >> , ceph-de...@vger.kernel.org >> Sent: Sunday, March 1, 2015 3:07:36 PM Subject: Re: >> [openstack-dev] [Manila

Re: [openstack-dev] [Manila] Ceph native driver for manila

Am 04.03.2015 um 15:18 schrieb Csaba Henk: > Hi Danny, > > - Original Message - >> From: "Danny Al-Gaaf" >> To: "Deepak Shetty" >> Cc: "OpenStack Development Mailing List (not for usage questions)" >> , >> ceph-de...@vger.kernel.org >> Sent: Wednesday, March 4, 2015 3:05:46 PM >> Subjec

Re: [openstack-dev] [Nova][Neutron] out-of-tree plugin for Mech driver/L2 and vif_driver

Hi all, On Wed, Feb 18, 2015 at 04:12:11PM -0330, Brent Eagles wrote: > Hi, > Thanks Maxime. I've made some updates to the etherpad. > (https://etherpad.openstack.org/p/nova_vif_plug_script_spec) > I'm going to start some proof of concept work these evening. If I get > anything worth reading, I

Re: [openstack-dev] [Glance] Core nominations.

On Wed, Mar 04, 2015 at 07:38:42AM -0430, Flavio Percoco wrote: > I'm sorry but no. I don't think there's anything that requires extra > patience than 2 (or even more) cycles without provaiding reviews or > even any kind of active contribution. > > I personally don't think adding new cores without

Re: [openstack-dev] [Glance] Core nominations.

> From: Nikhil Komawar [mailto:nikhil.koma...@rackspace.com] > Sent: Tuesday, March 03, 2015 4:10 PM > To: OpenStack Development Mailing List (not for usage questions); Daniel P. > Berrange > Cc: krag...@gmail.com > Subject: Re: [openstack-dev] [Glance] Core nominations. > > If it was not clear i

Re: [openstack-dev] [Manila] Ceph native driver for manila

Hi Danny, - Original Message - > From: "Danny Al-Gaaf" > To: "Deepak Shetty" > Cc: "OpenStack Development Mailing List (not for usage questions)" > , > ceph-de...@vger.kernel.org > Sent: Wednesday, March 4, 2015 3:05:46 PM > Subject: Re: [openstack-dev] [Manila] Ceph native driver for m

Re: [openstack-dev] [Manila] Ceph native driver for manila

Hi Danny, - Original Message - > From: "Danny Al-Gaaf" > To: "OpenStack Development Mailing List (not for usage questions)" > , > ceph-de...@vger.kernel.org > Sent: Sunday, March 1, 2015 3:07:36 PM > Subject: Re: [openstack-dev] [Manila] Ceph native driver for manila ... > For us securit

[openstack-dev] removal of v3 in tree testing

I have proposed the following patch series to remove the API v3 direct testing in tree - https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:rm_v3_paste,n,z This also removes the /v3 entry from the paste.ini that we ship. I think it's important that we remove th

Re: [openstack-dev] [Manila] Ceph native driver for manila

Am 04.03.2015 um 05:19 schrieb Deepak Shetty: > On Wed, Mar 4, 2015 at 5:10 AM, Danny Al-Gaaf > wrote: >> Am 03.03.2015 um 19:31 schrieb Deepak Shetty: [...] [...] >> >>> I was curious to understand. IIUC Neutron provides private and >>> public networks and for VMs to access external CephFS netw

Re: [openstack-dev] [openstackclient] doodle for meeting time selection

On Tue, Mar 3, 2015, at 06:17 PM, Dean Troyer wrote: > On Thu, Feb 26, 2015 at 3:32 PM, Doug Hellmann > wrote: > > > As we discussed in the meeting today, I’ve created a Doodle to coordinate > > a good day and time for future meetings. I picked a bunch of options based > > on when it looked lik

Re: [openstack-dev] [nova][ec2-api] Functional tests for EC2-API in nova

Agree with dims. On Mon, Mar 2, 2015 at 6:14 PM, Davanum Srinivas wrote: > Alex, > > It's better do a experimental one first before trying to a non-voting: > http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul/layout.yaml#n1509 > > -- dims > > On Mon, Mar 2, 2015 at 7:24 AM, Al

Re: [openstack-dev] [devstack]Specific Juno version

Hi Ihar, This is the error i see in c-vol screen: 2015-03-03 18:39:34.060 DEBUG taskflow.engines.action_engine.runner [req-87db2771-5c25-4c9b-a3bc-f7a504468315 4af0a30fe2c14deb9f9cf341a97daa9f 1fbab1e235ff414abf249c741fb3c6c9] Exiting old state 'WAITING' in response to event 'analyze' from (pid=297

Re: [openstack-dev] [oslo_messaging]Notification listener for nova

I assume you have notifications enabled in nova.conf? See the "Enabling notifications in OpenStack" section http://www.stacktach.com/about.html Oh, there are couple more flags that could be useful too: notify_on_state_change=vm_and_task_state notify_on_any_change=True ? __

Re: [openstack-dev] Gerrit tooling improvements

Salvatore Orlando said on Tue, Mar 03, 2015 at 08:21:08PM +0100: > Is common sense an option here? Common sense is never an option :) Mainly because it's situational and hence arises out of shared culture and expectations, so those not indoctrinated into the group yet get scolded for lacking comm

Re: [openstack-dev] auto-abandon changesets considered harmful (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])

John Griffith writes: > ​Should we just rename this thread to "Sensitivity training for > contributors"? Culture plays a role in shaping ones expectations here. I was lucky enough to grow up in open source culture, so I can identify an automated response easily and I don't take it too seriously.

Re: [openstack-dev] [keystone] Output on stderr

On Wed, Mar 4, 2015 at 6:50 AM, Abhishek Talwar/HYD/TCS < abhishek.tal...@tcs.com> wrote: > While working on a bug for keystoneclient I have replaced sys.exit with > return. However, the code reviewers want that the output should be on > stderr(as sys.exit does). So how can we get the output on st

Re: [openstack-dev] [devstack]Specific Juno version

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2015 04:42 PM, Eduard Matei wrote: > Hi, > > Is there a way to specify the Juno version to be installed using > devstack. For now we can only specify stable/juno *git clone -b > stable/juno https://github.com/openstack-dev/devstack.git > /op

Re: [openstack-dev] [Glance] Core nominations.

On 03/03/15 16:10 +, Nikhil Komawar wrote: If it was not clear in my previous message, I would like to again emphasize that I truly appreciate the vigor and intent behind Flavio's proposal. We need to be proactive and keep making the community better in such regards. However, at the same ti

[openstack-dev] [keystone] Output on stderr

Hi All, While working on a bug for keystoneclient I have replaced sys.exit with return. However, the code reviewers want that the output should be on stderr(as sys.exit does). So how can we get the output on stderr. def do_user_password_update(kc, args): """Update user password.""" user

Re: [openstack-dev] [nova] what's the merge plan for current proposed microversions?

Christopher, Does this "So the plan for assignment of microversion api numbers is the same as what we currently do for db migration changes - take the next one knowing that you may need to rebase if someone else merges before you" mean that I should put 2.2 in my review for now instead of 2.4?

Re: [openstack-dev] [Fuel] Deprecation warnings in python-fuelclient-6.1.*

@romcheg - the idea is to switch partially to new client so keeping one package with two entry points: fuel and fuel_v2. It will be convenient for us to add new commands to fuel_v2 only and switch slowly old commands to new version and add warnings in old client commands. It will give users time to

Re: [openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

James Bottomley wrote: > On Tue, 2015-03-03 at 11:59 +0100, Thierry Carrez wrote: >> James Bottomley wrote: >>> Actually, this is possible: look at Linux, it freezes for 10 weeks of a >>> 12 month release cycle (or 6 weeks of an 8 week one). More on this >>> below. >> >> I'd be careful with compar

Re: [openstack-dev] [Fuel] Deprecation warnings in python-fuelclient-6.1.*

I’d like to resolve some questions: @Przemysław: - We can avoid that message by supplying --quiet. - Changelog is currently managed automatically by PBR so as soon as there is a release there will be a change log - I think #2 can be done along with #3 @Kamil: - The issue is that it’s not pos

Re: [openstack-dev] [nova] blueprint about multiple workers supported in nova-scheduler

Hi, I wonder what is the planned future of the scheduling. The scheduler does a lot of high field number query, which is CPU expensive when you are using sqlalchemy-orm. Does anyone tried to switch those operations to sqlalchemy-core ? The scheduler does lot of thing in the application, like fil

  1   2   >