build the osp undercloud images from the images provided by the rhospimages rpm.

Bug #1719902 reported by wes hayutin on 2017-09-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
High
John Trowbridge

Bug Description

Please help me fill out the details of this bug.
After a discussion about the TQ runs w/ OSP, it was identified that the workflow with OSP images can follow the same pattern as the upstream devmode pattern. We can install the rhosp-director-images rpm and then virt-customize the overcloud to be the undercloud.

This will provide the same advantages we've seen upstream with by ensuring a valid undercloud and by having pre-installed packages installed on the undercloud.

Alex Schultz (alex-schultz) wrote :

I'm not sure this is valid as it could lead to issues where packages are there and are not properly installed by the undercloud process. Techincally the undercloud install should start from a stock (empty) image and the install process should handle everything. If we are assuming the undercloud has software installed this might be an area where customers won't have something that we have.

Changed in tripleo:
status: Triaged → Opinion
wes hayutin (weshayutin) wrote :

So, agreed this is not how customers would install. We have the configs in place to take a base os image [1] and install with the images provided by rhosp-director-images.rpm. This is a much longer install and I would argue that we don't need to do it in every ci job. Keep in mind that baremetal jobs are also in place for the same reason.

This is another consideration made for speed in CI, something that is hardly unprecedented.

I'm going to move this back to triaged for now, if you feel like it's still a problem let's discuss on irc. OK?

Thanks for the feedback, it's really great to see the input!!

[1] https://github.com/openstack/tripleo-quickstart/blob/master/config/environments/baseos_rhel_libvirt.yml.example

Changed in tripleo:
status: Opinion → Triaged
Alex Schultz (alex-schultz) wrote :

As long as it's not the primary method for installation, we have additional jobs that cover just the install running in the same gate, and it's appropriately documented then it might be ok. The problem is that jobs that use this method will reduce our coverage and could possibly allow for regressions. Additionally as we move to trying to replace the overcloud image with a stock image this may not be beneficial in the long term.

John Trowbridge (trown) wrote :

https://review.openstack.org/508868 should be all we need to allow this to work via downstream release config files (so we dont need some downstream specific thing in the role)

Reviewed: https://review.openstack.org/508868
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=a38e9635bb9eb8166fad6d72d881118cd3376767
Submitter: Jenkins
Branch: master

commit a38e9635bb9eb8166fad6d72d881118cd3376767
Author: John Trowbridge <email address hidden>
Date: Mon Oct 2 08:44:36 2017 -0400

    Make the convert-image role more generic

    Specifically this patch adds knobs for controlling whether:
    - an update is run (convert_image_update)
    - what packages get removed (convert_image_remove_pkgs)
    - what packages get installed (convert_image_install_pkgs)
    - what tempest plugins get installed (convert_image_tempest-plugins)

    All defaults for the above options are set to the current hardcoded
    values, so this is a no-op change wrt current configurations.
    However, it allows for new configurations to take advantage of this
    feature.

    Change-Id: Iecb2d07e4451eb97c958dcf19d9a76aa0982acef
    Related-Bug: 1719902

Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Changed in tripleo:
milestone: stein-2 → stein-3

Is this still an issue?

Changed in tripleo:
milestone: stein-3 → stein-rc1
Changed in tripleo:
milestone: stein-rc1 → train-1
Changed in tripleo:
milestone: train-1 → train-2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers