Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[vote] the name of component that provide governance ability in nodepool. #786

Closed
rambohe-ch opened this issue Mar 29, 2022 · 25 comments
Closed
Labels
kind/feature kind/feature

Comments

@rambohe-ch
Copy link
Member

rambohe-ch commented Mar 29, 2022

What would you like to be added:
In the proposal, a new component(named pool-spirit) will be added in the edge NodePool. the new component mainly provides the following ability:

  • To store metadata for NodePool as a kv storage
  • To provide a distributed lock for leader electing.
  • To use native kubernetes API to provide these above two abilities.

For these abilities, the name pool-spirit maybe make end user confused, so OpenYurt community have decided to rename the new component. all candidate names as following:

  • pool-spirit: 节点池精灵
  • pool-coordinator: 节点池协调器
  • pool-linker: 节点池连接器
  • pool-fort: 大本营
  • sheepdog:牧羊犬
  • yurt-minister: yurt主持
  • shepherd:牧羊人
  • hive: 蜂巢
  • pool-harbor: 节点池港口

please select your favourite name and reply this issue.

btw: other names for new component are also welcome.

@rambohe-ch rambohe-ch added the kind/feature kind/feature label Mar 29, 2022
@iutx
Copy link

iutx commented Mar 29, 2022

sheepdog+1

@rambohe-ch
Copy link
Member Author

sheepdog +1

1 similar comment
@njucjc
Copy link
Member

njucjc commented Mar 29, 2022

sheepdog +1

@zzguang
Copy link
Member

zzguang commented Mar 29, 2022

yurt-minister: yurt大臣/使节
(cloud->master, nodepool->minister)

@miskin-lee
Copy link

pool-coordinator+1

@zyjhtangtang
Copy link
Contributor

sheepdog +1

@donychen1134
Copy link
Contributor

pool-coordinator +1

@luc99hen
Copy link
Member

sheepdog +1

@ujnzxw
Copy link

ujnzxw commented Mar 29, 2022

shepherd +1
In my opinion, "shepherd" is a better name than "sheepdog".
The role of a Shepherd is a leader flock of sheep and manage them. A shepherd is a person who tends, herds, feeds, or guards flocks of sheep
But the primary role of a sheepdog is to assist the shepherd. The sheepdog assists the shepherd with gathering and handling the sheep.
Be a Shepherd Not a Sheepdog

@Congrool
Copy link
Member

sheepdog +1
@ujnzxw
From my perspective, sheepdogs are not only responsible for guarding sheep but also moving, managing and controling sheep. We can see that on wiki.

But the primary role of a sheepdog is to assist the shepherd.

I totally agree the opinion, and that is one of the reasons I prefer "sheepdog". Because this new component is used for nodepool-level autonomy when there're some nodes(sheep) offline. It will not replace the API Server(shepherd) at the cloud, which has stronger capability and manages the whole cluster, and only serve as an assistance.

@windydayc
Copy link
Member

yurt-minister +1

@ujnzxw
Copy link

ujnzxw commented Mar 29, 2022

sheepdog +1 @ujnzxw From my perspective, sheepdogs are not only responsible for guarding sheep but also moving, managing and controling sheep. We can see that on wiki.

But the primary role of a sheepdog is to assist the shepherd.

I totally agree the opinion, and that is one of the reasons I prefer "sheepdog". Because this new component is used for nodepool-level autonomy when there're some nodes(sheep) offline. It will not replace the API Server(shepherd) at the cloud, which has stronger capability and manages the whole cluster, and only serve as an assistance.

Thanks for your reply.
Based on my understanding, the project name is "OpenYurt", shepherd belongs to Yurt, API Server is the higher-level component than Yurt, we can call it "government", maybe.
Generally, one shepherd can only manage one flock of sheep at the same time, and the shepherd manages the sheep(edge nodes) far away from the Yurt. The shepherd can work standalone(autonomy), but the sheepdog cannot. And the sheepdog has no ability to determine which sheep is the HEAD of flocks of sheep(To provide a distributed lock for leader electing).

Maybe I have some misunderstanding about the project name or the role of this new component.
Anyway, either name is OK to me:)

@rambohe-ch
Copy link
Member Author

sheepdog +1 @ujnzxw From my perspective, sheepdogs are not only responsible for guarding sheep but also moving, managing and controling sheep. We can see that on wiki.

But the primary role of a sheepdog is to assist the shepherd.

I totally agree the opinion, and that is one of the reasons I prefer "sheepdog". Because this new component is used for nodepool-level autonomy when there're some nodes(sheep) offline. It will not replace the API Server(shepherd) at the cloud, which has stronger capability and manages the whole cluster, and only serve as an assistance.

Thanks for your reply. Based on my understanding, the project name is "OpenYurt", shepherd belongs to Yurt, API Server is the higher-level component than Yurt, we can call it "government", maybe. Generally, one shepherd can only manage one flock of sheep at the same time, and the shepherd manages the sheep(edge nodes) far away from the Yurt. The shepherd can work standalone(autonomy), but the sheepdog cannot. And the sheepdog has no ability to determine which sheep is the HEAD of flocks of sheep(To provide a distributed lock for leader electing).

Maybe I have some misunderstanding about the project name or the role of this new component. Anyway, either name is OK to me:)

@ujnzxw Very appreciate for your reply. we will keep this vote until 4.1(Friday) and wait for more discussion and vote.
According to the voting rules, we will finally choose the name with the most votes.

@casperakos
Copy link

yurt-minister +1

@dongzl
Copy link

dongzl commented Mar 31, 2022

pool-coordinator +1

1 similar comment
@qclc
Copy link
Member

qclc commented Mar 31, 2022

pool-coordinator +1

@GLTSC
Copy link

GLTSC commented Mar 31, 2022

shepherd +1

@cishidai
Copy link

pool-coordinator + 1

@h3ar7dump
Copy link

new proposal:
hive

@JcJinChen
Copy link
Member

pool-coordinator + 1

@Fei-Guo
Copy link
Member

Fei-Guo commented Mar 31, 2022

pool-coordinator +1 or new proposal: pool-harbor

@lorrielau
Copy link
Member

sheepdog+1

@showeriszero
Copy link

yurt-minister+1

@DrmagicE
Copy link
Member

pool-coordinator + 1

@rambohe-ch
Copy link
Member Author

more than 20 people have already voted, and the top three names are:

  • pool-coordinator 8votes
  • sheepdog 7votes
  • yurt-minister 3votes

so according to the voting rules, pool-coordinator becomes the name for the new component in NodePool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature kind/feature
Projects
None yet
Development

No branches or pull requests