vider external networks as well
as in the transparent patching hooks within that block is up to the
provider I guess. Just a tiny abstract idea out of the top of my head that
I can detail in the specs if there's a tiny interest/match with what is
required?
Thanks,
Best Regards,
Racha
On Th
+1
On Thu, Jul 31, 2014 at 1:31 AM, Aaron Rosen wrote:
> +1!
>
>
> On Thu, Jul 31, 2014 at 12:40 AM, Nikola Đipanov
> wrote:
>
>> On 07/30/2014 11:02 PM, Michael Still wrote:
>> > Greetings,
>> >
>> > I would like to nominate Jay Pipes for the nova-core team.
>> >
>> > Jay has been involved wi
Hi,
Does it make sense also to have the choice between ovs-ofctl CLI and a
direct OF1.3 connection too in the ovs-agent?
Best Regards,
Racha
On Tue, Jun 17, 2014 at 10:25 AM, Narasimhan, Vivekanandan <
vivekanandan.narasim...@hp.com> wrote:
>
>
> Managing the ports and plumbing
that
enable that in Nova and apply it to your installation, and voila you can
have nova boot VMs with multi vnics on same neutron. If you want to test
your setup with a public cloud provider that allow that, you can loock in
to Amazon EC2.
Best Regards,
Racha
On Wed, Apr 16, 2014 at 3:48 AM, V
Hi Bob,
Thanks a lot for answering my question regarding the simultaneous operation
of mechanism drivers (that wasn't probably clear enough in my first email).
Best Regards,
Racha
On Tue, Mar 18, 2014 at 12:52 PM, Robert Kukura wrote:
>
> On 3/18/14, 3:04 PM, racha wrote:
>
; could also be used so
that the first responding MD matching the filter will assign itself.
Thanks for your answer.
Best Regards,
Racha
On Mon, Mar 17, 2014 at 3:17 AM, Mathieu Rohon wrote:
> Hi racha,
>
> I don't think your topic has something to deal with Nader's topics.
(as
in the provider segmentation type/id/etc) so that ML2 assigns a mechanism
driver to the virtual network? The other alternative I guess is to create
another integration bridge managed by a different Neutron instance? Probably
I am missing something.
Best Regards,
Racha
On Fri, Mar 7, 2014 a
