The condor package introduced new or modified debconf templates. This is often a good moment for a review to help the package maintainer following the general suggested writing style and track down typos and errors in the use of English language. A bug report has been sent against the package: 670487 If someone wants to pick up this review, please answer to this mail, in the mailing list, with an [ITR] (Intent To Review) label. The templates file is attached. To propose the file you reviewed for peer review, please send a [RFR] (Request For Review) mail with the reviewed file attached...then a few days later, when no more contributions come, a summary mail with a [LCFC] (Last Chance For Comments) label. These RFR and LCFC mails should CC the opened bug report. Finally, after no more comments coming to the LCFC mail, you can send the reviewed templates file in the bug report. Then, please notify the list with a last mail using a [BTS] label with the bug number. Helping the package maintainer to deal with induced translation updates at that moment will be nice. If you're not comfortable with that part of the process, please hand it off to a translator. --
Template: condor/title Type: title _Description: Condor configuration Template: condor/wantdebconf Type: boolean Default: false _Description: Manage initial configuration with Debconf? This package can create an appropriate initial configuration for a machine that shall join an existing Condor pool, or configure a fully functional "personal condor" installation by asking a few questions. The generated initial configuration can be further extended later on. If this configuration helper is undesired, Condor will be installed with a default configuration that needs to be customized manually. Template: condor/phonehome Type: boolean Default: false _Description: Enabled submission of usage statistics? The Condor authors kindly ask that each Condor pool sends them periodic updates with basic information about the status of the pool. Updates include only the number of total machines, the number of jobs submitted, the number of machines running jobs, the host name of the central manager, and the name of the pool. These updates help the Condor Team see how Condor is being used around the world. Template: condor/centralmanager Type: string _Description: Address of the central manager: If this machine is supposed to join an existing Condor pool, the address of the central manager machine has to be specified. Any address format supported by Condor can be used, including macro expressions. . Example: condor-manager.example.org Template: condor/daemons Type: multiselect Choices-C: SCHEDD, STARTD, COLLECTOR:NEGOTIATOR __Choices: Job submission, Job execution, Central manager __Default: Job submission, Job execution _Description: Role of this machine in the Condor pool: A machine in a Condor pool can have multiple roles. In general there is one central manager and multiple nodes that run jobs. Often the central manager is also the machine from which users submit jobs. However, it is also possible to have multiple machines available for job submission. By indicating the intended roles of this machine the Debian package will enable the corresponding daemons to be started automatically. Template: condor/admin Type: string Default: root@localhost _Description: Email address of the local Condor administrator: The condor administrator will receive error messages when something goes wrong with Condor on this machine. Template: condor/uiddomain Type: string _Description: User id domain: Condor uses this label to decide under which user account to run a particular job. If the UID domain on the submitting machine is different than the UID domain on the machine that runs your job, then Condor will automatically run the job as a user 'nobody'. If the UID domain is identical, Condor will run a job as the user that submitted the job. The UID domain needs to be a real domain name. When Condor sends e-mail about a job, it sends the e-mail to user@UID_DOMAIN. If this is left blank Condor will run all job on this machine as 'nobody'. . Any domain format supported by Condor can be used, including macro expressions. Example: $(FULL_HOSTNAME) Template: condor/filesystemdomain Type: string _Description: File system domain label: This label is an arbitrary string that is used to decide if two machines (a submitting machine and an execute machine) share the same file system. Note that if you leave this parameter blank, Condor will automatically set the value to be the fully qualified hostname of the local machine, and consequently assume that any two machines don't share a file system. In a dedicated cluster all machines will most likely use a shared file system and hence should carry the same label. . Example: my_super_computer Template: condor/personal Type: boolean Default: true _Description: Perform a "Personal Condor" installation? A personal condor installation is a fully functional Condor pool on a single machine. Condor will automatically configure and advertise as many slots as it detects CPU cores on this machine. Condor daemons will not be available through external network interfaces. . If this machine is supposed to join an existing pool or a new pool with more than one machine shall be created, a personal installation is not desired. Template: condor/reservedmemory Type: string _Description: Amount of physical memory to withhold from Condor (in MB): By default, Condor considers all the physical memory of a machine as available to be used by Condor jobs. If this value is defined, Condor subtracts it from the amount of memory it advertises as available. . Example setting to reserve 1GB: 1024 Template: condor/allowwrite Type: string _Description: Machines with write access to this host: All machines that shall participate in the Condor pool need to be listed here. This setting can be a plain list, a domain with wildcards or a macro expression. By default only the localhost is allows to access Condor daemons on this machine. . Example: *.condor-pool.example.org Template: condor/startpolicy Type: boolean Default: false _Description: Run Condor jobs regardless of other machine activity? By default Condor only starts jobs when a machine is idle, i.e. no keyboard activity or CPU load for some time. Moreover, it also suspends jobs whenever there is console activity and doesn't continue them until the machine becomes idle again. However, for a dedicated compute node or a Personal Condor installation it might be desirable to always start jobs as soon as they are submitted (given that resources are still available), and to run them continuously regardless of other activity on this machine. . If it is planned to compose a custom policy it is best to keep Condor's default here.
Source: condor
Section: science
Priority: extra
Maintainer: Condor Developers <condor-debian@cs.wisc.edu>
Uploaders: Michael Hanke <mih@debian.org>
Build-Depends: debhelper (>= 7.0.50~), po-debconf, cmake, libpq-dev,
libcurl4-openssl-dev, zlib1g-dev, libglobus-gss-assist-dev,
libglobus-gram-protocol-dev, libglobus-gram-client-dev,
libglobus-gass-server-ez-dev, libglobus-ftp-client-dev, latex2html, transfig,
libpcre3-dev, libboost-thread-dev, libboost-program-options-dev,
libboost-system-dev, libboost-regex-dev, libboost-filesystem-dev,
libexpat1-dev, libxml2-dev, libvirt-dev, zlib1g-dev, gcj-jdk | java-compiler,
libcgroup-dev (>= 0.37~), uuid-dev, chrpath, libldap2-dev | libldap-dev,
help2man, gsoap (>= 2.7.17-1~)
Standards-Version: 3.9.3
Homepage: http://research.cs.wisc.edu/condor
Vcs-Browser: http://git.debian.org/?p=pkg-exppsy/condor.git
Vcs-Git: git://git.debian.org/git/pkg-exppsy/condor.git
Package: condor
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}, ${python:Depends}, ${perl:Depends},
debconf (>= 0.5) | debconf-2.0, adduser, libdate-manip-perl,
libcgroup1 (>=0.37~)
Recommends: dmtcp
Suggests: coop-computing-tools
Description: workload management system
Like other full-featured batch systems, Condor provides a job queueing
mechanism, scheduling policy, priority scheme, resource monitoring, and
resource management. Users submit their serial or parallel jobs to Condor,
Condor places them into a queue. It chooses when and where to run the jobs
based upon a policy, carefully monitors their progress, and ultimately
informs the user upon completion.
.
Unlike more traditional batch queueing system, Condor can also effectively
harness wasted CPU power from otherwise idle desktop workstations. Condor
does not require a shared file system across machines - if no shared file
system is available, Condor can transfer the job's data files on behalf of
the user.
.
The Debian package uses Debconf to determine an appropriate initial
configuration for a machine that shall join an existing Condor pool, and
moreover, allows creating a "Personal" (single machine) Condor pool
automatically.
#Package: condor-tests
#Architecture: any
#Depends: ${misc:Depends}, ${shlibs:Depends}
#Description: test suite for Condor
# Like other full-featured batch systems, Condor provides a job queueing
# mechanism, scheduling policy, priority scheme, resource monitoring, and
# resource management. Users submit their serial or parallel jobs to Condor,
# Condor places them into a queue. It chooses when and where to run the jobs
# based upon a policy, carefully monitors their progress, and ultimately
# informs the user upon completion.
# .
# Unlike more traditional batch queueing system, Condor can also effectively
# harness wasted CPU power from otherwise idle desktop workstations. Condor
# does not require a shared file system across machines - if no shared file
# system is available, Condor can transfer the job's data files on behalf of
# the user.
# .
# This package provides Condor's test-suite that can be used to verify
# proper functioning of a Condor installation.
Package: condor-dev
Section: devel
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}
Description: development files for Condor
Like other full-featured batch systems, Condor provides a job queueing
mechanism, scheduling policy, priority scheme, resource monitoring, and
resource management. Users submit their serial or parallel jobs to Condor,
Condor places them into a queue. It chooses when and where to run the jobs
based upon a policy, carefully monitors their progress, and ultimately
informs the user upon completion.
.
Unlike more traditional batch queueing system, Condor can also effectively
harness wasted CPU power from otherwise idle desktop workstations. Condor
does not require a shared file system across machines - if no shared file
system is available, Condor can transfer the job's data files on behalf of
the user.
.
This package provides headers and libraries for development of Condor add-ons.
Package: condor-doc
Section: doc
Architecture: all
Depends: ${misc:Depends}
Description: documentation for Condor
Like other full-featured batch systems, Condor provides a job queueing
mechanism, scheduling policy, priority scheme, resource monitoring, and
resource management. Users submit their serial or parallel jobs to Condor,
Condor places them into a queue. It chooses when and where to run the jobs
based upon a policy, carefully monitors their progress, and ultimately
informs the user upon completion.
.
Unlike more traditional batch queueing system, Condor can also effectively
harness wasted CPU power from otherwise idle desktop workstations. Condor
does not require a shared file system across machines - if no shared file
system is available, Condor can transfer the job's data files on behalf of
the user.
.
This package provides Condor's documentation in HTML and PDF format, as well
as configuration and other examples.
Package: condor-dbg
Section: debug
Architecture: any
Depends: ${misc:Depends}, condor (= ${binary:Version})
Description: debugging symbols for Condor
Like other full-featured batch systems, Condor provides a job queueing
mechanism, scheduling policy, priority scheme, resource monitoring, and
resource management. Users submit their serial or parallel jobs to Condor,
Condor places them into a queue. It chooses when and where to run the jobs
based upon a policy, carefully monitors their progress, and ultimately
informs the user upon completion.
.
Unlike more traditional batch queueing system, Condor can also effectively
harness wasted CPU power from otherwise idle desktop workstations. Condor
does not require a shared file system across machines - if no shared file
system is available, Condor can transfer the job's data files on behalf of
the user.
.
This package provides the debugging symbols for Condor.
Package: libclassad-dev
Replaces: libclassad0-dev
Conflicts: libclassad0-dev
Section: libdevel
Architecture: any
Depends: libclassad3 (= ${binary:Version}), ${misc:Depends}
Description: library for Condor's classads expression language (development)
A classad (classified ad) is a mapping from attribute names to expressions. In
the simplest cases, the expressions are simple constants (integer, floating
point, or string), thus a form of property list. Attribute expressions
can also be more complicated. There is a protocol for evaluating an attribute
expression of a classad vis a vis another ad. Two classads match if each ad has
attribute requirements that evaluate to true in the context of the other ad.
Classad matching is used by the Condor central manager to determine the
compatibility of jobs and workstations where they may be run.
.
This package provides the static library and header files.
Package: libclassad3
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: library for Condor's classads expression language
A classad (classified ad) is a mapping from attribute names to expressions. In
the simplest cases, the expressions are simple constants (integer, floating
point, or string), thus a form of property list. Attribute expressions
can also be more complicated. There is a protocol for evaluating an attribute
expression of a classad vis a vis another ad. Two classads match if each ad has
attribute requirements that evaluate to true in the context of the other ad.
Classad matching is used by the Condor central manager to determine the
compatibility of jobs and workstations where they may be run.
.
This package provides the runtime library.
Attachment:
signature.asc
Description: Digital signature