[openstack-dev] [astara] PTL non-candidacy

Hi All- I've decided that I will not be running for Astara PTL this coming cycle. It's been great helping the project grow and find its place within the OpenStack tent over the last 8 months or so. We're a small group of developers and I think its important to stir the pot and let another

[openstack-dev] [astara] Outstanding mitaka-2 bugs

Hi All- I mentioned this in todays meeting but wanted to drop a note here since most of us are out on a US holiday... This week is Mitaka-2 [1] and we still have quite a few outstanding bugs that still need resolution. The good news is that (i think) all of them have had patches up for review

Re: [openstack-dev] [astara][requirements] astara-appliance has requirements not in global-requirements

Thanks for the heads up, Andreas. I've opened https://bugs.launchpad.net/astara/+bug/1526527 and hope to resolve it in the coming days. Cheers Adam On Sun, Dec 13, 2015 at 3:26 AM, Andreas Jaeger wrote: > Astara team, > > The requirements proposal job complains about

Re: [openstack-dev] [astara] contributor meetup during Mitaka summit

been noted on the etherpad [1], but feel free to add more if there's something you'd like to discuss. Cheers, Adam [1] https://etherpad.openstack.org/p/akanda-mitaka-planning On Mon, Oct 26, 2015 at 7:00 PM, Adam Gandelman <gandelma...@gmail.com> wrote: > Should we shoot for a co

[openstack-dev] [astara] contributor meetup during Mitaka summit

Should we shoot for a contributor meetup Friday in the developer lounge, alongside the other project meetups? Does this *not* work for anyone? Is afternoon better than the AM? I propose we meet before lunch and carry on into the afternoon if necessary. Please jot your name down on the etherpad

[openstack-dev] [astara] Announcing the Astara Liberty release (formely Akanda)

Hi All- The Astara team is pleased to announce the availability of the Astara Liberty release. You can find a list of closed bugs, implemented blueprints and release tarballs on launchpad at https://launchpad.net/astara/+milestone/7.0.0. We are proud of what we've accomplished this release and

Re: [openstack-dev] [stable][releases] OpenStack 2014.2.3 released

Correction. Also included in the list of released projects for 2014.2.3, Sahara: https://launchpad.net/sahara/juno/2014.2.3 Apologies, Adam On Mon, Apr 13, 2015 at 10:30 AM, Adam Gandelman gandelma...@gmail.com wrote: Hello everyone, The OpenStack Stable Maintenance team is happy to announce

[openstack-dev] [stable][releases] OpenStack 2014.2.3 released

Hello everyone, The OpenStack Stable Maintenance team is happy to announce the release of the 2014.2.3 stable Juno release. We have been busy reviewing and accepting backported bugfixes to the stable/juno branches according to the criteria set at: https://wiki.openstack.org/wiki/StableBranch A

Re: [openstack-dev] [qa][nova][ironic] How to run microversions tests on the gate

FWIW the Ironic microversion test patch mentioned on gerrit is only targeted at Tempest because thats where the API tests currenty live and from which our infra is setup to run. The eventual goal is to move all of tempest.api.baremetal.* to the Ironic tree, there's no reason why those proposed new

[openstack-dev] [stable] Call for testing: 2014.2.3 candidate tarballs

Hi all, We are scheduled to publish 2014.2.3 on Thursday April 9th for Ceilometer, Cinder, Glance, Heat, Horizon, Keystone, Neutron, Nova, Sahara and Trove. We'd appreciate anyone who could test the candidate 2014.2.3 tarballs, which include all changes aside from any pending freeze exceptions:

[openstack-dev] [stable] Preparing for 2014.2.3 -- branches freeze April 2nd

Hi All- We'll be freezing the stable/juno branches for integrated Juno projects this Thursday April 2nd in preparation for the 2014.2.3 stable release on Thursday April 9th. You can view the current queue of proposed patches on gerrit [1]. I'd like to request all interested parties review

Re: [openstack-dev] [stable] Icehouse 2014.1.4 freeze exceptions

Big +2 on both those, but will leave it up to Alan make the final call Cheers On Wed, Mar 11, 2015 at 3:42 PM, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 12:21 PM, Alan Pevec wrote: Hi, next Icehouse stable point release

Re: [openstack-dev] [stable][requirements] External dependency caps introduced in 499db6b

On Fri, Feb 20, 2015 at 3:06 AM, Sean Dague s...@dague.net wrote: It sounds like you are suggesting we take the tool we use to ensure that all of OpenStack is installable together in a unified way, and change it's installation so that it doesn't do that any more. Which I'm fine with. But

Re: [openstack-dev] [stable][requirements] External dependency caps introduced in 499db6b

On Fri, Feb 20, 2015 at 10:16 AM, Joshua Harlow harlo...@outlook.com wrote: It'd be interesting to see what a distribution (canonical, redhat...) would think about this movement. I know yahoo! has been looking into it for similar reasons (but we are more flexibly then I think a packager such

[openstack-dev] [ironic] Ironic 2014.2.1 released

Hello- The Ironic team is pleased to announce the release of the 2014.2.1 stable Juno release. This release contains a number of backported fixes that have accrued in our stable branch since the release of 2014.2. These updates to Juno are intended to be low risk with no intentional regressions

Re: [openstack-dev] [stable][requirements] External dependency caps introduced in 499db6b

This creates a bit of a problem for downstream (packagers and probably others) Shipping a requirements.txt with explicit pins will end up producing an egg with a requires.txt that reflects those pins, unless there is some other magic planned that I'm not aware of. I can't speak for all packaging

Re: [openstack-dev] [stable][requirements] External dependency caps introduced in 499db6b

with the libraries from git-or-master but we can probably add something to warm the system with dependencies from the compiled version prior to calling pip/setup.py/etc Adam On Thu, Feb 19, 2015 at 2:31 PM, Joe Gordon joe.gord...@gmail.com wrote: On Thu, Feb 19, 2015 at 1:48 PM, Adam Gandelman ad

Re: [openstack-dev] [Ironic] volunteer to be rep for third-party CI

Hi- I believe I'm the one who was volunteered for this on IRC. I'm still fine with being the contact for these matters, but making the meetings at 0800/1500 UTC will be difficult for me. Feel free to sign me up if that is not a blocker. I've been driving the ironic CI/QA stuff over the last

Re: [openstack-dev] [infra] Re: [stable] Stable check of openstack/nova failed - EnvironmentError: mysql_config not found

Looking at the image build logs @ nodepool.openstack.org, it *looks* like package dependencies are not being installed properly on one of the slaves (hpcloud-b2.bare-precise): http://paste.ubuntu.com/9886045/ The failing periodic jobs all land on this b2 node. nodepool is, however, pre-caching

Re: [openstack-dev] [infra] Re: [stable] Stable check of openstack/nova failed - EnvironmentError: mysql_config not found

https://review.openstack.org/150120 should address it. On Mon, Jan 26, 2015 at 11:16 AM, Adam Gandelman ad...@ubuntu.com wrote: Looking at the image build logs @ nodepool.openstack.org, it *looks* like package dependencies are not being installed properly on one of the slaves (hpcloud-b2.bare

Re: [openstack-dev] [stable] Stable branch status and proposed stable-maint members mentoring

Thanks, Ihar. Lets make this the 'official' tracking pad for stable branches. We were previously using branch-specific pads (ie, https://etherpad.openstack.org/p/StableJuno) but it makes sense to track both releases in one place. I've updated it with current staus there and added a reference on

Re: [openstack-dev] [nova]nova not work with eventlet 0.16.0

So eventlet 0.16.x has started hitting slaves and breaking stable branches (its not like we weren't warned :\ ) https://bugs.launchpad.net/nova/+bug/1410626 Should hopefully be resolved by eventlet versions caps in icehouse + juno's requirements:

[openstack-dev] [stable] Proposal to add Flavio Percoco to stable-maint-core

Hiya- Flavio has been actively involved in stable branch maintenance for as long as I can remember, but it looks like his +2 abilities were removed after the organizational changes made to the stable maintenance teams. He has expressed interest in continuing on with general stable maintenance

[openstack-dev] check-grenade-dsvm-ironic-sideways failing, blocking much code

Heads up here since IRC seems to be crickets this week... Fallout from newer pip's creation and usage of ~/.cache is still biting the sideways ironic grenade job: https://bugs.launchpad.net/ironic/+bug/1405626 This is blocking patches to ironic, nova, devstack, tempest, grenade master +

Re: [openstack-dev] [CI][TripleO][Ironic] check-tripleo-ironic-xxx fails

This is fallout from a new upstream release of pip that went out earlier in the week. It looks like no formal bug ever got filed, tho the same problem discovered in devstack and trove's integration testing repository. Added some comments comments to the bug. On Thu, Dec 25, 2014 at 10:59 PM,

[openstack-dev] [stable] Proposal to add Dave Walker back to stable-maint-core

Hi All- Daviey was an original member of the stable-maint team and one of the driving forces behind the creation of the team and branches back in the early days. He was removed from the team later on during a pruning of inactive members. Recently, he has began focusing on the stable branches

Re: [openstack-dev] [all] icehouse failure rates are somewhat catastrophic - who is actually maintaining it?

The stable-maint team has been more active in the last couple months of keeping on top of stable branch specific gate breakage (usually identified by periodic job failures). We managed to flush a bunch of reviews through the gate over the last couple weeks [1] Yea, many required rechecks, but the

[openstack-dev] Call for testing: 2014.1.3 candidate tarballs

Hi all, We are scheduled to publish 2014.1.3 on Thurs Oct. 2nd for Ceilometer, Cinder, Glance, Heat, Horizon, Keystone, Neutron, Nova and Trove. The list of issues fixed so far can be seen here: https://launchpad.net/ceilometer/+milestone/2014.1.3

[openstack-dev] Preparing for 2014.1.3 -- branches freeze September 25th

Hi All- We'll be freezing the stable/icehouse branches for integrated projects this Thursday September 25th in preparation for the 2014.1.3 stable release on Thursday October 2nd. You can view the current queue of proposed patches on gerrit [1]. I'd like to request all interested parties review

Re: [openstack-dev] [Ironic] Error in deploying ironicon Ubuntu 12.04

On Mon, Sep 15, 2014 at 11:38 PM, Peeyush Gupta gpeey...@linux.vnet.ibm.com wrote: What I am interested to know is if this is a problem with precise or with devstack script? As mentioned, we test this in the gate using Ubuntu Trusty 14.04. When we were using Precise, we would setup access

Re: [openstack-dev] [ironic] [neutron] make mac address updatable - port status for ironic servers

Yes, its to be expected. IIRC, you were helping me investigate the same thing at the TripleO mid-cycle. :) The port gets the necessary configuration setup by the DHCP agent to take care of PXE, but this being baremetal there is no hypervisor on which some agent is running and plugging VIFs into

Re: [openstack-dev] Problematic gate-tempest-dsvm-virtual-ironic job

I've opened https://bugs.launchpad.net/openstack-ci/+bug/1329430 to track the progress of getting the ironic job in better shape. Monty had a great suggestion this morning about how cache_devstack.py can be updated to cache the UCA stuff for any job that may need it. I'm putting together a patch

Re: [openstack-dev] [TripleO] pacemaker management tools

It's been a while since I've used these tools and I'm not 100% surprised they've fragmented once again. :) That said, does pcs support creating the CIB configuration in bulk from a file? I know that crm shell would let you dump the entire cluster config and restore from file. Unless the CIB

Re: [openstack-dev] [nova][neutron] VIF event callbacks implementation

On Tue, Apr 29, 2014 at 12:23 PM, Dan Smith d...@danplanet.com wrote: Yeah, we've already got plans in place to get Cinder to use the interface to provide us more detailed information and eliminate some polling. We also have a very purpose-built notification scheme between nova and cinder

[openstack-dev] [Ironic][QA] Ironic functional gate tests stable, thoughts on extending?

Hi All-- We've finally got the check-tempest-dsvm-virtual-ironic passing successfully in the Ironic gate. Among other things, this test runs the tempest.scenario.test_baremetal_basic_ops which is a functional provisioning test directly stressing Ironic, Nova and Neutron as well as devstack and

Re: [openstack-dev] [qa] Selecting Compute tests by driver/hypervisor

On Tue, Apr 22, 2014 at 4:23 AM, Sean Dague s...@dague.net wrote: Agreed. Though I think we probably want the Nova API to be explicit about what parts of the API it's ok to throw a Not Supported. Because I don't think it's a blanket ok. On API endpoints where this is ok, we can convert not

[openstack-dev] Call for testing: 2013.2.3 candidate tarballs

Hi all, We are scheduled to publish the 2013.2.3 release on Thursday April 3 for Ceilometer, Cinder, Glance, Heat, Horizon, Keystone, Neutron and Nova. The list of issues fixed so far can be seen here: https://launchpad.net/ceilometer/+milestone/2013.2.3

[openstack-dev] Preparing for 2013.2.3 -- branches freeze March 27th

Hi All- We'll be freezing the stable/havana branches for integrated projects this Thursday March 27th in preparation for the 2013.2.3 stable release on Thursday April 3rd. You can view the current queue of proposed patches on gerrit [1]. I'd like to request all interested parties review current

[openstack-dev] [Ironic] Functional testing, Tempest

Hi-- We've made some progress over the last week or so toward more thorough Ironic CI: * Initial devstack support has been merged enabling an all-in-one Ironic environment that uses libvirt+VMs+OVS to support baremetal deployments [1] * Devananda and myself have been getting patches pushed into

Re: [openstack-dev] [Openstack-stable-maint] Stable/grizzly

On 10/10/2013 04:42 AM, Gary Kotton wrote: Trunk - https://review.openstack.org/50904 Stable/Grizzly - https://review.openstack.org/#/c/50905/ There is an alternative patch - https://review.openstack.org/#/c/50873/7 I recall seeing the same problem a few month ago and the bot version was

Re: [openstack-dev] Gate issues - what you can do to help

On 10/01/2013 12:02 AM, Alan Pevec wrote: 1) Please *do not* Approve or Reverify stable/* patches. The pyparsing requirements conflict with neutron client from earlier in the week is still not resolved on stable/*. Also there's an issue with quantumclient and Nova stable/grizzly: