Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 18 2017 22:37

    shoekstra on use_nginx

    (compare)

  • Sep 18 2017 22:37

    tas50 on master

    Depend on nginx instead of chef… Use nginx >= 7.0 Merge pull request #552 from so… (compare)

  • Sep 18 2017 22:37
    tas50 closed #552
  • Sep 18 2017 22:14
    shoekstra synchronize #552
  • Sep 18 2017 22:14

    shoekstra on use_nginx

    Use nginx >= 7.0 (compare)

  • Sep 18 2017 22:12
    shoekstra commented #551
  • Sep 18 2017 22:11
    shoekstra commented #552
  • Sep 18 2017 22:11
    shoekstra commented #552
  • Sep 18 2017 22:09
    shoekstra closed #546
  • Sep 18 2017 22:09
    shoekstra commented #546
  • Sep 18 2017 22:06
    shoekstra synchronize #552
  • Sep 18 2017 22:06

    shoekstra on use_nginx

    Depend on nginx instead of chef… (compare)

  • Sep 18 2017 22:03
    shoekstra review_requested #551
  • Sep 18 2017 22:01
    shoekstra synchronize #551
  • Sep 18 2017 22:01

    shoekstra on release_8.0.0

    Release 8.0.0 (compare)

  • Sep 18 2017 22:00
    shoekstra review_requested #552
  • Sep 18 2017 22:00
    shoekstra review_requested #552
  • Sep 18 2017 22:00
    shoekstra opened #552
  • Sep 18 2017 21:59

    shoekstra on use_nginx

    Depend on nginx instead of chef… (compare)

  • Sep 18 2017 21:57
    shoekstra review_requested #551
Deepak Kosaraju
@kkdk5535
normally u don’t specify register as 0 for service defintion in nagios, we only do that for templates in best world of nagios implementation
Sander Botman
@sbotman
Remove the name. When specifying name it will register as template.
Ilja Krauchanka
@ikrauchanka
@sbotman aha, so then we should remove 'name ' from https://github.com/schubergphilis/nagios/wiki/services.cfg ?
Sander Botman
@sbotman
done
Ilja Krauchanka
@ikrauchanka

Guys, another question, sorry if it is a stupid one.
I have nagios config file with about 100 definitions for services. It looks like:

define service{
        use                             fine-vone-service
        host_name                                    fine-services-web
    service_description             API authenticaion for 192.168.220.244
        is_volatile                     0
        check_period                    24x7
        max_check_attempts              3
        normal_check_interval           10
        retry_check_interval            2
        notification_interval           20
        notification_period             24x7
        check_command                   check_fine_login!192.168.220.244
        }
define service{
        use                             fiine-vone-service
        host_name                                    fine-services-web
        service_description             API authentication for 192.168.220.245
        is_volatile                     0
        check_period                    24x7
        max_check_attempts              3
        normal_check_interval           10
        retry_check_interval            2
        notification_interval           20
        notification_period             24x7
        check_command                   check_fine_login!192.168.220.245
        }

I've already prepared them for nagios_service definitions, by converting into hashes. From the link above, service should be defined like:

nagios_service 'default-service' do

What I should pass into nagios_service instead of 'default-service' ?
As you can see I do not have names in my current nagios configs.
Thanks!

Sander Botman
@sbotman
You pass the service_description
Ilja Krauchanka
@ikrauchanka
but descriptions is ugly, they are with '/' , ' ', and even may be with '%' and no guarantee that somebody in the future will not use these characters :(
actually I already did service_description with another two cfg files,but decided ask you about to find better way.
Ilja Krauchanka
@ikrauchanka
solved in im:
A:
Well.. calling nagios_service "bla" do within a recipe, sets bla as the service_description in the object..
Q:
can I call nagios_service without "bla" ?
A:
no... objects should have a name to store them in the model
Q:
and the name I should take from service_description from nagios configs?
A:
yes
Sander Botman
@sbotman
:thumbsup:
Sander Botman
@sbotman
@joshskains on what platform are you installing?
Ken Schmidt
@Maigard
@sbotman I am around, but I am at a conference this week, so my access is spotty.
Sander Botman
@sbotman
Oke, wanted to chat about the last branch...
Ken Schmidt
@Maigard
ok.
Sander Botman
@sbotman
I looked at it and did some testing... with the pop method, do you want to remove the 'item' at all?
Or was it used for the null option to clear-out settings....
Ken Schmidt
@Maigard
I was wondering about that. I left the item there with the ussumption that without a connection to something else, it wouldn't be rendered
Sander Botman
@sbotman
Well, I already added the delete method on the Nagios.instance in the past, but that didnt remove the relations that were made within the model, so deleting a host would not delete the host in the host-group what it was a member of.
Guess we need to have a chat about this to fully explorer all the problems...when are you available on stable internet connection and out of the conference?
Ken Schmidt
@Maigard
I was trying to think of a way to remove an item if it was no longer connected to something, but couldn't come up with a good way to do it. Then decided that if an object didn't make sense anymore, it would rely on your checks to not actually put it in the config.
I won't be back until Saturday.
Sander Botman
@sbotman
Well, I will have until saturday then to write-up some tests and explorer your code...
:)
Ken Schmidt
@Maigard
Ha, I guess so. :smile:
Sander Botman
@sbotman
I already created a new branch, with the same name and fixed the merge conflict and made some changes..
It based of your code, so merging this will also merge yours...
Ken Schmidt
@Maigard
Ok, I will keep an eye on it occasionally during the conference.
Are you going to do a release in the meantime?
Sander Botman
@sbotman
I was thinking of doing that yes...
Ken Schmidt
@Maigard
ok.
Sander Botman
@sbotman
and leave this open for the next release..
Ken Schmidt
@Maigard
That sounds good.
Sander Botman
@sbotman
oke...
Thanks for your time..
Lets chat next week...
Ken Schmidt
@Maigard
thanks for looking at it.
Ilja Krauchanka
@ikrauchanka
guys, how I can include configs with legacy hosts/services which I prefer do not convert into chef cookbook?
Sander Botman
@sbotman
you mean that you have old config that you want to load that are not part of the generated templates?
Ilja Krauchanka
@ikrauchanka
yes
configs were populated in chaotic type, and I do not possibilities and time on converting them into chef definitions. So I decided just merge them into one file and include the file from nagios cookbook generated configs.
Sander Botman
@sbotman
currently chef is cleaning up the conf.d directory. It's zapping all files that don't belong to the nagios cookbook configuration... You will need to disable this if you want to add extra configuration files next to the one that are created by the cookbook
Sander Botman
@sbotman
@karnold what kind of hostgroups do you have?
Kristen Arnold
@karnold
i havent configured any hostgroups specifically, it looks like it has autogenerated groups for my various roles configured in chef
Sander Botman
@sbotman
oke, but what does the hostgroup file contain currently?
Kristen Arnold
@karnold
# $Id: Generated by chef for node: devops
# ----------------------------------------------------------------
# NOTE: This file is controlled by chef templates!
# Do not edit or change this file but change the following:
# template file : hostgroups.cfg.erb
# ----------------------------------------------------------------
# Hostgroup definitions
# ----------------------------------------------------------------

define hostgroup {
  hostgroup_name all
  alias all
  members *
}

define hostgroup {
  hostgroup_name  general
  members         chef,devops,elk,jira
}

define hostgroup {
  hostgroup_name  linux
  members         chef,devops,elk,jira
}

define hostgroup {
  hostgroup_name  monitoring
  members         devops
}

define hostgroup {
  hostgroup_name  production-admin
  members         chef,devops,elk,jira
}
Sander Botman
@sbotman
oke, so the new node is not a member of any role within chef
and it's still in the _default environment I guess...
on the other hand... it should have been a member of the hostgroup linux....
so that's a bit strange
Kristen Arnold
@karnold
it is not in the default environment, but it is in the general role with the other servers