Changes between Version 5 and Version 6 of Software/fImages/cBuildingCustomOS


Ignore:
Timestamp:
Aug 31, 2011, 7:23:05 PM (13 years ago)
Author:
seskar
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Software/fImages/cBuildingCustomOS

    v5 v6  
    44= Creating custom OS images =
    55
    6 In order to use an OS other than the one currently supported (Debian Linux kernel 2.6.12), you may do one of the following
    7  * 1) provide your own (frisbee) image of the OS of your choice '''or '''
    8  * 2) install the OS of your choice on our nodes from scratch. 
     6In order to use an OS other than the ones provided with stock images (Ubuntu based images), you can either provide your own (frisbee) image of the OS of your choice (that was prepared off-site) or use the netboot method on ORBIT infrastructure.
     7install the OS of your choice on our nodes from scratch. Regardless of the method, the resulting image should support:
    98
    10 == For Approach 1)  ==
    11 Here are a few guidelines
    12  * when you create your image, it occupies less than 20gb (make that 15 to be safe).
    13  * your OS image supports the following:
    14    * a serial console @9600,8,n,1 on the first serial port
    15    * driver support for 2 Marvell gigabit network card
    16    * and dhcp on the 2nd wired interface.
    17  * have wireless drivers (Atheros and Intel) support and a set of corresponding utilities installed
     9   * a serial console (@115K, 8, n, 1) on the first serial port
     10   * driver support for 2  gigabit network card
     11   * and dhcp on the 2nd wired gigabit network interface
    1812
    19 After you have an image, simply use
    20 {{{
    21 saveNode x,y
    22 }}}
    23 to save the image of the node in our repository for further use
     13== netboot method ==
    2414
    25 == For Approach 2) ==
    26 Our nodes support installation of any OS via network installers. 
     15 OS via network installers. 
    2716
    28 Please be sure the installer for the OS of your choice provides
    29 a serial console on the first serial port @9600,8,n,1 and has network
    30 drivers for the Marvell gigabit network cards (I believe they are officially
    31 Yukon compatible but I believe Marvell cards are mostly identical). 
     17Please be sure the installer for the OS of your choice provides
     18a serial console on the first serial port (@115K,8,n,1) and has
     19appropriate network drivers. 
    3220
    33  * The PXE service can be queried from any console at http://pxe:5012/pxe/. 
     21
    3422 * The XML interface is self explanatory. 
    3523 * Copy your boot script to /tftpboot on repository2 and control the boot behavior of your node via the PXE service.
    … …  
    4129will show you all of the available URLs. What you need to use is:
    4230
    43 http://pxe:5012/pxe/nodeSetBootImage?img="image_file_name"&nodes="set-of
    44 -nodes"
     31http://pxe:5012/pxe/nodeSetBootImage?img="image_file_name"&nodes="set-of-nodes"
    4532
    4633and:
    4734
    48 http://pxe:5012/pxe/nodeSetClearBootImage?img="image_file_name"&nodes="s
    49 et-of-nodes"
     35http://pxe:5012/pxe/nodeSetClearBootImage?img="image_file_name"&nodes="set-of-nodes"
    5036
    51 You have to come from the grid console to use this. Please let us know if
    52 permissions are not working as expected or if you have problems with the
    53 service.
     37You have to come from the domain console to use this service (i.e. if you are working with the node in sb1 you have to issue this on console.sb1).
    5438
    55 To interact with your node, follow the instructions on our FAQ concerning
    56 interaction via serial consoles
     39To interact with your node, follow the instructions on our FAQ concerning interaction via serial consoles
    5740
     41After you have an image, simply use
     42{{{
     43omf save x,y
     44}}}
     45to save the image of the node in our repository for further use