John-Paul, Sorry I missed chiming in on your original email. We've working in OpenCrowbar to address some of these issues - the website uses more standard Rails 4 / Ruby 2 configuration with a standard Postgresql database. More importantly, we're enabling Berkshelf support to make it easy to use upstream cookbooks. The OpenCrowbar attribute injection approach does not require customization of the cookbooks if you are using the attribute pattern. Also, because of the way we use Chef-solo, the updated cookbooks can be immediately updated in place. Lastly, we've been working towards upgrades of both Crowbar and the workloads. These are primary focus points for us. Here's some more information: http://robhirschfeld.com/2014/03/17/opencrowbar-reaches-critical-milestone-boot-discover-and-forge-on/ Rob
> -----Original Message----- > From: crowbar-bounces On Behalf Of John-Paul Robinson > Sent: Thursday, March 20, 2014 4:30 PM > To: Adam Spiers; crowbar > Subject: Re: [Crowbar] hooking into a crBaowbar-instantiated chef > server > > Nice to hear what SUSE's been up too. I'll put that in my thinking cap. > > So in the Crowbar interface I have (Dell branded) I don't see an > interface to monkey with the actual settings like http vs https via > the web UI. Is there a backend API that I should be learning about to > pull and push barclamps into and get updated behavior from my nodes? > > The existing user docs seem to focus on navigating the web ui to > provision nodes and the dev docs are more focused on building the iso > than post- provisioned config tuning. > > Some insight on the best practices in the 1.x world or a pointer to > the doc/concept I'm overlooking would help. > > Thanks, > > ~jpr > > On 03/20/2014 07:08 AM, Adam Spiers wrote: > > John-Paul Robinson (j...@uab.edu) wrote: > >> On 03/18/2014 09:34 PM, Keith Hudgins wrote: > >> As a first step, I'm not as interested in add new packages to the > >> nodes (that's coming) but more interested in how tune/update the > >> behavior of an install service, eg. switch OpenStack to using HTTPS > >> instead > of HTTP. > > Actually HTTPS is more or less just simple clicks of the mouse in > > the barclamp proposal options - or at least it is in the SUSE Cloud > > version of Crowbar, and IIRC in all recent Crowbar 1.x releases too. > > I'm not sure about 2.x. > > > >> In general, the assumption for the engage-with-crowbar approach > >> seems to be "build an an iso and deploy" > > Last time I checked, that was the Dell approach. The SUSE approach > > has been quite different for the last couple of years - we build > > packages which are then layered on top of a standard OS installation. > > Having said that, I believe Dell may also be moving to a more > > package-oriented approach, but I don't know the status of that. > > > >> I know there isn't an defined upgrade path in crowbar. > > Actually there is in SUSE Cloud ;-) > > > > _______________________________________________ > > Crowbar mailing list > > Crowbar@dell.com > > https://lists.us.dell.com/mailman/listinfo/crowbar > > For more information: http://crowbar.github.com/ > > _______________________________________________ > Crowbar mailing list > Crowbar@dell.com > https://lists.us.dell.com/mailman/listinfo/crowbar > For more information: http://crowbar.github.com/
_______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
