On 5/15/2016 7:42 PM, Jason Kölker wrote:
On Sun, May 15, 2016 at 3:56 PM, Sean M. Collins wrote:
Matt Riedemann wrote:
The nova create-server API allows passing a network id that's prefixed with
br- [1]. That was added due to this bug from Folsom [2].
I'm wondering if
On Sun, May 15, 2016 at 3:56 PM, Sean M. Collins wrote:
> Matt Riedemann wrote:
>> The nova create-server API allows passing a network id that's prefixed with
>> br- [1]. That was added due to this bug from Folsom [2].
>>
>> I'm wondering if that's still valid? Looking at the
> On May 15, 2016, at 10:17 AM, Matt Riedemann
> wrote:
>
>> On 5/15/2016 10:56 AM, Sean M. Collins wrote:
>> Matt Riedemann wrote:
>>> The nova create-server API allows passing a network id that's prefixed with
>>> br- [1]. That was added due to this bug from
On 5/15/2016 10:56 AM, Sean M. Collins wrote:
Matt Riedemann wrote:
The nova create-server API allows passing a network id that's prefixed with
br- [1]. That was added due to this bug from Folsom [2].
I'm wondering if that's still valid? Looking at the network.id data model in
Neutron it
Matt Riedemann wrote:
> The nova create-server API allows passing a network id that's prefixed with
> br- [1]. That was added due to this bug from Folsom [2].
>
> I'm wondering if that's still valid? Looking at the network.id data model in
> Neutron it doesn't look like it would be [3].
Wow.
The nova create-server API allows passing a network id that's prefixed
with br- [1]. That was added due to this bug from Folsom [2].
I'm wondering if that's still valid? Looking at the network.id data
model in Neutron it doesn't look like it would be [3].
I'm trying to sort this out for the