| commit | 2d4d09a6e53ef9bc0a59ebf37084995b2f4bdaf7 | [log] [tgz] |
|---|---|---|
| author | Kinga Marton <kmarton@cloudera.com> | Fri Feb 26 15:39:18 2021 +0100 |
| committer | kmarton <kmarton@cloudera.com> | Fri Feb 26 15:44:48 2021 +0100 |
| tree | 61bc77d7907dac8ad607997e540cad883bba826d | |
| parent | 49c4f33ed27be266dbf57318924c61356822b0ef [diff] |
[YUNIKORN-460] Handle app reservation timeout (32)
The TerminationType is stored in a separate enum, so it can be reused for an AllocationAsk as well.
Also The AllocationAskReleaseRequest message is renamed to AllocationAskRelease, so it can be used
in both directions, not only from shim to core.
Fixes: #32
commit fc1085fa3f7ff45adc697460e6f78b4857fb4f1a
Author: kmarton <kmarton@cloudera.com>
Date: Tue Feb 23 14:48:17 2021 +0100
[YUNIKORN-460] Handle app reservation timeout
Made the AllocationAskRelease message bidirectional.
Also extended the UpdateResponse message with an array of AllocationAskRelease
YuniKorn Scheduler Interface defines protobuf interfaces for the communication between the yunikorn-core and the resource management systems.
For detailed information on the components and how to build the overall scheduler please see the yunikorn-core.
The interface defines messages for two implementations:
Both implementations are build from the same source.
Messages might require standardised constants used as identifiers. The specification declares constants that are used by the core and one or more resource management system. Constants used by just the core or one resource management system are not part of the interface specification. Default values for any part of the messages are not part of the specification.
The source and documentation are part of the same file the scheduler-interface-spec. The build process extracts the messages and the constants from the file.
The extracted protocol definition with the source code generated from the definition are part of the repository but should not be modified directly.
The messages and constants used in those messages must be updated in the documentation. The messages must be defined in the specification as blocks of type protobuf as follows:
```protobuf defintion following the protobuf specifications ```
Those blocks of definitions will be extracted from the specification file and added together to form the protobuf input. The definitions cannot have lines exceeding 200 characters.
The messages must be defined in the specification as blocks of type constants as follows:
```constants constant(s) definition ```
A constant block must be a legal go definition of one or more constants. All blocks will be extracted from the specification file and added together as a go source file. The build process will perform a syntax check on the generated go file.
The output of this build is required to build the scheduler and the shims for the resource manager(s). However, to allow building those projects against a predefined interface and without the requirement of generating the interface artifacts in each build the generated artifacts are part of the repository for direct use.
The dependent projects can use the interface by importing github.com/apache/incubator-yunikorn-scheduler-interface/lib/go/si as part of the code:
package example
import "github.com/apache/incubator-yunikorn-scheduler-interface/lib/go/si"
import "github.com/apache/incubator-yunikorn-scheduler-interface/lib/go/common"
To be added: currently only the go artifacts will be generated.
The scheduler interface is a required component for all other components of YuniKorn. For building the scheduler and its shims please check the instructions in the How to build section in the yunikorn-core repository.
The build process will download and install all required tools to build this artifact. Building the interface should only be required if the interface has been modified.
Prerequisite:
Steps:
make to build.Including the modified interface in other components without updating the repository is possible by replacing the artifact checked out from the repository with the newly generated artifact. The exact procedure is language dependent. Check the build instructions for details.
The scheduler interface specification provides the definition for the communication between different components in YuniKorn. Changes in the interface have flow on effects in all other components.
Please keep in mind that changes in the interface specification will be highly scrutinised and are not really suited as a simple start to become familiar with YuniKorn.
See how to contribute code in our website.