-
Notifications
You must be signed in to change notification settings - Fork 15
Conversation
We are not using rpms anymore to deploy containers for caasp4(SLE15). However, we would like to choose which images we use, so we will use a patch instead of a sed command. Signed-off-by: Jordi Massaguer Pla <[email protected]>
Signed-off-by: Jordi Massaguer Pla <[email protected]>
I don't like very much this thing but I don't know how to make it work with kubic and caasp. I wanted to keep compatibility with sle12 since we don't yet have the sle15 image, but this is a "nice to have" thing. @davidcassany @bergmannf : any ideas on how to do this differently? |
what if we had yaml files for each version? like public.yaml.caasp4, private.yaml.caasp4, public.yaml.caasp3, private.yaml.caasp3, public.yaml.kubic, etc... And then in the package we install one or the other depending on the build architecture. How does it sound? |
I think using the concrete versions might be a problem - I don't know how often those change, but whenever they do we have to change the Maybe there is a way to use one of those Also - if we do it like this, I think using the same approach in |
Having some automation in place would be great. Actually, once we were discussing with @davidcassany about getting the information from the build service by generating some metadata packages with each image build, and requiring this metadata when building c-c-m package (and k8s-salt). The key point is to know if the tags will change that much. Thus, will velum image be tagged on velum version, which changes on each commit, or will the velum image be tagged with a more stable number, as 0.0? |
I agree using the patch is not a good approach. If we were using some kind of obs trick to get the tag, should we leave some defaults in case we don't use the RPM? @ereslibre @MaximilianMeister : Are the development environments using the manifests files without the RPM? |
@bergmannf : Right now we are using the images based on sle12, like registry.suse.de/devel/casp/head/controllernode/images_container_base/sles12/velum:0.0, which have a tag that does not change. What if we used this as a default until we have the automation in place? |
If we were using, as a first step, the ones based in sle12: registry.suse.de/devel/casp/head/controllernode/images_container_base/sles12/velum:0.0 we could easily do that by setting the _base_image variable to registry.suse.de/devel/casp/head/controllernode/images_container_base/sles12 in the spec file. Then on a second step, we could use the obs mechanism. How does it sound? |
@jordimassaguerpla I think setting the AFAIK the dev environment is using the packaged |
I just created a new PR that uses the sles12 images from the registry as a starting point, until we have more info on the dev env and the tagging strategy. |
We are not using rpms anymore to deploy containers for caasp4(SLE15).
However, we would like to choose which images we use, so we will use a
patch instead of a sed command.
Signed-off-by: Jordi Massaguer Pla [email protected]