[rdo-dev] [Octavia] Providing service VM images in RDO

[Assaf Muller]

On Wed, Jan 10, 2018 at 8:10 AM, Alan Pevec <apevec at redhat.com> wrote:
> Hi Bernard,
>
> I've added this as a topic for the
> https://etherpad.openstack.org/p/RDO-Meeting today,
> with some initial questions to explore.
>
> On Wed, Jan 10, 2018 at 1:50 PM, Bernard Cafarelli <bcafarel at redhat.com> wrote:
>> * easier install/maintenance for the user, tripleo can consume the
>> image directly (from a package)
>
> How do you plan to distribute the image, wrapped inside RPM?
>
>> * ensuring up-to-date amphora images (to match the controller version,
>> for security updates, …)
>
> That's the most critical part of the process to figure out, how to
> automate image updates,
> just run it daily, trigger when included packages change...

On Octavia patches (because the agent in the image might change), but
it's worth pointing out that other elements in the image may need
updating - Say, on a kernel CVE fix, haproxy update, etc. Maybe on
Octavia changes + on a nightly basis?

>
>> * allow to test and confirm the amphora works properly with latest
>> changes, including enforcing SELinux (CentOS upstream gate runs in
>> permissive)
>
> And that's the second part, which CI job would test it properly?
>
>> * use this image in tripleo CI (instead of having to build it there)
>
> Related to the up-to-date issue: how to ensure it's latest for CI?
>
>> * (future) extend this system for other system VM images
>
> Which ones?
>
> Cheers,
> Alan
> _______________________________________________
> dev mailing list
> dev at lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/dev
>
> To unsubscribe: dev-unsubscribe at lists.rdoproject.org