Analysis of J.F.Denise’s idea

Analysis of J.F.Denise’s idea

Chuan Xiao

Fudan-Hitachi InSTech Joint Lab

2008/09/10

Two Assumptions

• We focus on the CPU usage. The CPU is the managed resource.

• From the viewpoint of an operator, the less operation, even if it may be just one click, the better.

The UI for an operator

Computer IP Address:All subscriptions

subscription01

subscription02

subscription03

subscription04

subscription05

subscription06

subscription07

subscription08

Usage High Threshold:

Usage Low Threshold:

States:

subscribe unsubscribe pause resume

192.168.30.18

98 %

5 %

ACTIVE

ACTIVEPAUSED

Subscription Name: subscriptionByJamesAdd one subscription

grey buttongrey buttongrey button

Expiration: 2008-10-1 12:20:30

The UI for an operator

Computer IP Address:All subscriptions

subscription01

subscription02

subscription03

subscription04

subscription05

subscription06

subscription07

subscription08

Usage High Threshold:

Usage Low Threshold:

States:

subscribe unsubscribe pause resume

192.168.29.13

95 %

10 %

ACTIVE

ACTIVEPAUSED

Subscription Name: subscription03Add one subscription

grey button grey button

Expiration: 2008-10-1 12:20:30

The UI for an operator

Computer IP Address:All subscriptions

subscription01

subscription02

subscription03

subscription04

subscription05

subscription06

subscription07

subscription08

Usage High Threshold:

Usage Low Threshold:

States:

subscribe unsubscribe pause resume

192.168.50.17

99 %

15 %

PAUSED

ACTIVEPAUSED

Subscription Name: subscription06Add one subscription

grey button grey button

Expiration: 2008-10-1 12:20:30

Model

Management software

PC 192.168.30.18

Client

Server

WS-Management

When the operator click “subscribe” button

Management software

PC 192.168.30.18

R1 CIM_Processor instance

FIFO

1. WS-Transfer:Create

2. WS-Eventing:Subscribe (subP)

subP’s events

3.WS-Eventing:Subscribe (subR)

subR’s events

Client

Server

Sequence of automatic operations

1.Client constructs a new resource (named R1) at the server side using WS-Transfer:Create operation. In the R1 there is a FIFO list.

2.Client subscribes to the CIM_Processor instance that emits notifications using WS-Eventing:Subscribe operation. The subscription is called subP and its NotifyTo is R1.

3.Client subscribes to the R1 that receives notifications from the CIM_Processor instance, using WS-Eventing:Subscribe operation. The subscription is called subR and its NotifyTo is the Client.

4. The automatic operations are over and the operator can get the promotion of “successfully subscribe”.

Implicit information at client sideafter successfully “subscribe”

• subscriptionID which identifies the conditions specified by the operator in UI

• EPR of R1

• One relationship: – (subscriptionID, subP, subR, EPR of R1)

When the operator click “unsubscribe” button

Management software

PC 192.168.30.18

R1 CIM_Processor instance

FIFO

2. WS-Eventing:Unsubscribe (subR)

1. WS-Eventing:Unsubscribe (subP)

3.WS-Transfer:Delete

Client

Server

subscriptionMgr

subP’s events

subR’s events

Sequence of automatic operations

1.Client unsubscribes to the CIM_Processor instance to terminate the subscription called subP using WS-Eventing:Unsubscribe operation.

2.Client unsubscribes to the R1 instance to terminate the subscription called subR using WS-Eventing:Unsubscribe operation.

3.Client deletes the R1 instance at server side using WS-Transfer:Delete operation.

4. The automatic operations are over and the operator can get the promotion of “successfully unsubscribe”.

Implicit information at client sideafter successfully “unsubscribe”

• Because the subscription is deleted, there is no implicit information at client side.

When the operator click “pause” button

Management software

PC 192.168.30.18

R1 CIM_Processor instance

FIFO

1. WS-Eventing:Unsubscribe (subR)

Client

Server

subscriptionMgr

subP’s events

subR’s events

Sequence of automatic operations

1.Client unsubscribes to the R1 instance to terminate the subscription called subR using WS-Eventing:Unsubscribe operation. The events are not sent from R1 to Client any more.

2. The automatic operations are over and the operator can get the promotion of “successfully pause”.

Implicit information at client sideafter successfully “pause”

• subscriptionID which identifies the conditions specified by the operator in UI

• EPR of R1

• One relationship: – (subscriptionID, subP, null , EPR of R1)

When the operator click “resume” button

Management software

PC 192.168.30.18

R1 CIM_Processor instance

FIFO

1. WS-Eventing:Subscribe (subR2)

Client

Server

subscriptionMgr

subP’s events

subR2’s events

Sequence of automatic operations

1. Client subscribes to the R1 that receives notifications from the CIM_Processor instance, using WS-Eventing:Subscribe operation. The subscription is called subR2 and its NotifyTo is the Client.

2. The automatic operations are over and the operator can get the promotion of “successfully resume”.

Implicit information at client sideafter successfully “resume”

• subscriptionID which identifies the conditions specified by the operator in UI

• EPR of R1

• One relationship: – (subscriptionID, subP, subR2, EPR of R1)

Other requirements

• The server(such as PC 192.168.30.18) has to provide the event sink interface so that the subP’s events can be sent to the R1 instance.

• The FIFO list has to support the producer/consumer synchronization mechanism.

• Client has to make two subscriptions for operator’s one “subscribe” click, which leads to the additional consumption at traffic and sever side.

When one event can not be sent to client

Management software

PC 192.168.30.18

R1 CIM_Processor instance

FIFO

Client

Server

subscriptionMgr

subP’s events

subR’s events

x

Sequence of operations

1. The operator get the SubscriptionEnd notification, then he click “resume” button of this subscription.

When one subscription expires

Management software

PC 192.168.30.18

R1 CIM_Processor instance

FIFO

Client

Server

subscriptionMgr

subP’s events

subR’s events

Sequence of automatic operations

1.The subP is automatically terminated at server side.

2.The subR is automatically terminated at server side.

3.The R1 instance can NOT be deleted automatically.

4. The implicit information at client side is deleted automatically.

Conclusion

• This way can implement the pause and resume operation to one subscription.

• When one subscription is terminated because of expiration, the additional resource instance (such as R1) can not be deleted automatically.

Thank you!Welcome your any comments.