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.

Deploy a Control Plane on a Remote Host

Create a template of controlplane.yaml like so:

echo "---
apiVersion: iofog.org/v3
kind: ControlPlane
metadata:
  name: albatros
spec:
  iofogUser:
    name: Foo
    surname: Bar
    email: user@domain.com
    password: iht234g9afhe
  auth:
    url: https://example.com/
    realm: realm-name
    realmKey: realm-key
    ssl: exter
    controllerClient: pot-controller
    controllerSecret:
    viewerClient: ecn-viewer
  events:
    auditEnabled: true
    retentionDays: 14
    captureIpAddress: true
  nats:
    enabled: true
  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:

iofogctl deploy -f /tmp/controlplane.yaml

Verify the Deployment

We can use the following commands to verify the Control Plane is up and running:

iofogctl get controllers

iofogctl describe controller alpaca-1

iofogctl describe controlplane