Project

Profile

Help

Task #6638

[Epic] Host fixtures docker container at https://fixtures.pulpproject.org

Added by bmbouter 6 months ago. Updated 3 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

100%

Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Background

Goals

  • Have the fixtures serve from fixtures.pulpproject.org
  • Have them be up to date so as the pulp-fixtures content changes, fixtures.pulpproject.org automatically updates
  • Updating every 15 minutes
  • SSL with valid letsencrypt certs would also be sweet, but that's a bonus

Subtasks

Task #6646: Host fixtures with osci.ioCLOSED - COMPLETE

Actions
Pulp - Task #6647: Update "Infrastructure" wiki pageCLOSED - COMPLETEbmbouter

Actions
Task #6649: Take down fixtures at fedorapeople.orgCLOSED - COMPLETEdkliban@redhat.com

Actions
Ansible Plugin - Task #6650: Remove use of fixtures from fedorapeople.orgCLOSED - COMPLETE

Actions
Debian Support - Task #6651: Remove use of fixtures from fedorapeople.orgCLOSED - NOTABUG

Actions
Container Support - Task #6652: Remove use of fixtures from fedorapeople.orgCLOSED - COMPLETE

Actions
File Support - Task #6653: Remove use of fixtures from fedorapeople.orgCLOSED - CURRENTRELEASEdaviddavis

Actions
Maven Plugin - Task #6654: Remove use of fixtures from fedorapeople.orgCLOSED - COMPLETE

Actions
Python Support - Task #6655: Remove use of fixtures from fedorapeople.orgMODIFIEDdaviddavis

Actions
RPM Support - Task #6656: Remove use of fixtures from fedorapeople.orgCLOSED - CURRENTRELEASEppicka

Actions
Pulp - Task #6880: Move https://fixtures.pulpproject.org/fixtures/ to https://fixtures.pulpproject.org/CLOSED - COMPLETEdaviddavis

Actions
Pulp - Task #6881: Switch pulp-smash to use fixtures.pulpproject.org instead of fedorapeopleCLOSED - COMPLETEdaviddavis

Actions
Pulp - Task #6883: Have Robotello use fixtures from https://fixtures.pulpproject.org/ or a local containerCLOSED - COMPLETE

Actions
Pulp - Issue #6943: New Pulp Project fixutres site is incorrectly setup for python pluginCLOSED - CURRENTRELEASEdaviddavisActions

History

#1 Updated by bmbouter 6 months ago

  • Description updated (diff)

#2 Updated by bmbouter 6 months ago

  • Description updated (diff)

#3 Updated by bmbouter 6 months ago

  • Subject changed from Host fixtures docker container at https://fixtures.pulpproject.org to [Epic] Host fixtures docker container at https://fixtures.pulpproject.org
  • Description updated (diff)

#4 Updated by bmbouter 6 months ago

  • Tracker changed from Issue to Task
  • % Done set to 0

#5 Updated by misc 5 months ago

So, i started to look at this. I was planning on doing that on openshift online, but my account is currently blocked (ticket is opened).

I am going to deploy that on www for the time being, but I do have some issues with that:

  • the container is kinda big. I did fill the disk while doing tests, but I didn't looked if that's big and required, or big and need some cleanup from build artificats. I will take a look later once that's deployed, and make sure to cleanup podman on upgrade.

  • that would be on 1 single server, which is not optimal for CI, in case we do reboot it.

Moving to openshift would alleviate the 2nd issue, cleaning the container would alleviate the 1st.

However, due to the use of HSTS, we would have to get a digicert certificate first, which requires likely a rather lengthy process. I will see with Duck about that.

#6 Updated by misc 5 months ago

Here is the PR: https://github.com/pulp/pulp-infra-ansible/pull/6

The service is almost ready, but I would like to requests that people keep a way to revert to previous CI in case anything happen. For example, I am still unsure that deployment of new system is working.

Quick summary. This is running directly in the container, we do not have any automated test to see if it work, and it will upgrade within 5 minutes to the latest pushed version. Among the problem that could arise, I see:

  • filling the hard drive. A docker all time classic. I do not think we have monitoring on that server.
  • having a dubious distro container not running well on a RHEL 7 system, due to "too old" or some weird selinux/apparmor issue.
  • the host being blacklisted by

If people need to verify what is running, there is a service "systemctl status fixtures". The current version should be in ~/.current_fixtures as root, and all is done with a cronjob.

I still have a few things to fix before we can use it.

#7 Updated by bmbouter 5 months ago

misc wrote:

Here is the PR: https://github.com/pulp/pulp-infra-ansible/pull/6

The service is almost ready, but I would like to requests that people keep a way to revert to previous CI in case anything happen. For example, I am still unsure that deployment of new system is working.

OK will do. We'll wait to take down the old ones until we get the OK from you.

Quick summary. This is running directly in the container, we do not have any automated test to see if it work, and it will upgrade within 5 minutes to the latest pushed version. Among the problem that could arise, I see:

  • filling the hard drive. A docker all time classic. I do not think we have monitoring on that server.
  • having a dubious distro container not running well on a RHEL 7 system, due to "too old" or some weird selinux/apparmor issue.
  • the host being blacklisted by

If people need to verify what is running, there is a service "systemctl status fixtures". The current version should be in ~/.current_fixtures as root, and all is done with a cronjob.

OK we can document this in our fixtures usage docs. Can you link me to that actual file when it's online?

I still have a few things to fix before we can use it.

OK we'll standy. Thank you!

Also regarding the container's size: I suspect the container is legitimately big. It stores all the fixture data for all plugins (EL rpms, container content, ansible content, debian content, python content, file content, etc)

Please register to edit this issue

Also available in: Atom PDF