15:00:42 <TheJulia> #startmeeting ironic
15:00:43 <openstack> Meeting started Mon Feb 10 15:00:42 2020 UTC and is due to finish in 60 minutes.  The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:44 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:44 <TheJulia> o/
15:00:46 <TheJulia> \o
15:00:47 <openstack> The meeting name has been set to 'ironic'
15:00:50 <TheJulia> Good morning everyone!
15:00:56 <cdearborn> o/
15:00:58 <rpioso> o/
15:01:00 <dtantsur> o/
15:01:00 <kaifeng> o/
15:01:01 <stendulker> o/
15:01:02 <etingof> \o
15:01:11 <TheJulia> Our agenda this morning can be found on the wiki - https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting
15:01:16 <TheJulia> #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting
15:01:26 <rloo> o/
15:01:27 <rpittau> o/
15:01:37 <jerrywang1> o/
15:01:41 <TheJulia> #topic Announcements / Reminders
15:02:13 <TheJulia> It seems like the mid-cycle is definitely on!
15:02:18 <TheJulia> #info OpenStack Ironic Mid-cycle Meetup, 25-26 February 2020, CERN, Geneva, Switzerland
15:02:25 <TheJulia> #link https://etherpad.openstack.org/p/ironic-ussuri-midcycle
15:02:32 <dtantsur> please tell arne_wiebalck if you're coming and provide the necessary information ASAP!
15:03:02 <TheJulia> Arne messaged me to let me know he closed registrations yesterday. If anyone is still interested in attending arne_wiebalck needs to know ASAP
15:03:07 * dtantsur wonders how many people do come in the end
15:03:18 * rpittau will be there
15:03:23 <dtantsur> rpittau: w00t!
15:03:33 <rpittau> me and my wife actually :D
15:03:37 <dtantsur> ditto :)
15:03:41 <rpittau> :)
15:03:45 <TheJulia> He also indicated the tour is full based upon registrations, so if your registered and will not be joining us, arne_wiebalck needs to know.
15:03:48 <TheJulia> triple!
15:04:08 <dtantsur> lovely :)
15:04:14 <TheJulia> #info Opendev + PTG Vancouver, Dates: Mon, Jun 8, 2020 - Thu, Jun 11, 2020
15:04:37 <dtantsur> TheJulia: have you told the foundation anything about our presence?
15:05:04 <TheJulia> They are looking for track chairs and hardware automation is something they are interested in. If anyone is interested in helping out, please feel free to reach out to me.
15:05:33 <dtantsur> I'd not mind helping, but I don't know if I'm coming (and won't know soon)
15:05:38 <TheJulia> dtantsur: I have not, but I would assume that they wouldn't be unaware as some of the staffers do join the channel occassionally for our meetings
15:06:05 * rpittau wouldn't mind helping and definitely wouldn't mind some maple syrup
15:06:05 <TheJulia> Also, if anyone is in the eastern US, there is a conference that is looking for topics
15:06:10 * TheJulia looks for the link
15:07:03 <TheJulia> #info 2020 Open Cloud Workshop - March 2-3
15:07:04 <dtantsur> ping me if you need an ironic talk in the Central Europe :)
15:07:08 <TheJulia> #link https://docs.google.com/forms/d/e/1FAIpQLSen4GUE_9MkJIomYazU933k8lRnNpdJgU-cwbpC1DVZn2upsQ/viewform
15:07:33 <TheJulia> That closes in just a few days
15:07:53 <TheJulia> Anyway, Does anyone have anything else to announce or remind us of this morning?
15:08:02 <etingof> dtantsur, pycon in Ostrava? ;)
15:08:13 <dtantsur> Ostrava, oh my :D
15:08:21 <TheJulia> dtantsur: I feel like maybe we should somehow demo kexec in Berlin :)
15:08:21 <etingof> (very much Central Europe, as you wish!)
15:08:33 <dtantsur> TheJulia: mmmmm :)
15:08:49 <TheJulia> of course, patches merge conflicted long ago
15:08:55 <TheJulia> and not yet tested
15:09:11 <dtantsur> kexec + fast-forward, going to be hot!
15:09:13 <TheJulia> We had no action items last week, so it seems like we can skip past that
15:09:22 <dtantsur> mmmm, fast-track
15:09:38 <TheJulia> Add in the ability for an instance to be redeployed from a running instance and the supercomputer folks will drool
15:09:52 <dtantsur> that sounds much trickier though
15:10:05 <TheJulia> Less than you'd think, but we can discuss it in a few weeks
15:10:13 <dtantsur> sure
15:10:17 <TheJulia> Anyway, moving on
15:10:24 <dtantsur> damn, we should have requested 3 days in CERN
15:10:29 <TheJulia> #topic Review subteam status reports
15:10:32 <TheJulia> dtantsur: doh!
15:10:53 <dtantsur> what about a follow-up hiking with technical discussions? :D
15:10:57 <TheJulia> Oh, one annoucement, I'm taking the rest of the week off after the midcycle
15:11:03 <dtantsur> ditto ^^^
15:11:36 <yolanda> etingof, why is node starting cleaning if i have automated_clean=false on ironic conductor?
15:11:37 <TheJulia> The following week I may also be busy, unsure yet
15:11:48 <yolanda> i see that on log:  Entering new state 'cleaning' in response to event 'provide' on_enter /usr/lib/python3.6/site-packages/ironic/common/states.py:300ESC[00m
15:11:50 <TheJulia> Anyway!
15:11:52 <TheJulia> #link https://etherpad.openstack.org/p/IronicWhiteBoard
15:12:01 <TheJulia> Starting at line 160
15:12:06 <TheJulia> err
15:12:09 <dtantsur> yolanda: it always walks the state machine, I think. even if cleaning is no-op.
15:12:12 <TheJulia> no, starting at 281
15:14:19 <TheJulia> I'm really worried about the deploy steps stuff landing super late int he cycle
15:14:47 <TheJulia> I think it would be good if we could get some folks to at least perform a review of the PoC patches?
15:14:48 <TheJulia> thoughts?
15:14:54 <TheJulia> I'm sure mgoddard would be happy
15:14:57 <dtantsur> I should have done it long ago
15:15:03 * dtantsur is sorry
15:15:25 <TheJulia> c'est la vie
15:15:48 * TheJulia needs to work on her very minimal french
15:16:10 <TheJulia> wsme/flask/etc, does anyone have an update?
15:16:36 <jerrywang1> no update at my side, no one review my code change yet
15:16:42 <jerrywang1> for wsme
15:16:59 <TheJulia> 675853?
15:17:03 <jerrywang1> yes
15:17:15 <rloo> didn't we talk about wsme last week? I forgot how it ended...
15:17:20 <rpittau> TheJulia: for Flask, there was not a mutual understanding that we were going that direction btw
15:17:30 <jerrywang1> My change was for json schema
15:17:32 <TheJulia> oh, okay, I was hopful there
15:17:33 <dtantsur> wasn't there? I think it has been decided many times
15:17:34 <rpittau> or what the exact plan is
15:17:39 <jerrywang1> Last week was others
15:17:51 * TheJulia feels like she has opened a "can of worms"
15:17:58 <dtantsur> worms, yummy!
15:18:01 <TheJulia> lol
15:18:05 <rpittau> dtantsur: yeah, but I remember the last discussion where the execution was not clear for someone
15:18:10 <rpittau> gummy worms ?
15:18:25 <dtantsur> well, one thing is clear: we need to get off wsme
15:18:49 <dtantsur> pecan is painful to use, but we can probably stay on it
15:18:54 <TheJulia> It feels like we explicitly need to have an explicit plan gotten together since we've let it be nebulous to try and encourage progress as opposed to try design it forever
15:18:58 * dtantsur assumes pecan is not dead
15:19:04 <TheJulia> Umm...
15:19:08 * TheJulia gets a parrot out
15:19:23 <TheJulia> Or would Doctor Mccoy work?
15:19:24 <dtantsur> last commit in August: https://github.com/pecan/pecan
15:19:38 * dtantsur as usual misses the references :)
15:19:42 <TheJulia> Well that is good
15:19:53 <TheJulia> dtantsur: go watch the original star trek and look for "its dead jim"
15:20:00 <rpittau> oh gosh :D
15:20:01 <TheJulia> anyway we're off topic
15:20:17 * dtantsur won't admit he hasn't watched star trek for $insert_silly_reasons
15:20:18 <rpittau> do we want to get that to the mid-cycle instead ?
15:20:36 <dtantsur> rpittau: the schedule is packed and we won't have a quorum anyway
15:20:37 <TheJulia> DHCP-less has had good discussions, I feel like we just need to focus it a little bit more and everyone will be happy
15:20:43 <rpittau> mmmm right
15:20:44 <dtantsur> ++
15:21:05 * etingof is focusing on that
15:21:12 <TheJulia> Looks like uefi software raid is starting to get some review traction
15:21:16 <TheJulia> and activity which is awesome
15:21:42 <TheJulia> Node retirement is done, at least in ironic. I wonder if there is anything besides openstacksdk?
15:21:48 <TheJulia> or do we consider that out of scope?
15:22:03 <TheJulia> Well, I take that bcak
15:22:08 <TheJulia> the osc commands have not merged https://review.opendev.org/#/c/703982
15:22:09 <patchbot> patch 703982 - python-ironicclient - Add support for retired{_reason} fields. (MERGED) - 5 patch sets
15:22:22 <dtantsur> I've been slowly poking people towards starting to take openstacksdk in scope
15:22:32 <dtantsur> note that, being an SDK core, I'm clearly biased
15:23:01 * TheJulia adds the OSC patch to the retirement support list under priorities since the other two have merged
15:23:26 <rloo> i had some questions about the client part of the retired * stuff (but i commented in the PR, after it merged though.)
15:23:48 <rloo> i thnk we should add that all the ironic API stuff ought to be avail in the openstacksdk.
15:24:04 <dtantsur> rloo: I'll respond to your comments
15:24:07 <TheJulia> That kind of seems I concur, it seems reasonable to me, as long as we're able to time/committment wise
15:24:19 <TheJulia> Anyway, I think we're good to move on?
15:24:28 <rloo> (wonder if we should update our spec template to mention that, if it hasn't been updated already)
15:24:32 <rloo> thx dtantsur
15:24:39 <TheJulia> rloo: good point
15:24:45 <TheJulia> afaik, it has not been updated
15:24:54 <rloo> TheJulia: i'll offer to do that :D
15:25:00 <TheJulia> rloo: thanks!
15:25:24 <TheJulia> Moving on!
15:25:43 <TheJulia> #topic Deciding on priorities for the coming week!
15:25:53 <TheJulia> #link https://etherpad.openstack.org/p/IronicWhiteBoard
15:26:03 <TheJulia> Starting at 160
15:26:04 <dtantsur> rloo: tl;dr what we did with maintenance was bad and I feel bad for not preventing it :(
15:26:20 * TheJulia starts by removing merged things which is a number of things
15:26:26 <rloo> dtantsur: OH. (talk later)
15:26:48 <dtantsur> I can offer anyone a good rant with my API SIG hat on :)
15:27:08 <TheJulia> Any objection to removing the reconfiguration spec from the list of things to review?
15:27:14 <dtantsur> not from me
15:27:36 <openstackgerrit> Ilya Etingof proposed openstack/sushy master: Fix 'None' field value processing  https://review.opendev.org/703652
15:28:45 <rloo> +1 on removing reconfiguration spec from list
15:28:54 <TheJulia> iurygregory: looks like you've got a few things you need reviewed :)
15:29:09 <iurygregory> TheJulia, yeah XD
15:29:26 <openstackgerrit> Ilya Etingof proposed openstack/sushy master: Relax required Redfish fields handling  https://review.opendev.org/703825
15:29:27 * iurygregory finally got redfish CI job working =D
15:29:47 <dtantsur> TheJulia: I've checked the agent_token stuff as promised. It seems to need another rebase :(
15:29:52 * iurygregory the i-p-e =)
15:29:57 <TheJulia> tzumainn: any node ownership stuff needed?
15:30:05 <rloo> are we preparing to do some releases? I see some PRs related to that. if so, should they go in this week's list?
15:30:07 <TheJulia> dtantsur: I'll rebase it either during the next meeting or after
15:30:23 <TheJulia> rloo: already on the list
15:30:30 <dtantsur> I'll need review on https://review.opendev.org/#/c/706863/ once I'm done testing it. It's quite serious, the DIB-IPA jobs don't test IPA.
15:30:31 <patchbot> patch 706863 - ironic - Actually use ironic-python-agent from source in so... - 1 patch set
15:30:45 <TheJulia> in the wrong place of course
15:30:47 * TheJulia shuffles the list
15:31:00 <rloo> TheJulia: ah, that explains it, cuz I stared a bit more and didn't see !
15:31:01 <rpittau> dtantsur: I'll add it to my list
15:31:05 <dtantsur> thx
15:31:11 <tzumainn> TheJulia, hi! just the lessee implementation patch
15:31:36 <TheJulia> tzumainn: do you have the link handy
15:31:47 <tzumainn> ah, yep! one sec
15:32:03 <tzumainn> https://review.opendev.org/#/c/706864/
15:32:03 <patchbot> patch 706864 - ironic - Add node lessee field - 1 patch set
15:32:09 <TheJulia> I think the list is good
15:32:12 <tzumainn> I also put it on the whiteboard somewhere, maybe in the wrong place
15:32:55 <TheJulia> The ipa bugs I found this week seem to relate to our standalone test failure rate, I'll try and get that patch fixed and then some of the approved stuff may have more luck getting past the raid tests
15:33:44 <TheJulia> Does anyone have anything to add to the list?
15:33:54 <kaifeng> https://review.opendev.org/706445 can use some reviews
15:33:55 <patchbot> patch 706445 - ironic - Automatic port allocation for the serial console - 2 patch sets
15:34:04 <TheJulia> kaifeng: already added  :)
15:34:10 <TheJulia> Thanks for that by the way!
15:34:17 <kaifeng> TheJulia: thanks :D
15:34:45 * TheJulia takes silence as agreement with the list and to proceed
15:35:02 <dtantsur> ++
15:35:07 <TheJulia> #topic Discussion
15:35:09 <TheJulia> We have three topics
15:35:18 <TheJulia> (Which is why I'm trying to move us through the meeting quickly)
15:35:32 <TheJulia> Topic #1, do we cancel the IRC meeting the week of the midcycle?
15:35:52 <dtantsur> at least the two of us will be travelling, right?
15:35:53 <rpittau> that's probably a good idea
15:35:55 <rloo> yes
15:36:18 <TheJulia> I think my train arrives in geneva around 4 PM local, so i may still be on the move to the hotel
15:36:34 <rpittau> we might be on the same train :)
15:36:54 <TheJulia> Any objections to canceling?
15:37:12 * TheJulia gives a chance for objections before moving along
15:38:08 <TheJulia> rpittau: Gare de Lyon departure?
15:38:11 <rpittau> yeah
15:38:17 <TheJulia> very likely then!
15:38:19 * dtantsur flies in
15:38:22 <iurygregory> ++ to cancel =)
15:38:23 <TheJulia> Okay, moving on!
15:38:41 * iurygregory arrives at 5PM
15:38:45 <TheJulia> #2, PTG in Vancouver? Is anyone interested in attending?
15:38:52 * rpittau very
15:38:58 <rpittau> (maple syrup)
15:39:00 <TheJulia> They are polling for project space and I likely need to respond (soon)
15:39:12 <TheJulia> heh
15:39:21 <dtantsur> I'm interested, not sure about budget and visa stuff
15:39:30 <TheJulia> That is fair
15:39:35 <rpittau> same for the budget :/
15:40:01 <TheJulia> I planned for ~12 people to appear in Shanghai and 15 joined us, so I'm thinking slightly more seats
15:40:15 <rpioso> Interested. It will likely depend on travel budget.
15:40:16 <dtantsur> yeah, a much higher NA presence
15:40:45 <TheJulia> Yeah
15:40:51 <TheJulia> Okay, I'll respond to the foundation
15:41:28 <TheJulia> Topic #3! That ye olde bug about users being able to orphan vifs in neutron that prevent the node from being deployed/reused/etc due to duplicate mac addresses
15:41:42 <TheJulia> #link https://review.opendev.org/665835
15:41:42 <patchbot> patch 665835 - ironic - Block port deletions where vif is present - 8 patch sets
15:42:43 <mgoddard> \o
15:42:47 <mgoddard> sorry, been in an intervie
15:43:00 <TheJulia> Does anyone actually care about this bug? Because there has been some back and forth on requirements and the intent was to guard against humans doing silly things and as a result perceptions have differed and it has been slightly frustrating
15:43:53 <TheJulia> If at least one person cares, I'll try and clarify things further and see if I can make reviewers happy and operators have suffient guards/information
15:43:54 * rpioso wishes mgoddard good luck ;-)
15:44:16 <kaifeng> TheJulia: do you aware the reasons why the vif is not removed?
15:44:17 <mgoddard> rpioso: luck would be better directed at the candidate :)
15:44:24 <TheJulia> I suspect that guarding deletions becomes more important with multitenant access
15:44:42 <TheJulia> kaifeng: node put in maintenance state and ports and or the node itself removed.
15:44:54 <rloo> it seems like a valid bug and i think we ought to address it.
15:45:41 <TheJulia> upon removal, if there is any sort of vif, even an internal vif for ironic, that port is orphaned in neutron
15:46:11 <TheJulia> s/that port/ the neutron vif/port/
15:46:40 <TheJulia> I think we found it downstream when someone decided that they were just going to delete everything due to being frustrated and then couldn't ever deploy again
15:47:04 <TheJulia> Anyway, I'll go ahead and carry it forward
15:47:21 <rloo> based on my last comment, I think I'm good with the idea. Just that, if I recall, this adds a new method to our NetworkInterface API, so I wanted that to be somewhat 'solid'.
15:48:02 <TheJulia> solid as in we're not going to change its behavior after adding?
15:48:16 <TheJulia> I suspect if I just rename the method people might become happy
15:48:19 <TheJulia> truthfully
15:48:29 <rloo> i wasn't thinking that but solid wrt description etc so if someone subclasses with their own network, they know what that method should do
15:49:05 <TheJulia> Regarding moving on, It doesn't look like we have anything to visit for the Bare Metal SIG or RFEs, so I'll move us to Open Discussion.
15:49:11 <rloo> ie, what does 'get_current_vif_with_tag()' mean/do? Not that clear to me. I'm fine if that is clear to others.
15:49:33 <TheJulia> hmm
15:49:47 <rloo> (it is possibly more than one vif)
15:49:49 <kaifeng> TheJulia: i am thinking in cases ironic failed to remove vif from neutron, it seems we have no other ways to remove it from ironic governance
15:49:56 <TheJulia> rloo: thank you, I think I understand your feedback now.
15:50:06 <rloo> TheJulia: :) Sorry if it wasn't clear.
15:50:20 <TheJulia> rloo:  you likely were and I just didn't read it right
15:50:34 <rloo> TheJulia: no worries, glad you asked! :)
15:51:27 <TheJulia> kaifeng: Yeah, if someone short circuits processes.. .we can search by mac and possibly replace ports but unique macs may not always be... unique.
15:51:34 <TheJulia> #topic Open Discussion
15:51:43 * TheJulia feels trying to auto-resolve things may be better eventually
15:51:55 <TheJulia> with a giant "this may do undesirable things" warning
15:52:14 <dtantsur> a periodic task to clean up orphaned VIFs? :)
15:52:15 <TheJulia> Anyone have anything to discuss today?
15:52:27 <tzumainn> hi! quick question - has anyone ever tried non-admin deployments upon a node using standalone Ironic? I tried it for a bit and ran into the issue of having to create Neutron ports, which required admin API access
15:52:48 <dtantsur> ehmmm, creating ports shouldn't require admin
15:52:52 <TheJulia> dtantsur: reconciling our ports versus neutron's ports seems like it could be... slightly complex.
15:53:04 <dtantsur> TheJulia: since when are we afraid of complexity? :D
15:53:22 <tzumainn> I think the part that required admin was associating a neutron port with a mac address
15:53:29 <dtantsur> oh wow
15:53:32 <TheJulia> dtantsur: I'm more worried about interaction latency, we've seen how data syncs with neutron can be painful
15:53:46 <TheJulia> yes, adding a mac is an admin action
15:53:49 <kaifeng> maybe it's not a shared network
15:53:51 <dtantsur> ouch
15:54:10 <rpioso> Are folks open to adding the driver for the Intel I350 NIC to the Tiny Core IPA ramdisk?
15:54:11 <TheJulia> It always has been... We likely need to revisit our neutron code then
15:54:37 <dtantsur> rpioso: only if it doesn't change the resulting size substantially IMO
15:54:49 <rpittau> rpioso: how big is that ?
15:54:54 <TheJulia> rpioso: I am not since it is for VM testing and  and I looked for other drivers and it doesn't seem to really have much of a selection for network drivers
15:54:57 <dtantsur> TheJulia, tzumainn, then we may need to use an admin token for this particular operation
15:55:20 <TheJulia> dtantsur: indeed, I think we did originally but session code changes likely caused us to change it to re-using the nova request token
15:55:21 <dtantsur> yeah, essentially what TheJulia said. we need to invest into DIB images as our hardware solution.
15:55:48 <dtantsur> tzumainn: okay, so it's probably a bug. let's start with collecting the details and filing it.
15:55:57 <TheJulia> dtantsur: ++ on both items
15:56:05 <tzumainn> dtantsur, okay, can I ask you a few more questions post-meeting?
15:56:06 <rpioso> TheJulia: It has the driver for Intel X710 10/40 Gbps NIC. The I350 is a 1 Gbps port.
15:56:10 <dtantsur> tzumainn: sure thing
15:56:47 <rpioso> TheJulia: Dell EMC's lab equipment has an I350 connected to the provisioning network.
15:57:06 <dtantsur> rpioso: do you envision any problems with using DIB images?
15:57:10 <TheJulia> rpioso: I'm afraid the drivers just don't exist for tinycore as far as I've seen
15:57:40 <iurygregory> TheJulia, I'm wondering if the fixes in ironic-prometheus-exporter would be ok to backport to stable/train =)
15:57:42 <TheJulia> 3 minute warning
15:57:43 <dtantsur> by the way, TinyCore 11 is out :)
15:57:51 <TheJulia> dtantsur: ohhh
15:57:56 <TheJulia> iurygregory: should be fine
15:57:59 <dtantsur> iurygregory: "fixed" usually are
15:58:09 <rpioso> dtantsur: I have had probs using it and RDO's IPA ramdisk to Redfish vmedia boot with the UEFI / local / partition image workflow.
15:58:34 <rpioso> dtantsur: tinyipa appears to be close to working.
15:58:39 <iurygregory> dtantsur, also the redfish job (not a fix but a real testing job) XD
15:59:00 <rpioso> dtantsur: For at least RDO's IPA ramdisk, the kernel crashes.
15:59:17 <dtantsur> rpioso: well, it should be fixed. that's what the customers will be using.
15:59:30 <TheJulia> iurygregory: if it fixes issues or makes operational use better/more reasonable on that branch, It should be fine when it comes to releasing it
15:59:34 <dtantsur> iurygregory: any CI changes can be backported with a reasonable motivation.
15:59:43 <dtantsur> the policies only affect the actual code we ship
15:59:48 <iurygregory> awesome =)
16:00:02 <rpioso> dtantsur: We hope to explore that at Geneva. Meanwhile, it would be helpful to have something we can inform operators works.
16:00:30 <rpioso> dtantsur: So far, nothing has worked for UEFI / local / partition image.
16:00:36 <dtantsur> we, as ironic upstream, don't really support using tinyIPA in production
16:00:38 <TheJulia> The policies are also slightly flexible when operators are kept in mind and we can do appropriate versioning
16:01:02 <dtantsur> rpioso: we have been doing this for a while in TripleO..
16:01:02 <rpioso> dtantsur: Which do we support?
16:01:10 <dtantsur> DIB images are now official for production
16:01:16 <rpioso> dtantsur: Who is "we"?
16:01:27 <dtantsur> rpioso: "in TripleO" so ~ Red Hat
16:01:33 <TheJulia> dtantsur: what rpioso indicated is that his grub, which coems from his ubuntu devstack host is spitting out an error about the ramdisk being too being, apparently before crashing. I suspect the ramdisk is getting truncated on his machine and I bet the kernel crashes.
16:01:39 <TheJulia> We're at time, Thanks everyone!
16:01:46 <rpioso> dtantsur: With Redfish vmedia boot?
16:02:02 <dtantsur> rpioso: that's the bit you didn't mention :) worth asking yolanda
16:02:05 <rloo> thx TheJulia!
16:02:16 <TheJulia> #endmeeting