The primary purpose is to provide users with an environment for experimentation and quick testing, or even production use of the software, which for various reasons cannot be installed directly on CVT FI servers (for example, Anxur or Aisa).
- Cloud versus User view
- User context configuration
- I want to quickly create a pre-installed virtual machine
- Quotas and usage rules
- I want to install my operating system
The Stratus.FI cloud web interface can be found at the following URL:
Log in to the web interface by faculty login and faculty password (more about faculty account and password change) here ).
Cloud versus User view
The Stratus.FI web interface is available to users in two versions: a simpler cloud view that is set by default and described in I want to quickly create a virtual machine , and a more complex user view with left menu and multiple controls. You can switch between them by clicking on the user name and selecting the last item named Views . Compare - cloud view:
... a user view:
User context configuration
Preinstalled virtual machine images are configured to take some information from the user settings (SSH key, superuser password, ...). It is therefore necessary to set these parameters before creating the virtual machine. Sign in to web interface , click on the user name at the top right and select Settings from the menu:
If you do not already have one, create an SSH key for example on Aise:
ssh-keygen -b 4096 -t rsa
The secret key is saved to your file
$HOME/.ssh/id_rsa and public there to file
id_rsa.pub . When creating, you can enter a
passphrase that will be required each time an SSH key is used.
In the web interface in the user settings click on the Config section and then on the Add SSH Key item and copy the
public key - file content into the form box
Create an encrypted password for a virtual machine, for example, with the command
openssl passwd -1 on Aise or other Linux:
xnekdo@aisa$ openssl passwd -1 Password: correct horse battery staple Retype password: correct horse battery staple $1$t2DaE4vm$i8A...630 xnekdo@aisa$
In the user settings in the Stratus.FI web interface, at the bottom of the
Attributes section, add a new attribute named
CRYPTED_PASSWORD , value created above (string
$1$... ) and click to save
Windows VM password
To use a Windows virtual machine, you must add two additional attributes to your custom attributes:
WIN_USERNAME with user login name a
WIN_PASSWORD containing an
unencrypted login password. Here we recommend choosing a different password than you use on faculty systems.
Choose a non-trivial password, otherwise Windows may reject logging into the VM with too simple a password.
Overall, the contextual information that you set looks like this:
I want a pre-installed virtual machine
You can use the following procedure if you need to test something on an already installed machine (run / compile your software version, and so on) and don't want to waste time installing and configuring your operating system.
Configure the user context as described in the previous chapter .
Open it main page Stratus.FI (from the other Stratus.FI page, click on the Dashboard above).
Click on green on the left side of the page
Choose from a selection of preinstalled systems (such as CentOS 7) and click on the selected system.
Tip: if you just want to try Stratus.FI quickly, use the pre-installed ttylinux minidistribution system. There is even no need to configure the context here: the superuser password is fixed and is displayed on the system console.
On the left side of the page, fill in the name of the virtual machine you are creating (for example, Test CentOS ) and right-click on Create green.
Wait for the virtual machine name you just created to have a green square instead of orange (you can refresh the view with the two arrows icon in the circle shown at the top right).
For example, once the virtual machine is active, you can try SSH login to the IP address displayed on the created virtual machine from the internal FI network (if the template uses SSH contextualization, it has an SSH server and an IP address). You can reach the machine console by clicking on its title and then on the bottom left of the blue terminal icon. You can log in as root with a previously entered password.
For newly instantiated machines, we recommend that you update your packages, especially if you plan to use the machine for a long time and restart the machine for their full application.
Newly created virtual machines have a NATed private IPv4 and a public IPv6 address. No need to use HTTP proxy cache to access public IPv4 Internet. You can read more about the technical solution in our blog post in ISe.
Quotas and usage rules
Our goal is to allow users to use even more computing resources in the short term (8 virtual machines). This will allow users to try distributed applications for example. Therefore, system resource quotas are set to use this way. For detailed information on quotas, see the Quotas section of the user interface.
Please be careful with other users: current hardware does not have the capacity to make every FI user permanently use all the resources up to their quota at a time. Therefore, the quota settings do not apply to permanently running virtual machines . If we detect virtual machines running longer than a day, or at most small days, we will stop these machines and cancel their drives later.
If you need a running test or production virtual machine for a longer period of time, or a number of computing resources in the short term, please contact your system administrator at
When using virtual machines, keep in mind that this is true as well Operating rules , in particular the prohibition of putting into service of publicly available network services without the prior approval of the CVT FI.
I want to install my operating system
In this chapter, we assume that the user has the interface switched to User view .
For your virtual machine, you will need the installation media (CD-ROM image), a system disk, and possibly a volatile disk for temporary data, such as swap space. To view the available disks, click Storage → Images in the left menu.
If you do not find the installation media of your chosen system among the available disks, you can create one:
- click on green [+] at the top of the page
- fill in the disk name (for example, CentOS 7.1511 netinst.iso ), possibly a description
- choose Read-only CD-ROM as the type and leave cephds in the datastore
- under Image location, select Upload and browse the ISO image on your computer
- create an image by clicking on the Green Create above.
The newly created disk should appear in the list of available disks. To save disk space, you can also offer other users the ISO image you have introduced: click on the appropriate line in the drive list and add Use right for Group and Other in the access rights on the right side of the page.
Similarly, create a system disk. On the Storage → Images page, click green [+] , fill in the name of the drive (for example, MyTest ), or a description. As type, select Generic DataBlock storage, storage cephds leave. Important: check this image is persistent checkbox . (Non persistent image: created instances using copy-on-write copy of the image. When canceling VM changes will be lost. Persistent image: it can only be used by one VM, the changes are retained even after the abolition of the VM.) Next, select the source Empty disk image and enter the size. To complete the action, click the green Create at the top of the page. After creating a disc, you can still click its row in the disc list and change the disc type from DATABLOCK to OS .
Virtual machine template
Stratus.FI (OpenNebula) uses templates to describe how a virtual machine should look. Primarily, templates are designed to efficiently create multiple identical virtual machines, for example, for load balancing. However, each virtual machine must have a template, even if we know in advance that it will only run in one instance.
In the left menu, select Templates → VMs to display a list of available templates (all of yours and others). Click green [+] to create a new template. On the General tab, fill in the template name, default memory size, and processor information: CPU specifies the complexity of this virtual machine for the purpose of selecting the physical node where the machine will run. Since the machine may not take the entire processor 100% of the time, set the value around 0.2 . VCPU says how much virtual machine operating system will see processors. Set the value to 1 . Leave Hypervisor on KVM.
Next, click the Storage tab at the top of the page (next to the General tab). As a Select Disk 0 (leave) the type of image, and select from the list above created disc. Add the next disc with blue (+) . For Disk 1, select the installation CD-ROM. Similarly, you can add a Volatile disc , such as a swap . This disk is not a separate image, it is always created again when the template is instantiated. One suitable type of use is just the swap space.
On the third Network tab, you set up virtual machine network interfaces. Connect the NIC 0 network card to 503-usrpriv .
The fourth OS Booting tab controls the order of the drives when booting. To install the operating system from the CD-ROM image, select this image first (check the boot from Disk 1 and move the arrow up with the arrow keys).
On the other tabs at this stage you don't need to set anything else, just click on the green Create at the top of the page.
Start virtual machine
Based on the created template, we can create ( instantiate ) a virtual machine. Select the appropriate template from the list by clicking on its row, and from the detail page of the template click on the blue Instantiate above . Here, it is still possible to change some parameters for a particular instance, which is mainly used to customize the pre-installed images and templates. Just click on the green Instantiate at the top of the page.
The newly created virtual machine is visible in the list of virtual machines: Instances → VMs from the left menu. Allocated network addresses are also visible. When installing a new system, set the network statically; rewrite this information in the installer. For production virtual machines, it is better to use contextualization packages that the system sets itself, for example addon-context-linux , addon-context-windows .
You can access the console of the virtual machine using the terminal icon on the right in the list of virtual machines, or by using the terminal icon labeled VNC from the virtual machine details page. Here you can continue to install the system.
After the installation is complete, it is only necessary to enable boot from disk. Turn off the installed virtual machine ( power button at the top of the details page of this virtual machine, and then Undeploy ). Then select the Conf tab at the far right, click on the green Update Configuration and change the boot order. Save changes by clicking the Green Update button at the top of the page. You can then start the virtual machine with the triangle button right ("Play", ⏵ ). Alternatively, a similar effect can be achieved by completely aborting the virtual machine (persistent disk remains), modifying the template, and reinstating it.
Finally, we recommend checking the list tips for installing the machine on FI . It contains useful advice, both general and advice on how to use some faculty-specific services.