Difference between revisions of "COSI Linux Build"

From CSLabsWiki
(Updated to reflect massive changes.)
Line 4: Line 4:
 
|host_vm =
 
|host_vm =
 
|vm_host =
 
|vm_host =
|services = PXE Image for COSI
+
|services = Linux Image for COSI
 
|category = Lab Build
 
|category = Lab Build
 
|handoff =
 
|handoff =
Line 12: Line 12:
 
This page summarizes how to set up and maintain the COSI Lab Build.
 
This page summarizes how to set up and maintain the COSI Lab Build.
   
  +
The lab build was once a separate project from the ITL build, but to reduce maintenance work, the ITL build is now the primary effort, and it serves well enough as the COSI lab build once several minor adjustments are made. A script is stored in /root/ of the ITL image, which can be run as root to prepare the image for use in cosi as opposed to the ITL. This script is maintained along with the ITL image itself.
The Lab Build is based off of Arch Linux. We use a read-only network drive over [http://en.wikipedia.org/wiki/Network_block_device NBD]. The disk image is created automatically [https://github.com/COSI-Lab/lab_creation with a script]. It uses standard packages with custom configuration that is automatically applied.
 
  +
  +
The ITL image is currently tracking Debian Jessie, though this may change after Jessie is released.
  +
  +
Austin's PXE cloning method is the typical way to deploy this image.
   
 
= Project Members =
 
= Project Members =
Line 25: Line 29:
   
 
= Requests =
 
= Requests =
  +
Requests for software for in COSI can go below, but please add requests for software in the ITL on the ITL Linux page.
To make requests for the lab build, the preferred method is writing a message on the whiteboard in the space allocated for this purpose. Alternatively, email the maintainer, or open a pull request on the [https://github.com/COSI-Lab/lab_creation script].
 
   
Requests for packages which are in the repositories are very likely to succeed, as well as anything in the AUR. Changes requiring significant configuration are going to take longer.
 
   
 
= Initial Configuration =
 
= Initial Configuration =
 
== Installation ==
 
== Installation ==
  +
Use Austin's PXE cloning method, and then run /root/cosify.sh as root to adjust privileges, install other software, and whatever other changes are in that script at the moment.
Here are the steps to setting up the lab build. I will assume that the host has /dev/sda3 formatted to an empty filesystem with significant (>22G) free space. It also assumes that the [https://github.com/falconindy/arch-install-scripts arch-install-scripts] are available.
 
 
Clone [https://github.com/COSI-Lab/lab_creation.git the repository]. Run make_image.sh as root. It will leave the image in /mnt/something.img.
 
   
 
[[Category:Lab Builds]]
 
[[Category:Lab Builds]]

Revision as of 23:48, 15 October 2014

COSI Linux Build
Contact Person: Corey Richardson
Last Update: unknown
Services: Linux Image for COSI


Introduction

This page summarizes how to set up and maintain the COSI Lab Build.

The lab build was once a separate project from the ITL build, but to reduce maintenance work, the ITL build is now the primary effort, and it serves well enough as the COSI lab build once several minor adjustments are made. A script is stored in /root/ of the ITL image, which can be run as root to prepare the image for use in cosi as opposed to the ITL. This script is maintained along with the ITL image itself.

The ITL image is currently tracking Debian Jessie, though this may change after Jessie is released.

Austin's PXE cloning method is the typical way to deploy this image.

Project Members

Current Maintainer

Past Maintainers

Requests

Requests for software for in COSI can go below, but please add requests for software in the ITL on the ITL Linux page.


Initial Configuration

Installation

Use Austin's PXE cloning method, and then run /root/cosify.sh as root to adjust privileges, install other software, and whatever other changes are in that script at the moment.