Changes in ve .conf file in 2.0

[zeedon]

Hey Guys

I noticed my script for cloning VE's seemed to break in 2.0

After looking into it seems the .conf file for a newly created ve are different for example VE 100

in proxve 2.0

VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/100"

where as in 1.9 it was

VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"

I assume there is no issue in me changing this back to $VEID, seems to work fine was just wondering why this has changed?

 

[dietmar]

was just wondering why this has changed?

We now support several storage locations (not only /var/lib/vz). I guess that change is the result of using the pve storage library to generate the path.

 

[zeedon]

We now support several storage locations (not only /var/lib/vz). I guess that change is the result of using the pve storage library to generate the path.

OK, So there is no problem in setting this back to use $VEID?

 

[dietmar]

OK, So there is no problem in setting this back to use $VEID?

I guess you need to test that yourself.