Updates in the micro space

565 views
528 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
565
On SlideShare
0
From Embeds
0
Number of Embeds
54
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Updates in the micro space

  1. 1. Updates in the micro space<br />Katya Todorova<br />March, 2011<br />
  2. 2. p2<br />“Simple things should be simple. Complex things should be possible ”<br />
  3. 3. The problem – Store management<br />Corporate headquarters<br />Store n<br />Store 1<br />
  4. 4. Store management - requirements<br /><ul><li>No synchronized update of the stores
  5. 5. Need to be able to install the server/device apps
  6. 6. Create a store with minimal configuration
  7. 7. No / minimal maintenance
  8. 8. The device can be of various sizes (from GB to MB)
  9. 9. The device has no state </li></li></ul><li>Store management scenarios<br />Technical scenarios: <br /><ul><li>Initial install
  10. 10. Takes the server out of the box in the store and needs to get setup
  11. 11. Update
  12. 12. Checks for newer version of server software</li></ul>Business scenario:<br /><ul><li>“configuration propagation”
  13. 13. Changing the configuration of the device (we are using ConfigAdmin)</li></li></ul><li>Store management and p2<br />p2 repository<br />RT basic package<br />(p2 on top of equinox)<br /> Running in the process of the app<br />RT basic package<br /> Running in the process of the app<br />
  14. 14. Initial install with p2<br />Corporate server initial provisioning<br /><ul><li>Make p2 repository available</li></ul>Store server<br /><ul><li>Unpack the server
  15. 15. Start it up
  16. 16. Configure the address of the corporate server (aka repo)
  17. 17. Configure the name of the app (store type  the product IU)
  18. 18. Invoke p2 director to install the server product</li></ul>Device<br /><ul><li>Start it up
  19. 19. Configure the address of the store server
  20. 20. When it boots p2 installs device product from store server local repository</li></li></ul><li>Update / propagate configuration with p2<br />Corporate server initial provisioning<br /><ul><li>Out of scope</li></ul>Store server<br /><ul><li>An update is done to the store server app
  21. 21. The corporate server repository is updated with the new content
  22. 22. Corporate server app notifies relevant store servers
  23. 23. Each store server decides when to apply the changes </li></ul>publishes new POS configuration if any<br />update server app <br />Device<br /><ul><li>Installs updates from server p2 repository (device app binaries)
  24. 24. Generates new IU component corresponding configuration changes </li></li></ul><li>Summary<br />p2 has a lot of basic building blocks to take care of the complete problem<br /><ul><li>director / engine for the RT side of things
  25. 25. publisher for the “development”
  26. 26. application (e.g. director app)</li></ul>Don’t hesitate to engage with them on the ML, they don’t bite<br />
  27. 27. Thank You!<br />Contact information:<br />Katya Todorova<br />katya.todorova@sap.com<br />

×