Quick Start Manual

The Nano design for a multi-server node cluster, but you can also install all modules on the same server or virtual machine as an All-In-One deployment, then extend to more servers later.

The Nano has an installer for automated deployment, get the latest version from the official website or on Github.

For new users, it highly recommends that don’t adjust configuration when installing the first time, the installer will choose appropriate parameters.

Follow below instructions building a single server Nano platform.

Read the FAQs and the manual first, make sure to familiar with the concepts and processes before operating.

Minimal System Requirements:

  • Virtualization enabled X86 servers, or nested virtualization enabled virtual machines(Intel VT-x/AMD-v)
  • 2 cores/4 GB memory/50 GB disk/1 network interface
  • CentOS 7 Minimal installed with network ready. If you have raid or LVM, please configure them before installing Nano.

Must Read Before Installation <Very Important>

  • Try to use Dell iDrac or IPMI to install Nano, Do not use SSH. Because the network devices will reconfigure during the installation, it may break the network connection on some systems and cause the installation to fail.
  • Do not disable or stop Firewalld and Selinux services. The Nano module will configure the rules of Firewalld and file storage. Stopping service will result in abnormal network communication or file access.
  • By default, the paths "/var/lib/libvirt/images" and "/opt/nano/core/data" store the files for instances and images. Make sure to allocate enough disk for the root mount point "/" before installation.
  • The Installer will choose an active interface with the prefix "em" that enables multicast and unicast. Please check all interfaces before installation.
  • Do not install QEMU before Nano, or you may encounter a permission denied error when starting an instance due to the default bound user of QEMU.
  • Make sure that the yum source is available. If the offline installation using local rpm fails, it will switch to the online yum repository.
  • After every module starts up successfully, add a cell node to the resource pool 'default' first, then create and start an empty instance to validate. Make sure the installation succeeds before try any other features.
  • It is strongly discouraging to use the address and storage pools for rookies. Cause the troubleshooting is very complex, only suitable for most experienced users.

New installation

step 1. download and install all modules.

$tar zxfv nano_installer_1.3.1.tar.gz
$cd nano_installer

For example, “2” for the Cell only, and "3" to install all modules in the current server. No need to change parameters configured by the installer when you install Nano in the first time. If you have multiple network interfaces, choose the one access internal network. See Quick Guide for more details.

step 2. start all services.

All modules installed at '/opt/nano/' in default. Start module manually, or configure to startup with the system. Must start Core module first.

$cd /opt/nano/core
$./core start
$cd ../cell
$./cell start
$ cd ../frontend
$./frontend start

When front-end module successfully started, it will give you a listen address likes"". Using Chrome or Firefox open this web portal to manage your newly installed Nano platform.

step 3. manage via front-end web portal.

The first time you open the Nano Web portal, you will be prompted to create an initial administrator.

After you log in, add a resource node to the resource pool first, then create and start an empty instance to verify the installation. If successful, you can begin to explore the rich features.

You can also upload or build new ISO or disk images for batch deployment of instances. For more details please read the manual

Upgrade installation

All modules of Nano are compiled binary without any external library dependency, and configuration and data file formats are usually backward compatible.

It highly recommends that executing the installer and selecting “4” to upgrade all modules automatically. The installer will check which module installed need to update, and stop and restart a running module automated.

When you have a problem with the automatic upgrade, you manually upgrade all modules.

All you need is stop a running module, replace the binary and restart. The only exception is that the FrontEnd module also contains resource files need to replace.