Project

Profile

Help

Story #8847

Story #8846: As a pulp_installer user, I do not need to use the latest micro release to install the latest micro release of pulpcore

As a pulp_installer user, I can specify variables for the minor release branch of pulpcore/plugins

Added by mdepaulo@redhat.com 5 months ago. Updated 18 days ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

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

Description

The tentative design is the following variables:

pulpcore_branch: defaults to the same minor release branch as the installer, and we do not want users to change this

pulpcore_update: boolean, defaults to false for idempotency, whether to update to the latest micro release on the minor release branch

pulp_install_plugins.plugin-name.branch: no default value, users are encouraged to provide it in the format like "3.14"

pulp_install_plugins.plugin-name.update: boolean, defaults to false for idempotency, whether to update to the latest micro release on the minor release branch

It also means that when say a user runs pulp_installer 3.15 against pulpcore 3.14, the "upgrade" must happen. This is the current logic, but it needs to be updated for the new logic above.

docs/customizing.md will need particular updates.

Associated revisions

Revision aaa52ba2 View on GitHub
Added by dkliban@redhat.com 19 days ago

Add ability to specify a minor version for pulpcore_version

pulpcore_version now defaults to a specific minor release of pulpcore (e.g.: 3.15) which the installer is going to install.

When the installer is run for the first time, the latest patch release of pulpcore (e.g.: 3.15.2) is installed. If the installer is run again with the same value of pulpcore_version, the pulpcore package is not updated. In order to update to the latest patch release within a minor stream, the user must set pulpcore_update to true.

If the user sets the pulpcore_version to a different minor release of pulpcore (e.g.: 3.16), the installer will attempt to upgrade pulpcore to the latest patch release (e.g.: 3.16.1) for that minor release of pulpcore.

If the user sets the pulpcore_version to a specific patch release, the installer will attempt to install that specific release of pulpcore.

If the installed plugins are not compatible with the requested release of pulpcore, the installer will not make any changes.

The version of a plugin can now also be specified as a minor release (e.g.: 1.8) or a specific patch release (e.g.: 1.8.2). When the a minor release is specified and it is the same as the installed version of the plugin, the upgrade parameter for that plugin must be set to true in order for the plugin to be updated to the latest patch release.

The internal variable __pulp_version was renamed to __pulpcore_version.

The release-static test scenario for molecule was also updated to test this feature.

fixes: #8847 https://pulp.plan.io/issues/8847

History

#1 Updated by mdepaulo@redhat.com 5 months ago

  • Subject changed from As a pulp_installer user, I can specify variables for the minor release branch of pulpcore/plugins, and whether to update within that branch to As a pulp_installer user, I can specify variables for the minor release branch of pulpcore/plugins

#2 Updated by mdepaulo@redhat.com 5 months ago

  • Description updated (diff)

#3 Updated by pulpbot about 1 month ago

  • Status changed from NEW to POST

#4 Updated by dkliban@redhat.com 18 days ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#5 Updated by dkliban@redhat.com 18 days ago

  • Sprint/Milestone set to 3.16.0

#6 Updated by pulpbot 18 days ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF