Tomasz, Vladimir, others,

The way I see it is we need a way to discover the corresponding IPMI
address for a given node for out-of-band power management. The
ultimate ipmitool command is going to be exactly the same whether it
comes from Cobbler or Ironic, and all we need to do is feed
information to the appropriate utility when it comes to power
management. If it's the same command, it doesn't matter who does it.
Ironic of course is a better option, but I'm not sure where we are
with discovering ipmi IP addresses or prompting admins to enter this
data for every node. Without this step, neither Cobbler nor Ironic is
capable of handling this task.

Best Regards,
Matthew Mosesohn

On Wed, Nov 19, 2014 at 7:38 PM, Tomasz Napierala
<tnapier...@mirantis.com> wrote:
>
>> On 19 Nov 2014, at 16:10, Vladimir Kozhukalov <vkozhuka...@mirantis.com> 
>> wrote:
>>
>> I am absolutely -1 for using Cobbler for that. Lastly, Ironic guys became 
>> much more open for adopting new features (at least if they are implemented 
>> in terms of Ironic drivers). Currently, it looks like we are  probably able 
>> to deliver zero step Fuel Ironic driver by 6.1. Ironic already has working 
>> IPMI stuff and they don't oppose ssh based power management any more. 
>> Personally, I'd prefer to focus our efforts towards  Ironic stuff and 
>> keeping in mind that Cobbler will be removed in the nearest future.
>
> I know that due to time constraints we would be better to go with Cobbler, 
> but I also think we should be closer to the community and switch to Ironic as 
> soon as possible.
>
> Regards,
> --
> Tomasz 'Zen' Napierala
> Sr. OpenStack Engineer
> tnapier...@mirantis.com
>
>
>
>
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to