Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • slapos slapos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Merge requests 129
    • Merge requests 129
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedinexedi
  • slaposslapos
  • Merge requests
  • !519

caddy-frontend: Publish only active slaves from main partition

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Łukasz Nowak requested to merge luke/slapos:fix/caddy-frontend-no-publish-destroyed-slave into master Mar 01, 2019
  • Overview 8
  • Commits 1
  • Pipelines 0
  • Changes 3

As some of the nodes can lag behind, the system can be in state, that those nodes will send inactive (also destroyed) slave publish information. Before publishing it to master, check if each of slaves is really present on master.

Tasks:

  • prove it really works on simulated environment
  • check impact on massive simulated environment
  • cover with a test (optionally)
  • check test results with this change
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: fix/caddy-frontend-no-publish-destroyed-slave
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7