00:21:07  * mhicks1joined
00:21:07  * mhicksquit (Read error: Connection reset by peer)
01:05:51  * trentmquit (Quit: Leaving.)
01:06:47  * headw01quit (Quit: Leaving.)
01:20:00  * ed209quit (Remote host closed the connection)
01:20:07  * ed209joined
01:50:10  * jhendricksquit (Quit: Leaving.)
02:15:37  * dap_quit (Quit: Leaving.)
02:15:58  * pmooneyquit (Quit: WeeChat 1.5)
03:19:23  * mellocquit (Quit: Leaving.)
04:32:02  * mellocjoined
05:16:45  * mhicks1quit (Quit: Leaving.)
06:02:21  * mellocquit (Quit: Leaving.)
06:18:32  * jhendricksjoined
07:10:09  * jhendricksquit (Quit: Leaving.)
10:20:00  * ed209quit (Remote host closed the connection)
10:20:07  * ed209joined
11:34:13  * jhendricksjoined
12:29:11  * jhendricksquit (Quit: Leaving.)
15:02:20  * mhicksjoined
15:22:51  * pmooneyjoined
15:34:46  * chorrelljoined
15:40:17  * axisysjoined
15:40:51  * axisysquit (Client Quit)
16:29:49  * mhicksquit (Quit: Leaving.)
16:41:53  * mhicksjoined
16:44:14  * trentmjoined
17:02:15  * mellocjoined
17:03:51  * jhendricksjoined
17:06:12  * mellocquit (Client Quit)
17:14:18  * dap_joined
17:57:36  * mellocjoined
17:58:16  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:13:51  * pmooneyquit (Ping timeout: 256 seconds)
18:23:04  * pmooneyjoined
18:37:23  <bahamas10>metsuke: it might be - that logic could probably be handled more gracefully... i believe it does a full source tree of walk of the remote side, which will probably slower than grabbing a local file tree
18:37:35  <bahamas10>metsuke: did it ever finish? did you cancel it?
18:43:03  <metsuke>bahamas10: it did finish after about 4 hours
18:45:22  <bahamas10>metsuke: https://github.com/bahamas10/node-manta-sync/issues/7 this also applies to DELETEs (indirectly)... like most programs I started this for a small directory i wanted to sync with manta and never imagined it syncing TBs (or even GBs of data)!
18:45:30  <bahamas10>basically: it's innefficient in a lot of ways
18:45:47  <bahamas10>i'm VERY PLEASED it worked for you though! but there is still much to be done regarding performance
18:48:12  <metsuke>does work great, so thank you for maintaining it!
18:48:18  <metsuke>It does*
18:50:19  <bahamas10>:) i'll have more time tonight to take a look at speeding up the gathering logic
19:09:46  * jhendricksquit (Quit: Leaving.)
19:10:40  <metsuke>Is there a way to determine how many copies of a file exist in the Joyent cloud? I only want one, but I uploaded two, so I was going to try to delete one of the copies. It looks like I may just have to re-upload though.
19:12:01  <jayschmidt>metsuke: are you talking about durability of a manta object?
19:12:54  <jayschmidt>if so, minfo FILENAME | grep durability-level
19:15:30  <metsuke>jayschmidt: that sounds like it
19:55:43  <metsuke>jayschmidt: is there a way to change durability of an object?
19:58:02  <metsuke>never mind, I think I just found in the docs: "You cannot change "critical" headers" like durability level
19:58:57  * chorrelljoined
20:00:33  <jayschmidt>metsuke: yeah, it's read-only for you basically.
20:10:51  * therealkoopajoined
20:20:00  * ed209quit (Remote host closed the connection)
20:20:07  * ed209joined
21:05:39  * jhendricksjoined
21:06:31  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
22:04:11  * marc___joined
22:06:30  <marc___>when setting up manta with 3 data centers, the documentation when setting up the network configuration, "your SDC networks have cross datacetner connectivity and routing set up and (2) the SDC firewalls allow TCP and UDP traffic cross-datacenter"
22:07:01  <marc___>is cross-datacenter connectivity the same as linking the Triton data centers?
22:07:07  <marc___>i.e.
22:07:39  <marc___>if i have the 3 data centers linked as master-slave datacenters, does this complete the cross-datacenter connectivity?
22:10:17  <marc___>is this channel alive?
22:10:55  <bahamat>marc___: Cross-datacenter conectivity is not the same as linking datacenters, but linking datacenters should also be done.
22:11:21  <marc___>is there a link for cross-datacenter connectivity?
22:11:28  <bahamat>You want high-bandwidth, low-latency connections between each datacenter.
22:11:37  <marc___>i have 10G
22:11:50  * trentmquit (Quit: Leaving.)
22:12:02  <marc___>i'm simulating 3 datacenters within the same internal environment
22:12:09  <bahamat>The L2/L3 topology is less important than that you have high-bandwidth, low-latency.
22:12:20  <marc___>i have both
22:12:23  <bahamat>That's sufficient then.
22:12:42  <marc___>what should i follow to set up the cross-datacenter connectivity?
22:13:02  <bahamat>I would say talk to your network administrator, unless that's also you.
22:13:11  <marc___>that would be me
22:13:29  <marc___>so i have some ideas on what could be done
22:13:35  <bahamat>Each DC should be able to inter-route with the others with no packet filtering in between.
22:13:51  <marc___>i'm just a little nervous that it is looking for something very specific
22:13:56  <bahamat>It's not.
22:13:59  <marc___>such as
22:14:25  <marc___>perhaps the data centers share a network for cross-datacenter connectivity
22:14:42  <marc___>over the admin network?
22:16:15  <bahamat>Within each DC you need admin, manta, mantanat, external.
22:16:31  <marc___>got it
22:16:33  <marc___>thanks
22:16:37  <bahamat>At least admin, manta, and external need to be able to inter-route.
22:16:40  <marc___>stepping out
22:16:49  <bahamat>mantanat, I don't think needs to be able to inter-route.
22:24:35  * mhicksquit (Quit: Leaving.)
22:28:21  * mhicksjoined
22:29:42  * mhicks1joined
22:32:55  * mhicksquit (Ping timeout: 244 seconds)
23:23:14  * pmooneyquit (Quit: WeeChat 1.5)
23:28:42  * mhicks1quit (Quit: Leaving.)
23:29:03  * mhicksjoined
23:31:11  * marc___quit (Ping timeout: 260 seconds)
23:58:53  * trentmjoined