[Provider Audit] provider.maintek.ch

[jackserippi]

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: "<your email>"
    website: "<your website>"

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

• More info on what DNS records should look like are available in the Akash Documentation here.

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

• If you are using a firewall, please follow this doc: https://akash.network/docs/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/#step-11---firewall-rule-review
• If you are behind NAT, then you need to make sure these ports are open between your provider worker nodes and the internet.

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. Jakob
2. Discord / jackserippl
3. info@maintek.ch

[shimpa1]

hi @jackserippi ,

The provider attributes are good.

The performance is quite low however. It's not mandatory for a provider to be fast however the user experience will not be great. A simple deployment took 20 minutes to load, something that usually takes 30 seconds. The provider can still get audited and signed.

Another much more serious issue is reliability. The provider is constantly going down and is unreachable. This is a hindrance in the auditing process. The provider needs to be up 24/7 in order to receive an audited status.

Shimpa

[jackserippi]

@shimpa1 Hi, yes I know It was a little bit to early to apply for the audit. I am reorganizing my storage completly, which caused the cluster to be down and heavly degreaded (Change from Raid to Ceph). Will be up 24/7 with high performance, when done.

[shimpa1]

OK, Please sort out the infrastructure and let us know when you're done. thank you, Shimpa

[andy108369]

Closing as stale. Provider is offline and it's been longer than a month.