Hi, 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, Belmiro
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
On Thu, Aug 13, 2020 at 2:19 PM Belmiro Moreira < moreira.belmiro.email.lists@gmail.com> wrote: 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. - jokke On Mon, Aug 10, 2020 at 10:13 AM Belmiro Moreira <
moreira.belmiro.email.lists@gmail.com> wrote:
Hi, during the last PTG the TC discussed the problem of supporting different clients (OpenStack Client - OSC vs python-*clients) [1]. Currently, we don't have feature parity between the OSC and the python-*clients.
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.
Belmiro, on behalf of the TC
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015418.html