7. Verify that the li/jointfilesconvert/47223/bguestfs and li/jointfilesconvert/47223/bguestfs-tools packages were installed:
yum list | grep li/jointfilesconvert/47223/bguestfs*
Configuring CloudSystem compute node network settings
Prerequisites
• RHEL 6.4 is installed on the compute node.
• Dependency packages are installed on the compute node. See Creating a local YUM repository
and validating dependencies (page 99)
• Checklist of requirements is completed for the compute node.
Procedure 53 Configuring CloudSystem compute settings
1. Log in to the compute node.
2. Configure the network device where the Cloud Management Network is plumbed.
In the example below, ethM represents the network device:
DEVICE="ethM"
BOOTPROTO="dhcp"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="Ethernet"
PEERDNS="no"
PERSISTENT_DHCLIENT=1
DHCP_HOSTNAME=<short_hostname_of_your_compute_node>
The DHCP_HOSTNAME should be the short host name of the compute node. On the Foundation
base appliance, the DHCP server uses this value to determine the base host name to prepend
to the hpiscmgmt.local domain to get the fully-qualified domain name for the base
appliance.
3. Bring up the Cloud Management Network:
ifdown ethM
ifup ethM
4. Configure the network device where the Data Center Management Network is plumbed.
In the example below, ethN represents the network device.
DEVICE=ethN
...
IPADDR=<your management network IP address>
NETMASK=<your management network NETMASK>
NM_CONTROLLED=”no”
PEERDNS=”no”
PERSISTENT_DHCLIENT=1
BOOTPROTO=”static”
ONBOOT=”yes”
...
Save the change and close the file.
5. Bring up the Data Center Management Network:
ifdown ethN
ifup ethN
6. Configure the network device where the Cloud Data Trunk is plumbed.
In the example below, ethP and ethQ represent the network device.
DEVICE=[eth-P] or [eth-Q]
...
NM_CONTROLLED=”no”
PEERDNS=”no”
ONBOOT=”yes”
Creating KVM compute nodes 101
Comentários a estes Manuais