Features/Upstart0.6.0

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Benefit to Fedora)
(User Experience)
Line 70: Line 70:
 
== User Experience ==
 
== User Experience ==
 
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 +
Possibly some changes in command interfaces like initctl, but for most users noticing the change would be a Bad Thing.
  
 
== Dependencies ==
 
== Dependencies ==

Revision as of 18:45, 15 July 2009

Contents

Upstart 0.6.0

Summary

New upstart upstream release with a lot of new features.

Owner

  • email: <plautrba@redhat.com>
  • email: <cdahlin@redhat.com>

Current status

  • Targeted release: Fedora 21
  • Last updated: 2009-07-13
  • Percentage of completion: 01%


Detailed Description

Upstart is an event-based replacement for the /sbin/init daemon which handles starting of tasks and services during boot, stopping them during shutdown and supervising them while the system is running.

Feature highlights:

  • Tasks and Services are started and stopped by events;
  • Events are generated as tasks and services are started and stopped;
  • Events may be received from any other process on the system;
  • Services may be respawned if they die unexpectedly;
  • Supervision and respawning of daemons which separate from their parent process;
  • Communication with the init daemon over D-Bus.


Benefit to Fedora

The latest upstream Upstart version is 0.6.0 and upstream is pushing to have all the major distros move to the 0.6 series. The new release fixes a lot of bugs, strengthens some of the code patterns against future bugs, and introduces a job format that will continue to be supported through 1.0.

Scope

How To Test

  • Bring each upstart job up and down and verify that the job is started and cleaned up correctly and that initctl list reflects its state.
  • Move from runlevel s to 1, 3, and 5 and back again and verify that the system ends up in the correct state each time.
  • Re-exec init and verify that jobs that were running stay running according to initctl list.

User Experience

Possibly some changes in command interfaces like initctl, but for most users noticing the change would be a Bad Thing.

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion