-gswitch installs the tools globally, usually in
/usr/local/bin, so that you can use them easily from the command line. Omit this switch if you'd rather the tools be installed in your home hierarchy, but you'll need to set your PATH appropriately.
SDC_URL: The URL of the CloudAPI endpoint.
SDC_KEY_ID: Fingerprint for the key you uploaded to Triton.
SDC_ACCOUNT: Your username; the login you use for Triton.
SDC_TESTING: If using a self-signed SSL certificate, set this to 1.
https://us-west-1.api.joyent.com. Each datacenter in a cloud has its own CloudAPI endpoint; a different cloud that uses Triton would have a different URL.
SDC_URLendpoint; please replace it with the URL of your datacenter(s). Note that CloudAPI always uses SSL/TLS, which means that the endpoint URL must begin with
~/.ssh/id_rsa.pubwith the path to the public key you want to use for signing requests.
--helpflag. For example:
ids for the image and package you want to use as the base for your instance.
triton image listor
sdc-listimagescommands; see the ListImages section below for a detailed explanation of these commands.
triton package listor
sdc-listpackagescommands; see the ListPackages section below for a detailed explanation of these commands.
--nameflag to name your instance; if you do not specify a name, Triton will generate one for you.
idof the image you'd like to use as the new instance's base.
idof the package to use to set instance dimensions. For the
tritoncommand, you can also pass the name of the image or the package instead of their id.
stateattribute will reflect this. Once the
stateattribute "running", you can login to your new instance (assuming it's a Unix-based instance), with the following:
adminuser on an instance. Note that the
adminuser has password-less sudo capabilities, so you may want to set up some less privileged users. The SSH keys on your account will allow you to login as
adminon your new instance.
triton instance list -o id,brandor
sdc-listmachines), you can manage the SSH keys that allow logging into the instance via CloudAPI. For example, to rotate keys:
--nameoption sets the name of the key. If you don't provide one, CloudAPI sets it to the name of the file; in this case
bhyve. Hardware virtual machines are static, and whatever keys were in your account at instance creation time are used, provided the OS inside KVM is a *nix.