# Migration test -> prod HAPROXY --- # Sommaire - Haute Disponibilité (HA) : éviter les coupures en prod - Déploiement : copie de test à prod --- # Stratégies de déploiement - Blue Green Deployment - Rolling Deployment Ressources : [Ansible](https://docs.ansible.com/ansible/latest/playbook_guide/guide_rolling_upgrade.html#the-rolling-upgrade), [AWS](https://docs.aws.amazon.com/pdfs/whitepapers/latest/blue-green-deployments/blue-green-deployments.pdf#welcome), [Blog Personnel](https://blog.itaysk.com/2017/11/20/deployment-strategies-defined) --- # HA ![HA01](https://gricad-gitlab.univ-grenoble-alpes.fr/tienyoun/gdml_deployment/-/raw/main/doc/ha/gdml%20deployment%20HA1.png =80%x) --- # HA ![HA02](https://gricad-gitlab.univ-grenoble-alpes.fr/tienyoun/gdml_deployment/-/raw/main/doc/ha/gdml%20deployment%20HA2.png =80%x) --- # HA ![HA03](https://gricad-gitlab.univ-grenoble-alpes.fr/tienyoun/gdml_deployment/-/raw/main/doc/ha/gdml%20deployment%20HA3.png =80%x) --- # HA ![HA04](https://gricad-gitlab.univ-grenoble-alpes.fr/tienyoun/gdml_deployment/-/raw/main/doc/ha/gdml%20deployment%20HA4.png =80%x) --- # HA : Notes - Reverse proxy - X-Forwarded-For - Choix du logiciel : HaProxy, Nginx, Apache... - Rollback difficile (sauf si...) - Health checks - Serveur "sur demande" --- # Copie test -> prod - [ZFS](https://gricad-gitlab.univ-grenoble-alpes.fr/tienyoun/gdml_deployment/-/blob/zfs/prod_deploy.sh?ref_type=heads) - [rsync](https://gricad-gitlab.univ-grenoble-alpes.fr/tienyoun/gdml_deployment/-/blob/main/haproxy/prod_deploy.sh?ref_type=heads) --- | | ZFS | rsync | | ------------------------------------ | --- | ----- | | Abstraction hyperviseur | | x | | Simplicité/Complexité de maintenance | | x | | Simplicité/Complexité d'usage | | x | | Déduplication des données | x | | | Optimisation | x | | | Rollback | x | (?) | --- # Choix ? * **Rsync** : pour les petits datasets ou pour des fichiers "statiques" * **ZFS** : pour les grosses données (>)