coordination #117583
openBCI Testing on IBM Hyper Protect Platform (HPVS)
0%
Description
We are asked to test our BCI containers in the IBM cloud. This is the coordination ticket for all related tickets for solving this.
- Jira ticket: https://jira.suse.com/browse/PED-2263
- Validation proposal: https://confluence.suse.com/display/qasle/BCI+on+IBM+Cloud+validation+proposal
- Testing done by Michael Frisseneger: https://confluence.suse.com/display/ENGCTNRSTORY/Confidential+computing+with+SLE+BCI+and+IBM+Hyper+Protect+Virtual+Servers
- Some other page from Felix: https://confluence.suse.com/display/~ph03nix/IBM+Cloud
Updated by jlausuch over 1 year ago
We are still waiting for an account. As soon as we get some more info, we'll be able to create the sub-tasks for this.
Updated by jlausuch over 1 year ago
- Subject changed from [epic] IBM cloud to IBM cloud
Updated by jlausuch about 1 year ago
- Status changed from Blocked to Rejected
As a matter of a backlog cleanup, I am rejecting this ticket as there has been no feedback about this in the last months from management side. If this topic comes again, I will re-open.
Updated by jlausuch 1 day ago
Reopening the ticket. The task has been asked by PM (François X.), cause there is customer interest about this.
The test is described in this confluence page: https://confluence.suse.com/display/qasle/BCI+on+IBM+Cloud+validation+proposal
We don't need to run this as part of ALL BCI Containers validation, we can limit it to the NodeJS container.
Updated by ph03nix 39 minutes ago
Kickoff meeting 03.07.2024:
- The IBM cloud has high environment complexity, because it does not allow you to directly interact with the container engine
- Test complexity requires us to define only a limited test scope - To be clarified: Which containers to test? (Suggestion: BCI-Base only)
- The environment has been sporadic, the existing test environment stopped working after some weeks of testing
- Action item: Determine, if we can obtain the container logs (this was not possible with the free account)
- To clarify: Only test released images. We cannot block our release pipeline for IBM images, due to the test environment (too flanky due to high complexity, not easy to interact)
Updated by ph03nix 36 minutes ago
ph03nix wrote in #note-8:
Kickoff meeting 03.07.2024:
- The IBM cloud has high environment complexity, because it does not allow you to directly interact with the container engine
- Test complexity requires us to define only a limited test scope - To be clarified: Which containers to test? (Suggestion: BCI-Base only)
- The environment has been sporadic, the existing test environment stopped working after some weeks of testing
- Action item: Determine, if we can obtain the container logs (this was not possible with the free account)
- To clarify: Only test released images. We cannot block our release pipeline for IBM images, due to the test environment (too flanky due to high complexity, not easy to interact)
@jlausuch question to clarify:
- We can only test a minimal test of BCI containers due to the high text complexity. We cannot test all containers. Which ones do we need to test? Our suggestion are the following containers:
bci-basebci-busybox
We think because all other containers rely on them, this is a good start. Plus, we already test all containers internally on s390x, so that a lifeness-test of the BCI containers provides us with sufficient test coverage to be confident, that BCI would run in the IBM cloud.
- Is testing BCI images after the release sufficient? We would highly recommend to not include IBM cloud into our main BCI test pipeline, because this will mean a considerable increase in the testing latency, possible up to 1-2 weeks because of the high complexity of the test environment.