Closed rafi16jan closed 10 years ago
On Wed, 2014-10-01 at 08:30 -0700, farrell16jan wrote:
I'm stuck at configuring the hw-daemon, I use the openvz kernel and the owp at the same server, so according to INSTALL file (that really-really not giving me guidance) where I should put the /utils/hw-daemon at this server? (cause it's mentioned that "Next step is to generate unique key, which will be used for authorization between panel and daemon.") And do I need to make two of that in different directory and port and then run two of them? Or just one at this server?
You only need the hw-daemon on the hardware node itself, you don't install it in any containers. (I assume you installed owp into a container? If so, you don't install hw-daemon in that container.)
Jesse Norell Kentec Communications, Inc. 970-522-8107 - www.kci.net
excuse me, it's a little stupid asking this, according to https://openvz.org/Hardware_Node it's mentioned "Hardware Node (otherwise known as host system) is a term used in OpenVZ documentation. Basically it means the physical server on which OpenVZ is installed and running." So, what is the difference between the container and the physical server on which openvz is installed and running (hardware node)? I thought they're in the same meaning. And what should I need to start using OpenVZ?
please heeelpp!!
On Wed, 2014-10-01 at 15:40 -0700, farrell16jan wrote:
excuse me, it's a little stupid asking this, according to https://openvz.org/Hardware_Node it's mentioned "Hardware Node (otherwise known as host system) is a term used in OpenVZ documentation. Basically it means the physical server on which OpenVZ is installed and running." So, what is the difference between the container and the physical server on which openvz is installed and running? I thought they're in the same meaning
The hardware node refers to the OS on the server which loads the kernel; containers are virtual environments where you typically install applications (like a webserver, email server, or whatever). You can/normally do run many containers on a single hardware node.
Eg. you might have one container running your web server, another for your email, and another for your dns service. You could run a container specifically for owp, which is probably a recommended way to set it up (that's what we do).
So the hardware node runs the hw-daemon. A container runs owp, which you configure to talk to the hw-daemon on that hardware node, and to the hw-daemon on any other hardware nodes you might add in the future. Then you can use owp to create additional containers on the hardware node, one for your web server, one for your dns server, etc.
more clear now?
Issue tracker is not for personal support queries, it's for bug reports (and bug reports should contain all necessary information). Please read https://github.com/sibprogrammer/owp/wiki/Support
I'm stuck at configuring the hw-daemon, I use the openvz kernel and the owp at the same server, so according to INSTALL file (that really-really not giving me guidance) where I should put the /utils/hw-daemon at this server? (cause it's mentioned that "Next step is to generate unique key, which will be used for authorization between panel and daemon.") And do I need to make two of that in different directory and port and then run two of them? Or just one at this server?