Differences

This shows you the differences between two versions of the page.

--- en:cloud [2017/09/26 10:49] – arnas15
+++ en:cloud [2022/02/11 12:51] – grikiete
@@ Line 8: / Line 8: @@
 **Each MIF user is provided with such IT resources:** \\
-CPU: 1\\
+<code>
-MEMORY: 2048MB\\
+CPU: 1.0
-VMS: 4 (total count of VM)\\
+MEMORY: 5GB
-Datastores/lustre: SIZE=10240MB, IMAGES=4\\
+VMS: 5 (VM quantity)
-Networks/VNET2: LEASES=4\\
+Datastores/default: SIZE=20GB, IMAGES=10
+Datastores/files: SIZE=1GB, IMAGES=10
+Datastores/qcow2: SIZE=20GB, IMAGES=10
+Datastores/lvm: SIZE=20GB, IMAGES=10
+Networks/VNET1: LEASES=2
+Networks/VNET2: LEASES=5
+</code>
-== *Please delete unused VM's ==
+**NOTE:** If you don't use your VM please delete it.
-If you need extend limits please write us: admin[eta]mif.vu.lt.\\
-Available resources are 4 x IBM BladeCenter HS22/7870SGW with 2 x 6 CPU cores, 24GB RAM, 160GB HDD in each.\\
 ----
@@ Line 23: / Line 26: @@
 **User Configuration**
-Views:
+There are two views: **cloud** and **user**:
-**cloud** - reduced functionality - new VM could be created from existing templates only.\\
-**user** - full functionality.\\
+  - **cloud** – for simplified use when new VMs are created from existing templates.
+  - **user** – all features are available to the user, but may require some training (default).
 You can change user view by going to **username → Settings → Info → View**:
  {{ :user_settings.png |}}
-Before creating virtual machines it is recommended to upload the public part of your SSH key. You can do this via settings by going to **username → Settings → Info → Public SSH key**.
+Before creating virtual machines it is recommended to upload the public part of your SSH key. If you are using **cloud view**, you can do this in **User Name -> Settings -> Config -> Add SSH Key**. If you are using **user view**, load the SSH public part into the **Public SSH Key** field:
 {{ :user_ssh.png |}}
@@ Line 38: / Line 42: @@
 **Creating a virtual machine**
-To create a new VM you have to go to **Virtual Resources → Virtual Machines → click green plus button**. Then choose a template, fill in your VM name, change capacity (if needed) and click "**Create**" button.
+To create a new VM you have to go to **Virtual Resources → Virtual Machines → click green plus button**.
+Then choose a template, fill in your VM name, change capacity (if needed) and click "**Create**" button.
 {{ :user_create.png |}}
@@ Line 46: / Line 51: @@
 **Remarks**:
 Windows 2012 R2 virtual disk is recommended for use with templates containing the prefix win. \\
-DISK_SIZE - indicates how much to increase the OS disk using the appropriate template. (If you copy an existing systematic pattern - remove this attribute).
 ^ INSTANCE_TYPE ^ CPU ^ VCPU ^ MEMORY ^ DISK_SIZE ^ swap ^
@@ Line 80: / Line 85: @@
 | done | Done | The VM is done. VMs in this state won’t be shown with onevm list but are kept in the database for accounting purposes. You can still get their information with the onevm show command. |
-VM states sheme [[http://docs.opennebula.org/4.14/_images/states-simple.png|čia]].
+VM states scheme is [[http://docs.opennebula.org/4.14/_images/states-simple.png| here]].
 ----
@@ Line 103: / Line 108: @@
 | Resizing VM | If you have created a Virtual Machine and you need more resources, the following procedure is recommended: Perform any operation needed to prepare your Virtual Machine for shutting down, e.g. you may want to manually stop some services... 1. Poweroff the Virtual Machine. 2. Re-size the VM. 3. Resume the Virtual Machine using the new capacity. |
 | Sheduling | Most of the onevm commands accept the ‘–schedule’ option, allowing users to delay the actions until the given date and time. |
-**Note**. If you don't use your VM please shutdown, cancel or delete it. After 24 hours of running your VM could be shutdown automatically.
 ----
@@ Line 117: / Line 120: @@
 Attribute **CONNECT_INFO2** for Windows users who use Putty terminal emulator. Copy attribute value to command line or enter corresponding values (For example: IP/Hostname = 193.219.91.103, port=14152) into Putty to log in to your VM.
+To use the redirects of TCP connections, you must add **TCP_PORT_FORWARDING** attribute value with the desired connections (max 4). After changing the attribute value, remember to restart your VM (PowerOff → Boot) and to check which connections were created. For example, if you want to open connection 80, type 80 and restart the VM. You will see TCP_PORT_FORWARDING value change to PORT: 80, where PORT is an external IP (PUBLIC_IP value) connection through which you can connect to the VM of your desired connection (80).
+On a **VNET1** network, VM can receive not only the usual internal **IPv4** address but also the globally accessible **IPv6** address. More about connecting to [[http://ipv6.lt|IPv6]].
+----
+=== Increasing Resources of VM ===
+To increase your VM resources, please write a request by email [[itapc@mif.vu.lt]].