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 in
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.: n
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
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 re
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 O
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
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.
I