Quick Installation Guide
The design scenario of the Nano cloud platform is to work in a multi server node cluster, but it is also possible to deploy all modules on the same server or virtual machine to achieve the minimum verification deployment of All In One, and then gradually expand to a larger cluster.
The Nano platform provides an Installer installer for automated deployment. The latest version of Installer can be installed through Download on official website perhaps Github Publishing Page obtain.
The installer will choose the most appropriate configuration and make recommendations, For new users who install Nano for the first time, try not to adjust any parameters during installation, nor use address pool or storage pool If you need to adjust parameters, modify configuration or directly upgrade binary files, please operate after you are familiar with the product.
Please read before installation common problem and Quick Start Guide Be familiar with relevant concepts and processes before operation
Server Requirements
- At least one X86 server supporting virtualization or virtual machine with nested virtualization (Intel VT-x/AMD-v) turned on
- 2-core 4G memory 50GB disk and one network device
- The operating system uses CentOS 7 Minimal and the network can communicate normally. If there is a Raid/LVM, please complete the configuration before installing the Nano
Must read before installation<Very important>
- Try to install the Nano using Dell iDrac or IPMI remote management protocol instead of SSH, because the host network will be reconfigured during the installation process, and some device network cards will disconnect, causing installation failure
- Do not disable or stop the Firewalld and Selinux services. The Nano module will configure firewall rules and image file storage rules. Stopping the services will lead to abnormal network access or file permissions between modules
- By default, the path "/var/lib/libvirt/images" stores the virtual machine disk files, and the path "/opt/nano/core/data" stores the system image files. Therefore, by default, the Nano uses the disk space under the path/for allocation. Before installation, make sure that you allocate enough disk space to the path/.
- When the installer selects the network card, only select the network card that starts with "em" and supports multicast and is in the up state. Please check in advance before starting the installation to avoid failing to find the network device
- Avoid installing the qemu service before installing the Nano. Otherwise, the instance may fail to start because the pre installed qemu binding users are different
- Ensure the yum source is available. If the local offline rpm is unavailable during the installer installation process, it will switch to yum online installation
- After the platform installation is successful, first add a resource node to the default resource pool, then create an empty white cloud host and start it. Verify whether the installation is normal, and then try other functions.
- Address pool and storage pool are familiar functions. Once problems occur, troubleshooting is very complicated, and initial use is not recommended.
New Installation
Step 1 Download and install all modules
$wget https://nanos.cloud/files/nano_installer_1.3.1.tar.gz $tar zxfv nano_installer_1.3.1.tar.gz $cd nano_installer $./ installer
Enter "0,1,2" or "3" to install all modules on the current server When you first install the Nano, it is recommended that you use the default configuration recommended by the installer without modification. If you have more than one network card device, please select the network card device connected to the intranet in the prompt of the installer to install it.
For configuration details, refer to Quick Start Guide
Step 2 Start all services
After the module installation is completed, you need to start the module to provide services. The module is installed in the/opt/nano directory by default. Use the command to manually start all modules (assuming that all modules are installed on the same server), Note that the Core module must be started first 。
$cd /opt/nano/core $./ core start $cd ../ cell $./ cell start $ cd ../ frontend $./ frontend start
When the front end module is successfully started, a message like "192.168.6.3:5870" You can use Chrome or Firefox to open this address for platform management.
Step 3 Use the web portal management platform
When you open the Nano management page in the browser for the first time, you will be prompted to create an initial administrator. After success, you can log in to the platform.
After logging into the system, First, add a resource node to the computing resource pool, then create an empty white cloud host and start it to verify whether the system is successfully installed 。 If you succeed, you can begin to explore the rich functions provided by Nano.
You can also upload or build new CD images or disk images for rapid batch deployment of instances. For other detailed configuration options, please refer to Configuration Manual
upgrade installation
All modules of the Nano are compiled into binary executable files using go, without external library dependencies. The configuration and data file formats are generally backward compatible, without user intervention.
The Nano can be upgraded in two ways. Start the Installer and select "4" to automatically upgrade. The automatic upgrade will check the installed modules for replacement according to the installation path entered by the user, and automatically stop and restart the running modules. This is the recommended upgrade method.
When there is a problem with the automatic upgrade mode, you can choose to upgrade manually, just use "/ The module name stop "stops the running module file and replaces the executable file."/ Module name start "just restart the service.
The only exception is that the FrontEnd module also contains front-end page files. Therefore, in addition to replacing executable files, you need to manually copy the page and js script files from the resource directory in the release package to overwrite them.