Inactive nodes will not start any new VMs, but they can be running VMs that were started while the node was active. This facilitates "draining" a VMM without forcibly killing any VMs.
Hopefully without collateral damage
Copy native jars, setup socket dir at install. Added junixsocket system property to run-services.sh Fixed AdminClient log configuration.
Using json serialization because type marshaling with RMI was getting freaky.
Avoided adding extra field to network assoc database table by encoding whether MAC is explicit in the MAC field itself (prefixed with 'X'). Since we aren't likely changing anything else in the schema for 2.6, this seems reasonable and simplifies upgrading. Up for discussion, however.
But now we probably need log rotation...
v# modified: autocommon/src/org/nimbustools/auto_common/confmgr/TransformerIdentity.java vv# modified: docs/src/examples/compact/metadata/vw-logistics.xsd v# modified: docs/src/img/5.png
Conflicts: service/client/java/source/src/org/globus/workspace/cloud/client/util/CumulusTask.java tests/bt-nimbus.sh
…d correctly in the image lookup