UBUNTU LANDSCAPE DEDICATED SERVER (LDS)
The starting point for our lab is the following:
while on juju gui we will have that:
1 STEP – CREATE A NODE ON VMWARE ESX FOR LANDSCAPE CLIENT
As we’ve made for the node dedicated to Juju and Landscape Server we can replicate the same tasks also for this node in way to obtain a server where we’ll deploy a service and Landscape Client.
and then making all task our node will be in this status
2 STEP – CREATE A JUJU MODEL FOR OUR SERVER
Now we can either to create a new model or use the default, for our lab we’ve decided to create two different model, one for LANDSCAPE and the other one for OPENSTACK. To have that we’v to run the following commands:
$: juju add-model serverslab Added 'serverslab' model with credential 'richardsith' for user 'admin'
on Juju gui we’ll see that one added:
check our juju models:
$: juju models Controller: maaslab-controller Model Cloud/Region Status Machines Cores Access Last connection controller maaslab available 1 2 admin just now default maaslab available 0 - admin just now landscapelab maaslab available 1 2 admin just now serverslab maaslab available 0 - admin never connected
3 STEP – DEPLOY A SERVICE ON SERVER
We can deploy a service, in our case Apache 2, using the gui:
or via command line
$: juju deploy cs:apache2-21
After few second the charm will be deployed on node.
To know which IP address is used for Apache, we have to use juju status and see that:
$:juju status Model Controller Cloud/Region Version serverslab maaslab-controller maaslab 2.1.3 App Version Status Scale Charm Store Rev OS Notes apache2 unknown 1 apache2 jujucharms 21 ubuntu Unit Workload Agent Machine Public address Ports Message apache2/0* unknown idle 6 10.20.81.24 Machine State DNS Inst id Series AZ 6 started 10.20.81.24 dxawh4 xenial default
To check the result, using our browser and using that ip we’ll see our service runs right.
the first part is done see you to next one.
Disclaimer: All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.
“We learn from our mistakes”