Re: [openstack-dev] [horizon][infra] django.pot hardcoded or not?

The problem with using a tox target is that we use privileged Jenkins machines to do the extraction and don't want arbitrary code to run on them. It would be possible to run arbitrary code if we used a tox target. Clark On Wed, Dec 30, 2015, at 10:07 AM, Akihiro Motoki wrote: > I haven't looked i

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11, completed.

On Wed, Dec 23, 2015, at 03:00 PM, Carl Baldwin wrote: > On Wed, Dec 23, 2015 at 3:40 PM, Zaro wrote: > > On Tue, Dec 22, 2015 at 4:51 PM, Carl Baldwin wrote: > >> I noticed another thing. I'm working with a chain of three patches. > >> I just updated the patch in the middle [1] to patch set 37.

Re: [openstack-dev] [Infra][nova][magnum] Jenkins failed quite often for "Cannot set up guest memory 'pc.ram': Cannot allocate memory"

of them occurred in OVH host. Any further suggestion? > > [1] http://status.openstack.org/elastic-recheck/#1521237 > > Best regards, > Hongbin > > -Original Message- > From: Clark Boylan [mailto:cboy...@sapwetik.org] > Sent: December-15-15 5:41 PM > T

Re: [openstack-dev] [keystone]How do we avoid token expired?

On Sun, Dec 20, 2015, at 07:43 AM, zhu4236926 wrote: > Hi guys, > I'm using cinder-clinet to backup a volume and query the status of > the backup-volume in a loop per 3 seconds. I got the token from > keystone when I begin to backup the volume,assuming that the token is > expired in

Re: [openstack-dev] [Infra][nova][magnum] Jenkins failed quite often for "Cannot set up guest memory 'pc.ram': Cannot allocate memory"

On Sun, Dec 13, 2015, at 10:51 AM, Clark Boylan wrote: > On Sat, Dec 12, 2015, at 02:16 PM, Hongbin Lu wrote: > > Hi, > > > > As Kai Qiang mentioned, magnum gate recently had a bunch of random > > failures, which occurred on creating a nova instance with 2G of RAM.

Re: [openstack-dev] [Infra][nova][magnum] Jenkins failed quite often for "Cannot set up guest memory 'pc.ram': Cannot allocate memory"

thw-0-nmaiwpjhkqg6-kube-minion-5emvszmbwpi2 systemd[1]: > docker.service failed. > > > http://logs.openstack.org/58/251158/3/check/gate-functional-dsvm-magnum-k8s/5ed0e01/logs/bay-nodes/worker-test_replication_controller_apis-172.24.5.11/docker.txt.gz > > > — > Egor > &

Re: [openstack-dev] [Infra][nova][magnum] Jenkins failed quite often for "Cannot set up guest memory 'pc.ram': Cannot allocate memory"

On Sat, Dec 12, 2015, at 02:16 PM, Hongbin Lu wrote: > Hi, > > As Kai Qiang mentioned, magnum gate recently had a bunch of random > failures, which occurred on creating a nova instance with 2G of RAM. > According to the error message, it seems that the hypervisor tried to > allocate memory to the

Re: [openstack-dev] [oslo.log] RFC5424-compliant dates

On Fri, Dec 11, 2015, at 10:12 AM, Chris St. Pierre wrote: > RFC5424 requires timestamps in a strict subset of RFC3339. Currently, > oslo.log has no way to provide dates in this format without specifying a > custom logging formatter, which means that oslo.log is incapable of > providing RFC5424-com

Re: [openstack-dev] [infra][devstack][gnocchi] Unable to run devstack-gate with stable/1.3

On Thu, Nov 19, 2015, at 05:17 AM, Julien Danjou wrote: > Hi, > > The Gnocchi gate is broken for stable/1.3 because of devstack-gate > saying¹: > ERROR: branch not allowed by features matrix: 1.3 > > From what I understand, that's because devstack-gate thinks it should > try to pull stable/1.3

Re: [openstack-dev] [tc][infra][neutron] branches for release-independent projects targeting Openstack release X

On Fri, Nov 20, 2015, at 04:32 AM, Julien Danjou wrote: > On Fri, Nov 20 2015, Clark Boylan wrote: > > > If you have a stable/X.Y branch or stable/foo but are still wanting to > > map onto the 6 month release cycle (we know this because you are running > > devstack-g

Re: [openstack-dev] [tc][infra][neutron] branches for release-independent projects targeting Openstack release X

On Thu, Nov 19, 2015, at 12:55 PM, Chris Dent wrote: > On Thu, 19 Nov 2015, Julien Danjou wrote: > > > It would be good to support that as being *normal*, not "potentially > > incorrect and random"! > > Yes. > > The underlying issue in this thread is the dominance of the six month > cycle and

Re: [openstack-dev] [infra][glance] How do we fix the glance_store git > glance-store LP mapping?

; launchpad and we went with the best alternative possible. > > I can't change it and the project is glance-store in LP whereas all > other details (title, display name etc) reflects glance_store. > > On 11/19/15 12:38 PM, Clark Boylan wrote: > > On Thu, Nov 19, 2015, at

Re: [openstack-dev] [infra][glance] How do we fix the glance_store git > glance-store LP mapping?

On Thu, Nov 19, 2015, at 08:00 AM, Matt Riedemann wrote: > Patches in Gerrit aren't syncing status to the glance-store project in > launchpad b/c the project in launchpad is called glance-store and in git > it's glance_store. > > Looking at the project creators guide it says to specify a group f

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On Wed, Nov 4, 2015, at 09:14 AM, Sean Dague wrote: > On 11/04/2015 12:10 PM, Jeremy Stanley wrote: > > On 2015-11-04 08:43:27 -0600 (-0600), Matthew Thode wrote: > >> On 11/04/2015 06:47 AM, Sean Dague wrote: > > [...] > >>> Is there a nodepool cache strategy where we could pre build these? A 25%

[openstack-dev] Upgrading elasticsearch cluster Monday 11/9

Hello, The infrastructure team will be upgrading the Elasticsearch cluster used by Logstash and elastic-recheck on Monday November 9th starting at about 1700UTC. Because we are upgrading from 0.90.9 to 1.7.3 this will require a full cluster restart. During the cluster restart you will not be able

Re: [openstack-dev] Open a new project in OpenStack or Stackforge ?

On Mon, Oct 12, 2015, at 05:09 PM, joehuang wrote: > Hello, > > Could you or someone else pls. help us to open a new project? We learned > that Stackforge will be retired soon, so shall we open this new project > under OpenStack directly instead? How to do it ? > > A new project, a standalone ne

Re: [openstack-dev] [Murano] py26 support in python-muranoclient

On Fri, Oct 9, 2015, at 10:32 AM, Vahid S Hashemian wrote: > Serg, Jeremy, > > Thank you for your response, so the issue I ran into with my patch is the > gate job failing on python26. > You can see it here: https://review.openstack.org/#/c/232271/ > > Serg suggested that we add 2.6 support to

Re: [openstack-dev] [infra][nova][all] Pillow breaking gate?

On Thu, Oct 1, 2015, at 03:48 PM, Kevin L. Mitchell wrote: > It looks like Pillow (pulled in by blockdiag, pulled in by > sphinxcontrib-seqdiag, in test-requirements.txt of nova and probably > others) had a 3.0.0 release today, and now the gate is breaking because > libjpeg isn't available in the i

Re: [openstack-dev] [puppet] use zuul-cloner when running rspec

On Thu, Sep 24, 2015, at 12:39 PM, Alex Schultz wrote: > On Thu, Sep 24, 2015 at 1:58 PM, Emilien Macchi > wrote: > > > > > > On 09/24/2015 02:19 PM, Alex Schultz wrote: > >> On Thu, Sep 24, 2015 at 11:54 AM, Emilien Macchi > >> wrote: > >>> > >>> > >>> On 09/24/2015 10:14 AM, Alex Schultz wrote

Re: [openstack-dev] Patches coming for .coveragerc

On Tue, Sep 22, 2015, at 02:59 AM, Alan Pevec wrote: > 2015-09-21 16:12 GMT+02:00 Monty Taylor : > > We're running a script right now to submit a change to every project with > > this change. The topic will be coverage-v4 > > stable/kilo has uncapped coverage>=3.6 do we patch-spam it or cap > cove

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On Tue, Sep 15, 2015, at 11:00 AM, Fox, Kevin M wrote: > We run several clouds where there are multiple external networks. the > "just run it in on THE public network" doesn't work. :/ Maybe this would be better expressed as "just run it on an existing public network" then? > > I also strongly rec

Re: [openstack-dev] [neutron][gate] please stop approving patches until netaddr issue is solved

I was just looking at this, it appears that keystonemiddleware caps pbr to <1.0 so pulls down 0.11. http://logs.openstack.org/87/218987/1/check/gate-tempest-dsvm-large-ops/a32152f/logs/devstacklog.txt.gz#_2015-08-31_20_28_11_159 different job but same result. Clark On Mon, Aug 31, 2015, at 01:55

Re: [openstack-dev] [neutron][gate] please stop approving patches until netaddr issue is solved

If the check tests ran prior to the netaddr release and got a +1 any approvals will put them straight into the gate. They will only go through check first (and fail there) if they do not already have a +1 from Jenkins. When they fail in the gate they reset all the changes behind them. When you hav

Re: [openstack-dev] [release] Liberty release branches / [non] capping process

On Tue, Aug 25, 2015, at 05:32 AM, Thierry Carrez wrote: > Thierry Carrez wrote: > > [...] > > 1. Enable master->stable cross-check > > 2. Release Oslo, make stable branches for Oslo > > 2.1 Converge constraints > > 3. liberty-3 / FF / soft requirements freeze > > 4. hard requirements freeze > > 5.

Re: [openstack-dev] [third-party] Timeout waiting for ssh access

On Tue, Aug 25, 2015, at 05:01 AM, Tang Chen wrote: > Hi all, > > Does anybody have any idea about this problem ? > > Since ubuntu does not have /etc/sysconfig/network-scripts/ifcfg-*, > obviously it is a fedora like fs structure, we have tried to use centos, > but we still got the same error. >

Re: [openstack-dev] [Magnum] Consistent functional test failures

On Thu, Aug 13, 2015, at 03:13 AM, Tom Cammann wrote: > Hi Team, > > Wanted to let you know why we are having consistent functional test > failures in the gate. > > This is being caused by Nova returning "No valid host" to heat: > > 2015-08-13 08:26:16.303 31543 INFO heat.engine.resource [-] CR

Re: [openstack-dev] [Security] Would people see a value in the cve-check-tool? (Reshetova, Elena)

On Wed, Aug 5, 2015, at 08:22 AM, Jeremy Stanley wrote: > On 2015-08-05 15:04:15 + (+), Ian Cordasco wrote: > > One point of clarification. Not every project has to opt into > > global-requirements so this isn't necessarily true. Also with the > > merging of the stackforge and openstack nam

Re: [openstack-dev] [pbr] [stable] [infra] How to generate .Z version increments on stable/liberty commits

On Tue, Aug 4, 2015, at 06:22 AM, Doug Hellmann wrote: > Excerpts from Clark Boylan's message of 2015-08-03 11:54:06 -0700: > > On Mon, Aug 3, 2015, at 05:46 AM, Thierry Carrez wrote: > > > Hi everyone, > > > > > > A month ago the stable branch team decided to move away from > > > synchronized s

Re: [openstack-dev] [pbr] [stable] [infra] How to generate .Z version increments on stable/liberty commits

On Mon, Aug 3, 2015, at 05:46 AM, Thierry Carrez wrote: > Hi everyone, > > A month ago the stable branch team decided to move away from > synchronized stable point releases and enable continuous stable branch > delivery instead. > > The end goal is that every commit on a stable branch for a "serv

Re: [openstack-dev] [infra] Getting notified of closed pull requests on github?

On Wed, Jul 29, 2015, at 09:14 AM, Joshua Harlow wrote: > Every now and then I go look at github to see what pull requests have > been auto-closed there, since it seems most of the repos under > https://github.com/openstack/(.*) auto-close pull requests (with > messages telling people to use ger

Re: [openstack-dev] [neutron][testing] How to modify DSVM tests to use a DevStack plugin?

On Fri, Jul 24, 2015, at 02:05 PM, Paul Michali wrote: > Hi, > > I've created a DevStack plugin for the neutron-vpnaas repo. Now, I'm > trying > to remove the q-vpn service setup from the DevStack repo ( > https://review.openstack.org/#/c/201119/). > > However, I'm hitting an issue in that (almos

Re: [openstack-dev] Friday 1900UTC etherpad.openstack.org downtime for DB maintenance

On Tue, Jun 30, 2015, at 04:16 PM, Clark Boylan wrote: > Hello, > > The Infra team will be taking etherpad.openstack.org offline this Friday > (July 3rd) at 1900UTC to upgrade the database instance that backs this > service. This upgrade will allow us to convert the utf8 character

[openstack-dev] Friday 1900UTC etherpad.openstack.org downtime for DB maintenance

Hello, The Infra team will be taking etherpad.openstack.org offline this Friday (July 3rd) at 1900UTC to upgrade the database instance that backs this service. This upgrade will allow us to convert the utf8 character set in the db to one supporting 4 byte characters fixing a major bug discovered d

Re: [openstack-dev] [all] Any other downstream developers having problems with pbr?

On Fri, Jun 26, 2015, at 04:01 AM, Matthew Booth wrote: > I wrote this: > > https://review.openstack.org/#/c/195983/1/tools/de-pbr.py,cm > > Ideally we'd fix PBR, but this seems to be expected behaviour. Thoughts? > Use the PBR_VERSION env var [1], it exists so that downstreams can assert a spec

Re: [openstack-dev] [all] setting the clock to remove pypy testing

On Thu, May 14, 2015, at 05:53 AM, Sean Dague wrote: > We've disabled all the pypy tests across OpenStack because it was > failing, and after 48hrs no one was actually working on any fixes. It's > thus effectively just burning nodes for no value. I think my change to upgrade virtualenv on our tes

Re: [openstack-dev] [pbr] regular releases, and path to 1.0

On Mon, May 4, 2015, at 12:53 PM, Robert Collins wrote: > Hi, I'd like to talk about how often we can and should release pbr, > and what criteria we should use for 1.0. > > tl;dr: release weekly [outside of organisation-wide-freezes], do a 1.0 > immediately. > > pbr, like all our libraries affe

[openstack-dev] etherpad.openstack.org upgraded

Just letting everyone know I just upgraded etherpad.openstack.org to the latest etherpad-lite version to address CVE-2015-3297. If you see any javascript load errors you may need to do a hard refresh of your etherpads (sorry about this, I will have to figure out a way to invalidate cached js autom

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

On Wed, Mar 11, 2015, at 05:59 AM, Sean Dague wrote: > Galera Upstream Testing > --- > > The majority of deploys run with Galera MySQL. There was a question > about whether or not we could get that into upstream testing pipeline > as that's the common case. > It should be poss

Re: [openstack-dev] [devstack] [Cinder-GlusterFS CI] centos7 gate job abrupt failures

On Thu, Feb 26, 2015, at 03:03 AM, Deepak Shetty wrote: > On Wed, Feb 25, 2015 at 6:11 AM, Jeremy Stanley > wrote: > > > On 2015-02-25 01:02:07 +0530 (+0530), Bharat Kumar wrote: > > [...] > > > After running 971 test cases VM inaccessible for 569 ticks > > [...] > > > > Glad you're able to rep

Re: [openstack-dev] [infra] [cinder] CI via infra for the DRBD Cinder driver

On Fri, Feb 20, 2015, at 11:24 AM, Philipp Marek wrote: > Hi all, > > this is a reflection of the discussion I just had on #openstack-infra; > it's > about (re-)using the central CI infrastructure for our Open-Source DRBD > driver too. > > > The current status is: > * The DRBD driver is alrea

Re: [openstack-dev] [OpenStack-Dev] [gate tests] Cinder drivers being set up as jobs in infra

On Thu, Feb 19, 2015, at 04:38 PM, John Griffith wrote: > Hey Everyone, > > Anteaya was kind enough to ask in the Cinder channel about some tests > that were added to the gate for SheepDog [1]. I would like to know > why there's no process for the projects that are impacted by these > changes t

Re: [openstack-dev] The root-cause for IRC private channels (was Re: [all][tc] Lets keep our community open, lets fight for it)

On Tue, Feb 17, 2015, at 09:32 AM, Stefano Maffulli wrote: > Changing the subject since Flavio's call for openness was broader than > just private IRC channels. > > On Tue, 2015-02-17 at 10:37 +, Daniel P. Berrange wrote: > > If cases of bad community behaviour, such as use of passwd protected

Re: [openstack-dev] [devstack] Compute-node-only installation fails

On Wed, Feb 11, 2015, at 08:18 AM, Alexander Schmidt wrote: > Hi Daniel, > > with your recent change[1] to error handling in stack.sh, compute > node only installations via devstack fail because there is > no database selected. A database should not be required on > compute nodes. > > Was this do

Re: [openstack-dev] [infra] Nominating Elizabeth K. Joseph for infra-core and root

On Fri, Jan 30, 2015, at 09:20 AM, James E. Blair wrote: > Hi, > > The Infrastructure program has a unique three-tier team structure: > contributors (that's all of us!), core members (people with +2 ability > on infra projects in Gerrit) and root members (people with > administrative access). Rea

Re: [openstack-dev] [oslo] temporarily disabling python 3.x testing for oslo.messaging and oslo.rootwrap

On Tue, Jan 27, 2015, at 09:13 AM, Julien Danjou wrote: > On Tue, Jan 27 2015, Doug Hellmann wrote: > > > The infra team has been working hard to update our Python 3 testing for all > > projects to run on 3.4 instead of 3.3. Two of the last projects to be able > > to > > shift are oslo.messagin

Re: [openstack-dev] [oslo] temporarily disabling python 3.x testing for oslo.messaging and oslo.rootwrap

On Tue, Jan 27, 2015, at 09:06 AM, victor stinner wrote: > Hi, > > What is the Python bug? Do you have a reference to the bug report and the > patch? > https://bugs.launchpad.net/ubuntu/trusty/+source/python3.4/+bug/1367907 Is the bug I filed with the ubuntu package and it has links back to the

Re: [openstack-dev] [tc][python-clients] More freedom for all python clients

On Wed, Jan 14, 2015, at 04:50 AM, Sean Dague wrote: > On 01/14/2015 03:55 AM, Flavio Percoco wrote: > > On 13/01/15 14:31 -0500, Sean Dague wrote: > >> On 01/13/2015 02:10 PM, Jay Pipes wrote: > >>> On 01/13/2015 12:39 PM, Zane Bitter wrote: > On 13/01/15 10:01, Jeremy Stanley wrote: > >

Re: [openstack-dev] oslo.db 1.3.0 released

On Mon, Dec 15, 2014, at 11:09 AM, Doug Hellmann wrote: > > On Dec 15, 2014, at 2:02 PM, Donald Stufft wrote: > > > > >> On Dec 15, 2014, at 1:57 PM, Sean Dague wrote: > >> > >> On 12/15/2014 01:53 PM, Donald Stufft wrote: > >>> > On Dec 15, 2014, at 1:50 PM, Sean Dague wrote: >

Re: [openstack-dev] Session length on wiki.openstack.org

On Fri, Dec 5, 2014, at 06:26 AM, Jeremy Stanley wrote: > On 2014-12-04 18:37:48 -0700 (-0700), Carl Baldwin wrote: > > +1 I've been meaning to say something like this but never got > > around to it. Thanks for speaking up. > > https://storyboard.openstack.org/#!/story/1172753 > > I think Ryan

[openstack-dev] Deprecation of Python 2.6 CI Testing

Hello, At the Atlanta summit there was a session on removing python2.6 testing/support from the OpenStack Kilo release [0]. The Infra team is working on enacting this change in the near future. The way that this will work is python26 jobs will be removed from running on master and feature branche

Re: [openstack-dev] [api] API Workgroup git repository

It is a code change :) Everything is a code change around here. You will want to update the projects.yaml file in openstack-infra/project-config [0]. If you add a 'homepage: https://wiki.openstack.org/wiki/API_Working_Group' key value pair to the api-wg dict there the jeepyb tooling should update t

[openstack-dev] [nova][neutron] "Sideways" grenade job to test Nova Network to Neutron migration

Hello, One of the requirements placed on Ironic was that they must have a path from Nova Baremetal to Ironic and that path should be tested. This resulted in a "sideways" grenade job which instead of going from one release of OpenStack to another, swaps out components within a release. In this cas

Re: [openstack-dev] [infra] Nominating Anita Kuno for project-config-core

On September 26, 2014 8:34:48 AM PDT, cor...@inaugust.com wrote: >I'm pleased to nominate Anito Kuno to the project-config core team. > >The project-config repo is a constituent of the Infrastructure Program >and has a core team structured to be a superset of infra-core with >additional reviewers w

Re: [openstack-dev] [infra] Nominating Andreas Jaeger for project-config-core

On September 26, 2014 8:35:02 AM PDT, cor...@inaugust.com wrote: >I'm pleased to nominate Andreas Jaeger to the project-config core team. > >The project-config repo is a constituent of the Infrastructure Program >and has a core team structured to be a superset of infra-core with >additional reviewe

Re: [openstack-dev] [infra] Nominating Sean Dague for project-config-core

On September 26, 2014 8:35:18 AM PDT, cor...@inaugust.com wrote: >I'm pleased to nominate Sean Dague to the project-config core team. > >The project-config repo is a constituent of the Infrastructure Program >and has a core team structured to be a superset of infra-core with >additional reviewers w

Re: [openstack-dev] Unusual behavior on committing a change

On Mon, Sep 29, 2014, at 12:34 PM, Sharan Kumar M wrote: > Hi all, > > I am getting some weird things when I try to submit a patch for review. > May > be I am doing something wrong. > > I cloned the repo, setup git review and setup my gerrit username in git > config. I updated an image in the doc

Re: [openstack-dev] PostgreSQL jobs slow in the gate

On Wed, Sep 17, 2014, at 06:48 PM, Clark Boylan wrote: > On Wed, Sep 17, 2014, at 06:37 PM, Matt Riedemann wrote: > > > > > > On 9/17/2014 7:59 PM, Ian Wienand wrote: > > > On 09/18/2014 09:49 AM, Clark Boylan wrote: > > >> Recent sampling of test

Re: [openstack-dev] PostgreSQL jobs slow in the gate

On Wed, Sep 17, 2014, at 06:37 PM, Matt Riedemann wrote: > > > On 9/17/2014 7:59 PM, Ian Wienand wrote: > > On 09/18/2014 09:49 AM, Clark Boylan wrote: > >> Recent sampling of test run times shows that our tempest jobs run > >> against clouds using PostgreSQL a

[openstack-dev] PostgreSQL jobs slow in the gate

Hello, Recent sampling of test run times shows that our tempest jobs run against clouds using PostgreSQL are significantly slower than jobs run against clouds using MySQL. (check|gate)-tempest-dsvm-full has an average run time of 52.9 minutes (stddev 5.92 minutes) over 516 runs. (check|gate)-temp

Re: [openstack-dev] China blocking access to OpenStack git review push

On Mon, Sep 8, 2014, at 12:20 PM, Thomas Goirand wrote: > Am I dreaming, or is the Chinese government is trying to push for the > cloud, they said. However, today, bad surprise: > > # nmap -p 29418 23.253.232.87 > > Starting Nmap 6.00 ( http://nmap.org ) at 2014-09-09 03:10 CST > Nmap scan report

Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt

On Wed, Sep 3, 2014, at 01:06 PM, Kuvaja, Erno wrote: > > -Original Message- > > From: Clark Boylan [mailto:cboy...@sapwetik.org] > > Sent: 03 September 2014 20:10 > > To: openstack-dev@lists.openstack.org > > Subject: Re: [openstack-dev] [

Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt

On Wed, Sep 3, 2014, at 11:51 AM, Kuvaja, Erno wrote: > > -Original Message- > > From: Sean Dague [mailto:s...@dague.net] > > Sent: 03 September 2014 13:37 > > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev] [all] [glance] do NOT ever sort req

Re: [openstack-dev] znc as a service (was Re: [nova] Is the BP approval process broken?)

On Wed, Sep 3, 2014, at 07:26 AM, Ryan Brown wrote: > On 09/03/2014 09:35 AM, Sylvain Bauza wrote: > > Re: ZNC as a service, I think it's OK provided the implementation is > > open-sourced with openstack-infra repo group, as for Gerrit, Zuul and > > others. > > The only problem I can see is how to

Re: [openstack-dev] [oslo] [infra] Alpha wheels for Python 3.x

On Wed, Sep 3, 2014, at 08:22 AM, Doug Hellmann wrote: > > On Sep 2, 2014, at 3:17 PM, Clark Boylan wrote: > > > On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote: > >> Hello. > >> > >> Currently for alpha releases of oslo libraries we generate eit

Re: [openstack-dev] [oslo] [infra] Alpha wheels for Python 3.x

On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote: > Hello. > > Currently for alpha releases of oslo libraries we generate either > universal > or Python 2.x-only wheels. This presents a problem: we can't adopt alpha > releases in projects where Python 3.x is supported and verified in the > ga

Re: [openstack-dev] [infra] [neutron] [tc] Neutron Incubator workflow

On Wed, Aug 27, 2014, at 04:05 PM, Joe Gordon wrote: > On Wed, Aug 27, 2014 at 12:30 PM, James E. Blair > wrote: > > > Kevin Benton writes: > > > > > From what I understand, the intended projects for the incubator can't > > > operate without neutron because they are just extensions/plugins/drive

Re: [openstack-dev] [infra] [neutron] [tc] Neutron Incubator workflow

On Wed, Aug 27, 2014, at 03:52 PM, Ivar Lazzaro wrote: > Quoting Stefano from a different thread [0]: > > The rationale for the separate repository is that Neutron's code needs a > > lot of love for the *existing* codebase, before new features can be > > added (and before core team can accept mo

Re: [openstack-dev] [cinder]pylint errors with hashlib

On Mon, Aug 25, 2014, at 06:45 PM, Murali Balcha wrote: > Pylint on my patch is failing with the following error: > > Module 'hashlib' has no 'sha256' > > Cinder pylint already has following exceptions, > > > pylint_exceptions:["Instance of 'sha1' has no 'update' member", ""] > > pylint_except

Re: [openstack-dev] [Neutron] [LBaaS] LBaaS v2 API syntax additions/changes

On Sun, Aug 24, 2014, at 06:37 AM, John Schwarz wrote: > Hi, > > With the ongoing development of LBaaS v2, support for v2 of LBaaS in > neutronclient is also being developed, as can be seen in [1]. > The current implementation adds a new syntax for v2; Whereas the v1 > syntax is 'neutron lb--', th

Re: [openstack-dev] [all] new testtools breaking gate

On Fri, Aug 22, 2014, at 05:55 AM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi all, > > this week is quite bumpy for unit testing in gate. First, it was > upgrade to new 'tox' version that broke quite some branches. > I did a ton of work to make the tox upgr

Re: [openstack-dev] [Ceilometer][WSME] Sphinx failing sporadically because of wsme autodoc extension

On Thu, Aug 21, 2014, at 11:25 AM, Doug Hellmann wrote: > > On Aug 21, 2014, at 8:30 AM, Nejc Saje wrote: > > > Yesterday, doc builds started failing sporadically in Ceilometer gate. > > > > http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkVSUk9SOiBJbnZvY2F0aW9uRXJyb3I6ICcvaG9tZS9qZW5raW5zL3dvc

Re: [openstack-dev] [nova][libvirt] Non-readonly connection to libvirt in unit tests

On Thu, Aug 21, 2014, at 09:25 AM, Matt Riedemann wrote: > > > On 8/21/2014 10:23 AM, Daniel P. Berrange wrote: > > On Thu, Aug 21, 2014 at 11:14:33AM -0400, Solly Ross wrote: > >> (reply inline) > >> > >> - Original Message - > >>> From: "Daniel P. Berrange" > >>> To: "OpenStack Devel

Re: [openstack-dev] [All] Switching default test node to Trusty for all projects and upgrading tox to version 1.7.2

On Tue, Aug 5, 2014, at 05:04 PM, Clark Boylan wrote: > Hello, > > On August 20th the Infra team will be switching the default test node > from Ubuntu Precise to Ubuntu Trusty. This means that `tox -epy27`, `tox > -ecover`, `tox -epep8`, `tox -evenv -- python setup.py build_sphinx

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

On Mon, Aug 18, 2014, at 01:59 AM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 17/08/14 02:09, Angus Lees wrote: > > > > On 16 Aug 2014 06:09, "Doug Hellmann" > > wrote: > >> > >> > >> On Aug 15, 2014, at 9:29 AM, Ihar Hrachys

[openstack-dev] [All] Switching default test node to Trusty for all projects and upgrading tox to version 1.7.2

Hello, On August 20th the Infra team will be switching the default test node from Ubuntu Precise to Ubuntu Trusty. This means that `tox -epy27`, `tox -ecover`, `tox -epep8`, `tox -evenv -- python setup.py build_sphinx` will run on Trusty build nodes intead of Precise nodes. This will not affect py

[openstack-dev] [All] Gate bugs in the real world

Hello, An interesting thing happened today. The Infra team noticed that nodepool was unable to delete a significant number of nodes from the two public clouds we use to test OpenStack. Upon further investigation it was determined that we were hitting https://bugs.launchpad.net/python-neutronclien

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On Wed, Jul 30, 2014, at 03:23 PM, Jeremy Stanley wrote: > On 2014-07-30 13:21:10 -0700 (-0700), Joe Gordon wrote: > > While forcing people to move to a newer version of libvirt is > > doable on most environments, do we want to do that now? What is > > the benefit of doing so? > [...] > > The only

[openstack-dev] [ALL] Removing the tox==1.6.1 pin

Hello, The recent release of tox 1.7.2 has fixed the {posargs} interpolation issues we had with newer tox which forced us to be pinned to tox==1.6.1. Before we can remove the pin and start telling people to use latest tox we need to address a new default behavior in tox. New tox sets a random PYT

Re: [openstack-dev] [Infra] MyISAM as a default storage engine for MySQL in the gate

On Jul 21, 2014 8:28 AM, "Roman Podoliaka" wrote: > > Hi all, > > To my surprise I found that we default to using MyISAM in the gate > [1], while InnoDB would be a much more suitable choice, which people > use in production deployments (== we should test it in the gate). This > means, that every t

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Wed, Jul 16, 2014 at 7:50 AM, Daniel P. Berrange wrote: > On Wed, Jul 16, 2014 at 04:15:40PM +0200, Sean Dague wrote: >> Recently the main gate updated from Ubuntu 12.04 to 14.04, and in doing >> so we started executing the livesnapshot code in the nova libvirt >> driver. Which fails about 20%

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

On Sun, Jul 13, 2014 at 9:20 AM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 11/07/14 19:20, Clark Boylan wrote: >> Before we get too far ahead of ourselves mysql-connector is not >> hosted on pypi. Instead it is an external p

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

Before we get too far ahead of ourselves mysql-connector is not hosted on pypi. Instead it is an external package link. We recently managed to remove all packages that are hosted as external package links from openstack and will not add new ones in. Before we can use mysql-connector in the gate ora

Re: [openstack-dev] [Infra] Jenkins gate jobs fails

On Thu, Jul 10, 2014 at 10:12 PM, stanzgy wrote: > Several jenkins gate jobs failed since some lib packages in ubuntu source > are missing and devstack failed to setup the tempest env. Could there be > someone help to fix this? > I have filed the bug here: > https://bugs.launchpad.net/openstack-ci

Re: [openstack-dev] Policy around Requirements Adds (was: New class of requirements for Stackforge projects)

d give serious consideration to adding python-mistralclient to >> > global requirements. I have posted a review[3] for that to get input >> > from the requirements review team. >> > >> > Thanks, >> > >> > Adrian >> > >> > [1] https://re

Re: [openstack-dev] [Infra][Solum][Mistral] New class of requirements for Stackforge projects

On Tue, Jun 24, 2014 at 9:54 PM, Adrian Otto wrote: > Hello, > > Solum has run into a constraint with the current scheme for requirements > management within the OpenStack CI system. We have a proposal for dealing > with this constraint that involves making a contribution to openstack-infra. >

[openstack-dev] [All] Tempest testing for master is now running on Trusty

Hello everyone, The Infra team switched all Tempest testing (really all jenkins jobs with names containing 'dsvm') for the master branch to Trusty slaves today. This means that integration testing has access to new libvirt, new mongodb, and new kernels among other things. Python27 unittesting for

Re: [openstack-dev] [OpenStack-Infra] [infra] Nominations for jenkins-job-builder core

On Mon, Jun 23, 2014 at 1:35 AM, Antoine Musso wrote: > Le 23/06/2014 01:47, Jeremy Stanley a écrit : >> On 2014-06-20 14:01:01 -0700 (-0700), James E. Blair wrote: >>> > The Jenkins Job Builder project [...] core reviewers [...] I would >>> > like to add Darragh Bailey [...] and Marc Abramowitz >

Re: [openstack-dev] [OpenStack-Infra] Nomination for python-jenkins

On Mon, Jun 23, 2014 at 1:42 AM, Antoine Musso wrote: > Hello, > > The python-jenkins module is a thin wrapper to interact with Jenkins. It > has been migrated from Launchpad to Stackforge a couple months ago to > attract more developers and easily upstream work down being done in over > OpenStack

Re: [openstack-dev] DevStack hacks requirements.txt et al

On Tue, Jun 17, 2014 at 10:33 PM, Mike Spreitzer wrote: > I have noticed that lately DevStack has been hacking requirements.txt in > most projects and test-requirements.txt in many. Why is this being done? > > Thanks, > Mike > ___ > OpenStack-dev mailin

Re: [openstack-dev] [All] Disabling Pushes of new Gerrit Draft Patchsets

h patches to affect gerrit stream or trigger CIs, but > gerrit could still be used for regular reviewing process. > > Thanks, > Eugene. > > > On Sat, May 31, 2014 at 12:51 AM, Sergey Lukjanov > wrote: >> >> Yay! >> >> No more weird CR chains. >> &

Re: [openstack-dev] [All] Disabling Pushes of new Gerrit Draft Patchsets

On Wed, May 21, 2014 at 4:24 PM, Clark Boylan wrote: > Hello everyone, > > Gerrit has long supported "Draft" patchsets, and the infra team has long > recommended against using them as they are a source of bugs and > confusion (see below for specific details if yo

[openstack-dev] [All] Disabling Pushes of new Gerrit Draft Patchsets

Hello everyone, Gerrit has long supported "Draft" patchsets, and the infra team has long recommended against using them as they are a source of bugs and confusion (see below for specific details if you are curious). The newer version of Gerrit that we recently upgraded to allows us to prevent peop

Re: [openstack-dev] [infra] Nominating Joshua Hesketh for infra-core

On Wed, May 21, 2014 at 2:57 PM, James E. Blair wrote: > The Infrastructure program has a unique three-tier team structure: > contributors (that's all of us!), core members (people with +2 ability > on infra projects in Gerrit) and root members (people with > administrative access). Read all abou

Re: [openstack-dev] [infra] Nominating Sergey Lukjanov for infra-root

On Wed, May 21, 2014 at 2:42 PM, James E. Blair wrote: > The Infrastructure program has a unique three-tier team structure: > contributors (that's all of us!), core members (people with +2 ability > on infra projects in Gerrit) and root members (people with > administrative access). Read all abou

Re: [openstack-dev] [all] process problem with release tagging

On Mon, May 5, 2014 at 5:14 PM, John Dickinson wrote: > tl;dr: (1) the current tag names used don't work and we need > something else. (2) Swift (at least) needs to burn a > release number with a new tag > > The current process of release is: > > 1) branch milestone-proposed (hereafter, m-p) from

Re: [openstack-dev] [Nova] Juno open for development

The infrastructure team can update the OSes used by the gate when new versions of the distros we use release, and our cloud providers make those images available to us (or provide us with glance upload access, whichever comes first). That means we can't upgrade Ubuntu to Trusty until Trusty release

Re: [openstack-dev] [depfreeze] Exception: limit psutil to <2.0.0

On Wed, Mar 26, 2014 at 12:32 PM, Solly Ross wrote: > What bug tracker should I file under? I tried filing one under the openstack > common infrastructure tracker, > but was told that it wasn't the correct place to file such a bug. > > Best Regards, > Solly Ross > > - Original Message -

Re: [openstack-dev] [Neutron] Error while running tox -v -epy27 tests.unit.ml2

On Mon, Mar 24, 2014 at 1:35 PM, Chris Jones wrote: > > Hello; > > I was talking with some people on the openstack-neutron IRC channel, and was > trying to get assistance to root cause why the ml2 unit tests are failing. > I have cloned a fresh neutron tree that I have pegged back to hash: b78eea6

[openstack-dev] Jenkins test logs and their retention period

ph_id=717&rra_id=all Thank you, Clark Boylan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] testr help

On Mon, Mar 10, 2014 at 4:20 PM, Zane Bitter wrote: > On 10/03/14 16:04, Clark Boylan wrote: >> >> On Mon, Mar 10, 2014 at 11:31 AM, Zane Bitter wrote: >>> >>> Thanks Clark for this great write-up. However, I think the solution to >>> the >>>

<    1   2   3   4   >