[Container-tools] vagrant-service-manager as proxy to systemctl services

[Hardy Ferentschik]

Hi there,

I wanted quickly wanted to get some feedback on a design decision regarding vagrant-service-manager.

According to my understanding, vagrant-service-manager "is designed to enable easier access to the features 
and services provided by the Atomic Developer Bundle (ADB)." At least that is also the objective from the 
README. 

The question is around the term "services". In the context of vagrant-service-manager services are 
docker, openshift, kubernete, (mesos). The higher level components we are managing for the user to use
the ADB/CDK. These might be system services (systemd), but they also might be just a bunch of running 
Docker containers. 

There is an outstanding pull request [1] for vagrant-service-manager which adds a start/stop
to the already existing 'vagrant service-manager restart <service>'. Adding start/stop makes sense,
but as a side effect it also allows and documents that now any systemd service can be controlled 
via 'vagrant service-manager [start|stop|restart] <service>'. This is the part I am not so happy about.
I think we go too far in this case on what the vagrant-service-manager can and should do. It is
not its responsibility to control systemd services. 

I am also concerned that the term 'service' gets now overloaded in the context of the plugin. Once meaning
systemd service once functional service as provided by ADB/CDK to fulfill container based tasks. 

I am interested to hear what others thing in this regard or whether I stand alone with my concerns.

--Hardy


[1] https://github.com/projectatomic/vagrant-service-manager/pull/219 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/container-tools/attachments/20160524/c3fb6636/attachment.sig>