registry team mailing list archive

[Vish Ishaya <vishvananda@xxxxxxxxx>]

This was part of moving the code to create the instance db record into
ComputeManager.  Ideally, the important info will be passed in a message
instead of the api calling the method.  Regardless, if we are going to
continue to use Manager's in two modes (locally via python import,
remotely via rpc and the Service class), we need to be careful about
where we are loading additional objects like templates.

The init_host() method is for initialization that should only happen if
the manager is run as a standalone service.  Perhaps we should move the
hyperisor connection in ComputeManager to init_host() instead of
__init__?  I think compute manager only needs to connect to the
hypervisor when it is standalone.  This problem may also go away with
the distributed data model.

Vish
On Nov 22, 2010, at 1:41 AM, Soren Hansen wrote:

> Agreed. Why does the API server need to instantiate the compute manager?
> 
> ** Changed in: nova
>   Importance: Undecided => Medium
> 
> -- 
> Nova-api requires nova-compute templates in order to run.
> https://bugs.launchpad.net/bugs/677537
> You received this bug notification because you are a member of Nova
> Bugs, which is subscribed to OpenStack Compute (nova).
> 
> Status in OpenStack Compute (Nova): New
> 
> Bug description:
> Recently, in order for the nova-api daemon it needs the --libvirt_xml_template, --libvirt_uml_xml_template, --libvirt_rescue_xml_template, and --libvirt_rescue_uml_xml_template. It is behavior that I did not expect and looks odd to me.
> 
> chuck
> 
>

-- 
Nova-api requires nova-compute templates in order to run.
https://bugs.launchpad.net/bugs/677537
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack.