Re: [openstack-dev] [cinder] Testing Cinder upgrades - c-bak upgrade

@ DuncanT and @dule: I noticed from IRC log that you are discussing about c-bak upgrade, and I am working on this, please see following message. Hope I don't miss anything. As you know, currently c-bak and c-vol are in same nodes. c-bak depends on c-vol service. But it is not necessary that

Re: [openstack-dev] [Neutron] OVS flow modification performance

I don't think 400 flows can show the difference , do you have setup any tunnel peer? In fact we may set the network type as "vxlan", then make a fake MD simulate sending l2pop fdb add messages, to push ten's of thousands flows into the testing ovs agent.

Re: [openstack-dev] [heat] spec-lite for simple feature requests

+1 And how everyone think about if we deprecate to use Blueprint in Launchpad and use bug system instead? If this make more sense, we can move all spec to bug system, lite or not. I have saw Ironic and some other project discuss about doing it. Most of the reason is they think Launchpad bug

[Openstack] [Diversity] OpenStack Diversity Working Group Meetings

Hello Everyone, I would like to invite everyone to participate in Diversity Working Group. To join, sign up for foundat...@openstack.org mailing list, attend meetings, or find us on #openstack-diversity IRC channel. Diversity working group holds weekly meetings at alternating times. We are

Re: [openstack-dev] [tricircle] weekly meeting of Jan.20

Hi Joe, I was busy working on other business did not get the chance to join the meeting, do we have a minute of the last meeting ? On Tue, Jan 19, 2016 at 9:45 PM, joehuang wrote: > Hello, > > After the stateless design was moved to the master branch, we also move > the

Re: [openstack-dev] [ceilometer] :Regarding wild card configuration in pipeline.yaml

Hi , Just to reframe my query: I have a meter subscription m1.* for publisher p1 and I need a subset of m1.* notifications for ex:m1.xyz.* for publisher p2. If we add p2 to already exisiting sink along with p1, p2 will get other notification's along with m1.xyz.* which are not needed for

Re: [openstack-dev] [neutron][api] GET call with huge argument list

Thank you all for the comments. The client that we expect to call this API with thousands of network-ids is nova-scheduler. Since this call is happening in the middle of scheduling, we don't want to spend time in paginating or sending multiple requests. I have tens of thousands of networks and

[openstack-dev] [Congress] Mid-cycle sprint and next week's IRC

Just a reminder that next week Jan 26-Jan 28 is the Congress mid-cycle Sprint in the Bay Area. It's not too late to attend. It'd be best to register, but we'd love to have you in any case. More details here: https://wiki.openstack.org/wiki/Sprints/CongressMitakaSprint Also, since we're at the

[openstack-dev] [nova] Live migration with the VMware driver

Hi, I posted a patch which implements live migration with the VMware driver: https://review.openstack.org/#/c/270116 The assumption is that each nova-compute is managing a cluster in the same vCenter server. In that case the only information that we need from the destination node is the

[openstack-dev] [Nova] PCI CI is down

Hey Nova, It seems the a bug [1] sneaked in that made the PCI CI jobs fail 100% of the time so they got turned off. Fix for the bug should be making it's way through the queue soon, but it was hinted on the review that there may be further problems. I'd like to help fix these issues ASAP as the

Re: [openstack-dev] [gate] large-ops failure spike

On Wed, Jan 20, 2016 at 07:45:16AM -0500, Sean Dague wrote: > The large-ops jobs jumped to a 50% fail in check, 25% fail in gate in > the last 24 hours. > > http://tinyurl.com/j5u4nf5 > > There isn't an obvious culprit at this point. I spent some time this There is a very obvious culprit, pip 8

Re: [openstack-dev] [Nova] PCI CI is down

Nikola, I guess Mellanox CI ( running, failing , non-voting ) can assist on this issue. Since we found it and opened a bug. -Original Message- From: Nikola Đipanov [mailto:ndipa...@redhat.com] Sent: Wednesday, January 20, 2016 4:41 PM To: OpenStack Development Mailing List

Re: [openstack-dev] [fuel][plugins] Detached components plugin update requirement

If there is a new requirement for plugin developers, I would also make sure it is documented here: https://wiki.openstack.org/wiki/Fuel/Plugins *From:* Sergii Golovatiuk [mailto:sgolovat...@mirantis.com] *Sent:* Wednesday, January 20, 2016 10:59 AM *To:* OpenStack Development Mailing List (not

Re: [openstack-dev] [ceilometer] :Regarding wild card configuration in pipeline.yaml

hi, i don't completely recall why we don't allow wildcarded exclude and include meters. it's probably because there's ambiguity of ordering of wildcard which can lead to different filter results. someone can correct me, but i don't think there's a strict requirement that stops us from

[openstack-dev] [glance][drivers] Re-think the Glance Driver's team

Yo! Glancers, Gonna cut the chase: I think we would do a better job on the specs (and light specs) side if we get rid of the Glance Drivers team and encourage everyone (especially from the core team) to weight in. As it stands right now, the Glance Drivers team is the bottleneck for new

[Openstack] Feb 1 Deadline Call for Speakers - OpenStack Summit Austin

Hi everyone, Monday, February 1 at 11:59pm PST is the deadline to submit a speaking proposal for the Austin OpenStack Summit. Submit your speaking proposals HERE ! Speakers are limited to a maximum of THREE submissions total.

Re: [openstack-dev] [Oslo] Improving deprecated options identification and documentation

Markus, > > Yes, in what release it is to be removed, e.g. Mitaka. So when is > > that release cycle, i.e. now once removed there is no record. > > The information at which point in time a removal will happen can be > derived from a combination of: > * the "Deprecation Notes" (e.g. Nova's at

[openstack-dev] [fuel][plugin] node_role only need when attribute false - where is the fuel plugin parser code?

Hey, I am developing on a fuel plugin at the moment. (fuel-plugin-opendaylight) In node_roles.yaml I would like to define something similar to: opendaylight: limits: max: 1 min: if "attributes:use_external_odl == true" then 0 else 1 attributes:use_external_odl comes from the

Re: [openstack-dev] [nova][bugs] nova-bugs-team IRC meeting

Due to other meetings which merged since the announcement, the IRC meeting patch [1] I pushed proposes now: Tuesday 1000 UTC #openstack-meeting beweekly-odd Tuesday 1700 UTC #openstack-meeting beweekly-even February the 9th at 1000 UTC will be the first kickoff meeting. I'll have an

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

On 20 January 2016 at 08:20, Edgar Magana wrote: > Just providing support for Kyle’s proposal! > It is working very well for other teams such as nova, docs between others. > At risk of stating the obvious, not every project is equal, and as I mentioned in an earlier

Re: [openstack-dev] [fuel][plugins] Detached components plugin update requirement

Sergii, I am curious - does it mean that the plugins will stop working with older versions of Fuel? Thanks, Dmitry 2016-01-20 19:58 GMT+03:00 Sergii Golovatiuk : > Hi, > > Recently I merged the change to master and 8.0 that moves one task from > Nailgun to Library

[Openstack-operators] Draft Agenda for MAN Ops Meetup (Feb 15, 16)

Hi all, Matt, Nick and myself took some time to take our suggestions from the etherpad and attempted to wrangle them into something that would fit in the space we have over 2 days. As a reminder, we have two different kind of sessions - General Sessions, which are discussions for the

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

This is something I'd really like to see happen. It's an idea we've been tossing around for the Keystone project, or at least a release with minimal features, maybe 1 or 2. More comments in line Steve Martinelli Keystone PTL Flavio Percoco wrote on 2016/01/20 08:23:02 AM: >

[openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

Hi all, Unit tests on CI and gate bottleneck are really slowing down commit progress. We recently had a meeting to discuss possible ways to improve this, including symlinks, caching git repositories, etc, but one thing we can do much faster is to simply disable 3.3-3.7 puppet jobs. We don't

Re: [openstack-dev] [Neutron] MTU configuration pain

On Tue, Jan 19, 2016 at 08:15:18AM EST, Matt Kassawara wrote: > No. However, we ought to determine what happens when both DHCP and RA > advertise it. We'd have to look at the RFCs for how hosts are supposed to behave since IPv6 has a minimum MTU of 1280 bytes while IPv4's minimum mtu is 576 (what

Re: [Openstack] DVR and public IP consumption

James Denton writes: > > > > Hi, > > >> You cannot get around each tenant gateway router consuming an extra public IP address itself as far as I know. > > Almost. With DVR, a FIP namespace is created on compute nodes, with one FIP namespace per external network. The FIP

Re: [openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

+1 for 3.3, 3.4, 3.8 and 4 -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Jan 20, 2016 at 6:12 PM, Alex Schultz wrote: > On Wed, Jan 20, 2016 at 9:02 AM, Matthew Mosesohn > wrote: > > Hi all, > > > > Unit tests on CI and

[openstack-dev] [Neutron] Drivers meeting calendar update

Hi folks, At request of a team member, we've been looking into other time slots [1] I am afraid, there is no way we can please everyone, and we may want to revise the slot in function of the location of the team members in the future. Let me remind that we look at team membership [2] regularly

Re: [Openstack] DVR and public IP consumption

Tom Verdaat writes: > > > > Hi Tomas, > Actually the networking nodes, and in a DVR scenario the compute nodes, don't need a public IP assigned to the node itself. All they need is a networking interface connected to the "public" network. Only tenant routers set as a gateway consume

Re: [openstack-dev] swift missing X-Timestamp header commit review

On Wed, 20 Jan 2016 13:46:13 +0200 (EET) Mustafa ÇELİK (BİLGEM-BTE) wrote: > commit-1: This one is my patch for the bug. > https://review.openstack.org/#/c/268163/ > I need someone to review my commit-1. > Can somebody help me with code-review? Sure... I am

Re: [Openstack] CEPH Speed Limit

On 1/19/16 5:28 PM, John van Ommen wrote: I have a client who isn't happy with the performance of their storage. The client is currently running a mix of SAS HDDs and SATA SSDs. They wanted to remove the SAS HDDs and replace them with SSDs, so the entire array would be SSDs. I was running

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On 20 January 2016 at 10:03, Jiří Stránský wrote: > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: > >> - Original Message - >> >>> On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: >>> - Original Message - > On Wed, Jan 13, 2016 at

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

Just providing support for Kyle’s proposal! It is working very well for other teams such as nova, docs between others. Edgar On 1/20/16, 3:55 AM, "Rossella Sblendido" wrote: > > >On 01/19/2016 05:14 PM, Ihar Hrachyshka wrote: >> Rossella Sblendido

Re: [openstack-dev] [Nova] PCI CI is down

On 01/20/2016 10:14 AM, Nikola Đipanov wrote: > On 01/20/2016 03:03 PM, Lenny Verkhovsky wrote: >> Nikola, >> I guess Mellanox CI ( running, failing , non-voting ) can assist on this >> issue. >> Since we found it and opened a bug. >> > > Ah - I was not aware that they use the same

[openstack-dev] [fuel][plugins] Detached components plugin update requirement

Hi, Recently I merged the change to master and 8.0 that moves one task from Nailgun to Library [1]. Actually, it replaces [2] to allow operator more flexibility with repository management. However, it affects the detached components as they will require one more task to add as written at [3].

Re: [openstack-dev] [Nova] PCI CI is down

On 01/20/2016 03:03 PM, Lenny Verkhovsky wrote: > Nikola, > I guess Mellanox CI ( running, failing , non-voting ) can assist on this > issue. > Since we found it and opened a bug. > Ah - I was not aware that they use the same hw/configuration. Will take a look! Thanks, N. > > -Original

[openstack-dev] [openstack-ansible][designate] : Ansible Designate Role

Hi Jesse, Thanks for checking out the files on https://github.com/sharmaswati6/designate_files The Designate roles are still not fully completed to be contributed on Gerrit. While the Designate services seem to up and running now in its container, I am stuck up with one last issue for the

Re: [openstack-dev] [Neutron] Removing ml2_type_vxlan.vxlan_group parameter?

On Wed, Jan 20, 2016 at 04:11:49AM EST, Ihar Hrachyshka wrote: > As I commented in gerrit, agents are not supposed to load ml2 config files, > so if that’s the approach you suggest, I don’t think it’s the right one. > Though if we talk about server passing the value into agents by some other >

[openstack-announce] [release][heat] heat release 6.0.0.0b2 (mitaka)

We are tickled pink to announce the release of: heat 6.0.0.0b2: OpenStack Orchestration This release is part of the mitaka release series. With package available at: https://pypi.python.org/pypi/heat For more details, please see below. Changes in heat 6.0.0.0b1..6.0.0.0b2

[openstack-dev] [Nova] Cells v2 remaining Mitaka work

Hi all, I just wanted to send out a quick status report on what work is in progress in Mitaka and what work is still outstanding. This is not inclusive of all work that has occurred this cycle. There are some reviews up from CERN to create flavor tables in the nova_api database and begin the

[openstack-announce] [release][stable][heat] python-heatclient release 0.8.1 (liberty)

We are glad to announce the release of: python-heatclient 0.8.1: OpenStack Orchestration API Client Library This release is part of the liberty stable release series. With source available at: https://git.openstack.org/cgit/openstack/python-heatclient With package available at:

Re: [openstack-dev] [nova][bugs] help needed: volunteers for bug skimming (1 week)

Nova needs another volunteer for the weekly "bug skimming duty". Please add your name(s) to the wiki [1] or mention it on the Nova team IRC meeting on Thursday. If there are questions during your duty you can ping me every time in IRC (I'm in UTC+1). Thanks to cihand, auggy and rpodolyaka for

Re: [openstack-dev] [Neutron] MTU configuration pain

On 01/20/2016 08:56 AM, Sean M. Collins wrote: On Tue, Jan 19, 2016 at 08:15:18AM EST, Matt Kassawara wrote: No. However, we ought to determine what happens when both DHCP and RA advertise it. We'd have to look at the RFCs for how hosts are supposed to behave since IPv6 has a minimum MTU of

Re: [Openstack] DVR and public IP consumption

Hi Tomas, Actually the networking nodes, and in a DVR scenario the compute nodes, don't need a public IP assigned to the node itself. All they need is a networking interface connected to the "public" network. Only tenant routers set as a gateway consume one public IP address each as overhead. You

Re: [openstack-dev] [gate] large-ops failure spike

On 01/20/2016 10:03 AM, Matthew Treinish wrote: > On Wed, Jan 20, 2016 at 07:45:16AM -0500, Sean Dague wrote: >> The large-ops jobs jumped to a 50% fail in check, 25% fail in gate in >> the last 24 hours. >> >> http://tinyurl.com/j5u4nf5 >> >> There isn't an obvious culprit at this point. I spent

Re: [openstack-dev] [Neutron] MTU configuration pain

Maybe it will do the obvious thing and add them together. ;) On Jan 20, 2016 12:03, "Sean M. Collins" wrote: > On Tue, Jan 19, 2016 at 08:15:18AM EST, Matt Kassawara wrote: > > No. However, we ought to determine what happens when both DHCP and RA > > advertise it. > > We'd

Re: [openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

On Wed, Jan 20, 2016 at 9:02 AM, Matthew Mosesohn wrote: > Hi all, > > Unit tests on CI and gate bottleneck are really slowing down commit > progress. We recently had a meeting to discuss possible ways to improve > this, including symlinks, caching git repositories, etc,

[openstack-dev] [Monasca] Monasca mid-cycle meetup

Hi Everyone, The Monasca Mitaka Mid-cycle Meetup will be hosted via WebEx using the contact information below on Wednesday February 3rd and Thursday February 4th, 2016. The Etherpad with additional information is at, https://etherpad.openstack.org/p/monasca_mitaka_midcycle. The meeting is

Re: [Openstack] [Help-Ask]creating a Cinder volume problem --> volume status is stuck in creating status......

디케이 writes: > > > Hello, I have a problem about cinder volume, > After cinder create command, new volume status is stuck in creating status. is not changed to available or error.. > What part of service should I focous on ???..   lvm? rabbit? cinder-api? cinder-volume?

[openstack-dev] [nova] Feature suggestion - API for creating VM without powering it up

Hi, I would like to suggest a feature in nova to allow creating a VM, without powering it up. If the user will be able to create a stopped VM, it will allow for better flexibility and user automation. I can personally say such a feature would greatly improve comfortability of my work with nova

Re: [OpenStack-Infra] JJB 1.4.0 delete-all no longer deletes jobs

No flags it's simply just a call to: $ jenkins-jobs delete-all Thanh On 19 January 2016 at 13:00, Wayne Warren wrote: > What command line flags did you pass? > > I don't generally use this or the 'delete' subcommand, preferring > instead to use python-jenkins

Re: [openstack-dev] [gate] large-ops failure spike

On Wed, Jan 20, 2016 at 07:45:16AM -0500, Sean Dague wrote: > The large-ops jobs jumped to a 50% fail in check, 25% fail in gate in > the last 24 hours. > > http://tinyurl.com/j5u4nf5 > > There isn't an obvious culprit at this point. I spent some time this > morning digging into it a bit.

Re: [openstack-dev] [Neutron] Removing ml2_type_vxlan.vxlan_group parameter?

This option is used to configure a global multicast group IP for VXLAN networks. The Cisco Nexus1000V mech driver uses the IP address from this config option when creating a VXLAN network in multicast mode. If this config option has an empty value, it is interpreted as selecting unicast mode for

Re: [openstack-dev] [fuel][plugins] Detached components plugin update requirement

Plugin master branch won't be compatible with older versions. Though the plugin developer may create stable branch to have compatibility with older versions. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Jan 20, 2016 at 6:41 PM, Dmitry Mescheryakov <

Re: [openstack-dev] [Neutron] Removing ml2_type_vxlan.vxlan_group parameter?

On Wed, Jan 20, 2016 at 02:24:35PM EST, Sourabh Patwardhan wrote: > This option is used to configure a global multicast group IP for VXLAN > networks. > The Cisco Nexus1000V mech driver uses the IP address from this config > option when creating a VXLAN network in multicast mode. Right - and I

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

Excerpts from Ian Cordasco's message of 2016-01-20 18:38:26 +: > -Original Message- > From: Flavio Percoco > Reply: Flavio Percoco , OpenStack Development Mailing List > (not for usage questions) > Date: 

Re: [openstack-dev] [keystone][neutron][requirements] - keystonemiddleware-4.1.0 performance regression

So this was due to a change in keystonemiddleware. We stopped doing in-memory caching of tokens per process, per worker by default [1]. There are a couple of reasons: 1) in-memory caching produced unreliable validation because some processed may have a cache, some may not 2) in-memory caching was

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 01/20/2016 01:30 PM, Doug Hellmann wrote: Excerpts from Flavio Percoco's message of 2016-01-20 13:23:02 -0430: Greetings, At the Tokyo summit, we discussed OpenStack's development themes in a cross-project session. In this session a group of folks started discussing what topics the overall

Re: [openstack-dev] [nova] Bulk Instance Delete support

On Tue, 19 Jan 2016 09:37:17 -0500 Sean Dague wrote: > I think it's also important to think about what efficiency might be > gained, which isn't much. DELETE is an async action that returns 202. If > you care about those resources or quota so you can build more, you need > to

Re: [openstack-dev] [fuel][plugin] node_role only need when attribute false - where is the fuel plugin parser code?

Hi Nikolas, I'm not exactly sure about your case, but you should try something like this: https://github.com/openstack/fuel-plugin-detach-keystone/blob/master/node_roles.yaml#L14-L15 restrictions: - condition: "settings:opendaylight_plugin:use_external_odl == false" - message: "OpenDaylight role

Re: [openstack-dev] Spam of patches (was: [trove][neutron][cinder][swift][ceilometer][nova][keystone][sahara][glance][neutron-lbaas][imm] stylistic changes to code, how do we handle them?)

On 15:32 Jan 12, Julien Danjou wrote: > On Tue, Jan 12 2016, Amrith Kumar wrote: > > > My question to the ML is this, should stylistic changes of this kind be > > handled > > in a consistent way across all projects, maybe with a hacking rule and some > > discussion on the ML first? After all, if

[Openstack] Cinder quota-show demo error

Hello all, does anyone have an suggestion on this error? [root@osc1 ~(keystone_admin)]# cinder quota-show demo ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-4a681bb0-a0b5-4325-8c12-3f48659a42f1) [root@osc1

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

- Original Message - > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: > > - Original Message - > >> On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: > >>> > >>> - Original Message - > On Wed, Jan 13, 2016 at 04:41:28AM -0500, Tzu-Mainn Chen wrote: > > Hey all, >

[openstack-announce] [OSSA 2016-004] Swift proxy-server DoS through Large Object (CVE-2016-0737, CVE-2016-0738)

== OSSA-2016-004: Swift proxy-server DoS through Large Object == :Date: January 20, 2016 :CVE: CVE-2016-0737 (client to proxy), CVE-2016-0738 (proxy to server) Affects ~~~ -

[openstack-dev] [release][oslo] oslo.config release 3.3.0 (mitaka)

We are psyched to announce the release of: oslo.config 3.3.0: Oslo Configuration API This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.config With package available at: https://pypi.python.org/pypi/oslo.config

[Openstack] [OSSA 2016-004] Swift proxy-server DoS through Large Object (CVE-2016-0737, CVE-2016-0738)

== OSSA-2016-004: Swift proxy-server DoS through Large Object == :Date: January 20, 2016 :CVE: CVE-2016-0737 (client to proxy), CVE-2016-0738 (proxy to server) Affects ~~~ -

Re: [openstack-dev] [fuel][plugins] Detached components plugin update requirement

2016-01-20 22:34 GMT+03:00 Sergii Golovatiuk : > Plugin master branch won't be compatible with older versions. Though the > plugin developer may create stable branch to have compatibility with older > versions. > Got it, thank you for clarifying this. Dmitry > -- >

[openstack-dev] nova cli commands fail with 404. devstack installation from today

Installed devstack today, this morning actually, and most everything works except simple nova cli commands, nova image list, list, flavor-list all fail) glance ok, nuetron ok, As an example, nova image list returns: devstack$ nova image list ERROR (NotFound): The resource could not be

Re: [openstack-dev] [neutron][api] GET call with huge argument list

So having a URI too long error is, in this case, likely an indication that you're requesting too many things at once. You could: 1. Request 100 at a time in parallel 2. Find a query that would give you all those networks & page through the reply 3. Page through all the user's networks and

Re: [openstack-dev] [keystone][neutron][requirements] - keystonemiddleware-4.1.0 performance regression

On 01/20/2016 02:59 PM, Morgan Fainberg wrote: > So this was due to a change in keystonemiddleware. We stopped doing > in-memory caching of tokens per process, per worker by default [1]. > There are a couple of reasons: > > 1) in-memory caching produced unreliable validation because some >

Re: [openstack-dev] [ceilometer] ceilometer Floatingip Pollster change

i guess i should probably add that the current pollster doesn't work because of limitation in nova api[1]. if we want to support discovery of whether nova-network or neutron is used, the existing pollster and nova-api still needs to be fixed. [1]

Re: [openstack-dev] [Oslo][all] os-profiler under Oslo umbrella

Dims, Great news! =) When we address some small issues I'll make demo. Best regards, Boris Pavlovic On Wed, Jan 13, 2016 at 5:06 AM, Davanum Srinivas wrote: > Team, > > Oslo folks have voted[1] to be the home for the osprofiler project[2]. > Several projects are already

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 20/01/16 18:38 +, Ian Cordasco wrote: -Original Message- From: Flavio Percoco Reply: Flavio Percoco , OpenStack Development Mailing List (not for usage questions) Date: January 20, 2016 at 11:57:56 To: 

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 20/01/16 13:44 -0500, Steve Martinelli wrote: This is something I'd really like to see happen. It's an idea we've been tossing around for the Keystone project, or at least a release with minimal features, maybe 1 or 2. More comments in line Steve Martinelli Keystone PTL Flavio Percoco

Re: [openstack-dev] [keystone][neutron][requirements] - keystonemiddleware-4.1.0 performance regression

As promised here are the fixes: https://review.openstack.org/#/q/Ifc17c27744dac5ad55e84752ca6f68169c2f5a86,n,z Proposed to both master and liberty. On Wed, Jan 20, 2016 at 12:15 PM, Sean Dague wrote: > On 01/20/2016 02:59 PM, Morgan Fainberg wrote: > > So this was due to a

[openstack-dev] [heat] spec-lite for simple feature requests

Hi All, As discussed in the team meeting, below is the proposed spec-lite process for simple feature requests. This is already being used in Glance project. Feedback/comments/concerns are welcome, before we update the contributor docs with this:). tl;dr - spec-lite is a simple feature

Re: [Openstack] DVR and public IP consumption

Hi, >> You cannot get around each tenant gateway router consuming an extra public >> IP address itself as far as I know. Almost. With DVR, a FIP namespace is created on compute nodes, with one FIP namespace per external network. The FIP namespace owns an IP address from the external provider

Re: [openstack-dev] [nova][stable/liberty] Are release tarballs still provided via Launchpad?

Lee Yarwood wrote: Hello all, $subject, for example with Kilo : https://launchpad.net/nova/kilo/2015.1.2/+download/nova-2015.1.2.tar.gz If not, should we be using http://tarballs.openstack.org/nova/ directly for these stable releases? We are no longer using Launchpad for tarball

Re: [openstack-dev] [neutron][api] GET call with huge argument list

I tend to agree with Doug and Ryan's stance. If you need to pass 1000s of network-id on a single request you're probably not doing things right on the client side. As Ryan suggested you can try and split the request in multiple requests with acceptable URI lenght and send them in parallel; this

Re: [openstack-dev] [heat] spec-lite for simple feature requests

On 21/01/16 04:21, Rabi Mishra wrote: Hi All, As discussed in the team meeting, below is the proposed spec-lite process for simple feature requests. This is already being used in Glance project. Feedback/comments/concerns are welcome, before we update the contributor docs with this:).

[openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

Greetings, At the Tokyo summit, we discussed OpenStack's development themes in a cross-project session. In this session a group of folks started discussing what topics the overall community could focus on as a shared effort. One of the things that was raised during this session is the need of

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

Excerpts from Flavio Percoco's message of 2016-01-20 13:23:02 -0430: > Greetings, > > At the Tokyo summit, we discussed OpenStack's development themes in a > cross-project session. In this session a group of folks started discussing > what > topics the overall community could focus on as a

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

-Original Message- From: Flavio Percoco Reply: Flavio Percoco , OpenStack Development Mailing List (not for usage questions) Date: January 20, 2016 at 11:57:56 To: openstack-dev@lists.openstack.org

Re: [openstack-dev] [keystone][neutron][requirements] - keystonemiddleware-4.1.0 performance regression

On 19 January 2016 at 23:11, Steve Martinelli wrote: > Hmm, looking at: > https://github.com/openstack/keystonemiddleware/compare/4.0.0...4.1.0 the > only change that I can think of that might be the culprit is: >

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

On 20/01/16 14:58 -0500, Jay Pipes wrote: On 01/20/2016 01:30 PM, Doug Hellmann wrote: Excerpts from Flavio Percoco's message of 2016-01-20 13:23:02 -0430: Greetings, At the Tokyo summit, we discussed OpenStack's development themes in a cross-project session. In this session a group of folks

Re: [openstack-dev] [ceilometer] ceilometer Floatingip Pollster change

On Wed, Jan 20, 2016 at 3:27 PM, gord chung wrote: > i guess i should probably add that the current pollster doesn't work > because of limitation in nova api[1]. > if we want to support discovery of whether nova-network or neutron is > used, the existing pollster and nova-api still

[openstack-dev] [Neutron] Mitaka-2

Hi neutrinos, The release patch [1] has landed. The existing workload for the remainder of the cycle is tracked in [2]. If you have something shown on this dashboard (or if you don't, but you want to), please reach out either via ML (on this thread) or on #openstack-neutron. Cheers, Armando

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

+1 for Kyles proposal as well! I think we can give it a try. If we realize that it becomes kind of a "second class" meeting, as only less people will join or that the meeting has no impact, we still can go back to the weekly meeting slot on Monday IMO. Andreas (IRC: scheuran) On Mi,

[openstack-dev] [Neutron] Removing ml2_type_vxlan.vxlan_group parameter?

There was some discussion if the ml2_type_vxlan.vxlan_group of the ml2 config file (Neutron Server) can be removed [1], as it is not being used by in-tree drivers (ovs, lb, sriov). OVS: does not support vxlan mcast LB: uses it's own agent configuration today. SRIOV: does not support vxlan at

Re: [openstack-dev] [kuryr] Failed to create network with kuryr driver type

Hi mars Which code are u using? I repeated your steps with latest master branch. And the error from kuryr is 127.0.0.1 - - [20/Jan/2016 17:23:50] "POST /IpamDriver.GetDefaultAddressSpaces HTTP/1.1" 200 - ERROR in

Re: [openstack-dev] [TripleO] Mitaka Milestone 2

Hi John, fully agreed on your proposal. On Mon, Jan 18, 2016 at 10:59:03AM -0500, John Trowbridge wrote: > I have been tracking the issues when deploying with current from all > other projects[2] (as opposed to using an old pinned delorean for > non-tripleo projects). This has been a rapidly

[Openstack] Question about OpenStack Networking on Liberty

Hello. I've been learning OpenStack from Havana, and as far as I know the DVR (Distributed Virtual Router) Concept has been raised since Juno. I wonder whether the DVR is finally supported fully at Liberty. Furthermore, does it solve the issue related networking performance of OpenStack,

Re: [openstack-dev] [kuryr] Failed to create network with kuryr driver type

Hi Vikas, I added your fix , and also have problem, but different : $ neutron subnetpool-list +--+---+---+---+--+ | id | name | prefixes | default_prefixlen |

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

Mondays 21UTC and Tuesdays 14UTC are OK for me, so personally I do not have problem to attend both meetings, but I know that for someone one or another can be in the middle of night. In this case, would be good to again have bi-weekly to allow attendance at least once per two weeks. +1 for

Re: [openstack-dev] [Neutron] Removing ml2_type_vxlan.vxlan_group parameter?

Andreas Scheuring wrote: There was some discussion if the ml2_type_vxlan.vxlan_group of the ml2 config file (Neutron Server) can be removed [1], as it is not being used by in-tree drivers (ovs, lb, sriov). OVS: does not support vxlan mcast LB: uses it's own agent

Re: [openstack-dev] [kuryr] Failed to create network with kuryr driver type

Much thanks to @Vikas Thanks & Best regards ! Mars Ma On Wed, Jan 20, 2016 at 5:55 PM, Vikas Choudhary wrote: > Hi Mars, > > Your problem will be solved by this patch, > https://review.openstack.org/#/c/265744/ . It has not been

[openstack-dev] swift missing X-Timestamp header commit review

Hi, I sent code for review related with this bug(https://bugs.launchpad.net/swift/+bug/1509429) which is about missing X-Timestamp header in HTTP response in Swift-API. commit-1: This one is my patch for the bug. https://review.openstack.org/#/c/268163/ commit-2: This one is the related

Re: [openstack-dev] [fuel] [fuelclient] Pre-release versions of fuelclient for testing purposes

Releasing a beta version sounds like a good plan but does OpenStack Infra actually support this? > 20 січ. 2016 р. о 12:05 Oleg Gelbukh написав(ла): > > Hi, > > Currently we're experiencing issues with Python dependencies of our package > (fuel-octane), specifically

Re: [openstack-dev] [Oslo] Improving deprecated options identification and documentation

Ronald Bradford wrote on 01/15/2016 03:04:29 AM: > From: Ronald Bradford > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 01/15/2016 03:05 AM > Subject: Re: [openstack-dev]

Re: [openstack-dev] [all] pip 8 no longer over-installs system packages [was: Gate failure]

On 01/20/2016 06:21 PM, Andreas Jaeger wrote: > Now docs, pep8, and python27 are broken as well here: > https://review.openstack.org/#/c/268687/ Ok, so this is a weird one. On trusty, argparse is sort of in, and sort of out of the virtualenv. I think it has to do with [1] ---

  1   2   >