Sorry about the confusion!
I have two nodes, with two network interfaces each. One configured with 192.*
IP and one with 133.*
I can access them with SSH directly at 133.*
Both nodes can ping one another and both nodes can ping Internet addresses e.g.
google. com
No other router available fo
Okay, I believe I see what you're going for now. Are you planning on
assigning 133.* addresses directly to your guest instances?
On Wed Nov 19 2014 at 5:53:36 PM Dimitrakakis Georgios
wrote:
> Sorry about the confusion!
>
> I have two nodes, with two network interfaces each. One configured with
Yes!
I am planning to assign 133.* IP addresses to all guest instances.
Best,
George
On Thu, 20 Nov 2014 02:42:08 +, Aaron Segura wrote:
Okay, I believe I see what youre going for now. Are you planning on
assigning 133.* addresses directly to your guest instances?
On Wed Nov 19 2014 at
Excellent!
You're going to want to remove the 192.* addresses and make sure both NICs
are cabled to the same layer-2 network. One NIC will have your 133.*
address (host management and API access), and one will be completely
unnumbered (VM traffic).
So, if you have your 133.* NIC plugged in to on
Hi Aaron!
Once again I 'd like to thank you a lot for the time spending with me.
I totally understand what you are saying that I should do but as you
have guessed there is a problem. The problem is that the Datacenter
informed me that it's not possible to change the cabling and connect the
19
Hi George!
Sorry, I've been fairly busy the last day. Can you tell me more about how
you intend to use this implementation? When you say you want to use 10Gb
for "all internal communications", what does that encompass? API calls?
VM-to-VM traffic? Please provide as much detail as you can in re
Aaron,
thank you for your time. I totally understand that you 've been busy.
I would like to use the 10Gbit network for OpenStack communications
(physical machine-to-physical machine communication, start/stop VMs from
controller, transfer images and create snapshots over it, API calls,
VM-to-
