Modified: jclouds/site-content/releasenotes/1.1.0/index.html URL: http://svn.apache.org/viewvc/jclouds/site-content/releasenotes/1.1.0/index.html?rev=1923693&r1=1923692&r2=1923693&view=diff ============================================================================== --- jclouds/site-content/releasenotes/1.1.0/index.html (original) +++ jclouds/site-content/releasenotes/1.1.0/index.html Mon Feb 10 07:25:53 2025 @@ -150,7 +150,7 @@ <h1>Release Notes Version 1.1.0</h1> </div> - <h2>Introduction</h2> + <h2 id="introduction">Introduction</h2> <p>The 1.1.0 release of jclouds includes results of 2 months effort by our contributors. A total of <a href="http://code.google.com/p/jclouds/issues/list?can=1&q=Milestone%3D1.1.0&colspec=IDTypeStatusPriorityMilestoneOwnerSummary&cells=tiles";>30 Issues</a> @@ -164,455 +164,442 @@ Next release will be in about a month an <a href="http://code.google.com/p/jclouds/issues/detail?id=158";>Softlayer</a> providers in the next version.</p> <p>Please <a href="http://code.google.com/p/jclouds/issues";>submit your own ideas</a> and <a href="http://groups.google.com/group/jclouds";>let us know</a> if there are features - you'd like to see, need help on, or are interested in contributing. Make sure you follow us on <a href="http://twitter.com/#!/jclouds";>Twitter</a> for updates.</p> + youâd like to see, need help on, or are interested in contributing. Make sure you follow us on <a href="http://twitter.com/#!/jclouds";>Twitter</a> for updates.</p> -<h2>New Features</h2> - -<h3>Green House Data vCloud Support</h3> - -<p>Green House Data run a completely wind-powered public vCloud offering in Wyoming, accessible as <code>greenhousedata-element-vcloud</code> in jclouds. +<h2 id="new-features">New Features</h2> +<h3 id="green-house-data-vcloud-support">Green House Data vCloud Support</h3> +<p>Green House Data run a completely wind-powered public vCloud offering in Wyoming, accessible as <code class="language-plaintext highlighter-rouge">greenhousedata-element-vcloud</code> in jclouds. Check out their <a href="http://www.greenhousedata.com/element-cloud-hosting/vcloud-services/";>site</a> for more details.</p> -<h3>SSHJ driver</h3> - -<p>Troubleshooting ssh connections consumed a lot of time during past releases of jclouds. This is because clouds have different operating system configurations, and sometimes distant or complicated networks between you and the nodes. Having a reliable ssh client implementation can significantly cut debugging time when problems occur. We've found [https://github.com/shikhar/sshj sshj] the most reliable and hackable open source java ssh library, and importantly with best feedback when failures occur. Here's how to configure it, noting you'll need to include the <code>org.jclouds.driver/jclouds-sshj</code> dependency in your codebase.</p> +<h3 id="sshj-driver">SSHJ driver</h3> +<p>Troubleshooting ssh connections consumed a lot of time during past releases of jclouds. This is because clouds have different operating system configurations, and sometimes distant or complicated networks between you and the nodes. Having a reliable ssh client implementation can significantly cut debugging time when problems occur. Weâve found [https://github.com/shikhar/sshj sshj] the most reliable and hackable open source java ssh library, and importantly with best feedback when failures occur. Hereâs how to configure it, noting youâll need to include the <code class="language-plaintext highlighter-rouge">org.jclouds.driver/jclouds-sshj</code> dependency in your codebase.</p> <p><em>java</em></p> -<div class="highlight"><pre><code class="java"><span class="n">compute</span> <span class="o">=</span> <span class="k">new</span> <span class="n">ComputeServiceContextFactory</span><span class="o">().</span><span class="na">createContext</span><span class="o">(</span><span class="n">provider</span><span class="o">,</span> <span class="n">identity</span><span class="o">,</span> <span class="n">credential</span><span class="o">,</span> <span class="n">ImmutableSet</span><span class="o">.<</span><span class="n">Module</span><span class="o">></span> <span class="n">of</span><span class="o">(</span><span class="k">new</span> <span class="n">SshjSshClientModule</span><span class="o">()),</span> <span class="n">properties</span><span class="o">);</span> -</code></pre></div> - +<figure class="highlight"><pre><code class="language-java" data-lang="java"><span class="n">compute</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">ComputeServiceContextFactory</span><span class="o">().</span><span class="na">createContext</span><span class="o">(</span><span class="n">provider</span><span class="o">,</span> <span class="n">identity</span><span class="o">,</span> <span class="n">credential</span><span class="o">,</span> <span class="nc">ImmutableSet</span><span class="o">.<</span><span class="nc">Module</span><span class="o">></span> <span class="nf">of</span><span class="o">(</span><span class="k">new</span> <span class="nc">SshjSshClientModule</span><span class="o">()),</span> <span class="n">properties</span><span class="o">);</span></code></pre></figure> <p><em>clojure</em></p> -<div class="highlight"><pre><code class="clojure"><span class="p">(</span><span class="k">def </span><span class="nv">compute</span> - <span class="p">(</span><span class="nf">compute-service</span> <span class="nv">provider</span> <span class="nv">provider-identity</span> <span class="nv">provider-credential</span> <span class="ss">:sshj</span><span class="p">))</span> -</code></pre></div> - +<figure class="highlight"><pre><code class="language-clojure" data-lang="clojure"><span class="p">(</span><span class="k">def</span><span class="w"> </span><span class="n">compute</span><span class="w"> + </span><span class="p">(</span><span class="nf">compute-service</span><span class="w"> </span><span class="n">provider</span><span class="w"> </span><span class="n">provider-identity</span><span class="w"> </span><span class="n">provider-credential</span><span class="w"> </span><span class="no">:sshj</span><span class="p">))</span></code></pre></figure> -<h3>Hostname in NodeMetadata</h3> +<h3 id="hostname-in-nodemetadata">Hostname in NodeMetadata</h3> <p>Those writing shell scripts from data inside !NodeMetadata often need to know what the local hostname is of the operating system you are working against. We now return hostname data on clouds that assign this value predictably, or null if unpredictable.</p> -<p>As of 1.1.0, the following apis and providers assign hostnames predictably: byon, aws-ec2, cloudservers-us|uk, slicehost, and trmk-ecloud|vcloudexpress.</p> - -<h3>Configurable defaults for Multi-Site vCloud and Terremark installations</h3> +<table> + <tbody> + <tr> + <td>As of 1.1.0, the following apis and providers assign hostnames predictably: byon, aws-ec2, cloudservers-us</td> + <td>uk, slicehost, and trmk-ecloud</td> + <td>vcloudexpress.</td> + </tr> + </tbody> +</table> +<h3 id="configurable-defaults-for-multi-site-vcloud-and-terremark-installations">Configurable defaults for Multi-Site vCloud and Terremark installations</h3> <p>When working with a multi-site Terremark or vCloud provider, you may want to change the default datacenter or network to launch VMs into, rather than have jclouds pick one. With new configuration properties, you can specify the name of the Org, VDC, Catalog, and Network you prefer for a particular invocation of jclouds.</p> -<div class="highlight"><pre><code class="java"> <span class="n">overrides</span> <span class="o">=</span> <span class="k">new</span> <span class="n">Properties</span><span class="o">();</span> - <span class="n">overrides</span><span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="n">VCloudConstants</span><span class="o">.</span><span class="na">PROPERTY_VCLOUD_DEFAULT_VDC</span><span class="o">,</span> <span class="s">"MyCompany - MIA"</span><span class="o">);</span> - <span class="n">context</span> <span class="o">=</span> <span class="k">new</span> <span class="n">ComputeServiceContextFactory</span><span class="o">().</span><span class="na">createContext</span><span class="o">(</span><span class="s">"trmk-ecloud"</span><span class="o">,</span> <span class="n">email</span><span class="o">,</span> <span class="n">pass</span><span class="o">,</span> - <span class="n">ImmutableSet</span><span class="o">.<</span><span class="n">Module</span><span class="o">></span> <span class="nf">of</span><span class="o">(</span><span class="k">new</span> <span class="n">SshjSshClientModule</span><span class="o">()),</span> <span class="n">overrides</span><span class="o">)</span> -</code></pre></div> - - -<h3>Amazon EC2 Image Filters</h3> +<figure class="highlight"><pre><code class="language-java" data-lang="java"> <span class="n">overrides</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">Properties</span><span class="o">();</span> + <span class="n">overrides</span><span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="nc">VCloudConstants</span><span class="o">.</span><span class="na">PROPERTY_VCLOUD_DEFAULT_VDC</span><span class="o">,</span> <span class="s">"MyCompany - MIA"</span><span class="o">);</span> + <span class="n">context</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">ComputeServiceContextFactory</span><span class="o">().</span><span class="na">createContext</span><span class="o">(</span><span class="s">"trmk-ecloud"</span><span class="o">,</span> <span class="n">email</span><span class="o">,</span> <span class="n">pass</span><span class="o">,</span> + <span class="nc">ImmutableSet</span><span class="o">.<</span><span class="nc">Module</span><span class="o">></span> <span class="nf">of</span><span class="o">(</span><span class="k">new</span> <span class="nc">SshjSshClientModule</span><span class="o">()),</span> <span class="n">overrides</span><span class="o">)</span></code></pre></figure> +<h3 id="amazon-ec2-image-filters">Amazon EC2 Image Filters</h3> <p>Even refining lists to a set of user ids, using EC2 can be bogged down, parsing the thousands of public images published by the Amazon EC2 community. Several users have expressed the desire to refine further, based on qualifications they choose. You can set a property to restrict the list to a subset matching any recognized <a href="http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html";>image query</a>.</p> -<div class="highlight"><pre><code class="java"> <span class="n">overrides</span> <span class="o">=</span> <span class="k">new</span> <span class="n">Properties</span><span class="o">();</span> +<figure class="highlight"><pre><code class="language-java" data-lang="java"> <span class="n">overrides</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">Properties</span><span class="o">();</span> <span class="c1">// choose only amazon images that are ebs-backed</span> - <span class="n">overrides</span><span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="n">AWSEC2Constants</span><span class="o">.</span><span class="na">PROPERTY_EC2_AMI_QUERY</span><span class="o">,</span> - <span class="s">"owner-id=137112412989;state=available;image-type=machine;root-device-type=ebs"</span><span class="o">);</span> - <span class="n">context</span> <span class="o">=</span> <span class="k">new</span> <span class="n">ComputeServiceContextFactory</span><span class="o">().</span><span class="na">createContext</span><span class="o">(</span><span class="s">"aws-ec2"</span><span class="o">,</span> <span class="n">access</span><span class="o">,</span> <span class="n">secret</span><span class="o">,</span> - <span class="n">ImmutableSet</span><span class="o">.<</span><span class="n">Module</span><span class="o">></span> <span class="nf">of</span><span class="o">(</span><span class="k">new</span> <span class="n">SshjSshClientModule</span><span class="o">()),</span> <span class="n">overrides</span><span class="o">)</span> -</code></pre></div> - + <span class="n">overrides</span><span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="nc">AWSEC2Constants</span><span class="o">.</span><span class="na">PROPERTY_EC2_AMI_QUERY</span><span class="o">,</span> + <span class="s">"owner-id=137112412989;state=available;image-type=machine;root-device-type=ebs"</span><span class="o">);</span> + <span class="n">context</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">ComputeServiceContextFactory</span><span class="o">().</span><span class="na">createContext</span><span class="o">(</span><span class="s">"aws-ec2"</span><span class="o">,</span> <span class="n">access</span><span class="o">,</span> <span class="n">secret</span><span class="o">,</span> + <span class="nc">ImmutableSet</span><span class="o">.<</span><span class="nc">Module</span><span class="o">></span> <span class="nf">of</span><span class="o">(</span><span class="k">new</span> <span class="nc">SshjSshClientModule</span><span class="o">()),</span> <span class="n">overrides</span><span class="o">)</span></code></pre></figure> <p>See <a href="/documentation/reference/using-ec2">EC2 Image Filters</a> for more.</p> -<h3>New syntax for creating EC2 ingress rules</h3> +<h3 id="new-syntax-for-creating-ec2-ingress-rules">New syntax for creating EC2 ingress rules</h3> -<p>For those using the "aws-ec2" provider, you'll notice that AWS now supports security groups constraints that are more fine grained than before. For example, you can now assign rules constrained by source group and also port. We now have an fluent api for creating and applying ingress rules.</p> +<p>For those using the âaws-ec2â provider, youâll notice that AWS now supports security groups constraints that are more fine grained than before. For example, you can now assign rules constrained by source group and also port. We now have an fluent api for creating and applying ingress rules.</p> -<div class="highlight"><pre><code class="java"><span class="c1">// get a hold of an ec2 client so you can access security group services</span> -<span class="n">securityGroupClient</span> <span class="o">=</span> <span class="n">AWSEC2Client</span><span class="o">.</span><span class="na">class</span><span class="o">.</span><span class="na">cast</span><span class="o">(</span><span class="n">context</span><span class="o">.</span><span class="na">getProviderSpecificContext</span><span class="o">().</span><span class="na">getApi</span><span class="o">()).</span><span class="na">getSecurityGroupServices</span><span class="o">();</span> +<figure class="highlight"><pre><code class="language-java" data-lang="java"><span class="c1">// get a hold of an ec2 client so you can access security group services</span> +<span class="n">securityGroupClient</span> <span class="o">=</span> <span class="nc">AWSEC2Client</span><span class="o">.</span><span class="na">class</span><span class="o">.</span><span class="na">cast</span><span class="o">(</span><span class="n">context</span><span class="o">.</span><span class="na">getProviderSpecificContext</span><span class="o">().</span><span class="na">getApi</span><span class="o">()).</span><span class="na">getSecurityGroupServices</span><span class="o">();</span> <span class="c1">// create a new group and get back its id</span> <span class="n">groupId</span> <span class="o">=</span> <span class="n">securityGroupClient</span><span class="o">.</span><span class="na">createSecurityGroupInRegionAndReturnId</span><span class="o">(</span><span class="n">regionOrNull</span><span class="o">,</span> <span class="n">groupName</span><span class="o">,</span> <span class="n">groupDescription</span><span class="o">);</span> <span class="c1">// add new rule(s) to the group</span> <span class="n">securityGroupClient</span><span class="o">.</span><span class="na">authorizeSecurityGroupIngressInRegion</span><span class="o">(</span><span class="n">regionOrNull</span><span class="o">,</span> <span class="n">groupId</span><span class="o">,</span> - <span class="n">IpPermissions</span><span class="o">.</span><span class="na">permit</span><span class="o">(</span><span class="n">IpProtocol</span><span class="o">.</span><span class="na">UDP</span><span class="o">).</span><span class="na">fromPort</span><span class="o">(</span><span class="mi">11</span><span class="o">).</span><span class="na">to</span><span class="o">(</span><span class="mi">53</span><span class="o">)</span> - <span class="o">.</span><span class="na">originatingFromSecurityGroupId</span><span class="o">(</span><span class="s">"otherGroup"</span><span class="o">));</span> -</code></pre></div> - + <span class="nc">IpPermissions</span><span class="o">.</span><span class="na">permit</span><span class="o">(</span><span class="nc">IpProtocol</span><span class="o">.</span><span class="na">UDP</span><span class="o">).</span><span class="na">fromPort</span><span class="o">(</span><span class="mi">11</span><span class="o">).</span><span class="na">to</span><span class="o">(</span><span class="mi">53</span><span class="o">)</span> + <span class="o">.</span><span class="na">originatingFromSecurityGroupId</span><span class="o">(</span><span class="s">"otherGroup"</span><span class="o">));</span></code></pre></figure> <p>See <a href="http://code.google.com/p/jclouds/issues/detail?id=606&can=1&q=Milestone%3D1.1.0";>Issue 606</a> for more examples.</p> -<h3>Preferring S3-Backed Images in EC2</h3> - +<h3 id="preferring-s3-backed-images-in-ec2">Preferring S3-Backed Images in EC2</h3> <p>During the recent aws outage, instances which used EBS (elastic block store) were more impacted from an availability standpoint. We now have a template builder option that allows you to prefer instance store.</p> -<div class="highlight"><pre><code class="java"> <span class="c1">// match the smallest hardware configuration that will run amazon linux with an S3-backed image.</span> +<figure class="highlight"><pre><code class="language-java" data-lang="java"> <span class="c1">// match the smallest hardware configuration that will run amazon linux with an S3-backed image.</span> <span class="c1">// Note that t1.micro does not support instance store, therefore this will match m1.small.</span> - <span class="n">Template</span> <span class="n">template</span> <span class="o">=</span> <span class="n">templateBuilder</span><span class="o">.</span><span class="na">osFamily</span><span class="o">(</span><span class="n">OsFamily</span><span class="o">.</span><span class="na">AMZN_LINUX</span><span class="o">)</span> - <span class="o">.</span><span class="na">imageMatches</span><span class="o">(</span><span class="n">EC2ImagePredicates</span><span class="o">.</span><span class="na">rootDeviceType</span><span class="o">(</span><span class="n">RootDeviceType</span><span class="o">.</span><span class="na">INSTANCE_STORE</span><span class="o">)).</span><span class="na">build</span><span class="o">();</span> -</code></pre></div> + <span class="nc">Template</span> <span class="n">template</span> <span class="o">=</span> <span class="n">templateBuilder</span><span class="o">.</span><span class="na">osFamily</span><span class="o">(</span><span class="nc">OsFamily</span><span class="o">.</span><span class="na">AMZN_LINUX</span><span class="o">)</span> + <span class="o">.</span><span class="na">imageMatches</span><span class="o">(</span><span class="nc">EC2ImagePredicates</span><span class="o">.</span><span class="na">rootDeviceType</span><span class="o">(</span><span class="nc">RootDeviceType</span><span class="o">.</span><span class="na">INSTANCE_STORE</span><span class="o">)).</span><span class="na">build</span><span class="o">();</span></code></pre></figure> - -<h2>API Breakers</h2> - -<h3>New Terremark and vCloud models</h3> +<h2 id="api-breakers">API Breakers</h2> +<h3 id="new-terremark-and-vcloud-models">New Terremark and vCloud models</h3> <p>Terremark vCloud Express was the first operable vCloud Express environment. Over time, the vCloud model changed as did Terremark offerings, in different directions. Troubleshooting and coding these models became complicated over time, with vain attempts to share code across incompatible models. -In the jclouds 1.1.0, we've cut vcloud models from Terremark models, simplifying maintenance of both. -This doesn't impact use of <a href="/documentation/userguide/compute">ComputeService</a>, but it does impact the provider-specific terremark apis, -as they've been repackaged under <code>org.jclouds.trmk</code>. Also, the maven dependencies of <code>org.jclouds.api/vcloud</code>, -<code>org.jclouds.provider/trmk-ecloud</code>, and <code>org.jclouds.provider/trmk-vcloudexpress</code> have been refactored.</p> +In the jclouds 1.1.0, weâve cut vcloud models from Terremark models, simplifying maintenance of both. +This doesnât impact use of <a href="/documentation/userguide/compute">ComputeService</a>, but it does impact the provider-specific terremark apis, +as theyâve been repackaged under <code class="language-plaintext highlighter-rouge">org.jclouds.trmk</code>. Also, the maven dependencies of <code class="language-plaintext highlighter-rouge">org.jclouds.api/vcloud</code>, +<code class="language-plaintext highlighter-rouge">org.jclouds.provider/trmk-ecloud</code>, and <code class="language-plaintext highlighter-rouge">org.jclouds.provider/trmk-vcloudexpress</code> have been refactored.</p> -<h2>Cool Stuff</h2> +<h2 id="cool-stuff">Cool Stuff</h2> -<h3>JBoss AS7 in our integration tests</h3> +<h3 id="jboss-as7-in-our-integration-tests">JBoss AS7 in our integration tests</h3> -<p>Many jclouds <a href="/documentation/userguide/compute">ComputeService</a> users install middleware via our <code>runScript</code> functionality directly +<p>Many jclouds <a href="/documentation/userguide/compute">ComputeService</a> users install middleware via our <code class="language-plaintext highlighter-rouge">runScript</code> functionality directly as opposed to using a configuration tool. In order to test our ability to deploy simple configurations, we formerly used JBoss version 6.0. However, this took a long while to startup, was a big image, and generally slowed testing. Seeing tweets about version 7, we were quite excited to see improvements in test execution, based on claims. -We've verified very fast startup, many times under 2 seconds using AS7 in our service-based testing. -If you'd like more details or results, have a look at the [issue]http://code.google.com/p/jclouds/issues/detail?id=616) we migrated to AS7 in. +Weâve verified very fast startup, many times under 2 seconds using AS7 in our service-based testing. +If youâd like more details or results, have a look at the [issue]http://code.google.com/p/jclouds/issues/detail?id=616) we migrated to AS7 in. Also, if you are interested in contributing a test using a different product, let us know!</p> -<h2>Tracking</h2> +<h2 id="tracking">Tracking</h2> <p>Status of the release is tracked in <a href="http://code.google.com/p/jclouds/issues/detail?id=641";>issue 641</a></p> -<h2>Test Results</h2> +<h2 id="test-results">Test Results</h2> <table> -<thead> -<tr> -<th> <em>maven dependency</em> </th> -<th> <em>abstraction</em> </th> -<th> <em>iso 3166 codes</em> </th> -<th> <em>result</em> </th> -<th> <em>notes</em> </th> -</tr> -</thead> -<tbody> -<tr> -<td> org.jclouds.provider/aws-ec2</td> -<td> compute</td> -<td> US-VA,US-CA,IE,SG</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410015000&name=aws-ec2.txt&token=eb35302e4ede816a16e4ec5a20d571b8";>pass</a></td> -<td> only failure was a timeout from my laptop</td> -</tr> -<tr> -<td> org.jclouds.provider/aws-s3</td> -<td> blobstore</td> -<td> US,US-CA,IE,SG</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410001000&name=aws-s3.txt&token=4a7dd79d12aae523b5a7407176251248";>pass</a></td> -<td> test failure was due to client-side network timeout</td> -</tr> -<tr> -<td> org.jclouds.provider/azureblob</td> -<td> blobstore</td> -<td> US-TX,US-IL,IE-D,SG,NL-NH,HK</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410004000&name=azureblob.txt&token=307572b69cb83868ea3b738027add61c";>pass</a></td> -<td> one glitch on integration test, likely due to slow wifi</td> -</tr> -<tr> -<td> org.jclouds.provider/bluelock-vcloud-vcenterprise</td> -<td> compute</td> -<td> US-IN</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410028000&name=bluelock-vcloud-vcenterprise.txt&token=81dfe72af473ff124e7a1d538c106eb3";>pass</a></td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/bluelock-vcloud-zone01</td> -<td> compute</td> -<td> US-IN</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410027000&name=bluelock-vcloud-zone01.txt&token=b0099cfb15a6aab14735c58b8a53b7fb";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/cloudfiles-uk</td> -<td> blobstore</td> -<td> GB-SLG</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410010000&name=cloudfiles-uk.txt&token=946766baf5669d44c9d26256798bc5e9";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/cloudfiles-us</td> -<td> blobstore</td> -<td> US-TX</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410010001&name=cloudfiles-us.txt&token=d3d3327a05eb713f5f809e76c2066b99";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/cloudloadbalancers-us</td> -<td> loadbalancer</td> -<td> US-IL,US-TX</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410021000&name=cloudloadbalancers-us.txt&token=e4286e87f5e5970171e32c861a0f911c";>pass</a></td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/cloudonestorage</td> -<td> blobstore</td> -<td> US-GA,US-TX</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410036001&name=cloudonestorage.txt&token=9afd58cd83ea1db0f64f5c9dd58fc630";>pass</a> </td> -<td> see note on atmos. operations except ones requiring ListContainerOptions.recursive operate</td> -</tr> -<tr> -<td> org.jclouds.provider/cloudservers-uk</td> -<td> compute</td> -<td> GB-SLG</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410008000&name=cloudservers-uk.txt&token=08ff814d1faef7bd3e6c2ca984e6c4b1";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/cloudservers-us</td> -<td> compute</td> -<td> US-IL,US-TX</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410008001&name=cloudservers-us.txt&token=13944d52ae9f8befe3c5557b121ef521";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/cloudsigma-zrh</td> -<td> compute</td> -<td> CH-ZH</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410037000&name=cloudsigma-zrh.txt&token=4857a89c1098866767d743cdb89c19c9";>unknown</a></td> -<td> operations seem to work fine, but since images don't support automated ssh login, we cannot verify</td> -</tr> -<tr> -<td> org.jclouds.provider/elastichosts-lon-b</td> -<td> compute</td> -<td> GB-LND</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410009000&name=elastichosts-lon-b.txt&token=87632bd44b76925e6e59876df0c5f6c2";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/elastichosts-lon-p</td> -<td> compute</td> -<td> GB-LND</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410009001&name=elastichosts-lon-p.txt&token=8921d25b4b0db9f938db864b15654d68";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/elastichosts-sat-p</td> -<td> compute</td> -<td> US-TX</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410009002&name=elastichosts-sat-p.txt&token=cea940fb19a2ed70339d83eaeb46bebc";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/eucalyptus-partnercloud-ec2</td> -<td> compute</td> -<td> US-CA</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410025000&name=eucalyptus-partnercloud-ec2.txt&token=49205b56e47672af46bfa874ed4895dc";>unknown</a></td> -<td> account doesn't have enough resources to verify things operate</td> -</tr> -<tr> -<td> org.jclouds.provider/eucalyptus-partnercloud-s3</td> -<td> blobstore</td> -<td> US-CA</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410018000&name=eucalyptus-partnercloud-s3.txt&token=d967dc03d3d8a07e389b8848d051e216";>unstable</a></td> -<td> acls are not compatible with s3 (testPublicReadOnObject,testPublicWriteOnObject,testUpdateObjectACL); lack of NextMarker makes list continuations unreliable (testListContainerMarker testPutMoreThanSingleListing); different http code on etag conditional (testGetIfMatch)</td> -</tr> -<tr> -<td> org.jclouds.provider/gogrid</td> -<td> compute</td> -<td> US-CA,US-VA</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410019000&name=gogrid.txt&token=b556956bf7b31350ac00ae38f4dfbafb";>unstable</a></td> -<td> sometimes metadata like running status flip off our tests. Since I cannot get a clean run after several tries, I marking this unstable conceding most tests do pass.</td> -</tr> -<tr> -<td> org.jclouds.provider/greenhousedata-element-vcloud</td> -<td> compute</td> -<td> US-WY</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410026000&name=greenhousedata-element-vcloud.txt&token=6a892bf558d77b858e0c788ed803c41d";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/ninefold-storage</td> -<td> blobstore</td> -<td> AU-NSW</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410031000&name=ninefold-storage.txt&token=e491d8344613bae591f7760d4cb7a2e5";>pass</a> </td> -<td> see note on atmos. operations except ones requiring ListContainerOptions.recursive operate</td> -</tr> -<tr> -<td> org.jclouds.provider/openhosting-east1</td> -<td> compute</td> -<td> US-VA</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410016000&name=openhosting-east1.txt&token=84ef8be1ececcd191376975208689e6e";>pass</a> </td> -<td> works from a computeService perspective, but don't expect openjdk to install properly on their default image, as the tests show there's problems installing it</td> -</tr> -<tr> -<td> org.jclouds.provider/rimuhosting</td> -<td> compute</td> -<td> NZ-AUK,US-TX,AU-NSW,GB-LND</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410033001&name=rimuhosting.txt&token=33f5976e615fc8db2017379a89a47dad";>unstable</a></td> -<td> rimuhosting works while servers are launched sequentially. During the tests, servers launched sequentially operated as expected, but when 2 were launched at the same time, we started to receive unexpected content back from the rest api</td> -</tr> -<tr> -<td> org.jclouds.provider/savvis-symphonyvpdc</td> -<td> compute</td> -<td> US,CA</td> -<td> <a href="http://jclouds.googlecode.com/issues/attachment?aid=6410011000&name=jclouds_savvis-symphonyvpdc_livetests_reports_07282011.zip&token=f95192bf5511519333f1187ac64c7afd";>unstable</a></td> -<td> NOTE this provider does not yet implement ComputeService interface, so you have to use the provider api; a few minor tests fail, and since we don't have comprehensive support due to lacking ComputeService impl, marking unstable</td> -</tr> -<tr> -<td> org.jclouds.provider/serverlove-z1-man</td> -<td> compute</td> -<td> GB-MAN</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410012000&name=serverlove-z1-man.txt&token=3c566c0d55d469a991ca23d99f1e2763";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/skalicloud-sdg-my</td> -<td> compute</td> -<td> MY-10</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410013000&name=skalicloud-sdg-my.txt&token=2ce8ca22fe95fb9ea7158895f74f7033";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.provider/slicehost</td> -<td> compute</td> -<td> US-IL,US-TX,US-MO</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410006000&name=slicehost.txt&token=d25355a92499ad9b3e9c8687b4ef0020";>pass</a> </td> -<td> slicehost slice status is sometimes inconsistent and reports pending when in active state</td> -</tr> -<tr> -<td> org.jclouds.provider/stratogen-vcloud-mycloud</td> -<td> compute</td> -<td> GB</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410030000&name=stratogen-vcloud-mycloud.txt&token=28eccdc143d550c0855c6973bcb0f9cf";>pass</a> </td> -<td> passes critical tests, and a re-run should go clean</td> -</tr> -<tr> -<td> org.jclouds.provider/synaptic-storage</td> -<td> blobstore</td> -<td> US-VA,US-TX</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410040000&name=synaptic-storage.txt&token=90a28048e50b5f9777136eb398ac883a";>pass</a> </td> -<td> see note on atmos. operations except ones requiring ListContainerOptions.recursive operate</td> -</tr> -<tr> -<td> org.jclouds.provider/trmk-ecloud</td> -<td> compute</td> -<td> US-FL,NL-NH</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410023000&name=trmk-ecloud.txt&token=488128a5141a3931a5c5fca1609cb028";>pass</a> </td> -<td> functionality works, with a few glitches: overriding credentials via runScriptOnNodes doesn't seem to apply (testAScriptExecutionAfterBootWithBasicTemplate);NPE attempting to create a new node after closing and recreating your context in the same VM (testCreateAnotherNodeWithANewContextToEnsureSharedMemIsntRequired)</td> -</tr> -<tr> -<td> org.jclouds.provider/trmk-vcloudexpress</td> -<td> compute</td> -<td> US-FL</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410032000&name=trmk-vcloudexpress.txt&token=2e9c483b5870486cc8f4027cfce3419e";>pass</a> </td> -<td> same glitches as ecloud</td> -</tr> -</tbody> + <thead> + <tr> + <th><em>maven dependency</em></th> + <th><em>abstraction</em></th> + <th><em>iso 3166 codes</em></th> + <th><em>result</em></th> + <th><em>notes</em></th> + </tr> + </thead> + <tbody> + <tr> + <td>org.jclouds.provider/aws-ec2</td> + <td>compute</td> + <td>US-VA,US-CA,IE,SG</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410015000&name=aws-ec2.txt&token=eb35302e4ede816a16e4ec5a20d571b8";>pass</a></td> + <td>only failure was a timeout from my laptop</td> + </tr> + <tr> + <td>org.jclouds.provider/aws-s3</td> + <td>blobstore</td> + <td>US,US-CA,IE,SG</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410001000&name=aws-s3.txt&token=4a7dd79d12aae523b5a7407176251248";>pass</a></td> + <td>test failure was due to client-side network timeout</td> + </tr> + <tr> + <td>org.jclouds.provider/azureblob</td> + <td>blobstore</td> + <td>US-TX,US-IL,IE-D,SG,NL-NH,HK</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410004000&name=azureblob.txt&token=307572b69cb83868ea3b738027add61c";>pass</a></td> + <td>one glitch on integration test, likely due to slow wifi</td> + </tr> + <tr> + <td>org.jclouds.provider/bluelock-vcloud-vcenterprise</td> + <td>compute</td> + <td>US-IN</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410028000&name=bluelock-vcloud-vcenterprise.txt&token=81dfe72af473ff124e7a1d538c106eb3";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/bluelock-vcloud-zone01</td> + <td>compute</td> + <td>US-IN</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410027000&name=bluelock-vcloud-zone01.txt&token=b0099cfb15a6aab14735c58b8a53b7fb";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/cloudfiles-uk</td> + <td>blobstore</td> + <td>GB-SLG</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410010000&name=cloudfiles-uk.txt&token=946766baf5669d44c9d26256798bc5e9";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/cloudfiles-us</td> + <td>blobstore</td> + <td>US-TX</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410010001&name=cloudfiles-us.txt&token=d3d3327a05eb713f5f809e76c2066b99";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/cloudloadbalancers-us</td> + <td>loadbalancer</td> + <td>US-IL,US-TX</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410021000&name=cloudloadbalancers-us.txt&token=e4286e87f5e5970171e32c861a0f911c";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/cloudonestorage</td> + <td>blobstore</td> + <td>US-GA,US-TX</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410036001&name=cloudonestorage.txt&token=9afd58cd83ea1db0f64f5c9dd58fc630";>pass</a></td> + <td>see note on atmos. operations except ones requiring ListContainerOptions.recursive operate</td> + </tr> + <tr> + <td>org.jclouds.provider/cloudservers-uk</td> + <td>compute</td> + <td>GB-SLG</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410008000&name=cloudservers-uk.txt&token=08ff814d1faef7bd3e6c2ca984e6c4b1";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/cloudservers-us</td> + <td>compute</td> + <td>US-IL,US-TX</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410008001&name=cloudservers-us.txt&token=13944d52ae9f8befe3c5557b121ef521";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/cloudsigma-zrh</td> + <td>compute</td> + <td>CH-ZH</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410037000&name=cloudsigma-zrh.txt&token=4857a89c1098866767d743cdb89c19c9";>unknown</a></td> + <td>operations seem to work fine, but since images donât support automated ssh login, we cannot verify</td> + </tr> + <tr> + <td>org.jclouds.provider/elastichosts-lon-b</td> + <td>compute</td> + <td>GB-LND</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410009000&name=elastichosts-lon-b.txt&token=87632bd44b76925e6e59876df0c5f6c2";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/elastichosts-lon-p</td> + <td>compute</td> + <td>GB-LND</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410009001&name=elastichosts-lon-p.txt&token=8921d25b4b0db9f938db864b15654d68";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/elastichosts-sat-p</td> + <td>compute</td> + <td>US-TX</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410009002&name=elastichosts-sat-p.txt&token=cea940fb19a2ed70339d83eaeb46bebc";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/eucalyptus-partnercloud-ec2</td> + <td>compute</td> + <td>US-CA</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410025000&name=eucalyptus-partnercloud-ec2.txt&token=49205b56e47672af46bfa874ed4895dc";>unknown</a></td> + <td>account doesnât have enough resources to verify things operate</td> + </tr> + <tr> + <td>org.jclouds.provider/eucalyptus-partnercloud-s3</td> + <td>blobstore</td> + <td>US-CA</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410018000&name=eucalyptus-partnercloud-s3.txt&token=d967dc03d3d8a07e389b8848d051e216";>unstable</a></td> + <td>acls are not compatible with s3 (testPublicReadOnObject,testPublicWriteOnObject,testUpdateObjectACL); lack of NextMarker makes list continuations unreliable (testListContainerMarker testPutMoreThanSingleListing); different http code on etag conditional (testGetIfMatch)</td> + </tr> + <tr> + <td>org.jclouds.provider/gogrid</td> + <td>compute</td> + <td>US-CA,US-VA</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410019000&name=gogrid.txt&token=b556956bf7b31350ac00ae38f4dfbafb";>unstable</a></td> + <td>sometimes metadata like running status flip off our tests. Since I cannot get a clean run after several tries, I marking this unstable conceding most tests do pass.</td> + </tr> + <tr> + <td>org.jclouds.provider/greenhousedata-element-vcloud</td> + <td>compute</td> + <td>US-WY</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410026000&name=greenhousedata-element-vcloud.txt&token=6a892bf558d77b858e0c788ed803c41d";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/ninefold-storage</td> + <td>blobstore</td> + <td>AU-NSW</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410031000&name=ninefold-storage.txt&token=e491d8344613bae591f7760d4cb7a2e5";>pass</a></td> + <td>see note on atmos. operations except ones requiring ListContainerOptions.recursive operate</td> + </tr> + <tr> + <td>org.jclouds.provider/openhosting-east1</td> + <td>compute</td> + <td>US-VA</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410016000&name=openhosting-east1.txt&token=84ef8be1ececcd191376975208689e6e";>pass</a></td> + <td>works from a computeService perspective, but donât expect openjdk to install properly on their default image, as the tests show thereâs problems installing it</td> + </tr> + <tr> + <td>org.jclouds.provider/rimuhosting</td> + <td>compute</td> + <td>NZ-AUK,US-TX,AU-NSW,GB-LND</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410033001&name=rimuhosting.txt&token=33f5976e615fc8db2017379a89a47dad";>unstable</a></td> + <td>rimuhosting works while servers are launched sequentially. During the tests, servers launched sequentially operated as expected, but when 2 were launched at the same time, we started to receive unexpected content back from the rest api</td> + </tr> + <tr> + <td>org.jclouds.provider/savvis-symphonyvpdc</td> + <td>compute</td> + <td>US,CA</td> + <td><a href="http://jclouds.googlecode.com/issues/attachment?aid=6410011000&name=jclouds_savvis-symphonyvpdc_livetests_reports_07282011.zip&token=f95192bf5511519333f1187ac64c7afd";>unstable</a></td> + <td>NOTE this provider does not yet implement ComputeService interface, so you have to use the provider api; a few minor tests fail, and since we donât have comprehensive support due to lacking ComputeService impl, marking unstable</td> + </tr> + <tr> + <td>org.jclouds.provider/serverlove-z1-man</td> + <td>compute</td> + <td>GB-MAN</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410012000&name=serverlove-z1-man.txt&token=3c566c0d55d469a991ca23d99f1e2763";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/skalicloud-sdg-my</td> + <td>compute</td> + <td>MY-10</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410013000&name=skalicloud-sdg-my.txt&token=2ce8ca22fe95fb9ea7158895f74f7033";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.provider/slicehost</td> + <td>compute</td> + <td>US-IL,US-TX,US-MO</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410006000&name=slicehost.txt&token=d25355a92499ad9b3e9c8687b4ef0020";>pass</a></td> + <td>slicehost slice status is sometimes inconsistent and reports pending when in active state</td> + </tr> + <tr> + <td>org.jclouds.provider/stratogen-vcloud-mycloud</td> + <td>compute</td> + <td>GB</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410030000&name=stratogen-vcloud-mycloud.txt&token=28eccdc143d550c0855c6973bcb0f9cf";>pass</a></td> + <td>passes critical tests, and a re-run should go clean</td> + </tr> + <tr> + <td>org.jclouds.provider/synaptic-storage</td> + <td>blobstore</td> + <td>US-VA,US-TX</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410040000&name=synaptic-storage.txt&token=90a28048e50b5f9777136eb398ac883a";>pass</a></td> + <td>see note on atmos. operations except ones requiring ListContainerOptions.recursive operate</td> + </tr> + <tr> + <td>org.jclouds.provider/trmk-ecloud</td> + <td>compute</td> + <td>US-FL,NL-NH</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410023000&name=trmk-ecloud.txt&token=488128a5141a3931a5c5fca1609cb028";>pass</a></td> + <td>functionality works, with a few glitches: overriding credentials via runScriptOnNodes doesnât seem to apply (testAScriptExecutionAfterBootWithBasicTemplate);NPE attempting to create a new node after closing and recreating your context in the same VM (testCreateAnotherNodeWithANewContextToEnsureSharedMemIsntRequired)</td> + </tr> + <tr> + <td>org.jclouds.provider/trmk-vcloudexpress</td> + <td>compute</td> + <td>US-FL</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410032000&name=trmk-vcloudexpress.txt&token=2e9c483b5870486cc8f4027cfce3419e";>pass</a></td> + <td>same glitches as ecloud</td> + </tr> + </tbody> </table> - <table> -<thead> -<tr> -<th> <em>maven dependency</em> </th> -<th> <em>abstraction</em> </th> -<th> <em>endpoint tested</em> </th> -<th> <em>result</em> </th> -<th> <em>notes</em> </th> -</tr> -</thead> -<tbody> -<tr> -<td> org.jclouds.api/atmos</td> -<td> blobstore</td> -<td> </td> -<td> pass</td> -<td> one exception ListContainerOptions.recursive listings via BlobStore Map interfaces do not actually recurse. This is <a href="http://code.google.com/p/jclouds/issues/detail?id=654";>issue 654</a></td> -</tr> -<tr> -<td> org.jclouds.api/byon</td> -<td> compute</td> -<td> </td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410038000&name=byon.txt&token=cf5c6af93dcbfba99b5d8362eebb8ddf";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.api/cloudfiles</td> -<td> blobstore</td> -<td> </td> -<td> pass</td> -<td> didn't test directly, rather via cloudfiles-<code>*</code> </td> -</tr> -<tr> -<td> org.jclouds.api/cloudservers</td> -<td> blobstore</td> -<td> </td> -<td> pass</td> -<td> didn't test directly, rather via cloudservers-<code>*</code> </td> -</tr> -<tr> -<td> org.jclouds.api/deltacloud</td> -<td> compute</td> -<td> </td> -<td> unknown</td> -<td> didn't test, but suspect this doesn't work as we were on a snapshot version of deltacloud last time</td> -</tr> -<tr> -<td> org.jclouds.api/elasticstack</td> -<td> compute</td> -<td> </td> -<td> pass</td> -<td> didn't test directly, rather through elastichosts-<code>*</code></td> -</tr> -<tr> -<td> org.jclouds.api/eucalyptus</td> -<td> compute</td> -<td> </td> -<td> unknown</td> -<td> was not able to get a hold of a stable env</td> -</tr> -<tr> -<td> org.jclouds.api/filesystem</td> -<td> blobstore</td> -<td> </td> -<td> pass</td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.api/nova</td> -<td> compute</td> -<td> </td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410022000&name=nova-live-tests.txt&token=cdd95bcdac61c3f2e15b0103a6953fdc";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.api/swift</td> -<td> blobstore</td> -<td> http://50.16.106.110:11000</td> -<td> <a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410007000&name=swift.txt&token=697430c5d84333a4a901a060b5c4f616";>pass</a> </td> -<td> </td> -</tr> -<tr> -<td> org.jclouds.api/vcloud</td> -<td> compute</td> -<td> </td> -<td> pass</td> -<td> tested via greenhousedata-element-vcloud</td> -</tr> -<tr> -<td> org.jclouds.api/walrus</td> -<td> blobstore</td> -<td> </td> -<td> unstable</td> -<td> see eucalyptus-partnercloud-s3</td> -</tr> -</tbody> + <thead> + <tr> + <th><em>maven dependency</em></th> + <th><em>abstraction</em></th> + <th><em>endpoint tested</em></th> + <th><em>result</em></th> + <th><em>notes</em></th> + </tr> + </thead> + <tbody> + <tr> + <td>org.jclouds.api/atmos</td> + <td>blobstore</td> + <td>Â </td> + <td>pass</td> + <td>one exception ListContainerOptions.recursive listings via BlobStore Map interfaces do not actually recurse. This is <a href="http://code.google.com/p/jclouds/issues/detail?id=654";>issue 654</a></td> + </tr> + <tr> + <td>org.jclouds.api/byon</td> + <td>compute</td> + <td>Â </td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410038000&name=byon.txt&token=cf5c6af93dcbfba99b5d8362eebb8ddf";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.api/cloudfiles</td> + <td>blobstore</td> + <td>Â </td> + <td>pass</td> + <td>didnât test directly, rather via cloudfiles-<code class="language-plaintext highlighter-rouge">*</code></td> + </tr> + <tr> + <td>org.jclouds.api/cloudservers</td> + <td>blobstore</td> + <td>Â </td> + <td>pass</td> + <td>didnât test directly, rather via cloudservers-<code class="language-plaintext highlighter-rouge">*</code></td> + </tr> + <tr> + <td>org.jclouds.api/deltacloud</td> + <td>compute</td> + <td>Â </td> + <td>unknown</td> + <td>didnât test, but suspect this doesnât work as we were on a snapshot version of deltacloud last time</td> + </tr> + <tr> + <td>org.jclouds.api/elasticstack</td> + <td>compute</td> + <td>Â </td> + <td>pass</td> + <td>didnât test directly, rather through elastichosts-<code class="language-plaintext highlighter-rouge">*</code></td> + </tr> + <tr> + <td>org.jclouds.api/eucalyptus</td> + <td>compute</td> + <td>Â </td> + <td>unknown</td> + <td>was not able to get a hold of a stable env</td> + </tr> + <tr> + <td>org.jclouds.api/filesystem</td> + <td>blobstore</td> + <td>Â </td> + <td>pass</td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.api/nova</td> + <td>compute</td> + <td>Â </td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410022000&name=nova-live-tests.txt&token=cdd95bcdac61c3f2e15b0103a6953fdc";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.api/swift</td> + <td>blobstore</td> + <td>http://50.16.106.110:11000</td> + <td><a href="http://code.google.com/p/jclouds/issues/attachmentText?id=641&aid=6410007000&name=swift.txt&token=697430c5d84333a4a901a060b5c4f616";>pass</a></td> + <td>Â </td> + </tr> + <tr> + <td>org.jclouds.api/vcloud</td> + <td>compute</td> + <td>Â </td> + <td>pass</td> + <td>tested via greenhousedata-element-vcloud</td> + </tr> + <tr> + <td>org.jclouds.api/walrus</td> + <td>blobstore</td> + <td>Â </td> + <td>unstable</td> + <td>see eucalyptus-partnercloud-s3</td> + </tr> + </tbody> </table> - <div class="row clearfix"> <div id="footer" class="col-md-12 column"> <div id="footer">
Modified: jclouds/site-content/releasenotes/1.1.1/index.html URL: http://svn.apache.org/viewvc/jclouds/site-content/releasenotes/1.1.1/index.html?rev=1923693&r1=1923692&r2=1923693&view=diff ============================================================================== --- jclouds/site-content/releasenotes/1.1.1/index.html (original) +++ jclouds/site-content/releasenotes/1.1.1/index.html Mon Feb 10 07:25:53 2025 @@ -150,22 +150,20 @@ <h1>Release Notes Version 1.1.1</h1> </div> - <h2>Introduction</h2> + <h2 id="introduction">Introduction</h2> -<p>The 1.1.1 release of jclouds is a bugfix release addressing 2 defects in the "aws-ec2" provider. +<p>The 1.1.1 release of jclouds is a bugfix release addressing 2 defects in the âaws-ec2â provider. Many thanks to Andrew Phillips for working hard to get this cut in the same day.</p> -<p>If you are using the "aws-ec2" provider you should update to version 1.1.1 immediately. If you are not, you can ignore this release.</p> - -<h2>Defects Addressed</h2> +<p>If you are using the âaws-ec2â provider you should update to version 1.1.1 immediately. If you are not, you can ignore this release.</p> +<h2 id="defects-addressed">Defects Addressed</h2> <ul> -<li><a href="http://code.google.com/p/jclouds/issues/detail?id=660";>null group on nodes from aws-ec2 provider</a></li> -<li><a href="http://code.google.com/p/jclouds/issues/detail?id=662";>ec2 ami query syntax from < 1.1.0 doesn't work on >= 1.1.0</a></li> + <li><a href="http://code.google.com/p/jclouds/issues/detail?id=660";>null group on nodes from aws-ec2 provider</a></li> + <li><a href="http://code.google.com/p/jclouds/issues/detail?id=662";>ec2 ami query syntax from < 1.1.0 doesnât work on >= 1.1.0</a></li> </ul> - -<h2>Tracking</h2> +<h2 id="tracking">Tracking</h2> <p>Status of the release is tracked in <a href="http://code.google.com/p/jclouds/issues/detail?id=661";>issue 661</a></p> Modified: jclouds/site-content/releasenotes/1.2.2/index.html URL: http://svn.apache.org/viewvc/jclouds/site-content/releasenotes/1.2.2/index.html?rev=1923693&r1=1923692&r2=1923693&view=diff ============================================================================== --- jclouds/site-content/releasenotes/1.2.2/index.html (original) +++ jclouds/site-content/releasenotes/1.2.2/index.html Mon Feb 10 07:25:53 2025 @@ -150,9 +150,9 @@ <h1>Release Notes Version 1.2.2</h1> </div> - <h2>Introduction</h2> + <h2 id="introduction">Introduction</h2> -<p>The 1.2.2 release of jclouds is a bug fixing release that addresses some of the important issues we've discovered while developing the next major release (1.3.0) +<p>The 1.2.2 release of jclouds is a bug fixing release that addresses some of the important issues weâve discovered while developing the next major release (1.3.0) A total of <a href="http://code.google.com/p/jclouds/issues/list?can=1&q=label%3AMilestone%3A1.2.1%2C1.2.2+status%3AFixed&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary&cells=tiles";>3 Issues</a> were addressed.</p> @@ -160,45 +160,40 @@ were addressed.</p> Next release is schedule for the beginning of January 2012. Look out for progress including vCloud1.5, Voxel, CloudStack and VirtualBox.</p> <p>Please <a href="http://code.google.com/p/jclouds/issues";>submit your own ideas</a> and <a href="http://groups.google.com/group/jclouds";>let us know</a> if there are features -you'd like to see, need help on, or are interested in contributing. Make sure you follow us on <a href="http://twitter.com/#!/jclouds";>Twitter</a> for updates.</p> - -<h2>Credits</h2> +youâd like to see, need help on, or are interested in contributing. Make sure you follow us on <a href="http://twitter.com/#!/jclouds";>Twitter</a> for updates.</p> +<h2 id="credits">Credits</h2> <p>Many thanks to everyone who contributed their time and effort in order to make this release happen.</p> -<h2>New Features</h2> - -<h3>Amazon EC2 Enhancements</h3> +<h2 id="new-features">New Features</h2> +<h3 id="amazon-ec2-enhancements">Amazon EC2 Enhancements</h3> <p>We now support the Oregon (us-west-2) and Sao Paolo (sa-east-1) datacenters</p> -<h3>Enhancements</h3> +<h3 id="enhancements">Enhancements</h3> <ul> -<li><a href="http://code.google.com/p/jclouds/issues/detail?id=727";>enable ubuntu Natty on cloudsigma-zrh</a></li> -<li><a href="http://code.google.com/p/jclouds/issues/detail?id=780";>add new sa-east-1 region</a></li> + <li><a href="http://code.google.com/p/jclouds/issues/detail?id=727";>enable ubuntu Natty on cloudsigma-zrh</a></li> + <li><a href="http://code.google.com/p/jclouds/issues/detail?id=780";>add new sa-east-1 region</a></li> </ul> - -<h2>Defects Addressed</h2> +<h2 id="defects-addressed">Defects Addressed</h2> <ul> -<li><a href="http://code.google.com/p/jclouds/issues/detail?id=660";>null group on nodes from aws-ec2 provider</a></li> + <li><a href="http://code.google.com/p/jclouds/issues/detail?id=660";>null group on nodes from aws-ec2 provider</a></li> </ul> - -<h2>API Breakers</h2> - +<h2 id="api-breakers">API Breakers</h2> <p>There are no api breakers in this release and nothing new has been deprecated. Deprecated methods will be removed in the next release.</p> -<h2>Cool Stuff</h2> +<h2 id="cool-stuff">Cool Stuff</h2> -<h2>Tracking</h2> +<h2 id="tracking">Tracking</h2> <p>Status of release 1.2.2 is tracked in <a href="http://code.google.com/p/jclouds/issues/detail?id=793";>issue 793</a></p> -<h2>Test Results</h2> +<h2 id="test-results">Test Results</h2> <p>TODO</p>
