Live minutes FWIW: https://docs.google.com/document/d/1c-dFS5-7IEUOUm4Yikb3v-T7jfuaw9f_KRUT7wvyprU/edit#heading=h.2itk9lr36liz

Live minutes: https://docs.google.com/document/d/1c-dFS5-7IEUOUm4Yikb3v-T7jfuaw9f_KRUT7wvyprU

Hi all - I think some folks are accidentally unmuted and am going to mute all real quick. Feel free to unmute yourself for questions!

Thanks :-)

Are the slides online somewhere?

not yet - will post them after Carl's done.

Could we also get that notebook file posted.

That was impressive.

Very nice!

What do you envision the notebook to look like eventually. Currently there is quite a bit of code related to HTCondor, Dask, etc.

Put the links in the live notes, please

My question: What do you envision the notebook to look like eventually. Currently there is quite a bit of code related to HTCondor, Dask, etc.

How hard is it to interact with the DASK cluster via python code on my local laptop instead of through Jupyter/

Side note: US ATLAS is also working on a k8 Tier 3 which has some similar elements. It might be nice to organize a blue print meeting that looks at the efforts and what is availible. @MarkN.

Helm charts for any of this, for deployment elsewhere?

about SSO: we should not tie entirely and only into CERN for authz. It makes working with undergraduates impossible. I’d like to be able to give non-sms members access to my facility because they are undergraduates that come and go.

+1 to Rob's and Frank's comment.

Also - needs to be able to run this sort of thing from a python script - not just a notebook environment.

@RobG: The Helm chart is in the live notes. Apologies to those who are helm experts for the ugly code.

Yes! @msn

Blueprint!

We normally support libraries - people build a fitting library. Are we just talking about moving that model to supporting a service rather than a library?

I think the service would take a workspace + an instruction of what to do with it and return you the result (there’s a slide or two in Matthew’s pyhf talk in the next parallel).

I think the libraries is a SW side, but when we talk about analysis systems, it includes the infrastructure / service elements to run the code

There is a demo of a fitting service already that Lukas demo’d at CERN. It’s a function-as-a-service model and you stream pyhf JSON to it.

How much does it make sense to talk about specific “services” when we have the kubernetes and DASK backplane? Does something specific need to be running, or is it just config that can be launched into the framework?

Yes, and there is also FuncX which takes the idea and makes it more general.

Yes

And I wonder if people couldn't just "code-to-that" as it were.

So you still do what you are interested in - the software that does the fitting or whatever - but then you slot it into an infrastructure that makes it easy to live in the analysis system's ecosystem.

(e.g. play with other tools)

For me the service does something specific with a specific API

A thin layer around the software that does the hard work?

Yes (well-defined, useful analysis services to talk to)

(at least, that is where I was trying to head)

(and not that infrastructure isn't hard work)

What RobG is talking about now.

Here is the fitting service demo:

https://github.com/lukasheinrich/lhoodbinder2/blob/master/PlotContour.ipynb

I just saw a bunch of people wanted access to the minutes. I've granted it - if you refresh your page you should be able to contribute. Appologies for having missed the messages!

my mic may be busted but this is definitely something we've been trying to simplify with SLATE. We would like to reduce the amount of stuff that admins have to worry about in the world of K8S

part of that is having very opinionated deployments of K8S

reminder we have wlcg-k8s working group

I agree 100% with what FKW is saying, but need to drop out for a Princeton administrative discussion.

n.b. we do have the SSL convo coming next, https://docs.google.com/document/d/1BZAR1p_54xn2d8yekzjYmTPjsjj5qhfTCUISZ9T_mz8/edit# for those who want to continue

Related to handling dynamic environments in kubernetes that are CI/CD’d, there are tools such as Orca that can help automate this an plug it to Gitlab https://github.com/nuvo/orca