OpenSolaris zones - Revision history

NeilArmstrong: Added a Glossary link to Configuration~

2012-12-04T06:03:18Z

Added a Glossary link to Configuration~

← Older revision		Revision as of 06:03, 4 December 2012
Line 53:		Line 53:
	==Assumptions==		==Assumptions==

	Setting and ~~configurations~~ based on how I did this: (Adjust to your specific situation)		Setting and [[configuration~\|Configuration]]s based on how I did this: (Adjust to your specific situation)
	# You have either root level access, or you have been assigned [http://hub.opensolaris.org/bin/view/Community+Group+security/rbac RBAC] privileges for zones on an OpenSolaris machine.		# You have either root level access, or you have been assigned [http://hub.opensolaris.org/bin/view/Community+Group+security/rbac RBAC] privileges for zones on an OpenSolaris machine.
	# You know how to add users and set permissions on a directory.		# You know how to add users and set permissions on a directory.
Line 119:		Line 119:
	hosts: files dns nis		hosts: files dns nis

	user@computer# vi /zones/zone1/root/etc/resolv.conf (Edit the file according to your network configuration.		user@computer# vi /zones/zone1/root/etc/resolv.conf (Edit the file according to your network [[configuration~\|Configuration]].
	I used public nameservers for this demo.)		I used public nameservers for this demo.)
	domain opendns.org		domain opendns.org

NeilArmstrong: Added Glossary Link to Prompt~

2012-03-05T21:31:34Z

Added Glossary Link to Prompt~

← Older revision		Revision as of 21:31, 5 March 2012
Line 8:		Line 8:

	Q. Why should you consider OpenSolaris?<br />		Q. Why should you consider OpenSolaris?<br />
	A. I think a better question might be, why '''''shouldn't''''' you try OpenSolaris. If you're reading ~~this~~ then you must be at least slightly interested, so here are a few reasons why you should try it.		A. I think a better question might be, why '''''shouldn't''''' you try OpenSolaris. If you're reading thiAs then you must be at least slightly interested, so here are a few reasons why you should try it.

	* [http://hub.opensolaris.org/bin/view/Main/ OpenSolaris] was designed from the beginning for enterprise computing.		* [http://hub.opensolaris.org/bin/view/Main/ OpenSolaris] was designed from the beginning for enterprise computing.
Line 145:		Line 145:
	sh-3.2#		sh-3.2#
	</pre>		</pre>
	At this point, you have a login that resembles a Linux run level 1 command prompt. The reason for logging in this way is to reset the root password to something of a known value.		At this point, you have a login that resembles a Linux run level 1 command [[prompt~\|Prompt]]. The reason for logging in this way is to reset the root password to something of a known value.
	<pre>		<pre>
	sh-3.2# passwd root		sh-3.2# passwd root

NeilArmstrong: Added glossary link to Application~

2012-02-23T00:17:19Z

Added glossary link to Application~

← Older revision		Revision as of 00:17, 23 February 2012
Line 14:		Line 14:
	* [http://hub.opensolaris.org/bin/view/Community+Group+dtrace/dtracetoolkit Dtrace] Wanna know what your program is doing? Dtrace allows developers and system admins, ways to look at running programs in ways that weren't possible before.		* [http://hub.opensolaris.org/bin/view/Community+Group+dtrace/dtracetoolkit Dtrace] Wanna know what your program is doing? Dtrace allows developers and system admins, ways to look at running programs in ways that weren't possible before.
	* [http://hub.opensolaris.org/bin/view/Community+Group+xen/WebHome xVM] The OpenSolaris version of the popular Xen hypervisor.		* [http://hub.opensolaris.org/bin/view/Community+Group+xen/WebHome xVM] The OpenSolaris version of the popular Xen hypervisor.
	* [http://hub.opensolaris.org/bin/view/Community+Group+zones/WebHome Zones/Containers]. OS level virtualization, zones allow for completely isolated instances for running software. This is similar to the xVM hypervisor in that it allows absolute containment of ~~applications~~ and utilities, the biggest difference being, xVM requires a separate kernel, and running operating system. Zones utilize a single operating system instance, and don't incur the overhead associated with a hypervisor based model. However, xVM and Zones are ''NOT'' mutually exclusive, and work quite well in parallel. Zones are the main focus of this document.		* [http://hub.opensolaris.org/bin/view/Community+Group+zones/WebHome Zones/Containers]. OS level virtualization, zones allow for completely isolated instances for running software. This is similar to the xVM hypervisor in that it allows absolute containment of [[application~\|Application]]s and utilities, the biggest difference being, xVM requires a separate kernel, and running operating system. Zones utilize a single operating system instance, and don't incur the overhead associated with a hypervisor based model. However, xVM and Zones are ''NOT'' mutually exclusive, and work quite well in parallel. Zones are the main focus of this document.
	* [http://hub.opensolaris.org/bin/view/Project+crossbow/WebHome Crossbow]: The new virtualized networking stack built into the current release of OpenSolaris		* [http://hub.opensolaris.org/bin/view/Project+crossbow/WebHome Crossbow]: The new virtualized networking stack built into the current release of OpenSolaris
	* Support: You can get help from the [http://opensolaris.org/jive/index.jspa forums], [http://www.sun.com/service/opensolaris/ support contracts] from Sun, and as with most any other question, [http://www.google.com Google] is an invaluable resource.		* Support: You can get help from the [http://opensolaris.org/jive/index.jspa forums], [http://www.sun.com/service/opensolaris/ support contracts] from Sun, and as with most any other question, [http://www.google.com Google] is an invaluable resource.
	* [http://hub.opensolaris.org/bin/view/Community+Group+brandz/WebHome BrandZ]: An extension of the zone/container framework, designed to support Linux ~~applications~~ on the OpenSolaris platform. People have run apps ranging from Apache for Linux, to Unreal Tournament 2004 (playable with audio), to modern day game servers, to GT.M. There is a pretty high likelihood that if you can do it in Linux, you can do it in a zone/container.		* [http://hub.opensolaris.org/bin/view/Community+Group+brandz/WebHome BrandZ]: An extension of the zone/container framework, designed to support Linux [[application~\|Application]]s on the OpenSolaris platform. People have run apps ranging from Apache for Linux, to Unreal Tournament 2004 (playable with audio), to modern day game servers, to GT.M. There is a pretty high likelihood that if you can do it in Linux, you can do it in a zone/container.

	==What this document is==		==What this document is==
Line 32:		Line 32:
	* A virtualized operating system environment		* A virtualized operating system environment
	* Each zone has its own characteristics e.g. zonename, IP addresses, hostname, naming services, root and non-root users		* Each zone has its own characteristics e.g. zonename, IP addresses, hostname, naming services, root and non-root users
	* Isolated application environments within a single OS instance		* Isolated [[application~\|Application]] environments within a single OS instance

	==Document Conventions==		==Document Conventions==

Butch: /* Download the template file */ Updated link to template file

2010-03-15T20:17:20Z

Download the template file: Updated link to template file

← Older revision		Revision as of 20:17, 15 March 2010
Line 71:		Line 71:
	<pre>		<pre>
	user@computer# cd /etc/zones		user@computer# cd /etc/zones
	user@computer# wget http://~~www~~.opensolaris.org/os/~~community~~/zones/files/SUNWlx26.xml		user@computer# wget http://hub.opensolaris.org/bin/download/Community+Group+zones/files/SUNWlx26.xml
	user@computer# chown root:bin SUNWlx26.xml		user@computer# chown root:bin SUNWlx26.xml
	user@computer# chmod 444 SUNWlx26.xml		user@computer# chmod 444 SUNWlx26.xml

Butch: /* Download the template file */

2010-02-02T21:55:33Z

Download the template file

← Older revision		Revision as of 21:55, 2 February 2010
Line 71:		Line 71:
	<pre>		<pre>
	user@computer# cd /etc/zones		user@computer# cd /etc/zones
	user@computer# wget http://www.opensolaris.org/os/community/~~brandz~~/files/SUNWlx26.xml		user@computer# wget http://www.opensolaris.org/os/community/zones/files/SUNWlx26.xml
	user@computer# chown root:bin SUNWlx26.xml		user@computer# chown root:bin SUNWlx26.xml
	user@computer# chmod 444 SUNWlx26.xml		user@computer# chmod 444 SUNWlx26.xml

Butch at 14:33, 2 February 2010

2010-02-02T14:33:23Z

← Older revision		Revision as of 14:33, 2 February 2010
Line 186:		Line 186:

	--<br />		--<br />
	[[User:Butch \| Butch ~~Whitby~~]]		[[User:Butch \| Butch]]

Ssw0213: minor readability edits

2009-11-27T22:34:30Z

minor readability edits

Butch: /* The Medsphere installation method */

2009-11-18T18:07:51Z

The Medsphere installation method

← Older revision		Revision as of 18:07, 18 November 2009
Line 185:		Line 185:
	My thanks to Medsphere's OpenVistA team for producing this software, and for working with me in testing it on OpenSolaris.		My thanks to Medsphere's OpenVistA team for producing this software, and for working with me in testing it on OpenSolaris.

	--		--<br />
	[[User:Butch \| Butch Whitby]]		[[User:Butch \| Butch Whitby]]

Butch: /* Finishing up */ Context edit

2009-11-18T18:07:13Z

Finishing up: Context edit

← Older revision		Revision as of 18:07, 18 November 2009
Line 160:		Line 160:
	user@computer# zlogin zone1		user@computer# zlogin zone1
	</pre>		</pre>
	It is necessary to do so as logging in with zlogin -S gives you the equivalent of a single user Linux environment, and many of the tools and such wont work.		The logout/in process is necessary to do as logging in with zlogin -S gives you the equivalent of a single user Linux environment, and many of the tools and such wont work.

	Now that the zone is running, and the root password is set, it's time to run some basic commands. Start by making sure that all the existing packages are up to date.		Now that the zone is running, and the root password is set, it's time to run some basic commands. Start by making sure that all the existing packages are up to date.

Butch: /* Finishing up */ Edited for informational accuracy

2009-11-18T18:06:03Z

Finishing up: Edited for informational accuracy

← Older revision		Revision as of 18:06, 18 November 2009
Line 156:		Line 156:
	</pre>		</pre>
	===Finishing up===		===Finishing up===
	~~You can at~~ this point logout and ~~ssh~~ back into the machine, ~~although it's not really necessary to do what needs doing. Now that~~ the ~~zone is running, and the root password is set, it's time to run some basic commands~~. ~~Start by making sure that all the existing packages are up to date.~~		At this point you need logout and back into the virtual machine, either by SSH or by zlogin without the -S flag.
	<pre>		<pre>
	sh-3.2# yum update		user@computer# zlogin zone1
			</pre>
			It is necessary to do so as logging in with zlogin -S gives you the equivalent of a single user Linux environment, and many of the tools and such wont work.

			Now that the zone is running, and the root password is set, it's time to run some basic commands. Start by making sure that all the existing packages are up to date.
			<pre>
			user@computer# yum update
	</pre>		</pre>
	This process may take a considerable amount of time, but it's well worth doing. Unless you have specific reasons to not do so, (you already know that an updated package is going to interfere with whatever else your doing, etc.) update the system. Current testing shows no negative impact on [http://en.wikipedia.org/wiki/RPM_Package_Manager rpm] based VistA installations.		This process may take a considerable amount of time, but it's well worth doing. Unless you have specific reasons to not do so, (you already know that an updated package is going to interfere with whatever else your doing, etc.) update the system. Current testing shows no negative impact on [http://en.wikipedia.org/wiki/RPM_Package_Manager rpm] based VistA installations.

← Older revision		Revision as of 22:34, 27 November 2009
Line 2:		Line 2:

	Q. Why did I write this?<br />		Q. Why did I write this?<br />
	A. Several reasons, here are a few of them.		A. Several reasons; here are a few of them:
	* First and foremost, choice: OpenSolaris is a tool ~~to be used in whatever endeavor~~ you may want to tackle ~~with it~~. In the context of this article, using it as a platform for VistA.		* First and foremost, choice: OpenSolaris is a tool you may want to use to tackle whatever endeavor you are contemplating. In the context of this article, you might consider using it as a platform for VistA.
	* To inform: Relatively few people know ~~anything about~~ OpenSolaris and even fewer ~~even~~ know ~~that~~ it ~~exists~~. This is something ~~I think that~~ it shares with VistA. They are both extremely powerful software environments, and are so expansive that it would be nearly impossible for any one person to know everything. That very expansiveness fosters a community of users, from all parts of the world.		* To inform: Relatively few people know that OpenSolaris even exists, and even fewer know anything about using it. This is something it shares with VistA. They are both extremely powerful software environments, and are so expansive that it would be nearly impossible for any one person to know everything. That very expansiveness fosters a community of users, from all parts of the world.
	* To share: I have been using OpenSolaris for over a year now, and previously used Solaris 10 since 2007. I have gained a lot of experience with the OS, and think that I may be able to provide help and insight as to different ways to attack a given problem.		* To share: I have been using OpenSolaris for over a year now, and previously used Solaris 10 since 2007. I have gained a lot of experience with the OS, and think that I may be able to provide help and insight as to different ways to attack a given problem.

	Q. Why should you consider OpenSolaris?<br />		Q. Why should you consider OpenSolaris?<br />
	A. I think a better question might be, why '''''shouldn't''''' you try OpenSolaris. If ~~your~~ reading this ~~than~~ you must be at least slightly interested, so here are a few reasons why you should try it.		A. I think a better question might be, why '''''shouldn't''''' you try OpenSolaris. If you're reading this then you must be at least slightly interested, so here are a few reasons why you should try it.

	* [http://hub.opensolaris.org/bin/view/Main/ OpenSolaris] was designed from the beginning for enterprise computing.		* [http://hub.opensolaris.org/bin/view/Main/ OpenSolaris] was designed from the beginning for enterprise computing.
Line 15:		Line 15:
	* [http://hub.opensolaris.org/bin/view/Community+Group+xen/WebHome xVM] The OpenSolaris version of the popular Xen hypervisor.		* [http://hub.opensolaris.org/bin/view/Community+Group+xen/WebHome xVM] The OpenSolaris version of the popular Xen hypervisor.
	* [http://hub.opensolaris.org/bin/view/Community+Group+zones/WebHome Zones/Containers]. OS level virtualization, zones allow for completely isolated instances for running software. This is similar to the xVM hypervisor in that it allows absolute containment of applications and utilities, the biggest difference being, xVM requires a separate kernel, and running operating system. Zones utilize a single operating system instance, and don't incur the overhead associated with a hypervisor based model. However, xVM and Zones are ''NOT'' mutually exclusive, and work quite well in parallel. Zones are the main focus of this document.		* [http://hub.opensolaris.org/bin/view/Community+Group+zones/WebHome Zones/Containers]. OS level virtualization, zones allow for completely isolated instances for running software. This is similar to the xVM hypervisor in that it allows absolute containment of applications and utilities, the biggest difference being, xVM requires a separate kernel, and running operating system. Zones utilize a single operating system instance, and don't incur the overhead associated with a hypervisor based model. However, xVM and Zones are ''NOT'' mutually exclusive, and work quite well in parallel. Zones are the main focus of this document.
	* [http://hub.opensolaris.org/bin/view/Project+crossbow/WebHome Crossbow]: The new virtualized networking stack built into the current ~~released~~ of OpenSolaris		* [http://hub.opensolaris.org/bin/view/Project+crossbow/WebHome Crossbow]: The new virtualized networking stack built into the current release of OpenSolaris
	* Support: You can get help from the [http://opensolaris.org/jive/index.jspa forums], [http://www.sun.com/service/opensolaris/ support contracts] from Sun, and as with most any other question, [http://www.google.com Google] is an invaluable resource.		* Support: You can get help from the [http://opensolaris.org/jive/index.jspa forums], [http://www.sun.com/service/opensolaris/ support contracts] from Sun, and as with most any other question, [http://www.google.com Google] is an invaluable resource.
	* [http://hub.opensolaris.org/bin/view/Community+Group+brandz/WebHome BrandZ]: An extension of the zone/container framework~~. Designed~~ to support Linux applications on the OpenSolaris platform. People have run apps, ranging from Apache for Linux, to Unreal Tournament 2004 (playable with audio), to modern day game servers, to GT.M. There is a pretty high likelihood that if you can do it in Linux, you can do it in a zone/container.		* [http://hub.opensolaris.org/bin/view/Community+Group+brandz/WebHome BrandZ]: An extension of the zone/container framework, designed to support Linux applications on the OpenSolaris platform. People have run apps ranging from Apache for Linux, to Unreal Tournament 2004 (playable with audio), to modern day game servers, to GT.M. There is a pretty high likelihood that if you can do it in Linux, you can do it in a zone/container.

	==What this document is==		==What this document is==
Line 25:		Line 25:
	==What this document is not==		==What this document is not==

	This document is not meant ~~to be~~ the be-all-end-all of zone documentation. There is a great deal more to the technology than I'm even going to begin to cover in this write up. If you want to know more about lx26 zones, you can find lots of information [http://hub.opensolaris.org/bin/view/Community+Group+brandz/linux_2_6 here].		This document is not meant as the be-all-end-all of zone documentation. There is a great deal more to the technology than I'm even going to begin to cover in this write up. If you want to know more about lx26 zones, you can find lots of information [http://hub.opensolaris.org/bin/view/Community+Group+brandz/linux_2_6 here].

	These instructions are not meant for Amazon's EC2. The architecture of EC2 requires several additional steps, however the details of such are well beyond the scope or intent of this document.		These instructions are not meant for Amazon's EC2. The architecture of EC2 requires several additional steps, however the details of such are well beyond the scope or intent of this document.
Line 48:		Line 48:
	# You need to decide how your going to name your zones. Zones are a method of virtualization, and should be treated as if they were individual systems. (IP, hostnames, etc.) This is no different than if you were using Xen or vmWare.		# You need to decide how your going to name your zones. Zones are a method of virtualization, and should be treated as if they were individual systems. (IP, hostnames, etc.) This is no different than if you were using Xen or vmWare.
	# You need to decide if you want the zones to start up on boot of the main system, or if you want to boot them manually after system start up. In a testing environment this is purely a matter of preference.		# You need to decide if you want the zones to start up on boot of the main system, or if you want to boot them manually after system start up. In a testing environment this is purely a matter of preference.
	# You need to decide what method you are going to use to install VistA. (Astronaut, Nancy's instructions, Medsphere's installation method etc.) I will briefly cover ~~the~~ 3 at the end of this how-to.		# You need to decide what method you are going to use to install VistA. (Astronaut, Nancy's instructions, Medsphere's installation method etc.) I will briefly cover these 3 at the end of this how-to.
	# You need to be aware that the terms Zones and Containers are often used interchangeably, the difference being a container is a zone with resource management tools applied. [http://hub.opensolaris.org/bin/view/Project+rm/WebHome Resource management] is not covered in this document.		# You need to be aware that the terms Zones and Containers are often used interchangeably, the difference being that a container is a zone with resource management tools applied. [http://hub.opensolaris.org/bin/view/Project+rm/WebHome Resource management] is not covered in this document.

	==Assumptions==		==Assumptions==
Line 175:		Line 175:

	===Nancy's installation instructions===		===Nancy's installation instructions===
	This method, is probably the oldest written installation method available, and is likewise in turn, probably responsible for more installations than we will ever know. However, being that it is a completely manual process, it is prone to errors, if you don't follow the instructions explicitly. Cut and paste will be your friend with this method.		This method is probably the oldest written installation method available, and is likewise in turn, probably responsible for more installations than we will ever know. However, being that it is a completely manual process, it is prone to errors if you don't follow the instructions explicitly. Cut and paste will be your friend with this method.
	My thanks to Nancy for producing this document.		My thanks to Nancy for producing this document.
	===The Astronaut auto-installer===		===The Astronaut auto-installer===
	This method was the first fully automated method that I am aware of, and is developed and maintained by Ignacio Valdes. Using the functionality of dpkg and rpm (and their corresponding front ends) Ignacio has automated the entire installation process. What started as an all in one installer that was designed to get the product into the hands of as many people as possible, is quickly maturing, and is beginning to be broken out into it's component pieces. This will make it much more appealing to sys admins, who don't want to install extra software on their systems, and it should make maintaining an Astronaut based, VistA system easier. There is a version of the Astronaut installer for both WorldVistA and Medsphere's OpenVistA server products. This installer seems to work out of the box, within the OpenSolaris zone environment with no problems, that are not present in a standard installation on any other system.		This method was the first fully automated method that I am aware of, and is developed and maintained by Ignacio Valdes. Using the functionality of dpkg and rpm (and their corresponding front ends) Ignacio has automated the entire installation process. What started as an all in one installer that was designed to get the product into the hands of as many people as possible, is quickly maturing, and is beginning to be broken out into it's component pieces. This will make it much more appealing to sys admins, who don't want to install extra software on their systems, and it should make maintaining an Astronaut based, VistA system easier. There is a version of the Astronaut installer for both WorldVistA and Medsphere's OpenVistA server products. This installer seems to work out of the box, within the OpenSolaris zone environment with no problems, that are not present in a standard installation on any other system.
	My thanks to Ignacio for producing this installer, as well as allowing me to be involved as much as I have. Which has included ripping apart and analyzing almost every version of the installer that he has released so far, and offering input and insight from a sys ~~admins~~ point of view.		My thanks to Ignacio for producing this installer, as well as allowing me to be involved as much as I have. Which has included ripping apart and analyzing almost every version of the installer that he has released so far, and offering input and insight from a sys admin's point of view.
	===The Medsphere installation method===		===The Medsphere installation method===
	This method is similar to the Astronaut installation method, in that many of the tasks are automated. Installing Medsphere's OpenVistA packages is somewhat more involved than using Astronaut, but not nearly as involved as the manual method. Installing the OpenVistA server packages requires manually adding the EPEL software repo as well as the yum-priorities package. Current testing within a zone environment also shows some problems with Medsphere's packages.		This method is similar to the Astronaut installation method, in that many of the tasks are automated. Installing Medsphere's OpenVistA packages is somewhat more involved than using Astronaut, but not nearly as involved as the manual method. Installing the OpenVistA server packages requires manually adding the EPEL software repo as well as the yum-priorities package. Current testing within a zone environment also shows some problems with Medsphere's packages.