“Ubuntu 16.04 LTS Landscape Server – part 3/8”

ubuntu-16-04-lts

For more informations about Landscape we can view this link:

https://jujucharms.com/https://landscape.canonical.com/

or we can view this video

UBUNTU LANDSCAPE DEDICATED SERVER (LDS)

1 STEP – CREATE A NODE ON VMWARE ESX FOR LANDSCAPE SERVER

As we’ve made for the node dedicated to Juju we can replicate the same tasks also for this node in way to obtain that

Screen Shot 2017-05-26 at 17.30.59.png

and then

2 STEP – CREATE A JUJU MODEL FOR LANDSCAPE 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 landscapelab
Added 'landscapelab' 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         0      -  admin   never connected

on Maas our node is in this situation

Screen Shot 2017-05-26 at 17.36.08.png

3 STEP – DEPLOY LANDSCAPE SERVER

We can make this task using the juju cli or via juju gui:

via cli

$: juju deploy landscape-dense-maas

via gui

Screen Shot 2017-06-29 at 16.22.17.png

After few second the charm will be deployed on node and the situation on MAAS will changed, the node passes from Ready to Deployed, as reported here:

Screen Shot 2017-05-26 at 18.18.10

This task will take a long time but at the end, our Ubuntu Landscape will be deployed. To know which IP address is used for its own dashboard, we have to use juju status and see haproxy

$:juju status
Model         Controller          Cloud/Region  Version
landscapelab  maaslab-controller  maaslab       2.0.2
App               Version  Status   Scale  Charm             Store       Rev  OS      Notes
haproxy                    unknown      1  haproxy           jujucharms   41  ubuntu  exposed
landscape-server           active       1  landscape-server  jujucharms   21  ubuntu 
postgresql                 active       1  postgresql        jujucharms  101  ubuntu 
rabbitmq-server            active       1  rabbitmq-server   jujucharms    5  ubuntu 
Unit                 Workload  Agent      Machine  Public address  Ports           Message
haproxy/0*           unknown   idle       0/lxd/0  10.20.81.4      80/tcp,443/tcp 
landscape-server/0*  active    idle       0/lxd/1  10.20.81.5                      
postgresql/0*        active    executing  0/lxd/2  10.20.81.6      5432/tcp        (update-status) Live master (9.5.6)
rabbitmq-server/0*   active    idle       0/lxd/3  10.20.81.3      5672/tcp        Unit is ready
Machine  State    DNS         Inst id              Series  AZ
0        started  10.20.81.2  twrpdq               xenial  default
0/lxd/0  started  10.20.81.3  juju-a9da94-0-lxd-0  xenial 
0/lxd/1  started  10.20.81.4  juju-a9da94-0-lxd-1  xenial 
0/lxd/2  started  10.20.81.5  juju-a9da94-0-lxd-2  xenial 
0/lxd/3  started  10.20.81.6  juju-a9da94-0-lxd-3  xenial 
Relation     Provides          Consumes          Type
peer         haproxy           haproxy           peer
website      haproxy           landscape-server  regular
db-admin     landscape-server  postgresql        regular
amqp         landscape-server  rabbitmq-server   regular
replication  postgresql        postgresql        peer
cluster      rabbitmq-server   rabbitmq-server   peer

at the end its own gui will be that

Screen Shot 2017-05-26 at 18.22.51.png

the third part is done see you to next part.

<- part 2/8 . part 4/8 ->


“cya to the next 1…. Njoy !”
bye dakj

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”

Advertisements