Closed tcooper closed 7 years ago
Rocks7 custom partitioning cannot be done in extend-<node>.xml and possibly in replace-<node>.xml due to new installation behavior related to Anaconda in CentOS 7.
extend-<node>.xml
replace-<node>.xml
Example solution is to splice onto the graph with custom graph & node XML...
<?xml version="1.0" standalone="no"?> <graph> <edge from="compute" to="compute-partitioning"/> <order head="compute-partitioning" tail="partition"/> </graph>
<?xml version="1.0" standalone="no"?> <kickstart> <pre> cat >> /tmp/user_partition_info << 'EOF' clearpart --all --initlabel --drives=[device_name] zerombr part / --fstype=ext4 --size=65536 --ondisk=[device_name] part /scratch --fstype=ext4 --size=1 --grow --ondisk=[device_name] EOF </pre> </kickstart>
Where [device_name] is sda or vda or other raw block device detected during install.
[device_name]
sda
vda
Thanks, Trevor. The most likely fix will be:
Partially completed. Latest version has custom-partition. Docs haven't been modified yet.
Resolved by https://github.com/rocksclusters/base/commit/d50fdbe48c95078668252ab6d440a792c2174a7f
Order is important...
Rocks7 custom partitioning cannot be done in
extend-<node>.xml
and possibly inreplace-<node>.xml
due to new installation behavior related to Anaconda in CentOS 7.Example solution is to splice onto the graph with custom graph & node XML...
/export/rocks/install/site-profiles/7.0/graphs/default/compute-partitioning.xml
/export/rocks/install/site-profiles/7.0/nodes/compute-partitioning.xml
Where
[device_name]
issda
orvda
or other raw block device detected during install.