--- Log opened Tue May 05 00:00:19 2020
01:59 -!- dc0de [~jim@198.46.153.211] has quit [Remote host closed the connection]
02:00 -!- dc0de [~jim@198.46.153.211] has joined #se2600
02:00 -!- mode/#se2600 [+o dc0de] by ChanServ
02:09 -!- Netsplit *.net <-> *.split quits: @Shadow404
02:16 -!- Netsplit over, joins: @Shadow404
05:28 -!- K`Tetch_ [~no@047-039-211-239.res.spectrum.com] has joined #se2600
05:28 -!- K`Tetch_ [~no@047-039-211-239.res.spectrum.com] has quit [Changing host]
05:28 -!- K`Tetch_ [~no@unaffiliated/ktetch] has joined #se2600
05:30 -!- K`Tetch [~no@unaffiliated/ktetch] has quit [Ping timeout: 246 seconds]
06:05 <@Dolemite> mr0ning, be0tches and h0ez!
06:13  * aestetix hugs Dolemite 
06:18 <@Dolemite> I had a data migration scheduled last night...    unfortunately it was at the same time as backups.    Took nearly 5 hours to migrate 500GB from local storage to NFS.
07:22 <@dc0de> g'mernin
07:46 <@Corydon76> Dolemite: you don't keep a graph of what's scheduled to run, and how long it's expected to take?
07:47 <@Dolemite> Basically the backups run constantly off hours
07:47 <@Dolemite> But I have nothing to do with those
07:47 <@Dolemite> So I don't really keep track
07:47 <@aestetix> Dolemite: why did it take so long?
07:48 <@Dolemite> aestetix: It was just slow.    NFS writes to the Isilon have always been slow IMO.
07:49 <@Dolemite> But I no longer care/worry about physical infrastructure.    That's another group's job.
07:49 <@aestetix> so that is 100 gigs an hour
07:50 <@dc0de> I hated running any jobs during backups when I had a large SAN
07:50 <@dc0de> regardless of the software/hardware....everything was super slow during bkups.
07:52 <@Dolemite> yep
07:54 -!- rpifan [~rpifan@p200300D2673DBE30F3DE57F7376E841D.dip0.t-ipconnect.de] has joined #se2600
08:07 <@`g|-> 277Mbit/s
08:12 <@Dolemite> It's on a 10Gbit/s link
08:15 <@dc0de> I used to run a multi terrabyte FC2 SAN... and it was fast...
08:16 <@dc0de> for the time.
08:16 <@dc0de> It sure beat Ultra-Wide SCSI speeds.
08:18 <@Dolemite> Well I'm sure a factor was that it was copying a shitload of small size files.    It was all the hashed blobs from the container registry.
08:25 <@`g|-> how fast is FC2
08:25 <@`g|-> can you multithread backups?
08:26 <@`g|-> do you use netbackup?
08:26 <@`g|-> i thin that was the commercial one
08:30 <@dc0de> We used netbackup, block level backups, but we found it much easier to simply take a portion of the SAN for SNAPs, (EMC - can do them live) and then we just backed up the snaps... 24/7/365, on another SAN Switch that wasn't connected to anything else.
08:31 <@`g|-> yea that's what i did with 2 EMC Clariion's
08:32 <@`g|-> the software was atrocious, probably still is
08:32 <@Evilpig> I'd love to have netbackup back over this avamar shit we're currently using
08:33 <@`g|-> we have avamar here too
08:33 <@Dolemite> we're on avamar, too
08:33 <@`g|-> i don't do any systems work so i just verified my shit is backed up and called it a day
08:34 <@`g|-> not having and real responsibility is pretty awesome
08:34 <@`g|-> well, ansible tower is sorta mine
09:01 <@Evilpig> I like tower, but I hate it too
09:01 <@Evilpig> avamar is hot steaming garbage
09:02 <@Evilpig> the bug report we had to file with them that it woudln't restore ownership/rights was absurd
09:03 <@`g|-> i'm pivoting tower into an api-driven job execution engine and building my own frontend
09:03 <@dc0de> question: re: Ansible - can I use it to build test environments on proxmox?
09:03 <@Evilpig> probably
09:03 <@dc0de> I'm looking for the EASY button.
09:03 <@Evilpig> proxmox has an api that's exposed so you should be able to.  I havent' looked into that directly
09:03 <@dc0de> sweet.
09:04 <@`g|-> motherfuckers and their easy buttons
09:04 <@`g|-> not you specifically
09:04 <@Evilpig> https://docs.ansible.com/ansible/latest/modules/proxmox_module.html
09:04 <@Evilpig> https://docs.ansible.com/ansible/latest/modules/proxmox_kvm_module.html
09:04 <@Evilpig> a few different proxmox modules so it should be doable
09:05 <@dc0de> So, I'm gonna say, Yup.
09:05 <@dc0de> I guess I need to Learn ansible. - point me at the dummy version.
09:05 <@`g|-> https://galaxy.ansible.com/search?deprecated=false&keywords=proxmox&order_by=-relevance&page=1
09:05 <@Evilpig> https://docs.ansible.com/ansible/latest/network/getting_started/first_playbook.html
09:05 <@`g|-> steal the code
09:15 <@dc0de> nice... thanks.
09:28 -!- dc0de1 [~jim@198.46.153.211] has joined #se2600
09:28 -!- mode/#se2600 [+o dc0de1] by ChanServ
09:29 -!- dc0de [~jim@198.46.153.211] has quit [Disconnected by services]
09:29 -!- dc0de1 is now known as dc0de
10:03 <@dc0de> are NVidia Quaddro 4000's anything to be excited by?
10:08 <@Evilpig> they're nice if you need a hardware encoder
10:08 <@Evilpig> i've got a quadro p2000
10:09 <@Evilpig> iirc the main difference from the quadro line to the standard gpus is that the quadro doesn't have the two transcode limit
10:09 <@Evilpig> https://gpu.userbenchmark.com/Compare/Nvidia-Quadro-P2000-vs-Nvidia-Quadro-4000/m257811vsm7693
10:11 <@dc0de> Well, it's just that I got two of them in my new (refurbished) workstation... and I'm waiting on 10' cables to connect to my 4 monitors.
10:12 <@Evilpig> is it the p4000 or the 4000?
10:25 <@dc0de> I think just the 4000...
10:26 <@Evilpig> if it's just the 4000, it's trash.
10:26 <@dc0de> We'll see, when I get this setup.
10:43 -!- dc0de [~jim@198.46.153.211] has quit [Remote host closed the connection]
10:50 -!- dc0de [~jim@198.46.153.211] has joined #se2600
10:50 -!- mode/#se2600 [+o dc0de] by ChanServ
13:38 -!- dc0de [~jim@198.46.153.211] has quit [Remote host closed the connection]
13:45 -!- dc0de [~jim@198.46.153.211] has joined #se2600
13:45 -!- mode/#se2600 [+o dc0de] by ChanServ
13:58 -!- K`Tetch [~no@047-039-211-239.res.spectrum.com] has joined #se2600
13:58 -!- K`Tetch [~no@047-039-211-239.res.spectrum.com] has quit [Changing host]
13:58 -!- K`Tetch [~no@unaffiliated/ktetch] has joined #se2600
14:02 -!- K`Tetch_ [~no@unaffiliated/ktetch] has quit [Ping timeout: 256 seconds]
14:17 -!- K`Tetch [~no@unaffiliated/ktetch] has quit [Read error: Connection reset by peer]
14:17 -!- K`Tetch [~no@047-039-211-239.res.spectrum.com] has joined #se2600
14:17 -!- K`Tetch [~no@047-039-211-239.res.spectrum.com] has quit [Changing host]
14:17 -!- K`Tetch [~no@unaffiliated/ktetch] has joined #se2600
16:22 -!- K`Tetch_ [~no@047-039-211-239.res.spectrum.com] has joined #se2600
16:22 -!- K`Tetch_ [~no@047-039-211-239.res.spectrum.com] has quit [Changing host]
16:22 -!- K`Tetch_ [~no@unaffiliated/ktetch] has joined #se2600
16:25 -!- K`Tetch [~no@unaffiliated/ktetch] has quit [Ping timeout: 246 seconds]
16:36 -!- dc0de [~jim@198.46.153.211] has quit [Remote host closed the connection]
17:06 <@Evilpig> it appears the storms claimed another victim. my hdhomerun won't power on
17:06 <@Evilpig> hit the power supply with the voltmeter and getting a strong 5v so it's not that
17:38 -!- dc0de [~jim@198.46.153.211] has joined #se2600
17:38 -!- mode/#se2600 [+o dc0de] by ChanServ
18:00 -!- rpifan_ [~rpifan@p200300D2673DBE906052459BBB5BA189.dip0.t-ipconnect.de] has joined #se2600
18:03 -!- rpifan [~rpifan@p200300D2673DBE30F3DE57F7376E841D.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds]
18:03 -!- dc0de [~jim@198.46.153.211] has quit [Ping timeout: 256 seconds]
18:54 -!- dc0de [~jim@198.46.153.211] has joined #se2600
18:54 -!- mode/#se2600 [+o dc0de] by ChanServ
19:04 -!- rpifan__ [~rpifan@p200300D267019D5310ADBEC59A483E2F.dip0.t-ipconnect.de] has joined #se2600
19:07 -!- rpifan_ [~rpifan@p200300D2673DBE906052459BBB5BA189.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds]
21:32 -!- rpifan__ is now known as rpifan
21:41 -!- rpifan [~rpifan@p200300D267019D5310ADBEC59A483E2F.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
--- Log closed Wed May 06 00:00:20 2020