[Freedombox-discuss] Virtual Machine Scripting and Tiny Tiny RSS
anders.jackson at gmail.com
Mon May 20 10:39:16 UTC 2013
Den 20 maj 2013 02:15 skrev "Sean Alexandre" <sean at alexan.org>:
> I went to a presentation this past weekend about Tiny Tiny RSS. It's an
> app that can be installed on a server, to provide something like a
"Google Reader" app.
> (The title of the presentation was "The Coming Google RSS Reader
> BarCampRDU 2013.)
> The presenter has Tiny Tiny RSS running on a machine at home, and is
> Tiny Tiny RSS is listed on the FreedomBox LeavingTheCloud page:
> This got me thinking about how I'd like to Tiny Tiny on the machine I've
got at home.
> Ideally I'd have a script I could run, that just spins up a new VM
running Tiny Tiny.
> It would be something like:
> freedombox-vm create tiny-tiny-rss [instance-name] [config-script-file]
> freedombox-vm start [instance-name]
> The VMs would run using KVM. Here's an interesting post on this, from
this past week:
> How to get started with libvirt on Debian
Thanks for those links.
I like the idea, a lot. Make the Freedombox a router in front of all
services, manage the network connections for all services to Internet and
the local network.
As Freedombox are targeted at low powered devices, virtual machines might
be to heavy though. You might look into containers instead. LCX might be a
better solution for this. Faster and lighter to set up, run and tear down.
And I know it works on more targets, like in ARM machines.
> I want to dig into this as a next project, after some other things I'm
> I thought I'd put it out there to get any thoughts other might have on
> find out if anyone else is doing something similar.
Yes, there are some work based on LCX. I at least have read about a duch
who made some progress about LCX last year. Very interesting work.
> Ultimately, it seems this kind of approach would be a good one for
> general. The process of spinning up instances would be hidden behind the
> web UI, but a user would essentially be doing things such as
> and "freedombox-vm start".
> This way, services are better insulated from each other, for better
> host machine would probably be doing basic network services (dhcpd,
> etc.) But then there would be a separate VM for user services such as an
> social networking, chat, etc.
I like this approach.
> To take this one step further, the longer term goal would be to do
something similar to
> what Qubes is doing with things such as temporary VMs -- VMs created
> just one task and then discarded:
> Freedombox-discuss mailing list
> Freedombox-discuss at lists.alioth.debian.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Freedombox-discuss