[FEATURE REQUEST] Overall Progress Bar about rpm-ostree

[cgwalters]

This would allow us to pipe the status into applications such as Steam & Topgrade

Pipe? Not the DBus API?

These are pretty different things right now.

I know the DBus API is...unfriendly.

[KyleGospo]

This would allow us to pipe the status into applications such as Steam & Topgrade

Pipe? Not the DBus API?

These are pretty different things right now.

I know the DBus API is...unfriendly.

Ah sorry, that was pipe in the metaphorical sense rather than me explicitly requesting it be pipe-able. I think either way is fine, whatever you believe to be most correct for ostree. I just need a way to get a 0-100 number from it.

[antheas]

Ideally jsonl (JSON line) output that includes:

• total image size
• download size
• currently downloaded size
• total ostree layer number
• total custom layer number
• download ostree layer number
• download custom ostree layer number
• downloaded ostree layer number
• downloaded custom ostree layer number

OR a dictionary with a mapping of layer keys to:

• layer size
• whether the layer is custom
• whether the layer exists in cache
• how % of the layer is downloaded

Latter is preferable, especially if parallel layer pulls are implemented*. But either work and give great flexibility in presentation.

These three attrs are especially important and should probably be included regardless, esp. to assist naive implementations (e.g., bash with jq):

• total image size
• download size
• currently downloaded size

As they allow for proper download time estimation while showing a two-stage slider that begins e.g., at 60% if 60% of the image is already downloaded.

Can either be through e.g., a dbus signal or rpm-ostree update --json. Since it will be wrapped it does not really matter.

*after benchmarking I found that the current single threaded implementation saturates an internet connection of 70mbps-100mps, not so quite at 1gbps.