Prepare a Linux Server

Linux Distributions


To deploy a Nebula system, you need to prepare a Linux server. Nebula can be deployed on the following Linux distributions:
  • Alma Linux-9
  • Debian-12
  • Rocky Linux-9

Server Configuration


The server must meet the following minimum requirements for deploying the Nebula System:

  • Processor: 64-bit Intel or AMD with at least 4 CPU cores
  • RAM: 16 GB
  • Disk Space: 150 GB
The server can be a physical bare-metal machine, a virtual server, or a cloud server instance with internet access to the Linux distribution repositories. While these are the minimum specifications necessary for Nebula to function effectively as a small cloud environment, there are no upper limits on the number of CPU sockets, RAM, or disk capacity.


Linux Installation


One of the listed Linux distributions must be installed with the minimal server option, without any extra packages, and the following configurations must be set:

  • Partitioning
    You can partition the disk as you prefer, but ensure that the /var volume is the largest partition, as /var/node will serve as the root of the Sky Node storage system.

  • SSH Server
    If the openssh-server package is not included in the base installation of your Linux distribution, you can install it using the following command:
    • Debian Linux
      apt install openssh-server -y

    • RHEL-based distributions
      dnf install openssh-server -y

  • Enable root user
    The Nebula deployment requires that the root user be enabled and allowed to log in with a password. In the /etc/ssh/sshd_config file, ensure that the PermitRootLogin directive is set to yes.

  • Change SSH Port to 2318
    In the /etc/ssh/sshd_config file, change the # Port 22 directive to Port 2318.

  • Disable SELinux
    For RHEL-based Linux distributions, modify the /etc/selinux/config file by changing the SELINUX=enforcing directive to SELINUX=disabled.

  • Remove firewalld
    For RHEL-based Linux distributions, remove the firewalld service using the following command:
      dnf remove firewalld -y

  • Network Interfaces
    Your server should have a primary static IP address, which can be a public IP if you're using cloud machines. If you have two network interfaces, you can either bond them into one for failover protection or assign a second static private IP address to be used as a "Motion IP" for data transfers. The Nebula system will use the "Motion IP" for cloning and migration tasks to reduce reliance on the public IP. Please refer to your Linux distribution's documentation for detailed information on configuring and managing network devices.

  • XVM Storage Check
    If you plan to use an NFS mount for XVM Storage separation, ensure that your server can resolve the hostname or ping the IP address of the NFS server.

  • Nebula Image Repository Check
    Ensure that your server can access the repo_address specified in your Nexus configuration to retrieve Nebula images via HTTPS. To verify connectivity, confirm that your server can resolve or ping the repository server.

  • Linux Repository Check
    Your Linux machine must be configured to use installation commands and download packages from the Linux distribution repositories. To verify this, execute the following command:
    • Debian Linux
      apt update && apt upgrade -y

    • RHEL-based distributions
      dnf update -y

Finally reboot once.

At this point, your Linux server is prepared to be added to the inventory of Nexus, and Nebula can be deployed. However, if you intend to add Nvidia vGPU or Nested GPU capabilities, this is also the stage at which you need to install the Nvidia driver and configure the GPU device into multiple mdev (mediated device) virtual devices.

This involves:

  1. Installing the Nvidia Driver: Ensure you have the appropriate Nvidia driver for your GPU model and Linux distribution. Follow Nvidia's installation guide for the driver version that matches your GPU.

  2. For Nvidia vGPU: Creating the /nvidia/vgpu.sh mdev partitioning script, which also functions as a vGPU profile list for the Nexus application.

  3. For Nested GPU: Installing additonal packages to enable Nested GPU for conatiners.
By completing these steps, your server will be fully equipped to support Nvidia vGPU technology, allowing for enhanced graphical processing capabilities in a virtualized environment. For more information about enabling and configuring vGPU please read the document: GPU for Instances

Please continue to the next step: Deploy Nebula

We utilize xcware specifically for our external CAD/CAE workforce needs. Our vGPU Workstations outperform our previously used VMware Horizon on the same hardware. More importantly, it is now easier to onboard and scalable for every project.

— Mark K.
IT-Manager @ Bielomatik

I rely on xcware for crafting and implementing solutions for my clients due to its scalability and quick setup time for projects. 8 out of 10 customers remain with the initial xcware project setup, streamlining my delivery process.

— Thomas B.
Cloud Solutions Architect

We have successfully migrated 500+ servers and desktops from VMware to xcware. We extend our gratitude to the xcware Consulting Team for delivering exceptional work.

— Franco O.
IT Manager @ SportSA

We were pleasantly surprised by how effortlessly we could construct our Big Data platform and extend it to various production lines across the globe.

— Simone C.
Big Data Engineer @ UBX

As a developer specializing in native cloud solutions, I am delighted that xcware is available for free for developers like me. This allows me to enhance my cloud skills and expand my expertise.

— Sindra L.
Cloud Engineer

My favorite is the Flow-fx engine and the API. With Nexus Flow-fx, you can automate everything, and I mean everything! I manage over 150+ Linux servers fully automated.

— Mirco. W.
Linux Administrator @ S&P

xcware Strategic Partners