Skip to content

Conversation

@mburke5678
Copy link
Contributor

@mburke5678 mburke5678 commented Jan 25, 2018

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 25, 2018
@mburke5678
Copy link
Contributor Author

@tripledes I am not clear on the openshift_cockpit_deployer_prefix setting. Can the prefix be any test string or does it point to an existing image and path?

@mburke5678
Copy link
Contributor Author

@tripledes PTAL

@tripledes
Copy link

@mburke5678 LGTM, @jtudelag works?

Copy link

@jtudelag jtudelag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mburke5678 @tripledes Please review ;)


For example:
----
openshift_cockpit_deployer_prefix='registry.example.com/openshift'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This example does not match the variable format <registry>/<namespace>/<cockpit-image-name>. The <cockpit-image-name> is missing... https://github.com/openshift/openshift-docs/pull/7331/files#diff-fe94157edddadf88425cf07b556a00a3R794

Shouldn't it be openshift_cockpit_deployer_prefix='registry.example.com/openshift/console instead?

@tripledes @mburke5678 please review!!

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on https://github.com/openshift/openshift-ansible/blob/release-3.6/inventory/byo/hosts.ose.example#L416-L423 I'd say what @mburke5678 is correct. @mburke5678 could you please ping anyone from openshift-ansible to confirm?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sdodson Can you help? We are trying to determine an appropriate example for the openshift_cockpit_deployer_prefix parameter.
openshift_cockpit_deployer_prefix='registry.example.com/openshift'
openshift_cockpit_deployer_prefix='registry.example.com/openshift/console'
Other?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If your image is at registry.example.com/openshift3/registry-console then it should be openshift_cockpit_deployer_prefix='registry.example.com/openshift3/' as registry-console is appended on to the end, though that too can be modified via openshift_cockpit_deployer_basename

@mburke5678
Copy link
Contributor Author

mburke5678 commented Jan 31, 2018

@jianlinliu PTAL


----
openshift_cockpit_deployer_prefix=<registry-name>/<namespace>/
openshift_cockpit_deployer_basename=<my-console>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is targeted for 3.7, right? If yes, then it is okay. "openshift_cockpit_deployer_basename" is not supported yet in 3.6 openshift-ansible code yet.

version 1.4.1, enter:
----
openshift_cockpit_deployer_prefix='registry.example.com/openshift3/'
openshift_cockpit_deployer_basename=`registry-console`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"registry-console" is the default value, in this example, it is better to change it to other than the default name

@mburke5678
Copy link
Contributor Author

mburke5678 commented Feb 5, 2018

@tripledes Can you comment on @jianlinliu comment about which version that openshift_cockpit_deployer_basename was added? ^^
I removed openshift_cockpit_deployer_basename from this PR and do a follow-up to add the parameter to 3.7+, if needed.
See: #7578

@mburke5678 mburke5678 force-pushed the BZ-1518204 branch 2 times, most recently from 9ac309c to 43fe698 Compare February 5, 2018 17:33
@mburke5678
Copy link
Contributor Author

mburke5678 commented Feb 5, 2018

[rev_history]
|xref:../install_config/install/advanced_install.adoc#install-config-install-advanced-install[Installing a Cluster -> Advanced Installation]
|Added information on xref:../install_config/install/advanced_install.adoc#advanced-install-configuring-registry-console[using a Cockpit registry console image other than the default].
%

@mburke5678
Copy link
Contributor Author

@openshift/team-documentation PTAL as we settle on versioning.

@jianlinliu
Copy link

LGTM.

@mburke5678
Copy link
Contributor Author

@openshift/team-documentation PTAL

@ahardin-rh
Copy link
Contributor

@mburke LGTM. In the revision history, you just need to update the first line to show:
[Installing a Cluster -> Advanced Installation] 🎆

@ahardin-rh ahardin-rh added the peer-review-done Signifies that the peer review team has reviewed this PR label Feb 7, 2018
@mburke5678 mburke5678 merged commit 91cf06f into openshift:master Feb 7, 2018
mburke5678 added a commit to mburke5678/openshift-docs that referenced this pull request Feb 7, 2018
mburke5678 added a commit to mburke5678/openshift-docs that referenced this pull request Feb 7, 2018
mburke5678 added a commit to mburke5678/openshift-docs that referenced this pull request Feb 7, 2018
mburke5678 added a commit to mburke5678/openshift-docs that referenced this pull request Feb 7, 2018
@mburke5678 mburke5678 deleted the BZ-1518204 branch February 15, 2018 20:23
openshift_docker_additional_registries=example.com
----

[[advanced-install-configuring-registry-location]]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mburke5678 this is a duplicate id, which seems to be copied from the previous section. I have changed it to advanced-install-configuring-registry-console.

@vikram-redhat
Copy link
Contributor

@mburke5678 - the rev history link to the section id was not correct. Instead of configuring-a-registry-location it should have been advanced-install-configuring-registry-console.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-3.6 branch/enterprise-3.7 branch/enterprise-3.9 peer-review-done Signifies that the peer review team has reviewed this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants