Hi all,
Has anyone written a logger to dump all rabbitmq logs in an OpenStack
deployment?
Thanks.
-Simon
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More h
Hi folks,
(Resending, since I did something wrong with the subject last time...)
I wonder if there is a way to intentionally allow ip "spoofing" for certain
VMs...
The use case is the following. We have two DCs, both have openstack
deployed. One tenant lives on both DCs, say 10.0.0.0/24 in DC1 a
Salvatore,
This is a very interesting concept... I can see it being useful in our
production environments...
I wonder if we can make this a bit more general than "public or
not"... Think about a generic ownership and "mode bits" concept of networks.
For example, the infrastructure owner can crea
Narayan,
If you do net.bridge.bridge-nf-call-iptables = 0 on the network
controller, does floating IP still work? For each tenant/network, a subnet
is created, and the nova-network has a .1 gateway configured on the bridge
with the vlan interface plugged in.
The packets from VMs are actually sen
Xu (Simon) Chen
> wrote:
> > Narayan,
> >
> > If you do net.bridge.bridge-nf-call-iptables = 0 on the network
> controller,
> > does floating IP still work? For each tenant/network, a subnet is
> created,
> > and the nova-network has a .1 gateway configured o
com> wrote:
>
> Yup, that has definitely helped, thanks a bunch Xu.
>
>
> Regards,
>
> Wael
>
>
>
> On Jul 20, 2012, at 8:09 AM, Xu (Simon) Chen wrote:
>
> Yes, one solution is to modify the iptables driver, so that you don't SNAT
> for internal sub
l host, are able to communicate to each other via
> their private IPs.
>
> Has anyone faced this issue before?
>
>
> Regards,
>
> Wael
>
>
>
> On Jul 21, 2012, at 5:36 AM, Xu (Simon) Chen wrote:
>
> Here is what happened on a different thread:
> http:
Hi all,
I am running devstack and got a dev instance of OpenStack running.
I am happy to see the concept of multiple floating IP pools, and the
per-floating-ip interface in the trunk, which I consider a very good basis
for my blueprint proposal here:
https://blueprints.launchpad.net/nova/+spec/mu
My two cents...
The current multi-host mode is really making the assumption that if the NC
running in the dom0 is gone, all the VMs are likely screwed anyway.
When you are talking about a middle-ground, you'll need to handle NC
failures and load-balance among the NCs. You'll also need to worry ab
9 matches
Mail list logo
