<commit_before>%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\label{sec:History-7-1}Development Release Series 7.1}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

This is the development release series of Condor.
The details of each version are described below.


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection*{\label{sec:New-7-1-3}Version 7.1.3}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\noindent Release Notes:

\begin{itemize}

\item Updated the version of Globus Toolkit: The Condor binaries are now
	linked against Globus v4.2.0.

\item Updated the version of OpenSSL: The Condor binaries are now linked
	against OpenSSL 0.9.8h.

\item Updated the version of GCB: The Condor binaries are now linked
	against GCB 1.5.6.

\item Changes to the \MacroNI{ALLOW\_*} and \MacroNI{DENY\_*} configuration
	variables no longer require the use of the \Opt{-full} option to
	\Condor{reconfig} upon reconfiguration.

\end{itemize}

\noindent New Features:

\begin{itemize}

\item Added a new mechanism termed \Term{Concurrency Limits}.  This
	mechanism allows the Condor pool administrator to define an arbitrary
	number of consumable resources in the configuration file of the
	matchmaker.  The availability of these consumable resources will be taken
	into account during the matchmaking process.  Individual jobs can specify
	how many of each type of consumable resource is required.  
	Typical applications of Concurrency Limits could include management of
	software licenses, database connections, or any other consumable resource
	that is external to Condor.  NOTE: Documentation still being written on
	this feature.

\item Added support for Condor to manage serial high throughput computing
	workloads on the IBM Blue Gene supercomputer.  The IBM Blue Gene/P is now
	a supported platform.

\item Extended Job Hooks (see section~\ref{sec:job-hooks}) to allow for
	alternate transformation and/or monitoring engines for the Job Router (see
	section~\ref{sec:JobRouter}.  Routing is still controlled by the Job
	Router, but if Job Router Hooks are configured, then external programs or
	scripts can be used to transform and monitor the job instead of Condor's
	internal engine.

\item Added the ability for Windows slot users to load and run their jobs
within the context of their profile. 
This includes the \File{My Documents} directory 
hierarchy, its monikers, and the user's registry hive.
To use the profile, add a \SubmitCmd{load\_profile} command to the 
submit description file.  A current restriction prevents the use of
\SubmitCmd{load\_profile} 
in conjunction with \SubmitCmd{run\_as\_owner}. Please refer to 
section~\ref{sec:windows-load-profile} for further details.

\item The \File{StarterLog} file for local universe jobs now displays the job id
in each line in the file, so that interleaved messages relevant to
different jobs running concurrently can be identified.

\item Added the \Opt{-AllowVersionMismatch} command line option to
\Condor{submit\_dag} and \Condor{dagman} to (if absolutely necessary)
allow a version mismatch between \Condor{dagman} and the
\File{.condor.sub} file used to submit it.
This permits a Condor version mismatch between
\Condor{submit\_dag} and \Condor{dagman}).

\item Streamlined the protocol between submit and execute machines; in some
	instances less messages will be exchanged over the network.


\end{itemize}

\noindent Configuration Variable Additions and Changes:

\begin{itemize}

\item Added the new configuration variable
\Macro{MAX\_PENDING\_STARTD\_CONTACTS}.  This limits the
number of simultaneous connection attempts by the \Condor{schedd} when
it is requesting claims from the \Condor{startd}s.  The intention is
to protect the \Condor{schedd} from being overloaded by authentication
operations.  The default is 0, which indicates no limit.

\item Added the new configuration variable
\Macro{SEC\_INVALIDATE\_SESSIONS\_VIA\_TCP},  which
defaults to \Expr{True}.  Previously, attempts to use an invalid security
session resulted in a UDP rather than a TCP response.  In networks with
different firewall rules for UDP and TCP, the filtering of the session
invalidation messages was easily overlooked, since it would not
typically happen during the initial vetting of the pool.  If these
packets were filtered out, then at the subsequent \Condor{collector}
restart, no daemons would be able to advertise themselves to the
pool until their existing security sessions expired.  The old behavior
can be achieved by setting this configuration parameter to \Expr{False}.

\item Added the new configuration variable
\Macro{SEC\_ENABLE\_MATCH\_PASSWORD\_AUTHENTICATION}.
This is a special authentication mechanism designed to minimize
overhead in the \Condor{schedd} when communicating with the execute
machine.  Essentially, matchmaking results in a secret being shared
between the \Condor{schedd} and \Condor{startd}, and this is used to
establish a strong security session between the execute and submit
daemons without going through the usual security negotiation protocol.
This is especially important when operating at large scale over high
latency networks, as in a glidein pool with one submit machine and thousands of
execute machines on a network with 0.1 second round trip times.  See
\pageref{param:SecEnableMatchPasswordAuthentication} for
details.

\item Added configuration entry \Macro{GLEXEC\_JOB} which replaces the
	functionality previously encapsulated in \Macro{GLEXEC\_STARTER}.  Using
	\Macro{GLEXEC\_JOB} enables privilege separation in Condor via glexec in a
	manner much more consistent with how Condor's own privilege separation
	machanism works.  Specifically, the user identity switching will now occur
	between the \Condor{starter} and the actual user job.

\item Added configuration parameter \Macro{AMAZON\_GAHP\_WORKER\_MAX\_NUM}
	to specify a ceiling on the number of threads spawned on the submit
	machine to support jobs running on Amazon EC2.  Defaults to 5.

\end{itemize}

\noindent Bugs Fixed:

\begin{itemize}

\item Fixed a bug in the \Condor{schedd} that would cause it to
except if a crontab entry was incorrectly formatted.

\item Fixed a bug in the CondorView server (collector) that caused it
to except (crash) when it received a machine ClassAd without a valid state.
It now logs this under level \MacroNI{D\_ALWAYS} and ignores the ClassAd.

\item Fixed a bug from Condor version 7.1.2 that would cause 
Condor daemons to start
consuming a lot of cpu time after rare types of communication failures
during security negotiation.

\item Fixed a bug from Condor version 7.1.2 that in rare cases could cause
	Condor to fail to recognize when a call to exec() fails on Unix
	platforms.

\item Fixed problems with configuration parameter
	\Macro{JOB\_INHERITS\_STARTER\_ENVIRONMENT} when using PrivSep.

\item Improved the deletion of Amazon EC2 jobs when the server is
	unreachable.

\item Fixed problems with Condor parallel universe jobs when recovering from
	a reboot of the submit machine.

\end{itemize}
<commit_msg>Added blurb that v7.1.3 includes patches from v7.0.5.<commit_after>%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\label{sec:History-7-1}Development Release Series 7.1}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

This is the development release series of Condor.
The details of each version are described below.


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection*{\label{sec:New-7-1-3}Version 7.1.3}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\noindent Release Notes:

\begin{itemize}

\item This developer release includes the majority of the bug fixes released
	in stable version 7.0.5, including the security patches documented in that
	release.  See section~\ref{sec:New-7-0-5} below.

\item Updated the version of Globus Toolkit: The Condor binaries are now
	linked against Globus v4.2.0.

\item Updated the version of OpenSSL: The Condor binaries are now linked
	against OpenSSL 0.9.8h.

\item Updated the version of GCB: The Condor binaries are now linked
	against GCB 1.5.6.

\item Changes to the \MacroNI{ALLOW\_*} and \MacroNI{DENY\_*} configuration
	variables no longer require the use of the \Opt{-full} option to
	\Condor{reconfig} upon reconfiguration.

\end{itemize}

\noindent New Features:

\begin{itemize}

\item Added a new mechanism termed \Term{Concurrency Limits}.  This
	mechanism allows the Condor pool administrator to define an arbitrary
	number of consumable resources in the configuration file of the
	matchmaker.  The availability of these consumable resources will be taken
	into account during the matchmaking process.  Individual jobs can specify
	how many of each type of consumable resource is required.  
	Typical applications of Concurrency Limits could include management of
	software licenses, database connections, or any other consumable resource
	that is external to Condor.  NOTE: Documentation still being written on
	this feature.

\item Added support for Condor to manage serial high throughput computing
	workloads on the IBM Blue Gene supercomputer.  The IBM Blue Gene/P is now
	a supported platform.

\item Extended Job Hooks (see section~\ref{sec:job-hooks}) to allow for
	alternate transformation and/or monitoring engines for the Job Router (see
	section~\ref{sec:JobRouter}.  Routing is still controlled by the Job
	Router, but if Job Router Hooks are configured, then external programs or
	scripts can be used to transform and monitor the job instead of Condor's
	internal engine.

\item Added the ability for Windows slot users to load and run their jobs
within the context of their profile. 
This includes the \File{My Documents} directory 
hierarchy, its monikers, and the user's registry hive.
To use the profile, add a \SubmitCmd{load\_profile} command to the 
submit description file.  A current restriction prevents the use of
\SubmitCmd{load\_profile} 
in conjunction with \SubmitCmd{run\_as\_owner}. Please refer to 
section~\ref{sec:windows-load-profile} for further details.

\item The \File{StarterLog} file for local universe jobs now displays the job id
in each line in the file, so that interleaved messages relevant to
different jobs running concurrently can be identified.

\item Added the \Opt{-AllowVersionMismatch} command line option to
\Condor{submit\_dag} and \Condor{dagman} to (if absolutely necessary)
allow a version mismatch between \Condor{dagman} and the
\File{.condor.sub} file used to submit it.
This permits a Condor version mismatch between
\Condor{submit\_dag} and \Condor{dagman}).

\item Streamlined the protocol between submit and execute machines; in some
	instances less messages will be exchanged over the network.


\end{itemize}

\noindent Configuration Variable Additions and Changes:

\begin{itemize}

\item Added the new configuration variable
\Macro{MAX\_PENDING\_STARTD\_CONTACTS}.  This limits the
number of simultaneous connection attempts by the \Condor{schedd} when
it is requesting claims from the \Condor{startd}s.  The intention is
to protect the \Condor{schedd} from being overloaded by authentication
operations.  The default is 0, which indicates no limit.

\item Added the new configuration variable
\Macro{SEC\_INVALIDATE\_SESSIONS\_VIA\_TCP},  which
defaults to \Expr{True}.  Previously, attempts to use an invalid security
session resulted in a UDP rather than a TCP response.  In networks with
different firewall rules for UDP and TCP, the filtering of the session
invalidation messages was easily overlooked, since it would not
typically happen during the initial vetting of the pool.  If these
packets were filtered out, then at the subsequent \Condor{collector}
restart, no daemons would be able to advertise themselves to the
pool until their existing security sessions expired.  The old behavior
can be achieved by setting this configuration parameter to \Expr{False}.

\item Added the new configuration variable
\Macro{SEC\_ENABLE\_MATCH\_PASSWORD\_AUTHENTICATION}.
This is a special authentication mechanism designed to minimize
overhead in the \Condor{schedd} when communicating with the execute
machine.  Essentially, matchmaking results in a secret being shared
between the \Condor{schedd} and \Condor{startd}, and this is used to
establish a strong security session between the execute and submit
daemons without going through the usual security negotiation protocol.
This is especially important when operating at large scale over high
latency networks, as in a glidein pool with one submit machine and thousands of
execute machines on a network with 0.1 second round trip times.  See
\pageref{param:SecEnableMatchPasswordAuthentication} for
details.

\item Added configuration entry \Macro{GLEXEC\_JOB} which replaces the
	functionality previously encapsulated in \Macro{GLEXEC\_STARTER}.  Using
	\Macro{GLEXEC\_JOB} enables privilege separation in Condor via glexec in a
	manner much more consistent with how Condor's own privilege separation
	machanism works.  Specifically, the user identity switching will now occur
	between the \Condor{starter} and the actual user job.

\item Added configuration parameter \Macro{AMAZON\_GAHP\_WORKER\_MAX\_NUM}
	to specify a ceiling on the number of threads spawned on the submit
	machine to support jobs running on Amazon EC2.  Defaults to 5.

\end{itemize}

\noindent Bugs Fixed:

\begin{itemize}

\item Includes bug fixes from Condor v7.0.5, including the security fixes.
	See section~\ref{sec:New-7-0-5}.

\item Fixed a bug in the \Condor{schedd} that would cause it to
except if a crontab entry was incorrectly formatted.

\item Fixed a bug in the CondorView server (collector) that caused it
to except (crash) when it received a machine ClassAd without a valid state.
It now logs this under level \MacroNI{D\_ALWAYS} and ignores the ClassAd.

\item Fixed a bug from Condor version 7.1.2 that would cause 
Condor daemons to start
consuming a lot of cpu time after rare types of communication failures
during security negotiation.

\item Fixed a bug from Condor version 7.1.2 that in rare cases could cause
	Condor to fail to recognize when a call to exec() fails on Unix
	platforms.

\item Fixed problems with configuration parameter
	\Macro{JOB\_INHERITS\_STARTER\_ENVIRONMENT} when using PrivSep.

\item Improved the deletion of Amazon EC2 jobs when the server is
	unreachable.

\item Fixed problems with Condor parallel universe jobs when recovering from
	a reboot of the submit machine.

\end{itemize}

{'fraction_non_alphanumeric': 0.08744131455399061, 'fraction_numerical': 0.005216484089723527, 'mean_word_length': 4.7291744490100855, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6594745', 'n_tokens_mistral': 4218, 'n_tokens_neox': 4007, 'n_words': 1997}