Preparing VM for Gluu Server Installation#
Thank you for your interest in the Gluu Server! This document will provide instructions for preparing your VM for a standard Gluu Server deployment. Once your servers are ready you can move on to the installation instructions.
Good luck with your deployment, and welcome to the community!
The Gluu Server Community Edition (CE) needs to be deployed on a server or VM with the following minimum requirements.
|CPU Unit||RAM||Disk Space||Processor Type|
If you plan on installing more than the default components (i.e. oxAuth, oxTrust, and LDAP), we recommend that your server or VM have at least 8GB of RAM.
Please only post installation issues to Gluu Support if all the above requirements are met!
Supported Operating Systems#
The Gluu Server should be deployed on a server or VM using one of the following operating systems:
- Ubuntu 14.04, 16.04
- CentOS 6.x, 7.x
- RHEL 6.x, 7.x
- Debian 8
Note: You can try installing Gluu on other versions or operating systems, but the above operating systems have been tested and confirmed to work. We will not support deployments on other operating systems.
The following ports are open to the Internet by default.
|80||tcp||Forwards to 443|
The Gluu Server requires setting the
file descriptors to 65k.
Follow these steps or research how to do this on your Linux platform.
- Add the following lines in the
* soft nofile 65536 * hard nofile 262144
- Add the following lines to
session required pam_limits.so
- Increase the file descriptor limit to 65535. The system file limit
is set in
It is recommended to check the file descriptor size before increasing, and if the file descriptor size more than the default and customized, it is the recommended to the use the higher file size. File descriptor size can be found using the below command.
# cat /proc/sys/fs/file-max
Please note command may vary depending on the OS flavor used.
echo 65535 > /proc/sys/fs/file-max**
- Use the
ulimitcommand to set the file descriptor limit to the hard limit specified in
** ulimit -n unlimited**
Centos by default will not accept more than the default maximum of 65535. You may get an error while performing the above command.
- Restart your system.
Amazon AWS instances provide a public and private IP address. While
/install/community-edition-setup/setup.py script, use the
Private IP address. Also, use a hostname other then the long default
hostname that Amazon provides. Update your DNS or hosts files accordingly.
Accessing the Gluu Server on Azure can be a little bit tricky because of the Public/Private IP. Azure assigns a new Public/Private IP addresses each time the server is started.
Setting up VM#
Log into Windows Azure Administrative Panel
Virtual Machinestab, and click
Create a Virtual Machinelink
From the menu, choose
Choose Ubuntu Server 14.04 LTS or CentOS 6.7. Remember to set selinux to permissive if you choose CentOS.
Provide a name for the VM in the
Virtual Machine Namefield and use
Select a server with at least 4GB RAM in the
Provide a username/password to connect via ssh and upload ssh certificate. Click
Create a new cloud service and select
Availability Setoption. * Endpoints Section: This is where port forwarding is set so that the internal IP address can be selectively reachable from the outside world. By default, only tcp /22 is there for ssh. The public ports for
https(tcp ports 80 and 443) have to be added and mapped to the same private ports. If the cloud mappings are flagged conflicting, proceed without setting them. Remember to set them after the creation of the VM. Then, click
Choose not to install
VM Agentand click the
tickbutton to finalize the VM.
Go to the
Dashboardtab of VM Management Panel and copy the
DNS Name. This is the name that is used to access the Gluu Server.
You should now be able to ssh to the server and proceed with the installation.
Linode Virtual Machines (VM) use a custom kernel which is not supported by the Gluu Server, therefore the kernel must be updated before the Gluu Server can be installed in a Linode VM. The following steps will guide you through kernel update in the Linode VM.
- Check for the current version of the kernel. If the output contains
-Linode, then proceed
# uname -a
- Run the following command to update the kernel:
# apt-get install linux-image-virtual grub2
grubfile in the
# vim /etc/default/grub
- Ensure that the following lines are present in the grub file
GRUB_TIMEOUT=10 GRUB_CMDLINE_LINUX="console=ttyS0,19200n8" GRUB_DISABLE_LINUX_UUID=true GRUB_SERIAL_COMMAND="serial --speed=19200 --unit=0 --word=8 --parity=no --stop=1"
- Finally run the following commands to update
# update-grub # reboot