<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>If HostXML::test_<span style="font-style: italic; ">ds_</span>capacity only creates $DATASTORE_LOCATION/<id> assuming $DATASTORE_LOCATION itself exists,</div>
<div>my next question here might be, </div>
<div>which code creates $DATASTORE_LOCATION itself and when?</div>
<div><br>
</div>
<div>I don't think I missed an instruction to create $DATASTORE_LOCATION manually in the ON documentation..</div>
<div>i.e. $DATASTORE_LOCATION must be created by ON codes (maybe) during the first VM deployment.</div>
<div><br>
</div>
<div>But like I described in the original email, our test ON4.4 fails at this.</div>
<div><br>
</div>
<div>Hyunwoo Kim</div>
<div>FermiCloud</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>The $DATASTORE_LOCATION/<id> dir is created by the first VM deployment. That is why in HostXML::test_ds_capacity (called from Scheduler.cc), we use HOST/FREE_DISK as the free space when the ds-id subdir does not exist, to allow the first deployment.</div>
<div>But now it seems that monitor_ds should also consider that $DATASTORE_LOCATION may actually not exist.</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>