Bugzilla – Bug 7736
image plan should provide space requirements for operation
Last modified: 2009-07-17 16:43:06 UTC
You need to log in before you can comment on or make changes to this bug.
Automated installer consumes pkg(5) for installing bits to the target. Before the installation process can be started, it is necessary to determine if the target system has enough space for bits to be installed. Once the installation process is running, it is also desired to provide user with the information about progress of the installation. API which would provide following information would be desired: * total size of bits to be downloaded * total size of bits to be installed * full list of packages to be installed List of IPS objects (packages, clusters, ...) would be provided as input, e.g. SUNWcsd SUNWcs babel_install entire Distribution Constructor might also take advantage of those features.
Marking as blockers for bugs which would be consumers of those APIs: bug 4546 Automated Installer needs mechanism for calculating size of bits to be installed bug 4278 AI needs a better way of reporting install progress
Lowering priority to reflect that it won't happen for 2009.06. Marking as RFE. Also note that implementing this RFE isn't required for fixing bug 4278. You don't need total size or full list of packages in advance of creating the plan (and, in fact, you never will be able to), and once the install plan is created, you can have the same kind of progress indicators that are already available for the pkg(5) commandline and the packagemanager gui. The only thing this RFE will really help with is determining this information prior to creating the image, so that you can know how big to make the image dataset.
(In reply to comment #2) > > Also note that implementing this RFE isn't required for fixing bug 4278. You > don't need total size or full list of packages in advance of creating the plan > (and, in fact, you never will be able to), and once the install plan is > created, you can have the same kind of progress indicators that are already > available for the pkg(5) commandline and the packagemanager gui. > Danek, this is a good point - where is possible to take a look in order to obtain more information about * how could this plan be created by pkg(5) consumers ? * what kind of information this plan contains ? * what the format of plan is ?
src/modules/client/api.py, and maybe a bit in src/modules/client/image.py.