Re: [openstack-dev] [Dpdk-ovs] [networking-ovs-dpdk]networking-ovs-dpdk configuration on devstack

Hi this mailing list if for OVDK the intel for ovs with the dpdk dpif datapath. The networking-ovs-dpdk repo support ovs from openvswitch.org with the dpdk netdev datapath. Issue and support should be directed to the openstack dev mailing list (openstack-dev@lists.openstack.org) with the

Re: [openstack-dev] [Neutron] Reminder: Team meeting on Monday at 2100 UTC

There is also 'GMT (no daylight saving)’ TZ available in Google Calendar that is identical to UTC for all practical matters. Ihar Carl Baldwin wrote: I've been using Iceland's TZ for this. Seems to work well and handle the TZ changes nicely. Carl On Sat, Nov 7, 2015

[openstack-dev] [fuel] Using upstream packages & modules

Hey folks, I'm testing[0] out flipping our current method of consuming upstream puppet modules from using pinned versions hosted on fuel-infra to be able to use the ones directly from upstream (master). This work is primarily to be closer aligned with the other OpenStack projects as well as

Re: [openstack-dev] [designate] Code Freeze - Happening tomorrow

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Last reminder! See http://graham.hayes.ie/posts/the-big-rename/ for more details On 19/10/15 19:26, Hayes, Graham wrote: > Hi All, > > Just a reminder that at the last IRC meeting [0] we decided a few > things > > 1 - We are skipping 2 weeks or

Re: [openstack-dev] [openstack-ansible][security] Next steps: openstack-ansible-security

On 11/06/2015 05:38 PM, Jesse Pretorius wrote: > While I applaud the idea, changing the current commit integration test is > probably not the best approach. We're in the middle of splitting the roles > out into their own repositories and also extending the gate checks into > multiple use-cases.

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

On Mon, Nov 9, 2015, at 10:24 PM, Kevin Carter wrote: > Hello all, > > The rational behind using a solution like zookeeper makes sense however > in reviewing the thread I found myself asking if there was a better way > to address the problem without the addition of a Java based solution as > the

[openstack-dev] [Nova] Question about server update API

Hello, Nova experts, I'm trying to update Nova server by invoking Nova API interface. However, the API document[1] doesn't describe which properties are updatable by invoking server update API(although I guess 'name' and 'accessIP' updating are supported according to the given example). So my

Re: [openstack-dev] [OpenStack-Infra] Report from Gerrit User Summit

On Mon, Nov 9, 2015 at 2:03 PM James E. Blair wrote: > Khai Do and I attended the Gerrit User Summit this weekend. It was a > very busy weekend indeed with quite a lot of activity in all areas > related to Gerrit. The following is a brief summary of items which > may be of

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

On Mon, Nov 9, 2015, at 10:24 PM, Kevin Carter wrote: > Hello all, > > The rational behind using a solution like zookeeper makes sense however > in reviewing the thread I found myself asking if there was a better way > to address the problem without the addition of a Java based solution as > the

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

On 10 November 2015 at 19:24, Kevin Carter wrote: > Hello all, > > The rational behind using a solution like zookeeper makes sense however in > reviewing the thread I found myself asking if there was a better way to > address the problem without the addition of a

[openstack-dev] [oslo] Graduate apiclient library

Hi Devs, In the Mitaka design summit session [1], it was decided to create a new library apiclient with completely new code (Metadata classes) and copy only code from oslo-incubator/openstack/common/apiclient that is needed by all python clients libraries. We have done extensive analysis to

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

We don't develop features for already released versions… It should be done for master instead. BP On Tue, Nov 10, 2015 at 7:02 AM, Adam Heczko wrote: > Dmitry, > +1 > > Do you plan to port your patchset to future Fuel releases? > > A. > > On Tue, Nov 10, 2015 at 12:14 AM,

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

Hello all, The rational behind using a solution like zookeeper makes sense however in reviewing the thread I found myself asking if there was a better way to address the problem without the addition of a Java based solution as the default. While it has been covered that the current

[openstack-dev] [OpenStack-Infra] Configure gerrit to have two reviewers giving +2

Hello, How do I configure gerrit to have two reviewers giving +2 for a change? Thanks, Maty __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Nova] SR-IOV subteam

On 11/04/2015 07:56 AM, Moshe Levi wrote: > Maybe we can you use the pci- passthrough meeting slot > http://eavesdrop.openstack.org/#PCI_Passthrough_Meeting > It been a long time since we had a meeting. > I think that slot works well (at least for me). I'd maybe change the cadence to

Re: [openstack-dev] [Neutron] Reminder: Team meeting on Monday at 2100 UTC

Hi Team, I won't be able to work for couple of weeks as my mother passed away yesterday. Hope the team will understand and support in this difficult time. Thanks Vikram On 10-Nov-2015 2:00 am, "Ihar Hrachyshka" wrote: > GMT time zone is available by following the official

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

+1 I think that as OpenStack's customer base grows, this is going to become more and more important, and will get the pain of users not getting updates will increase enough that there *will* be a group of engineers willing to do not only backports and releases, but bugfixes in trunk and gate

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 11/9/2015 9:12 PM, Matthew Treinish wrote: On Mon, Nov 09, 2015 at 10:54:43PM +, Kuvaja, Erno wrote: On Mon, Nov 09, 2015 at 05:28:45PM -0500, Doug Hellmann wrote: Excerpts from Matt Riedemann's message of 2015-11-09 16:05:29 -0600: On 11/9/2015 10:41 AM, Thierry Carrez wrote: Hi

Re: [openstack-dev] [nova] Adding a new feature in Kilo. Is it possible?

Hi John, Thanks for doing that. Regards, Michal On 9 November 2015 at 11:16, John Garbutt wrote: > On 4 November 2015 at 15:38, Michał Dubiel wrote: > > Hi John, > > > > Just to let you know, I have just filled in the blueprint here: > > >

[openstack-dev] [tc][all][osprofiler] OSprofiler is dead, long live OSprofiler

Hi stackers, Intro --- It's not a big secret that OpenStack is huge and complicated ecosystem of different services that are working together to implement OpenStack API. For example booting VM is going through many projects and services: nova-api, nova-scheduler, nova-compute, glance-api,

[openstack-dev] [Heat] Admin operations on all tenants

Hello, I was looking to enable admin operations for heat stacks on all tenants. This is useful to do support operations and debug stacks owned by different users. I came across the “heat stack-list -g” command that allows to see all stacks but after that is not possible to “heat stack-show” or

Re: [openstack-dev] [all] [dlm] Zookeeper and openjdk, mythbusted

Joshua Harlow wrote: > [...] > So in order to dispel this, I tried in that session to say 'actually I > have heard nothing saying it doesn't work with openjdk' in that session > but the voices did not seem to hear that (or they were unable to listen > due to there emotions stressed/high). As one

Re: [openstack-dev] [QA][Nova] Tempest Hypervisor Feature Tagging

Thanks John. Maybe we can just start simple: tag each feature in support-matrix.ini and add the metadata to each of the tests that uses that feature. Then we can query that info as we want. I added my comments to that change. Thanks. -rfolco Rafael Folco OpenStack Continuous Integration IBM

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Excerpts from Matthew Treinish's message of 2015-11-09 17:09:54 -0500: > On Mon, Nov 09, 2015 at 05:41:53PM +0100, Thierry Carrez wrote: > > Hi everyone, > > > > A few cycles ago we set up the Release Cycle Management team which was a > > bit of a frankenteam of the things I happened to be

[openstack-dev] [Fuel] Running Fuel node as non-superuser

Hey guys. I've been working on making Fuel not to rely on superuser privileges at least for day-to-day operations. These include: a) running Fuel services (nailgun, astute etc) b) user operations (create env, deploy, update, log in) The reason for this is that many security policies simply do

Re: [openstack-dev] Learning to Debug the Gate

On 11/05/2015 07:45 PM, Anita Kuno wrote: > On 11/03/2015 05:30 PM, Anita Kuno wrote: >> On 11/02/2015 12:39 PM, Anita Kuno wrote: >>> On 10/29/2015 10:42 PM, Anita Kuno wrote: On 10/29/2015 08:27 AM, Anita Kuno wrote: > On 10/28/2015 12:14 AM, Matt Riedemann wrote: >> >> >>

Re: [openstack-dev] [neutron] [networking-powervm] Please create networking-powervm on PyPI

Hi Kyle,    The networking-powervm pypi project is now up [1] with the openstackci user set appropriately. Let me know if you need anything else.   [1] https://pypi.python.org/pypi/networking-powervm   Regards,   Adam Reznechek   From:   Kyle Mestery To:     "OpenStack

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Excerpts from Matt Riedemann's message of 2015-11-09 16:05:29 -0600: > > On 11/9/2015 10:41 AM, Thierry Carrez wrote: > > Hi everyone, > > > > A few cycles ago we set up the Release Cycle Management team which was a > > bit of a frankenteam of the things I happened to be leading: release > >

Re: [openstack-dev] [stable][infra][neutron] ZUUL_BRANCH not set for periodic stable jobs

Jeremy Stanley wrote: On 2015-11-09 17:31:00 +0100 (+0100), Ihar Hrachyshka wrote: [...] From the failure log, I determined that the tests fail because they assume neutron/liberty code, but actually run against neutron/master (that does not have that

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

> -Original Message- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: 09 November 2015 16:42 > To: OpenStack Development Mailing List > Subject: [openstack-dev] [stable] Making stable maintenance its own > OpenStack project team > > Hi everyone, > > A few cycles ago we set

Re: [openstack-dev] [neutron][qos][fwaas] service groups vs. traffic classifiers

I agree that the timing is good for FWaaS to look at the possibility of using a common traffic classifier in the new FWaaS 2.0 API. If we can agree on a definition and get moving on an implementation in the Mitaka time frame, we could avoid a painful API migration later on. Sean has started

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

> -Original Message- > From: Matthew Treinish [mailto:mtrein...@kortar.org] > Sent: 09 November 2015 22:40 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [stable] Making stable maintenance its own > OpenStack project team > > On Mon, Nov

[openstack-dev] Couldn't ping/ssh cirros instance using its floating ip

Hi there, In a fresh devstack(master branch) install, 1. I booted up a cirros instance and associated it with a floating ip. 2. Created a security group rule to allow tcp port 22 and associated it with the nova instance 3. From the qrouter namespace, I can ping both the private and fip

Re: [openstack-dev] [Neutron][Kuryr] - IRC Meetings

I talked with Toni and the next meeting is scheduled in the regular time. So we have a meeting at 15:00 UTC on 9th November this week and the next one will be scheduled at 3:00 UTC on 17th November. Best regards, Taku Fukushima On Mon, Nov 9, 2015 at 12:52 PM, Taku Fukushima

Re: [openstack-dev] [Openstack-operators] [logs] Neutron not logging user information on wsgi requests by default

Kris G. Lindgren wrote: Hello all, I noticed the otherday that in our Openstack install (Kilo) Neutron seems to be the only project that was not logging the username/tenant information on every wsgi request. Nova/Glance/heat all log a username and/or project on

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

On 11/03/2015 08:46 PM, Doug Hellmann wrote: As we discussed at the summit, the release management team is modifying our change management tracking tools and processes this cycle. This email is the official announcement of those changes, with more detail than we provided at the summit. In past

Re: [openstack-dev] [Openstack-operators] Performance Team summit session results

Folks, due to the doodle 3:00 - 4:00 UTC Tuesdays (starting from tomorrow) is ok for all voted people. Although for the US folks with PST time zone it'll be very early due to the time zone change happened for US on November, 1st. Still hope seeing

Re: [openstack-dev] [stable][all] Keeping Juno "alive" for longer.

Hiya, On 7/11/2015 06:42, Sean Dague wrote: On 11/06/2015 01:15 AM, Tony Breeds wrote: Hello all, I'll start by acknowledging that this is a big and complex issue and I do not claim to be across all the view points, nor do I claim to be particularly persuasive ;P Having stated that, I'd like

[openstack-dev] [oslo][messaging] Summary for drivers discussion

Hi folks, Just wanted to sum up a little bit from the discussions at Mitaka summit (etherpad available [0]). General for oslo.messaging: - Implement single-machine failover test suite using multiprocessing + iptables for network failures emulation. Needed for emulating different

Re: [openstack-dev] [neutron] [networking-powervm] Please create networking-powervm on PyPI

Thanks Adam, that should be all that's required. I unblocked [1] after verifying the PyPI config. [1] https://review.openstack.org/#/c/233466/ On Mon, Nov 9, 2015 at 4:15 PM, Adam D Reznechek wrote: > Hi Kyle, > > The networking-powervm pypi project is now up [1] with the

Re: [openstack-dev] [nova] Proposal to add Alex Xu to nova-core

On 11/6/2015 9:32 AM, John Garbutt wrote: Hi, I propose we add Alex Xu[1] to nova-core. Over the last few cycles he has consistently been doing great work, including some quality reviews, particularly around the API. Please respond with comments, +1s, or objections within one week. Many

Re: [openstack-dev] [nova] Proposal to add Sylvain Bauza to nova-core

On 11/6/2015 9:32 AM, John Garbutt wrote: Hi, I propose we add Sylvain Bauza[1] to nova-core. Over the last few cycles he has consistently been doing great work, including some quality reviews, particularly around the Scheduler. Please respond with comments, +1s, or objections within one

Re: [openstack-dev] Introducing Lwood - a weekly summary of openstack-dev traffic

Hiya, Thankyou for the positive feedback received thus far for Lwood [1] I won't trouble the list with ongoing weekly posts for each edition but did want to flag the existence of the summaries one more time being mindful of the vagaries of reading the list during Summit :) For reference

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On Mon, Nov 09, 2015 at 05:28:45PM -0500, Doug Hellmann wrote: > Excerpts from Matt Riedemann's message of 2015-11-09 16:05:29 -0600: > > > > On 11/9/2015 10:41 AM, Thierry Carrez wrote: > > > Hi everyone, > > > > > > A few cycles ago we set up the Release Cycle Management team which was a > > >

Re: [openstack-dev] [nova][api]

On 9 November 2015 at 06:29, Tony Breeds wrote: > On Fri, Nov 06, 2015 at 12:30:19PM +, John Garbutt wrote: > >> Ideally, I would like us to fill out that pagination part first. > > It seems the person leading this within the API-WG is AWOL so ... > >> If we can't get

Re: [openstack-dev] [nova][bugs] Weekly Status Report

On 6 November 2015 at 21:39, Augustina Ragwitz wrote: > I totally second that on the low-hanging-fruit tag! And I'm happy to help > with some of the triaging. I'm still pretty new to Nova so I'm not sure how > helpful I'll be but it seems like a good task for getting to know

[openstack-dev] Error: Actor crashed

Hi all, I was trying running stable/kilo branch infrastructure with the following setting of chef dk: * Chef Development Kit Version: 0.9.0 * chef-client version: 12.5.1 * berks version: 4.0.1 * kitchen version: 1.4.2 But when I run the command: * chef exec rake berks_vendor I got

Re: [openstack-dev] [Heat] Deprecate heat-keystone-setup

On Sun, Nov 08, 2015 at 09:38:42PM +0800, xuanlangjian wrote: >I would like to deprecate heat-keystone-setup tool in bin folder, because >it's still using keystone client for execute keystone commands, and I >dona**t know if anyone still needs it. If no one use it, I think ita**s >

Re: [openstack-dev] [nova] Adding a new feature in Kilo. Is it possible?

On 4 November 2015 at 15:38, Michał Dubiel wrote: > Hi John, > > Just to let you know, I have just filled in the blueprint here: > https://blueprints.launchpad.net/nova/+spec/libvirt-vhostuser-vrouter-vif I have added this blueprint to the etherpad, to be reviewed at the next

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

Hi, Thanks for the reply, for some scenario, launching an new instance is easier. But for production deployment, an instance may contain a large number of data such as keypairs, metadata, bdm etc. and it may have multiple internet interfaces that are connected to multiple networks. That is to

[openstack-dev] [QA][Tempest] Working items for service clients

Hi, As we discussed in Tokyo summit[1], we need to implement service clients for tempest-lib. And we can get many volunteers for doing that. I have prepared an etherpad for managing this working items on the following: https://etherpad.openstack.org/p/mitaka-tempest-service-clients If you are

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

Cinder has, and probably will, continue to resist operations that are only added so that some other operation can be done while 'keeping the volume UID'. It is not a cloud mentality, and it leads to increased code complexity and in several cases risk of data loss within cinder. On 9 November 2015

Re: [openstack-dev] [Fuel] Master node upgrade

Looks like most people thing that building backup/re-install approach is more viable. So, we certainly need to invent completely new upgrade from and thus my suggestion is disable building/testing upgrade tarball right now, because anyway it makes no sense. Vladimir Kozhukalov On Fri, Nov 6,

Re: [openstack-dev] [nova][api]

Hi, Wouldn't be easier to change the database, create an index, maybe? On Mon, Nov 9, 2015 at 8:29 AM, Tony Breeds wrote: > On Fri, Nov 06, 2015 at 12:30:19PM +, John Garbutt wrote: > > > Ideally, I would like us to fill out that pagination part first. > > It seems

Re: [openstack-dev] [tc][all][osprofiler] OSprofiler is dead, long live OSprofiler

Boris, I believe finishing work related to OSprofiler development is crucial for the teams like Performance Team kicked off during the Tokyo summit. I'll raise question is people are interested in taking part in its development tomorrow on IRC meeting

Re: [openstack-dev] [Openstack-operators] [tc][all][osprofiler] OSprofiler is dead, long live OSprofiler

(Sorry Boris, now with correct CC list.) Boris Pavlovic wrote: Hi stackers, Intro --- It's not a big secret that OpenStack is huge and complicated ecosystem of different services that are working together to implement OpenStack API. For example booting VM is going

Re: [openstack-dev] [nova] Proposal to add Alex Xu to nova-core

On 11/06/2015 03:32 PM, John Garbutt wrote: > Hi, > > I propose we add Alex Xu[1] to nova-core. > +1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [nova] Proposal to add Sylvain Bauza to nova-core

On 11/06/2015 03:32 PM, John Garbutt wrote: > Hi, > > I propose we add Sylvain Bauza[1] to nova-core. > +1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] Couldn't ping/ssh cirros instance using its floating ip

You will have a much better time on ask.openstack.org - It's a super active Q site for questions exactly like this one. You posted your question to a developers mailing list where we choose release names and make other ultra important mission critical decisions. On Mon, Nov 9, 2015 at 6:34 PM,

Re: [openstack-dev] [stable][infra][neutron] ZUUL_BRANCH not set for periodic stable jobs

On Mon, Nov 9, 2015 at 5:30 PM, Ihar Hrachyshka wrote: > Jeremy Stanley wrote: > >> On 2015-11-09 17:31:00 +0100 (+0100), Ihar Hrachyshka wrote: >> [...] >>> >>> From the failure log, I determined that the tests fail because they >>> assume >>>

Re: [openstack-dev] Couldn't ping/ssh cirros instance using its floating ip

Thanks Assaf. Will post my question there. > On Nov 9, 2015, at 5:07 PM, Assaf Muller wrote: > > You will have a much better time on ask.openstack.org - It's a super > active Q site > for questions exactly like this one. You posted your question to a > developers mailing

<    1   2