On 08/07/2017 11:55 AM, Boden Russell wrote:
On 8/4/17 1:26 PM, Boris Pavlovic wrote:
That's not going to work for dozens of OpenStack projects. It's just
won't scale. Every project should maintain plugin for their project. And
it should be enough to say "pip install python-client" that
extend
On 8/4/17 1:26 PM, Boris Pavlovic wrote:
>
> That's not going to work for dozens of OpenStack projects. It's just
> won't scale. Every project should maintain plugin for their project. And
> it should be enough to say "pip install python-client" that
> extend the Core OpenStack python client and
On 08/04/2017 04:03 PM, Dean Troyer wrote:
On Fri, Aug 4, 2017 at 11:52 AM, Monty Taylor wrote:
[...]
* Both shade and python-openstackclient have investigated using openstacksdk
as their REST layer but were unable to because it puts some abstractions in
layers that make it impossible to do som
On Fri, Aug 4, 2017, at 02:37 PM, Kevin L. Mitchell wrote:
> On Fri, 2017-08-04 at 12:26 -0700, Boris Pavlovic wrote:
> > By the way stevedore is really providing very bad plugin experience
> > and should not be used definitely.
>
> Perhaps entrypointer[1]? ;)
>
> [1] https://pypi.python.org/pyp
On Fri, 2017-08-04 at 12:26 -0700, Boris Pavlovic wrote:
> By the way stevedore is really providing very bad plugin experience
> and should not be used definitely.
Perhaps entrypointer[1]? ;)
[1] https://pypi.python.org/pypi/entrypointer
--
Kevin L. Mitchell
signature.asc
Description: This is
On Fri, Aug 4, 2017 at 11:52 AM, Monty Taylor wrote:
[...]
> * Both shade and python-openstackclient have investigated using openstacksdk
> as their REST layer but were unable to because it puts some abstractions in
> layers that make it impossible to do some of the advanced things we need.
OSC _
Monty,
* drop stevedore/plugin support. An OpenStack REST client has no need for
> plugins. All services are welcome. *note below*
Back to 60s style of development? Just copy paste things? no plugins? no
architecture? no libs?
That's not going to work for dozens of OpenStack projects. It's jus
Also note that this appears to exist:
https://github.com/openstack/python-openstackclient/blob/master/requirements.txt#L10
So even if python-openstacksdk is not a top level project, I would
assume that it being a requirement would imply that it is? Or perhaps
neither the python-openstackclient
-Original Message-
From: Monty Taylor [mailto:mord...@inaugust.com]
Sent: Friday, August 4, 2017 9:53 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [python-openstacksdk] Status of
python-openstacksdk project
Conclusion
--
As I mentioned at the top, I'd
rage-quit
On Fri, Aug 4, 2017 at 11:52 AM, Monty Taylor wrote:
> On 08/04/2017 03:24 AM, Thierry Carrez wrote:
>
>> Michael Johnson wrote:
>>
>>> I was wondering what is the current status of the python-openstacksdk
>>> project. The Octavia team has posted some patches implementing our new
>>>
On 08/04/2017 03:24 AM, Thierry Carrez wrote:
Michael Johnson wrote:
I was wondering what is the current status of the python-openstacksdk
project. The Octavia team has posted some patches implementing our new
Octavia v2 API [1] in the SDK, but we have not had any reviews. I have also
asked so
Michael Johnson wrote:
> I was wondering what is the current status of the python-openstacksdk
> project. The Octavia team has posted some patches implementing our new
> Octavia v2 API [1] in the SDK, but we have not had any reviews. I have also
> asked some questions in #openstack-sdks with no r
12 matches
Mail list logo
