[openstack-dev] [tripleo] ironic automated cleaning by default?
Dmitry Tantsur
dtantsur at redhat.com
Fri Apr 27 13:43:34 UTC 2018
Okay, it seems like the idea was not well received, but I do have some action
items out of the discussion (thanks all!):
1. Simplify running cleaning per node. I've proposed patches [0] to add a new
command (documentation to follow) to do it.
2. Consider running metadata cleaning during deployment in Ironic. This is a bit
difficult right now, but will simplify substantially after the deploy steps work.
Any other ideas?
I would like to run at least one TripleO CI job with cleaning enabled. Any
objections to that? If not, what would be the best job (it has to run ironic,
obviously)?
[0] https://review.openstack.org/#/q/topic:cleaning+status:open
On 04/25/2018 03:14 PM, Dmitry Tantsur wrote:
> Hi all,
>
> I'd like to restart conversation on enabling node automated cleaning by default
> for the undercloud. This process wipes partitioning tables (optionally, all the
> data) from overcloud nodes each time they move to "available" state (i.e. on
> initial enrolling and after each tear down).
>
> We have had it disabled for a few reasons:
> - it was not possible to skip time-consuming wiping if data from disks
> - the way our workflows used to work required going between manageable and
> available steps several times
>
> However, having cleaning disabled has several issues:
> - a configdrive left from a previous deployment may confuse cloud-init
> - a bootable partition left from a previous deployment may take precedence in
> some BIOS
> - an UEFI boot partition left from a previous deployment is likely to confuse
> UEFI firmware
> - apparently ceph does not work correctly without cleaning (I'll defer to the
> storage team to comment)
>
> For these reasons we don't recommend having cleaning disabled, and I propose to
> re-enable it.
>
> It has the following drawbacks:
> - The default workflow will require another node boot, thus becoming several
> minutes longer (incl. the CI)
> - It will no longer be possible to easily restore a deleted overcloud node.
>
> What do you think? If I don't hear principal objections, I'll prepare a patch in
> the coming days.
>
> Dmitry
More information about the OpenStack-dev
mailing list