Hello,
Toni, that's the question !
Good news :) I'will go into the source code.
If you have a link to point me to the right direction, i take it ;)
Regards,
2013/10/8 Antoni Segura Puimedon <asegurap(a)redhat.com>
----- Original Message -----
> From: "Mike Kolesnik" <mkolesni(a)redhat.com>
> To: "Benoit ML" <ben42ml(a)gmail.com>
> Cc: users(a)ovirt.org
> Sent: Tuesday, October 8, 2013 11:29:31 AM
> Subject: Re: [Users] Ovirt 3.3 - How to write a network plugin
>
>
>
>
>
>
> Hello,
> Hi Benoit
>
>
>
>
> I've seen ovirt can support plugin ... so is there any documentation
about
> writing a plugin ?
> What do you mean "can support plugin"?
>
>
>
> Can we write it in python ?
>
>
> Well because, here, we don't want to install openstack/neutron for
network
> management ... It's too complicated and to heavy. I, your opinion wrong
> design choice about openvswitch implementation.
> Not sure what you mean here about openvswitch implementation, can you
please
> clarify?
>
>
>
>
> Thank you in advance.
>
> Regards,
>
>
> --
> --
> Benoit
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
Hi Benoit,
If the question is: "can we write a network plugin so that networks are
defined in open vSwitch instead of in traditional linux bonds, vlans and
bridges"; the answer is yes. The language to do that is Python and the
correct oVirt component to do it in is vdsm. Now we have an ifcfg
configurator
and a partial iproute2 configurator. The task would be to make an open
vSwitch
one.
Best regards,
Toni