Related review URL: https://review.openstack.org/#/c/605014/ https://review.openstack.org/#/c/605006/ Compare with upstream glance, starlingx added "Store" column as below +-----+--------+-------+-----------------+-----+------------+--------+---------+ | ID | Name | Store | Disk_format | ... | Size | Status |Owner| +-----+--------+-------+-----------------+-----+------------+--------+---------+ | xxx | img1 | file | raw | ... | 10737418 | active | xxx | | xxx | img2 | file | raw | ... | 5086345 | active | xxx | +-----+--------+-------+-----------------+-----+------------+--------+---------+ Regards Liang -----Original Message----- From: Fang, Liang A [mailto:liang.a.fang@intel.com] Sent: Wednesday, October 10, 2018 4:35 PM To: jack.ding@windriver.com; robert.church@windriver.com; Rowsell, Brent <Brent.Rowsell@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] What's the use case of these 2 patches? Hi I'm working on upstreaming below 2 patches and the code review was slightly blocked because community need to know the use case: Commit from glanceclient: 75967f4c9c9ca582277d036581effcac0c7ee5a9: Show glance_backend rbd or file. Commit from glance: f6ad3a44303a1bf9abec91e1d679cdd13fb9c4f6: Add store info in glance image-list and image-show Could anybody share the original intention of these two patches? What's the use case of saving/showing the store info? It seems end user cannot do anything with this information. Thanks! Regards Liang _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss