[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [MirageOS-devel] libvirt with mirageos and tls
On 30/07/14 09:51, Anil Madhavapeddy wrote: > On 30 Jul 2014, at 10:48, Jon Ludlam <jjl25@xxxxxxxxx> wrote: > >> On 30/07/14 09:40, Anil Madhavapeddy wrote: >>> On 30 Jul 2014, at 10:37, Jon Ludlam <jjl25@xxxxxxxxx> wrote: >>> >>>> On 30/07/14 09:32, Anil Madhavapeddy wrote: >>>>> This is a great writeup, thank you! It's very useful to see all the >>>>> libvirt steps in one place. It's a pity that Ubuntu Launchpad doesn't >>>>> build PPAs on ARM yet (as far as I know), or else we could get a binary >>>>> repository published to make these steps easier. >>>> There are lots of things we do that could benefit from nice binary >>>> repository hosting. Does anyone have a secret stash of credits for >>>> Amazon's S3? There's a tutorial of how to host repositories on it here: >>>> http://xn.pinkhamster.net/blog/tech/host-a-debian-repository-on-s3.html. >>>> RPM hosting should be similarly easy. >>> Rackspace has very generously given us developer accounts for VM hosting, >>> so blobs.openmirage.org has a healthy amount of storage (and is currently >>> hosting the ARM SDcard images). >>> >>> So we have somewhere to host the RPMs, but the most convenient aspect of >>> Launchpad is that it automates the build process as well. Have you ever >>> decrypted the mysterious workings of the OpenSUSE build service? It appears >>> to support ARM, but the Web UI is...scary. >> No, I had a similar experience with the UI! >> >> We've got automatic building here of x86 RPMs, and I suspect we're not >> too far off being able to do something similar with ARM. We're using >> Vagrant (using the vagrant-xenserver plugin) to set up build >> environments and do the builds automatically. Once the >> xenserver/buildroot packages can do the vagrant thing we should be able >> to make some base boxes for the cubieboard and then it should be simple >> to do the builds. >> >> Compute resource isn't really our problem, we need more externally >> visible storage. > Great -- we can certainly arrange to rsync the results to > blobs.openmirage.org then. Do you plan to run the Cubieboard builds > physically or in a qemu-arm environment? The Cubietrucks are pretty > fast at doing builds -- I can bring one along to the compiler hacking > session on Friday. > > -anil Physically ideally. The one stumbling block there may be is blktap on ARM - it depends upon a kernel module which is unmaintained as an out-of-tree dkms, so if there are any problems we may have to find alternatives, which would involve quite a lot of development. xenserver/buildroot's storage stack is pretty dependent on blktap right now. I'd love to have a look at the cubietruck, so please do bring it along! Jon _______________________________________________ MirageOS-devel mailing list MirageOS-devel@xxxxxxxxxxxxxxxxxxxx http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |