bs target

[wsehjk]

What problem does this PR solve?

Issue Number: #2564

Problem Summary:

What is changed and how it works?

What's Changed: add target/target.go, How it Works: this command is dependent on two command: curve bs status cluster and curve bs status client Side effects(Breaking backward compatibility? Performance regression?): No side effects found command output:

[
  {
    "label": {
      "job": "etcd"
    },
    "targets": [
      "172.21.0.13:23790",
      "172.21.0.13:23791",
      "172.21.0.13:23792"
    ]
  },
  {
    "label": {
      "job": "mds"
    },
    "targets": [
      "172.21.0.13:6700",
      "172.21.0.13:6701",
      "172.21.0.13:6702"
    ]
  },
  {
    "label": {
      "job": "chunkserver"
    },
    "targets": [
      "172.21.0.13:8200",
      "172.21.0.13:8202",
      "172.21.0.13:8201"
    ]
  },
  {
    "label": {
      "job": "snapshotcloneserver"
    },
    "targets": [
      "172.21.0.13:5550",
      "172.21.0.13:5551",
      "172.21.0.13:5552"
    ]
  },
  {
    "label": {
      "job": "client"
    },
    "targets": [
      "172.21.0.13:9000"
    ]
  }
]

Check List

• [x] Relevant documentation/comments is changed or added
• [x] I acknowledge that all my contributions will be made under the project's license

[caoxianfei1]

@wsehjk you should squash to one commit and modify the commit message is meaningful.

[caoxianfei1]

cicheck

[montaguelhz]

It is better to show the results of your test.

[montaguelhz]

cicheck

[caoxianfei1]

The commit message suggestion: Feat/tool: support export cluster targets for monitor.

[caoxianfei1]

The command can generate a target.json file is better. And the default path is current directory.

[wsehjk]

cicheck

[wsehjk]

cicheck

[wsehjk]

cicheck

[wsehjk]

cicheck

[wsehjk]

cicheck

[montaguelhz]

cicheck

[wsehjk]

cicheck

[wsehjk]

cicheck

[wsehjk]

cicheck

[wsehjk]

cicheck

[wsehjk]

cicheck

[wsehjk]

cicheck