[RFE] Ironic doesn't support zmq with oslo.messaging

[zhangjialong]

[Describe]
I deploied ironic using devstack with zmq as rpc_backend, but my ironic cannot work as expected.
Ironic node-create return 500 error.

[Step to reproduce]
1.Modify the local.conf according to [1]
2.run the ./stack
3.Then the error occured

[Version of Ironic]
master

[Ironic Config File]
http://paste.openstack.org/show/601038/

[Ironic API LOG]
http://paste.openstack.org/show/601039/

[1]: https://docs.openstack.org/developer/oslo.messaging/zmq_driver.html

[zhangjialong (zhangjl)]

I changed my devstack to using rabbitmq. After deploying, i changed the rpc_backend to zmq, then, most of ironic api were broken. And most of them return the 500 error:

ironic node-delete
ironic node-update
ironic node-validate
ironic node-vif-attach
ironic node-vif-detach

[zhangjialong (zhangjl)]

To fix this problem , one available choice is change the rpc usage like nova[1].
While, according to the discusstion in irc, ironic make heavy use of topic. Maybe, it`s better to not to change it.

While, i left my patch for anyone who also use ironic with zmq.

[zhangjialong (zhangjl)]

[1]: https://github.com/openstack/nova/blob/master/nova/compute/rpcapi.py#L427

[Galyna Zholtkevych (gzholtkevych)]

Checked and met the same error. Thank you for addressing this

[Galyna Zholtkevych (gzholtkevych)]

The reason of failures is the wrong topic (hostname should be passed to server parameter in rpc context, but not to the topic)
So then to resolve this bug RPC API version will need to be bumped (adding new parameter server to be passed to context)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/445550

[Galyna Zholtkevych (gzholtkevych)]

Investigating this more, I am not sure about bumping, IMO we could proceed without it

[Ruby Loo (rloo)]

Galyna, if this needs an RPC bump, please ping me. I'd like to get the rolling upgrades in first :)

[Vladyslav Drok (vdrok)]

Not in progress anymore.

[Ruby Loo (rloo)]

Thanks for submitting this. We discussed this in today's ironic meeting [1]. There are enough questions that we would like to see a spec describing the problem and the proposed change.

[1] http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-12-04-17.00.log.html#l-239