Wiki code for Problem Statement

Hide Line numbers
1: == OpenSolaris 2009.06 Requirements Document
2: 
3: Document Author: Glynn Foster, v0.1
4: 
5: === 1. Executive Summary
6: 
7:  With OpenSolaris 2009.06, the focus starts to shift to the enterprise building on the latest successful release. Technology advancements such as Image Packaging System, ZFS Boot, Automated Install and the Distribution Constructor pave the way for new deployments in the enterprise with maximimal ease of use and reliability, whatever the task.
8: 
9:  Two new package repositories, pending and contrib, provide the opportunity of hosting the very latest in best of breed free and open source software in a readily accessible format. A series of contribution, rating and feedback tools for the software contained in those repositories encourages the participatory effect of community support, and ensures that OpenSolaris is the best platform for development and deployment of open source software.
10: 
11:  OpenSolaris will continue to have a re-distributable install image that can be mirrored on download sites around the world. Additionally, package repositories will be mirrored externally for the first time to allow users to connect to the closest repository and install software they need faster than ever.
12: 
13:  With software appliances becoming popular in today’s market, the need for OpenSolaris to be flexible enough in a ’shrink to fit’ (e.g. JeOS) environment is increasingly important. Significant package refactoring efforts, through package naming, meta-data and contents, will ensure OpenSolaris proves to be an excellent open source platform to develop new appliances, from storage to network.
14: 
15:  OpenSolaris 2009.06 will continue to strive toward key themes for each release - usability and user experience in out of the box configuration, security and auditability in a trusted environment, virtualization, performance and scalability, globalization in a changing world, accessibility for those with assistive needs, while highlighting OpenSolaris’ unique technology and strengths.
16: 
17: === 2. Technology Priorities
18: 
19:  The following section lists out a set of technology priorities for OpenSolaris 2009.06. It by no means attempts to be an exhaustive list of projects for inclusion in this release.
20: 
21: > ==== 2.1 Installation
22: 
23: {{{
24:         INS-1: Continue to advance the area of automated installation in
25:                OpenSolaris 2009.06 with the addition of a graphical
26: 	       user interface alongside the existing command-line utility
27: 	       for starting the AI web service on a given server.
28:         INS-2: Provide a command-line utility to convert existing
29: 	       Jumpstart installation profiles to Automated Install ones.
30:         INS-3: Provide an installation web service hosted on opensolaris.com
31: 	       allowing registered users to connect their machines and
32: 	       install against a selection of profiles.
33: 	INS-4: Allow users to upload their favourite automated installation
34: 	       profiles to share among other users, or register them with
35: 	       the installation web service hosted on opensolaris.com.
36:         INS-5: The distribution constructor should be capable of creating
37: 	       install images that Automated Install can consume.
38:         INS-6: Automated Install should support both x86 and SPARC
39: 	       platforms.
40:         INS-7: Live CD install should support a ’lightweight install’ option
41: 	       booting into a simple X session and starting the graphical
42: 	       installer immediately.
43:         INS-8: The minimum required memory for Live CD install should
44:                continue to be 512 MB. Both Live CD ’lightweight install’ and
45: 	       automated install should work on considerably less, though no
46: 	       required minimum is provided at this time.
47:         INS-9: GRUB, the graphical boot manager, should support nested
48:                menu options such that additional options can be displayed
49:                without reducing simplicity/usability of fewer options.
50:        INS-10: All installation options, both Live CD and automated
51: 	       install, should provide accessible interfaces for those
52: 	       with disabilities to successfully install OpenSolaris.
53:        INS-11: The installer should be able to detect if existing platforms
54: 	       are installed on a system (and, preferably be able to read
55:                common file-systems in use today), along with providing some basic
56: 	       partitioning tools to make the transition to installing
57: 	       OpenSolaris easier.
58:        INS-12: The installer (both graphical and network based) should be
59:                able to install additional software from a network repository
60:                at install time.
61: }}}
62: 
63: ==== 2.2 Package Management
64: 
65: {{{
66:         PKG-1: Provide the infrastructure to allow site admins to easily mirror
67: 	       the contents of the package repositories on opensolaris.org
68: 	       without needing to have OpenSolaris (or a package depot)
69:                installed on their system. Preferably the solution should use
70: 	       the rsync utility for convenience and familiarity.
71:         PKG-2: Users should be notified when an existing package update
72: 	       requires a reboot of their system, so they may choose to
73: 	       postpone those updates until a more convenient time. Additionally
74: 	       users may decide to lock down a specific version or versions
75: 	       of software from a package update, and should only be notified
76: 	       of package updates that conform to these rules.
77:         PKG-3: The graphical package manager should notify the user when
78: 	       new packages become available, preferably in a non-intrusive
79: 	       fashion.
80:         PKG-4: Provide a graphical way to find out which are the most popular
81: 	       packages that users are installing, allowing the user to 
82: 	       rate a package, or submit feedback on that package to a global
83: 	       database.
84:         PKG-5: Provide a way through a series of package operations for users
85: 	       to see what files within that package have changed between two
86: 	       given versions (or set of versions).
87:         PKG-6: Provide a way through MIME type association or otherwise, for
88: 	       the user to be able to perform a single-click download and
89:         PKG-7: The package repository depot server should provide a full
90: 	       search capability through a web browser, and allow users
91: 	       to determine information (name, description, version,
92: 	       contents, license etc) about a given package. Additionally,
93: 	       they should be able to determine which packages are available
94: 	       for a given milestone release and associated updates.
95:         PKG-8: IPS should support the creation and management of lightweight
96: 	       zones inheriting a core package set up from the global zone,
97: 	       allow the user to additionally install what they need. IPS
98: 	       should search for what it needs locally on the global zone before
99: 	       going to the network ie. if mysql was available in the global
100: 	       zone, it should inherit from that rather than download it again
101: 	       from the package repository.
102: 	PKG-9: IPS should support an image-update across multiple zones as a
103: 	       default option.
104:        PKG-10: IPS should support the removal of EOL’ed packages from a package
105: 	       repository, either by actual removal or hidden browsing.
106: }}}
107: 
108: ==== 2.3 Familiarization
109: 
110: {{{
111:         FAM-1: Package refactoring (name, meta-data and dependencies) should be
112: 	       performed on packages in the /release repository to aid with
113: 	       familiarization for those coming from a different platform, and
114: 	       be consistent to the upstream component name. Where there is a
115: 	       strong relationship between a group of packages, a meta-package
116:                can be created.
117:         FAM-2: Provide at least 80% of the top 20 searches to pkg.opensolaris.org
118:                as new software packages in the network package repository. The
119: 	       top 20% of packages in the /contrib and /pending repositories
120: 	       should be candidates for eventual integration into the /release
121: 	       repository.
122:         FAM-3: The default boot splash should be a graphical progress
123: 	       indicator, hiding some of the boot messages from the user.
124: 	       The user should have the option, during boot, to dynamically
125: 	       show the boot messages should they wish.
126:         FAM-4: New boot environments should be associated with a user defined
127: 	       label, for a more consistent and usable experience in the GRUB
128: 	       boot manager. Existing menu options during install and post-install
129: 	       should be simplified where possible for improved usability.
130: }}}
131: 
132: ==== 2.4 Hardware Support
133: 
134: {{{
135:         HDW-1: Ensure there is an easy mechanism to install hardware drivers 
136: 	       onto a potentially non-networked base system, when a driver is
137: 	       not installed by default.
138: }}}
139: 
140: ==== 2.5 Desktop
141: 
142: {{{
143:         DSK-1: Provide a graphical interface to allow the user to regularly
144: 	       back up their data onto an external drive using ZFS snapshots
145: 	       or mirroring. Users should be able to restore their data from
146: 	       a given back up drive with a simple grahical interface.
147:         DSK-2: A user should be able to automatically detect printers
148: 	       connected directly through USB, or attached to their network.
149: 	       For each printer, they should be able to configure their
150: 	       printing options with a simplified graphical user interface,
151: 	       along with monitoring any queues to that printer, and their
152: 	       current print job. Preferably this should be a CUPS based solution.
153:         DSK-3: Provide KDE and Xfce as alternative desktop environments for those
154: 	       wishing to install it.
155:         DSK-4: Provide an interface to easily switch between virtual consoles and
156: 	       existing desktop sessions through a series of keybindings.
157:         DSK-5: Compiz should be the default window manager for all capable
158: 	       graphics cards.
159:         DSK-6: Graphical boot should be the default option for OpenSolaris 2009.04,
160: 	       providing an obvious indication of boot progress. An option to allow
161: 	       advanced users to read boot messages with a simple key press toggle.
162:         DSK-7: Fast reboot should be the default option where possible. The system
163: 	       should try to detect whether drivers support quiesce(9E) or not
164: 	       and judge whether the environment is suitable for a fast reboot
165: 	       appropriately.
166: }}}
167: 
168: ==== 2.6 Network
169: 
170: {{{
171:         NET-1: Provide network virtualization and resource control, allowing the creation
172: 	       of a virtual stack that can be assigned its own priority and bandwidth
173: 	       on a shared NIC ie. Crossbow.
174:         NET-2: Provide a graphical interface to allow users to share out their
175: 	       network connection to others ie. they connect through a wired connection,
176: 	       and share out over wireless with a user set network encryption key.
177: 	       Additionally, users should be able to set predefined conditions for this
178: 	       network share like bandwidth allocation or CPU throttling.
179: }}}
180: 
181: ==== 2.7 Storage
182: 
183: {{{
184:         STO-1: Provide a iSCSI port provider adding support for an iSCSI transport
185: 	       option for COMSTAR.
186: }}}
187: 
188: ==== 2.8 Documentation
189: 
190: {{{
191:         DOC-1: Provide a wiki on opensolaris.com to host documentation for the OpenSolaris
192: 	       distribution, allowing users to be able to provide feedback on existing
193: 	       howtos based on their experiences.
194: }}}
195: 
196: ==== 2.9 Power Management
197: 
198: {{{
199:         PWR-1: Provide a tickless kernel architecture to OpenSolaris ensuring that
200: 	       all systems reduce their power consumption during idle periods, and
201: 	       power down the CPU appropriately.
202: }}}
203: 
204: ==== 2.10 Developer Stack
205: 
206: {{{
207:         DEV-1: Provide the latest versions of the popular GNU compiler stack used
208: 	       in common free software communities today, including autotools and scons.
209: 	       Versions should be decided on feedback from the pkgfactory project,
210: 	       and other consumers of that software.
211:         DEV-2: Provide Bazaar and Git in the package repository, 2 of the more popular
212:                source code management tools used in the open source communities.
213: 	DEV-3: Provide the popular JavaFX stack in the network package repository.
214: }}}
215: 
216: ==== 2.11 Web Stack
217: 
218: {{{
219:         WEB-1: Provide a set of the 10 most popular web development frameworks
220: 	       eg. Rails, Django, in the network package repository.
221:         WEB-2: Provide a set of the 10 most popular content management frameworks
222: 	       eg. Zope, Plone, Joomla!, Drupal, SilverStripe in the network
223: 	       package repository.
224:         WEB-3: Provide a set of the 5 most popular wiki frameworks eg. TWiki, JSPWiki,
225: 	       MediaWiki, Moin Moin in the network package repository.
226:         WEB-4: Provide a set of the 3 most popular blogging frameworks
227: 	       eg. Wordpress, Movable Type, Roller in the network package repository.
228:         WEB-5: Provide a set of 4 of the most popular database frameworks used by
229: 	       various web applications eg. MySQL, postgresql, sqlite, drizzle in the network
230: 	       repository.
231:         WEB-6: For at least 70% of the frameworks added, provide an initial set of
232:                DTrace probes to allow developers to profile their web applications
233:                in realtime.
234:         WEB-7: For at last 40% of the frameworks added, provide an optimized experience
235: 	       on OpenSolaris eg. optimized binaries, SMF service support
236:         WEB-8: For each framework added to the network package repository, provide the
237:                shortest time to startup possible, starting them using a default
238: 	       configuration, default database, and port so that the user can see the
239: 	       results of their software addition immediately.
240: }}}
241: 
242: ==== 2.12 Distribution Construction
243: 
244: {{{
245:         CON-1: Provide infrastructure to easily create virtual images for VirtualBox.
246:         CON-2: The distribution constructor should allow the creation of images to
247: 	       be used in co-ordination with the automated install web service.
248:         CON-3: The distribution constructor should have a graphical interface to
249: 	       accompany the command-line interface.
250: }}}
251: 
252: ==== 2.13 Device Detection
253: 
254: {{{
255:         DDU-1: Provide a means to submit the collected information securely to a
256: 	       centralized database, along with any additional reports from the user
257:                of whether certain devices work eg. sound. The user should get a
258:                confirmation thanking them for their submission, stating that it has
259:                been an invaluable contribution to the project, with a link to where
260:                their report is available to view anonymously. 
261:         DDU-2: The database should have a public front-end, preferably on opensolaris.org/com,
262:                allowing users to anonymously search entries that have been submitted, along
263:                with being able to get a series of reports based on the raw data eg. top 10
264:                wireless drivers that are supported, unsupported, or known to work. Additionally,
265:                the interface should allow the users to comment as appropriate on various 
266:                platforms with workarounds or otherwise that are available.  
267: }}}
OpenSolaris

Top Menu

Wiki code for Problem Statement

Search

Collectives

Community Group

Project

User Group

Subsites

Project indiana Pages
