Andrew Smith 78bc457585 Support separate oslo.messaging services for RPC and Notification ... This commit introduces oslo.messaging services in place of a single rabbitmq server. This will enable the separation of rpc and notifications for the continued use of a single backend (e.g. rabbitmq server) or a dual backend for the messaging communications. This patch: * add oslo_messaging_rpc and oslo_messaging_notify services * add puppet services for rpc and notification (rabbitmq and qdrouterd servers) * add docker services to deploy rpc (rabbitmq or qdrouterd) and notify (rabbitmq or shared) * retains rabbit parameters for core services * update resource registries, service_net_map, roles, etc. * update ci environment container scenarios * add environment generator for messaging * add release note Depends-On: Ic2c1a58526febefc1703da5fec12ff68dcc0efa0 Depends-On: I154e2fe6f66b296b9b643627d57696e5178e1815 Depends-On: I03e99d35ed043cf11bea9b7462058bd80f4d99da Needed-By: Ie181a92731e254b7f613ad25fee6cc37e985c315 Change-Id: I934561612d26befd88a9053262836b47bdf4efb0		2018-04-22 04:33:44 +00:00
..
rpc-qdrouterd-notify-rabbitmq-hybrid.yaml	Support separate oslo.messaging services for RPC and Notification	2018-04-22 04:33:44 +00:00
rpc-rabbitmq-notify-rabbitmq-shared.yaml	Support separate oslo.messaging services for RPC and Notification	2018-04-22 04:33:44 +00:00