Improve perceived install time by deferring network config
Bug #1750124 reported by
Mark Shuttleworth
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| subiquity |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
If we handle the disk partitioning before networking, we will use time more efficiently as our user will be setting IP addresses and other networking aspects while we partition the disk. Is it possible to kick off disk partitioning and image transfer before all the other aspects of config are agreed?
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #1 |
| Changed in subiquity: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
To post a comment you must log in.
Interesting idea. In the long run we want to support iscsi mounts which will require having the network up before partitioning. I'm also not quite sure how to implement this, it might require us to be much more involved in how curtin executes rather than just generating a config and handing if off, which is not necessarily a bad thing just a bit trickier to do.