Ceph Testing Weekly, 6 Feb 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2019-02-06 :: Ceph Testing Weekly

Description

Weekly collaboration call of all community members working on Ceph Testing.

https://ceph.com/testing/

A

B

A

C

Things number one: I'm gonna take a stab I'm gonna relook at that PR I, had the Beast chart runner one for our GW 2011 documentation number for one of the tooth ology tasks that it ran. There was nothing going to standard out and I wanted to figure out why that was but from what I remember that PR was more or less ready to be merged outside of just how to use it. The other thing and I shot you an email about this Greg was I'm.

C

Coordinating the google Summer of Code and outreach Eve programs for Seth and I was wondering if you guys had any project ideas for interns in the summer on like core technology itself or technology. Tasks that need to be written I mean anything really anything that can be upstream and beneficial to the Ceph project upstream.

C

Yeah, exactly there's not that. How do I say that this that overhead of you know waiting an hour for stuff to build on some like student laptop and trying to understand what distributed storage is on top of that when you've only taken like three computer science classes ever.

C

And then, like contrary with this, like large mass of C++ code base and I, don't know how many people are even working on like tooth ology itself at the moment right now, because Zach doesn't work on it. Much me more. Does he no? No.

B

It's actually mostly here and some Nathan computer and I'm poking around at it, but having made the actual code changes yet.

C

So yeah I just want to plant the seed in your heads.

B

B

C

So we find out if we get accepted for google Summer of Code, the 26th so like. In the meantime, we need to have our projects up on the website, which we already have 8 projects that are gonna be on the website by the end of today. There's like four already up and then there's four I'm adding later tonight, and we can really keep adding projects.

C

The students don't start applying to them until the beginning of March, and for that I was gonna work with whoever the mentors words have a very streamlined application process, so that I usually do some of the initial weeding, weeding out to make sure that these people, these applicants, actually know how to use Linux and can do some basic Python programming before I kind of pass, the more serious ones on to the Mentors, and you can interact with them a little bit more I guess: I'm less of a fan of just like students, writing up a plan and trying to do in the summer and more that students can show me that they can open up a very small pool request in the very beginning and do a little back and forth emailing with the mentors to understand what their working styles like before.

C

We even accept them. If you, if you can kind of see the difference, yeah.

B

Come on something for sure anyone else, if you have ideas.

C

Yeah I don't want to guarantee that this project will happen and.

C

But yeah I mean I want to do the best I can with what we got right.

B

C

And hopefully something come of it.

B

C

That's it for me: I'll, probably I'll, stick around for the rest of this meeting and I'll probably come to the next few, just hear about ideas and stuff. If you guys can think of with anything.

B

All right I'm, the only thing I had, although it I think got anywhere yet but Sebastian I was talking to Noah in our stand-up on Monday and he sounded too open to the idea of switching Pathology, you systemd, so that we can actually write some Orchestrator there's some acetate Orchestrator tests, but I've crossed my fingers. That may happen.

B

um You got anything else.

A

um Yeah the answer mr. dusters, but we we've talked the week before last week straight and there was no real progress on that Oh Sean Michael is really the only one looking at the anti-balaka straighter and there is no testing at all, no one looking at it other than John meager.

A

So I don't know. If we really should release the internal orchestrator as it is.

B

Orchestrators would need I, don't think we have any actual expose functionality that relies on them. Yet no.

A

We don't have any functionality that, but we will so. For example, the dashpot will vary the orchestrator to look for the a scuzzy.

A

Suffice Kazi API URL, for example, and possibly the the dashboard will also look if there is an NFS, Ganesha gateway that it's running, so it's going to be to get use, even though not everything is really supported by the answer orchestra as of right now so, but I really don't know what we should do about. The ant will Orchestrator right now, as especially as no one really has a look at it. I.

B

Mean I'm all for not releasing tested untested code and if the Etzel or Crusaders doesn't have the maintainer ISM. That seems bad, but.

B

It's not really a decision we should make in this meeting either I think you probably lost the sage and yeah.

A

B

The leadership team about what it would mean because I don't think most of us even know what would mean for it to not be released or to be released. Mike can we just not ship it and then once it's all done like? Is it icing down you to put in the in the folder and package for a point release.

A

Down yeah, so I don't have any problems and Beck quoting into a Nautilus deck, putting new features internal dos so which will then end up in the next minor release. Or if someone really in including me has a time to look at the end, super Orchestrator, then yeah we are, we might ship it in in the dot. Oh release, but yeah that orchestrate has a bit problematic.