https://github.com/apn-pucky/rolling-ansible-container
Science Score: 13.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (9.7%) to scientific vocabulary
Repository
Basic Info
- Host: GitHub
- Owner: APN-Pucky
- Language: Python
- Default Branch: master
- Size: 36.1 KB
Statistics
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
- Releases: 0
Metadata Files
README.md
rolling-ansible-container
fast development of containers
Why?
One major drawback of working with docker containers is that a small change in the one of the first steps results in a cascade of steps that need to be redone. When one is only installing software (by source or binary) these installation steps are mostly commuting.
In this pilot project we try to solve this by reusing the container and reuse already installed software. If however some steps actually depend on one another ansible can be used to manage these.
In doing so we solve another issue with Docker containers, namely that they can get quite ugly with more features being added.
Advantages
- Combining the best of two world: Ansible and containers
- Easy way to have commutable installations in a container (i.e. you don't have to bother with the order of the installations, but can order them if necessary)
- Well suited for rolling release systems
- Very large containers should be reused to save Network as much as possible
- Use the same technology on your containers as on your hardware (-> ansible)
- Ansible prevents (accidental) regression
- Ansible sort-of provides an operating system/distro independent way of installing software
- Ansible is better structured than e.g. Dockerfiles
- Reuse of missing binaries
- No need to force single commands into a single line
- Enjoy the large ansible ecosystem
Disadvantages
- Containers will grow with time. However, one can solve this by either clearing logs or rerun ansible on a fresh container
- Overhead of ansible (and thereby python). However, they can be purged after the installation if one aims for a clean production container.
- No linear installation history
- Older code will remain in the docker, unless ansible
state: latestis used. - Docker caches might not be used as efficently
Owner
- Name: Alexander Puck Neuwirth
- Login: APN-Pucky
- Kind: user
- Company: Uni Münster
- Website: https://apn-pucky.github.io/
- Repositories: 163
- Profile: https://github.com/APN-Pucky
GitHub Events
Total
Last Year
Issues and Pull Requests
Last synced: over 1 year ago
All Time
- Total issues: 0
- Total pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Total issue authors: 0
- Total pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0