Re: [Openstack-operators] new SIGs to cover use cases

Good point. Adding SIG list. -Original Message- From: Jeremy Stanley [mailto:fu...@yuggoth.org] Sent: Monday, November 12, 2018 4:46 PM To: openstack-operators@lists.openstack.org Subject: Re: [Openstack-operators] new SIGs to cover use cases [EXTERNAL EMAIL] Please report any

[Openstack-operators] new SIGs to cover use cases

Team, At today Board and joint TC and UC meetings 2 questions come up: 1. Do we have or want to create a user community around Hybrid cloud. This is one of the major push of OpenStack for the communities. With 70+% of questionnaire responders told that they deploy and use hybrid cloud. We do

Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

Love the idea to have clearer terminology. Suggest we let telco folks to suggest terminology to use. This is not a 3 level hierarchy but much more. There are several layers of aggregation from local to metro, to regional, to DC. And potential multiple layers in each. -Original Message-

Re: [openstack-dev] [all][tc][elections] Stein TC Election Results

Congrats to newly elected TCs and all people who run. -Original Message- From: Doug Hellmann Sent: Friday, September 28, 2018 10:29 AM To: Emmet Hikory; OpenStack Developers Subject: Re: [openstack-dev] [all][tc][elections] Stein TC Election Results [EXTERNAL EMAIL] Please report any

Re: [openstack-dev] [release] Release model for feature-complete OpenStack libraries

How will we handle which versions of libraries work together? And which combinations will be run thru CI? -Original Message- From: Thierry Carrez Sent: Friday, September 28, 2018 7:17 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [release] Release model for

Re: [Openstack-operators] [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

+1 -Original Message- From: Tim Bell [mailto:tim.b...@cern.ch] Sent: Wednesday, September 26, 2018 1:56 PM To: OpenStack Development Mailing List (not for usage questions); openstack-operators; openstack-sigs Subject: Re: [Openstack-sigs] [openstack-dev] [goals][tc][ptl][uc] starting

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

+1 -Original Message- From: Tim Bell [mailto:tim.b...@cern.ch] Sent: Wednesday, September 26, 2018 1:56 PM To: OpenStack Development Mailing List (not for usage questions); openstack-operators; openstack-sigs Subject: Re: [Openstack-sigs] [openstack-dev] [goals][tc][ptl][uc] starting

Re: [openstack-dev] [tripleo] PTL non-candidacy

Indeed. Thanks Alex for your great leadership of TripleO. From: Remo Mattei [mailto:r...@rm.ht] Sent: Wednesday, July 25, 2018 4:09 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tripleo] PTL non-candidacy I want publically want to say THANK

Re: [openstack-dev] [cinder] about block device driver

Is this for ephemeral storage handling? -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Monday, July 16, 2018 8:44 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [cinder] about block device driver On 07/16/2018 09:32 AM, Sean McGinnis wrote: >

Re: [openstack-dev] [tripleo] Proposing Alan Bishop tripleo core on storage bits

+1 From: John Fulton [mailto:johfu...@redhat.com] Sent: Wednesday, June 13, 2018 11:23 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tripleo] Proposing Alan Bishop tripleo core on storage bits On Wed, Jun 13, 2018, 12:04 PM Marios Andreou

Re: [Openstack-operators] [openstack-dev] The Forum Schedule is now live

LOL From: Jimmy McArthur [mailto:ji...@openstack.org] Sent: Monday, April 30, 2018 1:22 PM To: Kanevsky, Arkady Cc: a...@demarco.com; openstack-...@lists.openstack.org; OpenStack-operators@lists.openstack.org Subject: Re: [Openstack-operators] [openstack-dev] The Forum Schedule is now live We

Re: [openstack-dev] [Openstack-operators] The Forum Schedule is now live

LOL From: Jimmy McArthur [mailto:ji...@openstack.org] Sent: Monday, April 30, 2018 1:22 PM To: Kanevsky, Arkady Cc: a...@demarco.com; openstack-dev@lists.openstack.org; openstack-operat...@lists.openstack.org Subject: Re: [Openstack-operators] [openstack-dev] The Forum Schedule is now live We

Re: [Openstack-operators] [openstack-dev] The Forum Schedule is now live

Both are currently empty. From: Jimmy McArthur [mailto:ji...@openstack.org] Sent: Monday, April 30, 2018 10:48 AM To: Amy Marrich Cc: OpenStack Development Mailing List (not for usage questions); OpenStack-operators@lists.openstack.org Subject: Re: [Openstack-operators] [openstack-dev] The Forum

Re: [openstack-dev] [Openstack-operators] The Forum Schedule is now live

Both are currently empty. From: Jimmy McArthur [mailto:ji...@openstack.org] Sent: Monday, April 30, 2018 10:48 AM To: Amy Marrich Cc: OpenStack Development Mailing List (not for usage questions); openstack-operat...@lists.openstack.org Subject: Re: [Openstack-operators] [openstack-dev] The Forum

Re: [openstack-dev] [tripleo] ironic automated cleaning by default?

+1. It would be good to also identify the use cases. Surprised that node should be cleaned up automatically. I would expect that we want it to be a deliberate request from administrator to do. Maybe user when they "return" a node to free pool after baremetal usage. Thanks, Arkady -Original

Re: [Openstack-operators] Ops Meetup, Co-Location options, and User Feedback

+1 From: Erik McCormick [mailto:emccorm...@cirrusseven.com] Sent: Monday, April 2, 2018 3:57 PM To: Melvin Hillsman Cc: openstack-operators Subject: Re: [Openstack-operators] Ops Meetup, Co-Location options, and User Feedback I'm

Re: [Openstack] iSCSI multipath

Ramon, It is volume_driver=cinder.volume.drivers.dell_emc.sc.storagecenter_iscsi.SCISCSIDriver these days. The volume is mapped to all paths whether they will be used or not. -Original Message- From: Ramon Orru [mailto:ramon.o...@immobiliare.it] Sent: Friday, March 23, 2018 9:07 AM

Re: [Openstack] iSCSI multipath

Ramon, Which DellEMC driver is that? VNX? -Original Message- From: Ramon Orru [mailto:ramon.o...@immobiliare.it] Sent: Friday, March 23, 2018 6:35 AM To: openstack@lists.openstack.org Subject: [Openstack] iSCSI multipath Hi everyone, I'm using delliscsi driver as cinder backend in a

Re: [openstack-dev] [refstack] Full list of API Tests versus 'OpenStack Powered' Tests

Greg, For compliance it is sufficient to run https://refstack.openstack.org/#/guidelines. But it is good if you can also submit fill Tempest run. That is used internally by refstack to identify which tests to include in the future. This can be submitted anonymously if you like. Thanks, Arkady

Re: [openstack-dev] [DriverLog] DriverLog future

Having 3rd party CI report results automatically will be helpful. While it is possible for PTLs to report per release which drivers should be listed in marketplace for release, currently PTLs are signed for this extra work. Driver owners submitting DriverLog updates per release – not a big

Re: [Openstack-operators] [User-committee] User Committee Election Results - February 2018

Congrats to new committee members. And thanks for great job for previous ones. From: Shilla Saebi [mailto:shilla.sa...@gmail.com] Sent: Sunday, February 25, 2018 5:52 PM To: user-committee ; OpenStack Mailing List ; OpenStack

Re: [openstack-dev] [User-committee] User Committee Election Results - February 2018

Congrats to new committee members. And thanks for great job for previous ones. From: Shilla Saebi [mailto:shilla.sa...@gmail.com] Sent: Sunday, February 25, 2018 5:52 PM To: user-committee ; OpenStack Mailing List ; OpenStack

Re: [Openstack-operators] User Committee Elections

I saw election email with the pointer to votes. See no reason for stopping it now. But extending vote for 1 more week makes sense. Thanks, Arkady From: Melvin Hillsman [mailto:mrhills...@gmail.com] Sent: Monday, February 19, 2018 11:32 AM To: user-committee ;

Re: [openstack-dev] [Openstack-operators] User Committee Elections

I saw election email with the pointer to votes. See no reason for stopping it now. But extending vote for 1 more week makes sense. Thanks, Arkady From: Melvin Hillsman [mailto:mrhills...@gmail.com] Sent: Monday, February 19, 2018 11:32 AM To: user-committee ;

Re: [Openstack-operators] [User-committee] Stepping aside announcement

Edgar, thank you for all your hard work and passion. From: Melvin Hillsman [mailto:mrhills...@gmail.com] Sent: Monday, January 29, 2018 12:45 PM To: Amy Marrich Cc: openst...@lists.openstack.org; openstack-operators ; user-committee

Re: [openstack-dev] [cinder] Leaving the Cinder core team

Good luck. We will miss you. From: Patrick East [mailto:patrick.e...@purestorage.com] Sent: Wednesday, December 20, 2017 6:10 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [cinder] Leaving the Cinder core team Hi

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

Thanks for response. My recommendation is: 1. only allow patches into openstack/ironic-tempest-plugin 2. Give Ironic CI owners time period (3 weeks?) to switch their setup to only use openstack/ironic-tempest-plugin and not master and report back to Ironic CI team if it works for them. If yes,

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

John, Should we give all Ironic CI maintainers to do the migration before pulling the code from master? Especially that close to holiday season when a lot of folks are out. We want to avoid Ironic CI not being functional for several weeks. Thanks, Arkady From: John Villalovos

Re: [Openstack-operators] Openstack operational configuration improvement.

Flint, I do support UI method for solution management. My point is that it is not Horizon one as it is on a different layer. From: Flint WALRUS [mailto:gael.ther...@gmail.com] Sent: Monday, December 18, 2017 9:40 AM To: Kanevsky, Arkady Cc:

Re: [openstack-dev] [all] Switching to longer development cycles

How about add to our biannual questionnaire how often customer upgrade their openstack environment? -Original Message- From: Thierry Carrez [mailto:thie...@openstack.org] Sent: Wednesday, December 13, 2017 4:20 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [all]

Re: [Openstack-operators] thierry's longer dev cycle proposal

It is a sign of the maturity of OpenStack. With lots of deployment and most of them in production, the emphasis is shifting from rapid functionality additions to stability, manageability, and long term operability. -Original Message- From: Melvin Hillsman [mailto:mrhills...@gmail.com]

Re: [openstack-dev] [all] Switching to longer development cycles

A lot of great points. If we are switching to 1 year cycle do we also move summits/forum to once a year... That impacts much more than developers. -Original Message- From: Matt Riedemann [mailto:mriede...@gmail.com] Sent: Wednesday, December 13, 2017 10:52 AM To:

Re: [openstack-dev] [all] Switching to longer development cycles

Thierry, Thanks for starting this discussion. I support move to 1 year cycle. With OpenStack maturity and adoption it is a natural transformation. However, we also need to consider previous releases, support for them and "." release for them. Also for projects that are "in early stages" they

Re: [Openstack-operators] [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

See you there Eric. From: Erik McCormick [mailto:emccorm...@cirrusseven.com] Sent: Monday, October 30, 2017 10:58 AM To: Matt Riedemann Cc: OpenStack Development Mailing List ; openstack-operators

Re: [openstack-dev] [Openstack-operators] [skip-level-upgrades][fast-forward-upgrades] PTG summary

See you there Eric. From: Erik McCormick [mailto:emccorm...@cirrusseven.com] Sent: Monday, October 30, 2017 10:58 AM To: Matt Riedemann Cc: OpenStack Development Mailing List ; openstack-operators

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

The second seem to be better suited for per driver requirement handling and per HW type per function. Which option is easier to handle for container per dependency for the future? Thanks, Arkady -Original Message- From: Doug Hellmann [mailto:d...@doughellmann.com] Sent: Monday,

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

Congrats to all From: Edgar Magana [mailto:edgar.mag...@workday.com] Sent: Saturday, October 21, 2017 12:00 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] [elections] Technical Committee Election Results

[Openstack-operators] https://www.openstack.org/marketplace/ web changes

Danny and team, What is the process of updating the web page template for detailed "distro" information to align with updated project-navigator. For example, to add AODH, PANKO, Tempest, Rally as projects for distro solution offering? Just looking for a process of requesting/making changes to

Re: [Openstack-operators] It's time...

Tom, Thank you for everything. Arkady From: Rico Lin [mailto:rico.lin.gua...@gmail.com] Sent: Wednesday, October 04, 2017 9:45 AM To: Tom Fifield Cc: OpenStack Operators Subject: Re: [Openstack-operators] It's time... Tom, It's my

Re: [Openstack-operators] [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

There are some loose ends that Saverio correctly bringing up. These perfect points to discuss at Forum. Suggest we start etherpad to collect agenda for it. -Original Message- From: Lee Yarwood [mailto:lyarw...@redhat.com] Sent: Friday, September 29, 2017 7:04 AM To: Saverio Proto

Re: [openstack-dev] [Openstack-operators] [skip-level-upgrades][fast-forward-upgrades] PTG summary

There are some loose ends that Saverio correctly bringing up. These perfect points to discuss at Forum. Suggest we start etherpad to collect agenda for it. -Original Message- From: Lee Yarwood [mailto:lyarw...@redhat.com] Sent: Friday, September 29, 2017 7:04 AM To: Saverio Proto

Re: [Openstack-operators] [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Erik, Thanks for setting up a session for it. Glad it is driven by Operators. I will be happy to work with you on the session and run it with you. Thanks, Arkady From: Erik McCormick [mailto:emccorm...@cirrusseven.com] Sent: Thursday, September 28, 2017 7:40 AM To: Lee Yarwood

Re: [openstack-dev] [Openstack-operators] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Erik, Thanks for setting up a session for it. Glad it is driven by Operators. I will be happy to work with you on the session and run it with you. Thanks, Arkady From: Erik McCormick [mailto:emccorm...@cirrusseven.com] Sent: Thursday, September 28, 2017 7:40 AM To: Lee Yarwood

Re: [Openstack-operators] [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Lee, I can chair meeting in Sydney. Thanks, Arkady -Original Message- From: Lee Yarwood [mailto:lyarw...@redhat.com] Sent: Wednesday, September 20, 2017 8:29 AM To: openstack-...@lists.openstack.org; openstack-operators@lists.openstack.org Subject: [openstack-dev]

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Lee, I can chair meeting in Sydney. Thanks, Arkady -Original Message- From: Lee Yarwood [mailto:lyarw...@redhat.com] Sent: Wednesday, September 20, 2017 8:29 AM To: openstack-dev@lists.openstack.org; openstack-operat...@lists.openstack.org Subject: [openstack-dev]

Re: [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary

Lee, I can chair meeting in Sydney. Thanks, Arkady -Original Message- From: Lee Yarwood [mailto:lyarw...@redhat.com] Sent: Wednesday, September 20, 2017 8:29 AM To: openstack-dev@lists.openstack.org; openstack-operat...@lists.openstack.org Subject: [openstack-dev]

Re: [openstack-dev] [interop][refstack] proposal for extending published and submitted info

Fellow interop members, I would like to request we consider adding information on what was tested for interop. Specifically, if you are listed in distros and appliances it would be good to be able to specify what underlying HW was used for interop testing. I do not propose that as the

Re: [openstack-dev] [ironic] Team dinner at the PTG?

Great. See you all there. -Original Message- From: Dmitry Tantsur [mailto:dtant...@redhat.com] Sent: Monday, August 28, 2017 1:07 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [ironic] Team dinner at

Re: [openstack-dev] [Interop-wg] [refstack][interop-wg] Non-candidacy for RefStack PTL

Here here. Thanks Catherine for a great job for many years. From: Egle Sigler [mailto:ushnish...@hotmail.com] Sent: Wednesday, August 02, 2017 3:54 PM To: Catherine Cuong Diep ; openstack-dev@lists.openstack.org; interop...@lists.openstack.org Subject: Re: [openstack-dev]

Re: [openstack-dev] [elections][tripleo] Queens PTL candidacy

+1 -Original Message- From: Alex Schultz [mailto:aschu...@redhat.com] Sent: Wednesday, August 02, 2017 8:56 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [elections][tripleo] Queens PTL candidacy I would

Re: [openstack-dev] [all][tc] Wiki

Most of google searches will pickup wiki pages. So people will view wiki as the current state of projects. -Original Message- From: Thierry Carrez [mailto:thie...@openstack.org] Sent: Monday, July 03, 2017 9:30 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev]

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

Right on the point Rocky (no wonder you have release named after you) We also need to update https://www.openstack.org/software/project-navigator/ To align with whatever decision agreed upon. And we better make decision stick and not change it again in a year or two. Arkady -Original

Re: [openstack-dev] [Product] PTG attendance

Fellow Product WG members, We are taking informal poll on how many of us plan to attend PTG meeting in Denver? Second question should we have mid-cycle meeting co-located with PTG or with operator summit in Mexico city? Please, respond to this email so Shamail and Leong can tally the results.

Re: [openstack-dev] [Openstack-operators] [dev] [doc] Operations Guide future

Option 3 sound reasonable if wiki can be searchable. -Original Message- From: Blair Bethwaite [mailto:blair.bethwa...@gmail.com] Sent: Thursday, June 01, 2017 8:44 PM To: Alexandra Settle Cc: OpenStack Operators ;

[openstack-dev] [User] Achieving Resiliency at Scales of 1000+

Team, We manage to have a productive discussion on resiliency for 1000+ nodes. Many thanks to Adam Spiers on helping with it. https://etherpad.openstack.org/p/Achieving_Resiliency_at_Scales_of_1000+ There are several concrete actions especially for current gate testing. Will bring these at the

Re: [openstack-dev] [User-committee] [Forum] Moderators needed!

No problems. All sorted out. From: Sam P [mailto:sam47pr...@gmail.com] Sent: Saturday, April 29, 2017 9:15 PM To: Kanevsky, Arkady Cc: Shamail Tahir ; OpenStack Operators ; OpenStack Development Mailing

Re: [openstack-dev] [User-committee] [Forum] Moderators needed!

Shamail, I can moderate either Achieving Resiliency at Scales of 1000+ or High Availability in

Re: [openstack-dev] [PWG] mid-cycle venue option

Team, I had updated venue info at https://etherpad.openstack.org/p/MIL-pwg-meetup. That includes nearby hotel info. Rate from Hotels.com, booking.com, expedia.com and so on give me better rate than corporate one. Need to cover some logistic issues. 1. Do we need breakfast? Or everybody

[openstack-dev] call today

Do we have PTG call this week? __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

There is no project that can stand on its own. Even Swift need some identity management. Thus, even if you are contributing to only one project your are still dependent on many others. Including QA and infrastructure and so on. While most Customers are looking on a few projects together and not

Re: [openstack-dev] Refstack - final mascot

+1 From: Rochelle Grober [mailto:rochelle.gro...@huawei.com] Sent: Tuesday, February 07, 2017 8:36 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] Refstack - final mascot Looks great to me. --Rocky From:

[openstack-dev] [PWG] mid-cycle venue option

Team, I finally checked on my side for the venue. The address of my available venue is Company: Dell Street: Viale Piero e Alberto Pirelli 6 City: Milano That is about 15 min drive or 20 min on public transport from coworking place. I reserved 2 conf rooms for mon-tue. While on Tue you'll

Re: [openstack-dev] [ironic] New mascot design

I think Russian already owns the bear. From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] Sent: Tuesday, January 31, 2017 2:49 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [ironic] New mascot design Hey

Re: [openstack-dev] [tripleo] Release notes in TripleO

Does that applies to drivers also? -Original Message- From: Ben Nemec [mailto:openst...@nemebean.com] Sent: Wednesday, January 11, 2017 8:49 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tripleo]

Re: [openstack-dev] [tripleo] Fwd: Do you want to ask a project-specific question on the next User Survey?

+1 From: Ligong LG1 Duan [mailto:duan...@lenovo.com] Sent: Sunday, January 08, 2017 7:41 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tripleo] Fwd: Do you want to ask a project-specific question on the next

Re: [openstack-dev] [TripleO] Fixing Swift rings when upscaling/replacing nodes in TripleO deployments

Thanks -Original Message- From: Christian Schwede [mailto:cschw...@redhat.com] Sent: Thursday, January 05, 2017 1:29 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [TripleO] Fixing Swift rings when upscaling/replacing nodes in TripleO deployments On 05.01.2017

Re: [openstack-dev] [tripleo] Fwd: Do you want to ask a project-specific question on the next User Survey?

Suggest we request a question on life-cycle management tools, including TripleO, like upgrade, patching, etc. Not just deployment. Arkady From: Emilien Macchi [mailto:emil...@redhat.com] Sent: Tuesday, January 03, 2017 8:08 AM To: OpenStack Development Mailing List

Re: [openstack-dev] [TripleO] Fixing Swift rings when upscaling/replacing nodes in TripleO deployments

I have concern to rely on undercloud for overcloud swift. Undercloud is not HA (yet) so it may not be operational when disk failed or swift overcloud node is added/deleted. -Original Message- From: Christian Schwede [mailto:cschw...@redhat.com] Sent: Thursday, January 05, 2017 6:14 AM

Re: [openstack-dev] [ironic] python-wsmanclient future

+1 -Original Message- From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] Sent: Tuesday, November 15, 2016 10:00 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [ironic] python-wsmanclient future On

Re: [openstack-dev] [ironic] Removing agent vendor passthru and unsupported drivers

Agree with removal of unsupported drivers. For supported drivers we will still need to support passthru. First, because it is currently used by many customers and for many drivers. Second, we will need to add support in Ironic and expose it in API for many features before we can do them without

Re: [openstack-dev] [ironic] When should a project be under Ironic's governance?

Second try -Original Message- From: Kanevsky, Arkady Sent: Thursday, November 10, 2016 10:08 AM To: OpenStack Development Mailing List (not for usage questions) Subject: RE: [openstack-dev] [ironic] When should a project be under Ironic's governance?