1. Removed the job_submit and job_modify functions from the plugin, they are not required for the "slurmctld" plugin type
2. Renamed the new parameter from "JobSubmitDynAllocPort" to "DynAllocPort" and renamed the variable (You need to change this in your slurm.conf file)
3. Added logic so you can see the DynAllocPort value using "scontrol show config" or "sview"
4. I made some minor formatting changes, mostly for lines that were too long
5. Added #ifdef to the msg.h header file
6. Changed the #ifdef variables in the header files to start with "DYNALLOC_", perhaps not needed, but it should safer, especiallly with some common names like "INFO_H"
7. I re-wrote much of info.c. There was no need to get a copy of the node information and process the copy. We can just work directly with the data structures.

These provide support for MapReduce+

Make core reservation test a bit more flexible in terms of node names

Fix arithmetic for core reservation count return for old RPCs
Update NEWS and RELEASE_NOTES

Remove trailing spaces from recent scontrol man page changes

Core based reservations in an asymmetric cluster should use a nodelist
with a corecnt array which overcomes the last limitation when using
these kind of reservations.
Next work will be to allow updating a core based reseravtion.

Old functions were completely wrong, but not used on most systems

Old logic uses some vestigial power management logic that no longer
applies. It creates a job allocation, but the job step blocks
indefinitely.

Once the first complete job is found, there is no need to check for
its dependencies as they will not stop another job from starting

Added for MR+ operation

Conflicts:
	NEWS

Conflicts:
	META

since left the system.

to compile correctly on newer compilers

Signed-off-by: Danny Auble <da@schedmd.com>

If job involved in dependency completes and is purged the logic
used to test for circular dependencies can use the invalid pointer
and generate an invalid memory reference before the pointer is
cleared from the dependency list data structure.

Without this change, allocations less than a whole node can result
in an incorrect task binding for power7 processors

Without this change, the testing only happens with task/affinity

This bug was introduced in 2.5.2 for the case where a GPU count was
configured, but without device files. Unfortunately it left the
CUDA_VISIBLE_DEVICES environment variable unset if GPUs were configured,
but the job did not request any of them.

Conflicts:
	NEWS