There are two flavours of Control Plane deployments - Remote and Kubernetes. This guide will focus on deploying a Remote Control Plane on a single Linux remote host. Go to Kubernetes - Prepare A Cluster to deploy the Control Plane on Kubernetes Cluster instead.
Remote Host - Deploy Control Plane
Every Edge Compute Network ('ECN') starts with a Control Plane that allows us to manage ECN's resources.
In this guide, our Control Plane will deploy a single Controller instance on a remote host.
The following procedures will define resources in YAML for potctl to consume. Specification of those YAML resources can be found here.
We recommened going through the Keycloak Installation Guide before continuing on here.
Deploy a Control Plane on a Remote Host
Create a template of controlplane.yaml like so:
echo "---
apiVersion: datasance.com/v3
kind: ControlPlane
metadata:
name: albatros
spec:
iofogUser:
name: Foo
surname: Bar
email: [email protected]
password: iht234g9afhe
auth:
url: https://example.com/
realm: realm-name
realmKey: realm-key
ssl: exter
controllerClient: pot-controller
controllerSecret:
viewerClient: ecn-viewer
controllers:
- name: alpaca-1
host: 38.101.23.2
ssh:
user: bar
keyFile: ~/.ssh/id_rsa" > /tmp/controlplane.yaml
Make sure to edit the host, ssh.user, and ssh.keyFile fields to correspond with the remote host we are deploying to.
Once we have edited the fields to our liking, go ahead and run:
potctl deploy -f /tmp/controlplane.yaml
Verify the Deployment
We can use the following commands to verify the Control Plane is up and running:
potctl get controllers
potctl describe controller alpaca-1
potctl describe controlplane
Having our Control Plane up and running, we can now go to Setup Agents guide to deploy our Agents and finalize the ECN deployment.