Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Ganymede Provisioning Workshop Breakout Results"

(Spectrum of Governance : Local control with central governance)
m (Spectrum of Governance : Local control with central governance)
Line 34: Line 34:
 
*** potential for some user interface but may be restricted
 
*** potential for some user interface but may be restricted
 
** no management
 
** no management
*** complete provisioning ui
+
*** complete provisioning ui (comparable to existing update manager UI)

Revision as of 14:22, 10 April 2007

Co-existence of multiple provisioners

  • multiple sources
  • multiple users
  • interaction of multiple sources (priority, precedence, preference)
  • shared runtimes
  • shared binaries
  • repository discover (RSS? Web servcies?)
  • disconnected cases
    • media (including media and/or artifacts)
    • pending connection - future installation
  • on-the-fly creation of native packages (in the background)
  • admin interaction
  • touchpoints for native installation methods (ex. MSI, RPM)

Spectrum of Governance : Local control with central governance

  • initial provisioning
  • ongoing provisioning
    • points of control
      • "I am the governance provider" -- ensure that at the OSGi layer we can control who can activate bundles
    • potential for ongoing communication between provisioning server and client
      • license revocation or mandatory changes for other reasons
  • hooks for governance both server and client side
    • validation at provisioning server
      • based on not only resolver but also other policies including software configuration settings
  • spectrum of governance
    • fully managed
      • no or almost no client-side ui
      • user has no choice over what is installed and can not install additional software
    • partially managed
      • roles of user can differ (can they choose to install software)
      • governance may be required while end user is installing software
      • governance may be restricted to a certain set of "critical" components
      • potential for some user interface but may be restricted
    • no management
      • complete provisioning ui (comparable to existing update manager UI)

Back to the top