[
https://issues.apache.org/jira/browse/AIRFLOW-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017309#comment-17017309
]
ASF GitHub Bot commented on AIRFLOW-4030:
-----------------------------------------
vsoch commented on pull request #7191: [AIRFLOW-4030] second attempt to add
singularity to airflow
URL: https://github.com/apache/airflow/pull/7191
This is a second attempt to add Singularity Container support to Apache
Airflow by way of Singularity Python. I am using the previously created JIRA
ticket 4030 (created in March 2019) as it is still relevant. I am a new
contributor and largely not familiar with the community here (and yes I've read
the guidelines) so I would appreciate support and kindness from the individuals
that act as maintainers here, and any additional support from other folks that
are also interested in this integration. Thank you!
Signed-off-by: Vanessa Sochat <[email protected]>
---
Issue link: WILL BE INSERTED BY
[boring-cyborg](https://github.com/kaxil/boring-cyborg)
Make sure to mark the boxes below before creating PR: [x]
- [x] Description above provides context of the change
- [x] Commit message/PR title starts with `[AIRFLOW-NNNN]`. AIRFLOW-NNNN =
JIRA ID<sup>*</sup>
- [ ] Unit tests coverage for changes (not needed for documentation changes)
- [x] Commits follow "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)"
- [ ] Relevant documentation is updated including usage instructions.
- [ ] I will engage committers as explained in [Contribution Workflow
Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example).
<sup>*</sup> For document-only changes commit message can start with
`[AIRFLOW-XXXX]`.
---
In case of fundamental code change, Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
Read the [Pull Request
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)
for more information.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Add Singularity Container Operator
> ----------------------------------
>
> Key: AIRFLOW-4030
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4030
> Project: Apache Airflow
> Issue Type: Improvement
> Components: operators
> Reporter: Vanessa
> Assignee: Vanessa
> Priority: Minor
>
> Singularity containers are comparable to Docker in the level of operation -
> they provide an encapsulated environment with an OS, libraries, and custom
> software for the user to run. The key difference is that Docker is not
> optimized for scientific compute because it could never be installed on a
> shared research cluster. Singularity, on the other hand, does not have these
> issues and is installed across HCP centers internationally.
> This issue is to add Singularity containers as an operator to Apache Airflow,
> so that we can start to explore using airflow in an HPC environment. I work
> with Encode DCC at Stanford, and am hopeful to explore Airflow as an
> alternative to the workflow manager(s) we are using. I am one of the
> [original Singularity developers see
> |https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0177459]
> that manages the Singularity Python client (spython), Singularity Hub and
> Singularity Registry Server, and have started working on this issue here:
> [https://github.com/apache/airflow/pull/4846.] Looking forward to working
> with you!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
