Physicalization at work – software pricing at bay

This is an unashamed take from an Arstechnica.com article, and I certainly can’t take credit for the term. I’m just back from a week of touring around Silicon valley talking about our thinking for Dell 12G servers, to Dell customers and especially to those that take our products and integrate them into their own product offerings. It was a great learning experience, and if you took time to see me and the team, thank you!

One of the more interesting discussions both amongst the Dell team, and with the customers and integrators, was around the concept of physicalization. Instead of building bigger and faster servers, based around more and more cores and sockets, why not have a general purpose, low power, low complexity physical server that is boxed up, aggregated and multiplexed into a physicalization offering?

For example, as discussed in the arstechnica article, using a very simplified, atom based server, eliminate many of the older software and hardware additions that make motherboards more complex and more expensive to build, which in turn with the reduced power and heat, makes them even more reliable. Putting twelve, or more in a single 2U server makes a lot of sense.

They also, typically don’t need a lot of complex virtualization software to make full use of the servers. That might sound like heresy in these days when virtualization is assumed and the major driver behind much of the marketing spend, and much of the technology spend.

So what’s driving this? Well mostly, if you think about it, the amount of complexity needed in the x86 marketplace these days, and also in mainframe and Power/UNIX marketplace is through complex software and systems management. That complexity is driven by two needs.

  1. Server utilization – in order to utilize the increasing processor power, sockets and cores, you need to virtualize the server and split into consumable, useful chunks. This would normal require a complex discussion about multi-threaded programming and complexity, but I’ll ignore that this time. Net, net there are very few workloads and applications that can use the effective capacity offered by current top-end Intel and AMD x86 processors.
  2. Software Pricing – Since the hardware vendors, including Dell, sell these larger virtualized servers as great business opportunities to simplify IT and server deployment by consolidating disperate, and often distributed server workloads into a single, larger, more manageable server, the software vendors want in on the act. Otherwise they lose out on revenue as the customer deploys fewer and fewer servers. On eploy to combat this, to to charge by core or socket. Ultimately their software software does little and sometimes nothing to exploit these features, they just charge, well, because they can. In a virtualized server environment, the same is true. The software vendors don’t exploit the virtualization layer, heck in some cases they are even reluctant to support their software running in this environment and require customers to recreate any problems in a non-virtualized environment before looking at them.

And so it is that physicalization is starting to become attractive. I’ve discussed both the software pricing and virtualization topics many times in the past. In fact, I’ve expressed my frustration that software pricing still seems to drive our industry and, more importantly, our customers to do things that they otherwise wouldn’t. Does your company make radical changes to your IT infrastructure just to get around uncompetitive and often restrictive software pricing practices? Is physicalization interesting or just another dead-end IT trend?

IBM Big Box quandary

In another follow-up from EMC World, the last session I went to was “EMC System z, z/OS, z/Linux and z/VM”. I thought it might be useful to hear what people were doing in the mainframe space, although largely unrelated to my current job. It was almost 10-years to the day that I was at IBM, were writing the z/Linux strategy, hearing about early successes etc. and strangely, current EMC CTO Jeff Nick and I were engaged in vigourous debate about implementation details of z/Linux the night before we went and told SAP about IBM’s plans.

The EMC World session demonstrated, that as much as things change, the they stay the same. It also reminded me, how borked the IT industry is, that we mostly force customers to choose by pricing rather than function. 10-12 years ago z/Linux on the mainframe was all about giving customers new function, a new way to exploit the technology that they’d already invested in. It was of course also to further establish the mainframes role as a server consolidation platform through virtualization and high levels of utilization.(1)

What I heard were two conflicting and confusing stories, at least they should be for IBM. The first was a customer who was moving all his Oracle workloads from a large IBM Power Systems server to z/Linux on the mainframe. Why? Becuase the licensing on the IBM Power server was too expensive. Using z/Linux, and the Integrated Facility for Linux (IFL) allows organizations to do a cost avoidance exercise. Processor capacity on the IFL doesn’t count towards the total installed, general processor capacity and hence doesn’t bump up the overall software licensing costs for all the other users. It’s a complex discussion and that wasn’t the purpose of this post, so I’ll leave it at that.

This might be considered a win for IBM, but actually it was a loss. It’s also a loss for the customer. IBM lost because the processing was being moved from it’s growth platform, IBM Power Systems, to the legacy System z. It’s good for z since it consolidates it’s hold in that organization, or probably does. Once the customer has done the migration and conversion, it will be interesting to see how they feel the performance compares. IBM often refers to IFL and it’s close relatives the ziip and zaap as speciality engines. Giving the impression that they perform faster than the normal System z processors. It’s largely an urban myth though, since these “specialty” engines really only deliver the same performance, they are just measured, monitored and priced differently.

The customer lost becuase they’ve spent time and effort to move from one architecture to another, really only to avoid software and server pricing issues. While the System z folks will argue the benefits of their platform, and I’m not about to “dis” them, actually the IBM Power server can pretty mouch deliver a good enough implementation as to make the difference, largely irrelavant.

The second confliction I heard about was from EMC themselves. The second main topic of the session was a discussion about moving some of the EMC Symmetrix products off the mainframe, as customers have reported that they are using too much mainframe capacity to run. The guys from EMC were thinking of moving the function of the products to commodity x86 processors and then linking those via high speed networking into the mainframe. This would move the function out of band and save mainframe processor cycles, which in turn would avoid an upgrade, which in turn would avoid bumping the software costs up for all users.

I was surprised how quickly I interjected and started talking about WLM SRM Enclaves and moving the EMC apps to run on z/Linux etc. This surely makes much more sense.

I was left with though a definate impression that there are still hard times ahead for IBM in large non-X86 virtualized servers. Not that they are not great pieces of engineering, they are. But getting to grips with software pricing once and for all should really be their prime focus, not a secondary or tertiary one. We were working towards pay per use once before, time to revist me thinks.

(1) Sport the irony of this statement given the preceeding “Nano, Nano” post!

Nano, Nano – Serving you on 15-Watts

The Dell XS11-VX8 Server

The Dell XS11-VX8 Server

This is something I was asked about a few times at EMC World, power and form factors for servers. Here is the latest server from the Dell Data Center Solutions group (DCS). It’s only a little bigger than a disk drive, and you can get 252 servers in a 42U rack. While the form factor is interesting, very interesting, you need to think outside the “box” to get the true value.

It uses the Via Nano CPU, to deliver an incredibly low-power solution of 20-29 Watts/server when fully busy, and 15 Watts/server when the OS is idle. It includes enterprise features like 64-bit operating systems, 1-to-1 virtualization, and remote management via IPMI. What this does is turn the current server paradigm on it’s head. Instead of using more and more power hungry server chips that deliver more performance than you really need, which opens the gate for someone to tell you about server virtualization and consolidation to make the most of the power per watt, or cost of the server. The Dell XS11-VX8 just gives you “enough” performance, at a good price, and an effective price per watt. For those sensative to cross-charging, billing out IT services etc. it has another side effect of simplifying software licensing and allocation.

Over on the Direct2Dell blog community, Todd has written a post with some useful additional detail.

EMC World – standards?

Tucci and Maritz at EMC World 2009

Tucci and Maritz at EMC World 2009

I’ve been attending the annual EMC World conference in Orlando this week. A few early comments, there has been a massive 64,000ft shift to cloud computing in the messaging, but less so at ground level. There have been one or two technical sessions, but none on how to implement a cloud, or to put data in a cloud, or to manage data in a cloud. Maybe next year?

Yesterday in the keynote, Paul Maritz, President and CEO of VMware said that VMware is no longer in the business of individual hypervisors but in stitching together an entire infrastructure. In a single sentence laying out clearly where they are headed, if it wasn’t clear before. In his keynote this morning, Mark Lewis, President, Content Management and Archiving Division, was equally clear about the future of information virtualization, talking very specifically about federation and distributed data, with policy management. He compared that to a consolidated, centralized vision which he clearly said, hadn’t worked. I liked Lewis’s vision for EMC Documentum xCelerated Composition Platform (xCP) as a next generation information platform.

However, so far this week, and especially after this afternoons “Managing the Virtualized Data Center” BOF, where I had the first and last questions on standards, which didn’t get a decent discussion, there has been little real mention of standards or openness.

Generally, while vendors like to claim standards compliance and involvement, they don’t like them. Standards tend to slow down implementation historically. This hasn’t been the case with some of the newer technologies, but at least some level of openness is vital to allow fair competition. Competition almost always drives down end user costs.

Standards are of course not required if you can depend on a single vendor to implement everything you need, as you need it. However, as we’ve seen time and time again, that just doesn’t work, something gets left out, doesn’t get done, or gets a low priority from the implementing vendor, but it’s a high priority for you – stalemate.

I’ll give you an example: You are getting recoverable errors on a disk drive. Maybe it’s directly attached, maybe it’s part of a SAN or NAS. If you need to run multiple vendors server and/or storage/virtualization, who is going to standardize the error reporting, logging, alerting etc. ?

The vendors will give you one of a few canned answers. 1. It’s the hardware vendors job(ie. they pass the buck) 2. They’ll build agents that can monitor this for the most popular storage systems (ie. you are dependent on them, and they’ll do it for their own storage/disks first) 3. They’ll build a common interface through which they can consume the events(ie. you are dependent on the virtualization vendor AND the hardware vendor to cooperate) or 4. They are about managing across the infrastructure for servers, storage and network(ie. they are dodging the question).

There are literally hundreds of examples like this if you need anything except a dedicated, single vendor stack including hardware+virtualization. This seems to be where Cisco and Oracle are lining up. I don’t think this is a fruitful direction and can’t really see this as advantageous to customers or vendors. Notwithstanding cloud, Google, Amazon et al. where you don’t deal with hardware at all, but have a whole separate set of issues, and standards and openness are equally important.

In an early morning session today, Tom Maguire, Senior Director of Technology Architecture, Office of the CTO on EMC’s Service-Oriented Infrastructure Strategy: Providing Services, Policies, and Archictecture models. Tom talked about lose coupling, and defining stateful and REST interfaces that would allow EMC to build products that “snap” together and don’t require a services engagement to integrate them. He talked also talked about moving away from “everyone discovering what they need” to a common, federated fabric.

This is almost as powerful message as that of Lewis or Maritz, but will get little or no coverage. If EMC can deliver/execute on this, and do it in a de jure or de facto published standard way, this will indeed give them a powerful platform that companies like Dell can partner in, and bring innovation and competitive advantge for our customers.

Community involvement or free labor?

I’ve been following Andrew McAfee’s blog for a couple of weeks now, as a result of someone twittering a link to one of his blog entries. In his latest blog post, “Three Mantras“, McAfee discusses something many of the tech industry will recognize, self support systems. McAfee nicely summarizes the business opportunity to build around online communities as support subsystems.

I posted some of my thoughts on the topic in comments, namely the question of recognition and reward, not for participating, but for those that stay on and continue to participate. Initial participation is often self rewarding, we go look for help, experience or education in order to achieve some work related task. Need to get some help using a particular programming language or API – as Apple could have said “there’s a community forum for that!”

What makes McAfees blog interesting is his recognition of this phenomena, and his translation of it in to business terms and impact. For Dell, the guys that are part of the TechCenter have been doing a great job recently of creating knowledge and sharing it. They’ve recently run a number of demo and tech sessions on some of our key management technologies. You can find the Dell TechCenter here. It provides links into a wiki, Discussion Forums(just like the ones discussed by McAfee, the techcenter forum currently has some 34,000 topics) and the increasingly popular TechTuesday chats.

As I said in a comment to McAfee’s blog, this isn’t a new phenomena, as long ago as the late 1970’s I was first introduced to VMSHARE. A User run online bulletinboard/time sharing system aka forum to support and help users of IBM’s VM/370 operating system. While today there are many, many more forums, technologies and places to go for help, you can gain as much value from them today as I did then, because, and thats especially true for the Dell Techcenter, the people who participate are knowledgeable, dedicated and passionate about what they do, otherwise they wouldn’t do it.

Dell Management Console and 11G Server Launch

I spent Friday afternoon in a wet Round Rock parking lot where we held the launch thank you party for the team that put together the 11th Generation of Dell servers and the associated management software. We don’t complain about rain in Austin, it feeds some of the best things about town, namely Barton Springs, Lake Travis, which feeds Town Lake where I run, and the lake at Pure Austin North where I swim, in perfect conditions, twice per week. The celebration was sponsored by our partner Broadcom.

The event was hosted by our executives, including Michael Dell, and they made some important observations on the process to design the servers, market acceptance and customer feedback. While I was waiting in the food line, one the other folks and I got talking, he said “I looked at your blog the other day and you didn’t write anything on the Dell Management Console”. And he’s right.

It’s a significant step forward for Dell customers and for Dell. The DMC is based on the modular Symantec Management Platform architecture and offers a comprehensive set of features at no additional cost. While I was in IBM Power Systems, one of the fights I had with them was over their console and management strategy. While I’m sure they had good reasons the way they did, what they did, their ongoing strategy couldn’t follow the same path of fragmented consoles for this, consoles for that, different interfaces, different terminology for the same things etc. I’m hopeful still that when they introduce their next generation of servers, they’ll have learned the lessons that Dell already has.

DMC replaces the existing Dell hardware management console, Dell OpenManage IT Assistant. DMC has a plug-in architecture that allows the console to be extended with additional function and to be used as a manager for other scenarios, devices etc. However, true to the Dell mission to simply IT, Reduce TCO and one way we are doing that is to included a significant amount of function in the base, rather than as chargeable plugins. Here’s a summary of the major functions and improvements over prior offerings:

  • Hardware - multiple choices on how to explore, report and understand hardware configs plus export as tables; many pre-configured reports asd well as the ability to create your own.

    Proactive heartbeat monitoring is also supported, based on a user defined schedule; event suscription is also supported for Dell servers and MIBs can be imported for non-Dell hardware.

    You can push config changes and agent, BIOS, driver and firmware patches to many servers simultaneously without scripting.

  • Security – you can group devices and servers by geographical, logical, organisztional or type, or create your own. These can then be managed using role based secuity. You can create your own roles, or import them from Microsoft Active Directory.
  • Software – Support for hypervisors such as VMware(r) ESXi as well as Microsoft and Citrix. Health monitoring, discovery of virtual machines, associate to physical host server etc. Also included is the normal OS monitoring of utilization for memory, processors, free space and I/O.
  • Networking – The console includes support for a broad range of devices, but also includes support for Fibre Channel switches.

Thats an outline of the support in the new Dell Management Console, powered by Altiris from Symantec. I went to look for a couple of white papers to include links for. One with a more detailed list of device support and a second with a more comprehensive strategy that showed the plug-in architecture and the other function available for DMC. I came across this great resource, the Dell POWER Solutions magazine(just a hint of irony).

Here is a link where you can download the entire magazine, as a 21Mb PDF file. Alternatively, here is a link for an index into the articles where you can review each article seperately.

Oracle gets big on Sun

Predicting the Future, The Oracle concept watches by Designer Andy Kurovets mixes time with Chinese philosophy

Predicting the Future, The Oracle concept watches by Designer Andy Kurovets mixes time with Chinese philosophy

Fascinating news. I didn’t see a single consultant, analyst, journalist predict this. WRT to the supposed IBM/SUN on/off deal, I guess the biggest part to work out is how this will effect Oracle products on IBM Power Systems servers.

Oracle was definately the most significant software product on Power systems, I assume if Oracle decides it wants to keep the SPARC hardware architecture alive, it’s going to have to start favouring SPARC over Power. If nothing else, one assumes the fees IBM pays Oracle for Power support/currency/testing etc. will likely go up. Fascinating indeed.

I guess that also puts Oracle into competition with Dell and HP too, not just becuase of their SUN x86 hardware, but also again for platform currency. I didn’t dial-in to the investor call this morning, but I wonder how many are already wondering what the chances are of Oracle spending a year to work out how to sell-off the parts of Sun it doesn’t want, like the hardware business, but keeping the bits it does want, like Java and the other key software assets and intellectual property. Fascinating indeed.

However, if this knoxnews.com picture is anything to go by, Oracle have some work to do on their Industrial design and human factors for their hardware.

Profiles in, err, courage

Back in March I caught an early morning bus on Saturday to downtown Austin to attend Bar Camp IV, suffice to say it’s mostly not a bar, and doesn’t involve camping(anymore).

I attend a few interesting sessions, I learned a few things about Windows 7, mobile development and attended a session on airships and blimps that I assumed was some kind of coded language for a session on clouds, but it wasn’t it WAS about airships and blimps and more.

Big-up to @whurley @sarad and @linearb for organising and to the various sponsors which included not only free attendance, but also free lunch and libations.

I was on my way out when I bumped into Texas Social Media Awards finalist and local tech analyst and sometime contact, Michael Cote from Redmonk. We passed the time of day, and he asked me if I wanted to be interviewed for a podcast, why not?

I learned a ton about Cote from the interview, mostly that he doesn’t forget anything. We’ve met probably 5-6 times in the past and he seemed to pull 1x question from each discussion. I mostly laughed the whole way through, I thought it was going to be a tech discussion, and we did touch on a few topics, but it was just a fun way to spend 10-mins. You can hear the podcast and read the liner notes here on Redmonk Radio Episode 55. – And no, I have no idea why the series was called “profiles in courage”, why I was selected, a why I giggled all the way through. It’s been a while since I did my press training, I don’t remember them telling us about giggling as a technique!

Social networking/Web 2.0 amnesia

I’d never really thought about longevity of email addresses, I’ve no idea how long I’ve had my yahoo.co.uk address, probably not 10-years but I have no idea. [Update: Yahoo think's I've had my email since Oct. 1999]

When I was first at IBM UK they insisted on openness and transparency, and so we were encouraged to use our work Internet address by default. So – was name@vnet.ibm.com and then name@uk.ibm.com for most email from 1987. But then I got in a legal fight over an online triathlon forum I ran, and the companies lawyers wrote to IBM to complain as that was the only way they had to contact me. My boss at the time suggested it would be smart to separate my identities, I figure that was only about 2001. Since then I’ve fairly successfullly kept my online persona separate.

I don’t recall having an Internet email address before I joined IBM, but we’d had teletype and terminal systems where we could send messages between systems across the world, kinda like twitter but point to point mostly. My first memory of this was around 1978…

Transparency and declarative living have really been the default since then, the tools have got better overtime. I like the way things are coalescing around a few tools. Facebook is becoming a useful repository, being able to redirect via RSS your journal, tweets, pictures, friends, social contacts, travel plans via tripit etc.

Livejournal really hasn’t kept up and really serves little purpose these days except its original use, as a journal. Here it still stacks up better than many other blogging platforms as it still has private, friends, public entries.

However, I continue to be concerned that Facebook will eventually have a screw-up that will amount to mass amnesia, all sorts of content and contacts will be lost and irrecoverable. For that reason I still do 6-monthly backups of Livejournal to PDF’s via LJBook – that way my memories still have some collective memory, although I’m not sure what I’ll do with it. I’ve often thought about giving my lawyer passwords for key accounts etc. along with my will…

Have any others given this any thought ? Are there any Facebook backup or data extraction tools? What have you done about longterm password, or data storage? In 30-years time, possibly after you pass on, how will that picture get removed from Flicker ?

Whither IBM, Sun and Sparc?

So the twitterati and blog space is alight with discussion that IBM is to buy Sun for $6.25 billion. The only way we’ll know if there is any truth to it is if it goes ahead, these rumors are never denied.

Everyone is of course focussed on the big questions which mostly are around hardware synergies(server, chips, storage) and Java. Since I don’t work at IBM I have no idea whats going on or if there is any truth to this. There some more interesting technical discussions to be had than those generally think they have an informed opinion.

IBM bought Transitive in 2008; Transitive has some innovative emulation software, called QuickTransit. It allows binaries created and compiled on one platform, to be run on another hardware platform without change or recompilation. There were some deficiencies, and you can read more into this in my terse summary blog post at the time of the acquisition announcement. Prior to acquisition QuickTransit supported a number of platforms including SPARC and PowerMac and had been licensed by a number of companies, including IBM.

I assume IBM is in the midst of their classic “blue rinse” process and this explains the almost complete elimination of the Transitive web site(1), and it’s nothing more sinister than they are getting ready to re-launch under the IBM branding umbrella of POwerVM or some such.

Now, one could speculate that by acquiring SUN, IBM would achieve three things that would enhance their PowerVM stratgey and build on their Transitive acquisition. First, they could reduce the platforms supported by QuickTransit and over time, not renegotiate their licensing agreements with 3rd parties. This would give IBM “leverage” in offering binary emulation for the architectures previsouly supported, on say, only the Power and Mainframe processor ranges.

Also, by further enhancing QuickTransit, and driving it into the IBM microcode/firmware layer, thus making it more reliable, providing higher performance by reducing duplicate instruction handling, they could effectively eliminate future SPARC based hardware utilising the UNIX based Power hardware, PowerVM virtualization. This would also have the effect taking this level of emulation mainstream and negating much of the transient(pun intended) nature typically associated with this sort of technology.

Finally, by acquiring SUN, IBM would eliminate any IP barriers that might occur due to the nature of the implementation of the SPARC instruction set.

That’s not to say that there are not any problems to overcome. First, as it currently stands the emulation tends to map calls from one OS into another, rather than operating at a pure architecture level. Pushing some of the emulation down into the firmware/microcode layer wouldn’t help emulation of CALL SOLARIS API with X, Y, even if it would emulate the machine architecture instructions that execute to do this. So, is IBM really committed to becoming a first class SOLARIS provider? I don’t see any proof of this since the earlier announcement. Solaris on Power is pretty non-existentThe alternative is that IBM is to use Transitive technology to map these calls into AIX, which is much more likely.

In economic downturns, big, cash rich companies are kings. Looking back over the last 150 years there are plenty of examples of big buying competitors and emerging from the downturn even more powerful. Ultimately I believe that the proprietary chip business is dead, it’s just a question of how long it takes for it to die and if regulators feel that by allowing mergers and acquisitions in this space is good or bad for the economy and the economic recovery.

So, there’s a thought. As I said, I don’t work at IBM.

(1) It is mildly ammusing to see that one of the few pages left extoles the virtues of the Transitive technology by one Mendel Rosenblum, formerly Chief Scientist and co-founder of VMWare.

Moo cards II

Moo cards II - The Next GenerationWhen I first created “business” moo cards, it created quite a bit of a stir. So I figured I’d post the moo cards II the next generation design. Unfortunately I didn’t get organised early enough to get them for this weekends AustinBarCampIV, so I’ll be using the standard Dell ones if needed.

I actually found a useful feature of PowerPoint 2007. If you import the image(s). and the text on top, then select all the elements, you can export as a single file, rather than a ppt file or doing a screen copy and then saving with another program. Go ahead, make your own ;-)

Short DNS and brand ownership

I cycle home Wednesday evenings and back in on Thursday morning, it’s a 22-mile drag from Round Rock to Down Town Austin, with some quiet bits, some busy bits and some dangerous bits. While spinning up North Lamar heading south  towards 183, I was thinking about the rise of web URL shortnening websites such as tinyurl.com, which was the first I was aware of that offered a free service to take a long url such as this blog entry http://cathcam.wordpress.com/2009/03/05/short-dns-and-brand-ownership/ and turn it into http://snipurl.com/shorterdns

The main reason these became really popular was becuase some systems, such as Lotus Notes used to produce bizzare, very, very long URL’s for pages in Notes databases. It was easier to remember tinyurl.com/ae5ny than it would be to remember the page name, try it… Now, people these days know these services for twitter.com where every character counts, but thats not how or why they started.

There are a bunch of these services, tinyurl.com, snurl.com, is.gd, bit.ly etc. I tend to use snurl as it allows you to save specific names, I’m sure other shortners do too. What I was thinking about last night was the ownership, rights etc. to shortened URLs.

When my son wanted some cards from http://moo.com to help him promote his DJ work, I created them for him, but his myspace URL didn’t easily fit and flow, and what if later he wanted to create a website, he’d have to get new cards.

Answer, use snurl. So Oli and his alter ego Kaewan are now http://snurl.com/kaewan - It currently points to his myspace profile, but I can change it whenever I want. 

So these services have become, in some way, analgous to Domain Registrars. Sure a short URL isn’t a domain, but effectively it’s the same as one, except you don’t own it, and you didn’t have to pay for it. For fun I created http://snurl.com/redmonk - It actually points to Redmonks home page. But it could easily point elsewhere. And there’s the rub. With a traditional Name regsitrar there is an established right of review and appeal if you believe that someone has registered a domain that impinges on your brand and trademarks.

Not long after I created this blog, original DNS http://ibmcorner.com _ I got a “cease and desist” call from IBM legal pointing out that this wasn’t allowed and I should stop using it and not re-register the domain when it expired. SO where does http://snurl.com/ibm point to? Well not IBM and is was nothing to do with me.

Use cases for management/consoles

I think I’ve got a pretty good idea how people use consoles and do management for large centralised servers either UNIX or Mainframe based. What I’m quickly learning is that while I can speculate on how organisations would do management and use consoles for x86 servers, there doesn’t seem to be a concensus, or many clear use cases.

As you’ll see in the coming weeks, Dell have worked with partners to come up with some pretty compelling technologies in the management space, and especially in consoles. I can’t claim to have had anything to do with those. However, we are now on the road to make some pretty important decisions on where we go next, what technologies we use, especially in standards, and how we tie a number of the existing threads and product offerings together.

I worked on a similar decision while at IBM, it turned into a pretty vigorous and fractious debate, but unless things have changed since December, they’ll be implementing the broad outline as part of their Power 7 Server rollout.

Now, I could just get Dell lined up to do the same thing. Only I don’t think that would be right for Dell customers, and specifically around x86 rack and row management, and even probably down at the Small business level, although perversly, the proposal for IBM Power would have a lot on interest for SMB customers, but for a whole different set of reasons.

First thing this morning I got invited to listen to AG Lafley, the P&G CEO who is also a member of the Dell board of Directors. He made some interesting observations about being customer driven, it was a refreshing reminder.

So, rather than develop some “best effort” use cases for server management internally, I’d like your help. Would you be willing to send me a chart or diagram that shows how you manage your servers and how you use consoles? I’d like to know how many servers per consolve, connectivity between console and server(s), speed of connection, location of any firewalls etc. How many people need access to the console and so on. Mostly initially though I’m looking for some schematics that show the console, the servers, connectivity, placement of firewalls, secure zones etc.

Feel free to leave a comment here, I’ll email you directly or you can send any questions or diagrams to mark_cathcart at dell dot com .

(Belated) Leaving drinks in London

Since I’m coming over to the UK to get my new machine readable visa inserted in my passport, it’s a great opportunity for a “leaving drink”. So consider this an open invitation to all my former IBM UK Colleagues, either current or past, and any customers, analysts, journalists or consultants that I worked with.

I’ll be at the Archduke on Concert Hall Approach between IBM South Bank at Waterloo Station from 5.30pm onwards on February 23rd to buy drinks. I was going to say I’d be easy to find since I’ll be the one in cowboy boots and hat, but that would be an untrue stereotype for Austin, and decent cowboy boots are expensive, and I doubt I can find a hat big enough for my head ;-) – So I’ll pass on that idea.

If you can make it along it would be great to see you, even if you just have time to stop in and say “goodbye”. Feel free to add a comment if you can or can’t make it, in case I need to make any special arrangements with the Archduke.

Dell PowerEdge R905 Virtulization Server

In between meetings etc. I’m trying to find and keep up with some of the best Dell information sources.

Over on his Dell Community Blog, Matt M has put together a good blog entry with links and a video on the recent InfoWorld 2009 Technology award for the Dell PowerEdge R905 as the “Best Virtualization Server”.

I called this blog entry out as a follow-up to my prior posting about in-bound and out-bound management, and the challenges of using Intels AMT. The PowerEdge R905 was specifically designed around the AMD Virtaulization platform, which isn’t AMT compatible, but does have AMD-Virtualization or AMD-V which is exploited to the max in the R905.

Next Page »


About & Contact

I'm Mark Cathcart, Director of Systems Engineering and a Distinguished Engineer at Dell. I was formerly an IBM Distinguished Engineer and member of the IBM Academy of Technology. I'm an information technology optimist.

Subscribe to updates via rss:

Feed Icon

Blog Stats

  • 30,089 hits