[openstack-dev] [tripleo] [quickstart] [networking-ovn] No more overcloud_prep-containers.sh script

Miguel Angel Ajo Pelayo majopela at redhat.com
Wed Oct 3 09:25:56 UTC 2018


Hi Jirka & Daniel, thanks for your answers... more inline.

On Wed, Oct 3, 2018 at 10:44 AM Jiří Stránský <jistr at redhat.com> wrote:

> On 03/10/2018 10:14, Miguel Angel Ajo Pelayo wrote:
> > Hi folks
> >
> >    I was trying to deploy neutron with networking-ovn via
> tripleo-quickstart
> > scripts on master, and this config file [1]. It doesn't work, overcloud
> > deploy cries with:
> >
> > 1) trying to deploy ovn I end up with a 2018-10-02 17:48:12 | "2018-10-02
> > 17:47:51,864 DEBUG: 26691 -- Error: image
> > tripleomaster/centos-binary-ovn-controller:current-tripleo not found",
> >
> > it seems like the overcloud_prep-containers.sh is not there anymore (I
> > guess overcloud deploy handles it automatically now? but it fails to
> > generate the ovn containers for some reason)
> >
> > Also, if you look at [2] which are our ansible migration scripts to
> migrate
> > ml2/ovs to ml2/networking-ovn, you will see that we make use of
> > overcloud_prep-containers.sh , I guess that we will need to make sure [1]
> > works and we will get [2] for free.
>
> Hi Miguel,
>
> i'm not subject matter expert but here's some relevant info:
>
> * overcloud_prep-containers.sh is not a production thing, it's
> automation from TripleO Quickstart, which is not part of production
> deployments. We shouldn't depend on it in docs/automation for OVN
> migration.
>
> Yes I know, but based on the deployment details we have for networking-ovn
it should be enough, we will have to update those documents with the new
changes anyway, because surprisingly this change has came for "Rocky" last
minute. Why did we have such last minute change? :-/

I understand the value of simplifying workflows to cloud operators, but
when we make workflow changes last minute we make others life harder (now I
need to rework something I want to be available in rocky, the migration
scripts/document).


> * For production envs, the image preparation steps used to be documented
> and performed manually. This now is now changing in Rocky+, as Steve
> Baker integrated the image prep into the deployment itself. There are
> docs about the current method [3].
>

Oops, I see

openstack tripleo container image prepare default \
      --output-env-file containers-prepare-parameter.yaml

Always outputs neutron_driver: null


@Emilien Macchi, @Steve Baker <sbaker at redhat.com>  How can I make sure it
provides "ovn" for example?   ^

I know I could manually change the file, but then, how would I run... " --
local-push-destination" ?


>
>
> * I hit similar issues with incorrect Neutron images being uploaded to
> undercloud registry, you can try deploying with this patch [4] which
> aims to fix that problem (also the depends-on patch is necessary).
>

Thanks a lot!

>
> Jirka
>
> > [1]
> https://github.com/openstack/networking-ovn/blob/master/tripleo/ovn.yml
> > [2]
> https://docs.openstack.org/networking-ovn/latest/install/migration.html
>
> [3]
> http://tripleo.org/install/advanced_deployment/container_image_prepare.html
> [4] https://review.openstack.org/#/c/604953/
>
>

-- 
Miguel Ángel Ajo
OSP / Networking DFG, OVN Squad Engineering
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20181003/b6d212fb/attachment.html>


More information about the OpenStack-dev mailing list