Skip to content

Latest commit

 

History

History
344 lines (240 loc) · 13.4 KB

README.md

File metadata and controls

344 lines (240 loc) · 13.4 KB

3-tier unit setup with Ansible

Overview

The purpose of this document is to explain explicitly how to construct Personium unit on 3-tier using Ansible. This ansible is checking the operation with Personium version 1.5.2 later and CentOS 7.2.

Server setup ✅

server configuration sample

Below are the server structure that we configured.

Servers Role MW default memory size (*1) AWS EC2 specs (*2)
Server 1 Bastion t2.micro
Server 2 Web nginx t2.micro
Server 3 AP,NFS,MQ tomcat(1280MB),memcached(1024MB*2),ActiveMQ 3328MB m3.medium
Server 4 ES Elasticsearch(3328MB) 3328MB m3.medium

(*1) : Required default memory size. Memory size of each MW configuration file could be modified

(*2) : Tested AWS EC2 instance specs

Alternatively, you can use HeatTemplate to create the infrastructure.
Heat Template Sample

File structure

File name Contents
/init_personium.yml yml file which should be executed by Ansible-playbook
/[group name].yml yml file to retrieve the variable of each group and execute its related tasks
/ansible.cfg Describes the required Settings for Ansible execution. (*Modification is not required)
/static_inventory/ This folder contains all the essential information of different environments
/static_inventory/hosts\*# Describes information of hosts (IP address, FQDN, group, User name, Private Key, etc.)
/group_vars/ Folder to organize files in order to perform various customization or tuning on servers
/group_vars/[group name].yml\*# Collections of values for each group, which requires to customize/tune the settings
/resource/ Folder to organize files which are necessary in task (*Modification is not required)
/resource/[groue name]/ Store the resources of each group
/tasks/ Folder to organize task
/tasks/[groue name]/ Store specific task for each group
/handlers/ Folder to organize handlers
/handlers/[group name]/ Store handler for each group

*# : Files required to modify according to the environment.

*[group name] : web, ap, nfs, es, mysql, bastion and common. All in all 7 groups. (Here common is not the server role. Common group is used to set some general functionalities on all the servers.)

File (key) handling Caution: ⚡

The following key file will be generated automatically during the Ansible execution. Please handle these keys carefully.

/personium/personium/conf/salt.key

/personium/personium/conf/token.key

Initial setup for Ansible ✅

  • Prerequisite:
    • All infrastructure is created
    • User account: sudo user
    • Ansible execution user account: sudo user
    • Ansible execution environment : Bastion server
    • Fixed global IP address is attached to the Web server
    • Fixed private IP of all the remote servers.

1: Configure DNS setting

See DNS Setup for per-cell URL

2: Log in Bastion Server

Log in Bastion Server.

3: Git clone Ansible

  • Using git client, clone the ansible repository (https://github.com/personium/ansible) to your local environment.
    * Please clone or download the zip file from the release branch.
    * Since the master branch may contain new features which are under testing and development, erroneous behavior may be expected.
    * From now on, we describe this 3-tier folder as $ansible.

4: Setup Ansible parameters

  • Edit the following files
    • Edit $ansible/static_inventory/hosts file and set the value of each parameter.
    • Check $ansible/group_vars/[group name].yml file. Re-set the parameter value, if server tuning is necessary.
      * Please refer to Ansible Settings Instruction file, for more details about each parameter.

5: Prepare Self-signed unit certificate and secret key

6: Configure the self-signed unit certificate and private key

  • Arrange certificate
    • Deploy the self-signed unit certificate and private key under $ansible/resource/ap/opt/x509/ folder with the following file names.

7: Prepare SSL certificate / private key

  • Prepare the SSL certificate and private key separately
    If you have a domain and can set it to DNS, you can use an official SSL certificate. Example of using Let's Encrypt.
  • Create and use self-signed SSL certificate when the official SSL certificate is not available. Example of using Self-sign.

8: Deploy SSL certificate / private key

  • Certificate deployment
    • Deploy the certificate under $ansible/resource/web/opt/nginx/conf/ folder
    $ansible/resource/web/opt/nginx/conf/
       - server.crt(SSL certificate)
       - server.key(private key)

* In the case of Self-signed SSL certificate, the above process is not required to follow.

9: Add DISK

  • Add the external disk to the servers below (*Following disk sizes are recommended). Note: It is required to add the external disk on the following path
Server Storage Path Mount Point Usage
ES 200GB /dev/xvdb /opt/es_data-log ES data
AP + NFS server 50GB /dev/xvdb /opt/ap_piolog PIO log
AP + NFS server 100GB /dev/xvdc /opt/nfs_webdav WebDav, event log

10: Generate SSH key

  • Setup the ssh keys (RSA key pair) to access other servers from bastion server as root user. Follow the steps below:
Step 1: Create the RSA Key Pair on the client machine (Bastion server)
  • The entire key generation process looks like as follows:
    $ ssh-keygen -t rsa
    Generating public/private rsa key pair.
    Enter file in which to save the key (~/.ssh/id_rsa):  (\* press enter to save the rsa key pair at ~/.ssh/id_rsa, otherwise specify the alternative path)
    Enter passphrase (empty for no passphrase):               (\* press enter to save the key without password)
    Enter same passphrase again:                              (\* press enter if no password added on passphrase)
    Your identification has been saved in ~/.ssh/id_rsa.
    Your public key has been saved in ~/.ssh/id_rsa.pub.

The public key will be placed in ~/.ssh/id_rsa.pub

The private key (identification) will be placed in ~/.ssh/id_rsa

Step 2: Put the public key to other remote servers. Follow the steps below:
  • Copy the public key from bastion server
    $ cat ~/.ssh/id_rsa.pub
    sample output)
    ------------------
    ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAxUTAHN8vxgp8w2tBeSYKLDvISg3LF9W/iiIQ5boQNPfHQkpXtbFAVmQ1uDMBf3bUOzQN0
    Hr+YnAtiV1D7mPjRdBapM7dzI3o4hcuy1Jk9o6J6ZY4SQosH23jOJJZhz0yLn/ACQ+aKeIu3DPj4Pw4C/BUfd+JlFGCRcr/OTjLmqtVer
    W70LLGSh1CwYr/b7uvKjxdzArxKlzsvCpGBU69Vn0g5+tUzOtvMEYRz1Jttn1gxrRpCqIUbtRbIlYEoNYpzt0hVBfOhNtfbBE8yb8Lw1A
    enBBP0WcBI7uGJpIdIhlPSIiOqyfG/XnSCVOWZCFGIc13CtOjHq3rabcdefg== user@ip-XX-XX-XX-XX
   ------------------
  • Add the public key of bastion server in ~/.ssh/authorized_keys of all target remote servers
    • Access to each remote server, and add the bastion server root public key in ~/.ssh/authorized_keys
  • Access to the remote server
    $ su -  (\* switch to the root user)
    $ vim ~/.ssh/authorized_keys  (\* Add the key below and save)
    -----------------
    ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAxUTAHN8vxgp8w2tBeSYKLDvISg3LF9W/iiIQ5boQNPfHQkpXtbFAVmQ1uDMBf3bUOzQN0
    Hr+YnAtiV1D7mPjRdBapM7dzI3o4hcuy1Jk9o6J6ZY4SQosH23jOJJZhz0yLn/ACQ+aKeIu3DPj4Pw4C/BUfd+JlFGCRcr/OTjLmqtVer
    W70LLGSh1CwYr/b7uvKjxdzArxKlzsvCpGBU69Vn0g5+tUzOtvMEYRz1Jttn1gxrRpCqIUbtRbIlYEoNYpzt0hVBfOhNtfbBE8yb8Lw1A
    enBBP0WcBI7uGJpIdIhlPSIiOqyfG/XnSCVOWZCFGIc13CtOjHq3rabcdefg== root@ip-XX-XX-XX-XX
    ------------------

  • Notes:

    1. vi command displays the contents of the file
    2. Press [i] to change the file to edit mode, and you will be able to copy the public key
    3. Paste the public key, copied from bastion server
    4. Press [Esc], then type [:wq!] to save the file

  • If the directory and the file are not available on remote servers, then create them first

    $ mkdir .ssh
    $ touch authorized_keys
  • Check the permission. Change if necessary
    $ ls -la ~/.ssh/authorized_keys
    -rw-------. 1 root root 952 Aug 27 02:41 ~/.ssh/authorized_keys
  • Change the permission if required
    $ chmod 600 ~/.ssh/authorized_keys
    $ ls -la ~/.ssh/authorized_keys
    -rw-------. 1 root root 952 Aug 27 02:41 ~/.ssh/authorized_keys
  • Check the permission. Change if necessary
    $ ls -la ~/
    drwx------.  2 root root 4096 Aug 27 02:41 .ssh
  • Change the permission if required
    $ chmod 700 ~/.ssh
    $ ls -la ~/
    drwx------.  2 root root 4096 Aug 27 02:41 .ssh
    $ exit
Step 3: SSH connection test (* Access to remote servers as root user form Bastion server using the private key)
- Access to Bastion server
    $ ssh -i ~/.ssh/id_rsa sudouser@[Private IP of remote server]  (\*ssh to remote servers as root user)

    $ exit (\* Exit from remote server, after confirming the successful access from bastion server)

Ansible configuration ✅

1: Install Ansible(Client server : Bastion server)

  • Add epel repository to Bastion server
    $ sudo yum install epel-release
    this ok [y/N]:  (\* type [y] and press enter)
  • Install Ansible
    $ sudo yum install ansible
    this ok [y/N]:  (\* type [y] and press enter)

2: Check the Ansible configuration file on client server (Bastion server)

  • Access to Bastion server and check the following Ansible setup files, if those are configured properly

    1. /hosts file (* Static inventory file) * Check the hosts file if anything is missing
      $ cat $ansible/static_inventory/hosts | grep "{"
  • If nothing shows, meaning all are configured
  1. /group_vars/[group name].yml file (* Group Variable files) * Check if all the yml files under group_vars are modified as required
      $ cat $ansible/group_vars/ap.yml
      $ cat $ansible/group_vars/bastion.yml
      $ cat $ansible/group_vars/common.yml
      $ cat $ansible/group_vars/es.yml
      $ cat $ansible/group_vars/nfs.yml
      $ cat $ansible/group_vars/web.yml

3: Execute Ansible

  • Access to the Bastion server and change to the Ansible directory
    $ cd $ansible
  • Execute Ansible
    $ date; ansible-playbook init_personium.yml ; date

* After few minutes-hours (varies on case by case) Ansible process will be done. (* Don't kill the process in between) Personium Unit will be created with the configured FQDN. Also will be accessible from web (ex: https://FQDN)

  • Confirm if Ansible executed properly
  $ egrep -B 3 -A 3 'failed:|error' $ansible/ansible.log

Check the Ansible log file, if it shows any error
If there is no error, please restart the constructed servers

4: Deployment testing on Bastion server

  • Execute the reachability testing tool
    $ sudo /bin/sh personium_regression.sh {{ FQDN of Web server }}
    [personium Version(default) RT OK]

* reachability testing is done, if it shows the same

For the developers convenience this document introduced the procedure to construct Personium unit using Ansible. Hope developers will enjoy deploying Personium unit on any of their suitable environment. Please try Personium and let us know your feedback or comments for further betterment of Personium. Your feedback and comments will be highly appreciated.

Update the server partially

After sever setup, there are times when you want to partially update the server.

For example, suppose you want to upgrade Nginx. At that time, you perform the following steps.

  1. Edit group_vars/web.yml to change the value of nginx_version
  2. Execute the playbook with --tags web option
  $ ansible-playbook --tags web init_personium.yml

Caution

If you edit a configuration file without going through the playbook, the modification will not be reflected. Please make all corrections through the playbooks or update manually after executing the playbooks.