Woops, meant to respond to this in the email I just sent...
On Aug 21, 2014 11:35 PM, "Steve Kowalik" wrote:
>
> For other drivers, we think that the pm_address for each machine
will be unique. Would it be possible add some advice to that effect to
Ironic's driver API?
>
pm_address is cr
On Aug 22, 2014 12:48 AM, "Steve Kowalik" wrote:
>
> On 22/08/14 17:35, Chris Jones wrote:
>>
>> Hi
>>
>> When register-nodes blows up, is the error we get from Ironic
sufficiently unique that we can just consume it and move on?
>>
You should get a clear error when attempting to add a port with a
Excerpts from Steve Kowalik's message of 2014-08-22 06:32:04 +:
> At the moment, if you run register-nodes a second time with the same
> list of nodes, it will happily try and register them and then blow up
> when Ironic or Nova-bm returns an error. If operators are going to
> update the
Hi
Nice, sounds like a very good thing from an operator's perspective.
Cheers,
--
Chris Jones
> On 22 Aug 2014, at 08:44, Steve Kowalik wrote:
>
>> On 22/08/14 17:35, Chris Jones wrote:
>> Hi
>>
>> When register-nodes blows up, is the error we get from Ironic sufficiently
>> unique that we
On 22/08/14 17:35, Chris Jones wrote:
Hi
When register-nodes blows up, is the error we get from Ironic sufficiently
unique that we can just consume it and move on?
I'm all for making the API more powerful wrt inspecting the current setup, but
I also like idempotency :)
If the master nodes l
Hi
When register-nodes blows up, is the error we get from Ironic sufficiently
unique that we can just consume it and move on?
I'm all for making the API more powerful wrt inspecting the current setup, but
I also like idempotency :)
Cheers,
--
Chris Jones
> On 22 Aug 2014, at 07:32, Steve Kowa
Hi,
TripleO has a bridging script we use to register nodes with a baremetal
service (eg: Ironic or Nova-bm), called "register-nodes", which given a
list of node descriptions (in JSON), will register them with the
appropriate baremetal service.
At the moment, if you run register-nodes a sec
