A good clarification for the planned new2.8 feature of allowing Shared Storage for VM repository
NOTE: - As of the posting of this information on ODA community 2.8 is not released ( planned for ~ Nov.2013)
=====
The following is a discussion from an internal Oracle ODA Email thread discussing the planned 2.8 functionality!
- I am posting this as this is a highly requested feature that the community can use for future planning
Q> "...Can you explain in more detail why the VM Repository can be on the shared disks but VMs store data cannot?.."
A> "... Keep in mind that the focus for the ODA is on the Oracle Database. OVM helps customers use hardware resources they might not need for their database, but the goal is to ensure a simple, reliable HA solution for the database. In addition, customers have expressed concern over the amount of storage possible in an ODA as not being enough for their data and growth, so opening it up to other uses impacts the space available for db data.
=====
The following is a discussion from an internal Oracle ODA Email thread discussing the planned 2.8 functionality!
- I am posting this as this is a highly requested feature that the community can use for future planning
Q> "...Can you explain in more detail why the VM Repository can be on the shared disks but VMs store data cannot?.."
A> "... Keep in mind that the focus for the ODA is on the Oracle Database. OVM helps customers use hardware resources they might not need for their database, but the goal is to ensure a simple, reliable HA solution for the database. In addition, customers have expressed concern over the amount of storage possible in an ODA as not being enough for their data and growth, so opening it up to other uses impacts the space available for db data.
1