Hi David, If your external network has DHCP, then this should just work.
If not, then you can: * Statically configure an IP address on your All-In-One node. * Run "service clearwater-auto-config-generic restart && service clearwater-infrastructure restart". * Stop all of the Clearwater processes using "service X stop", where the processes are ellis, bono, sprout, cassandra, memcached, restund, mysql, chronos, homestead, homestead-prov and homer. Note that you don't need to restart the processes as monit will restart them (and explicitly starting can mean that you end up with two instances of the process trying to run). Ellie From: [email protected] [mailto:[email protected]] On Behalf Of David Ferry Sent: 19 March 2014 01:41 To: [email protected] Subject: [Clearwater] Switching the All In One OVF image to Bridged Adapter? Hi We're trying to get our TAS on a particular subnet to communicate with Clearwater on the same subnet. We're wanting to use the Clearwater all in One OVF, so that we don't have to do an install of clearwater. We want to change the VirtualBox networking config so that clearwater isn't behind a VirtualBox NAT. I.e. we want the Clearwater OVF image to just appear on our own subnet using VirtualBox bridged adaptor. Then we could talk to the TAS easily, and not muck around with installs of clearwater. Is this something that can be changed within the Clearwater All in One, or will we bump into many gotchas and end up having less pain by just doing a clearwater install? Regards David
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
