- 3,715,958 Users
- 2,242,917 Discussions
- 7,845,703 Comments
LDOMs using OPS Centre have problem
I went for LDOMs (VMs) on our Solaris Sparc Servers. We had two T5 servers and made a Pool and built our LDOMs and hosts underneath it. We also used Oracle Ops Centre 12.c to build our LDOMs and hosts.
The whole idea looked good on paper, as it looked similar to VMWare type, being able to move one VM from one physical host to another physical host. The limitation was that we could not change the LDOM (VM) name.
However, the problem started to surface, as we built more machines and wanted different functionalities, which are usually taken for granted.
- We could change the hostname of the machine, but it would not show up in the Ops Centre.
- We could change the IP address of the machine, from the host, but it would not show up in the Ops Centre. Doing it from the Ops Centre, say over net1, creates vnic. While this may not be a problem, this certainly was not the expected behaviour.
- The major problem was the inability to move the LDOM (VM) from one physical machine to the other while the machine is still running. We found a way out, but shutting down the machine, and moving the machine that way, but that was not I expected. The problem could be due to the lack of experience of the consultant who set it up.
However, the other two are real problems and should be addressed. If anybody has faced these problems and found a way round it, I would be grateful if they can share their knowledge. BTW, we have Ops Centre 18.104.22.1683. The latest one is 12.3 and I am not sure going to the most recent version of the Ops Centre will solve our existing problem.
Having seen these problem, as a person, who looks after the whole enterprise, I am not sure whether I would recommend anybody to go for Ops Centre or for that matter LDOMs