This document outlines MidoNet's roadmap to solve common problems in network and container management. It discusses improving installation processes, adding troubleshooting tools like integrated tracing and mirroring, enhancing security through distributed agents and programmable firewalls, enabling multi-site connectivity, and integrating container orchestration with projects like Kubernetes. Future releases over 2016-2017 aim to address these issues through less complex components, non-disruptive upgrades, auto discovery, and single-pane-of-glass management across sites.

1. MidoNet
Roadmap & Vision
Jean-François Joly
Product Manager @ Midokura
October 2015

2. Disclaimer
• This presentation contains product features that are currently
under development.
• Features are subject to change.
• Technical feasibility and user demand will affect final delivery.

3. Agenda
Solving problems
⚫ Install
⚫ Troubleshoot
⚫ Security
⚫ Multi-sites
⚫ Faster delivery
Problem
Today’s solution
Tomorrow’s
solution

4. MidoNet Releases
2016.H1 2016.H22015.H2 2017.H1
MidoNet 5.1 MidoNet 5.3
MidoNet 5.0
MidoNet 5.5
MidoNet 5.2 MidoNet 5.4

5. Installing
First problem

6. Example install flow
# apt-get install figlet
[…]
The following NEW packages will be installed:
figlet
[…]
Setting up figlet (2.2.5-2) ...
# figlet easy
___ __ _ ___ _ _
/ _ / _` / __| | | |
| __/ (_| __ |_| |
___|__,_|___/__, |
|___/

7. Who needs to deploy
Production DevOps
Systems and networks admins
Support
DevOps
Systems and networks admins
Quality assurance
Test
DevOps
Software engineers
Development

8. MidoNet today
Production Quick start guide
Installers: Puppet, Mirantis Fuel,
Juju, TripleO (RDO Manager) ...
quickstart.sh
# curl https://www.midonet.org/quickstart-v5.0.sh | sudo bash
Test
devstackDevelopment

9. MidoNet today - continued
Agents non disruptive upgrades
Flows are not interrupted during an upgrade

10. MidoNet tomorrow
More installers (Liberty , Suse Openstack
installer)
Less components : distributed flow and topology
database
Seamless upgrades : API is available, topology
can change during an upgrade
Auto discovery of services

11. Troubleshooting
Second problem

12. Lack of visibility

13. Today : trace

14. Trace
Use mm-trace to trace the traffic
See every hosts where a packet transits
See the logical topology
See the security rules that are applied

15. Today : inspect

16. Mirroring
Mirror any destination or subnet
Mirror to multiple ports
Mirror to a VM or physical appliance
Use tcpdump to view the traffic
Use an appliance to perform deep packet
inspection and prevent advanced persistent
threats

17. Physical switches

20. Tomorrow
Integration with the fabric
⚫ Underlay and overlay trace
⚫ Underlay and overlay topology history
Curate the information to show what's most
relevant to the operators
Pro-active fault detection

21. Security
Third problem

22. Endless pressure
External: Advanced persistent threats requires
protection of every machine and detection
mechanism
Internal : Compliance and auditors can dictate
software choices

23. Today : security groups
Manage the security per
port

24. Today : mirroring
Use port mirroring with VM
appliances to insert
additional security systems
Security appliance

25. Today : perimeter firewall
Perimeter Firewall for
traditional rules
management and easier
audits

26. Today : distributed agents
Attacks are dropped at the edge with MidoNet
being distributed

27. Tomorrow
Insert network services directly in the network
path at L2 or L3
This can be done programmatically using API
Retrieve the Firewall logs via the API for
monitoring, audits or compliance
Support Neutron Tap as a Service

28. Multi sites
Fourth problem

29. Expansion and availability
Enterprises outgrow their
initial datacenter
Disasters, compliances drive
the organization’s multi-sites
agenda

31. Today
Run MidoNet
distributed over
multiple sites
Orchestrate the
multiple sites via
the API

32. Tomorrow
Peer several router to establish a private
network between data centers and tenants
On demand VPN using VPNaaS
Single pane of glass to manage multiple sites :
same authentication, security rules...

33. Containers
Fifth problem

34. Faster delivery
Interest for containers is similar to what
happened with VMs 10 years ago
Improve application delivery time and frequency
Containers enable reproducible delivery at scale
with continuous integration and deployment.
Faster to deploy and easier to manipulate than VM

35. Higher density
Containers footprint is
smaller than virtual
machines
More applications running
on the same hardware
brings more density and
even higher network port
concentration

36. Micro services
Application architecture is split in
small, specialized, services requiring
granular security Virtual Machine
Image treatment
Communication
Authentication
Business workflow
Container
Image treatment
Container
Container
Container
Communication
Authentication
Business workflow

37. Today
Run docker containers inside physical machine
(nova docker)
Run kubernetes and mesos on top of Openstack
and MidoNet

38. Tomorrow
Natively connect docker containers to MidoNet
(project Kuryr)
Integration of containers within Openstack
through Openstack Magnum
Orchestrate MidoNet with Mesos, Kubernetes,
Swarm...

39. Join us on Slack to discuss these problems and
implement great solution inside MidoNet
Check MidoNet Releases page in wiki:
https://github.com/midonet/midonet/wiki/Release-Schedule
Read MidoNet documentation for more details:
https://docs.midonet.org/
Follow MidoNet roadmap

40. Questions
Reach over to me on
⚫ Slack @jfjoly
⚫ Mail jf@midokura.com
⚫ IRC jfjoly