Transcript FEDERICA Vmware examples

THE OVERLAY NETWORKS WITH VIRTUAL
RESOURCES NEED NEW FORMS OF
MONITORING
Jiri Navratil,
Tomas Kosnar, Jan Furman, Tomas Mrazek, Vojtech Krmicek
CESNET
Main goal:
Create playground for network
engineers and other scientists who need
experimental network s for testing
new designs, proof new concepts and
idea needed for Future Internet
Main feature:
Each group of users should play in
FEDERICA independently, fully
separated from other players
Motto:
You have to know well the system
which you want to monitor, measure,
manage
Federica.eu
as
ibm.com or hp.com
From https://wiki.fp7-federica.eu/bin/view/SA1/Sa1Deliverable
Virtualization helps us
make a identical copies
Virtualization helps us
make a identical copies
Virtualization helps us
make a identical copies
Virtualization helps us
make a identical copies
How we can achieve this ?
Typical site infrastructure
From https://wiki.fp7-federica.eu/bin/view/SA1/Sa1Deliverable
Via virtual nodes
Core POP
Via virtual networks
Non Core POP
a/ Multiply nodes
b/ Allocate new nodes to slices (users playgrounds)
c/ Create new networks
Slice centric
(users)
Node centric
(node managers)
Physical centric
(FEDERICA NOC)
Physical level - Basic Orientation Map
(based on SNMP)
Tools available from SNMP
Last 24 hours
week
months
FEDERICA Host reachability
RTT
Practical Slicing
Making new networking substrate in selected Vnodes
Example for two slices with different network structure
Star network: A-D, A-C, A-B
Circle network: A-D-B-C-A
(VLAN 101,102,103)
(VLAN 111,112,113,114)
VLAN-113
Uplink
Site C
FEDERICA
core
Site B
VLAN-103
VLAN-114
Uplink
VLAN-112
VLAN-102
VLAN-111
802.1q
Uplink
Site D
VLAN-101
Uplink
Uplink
Site A
Variability in FEDERICA sites
Location of MP - Measuring points / edges
vmnic
physical Eth. adapters
Networking virtual
infrastructure
Ports
100
VLANs
Mgmt..
network
1
VSwitch-1
1
2
2
802.1Q trunk
103
104
VSwitch-2
111
112
Networking virtual
infrastructure
VNIC (max 4 for VM)
VLANs
802.1Q trunk
Slice-3
2
3
3
103
eth1
Uplink
11
VMware virtual
infrastructure
111
112
12
eth0
Slice-8
VSwitch-3
SNMP MP
Ext. Switch
JUNIPER MX/EX
eth1
8
VM
VNIC (max 4 for VM)
eth0
Ext. Switch
JUNIPER MX/EX
VM
eth0
2
104
VMware virtual
infrastructure
12
Slice-1
Mgmt..
network
1
1
VM
eth0
physical Eth. adapters
eth0
eth1
Uplink
11
VM
Slice-3
3
3
Slice-1
100
vmnic
eth0
VM
VSwitch-1
Vnode (ESXi Server)
SNMP MP
Vmware MPs
This solution has limit in # of VMNIC
VNIC
8
VM
Tagging ends in ext. switches
Slice-8
eth1
Vnode (ESXi Server)
Vmware MPs
OR
Tagging ends in Vswitches
This solution has no practical limit
(due to VMWARE variability)
Vmware networking infrastructure
opens high variability
Configuration example when tagging ends on external switches
(Slices appear and disappear - mapping problem)
Site C
Site B
ESXi Server
Slice-2
Slice-8
Ext. Switch
1
Ports
1
FEDERICA
core
103
113
112
114
2
3
VLAN-104
VLAN-114
Slice-8
Slice-3
11
7
12
11
Slice-1
Slice-4
104
104
VLAN-112
Uplink
1
2 113
VLAN-113
Uplink
VLAN-103
VLAN-113
3
10
vmnic
Ports
2
Slice-3
ESXi Server
Ext. Switch
8
12
VLAN-114
Slice-1
Star network: slice 3
Circle network: slice 8
Ports
Slice-3
ESXi Server
1
1
VLAN-101
VLAN-111
2
Slice-8
Ports
VLAN-112
3
Uplink
2
VLAN-111
3
Uplink
1
2
4 101,103,
104
Slice-1
Slice-8
Slice-4
11
11
101
111.114
12
12
Ext. Switch
Ext. Switch
Probably the simplest solution but it allows make only (N-1) slices on
Vnode if we don’t allow port sharing . ( In our case 7 slices on Vnode)
7
8
ESXi Server
Site D
Slice-3
Site A
SNMP
VMware
The simplest slice example
(CESNET SLICE}
AS (Poz)
Internet
VN2
(Erl)
management
network
private IP
addr. space
VN1
(Prg)
VN3
(Mil)
Internet and SLICE
Two independent worlds
lightly coupled via AS !
Tools available from VMware
Tools available from Vmware
(good for managers not users)
Tools available from VMware
Tools available from Vmware - resxtop
Our new tools (node-centric mode)
Our new tools (node-centric mode)
More details (node-centric mode)
More details (node-centric mode)
Monitoring tools
(slice-centric mode)
We still need more work on it
We need:
- configuration data from central database
- more detail coordination with NOC
- automatic links between admin tools
The experiments on the SLICE: SNMP - Vmware match
(CESNET SLICE}
AS (Poz)
Internet
management
network
VN2
(Erl)
VN1
(Prg)
SNMP G3 Monitor
private IP network
VN3
(Mil)
The experiments on the SLICE: Correlation: CPU load versus network
Port – slice mapping ?
(from DB ?)
App1:
scp 4G file
App2:
Data collection
with processing
The experiments on the SLICE: Resource sharing (CPU)
Multi-line versus STACK
CPU distribution on host
- SMP random
- rules for dedication to VM
CPU utilization on host
Capacity:
8x20 K units:
160 000 ms
The experiments on the SLICE: Resource sharing (CPUs)
5 VM
- 1 dominate
4 CPU active
Total CPU activity ~ 0,13%
7 VM
- 1 dominate
4 CPU active
Total CPU activity ~ 0,05%
9 VM
- 1 dominate
4 CPU active
Total CPU activity ~ 0,14%
The experiments on the SLICE: Resource capacity test (CPU)
Integrated value all CPU on host
Individual CPUs on host
+ utilization
- Idle
Source sharing - compare to Planetlab
Total # slices running on this node: 73
Actively using CPU: 9 (only one CPU)
Actively using Network: 18
Conclusion:
Most slices running randomely
It allows stronger overallocation !
External PROBE Monitoring
(more details in 4D section - Jiri Novotny and in the poster)
http://tnc2009.terena.org/schedule/posters/pdf/090529165558federica-monitoring-poster.pdf
FEDERICA - CESNET POP
More details in the POSTER: …..
Thank You
Any questions ?