New gateway registration flow (Console)

[kschiffer]

Summary

Congruently to #3522, we also want to revisit the gateway registration flow, which is currently too verbose and has many options that are usually not relevant during registration. Additionally, we can use templates of the device repository once we add support for gateways.

Why do we need this?

Gateway onboarding is currently not smooth.

What is already there? What do you see now?

Gateway registration using the gateway registration form.

What is missing? What do you want to see?

• Many UX improvements
  • Remove irrelevant fields
  • Revisit use flow
  • Allow limit frequency plan selection for gateways #3823
• Onboarding assistance from the device repository

How do you propose to implement this?

This issue is currently still a bit of a stub. I will follow up timely with wireframes to make this issue actionable. Implementation will likely happen in two stages:

1. Clean up of the current onboarding without device repository
2. Addition of onboarding via device repository to provide two onboarding modes, congruently with end device onboarding

How do you propose to test this?

While doing so, we should also extend the gateway end-to-end tests accordingly.

Can you do this yourself and submit a Pull Request?

I'll follow up with the wireframes and then we can decide who picks up the implementation.

[johanstokking]

• Clean up of the current onboarding without device repository

Let's start with this indeed.

Do you need a list of fields that are advanced, with their default values? That would eliminate already some fields that are always shown now.

[johanstokking]

Other things in scope:

• Ability to set antenna placement (indoor or outdoor) (refs Edit gateway antenna placement #4324)
• Filter frequency plans (refs Allow limit frequency plan selection for gateways #3823, probably needs gateways in device repository)

[johanstokking]

Should we triage this then? @NicolasMrad

[kschiffer]

@mjamescompton

Here's the scaffold I would suggest for this:

Let me know if you have any questions. You can also refer to my comment on end device onboarding. Many notes are relevant for this as well.

Again, here's the full wireframe:
https://github.com/TheThingsNetwork/lorawan-stack/files/8715860/220517_integrated_gateway_onboarding_01.pdf

Note that there are two onboarding flows, based on whether the gateway is claimable or not (<GatewayRegistrationFormSection /> and <GatewayClaimFormSection />). Please make sure to resolve any unclarities about it before starting the implementation. Thanks!

[johanstokking]

References also TheThingsNetwork/lorawan-devices#124.

If there's anything needed that is generic for a particular gateway and model, we might want to load that from the device repository too.

[kschiffer]

The new gateway onboarding foundation (as laid out here: #3947 (comment)) was just merged and is now available in OS and Enterprise.

I'm leaving this issue open since there are still some missing bits:

• Allow limit frequency plan selection for gateways #3823
• Extending the device repository to include gateways, and making that available through the Console Add support for gateways lorawan-devices#124

@mjamescompton is currently working on updating the documentation accordingly.

[KrishnaIyer]

The two remaining items here depend on https://github.com/TheThingsIndustries/lorawan-stack/issues/2018. I'm removing the milestone on this until we resolve the blocker.

[kschiffer]

I would even suggest to close this and track the rest of the progress in #2018 and a new issue once this is resolved.