Document the need to open firewalld service frontend ports (Alma 9 and Redhat derivatives)

[brodriguez-opennebula]

Description In some cases, Redhat derivatives (i.e. Alma 9) defaults keep firewalld installed and working. OpenNebula does not provide currently service files, thus ports for critical services (i.e. onegate) are not opened.

To Reproduce

• Have an OpenNebula installation on Alma 9
• Install and start firewalld
• Access to onegate port won't be possible (the port will be closed)

Expected behavior

It is already in the documentation.

• [ ] onedeploy should automatically take care of this

Details

• Affected Component: All (external, firewall)
• Hypervisor: KVM
• Version: 6.8

Additional context Example files for the frontend services

# cat > /usr/lib/firewalld/services/opennebula-gate.xml << EOF
<?xml version="1.0" encoding="utf-8"?>
<service>
  <short>OpenNebula Gate</short>
  <description>OpenNebula service to provide information from/to instances</description>
  <port protocol="tcp" port="5030"/>
</service>
EOF

# cat > /usr/lib/firewalld/services/opennebula-sunstone.xml << EOF
<?xml version="1.0" encoding="utf-8"?>
<service>
  <short>OpenNebula Sunstone</short>
  <description>OpenNebula web interface (self contained)</description>
  <port protocol="tcp" port="9869"/>
</service>
EOF

# cat > /usr/lib/firewalld/services/opennebula-fireedge.xml << EOF
<?xml version="1.0" encoding="utf-8"?>
<service>
  <short>OpenNebula Fireedge</short>
  <description>OpenNebula Javascript web interface (self contained)</description>
  <port protocol="tcp" port="2616"/>
</service>
EOF

Progress Status

• [ ] Code committed
• [ ] Testing - QA
• [ ] Documentation (Release notes - resolved issues, compatibility, known issues)