Installation Guide Standard
- Emerginov Enterprise installation guide
Emerginov Enterprise installation guide
Requirements
Please, before proceeding, be sure to have all requirements.
You also need a configured Domain Name.
And the most important thing is to have a well configured Firewall.
How-To Install
At least 4 virtual machines have to be installed in this order:
- gardien: it is the configuration repository server (a.k.a. Puppet Master), and the internal DNS
- routing: it is the public node, hiding the other servers
- content: this node hosts the emerginov web pages, subversion repository and web services
- dev(s): those nodes hosts the projects (apache and asterisk)
Depending on the scenario you choose for the gateway, you may also have a gateway virtual machine as well.
Install Gardien
Prepare your machine
First, be root:
Update your machine
apt-get upgrade
apt-get dist-upgrade
Eventually, reboot:
Add the emerginov launchpad repo:
add-apt-repository ppa:emerginovteam/emerginov
apt-get update
Install the emerginov-master package
The emerginov-master package contains some custom scripts to help you start with emerginov:
Grab emerginov source code
Grab emerginov source code from subversion repo with the emerginov-update command:
You'll be ask to continue because of No Emerginov files found, checkout needed.
Answer Yes by pressing y followed by enter
Initialise configuration files
The emerginov-init command will initialise the configuration files to reflect your installation of emerginov:
Answer all the questions. If you need help to answer the questions, you can Contact us.
Once done, the configuration files are stored in /etc/emerginov/.
These files are puppet files. Indeed, we use puppet to configure the whole emerginov platform.
Please, check at least that the emerginov.pp file is well configured before going further:
Start the installation using puppet
To ease the installation of emerginov, we wrote some script to use puppet with finger in the nose. These scripts are inside the emerginov-agent package:
The main script is called emerginov-apply. At first, it will try to connect to the puppet master you installed in previous section and then apply the whole configuration:
puppet cert sign gardien.emerginov.localnet
emerginov-apply
At this step, the console will throw a lot of information. At long as it's green or blue, it means that puppet is working fine.
When it becomes purple or yellow, it means that something went wrong. Please run emerginov-apply again:
Depending on your installation, it may happen that you still see some purple errors.
Before worrying a lot, please run emerginov-apply few times more to see if the error is still there.
If you still have some purple, do not hesitate to Contact us.
At the end, you must have run emerginov-apply at least 3 times.
Install Routing
Before going further, be sure that the Gardien is well installed (no purple or yellow errors).
Prepare your machine
First, be root:
Update your machine
apt-get upgrade
apt-get dist-upgrade
Eventually, reboot:
Add the emerginov launchpad repo:
add-apt-repository ppa:emerginovteam/emerginov
apt-get update
Start the installation using puppet
In the same way you did for Gardien, install the emerginov-agent package:
Run a first emerginov-apply to connect to the puppet master (which is on Gardien):
On Gardien machine, run the following commands to let puppet master accept the Routing machine:
puppet cert sign routing.emerginov.localnet
emerginov-nursery-auth.sh --create
Back on Routing machine, run again emerginov-apply twice:
# ...
# Wait for completion..
# ...
emerginov-apply
At the end, you must have run emerginov-apply at least 3 times.
Install Dev(s)
Before going further, be sure that the Gardien and Routing are well installed (no purple or yellow errors).
Prepare your machine
First, be root:
Update your machine
apt-get upgrade
apt-get dist-upgrade
Eventually, reboot:
Add the emerginov launchpad repo:
add-apt-repository ppa:emerginovteam/emerginov
apt-get update
Start the installation using puppet
In the same way you did for Routing, install the emerginov-agent package:
Run a first emerginov-apply to connect to the puppet master (which is on Gardien):
On Gardien machine, run the following commands to let puppet master accept the Dev machine:
puppet cert sign dev.emerginov.localnet
emerginov-nursery-auth.sh --create
Back on Dev machine, run again emerginov-apply twice:
# ...
# Wait for completion..
# ...
emerginov-apply
At the end, you must have run emerginov-apply at least 3 times.
Install Content
Before going further, be sure that the Gardien, Routing and Dev are well installed (no purple or yellow errors).
Prepare your machine
First, be root:
Update your machine
apt-get upgrade
apt-get dist-upgrade
Eventually, reboot:
Add the emerginov launchpad repo:
add-apt-repository ppa:emerginovteam/emerginov
apt-get update
Start the installation using puppet
In the same way you did for Dev, install the emerginov-agent package:
Run a first emerginov-apply to connect to the puppet master (which is on Gardien):
On Gardien machine, run the following commands to let puppet master accept the Content machine:
puppet cert sign content.emerginov.localnet
emerginov-nursery-auth.sh --create
Back on Content machine, run again emerginov-apply twice:
# ...
# Wait for completion..
# ...
emerginov-apply
At the end, you must have run emerginov-apply at least 3 times.
Finishing the installation
Gateway
You will need a gateway to add to your new emerginov platform some telecom connectors.
To do so, follow this guide: Gateway installation
Testing
To check that everything is working fine, please follow the Post Installation Testing Suite.