
See the
ux-tenant-remove
manual page for more information on this command.
Administering Existing Tenant VMs
Once created, a tenant VM can be administered like any other Linux system using standard Linux administrative
tools. Changes to a tenant VM's configuration on the SMW do not propagate to the deployed tenant VM, so they
must either be managed locally on the tenant VM administratively, or re-instantiated by destroying and re-
deploying the tenant VM. It is worth noting that the tenant VM itself has limited storage resources, with the
expectation that user data will be stored either within Urika-GX (Lustre or HDFS) or within user home directories.
As long as user data are not stored on the tenant VM, and administrators keep careful track of local customization
of existing tenant VMs, then it is fairly straightforward to re-deploy (using
ux-tenant-remove
and
ux-tenant-
create
) a tenant that becomes damaged or badly out of date.
7.5.3
Tenant Virtual Machine States
A tenant VM's state can be retrieved via the
urika-tenant-status
command. The list of states that a tenant
VM can be in at a given time include:
Table 20. Tenant States
State
Description
notfound
The tenant is configured but has not been created
shutoff
The tenant has been created but is currently not running
running
The tenant is currently running
inshutdown
The tenant is currently shutting down. This is a transient state
crashed
The tenant VM has failed due to a software error of some kind
State Transitions
A tenant VM can go from one state to another. The following tables depicts the list of possible state transitions:
Table 21. Tenant VM State Transitions
From
To
Command Used for performing the transition /
Due to
notfound
running
ux-tenant-create
. The
ux-tenant-create
command initially creates the VM and starts the
HDFS Name nodes. The
ux-tenant-stop
stops the VM but does not stop the Name nodes
because they do not use a significant amount of
resources. It is safer not to stop and start the
Name nodes.
running
inshutdown
ux-tenant-stop
running
notfound
ux-tenant-remove
--force
. The
--force
option enables removing a tenant that is currently
running.
Security
S3016
195