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

salt: use all etcd servers as apiserver backends #2181

Merged
merged 1 commit into from
Jan 24, 2020

Conversation

alexandre-allard
Copy link
Contributor

@alexandre-allard alexandre-allard commented Jan 10, 2020

Component: salt, apiserver

Context:
Until now, we only use the local etcd as the apiserver backend

Summary:
Define all clients URLs as etcd servers for API server backend, this way, if the local etcd is
down, the API server is still able to answer.

Acceptance criteria: Green build


Closes: #2080

@alexandre-allard alexandre-allard requested a review from a team as a code owner January 10, 2020 09:37
@bert-e
Copy link
Contributor

bert-e commented Jan 10, 2020

Hello alexandre-allard-scality,

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 Jan 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

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 Jan 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:

@alexandre-allard alexandre-allard force-pushed the bugfix/2080-kas-on-local-etcd branch from 1234af4 to e31f53b Compare January 10, 2020 10:13
@bert-e
Copy link
Contributor

bert-e commented Jan 10, 2020

History mismatch

Merge commit #1234af47f338186079d504f618b96f782ae202f8 on the integration branch
w/2.5/bugfix/2080-kas-on-local-etcd is merging a branch which is neither the current
branch bugfix/2080-kas-on-local-etcd nor the development branch
development/2.5.

It is likely due to a rebase of the branch bugfix/2080-kas-on-local-etcd 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.

@alexandre-allard alexandre-allard force-pushed the bugfix/2080-kas-on-local-etcd branch from e31f53b to f7b8c9c Compare January 10, 2020 10:15
@alexandre-allard
Copy link
Contributor Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Jan 10, 2020

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Jan 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

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 Jan 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:

@alexandre-allard alexandre-allard force-pushed the bugfix/2080-kas-on-local-etcd branch from f7b8c9c to 20cfe2b Compare January 10, 2020 11:14
@bert-e
Copy link
Contributor

bert-e commented Jan 10, 2020

History mismatch

Merge commit #f7b8c9c6b8741bae45e2dde49c54382b63964e29 on the integration branch
w/2.5/bugfix/2080-kas-on-local-etcd is merging a branch which is neither the current
branch bugfix/2080-kas-on-local-etcd nor the development branch
development/2.5.

It is likely due to a rebase of the branch bugfix/2080-kas-on-local-etcd 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.

@alexandre-allard
Copy link
Contributor Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Jan 10, 2020

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Jan 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

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 Jan 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:

@alexandre-allard alexandre-allard force-pushed the bugfix/2080-kas-on-local-etcd branch from 20cfe2b to ca15d95 Compare January 20, 2020 09:06
@bert-e
Copy link
Contributor

bert-e commented Jan 20, 2020

History mismatch

Merge commit #20cfe2b5101a348097c70d1e9bdd470e37abfbed on the integration branch
w/2.5/bugfix/2080-kas-on-local-etcd is merging a branch which is neither the current
branch bugfix/2080-kas-on-local-etcd nor the development branch
development/2.5.

It is likely due to a rebase of the branch bugfix/2080-kas-on-local-etcd 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.

@alexandre-allard alexandre-allard force-pushed the bugfix/2080-kas-on-local-etcd branch from ca15d95 to fb17a59 Compare January 20, 2020 10:32
TeddyAndrieux
TeddyAndrieux previously approved these changes Jan 20, 2020
Copy link
Collaborator

@TeddyAndrieux TeddyAndrieux left a comment

Choose a reason for hiding this comment

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

LGTM

@alexandre-allard
Copy link
Contributor Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Jan 20, 2020

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Jan 20, 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

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 Jan 20, 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:

Define all clients URLs as etcd servers for API
server backend, this way, if the local etcd is
down, the API server is still able to answer.
Set the local etcd, if any, as the first member
in the list.

Refs: #2080
@bert-e
Copy link
Contributor

bert-e commented Jan 23, 2020

History mismatch

Merge commit #fb17a59dda748509be49b442f1932b3f8d52ba22 on the integration branch
w/2.5/bugfix/2080-kas-on-local-etcd is merging a branch which is neither the current
branch bugfix/2080-kas-on-local-etcd nor the development branch
development/2.5.

It is likely due to a rebase of the branch bugfix/2080-kas-on-local-etcd 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.

@alexandre-allard
Copy link
Contributor Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Jan 23, 2020

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Jan 23, 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

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 Jan 23, 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:

@alexandre-allard
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Jan 23, 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

Comment on lines +24 to +29
{%- set etcd_servers = [] %}
{#- NOTE: Filter out members with empty name as they are not started yet. #}
{%- for member in pillar.metalk8s.etcd.members | selectattr('name') %}
{%- do etcd_servers.extend(member['client_urls']) %}
{%- endfor %}
{%- set etcd_servers = etcd_servers | sort %}
Copy link
Contributor

Choose a reason for hiding this comment

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

If you like Jinja tricks:

{%- set etcd_servers = pillar.metalk8s.etcd.members
                       | selectattr('name')
                       | sum(attribute='client_urls', start=[])
                       | sort %}

@bert-e
Copy link
Contributor

bert-e commented Jan 23, 2020

Build failed

The build for commit did not succeed in branch bugfix/2080-kas-on-local-etcd.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Jan 23, 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.4

  • ✔️ development/2.5

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

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 Jan 24, 2020

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

  • ✔️ development/2.4

  • ✔️ development/2.5

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

Please check the status of the associated issue None.

Goodbye alexandre-allard-scality.

@bert-e bert-e merged commit bb84b6a into development/2.4 Jan 24, 2020
@bert-e bert-e deleted the bugfix/2080-kas-on-local-etcd branch January 24, 2020 09:13
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.

kube-apiserver instances only rely on a local etcd member
7 participants