Skip to content
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.

Commit

Permalink
Release 3.8.0
Browse files Browse the repository at this point in the history
[noissue]
  • Loading branch information
goosemania committed Oct 21, 2020
1 parent 642a6c8 commit f85794f
Show file tree
Hide file tree
Showing 11 changed files with 52 additions and 24 deletions.
1 change: 0 additions & 1 deletion CHANGES/7573.removal

This file was deleted.

1 change: 0 additions & 1 deletion CHANGES/7574.feature

This file was deleted.

1 change: 0 additions & 1 deletion CHANGES/7646.feature

This file was deleted.

2 changes: 0 additions & 2 deletions CHANGES/7662.feature

This file was deleted.

1 change: 0 additions & 1 deletion CHANGES/7667.feature

This file was deleted.

1 change: 0 additions & 1 deletion CHANGES/7667.removal

This file was deleted.

1 change: 0 additions & 1 deletion CHANGES/7709.misc

This file was deleted.

36 changes: 36 additions & 0 deletions docs/CHANGES.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,42 @@ Changelog

<!-- TOWNCRIER -->

3.8.0 (2020-10-21)
==================


Features
--------

- Compile and install the pulpcore-selinux policy on CentOS/RHEL/Fedora.
[#7574](https://pulp.plan.io/issues/7574)
- When installing from distro packages (`pulp_install_source==packages`), from a repo (`pulp_pkg_repo`), and upgrading them (`pulp_pkg_upgrade_all==true`), pulp_installer will now upgrade all the packages from the repo. This addresses any incorrect dependency declarations in the repo, which would cause pulp_installer to fail on collectstatic.
[#7646](https://pulp.plan.io/issues/7646)
- Allow one to customize webserver ports pulp will be listening on via `pulp_webserver_http_port`
(defaults to 80) and `pulp_webserver_https_port` (defaults to 443).
[#7662](https://pulp.plan.io/issues/7662)
- Start rq & gunicorn from the bash wrapper scripts provided by newer pulpcore 3.7 RPM packages, `/usr/libexec/pulpcore/{rq,gunicorn}`. These scripts enable pulp processes to transitioning to the Pulp SELinux context, rather than the generic rq/gunicorn context.
[#7667](https://pulp.plan.io/issues/7667)


Deprecations and Removals
-------------------------

- pulp_installer will no longer set SELinux to enabled, permissive and enforcing (casually referred to as "disabled") on CentOS/RHEL/Fedora.
[#7573](https://pulp.plan.io/issues/7573)
- pulp_installer no longer supports installing from older RPM packages that lack the wrapper scripts `/usr/libexec/pulpcore/{rq,gunicorn}`.
[#7667](https://pulp.plan.io/issues/7667)


Misc
----

- [#7709](https://pulp.plan.io/issues/7709)


----


3.7.1 (2020-09-30)
==================

Expand Down
28 changes: 14 additions & 14 deletions docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,9 @@ The Pulp 3 Ansible installer is a collection of Ansible roles that you can use t

Each Ansible role installs and configures a component of Pulp.

This version of the installer, 3.7.1, installs Pulp 3.7.1 specifically.
This version of the installer, 3.8.0, installs Pulp 3.8.0 specifically.

If run against an older version of Pulp 3, it will upgrade it to 3.7.1.
If run against an older version of Pulp 3, it will upgrade it to 3.8.0.

System Requirements
-------------------
Expand Down Expand Up @@ -93,18 +93,18 @@ Recommended Workflows for Pulpcore & Plugin Versioning
Initial installation:

1. Make sure you are running the latest version of the installer, which installs the latest version
of pulpcore (3.7.1).
of pulpcore (3.8.0).
1. Confirm that all the latest stable releases of your desired plugins are compatible with pulpcore
3.7.1, such as by reading the release announcement email thread for pulpcore 3.7.1, reading the
3.8.0, such as by reading the release announcement email thread for pulpcore 3.8.0, reading the
plugins README, or as a last resort, reading their `setup.py`.
1. Run `pulp_installer`.

Upgrading your installation:

1. Observe what is the latest version of `pulp_installer`, and what version of pulpcore it installed
(3.7.1).
(3.8.0).
1. Confirm that all the latest stable releases of **currently installed** plugins are compatible
with pulpcore 3.7.1, such as by reading the release announcement email thread for pulpcore 3.7.1,
with pulpcore 3.8.0, such as by reading the release announcement email thread for pulpcore 3.8.0,
reading the plugins README, or as a last resort, reading their setup.py.
1. If they are not all compatible yet, **wait** for the plugins to be updated for
compatibility.
Expand All @@ -116,27 +116,27 @@ reading the plugins README, or as a last resort, reading their setup.py.

Initial installation:

1. Observe the latest branch of `pulp_installer`, and what version of pulpcore it installs (3.7.1).
1. Observe the latest branch of `pulp_installer`, and what version of pulpcore it installs (3.8.0).
1. Confirm that all the latest stable releases of your desired plugins are compatible with pulpcore
3.7.1, such as by reading the release announcement email thread for pulpcore 3.7.1, reading the
3.8.0, such as by reading the release announcement email thread for pulpcore 3.8.0, reading the
plugins README, or as a last resort, reading their setup.py.
1. If they are not all compatible yet, try the last version of the installer that installs pulpcore
3.3.z . Then confirm that there exist stable releases of your desired plugins that are compatible
with pulpcore 3.3.z. If there are none, try pulpcore 3.2.z, and repeate.
3.7.z . Then confirm that there exist stable releases of your desired plugins that are compatible
with pulpcore 3.7.z. If there are none, try pulpcore 3.6.z, and repeat.
1. Once a compatible pulpcore version is found, specify `version` for each plugin under
`pulp_install_plugins`.
1. Run `pulp_installer`

Upgrading your install:

1. Observe what the latest version of `pulp_installer` is, and what version of pulpcore it installed
(3.7.1). (Even if there is no update, you can still upgrade your plugins.)
(3.8.0). (Even if there is no update, you can still upgrade your plugins.)
1. Confirm that all the latest stable releases of **currently installed** plugins are compatible
with pulpcore 3.7.1, such as by reading the release announcement email thread for pulpcore 3.7.1,
with pulpcore 3.8.0, such as by reading the release announcement email thread for pulpcore 3.8.0,
reading the plugins README, or as a last resort, reading their setup.py.
1. If they are not all compatible yet, try the last version of the installer that installs pulpcore
3.3.z . Then confirm that there exist stable releases of your desired plugins that are compatible
with pulpcore 3.3.z. If there are none, try pulpcore 3.2.z, and repeat.
3.7.z . Then confirm that there exist stable releases of your desired plugins that are compatible
with pulpcore 3.7.z. If there are none, try pulpcore 3.6.z, and repeat.
1. Once a compatible pulpcore version is found, **revise** `version` for each plugin under
`pulp_install_plugins`. Do not specify `upgrade` as well.
1. Upgrade `pulp_installer` to the latest version (if there is a new version.)
Expand Down
2 changes: 1 addition & 1 deletion galaxy.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ namespace: pulp
name: pulp_installer

# The version of the collection. Must be compatible with semantic versioning
version: 3.7.1
version: 3.8.0

# The path to the Markdown (.md) readme file. This path is relative to the root of the collection
readme: README.md
Expand Down
2 changes: 1 addition & 1 deletion roles/pulp_common/defaults/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ pulp_upgrade: false
# they are confident that this version of pulp_installer is compatible with
# pulp_version.
# Ignored if pulp_source_dir is set
pulp_version: "3.7.1"
pulp_version: "3.8.0"
pulp_user: pulp
pulp_user_id:
pulp_group: pulp
Expand Down

0 comments on commit f85794f

Please sign in to comment.