You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jclouds.apache.org by na...@apache.org on 2016/08/31 08:51:36 UTC
[1/5] jclouds-site git commit: Added warning for snapshot downloads
and added License link
Repository: jclouds-site
Updated Branches:
refs/heads/master 46d8da345 -> a31b6f947
Added warning for snapshot downloads and added License link
Project: http://git-wip-us.apache.org/repos/asf/jclouds-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/jclouds-site/commit/f33f61f5
Tree: http://git-wip-us.apache.org/repos/asf/jclouds-site/tree/f33f61f5
Diff: http://git-wip-us.apache.org/repos/asf/jclouds-site/diff/f33f61f5
Branch: refs/heads/master
Commit: f33f61f57a6c3eba81410503c27e63416c1ce9e4
Parents: 46d8da3
Author: Ignasi Barrera <na...@apache.org>
Authored: Mon Aug 29 23:34:58 2016 +0200
Committer: Ignasi Barrera <na...@apache.org>
Committed: Mon Aug 29 23:43:49 2016 +0200
----------------------------------------------------------------------
_includes/navbar.html | 1 +
start/install.md | 12 ++++++++++++
2 files changed, 13 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/jclouds-site/blob/f33f61f5/_includes/navbar.html
----------------------------------------------------------------------
diff --git a/_includes/navbar.html b/_includes/navbar.html
index 8fa7c68..0db64b0 100755
--- a/_includes/navbar.html
+++ b/_includes/navbar.html
@@ -56,6 +56,7 @@
<a href="#" class="dropdown-toggle" data-toggle="dropdown">About Apache<strong class="caret"></strong></a>
<ul class="dropdown-menu">
<li><a href="http://www.apache.org">The Apache Software Foundation</a></li>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
<li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
<li><a href="http://www.apache.org/security/">Report a Vulnerability</a></li>
http://git-wip-us.apache.org/repos/asf/jclouds-site/blob/f33f61f5/start/install.md
----------------------------------------------------------------------
diff --git a/start/install.md b/start/install.md
index bbc16fd..3691388 100644
--- a/start/install.md
+++ b/start/install.md
@@ -43,6 +43,10 @@ If you do not have a *pom.xml* file, you can copy and paste the one below. If yo
###�Using the daily builds
+<div class="alert alert-danger">
+<strong>Warning!</strong> These are snapshot builds; untested builds provided for your convenience. They have not been tested, and are not official releases of the Apache jclouds project or the Apache Software Foundation.
+</div>
+
If you want to use the bleeding edge release of jclouds, you'll need to setup a maven dependency pointing to our snapshot repository. You need to update your repositories and add the following in your project's pom.xml:
{% highlight xml %}
@@ -88,6 +92,10 @@ You can add jclouds to your *project.clj* like below, supporting clojure 1.2 and
### Using the daily builds
+<div class="alert alert-danger">
+<strong>Warning!</strong> These are snapshot builds; untested builds provided for your convenience. They have not been tested, and are not official releases of the Apache jclouds project or the Apache Software Foundation.
+</div>
+
You can add jclouds snapshots to your *project.clj* like below:
{% highlight clojure %}
@@ -127,6 +135,10 @@ Then, add jclouds to your *build.xml* as shown below:
### Using the daily builds
+<div class="alert alert-danger">
+<strong>Warning!</strong> These are snapshot builds; untested builds provided for your convenience. They have not been tested, and are not official releases of the Apache jclouds project or the Apache Software Foundation.
+</div>
+
You will need to install [maven ant tasks](http://maven.apache.org/ant-tasks/index.html). Then, add jclouds snapshot dependencies to your *build.xml* as shown below:
{% highlight xml %}
[5/5] jclouds-site git commit: Remove dead links to the old HEAD
Javadoc site
Posted by na...@apache.org.
Remove dead links to the old HEAD Javadoc site
Project: http://git-wip-us.apache.org/repos/asf/jclouds-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/jclouds-site/commit/a31b6f94
Tree: http://git-wip-us.apache.org/repos/asf/jclouds-site/tree/a31b6f94
Diff: http://git-wip-us.apache.org/repos/asf/jclouds-site/diff/a31b6f94
Branch: refs/heads/master
Commit: a31b6f947c850a32045cbfc21d9445f86bd8baea
Parents: 1c03555
Author: Andrew Phillips <an...@apache.org>
Authored: Tue Aug 30 22:35:23 2016 -0400
Committer: Ignasi Barrera <na...@apache.org>
Committed: Wed Aug 31 10:49:47 2016 +0200
----------------------------------------------------------------------
guides/rackspace.md | 5 +----
start/blobstore.md | 2 +-
2 files changed, 2 insertions(+), 5 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/jclouds-site/blob/a31b6f94/guides/rackspace.md
----------------------------------------------------------------------
diff --git a/guides/rackspace.md b/guides/rackspace.md
index 05b085a..1a299fa 100644
--- a/guides/rackspace.md
+++ b/guides/rackspace.md
@@ -281,7 +281,6 @@ Cloud Load Balancers works with the Rackspace layer in jclouds that is used to a
You can access Cloud Databases with the jclouds openstack-trove API by specifying the rackspace clouddatabases providers "rackspace-clouddatabases-us" and "rackspace-clouddatabases-uk". The -us one can be used to access the United States regions, and the -uk one is for the United Kingdom regions. The examples use the -us provider, but the providers are interchangeable (but regions will differ).
1. The Rackspace compatible API for Cloud Databases is org.jclouds.openstack.trove.v1.TroveApi - All other APIs for working with Cloud Databases are accessible via the TroveApi.
-1. You can find these APIs in the latest [Javadoc](http://javadocs-labs-openstack.jclouds.cloudbees.net/).
### <a id="databases-source"></a>The Source Code
@@ -321,8 +320,7 @@ In addition to the create database instance example, by going through the cloudd
You can access Cloud Auto Scale with the jclouds rackspace-autoscale API by specifying the Auto Scale provider "rackspace-autoscale-us". There is no -uk provider at this time.
-1. The Rackspace compatible API for Auto Scale is org.jclouds.rackspace.autoscale.v1.AutoscaleApi - All other APIs for working with Auto Scale are accessible via the [AutoscaleApi](http://javadocs-labs-openstack.jclouds.cloudbees.net/org/jclouds/rackspace/autoscale/v1/AutoscaleApi.html).
-1. You can find these APIs in the latest [Javadoc](http://javadocs-labs-openstack.jclouds.cloudbees.net/).
+1. The Rackspace compatible API for Auto Scale is org.jclouds.rackspace.autoscale.v1.AutoscaleApi - All other APIs for working with Auto Scale are accessible via the [AutoscaleApi](http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/rackspace/autoscale/v1/AutoscaleApi.html).
### <a id="autoscale-source"></a>The Source Code
@@ -364,7 +362,6 @@ In addition to the CreatePolicy example, by going through the Auto Scale example
Cloud Queues works with the OpenStack layer in jclouds that is used to access features common to all OpenStack Marconi queuing systems.
1. The OpenStack API for Cloud Queues is the org.jclouds.openstack.marconi.v1.MarconiApi. All other APIs for working with queues are accessible via the MarconiApi.
-1. You can find these APIs in the latest [Javadoc](http://javadocs-labs-openstack.jclouds.cloudbees.net).
### <a id="queues-source"></a>The Source Code
http://git-wip-us.apache.org/repos/asf/jclouds-site/blob/a31b6f94/start/blobstore.md
----------------------------------------------------------------------
diff --git a/start/blobstore.md b/start/blobstore.md
index 9063203..719d339 100644
--- a/start/blobstore.md
+++ b/start/blobstore.md
@@ -153,7 +153,7 @@ context.close();
{% endhighlight %}
There are many options available for creating a `Context`. Please see the
-[ContextBuilder](http://javadocs.jclouds.cloudbees.net/org/jclouds/ContextBuilder.html) Javadocs for
+[ContextBuilder](http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/ContextBuilder.html) Javadocs for
a detailed description.
[2/5] jclouds-site git commit: Added link to the GSoC post in the
landing page
Posted by na...@apache.org.
Added link to the GSoC post in the landing page
Project: http://git-wip-us.apache.org/repos/asf/jclouds-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/jclouds-site/commit/e52f85e3
Tree: http://git-wip-us.apache.org/repos/asf/jclouds-site/tree/e52f85e3
Diff: http://git-wip-us.apache.org/repos/asf/jclouds-site/diff/e52f85e3
Branch: refs/heads/master
Commit: e52f85e330f925ca1df2d07d3199d215d4cb7d08
Parents: f33f61f
Author: Ignasi Barrera <na...@apache.org>
Authored: Mon Aug 29 23:35:23 2016 +0200
Committer: Ignasi Barrera <na...@apache.org>
Committed: Mon Aug 29 23:43:50 2016 +0200
----------------------------------------------------------------------
_posts/2016-08-22-arbitrary-cpu-ram.md | 1 +
1 file changed, 1 insertion(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/jclouds-site/blob/e52f85e3/_posts/2016-08-22-arbitrary-cpu-ram.md
----------------------------------------------------------------------
diff --git a/_posts/2016-08-22-arbitrary-cpu-ram.md b/_posts/2016-08-22-arbitrary-cpu-ram.md
index e2d25a7..e5acd01 100644
--- a/_posts/2016-08-22-arbitrary-cpu-ram.md
+++ b/_posts/2016-08-22-arbitrary-cpu-ram.md
@@ -5,6 +5,7 @@ date: 2016-08-22 07:00:00+00:00
layout: post
slug: arbitrary-cpu-ram
title: Arbitrary CPU and RAM supported in the ComputeService
+quicknews: Read about our <strong>GSoC 2016 project</strong>! Support for arbitrary CPU and RAM has been added to the Compute abstraction
---
As part of a [Google Summer of Code](https://developers.google.com/open-source/gsoc/) project has been added a feature to allow users to set manually specific values of CPU and RAM.
[4/5] jclouds-site git commit: Language and minor style tweaks to
Ivan's nice guest blog
Posted by na...@apache.org.
Language and minor style tweaks to Ivan's nice guest blog
Project: http://git-wip-us.apache.org/repos/asf/jclouds-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/jclouds-site/commit/1c035552
Tree: http://git-wip-us.apache.org/repos/asf/jclouds-site/tree/1c035552
Diff: http://git-wip-us.apache.org/repos/asf/jclouds-site/diff/1c035552
Branch: refs/heads/master
Commit: 1c035552ddff1aba92cd974065867f30b89fb293
Parents: 4d46742
Author: Andrew Phillips <an...@apache.org>
Authored: Tue Aug 30 22:27:39 2016 -0400
Committer: Ignasi Barrera <na...@apache.org>
Committed: Wed Aug 31 10:48:58 2016 +0200
----------------------------------------------------------------------
_posts/2016-08-22-arbitrary-cpu-ram.md | 64 +++++++++++++++--------------
1 file changed, 33 insertions(+), 31 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/jclouds-site/blob/1c035552/_posts/2016-08-22-arbitrary-cpu-ram.md
----------------------------------------------------------------------
diff --git a/_posts/2016-08-22-arbitrary-cpu-ram.md b/_posts/2016-08-22-arbitrary-cpu-ram.md
index e5acd01..85939bd 100644
--- a/_posts/2016-08-22-arbitrary-cpu-ram.md
+++ b/_posts/2016-08-22-arbitrary-cpu-ram.md
@@ -4,29 +4,33 @@ comments: true
date: 2016-08-22 07:00:00+00:00
layout: post
slug: arbitrary-cpu-ram
-title: Arbitrary CPU and RAM supported in the ComputeService
+title: Adding support for arbitrary CPU and RAM to ComputeService
quicknews: Read about our <strong>GSoC 2016 project</strong>! Support for arbitrary CPU and RAM has been added to the Compute abstraction
---
-As part of a [Google Summer of Code](https://developers.google.com/open-source/gsoc/) project has been added a feature to allow users to set manually specific values of CPU and RAM.
+Through of a [Google Summer of Code](https://developers.google.com/open-source/gsoc/) project, Apache jclouds now allows users to manually set arbitrary values for desired CPU and RAM of compute instances.
<!--more-->
-The previous Compute Service abstraction assumed that all providers had hardware profiles, a list of profiles describing different cpu, memory and disk configurations that can be used to run a node. Some providers, such as [ProfitBricks](https://www.profitbricks.com/) or [ElasticHosts](https://www.elastichosts.com/), do not have the hardware profiles concept and the previous implementation provides a fixed configuration with a fixed (hardcoded) list just to conform the interface. The new implementation allows to use custom hardwares or both (when supported) hardware profiles and custom hardwares.
+The previous ComputeService abstraction assumed that all providers have hardware profiles: a list of "specs" of available CPU, memory and disk configurations that can be used when creating a node. Some providers, such as [ProfitBricks](https://www.profitbricks.com/) or [ElasticHosts](https://www.elastichosts.com/), do not have the concept of hardware profiles; the previous implementation provided a fixed configuration with a fixed, hard-coded list of "fake" profiles just to conform to the Apache jclouds interface. The new implementation allows users to create nodes with arbitrary settings or, where supported, to choose between provided hardware profiles or custom settings.
-Note that using hardware profiles provides hardware optimization or in some cases cheaper pricings.
+Note that pre-defined hardware profiles can sometimes be more performant and/or cheaper than custom settings.
-### How to use custom hardwares
-There are two ways to use a custom hardware: setting in on the hardwareId or specifying cores and ram values using minCores and minRam.
+### How to create a node with custom settings
+There are two ways to use the new feature: setting an appropriate value for the `hardwareId` property, or specifying the desired number of cores, amount of RAM and, in some cases, disk size via the `minCores`, `minRam` and `minDisk` properties.
-#### Custom hardware using hardwareId
+#### Creating a node with custom settings using the `hardwareId`
-When user set the hardwareId, the Template Builder first check if the provided hardwareId corresponds with an existent hardware profile, and if it corresponds, it would use it. In case that the provided hardwareId do not match with an existing hardware profile and have the automatic hardwareId format, it would use a custom hardware.
+If the user sets the `hardwareId` property, the Apache jclouds [TemplateBuilder](/reference/javadoc/1.9.x/org/jclouds/compute/domain/TemplateBuilder.html) implementation first checks if the provided ID matches an existing hardware profile. If so, the matching profile is used.
-To set CPU and RAM with hardwareId you have to set the hardwareId using template builder with the format:
+If the provided ID does _not_ match an existing hardware profile, and it has the format of an "automatic" hardware ID, Apache jclouds will create a node with custom settings.
-`automatic:cores=2;ram=4096`
+To set CPU and RAM via an automatic hardware ID, [set the `hardwareId`](https://jclouds.apache.org/reference/javadoc/1.9.x/org/jclouds/compute/domain/TemplateBuilder.html#hardwareId\(java.lang.String\)) property on your `TemplateBuilder` to a value with the format:
-as you can see in the following example:
+```
+automatic:cores=<num-cores>;ram=<memory-size>
+```
+
+For example:
{% highlight Java %}
Template template = templateBuilder
@@ -35,7 +39,7 @@ Template template = templateBuilder
compute.createNodesInGroup("jclouds", 1, template);
{% endhighlight %}
-In providers that configure disks based on the volume information provided in the hardware profile you have to specify also the disk size, like in ProfitBricks, where disk is mandatory, you need to specify it to use custom machines:
+For providers such as ProfitBricks that configure disks based on the volume information provided in the hardware profile, you will also need to specify the desired disk size:
{% highlight Java %}
Template template = templateBuilder
@@ -44,7 +48,7 @@ Template template = templateBuilder
compute.createNodesInGroup("jclouds", 1, template);
{% endhighlight %}
-To help building the automatic hardwareId, the `automaticHardwareIdSpecBuilder` utility creates an automaticHardwareId string with the provided values of cores, ram and optional disk size.
+You can use the `AutomaticHardwareIdSpec` to more easily construct automatic hardware IDs:
{% highlight Java %}
Template template = templateBuilder
@@ -55,13 +59,11 @@ Template template = templateBuilder
compute.createNodesInGroup("jclouds", 1, template);
{% endhighlight %}
+#### Creating a node with custom settings using `minCores`, `minRam` and `minDisk`
+If the user sets the `minCores`, `minRam` and, where required, `minDisk` properties, Apache jclouds first checks if a hardware profile matching the desired values exists. If no such profile can be found, Apache jclouds will create a node with custom settings.
-#### Custom hardware using minCores and minRam
-
-When user set minCores and minRam, first the template builder checks if a hardware profile matches with the provided minRam and minCores. If not, the templateBuilder will use the automatic hardware.
-
-To set up custom hardwares using minRam and minCores you have to set them using template builder.
+Set the appropriate properties on your `TemplateBuilder`:
{% highlight Java %}
Template template = templateBuilder
@@ -71,7 +73,7 @@ Template template = templateBuilder
compute.createNodesInGroup("jclouds", 1, template);
{% endhighlight %}
-In providers that need to specify disk, set also minDisk:
+For providers that need a disk size specification also set `minDisk`:
{% highlight Java %}
Template template = templateBuilder
@@ -82,30 +84,30 @@ Template template = templateBuilder
compute.createNodesInGroup("jclouds", 1, template);
{% endhighlight %}
-### Providers supported
-There are several providers that support arbitrary values of CPU and RAM like Docker, ElasticHosts, Google Compute Engine, etc. The first available providers supported by the new feature are:
+### Supported providers
-* [Google Compute Engine](https://cloud.google.com/compute/)
-* [ProfitBricks](https://www.profitbricks.com/)
+There are several providers that support arbitrary values of CPU and RAM, such as Docker, ElasticHosts, Google Compute Engine, etc. The first available Apache jclouds providers to support this feature are:
-To configure the new feature in other providers add a bind() to the `ArbitraryCpuRamTemplateBuilderImpl` class at the provider's context module:
+* [Google Compute Engine](/guides/google/)
+* [ProfitBricks](/guides/profitbricks/)
+
+To add this feature to other providers, bind the `ArbitraryCpuRamTemplateBuilderImpl` class in the provider's context module:
{% highlight Java %}
bind(TemplateBuilderImpl.class).to(ArbitraryCpuRamTemplateBuilderImpl.class);
{% endhighlight %}
-Also is necessary to modify the function that transform a node from the provider model to the portable model of jclouds, to include the new automatic hardwareId (if apply).
+You will also need to modify the function that converts the representation of a node from the provider's model to the jclouds representation, so that the required automatic `hardwareId` is included.
### Further development
-* **Support other providers**: add support for other providers such as [ElasticHosts](https://www.elastichosts.com/) and [Docker](https://www.docker.com/).
-* **Improve AutomaticHardwareSpec**: improve the AutomaticHardwareSpec with specific parsers for every parameter in order to support more custom parameters and some fields, like bootDisk and durable (part of volumes), that are currently hardcoded to true.
-* **Usage examples of the new features**: create examples of the new features in the jclouds-examples repo.
-* **Custom TemplateBuilderImpl for ProfitBricks**: add a custom implementation of the TemplateBuilderImpl to fail early when users don't set the minDisk.
-
+* **Support other providers**: add support for other providers such as [ElasticHosts](https://www.elastichosts.com/) or [Docker](https://www.docker.com/).
+* **Improve `AutomaticHardwareSpec`**: add parsers to `AutomaticHardwareSpec` for further properties that can have arbitrary values, such as `bootDisk` or `durable` (part of a volume description).
+* **Usage examples of the new features**: add examples of using the new features to the [jclouds-examples](http://github.com/jclouds/jclouds-examples) repo.
+* **Custom `TemplateBuilderImpl` for ProfitBricks**: add a custom implementation of the `TemplateBuilderImpl` that fails fast if `minDisk` is not set.
### Special thanks
Special thanks to [Ignasi Barrera](https://github.com/nacx) for all the help, [Andrew Phillips](https://github.com/demobox) for code reviews and the rest of jclouds comunity.
-Of course, also thanks to Google for running GSoC.
+Of course, thanks also to Google for running GSoC.
[3/5] jclouds-site git commit: Simplify snapshot warning
Posted by na...@apache.org.
Simplify snapshot warning
Project: http://git-wip-us.apache.org/repos/asf/jclouds-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/jclouds-site/commit/4d46742a
Tree: http://git-wip-us.apache.org/repos/asf/jclouds-site/tree/4d46742a
Diff: http://git-wip-us.apache.org/repos/asf/jclouds-site/diff/4d46742a
Branch: refs/heads/master
Commit: 4d46742a3142391a53dfe16f815f48069d176f33
Parents: e52f85e
Author: Ignasi Barrera <na...@apache.org>
Authored: Tue Aug 30 09:51:20 2016 +0200
Committer: Ignasi Barrera <na...@apache.org>
Committed: Tue Aug 30 09:51:20 2016 +0200
----------------------------------------------------------------------
start/install.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/jclouds-site/blob/4d46742a/start/install.md
----------------------------------------------------------------------
diff --git a/start/install.md b/start/install.md
index 3691388..5505463 100644
--- a/start/install.md
+++ b/start/install.md
@@ -44,7 +44,7 @@ If you do not have a *pom.xml* file, you can copy and paste the one below. If yo
###�Using the daily builds
<div class="alert alert-danger">
-<strong>Warning!</strong> These are snapshot builds; untested builds provided for your convenience. They have not been tested, and are not official releases of the Apache jclouds project or the Apache Software Foundation.
+<strong>Warning!</strong> These are untested snapshot builds provided for convenience; they are not official releases of the Apache jclouds project, or the Apache Software Foundation.
</div>
If you want to use the bleeding edge release of jclouds, you'll need to setup a maven dependency pointing to our snapshot repository. You need to update your repositories and add the following in your project's pom.xml:
@@ -93,7 +93,7 @@ You can add jclouds to your *project.clj* like below, supporting clojure 1.2 and
### Using the daily builds
<div class="alert alert-danger">
-<strong>Warning!</strong> These are snapshot builds; untested builds provided for your convenience. They have not been tested, and are not official releases of the Apache jclouds project or the Apache Software Foundation.
+<strong>Warning!</strong> These are untested snapshot builds provided for convenience; they are not official releases of the Apache jclouds project, or the Apache Software Foundation.
</div>
You can add jclouds snapshots to your *project.clj* like below:
@@ -136,7 +136,7 @@ Then, add jclouds to your *build.xml* as shown below:
### Using the daily builds
<div class="alert alert-danger">
-<strong>Warning!</strong> These are snapshot builds; untested builds provided for your convenience. They have not been tested, and are not official releases of the Apache jclouds project or the Apache Software Foundation.
+<strong>Warning!</strong> These are untested snapshot builds provided for convenience; they are not official releases of the Apache jclouds project, or the Apache Software Foundation.
</div>
You will need to install [maven ant tasks](http://maven.apache.org/ant-tasks/index.html). Then, add jclouds snapshot dependencies to your *build.xml* as shown below: