Site planning check list
The purpose of this document is to act as a check list when planning and preparing sites for Avassa Edge Applications. Make sure you have understood each check-box and read corresponding documentation. This will guarantee a smoother site deployment phase. Reach out to Avassa support for guidance if needed.
Plan and design
- Validate host requirements (Linux distribution, kernel options, memory, disc etc)
- Is multi-tenancy required?
- Design tenant resource profiles
- Site and host onboarding
- Which unique key is to be used for host identification?
- Optionally require client certificates.
- Optionally enable the unclaimed hosts list
- Requirements on Edge Enforcer and application upgrade windows
- Validate application requirements
- Ingress IP: availability of IP addresses on site, DHCP or pool allocation?
- Required application mounts?
- Plan volumes and partitions for your hosts
- Is Inter application networking needed? (Shared network or ingress IPs)
- Log retention, log archiving (see configuration on container logs)
- Host networking required?
- GPU passthrough
- NVIDIA container toolkit is needed on hosts
- Resource constraints - Configure profiles to constrain application resource consumption
- Site networking
- When disconnected - how Control Tower reacts when sites are disconnected
- Outgoing ports to reach Control Tower
- Inter host networking for Edge Enforcers on site
- Preferred network for Edge Enforcer communication
- Site proxy - For networks where the Edge Enforcer cannot directly connect to Control Tower.
- Local unseal - Should a host be allowed to unseal itself without any connection to Control Tower or site Edge Enforcers?
Plan site configuration in Control Tower
- Plan site config for:
- Site naming conventions
- Ingress IP
- Local unseal
- When disconnected
- Labels
- Device and GPU discovery labels
See tutorial on adding a site