Closed jmhands closed 3 weeks ago
hi JM, welcome back,
These are your current attributes:
provider-services query provider get akash1kkjkd0pv0c7r53luacjj6aeaaalerjjnh7z9kv -o text attributes:
There's a few missing attributes:
The "tier" value should be set to "community"
The "organization" key is missing;
I presume you will want to do Chia plotting, please use:
The persistent storage should be set to beta3 (you are using nvme drives I presume). The other keys should be deleted.
In case your provider does not have persistent storage, all keys pertaining to it should be removed.
Next, upon trying to deploy a beta3 workload (a wordpress site) your provider did not place a bid. The inventory operator does not seem to be aware of any persistent storage. Please go through the steps explained here: https://akash.network/docs/providers/build-a-cloud-provider/helm-based-provider-persistent-storage-enablement/ Please feel free to skip those steps in case you do not plan on having persistent storage enabled.
thanks,
Shimpa
awesome, hit me up again to catch up sir!!
I'm adding 12 more nodes next week with NVMe, should I just leave beta3 on and set the others to false?
--set attributes[8].key=capabilities/storage/1/class --set attributes[8].value=beta1 \
--set attributes[9].key=capabilities/storage/1/persistent --set attributes[9].value=true \
--set attributes[10].key=capabilities/storage/2/class --set attributes[10].value=beta2 \
--set attributes[11].key=capabilities/storage/2/persistent --set attributes[11].value=true \
--set attributes[12].key=capabilities/storage/3/class --set attributes[12].value=beta3 \
--set attributes[13].key=capabilities/storage/3/persistent --set attributes[13].value=true \
Sounds good! Just delete the others referencing either beta1 or beta2. I can help you on Discord, might be faster.
all right I just turned off for now, should be ready to verify. I will get more comfortable with the ceph / rook before I add back in. Please add me again on Discord! you have DMs off 😉
@andy108369 Provider akash1kkjkd0pv0c7r53luacjj6aeaaalerjjnh7z9kv ready to be signed
@andy108369 Provider akash1kkjkd0pv0c7r53luacjj6aeaaalerjjnh7z9kv ready to be signed
Signed. Apologies for the delay.
@jmhands I suggest you topping up the provider balance a bit more than it currently has ~0.49 AKT
Prerequisite Steps:
1. Make sure your provider has community provider attributes and your contact details (email, website):
Ref documentation:.
2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)
Example:
3. Please make sure your Akash provider doesn't block any Akash specific ports.
Audit Steps:
1. Title the issue: " [Provider Audit]: Provider Address" (e.g. "[Provider Audit]: provider.europlots.com")
2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed.
3. If there are issues during the provider Audit, debug those issues, and Audit will be complete.
4. Audit Issue will be closed by core team member.
Leave contact information (optional)