VMLabs System - Revision history

Digitaltinker at 04:41, 6 January 2023

2023-01-06T04:41:45Z

← Older revision		Revision as of 21:41, 5 January 2023
Line 62:		Line 62:
	# Create vmlab architecture diagram		# Create vmlab architecture diagram
	# Set agenda for individual boxes & services plan		# Set agenda for individual boxes & services plan


			[[Category:Project]]

Flay at 22:48, 1 October 2016

2016-10-01T22:48:02Z

← Older revision		Revision as of 15:48, 1 October 2016
Line 19:		Line 19:


	<H1>Old VMLab Info <H1>		<H1>Old VMLab Info </H1>
	<br>		<br>
	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.

Flay: making note updates

2016-10-01T22:46:41Z

making note updates

@@ 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.
 <br>
 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.

Flay at 03:51, 17 July 2016

2016-07-17T03:51:54Z

← Older revision		Revision as of 20:51, 16 July 2016
Line 10:		Line 10:

	<br>		<br>
	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.

	<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 box, ask flay </br>

	[http://10.0.1.110:8000 Kimchi]		[http://10.0.1.110:8000 Kimchi]
Line 20:		Line 21:
	<br>pw: uas		<br>pw: uas

	~~<br>~~<br><br>		<br><br>

	<h2>VMLABS physical Specs</h2>		<h2>VMLABS physical Specs</h2>
Line 31:		Line 32:

	<h2> System Architecture </h2>		<h2> System Architecture </h2>
	TODO: Finalize plan~~, write this~~		TODO: Finalize plan.

	<h3>Links</h3>		<h3>Links</h3>
Line 44:		Line 45:
	# Create vmlab architecture diagram		# Create vmlab architecture diagram
	# Set agenda for individual boxes & services plan		# Set agenda for individual boxes & services plan


	~~<h1> If you want a vm talk to flay! </h1>~~

Flay at 03:46, 17 July 2016

2016-07-17T03:46:53Z

← Older revision		Revision as of 20:46, 16 July 2016
Line 1:		Line 1:
	VMLAB:		<H2> VMLAB Overview </H2>
			<br>
	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.

			<br>
	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 7:		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

			<br>
			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 from template (locally hosted iso's), monitor usage, and run a console through the web browser~~		<H2>Login Info </H2>

	~~Login info:~~		These credentials are suitable for anyone looking to use the vmlab as a sandbox
	~~10.0.1.110:8000~~
	~~uname:~~ vmlab
	~~pw: uas~~

	~~VMLab Specs~~:		[http://10.0.1.110:8000 Kimchi]
			<br>uname: vmlab
			<br>pw: uas

			<br><br><br>

			<h2>VMLABS physical Specs</h2>
			<br>
	OS:Ubuntu 14.04 LTS (Sorry, I built it right before the new release)		OS:Ubuntu 14.04 LTS (Sorry, I built it right before the new release)
	RAM: 64 Gb		<br>RAM: 64 Gb
	CPU: 4 dual core AMD Opterons (3GHZ)		<br>CPU: 4 dual core AMD Opterons (3GHZ)
	HDD: 660Gb		<br>HDD: 660Gb


			<h2> System Architecture </h2>
			TODO: Finalize plan, write this

			<h3>Links</h3>
			[https://github.com/kimchi-project/kimchi : Kimchi]
			<br>[https://github.com/kimchi-project/wok : Wok]
			<br>[https://www.linux.com/news/kvm-or-xen-choosing-virtualization-platform : kvm or xen]


			<h3> TODO </h3>
			# Document KVM architecture
			# Document Kimchi startup procedure
			# Create vmlab architecture diagram
			# Set agenda for individual boxes & services plan


	~~Relevant links:~~		<h1> If you want a vm talk to flay! </h1>
	~~https:~~/~~/github.com/kimchi-project/kimchi~~
	~~https://github.com/kimchi-project/wok~~
	~~https://www.linux.com/news/kvm-or-xen-choosing-virtualization-platform~~

Flay at 01:08, 17 July 2016

2016-07-17T01:08:46Z

@@ Line 1: / Line 1: @@
-Hyper-V 3.x (Server 2012 R2 release) or ESXi 5.1 (pending benchmarking of key resources such as CPU and I/O load distribution, last round of benchmarking Hyper-V trashed ESXi on our hardware for our specific usage scenarios due to how multipath I/O was handled and ram manipulation. Will test the latest update rollups of both.) managed by System Center Virtual Machine Manager 2012 R2 preview. (or RTM, if available upon launch).
+VMLAB:
-Limited user accounts are provided for users to create/share VMs using specific resource allocations per user as well as a specific SAN share for their VM's disk files and ISO uploads.
+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.
-Private file shares as well will be provided for users with individualized accounts.
+I did this through a management interface called Kimchi, which is a plugin for wok the webserver. ginger is used as a plugin mgmt system. the whole thing is backed by KVM acting as a hypervisor.

Hunterkll at 17:24, 5 August 2013

2013-08-05T17:24:09Z

← Older revision		Revision as of 10:24, 5 August 2013
Line 1:		Line 1:
	Hyper-V 3.0 or ESXi 5.1 (pending benchmarking of key resources such as CPU and I/O load distribution) managed by System Center Virtual Machine Manager 2012 R2 preview.		Hyper-V 3.x (Server 2012 R2 release) or ESXi 5.1 (pending benchmarking of key resources such as CPU and I/O load distribution, last round of benchmarking Hyper-V trashed ESXi on our hardware for our specific usage scenarios due to how multipath I/O was handled and ram manipulation. Will test the latest update rollups of both.) managed by System Center Virtual Machine Manager 2012 R2 preview. (or RTM, if available upon launch).

	Limited user accounts are provided for users to create/share VMs using specific resource allocations per user as well as a specific SAN share for their VM's disk files and ISO uploads.		Limited user accounts are provided for users to create/share VMs using specific resource allocations per user as well as a specific SAN share for their VM's disk files and ISO uploads.

			Private file shares as well will be provided for users with individualized accounts.

Hunterkll: Created page with "Hyper-V 3.0 or ESXi 5.1 (pending benchmarking of key resources such as CPU and I/O load distribution) managed by System Center Virtual Machine Manager 2012 R2 preview. Limited u..."

2013-08-05T17:22:17Z

Created page with "Hyper-V 3.0 or ESXi 5.1 (pending benchmarking of key resources such as CPU and I/O load distribution) managed by System Center Virtual Machine Manager 2012 R2 preview. Limited u..."

New page

Hyper-V 3.0 or ESXi 5.1 (pending benchmarking of key resources such as CPU and I/O load distribution) managed by System Center Virtual Machine Manager 2012 R2 preview.

Limited user accounts are provided for users to create/share VMs using specific resource allocations per user as well as a specific SAN share for their VM's disk files and ISO uploads.