k8s heat templates are confusing master with minion
Bug #1608923 reported by
Piotr Parczewski
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
Low
|
Drago |
Bug Description
k8s master is the first instance being spawned by bay creation - however, it's configured with 'minion' user. This is highly confusing.
Steps to reproduce:
1. Use devstack with magnum.
2. Create bay with coe = kubernetes
Changed in magnum: | |
assignee: | nobody → rajiv (rajiv-kumar) |
To post a comment you must log in.
There are two possibilities for solution:
1) Change the user name from the minion to some generic name, not dependant on the role of the instance. Name can be something describing driver name or used base image. So choices might be
a) kubernetes
b) fedora/coreos
2) Change the user name of the instance hosting master, from the "minion" to "master" and keep minion user name as it is.
No. 2 option introduce little complexity into the code. For just user name, we have to add extra code and maintain it. Now it has to be decided whether it is worth implementing or not.
No. 1.b suffer from the same disadvantage of No 2.
No. 1.a is easy to implement and does not require addition of extra code, just name from "minion" to generic name(TBD) will be changed.