the-maestro 0.3.7 → 0.3.8

Sign up to get free protection for your applications and to get access to all the features.
Files changed (4) hide show
  1. data/README.rdoc +63 -4
  2. data/VERSION +1 -1
  3. data/the-maestro.gemspec +2 -2
  4. metadata +2 -2
data/README.rdoc CHANGED
@@ -22,7 +22,7 @@ Add the following gem dependency to your Rails project's <code>config/environmen
22
22
 
23
23
  Rails::Initializer.run do |config|
24
24
 
25
- config.gem "the-maestro", :lib => "maestro", :version => "0.3.7", :source => "http://gemcutter.org"
25
+ config.gem "the-maestro", :lib => "maestro", :version => "0.3.8", :source => "http://gemcutter.org"
26
26
 
27
27
  end
28
28
 
@@ -38,7 +38,7 @@ You'll interact with Maestro through custom Rake tasks that Maestro adds to your
38
38
 
39
39
  require 'maestro/tasks'
40
40
 
41
- Make sure the Maestro gem in successfully installed before adding this line to your Rails project's Rakefile.
41
+ Make sure the Maestro gem is successfully installed before adding this line to your Rails project's Rakefile.
42
42
 
43
43
  === Configuration
44
44
 
@@ -346,11 +346,70 @@ Node-specific messages are not logged to STDOUT, but only to the node's log file
346
346
  consult the individual node log files for information.
347
347
 
348
348
 
349
- == Using Maestro with a stand alone Ruby application
349
+ == Using Maestro stand alone
350
+
351
+ Maestro can also be used in stand alone mode, as a simple command line cloud management utility.
352
+
353
+
354
+ === Installation
355
+
356
+ Install the Maestro gem by running the following command:
350
357
 
351
358
  sudo gem install the-maestro
352
359
 
353
- TODO...
360
+ === Requirements
361
+
362
+ Maestro requires the following in order to be run in stand alone mode:
363
+
364
+ - A base directory structure
365
+ - An environment variable <code>MAESTRO_DIR</code> set to the location of the base directory
366
+ - A Rake file
367
+
368
+ ==== Create the base directory structure
369
+
370
+ Maestro requires a directory representing your project. This directory will house your Rake file, and a subdirectory named "config" where all of your Maestro configuration files will live.
371
+
372
+ For example, suppose we are running a Hadoop cluster in the cloud. We would create the following directory structure:
373
+
374
+ mkdir /home/bob/projects/hadoop-cluster
375
+ mkdir /home/bob/projects/hadoop-cluster/config
376
+
377
+ ==== Set the <code>MAESTRO_DIR</code> environment variable
378
+
379
+ When run in stand alone mode, Maestro requires that an environment variable named <code>MAESTRO_DIR</code> be set, pointing at the base directory defined above.
380
+ The mechanism for setting environment variables is operating system and/or shell specific, but as an example:
381
+
382
+ export MAESTRO_DIR="/home/bob/projects/hadoop-cluster"
383
+
384
+ Please note that if you wish to use Maestro with multiple stand alone projects, you may want to set the <code>MAESTRO_DIR</code> environment variable in shell/batch scripts.
385
+
386
+ ==== Create a Rakefile
387
+
388
+ You'll interact with Maestro through Rake tasks. Create a Rakefile in your base directory, and add the following:
389
+
390
+ require 'rubygems'
391
+ require 'rake'
392
+ require 'maestro/tasks'
393
+
394
+ Make sure the Maestro gem is successfully installed before adding these lines to your Rakefile.
395
+
396
+ ==== Create the Maestro configuration directory structure
397
+
398
+ To create the Maestro configuration directory structure, run the following Rake task within the base directory containing your Rake file:
399
+
400
+ rake maestro:create_config_dirs
401
+
402
+ This will create the following directory structure within your project's config/ directory:
403
+
404
+ $MAESTRO_DIR/config/maestro/clouds/ - the directory which contains your cloud configuration files
405
+ $MAESTRO_DIR/config/maestro/cookbooks/ - the directory which contains your Chef cookbooks
406
+ $MAESTRO_DIR/config/maestro/roles/ - the directory which contains your Chef JSON Roles files
407
+
408
+ If these directories already exist when running <code>rake maestro:create_config_dirs</code>, no action is taken.
409
+
410
+ === Conduct!
411
+
412
+ At this point, you can use Maestro as described above. Define your clouds, create your Chef assets, and conduct!
354
413
 
355
414
 
356
415
  == Where To Get Help
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.3.7
1
+ 0.3.8
data/the-maestro.gemspec CHANGED
@@ -5,11 +5,11 @@
5
5
 
6
6
  Gem::Specification.new do |s|
7
7
  s.name = %q{the-maestro}
8
- s.version = "0.3.7"
8
+ s.version = "0.3.8"
9
9
 
10
10
  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
11
11
  s.authors = ["Brian Ploetz"]
12
- s.date = %q{2010-06-29}
12
+ s.date = %q{2010-08-01}
13
13
  s.description = %q{Maestro is a cloud provisioning, configuration, and management utility for your Ruby and Ruby On Rails applications.}
14
14
  s.extra_rdoc_files = [
15
15
  "LICENSE",
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: the-maestro
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.3.7
4
+ version: 0.3.8
5
5
  platform: ruby
6
6
  authors:
7
7
  - Brian Ploetz
@@ -9,7 +9,7 @@ autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
11
 
12
- date: 2010-06-29 00:00:00 -04:00
12
+ date: 2010-08-01 00:00:00 -04:00
13
13
  default_executable:
14
14
  dependencies:
15
15
  - !ruby/object:Gem::Dependency