# Tenant network support/SDN

**URL:** <https://forum.opennebula.io/t/tenant-network-support-sdn/3684>\
**Category:** Integration Support\
**Created:** [January 30, 2017, 6:04pm UTC](https://forum.opennebula.io/t/tenant-network-support-sdn/3684 "2017-01-30T18:04:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nwilging](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/nwilging/32/5021_2.png) [@nwilging](https://forum.opennebula.io/u/nwilging)\
**Post date:** [January 30, 2017, 6:04pm UTC](https://forum.opennebula.io/t/tenant-network-support-sdn/3684/1 "2017-01-30T18:04:47Z")

</div>

For OpenNebula version \<5, see here: [GitHub - OpenNebula/addon-eywa: Virtual Network Driver for HA/LB](https://github.com/OpenNebula/addon-eywa)

I have installed and began working with the above mentioned addon. However, either it is lacking support for v5+ or simply does not work as intended anymore. I think that the OpenNebula project would greatly benefit from a built in solution much like the above example. What I specifically would like to see is a model similar to OpenStack for tenant networking (without the headache that is openstack, of course). Tenants should be able to define their own internal networks, routers, etc.

I would volunteer to test any new addon like this on my systems.