Closed jsafrane closed 1 year ago
@jsafrane: This pull request references Jira Issue OCPBUGS-14177, which is invalid:
Comment /jira refresh
to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jsafrane
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/jira refresh
@jsafrane: This pull request references Jira Issue OCPBUGS-14177, which is valid. The bug has been moved to the POST state.
No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.
We are about to add support for multiple vCenters in OCP. Should we update this PR to be somewhat future proof? Such as - another datacenter with same name can exist in different vcenter etc.
Do we know how multiple vCenter support would look like? Would we have multiple clients? I can make it more future proof, but I need to know how the API should look like:
func NewCheckCache( XXX /* what parameters can we expect here? */ ) VSphereCache
func GetDatastore(ctx context.Context, vCenter YYY, dcName, dsName string)
There is a risk that I design something that will need refactoring, because I get the API wrong.
@jsafrane: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
ci/prow/e2e-vsphere-csi-extended | e92669d220be470b7318ee1bb544980661390061 | link | false | /test e2e-vsphere-csi-extended |
ci/prow/e2e-vsphere-zones | e92669d220be470b7318ee1bb544980661390061 | link | false | /test e2e-vsphere-zones |
Full PR test history. Your PR dashboard.
/lgtm
@jsafrane: Jira Issue OCPBUGS-14177: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-14177 has been moved to the MODIFIED state.
The cache is fresh for each check run. It caches all datacenters that any check loaded + all their datastores, even though not all of them may be used by the checks.
I still need to figure our how to unit-test this.
@openshift/storage