From 62714bb13cfde51ce6210dba626d7248847ba8c1 Mon Sep 17 00:00:00 2001 From: rsum1 <48501208+rsum1@users.noreply.github.com> Date: Sun, 7 Mar 2021 18:22:55 -0800 Subject: [PATCH] updates links to stay at docs.akash (#141) --- SUMMARY.md | 2 ++ design/README.md | 16 ++++++++-------- sdl/README.md | 2 +- sdl/deployment.yaml | 2 +- 4 files changed, 12 insertions(+), 10 deletions(-) diff --git a/SUMMARY.md b/SUMMARY.md index ff8cb30c..9fb7129c 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -22,6 +22,8 @@ * [API Service](/guides/node/api-service.md) * [Run a Validator](/guides/node/validator.md) * [Become a Provider](/guides/provider/README.md) +* [Common Commands](/guides/general-commands.md) +* [Upgrade to Akashnet-2](/guides/upgrade-mainnet.md) ## Documentation diff --git a/design/README.md b/design/README.md index 543ba1f2..0472954a 100644 --- a/design/README.md +++ b/design/README.md @@ -20,15 +20,15 @@ Deploying applications onto [Akash](https://github.com/ovrclk/akash) involves tw Given that there are live providers on the network, the lifecycle of a typical application deployment is as follows: -1. The tenant describes their desired deployment in \[SDL\], called a [deployment](../marketplace.md#deployment). +1. The tenant describes their desired deployment in \[SDL\], called a [deployment](/design/marketplace.md#deployment). 2. The tenant submits that definition to the blockchain. -3. Their submission generates an [order](../marketplace.md#order) on the \[marketplace\]. -4. Providers that would like to fulfill that [order](../marketplace.md#bid) bid on it. -5. After some period of time, a winning [bid](../marketplace.md#bid) for the [order](../marketplace.md#order) is chosen, and a [lease](../marketplace.md#lease) is created. -6. Once a [lease](../marketplace.md#lease) has been created, the tenant submits a [manifest](../provider-services.md#manifest) to the provider. -7. The provider executes workloads as instructed by the [manifest](../provider-services.md#manifest). +3. Their submission generates an [order](/design/marketplace.md#order) on the marketplace. +4. Providers that would like to fulfill that order [bid](/design/marketplace.md#bid) on it. +5. After some period of time, a winning [bid](/design/marketplace.md#bid) for the [order](/design/marketplace.md#order) is chosen, and a [lease](/design/marketplace.md#lease) is created. +6. Once a [lease](/design/marketplace.md#lease) has been created, the tenant submits a [manifest](/sdl/README.md) to the provider. +7. The provider executes workloads as instructed by the [manifest](/sdl/README.md). 8. The workload is running - if it is a web application it can be visited, etc... -9. The provider or tenant eventually closes the [lease](../marketplace.md#lease), shutting down the workload. +9. The provider or tenant eventually closes the [lease](/design/marketplace.md#lease), shutting down the workload. # Features @@ -42,7 +42,7 @@ Tenants define workloads requirements, as well as regional and pricing parameter ## Networking -Networking - allowing connectivity to and between workloads - can be configured via the [SDL](../documentation/sdl.md) for a deployment. +Networking - allowing connectivity to and between workloads - can be configured via the [SDL](/sdl/README.md) for a deployment. By default, workloads in a deployment group are isolated - nothing else is allowed to connect to them. This restriction can be relaxed by enabling diff --git a/sdl/README.md b/sdl/README.md index 742949ac..3a22e1bc 100644 --- a/sdl/README.md +++ b/sdl/README.md @@ -13,7 +13,7 @@ An example deployment configuration can be found [here](deployment.yaml). ### version -Indicates version of Akash configuration file. Currently only `"1.5"` is accepted. +Indicates version of Akash configuration file. Currently only `"2.0"` is accepted. ### services diff --git a/sdl/deployment.yaml b/sdl/deployment.yaml index 957c19c6..cc8e0dd7 100644 --- a/sdl/deployment.yaml +++ b/sdl/deployment.yaml @@ -1,5 +1,5 @@ --- -version: "1.0" +version: "2.0" include: - "foo.yml"