
○
UXTENANT_TENANT_IP_ONBOOT
is a flag that indicates whether or not it is required to have the
externally facing IP address to be active on boot of the tenant VM. For normal operations, this should be
yes
but an admin may want to set it to
no
during pre-production testing.
○
UXTENANT_TENANT_IP_GATEWAY
is the gateway IP address for the public network for the tenant VM.
This should be the same as the gateway IP address for the host physical node.
○
UXTENANT_TENANT_IP_DNS1
is the IP address of the primary name server for the tenant VM.
○
UXTENANT_TENANT_IP_DNS2
is the IP address of the secondary name server for the tenant VM
○
UXTENANT_TENANT_IP_DOMAIN
is the DNS search domain for the tenant VM
○
UXTENANT_TENANT_MOUNTS
is a list of named mount point configurations to use with the tenant VM,
each one names a configuration file in the
/etc/sysconfig/uxtenant/mounts
directory.
○
UXTENANT_TENANT_HOST
is the name of the host node configuration for the host node on which the
admin wants the tenant VM to run. It names a configuration file in the
/etc/sysconfig/uxtenant/
hosts
directory. There are two default host configurations,
login1
and
login2
that come with the
Urika-GX tenant management package and are already installed on the system. In general, it will be
required to pick one of these without needing to configure a new host.
●
Tenant Mount Point Configuration Files - Notice the
UXTENANT_TENANT_MOUNTS
in this sample
configuration. This sets up NFS mount points for use by the tenant. In the sample configuration, there are two
sample mount point configurations,
home
and
lustre
, provided. Site specific ones can be added as needed.
The sample mount points can be found by looking in the configuration
files
/etc/sysconfig/uxtenant/mounts/home
and
/etc/sysconfig/uxtenant/mounts/lustre
respectively. The sample configuration assumes that the home directories being used are exported over the
management Ethernet from the SMW as home directories. It further assumes that the users' home directories
are all grouped together at the same level of the directory tree (e.g.
/home/users/
userName
) and that this
directory tree has already been created and exported globally, so there is nothing to be done to set up the
NFS export specifically for this tenant:
UXTENANT_MOUNT_MOUNT_POINT=/home
UXTENANT_MOUNT_TENANT_ISOLATED=NO
UXTENANT_MOUNT_TYPE=nfs
UXTENANT_MOUNT_SERVER=smw
UXTENANT_MOUNT_OPTIONS="rw"
UXTENANT_MOUNT_EXPORT_OPTIONS="rw,no_root_squash,anonuid=12796,anongid=12796"
UXTENANT_MOUNT_EXPORT_CREATE=NO
In the preceding code block:
○
UXTENANT_MOUNT_MOUNT_POINT
is the path on both the server and the client of the exported file
system where the home directories live. In this case, it is
/home
.
○
UXTENANT_MOUNT_TENANT_ISOLATED
is a flag indicating whether the mount point is structured in such
a way as to isolate users from different tenants from each other.
○
UXTENANT_MOUNT_TYPE
is the type of mount this is. The only supported type at this time is NFS. Do not
change this value.
○
UXTENANT_MOUNT_SERVER
is the IP address (either named or numeric) of the NFS server exporting this
mount point. If the server is not a local Urika-GX node, it is best to use a numeric address in case a DNS
outage causes Urika-GX to lose the ability to resolve the server name, which can cause NFS outages. If
Security
S3016
191