Updates in the micro space
Upcoming SlideShare
Loading in...5

Like this? Share it with your network

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 54

http://www.eclipsecon.org 39
http://eclipsecon.org 15

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


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