Key Problem Research Of Flow Bottle-neck And Controllability Based On Neutron

With the booming of Cloud Compute, the Infrastructure As A Server has been much more popular, and opensource cloud platform OpenStack is developing very quickly. From the first version Austin to Kilo, it just spends five years. The research is based on the newest version, and in the research we keep focus on the development about OpenStack.This paper is mainly focusing on the network component of OpenStack, in the former version of OpenStack, the Network architecture is based on Nova-Network.But the structure of Nova-Network is very simple, it just can satisfy the lay2 network.As the booming of the size of network, and concept about the network as a server is been brought out, Openstack community proposes the Neutron network component,and user can define their network topology by using the api, such as VPN, Firewall etc.Although Neutron has achieved the network as a server, also satisfy Software Define Network in a general sense. But there are also some disadvantages such as:firstly, in the structure the network node is the most important node, all the flow must be sent to the node to get the routing decision. So there would be some problem such as Single Point of Failure and bottle-neck. Secondly, though the network device is mainly based on the visual Switch. So the control layer and data forwarding layer has not been departured, so the controbility of the flow is bad.So this paper is mainly focusing on the disadvantage of the Neutron network,and the work has three parts:1. Because of the bottle-neck of Neutron network, this paper takes a design based on the distributed virtual router, in this design, there is a virtual router process in every compute node, this router is mainly responsible for the routing decision, if the flow is the East-West traffic, the flow will be sent to the destination ccompute node directly, if the flow is North-South traffic, the flow will be sent to the network node.2. In order to solve the controbility of the Neutron flow, this part bring the OpenFlow network, and OpenFlow will be a Plugin in the Neutron network, so that we can use the OpenFlow controller to control the flow in Neutron network. Finally because the OpenFlow protocol can not support routing in OpenFlow network, this part does a lot of work to improve the OpenFlow protocol so that it can sopport therequest and reply about ARP and ICMP, after that the OpenFlow network can satisfy the routing in lay3.3. In the end, this paper gives a simulation deployment about OpenStack, and takes some experimental tests about the bottle-neck and controbility about Neutron,after that we make a conclusion and take a prospect about the Neutron network.