LAA Subscriptions, Environments, Health Checks, and Users Levels - LKFT

LAA Subscriptions, Environments, Health Checks, and Users Levels - LKFT

This is a document that is meant to give as many details on how the LAA ecosystem works and clarify what each user has access to. You’ll find info on who to contact for more info, for example “how do I get a subscription“.

We will show how the LAA solution supports LKFT.

For LKFT the LAAs are just devices that can better isolate their DUTs. They already have jobs.

 

Please have a read here

 

 

Environments for LKFT

There are three environments:

  • Production: stable environment with official releases

  • Staging: environment under development and therefore tends to be unstable

  • Development: under continuous development, used for testing and new features

 

It is very important to seek direct approval from the Internal Manager of the LAA before moving an LAA is any environment. Especially in Prod!

 

The environments are supposed to be separate.

At the moment we have LAAs that are meant for development that are making use of both Staging and Production services. We will clear them out with time

Moving forward we will setup the LAAs to be working within one of the environment without cross-contaminations

 

LKFT has its own Prod and Stag environment on top of the LAA Prod environment.

While LKFT Dev is on top of the LAA Stag environment.

 

The WebServices associated to each environment are in the following table

We indicated the LAVA instances since that LKFT Frontend

This is the Environment structure for LKFT. Other projects can opt to be different.

 

LKFT Health Checks

  • These are custom health check to make sure more advanced features are available on the board

  • Example EUFI

  • They are used for the LKFT LAAs

  • They are defined by the LKFT team

  • They are assigned by the LKFT team

  • Visibility decided by the LKFT team