Re: [openstack-dev] [openstackclient][openstacksdk] why does openstackclient rely on openstacksdk for get a network client
On 06/20/2018 10:23 AM, Dean Troyer wrote: On Tue, Jun 19, 2018 at 9:42 PM, zijian1...@163.com wrote: Thks for replying, just want to confirm, you mentioned "We have intended to migrate everything to use OpenStackSDK", the current use of python-*client is: 1. OSC 2. all services that need to interact with other services (e.g.: nova libraries: self.volume_api = volume_api or cinder.API()) Do you mean that both of the above will be migrated to use the OpenStack SDK? I am only directly speaking for OSC. Initially we did not think that services using the SDK would be feasible, Monty has taken it to a place where that should now be a possibility. I am willing to find out that doing so is a good idea. :) Yes, I think this is a good idea to explore - but I also think we should be conservative with the effort. There are things we'll need to learn about and improve. We're VERY close to time for making the push to get OSC converted (we need to finish one more patch for version discovery / microversion support first - and I'd really like to get an answer for the Resource/munch/shade interaction in - but that's honestly realistically like 2 or maybe 3 patches, even though they will be 2 or 3 complex patches. I started working a bit on osc-lib patches - I'll try to get those pushed up soon. Monty __ 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
Re: [openstack-dev] [openstackclient][openstacksdk] why does openstackclient rely on openstacksdk for get a network client
On Tue, Jun 19, 2018 at 9:42 PM, zijian1...@163.com wrote: > Thks for replying, just want to confirm, you mentioned "We have intended to > migrate everything to use > OpenStackSDK", the current use of python-*client is: > 1. OSC > 2. all services that need to interact with other services (e.g.: nova > libraries: self.volume_api = volume_api or cinder.API()) > Do you mean that both of the above will be migrated to use the OpenStack > SDK? I am only directly speaking for OSC. Initially we did not think that services using the SDK would be feasible, Monty has taken it to a place where that should now be a possibility. I am willing to find out that doing so is a good idea. :) dt -- Dean Troyer dtro...@gmail.com __ 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
Re: [openstack-dev] [openstackclient][openstacksdk] why does openstackclient rely on openstacksdk for get a network client
On Tue, Jun 19, 2018 at 11:15 AM, 李健 wrote: >> So, my question is, why does the network service not use the >> python2-neutronclient to get the client like other core projects, but >> instead uses another separate project(openstacksdk)? > There were multiple reasons to not use neutron client lib for OSC and > the SDk was good enough at the time to use ut in spite of not being at > a 1.0 release. We have intended to migrate everything to use > OpenStackSDK and eliminate OSC's use of the python-*client libraries > completely. Thks for replying, just want to confirm, you mentioned "We have intended to migrate everything to use OpenStackSDK", the current use of python-*client is: 1. OSC 2. all services that need to interact with other services (e.g.: nova libraries: self.volume_api = volume_api or cinder.API()) Do you mean that both of the above will be migrated to use the OpenStack SDK? > We are waiting on an SDK 1.0 release, it has stretched on > for years longer than originally anticipated but the changes we have > had to accommodate in the network commands in the past convinced me to > wait until it was declared stable, even though it has been nearly > stable for a while now. >> My personal opinion, openstacksdk is a project that can be used >> independently, it is mainly to provide a unified sdk for developers, so >> there should be no interdependence between python-xxxclient and >> openstacksdk, right? > Correct, OpenStackSDK has no dependency on any of the python-*client > libraries.. Its primary dependency is on keystoneauth for the core > authentication logic, that was long ago pulled out of the keystone > client package. > dt __ 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
Re: [openstack-dev] [openstackclient][openstacksdk] why does openstackclient rely on openstacksdk for get a network client
On 06/19/2018 03:51 PM, Dean Troyer wrote: On Tue, Jun 19, 2018 at 11:15 AM, 李健 wrote: So, my question is, why does the network service not use the python2-neutronclient to get the client like other core projects, but instead uses another separate project(openstacksdk)? There were multiple reasons to not use neutron client lib for OSC and the SDk was good enough at the time to use ut in spite of not being at a 1.0 release. We have intended to migrate everything to use OpenStackSDK and eliminate OSC's use of the python-*client libraries completely. We are waiting on an SDK 1.0 release, it has stretched on for years longer than originally anticipated but the changes we have had to accommodate in the network commands in the past convinced me to wait until it was declared stable, even though it has been nearly stable for a while now. Soon. Really soon. I promise. My personal opinion, openstacksdk is a project that can be used independently, it is mainly to provide a unified sdk for developers, so there should be no interdependence between python-xxxclient and openstacksdk, right? Correct, OpenStackSDK has no dependency on any of the python-*client libraries.. Its primary dependency is on keystoneauth for the core authentication logic, that was long ago pulled out of the keystone client package. dt __ 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
Re: [openstack-dev] [openstackclient][openstacksdk] why does openstackclient rely on openstacksdk for get a network client
On Tue, Jun 19, 2018 at 11:15 AM, 李健 wrote: > So, my question is, why does the network service not use the > python2-neutronclient to get the client like other core projects, but > instead uses another separate project(openstacksdk)? There were multiple reasons to not use neutron client lib for OSC and the SDk was good enough at the time to use ut in spite of not being at a 1.0 release. We have intended to migrate everything to use OpenStackSDK and eliminate OSC's use of the python-*client libraries completely. We are waiting on an SDK 1.0 release, it has stretched on for years longer than originally anticipated but the changes we have had to accommodate in the network commands in the past convinced me to wait until it was declared stable, even though it has been nearly stable for a while now. > My personal opinion, openstacksdk is a project that can be used > independently, it is mainly to provide a unified sdk for developers, so > there should be no interdependence between python-xxxclient and > openstacksdk, right? Correct, OpenStackSDK has no dependency on any of the python-*client libraries.. Its primary dependency is on keystoneauth for the core authentication logic, that was long ago pulled out of the keystone client package. dt -- Dean Troyer dtro...@gmail.com __ 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
Re: [openstack-dev] [openstackclient][openstacksdk] why does openstackclient rely on openstacksdk for get a network client
Hi, No. Not right. Idea is to unify CLI for all projects inside of the python-openstackclient and obsolete all individual python-XXXclients. This can be achieved by using the openstacksdk. Network module was just first in the row, where the progress stucked a bit. Regards, On Tue, Jun 19, 2018 at 6:15 PM, 李健 wrote: > Hello everyone > --- > CentOS Linux release 7.3.1611 > OpenStack Version: Newton > # rpm -qa | egrep "(openstacksdk|openstackclient)" > python-openstackclient-3.2.1-1.el7.noarch > python2-openstacksdk-0.9.5-1.el7.noarch > > The openstack CLI is implemented by python-openstackclient. > In the python-openstackclient package, the function make_client(instance) > is used to obtain the client for each service (openstackclient/xxx/client.py), > I noticed that almost all core services are import their own > python2-xxxclient to get the client, for example: > image/client.py --> import glanceclient.v2.client.Client > compute/client.py --> import novaclient.client > volume/client.py --> import cinderclient.v2.client.Client > > But only the network service is import openstacksdk to get the client, as > follows: > network/client.py --> import openstack.connection.Connection > > So, my question is, why does the network service not use the > python2-neutronclient to get the client like other core projects, but > instead uses another separate project(openstacksdk)? > My personal opinion, openstacksdk is a project that can be used > independently, it is mainly to provide a unified sdk for developers, so > there should be no interdependence between python-xxxclient and > openstacksdk, right? > > For any help, thks > > > __ > 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 > > __ 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
[openstack-dev] [openstackclient][openstacksdk] why does openstackclient rely on openstacksdk for get a network client
Hello everyone --- CentOS Linux release 7.3.1611 OpenStack Version: Newton # rpm -qa | egrep "(openstacksdk|openstackclient)" python-openstackclient-3.2.1-1.el7.noarch python2-openstacksdk-0.9.5-1.el7.noarch The openstack CLI is implemented by python-openstackclient. In the python-openstackclient package, the function make_client(instance) is used to obtain the client for each service (openstackclient/xxx/client.py), I noticed that almost all core services are import their own python2-xxxclient to get the client, for example: image/client.py --> import glanceclient.v2.client.Client compute/client.py --> import novaclient.client volume/client.py --> import cinderclient.v2.client.Client But only the network service is import openstacksdk to get the client, as follows: network/client.py --> import openstack.connection.Connection So, my question is, why does the network service not use the python2-neutronclient to get the client like other core projects, but instead uses another separate project(openstacksdk)? My personal opinion, openstacksdk is a project that can be used independently, it is mainly to provide a unified sdk for developers, so there should be no interdependence between python-xxxclient and openstacksdk, right? For any help, thks __ 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
