[tripleo] Plan around switching Podman to default
yes let's keep some jobs with pacemaker too. My goal is to switch the
majority of CI and keep small/minimum coverage for HA (even if deployed
On Thu, Feb 14, 2019 at 2:02 PM James Slagle <james.slagle at gmail.com> wrote:
> On Thu, Feb 14, 2019 at 11:59 AM Emilien Macchi <emilien at redhat.com>
> > Sorry I forgot to mention Standalone, but it's in the same situation as
> > Let's keep Docker by default on both until CentOS8 is out.
> > On Thu, Feb 14, 2019 at 11:48 AM Emilien Macchi <emilien at redhat.com>
> >> Pacemaker provided by CentOS7 doesn't work with Podman, and only works
> with Docker.
> >> Podman is already the default on the Undercloud, and this is fine, as
> we don't deploy Pacemaker on this node.
> >> However for the Overcloud, it causes problem as upstream is tested on
> CentOS7 and downstream is being tested on RHEL8.
> >> With that said, I propose that we:
> >> - Keep Docker as the default on the Overcloud until CentOS8 is out.
> >> - Switch downstream to use Podman on the Overcloud (since we run RHEL8
> it's fine).
> >> - Switch all CI jobs except OVB to NOT deploy Pacemaker and switch to
> >> - Once CentOS8 is out, we revert the downstream only patch and land it
> I'd prefer to keep some gating jobs (non-OVB) that deploy pacemaker,
> so that we have coverage of pacemaker in the gate. I'm not sure if
> that's what your followup comment about standalone was implying. If it
> was then the plan sounds ok to me, otherwise I'd be concerned about
> the loss of pacemaker coverage.
> -- James Slagle
-------------- next part --------------
An HTML attachment was scrubbed...