delta/openstack/python-openstackclient.git/doc/source/command-objects/server.rst, branch 5.0.0

reorganize existing documentation according to the new standard layout

2017-06-23T09:54:32+00:00

Move existing content around based on the doc-migration specification.

Replace :doc: markup with :ref: to have sphinx keep track of where the
files move and generate valid hyperlinks.

Add a few toctrees and index pages for the new directories.

Depends-On: Ia750cb049c0f53a234ea70ce1f2bbbb7a2aa9454
Change-Id: I253ee8f89d3ec40e39310c18bb87ed1d3d5de330
Signed-off-by: Doug Hellmann

Merge "Create server with security group ID and name"

2017-05-22T23:09:02+00:00

Create server with security group ID and name

2017-05-22T20:32:01+00:00

Both resource ID and name are supported to identify an object
in openstackclient to make user easy to input, for security group,
nova only support security group name in API when launch a new server,
this patch convert ID to name, then pass name to nova API, and check
the security group exist before creating server.

Change-Id: I1ed4a967fb9de3f91c8945a1ef63f6c7b6b2dfb2
Closes-Bug: #1687814

Make block-device-mapping more stable and clear

2017-05-17T01:42:12+00:00

The patch fix the following issues:

1. ValueError is raised if input don't contain "=". Sometimes the whole
"server create" command is very complex, it's difficult to find out root
reason directly.
2. Don't support to add block device from snapshot, like:
--block-device-mapping
vdb=0c8ae9d8-cadc-4a23-8337-4254614d277e:snapshot:1, it's supported by
novaclient, but not in osc.
3. If input "vdb=", not add any mapping information, the server will be
launched successfully, not raise error message to let use add
volume/snapshot id, just ignore "--block-device-mapping" option.
4. The help message of "block-device-mapping" option is so simple, need
to add some details about how to add , 
contains.

Change-Id: Ib7f7a654c3dc2a8272545f168b4c4ced230ce39e
Depends-On: Ib37913891bbf7a31b570404c4668c490d5ac859b
Closes-Bug: #1667266

Merge "Add --network and --port to server create"

2017-04-25T13:54:46+00:00

Add --network and --port to server create

2017-04-07T14:36:18+00:00

--nic option is quite unhandy. It is better to have
two seperate options --network and --port to add a
network to a new server.

Change-Id: I523abdc83ca2dd4c5dd3871f8f109c2bf57c2e02
Closes-Bug: #1612898

Enable to specify which fixed-ip to add to a vm.

2017-04-04T16:15:29+00:00

This change enables to specify which fixed-ip will be added to a vm using:

 openstack server add fixed ip   --fixed-ip-address 

This change uses interface_attach instead of add_fixed_ip[1] which is
less flexible and uses a deprecated API.

[1] https://review.openstack.org/384261

Closes-Bug: #1678140
Change-Id: I7fe4621439ef0d8dca080551ffaeb614c5a91174

Merge "Help/docs cleanups: marker, limit, ip-address metavars"

2017-04-04T12:32:55+00:00

Help/docs cleanups: marker, limit, ip-address metavars

2017-04-04T03:56:19+00:00

Cleanup help strings and docs for clarity and to keep things consistent:
* --limit metavar should be  to indicate what is being counted
* --marker metavar should be  or  to indicate the
  type of value being specified
* <*-ip-address> metavars should be just  as there is no difference
  in format between fixed and floating IPs
* Move all occurances of '(name or ID)' to end of help text

Change-Id: I2c31746ed6ded3845244e03e57d809f8bc0e6b9d

Enable to add/remove port to/from a server

2017-04-03T18:19:40+00:00

This change enables to add/remove a specific port to/from a server using
the new commands:

 openstack server add port  
 openstack server remove port  

Closes-Bug: #1678137
Change-Id: I6ee57df089235ccc1fb9d38316bd484956b1134d