This section contains the following topics:
Cloud Management CLI commands one of the following prefixes:
akm
Commands used for tasks related to access key management.
iaas
Commands used for the full set of supported cloud management tasks.
All IaaS calls are asynchronous. Each CLI command has some common options. Depending on the command prefix, the options can vary. The following table lists these options and their descriptions.
Option | Description | Required |
---|---|---|
--base-url <base_url> |
Base URL of the Oracle Enterprise Manager Ops Center vServer. |
Yes |
--user |
User name of the cloud user. |
Yes for |
--password-file|-p <pw_file> |
Path to the file storing the password of the cloud user. |
Yes for |
--access-key-file|-a <access_key_file> |
Path to the file storing the access key. |
Yes for |
--help|-h |
Explains the command usage and its arguments. |
No |
--header|-H |
Adds a header row to the output. |
No |
--sep <separator> |
Specifies a column separator character. The default separator is TAB. |
No |
--xml |
Displays the output in XML format. The default output is in tabular format. |
No |
--verbose|-v |
Starts the command in verbose mode. |
No |
--debug|-D |
Starts the command in debug mode. |
No |
Before you can use the vDC infrastructure as an Iaas user, you must create an access key, which is used for authenticating cloud web service requests for an account.
User management is provided by a central service within Exalogic Control. The central entry point for cloud API or CLI requests is the cloud web service. The cloud web service handles the authentication and authorization of the calling user, and it manages access keys.
An access key consists of an ID, a private key, a public key, and an authentication target account. The private key is used on the client side to sign HTTP requests. The cloud web service uses the public key to verify incoming HTTP requests and to authenticate the calling user. After creation, the private key is provided to the user. The Cloud User is responsible for limiting access to the private key.
Run the following commands to get started:
View Accounts' information for a cloud user by using the akm-describe-accounts command, as in the following example:
./akm-describe-accounts --base-url https://<localhost>/ --user testuser --password-file ~/pwd.file
This command displays the user name of the specified cloud user along with the account ID, the name, and the description of each account available for that cloud user.
Create an access key by using the akm-create-access-key command, as in the following example:
./akm-create-access-key --base-url https://<localhost>/ --user User1 --password-file ~/pwd.file --account ACC-4b83b85e-592c-45a1-ba71-3bd0774fbd0e --access-key-file ~/ak.file
This command creates an access key and returns an access key identifier, such as AK_32
.
Note:
You can obtain the account ID from the output of the akm-describe-accounts command.
View information about an access key by using the akm-describe-access-keys command, as in the following example:
akm-describe-access-keys --base-url https://<localhost>/ --user User1 --password-file ~/pwd.file
You can describe the vDC capabilities for an account by using the iaas-describe-vdc-capabilities command, as in the following example:
./iaas-describe-vdc-capabilities --base-url https://<localhost>/ -a ak.file -H
This command displays information about the following:
Virtualization type, such as OVM
Virtualization version, such as OVM 3.0.2
Processor architecture
Distribution group support
To import a Server Template, complete the following steps:
You must allocate a set of IP addresses from the private virtual network (vNet) for vServers to be created later.
Complete the following tasks:
Distribution groups are necessary for anti-affinity scaling in an Oracle VM Server pool.
Complete the following tasks:
Complete the following tasks:
Note:
After creating a volume, you must partition the volume using fdisk
and create a file system using mkfs
on the first vServer that is created with the volume. On the vServer, the volume appears as a disk (/dev/hdX
or /dev/xvdX
). After the volume is partitioned and file system created, you must mount it using the /etc/fstab
file on the vServer to make the file system accessible.
If you wish to import a volume from an existing URL instead of creating a new volume, complete the following tasks:
You can create vServers using one of the following commands:
iaas-run-vservers
This command enables you to create and start multiple vServers at once. For more information, see Example Procedure: Creating Multiple vServers.
iaas-run-vserver
This command enables you to create and start a single vServer. For more information, see Example Procedure: Creating a Single vServer.
When you create multiple vServers, only automatic IP address assignment is possible, and a suffix is added to the vServer name for each vServer. When you create a single vServer, you can assign a static IP address. In this case, a suffix is not added to the name of the vServer.
To stop a running vServer, run the iaas-stop-vservers command, as in the following example:
./iaas-stop-vservers --base-url https://<localhost>/ -a ak.file --vserver-ids VSRV-0fb57293-347c-4717-96ef-6dd23154596f
This command stops the specified vServer. It does not return any value.
To attach a volume to a vServer, complete the following steps:
If you wish to detach a volume from a vServer, complete the following steps:
To create a Snapshot from a volume, complete the following steps: