ECS: The capacity unit of the ECS differ between the UI and REST API (GiB vs GB)

Note the GB unit in CLI and REST API Commands:

admin@ecsnode1:~> svc_bucket info chris-s3-bkt
svc_bucket v1.1.1 (svc_tools v2.20.0)                 Started 2024-11-22 15:51:33

Bucket ID                        chris-ns.chris-s3-bkt

  Name                             chris-s3-bkt
  Namespace                        chris-ns
  Owner User                       chris-s3-user
  Owner VDC Name                   VDC1
  Owner zone/VDC ID                urn:storageos:VirtualDataCenterData:8af5b9c3-9c0c-43b5-9402-14d181ade5bf
  Keypool Hash ID                  43344cc6ad534c4e600dc0a32d90e5104a8f718d99487938bf9f273f2100f248
  Bucket Deletion Status           None

  Replication Group (vpool) Name   local_vdc
  Replication Group (vpool) ID     urn:storageos:ReplicationGroupInfo:9eaa2c9d-4ed5-4f40-90f1-e347f8f3f3fd:global
  Bucket Creation Date             2024-11-22 15:13:33 (1732288413155)
  Temp Failed (TSO)                False

  API Type                         S3
  FS Access Enabled                False
  Encryption Enabled               False
  Versioning State                 Disabled
  ADO Enabled                      False
  ADO Read-Only                    False
  Object Lock Enabled              False
  Auto commit period (seconds)     None
  Enforce Retention                False
  Lifecycle Policy                 None

  Keypool Policy                   None

  Bucket ACL:
    Type       Affects    Name                               
    user       file/dir   chris-s3-user                       FULL_CONTROL

  Object count                     2
  Total Object Size                11 GB


admin@ecsnode1:~> 

admin@ecsnode1:~> svc_rest_cmd /object/billing/buckets/chris-ns/chris-s3-bkt/info | xmllint --format -
svc_rest_cmd 1.0.17

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<bucket_billing_info>
  <total_size_deleted>0</total_size_deleted>
  <total_objects_deleted>0</total_objects_deleted>
  <name>chris-s3-bkt</name>
  <uptodate_till>2023-06-15T18:25:45Z</uptodate_till>
  <namespace>chris-ns</namespace>
  <sample_time>2024-11-27T14:23:38Z</sample_time>
  <TagSet/>
  <total_mpu_parts>0</total_mpu_parts>
  <total_mpu_size>0</total_mpu_size>
  <total_objects>2</total_objects>
  <total_size>11</total_size>
  <total_size_unit>GB</total_size_unit>
  <vpool_id>urn:storageos:ReplicationGroupInfo:9eaa2c9d-4ed5-4f40-90f1-e347f8f3f3fd:global</vpool_id>
</bucket_billing_info>
admin@ecsnode1:~> 

But checking the UI metering information we do see the same reading in GiB instead of GB, what seems not to be correct:

If we hover over the 11.00 GiB, it shows in bytes.
 

11 GB = 11 * 1000^3 = 11000000000 bytes
11 GiB = 11 * 1024^3 = 11811160064 bytes

The values returned in the UI and the command line are both GiB. At the command line, the unit is displayed as GB instead of GiB which is wrong. 
So the GiB values in the metering page are correct.

The capacity reading of CLI or REST API commands are true and are matching the UI metering reading. A future ECS code version fixes the CLI/REST API capacity units from GB in GiB.