[all][TC] OpenStack Client (OSC) vs python-*clients
ekuvaja at redhat.com
Thu Aug 13 13:36:34 UTC 2020
On Thu, Aug 13, 2020 at 2:19 PM Belmiro Moreira <
moreira.belmiro.email.lists at gmail.com> wrote:
> we would really appreciate your comments on this.
> Especially the OSC team and all the project teams that are facing issues
> migrating their clients.
> Let us know,
> In Glance perspective we already stated that we're more than happy to try
endorsing osc again once it has stabilized the Images API facing code and
maintained feature parity for a few cycles. Just stopping developing
python-glanceclient will only result in no up-to-date stable client for
Images API developed under OpenStack Governance. I really don't think
forcing to fork python-glanceclient to keep development going outside of
OpenStack Governance will be the better solution here.
On Mon, Aug 10, 2020 at 10:13 AM Belmiro Moreira <
> moreira.belmiro.email.lists at gmail.com> wrote:
>> during the last PTG the TC discussed the problem of supporting different
>> clients (OpenStack Client - OSC vs python-*clients) .
>> Currently, we don't have feature parity between the OSC and the
>> Different OpenStack projects invest in different clients.
>> This can be a huge problem for users/ops. Depending on the projects
>> deployed in their infrastructures, they need to use different clients for
>> different tasks.
>> It's confusing because of the partial implementation in the OSC.
>> There was also the proposal to enforce new functionality only in the SDK
>> (and optionally the OSC) and not the project’s specific clients to stop
>> increasing the disparity between the two.
>> We would like to understand first the problems and missing pieces that
>> projects are facing to move into OSC and help to overcome them.
>> Let us know.
>> on behalf of the TC
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss