Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Provider Audit] provider.akash.colnetwork.com #711

Open
jars101 opened this issue Oct 26, 2024 · 7 comments
Open

[Provider Audit] provider.akash.colnetwork.com #711

jars101 opened this issue Oct 26, 2024 · 7 comments
Assignees

Comments

@jars101
Copy link

jars101 commented Oct 26, 2024

Prerequisite Steps:

1. Make sure your provider has community provider attributes and your contact details (email, website):

Done

2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)

root@akash-1:/home/user# host aaa.ingress.akash.colnetwork.com
aaa.ingress.akash.colnetwork.com is an alias for akash.colnetwork.com.
akash.colnetwork.com has address 161.10.254.22

3. Please make sure your Akash provider doesn't block any Akash specific ports.

Confirmed

Leave contact information (optional)

  1. Name: Jairo Rizzo
  2. Discord handle or Telegram handle: Colnet in Discord
  3. Contact email address: [email protected]
@shimpa1
Copy link

shimpa1 commented Oct 28, 2024

hi @jars101 ,
Provider name: provider.akash.colnetwork.com
Provider address: akash1hqnu7hg59jg4579p65s5zmukgqss6ev28yg0sg
Provider URI name resolution works?: YES
Provider Ingress name resolution works?: YES
Provider responding to orders?: NO
Deployment works?: NO
Network functional?: N/A
attributes OK?: NO
status endpoint works?: YES
GRPC status endpoint works?: YES

First provider attributes:
provider-services query provider get akash1hqnu7hg59jg4579p65s5zmukgqss6ev28yg0sg -o text
attributes:

  • key: organization
    value: colnetwork
  • key: arch
    value: amd64
  • key: tier
    value: community
  • key: email
    value: [email protected]
  • key: website
    value: colnetwork.com
  • key: region
    value: sa-west-1
  • key: capabilities/cpu
    value: intel
  • key: network-speed-up
    value: "1000"
  • key: network-speed-down
    value: "1000"
  • key: capabilities/storage/2/class
    value: beta3
    host_uri: https://provider.akash.colnetwork.com:8443
    info:
    email: ""
    website: ""
    owner: akash1hqnu7hg59jg4579p65s5zmukgqss6ev28yg0sg

This key-value pair:

  • key: capabilities/storage/2/class
    value: beta3

Pertains to persistent storage which your provider doesn't have. Please remove it.

The info section needs to be populated as well.

Also, your provider is not responding to orders.

Please fix those issues then we can continue.

thanks,
Shimpa

@jars101
Copy link
Author

jars101 commented Oct 28, 2024

Thank you for the update. Please see comments below:

a) Pertains to persistent storage which your provider doesn't have. Please remove it.
Done - this attribute has been removed from provider.yaml

b) The info section needs to be populated as well.
Done - added to provider.yaml

c) Also, your provider is not responding to orders.
Re-ran https://github.com/chainzero/provider-build-scripts/blob/main/providerBuild.sh with new address different than the one used when deploying.

####################################################
attributes:
- key: organization
value: colnetwork
- key: arch
value: amd64
- key: tier
value: community
- key: email
value: [email protected]
- key: website
value: colnetwork.com
- key: region
value: sa-west-1
- key: capabilities/cpu
value: intel
- key: network-speed-up
value: 1000
- key: network-speed-down
value: 1000
email: [email protected] # set your email here
website: colnetwork.com # set your website (if you have)

#########################################################

@jars101
Copy link
Author

jars101 commented Oct 29, 2024

Unfortunately, I have tried like 20 times to get orders to work but im still unable to do so. Discord channel not being very helpful. I have read the majority of the docs at https://akash.network/docs/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/ and https://akashengineers.xyz/provider-build-scripts/ multiple times.

@jars101
Copy link
Author

jars101 commented Oct 29, 2024

I honestly dont want to give up also when i have bough like 100 AKT already tryhing to set this up.

@shimpa1
Copy link

shimpa1 commented Oct 29, 2024

Of course not.
Contact me on Discord Directly.

@shimpa1
Copy link

shimpa1 commented Oct 29, 2024

Update:

Provider name: provider.akash.colnetwork.com
Provider address: akash1hqnu7hg59jg4579p65s5zmukgqss6ev28yg0sg
Provider URI name resolution works?: YES
Provider Ingress name resolution works?: YES
Provider responding to orders?: YES
Deployment works?: YES
Network functional?: YES
attributes OK?: YES
status endpoint works?: YES
GRPC status endpoint works?: YES

@andy108369
Provider akash1hqnu7hg59jg4579p65s5zmukgqss6ev28yg0sg ready to be signed

@jars101
Copy link
Author

jars101 commented Nov 1, 2024

Hello, so I redeployed my cluster from scratch and added 2 gpu worker nodes. One with a t4 and one with a rtx 3050 (this one is not yet listed by you so I opened akash-network/provider-configs#37 ) . Please advice if all ok . This is the final production cluster deployment with 3 control plane nodes + multiple workers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants