08:00:28 #startmeeting multi_arch 08:00:30 Meeting started Tue Jan 21 08:00:28 2020 UTC and is due to finish in 60 minutes. The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:36 The meeting name has been set to 'multi_arch' 08:00:38 #topic roll call 08:00:42 o/ 08:00:43 o/ 08:00:48 ianw, o/ 08:02:02 tonyb, is traveling in Europe, so I assume will join our 2nd meeting today 08:02:15 o/ 08:02:23 hi mrda :) 08:02:26 hey! 08:02:55 #topic adding items to agenda 08:03:00 #link https://etherpad.openstack.org/p/Multi-Arch-agenda 08:04:01 what's your current multi-arch WIP task mrda ianw?:) 08:04:21 so just today i got credentials for the linaro US cloud 08:04:42 #link https://review.opendev.org/#/c/703535/ 08:05:02 when we get this up, we'll have 08:05:27 another 8 nodes at least 08:06:10 and I'm just got access to a power9 box which I'm planning on doing some testing on (up until now I've just been using a power 8 box). 08:06:18 ianw, is that the same group of node Kevin Zhao mentioned last time? 08:06:44 (with ~400vcpu) 08:07:32 ricolin: yes, i think he said 8*44 == 352 vcpu 08:07:32 mrda, stress test?:) 08:07:45 ianw: very cool 08:07:48 ianw, that's awesome! 08:08:21 well all thanks to linaro and kevinz :) 08:08:44 ricolin: just looking at some tripleo undercloud introspection and trait-based deployment. 08:09:03 i know the networking is ipv6 only, that shouldn't be a problem but it is new territory for the arm64 clouds, so may be issues lurking 08:09:08 ...making sure it works as expected on both power8 and 9 08:09:39 ianw, is that means only ipv6 for devstack too? 08:10:12 huh, v6 only networking. At what layer is that implemented? 08:10:27 mrda, that sounds like a looooot~ of works! 08:10:47 ricolin: we haven't got devstack working on arm64, yet. but i'd say the nodes can communicate between themselves via ipv4 (for multinode jobs), just no routed public ip 08:10:53 ipv4 i mean 08:11:23 we have several other clouds like this too 08:11:32 ianw: thanks for clarifying. v6-only should just work :) 08:12:54 #topic Follow on Repo and StoryBoard setup 08:13:06 Our Repo is there, but I haven't add the doc and zuul structure yet. Will do it this week. 08:13:07 #link https://opendev.org/openstack/multi-arch-sig 08:13:25 According to the plan we got from last meeting, documents will first to put in. I think that can started now, and send out once the repo structure is ready. 08:13:54 #action ricolin add doc and zuul structure to https://opendev.org/openstack/multi-arch-sig 08:14:24 Since we have our own repo, we have core reviewer list 08:14:28 #link https://review.opendev.org/#/admin/groups/2079,members 08:14:43 And I would like to suggest we add volunteers as core reviewers. 08:14:57 ianw, mrda interested?:) 08:15:02 Sure 08:15:23 yes, i can subscribe to the repos and watch for things i might know something about :) 08:16:16 super! 08:16:45 I will add both of you in that list later:) 08:17:19 ianw, How about SIG chair role?:) 08:17:27 thanks ricolin, you're pretty organised :) 08:18:19 sorry I just got time to join 08:18:24 ianw: my pleasure 08:18:29 mrda, thx, try to be:) 08:18:39 kevinz, o/ 08:18:48 umm, i dunno about a chair, probably be better to go to someone who travels to things a bit more 08:18:49 kevinz, thanks for the effort!:) 08:19:26 :D 08:20:38 ianw, NP, we know have tonyb and I volunteered, and we still got room for one more IMO, so feel free to let me know if you would like to take it:) 08:20:44 *now 08:21:05 next 08:21:12 Our StoryBoard is created 08:21:18 #link https://storyboard.openstack.org/#!/project/openstack/multi-arch-sig 08:21:46 We should start added task into it. So if all members can put in their current work in progress task in this story will make others easier to track. 08:22:12 We already have some collected WIP patch recorded in https://etherpad.openstack.org/p/Multi-arch which I think will make sense to move to StoryBoard too. 08:22:29 ianw, kevinz mrda thoughts? 08:23:10 sounds good, i can do that for what i get up to 08:23:17 yup, works for me 08:23:35 i guess if we have bigger tasks, split that out into separate stories? 08:24:01 yeah, I think so 08:24:54 for some small one, can created under a story with general title 08:25:25 #action Everyone please help to put on tasks in Storyboard https://storyboard.openstack.org/#!/project/openstack/multi-arch-sig 08:26:31 The most need to track tasks IMO are tasks that already generated patches 08:27:41 let's start with our storyboard and record all future tasks on it:) 08:28:41 Also we can use storyboard to link and assign tasks to another project team (if they also use storyboard too) 08:28:48 ++ 08:29:00 pretty handy:) 08:29:05 +1 08:29:25 I also create a irc channel #openstack-multi-arch mostly because we need a place to record gerrit update also will be nice if people all join that irc and easier to find each other. So please join:) 08:29:55 #action Everyone please join IRC channel #openstack-multi-arch :) 08:30:09 Done 08:30:20 mrda, fast! 08:31:01 I think that's all I got from SIG infra set up 08:31:02 * mrda notes he might otherwise forget 08:31:47 #topic Follow on CI Resources 08:32:21 For what I know mnaser mentioned that there might be some ARM resource Vexxhost can donate to community. 08:32:33 Also Huawei mentioned that they can donate ARM resources too. 08:32:58 I will keep tracking with them and see if anything scheduled. 08:33:44 Also ianw and kevinz already give us even better news already:) 08:34:24 so soon, two group of nodes 08:35:53 it's great to have multiple sources of nodes 08:35:54 * ricolin thinking crazy CI job ideas 08:37:39 mrda, yeah, that help us to avoid single group of resource failing issue. Also since ARM performance is totally different between providers, we can even help to testing the general performance:) 08:38:22 ianw, when you mentioned about devstack is not working with arm64, you mean devstack itself? or other component? 08:38:29 yeah, great idea... 08:39:31 ricolin: i haven't tried, would be things like package installs etc that would need to be sorted out 08:41:10 ianw, we can put on a patch and test that out:) 08:41:53 * mrda is going to have to drop off. 08:41:55 certainly, it can all be speculatively done with a new job using arm64 nodes 08:41:57 Thanks everyone. 08:42:04 mrda, thanks for join:) 08:42:51 ianw, we can put those job definition in SIG repo if we plan to use it officially 08:43:41 like a general devstack-arm64 job 08:44:36 yes, i'll try to find some time at least get a job definition up, so if someone who maybe isn't so familiar with zuul configs wants to really run with it they have a head start 08:45:02 sounds great! 08:45:26 ianw, can I put that on as an action? 08:45:37 ok, sure :) 08:46:00 #action ianw help to provide arm base job definition for devstack 08:46:06 super!:) 08:46:56 ianw, kevinz anything you would like to add in CI topic? 08:48:08 Okay, move on:) 08:48:13 #topic Follow on documentation 08:49:02 jeremyfreudberg has take the action to working on docs, but didn't sync that with him yet 08:49:34 * ricolin knows that 2nd meeting is the right time for jeremyfreudberg:) 08:49:52 So I don't have much to update here 08:50:52 I guess that's all from me 08:51:35 Anything you would like to covered in this meeting? 08:51:43 ianw, kevinz 08:51:56 no 08:52:09 thanks for all your work ricolin driving this along 08:52:10 that's all from my side :) 08:52:23 Thanks ianw ricolin 08:52:30 If we can have the doc, storyboard tasks, zuul job out, will be a big success of this SIG:) 08:52:54 ianw, kevinz Anytime!:) 08:53:18 I think we can end this meeting now:) 08:53:39 thanks everyone!:) 08:53:54 see you on storyboard!:) 08:54:03 ...and irc:) 08:54:05 #endmeeting