but, i got them on sale!

Back in August 2008, I had a one-week “quick start” professional services engagement in Nutley New Jersey. It was a supposed to be a super simple week: install HP Server Automation at BT Global.

Another ProServe engineer was onsite to setup HP Network Automation.

Life was gonna be easy-peasy – the only deliverable was to setup and verify a vanilla HPSA installation.

Except, like every Professional Services engagement in history, all was not as it seemed.

First monkey wrench: our primary technical contact / champion was an old-hat Sun Solaris fan (to the near-exclusion of any other OS for any purpose – he even wanted to run SunOS on his laptop).

Second monkey wrench: expanding on the first, out technical contact was super excited about the servers he’d gotten just the weekend before from Sun because they were “on sale”.

It’s time for a short background digression. Because technical intricacies matter.

HP Server Automation was written on Red Hat Linux. It worked great on RHEL. But, due to some [large] customer requests, it also supported running on Sun Solaris.

In 2007, Sun introduced a novel architecture dubbed, “Niagara”, or UltraSPARC T1, which they offered in their T1000 and T2000 series servers. Niagara did several clever things – it offered multiple threads running per core, with as many as 32 simultaneous processes running.

According to AnandTech, the UltraSPARC T1 was a “72 W, 1.2 GHz chip almost 3 times (in SpecWeb2005) as fast as four Xeon cores at 2.8 GHz”.

But there is always a tradeoff. The tradeoff Sun chose for the first CPU in the product line was to share a single FPU (floating point unit) between the integer cores and pipelines. For workloads that mostly involve static / simple data (ie, not much in the way of calculation), they were blazingly fast.

But sharing an FPU brings problems when you need to actually do floating-point math – as cryptographic algorithms and protocols all end up relying upon for gathering entropy for their random value generation processes. Why does this matter? Well, in the case of HPSA, not only is all interprocess, intraserver, and interserver communication secured with HTTPS certificates, but because large swaths are written in Java, each JVM needs to emulate its own FPU – so not only is the single FPU shared between all of the integer cores of the T1 CPU, it is further time-sliced and shared amongst every JRE instance.

At the time, the “standard” reboot time for a server running in an SA Core was generally benchmarked at ~15-20 minutes. That time encompassed all of the following:

  • stop all SA processes (in the proper order)
  • stop Oracle
  • restart the server
  • start Oracle
  • start all SA components (in the proper order)

As you’ll recall from my article on the Sun JRE 1.4.x from 6.5 years ago, there is a Java component (the Twist) that already takes a long time to start as it seeds its entropy pool.

So when it is sharing the single FPU not only between other JVMs, but between every other process which might end up needing it, the total start time is reduced dramatically.

How dramatically? Shutdown alone was taking upwards of 20 minutes. Startup was north of 35 minutes.

That’s right – instead of ~15-20 minutes for a full restart cycle, if you ran HPSA on a T1-powered server, you were looking at ~60+ minutes to restart.

Full restarts, while not incredibly common, are not all that unordinary, either.

At the time, it was not unusual to want to fully restart an HPSA Core 2-3 times per month. And during initial installation and configuration, restarts need to happen 4-5 times in addition to the number of times various components are restarted during installation as configuration files are updated, new processes and services are started, etc.

What should have been about a one-day setup, with 2-3 days of knowledge transfer – turned into nearly 3 days just to install and initially configure the software.

And why were we stuck on this “revolutionary” hardware? Because of what I noted earlier: our main technical contact was a die-hard Solaris fanboi who’d gotten these servers “on sale” (because their Sun rep “liked them”).

How big a “sale” did he get? Well, his sales rep told him they were getting these last-model-year boxes for 20% off list plus an additional 15% off! That sounds pretty good – depending on how you do the math, he was getting somewhere between 32% and 35% off the list price – for a little over $14,000 a piece (they’d bought two servers – one to run Oracle RDBMS (which Oracle themselves recommended not running on the T1 CPU family), and the other to run HPSA proper).

Except his sales rep lied. Flat-out lied. How do I know? Because I used Sun’s own server configurator site and was able to configure two identical servers for just a smidge over $15,000 each – with no discounts. That means they got 7% off list …

So not only were they running hardware barely discounted off list (and, interestingly, only slightly cheaper (less than $2000) than the next generation T2-powered servers which had a single FPU per core, not per CPU (which still had some performance issues, but at least weren’t dog-vomit slow), but they were running on Solaris – which had always been a second-class citizen when it came to HPSA performance: all things being roughly equal, x86 hardware running RHEL would always smack the pants off SPARC hardware running Solaris under Server Automation.

For kicks, I configured a pair of servers from Dell (because their online server configurator worked a lot better than any other I knew of, and because I wanted to demonstrate that just because SA was an HP product didn’t mean you had to run HP servers), and was able to massively out-spec two x86 servers for less than $14,000 a pop (more CPU cores, more RAM, more storage, etc) and present my findings as part of our write-up of the week.

Also for kicks, I demoed SA running in a 2-CPU, 4GB VM on my laptop rebooting faster than either T1000 server they had purchased could run.

Whats the moral of this story? There’s two (at least):

  1. Always always always find out from your vendor if they have a preferred or suggested architecture before namby-pamby buying hardware from your favorite sales rep, and
  2. Be ever ready and willing to kick your preconceived notions to the sidelines when presented with evidence that they are not merely ill thought out, but out and out, objectively wrong

These are fundamental tenets of automation:

“Too many people try to take new tools and make them fit their current processes, procedures, and policies – rather than seeing what policies, procedures, and processes are either made redundant by the new tools, or can be improved, shortened, or – wait for it – automated!”

You must always be reviewing and rethinking your preconceived notions, what policies you’re currently following, etc. As I heard recently, you need to reverse your benchmarks: don’t ask, “why are we doing X?”; ask, “what would happen if we didn’t do X?”

That was a question never asked by anyone prior to our arrival to implement what sales had sold them.

what is “plan b” for iot security?

Schneier has a recent article on security concerns for IoT (internet of things) devices – IoT Cybersecurity: What’s Plan B?

We can try to shop our ideals and demand more security, but companies don’t compete on IoT safety — and we security experts aren’t a large enough market force to make a difference.

We need a Plan B, although I’m not sure what that is. Comment if you have any ideas.

There are loads of great comments on the post.

Here’s the start of some of my thoughts:

There are a host of avenues which need to be gone down and addressed regarding device security in general, and IoT security in particular.

Any certification program could be good .. right up until the vendor goes out of business. Or ends the product line. Or ends formal support. Unless we go to a lease model for everything, you’re going to have unsupported/unsupportable devices out there.

We can’t have patches ad infinitum because it’s not practical: every vendor EOLs products (from OSes to firearms to DB servers to cars, etc).

A few things which would be good:

  • safe/secure by default from the vendor – you have to manually de-safe it to use it (like a rifle which only becomes usable/dangerous/operable when you load a cartridge and put the safety off)
  • well-known, highly-publicized support lifecycles (caveating the vendor going out of business)
  • related to the above, notifications from the device as it nears end of support
  • notifications from the device as well as the vendor that updates/patches are available
  • liability regulations – and an associated insurance structure – affecting businesses which choose to offer IoT devices across a few levels:
    1. here it is :: you deal with it || no support, no insurance, whatever risk is there is your problem
    2. patches / updates for 1 year || basic insurance / guarantee of operation through supported period, as long as you’re patched up to date
    3. patches / updates for 3 years ||
    4. patches / updates for 5 years || first-level business offering || insurance against hacks / flaws that have been disclosed for more than 90 days so long as you have patched
    5. patches / updates for 10 years || enterprise / long-term support || “big” insurance coverage (up to a year, so long as you’re yp-to-date) || proactive notifications from the vendor to customers regarding flaws, patches, etc

There are probably other things which need to be considered.

But there’s my start.

david pogue’s 1996 mac holiday sing-along

Thanks, Archive.org!

God Rest Ye Copland Programmers
(to the tune of “God Rest Ye Merry Gentlemen”)

God rest ye Copland programmers,
It’s finally Christmas Day.
You’ve all worked 20-hour shifts
Beginning back in May.
No wonder after such neglect
Your spouses moved away.
The last real meal you had
Was late last year–
That’s what we hear;
And since then you’ve lived on
Pizza, Coke, and beer.

Your bosses change, and change their minds,
Is Copland off or on?
Are last week’s OS plans in place
Or now completely gone?
God rest ye well this Christmas Day,
You’d better sleep in late–
It’s the last sleep you’ll get till ’98.
Isn’t that great?
It’s the last day off you’ll have till ’98!

The Bill Gates Song
(to the tune of “The Christmas Song”)

Netscape roasting on an open fire,
Apple begging on its knees,
Photo popping up on Time magazine,
Yes, Bill Gates dreams of days like these!
Everybody knows he’s never fully satisfied,
Throws himself behind each task,
World dominion is his company’s goal.
Well, hey, is that so much to ask?
He knows the world is in his sway,
We’ll buy whatever software he might toss our way,
We’ll surf his Internet, watch his TV,
He’ll take us anywhere we ask him–for a fee.

And so we’re offering this simple prayer,
To Bill and all his MS grunts:
Since we all follow any standard you write,
Make it good, please,
Make it good, please,
Make it good, please, just once!

Gil Amelio’s Coming to Town!
(to the tune of “Santa Claus Is Coming to Town”)

You better watch out,
Absurd as it sounds,
‘Cause Apple’s about
To lose a few pounds–
Gil Amelio’s coming to town!

He’s making a list,
And trimming the rolls
Of projects that missed
Their revenue goals–
Gil Amelio’s coming to town!
He knows what’s losing money,
Like eWorld, PowerTalk . . .
You’d better make your project work
Or prepare to take a walk!

Though you follow his lead
Right out the back door,
You know he’ll succeed–
He’s done it before!
Gil Amelio’s coming to town!

(to the tune of “Jingle Bells”)

Nine-tenths of a gig,
Biggest ever seen,
God, this program’s big–
MS Word 15!
Comes on ten CDs,
And requires–damn!
Word is fine, but jeez–
60 megs of RAM?!

Oh! Microsoft, Microsoft,
Bloatware all the way!
I’ve sat here installing Word
Since breakfast yesterday!
Oh! Microsoft, Microsoft,
Moderation, please.
Guess you hadn’t noticed:
Four-gig drives don’t grow on trees!

I’m Dreaming of a Clean System
(to the tune of “White Christmas”)

I’m dreaming of a clean System,
Something that fits on one CD.
Each component matches,
Not bits and patches,
Unlike 7-5-point-3.
I’m longing for a dream System,
Small, stable, fast, and trouble-free.
What we want, I think you’ll agree,
Is called System 6-point-oh-3!

Violent Night
(to the tune of “Silent Night”)

Silent Mac, broken Mac!
System bombed, screen went black.
Books suggested things; I tried ’em all:
Shift key, desktop file, clean reinstall.
Now my deadline is tight,
This Mac’s been silent all night.

Violent night, horrible night!
Lost my cool, filled with spite,
Threw my Mac through the balcony door
Watched it fall from the 20th floor,
Now I’m sleeping in peace;
Thank God I had it on lease.

Prove It’s So!
(to the tune of “Let It Snow”)

Oh, the papers say Apple’s dying,
But before we start good-byeing,
We should call them all up and go,
“Prove it’s so! Prove it’s so! Prove it’s so!”

They say “Mac OS software’s scarcer.”
We say, “Read those numbers, there, sir,
Sales continued this year to grow.
There ya go, there ya go, there ya go!”

When they tell us Win 95
Made the Mac’s famed advantages ebb,
We’ll say, “Why, then, do Macs now drive
60 percent of the Web?”

We can win our PR reversal–
Make the Mac be universal–
Though we may have some years to go,
Make it so, make it so, make it so!

Happily Addicted to the Web
(to the tune of “Winter Wonderland”)

Doorbell rings, I’m not list’nin’,
From my mouth, drool is glist’nin’,
I’m happy–although
My boss let me go–
Happily addicted to the Web.
All night long, I sit clicking,
Unaware time is ticking,
There’s beard on my cheek,
Same clothes for a week,
Happily addicted to the Web.

Friends come by; they shake me,
Saying, “Yo, man!
Don’t you know tonight’s the senior prom?”
With a listless shrug, I mutter, “No, man;
I just discovered letterman-dot-com!”

I don’t phone, don’t send faxes,
Don’t go out, don’t pay taxes,
Who cares if someday
They drag me away?
I’m happily addicted to the Web!

fallocate vs dd for swap file creation

I recently ran across this helpful Digital Ocean community answer about creating a swap file at droplet creation time.

So I decided to test how long using my old method (using dd) takes to run vs using fallocate.

Here’s how long it takes to run fallocate on a fresh 40GB droplet:

root@ubuntu:/# rm swapfile && time fallocate -l 1G /swapfile
real	0m0.003s
user	0m0.000s
sys	0m0.000s

root@ubuntu:/# rm swapfile && time fallocate -l 2G /swapfile
real	0m0.004s
user	0m0.000s
sys	0m0.000s

root@ubuntu:/# rm swapfile && time fallocate -l 4G /swapfile
real	0m0.006s
user	0m0.000s
sys	0m0.004s

root@ubuntu:/# rm swapfile && time fallocate -l 8G /swapfile
real	0m0.007s
user	0m0.000s
sys	0m0.004s

root@ubuntu:/# rm swapfile && time fallocate -l 16G /swapfile
real	0m0.012s
user	0m0.000s
sys	0m0.008s

root@ubuntu:/# rm swapfile && time fallocate -l 32G /swapfile
real	0m0.029s
user	0m0.000s
sys	0m0.020s

Interestingly, the relationship of size to time is non-linear when running fallocate.

Compare to building a 4GB swap file with dd (on the same server, it turned out using either a 16KB or 4KB bs gives the fastest run time):

time dd if=/dev/zero of=/swapfile bs=16384 count=262144 

262144+0 records in
262144+0 records out
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 4.52602 s, 949 MB/s

real	0m4.528s
user	0m0.048s
sys	0m4.072s

Yes, you read that correctly – using dd with an “optimum” bs of 16KB (after much testing different bs settings) takes ~1000x as long as using fallocate to create the same “size” file!

How is fallocate so much faster? The details are in the man pages for it (emphasis added):

fallocate is used to manipulate the allocated disk space for a file, either to deallocate or preallocate it. For filesystems which support the fallocate system call, preallocation is done quickly by allocating blocks and marking them as uninitialized, requiring no IO to the data blocks. This is much faster than creating a file by filling it with zeroes.

dd will “always” work. fallocate will work almostall of the time … but if you happen to be using a filesystem which doesn’t support it, you need to know how to use dd.

But: if your filesystem supports fallocate (and it probably does), it is orders of magnitude more efficient to use it for file creation.