User Tools

Site Tools


playground:computer_engineering

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
playground:computer_engineering [2012/12/21 14:57]
mcawood
playground:computer_engineering [2021/12/09 16:42] (current)
Line 1: Line 1:
  
  
-====== Further background to the problem======+====== Further background to the problem ======
  
  
Line 19: Line 19:
 ===== 21/12/2012 ===== ===== 21/12/2012 =====
  
-After 2 weeks of work, the Convey Machines can now be successfully started and stopped as well as report accurate monitoring information to OpenNebula. +After 2 weeks, the Convey Machines can now be successfully started and stopped as well as report accurate monitoring information to OpenNebula. 
-So far focus has been placed on getting the Conveys to communicate with OpenNebula. Now work must be done to allow OpenNebula to remotely deploy images onto the machines to allow them to root from different Operating Systems.+So far focus has been placed on getting the Conveys to communicate with OpenNebula. Now work must be done to allow OpenNebula to remotely deploy images onto the machines to allow them to boot from different Operating Systems.
  
 +===== 30/01/2013 =====
 +
 +A new method for modifying OpenNedula was discovered to allow for improved integration and compatibility, instead of hi-jacking the Hypervisor of the nodes, a custom Information Monitor (IM) and Virtual Machine Monitor (VMM) were created which allows the machines to be monitored while not interfering with the management infrastructure already in place for Virtual Machines. 
 +
 +The AMDDev node was configured as a Bare Metal Machine and then benchmarked to ensure that the BMM management driver was working correctly, a HPL throughput of 295.6 GFLOPS was achieved in the process.
 +
 +Attention was then placed of getting a single machine to swap Operating Systems.  This has been done by several scripts, initially the Operating System image is mounted and analyzed by a LVM (Logical Volume Manager) and a partition is created based on its size. Then the contents of the image are copied to the partition and the GRUB2 boot is loader modified to automatically select the new Operating System as the default boot device. After the system is rebooted, it is effectively running on a separate, independent Operating System.  Currently various issues are being addressed, firstly to maximize the configuration compatibility of the scripts and secondly to resolve portability issues with the Operating System images (i.e. swap space and drivers).
  
/app/dokuwiki/data/attic/playground/computer_engineering.1356094622.txt.gz · Last modified: 2021/12/09 16:42 (external edit)