Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Iterative setup for podman pods infra #22

Open
abitrolly opened this issue Aug 5, 2019 · 1 comment
Open

Iterative setup for podman pods infra #22

abitrolly opened this issue Aug 5, 2019 · 1 comment

Comments

@abitrolly
Copy link
Member

podman promises to be better Docker, and provides pods on top of ordinary containers, similar to kubernetes. Let's see if it can handle the standard case of test driven/iterative infrastructure development.

In https://github.com/release-monitoring/anitya Dockerfile is greatly outdated. Missing dependencies, absent services, different commands that run for Dockerfile, for Development Ansible and for production.

Let's try to see how podman improves that. And first, let's setup DevOps workbench.

  1. Terminal pane to write container build code
  2. Terminal pane that watches container build code, rebuilds container and restarts it (could be two panes - one for building, one for starting)
  3. Terminal pane that waits for container to startup, then for services to start, then testes them and report result

This is setup for TDD for infrastructure. The third panel is our test, which is connected to the second panel - if container failed to start or failed in the middle, the test panel should detect that and report as well.

Them we can just leave all three panels independently and work on the code.

@abitrolly abitrolly changed the title Test podman pods Iterative setup for podman pods infra Sep 10, 2019
@abitrolly
Copy link
Member Author

This setup we need to create container for https://github.com/release-monitoring/anitya and try to reuse Ansible scripts that will be shared with production.

  1. Get Anitya running
  2. Expose DB connection for inspection
  3. Run shemaspy/schemaspy container

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant