> Mike
>
> From: Denis Egorenko
> Reply-To: "OpenStack Development Mailing List (not for usage
> questions)"
> Date: Thursday, December 31, 2015 at 5:59 AM
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Subject: Re: [openstack-dev]
5:59 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [puppet] [neutron] Serious bug in puppet neutron
cli json output parsing.
Last I checked, which was quite a while ago, openstackcli
Denis Egorenko writes:
> Last I checked, which was quite a while ago, openstackclient didn't
> support everything we were using from the neutron client.
>
> That's true. Openstack client doesn't support all features of neutron
> client [1].
What I had in mind was more like using the same
>
> Last I checked, which was quite a while ago, openstackclient didn't
> support everything we were using from the neutron client.
That's true. Openstack client doesn't support all features of neutron
client [1].
I would prefer use 3) option, but, unfortunately, i also don't see way, how
to det
On Wed, Dec 30, 2015 at 8:37 AM, Sofer Athlan-Guyot
wrote:
> Hi,
>
> I have added neutron people as they may help to find a solution.
>
> After banging my head against the wall for a whole afternoon I
> discovered a serious bug in puppet neutron module.
>
> I not going to repeat here the detail o
Hi,
I have added neutron people as they may help to find a solution.
After banging my head against the wall for a whole afternoon I
discovered a serious bug in puppet neutron module.
I not going to repeat here the detail of the bug report[1]. Basically:
- neutron_port
- neutron_subnet
- neut
