Changes between Version 13 and Version 14 of LAMP/Tutorial


Ignore:
Timestamp:
09/21/10 14:41:36 (9 years ago)
Author:
fernande@cis.udel.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LAMP/Tutorial

    v13 v14  
    6565   
    6666   <link virtual_id="link1" >
    67       <interface_ref virtual_node_id="client1" virtual_interface_id="iface0"/>
    68       <interface_ref virtual_node_id="client2" virtual_interface_id="iface0"/>
     67      <interface_ref virtual_node_id="node1" virtual_interface_id="iface0"/>
     68      <interface_ref virtual_node_id="node2" virtual_interface_id="iface0"/>
    6969      <link_type type_name="ethernet" />
    7070      <latency>100</latency>
     
    8686}}}
    8787
    88 We can see on the above RSpec three LAMP specific elements: the startup_command for running the bootstrapping script, the disk image element with the LAMP image, and the <lamp:config> extension (note the XML namespace for this extension at the top). The startup_command will run a shell script that sets up a few basic variables describing the node so that the LAMP services know where they're running. Services will not be able to run without these variables set. The usage for this script is as follows.
     88We can see on the above RSpec three LAMP-specific elements: the startup_command for running the bootstrapping script, the disk image element with the LAMP image, and the `<lamp:config>` extension (note the XML namespace for this extension at the top). The startup_command will run a shell script that sets up a few basic variables describing the node so that the LAMP services know where they're running. Services will not be able to run without these variables set. The usage for this script is as follows.
    8989
    9090{{{
     
    9494Bootstrapping only needs to be done once, but the script is idempotent and can thus be run through the startup_command directive of the ProtoGENI CF. Alternatively, you can also run this command manually on the nodes and restart the configuration service (more on this later).
    9595
    96 The next element of our RSpec, the disk_image directive, has already been discussed above. Finally, the `<lamp:config />` extension lets us specify the initial configuration for our nodes. For example, looking at the ''lamp'' node in the RSpec, we see that we have specified that the lamp_portal service should be enabled. '''This extension, however, also specifies which nodes can be configured through the LAMP Portal (and topology annotations).''' This is why we have the empty config element `<lamp:config />` on the ''node1'' and ''node2'' nodes. In other words, the ''lamp'' node will be our host for accessing the LAMP Portal, wherein we can configure all three nodes of our slice.
     96The next LAMP-specific element in our RSpec, the disk_image directive, has already been discussed above. Finally, the `<lamp:config />` extension lets us specify the initial configuration for our nodes. For example, looking at the ''lamp'' node in the RSpec, we see that we have specified that the lamp_portal service should be enabled. '''This extension, however, also specifies which nodes can be configured through the LAMP Portal (and topology annotations).''' This is why we have the empty config element `<lamp:config />` on the ''node1'' and ''node2'' nodes. In other words, the ''lamp'' node will be our host for accessing the LAMP Portal, wherein we can configure all three nodes of our slice.
    9797
    9898Other services can be enabled using the same mechanism, but on this quick start guide we will only cover enabling and configuring services through the LAMP Portal (who wants to read and write XML after all? :).
     
    104104
    105105
     106