Yes, the provider network provide a way for that use case.
And I proposed a blueprint [1] to be able to isolate ports on a same
network/subnet.
So in you case, if you set a provider network as a public network and if
you like to share this network between tenants, you will be able to isolate
l2 tr
Hi,
I also try to do that but I faced some troubles.
I explained and ask for that here
https://ask.openstack.org/question/633/create-vm-image-from-an-iso-containing-installation/
It could be help you.
Regards,
Édouard.
On Sat, May 18, 2013 at 7:49 AM, Martinx - ジェームズ
wrote:
> That is pretty c
OVS is not compatible with iptables + ebtables rules that are applied
directly on VIF ports.
So the libvirt_vif_driver 'nova.virt.libvirt.vif.LibvirtHybirdOVSBridgeDriver'
create a Linux software bridge to be able to apply security group rules
with iptables.
If you don't need the security group fu
And if you use libvirt virt driver, the hypervisor (libvirt+KVM in my case)
adds anti MAC and IP spoofing rules on VNICs of VM:
$ virsh nwfilter-list
UUID Name
991dbd1a-373b-a005-57b2-5b1f4107f653 al
works now, and I am appreciate if
> rebase and submit again, I can help review the code.:)
>
>
> On 01/24/2013 03:35 PM, Édouard Thuleau wrote:
>
> Hi,
>
> I'm glad that you confirm my first impression about this blueprint :-) I'm
> eager to help on this i
obsoleted the quantum blueprint now, it can be implemented
> from nova side and has no dependency to quantum any more, and I'll update
> the code and resubmit the code ASASP, hope it can be accepted before
> grrizzly-3.
>
>
> 2013/1/24 Édouard Thuleau
>
>> Hi all,
Hi all,
I took a look to the Nova blueprint [1] and I noticed that it depends on a
Quantum blueprint [2].
This blueprint [2] was created April 2012. Quantum is now able to
dynamically allocate ports and it's all Nova needs to implement this new
feature.
Can we obsoleted the Quantum blueprint [2]
Hi,
A blueprint was open to address this:
https://blueprints.launchpad.net/nova/+spec/multi-boot-instance-naming
Regards,
Édouard.
Le 2 janv. 2013 06:54, "heut2008" a écrit :
> Hi,all
>
> When booting multi instances at a time , we face a hostname naming
> problem, now all instances will us
s,
Édouard.
On Fri, Dec 7, 2012 at 6:45 PM, Édouard Thuleau wrote:
> The code doesn't make lot of change to the nova network manager code. It
> modifies principally the linux_net driver code.
>
> And I don't think we can consider it like a new feature. I think it's mor
so they aren't being deleted properly? In fact,
> that may be a bug. It looks like plug is called for each vm so we might end
> up with multiple copies of the isolation rules.
>
> Vish
>
> On Dec 3, 2012, at 6:34 AM, Édouard Thuleau wrote:
>
> Hi Vis
ifficult to make a
> patch that would remove them, but you will likely have to do some creative
> locking to make sure that you don't run into issues.
>
> Vish
>
> On Nov 20, 2012, at 9:25 AM, Édouard Thuleau wrote:
>
>> Hi all,
>>
>> I use nova-network
Hi all,
I use nova-network with VLAN manager.
Why nova-network doesn't remove unused network interfaces on a host ?
ie, if none VM on a host have a fixed IP attach to network X, the VLAN
and bridge of this network still up and unused. And 'dnsmasq' process
still listen and running.
The number o
a is gone too, or you are talking about DB entries?
>
>
> On Mon, Nov 12, 2012 at 11:08 AM, Édouard Thuleau wrote:
>>
>> I try to implement a simple way to automate the backup mechanism (eg.
>> every day): https://blueprints.launchpad.net/nova/+spec/backup-schedule
>>
I try to implement a simple way to automate the backup mechanism (eg.
every day): https://blueprints.launchpad.net/nova/+spec/backup-schedule
And I though of a solution to respond to your needs: when a node fails
(for any reasons), I disable it, I delete all servers was running on
it and I restart
14 matches
Mail list logo
