Following the component retirement process defined in [1], a vote thread was started in [2]. The community decided to retire the Midonet plugin. This task represents the final step of the retirement, which is the removal of the plugin from CloudStacks code base.

Based on my conversation with the user terbolous in #cloudstack...Changed the sequence of operations in the section "Initial setup of your fork" to move the two commands related to the upstream repository together.

* pr/12:
Based on my conversation with the user terbolous in #cloudstack: Changed the sequence of operations in the section "Initial setup of your fork" to move the two commands related to the upstream repository together.

Based on my conversation with the user terbolous in #cloudstack: Changed the sequence of operations in the section "Initial setup of your fork" to move the two commands related to the upstream repository together.

In both the master and 4.3 branch there is a patch which sets
the VNC address to the private IP of the hypervisor and during
migration this will be changed to the private IP of the destination
hypervisor.

Binding VNC on 0.0.0.0 is a potential security issue with the hypervisors
also have a public IP address and the VNC ports are not firewalled.