Author: buildbot
Date: Mon Jul 14 02:18:05 2014
New Revision: 916126
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/jclouds.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/jclouds.html
==============================================================================
--- websites/production/camel/content/jclouds.html (original)
+++ websites/production/camel/content/jclouds.html Mon Jul 14 02:18:05 2014
@@ -86,37 +86,16 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2
id="jclouds-JcloudsComponent">Jclouds Component</h2>
-
-<p><strong>Available as of Camel 2.9</strong></p>
-
-<p>This component allows interaction with cloud provider key-value engines
(blobstores) and compute services. The component uses <a shape="rect"
class="external-link" href="http://code.google.com/p/jclouds";
rel="nofollow">jclouds</a> which is<br clear="none">
-a library that provides abstractions for blobstores and compute services.</p>
-
-<p><strong>ComputeService</strong> simplifies the task of managing machines in
the cloud. For example, you can use ComputeService to start 5 machines and
install your software on them.<br clear="none">
-<strong>BlobStore</strong> simplifies dealing with key-value providers such as
Amazon S3. For example, BlobStore can give you a simple Map view of a
container.</p>
-
-<p>The camel jclouds component allows you to use both abstractions, as it
specifes two types of endpoint the JcloudsBlobStoreEndpoint and the
JcloudsComputeEndpoint. You can have both producers and consumers on a
blobstore endpoint but you can only have producers on compute endpoints.</p>
-
-<p>Maven users will need to add the following dependency to their
<code>pom.xml</code> for this component:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<dependency>
+<div class="wiki-content maincontent"><h2
id="jclouds-JcloudsComponent">Jclouds Component</h2><p><strong>Available as of
Camel 2.9</strong></p><p>This component allows interaction with cloud provider
key-value engines (blobstores) and compute services. The component uses <a
shape="rect" class="external-link" href="http://code.google.com/p/jclouds";
rel="nofollow">jclouds</a> which is<br clear="none"> a library that provides
abstractions for blobstores and compute
services.</p><p><strong>ComputeService</strong> simplifies the task of managing
machines in the cloud. For example, you can use ComputeService to start 5
machines and install your software on them.<br clear="none">
<strong>BlobStore</strong> simplifies dealing with key-value providers such as
Amazon S3. For example, BlobStore can give you a simple Map view of a
container.</p><p>The camel jclouds component allows you to use both
abstractions, as it specifes two types of endpoint the JcloudsBlobStoreEndpoint
and the JcloudsCom
puteEndpoint. You can have both producers and consumers on a blobstore
endpoint but you can only have producers on compute endpoints.</p><p>Maven
users will need to add the following dependency to their <code>pom.xml</code>
for this component:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-jclouds</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
]]></script>
-</div></div>
-
-<h3 id="jclouds-Configuringthecomponent">Configuring the component</h3>
-
-<p>The camel jclouds component will make use of multiple jclouds blobstores
and compute services as long as they are passed to the component during
initialization. The component accepts a list blobstores and compute services.
Here is how it can be configured.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
- <bean id="jclouds"
class="org.apache.camel.component.jclouds.JcloudsComponent">
+</div></div><h3 id="jclouds-Configuringthecomponent">Configuring the
component</h3><p>The camel jclouds component will make use of multiple jclouds
blobstores and compute services as long as they are passed to the component
during initialization. The component accepts a list blobstores and compute
services. Here is how it can be configured.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[ <bean id="jclouds"
class="org.apache.camel.component.jclouds.JcloudsComponent">
<property name="computeServices">
<list>
<ref bean="computeService"/>
@@ -151,215 +130,101 @@ a library that provides abstractions for
<bean id="computeService"
factory-bean="computeServiceContext"
factory-method="getComputeService"/>
]]></script>
-</div></div>
-
-<p>As you can see the component is capable of handling multiple blobstores and
compute services. The actual implementation that will be used by each endpoint
is specified by passing the provider inside the URI.</p>
-
-
-
-
-<h3 id="jclouds-URIformat">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-jclouds:blobstore:[provider id][?options]
+</div></div><p>As you can see the component is capable of handling multiple
blobstores and compute services. The actual implementation that will be used by
each endpoint is specified by passing the provider inside the URI.</p><h3
id="jclouds-URIformat">URI format</h3><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[jclouds:blobstore:[provider id][?options]
jclouds:compute:[provider id][?options]
]]></script>
-</div></div>
-
-<p>The <strong>provider id</strong> is the name of the cloud provider that
provides the target service (<em>e.g. aws-s3 or aws_ec2</em>).</p>
-
-<p>You can append query options to the URI in the following format,
<code>?option=value&option=value&...</code></p>
-
-<h3 id="jclouds-BlobstoreURIOptions">Blobstore URI Options</h3>
-
-<div class="confluenceTableSmall">
+</div></div><p>The <strong>provider id</strong> is the name of the cloud
provider that provides the target service (<em>e.g. aws-s3 or
aws_ec2</em>).</p><p>You can append query options to the URI in the following
format, <code>?option=value&option=value&...</code></p><h3
id="jclouds-BlobstoreURIOptions">Blobstore URI Options</h3><div
class="confluenceTableSmall">
<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>operation</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> PUT </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Producer Only</strong>. Specifies
the type of operation that will be performed to the blobstore. Allowed values
are PUT, GET. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>container</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> The name of the blob container. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>blobName</code>
</p></td><td colspan="1" rowspan="1" class=
"confluenceTd"><p> null </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> The name of the blob. </p></td></tr></tbody></table>
-</div>
-
-<p>You can have as many of these options as you like.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-jclouds:blobstore:aws-s3?operation=CamelJcloudsGet&container=mycontainer&blobName=someblob
+</div><p>You can have as many of these options as you like.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[jclouds:blobstore:aws-s3?operation=CamelJcloudsGet&container=mycontainer&blobName=someblob
]]></script>
-</div></div>
-
-<p>For producer endpoint you can override all of the above URI options by
passing the appropriate headers to the message.</p>
-
-<h4 id="jclouds-MessageHeadersforblobstore">Message Headers for blobstore</h4>
-<div class="confluenceTableSmall">
+</div></div><p>For producer endpoint you can override all of the above URI
options by passing the appropriate headers to the message.</p><h4
id="jclouds-MessageHeadersforblobstore">Message Headers for blobstore</h4><div
class="confluenceTableSmall">
<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p> Header </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>CamelJcloudsOperation</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The operation to
be performed on the blob. The valid options are</p>
<ul class="alternate" type="square"><li>PUT</li><li>GET</li></ul>
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>CamelJcloudsContainer</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> The name of the blob container. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>CamelJcloudsBlobName</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> The name of the blob. </p></td></tr></tbody></table>
-</div>
-
-<h3 id="jclouds-BlobstoreUsageSamples">Blobstore Usage Samples</h3>
-
-<h4 id="jclouds-Example1:Puttingtotheblob">Example 1: Putting to the blob</h4>
-
-<p>This example will show you how you can store any message inside a blob
using the jclouds component.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-from("direct:start")
+</div><h3 id="jclouds-BlobstoreUsageSamples">Blobstore Usage Samples</h3><h4
id="jclouds-Example1:Puttingtotheblob">Example 1: Putting to the
blob</h4><p>This example will show you how you can store any message inside a
blob using the jclouds component.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[from("direct:start")
.to("jclouds:blobstore:aws-s3" +
"?operation=PUT" +
"&container=mycontainer" +
"&blobName=myblob");
]]></script>
-</div></div>
-
-<p>In the above example you can override any of the URI parameters with
headers on the message.<br clear="none">
-Here is how the above example would look like using xml to define our
route.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<route>
+</div></div><p>In the above example you can override any of the URI parameters
with headers on the message.<br clear="none"> Here is how the above example
would look like using xml to define our route.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<route>
<from uri="direct:start"/>
<to
uri="jclouds:blobstore:aws-s3?operation=PUT&container=mycontainer&blobName=myblob"/>
</route>
]]></script>
-</div></div>
-
-<h4 id="jclouds-Example2:Getting/Readingfromablob">Example 2: Getting/Reading
from a blob</h4>
-
-<p>This example will show you how you can read the contnet of a blob using the
jclouds component.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-from("direct:start")
+</div></div><h4 id="jclouds-Example2:Getting/Readingfromablob">Example 2:
Getting/Reading from a blob</h4><p>This example will show you how you can read
the contnet of a blob using the jclouds component.</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[from("direct:start")
.to("jclouds:blobstore:aws-s3" +
"?operation=GET" +
"&container=mycontainer" +
"&blobName=myblob");
]]></script>
-</div></div>
-
-<p>In the above example you can override any of the URI parameters with
headers on the message.<br clear="none">
-Here is how the above example would look like using xml to define our
route.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<route>
+</div></div><p>In the above example you can override any of the URI parameters
with headers on the message.<br clear="none"> Here is how the above example
would look like using xml to define our route.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<route>
<from uri="direct:start"/>
<to
uri="jclouds:blobstore:aws-s3?operation=PUT&container=mycontainer&blobName=myblob"/>
</route>
]]></script>
-</div></div>
-
-
-<h4 id="jclouds-Example3:Consumingablob">Example 3: Consuming a blob</h4>
-
-<p>This example will consume all blob that are under the specified container.
The generated exchange will contain the payload of the blob as body.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
- from("jclouds:blobstore:aws-s3" +
+</div></div><h4 id="jclouds-Example3:Consumingablob">Example 3: Consuming a
blob</h4><p>This example will consume all blob that are under the specified
container. The generated exchange will contain the payload of the blob as
body.</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[ from("jclouds:blobstore:aws-s3"
+
"?container=mycontainer")
.to("direct:next");
]]></script>
-</div></div>
-
-<p>You can achieve the same goal by using xml, as you can see below.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<route>
+</div></div><p>You can achieve the same goal by using xml, as you can see
below.</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<route>
<from
uri="jclouds:blobstore:aws-s3?operation=GET&container=mycontainer&blobName=myblob"/>
<to uri="direct:next"/>
</route>
]]></script>
-</div></div>
-
-<h3 id="jclouds-ComputeServiceURIOptions">Compute Service URI Options</h3>
-
-<div class="confluenceTableSmall">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>operation</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> PUT </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Specifies the type of operation that will
be performed to the compute service. Allowed values are CREATE_NODE,
RUNS_CRIPT, DESTROY_NODE, LIST_NODES, LIST_IMAGES, LIST_HARDWARE.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>imageId</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>CREATE_NODE operation only</strong> The
imageId that will be used for creating a node. Values depend on the actual clou
d provider. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>locationId</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>CREATE_NODE operation only</strong> The
location that will be used for creating a node. Values depend on the actual
cloud provider. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>hardwareId</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>CREATE_NODE operation only</strong> The
hardware that will be used for creating a node. Values depend on the actual
cloud provider. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>group</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>CREATE_NODE operation only</st
rong> The group that will be assigned to the newly created node. Values depend
on the actual cloud provider. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>nodeId</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>RUN_SCRIPT & DESTROY_NODE operation
only</strong> The id of the node that will run the script or destroyed.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>user</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
null </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
<strong>RUN_SCRIPT operation only</strong> The user on the target node that
will run the script. </p></td></tr></tbody></table>
-</div>
-
-
-<p>The combination of parameters for use with the compute service depend on
the operation.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-jclouds:compute:aws-ec2?operation=CREATE_NODE&imageId=AMI_XXXXX&locationId=eu-west-1&group=mygroup
-]]></script>
-</div></div>
-
-<h3 id="jclouds-ComputeUsageSamples">Compute Usage Samples</h3>
-
-<p>Below are some examples that demonstrate the use of jclouds compute
producer in java dsl and spring/blueprint xml.</p>
-
-<h4 id="jclouds-Example1:Listingtheavailableimages.">Example 1: Listing the
available images.</h4>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
- from("jclouds:compute:aws-ec2" +
- "&operation=LIST_IMAGES")
+</div></div><h3 id="jclouds-ComputeServiceURIOptions">Compute Service URI
Options</h3><div class="confluenceTableSmall">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Default Value </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>operation</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> CamelJcloudsPut </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the type of
operation that will be performed to the compute service. Allowed values are
CamelJcloudsCreateNode, <br clear="none">
+CamelJcloudsRunScript, CamelJcloudsDestroyNode, CamelJCloudsDestroyNode,
CamelJCloudsListNodes, CamelJCloudsListImages, CamelJCloudsListHardware.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>imageId</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>CamelJcloudsCreateNode operation only</strong>
The imageId that will be used for creating a node. Values depend on the actual
cloud provider. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>locationId</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>CamelJcloudsCreateNode operation only</strong>
The location that will be used for creating a node. Values depend on the actual
cloud provider. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>hardwareId</code> </p></td><
td colspan="1" rowspan="1" class="confluenceTd"><p> null </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>CamelJcloudsCreateNode
operation only</strong> The hardware that will be used for creating a node.
Values depend on the actual cloud provider. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>group</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>CamelJcloudsCreateNode operation
only</strong> The group that will be assigned to the newly created node. Values
depend on the actual cloud provider. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>nodeId</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>CamelJcloudsRunScript &
CamelJcloudsDestroyNode operation only</strong> The id of the node that will
run the script or
destroyed. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>user</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> <strong>CamelJcloudsRunScript operation only</strong>
The user on the target node that will run the script.
</p></td></tr></tbody></table>
+</div><p>The combination of parameters for use with the compute service depend
on the operation.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[jclouds:compute:aws-ec2?operation=CamelJcloudsCreateNode&imageId=AMI_XXXXX&locationId=eu-west-1&group=mygroup
+]]></script>
+</div></div><h3 id="jclouds-ComputeUsageSamples">Compute Usage
Samples</h3><p>Below are some examples that demonstrate the use of jclouds
compute producer in java dsl and spring/blueprint xml.</p><h4
id="jclouds-Example1:Listingtheavailableimages.">Example 1: Listing the
available images.</h4><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[ from("jclouds:compute:aws-ec2" +
+ "&operation=CamelJCloudsListImages")
.to("direct:next");
]]></script>
-</div></div>
-
-<p>This will create a message that will contain the list of images inside its
body. You can also do the same using xml.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<route>
- <from uri="jclouds:compute:aws-ec2?operation=LIST_IMAGES"/>
+</div></div><p>This will create a message that will contain the list of images
inside its body. You can also do the same using xml.</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<route>
+ <from
uri="jclouds:compute:aws-ec2?operation=CamelJCloudsListImages"/>
<to uri="direct:next"/>
</route>
]]></script>
-</div></div>
-
-<h4 id="jclouds-Example2:Createanewnode.">Example 2: Create a new node.</h4>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
- from("direct:start").
+</div></div><h4 id="jclouds-Example2:Createanewnode.">Example 2: Create a new
node.</h4><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[ from("direct:start").
to("jclouds:compute:aws-ec2" +
- "?operation=CREATE_NODE" +
+ "?operation=CamelJcloudsCreateNode" +
"&imageId=AMI_XXXXX" +
"&locationId=XXXXX" +
"&group=myGroup");
]]></script>
-</div></div>
-
-<p>This will create a new node on the cloud provider. The out message in this
case will be a set of metadata that contains information about the newly
created node (e.g. the ip, hostname etc). Here is the same using spring xml.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<route>
+</div></div><p>This will create a new node on the cloud provider. The out
message in this case will be a set of metadata that contains information about
the newly created node (e.g. the ip, hostname etc). Here is the same using
spring xml.</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<route>
<from uri="direct:start"/>
- <to
uri="jclouds:compute:aws-ec2?operation=CREATE_NODE&imageId=AMI_XXXXX&locationId=XXXXX&group=myGroup"/>
+ <to
uri="jclouds:compute:aws-ec2?operation=CamelJcloudsCreateNode&imageId=AMI_XXXXX&locationId=XXXXX&group=myGroup"/>
</route>
]]></script>
-</div></div>
-
-<h4 id="jclouds-Example3:Runashellscriptonrunningnode.">Example 3: Run a shell
script on running node.</h4>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
- from("direct:start").
+</div></div><h4 id="jclouds-Example3:Runashellscriptonrunningnode.">Example 3:
Run a shell script on running node.</h4><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[ from("direct:start").
to("jclouds:compute:aws-ec2" +
- "?operation=RUN_SCRIPT" +
+ "?operation=CamelJcloudsRunScript" +
"?nodeId=10" +
"&user=ubuntu");
]]></script>
-</div></div>
-
-<p>The sample above will retrieve the body of the in message, which is
expected to contain the shell script to be executed. Once the script is
retrieved, it will be sent to the node for execution under the specified user
(<em>in order case ubuntu</em>). The target node is specified using its nodeId.
The nodeId can be retrieved either upon the creation of the node, it will be
part of the resulting metadata or by a executing a LIST_NODES operation.</p>
-
-<p><strong>Note</strong> This will require that the compute service that will
be passed to the component, to be initialized with the appropriate jclouds ssh
capable module (<em>e.g. jsch or sshj</em>).</p>
-
-<p>Here is the same using spring xml.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<route>
+</div></div><p>The sample above will retrieve the body of the in message,
which is expected to contain the shell script to be executed. Once the script
is retrieved, it will be sent to the node for execution under the specified
user (<em>in order case ubuntu</em>). The target node is specified using its
nodeId. The nodeId can be retrieved either upon the creation of the node, it
will be part of the resulting metadata or by a executing a LIST_NODES
operation.</p><p><strong>Note</strong> This will require that the compute
service that will be passed to the component, to be initialized with the
appropriate jclouds ssh capable module (<em>e.g. jsch or sshj</em>).</p><p>Here
is the same using spring xml.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<route>
<from uri="direct:start"/>
- <to
uri="jclouds:compute:aws-ec2?operation=RUN_SCRIPT&?nodeId=10&user=ubuntu"/>
+ <to
uri="jclouds:compute:aws-ec2?operation=CamelJcloudsListNodes&?nodeId=10&user=ubuntu"/>
</route>
]]></script>
-</div></div>
-
-<h4 id="jclouds-Seealso">See also</h4>
-
-<p>If you want to find out more about jclouds here is list of interesting
resources<br clear="none">
-<a shape="rect" class="external-link"
href="http://jclouds.incubator.apache.org/documentation/userguide/blobstore-guide/";>Jclouds
Blobstore wiki</a><br clear="none">
-<a shape="rect" class="external-link"
href="http://jclouds.incubator.apache.org/documentation/userguide/compute/";>Jclouds
Compute wiki</a></p></div>
+</div></div><h4 id="jclouds-Seealso">See also</h4><p>If you want to find out
more about jclouds here is list of interesting resources<br clear="none"> <a
shape="rect" class="external-link"
href="http://jclouds.incubator.apache.org/documentation/userguide/blobstore-guide/";>Jclouds
Blobstore wiki</a><br clear="none"> <a shape="rect" class="external-link"
href="http://jclouds.incubator.apache.org/documentation/userguide/compute/";>Jclouds
Compute wiki</a></p></div>
</td>
<td valign="top">
<div class="navigation">
