UpstartJobAdministration
2462
Comment: converted to 1.6 markup
|
3032
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
## page was copied from SpecTemplate | |
Line 3: | Line 4: |
* '''Launchpad Entry''': UbuntuSpec:foo * '''Created''': * '''Contributors''': * '''Packages affected''': |
* '''Launchpad Entry''': UbuntuSpec:todo * '''Created''': 2010-05-24 * '''Contributors''': [[JacobPeddicord|Jacob Peddicord]] * '''Packages affected''': jobs-admin, jobservice (both new, names not final) |
Line 10: | Line 11: |
This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples. | This spec consists of two main components: * A service administration and configuration UI (say, jobs-admin) * Configuration backend (jobservice) jobs-admin, in short, would be a replacement for services-admin in gnome-system-tools but written with Upstart in mind. jobservice will be a dbus backend for jobs-admin which talks to Upstart and manages service-level settings. Key features of jobs-admin and jobservice include: * Upstart and SysV compatability * Service-level settings: ability to easily set a setting for a specific service; ex. a document-root for apache2. This includes the proposed Upstart 0.10 overrides. * Start/stop/enable/disable services |
Line 20: | Line 30: |
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. == Use Cases == |
== User stories == |
Line 51: | Line 59: |
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. | It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage. |
Line 55: | Line 63: |
== Outstanding Issues == | == Unresolved issues == |
Launchpad Entry: todo
Created: 2010-05-24
Contributors: Jacob Peddicord
Packages affected: jobs-admin, jobservice (both new, names not final)
Summary
This spec consists of two main components:
- A service administration and configuration UI (say, jobs-admin)
- Configuration backend (jobservice)
jobs-admin, in short, would be a replacement for services-admin in gnome-system-tools but written with Upstart in mind. jobservice will be a dbus backend for jobs-admin which talks to Upstart and manages service-level settings.
Key features of jobs-admin and jobservice include:
- Upstart and SysV compatability
- Service-level settings: ability to easily set a setting for a specific service; ex. a document-root for apache2. This includes the proposed Upstart 0.10 overrides.
- Start/stop/enable/disable services
Release Note
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
It is mandatory.
Rationale
User stories
Assumptions
Design
You can have subsections that better describe specific parts of the issue.
Implementation
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
UI Changes
Should cover changes required to the UI, or specific UI that is required to implement this
Code Changes
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Migration
Include:
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
Test/Demo Plan
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
DesktopTeam/Specs/Maverick/UpstartJobAdministration (last edited 2010-05-30 16:47:43 by pool-96-230-20-221)