The minimum configuration required can be instantiated by running:

cedana-orch bootstrap

which will guide you through the process and set up your local system for cedana.

There’ll be a lot of callouts for configuration here since most of it’s a work in progress right now and subject to change multiple times a day! (This should probably be a callout too)

A description of each piece of the configuration is below.

Cedana Configuration

cedana_managed

Set this to true if you’re using our migration systems for multi-cloud. Otherwise, cedana-orch functions without true multi-cloud migration support (although still supports instantiating instances across providers).

{
  "cedana_managed": true,
  "enabled_providers": [
    "aws", "paperspace"
  ],
 "shared_storage": {
    "mount_point": "/home/ubuntu/s3/",
    "dump_storage_dir": "/home/ubuntu/.cedana/"
  },
 "aws" : {
    "enabled_regions": ["us-east-1", "ap-southeast-1"],
    "enabled_instance_families": ["t2", "p4"],
    "ssh_key_path": "/path/to/ssh/key",
    "launch_template": "template"
  },
  "paperspace": {
    "api_key": "API_KEY",
    "ssh_key_path": "/path/to/ssh/key",
    "enabled_regions": ["East Coast (NY2)"]
  },
  "server_config": {
      "nats_addr": "NATS_ADDR",
      "nats_port": 4222,
      "auth_token": "AUTH_TOKEN"
  }
}

"server": {
    "network": {
      "addr": "locahost", 
      "port": 5000
    }

<aside> 💡 A lot of the functionality here is gated since it’s very much WIP and subject to change soon - as we shift the backend towards kubernetes.

</aside>