{section: Lark}
{subsection: Introduction}
-Lark is a NSF-funded project for adding network-awareness to Condor's High Throughput Computing approach.
+Lark is a NSF-funded project for adding network-awareness to HTCondor's High Throughput Computing approach.
Broadly, it can be split into three major areas:
-*: Advanced Network Testbed: A small testbed for Condor networking technologies. Consists of dedicated Condor pools at Wisconsin and Nebraska. This will serve as a "launch point" for Lark technologies onto the production clusters at the sites.
-*: Network Monitoring: Integrating existing network monitoring tools (particularly, perfSONAR) into the Condor ecosystem. This will provide various Condor daemons with the ability to make decisions based on the observed network state.
-*: Network Management: Have Condor actively alter the network layer based on its internal policies.
+*: Advanced Network Testbed: A small testbed for HTCondor networking technologies. Consists of dedicated HTCondor pools at Wisconsin and Nebraska. This will serve as a "launch point" for Lark technologies onto the production clusters at the sites.
+*: Network Monitoring: Integrating existing network monitoring tools (particularly, perfSONAR) into the HTCondor ecosystem. This will provide various HTCondor daemons with the ability to make decisions based on the observed network state.
+*: Network Management: Have HTCondor actively alter the network layer based on its internal policies.
Lark started on October 1 and will last for approximately two years. More information will be added to this wiki page as the project progresses.
{subsection: Advanced Network Testbed (ANT)}
-The ANT consists of small Condor pools at Nebraska and Wisconsin. These are meant to test Lark technologies and harden existing advanced Condor network technologies.
+The ANT consists of small HTCondor pools at Nebraska and Wisconsin. These are meant to test Lark technologies and harden existing advanced HTCondor network technologies.
Example ANT use cases include:
*: Verification of IPv6 support, especially of the flocking use case.
@@ -22,9 +22,9 @@
{subsection: Network Monitoring}
-Condor is relatively uninformed of the underlying network conditions. For example, its queuing is based on the number of concurrent file transfers, regardless of whether the underlying network is 100Mbps or 100 Gbps.
+HTCondor is relatively uninformed of the underlying network conditions. For example, its queuing is based on the number of concurrent file transfers, regardless of whether the underlying network is 100Mbps or 100 Gbps.
-The network monitoring task will work on gathering data from the perfSONAR boxes in the DYNES project and pushing them into a Condor collector.
+The network monitoring task will work on gathering data from the perfSONAR boxes in the DYNES project and pushing them into a HTCondor collector.
From there, the schedd would be able to utilize this information to better adjust its concurrent file transfers.
@@ -35,4 +35,4 @@
Personnel responsible: Zhe Zhang, Brian Bockelman
{subsection: Development Documentation}
-*: {wiki: NetworkRelatedPolicy Network Related Policy for Condor}
+*: {wiki: NetworkRelatedPolicy Network Related Policy for HTCondor}
