As someone who also thinks Ruby but types Perl, I can relate. Crowbar 1.x's use case is founded upon having complete control over the LAN. Effort to shoehorn it will be friendly and interesting, but hacking on code we plan to move away from.
Crowbar 2 is a major refactor. The tools available to us have changed much in the two years since Crowbar 1's inception. I warmly invite you to keep contributing use cases to this list, and even attend our weekly design review meetings. http://crowbar.github.io/docs/getting-help.html We should drop a link to the calendar there.. but you can also find it on the wiki. Use cases of a PXE/DHCP-free environment are very interesting to us. -judd On Tue, May 21, 2013 at 3:55 PM, Timothy Rees <[email protected]> wrote: > Hi Rob, > > We have security policies that forbid the use of both DHCP/PXE in segments > of our datacenters. In order to have a unified deployment process, we would > have to achieve it without either. > > The iDRAC/LC can be leveraged to mount a boot iso, however things such as IP > assignment for the host would then need to be included on the mounted imaged > for the specific host. In our use case then the boot can pull a kickstart > from a Satellite node and then deploy to the host. > > I wouldn't have thought this acquirement would be unique to us. Could it > possibly be considered/written into the 2.0 release? If it is a desired > feature I would be happy to work on it. > > @Adam - Apologies, I was thinking Ruby but somehow typed Perl. > > Regards, > Tim > > > > On 21 May 2013 20:58, <[email protected]> wrote: >> >> Tim, >> >> This has been discussed - it's tricky in CB 1.x because we rely on the >> PXE/DHCP discovery to register nodes in Chef for management. >> >> Question -> is your concern more about DHCP or PXE? DHCP helps w/ >> discovery and proving the sledgehammer inventory image. PXE is how >> sledgehammer and the install image are delivered. iDRAC could be used to >> bypass either or both, but it changes your use case. >> >> In CB 2.x work, we have more options on how to populate and manage nodes. >> >> Rob >> >> From: crowbar-bounces On Behalf Of Timothy Rees >> Sent: Tuesday, May 21, 2013 10:24 AM >> To: crowbar >> Subject: [Crowbar] Crowbar for non-PXE deployments >> >> Hi, >> >> This project recently came to my attention when I was looking for a >> generic application that could be used to push OS deployments to Dell >> PowerEdge bare-metal without the requirement of PXE. However, of course I >> now see that this project depends depends on PXE and it was originally >> intended to push a complete cloud environment, not just one off OS >> deployments. >> >> My question is, could the work to incorporate deployments using the >> PowerEdge Lifecycle controller (wsman) be incorporated into this project and >> if so, would that be of interest? Back to my specific use case, we've >> already got management systems such as SCCM/Satellite that can manage the OS >> through its lifecycle once it has been deployed, we're only looking for a >> single deployment tool that can be used without the requirement for PXE. >> >> Although I have more of a python background, I would be happy to try and >> port to Perl and contribute if this is something that would be seen to add >> value to crowbar. I see in the recent youtube video for 2.0 that >> 'Heterogeneous OS deployment' was an agenda item. >> >> Regards, >> Tim > > > > _______________________________________________ > Crowbar mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/crowbar > For more information: http://crowbar.github.com/ -- Judd Maltin T: 917-882-1270 F: 501-694-7809 what could possibly go wrong? _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
