thanks Jean Marie, somebody assigned this bug to the wrong team, taht's 
why you and others got it. I have fixed the issue now.

/stef

On Mon 08 Oct 2012 11:00:09 AM PDT, jean marie martini wrote:
> Hi there,
>
> I'm not certain why I am included on the note here - please check to see
> who should be getting this note instead of me.
>
> Many thanks,
>
> Jean Marie
>
> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On Behalf Of vivekraghuwanshi
> Sent: Monday, October 08, 2012 11:23 AM
> To: Martini, Jean Marie
> Subject: Re: [Bug 1063689] Re: CRITICAL nova [-] No module named quantum.manager
>
> Thanks for testing this file, can i go with this file for production
> setup and can i also need to run nova-network and nova-volume service
> also along with quantum and cinder
>
> On Mon, Oct 8, 2012 at 10:39 PM, Akihiro Motoki
> <email address hidden>wrote:
>
>> Your nova.conf works for me. nova-compute starts successfully with
>> your nova.conf.
>> Do you still fail to start nova-compute with this conf?
>>
>> If  I enabled the line network_manager in nova.conf, I got the same
>> error as yours:
>> 2012-10-09 02:03:18 INFO nova.compute.manager [-] Loading compute
>> driver 'libvirt.LibvirtDriver'
>> 2012-10-09 02:03:18 CRITICAL nova [-] No module named quantum.manager
>>
>> P.S.
>> I tested with git version. I tried the ubuntu package version later.
>>
>> --
>> You received this bug notification because you are subscribed to the
>> bug report.
>> https://bugs.launchpad.net/bugs/1063689
>>
>> Title:
>>    CRITICAL nova [-] No module named quantum.manager
>>
>> Status in OpenStack Community Project:
>>    New
>> Status in OpenStack Quantum (virtual network service):
>>    New
>>
>> Bug description:
>>    Hi All,
>>
>>    I am using Ubuntu 12.04 and using Folsom release with OpenVSwitch and
>>    Quantum and facing the same issue in a Folsom
>>
>>    root@us000901:/var/log/quantum# tail -f /var/log/nova/nova-compute.log
>>    2012-10-08 15:35:56 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 8
>>    2012-10-08 15:35:56 INFO nova.compute.resource_tracker [-]
>> Compute_service record updated for us000901
>>    2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free ram
>> (MB): 63874
>>    2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free
>> disk
>> (GB): 275
>>    2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 8
>>    2012-10-08 15:37:04 INFO nova.compute.resource_tracker [-]
>> Compute_service record updated for us000901
>>    2012-10-08 15:37:04 INFO nova.compute.manager [-] Updating host status
>>    2012-10-08 15:38:06 INFO nova.service [-] Caught SIGTERM, exiting
>>    2012-10-08 15:38:07 INFO nova.compute.manager [-] Loading compute
>> driver 'libvirt.LibvirtDriver'
>>    2012-10-08 15:38:07 CRITICAL nova [-] No module named
>> quantum.manager
>>
>>    My quantum-server is running
>>    root@us000901:~# /etc/init.d/quantum-server status
>>    Rather than invoking init scripts through /etc/init.d, use the service(8)
>>    utility, e.g. service quantum-server status
>>
>>    Since the script you are attempting to invoke has been converted to an
>>    Upstart job, you may also use the status(8) utility, e.g. status
>> quantum-server
>>    quantum-server start/running, process 5996
>>    root@us000901:~#
>>
>>    and i am stuck here the config is working properly in EsseX
>>    (essex+openvswitch+quantum)
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/openstack-community/+bug/1063689/+subscript
>> ions
>>
>
>
> --
> ViVek Raghuwanshi
> Mobile -+91-09595950504
>
> Skype - vivek_raghuwanshi
>
> --
> You received this bug notification because you are a member of THIS TEAM IS DEPRECATED, which is subscribed to OpenStack Community Project.
> https://bugs.launchpad.net/bugs/1063689
>
> Title:
>    CRITICAL nova [-] No module named quantum.manager
>
> Status in OpenStack Community Project:
>    New
> Status in OpenStack Quantum (virtual network service):
>    New
>
> Bug description:
>    Hi All,
>
>    I am using Ubuntu 12.04 and using Folsom release with OpenVSwitch and
>    Quantum and facing the same issue in a Folsom
>
>    root@us000901:/var/log/quantum# tail -f /var/log/nova/nova-compute.log
>    2012-10-08 15:35:56 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 8
>    2012-10-08 15:35:56 INFO nova.compute.resource_tracker [-] Compute_service record updated for us000901
>    2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 63874
>    2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 275
>    2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 8
>    2012-10-08 15:37:04 INFO nova.compute.resource_tracker [-] Compute_service record updated for us000901
>    2012-10-08 15:37:04 INFO nova.compute.manager [-] Updating host status
>    2012-10-08 15:38:06 INFO nova.service [-] Caught SIGTERM, exiting
>    2012-10-08 15:38:07 INFO nova.compute.manager [-] Loading compute driver 'libvirt.LibvirtDriver'
>    2012-10-08 15:38:07 CRITICAL nova [-] No module named quantum.manager
>
>    My quantum-server is running
>    root@us000901:~# /etc/init.d/quantum-server status
>    Rather than invoking init scripts through /etc/init.d, use the service(8)
>    utility, e.g. service quantum-server status
>
>    Since the script you are attempting to invoke has been converted to an
>    Upstart job, you may also use the status(8) utility, e.g. status quantum-server
>    quantum-server start/running, process 5996
>    root@us000901:~#
>
>    and i am stuck here the config is working properly in EsseX
>    (essex+openvswitch+quantum)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-community/+bug/1063689/+subscriptions
>