| Re: Stopping puppet on hn stops it in all VE [message #14746 is a reply to message #14732] |
Mon, 09 July 2007 13:48   |
ugob
Messages: 271
Registered: March 2007
|
Senior Member |
|
|
| n00b_admin wrote on Mon, 09 July 2007 06:16 |
This is a "problem" i also ran into.
You do not run any services on the hn that you run on the ve's.
|
I know we should not run any real services on the HN, but I still need to monitor/configure it. For example, crond works perfectly on the HN and when I do a 'service crond stop' on the HN, it only stops the instance on the HN, not in the VEs.
| n00b_admin wrote on Mon, 09 July 2007 06:16 |
I don't know how the puppet daemon works but i presume it works as a client-server (as far as i understood from their wiki), so you run the master on the hn and the clients on the ve's.
That should not pose any problems. Again if i understood correctly how puppet works.
|
There is no problem running puppet on the HN, except for this problem. Well, the service tests on the HN are not done correctly, because if you tell puppet to make sure crond runs on the HN, it will say it is running even if it is not, because it sees all the VE's instances. I'll try monitoring the HN with nagios instead, but I'll still be configuring the HN with puppet.
Thanks,
Please read the manual before asking questions:
http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf
Please have a look at the wiki before asking questions:
http://wiki.openvz.org/Main_Page
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
