Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Linux partitioning information for Containerized NOM setup

Hi Team,

Could you help us on Linux Partitioning information for each: partitions are like /opt , /var/
Example: for Ops Br, The document says /var /opt folder and no separate disk or partition for kubernetes (just folder). However, when a server is built, we discovered we need a separate disk and a separate partition for /var /opt etc.

Customer is attempting a containerized installation
OpsBridge 2018.11
Proof of Concept

HP Support
The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of HP.
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution, If you are satisfied with anyone’s response please remember to give them a KUDOS and show your appreciation.
Labels (2)
Tags (3)
2 Replies
Micro Focus Contributor
Micro Focus Contributor


for NNM the folders are the same: 

NNMi installs all application binaries in the /opt/OV directory and all data files in the /var/opt/OV directory.

you can change the installation path but the above are the default.


Micro Focus Contributor
Micro Focus Contributor

Hi Community,

We just came out of a final discussion with our team on this topic. The idea was to trace back on where the actual requirements / those numbers came from. And here are the conclusions. Practically whatever OpsB team has recommended are the minimum's enforced by CDF in it's installer check, without which it won't proceed. So we can recommend the same scheme as mentioned by CDF.

The realities are however very less, but this need not be quoted. These are mostly specified higher to give room for future expansion, upgrades etc (older containers will remain in the system even after upgrade and fill up space .. such scenarios possibly).

For example /opt/kubernetes we hardly use 5 GB, /var/opt/kubernetes about 7.5 GB (and that too only on downloadimages machine), the docker bootstrap (thinpool LVM) consumes hardly about 1.5 GB, docker main (thinpool LVM) consumes about 14 GB. In the 2019.02 we would make a better estimate of this and clarify in the docs separately. However most likely it still will be quoted higher to give buffer for expansion / unknown.

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.