06 AM
> To: Prachi Damle;
> Subject: Re: VMEntityVO and VMInstanceVO
>
> Thanks Prachi.
> I was looking at CLOUDSTACK-5458 when I came across this.
>
> I don't quite follow the logic of multiple VOs based on a subset of fields.
> If multiple VOs are targeting a subset of fields
Koushik,
My comments inline.
Prachi
-Original Message-
From: Koushik Das
Sent: Tuesday, December 17, 2013 4:06 AM
To: Prachi Damle;
Subject: Re: VMEntityVO and VMInstanceVO
Thanks Prachi.
I was looking at CLOUDSTACK-5458 when I came across this.
I don't quite follow the log
tities for which this has been done so far, Alex has
> put everything under cloud-engine-schema recently where you can find some
> more of such examples.
>
> Prachi
>
> -Original Message-
> From: Koushik Das
> Sent: Sunday, December 15, 2013 9:50 PM
> To:
>
many other entities for which this has been done so far, Alex has put
everything under cloud-engine-schema recently where you can find some more of
such examples.
Prachi
-Original Message-
From: Koushik Das
Sent: Sunday, December 15, 2013 9:50 PM
To:
Cc: Prachi Damle
Subject: Re: VMEn
Prachi, From the history I see that you added VMEntityVO. Any specific reason
for having both?
On 12-Dec-2013, at 2:36 PM, Koushik Das wrote:
> I see that both the VOs uses the same vm_instance table. What is the need for
> having 2 VOs for the same table? Should one be removed?
> Also VMEntit
I see that both the VOs uses the same vm_instance table. What is the need for
having 2 VOs for the same table? Should one be removed?
Also VMEntityVO I see a field called "speed" which is not there in
VMInstanceVO. Why this discrepancy?
Thanks,
Koushik
