Software Defined Networking as a Charm in OpenStack (or others)

Kapil Thangavelu kapil.thangavelu at canonical.com
Tue Nov 12 01:36:45 UTC 2013


Hi Tim,

That sounds great. I'd suggest breaking up the charms into two components,
the hypervisor agent as a subordinate that is deployed as a subordinate to
the nova-compute service and also a relation to the neutron service.
Subordinate services 'live' in the same machine as their 'parent' services
and are scaled out along with the parent service. The other part sounds
like it would be a neutron charm plugin to configure neutron with the
midokura backend.

cc'ing our openstack charmers.

cheers,

Kapil


On Thu, Nov 7, 2013 at 12:47 AM, Tim Fall <tim at midokura.com> wrote:

> Howdy from OpenStack Hong Kong everyone.
>
> Some of you may be aware that MidoKura is working on JuJu support for our
> SDN virtual network. On that front, I have a question for consideration.
>
> Since networking isn’t really a straightforward “component” of OpenStack
> that fits nicely inside a box, I was wondering what would be best way to go
> about integrating it for general use. The standard install process involves
> installing agents on each hypervisor, and doing upstream calls through the
> neutron API. Would it be wise to try to include this sort of thing as a
> pure charm and then establish service connections to the relevant
> components, or to try and include it as a networking “option” within other
> charms (like Neutron)?
>
> Thanks for the thoughts!
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20131111/58bf7568/attachment.html>


More information about the Juju-dev mailing list