On Mon, 2015-06-22 at 18:10 +0100, Daniel P. Berrange wrote: > On Mon, Jun 22, 2015 at 11:10:40AM -0500, Kevin L. Mitchell wrote: > > On Sat, 2015-06-20 at 21:35 +0100, Daniel P. Berrange wrote: > > > In general I would say that is an unsupported deployment scenario to > > > have other random virt guests running on a nova compute node. > > > > On the other hand, this is exactly how compute nodes themselves are > > often deployed—a random guest on the hypervisor node… > > In a devstack env maybe, but in production we expect the hypervisor to > be exclusively used by Nova, or things Nova uses.
In production, at least in some Xen deployments, the hypervisor does not run the nova-compute service; instead, we have a VM specifically set aside for running the nova-compute. This is done because the hypervisor (in older Xen deployments, at least) has an old version of Python, and because some operations are most conveniently done by a co-located compute node. -- Kevin L. Mitchell <kevin.mitch...@rackspace.com> Rackspace __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
