Opened 9 years ago

#427 new

milestone S2.d completion

Reported by: Seung-Jong Park Owned by: pkondi1@lsu.edu
Priority: major Milestone:
Component: CRON Version: SPIRAL2
Keywords: Cc: hmussman@bbn.com
Dependencies:

Description

Rspec allows advertising, Request and describing the resources used in CRON project. The format used in describing the Rspect is referred from Protogeni. Rspec is divided into three categories based on the purpose

  1. Advertisements – Used to describe the resources available on a Component Manager. They contain information used by clients to choose resources (components). Other kinds of information (MAC addresses, hostnames, etc.) which are not used to select resources should not be in the Advertisement.
  1. Requests - specify which resources a client is selecting from Component Managers. They contain a (perhaps incomplete) mapping between physical components and abstract nodes and links
  1. Manifests - provide useful information about the slivers actually allocated by a Component Manager to a client. This involves information that may not be known until the sliver is actually created (i.e. dynamically assigned IP addresses, hostnames), or additional configuration options provided to a client.

The resources offered by CRON are,
—PCs with 10G interface (Sun X4240)
—10G switch (Cisco Nexus 5000 series switch)
—10G hardware Emulator (Anue XGEM)

We have defined the advertisement Rspec for all the above resources as below.

<node component_manager_uuid="urn:publicid:IDN+cron.cct.lsu.edu+authority+cm" component_name="cisco10G" component_uuid="urn:publicid:IDN+cron.cct.lsu.edu+node+cisco10G">

<node_type type_name="switch" type_slots="1" /> <available>true</available>

<exclusive>true</exclusive> <interface component_id="urn:publicid:IDN+cron.cct.lsu.edu+interface+cisco10G:(null)” />

</node> <node component_manager_uuid="urn:publicid:IDN+cron.cct.lsu.edu+

authority+cm" component_name="pc2" component_uuid="urn:publicid:IDN+cron.cct.lsu.edu+node+pc2">

<node_type type_name="pc4240" type_slots="1" /> <node_type type_name="pc" type_slots="1" /> <node_type type_name="delay" type_slots="1" /> <node_type type_name="pcvm" type_slots="20" /> <available>true</available> <exclusive>true</exclusive> <interface component_id="urn:publicid:IDN+cron.cct.lsu.edu+ interface+ pc2:eth4" />

<interface component_id="urn:publicid:IDN+cron.cct.lsu.edu+

interface+pc2:eth5" />

<node component_manager_uuid="urn:publicid:IDN+cron.cct.lsu.edu+

authority+cm" component_name="em01" component_uuid="urn:publicid:IDN+cron.cct.lsu.edu+node+em01">

<node_type type_name="hwem" type_slots="1" /> <available>true</available> <exclusive>true</exclusive> <interface component_id="urn:publicid:IDN+cron.cct.lsu.edu+

interface+em01:eth0" />

<link component_manager_uuid="urn:publicid:IDN+cron.cct.lsu.edu+authority+sa" component_name="link-pc1:eth4-cisco10G:(null)" component_uuid="urn:publicid:IDN+cron.cct.lsu.edu+link+link-pc1:eth4- cisco10G:(null)">

<interface_ref

component_node_uuid="urn:publicid:IDN+cron.cct.lsu.edu+node+pc1" component_interface_id="urn:publicid:IDN+cron.cct.lsu.edu+

interface+pc1:eth4" />

<interface_ref

component_node_uuid="urn:publicid:IDN+cron.cct.lsu.edu+node+ cisco10G" component_interface_id="urn:publicid:IDN+cron.cct.lsu.edu+ interface+cisco10G:(null)" />

<bandwidth>10000000</bandwidth> <latency>0</latency> <packet_loss>0</packet_loss>

<link_type type_name="ethernet" />

</link>

Few aspects of hardware emulator Rspec needs to be finalized

Change History (0)

Note: See TracTickets for help on using tickets.