Re: [openstack-dev] [Openstack-sigs] [PTL][SIG][PTG]Team Photos

On Thu, Feb 8, 2018 at 6:21 PM Kendall Nelson wrote: > This link might work better for everyone: > > https://docs.google.com/spreadsheets/d/1J2MRdVQzSyakz9HgTHfwYPe49PaoTypX66eNURsopQY/edit?usp=sharing > +1 thanks this is editable > > -Kendall (diablo_rojo) > > > On Wed,

[openstack-dev] [charms] Propose Dmitrii Shcherbakov for OpenStack Charmers team.

Hi I'd like to propose Dmitrii Shcherbakov to join the launchpad "OpenStack Charmers" team. He's done some tremendous work on existing the charms, has developed some new ones, and has really developed his understanding of configuring and implementing OpenStack. I think he'd make a great

Re: [openstack-dev] [PTL][SIG][PTG]Team Photos

Hi Kendall, Can you add Neutron on Thursday at 2pm. If that is not available, then anytime Wednesday or Thursday. I am the contact: mig...@mlavalle.com Thanks On Wed, Feb 7, 2018 at 11:15 PM, Kendall Nelson wrote: > Hello PTLs and SIG Chairs! > > So here's the deal, we

Re: [openstack-dev] [all][Kingbird]Multi-Region Orchestrator

On 07/02/18 11:20, Chris Friesen wrote: One use-case I've seen for this sort of thing is someone that has multiple geographically-separate clouds, and maybe they want to run the same heat stack in all of them. Something like "create a keypair in each of the clouds with the same public key

Re: [openstack-dev] [PTL][SIG][PTG]Team Photos

Done! On Thu, Feb 8, 2018 at 10:13 AM Matthew Thode wrote: > On 18-02-08 10:00:58, Michael Johnson wrote: > > Hi Kendall, > > > > Can you put Octavia down for 2:10 on Thursday after neutron? > > Thanks, > > Michael > > > > > > On Wed, Feb 7, 2018 at 9:15 PM, Kendall

[openstack-dev] [blazar] blazar 1.0.0.0rc1 (queens)

Hello everyone, A new release candidate for blazar for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/blazar/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

Re: [openstack-dev] [PTL][SIG][PTG]Team Photos

Done! On Thu, 8 Feb 2018, 8:56 am Miguel Lavalle, wrote: > Hi Kendall, > > Can you add Neutron on Thursday at 2pm. If that is not available, then > anytime Wednesday or Thursday. I am the contact: mig...@mlavalle.com > > Thanks > > On Wed, Feb 7, 2018 at 11:15 PM, Kendall

Re: [openstack-dev] [PTL][SIG][PTG]Team Photos

On 18-02-08 10:00:58, Michael Johnson wrote: > Hi Kendall, > > Can you put Octavia down for 2:10 on Thursday after neutron? > Thanks, > Michael > > > On Wed, Feb 7, 2018 at 9:15 PM, Kendall Nelson wrote: > > Hello PTLs and SIG Chairs! > > > > So here's the deal, we have

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, Today's meeting was chock-full of interesting discussion. Let me recap it for you. We began with a follow-up conversation about the use of "action" URLs (as opposed to resource-based URLs). The origin of this discussion came from an email posted to the dev list

Re: [openstack-dev] [PTL][SIG][PTG]Team Photos

Hi Kendall, Can you put Octavia down for 2:10 on Thursday after neutron? Thanks, Michael On Wed, Feb 7, 2018 at 9:15 PM, Kendall Nelson wrote: > Hello PTLs and SIG Chairs! > > So here's the deal, we have 50 spots that are first come, first served. We > have slots

Re: [openstack-dev] [PTL][SIG][PTG]Team Photos

Hello Kendall, QA Team Tue at 11:00 please :) Andrea On Thu, Feb 8, 2018 at 5:37 PM Kendall Nelson wrote: > Done! > > On Thu, 8 Feb 2018, 8:56 am Miguel Lavalle, wrote: > >> Hi Kendall, >> >> Can you add Neutron on Thursday at 2pm. If that is not

[openstack-dev] [magnum][release] release-post job for openstack/releases failed

The release job for magnum failed, but luckily it was after tagging and branching the release. It was not able to get to the point of uploading a tarball to http://tarballs.openstack.org/magnum/ though. The problem the job encountered is that magnum is now configured to publish to Pypi. The

[openstack-dev] [magnum] Release of openstack/magnum failed

Apologies, I forwarded the wrong one just a bit ago. See below for the actual links to the magnum release job failures if you wish to take a look. Sean - Forwarded message from z...@openstack.org - Date: Thu, 08 Feb 2018 18:06:54 + From: z...@openstack.org To:

[openstack-dev] [PTG] Last Chance for PTG Dublin Tickets

Hi everyone, Yesterday we sold out the upcoming Dublin PTG, and have since received many requests for more tickets. We have been working with the venue to accommodate extra capacity, but every additional attendee incrementally increases our costs $600. We understand the importance of this

[openstack-dev] nova_powervm 6.0.0.0rc1 (queens)

Hello everyone, A new release candidate for nova_powervm for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/nova-powervm/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

[openstack-dev] [neutron] [networking-ovn] Rocky PTG

I have created an etherpad for networking-ovn, if https://etherpad.openstack.org/p/networking-ovn-ptg-rocky with some topics I thought are relevant. But please feel free to add anything you believe it could be interesting and fill attendance so it's easier to sync & meet. :)

Re: [openstack-dev] [ironic][neutron] bare metal on vxlan network

Hi Moshe, I'm not aware of any mechanism drivers that actually create the VTEP (that will be a manual step,) but there are drivers that support Hierarchical Port Binding [1]. The networking-arista mechanism driver [2] is one such driver, but there are others. Such drivers will configure a VLAN to

[openstack-dev] [cinder] cinder 12.0.0.0rc1 (queens)

Hello everyone, A new release candidate for cinder for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/cinder/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

Re: [openstack-dev] [PTL][SIG][PTG]Team Photos

This link might work better for everyone: https://docs.google.com/spreadsheets/d/1J2MRdVQzSyakz9HgTHfwYPe49PaoTypX66eNURsopQY/edit?usp=sharing -Kendall (diablo_rojo) On Wed, Feb 7, 2018 at 9:15 PM Kendall Nelson wrote: > Hello PTLs and SIG Chairs! > > So here's the deal,

[openstack-dev] networking-powervm 6.0.0.0rc1 (queens)

Hello everyone, A new release candidate for networking-powervm for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/networking-powervm/ Unless release-critical issues are found that warrant a release candidate respin, this

Re: [openstack-dev] [charms] Propose Dmitrii Shcherbakov for OpenStack Charmers team.

Dmitrii easily gets a +1 from me! On 02/08/2018 09:42 AM, Alex Kavanagh wrote: > Hi > > I'd like to propose Dmitrii Shcherbakov to join the launchpad > "OpenStack Charmers" team.  He's done some tremendous work on existing > the charms, has developed some new ones, and has really developed his >

Re: [openstack-dev] [PTL][SIG][PTG]Team Photos

Done! On Thu, Feb 8, 2018 at 9:39 AM Andrea Frittoli wrote: > Hello Kendall, > > QA Team Tue at 11:00 please :) > > Andrea > > On Thu, Feb 8, 2018 at 5:37 PM Kendall Nelson > wrote: > >> Done! >> >> On Thu, 8 Feb 2018, 8:56 am Miguel Lavalle,

Re: [openstack-dev] [charms] Propose Dmitrii Shcherbakov for OpenStack Charmers team.

+1 from me On Thu, 8 Feb 2018 at 18:23 Billy Olsen wrote: > Dmitrii easily gets a +1 from me! > > On 02/08/2018 09:42 AM, Alex Kavanagh wrote: > > Hi > > > > I'd like to propose Dmitrii Shcherbakov to join the launchpad > > "OpenStack Charmers" team. He's done some

[openstack-dev] [designate] designate-dashboard 6.0.0.0rc1 (queens)

Hello everyone, A new release candidate for designate-dashboard for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/designate-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [trove] trove-dashboard 10.0.0.0rc1 (queens)

Hello everyone, A new release candidate for trove-dashboard for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/trove-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [freezer] freezer-api 6.0.0.0rc1 (queens)

Hello everyone, A new release candidate for freezer-api for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer-api/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will

[openstack-dev] [freezer] freezer-dr 6.0.0.0rc1 (queens)

Hello everyone, A new release candidate for freezer-dr for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer-dr/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

Re: [openstack-dev] [all][Kingbird][Heat][Glance]Multi-Region Orchestrator

On 07/02/18 12:24, Goutham Pratapa wrote: >Yes as you said it can be interpreted as a tool that can orchestrate multiple-regions. Actually from your additional information I'm now getting the impression that you are, in fact, positioning this as a partial competitor to Heat.

[openstack-dev] [designate] designate 6.0.0.0rc1 (queens)

Hello everyone, A new release candidate for designate for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/designate/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [OpenStack Foundation] CFP Deadline Today - OpenStack Summit Vancouver

Hi everyone, The Vancouver Summit CFP closes *TODAY at 11:59pm Pacific Time (February 9 at 6:59am UTC).* Get your talks in for: • Container infrastructure • Edge computing • CI/CD • HPC/GPU/AI • Open source community • OpenStack private,

[openstack-dev] [congress] congress 7.0.0.0rc1 (queens)

Hello everyone, A new release candidate for congress for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/congress/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [searchlight] searchlight 4.0.0.0rc1 (queens)

Hello everyone, A new release candidate for searchlight for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/searchlight/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will

[openstack-dev] [searchlight] searchlight 4.0.0.0rc1 (queens)

Hello everyone, A new release candidate for searchlight for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/searchlight/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will

[openstack-dev] [congress] congress-dashboard 2.0.0.0rc1 (queens)

Hello everyone, A new release candidate for congress-dashboard for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/congress-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [requirements] more help needed

The following do not have a stable/queens branch and could cause requirements to remain frozen until they do. If I get no response by tomorrow afternoon my time (about 24 horus from the time this email was SENT) I may still move to unfreeze requirements. [tricircle] tricircle [heat] heat-agents

Re: [openstack-dev] [requirements][tricircle][heat] more help needed

On 18-02-08 15:20:54, Matthew Thode wrote: > The following do not have a stable/queens branch and could cause > requirements to remain frozen until they do. If I get no response by > tomorrow afternoon my time (about 24 horus from the time this email was > SENT) I may still move to unfreeze

[openstack-dev] [glance] glance 16.0.0.0rc1 (queens)

Hello everyone, A new release candidate for glance for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/glance/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [requirements][kolla][openstack-ansible][puppet][tripleo] requirements unfreeze and you, how you should handle it

As the title states, cycle trailing projects will need to change their requirements update behavior until they create stable/queens branches. When requirements unfreezes we will be doing rocky work, meaning that requirements updates to your projects (our master to your master) will be for rocky.

[openstack-dev] [freezer] freezer-web-ui 6.0.0.0rc1 (queens)

Hello everyone, A new release candidate for freezer-web-ui for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer-web-ui/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

[openstack-dev] [freezer] freezer 6.0.0.0rc1 (queens)

Hello everyone, A new release candidate for freezer for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [trove] trove 9.0.0.0rc1 (queens)

Hello everyone, A new release candidate for trove for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/trove/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

Re: [openstack-dev] [tripleo] FFE - Feuture Freeze Exception request for Routed Spine and Leaf Deployment

Hi, Thanks for all the reviews. Just one more + CI change and docs left now. **HEADs UP**: I think we might have broken ovb jobs until 537830 is landed once packages are promoted. This is due to a change in Ironic[1] that I realized yesterday is not yet in

[openstack-dev] [reno] an alternative approach to known issues

Hi, sometimes it happens, while reviewing a patch, to find an issue that is not quite a bug, because it doesn't limit functionality, but may represent a problem in some corner case, or with some possible future modification in some component involved in the patch; it may best be described as a

Re: [openstack-dev] [reno][tripleo] an alternative approach to known issues

So TripleO has a tech debt policy: https://specs.openstack.org/openstack/tripleo-specs/specs/policy/tech-debt-tracking.html (and I'm tagging tripleo on this thread for visibility). It essentially comes down to: open a bug, tag it "tech-debt", and reference it in the code near the tech debt.

[openstack-dev] [searchlight] searchlight-ui 4.0.0.0rc2 (queens)

Hello everyone, A new release candidate for searchlight-ui for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/searchlight-ui/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

[openstack-dev] [manila] manila 6.0.0.0rc1 (queens)

Hello everyone, A new release candidate for manila for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/manila/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

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] [tripleo] Unbranched repositories and testing

On Tue, Oct 10, 2017 at 2:24 PM, Emilien Macchi wrote: > On Fri, Oct 6, 2017 at 5:09 AM, Jiří Stránský wrote: >> On 5.10.2017 22:40, Alex Schultz wrote: >>> >>> Hey folks, >>> >>> So I wandered across the policy spec[0] for how we should be handling >>>

Re: [openstack-dev] [requirements][kolla][openstack-ansible][puppet][tripleo] requirements unfreeze and you, how you should handle it

On Thu, Feb 8, 2018 at 2:29 PM, Matthew Thode wrote: > As the title states, cycle trailing projects will need to change their > requirements update behavior until they create stable/queens branches. > > When requirements unfreezes we will be doing rocky work, meaning

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

On 2018-02-08 18:29:18 -0500 (-0500), Doug Hellmann wrote: [...] > Another alternative is to change the job configuration for magnum to use > release-openstack-server instead of publish-to-pypi, at least for the > near term. That would give the magnum team more time to make the changes > need to

[openstack-dev] [glance] priorities for the coming week (9 Feb - 15 Feb)

Congratulations to Erno for his election as the Rocky PTL! Erno is taking over PTG planning, so don't forget to add ideas to the planning etherpad: https://etherpad.openstack.org/p/glance-rocky-ptg-planning The first Release Candidate for the Queens edition of Glance was released today and the

[openstack-dev] [release][requirements][monasca] FFE request for monasca-common

Hello, I would like to request FFE for monasca-common to be bumped in upper constraints. The version has been bumped together with the rest of Monasca components [1]. Monasca-common is used only in Monasca projects [2]. Best greetings Witek [1] https://review.openstack.org/541767 [2]

[openstack-dev] [monasca] Feature freeze lifted

Hello, Yesterday I have created stable/queens branches for our repos. It will be used to create the final Queens release. We can continue the work on new features on master. Cheers Witek __ OpenStack Development Mailing

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

Borne Mace wrote: > I would be interested in taking part in this discussion as well, OK I think we have enough people to warrant a spot on the pre-scheduled tracks (Tuesday afternoon). I'll make it happen. Cheers, -- Thierry Carrez (ttx)

Re: [openstack-dev] [heat][rally] What should we do with legacy-rally-dsvm-fakevirt-heat

Thx Andrey, looking forward to new rally job At meanwhile, seems current job is broken [1] and we're expecting for a new job to replace. We will remove the old legacy one (see patch [2]) for now if that won't break rally (in any way). I'm changing only config for heat (under

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 02/07/2018 10:31 PM, Tony Breeds wrote: 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

Re: [openstack-dev] [ptg] Lightning talks

Mike Perez wrote: > [...] > Appropriate 5 minute talk examples: > * Neat features in libraries like oslo that we should consider adopting in our > community wide goals. > * Features and tricks in your favorite editor that makes doing work easier. > * Infra tools that maybe not a lot of people

Re: [openstack-dev] [heat][rally] What should we do with legacy-rally-dsvm-fakevirt-heat

Hi Rico 2018-02-08 11:38 GMT+02:00 Rico Lin : > Thx Andrey, looking forward to new rally job > > At meanwhile, seems current job is broken [1] > Based on the error, the fix requires +2;-2 change to

Re: [openstack-dev] [glance][cinder]Question about cinder as glance store

Hello Gorka, Thank you for replying! I'll try to run glance-api and cinder-volume on the same node according to your information. On 2018/02/07 19:27, Gorka Eguileor wrote: On 07/02, Rikimaru Honjo wrote: Hello, I'm planning to use cinder as glance store. And, I'll setup cinder to connect

Re: [openstack-dev] [Senlin] [PTL] PTL nomination for Senlin

+1 --- Lee Yi / Fiberhome Corp. liyi8...@gmail.com > On 3 Feb 2018, at 12:38, YUAN RUIJIE wrote: > > +1 > Thanks for taking up responsibility to lead the team!!! > > 2018-01-31 15:58 GMT+08:00

[openstack-dev] [murano] murano 5.0.0.0rc1 (queens)

Hello everyone, A new release candidate for murano for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/murano/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [nova] nova 17.0.0.0rc1 (queens)

Hello everyone, A new release candidate for nova for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/nova/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

Re: [openstack-dev] [ironic] Nominating Hironori Shiina for ironic-core

+1 On Wed, Feb 7, 2018 at 11:53 AM, John Villalovos wrote: > +1 > > On Mon, Feb 5, 2018 at 10:12 AM, Julia Kreger > wrote: > >> I would like to nominate Hironori Shiina to ironic-core. He has been >> working in the ironic community for

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

On 02/09/2018 02:35 PM, Tony Breeds wrote: >> - 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-run these jobs. Done with [1] -i

[openstack-dev] [horizon] horizon 13.0.0.0rc1 (queens)

Hello everyone, A new release candidate for horizon for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/horizon/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

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

Excerpts from Sean McGinnis's message of 2018-02-08 13:00:52 -0600: > The release job for magnum failed, but luckily it was after tagging and > branching the release. It was not able to get to the point of uploading a > tarball to http://tarballs.openstack.org/magnum/ though. > > The problem the

Re: [openstack-dev] [reno][tripleo] an alternative approach to known issues

On 08 Feb, Ben Nemec wrote: > So TripleO has a tech debt policy: > https://specs.openstack.org/openstack/tripleo-specs/specs/policy/tech-debt-tracking.html > (and I'm tagging tripleo on this thread for visibility). I didn't know about this policy. I've been circling around tech debts for more

[openstack-dev] [horizon] PTG Planning Etherpad

Hi team, In case if you missed it, it's a friendly reminder that we've got etherpad [1] with Rocky PTG topics proposals. If you're going to attend it or want to get some topic discussed, please add your name and topic to the list [1]. Hope to see you all in Dublin. [1]

[openstack-dev] [senlin] senlin 5.0.0.0rc1 (queens)

Hello everyone, A new release candidate for senlin for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/senlin/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

Re: [openstack-dev] [glance][cinder]Question about cinder as glance store

On 07/02, Erlon Cruz wrote: > That will depend on the Cinder/OS-brick iscsiadm versions right? Can you > tell what are the versions from where the problem was fixed? > > Erlon > Hi, Like you said it depends on your Cinder and OS-Brick versions, and the open-iscsi package will be different

Re: [openstack-dev] [release][requirements][monasca] FFE request for monasca-common

2018-02-08 11:05 GMT+01:00 Bedyk, Witold : > I would like to request FFE for monasca-common to be bumped in upper > constraints. The version has been bumped together with the rest of Monasca > components [1]. Monasca-common is used only in Monasca projects [2].

[openstack-dev] [release] Release countdown for week R-2, February 10 - 16

The end is near! Before I continue with the countdown info for next week, just a reminder that today, 8th February, is the RC1 milestone. Please make sure your project submits a release patch for an RC (cycle-with-milestones) or final (cycle-with-intermediary) release with a request to create a

Re: [openstack-dev] [requirements][release] FFE for constraints update for python-tackerclient bug-fix release

Matthew Thode wrote: > It should have time to get in for the freeze, the question I have is > 'What in openstack is broken if we update upper-contraints after the > freeze instead of before?' > A follow up question is 'does this need a global-requirements.txt bump?' In other words, will the new

Re: [openstack-dev] [neutron] cycle highlights for sub-projects

On 2 February 2018 at 13:33, Armando M. wrote: > Hi neutrinos, > > RC1 is fast approaching and this time we can add highlights to the release > files [1]. If I can ask you anyone interested in contributing to the > highlights: please review [2]. > > Miguel and I will make sure

[openstack-dev] [octavia] octavia-dashboard 1.0.0.0rc1 (queens)

Hello everyone, A new release candidate for octavia-dashboard for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/octavia-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [octavia] neutron-lbaas 12.0.0.0rc1 (queens)

Hello everyone, A new release candidate for neutron-lbaas for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron-lbaas/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

[openstack-dev] [octavia] octavia 2.0.0.0rc1 (queens)

Hello everyone, A new release candidate for octavia for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/octavia/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [octavia] neutron-lbaas-dashboard 4.0.0.0rc1 (queens)

Hello everyone, A new release candidate for neutron-lbaas-dashboard for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron-lbaas-dashboard/ Unless release-critical issues are found that warrant a release candidate

[openstack-dev] [vitrage] Tagged Vitrage release candidates and created stable/queens branches

Hi, I tagged the following release candidates for Vitrage: vitrage 2.1.0 vitrage-dashboard 1.4.1 python-vitrageclient 2.0.0 (already tagged) All these repositories now have stable/queens branches, so the master can be used for Rocky development. Thanks, Ifat.

Re: [openstack-dev] [release][requirements][monasca] FFE request for monasca-common

On 18-02-08 14:41:21, Dirk Müller wrote: > 2018-02-08 11:05 GMT+01:00 Bedyk, Witold : > > > I would like to request FFE for monasca-common to be bumped in upper > > constraints. The version has been bumped together with the rest of Monasca > > components [1].