CSE 411 Project 6: Solaris Containers, the N1 Grid, and IBM’s z/VM

              Emily Celeskey, Michael Lin, Daniel Rapi...
executables that define specific actions that can be called upon by Plans. A Plan

organizes Components to organize the us...
Plans that dictate the use of Components, corporations can efficiently compartmentalize

and distribute computing tasks ac...
Containers hold all of the resources and applications available for use in a particular

Zone. These features make the N1 ...
References:

http://docs-pdf.sun.com/819-0408/819-0408.pdf

http://docs.sun.com/app/docs/doc/817-1592

http://techupdate.z...
Upcoming SlideShare
Loading in...5
×

CSE 411 Project 6-1.doc.doc

302

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
302
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

CSE 411 Project 6-1.doc.doc

  1. 1. CSE 411 Project 6: Solaris Containers, the N1 Grid, and IBM’s z/VM Emily Celeskey, Michael Lin, Daniel Rapiniski, Brent Schooley Solaris is touting its new N1 Grid Containers and Just-in-Time computing as a great new invention in computing, but in reality it is just a re-packaging of virtual machines and strategies used by IBM in its z/VM operating system. Furthermore it has less flexibility than z/VM because it does not allow operating systems to be layered: it only runs Solaris. However, the N1 Grid architecture’s technique of compartmentalization and distribution does bring new ideas to the forefront of server design and management. Also, Solaris Zones provide a secure environment for the running of system applications. The Solaris Zones isolate processes from the remainder of the system to prevent interference from other processes which are running in other zones. Solaris Containers take a subset of the applications and services in the Solaris 10 operating system and make them available to the user in a completely independent and transparent environment. It can do all this on a single server running Solaris 10, which is useful if you are using Solaris Zones, which allow the administrator to create multiple Solaris 10 environments. Similarly, the z/VM operating system allows the creation of layered operating systems; for example a server could run several Linux virtual servers on one Z Series server, and then run whatever was needed, wanted, and compatible on the Linux servers. The way Solaris containers work is fundamentally different from the idea of virtual machines. Basically, a Container is a type of Component, which is one of the fundamental objects in the N1 Grid architecture. Components are groupings of source or
  2. 2. executables that define specific actions that can be called upon by Plans. A Plan organizes Components to organize the use of resources. Containers are a special type of Component that can group many Components into one, or simply provide a partitioned, independent runtime environment for certain processes. Components also include information on procedures supported as well as install/uninstall information. This approach can be compared and contrasted with the way virtual machines simulate copies of the machine to each user. Thus, in Solaris, each application can believe it is running in its own environment with each user believing he/she is running his/her own environment. Solaris can support Windows applications to a limited extent, but z/VM can actually run Windows on the virtual Linux servers. Solaris Containers and Zones are limited to the Solaris 10 operating system, and as a result they are more efficient than full-fledged virtual machines. While virtual machines must account for every single aspect of the computer, and make sure that every hardware/software interface is accurately emulated, Containers can be more lax. Because Containers are relatively homogenous compared to virtual machines, they can afford higher performance with less overhead and thus lead to better resource utilization. Since Zones allow many fully independent runtime environments to coexist on a server, the effect of a z/VM system is fairly accurately replicated. Furthermore, because of the common Solaris 10 system, security is easier to manage. Updating and patching the different Zones is similarly made more manageable because of the common system at the core of Solaris Containers. An interesting aspect of Solaris Containers that is not seen in other similar systems is the N1 Grid architecture. By using Components, such as Containers, and
  3. 3. Plans that dictate the use of Components, corporations can efficiently compartmentalize and distribute computing tasks across the entire N1 Grid. In doing so, they can increase resource utilization across the entire company network, even at servers that are at remote sites. The Solaris Zones structure encompasses many of the ideas of a virtual machines. Solaris Zones isolate one set of processes into separate boxes, where each box contains a subset of the Solaris Operating System software packages, software packages from the global zone, and additional software packages and directories created in the non-global zone. As in virtual machines, Solaris Non-Global Zones are unaware of other existing zones; this prevents each zone from possibly trying to alter another zone. If security is compromised by a process running in a zone, the intruder is confined to the actions which are available to processes in that zone and cannot exploit the whole system. Zones cannot view the network traffic of other zones; this keeps other users from being affected by an exploit in one user’s zone. In this way the Solaris Zones concept is very similar to that of a virtual machine as each set of processes gets its own place to operate. Another factor which differentiates the Solaris Container structure from other operating systems is the idea that the operations can be set by using non-system data. Operating systems gather data from the system in order to provide a more efficient way to accomplish its tasks. The Solaris 10 operating system’s Containers collect data based on the workload usage in order to provide the maximum utilization of system resources for the user’s needs. The Solaris 10 operating system’s Container structure along with the Zones structure creates an environment very similar to a virtual machine environment. The
  4. 4. Containers hold all of the resources and applications available for use in a particular Zone. These features make the N1 Grid System comparable to a virtual machine system. However, there are some significant differences. A virtual machine system does not require the use of a particular operating system whereas the Solaris Containers will only run when the operating system being used is Solaris 10. As a result, the Solaris Containers system does not provide much of the flexibility that comes with most virtual machine packages. The Solaris Containers system is good for those individuals or businesses which currently run a Solaris environment on their systems, but it would likely cause problems for those wanting switch to this system who are currently running multiple operating environments and use applications created for each of the individual operating systems because Solaris Containers do not allow multiple types of operating environments. Also, Solaris Containers are not backwards compatible for those who would like to continue using the Solaris 9 operating system but want the security provided by the Solaris Container and Zones constructs. Solaris Containers offer a slightly different approach than virtual machines to the problem of virtualization. Unlike virtual machines, Containers are tied to the Solaris family of products, although support is provided for some individual applications outside of it. Also, Containers have less work to do than virtual machines because they do not have to simulate every part of the base computer, only those necessary to run the Container. Still, no matter whether a user picks Solaris Containers or virtual machines as a scheme, system resources will still be shared amongst applications and users and business will run as usual.
  5. 5. References: http://docs-pdf.sun.com/819-0408/819-0408.pdf http://docs.sun.com/app/docs/doc/817-1592 http://techupdate.zdnet.com/techupdate/stories/main/0,14179,2806411,00.html http://www.sun.com/2004-0330/feature/index.html http://wwws.sun.com/software/n1gridsystem/docs.html http://wwws.sun.com/software/n1gridsystem/faqs.html http://wwws.sun.com/software/n1gridsystem/wp-n1.pdf http://www.vm.ibm.com/overview/

×