On 26 July 2016 at 10:52, Sam Betts (sambetts) wrote:
> On 26/07/2016 09:32, "John Garbutt" wrote:
>
>>On 22 July 2016 at 11:51, Vasyl Saienko wrote:
>>> Kevin, thanks for reply,
>>>
>>> On Fri, Jul 22, 2016 at 11:50 AM, Kevin Benton wrote:
Hi,
Once you solve the issue of ge
On 26/07/2016 09:32, "John Garbutt" wrote:
>On 22 July 2016 at 11:51, Vasyl Saienko wrote:
>> Kevin, thanks for reply,
>>
>> On Fri, Jul 22, 2016 at 11:50 AM, Kevin Benton wrote:
>>>
>>> Hi,
>>>
>>> Once you solve the issue of getting the baremetal ports to transition
>>>to
>>> the ACTIVE sta
On 22 July 2016 at 11:51, Vasyl Saienko wrote:
> Kevin, thanks for reply,
>
> On Fri, Jul 22, 2016 at 11:50 AM, Kevin Benton wrote:
>>
>> Hi,
>>
>> Once you solve the issue of getting the baremetal ports to transition to
>> the ACTIVE state, a notification will automatically be emitted to Nova of
Kevin, thanks for reply,
On Fri, Jul 22, 2016 at 11:50 AM, Kevin Benton wrote:
> Hi,
>
> Once you solve the issue of getting the baremetal ports to transition to
> the ACTIVE state, a notification will automatically be emitted to Nova of
> 'network-vif-plugged' with the port ID. Will ironic not
Hi,
Once you solve the issue of getting the baremetal ports to transition to
the ACTIVE state, a notification will automatically be emitted to Nova of
'network-vif-plugged' with the port ID. Will ironic not have access to that
event via Nova?
If not, Ironic could develop a service plugin that jus
Hello Community,
I'm working to make Ironic be aware about Neutron port state changes [0].
The issue consists of two parts:
- Neutron ports for baremetal instances remain in DOWN state [1]. The
issue occurs because there is no mechanism driver that binds ports. To
solve it we need to cr
