You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@deltacloud.apache.org by ma...@apache.org on 2012/10/23 13:12:57 UTC
git commit: Update site docs to include fgcp specific caveats/notes
Updated Branches:
refs/heads/master c96c7d3dd -> 8116e6a35
Update site docs to include fgcp specific caveats/notes
https://issues.apache.org/jira/browse/DTACLOUD-338
Project: http://git-wip-us.apache.org/repos/asf/deltacloud/repo
Commit: http://git-wip-us.apache.org/repos/asf/deltacloud/commit/8116e6a3
Tree: http://git-wip-us.apache.org/repos/asf/deltacloud/tree/8116e6a3
Diff: http://git-wip-us.apache.org/repos/asf/deltacloud/diff/8116e6a3
Branch: refs/heads/master
Commit: 8116e6a35a6ea0f31ada8767eafd13dd2e7da6bd
Parents: c96c7d3
Author: marios <ma...@redhat.com>
Authored: Tue Oct 23 14:07:11 2012 +0300
Committer: marios <ma...@redhat.com>
Committed: Tue Oct 23 14:07:11 2012 +0300
----------------------------------------------------------------------
site/content/addresses.md | 10 +++++-----
site/content/blob-storage.md | 2 +-
site/content/firewalls.md | 19 +++++++++++--------
site/content/images.md | 15 ++++++++++-----
site/content/load-balancers.md | 4 ++--
site/content/rest-api.md | 4 ++--
site/content/storage-resources.md | 15 ++++++++++++---
site/output/addresses.html | 10 +++++-----
site/output/blob-storage.html | 2 +-
site/output/firewalls.html | 19 +++++++++++--------
site/output/images.html | 15 ++++++++++-----
site/output/load-balancers.html | 4 ++--
site/output/rest-api.html | 2 +-
site/output/storage-resources.html | 15 ++++++++++++---
14 files changed, 85 insertions(+), 51 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/content/addresses.md
----------------------------------------------------------------------
diff --git a/site/content/addresses.md b/site/content/addresses.md
index d752120..0d802d7 100644
--- a/site/content/addresses.md
+++ b/site/content/addresses.md
@@ -11,11 +11,11 @@ title: Addresses
<h3 id="addresses">Addresses</h3>
<p>
-The addresses collection represents IP addresses and allows <strong>IP address management</strong>.
+The addresses collection represents IP addresses and allows <strong>IP address management</strong>.
</p>
<p>
-This collection is currently implemented for the Amazon EC2 cloud driver. For EC2, IP address management corresponds to Amazon's 'Elastic IP' feature.
+This collection is currently implemented for Amazon EC2 and Fujitsu GCP drivers. For EC2, IP address management corresponds to Amazon's 'Elastic IP' feature.
</p>
<br/>
@@ -72,7 +72,7 @@ The addresses collection supports these operations:
<div class="tab-content">
<div class="tab-pane active" id="tab1">
-
+
<h4>Get a list of all addresses</h4>
<p>
@@ -220,10 +220,10 @@ Date: Wed, 27 Jul 2011 13:29:00 GMT
</div>
<div class="tab-pane" id="tab4">
-<h4>Associate an adress with an instance</h4>
+<h4>Associate an address with an instance</h4>
<p>
-To associate a given address with a running instance use call <strong>POST /api/addresses/:id/associate</strong>. The client must specify the <strong>instance_id</strong> as a parameter to this call. For Amazon EC2, the specified address will replace the currently assigned public_address of the instance. A succesful operation results in a <strong>HTTP 202 Accepted</strong> response. The example client request below specifies the required instance_id parameter using the application/x-www-form-urlencoded content-type, however client can also use multipart/form-data.
+To associate a given address with a running instance use call <strong>POST /api/addresses/:id/associate</strong>. The client must specify the <strong>instance_id</strong> as a parameter to this call. For Amazon EC2, the specified address will replace the currently assigned public_address of the instance, while for the Fujitsu GCP it is added. A succesful operation results in a <strong>HTTP 202 Accepted</strong> response. The example client request below specifies the required instance_id parameter using the application/x-www-form-urlencoded content-type, however client can also use multipart/form-data.
</p>
<p>Example request:</p>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/content/blob-storage.md
----------------------------------------------------------------------
diff --git a/site/content/blob-storage.md b/site/content/blob-storage.md
index 3e24e4b..f515116 100644
--- a/site/content/blob-storage.md
+++ b/site/content/blob-storage.md
@@ -11,7 +11,7 @@ title: Blob storage
<h3 id="blob">Blob Storage</h3>
<p>
-Blob storage represents a generic key ==> value data store. It is implemented by Amazon S3 or Rackspace Cloudfiles. In Deltacloud, the organisational unit of blob storage is a bucket. Individual data items - blobs are exposed as a subcollection under each bucket.
+Blob storage represents a generic key ==> value data store, as implemented for example by Amazon S3 or Openstack swift. In Deltacloud, the organisational unit of blob storage is a bucket. Individual data items - blobs are exposed as a subcollection under each bucket.
</p>
<p>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/content/firewalls.md
----------------------------------------------------------------------
diff --git a/site/content/firewalls.md b/site/content/firewalls.md
index a4036c1..535518e 100644
--- a/site/content/firewalls.md
+++ b/site/content/firewalls.md
@@ -11,7 +11,7 @@ title: Firewalls
<h3 id="firewalls">Firewalls</h3>
<p>
-Firewalls represent sets of rules that govern the accessibility of a running instance over the public Internet. At present, only the Amazon EC2 cloud supports this collection (Amazon EC2 'Security Groups'). A firewall has these attributes:
+Firewalls represent sets of rules that govern the accessibility of a running instance over the public Internet. At present, only Amazon EC2 cloud (Amazon EC2 'Security Groups') and Fujitsu GCP support this collection. A firewall has these attributes:
</p>
<ul>
@@ -22,11 +22,11 @@ Firewalls represent sets of rules that govern the accessibility of a running ins
</ul>
<p>
-An instance is launched into a firewall by specifying the <strong>firewalls1 ... firewallsN</strong> parameters in the <strong>POST /api/instances</strong> operation (see the <a href="/instances.html#instance">Create an instance</a> section).
+For Amazon EC2, an instance is launched into a firewall by specifying the <strong>firewalls1 ... firewallsN</strong> parameters in the <strong>POST /api/instances</strong> operation (see the <a href="/instances.html#instance">Create an instance</a> section).
</p>
<p>
-Each <strong>firewall rule</strong> has a number of attributes describing the access granted to clients that want to communicate with the instance over the Internet. Each rule cosists of
+Each <strong>firewall rule</strong> has a number of attributes describing the access granted to clients that want to communicate with the instance over the Internet. Each rule consists of
</p>
<ul>
@@ -63,7 +63,8 @@ Each <strong>firewall rule</strong> has a number of attributes describing the ac
</div>
<p>
-Each rule also specifies a <strong>direction</strong>, indicating whether it applies to ingress or egress traffic.
+Each rule also specifies a <strong>direction</strong>, indicating whether it applies to ingress or egress traffic. A rule can also specify a <strong>rule_action</strong> (accept, deny), to indicate whether the firewall should accept or deny access for this traffic, and <strong>log_rule</strong> (true, false), to indicate whether an entry should be added to the log.
+
</p>
<p>
@@ -281,11 +282,13 @@ Date: Wed, 27 Jul 2011 09:47:43 GMT
</pre>
<p>
-The rules governing the deletion of a firewall are back-end cloud specific. At present, only the Amazon EC2 cloud supports the firewalls collection, so we describe the firewall deletion rules for EC2 here.
+The rules governing the deletion of a firewall are back-end cloud specific.
+</p>
+<p>
+For Fujitsu GCP, as this operation destroys the virtual system with it, all instances in the system, including the firewall need to be in the STOPPED state.
</p>
-
<p>
-It is permitted to delete a firewall that has rules defined within it, with two exceptions. You cannot delete a firewall if it is referenced by another firewall; for instance <strong>firewall_1</strong> has a rule giving access to <strong>firewall_2</strong>. An attempt to delete firewall_2 will result in the error <strong>InvalidGroup.InUse</strong>, as you can see in the example below. The second exception is that you cannot delete a firewall if there are currently any running instances within that firewall (i.e. instances that specified the given firewall when they were launched). The error message in that case would be <strong>InvalidGroup.InUse: There are active instances using security group</strong>. In both cases the error messages are propagated from the back-end cloud provider to the requesting client.
+For Amazon EC2, it is permitted to delete a firewall that has rules defined within it, with two exceptions. You cannot delete a firewall if it is referenced by another firewall; for instance <strong>firewall_1</strong> has a rule giving access to <strong>firewall_2</strong>. An attempt to delete firewall_2 will result in the error <strong>InvalidGroup.InUse</strong>, as you can see in the example below. The second exception is that you cannot delete a firewall if there are currently any running instances within that firewall (i.e. instances that specified the given firewall when they were launched). The error message in that case would be <strong>InvalidGroup.InUse: There are active instances using security group</strong>. In both cases the error messages are propagated from the back-end cloud provider to the requesting client.
</p>
<p>
@@ -324,7 +327,7 @@ Content-Length: 626
<h4>Create a firewall rule</h4>
<p>
-To create a new firewall rule within a specified firewall use call <strong>POST /api/firewalls/:id/rules</strong>. A client must supply the <strong>protocol</strong> (one of udp, tcp or icmp), <strong>port_from</strong> and <strong>port_to</strong> as parameters. Of course the client must also specify the <strong>sources</strong> to which the given rule is applied. IP addresses are specified in CIDR format sequentially: ip_address1=192.168.10.10/24, ip_address2=10.1.1.1/16 ... ip_addressN=.... The IP address '0.0.0.0/0' acts as a wildcard to specify any IP address. Source firewalls are also specified sequentially, but the <strong>owner_id</strong> of the firewall prepared for authorization must also be supplied (this is an Amazon EC2 requirement): group1=name1, group1owner=1234567890, group2=name2, group2owner=0987654321, ... groupN=nameN, groupNowner=...
+To create a new firewall rule within a specified firewall use call <strong>POST /api/firewalls/:id/rules</strong>. This operation of the firewalls collection is not supported by Fujitsu GCP. A client must supply the <strong>protocol</strong> (one of udp, tcp or icmp), <strong>port_from</strong> and <strong>port_to</strong> as parameters. Of course the client must also specify the <strong>sources</strong> to which the given rule is applied. IP addresses are specified in CIDR format sequentially: ip_address1=192.168.10.10/24, ip_address2=10.1.1.1/16 ... ip_addressN=.... The IP address '0.0.0.0/0' acts as a wildcard to specify any IP address. Source firewalls are also specified sequentially, but the <strong>owner_id</strong> of the firewall prepared for authorization must also be supplied (this is an Amazon EC2 requirement): group1=name1, group1owner=1234567890, group2=name2, group2owner=0987654321, ... groupN=nameN, groupNowner=...
</p>
<p>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/content/images.md
----------------------------------------------------------------------
diff --git a/site/content/images.md b/site/content/images.md
index e0f41c1..b66a1f5 100644
--- a/site/content/images.md
+++ b/site/content/images.md
@@ -177,14 +177,14 @@ Content-Length: 433
<h4>Create an image</h4>
<p>
-To create a new image from an existing running instance use call <strong>POST /api/images</strong>. This operation is not available to all cloud providers and for some cloud providers this operation is not possible for all instances. For example, in the Amazon EC2 cloud, you can create a custom image from EBS backed instances but not from root-store instances.
+To create a new image from an existing running instance use call <strong>POST /api/images</strong>. This operation is not available to all cloud providers and for some cloud providers this operation is not possible for all instances. For example, in the Amazon EC2 cloud, you can create a custom image from EBS backed instances but not from root-store instances.
</p>
<div class="alert alert-error">
<a class="close" data-dismiss="alert" href="#">×</a>
- <strong>Note: </strong>
+ <strong>Note: </strong>
<p>
- RHVE-M and vSphere providers allow you to create an image only from a stopped instance, not from a running instance.
+ RHVE-M, vSphere and Fujitsu GCP providers allow you to create an image only from a stopped instance, not from a running instance.
</p>
</div>
@@ -248,10 +248,15 @@ Content-Length: 427
<div class="alert alert-error">
<a class="close" data-dismiss="alert" href="#">×</a>
- <strong>Note: </strong>
+ <strong>Note: </strong>
<p>When you create an image from a stopped instance in <strong>vSphere</strong> cloud, this particular instance is marked as <strong>template</strong> and it is also removed from Instances.</p>
-
+
<p>Unlike other providers, vSphere does not support assigning a <strong>name</strong> and a <strong>description</strong> to the image when you create an image from a stopped instance. The image created in vSphere ignores these attributes passed to the API during the creation.</p>
+ <p><strong>Fujitsu GCP</strong> does not return an ID that can be used to track the state of the image
+ creation. Poll the list of all images until your image appears. This will contain the
+ proper image id that can be used in other image actions.
+ </p>
+
</div>
<h4>Delete an image</h4>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/content/load-balancers.md
----------------------------------------------------------------------
diff --git a/site/content/load-balancers.md b/site/content/load-balancers.md
index 48d27af..fa3147e 100644
--- a/site/content/load-balancers.md
+++ b/site/content/load-balancers.md
@@ -15,7 +15,7 @@ Load balancers allow distribution of ingress network traffic received by a speci
</p>
<p>
-This collection is not supported by all back-end cloud providers and at present, it is implemented for the Gogrid and Amazon EC2 cloud drivers. A load balancer is launched into a specific realm. Only instances within this specific realm may be attached to the balancer. Each load balancer has
+This collection is not supported by all back-end cloud providers and at present, it is implemented for the Fujitsu GCP, Gogrid and Amazon EC2 cloud drivers. A load balancer is launched into a specific realm. Only instances within this specific realm may be attached to the balancer. Each load balancer has
</p>
<ul>
@@ -69,7 +69,7 @@ Each <strong>listener</strong> has a <strong>protocol</strong> (e.g. TCP), a <st
<div class="tab-content">
<div class="tab-pane active" id="tab1">
-
+
<h4>Get the details of all load balancers</h4>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/content/rest-api.md
----------------------------------------------------------------------
diff --git a/site/content/rest-api.md b/site/content/rest-api.md
index 30a85a6..bc58934 100644
--- a/site/content/rest-api.md
+++ b/site/content/rest-api.md
@@ -1,4 +1,4 @@
----
+---
site_name: Deltacloud API
title: REST API
---
@@ -98,7 +98,7 @@ The following terms describe abstractions used in the Apache Deltacloud API. Eac
</dd>
<dt><h4>Metrics</h4></dt>
<dd>
- Metrics collection provides useful information about your cloud resources, e.g. CPU utilization or network throughput. It may be helpful for developers for better scaling and monitoring. The collection is currently supported only for Amazon EC2 cloud. It collects information from Amazon CloudWatch service.
+ Metrics collection provides useful information about your cloud resources, e.g. CPU utilization or network throughput. It may be helpful for developers for better scaling and monitoring. The collection is currently supported for Amazon EC2 cloud, collecting information from Amazon CloudWatch service, and Fujitsu GCP.
</dd>
</dl>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/content/storage-resources.md
----------------------------------------------------------------------
diff --git a/site/content/storage-resources.md b/site/content/storage-resources.md
index 796a9a5..3c8d574 100644
--- a/site/content/storage-resources.md
+++ b/site/content/storage-resources.md
@@ -180,9 +180,18 @@ Content-Length: 794
<h4>Create a new storage volume</h4>
<p>
-To create a new storage volume use call <strong>POST /api/storage_volumes</strong>. A client may specify a <strong>snapshot_id</strong> from which the storage volume is instantiated though this is optional. The <strong>capacity</strong> parameter, expressed in Gigabytes, is also optional and its default size is 1 GB. Finally clients may also specify the <strong>realm_id</strong>, as a storage volume can typically only be attached to instances running within the specified realm. If the realm is not specified it will set it at the first realm returned by the cloud provider. A succesful operation will return <strong>HTTP 201 Created</strong> with the details of the new storage volume.
+To create a new storage volume use call <strong>POST /api/storage_volumes</strong>. A client may specify a <strong>snapshot_id</strong> from which the storage volume is instantiated though this is optional. The <strong>capacity</strong> parameter, expressed in Gigabytes, is also optional and its default size is 1 GB. Finally clients may also specify the <strong>realm_id</strong>, as a storage volume can typically only be attached to instances running within the specified realm. If the realm is not specified it will set it at the first realm returned by the cloud provider. A successful operation will return <strong>HTTP 201 Created</strong> with the details of the new storage volume.
</p>
+<div class="alert alert-error">
+ <a class="close" data-dismiss="alert" href="#">×</a>
+ <strong>Note: </strong>
+ <p>
+ Fujitsu GCP requires the size to be a multiple of 10, so the specified capacity is rounded
+ up to the nearest multiple of ten, making the default size 10 GB.
+ </p>
+</div>
+
<p>
As with the other POST operations in the Deltacloud API, clients may choose to specify operation parameters as multipart/form-data or as application/x-www-form-urlencoded data.
</p>
@@ -225,12 +234,12 @@ Content-Length: 649
<h4>Delete a storage volume</h4>
<p>
-To delete the specified storage volume use call <strong>DELETE /api/storage_volumes/:id</strong>. The operation will return a <strong>HTTP 204 No Content</strong> after a succesful operation.
+To delete the specified storage volume use call <strong>DELETE /api/storage_volumes/:id</strong>. The operation will return a <strong>HTTP 204 No Content</strong> after a succesful operation.
</p>
<div class="alert alert-error">
<a class="close" data-dismiss="alert" href="#">×</a>
- <strong>Note:</strong>
+ <strong>Note:</strong>
<p> The operation will fail if the given storage_volume is currently attached to an instance. </p>
</div>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/output/addresses.html
----------------------------------------------------------------------
diff --git a/site/output/addresses.html b/site/output/addresses.html
index b18d2f2..fe7ccda 100644
--- a/site/output/addresses.html
+++ b/site/output/addresses.html
@@ -95,11 +95,11 @@
<h3 id="addresses">Addresses</h3>
<p>
-The addresses collection represents IP addresses and allows <strong>IP address management</strong>.
+The addresses collection represents IP addresses and allows <strong>IP address management</strong>.
</p>
<p>
-This collection is currently implemented for the Amazon EC2 cloud driver. For EC2, IP address management corresponds to Amazon's 'Elastic IP' feature.
+This collection is currently implemented for Amazon EC2 and Fujitsu GCP drivers. For EC2, IP address management corresponds to Amazon's 'Elastic IP' feature.
</p>
<br><p>
@@ -147,7 +147,7 @@ The addresses collection supports these operations:
<div class="tab-content">
<div class="tab-pane active" id="tab1">
-
+
<h4>Get a list of all addresses</h4>
<p>
@@ -295,10 +295,10 @@ Date: Wed, 27 Jul 2011 13:29:00 GMT
</div>
<div class="tab-pane" id="tab4">
-<h4>Associate an adress with an instance</h4>
+<h4>Associate an address with an instance</h4>
<p>
-To associate a given address with a running instance use call <strong>POST /api/addresses/:id/associate</strong>. The client must specify the <strong>instance_id</strong> as a parameter to this call. For Amazon EC2, the specified address will replace the currently assigned public_address of the instance. A succesful operation results in a <strong>HTTP 202 Accepted</strong> response. The example client request below specifies the required instance_id parameter using the application/x-www-form-urlencoded content-type, however client can also use multipart/form-data.
+To associate a given address with a running instance use call <strong>POST /api/addresses/:id/associate</strong>. The client must specify the <strong>instance_id</strong> as a parameter to this call. For Amazon EC2, the specified address will replace the currently assigned public_address of the instance, while for the Fujitsu GCP it is added. A succesful operation results in a <strong>HTTP 202 Accepted</strong> response. The example client request below specifies the required instance_id parameter using the application/x-www-form-urlencoded content-type, however client can also use multipart/form-data.
</p>
<p>Example request:</p>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/output/blob-storage.html
----------------------------------------------------------------------
diff --git a/site/output/blob-storage.html b/site/output/blob-storage.html
index df409cc..a6995b2 100644
--- a/site/output/blob-storage.html
+++ b/site/output/blob-storage.html
@@ -95,7 +95,7 @@
<h3 id="blob">Blob Storage</h3>
<p>
-Blob storage represents a generic key ==> value data store. It is implemented by Amazon S3 or Rackspace Cloudfiles. In Deltacloud, the organisational unit of blob storage is a bucket. Individual data items - blobs are exposed as a subcollection under each bucket.
+Blob storage represents a generic key ==> value data store, as implemented for example by Amazon S3 or Openstack swift. In Deltacloud, the organisational unit of blob storage is a bucket. Individual data items - blobs are exposed as a subcollection under each bucket.
</p>
<p>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/output/firewalls.html
----------------------------------------------------------------------
diff --git a/site/output/firewalls.html b/site/output/firewalls.html
index 7b398f4..3b5faf1 100644
--- a/site/output/firewalls.html
+++ b/site/output/firewalls.html
@@ -95,7 +95,7 @@
<h3 id="firewalls">Firewalls</h3>
<p>
-Firewalls represent sets of rules that govern the accessibility of a running instance over the public Internet. At present, only the Amazon EC2 cloud supports this collection (Amazon EC2 'Security Groups'). A firewall has these attributes:
+Firewalls represent sets of rules that govern the accessibility of a running instance over the public Internet. At present, only Amazon EC2 cloud (Amazon EC2 'Security Groups') and Fujitsu GCP support this collection. A firewall has these attributes:
</p>
<ul>
@@ -109,11 +109,11 @@ Firewalls represent sets of rules that govern the accessibility of a running ins
</li>
</ul>
<p>
-An instance is launched into a firewall by specifying the <strong>firewalls1 ... firewallsN</strong> parameters in the <strong>POST /api/instances</strong> operation (see the <a href="instances.html#instance">Create an instance</a> section).
+For Amazon EC2, an instance is launched into a firewall by specifying the <strong>firewalls1 ... firewallsN</strong> parameters in the <strong>POST /api/instances</strong> operation (see the <a href="instances.html#instance">Create an instance</a> section).
</p>
<p>
-Each <strong>firewall rule</strong> has a number of attributes describing the access granted to clients that want to communicate with the instance over the Internet. Each rule cosists of
+Each <strong>firewall rule</strong> has a number of attributes describing the access granted to clients that want to communicate with the instance over the Internet. Each rule consists of
</p>
<ul>
@@ -148,7 +148,8 @@ Each <strong>firewall rule</strong> has a number of attributes describing the ac
</div>
<p>
-Each rule also specifies a <strong>direction</strong>, indicating whether it applies to ingress or egress traffic.
+Each rule also specifies a <strong>direction</strong>, indicating whether it applies to ingress or egress traffic. A rule can also specify a <strong>rule_action</strong> (accept, deny), to indicate whether the firewall should accept or deny access for this traffic, and <strong>log_rule</strong> (true, false), to indicate whether an entry should be added to the log.
+
</p>
<p>
@@ -362,11 +363,13 @@ Date: Wed, 27 Jul 2011 09:47:43 GMT
</pre>
<p>
-The rules governing the deletion of a firewall are back-end cloud specific. At present, only the Amazon EC2 cloud supports the firewalls collection, so we describe the firewall deletion rules for EC2 here.
+The rules governing the deletion of a firewall are back-end cloud specific.
+</p>
+<p>
+For Fujitsu GCP, as this operation destroys the virtual system with it, all instances in the system, including the firewall need to be in the STOPPED state.
</p>
-
<p>
-It is permitted to delete a firewall that has rules defined within it, with two exceptions. You cannot delete a firewall if it is referenced by another firewall; for instance <strong>firewall_1</strong> has a rule giving access to <strong>firewall_2</strong>. An attempt to delete firewall_2 will result in the error <strong>InvalidGroup.InUse</strong>, as you can see in the example below. The second exception is that you cannot delete a firewall if there are currently any running instances within that firewall (i.e. instances that specified the given firewall when they were launched). The error message in that case would be <strong>InvalidGroup.InUse: There are active instances using security group</strong>. In both cases the error messages are propagated from the back-end cloud provider to the requesting client.
+For Amazon EC2, it is permitted to delete a firewall that has rules defined within it, with two exceptions. You cannot delete a firewall if it is referenced by another firewall; for instance <strong>firewall_1</strong> has a rule giving access to <strong>firewall_2</strong>. An attempt to delete firewall_2 will result in the error <strong>InvalidGroup.InUse</strong>, as you can see in the example below. The second exception is that you cannot delete a firewall if there are currently any running instances within that firewall (i.e. instances that specified the given firewall when they were launched). The error message in that case would be <strong>InvalidGroup.InUse: There are active instances using security group</strong>. In both cases the error messages are propagated from the back-end cloud provider to the requesting client.
</p>
<p>
@@ -405,7 +408,7 @@ Content-Length: 626
<h4>Create a firewall rule</h4>
<p>
-To create a new firewall rule within a specified firewall use call <strong>POST /api/firewalls/:id/rules</strong>. A client must supply the <strong>protocol</strong> (one of udp, tcp or icmp), <strong>port_from</strong> and <strong>port_to</strong> as parameters. Of course the client must also specify the <strong>sources</strong> to which the given rule is applied. IP addresses are specified in CIDR format sequentially: ip_address1=192.168.10.10/24, ip_address2=10.1.1.1/16 ... ip_addressN=.... The IP address '0.0.0.0/0' acts as a wildcard to specify any IP address. Source firewalls are also specified sequentially, but the <strong>owner_id</strong> of the firewall prepared for authorization must also be supplied (this is an Amazon EC2 requirement): group1=name1, group1owner=1234567890, group2=name2, group2owner=0987654321, ... groupN=nameN, groupNowner=...
+To create a new firewall rule within a specified firewall use call <strong>POST /api/firewalls/:id/rules</strong>. This operation of the firewalls collection is not supported by Fujitsu GCP. A client must supply the <strong>protocol</strong> (one of udp, tcp or icmp), <strong>port_from</strong> and <strong>port_to</strong> as parameters. Of course the client must also specify the <strong>sources</strong> to which the given rule is applied. IP addresses are specified in CIDR format sequentially: ip_address1=192.168.10.10/24, ip_address2=10.1.1.1/16 ... ip_addressN=.... The IP address '0.0.0.0/0' acts as a wildcard to specify any IP address. Source firewalls are also specified sequentially, but the <strong>owner_id</strong> of the firewall prepared for authorization must also be supplied (this is an Amazon EC2 requirement): group1=name1, group1owner=1234567890, group2=name2, group2owner=0987654321, ... groupN=nameN, groupNowner=...
</p>
<p>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/output/images.html
----------------------------------------------------------------------
diff --git a/site/output/images.html b/site/output/images.html
index 7301c8e..144bb97 100644
--- a/site/output/images.html
+++ b/site/output/images.html
@@ -260,14 +260,14 @@ Content-Length: 433
<h4>Create an image</h4>
<p>
-To create a new image from an existing running instance use call <strong>POST /api/images</strong>. This operation is not available to all cloud providers and for some cloud providers this operation is not possible for all instances. For example, in the Amazon EC2 cloud, you can create a custom image from EBS backed instances but not from root-store instances.
+To create a new image from an existing running instance use call <strong>POST /api/images</strong>. This operation is not available to all cloud providers and for some cloud providers this operation is not possible for all instances. For example, in the Amazon EC2 cloud, you can create a custom image from EBS backed instances but not from root-store instances.
</p>
<div class="alert alert-error">
<a class="close" data-dismiss="alert" href="#">×</a>
- <strong>Note: </strong>
+ <strong>Note: </strong>
<p>
- RHVE-M and vSphere providers allow you to create an image only from a stopped instance, not from a running instance.
+ RHVE-M, vSphere and Fujitsu GCP providers allow you to create an image only from a stopped instance, not from a running instance.
</p>
</div>
@@ -331,10 +331,15 @@ Content-Length: 427
<div class="alert alert-error">
<a class="close" data-dismiss="alert" href="#">×</a>
- <strong>Note: </strong>
+ <strong>Note: </strong>
<p>When you create an image from a stopped instance in <strong>vSphere</strong> cloud, this particular instance is marked as <strong>template</strong> and it is also removed from Instances.</p>
-
+
<p>Unlike other providers, vSphere does not support assigning a <strong>name</strong> and a <strong>description</strong> to the image when you create an image from a stopped instance. The image created in vSphere ignores these attributes passed to the API during the creation.</p>
+ <p><strong>Fujitsu GCP</strong> does not return an ID that can be used to track the state of the image
+ creation. Poll the list of all images until your image appears. This will contain the
+ proper image id that can be used in other image actions.
+ </p>
+
</div>
<h4>Delete an image</h4>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/output/load-balancers.html
----------------------------------------------------------------------
diff --git a/site/output/load-balancers.html b/site/output/load-balancers.html
index 57d9bcf..34ccbb6 100644
--- a/site/output/load-balancers.html
+++ b/site/output/load-balancers.html
@@ -99,7 +99,7 @@ Load balancers allow distribution of ingress network traffic received by a speci
</p>
<p>
-This collection is not supported by all back-end cloud providers and at present, it is implemented for the Gogrid and Amazon EC2 cloud drivers. A load balancer is launched into a specific realm. Only instances within this specific realm may be attached to the balancer. Each load balancer has
+This collection is not supported by all back-end cloud providers and at present, it is implemented for the Fujitsu GCP, Gogrid and Amazon EC2 cloud drivers. A load balancer is launched into a specific realm. Only instances within this specific realm may be attached to the balancer. Each load balancer has
</p>
<ul>
@@ -147,7 +147,7 @@ Each <strong>listener</strong> has a <strong>protocol</strong> (e.g. TCP), a <st
<li><a href="#tab4" data-toggle="tab">Register/unregister an instance</a></li>
</ul><hr><div class="tab-content">
<div class="tab-pane active" id="tab1">
-
+
<h4>Get the details of all load balancers</h4>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/output/rest-api.html
----------------------------------------------------------------------
diff --git a/site/output/rest-api.html b/site/output/rest-api.html
index 40f9cc6..6528d52 100644
--- a/site/output/rest-api.html
+++ b/site/output/rest-api.html
@@ -182,7 +182,7 @@ The following terms describe abstractions used in the Apache Deltacloud API. Eac
</dd>
<dt><h4>Metrics</h4></dt>
<dd>
- Metrics collection provides useful information about your cloud resources, e.g. CPU utilization or network throughput. It may be helpful for developers for better scaling and monitoring. The collection is currently supported only for Amazon EC2 cloud. It collects information from Amazon CloudWatch service.
+ Metrics collection provides useful information about your cloud resources, e.g. CPU utilization or network throughput. It may be helpful for developers for better scaling and monitoring. The collection is currently supported for Amazon EC2 cloud, collecting information from Amazon CloudWatch service, and Fujitsu GCP.
</dd>
http://git-wip-us.apache.org/repos/asf/deltacloud/blob/8116e6a3/site/output/storage-resources.html
----------------------------------------------------------------------
diff --git a/site/output/storage-resources.html b/site/output/storage-resources.html
index 81f1bcf..20a6b21 100644
--- a/site/output/storage-resources.html
+++ b/site/output/storage-resources.html
@@ -258,9 +258,18 @@ Content-Length: 794
<h4>Create a new storage volume</h4>
<p>
-To create a new storage volume use call <strong>POST /api/storage_volumes</strong>. A client may specify a <strong>snapshot_id</strong> from which the storage volume is instantiated though this is optional. The <strong>capacity</strong> parameter, expressed in Gigabytes, is also optional and its default size is 1 GB. Finally clients may also specify the <strong>realm_id</strong>, as a storage volume can typically only be attached to instances running within the specified realm. If the realm is not specified it will set it at the first realm returned by the cloud provider. A succesful operation will return <strong>HTTP 201 Created</strong> with the details of the new storage volume.
+To create a new storage volume use call <strong>POST /api/storage_volumes</strong>. A client may specify a <strong>snapshot_id</strong> from which the storage volume is instantiated though this is optional. The <strong>capacity</strong> parameter, expressed in Gigabytes, is also optional and its default size is 1 GB. Finally clients may also specify the <strong>realm_id</strong>, as a storage volume can typically only be attached to instances running within the specified realm. If the realm is not specified it will set it at the first realm returned by the cloud provider. A successful operation will return <strong>HTTP 201 Created</strong> with the details of the new storage volume.
</p>
+<div class="alert alert-error">
+ <a class="close" data-dismiss="alert" href="#">×</a>
+ <strong>Note: </strong>
+ <p>
+ Fujitsu GCP requires the size to be a multiple of 10, so the specified capacity is rounded
+ up to the nearest multiple of ten, making the default size 10 GB.
+ </p>
+</div>
+
<p>
As with the other POST operations in the Deltacloud API, clients may choose to specify operation parameters as multipart/form-data or as application/x-www-form-urlencoded data.
</p>
@@ -303,12 +312,12 @@ Content-Length: 649
<h4>Delete a storage volume</h4>
<p>
-To delete the specified storage volume use call <strong>DELETE /api/storage_volumes/:id</strong>. The operation will return a <strong>HTTP 204 No Content</strong> after a succesful operation.
+To delete the specified storage volume use call <strong>DELETE /api/storage_volumes/:id</strong>. The operation will return a <strong>HTTP 204 No Content</strong> after a succesful operation.
</p>
<div class="alert alert-error">
<a class="close" data-dismiss="alert" href="#">×</a>
- <strong>Note:</strong>
+ <strong>Note:</strong>
<p> The operation will fail if the given storage_volume is currently attached to an instance. </p>
</div>