[Openstack-operators] New networking solution for Cloud Native apps....
Chris Marino
chris at romana.io
Mon Feb 1 14:08:34 UTC 2016
Hello everyone, just wanted to let you know that today we opened up the
repos for the new open source networking project we’ve been working on.
It’s called Romana and the project site is romana.io.
Thought you would be interested because it enables multi-tenant networking
without a virtual network overlay. It's targeted for use with applications
that only need L3 networks so we’ve been able to eliminate and simplify
many things to make the network faster, and easier to build and operate.
If you run these kind of Cloud Native apps on OpenStack (or even directly
on bare metal with Docker or Kubernetes), we’d love to hear what you think.
We’re still working on the container CNM/CNI integration. Any and all
feedback is welcome.
The code is on Github at github.com/romana and you can see how it all works
with a demo we’ve set up that lets you install and run OpenStack on EC2
<http://romana.io/try_romana/openstack/>.
You can read about how Romana works on the project site, here
<http://romana.io/how/romana_basics/>. In summary, it extends the physical
network hierarchy of a layer 3 routed access design
<http://romana.io/how/background/#routed-access-datacenter> from spine and
leaf switches on to hosts, VMs and containers.
This enables a very simple and intuitive tenancy model: For every tenant
(and each of their network segments) there is an actual physical network
CIDR on each host, with all tenants sharing the host-specific address
prefix. The advantage of this is that route aggregation makes route
distribution unnecessary and collapses the number of iptables rules
required for segment isolation. In addition, traffic policies, such as
security rules, can easily be applied to those tenant or segment specific
CIDRs across all hosts.
Any/all comments welcome.
Thanks
CM
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160201/1e36274c/attachment.html>
More information about the OpenStack-operators
mailing list