Re: [Xen-devel] [OSSTEST PATCH 09/11] mg-schema-test-database: New script

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Campbell writes ("Re: [OSSTEST PATCH 09/11] mg-schema-test-database: New 
script"):
> On Fri, 2015-12-04 at 19:35 +0000, Ian Jackson wrote:
> > This allows a user in non-standalone mode to make a whole new test
> > database, which is largely a clone of the original database.
> > 
> > The new db refers to the same resources (hosts), and more-or-less
> > safely borrows some of those hosts.
> 
> "more-or-less" ? ;-)

This is a reference to the lack of owner/queue daemon handling.  (And
of course, the general limitations of `safety' in this kind of
context.)

> What's the overall idiom for use here, something like:
> 
> Against the production DB:
> OSSTEST_TASK=ianc@testing-something ./mg-allocate [-U ...] a-host
> 
> ./mg-schema-test-database create [_SUFFIX] ianc@testing-something
> 
> Ending up in a state where a-host is allocated in the production db and
> idle in this new test db and all other hosts are allocated in the test db
> and left to go about their usual business in the production db?

Exactly.  Maybe I should copy this to the doc comment :-).

> I glanced through this, but TBH I don't think picking through it line by
> line will be very productive, I trust you've tested it and its ok...

Due to being incompetent I've hammered each part of it quite a bit and
the all the resulting database states (even intermediate ones) look
good.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel