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.
Difference between revisions of "Ganymede Provisioning Workshop Breakout Results"
(→Spectrum of Governance : Local control with central governance) |
(→Co-existence of multiple provisioners) |
||
| Line 17: | Line 17: | ||
* admin interaction | * admin interaction | ||
* touchpoints for native installation methods (ex. MSI, RPM) | * 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) | ||
== metadata for user == | == metadata for user == | ||
== metadata for system == | == metadata for system == | ||
== metadata for configuration == | == metadata for configuration == | ||
Revision as of 16:04, 10 April 2007
Contents
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)
- validation of profiles
- licensing issues
- shared runtimes
- shared binaries
- repository discovery (RSS? Web servcies?)
- disconnected cases
- media (including metadata and/or artifacts)
- pending connection - future installation
- on-the-fly creation of native packages (in the background)
- add dependencies on native bits (ex. adding a dependency on GTK for SWT so that if GTK is going to be removed, SWT will either also be removed or at least the potential for the removal will be presented)
- 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