|
|
|
|
|
|
As I write this, today (4-Mar-2008) is primary day here in Texas, so it got
me thinking. Over the past 20 or so years, I’m sure that numerous
political party strategists have mused something along the lines of, “If only
we had a credible,
recognizable woman candidate that we could run for president...”
Likewise, many of those same party luminaries as well as some different ones
probably had the thought, “If only we had an African-American
politico with mainstream appeal that we could run for president...”
Well, be careful what you wish for, because right now we’ve got both. I’m
not saying anything about policies or their relative merits, but rather
commenting on the inevitable: as in all contests, someone is going to
win, and someone is going to lose. …and whoever is on the losing side is
probably going to set back the opportunity for another person with the same
characteristics in a future election by several years. In other words, no
matter who wins the nomination, the pundits will inevitably conclude that
America wasn’t ready for a [black or woman] candidate for president.
Obviously, we’ll see how it goes.
But wishes so often have some kind of downside—witness the numerous genie-in-a-bottle and
leprechaun jokes that abound (sorry, couldn’t think of one suitable to
publish here, so do
your own search). On a side note, I have always wondered why you
couldn’t wish for 3 more wishes as your third wish and keep the ball
rolling. But, back to the subject, just a few years ago there were
organizations of all sizes looking at their infrastructure and wishing for a
solution to what was called “server sprawl.”
This so-called sprawl was brought about because of the desire to have a stable
and sustainable environment, so the practice of hosting a single application
per server was deemed the best practice to avoid the dreaded “blue screen of
death” since applications couldn’t be trusted to interoperate together. A
side effect of this is that since Moore’s Law kept pushing processor
performance higher and higher, the 1-application-per-server rule meant that
average utilization would keep dropping with each successive generation of
server. Now all of a sudden what started out as a technology policy had
implications on the financial side, and that is that the return on IT assets
didn’t look very good.
Think of it this way: if you operated a dry cleaner and owned
several washers, dryers, pressing machines and whatever is used to do “dry”
cleaning (and just what is “Martinizing”
anyway?) and they were in use less than 30% of the time—equivalent to what
Gartner Group and others report average utilization of servers to be—how long
would it be before your accountant commented that you needed to either improve
your usage of those assets or look to downsizing?
Virtualization rode in on its white horse to save the
day. Now there was an effective method to stack multiple instances of an
operating system on a single server to improve utilization. Server
consolidation projects became all the rage in the wave of “virtualization 1.0.”
What’s interesting is how many customers I’ve chatted with
that have said that their server consolidation project was undertaken with no
more analysis than “We
have too many servers. Reduce them by half. (By next Tuesday…)” Along
the way, another phenomenon occurred. It became so easy to deploy a virtual
machine that now we had to confront a new horror: virtual server sprawl. You
see, even when virtualized, a server has to have an operating system and
applications and connections to the outside world. And those components have
to be configured, secured, administered and monitored. And it’s the same
amount of work whether it’s a physical host or a virtual one.
Virtualization isn’t a technology magic bullet. If you
move from physical to virtual and use the same processes, procedures and tools
that you always have, your administration costs are going to remain the same.
That’s why it’s so important that as part of a well-considered virtualization
strategy that you implement time-saving tools such as HP Systems Insight
Manager, in which an IDC
report documented that administrator-to-server ratios could be doubled
afterward (yes, I know I’ve
blogged about this before). There’s even a more
recent report that shows that the addition of the Insight Control Environment
(which includes specific management for virtualization from VMware and
Microsoft) can provide even more cost savings when implemented.
Okay, I’m off my soapbox for the week.
|
|
|
| » Read the full content |
|
|
|
| Posted by David Claypool on Wednesday, March 05, 2008 at 4:32:00 PM |
| Permalink
| Trackbacks (0)
|
|
|
|
|
|
One of the best parts of my job is that I get to travel the
world to meet with colleagues, partners and customers and talk about
infrastructure software. Last week I spent in Tokyo and got my first “taste”
of Japan. Unfortunately, snow nipped at the city's heels several times during the week and put a damper
on any sightseeing on my part, but I think I got a good introduction to real
Japanese culture, not just the Americanized version of it. Among other things,
I learned at dinner one night that “teppanyaki-style” dining referred to the hot
griddle in the middle of the table on which selections came out from the
kitchen onto to be kept warm or to finish cooking. Not once during the evening
did a faux kitchen samurai approach our table with a Benihana dinner show performance,
so I know it was authentic. I requested that they not tell me what a few things
were until after I’d eaten them, but it turned out that nothing more outrageous
than tripe
and squid
were served. I thoroughly acquitted myself with my chopstick
technique, and I didn’t have to ask for a fork even once.
The reason I was in Japan was to do training and meet with
customers on HP
Systems Insight Manager 5.2 and other future products. HP SIM 5.2
announced today (11-Feb-08) and is immediately
available, as is the updated Insight
Control Management DVD that contains the updated HP SIM install. Something
important to know before upgrading to HP SIM 5.2 is that there are internal
changes that affect the ability of plug-ins like Performance Management Pack,
Vulnerability and Patch Management Pack and others that require the plug-ins to
be updated for this new version of HP SIM. Therefore, it is better to use the Insight
Control Management DVD for your install rather than the straight HP
SIM-only install because it will automatically take care of updating the
plug-ins for you. If you don’t use this path, you could very well have a
happily updated HP SIM installation with plug-ins effectively disabled until
they are updated, and then you’ll need the Insight Control Management DVD
anyway to correct it.
Usually when we release a new version of a product there is
a long laundry list that goes along with it of all the new features. While
there are some new
features in HP SIM 5.2, the list is rather modest; rather, the focus of
this release was on improving its installation process, usability, and a number
of UI enhancements requested by users.
My favorite new feature is ‘Manage
Communications’ which provides a new level of detail and analysis for users
trying to debug connections between the HP SIM central management server and
the devices it is managing. Not only does it tell you what is going on, it
makes recommendations on how to fix it and also lets you jump right in to the ‘Configure
or Repair Agents’ function to make automatic corrections.
I encourage everyone to download and install the new version
as soon as they can so you can stay up to date with the latest software from
HP. This new version of HP SIM may even surprise the most cynical users by its
responsiveness and user-pleasing UI enhancements. P.S. I want to extend a big thank you to Makoto Akai, Junichi Kobiyama and Takao Ooe of HP Japan for the great way they organized my week and did their best to take care of me and make my visit special.
|
|
|
| » Read the full content |
|
|
|
| Posted by David Claypool on Monday, February 11, 2008 at 5:49:00 PM |
| Permalink
| Trackbacks (0)
|
|
|
|
|
|
| A few weeks ago, several of my colleagues and I were in the studio
shooting a number of short videos about HP Systems Insight Manager and the
Insight Control Environment. These will
appear in the not-too-distant future on hp.com so you’ll
be able to see the results.
I have long complained that the process of creating
presentations for products is extremely un-natural, and that in distilling
thoughts into a few bullets on a slide, we aren’t able
to convey all of the “cool” aspects of the product, why people should be
interested, and what the benefits to customers are. I’m not alone, and there are those that claim
that PowerPoint is
evil (not picking on Microsoft here—equivalent blame is due OpenOffice
Impress and like products; they just aren’t as ubiquitous)and
will be the death of the human race, or
at least human communications, or maybe just you. I’m sure everyone
has attended at least one “training” session or briefing in which a slow death by PowerPoint
was administered.
A skewering example
of this is the brilliant rendering of Abraham
Lincoln’s Gettysburg Address in
PowerPoint, a speech thought by many to be the most poetic, poignant and
perhaps most important political speech ever made by an American president. At the other end of the spectrum is former
art school student David Byrne,
notable for his participation in the 80s band Talking
Heads, who started out to lampoon PowerPoint because of its limitations,
but instead embraced it, finding an almost haiku-like freedom in its
restrictions.
Back to the videos, since the essence of a product is so often missed in the presentations, with the videos the
product managers would be able to talk about their products directly. Tell about all the cool features that they
know about and tell customers, but so often get missed
when sitting down to create a presentation.
So the videos had no scripts, no limiting
factors, just reality-TV HP-style. We were told not to prepare anything, just show up and
talk. Two cameras and
2 days of studio time.
The point I’m getting to is
this: after doing about 4 different
videos covering various products, one of the camera operators after the cut
asked me, “Aren’t you ever at a loss for words?” That’s it, isn’t
it? I can talk at length about the topic
and about the products, and I do, all around the
world. Some people get tired of me, I’m sure, with my persistent examples and
analogies. But finally,
I get to shut up. Because you don’t have to listen to me anymore; you don’t have to
subscribe to my belief that HP infrastructure software is cool, that it has
value, and that it saves customers money.
That’s because world-renowned
researcher International Data Corporation has
the data about how it saves.
In a just-published report, “Gaining
Business Val u e and ROI with HP Insight Control,” IDC writes about the
results customers who adopt Insight Control achieved:
A
savings of $48,380 per 100 users over 3 years
IDC identified that the savings fell across 4 categories:
- IT staff efficiencies
- IT infrastructure cost savings
- User productivity
- Time savings (allowing IT personnel to
focus on value-add initiatives)
The full details and the methodology are
in the report. Access it at the link
above.
|
|
|
| » Read the full content |
|
|
|
| Posted by David Claypool on Monday, February 04, 2008 at 3:42:00 AM |
| Permalink
| Trackbacks (0)
|
|
|
|
|
|
Kermit the Frog probably said it best when he sang, “It’s not easy being green,”
but then again, he was talking about a completely different subject. I am amazed at how quickly society and the
commercial sector have transformed ecological energy awareness from socially-awkward kookiness (embodied best by Ed Begley, Jr.,
in his HGTV show “Living with Ed”)
to the new cool. Sure, a lot of it is
credited to the “man
who invented the internet,” but face it, Al Gore, Jr. isn’t
much cooler than Ed. But
in an all-pile-on frenzy, the media have become laser focused on the topic and
public sentiment has followed suit. Even
the peace/love/save-the-world sixties didn’t have as
much impact on this topic.
But poking beneath the surface, it
seems that appearing green is more important to some than actually being
green. During
conversation at dinner last night, the owner of a Toyota Camry hybrid confessed
to not being in the “in” crowd because you had to look closely to see that it
was a hybrid—it looked just like the regular Camry and so didn’t shout “Green!”
to everyone who saw it, so he wasn’t supporting the cause the same way as if he
had a Prius (although if you really wanted to publicly display green-ness, the
homely Honda
Insight would be the way to go).
This “green image” has got to be a consolation
prize, because there is widespread disappointment
with hybrid gas mileage, even leading to several lawsuits. And now there’s a
big blow to all of those whose consciences have been soothed by buying a
hybrid, a recent report that a Prius
does more environmental damage than a Hummer. It seems like the most eco-friendly thing to
do is to really use less by changing habits and
driving less often.
There’s a lot of truth to this as
it applies to the computer industry as well.
Since a fair percentage of servers exhibit low
utilization on average, stacking applications on servers through the use of
virtualization has been a popular method of consolidation. HP even cooperated with Pacific Gas &
Electric in a rebate program
designed to cut energy use through virtualization. PG&E’s interest was in cutting
future demand growth so it could avoid having to build new power generating
capacity to meet the projected need.
HP has taken many steps to reduce energy consumption in
ProLiant servers. When we moved to the
Generation 5 series, we transitioned from hard drives with 3.5” platters to
2.5” that (if I did my math right) require about half the power at peak and
operating modes. We also have been
providing highly efficient power supplies for some time, and been designing
for power efficiency. Recently,
we’ve qualified low-power memory DIMM options for ProLiant servers which have
resulted in placing
3 of our servers in the top 5 of the new SPECpower_ssjTM 2008 benchmark results.
Server-class processors from Intel
and AMD
have also become available that consume less power and allow stepping down
power consumption to meet the demands of lower utilization. If you’re using an
operating system that recognizes that, some power savings can be realized. However, self-deterministic individual
policies aren’t really in keeping with data center
operational best practices, and administrators want to have a way of getting
insight into what actually is happening and the actual wattage consumed and the
BTUs produced.
Enter HP
Insight Power Manager. This plug-in
to HP Systems Insight Manager
interfaces with the Integrated Lights-Out processor on ProLiant servers and
blades (and the newest version supports Integrity servers, too) to monitor and
control power. It’s
available as part of the Insight Control Environment license, on its own, or as
a bundle with an iLO 2 license. Insight
Power Manager lets you collect data from systems on how much power they
actually are consuming as well as actual thermal output and retain it for up to
3 years. You also can input what your
local utility charges on a per-killowatt-hour basis so it can express costs to
power the system. Probably best of all
is that you can set the dynamic power saving mode across one or more systems,
and by using the iLO 2 management processor, it’s able to sample utilization up
to 5 times a second without having to install any software on the operating
system. Testing in the lab has found
that for servers with utilization up to 80%, there is no sacrifice in
performance in running in this low-power mode (see “Power
Regulator for ProLiant,” page 6). It
also can enforce an average power “cap” on a set of systems and soon it will be
able to cap the maximum power as well.
What does it all mean?
Even though power prices have gone up, it’s
still relatively cheap, isn’t it? Well,
analysis shows that the 3-year
cost of power and cooling can actually exceed the equipment cost. Whoa. But there’s more. Since
power consumption has actually been growing faster than Moore’s Law (see “Data
Center Cooling Strategies,” page 3), unless you’re
using some power conservation strategy, you’re probably paying for wasted
electricity.
It’s more than just paying your
electricity bill. Power consumption has
implications for the server room or data center with each new device added to
it. And data
center build-outs are millions of dollars of capital expense. It’s easy to see
that using one or more of the strategies above is an imperative for a business,
not just from an economic standpoint, but also an ecological one. In fact, HP’s own efforts at data
center consolidation and efficiency are designed to
reduce IT power and cooling consumption by more than 50 per cent—enough to
power a city the size of Palo Alto, California, where HP is headquartered.
Go green. Be
green. Live green. Learn more at HP’s Green
Power and Cooling Seminar.
|
|
|
| » Read the full content |
|
|
|
| Posted by David Claypool on Sunday, January 27, 2008 at 4:23:00 PM |
| Permalink
| Trackbacks (0)
|
|
|
|
|
|
I frequently have the chance to present in front of real customers who come in to find out the latest that HP is doing during visits to the Executive Briefing Center here in Houston and also in Cupertino. This morning was one of those times, but a little bit different, because the customer was a little smaller than those who usually visit (not that there's anything wrong with that). It was the CIO and one of the members of the server admin team, and the company runs around 40 ProLiant servers from the DL300 series, and a StorageWorks SAN.
As I asked questions to get a better picture of how they managed things in the environment, it became apparent that their current state was something they arrived at accidentally; it wasn't planned. Their practice was to load the ProLiant server management agents on the servers as they built them, but they didn't have any coordinated approach to how they used them. The server admin in the meeting today said he thought one of his colleagues had "Insight Manager" set up some where, but he wasn't sure what version it was, how often it was used, and only that person had access to it. In fact, the CIO had asked the server admin in the last week if he could report on how much memory was in their Citrix server, and he logged in to the ProLiant server management agents' System Management Homepage for each of them (luckily there were only 4) and was able to tell the CIO the information.
I thought that was a good example of an issue I've discussed with a lot of CIOs. In most IT organizations, there are certain fixed costs, like facilities. It takes some amount of power to keep the lights on and the cooling going, physical security, and so forth. Not a lot of variability in those costs. Likewise the hardware and software costs--sure you negotiate the best you can with your suppliers, but the biggest lever is always going to be volume, so unless you plan on doubling the number of servers you have in the next year, there isn't much to talk about.
What it gets down to is that for most IT organizations the cost that can be controlled the most is people cost. Getting back to the customer this morning, that almost made the CIO fall out of his chair laughing, saying I'd made his day. According to him, any control he had over his staff was at most an illusion. So I asked a few more questions and got mostly the answers I expected, because I've seen it time after time. His staff is made up of very skilled and experienced administrators. The kind of dream team that you can throw anything at and expect them to deal with it. But since you don't need the services of a "rocket scientist" every day, sometimes the tasks they do aren't always a match for their expertise.
I've said this many times to audiences around the world... (with some apologies for Jeff Foxworthy and his 'You might just be a redneck...' routine)
- If you see a Microsoft Certified System Engineer in your server room with a screwdriver in hand racking servers, you have a problem...
- If you see a Cisco Certified Network Administrator having to stand in front of a rack of equipment, you have a problem...
- If you see a Red Hat Certified Engineer with CDs in hand installing an application or operating system module, you have a problem...
I'm sure a lot of you just thought of an incident that happened recently in your own organization similar to that described above. I know every time I talk about this with groups of customers I always see heads nodding in agreement. In a way, we've all done this to ourselves. By not getting ahead of the curve and really planning out how incidents are dealt with and implemented solid procedures that are replicatable and repeatable, we end up in a situation where we need an extremely experienced crew because Murphy's Law always applies.
Think about it. If everyone who came into an ER, whether with a head laceration, broken bone or in full cardiac arrest all required immediate and continuous care from an experienced physician, it would be unmanageable (not to mention extremely costly). When you come to an ER you get triaged, and depending on the severity of your complaint, may end up being cared for by an intern, resident, physician's assistant, or nurse for part or all of your visit. How is this possible? Because of well-defined procedures and escalation processes.
From a process and procedure perspective, HP Systems Insight Manager can be a big help. If you utilize it properly, it can help to parcel out easy tasks like replacing a hot-plug hard drive to less experienced staff members. You also can use it to document how situations have been solved, thereby building organizational knowledge. While you may have enjoyed my story above and generally agreed with my logic and conclusions, we have the data to prove the benefits of using HP SIM from real customer reports. What they report is that by using HP SIM, most administrators can double the number of servers they supervise. Additionally, unplanned downtime can do down by as much as 77%, because of features like the pre-failure alerts on CPU, disk and memory, and the quality of information provided that can minimize downtime when it happens. This is documented in a report published by IDC called "Gaining Business Value and ROI with HP Systems Insight Manager." The methodology and quotes from the customers interviewed is available in the report.
But what do you think? Reports are well and good, but do you have an experience to share on this topic as well? Use the comments feature to talk back! |
|
|
| » Read the full content |
|
|
|
| Posted by David Claypool on Monday, January 14, 2008 at 7:34:00 PM |
| Permalink
| Trackbacks (0)
|
|
|
|
|
|
I always have said that industry standards are great--there's so many of them to choose from! This is especially true in the area of management, where there are numerous standards, some overlapping, creating an alphabet soup of protocols and transports whenever the topic of management comes up.
Industry standards are important to ensuring interoperability in today's heterogeneous environments. There are 2 basic types of industry standards, documented and de-facto. A 'documented' industry standard has some vendor-independent body responsible for the specifications and in some cases for certifying compliance. Most all real industry standards have some silent (or not so silent) standards organization backing it up.
This could make a good quiz. Match the standards to the standards body: RS-232? Its full name is EIA RS-232 because the spec was sponsored by the Electronics Industry Association. 802.11g wireless? Its full name is IEEE 802.11g since the Institute of Electrical and Electronics Engineers is the sponsoring body. Other bodies of note that have work impacting management are the Internet Engineering Task Force (IETF), sponsor of SNMP (simple networking management protocol) and lots of other things related to IP or internet protocols, and the Distributed Management Task Force, sponsor of WBEM (web-based enterprise management), CIM (common information model) and SMASH (systems management architecture for server hardware).
A de-facto standard is one which has not been codified by a standards group, but might be treated as such by the industry. For example, Microsoft publishes a Server Design Guide for manufacturers of x86 and IA64 servers to design systems compatible with Microsoft Windows server editions. You might also say that the x86 instruction set is a de-facto industry standard because both Intel and AMD provide processors compatible with it (although both are continually extending the the library of instructions to exploit specific capabilities in new processor hardware, meaning that some software has to know how to detect and run the specific processor extension for some operations).
There's one additional type of industry standard--and that's a standard by 'proclamation.' This is usually when a company prepares a press release, on its own or in conjunction with a partner or two, and declares what they've done an 'industry standard.' A prime example of this is IPMI, the Intelligent Platform Management Interface. Originally specified by a consortium led by Intel, at first Intel was the only manufacturer of IPMI chips. As time went on, not only Intel, but others such as Avocent, Qlogic and others began providing chips. Even though there was a sheen of standardization surrounding IPMI and there even were version numbers applied to certain sets of features, there could be wild variability as to what chip manufacturer actually implemented in a chip they labeled IPMI 2.0.
While commodity IPMI chips from various manufacturers have been featured in the HP ProLiant 100 series, HP's enterprise-class servers in the ProLiant, BladeSystem and Integrity lines have implemented some IPMI features in a controlled fashion. Specifically, the iLO2 management processor used in these products is a unique HP-designed component, not a commodity IPMI part.
Some readers might be tempted to read "unique" and "HP-designed" and make the immediate jump to the word that has become the kiss-of-death in the industry: proprietary. Personally, I prefer to think of these things as innovative, for the flip-side of industry standards is the fact that getting multiple parties in agreement can be time-consuming at best and at worst creatively stifling. Sometimes innovation and great leaps of technology are only possible in an environment of solo invention.
We are surrounded by an environment of innovation that sometimes is proprietary and exclusive, and in many industries this is a benefit, not a detriment. When Chrysler advertises their HEMI engine design--an exclusive Chrysler innovation, in fact, dating back several decades--we take this as engineering prowess and may choose to buy a Chrysler because of it, knowing that we still can buy gasoline from the corner and drive on the same highways as other cars. Sometimes this innovation is just a trade or marketing name, and doesn't represent any scientific or engineering development at all (just what was Certs with "Retsyn" anyway...check any number of household cleaning products claiming to be new and improved for other similar examples).
Perhaps closer to home is the incredibly successful iPod It utilizes a proprietary media format, AAC, licensed from Dolby Labs which hasn't been adopted by many (if any) other portable music players, so music you download to the iPod can't easily be used on any other device. And while the topic is undergoing much debate today, the iPod and iTunes implement a Digital Rights Management scheme that is specifically designed to prevent you from buying and downloading a song from iTunes and then sharing it with all of your friends for free.
Getting back to the topic of industry standards, not only does it assist in interoperability, but to some degree makes sure that you retain something of value when the company you purchase a device from goes out of business or discontinues development of an item. This can happen all the time. In fact, Intel has moved on from IPMI, and its newest offering is called iAMT or Intel Advanced Management Technology.
What does this mean? It means that sometimes you have to weigh the value of an innovation against the value of industry standards that are available. Sometimes you don't have to specify a technology at the lowest level. In this area, there actually is an industry standard available to help, and it helps in one way by abstracting the raw technology underneath. Sponsored by the Distributed Management Task Force, the SMASH command-line protocol (system management architecture for server hardware) has been implemented by several manufacturers of IPMI chips, Sun, IBM, and most notably HP's iLO and iLO2 management processors. Whereas someone trying to utilize things based on an "IPMI 2.0" environment might find variability between what features are available from one set of systems to another, those implementing SMASH CLP will enjoy a consistent environment from one generation to another and from one manufacturer to another.
Speaking as a marketing person, I feel rather qualified to issue the warning to read past the marketing hype present in press releases and web pages. Make intelligent choices about your implementations, choose industry standards wisely, and don't let innovation scare you away because it exclusively is available from one manufacturer. There may be enough industry standards involved to provide the interoperability and sustainability that you need.
|
|
|
| » Read the full content |
|
|
|
| Posted by David Claypool on Monday, January 07, 2008 at 4:23:00 PM |
| Permalink
| Trackbacks (0)
|
|
|
|
|
|
Well, it's the first business day of 2008, and here we inaugurate a new series of blogs, oriented to what we call "HP Infrastructure Software." That's a label we've arbitrarily applied to the fun stuff our little group does here at HP, and it's not particularly descriptive. During the recent holiday break, I struggled to describe the technology area I worked in to relatives and friends, and about the best I could do was, "It's for organizations with dozens, hundreds or even thousands of computer servers, where it's not appropriate to have someone walking down the aisles looking for red warning or fault lights..."
It's inadequate a description because the topics we'll be tackling will range far beyond the stuff of component failures and system outages. To the knowledgeable, I'd describe HP Infrastructure Software as the set of tools that help administrators deploy and provision physical and virtual servers, make sure they're available, up-to-date and optimally configured. That's about as comprehensive and succinct as it comes.
To bring this short inaugural posting to a close, I'd like to invite you, the reader, to participate. While I'm committed to featuring a lively diatribe on things I think are timely and important, I also want to make sure that it's pertinent, so please make use of the comments feature here to provide your feedback on what's written, but as importantly to suggest topics for future blogs postings.
Finally, I want to remind everyone that this is not the best place to discuss problems or get questions to answers about the HP products discussed. There is a public forum in the HP IT Resource Center that is dedicated to the topic at http://forums.itrc.hp.com/service/forums/familyhome.do?familyId=121 and you can see specific sub-topics that help organize the discussions.
|
|
|
| » Read the full content |
|
|
|
| Posted by David Claypool on Wednesday, January 02, 2008 at 2:56:00 PM |
| Permalink
| Trackbacks (0)
|
|
| Apr |
May 2008 |
Jun |
| S | M | T | W | T | F | S | | 27 | 28 | 29 | 30 | 1 | 2 | 3 | | 4 | 5 | 6 | 7 | 8 | 9 | 10 | | 11 | 12 | 13 | 14 | 15 | 16 | 17 | | 18 | 19 | 20 | 21 | 22 | 23 | 24 | | 25 | 26 | 27 | 28 | 29 | 30 | 31 | | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
|
|
| » |
|
|
Printable version
