Lauren,

A few comments.

1. Ironic is both baremetal provisioning and deployment tool. Suggest we replace Bifrost with Bifrost/Ironic.

2. Deployment tools is too restrictive. Suggest renaming it Life-cycle Management. It covers deployment, update, upgrade, etc.

3. Why is AODH part of Orchestration and not Monitoring Tools.

4. Suggest adding Tempest to Optimization/policy tools bucket. Also suggest renaming it as validation/optimization/policy tools. Tempest is used by many users as validation tool and we expect customers and distros submit tempest results for interop/refstack.

Thanks,
Arkady

From: Lauren Sell [mailto:lauren@openstack.org]
Sent: Monday, October 09, 2017 4:47 PM
To: foundation-board@lists.openstack.org mailing list <foundation-board@lists.openstack.org>; goldmembers@lists.openstack.org; openstack-tc@lists.openstack.org
Cc: Thierry Carrez <thierry@openstack.org>
Subject: Re: [Gold Members] [Foundation Board] OpenStack Deliverables Map -- Feedback Request

Hi everyone,

To follow up on this process, Thierry and I updated the OpenStack projects map based on feedback provided at the joint leadership meeting and subsequently in the etherpad. Thank you to everyone who took the time to review the map and provide feedback. Unless there are any major issues, we hope to present the current draft as v1 in Sydney and continue iterating over the next cycle.

Changes made to v1 based on community feedback:

- Added python sdk in the openstack-user bucket, since it is an official SDK

- Added Blazar in Orchestration subcategory

- Added Tricircle to the operations bucket under a "multi-region tools” subcategory

- Added Cyborg to operations bucket under “Optimization"

- Moved Freezer to 'Application Lifecycle’ subcategory

- Moved Tacker to the "adjacent tech enabler" bucket, in a "NFV” subcategory

- Moved Aodh to the "Orchestration” subcategory

- Renamed the "OPENSTACK-IAAS" bucket to simply "OPENSTACK”  (addressing some issues about what was defined as iaas, and side benefit: this would keep existing links to the main github org working)

- Moved Glance to the "shared services” subcategory, based on feedback that it did not fit under virtual machines

- Added Zun to a "Containers" column within the "Compute” subcategory, based on feedback that it was a lower level service, not orchestration

Outstanding work (post Sydney v2):

- Would be nice to be able to dynamically change the map to only show projects that have a given maturity level or higher - e.g. if you set it to "maturity of 6 and above", you'd see a map with Nova, Cinder, Keystone, Neutron, and Swift

- There was also a comment about bold vs non-bold projects which is intended to be a maturity/adoption indicator in the meantime

Also note we adjusted the layout so it fits more nicely into presentations without having to shrink the font as much.

Thanks!

Lauren