Vendor group announces cloud storage initiative

The Storage Networking Industry Association (SNIA) announced today the formation of the Cloud Storage Initiative (CSI) in order to establish a lexicon of cloud-computing terminology, publish use cases, white papers and technical specifications, and to create reference implementation models for grid-storage architectures. – Published by Computerworl …

URL: http://www.computerworld.com/s/article/9139203/Vendor_group_forms_cloud_storage_initiative

Inside a ��Compliance and Interoperability�� Workshop

Do you read the comic strip ��Dilbert��? If so, you know what a work environment based on cubicles looks like. Many of us involved with the Server System Infrastructure (SSI) Forum just finished our first ��compliance and interoperability�� (C&I) workshop and, interestingly, cubicles played a key role.

Cubicles are a useful compromise between noise, openness, ease of access and other factors. However, one thing a cubicle is not, is private. Why is that relevant to a C&I event? Let me explain.

��Compliance�� refers to the conformance of a physical device, say a computer or plug-in card, to a written specification. ��Interoperability�� refers to the ability of the physical device to connect with other devices and perform according to predetermined tests.

A C&I workshop has elements of testing for specifications and for tests of devices connected together. Depending on the devices under test, testing can be extremely complex process, often involving entirely new-to-the-world components. In fact, multiple entirely new components can be connected together, based on untested specs and using the latest generation of test equipment.

Participating company��s most talented engineers work to get their components proven compliant and interoperable. That��s where secrecy comes in: engineers have to be able to work without being concerned about prying eyes.

Privacy is also essential for the tests themselves. Early results may not be positive, but those early results could be damaging to a company��s reputation, so they are correctly kept confidential.

How is this privacy achieved? The first C&I workshop was held at an Intel facility. At the lab there are cubicles, per the Intel norm. However, the larger than usual cubicles featured translucent fiberglass panels bolted to the cubicle walls. Also, a sliding lockable door was added to each cubicle.

During the three-day workshop, much was accomplished. Engineers from across the US, Israel and China, representing several blade components, were able to connect their devices together. There were two basic blade systems, one developed by Intel and one by a system OEM. They were developed independently and in parallel, but both were based on specifications provided by SSI.

SSI develops and promotes open specifications for blades and for chassis and power supplies for servers. It currently has almost 40 member companies around the world. SSI has produced 6 blade specs, currently in draft form, to be finalized by the time of the Intel Developer Forum (IDF), September 22-24. SSI has also made 3 switch specs from IBM BladeCenter available to SSI members.

There are two focus areas for specification in the ��traditional�� server area of SSI, one for electronics bays (chassis) and one for power supplies �V with over 40 specs released since the inception of SSI. Current specs are always available on the SSI web site, and specs now in development for the next CPU generation will be available for prerelease access.

<![CDATA[The C&I Workshop is an important first step on a long journey. Workshops will be held at independent test organizations, purpose-built for such activities. Workshops will expand in scope and participation, as we deliver on the promise of interoperability; really the central tenet of SSI.]]>

See you at IDF! Please come to my session, EMTS006, ��SSI Interoperability Delivered: How Server System Infrastructure (SSI) Specifications Provides Interoperable Components��, September 24, at 2:40. I suggest you attend my colleague, Steve Krig��s, lab ECTL001, ��Lab: SSI Server System Infrastructure �V Industry Open Blades Standards Compliance and Interoperability��, September 23, at 2:05 and 4:15, for a more technical description of C&I tools and methodologies. I also suggest you visit our booth to see our interoperability demo at booth number 520.

Jim Ryan, Chairman, SSI

Intel Intelligent Power Node Manager… where’s the on-off switch?

One of the recurring themes that I&aposve been noticing from end-users who are testing or evaluating Intel Intelligent Power Node Manager (or Node Manager) – the question is "How do we turn it on or off?"  To put it simply – when you have a Node Manager capable platform – you can simply put it to work and let your power policies decide when to enable/disable the features…

So let me step things back a bit and talk about the technology itself first.The platform is based on the Xeon 5500 Series Chipset (codename Tylersburg-EP) server boardXeon 5500 Series Processors (codename Nehalem EP)Node Manager Enabled Firmware with the Manageability Engine Server chassis components that meet IPMI 2.0 specifications for monitoring (e.g. thermal monitoring)PMBUS Power Supply – this communicates with the Baseboard Management Controller (BMC) for platform power usageFor those of you wanting to get your hands on this technology TODAY – check out the Intel Server linueup:Intel (codename Willowbrook) which is optimized for IPDC deployment, and supports IPMI 2.0, Intel Intelligent Power Node Manager, and can also support the Data Center Manageability Interface (DCMI) 1.0 specification.Intel (codename Urbanna) is the mainstream Enterprise platform which support IPMI 2.0 and Intel Intelligent Power Node ManagerBoth platforms work in conjunction with Intel (IntelOk – so that reads like a bunch of marketing stuff… but here&aposs the &aposguts&apos of the technology…When you purchase a Node Manager enabled server, there are a few simple steps to take to set things up to monitor/manage your server.Most likely you&aposll need to setup your BMC, Intel provides a CD based implementation to help with this in our servers – it&aposs called the Intel Deployment Assistant.The BMC needs an ip address, netmask, and default gateway setup – and according to IPMI specifications – you can also set the administrative (user) access rights if you would like to tighten down security a bit.Here&aposs a great demo video showcasing some of the Node Manager Intel DCM use cases:How many of you have done IPMI management before?

URL: http://feedproxy.google.com/~r/IntelBlogs/~3/7DjkzjrNHYU/intel-intelligent-power-node-manager-wheres-the-on-off-switch