[Blueprint server-o-boot-experience] Server boot experience
Blueprint changed by Clint Byrum: Whiteboard changed: Status: spec drafting, work items are still in flux Work Items: [cjwatson] turn off quiet for server: DONE [jamesodhunt] allow upstart visualization tool to filter out jobs/events that aren't in existence: POSTPONED [clint-fewbar] define/document a simple job/alias/event for networking up, for generic network services (event: static-network-up): DONE define/document a simple job/alias/event for system has booted, for /etc/rc.local type behavior: TODO improve start on for cron and other services (start when all user info available): TODO update Upstart Cookbook with abstract jobs and full exposition of how to define optimal start on and stop on for a new job: TODO [clint-fewbar] file bugs on services that don't respect single user mode appropriately: TODO [clint-fewbar] automated testing for single to multiuser: TODO - [clint-fewbar] add init-checkconf rule to lintian for upstart jobs: TODO + [clint-fewbar] add init-checkconf rule to lintian for upstart jobs (may be infeasible as emits lines aren't always available to validate start/stop on conditions): POSTPONED need to measure boot speed difference between sourcing /etc/default files, and not: TODO N/A work: define/document a simple job/alias/event for local filesystems are up, for local services -- already exists, local-filesystems define/document a simple job/alias/event for network filesystems are up, for network filesystem services - already exists, remote-filesystems Ideas * Serialize for debugging * Logging of job output (ideas also in upstart bug list) * Fencing (well defined sync points for boot) http://upstart.at/wp-content/uploads/2011/03/initctl2dot.png * as late as possible -- grub common one example for init.d * Generic Jobs (network-services, etc) * Document best practice in /usr/share/doc/upstart/examples and man page * Delay until all network interfaces are up * Default to always showing plymouth upstart bridge output * runlevel 1 and back to 2 doesn't work right * useful for emergency maintenance recovery * consider adding call to init-checkconf to lintian rule to ensure job config syntactically valid * clean-up behaviour of single-user mode * /etc/default/* - what to do Actions: -- Server boot experience https://blueprints.launchpad.net/ubuntu/+spec/server-o-boot-experience -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-boot-experience] Server boot experience
Blueprint changed by Clint Byrum: Whiteboard changed: - Status: spec drafting, work items are still in flux + Status: progress on some work items. + https://bugs.launchpad.net/ubuntu/+bugs?field.tag=runlevel1 bugs + reported. Work Items: [cjwatson] turn off quiet for server: DONE [jamesodhunt] allow upstart visualization tool to filter out jobs/events that aren't in existence: POSTPONED [clint-fewbar] define/document a simple job/alias/event for networking up, for generic network services (event: static-network-up): DONE define/document a simple job/alias/event for system has booted, for /etc/rc.local type behavior: TODO improve start on for cron and other services (start when all user info available): TODO update Upstart Cookbook with abstract jobs and full exposition of how to define optimal start on and stop on for a new job: TODO - [clint-fewbar] file bugs on services that don't respect single user mode appropriately: TODO - [clint-fewbar] automated testing for single to multiuser: TODO + [clint-fewbar] file bugs on services that don't respect single user mode appropriately: bug tag 'runlevel1' used for 21 bugs filed: DONE + [clint-fewbar] automated testing for single to multiuser: POSTPONED [clint-fewbar] add init-checkconf rule to lintian for upstart jobs (may be infeasible as emits lines aren't always available to validate start/stop on conditions): POSTPONED - need to measure boot speed difference between sourcing /etc/default files, and not: TODO + need to measure boot speed difference between sourcing /etc/default files, and not: POSTPONED N/A work: define/document a simple job/alias/event for local filesystems are up, for local services -- already exists, local-filesystems define/document a simple job/alias/event for network filesystems are up, for network filesystem services - already exists, remote-filesystems Ideas * Serialize for debugging * Logging of job output (ideas also in upstart bug list) * Fencing (well defined sync points for boot) http://upstart.at/wp-content/uploads/2011/03/initctl2dot.png * as late as possible -- grub common one example for init.d * Generic Jobs (network-services, etc) * Document best practice in /usr/share/doc/upstart/examples and man page * Delay until all network interfaces are up * Default to always showing plymouth upstart bridge output * runlevel 1 and back to 2 doesn't work right * useful for emergency maintenance recovery * consider adding call to init-checkconf to lintian rule to ensure job config syntactically valid * clean-up behaviour of single-user mode * /etc/default/* - what to do Actions: -- Server boot experience https://blueprints.launchpad.net/ubuntu/+spec/server-o-boot-experience -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-boot-experience] Server boot experience
Blueprint changed by Clint Byrum: Whiteboard changed: Status: progress on some work items. https://bugs.launchpad.net/ubuntu/+bugs?field.tag=runlevel1 bugs reported. Work Items: [cjwatson] turn off quiet for server: DONE [jamesodhunt] allow upstart visualization tool to filter out jobs/events that aren't in existence: POSTPONED [clint-fewbar] define/document a simple job/alias/event for networking up, for generic network services (event: static-network-up): DONE - define/document a simple job/alias/event for system has booted, for /etc/rc.local type behavior: TODO - improve start on for cron and other services (start when all user info available): TODO - update Upstart Cookbook with abstract jobs and full exposition of how to define optimal start on and stop on for a new job: TODO + define/document a simple job/alias/event for system has booted, for /etc/rc.local type behavior (note that 'stopped rc' is usable but not well documented): POSTPONED + improve start on for cron and other services (start when all user info available) (cron should probably start on stopped rc): POSTPONED + update Upstart Cookbook with abstract jobs and full exposition of how to define optimal start on and stop on for a new job: POSTPONED [clint-fewbar] file bugs on services that don't respect single user mode appropriately: bug tag 'runlevel1' used for 21 bugs filed: DONE [clint-fewbar] automated testing for single to multiuser: POSTPONED [clint-fewbar] add init-checkconf rule to lintian for upstart jobs (may be infeasible as emits lines aren't always available to validate start/stop on conditions): POSTPONED need to measure boot speed difference between sourcing /etc/default files, and not: POSTPONED N/A work: define/document a simple job/alias/event for local filesystems are up, for local services -- already exists, local-filesystems define/document a simple job/alias/event for network filesystems are up, for network filesystem services - already exists, remote-filesystems Ideas * Serialize for debugging * Logging of job output (ideas also in upstart bug list) * Fencing (well defined sync points for boot) http://upstart.at/wp-content/uploads/2011/03/initctl2dot.png * as late as possible -- grub common one example for init.d * Generic Jobs (network-services, etc) * Document best practice in /usr/share/doc/upstart/examples and man page * Delay until all network interfaces are up * Default to always showing plymouth upstart bridge output * runlevel 1 and back to 2 doesn't work right * useful for emergency maintenance recovery * consider adding call to init-checkconf to lintian rule to ensure job config syntactically valid * clean-up behaviour of single-user mode * /etc/default/* - what to do Actions: -- Server boot experience https://blueprints.launchpad.net/ubuntu/+spec/server-o-boot-experience -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-boot-experience] Server boot experience
Blueprint changed by Clint Byrum: Whiteboard changed: Status: spec drafting, work items are still in flux Work Items: [cjwatson] turn off quiet for server: DONE [jamesodhunt] allow upstart visualization tool to filter out jobs/events that aren't in existence: POSTPONED - [clint-fewbar] define/document a simple job/alias/event for networking up, for generic network services: TODO + [clint-fewbar] define/document a simple job/alias/event for networking up, for generic network services (event: static-network-up): DONE define/document a simple job/alias/event for system has booted, for /etc/rc.local type behavior: TODO improve start on for cron and other services (start when all user info available): TODO update Upstart Cookbook with abstract jobs and full exposition of how to define optimal start on and stop on for a new job: TODO [clint-fewbar] file bugs on services that don't respect single user mode appropriately: TODO [clint-fewbar] automated testing for single to multiuser: TODO [clint-fewbar] add init-checkconf rule to lintian for upstart jobs: TODO need to measure boot speed difference between sourcing /etc/default files, and not: TODO N/A work: define/document a simple job/alias/event for local filesystems are up, for local services -- already exists, local-filesystems define/document a simple job/alias/event for network filesystems are up, for network filesystem services - already exists, remote-filesystems Ideas * Serialize for debugging * Logging of job output (ideas also in upstart bug list) * Fencing (well defined sync points for boot) http://upstart.at/wp-content/uploads/2011/03/initctl2dot.png * as late as possible -- grub common one example for init.d * Generic Jobs (network-services, etc) * Document best practice in /usr/share/doc/upstart/examples and man page * Delay until all network interfaces are up * Default to always showing plymouth upstart bridge output * runlevel 1 and back to 2 doesn't work right * useful for emergency maintenance recovery * consider adding call to init-checkconf to lintian rule to ensure job config syntactically valid * clean-up behaviour of single-user mode * /etc/default/* - what to do Actions: -- Server boot experience https://blueprints.launchpad.net/ubuntu/+spec/server-o-boot-experience -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-boot-experience] Server boot experience
Blueprint changed by Dave Walker: Whiteboard changed: Status: spec drafting, work items are still in flux Work Items: [cjwatson] turn off quiet for server: DONE - [jamesodhunt] allow upstart visualization tool to filter out jobs/events that aren't in existence: TODO + [jamesodhunt] allow upstart visualization tool to filter out jobs/events that aren't in existence: POSTPONED [clint-fewbar] define/document a simple job/alias/event for networking up, for generic network services: TODO define/document a simple job/alias/event for system has booted, for /etc/rc.local type behavior: TODO improve start on for cron and other services (start when all user info available): TODO update Upstart Cookbook with abstract jobs and full exposition of how to define optimal start on and stop on for a new job: TODO [clint-fewbar] file bugs on services that don't respect single user mode appropriately: TODO [clint-fewbar] automated testing for single to multiuser: TODO [clint-fewbar] add init-checkconf rule to lintian for upstart jobs: TODO need to measure boot speed difference between sourcing /etc/default files, and not: TODO N/A work: define/document a simple job/alias/event for local filesystems are up, for local services -- already exists, local-filesystems define/document a simple job/alias/event for network filesystems are up, for network filesystem services - already exists, remote-filesystems Ideas * Serialize for debugging * Logging of job output (ideas also in upstart bug list) * Fencing (well defined sync points for boot) http://upstart.at/wp-content/uploads/2011/03/initctl2dot.png * as late as possible -- grub common one example for init.d * Generic Jobs (network-services, etc) * Document best practice in /usr/share/doc/upstart/examples and man page * Delay until all network interfaces are up * Default to always showing plymouth upstart bridge output * runlevel 1 and back to 2 doesn't work right * useful for emergency maintenance recovery * consider adding call to init-checkconf to lintian rule to ensure job config syntactically valid * clean-up behaviour of single-user mode * /etc/default/* - what to do Actions: -- Server boot experience https://blueprints.launchpad.net/ubuntu/+spec/server-o-boot-experience -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-boot-experience] Server boot experience
Blueprint changed by Colin Watson: Whiteboard changed: Status: spec drafting, work items are still in flux Work Items: - [cjwatson] turn off quiet for server: TODO + [cjwatson] turn off quiet for server: DONE [jamesodhunt] allow upstart visualization tool to filter out jobs/events that aren't in existence: TODO [clint-fewbar] define/document a simple job/alias/event for networking up, for generic network services: TODO define/document a simple job/alias/event for system has booted, for /etc/rc.local type behavior: TODO improve start on for cron and other services (start when all user info available): TODO update Upstart Cookbook with abstract jobs and full exposition of how to define optimal start on and stop on for a new job: TODO [clint-fewbar] file bugs on services that don't respect single user mode appropriately: TODO [clint-fewbar] automated testing for single to multiuser: TODO [clint-fewbar] add init-checkconf rule to lintian for upstart jobs: TODO need to measure boot speed difference between sourcing /etc/default files, and not: TODO N/A work: define/document a simple job/alias/event for local filesystems are up, for local services -- already exists, local-filesystems define/document a simple job/alias/event for network filesystems are up, for network filesystem services - already exists, remote-filesystems Ideas * Serialize for debugging * Logging of job output (ideas also in upstart bug list) * Fencing (well defined sync points for boot) http://upstart.at/wp-content/uploads/2011/03/initctl2dot.png * as late as possible -- grub common one example for init.d * Generic Jobs (network-services, etc) * Document best practice in /usr/share/doc/upstart/examples and man page * Delay until all network interfaces are up * Default to always showing plymouth upstart bridge output * runlevel 1 and back to 2 doesn't work right * useful for emergency maintenance recovery * consider adding call to init-checkconf to lintian rule to ensure job config syntactically valid * clean-up behaviour of single-user mode * /etc/default/* - what to do Actions: -- Server boot experience https://blueprints.launchpad.net/ubuntu/+spec/server-o-boot-experience -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-boot-experience] Server boot experience
Blueprint changed by Robbie Williamson: Assignee: (none) = Ubuntu Server Team -- Server boot experience https://blueprints.launchpad.net/ubuntu/+spec/server-o-boot-experience -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint server-o-boot-experience] Server boot experience
Blueprint changed by Robbie Williamson: Priority: Undefined = High -- Server boot experience https://blueprints.launchpad.net/ubuntu/+spec/server-o-boot-experience -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs