Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Ganymede Provisioning Workshop Breakout Results
Revision as of 14:24, 10 April 2007 by Unnamed Poltroon (Talk) (→Co-existence of multiple provisioners)
Co-existence of multiple provisioners
- multiple sources
- consistent UI / operations story
- multiple users
- Linux experience but Vista issues, too
- interaction of multiple sources (priority, precedence, preference)
- shared runtimes
- shared binaries
- repository discovery (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
- points of control
- 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
- validation at provisioning server
- 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)
- fully managed