Posts tagged vmForge

ipHouse Dot Logo

Tegile in the news, and so are we!

Congratulations to Tegile, whose press release today (picked up on multiple news sites, links below) includes one of the reasons we chose their HA2100EP storage array for our needs: Low latency & high throughput. We also needed iSCSI and F/C for our customers.

ipHouse has a Tegile Zebi storage array in production since March, 2012, and the increase in performance has been noticeable.

ipHouse Deploys Tegile’s Zebi Storage Array – Exciting to see Tegile growing and I’m still happy with my choice in new storage for our VMware clusters.

Newcomer gets out its box, plans to sell it cheaply to all comers

Tegile Selected as a Red Herring Top 100 North America Tech Startup

Our vmForge VDC clusters are peaking around 14,000 IOPS and the MASS solution is offloading about 11,500 IOPS via SSD. I wish I could graph this and show it to the public at large but I don’t have a way yet. (those are peaks, average is closer to ~8,000 IOPS with ~6,900 IOPS via SSD)

ipHouse Dot Logo

Into the vCloud API

We’ve been working on building a proper vmForge account creation and management site, so for the last couple of weeks I’ve worked a lot with the vCloud API. It’s a RESTful system, which means everything’s done by getting XML from and posting XML to a web server. It’s perhaps not the worst API I’ve ever worked with, but its tedious to work through. Even more so because their parser is insanely pedantic, to the point of requiring elements in a specific order. So that’s a point in PHP’s favor, that it maintains key order in associated arrays.


Dev Server Parity

Having a development server separate from your production server is a great idea. You can make changes without fear of breaking your production system. You can develop and test new features before they’re ready to roll out. And you can try out entirely new ideas without committing to development.

With that, it should be pretty clear that your development server should be as identical as possible to your production environment. It does you no good to write a new feature which leverages FiddlyC 4.2pl64 with QuirkyProc enabled if your production server is designed for and built and upon FiddlyC 3.

Fortunately, this is something which a virtual data center makes really easy. If you’ve based your production server on a template from your catalog, it’s just as easy to create two or three identical VMs based on that template as it is to create one. If you want to try something really new, create a new VM. If it doesn’t work out, tear it down and recover the resources.

You can even clone your current production vApp and servers into a template, if you have space available and can afford the downtime. You’ll need to shut down the vApp, then right-click on it and select “Add to Catalog”. Give it a name, and click OK. This will take some time, depending on how many VMs and how much disk is allocated. Once the process completes, don’t forget to restart your production vApp. But now you’ll be able to create a development environment which is exactly identical (aside from network names and addresses) to the original.

ipHouse Dot Logo

Hosting decision time: physical hosting vs cloud services

When it is time to change or update your hosting services, the choice between co-location and cloud services can become overwhelming.

This quick post on how virtualization and physical hosting compare may help you.

Included are hosting costs to host your own physical server the ipHouse data center versus different cloud providers and ipHouse virtualization services.


ipHouse Logo

Automagic Hacklisting of IP addresses

So, I got a little tired of FTP and SSH brute force attempts. I know that if you have strong passwords on your system, you can safely ignore them, and on customer systems behind real firewalls, I do so. However, on my personal systems, I have 0 problem blocking people who annoy me. So I installed pfBlocker on my virtual firewall to see what I could do.

pfBlocker is a package that has blacklist functions that supersede a couple older packages. I initially installed it a replacement for CountryBlock. The first thing I did was go through my logs and see which countries were the most obnoxious. China was the first to go, followed by Southeast Asia, and Venezuela. Sorry, I don’t want you accessing my network.

That allow took care of 70% of my attempted exploits. There are, however, plenty of compromised machines in the United States of America, so I had to think of something else.


Go to Top