Project

Profile

Help

Task #5116

closed

Task #5069: Build pulp 3 containers

Handle properly whether to build container images with pulpcore stable or dev

Added by mdepaulo@redhat.com almost 5 years ago. Updated over 4 years ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 56
Quarter:

Description

Right now building pulpcore & pulpcore-plugin stable or nightly is hardcoded into the Dockerfile.

And it is hardcoded as nightly.

It should be a configuration option.

For CI purposes, some plugins will want to target stable, while others will want to target nightly.

Actions #1

Updated by ipanova@redhat.com almost 5 years ago

  • Status changed from NEW to ASSIGNED
Actions #2

Updated by dkliban@redhat.com almost 5 years ago

  • Sprint changed from Sprint 55 to Sprint 56
Actions #3

Updated by mdepaulo@redhat.com almost 5 years ago

Also need to handle whether nightly deps are installed or not.

Actions #4

Updated by mdepaulo@redhat.com over 4 years ago

  • % Done changed from 0 to 50
Actions #5

Updated by mdepaulo@redhat.com over 4 years ago

  • Subject changed from Handle properly whether to build containers with pulpcore stable or dev to Handle properly whether to build container images with pulpcore stable or dev
Actions #6

Updated by mdepaulo@redhat.com over 4 years ago

  • Status changed from ASSIGNED to POST
  • % Done changed from 50 to 90
Actions #7

Updated by mdepaulo@redhat.com over 4 years ago

  • % Done changed from 90 to 100

Added by Mike DePaulo over 4 years ago

Revision 3eec12c9 | View on GitHub

Replace configMaps with better featured K8s Custom Resources

Because ansible operators use them by default, they specifically watch for changes to them, and because the variable names are simpler.

This commit includes:

Making more options configurable

Switching to the stable tag for the "pulp" image It (3.0.0rc4) actually contains drf 3.9.4, and therefore works.

Let users easily define their own Custom Resources

Rename the pulp image "version" to "tag"

Note: Automatic camelCase conversion of CR field names necessitates using snake_case

fixes: #5069 containers: Replace configMap with better featured custom resources https://pulp.plan.io/issues/5219

re: #5116 Handle properly whether to build container images with pulpcore stable or dev https://pulp.plan.io/issues/5116

Added by Mike DePaulo over 4 years ago

Revision 17ccb3ee | View on GitHub

containers: Build both stable and dev images

and make images far more configurable.

Implementation includes:

Build stable and master (latest) versions (tags) of both images.

Use an undefined plugins list for no plugins ather than the dummy pulpcore-plugin.

Use variables for the pulpcore & pulpcore-plugin pip installs

Use vars/vars.yml as an override for vars (including the images data structure.)

Start work on installing into the container, and limit the CI builds to only pulpcore & pulpcore-plugin stable.

fixes: #5116 Handle properly whether to build container images with pulpcore stable or dev (Actually does more than that.) https://pulp.plan.io/issues/5116

Includes some work on: re: #5062 Create pulpcore and pulp_file container images automatically via CI https://pulp.plan.io/issues/5062

Actions #8

Updated by mdepaulo@redhat.com over 4 years ago

  • Status changed from POST to 5
Actions #9

Updated by Anonymous over 4 years ago

  • Status changed from 5 to MODIFIED
Actions #10

Updated by mdepaulo@redhat.com over 4 years ago

  • Status changed from MODIFIED to CLOSED - COMPLETE

Also available in: Atom PDF