threefoldtecharchive / 0-robot

Distributed live cycle management system
Apache License 2.0
0 stars 0 forks source link

find another way then automatically installing node service to register capacity #19

Closed rkhamis closed 6 years ago

rkhamis commented 6 years ago

Issue migrated from [https://api.github.com/repos/zero-os/0-robot/issues/211](), opened by @zaibon

in the case of the node robot, now since 76794ce the node robot automatically installed a node service on the robot to allow automatic registration of the node. This means the secret of this node service is own by no one. Not even the farmer that own the node. This is wrong cause the node service provide useful actions like reboot, info, .... Things that a farmer should be able to schedule

One possible solution would be to extract the capacity registration action from the node template and move it into its own template and install this template instead of the node one. So farmer can still create the node template themself and access the service normally

rkhamis commented 6 years ago

commented by @zaibon registration has been extracted (https://github.com/zero-os/0-templates/commit/e23fc12f81b8e252f209119cbdd1d07f8262c7a7) I'm not merging yet, cause I need to change code in 0-robot to install the new registration service instead of the node service.

zaibon commented 6 years ago

fixed in https://github.com/threefoldtech/0-templates/commit/3f74a78d51726d4f7d86386d423f1e12c787897a