Tags:
create new tag
, view all tags

ASTDL

What is ASTDL?

Application Specific Topology Description Language (ASTDL) is the tool developed to define, instantiate and manage those application specific networks. Indeed, ASTDL provides the ability to describe all the resources to be incorporated into an application include those resources that reside on end systems (not particularly network resources). The entire distributed application topology can thereby be formally and completely specified and captured in an XML text file that can be processed by web services agents or other tools.

While there are different established XML schema on network topology, such as Network Descriptive Language from University of Amsterdam and perfSONAR, these schema are designed to describe a known topology and is more geared to be used by network engineers or people who have some experience in network management. What AST needs is a more flexible schema that enables the schema to work in different kinds of provisioning systems and is intuitive enough for regular users.

In particular, here are some of the considerations in designing the ASTDL for AST. AST is a tool for users who would like to run their applications over a dynamic network. These users are mostly likely NOT network engineer who would understand the nuts and bolts in provisioning a link over a heterogeneous or homogeneous network. What the AST users care is that they can easily provision a topology and use it when they want to run their application or experiment. Thus, a lot of details about the end systems and the network are going to be filled in automatically by AST, not by the user who submit the AST requests. Besides, AST also needs to know extra details on the node resource even if that node resource is not a network resource. For example, in e-VLBI application, AST would also need to understand certain aspects of a telescope in order to set up the experiment correctly.

ASTDL is still under constantly revision. As ASTDL gets more mature, the changes in the schema will be minor and backward compatibility to older version of ASTDL will be provided.

Warning: Can't find topic AST.NodeResource

Warning: Can't find topic AST.LinkResource

Warning: Can't find topic AST.CompositeResource

ASTDL Examples

SETUP_REQ

<topology action="setup_req">
<xml_file>xml_schema/a-b.xml</xml_file>
<resource res_type="node" subtype="dragon_node_pc" name="max-es2">
        <ip>X.X.X.X</ip>
        <res_details>
                <command>ping $max-lab4.dest</command>
        </res_details>
</resource>
<resource res_type="node" subtype="dragon_node_pc" name="lab4-es1">
        <ip>X.X.X.X</ip>
</resource>
<resource res_type="link" subtype="dragon_link" name="max-lab4">
        <res_details dragon_type="uni">
                <link_status>did_not_commit</link_status>
                <src>
                        <node>max-es2</node>
                </src>
                <dest>
                        <node>lab4-es1</node>
                </dest>
                <te_params profile="EtherBasic">
                </te_params>
        </res_details>
</resource>

SETUP_RESP

<topology ast_id="leia.east.isi.edu_1192056756" action="release_resp">
<status>ast_success</status>
<xml_file>xml_schema/a-b.xml</xml_file>
<resource res_type="node" subtype="dragon_node_pc" name="max-es2">
        <status>ast_success</status>
        <ip>X.X.X.X</ip>
        <res_details>
                <router_id>X.X.X.X</router_id>
                <tunnel>gre3</tunnel>
                <ifaces>
                        <iface>eth1.3000</iface>
                        <assign_ip>140.173.96.41</assign_ip>
                        <vtag>3000</vtag>
                </ifaces>
        </res_details>
</resource>
<resource res_type="node" subtype="dragon_node_pc" name="lab4-es1">
        <status>ast_success</status>
        <ip>X.X.X.X</ip>
        <res_details>
                <router_id>X.X.X.X</router_id>
                <tunnel>gre1</tunnel>
                <ifaces>
                        <iface>eth1.3000</iface>
                        <assign_ip>140.173.96.42/30</assign_ip>
                        <vtag>3000</vtag>
                </ifaces>
        </res_details>
</resource>
<resource res_type="link" subtype="dragon_link" name="max-lab4">
        <status>ast_success</status>
        <ip>206.196.176.147</ip>
        <res_details dragon_type="uni">
                <link_status>in-service</link_status>
                <lsp_name>AST-619174192</lsp_name>
                <src>
                        <node>max-es2</node>
                        <iface>eth1.3000</iface>
                        <assign_ip>140.173.96.41</assign_ip>
                </src>
                <dest>
                        <node>lab4-es1</node>
                        <iface>eth1.3000</iface>
                        <assign_ip>140.173.96.42/30</assign_ip>
                </dest>
                <te_params>
                        <bandwidth>eth100M</bandwidth>
                        <swcap>l2sc</swcap>
                        <encoding>ethernet</encoding>
                        <gpid>ethernet</gpid>
                        <vtag>3000</vtag>
                </te_params>
        </res_details>
</resource>
</topology>
Topic revision: r4 - 2008-04-01 - FionaLeung
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback