Opened 10 years ago

Closed 3 years ago

#11330 closed enhancement (fixed)

Automatically build VirtualBox image

Reported by: vbraun Owned by: GeorgSWeber
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: build Keywords:
Cc: Merged in:
Authors: Volker Braun Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by ltw)

We should automatically build a VirtualBox/VMware image for each Sage release. This requires some script support to create a image and perform an unattended sage install.

sage-devel discussion

Attachments (1)

build-sage-virtualbox.tar.bz2 (3.7 KB) - added by vbraun 10 years ago.
scripts to auto-build virtual machine

Download all attachments as: .zip

Change History (15)

comment:1 Changed 10 years ago by ltw

Maybe the script can use debootstrap to create a base system, chroot into it to install whatever necessary tools (e.g. graphical environment, kernel, package manager, web browser), exit the chroot, build Sage (or copy a pre-built linux binary), wrap it up in a VirtualBox/VMware disk image, and finally configure the VM.

comment:2 Changed 10 years ago by vbraun

I'm working on an Fedora kickstart unattended install in an automatically generated VM. Its basically working, just needs some bugs ironed out. You can swap out the embedded Linux distribution with any install DVD as long as

  1. It installs without any user interaction
  2. It powers off the VM when it is done installing.
  3. It automatically installs Sage

The script that creates the VM then boots of the DVD medium and waits until the VM powers itself off...

comment:3 follow-up: Changed 10 years ago by vbraun

  • Authors set to Volker Braun
  • Description modified (diff)
  • Status changed from new to needs_info

Here is an example of the built virtual machine that is built by the attached scripts without user intervention:

http://www.stp.dias.ie/~vbraun/Sage/Sage-4.7.rc2.ova

The virtual machine starts up in text mode and automatically runs the Sage notebook server. At first startup you are prompted to enter a password, as usual. Once you set up your admin password you have to use your host OS web browser to open http://localhost:8000.

At this point it would be nice if somebody could try it out on a windows machine (or any other machine).

Changed 10 years ago by vbraun

scripts to auto-build virtual machine

comment:4 in reply to: ↑ 3 Changed 10 years ago by ltw

Replying to vbraun:

Here is an example of the built virtual machine that is built by the attached scripts without user intervention:

http://www.stp.dias.ie/~vbraun/Sage/Sage-4.7.rc2.ova

I get a "403 Forbidden" error for that file. Interestingly, I can access all of your other files in that same directory.

comment:5 Changed 10 years ago by vbraun

Sorry, wrong permissions. Fixed!

comment:6 follow-up: Changed 10 years ago by dimpase

I'll try this on a Windows 7 box, as soon as I figure out what is needed.

I got the latest VirtualBox? (4.0.6) with no guest OS installed. Do I need anything else, apart from the .ova - file, to have it running?

comment:7 Changed 10 years ago by ltw

  • Description modified (diff)

comment:8 in reply to: ↑ 6 Changed 10 years ago by dimpase

Replying to dimpase:

I'll try this on a Windows 7 box, as soon as I figure out what is needed.

I got the latest VirtualBox? (4.0.6) with no guest OS installed. Do I need anything else, apart from the .ova - file, to have it running?

for the record, it does not work, perhaps because this Windows 7 installation is itself a VMWare virtual host.

comment:9 Changed 8 years ago by jdemeyer

  • Milestone changed from sage-5.11 to sage-5.12

comment:10 Changed 8 years ago by vbraun_spam

  • Milestone changed from sage-6.1 to sage-6.2

comment:11 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.2 to sage-6.3

comment:12 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.3 to sage-6.4

comment:13 Changed 6 years ago by vbraun

  • Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix

comment:14 Changed 3 years ago by embray

  • Resolution set to fixed
  • Status changed from needs_info to closed

Seems, then, that this is done.

Note: See TracTickets for help on using tickets.