Cluster: Sage Chroot - Revision history

Kay at 18:08, 11 September 2009

2009-09-11T18:08:14Z

← Older revision		Revision as of 18:08, 11 September 2009
Line 12:		Line 12:
	<pre>		<pre>
	/mounts/bobsced/sage_chroot.image /mounts/bobsced/sage_chroot ext3 loop 0 0		/mounts/bobsced/sage_chroot.image /mounts/bobsced/sage_chroot ext3 loop 0 0
	/dev /mounts/bobsced/sage_chroot/dev ~~devpts defaults~~ 0 0		/dev /mounts/bobsced/sage_chroot/dev none rbind,dev 0 0
	/proc /mounts/bobsced/sage_chroot/proc ~~proc~~ ~~defaults~~ 0 0		/proc /mounts/bobsced/sage_chroot/proc none bind 0 0
			/selinux /mounts/bobsced/sage_chroot/selinux none bind 0 0
	</pre>		</pre>

Line 47:		Line 48:
	COMMAND="notebook(address='$ADDRESS', port=$PORT, accounts=True, open_viewer=false, secure=true)"		COMMAND="notebook(address='$ADDRESS', port=$PORT, accounts=True, open_viewer=false, secure=true)"

	nohup /usr/sbin/chroot $SAGE_SERVER su - sage -c "sage -c \"$COMMAND\" " &		nohup /usr/sbin/chroot $SAGE_SERVER su - sage -c "./sage -c \"$COMMAND\" " print >>/var/log/sage &
	</pre>		</pre>

Line 56:		Line 57:
	. /etc/sysconfig/sage-config		. /etc/sysconfig/sage-config

	kill -9 `~~ps -u~~ $~~USER -o "~~pid="` > /~~dev/null 2>~~/~~dev~~/~~null~~		kill -INT `cat $SAGE_SERVER/home/sage/.sage/sage_notebook/twistd.pid` 2>&1 >>/var/log/sage
	</pre>		</pre>

	And finally, <code>/etc/rc.d/init.d/sage~~-notebook~~</code>:		And finally, <code>/etc/rc.d/init.d/sage</code>:
	<pre>		<pre>
	#!/bin/sh		#!/bin/sh
Line 76:		Line 77:
	echo -n $"Starting sage "		echo -n $"Starting sage "
	if [ ! -f /var/lock/subsys/sage ]; then		if [ ! -f /var/lock/subsys/sage ]; then
	nohup /usr/local/bin/sage-notebook 2/~~dev~~/~~null~~		nohup /usr/local/bin/sage-notebook print >>/var/log/sage &
	/~~dev/null~~ &
	fi		fi
	touch /var/lock/subsys/sage		touch /var/lock/subsys/sage

Kay: /* Chroot */

2009-09-10T16:15:35Z

Chroot

← Older revision		Revision as of 16:15, 10 September 2009
Line 18:		Line 18:
	In order to get yum to install there, I had to edit <code>/etc/yum.repos.d/CentOS-Base.repo</code> and hard code $releasever to 3.5. I also commented out all the repositories except the top one. Then I was able to run:		In order to get yum to install there, I had to edit <code>/etc/yum.repos.d/CentOS-Base.repo</code> and hard code $releasever to 3.5. I also commented out all the repositories except the top one. Then I was able to run:

	:<code>yum --installroot=/mounts/bobsced/sage_chroot install bash fileutils sed which make gcc gcc-c++ m4 tar gzip bzip2 flex bison findutils yum rpm passwd perl diffutils</code>		:<code>yum --installroot=/mounts/bobsced/sage_chroot install bash fileutils sed which make gcc gcc-c++ m4 tar gzip bzip2 flex bison findutils yum rpm passwd perl diffutils sudo</code>

	to set up the base install of the OS for the chroot. It also needs a copy of /etc/hosts for the localhost entry.		to set up the base install of the OS for the chroot. It also needs a copy of /etc/hosts for the localhost entry.

Kay: /* Sage Setup on the Base Filesystem */

2009-09-10T15:57:11Z

Sage Setup on the Base Filesystem

@@ Line 31: / Line 31: @@
 == Sage Setup on the Base Filesystem ==
-On the filesystem outside the chroot, I populated <code>/etc/sysconfig/sage-config</code>:
+I followed the post above for Red Hat.  On the filesystem outside the chroot, I populated <code>/etc/sysconfig/sage-config</code>:
 <pre>
@@ Line 38: / Line 38: @@
 PORT=8000
 USER=5000
 </pre>

Kay at 15:32, 10 September 2009

2009-09-10T15:32:39Z

← Older revision		Revision as of 15:32, 10 September 2009
Line 5:		Line 5:
	* [http://www.mail-archive.com/sage-support@googlegroups.com/msg01201.html [sage-support] Re: How to run the notebook in the background]		* [http://www.mail-archive.com/sage-support@googlegroups.com/msg01201.html [sage-support] Re: How to run the notebook in the background]
	* [http://groups.google.com/group/sage-support/msg/849e906146b41d28?pli=1 [sage-support] chroot jail -- unable to mount image file]		* [http://groups.google.com/group/sage-support/msg/849e906146b41d28?pli=1 [sage-support] chroot jail -- unable to mount image file]
	* [http://www.mail-archive.com/sage-devel@googlegroups.com/msg03545.html [sage-devel] Re: SAGE in chroot]		* [http://www.mail-archive.com/sage-devel@googlegroups.com/msg03545.html [sage-devel] Re: SAGE in chroot] - This one is for RedHat

	== Chroot ==		== Chroot ==

Kay: /* Sage Install */

2009-09-10T15:31:57Z

Sage Install

← Older revision		Revision as of 15:31, 10 September 2009
Line 23:		Line 23:

	== Sage Install ==		== Sage Install ==
	I downloaded the tar ball normally and then moved it into the chroot from the base filesystem. I untarred it from the base filesystem, too, and put it in the directory /home/sage in the chroot, then ran (as the sage user in the chroot)		I downloaded the tar ball normally and then moved it into the chroot from the base filesystem. I untarred it from the base filesystem, too, and put it in the directory /home/sage in the chroot, then ran (as the <code>sage</code> user in the chroot, which has id 5000, which isn't used in the main filesystem)

	:<code>make</code>		:<code>make</code>
	:<code>make test</code>		:<code>make test</code>

			Make sure to run <code>./sage</code> once inside the chroot so it sets up its variables and everything.

			== Sage Setup on the Base Filesystem ==
			On the filesystem outside the chroot, I populated <code>/etc/sysconfig/sage-config</code>:

			<pre>
			SAGE_SERVER=/mounts/bobsced/sage_image
			ADDRESS=159.28.234.200
			PORT=8000
			USER=5000
			</pre>

Kay: /* Sage Install */

2009-09-10T15:28:33Z

Sage Install

← Older revision		Revision as of 15:28, 10 September 2009
Line 27:		Line 27:
	:<code>make</code>		:<code>make</code>
	:<code>make test</code>		:<code>make test</code>
	~~:<code>make install</code>~~

Kay: /* Sage Install */

2009-09-10T15:28:07Z

Sage Install

← Older revision		Revision as of 15:28, 10 September 2009
Line 23:		Line 23:

	== Sage Install ==		== Sage Install ==
	I downloaded the tar ball normally and then moved it into the chroot from the base filesystem. I untarred it from the base filesystem, too, then ran		I downloaded the tar ball normally and then moved it into the chroot from the base filesystem. I untarred it from the base filesystem, too, and put it in the directory /home/sage in the chroot, then ran (as the sage user in the chroot)

	:<code>make</code>		:<code>make</code>
	:<code>make test</code>		:<code>make test</code>
	:<code>make install</code>		:<code>make install</code>

Kay at 15:26, 10 September 2009

2009-09-10T15:26:11Z

← Older revision		Revision as of 15:26, 10 September 2009
Line 1:		Line 1:
	In order to chroot the Sage notebook, I used a mix of steps from the following guides:		In order to chroot the Sage notebook, I used a mix of steps from the following guides:

	* http://www.msri.org/about/computing/docs/sage/inst/node4.html		<!-- COMMENT: ] is for the right bracket HTML so that Mediawiki doesn't interpret it as the end of the link -->
	* http://www.mail-archive.com/sage-support@googlegroups.com/msg01201.html		* [http://www.msri.org/about/computing/docs/sage/inst/node4.html MSRI SAGE Installation Guide: Running the SAGE Notebook Securely]
	* http://groups.google.com/group/sage-support/msg/849e906146b41d28?pli=1		* [http://www.mail-archive.com/sage-support@googlegroups.com/msg01201.html [sage-support] Re: How to run the notebook in the background]
	* http://www.mail-archive.com/sage-devel@googlegroups.com/msg03545.html		* [http://groups.google.com/group/sage-support/msg/849e906146b41d28?pli=1 [sage-support] chroot jail -- unable to mount image file]
			* [http://www.mail-archive.com/sage-devel@googlegroups.com/msg03545.html [sage-devel] Re: SAGE in chroot]

	== Chroot ==		== Chroot ==

Kay at 15:22, 10 September 2009

2009-09-10T15:22:17Z

← Older revision		Revision as of 15:22, 10 September 2009
Line 7:		Line 7:

	== Chroot ==		== Chroot ==
	The image itself is at /mounts/bobsced/sage_chroot.image (aka /cluster/bobscednew/sage_chroot.image). It gets mounted in the same directory as sage_chroot. It ~~has an ext3~~ filesystem.		The image itself is at /mounts/bobsced/sage_chroot.image (aka /cluster/bobscednew/sage_chroot.image). It gets mounted in the same directory as sage_chroot (it's an ext3 filesystem). The chroot needs to have /dev and /proc, so here's a copy of the relevant parts of <code>/etc/fstab</code>:

			<pre>
			/mounts/bobsced/sage_chroot.image /mounts/bobsced/sage_chroot ext3 loop 0 0
			/dev /mounts/bobsced/sage_chroot/dev devpts defaults 0 0
			/proc /mounts/bobsced/sage_chroot/proc proc defaults 0 0
			</pre>

			In order to get yum to install there, I had to edit <code>/etc/yum.repos.d/CentOS-Base.repo</code> and hard code $releasever to 3.5. I also commented out all the repositories except the top one. Then I was able to run:

			:<code>yum --installroot=/mounts/bobsced/sage_chroot install bash fileutils sed which make gcc gcc-c++ m4 tar gzip bzip2 flex bison findutils yum rpm passwd perl diffutils</code>

			to set up the base install of the OS for the chroot. It also needs a copy of /etc/hosts for the localhost entry.

			== Sage Install ==
			I downloaded the tar ball normally and then moved it into the chroot from the base filesystem. I untarred it from the base filesystem, too, then ran

			:<code>make</code>
			:<code>make test</code>
			:<code>make install</code>

Kay at 15:14, 10 September 2009

2009-09-10T15:14:06Z

← Older revision		Revision as of 15:14, 10 September 2009
Line 5:		Line 5:
	* http://groups.google.com/group/sage-support/msg/849e906146b41d28?pli=1		* http://groups.google.com/group/sage-support/msg/849e906146b41d28?pli=1
	* http://www.mail-archive.com/sage-devel@googlegroups.com/msg03545.html		* http://www.mail-archive.com/sage-devel@googlegroups.com/msg03545.html

			== Chroot ==
			The image itself is at /mounts/bobsced/sage_chroot.image (aka /cluster/bobscednew/sage_chroot.image). It gets mounted in the same directory as sage_chroot. It has an ext3 filesystem.