Thanks so much! It looks like this is going to be easier than I at first
suspected.
On Tue, May 14, 2013 at 2:08 PM, Ben Pfaff wrote:
> On Tue, May 14, 2013 at 12:07:46PM -0700, Nick wrote:
> > Ok that sounds better. So would it be best to use the same eth0 (or
> > whatever the physical interf
On Tue, May 14, 2013 at 12:07:46PM -0700, Nick wrote:
> Ok that sounds better. So would it be best to use the same eth0 (or
> whatever the physical interface name is) as the untagged network management
> device, or should I somehow create a virtual interface via OVS?
This is a FAQ.
Q: I created
Ok that sounds better. So would it be best to use the same eth0 (or
whatever the physical interface name is) as the untagged network management
device, or should I somehow create a virtual interface via OVS?
Also, if I:
1. Start the database server with an empty database
2. Start ovs-vswitchd
3.
On Mon, May 13, 2013 at 9:24 PM, Nick wrote:
> 5. Start ovsdb-server on one node (on a floating IP which would be an alias
> on eth0.mgmt), with a persistent storage data directory. If this server
> dies it will be automatically master elected (using our internal automation
> framework) on anoth
I'm working on a large-scale netbooted cluster configuration, which has
it's persistent data stored on a clustering filesystem for redundancy.
There is only one physical network link, where the untagged vlan is used
for management/filesystem replication, and tagged vlans are used for other
things.
