Feature #174
Automatic XMPP system node creation
| Status: | Closed | Start: | 16/09/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | Christoph Dwertmann | % Done: | 0% |
|
| Category: | OMF Software | |||
| Target version: | OMF 5.3 |
Description
To make XMPP work, we need to have a system node (/Domain/System/10.0.0.37) for each node on the XMPP server before the node boots up for the first time. We only need to create it once, since it is persistent. We create it using a separate XMPP user (aggmgr) so that no testbed user can delete them.
To automate this, I can think of two solutions:- we build some kind of a "node checkin" procedure. A user runs a script and powers up a new node that should be introduced into the testbed. We read the MAC address from the DHCP request in the syslog, add the node to our inventory and create the XMPP system node for it.
- we build an XMPP gridservice. Whenever an experiment starts, the EC can ask the AM to create system nodes for all nodes that are part of the experiment to make sure they are there. Or alternatively, the EC can ask the AM to create a node if a node in the experiment does not enrol.
Related issues
| related to Feature #290: Post-install configuration script for all OM entities | Assigned | 07/05/2010 |
Associated revisions
updated omf command line topology syntax, RM now creates its own system node (default: /OMF/system/omf.nicta.hostname), closes #174
History
Updated by Christoph Dwertmann 12 months ago
- Assigned to set to Christoph Dwertmann
Interim solution for 5.2 release:
For each node in your testbed, run omf_create_sysnode 10.0.0.200 10.0.0.1, where the first parameter is the XMPP server address and the second is the node's address. This needs to be done only once for each node that is added to the testbed.
Updated by Christoph Dwertmann 9 months ago
- Status changed from New to Assigned
- Target version changed from Trunk to OMF 5.3
Updated by Christoph Dwertmann 25 days ago
System nodes are not needed anymore for EC-RC communication. Only the RM needs them, at it creates them itself. So there is no more need for a createnode script or any AM service to do that.
TODO: implement the automatic creation in the RM.