1

THE FLUID INTERNET:SERVICE-CENTRIC MANAGEMENT OF AVIRTUALIZED FUTURE INTERNET

Group member: Kai Hu Weili Yin Xingyu Wu Yinhao Nie Xiaoxue Liu Date:2015/10/21

TELE9752 GROUP PRESENTATION

1

2

OUTLINE Introduction Background The internet (r)evolution The fluid internet Service delivery in the fluid internet The challenges of the fluid internet Conclusion

2

3

BACKGROUND 1.The internet purpose has changed. 2. The traditional structure of the

Internet has been unable to meet the new demand

3.How to solve this issue?

3

4

THE INTERNET (R)EVOLUTION

1. The trend of changing

I nf rastructure-rel ated trends

Increased immersion and new levels of interactivi ty

Internet of Things

Network vi rtual i zation

4

5

THE INTERNET (R)EVOLUTION

2. Three main management challenges. 2.1 The current provision and management is inflexible 2.2 The current quality requirements are versatile and fluctuating. 2.3 Internet management should focus on the mobility support problems.

5

6

THE INTERNET (R)EVOLUTION

3. How to solve these challenges? Fluid Internet paradigm 3.1 treats services as the first consideration. 3.2 can benefit the elastic provision of virtualized end-to-end service delivery infrastructures.Current Internet paradigm Fluid Internet paradigm

leasing of a set of virtual machines, without any guarantees concerningtheir connectivity

Able to lease full-fledged virtual data center networks

data center virtualization is limited to a single data center network domain

Facilitates end-to-end virtual service delivery networks, combining multiple physical networks

low-level network and computingrequirements

high-level service and userrequirements

6

7

THE FLUID INTERNETWhat technologies constitutes a fluid network management principles?

Fluid Internet1.Cloud computing

3.Network vi rtual i zation

2.Servi ce-centri cnetworking

I nformati on-centri c networki ng

Pure networki ng capabi l i t i es

El asti c al l ocati on of resources as wel l as hi gh- l evel capabi l i t i es i n both the cl oud and the network

FURTHER

Extension

Current network vi rtual i zati on

Pure networki ng capabi l i t i es

7

8

THE FLUID INTERNETdeliver the servicegiven the requested quality guarantees

From

The

per

spec

tive

of c

urre

nt n

etw

ork

stru

ctur

e to

ach

ieve

leas

ing

addi

tiona

l co

mpu

tatio

nal a

nd s

tora

ge c

apab

ilitie

s

Different applications

How to achieve leasing action

Current network structure

8

9

THE FLUID INTERNET

Three main advantages of the Fluid Internet:1. Delegation of management responsibilities.2. End-to-end manageability3. Dynamic management

9

10

SERVICE DELIVERY IN THEFLUID INTERNET

More details of the interactions

Step 1 Dimensioning Planning Provisioning

Step 2 Elastic management

10

11

STEP 1 DIMENSIONING ,PLANNING & PROVISIONING

the VSIP should calculate the optimal mapping of all SP VSIs to its own VSIs.

But Embedding the newly requested VSI configuration may FAIL due to ① a lack of available resources ② VSIP does not operate a VSI that can satisfy the requested service

guarantees.11

12

Several actions performed to deal with such failure

Based on the changed resource capacities or service requirements, the VSIP will adjust one or more of its own VSIs

VSIP performs a horizontal VNE step. Partitioning the end-to-end VSIs in multiple intra-domain VSI

components. The VSIP maps all intra-domain VSI parts of all its VSIs onto compatible physical infrastructures.

the VSIP sends requests to the relevant IPs Adjusting its leased capabilities in line with the results of the

horizontal VNE step. Each IP solves the vertical VNE problem for all intra-domain VSI

components that are provisioned on its infrastructure. (mapping virtual capabilities onto concrete physical resources.)

the lease contracts back to the VSIP and SP Delivering services to its users under the pre-requested service

guarantees.12

13

STEP 2 ELASTIC MANAGEMENT

The SP is expected to reserve spare capacity in its VSIs to be able to cope with minor fluctuations in user behavior and demand

However, providing too much spare capacity would result in inefficient resource utilization and unnecessarily high costs.

13

14

The SP detects a modified access pattern and decides that more capabilities are needed to continue supporting the service adequately. Then the SP forwards the modified service requirements to the relevant VSIP

VSIP translates them into a modified VSI configuration.14

15

Then VSIP is expected to provide some spare capacity in anticipation of minor service requirement fluctuations.

If the spare capacity is insufficient, or if the modified requirements cannot be supported by the VSIP’s current set of VSIs, several other actions need to be taken.

the VSIP performs the horizontal scaling step. Similar to the horizontal VNE step it performs when provisioning

new services, but these changes in requirements are required to be much faster than provisioning new services.

(requires fast heuristics that iteratively adapt existing solutions)

the VSIP releases, scales, and/or leases capabilities from different IPs Based on the modified VSIs resulting from the horizontal scaling step

IPs perform vertical scaling operations. Similarly, it is a faster online version of the vertical VNE step.

15

16

THE CHALLENGES OF THE FLUID INTERNET

① REQUIREMENT

TRANSLATION

② SERVICE-CENTRIC

NETWORK EMBEDDING

③ ELASTIC

MANAGEMENT

④ SERVICE ADDRESSING ANDPROTOCOL SIGNALLING

⑤ Security

Although it has huge advantages comparing to traditional network, fluid internet is still facing challenges in many areas, especially the scientific problems. The figure above shows five important open issues.16

17

① REQUIREMENT TRANSLATION

VSIP translates the received end-to-end service requirements into a VSI configuration. As the first step of the whole interaction, it is extremely crucial to ensure that this configuration to be constructed.

Therefore, the algorithms of the translation should be able to:

Translate a wide range of QoS requirements into a set of virtual capabilities

Connect those capabilities in an end-to-end VSI, and incorporate the dependencies

Provide suitable solutions that do not interfere the network embedding process

which makes such algorithms hard to design17

18

Current advances The requirement translation is related to

automated software requirements refinement (semi-automated now)

Fluid Internet-based requirement translation has

potential to achieve fully automated algorithms rather than current semi-automated tools for two reasons:

The translation is less complicated than pure policy refinement

Increasing attention on the design of network programming languages could be helpful to prove the feasibility and accuracy of a requirement translation

18

19

② SERVICE-CENTRIC NETWORK EMBEDDING

Current network embedding algorithms focus mainly on solving the problem in a centralized way

Do not scale well to a huge network (Internet) Could hardly work in complicated virtual networks

We need distributed network embedding algorithms to:

scale to immense amounts of VSIs. support for inter-provider VSIs Transcend traditional embedding algorithms

19

20

③ ELASTIC MANAGEMENT

There is a need for an integrated approach that keeps balance between computationally intensive optimal algorithms with fast responding to requirements.

Nowsdays, virtual network embedding algorithms focus mostly on static embedding and do not combine distributed and dynamic embedding.

Therefore, we need a dynamic algorithm that be able to adapting VSI based on changes in requirements.

( Similar to cloud management approaches)

20

21

④ SERVICE ADDRESSING AND PROTOCOL SIGNALLING

The Fluid Internet paradigm reuse ICN concepts, associated with ICN-related challenges.

Communication protocols between the stakeholders are needed

Should be extended to support configuration of service-centric concepts

21

22

⑤ SECURITY

Remote parties are given access to the management of local network, which leads to security issues

Fluid Internet should target a distributed security model, Combining both cloud-originated with network-originated security concerns.

22

23

CONCLUSION

Three technologies

Three advantages

Five challenges

23

24

THANK YOU

24