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

docs: add documentation on the list of Cluster and Service Configuration #2291

Conversation

Ebaneck
Copy link
Contributor

@Ebaneck Ebaneck commented Mar 6, 2020

Component:

'docs'

Context:

See #2264

Summary:

Document the complete list of deployed cluster and service configurations

Acceptance criteria:


Closes: #2264

@Ebaneck Ebaneck requested review from lucieleonard and a team March 6, 2020 10:20
@bert-e
Copy link
Contributor

bert-e commented Mar 6, 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 Mar 6, 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 Mar 6, 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:

@Ebaneck Ebaneck force-pushed the feature/2264-provide-documentation-on-list-of-cluster-service-configuration branch from bf2bede to 944c5fa Compare March 6, 2020 10:26
@bert-e
Copy link
Contributor

bert-e commented Mar 6, 2020

History mismatch

Merge commit #bf2bedec611f13d971853d0d90343e86444c5e68 on the integration branch
w/2.6/feature/2264-provide-documentation-on-list-of-cluster-service-configuration is merging a branch which is neither the current
branch feature/2264-provide-documentation-on-list-of-cluster-service-configuration nor the development branch
development/2.6.

It is likely due to a rebase of the branch feature/2264-provide-documentation-on-list-of-cluster-service-configuration 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.

Copy link
Contributor

@lucieleonard lucieleonard left a comment

Choose a reason for hiding this comment

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

Overall comment:
I would get rid of the titles inside, and the introduction (does not really provide information).
I would use what's written under "Managing Cluster and Services Configurations" as the topic intro.
And then, you present the table of parameters.
It would give:

Main title
<text on managing parameters/configuration>

@Ebaneck Ebaneck requested a review from thomasdanan March 6, 2020 15:27
@Ebaneck Ebaneck force-pushed the feature/2264-provide-documentation-on-list-of-cluster-service-configuration branch 4 times, most recently from e990e26 to 0abe961 Compare March 9, 2020 16:25
@Ebaneck Ebaneck requested a review from gdemonet March 9, 2020 17:12
@Ebaneck Ebaneck force-pushed the feature/2264-provide-documentation-on-list-of-cluster-service-configuration branch from 0abe961 to 594254f Compare March 10, 2020 08:46
@Ebaneck Ebaneck marked this pull request as ready for review March 11, 2020 15:08
docs/operation/cluster_and_service_configuration.rst Outdated Show resolved Hide resolved

root@bootstrap $ crictl exec -it \
$(crictl ps -q --label io.kubernetes.container.name=salt-master) bash

Copy link
Contributor

Choose a reason for hiding this comment

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

Why using crictl there and not kubectl ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think throughout the MetalK8s documentation, we have been using crictl to connect to the salt-master container. I think it is only fair that we stick to one for consistency


- Configuring LDAP
- Configuring Active Directory(AD)

Copy link
Contributor

Choose a reason for hiding this comment

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

Is it something that we can do from the GUI (create user, role ...) ?

Copy link
Contributor Author

@Ebaneck Ebaneck Mar 12, 2020

Choose a reason for hiding this comment

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

I am afraid no for now. cc @thomasdanan

Copy link
Contributor

Choose a reason for hiding this comment

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

@xaf-scality UI configuration is tracked with #1991


root@bootstrap $ crictl exec -it \
$(crictl ps -q --label io.kubernetes.container.name=salt-master) bash

Copy link
Contributor

Choose a reason for hiding this comment

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

same comment, why crictl and not kubectl ?

@Ebaneck Ebaneck force-pushed the feature/2264-provide-documentation-on-list-of-cluster-service-configuration branch from 44d8c44 to 2165ecf Compare March 13, 2020 01:15
@Ebaneck
Copy link
Contributor Author

Ebaneck commented Mar 13, 2020

/reset

@bert-e
Copy link
Contributor

bert-e commented Mar 13, 2020

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Mar 13, 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 Mar 13, 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:

thomasdanan
thomasdanan previously approved these changes Mar 13, 2020
@Ebaneck
Copy link
Contributor Author

Ebaneck commented Mar 13, 2020

/approve

@Ebaneck
Copy link
Contributor Author

Ebaneck commented Mar 16, 2020

/reset

@bert-e
Copy link
Contributor

bert-e commented Mar 16, 2020

Reset complete

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

The following options are set: approve

@scality scality deleted a comment from bert-e Mar 16, 2020
@scality scality deleted a comment from bert-e Mar 16, 2020
@bert-e
Copy link
Contributor

bert-e commented Mar 16, 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

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Mar 16, 2020

Build failed

The build for commit did not succeed in branch feature/2264-provide-documentation-on-list-of-cluster-service-configuration.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Mar 16, 2020

Build failed

The build for commit did not succeed in branch w/2.6/feature/2264-provide-documentation-on-list-of-cluster-service-configuration.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Mar 16, 2020

Build failed

The build for commit did not succeed in branch feature/2264-provide-documentation-on-list-of-cluster-service-configuration.

The following options are set: approve

@Ebaneck Ebaneck force-pushed the feature/2264-provide-documentation-on-list-of-cluster-service-configuration branch from 2165ecf to 75c3632 Compare March 17, 2020 13:47
@bert-e
Copy link
Contributor

bert-e commented Mar 17, 2020

History mismatch

Merge commit #2165ecfe7d741f40500c51cbeeaf22576b03dbca on the integration branch
w/2.6/feature/2264-provide-documentation-on-list-of-cluster-service-configuration is merging a branch which is neither the current
branch feature/2264-provide-documentation-on-list-of-cluster-service-configuration nor the development branch
development/2.6.

It is likely due to a rebase of the branch feature/2264-provide-documentation-on-list-of-cluster-service-configuration 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.

The following options are set: approve

@Ebaneck
Copy link
Contributor Author

Ebaneck commented Mar 17, 2020

/reset

@bert-e
Copy link
Contributor

bert-e commented Mar 17, 2020

Reset complete

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

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Mar 17, 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

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Mar 17, 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 options are set: approve

thomasdanan
thomasdanan previously approved these changes Mar 17, 2020
@bert-e
Copy link
Contributor

bert-e commented Mar 17, 2020

Build failed

The build for commit did not succeed in branch w/2.6/feature/2264-provide-documentation-on-list-of-cluster-service-configuration.

The following options are set: approve

@Ebaneck Ebaneck force-pushed the feature/2264-provide-documentation-on-list-of-cluster-service-configuration branch from 75c3632 to 1a694e9 Compare March 18, 2020 12:20
@bert-e
Copy link
Contributor

bert-e commented Mar 18, 2020

History mismatch

Merge commit #75c3632fc831f0a8075079f042f95deb08e0e391 on the integration branch
w/2.6/feature/2264-provide-documentation-on-list-of-cluster-service-configuration is merging a branch which is neither the current
branch feature/2264-provide-documentation-on-list-of-cluster-service-configuration nor the development branch
development/2.6.

It is likely due to a rebase of the branch feature/2264-provide-documentation-on-list-of-cluster-service-configuration 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.

The following options are set: approve

This PR adds doc on the list of available Cluster and Service
Configurations deployed by default in a MetalK8s cluster

Closes: #2264
@Ebaneck
Copy link
Contributor Author

Ebaneck commented Mar 18, 2020

/reset

@bert-e
Copy link
Contributor

bert-e commented Mar 18, 2020

Reset complete

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

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Mar 18, 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

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Mar 18, 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 options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Mar 18, 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 Mar 18, 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 7442b27 into development/2.5 Mar 18, 2020
@bert-e bert-e deleted the feature/2264-provide-documentation-on-list-of-cluster-service-configuration branch March 18, 2020 16:40
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.

6 participants