Hi folks! I messed around with using boxgrinder and the new rpm repository to build MH v-boxen. I don't have any trouble grinding out images, and I'm tossing puppet and whatnot into the mix as well, so managing configurations after grinding is easy, etc.. (I'll post the recipes on github as I iron them out- eventually add openstack y todo, probably).
I'm just wondering how the different profiles will work from a binary installation perspective. I'm not sure how they work in general, to be honest. Is it mostly a matter of turning on and off bundles in felix and adjusting corresponding service URLs? I generate an internal RPM repository as part of my CI stuff, and I'm just wondering if it is best to have everything in one package, or to break stuff up somehow (admin, worker, engage, capture?). How are people envisioning the binary installation experience? How are people handling binary installation currently? :Denny -- I cannot give you the formula for success, but I can give you the formula for failure--which is: Try to please everybody. Herbert Bayard Swope _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
