Hi Jorge,

The Docker images on quay.io are images that are build in different CI pipelines and then used in other pipelines for all kind of builds/validations.
These are not images to install/setup an oVirt environment.

Jean-Louis

On 5/13/25 00:12, Jorge Visentini wrote:
So... I don't know where this link comes from and if it is being used for any functionality or purpose.

https://quay.io/organization/ovirt

Regarding orchestration, I think it is too early to decide. It could even be ansible with docker or podman... similar to kolla-ansible for osp.

Anyway, these are just my ramblings.

Em sex., 9 de mai. de 2025 às 01:58, Marcos Sungaila via Users <[email protected]> escreveu:

    Hi Jorge,

    This is a great initiative and I believe it is worth enough for
    the challenge you have ahead.

    A solid first step in this process is to work with small,
    dedicated containers, each tailored to a specific application or
    service. This approach ensures modularity, reduces complexity, and
    facilitates troubleshooting when needed.

    Once you have the basic containerization structure, the next step
    involves modularizing the application by breaking down the engine
    monolithic application into multiple independent containers. This
    will offer enhanced scalability, flexibility, and efficiency in
    managing updates and deployments.

    For such a project, using a container orchestration platform such
    as Kubernetes is recommended. Helm, a package manager for
    Kubernetes, can streamline deployment by managing configurations
    and automating complex processes. Using Helm to run an Engine
    server ensures smoother deployment and operational consistency.

    Do you already have a path in mind?

    Marcos

    *From:* Jorge Visentini <[email protected]>
    *Sent:* Wednesday, May 7, 2025 5:26 PM
    *To:* users <[email protected]>
    *Subject:* [External] : [ovirt-users] build ovirt in docker container

    hey...

    Is it crazy of me to try to compile everything in a single (big)
    container, or at least divide the closest services into containers?

    Is there any initiative in this direction?
    I swear, I didn't smoke anything to have this idea 🙏🤣

    I ask this because I'm in the initial process of creating a build
    in rocky linux 9.
    By the way, if anyone has basic documentation for this porting
    from centos 9 stream to rl9, it would be very welcome.
    Here we use Mellanox 3 and 4, and Emulex, so I need to standardize
    the kernel to compile the drivers lol

    many thanks

--
    Att,

    Jorge Visentini
    +55 55 98432-9868

    _______________________________________________
    Users mailing list -- [email protected]
    To unsubscribe send an email to [email protected]
    Privacy Statement: https://www.ovirt.org/privacy-policy.html
    oVirt Code of Conduct:
    https://www.ovirt.org/community/about/community-guidelines/
    List Archives:
    
https://lists.ovirt.org/archives/list/[email protected]/message/HGYNNFC5XPBEDK6TWLERHRMXZGTBHLYM/



--
Att,
Jorge Visentini
+55 55 98432-9868

_______________________________________________
Users mailing list [email protected]
To unsubscribe send an email [email protected]
Privacy Statement:https://www.ovirt.org/privacy-policy.html
oVirt Code of 
Conduct:https://www.ovirt.org/community/about/community-guidelines/
List 
Archives:https://lists.ovirt.org/archives/list/[email protected]/message/XVIVIFKRVHXG6VMQ5EPIBCVGLWSFGBP5/
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/7OLWLM7TBP2BXMFFQW7HTATWVGFALLFB/

Reply via email to