|
| 1 | +// vim: tw=79 |
| 2 | + |
| 3 | += SOS Report integration |
| 4 | + |
| 5 | +The propose of this file is to identify data-points and techniques for |
| 6 | +SOS Report integration with Tendrl components. |
| 7 | + |
| 8 | +== Problem description |
| 9 | +The current SOS report is not having any feature or plugin to analyze Tendrl components. Since the Tendrl components function as individual services, these components can be analysed with the help of SOS report in case of failures. |
| 10 | + |
| 11 | +== Use Cases |
| 12 | + |
| 13 | +One way to integrate SOS Report with Tendrl is creating plugin for each Tendrl component. |
| 14 | + |
| 15 | +* Usually SOS Report is run by an admin on each node to get the report. Assuming a multi-cluster environment with large number of nodes, two types of situations can come into picture here : |
| 16 | + |
| 17 | +** One or a few nodes fail and admin runs SOS-Report on them. |
| 18 | + |
| 19 | +** There is a multi-node failure. Will it feasible to let admin run SOS Report on all of the failed nodes? |
| 20 | + |
| 21 | +* Using policies in SOS Report it is decided how it will behave on a particular distribution. It has to be decided for which distributions the policies have to be written. |
| 22 | + |
| 23 | +== Proposed change |
| 24 | + |
| 25 | +For different Tendrl services their respective plugins have to be written. |
| 26 | + |
| 27 | +* Following are the data-points which can be used for the plugins: |
| 28 | + |
| 29 | +** Tendrl-node-agent |
| 30 | +*** Rpm versions for common and node-agent |
| 31 | +*** If tendrl-tendrl-epel-7.repo is enabled |
| 32 | +*** Configurations in /etc/tendrl/node-node/ |
| 33 | +*** Status of tendrl-node-agent.socket service |
| 34 | +*** SELinux configurations |
| 35 | +*** Firewall status and configurations |
| 36 | +*** Package requirements |
| 37 | + |
| 38 | +** Tendrl-gluster-integration |
| 39 | +*** Rpm versions of commons, node-agent and gluster-integration |
| 40 | +*** Tendrl-node-agent service status |
| 41 | +*** Glusterd service status |
| 42 | +*** Gdeploy status |
| 43 | +*** Gluster peer status |
| 44 | +*** Configurations in /etc/tendrl/gluster-integration/ |
| 45 | +*** Package requirements |
| 46 | + |
| 47 | +** Tendrl-ceph-integration |
| 48 | +*** Rpm versions of commons, node-agent and ceph-integration |
| 49 | +*** Tendrl-node-agent service status |
| 50 | +*** Ceph cluster health ("ceph -w" or "ceph status || ceph -w") |
| 51 | +*** Node-agent service status |
| 52 | +*** Configuration in /etc/tendrl/ceph-integration/ |
| 53 | +*** Package requirements |
| 54 | + |
| 55 | +** Tendrl-performance-monitoring |
| 56 | +*** Rpm versions of commons, node-agent and performance-monitoring |
| 57 | +*** Tendrl-node-agent service status |
| 58 | +*** GraphiteDB status and required permissions |
| 59 | +*** Carbon-cache service status |
| 60 | +*** Configurations in /etc/tendrl/performance-monitoring/ |
| 61 | +*** Package requirements |
| 62 | + |
| 63 | +** Tendrl-api |
| 64 | +*** Installed ruby version |
| 65 | +*** Package requirements |
| 66 | +*** Gem dependencies |
| 67 | +*** Apache httpd process status and configurations |
| 68 | +*** Etcd connection configuration |
| 69 | + |
| 70 | +* Since logging is common for all the Tendrl services the logs can be captured from syslog. |
| 71 | +** According to current rsyslog config the log messages are present in /var/log/messages |
| 72 | + |
| 73 | +=== Alternatives |
| 74 | + |
| 75 | +None |
| 76 | + |
| 77 | +=== Data model impact: |
| 78 | + |
| 79 | +None |
| 80 | + |
| 81 | +=== Impacted Modules: |
| 82 | + |
| 83 | +None |
| 84 | + |
| 85 | +==== Tendrl API impact: |
| 86 | + |
| 87 | +None |
| 88 | + |
| 89 | +==== Notifications/Monitoring impact: |
| 90 | + |
| 91 | +None |
| 92 | + |
| 93 | +==== Tendrl/common impact: |
| 94 | + |
| 95 | +None |
| 96 | + |
| 97 | +==== Tendrl/node_agent impact: |
| 98 | + |
| 99 | +None |
| 100 | + |
| 101 | +==== Sds integration impact: |
| 102 | + |
| 103 | +None |
| 104 | + |
| 105 | +=== Security impact: |
| 106 | + |
| 107 | +None |
| 108 | + |
| 109 | +=== Other end user impact: |
| 110 | + |
| 111 | +None |
| 112 | + |
| 113 | +=== Performance impact: |
| 114 | + |
| 115 | +None |
| 116 | + |
| 117 | +=== Other deployer impact: |
| 118 | + |
| 119 | +None |
| 120 | + |
| 121 | +=== Developer impact: |
| 122 | + |
| 123 | +None |
| 124 | + |
| 125 | +== Implementation: |
| 126 | + |
| 127 | +None |
| 128 | + |
| 129 | +=== Assignee(s): |
| 130 | + |
| 131 | +Primary assignee: |
| 132 | + anmolsachan |
| 133 | + |
| 134 | +=== Work Items: |
| 135 | + |
| 136 | +To be decided. |
| 137 | + |
| 138 | +== Dependencies: |
| 139 | + |
| 140 | +Listed in proposed change section. |
| 141 | + |
| 142 | +== Testing: |
| 143 | + |
| 144 | +None |
| 145 | + |
| 146 | +== Documentation impact: |
| 147 | + |
| 148 | +None |
| 149 | + |
| 150 | +== References: |
| 151 | + |
| 152 | +* https://github.com/Tendrl/documentation/wiki/Tendrl-Package-Installation-Reference |
| 153 | +* https://github.com/Tendrl/api#_deployment_requirements |
0 commit comments