weixin_39677870 2020-11-21 21:55
浏览 0

Incremental deploys

Still needs plenty of work, but opening up early for feedback.

Right now I am adding a field to the SingularityPendingDeploy object that will track the progress of an incremental deploy as it goes along. This new field is an object that holds information about the current target number of instances and rate at which the deploy should proceed.

Still to-do: - [x] Better scheduling of upcoming tasks. Right now it's just keying off of numMissingInstances, but since we know the time between deploy steps, we can go ahead and schedule them - [x] Make it play nice with load balancer add/remove. Regular deploys add everything all at once when the deploy succeeds, this will need to do it per-task - [x] Surface more information about what is happening in the deploy, if you aren't watching the logs it's kind of mysterious right now - [x] Option to manually move the deploy forward or backward a step (should be fairly straightforward since we have the info in the SingularityPendingDeploy object) - [x] Tests, tests, tests, tests, tests.... - [x] UI

/cc

该提问来源于开源项目:HubSpot/Singularity

  • 写回答

5条回答 默认 最新

  • weixin_39677870 2020-11-21 21:55
    关注

    The basics are working now. All deploys now use a similar system where progress is tracked in the pending deploy object, incrementing a target number of instances for each step of the deploy. By default the number of instances per deploy step is the total instances (i.e. everything at once like before) unless a deployRate is set that then determines how many instances to deploy in each 'step'. Load balancer actions are triggered at the end of each step.

    Some info is surfaced in the ui now on the request page, but the wording/design could probably still be a bit cleaner.

    评论

报告相同问题?