<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://beren.engr.udel.edu/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>UDCECC Wiki caviness</title>
        <description></description>
        <link>http://beren.engr.udel.edu/</link>
        <lastBuildDate>Tue, 28 Apr 2026 16:10:27 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>http://beren.engr.udel.edu/lib/tpl/bootstrap3/images/favicon.ico</url>
            <title>UDCECC Wiki</title>
            <link>http://beren.engr.udel.edu/</link>
        </image>
        <item>
            <title>caviness:jobs</title>
            <link>http://beren.engr.udel.edu/caviness/jobs?rev=1561656835</link>
            <description>Running jobs

Caviness uses the Slurm workload manager, a free and open-source resource management and job scheduling system.  Users are expected to submit jobs with accurate resource requirements (node and core counts, memory size limits, time limits) so that Slurm can match your work against available compute resources.  Some general rules of thumb with regard to job submission:</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>caviness</category>
            <pubDate>Thu, 27 Jun 2019 17:33:55 +0000</pubDate>
        </item>
        <item>
            <title>caviness:login</title>
            <link>http://beren.engr.udel.edu/caviness/login?rev=1604934862</link>
            <description>Round-robin DNS load balancing returns multiple IP addresses when the name</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>caviness</category>
            <pubDate>Mon, 09 Nov 2020 15:14:22 +0000</pubDate>
        </item>
        <item>
            <title>caviness:resources</title>
            <link>http://beren.engr.udel.edu/caviness/resources?rev=1561728906</link>
            <description>Resources

The design of Caviness is similar to previous community clusters.

Compute

Designed as a multi-generational system, over time Caviness will host a variety of nodes, differing not just in memory sizes and presence of coprocessors but also in processor microarchitecture.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>caviness</category>
            <pubDate>Fri, 28 Jun 2019 13:35:06 +0000</pubDate>
        </item>
        <item>
            <title>caviness:start</title>
            <link>http://beren.engr.udel.edu/caviness/start?rev=1561650837</link>
            <description>Caviness

The Caviness cluster was built in late 2018 according to a rolling upgradeable design strategy.  Like previous community clusters, over time additional nodes will be added.  But starting in the sixth year of its life, nodes exiting their warranty period will be replaced and the infrastructure surrounding them reused.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>caviness</category>
            <pubDate>Thu, 27 Jun 2019 15:53:57 +0000</pubDate>
        </item>
        <item>
            <title>caviness:valet</title>
            <link>http://beren.engr.udel.edu/caviness/valet?rev=1561655502</link>
            <description>Using VALET

VALET, a module-like system developed and maintained at UD, makes it easy to manage your environment so you have access to the software that you use to conduct your work on Caviness.  On a system like Caviness there are simultaneously many different software packages present, and many unique versions and variants of those packages.  Some software is maintained by UD IT for all of the users of Caviness.  Some software is maintained by individual workgroups or users.  Having a single …</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
        <category>caviness</category>
            <pubDate>Thu, 27 Jun 2019 17:11:42 +0000</pubDate>
        </item>
    </channel>
</rss>
