Alternatives to Oracle VM Server logo

Alternatives to Oracle VM Server

VirtualBox, VMware vSphere, Proxmox VE, KVM, and VMware Fusion are the most popular alternatives and competitors to Oracle VM Server.
1
0
+ 1
0

What is Oracle VM Server and what are its top alternatives?

It is a zero license cost server virtualization and management solution that makes enterprise applications easier to deploy, manage, and support. Backed worldwide by affordable enterprise-quality support for both Oracle and non-Oracle environments, it reduces operations and support costs while increasing IT efficiency and agility.
Oracle VM Server is a tool in the Virtualization Platform category of a tech stack.

Oracle VM Server alternatives & related posts

VirtualBox logo

VirtualBox

8.6K
6.9K
1.1K
8.6K
6.9K
+ 1
1.1K
Run nearly any operating system on a single machine and to freely switch between OS instances running simultaneously
VirtualBox logo
VirtualBox
VS
Oracle VM Server logo
Oracle VM Server

related VirtualBox posts

Tymoteusz Paul
Tymoteusz Paul
Devops guy at X20X Development LTD | 17 upvotes 589.2K views
Vagrant
Vagrant
VirtualBox
VirtualBox
Ansible
Ansible
Elasticsearch
Elasticsearch
Kibana
Kibana
Logstash
Logstash
TeamCity
TeamCity
Jenkins
Jenkins
Slack
Slack
Apache Maven
Apache Maven
Vault
Vault
Git
Git
Docker
Docker
CircleCI
CircleCI
LXC
LXC
Amazon EC2
Amazon EC2

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
Marcel Kornegoor
Marcel Kornegoor
CTO at AT Computing | 5 upvotes 198.8K views
atAT ComputingAT Computing
Linux
Linux
Ubuntu
Ubuntu
CentOS
CentOS
Debian
Debian
Red Hat Enterprise Linux
Red Hat Enterprise Linux
Fedora
Fedora
Visual Studio Code
Visual Studio Code
Jenkins
Jenkins
VirtualBox
VirtualBox
GitHub
GitHub
Docker
Docker
Kubernetes
Kubernetes
Google Compute Engine
Google Compute Engine
Ansible
Ansible
Puppet Labs
Puppet Labs
Chef
Chef
Python
Python
#ATComputing

Since #ATComputing is a vendor independent Linux and open source specialist, we do not have a favorite Linux distribution. We mainly use Ubuntu , Centos Debian , Red Hat Enterprise Linux and Fedora during our daily work. These are also the distributions we see most often used in our customers environments.

For our #ci/cd training, we use an open source pipeline that is build around Visual Studio Code , Jenkins , VirtualBox , GitHub , Docker Kubernetes and Google Compute Engine.

For #ServerConfigurationAndAutomation, we have embraced and contributed to Ansible mainly because it is not only flexible and powerful, but also straightforward and easier to learn than some other (open source) solutions. On the other hand: we are not affraid of Puppet Labs and Chef either.

Currently, our most popular #programming #Language course is Python . The reason Python is so popular has to do with it's versatility, but also with its low complexity. This helps sysadmins to write scripts or simple programs to make their job less repetitive and automating things more fun. Python is also widely used to communicate with (REST) API's and for data analysis.

See more
VMware vSphere logo

VMware vSphere

298
201
25
298
201
+ 1
25
Free bare-metal hypervisor that virtualizes servers so you can consolidate your applications on less hardware
VMware vSphere logo
VMware vSphere
VS
Oracle VM Server logo
Oracle VM Server
Proxmox VE logo

Proxmox VE

55
32
4
55
32
+ 1
4
Open-Source Virtualization Platform
Proxmox VE logo
Proxmox VE
VS
Oracle VM Server logo
Oracle VM Server
KVM logo

KVM

38
36
0
38
36
+ 1
0
Kernel-based Virtual Machine is a full virtualization solution for Linux
    Be the first to leave a pro
    KVM logo
    KVM
    VS
    Oracle VM Server logo
    Oracle VM Server
    VMware Fusion logo

    VMware Fusion

    31
    18
    0
    31
    18
    + 1
    0
    Simple Virtual Machines for Mac
      Be the first to leave a pro
      VMware Fusion logo
      VMware Fusion
      VS
      Oracle VM Server logo
      Oracle VM Server
      Qemu logo

      Qemu

      19
      10
      1
      19
      10
      + 1
      1
      A generic and open source machine emulator and virtualizer
      Qemu logo
      Qemu
      VS
      Oracle VM Server logo
      Oracle VM Server
      Xen logo

      Xen

      7
      6
      0
      7
      6
      + 1
      0
      Advancing virtualization in a number of different commercial and open source applications
        Be the first to leave a pro
        Xen logo
        Xen
        VS
        Oracle VM Server logo
        Oracle VM Server
        Parallels logo

        Parallels

        2
        2
        0
        2
        2
        + 1
        0
        Lets you run Windows applications like they were made for your Mac
          Be the first to leave a pro
          Parallels logo
          Parallels
          VS
          Oracle VM Server logo
          Oracle VM Server
          Ottomatica slim logo

          Ottomatica slim

          1
          8
          0
          1
          8
          + 1
          0
          Build and run tiny vms from Dockerfiles
            Be the first to leave a pro
            Ottomatica slim logo
            Ottomatica slim
            VS
            Oracle VM Server logo
            Oracle VM Server
            Virtuozzo logo

            Virtuozzo

            1
            1
            0
            1
            1
            + 1
            0
            An operating system-level server virtualization solution
              Be the first to leave a pro
              Virtuozzo logo
              Virtuozzo
              VS
              Oracle VM Server logo
              Oracle VM Server