...
- Background & Requirements
- Migration of a Grouper installation to new platform requires:
- Full database backup and restore.
- Filesystem configuration files backup and restore
- Hopefully sites have some form of configuration management in place. How to leverage this in a TIER context is a question.
- High vs. Standard Availability
- While we believe that the majority of schools operate Grouper without High Availability, some schools do operate the web services components of Grouper in HA mode.
- Expandability
- Users will need the ability to install additional modules
- Provisioning and Integration
- Consider the use of supervisord for multi-process containers
- Migration of a Grouper installation to new platform requires:
- TIER Distribution Components
- Grouper Database (HA)
The database may be TIER supplied or Campus provided. Configuration options for must be available for either scenario. TIER will use MARIADB. - Grouper Web Services (HA)
- Grouper user interface (HA)
- Grouper message bus to AMQP (soon) HA
- TIER will select a product, likely RabbitMQ
- Grouper PSPNG (HA) for LDAP provisioning
- Shibboleth SP for authentication to Grouper UI
- Grouper Database (HA)
- Configuration Defaults and Options
- Web Services Authentication
- Apache basic
- LDAP
- future: certificate
- Web Services Authentication
- Implementation
- Containers
- Grouper UI Container
- Grouper UI
- Apache
- Shibboleth SP
- Grouper Web Services Container
- Grouper Web Services
- Apache
- Shibboleth SP
- Database
- TIER-provided MARIADB
- Grouper Loader
- Grouper Loader
- Just needs Java
- LDAP
- TIER LDAP (or none)
- Load Balancing
- Docker native vs. haproxy
- Sticky sessions are needed for the Grouper UI
- Grouper UI Container
- Misc
- time sync in all containers
- Default Configuration
- Containers