Download Network Solution In Our Public Cloud

OpenStack
Network Solution In Our Public Cloud
OpenStack
All OpenStack Projects Status
Navigator
it is aimed at helping users make informed decisions about
how to consume the software.
OpenStack
Who Is OpenStack Powered
1. OpenStack Interoperability
Ensure that the various products and services bearing the
OpenStack marks achieve a high level of interoperability.
2. How many products are OpenStack powered
Distro: total 29, 19 were tested
Private Clouds: total 13, 6 were tested
Public Clouds: total 20, 6 were tested
OpenStack
Cascading Solution
OpenStack
Tricircle
OpenStack
Network Solution In Tricircle
Neutron + open source reference:
1. ml2 + openvswitch + vxlan
2. DVR + l2 population
3. Distributed SNAT
4. Distributed DHCP
OpenStack
Why Neutron Need DVR
OpenStack
DVR Implement
OpenStack
DVR Pain Points
1. Complicated implement
-- DVR codes fly all over
-- Just focus on data plane, not consider complex in
control plane
2. Bugs
-- Creating new port trigger DVR schedule
-- Binding FloatingIP trigger DVR schedule
-- Update Router GateWay trigger DVR schedule
…
3. Some Bugs can’t be solved in current
architecture (etc. bulk deleting/migrating
port)
OpenStack
Status Of DVR + L2 pop + HA
Conclusion : they are not ready for production
L2 pop:
-- After VM migration, tunnels not getting removed
with
-- Performance
…
HA:
-- L3 HA did not work with l2pop at all(bug# 1522980)
OpenStack
DHCP Service Workflow
OpenStack
DHCP HA Mode
1. What’s DHCP HA
-- two or more DHCP agents per network.
-- these DHCP agents are in ACTIVE/ACTIVE
mode.
2. Problems for current DHCP Service
-- VM can't get IP at booting time
-- dhcp-agent need much time to reboot if it has served for a
large VMs
-- network node has a large number of namespaces
3. Deploy more dhcp-agents to make DHCP service
available
OpenStack
How Does DHCP Work In Large Scale
Scenarios:
1000 compute nodes, 10000 networks, 100
VMs per nodes, 4 VNIC per VM, 2 dhcp-agents
per network.
running dhcp-agent on every compute node.
Total VMs: 1000 X 50 = 50000
Total Ports: 50000 X 4 = 200000
Ports per network: 200000/10000 = 20
Total namespaces: 10000 X 2 /1000 = 20
OpenStack
DHCP HA shortcomings
1. Shortcomings:
-- Need very smart scheduler
-- Enable DHCP service for a network even if no
port in this network
-- Metadata service through dhcp-agent is
unavailable
…
2. Why we need Distributed DHCP
-- a network in Tricircle is across OpenStack
-- make DHCP service more stable
OpenStack
Distributed DHCP Agent
OpenStack
Distributed DHCP In Neutron
It is not accepted in Neutron now:
-- Do not want a complicated service like DVR
-- In most Scenarios, we can use current DHCP
HA
OpenStack
Neutron Pain Points
Neutron + open source reference Pain Points:
-- neutron-server = API + DB + RPC
-- over-weight neutron-server and lighter agent for
RPC
Neutron is most active in OpenStack
--neutron is a common platform, provide API + DB
--SDN drivers
OpenStack
Thanks!
OpenStack