.yml
or .yaml
."2.0"
is accepted.services
entry contains a map of workloads to be ran on the Akash deployment. Each key is a service name; values are a map containing the following keys:image
depends-on
command
args
expose
is a list describing what can connect to the service. Each entry is a map containing one or more of the following fields:port
as
accept
proto
tcp
,http
, or https
)port
value governs the default proto
value as follows:port
proto
defaultexpose.to
is a list of clients to accept connections from. Each item is a map with one or more of the following entries:service
global
true
or false
false
global
is true, any client can connect from anywhere (web servers typically want this).global
is false
, only the services in the current datacenter can connect. If a service name is given and global
is true
, services in other datacenters for this deployment can connect.global
is false
then a service name must be given.profiles.compute
is map of named compute profiles. Each profile specifies compute resources to be leased for each service instance uses uses the profile.web
having resource requirements of 2 vCPUs, 2 gigabytes of memory, and 5 gigabytes of storage space available.cpu
units represent a vCPU share and can be fractional. When no suffix is present the value represents a fraction of a whole CPU share. With a m
suffix, the value represnts the number of milli-CPU shares (1/1000 of a CPU share).1
0.5
"100m"
"50m"
memory
, storage
units are described in bytes. The following suffixes are allowed for simplification:k
Ki
M
Mi
G
Gi
T
Ti
P
Pi
E
Ei
profiles.placement
is map of named datacenter profiles. Each profile specifies required datacenter attributes and pricing configuration for each compute profile that will be used within the datacenter. It also specifies optional list of signatures of which tenants expects audit of datacenter attributes.westcoast
having required attributes {region="us-west"}
, and with a max price for the web
and db
compute profiles of 8 and 15 uakt
per block, respectively. It also requires that the provider's attributes have been signed by the accounts akash1vz375dkt0c60annyp6mkzeejfq0qpyevhseu05
and akash1vl3gun7p8y4ttzajrtyevdy5sa2tjz3a29zuah
.signedBy
section allows you to state attributes that must be signed by one or more accounts of your choosing. This allows for requiring a third-party certification of any provider that you deploy to.deployment
section defines how to deploy the services. It is a mapping of service name to deployment configuration.deployment
. This entry is maps datacenter profiles to compute profiles to create a final desired configuration for the resources required for the service.web
service should be deployed to a datacenter matching the westcoast
datacenter profile. Each instance will have the resources defined in the web
compute profile available to it.