Re: [openstack-dev] [tc] [ptl] PTL E-mail addresses on rendered team pages

On Fri, Jun 15, 2018 at 03:05:51PM -0400, Doug Hellmann wrote: > Excerpts from Jean-Philippe Evrard's message of 2018-06-15 17:37:02 +0200: > > > Not sure it'd help but one option we do is to create aliases based on > > > the title. Though since the PTLs don't have addresses on the openstack > >

Re: [openstack-dev] [neutron][stable] Stepping down from core

On Mon, Jun 04, 2018 at 01:31:11PM -0700, Ihar Hrachyshka wrote: > Hi neutrinos and all, > > As some of you've already noticed, the last several months I was > scaling down my involvement in Neutron and, more generally, OpenStack. > I am at a point where I feel confident my disappearance won't

Re: [openstack-dev] [stable][kolla] tagging newton EOL

On Sat, Apr 14, 2018 at 11:02:54AM +0800, Jeffrey Zhang wrote: > hi stable team, > > Kolla project is ready for Newton EOL. Since kolla-ansible is split from > kolla since ocata cycle, so there is not newton branch in kolla-ansible. > please make following repo EOL > > openstack/kolla Okay I

Re: [openstack-dev] [OpenStackAnsible] Tag repos as newton-eol

On Sun, Apr 29, 2018 at 09:36:15AM +0200, Jean-Philippe Evrard wrote: > Hello, > > > I'd like to phase out openstack/openstack-ansible-tests and > > openstack/openstack-ansible later. > > Now that we had the time to bump the roles in openstack-ansible, and > adapt the tests, we can now EOL the

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

On Wed, May 16, 2018 at 04:14:36PM -0500, Matthew Thode wrote: > On 18-05-16 17:07:09, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500: > > > Sphinx has breaking changes (yet again) and we need to figure out how to > > > deal with it. I think the fix

Re: [openstack-dev] [ironic][stable] Re-adding Jim Rollenhagen to ironic stable maintenance team?

On Fri, May 11, 2018 at 08:37:43AM -0400, Julia Kreger wrote: > On Fri, May 11, 2018 at 8:20 AM, Dmitry Tantsur wrote: > > Hi, > [trim] > >> If there are no objections, I'll re-add him next week. > > > > > > I don't remember if we actually can add people to these teams or it

Re: [openstack-dev] Changes to keystone-stable-maint members

On Tue, Apr 24, 2018 at 10:58:06AM -0700, Morgan Fainberg wrote: > Hi, > > I am proposing making some changes to the Keystone Stable Maint team. > A lot of this is cleanup for contributors that have moved on from > OpenStack. For the most part, I've been the only one responsible for > Keystone

Re: [openstack-dev] [tripleo] roadmap on containers workflow

On Sun, Apr 15, 2018 at 07:24:58PM -0700, Emilien Macchi wrote: > This patch: https://review.openstack.org/#/c/561377 is deploying Docker and > Docker Registry v2 *before* containers deployment in the docker_steps. > It's using the external_deploy_tasks interface that runs right after the >

Re: [openstack-dev] [all][requirements] uncapping eventlet

On Mon, Apr 09, 2018 at 09:58:28AM -0400, Doug Hellmann wrote: > Now that projects don't have to match the global requirements list > entries exactly we should be able to remove caps from within the > projects and keep caps in the global list for cases like this where we > know we frequently

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/networking-midonet failed

On Tue, Apr 03, 2018 at 02:05:35PM +0200, Elõd Illés wrote: > Hi, > > These patches probably solve the issue, if someone could review them: > > https://review.openstack.org/#/c/557005/ > > and > > https://review.openstack.org/#/c/557006/ > > Thanks, Thanks for digging into that. I've

Re: [openstack-dev] [all][requirements] uncapping eventlet

On Fri, Apr 06, 2018 at 09:41:07AM -0700, Clark Boylan wrote: > My understanding of our use of upper constraints was that this should > (almost) always be the case for (almost) all dependencies. We should > rely on constraints instead of requirements caps. Capping libs like > pbr or eventlet and

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/networking-midonet failed

On Sat, Mar 31, 2018 at 06:17:41AM +, A mailing list for the OpenStack Stable Branch test reports. wrote: > Build failed. > > - build-openstack-sphinx-docs >

Re: [openstack-dev] [midonet][Openstack-stable-maint] Stable check of openstack/networking-midonet failed

On Sat, Mar 31, 2018 at 06:17:07AM +, A mailing list for the OpenStack Stable Branch test reports. wrote: > Build failed. > > - build-openstack-sphinx-docs >

[openstack-dev] [all][stable] No more stable Phases welcome Extended Maintenance

Hi all, At Sydney we started the process of change on the stable branches. Recently we merged a TC resolution[1] to alter the EOL process. The next step is refinining the stable policy itself. I've created a review to do that. I think it covers most of the points from Sydney and Dublin.

Re: [openstack-dev] [OpenStackAnsible] Tag repos as newton-eol

On Thu, Mar 15, 2018 at 10:57:58AM +, Jean-Philippe Evrard wrote: > Looks good to me. This has been done now. Thanks for being patient :) Yours Tony. signature.asc Description: PGP signature __ OpenStack Development

Re: [openstack-dev] [devstack] stable/queens: How to configure devstack to use openstacksdk===0.11.3 and os-service-types===1.1.0

On Fri, Mar 16, 2018 at 02:29:51PM +, Kwan, Louie wrote: > In the stable/queens branch, since openstacksdk0.11.3 and > os-service-types1.1.0 are described in openstack's upper-constraints.txt, > > https://github.com/openstack/requirements/blob/stable/queens/upper-constraints.txt#L411 >

Re: [openstack-dev] [stable][release] Remove complex ACL changes around releases

On Wed, Mar 28, 2018 at 03:34:32PM +0100, Graham Hayes wrote: > It is more complex than just "joining that team" if the project follows > stable policy. the stable team have to approve the additions, and do > reject people trying to join them. This is true but when we (I) say no I explain what's

Re: [OpenStack-Infra] git review -d without check out

On Tue, Mar 27, 2018 at 02:16:32PM +0300, Ram Rachum wrote: > Hi, > > Is there a way to do `git review -d` without having it do a checkout? i.e. > I just want to have these commits in my Git database so I could cherrypick > them on some other branch. We've got tons of submodules so checking out >

Re: [openstack-dev] [stable][release] Remove complex ACL changes around releases

On Mon, Mar 26, 2018 at 03:33:03PM +0200, Thierry Carrez wrote: > Let me know if you have any comment, otherwise we'll start using that > new process for the Rocky cycle (stable/rocky branch). Sounds good to me, Thanks Thierry Yours Tony. signature.asc Description: PGP signature

Re: [OpenStack-Infra] Adding new etcd binaries to tarballs.o.o

On Tue, Mar 27, 2018 at 10:22:26AM +1100, Ian Wienand wrote: > On 03/27/2018 09:25 AM, Tony Breeds wrote: > > Can we please add the appropriate files for the 3.3.2 (or 3.2.17) > > release of etcd added to tarballs.o.o > > ISTR that we had problems even getting them from

[OpenStack-Infra] Adding new etcd binaries to tarballs.o.o

Hi All, Dredging up the past a little here ... In Denver James, Monty, Paul, Clark and I talked about the fact that we have an unoffical mirror for etcd binaries on tarballs.o.o[1]. We all agreed that this was ... sub-optimal. So I took ownership of getting etcd 3.2 (for all architectures)

Re: [openstack-dev] [OpenStackAnsible] Tag repos as newton-eol

On Wed, Mar 14, 2018 at 09:40:33PM +, Jean-Philippe Evrard wrote: > Hello folks, > > The list is almost perfect: you can do all of those except > openstack/openstack-ansible-tests. > I'd like to phase out openstack/openstack-ansible-tests and > openstack/openstack-ansible later. Okay

Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

On Thu, Mar 15, 2018 at 07:16:11AM +0900, Akihiro Motoki wrote: > The current version of proposed patches which drops tox_install.sh > works in our CI. Even if we have neutron>=12.0.0 (queens) or > horizon>=13.0.0 (queens), if we have "required-projects" in zuul v3 > config, tox-sibling role

[openstack-dev] [OpenStackAnsible] Tag repos as newton-eol

Hi all, JP has asked me to to work with infra to tag the newton branches of the following repos as EOL: openstack/ansible-hardening openstack/openstack-ansible-apt_package_pinning openstack/openstack-ansible-ceph_client openstack/openstack-ansible-galera_client

Re: [openstack-dev] [tripleo] Blueprints for Rocky

On Tue, Mar 13, 2018 at 07:58:48AM -0600, Alex Schultz wrote: > Hey everyone, > > So we currently have 63 blueprints for currently targeted for > Rocky[0]. Please make sure that any blueprints you are interested in > delivering have an assignee set and have been approved. I would like > to have

Re: [openstack-dev] [murano][Openstack-stable-maint] Stable check of openstack/murano failed

On Fri, Mar 09, 2018 at 03:32:02PM +1100, Tony Breeds wrote: > On Thu, Mar 08, 2018 at 06:16:27AM +, A mailing list for the OpenStack > Stable Branch test reports. wrote: > > Build failed. > > > > - build-openstack-sphinx-docs > > http://logs.openstack.org/per

Re: [openstack-dev] [requirements][zun][karbor][magnum][tacker][kolla][tripleo][zaqar][networking-odl] update websocket-client and kubernetes libraries

On Mon, Mar 12, 2018 at 06:47:14PM -0500, Matthew Thode wrote: > Requirements plans to update both versions, removing the current cap on > websocket-cient. The plan to do so is as follows. > > a. Remove the cap on websocket-client This is being done in: https://review.openstack.org/#/c/549664/

Re: [openstack-dev] [murano][Openstack-stable-maint] Stable check of openstack/murano failed

On Thu, Mar 08, 2018 at 06:16:27AM +, A mailing list for the OpenStack Stable Branch test reports. wrote: > Build failed. > > - build-openstack-sphinx-docs > http://logs.openstack.org/periodic-stable/git.openstack.org/openstack/murano/stable/pike/build-openstack-sphinx-docs/8b023b7/html/ >

Re: [openstack-dev] [Release-job-failures] Release of openstack/paunch failed

On Wed, Mar 07, 2018 at 06:05:56AM +, z...@openstack.org wrote: > Build failed. > > - release-openstack-python > http://logs.openstack.org/34/34e767fbcc4dd488c94023b5ee682dd2369db7bd/release/release-openstack-python/5edd302/ > : FAILURE in 16m 43s > - announce-release announce-release :

Re: [openstack-dev] [yaql] [tripleo] Backward incompatible change in YAQL minor version

On Wed, Feb 21, 2018 at 08:53:09PM +0100, Alfredo Moralejo Alonso wrote: > Short version is: > > 1. We generate a review to rdoinfo (RDO's package database) every time a > change is detected in upper-constraints.txt proposing it as candidate in > dependencies repo. > 2. A job in rdoinfo gate

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

On Mon, Feb 19, 2018 at 10:00:59AM -0500, Michael Bayer wrote: > Hi list - > > Apparently Cinder was misled by my deprecations within the > oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and > in https://review.openstack.org/#/c/522290/ the assumption was made > that these

Re: [openstack-dev] [yaql] [tripleo] Backward incompatible change in YAQL minor version

On Mon, Feb 19, 2018 at 03:24:24PM +0100, Bogdan Dobrelya wrote: > With a backport of the YAQL fixes for tht made for Pike, would it be the > full fix to make a backport of yaql 1.1.3 for Pike repos as well? Or am I > missing something? At some level that should be fine. In the broader

Re: [openstack-dev] [yaql] [tripleo] Backward incompatible change in YAQL minor version

On Mon, Feb 19, 2018 at 06:10:56PM +0100, Alfredo Moralejo Alonso wrote: > Recently, we have added a job in post pipeline for openstack/requirements > in https://review.rdoproject.org to > automatically post updates in RDO dependencies repo when changes are > detected in upper-constraints. This >

Re: [openstack-dev] [yaql] [tripleo] Backward incompatible change in YAQL minor version

On Sat, Feb 17, 2018 at 04:40:12PM -0500, Dan Prince wrote: > Thanks for the update Emilien. A couple of things to add: > > 1) This was really difficult to pin-point via the Heat stack error > message ('list index out of range'). I actually had to go and add > LOG.debug statements to Heat to get

Re: [openstack-dev] [requirements][trove][tatu][barbican][compass][daisycloud][freezer][fuel][nova][openstack-ansible][pyghmi][solum] Migration from pycrypto

On Wed, Feb 14, 2018 at 01:59:29PM -0600, Matthew Thode wrote: > On 18-02-14 13:55:53, Sean McGinnis wrote: > > On Wed, Feb 14, 2018 at 10:09:47AM -0600, Matthew Thode wrote: > > > Development has stalled, (since 2014). It's been forked but now would > > > be a good time to move to a more

Re: [openstack-dev] [QA][stable] Py3 integration jobs on stable

On Thu, Feb 15, 2018 at 05:28:29PM +, Andrea Frittoli wrote: > Dear all, > > since it's now RC1 time, C1 we're setting up CI jobs for stable branches > and periodic-stable jobs for stable/queens. > > In the past, we used to run the py27 based tempest-full integration job >

Re: [Openstack] diskimage-builder: prepare ubuntu 17.x images

On Thu, Feb 08, 2018 at 10:53:14PM +0200, Volodymyr Litovka wrote: > Hi colleagues, > > does anybody here know how to prepare Ubuntu Artful (17.10) image using > diskimage-builder? > > diskimage-builder use the following naming style for download - >

Re: [Openstack-operators] [Openstack] diskimage-builder: prepare ubuntu 17.x images

On Thu, Feb 08, 2018 at 10:53:14PM +0200, Volodymyr Litovka wrote: > Hi colleagues, > > does anybody here know how to prepare Ubuntu Artful (17.10) image using > diskimage-builder? > > diskimage-builder use the following naming style for download - >

Re: [openstack-dev] [Release-job-failures] release-post job for openstack/releases failed

On Fri, Feb 09, 2018 at 03:28:23AM +, z...@openstack.org wrote: > Build failed. > > - tag-releases > http://logs.openstack.org/bd/bd802368fe546a891b89f78fec89d3ea9964c155/release-post/tag-releases/ffc68e7/ > : TIMED_OUT in 32m 19s > - publish-static publish-static : SKIPPED Can we please

Re: [openstack-dev] [OpenStackClient][Security][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][masakari][neutron][senlin][shade][solum][swift][tacker][tricircle][vitrage][watcher][winstackers]

On Thu, Feb 08, 2018 at 08:18:37AM +1100, Tony Breeds wrote: > Okay It's safe to ignore then ;P We should probably remove it from > projects.txt if it really is empty I'll propose that. Oh my bad, ironic-python-agent-builder was included as it's included as an ironic project[1] NOT b

Re: [openstack-dev] [OpenStackClient][Security][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][masakari][neutron][senlin][shade][solum][swift][tacker][tricircle][vitrage][watcher][winstackers]

On Wed, Feb 07, 2018 at 06:11:33PM +0100, Dmitry Tantsur wrote: > Hi, > > On 02/07/2018 05:23 PM, Matthew Thode wrote: > > Hi all, > > > > it looks like some of your projects may need to cut a queens > > branch/release. Is there anything we can do to move it along? > > Review patches? Make the

Re: [openstack-dev] [ptg] Track around release cycle, consumption models and stable branches

On Wed, Feb 07, 2018 at 12:42:05PM +0100, Thierry Carrez wrote: > Would anyone be interested in such a discussion ? It would be scheduled > on the Tuesday. How much time would we need ? I was thinking we could > use only Tuesday afternoon. +1 Sounds good to me. I'll be there :) Yours Tony.

Re: [Openstack] tripleO Error No valid host was found

On Wed, Jan 31, 2018 at 06:10:11PM -0500, Satish Patel wrote: > I am playing with tripleO and getting following error when deploying > overcloud, I doing all this on VMware Workstation with fake_pxe > driver, I did enable drive in ironic too. > > What could be wrong here? There's lots that could

Re: [Openstack] [Devstack]Installation of Barbican failing in ubuntu 16.04 LTS

On Wed, Jan 31, 2018 at 09:21:34AM +0530, Himanshu Gupta wrote: > Hi Guys, > > I was trying to install the Devstack(Ocata branch) on the ubuntu 16.04 LTS > by performing pre-requisite steps and running stack.sh. But the > installation throws an error while installing Barbican. It throws the >

[openstack-dev] [nova][ironic] Tagging newton EOL

Hi All, When we tagged newton EOL in October there were in-flight reviews for nova and ironic that needed to land before we could EOL them. That work completed but I dropped the ball. So can we tag those last 2 repos? As in October a member of the infra team needs to do this *or* I can be

[openstack-dev] [tripleo] Mutli-arch image support

Hi All, As you're all aware we're trying to bring support to tripleo that enables multiple-architectures in the same tripleo managed/deployed overcloud. The first real difference comes to how we handle the ,now, multiple images required. To validated that my understanding of the x86_64 only

Re: [openstack-dev] [tripleo] Removing old baremetal commands from python-tripleoclient

On Fri, Dec 15, 2017 at 01:04:52PM +0100, Dmitry Tantsur wrote: > On 12/15/2017 04:49 AM, Tony Breeds wrote: > > Hi All, > > In review I01837a9daf6f119292b5a2ffc361506925423f11 I updated > > ValidateInstackEnv to handle the case when then instackenv.json file > >

Re: [openstack-dev] [all] propose to upgrade python kubernetes (the k8s python client) to 4.0.0

On Wed, Dec 13, 2017 at 10:16:29PM +1300, Lingxian Kong wrote: > hi, leyal, > > I suppose the upgrade is backward compatible, right? By, semantic versioning, defintion 1.y.z is NOT compatible with 4.y.z. That's what a major bump means. And in this case we're doing 3 major bumps. The only

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

On Fri, Dec 15, 2017 at 11:39:16AM -0700, Alex Schultz wrote: > Perhaps we can start reviewing the items and those with little to no > impact we can merge for the remainder of the cycle. I know > realistically everything has an impact so it'll be >0, but lets try > and keep it as close to 0 as

[openstack-dev] [tripleo] Removing old baremetal commands from python-tripleoclient

Hi All, In review I01837a9daf6f119292b5a2ffc361506925423f11 I updated ValidateInstackEnv to handle the case when then instackenv.json file needs to represent a node that deosn't require a pm_user for IMPI to work. It turns out that I foudn that code path with grep rather than the result of a

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

On Wed, Dec 13, 2017 at 03:01:41PM -0700, Alex Schultz wrote: > I assume since some of this work was sort of done earlier outside of > tripleo and does not affect the default installation path that most > folks will consume, it shouldn't be impacting to general testing or > increase regressions.

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

On Fri, Dec 08, 2017 at 04:34:09PM -0700, Alex Schultz wrote: > Hey folks, > > So I went through the list of blueprints and moved some that were > either not updated or appeared to have a bunch of patches not in a > mergable state. > > Please take some time to review the list of blueprints

Re: [openstack-dev] [Release-job-failures] Release of openstack/tripleo-ui failed

On Wed, Nov 22, 2017 at 03:07:33AM +, z...@openstack.org wrote: > Build failed. > > - publish-openstack-javascript-tarball > http://logs.openstack.org/e5/e5831f230bd29516dc202eb406270604f27e27f9/release/publish-openstack-javascript-tarball/9908482/ > : SUCCESS in 4m 58s > -

Re: [OpenStack-Infra] Zuul roadmap

On Thu, Nov 02, 2017 at 12:33:30AM +, Tristan Cacqueray wrote: > On November 1, 2017 11:56 pm, Tony Breeds wrote: > > On Wed, Nov 01, 2017 at 02:47:20PM -0700, James E. Blair wrote: > > > Hi, > > > > > > At the PTG we brainstormed a road map for Zuul once

Re: [OpenStack-Infra] Zuul roadmap

On Wed, Nov 01, 2017 at 02:47:20PM -0700, James E. Blair wrote: > Hi, > > At the PTG we brainstormed a road map for Zuul once we completed the > infra cutover. I think we're in a position now that we can get back to > thinking about this, so I've (slightly) cleaned it up and organized it > here.

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

On Mon, Oct 30, 2017 at 08:07:10PM -0400, Doug Hellmann wrote: > Excerpts from Richard.Pioso's message of 2017-10-30 23:11:31 +: > > 2. And would that be correctly handled? > > Good question. We should test the requirements update script to see. It does. I did a quick fictional test: This:

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

On Mon, Oct 30, 2017 at 05:51:49PM +0100, Dmitry Tantsur wrote: > Hi all, > > So far driver requirements [1] have been managed outside of > global-requirements. This was mostly necessary because some dependencies > were not on PyPI. This is no longer the case, and I'd like to consider > managing

Re: [openstack-dev] [nova][neutron] How do you use the instance IP filter?

On Thu, Oct 26, 2017 at 10:35:47PM -0500, Matt Riedemann wrote: > On 10/26/2017 9:54 PM, Tony Breeds wrote: > > Can you use RLIKE/REGEX? or is that too MySQL specific ? > > I thought about that, and my gut response is 'no' because even if it does > work for mysql, I'm assu

Re: [openstack-dev] [nova][neutron] How do you use the instance IP filter?

On Thu, Oct 26, 2017 at 09:23:50PM -0500, Matt Riedemann wrote: > Nova has had this long-standing known performance issue if you're filtering > a large number of instances by IP. The instance IPs are stored in a JSON > blob in the database so we don't do filtering in SQL. We pull the instances >

Re: [openstack-dev] [openstack-infra][stable][urgent][rally] Someone deleted Rally stable branch, we need to restore

On Thu, Oct 26, 2017 at 01:36:01PM -0700, Boris Pavlovic wrote: > Hi, > > Someone somehow deleted 0.9.* branches from GitHub repo > https://github.com/openstack/rally > A lot of end users are using these branches and are affected by this > change. > > Can someone help to restore them? So sorry

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

On Wed, Oct 25, 2017 at 10:06:46PM -0400, David Moreau Simard wrote: > Was it just me or did the "official" period for campaigning/questions was > awfully short ? > > The schedule [1] went: > ​TC Campaigning: (Start) Oct 11, 2017 23:59 UTC (End) Oct 14, 2017 23:45 > UTC​ The original was: -

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

On Wed, Oct 25, 2017 at 09:48:06PM +, Jeremy Stanley wrote: > On 2017-10-25 12:18:59 -0400 (-0400), Zane Bitter wrote: > [...] > > Can we maybe calculate the electorate size using the old method as well so > > that we can quantify how much of the dropoff (in theory it could be more > > than

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

On Wed, Oct 25, 2017 at 12:18:59PM -0400, Zane Bitter wrote: > On 20/10/17 20:20, Tony Breeds wrote: > > > > Hi All, > > With the election behind us it's somewhat traditional to look at > > some simp

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

On Wed, Oct 25, 2017 at 11:05:44AM +0100, Chris Dent wrote: > On Tue, 24 Oct 2017, Tony Breeds wrote: > > > On Mon, Oct 23, 2017 at 09:35:34AM +0100, Jean-Philippe Evrard wrote: > > > > > I agree, we should care about not repeating this Pike trend. It looks > >

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On Wed, Oct 25, 2017 at 10:24:59AM -0500, Matt Riedemann wrote: > On 10/24/2017 9:57 PM, Tony Breeds wrote: > > The timing of the next phase is uncertain right now but I'd like to take > > care of: > > > > - openstack/nova > > Just a status update, but the fin

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On Wed, Oct 25, 2017 at 01:11:53PM +0200, Dmitry Tantsur wrote: > The last ironic newton release was done, we're ready for EOL. Thanks that must've happened overnight. Yours Tony. signature.asc Description: PGP signature

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On Wed, Oct 25, 2017 at 10:11:01AM +0100, Jean-Philippe Evrard wrote: > On 25 October 2017 at 03:57, Tony Breeds <t...@bakeyournoodle.com> wrote: > > On Tue, Oct 24, 2017 at 05:11:15PM +1100, Tony Breeds wrote: > >> On Fri, Oct 06, 2017 at 10:15:56AM +1100, Tony Breeds wrot

Re: [openstack-dev] [all][charms][fuel][Packaging-Deb] Remove old numeric branches

On Wed, Sep 20, 2017 at 01:52:11PM -0400, Tony Breeds wrote: > Hello all, > Now we have cleaned up some of the older series based branches I've > taken a look at some of the numeric based branches. > > The projects in $subject are particularly impacted. I've made my best &

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On Tue, Oct 24, 2017 at 05:11:15PM +1100, Tony Breeds wrote: > On Fri, Oct 06, 2017 at 10:15:56AM +1100, Tony Breeds wrote: > > On Wed, Oct 04, 2017 at 02:51:06PM +1100, Tony Breeds wrote: > > > I'll prep the list of repos that will be tagged EOL real soon no

Re: [openstack-dev] [os-vif] [nova] Changes to os-vif cores

On Tue, Oct 24, 2017 at 03:32:15PM +0100, Stephen Finucane wrote: > Hey, > > I'm not actually sure what the protocol is for adding/removing cores to a > library project without a PTL, so I'm just going to put this out there: I'd > like to propose the following changes to the os-vif core team.

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On Fri, Oct 06, 2017 at 10:15:56AM +1100, Tony Breeds wrote: > On Wed, Oct 04, 2017 at 02:51:06PM +1100, Tony Breeds wrote: > > I'll prep the list of repos that will be tagged EOL real soon now for > > review. > > As promised here's the list. The fomat is new, It's grouped

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

On Mon, Oct 23, 2017 at 09:35:34AM +0100, Jean-Philippe Evrard wrote: > I agree, we should care about not repeating this Pike trend. It looks > like Queens is better in terms of turnout (see the amazing positive > delta!). However, I can't help but noticing that the trend for > turnouts is slowly

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

Hi All, With the election behind us it's somewhat traditional to look at some simple stats from the elections: +--+---+---+---+ | Election | Electorate (delta %) | Voted (delta %) | Turnout % (delta %) |

Re: [openstack-dev] [all][elections] TC nomination period is now over

On Wed, Oct 11, 2017 at 12:18:30AM +, Kendall Nelson wrote: > Hello!TC Nomination is now over. The official candidate list is available > on the election website[0].We now enter the campaigning period where > candidates and electorate may debate their statements.The election will > start this

Re: [openstack-dev] [all] Update on Zuul v3 Migration - and what to do about issues

On Thu, Oct 05, 2017 at 09:06:24PM +0900, Takashi Yamamoto wrote: > i was told this is a fix. https://review.openstack.org/#/c/508898/ Yup the transition will be complete when https://review.openstack.org/#/c/509855/ merges. At that point we'll be using all the zuulv3 goodness :) Thanks again

Re: [openstack-dev] [all][elections] Candidate proposals for TC (Technical Committee) positions are now open

On Fri, Oct 06, 2017 at 12:30:51AM +0900, Emmet Hikory wrote: > While all of the prose above is correct, the table does not reflect > the extended dates (although we'd be delighted to have nominations well in > advance of the dates listed). The updated delayed-two-days dates are: > > Events

Re: [openstack-dev] [DIB] DIB Meetings

On Thu, Oct 05, 2017 at 05:19:07PM +0200, Andreas Scheuring wrote: > Hi, > > seems like there is some confusing information about the DIB meetings in the > wiki [1]. The meeting is alternating between 15:00 and 20:00 UTC. But > whenever the Text says 15:00 UTC, the link points to a 20:00 UTC

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On Wed, Oct 04, 2017 at 02:51:06PM +1100, Tony Breeds wrote: > I'll prep the list of repos that will be tagged EOL real soon now for > review. As promised here's the list. The fomat is new, It's grouped by project team so it should be easy for teams to find repos they care about. The onl

Re: [openstack-dev] [stable] Preping for the stable/newton EOL

On Thu, Oct 05, 2017 at 09:00:00AM -0600, Alex Schultz wrote: > On Tue, Oct 3, 2017 at 9:51 PM, Tony Breeds <t...@bakeyournoodle.com> wrote: > Would it be possible to delay the Newton EOL for the TripleO projects > for ~1month? We still have some patches outstanding and would

Re: [openstack-dev] [all][elections] Candidate proposals for TC (Technical Committee) positions are now open

On Sun, Oct 01, 2017 at 11:26:33PM +, Kendall Nelson wrote: > Hello Again, > > A few corrections from the kickoff email: > > Candidates for the Technical Committee Positions: Any Foundation individual > member can propose their candidacy for an available, directly-elected TC > seat. (except

[openstack-dev] [stable] Preping for the stable/newton EOL

Hi All, This is a quick update on the process for tagging stable/newton as EOL: The published[1][2] timeline is: Sep 29 : Final newton library releases Oct 09 : stable/newton branches enter Phase III Oct 11 : stable/newton branches get tagged EOL Given that those key dates were a little

Re: [openstack-dev] [tripleo] Newton End-Of-Life (EOL) next month (reminder #1)

On Wed, Sep 27, 2017 at 08:14:19PM -0700, Emilien Macchi wrote: > On Wed, Sep 27, 2017 at 5:37 PM, Tony Breeds <t...@bakeyournoodle.com> wrote: > > On Wed, Sep 27, 2017 at 10:39:13AM -0600, Alex Schultz wrote: > > > >> One idea would be to allow trailin

Re: [openstack-dev] [tripleo] Newton End-Of-Life (EOL) next month (reminder #1)

On Wed, Sep 27, 2017 at 10:17:16PM -0500, Ben Nemec wrote: > > > On 09/27/2017 08:13 PM, Tony Breeds wrote: > > On Wed, Sep 27, 2017 at 03:35:43PM -0500, Ben Nemec wrote: > > > It's a little weird because essentially we want to provide a higher level > > > of

Re: [openstack-dev] [tripleo] Newton End-Of-Life (EOL) next month (reminder #1)

On Wed, Sep 27, 2017 at 03:35:43PM -0500, Ben Nemec wrote: > It's a little weird because essentially we want to provide a higher level of > support for stable branches than most of OpenStack. My understanding is > that a lot of the current stable branch policy came out of the fact that > there

Re: [openstack-dev] [tripleo] Newton End-Of-Life (EOL) next month (reminder #1)

On Wed, Sep 27, 2017 at 10:39:13AM -0600, Alex Schultz wrote: > One idea would be to allow trailing projects additional trailing on > the phases as well. Honestly 2 weeks for trailing for just GA is hard > enough. Let alone the fact that the actual end-users are 18+ months > behind. For some

Re: [openstack-dev] [tripleo] Newton End-Of-Life (EOL) next month (reminder #1)

On Tue, Sep 26, 2017 at 10:31:59PM -0700, Emilien Macchi wrote: > On Tue, Sep 26, 2017 at 10:17 PM, Tony Breeds <t...@bakeyournoodle.com> wrote: > > With that in mind I'd suggest that your review isn't appropriate for > > If we have to give up backports that help customer

Re: [openstack-dev] [tripleo] Newton End-Of-Life (EOL) next month (reminder #1)

On Wed, Sep 27, 2017 at 06:55:13AM +0200, Giulio Fidente wrote: > On 09/26/2017 06:58 PM, Emilien Macchi wrote: > > Newton is officially EOL next month: > > https://releases.openstack.org/index.html#release-series > > > > As an action from our weekly meeting, we decided to accelerate the > >

Re: [openstack-dev] [tripleo] Newton End-Of-Life (EOL) next month (reminder #1)

On Tue, Sep 26, 2017 at 10:58:46AM -0600, Emilien Macchi wrote: > Newton is officially EOL next month: > https://releases.openstack.org/index.html#release-series > > As an action from our weekly meeting, we decided to accelerate the > reviews for stable/newton before it's too late. > This email

Re: [openstack-dev] Disk Image Builder for redhat 7.4

On Tue, Sep 26, 2017 at 10:19:45PM +0530, Amit Singla wrote: > Hi, > > Could you tell me how I can create qcow2 image for rhel 7.4 by disk image > builder and I want also to install oracle 12.2 on that image with DIB. Is > it possible? For the RHEL 7.4 side of things there is a rhel7 dib target,

Re: [openstack-dev] [devstack] etcd v3.2.0?

On Fri, Jun 16, 2017 at 12:06:47PM +1000, Tony Breeds wrote: > Hi All, > I just push a review [1] to bump the minimum etcd version to > 3.2.0 which works on intel and ppc64le. I know we're pretty late in the > cycle to be making changes like this but releasing pike with a depend

Re: [openstack-dev] [stable][release] Last release date vs End of Life date

On Thu, Jun 29, 2017 at 01:34:05PM +0800, ChangBo Guo wrote: > Thanks tony for raising up this, better document this in some place :-) For the record this was just added to the queens schedule [1]. The deadline is this week but in reality early nest week would probably also be accepted. Yours

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Thu, Sep 21, 2017 at 12:13:23PM -0400, Doug Hellmann wrote: > Excerpts from Tony Breeds's message of 2017-09-21 08:36:39 -0400: > > On Wed, Sep 20, 2017 at 06:08:22PM -0400, Doug Hellmann wrote: > > > > > I like the idea. I'm not sure why, if the constraints file is only used > > > for the

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 06:08:22PM -0400, Doug Hellmann wrote: > I like the idea. I'm not sure why, if the constraints file is only used > for the dependency installation step, we still need tox_install.sh? Right now that isn't true, when we get something like my idea implemented we'd still need

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 04:51:21PM -0400, Doug Hellmann wrote: > Excerpts from Jeremy Stanley's message of 2017-09-20 18:59:50 +: > > On 2017-09-20 14:46:32 -0400 (-0400), Tony Breeds wrote: > > [...] > > > I'd like to find a solution that doesn

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 06:59:50PM +, Jeremy Stanley wrote: > On 2017-09-20 14:46:32 -0400 (-0400), Tony Breeds wrote: > [...] > > I'd like to find a solution that doesn't need a tox_install.sh > [...] > > This wart came up when discussing Zuul v3 job translations...

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 02:24:32PM -0400, Doug Hellmann wrote: > That solves the problem of having the constraints file disappear after > the EOL, but it doesn't really solve the problem of having to update the > branches every time we open one. Having tox_install.sh figure out the > URL from the

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 02:09:15PM -0400, Tony Breeds wrote: > On Wed, Sep 20, 2017 at 01:43:51PM -0400, Tony Breeds wrote: > > > The solution I thought we decide on at the PTG is: > > * Add a post job to all branches that publish a constraints/$series.txt > >to $serv

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 01:43:51PM -0400, Tony Breeds wrote: > The solution I thought we decide on at the PTG is: > * Add a post job to all branches that publish a constraints/$series.txt >to $server (I don't mind if it's releases.o.o or tarballs.o.o). Actually we might be bet

[openstack-dev] [all][charms][fuel][Packaging-Deb] Remove old numeric branches

Hello all, Now we have cleaned up some of the older series based branches I've taken a look at some of the numeric based branches. The projects in $subject are particularly impacted. I've made my best guess at which branches are current, but I'd really appreciate guidance on the life span of

Re: [openstack-dev] [requirements][stable] EOL tags and upper-constraints.txt in tox.ini

On Wed, Sep 20, 2017 at 01:08:45PM -0400, Doug Hellmann wrote: > Excerpts from Jeremy Stanley's message of 2017-09-20 13:36:38 +: > > On 2017-09-20 08:41:14 -0400 (-0400), Doug Hellmann wrote: > > [...] > > > Is there any reason not to use the published files for all regular > > > builds,

<    1   2   3   4   5   6   7   8   >