Technological and coding misadventures!
Over yonder I was reading Luc’s blog entries on the AppFog Blog. While catching up I caught this video about my friend Eric Redmond’s book 7 Databases in 7 Weeks.
After you’re watching the video, if you’re interested in databases definitely pick up the book. I’d recommend it even if I wasn’t friends with Eric. 😉
Generally, you’d just install rvm (Ruby Version Manager) and execute this command.
rvm install 1.9.3
But alas, as happens sometimes, I ran into an issue related to the C compiler being found. Checking the log file for errors I found the message and went searching, finding an immediate solution thanks to good ole’ Stack Overflow. Simply executing the install with a specific C compiler will get things running smoothly.
rvm install 1.9.3 --with-gcc=clang
This part is pretty stupidly simple. Just download the installer and execute it. Once you’ve done this you’ve got all the gem bits and ruby bits you need to get the CLI for Cloud Foundry w/ the Iron Foundry .NET Additions!
Why am I installing Ruby 1.9.3 besides the obvious fact that it is Ruby, and awesome, and inherently great for getting shit done? I need the latest bits in order to install the latest Iron Foundry vmc client! You may ask, what’s wrong with the vmc client that Cloud Foundry has made? Well, the .NET bits aren’t included to appropriately identify when you have a .NET application. Basically, the vmc client is the exact same one that the core Cloud Foundry team puts together, but with the additions to know that there are Iron Foundry DEAs that can launch and run .NET Web Applications. To install this, execute the following command on OS-X.
gem install vmc-IronFoundry
If you ever run into the
“Could not find a valid gem ‘vmc-ironfoundry’ (>= 0) in any repository”
a quick call to update will usually resolve the issue. You may need to run this command with sudo, to insure you have access to the gems directory.
sudo gem update --system
At this point you can deploy a ton of languages and frameworks in addition to having .NET & SQL Server Support. I’ll be following up this with a how-to on deploying an ASP.NET 4.0 MVC Application, Node.js, and Ruby on Rails Application, scaling them to multiple instances, and best practices around that in the next month or three. In addition to that, I’ll have some great material coming up regarding some practices around getting these frameworks to work well together against data sources, across end points, via services and more.
Ok, I’ll admit a secret.
I haven’t read a single flippin’ SLA ever for cloud computing, hosting, managed hosting or other services. The main reason, is because it doesn’t matter unless you plan on prospectively suing or whining about your own bad architecture at some point. Sometimes, rarely, service is soooooo bad you have to pull out of the service, but generally in the vast majority of situations you can find information regarding the quality of a service. Google, Bing, and Yahoo are your friends when it comes to this. Also don’t forget your own network (you do have a network of people right?) Ask around, look around, read, research and check out anyone your going with. SLAs are a LAST RESORT item and should be treated as such.
Simply, the only thing I want in the SLA is something that covers me if I need to pull my services out of somewhere. Especially with cloud computing services (and I mean real cloud computing services that meet my baseline of geographically distributed, highly available, etc., etc like: AWS (yes I’ve done work with them), Rackspace (collaborated with them), Tier 3 (yes, I work for them), Windows Azure (yup, worked for them too and with their services), Joyent (I’ve actually never touched their services but I know what they are and what they’re capable of, no problem putting them in this category), and a few others.
So I dragged a few SLAs together for a comparo to see if there were many real differences between them. Here’s what I found from the following SLAs.
A great comparison, with grade rating of various SLAs is also available at IT Knowledge Exchange titled “A Tale of Three Cloud SLAs“. I got a few points from there in putting together this blog entry.
Overall it looks like AWS & Windows Azure both have fairly elaborate SLAs at first glance. However the company that really seems to have put together a solid “honor” based SLA is EngineYard’s. AWS & Azure both read like a bunch of lawyers sat around in a big room, that don’t understand anything about computing, and had one engineer throw words out that actually mean something – and then they ran rampant with those terms spliced through a few thousand pages of material. However, to summarize…
Both of their agreements tend to state that if YOU can PROVE that the downtime was caused by them then you can get recouped with service credits for those hours. Note, that it is a remuneration in credits, not in cold hard cash or otherwise. This seems to continue in others that I read too. But let’s loop back around for a second…
Do you want an SLA or service? That’s the real quistion. If you want service and you actually have your systems put together well then moving infrastructure to the cloud or platform operations to the cloud is what you want. The fact of the matter, most of the cloud services by Windows Azure, AWS, EngineYard, Tier 3, Heroku, or otherwise have an extremely high uptime. Expectations can EASILY be in the five 9’s range. However, it is up to you to make sure that YOUR SOFTWARE is going to be able to handle that.
One issue I have noticed is this expectation that you can put a traditional application in the cloud and then it magically has better high availability and such. This is absolutely WRONG. Cloud services give you the ability to build or expand “SCALABLE” applications to a higher uptime that can’t be achieved easily, or at all, with traditional hosting and data center operations. If you take SAP, Oracle’s Database, SQL Server, Exchange, or other NON-cloud type software and stick it in the cloud you’ll still have the traditional issues to deal with related to vertically designed software. These packages are not, nor were they intended to be run in geographically dispersed, fabric enabled, highly scaled, low cost cloud provisions. They don’t make use of map reduction, query enhancements, node based computing or storage integrity, or other characteristics that cloud computing brings to us.
So the real problem isn’t “is the cloud going to provide X 9’s of uptime…?” the real question is, “Will the software you’ve made, bought, or what to use going to take advantage of the features in the cloud that will allow it to have X 9’s of uptime?”
So really, focus the question around how your software works, not SLAs. That’s my two cents, maybe you still want that CYA in the SLA, but you won’t rest easy because there isn’t a whole lot of recourse if you stick crappy software in the cloud and then it falls over on you. So best of luck, but focus on that software, not on SLAs. Cheers!
The bikes of OS Bridge Attendees, we’re cool like that… (Click for full size image)
Today was the kick off of OS Bridge 2012. I jumped aboard my trusty steed (bicycle) for the mighty 6 block ride to the conference. Yeah, I could have just walked, but I just felt like getting their the fastest way possible. After arriving I was immediately faced with two great greetings. The first one went like this.
The “Do you do .NET still” Introduction
Hey Adron, how are you?
I’m good, and you?
Doing well, hey… so are you still doing that .NET stuff?
OS Bridge 2012
Funny how after all this time of using JavaScript, working with Node.js, Ruby, deploying with Sinatra and Rails and even tweaking around with Objective-C that I still get this question. I’ve branched out, I’m not a limited, mono-language, mort Microsoft programmer. Technically I never have been, I’ve always had a passion for things besides the Microsoft ‘just feed me’ stack. It just happened to pay my bills for a while. What is really happening here though, to paraphrase, is someone asking “so are you working with any interesting problems these days?”
The sad fact that most programmers, even people who code with .NET everyday, feel and observe almost nothing interesting happening in the .NET stack these days. Generally almost no startups use it. The vast majority of scientists don’t. Overall there isn’t much of it in colleges either these days. All for a deluge of reasons.
Rest assured, I’ve observed this, and this is merely a single reason that I commonly use many other languages. This is the reason I never get mad when people ask me this. I understand the preloaded context, it’s ok. Microsoft & their communities did this to the .NET stack, it’s unfortunate.
The simple truth is that many companies trying to solve hard problems, do genomic research, figure out how to launch rockets, and other really exciting interesting problems use almost anything except Microsoft’s stack. So yes, I’m doing .NET stuff, but I do a ton of other things based on what the job requires. I’m a firm believer of using the right tool for the job, and sometimes that is indeed .NET. So what was my answer?
Yeah, still doing .NET. Along with Node.js with JavaScript, Ruby, working on learning some Scala, how to test better in Javascript and Ruby, and even trying to schedule myself some time to jump into Go!
Yup, I was more prepared for this question than I was in the past.
The next introduction that came at me was much simpler.
Hey Adron, how goes things?
Things go well
What is it you do these days? I know you’re working with Iron Foundry and blog with New Relic sometimes, but what do you actually do besides that?
I went on to explain my rather exhaustive range of work I do. Ranging from the coding to the organizational community things. All good stuff that led our conversation down different routes.
Both of these introductions went well and I dig both of them, albeit I need a pre-printed response to the .NET question. Breakfast muffins were great and then the several hundred people at the conference went to find seats in the main sanctuary room for the keynote.
A few key quotes from the keynote by Sumana Harihareswara (@brainwane), via Twitter.
“@demew: #**osb12** is already off to a ridiculous start because of the KEYNOTE ORGANIST” Really?
Larissa Shapiro @larissashapiro
to change open source girls have to be able to say about the local open source event “its okay mom, there will be other girls there”#osb12
“Help these kids fight their parents!” #osb12
The summary of the keynote is one that should resound loudly in America,
“…being free is better than being safe…”
NGINX Talk w/ Cliff Wells
Nginx, Overview and Deployment
The first session I attended was the session on Nginx by Cliff Wells (@cliff_wells). A few notes from this session:
There were a few other bits, but those were the main takeaways. The main reason I jumped into this session was because I wanted a more context around what NGINX is exactly. I got some of this, which is handy to know since this server is used in so many projects I’ve been working recently. Specifically it is readily used in Cloud Foundry.
This talk seemed like a keen match to a lot of the work I do. I’m remote for about 90% or more of my work these days. I code remotely, work up blog entries, articles, media calls, and related communications all from locations that are remote from their point of presence.
…errr, well, I tried to attend this one. Some work coding priorities trumped the evening session so I had to jet out of the conference. I did, as I coded away, kept an eye on all the tweets coming from the conference. It sounded like a great session. I have, unto the topic, a whole lot more to add. So maybe I can just spawn this into a blog entry at some point.
With that, have no fear, I’ll be back tomorrow for day #2 & the respective coverage of the event!
I just got signed up for Cloud Connect Chicago and started checking out some of the talks. One talk jumped out, being that it is about PaaS Technology. After reading it though I immediately felt the need to straighten out some things that looked misleading. Maybe the presenter (JP Morgenthal) will lay these things out well for the attendees, but at this point I don’t know that. I’m making a point to see this session while I’m at Cloud Connect. I’m curious to see how he lays out the content. Here’s the description for the “Navigating PasS: Your Road Map for Application Development“. Hopefully I’ll see you there!
Platform-as-a-Service (PaaS) has most simply been described as the set of tools above the infrastructure (hypervisor) and contains the applications being served out of the cloud. However, this description covers a large body of resources. Navigating the use of PaaS for application development and delivery requires a very wide understanding of the computing environment and doesn’t fully relieve the user from understanding the infrastructure that is used to operate the PaaS.
First off, the thing that really caught my attention about this session is that it sounds like someone from a very specific company trying to sell a very specific thing wrote this initial description. A PaaS, or Platform as a Service does NOT have to run on an infrastructure hypervisor. It has ZERO association to a hypervisor. All a PaaS should do, ought to be, and generally is regardless who it is made by or who is running it, is a set of software that automates deployment, application distribution to systems serving the application, and generally simplifies the deployment of an application and to some degree databases or data repositories. There is, and should NOT be, any type of coupling, especially any tight coupling, to some hypervisor.
In summary, a PaaS should have zero to do with a hypervisor. It should rely on a simple operating system that has minimal resource overhead and minimal requirements. Take Cloud Foundry or Open Shift. They rely on some of the most capable operating systems, Red Hat Linux (RHEL) and Ubunut LTE to run the PaaS Systems. These are by far some of the best choices in the industry to determine the core of where a PaaS should run. Based on this, it is an operating system, at the core that enables these systems. NOT a hypervisor. If you’re looking to base your PaaS System off of a hypervisor, I’m afraid you’ll have made a severe mistake right off the bat.
Now if you put your Red Hat or Ubuntu OS on a hypervisor, or straight on the metal, you’re fine. Just don’t cross the seperations of concern from the operating system to travel from PaaS to hypervisor. That’d just be…
wrong.
One thing I agree with in the above description and I’m betting JP will put some emphasis on this part of the discussion, is that you absolutely need to have an understanding of your infrastructure that runs underneath your PaaS. There are a multitude of reasons to keep in mind what the infrastructure is doing underneath and how it handles what you’re deploying to your PaaS. Here’s two hugely important topics of concern when you deploy a PaaS into any environment.
It looks like the session will cover a lot of these topics. So if you’re looking to attend, I highly suggest checking out JP’s session. I’ll be looking forward to his approach to many of the other topics (check out the site description) such as those I just mentioned along with security, deployment concerns, deploying a single language PaaS (like Apprenda, Cloudbees, etc) and other solutions. In addition to that, I’ll likely be bringing an arsenal of questions, see you all and JP at Cloud Connect!
Alolita Sharma 
kalium