*** dmsimard is now known as dmsimard_away | 00:05 | |
mattoliverau | smart_developer: do you have the object and container updater services running? Cause it is these that update the stats in the account and container databases. | 00:08 |
---|---|---|
smart_developer | mattoliverau : So is it the container updater service that updates the account database, and the object updater service that updates the container database ? | 00:15 |
smart_developer | Also, how do you view the account and container databases as tables (because I believe they are SQL databases)? | 00:21 |
smart_developer | Can one actually read them | 00:21 |
mattoliverau | Yeah they are sqlite databases | 00:52 |
smart_developer | mattoliverau : Where does one find them / how does one view them ? | 01:04 |
smart_developer | view* the entries in the db's | 01:04 |
*** bobbinnumerous has quit IRC | 01:18 | |
*** echevemaster has joined #openstack-swift | 01:35 | |
*** j_king_ has quit IRC | 02:30 | |
*** mandarine has quit IRC | 02:30 | |
*** kevinbenton has quit IRC | 02:31 | |
*** tristanC has quit IRC | 02:31 | |
*** mandarine has joined #openstack-swift | 02:31 | |
*** j_king has joined #openstack-swift | 02:31 | |
*** tristanC has joined #openstack-swift | 02:31 | |
*** kevinbenton has joined #openstack-swift | 02:38 | |
smart_developer | What exactly is the healthcheck middleware supposed to do? | 03:01 |
smart_developer | The description in http://docs.openstack.org/developer/swift/middleware.html#healthcheck seems kind of vague. | 03:01 |
smart_developer | And along those lines, what is the significance of DISABLED BY FILE ?? | 03:02 |
smart_developer | (it's in all-caps in the description). | 03:02 |
smart_developer | So if a file is present at "disable_path = ", does that mean the services on that node will not be used ? | 03:19 |
smart_developer | ^ that's the impending question here. | 03:19 |
smart_developer | I see what the disable_path is supposed to do, but still not exactly sure what kind of "checking" the healthcheck does for a server (for instance, it just checks whether that server is ping-able, or that the particular Swift service of interest actually functions properly)? | 03:27 |
smart_developer | basically, what kind of "health" is it checking? | 03:29 |
*** bkopilov has joined #openstack-swift | 04:15 | |
*** mrsnivvel has joined #openstack-swift | 04:44 | |
*** hhuang has joined #openstack-swift | 06:41 | |
*** hhuang has quit IRC | 07:00 | |
*** echevemaster has quit IRC | 07:09 | |
*** hhuang has joined #openstack-swift | 07:28 | |
*** mahatic has quit IRC | 07:33 | |
*** peluse has quit IRC | 08:06 | |
*** Zerpies has left #openstack-swift | 09:03 | |
*** mkollaro has joined #openstack-swift | 09:25 | |
*** jamiehannaford has joined #openstack-swift | 10:09 | |
*** mahatic has joined #openstack-swift | 10:47 | |
*** clds_ is now known as clds | 11:42 | |
ctennis | smart_developer: it allows you to enable or disable that node via the HTTP healthcheck. This is so your upstream load balancer (haproxy) knows whether it should use that machine or not as a proxy server. | 12:01 |
ctennis | smart_developer: in other words, it's a tool for you to use to put proxies into rotation | 12:01 |
ctennis | smart_developer: it's not checking any health, it's providing a status back to something checking health | 12:01 |
*** ekarlso has quit IRC | 12:29 | |
*** bkopilov has quit IRC | 12:52 | |
*** hhuang has quit IRC | 13:47 | |
*** dmsimard_away is now known as dmsimard | 14:09 | |
*** hhuang has joined #openstack-swift | 14:40 | |
*** dmsimard is now known as dmsimard_away | 14:51 | |
*** bkopilov has joined #openstack-swift | 15:05 | |
*** perfectredneck has joined #openstack-swift | 15:14 | |
*** hhuang has quit IRC | 15:32 | |
hugokuo | nice answers... | 16:04 |
*** tkay has joined #openstack-swift | 16:19 | |
*** tkay has quit IRC | 16:22 | |
*** geaaru has joined #openstack-swift | 16:54 | |
*** bkopilov has quit IRC | 17:33 | |
*** bkopilov has joined #openstack-swift | 17:56 | |
smart_developer | ctennis : Thanks! | 18:05 |
smart_developer | So, what is the siginificance of the [filter:proxy-logging] middleware? | 18:14 |
smart_developer | Sorry, emoticon automatically inserted in. | 18:14 |
smart_developer | I meant [filter : proxy-logging]. | 18:14 |
smart_developer | Isn't logging something that's set up by default ? | 18:15 |
smart_developer | why does there need to be an associated middleware with it? | 18:15 |
smart_developer | Moreover, if you look at object-server.conf, container-server.conf, and account-server.conf, you don't see middleware like [filter : object-logging], [filter : container-logging], nor [filter : account-logging] | 18:16 |
*** mahatic has quit IRC | 18:51 | |
*** annegentle has quit IRC | 18:53 | |
*** mkollaro has quit IRC | 19:00 | |
*** mahatic has joined #openstack-swift | 19:08 | |
*** bgmccollum_ has quit IRC | 19:26 | |
*** bgmccollum has joined #openstack-swift | 19:31 | |
*** mahatic has quit IRC | 20:09 | |
*** jamiehannaford has quit IRC | 20:40 | |
*** viklund has joined #openstack-swift | 21:27 | |
*** Tyger_ has joined #openstack-swift | 21:27 | |
*** charz has joined #openstack-swift | 21:29 | |
*** MooingLe1ur has joined #openstack-swift | 21:29 | |
*** yuanzz has joined #openstack-swift | 21:29 | |
*** Tyger has quit IRC | 21:31 | |
*** mitz has quit IRC | 21:31 | |
*** yuanz has quit IRC | 21:31 | |
*** charz_ has quit IRC | 21:31 | |
*** MooingLemur has quit IRC | 21:31 | |
*** ndk has quit IRC | 21:31 | |
*** viklund_ has quit IRC | 21:31 | |
*** DisneyRicky has quit IRC | 21:31 | |
*** ndk has joined #openstack-swift | 21:31 | |
*** mikehn has quit IRC | 21:31 | |
*** mikehn has joined #openstack-swift | 21:31 | |
*** MooingLe1ur is now known as MooingLemur | 21:32 | |
*** mitz has joined #openstack-swift | 21:32 | |
smart_developer | Hello? Does anyone know the answer to the proxy-logging question above ? | 21:35 |
*** craig has joined #openstack-swift | 21:36 | |
*** cdelatte has quit IRC | 21:37 | |
*** dabbler has joined #openstack-swift | 21:40 | |
*** ekarlso has joined #openstack-swift | 22:01 | |
*** ekarlso has quit IRC | 22:01 | |
*** ekarlso has joined #openstack-swift | 22:01 | |
mattoliverau | Morning all | 22:18 |
*** alpha_ori has quit IRC | 22:21 | |
*** mitz_ has quit IRC | 22:21 | |
*** geaaru has quit IRC | 22:21 | |
*** tristanC has quit IRC | 22:22 | |
mattoliverau | smart_developer: each middle ware is actually quite documented at the start of the implementation. So for proxy-logging: https://github.com/openstack/swift/blob/master/swift/common/middleware/proxy_logging.py | 22:22 |
*** tristanC has joined #openstack-swift | 22:23 | |
*** alpha_ori has joined #openstack-swift | 22:25 | |
ekarlso | /j golang | 22:27 |
*** dabbler has quit IRC | 22:27 | |
*** Trixboxer has quit IRC | 23:08 | |
smart_developer | mattoliverau : Yeah, but the question is, why is there a middleware for proxy-logging, while there isn't one for account-logging, container-logging, and object-logging ? | 23:47 |
smart_developer | and why logging is a middleware for the proxy-server - shouldn't logging be one of the default options ? | 23:48 |
smart_developer | mattoliverau : I've read the documentation in the link that you gave me, but it doesn't seem to answer my question though ..... | 23:51 |
smart_developer | :/ | 23:52 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!