Open Stack

On Fri, Nov 09, 2012 at 01:04:50PM -0500, Russell Bryant wrote:
> Greetings,
> 
> Dan Smith and I are getting pretty close to finishing the first stage of
> no-db-compute work for Grizzly.  Specifically, that means these two things:
> 
> 1) Sending more data from the nova-api service to avoid db reads in
> nova-compute.
> 
> 2) Pulling db access out of nova virt drivers and having the only code
> in nova-compute that touches the db in nova/compute/manager.py.

[snip]

> Some questions, complications, vagueness:

I'm curious about what kind of information flow / control you see
happenning between the new component (whatever its name is :-) and
the compute nodes. From a security POV, the nova-compute service is
probably the least trusted part of our entire stack. Talking to the
DB implies a fairly high level of trust for the new service. As such
I'd hope that RPC calls are primarly /from/ the new service, to the
compute and minimal (or even none) in the other direction, so that
we're always goiong from high trusted component to a low trusted
component


Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|