IRC logs for #cip for Wednesday, 2018-11-28

*** szlin has quit IRC04:27
*** szlin has joined #cip04:27
*** dl9pf has quit IRC05:35
*** dl9pf has joined #cip05:48
*** dl9pf has joined #cip05:48
*** robertmarshall has joined #cip08:09
*** robertmarshall has quit IRC08:16
*** toscalix has joined #cip09:19
*** tpollard has joined #cip10:05
*** robertmarshall has joined #cip11:04
*** robertmarshall is now known as rajm11:28
* rajm has run an iwg20m health check email to list11:29
rajm...and a BBB health check - ditto11:29
*** mungaip has joined #cip11:50
mungaiprajm: Hello!12:07
mungaipI'm trying to setup LAVA notifications via email and IRC12:08
mungaipQ1: Does LAVA use any SMPT server installed and configured on the host machine?12:09
mungaipQ2: I assume in a dockerised setup, the SMTP server should be installed on the docker container the LAVA master is running on? Or can LAVA still use an SMTP server running on the host machine of that container?12:10
toscalixmungaip: rajm will return later. He is not connected at the moment12:50
*** mungaip has quit IRC12:57
*** mungaip has joined #cip13:43
mungaipokay thanks toscalix13:44
* rajm is returned....13:46
rajmmungaip: yes in b@d we were using an smtp server installed on the virtual machine13:47
rajmif you were to use an SMTP server installed on host (which would have an advantage wrt any local setting up passwords) I think there might be comms issues getting that communication but maybe it's just a setup to forward smtp13:48
mungaipOkay, thanks rajm13:55
patersoncrajm: How does the LAVA master pick up the SMTP server settings?13:57
rajmit assumes (I think) that the smtp server is local and communicates on that basis - let me just check up13:58
rajmthough I see https://lists.lavasoftware.org/pipermail/lava-users/2018-February/000833.html14:00
patersoncrajm: Thanks14:03
mungaiprajm: Are you still unable to ping your healthcheck results on IRC?14:14
rajmon the freenode irc server - I think so - I may have disabled it once it ceased to work14:19
toscalixafter discussing it internally, we have decided to publish a snapshot instead of doing a proper release. The main reason is that we should not release what we have no guarantee we will maintain14:19
toscalixwe will publish the new box as a snapshot, save some of the release processes and the compliance related part14:20
toscalixand add the link in a couple of places in the wiki and in the cip-dev ML14:20
toscalixas a project, releasing something that we will not provide maintenance on is a dab practice14:21
toscalixbut still the box is useful, so we will publish it14:21
patersonctoscalix: Thank you. Makes sense to me.14:22
toscalixgreat then14:22
mungaiprajm: okay thanks14:27
* rajm has updated the download and the feature page to reference the latest box14:36
toscalixlinks?14:50
toscalixdownload https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipdownload14:51
patersoncIs it worth adding a date to that snapshot release table? Or the SHA it was built from?14:56
toscalixseems like a good thing to add. Is it possible rajm?14:59
rajmyes will do15:00
rajmI've also modded https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptestingboardatdeskdingledevdeployment but the snapshot is a bit too hidden15:00
*** alicef has quit IRC15:06
* rajm adds both the SHA and the date to the download table15:06
toscalixthanks15:16
patersoncrajm: Perfect.15:22
rajm#204 has been closed!15:31
*** alicef has joined #cip15:45
*** rajm has quit IRC16:44
*** tpollard has quit IRC17:45
*** mungaip has quit IRC17:51
*** toscalix has quit IRC18:18

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!