<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OpenNebula Services Configuration on</title><link>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/</link><description>Recent content in OpenNebula Services Configuration on</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 03 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview</title><link>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/overview/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/overview/</guid><description>&lt;p&gt;&lt;a id="deployment-references-overview"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Overview --&gt;
&lt;p&gt;This chapter is a configuration and deployment reference for all OpenNebula services. It contains the description of the configuration files (for least effort, basic and even advanced setups), how to stop and start them, and where to find their logs.&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;Read the sections for services you are interested in&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/oned/#oned-conf"&gt;OpenNebula Daemon&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/fireedge/#fireedge-conf"&gt;FireEdge&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/oneflow/#oneflow-conf"&gt;OneFlow&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/onegate/#onegate-conf"&gt;OneGate&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Move on to &lt;a href="https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/database/#database-maintenance"&gt;Database Maintenance&lt;/a&gt; and &lt;a href="https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/troubleshooting/#troubleshoot"&gt;Troubleshooting&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Users of &lt;strong&gt;Enterprise Edition&lt;/strong&gt; might find &lt;a href="https://docs.opennebula.io/7.2/product/operation_references/command_line_interface/support/#support"&gt;Support Utilities&lt;/a&gt; useful, which generates support bundles with detailed information about the cloud environment of the customer. The bundles help OpenNebula Customer Care to provide better support responses.&lt;/p&gt;</description></item><item><title>OpenNebula Configuration</title><link>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/oned/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/oned/</guid><description>&lt;p&gt;&lt;a id="oned-conf"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# OpenNebula Configuration (oned) --&gt;
&lt;p&gt;The OpenNebula Daemon (&lt;code&gt;oned&lt;/code&gt;) is the &lt;strong&gt;core service of the cloud management platform&lt;/strong&gt;. It manages the cluster nodes, Virtual Networks and storages, groups, users and their Virtual Machines, and provides the XML-RPC API to other services and end users. The service is distributed as an operating system package &lt;code&gt;opennebula&lt;/code&gt; with system service &lt;code&gt;opennebula&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;p&gt;The OpenNebula Daemon configuration file can be found in &lt;code&gt;/etc/one/oned.conf&lt;/code&gt; on the Front-end, and can be customized with the parameters listed in the table below.&lt;/p&gt;</description></item><item><title>FireEdge Configuration</title><link>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/fireedge/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/fireedge/</guid><description>&lt;p&gt;&lt;a id="fireedge"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a id="fireedge-setup"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a id="fireedge-configuration"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a id="fireedge-conf"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# FireEdge Configuration --&gt;
&lt;p&gt;The OpenNebula FireEdge server provides a &lt;strong&gt;next-generation web-management interface&lt;/strong&gt; for remote OpenNebula Cluster provisioning as well as additional functionality to Sunstone. It’s a dedicated daemon installed by default as part of the &lt;a href="https://docs.opennebula.io/7.2/software/installation_process/manual_installation/front_end_installation/"&gt;Single Front-end Installation&lt;/a&gt;, but can be deployed independently on a different machine. The server is distributed as an operating system package &lt;code&gt;opennebula-fireedge&lt;/code&gt; with the system service &lt;code&gt;opennebula-fireedge&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id="main-features"&gt;Main Features&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Guacamole Proxy&lt;/strong&gt; for Sunstone to remotely access the VMs (incl., VNC, RDP, and SSH)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;FireEdge Sunstone&lt;/strong&gt;: new iteration of Sunstone written in React/Redux. Accessible through the following URL:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre tabindex="0"&gt;&lt;code class="language-default" data-lang="default"&gt;http://&amp;lt;OPENNEBULA-FRONTEND&amp;gt;:2616
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;&lt;a id="fireedge-install-configuration"&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>OneFlow Configuration</title><link>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/oneflow/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/oneflow/</guid><description>&lt;p&gt;&lt;a id="appflow-configure"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a id="oneflow-conf"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# OneFlow Configuration --&gt;
&lt;p&gt;OneFlow &lt;strong&gt;orchestrates multi-VM services&lt;/strong&gt; as a whole, interacts with the OpenNebula Daemon to manage the Virtual Machines (starts, stops), and can be controlled via the Sunstone GUI or over CLI. It’s a dedicated daemon installed by default as part of the &lt;a href="https://docs.opennebula.io/7.2/software/installation_process/manual_installation/front_end_installation/"&gt;Single Front-end Installation&lt;/a&gt;, but can be deployed independently on a different machine. The server is distributed as an operating system package &lt;code&gt;opennebula-flow&lt;/code&gt; with the system service &lt;code&gt;opennebula-flow&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>OneGate Configuration</title><link>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/onegate/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/onegate/</guid><description>&lt;p&gt;&lt;a id="onegate-conf"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# OneGate Configuration --&gt;
&lt;p&gt;The OneGate server allows &lt;strong&gt;Virtual Machines to pull and push information from/to OpenNebula&lt;/strong&gt;. It can be used with both the KVM and LXC hypervisors if the guest operating system has preinstalled the OpenNebula &lt;a href="https://docs.opennebula.io/7.2/product/virtual_machines_operation/guest_operating_systems/creating_images/#os-install"&gt;contextualization package&lt;/a&gt;. It’s a dedicated daemon installed by default as part of the &lt;a href="https://docs.opennebula.io/7.2/software/installation_process/manual_installation/front_end_installation/"&gt;Single Front-end Installation&lt;/a&gt;, but can be deployed independently on a different machine. The server is distributed as an operating system package &lt;code&gt;opennebula-gate&lt;/code&gt; with the system service &lt;code&gt;opennebula-gate&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Database Maintenance</title><link>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/database/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/database/</guid><description>&lt;p&gt;&lt;a id="database-maintenance"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Database Maintenance --&gt;
&lt;p&gt;OpenNebula persists the state of the cloud into the selected &lt;a href="https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/database/"&gt;SQL database&lt;/a&gt;. The database should be monitored and tuned for the best performance by cloud administrators following the best practices of the particular database product. In this guide, we provide a few tips on how to optimize the database for OpenNebula and thoroughly describe OpenNebula’s database maintenance tool &lt;code&gt;onedb&lt;/code&gt;, which simplifies the most common database operations - backups and restores, version upgrades, or consistency checks.&lt;/p&gt;</description></item><item><title>Troubleshooting</title><link>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/troubleshooting/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/troubleshooting/</guid><description>&lt;p&gt;&lt;a id="troubleshoot"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Troubleshooting --&gt;
&lt;h2 id="logging"&gt;Logging&lt;/h2&gt;
&lt;p&gt;Every OpenNebula server generates logs with a configurable verbosity (level of detail) and through different means (file, syslog, or standard error output) to allow cloud administrators to troubleshoot the potential problems. Logs are stored in &lt;code&gt;/var/log/one/&lt;/code&gt; on a Front-end Host with a particular component. Some valuable error messages can be also seen by the end users in &lt;a href="https://docs.opennebula.io/7.2/product/operation_references/command_line_interface/cli/#cli"&gt;CLI&lt;/a&gt; tools or the &lt;a href="https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/fireedge/#fireedge"&gt;Sunstone GUI&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id="configure-logging-system"&gt;Configure Logging System&lt;/h3&gt;
&lt;p&gt;Follow the guides of each component to find the logs’ location and configuration of log verbosity:&lt;/p&gt;</description></item><item><title>OneForm Configuration</title><link>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/oneform/</link><pubDate>Tue, 03 Jun 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/operation_references/opennebula_services_configuration/oneform/</guid><description>&lt;p&gt;&lt;a id="oneform-conf"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;OpenNebula Form, also known as &lt;em&gt;OneForm&lt;/em&gt;, is the hybrid provisioning engine for OpenNebula, responsible for automating the deployment, scaling, and configuration of edge and cloud infrastructure using &lt;a href="https://developer.hashicorp.com/terraform"&gt;Terraform&lt;/a&gt; and &lt;a href="https://docs.ansible.com/"&gt;Ansible&lt;/a&gt;. It is delivered as a standalone service and interacts with the core OpenNebula services to register compute Hosts, Virtual Networks, and storage resources as part of a Provision lifecycle.&lt;/p&gt;
&lt;p&gt;OneForm is installed by default as part of the standard OpenNebula package set and runs as a systemd service named &lt;code&gt;opennebula-form&lt;/code&gt;. It can also be deployed independently on a separate Host if needed.&lt;/p&gt;</description></item></channel></rss>