Re: [openstack-dev] [Fuel] Power management in Cobbler

2014-11-19 Thread Vladimir Kozhukalov
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.

Vladimir Kozhukalov

On Wed, Nov 5, 2014 at 7:28 PM, Vladimir Kuklin vkuk...@mirantis.com
wrote:

 I am +1 for using cobbler as power management before we merge Ironic-based
 stuff. It is essential part also for our HA and stop
 provisioning/deployment mechanism.

 On Tue, Nov 4, 2014 at 1:00 PM, Dmitriy Shulyak dshul...@mirantis.com
 wrote:

 Not long time ago we discussed necessity of power management feature in
 Fuel.

 What is your opinion on power management support in Cobbler, i took a
 look at documentation [1] and templates [2] that  we have right now.
 And it actually looks like we can make use of it.

 The only issue is that power address that cobbler system is configured
 with is wrong.
 Because provisioning serializer uses one reported by boostrap, but it can
 be easily fixed.

 Ofcourse another question is separate network for power management, but
 we can leave with
 admin for now.

 Please share your opinions on this matter. Thanks

 [1] http://www.cobblerd.org/manuals/2.6.0/4/5_-_Power_Management.html
 [2] http://paste.openstack.org/show/129063/

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




 --
 Yours Faithfully,
 Vladimir Kuklin,
 Fuel Library Tech Lead,
 Mirantis, Inc.
 +7 (495) 640-49-04
 +7 (926) 702-39-68
 Skype kuklinvv
 45bk3, Vorontsovskaya Str.
 Moscow, Russia,
 www.mirantis.com http://www.mirantis.ru/
 www.mirantis.ru
 vkuk...@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


Re: [openstack-dev] [Fuel] Power management in Cobbler

2014-11-19 Thread Tomasz Napierala

 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


Re: [openstack-dev] [Fuel] Power management in Cobbler

2014-11-19 Thread Matthew Mosesohn
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


Re: [openstack-dev] [Fuel] Power management in Cobbler

2014-11-19 Thread Fox, Kevin M
Would net booting a minimal discovery image work? You usually can dump ipmi 
network information from the host.

Thanks,
Kevin

From: Matthew Mosesohn [mmoses...@mirantis.com]
Sent: Wednesday, November 19, 2014 7:46 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Bogdan Dobrelya
Subject: Re: [openstack-dev] [Fuel] Power management in Cobbler

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

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


Re: [openstack-dev] [Fuel] Power management in Cobbler

2014-11-19 Thread Tomasz Napierala

 On 19 Nov 2014, at 17:56, Fox, Kevin M kevin@pnnl.gov wrote:
 
 Would net booting a minimal discovery image work? You usually can dump ipmi 
 network information from the host.
 

To boot from minimal iso (which is waht we do now) you still need to tell the 
host to do it. This is where IPMI discovery is needed I guess.

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


Re: [openstack-dev] [Fuel] Power management in Cobbler

2014-11-19 Thread Fox, Kevin M
I meant, either go into the bios and set the node to netboot, or hit f12(or 
whatever) and netboot. the netbooted discovery image should be able to gather 
all the rest of the bits? Minimal ISO could also be just gpxe or something like 
that and would do the same as above. Then you don't have to update the iso 
every time you enhance discovery process too.

Hmmm... Some bmc's do dhcp though out of the box. I guess if you watched for 
dhcp leases and then tried to contact them over ipmi with a few default 
username/passwords, you'd probably get a fair number of them without much 
effort, if they are preconfigured.

In our experience though, we usually get nodes in that we have to configure 
netboot in the bios, then the next easiest step is to install and then 
configure the bmc via the installed linux. You can manually setup the bmc 
username/password/ip/whatever but its work. Most of the bmc's we've seen have 
ipmi over the network disabled by default. :/ So in that case, the former, 
netboot the box, load a discovery image, and have it configure the bmc all in 
one go would be nicer I think.

Thanks,
Kevin

From: Tomasz Napierala [tnapier...@mirantis.com]
Sent: Wednesday, November 19, 2014 9:28 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Bogdan Dobrelya
Subject: Re: [openstack-dev] [Fuel] Power management in Cobbler

 On 19 Nov 2014, at 17:56, Fox, Kevin M kevin@pnnl.gov wrote:

 Would net booting a minimal discovery image work? You usually can dump ipmi 
 network information from the host.


To boot from minimal iso (which is waht we do now) you still need to tell the 
host to do it. This is where IPMI discovery is needed I guess.

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


Re: [openstack-dev] [Fuel] Power management in Cobbler

2014-11-05 Thread Vladimir Kuklin
I am +1 for using cobbler as power management before we merge Ironic-based
stuff. It is essential part also for our HA and stop
provisioning/deployment mechanism.

On Tue, Nov 4, 2014 at 1:00 PM, Dmitriy Shulyak dshul...@mirantis.com
wrote:

 Not long time ago we discussed necessity of power management feature in
 Fuel.

 What is your opinion on power management support in Cobbler, i took a look
 at documentation [1] and templates [2] that  we have right now.
 And it actually looks like we can make use of it.

 The only issue is that power address that cobbler system is configured
 with is wrong.
 Because provisioning serializer uses one reported by boostrap, but it can
 be easily fixed.

 Ofcourse another question is separate network for power management, but we
 can leave with
 admin for now.

 Please share your opinions on this matter. Thanks

 [1] http://www.cobblerd.org/manuals/2.6.0/4/5_-_Power_Management.html
 [2] http://paste.openstack.org/show/129063/

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




-- 
Yours Faithfully,
Vladimir Kuklin,
Fuel Library Tech Lead,
Mirantis, Inc.
+7 (495) 640-49-04
+7 (926) 702-39-68
Skype kuklinvv
45bk3, Vorontsovskaya Str.
Moscow, Russia,
www.mirantis.com http://www.mirantis.ru/
www.mirantis.ru
vkuk...@mirantis.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev