Bug 1644671 - [RFE] Request for template based partition deployment for overcloud
Summary: [RFE] Request for template based partition deployment for overcloud
Keywords:
Status: CLOSED DUPLICATE of bug 1381111
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 13.0 (Queens)
Hardware: All
OS: Linux
high
high
Target Milestone: Upstream M3
: ---
Assignee: Dmitry Tantsur
QA Contact: mlammon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-31 11:28 UTC by coldford@redhat.com
Modified: 2023-12-15 16:12 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-05 16:15:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-13805 0 None None None 2022-03-13 16:48:18 UTC

Description coldford@redhat.com 2018-10-31 11:28:20 UTC
Description of problem:

We would like to see a template based partition deployment for the overcloud nodes. That is a template with information on disk layout for the overcloud nodes.  currently the whole disk image makes it necessary for the undercloud to have enough free space for director to expand the image. This is an issue with underclouds that have limited space due to being vms themselfs. 

I believe that it would be more in line with the way director works if the template was passed to director and it took care of partitioning the drive before applying the standard image. Then it could update links to the partitions on the OS.

Comment 2 Dmitry Tantsur 2019-04-02 09:31:55 UTC
This has been a recurring topic, but it was determined to require massive changes to ironic. Some of these changes have been done, so we can try revisiting it for OSP 16. I don't envision any practical way to backport it to 13 though.

An alternative is to use the ansible deploy, but it's a TechPreview still: http://tripleo.org/install/advanced_deployment/ansible_deploy_interface.html.

Comment 4 Dmitry Tantsur 2019-05-14 11:08:48 UTC
Implementation notes:

The feature as it is requested here will probably be implemented via deploy steps. The bare deploy steps framework has landed in Stein (15), but more work is planned in Train (16) to make it usable for cases like this. An actual deploy step to do custom partitioning is planned for the future, but is not currently on the Train (16) roadmap upstream. TripleO integration needed for us to use it is unlikely to land until 17.

Realistically, I'd plan this as a stretch goal for 16 with a very high probability of slipping into 17+

Comment 5 Dmitry Tantsur 2020-08-05 16:15:10 UTC

*** This bug has been marked as a duplicate of bug 1381111 ***


Note You need to log in before you can comment on or make changes to this bug.