Pages

Wednesday 30 August 2017

Adding a new node to a role in crowbar

I had some issues with the swift proposal. Proxy nodes were clustered but not all nodes of the cluster were part of the storage nodes. Therefore it always failed with a message like:

See that the proposal has issues:

crowbarctl proposal show --format=json swift default > swift.json

The relevant part:
      "elements": {
        "swift-dispersion": [
          "d52-54-77-77-01-01.vh6.cloud.suse.de"
        ],
        "swift-proxy": [
          "cluster:data"
        ],
        "swift-ring-compute": [
          "d52-54-77-77-01-01.vh6.cloud.suse.de"
        ],
        "swift-storage": [
          "d52-54-77-77-01-05.vh6.cloud.suse.de",
          "d52-54-77-77-01-03.vh6.cloud.suse.de",
          "d52-54-77-77-01-04.vh6.cloud.suse.de",
          "d52-54-77-77-01-02.vh6.cloud.suse.de"
        ]

      },

Then edit the file, so you create a swift-new.json like so:

{
  "deployment": {
    "swift": {
      "elements": {
        "swift-storage": [
          "d52-54-77-77-01-05.vh6.cloud.suse.de",
          "d52-54-77-77-01-03.vh6.cloud.suse.de",
          "d52-54-77-77-01-04.vh6.cloud.suse.de",
          "d52-54-77-77-01-01.vh6.cloud.suse.de",
          "d52-54-77-77-01-02.vh6.cloud.suse.de"
        ]
      }
    }
  }
}

And edit the proposal:

crowbarctl proposal edit --merge --file swift-new.json swift default
crowbarctl proposal commit swift default

Rabbitmq Cheatsheet

I am new to rabbit, so here are some notes:

First find out where rabbit api listens:
ss -na | grep 15672

And then get the management cli:
wget  192.168.243.81:15672/cli/rabbitmqadmin
chmod +x rabbitmqadmin

Get a message from a queue:
./rabbitmqadmin --host 192.168.243.81 -u nova -p gD6Yzyvr4E7h  -V /nova get queue=notifications.info