Sadly, this doesn't always work.
On Fri, Nov 22, 2013 at 10:55 PM, Gangur, Hrushikesh (R & D HP Cloud) < [email protected]> wrote: > bluepill status > > > > bluepill chef-server stop > > > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Shane Gibson > *Sent:* Friday, November 22, 2013 2:40 PM > *To:* [email protected] > *Subject:* [Crowbar] how to shutdown bluepill/chef ? > > > > > > Does anyone out there have a “correct” procedure on how to completely > disable chef-server/chef-client on a Crowbar built cluster? We want to > “freeze” the config on a cluster, and make significant changes (installing > plugins, etc…) without Chef interfering with the changes. > > > > I realize that once we’re done we can’t safely return control back to the > Chef services, so effectively, we’d be shutting down chef. I know that > “chef-client” is under bluepill control, and I didn’t have much success > “shutting it off” last time I tried. > > > > Any pointers/suggestions would be greatly appreciated. Thanks! > > > > ~~shane > > > > > > _______________________________________________ > 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/
