Comment 0 for bug 1673818
Revision history for this message
| George Shuklin (george-shuklin) wrote | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Current documentation states that:
http://
... a config drive: ...Must be a un-partitioned block device (/dev/vdb, not /dev/vdb1)...
This is not correct.
1. Cloud-init actually, works with ConfigDrive as partition.
2. Ironic uses partition at the end of disk to write metadata, and it's absurd for baremetal provisioning to dedicate whole disk (actual SATA, SSD, SAS/FC drive) just to tiny metada.
3. According to @smoser at #cloud-init IRC, " i'm pretty sure the doc is just wrong, ... i'm pretty sure reading current code that if the filesystem has a label of 'config-2', then it will work".
I think this part of documentation should be rewritten to avoid confusion with Ironic workflow for ConfigDrive.