1 / 25

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.

gema
Download Presentation

Analysis of J.F.Denise’s idea

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Analysis of J.F.Denise’s idea Chuan Xiao Fudan-Hitachi InSTech Joint Lab 2008/09/10

  2. 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.

  3. The UI for an operator Add one subscription Subscription Name: subscriptionByJames All subscriptions Computer IP Address: 192.168.30.18 subscription01 subscription02 Usage High Threshold: % 98 subscription03 Usage Low Threshold: % 5 subscription04 Expiration: 2008-10-1 12:20:30 subscription05 subscription06 States: ACTIVE subscription07 ACTIVE PAUSED subscription08 subscribe unsubscribe pause resume grey button grey button grey button

  4. The UI for an operator Add one subscription Subscription Name: subscription03 All subscriptions Computer IP Address: 192.168.29.13 subscription01 subscription02 Usage High Threshold: % 95 subscription03 Usage Low Threshold: % 10 subscription04 Expiration: 2008-10-1 12:20:30 subscription05 subscription06 States: ACTIVE subscription07 ACTIVE PAUSED subscription08 subscribe unsubscribe pause resume grey button grey button

  5. The UI for an operator Add one subscription Subscription Name: subscription06 All subscriptions Computer IP Address: 192.168.50.17 subscription01 subscription02 Usage High Threshold: % 99 subscription03 Usage Low Threshold: % 15 subscription04 Expiration: 2008-10-1 12:20:30 subscription05 States: subscription06 PAUSED subscription07 ACTIVE PAUSED subscription08 subscribe unsubscribe pause resume grey button grey button

  6. Model Management software Client WS-Management Server PC 192.168.30.18

  7. When the operator click “subscribe” button Management software Client subR’s events 1. WS-Transfer:Create 2. WS-Eventing:Subscribe (subP) 3.WS-Eventing: Subscribe (subR) R1 CIM_Processor instance subP’s events Server FIFO PC 192.168.30.18

  8. 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”.

  9. 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)

  10. When the operator click “unsubscribe” button Management software Client subR’s events 2. WS-Eventing: Unsubscribe (subR) 1. WS-Eventing: Unsubscribe (subP) 3.WS-Transfer:Delete subscriptionMgr R1 CIM_Processor instance Server FIFO subP’s events PC 192.168.30.18

  11. 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”.

  12. Implicit information at client sideafter successfully “unsubscribe” • Because the subscription is deleted, there is no implicit information at client side.

  13. When the operator click “pause” button Management software Client subR’s events 1. WS-Eventing: Unsubscribe (subR) subscriptionMgr R1 CIM_Processor instance Server FIFO subP’s events PC 192.168.30.18

  14. 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”.

  15. 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)

  16. When the operator click “resume” button Management software Client subR2’s events 1. WS-Eventing: Subscribe (subR2) subscriptionMgr R1 CIM_Processor instance Server FIFO subP’s events PC 192.168.30.18

  17. 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”.

  18. 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)

  19. 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.

  20. When one event can not be sent to client Management software x Client subR’s events subscriptionMgr R1 CIM_Processor instance Server FIFO subP’s events PC 192.168.30.18

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

  22. When one subscription expires Management software Client subR’s events subscriptionMgr R1 CIM_Processor instance Server FIFO subP’s events PC 192.168.30.18

  23. 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.

  24. 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.

  25. Thank you!Welcome your any comments.

More Related