<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://oar.imag.fr/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://oar.imag.fr/feed.php">
        <title>OAR - wiki</title>
        <description></description>
        <link>https://oar.imag.fr/</link>
        <image rdf:resource="https://oar.imag.fr/_media/wiki:dokuwiki.svg" />
       <dc:date>2026-04-11T08:56:32+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:about_the_general_data_protection_regulation?rev=1523432382&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:about_the_job_resources_manager?rev=1613067729&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:an_equivalent_to_slurm_s_srun_for_oar?rev=1505393754&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:aptly?rev=1499201400&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:augeas?rev=1415025875&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:bug_tracking?rev=1418219099&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:coreos?rev=1393593403&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:coupling_oarsh_with_gnu_parallel_to_mimic_salloc_srun?rev=1587044734&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:criu?rev=1553618992&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:custom_admission_rules?rev=1585146497&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:customization_tips?rev=1585146276&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:database_slow_queries?rev=1436113921&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:debian_packaging?rev=1740659934&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:dedicated_command_for_queue_management?rev=1392488409&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:developing_admission_rules?rev=1584986827&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:disk_reservation?rev=1480700039&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:document_the_migration_from_an_existing_mysql_database_to_postgresql?rev=1392738936&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:documentation?rev=1393587677&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:dokuwiki?rev=1748266447&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:dput_setup?rev=1617197563&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:editors?rev=1393587716&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:enable_to_mix_timesharing_modes?rev=1456925201&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:example_of_setup_with_oar_energy_saving_mechanism?rev=1460115779&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:fix_for_database_schema_version_2.5.0?rev=1414780535&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:froggy_job_resource_manager_ht?rev=1436084598&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:green_computing?rev=1585145971&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:gvirt?rev=1584621499&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:handle_systemd_api_for_managing_oar_cgroups?rev=1407418351&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:how_i_work_with_oar-docker?rev=1434054257&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:how_to_handle_a_bigger_and_bigger_oar_database?rev=1467226491&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:implement_quotas_based_on_cpu-time_into_the_scheduler?rev=1407172037&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:job_event_notifications?rev=1458776302&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:job_scheduling_constraints?rev=1456926116&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:job_types?rev=1539616821&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:linux_cgroup_sysfs_and_other_sysctl?rev=1430419489&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:managing_resources_cpu_gpu?rev=1583241004&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:migrate_runner_module_into_almighty_bipbip_handler_processus?rev=1395570956&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:migration_from_a_mysql_to_a_postgresql_database?rev=1443021088&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:multi-cluster_with_priority?rev=1613064087&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:nix?rev=1399981889&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:nonexisting?rev=1373448888&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:oar_drmaa_interface?rev=1442432859&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:oar_skylight?rev=1487771715&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:oar-docker-admin?rev=1488817468&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:oar-docker?rev=1585662217&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:oar-vagrant?rev=1712758812&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:oar3_dev_with_oar_docker?rev=1486117217&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:oardocker_setup_for_grid_5000?rev=1585662134&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:oarstat_vs_rest_api?rev=1481575216&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:oarwalltime?rev=1582028267&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:pagename?rev=1373448867&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:passing_environment_variables_to_openmpi_nodes?rev=1706640298&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:processors?rev=1393518958&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:publication_of_the_documentation?rev=1455607784&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:releasing?rev=1445879891&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:rename_oar_modules?rev=1432650819&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:reprepro?rev=1414623462&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:rest-api-specs?rev=1478470605&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:rpm_packaging?rev=1611325600&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:running_the_api_tests?rev=1498834149&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:sbuild-debian?rev=1601299825&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:schroot-centos?rev=1373359928&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:setup_a_oar_cluster_on_a_single_machine?rev=1395775802&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:some_examples_of_admission_rules?rev=1586289689&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:source_control?rev=1393587511&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:start?rev=1584985427&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:syntax?rev=1748266447&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:systemd_for_administrators?rev=1415021123&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:tarball_release?rev=1455574830&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:technology_watch?rev=1484820367&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:testing?rev=1531912714&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:ui_toolkit?rev=1393593133&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:use_a_cache_system_in_the_scheduling_algorithms?rev=1404479518&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:use_cases_and_user_tips?rev=1627480792&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:useful_commands_and_administration_tasks?rev=1585145707&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:using_hyperthreading_on_nodes?rev=1441380240&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:using_oar_on_debian_based_systems?rev=1585661384&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:using_oar_on_redhat_based_systems?rev=1585661518&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:web_ui?rev=1393593799&amp;do=diff"/>
                <rdf:li rdf:resource="https://oar.imag.fr/wiki:welcome?rev=1748266447&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://oar.imag.fr/_media/wiki:dokuwiki.svg">
        <title>OAR</title>
        <link>https://oar.imag.fr/</link>
        <url>https://oar.imag.fr/_media/wiki:dokuwiki.svg</url>
    </image>
    <item rdf:about="https://oar.imag.fr/wiki:about_the_general_data_protection_regulation?rev=1523432382&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-04-11T07:39:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>about_the_general_data_protection_regulation</title>
        <link>https://oar.imag.fr/wiki:about_the_general_data_protection_regulation?rev=1523432382&amp;do=diff</link>
        <description>Europe is pushing for a new regulation for data protection: &lt;https://www.eugdpr.org&gt; (translated to RGPD in french).

In short, user data are sensitive data that shouldn&#039;t be conserved forever in databases.

With regards to OAR, that would mean that usernames associated to jobs in a OAR database should be forgotten after some time. Another option could be to anonymize them.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:about_the_job_resources_manager?rev=1613067729&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-02-11T18:22:09+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>about_the_job_resources_manager</title>
        <link>https://oar.imag.fr/wiki:about_the_job_resources_manager?rev=1613067729&amp;do=diff</link>
        <description>Job resource manager

The part of OAR that is usually responsible for setting up and cleaning up the operating system of resources
given to a job is the job resource manager.

This is a Perl script that is part of the OAR configuration files:
located on the OAR server in</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:an_equivalent_to_slurm_s_srun_for_oar?rev=1505393754&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-09-14T12:55:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>an_equivalent_to_slurm_s_srun_for_oar</title>
        <link>https://oar.imag.fr/wiki:an_equivalent_to_slurm_s_srun_for_oar?rev=1505393754&amp;do=diff</link>
        <description>Slurm&#039;s “srun” runs a given command (or script) on a reserved set of
resources, ties stdout and stderr to those of the parent process, and
exits with the exit code of the called script.

e.g. you can do
   srun make
It&#039;s great for batch scripts that run on the frontend.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:aptly?rev=1499201400&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-07-04T20:50:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>aptly</title>
        <link>https://oar.imag.fr/wiki:aptly?rev=1499201400&amp;do=diff</link>
        <description>OAR&#039;s Debian repositories setup

For a list of the existing management tools for Debian packages, see:

	*  &lt;https://wiki.debian.org/HowToSetupADebianRepository&gt;

Til August 2015, reprepro was used to manage OAR&#039;s Debian packages (thx plb). But:

	*  it was difficult to use
	*  it was difficult to maintain</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:augeas?rev=1415025875&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-03T14:44:35+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>augeas</title>
        <link>https://oar.imag.fr/wiki:augeas?rev=1415025875&amp;do=diff</link>
        <description>Edit Configuration Files with Augeas

From Augeas site:

“Augeas is a configuration editing tool. It parses configuration files in their native formats and transforms them into a tree. Configuration changes are made by manipulating this tree and saving it back into native config files.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:bug_tracking?rev=1418219099&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-12-10T13:44:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>bug_tracking</title>
        <link>https://oar.imag.fr/wiki:bug_tracking?rev=1418219099&amp;do=diff</link>
        <description>Using github bugtracker

	*  &lt;http://code.tutsplus.com/articles/team-collaboration-with-github--net-29876&gt;</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:coreos?rev=1393593403&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-28T13:16:43+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>coreos</title>
        <link>https://oar.imag.fr/wiki:coreos?rev=1393593403&amp;do=diff</link>
        <description>CoreOS

Site du projet: &lt;https://coreos.com/&gt;

Un projet de gestion déploiement de serveur qui utilise systemd, docker,
etcd (un outils de partage de configuration basé sur le protocole Raft)
et un outils au dessus fleet comme system d&#039;init distribué.

C&#039;est très léger et plutôt intelligent. Si vous voulez tester il y a
tout ce qu&#039;il faut ici:</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:coupling_oarsh_with_gnu_parallel_to_mimic_salloc_srun?rev=1587044734&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-04-16T13:45:34+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>coupling_oarsh_with_gnu_parallel_to_mimic_salloc_srun</title>
        <link>https://oar.imag.fr/wiki:coupling_oarsh_with_gnu_parallel_to_mimic_salloc_srun?rev=1587044734&amp;do=diff</link>
        <description>Demonstration of the use of GNU parallel with oarsh, so that a user can execute batch (parallel) jobs using subsets of the resources allocated to a bigger (OAR) job. 

E.g. 1 batch per core (or gpu), in a job which has many nodes/cores/gpus allocated.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:criu?rev=1553618992&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-03-26T16:49:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>criu</title>
        <link>https://oar.imag.fr/wiki:criu?rev=1553618992&amp;do=diff</link>
        <description>Some work is in progress for the setup of a mechanism to allow system level checkpointing of applications using CRIU.

See:
&lt;https://github.com/oar-team/oar/tree/2.5/misc/checkpointing/criu&gt;</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:custom_admission_rules?rev=1585146497&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-25T14:28:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>custom_admission_rules</title>
        <link>https://oar.imag.fr/wiki:custom_admission_rules?rev=1585146497&amp;do=diff</link>
        <description>Admission rules

OAR offers a powerful system letting you customize the way that jobs enter into queues (or are rejected from queues) called “admission rules”. An admission rule is a little perl script that you insert into the admission_rules SQL table of the OAR database. Here, you&#039;ll find some advanced and useful examples.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:customization_tips?rev=1585146276&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-25T14:24:36+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>customization_tips</title>
        <link>https://oar.imag.fr/wiki:customization_tips?rev=1585146276&amp;do=diff</link>
        <description>Configuration

In this section, you&#039;ll find advanced configuration tips

Priority to the nodes with the lower workload

This tip is useful for clusters of big nodes, like NUMA hosts with numerous cpus and a few nodes. When the cluster has a lot of free resources, users often wonder why their jobs are always sent to the first node while the others are completely free. With this simple trick, new jobs are sent preferably on the nodes that have the lowest 15 minutes workload.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:database_slow_queries?rev=1436113921&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-07-05T16:32:01+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>database_slow_queries</title>
        <link>https://oar.imag.fr/wiki:database_slow_queries?rev=1436113921&amp;do=diff</link>
        <description>*  &lt;https://wiki.postgresql.org/wiki/Slow_Query_Questions&gt;
	*  &lt;https://wiki.postgresql.org/wiki/Logging_Difficult_Queries&gt;
	*  Analysers:
		*  &lt;https://github.com/WoLpH/pg_query_analyser&gt;
		*  pgbadger (debian pkg) -&gt; couldn&#039;t make work
		*  pgfouine (debian pkg) -&gt; couldn&#039;t make work
		*  &lt;http://explain.depesz.com/&gt;</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:debian_packaging?rev=1740659934&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-27T12:38:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>debian_packaging</title>
        <link>https://oar.imag.fr/wiki:debian_packaging?rev=1740659934&amp;do=diff</link>
        <description>Back to releasing

Debian packaging

Prepare your packaging environment

See:

	*  dput setup
	*  sbuild-debian
	*  aptly setup

Build for sid

Import origin tarball

With uscan

If tarball is published, use uscan:


git checkout debian/2.5
# Workaround for bugs in gbp/uscan ($USCAN_DESTDIR not considered and no way to pass uscan options to the gpb import-orig --uscan the command line):
uscan --no-conf -ddd --destdir=../tarballs/
gbp import-orig $(ls ../tarballs/oar_*.orig.tar.gz | tail -n1)</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:dedicated_command_for_queue_management?rev=1392488409&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-15T18:20:09+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dedicated_command_for_queue_management</title>
        <link>https://oar.imag.fr/wiki:dedicated_command_for_queue_management?rev=1392488409&amp;do=diff</link>
        <description>Provide a dedicated command, instead of oarnotify, and allow modifying queue instead of requiring remove+add.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:developing_admission_rules?rev=1584986827&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-23T18:07:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developing_admission_rules</title>
        <link>https://oar.imag.fr/wiki:developing_admission_rules?rev=1584986827&amp;do=diff</link>
        <description>Developing admission rules

The admission rules are executed within the add_micheline_job function of OAR&#039;s IO lib. See &lt;https://github.com/oar-team/oar/blob/2.5/sources/core/common-libs/lib/OAR/IO.pm#L1507&gt;.

The following perl variables can be used in admission rules:

	*  $jobType
	*  $ref_resource_list
	*  $command
	*  $infoType
	*</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:disk_reservation?rev=1480700039&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-12-02T17:33:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>disk_reservation</title>
        <link>https://oar.imag.fr/wiki:disk_reservation?rev=1480700039&amp;do=diff</link>
        <description>This page describes a proof of concept to use OAR to couple “cpu” resources with some “disk” resources.
E.g. Each node has “cpus” and “disks”, we want to allow users to create jobs to reserve disks for a long period, and eventually request smaller compute jobs on resources on which those disks are reserved.
This would give users the capability of keeping data on disk for a longer time than the compute time, e.g. a more persistent storage for data.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:document_the_migration_from_an_existing_mysql_database_to_postgresql?rev=1392738936&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-18T15:55:36+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>document_the_migration_from_an_existing_mysql_database_to_postgresql</title>
        <link>https://oar.imag.fr/wiki:document_the_migration_from_an_existing_mysql_database_to_postgresql?rev=1392738936&amp;do=diff</link>
        <description>Page a creer: Migration from a Mysql to a PostgreSQL database

Voir avec Pascal, migration effectuée sur Igrida.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:documentation?rev=1393587677&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-28T11:41:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>documentation</title>
        <link>https://oar.imag.fr/wiki:documentation?rev=1393587677&amp;do=diff</link>
        <description>Sphinx

	*  &lt;http://sphinx-doc.org/&gt;

1ers essais:

html : &lt;http://miyuki.quicker.fr/html/&gt;

autres thèmes :
&lt;http://miyuki.quicker.fr/theme2/&gt;
&lt;http://miyuki.quicker.fr/theme3/&gt;
&lt;http://miyuki.quicker.fr/theme4/&gt;
&lt;http://miyuki.quicker.fr/theme5/&gt;
&lt;http://miyuki.quicker.fr/theme6/&gt;
&lt;http://miyuki.quicker.fr/theme7/&gt;
&lt;http://miyuki.quicker.fr/theme8/&gt;

Man : &lt;http://miyuki.quicker.fr/man/oar.1&gt;

Epub : &lt;http://miyuki.quicker.fr/epub/&gt;

PDF : &lt;http://miyuki.quicker.fr/latex/OAR.pdf&gt;</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:dokuwiki?rev=1748266447&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-05-26T13:34:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dokuwiki</title>
        <link>https://oar.imag.fr/wiki:dokuwiki?rev=1748266447&amp;do=diff</link>
        <description>DokuWiki

wiki:dokuwiki DokuWiki is a simple to use and highly versatile Open Source wiki software that doesn&#039;t require a database. It is loved by users for its clean and readable syntax. The ease of maintenance, backup and integration makes it an administrator&#039;s favorite. Built in</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:dput_setup?rev=1617197563&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-03-31T13:32:43+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dput_setup</title>
        <link>https://oar.imag.fr/wiki:dput_setup?rev=1617197563&amp;do=diff</link>
        <description>Obviously, we do not want to push to Debian&#039;s FTP.

We push to oar-ftp using scp.

oar-ftp is behind the LIG&#039;s firewall so having a LIG account is required.

Also, access to the ftpmaster account must be enable (your SSH key must be added to the ftpmaster account).</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:editors?rev=1393587716&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-28T11:41:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>editors</title>
        <link>https://oar.imag.fr/wiki:editors?rev=1393587716&amp;do=diff</link>
        <description>Sublime Text

	*  &lt;http://www.sublimetext.com/&gt;

atom.io

	*  &lt;http://atom.io&gt;</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:enable_to_mix_timesharing_modes?rev=1456925201&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-03-02T13:26:41+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>enable_to_mix_timesharing_modes</title>
        <link>https://oar.imag.fr/wiki:enable_to_mix_timesharing_modes?rev=1456925201&amp;do=diff</link>
        <description>Idea

The idea here is to allow someone that runs a “timesharing=*,*” job, to run a new job on the resource but with the more restrictive specification: “timesharing=user,*”, if no “timesharing=*,*” jobs are running from other users.

With the semantic of the Digitalis platform where:</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:example_of_setup_with_oar_energy_saving_mechanism?rev=1460115779&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-04-08T11:42:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>example_of_setup_with_oar_energy_saving_mechanism</title>
        <link>https://oar.imag.fr/wiki:example_of_setup_with_oar_energy_saving_mechanism?rev=1460115779&amp;do=diff</link>
        <description>FAQ

Hubot does nothing because wake-up is already in progress, but it is actually not

Q: I get in the logs:
 [...] [Hulot] Wanted to wake up node to satisfy &#039;property&#039; keepalive, but a command is already running on this node. So doing nothing and waiting for the next cycles to converge.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:fix_for_database_schema_version_2.5.0?rev=1414780535&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-10-31T18:35:35+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>fix_for_database_schema_version_2.5.0</title>
        <link>https://oar.imag.fr/wiki:fix_for_database_schema_version_2.5.0?rev=1414780535&amp;do=diff</link>
        <description>This fix applies to OAR 2.5.2 and OAR 2.5.3, and must be taken into account if upgrading to any later version of OAR (i.e. starting from OAR 2.5.4)

Description of the issue

With OAR 2.5.2 and OAR 2.5.3, OAR&#039;s database schema version must be 2.5.2 but is actually 2.5.0 in case of a fresh database setup with oar-database.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:froggy_job_resource_manager_ht?rev=1436084598&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-07-05T08:23:18+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>froggy_job_resource_manager_ht</title>
        <link>https://oar.imag.fr/wiki:froggy_job_resource_manager_ht?rev=1436084598&amp;do=diff</link>
        <description>--- /etc/oar/job_resource_manager_cgroups_memory.pl	2013-06-03 15:55:30.282952914 +0200
+++ /etc/oar/job_resource_manager_cgroups_memory_ht.pl	2014-07-07 14:36:44.730720175 +0200
@@ -32,6 +32,8 @@
 my $Old_umask = sprintf(&quot;%lo&quot;,umask());
 umask(oct(&quot;022&quot;));
 
+my $hyperthreading_type = &quot;ht&quot;;
+
 my $Cgroup_mount_point = &quot;/dev/oar_cgroups&quot;;
 my $Cpuset;
 my $Log_level;
@@ -191,6 +193,16 @@
             exit_myself(5,&quot;Failed to create and feed the cpuset $Cpuset_path_job&quot;);
         }
 
+        # …</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:green_computing?rev=1585145971&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-25T14:19:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>green_computing</title>
        <link>https://oar.imag.fr/wiki:green_computing?rev=1585145971&amp;do=diff</link>
        <description>Green computing

In this page, you&#039;ll find tips for optimizing the fluids consumptions of your clusters

Warning: this tip is now partly obsoleted by the new hulot module that comes with the latest oar release. this energy saving module has got a keepalive feature. take a look at the comments above all the energy* variables into the oar.conf file.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:gvirt?rev=1584621499&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-19T12:38:19+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>gvirt</title>
        <link>https://oar.imag.fr/wiki:gvirt?rev=1584621499&amp;do=diff</link>
        <description>Gvirt is a tool developed for the Igrida and Grid&#039;5000 platform at Inria.

It interfaces OAR jobs with VMs.

&lt;https://gitlab.inria.fr/igrida/gvirt&gt;

Documentation is a work in progress.

Any contribution to make it usable for other platforms would be very welcomed.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:handle_systemd_api_for_managing_oar_cgroups?rev=1407418351&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-08-07T13:32:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>handle_systemd_api_for_managing_oar_cgroups</title>
        <link>https://oar.imag.fr/wiki:handle_systemd_api_for_managing_oar_cgroups?rev=1407418351&amp;do=diff</link>
        <description>Apparently there are some works in progress to change the CGROUPS API in the kernel.

Accordingly to

&lt;http://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/&gt;

they want to allow only 1 process to become a CGROUPS manager.

So systemd is a good candidate.
In this case we have to find a way to use the systemd CGROUPS</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:how_i_work_with_oar-docker?rev=1434054257&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-06-11T20:24:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>how_i_work_with_oar-docker</title>
        <link>https://oar.imag.fr/wiki:how_i_work_with_oar-docker?rev=1434054257&amp;do=diff</link>
        <description>How I work with oar-docker

(see also oar-docker)

I&#039;m currently using Debian 8 (jessie) as my operating system, and since I do not like to install python packages in my system outside of Debian packaging, I use the --user option of pip.

But first I need to install pip from Debian</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:how_to_handle_a_bigger_and_bigger_oar_database?rev=1467226491&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-06-29T18:54:51+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>how_to_handle_a_bigger_and_bigger_oar_database</title>
        <link>https://oar.imag.fr/wiki:how_to_handle_a_bigger_and_bigger_oar_database?rev=1467226491&amp;do=diff</link>
        <description>Serveral installations of OAR are known to have reached more than several millions of jobs. With the corresponding size of the OAR database, some problems may arise, first of all depending on the sizing of the database server in use.

The main CIMENT cluster for instance (froggy) currently runs jobs with id &gt; 11.000.000, with not known issues. CIMENT uses a PostreSQL database with a dedicated server (not a VM) with the follwing hardware specs:</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:implement_quotas_based_on_cpu-time_into_the_scheduler?rev=1407172037&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-08-04T17:07:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>implement_quotas_based_on_cpu-time_into_the_scheduler</title>
        <link>https://oar.imag.fr/wiki:implement_quotas_based_on_cpu-time_into_the_scheduler?rev=1407172037&amp;do=diff</link>
        <description>Proposition (CIMENT)

For a given project (or user), the jobs currently running in the system should not exceed a certain amount of cpu-time Q(project). 

The current cpu-time of a project T(project) is defined as the sum of all remaining cpu-times of the running jobs of a project (number_of_resources*remaining_walltime).</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:job_event_notifications?rev=1458776302&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-03-23T23:38:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>job_event_notifications</title>
        <link>https://oar.imag.fr/wiki:job_event_notifications?rev=1458776302&amp;do=diff</link>
        <description>oarsub notification option

The oarsub command provides an option to send notifications of job events.

Quoting oarsub manual page, the --notify option works as follows: 


       --notify &lt;TXT&gt;
           Specify a notification method (mail or command to execute).  Ex:
            --notify &quot;mail:name@domain.com&quot;
            --notify &quot;exec:/path/to/script args&quot;

           args are job_id,job_name,TAG,comment

           TAG can be:
             - RUNNING : when the job is launched
             …</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:job_scheduling_constraints?rev=1456926116&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-03-02T13:41:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>job_scheduling_constraints</title>
        <link>https://oar.imag.fr/wiki:job_scheduling_constraints?rev=1456926116&amp;do=diff</link>
        <description>Allow to force jobs to be scheduled only during night for instance.

Quick description

Je viens de pousser le branche de travail: 2.5-sched-constraints:

J&#039;ai pas mal retravaillé le oar_meta_sched et le scheduler de base:
oar_sched_timesharing_and_placeholder, ainsi que la lib GanttHoleStorage.pm.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:job_types?rev=1539616821&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-10-15T15:20:21+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>job_types</title>
        <link>https://oar.imag.fr/wiki:job_types?rev=1539616821&amp;do=diff</link>
        <description>This page aims at gathering information about the different job types (might be renamed job tags someday...), as passed to oarsub using the -t option.

Some job types have effects on the job execution mechanisms, some on the job scheduling, some (user defined) can be abstract/virtual, or only have effect outsite of OAR (e.g. in the prologue/epilogue scripts set by the administrator).
Job types control is managed by the admission rule. The 15th admission rule handle the syntax checking of the acc…</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:linux_cgroup_sysfs_and_other_sysctl?rev=1430419489&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-04-30T18:44:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>linux_cgroup_sysfs_and_other_sysctl</title>
        <link>https://oar.imag.fr/wiki:linux_cgroup_sysfs_and_other_sysctl?rev=1430419489&amp;do=diff</link>
        <description>*  &lt;http://0pointer.net/blog/projects/cgroups-vs-cgroups.html&gt;
	*  &lt;http://0pointer.net/blog/projects/systemd-for-admins-2.html&gt;</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:managing_resources_cpu_gpu?rev=1583241004&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-03T13:10:04+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>managing_resources_cpu_gpu</title>
        <link>https://oar.imag.fr/wiki:managing_resources_cpu_gpu?rev=1583241004&amp;do=diff</link>
        <description>This page presents some internals of OAR&#039;s management of resources, in order to give administrators some useful knowledge and help creating relevant definitions of the resources with regards to CPUs-cores topologies as well as CPUs-GPUs.

Managing processing unit topologies</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:migrate_runner_module_into_almighty_bipbip_handler_processus?rev=1395570956&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-03-23T10:35:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>migrate_runner_module_into_almighty_bipbip_handler_processus</title>
        <link>https://oar.imag.fr/wiki:migrate_runner_module_into_almighty_bipbip_handler_processus?rev=1395570956&amp;do=diff</link>
        <description>The goals are:

	*  let the bipbip handler processus in Almighty to manage the launch of bipbip (for starting jobs). This will handle the window launch of processes as when the jobs are finishing. I think it is the right place.
	*  make the starting jobs asynchronous. So when the scheduler decides that a job can be launched it is launched in background without waiting the end of the scheduler (can be &gt; 30s).</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:migration_from_a_mysql_to_a_postgresql_database?rev=1443021088&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-09-23T15:11:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>migration_from_a_mysql_to_a_postgresql_database</title>
        <link>https://oar.imag.fr/wiki:migration_from_a_mysql_to_a_postgresql_database?rev=1443021088&amp;do=diff</link>
        <description>Migrating a OAR database from MySQL to PostgreSQL

The Migrating a OAR database from MySQL to PostgreSQL is not straight-forward. A Tool like mysql2psql does not do the trick by itself.

New procedure

A tool has been developed to help migrating from a mysql to a postgresql OAR database: oar-database-migrate.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:multi-cluster_with_priority?rev=1613064087&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-02-11T17:21:27+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>multi-cluster_with_priority</title>
        <link>https://oar.imag.fr/wiki:multi-cluster_with_priority?rev=1613064087&amp;do=diff</link>
        <description>For a OAR setup with different set of nodes (i.e. different homogeneous clusters) in the resources, you might want to give different priorities to nodes, so that
some nodes are used in priority compared to others.

For that purpose, you can use the scheduler_priority property of the nodes (setting it using the oarnodesetting command), which will be taken into account as specified per the
SCHEDULER_RESOURCE_ORDER configuration setting in oar.conf.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:nix?rev=1399981889&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-05-13T11:51:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>nix</title>
        <link>https://oar.imag.fr/wiki:nix?rev=1399981889&amp;do=diff</link>
        <description>Nix

Nix is a purely functional package manager. This means that it treats packages like values in purely functional programming languages such as Haskell — they are built by functions that don’t have side-effects, and they never change after they have been built.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:nonexisting?rev=1373448888&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-07-10T09:34:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>nonexisting</title>
        <link>https://oar.imag.fr/wiki:nonexisting?rev=1373448888&amp;do=diff</link>
        <description>This page does not exist.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:oar_drmaa_interface?rev=1442432859&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-09-16T19:47:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>oar_drmaa_interface</title>
        <link>https://oar.imag.fr/wiki:oar_drmaa_interface?rev=1442432859&amp;do=diff</link>
        <description>One can find a DRMAA interface for OAR with the project hosted at &lt;https://github.com/oar-team/oar-drmaa-v1&gt;.

See &lt;https://github.com/oar-team/oar-drmaa-v1/blob/master/doc_drmaa1.rst&gt;.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:oar_skylight?rev=1487771715&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-02-22T13:55:15+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>oar_skylight</title>
        <link>https://oar.imag.fr/wiki:oar_skylight?rev=1487771715&amp;do=diff</link>
        <description>Devel environment Install

	*  Install oar-docker (follow oar3_dev_with_oar_docker)
	*  Start and connect on frontend:


oardocker start -n 2 -v ~/git/oar-skylight/:/home/docker/oar-skylight
oardocker connect frontend



sudo apt-get update
# repeat if warnings occur
sudo apt-get install -t testing libc-ares2 libssl1.0-dev
sudo apt-get install -t experimental nodejs nodejs-dev
sudo apt-get install npm
sudo ln -s /usr/bin/nodejs /usr/local/bin/node</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:oar-docker-admin?rev=1488817468&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-03-06T16:24:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>oar-docker-admin</title>
        <link>https://oar.imag.fr/wiki:oar-docker-admin?rev=1488817468&amp;do=diff</link>
        <description>Procédure de mise à jour des images oardocker sur le Docker Hub

Mettre à jour l&#039;image de debian

L&#039;image utilisée est debian stable avec quelques paquets qui viennent de testing il me semble (nginx/apache/systemd ?).

Pour mettre à jour cette image :</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:oar-docker?rev=1585662217&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-31T13:43:37+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>oar-docker</title>
        <link>https://oar.imag.fr/wiki:oar-docker?rev=1585662217&amp;do=diff</link>
        <description>Build your own OAR cluster with docker

OAR-docker is a tool to setup a cluster of docker containers emulating a OAR cluster, with a frontend, a server, and possibly many nodes.

OAR-docker is the perfect tool for testing OAR developments. It also allows prototyping the use of other tools on top of OAR.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:oar-vagrant?rev=1712758812&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-10T14:20:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>oar-vagrant</title>
        <link>https://oar.imag.fr/wiki:oar-vagrant?rev=1712758812&amp;do=diff</link>
        <description>Overview

The oar-vagrant project aims at using Vagrant to test the different flavors of installation of OAR.

For now, you can test the installation of OAR&#039;s packages (rpm, dev) on VMs running Centos 6, Centos 7, Debian 7 (wheezy) and Debian 8 (jessie), with mysql or postgresql as the database backend.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:oar3_dev_with_oar_docker?rev=1486117217&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-02-03T10:20:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>oar3_dev_with_oar_docker</title>
        <link>https://oar.imag.fr/wiki:oar3_dev_with_oar_docker?rev=1486117217&amp;do=diff</link>
        <description>Initialisation d&#039;un environnement de dev OAR3

Nettoyage de l&#039;environnement docker


 docker rm $(docker ps -a -q|head -n1)
 docker rm $(docker ps -a -q|head -n1)
 ...
 docker images |awk &#039;{print &quot;docker rmi &quot; $3}&#039; |bash
 rm -rf .oardocker


Creation/chargement virtualenv</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:oardocker_setup_for_grid_5000?rev=1585662134&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-31T13:42:14+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>oardocker_setup_for_grid_5000</title>
        <link>https://oar.imag.fr/wiki:oardocker_setup_for_grid_5000?rev=1585662134&amp;do=diff</link>
        <description>Emulating a Grid&#039;5000 OAR setup

This setup fakes the boot stages (post-deploy or standby) with at commands.

It uses oar-docker.

On the host

Start the oar-docker cluster from within a oar git clone.

	*  cd .../oar
	*  oardocker -v$PWD:/mnt -n 20

On the frontend container</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:oarstat_vs_rest_api?rev=1481575216&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-12-12T20:40:16+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>oarstat_vs_rest_api</title>
        <link>https://oar.imag.fr/wiki:oarstat_vs_rest_api?rev=1481575216&amp;do=diff</link>
        <description>OAR 2.5.7

oarstat

WAITING/job batch

oarstat -fj:


assigned_resources=
assigned_hostnames=


	*  no information on scheduled resources

oarstat -pj: empty

WAITING/reservation a l&#039;avance

oarstat -fj:


assigned_resources=
assigned_hostnames=
reserved_resources=1+2</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:oarwalltime?rev=1582028267&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-02-18T12:17:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>oarwalltime</title>
        <link>https://oar.imag.fr/wiki:oarwalltime?rev=1582028267&amp;do=diff</link>
        <description>oarextratime

Coming with OAR 2.5.8, oarwalltime is a new OAR command.

This page talk about oarextratime, which was the former name for oarwalltime. 

One could just exchange the two words.

Usage


$ oarextratime 
Usage:
  /usr/local/lib/oar/oarextratime [&lt;options&gt;] &lt;job_id&gt; [&lt;extra_time&gt;]

Manage extra time requests for a job.
- If extra time is given, the command requests the addition of some extra time
  to the job or update a previous request.
- If no extra time is given, the command shows…</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:pagename?rev=1373448867&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-07-10T09:34:27+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>pagename</title>
        <link>https://oar.imag.fr/wiki:pagename?rev=1373448867&amp;do=diff</link>
        <description>Replace pagename by the name of the page you want !</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:passing_environment_variables_to_openmpi_nodes?rev=1706640298&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-01-30T18:44:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>passing_environment_variables_to_openmpi_nodes</title>
        <link>https://oar.imag.fr/wiki:passing_environment_variables_to_openmpi_nodes?rev=1706640298&amp;do=diff</link>
        <description>Passing environment variables to nodes

While some batch schedulers (e.g. Slurm) do some tricks to transparently pass some environment variables from the head node shell to all execution nodes given to mpirun, OAR does not (OAR provides no more than what OpenSSH does, be it used directly as</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:processors?rev=1393518958&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-27T16:35:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>processors</title>
        <link>https://oar.imag.fr/wiki:processors?rev=1393518958&amp;do=diff</link>
        <description>This page aims at listing resources regarding processors (Intel, AMD, ...) and discussing enhancement for the ways of handling them in OAR...

	*  &lt;http://en.wikipedia.org/wiki/List_of_Intel_Xeon_microprocessors&gt;
	*  &lt;http://ark.intel.com&gt;
	*  &lt;http://en.wikipedia.org/wiki/Intel_Turbo_Boost&gt;
	*  &lt;http://www.qdpma.com/systemarchitecture/systemarchitecture_qpi.html&gt;
	*  &lt;http://www.hardwaresecrets.com/article/Inside-the-Intel-Sandy-Bridge-Microarchitecture/1161&gt;</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:publication_of_the_documentation?rev=1455607784&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-02-16T07:29:44+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>publication_of_the_documentation</title>
        <link>https://oar.imag.fr/wiki:publication_of_the_documentation?rev=1455607784&amp;do=diff</link>
        <description>Publishing

To publish the documentation, run from OAR git:


$ make -C docs publish


If you don&#039;t want to publish using the the default DOC_TARGET (docmaster@oar.lig), set it as follows:


$ make -C docs DOC_TARGET=my_user@my_host publish


If you want to push to a specific version, set the DOC_VERSION:</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:releasing?rev=1445879891&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-10-26T17:18:11+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>releasing</title>
        <link>https://oar.imag.fr/wiki:releasing?rev=1445879891&amp;do=diff</link>
        <description>This page describes the procedure to release a new version of OAR. This procedure applies to OAR version &gt; 2.5.2

Releasing is 3 folds:

	*  create the tarball for the release
	*  create the new Debian packages
	*  create the new RPM packages

New Debian and/or RPM packages can also be created for an existing tarball release, to correct packaging bugs (hence, skipping step 1).</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:rename_oar_modules?rev=1432650819&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-05-26T14:33:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>rename_oar_modules</title>
        <link>https://oar.imag.fr/wiki:rename_oar_modules?rev=1432650819&amp;do=diff</link>
        <description>Plan is to rename OAR module to less fancy names, e.g. oar_...

We hope to only need some `sed&#039; commands.

Almighty

	*  oarserver (-&gt; already used as the wrapper script) 

bipbip

	*  oarrunner
	*  oarlauncher
	*  (the runner module: does not exist anymore)</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:reprepro?rev=1414623462&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-10-29T22:57:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>reprepro</title>
        <link>https://oar.imag.fr/wiki:reprepro?rev=1414623462&amp;do=diff</link>
        <description>The goal of this page is to provide useful information for installing and managing OAR&#039;s reprepro Debian repository

Installation

TBC

Basic commands

TBC

Snapshoting

Before copying some package version from one distribution (e.g. sid-unstable) to another (e.g. sid), it might be wise to generate a snaptshot, so that one can still configure a sources.list file providing access to an earlier version of OAR&#039;s packages.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:rest-api-specs?rev=1478470605&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-11-06T22:16:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>rest-api-specs</title>
        <link>https://oar.imag.fr/wiki:rest-api-specs?rev=1478470605&amp;do=diff</link>
        <description>OAR 2 Perl REST API

Jobs

	*  GET ^/version\.*(yaml|json|html)*$
	*  GET ^/whoami\.*(yaml|json|html)*$
	*  GET ^/timezone\.*(yaml|json|html)*$
	*  GET ^/jobs(/details|/table)*\.*(yaml|json|html)*$
	*  GET ^/jobs/(\d+)(/details)*(\.yaml|\.json|\.html)*$</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:rpm_packaging?rev=1611325600&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-01-22T14:26:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>rpm_packaging</title>
        <link>https://oar.imag.fr/wiki:rpm_packaging?rev=1611325600&amp;do=diff</link>
        <description>Back to releasing

RPM packaging

Adapt the spec file

Make sure to update the version (top of the file) and the changelog (bottom of the file) at least.


workstation$ git checkout centos7/2.5
workstation$ git pull --rebase
workstation$ vi rpm/SPECS/oar.spec
workstation$ git add rpm/SPECS/oar.spec &amp;&amp; git commit</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:running_the_api_tests?rev=1498834149&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-06-30T14:49:09+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>running_the_api_tests</title>
        <link>https://oar.imag.fr/wiki:running_the_api_tests?rev=1498834149&amp;do=diff</link>
        <description>Manual testing with oardocker

Set user:


APIUSER=docker:docker


or to get access to privileged commands


APIUSER=oar:oar


Then set the URL API:

	*  from outside oardocker containers


OARAPI=http://$APIUSER@localhost:46668/oarapi-priv


	*  from inside the oardocker frontend container</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:sbuild-debian?rev=1601299825&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-09-28T13:30:25+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>sbuild-debian</title>
        <link>https://oar.imag.fr/wiki:sbuild-debian?rev=1601299825&amp;do=diff</link>
        <description>This setup was guided by the following page:

&lt;http://wiki.debian.org/sbuild?rev=19&gt;

(Since then, that Debian wiki page evolved, update my be need on our side...)

Install sbuild + initial setup


apt-get install sbuild

user=neyron

sbuild-adduser $user

# this needs &quot;entropy&quot;... Do weird things and think different, waiting for it to complete...
sbuild-update --keygen

# share the deb archives among schroots...
echo /var/cache/apt/archives /var/cache/apt/archives none rw,bind 0 0 &gt;&gt;/etc/schroo…</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:schroot-centos?rev=1373359928&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-07-09T08:52:08+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>schroot-centos</title>
        <link>https://oar.imag.fr/wiki:schroot-centos?rev=1373359928&amp;do=diff</link>
        <description>Setup a CentOS schroot on Debian

Inspired by the setup of Debian chroot for sbuild:

	*  &lt;http://wiki.debian.org/sbuild?rev=19&gt;
	*  &lt;http://wiki.debian.org/mk-sbuild&gt;


$ apt-get install schroot sbuild btrfs-tools


We will use the btrfs flavor of schroot.

Since btrfs is still experimental, I choose to create loopback device formated with btrfs and mounted as follows:</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:setup_a_oar_cluster_on_a_single_machine?rev=1395775802&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-03-25T19:30:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>setup_a_oar_cluster_on_a_single_machine</title>
        <link>https://oar.imag.fr/wiki:setup_a_oar_cluster_on_a_single_machine?rev=1395775802&amp;do=diff</link>
        <description>Setup the machine

We setup a VM with a basic installation of Debian Stable (Wheezy).

We call the VM “oar” and setup root&#039;s ssh keys.

Create OAR tarball and push it to the VM


neyron@takelma:~$ cd scm/OAR/oar
neyron@takelma:~/scm/OAR/oar (2.5 $=)$ git pull --rebase
Current branch 2.5 is up to date.
neyron@takelma:~/scm/OAR/oar (2.5 $=)$ make tarball
./misc/make_tarball
Using the Git repository &#039;/home/neyron/scm/OAR/oar&#039;
Using the Git tree-ish   &#039;2.5&#039;
../tarballs/oar-2.5.3+94.g6396d49.tar.gz
n…</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:some_examples_of_admission_rules?rev=1586289689&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-04-07T20:01:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>some_examples_of_admission_rules</title>
        <link>https://oar.imag.fr/wiki:some_examples_of_admission_rules?rev=1586289689&amp;do=diff</link>
        <description>Admission rules are managed with the oaradmissionrule command. See the usage or man page of the command.

The code of the admission rules is executed within oarsub at submission time.
Many internal variables are available, making the mechanism very powerful</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:source_control?rev=1393587511&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-28T11:38:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>source_control</title>
        <link>https://oar.imag.fr/wiki:source_control?rev=1393587511&amp;do=diff</link>
        <description>Git

	*  &lt;http://nvie.com/posts/a-successful-git-branching-model/&gt;
	*  &lt;https://sandofsky.com/blog/git-workflow.html&gt;
	*  &lt;http://yakiloo.com/getting-started-git-flow/&gt;
	*  &lt;https://wiki.debian.org/PackagingWithGit&gt;
	*  &lt;http://www.eyrie.org/~eagle/notes/debian/git.html&gt;

GitHub

	*  &lt;http://code.tutsplus.com/articles/team-collaboration-with-github--net-29876&gt;</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:start?rev=1584985427&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-23T17:43:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>start</title>
        <link>https://oar.imag.fr/wiki:start?rev=1584985427&amp;do=diff</link>
        <description>This wiki section is open to contributions from anyone (regular users, developers, ...) who&#039;s registered a login account.

Developer&#039;s head pages

OAR&#039;s Github page: &lt;https://github.com/oar-team/oar&gt;

	*  Todos
	*  Testing
	*  Releasing
	*  Oar-docker-admin
	*  Technology watch
	*  Job types

Restricted area

The wiki restricted area is only accessible to the core team members.

Old wiki content</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:syntax?rev=1748266447&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-05-26T13:34:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>syntax</title>
        <link>https://oar.imag.fr/wiki:syntax?rev=1748266447&amp;do=diff</link>
        <description>Formatting Syntax

DokuWiki supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:systemd_for_administrators?rev=1415021123&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-11-03T13:25:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>systemd_for_administrators</title>
        <link>https://oar.imag.fr/wiki:systemd_for_administrators?rev=1415021123&amp;do=diff</link>
        <description>*  &lt;http://0pointer.de/blog/projects/systemd-for-admins-1.html&gt;
	*  &lt;http://0pointer.de/blog/projects/systemd-for-admins-2.html&gt;
	*  &lt;http://0pointer.de/blog/projects/systemd-for-admins-3.html&gt;
	*  &lt;http://0pointer.de/blog/projects/systemd-for-admins-4.html&gt;
	*  &lt;http://0pointer.de/blog/projects/three-levels-of-off&gt;
	*  &lt;http://0pointer.de/blog/projects/changing-roots.html&gt;
	*  &lt;http://0pointer.de/blog/projects/blame-game.html&gt;
	*  &lt;http://0pointer.de/blog/projects/the-new-configuration-files&gt;
	…</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:tarball_release?rev=1455574830&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-02-15T22:20:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>tarball_release</title>
        <link>https://oar.imag.fr/wiki:tarball_release?rev=1455574830&amp;do=diff</link>
        <description>This page describe how new release tarball are created from the Git repository. Please have a look at the releasing for the overall process. 

If one only wants to publish a snapshot tarball, one can skip the first step, and use the snapshot branch on the archive server.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:technology_watch?rev=1484820367&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-01-19T10:06:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>technology_watch</title>
        <link>https://oar.imag.fr/wiki:technology_watch?rev=1484820367&amp;do=diff</link>
        <description>This page aims a listing new technologies we are watching for possible later (or current) use in OAR or OAR ecosystem.

Sub-pages should provide:

	*  quick description applied to our ecosystem
	*  bookmarks, URLs
	*  any example
	*  anything else
	*</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:testing?rev=1531912714&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-07-18T11:18:34+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>testing</title>
        <link>https://oar.imag.fr/wiki:testing?rev=1531912714&amp;do=diff</link>
        <description>Several subprojects aim at providing environments to test OAR:

	*  OAR-Docker -&gt; for OAR developers, or advanced users (see also how_i_work_with_oar-docker or oar3_dev_with_oar_docker)
	*  OAR-Vagrant -&gt; for OAR packaging developers and OAR users (admins who want to test with OAR installation, users who want to test a basic cluster setup with resources and tasks managed by OAR)</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:ui_toolkit?rev=1393593133&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-28T13:12:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ui_toolkit</title>
        <link>https://oar.imag.fr/wiki:ui_toolkit?rev=1393593133&amp;do=diff</link>
        <description>Kivy

	*  External Link
	*   Kivy: a Crossplatform Framework for NUI in Pytonh</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:use_a_cache_system_in_the_scheduling_algorithms?rev=1404479518&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-07-04T13:11:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>use_a_cache_system_in_the_scheduling_algorithms</title>
        <link>https://oar.imag.fr/wiki:use_a_cache_system_in_the_scheduling_algorithms?rev=1404479518&amp;do=diff</link>
        <description>Move some gantt prediction related data from DB to  cache system (like memcached or redis)

OR

Put the volatile gantt tables in /dev/shm for example


DROP TABLESPACE IF EXISTS oarramts;
CREATE TABLESPACE oarramts LOCATION &#039;/dev/shm/oar&#039;;
CREATE UNLOGGED TABLE foo(i int) TABLESPACE oarramts;</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:use_cases_and_user_tips?rev=1627480792&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-07-28T13:59:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>use_cases_and_user_tips</title>
        <link>https://oar.imag.fr/wiki:use_cases_and_user_tips?rev=1627480792&amp;do=diff</link>
        <description>Use cases

OpenMPI + affinity

We saw that the Linux kernel seems to be incapable of using correctly all the CPUs from the cpusets.

Indeed, reserving 2 out of 8 cores on a node and running a code that uses 2
process, these 2 process where not well assigned to each cpu.
We had to give the CPU MAP to OpenMPI to do cpu_affinity:</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:useful_commands_and_administration_tasks?rev=1585145707&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-25T14:15:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>useful_commands_and_administration_tasks</title>
        <link>https://oar.imag.fr/wiki:useful_commands_and_administration_tasks?rev=1585145707&amp;do=diff</link>
        <description>Useful commands and administration tasks

Here, you&#039;ll find useful commands, sometimes a bit tricky, to put into your scripts or administration tasks

List suspected nodes without running jobs

You may need this list of nodes if you want to automatically reboot them because you don&#039;t know why they have been suspected and you think that it is a simple way to clean things:</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:using_hyperthreading_on_nodes?rev=1441380240&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-09-04T15:24:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>using_hyperthreading_on_nodes</title>
        <link>https://oar.imag.fr/wiki:using_hyperthreading_on_nodes?rev=1441380240&amp;do=diff</link>
        <description>On using (hyper)threads as the leafs of the resources tree

If HyperThreading is enabled in BIOS, using threads as the leafs of OAR (implicit) resources tree is quite simple.

Using the oar_resource_init script

The last version of the oar_resource_init</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:using_oar_on_debian_based_systems?rev=1585661384&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-31T13:29:44+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>using_oar_on_debian_based_systems</title>
        <link>https://oar.imag.fr/wiki:using_oar_on_debian_based_systems?rev=1585661384&amp;do=diff</link>
        <description>Deploying OAR on Debian based systems

OAR is packaged in Debian, see Download.

Examples

See oar-vagrant: provision scripts in the deb_debian* directories give a good overview of how to perform a basic cluster installation using OAR on a Debian system.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:using_oar_on_redhat_based_systems?rev=1585661518&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-31T13:31:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>using_oar_on_redhat_based_systems</title>
        <link>https://oar.imag.fr/wiki:using_oar_on_redhat_based_systems?rev=1585661518&amp;do=diff</link>
        <description>Deploying OAR on Redhat based systems

The Download page provides RPM packages.

They are currently out-dated, but up-to-date packages could be built from sources.

Contributions on that matter are very welcomed.

Examples

See oar-vagrant: provision scripts in the rpm_centos* directories give a good overview of how to perform a basic cluster installation using OAR on a Redhat like system.</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:web_ui?rev=1393593799&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-02-28T13:23:19+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>web_ui</title>
        <link>https://oar.imag.fr/wiki:web_ui?rev=1393593799&amp;do=diff</link>
        <description>w2ui

	*   w2ui  : a javascript UI based on Jquery
	*  &lt;http://w2ui.com/web/demos/&gt;
	*  &lt;https://github.com/vitmalina/w2ui&gt;

Web Admin-Template

	*  &lt;https://github.com/onokumus/Bootstrap-Admin-Template&gt; Bootstrap-Admin-Template</description>
    </item>
    <item rdf:about="https://oar.imag.fr/wiki:welcome?rev=1748266447&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-05-26T13:34:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>welcome</title>
        <link>https://oar.imag.fr/wiki:welcome?rev=1748266447&amp;do=diff</link>
        <description>Welcome to your new DokuWiki

Congratulations, your wiki is now up and running. Here are a few more tips to get you started.

Enjoy your work with DokuWiki,

-- the developers

Create your first pages

Your wiki needs to have a start page. As long as it doesn&#039;t exist, this link will be red:</description>
    </item>
</rdf:RDF>
