2024-08-13 11:17:09 +02:00
|
|
|
# oc-datacenter OpenCloud shared service.
|
|
|
|
|
|
|
|
|
|
Manages user shared
|
|
|
|
|
|
|
|
|
|
To build :
|
|
|
|
|
|
|
|
|
|
bee generate routers
|
|
|
|
|
bee run -gendoc=true -downdoc=true
|
|
|
|
|
|
2025-03-06 09:33:38 +01:00
|
|
|
OR
|
|
|
|
|
make dev
|
|
|
|
|
|
2024-08-13 11:17:09 +02:00
|
|
|
If default Swagger page is displayed instead of tyour api, change url in swagger/index.html file to :
|
|
|
|
|
|
|
|
|
|
url: "swagger.json"
|
|
|
|
|
|
2024-08-30 10:55:35 +02:00
|
|
|
Note on particular process :
|
2025-02-19 12:28:48 +01:00
|
|
|
- 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`.
|
2025-02-19 12:28:48 +01:00
|
|
|
|
|
|
|
|
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`.
|
2025-02-19 12:28:48 +01:00
|
|
|
|
|
|
|
|
Once the Target is set the remote cluster appears in the output of `kubectl get nodes` under the name `admiralty-<namespace>-<target name>-*`
|
|
|
|
|
|
2025-02-19 14:40:56 +01:00
|
|
|
**TODO** : We might need a way to test if an IP is associated to an admiralty target
|
|
|
|
|
|
2025-02-17 08:33:19 +01:00
|
|
|
# Docker Kube Settings
|
|
|
|
|
|
|
|
|
|
Set up your base64 key from your ~/.kube/config.
|
2025-02-19 12:28:48 +01:00
|
|
|
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
|
