-
Notifications
You must be signed in to change notification settings - Fork 89
MidoNet 5.0.0 Release Notes
This is the fifth release of the MidoNet project.
The focus of this release is on network services as well as usability; many improvements and features are included, see the details in the Features section of the release notes.
Important Note: MidoNet now depends on Java 8.
URL of the repositories:
- MidoNet : http://builds.midonet.org/midonet-5/
- OpenStack MidoNet plugin
| Package | Version (Ubuntu) | Version (Red Hat) |
|---|---|---|
| python-midonetclient | 5.0.0 | 5.0.0-0.1 |
| quagga | 0.99.23.1-0midokura | 0.99.23-0.el7.midokura |
| zkdump | 1.03 | 1.03-1 |
| zookeeper | 3.4.5+dfsg-1 | 3.4.5-1 |
| midolman | 5.0.0 | 5.0.0-0.1 |
| midonet-api | 5.0.0 | 5.0.0-0.1 |
| python-neutron-plugin-midonet | 2015.1.0 | 2015.1.0-1 |
| openjdk-8-jre-headless | 8u45-b14-1~14.04 | - |
| java-1.8.0-openjdk-headless | - | 1.8.0.65-2.b17.el7_1 |
| Operating System | OpenStack | MidoNet |
|---|---|---|
| Ubuntu 14.04 LTS | Kilo | MidoNet 5.0.0 |
| CentOS 7 | Kilo | MidoNet 5.0.0 |
| Ubuntu 14.04 LTS | Liberty | MidoNet 5.0.0 |
| CentOS 7 | Liberty | MidoNet 5.0.0 |
Those are the platform that were tested; MidoNet might work with other distributions or Openstack versions, we would love to hear your experience.
At time of release, there is no upgrade path from 2015.06 ; a fresh install is recommended.
An upgrade tool is worked on as part of MNA-199 and MNA-48.
Reference: MNA-412
Allowed address pairs is an API to configure which IP/MAC addresses a VM can receive/send traffic for. This is needed by VRRH/HSRP type protocols. By default Neutron only allows a VM to send/receive traffic for 1 MAC, 1 IPv4 and 2 IPv6 (link-local and subnet address).
Reference: MNA-718
Neutron routers by default get routes to the networks on which they have interfaces (and a default route to their "gateway" interface). When VMs act as Routers, the Neutron virtual router may need to forward traffic for specific prefixes to the VM. The Extra Routes API allows managing these additional routes.
Reference: MNA-912
In order to insert and chain services such as packet filters, MidoNet offers an API that enables L2 service insertion.
This is currently in technical preview.
Reference: MNA-205
Users are able to mirror any device : ports, bridge, routers
The mirror can be applied on input or output.
Multiple mirrors can be added to the same device.
Reference: MNA-494
For redundancy, a user wants to configure multiple BGP sessions for one virtual port.
Reference: MNA-61
Previously, DHCP agent was used as the metadata server proxy. This is the last agent that MidoNet depended on, and the presence of the agent complicated deployment, especially setting up HA. This features removes the need for this agent in MidoNet deployment to provide metadata service.
All MN Agents (on any compute) are able to proxy Metadata requests to Nova and back to the requesting VMs.
Reference: MNA-725
It is now possible to use Neutron LBaaS reference implementation (HAproxy in Kilo) instead of MidoNet native Load Balancer.
Reference: MNA-412
This will be available with the next version of the MidoNet plugin for Openstack
Port security is an API that allows turning off all IP anti-spoofing protection and Security Groups for a VM. This is needed when a VM acts as a Router because it will be forwarding traffic for arbitrary IP addresses and L4 ports.
Reference: MNA-55
This will be available with the next version of the MidoNet plugin for Openstack
Neutron FWaaS is a tenant-facing API to configure FW Policy (set of ACCEPT/DROP rules) and attach FW instances to Tenant Routers. The router-level Firewall is another layer of security managed by the Tenant Admin, on top of that provided by Security Groups (often managed by Tenant Users).
See the full list of New Features and Bug fixes in Jira.
See the list of open bugs in Jira.
| Date | Milestone |
|---|---|
| September 18, 2015 | Feature Freeze |
| October 14, 2015 | Code Freeze |
| November 13, 2015 | Release |