[Openstack-operators] [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series
Arkady.Kanevsky at dell.com
Arkady.Kanevsky at dell.com
Wed Sep 26 19:22:21 UTC 2018
From: Tim Bell [mailto:Tim.Bell at 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 goal selection for T series
Please report any suspicious attachments, links, or requests for sensitive information.
Thanks for raising this. I'd like to highlight the goal "Finish moving legacy python-*client CLIs to python-openstackclient" from the etherpad and propose this for a T/U series goal.
To give it some context and the motivation:
At CERN, we have more than 3000 users of the OpenStack cloud. We write an extensive end user facing documentation which explains how to use the OpenStack along with CERN specific features (such as workflows for requesting projects/quotas/etc.).
One regular problem we come across is that the end user experience is inconsistent. In some cases, we find projects which are not covered by the unified OpenStack client (e.g. Manila). In other cases, there are subsets of the function which require the native project client.
I would strongly support a goal which targets
- All new projects should have the end user facing functionality fully exposed via the unified client
- Existing projects should aim to close the gap within 'N' cycles (N to be defined)
- Many administrator actions would also benefit from integration (reader roles are end users too so list and show need to be covered too)
- Users should be able to use a single openrc for all interactions with the cloud (e.g. not switch between password for some CLIs and Kerberos for OSC)
The end user perception of a solution will be greatly enhanced by a single command line tool with consistent syntax and authentication framework.
It may be a multi-release goal but it would really benefit the cloud consumers and I feel that goals should include this audience also.
From: Doug Hellmann <doug at doughellmann.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Wednesday, 26 September 2018 at 18:00
To: openstack-dev <openstack-dev at lists.openstack.org>, openstack-operators <openstack-operators at lists.openstack.org>, openstack-sigs <openstack-sigs at lists.openstack.org>
Subject: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series
It's time to start thinking about community-wide goals for the T series.
We use community-wide goals to achieve visible common changes, push for
basic levels of consistency and user experience, and efficiently improve
certain areas where technical debt payments have become too high -
across all OpenStack projects. Community input is important to ensure
that the TC makes good decisions about the goals. We need to consider
the timing, cycle length, priority, and feasibility of the suggested
If you are interested in proposing a goal, please make sure that before
the summit it is described in the tracking etherpad  and that you
have started a mailing list thread on the openstack-dev list about the
proposal so that everyone in the forum session  has an opportunity to
consider the details. The forum session is only one step in the
selection process. See  for more details.
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
openstack-sigs mailing list
openstack-sigs at lists.openstack.org
More information about the OpenStack-operators