Skip to content

Add openstack ussuri into support list #586

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

Merged
merged 1 commit into from
Nov 19, 2020

Conversation

jichenjc
Copy link
Contributor

@jichenjc jichenjc commented Jul 13, 2020

What this PR does / why we need it:

Add openstack ussuri into support list (tested)

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

  1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:


@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jichenjc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 13, 2020
@theopenlab-ci
Copy link

theopenlab-ci bot commented Jul 13, 2020

Build failed.

@hidekazuna
Copy link
Contributor

@jichenjc Did you test both HA and non-HA?

@jichenjc
Copy link
Contributor Author

ah... good point, I think you are talking about LB case, correct?
I tested non-LB case today
I can test LB case or have you tested that?

@hidekazuna
Copy link
Contributor

@jichenjc

ah... good point, I think you are talking about LB case, correct?

Yes, I am.

I tested non-LB case today
I can test LB case or have you tested that?

Unfortunately I only have stable Stein environment and do not have new machine.

@jichenjc
Copy link
Contributor Author

@jichenjc

ah... good point, I think you are talking about LB case, correct?

Yes, I am.

I tested non-LB case today
I can test LB case or have you tested that?

Unfortunately I only have stable Stein environment and do not have new machine.

ok, I have to create LB env (I only have non-LB env now)

@hidekazuna
Copy link
Contributor

@jichenjc Did you test lb version?

@jichenjc
Copy link
Contributor Author

@hidekazuna not yet, run out of my time ,if you can help to verify , then it will be helpful
or I will do it in a few days

@hidekazuna
Copy link
Contributor

@hidekazuna not yet, run out of my time ,if you can help to verify , then it will be helpful
or I will do it in a few days

@jichenjc It's OK, I can wait.

@jichenjc
Copy link
Contributor Author

recheck

@jichenjc
Copy link
Contributor Author

jichenjc commented Aug 17, 2020

@hidekazuna we by default use U release in CI, so I think we can merge this?

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 17, 2020

Build failed.

@jichenjc
Copy link
Contributor Author

recheck

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 17, 2020

Build failed.

@hidekazuna
Copy link
Contributor

@hidekazuna we by default use U release in CI, so I think we can merge this?

@jichenjc If you tested HA version, we can merge this PR.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 15, 2020
@sbueringer
Copy link
Member

@jichenjc any news? Is this PR still active?

@jichenjc
Copy link
Contributor Author

yes, but I am lack of time recently, if you did please help .. thanks @sbueringer

@sbueringer
Copy link
Member

sbueringer commented Nov 17, 2020

@jichenjc Sorry I don't have OpenStack Ussuri available, just wanted to ask.
I'm also not entirely sure what exactly we're achieving with our "supported OpenStack versions list".

Almost none of them are continuously tested by us (on every release). So basically it comes down to a handful of versions which we
really know that work, because we're using them all the time. (I assume the actual list is not really in sync with the documented one)

@jichenjc
Copy link
Contributor Author

@sbueringer I agree all you mentioned here, how about let's just say something like
'should work but not tested ...'

@theopenlab-ci
Copy link

theopenlab-ci bot commented Nov 18, 2020

Build succeeded.

@sbueringer
Copy link
Member

@sbueringer I agree all you mentioned here, how about let's just say something like
'should work but not tested ...'

sounds good to me

README.md Outdated
| OpenStack Provider v1alpha2 (v0.2) | + | ✓ | + | ✓ | + | + | + |
| OpenStack Provider v1alpha3 (v0.3) | + | + | + | ✓ | ✓ | ✓ | ✓ |

**NOTE:** : There is no formal CI test for specific OpenStack version, the development team has a CI running on latest OpenStack devstack and that covers most of `✓` at above table.
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

CI tests only non HA version. Some OpenStack versions for HA are tested manually.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

understand .. thanks for point out
so we need some manual test but actually CI is preferred

let me check how we can do and submit some proposal for review

Copy link
Contributor

@hidekazuna hidekazuna Nov 18, 2020

Choose a reason for hiding this comment

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

Ideally using CAPI e2e test framework is the best to test HA. I tried but still in progress. I confirmed it tests HA.

So in this PR, I propose to remove Victoria, and update NOTE:
The development team has a CI using non HA template running on latest OpenStack devstack and that covers most of at above table. Some versions are tested against HA template.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Nov 19, 2020

Build failed.

@jichenjc
Copy link
Contributor Author

recheck

@hidekazuna
Copy link
Contributor

@jichenjc We can add Victoria now!!

README.md Outdated
| OpenStack Provider v1alpha2 (v0.2) | + | ✓ | + | ✓ | + | + | + |
| OpenStack Provider v1alpha3 (v0.3) | + | + | + | ✓ | ✓ | ✓ | ✓ |

**NOTE:** : The development team has a CI using [non HA template](https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/templates/cluster-template-without-lb.yaml) running on latest OpenStack devstack and that covers most of ✓ at above table. Some versions are tested against [HA template](https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/templates/cluster-template.yaml).
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ok, will do

@theopenlab-ci
Copy link

theopenlab-ci bot commented Nov 19, 2020

Build succeeded.

@hidekazuna
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 19, 2020
@k8s-ci-robot k8s-ci-robot merged commit d6a1684 into kubernetes-sigs:master Nov 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants