search

openflighthpc / flight-control

0 stars 0 forks source link

OpenStack Support #18

Open ColonelPanicks opened 2 years ago

ColonelPanicks commented 2 years ago

Due to security concerns of OpenStack installations being a private cloud solution it is not a good idea for OpenStack support to be directly in Flight Control. For this reason there is a separate openstack server which will be setup on a separate server which will have access to the sites (ensuring that no auth keys or direct access to open stack is available to the Flight Control server).

I think it'd be best to have an application-wide setting for the OpenStack Usage API server IP/hostname. Flight Control can then use this IP to hit the endpoints described in the API notes.

timalces commented 2 years ago

Just an initial thought, but for the instance statuses we really need an endpoint (e.g. /status/PROJECT) for getting the statuses for all instances, not just one specified. As otherwise we will need some additional mechanism/ endpoint for determining all the current instance names and then querying each status one by one.