carenet fall2011 [pres 03] final presentation flatted

8/3/2019 CareNet Fall2011 [PRES 03] Final Presentation Flatted

1/42


2/42

* CareNet11

Team member overview

2

Elis Kullberg Bowei Dai

Vasily Prokopov

Siddharth Madan

Nur Mohammad RashedHannes Junnila


3/42

* CareNet11

Agenda

3

Introduction to CareNet fall 11

Network operations

Residential Gateways

Virtualization analysis

Field testing

Other contributions

Management issues

Further work


4/42

Infrastructure operation

* CareNet11

Introduction: CareNet-SE

4

Gateway

improvementField testing Collaboration

Media /

Bifrost wiki

Successful take-over, operation and hand-over of the CareNet network and services.

Development and field testing of the CareNet Home Extension, including residential

gateways, HDVC clients, sensor gateways, health portal access and associated use-cases.

Primary objectives:


5/42

Robustness

NOC: development vectors

Bifrost router@ Valhallavgen

KR

130.237.0.0

/29

2001:6b0:1:2::/64

192.36

.250

.0/25

Bifrost router@ Kista

Core Network

Access NetworkKista

Bifrost router@ Huddinge

Access NetworkHuddinge

eth0

eth1

eth7

.1

Edge Network

.65::1

eth0

.5

::1

.2::2

eth2

.1

::1

EdgeRouter 1

.9

192.16.124.8/30

.10

eth5 eth3

.35

OSPF

area 0

192.16

.126

.0/30

2001

:6b0

:32:1::/6

4 192.16.126.4/30

2001:6b0:32:3::/64

AS 2839

AS 8973

IBGP

AS 8973

AS 8973

Servers

eth2 e

th5

eth4

eth3

eth2

192.16.126.176/28

2001:6b0:32:7::/64

192.16.126.160/28

2001:6b0:32:6::/64

192.16.126.144/28

2001:6b0:32:5::/64

192.16.126.128/28

2001:6b0:32:4::/64

HDVIPER devices and IP phones

HR

EdgeRouter 2

EBGP

Mgmt.Domain VPNSIP OMRS

192.16.126.64/26

2001:6b0:32::/64

...

.80

::0000

.126

::0fff

Clients

PortalGwupd. Log

.6::2

.177::1

.161::1

.145::1

.129::1

.4::4

.1::1

KTH-LANSSVL

CSC

eth 4:1, Ventspils192.16.126.57/29

VRAvailability

Security

Efficiency

Scalability


6/42


7/42

Bifrost router@ Valhallavgen

2001:6b0:1:2::/64

eth1

::1

eth2

::1

VR

eth3

OSPFv3area 0.0.0.0

2001

:6b0

:32:1::/6

4 2001:6b0:32:3::/64

AS 2839

AS 8973

EdgeRouter 2

EBGP

::4

::1

KTH-LAN

IPv6

SUNETIPv6

Announcing:

2001:6b0:32::/49

Receiving:

::/0

Internet

IPv6

* CareNet11

NOC: IPv6

8

OSPFv3 as IGP in the core network

DHCPv6 in access networks

IPv6 EBGP peering with neighbors


8/42

NOC: network uptime

A measurable objective was set to 99,9%

Has it been acheivied?Almost, the uptime was 99,6%


9/42* CareNet

Gateway: Background

10


10/42* CareNet

Gateway: Background

11

ISP


11/42


12/42* CareNet

Gateway: Background

13

Primary ISP

Backup ISP


13/42* CareNet

Gateway: Background

14

Primary ISP

Backup ISP


14/42* CareNet

Gateway: Background

15


15/42

* CareNet11

Gateway: Connectivity

16

Iptables

masquerade

Kerneleth0 eth1 eth2 eth3 eth4 eth5 ppp0

eth0 eth1 eth2 eth3 eth4 eth5 ppp0 eth0 eth1 eth2 eth3 eth4 eth5

Mudp

br0 eth3

OpenVPN

tun0

CareNetContainer InternetContainerHostNamespace

HDVC Sensor GW Home Network ISP 1 ISP 2 Wireless ISPHealth Portal


16/42

* CareNet11

Gateway: WebGUI

17

Similar to web interface on homerouters

Visualizes all relevant configurationand debug information

Requires low technical literacy


17/42

* CareNet11

Gateway: Virtualization issue tree

18

LXC isolation

Resourceisolation

CPU

CPUratelimitingCPUsharingfor

multi-coreenvironment

Memory

Memory util izationlimiting

Memory accessisolation

Network

Ratelimiting

Disk

I/O utilization

Data isolation

F i le s ys te m is ol at io n F i le i so la ti on

Namespaceisolation

P ID i sol at io n N et wo rk i so la ti onProc/API(kernel)

isolation

Error i solation

Unintentional error

Bus error

Accessviolation Unaligned access

Resourcesinefficienterror

Ra ce con di tio ns D ri ver er ror

Driver programmingerror

Providean invalidbuffer address

Filesystemerror

Intentional error

Synthetically withunintentional errors

Break namespaces

Do Linux Containers provide the level of isolation needed for the Residential Gateways?

- Overall research question


18/42

* CareNet11


19

LXC Resourceisolation

CPU

CPU ratelimiting

CPU sharingfor multi-coreenvironment

Memory

Memoryutilization

limiting

Memoryaccess

isolation

Network

Rate limiting

Disk

I/O utilization




19/42

* CareNet11


20

LXC Resourceisolation

CPU

CPU ratelimiting

CPU sharingfor multi-coreenvironment

Memory

Memoryutilization

limiting

Memoryaccess

isolation

Network

Rate limiting

Disk

I/O utilization




20/42

* CareNet11

Gateway: Virtualization platform

21

Packet receiverPacket generator

Container 2

Container 1

eh0: 10.0.1.2 eh1: 10.0.3.2

eth0:0 10.0.1.1

routes 10.0.3.0/24

nexthop 10.0.1.2

eth0:1 10.0.2.1

routes 10.0.4.0./24

nexthop 10.0.2.2

eth0:0 10.0.3.1

routes 10.0.1.0/24

nexthop 10.0.3.2

eth0:1 10.0.4.1

routes 10.0.2.0/24

nexthop 10.0.4.2eh0: 10.0.2.2 eh1: 10.0.4.2

Physical interface(2 VLANS)

Bifrost Host

Physical interface(2 VLANS)


21/42

* CareNet11

Gateway: Virtualization example results

22

0

20

40

60

80

100

120

545

53

73

93

CPUCoreload%

Time (s)

CPU load (%) as a function of Time (s)

%CPU Container 1

%CPU Container 2

Scheduling limits are enforced!


22/42

* CareNet11

Gateway: Sensor gateway topology

23


23/42


24/42

* CareNet11

Gateway: Sensor gateway topology

25

server.py

API_png.pyAPI_xml.py

Sensor 1 Sensor 2 Sensor N

Round Robin Databases

JSON over TCP

HTTP API


25/42

* CareNet11

Gaetway: Sensor Gateway Client

26

Functionality specification

Heart Rate monitoring

SPO2 monitoring

Graphical User Interface

Audio Alarms

Fully Open Source

Meets Karolinska requirements

Application overview

Platform overview


26/42

* CareNet11

Gaetway: Sensor Gateway Client

27

Functionality specification

Heart Rate monitoring

SPO2 monitoring

Graphical User Interface

Audio Alarms

Fully Open Source

Meets Karolinska requirements

Application overview

Platform overview


27/42

* CareNet11

Gaetway: Sensor Gateway HTTP API

28

Parameters

- Time Span

- Data type

- Patient ID

Return Data

- PNG output

- XML output


28/42

* CareNet11

Infrastructure Testing

29

Testing

In-House

Testing

Custodian

Testing

Hospital

Testing


29/42

* CareNet11

In House Testing: Overview

30

In the fully controlled TSLab environmentWhere

Via well established scientific methodologyHow

See next slideOutcome


30/42


31/42

* CareNet11

Custodian Testing: Overview

32

At homes of six custodians

Located in different parts of Stockholm area

Different internet setups and internal networks

Where

Initially manual data-collection via SSH Later automated data-collection via MRTG & Cacti

See next slide for example

How

Automated data-collection deployed

On average two active custodians Numerous bug-fixes and redesigns

Outcome

M l


32/42

* CareNet11

Custodian Testing:MRTG Data & Analysis

33

Figure 1 Temperature in the CareNet room

Figure 2 CPU usage for a Residential Gateway

l


33/42

* CareNet11

Hospital Testing: Overview

34

At the MT Analys lab at Karolinska in Huddinge

Fully integrated into the Karolinska hospital ITinfrastructure

Semi-controlled environment

Where

Phase 1: RG installation and field testing Phase 2: HDVC installation and field testing

Phase 3: Update and handover to Carenet Spring2012 team

How

Reassurance that CareNet infrastructure

compatible with Karolinska infrastructure Numerous bug-fixes in HDVC systems and RGs

Outcome

l T


34/42

* CareNet11

Hospital Testing: Outcomes

35

t W d d t


35/42

* CareNet11

Future Work and Recommendation

36

The primary aspects of the Carenet system that need to be tested are Sensor Gateway

HDVC

The primary aspects of each system that should be focused are:

Robustness Scalability

Reliability

t t t f t


36/42

* CareNet11

Other contributions: Bifrost wiki screencap

37

bifrost.slu.seCSD course

documentationMailing list

t t C UM t


37/42

* CareNet11

Project management: SCRUM routine

38

Overall adoptions for CareNet-team

1 week sprints

2x meetings per week

Combined sprint review/plan meeting

Outcome

Good experiences

Used week 8 and forward

More appropriate than Kanban?

P t t SC UM d


38/42

* CareNet11

Project management: SCRUM burndown

39

0

200

400

600

800

1000

1200

1400

0 5 10 15 20 25 30 35 40

Hoursrem

aining

Time (days)

SCRUM Burndown Chart, project week 8-19

Measured Burn Down

Planned Burn Down

P t t T t


39/42

* CareNet11

Project management: Time spent per member

40

0

50

100

150

200

250

300

350

400

450

Boewi Dai Elis Kullberg Hannes Junnila Siddharth Madan Nur Mohammad Rashed Vasily Prokopov

Time per member and work package outcome until week #18

MonAMI

Media

Field Testing

NOC

Gateway

Management

P t t B t t !


40/42

* CareNet11

Project management: Best team ever!

41

P t t t ti S i t


41/42

* CareNet11

Project management: Expectations on Spring team

42

Item Priority Tech. Complexity

Operate infrastructure High Medium

Continue field testing RGs High Medium

Solve any found RG bugs High High

Q ti d A w r


42/42

Question and Answer

43

*

carenet fall2011 [pres 03] final presentation flatted

Documents