1 sipb-xen-remote-server (0.10.2) unstable; urgency=low
3 * There's a race condition for if the VM gets powered off between the
4 listvms and the actual request. Solve the problem correctly by using a
5 non-conflicting error code to indicate an invalid command
7 -- Evan Broder <broder@mit.edu> Wed, 22 Oct 2008 00:46:38 -0400
9 sipb-xen-remote-server (0.10.1) unstable; urgency=low
11 * Make both list-host and listhost valid commands, and for parity with
12 list-long, document list-host
14 -- Evan Broder <broder@mit.edu> Wed, 22 Oct 2008 00:36:32 -0400
16 sipb-xen-remote-server (0.10) unstable; urgency=low
18 * If a command is invalid, but the machine's on, give an actually useful
21 -- Evan Broder <broder@mit.edu> Wed, 22 Oct 2008 00:29:50 -0400
23 sipb-xen-remote-server (0.9.2) unstable; urgency=low
25 * Expose an interface to the autoinstaller over remctl
26 * Validate options to be passed to the autoinstaller on the remctl
29 -- Evan Broder <broder@mit.edu> Thu, 09 Oct 2008 02:06:00 -0400
31 sipb-xen-remote-server (0.9.1) unstable; urgency=low
33 * Fix a bug in the database handling code
35 -- Evan Broder <broder@mit.edu> Fri, 03 Oct 2008 18:42:48 -0400
37 sipb-xen-remote-server (0.9) unstable; urgency=low
40 * Make the acl/ subdir of RemConfFS listable
43 * Update RemConfFS for new SQLAlchemy code
45 -- Evan Broder <broder@mit.edu> Wed, 01 Oct 2008 19:28:23 -0400
47 sipb-xen-remote-server (0.8) unstable; urgency=low
49 * Use RouteFS for RemConfFS
51 -- Evan Broder <broder@mit.edu> Wed, 01 Oct 2008 02:21:00 -0400
53 sipb-xen-remote-server (0.7) unstable; urgency=low
55 * depend on sipb-xen-base
57 -- Greg Price <price@mit.edu> Tue, 30 Sep 2008 20:47:05 -0400
59 sipb-xen-remote-server (0.6) unstable; urgency=low
61 * sipb_xen_database -> invirt.config
63 -- Yang Zhang <y_z@mit.edu> Sun, 3 Aug 2008 00:54:59 -0400
65 sipb-xen-remote-server (0.5) unstable; urgency=low
67 * use invirt config in sipb-xen-remconffs, sipb-xen-remctl-help,
70 -- Yang Zhang <y_z@mit.edu> Sun, 3 Aug 2008 00:32:59 -0400
72 sipb-xen-remote-server (0.4) unstable; urgency=low
74 * use invirt.config to get hostnames
75 * refactoring: extracted bcast() function into invirt.remote package
77 -- Yang Zhang <y_z@mit.edu> Sat, 2 Aug 2008 20:34:50 -0400
79 sipb-xen-remote-server (0.3) unstable; urgency=low
81 * Fill in all the code to make the package work (mostly weeks ago.)
82 * sipb-xen-remote-listvms aggregates listvms across hosts (with
84 * sipb-xen-remctl-help gives help
85 * sipb-xen-remote-control proxies to where a machine is running
86 * sipb-xen-remote-create chooses where to boot by load-balancing
88 -- Greg Price <price@mit.edu> Thu, 24 Jul 2008 21:34:20 -0400
90 sipb-xen-remote-server (0.2) unstable; urgency=low
92 * FUSE filesystem for remctl configuration.
93 * Remove *register calls, since the FUSE keeps things up to date.
94 * An init script to keep the FUSE fs up.
96 -- Greg Price <price@mit.edu> Sat, 10 May 2008 22:04:32 -0400
98 sipb-xen-remote-server (0.1) unstable; urgency=low
102 -- Greg Price <price@mit.edu> Sun, 30 Mar 2008 01:08:50 -0400