Tuesday Jan 30, 2007

Innovating in High Performance Computing

There is an interesting parallel between building Ferraris and building computers. Both require elements to make them very fast and very complex. Like computers, Ferraris have a lot of commodity components such as tires. But the way these components are put together and the resulting end system is what makes them unique. The high performance computing space is no different.

Sun's Director of Technology in the Global Systems Practice, Marc Hamiltons's Blog, meets with Hal Stern, vice president of global systems engineering, in this edition of Innovating@Sun to discuss the art of tying together commodity components to get the most compute, networking, and storage in the smallest space.

Hamilton and Stern discuss what the high-performance computing (HPC) market looks like today with a focus on how technical problems today needs more capacity than you can deliver on a single desktop. Highlights of the interview include:

  • What mechanisms in Solaris make it possible to scale with increased clustering
  • Market interest around HPC given that applications are expanding and becoming more data and network driven
  • Mitigating silent data corruption with ZFS
  • Accounting for hardware failures in your software architecture to reduce the frequency of system failures
  • Multicore chips that are increasing demands on the operating system
  • The ever-present issues of power and cooling and what new innovations address these
  • Fortress – a modern language for HPC programming

    Links:



    Show Transcript
    Marc Hamiltons's Blog
    Open MPI
    X4500 storage server
    Andy Bechtolsheim
    Fortress
    Guy Steele

  • Tuesday Jan 16, 2007

    A Closer Look at Solaris 10 Security

    For as long as technology innovations have occurred, higher-end technologies have eventually made their way into the mainstream, allowing wider groups of users to access functionality formerly only available to a select few.

    Such is the case with security features in Solaris 10, now boasting capabilities formerly only available in Trusted Solaris versions of the operating system. VP of Systems Engineering Hal Stern welcomes Darren Moffat, Sr. Staff Engineer, and Glenn Brunette, distinguished engineer, to this edition of Innovating@Sun to discuss important security features of Solaris 10 that further enable enterprises to drive their business forward safely while allowing for a more open interchange with their customers and partners. Key discussion points include:

  • Least privilege boasting 100% backwards compatibility
  • Labelling to control flow of data
  • Role-based Access Control (RBAC)
  • Putting these technologies to use as larger volumes of content are posted back to your site
  • Managing the distinction between your firewall and the outside world
  • Sharing different classifications of data
  • Zoning and managing virtualized technologies

    The trio also discuss cool things imminently on the horizon such as:

  • Cryptographically signed binaries
  • Solving the issue of security of data at rest with encryption support added to ZFS file systems
  • Rules of engagement for minimization (now available)
  • Solaris security recommendations

    Links:



    Show Transcript
    Solaris 10 Security website
    Darren Moffat's Blog
    Glenn Brunette's Blog
    ZFS Crypto Project
    lofi Crypto
    OpenSolaris Security Community

  • Wednesday Jan 03, 2007

    A Different View at Security

    Security is about how all of the products and processes fit together into a comprehensive ecosystem that protects a company's information and information assets – essentially the system. And the architecture for systemic security is based on a set of modular components, or micro patterns, that address a variety of security problems.

    Hal Stern, VP of Systems Engineering welcomes Glenn Brunette, distinguished engineer, security expert, and fellow Jersey native to discuss the difference between systemic security and secure systems.

    Brunette discusses how early on, architectural patterns were discovered from customer deployments. This led to the ability to instantiate the patterns with a variety of products and services based on individual customer requirements while maintaining the integrity of the security architecture.

    Properties we might try to capture include:

  • Self Preservation - that every element within the environment should be able to protect itself from attack
  • Defense and depth
  • Mutual reinforcing layered security controls
  • Compartmentalization
  • Lease privileges to contain and limit exposure

    Check out the full podcast to understand why security is not about products – but about the products and the processes that fit together into a comprehensive ecosystem that protects information assets.

    Links:



    Show Transcript
    Systemic Security Website
    Glenn Brunette's Blog
    Alec Muffett's Blog
    Alec Muffett Security Video
    Contrarian Minds: Making Security Simple
    Inner Circle: Sun Systemic Security: Building Blocks for the Secure Enterprise