Public bug reported: = Overview =
This bug documents a number of new features we'd like to introduce to the upstart package for raring. = New Features = == Enabling of User Sessions == https://wiki.ubuntu.com/FoundationsTeam/Specs/RaringUpstartUserSessions === Rationale === Upstart 1.7, which is already in the archive, provides enhanced user sessions. These offer a wealth of benefits as listed on: http://upstart.ubuntu.com/cookbook/#session-init Further, they are planned for inclusion in raring at the request of the Desktop Team (seb128 is a prime contact). === Risk === LOW/MEDIUM - although well tested by the Foundations Team who have been running desktop sessions managed by upstart for some weeks now, all desktop elements that wish to "opt-in" to having the session managed by Upstart need to provide their own Upstart Session Job. At the time of writing, the elements that are required prior to enabling Upstart User Sessions but which have not yet landed are: - D-Bus: stgraber has a branch in proposed with the required /usr/share/upstart/sessions/dbus.conf job file. - ssh-agent: TODO. - im-switch: TODO. Once the final elements are in place, the default 'ubuntu' desktop will migrate from being managed by gnome-session to being manged by Upstart. This will require final testing by both the Foundations and Desktop teams. === Contingency === Revert to the gnome-session-managed desktop. However, this is potentially hampered by bug 1131968. == New Upstart Bridge: upstart-file-bridge == The upstart-file-bridge is a now process that will be run both as a system job (as root), and as a user session job (1 per Upstart Session). === Rationale === The upstart-file-bridge provides the ability for Upstart jobs to 'start on' actual files in the filesystem being created, modified or deleted. This allows some of what are currently long-running daemons to just run 'on demand'. A good example of this is whoopsie: currently it runs all the time, but with the file bridge its Upstart job configuration file can be modified to be: start on file FPATH=/var/crash/*.crash FEVENT=create exec whoopsie This will have the effect of only starting whoopsie iff and when crash files are created. As such, this is a valuable tool in our ongoing efforts to reduce memory consumption and speed up the boot. === Risk === LOW - this is a new facility. If it does not work, any application that makes use of it may not start, but can still be started manually should the need arise. Additionally, this bridge is not running within init itself so any instability will not affect system reliability. === Contingency === Disable the bridge if it proves problematic and revert applications such as whoopsie to running all the time. == Upstart GUI: upstart-monitor == The upstart-monitor is a simple python application that shows upstart events (both system-level and session-level) as they occur. === Rationale === Now that Upstart is able to manage a user sessions, non-privileged users will potentially be able to explore Upstarts benefits for themselves without having to worry about destablising their systems. This is a huge opportunity for Upstart and any tooling that makes it easier to use should be considered IMHO. This tool should be extremely useful to newcomers to Upstart and even to experienced admins who wish to observe event flows. It also makes it significantly easier to write custom session jobs. === Risk === LOW - this tool runs as a non-privileged user and does not provide any more information than can currently be ascertained using existing tooling - it just puts it into a familiar form. === Contingency === Disable/remove the tool. == Apport hook == === Rationale === - Upstart currently has no apport hook. - We intend to enable User Sessions which expands the scope for upstart so although we have tested the code as thoroughly as possible, if problems occur, an apport hook will be invaluable to simplify the job of both reporting the issue and diagnosing them. === Risk === LOW - this hook is not part of the init daemon itself and is only invoked when Upstart crashes. === Contingency === Even if this apport hook crashes, apport still allows a problem to be reported; it just won't have all the extra attachments the hook is designed to capture. ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Description changed: = Overview = This bug documents a number of new features we'd like to introduce to the upstart package for raring. = New Features = == Enabling of User Sessions == https://wiki.ubuntu.com/FoundationsTeam/Specs/RaringUpstartUserSessions === Rationale === Upstart 1.7, which is already in the archive, provides enhanced user sessions. These offer a wealth of benefits as listed on: http://upstart.ubuntu.com/cookbook/#session-init Further, they are planned for inclusion in raring at the request of the Desktop Team (seb128 is a prime contact). === Risk === LOW/MEDIUM - although well tested by the Foundations Team who have been running desktop sessions managed by upstart for some weeks now, all desktop elements that wish to "opt-in" to having the session managed by Upstart need to provide their own Upstart Session Job. At the time of writing, the elements that are required prior to enabling Upstart User Sessions but which have not yet landed are: - D-Bus: stgraber has a branch in proposed with the required /usr/share/upstart/sessions/dbus.conf job file. - ssh-agent: TODO. - im-switch: TODO. Once the final elements are in place, the default 'ubuntu' desktop will migrate from being managed by gnome-session to being manged by Upstart. This will require final testing by both the Foundations and Desktop teams. === Contingency === Revert to the gnome-session-managed desktop. However, this is potentially hampered by bug 1131968. == New Upstart Bridge: upstart-file-bridge == The upstart-file-bridge is a now process that will be run both as a system job (as root), and as a user session job (1 per Upstart Session). === Rationale === The upstart-file-bridge provides the ability for Upstart jobs to 'start on' actual files in the filesystem being created, modified or deleted. This allows some of what are currently long-running daemons to just run 'on demand'. A good example of this is whoopsie: currently it runs all the time, but with the file bridge its Upstart job configuration file can be modified to be: - start on file FPATH=/var/crash/*.crash FEVENT=create - exec whoopsie + start on file FPATH=/var/crash/*.crash FEVENT=create + exec whoopsie This will have the effect of only starting whoopsie iff and when crash files are created. As such, this is a valuable tool in our ongoing efforts to reduce memory consumption and speed up the boot. === Risk === LOW - this is a new facility. If it does not work, any application that makes use of it may not start, but can still be started manually should the need arise. Additionally, this bridge is not running within init itself so any instability will not affect system reliability. === Contingency === Disable the bridge if it proves problematic and revert applications such as whoopsie to running all the time. == Upstart GUI: upstart-monitor == - The upstart-monitor is a simple python application that shows upstart events (both system-level and session-level) as they occur. + The upstart-monitor is a simple python application that shows upstart + events (both system-level and session-level) as they occur. + === Rationale === Now that Upstart is able to manage a user sessions, non-privileged users will potentially be able to explore Upstarts benefits for themselves without having to worry about destablising their systems. This is a huge opportunity for Upstart and any tooling that makes it easier to use should be considered IMHO. This tool should be extremely useful to newcomers to Upstart and even to experienced admins who wish to observe event flows. It also makes it significantly easier to write custom session jobs. === Risk === LOW - this tool runs as a non-privileged user and does not provide any more information than can currently be ascertained using existing tooling - it just puts it into a familiar form. === Contingency === Disable/remove the tool. == Apport hook == === Rationale === - Upstart currently has no apport hook. - We intend to enable User Sessions which expands the scope for upstart so although we have tested the code as thoroughly as possible, if problems occur, an apport hook will be invaluable to simplify the job of both reporting the issue and diagnosing them. === Risk === LOW - this hook is not part of the init daemon itself and is only invoked when Upstart crashes. === Contingency === Even if this apport hook crashes, apport still allows a problem to be reported; it just won't have all the extra attachments the hook is designed to capture. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155205 Title: FFE Request for Upstart in raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1155205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
