For years, Linux administrators have been successfully using Samba winbind to integrate Linux with Active directory. While configuring a Linux host to join an Active Directory Domain is pretty simple, it still involves editing a few configuration files manually in most cases. The new software, realmd, changes all of that, and makes joining a Linux host to an Active Directory Domain easier than ever before!
I recently registered for an watched a Red Hat online seminar, Taste of Training for the upcoming Red Hat Open Stack course. Up until very recently, Red Hat OpenStack was only a technology preview, but now Red Hat is offering full support for OpenStack as part of it’s Red Hat Cloud Infrastructure product suite.
If you’re already familiar with OpenStack and/or Fedora, you can refer to this ’3 step’ guide from Red Hat: http://openstack.redhat.com/Quickstart Since you’re using Fedora 19, you’re not likely going to actually be able to complete the install in 3 steps as the guide suggests. I have found there are numerous steps that must/should be modified for a smooth installation, and I have compiled those steps here for my readers.
What I’m going to outline here are some of the necessary tips and methods I gleaned from hours of frustration. I also hope to include pretty screen shots for your convenience :).
I also intend to use Quantum networking, and (coming soon) GlusterFS as cinder storage.
Recently I filed a bug report with bugzilla regarding Fedora 18′s inability to boot after successful installation from all types of installation methods. Check the comment section of the Fedora 18 Review post for a direct link to the bug report.
Fedora 18, like many other fresh distros, utilizes GRUB2. However, Fedora 18 is the only distro I have personally encountered this problem of not booting after a successful install. This problem seems to be related to older hardware, or devices that lack the ability / video memory to use the highly graphical GRUB2 boot screen. There is no science in my previous statement, just an educated guess.
Fedora 18 was released in the middle of last month without too much fanfare. I suspect this is likely because the beta was extremely buggy; many people had trouble installing Fedora 18 Beta using the new Anaconda installer interface, and I myself even filed a bug report for GRUB2 not loading after installation (which is still outstanding).
Why should you be interested in Fedora 18? Well, aside from the fact that it’s already a very popular desktop distro, according to this article from ServerWatch.com, Fedora 17 and Fedora 18 will debut some of the features slated for release in RHEL 7, which is due out within the next year or so.
Currently I am testing the usability and performance of GlusterFS as a suitable virtual image store for the KVM hypervisor on Centos 6.
Hypervisor: Centos 6 x64, AMD Phenom II 1090T, 16G RAM DDR3 1033mhz. HDD: 7200RPM SATA II.
Storage Node: Fedora 18 x64. HP Proliant DL380 G4. 4G RAM DDR. RAID 1 SAS 10k.
VM-remote: Debian 6 x64. 2G RAM, 2 Virtual CPUs. RAW 8G disk on glusterfs volume.
VM-local: N/A (coming soon)
Network: Direct patch 1Gbps ethernet.
Fedora 18 beta has finally been released, after much delay. If you’re a follower of the Red Hat world, then you know Fedora 18 is likely going to serve as part of the upstream base for Red Hat Enterprise Linux 7, which is reportedly supposed to be released in beta form sometime next year. Also, I feel Fedora is now really offering a great user experience and deserves to be explored as a primary desktop distro. (more…)