<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Virtual Machines Networking on</title><link>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/</link><description>Recent content in Virtual Machines Networking on</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 17 Feb 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview</title><link>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/overview/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/overview/</guid><description>&lt;!--# Overview --&gt;
&lt;p&gt;This section contains documentation on how to create and manage &lt;a href="https://docs.opennebula.io/7.2/product/cluster_configuration/networking_system/manage_vnets/"&gt;Virtual Networks&lt;/a&gt; and their related objects.&lt;/p&gt;
&lt;h2 id="how-should-i-read-this-chapter"&gt;How Should I Read This Chapter&lt;/h2&gt;
&lt;p&gt;Before reading this section , you should have already installed and configured your cloud.&lt;/p&gt;
&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/vn_templates/"&gt;Virtual Networks Templates&lt;/a&gt; explains how to create networks.&lt;/li&gt;
&lt;li&gt;The &lt;a href="https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/self_provision/"&gt;Self Provision&lt;/a&gt; section details how regular users can self-provision virtual networks for their use.&lt;/li&gt;
&lt;li&gt;You will also find information on &lt;a href="https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/security_groups/"&gt;Security Groups&lt;/a&gt;, to easily define firewall rules.&lt;/li&gt;
&lt;li&gt;Additionally you will learn on how to manage &lt;a href="https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/vrouter/"&gt;Virtual Routers&lt;/a&gt; which are an OpenNebula resource that provide routing across Virtual Networks.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;h2 id="hypervisor-compatibility"&gt;Hypervisor Compatibility&lt;/h2&gt;
&lt;p&gt;Virtual Networks are common to all hypervisors.&lt;/p&gt;</description></item><item><title>Virtual Network Templates</title><link>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/vn_templates/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/vn_templates/</guid><description>&lt;p&gt;&lt;a id="vn-templates"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Virtual Networks Templates --&gt;
&lt;p&gt;The Virtual Network Templates allow the end user to create Virtual Networks without knowing the details of the underlying infrastructure. Typically the administrator sets up the templates with the required physical attributes, e.g., driver or physical device information and lets the end user add all the logic information like address ranges or gateway.&lt;/p&gt;
&lt;p&gt;Virtual Network Templates can be instantiated several times and shared between multiple users.&lt;/p&gt;</description></item><item><title>Security Groups</title><link>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/security_groups/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/security_groups/</guid><description>&lt;p&gt;&lt;a id="security-groups"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a id="firewall"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Security Groups --&gt;
&lt;p&gt;Security Groups define firewall rules to be applied to Virtual Machines.&lt;/p&gt;









&lt;div class="alert alert-warning" role="alert"&gt;
 
 &lt;div class="alert-heading"&gt;
 &lt;i class="alert-icon fas fa-triangle-exclamation"&gt;&lt;/i&gt; Warning
 &lt;/div&gt;
 
 &lt;div class="alert-body"&gt;
 Security groups are not supported for OpenvSwitch.
 &lt;/div&gt; 
&lt;/div&gt;
&lt;p&gt;&lt;a id="security-groups-requirements"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="defining-a-security-group"&gt;Defining a Security Group&lt;/h2&gt;
&lt;p&gt;A Security Group is composed of several Rules. Each Rule is defined with the following attributes:&lt;/p&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Attribute&lt;/th&gt;
 &lt;th&gt;Type&lt;/th&gt;
 &lt;th&gt;Meaning&lt;/th&gt;
 &lt;th&gt;Values&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;PROTOCOL&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Mandatory&lt;/td&gt;
 &lt;td&gt;Defines the protocol of the rule&lt;/td&gt;
 &lt;td&gt;ALL, TCP, UDP, ICMP, IPSEC&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;RULE_TYPE&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Mandatory&lt;/td&gt;
 &lt;td&gt;Defines the traffic direction&lt;/td&gt;
 &lt;td&gt;INBOUND, OUTBOUND&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;IP&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Optional&lt;/td&gt;
 &lt;td&gt;If the rule only applies to a specific net. This is the first&lt;br/&gt;&lt;strong&gt;IP&lt;/strong&gt; of the consecutive set of &lt;strong&gt;IPs&lt;/strong&gt;. Must be used with&lt;br/&gt;&lt;strong&gt;SIZE&lt;/strong&gt;.&lt;/td&gt;
 &lt;td&gt;A valid IP&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;SIZE&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Optional&lt;/td&gt;
 &lt;td&gt;If the rule only applies to a net. The number of total&lt;br/&gt;consecutive IPs of the network. Use always with &lt;strong&gt;IP&lt;/strong&gt;.&lt;/td&gt;
 &lt;td&gt;An integer &amp;gt;= 1&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;RANGE&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Optional&lt;/td&gt;
 &lt;td&gt;A Port Range to filter specific ports. Only works with&lt;br/&gt;&lt;strong&gt;TCP&lt;/strong&gt; and &lt;strong&gt;UDP&lt;/strong&gt;.&lt;/td&gt;
 &lt;td&gt;(iptables syntax) multiple ports or port&lt;br/&gt;ranges are separated using a comma, and a&lt;br/&gt;port range is specified using a colon.&lt;br/&gt;Example: &lt;code&gt;22,53,80:90,110,1024:65535&lt;/code&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;ICMP_TYPE&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Optional&lt;/td&gt;
 &lt;td&gt;Specific ICMP type of the rule. If a type has multiple codes,&lt;br/&gt;it includes all the codes within. This can only be used with&lt;br/&gt;&lt;strong&gt;ICMP&lt;/strong&gt;. If omitted the rule will affect the whole &lt;strong&gt;ICMP&lt;/strong&gt;&lt;br/&gt;protocol.&lt;/td&gt;
 &lt;td&gt;0,3,4,5,8,9,10,11,12,13,14,17,18&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;NETWORK_ID&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Optional&lt;/td&gt;
 &lt;td&gt;Specify a network ID to which this Security Group will apply&lt;/td&gt;
 &lt;td&gt;A valid networkd ID&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;









&lt;div class="alert alert-info" role="alert"&gt;
 
 &lt;div class="alert-heading"&gt;
 &lt;i class="alert-icon fa-sharp fa-solid fa-circle-info"&gt;&lt;/i&gt; Note
 &lt;/div&gt;
 
 &lt;div class="alert-body"&gt;
 When using &lt;code&gt;IPSEC&lt;/code&gt; value for &lt;code&gt;PROTOCOL&lt;/code&gt;, rules for the Encapsulating Security Payload (ESP) protocol of IPSec are set.
 &lt;/div&gt; 
&lt;/div&gt;
&lt;p&gt;To create a Security Group, use the &lt;a href="https://docs.opennebula.io/7.2/product/control_plane_configuration/graphical_user_interface/fireedge_sunstone/#fireedge-sunstone"&gt;Sunstone UI Interface&lt;/a&gt; or create a template file following this example:&lt;/p&gt;</description></item><item><title>Self Provision</title><link>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/self_provision/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/self_provision/</guid><description>&lt;p&gt;&lt;a id="self-provision"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Virtual Network Self-Provisioning --&gt;
&lt;p&gt;End users can create their own Virtual Networks in two different ways:&lt;/p&gt;
&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;making a &lt;strong&gt;reservation&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;instantiating a &lt;strong&gt;Virtual Network Template&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;a id="vgg-vn-reservations"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="reservations"&gt;Reservations&lt;/h2&gt;
&lt;p&gt;Reservations allow users to create their own networks consisting of portions of an existing Virtual Network. Each portion is called a Reservation. To implement this you need to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Define a VNET&lt;/strong&gt; with the desired ARs and configuration attributes. These attributes will be inherited by any Reservation, so the final users do not need to deal with low-level networking details.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Set up access&lt;/strong&gt;. In order to make a Reservation, users need &lt;code&gt;USE&lt;/code&gt; rights on the Virtual Network, just as if they would use it to directly provision IPs from it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Make Reservations&lt;/strong&gt;. Users can easily request specific addresses or a number of addresses from a network. Reservations are placed in a new Virtual Network for the user.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Use Reservations&lt;/strong&gt;. Reservations are Virtual Networks and offer the same interface, so simply point any Virtual Machine to them. The number of addresses and usage stats are also shown in the same way.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="make-and-delete-reservations"&gt;Make and Delete Reservations&lt;/h3&gt;
&lt;p&gt;To make reservations just choose the source Virtual Network, the number of addresses, and the name of the reservation. For example, to reserve 10 addresses from &lt;code&gt;Private&lt;/code&gt; and place them on &lt;code&gt;MyVNET&lt;/code&gt; just:&lt;/p&gt;</description></item><item><title>Virtual Routers</title><link>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/vrouter/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/vrouter/</guid><description>&lt;p&gt;&lt;a id="vrouter"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Virtual Routers --&gt;
&lt;p&gt;Virtual Routers provide routing across Virtual Networks. The administrators can easily connect Virtual Networks from Sunstone and the CLI. The routing itself is implemented with a Virtual Machine appliance available though the Marketplace. This Virtual Machine can be seamlessly deployed in high availability mode.&lt;/p&gt;
&lt;h2 id="download-the-virtual-router-appliance"&gt;Download the Virtual Router Appliance&lt;/h2&gt;
&lt;p&gt;OpenNebula provides an appliance which implements various Virtual Network Functions (VNFs), including the Virtual Router. The Virtual Router image is prepared to run in an HA mode and process the context information from OpenNebula. In this way, its base capabilities can be easily extended. Continue to the &lt;a href="https://docs.opennebula.io/7.2/product/integration_references/marketplace_appliances/vnf/#service-vnf"&gt;VNF appliance documentation&lt;/a&gt; for more details about the advanced usage and other implemented functions.&lt;/p&gt;</description></item><item><title>Transparent Proxies</title><link>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/tproxy/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/virtual_machines_operation/virtual_machines_networking/tproxy/</guid><description>&lt;p&gt;&lt;a id="tproxy"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Transparent Proxies --&gt;
&lt;p&gt;Transparent Proxies make it possible to connect to management services, such as OneGate, by implicitly using the existing data center backbone networking. The OneGate service usually runs on the leader Front-end machine, which makes it difficult for Virtual Machines running in isolated Virtual Networks to contact it. This situation forces OpenNebula users to design virtual networking in advance, to ensure that VMs can securely reach OneGate. Transparent Proxies have been designed to remove that requirement.&lt;/p&gt;</description></item></channel></rss>