Memory and storage should have its value in GB rather than MB

Memory and storage should have its value in GB rather than MB

Memory, especially storage, should have its value in GB rather than MB (e.g. logicalvolume_size of CIT LogicalVolume, memory_limit of CIT VMware Host Resource, disk_size of CIT FileSystem).

Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

The idea has received an initial review to ensure adherence to our idea submission and community guidelines. More information may be needed at this stage and we expect the community to help prioritize the idea with comments and voting

Gopal Ram Valued Contributor.
Valued Contributor.

I agree, most of the tools now display in GB instead of MB, how to vote for this?

popadiyski Outstanding Contributor.
Outstanding Contributor.

For me all the attributes have to have the same value type. If you move to GB in disk_size, you would need to put GB in free space attribute. But then what we do with the small partitions in Linux, which are often less than a GB? Or than if you have less than a GB free space, then you will show 0? Such a change is pretty dangerous, and maybe in 20 years the MB will not count at all, but currently it is just unnecessary. Just device the result with 1024.

Dmitry P Super Contributor.
Super Contributor.
An idea - do not change current attriubutes, just create a new one attribute "Size in GB" where it needed, espesially for storages. In situation when size < 1GB I think Float attribute type may be useful.
Micro Focus Expert
Micro Focus Expert
Status changed to: Under Consideration

This idea received enough votes and comments from the community and been reviewed by Micro Focus for strategic fit. These ideas are continually monitored and considered for prioritization in our development planning.

RohitSS Super Contributor.
Super Contributor.

I think implementing size of RAM in GB is the need of the hour. Nobody has desktop/server/thin client in MB nowadays. Even if somebody has, a logic can be placed where RAM size is less than 1 GB, automatically RAM size should be calculated in MB (for instance 512 MB).

About the Author
Bill has over 26 years of experience in the IT industry focusing on providing business solutions utilizing HPE Software’s tools at enterprise scale. He comes from the HPE-IT organization where he managed the first deployment of HPSC (now HPSM) and then later UCMDB with its discovery partner UD. Bill also managed a team of IT Developers, who created customized configuration management solutions for HPE-IT and HPE’s ES clients.
Most "Liked" Contributors
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.