Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A ansible-sc_pack-public
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • public-items
  • ansible-sc_pack-public
  • Issues
  • #16

Closed
Open
Created Mar 11, 2021 by Vladir@vladirOwner

haproxy for CDN like recipes

There are several things we need to put in place here:

  • we need to use what we implement at #15, to have the haproxy template in the accelerator database with the right tags. For that Carlos and Vladir discussed that we can have several defaults regarding the more common haproxy templates we use here https://gitlab.zunzun.se/public-items/ansible-sc_pack-public/-/blob/develop/roles/create_deploy_type_cdn/defaults/main.yml, so if nothing is passed as haproxy template content on the recipe we take one of those defaults (we need to document that somehow).
  • sc_pack pull command should be run so that we get the <install_dir>/haproxy/data/haproxy.cfg stored for all the deployments of the tags passed.
  • Symbolic link <install_dir>/haproxy/data/haproxy.cfg -> /srv/haproxy/data/haproxy.cfg
  • run systemctl daemon-reload so that the haproxy.cfg change is got,
  • run systemctl restart haproxy
Assignee
Assign to
Time tracking