- For server you can use the file called abiCloud-0.8.0-PLATFORM-installer.bin
- For cloud nodes you have to download and install aim-0.8.0-ARCHITECTURE.tar.bz
Requirements
First of all is important to assure that you have the requirements detailed on this [page].
Supported platforms
If you want to show the supported platforms (OSs for server instalation and virtualization technologies) please click [here].
TIP: The installer downloads MySQL(if you choose to install it) and Tomcat. If you have the installers, you can create a directory named /opt/external (in GNU/Linux) or c:/external (in Windows), save the files mysql.tgz and tomcat.tgz (in GNU/Linux) or mysql.zip and tomcat.zip (in Windows) in this directory. For mysql download the version without the installer. The name of the files are IMPORTANT.
abiCloud Server Node installation
Instructions
The installer works in graphic and command line mode.
Step 1: Welcome page

Information screen. Press "next".
Step 2 : License Agreement

License agreement. AbiCloud have a MPL license for AbiCloud_server, AbiCloud_WS and other server components and CPAL for Flex interface
Step 3 : Installation path

Installation path. The directory where AbiCloud will be installed. Tomcat and MySQL (if you choose it) will be installed in this directory.
On windows we suggest to install in the $_USER_HOME folder.
TIP: Remember to select a folder with the correct user permissions
Step 4: Database Installation

Database type. If you choose "[AbiCloud:MySQL]" the database server will be installed. If you already have a [AbiCloud:MySQL] server, choose "none".
Step 5 ( only applicable if "none" was chosen in step 4)
Database configuration: You must create a database named kinton. One database user has to be able to write to this kinton database.

Step 6 : Internal IP selection

Add the private IP of the server machine in order to allow the internal connections between modules.
TIP: abiquo suggest doesn't use 127.0.0.1 if you want to work in a environment of multiple servers.
Step 7 : Final step

Step 8: Server customization
ONLY for Linux users:
After install abiCloud on the server, this computer needs some customization depending on your required virtualization technology
- Install NFS server and configure it to share a folder (by default /opt/vm_repository, if user decides to change it, please change the parameter.
- repositoryLocation on abi.config.xml on 'server' application).
- Edit /etc/exports and add the line: /opt/vm_repository *(rw,no_root_squash,subtree_check,insecure)
- Restart the NFS server.
- If you want to show the Google Maps on Infraestructure management section you have to change the KEY. For generate a key, please, follow the instructions on [google page|http://code.google.com/intl/en-US/apis/maps/] and copy the key on GOOGLE_MAPS_KEY parameter hosted on client-config.xml
If you decide to work with libvirt, please, follow the next steps:
- Add LD_LIBRARY_PATH variable to system with the reference to libvirt.so (jni) path (We propose you download here and compile for your platform).
ONLY for Windows users:
After install abiCloud on the server, this computer needs some customization depending on your required virtualization technology
- Install a NFS Server in your machine (you can follow this tutorial). Configure it to share a folder (/mnt/c/vm_repository if you followed the tutorial), if user decides to change it, please change the parameter.
- repositoryLocation on abi.config.xml on 'server' application).
- Edit /etc/exports and add the line: /mnt/c/vm_repository *(rw,no_root_squash,subtree_check,insecure) ('*' should be changed by something like 192.168.x.0/255.255.255.0 in some cases)
- Restart the NFS server.
- If you want to show the Google Maps on Infraestructure management section you have to change the KEY. For generate a key, please, follow the instructions on [google page|http://code.google.com/intl/en-US/apis/maps/] and copy the key on GOOGLE_MAPS_KEY parameter hosted on client-config.xml
- Go to $ABICLOUD_HOMEtomcat\webapps\am\WEB-INF\classes\conf and modify config.xml. Change the 'localRepositoryPath' property by 'C:/vm_repository'.
- Go to $ABICLOUD_HOMEtomcat\webapps\server\WEB-INF\classes\conf and modify config.xml. Change the 'repositoryLocation' property by 'C:/vm_repository'.
If you decide to work with libvirt, please, follow the next steps:
- Add LD_LIBRARY_PATH variable to system with the reference to libvirt.so (jni) path (We propose you download here and compile for your platform).
AbiCloud Cloud node installation
Instructions
Step 0: Install the desired hypervisor
This install process don't detail how to install virtualbox or libvirt, but user has to install the hypervisor technology in each clod node.
- For virtualbox (2.2.x) follow the user manual
- For libvirt (0.6.3 or better) + KVM or XEN follow this document.
Step 1 : AIM agent installation
Download, uncompress AIM and follow the [next steps].
Step 2: Network configuration
Network configuration on each node. Follow the [next steps].
Start and validation
Cloud server start
If all is OK you are ready to go to $ABICLOUD_HOME defined on Step3 and start the application with the run.sh or Run.bat file. You must run this commands from $ABICLOUD_HOME folder.
abiCloud-0.8.0 $ ./bin/run.sh
In the example, the application will be accessible from a browser via the URL: http://localhost:5050/client
For more details about the first steps with the application see the [Getting started] document.
You can stop AbiCloud anytime executing the stop script.
abiCloud-0.8.0 $ ./bin/stop.sh
Cloud node start
- Starts the hypervisor
- For virtualbox hypervisor you have to stop the authentication and start the web service facade with the abiquo user.
## Go to your Virtualbox Folder $VIRTUALBOX_HOME ## Disable virtualbox authentication su - abiquo -c "VBoxManage setproperty websrvauthlibrary null" ## Execute Web service facade su - abiquo -c "vboxwebsrv -t 0"
- For libvirt you have to start it in the standard way
/etc/init.d/libvirt start
- Starts the agents (If you did not do it in [AIM installation]
/etc/init.d/openwsmand start /etc/init.d/vboxmonitor start

