<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Multi-VM Workflows on</title><link>https://docs.opennebula.io/7.2/product/virtual_machines_operation/multi-vm_workflows/</link><description>Recent content in Multi-VM Workflows 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/multi-vm_workflows/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview</title><link>https://docs.opennebula.io/7.2/product/virtual_machines_operation/multi-vm_workflows/overview/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/virtual_machines_operation/multi-vm_workflows/overview/</guid><description>&lt;p&gt;&lt;a id="oneapps-overview"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a id="oneflow-overview"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a id="multivm-service-management-overview"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Overview --&gt;
&lt;h2 id="how-should-i-read-this-chapter"&gt;How Should I Read This Chapter&lt;/h2&gt;
&lt;p&gt;Some applications require multiple VMs to implement their workflow. OpenNebula allows you to coordinate the deployment and resource usage of such applications through the OneFlow component.&lt;/p&gt;
&lt;p&gt;This component is able to deploy services; these services are a group of interconnected Virtual Machines that work as an entity. They can communicate with each other using Virtual Networks deployed by the OneFlow server itself, and they can also have some relationship. A group of Virtual Machines, known as a Role, can depend on other Roles, so it will be deployed when the parent is ready.&lt;/p&gt;</description></item><item><title>OneFlow Services Management</title><link>https://docs.opennebula.io/7.2/product/virtual_machines_operation/multi-vm_workflows/appflow_use_cli/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/virtual_machines_operation/multi-vm_workflows/appflow_use_cli/</guid><description>&lt;p&gt;&lt;a id="appflow-use-cli"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# OneFlow Services Management --&gt;
&lt;p&gt;OneFlow allows users and administrators to define, execute, and manage multi-tiered applications, which we call &lt;strong&gt;Services&lt;/strong&gt;, composed of interconnected Virtual Machines with deployment dependencies between them. Each group of Virtual Machines is deployed and managed as a single entity and is completely integrated with the advanced &lt;a href="https://docs.opennebula.io/7.2/product/cloud_system_administration/multitenancy/auth_overview/#auth-overview"&gt;OpenNebula user and group management&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="what-is-a-service"&gt;What Is a Service&lt;/h2&gt;
&lt;p&gt;The following diagram represents a multi-tier application. Each node represents a Role and its cardinality (the number of VMs that will be deployed). The arrows indicate the deployment dependencies: each Role’s VMs are deployed only when all its parent’s VMs are running.&lt;/p&gt;</description></item><item><title>OneFlow Services Auto-scaling</title><link>https://docs.opennebula.io/7.2/product/virtual_machines_operation/multi-vm_workflows/appflow_elasticity/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/virtual_machines_operation/multi-vm_workflows/appflow_elasticity/</guid><description>&lt;p&gt;&lt;a id="appflow-elasticity"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# OneFlow Services Auto-scaling --&gt;
&lt;p&gt;A Service Role’s cardinality can be adjusted either manually or automatically in two ways: based on metrics or based on a schedule.&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;When a scaling action starts, the Role and Service enter the &lt;code&gt;SCALING&lt;/code&gt; state. In this state, the Role will &lt;code&gt;instantiate&lt;/code&gt; or &lt;code&gt;terminate&lt;/code&gt; a number of VMs to reach its new cardinality.&lt;/p&gt;
&lt;p&gt;A Role with elasticity policies must define a minimum and maximum number of VMs:&lt;/p&gt;</description></item><item><title>OneGate Usage</title><link>https://docs.opennebula.io/7.2/product/virtual_machines_operation/multi-vm_workflows/onegate_usage/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/virtual_machines_operation/multi-vm_workflows/onegate_usage/</guid><description>&lt;p&gt;&lt;a id="onegate-overview"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a id="onegate-usage"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# OneGate Usage --&gt;
&lt;p&gt;The OneGate component allows Virtual Machine guests to pull and push VM information from OpenNebula. Users and administrators can use it to gather metrics, detect problems in their applications, and trigger OneFlow elasticity rules from inside the VM.&lt;/p&gt;
&lt;p&gt;For Virtual Machines that are part of a Multi-VM Application (&lt;a href="https://docs.opennebula.io/7.2/product/virtual_machines_operation/multi-vm_workflows/overview/#oneflow-overview"&gt;OneFlow Service&lt;/a&gt;), they can also retrieve the Service information directly from OneGate and trigger actions to reconfigure the Service or pass information among different VMs.&lt;/p&gt;</description></item></channel></rss>