I recently installed VMware’s vSphere CLI 5.1 tools on a CentOS 6 x86_64 VM. Despite the rather reassuring documentation released by VMware, installing these tools was no simple task. I will outline the steps that I took for a successful installation of the vSphere CLI software, as some of it is not very obvious, especially for beginners.
Here are some tools I use on a fairly frequent basis, which may or may not be installed by default in your distribution. I highly recommend installing these tools during the provisioning stage of your system/environment because repositories aren’t always reachable on production systems. Furthermore, installing software on a running critical production system is often a tightly controlled process.
Part one, take the first full backup. At the present time, this code is still under development and should not be used on a production machine. However, I am posting it here for reference.
Eventually, this code is going to be included in a backup client I am developing that will interface with glusterfs and Amazon S3 storage.
Currently, this code is tested to run on Python v2.7.4 on a Fedora 18 machine. With all three python files, and any number of properly defined job xml files in the jobs.d/ directory, these scripts are currently functional.
If you are trying to make iptables survive a reboot in Debian Squeeze or Wheezy, you may find the following of use. After you get your iptables all squared away, save them to a text file with the incredibly handy /sbin/iptables-save command:
/sbin/iptables-save > /root/iptables.saved
This will create a text file in the /root directory containing lines that will be parsed by iptables when used with the iptables-restore command.
Next, add the following script to your system:
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.
I’ve been playing around with the latest stable release of GlusterFS, currently 3.3.1, for the last couple of weeks. GlusterFS is a scale-out cluster storage system that is extremely easy to setup and get running. However, during my short time working with it, I’ve stumble across a few items that were a little tricky to solve, and not well documented in the FAQ or elsewhere (that I found).
Problem: Attaching a Peer
The first problem I ran into was the inability to successfully attach a peer. After running gluster peer attach gluster-node2 I would receive “Probe unsuccessful” “Probe returned with unknown errno 107″ Suffice to say that when an application gives you an “unknown error” it is very demoralizing. Especially if you read Gluster’s documentation about how easy it is to setup. If you check in /var/log/glusterfs/etc-glusterfs-glusterd.vol.log you can generally find some text that points to the problem.
If you are considering obtaining a certification in Linux to advance your career, a great certificate to hold is the Red Hat Certified System Administrator (RHCSA). Red Hat is the premier enterprise Linux distribution, used in countless production environments worldwide. Red Hat certifications require a candidate to sit for a practical exam; there are no multiple choice questions, you must actually configure a live system.
Please excuse the formatting of this post. I am working to clean it up.
Throughout the web, you can find a collection of study guides for the RHCSA. I have created my own, which is a collection of my own notes and the notes of others. I highly recommend using the following book:
RHCSA/RHCE Red Hat Linux Certification Study Guide (Exams EX200 & EX300), 6th Edition (Certification Press)
Current exam objectives can be found here: http://www.redhat.com/training/courses/ex200/examobjective
Build the cloud on Linux! This year looks very promising for Linux when it comes to building your private cloud using open source technologies. Finally, Linux-based software and applications for building and managing your private cloud are coming to maturity. Look forward to more articles on creating and integrating your Linux Cloud throughout 2013!
On this page, you will find brief overview / review of different technologies available today that can help you move forward with building a successful cloud deployment.
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.