vllm 0.6.6

[maysunfaisal]

What does this PR do?:

Upload the vllm 0.6.6 Containerfile and requirements.txt changes as granite 3.1 require vllm 0.6.6.

This is a copy paste from https://github.com/maysunfaisal/llm-on-openshift/tree/vllm-0.6.6/llm-servers/vllm/gpu

Which issue(s) this PR fixes:

https://issues.redhat.com/browse/RHDHPAI-494

PR acceptance criteria:

Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened and linked to this PR, if they are not in the PR scope due to various constraints.

• Tested and Verified

• Documentation (READMEs, Product Docs, Blogs, Education Modules, etc.)

How to test changes / Special notes to the reviewer:

https://quay.io/repository/redhat-ai-dev/vllm-openai-ubi9?tab=tags

[thepetk]

lgtm

[thepetk]

lgtm

To clarify I feel the error of the status check is unrelated to this update. Looking at:

ERROR: Could not install packages due to an OSError: [Errno 28] No space left on device

it seems that we might need bigger memory limit to build the image. I'm curious to see here if this can be covered from github or we need something from our side to handle those builds

[maysunfaisal]

lgtm

To clarify I feel the error of the status check is unrelated to this update. Looking at:

ERROR: Could not install packages due to an OSError: [Errno 28] No space left on device

it seems that we might need bigger memory limit to build the image. I'm curious to see here if this can be covered from github or we need something from our side to handle those builds

I have been thinking about this. I feel like I am going to exclude these set of Containerfiles from renovate.. This should be manually handles because the image sizes are > 5GB

[thepetk]

lgtm

To clarify I feel the error of the status check is unrelated to this update. Looking at:

ERROR: Could not install packages due to an OSError: [Errno 28] No space left on device

it seems that we might need bigger memory limit to build the image. I'm curious to see here if this can be covered from github or we need something from our side to handle those builds

I have been thinking about this. I feel like I am going to exclude these set of Containerfiles from renovate.. This should be manually handles because the image sizes are > 5GB

+1 at least until we find a proper way to cover this

[Jdubrick]

lgtm. I agree with the comments about manually doing these ones since they are so large. We will need to add some logic to the workflow for skipping images if we'd like to avoid errors

[maysunfaisal]

@thepetk @Jdubrick can you please take a look at #27, once #27 is merged I will rebase the PR

[maysunfaisal]

rebased, green check, merging