• EMOC needs more attention and simplification.
• The integration with EM cloud manager should be straightforward.
• The ZFS interface (BUI) should be simplified.
• Modifying the OS template should be more flexible.
• Backup and restore using the Exabar tool should be redeveloped.
• You can not restore a deleted VM directly; you have to create a VM and then restore to it.
• You have a limitation with creating attached volumes to the VM (just 4 volumes including the template volume).
• The included ZFS doesn't support replicating data inside the local disk (attached volume). You have to convert the local storage (attached volume) to shared storage NFS.
• It doesn't support OVA.
• You can not share the internal ZFS storage with any platform other than Exalogic, so it is a closed box.

Currently the management functions of Exalogic are not as smooth as one would desire. Basically, it is designed with one objective in mind and that is performance. Because of this, the user interface might not be as user friendly as one would expect.

Also, one of the shortcomings of the current product is that it does not allow the internal ZFS to be expanded with multiple storage trays. This would be a very useful capability and it would also enable active-active failover at the storage layer.

Live Migration of the vServers will be a plus, as well as a more robust EMOC/EL control behavior.

There is still room for improvement, especially in regards to Oracle support.

Also, the SDP InfiniBand protocol needs to be usable in VM’s and patches for OVM installed for delivery.

The solution is prone to disk failures. This needs to improve. Over the past four years we've had to replace about six of them. They've failed almost every three to six months. 

The solution would benefit from the addition of real-time physical monitoring, like noting the temperature of the actual physical machine. The console should be able to tell you if it's overheating right away. Right now, it's not really in real-time. If I take my own temperature measurement versus what the console tells me, I find that my readings are more accurate than on the console itself.

Reporting and bug fixes should be applied for this product on-time.

The storage system needs to be improved. Perhaps the newer version (X4) is better but on X3, we had many storage issues.

I would like to be able to dynamically size the virtual servers. Today, this requires a full reboot.

With the shift to public cloud, and with Oracle releasing Oracle Public Cloud Machine and Oracle Private Cloud Appliance, the Exalogic X6-2 version was still released, but, clearer goals in the product roadmap are necessary to be able to affirm the improvements.

EMOC (Oracle Enterprise Manager Ops Center) is not very user-friendly, the user interface could be improved.

The administration of the VMs is cumbersome and lacks features that are taken for granted in other virtualization platforms – many administrative and availability features, even available in traditional OVM, are not available on Exalogic. This includes not having the ability to increase VM resources while the VM is online, or even being able to change CPU and memory sizes for a VM without recreating and cloning it. There is also no live migration feature available.

There's a lot of additional features I would like to see in the Exalogic. The user interface would be nice to better integrate into Enterprise Manager 13 and eliminate the whole EMOC layer to the Exalogic. That causes a lot of confusion both internally as well as clients that use the platform.

• Expand the templates and appliances like those that are available in OVM 3.4, such as the Oracle database firewall used in IPoIB private networks.
• Use of Virtual Network Services (VNS 1..02) for multi-tenancy (MT) use cases, and building secure enclaves.
• Continued evolution of the integration with EM 13c to extend MWaaS/PaaS and IaaS on Exalogic into the Oracle Cloud.
• Tell the great story of WebLogic Partitions for separation and promotion up/from the Oracle public cloud (using Exalogic as the on-premise platform of choice).
• Using OVAB or something like that to support Exalogic would be nice to have. The OVAB studio is not supported on Exalogic. That nurtured a service opportunity for application deployments using OVAB on Exalogic.
• Setting up different InfiniBand partitions in the EMOC would be a nice to have for additional MTs.

It's very expensive. Oracle Platinum Services (patching) is terrible, and we haven't had a patching exercise occur without significant problems and often impact to production operations.

- Management console: Awful to use it, complicated, too many options spread around many menus that don’t make any sense.
- Networking: Everything is locked. It doesn’t allow you to change an IP address after creating a VM.
- VM template creation: Too complicated. Better install manually.

• Highspeed transactions per second for business areas such as public-service, telco, banking, online store, payment gateway).
• Middleware application service, suchas statistics, data mining, could be better.

The solution needs to add a network virtualization feature similar to that of VxRail. If they could implement that, it would be great for the product.

Whenever there is a problem, opening a service request to get help from Oracle is an endless story.

For example, I had problems that I lived with for eight months. The answer that goes out of fashion is "the latest fw", but updating it also requires a downtime of 48 hours. It doesn’t mention when these interventions fail and must be rescheduled.

I would like to see more than four virtual disk capability in future versions of this product.

The current Exalogic X5-2 is enough for financial systems. Exadata's current speed is almost enough but sometimes much slower than the older mainframe systems, so some performance improvements would be helpful.