saltstack-formulas / graphite-formula Goto Github PK

View Code? Open in Web Editor NEW

15.0 43.0 41.0 57 KB

Home Page: http://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html

License: Other

Shell 12.32% Python 33.08% SaltStack 54.59%

saltstack graphite python

graphite-formula's Introduction

graphite

Formula to set up and configure graphite servers on Debian and RedHat systems

Set monitor_master role grain on the minion you want graphite installed on:

salt 'graphitemaster' grains.append roles monitor_master

Note

See the full Salt Formulas installation and usage instructions.

Starting Service

Setup database if not already done :

python /opt/graphite/webapp/graphite/manage.py syncdb

Start graphite :

/opt/graphite/bin/run-graphite-devel-server.py /opt/graphite &

Generating a new password

Uses the Passlib library :

pip install passlib

Then make:

python -c "from passlib.hash import pbkdf2_sha256; import getpass, pwd; print pbkdf2_sha256.encrypt(getpass.getpass())"
Password: [ENTER YOUR PASSWORD HERE]

Available states

`graphite`

Installs all dependencies and the graphite packages themselves, sets up a minimal system including supervisor to run carbon and django and nginx as the proxy.

`graphite.supervisor`

Adds a basic supervisor configuration for the graphite daemons to work on top of. The graphite state already depends on this one internally - eventually there should be a supervisor-formula.

`graphite.mysqldb`

Depends on the mysql-formula's mysql.client and mysql.server, makes the graphite server use mysql for the admin login.

Please note that this is a very basic (and monolithic) formula, not necessarily intended for production use.

graphite-formula's People

Contributors

Stargazers

Watchers

graphite-formula's Issues

MySQL-python is not a package in Ubuntu

The install-deps state fails because the package MySQL-python doesn't exist. In fact it appears to be a pip package.

supervisor-service not starting

Using Ubuntu:


# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.1 LTS
Release:	16.04
Codename:	xenial

On state.apply:

---------
          ID: supervisor-service
    Function: service.running
        Name: supervisor
      Result: False
     Comment: The named service supervisor is not available
     Started: 03:27:01.323226
    Duration: 31.832 ms
     Changes:

When starting manually:

# /etc/init.d/supervisor start
/etc/init.d/supervisor: line 17: /etc/rc.d/init.d/functions: No such file or directory
Starting supervisord:

formatting within the example pillar

Just fixing a few extra quotes:

    admin_email: '[email protected]''
   ...
   #admin_email: '[email protected]''

Ensure lock file location exists

The supervisor init script attempts to touch the file /var/lock/subsys/supervisord without asserting that the parent folder exists, resulting in a failure to start the service.

We should ensure this folder exists as part of the salt state.

Use debian packages for graphite deploy

The graphite packages are pretty recent https://packages.debian.org/search?keywords=graphite it would be nice to use them instead of deploying via pip.

This way we don't need to deploy supervisor, there is a supported init script.

pip not installed early enough

Traceback (most recent call last):
  File "/usr/bin/salt-call", line 11, in <module>
    salt_call()
  File "/usr/lib/python2.7/dist-packages/salt/scripts.py", line 227, in salt_call
    client.run()
  File "/usr/lib/python2.7/dist-packages/salt/cli/call.py", line 69, in run
    caller.run()
  File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 236, in run
    ret = self.call()
  File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 138, in call
    ret['return'] = func(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/salt/modules/state.py", line 681, in sls
    ret = st_.state.call_high(high_)
  File "/usr/lib/python2.7/dist-packages/salt/state.py", line 2067, in call_high
    ret = dict(list(disabled.items()) + list(self.call_chunks(chunks).items()))
  File "/usr/lib/python2.7/dist-packages/salt/state.py", line 1623, in call_chunks
    running = self.call_chunk(low, running, chunks)
  File "/usr/lib/python2.7/dist-packages/salt/state.py", line 1769, in call_chunk
    self._mod_init(low)
  File "/usr/lib/python2.7/dist-packages/salt/state.py", line 612, in _mod_init
    self.states['{0}.{1}'.format(low['state'], low['fun'])]  # pylint: disable=W0106
  File "/usr/lib/python2.7/dist-packages/salt/utils/lazy.py", line 90, in __getitem__
    raise KeyError(key)
KeyError: 'pip.installed'
root@graphite:~# salt-call --versions-report
                  Salt: 2015.5.3
                Python: 2.7.8 (default, Oct 18 2014, 12:50:18)
                Jinja2: 2.7.3
              M2Crypto: 0.21.1
        msgpack-python: 0.4.2
          msgpack-pure: Not Installed
              pycrypto: 2.6.1
               libnacl: Not Installed
                PyYAML: 3.11
                 ioflo: Not Installed
                 PyZMQ: 14.4.0
                  RAET: Not Installed
                   ZMQ: 4.0.5
                  Mako: Not Installed
               Tornado: Not Installed
 Debian source package: 2015.5.3+ds-1~bpo8+1

folders under /var/run/ won't be created after system reboot

The specific folder location is:

/var/run/gunicorn-graphite/
/var/run/carbon/

This cause graphite and carbon services start fail.
I think we should create /var/run/xxx in supervisor init script.
See more information here:
http://askubuntu.com/questions/303120/how-folders-created-in-var-run-on-each-reboot

BTW, my system is Debian 8.2

whisper directory perms should only be set on create

https://github.com/saltstack-formulas/graphite-formula/blob/master/graphite/init.sls#L86

If you have data already in that directory, the recurse can take forever.

provide a deploy of graphite-api

https://github.com/brutasse/graphite-api (Graphite-web, without the interface. Just the rendering HTTP API.) is a rewrite of parts of the graphite functionality. In some cases it's performance is far greater than graphite (remove django from the equation, has no database, pypy optimisation, etc.)

It would be nice to have a choice between the historic graphite and graphite-api.

We're starting to use the package from debian https://packages.debian.org/graphite-api but pip install might be interesting too.

sqlite3 initialize sequence fails

The state initialize-graphite-db-sqlite3 fails, with the error ImportError: No module named fields.

The solution appears to be locking django-tagging to 0.3.6.

/etc/init.d/functions (and the daemon function) doesn't exist in all distributions

/etc/init.d/functions as referenced in supervisord's init script doesn't exist in all daemons. Ubuntu's version of this (certainly in 14.04) is /lib/lsb/functions, but this doesn't contain the function daemon.

It appears the easiest way to provide this functionality is to install the daemon package in ubuntu.

saltstack-formulas / graphite-formula Goto Github PK

graphite-formula's Introduction

graphite

Starting Service

Generating a new password

Available states

graphite

graphite.supervisor

graphite.mysqldb

graphite-formula's People

Contributors

Stargazers

Watchers

Forkers

graphite-formula's Issues

Recommend Projects

Recommend Topics

Recommend Org

`graphite`

`graphite.supervisor`

`graphite.mysqldb`