Hi,
As apiclient is now removed from oslo-incubator, to proceed with request-id
spec [1] I have two options in mind,
1. Use keystoneauth1 + cliff in all python-clients (add request-id
support in cliff library)
2. apiclient code is available in all python-*clients, modify this code
in individual clients and add support to return request-id.
Please let me know your opinion on the same.
[1] https://review.openstack.org/#/c/156508/
Thanks & Regards,
Abhishek Kekane
> On Nov 11, 2015, at 3:54 AM, Andrey Kurilin <akurilin at
> mirantis.com<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>>
> wrote:
>
>
>
> On Tue, Nov 10, 2015 at 4:25 PM, Sean Dague <sean at
> dague.net<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> <mailto:sean at
> dague.net<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>>>
> wrote:
> On 11/10/2015 08:24 AM, Andrey Kurilin wrote:
> >>It was also proposed to reuse openstackclient or the openstack SDK.
> >
> > Openstack SDK was proposed a long time ago(it looks like it was several
> > cycles ago) as "alternative" for cliutils and apiclient, but I don't
> > know any client which use it yet. Maybe openstacksdk cores should try to
> > port any client as an example of how their project should be used.
>
> The SDK is targeted for end user applications, not service clients. I do
> get there was lots of confusion over this, but SDK is not the answer
> here for service clients.
>
> Ok, thanks for explanation, but there is another question in my head: If
> openstacksdk is not for python-*clients, why apiclient(which is actually used
> by python-*clients) was marked as deprecated due to openstacksdk?
The Oslo team wanted to deprecate the API client code because it wasn't being
maintained. We thought at the time we did so that the SDK would replace the
clients, but discussions since that time have changed direction.
>
> The service clients are *always* going to have to exist in some form.
> Either as libraries that services produce, or by services deciding they
> don't want to consume the libraries of other clients and just put a
> targeted bit of rest code in their own tree to talk to other services.
>
> -Sean
>
> --
> Sean Dague
> http://dague.net <http://dague.net/>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at
> lists.openstack.org<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
> --
> Best regards,
> Andrey Kurilin.
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at
> lists.openstack.org<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> <mailto:OpenStack-dev-request at
> lists.openstack.org<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>>?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openstack.org/pipermail/openstack-dev/attachments/20151111/d457a660/attachment.html>
______________________________________________________________________
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
