Tuesday, 2020-07-21

*** openstack has joined #openstack-meeting07:30
*** ChanServ sets mode: +o openstack07:30
*** ralonsoh has joined #openstack-meeting07:30
*** rcernin_ has quit IRC07:34
*** njohnston has quit IRC07:46
*** Liang has joined #openstack-meeting07:59
*** masazumi-ota has joined #openstack-meeting08:00
*** takahashi-tsc has joined #openstack-meeting08:02
yasufumhi tacker team08:02
*** ueha has joined #openstack-meeting08:03
yasufum#startmeeting tacker08:03
openstackMeeting started Tue Jul 21 08:03:23 2020 UTC and is due to finish in 60 minutes.  The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot.08:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:03
*** openstack changes topic to " (Meeting topic: tacker)"08:03
openstackThe meeting name has been set to 'tacker'08:03
*** NAO_H has joined #openstack-meeting08:03
yasufumIs there any topic for the meeting today?08:04
takahashi-tscI have topics about my 2 Spec status and TST meeting.08:04
*** keiko-k has joined #openstack-meeting08:04
yasufumI have two topics, but priority is not so high. So, please start from takahashi-tsc.08:06
yasufum#topic etsi-nfv-tst08:06
*** openstack changes topic to "etsi-nfv-tst (Meeting topic: tacker)"08:06
*** tsukasasa has quit IRC08:07
takahashi-tscSure, as I said last meeting, I'd like to request input parameter coverage of test code to TST members.08:07
*** ociuhandu has joined #openstack-meeting08:08
takahashi-tscSee L252-08:08
*** tsukasasa has joined #openstack-meeting08:08
takahashi-tscMy request is test all patterns which is clearly specified in SOL docs like L253-264.08:08
takahashi-tscIf definition is not clear, we should propose how to define all test. My proposal is we do 2 tests, testing with input which include all attributes is set, and testing input which is only include minimum necessary attributes.08:10
takahashi-tscSo I'd like to know tacker members' comment about it.08:11
takahashi-tscAh... I forget to write URL of SOL003 and SOL013. I write it.08:13
yoshito-itoLet me confirm what the main topic is08:14
yoshito-itoAs shown from L106, we have the request to show a clear coverage of TST08:14
yoshito-itoand we have three main check points; Response code, HTTP response header, and Input parameter08:15
yoshito-itoWe are discussing how the "Input parameter" should be defined in tests08:16
takahashi-tscYes, right.08:16
yoshito-itoThen, takahashi-tsc is proposing "testing with input which include all attributes is set, and testing input which is only include minimum necessary attributes"08:16
*** rcernin_ has joined #openstack-meeting08:17
takahashi-tscYes, but this is just *my* proposal, all combination pattern may be large size and I do not know it is meaningful.08:17
takahashi-tscSo I'd like to know comment about it.08:17
yoshito-itoExactly, I agree to have a clear approach to define it not to have too many conbinations.08:18
yoshito-itoI agree with takahashi-tsc's idea. That can be the minimum set to test.08:18
takahashi-tscAre there any comment? or if you have some comments, please write in etherpad08:21
takahashi-tscComment by end of this week can be included in TST meeting proposal.08:22
yasufumYour proposal means, in other word, define mandatory and optional clearly, right?08:22
yasufumabout input params08:22
yasufumnot params, but attributes08:23
*** hyunsikyang has joined #openstack-meeting08:24
takahashi-tscYes, in addition, I want to clarify mandatory and optional attributes in test codes.08:24
*** priteau has joined #openstack-meeting08:25
yasufumI understand.08:25
yasufumWhat do you think to update our test code in addition to propose it to TST if neccesary?08:25
*** rcernin_ has quit IRC08:26
yasufumIs it not required currently?08:26
takahashi-tscDo you mean update for Tacker teams? i.e. How to manage our internal test code update?08:27
yasufumYes. I think current tacker’s test codes are not perfect, and required some updates from your point of view of the suggestion.08:29
yasufumpossibly, I mean.08:29
*** psahoo_ has joined #openstack-meeting08:29
*** e0ne has joined #openstack-meeting08:31
takahashi-tscUnderstood, I think we need some update. But such update should be defined clearly. 1 example is "test list" in my Robot Framework sepc, which select only test for Tacker support API.08:31
takahashi-tscI'd like to continue to discuss it. We make clear documentation about how to use TST code, including  update.08:32
yasufumOK, thanks08:32
*** psahoo has quit IRC08:33
yasufumIs there any comment, or can we go to the next topic?08:34
takahashi-tscCan I go next topic? it is just about spec status.08:36
hyunsikyangHi I am late.  I had a seminar today.08:36
yasufum#topic spec-status08:36
*** openstack changes topic to "spec-status (Meeting topic: tacker)"08:36
yasufumtakahashi-tsc: please share your status about specs08:37
*** moguimar has joined #openstack-meeting08:37
takahashi-tscSpec about customize LCM workflow is completed, I'm glad if you review it.08:37
takahashi-tscThank you for comment about Robot Framework use spec.08:38
takahashi-tscyoshito-ito Sorry but I want to confirm. Last comment means that you think spec is needed to be updated?08:39
yasufumI did not find the first one. I would like to check it.08:40
yoshito-itoI will.08:41
yasufumIt seems enough for this topic, so go to the next topic.08:43
yasufum#topic tacker-studio08:43
*** openstack changes topic to "tacker-studio (Meeting topic: tacker)"08:43
yasufumI have started review remained patches. This is one of them.08:45
yasufum#link https://review.opendev.org/#/c/547018/08:45
yoshito-itotakahashi-tsc: I'll update my comment on the patch08:45
yoshito-itosorry pls move to the next topic08:46
yasufumOK. no problem.08:46
hyunsikyangI will review it to:)08:47
yasufumI understand that dharmendra agreed to merge it, but there is no update because Trinh seems left from tacker dev.08:47
*** rcernin_ has joined #openstack-meeting08:47
hyunsikyangyes. right08:48
yasufumAs current status, we have no one has responsibility for that.08:48
hyunsikyangno one handle that thing.08:48
hyunsikyanghe left.08:48
yasufumI have wondered that we should continue to develop this feature, or drop it.08:48
hyunsikyangif no one want to handle it, we should remove it.08:49
hyunsikyangLet's check it it necessary or not.08:49
hyunsikyangLet's discuss it next week and vote it.08:49
yasufumThanks. I think it is wounderful if this feature is implemented in tacker.08:50
yasufumPlease continue to discuss.08:51
yasufumI have one more topic about doc update.08:51
yasufum# topic doc-update08:51
yasufum#topic doc-update08:51
*** openstack changes topic to "doc-update (Meeting topic: tacker)"08:51
hyunsikyangthanks yasfum:)08:51
yasufumAs we agreed in the previous PTG, I have started to revise docs.08:52
yasufumAnd I find that our doc is described based on Ubuntu, but not care about redhat distro, such as fedora or centos.08:53
yasufumSo I think we need to support them.08:54
yasufumBut I am not sure how we start to do.08:54
yasufumDo you have any comment?08:54
takahashi-tscsupport means both "Tacker can run on redhat distro" and "docs show how to run Tacker on redhat distro"?08:55
takahashi-tscAnd is there any issues about ”Tacker can run...”?08:56
yasufumyes. I mean the lackness of manuals for installation and how to use08:56
yasufumand so one08:56
*** baojg has quit IRC08:56
*** baojg has joined #openstack-meeting08:57
yoshito-itoI think we can update or add new installation guide for redhat distro08:57
yoshito-itoor do we have any other docs to be updated?08:57
*** tetsuro has joined #openstack-meeting08:58
yasufumI think covering installation and configuration is enogh basically.08:58
yasufumUsage is almost the same among them.08:59
*** tetsuro has quit IRC09:00
yasufumDo you anyone raise a hand for the task kindly?09:01
yasufumOr I would like to register it to blueprint as a next TODO, now…09:01
yoshito-itoWill it be a task till V release?09:03
*** tetsuro has joined #openstack-meeting09:03
yasufumI am not sure, but sooner is better.09:03
yasufumOops, it is the end of the time. Please continue to discuss in the next meeting. thanks.09:03
manpreetI have few general queries, first would like to know whether we backport documentation bugs in tacker, as I could see Bug #1887151 persist in Ussuri release docs.09:03
openstackbug 1887151 in tacker "Incorrect document link in Tacker Manual Installation " [Low,Fix released] https://launchpad.net/bugs/1887151 - Assigned to Manpreet Kaur (manpreetk)09:03
manpreetSecond in the current release could we fix documentation bug detected in the older release?09:04
manpreetPlease comment..09:04
yasufummanpreet: Thanks for your suggestions. I understand these problems, and would like to go forward.09:05
yasufumI would like to make it clear how we do backporting.09:06
*** rcernin_ has quit IRC09:07
yasufumCould we continue to discuss for making an agreement in the next meeting, or tacker IRC?09:07
manpreetThank you, yes we could discuss in next meeting.09:09
manpreetLast I would like to share my interest in networking-sfc on going participation.09:09
manpreetThank you thats all from my side.09:10
yasufumThank you for joining, bye09:12
yoshito-itothank you. bye09:12
yasufum#endmeeting tacker09:12
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:12
openstackMeeting ended Tue Jul 21 09:12:33 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:12
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-07-21-08.03.html09:12
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-07-21-08.03.txt09:12
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-07-21-08.03.log.html09:12
*** tsukasasa has quit IRC09:12
*** takahashi-tsc has quit IRC09:12
*** markvoelker has joined #openstack-meeting09:16
*** markvoelker has quit IRC09:21
*** tetsuro has quit IRC09:22
*** NAO_H has quit IRC09:23
*** tetsuro has joined #openstack-meeting09:25
*** tetsuro has quit IRC09:29
*** keiko-k has quit IRC09:35
*** rcernin_ has joined #openstack-meeting09:42
*** sluna has joined #openstack-meeting09:46
*** baojg has quit IRC09:52
*** baojg has joined #openstack-meeting09:53
*** rcernin_ has quit IRC09:55
*** yasufum has quit IRC10:06
*** ricolin has quit IRC10:18
*** psachin has joined #openstack-meeting10:22
*** Liang__ has quit IRC10:26
*** markvoelker has joined #openstack-meeting10:27
*** rcernin_ has joined #openstack-meeting10:29
*** markvoelker has quit IRC10:31
*** Lucas_Gray has joined #openstack-meeting10:33
*** masazumi-ota has quit IRC11:07
*** baojg has quit IRC11:13
*** baojg has joined #openstack-meeting11:14
*** markvoelker has joined #openstack-meeting11:18
*** markvoelker has quit IRC11:22
*** Lucas_Gray has quit IRC11:41
*** Lucas_Gray has joined #openstack-meeting11:44
*** baojg has quit IRC11:54
*** baojg has joined #openstack-meeting11:54
*** raildo has joined #openstack-meeting12:01
*** ueha has quit IRC12:01
*** ociuhandu_ has joined #openstack-meeting12:04
*** ociuhandu has quit IRC12:07
*** rfolco has joined #openstack-meeting12:08
*** rh-jelabarre has joined #openstack-meeting12:09
*** ricolin has joined #openstack-meeting12:15
*** ociuhandu_ has quit IRC12:15
*** ociuhandu has joined #openstack-meeting12:16
*** diurnalist has joined #openstack-meeting12:33
*** diurnalist has quit IRC12:37
*** baojg has quit IRC12:44
*** baojg has joined #openstack-meeting12:45
*** alecuyer has joined #openstack-meeting12:48
*** rcernin_ has quit IRC12:54
*** ricolin has quit IRC12:56
*** njohnston has joined #openstack-meeting13:00
*** njohnston has quit IRC13:05
*** njohnston has joined #openstack-meeting13:06
*** TrevorV has joined #openstack-meeting13:23
*** manpreet has quit IRC13:30
*** sluna has quit IRC13:30
*** sluna has joined #openstack-meeting13:30
*** bnemec has joined #openstack-meeting13:38
*** armstrong has joined #openstack-meeting13:38
*** baojg has quit IRC13:46
*** baojg has joined #openstack-meeting13:47
*** psachin has quit IRC13:49
*** yaawang has quit IRC14:05
*** yaawang has joined #openstack-meeting14:05
*** psahoo_ has quit IRC14:19
*** ricolin has joined #openstack-meeting14:21
*** markmcclain has quit IRC14:23
*** markmcclain has joined #openstack-meeting14:24
*** dmacpher_ has quit IRC14:25
*** dmacpher has joined #openstack-meeting14:29
*** diurnalist has joined #openstack-meeting14:32
*** Luzi has quit IRC14:34
*** mlavalle has joined #openstack-meeting14:38
*** Luzi has joined #openstack-meeting14:48
*** Luzi has quit IRC14:50
ricolin#startmeeting multi_arch15:07
openstackMeeting started Tue Jul 21 15:07:34 2020 UTC and is due to finish in 60 minutes.  The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:07
*** openstack changes topic to " (Meeting topic: multi_arch)"15:07
openstackThe meeting name has been set to 'multi_arch'15:07
ricolin#topic roll call15:07
*** openstack changes topic to "roll call (Meeting topic: multi_arch)"15:07
ricolino/ :)15:07
ricolinThere's no much progress recently, just please help on actions in https://etherpad.opendev.org/p/Multi-arch-2020-VPTG15:14
ricolin#link https://etherpad.opendev.org/p/Multi-arch-2020-VPTG15:14
ricolinWe still need to manage to have those things done:)15:14
ricolinI will send out ML for meeting next time as reminder to all(mostly for me:) )15:15
ricolin#action please help with actions on https://etherpad.opendev.org/p/Multi-arch-2020-VPTG15:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:16
openstackMeeting ended Tue Jul 21 15:16:18 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/multi_arch/2020/multi_arch.2020-07-21-15.07.html15:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/multi_arch/2020/multi_arch.2020-07-21-15.07.txt15:16
openstackLog:            http://eavesdrop.openstack.org/meetings/multi_arch/2020/multi_arch.2020-07-21-15.07.log.html15:16
*** baojg has quit IRC15:20
*** baojg has joined #openstack-meeting15:21
*** LuckyClover has joined #openstack-meeting15:31
LuckyCloverAnyone have any ideas about the cluster failing to create when you check off registry15:41
*** gyee has joined #openstack-meeting15:41
*** LuckyClover has quit IRC15:50
*** ricolin has quit IRC16:02
*** strigazi has joined #openstack-meeting16:06
*** diurnalist has quit IRC16:10
*** ociuhandu_ has joined #openstack-meeting16:17
*** ociuhandu has quit IRC16:20
*** ociuhandu_ has quit IRC16:21
*** priteau has quit IRC16:28
*** diurnalist has joined #openstack-meeting16:38
*** ralonsoh_ has joined #openstack-meeting16:41
*** ralonsoh has quit IRC16:43
*** armstrong has quit IRC16:48
*** priteau has joined #openstack-meeting17:01
*** priteau has quit IRC17:21
*** ralonsoh_ has quit IRC17:33
*** alistarle has joined #openstack-meeting17:39
*** Lucas_Gray has quit IRC17:40
*** ralonsoh has joined #openstack-meeting17:41
*** alistarle has quit IRC17:44
*** alistarle has joined #openstack-meeting17:46
*** ralonsoh has quit IRC18:08
*** alistarle has quit IRC18:14
*** diurnalist has quit IRC18:24
*** vishalmanchanda has quit IRC18:26
*** diurnalist has joined #openstack-meeting18:35
*** diurnalist has quit IRC18:39
*** haleyb has quit IRC18:39
*** haleyb has joined #openstack-meeting18:41
*** ociuhandu has joined #openstack-meeting18:48
*** diurnalist has joined #openstack-meeting18:49
*** ociuhandu has quit IRC18:53
*** ociuhandu has joined #openstack-meeting18:56
*** e0ne has quit IRC20:27
*** trandles has joined #openstack-meeting20:29
*** TrevorV has quit IRC20:31
*** ircuser-1 has joined #openstack-meeting20:40
*** rbudden has joined #openstack-meeting20:50
*** oneswig has joined #openstack-meeting20:52
*** jmlowe has joined #openstack-meeting20:59
oneswig#startmeeting scientific-sig21:00
openstackMeeting started Tue Jul 21 21:00:04 2020 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: scientific-sig)"21:00
openstackThe meeting name has been set to 'scientific_sig'21:00
oneswigI don't think there is a formal agenda set for today, any items to suggest?21:01
oneswigHi jmlowe, good afternoon.21:01
oneswigOver here we've been watching 'stranger things' - lots of Indiana-themed action.21:01
*** martial has joined #openstack-meeting21:01
oneswigHi rbudden21:01
jmloweDue to tax credits, filmed in Georga21:01
martial? :)21:02
jmloweDoesn't have quite the same look21:02
trandlesHi all21:02
oneswighi trandles martial21:02
trandlesI have an agenda item oneswig21:02
oneswig#chair martial21:02
openstackCurrent chairs: martial oneswig21:02
jmloweThey did get lots of other things just like I remember them21:02
oneswigtrandles: go for it21:02
trandlesIt's a quick one, and amusing21:02
trandlesIf anyone remembers the Slurm plugins I wrote and spoke about in Austin and Barcelona, you'll know that I submitted paperwork to the lab to get the open sourced.21:03
trandlesI haven't heard anything since October 201721:03
oneswigI remember!21:03
trandlesEven when I asked for status updates, I got nothing back.21:03
jmloweYou accidentally ripped a hole with some classified high energy experiments and allowed the Gorgon in?21:03
trandlesWell, today someone contacted me.21:03
trandlesIt looks like I'll be able to release that code after all21:03
jmloweThat's less likely than releasing the Gorgon21:03
oneswigMan, that's awesome.  I'm going to downgrade to 2017 OpenStack specially21:04
trandlesI haven't looked at it since it seemed that it would never be approved to see the light of day.21:04
trandlesSo I'll get it working with Slurm 20 and the current OpenStack API and get it released ASAP21:04
oneswig... won't that require another approval? :-)21:04
jmloweI would imagine it's covered by the open source license21:05
oneswigtrandles: can you remind us what the plugins did, and how?21:05
trandlesI wrote the request in a very open ended fashion as "Open source contributions to Slurm"21:05
jmlowemust now release every change21:05
oneswigback in a sec, kids are up21:06
trandlesTwo sets of functionality: 1) slurm grabs images from glance and deposits the on the nodes in a job allocation and 2) dynamic VLAN manipulation via Neutron controlled by slurm21:07
trandlesI'm not sure how interesting #1 is any more. I'm willing to get it working if anyone cares. #2 is definitely still interesting at least to us at LANL.21:07
*** raildo has quit IRC21:08
oneswigWith #2 was that for bare metal networking?21:08
trandlesYeah. Nothing installed on the compute hosts.21:09
oneswigDone how?21:09
trandlesThe prototype I wrote made calls to the neutron API, neutron was using the Arista ML2 plugin21:09
oneswigVery interesting.21:10
oneswigDid you have issues with scaling the number of ports?  And reliability?21:10
trandlesSo it was configuring VLANs on the switch, adding/removing/creating/deleting depending on the job's request.21:10
trandlesI never did scale past my testbed size of 48 nodes.21:10
trandlesReliability using Arista's CloudVision was fine21:11
oneswigWas it doing the port updates in a single batched operation?21:11
oneswigI've heard of similar activities using networking-generic-switch and ansible-networking21:12
trandlesI'll have to look at the code again, but as I recall it was one update to the switches per VLAN operation.21:13
jmloweIsn't there a neutron vxlan vtep thingy21:13
oneswigOne persistent problem appears to be making changes to large numbers of ports, if they can't be bulk-processed then it can lead to timeouts getting exceeded.21:13
oneswigjmlowe: if the hardware supports it, yes but I am not sure which mechanism drivers support that for bare metal.21:14
trandlesThe two use cases were isolating the nodes in a job, for instance if you were going to start up an insecure listening service (like DASK at the time), and making network-attached resources available ONLY to specific nodes in an allocation.21:14
trandlesSo for the later, imagine you have an RDBMS like Oracle that you don't want an entire cluster to be able to see or a filesystem that should only be mounted by specific nodes in an allocation.21:15
martialquestion: some people here are having a lot of issues with Octavia, is there some advice that21:16
martialI can pass along?21:16
trandlesI had thought about going further and doing things like manipulating flows at the switch hardware level21:16
trandlesBut never got that far with it21:16
oneswigtrandles: so how long would it take to program the switch with new vlan config?21:17
trandlesOn a 2-switch testbed, it was fast21:17
oneswigAnd how did you interface between slurmctld and Neutron?21:18
trandlesI want to say it didn't delay job start by more than a few seconds21:18
johnsommartial What issues are you having with Octavia?21:18
trandlesThe openstack API calls were all made by a Slurm job start plugin21:18
trandlesSlurmctld that is, not slurmd21:18
trandlesIt was a lot like some fabric management stuff that slurm had long ago for the bluegene systems from IBM IIRC21:19
trandlesAlthough that's been removed from Slurm I think21:19
trandlesI've since wondered if using PMIx's fabric setup hooks would be a better generic solution for job-specific SDN21:20
oneswigFor Ethernet and bare metal Slurm, would be a nice additional method of job isolation.21:22
trandlesI agree. I'm interested to know if slingshot, since it's based on ethernet, will have similar isolation mechanisms.21:23
trandlesI just haven't had time to get near slingshot yet. Perhaps some of you have.21:23
oneswigI wouldn't know.  They shipped 4 Shasta cabinets to Edinburgh Parallel Computing Centre a few weeks ago.21:24
*** armstrong has joined #openstack-meeting21:24
trandlesKill them with fire and throw them in a loch :P21:24
oneswigDeployment running a bit behind schedule it seems.21:25
trandles(My opinion, I speak not for LANL/NNSA/DOE)21:25
oneswigI'm sure you're just jealous of such a large body of fresh water :-)21:25
oneswigtrandles: Are you aware of the OpenDev session on bare metal networking tomorrow?  My colleague Mark is chairing.21:25
oneswigYou should join in!21:26
trandlesUnfortunately I've been too swamped to attend any of this week's sessions. :(21:26
trandlesWhat time tomorrow?21:26
oneswig13:15 UTC21:27
oneswig#link baremetal networking etherpad https://etherpad.opendev.org/p/OpenDev_HardwareAutomation_Day321:27
martialjohnsom: truthfully not 100% sure, I heard issue about port collisions21:27
trandles7:15 here, I'll be available and will attend21:27
oneswigExcellent.  It's always useful to get many points of view.21:28
johnsommartial Hm, ok, well let them know we are in the #openstack-lbaas channel and happy to help.21:28
martialjohnsom: will do21:28
trandlesIn other relevant news, I've been working quite a lot with Ironic and will be doing an internal demo for some systems staff. It's a candidate for our next bare metal cluster provisioning system.21:28
martialcool, re tomorrow, will see if my meeting is done and will try to attend :)21:29
oneswigtrandles: that would be very cool.  Is that with the deploy-to-ramdisk stuff?21:30
oneswigtrandles: did you sign up for opendev this week?  https://www.eventbrite.com/e/opendev-hardware-automation-registration-104569991660?aff=ebemnsuserinsight&afu=226342862332&utm_term=eattnewsrecs&recommended_events_quantity=6&utm_campaign=newsletter_editorial&utm_content=new_york-ny.r2020_28&utm_source=eventbrite&utm_medium=email&rank=0&ref=ebemnsuserinsight21:31
trandlesSome of it is. I'm pitching it to replace all provisioning, not just cluster but also lots of diskful infrastructure services too21:31
oneswigWe've been having fun recently with Ironic's new deploy to software RAID capability21:32
trandlesRegistered, I thought I had but that's for the containers in production event21:33
oneswig#link Software raid in Ironic blog https://www.stackhpc.com/software-raid-in-ironic.html21:33
oneswigDid you also see the baremetal whitepaper came out this week?21:34
trandlesI saw your section of the new ironic whitepaper21:34
oneswigAh, great (it's the same stuff)21:34
oneswig#link Baremetal Ironic whitepaper https://www.openstack.org/bare-metal/how-ironic-delivers-abstraction-and-automation-using-open-source-infrastructure21:36
oneswigI have to drop off, alas - all this typing is waking my kids up (either that or the after effects of Stranger Things)21:37
oneswigmartial: can you take over as chair?21:37
oneswigInteresting discussion, hopefully catch you at OpenDev tomorrow21:38
martialsure thing21:39
martialI would bet Stranger Things has something to do with it :)21:39
martialchecking the agenda to see if anything else is to be covered today21:41
martialokay not much there :)21:42
martial#topic AOB21:43
*** openstack changes topic to "AOB (Meeting topic: scientific-sig)"21:43
martialopening the floor for additional conversations as needed21:43
*** oneswig has quit IRC21:43
martialwell offering to save people 15 minutes then :)21:45
trandlesSorry, had a phone call21:47
trandlesI'll be at opened tomorrow, later everyone21:47
martialbye then, bye all :)21:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:48
openstackMeeting ended Tue Jul 21 21:48:46 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-07-21-21.00.html21:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-07-21-21.00.txt21:48
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-07-21-21.00.log.html21:48
*** moguimar has quit IRC21:59
*** trandles has quit IRC22:03
*** rcernin_ has joined #openstack-meeting22:22
*** rcernin_ has quit IRC22:22
*** rcernin has joined #openstack-meeting22:34
*** bnemec has quit IRC22:47
*** mlavalle has quit IRC23:08
*** rbudden has quit IRC23:17
*** makoto-h has quit IRC23:27
*** armstrong has quit IRC23:34
*** rbudden has joined #openstack-meeting23:53

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!