|
|
AnnouncementsHPC Developer Edition Release | 06/11/2009Announcing HPC Developer Edition v1.0A complete development environment in a Virtual Machine …Have you been hearing all the buzz about HPC grid and cloud computing. You want to learn what its all about, but just didn't have the time and resources for the complex setup. I mean you need hardware, compilers, grid/cluster, parallel communications libraries. . . Sun developers have heard your wishes and made it easy for everyone wanting to learn how with HPC Developer Stack. Sun has put together a complete setup for development and testing of the software you want to create. Everything is combined in a single Virtual Machine Image. You can write the code in C, C++, Java, Fortran and many other scripting languages Bourne, bash, C-shell, tclsh, perl, python and more. The Virtual Machine Image uses Solaris Zones and SGE to give you a virtual grid computing system. Everything wrapped up in a single Virtual Image. So from a single laptop or desktop you have everything to get started. Virtual Images are available for both VMware or VirtualBox. Get it HERE. Sun has also included a full IDE development environment with Sun Studio. MPI (Message Passing Interface) library is included from Sun HPC ClusterTools for parallel process communication and synchronization. Everything you need to get started learning and using parallel programming and a completely integrated grid computing test environment in a few simple steps. HPC Developer Edition 1.0, with on demand Cloud Computing and other exciting stuff for HPC developer! Image download will be available on June 21st 2009 Here Or cut and paste this address to your browser: https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDSSMI-Site/enUS/-/USD/ViewProductDetail-Start?ProductRef=HPCSDE-1.0-G-F@CDS-CDS_SMI HPC Developer Wiki Page HPC Developer Virtual Machine Distro Support.For anyone needing help or support for the HPC Developer Distribution please send email to hpcdistro dash support at opensolaris dot org. If you wish to sign up and follow the support alias send email to hpcdistro dash support dash request at opensolaris dot org. Email Archives are kept at. Announcing Sun Grid Engine 6.2 | 08/05/2008The Sun Grid Engine 6.2 release is now available! See the following resources for more details:
Project Berlin 1.0 alpha | 06/25/2007The Project Berlin 1.0 alpha release is available here:
BACKGROUNDProject Berlin is an attempt to integrate Grid Engine with Solaris Zones in a tight fashion. Out of the box, Grid Engine supports the notion of Solaris Zones, in that Grid Engine allows an execution daemon to run in a Zone, potentially on the same physical machine as another execution daemon in another Zone. (The only restriction is that if an execution daemon is running in a non-global Zone, no execution should run in the global Zone. Otherwise, resource accounting can get confused.) While this basic level of integration is useful, more can certainly be done. In response to a feature request from the Sun Grid Compute Utility, one of the Grid Engine project engineers produced a tighter integration of Grid Engine with Solaris Zones. In this tighter integration, an execution daemon running in the global Zone would round-robin jobs into the known non-global zones. As a proof of concept, the integration worked. The downside, however, is that the integration involved source code changes in the Grid Engine shepherd binary. This project is an attempt to recreate the functionality of that tight integration without making changes to the Grid Engine binaries themselves. Not changing the Grid Engine binaries carries the distinct advantage that such an integration can be applied to pre-existing Grid Engine installations without requiring the administrator to upgrade the cluster. Not changing the binaries carries the distinct disadvantage of having to go around by Aunt Jane's house to make anything work. (That's Southern for "it complicates things.") ARCHITECTUREThe basic idea is that instead of having the execution daemon fork and exec a shepherd process, we replace the shepherd process with a proto-shepherd. The proto-shepherd attempts to determine in which Zone the job should run. If no Zone can be determined, the proto-shepherd simply execs the shepherd, and things work normally. If a Zone can be determined, the proto-shepherd forks and execs a zlogin into the Zone to run the shepherd. Because the shepherd is not the process that the execution daemon forked off, the execution daemon cannot find the shepherd to send it signals. To solve that issue, the proto-shepherd (which is sitting where the execution daemon expects the shepherd to be) listens for the 8 signals that the execution daemon uses to communicate with the shepherd and forwards any signals it receives to the shepherd running in the Zone. (The proto-shepherd finds the shepherd through the pid file that the later writes as soon as it starts running.) Solaris privileges present another issue. In order to run zlogin, the proto-shepherd has to be running with all privileges in its effective privilege set. Because the default inherited privilege set for root contains only the basic privileges, the shepherd is started by default with only the basic privileges in its effective privilege set. When we substitute in the proto-shepherd, it gets the same privileges, and is hence prevented from running zlogin. To solve the problem, we created a simple wrapper script around the execution daemon process that sets the inherited privilege set to all privileges. In this way, the proto-shepherd is run with all privileges in its effective privilege set. Announcing Grid Engine 6.1 Binaries | 05/03/2007Grid Engine 6.1 courtesy binaries are now ready for download. The courtesy binaries are available at http://gridengine.sunsource.net/project/gridengine/61downloads/download.html Read the full announcement here. |
