Make provider attributes available in bids

[baktun14]

The scope of this is larger than just GPU attributes but GPU model is the biggest painpoint at this time.

When deploying for a GPU, the bid engine doesn't return the GPU model or vendor. This is crucial for users to know which provider to choose for which model, especially when deploying with a wildcard in the SDL.

Here's an example of a bid:

{
    "bid": {
        "bid_id": {
            "owner": "akash1...tkvk",
            "dseq": "12793097",
            "gseq": 1,
            "oseq": 1,
            "provider": "akash19p4t9d069nashxre9jg6j60cqlqkvtht6egpc9"
        },
        "state": "open",
        "price": {
            "denom": "uakt",
            "amount": "368.320765000000000000"
        },
        "created_at": "12793100"
    },
    "escrow_account": {
        "id": {
            "scope": "bid",
            "xid": "akash...tkvk/12793097/1/1/akash1...pc9"
        },
        "owner": "akash1...pc9",
        "state": "open",
        "balance": {
            "denom": "uakt",
            "amount": "5000000.000000000000000000"
        },
        "transferred": {
            "denom": "uakt",
            "amount": "0.000000000000000000"
        },
        "settled_at": "12793100",
        "depositor": "akash1...pc9",
        "funds": {
            "denom": "uakt",
            "amount": "0.000000000000000000"
        }
    }
}

Also, if the protobuf types are to change for the bids, I think it would be a great idea to also add the model/vendor chosen on the deployment or lease. Currently on the deployment, we can see the model/vendor requested, but not the one leased.

[baktun14]

Also, I think it would be a great idea to have something generic to handle other specs/attributes than GPUs, like the type of CPU offered or memory or disk etc etc. To not have to change the protobuf type later on. Something like an attribute array.

[anilmurty]

Oct 17 sync: This will need a network upgrade

[brewsterdrinkwater]

Oct 24 sync:

• attributes are bound to hardware.
• Artur took into account future cases, so this is all included in the network upgrade.
• Max wants to include provider attributes.
• The only attributes available after the network upgrade is GPU. Other attributes will be there, but not used at this stage.
• Future changes will not need an upgrade.
• Artur is happy with the spec. Will be sharing later today.
• Will be shared with clients ASAP.
• Will sync with internal team for Network upgrade.

[brewsterdrinkwater]

oct 31st:

• API part is done.
• Network upgrade migration is implemented.
• Going through testing right now. Testnetify tool needed to be updated for use in testing network upgrade.
• Need to chat with Cloudmos guys on supporting client

[anilmurty]

Nov 7:

• Finalized updates to the blockchain and verified that network upgrade works
• Once the end-to-end tests and verified, will be able to cut a release
• Mainnet upgrade is set for Nov 20th