Subsections
8.3 Stable Release Series 7.6
This is a stable release series of Condor.
As usual, only bug fixes (and potentially, ports to new platforms)
will be provided in future 7.6.x releases.
New features will be added in the 7.7.x development series.
The details of each version are described below.
Version 7.6.0
Release Notes:
- Condor version 7.6.0 not yet released.
- Prior to Condor version 7.5.0, commenting out PREEN in the
default configuration file disabled condor_preen.
Starting in Condor version 7.5.0,
there was an internal default value for PREEN, so if
the configuration variable was not set in any configuration file,
condor_preen would still run.
To disable this functionality, PREEN can be explicitly set to
nothing.
New Features:
- Condor can now create and manage virtual machine instances in a
cloud service via Deltacloud. This is done via the new
deltacloud grid type in the grid universe.
See section 5.3.9 for details.
- Improved scalability of submission of cream grid type jobs.
Configuration Variable and ClassAd Attribute Additions and Changes:
- The new configuration variable DELTACLOUD_GAHP specifies
where the deltacloud_gahp binary is located. This binary is used to
manage deltacloud grid type jobs in the grid universe.
In a normal Condor installation, the value should be
$(SBIN)/deltacloud_gahp.
- Several new job ClassAd attributes have been added to support
the deltacloud grid type in the grid universe.
These attributes are taken from the submit description file:
DeltacloudUsername,
DeltacloudPasswordFile,
DeltacloudImageId,
DeltacloudRealmId,
DeltacloudHardwareProfile,
DeltacloudHardwareProfileCpu,
DeltacloudHardwareProfileMemory,
DeltacloudHardwareProfileStorage,
DeltacloudKeyname, and
DeltacloudUserData.
These attributes are set by Condor when the instance runs:
DeltacloudAvailableActions,
DeltacloudPrivateNetworkAddresses,
DeltacloudPublicNetworkAddresses.
See section 5.3.9 for details of running jobs under
Deltacloud, and see section 10
for definitions of these job ClassAd attributes.
- The configuration variable JAVA_MAXHEAP_ARGUMENT
has been removed.
This means that Java universe jobs will now run with the JVM's
default maximum heap setting,
unless specified otherwise by the administrator using the configuration
of JAVA_EXTRA_ARGUMENTS ,
or by the job via
java_vm_args in the submit description file
as described in section 2.8.
- The configuration variable TRUST_UID_DOMAIN
was set to True in the default condor_config.local
in the rpm and debian packages. This is no longer the case.
This setting will therefore use the default value False.
- The configuration variable NEGOTIATOR_INTERVAL was set
to 20 in the default condor_config.local in the rpm and
debian packages. This is no longer the case. This setting
therefore will use the default value 60.
Bugs Fixed:
- Fixed a bug in condor_dagman that caused it to fail when in recovery
mode in the face of a specific combination of node job failures with
retries.
- Fixed a bug that resulted in the spooled user log not being
fetched by condor_transfer_data. Prior to Condor version 7.5.4, this
problem affected spooled jobs submitted with an explicit list of
output files to transfer. In Condor version 7.5.4, this problem also
affected spooled jobs that auto-detected output files.
- When a job is submitted with the -spool option to condor_submit,
the condor_schedd now correctly writes the submit event to the user log
in its spool directory.
Previously, it would try to write the event using the user
log path given to condor_submit by the user,
which condor_submit may not have access to.
- Fixed a file descriptor leak in the condor_vm-gahp. The leak would
cause the daemon to fail if a VMware job ran for more than 16 hours on a
Linux machine.
- Fixed a bug in condor_dagman that caused it to treat any dollar
sign in the log file name of a node job's submit description file
as an illegal condor_dagman macro.
Now only the sequence of characters $( delimits a macro.
Known Bugs:
- There are two known issues related to the automatic creation
of checkpoints with the Condor checkpointing library in
Condor version 7.6.0.
The first is that compression of
standalone checkpoints is disabled for 32-bit binaries.
It was always disabled previously, for 64-bit binaries.
A standalone checkpoint is one that is run outside
of Condor's standard universe. The second problem has to do with compressed
32-bit checkpoint files within the standard universe.
If a user requests a compressed 32-bit checkpoint in the standard universe,
the resulting checkpoint will not be compressed.
As with standalone checkpoints, this has never been supported
in 64-bit binaries. We hope to fix both problems in
Condor version 7.6.1.
Additions and Changes to the Manual:
condor-admin@cs.wisc.edu
