Nebula front end , fireedge , mysql in separate server

Hi I am installing opennebula 10 in Alma 9.

Front-end - Alma 9
Firedge - Alma 9
Mysql - Rocky 9

I have made connection between frontend and db when comes to front end and firedge i cound int make a connection

[root@e2e-70-108 ~]# tail -f /var/log/one/fireedge.log
[2025-04-07T13:34:16.506Z] - [info] worker: user.info, [-1,false]: undefined
[2025-04-07T13:34:16.506Z] - [error] 59.93.245.90 - - [07/Apr/2025:13:34:16 +0000] “GET /fireedge/api/user/info HTTP/1.1” 500 44 “http://164.52.202.108:2616/fireedge/sunstone” "Mozilla…
[2025-04-07T13:34:20.104Z] - [error] [object Object]
[2025-04-07T13:34:20.105Z] - [error] 59.93.245.90 - - [07/Apr/2025:1

fireedge configuration:

Server Configuration

System log (Morgan) prod or dev
log: prod

Enable cors (cross-origin resource sharing)
cors: true

FireEdge server IP
host: ‘0.0.0.0’

FireEdge server port
port: 2616

OpenNebula: use it if you have oned and fireedge on different servers
one_xmlrpc: ‘http://164.52.202.111:2633/RPC2

Flow Server: use it if you have flow-server and fireedge on different servers
oneflow_server: ‘http://164.52.202.111:2474

JWT expiration time (minutes)
session_expiration: 180

JWT expiration time when using remember check box (minutes)
session_remember_expiration: 3600

Minimum time to reuse previously generated JWTs (minutes)
minimum_opennebula_expiration: 30

Endpoint to subscribe for OpenNebula events must match those in
oned.conf
subscriber_endpoint: tcp://localhost:2101

Log debug level: GitHub - winstonjs/winston: A logger for just about everything.
0 = ERROR, 1 = WARNING, 2 = INFO, 5 = DEBUG

debug_level: 2

Maximum length of log messages (chars)
Messages exceeding this limit will be truncated
-1 => No limit
truncate_max_length: 150

################################################################################
Global API Timeout
################################################################################

This configuration option sets the maximum time (in milliseconds) that the application
will wait for a response from the server before considering the request as timed out.
If the server does not respond within this timeframe, the request will be aborted,
and the connection will be closed.
api_timeout: 120_000

Guacamole daemon
guacd:
port: 4822
host: ‘localhost’

Local zone in a Federation setup
This attribute must point to the Zone ID of the local OpenNebula to which this FireEdge belongs to.
default_zone:
id: 0
name: ‘OpenNebula’
endpoint: ‘http://164.52.202.111:2633/RPC2’ ( frontend-ip)

Authentication driver for incoming requests
opennebula: the authentication will be done by the opennebula core using the
driver defined for the user
remote: performs the login based on a Kerberos X-Auth-Username header
provided by authentication backend
auth: ‘opennebula’

This configuration is for the login button redirect. The available options are: “/”, “.” or a URL
auth_redirect: ‘/’
~

can u say where i am missing . Waiting for reply.

This is fixed

Can you share the fix? or how you solve it?

Sure ,
since i change here /etc/one/fireedge-server.conf

OpenNebula: use it if you have oned and fireedge on different servers

one_xmlrpc: ‘http://164.52.202.111:2633/RPC2

Flow Server: use it if you have flow-server and fireedge on different servers

oneflow_server: ‘http://164.52.202.111:2474

This attribute must point to the Zone ID of the local OpenNebula to which this FireEdge belongs to.
default_zone:
id: 0
name: ‘OpenNebula’
endpoint: ‘http://164.52.202.111:2633/RPC2’ ( frontend-ip)

I also change this in frontend server
su - oneadmin

onezone update OpenNebula

ENDPOINT=“http://164.52.202.111:2633/RPC2

before it was ENDPOINT=“http://localhost:2633/RPC2

Also change one-flow , onegate configuration files as per this . now its working.

Could please confirm any more steps to do ? Waiting for your reply .

1 Like