VMLab - Revision history

Digitaltinker at 22:09, 21 June 2023

2023-06-21T22:09:43Z

← Older revision		Revision as of 15:09, 21 June 2023
Line 15:		Line 15:
	Anyone on the UAS network can access the VM-lab.		Anyone on the UAS network can access the VM-lab.
	<H2>Login Info </H2>		<H2>Login Info </H2>

	~~These creds will allow you to use existing vm's~~

	[https://10.0.1.8:8001 Kimchi]		[https://10.0.1.8:8001 Kimchi]
	~~<br>uname: vmlab~~
	~~<br>pw: uas~~

	~~Alternatively, you~~ can use your LDAP credentials.		You can use your LDAP credentials.

	<br> If you want a specialized machine/template to clone later, ask flay</br>		<br> If you want a specialized machine/template to clone later, ask flay</br>

Digitaltinker at 04:41, 6 January 2023

2023-01-06T04:41:56Z

← Older revision		Revision as of 21:41, 5 January 2023
Line 87:		Line 87:
	<h2> Steps to recreate this lab </h2>		<h2> Steps to recreate this lab </h2>
	[[Recreate]]		[[Recreate]]

			[[Category:Project]]

Flay at 18:17, 18 August 2018

2018-08-18T18:17:19Z

@@ Line 72: / Line 72: @@
 <br>[[Ovirt]]
 <h2> Steps to recreate this lab </h2>
 [[Recreate]]

Flay at 23:33, 6 July 2018

2018-07-06T23:33:59Z

← Older revision		Revision as of 16:33, 6 July 2018
Line 16:		Line 16:
	<H2>Login Info </H2>		<H2>Login Info </H2>

	These ~~credentials are suitable for anyone looking~~ to use ~~the vmlab as a sandbox.~~		These creds will allow you to use existing vm's

	[https://10.0.1.8:8001 Kimchi]		[https://10.0.1.8:8001 Kimchi]
Line 22:		Line 22:
	<br>pw: uas		<br>pw: uas

	Alternatively, you can use your ~~ldap~~ credentials.		Alternatively, you can use your LDAP credentials.

	<br> If you want a specialized machine/template to clone later, ask flay</br>		<br> If you want a specialized machine/template to clone later, ask flay</br>

Flay at 00:43, 6 July 2018

2018-07-06T00:43:15Z

← Older revision		Revision as of 17:43, 5 July 2018
Line 18:		Line 18:
	These credentials are suitable for anyone looking to use the vmlab as a sandbox.		These credentials are suitable for anyone looking to use the vmlab as a sandbox.

	[https://10.0.0.8:8001 Kimchi]		[https://10.0.1.8:8001 Kimchi]
	<br>uname: vmlab		<br>uname: vmlab
	<br>pw: uas		<br>pw: uas

Flay at 18:22, 24 June 2017

2017-06-24T18:22:10Z

@@ Line 25: / Line 25: @@
 <br> If you want a specialized machine/template to clone later, ask flay</br>
 <h2> Requesting a VM </h2>
 Ask flay on slack and tell him exactly what you need. If you're not sure, explain your goal and he'll try to set it up. If you need something more complex feel free to ask for administrative access to make your own.
 Every student Guest (VM) will be set up via administrator-created template.
 <h3> Administrator Notes </h3>
@@ Line 76: / Line 57: @@
 # Set agenda for individual boxes & services plan
 <h3>Links</h3>
@@ Line 82: / Line 71: @@
 <br>[https://www.linux.com/news/kvm-or-xen-choosing-virtualization-platform : kvm or xen]
 <br>[[Ovirt]]

Flay at 18:11, 24 June 2017

2017-06-24T18:11:25Z

← Older revision		Revision as of 11:11, 24 June 2017
Line 39:		Line 39:


	<h2> ~~Set-up~~ </h2>		<h2> Requesting a VM </h2>
	~~Want a VM?~~ Ask flay on slack and tell him exactly what you need. If you need something more complex feel free to ask for administrative access to make your own.		Ask flay on slack and tell him exactly what you need. If you're not sure, explain your goal and he'll try to set it up. If you need something more complex feel free to ask for administrative access to make your own.
	Every student Guest (VM) will be set up via administrator-created template.		Every student Guest (VM) will be set up via administrator-created template.

Line 53:		Line 53:

	Don't give Guests names which contain spaces. You'll get insane errors.		Don't give Guests names which contain spaces. You'll get insane errors.

			<h3>Important Paths</h3>
			This is where all iso images go
			/var/lib/kimchi/iso's

			This is where the XML templates are kept
			/etc/libvirt/qemu

			<h2>Importing from OVA </h2>

			OVA files are a common way to pass around VM's, but you cannot import them directly into a template.

			#OVA files are actually archives, so the first step is to extract them (tar -xzf example.ova)
			# Convert the virtual disk (.vmdk) into a qcow2 format using an invocation like: qemu-img convert -O qcow2 example.vmdk example.qcow2


	<h3> TODO </h3>		<h3> TODO </h3>
Line 60:		Line 75:
	# Create vmlab architecture diagram		# Create vmlab architecture diagram
	# Set agenda for individual boxes & services plan		# Set agenda for individual boxes & services plan
	~~# Set up/demo Ovirt~~

Flay at 06:27, 22 June 2017

2017-06-22T06:27:10Z

← Older revision		Revision as of 23:27, 21 June 2017
Line 25:		Line 25:

	<br> If you want a specialized machine/template to clone later, ask flay</br>		<br> If you want a specialized machine/template to clone later, ask flay</br>


	~~<br><br>~~

	<h2> Steps to recreate this lab </h2>		<h2> Steps to recreate this lab </h2>

Flay at 06:26, 22 June 2017

2017-06-22T06:26:34Z

← Older revision		Revision as of 23:26, 21 June 2017
Line 3:		Line 3:
	The rationale for this implementation was to reduce the barrier for project creation and facilitate ad hoc experimentation. It was my goal to make this minimally intimidating for inexperienced users.		The rationale for this implementation was to reduce the barrier for project creation and facilitate ad hoc experimentation. It was my goal to make this minimally intimidating for inexperienced users.

	A secondary goal was to ~~add~~		A secondary goal was to make sure this would be as useful as possible for instructors and members who wanted to run in-house services.
	I thought it easiest if those who were less confident had a familiar interface and I didn't suspect anyone regardless of experience will be offended by a GUI, so I opted for a browser based system.		I thought it easiest if those who were less confident had a familiar interface and I didn't suspect anyone regardless of experience will be offended by a GUI, so I opted for a browser based system.

Line 9:		Line 9:
	Here's a link of just the interface: https://raw.githubusercontent.com/kimchi-project/kimchi/master/docs/kimchi-templates.png		Here's a link of just the interface: https://raw.githubusercontent.com/kimchi-project/kimchi/master/docs/kimchi-templates.png

	<H1>~~EXPERIMENTATION IS ENCOURAGED!~~</H1>		<H1>How does it work?</H1>

	From the web interface, users can create VM's (guests) from template (Pre-made / provisioned VM's), monitor usage, and access the console. That means that any device that can run a web browser can in essence be used as a powerful server or specialized lab environment. This is good for classes, or designing your own services to run in the space.		From the web interface, users can create VM's (guests) from template (Pre-made / provisioned VM's), monitor usage, and access the console. That means that any device that can run a web browser can in essence be used as a powerful server or specialized lab environment. This is good for classes, or designing your own services to run in the space.

			Anyone on the UAS network can access the VM-lab.
	<H2>Login Info </H2>		<H2>Login Info </H2>

Line 41:		Line 42:


	<h2> ~~System Architecture~~ </h2>		<h2> Set-up </h2>
			Want a VM? Ask flay on slack and tell him exactly what you need. If you need something more complex feel free to ask for administrative access to make your own.
	Every student Guest (VM) will be set up via administrator-created template.		Every student Guest (VM) will be set up via administrator-created template.

Flay at 06:23, 22 June 2017

2017-06-22T06:23:00Z

← Older revision		Revision as of 23:23, 21 June 2017
Line 11:		Line 11:
	<H1>EXPERIMENTATION IS ENCOURAGED!</H1>		<H1>EXPERIMENTATION IS ENCOURAGED!</H1>

	From the web interface, users can create VM's (guests) from template (Pre-made / provisioned VM's), monitor usage, and access the console.		From the web interface, users can create VM's (guests) from template (Pre-made / provisioned VM's), monitor usage, and access the console. That means that any device that can run a web browser can in essence be used as a powerful server or specialized lab environment. This is good for classes, or designing your own services to run in the space.

	<H2>Login Info </H2>		<H2>Login Info </H2>

	These credentials are suitable for anyone looking to use the vmlab as a sandbox.		These credentials are suitable for anyone looking to use the vmlab as a sandbox.
	~~<br> If you want a specialized machine/template, ask flay~~

	[https://10.0.0.20:8001 Kimchi]		[https://10.0.0.8:8001 Kimchi]
	<br>uname: vmlab		<br>uname: vmlab
	<br>pw: uas		<br>pw: uas

			Alternatively, you can use your ldap credentials.

			<br> If you want a specialized machine/template to clone later, ask flay</br>


	<br><br>		<br><br>