2.35.13. hammer host interface
ホストのネットワークインターフェイスを表示および管理します。
Usage:
hammer host interface [OPTIONS] SUBCOMMAND [ARG] ...
Parameters:
SUBCOMMAND Subcommand
[ARG] ... Subcommand arguments
Subcommands:
create Create an interface on a host
delete, destroy Delete a host's interface
info, show Show an interface for host
list, index List all interfaces for host
update Update a host's interface
Options:
-h, --help Print help2.35.13.1. hammer host interface create
ホストにインターフェイスを作成します。
Usage:
hammer host interface create [OPTIONS]
Options:
--attached-devices ATTACHED_DEVICES Identifiers of attached interfaces, e.g. `['eth1',
'eth2']`. For bond interfaces those are the slaves. Only for bond
And bridges interfaces.
Comma separated list of values. Values containing comma should be quoted or escaped with backslash.
JSON is acceptable and preferred way for complex parameters
--attached-to ATTACHED_TO Identifier of the interface to which this interface belongs, e.g. eth1.
Only for virtual interfaces.
--bond-options BOND_OPTIONS Space separated options, e.g. miimon=100. Only for bond interfaces.
--compute-attributes COMPUTE_ATTRS Compute resource specific attributes
Comma-separated list of key=value.
JSON is acceptable and preferred way for complex parameters
--domain DOMAIN_NAME Domain name
--domain-id DOMAIN_ID Satellite domain ID of interface. Required for primary interfaces on
Managed hosts.
--execution EXECUTION Should this interface be used for remote execution?
One of true/false, yes/no, 1/0.
--host HOST_NAME Host name
--host-id HOST_ID ID or name of host
--identifier IDENTIFIER Device identifier, e.g. eth0 or eth1.1
--ip IP IPv4 address of interface
--ip6 IP6 IPv6 address of interface
--location LOCATION_NAME Set the current location context for the request
--location-id LOCATION_ID Set the current location context for the request
--location-title LOCATION_TITLE Set the current location context for the request
--mac MAC MAC address of interface. Required for managed interfaces on bare metal.
--managed MANAGED Should this interface be managed via DHCP and DNS capsule and should it be
Configured during provisioning?
One of true/false, yes/no, 1/0.
--mode MODE Bond mode of the interface, e.g. balance-rr. Only for bond interfaces.
Possible value(s): 'balance-rr', 'active-backup', 'balance-xor', 'broadcast', '802.3ad', 'balance-tlb', 'balance-alb'
--mtu MTU MTU, this attribute has precedence over the subnet MTU.
--name NAME Interface's DNS name
--organization ORGANIZATION_NAME Set the current organization context for the request
--organization-id ORGANIZATION_ID Set the current organization context for the request
--organization-title ORGANIZATION_TITLE Set the current organization context for the request
--password PASSWORD Only for BMC interfaces.
--primary Should this interface be used for constructing the FQDN of the host? Each managed hosts needs to have one primary interface
--provider PROVIDER Interface provider, e.g. IPMI. Only for BMC interfaces.
Possible value(s): 'IPMI', 'SSH'
--provision Should this interface be used for TFTP of PXELinux (or SSH for image-based hosts)? Each managed hosts needs to have one provision interface
--subnet SUBNET_NAME Subnet name
--subnet-id SUBNET_ID Satellite subnet ID of IPv4 interface
--subnet6-id SUBNET6_ID Satellite subnet ID of IPv6 interface
--tag TAG VLAN tag, this attribute has precedence over the subnet VLAN ID. Only for
Virtual interfaces.
--type TYPE Interface type, e.g. bmc. Default is interface
Possible value(s): 'interface', 'bmc', 'bond', 'bridge'
--username USERNAME Only for BMC interfaces.
--virtual VIRTUAL Alias or VLAN device
One of true/false, yes/no, 1/0.
-h, --help Print help