Bug #10533
As a developer, I want to move to move puppet-foreman_proxy to the top level of Katello installer
Related issues
Associated revisions
refs #10533 - decouple puppet-foreman_proxy from puppet-capsule
The changes in this commit are an initial step towards enabling the capsule
to be deployed as a kafo 'scenario' using the foreman-installer.
The following is an example of using the scenario-based installer to
install a capsule using this module:
foreman-installer --scenario capsule \
--capsule-parent-fqdn "katello.example.com"\
--foreman-proxy-register-in-foreman "true"\
--foreman-proxy-registered-proxy-url "https://capsule.example.com:9090"\
--foreman-proxy-oauth-consumer-key "QSJ2qCGV3zWyohCJfKxQBDCCjceBiTMy"\
--foreman-proxy-oauth-consumer-secret "DGKBJjXWfkyroiyDHNhYAFn9uTnUcJxa"\
--foreman-proxy-foreman-base-url "https://katello.example.com"\
--foreman-proxy-trusted-hosts "katello.example.com"\
--foreman-proxy-trusted-hosts "capsule.example.com"\
--capsule-pulp-oauth-secret "bQ5zUPVd2qVDY987D4VtD6Va9pDj4Y7J"\
--capsule-certs-tar "~/capsule.example.com-certs.tar"\
--capsule-puppet "true"\
--capsule-puppetca "true"\
--capsule-pulp "true"
The following is an example of using the existing capsule-installer to
install a capsule using this module:
capsule-installer --register-in-foreman "true"\
--registered-proxy-url "https://capsule.example.com:9090"\
--oauth-consumer-key "pvUutwvPU3Rni5RWqisL6Tx4fAF5yDSa"\
--oauth-consumer-secret "JTGnd3fx6GB4uki5LtNPFU6cCSq9NrFk"\
--foreman-base-url "https://katello.example.com"\
--trusted-hosts "katello.example.com"\
--trusted-hosts "capsule.example.com"\
--parent-fqdn "katello.example.com"\
--pulp-oauth-secret "3HNmounKP6mbQYthkvkw2GXV5toxeFsu"\
--certs-tar "~/capsule.example.com-certs.tar"\
--puppet "true"\
--puppetca "true"\
--enable-foreman-proxy-plugin-pulp\
--enabled "false"\
--pulpnode-enabled "true"
Note: In order to enable pulp and leverage parameters provided by the puppet-foreman_proxy,
the following arguments are now used : --enable-foreman-proxy-plugin-pulp (to enable the pulp plugin),
--enabled (do not configure as a pulp master), --pulpnode-enabled (configure as a pulp node)
refs #10533 - decouple puppet-foreman_proxy from puppet-capsule
The changes in this commit are an initial step towards enabling the capsule
to be deployed as a kafo 'scenario' using the foreman-installer.
The following is an example of using the scenario-based installer to
install a capsule using this module:
foreman-installer --scenario capsule \
--capsule-parent-fqdn "katello.example.com"\
--foreman-proxy-register-in-foreman "true"\
--foreman-proxy-registered-proxy-url "https://capsule.example.com:9090"\
--foreman-proxy-oauth-consumer-key "QSJ2qCGV3zWyohCJfKxQBDCCjceBiTMy"\
--foreman-proxy-oauth-consumer-secret "DGKBJjXWfkyroiyDHNhYAFn9uTnUcJxa"\
--foreman-proxy-foreman-base-url "https://katello.example.com"\
--foreman-proxy-trusted-hosts "katello.example.com"\
--foreman-proxy-trusted-hosts "capsule.example.com"\
--capsule-pulp-oauth-secret "bQ5zUPVd2qVDY987D4VtD6Va9pDj4Y7J"\
--capsule-certs-tar "~/capsule.example.com-certs.tar"\
--capsule-puppet "true"\
--capsule-puppetca "true"\
--capsule-pulp "true"
The following is an example of using the existing capsule-installer to
install a capsule using this module:
capsule-installer --register-in-foreman "true"\
--registered-proxy-url "https://capsule.example.com:9090"\
--oauth-consumer-key "pvUutwvPU3Rni5RWqisL6Tx4fAF5yDSa"\
--oauth-consumer-secret "JTGnd3fx6GB4uki5LtNPFU6cCSq9NrFk"\
--foreman-base-url "https://katello.example.com"\
--trusted-hosts "katello.example.com"\
--trusted-hosts "capsule.example.com"\
--parent-fqdn "katello.example.com"\
--pulp-oauth-secret "3HNmounKP6mbQYthkvkw2GXV5toxeFsu"\
--certs-tar "~/capsule.example.com-certs.tar"\
--puppet "true"\
--puppetca "true"\
--enable-foreman-proxy-plugin-pulp\
--enabled "false"\
--pulpnode-enabled "true"
Note: In order to enable pulp and leverage parameters provided by the puppet-foreman_proxy,
the following arguments are now used : --enable-foreman-proxy-plugin-pulp (to enable the pulp plugin),
--enabled (do not configure as a pulp master), --pulpnode-enabled (configure as a pulp node)
Fixes #10533 - add migrations to decouple foreman_proxy from capsule
Refs #10533: Katello scenario
History
#1
Updated by Stephen Benjamin about 7 years ago
- Blocks Tracker #7605: As a Foreman user, I would like to be able to add Katello later to an existing Foreman installation added
#2
Updated by Eric Helms over 6 years ago
- Legacy Backlogs Release (now unused) set to 86
#3
Updated by Brad Buckingham over 6 years ago
- Assignee set to Brad Buckingham
#4
Updated by Brad Buckingham over 6 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset katello-installer|6d388082ceb0127e88489de94379bc0fbaff1814.
#5
Updated by The Foreman Bot over 6 years ago
- Pull request https://github.com/Katello/katello-installer/pull/290 added
#6
Updated by The Foreman Bot over 6 years ago
- Pull request https://github.com/Katello/katello-installer/pull/291 added
#7
Updated by The Foreman Bot over 6 years ago
- Pull request https://github.com/Katello/katello-packaging/pull/169 added
fixes #10533 - update answers and config for decoupling of puppet-foreman_proxy from puppet-capsule
This commit contains some initial changes to support the puppet-capsule
changes that decouple puppet-foreman_proxy from the puppet-capsule.
(Ref: https://github.com/Katello/puppet-capsule/pull/64)
Below are a couple of example installs using this configuration:
katello-installer
capsule-installer --register-in-foreman "true"\
--registered-proxy-url "https://capsule.example.com:9090"\
--oauth-consumer-key "pvUutwvPU3Rni5RWqisL6Tx4fAF5yDSa"\
--oauth-consumer-secret "JTGnd3fx6GB4uki5LtNPFU6cCSq9NrFk"\
--foreman-base-url "https://katello.example.com"\
--trusted-hosts "katello.example.com"\
--trusted-hosts "capsule.example.com"\
--parent-fqdn "katello.example.com"\
--pulp-oauth-secret "3HNmounKP6mbQYthkvkw2GXV5toxeFsu"\
--certs-tar "~/capsule.example.com-certs.tar"\
--puppet "true"\
--puppetca "true"\
--enable-foreman-proxy-plugin-pulp\
--enabled "false"\
--pulpnode-enabled "true"