get_info and list_instances to be made async

We're supposed to move away from Twisted, so nothing gets to be async anymore.

Thanks for the heads-up! Can you fill me in? Is there a etherpad page that describes thia, and how the move is going to impact current code?

Well, things still need to be async, they just do it in a different
way. :)

On Tue, Dec 07, 2010 at 09:53:58PM -0000, Soren Hansen wrote:
> We're supposed to move away from Twisted, so nothing gets to be async
> anymore.
>
> --
> You received this bug notification because you are a member of Nova Bug
> Team, which is subscribed to OpenStack Compute (nova).
> https://bugs.launchpad.net/bugs/686772
>
> Title:
> get_info and list_instances to be made async
>
> Status in OpenStack Compute (Nova):
> New
>
> Bug description:
> I can see from the code in virt/libvirt_conn.py that most of the LibvirtConnection's methods are asynchronous. However list_instances and get_info are not.
>
> Based on Ewan's comment at revision 229 (http://bazaar.launchpad.net/~ewanmellor/nova/xenapi-concurrency-model/revision/229) it seems that these methods were meant to be made async at some point. It is not a bug per se, but it becomes an issue when compute->get_info compute->and list_instances are backed by xenapi.
>

https://blueprints.launchpad.net/nova/+spec/unified-service-architecture

On Tue, Dec 07, 2010 at 09:58:18PM -0000, Armando Migliaccio wrote:
> Thanks for the heads-up! Can you fill me in? Is there a etherpad page
> that describes thia, and how the move is going to impact current code?
>
> --
> You received this bug notification because you are a member of Nova Bug
> Team, which is subscribed to OpenStack Compute (nova).
> https://bugs.launchpad.net/bugs/686772
>
> Title:
> get_info and list_instances to be made async
>
> Status in OpenStack Compute (Nova):
> New
>
> Bug description:
> I can see from the code in virt/libvirt_conn.py that most of the LibvirtConnection's methods are asynchronous. However list_instances and get_info are not.
>
> Based on Ewan's comment at revision 229 (http://bazaar.launchpad.net/~ewanmellor/nova/xenapi-concurrency-model/revision/229) it seems that these methods were meant to be made async at some point. It is not a bug per se, but it becomes an issue when compute->get_info compute->and list_instances are backed by xenapi.
>

I was trying to do a bit of housekeeping and wanted to mark this bug 'Won't fix' but it is greyed out (like Triaged). Is that because 'Importance' has not been set yet?

Maybe you don't have privileges to do it. Hmmm...

I just set it up Won't Fix for you for now.