Re: [openstack-dev] [CI] How to set a proxy for zuul.

Hi all, I have constructed my CI system. When I tested it with sandbox project, I posted a patch to Gerrit. https://review.openstack.org/201002 But I got this error in zuul scheduler: 2015-07-14 14:07:24,921 DEBUG zuul.Scheduler: Run handler awake 2015-07-14 14:07:24,921 DEBUG zuul.Scheduler:

Re: [openstack-dev] [CI] How to set a proxy for zuul.

First of all, change the "vendor" to your vendor name in /etc/jenkins_jobs/config/projects.yaml file. Also, restart the zuul and zuul merger. On Mon, Jul 13, 2015 at 12:29 PM, Tang Chen wrote: > Hi all, > > I have constructed my CI system. > When I tested it with sandbox project, I posted a pat

Re: [openstack-dev] [CI] How to set a proxy for zuul.

Also check that Gearman is connecting or not through Jenkins UI. On Mon, Jul 13, 2015 at 12:45 PM, Abhishek Shrivastava < abhis...@cloudbyte.com> wrote: > First of all, change the "vendor" to your vendor name in > /etc/jenkins_jobs/config/projects.yaml file. Also, restart the zuul and > zuul merg

Re: [openstack-dev] [CI] How to set a proxy for zuul.

Hi Abhishek, Thanks for the quick reply. On 07/13/2015 03:16 PM, Abhishek Shrivastava wrote: Also check that Gearman is connecting or not through Jenkins UI. On Mon, Jul 13, 2015 at 12:45 PM, Abhishek Shrivastava mailto:abhis...@cloudbyte.com>> wrote: First of all, change the "vendor" t

Re: [openstack-dev] [Cinder]Restrict volume creation based on type

On Mon, Jul 13, 2015 at 07:56:36AM +0300, Eduard Matei wrote: > Hi, > > Forgot to mention, indeed we configured extra_specs: volume_backend_name. > The problem is that a volume of this type can get scheduled on a node where > c-vol is not configured with this backend. > > F.e.: I have 3 storage n

Re: [openstack-dev] [CI] How to set a proxy for zuul.

​Use tester or something, also are you updating the jobs or not?​ On Mon, Jul 13, 2015 at 1:16 PM, Tang Chen wrote: > Hi Abhishek, > > Thanks for the quick reply. > > On 07/13/2015 03:16 PM, Abhishek Shrivastava wrote: > > Also check that Gearman is connecting or not through Jenkins UI. > > On

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/13/2015 03:29 AM, Robert Collins wrote: > So, we've got constraints support for tox coming together nicely. > > The rollout for that will be per project (because tox.ini needs to > change). > > However, we're not compiling, nor are we easily

Re: [openstack-dev] [neutron][upgrades] Potential issues when performing Neutron upgrades

>because you won't have to run Neutron agents on compute nodes anymore. How will upgrades work for OVN? On Thu, Jul 9, 2015 at 2:30 PM, Russell Bryant wrote: > On 07/09/2015 10:11 AM, Ihar Hrachyshka wrote: > > On 07/09/2015 09:01 AM, Artur Korzen wrote: > >> Hi all, > > > >> I've been research

Re: [openstack-dev] [CI] How to set a proxy for zuul.

On 07/13/2015 03:50 PM, Abhishek Shrivastava wrote: Use tester or something, also are you updating the jobs or not? I used tester as my vendor. It doesn't work. And what do you mean by updating the jobs ? I built the noop-check-cimmunitication job once in Jenkins UI. Does it matter ? All th

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

Ian Cordasco wrote: > On 7/10/15, 03:44, "Thierry Carrez" wrote: >> Also you'll find that the various distros use different epoch values for >> the same software, because epoch are also used to cover local blunders >> in packaging and historical artifacts. That is why epochs should be >> local to

Re: [openstack-dev] [CI] How to set a proxy for zuul.

Updating jobs using "sudo jenkins-jobs --flush-cache update /etc/jenkins_jobs/config/". Also update the myvendor in examples.yaml On Mon, Jul 13, 2015 at 1:45 PM, Tang Chen wrote: > > On 07/13/2015 03:50 PM, Abhishek Shrivastava wrote: > > ​Use tester or something, also are you updating the jo

Re: [openstack-dev] [Cinder]Restrict volume creation based on type

Hi, Thanks for your replies. Got back to the team and tried to get more input: - the volume is created correctly (i misunderstood that part) - the problem is that (sometimes) the instance gets spawned on the 3rd node (which doesn't have the driver configured). This might be because of the availabi

Re: [openstack-dev] [neutron] Plethora of dbase migration questions...

Hi, Paul! This messages is OK. May be you can put a change on review in WIP status, that I will be able to check what is going on? I never have such problems with migrations in neutron-vpnaas repo. May be the problem is that database is already upgraded, was database cleaned before you run neutron

Re: [openstack-dev] [Fuel][Fuel-Packaging][Fuel-CI][Fuel-Infra] How to Deal with CI Failures Induced by Libraries Requirements Drift

Dima You have a very valid point, but the is a problem here - by doing it this way we are breaking developers' workflow which is based on using such repositories as pypi, rubygem, etc. If you convince developers (and I guess not only Fuel ones as we are moving towards community engagement) to swit

Re: [openstack-dev] [Fuel][Fuel-Packaging][Fuel-CI][Fuel-Infra] How to Deal with CI Failures Induced by Libraries Requirements Drift

Some comments inline. On Mon, Jul 13, 2015 at 9:24 AM, Bartlomiej Piotrowski < bpiotrow...@mirantis.com> wrote: > Freezing every moving part is complete overkill and puts a heavy burden on > devops > team as well as infra itself. The fix couldn't be more simple: just put > upper > bounds in requi

Re: [openstack-dev] [neutron][lbaas] Radware unit test issues

Brandon, thank you. I’ve pushed a fix for this issue https://review.openstack.org/#/c/201044 Evg From: Brandon Logan [mailto:brandon.lo...@rackspace.com] Sent: Friday, July 10, 2015 7:43 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron][lbaas

Re: [openstack-dev] [openstack][cinder]A discussion about quota update lower than current usage.

Hi, Mike I'm not sure we really don't need any change about this feature. At least, some end users I faced to think there should be changed IMHO, there is a main problem that some users whom I faced to can't understand: What's the purpose that admin reduce quota lowner than existing usage? Li

Re: [openstack-dev] [Murano] Versioning of Murano packages and MuranoPL classes

Hi Gosha, Supporting versioning in existing backend will require us to re-implement the significant part of Artifact Repository in Murano API: we'll need to add versions and dependencies concepts into our model (which is already complicated and dirty enough), extend appropriate API calls etc. And

Re: [openstack-dev] [neutron][qos] Priorities & Status for QoS

Miguel Angel Ajo wrote: I've been working on assembling a QoS[1] POC since last day of the coding sprint in Israel [2], Ihar has reported to the list our plan to get into master [3]. I've been able to validate and integrate lots of the patches, and find the gaps, while still finishing the

Re: [openstack-dev] [Fuel][Fuel-Packaging][Fuel-CI][Fuel-Infra] How to Deal with CI Failures Induced by Libraries Requirements Drift

Oleg The problem here is that you have this code released and it is running in production - how are you going to fix this? Pin requirements and deal with dependency hell? Seriously, it is much easier to deal with explicitly frozen mirror which is created by one 'pip install ' run than to play with

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

On 13 July 2015 at 20:08, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 07/13/2015 03:29 AM, Robert Collins wrote: >> So, we've got constraints support for tox coming together nicely. >> >> The rollout for that will be per project (because tox.ini needs to >> ch

[openstack-dev] [neutron] Should we document the using of "device:owner" of the PORT ?

Hi all, The device:owner the port is defined as a 255 byte string, and is widely used now, indicating the use of the port. Seems we can fill it freely, and user also could update/set it from cmd line(port-update $PORT_ID --device_owner), and I don't find the guideline for using. What is its fu

Re: [openstack-dev] [CI] How to set a proxy for zuul.

On 07/13/2015 04:35 PM, Abhishek Shrivastava wrote: Updating jobs using "sudo jenkins-jobs --flush-cache update /etc/jenkins_jobs/config/". Also update the myvendor in examples.yaml Sorry, I updated the jobs, restart the whole machine. But it still doesn't work. By the way, there is no ve

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

Rob, Please see: https://etherpad.openstack.org/p/juno-cross-project-future-of-python -- dims On Mon, Jul 13, 2015 at 5:39 AM, Robert Collins wrote: > On 13 July 2015 at 20:08, Ihar Hrachyshka wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> On 07/13/2015 03:29 AM, Robert Col

Re: [openstack-dev] [neutron] Reading an updated port's fixed IPs in mech driver update_port_postcommit

Hi Neil On 07/10/2015 12:49 PM, Neil Jerram wrote: > A pragmatic fix appears to be to explicitly requery the IPAllocation > table, as you can see in the two commits here: > https://github.com/Metaswitch/calico/commit/5512ce7dd50db414f161bddcef17b0846a1466ac > > https://github.com/Metaswitch/calic

Re: [openstack-dev] [openstack][cinder]A discussion about quota update lower than current usage.

The problem is, if you reject the request to lower quota unless the usage is under the new quota, you've got an inherently racy process where the admin needs to communicate with the tenant to say 'Stop using some of your quota while I reduce it', which is no less complicated than 'I've reduced your

Re: [openstack-dev] [Sahara] [QA] [tests coverage] Can we add CI job to control the unit tests coverage?

Hi, here is the commit on review: https://review.openstack.org/#/c/200433 We already added non-voting job in infra repository, need to merge this script. On Fri, Jul 3, 2015 at 1:29 PM, Anastasia Kuznetsova < akuznets...@mirantis.com> wrote: > Boris, > > thanks for an explanation! I will take a

Re: [openstack-dev] [Fuel][Fuel-Packaging][Fuel-CI][Fuel-Infra] How to Deal with CI Failures Induced by Libraries Requirements Drift

Vladimir, The failures you are referring to is purely test-related failures. They don't affect the code in production in any way, as far as I can see. All the same, production code won't be affected by pinning versions of test-requirements in the stable/* branches of the product and test suits.

Re: [openstack-dev] [nova] disk I/O perfomance

Hello, Warren. Yes, we use properly filled file on a single splining drive. All tests are done with fio, here is a link on full test report - http://koder-ua.github.io/6.1GA/ephemeral_drive.html. Here is a link on report for same test, executed directly on HDD, used for ephemeral storage - http://

[openstack-dev] [trove]Expose new API for monitoring

We have proposing the blueprint about exposing new API for monitoring in https://blueprints.launchpad.net/trove/+spec/expose-new-api-for-monitoring Looking forward to any discussion :) -- tobe from UnitedStack__ OpenStack

Re: [openstack-dev] [puppet] running tempest on beaker jobs

On 07/12/2015 11:29 PM, Matt Fischer wrote: > We used Tempest for a time against our production environment. It was a > pain to clean up but ephemeral test jobs solves that for you. A few > questions: > > What version of tempest will be using? master for now. We will see if new tags are create

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

On 2015-07-13 10:08:16 +0200 (+0200), Ihar Hrachyshka wrote: > clients and oslo libraries still maintain their py26 for a reason: > decision to drop py26 was for server projects only. Yes, that decision was made at a time when our server projects had stable branches, but our clients and shared lib

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

On 2015-07-13 06:03:56 -0400 (-0400), Davanum Srinivas wrote: > Please see: > https://etherpad.openstack.org/p/juno-cross-project-future-of-python That decision happened at a time when there were no stable branches of clients/libs and no expectation of their existence. Since then the situation has

[openstack-dev] [magnum] The way magnum-conductor communicates with k8s master

Hi, all. Currently magnum-conductor can communicates with k8s master which has a floating ip in all-in-one deployment. But if magnum-conductor is not deployed on the neutron network node which has the br-ex, how can magnum-conductor communicate with k8s master. The magnum-conductor node then has

[openstack-dev] [mistral] Team meeting - 07/13/2015

Hi, This is a reminder that we’ll have a team meeting today at #openstack-mistral at 16.00 UTC. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) Dashboard progress Liberty-2 progress Open discussion Add your topics either by replying to this email or modi

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

On 13/07/2015 13:57, Jeremy Stanley wrote: people on 2.6-only platforms who want to install and run python-novaclient from PyPI can use the stable/juno version (though I'll admit that finding which version works with 2.6 may be a tricky proposition for a consumer who is unaware of this situation)

Re: [openstack-dev] [murano] [congress] Congress needs to fetch environments from all tenants.

Hi Dolph Thanks for idea. Is this approach used somewhere for similar use-case I described? If so please point it out. Thanks Filip On 07/10/2015 04:57 PM, Dolph Mathews wrote: How about using domain-based role assignments in keystone and requiring domain-level authorization in policy, and t

Re: [openstack-dev] [murano] [congress] Congress needs to fetch environments from all tenants.

Hi Tim, The change was already merged to master. Withe next release of python-muranoclient it can be used in Congress. Regards Filip On 07/08/2015 03:57 PM, Tim Hinrichs wrote: There are two things to remember here. 1) When you configure the Congress datasource driver to talk to Murano, yo

Re: [openstack-dev] [puppet] First Sprint proposal

I just closed the poll after one week. It will happen on Wed 9/2 – Fri 9/4. We'll work on the agenda during the following weeks. Best, On 07/06/2015 10:26 PM, Matt Fischer wrote: > Operators mid-cycle is Aug 17-21 at a TBD location, I voted accordingly. > Thanks. > > On Mon, Jul 6, 2015 at 12:0

[openstack-dev] [puppet] weekly meeting #42

Hello Puppet masters! Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC in #openstack-meeting-4: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150714 Please add additional items you'd like to discuss. If our schedule allows it, we'll make bug triage durin

[openstack-dev] [FUEL] Nailgun agent master freeze

At the moment everything is ready for moving fuel-web/bin/agent to a separate git repository. Please, be informed that all patches changing fuel-web/bin/agent that will be merged after this moment will need to be ported into the new nailgun-agent repository. Current source repository which will b

Re: [openstack-dev] [neutron][upgrades] Potential issues when performing Neutron upgrades

On 07/13/2015 04:09 AM, Kevin Benton wrote: >>because you won't have to run Neutron agents on compute nodes anymore. > > How will upgrades work for OVN? We haven't written anything down yet, but here's what I expect. Right now we're still changing the db schema however is needed without messing

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

Excerpts from Jeremy Stanley's message of 2015-07-13 11:57:35 +: > On 2015-07-13 10:08:16 +0200 (+0200), Ihar Hrachyshka wrote: > > clients and oslo libraries still maintain their py26 for a reason: > > decision to drop py26 was for server projects only. > > Yes, that decision was made at a ti

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

On 7/13/2015 6:57 AM, Jeremy Stanley wrote: On 2015-07-13 10:08:16 +0200 (+0200), Ihar Hrachyshka wrote: clients and oslo libraries still maintain their py26 for a reason: decision to drop py26 was for server projects only. Yes, that decision was made at a time when our server projects had s

[openstack-dev] [neutron] Adding results to extension callbacks

Hi, I sent a simple patch to check the possibility to add results to callbacks: https://review.openstack.org/#/c/201127/ This will allow us to decouple the callback logic from the ML2 plugin in the QoS scenario where we need to update the agents in case the profile_id on a port/network chang

[openstack-dev] global-requirements sync not happening on stable/kilo? reqs check job busted?

From what I can tell, nova never got a global-requirements sync update for this change on stable/kilo: https://review.openstack.org/#/c/200493/ We need that so we don't have to try and do it manually: https://review.openstack.org/#/c/200880/ Which is apparently busted in the gate-nova-require

Re: [openstack-dev] global-requirements sync not happening on stable/kilo? reqs check job busted?

On 7/13/2015 9:01 AM, Matt Riedemann wrote: From what I can tell, nova never got a global-requirements sync update for this change on stable/kilo: https://review.openstack.org/#/c/200493/ We need that so we don't have to try and do it manually: https://review.openstack.org/#/c/200880/ Whic

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

On 2015-07-13 09:39:36 -0400 (-0400), Doug Hellmann wrote: [...] > On the other hand, how much longer will we be supporting Juno? A > matter of months, right? The reason it's being brought up again at this point is to ask whether it's more important that we keep master clients/libs working with 2.

Re: [openstack-dev] [nova][qa] turbo-hipster seems to be out to lunch

On 7/12/2015 1:50 AM, Joshua Hesketh wrote: Hey, Yes, sorry, I only discovered this yesterday. I should have updated the wiki page sooner but I've placed some details there now: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/kilo+topic:fix-th,n,z Basically t

Re: [openstack-dev] [Murano] Versioning of Murano packages and MuranoPL classes

On Mon, Jul 13, 2015 at 2:19 AM, Alexander Tivelkov wrote: > Hi Gosha, > > Supporting versioning in existing backend will require us to re-implement > the significant part of Artifact Repository in Murano API: we'll need to > add versions and dependencies concepts into our model (which is already

Re: [openstack-dev] [Openstack-operators] [Openstack] Rescinding the M name decision

On Jul 10, 2015, at 4:19 AM, Thierry Carrez wrote: > I think "growing up" is accepting the pain that comes with picking a > good name, rather than sidestepping the issue. I’ve heard the phrase that there are only two hard problems in computer science, and naming is one of them. Just because it

[openstack-dev] [ptl] Skipping Release management 0800-1000 UTC office hours next Tuesday

Hi PTLs and release liaisons, I'm taking some of tomorrow off on Bastille day, so I'll be missing my 0800-1000 UTC release management office hours on Tuesday, July 14. We'll still have office hours between 1800 and 2000 UTC on that day, in case you have anything to discuss or questions to ask. I

[openstack-dev] [keystone] No IRC Meeting Tuesday July 14

July 14 IRC Meeting is cancelled due to proximity to the Keystone MidCycle (Wed, Thurs, and Fri) of this week. Meetings will resume normal schedule as of July 21. See everyone either at the MidCycle or at the next IRC meeting. ___

Re: [openstack-dev] [Neutron] New Neutron subproject for a Neutron backed Docker remote networking driver

On Fri, Jul 10, 2015 at 5:34 PM, Gurucharan Shetty wrote: > On Fri, Jul 10, 2015 at 8:16 AM, Gurucharan Shetty wrote: >>> From a 2 min look, this seems to wrap docker commands instead of using >>> the new plugin >> The plugin is here: >> https://github.com/shettyg/ovn-docker/blob/master/ovn-docke

[openstack-dev] [Magnum] Magnum Quick-Start: Need clarification on Kubernetes/Redis example

Does anyone have recent experience getting the Kubernetes/Redis example to work in the Magnum developer Quick-Start guide?: https://github.com/openstack/magnum/blob/master/doc/source/dev/dev-quickstart.rst#exercising-the-services-using-devstack I can get everything in the Kubernetes/Redis ex

[openstack-dev] [mistral] Team meeting minutes/log - 07/13/2015

Thanks for joining us today and making a good meeting! As usually, Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-07-13-16.00.html Meeting log: http://eavesdrop.openstack.o

Re: [openstack-dev] [keystone] Liberty SFE Request - Dynamic Policies

On 07/03/2015 08:36 AM, Samuel de Medeiros Queiroz wrote: Hi Thierry, Thanks for clarifying. A Spec Freeze Exception is what I was supposed to ask for. Rectifying: On behalf of the team working on the Dynamic Policies subject, I would like to ask for a *Spec Freeze Exception* in Liberty for

[openstack-dev] [ceilometer][neutron] question about ceilometer/network/statistics

I'm trying to get my arms around how to develop ceilometer support for networking related data/counters. Seems like there might be a couple of ways to go about this. On the one hand, there are the OpenDaylight and opencontrail contributions in https://github.com/openstack/ceilometer/tree/master

[openstack-dev] [puppet] new etherpad to track Puppet OpenStack CI work

It comes up some people are interested to help with Puppet OpenStack CI work, so here is an etherpad: https://etherpad.openstack.org/p/puppet-openstack-CI Before working on any task, please make sure to chat with us on IRC or ML, and put your name in the etherpad. Also, any new topics are really

Re: [openstack-dev] [keystone] Liberty SFE Request - Dynamic Policies

++! Per my understanding, the work, and therefore the risks, are fairly compartmentalized. The upside is this will pave the way for a much richer authorization management system. Guang From: Adam Young [mailto:ayo...@redhat.com] Sent: Monday, July 13, 2015 10:15 AM To: openstack-dev@lists.ope

Re: [openstack-dev] [Ironic] how about those alternating meeting times?

This is a much-overdue follow up to this poll, which got 17 responses. TL;DR: The poll indicated that most responders did not personally find the 0500 meeting helpful. Reviewing the meeting logs for the last six months shows significantly lower core attendance in those meetings. Informal feedback

[openstack-dev] [Ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) As of Mon, Jul 13 (diff with Jun 29) Open: 147 (-3). 6 new (+1), 52 in progress, 1 critical (+1), 10 high (-1) and 8 incomplete (-1) Nova b

Re: [openstack-dev] [Ironic] how about those alternating meeting times?

On Mon, Jul 13, 2015 at 06:41:55PM +, Devananda van der Veen wrote: > This is a much-overdue follow up to this poll, which got 17 responses. > > > > So, though it saddens me, I would like to propose that we change back to a > single meeting time effective the week following our midcycle (Aug

Re: [openstack-dev] [puppet] new etherpad to track Puppet OpenStack CI work

On 07/13/2015 02:21 PM, Emilien Macchi wrote: It comes up some people are interested to help with Puppet OpenStack CI work, so here is an etherpad: https://etherpad.openstack.org/p/puppet-openstack-CI Before working on any task, please make sure to chat with us on IRC or ML, and put your name i

Re: [openstack-dev] [designate][lbaas][GSLB] IRC Meeting Tomorrow - 07/Jul/2015 @ 16:00 UTC

A quick reminder that we will be reconvening tomorrow at 16:00UTC in #openstack-meeting-4 to continue the API discussion. Thanks, Graham On 06/07/15 15:27, Hayes, Graham wrote: > Hi All, > > I have put up an agenda for the meeting tomorrow: > > https://wiki.openstack.org/wiki/Meetings/GSLB > >

Re: [openstack-dev] [keystone] Liberty SFE Request -DynamicPolicies

I am a +1 on this as well. I agree with Guang Brad Topol, Ph.D. IBM Distinguished Engineer OpenStack (919) 543-0646 Internet: bto...@us.ibm.com Assistant: Kendra Witherspoon (919) 254-0680 From: "Yee, Guang" To: "OpenStack Development Mailing List (not for usage questions)" Date: 0

Re: [openstack-dev] [Cinder] python-cinderclient functional tests

On 16:28 Jul 10, Ivan Kolodyazhny wrote: > Hi Mike, > > Unfortunately, we don't get a lot of stats [1] because we don't run it > often. I've added 'check experimental' comment to latest > python-cinderclient review request to get more stats. > > Review request to make this voting: https://review.

[openstack-dev] [Infra] Meeting Tuesday July 14th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday July 14th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone intereste

[openstack-dev] [Ironic] Reminder - midcycle Sprint in Seattle Aug 12 - 14

Hi all! Just dropping a reminder out here -- our midcycle is one month away! We're starting to jot down informal notes and plans on an etherpad here: https://etherpad.openstack.org/p/ironic-liberty-midcycle Please continue to use that to coordinate all the things. If you plan to attend, please m

Re: [openstack-dev] [glance] Additions and removals for the glance-drivers team

On 7/9/15, 13:37, "Flavio Percoco" wrote: >Greetings, > >I'd like to propose Stuart Mclaren for the glance-drivers team. Stuart >has a huge amount of knowledge about Glance's history, he knows the >Glance codebase well and he also has experience in deploying and >maintaning Glance production en

[openstack-dev] [nova] cross-site console web socket proxies no longer work

I noticed in Kilo there’s a validation check in the console web socket proxies to ensure the hostnames from the Origin and Host headers match. This was as a result of CVE-2015-0259 (https://bugs.launchpad.net/nova/+bug/1409142). Effectively it disabled cross-site web socket connections. This

Re: [openstack-dev] [Cinder] python-cinderclient functional tests

On Mon, Jul 13, 2015 at 12:04:05PM -0700, Mike Perez wrote: > On 16:28 Jul 10, Ivan Kolodyazhny wrote: > > Hi Mike, > > > > Unfortunately, we don't get a lot of stats [1] because we don't run it > > often. I've added 'check experimental' comment to latest > > python-cinderclient review request to

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

Excerpts from Matt Riedemann's message of 2015-07-13 08:52:37 -0500: > > On 7/13/2015 6:57 AM, Jeremy Stanley wrote: > > On 2015-07-13 10:08:16 +0200 (+0200), Ihar Hrachyshka wrote: > >> clients and oslo libraries still maintain their py26 for a reason: > >> decision to drop py26 was for server pr

Re: [openstack-dev] [glance] The sorry state of our spec process

On 7/3/15, 05:35, "Kuvaja, Erno" wrote: >First of all, Thanks Flavio for bring this open to the daylight! I agree. More of these discussions need to happen on the mailing list. >I have been really frustrated about the Glance spec process since the >beginning and as glance core tried to work a

[openstack-dev] [stackforge][deb][packges] Upstream repositories for OpenStack deb “server” packages

Hello everyone. During the Liberty summit in Vancouver, the idea to maintain OpenStack packages for Debian and Ubuntu on upstream infra sparked. As part of the Openstack and Debian community we still want to push for it. Instead of trying to directly go for the /openstack namespace, we currently

Re: [openstack-dev] [puppet] running tempest on beaker jobs

On Mon, Jul 13, 2015 at 07:50:59AM -0400, Emilien Macchi wrote: > > > On 07/12/2015 11:29 PM, Matt Fischer wrote: > > We used Tempest for a time against our production environment. It was a > > pain to clean up but ephemeral test jobs solves that for you. A few > > questions: > > > > What versi

[openstack-dev] [tags] ops:ha tag request for feedback

I would appreciate if you could all leave your comments and thoughts on the following patch [1]. Please be advised this is an initial version and your feedback is very much appreciated. [1] https://review.openstack.org/#/c/200128/1 -- Best Regards, Maish Saidel-Keesing __

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

On 7/13/15, 03:38, "Thierry Carrez" wrote: >Ian Cordasco wrote: >> On 7/10/15, 03:44, "Thierry Carrez" wrote: >>> Also you'll find that the various distros use different epoch values >>>for >>> the same software, because epoch are also used to cover local blunders >>> in packaging and historic

Re: [openstack-dev] [neutron] Reading an updated port's fixed IPs in mech driver update_port_postcommit

Since this is post-commit, can you try using a new admin context for the get_port call and see if it suffers from the same problem? So instead of passing context._plugin_context, pass in ctx.get_admin_context(). On Fri, Jul 10, 2015 at 4:49 AM, Neil Jerram wrote: > Sorry to leave this unanswered

Re: [openstack-dev] [puppet] running tempest on beaker jobs

On Sun, Jul 12, 2015 at 09:29:57PM -0600, Matt Fischer wrote: > We used Tempest for a time against our production environment. It was a > pain to clean up but ephemeral test jobs solves that for you. A few > questions Just curious how long ago was this? Because resource leaks have always been trea

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

On 13 Jul 2015 8:52 pm, "Ian Cordasco" wrote: > On 7/13/15, 03:38, "Thierry Carrez" wrote: > >By "counter-productive", I meant: likely to generate more confusion than > >clarity. If you provide an epoch in the version and it doesn't match > >downstream packagers ones, it's hard to rely on it. >

Re: [openstack-dev] [puppet] running tempest on beaker jobs

My tempest experience is dated to Havana, so I'll consider it to be completely out of date. Glad to he about all these improvements. On Jul 13, 2015 2:12 PM, "Matthew Treinish" wrote: > On Sun, Jul 12, 2015 at 09:29:57PM -0600, Matt Fischer wrote: > > We used Tempest for a time against our produc

[openstack-dev] [Magnum] [Networking]

For those involved in Magnum networking, I suggest attending the upcoming Docker Meetup: http://www.meetup.com/Docker-Online-Meetup/events/223796871/ Regards, Daneyon Hansen __ OpenStack Development Mailing List (not for us

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

On 7/13/15, 15:09, "Dave Walker" wrote: > >On 13 Jul 2015 8:52 pm, "Ian Cordasco" wrote: >> On 7/13/15, 03:38, "Thierry Carrez" wrote: > >> >By "counter-productive", I meant: likely to generate more confusion >>than >> >clarity. If you provide an epoch in the version and it doesn't match >> >

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

Hi German, We integrated UI with LBaaS v2 GET APIs. We have created all panels for CREATE and UPDATE as well. Plan is to share our code with community on stackforge for more collaboration from the community. So far Ganesh from cisco has shown interest in helping with some work. It will be great i

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

On 14 July 2015 at 02:10, Jeremy Stanley wrote: > On 2015-07-13 09:39:36 -0400 (-0400), Doug Hellmann wrote: > [...] >> On the other hand, how much longer will we be supporting Juno? A >> matter of months, right? > > The reason it's being brought up again at this point is to ask > whether it's mor

Re: [openstack-dev] [neutron] Adding results to extension callbacks

This sounds like a lot of overlap with the dict extend functions. Why weren't they adequate for the QoS use case? On Mon, Jul 13, 2015 at 7:58 AM, Mike Kolesnik wrote: > Hi, > > I sent a simple patch to check the possibility to add results to callbacks: > https://review.openstack.org/#/c/201127/

Re: [openstack-dev] [neutron][upgrades] Potential issues when performing Neutron upgrades

Thanks for the info. So the equivalent in neutron would be if we just ensure backward compatible AMQP APIs, right? On Mon, Jul 13, 2015 at 7:33 AM, Russell Bryant wrote: > On 07/13/2015 04:09 AM, Kevin Benton wrote: > >>because you won't have to run Neutron agents on compute nodes anymore. > > >

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

On 13 July 2015 at 21:58, Ian Cordasco wrote: > On 7/13/15, 15:09, "Dave Walker" wrote: > >> >>Therefore, these distro's would need to increment the distro epoch if the >>upstream version (without the upstream epoch) is lower than the version >>currently in their archives. >>I am not sure how rp

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

Ian Cordasco wrote: On 7/13/15, 15:09, "Dave Walker" wrote: On 13 Jul 2015 8:52 pm, "Ian Cordasco" wrote: On 7/13/15, 03:38, "Thierry Carrez" wrote: By "counter-productive", I meant: likely to generate more confusion than clarity. If you provide an epoch in the version and it doesn't

Re: [openstack-dev] [Sahara] Questions about how Sahara use trust ?

On 07/12/2015 09:45 PM, Li, Chen wrote: Hi Andrew, Thanks for the reply. Are you mean : 1. admin user is used by transient cluster is mainly to make it work. 2. The proxy user is the more secure way to do the same thing. Should we use proxy user at all situation then ? Should th

Re: [openstack-dev] [neutron][upgrades] Potential issues when performing Neutron upgrades

On 07/13/2015 05:08 PM, Kevin Benton wrote: > Thanks for the info. So the equivalent in neutron would be if we just > ensure backward compatible AMQP APIs, right? There's a few parts: 1) Backwards compatibility with changes to the oslo.messaging APIs using API versioning (what you're referring to

Re: [openstack-dev] [keystone] Liberty SFE Request - Dynamic Policies

So although I am in favor of approving some of this, it isn’t quite clear what portions of “Dynamic Policy” is being asked for an exception? We need to be clear exactly what bps we are taking about here, since there is a lot under that umbrella. Henry > On 13 Jul 2015, at 19:20, Yee, Guang

Re: [openstack-dev] [neutron][upgrades] Potential issues when performing Neutron upgrades

Some pedant comments inline. Salvatore On 13 July 2015 at 23:29, Russell Bryant wrote: > On 07/13/2015 05:08 PM, Kevin Benton wrote: > > Thanks for the info. So the equivalent in neutron would be if we just > > ensure backward compatible AMQP APIs, right? > > There's a few parts: > > 1) Backwar

[openstack-dev] [magnum][devstack] Request actions on a suspicious commit

Hi, I sent this email to request investigations on a suspicious commit [1] from devstack, which possibly breaks magnum's functional gate test. The first breakage at Magnum side occurred at Jul 10 4:18 PM [2], which is about half an hour after the suspicious commit being merged. By dipping into

Re: [openstack-dev] [openstack-announce] End of life for managed stable/icehouse branches

I missed this announce... On 07/02/2015 05:32 AM, Jeremy Stanley wrote: > Per the Icehouse EOL discussion[1] last month, now that the final > 2014.1.5 release[2] is behind us I have followed our usual end of > life steps for stable/icehouse branches on repos under the control > of the OpenStack Re

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

Excerpts from Robert Collins's message of 2015-07-14 09:05:43 +1200: > On 14 July 2015 at 02:10, Jeremy Stanley wrote: > > On 2015-07-13 09:39:36 -0400 (-0400), Doug Hellmann wrote: > > [...] > >> On the other hand, how much longer will we be supporting Juno? A > >> matter of months, right? > > >

Re: [openstack-dev] [swift] [ceilometer] Ceilometer log dir permissions bust swift proxy

On 13/07/15 06:44, Emilien Macchi wrote: I think this is something that could be fixed in packaging scripts. I can see you're using Puppet to deploy OpenStack, and fwiw, we are stopping to manage permissions in Puppet because of packaging overlap. From now, we totally rely on packaging permissi

Re: [openstack-dev] [magnum][bp] Power Magnum to run on metal with Hyper

Team, I woud like to ask for your input about adding support for Hyper in Magnum: https://blueprints.launchpad.net/magnum/+spec/hyperstack We touched on this in our last team meeting, and it was apparent that achieving a higher level of understanding of the technology before weighing in about t

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

> -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Monday, July 13, 2015 3:41 PM > To: openstack-dev > Subject: Re: [openstack-dev] [all] Time to remove Python2.6 jobs from > master > > Excerpts from Robert Collins's message of 2015-07-14 09:05:43 +1200: > >

  1   2   >