John-Paul Robinson (j...@uab.edu) wrote: > Rob, thanks for the insight on the future direction. > > What I really want is some clarification on how to best address these > issues in the context of an existing Crowbar 1.5 install. I'm > comfortable getting my hands dirty and retro-fitting capabilities. I > need some guidance on how to approach the retrofit. > > Let's go with a specific example: > > I want to convert my Dashboard to use HTTPS instead of HTTP. This will > involve changing the port number, adding some SSL configuration, and > ultimately having Dashboard respond with a hostname instead of IP for > any any redirects (not strictly part of HTTPS but needed to get services > exposed beyond firewalls). > > Where does one make this change, dig around in Crowbar or work > exclusively with Chef?
This is exactly the kind of setting for which Crowbar and Chef are intended to do all the hard work for you, so that it's as simple as choosing the right option in the GUI. Here's a screenshot from the keystone barclamp in SUSE Cloud; hopefully that will help you locate it in your installation: http://adamspiers.org/computing/SUSE/SUSE-cloud-keystone-HTTPS.png Of course, using SSL has a knock-on effect for all the other barclamps, which is why it makes sense for Crowbar/Chef to take care of this rather than expecting cloud operators to have to tweak stuff manually. _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
