M #-: Merge sync one-6.10 branch

Author: rsmontero

publish/config.yaml

@@ -1,5 +1,6 @@
 mapping:
-  master: '6.10'
+  master: '6.99'
+  one-6.10: '6.10'
   one-6.8: '6.8'
   one-6.6: '6.6'
   one-6.4: '6.4'

source/ext/spellchecking/wordlists/opennebula.txt

@@ -474,6 +474,7 @@ monitorization
 moref
 morefs
 mountpoints
+msi
 multicast
 multicluster
 multitenant
@@ -486,6 +487,7 @@ natively
 ncurses
 netaddr
 netmask
+netplan
 networkd
 nginx
 nic

source/images/aws_cluster_images_datastore.png

@@ -215,7 +215,7 @@ The following example shows how you can change the logo to a generic linux one (
 
 Configure DataTables
 --------------------------------------------------------------------------------
-You can change the style of the rows depending on your preferences. in case they are changed in the fireedge-server.conf file. this change will be priority. and it will adjust the view to all users. 
+You can change the style of the rows depending on your preferences. in case they are changed in the fireedge-server.conf file. this change will be priority. and it will adjust the view to all users.
 
 |fireedge_sunstone_list_datatable|
 

source/images/minione-aws-ubuntu24.04.png

@@ -4,14 +4,15 @@
 WHMCS Tenants Module Install/Update
 ===================================
 
+.. warning:: You must use PHP 7.4, currently PHP 8.x will cause an error when creating the user
+
 The install and update process are essentially identical. The Module files can be found in */usr/share/one/whmcs* after you have installed the *opennebula-whmcs-tenants* package via your package manager. You will just need to merge the *modules* directory to the main WHMCS directory on the server hosting WHMCS. When updating the module just copy the files on top of the existing files and overwrite them. An example command for copying the files:
 
 .. code-block:: bash
 
     cp -rf /usr/share/one/whmcs/modules /path/to/web/root/whmcs/.
 
 
-
 .. note:: Make sure you download the updated package from the EE repository before doing either an install or an update.
 
 ==================================

source/images/sunstone-aws_cluster_download_oneke.png

@@ -9,14 +9,45 @@ This page contains the OpenNebula Cloud API Specification for Java. It has been
 Download
 ================================================================================
 
-You can download the ``.jar`` file compiled using Java 1.8, the required libraries, and the javadoc packaged in a tar.gz file `following this link <http://downloads.opennebula.io/packages>`__ in the OpenNebula version you have installed.
+You can download the ``.jar`` file compiled using Java 11, the required libraries, and the javadoc packaged in a tar.gz file `following this link <http://downloads.opennebula.io/packages>`__ in the OpenNebula version you have installed.
 
 You can also consult the `javadoc online </doc/6.4/oca/java/>`__.
 
+Compilation
+================================================================================
+
+If you need to compile the Java bindings, please follow these steps
+
+- Download the source code of opennebula (available on `OpenNebula code repository <https://www.github.com/OpenNebula/one>`__)
+
+  ``git clone https://www.github.com/OpenNebula/one``
+
+- On the source code, change to the directory ``src/oca/java``
+
+  ``cd one/src/oca/java``
+
+- Download the apache xmlrpc library (note that the URL may change in your case)
+
+  ``curl -OL https://archive.apache.org/dist/ws/xmlrpc/binaries/xmlrpc-3.1.1-bin.tar.gz``
+
+- Uncompress it and move the ``/lib`` directory to the source code dir
+
+  ``tar xzvf xmlrpc-3.1.1-bin.tar.gz; mv xmlrpc-3.1.1/lib .``
+
+- Modify the build script adding to the libraries the xmlrpc library
+
+  ``sed -i 's@^LIB_DIR="/usr/share/java"$@LIB_DIR="/usr/share/java:./lib"@g' build.sh``
+
+- Build the library
+
+  ``build.sh``
+
+The jar file with the bindings will be the ``jar/org.opennebula.client.jar`` file
+
 Usage
 ================================================================================
 
-To use the OpenNebula Cloud API for Java in your Java project, you have to add to the classpath the org.opennebula.client.jar file and the XML-RPC libraries located in the lib directory.
+To use the OpenNebula Cloud API for Java in your Java project, you have to add to the classpath the ``org.opennebula.client.jar`` file and the XML-RPC libraries located in the lib directory.
 
 Code Sample
 ================================================================================

source/images/sunstone-aws_cluster_replica_host.png

@@ -28,13 +28,14 @@ Sunstone
 
 - Guacamole RDP as is currently shipped in OpenNebula does not support NLA authentication. You can follow `these instructions <https://www.parallels.com/blogs/ras/disabling-network-level-authentication/>`__ in order to disable NLA in the Windows box to use Guacamole RDP within Sunstone.
 
+- `'Groupadmin' view fails to load for groups with multiple admin users <https://github.com/OpenNebula/one/issues/6730>`__.
+
 - The current configuration for both Sunstone and One-Provision contain a mismatch in the `keep_me_logged` configuration option. This issue has been fixed but the new configuration files need to be downloaded in order for this fix to take effect, refer to :ref:`the following section <fireedge_install_configuration>` for instructions on how to do this.
 
 - The `Update VM Configuration` dialog contains a bug which will result in a blank screen if one tries to update the configuration of a virtual machine with less than 2 total disks attached. The quickest workaround for this is to attach another minimal disk to the VM.
 
 - When deleting an element in the datatable. such as running the terminate in a VM, we recommend refreshing the window. as there is an error in the client code discussed in the following `issue <https://github.com/OpenNebula/one/issues/6781>`__.
 
-
 Install Linux Graphical Desktop on KVM Virtual Machines
 ================================================================================
 

source/images/sunstone-aws_edge_cluster_deploying.png

@@ -33,6 +33,8 @@ Front-End Components
 | Ruby Gems                | Versions installed by opennebula-rubygems   | Detailed information in ``/usr/share/one/Gemfile``    |
 +--------------------------+---------------------------------------------+-------------------------------------------------------+
 
+.. note:: Support for nodes' operating system ensures that the latest two LTS releases feature certified packages.
+
 .. _vcenter_nodes_platform_notes:
 
 vCenter Nodes
@@ -43,7 +45,8 @@ vCenter Nodes
 +-----------+---------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------+
 | Component |                Version                |                                                            More information                                                            |
 +===========+=======================================+========================================================================================================================================+
-| vCenter   | 7.0.x, managing ESX 7.0.x             | :ref:`vCenter Node Installation <vcenter_node>`                                                                                        |
+| vCenter   | 7.0.x managing ESX 7.0.x &            | :ref:`vCenter Node Installation <vcenter_node>`                                                                                        |
+|           | 8.0.x managing ESX 8.0.x              |                                                                                                                                        |
 +-----------+---------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------+
 | NSX-T     | 2.4.1+                                | `VMware compatiblity <https://www.vmware.com/resources/compatibility/sim/interop_matrix.php>`__. :ref:`NSX Documentation <nsx_setup>`. |
 +-----------+---------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------+

source/images/sunstone-aws_edge_cluster_sys_ds.png

@@ -9,34 +9,34 @@ OpenNebula provides a set commands to interact with the system:
 CLI
 ================================================================================
 
-* `oneacct </doc/6.8/cli/oneacct.1.html>`__: gets accounting data from OpenNebula.
-* `oneacl </doc/6.8/cli/oneacl.1.html>`__: manages OpenNebula ACLs.
-* `onecfg </doc/6.8/cli/onecfg.1.html>`__: manages OpenNebula configuration files upgrade.
-* `onecluster </doc/6.8/cli/onecluster.1.html>`__: manages OpenNebula clusters.
-* `onedatastore </doc/6.8/cli/onedatastore.1.html>`__: manages OpenNebula datastores.
-* `onedb </doc/6.8/cli/onedb.1.html>`__: OpenNebula database migration tool.
-* `onegroup </doc/6.8/cli/onegroup.1.html>`__: manages OpenNebula groups.
-* `onehook </doc/6.8/cli/onehook.1.html>`__: manages OpenNebula hooks.
-* `onehost </doc/6.8/cli/onehost.1.html>`__: manages OpenNebula hosts.
-* `oneimage </doc/6.8/cli/oneimage.1.html>`__: manages OpenNebula images.
-* `onemarket </doc/6.8/cli/onemarket.1.html>`__: manages internal and external marketplaces.
-* `onemarketapp </doc/6.8/cli/onemarketapp.1.html>`__: manages appliances from marketplaces.
-* `oneprovider </doc/6.8/cli/oneprovider.1.html>`__: manages OpenNebula providers.
-* `oneprovision </doc/6.8/cli/oneprovision.1.html>`__: manages OpenNebula provisions.
-* `onesecgroup </doc/6.8/cli/onesecgroup.1.html>`__: manages OpenNebula security groups.
-* `oneshowback </doc/6.8/cli/oneshowback.1.html>`__: OpenNebula Showback tool.
-* `onetemplate </doc/6.8/cli/onetemplate.1.html>`__: manages OpenNebula templates.
-* `oneuser </doc/6.8/cli/oneuser.1.html>`__: manages OpenNebula users.
-* `onevcenter </doc/6.8/cli/onevcenter.1.html>`__: handles vCenter resource import.
-* `onevdc </doc/6.8/cli/onevdc.1.html>`__: manages OpenNebula Virtual DataCenters.
-* `onevm </doc/6.8/cli/onevm.1.html>`__: manages OpenNebula virtual machines.
-* `onevmgroup </doc/6.8/cli/onevmgroup.1.html>`__: manages OpenNebula VMGroups.
-* `onevnet </doc/6.8/cli/onevnet.1.html>`__: manages OpenNebula networks.
-* `onevntemplate </doc/6.8/cli/onevntemplate.1.html>`__: manages OpenNebula networks templates.
-* `onevrouter </doc/6.8/cli/onevrouter.1.html>`__: manages OpenNebula Virtual Routers.
-* `onezone </doc/6.8/cli/onezone.1.html>`__: manages OpenNebula zones.
-* `oneirb </doc/6.8/cli/oneirb.1.html>`__: opens an irb session.
-* `onelog </doc/6.8/cli/onelog.1.html>`__: access to OpenNebula services log files.
+* `oneacct </doc/6.10/cli/oneacct.1.html>`__: gets accounting data from OpenNebula.
+* `oneacl </doc/6.10/cli/oneacl.1.html>`__: manages OpenNebula ACLs.
+* `onecfg </doc/6.10/cli/onecfg.1.html>`__: manages OpenNebula configuration files upgrade.
+* `onecluster </doc/6.10/cli/onecluster.1.html>`__: manages OpenNebula clusters.
+* `onedatastore </doc/6.10/cli/onedatastore.1.html>`__: manages OpenNebula datastores.
+* `onedb </doc/6.10/cli/onedb.1.html>`__: OpenNebula database migration tool.
+* `onegroup </doc/6.10/cli/onegroup.1.html>`__: manages OpenNebula groups.
+* `onehook </doc/6.10/cli/onehook.1.html>`__: manages OpenNebula hooks.
+* `onehost </doc/6.10/cli/onehost.1.html>`__: manages OpenNebula hosts.
+* `oneimage </doc/6.10/cli/oneimage.1.html>`__: manages OpenNebula images.
+* `onemarket </doc/6.10/cli/onemarket.1.html>`__: manages internal and external marketplaces.
+* `onemarketapp </doc/6.10/cli/onemarketapp.1.html>`__: manages appliances from marketplaces.
+* `oneprovider </doc/6.10/cli/oneprovider.1.html>`__: manages OpenNebula providers.
+* `oneprovision </doc/6.10/cli/oneprovision.1.html>`__: manages OpenNebula provisions.
+* `onesecgroup </doc/6.10/cli/onesecgroup.1.html>`__: manages OpenNebula security groups.
+* `oneshowback </doc/6.10/cli/oneshowback.1.html>`__: OpenNebula Showback tool.
+* `onetemplate </doc/6.10/cli/onetemplate.1.html>`__: manages OpenNebula templates.
+* `oneuser </doc/6.10/cli/oneuser.1.html>`__: manages OpenNebula users.
+* `onevcenter </doc/6.10/cli/onevcenter.1.html>`__: handles vCenter resource import.
+* `onevdc </doc/6.10/cli/onevdc.1.html>`__: manages OpenNebula Virtual DataCenters.
+* `onevm </doc/6.10/cli/onevm.1.html>`__: manages OpenNebula virtual machines.
+* `onevmgroup </doc/6.10/cli/onevmgroup.1.html>`__: manages OpenNebula VMGroups.
+* `onevnet </doc/6.10/cli/onevnet.1.html>`__: manages OpenNebula networks.
+* `onevntemplate </doc/6.10/cli/onevntemplate.1.html>`__: manages OpenNebula networks templates.
+* `onevrouter </doc/6.10/cli/onevrouter.1.html>`__: manages OpenNebula Virtual Routers.
+* `onezone </doc/6.10/cli/onezone.1.html>`__: manages OpenNebula zones.
+* `oneirb </doc/6.10/cli/oneirb.1.html>`__: opens an irb session.
+* `onelog </doc/6.10/cli/onelog.1.html>`__: access to OpenNebula services log files.
 
 The output of these commands can be customized by modifying the configuration files that can be found in ``/etc/one/cli/``. They also can be customized on a per-user basis, in this case the configuration files should be placed in ``$HOME/.one/cli``.
 
@@ -45,13 +45,13 @@ List operation for each command will open a ``less`` session for a better user e
 OneFlow Commands
 ================================================================================
 
-* `oneflow </doc/6.8/cli/oneflow.1.html>`__: OneFlow Service management.
-* `oneflow-template </doc/6.8/cli/oneflow-template.1.html>`__: OneFlow Service Template management.
+* `oneflow </doc/6.10/cli/oneflow.1.html>`__: OneFlow Service management.
+* `oneflow-template </doc/6.10/cli/oneflow-template.1.html>`__: OneFlow Service Template management.
 
 OneGate Commands
 ================================================================================
 
-* `onegate </doc/6.8/cli/onegate.1.html>`__: OneGate Service management.
+* `onegate </doc/6.10/cli/onegate.1.html>`__: OneGate Service management.
 
 .. _cli_shell:
 

source/images/sunstone-aws_k8s_vms_list.png

@@ -72,7 +72,7 @@ Windows
 Download the MSI package into ``C:\``:
 
 
-* https://github.com/OpenNebula/one-apps/releases/download/v6.8.1/one-context-6.8.1.msi
+* https://github.com/OpenNebula/one-apps/releases/download/v|context_release|/one-context-|context_release|.msi
 
 
 Or execute this command in powershell:

source/images/sunstone-aws_kubernetes_vnf_ip.png

@@ -188,7 +188,7 @@ For example, to configure default page size of **1G** and **250** hugepages with
 
     # update-grub
 
-.. tip:: Use ``intel_iommu=on`` instead for hosts with an AMD CPU
+.. tip:: Use ``amd_iommu=on`` instead for hosts with an AMD CPU
 
 Then reboot the system. After rebooting, make sure that the hugepages mount can be seen so the applications can access them.
 

source/images/sunstone-k8s_enable_netw_params.png

@@ -13,14 +13,30 @@ Additionally, each VXLAN has an associated multicast address to encapsulate L2 b
 Considerations & Limitations
 ================================================================================
 
-This driver works with the default UDP server port 8472.
+By default, this driver uses the default linux UDP server port 8472 to transfer VXLAN traffic between host. 
+
+.. important::
+
+   Please note that the official IANA port for VXLAN transport is UDP 4789. If you will use hardware equipment take this in consideration
 
 VXLAN traffic is forwarded to a physical device; this device can be set (optionally) to be a VLAN tagged interface, but in that case you must make sure that the tagged interface is manually created first in all the Hosts.
 
 .. important::
 
     The network interface that will act as the physical device **must** have an IP.
 
+The bridge ``${PHYSDEV}.${VXLAN_ID}`` (PHYSDEV is the physical interface and VXLAN_ID is the VxLAN VNI) will be created and the VM NICs will be attached to it. This has a very important implication: **the amount of characters for a bridge name that iproute2 allows is 15**
+
+.. important::
+
+   If the physical interface name and the VNI are longer than 15 characters the deploy of any VM with that virtual network will fail. The solution can be creating an alternative name (alias) for the interface. For instance, if you have the interface ``en0s0f0p0``, you can execute
+
+   ``sudo ip link set en0s0f0p0 alias vx``
+
+   and use the physical device ``vx`` for the Virtual Network. 
+
+   This change DOES NOT PERSIST after a reboot (the command must be issued again or you should use netplan or some other software to make it persistent.
+
 Limited Count of VXLANs on Host
 --------------------------------------------------------------------------------