
All of these commands are bound to specific file system paths by the command whitelist to ensure that they
execute safely. The Spark and HDFS commands are all provided on the tenant VMs using a wrapper around the
utp-launch
command that is used to invoke commands through the Urika-GX tenant proxy, so users can use
these commands as though they were logged onto a physical node. The two additional commands are not
wrapped in this manner and need to be invoked using
utp-launch
as follows:
#
utp-launch env
#
utp-launch true
7.5.1
Configure a Bridge Port
Prerequisites
This procedure requires root privileges.
About this task
A bridge port needs to be configured before a tenant can be created
NOTE: The instructions provided in this procedure should be used as guidance only. Site specific
customizations/requirements are beyond the scope of this publication.
About Bridge Port 0 (Management Network)
The Urika-GX management network interface is
eth0
by default. The tenant management installation process
dynamically creates the
br0
interface and modifies/creates
the
/etc/sysconfig/network-scripts/
ifcfg-br0
|
ifcfg-eth0
files on the login nodes.
Examples of management configuration file contents before and after Urika-GX tenant management installation
are shown below:
●
Before UTM installation.
ifcfg-eth0
DEVICE=eth0
ONBOOT=yes
HWADDR=xx:xx:xx:xx:xx:xx
TYPE=Ethernet
BOOTPROTO=none
IPADDR=10.142.0.145
NETMASK=255.255.0.0
Note that
ifcfg-br0
does not exist in the preceding example.
●
After UTM installation:
ifcfg-eth0
NAME="eth0"
DEVICE="eth0"
HWADDR=xx:xx:xx:xx:xx:xx
ONBOOT=yes
BOOTPROTO=none
TYPE=Ethernet
NM_CONTROLLED=no
BRIDGE=br0
USERCTL=yes
Security
S3016
185