Nautilus - Revision history

Nathanrwells at 16:32, 23 September 2025

2025-09-23T16:32:28Z

← Older revision		Revision as of 11:32, 23 September 2025
Line 1:		Line 1:
			= NOTICE =

			The Nautilus folks have made changes to how we access the nautilus portal. While we work to make the system compatible, access to Nautilus through Fiona will be offline.

	== Nautilus ==		== Nautilus ==
	To access the Nautilus namespace, login using K-State SSO at https://portal.nrp-nautilus.io/ . Once you have done so, contact Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket] and request to be added to the Beocat Nautilus namespace (ksu-nrp-cluster). Once you have received notification that you have been added to the namespace, you can continue with the following steps to get set up to use the cluster resources.		To access the Nautilus namespace, login using K-State SSO at https://portal.nrp-nautilus.io/ . Once you have done so, contact Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket] and request to be added to the Beocat Nautilus namespace (ksu-nrp-cluster). Once you have received notification that you have been added to the namespace, you can continue with the following steps to get set up to use the cluster resources.

Nathanrwells: /* Nautilus */

2025-06-26T13:45:03Z

Nautilus

← Older revision		Revision as of 08:45, 26 June 2025
Line 1:		Line 1:
	== Nautilus ==		== Nautilus ==
	To access the Nautilus namespace, login using K-State SSO at https://portal.nrp-nautilus.io/ . Once you have done so, ~~email beocathelp@ksu.edu or~~ contact Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket] and request to be added to the Beocat Nautilus namespace (ksu-nrp-cluster). Once you have received notification that you have been added to the namespace, you can continue with the following steps to get set up to use the cluster resources.		To access the Nautilus namespace, login using K-State SSO at https://portal.nrp-nautilus.io/ . Once you have done so, contact Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket] and request to be added to the Beocat Nautilus namespace (ksu-nrp-cluster). Once you have received notification that you have been added to the namespace, you can continue with the following steps to get set up to use the cluster resources.
	<ol>		<ol>
	<li>SSH into headnode.beocat.ksu.edu</li>		<li>SSH into headnode.beocat.ksu.edu</li>

Nathanrwells at 20:17, 23 June 2025

2025-06-23T20:17:09Z

← Older revision		Revision as of 15:17, 23 June 2025
Line 1:		Line 1:
	== Nautilus ==		== Nautilus ==
	To access the Nautilus namespace, login using K-State SSO at https://portal.nrp-nautilus.io/ . Once you have done so, email ~~beocat~~@cs.ksu.edu and request to be added to the Beocat Nautilus namespace (ksu-nrp-cluster). Once you have received notification that you have been added to the namespace, you can continue with the following steps to get set up to use the cluster resources.		To access the Nautilus namespace, login using K-State SSO at https://portal.nrp-nautilus.io/ . Once you have done so, email beocathelp@ksu.edu or contact Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket] and request to be added to the Beocat Nautilus namespace (ksu-nrp-cluster). Once you have received notification that you have been added to the namespace, you can continue with the following steps to get set up to use the cluster resources.
	<ol>		<ol>
	<li>SSH into headnode.beocat.ksu.edu</li>		<li>SSH into headnode.beocat.ksu.edu</li>

Nathanrwells: /* Nautilus */

2024-10-10T20:24:45Z

Nautilus

← Older revision		Revision as of 15:24, 10 October 2024
Line 50:		Line 50:
	memory: 100Mi		memory: 100Mi
	cpu: 100m		cpu: 100m
	command: ["sh", "-c", "echo 'Im a new pod' ~~&& sleep infinity~~"]		command: ["sh", "-c", "echo 'Im a new pod'"]
	</syntaxhighlight>		</syntaxhighlight>
	<li>Place your .yaml file in the same directory created earlier (~/.kube).</li>		<li>Place your .yaml file in the same directory created earlier (~/.kube).</li>

Nathanrwells: /* Nautilus */

2024-10-10T17:53:05Z

Nautilus

← Older revision		Revision as of 12:53, 10 October 2024
Line 1:		Line 1:
	== Nautilus ==		== Nautilus ==
	To access the Nautilus namespace, ~~first make an account~~ at https://portal.nrp-nautilus.io/ . Once you have done so, email beocat@cs.ksu.edu and request to be added to the Beocat Nautilus namespace (ksu-nrp-cluster). Once you have received notification that you have been added to the namespace, you can continue with the following steps to get set up to use the cluster resources.		To access the Nautilus namespace, login using K-State SSO at https://portal.nrp-nautilus.io/ . Once you have done so, email beocat@cs.ksu.edu and request to be added to the Beocat Nautilus namespace (ksu-nrp-cluster). Once you have received notification that you have been added to the namespace, you can continue with the following steps to get set up to use the cluster resources.
	<ol>		<ol>
	<li>SSH into headnode.beocat.ksu.edu</li>		<li>SSH into headnode.beocat.ksu.edu</li>

Nathanrwells: /* Nautilus */

2024-10-07T16:17:21Z

Nautilus

← Older revision		Revision as of 11:17, 7 October 2024
Line 14:		Line 14:
	https://docs.nationalresearchplatform.org/userdocs/start/policies/ </li>		https://docs.nationalresearchplatform.org/userdocs/start/policies/ </li>
	a. This is to ensure we do not break any of the rules put in place by the NRP.		a. This is to ensure we do not break any of the rules put in place by the NRP.
	<br>b. Return to https://~~support~~.~~beocat~~.~~ksu.edu/Docs~~/~~Nautilus~~ and accept the Acceptable Use Policy (AUP)		<br>b. Return to https://portal.nrp-nautilus.io/ and accept the Acceptable Use Policy (AUP)
	<li>Next, return to the website specified in step 5, in the top right corner of the page press		<li>Next, return to the website specified in step 5, in the top right corner of the page press
	the “Get Config” option. </li>		the “Get Config” option. </li>

Nathanrwells: /* Nautilus */

2024-10-07T16:15:42Z

Nautilus

← Older revision		Revision as of 11:15, 7 October 2024
Line 14:		Line 14:
	https://docs.nationalresearchplatform.org/userdocs/start/policies/ </li>		https://docs.nationalresearchplatform.org/userdocs/start/policies/ </li>
	a. This is to ensure we do not break any of the rules put in place by the NRP.		a. This is to ensure we do not break any of the rules put in place by the NRP.
			<br>b. Return to https://support.beocat.ksu.edu/Docs/Nautilus and accept the Acceptable Use Policy (AUP)
	<li>Next, return to the website specified in step 5, in the top right corner of the page press		<li>Next, return to the website specified in step 5, in the top right corner of the page press
	the “Get Config” option. </li>		the “Get Config” option. </li>

Mozes: /* Nautilus */

2024-10-01T22:40:52Z

Nautilus

← Older revision		Revision as of 17:40, 1 October 2024
Line 33:		Line 33:
	K-State ID. It will look something like this “dan-pod”.</li>		K-State ID. It will look something like this “dan-pod”.</li>

	<syntaxhighlight lang=~~bash~~>		<syntaxhighlight lang=yaml>
	apiVersion: v1		apiVersion: v1
	kind: Pod		kind: Pod

Nathanrwells: /* Nautilus */

2024-10-01T22:32:43Z

Nautilus

← Older revision		Revision as of 17:32, 1 October 2024
Line 55:		Line 55:
	your current directory.</li>		your current directory.</li>
	<li>Now we are going to create our ‘pod’. This will request a ubuntu pc using the		<li>Now we are going to create our ‘pod’. This will request a ubuntu pc using the
	specifications ~~we specified earlier in pod1.yaml~~.</li>		specifications from above.</li>
	a. To do this enter the command “kubectl create -f pod1.yaml” NOTE: You must be		a. To do this enter the command “kubectl create -f pod1.yaml” NOTE: You must be
	in the same directory that you placed the pod1.yaml file in.		in the same directory that you placed the pod1.yaml file in (in this situation, the above pod config was put into a file named pod1.yaml).
	<br>b. If the command is successful you will see an output of “pod/{eid}-pod created”.		<br>b. If the command is successful you will see an output of “pod/{eid}-pod created”.
	<li>You will need to wait until the container for the pod is finished creating. You can check		<li>You will need to wait until the container for the pod is finished creating. You can check

Nathanrwells: /* Nautilus */

2024-10-01T22:31:34Z

Nautilus

← Older revision		Revision as of 17:31, 1 October 2024
Line 3:		Line 3:
	<ol>		<ol>
	<li>SSH into headnode.beocat.ksu.edu</li>		<li>SSH into headnode.beocat.ksu.edu</li>
	<li>SSH into fiona (fiona hosts the kubectl tool we will use for this ~~assignment~~)</li>		<li>SSH into fiona (fiona hosts the kubectl tool we will use for this)</li>
	<li>Once on fiona, use the command ‘cd ~’ to ensure you are in your home directory. If you		<li>Once on fiona, use the command ‘cd ~’ to ensure you are in your home directory. If you
	are not, this will return you to the top level of your home directory.<li>		are not, this will return you to the top level of your home directory.<li>