Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: update documentation with default login details for MetalK8s UI & Grafana service #2377

Conversation

Ebaneck
Copy link
Contributor

@Ebaneck Ebaneck commented Apr 7, 2020

Component:

'docs'

Context:

See #2351

Summary:

This PR adds the following changes:

  • Adds and update the default login credentials for both the MetalK8s GUI and Grafana Service
  • Introduces a new section in CSC that deals with changing passwords for local static user
  • Removes outdated information in the Account administration page.

The following was not taken care of:

Acceptance criteria:


Closes: #2351
Closes: #2352

@Ebaneck Ebaneck requested review from thomasdanan and a team April 7, 2020 09:42
@bert-e
Copy link
Contributor

bert-e commented Apr 7, 2020

Hello ebaneck,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Apr 7, 2020

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/1.0
  • development/1.1
  • development/1.2
  • development/1.3
  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Apr 7, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

docs/operation/account_administration.rst Outdated Show resolved Hide resolved
docs/operation/cluster_and_service_configuration.rst Outdated Show resolved Hide resolved
docs/operation/cluster_and_service_configuration.rst Outdated Show resolved Hide resolved
docs/operation/cluster_and_service_configuration.rst Outdated Show resolved Hide resolved
docs/operation/cluster_and_service_configuration.rst Outdated Show resolved Hide resolved
@bert-e
Copy link
Contributor

bert-e commented Apr 7, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following reviewers are expecting changes from the author, or must review again:

@Ebaneck Ebaneck force-pushed the bugfix/2351-update-documentation-with-default-login-details branch from 15a7eaa to ebe645a Compare April 8, 2020 11:15
@bert-e
Copy link
Contributor

bert-e commented Apr 8, 2020

History mismatch

Merge commit #2175d306ce6bcf4a080999ef774e555c1fff7cde on the integration branch
w/2.6/bugfix/2351-update-documentation-with-default-login-details is merging a branch which is neither the current
branch bugfix/2351-update-documentation-with-default-login-details nor the development branch
development/2.6.

It is likely due to a rebase of the branch bugfix/2351-update-documentation-with-default-login-details and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

@Ebaneck Ebaneck requested a review from gdemonet April 8, 2020 11:17
@Ebaneck Ebaneck force-pushed the bugfix/2351-update-documentation-with-default-login-details branch from ebe645a to 0f6ff2a Compare April 8, 2020 17:57
@Ebaneck Ebaneck requested a review from NicolasT April 8, 2020 17:59
@Ebaneck Ebaneck force-pushed the bugfix/2351-update-documentation-with-default-login-details branch from 0f6ff2a to 109ea97 Compare April 9, 2020 14:28
docs/installation/services.rst Show resolved Hide resolved

#. Now, roll out the new updates for Grafana:
The MetalK8s UI and the Grafana service instance make use of the same local
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe ask @lucieleonard to review the sentence

docs/operation/cluster_and_service_configuration.rst Outdated Show resolved Hide resolved
@Ebaneck Ebaneck force-pushed the bugfix/2351-update-documentation-with-default-login-details branch from 109ea97 to 57157e3 Compare April 9, 2020 16:17
@Ebaneck Ebaneck requested a review from lucieleonard April 9, 2020 16:33
@Ebaneck Ebaneck force-pushed the bugfix/2351-update-documentation-with-default-login-details branch from 57157e3 to 55d0345 Compare April 9, 2020 16:56
Copy link
Contributor

@gdemonet gdemonet left a comment

Choose a reason for hiding this comment

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

Some more changes in the doc, but it's looking much better, thanks a lot!

docs/operation/account_administration.rst Outdated Show resolved Hide resolved
docs/operation/account_administration.rst Outdated Show resolved Hide resolved
docs/operation/account_administration.rst Outdated Show resolved Hide resolved
docs/operation/account_administration.rst Outdated Show resolved Hide resolved
docs/operation/account_administration.rst Outdated Show resolved Hide resolved
docs/operation/cluster_and_service_configuration.rst Outdated Show resolved Hide resolved
docs/operation/cluster_and_service_configuration.rst Outdated Show resolved Hide resolved
docs/operation/cluster_and_service_configuration.rst Outdated Show resolved Hide resolved
@Ebaneck Ebaneck force-pushed the bugfix/2351-update-documentation-with-default-login-details branch from 55d0345 to 1c5721f Compare April 10, 2020 08:52
@Ebaneck Ebaneck requested review from gdemonet and thomasdanan April 10, 2020 08:52
@Ebaneck
Copy link
Contributor Author

Ebaneck commented Apr 10, 2020

/reset

@bert-e
Copy link
Contributor

bert-e commented Apr 10, 2020

Reset complete

I have successfully deleted this pull request's integration branches.

@bert-e
Copy link
Contributor

bert-e commented Apr 10, 2020

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/1.0
  • development/1.1
  • development/1.2
  • development/1.3
  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Apr 10, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following reviewers are expecting changes from the author, or must review again:

Ebaneck added 3 commits April 10, 2020 11:15
We need `htpasswd` to generate password hashes for the Dex static
user.
The htpasswd is provided by httpd-tools on redhat based os

Fixes: #2352
@Ebaneck Ebaneck force-pushed the bugfix/2351-update-documentation-with-default-login-details branch from 1c5721f to f4b5268 Compare April 10, 2020 09:17
@Ebaneck
Copy link
Contributor Author

Ebaneck commented Apr 10, 2020

/reset

@bert-e
Copy link
Contributor

bert-e commented Apr 10, 2020

Reset complete

I have successfully deleted this pull request's integration branches.

@scality scality deleted a comment from bert-e Apr 10, 2020
@bert-e
Copy link
Contributor

bert-e commented Apr 10, 2020

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/1.0
  • development/1.1
  • development/1.2
  • development/1.3
  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Apr 10, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following reviewers are expecting changes from the author, or must review again:

@Ebaneck
Copy link
Contributor Author

Ebaneck commented Apr 10, 2020

/approve

@bert-e
Copy link
Contributor

bert-e commented Apr 10, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following reviewers are expecting changes from the author, or must review again:

The following options are set: approve

Copy link
Contributor

@gdemonet gdemonet left a comment

Choose a reason for hiding this comment

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

👌 :shipit:

@bert-e
Copy link
Contributor

bert-e commented Apr 10, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following reviewers are expecting changes from the author, or must review again:

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Apr 10, 2020

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/2.5

  • ✔️ development/2.6

The following branches will NOT be impacted:

  • development/1.0
  • development/1.1
  • development/1.2
  • development/1.3
  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Apr 10, 2020

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/2.5

  • ✔️ development/2.6

The following branches have NOT changed:

  • development/1.0
  • development/1.1
  • development/1.2
  • development/1.3
  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4

Please check the status of the associated issue None.

Goodbye ebaneck.

@bert-e bert-e merged commit 98e4269 into development/2.5 Apr 10, 2020
@bert-e bert-e deleted the bugfix/2351-update-documentation-with-default-login-details branch April 10, 2020 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants