-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #16 from ArangoGutierrez/issue_14
fix typo on README
- Loading branch information
Showing
10 changed files
with
70 additions
and
80 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,21 +11,21 @@ works, incorporate into other computer software, distribute, and sublicense | |
such enhancements or derivative works thereof, in binary and source code | ||
form. | ||
|
||
## Contributing | ||
|
||
# Contributing | ||
|
||
When contributing to [sylabs/nomad-driver-singularity](https://github.com/sylabs/nomad-driver-singularity/), it | ||
is important to properly communicate the gist of the contribution. If it is a simple code or | ||
editorial fix, simply explaining this within the GitHub Pull Request (PR) will suffice. But | ||
if this is a larger fix or Enhancement, you are advised to first discuss the change | ||
with the project leader or developers. | ||
When contributing to [sylabs/nomad-driver-singularity](https://github.com/sylabs/nomad-driver-singularity/) | ||
it is important to properly communicate the gist of the contribution. | ||
If it is a simple code or editorial fix, simply explaining this within | ||
the GitHub Pull Request (PR) will suffice. But if this is a larger fix or Enhancement, | ||
you are advised to first discuss the change with the project leader or developers. | ||
|
||
Please note we have a code of conduct, described below. Please follow it in | ||
all your interactions with the project members and users. | ||
|
||
## Pull Requests (PRs) | ||
|
||
### Process | ||
|
||
1. Essential bug fix PRs should be sent to both master and release branches. | ||
2. Small bug fix and feature enhancement PRs should be sent to master only. | ||
3. Follow the existing code style precedent, especially for C. For Golang, you | ||
|
@@ -45,9 +45,9 @@ all your interactions with the project members and users. | |
requirements are met. | ||
10. Documentation must be provided if necessary (next section) | ||
|
||
# Code of Conduct | ||
## Code of Conduct | ||
|
||
## Our Pledge | ||
### Our Pledge | ||
|
||
In the interest of fostering an open and welcoming environment, we as | ||
contributors and maintainers pledge to making participation in our project and | ||
|
@@ -56,7 +56,7 @@ size, disability, ethnicity, gender identity and expression, level of experience | |
nationality, personal appearance, race, religion, or sexual identity and | ||
orientation. | ||
|
||
## Our Standards | ||
### Our Standards | ||
|
||
Examples of behavior that contributes to creating a positive environment | ||
include: | ||
|
@@ -90,7 +90,7 @@ that are not aligned to this Code of Conduct, or to ban temporarily or | |
permanently any contributor for other behaviors that they deem inappropriate, | ||
threatening, offensive, or harmful. | ||
|
||
## Scope | ||
### Scope | ||
|
||
This Code of Conduct applies both within project spaces and in public spaces | ||
when an individual is representing the project or its community. Examples of | ||
|
@@ -99,7 +99,7 @@ address, posting via an official social media account, or acting as an appointed | |
representative at an online or offline event. Representation of a project may be | ||
further defined and clarified by project maintainers. | ||
|
||
## Enforcement | ||
### Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
reported by contacting the project leaders ([email protected]). All | ||
|
@@ -113,10 +113,10 @@ Project maintainers, contributors and users who do not follow or enforce the | |
Code of Conduct in good faith may face temporary or permanent repercussions | ||
with their involvement in the project as determined by the project's leader(s). | ||
|
||
## Attribution | ||
### Attribution | ||
|
||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, | ||
available at [http://contributor-covenant.org/version/1/4][version] | ||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], | ||
version 1.4, available at [http://contributor-covenant.org/version/1/4][version] | ||
|
||
[homepage]: http://contributor-covenant.org | ||
[version]: http://contributor-covenant.org/version/1/4/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
# Maintainers: | ||
# Maintainers | ||
|
||
- Eduardo Arango <[email protected]> | ||
|
||
# Contributors: | ||
## Contributors |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,45 +1,48 @@ | ||
# nomad-driver-singularity | ||
|
||
[Hashicorp Nomad](https://www.nomadproject.io/) driver plugin using [Singularity containers](https://github.com/sylabs/singularity) to execute tasks. | ||
[Hashicorp Nomad](https://www.nomadproject.io/) driver plugin using | ||
[Singularity containers](https://github.com/sylabs/singularity) to execute tasks. | ||
|
||
Requirements | ||
------------ | ||
## Requirements | ||
|
||
- [Nomad](https://www.nomadproject.io/downloads.html) v0.9+ | ||
- [Go](https://golang.org/doc/install) v1.11+ (to build the provider plugin) | ||
- [Singularity](https://github.com/singularityware/singularity) v3.0.3+ | ||
|
||
Building The Driver | ||
--------------------- | ||
## Building The Driver | ||
|
||
Clone repository on your prefered path | ||
|
||
```sh | ||
$ git clone [email protected]:sylabs/nomad-driver-singularity | ||
git clone [email protected]:sylabs/nomad-driver-singularity | ||
``` | ||
|
||
Enter the provider directory and build the provider | ||
|
||
```sh | ||
$ nomad-driver-singularity | ||
$ make dep | ||
$ make build | ||
cd nomad-driver-singularity | ||
make dep | ||
make build | ||
``` | ||
|
||
Developing the Provider | ||
--------------------------- | ||
## Developing the Provider | ||
|
||
If you wish to contribute on the project, you'll first need [Go](http://www.golang.org) installed on your machine, and have have `singularity` installed. | ||
If you wish to contribute on the project, you'll first need [Go](http://www.golang.org) | ||
installed on your machine, and have have `singularity` installed. | ||
|
||
To compile the provider, run `make build`. | ||
This will build the provider and put the task driver binary under | ||
the NOMAD plugin dir, | ||
which by default is located under `<nomad-data-dir>/plugins/`. | ||
|
||
To compile the provider, run `make build`. This will build the provider and put the task driver binary under the NOMAD plugin dir, which by deafult is located under `<nomad-data-dir>/plugins/`. | ||
Check Nomad `-data-dir` and `-plugin-dir` flags for more information. | ||
|
||
```sh | ||
$ make build | ||
make build | ||
``` | ||
|
||
In order to test the provider, you can simply run `make test`. | ||
|
||
```sh | ||
$ make test | ||
make test | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.