Add OpensShift ci configuration for openstack-lightspeed/rag-content

[malingatembo]

This is a PR to onboard the openstack-lightspeed/rag-content repository into the OpenShift ci for the purpose of building the vector database image.

Currently we are hitting a 6hours limit with github runner when building the full vector database with openstack docs. This PR requests better resources: 16Gi memory, 4 CPU.

Configuations were generated with 'make new-repo'

• OWNERS file (umago, lpiwowar, Akrog)
• Prow plugin configuration (_pluginconfig.yaml)
• Prow CI configuration (_prowconfig.yaml)
• CI job definition with hello-world test ( jira acceptance criteria)
• Resource limits suitable for vector DB building (16Gi memory, 4 CPU)
• Image building configuration for Containerfile

Acceptance Criteria: Hello-world test runs successfully in OpenShift CI
Related: JIRA-71305
Inspired by: #71305"

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: malingatembo

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

The pull request process is described here

Details

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

[openshift-ci]

Hi @malingatembo. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[lpiwowar]

/ok-to-test

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@malingatembo: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openstack-lightspeed-rag-content-main-hello-world	openstack-lightspeed/rag-content	presubmit	Presubmit changed
pull-ci-openstack-lightspeed-rag-content-main-images	openstack-lightspeed/rag-content	presubmit	Presubmit changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

@malingatembo: 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/check-gh-automation-tide	f95bbde	link	true	/test check-gh-automation-tide
ci/prow/check-gh-automation	f95bbde	link	true	/test check-gh-automation

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.