Does anyone know if it is possible to install bundles "remotely". That is, if I have an application at another site (so it has a RHQ Server managing several nodes with RHQ Agents running on them), can I install something like an ant bundle that will check with my centralized website (via rhq:url or rhq:url-archive - I know how to do this part), where what is downloaded are new and/or modified ant bundles? These would need to be installed without operator intervention. Is this possible?
I don't quite understand what it is you are asking. Can you give an example or more details of this use case? It seems like you want to install an ant bundle on a remote machine without having to go through the RHQ server-agent architecture to do so? Need more info.
Yes, it is hard for me to describe what I am seeking - sorry!
I am focusing on the "Provisioning" capability of RHQ. To this end, consider that I might have 3 installations, each at a different client site, each of which knows nothing about one another. Nor do I have the capability to access the main RHQ Server installed at each site. How would a general model for unknown future installs/updates occur in such a deployment? [Further, the number of sites really needs to scale to the order of 1000's].
An idea I had would be to create a bundle that executes periodically on the server node itself and checks with a centralized "update site" created for this purpose. This particular bundle would be installed with the initial installation of the system. When it found something new, what would it need to do? I am looking for help here, but my guess was that it might find a new "bundle" that would need to be installed. This new bundle might be an update to existing software deployed at that site, or it might be a new feature/subsystem to be installed there for the first time. If this is the way to go, how would that bundle be installed via the other bundle? If this is not the way to go, then what is the proper way to achieve this?
thanks again for anyone's help!
Something like this could be achieved using a custom server plugin that you would have to write yourself [1]. This plugin would have to be installed on all the (independent) RHQ servers. The plugin would check the remote location for your new/updated bundles and then call the bundle subsystem on each particular RHQ server to deploy them.
[1] https://docs.jboss.org/author/display/RHQ/Server+Plugin+Development
On Thursday, January 03, 2013 12:44:58 Joe Gamache wrote:
Does anyone know if it is possible to install bundles "remotely". That is, if I have an application at another site (so it has a RHQ Server managing several nodes with RHQ Agents running on them), can I install something like an ant bundle that will check with my centralized website (via rhq:url or rhq:url-archive - I know how to do this part), where what is downloaded are new and/or modified ant bundles? These would need to be installed without operator intervention. Is this possible?
I don't quite understand what it is you are asking. Can you give an example or more details of this use case? It seems like you want to install an ant bundle on a remote machine without having to go through the RHQ server-agent architecture to do so? Need more info.
Yes, it is hard for me to describe what I am seeking - sorry!
I am focusing on the "Provisioning" capability of RHQ. To this end, consider that I might have 3 installations, each at a different client site, each of which knows nothing about one another. Nor do I have the capability to access the main RHQ Server installed at each site. How would a general model for unknown future installs/updates occur in such a deployment? [Further, the number of sites really needs to scale to the order of 1000's].
An idea I had would be to create a bundle that executes periodically on the server node itself and checks with a centralized "update site" created for this purpose. This particular bundle would be installed with the initial installation of the system. When it found something new, what would it need to do? I am looking for help here, but my guess was that it might find a new "bundle" that would need to be installed. This new bundle might be an update to existing software deployed at that site, or it might be a new feature/subsystem to be installed there for the first time. If this is the way to go, how would that bundle be installed via the other bundle? If this is not the way to go, then what is the proper way to achieve this?
thanks again for anyone's help! _______________________________________________ rhq-users mailing list rhq-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/rhq-users
rhq-users@lists.fedorahosted.org
-
Joe Gamache -
Lukas Krejci