Comment 4 for bug 1555938

Hi Sheel Rana,

For 1. All of extra CPU cycles and extra db query can accept. I mean that although the volume service is OK, there are other factors to make it failure that new volume created on the same host default. For example, the same host has too smaller residual size to create a new one.
   (1) Report a failure.
   (2) New volume can be created on other hosts by scheduler.
So, only check volume service status during this operation is not enough, take action (2) may safely.

For 2. It's my recommended approaches (just for me), and I have finished on my test bed.
   Why are we require same host for creating these where source exists? It can get high priority, but non-essential.

For 3. It's perfectly. But It difficult just for me to implement what pass host id to scheduler.

Pardon my low English level. Thank you. :)