Currently all ICP images are delivered as a single tarball. This means that a 10GB tarball, extracted to 28GB has to be loaded on the boot node to get to a single image, icp-inception, and then the process has to be repeated on all master nodes to get to the image manager.
This takes a substantial amount of time, and causes significant network and disk activity completely unnecessarily.
Consider instead delivering 3 tarballs that can be loaded as appropriate:
1. boot (icp-inception)
2. master (image manager)
3. everything else that needs to be loaded into private registry
This should shave a significant amount of time off the installation and improve the user experience.
Real Scenario + Problem Statement
|Who would benefit from this IDEA?||Anyone performing offline installation of ICP|
Why is it useful?
|Market Evidence - # of customers in next 12 months|
|Avg Annual Contract Value Per Customer|
|Secondary Persona (multi-select)|
How should it work?
|Geo Availability for this IDEA|
|Geo - Use for OBDR Reporting only|