It doesn't break any functionality, just that ids won't be in sequence. It applies only to vm_instance id.
-----Original Message----- From: Nitin Mehta [mailto:nitin.me...@citrix.com] Sent: Wednesday, 20 February 2013 12:02 PM To: cloudstack-dev@incubator.apache.org Cc: Kelven Yang Subject: Re: randomlyIncreasingVMInstanceDaoImpl used instead of UserVmDaoImpl Would it break something ? And are the other resources like volumes, snapshots following the same logic as well ? Thanks, -Nitin On 20/02/13 11:45 AM, "Kishan Kavala" <kishan.kav...@citrix.com> wrote: >Kelven, >randomlyIncreasingVMInstanceDaoImpl is being used instead of >UserVmDaoImpl in ComponentContext.xml. Was this change intentional? > > <bean id="randomlyIncreasingVMInstanceDaoImpl" >class="com.cloud.vm.dao.RandomlyIncreasingVMInstanceDaoImpl" /> > >Vm DB Ids increase randomly as a result. > >mysql> select id from vm_instance; >+----+ >| id | >+----+ >| 1 | >| 2 | >| 3 | >| 11 | >| 12 | >| 13 | >| 14 | >| 21 | >| 25 | >| 30 | >| 38 | >| 45 | >| 52 | >| 56 | >| 60 | >| 68 | >| 73 | >| 79 | >| 80 | >| 81 | >| 82 | >| 83 | >+----+ >22 rows in set (0.00 sec) > > >Regards, >Kishan >
