Juju installation (release 0): Difference between revisions

From OSM Public Wiki
Jump to: navigation, search
No edit summary
 
(49 intermediate revisions by 3 users not shown)
Line 1: Line 1:
This document intent is to provide a practical way to reproduce the environment in Telefonica lab (TEF) aim at running the demo scenario for Mobile World Congress 2016. It is not an explanation or long term recommendation for using juju.
__TOC__


Initially setup 2 Ubuntu 14.04 LTS VMs with 4 vcpu, 4G RAM and 40GB drive. Create user juju in sudo group (usermod -a -G sudo juju)
=VM creation=
* Juju Server and Client (single VM)
**Minimum Requirements:
*** 4 vCPU
*** 4GB RAM
*** 40GB disk
*Base image: ubuntu-14.04.4-server-amd64


#The first is juju client VM (or juju jump server) (10.95.172.10). This VM is only required for manual execution of juju commands and charms debugging.
In case you want to install them in separate VMs, the minimum requirements are:
#The second is juju server VM (10.95.172.193). This VM will receive commands from Juju client VM when doing manual testing, or directly from Rift.io Launchpad VM in OSM context. Juju charms will be deployed as containers in this VM
* Juju Server:
** 4 vCPU
** 4GB RAM
** 40GB disk
* Juju Client:
** 2 vCPU
** 2GB RAM
** 20GB disk
*Base image in both cases: ubuntu-14.04.4-server-amd64


On juju client VM:
=Installing required packages and libraries=
<cl>
==Install Juju Server==
#Install juju:
*Create a user (e.g. user osm, pwd osm) and add it to the sudo group.
<pre>sudo apt-get install python-software-properties
sudo adduser osm
sudo add-apt-repository ppa:juju/stable
usermod -a -G sudo osm
sudo apt-get update
*Install packages for Juju Server
sudo apt-get install juju-quickstart juju-core</pre>
sudo apt-get install systemd-services lxc ssh
#Configure the connection to juju server VM in manual provider mode: ensure to have the following in your ~/.juju/environements.yaml
*If required, edit the file '''/etc/default/lxc-net''' to change the lxc network addressing. This is only needed if there is overlapping with other network interfaces used by the Juju Server.
environments:
For instance, in order to use the subnet 10.0.3.0/24, you could make the following configuration:
  mwc16manual:
    admin-secret: nfvjuju
    bootstrap-host: 10.95.172.193
    bootstrap-user: juju
    default-series: trusty
    type: manual
*Execute the following commands to connect both VMs:
juju switch mwc16manual
juju bootstrap --upload-tools
*As a nice optional add-on deploy juju-gui to graphically monitor juju status
juju deploy juju-gui --to 0
Once done you can connect via https to the IP of the server.
 
</cl>
 
 
More information on the bootstrap process is available here: https://jujucharms.com/docs/1.25/config-manual
 
On juju server VM:
*Configure it to access the management networks of openvim and openstack
*Change the default lxc networks, as in the lab setup the default lxc network (10.0.3.0/24):
sudo apt-get install systemd-services lxc
 
Edit /etc/default/lxc-net to have something like :
  LXC_BRIDGE="lxcbr0"  
  LXC_BRIDGE="lxcbr0"  
  LXC_ADDR="10.1.3.1"
  LXC_ADDR="10.0.3.1"
  LXC_NETMASK="255.255.255.0"
  LXC_NETMASK="255.255.255.0"
  LXC_NETWORK="10.1.3.0/24"
  LXC_NETWORK="10.0.3.0/24"
  LXC_DHCP_RANGE="10.1.3.2,10.1.3.254"
  LXC_DHCP_RANGE="10.0.3.2,10.0.3.254"
LXC_DHCP_MAX="253"


==Install Juju Client==
*Install packages for Juju Client
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:juju/stable
sudo apt-get update
sudo apt-get install juju juju-local juju-quickstart charm-tools squid-deb-proxy


=Configuration=
*In the Juju client, edit '''/etc/squid-deb-proxy/mirror-dstdomain.acl''' to add the following lines:
# launchpad personal package archives (disabled by default)
ppa.launchpad.net
private-ppa.launchpad.net


*In the Juju client, restart squid-deb-proxy:
sudo service squid-deb-proxy restart


*In the Juju client, create file '''${HOME}/.juju/environments.yaml''' using the appropriate IP address for the bootstrap host (Juju server's IP address) and for the squid proxy (either the IP address of the LXC bridge - 10.0.3.1 - in case of a single-VM installation, or the IP address of the Juju client in case server and client are running in different VMs).
default: osm0-manual
environments:
  osm0-manual:
    admin-secret: osm
    bootstrap-host: <jujuserver-ip>
    bootstrap-user: osm
    default-series: trusty
    type: manual
    enable-os-refresh-update: False
    enable-os-upgrade: False
    apt-http-proxy: http://<proxy-ip>:8000
    apt-https-proxy: http://<proxy-ip>:8000
*From Juju client, bootstrap the environment:
juju bootstrap -v    # -v so you can see what's going on
*From Juju client, test the environment deploying juju-gui:
juju deploy juju-gui --to 0
*Access juju-gui through the web browser (https://<jujuserver-ip> user:admin, pwd:osm)
*Additional commands:
juju debug-log        # open this in another terminal or tab, so you can see what juju is doing while you type other commands
juju status          # provides the status. When no charms have been launched, you should see an output like below:
  environment: osm0-manual
  machines:
    "0":
      agent-state: started
      agent-version: 1.25.5
      dns-name: 10.11.12.13
      instance-id: 'manual:'
      series: trusty
      hardware: arch=amd64 cpu-cores=4 mem=3953M
      state-server-member-status: has-vote
  services: {}
juju status --format=tabular
[Services]
NAME      STATUS  EXPOSED CHARM
juju-gui  unknown false  cs:trusty/juju-gui-54
[Units]
ID        WORKLOAD-STATE AGENT-STATE VERSION MACHINE PORTS          PUBLIC-ADDRESS MESSAGE
juju-gui/0 unknown        idle        1.25.5  0      80/tcp,443/tcp 10.11.12.13
[Machines]
ID        STATE  VERSION DNS          INS-ID  SERIES HARDWARE
0          started 1.25.5  10.11.12.13  manual: trusty arch=amd64 cpu-cores=4 mem=3953M


More about using juju : https://github.com/juju/cheatsheet  
*More about using juju: https://github.com/juju/cheatsheet
 
Charms for MWC :
 
Get the charms (do once)
Let’s create a local repo of charms for convenience:
● mkdir -p ~/mwc16charms/trusty
● cd ~/mwc16charms/trusty
● git clone git@github.com:6WIND/LinuxPE.git vpe-router
● git clone -b clearwater-aio-proxy https://github.com/Metaswitch/clearwater-juju.git
● cp -rf clearwater-juju/charms/trusty/clearwater-aio-proxy/ .
 
To deploy
● cd ~/mwc16charms/
● juju deploy local:trusty/vpe-router --to lxc:0 vpe1
● juju deploy local:trusty/vpe-router --to lxc:0 vpe2
● juju deploy local:trusty/vpe-router --to lxc:0 vpe3
● juju deploy local:trusty/clearwater-aio-proxy --to lxc:0 ims-a
● juju deploy local:trusty/clearwater-aio-proxy --to lxc:0 ims-b
 
You can then configure/run actions on them.


Using the API:
{{Feedback}}
● juju api-endpoints
Will give you the IP:Port to connect the juju client API code to.

Latest revision as of 09:09, 22 June 2016

VM creation

  • Juju Server and Client (single VM)
    • Minimum Requirements:
      • 4 vCPU
      • 4GB RAM
      • 40GB disk
  • Base image: ubuntu-14.04.4-server-amd64

In case you want to install them in separate VMs, the minimum requirements are:

  • Juju Server:
    • 4 vCPU
    • 4GB RAM
    • 40GB disk
  • Juju Client:
    • 2 vCPU
    • 2GB RAM
    • 20GB disk
  • Base image in both cases: ubuntu-14.04.4-server-amd64

Installing required packages and libraries

Install Juju Server

  • Create a user (e.g. user osm, pwd osm) and add it to the sudo group.
sudo adduser osm
usermod -a -G sudo osm
  • Install packages for Juju Server
sudo apt-get install systemd-services lxc ssh
  • If required, edit the file /etc/default/lxc-net to change the lxc network addressing. This is only needed if there is overlapping with other network interfaces used by the Juju Server.

For instance, in order to use the subnet 10.0.3.0/24, you could make the following configuration: 

LXC_BRIDGE="lxcbr0" 
LXC_ADDR="10.0.3.1"
LXC_NETMASK="255.255.255.0"
LXC_NETWORK="10.0.3.0/24"
LXC_DHCP_RANGE="10.0.3.2,10.0.3.254"
LXC_DHCP_MAX="253"

Install Juju Client

  • Install packages for Juju Client
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:juju/stable
sudo apt-get update
sudo apt-get install juju juju-local juju-quickstart charm-tools squid-deb-proxy

Configuration

  • In the Juju client, edit /etc/squid-deb-proxy/mirror-dstdomain.acl to add the following lines:
# launchpad personal package archives (disabled by default)
ppa.launchpad.net
private-ppa.launchpad.net
  • In the Juju client, restart squid-deb-proxy:
sudo service squid-deb-proxy restart
  • In the Juju client, create file ${HOME}/.juju/environments.yaml using the appropriate IP address for the bootstrap host (Juju server's IP address) and for the squid proxy (either the IP address of the LXC bridge - 10.0.3.1 - in case of a single-VM installation, or the IP address of the Juju client in case server and client are running in different VMs).
default: osm0-manual
environments:
  osm0-manual:
    admin-secret: osm
    bootstrap-host: <jujuserver-ip>
    bootstrap-user: osm
    default-series: trusty
    type: manual
    enable-os-refresh-update: False
    enable-os-upgrade: False
    apt-http-proxy: http://<proxy-ip>:8000
    apt-https-proxy: http://<proxy-ip>:8000
  • From Juju client, bootstrap the environment:
juju bootstrap -v     # -v so you can see what's going on
  • From Juju client, test the environment deploying juju-gui:
juju deploy juju-gui --to 0
  • Access juju-gui through the web browser (https://<jujuserver-ip> user:admin, pwd:osm)
  • Additional commands:
juju debug-log        # open this in another terminal or tab, so you can see what juju is doing while you type other commands
juju status           # provides the status. When no charms have been launched, you should see an output like below:
 environment: osm0-manual
 machines:
   "0":
     agent-state: started
     agent-version: 1.25.5
     dns-name: 10.11.12.13
     instance-id: 'manual:'
     series: trusty
     hardware: arch=amd64 cpu-cores=4 mem=3953M
     state-server-member-status: has-vote
 services: {}
juju status --format=tabular
[Services]
NAME       STATUS  EXPOSED CHARM
juju-gui   unknown false   cs:trusty/juju-gui-54

[Units]
ID         WORKLOAD-STATE AGENT-STATE VERSION MACHINE PORTS          PUBLIC-ADDRESS MESSAGE
juju-gui/0 unknown        idle        1.25.5  0       80/tcp,443/tcp 10.11.12.13

[Machines]
ID         STATE   VERSION DNS          INS-ID  SERIES HARDWARE
0          started 1.25.5  10.11.12.13  manual: trusty arch=amd64 cpu-cores=4 mem=3953M

Your feedback is most welcome!
You can send us your comments and questions to OSM_TECH@list.etsi.org
Or join the OpenSourceMANO Slack Workplace
See hereafter some best practices to report issues on OSM
Retrieved from "http:///wikipub/index.php?title=Juju_installation_(release_0)&oldid=650"