Bugzilla – Full Text Bug Listing
| Summary: | OSEE Collaboration Opportunities | ||
|---|---|---|---|
| Product: | [Technology] OSEE | Reporter: | Ryan Brooks <ryan.d.brooks> |
| Component: | OSEE Application Framework | Assignee: | Project Inbox <osee.framework-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | donald.g.dunne |
| Version: | unspecified | ||
| Target Milestone: | 0.9.9 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Ryan Brooks
Here are some additional opportunities for collaboration: --------------- Advanced Launcher / Installer Problem: The current method of launching OSEE is via the shared network drives to ensure that all users are running the latest release. This is problematic due to network speed issues and permissions issues. The preferred method to use OSEE is an installation on the Windows machine the user is running. The problem with a local installation is the need to keep the release up-to-date and not require the users to have to continually re-install. Solution: We need an advanced launcher / installer that will: 1) Check for latest releases 2) Update release if necessary 3) Cleanup old releases 4) Launch OSEE 5) Be smart enough to only download / install what is necessary for update so user is not waiting long when updates are necessary 6) Since OSEE is based on Eclipse which is built on OSGI, the solution may involve the use of that technology to install and update 7) Would need configuration option that would force an update whether necessary or not --------------- Action Tracking System (ATS) Advanced Configuration Editor Background: ATS is a fully customizable problem/change request system. It allows product changes to be tracked at any level; tracking to be broken apart by teams that do the work; split into versions/builds; and contains a powerful state machine that allows each team to move throw their own “workflow” independent of other teams. Problem: Configuration of ATS is complex and different options require different types of user interfaces to configure. In addition, it requires a heavy client to perform the configuration. Solution: A single web-based user interface would be desired that allows the users to easily understand all the options available, set these options and persist these changes into the production environment. This web-based interface should be available via an external browser or an integrated browser in the OSEE client. All information retrieval and configuration changes would be implemented in a restful manner through an ATS server. --------------- OSEE Enterprise Manager Problem: OSEE http://www.eclipse.org/osee is a full Engineering Environment that handles Requirements Management, Configuration Management, Peer Reviews and many other features. We are migrating much of the functionality to the server to make the installed clients smaller and provide more user-friendly web-interfaces. In order to provide quick and efficient user support and admin support, tasks have to be run from a text based server console, a locally installed client, SQL Developer and Oracle Enterprise Manager. It is difficult for the team supporting OSEE to learn and keep up with all the different ways of configuring and retrieving information necessary to perform their tasks. Solution: Develop a single OSEE Enterprise Manager, much like Oracle Enterprise Manager, that would provide a dashboard to configure and query the OSEE Server. Included would be the ability to 1) start/stop servers 2) clear/reload caches 3) re-index the database for searching 4) purge branches 5) communicate via popup to running clients 6) request session information from all running clients 7) shutdown all running clients 8) request error log information from running clients 9) create/configure user accounts 10) set/update access control permissions 11) perform periodic health checks against database 12) perform periodic cleanup operations against database 13) provide for extensibility for future needs |