<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>CloudStack 開発者ガイド</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Apache_CloudStack-Developers_Guide-4.1.0-ja-JP-1-" /><meta name="description" content="このガイドではどのように CloudStack を開発するか、各種操作や統合にどのように API を利用するのか、使用率データへのアクセス、より簡単に開発するための CloudStack 独自ツールの使い方、テストと統合に関してを説明します。" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
              addID('Apache_CloudStack');
              
	      addID('Apache_CloudStack.4.1.0');
              
              addID('Apache_CloudStack.4.1.0.books');
	      addID('Apache_CloudStack.4.1.0.Developers_Guide');
              </script></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://cloudstack.apache.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://cloudstack.apache.org/docs"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="ja-JP" class="book" id="idm12312408" lang="ja-JP"><div class="titlepage"><div><div class="producttitle"><span class="productname">Apache CloudStack</span> <span class="productnumber">4.1.0</span></div><div><h1 id="idm12312408" class="title">CloudStack 開発者ガイド</h1></div><p class="edition">エディッション </p><div><h3 class="corpauthor">
			<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> </object></span>

		</h3></div><div><div xml:lang="ja-JP" class="authorgroup" lang="ja-JP"><div class="author"><h3 class="author"><span class="surname">CloudStack</span> <span class="firstname">Apache</span> [FAMILY Given]</h3></div></div></div><hr /><div><div id="idm35713520" class="legalnotice"><h1 class="legalnotice">法律上の通知</h1><div class="para">
		Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
	</div><div class="para">
		http://www.apache.org/licenses/LICENSE-2.0
	</div><div class="para">
		Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
	</div><div class="para">
		Apache CloudStack is an effort undergoing incubation at The Apache Software Foundation (ASF).
	</div><div class="para">
		Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
	</div></div></div><div><div class="abstract"><h6>概要</h6><div class="para">
				このガイドではどのように CloudStack を開発するか、各種操作や統合にどのように API を利用するのか、使用率データへのアクセス、より簡単に開発するための CloudStack 独自ツールの使い方、テストと統合に関してを説明します。
			</div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="chapter"><a href="#concepts">1. コンセプト</a></span></dt><dd><dl><dt><span class="section"><a href="#whatis">1.1. CloudStack とは</a></span></dt><dt><span class="section"><a href="#feature-overview">1.2. CloudStack の機能</a></span></dt><dt><span class="section"><a href="#deployment-architecture-overview">1.3. 展開アーキテクチャの概要</a></span></dt><dd><dl><dt><span class="section"><a href="#management-server-overview">1.3.1. 管理サーバーについて</a></span></dt><dt><span class="section"><a href="#cloud-infrastructure-overview">1.3.2. クラウドインフラストラクチャの概要</a></span></dt><dt><span class="section"><a href="#networking-overview">1.3.3. ネットワーク</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#building-with-maven">2. CloudStack をビルドするための Maven の利用</a></span></dt><dd><dl><dt><span class="section"><a href="#source-build">2.1. Building CloudStack from Source</a></span></dt><dt><span class="section"><a href="#build-prerequisites">2.2. Build Procedure Prerequisites</a></span></dt><dt><span class="section"><a href="#building-with-maven-steps">2.3. ビルド手順</a></span></dt><dt><span class="section"><a href="#building-with-maven-deploy">2.4. テスト環境における展開</a></span></dt></dl></dd><dt><span class="chapter"><a href="#developer-introduction">3. Introduction to the CloudStack API</a></span></dt><dd><dl><dt><span class="section"><a href="#roles">3.1. Roles</a></span></dt><dt><span class="section"><a href="#api-reference">3.2. API リファレンス</a></span></dt><dt><span class="section"><a href="#getting-started">3.3. Getting Started</a></span></dt></dl></dd><dt><span class="chapter"><a href="#whats-new">4. APIにおける新機能</a></span></dt><dd><dl><dt><span class="section"><a href="#whats-new-in-api-4.1">4.1. What's New in the API for 4.1</a></span></dt><dd><dl><dt><span class="section"><a href="#add-remove-nic">4.1.1. Reconfiguring Physical Networks in VMs</a></span></dt><dt><span class="section"><a href="#ipv6-support">4.1.2. IPv6 Support in CloudStack</a></span></dt><dt><span class="section"><a href="#vmx-settings-dev">4.1.3. Additional VMX Settings</a></span></dt><dt><span class="section"><a href="#reset-ssh-key-dev">4.1.4. Resetting SSH Keys to Access VMs</a></span></dt><dt><span class="section"><a href="#changed-apicommands-4.1">4.1.5. Changed API Commands in 4.1</a></span></dt><dt><span class="section"><a href="#added-API-commands-4.1">4.1.6. Added API Commands in 4.1-incubating</a></span></dt></dl></dd><dt><span class="section"><a href="#whats-new-in-api-4.0">4.2. 4.0 APIでの新機能</a></span></dt><dd><dl><dt><span class="section"><a href="#changed-apicommands-4.0">4.2.1. 4.0.0-incubating で変更された API コマンド</a></span></dt><dt><span class="section"><a href="#added-API-commands-4.0">4.2.2. Added API Commands in 4.0.0-incubating</a></span></dt></dl></dd><dt><span class="section"><a href="#whats-new-in-api-3.0">4.3. 3.0 APIでの新機能</a></span></dt><dd><dl><dt><span class="section"><a href="#enabling-port-8096">4.3.1. Enabling Port 8096</a></span></dt><dt><span class="section"><a href="#stopped-vm">4.3.2. Stopped VM</a></span></dt><dt><span class="section"><a href="#change-to-behavior-of-list-commands">4.3.3. Change to Behavior of List Commands</a></span></dt><dt><span class="section"><a href="#removed-API-commands">4.3.4. 削除された API コマンド</a></span></dt><dt><span class="section"><a href="#added-API-commands">4.3.5. 3.0 にて追加された API コマンド</a></span></dt><dt><span class="section"><a href="#added-error-codes">4.3.6. Added CloudStack Error Codes</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#api-calls">5. CloudStack API の呼び出し</a></span></dt><dd><dl><dt><span class="section"><a href="#making-api-request">5.1. API リクエストを作成します。</a></span></dt><dt><span class="section"><a href="#signing-api-requests">5.2. Signing API Requests</a></span></dt><dd><dl><dt><span class="section"><a href="#signing-api-calls-python">5.2.1. How to sign an API call with Python</a></span></dt></dl></dd><dt><span class="section"><a href="#enabling-api-call-expiration">5.3. Enabling API Call Expiration</a></span></dt><dt><span class="section"><a href="#api-throttling">5.4. Limiting the Rate of API Requests</a></span></dt><dd><dl><dt><span class="section"><a href="#api-throttling-configure">5.4.1. Configuring the API Request Rate</a></span></dt><dt><span class="section"><a href="#api-throttling-limitations">5.4.2. Limitations on API Throttling</a></span></dt></dl></dd><dt><span class="section"><a href="#responses">5.5. Responses</a></span></dt><dd><dl><dt><span class="section"><a href="#response-formats">5.5.1. Response Formats: XML and JSON</a></span></dt><dt><span class="section"><a href="#max-result-page-returned">5.5.2. Maximum Result Pages Returned</a></span></dt><dt><span class="section"><a href="#error-handling">5.5.3. Error Handling</a></span></dt></dl></dd><dt><span class="section"><a href="#asynchronous-commands">5.6. Asynchronous Commands</a></span></dt><dd><dl><dt><span class="section"><a href="#job-status">5.6.1. ジョブの状態</a></span></dt><dt><span class="section"><a href="#asynchronous-commands-example">5.6.2. 例</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#working-with-usage-data">6. Working With Usage Data</a></span></dt><dd><dl><dt><span class="section"><a href="#usage-record-format">6.1. Usage Record Format</a></span></dt><dd><dl><dt><span class="section"><a href="#virtual-machine-usage-record-format">6.1.1. Virtual Machine Usage Record Format</a></span></dt><dt><span class="section"><a href="#network-usage-record-format">6.1.2. Network Usage Record Format</a></span></dt><dt><span class="section"><a href="#ipaddress-usage-record-format">6.1.3. IP Address Usage Record Format</a></span></dt><dt><span class="section"><a href="#disk-volume-usage-record-format">6.1.4. Disk Volume Usage Record Format</a></span></dt><dt><span class="section"><a href="#template-iso-snapshot-usage-record-format">6.1.5. Template, ISO, and Snapshot Usage Record Format</a></span></dt><dt><span class="section"><a href="#loadbalancer-policy-port-forwarding-rule-usage-record-format">6.1.6. Load Balancer Policy or Port Forwarding Rule Usage Record Format</a></span></dt><dt><span class="section"><a href="#network-offering-usage-record-format">6.1.7. Network Offering Usage Record Format</a></span></dt><dt><span class="section"><a href="#VPN-user-usage-record-format">6.1.8. VPN User Usage Record Format</a></span></dt></dl></dd><dt><span class="section"><a href="#usage-types">6.2. 使用状況データの種類</a></span></dt><dt><span class="section"><a href="#example-response-from-listUsageRecords">6.3. Example response from listUsageRecords</a></span></dt><dt><span class="section"><a href="#dates-in-usage-record">6.4. Dates in the Usage Record</a></span></dt><dt><span class="section"><a href="#globally-configured-limits">6.5. Globally Configured Limits</a></span></dt></dl></dd><dt><span class="chapter"><a href="#working-with-documentation">7. Preparing and Building CloudStack Documentation</a></span></dt><dd><dl><dt><span class="section"><a href="#installing-publican">7.1. Installing Publican</a></span></dt><dt><span class="section"><a href="#building-documentation">7.2. Building CloudStack Documentation</a></span></dt><dt><span class="section"><a href="#writing-new-documentation">7.3. Writing CloudStack Documentation</a></span></dt><dt><span class="section"><a href="#building-translation">7.4. Translating CloudStack Documentation</a></span></dt><dd><dl><dt><span class="section"><a href="#translating-documentation">7.4.1. Translating CloudStack Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#tools">8. Tools</a></span></dt><dd><dl><dt><span class="section"><a href="#devcloud">8.1. DevCloud</a></span></dt><dd><dl><dt><span class="section"><a href="#devcloud-usage-mode">8.1.1. DevCloud Usage Mode</a></span></dt><dt><span class="section"><a href="#building-devcloud">8.1.2. Building DevCloud</a></span></dt></dl></dd><dt><span class="section"><a href="#marvin">8.2. Marvin</a></span></dt><dd><dl><dt><span class="section"><a href="#building-marvin">8.2.1. Building and Installing Marvin</a></span></dt></dl></dd><dt><span class="section"><a href="#cloudmonkey">8.3. CloudMonkey</a></span></dt><dd><dl><dt><span class="section"><a href="#gettingcloudmonkey">8.3.1. Installing CloudMonkey</a></span></dt><dt><span class="section"><a href="#configuringcloudmonkey">8.3.2. 構成</a></span></dt><dt><span class="section"><a href="#cliapidiscovery">8.3.3. API Discovery</a></span></dt><dt><span class="section"><a href="#clitabularoutput">8.3.4. Tabular Output</a></span></dt><dt><span class="section"><a href="#interactivecli">8.3.5. Interactive Shell Usage</a></span></dt><dt><span class="section"><a href="#startingavmexample">8.3.6. Starting a Virtual Machine instance with CloudMonkey</a></span></dt><dt><span class="section"><a href="#scriptingcli">8.3.7. Scripting with CloudMonkey</a></span></dt></dl></dd><dt><span class="section"><a href="#libcloud-examples">8.4. Apache Libcloud</a></span></dt></dl></dd><dt><span class="appendix"><a href="#event-types">A. イベントの種類</a></span></dt><dt><span class="appendix"><a href="#alerts">B. Alerts</a></span></dt><dt><span class="appendix"><a href="#time-zones">C. タイムゾーン</a></span></dt><dt><span class="appendix"><a href="#appe-cloudstack-Revision_History">D. Revision History</a></span></dt></dl></div><div xml:lang="ja-JP" class="chapter" id="concepts" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第1章 コンセプト</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#whatis">1.1. CloudStack とは</a></span></dt><dt><span class="section"><a href="#feature-overview">1.2. CloudStack の機能</a></span></dt><dt><span class="section"><a href="#deployment-architecture-overview">1.3. 展開アーキテクチャの概要</a></span></dt><dd><dl><dt><span class="section"><a href="#management-server-overview">1.3.1. 管理サーバーについて</a></span></dt><dt><span class="section"><a href="#cloud-infrastructure-overview">1.3.2. クラウドインフラストラクチャの概要</a></span></dt><dt><span class="section"><a href="#networking-overview">1.3.3. ネットワーク</a></span></dt></dl></dd></dl></div><div xml:lang="ja-JP" class="section" id="whatis" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="whatis">1.1. CloudStack とは</h2></div></div></div><div class="para">
		CloudStack はオープンソースのソフトウェアプラットフォームで、コン ピューティングリソースをプールすることにより、パブリック、プライベート、 およびハイブリッドの IaaS(Infrastructure as a Service)クラウドを構築す ることができます。CloudStack で、クラウドインフラストラクチャを構成する ネットワーク、ストレージ、およびコンピューティングノードを管理します。 CloudStack を使用して、クラウドコンピューティング環境を展開、管理、お よび構成します。
	</div><div class="para">
		本製品の主なユーザーはサービスプロバイダーと企業です。CloudStack を使用すると、次のタスクを実行できます。
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				オンデマンドで弾力的なクラウドコンピューティングサービスをセッ トアップする。サービスプロバイダーはインターネットを経由して、セルフサービスの仮想マシンインスタンス、スト レージボリューム、およびネットワーク構成を販売できます。
			</div></li><li class="listitem"><div class="para">
				従業員が使用するオンプレミスなプライベートクラウドをセットアップする。企業は物理マシンと同じ方法で仮想マシ ンを管理せずに、IT 部門を介さずにセルフサービスの仮想マシンをユーザーに提供することができます。
			</div></li></ul></div><div class="mediaobject"><img src="./images/1000-foot-view.png" width="444" alt="1000-foot-view.png: Overview of CloudStack" /></div></div><div xml:lang="ja-JP" class="section" id="feature-overview" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="feature-overview">1.2. CloudStack の機能</h2></div></div></div><div class="para">
		<span class="bold bold"><strong>複数のハイパーバイザーのサポート</strong></span>
	</div><div class="para">
		CloudStack はさまざまなハイパーバイザーと連動します。単一のクラウド環境に、ハイパーバイザーの実装を複数含められます。現在の CloudStack リリースでは、エンタープライズクラスのハイパーバイザーである Citrix XenServer や VMware vSphere も CentOS, Ubuntu 上の KVM, Xen と同様にサポートされます。
	</div><div class="para">
		<span class="bold bold"><strong>高度にスケーラブルなインフラストラクチャ管理</strong></span>
	</div><div class="para">
		CloudStack では、地理的に分散した複数のデータセンターに設置される、何万台ものサーバーを管理することが できます。集中型の管理サーバーを直線的に拡張できるので、中間のクラスターレベルの管理サーバーが不要 です。単一のコンポーネントに障害が発生しても、クラスターまたはクラウド全体が停止することはありません。ク ラウドで実行中の仮想マシンの機能に影響を与えずに、管理サーバーの定期保守を実行できます。
	</div><div class="para">
		<span class="bold bold"><strong>自動的な構成管理</strong></span>
	</div><div class="para">
		CloudStack では、各ゲスト仮想マシンのネットワークとストレージの設定が自動的に構成されます。
	</div><div class="para">
		CloudStack では、クラウド自体をサポートする仮想アプライアンスのプールが内部的に管理されます。これらのア プライアンスにより、ファイアウォール、ルーティング、DHCP、VPN アクセス、コンソールプロキシ、ストレージアク セス、およびストレージ複製などのサービスが提供されます。仮想アプライアンスを幅広く使用することによって、 クラウド環境のインストール、構成、および継続的な管理を大いに単純化します。
	</div><div class="para">
		<span class="bold bold"><strong>グラフィカルユーザーインターフェイス</strong></span>
	</div><div class="para">
		CloudStack には、クラウドのプロビジョニングと管理のための管理者用の Web インターフェイスと、仮想マシンの 実行と仮想マシンテンプレートの管理のためのエンドユーザー用の Web インターフェイスが搭載されています。 ユーザーインターフェイスは、サービスプロバイダーまたは企業が希望する外観になるようにカスタマイズできま す。
	</div><div class="para">
		<span class="bold bold"><strong>標準 API のサポート</strong></span>
	</div><div class="para">
		CloudStack provides an API that gives programmatic access to all the management features available in the UI. The API is maintained and documented. This API enables the creation of command line tools and new user interfaces to suit particular needs. See the Developer’s Guide and API Reference, both available at <a href="http://cloudstack.apache.org/docs/en-US/index.html">Apache CloudStack Guides</a> and <a href="http://cloudstack.apache.org/docs/api/index.html">Apache CloudStack API Reference</a> respectively.
	</div><div class="para">
		CloudStack のプラッガブルなアロケーターのアーキテクチャはホストやストレージに対する新しいタイプの割り当てを許容しています。以下のアロケーター実装ガイドも参照して下さい。<a href="http://docs.cloudstack.org/CloudStack_Documentation/Allocator_Implementation_Guide">http://docs.cloudstack.org/CloudStack_Documentation/Allocator_Implementation_Guide</a>
	</div><div class="para">
		<span class="bold bold"><strong>高可用性</strong></span>
	</div><div class="para">
		CloudStack は可用性を高めるためシステムに幾つかの機能を持っています。管理サーバーを複数ノードにインストールし、サーバー間でロードバランシングをすることが出来ます。MySQLをデータベースの障害時に手動でフェイルオーバーするためレプリケーションの設定をすることも可能でしょう。ホストに対しては CloudStack はNICのボンディングやiSCSIのマルチパスのようにストレージ通信を分割することをサポートしています。
	</div></div><div xml:lang="ja-JP" class="section" id="deployment-architecture-overview" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="deployment-architecture-overview">1.3. 展開アーキテクチャの概要</h2></div></div></div><div class="para">
		CloudStack のインストールは、管理サーバーおよび管理サーバーで管理するクラウドインフラストラクチャの 2 つの部分に分けられます。CloudStack クラウドのセットアップと管理においては、ホスト、ストレージデバイス、および IP アドレスのようなリソースを管理者が管理サーバーに準備し、管理サーバーがそれらのリソースを管理します。
	</div><div class="para">
		最小構成でインストールする場合は、CloudStack 管理サーバーを実行する 1 台のマシンとクラウドインフラストラクチャとして動作するもう 1 台のマシンをセットアップします。この場合のクラウドインフラストラクチャは非常に単純で、ハイパーバイザーソフトウェアを実行する 1 台のホストで構成されます。最小の展開では 1 台のマシン上で管理サーバーとハイパーバイザーホストの両方を担うことができます。(その場合、KVM ハイパーバイザーを利用します)
	</div><div class="mediaobject"><img src="./images/basic-deployment.png" alt="basic-deployment.png: Basic two-machine deployment" /></div><div class="para">
		A more full-featured installation consists of a highly-available multi-node Management Server installation and up to tens of thousands of hosts using any of several advanced networking setups. For information about deployment options, see the "Choosing a Deployment Architecture" section of the $PRODUCT; Installation Guide.
	</div><div xml:lang="ja-JP" class="section" id="management-server-overview" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="management-server-overview">1.3.1. 管理サーバーについて</h3></div></div></div><div class="para">
		管理サーバーは、クラウドリソースを管理する CloudStack ソフトウェアです。ユーザーインターフェイスまたは API を介して 管理サーバーを操作することにより、クラウドインフラストラクチャを構成し管理できます。
	</div><div class="para">
		管理サーバーは専用のサーバーまたは仮想マシンです。ホストに対する仮想マシンの割り当てを制御し、ストレージと IP アドレスを仮想マシンインスタンスに割り当てます。CloudStack 管理サーバーは Tomcat コンテナー内で動作し、データ保 持のために MySQL データベースを必要とします。
	</div><div class="para">
		このマシンは「4.3: 最小システム要件」にあるシステム要件を満たしている必要があります。
	</div><div class="para">
		管理サーバー
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				管理者とエンドユーザーに Web ユーザーインターフェイスを提供します。
			</div></li><li class="listitem"><div class="para">
				CloudStack プラットフォームの API を提供します。
			</div></li><li class="listitem"><div class="para">
				特定ホストに対するゲスト仮想マシンの割り当てを管理します。
			</div></li><li class="listitem"><div class="para">
				特定アカウントに対するパブリックおよびプライベート IP アドレスの割り当てを管理します。
			</div></li><li class="listitem"><div class="para">
				ゲストに対する仮想ディスクとしてのストレージの割り当てを管理します。
			</div></li><li class="listitem"><div class="para">
				スナップショット、テンプレート、および ISO イメージを管理し、場合によっては複数のデータセンターの間でそれらを 複製します。
			</div></li><li class="listitem"><div class="para">
				クラウド構成のための単一の場を提供します。
			</div></li></ul></div></div><div xml:lang="ja-JP" class="section" id="cloud-infrastructure-overview" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="cloud-infrastructure-overview">1.3.2. クラウドインフラストラクチャの概要</h3></div></div></div><div class="para">
		名前が示すとおり、管理サーバーで 1 つ以上のゾーンを管理します。ゾーンは通常データセンターに相当し、ゲスト仮想マ シンが動作するホストコンピューターを含みます。クラウドインフラストラクチャは次のように組織されます。
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				ゾーン:通常、1 つのゾーンは単一のデータセンターに相当します。ゾーンは 1 つ以上のポッドとセカンダリストレー ジから構成されます。
			</div></li><li class="listitem"><div class="para">
				ポッド:普通、ポッドはレイヤー2スイッチと1つ以上のクラスターを含む1ラック分のハードウェアです。
			</div></li><li class="listitem"><div class="para">
				クラスター:クラスターは 1 つ以上のホストとプライマリストレージから構成されます。
			</div></li><li class="listitem"><div class="para">
				ホスト:クラスター内の単一のコンピューティングノードです。実際のクラウドサービスは、ゲスト仮想マシンの形式で ホストから提供されます。
			</div></li><li class="listitem"><div class="para">
				プライマリストレージはクラスターと関連付けられ、そのクラスター内のホスト上で動作するすべての仮想マシンの ディスクボリュームを格納します。
			</div></li><li class="listitem"><div class="para">
				セカンダリストレージはゾーンと関連付けられ、テンプレート、ISO イメージ、およびディスクボリュームのスナップ ショットを格納します。
			</div></li></ul></div><div class="mediaobject"><img src="./images/infrastructure-overview.png" width="444" alt="infrastructure_overview.png: Nested organization of a zone" /></div><div class="para">
		<span class="bold bold"><strong>詳細情報</strong></span>
	</div><div class="para">
		より詳細な情報はドキュメントの「クラウドインフラストラクチャコンセプト」を参照してください。
	</div></div><div xml:lang="ja-JP" class="section" id="networking-overview" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="networking-overview">1.3.3. ネットワーク</h3></div></div></div><div class="para">
		CloudStack では基本と拡張の 2 種類のネットワーク設定を提供します。
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				基本ネットワーク。 基本ネットワーク設定では、AWSスタイルのネットワークの単一共有ネットワークを提供します。セキュリティグループ(発信元 IP アドレスのフィルター) のようなレイヤー3 レベルの方法でゲストを分離できます。
			</div></li><li class="listitem"><div class="para">
				拡張ネットワーク。拡張ネットワー ク設定は、より洗練されたネットワーク技術をサポートします。このネットワークモデルを選択すると、より柔軟にゲストの ネットワークを定義できます。
			</div></li></ul></div><div class="para">
		詳しくは、「ネットワークセットアップ」を参照してください。
	</div></div></div></div><div xml:lang="ja-JP" class="chapter" id="building-with-maven" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第2章 CloudStack をビルドするための Maven の利用</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#source-build">2.1. Building CloudStack from Source</a></span></dt><dt><span class="section"><a href="#build-prerequisites">2.2. Build Procedure Prerequisites</a></span></dt><dt><span class="section"><a href="#building-with-maven-steps">2.3. ビルド手順</a></span></dt><dt><span class="section"><a href="#building-with-maven-deploy">2.4. テスト環境における展開</a></span></dt></dl></div><div xml:lang="ja-JP" class="section" id="source-build" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="source-build">2.1. Building CloudStack from Source</h2></div></div></div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
			Prior to the 4.0.0 incubating release, Ant was used to build CloudStack. A migration to Maven started in the 4.0.0 cycle, and has completed in 4.1.0.
		</div><div class="para">
			The website and the wiki contain up to date information on the build procedure at:
		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
					<a href="https://cwiki.apache.org/CLOUDSTACK/building-with-maven.html">https://cwiki.apache.org/CLOUDSTACK/building-with-maven.html</a>
				</div></li><li class="listitem"><div class="para">
					<a href="https://cwiki.apache.org/CLOUDSTACK/setting-up-cloudstack-development-environment.html">https://cwiki.apache.org/CLOUDSTACK/setting-up-cloudstack-development-environment.html</a>
				</div></li></ul></div></div></div><div class="para">
		The overarching steps to build CloudStack are:.
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				Install the prerequisites and setup your environment
			</div></li><li class="listitem"><div class="para">
				Understand that various Maven profiles and build targets
			</div></li><li class="listitem"><div class="para">
				Deploy and test your build
			</div></li><li class="listitem"><div class="para">
				If needed, learn how to build binaries
			</div></li></ul></div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
			Learning Maven is outside the scope of this documentation.
		</div><div class="para">
			Go to the Maven website at <a href="http://maven.apache.org/guides/getting-started/index.html">http://maven.apache.org/guides/getting-started/index.html</a>
		</div></div></div></div><div xml:lang="ja-JP" class="section" id="build-prerequisites" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="build-prerequisites">2.2. Build Procedure Prerequisites</h2></div></div></div><div class="para">
		In this section we will assume that you are using the Ubuntu Linux distribution with the Advanced Packaging Tool (APT). If you are using a different distribution or OS and a different packaging tool, adapt the following instructions to your environment. To build CloudStack you will need:
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				git, <a href="http://git-scm.com">http://git-scm.com</a>
			</div><div class="para">
				
<pre class="programlisting">sudo apt-get install git-core</pre>
			</div></li><li class="listitem"><div class="para">
				maven, <a href="http://maven.apache.org">http://maven.apache.org</a>
			</div><div class="para">
				
<pre class="programlisting">sudo apt-get install maven</pre>
			</div><div class="para">
				Make sure that you installed maven 3
			</div><div class="para">
				
<pre class="programlisting">$ mvn --version
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.2.0-33-generic", arch: "amd64", family: "unix"</pre>
			</div></li><li class="listitem"><div class="para">
				java
			</div><div class="para">
				set the JAVA_HOME environment variable
			</div><div class="para">
				
<pre class="programlisting">$ export JAVA_HOME=/usr/lib/jvm/java-6-openjdk</pre>
			</div></li></ul></div><div class="para">
		In addition, to deploy and run CloudStack in a development environment you will need:
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				Mysql
			</div><div class="para">
				
<pre class="programlisting">sudo apt-get install mysql-server-5.5</pre>
			</div><div class="para">
				Start the mysqld service and create a cloud user with cloud as a password
			</div></li><li class="listitem"><div class="para">
				Tomcat 6
			</div><div class="para">
				
<pre class="programlisting">sudo apt-get install tomcat6</pre>
			</div></li></ul></div></div><div xml:lang="ja-JP" class="section" id="building-with-maven-steps" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="building-with-maven-steps">2.3. ビルド手順</h2></div></div></div><div class="para">
		CloudStack はソースバージョンの管理に git を利用しており、まずソースコードを pull する必要があります。
	</div><pre class="programlisting">git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git</pre><div class="para">
		いくつかのプロジェクトオブジェクトモデル(POM)を様々な CloudStack ビルド対象のために定義しています。いくつかのパッケージは Apache ライセンスに非互換であり、独自にダウンロードが必要となります。さらなる情報に関しては wiki <a href="https://cwiki.apache.org/CLOUDSTACK/building-with-maven.html">https://cwiki.apache.org/CLOUDSTACK/building-with-maven.html</a> を参照してください。これは CloudStack の全てのオープンソースコンポーネントをビルドするために必要となります。
	</div><div class="para">
		
<pre class="programlisting">mvn clean install</pre>
	</div><div class="para">
		コンパイルされたモジュールのサブディレクトリ以下にある対象ディレクトリに結果として jar ファイルが生成されます。
	</div></div><div xml:lang="ja-JP" class="section" id="building-with-maven-deploy" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="building-with-maven-deploy">2.4. テスト環境における展開</h2></div></div></div><div class="para">
		以下の2つの手順によりコンパイルされた CloudStack コードは展開されます。
	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
				データベースを構成していない、もしくはプロパティを以下のように編集している場合
			</div><div class="para">
				
<pre class="programlisting">mvn -P developer -pl developer -Ddeploydb</pre>
			</div></li><li class="listitem"><div class="para">
				その場合、 CloudStack 管理サーバーを起動させる必要があります。デバッガを起動させるには以下のようにします。
			</div><div class="para">
				
<pre class="programlisting">export MAVEN_OPTS="-Xmx1024 -Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"</pre>
			</div><div class="para">
				
<pre class="programlisting">mvn -pl :cloud-client-ui jetty:run</pre>
			</div></li></ol></div><div class="warning"><div class="admonition_header"><h2>警告</h2></div><div class="admonition"><div class="para">
			データベースの内容を編集する場合はデータセンターに対し過去に設定した情報全体を削除することができます。
		</div></div></div></div></div><div xml:lang="ja-JP" class="chapter" id="developer-introduction" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第3章 Introduction to the CloudStack API</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#roles">3.1. Roles</a></span></dt><dt><span class="section"><a href="#api-reference">3.2. API リファレンス</a></span></dt><dt><span class="section"><a href="#getting-started">3.3. Getting Started</a></span></dt></dl></div><div xml:lang="ja-JP" class="section" id="roles" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="roles">3.1. Roles</h2></div></div></div><div class="para">
		The CloudStack API supports three access roles:
	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
				Root Admin. Access to all features of the cloud, including both virtual and physical resource management.
			</div></li><li class="listitem"><div class="para">
				Domain Admin. Access to only the virtual resources of the clouds that belong to the administrator’s domain.
			</div></li><li class="listitem"><div class="para">
				User. Access to only the features that allow management of the user’s virtual instances, storage, and network.
			</div></li></ol></div></div><div xml:lang="ja-JP" class="section" id="api-reference" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="api-reference">3.2. API リファレンス</h2></div></div></div><div class="para">
		全ての API リファレンスドキュメントは以下のサイトから入手できます。
	</div><div class="para">
		<a href="http://cloudstack.apache.org/docs/api/">http://cloudstack.apache.org/docs/api/</a>
	</div></div><div xml:lang="ja-JP" class="section" id="getting-started" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="getting-started">3.3. Getting Started</h2></div></div></div><div class="para">
		To get started using the CloudStack API, you should have the following:
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				URL of the CloudStack server you wish to integrate with.
			</div></li><li class="listitem"><div class="para">
				Both the API Key and Secret Key for an account. This should have been generated by the administrator of the cloud instance and given to you.
			</div></li><li class="listitem"><div class="para">
				Familiarity with HTTP GET/POST and query strings.
			</div></li><li class="listitem"><div class="para">
				Knowledge of either XML or JSON.
			</div></li><li class="listitem"><div class="para">
				Knowledge of a programming language that can generate HTTP requests; for example, Java or PHP.
			</div></li></ul></div></div></div><div xml:lang="ja-JP" class="chapter" id="whats-new" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第4章 APIにおける新機能</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#whats-new-in-api-4.1">4.1. What's New in the API for 4.1</a></span></dt><dd><dl><dt><span class="section"><a href="#add-remove-nic">4.1.1. Reconfiguring Physical Networks in VMs</a></span></dt><dt><span class="section"><a href="#ipv6-support">4.1.2. IPv6 Support in CloudStack</a></span></dt><dt><span class="section"><a href="#vmx-settings-dev">4.1.3. Additional VMX Settings</a></span></dt><dt><span class="section"><a href="#reset-ssh-key-dev">4.1.4. Resetting SSH Keys to Access VMs</a></span></dt><dt><span class="section"><a href="#changed-apicommands-4.1">4.1.5. Changed API Commands in 4.1</a></span></dt><dt><span class="section"><a href="#added-API-commands-4.1">4.1.6. Added API Commands in 4.1-incubating</a></span></dt></dl></dd><dt><span class="section"><a href="#whats-new-in-api-4.0">4.2. 4.0 APIでの新機能</a></span></dt><dd><dl><dt><span class="section"><a href="#changed-apicommands-4.0">4.2.1. 4.0.0-incubating で変更された API コマンド</a></span></dt><dt><span class="section"><a href="#added-API-commands-4.0">4.2.2. Added API Commands in 4.0.0-incubating</a></span></dt></dl></dd><dt><span class="section"><a href="#whats-new-in-api-3.0">4.3. 3.0 APIでの新機能</a></span></dt><dd><dl><dt><span class="section"><a href="#enabling-port-8096">4.3.1. Enabling Port 8096</a></span></dt><dt><span class="section"><a href="#stopped-vm">4.3.2. Stopped VM</a></span></dt><dt><span class="section"><a href="#change-to-behavior-of-list-commands">4.3.3. Change to Behavior of List Commands</a></span></dt><dt><span class="section"><a href="#removed-API-commands">4.3.4. 削除された API コマンド</a></span></dt><dt><span class="section"><a href="#added-API-commands">4.3.5. 3.0 にて追加された API コマンド</a></span></dt><dt><span class="section"><a href="#added-error-codes">4.3.6. Added CloudStack Error Codes</a></span></dt></dl></dd></dl></div><div class="para">
		次で説明する CloudStack バージョンの新機能はAPIで実装されています。
	</div><div class="section" id="whats-new-in-api-4.1"><div class="titlepage"><div><div><h2 class="title" id="whats-new-in-api-4.1">4.1. What's New in the API for 4.1</h2></div></div></div><div xml:lang="ja-JP" class="section" id="add-remove-nic" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="add-remove-nic">4.1.1. Reconfiguring Physical Networks in VMs</h3></div></div></div><div class="para">
		CloudStack provides the ability to move VMs between networks and reconfigure a VM's network. You can remove a VM from a physical network and add to a new physical network. You can also change the default physical network of a virtual machine. With this functionality, hybrid or traditional server loads can be accommodated with ease.
	</div><div class="para">
		This feature is supported on XenServer and KVM hypervisors.
	</div><div class="para">
		The following APIs have been added to support this feature. These API calls can function only while the VM is in running or stopped state.
	</div><div class="section" id="addnic"><div class="titlepage"><div><div><h4 class="title" id="addnic">4.1.1.1. addNicToVirtualMachine</h4></div></div></div><div class="para">
			The addNicToVirtualMachine API adds a new NIC to the specified VM on a selected network.
		</div><div class="informaltable"><table border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th align="left">
							<div class="para">
								parameter
							</div>
						</th><th align="left">
							<div class="para">
								description
							</div>
						</th><th align="left">
							<div class="para">
								値
							</div>
						</th></tr></thead><tbody><tr><td align="left">
							<div class="para">
								virtualmachineid
							</div>
						</td><td align="left">
							<div class="para">
								The unique ID of the VM to which the NIC is to be added.
							</div>
						</td><td align="left">
							<div class="para">
								true
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								networkid
							</div>
						</td><td align="left">
							<div class="para">
								The unique ID of the network the NIC that you add should apply to.
							</div>
						</td><td align="left">
							<div class="para">
								true
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								ipaddress
							</div>
						</td><td align="left">
							<div class="para">
								The IP address of the VM on the network.
							</div>
						</td><td align="left">
							<div class="para">
								false
							</div>
						</td></tr></tbody></table></div><div class="para">
			The network and VM must reside in the same zone. Two VMs with the same name cannot reside in the same network. Therefore, adding a second VM that duplicates a name on a network will fail.
		</div></div><div class="section" id="removenic"><div class="titlepage"><div><div><h4 class="title" id="removenic">4.1.1.2. removeNicFromVirtualMachine</h4></div></div></div><div class="para">
			The removeNicFromVirtualMachine API removes a NIC from the specified VM on a selected network.
		</div><div class="informaltable"><table border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th align="left">
							<div class="para">
								parameter
							</div>
						</th><th align="left">
							<div class="para">
								description
							</div>
						</th><th align="left">
							<div class="para">
								値
							</div>
						</th></tr></thead><tbody><tr><td align="left">
							<div class="para">
								virtualmachineid
							</div>
						</td><td align="left">
							<div class="para">
								The unique ID of the VM from which the NIC is to be removed.
							</div>
						</td><td align="left">
							<div class="para">
								true
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								nicid
							</div>
						</td><td align="left">
							<div class="para">
								The unique ID of the NIC that you want to remove.
							</div>
						</td><td align="left">
							<div class="para">
								true
							</div>
						</td></tr></tbody></table></div><div class="para">
			Removing the default NIC is not allowed.
		</div></div><div class="section" id="defaultnic"><div class="titlepage"><div><div><h4 class="title" id="defaultnic">4.1.1.3. updateDefaultNicForVirtualMachine</h4></div></div></div><div class="para">
			The updateDefaultNicForVirtualMachine API updates the specified NIC to be the default one for a selected VM.
		</div><div class="informaltable"><table border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th align="left">
							<div class="para">
								parameter
							</div>
						</th><th align="left">
							<div class="para">
								description
							</div>
						</th><th align="left">
							<div class="para">
								値
							</div>
						</th></tr></thead><tbody><tr><td align="left">
							<div class="para">
								virtualmachineid
							</div>
						</td><td align="left">
							<div class="para">
								The unique ID of the VM for which you want to specify the default NIC.
							</div>
						</td><td align="left">
							<div class="para">
								true
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								nicid
							</div>
						</td><td align="left">
							<div class="para">
								The unique ID of the NIC that you want to set as the default one.
							</div>
						</td><td align="left">
							<div class="para">
								true
							</div>
						</td></tr></tbody></table></div></div></div><div xml:lang="ja-JP" class="section" id="ipv6-support" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="ipv6-support">4.1.2. IPv6 Support in CloudStack</h3></div></div></div><div class="para">
		CloudStacksupports Internet Protocol version 6 (IPv6), the recent version of the Internet Protocol (IP) that defines routing the network traffic. IPv6 uses a 128-bit address that exponentially expands the current address space that is available to the users. IPv6 addresses consist of eight groups of four hexadecimal digits separated by colons, for example, 5001:0dt8:83a3:1012:1000:8s2e:0870:7454. CloudStack supports IPv6 for public IPs in shared networks. With IPv6 support, VMs in shared networks can obtain both IPv4 and IPv6 addresses from the DHCP server. You can deploy VMs either in a IPv6 or IPv4 network, or in a dual network environment. If IPv6 network is used, the VM generates a link-local IPv6 address by itself, and receives a stateful IPv6 address from the DHCPv6 server.
	</div><div class="para">
		IPv6 is supported only on KVM and XenServer hypervisors. The IPv6 support is only an experimental feature.
	</div><div class="para">
		Here's the sequence of events when IPv6 is used:
	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
				The administrator creates an IPv6 shared network in an advanced zone.
			</div></li><li class="listitem"><div class="para">
				The user deploys a VM in an IPv6 shared network.
			</div></li><li class="listitem"><div class="para">
				The user VM generates an IPv6 link local address by itself, and gets an IPv6 global or site local address through DHCPv6.
			</div><div class="para">
				For information on API changes, see <a class="xref" href="#changed-apicommands-4.1">「Changed API Commands in 4.1」</a>.
			</div></li></ol></div><div class="section" id="guidelines-ipv6"><div class="titlepage"><div><div><h4 class="title" id="guidelines-ipv6">4.1.2.1. Prerequisites and Guidelines</h4></div></div></div><div class="para">
			Consider the following:
		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
					CIDR size must be 64 for IPv6 networks.
				</div></li><li class="listitem"><div class="para">
					The DHCP client of the guest VMs should support generating DUID based on Link-layer Address (DUID- LL). DUID-LL derives from the MAC address of guest VMs, and therefore the user VM can be identified by using DUID. See <a href="http://tools.ietf.org/html/rfc3315">Dynamic Host Configuration Protocol for IPv6 </a>for more information.
				</div></li><li class="listitem"><div class="para">
					The gateway of the guest network generates Router Advisement and Response messages to Router Solicitation. The M (Managed Address Configuration) flag of Router Advisement should enable stateful IP address configuration. Set the M flag to where the end nodes receive their IPv6 addresses from the DHCPv6 server as opposed to the router or switch.
				</div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
						The M flag is the 1-bit Managed Address Configuration flag for Router Advisement. When set, Dynamic Host Configuration Protocol (DHCPv6) is available for address configuration in addition to any IPs set by using stateless address auto-configuration.
					</div></div></div></li><li class="listitem"><div class="para">
					Use the System VM template exclusively designed to support IPv6. Download the System VM template from <a href="http://cloudstack.apt-get.eu/systemvm/">http://cloudstack.apt-get.eu/systemvm/</a>.
				</div></li><li class="listitem"><div class="para">
					The concept of Default Network applies to IPv6 networks. However, unlike IPv4 CloudStack does not control the routing information of IPv6 in shared network; the choice of Default Network will not affect the routing in the user VM.
				</div></li><li class="listitem"><div class="para">
					In a multiple shared network, the default route is set by the rack router, rather than the DHCP server, which is out of CloudStack control. Therefore, in order for the user VM to get only the default route from the default NIC, modify the configuration of the user VM, and set non-default NIC's <code class="code">accept_ra</code> to 0 explicitly. The <code class="code">accept_ra</code> parameter accepts Router Advertisements and auto-configure <code class="code">/proc/sys/net/ipv6/conf/interface</code> with received data.
				</div></li></ul></div></div><div class="section" id="limitsipv6"><div class="titlepage"><div><div><h4 class="title" id="limitsipv6">4.1.2.2. Limitations of IPv6 in CloudStack </h4></div></div></div><div class="para">
			The following are not yet supported:
		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
					Security groups
				</div></li><li class="listitem"><div class="para">
					Userdata and metadata
				</div></li><li class="listitem"><div class="para">
					Passwords
				</div></li></ol></div></div><div class="section" id="network-conf-dhcpv6"><div class="titlepage"><div><div><h4 class="title" id="network-conf-dhcpv6">4.1.2.3. Guest VM Configuration for DHCPv6</h4></div></div></div><div class="para">
			For the guest VMs to get IPv6 address, run dhclient command manually on each of the VMs. Use DUID-LL to set up dhclient.
		</div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
				The IPv6 address is lost when a VM is stopped and started. Therefore, use the same procedure to get an IPv6 address when a VM is stopped and started.
			</div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
					Set up dhclient by using DUID-LL.
				</div><div class="para">
					Perform the following for DHCP Client 4.2 and above:
				</div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
							Run the following command on the selected VM to get the dhcpv6 offer from VR:
						</div><pre class="programlisting">dhclient -6 -D LL &lt;dev&gt;</pre></li></ol></div><div class="para">
					Perform the following for DHCP Client 4.1:
				</div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
							Open the following to the dhclient configuration file:
						</div><pre class="programlisting">vi /etc/dhcp/dhclient.conf</pre></li><li class="listitem"><div class="para">
							Add the following to the dhclient configuration file:
						</div><pre class="programlisting">send dhcp6.client-id = concat(00:03:00, hardware);</pre></li></ol></div></li><li class="listitem"><div class="para">
					Get IPv6 address from DHCP server as part of the system or network restart.
				</div><div class="para">
					Based on the operating systems, perform the following:
				</div><div class="para">
					On CentOS 6.2:
				</div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
							Open the Ethernet interface configuration file:
						</div><pre class="programlisting">vi /etc/sysconfig/network-scripts/ifcfg-eth0</pre><div class="para">
							The <code class="code">ifcfg-eth0</code> file controls the first NIC in a system.
						</div></li><li class="listitem"><div class="para">
							Make the necessary configuration changes, as given below:
						</div><pre class="programlisting">DEVICE=eth0
HWADDR=06:A0:F0:00:00:38
NM_CONTROLLED=no
ONBOOT=yes
BOOTPROTO=dhcp6
TYPE=Ethernet
USERCTL=no
PEERDNS=yes
IPV6INIT=yes
DHCPV6C=yes</pre></li><li class="listitem"><div class="para">
							Open the following:
						</div><pre class="programlisting">vi /etc/sysconfig/network</pre></li><li class="listitem"><div class="para">
							Make the necessary configuration changes, as given below:
						</div><pre class="programlisting">NETWORKING=yes
HOSTNAME=centos62mgmt.lab.vmops.com
NETWORKING_IPV6=yes
IPV6_AUTOCONF=no</pre></li></ol></div><div class="para">
					On Ubuntu 12.10
				</div><div class="orderedlist"><ol class="loweralpha"><li class="listitem"><div class="para">
							Open the following:
						</div><pre class="programlisting">etc/network/interfaces:</pre></li><li class="listitem"><div class="para">
							Make the necessary configuration changes, as given below:
						</div><pre class="programlisting">iface eth0 inet6 dhcp
autoconf 0
accept_ra 1</pre></li></ol></div></li></ol></div></div></div><div xml:lang="ja-JP" class="section" id="vmx-settings-dev" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="vmx-settings-dev">4.1.3. Additional VMX Settings</h3></div></div></div><div class="para">
		A VMX (.vmx) file is the primary configuration file for a virtual machine. When a new VM is created, information on the operating system, disk sizes, and networking is stored in this file. The VM actively writes to its .vmx file for all the configuration changes. The VMX file is typically located in the directory where the VM is created. In Windows Vista / Windows 7 / Windows Server 2008, the default location is C:\Users\&lt;your_user_name&gt;\My Documents\Virtual Machines\&lt;virtual_machine_name&gt;.vmx. In Linux, vmware-cmd -l lists the full path to all the registered VMX files. Any manual additions to the .vmx file from ESX/ESXi are overwritten by the entries stored in the vCenter Server database. Therefore, before you edit a .vmx file, first remove the VM from the vCenter server's inventory and register the VM again after editing.
	</div><div class="para">
		The CloudStack API that supports passing some of the VMX settings is registerTemplate. The supported parameters are rootDiskController, nicAdapter, and keyboard. In addition to these existing VMX parameters, you can now use the keyboard.typematicMinDelay parameter in the registerTemplate API call. This parameter controls the amount of delay for the repeated key strokes on remote consoles. For more information on keyboard.typematicMinDelay, see <a href=" http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=196">keyboard.typematicMinDelay</a>.
	</div></div><div xml:lang="ja-JP" class="section" id="reset-ssh-key-dev" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="reset-ssh-key-dev">4.1.4. Resetting SSH Keys to Access VMs</h3></div></div></div><div class="para">
		Use the resetSSHKeyForVirtualMachine API to set or reset the SSH keypair assigned to a virtual machine. With the addition of this feature, a lost or compromised SSH keypair can be changed, and the user can access the VM by using the new keypair. Just create or register a new keypair, then call resetSSHKeyForVirtualMachine.
	</div></div><div xml:lang="ja-JP" class="section" id="changed-apicommands-4.1" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="changed-apicommands-4.1">4.1.5. Changed API Commands in 4.1</h3></div></div></div><div class="informaltable"><table border="1"><colgroup><col width="50%" align="left" class="1" /><col width="50%" align="left" class="2" /></colgroup><thead><tr><th align="left">
						<div class="para">
							API Commands
						</div>
					</th><th align="left">
						<div class="para">
							Description
						</div>
					</th></tr></thead><tbody><tr><td align="left">
						<div class="para">
							createNetworkOffering
						</div>

					</td><td align="left">
						<div class="para">
							The following request parameters have been added:
						</div>
						 <div class="itemizedlist"><ul><li class="listitem"><div class="para">
									isPersistent
								</div></li><li class="listitem"><div class="para">
									startipv6
								</div></li><li class="listitem"><div class="para">
									endipv6
								</div></li><li class="listitem"><div class="para">
									ip6gateway
								</div></li><li class="listitem"><div class="para">
									ip6cidr
								</div></li></ul></div>

					</td></tr><tr><td align="left">
						<div class="para">
							listNetworkOfferings
						</div>
						 <div class="para">
							listNetworks
						</div>

					</td><td align="left">
						<div class="para">
							The following request parameters have been added:
						</div>
						 <div class="itemizedlist"><ul><li class="listitem"><div class="para">
									isPersistent
								</div><div class="para">
									This parameter determines if the network or network offering listed are persistent or not.
								</div></li><li class="listitem"><div class="para">
									ip6gateway
								</div></li><li class="listitem"><div class="para">
									ip6cidr
								</div></li></ul></div>

					</td></tr><tr><td align="left">
						<div class="para">
							createVlanIpRange
						</div>

					</td><td align="left">
						<div class="para">
							The following request parameters have been added:
						</div>
						 <div class="itemizedlist"><ul><li class="listitem"><div class="para">
									startipv6
								</div></li><li class="listitem"><div class="para">
									endipv6
								</div></li><li class="listitem"><div class="para">
									ip6gateway
								</div></li><li class="listitem"><div class="para">
									ip6cidr
								</div></li></ul></div>

					</td></tr><tr><td align="left">
						<div class="para">
							deployVirtualMachine
						</div>

					</td><td align="left">
						<div class="para">
							The following parameter has been added: ip6Address.
						</div>
						 <div class="para">
							The following parameter is updated to accept the IPv6 address: iptonetworklist.
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							CreateZoneCmd
						</div>

					</td><td align="left">
						<div class="para">
							The following parameter have been added: ip6dns1, ip6dns2.
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							listRouters
						</div>
						 <div class="para">
							listVirtualMachines
						</div>

					</td><td align="left">
						<div class="para">
							For nic responses, the following fields have been added.
						</div>
						 <div class="itemizedlist"><ul><li class="listitem"><div class="para">
									ip6address
								</div></li><li class="listitem"><div class="para">
									ip6gateway
								</div></li><li class="listitem"><div class="para">
									ip6cidr
								</div></li></ul></div>

					</td></tr><tr><td align="left">
						<div class="para">
							listVlanIpRanges
						</div>

					</td><td align="left">
						<div class="para">
							For nic responses, the following fields have been added.
						</div>
						 <div class="itemizedlist"><ul><li class="listitem"><div class="para">
									startipv6
								</div></li><li class="listitem"><div class="para">
									endipv6
								</div></li><li class="listitem"><div class="para">
									ip6gateway
								</div></li><li class="listitem"><div class="para">
									ip6cidr
								</div></li></ul></div>

					</td></tr><tr><td align="left">
						<div class="para">
							listRouters
						</div>
						 <div class="para">
							listZones
						</div>

					</td><td align="left">
						<div class="para">
							For DomainRouter and DataCenter response, the following fields have been added.
						</div>
						 <div class="itemizedlist"><ul><li class="listitem"><div class="para">
									ip6dns1
								</div></li><li class="listitem"><div class="para">
									ip6dns2
								</div></li></ul></div>

					</td></tr><tr><td align="left">
						<div class="para">
							addF5LoadBalancer
						</div>
						 <div class="para">
							configureNetscalerLoadBalancer
						</div>
						 <div class="para">
							addNetscalerLoadBalancer
						</div>
						 <div class="para">
							listF5LoadBalancers
						</div>
						 <div class="para">
							configureF5LoadBalancer
						</div>
						 <div class="para">
							listNetscalerLoadBalancers
						</div>

					</td><td align="left">
						<div class="para">
							The following response parameter is removed: inline.
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							listFirewallRules
						</div>
						 <div class="para">
							createFirewallRule
						</div>
					</td><td align="left">
						<div class="para">
							The following request parameter is added: traffictype (optional).
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							listUsageRecords
						</div>
					</td><td align="left">
						<div class="para">
							The following response parameter is added: virtualsize.
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							deleteIso
						</div>

					</td><td align="left">
						<div class="para">
							The following request parameter is added: forced (optional).
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							createStoragePool
						</div>

					</td><td align="left">
						<div class="para">
							The following request parameters are made mandatory:
						</div>
						 <div class="itemizedlist"><ul><li class="listitem"><div class="para">
									podid
								</div></li><li class="listitem"><div class="para">
									clusterid
								</div></li></ul></div>

					</td></tr><tr><td align="left">
						<div class="para">
							createAccount
						</div>
					</td><td align="left">
						<div class="para">
							The following new request parameters are added: accountid, userid
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							createUser
						</div>
					</td><td align="left">
						<div class="para">
							The following new request parameter is added: userid
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							createDomain
						</div>
					</td><td align="left">
						<div class="para">
							The following new request parameter is added: domainid
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							listZones
						</div>

					</td><td align="left">
						<div class="para">
							The following request parameters is added: securitygroupenabled
						</div>

					</td></tr></tbody></table></div></div><div xml:lang="ja-JP" class="section" id="added-API-commands-4.1" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="added-API-commands-4.1">4.1.6. Added API Commands in 4.1-incubating</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				createEgressFirewallRules (creates an egress firewall rule on the guest network.)
			</div></li><li class="listitem"><div class="para">
				deleteEgressFirewallRules (deletes a egress firewall rule on the guest network.)
			</div></li><li class="listitem"><div class="para">
				listEgressFirewallRules (lists the egress firewall rules configured for a guest network.)
			</div></li><li class="listitem"><div class="para">
				resetSSHKeyForVirtualMachine (Resets the SSHkey for virtual machine.)
			</div></li><li class="listitem"><div class="para">
				addBaremetalHost (Adds a new host.)
			</div></li><li class="listitem"><div class="para">
				addNicToVirtualMachine (Adds a new NIC to the specified VM on a selected network.)
			</div></li><li class="listitem"><div class="para">
				removeNicFromVirtualMachine (Removes the specified NIC from a selected VM.)
			</div></li><li class="listitem"><div class="para">
				updateDefaultNicForVirtualMachine (Updates the specified NIC to be the default one for a selected VM.)
			</div></li><li class="listitem"><div class="para">
				addRegion (Registers a Region into another Region.)
			</div></li><li class="listitem"><div class="para">
				updateRegion (Updates Region details: ID, Name, Endpoint, User API Key, and User Secret Key.)
			</div></li><li class="listitem"><div class="para">
				removeRegion (Removes a Region from current Region.)
			</div></li><li class="listitem"><div class="para">
				listRegions (List all the Regions. Filter them by using the ID or Name.)
			</div></li><li class="listitem"><div class="para">
				getUser (This API can only be used by the Admin. Get user details by using the API Key.)
			</div></li></ul></div></div></div><div class="section" id="whats-new-in-api-4.0"><div class="titlepage"><div><div><h2 class="title" id="whats-new-in-api-4.0">4.2. 4.0 APIでの新機能</h2></div></div></div><div xml:lang="ja-JP" class="section" id="changed-apicommands-4.0" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="changed-apicommands-4.0">4.2.1. 4.0.0-incubating で変更された API コマンド</h3></div></div></div><div class="informaltable"><table border="1"><colgroup><col width="33%" align="left" class="1" /><col width="67%" align="left" class="2" /></colgroup><thead><tr><th align="left">
						<div class="para">
							API コマンド
						</div>
					</th><th align="left">
						<div class="para">
							説明
						</div>
					</th></tr></thead><tbody><tr><td align="left">
						<div class="para">
							copyTemplate
						</div>
						 <div class="para">
							prepareTemplate
						</div>
						 <div class="para">
							registerTemplate
						</div>
						 <div class="para">
							updateTemplate
						</div>
						 <div class="para">
							createProject
						</div>
						 <div class="para">
							activateProject
						</div>
						 <div class="para">
							suspendProject
						</div>
						 <div class="para">
							updateProject
						</div>
						 <div class="para">
							listProjectAccounts
						</div>
						 <div class="para">
							createVolume
						</div>
						 <div class="para">
							migrateVolume
						</div>
						 <div class="para">
							attachVolume
						</div>
						 <div class="para">
							detachVolume
						</div>
						 <div class="para">
							uploadVolume
						</div>
						 <div class="para">
							createSecurityGroup
						</div>
						 <div class="para">
							registerIso
						</div>
						 <div class="para">
							copyIso
						</div>
						 <div class="para">
							updateIso
						</div>
						 <div class="para">
							createIpForwardingRule
						</div>
						 <div class="para">
							listIpForwardingRules
						</div>
						 <div class="para">
							createLoadBalancerRule
						</div>
						 <div class="para">
							updateLoadBalancerRule
						</div>
						 <div class="para">
							createSnapshot
						</div>

					</td><td align="left">
						<div class="para">
							ここに記述されたコマンドは単一の新しいレスポンスパラメーターを持ち、それ以外の変更点はありません。
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: tags(*)
						</div>
						 <div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
								その他の多くのコマンドは新しい tags(*) パラメーターを持ちその他の変更点を含みます。これらのコマンドを別途記述します。
							</div></div></div>
					</td></tr><tr><td align="left">
						<div class="para">
							rebootVirtualMachine
						</div>
						 <div class="para">
							attachIso
						</div>
						 <div class="para">
							detachIso
						</div>
						 <div class="para">
							listLoadBalancerRuleInstances
						</div>
						 <div class="para">
							resetPasswordForVirtualMachine
						</div>
						 <div class="para">
							changeServiceForVirtualMachine
						</div>
						 <div class="para">
							recoverVirtualMachine
						</div>
						 <div class="para">
							startVirtualMachine
						</div>
						 <div class="para">
							migrateVirtualMachine
						</div>
						 <div class="para">
							deployVirtualMachine
						</div>
						 <div class="para">
							assignVirtualMachine
						</div>
						 <div class="para">
							updateVirtualMachine
						</div>
						 <div class="para">
							restoreVirtualMachine
						</div>
						 <div class="para">
							stopVirtualMachine
						</div>
						 <div class="para">
							destroyVirtualMachine
						</div>

					</td><td align="left">
						<div class="para">
							ここに記述されたコマンドは 2つの新しいレスポンスパラメーターを持ち、それ以外の変更点はありません。
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: keypair, tags(*)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							listSecurityGroups
						</div>
						 <div class="para">
							listFirewallRules
						</div>
						 <div class="para">
							listPortForwardingRules
						</div>
						 <div class="para">
							listSnapshots
						</div>
						 <div class="para">
							listIsos
						</div>
						 <div class="para">
							listProjects
						</div>
						 <div class="para">
							listTemplates
						</div>
						 <div class="para">
							listLoadBalancerRules
						</div>

					</td><td align="left">
						<div class="para">
							ここに記述されたコマンドは以下の新しいパラメーターを持ち、それ以外の変更点はありません。
						</div>
						 <div class="para">
							新しいリクエストパラメーター: tags (オプション)
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: tags(*)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							listF5LoadBalancerNetworks
						</div>
						 <div class="para">
							listNetscalerLoadBalancerNetworks
						</div>
						 <div class="para">
							listSrxFirewallNetworks
						</div>
						 <div class="para">
							updateNetwork
						</div>

					</td><td align="left">
						<div class="para">
							ここに記述されたコマンドは 3つの新しいレスポンスパラメーターを持ち、それ以外の変更点はありません。
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: canusefordeploy, vpcid, tags(*)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							createZone
						</div>
						 <div class="para">
							updateZone
						</div>

					</td><td align="left">
						<div class="para">
							ここに記述されたコマンドは以下の新しいパラメーターを持ち、それ以外の変更点はありません。
						</div>
						 <div class="para">
							新しいリクエストパラメーター: localstorageenabled (オプション)
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: localstorageenabled
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							listZones
						</div>
					</td><td align="left">
						<div class="para">
							新しいレスポンスパラメーター: localstorageenabled
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							rebootRouter
						</div>
						 <div class="para">
							changeServiceForRouter
						</div>
						 <div class="para">
							startRouter
						</div>
						 <div class="para">
							destroyRouter
						</div>
						 <div class="para">
							stopRouter
						</div>

					</td><td align="left">
						<div class="para">
							ここに記述されたコマンドは 2つの新しいレスポンスパラメーターを持ち、それ以外の変更点はありません。
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: vpcid, nic(*)
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							updateAccount
						</div>
						 <div class="para">
							disableAccount
						</div>
						 <div class="para">
							listAccounts
						</div>
						 <div class="para">
							markDefaultZoneForAccount
						</div>
						 <div class="para">
							enableAccount
						</div>

					</td><td align="left">
						<div class="para">
							ここに記述されたコマンドは 3つの新しいレスポンスパラメーターを持ち、それ以外の変更点はありません。
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: vpcavailable, vpclimit, vpctotal
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							listRouters
						</div>
					</td><td align="left">
						<div class="para">
							新しいリクエストパラメーター: forvpc (オプション), vpcid (オプション)
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: vpcid, nic(*)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							listNetworkOfferings
						</div>
					</td><td align="left">
						<div class="para">
							新しいリクエストパラメーター: forvpc(オプション)
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: forvpc
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							listVolumes
						</div>
					</td><td align="left">
						<div class="para">
							新しいリクエストパラメーター: detais (オプション), tags (オプション)
						</div>
						 <div class="para">
							新しいリクエストパラメーター: tags(*)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							addTrafficMonitor
						</div>
					</td><td align="left">
						<div class="para">
							新しいリクエストパラメーター: excludezones (オプション), includezones (オプション)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							createNetwork
						</div>
					</td><td align="left">
						<div class="para">
							新しいリクエストパラメーター: vpcid (オプション)
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: canusefordeploy, vpcid, tags(*)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							listPublicIpAddresses
						</div>
					</td><td align="left">
						<div class="para">
							新しいリクエストパラメーター: tags (オプション), vpcid (オプション)
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: vpcid, tags(*)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							listNetworks
						</div>
					</td><td align="left">
						<div class="para">
							新しいリクエストパラメーター: canusefordeploy (オプション), forvpc (オプション), tags (オプション), vpcid (オプション)
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: canusefordeploy, vpcid, tags(*)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							restartNetwork
						</div>
					</td><td align="left">
						<div class="para">
							新しいレスポンスパラメーター: vpcid, tags(*)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							enableStaticNat
						</div>
					</td><td align="left">
						<div class="para">
							新しいリクエストパラメーター: networkid (オプション)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							createDiskOffering
						</div>
					</td><td align="left">
						<div class="para">
							新しいリクエストパラメーター: storagetype (オプション)
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: storagetype
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							listDiskOfferings
						</div>
					</td><td align="left">
						<div class="para">
							新しいレスポンスパラメーター: storagetype
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							updateDiskOffering
						</div>
					</td><td align="left">
						<div class="para">
							新しいレスポンスパラメーター: storagetype
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							createFirewallRule
						</div>
					</td><td align="left">
						<div class="para">
							変更されたリクエストパラメーター: ipaddressid (古いバージョン - オプション, 新しいバージョン - 必須)
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: tags(*)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							listVirtualMachines
						</div>
					</td><td align="left">
						<div class="para">
							新しいリクエストパラメーター: isoid (オプション), tags (オプション), templateid (オプション)
						</div>
						 <div class="para">
							新しいレスポンスパラメーター: keypair, tags(*)
						</div>

					</td></tr><tr><td align="left">
						<div class="para">
							updateStorageNetworkIpRange
						</div>
					</td><td align="left">
						<div class="para">
							新しいレスポンスパラメーター: id, endip, gateway, netmask, networkid, podid, startip, vlan, zoneid
						</div>

					</td></tr></tbody></table></div></div><div xml:lang="ja-JP" class="section" id="added-API-commands-4.0" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="added-API-commands-4.0">4.2.2. Added API Commands in 4.0.0-incubating</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				createCounter (Adds metric counter)
			</div></li><li class="listitem"><div class="para">
				deleteCounter (Deletes a counter)
			</div></li><li class="listitem"><div class="para">
				listCounters (List the counters)
			</div></li><li class="listitem"><div class="para">
				createCondition (Creates a condition)
			</div></li><li class="listitem"><div class="para">
				deleteCondition (Removes a condition)
			</div></li><li class="listitem"><div class="para">
				listConditions (List Conditions for the specific user)
			</div></li><li class="listitem"><div class="para">
				createTags. Add tags to one or more resources. Example: 
<pre class="programlisting">command=createTags
&amp;resourceIds=1,10,12
&amp;resourceType=userVm
&amp;tags[0].key=region
&amp;tags[0].value=canada
&amp;tags[1].key=city
&amp;tags[1].value=Toronto</pre>
			</div></li><li class="listitem"><div class="para">
				deleteTags. Remove tags from one or more resources. Example: 
<pre class="programlisting">command=deleteTags
&amp;resourceIds=1,12
&amp;resourceType=Snapshot
&amp;tags[0].key=city</pre>
			</div></li><li class="listitem"><div class="para">
				listTags (Show currently defined resource tags)
			</div></li><li class="listitem"><div class="para">
				createVPC (Creates a VPC)
			</div></li><li class="listitem"><div class="para">
				listVPCs (Lists VPCs)
			</div></li><li class="listitem"><div class="para">
				deleteVPC (Deletes a VPC)
			</div></li><li class="listitem"><div class="para">
				updateVPC (Updates a VPC)
			</div></li><li class="listitem"><div class="para">
				restartVPC (Restarts a VPC)
			</div></li><li class="listitem"><div class="para">
				createVPCOffering (Creates VPC offering)
			</div></li><li class="listitem"><div class="para">
				updateVPCOffering (Updates VPC offering)
			</div></li><li class="listitem"><div class="para">
				deleteVPCOffering (Deletes VPC offering)
			</div></li><li class="listitem"><div class="para">
				listVPCOfferings (Lists VPC offerings)
			</div></li><li class="listitem"><div class="para">
				createPrivateGateway (Creates a private gateway)
			</div></li><li class="listitem"><div class="para">
				listPrivateGateways (List private gateways)
			</div></li><li class="listitem"><div class="para">
				deletePrivateGateway (Deletes a Private gateway)
			</div></li><li class="listitem"><div class="para">
				createNetworkACL (Creates a ACL rule the given network (the network has to belong to VPC))
			</div></li><li class="listitem"><div class="para">
				deleteNetworkACL (Deletes a Network ACL)
			</div></li><li class="listitem"><div class="para">
				listNetworkACLs (Lists all network ACLs)
			</div></li><li class="listitem"><div class="para">
				createStaticRoute (Creates a static route)
			</div></li><li class="listitem"><div class="para">
				deleteStaticRoute (Deletes a static route)
			</div></li><li class="listitem"><div class="para">
				listStaticRoutes (Lists all static routes)
			</div></li><li class="listitem"><div class="para">
				createVpnCustomerGateway (Creates site to site vpn customer gateway)
			</div></li><li class="listitem"><div class="para">
				createVpnGateway (Creates site to site vpn local gateway)
			</div></li><li class="listitem"><div class="para">
				createVpnConnection (Create site to site vpn connection)
			</div></li><li class="listitem"><div class="para">
				deleteVpnCustomerGateway (Delete site to site vpn customer gateway)
			</div></li><li class="listitem"><div class="para">
				deleteVpnGateway (Delete site to site vpn gateway)
			</div></li><li class="listitem"><div class="para">
				deleteVpnConnection (Delete site to site vpn connection)
			</div></li><li class="listitem"><div class="para">
				updateVpnCustomerGateway (Update site to site vpn customer gateway)
			</div></li><li class="listitem"><div class="para">
				resetVpnConnection (Reset site to site vpn connection)
			</div></li><li class="listitem"><div class="para">
				listVpnCustomerGateways (Lists site to site vpn customer gateways)
			</div></li><li class="listitem"><div class="para">
				listVpnGateways (Lists site 2 site vpn gateways)
			</div></li><li class="listitem"><div class="para">
				listVpnConnections (Lists site to site vpn connection gateways)
			</div></li><li class="listitem"><div class="para">
				enableCiscoNexusVSM (Enables Nexus 1000v dvSwitch in CloudStack.)
			</div></li><li class="listitem"><div class="para">
				disableCiscoNexusVSM (Disables Nexus 1000v dvSwitch in CloudStack.)
			</div></li><li class="listitem"><div class="para">
				deleteCiscoNexusVSM (Deletes Nexus 1000v dvSwitch in CloudStack.)
			</div></li><li class="listitem"><div class="para">
				listCiscoNexusVSMs (Lists the control VLAN ID, packet VLAN ID, and data VLAN ID, as well as the IP address of the Nexus 1000v dvSwitch.)
			</div></li></ul></div></div></div><div class="section" id="whats-new-in-api-3.0"><div class="titlepage"><div><div><h2 class="title" id="whats-new-in-api-3.0">4.3. 3.0 APIでの新機能</h2></div></div></div><div xml:lang="ja-JP" class="section" id="enabling-port-8096" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="enabling-port-8096">4.3.1. Enabling Port 8096</h3></div></div></div><div class="para">
		Port 8096, which allows API calls without authentication, is closed and disabled by default on any fresh 3.0.1 installations. You can enable 8096 (or another port) for this purpose as follows:
	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
				Ensure that the first Management Server is installed and running.
			</div></li><li class="listitem"><div class="para">
				Set the global configuration parameter integration.api.port to the desired port.
			</div></li><li class="listitem"><div class="para">
				管理サーバーを再起動します。
			</div></li><li class="listitem"><div class="para">
				On the Management Server host machine, create an iptables rule allowing access to that port.
			</div></li></ol></div></div><div xml:lang="ja-JP" class="section" id="stopped-vm" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="stopped-vm">4.3.2. Stopped VM</h3></div></div></div><div class="para">
		CloudStack now supports creating a VM without starting it. You can determine whether the VM needs to be started as part of the VM deployment. A VM can now be deployed in two ways: create and start a VM (the default method); or create a VM and leave it in the stopped state.
	</div><div class="para">
		A new request parameter, startVM, is introduced in the deployVm API to support the stopped VM feature.
	</div><div class="para">
		The possible values are:
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				true - The VM starts as a part of the VM deployment.
			</div></li><li class="listitem"><div class="para">
				false - The VM is left in the stopped state at the end of the VM deployment.
			</div></li></ul></div><div class="para">
		The default value is true.
	</div></div><div xml:lang="ja-JP" class="section" id="change-to-behavior-of-list-commands" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="change-to-behavior-of-list-commands">4.3.3. Change to Behavior of List Commands</h3></div></div></div><div class="para">
		There was a major change in how our List* API commands work in CloudStack 3.0 compared to 2.2.x. The rules below apply only for managed resources – those that belong to an account, domain, or project. They are irrelevant for the List* commands displaying unmanaged (system) resources, such as hosts, clusters, and external network resources.
	</div><div class="para">
		When no parameters are passed in to the call, the caller sees only resources owned by the caller (even when the caller is the administrator). Previously, the administrator saw everyone else's resources by default.
	</div><div class="para">
		When accountName and domainId are passed in:
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				The caller sees the resources dedicated to the account specified.
			</div></li><li class="listitem"><div class="para">
				If the call is executed by a regular user, the user is authorized to specify only the user's own account and domainId.
			</div></li><li class="listitem"><div class="para">
				If the caller is a domain administrator, CloudStack performs an authorization check to see whether the caller is permitted to view resources for the given account and domainId.
			</div></li></ul></div><div class="para">
		When projectId is passed in, only resources belonging to that project are listed.
	</div><div class="para">
		When domainId is passed in, the call returns only resources belonging to the domain specified. To see the resources of subdomains, use the parameter isRecursive=true. Again, the regular user can see only resources owned by that user, the root administrator can list anything, and a domain administrator is authorized to see only resources of the administrator's own domain and subdomains.
	</div><div class="para">
		To see all resources the caller is authorized to see, except for Project resources, use the parameter listAll=true.
	</div><div class="para">
		To see all Project resources the caller is authorized to see, use the parameter projectId=-1.
	</div><div class="para">
		There is one API command that doesn't fall under the rules above completely: the listTemplates command. This command has its own flags defining the list rules:
	</div><div class="informaltable"><table border="1"><colgroup><col align="left" class="c1" width="50%" /><col align="left" class="c2" width="50%" /></colgroup><thead><tr><th align="left">
						<div class="para">
							listTemplates Flag
						</div>
					</th><th align="left">
						<div class="para">
							説明
						</div>
					</th></tr></thead><tbody><tr><td align="left">
						<div class="para">
							featured
						</div>
					</td><td align="left">
						<div class="para">
							Returns templates that have been marked as featured and public.
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							self
						</div>
					</td><td align="left">
						<div class="para">
							Returns templates that have been registered or created by the calling user.
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							selfexecutable
						</div>
					</td><td align="left">
						<div class="para">
							Same as self, but only returns templates that are ready to be deployed with.
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							sharedexecutable
						</div>
					</td><td align="left">
						<div class="para">
							Ready templates that have been granted to the calling user by another user.
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							executable
						</div>
					</td><td align="left">
						<div class="para">
							Templates that are owned by the calling user, or public templates, that can be used to deploy a new VM.
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							community
						</div>
					</td><td align="left">
						<div class="para">
							Returns templates that have been marked as public but not featured.
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							all
						</div>
					</td><td align="left">
						<div class="para">
							Returns all templates (only usable by admins).
						</div>
					</td></tr></tbody></table></div><div class="para">
		The CloudStack UI on a general view will display all resources that the logged-in user is authorized to see, except for project resources. To see the project resources, select the project view.
	</div></div><div xml:lang="ja-JP" class="section" id="removed-API-commands" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="removed-API-commands">4.3.4. 削除された API コマンド</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				createConfiguration (設置値の追加)
			</div></li><li class="listitem"><div class="para">
				configureSimulator (構成シュミレーター)
			</div></li></ul></div></div><div xml:lang="ja-JP" class="section" id="added-API-commands" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="added-API-commands">4.3.5. 3.0 にて追加された API コマンド</h3></div></div></div><div class="section" id="added-api-commands-3.0.2"><div class="titlepage"><div><div><h4 class="title" id="added-api-commands-3.0.2">4.3.5.1. 3.0.2 にて追加</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
					changeServiceForSystemVm
				</div><div class="para">
					システム仮想マシン(コンソールプロキシーやセカンダリストレージ)のサービスオファリングを変更します。このコマンドを反映させるにはシステム仮想マシンは停止状態である必要があります。
				</div></li></ul></div></div><div class="section" id="added-api-commands-3.0.1"><div class="titlepage"><div><div><h4 class="title" id="added-api-commands-3.0.1">4.3.5.2. 3.0.1 にて追加</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
					changeServiceForSystemVm
				</div><div class="para">
					システム仮想マシン(コンソールプロキシーやセカンダリストレージ)のサービスオファリングを変更します。このコマンドを反映させるにはシステム仮想マシンは停止状態である必要があります。
				</div></li></ul></div></div><div class="section" id="added-api-commands-3.0.0"><div class="titlepage"><div><div><h4 class="title" id="added-api-commands-3.0.0">4.3.5.3. 3.0.0 にて追加</h4></div></div></div><div class="informaltable"><table border="1"><colgroup><col align="left" class="c1" width="33%" /><col align="left" class="c2" width="33%" /><col align="left" class="c3" width="33%" /></colgroup><tbody><tr><td align="left">
							<div class="para">
								assignVirtualMachine (ユーザーの仮想マシンを同一ドメインの他のユーザーに割り当てます)
							</div>
						</td><td align="left">
							<div class="para">
								restoreVirtualMachine (オリジナルのテンプレートや特定のスナップショットから仮想マシンをリストアします)
							</div>
						</td><td align="left">
							<div class="para">
								createLBStickinessPolicy (スティックネスポリシーの負荷分散装置を作成します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								deleteLBStickinessPolicy (スティックネスポリシーの負荷分散装置を削除します)
							</div>
						</td><td align="left">
							<div class="para">
								listLBStickinessPolicies (スティックネスポリシーを持つ負荷分散装置をリスト表示します)
							</div>
						</td><td align="left">
							<div class="para">
								ldapConfig (サイトにおける LDAP コンテキストを変更します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								addSwift (Swift を追加します)
							</div>
						</td><td align="left">
							<div class="para">
								listSwifts (Swift をリスト表示します)
							</div>
						</td><td align="left">
							<div class="para">
								migrateVolume (ボリュームを移行します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								updateStoragePool (ストレージプールを更新します)
							</div>
						</td><td align="left">
							<div class="para">
								authorizeSecurityGroupEgress (セキュリティグループに対し特定の出力規則を認証します)
							</div>
						</td><td align="left">
							<div class="para">
								revokeSecurityGroupEgress (セキュリティグループに対し特定の出力規則を削除します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								createNetworkOffering (ネットワークオファリングを作成します)
							</div>
						</td><td align="left">
							<div class="para">
								deleteNetworkOffering (ネットワークオファリングを削除します)
							</div>
						</td><td align="left">
							<div class="para">
								createProject (プロジェクトを作成します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								deleteProject (プロジェクトを削除します)
							</div>
						</td><td align="left">
							<div class="para">
								updateProject (プロジェクトを更新します)
							</div>
						</td><td align="left">
							<div class="para">
								activateProject (プロジェクトを始動させます)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								suspendProject (プロジェクトを一時停止させます)
							</div>
						</td><td align="left">
							<div class="para">
								listProjects (プロジェクトをリスト表示し、各プロジェクトに関する詳細情報を提示します)
							</div>
						</td><td align="left">
							<div class="para">
								addAccountToProject (Adds account to a project)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								deleteAccountFromProject (プロジェクトからアカウントを削除します)
							</div>
						</td><td align="left">
							<div class="para">
								listProjectAccounts (プロジェクトに所属するアカウントをリスト表示します)
							</div>
						</td><td align="left">
							<div class="para">
								listProjectInvitations (プロジェクトに参加するための招待をリスト表示します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								updateProjectInvitation (プロジェクトの招待を受理もしくは拒否します)
							</div>
						</td><td align="left">
							<div class="para">
								deleteProjectInvitation (プロジェクトの招待を削除します)
							</div>
						</td><td align="left">
							<div class="para">
								updateHypervisorCapabilities (ハイパーバイザーの性能情報を更新します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								listHypervisorCapabilities (ハイパーバイザーの全ての性能情報をリスト表示します)
							</div>
						</td><td align="left">
							<div class="para">
								createPhysicalNetwork (物理ネットワークを作成します)
							</div>
						</td><td align="left">
							<div class="para">
								deletePhysicalNetwork (物理ネットワークを削除します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								listPhysicalNetworks (物理ネットワークをリスト表示します)
							</div>
						</td><td align="left">
							<div class="para">
								updatePhysicalNetwork (物理ネットワークを更新します)
							</div>
						</td><td align="left">
							<div class="para">
								listSupportedNetworkServices (全ての CloudStack もしくは特定のプロバイダーによって提供されるネットワークサービスをリスト表示します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								addNetworkServiceProvider (物理ネットワークにネットワークサービスプロバイダーを追加します)
							</div>
						</td><td align="left">
							<div class="para">
								deleteNetworkServiceProvider (ネットワークサービスプロバイダーを削除します)
							</div>
						</td><td align="left">
							<div class="para">
								listNetworkServiceProviders (物理ネットワークで提供されるサービスプロバイダーをリスト表示します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								updateNetworkServiceProvider (物理ネットワークのネットワークサービスプロバイダーを更新します)
							</div>
						</td><td align="left">
							<div class="para">
								addTrafficType (物理ネットワークにトラフィックタイプを追加します)
							</div>
						</td><td align="left">
							<div class="para">
								deleteTrafficType (物理ネットワークのトラフィックタイプを削除します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								listTrafficTypes (物理ネットワークで提供されるトラフィックタイプをリスト表示します)
							</div>
						</td><td align="left">
							<div class="para">
								updateTrafficType (物理ネットワークのトラフィックタイプを更新します)
							</div>
						</td><td align="left">
							<div class="para">
								listTrafficTypeImplementors (全てのネットワークトラフィックタイプの提供者もしくは特定トラフィックタイプの提供者をリスト表示します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								createStorageNetworkIpRange (ストレージネットワークの IP 範囲を作成します)
							</div>
						</td><td align="left">
							<div class="para">
								deleteStorageNetworkIpRange (ストレージネットワークの IP 範囲を削除します)
							</div>
						</td><td align="left">
							<div class="para">
								listStorageNetworkIpRange (ストレージネットワークの IP 範囲をリスト表示します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								updateStorageNetworkIpRange (ストレージネットワークの IP 範囲を更新します。範囲に対して IP が使用中でない場合のみ利用できます)
							</div>
						</td><td align="left">
							<div class="para">
								listUsageTypes (利用タイプをリスト表示します)
							</div>
						</td><td align="left">
							<div class="para">
								addF5LoadBalancer (F5 BigIP 負荷分散装置を追加します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								configureF5LoadBalancer (F5 負荷分散装置を設定します)
							</div>
						</td><td align="left">
							<div class="para">
								deleteF5LoadBalancer (F5 負荷分散装置を削除します)
							</div>
						</td><td align="left">
							<div class="para">
								listF5LoadBalancers (F5 負荷分散装置をリスト表示します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								listF5LoadBalancerNetworks (F5 負荷分散装置を利用しているネットワークをリスト表示します)
							</div>
						</td><td align="left">
							<div class="para">
								addSrxFirewall (SRX ファイアウォールを追加します)
							</div>
						</td><td align="left">
							<div class="para">
								deleteSrxFirewall (SRX ファイアウォールを削除します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								listSrxFirewalls (物理ネットワーク上の SRX ファイアウォールをリスト表示します)
							</div>
						</td><td align="left">
							<div class="para">
								listSrxFirewallNetworks (SRX ファイアウォールを利用しているネットワークをリスト表示します)
							</div>
						</td><td align="left">
							<div class="para">
								addNetscalerLoadBalancer (NetScaler 負荷分散装置を追加します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								deleteNetscalerLoadBalancer (NetScaler 負荷分散装置を削除します)
							</div>
						</td><td align="left">
							<div class="para">
								configureNetscalerLoadBalancer (NetScaler 負荷分散装置を設定します)
							</div>
						</td><td align="left">
							<div class="para">
								listNetscalerLoadBalancers (NetScaler 負荷分散装置をリスト表示します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								listNetscalerLoadBalancerNetworks (NetScaler 負荷分散装置を利用しているネットワークをリスト表示します)
							</div>
						</td><td align="left">
							<div class="para">
								createVirtualRouterElement (仮想ルーターを作成します)
							</div>
						</td><td align="left">
							<div class="para">
								configureVirtualRouterElement (仮想マシンを設定します)
							</div>
						</td></tr><tr><td align="left">
							<div class="para">
								listVirtualRouterElements (全ての利用可能な仮想ルーターをリスト表示します)
							</div>
						</td><td align="left">
							<div class="para">
							</div>
						</td><td align="left">
							<div class="para">
							</div>
						</td></tr></tbody></table></div></div></div><div xml:lang="ja-JP" class="section" id="added-error-codes" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="added-error-codes">4.3.6. Added CloudStack Error Codes</h3></div></div></div><div class="para">
		You can now find the CloudStack-specific error code in the exception response for each type of exception. The following list of error codes is added to the new class named CSExceptionErrorCode.
	</div><div class="informaltable"><table border="1"><colgroup><col align="left" class="c1" width="33%" /><col align="left" class="c2" width="33%" /><col align="left" class="c3" width="33%" /></colgroup><tbody><tr><td align="left">
						<div class="para">
							4250 : "com.cloud.utils.exception.CloudRuntimeException"
						</div>
					</td><td align="left">
						<div class="para">
							4255 : "com.cloud.utils.exception.ExceptionUtil"
						</div>
					</td><td align="left">
						<div class="para">
							4260 : "com.cloud.utils.exception.ExecutionException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4265 : "com.cloud.utils.exception.HypervisorVersionChangedException"
						</div>
					</td><td align="left">
						<div class="para">
							4270 : "com.cloud.utils.exception.RuntimeCloudException"
						</div>
					</td><td align="left">
						<div class="para">
							4275 : "com.cloud.exception.CloudException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4280 : "com.cloud.exception.AccountLimitException"
						</div>
					</td><td align="left">
						<div class="para">
							4285 : "com.cloud.exception.AgentUnavailableException"
						</div>
					</td><td align="left">
						<div class="para">
							4290 : "com.cloud.exception.CloudAuthenticationException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4295 : "com.cloud.exception.CloudExecutionException"
						</div>
					</td><td align="left">
						<div class="para">
							4300 : "com.cloud.exception.ConcurrentOperationException"
						</div>
					</td><td align="left">
						<div class="para">
							4305 : "com.cloud.exception.ConflictingNetworkSettingsException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4310 : "com.cloud.exception.DiscoveredWithErrorException"
						</div>
					</td><td align="left">
						<div class="para">
							4315 : "com.cloud.exception.HAStateException"
						</div>
					</td><td align="left">
						<div class="para">
							4320 : "com.cloud.exception.InsufficientAddressCapacityException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4325 : "com.cloud.exception.InsufficientCapacityException"
						</div>
					</td><td align="left">
						<div class="para">
							4330 : "com.cloud.exception.InsufficientNetworkCapacityException"
						</div>
					</td><td align="left">
						<div class="para">
							4335 : "com.cloud.exception.InsufficientServerCapacityException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4340 : "com.cloud.exception.InsufficientStorageCapacityException"
						</div>
					</td><td align="left">
						<div class="para">
							4345 : "com.cloud.exception.InternalErrorException"
						</div>
					</td><td align="left">
						<div class="para">
							4350 : "com.cloud.exception.InvalidParameterValueException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4355 : "com.cloud.exception.ManagementServerException"
						</div>
					</td><td align="left">
						<div class="para">
							4360 : "com.cloud.exception.NetworkRuleConflictException"
						</div>
					</td><td align="left">
						<div class="para">
							4365 : "com.cloud.exception.PermissionDeniedException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4370 : "com.cloud.exception.ResourceAllocationException"
						</div>
					</td><td align="left">
						<div class="para">
							4375 : "com.cloud.exception.ResourceInUseException"
						</div>
					</td><td align="left">
						<div class="para">
							4380 : "com.cloud.exception.ResourceUnavailableException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4385 : "com.cloud.exception.StorageUnavailableException"
						</div>
					</td><td align="left">
						<div class="para">
							4390 : "com.cloud.exception.UnsupportedServiceException"
						</div>
					</td><td align="left">
						<div class="para">
							4395 : "com.cloud.exception.VirtualMachineMigrationException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4400 : "com.cloud.exception.AccountLimitException"
						</div>
					</td><td align="left">
						<div class="para">
							4405 : "com.cloud.exception.AgentUnavailableException"
						</div>
					</td><td align="left">
						<div class="para">
							4410 : "com.cloud.exception.CloudAuthenticationException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4415 : "com.cloud.exception.CloudException"
						</div>
					</td><td align="left">
						<div class="para">
							4420 : "com.cloud.exception.CloudExecutionException"
						</div>
					</td><td align="left">
						<div class="para">
							4425 : "com.cloud.exception.ConcurrentOperationException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4430 : "com.cloud.exception.ConflictingNetworkSettingsException"
						</div>
					</td><td align="left">
						<div class="para">
							4435 : "com.cloud.exception.ConnectionException"
						</div>
					</td><td align="left">
						<div class="para">
							4440 : "com.cloud.exception.DiscoveredWithErrorException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4445 : "com.cloud.exception.DiscoveryException"
						</div>
					</td><td align="left">
						<div class="para">
							4450 : "com.cloud.exception.HAStateException"
						</div>
					</td><td align="left">
						<div class="para">
							4455 : "com.cloud.exception.InsufficientAddressCapacityException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4460 : "com.cloud.exception.InsufficientCapacityException"
						</div>
					</td><td align="left">
						<div class="para">
							4465 : "com.cloud.exception.InsufficientNetworkCapacityException"
						</div>
					</td><td align="left">
						<div class="para">
							4470 : "com.cloud.exception.InsufficientServerCapacityException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4475 : "com.cloud.exception.InsufficientStorageCapacityException"
						</div>
					</td><td align="left">
						<div class="para">
							4480 : "com.cloud.exception.InsufficientVirtualNetworkCapcityException"
						</div>
					</td><td align="left">
						<div class="para">
							4485 : "com.cloud.exception.InternalErrorException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4490 : "com.cloud.exception.InvalidParameterValueException"
						</div>
					</td><td align="left">
						<div class="para">
							4495 : "com.cloud.exception.ManagementServerException"
						</div>
					</td><td align="left">
						<div class="para">
							4500 : "com.cloud.exception.NetworkRuleConflictException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4505 : "com.cloud.exception.PermissionDeniedException"
						</div>
					</td><td align="left">
						<div class="para">
							4510 : "com.cloud.exception.ResourceAllocationException"
						</div>
					</td><td align="left">
						<div class="para">
							4515 : "com.cloud.exception.ResourceInUseException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4520 : "com.cloud.exception.ResourceUnavailableException"
						</div>
					</td><td align="left">
						<div class="para">
							4525 : "com.cloud.exception.StorageUnavailableException"
						</div>
					</td><td align="left">
						<div class="para">
							4530 : "com.cloud.exception.UnsupportedServiceException"
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							4535 : "com.cloud.exception.VirtualMachineMigrationException"
						</div>
					</td><td align="left">
						<div class="para">
							9999 : "org.apache.cloudstack.api.ServerApiException"
						</div>
					</td><td align="left">
						<div class="para">
						</div>
					</td></tr></tbody></table></div></div></div></div><div xml:lang="ja-JP" class="chapter" id="api-calls" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第5章 CloudStack API の呼び出し</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#making-api-request">5.1. API リクエストを作成します。</a></span></dt><dt><span class="section"><a href="#signing-api-requests">5.2. Signing API Requests</a></span></dt><dd><dl><dt><span class="section"><a href="#signing-api-calls-python">5.2.1. How to sign an API call with Python</a></span></dt></dl></dd><dt><span class="section"><a href="#enabling-api-call-expiration">5.3. Enabling API Call Expiration</a></span></dt><dt><span class="section"><a href="#api-throttling">5.4. Limiting the Rate of API Requests</a></span></dt><dd><dl><dt><span class="section"><a href="#api-throttling-configure">5.4.1. Configuring the API Request Rate</a></span></dt><dt><span class="section"><a href="#api-throttling-limitations">5.4.2. Limitations on API Throttling</a></span></dt></dl></dd><dt><span class="section"><a href="#responses">5.5. Responses</a></span></dt><dd><dl><dt><span class="section"><a href="#response-formats">5.5.1. Response Formats: XML and JSON</a></span></dt><dt><span class="section"><a href="#max-result-page-returned">5.5.2. Maximum Result Pages Returned</a></span></dt><dt><span class="section"><a href="#error-handling">5.5.3. Error Handling</a></span></dt></dl></dd><dt><span class="section"><a href="#asynchronous-commands">5.6. Asynchronous Commands</a></span></dt><dd><dl><dt><span class="section"><a href="#job-status">5.6.1. ジョブの状態</a></span></dt><dt><span class="section"><a href="#asynchronous-commands-example">5.6.2. 例</a></span></dt></dl></dd></dl></div><div xml:lang="ja-JP" class="section" id="making-api-request" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="making-api-request">5.1. API リクエストを作成します。</h2></div></div></div><div class="para">
		All CloudStack API requests are submitted in the form of a HTTP GET/POST with an associated command and any parameters. A request is composed of the following whether in HTTP or HTTPS:
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				CloudStack API URL: This is the web services API entry point(for example, http://www.cloud.com:8080/client/api)
			</div></li><li class="listitem"><div class="para">
				Command: The web services command you wish to execute, such as start a virtual machine or create a disk volume
			</div></li><li class="listitem"><div class="para">
				Parameters: Any additional required or optional parameters for the command
			</div></li></ul></div><div class="para">
		A sample API GET request looks like the following:
	</div><pre class="programlisting">http://localhost:8080/client/api?command=deployVirtualMachine&amp;serviceOfferingId=1&amp;diskOfferingId=1&amp;templateId=2&amp;zoneId=4&amp;apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&amp;signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D
</pre><div class="para">
		Or in a more readable format:
	</div><pre class="programlisting">
1. http://localhost:8080/client/api
2. ?command=deployVirtualMachine
3. &amp;serviceOfferingId=1
4. &amp;diskOfferingId=1
5. &amp;templateId=2
6. &amp;zoneId=4
7. &amp;apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXqjB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ
8. &amp;signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D
</pre><div class="para">
		The first line is the CloudStack API URL. This is the Cloud instance you wish to interact with.
	</div><div class="para">
		The second line refers to the command you wish to execute. In our example, we are attempting to deploy a fresh new virtual machine. It is preceded by a (?) to separate itself from the CloudStack API URL.
	</div><div class="para">
		Lines 3-6 are the parameters for this given command. To see the command and its request parameters, please refer to the appropriate section in the CloudStack API documentation. Each parameter field-value pair (field=value) is preceded by an ampersand character (&amp;).
	</div><div class="para">
		Line 7 is the user API Key that uniquely identifies the account. See Signing API Requests on page 7.
	</div><div class="para">
		Line 8 is the signature hash created to authenticate the user account executing the API command. See Signing API Requests on page 7.
	</div></div><div xml:lang="ja-JP" class="section" id="signing-api-requests" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="signing-api-requests">5.2. Signing API Requests</h2></div></div></div><div class="para">
		Whether you access the CloudStack API with HTTP or HTTPS, it must still be signed so that CloudStack can verify the caller has been authenticated and authorized to execute the command. Make sure that you have both the API Key and Secret Key provided by the CloudStack administrator for your account before proceeding with the signing process.
	</div><div class="para">
		To show how to sign a request, we will re-use the previous example.
	</div><pre class="programlisting">http://http://localhost:8080/client/api?command=deployVirtualMachine&amp;serviceOfferingId=1&amp;diskOfferingId=1&amp;templateId=2&amp;zoneId=4&amp;apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&amp;signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D</pre><div class="para">
		Breaking this down, we have several distinct parts to this URL.
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				Base URL: This is the base URL to the CloudStack Management Server.
			</div><pre class="programlisting">http://localhost:8080</pre></li><li class="listitem"><div class="para">
				API Path: This is the path to the API Servlet that processes the incoming requests.
			</div><pre class="programlisting">/client/api?</pre></li><li class="listitem"><div class="para">
				Command String: This part of the query string comprises of the command, its parameters, and the API Key that identifies the account.
			</div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
					As with all query string parameters of field-value pairs, the "field" component is case insensitive while all "value" values are case sensitive.
				</div></div></div><pre class="programlisting">command=deployVirtualMachine&amp;serviceOfferingId=1&amp;diskOfferingId=1&amp;templateId=2&amp;zoneId=4&amp;apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ</pre></li><li class="listitem"><div class="para">
				Signature: This is the hashed signature of the Base URL that is generated using a combination of the user’s Secret Key and the HMAC SHA-1 hashing algorithm.
			</div><div class="para">
				&amp;signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D
			</div></li></ul></div><div class="para">
		Every API request has the format Base URL+API Path+Command String+Signature.
	</div><div class="para">
		To generate the signature.
	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
				For each field-value pair (as separated by a '&amp;') in the Command String, URL encode each value so that it can be safely sent via HTTP GET.
			</div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
					Make sure all spaces are encoded as "%20" rather than "+".
				</div></div></div></li><li class="listitem"><div class="para">
				Lower case the entire Command String and sort it alphabetically via the field for each field-value pair. The result of this step would look like the following.
			</div><pre class="programlisting">apikey=mivr6x7u6bn_sdahobpjnejpgest35exq-jb8cg20yi3yaxxcgpyuairmfi_ejtvwz0nukkjbpmy3y2bcikwfq&amp;command=deployvirtualmachine&amp;diskofferingid=1&amp;serviceofferingid=1&amp;templateid=2&amp;zoneid=4</pre></li><li class="listitem"><div class="para">
				Take the sorted Command String and run it through the HMAC SHA-1 hashing algorithm (most programming languages offer a utility method to do this) with the user’s Secret Key. Base64 encode the resulting byte array in UTF-8 so that it can be safely transmitted via HTTP. The final string produced after Base64 encoding should be "Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D".
			</div><div class="para">
				By reconstructing the final URL in the format Base URL+API Path+Command String+Signature, the final URL should look like:
			</div><pre class="programlisting">http://localhost:8080/client/api?command=deployVirtualMachine&amp;serviceOfferingId=1&amp;diskOfferingId=1&amp;templateId=2&amp;zoneId=4&amp;apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&amp;signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D</pre></li></ol></div><div xml:lang="ja-JP" class="section" id="signing-api-calls-python" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="signing-api-calls-python">5.2.1. How to sign an API call with Python</h3></div></div></div><div class="para">
		To illustrate the procedure used to sign API calls we present a step by step interactive session using Python.
	</div><div class="para">
		First import the required modules:
	</div><pre class="programlisting">

 
$python
Python 2.7.3 (default, Nov 17 2012, 19:54:34) 
[GCC 4.2.1 Compatible Apple Clang 4.1 ((tags/Apple/clang-421.11.66))] on darwin
Type "help", "copyright", "credits" or "license" for more information.
&gt;&gt;&gt; import urllib2
&gt;&gt;&gt; import urllib
&gt;&gt;&gt; import hashlib
&gt;&gt;&gt; import hmac
&gt;&gt;&gt; import base64
 
</pre><div class="para">
		Define the endpoint of the Cloud, the command that you want to execute and the keys of the user.
	</div><pre class="programlisting">
 

&gt;&gt;&gt; baseurl='http://localhost:8080/client/api?'
&gt;&gt;&gt; request={}
&gt;&gt;&gt; request['command']='listUsers'
&gt;&gt;&gt; request['response']='json'
&gt;&gt;&gt; request['apikey']='plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg'
&gt;&gt;&gt; secretkey='VDaACYb0LV9eNjTetIOElcVQkvJck_J_QljX_FcHRj87ZKiy0z0ty0ZsYBkoXkY9b7eq1EhwJaw7FF3akA3KBQ'
  
</pre><div class="para">
		Build the request string:
	</div><pre class="programlisting">
 
&gt;&gt;&gt; request_str='&amp;'.join(['='.join([k,urllib.quote_plus(request[k])]) for k in request.keys()])
&gt;&gt;&gt; request_str
'apikey=plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg&amp;command=listUsers&amp;response=json'
  
</pre><div class="para">
		Compute the signature with hmac, do a 64 bit encoding and a url encoding:
	</div><pre class="programlisting">
  
&gt;&gt;&gt; sig_str='&amp;'.join(['='.join([k.lower(),urllib.quote_plus(request[k].lower().replace('+','%20'))])for k in sorted(request.iterkeys())]) 
&gt;&gt;&gt; sig_str
'apikey=plgwjfzk4gys3momtvmjuvg-x-jlwlnfauj9gabbbf9edm-kaymmailqzzq1elzlyq_u38zcm0bewzgudp66mg&amp;command=listusers&amp;response=json'
&gt;&gt;&gt; sig=hmac.new(secretkey,sig_str,hashlib.sha1)
&gt;&gt;&gt; sig
&lt;hmac.HMAC instance at 0x10d91d680&gt;
&gt;&gt;&gt; sig=hmac.new(secretkey,sig_str,hashlib.sha1).digest()
&gt;&gt;&gt; sig
'M:]\x0e\xaf\xfb\x8f\xf2y\xf1p\x91\x1e\x89\x8a\xa1\x05\xc4A\xdb'
&gt;&gt;&gt; sig=base64.encodestring(hmac.new(secretkey,sig_str,hashlib.sha1).digest())
&gt;&gt;&gt; sig
'TTpdDq/7j/J58XCRHomKoQXEQds=\n'
&gt;&gt;&gt; sig=base64.encodestring(hmac.new(secretkey,sig_str,hashlib.sha1).digest()).strip()
&gt;&gt;&gt; sig
'TTpdDq/7j/J58XCRHomKoQXEQds='
&gt;&gt;&gt; sig=urllib.quote_plus(base64.encodestring(hmac.new(secretkey,sig_str,hashlib.sha1).digest()).strip())
  
</pre><div class="para">
		Finally, build the entire string and do an http GET:
	</div><pre class="programlisting">
  
&gt;&gt;&gt; req=baseurl+request_str+'&amp;signature='+sig
&gt;&gt;&gt; req
'http://localhost:8080/client/api?apikey=plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg&amp;command=listUsers&amp;response=json&amp;signature=TTpdDq%2F7j%2FJ58XCRHomKoQXEQds%3D'
&gt;&gt;&gt; res=urllib2.urlopen(req)
&gt;&gt;&gt; res.read()
'{ "listusersresponse" : { "count":3 ,"user" : [  {"id":"7ed6d5da-93b2-4545-a502-23d20b48ef2a","username":"admin","firstname":"admin","lastname":"cloud","created":"2012-07-05T12:18:27-0700","state":"enabled","account":"admin","accounttype":1,"domainid":"8a111e58-e155-4482-93ce-84efff3c7c77","domain":"ROOT","apikey":"plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg","secretkey":"VDaACYb0LV9eNjTetIOElcVQkvJck_J_QljX_FcHRj87ZKiy0z0ty0ZsYBkoXkY9b7eq1EhwJaw7FF3akA3KBQ","accountid":"7548ac03-af1d-4c1c-9064-2f3e2c0eda0d"}, {"id":"1fea6418-5576-4989-a21e-4790787bbee3","username":"runseb","firstname":"foobar","lastname":"goa","email":"joe@smith.com","created":"2013-04-10T16:52:06-0700","state":"enabled","account":"admin","accounttype":1,"domainid":"8a111e58-e155-4482-93ce-84efff3c7c77","domain":"ROOT","apikey":"Xhsb3MewjJQaXXMszRcLvQI9_NPy_UcbDj1QXikkVbDC9MDSPwWdtZ1bUY1H7JBEYTtDDLY3yuchCeW778GkBA","secretkey":"gIsgmi8C5YwxMHjX5o51pSe0kqs6JnKriw0jJBLceY5bgnfzKjL4aM6ctJX-i1ddQIHJLbLJDK9MRzsKk6xZ_w","accountid":"7548ac03-af1d-4c1c-9064-2f3e2c0eda0d"}, {"id":"52f65396-183c-4473-883f-a37e7bb93967","username":"toto","firstname":"john","lastname":"smith","email":"john@smith.com","created":"2013-04-23T04:27:22-0700","state":"enabled","account":"admin","accounttype":1,"domainid":"8a111e58-e155-4482-93ce-84efff3c7c77","domain":"ROOT","apikey":"THaA6fFWS_OmvU8od201omxFC8yKNL_Hc5ZCS77LFCJsRzSx48JyZucbUul6XYbEg-ZyXMl_wuEpECzK-wKnow","secretkey":"O5ywpqJorAsEBKR_5jEvrtGHfWL1Y_j1E4Z_iCr8OKCYcsPIOdVcfzjJQ8YqK0a5EzSpoRrjOFiLsG0hQrYnDA","accountid":"7548ac03-af1d-4c1c-9064-2f3e2c0eda0d"} ] } }'
  
</pre></div></div><div xml:lang="ja-JP" class="section" id="enabling-api-call-expiration" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="enabling-api-call-expiration">5.3. Enabling API Call Expiration</h2></div></div></div><div class="para">
		You can set an expiry timestamp on API calls to prevent replay attacks over non-secure channels, such as HTTP. The server tracks the expiry timestamp you have specified and rejects all the subsequent API requests that come in after this validity period.
	</div><div class="para">
		To enable this feature, add the following parameters to the API request:
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				signatureVersion=3: If the signatureVersion parameter is missing or is not equal to 3, the expires parameter is ignored in the API request.
			</div></li><li class="listitem"><div class="para">
				expires=YYYY-MM-DDThh:mm:ssZ: Specifies the date and time at which the signature included in the request is expired. The timestamp is expressed in the YYYY-MM-DDThh:mm:ssZ format, as specified in the ISO 8601 standard.
			</div></li></ul></div><div class="para">
		For example:
	</div><pre class="programlisting">expires=2011-10-10T12:00:00+0530</pre><div class="para">
		A sample API request with expiration is given below:
	</div><pre class="programlisting">http://&lt;IPAddress&gt;:8080/client/api?command=listZones&amp;signatureVersion=3&amp;expires=2011-10-10T12:00:00+0530&amp;apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&amp;signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D</pre></div><div xml:lang="ja-JP" class="section" id="api-throttling" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="api-throttling">5.4. Limiting the Rate of API Requests</h2></div></div></div><div class="para">
		You can limit the rate at which API requests can be placed for each account. This is useful to avoid malicious attacks on the Management Server, prevent performance degradation, and provide fairness to all accounts.
	</div><div class="para">
		If the number of API calls exceeds the threshold, an error message is returned for any additional API calls. The caller will have to retry these API calls at another time.
	</div><div class="section" id="api-throttling-configure"><div class="titlepage"><div><div><h3 class="title" id="api-throttling-configure">5.4.1. Configuring the API Request Rate</h3></div></div></div><div class="para">
			To control the API request rate, use the following global configuration settings:
		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
					api.throttling.enabled - Enable/Disable API throttling. By default, this setting is false, so API throttling is not enabled.
				</div></li><li class="listitem"><div class="para">
					api.throttling.interval (in seconds) - Time interval during which the number of API requests is to be counted. When the interval has passed, the API count is reset to 0.
				</div></li><li class="listitem"><div class="para">
					api.throttling.max - Maximum number of APIs that can be placed within the api.throttling.interval period.
				</div></li><li class="listitem"><div class="para">
					api.throttling.cachesize - Cache size for storing API counters. Use a value higher than the total number of accounts managed by the cloud. One cache entry is needed for each account, to store the running API total for that account.
				</div></li></ul></div></div><div class="section" id="api-throttling-limitations"><div class="titlepage"><div><div><h3 class="title" id="api-throttling-limitations">5.4.2. Limitations on API Throttling</h3></div></div></div><div class="para">
			The following limitations exist in the current implementation of this feature.
		</div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
				Even with these limitations, CloudStack is still able to effectively use API throttling to avoid malicious attacks causing denial of service.
			</div></div></div><div class="para">
		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
					In a deployment with multiple Management Servers, the cache is not synchronized across them. In this case, CloudStack might not be able to ensure that only the exact desired number of API requests are allowed. In the worst case, the number of API calls that might be allowed is (number of Management Servers) * (api.throttling.max).
				</div></li><li class="listitem"><div class="para">
					The API commands resetApiLimit and getApiLimit are limited to the Management Server where the API is invoked.
				</div></li></ul></div></div></div><div xml:lang="ja-JP" class="section" id="responses" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="responses">5.5. Responses</h2></div></div></div><div xml:lang="ja-JP" class="section" id="response-formats" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="response-formats">5.5.1. Response Formats: XML and JSON</h3></div></div></div><div class="para">
		CloudStack supports two formats as the response to an API call. The default response is XML. If you would like the response to be in JSON, add &amp;response=json to the Command String.
	</div><div class="para">
		The two response formats differ in how they handle blank fields. In JSON, if there is no value for a response field, it will not appear in the response. If all the fields were empty, there might be no response at all. In XML, even if there is no value to be returned, an empty field will be returned as a placeholder XML element.
	</div><div class="para">
		Sample XML Response:
	</div><pre class="programlisting">
     &lt;listipaddressesresponse&gt; 
        &lt;allocatedipaddress&gt;
        &lt;ipaddress&gt;192.168.10.141&lt;/ipaddress&gt; 
        &lt;allocated&gt;2009-09-18T13:16:10-0700&lt;/allocated&gt; 
        &lt;zoneid&gt;4&lt;/zoneid&gt; 
            &lt;zonename&gt;WC&lt;/zonename&gt; 
            &lt;issourcenat&gt;true&lt;/issourcenat&gt; 
        &lt;/allocatedipaddress&gt;
     &lt;/listipaddressesresponse&gt;
</pre><div class="para">
		Sample JSON Response:
	</div><pre class="programlisting">
        { "listipaddressesresponse" : 
          { "allocatedipaddress" :
            [ 
              { 
                "ipaddress" : "192.168.10.141", 
                "allocated" : "2009-09-18T13:16:10-0700",
                "zoneid" : "4", 
                "zonename" : "WC", 
                "issourcenat" : "true" 
              } 
            ]
          } 
        } 
</pre></div><div xml:lang="ja-JP" class="section" id="max-result-page-returned" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="max-result-page-returned">5.5.2. Maximum Result Pages Returned</h3></div></div></div><div class="para">
		For each cloud, there is a default upper limit on the number of results that any API command will return in a single page. This is to help prevent overloading the cloud servers and prevent DOS attacks. For example, if the page size limit is 500 and a command returns 10,000 results, the command will return 20 pages.
	</div><div class="para">
		The default page size limit can be different for each cloud. It is set in the global configuration parameter default.page.size. If your cloud has many users with lots of VMs, you might need to increase the value of this parameter. At the same time, be careful not to set it so high that your site can be taken down by an enormous return from an API call. For more information about how to set global configuration parameters, see "Describe Your Deployment" in the Installation Guide.
	</div><div class="para">
		To decrease the page size limit for an individual API command, override the global setting with the page and pagesize parameters, which are available in any list* command (listCapabilities, listDiskOfferings, etc.).
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				Both parameters must be specified together.
			</div></li><li class="listitem"><div class="para">
				The value of the pagesize parameter must be smaller than the value of default.page.size. That is, you can not increase the number of possible items in a result page, only decrease it.
			</div></li></ul></div><div class="para">
		For syntax information on the list* commands, see the API Reference.
	</div></div><div xml:lang="ja-JP" class="section" id="error-handling" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="error-handling">5.5.3. Error Handling</h3></div></div></div><div class="para">
		If an error occurs while processing an API request, the appropriate response in the format specified is returned. Each error response consists of an error code and an error text describing what possibly can go wrong. For an example error response, see page 12.
	</div><div class="para">
		An HTTP error code of 401 is always returned if API request was rejected due to bad signatures, missing API Keys, or the user simply did not have the permissions to execute the command.
	</div></div></div><div xml:lang="ja-JP" class="section" id="asynchronous-commands" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="asynchronous-commands">5.6. Asynchronous Commands</h2></div></div></div><div class="para">
		Asynchronous commands were introduced in CloudStack 2.x. Commands are designated as asynchronous when they can potentially take a long period of time to complete such as creating a snapshot or disk volume. They differ from synchronous commands by the following:
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				They are identified in the API Reference by an (A).
			</div></li><li class="listitem"><div class="para">
				They will immediately return a job ID to refer to the job that will be responsible in processing the command.
			</div></li><li class="listitem"><div class="para">
				If executed as a "create" resource command, it will return the resource ID as well as the job ID.
			</div><div class="para">
				You can periodically check the status of the job by making a simple API call to the command, queryAsyncJobResult and passing in the job ID.
			</div></li></ul></div><div xml:lang="ja-JP" class="section" id="job-status" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="job-status">5.6.1. ジョブの状態</h3></div></div></div><div class="para">
		非同期コマンドを利用する際の重要な点はコマンドを実行した際直ちに返ってくるジョブ ID です。ジョブ ID は queryAsyncJobResult コマンドを生成することで定期的にジョブの状態をチェックすることができ、3つの整数値でジョブの状態が返ってきます。
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				0 - ジョブは実行中です。続けて状態遷移を定期的にポーリングします。
			</div></li><li class="listitem"><div class="para">
				1 - ジョブは正常に完了しました。 ジョブはコマンド実行に紐づく成功値を返します。
			</div></li><li class="listitem"><div class="para">
				2 - ジョブは失敗しました。失敗した理由のコードである "jobresultcode" タグと、失敗理由を表す "jobresult" を確認してください。
			</div></li></ul></div></div><div xml:lang="ja-JP" class="section" id="asynchronous-commands-example" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="asynchronous-commands-example">5.6.2. 例</h3></div></div></div><div class="para">
		The following shows an example of using an asynchronous command. Assume the API command:
	</div><pre class="programlisting">command=deployVirtualMachine&amp;zoneId=1&amp;serviceOfferingId=1&amp;diskOfferingId=1&amp;templateId=1
</pre><div class="para">
		CloudStack will immediately return a job ID and any other additional data.
	</div><pre class="programlisting">
         &lt;deployvirtualmachineresponse&gt; 
              &lt;jobid&gt;1&lt;/jobid&gt;
             &lt;id&gt;100&lt;/id&gt;
         &lt;/deployvirtualmachineresponse&gt;
</pre><div class="para">
		Using the job ID, you can periodically poll for the results by using the queryAsyncJobResult command.
	</div><pre class="programlisting">command=queryAsyncJobResult&amp;jobId=1</pre><div class="para">
		Three possible results could come from this query.
	</div><div class="para">
		Job is still pending:
	</div><pre class="programlisting">
         &lt;queryasyncjobresult&gt; 
              &lt;jobid&gt;1&lt;/jobid&gt;
              &lt;jobstatus&gt;0&lt;/jobstatus&gt;
              &lt;jobprocstatus&gt;1&lt;/jobprocstatus&gt;
         &lt;/queryasyncjobresult&gt;
</pre><div class="para">
		Job has succeeded:
	</div><pre class="programlisting">
            &lt;queryasyncjobresultresponse cloud-stack-version="3.0.1.6"&gt;
                  &lt;jobid&gt;1&lt;/jobid&gt;
                  &lt;jobstatus&gt;1&lt;/jobstatus&gt;
                  &lt;jobprocstatus&gt;0&lt;/jobprocstatus&gt;
                 &lt;jobresultcode&gt;0&lt;/jobresultcode&gt;
                  &lt;jobresulttype&gt;object&lt;/jobresulttype&gt;
                  &lt;jobresult&gt;
                    &lt;virtualmachine&gt;
                    &lt;id&gt;450&lt;/id&gt;
                    &lt;name&gt;i-2-450-VM&lt;/name&gt;
                    &lt;displayname&gt;i-2-450-VM&lt;/displayname&gt;
                    &lt;account&gt;admin&lt;/account&gt;
                    &lt;domainid&gt;1&lt;/domainid&gt;
                    &lt;domain&gt;ROOT&lt;/domain&gt;
                    &lt;created&gt;2011-03-10T18:20:25-0800&lt;/created&gt;
                    &lt;state&gt;Running&lt;/state&gt;
                    &lt;haenable&gt;false&lt;/haenable&gt;
                    &lt;zoneid&gt;1&lt;/zoneid&gt;
                    &lt;zonename&gt;San Jose 1&lt;/zonename&gt;
                    &lt;hostid&gt;2&lt;/hostid&gt;
                    &lt;hostname&gt;905-13.sjc.lab.vmops.com&lt;/hostname&gt;
                    &lt;templateid&gt;1&lt;/templateid&gt;
                    &lt;templatename&gt;CentOS 5.3 64bit LAMP&lt;/templatename&gt;
                    &lt;templatedisplaytext&gt;CentOS 5.3 64bit LAMP&lt;/templatedisplaytext&gt;
                    &lt;passwordenabled&gt;false&lt;/passwordenabled&gt;
                    &lt;serviceofferingid&gt;1&lt;/serviceofferingid&gt;
                    &lt;serviceofferingname&gt;Small Instance&lt;/serviceofferingname&gt;
                    &lt;cpunumber&gt;1&lt;/cpunumber&gt;
                    &lt;cpuspeed&gt;500&lt;/cpuspeed&gt;
                    &lt;memory&gt;512&lt;/memory&gt;
                    &lt;guestosid&gt;12&lt;/guestosid&gt;
                    &lt;rootdeviceid&gt;0&lt;/rootdeviceid&gt;
                    &lt;rootdevicetype&gt;NetworkFilesystem&lt;/rootdevicetype&gt;
                    &lt;nic&gt;
                      &lt;id&gt;561&lt;/id&gt;
                      &lt;networkid&gt;205&lt;/networkid&gt;
                      &lt;netmask&gt;255.255.255.0&lt;/netmask&gt;
                      &lt;gateway&gt;10.1.1.1&lt;/gateway&gt;
                      &lt;ipaddress&gt;10.1.1.225&lt;/ipaddress&gt;
                      &lt;isolationuri&gt;vlan://295&lt;/isolationuri&gt;
                      &lt;broadcasturi&gt;vlan://295&lt;/broadcasturi&gt;
                      &lt;traffictype&gt;Guest&lt;/traffictype&gt;
                      &lt;type&gt;Virtual&lt;/type&gt;
                      &lt;isdefault&gt;true&lt;/isdefault&gt;
                    &lt;/nic&gt;
                    &lt;hypervisor&gt;XenServer&lt;/hypervisor&gt;
                   &lt;/virtualmachine&gt;
                 &lt;/jobresult&gt;
            &lt;/queryasyncjobresultresponse&gt;
</pre><div class="para">
		Job has failed:
	</div><pre class="programlisting">
            &lt;queryasyncjobresult&gt;
                  &lt;jobid&gt;1&lt;/jobid&gt; 
                  &lt;jobstatus&gt;2&lt;/jobstatus&gt; 
                  &lt;jobprocstatus&gt;0&lt;/jobprocstatus&gt;
                  &lt;jobresultcode&gt;551&lt;/jobresultcode&gt;
                  &lt;jobresulttype&gt;text&lt;/jobresulttype&gt;
                  &lt;jobresult&gt;Unable to deploy virtual machine id = 100 due to not enough capacity&lt;/jobresult&gt; 
            &lt;/queryasyncjobresult&gt;
</pre></div></div></div><div xml:lang="ja-JP" class="chapter" id="working-with-usage-data" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第6章 Working With Usage Data</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#usage-record-format">6.1. Usage Record Format</a></span></dt><dd><dl><dt><span class="section"><a href="#virtual-machine-usage-record-format">6.1.1. Virtual Machine Usage Record Format</a></span></dt><dt><span class="section"><a href="#network-usage-record-format">6.1.2. Network Usage Record Format</a></span></dt><dt><span class="section"><a href="#ipaddress-usage-record-format">6.1.3. IP Address Usage Record Format</a></span></dt><dt><span class="section"><a href="#disk-volume-usage-record-format">6.1.4. Disk Volume Usage Record Format</a></span></dt><dt><span class="section"><a href="#template-iso-snapshot-usage-record-format">6.1.5. Template, ISO, and Snapshot Usage Record Format</a></span></dt><dt><span class="section"><a href="#loadbalancer-policy-port-forwarding-rule-usage-record-format">6.1.6. Load Balancer Policy or Port Forwarding Rule Usage Record Format</a></span></dt><dt><span class="section"><a href="#network-offering-usage-record-format">6.1.7. Network Offering Usage Record Format</a></span></dt><dt><span class="section"><a href="#VPN-user-usage-record-format">6.1.8. VPN User Usage Record Format</a></span></dt></dl></dd><dt><span class="section"><a href="#usage-types">6.2. 使用状況データの種類</a></span></dt><dt><span class="section"><a href="#example-response-from-listUsageRecords">6.3. Example response from listUsageRecords</a></span></dt><dt><span class="section"><a href="#dates-in-usage-record">6.4. Dates in the Usage Record</a></span></dt><dt><span class="section"><a href="#globally-configured-limits">6.5. Globally Configured Limits</a></span></dt></dl></div><div class="para">
		The Usage Server provides aggregated usage records which you can use to create billing integration for the CloudStack platform. The Usage Server works by taking data from the events log and creating summary usage records that you can access using the listUsageRecords API call.
	</div><div class="para">
		The usage records show the amount of resources, such as VM run time or template storage space, consumed by guest instances. In the special case of bare metal instances, no template storage resources are consumed, but records showing zero usage are still included in the Usage Server's output.
	</div><div class="para">
		The Usage Server runs at least once per day. It can be configured to run multiple times per day. Its behavior is controlled by configuration settings as described in the CloudStack Administration Guide.
	</div><div xml:lang="ja-JP" class="section" id="usage-record-format" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="usage-record-format">6.1. Usage Record Format</h2></div></div></div><div xml:lang="ja-JP" class="section" id="virtual-machine-usage-record-format" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="virtual-machine-usage-record-format">6.1.1. Virtual Machine Usage Record Format</h3></div></div></div><div class="para">
		For running and allocated virtual machine usage, the following fields exist in a usage record:
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				account – name of the account
			</div></li><li class="listitem"><div class="para">
				accountid – ID of the account
			</div></li><li class="listitem"><div class="para">
				domainid – ID of the domain in which this account resides
			</div></li><li class="listitem"><div class="para">
				zoneid – Zone where the usage occurred
			</div></li><li class="listitem"><div class="para">
				description – A string describing what the usage record is tracking
			</div></li><li class="listitem"><div class="para">
				usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for VM running time)
			</div></li><li class="listitem"><div class="para">
				usagetype – A number representing the usage type (see Usage Types)
			</div></li><li class="listitem"><div class="para">
				rawusage – A number representing the actual usage in hours
			</div></li><li class="listitem"><div class="para">
				virtualMachineId – The ID of the virtual machine
			</div></li><li class="listitem"><div class="para">
				name – The name of the virtual machine
			</div></li><li class="listitem"><div class="para">
				offeringid – The ID of the service offering
			</div></li><li class="listitem"><div class="para">
				templateid – The ID of the template or the ID of the parent template. The parent template value is present when the current template was created from a volume.
			</div></li><li class="listitem"><div class="para">
				usageid – Virtual machine
			</div></li><li class="listitem"><div class="para">
				type – Hypervisor
			</div></li><li class="listitem"><div class="para">
				startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record
			</div></li></ul></div></div><div xml:lang="ja-JP" class="section" id="network-usage-record-format" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="network-usage-record-format">6.1.2. Network Usage Record Format</h3></div></div></div><div class="para">
		For network usage (bytes sent/received), the following fields exist in a usage record.
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				account – name of the account
			</div></li><li class="listitem"><div class="para">
				accountid – ID of the account
			</div></li><li class="listitem"><div class="para">
				domainid – ID of the domain in which this account resides
			</div></li><li class="listitem"><div class="para">
				zoneid – Zone where the usage occurred
			</div></li><li class="listitem"><div class="para">
				description – A string describing what the usage record is tracking
			</div></li><li class="listitem"><div class="para">
				usagetype – A number representing the usage type (see Usage Types)
			</div></li><li class="listitem"><div class="para">
				rawusage – A number representing the actual usage in hours
			</div></li><li class="listitem"><div class="para">
				usageid – Device ID (virtual router ID or external device ID)
			</div></li><li class="listitem"><div class="para">
				type – Device type (domain router, external load balancer, etc.)
			</div></li><li class="listitem"><div class="para">
				startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record
			</div></li></ul></div></div><div xml:lang="ja-JP" class="section" id="ipaddress-usage-record-format" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="ipaddress-usage-record-format">6.1.3. IP Address Usage Record Format</h3></div></div></div><div class="para">
		For IP address usage the following fields exist in a usage record.
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				account - name of the account
			</div></li><li class="listitem"><div class="para">
				accountid - ID of the account
			</div></li><li class="listitem"><div class="para">
				domainid - ID of the domain in which this account resides
			</div></li><li class="listitem"><div class="para">
				zoneid - Zone where the usage occurred
			</div></li><li class="listitem"><div class="para">
				description - A string describing what the usage record is tracking
			</div></li><li class="listitem"><div class="para">
				usage - String representation of the usage, including the units of usage
			</div></li><li class="listitem"><div class="para">
				usagetype - A number representing the usage type (see Usage Types)
			</div></li><li class="listitem"><div class="para">
				rawusage - A number representing the actual usage in hours
			</div></li><li class="listitem"><div class="para">
				usageid - IP address ID
			</div></li><li class="listitem"><div class="para">
				startdate, enddate - The range of time for which the usage is aggregated; see Dates in the Usage Record
			</div></li><li class="listitem"><div class="para">
				issourcenat - Whether source NAT is enabled for the IP address
			</div></li><li class="listitem"><div class="para">
				iselastic - True if the IP address is elastic.
			</div></li></ul></div></div><div xml:lang="ja-JP" class="section" id="disk-volume-usage-record-format" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="disk-volume-usage-record-format">6.1.4. Disk Volume Usage Record Format</h3></div></div></div><div class="para">
		For disk volumes, the following fields exist in a usage record.
	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				account – name of the account
			</div></li><li class="listitem"><div class="para">
				accountid – ID of the account
			</div></li><li class="listitem"><div class="para">
				domainid – ID of the domain in which this account resides
			</div></li><li class="listitem"><div class="para">
				zoneid – Zone where the usage occurred
			</div></li><li class="listitem"><div class="para">
				description – A string describing what the usage record is tracking
			</div></li><li class="listitem"><div class="para">
				usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for hours)
			</div></li><li class="listitem"><div class="para">
				usagetype – A number representing the usage type (see Usage Types)
			</div></li><li class="listitem"><div class="para">
				rawusage – A number representing the actual usage in hours
			</div></li><li class="listitem"><div class="para">
				usageid – The volume ID
			</div></li><li class="listitem"><div class="para">
				offeringid – The ID of the disk offering
			</div></li><li class="listitem"><div class="para">
				type – Hypervisor
			</div></li><li class="listitem"><div class="para">
				templateid – ROOT template ID
			</div></li><li class="listitem"><div class="para">
				size – The amount of storage allocated
			</div></li><li class="listitem"><div class="para">
				startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record
			</div></li></ul></div></div><div xml:lang="ja-JP" class="section" id="template-iso-snapshot-usage-record-format" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="template-iso-snapshot-usage-record-format">6.1.5. Template, ISO, and Snapshot Usage Record Format</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				account – name of the account
			</div></li><li class="listitem"><div class="para">
				accountid – ID of the account
			</div></li><li class="listitem"><div class="para">
				domainid – ID of the domain in which this account resides
			</div></li><li class="listitem"><div class="para">
				zoneid – Zone where the usage occurred
			</div></li><li class="listitem"><div class="para">
				description – A string describing what the usage record is tracking
			</div></li><li class="listitem"><div class="para">
				usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for hours)
			</div></li><li class="listitem"><div class="para">
				usagetype – A number representing the usage type (see Usage Types)
			</div></li><li class="listitem"><div class="para">
				rawusage – A number representing the actual usage in hours
			</div></li><li class="listitem"><div class="para">
				usageid – The ID of the the template, ISO, or snapshot
			</div></li><li class="listitem"><div class="para">
				offeringid – The ID of the disk offering
			</div></li><li class="listitem"><div class="para">
				templateid – – Included only for templates (usage type 7). Source template ID.
			</div></li><li class="listitem"><div class="para">
				size – Size of the template, ISO, or snapshot
			</div></li><li class="listitem"><div class="para">
				startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record
			</div></li></ul></div></div><div xml:lang="ja-JP" class="section" id="loadbalancer-policy-port-forwarding-rule-usage-record-format" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="loadbalancer-policy-port-forwarding-rule-usage-record-format">6.1.6. Load Balancer Policy or Port Forwarding Rule Usage Record Format</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				account - name of the account
			</div></li><li class="listitem"><div class="para">
				accountid - ID of the account
			</div></li><li class="listitem"><div class="para">
				domainid - ID of the domain in which this account resides
			</div></li><li class="listitem"><div class="para">
				zoneid - Zone where the usage occurred
			</div></li><li class="listitem"><div class="para">
				description - A string describing what the usage record is tracking
			</div></li><li class="listitem"><div class="para">
				usage - String representation of the usage, including the units of usage (e.g. 'Hrs' for hours)
			</div></li><li class="listitem"><div class="para">
				usagetype - A number representing the usage type (see Usage Types)
			</div></li><li class="listitem"><div class="para">
				rawusage - A number representing the actual usage in hours
			</div></li><li class="listitem"><div class="para">
				usageid - ID of the load balancer policy or port forwarding rule
			</div></li><li class="listitem"><div class="para">
				usagetype - A number representing the usage type (see Usage Types)
			</div></li><li class="listitem"><div class="para">
				startdate, enddate - The range of time for which the usage is aggregated; see Dates in the Usage Record
			</div></li></ul></div></div><div xml:lang="ja-JP" class="section" id="network-offering-usage-record-format" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="network-offering-usage-record-format">6.1.7. Network Offering Usage Record Format</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				account – name of the account
			</div></li><li class="listitem"><div class="para">
				accountid – ID of the account
			</div></li><li class="listitem"><div class="para">
				domainid – ID of the domain in which this account resides
			</div></li><li class="listitem"><div class="para">
				zoneid – Zone where the usage occurred
			</div></li><li class="listitem"><div class="para">
				description – A string describing what the usage record is tracking
			</div></li><li class="listitem"><div class="para">
				usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for hours)
			</div></li><li class="listitem"><div class="para">
				usagetype – A number representing the usage type (see Usage Types)
			</div></li><li class="listitem"><div class="para">
				rawusage – A number representing the actual usage in hours
			</div></li><li class="listitem"><div class="para">
				usageid – ID of the network offering
			</div></li><li class="listitem"><div class="para">
				usagetype – A number representing the usage type (see Usage Types)
			</div></li><li class="listitem"><div class="para">
				offeringid – Network offering ID
			</div></li><li class="listitem"><div class="para">
				virtualMachineId – The ID of the virtual machine
			</div></li><li class="listitem"><div class="para">
				virtualMachineId – The ID of the virtual machine
			</div></li><li class="listitem"><div class="para">
				startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record
			</div></li></ul></div></div><div xml:lang="ja-JP" class="section" id="VPN-user-usage-record-format" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="VPN-user-usage-record-format">6.1.8. VPN User Usage Record Format</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
				account – name of the account
			</div></li><li class="listitem"><div class="para">
				accountid – ID of the account
			</div></li><li class="listitem"><div class="para">
				domainid – ID of the domain in which this account resides
			</div></li><li class="listitem"><div class="para">
				zoneid – Zone where the usage occurred
			</div></li><li class="listitem"><div class="para">
				description – A string describing what the usage record is tracking
			</div></li><li class="listitem"><div class="para">
				usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for hours)
			</div></li><li class="listitem"><div class="para">
				usagetype – A number representing the usage type (see Usage Types)
			</div></li><li class="listitem"><div class="para">
				rawusage – A number representing the actual usage in hours
			</div></li><li class="listitem"><div class="para">
				usageid – VPN user ID
			</div></li><li class="listitem"><div class="para">
				usagetype – A number representing the usage type (see Usage Types)
			</div></li><li class="listitem"><div class="para">
				startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record
			</div></li></ul></div></div></div><div xml:lang="ja-JP" class="section" id="usage-types" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="usage-types">6.2. 使用状況データの種類</h2></div></div></div><div class="para">
		次の表は使用状況データの種類を表しています。
	</div><div class="informaltable"><table border="1"><colgroup><col width="4cm" class="c1" /><col width="8cm" class="c2" /><col width="5cm" class="c3" /></colgroup><thead><tr><th>
						Type ID
					</th><th>
						Type Name
					</th><th>
						説明
					</th></tr></thead><tbody><tr><td>
						1
					</td><td>
						RUNNING_VM
					</td><td>
						使用状況レコードの期間における仮想マシンの総稼働時間を追跡します。もし期間中に仮想マシンがアップグレードされた場合は、新しいアップグレードされた仮想マシンに対し別の使用状況レコードを取得します。
					</td></tr><tr><td>
						<div class="para">
							2
						</div>
					</td><td>
						<div class="para">
							ALLOCATED_VM
						</div>
					</td><td>
						<div class="para">
							仮想マシンが作成されてから削除されるまでの総時間を追跡します。この使用状況タイプは Windows ベースのテンプレートのような特定テンプレートの使用状況を確認するのに役立ちます。
						</div>
					</td></tr><tr><td>
						<div class="para">
							3
						</div>
					</td><td>
						<div class="para">
							IP_ADDRESS
						</div>
					</td><td>
						<div class="para">
							アカウントが所有するパブリック IP を追跡します
						</div>
					</td></tr><tr><td>
						<div class="para">
							4
						</div>
					</td><td>
						<div class="para">
							NETWORK_BYTES_SENT
						</div>
					</td><td>
						<div class="para">
							アカウントが所有している全ての仮想マシンから送信したデータの総バイト数を追跡します。Cloud.com は 現在仮想マシン毎のネットワークトラフィックは追跡しません。
						</div>
					</td></tr><tr><td>
						<div class="para">
							5
						</div>
					</td><td>
						<div class="para">
							NETWORK_BYTES_RECEIVED
						</div>
					</td><td>
						<div class="para">
							アカウントが所有している全ての仮想マシンで受信したデータの総バイト数を追跡します。Cloud.com は 現在仮想マシン毎のネットワークトラフィックは追跡しません。
						</div>
					</td></tr><tr><td>
						<div class="para">
							6
						</div>
					</td><td>
						<div class="para">
							VOLUME
						</div>
					</td><td>
						<div class="para">
							ディスクボリュームが作成されてから削除されるまでの総時間を追跡します。
						</div>
					</td></tr><tr><td>
						<div class="para">
							7
						</div>
					</td><td>
						<div class="para">
							TEMPLATE
						</div>
					</td><td>
						<div class="para">
							テンプレート(スナップショットから作成もしくはクラウド上にアップロードされたもの)が作成されてから削除されるまでの総時間を追跡します。また、テンプレートのサイズも返されます。
						</div>
					</td></tr><tr><td>
						<div class="para">
							8
						</div>
					</td><td>
						<div class="para">
							ISO
						</div>
					</td><td>
						<div class="para">
							ISO がアップロードされてから削除されるまでの総時間を追跡します。また、ISO のサイズも返されます。
						</div>
					</td></tr><tr><td>
						<div class="para">
							9
						</div>
					</td><td>
						<div class="para">
							SNAPSHOT
						</div>
					</td><td>
						<div class="para">
							スナップショットが作成されてから削除されるまでの総時間を追跡します。
						</div>
					</td></tr><tr><td>
						<div class="para">
							11
						</div>
					</td><td>
						<div class="para">
							LOAD_BALANCER_POLICY
						</div>
					</td><td>
						<div class="para">
							負荷分散ポリシーが作成されてから削除されるまでの総時間を追跡します。Cloud.com は規則がいつ仮想マシンに割り当てられたかまでは追跡しません。
						</div>
					</td></tr><tr><td>
						<div class="para">
							12
						</div>
					</td><td>
						<div class="para">
							PORT_FORWARDING_RULE
						</div>
					</td><td>
						<div class="para">
							ポートフォワーディング規則が作成されてから削除されるまでの総時間を追跡します。
						</div>
					</td></tr><tr><td>
						<div class="para">
							13
						</div>
					</td><td>
						<div class="para">
							NETWORK_OFFERING
						</div>
					</td><td>
						<div class="para">
							ネットワークオファリングが仮想マシンに割り当てられてから削除されるまでの時間を追跡します。
						</div>
					</td></tr><tr><td>
						<div class="para">
							14
						</div>
					</td><td>
						<div class="para">
							VPN_USERS
						</div>
					</td><td>
						<div class="para">
							VPN ユーザーが作成されてから削除されるまでの時間を追跡します。
						</div>
					</td></tr></tbody></table></div></div><div xml:lang="ja-JP" class="section" id="example-response-from-listUsageRecords" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="example-response-from-listUsageRecords">6.3. Example response from listUsageRecords</h2></div></div></div><div class="para">
		All CloudStack API requests are submitted in the form of a HTTP GET/POST with an associated command and any parameters. A request is composed of the following whether in HTTP or HTTPS:
	</div><pre class="programlisting">
            &lt;listusagerecordsresponse&gt;
                  &lt;count&gt;1816&lt;/count&gt;
                 &lt;usagerecord&gt;
                    &lt;account&gt;user5&lt;/account&gt;
                    &lt;accountid&gt;10004&lt;/accountid&gt;
                    &lt;domainid&gt;1&lt;/domainid&gt;
                    &lt;zoneid&gt;1&lt;/zoneid&gt;
                        &lt;description&gt;i-3-4-WC running time (ServiceOffering: 1) (Template: 3)&lt;/description&gt;
                    &lt;usage&gt;2.95288 Hrs&lt;/usage&gt;
                       &lt;usagetype&gt;1&lt;/usagetype&gt;
                    &lt;rawusage&gt;2.95288&lt;/rawusage&gt;
                       &lt;virtualmachineid&gt;4&lt;/virtualmachineid&gt;
                    &lt;name&gt;i-3-4-WC&lt;/name&gt;
                       &lt;offeringid&gt;1&lt;/offeringid&gt;
                    &lt;templateid&gt;3&lt;/templateid&gt;
                    &lt;usageid&gt;245554&lt;/usageid&gt;
                    &lt;type&gt;XenServer&lt;/type&gt;
                    &lt;startdate&gt;2009-09-15T00:00:00-0700&lt;/startdate&gt;
                    &lt;enddate&gt;2009-09-18T16:14:26-0700&lt;/enddate&gt;
                  &lt;/usagerecord&gt;

               … (1,815 more usage records)
            &lt;/listusagerecordsresponse&gt;
</pre></div><div xml:lang="ja-JP" class="section" id="dates-in-usage-record" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="dates-in-usage-record">6.4. Dates in the Usage Record</h2></div></div></div><div class="para">
		Usage records include a start date and an end date. These dates define the period of time for which the raw usage number was calculated. If daily aggregation is used, the start date is midnight on the day in question and the end date is 23:59:59 on the day in question (with one exception; see below). A virtual machine could have been deployed at noon on that day, stopped at 6pm on that day, then started up again at 11pm. When usage is calculated on that day, there will be 7 hours of running VM usage (usage type 1) and 12 hours of allocated VM usage (usage type 2). If the same virtual machine runs for the entire next day, there will 24 hours of both running VM usage (type 1) and allocated VM usage (type 2).
	</div><div class="para">
		Note: The start date is not the time a virtual machine was started, and the end date is not the time when a virtual machine was stopped. The start and end dates give the time range within which usage was calculated.
	</div><div class="para">
		For network usage, the start date and end date again define the range in which the number of bytes transferred was calculated. If a user downloads 10 MB and uploads 1 MB in one day, there will be two records, one showing the 10 megabytes received and one showing the 1 megabyte sent.
	</div><div class="para">
		There is one case where the start date and end date do not correspond to midnight and 11:59:59pm when daily aggregation is used. This occurs only for network usage records. When the usage server has more than one day's worth of unprocessed data, the old data will be included in the aggregation period. The start date in the usage record will show the date and time of the earliest event. For other types of usage, such as IP addresses and VMs, the old unprocessed data is not included in daily aggregation.
	</div></div><div xml:lang="ja-JP" class="section" id="globally-configured-limits" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="globally-configured-limits">6.5. Globally Configured Limits</h2></div></div></div><div class="para">
		In a zone, the guest virtual network has a 24 bit CIDR by default. This limits the guest virtual network to 254 running instances. It can be adjusted as needed, but this must be done before any instances are created in the zone. For example, 10.1.1.0/22 would provide for ~1000 addresses.
	</div><div class="para">
		The following table lists limits set in the Global Configuration:
	</div><div class="informaltable"><table border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th>
						<div class="para">
							Parameter Name
						</div>
					</th><th>
						<div class="para">
							Definition
						</div>
					</th></tr></thead><tbody><tr><td>
						<div class="para">
							max.account.public.ips
						</div>
					</td><td>
						<div class="para">
							Number of public IP addresses that can be owned by an account
						</div>
					</td></tr><tr><td>
						<div class="para">
							max.account.snapshots
						</div>
					</td><td>
						<div class="para">
							Number of snapshots that can exist for an account
						</div>
					</td></tr><tr><td>
						<div class="para">
							max.account.templates
						</div>
					</td><td>
						<div class="para">
							Number of templates that can exist for an account
						</div>
					</td></tr><tr><td>
						<div class="para">
							max.account.user.vms
						</div>
					</td><td>
						<div class="para">
							Number of virtual machine instances that can exist for an account
						</div>
					</td></tr><tr><td>
						<div class="para">
							max.account.volumes
						</div>
					</td><td>
						<div class="para">
							Number of disk volumes that can exist for an account
						</div>
					</td></tr><tr><td>
						<div class="para">
							max.template.iso.size
						</div>
					</td><td>
						<div class="para">
							Maximum size for a downloaded template or ISO in GB
						</div>
					</td></tr><tr><td>
						<div class="para">
							max.volume.size.gb
						</div>
					</td><td>
						<div class="para">
							Maximum size for a volume in GB
						</div>
					</td></tr><tr><td>
						<div class="para">
							network.throttling.rate
						</div>
					</td><td>
						<div class="para">
							Default data transfer rate in megabits per second allowed per user (supported on XenServer)
						</div>
					</td></tr><tr><td>
						<div class="para">
							snapshot.max.hourly
						</div>
					</td><td>
						<div class="para">
							Maximum recurring hourly snapshots to be retained for a volume. If the limit is reached, early snapshots from the start of the hour are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring hourly snapshots can not be scheduled
						</div>
					</td></tr><tr><td>
						<div class="para">
							snapshot.max.daily
						</div>
					</td><td>
						<div class="para">
							Maximum recurring daily snapshots to be retained for a volume. If the limit is reached, snapshots from the start of the day are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring daily snapshots can not be scheduled
						</div>
					</td></tr><tr><td>
						<div class="para">
							snapshot.max.weekly
						</div>
					</td><td>
						<div class="para">
							Maximum recurring weekly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the week are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring weekly snapshots can not be scheduled
						</div>
					</td></tr><tr><td>
						<div class="para">
							snapshot.max.monthly
						</div>
					</td><td>
						<div class="para">
							Maximum recurring monthly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the month are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring monthly snapshots can not be scheduled.
						</div>
					</td></tr></tbody></table></div><div class="para">
		To modify global configuration parameters, use the global configuration screen in the CloudStack UI. See Setting Global Configuration Parameters
	</div></div></div><div xml:lang="ja-JP" class="chapter" id="working-with-documentation" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第7章 Preparing and Building CloudStack Documentation</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#installing-publican">7.1. Installing Publican</a></span></dt><dt><span class="section"><a href="#building-documentation">7.2. Building CloudStack Documentation</a></span></dt><dt><span class="section"><a href="#writing-new-documentation">7.3. Writing CloudStack Documentation</a></span></dt><dt><span class="section"><a href="#building-translation">7.4. Translating CloudStack Documentation</a></span></dt><dd><dl><dt><span class="section"><a href="#translating-documentation">7.4.1. Translating CloudStack Documentation</a></span></dt></dl></dd></dl></div><div class="para">
		This chapter describes how to install publican, how to write new documentation and build a guide as well as how to build a translated version of the documentation using transifex
	</div><div xml:lang="ja-JP" class="section" id="installing-publican" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="installing-publican">7.1. Installing Publican</h2></div></div></div><div class="para">
		CloudStack documentation is built using publican. This section describes how to install publican on your own machine so that you can build the documentation guides.
	</div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
			The CloudStack documentation source code is located under <span class="emphasis"><em>/docs</em></span>
		</div><div class="para">
			Publican documentation itself is also very <a href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/Users_Guide/chap-Users_Guide-Installing_Publican.html">useful</a>.
		</div></div></div><div class="para">
		On RHEL and RHEL derivatives, install publican with the following command:
	</div><pre class="programlisting">yum install publican publican-doc</pre><div class="para">
		On Ubuntu, install publican with the following command:
	</div><pre class="programlisting">apt-get install publican publican-doc</pre><div class="para">
		For other distribution refer to the publican documentation listed above. For latest versions of OSX you may have to install from <a href="https://fedorahosted.org/publican/wiki/Installing_OSX">source</a> and tweak it to your own setup.
	</div><div class="para">
		Once publican is installed, you need to setup the so-called CloudStack brand defined in the <span class="emphasis"><em>docs/publican-CloudStack</em></span> directory.
	</div><div class="para">
		To do so, enter the following commands:
	</div><pre class="programlisting">
        sudo cp -R publican-cloudstack /usr/share/publican/Common_Content/cloudstack
</pre><div class="para">
		If this fails or you later face errors related to the brand files, see the publican <a href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/Users_Guide/chap-Users_Guide-Branding.html#sect-Users_Guide-Installing_a_brand">documentation</a>.
	</div><div class="para">
		With publican installed and the CloudStack brand files in place, you should be able to build any documentation guide.
	</div></div><div xml:lang="ja-JP" class="section" id="building-documentation" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="building-documentation">7.2. Building CloudStack Documentation</h2></div></div></div><div class="para">
		To build a specific guide, go to the source tree of the documentation in /docs and identify the guide you want to build.
	</div><div class="para">
		Currently there are four guides plus the release notes, all defined in publican configuration files:
	</div><pre class="programlisting">
        publican-adminguide.cfg
        publican-devguide.cfg
        publican-installation.cfg
        publican-plugin-niciranvp.cfg
        publican-release-notes.cfg
</pre><div class="para">
		To build the Developer guide for example, do the following:
	</div><pre class="programlisting">publican build --config=publican-devguide.cfg --formats=pdf --langs=en-US</pre><div class="para">
		A pdf file will be created in tmp/en-US/pdf, you may choose to build the guide in a different format like html. In that case just replace the format value.
	</div></div><div xml:lang="ja-JP" class="section" id="writing-new-documentation" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="writing-new-documentation">7.3. Writing CloudStack Documentation</h2></div></div></div><div class="para">
		CloudStack documentation is written in DocBook xml format. Each guide defined with a publican configuration file refers to a DocBook <span class="emphasis"><em>book</em></span>.
	</div><div class="para">
		These books are defined in xml files in docs/en-US, for instance if we look at the Developers guide, its configuration file contains:
	</div><pre class="programlisting">
        xml_lang: en-US
        type: Book
        docname: Developers_Guide
        brand: cloudstack
        chunk_first: 1
        chunk_section_depth: 1
</pre><div class="para">
		The <span class="emphasis"><em>docname</em></span> key gives you the basename of the DocBook file located in the en-US directory that contains the description of the book.
	</div><div class="para">
		Looking closely at Developers_Guide.xml we see that it contains <span class="emphasis"><em>book</em></span> tags and several references to other xml files. These are the chapters of the book, currently they are:
	</div><pre class="programlisting">
    
        &lt;xi:include href="concepts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
        &lt;xi:include href="building-with-maven.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
        &lt;xi:include href="developer-introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
        &lt;xi:include href="whats-new.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
        &lt;xi:include href="api-calls.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
        &lt;xi:include href="working-with-usage-data.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
        &lt;xi:include href="working-with-documentation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
        &lt;xi:include href="tools.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
        &lt;xi:include href="event-types.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
        &lt;xi:include href="alerts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
        &lt;xi:include href="time-zones.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
        &lt;xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
    
</pre><div class="para">
		All these xml files are written in DocBook format.
	</div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
			DocBook format is well <a href="http://www.docbook.org/tdg5/en/html/docbook.html">documented</a>, refer to the documentation for any questions about DocBook tags
		</div></div></div><div class="para">
		When writing documentation, you therefore need to located the book,chapter and section of the content you want to write/correct. Or create a new book,chapter,section.
	</div><div class="para">
		You will then learn much more about DocBook tagging. In order to write this chapter about documentation, I added the <span class="emphasis"><em>working-with-documentation.xml</em></span>file describing a chapter in the Developer book and I created several sections within that chapter like so:
	</div><pre class="programlisting">
    
        &lt;chapter id="working-with-documentation"&gt;
            &lt;title&gt;Preparing and Building CloudStack Documentation&lt;/title&gt;
            &lt;para&gt;This chapter describes how to install publican, how to write new documentation and build a guide as well as how to build a translated version of the documentation using transifex&lt;/para&gt;
            &lt;xi:include href="installing-publican.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
            &lt;xi:include href="building-documentation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
            &lt;xi:include href="writing-new-documentation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
            &lt;xi:include href="building-translation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /&gt;
        &lt;/chapter&gt;
    
</pre><div class="para">
		Note the id witin the chapter tag, it represents the basename of the xml file describing the chapter.
	</div><div class="para">
		For translation purposes it is important that this basename be less than 50 characters long.
	</div><div class="para">
		This chapter also refers to xml files which contains each section. While you could embed the sections directly in the chapter file and as a matter of fact also write the chapters within a single book file. Breaking things up in smaller files at the granularity of the section, allows us to re-use any section to build different books.
	</div><div class="para">
		For completeness here is an example of a section:
	</div><pre class="programlisting">
    
        &lt;section id="building-documentation"&gt;
            &lt;title&gt;Building CloudStack Documentation&lt;/title&gt;
            &lt;para&gt;To build a specific guide, go to the source tree of the documentation in /docs and identify the guide you want to build.&lt;/para&gt;
            &lt;para&gt;Currently there are four guides plus the release notes, all defined in publican configuration files:&lt;/para&gt;
            &lt;programlisting&gt;
               publican-adminguide.cfg
               publican-devguide.cfg
               publican-installation.cfg
               publican-plugin-niciranvp.cfg
               publican-release-notes.cfg
            &lt;/programlisting&gt;
            &lt;para&gt;To build the Developer guide for example, do the following:&lt;/para&gt;
            &lt;programlisting&gt;publican build --config=publican-devguide.cfg --formats=pdf --langs=en-US&lt;/programlisting&gt;
            &lt;para&gt;A pdf file will be created in tmp/en-US/pdf, you may choose to build the guide in a different format like html. In that case just replace the format value.&lt;/para&gt;
        &lt;/section&gt;
    
</pre><div class="para">
		Happy Publicating and DocBooking.
	</div></div><div xml:lang="ja-JP" class="section" id="building-translation" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="building-translation">7.4. Translating CloudStack Documentation</h2></div></div></div><div class="para">
		Now that you know how to build the documentation with Publican, let's move on to building it in different languages. Publican helps us build the documentation in various languages by using Portable Object Template (POT) files and Portable Objects (PO) files for each language.
	</div><div class="para">
		The POT files are generated by parsing all the DocBook files in the language of origin, en-US for us, and creating a long list of strings for each file that needs to be translated. The translation can be done by hand directly in the PO files of each target language or via the transifex service.
	</div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
			<a href="http://www.transifex.com">Transifex</a> is a free service to help translate documents and organize distributed teams of translators. Anyone interested in helping with the translation should get an account on Transifex
		</div><div class="para">
			Three CloudStack projects exist on Transifex. It is recommended to tour those projects to become familiar with Transifex: 
			<div class="itemizedlist"><ul><li class="listitem"><div class="para">
						<a href="https://www.transifex.com/projects/p/ACS_DOCS/">https://www.transifex.com/projects/p/ACS_DOCS/</a>
					</div></li><li class="listitem"><div class="para">
						<a href="https://www.transifex.com/projects/p/ACS_Runbook/">https://www.transifex.com/projects/p/ACS_Runbook/</a>
					</div></li><li class="listitem"><div class="para">
						<a href="https://www.transifex.com/projects/p/CloudStack_UI/">https://www.transifex.com/projects/p/CloudStackUI/</a>
					</div></li></ul></div>

		</div></div></div><div class="warning"><div class="admonition_header"><h2>警告</h2></div><div class="admonition"><div class="para">
			The pot directory should already exist in the source tree. If you want to build an up to date translation, you might have to update it to include any pot file that was not previously generated.
		</div><div class="para">
			To register new resources on transifex, you will need to be an admin of the transifex CloudStack site. Send an email to the developer list if you want access.
		</div></div></div><div class="para">
		First we need to generate the .pot files for all the DocBook xml files needed for a particular guide. This is well explained at the publican website in a section on how to <a href="http://rlandmann.fedorapeople.org/pug/sect-Users_Guide-Preparing_a_document_for_translation.html">prepare</a> a document for translation.
	</div><div class="para">
		The basic command to execute to build the pot files for the developer guide is:
	</div><pre class="programlisting">publican update_pot --config=publican-devguide.cfg</pre><div class="para">
		This will create a pot directory with pot files in it, one for each corresponding xml files needed to build the guide. Once generated, all pots files need to be configured for translation using transifex this is best done by using the transifex client that you can install with the following command (For RHEL and its derivatives):
	</div><pre class="programlisting">yum install transifex-client</pre><div class="para">
		The transifex client is also available via PyPi and you can install it like this:
	</div><pre class="programlisting">easy_install transifex-client</pre><div class="para">
		Once you have installed the transifex client you can run the <span class="emphasis"><em>settx.sh</em></span> script in the <span class="emphasis"><em>docs</em></span> directory. This will create the <span class="emphasis"><em>.tx/config</em></span> file used by transifex to push and pull all translation strings.
	</div><div class="para">
		All the resource files need to be uploaded to transifex, this is done with the transifex client like so:
	</div><pre class="programlisting">tx push -s</pre><div class="para">
		Once the translators have completed translation of the documentation, the translated strings can be pulled from transifex like so:
	</div><pre class="programlisting">tx pull -a</pre><div class="para">
		If you wish to push specific resource files or pull specific languages translation strings, you can do so with the transifex client. A complete documentation of the client is available on the <a href="http://help.transifex.com/features/client/">client</a> website
	</div><div class="para">
		When you pull new translation strings a directory will be created corresponding to the language of the translation. This directory will contain PO files that will be used by Publican to create the documentation in that specific language. For example assuming that you pull the French translation whose language code is fr-FR, you will build the documentation with publican:
	</div><pre class="programlisting">publican build --config=publican-devguide.cfg --formats=html --langs=fr-FR</pre><div class="warning"><div class="admonition_header"><h2>警告</h2></div><div class="admonition"><div class="para">
			Some languages like Chinese or Japanese will not render well in pdf format and html should be used.
		</div></div></div><div xml:lang="ja-JP" class="section" id="translating-documentation" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="translating-documentation">7.4.1. Translating CloudStack Documentation</h3></div></div></div><div class="para">
		There are two ways to translate the documentation:
	</div><div class="para">
		<div class="itemizedlist"><ul><li class="listitem"><div class="para">
					Directly using the Transifex website and using their user interface.
				</div></li><li class="listitem"><div class="para">
					Using the Transifex client and pushing your translated strings to the website.
				</div></li></ul></div>

	</div><div class="para">
		Once a translation is complete, a site admin will pull the translated strings within the CloudStack repository, build the documentation and publish it.
	</div><div class="para">
		For instructions on how to use the Transifex website see <a href="http://sebgoa.blogspot.ch/2012/11/translating-apache-cloudstack-docs-with.html">http://sebgoa.blogspot.ch/2012/11/translating-apache-cloudstack-docs-with.html</a>
	</div><div class="para">
		For instructions on how to use the Transifex client to translate from the command line see <a href="http://sebgoa.blogspot.ch/2012/12/using-transifex-client-to-translate.html">http://sebgoa.blogspot.ch/2012/12/using-transifex-client-to-translate.html</a>
	</div></div></div></div><div xml:lang="ja-JP" class="chapter" id="tools" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title">第8章 Tools</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#devcloud">8.1. DevCloud</a></span></dt><dd><dl><dt><span class="section"><a href="#devcloud-usage-mode">8.1.1. DevCloud Usage Mode</a></span></dt><dt><span class="section"><a href="#building-devcloud">8.1.2. Building DevCloud</a></span></dt></dl></dd><dt><span class="section"><a href="#marvin">8.2. Marvin</a></span></dt><dd><dl><dt><span class="section"><a href="#building-marvin">8.2.1. Building and Installing Marvin</a></span></dt></dl></dd><dt><span class="section"><a href="#cloudmonkey">8.3. CloudMonkey</a></span></dt><dd><dl><dt><span class="section"><a href="#gettingcloudmonkey">8.3.1. Installing CloudMonkey</a></span></dt><dt><span class="section"><a href="#configuringcloudmonkey">8.3.2. 構成</a></span></dt><dt><span class="section"><a href="#cliapidiscovery">8.3.3. API Discovery</a></span></dt><dt><span class="section"><a href="#clitabularoutput">8.3.4. Tabular Output</a></span></dt><dt><span class="section"><a href="#interactivecli">8.3.5. Interactive Shell Usage</a></span></dt><dt><span class="section"><a href="#startingavmexample">8.3.6. Starting a Virtual Machine instance with CloudMonkey</a></span></dt><dt><span class="section"><a href="#scriptingcli">8.3.7. Scripting with CloudMonkey</a></span></dt></dl></dd><dt><span class="section"><a href="#libcloud-examples">8.4. Apache Libcloud</a></span></dt></dl></div><div xml:lang="ja-JP" class="section" id="devcloud" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="devcloud">8.1. DevCloud</h2></div></div></div><div class="para">
		DevCloud is the CloudStack sandbox. It is provided as a Virtual Box appliance. It is meant to be used as a development environment to easily test new CloudStack development. It has also been used for training and CloudStack demos since it provides a <span class="emphasis"><em>Cloud in a box</em></span>.
	</div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
			DevCloud is provided as a convenience by community members. It is not an official CloudStack release artifact.
		</div><div class="para">
			The CloudStack source code however, contains tools to build your own DevCloud.
		</div></div></div><div class="warning"><div class="admonition_header"><h2>警告</h2></div><div class="admonition"><div class="para">
			DevCloud is under development and should be considered a Work In Progress (WIP), the wiki is the most up to date documentation:
		</div><div class="para">
			<a href="https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud">https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud</a>
		</div></div></div><div xml:lang="ja-JP" class="section" id="devcloud-usage-mode" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="devcloud-usage-mode">8.1.1. DevCloud Usage Mode</h3></div></div></div><div class="para">
		DevCloud can be used in several different ways:
	</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
				Full sandbox. Where CloudStack is run within the DevCloud instance started in Virtual Box.
			</div><div class="para">
				In this mode, the CloudStack management server runs within the instance and nested virtualization allows instantiation of tiny VMs within DevCloud itself. CloudStack code modifications are done within DevCloud.
			</div><div class="para">
				The following diagram shows the architecture of the SandBox mode.
			</div><div class="mediaobject"><img src="./images/DevCloud.png" width="270" alt="DevCloud.png: Schematic of the DevCloud SandBox architecture" /></div></li><li class="listitem"><div class="para">
				A deployment environment. Where CloudStack code is developed in the localhost of the developer and the resulting build is deployed within DevCloud
			</div><div class="para">
				This mode was used in the testing procedure of CloudStack 4.0.0 incubating release. See the following screencast to see how: <a href="http://vimeo.com/54621457">http://vimeo.com/54621457</a>
			</div></li><li class="listitem"><div class="para">
				A host-only mode. Where DevCloud is used only as a host. CloudStack management server is run in the localhost of the developer
			</div><div class="para">
				This mode makes use of a host-only interface defined in the Virtual Box preferences. Check the following screencast to see how: <a href="http://vimeo.com/54610161">http://vimeo.com/54610161</a>
			</div><div class="para">
				The following schematic shows the architecture of the Host-Only mode.
			</div><div class="mediaobject"><img src="./images/DevCloud-hostonly.png" width="270" alt="DevCloud-hostonly.png: Schematic of the DevCloud host-only architecture" /></div></li></ol></div></div><div xml:lang="ja-JP" class="section" id="building-devcloud" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="building-devcloud">8.1.2. Building DevCloud</h3></div></div></div><div class="para">
		The DevCloud appliance can be downloaded from the wiki at <a href="https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud">https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud</a>. It can also be built from scratch. Code is being developed to provide this alternative build. It is based on <span class="emphasis"><em>veewee</em></span>, <span class="emphasis"><em>Vagrant</em></span> and <span class="emphasis"><em>Puppet</em></span>.
	</div><div class="para">
		The goal is to automate the DevCloud build and make this automation capability available to all within the source release of CloudStack
	</div><div class="warning"><div class="admonition_header"><h2>警告</h2></div><div class="admonition"><div class="para">
			This is under heavy development. The code is located in the source tree under <span class="emphasis"><em>tools/devcloud</em></span>
		</div><div class="para">
			A preliminary wiki page describes the build at <a href="https://cwiki.apache.org/CLOUDSTACK/building-devcloud.html">https://cwiki.pache.org/CLOUDSTACK/building-devcloud.html</a>
		</div></div></div></div></div><div xml:lang="ja-JP" class="section" id="marvin" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="marvin">8.2. Marvin</h2></div></div></div><div class="para">
		Marvin is the CloudStack automation framework. It originated as a tool for integration testing but is now also used to build DevCloud as well as to provide a Python CloudStack API binding.
	</div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
			Marvin's complete documenation is on the wiki at <a href="https://cwiki.apache.org/CLOUDSTACK/testing-with-python.html">https://cwiki.apache.org/CLOUDSTACK/testing-with-python.html</a>
		</div><div class="para">
			The source code is located at <span class="emphasis"><em>tools/marvin</em></span>
		</div></div></div><div xml:lang="ja-JP" class="section" id="building-marvin" lang="ja-JP"><div class="titlepage"><div><div><h3 class="title" id="building-marvin">8.2.1. Building and Installing Marvin</h3></div></div></div><div class="para">
		Marvin is built with Maven and is dependent on APIdoc. To build it do the following in the root tree of CloudStack:
	</div><pre class="programlisting">mvn -P developer -pl :cloud-apidoc</pre><pre class="programlisting">mvn -P developer -pl :cloud-marvin</pre><div class="para">
		If successful the build will have created the cloudstackAPI Python package under tools/marvin/marvin/cloudstackAPI as well as a gziped Marvin package under tools/marvin dist. To install the Python Marvin module do the following in tools/marvin:
	</div><pre class="programlisting">sudo python ./setup.py install</pre><div class="para">
		The dependencies will be downloaded the Python module installed and you should be able to use Marvin in Python. Check that you can import the module before starting to use it.
	</div><pre class="programlisting">$ python
Python 2.7.3 (default, Nov 17 2012, 19:54:34) 
[GCC 4.2.1 Compatible Apple Clang 4.1 ((tags/Apple/clang-421.11.66))] on darwin
Type "help", "copyright", "credits" or "license" for more information.
&gt;&gt;&gt; import marvin
&gt;&gt;&gt; from marvin.cloudstackAPI import *
&gt;&gt;&gt;</pre><div class="para">
		You could also install it using <span class="emphasis"><em>pip</em></span> or <span class="emphasis"><em>easy_install</em></span> using the local distribution package in tools/marvin/dist :
	</div><pre class="programlisting">pip install tools/marvin/dist/Marvin-0.1.0.tar.gz</pre><div class="para">
		Or:
	</div><pre class="programlisting">easy_install tools/marvin/dist/Marvin-0.1.0.tar.gz</pre></div></div><div xml:lang="ja-JP" class="section" id="cloudmonkey" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="cloudmonkey">8.3. CloudMonkey</h2></div></div></div><div class="para">
		CloudMonkey is the CloudStack Command Line Interface (CLI). It is written in Python. CloudMonkey can be used both as an interactive shell and as a command line tool which simplifies CloudStack configuration and management. It can be used with CloudStack releases since the 4.0.x branch.
	</div><div class="warning"><div class="admonition_header"><h2>警告</h2></div><div class="admonition"><div class="para">
			CloudMonkey is still under development and should be considered a Work In Progress (WIP), the wiki is the most up to date documentation:
		</div><div class="para">
			<a href="https://cwiki.apache.org/CLOUDSTACK/cloudstack-cloudmonkey-cli.html">https://cwiki.apache.org/CLOUDSTACK/cloudstack-cloudmonkey-cli.html</a>
		</div></div></div><div class="section" id="gettingcloudmonkey"><div class="titlepage"><div><div><h3 class="title" id="gettingcloudmonkey">8.3.1. Installing CloudMonkey</h3></div></div></div><div class="para">
			CloudMonkey is dependent on <span class="emphasis"><em>readline, pygments, prettytable</em></span>, when installing from source you will need to resolve those dependencies. Using the cheese shop, the dependencies will be automatically installed.
		</div><div class="para">
			There are three ways to get CloudMonkey. Via the official CloudStack source releases or via a community maintained distribution at <a href="http://pypi.python.org/pypi/cloudmonkey/">the cheese shop</a>. Developers can also get it directly from the git repository in <span class="emphasis"><em>tools/cli/</em></span>.
		</div><div class="para">
			<div class="itemizedlist"><ul><li class="listitem"><div class="para">
						Via the official Apache CloudStack releases as well as the git repository.
					</div><pre class="programlisting">
    
$ git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git # (optional if using a release download)
$ mvn clean install -P developer
$ cd tools/cli # cloudmonkey-x.x.x.tar.gz will be built in dist
$ python setup.py build
$ python setup.py install
    
</pre></li><li class="listitem"><div class="para">
						Via a community maintained package on Cheese Shop
					</div><div class="para">
						
<pre class="programlisting">pip install cloudmonkey</pre>
					</div></li></ul></div>

		</div></div><div class="section" id="configuringcloudmonkey"><div class="titlepage"><div><div><h3 class="title" id="configuringcloudmonkey">8.3.2. 構成</h3></div></div></div><div class="para">
			To configure CloudMonkey you can edit the ~/.cloudmonkey/config file in the user's home directory as shown below. The values can also be set interactively at the cloudmonkey prompt. Logs are kept in ~/.cloudmonkey/log, and history is stored in ~/.cloudmonkey/history. Discovered apis are listed in ~/.cloudmonkey/cache. Only the log and history files can be custom paths and can be configured by setting appropriate file paths in ~/.cloudmonkey/config
		</div><pre class="programlisting">
$ cat ~/.cloudmonkey/config 
[core]
log_file = /Users/sebastiengoasguen/.cloudmonkey/log
asyncblock = true
paramcompletion = false
history_file = /Users/sebastiengoasguen/.cloudmonkey/history

[ui]
color = true
prompt = &gt; 
tabularize = false

[user]
secretkey =VDaACYb0LV9eNjTetIOElcVQkvJck_J_QljX_FcHRj87ZKiy0z0ty0ZsYBkoXkY9b7eq1EhwJaw7FF3akA3KBQ 
apikey = plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdMkAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg

[server]
path = /client/api
host = localhost
protocol = http
port = 8080
timeout = 3600
</pre><div class="para">
			The values can also be set at the CloudMonkey prompt. The API and secret keys are obtained via the CloudStack UI or via a raw api call.
		</div><pre class="programlisting">

$ cloudmonkey
☁ Apache CloudStack cloudmonkey 4.1.0-snapshot. Type help or ? to list commands.

&gt; set prompt myprompt&gt;
myprompt&gt; set host localhost
myprompt&gt; set port 8080
myprompt&gt; set apikey &lt;your api key&gt;
myprompt&gt; set secretkey &lt;your secret key&gt;

</pre><div class="para">
			You can use CloudMonkey to interact with a local cloud, and even with a remote public cloud. You just need to set the host value properly and obtain the keys from the cloud administrator.
		</div></div><div class="section" id="cliapidiscovery"><div class="titlepage"><div><div><h3 class="title" id="cliapidiscovery">8.3.3. API Discovery</h3></div></div></div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
				In CloudStack 4.0.* releases, the list of api calls available will be pre-cached, while starting with CloudStack 4.1 releases and above an API discovery service is enabled. CloudMonkey will discover automatically the api calls available on the management server. The sync command in CloudMonkey pulls a list of apis which are accessible to your user role, along with help docs etc. and stores them in ~/.cloudmonkey/cache. This allows cloudmonkey to be adaptable to changes in mgmt server, so in case the sysadmin enables a plugin such as Nicira NVP for that user role, the users can get those changes. New verbs and grammar (DSL) rules are created on the fly.
			</div></div></div><div class="para">
			To discover the APIs available do:
		</div><pre class="programlisting">
 &gt; sync
324 APIs discovered and cached
</pre></div><div class="section" id="clitabularoutput"><div class="titlepage"><div><div><h3 class="title" id="clitabularoutput">8.3.4. Tabular Output</h3></div></div></div><div class="para">
			The number of key/value pairs returned by the api calls can be large resulting in a very long output. To enable easier viewing of the output, a tabular formatting can be setup. You may enable tabular listing and even choose set of column fields, this allows you to create your own field using the filter param which takes in comma separated argument. If argument has a space, put them under double quotes. The create table will have the same sequence of field filters provided
		</div><div class="para">
			To enable it, use the <span class="emphasis"><em>set</em></span> function and create filters like so:
		</div><pre class="programlisting">
&gt; set tabularize true
&gt; list users filter=id,domain,account
count = 1
user:
+--------------------------------------+--------+---------+
|                  id                  | domain | account |
+--------------------------------------+--------+---------+
| 7ed6d5da-93b2-4545-a502-23d20b48ef2a |  ROOT  |  admin  |
+--------------------------------------+--------+---------+
</pre></div><div class="section" id="interactivecli"><div class="titlepage"><div><div><h3 class="title" id="interactivecli">8.3.5. Interactive Shell Usage</h3></div></div></div><div class="para">
			To start learning CloudMonkey, the best is to use the interactive shell. Simply type CloudMonkey at the prompt and you should get the interactive shell.
		</div><div class="para">
			At the CloudMonkey prompt press the tab key twice, you will see all potential verbs available. Pick on, enter a space and then press tab twice. You will see all actions available for that verb
		</div><pre class="programlisting">

cloudmonkey&gt;
EOF        assign     cancel     create     detach     extract    ldap       prepare    reconnect  restart    shell      update     
activate   associate  change     delete     disable    generate   list       query      register   restore    start      upload     
add        attach     configure  deploy     enable     get        mark       quit       remove     revoke     stop       
api        authorize  copy       destroy    exit       help       migrate    reboot     reset      set        suspend    
cloudmonkey&gt;create 
account                diskoffering           loadbalancerrule       portforwardingrule     snapshot               tags                   vpc
autoscalepolicy        domain                 network                privategateway         snapshotpolicy         template               vpcoffering
autoscalevmgroup       firewallrule           networkacl             project                sshkeypair             user                   vpnconnection
autoscalevmprofile     instancegroup          networkoffering        remoteaccessvpn        staticroute            virtualrouterelement   vpncustomergateway
condition              ipforwardingrule       physicalnetwork        securitygroup          storagenetworkiprange  vlaniprange            vpngateway
counter                lbstickinesspolicy     pod                    serviceoffering        storagepool            volume                 zone

</pre><div class="para">
			Picking one action and entering a space plus the tab key, you will obtain the list of parameters for that specific api call.
		</div><pre class="programlisting">

cloudmonkey&gt;create network 
account=            domainid=           isAsync=            networkdomain=      projectid=          vlan=               
acltype=            endip=              name=               networkofferingid=  startip=            vpcid=              
displaytext=        gateway=            netmask=            physicalnetworkid=  subdomainaccess=    zoneid=             

</pre><div class="para">
			To get additional help on that specific api call you can use the following:
		</div><pre class="programlisting">

cloudmonkey&gt;create network -h
Creates a network
Required args: displaytext name networkofferingid zoneid
Args: account acltype displaytext domainid endip gateway isAsync name netmask networkdomain networkofferingid physicalnetworkid projectid startip subdomainaccess vlan vpcid zoneid

cloudmonkey&gt;create network -help
Creates a network
Required args: displaytext name networkofferingid zoneid
Args: account acltype displaytext domainid endip gateway isAsync name netmask networkdomain networkofferingid physicalnetworkid projectid startip subdomainaccess vlan vpcid zoneid

cloudmonkey&gt;create network --help
Creates a network
Required args: displaytext name networkofferingid zoneid
Args: account acltype displaytext domainid endip gateway isAsync name netmask networkdomain networkofferingid physicalnetworkid projectid startip subdomainaccess vlan vpcid zoneid
cloudmonkey&gt;    

</pre><div class="para">
			Note the required arguments necessary for the calls.
		</div><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
				To find out the required parameters value, using a debugger console on the CloudStack UI might be very useful. For instance using Firebug on Firefox, you can navigate the UI and check the parameters values for each call you are making as you navigate the UI.
			</div></div></div></div><div class="section" id="startingavmexample"><div class="titlepage"><div><div><h3 class="title" id="startingavmexample">8.3.6. Starting a Virtual Machine instance with CloudMonkey</h3></div></div></div><div class="para">
			To start a virtual machine instance we will use the <span class="emphasis"><em>deploy virtualmachine</em></span> call.
		</div><pre class="programlisting">

cloudmonkey&gt;deploy virtualmachine -h
Creates and automatically starts a virtual machine based on a service offering, disk offering, and template.
Required args: serviceofferingid templateid zoneid
Args: account diskofferingid displayname domainid group hostid hypervisor ipaddress iptonetworklist isAsync keyboard keypair name networkids projectid securitygroupids securitygroupnames serviceofferingid size startvm templateid userdata zoneid

</pre><div class="para">
			The required arguments are <span class="emphasis"><em>serviceofferingid, templateid and zoneid</em></span>
		</div><div class="para">
			In order to specify the template that we want to use, we can list all available templates with the following call:
		</div><pre class="programlisting">

cloudmonkey&gt;list templates templatefilter=all
count = 2
template:
========
domain = ROOT
domainid = 8a111e58-e155-4482-93ce-84efff3c7c77
zoneid = e1bfdfaf-3d9b-43d4-9aea-2c9f173a1ae7
displaytext = SystemVM Template (XenServer)
ostypeid = 849d7d0a-9fbe-452a-85aa-70e0a0cbc688
passwordenabled = False
id = 6d360f79-4de9-468c-82f8-a348135d298e
size = 2101252608
isready = True
templatetype = SYSTEM
zonename = devcloud
...&lt;snipped&gt;

</pre><div class="para">
			In this snippet, I used DevCloud and only showed the beginning output of the first template, the SystemVM template
		</div><div class="para">
			Similarly to get the <span class="emphasis"><em>serviceofferingid</em></span> you would do:
		</div><pre class="programlisting">

cloudmonkey&gt;list serviceofferings | grep id
id = ef2537ad-c70f-11e1-821b-0800277e749c
id = c66c2557-12a7-4b32-94f4-48837da3fa84
id = 3d8b82e5-d8e7-48d5-a554-cf853111bc50

</pre><div class="para">
			Note that we can use the linux pipe as well as standard linux commands within the interactive shell. Finally we would start an instance with the following call:
		</div><pre class="programlisting">

cloudmonkey&gt;deploy virtualmachine templateid=13ccff62-132b-4caf-b456-e8ef20cbff0e zoneid=e1bfdfaf-3d9b-43d4-9aea-2c9f173a1ae7 serviceofferingid=ef2537ad-c70f-11e1-821b-0800277e749c
jobprocstatus = 0
created = 2013-03-05T13:04:51-0800
cmd = com.cloud.api.commands.DeployVMCmd
userid = 7ed6d5da-93b2-4545-a502-23d20b48ef2a
jobstatus = 1
jobid = c441d894-e116-402d-aa36-fdb45adb16b7
jobresultcode = 0
jobresulttype = object
jobresult:
=========
virtualmachine:
==============
domain = ROOT
domainid = 8a111e58-e155-4482-93ce-84efff3c7c77
haenable = False
templatename = tiny Linux
...&lt;snipped&gt;

</pre><div class="para">
			The instance would be stopped with:
		</div><pre class="programlisting">
cloudmonkey&gt;stop virtualmachine id=7efe0377-4102-4193-bff8-c706909cc2d2
</pre><div class="note"><div class="admonition_header"><h2>注記</h2></div><div class="admonition"><div class="para">
				The <span class="emphasis"><em>ids</em></span> that you will use will differ from this example. Make sure you use the ones that corresponds to your CloudStack cloud.
			</div></div></div></div><div class="section" id="scriptingcli"><div class="titlepage"><div><div><h3 class="title" id="scriptingcli">8.3.7. Scripting with CloudMonkey</h3></div></div></div><div class="para">
			All previous examples use CloudMonkey via the interactive shell, however it can be used as a straightfoward CLI, passing the commands to the <span class="emphasis"><em>cloudmonkey</em></span> command like shown below.
		</div><div class="para">
			
<pre class="programlisting">$cloudmonkey list users</pre>
		</div><div class="para">
			As such it can be used in shell scripts, it can received commands via stdin and its output can be parsed like any other unix commands as mentioned before.
		</div></div></div><div xml:lang="ja-JP" class="section" id="libcloud-examples" lang="ja-JP"><div class="titlepage"><div><div><h2 class="title" id="libcloud-examples">8.4. Apache Libcloud</h2></div></div></div><div class="para">
		There are many tools available to interface with the CloudStack API. Apache Libcloud is one of those. In this section we provide a basic example of how to use Libcloud with CloudStack. It assumes that you have access to a CloudStack endpoint and that you have the API access key and secret key of a user.
	</div><div class="para">
		To install Libcloud refer to the libcloud website. If you are familiar with Pypi simply do:
	</div><pre class="programlisting">pip install apache-libcloud</pre><div class="para">
		You should see the following output:
	</div><pre class="programlisting">
pip install apache-libcloud
Downloading/unpacking apache-libcloud
  Downloading apache-libcloud-0.12.4.tar.bz2 (376kB): 376kB downloaded
  Running setup.py egg_info for package apache-libcloud
    
Installing collected packages: apache-libcloud
  Running setup.py install for apache-libcloud
    
Successfully installed apache-libcloud
Cleaning up...
</pre><div class="para">
		You can then open a Python interactive shell, create an instance of a CloudStack driver and call the available methods via the libcloud API.
	</div><pre class="programlisting">
 
&gt;&gt;&gt; from libcloud.compute.types import Provider
&gt;&gt;&gt; from libcloud.compute.providers import get_driver
&gt;&gt;&gt; Driver = get_driver(Provider.CLOUDSTACK)
&gt;&gt;&gt; apikey='plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg'
&gt;&gt;&gt; secretkey='VDaACYb0LV9eNjTetIOElcVQkvJck_J_QljX_FcHRj87ZKiy0z0ty0ZsYBkoXkY9b7eq1EhwJaw7FF3akA3KBQ'
&gt;&gt;&gt; host='http://localhost:8080'
&gt;&gt;&gt; path='/client/api'
&gt;&gt;&gt; conn=Driver(apikey,secretkey,secure='False',host='localhost:8080',path=path)
&gt;&gt;&gt; conn=Driver(key=apikey,secret=secretkey,secure=False,host='localhost',port='8080',path=path)
&gt;&gt;&gt; conn.list_images()
[&lt;NodeImage: id=13ccff62-132b-4caf-b456-e8ef20cbff0e, name=tiny Linux, driver=CloudStack  ...&gt;]
&gt;&gt;&gt; conn.list_sizes()
[&lt;NodeSize: id=ef2537ad-c70f-11e1-821b-0800277e749c, name=tinyOffering, ram=100 disk=0 bandwidth=0 price=0 driver=CloudStack ...&gt;, &lt;NodeSize: id=c66c2557-12a7-4b32-94f4-48837da3fa84, name=Small Instance, ram=512 disk=0 bandwidth=0 price=0 driver=CloudStack ...&gt;, &lt;NodeSize: id=3d8b82e5-d8e7-48d5-a554-cf853111bc50, name=Medium Instance, ram=1024 disk=0 bandwidth=0 price=0 driver=CloudStack ...&gt;]
&gt;&gt;&gt; images=conn.list_images()
&gt;&gt;&gt; offerings=conn.list_sizes()
&gt;&gt;&gt; node=conn.create_node(name='toto',image=images[0],size=offerings[0])
&gt;&gt;&gt; help(node)
&gt;&gt;&gt; node.get_uuid()
'b1aa381ba1de7f2d5048e248848993d5a900984f'
&gt;&gt;&gt; node.name
u'toto'

</pre><div class="para">
		One of the interesting use cases of Libcloud is that you can use multiple Cloud Providers, such as AWS, Rackspace, OpenNebula, vCloud and so on. You can then create Driver instances to each of these clouds and create your own multi cloud application.
	</div></div></div><div xml:lang="ja-JP" class="appendix" id="event-types" lang="ja-JP"><div class="titlepage"><div><div><h1 class="title">イベントの種類</h1></div></div></div><div class="informaltable"><table border="1"><colgroup><col align="left" class="c1" width="33%" /><col align="left" class="c2" width="33%" /><col width="33%" /></colgroup><tbody><tr><td align="left">
						<div class="para">
							VM.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							TEMPLATE.EXTRACT
						</div>
					</td><td align="left">
						<div class="para">
							SG.REVOKE.INGRESS
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							VM.DESTROY
						</div>
					</td><td align="left">
						<div class="para">
							TEMPLATE.UPLOAD
						</div>
					</td><td align="left">
						<div class="para">
							HOST.RECONNECT
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							VM.START
						</div>
					</td><td align="left">
						<div class="para">
							TEMPLATE.CLEANUP
						</div>
					</td><td align="left">
						<div class="para">
							MAINT.CANCEL
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							VM.STOP
						</div>
					</td><td align="left">
						<div class="para">
							VOLUME.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							MAINT.CANCEL.PS
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							VM.REBOOT
						</div>
					</td><td align="left">
						<div class="para">
							VOLUME.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							MAINT.PREPARE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							VM.UPGRADE
						</div>
					</td><td align="left">
						<div class="para">
							VOLUME.ATTACH
						</div>
					</td><td align="left">
						<div class="para">
							MAINT.PREPARE.PS
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							VM.RESETPASSWORD
						</div>
					</td><td align="left">
						<div class="para">
							VOLUME.DETACH
						</div>
					</td><td align="left">
						<div class="para">
							VPN.REMOTE.ACCESS.CREATE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							ROUTER.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							VOLUME.UPLOAD
						</div>
					</td><td align="left">
						<div class="para">
							VPN.USER.ADD
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							ROUTER.DESTROY
						</div>
					</td><td align="left">
						<div class="para">
							SERVICEOFFERING.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							VPN.USER.REMOVE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							ROUTER.START
						</div>
					</td><td align="left">
						<div class="para">
							SERVICEOFFERING.UPDATE
						</div>
					</td><td align="left">
						<div class="para">
							NETWORK.RESTART
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							ROUTER.STOP
						</div>
					</td><td align="left">
						<div class="para">
							SERVICEOFFERING.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							UPLOAD.CUSTOM.CERTIFICATE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							ROUTER.REBOOT
						</div>
					</td><td align="left">
						<div class="para">
							DOMAIN.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							UPLOAD.CUSTOM.CERTIFICATE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							ROUTER.HA
						</div>
					</td><td align="left">
						<div class="para">
							DOMAIN.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							STATICNAT.DISABLE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							PROXY.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							DOMAIN.UPDATE
						</div>
					</td><td align="left">
						<div class="para">
							SSVM.CREATE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							PROXY.DESTROY
						</div>
					</td><td align="left">
						<div class="para">
							SNAPSHOT.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							SSVM.DESTROY
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							PROXY.START
						</div>
					</td><td align="left">
						<div class="para">
							SNAPSHOT.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							SSVM.START
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							PROXY.STOP
						</div>
					</td><td align="left">
						<div class="para">
							SNAPSHOTPOLICY.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							SSVM.STOP
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							PROXY.REBOOT
						</div>
					</td><td align="left">
						<div class="para">
							SNAPSHOTPOLICY.UPDATE
						</div>
					</td><td align="left">
						<div class="para">
							SSVM.REBOOT
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							PROXY.HA
						</div>
					</td><td align="left">
						<div class="para">
							SNAPSHOTPOLICY.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							SSVM.H
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							VNC.CONNECT
						</div>
					</td><td align="left">
						<div class="para">
							VNC.DISCONNECT
						</div>
					</td><td align="left">
						<div class="para">
							NET.IPASSIGN
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							NET.IPRELEASE
						</div>
					</td><td align="left">
						<div class="para">
							NET.RULEADD
						</div>
					</td><td align="left">
						<div class="para">
							NET.RULEDELETE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							NET.RULEMODIFY
						</div>
					</td><td align="left">
						<div class="para">
							NETWORK.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							NETWORK.DELETE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							LB.ASSIGN.TO.RULE
						</div>
					</td><td align="left">
						<div class="para">
							LB.REMOVE.FROM.RULE
						</div>
					</td><td align="left">
						<div class="para">
							LB.CREATE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							LB.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							LB.UPDATE
						</div>
					</td><td align="left">
						<div class="para">
							USER.LOGIN
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							USER.LOGOUT
						</div>
					</td><td align="left">
						<div class="para">
							USER.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							USER.DELETE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							USER.UPDATE
						</div>
					</td><td align="left">
						<div class="para">
							USER.DISABLE
						</div>
					</td><td align="left">
						<div class="para">
							TEMPLATE.CREATE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							TEMPLATE.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							TEMPLATE.UPDATE
						</div>
					</td><td align="left">
						<div class="para">
							TEMPLATE.COPY
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							TEMPLATE.DOWNLOAD.START
						</div>
					</td><td align="left">
						<div class="para">
							TEMPLATE.DOWNLOAD.SUCCESS
						</div>
					</td><td align="left">
						<div class="para">
							TEMPLATE.DOWNLOAD.FAILED
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							ISO.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							ISO.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							ISO.COPY
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							ISO.ATTACH
						</div>
					</td><td align="left">
						<div class="para">
							ISO.DETACH
						</div>
					</td><td align="left">
						<div class="para">
							ISO.EXTRACT
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							ISO.UPLOAD
						</div>
					</td><td align="left">
						<div class="para">
							SERVICE.OFFERING.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							SERVICE.OFFERING.EDIT
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							SERVICE.OFFERING.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							DISK.OFFERING.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							DISK.OFFERING.EDIT
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							DISK.OFFERING.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							NETWORK.OFFERING.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							NETWORK.OFFERING.EDIT
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							NETWORK.OFFERING.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							POD.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							POD.EDIT
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							POD.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							ZONE.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							ZONE.EDIT
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							ZONE.DELETE
						</div>
					</td><td align="left">
						<div class="para">
							VLAN.IP.RANGE.CREATE
						</div>
					</td><td align="left">
						<div class="para">
							VLAN.IP.RANGE.DELETE
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							CONFIGURATION.VALUE.EDIT
						</div>
					</td><td align="left">
						<div class="para">
							SG.AUTH.INGRESS
						</div>
					</td><td align="left">
						<div class="para">
						</div>
					</td></tr></tbody></table></div></div><div xml:lang="ja-JP" class="appendix" id="alerts" lang="ja-JP"><div class="titlepage"><div><div><h1 class="title">Alerts</h1></div></div></div><div class="para">
		The following is the list of alert type numbers. The current alerts can be found by calling listAlerts.
	</div><pre class="programlisting">MEMORY = 0</pre><pre class="programlisting">CPU = 1</pre><pre class="programlisting">STORAGE =2</pre><pre class="programlisting">STORAGE_ALLOCATED = 3</pre><pre class="programlisting">PUBLIC_IP = 4</pre><pre class="programlisting">PRIVATE_IP = 5</pre><pre class="programlisting">HOST = 6</pre><pre class="programlisting">USERVM = 7</pre><pre class="programlisting">DOMAIN_ROUTER = 8</pre><pre class="programlisting">CONSOLE_PROXY = 9</pre><pre class="programlisting">ROUTING = 10// lost connection to default route (to the gateway)</pre><pre class="programlisting">STORAGE_MISC = 11 // lost connection to default route (to the gateway)</pre><pre class="programlisting">USAGE_SERVER = 12 // lost connection to default route (to the gateway)</pre><pre class="programlisting">MANAGMENT_NODE = 13 // lost connection to default route (to the gateway)</pre><pre class="programlisting">DOMAIN_ROUTER_MIGRATE = 14</pre><pre class="programlisting">CONSOLE_PROXY_MIGRATE = 15</pre><pre class="programlisting">USERVM_MIGRATE = 16</pre><pre class="programlisting">VLAN = 17</pre><pre class="programlisting">SSVM = 18</pre><pre class="programlisting">USAGE_SERVER_RESULT = 19</pre><pre class="programlisting">STORAGE_DELETE = 20;</pre><pre class="programlisting">UPDATE_RESOURCE_COUNT = 21; //Generated when we fail to update the resource count</pre><pre class="programlisting">USAGE_SANITY_RESULT = 22;</pre><pre class="programlisting">DIRECT_ATTACHED_PUBLIC_IP = 23;</pre><pre class="programlisting">LOCAL_STORAGE = 24;</pre><pre class="programlisting">RESOURCE_LIMIT_EXCEEDED = 25; //Generated when the resource limit exceeds the limit. Currently used for recurring snapshots only</pre></div><div xml:lang="ja-JP" class="appendix" id="time-zones" lang="ja-JP"><div class="titlepage"><div><div><h1 class="title">タイムゾーン</h1></div></div></div><div class="para">
		CloudStack では、次のタイムゾーン識別子を使用できます。設定の一部で、必須またはオプションのパラメーターとしてタイムゾー ンを使用します。これには、構成テーブルにおける、定期スナップショットのスケジュール、ユーザーの作成、および使用タイムゾーンの指定が含まれます。
	</div><div class="informaltable"><table border="1"><colgroup><col align="left" class="c1" width="33%" /><col align="left" class="c2" width="33%" /><col align="left" class="c3" width="33%" /></colgroup><tbody><tr><td align="left">
						<div class="para">
							Etc/GMT+12
						</div>
					</td><td align="left">
						<div class="para">
							Etc/GMT+11
						</div>
					</td><td align="left">
						<div class="para">
							Pacific/Samoa
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							Pacific/Honolulu
						</div>
					</td><td align="left">
						<div class="para">
							US/Alaska
						</div>
					</td><td align="left">
						<div class="para">
							America/Los_Angeles
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							Mexico/BajaNorte
						</div>
					</td><td align="left">
						<div class="para">
							US/Arizona
						</div>
					</td><td align="left">
						<div class="para">
							US/Mountain
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							America/Chihuahua
						</div>
					</td><td align="left">
						<div class="para">
							America/Chicago
						</div>
					</td><td align="left">
						<div class="para">
							America/Costa_Rica
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							America/Mexico_City
						</div>
					</td><td align="left">
						<div class="para">
							Canada/Saskatchewan
						</div>
					</td><td align="left">
						<div class="para">
							America/Bogota
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							America/New_York
						</div>
					</td><td align="left">
						<div class="para">
							America/Caracas
						</div>
					</td><td align="left">
						<div class="para">
							America/Asuncion
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							America/Cuiaba
						</div>
					</td><td align="left">
						<div class="para">
							America/Halifax
						</div>
					</td><td align="left">
						<div class="para">
							America/La_Paz
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							America/Santiago
						</div>
					</td><td align="left">
						<div class="para">
							America/St_Johns
						</div>
					</td><td align="left">
						<div class="para">
							America/Araguaina
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							America/Argentina/Buenos_Aires
						</div>
					</td><td align="left">
						<div class="para">
							America/Cayenne
						</div>
					</td><td align="left">
						<div class="para">
							America/Godthab
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							America/Montevideo
						</div>
					</td><td align="left">
						<div class="para">
							Etc/GMT+2
						</div>
					</td><td align="left">
						<div class="para">
							Atlantic/Azores
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							Atlantic/Cape_Verde
						</div>
					</td><td align="left">
						<div class="para">
							Africa/Casablanca
						</div>
					</td><td align="left">
						<div class="para">
							Etc/UTC
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							Atlantic/Reykjavik
						</div>
					</td><td align="left">
						<div class="para">
							Europe/London
						</div>
					</td><td align="left">
						<div class="para">
							CET
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							Europe/Bucharest
						</div>
					</td><td align="left">
						<div class="para">
							Africa/Johannesburg
						</div>
					</td><td align="left">
						<div class="para">
							Asia/Beirut
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							Africa/Cairo
						</div>
					</td><td align="left">
						<div class="para">
							Asia/Jerusalem
						</div>
					</td><td align="left">
						<div class="para">
							Europe/Minsk
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							Europe/Moscow
						</div>
					</td><td align="left">
						<div class="para">
							Africa/Nairobi
						</div>
					</td><td align="left">
						<div class="para">
							Asia/Karachi
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							Asia/Kolkata
						</div>
					</td><td align="left">
						<div class="para">
							Asia/Bangkok
						</div>
					</td><td align="left">
						<div class="para">
							Asia/Shanghai
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							Asia/Kuala_Lumpur
						</div>
					</td><td align="left">
						<div class="para">
							Australia/Perth
						</div>
					</td><td align="left">
						<div class="para">
							Asia/Taipei
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							Asia/Tokyo
						</div>
					</td><td align="left">
						<div class="para">
							Asia/Seoul
						</div>
					</td><td align="left">
						<div class="para">
							Australia/Adelaide
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							Australia/Darwin
						</div>
					</td><td align="left">
						<div class="para">
							Australia/Brisbane
						</div>
					</td><td align="left">
						<div class="para">
							Australia/Canberra
						</div>
					</td></tr><tr><td align="left">
						<div class="para">
							Pacific/Guam
						</div>
					</td><td align="left">
						<div class="para">
							Pacific/Auckland
						</div>
					</td><td align="left">
						<div class="para">
						</div>
					</td></tr></tbody></table></div></div><div xml:lang="ja-JP" class="appendix" id="appe-cloudstack-Revision_History" lang="ja-JP"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
		<div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><strong>改訂履歴</strong></th></tr><tr><td align="left">改訂 0-0</td><td align="left">Tue May 29 2012</td><td align="left"><span class="author"><span class="surname">Tomechak</span> <span class="firstname">Jessica</span> [FAMILY Given]</span></td></tr><tr><td align="left" colspan="3">
					<table border="0" summary="Simple list" class="simplelist"><tr><td>Initial creation of book by publican</td></tr></table>

				</td></tr></table></div>

	</div></div></div></body></html>
