we use it to do manage 2 environments (test and live). Within that we add config for each node (app server, db, web server) and then use puppet to manage all the dependencies (s/w and refs to each other) as well as URL handling etc etc.
The, here, is that adding a node is a matter of adding to ec2, installing puppet on it amend puppet config and then refreshing each node to a) tell them about the new node and b) get the new node to install all the requisite s/w onto itself. Its great for ensuring all the nodes are consistent. I would say the learnig curve is quite steep; i inherited the initial setup so had a basis to learn. Now i've got a handle in it, its great. On 23 February 2011 22:19, Jesse Tayler <jtay...@oeinc.com> wrote: > > On Feb 23, 2011, at 5:14 PM, Martin Samm wrote: > > > We then use Puppet to automate installing an array of required packages > etc. > > oh? > > got scripts or examples? > > sounds like an approach we might want to document > > the examples we have require just a few dependancies - is Puppet good for a > larger docket or good for revision control? > > > -- Martin Samm Aetopia Ltd +44 (0) 28 9099 8767 ____________________________________________________________________________ Aetopia Ltd is a limited company registered in Belfast, Northern Ireland, with registration number NI053321, having its principal place of business (and postal address) at ECIT Institute, Queens Road, BELFAST BT3 9DT and registered office at 1, Lanyon Quay, BELFAST BT1 3LG
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
