Need to change the parameter that is used to check against max_memory

[sreeteja]

This max_memory parameter is checked against 'storage-customer'
https://github.com/openstack/nova-dpm/blob/2b53cd3f330432d43cc93cb1ad8785293203e4fd/nova_dpm/virt/dpm/utils.py#L49

'storage-customer' is the total memory of the CPC but to launch instance using devstack setup it needs to be checked against available memory of CPC.

https://github.com/zhmcclient/python-zhmcclient/blob/48b8d5c0619072afa1832758fe3c4a58628be95e/tools/cpcdata#L260

so this parameter needs to be replaced by 'storage-customer-available'

[Prabhat Ranjan (pranjank)]

I think this should not be bug.

Problem with 'storage-customer-available' is:
Let's say cpc has 10 GB memory(total) and no partition has created yet. And we start compute service with max_memory=5GB and created 3 partition of with 1GB RAM. And then if we restart compute service it will through exception.

[Prabhat Ranjan (pranjank)]

In above example lets say 5 GB instead of 10 GB

[Andreas Scheuring (andreas-scheuring)]

Agree with Prabhat!

[Andreas Scheuring (andreas-scheuring)]

Is not a bug - works as designed. See Prabhats comment.