Openstack Context is missing Nova RPCAPI Requirements

nova-compute seems to want read_deleted in RPC.

are you sure you didn't want to say 'self.show_deleted'?

Hey Armando,
   Nope. Nova-Compute expects the 'read_deleted' value inside the context
object which calls it. However, openstack-common doesn't export that by
default inside it's context, but rather, show_deleted. The two are same
from what I can gather, but perhaps not.

On Mon, Oct 22, 2012 at 8:17 PM, Armando Migliaccio <
<email address hidden>> wrote:

> are you sure you didn't want to say 'self.show_deleted'?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1061201
>
> Title:
> Openstack Context is missing Nova RPCAPI Requirements
>
> Status in openstack-common:
> New
>
> Bug description:
> Doing any sort of rpcapi from inside openstack-common, using an
> openstack-common context, there is a field missing, name
> 'read_deleted' for nova-network rpc
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-common/+bug/1061201/+subscriptions
>

It sounds like you want to use openstack.common.context..RequestContext to send RPC messages to a nova service

This isn't something we hope to support - the details of Nova's service API is private to Nova and we're not trying to expose that through openstack-common's API

If you want to do this, you must use nova.context.RequestContext

Hey Mark,
   Yup, you hit the nail on the head of what I was wanting to do with it. In another patch Vish mentioned to use HTTP instead. If I could close down this bug, I would .. although curiously, I don't see anyway to do that, other than marking it invalid as you have done and waiting for the activity to expire it.

   Ta.