Skip to content

Add contrail-service-checks charm#70

Open
n-pochet wants to merge 1 commit into
Juniper:R5from
n-pochet:add-contrail-nagios-checks
Open

Add contrail-service-checks charm#70
n-pochet wants to merge 1 commit into
Juniper:R5from
n-pochet:add-contrail-nagios-checks

Conversation

@n-pochet

@n-pochet n-pochet commented Jun 4, 2019

Copy link
Copy Markdown
  • Add reactive contrail-service-checks charm
  • Add unit and functional tests

* Add reactive contrail-service-checks charm
* Add unit and functional tests
@Andrey-mp

Copy link
Copy Markdown
Member

Hi, can you please describe what is it, why this is needed and why it's implemented in such manner?

I mean:

  • why this is separate charm and is not included into analytics?
  • why analytics api ip is added into config instead of adding relation to analytics charm?
  • why keystone creds are added to config instead of adding relation to keystone?

@n-pochet

n-pochet commented Jun 5, 2019

Copy link
Copy Markdown
Author

Hi @Andrey-mp,

  • This is a separate charm as it is not directly related to contrail analytics. The advantage is that you can modify this charm without having to release a new version of contrail-analytics.
  • This is already a config option of the contrail-controller charm. I did not see the advantage of creating a new relation just for this parameter.
  • The keystone creds can be added in two ways:
    • In the config option
    • Through a relation with keystone. This one being preferred .

@Andrey-mp

Copy link
Copy Markdown
Member

if this charm is not related to analytics then it's better to place it separately. But I would prefer to have this functionality inside analytics charm.

@aieri

aieri commented Sep 17, 2019

Copy link
Copy Markdown

Hi @Andrey-mp, has there been any progress around the topic of exporting Contrail alerts to Nagios (either within the analytics charm or separately)?

@Andrey-mp

Copy link
Copy Markdown
Member

Hi @aieri I don't see any activity here. I left my suggestions above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants