
we have used domain scope arguments --project-domain, --user-domain and --group-domain in identity commands, for example, role add v3, to prevent resources conflict from same resource name existence. To keep with the style of identity commands, it's better to rename --domain to --project-domain. Closes-Bug: #1468988 Change-Id: Ic6ccb895cf9be4a3d5f0001525e3b80cd340da8b
2.1 KiB
network
Network v2
network create
Create new network
network create
os network create
[--project <project> [--project-domain <project-domain>]]
[--enable | --disable]
[--share | --no-share]
<name>
--project <project>
Owner's project (name or ID)
--project-domain <project-domain>
Domain the project belongs to (name or ID). This can be used in case collisions between project names exist.
--enable
Enable network (default)
--disable
Disable network
--share
Share the network between projects
--no-share
Do not share the network between projects
New network name
network delete
Delete network(s)
network delete
os network delete
<network> [<network> ...]
Network to delete (name or ID)
network list
List networks
network list
os network list
[--external]
[--dhcp <dhcp-id>]
[--long]
--external
List external networks
--dhcp <dhcp-id>
DHCP agent ID
--long
List additional fields in output
network set
Set network properties
network set
os network set
[--name <name>]
[--enable | --disable]
[--share | --no-share]
<network>
--name <name>
Set network name
--enable
Enable network
--disable
Disable network
--share
Share the network between projects
--no-share
Do not share the network between projects
Network to modify (name or ID)
network show
Display network details
network show
os network show
<network>
Network to display (name or ID)