Zenoss ZenTech Community

I am looking for a complete documentation of serviced. I made some search on Google with no success.

A complete documentation of serviced is mandatory if you want to correctly manage Zenoss 5.

Subject:	http://controlcenter.io/docs
Author:	Jan Garaj
Posted:	2016-01-08 13:18

http://controlcenter.io/docs/index.html

+ serviced -h

+ source code https://github.com/control-center/serviced

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch

Subject:	I am not surprised about this
Author:	[Not Specified]
Posted:	2016-01-14 04:25

I am not surprised about this answer, still it is not the answer that I expected.

Subject:	What is missing there?
Author:	Jan Garaj
Posted:	2016-01-14 04:32

What is missing there

Subject:	There is a command help:
Author:	[Not Specified]
Posted:	2016-01-14 04:57

There is a command help: serviced -h

There is a technical doc Control Center : http://controlcenter.io/docs/index.html. Not really helpful.

There is source code. No time for this.

There is no man page. For example, what's the difference with:

serviced service shell,

serviced service attach

serviced service run

serviced script run

etc.

This is just an example. In fact, there is no man page describing extensively the serviced command.

This is important since each time to deploy zenoss (we have four environments completely isolated), I failed to install percona since there was a proxy problem. Yes, core-autodeploy does not work behind a proxy, so I have to add at some places proxy definitions. I failed to add it for percona installation because of the lack of doc. Therefore I have to modify the script, and fiddling with serviced commands quite blindly. By the way, I had also to remove every google calls, for PCI/DSS reasons.

Another really annoying point is the difficulty to "port" modifications from one environment to another. I made a try with ZenPacks, and I completely messed up an environment, which is no more usable. Therefore, we are using VMware snapshot before manipulating Zenoss. We KNOW that Docker has also a snapshot mechanism, but the VMWare one is far more easier to use. And I know I can trust it.

Subject:	Use -h for each particular
Author:	Jan Garaj
Posted:	2016-01-14 05:33

Use -h for each particular command. For example serviced service shell -h. To be honest you need docker background first. Serviced is only docker orchestration tool.

Autodeploy is (my) community project. Zenoss company doesn't have any responsibility. It's not solution for everything. Definitely it's not proper automation. And if you need PCI/DSS compatibility, then run away from third party scripts as this autodeploy script. BTW: GA calls are there for my QA analysis.

BTW: It'll be awesome if you contribute back to community. Could you create PR about proxy support please

Subject:	Here is the point:
Author:	[Not Specified]
Posted:	2016-01-14 05:50

Here is the point:

-------------

serviced service shell -h

NAME:

serviced service shell - serviced service shell SERVICEID [COMMAND]

USAGE:

serviced service shell [global options] command [command options] [arguments...]

------------

# serviced service attach -h

NAME:

serviced service attach - serviced service attach { SERVICEID | SERVICENAME | DOCKERID | POOL/...PARENTNAME.../SERVICENAME/INSTANCE } [COMMAND]

USAGE:

serviced service attach [global options] command [command options] [arguments...]

----------

How can I get the difference between the two

Subject:	Where to find a complete documentation of serviced
Author:	[Not Specified]
Posted:	2016-01-08 07:54

Where to find a complete documentation of serviced