Orabuntu-LXC 4.0-RC ChangeBlog

Haven’t done my changelog yet for the latest release of Orabuntu-LXC, but some mighty changes were brought into this release.

The dynamic DNS DHCP Server was moved itself into an LXC container (Xenial 16.04) so now Orabuntu_LXC doesn’t touch your existing bind9 or isc-dhcp-server configs at all. Also the Ubuntu LXC DNS DHCP container uses the faster image download too.

The required configs for sysctl.conf for Oracle on the Orabuntu_LXC host have been moved out of /etc/sysctl.conf and into /etc/sysctl.d/60-oracle.conf so sysctl.conf is now untouched too.

Same for /etc/limits.conf; it’s now updated via /etc/security/limits.d/70-oracle.conf so that limits.conf is not touched.

In fact, there are now only 3 files touched for Orabuntu_LXC install on the Ubuntu  LXC host, and one of them is /etc/NetworkManager/dnsmasq.d/local (see here for more info on that) so version 4.0-RC of Orabuntu-LXC represents an almost 100% transparent overlay of the Ubuntu host.

Orabuntu_LXC is also now totally re-runnable thanks to improvements such as iptables rule cleanups and many detailed improvements. Orabuntu_LXC re-runnable means that Orabuntu_LXC is like etch a sketch for multi-host multi-tier, RAC, multi-host Oracle EBS etc pilot projects. You can deploy as many Oracle-enterprise-software-install-ready fully-networked, all-Oracle-prequisites installed, Oracle Linux 5,6 or 7 containers (“hosts”) in literally less than 10 minutes to prototype something, and when done just blow them away and reset new in literally less than 10 minutes and optionally archive off your previous setups by just tar.gz’g your previous chroot container rootfs’s.

The SCST Linux SAN optional module has undergone major improvement as well. For Ubuntu kernels >= 2.6.30 there is NO custom kernel build required anymore for SCST thanks to Vladimir and Bart and the good people who bring us SCST as long as SCST branch 3.1.x is used. This has been incorporated into Orabuntu_LXC fully. The SCST SAN scripts build the entire file-backed iscsi Oracle ASM SAN in less than 10 minutes, configure all SCST groups, targets, devices, LUNs, etc, and there is a script that automatically builds your ASM LUNS (offers parameter [ external | normal | high] ASM redundancy build option) and  also configures the multipath.conf file automatically with all parameters, WWIDs, and aliases. Of course because it’s in bash, it’s easy to customize it to create your SAN in your own custom configuration.

Orabuntu_LXC uses iptables rules to provide WAN networking so your physical interfaces are untouched and remain fully independent of OpenvSwitch. 

There have also been enhancements to the Openvswitch-ovs design too. Orabuntu_LXC uses VLAN tagging to provide VLANs for the deployments. VirtualBox VMs can easily be added to the Openvswitch network using only the VBox GUI so LXC and  VMs can talk.

For the first time Orabuntu_LXC was designed to also be deployable in an Ubuntu VM so you can now build a multi-node Oracle app (eg RAC) in a single Ubuntu Linux VM which has its own integrated DNS DHCP. 

Orabuntu_LXC now supports user-supplied custom domain names and custom nameserver name. Orabuntu_LXC comes with a two-domain design so that its clear how to generalize to an n-domain design by editing the files and extending to n-domains.

Everything in Orabuntu_LXC is GNU3 Open Source license and written in straightforward bash code so you can fork Orabuntu_LXC and design it to suit your needs (remember to please share your tweaks, changes, improvements etc back to your github.com fork please).

All this and much more! Try out 4.0-RC here (it’s not at the github.com yet). Note that of course you can use Orabuntu-LXC to run anything you want in a container. Orabuntu-LXC provides Oracle Linux 5, 6 and 7 Containers, but you can create additional containers of other Linux distros at the LXC CLI, and, as long as you migrate them over to the OpenvSwitches the DNS DHCP uses those containers will also be in the same domain and network too. Support to deploy other non-Oracle-Linux distros directly from Orabuntu-LXC  is planned but does not have a roadmap date yet (because the primary goal of Orabuntu-LXC Is to enable running Oracle Enterprise software on Ubuntu Linux with NO hypervisor at bare metal network, compute, and storage performance). As always note that Oracle Corporation neither supports nor certifies Oracle on the Ubuntu Linux platform. 

Ubuntu Linux really turbocharged my career ever since I started working with Ubuntu 7 and 8 desktop back in my days as a TUSC Oracle consultant based in Chicago at the Butterfield Road HQ. Even then I had tried to build Oracle RAC on Ubuntu (pre-LXC) era, and I can only say LXC made my RAC-on-Ubuntu dream a straightforward no-hacks reality. Love; It’s what makes Ubuntu Ubuntu.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s