search for: synnefo

Hello everybody, we are happy to announce that since v0.15.1, Synnefo is available for the CentOS distribution via our official RPM packages. For those unfamiliar with Synnefo [1], it is a complete open source cloud platform built on top of Google Ganeti [2], with OpenStack APIs. Synnefo is written in Python from scratch. CentOS is the first RPM-based distro offici...

Hello all, I'd like to introduce to you snf-image-creator, an OS image creation tool that makes heavy use of libguestfs. We have been developing it for almost 3 years and use it with the Synnefo[1] open source IaaS cloud software and also with Google's Ganeti[2] cluster management software. However it is completely independent from the above solutions and can be used as a generic image creation tool too. It comes in two variants: * snf-image-creator: A user-friendly dialog-based prog...

On Wed, Dec 03, 2014 at 02:10:08PM +0200, Nikos Skalkotos wrote: > Hello, > > I've been trying to run the tests from master, before applying my > patches and it's not not working. I always get this: > > # make -C tests/mountable check > make: Entering directory `/root/src/libguestfs/tests/mountable' > make test-internal-parse-mountable > make[1]: Entering

LGTM Another thing concerning the disklabel partitions is that list_filesystems() will print both /dev/sda1 and /dev/sda5 as ufs file systems. I don't know if you care to change this. The fact is that both are mountable. P.S. I wish the kernel folks would stop treating the disklabel partitions as logical partitions. Logical partitions are sequential, there are no gaps in the numbering. On

Hello, I've been trying to run the tests from master, before applying my patches and it's not not working. I always get this: # make -C tests/mountable check make: Entering directory `/root/src/libguestfs/tests/mountable' make test-internal-parse-mountable make[1]: Entering directory `/root/src/libguestfs/tests/mountable' make[1]: `test-internal-parse-mountable' is up to

Hello, I was looking for a way to detect the installed boot loader of an image and I found this: https://github.com/arvidjaar/bootinfoscript This script will inspection a lot of things on a running system and will output a Report. The most interesting part is that it uses known Master and Volume Boot Record byte-patterns to determine the installed boot loader: