| * ion imagined the Fast Show “this week, I ’ave been mostly eating...” character saying that. | 00:00 | |
| wasabi__ | So I wonder if it makes sense to make instance jobs for starting virtual machines, and one job that starts instance jobs | 00:00 |
|---|---|---|
| Keybuk | ion: that's the exact way you should have imageined it ;) | 00:01 |
| === pocek_ is now known as pocek | ||
| wasabi__ | So... advice. I think I know how I'll proceed on this, but I want input none the less. Writing a init set for VirtualBox. Basically, system has a set of VMs which are configured to be managed by init script set. User of the system can add new Vms to the set and stuff. He has to be able to control individual VMs with upstart. Because that rocks. | 16:16 |
| wasabi__ | Two ways I can come up with; one, make a instance job, with variables for selecting the VM. | 16:16 |
| wasabi__ | That's interesting. It has the downside that I need another job to start the instance jobs. | 16:16 |
| wasabi__ | Which might be okay! | 16:16 |
| wasabi__ | It also has the benefit that the user can start any VM by just starting an instance ad hoc | 16:17 |
| wasabi__ | Second, let the user add .conf files underneath /etc/init/virtualbox/ | 16:17 |
| wasabi__ | That has the downside that the user has to write said files, or some utility does. It has the upside that the VMs are documented within the init system. | 16:18 |
| wasabi__ | For the instance thing I'd have a file /etc/virtualbox-start.conf or somethign which simply listed the instances to run at boot. | 16:18 |
| wasabi__ | Which the master task job would bring up | 16:19 |
| ion | naurun | 18:39 |
| wasabi | Hmm. So I have pre-stop successfully terminating the process. But after it terminates it, upstart respawns it. Heh. | 21:14 |
| wasabi | normal exit. aha. | 21:15 |
| wasabi | nope. | 21:16 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!