akash-network / community

Starting point for joining and contributing to building Akash Network
MIT License
55 stars 28 forks source link

[Provider Audit]: provider.digilob.net #639

Closed digilob1 closed 1 month ago

digilob1 commented 4 months ago

Prerequisite Steps:

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

  Example:
  $ provider-services query provider get akash1<REDACTED> -o text
  ...
  attributes:
  ...
  - key: host
  value: akash
  - key: tier
  value: community
  info:
    email: info@digilob.net

Ref documentation:.

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

host <anything>.ingress.<yourdomain>

Example:

$ host anything.ingress.akash.pro
anything.ingress.akash.pro is an alias for nodes.akash.pro.
nodes.akash.pro has address 65.108.6.185

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)

  1. Name - digilob
  2. Discord handle - digitallobster
  3. Contact email address - info@digilob.net
shimpa1 commented 4 months ago

hi @digilob1 , There's a few provider attributes missing:

provider-services query provider get akash1fhe99jw8yz35pr9z7g7cn6tnea3hyxzxmf84sa -o text attributes:

The info: section needs to be pupulated. If you have installed the provider using Praetor, please

If you have installed using standard Akash Helm charts installation, please

We can continue after that is completed

thank you,

digilob1 commented 4 months ago

@shimpa1 I've updated the provider.yaml file.

andy108369 commented 2 months ago

@shimpa1 I've updated the provider.yaml file.

@digilob1 the info sections is still empty:

$ provider-services query provider get akash1fhe99jw8yz35pr9z7g7cn6tnea3hyxzxmf84sa -o text
attributes:
- key: organization
  value: digilob
- key: arch
  value: amd64
- key: host
  value: akash
- key: tier
  value: community
- key: email
  value: info@digilob.net
host_uri: https://provider.digilob.net:8443
info:
  email: ""
  website: ""
owner: akash1fhe99jw8yz35pr9z7g7cn6tnea3hyxzxmf84sa

And email shouldn't be a part of the provider attribute, but the info field.

Please refer to Attributes of Community Providers section in https://akash.network/docs/providers/audited-attributes/

In your case you basically only need to remove the email provider attribute and add email: info@digilob.net without the indentation (i.e. without the empty spaces before that line), and then apply the changes (the provider helm chart update)

andy108369 commented 1 month ago

Closing this as the provider is no longer active and the owner has not been responsive.