--- aeolusproject.org/content/cleaning_up.haml | 2 + aeolusproject.org/content/start_image.haml | 66 +++++++++------------------- aeolusproject.org/content/stop_image.haml | 29 ++++++------ 3 files changed, 37 insertions(+), 60 deletions(-)
diff --git a/aeolusproject.org/content/cleaning_up.haml b/aeolusproject.org/content/cleaning_up.haml index d798e7e..9e3ebbe 100644 --- a/aeolusproject.org/content/cleaning_up.haml +++ b/aeolusproject.org/content/cleaning_up.haml @@ -74,6 +74,8 @@ Useful things to know when using development versions of Aeolus. Conductor related data. Don't use it on a server whose data you want to keep.
+ %p + If you are using Amazon EC2, follow the next steps to complete the cleanup. %br
.section-grouping diff --git a/aeolusproject.org/content/start_image.haml b/aeolusproject.org/content/start_image.haml index 43bf71c..c1a7296 100644 --- a/aeolusproject.org/content/start_image.haml +++ b/aeolusproject.org/content/start_image.haml @@ -7,12 +7,12 @@ filter: haml %h1 Start an Instance of the Image
%p - With the image as an AMI in the Amazon Cloud, you can start instances + With the image as an AMI in your provider account, you can start instances when desired.
%p We'll take you through starting an instance of the image using Aeolus's - web interface, then show you how to connect to that image remotely using + web interface. Then, if you're using Amazon EC2, we'll show you how to connect to that image remotely using SSH.
.page-listing @@ -53,10 +53,10 @@ filter: haml %br
.section-grouping - %h2 1. Launch a deployable + %h2 1. Create a Catalog and Deployable
%p - On your Aeolus server create a file accessible in your web root with the following content. + Create a deployable XML file with the following content. Use the image id generated when you pushed the built image in the previous step.
%pre :escaped @@ -73,7 +73,18 @@ filter: haml %ol %li In the Aeolus web interface, go to the - %b MONITOR + %b Administer + ⇒ <b>Content</b>. + + %li + Click the "New Catalog" button. Give your catalog a name, associate it with the Default pool, and save it. + + %li + Click on the name of your new catalog. Click on the "New Catalog Entry" button. Give your entry a name, description, and upload the deployable XML file you created. Save your new catalog entry. + + %li + In the Aeolus web interface, go to the + %b Monitor tab. %br Under "Your Pools" is the default pool. On the right side @@ -90,56 +101,21 @@ filter: haml %br
%li - Give your deployment a name and enter the url to the deployable xml file you - just created. - - %br - %center - %a{ :href => "images/getting_started/new_deployment_details.png", - :target => "_blank" } - %img.thumbnail{ :src => "images/getting_started/thumbnails/new_deployment_details_thumb.png", - :title => "New Deployment - click to view at full size in a new window", - :alt => "New Deployment - click to view at full size in a new window" } - %br - - %li + Give your deployment a name and select the deployable you just created. Click the %b Next button.
%li - To launch the deployment click the "Launch this deployment" button. - - %br - %center - %a{ :href => "images/getting_started/launch_deployment.png", - :target => "_blank" } - %img.thumbnail{ :src => "images/getting_started/thumbnails/launch_deployment_thumb.png", - :title => "Launch Deployment - click to view at full size in a new window", - :alt => "Launch Deployment - click to view at full size in a new window" } - %br - + To launch the deployment click the "Launch" button. %p Aeolus will then launch an instance of the template, using the AMI - created on the previous page. - %p - The main view will list your instances, with the message - "<em>Deployment launched.</em>" near the top: - - %p - - %center - %a{ :href => "images/getting_started/instance_added.png", - :target => "_blank" } - %img.thumbnail{ :src => "images/getting_started/thumbnails/instance_added_thumb.png", - :title => "Instance 1 added", - :alt => "Instance 1 added" } - - %p - Within a minute or two, the + created on the previous page. Within a minute or two, the %b State field for the instance should change to "<em>running</em>".
+ %p + If you are using Amazon EC2, follow the next steps to complete your configuration. %br
.section-grouping diff --git a/aeolusproject.org/content/stop_image.haml b/aeolusproject.org/content/stop_image.haml index 7f742ae..4de4a49 100644 --- a/aeolusproject.org/content/stop_image.haml +++ b/aeolusproject.org/content/stop_image.haml @@ -50,19 +50,6 @@ filter: haml Shutting down a running instance is very simple.
%p - %ol - %li - On the same screen the ssh key and public address were available - switch to the grid view by clicking the grid button on the right - side of the page. - - %li - Tick the checkbox next to the instance name in the instance list. - - %li - Click the "Stop Selected Instances" button: - - %p %center %a{ :href => "images/getting_started/aeolus_stop_instance_button.png", @@ -72,8 +59,18 @@ filter: haml :alt => "Shutting down the instance - click to view at full size in a new window" }
%p - Within a minute or two the instance status should change to say - <em>stopped</em>: + %ol + %li + In the Aeolus web interface, click the + %b MONITOR + tab and select the grid view by clicking the grid button on the right side of the page. + + + %li + Click on "Instances" to view your running instances. Tick the checkbox next to the instance name in the instance list. + + %li + Click the "Stop selected instances" button. Within a minute or two the instance status should change to say <em>stopped</em>:
%p @@ -84,6 +81,8 @@ filter: haml :title => "Instance has stopped - click to view at full size in a new window", :alt => "Instance has stopped - click to view at full size in a new window" }
+ %p + If you are using Amazon EC2, follow the next step to check for instances running in EC2. %br
.section-grouping