Support parallel deployments and SDL group deployments

[cloud-j-luna]

This provider needs to be performant and allow deployments to happen in parallel. Several resources can be created without specifying all of them in a single SDL. This allows for fine grained control over the resources through the Terraform state.

This issue will be updated with more detailed information as this gets investigated.

Limitations

Due to the way the Akash Network works, the DSEQ value is changed every block which is ~6 seconds at the time of this writing, thus for every deployment creation in that time frame the DSEQ is the same.

Cosmos SDK anti-replay

If the same account attempts multiple transactions within the same block - the account sequence mismatch message will be triggered. This safeguard is explained in this document:

https://docs.cosmos.network/v0.44/modules/auth/02_state.html

To counter this a locking mechanism in a per-block basis could be implemented so that operations could happen in parallel with a ~1 block (~6 seconds) interval between them. This solution is detailed below.

Features

The provider must:

• Handle deployments on the same block from the same account
• Handle deployment groups on the same/different providers (check Multiple Providers Deployment)
• Provide filtering of providers in a per GSEQ fashion.

Multiple Providers Deployment

A deployment could be deployed to multiple providers in this type of example SDL:

---
version: "2.0"

services:
  supermario:
    image: pengbai/docker-supermario 
    expose:
      - port: 8080
        as: 80
        to:
          - global: true

profiles:
  compute:
    supermario:
      resources:
        cpu:
          units: 0.1
        memory:
          size: 256Mi
        storage:
          size: 256Mi
  placement:
    akash:
      pricing:
        supermario: 
          denom: uakt
          amount: 10000
    akash2:
      pricing:
        supermario: 
          denom: uakt
          amount: 10000
    akash3:
      pricing:
        supermario: 
          denom: uakt
          amount: 10000

deployment:
  supermario:
    akash:
      profile: supermario
      count: 1
    akash2:
      profile: supermario
      count: 1
    akash3:
      profile: supermario
      count: 1

In order to support this SDL the provider must know how to handle multiple GSEQs for a given DSEQ, this requires a change in the structure used to identify deployments in the deployment which consists of 1 DSEQ, 1 GSEQ and 1 OSEQ. It must now support many GSEQ and treat each one as a bidding and leasing target (to be confirmed).

[cloud-j-luna]

Relevant links:
https://forum.cosmos.network/t/sending-txs-multiple-times-in-quick-succession-from-the-same-sender-account-fails/3363/3