SkyCluster Configuration#

SkyCluster Secret#

You need to create a secret containing a public key and a private key for the skycluster to authenticate itself with its components. The secret should be created in the skycluster namespace.

First export your public and private keys (adjust the paths to your keys):

export PUBLIC_KEY=$(cat ~/.ssh/id_rsa.pub)
export PRIVATE_KEY=$(cat ~/.ssh/id_rsa | base64 -w0)

And then run the following command to generate the secret:

curl -s https://skycluster.io/configs/skysecret-cfg.sh | bash

Alternatively, you can create a secret using a YAML file below:

apiVersion: v1
kind: Secret
metadata:
  namespace: skycluster
  name: public-private-key
  labels:
    skycluster.io/managed-by: skycluster
    skycluster.io/secret-type: keypair
type: Opaque
stringData:
  config: |
    {
      "publicKey": "ssh-rsa AAAAB3NzaC1yc...fKEgCExt6YjE= ubuntu@cluster-dev1",
      "privateKey": "LS0tLS1CRUdJTiBPUEVOU1..gS0VZLS0tLS0K"
    }

SkyCluster Post-installation Configuration#

After installing SkyCluster, you need to configure the providers you want to use. This includes setting up OpenStack providers and setting the latencies between registered regions and zones.

SkyCluster OpenStack Provider Configuration#

Note

This step is only required if you are using OpenStack and have enalbed it during the installation of SkyCluster.

For each OpenStack provider, you need to create a YAML file containing the essential mapping information for the provider. Use the YAML template below and provide the appropriate values for each field:

providerMappings:
  openstack:
    regions:
      - name:  # Name of the region
        region: # Name of the region
        regionAlias: # Alias of the region
        subnetCidr: x.y.z.0/24
        gatewayIp: x.y.z.1
        zones:
          # There should be at least one zone specified as default
          # for each region
          - name: default
            locationName:
            # the default zone is identified by setting
            # the defaultZone to true
            defaultZone: true
            type: cloud # Type of the zone (cloud, nte, edge)
            # flavors specifies the mapping between the flavor names
            # and the actual machine types in the OpenStack provider
            # within this <zone>.
            flavors:
              small:  n1.small
              medium: o1.medium
              large:  p1.medium
              xlarge: p3.large
              x.8G:   n1.medium
              x.16G:  o1.medium
              x.32G:  p1.medium
        # iamges specifies the mapping between the image names
        # and the actual image names in the OpenStack provider
        # within this <region>. We assume images are available
        # in all zones within the region.
        images:
          ubuntu-22.04: Ubuntu-22-04-Jammy
          ubuntu-20.04: Ubuntu-20-04-focal
          ubuntu-18.04: Ubuntu-18-04-bionic

We use the following settings for the SAVI testbed.

providerMappings:
  openstack:
    regions:
      - name: SCINET
        region: SCINET
        regionAlias: SCINET
        subnetCidr: 10.30.10.0/24
        gatewayIp: 10.30.10.1
        zones:
          - name: default
            locationName: Toronto
            defaultZone: true
            type: cloud
            flavors:
              small:  n1.small
              medium: o1.medium
              large:  p1.medium
              xlarge: p3.large
              x.8G:   n1.medium
              x.16G:  o1.medium
              x.32G:  p1.medium
        images:
          ubuntu-22.04: Ubuntu-22-04-Jammy
          ubuntu-20.04: Ubuntu-20-04-focal
          ubuntu-18.04: Ubuntu-18-04-bionic
      - name: VAUGHAN
        region: VAUGHAN
        regionAlias: VAUGHAN
        subnetCidr: 10.29.10.0/24
        gatewayIp: 10.29.10.1
        zones:
          - name: default
            locationName: Toronto
            defaultZone: true
            type: cloud
            flavors:
              small:  n1.small
              medium: o1.medium
              large:  p1.medium
              xlarge: p1.medium
              x.8G:   n1.medium
              x.16G:  o1.medium
              x.32G:  p1.medium
        images:
          ubuntu-22.04: Ubuntu-22-04-Jammy
          ubuntu-20.04: Ubuntu-20-04-focal
          ubuntu-18.04: Ubuntu-18-04-bionic

After creating the YAML file above, run the following command to configure the OpenStack provider:

helm install skycluster skycluster/skycluster \
  --set postInstall=true -f os-provider-setting.yaml

Latency Configuration#

Currently, SkyCluster automatically configures the latencies between regions and zones. The calculated latencies depends on the type and location of the provider. Table below summarizes how the latencies is calculated between different regions and zones based on our experiments and measurements from AWS. We will introduce automatic latency measurement in future releases.

Same Continents:

Source	Destination	Latency
Cloud	Cloud	100ms
Cloud	NTE	25ms
NTE	Edge	15ms
Edge	Edge	6ms
NTE	NTE	10ms
NTE	Edge	8ms

Different Continents, traffic between different continents is routed through the Cloud region.

Source	Destination	Latency
Cloud	Cloud	200ms

Crossplane Configuration#

SkyCluster utilizes Crossplane to manage the cloud resources. We create a series of composition and XRDs and use them to build our abstraction system on top of them. To install all required compositions and XRDs, run the following command:

curl -s http://skycluster.io:8000/crossplane/lists.txt | \
  while read url; do \
    curl -s "$url" | kubectl apply -f - ; done