Few weeks ago I started to look for a solution on this one (actually baremetal provisioning) and did some comparision here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Baremetal#CloudStackBaremetal-ImagebasedprovisioningforBaremetal
If anyone wants to take over, update the table and let's discuss on possible and appropriate solutions in CloudStack. Regards. ________________________________________ From: Prasanna Santhanam [[email protected]] Sent: Tuesday, October 23, 2012 9:36 PM To: [email protected] Subject: Re: [Discussion]Auto provision of hosts(hypervisors) into cloud using auto discovery mechanism from the specified IP address range On Tue, Oct 23, 2012 at 12:00:18PM -0400, John Burwell wrote: > David, > > Why not expose an API that would allow Cobbler, Foreman, Razor, etc > to call into CloudStack at the appropriate times? The current REST > API may even be sufficient. Speaking with experience using both > Cobbler and Foreman, they work better when they are coordinating the > provisioning activities rather than being embedded into another > system. It also avoid any licensing issues, and allows customers > to chose the tools that most appropriately fits their environment. > Yup - Foreman comes to mind since it plays well with puppet too during post-install. As a seperate appliance per pod would be best, an image that configures - cobbler/foreman/$your_fav_system as per your physical infrastructure with the admin's REST api of CloudStack. -- Prasanna.,
