Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
soc:2009:pravin:project_plan:start [2009/05/22 16:28] less1 |
soc:2009:pravin:project_plan:start [2009/06/03 14:48] (current) less1 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Pravin Shinde: boot.kernel.org - Universal remote network booting for the masses ====== | ====== Pravin Shinde: boot.kernel.org - Universal remote network booting for the masses ====== | ||
| + | Project aims for creation of website, which can be used by any user for creating and downloading | ||
| + | customized boot images, system tools, utilities and network installation images based on needs. | ||
| + | It will also support HTTP based booting with PXELinux and allow users to customize the system using | ||
| + | the flexibility of interface provided be Syslinux and boot from it without installation. We plan to enable normal | ||
| + | users to experiment with different tools, utilities and system images without any hassles. | ||
| + | |||
| + | ===== Project Plan ===== | ||
| + | |||
| This project is about making the network boot process available to users on a large scale. | This project is about making the network boot process available to users on a large scale. | ||
| Line 25: | Line 33: | ||
| This customized PXEClient is nothing but regular PXELinux with an embedded script that sets the "next-server" | This customized PXEClient is nothing but regular PXELinux with an embedded script that sets the "next-server" | ||
| to boot.kernel.org regardless of what the local DHCP server provides. This way, any user can use boot.linux.org without | to boot.kernel.org regardless of what the local DHCP server provides. This way, any user can use boot.linux.org without | ||
| - | having to (re)configure a dhcp server. | + | having to (re)configure a dhcp server. [Done] |
| Machines with static IP addresses can be handled by providing a separate embedded script which can be generated at | Machines with static IP addresses can be handled by providing a separate embedded script which can be generated at | ||
| Line 31: | Line 39: | ||
| values will be hard-coded into the embedded script which will be bundled with PXEClient handed to the user. | values will be hard-coded into the embedded script which will be bundled with PXEClient handed to the user. | ||
| User will be provided with web-interface at boot.linux.org where he will feed in his network setting, and customized | User will be provided with web-interface at boot.linux.org where he will feed in his network setting, and customized | ||
| - | PXEClient embedded script for user's network will be automatically generated. | + | PXEClient embedded script for user's network will be automatically generated. [Currently working on] |
| These customized PXElinux clients will start the machine and contact boot.kernel.org. boot.kernel.org will return a | These customized PXElinux clients will start the machine and contact boot.kernel.org. boot.kernel.org will return a | ||
| Line 70: | Line 78: | ||
| Most distributions come with network boot support over TFTP. But with small modifications these destributions can | Most distributions come with network boot support over TFTP. But with small modifications these destributions can | ||
| also support booting and installation over HTTP. | also support booting and installation over HTTP. | ||
| - | |||
| - | ===== Project Plan ===== | ||
| ==== Summary ==== | ==== Summary ==== | ||
| Line 78: | Line 84: | ||
| ==== Milestones and Timeline ==== | ==== Milestones and Timeline ==== | ||
| + | Deliverables with Timeline (Duration = 12 weeks) | ||
| + | |||
| + | [Week-0,1] | ||
| + | 1. PXE Knife on HTTP. | ||
| + | 2. PXE clients with embedded scripts. | ||
| + | |||
| + | [Week-2,3] | ||
| + | 3. Web interface for customized PXE-client based on network configuration of the user. | ||
| + | 4. Web interface for PXE Knife images of HTTP. | ||
| + | |||
| + | [Week-4] | ||
| + | 5. Detailed Syslinux menu from where user can choose which applications he wants add. | ||
| + | |||
| + | [Week-5,6] | ||
| + | 6. Base system with generic kernel and base initrdfs which should boot on most of the systems. | ||
| + | |||
| + | [Week-7,8] | ||
| + | 7. Precompiled applications and their respective configurations. | ||
| + | |||
| + | [Week-9,10] | ||
| + | 8. scripts for dynamically appending above precompiled applications into initramfs, | ||
| + | and reconfiguring the system so that appended application will work. | ||
| + | |||
| + | [Week-11] | ||
| + | 9. Providing various Network installable distributions online. | ||
| + | 10. Documentation | ||
| + | [End] | ||
