21:02:01 #startmeeting scientific-wg 21:02:02 Meeting started Tue May 31 21:02:01 2016 UTC and is due to finish in 60 minutes. The chair is b1airo. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:02:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:02:07 The meeting name has been set to 'scientific_wg' 21:02:11 #chair oneswig 21:02:12 Current chairs: b1airo oneswig 21:02:20 Thank you sir! 21:02:21 morning 21:02:23 evening 21:02:27 :-) 21:02:31 hi 21:02:44 hi leong 21:02:47 Hi Leong 21:03:05 hi LyleWinton 21:03:16 hey Blair 21:03:37 Hi Lyle 21:03:59 Stig? 21:04:03 The same! 21:04:10 Hi! 21:05:38 ok, let's get into it then 21:06:00 quick roll call... 21:06:07 here 21:06:09 o/ 21:06:22 here 21:06:28 here 21:06:35 (if for nothing more than to get the meetbot stats up ;-) ) 21:06:51 +1 :-) 21:06:54 an important stat 21:07:17 leong, craigs - would you please remind me of your names so I can try to recall? 21:07:42 leong from Intel 21:07:42 Craig Sterrett 21:07:47 from Intel 21:07:51 Yih Leong Sun :) 21:08:00 actually i should probably check irc before asking (sorry) ... 21:08:27 thanks! 21:09:07 #topic User Stories 21:09:14 do we have an agenda? 21:09:24 We do, bear with me... 21:09:28 might we link to the agenda if we have one? 21:09:32 yes: #link https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_May_31st_2016 21:09:32 oneswig: thanks 21:09:39 wonderful thank you 21:09:43 Got there first b1airo! 21:10:07 had it open 21:10:16 :) 21:10:25 OK, first item under user stories was the idea of creating a whitepaper describing the current position on OpenStack and HPC 21:11:09 o/ 21:11:19 There is interest in creating this in a similar form to the previous papers on OpenStack and containers (for example) 21:11:27 yes, so perhaps you can remind us of the approach you're talking with the cambridge paper oneswig ? 21:11:54 * b1airo admits he hasn't read one of those papers 21:12:03 OK, so the background is I have a contract with Cambridge Uni to deliver a very similar study for informing their purposes 21:12:31 cool 21:12:44 and by the way, still happy to contribute to that if we can do so usefully 21:12:49 And the plan is to extend that paper with further contribution, reshape it and improve it and then work with th eFoundation to shape it to their needs 21:13:09 b1airo: thanks, looking forward to that, will be in touch... 21:13:17 what needs does the foundation have here? 21:13:34 the user stories are for the scientific working group's consumption I had thought 21:13:36 glossary brochures by the sound of it :-) 21:13:37 oneswig can you share the whitepaper/sutdy with cambridge? 21:13:47 b1airo: can't have too many of those 21:14:04 anteaya: I'd say it's for anyone but the Scientific WG members 21:14:13 In the sense that that would be preaching to the choir 21:14:31 It's aim I think is to be outreach for organisations that could be considering this option 21:14:32 oneswig: oh I mis-understood then 21:14:38 agree with oneswig 21:14:46 but you make a good point anteaya - the User Stories we want to define should be from the user base of the scientific-wg 21:14:50 I think it will be great to produce a whitepaper talking about how OpenStack can support the HPC use case 21:15:16 Was the most frequent question after the scientific clouds panel in Austin, HPC and OS. 21:15:20 b1airo: yes that was what I had thought I heard from the beginning 21:15:30 yeah, there's a big gap there - we should simply create a wiki.o.o/HPC in the mean time 21:15:43 LyleWinton: what was the most frequent question? 21:16:08 "Can I do HPC with/on OS?" 21:16:14 anteaya: questions regarding HPC and OS. 21:16:31 LyleWinton: right 21:16:47 yes, that was what I had thought 21:16:56 I just wonder where the foundation needs got in there? 21:16:57 The interesting item to discuss for this WG is what members of this group might be able to contribute as material that exemplifies how OpenStack can be configured to deliver HPC 21:17:16 to which the answer is "yes, for some definitions of HPC and OS" 21:17:49 b1airo: Right, but lets say the document sticks some stakes in the ground (helping to skirt that tar pit!) 21:18:05 b1airo: awesome and the user stories provide the definitions and examples, yeah? 21:18:41 anteaya, i guess that would be ideal - but we need to define those... 21:19:10 okay thanks 21:19:18 I'm intending to produce with Cambridge a document that describes in some technical depth how a series of capabilities are delivered on OpenStack and introduce case studies and input from project leaders to reinforce 21:19:47 oneswig: can that be open sourced and considered a user story? 21:19:54 oneswig, by project leaders i guess you mean science projects that use the infrastructure 21:20:16 yes and yes, that's what I menat :-) 21:20:26 oneswig: awesome! 21:20:37 I think that will make a great user story 21:20:59 and help drive the conversation in this space when you lead by example 21:21:08 There would be a varying degree of reworking by the Foundation to make it into a freestanding whitepaper - or perhaps a set of connected chapters 21:21:13 I have a slide (as of last night) on clusters/HPC cases in the NeCTAR research cloud. 11 specific cases I could follow up in more detail if needed. 21:21:34 oneswig: 'reworking by the Foundation' what do you mean? 21:21:38 LyleWinton: that's exactly the kind of material that would be help 21:22:06 b1airo happens to be one of them ;) 21:22:16 anteaya: I don't think anything i can produce matches the technical material the Foundation can produce, it'll need some polishing without doubt 21:22:24 oneswig: as long as you have a licence on it that is one of our accepted open source licences it should be good 21:22:33 ASL2? 21:23:02 oneswig: ah let's not put the cart before the horse, I think if you open source what you produce for cambridge we can address any issues that arise 21:23:13 let's not create obstacles before you begin 21:23:20 Every deliverable for this project is open source - terms of the contract 21:23:31 oneswig: awesome, makes it easy then 21:24:11 so should we have a 5 minute brainstorm on what some of our User Stories might be? 21:24:22 Good idea 21:25:17 Other user stories do you mean b1airo: 21:25:40 One user story that is endless in its variation is cluster-as-a-service. Is it possible to capture that in some constructive way and compare the ways? 21:25:46 #idea I want to give users an easy on-demand HPC platform 21:26:11 jinx oneswig 21:26:42 or perhaps from the user's perspective (i always think architect/operator) ? 21:27:25 oneswig: we have a number of operators re-using patterns (orchestration scripts) created by other operators for building clusters, and several are in production use. 21:28:53 what is your definition of cluster? 21:28:53 LyleWinton: that's useful information. And another way of doing it too. Vive la difference 21:28:56 is a cloud a cluster? 21:28:56 #idea I want to run my (persistent) HPC platform/service using OpenStack as the infrastructure provisioning system 21:29:10 anteaya: typically I'd say in scientific compute people would think of a workload manager queue system - typically SLURM 21:29:20 thanks 21:29:36 anteaya: these are mostly HPC like clusters, slurm or torque front ended. 21:29:52 anteaya, yes probably, but i think we're usually talking about HPCC (high performance cluster computing) when we say clusters - which means batch system and/or low-latency interconnect 21:30:38 good to see we all agree on that :-) 21:30:39 anteaya: but some of the users say "they aren't HPC" because they use general purpose cloud infrastructure. never stopped most researchers using the definition in the past, but it's a distinction 21:30:45 There's an open-ended discussion on how to count the ways, should we go onto idea 2? 21:30:58 please 21:31:04 thank you 21:31:21 Perhaps in addition to this ideas for the use cases you would like to have, would be to approach contacts from around the community and ask them to put forward use cases? See what arises from requesting use cases be put forward from well known scientific users like CERN, NASA, NSA, Cambridge, etc. 21:32:08 dfflanders: that's a good point 21:32:34 dfflanders, definitely - but part of the problem i think we want to get towards solving today is figuring out a few examples to set the scene, else it's very open ended 21:32:44 +1 21:33:01 so i said: "I want to run my (persistent) HPC platform/service using OpenStack as the infrastructure provisioning system" as a possible #2. thoughts? 21:33:15 b1airo: how does OpenStack as an infrastructure provisioning system (idea 2) differ? 21:33:21 going to the users with some exemplars you'd like to achieve is a good approach imho. 21:33:38 Is this "I submit a job to SLURM, SLURM uses OpenStack to create infrastructure to run the job"? 21:33:43 that's distinct from HPC-aaS because the end-user does not necessarily see cloud anywhere 21:34:25 oneswig, it could be that dynamic yes, or just that all the compute nodes managed by SLURM are running on an OS cloud 21:34:51 with operator controlled expansion/contraction 21:35:13 Could I offer a perspective on how this might look to the world. scientific openstack = HPC ! Should we seek a different user story to HPC. 21:35:36 and also typically a managed system, whereas HPC-aaS is usually fire and forget 21:36:06 LyleWinton, for sure - getting there :-) 21:36:14 dhellmann i'll pick up the tag reviews this week 21:36:15 you have #3 21:36:15 K 21:36:35 dhellmann apologies on lag, been super busy dealing with backlog 21:36:39 which keeps getting longer and longer 21:36:41 oneswig, make sense? 21:36:41 going wrong direction :( 21:36:54 sdake_, there's a meeting on in here :-) 21:37:26 sdake: could you be in the wrong channel? Maybe you want openstack-release? 21:37:37 I'm thinking ... what a nice way of hiding the details of a cloud-centric implementation 21:38:14 i think #2 is where HPFS is likely to come in too 21:38:18 A discussion for a user story would be interesting and I'd be interested to see how it might hide the overhead of OpenStack infrastrcutre creation 21:39:30 So, in some ways, what I'm reading is that you folks are identifying "work loads" or "work flows" which the scientific community uses and you need to define what they look like on OS 21:39:31 HPFS could cut across many use cases, lets not box it in 21:40:04 that's true, but is that a use case on its own ? 21:40:20 rockyg: I think so, there's an amount of transposition between the interactive and flexible world of cloud versus the fast-but-inflexible world that HPC has lived in thus far 21:40:22 or does it just fit into various others ? 21:41:08 b1airo: perhaps discussion HPFS impelmentation strategies falls better as reference architecture than user story, could this be a distinction? 21:41:57 then another good set of user stories is how OS allows a team/multi-team to move from one format to another or live side by side on the same cloud.... 21:42:00 One of our use cases is a bit hybrid if you like. Automated Galaxy portal creation back-ended by clusterman HPC creation. 21:42:23 rockyg, +1 21:42:51 rockyg +1 21:43:11 oneswig, yes that sounds eminently sensible 21:43:50 rockyg: we may have stories where OS allows separate research project to live side by side, which is of significant research value 21:44:25 LyleWinton, I think that's a great exemplar of #1 ? 21:44:35 oneswig, ++ so identify architectures, identify workloads, the boundaries of each and how to morph across them? 21:44:41 Galaxy I mean 21:45:11 Ah, yes, you're right 21:45:44 LyleWinton: The Galaxy project is a good example of how cloud can be used to deliver something better than matching the functionality of what came before. I'd put it above cluster-as-a-service 21:46:03 b1airo: Oh, yes, it was one of the 11 that I was speaking of 21:46:21 So we might be slowly getting somewhere here :-) - sounds like we want use-cases with exemplars and reference architectures for specific capabilities ...? 21:47:05 oneswig: me too, but it's a cluster related pattern. One with a newer front end than slurm 21:47:13 blairo, ++ might be easier to start with exemplars and fit the defining bits around them 21:47:58 rockyg, sure, either way is fine with me 21:48:20 sounds like it would be up to the person who wants to write them 21:48:25 Pick a set of projects, then figure out the buckets that are the same and the ones that are different. Build the matrix, then reason about the info displayed 21:48:45 so just quickly, before we spend the last 10 minutes on this did anyone want to move on to other specific topics? i think this is a valuable discussion and happy to keep it going... 21:48:55 I think that would depend on who is volunteering to do the work, so far it is oneswig 21:49:21 so I'd say whatever he is most comfortable with 21:49:29 we are more than open to having volunteers! 21:49:30 I am definitely interested in hearing about volunteers to discuss areas of subject expertise! 21:49:30 anteaya, ++ 21:49:38 b1airo: oh yes 21:50:21 I have your powerpoint in my sights Lyle :-) 21:50:43 On my todo list to send you! 21:50:57 LyleWinton: thanks, appreciated 21:51:21 b1airo: last ten minutes. 21:51:31 Anything to report from last week 21:51:57 yeah let's move on then 21:52:28 #action Send summary of use-cases discussion to lists and seek input 21:52:50 so i have a skeleton for the science cloud wiki page up: https://wiki.openstack.org/wiki/Science_Clouds 21:52:59 #link https://wiki.openstack.org/wiki/Science_Clouds 21:53:36 still need to transfer more of the actual list over and follow up on checking out some of the clouds that were listed at the bottom 21:53:48 the table looks good 21:53:52 but mainly interested in feedback around the "Science Cloud" definition 21:54:01 did you mean for Grid500 to be in square brackets? 21:54:28 Looks good so far. There are many Euro projects in this area I'm only dimly aware of 21:54:38 anteaya: no, just a formatting glitch 21:54:57 b1airo: okay great, the wiki has a preview button you might find handy 21:55:16 also when editing a page it is helpful to add a note so you can find edits in the history 21:55:24 i think the original etherpad was dfflanders brainchild but scientific-wg is best place to curate it from i guess 21:55:37 the page looks good to me 21:56:02 So, it sounds like this is more the Public Research cloud definition than Science 21:56:09 I have something if we are in open discussion phase 21:56:48 rockyg, what's the distinction there (especially, what do you mean by Public)? 21:57:04 #topic General 21:57:06 rockyg: It's interesting that there is a distinction. Mostly the distinction is in who gets to use it perhaps? 21:57:34 anteaya: shoot 21:57:47 thanks I have some suggestions for https://wiki.openstack.org/wiki/Scientific_working_group 21:57:59 Well, both are good questions. The reason I said public research is specifically because of the footnote for "non-commercial" 21:58:05 put the history section above meetings and the meetings section as the last itme 21:58:07 item 21:58:25 then have the agendas in reverse chronological order, so the most recent agenda is at the top 21:58:30 anteaya: no problem with that, makes sense to me 21:58:32 Feedback on wiki page. Not sure if research "data" needs mentioning explicitly. 21:58:35 the page will get very long very fast 21:58:37 rockyg, ahh right - i meant not-for-profit cloud infrastructure, not clear enough i guess 21:58:38 oneswig: thanks 21:58:58 oneswig: I think it will improve useabiltiy once you have 30 or so meeting agendas in there 21:59:33 anteaya: by that point perhaps all but the most recent meetings ought to be punted onto another page? 21:59:38 i think we should just cap the number of agendas there 21:59:42 that might also be different for "community science cloud" whereby it is only used by a subset of universities but not offered to "public consumption" 21:59:46 let's not plan on that 21:59:53 let's plan for what we have now 21:59:57 leong, ++ 22:00:07 and then make changes once we have something concrete 22:00:19 oneswig, better yet, we just dump the agenda into the IRC history and let that be the Internet reference for it (then delete from the wiki) 22:00:34 b1airo: there you go 22:00:41 b1airo: seems OK to me, no value in keeping it for too long 22:00:47 blairo ++ 22:00:57 just creating work for ourselves in shuffling content around 22:01:00 technical committee and infra just change the same agenda in place: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee 22:01:05 and link to the meeting logs 22:01:09 time's up 22:01:17 thank you 22:01:18 thanks everyone 22:01:20 so it is! 22:01:20 lovely meeting 22:01:23 thanks all 22:01:28 until next time! 22:01:36 Thanks all! 22:01:39 TTFN 22:01:44 #endmeeting