Multi-HV OpenStack - It's 2015 already, are we there yet?

Multi-HV OpenStack

It’s 2015 already, are we there yet?

Today we’ll talk about:

• Multi-HV OpenStack – what and why?• Where we are today and what’s

available• Beautiful prerecorded demo with

insightful comments

Who we are

• Dmitriy Novakovskiy• Eugenia Shumakher• Maxim Datskovskiy

Poll

Multi-HV OpenStack

– what and why?

What and why

• What is multi-HV OpenStack• Use Cases and motivation– UC-1: Enabling developers– UC-2: Avoiding lock-in– UC-3: Supporting application needs

Possible configs

• KVM + vSphere• KVM + Xen• KVM + OracleVM• KVM + Containers

Where we are today and what’s

available

Basis - VMWare reference architecture

➔ VMware’s HA/FT➔ DRS➔ vMotion➔ NSX

Where’s the catch?

Challenges? Networking as always

• NSX is good but available not to everyone– There are nuances on NSX-V and NSX-

MH editions

• Contrail yet supports ESXi only, not vCenter

• Nova-network - well, works • What about Neutron + DVS?

Challenges? Networking as always

• A number of DVS drivers for ML2 are on the radar:– vsphere-neutron BP tree seems abandoned– Existing drivers [1], [2], [3] have limitations

(pre-existing port groups, single vNIC per VM only, etc)

– VMWare (VIO) DVS driver – on Stackforge!– Mirantis (MOS) DVS driver – on Stackforge!– HP Helion OVSvApp

Demo time!

OVS DVS

ESXiKVM

VM A

VM B

LB (HAproxy)

Tenant network (VLAN 123)

Demo scenario1. Spawn 2 VMs

1. VM A in VMW AZ2. VM B in KVM AZ

2. VMs ping each other by IP in private net

3. VM A and B get added into LB pool4. VM C from external net can get web

response from VMs A and B via VIP

[root@node-1 ml2]# less ml2_conf.ini [ml2]type_drivers = local,flat,vlan,gre,vxlantenant_network_types = flat,vlan,gremechanism_drivers =vmware_dvs,openvswitch

[ml2_type_vlan]network_vlan_ranges =physnet2:1000:1030

[ovs]enable_tunneling=Falseintegration_bridge=br-intbridge_mappings=physnet2:br-prv

[ml2_vmware]vsphere_hostname=172.16.0.254

vsphere_login=administrator@vsphere.localvsphere_password=bla-bla-blanetwork_maps = physnet2:dvSwitch

Conclusions

• Multi-HV OpenStack is useful in a number of scenarios

• Since Paris summit there’s a good progress on enabling OVS+DVS under ML2

• Gaps to be closed by Tokyo time– Contrail option– Security groups in Mirantis driver

How to get?

❏ MOS

❏ VIO

❏ DIY :)

Questions?

Thank you!