You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Draft in progress

Introduction

Like the other TIER distributions for larger production environments, the TIER Grouper solution will be built using Docker Swarm.  TIER will provide generic instructions and pointers on setting up the Docker environment for this solution but will not provide a pre-built virtual machine.  Schools needing a vm-based solution should focus on the TIER Grouper Appliance instead.

  1. Background & Requirements
    1. Migration of a Grouper installation to new platform requires:
      1. Full database backup and restore.
      2. Filesystem configuration files backup and restore
        1. Hopefully sites have some form of configuration management in place.  How to leverage this in a TIER context is a question.
    2. High vs. Standard Availability
      1. 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.
    3. Expandability
      1. Users will need the ability to install additional modules
      2. Provisioning and Integration
    4. Consider the use of supervisord for multi-process containers

  2. TIER Distribution Components
    1. 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.
    2. Grouper Web Services (HA)
    3. Grouper user interface (HA)
    4. Grouper message bus to AMQP (soon) HA
      1. TIER will select a product, likely RabbitMQ
    5. Grouper PSPNG (HA) for LDAP provisioning
    6. Shibboleth SP for authentication to Grouper UI

  3. Configuration Defaults and Options
    1. Web Services Authentication
      1. Apache basic
      2. LDAP
      3. future: certificate


  4. Implementation
    1. Containers
      1. Grouper UI Container
        1. Grouper UI
        2. Apache
        3. Shibboleth SP
      2. Grouper Web Services Container
        1. Grouper Web Services
        2. Apache
        3. Shibboleth SP
      3. Database
        1. TIER-provided MARIADB
      4. Grouper Loader
        1. Grouper Loader
        2. Java Application
      5. LDAP
        1. TIER LDAP (or none)
      6. Load Balancing
        1. Docker native vs. haproxy
        2. Sticky sessions are needed for the Grouper UI
    2. Default Configuration

  • No labels