Releases: xenon-middleware/xenon
This is release 3.1.0 of Xenon.
What problem does Xenon solve?
Many applications use remote storage and compute resources. To do so, they need to include code to interact with the scheduling systems and file transfer protocols used on those remote machines.
Unfortunately, many different scheduler systems and file transfer protocols exist, often with completely different programming interfaces. This makes it hard for applications to switch to a different system or support multiple remote systems simultaneously.
Xenon solves this problem by providing a single programming interface to many different types of remote resources, allowing applications to switch without changing a single line of code.
Notable changes compared to v3.0.4:
- improved error state returned by getJobStatusses to show the difference between no job and connection loss.
- added support for slurm 19
- added heartbeat in the SSH adaptor quickly detect lost connections.
- moved to version 2.4.0 of SSHD
This is release 3.0.4 of Xenon.
What problem does Xenon solve?
Many applications use remote storage and compute resources. To do so, they need to include code to interact with the scheduling systems and file transfer protocols used on those remote machines.
Unfortunately, many different scheduler systems and file transfer protocols exist, often with completely different programming interfaces. This makes it hard for applications to switch to a different system or support multiple remote systems simultaneously.
Xenon solves this problem by providing a single programming interface to many different types of remote resources, allowing applications to switch without changing a single line of code.
Notable changes compared to v3.0.3:
- fixed bug in FTP adaptor when listing the root directory
- fixed bug in SFTP adaptor when listing the root directory
This is release 3.0.3 of Xenon.
What problem does Xenon solve?
Many applications use remote storage and compute resources. To do so, they need to include code to interact with the scheduling systems and file transfer protocols used on those remote machines.
Unfortunately, many different scheduler systems and file transfer protocols exist, often with completely different programming interfaces. This makes it hard for applications to switch to a different system or support multiple remote systems simultaneously.
Xenon solves this problem by providing a single programming interface to many different types of remote resources, allowing applications to switch without changing a single line of code.
Notable changes compared to v3.0.2:
- fixed the FTP adaptor which lost bytes due to being in ASCII mode
- fixed the numbering in this changelog
This is release 3.0.2 of Xenon.
What problem does Xenon solve?
Many applications use remote storage and compute resources. To do so, they need to include code to interact with the scheduling systems and file transfer protocols used on those remote machines.
Unfortunately, many different scheduler systems and file transfer protocols exist, often with completely different programming interfaces. This makes it hard for applications to switch to a different system or support multiple remote systems simultaneously.
Xenon solves this problem by providing a single programming interface to many different types of remote resources, allowing applications to switch without changing a single line of code.
Notable changes compared to v3.0.1:
- updated jaxb dependencies to prevent illegal access warning from JVM
- removed leftover debug print in webdav
This is release 3.0.1 of Xenon.
What problem does Xenon solve?
Many applications use remote storage and compute resources. To do so, they need to include code to interact with the scheduling systems and file transfer protocols used on those remote machines.
Unfortunately, many different scheduler systems and file transfer protocols exist, often with completely different programming interfaces. This makes it hard for applications to switch to a different system or support multiple remote systems simultaneously.
Xenon solves this problem by providing a single programming interface to many different types of remote resources, allowing applications to switch without changing a single line of code.
Notable changes compared to v3.0.0:
- fixed minute delay on shutdown when SSH adaptor was used (discussed as part of #654).
This is release 3.0.0 of Xenon.
What problem does Xenon solve?
Many applications use remote storage and compute resources. To do so, they need to include code to interact with the scheduling systems and file transfer protocols used on those remote machines.
Unfortunately, many different scheduler systems and file transfer protocols exist, often with completely different programming interfaces. This makes it hard for applications to switch to a different system or support multiple remote systems simultaneously.
Xenon solves this problem by providing a single programming interface to many different types of remote resources, allowing applications to switch without changing a single line of code.
Notable changes compared to v2.6.2:
- Moved adaptors with large dependencies (such as S3 and HDFS) into separate libraries, resulting in a much smaller "core" distribution.
- Changed JobDescription to a tasks+cores model, instead of nodes+processes+thread (#625).
- Remove the JOB_OPTIONS hack from JobDescription (#629 and #628)
- Added support for memory requirements and job name in JobDescription (#562 and #609)
- Added an adaptor for the at scheduler (#381)
- Dropped offline support (#649)
- Require Java 11 or greater (#647)
- Many smaller bugfixes and updates of dependencies.
This is release 2.6.2 of Xenon.
What problem does Xenon solve?
Many applications use remote storage and compute resources. To do so, they need to include code to interact with the scheduling systems and file transfer protocols used on those remote machines.
Unfortunately, many different scheduler systems and file transfer protocols exist, often with completely different programming interfaces. This makes it hard for applications to switch to a different system or support multiple remote systems simultaneously.
Xenon solves this problem by providing a single programming interface to many different types of remote resources, allowing applications to switch without changing a single line of code.
Notable changes compared to v2.6.1:
- added support for temp space in JobDescription.
- added support stdout, stderr and stdin to Torque.
- fixed several unit tests that failed on OSX
This is release 2.6.1 of Xenon.
What problem does Xenon solve?
Many applications use remote storage and compute resources. To do so, they need to include code to interact with the scheduling systems and file transfer protocols used on those remote machines.
Unfortunately, many different scheduler systems and file transfer protocols exist, often with completely different programming interfaces. This makes it hard for applications to switch to a different system or support multiple remote systems simultaneously.
Xenon solves this problem by providing a single programming interface to many different types of remote resources, allowing applications to switch without changing a single line of code.
Notable changes compared to v2.6.0:
- fixed hashCode and equals of JobDescription
This is release 2.6.0 of Xenon.
What problem does Xenon solve?
Many applications use remote storage and compute resources. To do so, they need to include code to interact with the scheduling systems and file transfer protocols used on those remote machines.
Unfortunately, many different scheduler systems and file transfer protocols exist, often with completely different programming interfaces. This makes it hard for applications to switch to a different system or support multiple remote systems simultaneously.
Xenon solves this problem by providing a single programming interface to many different types of remote resources, allowing applications to switch without changing a single line of code.
Notable changes compared to v2.5.0:
- added support for scheduler specific arguments to JobDescription
- fixed specification of runtime limit in gridengine adaptor
This is release 2.5.0 of Xenon.
What problem does Xenon solve?
Many applications use remote storage and compute resources. To do so, they need to include code to interact with the scheduling systems and file transfer protocols used on those remote machines.
Unfortunately, many different scheduler systems and file transfer protocols exist, often with completely different programming interfaces. This makes it hard for applications to switch to a different system or support multiple remote systems simultaneously.
Xenon solves this problem by providing a single programming interface to many different types of remote resources, allowing applications to switch without changing a single line of code.