An Untold Story of Redundant Clouds: Making Your Service Deployment - - PowerPoint PPT Presentation

An Untold Story of Redundant Clouds: Making Your Service Deployment Truly Reliable

Ennan Zhai1, Ruichuan Chen2, David Isaac Wolinsky1, Bryan Ford1

1Yale University & 2Bell Labs

Road-Map

• Motivations
• Goal & Insight
• iRec System
• Next Steps

• Motivations
• Goal & Insight
• iRec System
• Next Steps

Road-Map

？

• Application providers:
• enjoy the simplicity of using the clouds
• have no idea about what happen in the clouds
• rent multiple clouds for redundancy

Background

？

• Application providers:
• enjoy the simplicity of using the clouds
• have no idea about what happen in the clouds
• rent multiple clouds for redundancy

Background

？

• Application providers:
• enjoy the simplicity of using the clouds
• have no idea about what happen in the clouds
• rent multiple clouds for redundancy

Background

EC2 availability zone EC2 availability zone EC2 availability zone

Netflix Application Service

IaaS App

Example 1: Netflix

iCloud Application Service

IaaS App

Amazon EC2 Service Microsoft Azure Service

Example 2: iCloud

Email App

Cloud Provider A Cloud Provider B

Problem

Email App

Cloud Provider A Cloud Provider B

Problem

Third-party infrastructure components

Email App

Cloud Provider A Cloud Provider B

ISP B ISP A ISP C

Problem

Third-party infrastructure components

Email App

Cloud Provider A Cloud Provider B

ISP B ISP A ISP C Power Source

Problem

Third-party infrastructure components

Email App

Cloud Provider A Cloud Provider B

ISP B ISP A ISP C Power Source

Problem

Third-party infrastructure components

Email App

Cloud Provider A Cloud Provider B

ISP B ISP A ISP C Power Source

Problem

Become unavailable !

Third-party infrastructure components

Problem

• Cloud providers allocate or tolerate failures via:
• diagnosis systems, e.g., Sherlock.
• fault-tolerant systems, e.g., F10, Skute.

Existing Efforts

• Cloud providers allocate or tolerate failures via:
• diagnosis systems, e.g., Sherlock.
• fault-tolerant systems, e.g., F10, Skute.
• Solving the problem after the outage occurs
• There is no any effort before the problem occur

Existing Efforts

• Cloud providers allocate or tolerate failures via:
• diagnosis systems, e.g., Sherlock.
• fault-tolerant systems, e.g., F10, Skute.
• Solving the problem after the outage occurs
• We want to prevent the problem before the
• utage occurs

Existing Efforts

• Cloud providers allocate or tolerate failures via:
• diagnosis systems, e.g., Sherlock.
• fault-tolerant systems, e.g., F10, Skute.
• Solving the problem after the outage occurs
• We want to prevent the problem before the
• utage occurs

Existing Efforts

• Recommending truly independent redundancy

services when deploying applications

• Motivations
• Goal & Insight
• iRec System
• Next Steps

Road-Map

Road-Map

• Motivations
• Goal & Insight
• iRec System
• Next Steps

App Provider

Goal & Insight

Cloud A Cloud B Cloud C

App Provider

Goal & Insight

Select two clouds for redundancy

Cloud A Cloud B Cloud C

App Provider

Goal & Insight

Cloud A Cloud B Cloud C

A and B ?

App Provider

Goal & Insight

Cloud A Cloud B Cloud C

B and C ?

App Provider

Goal & Insight

Cloud A Cloud C

A and C ?

Cloud B

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

Select two clouds for redundancy: A&B? B&C?

• r A&C?

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

Cloud A Cloud B Cloud C App Provider Recommender

Goal & Insight

Assessing independence by the # of

• verlapping components between clouds

Cloud A Cloud B Cloud C App Provider Recommender

Goal & Insight

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power B Power A

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power B Power A ISP A Power A Power B

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power B Power A ISP A Power A Power B

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP A Power B ISP B Power A

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP A Power B ISP B Power A ISP B Power A Power B

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP A Power B ISP B Power A ISP B Power A Power B

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP B Power A Power B ISP A Power B ISP B Power C Power A

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP B Power A Power B ISP A Power B ISP B Power C Power A ISP B Power C

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP B Power A Power B ISP A Power B ISP B Power C Power A ISP B Power C

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP B Power A Power B ISP A Power B ISP B Power C Power A ISP B Power C

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP B Power A Power B ISP A Power B ISP B Power C Power A ISP B Power C

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

=2

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP B Power A Power B ISP A Power B ISP B Power C Power A ISP B Power C

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

=2

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP B Power A Power B ISP A Power B ISP B Power C Power A ISP B Power C

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP B Power A Power B ISP A Power B ISP B Power C Power A ISP B Power C

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

=1

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP B Power A Power B ISP A Power B ISP B Power C Power A ISP B Power C

=1

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP A Power B ISP B Power C Power A ISP B Power C

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP A Power B ISP B Power C Power A ISP B Power C

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

=0

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

ISP A Power A Power B ISP A Power B ISP B Power C Power A ISP B Power C

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

=0

App Provider Recommender

Goal & Insight

Cloud A Cloud B Cloud C

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

Cloud A Cloud B Cloud C App Provider Recommender

• 1. Cloud A, C 0
• 2. Cloud B, C 1
• 3. Cloud A, B 2

| |

Goal & Insight

Deployment

Ranking List

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

Road-Map

• Motivations
• Goal & Insight
• iRec System
• Next Steps

Road-Map

• Motivations
• Goal & Insight
• iRec System
• Next Steps

Cloud Provider1 Cloud Provider2 Cloud Provider3 Recommender App Provider

Strawman Solution 1

Cloud Provider1 Cloud Provider2 Cloud Provider3 Recommender App Provider

Privacy Concern!

Strawman Solution 1

Cloud Provider1 Cloud Provider2 Cloud Provider3 Trusted Third Party App Provider

Strawman Solution 2

Cloud Provider1 Cloud Provider2 Cloud Provider3 Trusted Third Party App Provider

It is hard to find!

Strawman Solution 2

Cloud Provider1 Cloud Provider2 Cloud Provider3

Secure Multiparty Computation

App Provider

Strawman Solution 3

[Xiao et al, CCSW’13]

Cloud Provider1 Cloud Provider2 Cloud Provider3 SMPC App Provider

SMPC is difficult to scale!

Strawman Solution 3

[Xiao et al, CCSW’13]

• The first cloud independence recommender sys:
• achieving our goal
• preserving privacy of each cloud provider
• practical

Our Approach - iRec

Preliminary background: PSI-CA

Our Approach - iRec

• The first cloud independence recommender sys:
• achieving our goal
• preserving privacy of each cloud provider
• practical

• Private set-intersection cardinality proposed by

[Freedman et al, EuroCrypt’04].

• Allows k parties to compute the # of overlapping

elements without learning other information.

Preliminary: PSI-CA

Preliminary: PSI-CA

• Private set-intersection cardinality proposed by

[Freedman et al, EuroCrypt’04].

• Allows k parties to compute the # of overlapping

elements without learning other information.

11 3 10 1 5 20 3 7 3

PSI-CA

Preliminary: PSI-CA

11 3 10 1 5 20 3 7 3

PSI-CA

• Private set-intersection cardinality proposed by

[Freedman et al, EuroCrypt’04].

• Allows k parties to compute the # of overlapping

elements without learning other information.

11 3 10 1 5 20 3 7 3

PSI-CA

One overlapping element

Preliminary: PSI-CA

One overlapping element One overlapping element

• Private set-intersection cardinality proposed by

[Freedman et al, EuroCrypt’04].

• Allows k parties to compute the # of overlapping

elements without learning other information.

11 3 10 1 5 20 3 7 3

PSI-CA

But I do not know which element is overlapping

Preliminary: PSI-CA

But I do not know which element is overlapping But I do not know which element is overlapping

• Private set-intersection cardinality proposed by

[Freedman et al, EuroCrypt’04].

• Allows k parties to compute the # of overlapping

elements without learning other information.

1 4 6 2

• Alice and Bob has set A and B respectively and Alice wants to jointly

compute |A B|.

• Alice makes a polynomial P whose roots are the elements of data set A.
• Alice encrypts the coefficients of P and sends them to Bob. Note that Alice sends

homomorphic encryptions of the coefficients to Bob.

• Bob evaluates P(Bi) for each element in data set B.
• Bob returns the encrypted evaluations to Alice.
• Alice decrypts it and counts the number of zeroes.

Data Set A Data Set B

Alice Bob

Preliminary: PSI-CA

1 4 6 2

• Alice and Bob has set A and B respectively and Alice wants to jointly

compute |A B|.

• Alice makes a polynomial P whose roots are the elements of data set A.
• Alice encrypts the coefficients of P and sends them to Bob. Note that Alice sends

homomorphic encryptions of the coefficients to Bob.

• Bob evaluates P(Bi) for each element in data set B.
• Bob returns the encrypted evaluations to Alice.
• Alice decrypts it and counts the number of zeroes.

Data Set A Data Set B

Alice Bob

Preliminary: PSI-CA

P = (X-12)(X-5)(X-4) = x3-21x2+128X-240

1 4 6 2

• Alice and Bob has set A and B respectively and Alice wants to jointly

compute |A B|.

• Alice makes a polynomial P whose roots are the elements of data set A.
• Alice encrypts the coefficients of P and sends them to Bob. Note that Alice sends

homomorphic encryptions of the coefficients to Bob.

• Bob evaluates P(Bi) for each element in data set B.
• Bob returns the encrypted evaluations to Alice.
• Alice decrypts it and counts the number of zeroes.

Data Set A Data Set B

Alice Bob

Preliminary: PSI-CA

P = (X-12)(X-5)(X-4) = x3-21x2+128X-240 {E(1), E(-21), E(128), E(-240)}

1 4 6 2

• Alice and Bob has set A and B respectively and Alice wants to jointly

compute |A B|.

• Alice makes a polynomial P whose roots are the elements of data set A.
• Alice encrypts the coefficients of P and sends them to Bob. Note that Alice sends

homomorphic encryptions of the coefficients to Bob.

• Bob evaluates P(Bi) for each element in data set B.
• Bob returns the encrypted evaluations to Alice.
• Alice decrypts it and counts the number of zeroes.

Data Set A Data Set B

Alice Bob

Preliminary: PSI-CA

P = (X-12)(X-5)(X-4) = x3-21x2+128X-240 {E(P(1)), E(P(4)), E(P(6)), E(P(2))} {E(1), E(-21), E(128), E(-240)}

1 4 6 2

• Alice and Bob has set A and B respectively and Alice wants to jointly

compute |A B|.

• Alice makes a polynomial P whose roots are the elements of data set A.
• Alice encrypts the coefficients of P and sends them to Bob. Note that Alice sends

homomorphic encryptions of the coefficients to Bob.

• Bob evaluates P(Bi) for each element in data set B.
• Bob returns the encrypted evaluations to Alice.
• Alice decrypts it and counts the number of zeroes.

Data Set A Data Set B

Alice Bob

Preliminary: PSI-CA

P = (X-12)(X-5)(X-4) = x3-21x2+128X-240 {E(P(1)), E(P(4)), E(P(6)), E(P(2))} {E(1), E(-21), E(128), E(-240)}

1 4 6 2

• Alice and Bob has set A and B respectively and Alice wants to jointly

compute |A B|.

• Alice makes a polynomial P whose roots are the elements of data set A.
• Alice encrypts the coefficients of P and sends them to Bob. Note that Alice sends

homomorphic encryptions of the coefficients to Bob.

• Bob evaluates P(Bi) for each element in data set B.
• Bob returns the encrypted evaluations to Alice.
• Alice decrypts it and counts the number of zeroes.

Data Set A Data Set B

Alice Bob

Preliminary: PSI-CA

P = (X-12)(X-5)(X-4) = x3-21x2+128X-240 {E(P(1)), E(P(4)), E(P(6)), E(P(2))} {E(1), E(-21), E(128), E(-240)}

1 4 6 2

• Alice and Bob has set A and B respectively and Alice wants to jointly

compute |A B|.

• Alice makes a polynomial P whose roots are the elements of data set A.
• Alice encrypts the coefficients of P and sends them to Bob. Note that Alice sends

homomorphic encryptions of the coefficients to Bob.

• Bob evaluates P(Bi) for each element in data set B.
• Bob returns the encrypted evaluations to Alice.
• Alice decrypts it and counts the number of zeroes.

Data Set A Data Set B

Alice Bob

Preliminary: PSI-CA

P = (X-12)(X-5)(X-4) = x3-21x2+128X-240 {E(-132), E(0), E(-12), E(-60)} {E(1), E(-21), E(128), E(-240)}

1 4 6 2

• Alice and Bob has set A and B respectively and Alice wants to jointly

compute |A B|.

• Alice makes a polynomial P whose roots are the elements of data set A.
• Alice encrypts the coefficients of P and sends them to Bob. Note that Alice sends

homomorphic encryptions of the coefficients to Bob.

• Bob evaluates P(Bi) for each element in data set B.
• Bob returns the encrypted evaluations to Alice.
• Alice decrypts it and counts the number of zeroes.

Data Set A Data Set B

Alice Bob

Preliminary: PSI-CA

P = (X-12)(X-5)(X-4) = x3-21x2+128X-240 {E(-132), E(0), E(-12), E(-60)} {E(1), E(-21), E(128), E(-240)}

• Alice and Bob has set A and B respectively and Alice wants to jointly

compute |A B|.

• Alice makes a polynomial P whose roots are the elements of data set A.
• Alice encrypts the coefficients of P and sends them to Bob. Note that Alice sends

homomorphic encryptions of the coefficients to Bob.

• Bob evaluates P(Bi) for each element in data set B.
• Bob returns the encrypted evaluations to Alice.
• Alice decrypts it and counts the number of zeroes.

Data Set A

Alice

P = (X-12)(X-5)(X-4) = x3-21x2+128X-240 {-132, 0, -12, -60}

Preliminary: PSI-CA

• Alice and Bob has set A and B respectively and Alice wants to jointly

compute |A B|.

• Alice makes a polynomial P whose roots are the elements of data set A.
• Alice encrypts the coefficients of P and sends them to Bob. Note that Alice sends

homomorphic encryptions of the coefficients to Bob.

• Bob evaluates P(Bi) for each element in data set B.
• Bob returns the encrypted evaluations to Alice.
• Alice decrypts it and counts the number of zeroes.

Data Set A

Alice

P = (X-12)(X-5)(X-4) = x3-21x2+128X-240 {-132, 0, -12, -60}

Preliminary: PSI-CA

Result is: 1

11 3 10 1 5 20 3 7 3

PSI-CA

One overlapping element

Preliminary: PSI-CA

One overlapping element One overlapping element

Cloud A Cloud B Cloud C App Provider iRec

Our Approach - iRec

ISP A Power B ISP B Power C Power A

Cloud A Cloud B Cloud C App Provider iRec

Our Approach - iRec

ISP A Power B ISP B Power C Power A Select two clouds for redundancy: A&B? B&C?

• r A&C?

Cloud A Cloud B Cloud C App Provider iRec

Step 1

ISP A Power B ISP B Power C Power A

Cloud A Cloud B Cloud C App Provider iRec

Step 2

ISP A Power B ISP B Power C Power A

App Provider Cloud A Cloud B Cloud C

ISP A Power B ISP B Power C Power A

Step 3

iRec

ISP A Power A Power B ISP B Power A Power B ISP B Power C

App Provider Cloud A Cloud B Cloud C

ISP A Power B ISP B Power C Power A

Step 3

iRec

PSI-CA PSI-CA

ISP A Power A Power B ISP B Power A Power B ISP B Power C

Cloud A Cloud B Cloud C App Provider iRec

Step 4

ISP A Power B ISP B Power C Power A

App Provider Recommender

Step 5

Cloud A Cloud B Cloud C

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

ISP A Power B ISP B Power C Power A

Cloud A Cloud B Cloud C App Provider Recommender

• 1. Cloud A, C 0
• 2. Cloud B, C 1
• 3. Cloud A, B 2

| |

Step 5

Deployment

Ranking List

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

ISP A Power B ISP B Power C Power A

• Different infrastructure components play different

roles in the clouds

• Power source might be much more likely to fail

than ISPs

An Improvement Version

• Different infrastructure components play different

roles in the clouds

• Power source might be much more likely to fail

than ISPs

An Improvement Version

An Improvement Version

• We propose an improvement version
• Using Weighted PSI-CA (W-PSI-CA) to instead of

PSI-CA in Step2

• No other improvement
• Different infrastructure components play different

roles in the clouds

• Power source might be much more likely to fail

than ISPs

An Improvement Version

• We propose an improvement version
• Using Weighted PSI-CA (W-PSI-CA) to instead of

PSI-CA in Step3

• No other improvement
• Different infrastructure components play different

roles in the clouds

• Power source might be much more likely to fail

than ISPs

App Provider Cloud A Cloud B Cloud C

ISP A Power B ISP B Power C Power A

iRec

Recall: Step 3

PSI-CA PSI-CA

ISP A Power A Power B ISP B Power A Power B ISP B Power C

Cloud A Cloud B

ISP A Power B ISP B Power A

PSI-CA

ISP A Power A Power B ISP B Power A Power B

Recall: Step 3

Result is 2

Cloud A Cloud B

ISP A Power B ISP B Power A

Using W-PSI-CA

Cloud A Cloud B

ISP A Power B ISP B Power A ISP A Power A Power B ISP B Power A Power B

Using W-PSI-CA

Cloud A Cloud B

ISP A Power B ISP B Power A

Using W-PSI-CA

ISP A 1 Power A 2 Power B 2 ISP B 1 Power A 2 Power B 2

Cloud A Cloud B

ISP A Power B ISP B Power A

Using W-PSI-CA

ISP A 1 Power A 2 Power B 2 ISP B 1 Power A 2 Power B 2

Weights

Cloud A Cloud B

ISP A Power B ISP B Power A

Using W-PSI-CA

ISP A Power A Power A Power B Power B ISP B Power A Power A Power B Power B

ISP A 1 Power A 2 Power B 2 ISP B 1 Power A 2 Power B 2 DSI DSI

Cloud A Cloud B

ISP A Power B ISP B Power A

Using W-PSI-CA

ISP A Power A Power A Power B Power B ISP B Power A Power A Power B Power B

ISP A 1 Power A 2 Power B 2 ISP B 1 Power A 2 Power B 2 DSI DSI

Cloud A Cloud B

ISP A Power B ISP B Power A

Using W-PSI-CA

PSI-CA

ISP A Power A Power A Power B Power B ISP B Power A Power A Power B Power B

DSI DSI

Cloud A Cloud B

ISP A Power B ISP B Power A

Using W-PSI-CA

PSI-CA

Result is 4

ISP A Power A Power A Power B Power B ISP B Power A Power A Power B Power B

DSI DSI

Case Study

Cloud A Cloud B Cloud C App Provider iRec

Step 1

ISP A Power B ISP B Power C Power A Select two clouds for redundancy: A&B? B&C?

• r A&C?

Cloud A Cloud B Cloud C App Provider iRec

Step 1

ISP A Power B ISP B Power C Power A

Cloud A Cloud B Cloud C App Provider iRec

Step 2

ISP A Power B ISP B Power C Power A

Weights Weights Weights

App Provider Cloud A Cloud B Cloud C

ISP A Power B ISP B Power C Power A

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

ISP A 3 Power A 1 Power B 1 ISP B 3 Power A 1 Power B 1 ISP B 3 Power C 1

Step 3 & 4 with W-PSI-CA

iRec

App Provider Cloud A Cloud B Cloud C

ISP A Power B ISP B Power C Power A

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

ISP A 3 Power A 1 Power B 1 ISP B 3 Power A 1 Power B 1 ISP B 3 Power C 1

ISP A ISP A ISP A Power A Power B ISP B ISP B ISP B Power A Power B ISP B ISP B ISP B Power C

Step 3 & 4 with W-PSI-CA

iRec

App Provider Cloud A Cloud B Cloud C

ISP A Power B ISP B Power C Power A

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

ISP A ISP A ISP A Power A Power B ISP B ISP B ISP B Power A Power B ISP B ISP B ISP B Power C

Step 3 & 4 with W-PSI-CA

iRec

App Provider Cloud A Cloud B Cloud C

ISP A Power B ISP B Power C Power A

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

ISP A ISP A ISP A Power A Power B ISP B ISP B ISP B Power C

PSI-CA

Step 3 & 4 with W-PSI-CA

iRec

App Provider Cloud A Cloud B Cloud C

ISP A Power B ISP B Power C Power A

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

ISP A ISP A ISP A Power A Power B ISP B ISP B ISP B Power C

PSI-CA

Step 3 & 4 with W-PSI-CA

iRec

App Provider Cloud A Cloud B Cloud C

ISP A Power B ISP B Power C Power A

Cloud A, C 0 Cloud B, C 1 Cloud A, B 2

Deployment | |

ISP A ISP A ISP A Power A Power B ISP B ISP B ISP B Power A Power B ISP B ISP B ISP B Power C

PSI-CA

Step 3 & 4 with W-PSI-CA

iRec

App Provider Cloud A Cloud B Cloud C

ISP A Power B ISP B Power C Power A

Cloud A, C 0 Cloud B, C 3 Cloud A, B 2

Deployment | |

ISP A ISP A ISP A Power A Power B ISP B ISP B ISP B Power A Power B ISP B ISP B ISP B Power C

PSI-CA

Step 3 & 4 with W-PSI-CA

iRec

App Provider Cloud A Cloud B Cloud C

ISP A Power B ISP B Power C Power A

Cloud A, C 0 Cloud B, C 3 Cloud A, B 2

Deployment | |

ISP A ISP A ISP A Power A Power B ISP B ISP B ISP B Power A Power B ISP B ISP B ISP B Power C

PSI-CA

Step 3 & 4 with W-PSI-CA

iRec

App Provider Cloud A Cloud B Cloud C

ISP A Power B ISP B Power C Power A

Cloud A, C 0 Cloud B, C 3 Cloud A, B 2

Deployment | |

ISP A ISP A ISP A Power A Power B ISP B ISP B ISP B Power A Power B ISP B ISP B ISP B Power C

PSI-CA

Step 3 & 4 with W-PSI-CA

iRec

App Provider Cloud A Cloud B Cloud C

Cloud A, C 0 Cloud B, C 3 Cloud A, B 2

Deployment | |

Step 5

iRec

App Provider Cloud A Cloud B Cloud C

Cloud A, C 0 Cloud B, C 3 Cloud A, B 2

Deployment | |

Step 5

iRec

App Provider Cloud A Cloud B Cloud C

Cloud A, C 0 Cloud A, B 2 Cloud B, C 3

Deployment | |

Step 5

iRec

Cloud A Cloud B Cloud C App Provider

• 1. Cloud A, C 0
• 2. Cloud A, B 2
• 3. Cloud B, C 3

| |

Deployment

Ranking List

Cloud A, C 0 Cloud A, B 2 Cloud B, C 3

Deployment | |

Step 5

iRec

App Provider

• 1. Cloud A, C 0
• 2. Cloud A, B 2
• 3. Cloud B, C 3

| |

Deployment

Ranking List

Step 5

• 1. Cloud A, C 0
• 2. Cloud B, C 1
• 3. Cloud A, B 2

| |

Deployment

V.S.

Ranking list with W-PSI-CA Ranking list with PSI-CA iRec

Road-Map

• Motivations
• Goal & Insight
• iRec System
• Next Steps

Road-Map

• Motivations
• Goal & Insight
• iRec System
• Next Steps

Next Steps

• Can we provide stronger privacy preservation?
• Do cloud providers have incentives to join?
• Will the clouds behave honestly?
• Can we make iRec more scalable?
• How do we evaluate iRec with realistic cloud

dependency datasets?

Next Steps

• Can we provide stronger privacy preservation?
• Do cloud providers have incentives to join?
• Will the clouds behave honestly?
• Can we make iRec more scalable?
• How do we evaluate iRec with realistic cloud

dependency datasets?

Next Steps

• Can we provide stronger privacy preservation?
• Do cloud providers have incentives to join?
• Will the clouds behave honestly?
• Can we make iRec more scalable?
• How do we evaluate iRec with realistic cloud

dependency datasets?

Next Steps

• Can we provide stronger privacy preservation?
• Do cloud providers have incentives to join?
• Will the clouds behave honestly?
• Can we make iRec more scalable?
• How do we evaluate iRec with realistic cloud

dependency datasets?

Thanks! Questions?