Capgemini/Apollo

Handle scaling / replacing of nodes in conjunction with provisioning ansible / weave network addresses / config

Open

#355 建立於 2015年6月30日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Python (725 star) (109 fork)batch import
bughelp wantedthinking

描述

When adding nodes to the cluster we will run into problems with the way we assign the weave bridge address, and scaling. We need to think about the approach for this. Some options off the top of my head (but needs way more thought)

  • form a tigher integration with terraform to derive the values of the bridges / CIDR (possibly).
  • use a fact from the machine being provisioned which is dynamic / unique per host
  • use the backend service discovery (consul) to populate the values, where consul would hold the master state of the cluster at any point

We also need to handle if nodes are removed / replaced in the cluster, without screwing up the rest of the cluster configuration and breaking the weave network.

This is discussed over here - https://github.com/Capgemini/Apollo/pull/351#commitcomment-11938353 https://github.com/Capgemini/Apollo/pull/351 https://github.com/Capgemini/Apollo/pull/342

貢獻者指南

技術棧
pythondocker
領域
infrastructuredevopscloud
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
unclear
前置要求
Apache Mesos basicsDocker containersWeave networkAnsible provisioning
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
Investigate the linked PRs (#351, #342) and associated comments to understand the current network configuration and provisioning approach. Explore the three options: tighter Terraform integration, dynamic per host facts, or Consul based master state. Determine how node replacement and scaling can be handled without breaking the Weave network. Consider proposing a design document or prototype for further discussion.