In this diagram, each tenant has a sub-directory under
/mnt/lustre
that is named for the tenant. This sub-
directory is specifically exported to the named tenant across the virtual host (VHOST) network on the node
where the tenant VM is installed (
host-os
). When a new tenant VM is created, a new sub-directory and
export is created for that tenant. The configuration settings of interest include:
○
UXTENANT_MOUNT_SERVER
is set to
host-os
which is a specially recognized name for the node on
which the tenant is installed. Unlike other host-names or IP addresses,
host-os
is specifically
interpreted by Urika-GX tenant management to refer to the host where the VM is defined so that
operations can be done locally on that server to set up access to the NFS export across the virtual host
(VHOST) network on that node.
○
UXTENANT_MOUNT_TENANT_ISOLATED
is set to
YES
in this case, indicating that the above directory
structure will be used. This causes the mount point configuration in
/etc/fstab
on the tenant VM to be
set up with
/mnt/lustre/
tenant_name
, where
/mnt/lustre
is the value configured for the mount
point in
UXTENANT_MOUNT_MOUNT_POINT
and
tenant_name
is the name of the tenant to which the
tenant VM belongs.
○
UXTENANT_MOUNT_EXPORT_CREATE
is set to
YES
in this case, indicating that, if the
path
/mnt/lustre/
tenant_name
does not already exist on the server, Urika-GX tenant management
will attempt to create it by logging into the server as root and creating the directory. By the same token, if
there is no entry in
/etc/exports
specifically exporting
/mnt/lustre/
tenant_name
to the tenant IP
address, the Urika-GX tenant management infrastructure will attempt to create one by logging into the
server as root and editing that file. This is useful for locally defined 'tenant isolated' mount points. If the
mount point is not locally defined, but it is required to be tenant isolated, create the directory and export it
to the tenant manually (or by some site defined procedure) prior to creating the tenant VM. In that case,
set this setting to
NO
but leave the
UXTENANT_MOUNT_TENANT_ISOLATED
setting set to
YES
and
leverage the naturally occurring tenant isolation on an external server.
●
Tenant Host Configuration Files - Tenant host configuration files, located
under
/etc/sysconfig/uxtenant/hosts
, can be used to configure nodes other than the
login1
or
login2
nodes to host tenant VMs. Following is an example for
login1
:
UXTENANT_HOST_VHOST_IP_HOST_ADDR=192.168.122.1
UXTENANT_HOST_HOSTNAME=login1
The specifics of this configuration are as follows:
○
UXTENANT_HOST_VHOST_IP_HOST_ADDR
is the IP address on the local virtual host (VHOST) network to
be used for the
host-os
address to contact the host OS node for the VM. This address is used in setting
up the VHOST network on the host node the first time a tenant is created there, and in configuring the
DHCP host entries used to give each tenant VM an IP address on the VHOST network as well. There is
no configuration of network mask, forwarding or DNS here, since the network mask is assumed to be
255.255.255.0
and no forwarding or DNS is done through the host OS node. The 24 bit prefix (in this
case
192.168.122
) should always use the
192.168. 32
bit prefix and should be unique both within all
other
192.168
. networks on Urika-GX and within all host configuration files on Urika-GX.
○
UXTENANT_HOST_HOSTNAME
is the name or IP address of the host node within the Urika-GX
management network. This allows naming a host configuration file differently from the host name it
actually refers to, in the unlikely event that this is needed. Generally, this should be the same as the name
of the host configuration file.
The information here is intended primarily to fill out the admin's understanding of the Urika-GX tenant
management configuration. In most cases,
login1
or
login2
will be sufficient and should be used.
Security
S3016
193
