#7245 RFR: setup devpi on OpenShift
Closed: Will Not/Can Not fix 2 years ago by cverna. Opened 3 years ago by abompard.

  • Describe what you need us to do:
    The devpi tool is a caching proxy for PyPI.
    PyPI has been known to be down sometimes, and software sometimes disappears there too. By using devpi, we would make it much more reliable and reproducible to deploy our Python software without RPMs, ie by creating images that would download dependencies at build time.

  • When do you need this? (YYYY/MM/DD)
    No deadline. It's easy to configure a system to use an alternative PyPI server (it's a configuration file or an env var). So it'll be easy to switch to it even after we have a functioning pipeline to build images for our apps.

  • When is this no longer needed or useful? (YYYY/MM/DD)
    When we decide on yet another deployment method. So it'll stay useful for the forseeable future.

  • If we cannot complete your request, what is the impact?
    Image builds of Python apps may be unreliable because one dependency is gone from PyPI. Or PyPI is down altogether.

The software is: https://www.devpi.net/

Security officer: @puiterwijk

Phase I

  • Software: Devpi, it's a Pyramid app.
    Advantage for Fedora: Reliablility are reproductibility when building Python apps.
    Sponsor: abompard

Phase II

  • Email list thread:
  • Upstream source: https://github.com/devpi/devpi
  • Development contacts: abompard
  • Maintainership contacts: abompard
  • Load balanceable: yes, the software includes a replication protocol, but I think it's OK to start with a single server for now.
  • Caching: No, that's devpi's job.

Phase III

  • SOP link: To be written
  • Audit request: Requesting audit here.
  • Audit timeline: Whenever Patrick has time.

Phase IV

  • Ansible playbooks: not yet
  • Fully rebuilt from ansible: ?
  • Production goal: 2018-10-01

I found: https://github.com/saily/openshift-devpi which may be at least a good starting point...

Metadata Update from @kevin:
- Issue assigned to kevin
- Issue priority set to: Waiting on Assignee (was: Needs Review)

3 years ago

Is this still needed/wanted?

Let's close that for now, we can reopen if we want to set this up

Metadata Update from @cverna:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.