2025-03-14 12:30:36 +01:00
2025-04-28 14:39:53 +02:00
2025-04-28 14:39:53 +02:00
2025-04-28 14:39:53 +02:00
2025-06-16 09:13:43 +02:00
2024-10-03 09:40:38 +02:00
2025-06-16 09:13:43 +02:00
2025-04-01 10:09:25 +02:00

oc-datacenter OpenCloud shared service.

Manages user shared

To build :

bee generate routers
bee run -gendoc=true -downdoc=true

OR make dev

If default Swagger page is displayed instead of tyour api, change url in swagger/index.html file to :

url: "swagger.json"

Note on particular process :

  • set a bookin delete all related workflow booking before creating new ones. (no update of existing ones)

Admiralty

The routes in /admiralty will trigger actions on the DC's Kubernetes API to retrieve information on Admiralty resources.

Targets

Remote clusters that can be used by Admiralty to delegate pods.

To set up a target Admiralty needs to associate a secret which contains an edited version of the target's kubeconfig.

Once the Target is set the remote cluster appears in the output of kubectl get nodes under the name admiralty-<namespace>-<target name>-*

TODO : We might need a way to test if an IP is associated to an admiralty target

Docker Kube Settings

Set up your base64 key from your ~/.kube/config. Don't forget to set up your external IP in docker_datacenter.json

Admiralty

The routes in /admiralty will trigger actions on the DC's Kubernetes API to retrieve information on Admiralty resources.

Targets

Remote clusters that can be used by Admiralty to delegate pods.

To set up a target Admiralty needs to associate a secret which contains an edited version of the target's kubeconfig.

Once the Target is set the remote cluster appears in the output of kubectl get nodes under the name admiralty-<namespace>-<target name>-*

TODO : We might need a way to test if an IP is associated to an admiralty target

Docker Kube Settings

Set up your base64 key from your ~/.kube/config. Don't forget to set up your external IP in docker_datacenter.json

Admiralty

The routes in /admiralty will trigger actions on the DC's Kubernetes API to retrieve information on Admiralty resources.

Targets

Remote clusters that can be used by Admiralty to delegate pods.

To set up a target Admiralty needs to associate a secret which contains an edited version of the target's kubeconfig.

Once the Target is set the remote cluster appears in the output of kubectl get nodes under the name admiralty-<namespace>-<target name>-*

TODO : We might need a way to test if an IP is associated to an admiralty target

Description
Monitor owned datacenter activity
Readme 103 MiB
Languages
Go 97.5%
Dockerfile 1.6%
Makefile 0.9%