The Constitutional issues of cloud computing

Would James Madison, for example, agree with some current interpretations of the Fourth Amendment, which hold that old-fashioned letters stored in a dresser drawer enjoy stronger legal protection against search and seizure than an e-mail stored on the Web or a private post left for a friend on Facebook?

In a world where every computer is connected, where it doesn’t matter whether your e-mail is on the hard drive in your bedroom or a server half a world away, where your critical company documents can be viewed from anywhere, where would the Founding Fathers draw the line for law enforcement? The “cloud,” already well formed with Hotmail and Google docs, is a potential treasure trove for police investigators. But how can we make sure the cloud doesn’t rain all over Americans’ Fourth Amendment rights to avoid unfair searches?

Read more (off site)

How to Build a Lean Startup with Free and Open Source Software – Part 1

I have been reading recently about the “Lean Startup” concept, which is funny since I have been working with and been part of more than a few without knowing there is a nifty catch phrase for them. So now I am all up on the lingo and hash tag #leanstartup I can speak on it. Today is the perfect time to take a gamble and dive into a lean startup. Being that there are so many free tools and services you can use along with very inexpensive solutions to infrastructure that were not available even a few years ago. By using the power of Open Source software, free online services, and cloud computing one can build a scalable and very cost effective lean startup.

Core Needs

Let’s first look at your new companies hosting and servers.  being that you are lean you may most likely be working from home.  So let’s look at hosting and services you will need in order to host some of the Open Source applications will will talk about in a moment.  In my experience the basic things you need to get going in terms of setting up shop are the basics:

Future: Amazon’s ‘Think Clouds’ are Data Aware

As we understand it from the discussion on stage, a Think Cloud is a “body of knowledge” that is a real-time information base of Amazon cloud that can be pivoted all the way down to the threads and individual data concurrency. It would be an index that acts like a control point that helps define movement of data through a servers and compute tasks. Looking at the journey from the data point of view, including data about the environment itself and how to repair itself when damaged and keep data concurrency in tact.

Read more (off site)

Cloud security: Is it raining in the cloud?

SC has a good write up on cloud computing security:

Cloud computing, as least as a concept, is being driven largely by economics. It is generally less costly to run applications, add capacity and increase storage in the cloud, rather than investing in new hardware and software, and bringing on additional staff and beefing up networking.

“Cloud computing will happen because it has too much of an economic incentive and developer support – applications can be quickly added and developers can have a single place to maintain source code,” says Vatsal Sonecha, VP, business development & product management at TriCipher.

Overall, incentives include application-deployment speed, lower costs and fast prototyping. These are strong drivers. So much so that Gartner predicts that by 2012, 80 percent of Fortune 1000 companies will pay for some cloud computing service, and 30 percent of them will pay for a cloud computing infrastructure.

That is not to say that entire data centers will be moving to the cloud, at least in the largest companies. But for certain solutions, the cost benefits are hard to ignore.

Read More. . . (off site)

Locking Down Access to Scalr Web Interface

I wanted to touch briefly on the security concerns for having Scalr accessible via the Internet. If you are running your own install of Scalr this is an important factor before even adding the first farm. For my own sake I will not getting into my exact setup, but instead talk about a few approaches to locking down access to Scalr.

Possibly the best approach is to limit access to Scalr interface to internal network requiring users to use OpenVPN or some other VPN solution to access internal resources which would include Scalr.  If you are hosting Scalr on an AWS instance be sure to set the security group to only allow the port you are running for VPN.  You can find a quick and dirty howto for OpenVPN on an EC2 instance at Google Books.

Another option is to use SSL and mod_access (Apache 1.3) or its renamed equivalent in Apache 2.2 mod_authz_host to limit those who have access to Scalr interface.  You should for sure at least use SSL to access Scalr.  You can also add a layer of authentication for good measure using Apache Basic Authentication.

Being that Scalr controls the rest of your AWS setup it is by far the one thing you want to lock down as much as possible.

Using Subversion to Update Content with Scalr Scripts

I wanted to touch again on the use of Subversion (SVN) to populate the /var/www of app servers on Scalr.  Basically the issue is how to add your web content to a new instance once it has automagically launched a new instance due to high load.  So Scalr will launch another app role once the server reaches a load threshold you have previously set. So the issue is I can have the instance started, but once it has launched the /var/www needs to be populated for that server to be able to serve content via load balancer.

Scalr Scaling Settings

This is where SVN and Scalr Scripting come into play.  I keep all my site content in a SVN repo.  So I link to whatever production tag I want to be live at that time.  In order to get the directory populated I make a simple script to do an svn checkout of that tag to /var/www.  A simple bash script is added to do the checkout and is added to the “OnHostUp” option.  This way once the server sends its SNMP trap saying it is up the script will be executed.  This is also a helpful means of updating your servers to a newer build.  I DO NOT checkout the tag directly into /var/www instead I make a symlink to /var/svn where the tags are checked out.  So when it is time to roll out a new production tag I simply checkout the new tag to /var/svn and redo the symlink to point at new tag.  This way if there is an issue that was not forseen in the QA process I can roll back to known good tag by redoing symlink.  This is an easy but very effective way of using Scalr scripts and SVN to manage content loading on servers.

Using Zabbix to Monitor Scalr Farms

Since I have been using Scalr to manage my Amazon Web Services farms I have been wanting more monitoring in terms of statistical information on services, traffic, disk usage, and uptime to name a few.  Scalr has built in means of basic event notifications such as host up, host down, etc.  Along with providing very basic load statistic via RRDtool.  In the past I have always used Zabbix for most projects I have worked on so I wanted to be able to use it with Scalr.  I am still testing the setup I am going to speak of so please keep that in mind.  This is NOT a howto, but more of a brainstorming of how I plan on getting Zabbix integrated into my Scalr setup.  In the Zabbix documentation (PDF) there are a few ways to use the auto-discovery that they cover (page 173).  You can have Zabbix monitor a block of IPs to find new Zabbix Agents running for example.  So here is what I will have my Zabbix Server do:

• Look for new Zabbix Agents on my AWS internal IP range.
• If the system.uname contains “Scalr” it will add to Scalr server group
• Server must be up for 30+ minutes

There will be other stipulations in order to get the server added to Zabbix.  I will have system templates for each of my Scalr AMI roles.  Once the server is added to Zabbix it will add them to to their respective groups and monitor for items and triggers listed in the system template.  There will also be a rule to remove old instances after 24 hours from Zabbix after receiving the host down trigger.  This way I will not have a bunch of old instances that were once monitored still cluttering Zabbix database.  If you happen to also have Windows AWS instances you can add a rule to monitor these as well.  The AMI just needs to have the Zabbix Windows Agent installed.

Architecture of a Scalr DNS Infrastructure

When I decided to take the route of running Scalr on our own servers to manage our Amazon Web Services farms one important consideration was Scalr’s use of DNS servers to change records.  I made the choice of hosting our own DNS infrastructure in order to keep initial cost down.  But also to allow us the flexibility to change and control our DNS internally.  So now onto my approach to doing this most effectively.  Firstly two separate DNS servers were chosen of the self-managed dedicated server form.  One server was chosen in a west coast location while the second was on the east coast.  Being that more of our traffic come from the western states the NS1 was selected accordingly.  Now I used two non-Scalr managed AMIs to run our NS3 and NS4 servers.  Each in a separate AWS datacenter.  The idea being that the internal custom bundled AMIs for Scalr I built would use the NS3 and NS4 for their internal DNS.  I find this to be an excellent mix of using AWS and old fashioned dedicated servers to manage our DNS.

Cloud Computing and BSD’s Place In It

I am a Linux guy.  But I am also a big lover and user of OpenBSD and FreeBSD.  This got me to thinking of BSD and it’s place in Cloud Computing.  In terms of Amazon Web Services EC2 I have yet to see it.  When checking the FreeBSD and OpenBSD projects I have yet to see it at all in a Xen form.  There are a few posting regarding getting it to sort of work.  There is a wiki page for FreeBSD project dedicated to a Xen port.  I believe this lack of Xen support will not help BSDs to compete with Linux flavors.  I would love to be able to use BSD for certain roles.

Using Scalr to Manage Amazon Web Services

I have been using Amazon Web Services for some time now and decided to use the Open Source Scalr Project to manage my farms on AWS.  After overcoming many hurtles to getting Scalr running successfully I have been using it to manage my farms for about a month.  Compared to the initial outlay required my RightScale the time it took to get Scalr running was nominal.  Plus I like the ability to have a developer tweak the functionality of Scalr to fit our business requirements.  There is an active Google Group for Scalr that I have used to solve most of my issues.  People also have the option of using Scalr.net as a pay per month solution to manage their AWS farms.  I chose to host my own instance of Scalr since we are doing large scale hosting and the previously mentioned need to customize it.  I do enjoy the ease Scalr provides in bundling new custom roles I build for our various application servers.  It allows you to simply press a button to save a new role for future use.  Along with its ability to auto-scale as traffic dictates those are the two biggest pluses for me in using Scalr.

I will be adding more on my experiences with Scalr in coming days.  If you are installing on CentOS5 I have some install notes I posted here.