5
------------------------------------------------------
6
control and manage cloud computer instances and images
7
------------------------------------------------------
9
:Author: openstack@lists.launchpad.net
11
:Copyright: OpenStack LLC
14
:Manual group: cloud computing
19
cinder-manage <category> <action> [<args>]
24
cinder-manage controls cloud computing instances by managing cinder users, cinder projects, cinder roles, shell selection, vpn connections, and floating IP address configuration. More information about OpenStack Cinder is at http://cinder.openstack.org.
29
The standard pattern for executing a cinder-manage command is:
30
``cinder-manage <category> <command> [<args>]``
32
For example, to obtain a list of all projects:
33
``cinder-manage project list``
35
Run without arguments to see a list of available command categories:
38
Categories are user, project, role, shell, vpn, and floating. Detailed descriptions are below.
40
You can also run with a category argument such as user to see a list of all commands in that category:
41
``cinder-manage user``
43
These sections describe the available categories and arguments for cinder-manage.
48
``cinder-manage db version``
50
Print the current database version.
52
``cinder-manage db sync``
54
Sync the database up to the most recent version. This is the standard way to create the db as well.
59
``cinder-manage user admin <username>``
61
Create an admin user with the name <username>.
63
``cinder-manage user create <username>``
65
Create a normal user with the name <username>.
67
``cinder-manage user delete <username>``
69
Delete the user with the name <username>.
71
``cinder-manage user exports <username>``
73
Outputs a list of access key and secret keys for user to the screen
75
``cinder-manage user list``
77
Outputs a list of all the user names to the screen.
79
``cinder-manage user modify <accesskey> <secretkey> <admin?T/F>``
81
Updates the indicated user keys, indicating with T or F if the user is an admin user. Leave any argument blank if you do not want to update it.
86
``cinder-manage project add <projectname>``
88
Add a cinder project with the name <projectname> to the database.
90
``cinder-manage project create <projectname>``
92
Create a new cinder project with the name <projectname> (you still need to do cinder-manage project add <projectname> to add it to the database).
94
``cinder-manage project delete <projectname>``
96
Delete a cinder project with the name <projectname>.
98
``cinder-manage project environment <projectname> <username>``
100
Exports environment variables for the named project to a file named cinderrc.
102
``cinder-manage project list``
104
Outputs a list of all the projects to the screen.
106
``cinder-manage project quota <projectname>``
108
Outputs the size and specs of the project's instances including gigabytes, instances, floating IPs, volumes, and cores.
110
``cinder-manage project remove <projectname>``
112
Deletes the project with the name <projectname>.
114
``cinder-manage project zipfile``
116
Compresses all related files for a created project into a zip file cinder.zip.
121
``cinder-manage role add <username> <rolename> <(optional) projectname>``
123
Add a user to either a global or project-based role with the indicated <rolename> assigned to the named user. Role names can be one of the following five roles: cloudadmin, itsec, sysadmin, netadmin, developer. If you add the project name as the last argument then the role is assigned just for that project, otherwise the user is assigned the named role for all projects.
125
``cinder-manage role has <username> <projectname>``
126
Checks the user or project and responds with True if the user has a global role with a particular project.
128
``cinder-manage role remove <username> <rolename>``
129
Remove the indicated role from the user.
134
``cinder-manage logs errors``
136
Displays cinder errors from log files.
138
``cinder-manage logs syslog <number>``
140
Displays cinder alerts from syslog.
145
``cinder-manage shell bpython``
147
Starts a new bpython shell.
149
``cinder-manage shell ipython``
151
Starts a new ipython shell.
153
``cinder-manage shell python``
155
Starts a new python shell.
157
``cinder-manage shell run``
159
Starts a new shell using python.
161
``cinder-manage shell script <path/scriptname>``
163
Runs the named script from the specified path with flags set.
168
``cinder-manage vpn list``
170
Displays a list of projects, their IP prot numbers, and what state they're in.
172
``cinder-manage vpn run <projectname>``
174
Starts the VPN for the named project.
176
``cinder-manage vpn spawn``
183
``cinder-manage floating create <ip_range> [--pool <pool>] [--interface <interface>]``
185
Creates floating IP addresses for the given range, optionally specifying
186
a floating pool and a network interface.
188
``cinder-manage floating delete <ip_range>``
190
Deletes floating IP addresses in the range given.
192
``cinder-manage floating list``
194
Displays a list of all floating IP addresses.
199
``cinder-manage flavor list``
201
Outputs a list of all active flavors to the screen.
203
``cinder-manage flavor list --all``
205
Outputs a list of all flavors (active and inactive) to the screen.
207
``cinder-manage flavor create <name> <memory> <vCPU> <local_storage> <flavorID> <(optional) swap> <(optional) RXTX Quota> <(optional) RXTX Cap>``
209
creates a flavor with the following positional arguments:
210
* memory (expressed in megabytes)
212
* local storage (expressed in gigabytes)
213
* flavorid (unique integer)
214
* swap space (expressed in megabytes, defaults to zero, optional)
215
* RXTX quotas (expressed in gigabytes, defaults to zero, optional)
216
* RXTX cap (expressed in gigabytes, defaults to zero, optional)
218
``cinder-manage flavor delete <name>``
220
Delete the flavor with the name <name>. This marks the flavor as inactive and cannot be launched. However, the record stays in the database for archival and billing purposes.
222
``cinder-manage flavor delete <name> --purge``
224
Purges the flavor with the name <name>. This removes this flavor from the database.
229
The instance_type command is provided as an alias for the flavor command. All the same subcommands and arguments from cinder-manage flavor can be used.
234
``cinder-manage image image_register <path> <owner>``
236
Registers an image with the image service.
238
``cinder-manage image kernel_register <path> <owner>``
240
Registers a kernel with the image service.
242
``cinder-manage image ramdisk_register <path> <owner>``
244
Registers a ramdisk with the image service.
246
``cinder-manage image all_register <image_path> <kernel_path> <ramdisk_path> <owner>``
248
Registers an image kernel and ramdisk with the image service.
250
``cinder-manage image convert <directory>``
252
Converts all images in directory from the old (Bexar) format to the new format.
257
``cinder-manage vm list [host]``
258
Show a list of all instances. Accepts optional hostname (to show only instances on specific host).
260
``cinder-manage live-migration <ec2_id> <destination host name>``
261
Live migrate instance from current host to destination host. Requires instance id (which comes from euca-describe-instance) and destination host name (which can be found from cinder-manage service list).
267
The cinder-manage.conf file contains configuration information in the form of python-gflags.
272
* `OpenStack Cinder <http://cinder.openstack.org>`__
273
* `OpenStack Swift <http://swift.openstack.org>`__
278
* Cinder is sourced in Launchpad so you can view current bugs at `OpenStack Cinder <http://cinder.openstack.org>`__