<div dir="ltr"><div><br><div class="gmail_quote"><div dir="ltr">On Wed, Sep 26, 2018 at 1:56 PM Tim Bell <<a href="mailto:Tim.Bell@cern.ch">Tim.Bell@cern.ch</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Doug,<br>
<br>
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.<br>
<br>
To give it some context and the motivation:<br>
<br>
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.). <br>
<br>
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.<br>
<br>
I would strongly support a goal which targets<br>
<br>
- All new projects should have the end user facing functionality fully exposed via the unified client<br>
- Existing projects should aim to close the gap within 'N' cycles (N to be defined)<br>
- Many administrator actions would also benefit from integration (reader roles are end users too so list and show need to be covered too)<br>
- 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)<br>
<br></blockquote><div><br></div><div>Sorry to back up the conversation a bit, but does reader role require work in the clients? Last release we incorporated three roles by default during keystone's installation process [0]. Is the definition in the specification what you mean by reader role, or am I on a different page?<div><br></div><div>[0] <a href="http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html#default-roles">http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/define-default-roles.html#default-roles</a></div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The end user perception of a solution will be greatly enhanced by a single command line tool with consistent syntax and authentication framework.<br>
<br>
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.<br>
<br>
Tim<br>
<br>
-----Original Message-----<br>
From: Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>><br>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Date: Wednesday, 26 September 2018 at 18:00<br>
To: openstack-dev <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>, openstack-operators <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>>, openstack-sigs <<a href="mailto:openstack-sigs@lists.openstack.org">openstack-sigs@lists.openstack.org</a>><br>
Subject: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series<br>
<br>
It's time to start thinking about community-wide goals for the T series.<br>
<br>
We use community-wide goals to achieve visible common changes, push for<br>
basic levels of consistency and user experience, and efficiently improve<br>
certain areas where technical debt payments have become too high -<br>
across all OpenStack projects. Community input is important to ensure<br>
that the TC makes good decisions about the goals. We need to consider<br>
the timing, cycle length, priority, and feasibility of the suggested<br>
goals.<br>
<br>
If you are interested in proposing a goal, please make sure that before<br>
the summit it is described in the tracking etherpad [1] and that you<br>
have started a mailing list thread on the openstack-dev list about the<br>
proposal so that everyone in the forum session [2] has an opportunity to<br>
consider the details. The forum session is only one step in the<br>
selection process. See [3] for more details.<br>
<br>
Doug<br>
<br>
[1] <a href="https://etherpad.openstack.org/p/community-goals" rel="noreferrer">https://etherpad.openstack.org/p/community-goals</a><br>
[2] <a href="https://www.openstack.org/summit/berlin-2018/vote-for-speakers#/22814" rel="noreferrer">https://www.openstack.org/summit/berlin-2018/vote-for-speakers#/22814</a><br>
[3] <a href="https://governance.openstack.org/tc/goals/index.html" rel="noreferrer">https://governance.openstack.org/tc/goals/index.html</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div></div>