OPS can run on Microsoft Azure assuming your environment is setup.
Pre-requisites
Create a new resource group.
Create a storage account - that is your bucket.
You might need to login first.
az login --scope https://graph.windows.net//.default
Create a quickstart auth:
az ad sp create-for-rbac --sdk-auth > quickstart.auth
Create a role using the clientID as the assignee inside quickstart.auth:
az role assignment create --assignee dead-beef-feed-face --role Contributor
Most of the environment variables you need will be found in this json file.
Image Operations
Create Image
If you have already created an Ops project, you can update your existing config.json. You need to add CloudConfig which mentions specific details like ProjectID, BucketName.
Once, you have updated config.json you can create an image in Azure with the following command.
#!/bin/sh
# used for uploading blob
export AZURE_STORAGE_ACCOUNT="nanostest"
export AZURE_STORAGE_ACCESS_KEY=""
# used for create
export AZURE_SUBSCRIPTION_ID=""
export AZURE_LOCATION_DEFAULT=""
export AZURE_TENANT_ID=""
export AZURE_CLIENT_ID=""
export AZURE_CLIENT_SECRET=""
# used for everything?
export AZURE_BASE_GROUP_NAME="bob"
GOOS=linux go build -o gtest2
ops image create <elf_file|program> -c config.json -t azure -a gtest2
The newer version of ops uses Azure Galleries to store images as Azure has been moving away from their older image storage now. In fact most new instance types require it.
If you wish to override the default gallery name of 'nanos_gallery' you can export an env var like so:
export AZURE_GALLERY_NAME="my_new_gallery"
List Images
You can list existing images on Azure with ops image list.
By default, ops creates a VPC, a subnet and a security group per instance.
You can select a different VPC, subnet or security group using the configuration file. The keys to set are CloudConfig.VPC, CloudConfig.Subnet and CloudConfig.SecurityGroup.