Hello. Welcome to this presentation in which you see how to deploy an assembly, as a self
service user, with Oracle Enterprise Manager Cloud Control.
Before a self service user can deploy templates and assemblies, the self service administrator
has to prepare the software library, then prepare templates and assemblies that can
be published and shared with self service users.
When adequate resources are provided to self service users, they can then request servers
in the self service portal. The servers are deployed from templates and assemblies for
which the users have permission to access. Now, let's deploy an assembly....
In this session I'm logged in to the Oracle Enterprise Manager Cloud Control Self Service
Portal as a self service user. To start the assembly deployment process,
click Request Servers above the list of the 10 last requested servers.
The new server request sequence begins with the general page. Here, search for the assembly
by clicking the magnifying glass next to the source input.
The source software selection dialog box appears, and here, select the assembly named FMW Generic
WLS 13c. Click Select. The name appears in the source input, so click
next. The deployment configuration page provides
opportunities to change many of the server parameters. In this demonstration, the assembly
contains one VM as shown by the number of servers.
Other assemblies can contain more than one. So to work with any VM in the assembly, you
must first select it. Click the server item on the list, and deployment options appear.
For this deployment, check the box to Enable High Availability.
Note the root password and confirmation are already set. This is an option in the self
service portal preferences that has been set for this user.
Click the small triangle next to the Network label to see the default network configuration.
Note the backend network is set to 50_PVI, which is an interserver network in the virtualization
environment. Here, you can only edit the IP address for an individual NIC, and you cannot
change the backend network. To change the backend network, click the Configure
Networks link at the upper right corner of the page.
This self service user does not have network restrictions set by the self service administrator,
so the backend network can be changed. Configuration changes made here will apply to all VMs in
the assembly. Click on the magnifying glass next to the
50_PVI backend network. After the network list appears, click on the 52_PVI network,
then click Select. Now, click OK.
The 51_PVI network now shows up in the Backend Network column for the eth0 network interface.
However, the IP Assignment value is DHCP. We want to use a static IP address from a
network profile. While the network interface eth0 is selected,
click Edit, next to the pencil icon. The edit network interface card dialog appears,
and the new network assignment for 51_PVI is in place.
Click on the IP assignment menu, and select Network Profile. Grab the lower right corner
of the dialog box and stretch it down a small amount.
Click the small magnifying glass, then click the network profile named 51_PVI that appears
for the network. Click Select. Now, click OK
The IP Assignment now is set to static from profile, and the network profile name 51_PVI
appears in the interface configuration. The network profile provides the host name
and domain name. It also provides a fixed IP address from the range or list of addresses
in the network profile. Click the small triangle next to the Storage
label to see the default storage configuration. There is only one disk associated with the
server, and it's the system disk. To add another disk - and change the memory
and CPU configuration settings, click the Server Size menu and select Medium.
The Medium machine size applies 8GB of memory, 4 CPUs, and an additional disk of approximately
500 GB. We accept the current configuration on this
page and click Next. The schedule page appears, and the default
values are to start the server immediately, and maintain the server for about a year.
We retain these values and click Next. The review page appears with a summary of
all the settings. To see server details, you can click on the server name link on the list.
However, we are satisfied with this configuration, and click Finish to begin the deployment job.
The Self service portal home page appears with a confirmation message at the top. Dismiss
the message by clicking the small x in the upper right corner.
Select the latest request at the top of the 10 latest requests list and note that the
status is scheduled. Refresh the page by clicking the circular
arrow in the upper right corner. Now the status has changed to Executing.
After several minutes, refresh the page again and see that the status has changed to Successful
and the server now appears at the top of the list of the 10 last requested servers.
Click the server name to see server details. The server details page shows us that the
network profile has been invoked. The hostname is 51pvi-12, and the domain is 51pvi.com.
And the IP address is 51.0.0.12. Click the Server menu at the upper left corner
of the display, and select to Launch VNC console. The console window appears, and we set it
to full screen. Login as root, and provide the password. The
password for this server comes from the user preferences option.
Enter the command ip addr, and see that the IP address 50.0.0.12 has been configured for
the VM. And enter the cat command to display the interface configuration file for eth0.
The network interface is fully configured with a DNS server and gateway IP addresses,
netmask and other settings. You have seen deployment of a server from
an assembly, we added storage and invoked a network profile to configure the network
interface. This ends the presentation. Thank you for
watching.