-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added few more details for installation guidelines #31
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,16 +10,40 @@ Environment | |
Installation | ||
============ | ||
|
||
Since there is no stable release yet, the only option is to install the project from the source. | ||
|
||
1. Install http://github.com/tendrl/bridge_common | ||
2. Install http://github.com/tendrl/gluster_bridge | ||
Development version from the source | ||
----------------------------------- | ||
|
||
At the command line:: | ||
1. Install http://github.com/tendrl/bridge_common from the source code:: | ||
|
||
$ git clone https://github.com/Tendrl/bridge_common.git | ||
$ cd bridge_common | ||
$ mkvirtualenv bridge_common | ||
$ pip install . | ||
|
||
2. Install gluster_bridge itself:: | ||
$ git clone https://github.com/shtripat/gluster_bridge.git | ||
$ cd gluster_bridge | ||
$ workon gluster_bridge | ||
$ pip install . | ||
|
||
Note that we use virtualenvwrapper_ here to activate ``gluster_bridge`` `python | ||
virtual enviroment`_. This way, we install *gluster bridge* into the same virtual | ||
enviroment which we have created during installation of *bridge common*. | ||
|
||
.. _virtualenvwrapper: https://virtualenvwrapper.readthedocs.io/en/latest/ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I liked this note as it is informative.At-least I was not aware of this before reviewing this and was struggling to get this kind of thing working for my monitoring related stuff. Thanks ... |
||
.. _`python virtual enviroment`: https://virtualenv.pypa.io/en/stable/ | ||
|
||
3. Create config file:: | ||
|
||
$ python setup.py install | ||
$ cp etc/tendrl/tendrl.conf.sample /etc/tendrl/tendrl.conf | ||
|
||
4. Edit /etc/tendrl/tendrl.conf as required | ||
5. mkdir /var/log/tendrl | ||
6. Run | ||
$ tendrl-gluster-bridge | ||
4. Edit ``/etc/tendrl/tendrl.conf`` as required | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we add a reference to sample conf file here if it exists or add one and refer it here so that things like the conf file format and also the neessary fields of conf file can be easily known There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Its small change so should be ok I feel. |
||
|
||
5. Create log dir:: | ||
|
||
$ mkdir /var/log/tendrl | ||
|
||
6. Run:: | ||
$ tendrl-gluster-bridge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we just simply add a reference to these steps in bridge common instead of having to put the steps here again
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Earlier it was like that. But better user refers one and has the setup ready. so its OK I feel. Still if everybody feels strongly to refer from common, can be done :)