If I remember correctly you need to register with ULN to use OEM Linux management packs. Anyway, this topic has already come up a few times in the past. If you haven't done already, you may find the following useful:
1 person found this helpful
I cannot speak to the latest OEM. But when it was 12c, I did not like it. Patching was not reliable. It also seemed that every time the OEM DB was updated, the patching would break. I felt that I spent more time resolving OEM issues that I did using it to patch. In the end we ended up with spacewalk. I won't say that I have never had an issue, with spacewalk, but it's far less than OEM. Between spacewalk, ansible, and telegraf/influx/grafana, I have all that, I think, I need. I've been working on some spacewalk ansible modules the past week. If you are interested:
That is great! Thanks for the Ansible resources, I'll definitely take a look.
I read about other using OEM and Spacewalk definitely seems like the route I will stay on. It works and I understand it. Hopefully, it will work when it comes time for me to migrate to OL 8. I enjoy Spacewalk and looking at OEM it does appear more complicated than what I am looking for.
Thanks for all the feedback!
I am also curious about OL8 as well. I am not sure how that is going to be laid out. Currently there are only a few channels for 8. I checked and there are spacewalk bits in the app stream channel. They are 2.8. I am wondering if Oracle is getting ready to push spacewalk 2.8. I will probably hold off on 8 for a while. I still need to get use to the new packaging model. Cockpit is interesting, but I am not sold on it.
As a short rant. I hope Oracle ditches OVM and moves to oVirt/KVM. It has a lot more features out of the box.
1 person found this helpful
If it isn't possible to decide based on features or shortcomings perhaps you can apply other criteria. Comparing technical specifications is often not reliable or extremely useful. You will have to be lucky to find a particular requirement that only one product provides and where no work-around is available. However, forcing a product down peoples throat against better experience is never a good idea.
A DBA who is familiar with OEM will most likely appreciate and welcome an OEM solution. However, if your DBA does not want to take care of OS maintenance, the product won't matter. What I would probably not do is to purchase an OEM license to maintain a server farm in order to replace a working Spacewalk solution. OEM isn't for the faint of heart and introduces other complex issues that you probably don't want to deal with unless you rely on OEM to maintain your databases.
Oracle has already headed in the KVM/oVirt direction! It was announced on June 3rd...
Documentation for Oracle Linux Virtualization Manager (oVirt) are already published:
And this is Oracle Linux... Free to download, free to use, latest updates available for no cost.
SUPPORT for Oracle Linux KVM and Oracle Linux Virtualization Manager is available under Oracle Linux PREMIER Support.
I am aware. I was mainly stating that I hope Oracle abandons OVM and moves the direction to oVirt/KVM. I have OVM in my environment and I am not a fan. Things that lack are the ability to do snapshots through the webui (Simon Coter has supplied bash scripts for this). Another issue is that the hosts do not report downed paths to the manager. oVirt/KVM has a lot of this functionality. I also think that since it is an opensource upstream project, there is more active development that Oracle can leverage.