Differences

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

--- en:cloud [2022/02/11 12:33] – grikiete
+++ en:cloud [2022/08/31 10:56] (current) – mif28585
@@ Line 20: / Line 20: @@
 </code>
-Please delete unused VM's
+**NOTE:** If you don't use your VM please delete it.
 ----
@@ Line 85: / 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| here]].
+VM states scheme is [[http://docs.opennebula.org/4.14/_images/states-simple.png| here]].
 ----
@@ Line 108: / 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 125: / Line 123: @@
 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]].
+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]].
+----
+=== Virtual machine network settings ===
+From September 1, 2022, by default, the virtual machine can only be accessed from the MIF network and via VU VPN. To make your virtual machine accessible from external networks, you would need to change the firewall in the network settings in the template you will use to create the virtual machine.
+. If you are building a machine using templates. Choose the template you want, open it and make a copy by pressing the Clone button.
+. Open the copy of your template and press Update → Network → Advanced Options.
+. Below you will find Security Groups, by default vu-vpn-mif will be selected, you need to select default and save the template.
+{{ :securitygroup.jpg }}
+----
+=== Increasing Resources of VM ===
+To increase your VM resources, please write a request by email [[itapc@mif.vu.lt]].