[OSPRH-16305] Introduce OpenStackLightspeed#1495
Conversation
|
Skipping CI for Draft Pull Request. |
|
/test all |
aaa290a to
31e3f58
Compare
|
/test all |
31e3f58 to
ad47b46
Compare
|
/test all |
ratailor
left a comment
There was a problem hiding this comment.
Please fix one minor nit in comment and other for adding the pattern, we replicated in all operators, when you respin the PR.
743b77d to
ad85e76
Compare
|
/test all |
|
/test openstack-operator-build-deploy-kuttl |
|
This is the reason why the pre-commit checks are failing: It is about the introduction of new required fields. The newly introduced fields are wrapped in Optional section so it should not break the backward compatibility for the OpenStackControlPlane. Unless I'm mistaken. |
lpiwowar
left a comment
There was a problem hiding this comment.
One question related to the OpenStackLightspeed image. If somebody who is working on the openstack-operator has a perspective on this it would be really appreciated!:)
stuggi
left a comment
There was a problem hiding this comment.
maybe a general question for my understanding of OpenStackLightspeed. is it intended that it talks to the openstack api of the ctlplane it gets installed with?
@stuggi: Not right now, but this might come in the future. |
|
/retest |
1 similar comment
|
/retest |
289da51 to
9d4c0a2
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/637258ceae09405f853596ef5420d4b8 ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 18m 13s |
|
recheck /retest |
| TestTobikoImage *string `json:"testTobikoImage,omitempty"` | ||
| TestHorizontestImage *string `json:"testHorizontestImage,omitempty"` | ||
| TestAnsibletestImage *string `json:"testAnsibletestImage,omitempty"` | ||
| OpenstackLightspeedImage *string `json:"openstackLightspeedImage,omitempty"` |
There was a problem hiding this comment.
I think it would be good to drop the parameter from the OpenStackVersion and Controlplane resources and just have Lightspeed obtain its Image directly from the ENV variable. This would also work in the case where Lightspeed gets installed ahead of the Controlplane if that use case materializes.
There was a problem hiding this comment.
It has already been dropped from the OpenStackControlplane and regarding the OpenStackVersion, the code is written in such a way that it will work in both case:
- when
OpenStackVersionis present, we use an image fromOpenStackVersion - when
OpenStackVersionis not present, we fall back to the default image specified through the ENV variable
Is there any specific problem with this I'm not seeing? I'm just trying to understand.
There was a problem hiding this comment.
Just for the record, the OpenStackVersion section was removed as well with the recent update.
9d4c0a2 to
ee8f7a8
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/c282b3ccca9148d7be294f483154c3aa ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 35m 42s |
|
/retest-required |
|
recheck |
|
/retest-required |
46e9015 to
7cc36da
Compare
Introduce the OpenStackLightspeed custom resource that manages the deployment of Lightspeed-related functionalities. As of now, we expect the OLS operator to be present in the cluster. Otherwise, enabling of OpenStackLightspeed will fail. The Lightspeed functionalities can be enabled through the OpenStackLightspeed as follows: spec: llmEndpoint: <URL of the LLM> llmEndpointType: <endpoint type> llmCredentials: <secret containing token> modelName: <model name> tlsCACertBundle: <config map containg cert> Only one OpenStackLightspeed CR can configure OpenStack Lightspeed at a single time. If the user tries to manage the Lightspeed functionalities through two or more OpenStackLightspeed instances, the user will be warned, and the changes from the newest OpenStackLightspeed instance will be ignored.
7cc36da to
8362b19
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/3aa21f78ca1b4b33807b7695597436f6 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 55m 46s |
|
recheck |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/d9217dbd32ae42519c3801bd06c25d64 ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 29m 54s |
|
recheck |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprince, lpiwowar The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
35723e2
into
openstack-k8s-operators:main
This patch introduces the existing OpenStack Lightspeed API from openstack-k8s-operators/openstack-operator#1495 Co-authored-by: Lukáš Piwowarski <lpiwowar@redhat.com> Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
This patch introduces the existing OpenStack Lightspeed Controller code from openstack-k8s-operators/openstack-operator#1495 Co-authored-by: Lukáš Piwowarski <lpiwowar@redhat.com> Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
Introduce the OpenStackLightspeed custom resource that manages the
deployment of Lightspeed-related functionalities. As of now, we expect
the OLS operator to be present in the cluster. Otherwise, enabling of
OpenStackLightspeed will fail. The Lightspeed functionalities can be
enabled through the OpenStackLightspeed as follows:
Only one OpenStackLightspeed CR can configure OpenStack Lightspeed at a
single time. If the user tries to manage the Lightspeed functionalities
through two or more OpenStackLightspeed instances, the user will be
warned, and the changes from the newest OpenStackLightspeed instance
will be ignored.