Gives me a list of all configured network interfaces: 2: enp0s3: mtu 1500 qdisc pfifo_fast state UP qlen 1000 In VirtualBox I created a new host-only network called vboxnet1 and gave it the IP Address range of 192.168.56.x/24. ocp.lan And the hostname of the router is ‚router‘ (I was never good with names, though). $ subscription-manager repos -enable=rhel-7-server-rpms As I might be using it as another Node for OpenShift, I prepared a hard disk with 30GB.Īfter installing RHEL 7.3 as a minimal server, I registered the system via subscription-manager, attached my Employee SKU to the system via the WebUI under and enabled only the necessary repository: $ subscription-manager register I am giving my router VM 1 GB of RAM and 1 vCPU. At the end I decided against CentOS as my OpenShift VM should also be running RHEL. While Fedora is IMHO too new, I thought about CentOS or RHEL. Setting up the Router VMĪs I am working at Red Hat, it was clear for me that I have to use either Fedora, CentOS or RHEL for this machine.
#Setting up virtual box for mac os install#
The other VM, where I’d like to install OpenShift on, should only have host-only networking and should use the router VM as – well – the router. It should have dnsmasq being configured and should be acting as DHCP and DNS server. It should have two network interfaces (one NATed and the other one with Host-Only). The idea a friend came up with is to have 2 VMs. Which means, I would not be able to use OpenShift’s source to image mechanism where I am just providing a GIT repository and OpenShift is building an Image out of it. But the biggest one is that the pods of OpenShift are not able to talk to the outside of OpenShift as they are all bound to the internal network. And my idea was to bind OpenShift on the IP address of the host-only network, so that I can play with OpenShift from my Mac. One with NAT to use the host internet system and the other one with Host Only networking (host only means, that the Host and all VMs inside the same host-only network environment can see and access each other). So the next idea was to use two network interfaces. And this is nothing OpenShift can and / or should deal with. And this means the IP address changes every time I am in a new environment. But this mode also has a BIG drawback: I am working in different environments. So everything I do with my host system would also be possible with the VM (like internet etc.). Here the VM would be an official part of the overall network, where my host macOS is connected to as well. I would not be able to access my newly created apps.īridged Networking was my second thought. But this has one BIG drawback: I can not use my host system as I would like to. But I am not able to connect inside the VM from my macOS host system, except if I’d do ssh port forwarding. Because VirtualBox provides a set of different Network modes, where NAT and NAT Network allows the VM to use the host system as an internet gateway. And I want to make sure that I can do everything else from my macOS host.
So my decision was easy: I want to have a server VM only. I don’t really like the UI of Gnome or KDE.
Using VirtualBox and making sure you can use all the OpenShift services also from outside the virtual machine. Installing OpenShift 3.5 using the advanced method. Using the subscription-manager to attach a valid subscription to it. Until then I was only using either the Red Hat Container Development Kit (CDK) which is based on minishift since 3.0 or “oc cluster up” (and of course the great script set oc-cluster-wrapper done by our Evangelist team). I just wanted to understand everything which is necessary to use OpenShift. Now it was time for me to install OpenShift on my macOS based laptop inside a virtual machine. But from time to time I am getting a lot of questions on the infrastructure part of OpenShift as well.
#Setting up virtual box for mac os how to#
All I am talking about is the development part of it (so how to create apps, how to do release management with it etc.). Typically, required things should be there so that I can use them for my work.īut since some months I am travelling around to explain people the usage of OpenShift Container Platform. I am not necessarily one of those guys who love to dig into the infrastructure part too much. I am one of those guys who love to think about solving implementation problems.