Networking
Building a sandbox requires planning
Nov 14th
I mean it.
6 servers (5 operational as one is crashing itself repeatedly), 2 switches, and bandwidth.
This should be easy to do! I mean: what could go wrong?
DNS MX vs IPv4 & IPv6
Nov 12th
Yesterday – a very interesting issue cropped up…
Another local provider had email warnings being generated that they could not connect to our frontend MX servers.
The error itself was:
IPv6 is not supported
Which is not very clear for a reason email can not be delivered. I mean, my systems are working fine with IPv6 and we have native IPv6 connections occurring regularly.
So I scour our logs looking for case-insensitive ‘ipv6′ and all I find are hostnames with that listed, no errors, nothing with the word ‘supported’ listed.
The other provider thinks that maybe it is an issue on their side, which looks to be right, but for a different reason. Speculation: Their mail servers were trying IPv6 connections but were (at the time of discussion) not necessarily configured to handle IPv6 connections. No route (and router) for IPv6 means error. This makes sense.
But the culprit looks to be how different resource records are handled, and a probable mistake by me (humans…).
Apache 1.3 – you were loved
Feb 4th
So, across my RSS feed today, I saw a blurb…
Apache terminates ‘outated’ web server
What?
I clicked the link and was sent off to The Register for their report on the issue.
Apache 1.3 was released in July, 1998 – 12 years ago, and still in operation today.
At ipHouse – we use 1.3 as the tried and true Apache webserver on our cluster. We’ve not had either issues or problems; and security updates are few and far between. I guess after 12 years no one cares anymore to hack such old code or something.
Goodbye Apache 1.3, we had a long relationship, but your sister is younger and better equipped for todays Internet. Don’t cry, we’ll remember you fondly.
Hello Apache 2.2 – we are look forward to a long relationship on our network behind our F5 load balancers.
*sniffle*
Summary: Apache 1.3.42 is the final release according to the Apache Software Foundation. They recommend moving to Apache 2.2.14. Apache 2.0 will end once Apache 2.4 has been released, and finally, Apache 2.3.5 is in alpha stage.
Reference:
Example cost: Virtual Private Cloud on VMware
Sep 4th
In the last 6 months, I have helped multiple customers achieve their dream of a virtual machine environment built for them exclusively, but with abilities to control their virtual machine setup, configuration, turn up, tear down, etc. These dedicated infrastructure environments are in the ipHouse data center.
This isn’t ‘cloud computing’ as many people think of it (thanks to Amazon EC2 and the like), but it is pretty close to that vague definition, and with far more control available in terms of everything-vm-wise.
What do I mean? With this virtual private cloud, a customer can set up 3 Ubuntu systems, 2 Windows Server 2003, 1 FreeBSD, and 7 Windows Server 2008 systems. There really isn’t anything novel about this (again, reference Amazon EC2 and the like).
What is novel is that the customer can configure these VMs as they wish. Disk space allocation, partitioning, memory configurations, number of vCPUs. Basically, if you can do it on a physical server – you can do it virtually.
Another differentiating feature is that VMware vSphere 4 supports many operating systems while most public cloud providers offer a very limited number in comparison. This choice alone can be enough to warrant looking at this kind of solution.
No per hour fees, no storage fees (above what the customer has purchased), highly available (if configured to do so), dynamic resource scheduling (if configured to do so), bandwidth fees that are predictable. (see VMare vMotion and Storage vMotion, VMware HA, VMware DRS via website)
I’ll build a configuration example offering shared storage between the VMware physical servers. I’ll be doing some cost estimates for the per month fees. These estimates will be high and are purely shown for example. You would want to contact ipHouse Sales to get a real idea for the costs involved.
Virtualization and you – the business user
Feb 16th
Why virtualize? Better yet, why use virtualized server services for your business?
I’ll try to answer that question in this blog post, though from a service provider point of view, but I’ll try to remove my bias where feasible.
Summary: For many business needs, a virtualized server on a hosting providers infrastucture is very cost effective, very secure, and highly reliable. When those 3 items are combined, the argument to use separate, physical servers becomes moot. Virtualized server services are not for everyone, nor for ever task at hand, but for many, it is the more right solution.
Now that the summary is done, you can can read on for details as to why I think the above statements are true or just head on over to ipHouse and talk to sales and see what we can do for you, or both.
First, virtualization has a few meanings, but for this context, I am talking about the concept of taking a physical server (call it a host) and carving it into many virtual systems (call them guests) running concurrently. Here’s a picture from using VMware atoms to help visualize what I am getting at:
VM -> Host visualization
This allows the ability to spread the cost of a fast and expensive physical server amongst multiple guest systems.
