[ops-messaging]Configuring rabbitmq default password with clear test is insecure

[Ma Wen Cheng]

after use openstack-ops-messaging cookbook to deploy rabbitmq server:
cat /etc/rabbitmq/rabbitmq.config
[
  {kernel, [

  ]},
  {rabbit, [
    {ssl_listeners, [5671]},
    {ssl_options, [{cacertfile,"/opt/CA/cacert.pem"},
                    {certfile,"/opt/CA/certs/cert.pem"},
                    {keyfile,"/opt/CA/private/key.pem"},
                    {verify,verify_none},
                    {fail_if_no_peer_cert,false}]},
    {tcp_listen_options, [binary, {packet,raw},
                                  {reuseaddr,true},
                                  {backlog,128},
                                  {nodelay,true},
                                  {exit_on_close,false},
                                  {keepalive,false}]},
    {default_user, <<"rabbit">>},
    {default_pass, <<"password">>}
  ]}
].

The clear password should be removed for security purpose.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/128570
Committed: https://git.openstack.org/cgit/stackforge/cookbook-openstack-ops-messaging/commit/?id=0b087d93f34f57c6d992b6ab3fd9d8bef41bd2b2
Submitter: Jenkins
Branch: master

commit 0b087d93f34f57c6d992b6ab3fd9d8bef41bd2b2
Author: wenchma <email address hidden>
Date: Wed Oct 15 14:54:48 2014 +0800

    No need to push our rabbit user/pass to rabbit cookbook

    Because the rabbit user/pass is stored in internal user database,
    no need to push them to rabbit cookbook and expose them in config file.
    And configuring rabbitmq default password with clear test is insecure,
    so remove it.

    Change-Id: Iab95e2dc8cd28b4a45574cf8883f1626dc332db0
    Closes-Bug: #1381343

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cookbook-openstack-ops-messaging ocata-eol release.