Provisioning Project Intersections
There are many projects in the Eclipse community that are involved in aspects of software provisioning. This page is intended to track notable areas of Eclipse provisioning where the various efforts intersect. Tracking these intersection points over time, along with the parties of interest, allows us to see who may be interested when problems (or difficulties) arise in these areas. This page can also be used to set up ad-hoc working groups, or dynamic teams to focus work efforts in these areas.
This page is written by and for the entire Eclipse community. If you are working on something that relates to one of these areas, please put down the name of your project, or just your name in the case of an individual contributor. If new intersection points come up, add it to the list. If older intersection points become irrelevant or prove to be uninteresting, they can be removed from the list.
This page is based on an initial list of project intersections developed at the Ganymede Provisioning Workshop. See the Ganymede Provisioning Workshop Breakout Results page for the original list.
Contents
Definition of Parties
Here are the interested parties, along with pointers for more information:
- Buckminster
- Buckminster is an Eclipse Technology sub-project. In the area of provisioning, they have particular expertise in provisioning of Eclipse workspaces.
- ECF
- ECF stands for the Eclipse Communications Framework. EPP is an Eclipse Technology sub-project that is focused on supporting all manner of communications infrastructure from basic transports to presence, instant messaging, voice, ...
- EPP
- EPP stands for the Eclipse Package Project. EPP is an Eclipse Technology sub-project that is focused on creating entry level Eclipse downloads, and providing technology for creating such packages.
- Equinox
- Equinox is a sub-project of the Eclipse project. In this context, we are referring to the Equinox Provisioning work area in the Eclipse incubator.
- Expeditor
- Lotus Expeditor is an Eclipse-based product that has its own provisioning mechanism based on the existing Update Manager.
- Installation Manager
- Installation Manager is a proprietary technology used for provisioning of Eclipse-based IBM products.
- Linux Distros
- The Linux Distros project is focused on packaging and distributing Eclipse technology in Linux distributions. In the context of provisioning, they want to ensure Eclipse provisioning works well in a Linux environment, and interacts well with native provisioning technology provided by the various distros (such as yum on Fedora).
- Maya
- Maya is a sub-project of the Eclipse Technology project that focuses on provisioning and installation technology
- Smartup
- Smartup is a commercial provisioning technology that is not currently based on Eclipse.
- Spaces
- The Spaces project involves hosting services for Eclipse plugin development. Their interest in provisioning is related to ensuring that Eclipse provisioning infrastructure can interact with the Spaces discovery service.
Component Diagram
The above picture (work in progress) shows the rough components and their relationships as described below. This is a bit simplified from the version derived at the workshop as some of the lines did not accurately represent what may become the real relationships.
Project Intersections
(italics means interested party, but not necessarily an active participant)
Metadata
- Everyone
Admin/Advanced UI
- Maya
- Equinox
Central Manager
- Maya
- Installation manager
- Expeditor
- Smartup
Tools
- Maya
- Equinox
- EPP
- Expeditor
- Installation Manager
Director
- Maya
- Equinox
- Smartup
- Buckminster
Engine
- Equinox
- Maya
- Smartup
- Buckminster
End-user UI
- Equinox
- Maya
- Installation Manager
Touch Points
- Equinox
- Maya
Native Installer/Bootstrap
- EPP
- Maya
Repository
- Buckminster
- Equinox
- Maya
- Smartup
- Spaces
Transport
- Equinox
- Smartup
- Maya
Delta Server/mechanism
- Smartup
Profile Management
- Equinox
- Maya
- Buckminster
- EPP
Integration with other mechanisms
- Equinox
- Linux Distros
Cross cutting concerns
- Integration with other mechanisms
- Multiple directors