Re: [openstack-dev] [nova][cinder] Nova is now using the Cinder volume attachments API - multiattach comes next

*happy dance* A huge thanks to Ildiko Vansca (couldn't have made this happen without your leadership), Matt Riedemann, John Garbutt and John Griffith for making this happen.  You guys have worked so hard on this and it is greatly appreciated! Jay On 12/9/2017 1:15 PM, Matt Riedemann

Re: [openstack-dev] [nova][cinder] Nova is now using the Cinder volume attachments API - multiattach comes next

Great work and congratulations to everyone involved! On Sat, Dec 9, 2017 at 1:15 PM, Matt Riedemann wrote: > I just wanted to take a minute to recognize that the patch [1] to make > Nova use the new-style Cinder volume attach flow has merged. > > As one can tell from the

[openstack-dev] [nova][cinder] Nova is now using the Cinder volume attachments API - multiattach comes next

I just wanted to take a minute to recognize that the patch [1] to make Nova use the new-style Cinder volume attach flow has merged. As one can tell from the patch set count alone, this has been in the works for a long time now. We were talking about volume multi-attach support back in Mitaka

Re: [openstack-dev] [tripleo] [upgrade] CI status and Current effort.

On Fri, Dec 8, 2017 at 10:11 PM, Emilien Macchi wrote: > On Fri, Dec 8, 2017 at 11:42 AM, Emilien Macchi > wrote: > > On Fri, Dec 8, 2017 at 5:39 AM, Wesley Hayutin > wrote: > > [...] > >> Sofer, can you estimate when the

Re: [openstack-dev] [Release-job-failures][congress] Pre-release of openstack/congress failed

Excerpts from Eric K's message of 2017-12-09 03:03:10 -0800: > Submitted this after merging the fix: > https://review.openstack.org/#/c/526834/ > > Is that the correct step? Thanks again! The 0b2 tag was applied successfully, and our tools don't make it easy to move the tag after the fact (there

Re: [openstack-dev] [keystone] keystone client service_catalog is None

Hi, Have a look at how openstackclient does this. Read this code: https://github.com/openstack/python-openstackclient/blob/master/openstackclient/identity/v3/catalog.py#L43 and then this code: https://github.com/openstack/osc-lib/blob/master/osc_lib/clientmanager.py#L239 On 09.12.2017 04:15,

[openstack-dev] [evoque] Retiring evoque projects

Evoque cores, The last change merged to the evoque projects was January 2016, I propose to retire the projects to avoid people commiting to them and infra updating their jobs needlessly. See https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project on how to retire them. If

[openstack-dev] [cerberus] Retire openstack/*cerberus*

Anthony, Christophe, Gauvin, The last merge to one of the cerberus repositories was December 2015, I propose to retire the repositories to avoid people submitting changes to them. See https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project on how to retire a project. If

[openstack-dev] [astara] Retire openstack/*astara*

Ryan, Mark, nothing has merged to the OpenStack astara repos since over a year (last merge was October 2016). I suggest to retire the repos completely as explained at https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project to avoid people to submit patches to it. Could you

[openstack-dev] [all][infra] Playbooks need extension, otherwise job will fail

Playbooks in Zuul v3 config files now need the file extension like ".yaml". There are still a few ancient changes for zuul.yaml that do not have those - and some repos that did not take in Jim's update. If your jobs are failing with errors that playbooks cannot be found, add the file

Re: [openstack-dev] [all] Changes to releasenotes and docs build jobs

On 11/22/2017 07:39 AM, Monty Taylor wrote: Hey everybody! Following recent changes [0] in the PTI [1][2] we're rolling out some changes to the build-openstack-releasenotes and build-openstack-sphinx-docs jobs. If you see patches with the topic 'updated-pti' - they are in service of this.

Re: [Openstack] Hello all Magnum project info

There was an update on Magnum at the OpenStack Sydney summit (https://www.openstack.org/videos/sydney-2017/magnum-project-update). We’re using it at CERN based off the RDO distribution with over 100 different clusters. We’re running Kubernetes 1.8. Documentation for the CERN user is at

[openstack-dev] Introduction

Hi guys, My name is Angeh Courage, computer engineering student at the University of Buea currently in my forth year of studies. Was a GSoC intern at Mifos Initiavie for 2016/2017 and I am good with Python, Java - Spring, web(HTML, CSS, JS - React, Angular...) I am very interested in cloud

Re: [openstack-dev] [Release-job-failures][congress] Pre-release of openstack/congress failed

Submitted this after merging the fix: https://review.openstack.org/#/c/526834/ Is that the correct step? Thanks again! On 12/8/17, 2:10 PM, "Sean McGinnis" wrote: >On Fri, Dec 08, 2017 at 04:06:15PM -0600, Doug Hellmann wrote: >> Excerpts from zuul's message of

Re: [openstack-dev] [horizon][heat] heat-dashboard is ready for Horizon team's review

Hi all, I've confirmed a couple of things below. - heat-dashboard is released in queens-2 Thx! Rico :) you can see the release tag 1.0.0 in http://git.openstack.org/cgit/openstack/heat-dashboard/ - Dropped heat related code from horizon repo. Thx! Akihiro :)

Re: [openstack-dev] [E] [openstack-ansible] Cannot connect to proxy server from infra1-repo-container

On 7 December 2017 at 14:02, Gordon, Kent S wrote: > On Thu, Dec 7, 2017 at 3:24 AM, Goutham Pratapa > wrote: >> Hi, >> >> We are trying test environment deployment with OpenStack-ansible pike >> release. After executing