Kubernetes Storage SIG, 16 Mar 2017

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes SIG Storage 20170316

Description

Kubernetes Storage Special-Interest-Group (SIG) Meeting - 16 March 2017

Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.4wqz8vvnk99f

Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage

Moderator: Saad Ali (Google)

Chat Log:

09:04:43 From erinboyd : Please mute if you aren’t speaking
09:40:31 From hayley : can I get a link for the CSI doc?
09:40:53 From Jan Šafránek : https://docs.google.com/document/d/1JMNVNP-ZHz8cGlnqckOnpJmHF-DNY7IYP-Di7iuVhQI/edit#
09:41:46 From hayley : awesome! thank you!
09:47:02 From stephenwatt : DockerCon is April 17-20

A

Alright, so let's get started. This is the bi-weekly meeting of the crew. Burnetii storage special interest group today is March 16 and as a reminder, this meeting is public and recorded. Let's get started so first on the agenda is status, updates, I'm, going to go ahead and open up the planning doc, and we can reveal item.

B

If X, if you're not speaking, can you go on me.

A

Okay, so we have one week left until the 1.6 or equal to the front organization. We've been tracking for our the crew, benetti's storage side of things, and in fact there is a second spreadsheet which tracks all the features are supposed to be in 1.6 might be worthwhile just to focus on that.

A

So we go scroll down here to the storage section I.

A

Think there were only a couple of features that had outstanding docs all the features here had their code already checked in. Let's take a look.

C

Okay, I do have to control the meet others. Yeah we're great.

A

Okay, that should be better.

A

All right, so it looks like only this feature- does not have its docks in and that's the Flex volume plugging chakri. Are you in the line I.

D

Thought yeah I'm looking like most views your feedback and upgrade out tomorrow morning. Okay,.

A

Cool so I think they want to get the pr's in as soon as possible. They gonna have them merged by monday at the latest. Oh okay,.

D

How's, your foot in the project awesome.

A

Thank you very much, I think we'll do the wolf has their docs in and we're looking good all right. Thank you for working on that folks. I think we're good for 1.6, otherwise, Doug can't look low last I checked. Let me take a quick glance at it.

A

1.6 miles own label, storage, sig.

A

Won't have any open bugs, so there we go we're good from the storage side to the 1.6 release other than that open docx, and that should be resolved today. Alright, moving on to the next item design reviews, we have an item added by tamil tamil. Are you there? Yes,.

E

A

Floor is yours, take it away, yeah.

E

So, basically, that issue that I'm dealing with it is we are running coupon this cluster on, like digital ocean, our lineage kind of simple visas providers, and they only have like most of the land, only have like a single primary partition and there is no option to add any secondary disk. So so today, the you know like if you want to install a like the data is serve all the process or my sickle. The stateful set.

E

The problem is that you know you cannot really you the training and the only option you will have particularly using something like a host of the issues that the host park. Commissioner, there is no substitute for dynamic of professional, and actually I think the scheduler doesn't have enough information to like ensure that the if the pod restarts of the northeast as the host art expert example forgets to go back to the same part, because painless poodle, I guess. My point is like how do like the claws or like whatever options we have so.

A

Hope Pat has never was never intended to be used for production systems, it's more protesting than anything else from space. It's basically grateful I like urban, any paradigms it doesn't. You start writing things to a local disk. Kuber Nettie's doesn't do anything to ensure that your pod, when it gets rescheduled, comes back to the same machine. This problem space and all we're calling a local storage in general on there could be persistent local storage or a femoral. Local storage and Michelle from our side has been driving an effort to to to make local storage work.

A

Michelle. Do you have any comments on this.

F

Hi yeah so to all I, haven't taken a look at your profile, not really exactly what it's doing, but I think so. We've been discussing on the fish fish, I and Kamal has been discussing on our PR about this issue, so we can continue discussing their if we want, but the basically fish is suggesting that, as part of our proposal to add a new local PD object that we.

F

We also allow you to specify directories instead of partitions, who you know and allow for this kind of use case. I guess I still have some reservations about that, mainly because that usage is going to have a lot of the same issues as host path in terms of not being able to capacity enforcement.

F

Sorry but um I think we can try to see. Oh, yes, we can see if we can work something out there. Yeah.

E

I mean so the way you know we are looking at this is particularly if they're, like people were using something like a like a digital ocean of things like that. You know they without like qualities. They can actually go and install like it. Every cell wall on a maybe like any minute about their application, but the moment they, but you know who want to do the same thing with communities, is just a possible. So, like you don't cry so it.

B

Is possible I just want to frame it off. So what you're? What you're saying is? There's a limitation in the system volume framework? Okay, there is, but there's no limitation in the volume plug in print. So so what you? Basically to summarize, you can only claim network this ornate wood, shared process of you can't claim local disks. So that's Michelle's proposals to be able to be able to claim local system at it, advertised promiscuous, Ambani.

B

What you can do in the work around today. It is or be a little bit and it makes your Cooper natives nose pits rather than cattle, but what we we do, the Swift like running storage platforms and Cuban eighties, and things like that very similar, you think, is that um you give your pod a note selector, and so you label the node with the host forage.

B

And then you give you quite a node selector and then it always lands on a server that that has the disk and so surface a single instance relational database like mice, people and you set up this- might equal five. Maybe it's a replica set of one. So it's always running and uses the nose to lace always land on a particular host or distributed systems like like I'm.

B

You want it to do or Cassandra or go to Pixar movie elasticsearch on something like this, where you know those those distributed systems or follow sort of the same pattern where every node uses the local disk and then they expose the all the storage wire and some sort of federated API.

B

If you can need to do, is have a replica set of one. For every note. If I'm trying to do is 10 nodes, say Cassandra, cluster and I have 10 replica see each with their own notes. Selector. We.

E

Find so we haven't actually done all those, and we want to kind of want to move away from that because, because that makes it very difficult to like do something like that works and like Google cloud, but then doesn't work on like you know before somewhere else. Well, my my I guess it's not a very like a proposal, but more like you know. We just want to make it bring.

G

E

For that one time look or the first proposal is, you know available. It is particularly serious about it so that fateful fish can be, you know, do it well.

B

And that's why over will be I.

D

Had you looking to do a check, we are looking for a short term solution and you want to wait or for the local storage. If.

E

There is a short-term solution that will be kid. That I mean because I mean I, don't mind.

H

E

To be available, if only I like a timeline, I came on for six months along with me.

A

Local storage is charged metaphor.

F

A

Alpha in 1.7, which is a roughly three months out, but go ahead chakra, you said you might have a better short-term solution. Yes,.

D

Actually, you can replace the scheduler with your own scheduler, that's one way and which will have the knowledge about your local storage, which can pick the note for you and you do the scheduling decisions. That means you can ask badminton you're like.

E

Yeah so I guess that's what I'm really planning I mean. If you look at the other link that I have in the external some functional report about that file, is that sort of rule out I'm trying to actually think.

D

I have made more dynamic than a North character: yeah, let it mix it yeah.

E

Hello yeah I can hear you I think I.

D

Cumbia, why should read it? Oh.

E

Yes, I can hear you, okay,.

A

So it sounds like there are short-term workarounds they're, not ideal. There's work to be done. There are better long-term solutions. Put it online if you want to be involved with those reach out to the shelter.

H

B

Sorry I think you're having some connectivity issues to dwell. There's a lag and stuff.

A

Let's move on to the next item: Thomas snapshots: next steps: are you online Thomas.

I

Yes, I am well, but it will.

A

I

Oscar Whisky water to make sure that the proposal is progressing. Sowards merging me to the upstream. The whole document itself is so much public its Sun, but it says that it should be me. Yeah I, don't know imaging is the goal.

I

It's not, then I would ask her to to make the documents on publicly accessible, and I would like to also suggest that if it would be possible for people who are interested in the feature and in the proposal, if you can meet like more often more frequently once twice a week, Center some doodle question and we could discuss and make sure that the proposal is really moving towards merging. Oh, that's, all I was hoping that would be in the call, but I.

J

I

J

With you older one, filling whisenant.

I

Could you please repeat that I didn't lick, it twice, you think is better I after.

J

You well start with some time we'll see.

I

Ya I'll send an email to 26 storage and we can. We can agree on some sometime that would suit people who are interested in this announcement. That I would like to help with that, if possible,.

I

So, that's all for me.

A

Alright cool, thank you for that update, so keep an eye out for any go from Thomas on the six storage mailing list, and if anyone wants to get involved with that effort, I'll feel free to reply to that.

A

Moving on, we have PRS to discuss that need attention. Yawn added storage classes be one in 1.6 yawn. It looks like this was a change that you got in, but was reverted because of some gke issues and now you'd like to push it in again, nom exactly so, I I think it's a big change, so we might get pushed back from the released folks.

A

What if this doesn't get in what will not work? Well,.

K

Basically, everything will work, but we exposed v1 API, but internally we will use the data API. It's only change.

A

Okay, so internally, what we're going to be using the beta yeah I think that, okay to not get in for 1.6, would it be okay to get that in for 1.61? Well,.

K

It's kind of weird because the export API, but we don't even have into n test for the API.

A

I completely agree nah, it sucks, but we have one week left until code, freeze or sorry until release, and we are in code freeze and trying to get this passed. The release folks is going to be difficult. So unless you have a major driver, I say, let's hope.

K

We are is open for two weeks almost yeah.

A

I hear you I mean the run code freeze for that period, so yeah.

K

I know: well, it can sleep through 1.66, 31 I, don't see a programmer that, but still I will I get in as soon as possible. Okay,.

F

I have a one possible suggestion: would it be possible um just to have the test call z1, api's I, think if, if we can argue that this change is only changing tests and including the test coverage, then they might accept that mm-hmm.

K

Okay, such a good idea, but.

F

Maybe we should check with them first before we go through this effort. Ok,.

K

I can do the pr tomorrow and let's see what I say, Michelle.

A

Do you want to reach out to Dan and see if he'd be okay with that? Okay.

F

Yeah I'll reach out to him. First that way, you won't, you know to see if we, if he will approve that that PR is and did that cool sounds good.

K

I'm good, alright.

A

Thanks John thanks Michelle next up, Brad posted an item for attached, detached fixes for 1.6 Z Brad. Do you want to talk about this? Sir?.

L

So Hamas has been working on a PR, I, choose or restart of the attached detached controller right now, if it restarts it loses those days which leads to awkward problems I, we were trying to get this in for one dot six, but it was too big of a PR with too many issues actually get Burgess in time. We've talked about doing this for one dot. 65C hi is this some we want to consider and if so, what's the next steps to do that so.

A

I remember taking a look at this PR I think it's definitely something that we want it's too late for 1.60. It's definitely not a bug fix or it's too large to be considered. Your bug fix so we're, let's target it for 1.61, Jing, I and michelle's start taking a look at the the pr anybody else, who's interested in reviewing. It should take a look at it as well and will target 1.61 for.

I

Just one more note, Tomaj speaking, I'm just writing some battery unit tests, so we can eventually catch possible problems. So this is a PR, but I am but I am quite confident about the latest version. I think it's much better than what was originally so cool.

A

Sounds good more tests better do.

L

You know any logistics and a 16 g, that's something that were there. However, what do you mean logistics? What do we have to have the reviews them by windows that have to be well.

A

I'll after a 1.60 is cut the point releases, 1.6 115 you are or I guess, they're called patch releases are cut, basically a domestic in general, it's anywhere from two to four weeks cadence. So it's kind of a rolling train grab, whichever one works best for you, we're going to try for 161. If we missed that, we could always do 162 no big deal.

M

A

At worst, it would be about four weeks, but usually it's faster than that. What.

L

About merging distance there Master right now right.

A

Now masters on code trees because of 160 degrees is going to be lifted at some point between now and Wednesday. When the release is supposed to happen once it's lifted, then you absolutely. This should be able to get merged to master once its code reviewed and then you can share ii. Think it to the 160 branch after 160 is cut yeah.

L

That's what I hope we may could do is visit some masters and it opens up, and then you know back for it to 161 so that we're not backport you've been weird. All the time make.

A

Sense, Oh we'll keep that on the on the burner.

A

All right, I'm going to switch up a couple of these items. Next up I would like to talk about container storage interface. I posted a link there to a preliminary dock in the agenda. So the idea here is a a few weeks ago, a bunch of folks from Cooper Nettie's, docker, mezzos and cloud foundry got together to try to define what we all think.

A

Aiken standard container storage interface would look like and the the idea behind this, if you look at our number one goal, is that a storage plug-in author should be able to write one plug-in, preferably a container that just works across all container orchestration systems. That's a pretty grand goal, but I think one of the major feedbacks we've gotten from a lot of storage vendors is that you know they have to go in and write custom plugins for every one of these systems, sometimes its entry.

A

Sometimes it's at a tree and it's a pain and really they should be able to just do the work once and have it work everywhere and so to try to achieve this vision. We first just got all the cluster orchestration systems together right it. If this is something we want to do, and folks decided that this is one you know. This is something that everybody wants to do it's beneficial for both storage vendors, for cluster orchestrators and for users. Then it's a question of how we're going to make that happen on this design.

A

Doc is an attempt to try to converge on that answer. So far, what we're proposing is trying to limit what that inter food, trying to limit it to what the interface should be.

A

What is it that we absolutely would need from storage provider, and then the minimal amount of implementation dictation required to implement that, and so what that looks like at the moment is we're thinking about some sort of long-running container that will expose a REST API that it takes for following commands, create the lead, attach detached, publish on publish and a few others, and so the idea here is that we don't dictate how you are going to deploy the containers or anything like that.

A

That's up sequester orchestrator to decide. We don't, you know, try to we're going to try to minimize the interface as much as possible, and so folks are interested. We could go over some of this doc or I'll just open it up. The question now.

A

What do you guys think you guys want to just do a quick overview of the doc or does anyone have any questions when.

B

I get the first question I have is: does it just focus on bullying, plugins or Bishop provisioning like so like? If you broke out, the operations like mounts unmount attach detach, creates delete and then maybe snapshot replicate as a day to operation, but how far along response was a good yeah.

A

So the idea is to try to encompass everything that cluster orchestration system would need from a storage provider, and so that does include dynamic, provisioning and D provisioning volume. It does include attach detach, and it does include Mount unmount, which we're renaming to publish unpublish, because mountain mount is very overloaded and those steps could be could encompass a lot more things than just mounting and unmounting.

N

Well, I appreciate the intro, but I think I'm going to need more time. Maybe you really plan on a more detailed dive into this Facebook base. I.

A

An idea here is this is very, very much a draft. We wanted to make sure that all the cluster orchestration systems were on the same page to begin with and then open it up for comment and and then see if we could all converge on on an agreed-upon design. Oh ok, I'm here final, yet.

N

I'll go away because, just in the last couple days made those just published their own version of a proposal as well and should be the same exact doc, we've been working together. Okay, it isn't, but maybe it's at a different level, because they're even talking about how it ties into some of the higher level functions nicely.

F

N

Bezos but okay.

C

N

I want to do is kind of an audit of you know whether there's any differences or gaps and even compare it to the you know. The scale Liam sees a Lib storage and what's going down there, but yeah I'd like to have a few days to look it over and then I definitely want to cover it in detail at that basic excuse me and.

C

The use of the geography sent actually just the specification that my fairly commencing location detail so.

A

uh It's an open question at this point: we've been thinking about whether to enforce grp, see as the standard interface that the containers must expose. The idea here is, on the one hand, if you want to have this ideal of a storage provider, just gives you a single container and it just works, and we interface that it exposes the rest. Api should be consistent so that you know you don't have to have four or five different flavors in the same container.

A

On the other hand, it is an implementation detail and it may be something that we want to leave open and let storage providers and cluster orchestrators decide that could cause fragmentation pros and cons on both sides haven't really finalized that yet all right, we're using grp, see just as a mechanism to write down what the interface should look like, but you can swap that out with JSON or something else that you really wanted to all right.

O

So that's where feedback of those documents community just should you just add comments to the document. Is there another.

A

Meeting scheduled.

O

A

Just add comments to be to this document and that will be the central place to start organizing feedback. All.

O

Right and is there to like a plan to involve these storage providers and a future meetings of the office pages. So.

A

I think there's going to be one more meeting between the cluster orchestrators, probably in the next couple weeks or so, and then, after that, the plan is to start getting representatives from various storage vendors involved in the discussions as well.

J

This page, yes, so for things like for vertical the future plans like an aggregation, specific video, that's unlikely! Oh, you see that interacts with this. So.

A

At this point, we want the interface to be everything covering everything that we currently have, but we definitely need to consider expanding the API in the future and so the exact details of how to do API, versioning haven't been defined yet. But the idea would be that this is a versioned API and that you could expand it in the future to encompass new functionality like replication and snapshots, and things like that. Okay.

J

Yeah I think that's very important for this to be wrong, leaving yep, because you never have nuptials cutting and that's definitely not covered right now. Information who knows with it yeah.

A

We definitely want to make sure that it is flexible enough to add things in the future, but start off with something minimal that will be sufficient to get us off the ground. Okay,.

J

I, don't have it I just suggest that we should do someone mentions down to include an attack. Okay, cool.

E

Sup, human psl, or just looking at, like the publish, unpublished operations that happen on the node, sounds like we're, considering the restful service or something like this of service. So how do we deal with like services that has to select the operation that has to run on the node and cannot be centralized? Yeah.

A

So arm in the stock right now, it's not very clear, but one thing that we want to make clear is that some subset of these operations will only be able to be executed on the node. Other operations could be executed either from the node or from a master machine in particular.

A

Publish unpublish, get node, ID and probe are all operations that can only be executed from node machines. The remaining operations should be able to able to buy by either node or master machine.

B

M

Ok, so this is venkat from Port words. Absa doc is great, but when you guys say you know you're doing this, palanga orchestrators and I see the EMP scalar product name them the sample workflows. It doesn't really talk about democracy or you know now.

A

This is what I an exhaustive list at all. This is just a starting point, so feel free to add storage systems. There yeah.

M

What we don't want to do is to take like one implementation, and just you know back over so think about if you want to make sure absolutely.

A

Yeah yeah now I I completely want this to be a fair, open and transparent process. So the part of the reasoning for only including the orchestration systems in the initial conversation was to prevent this kind of biasing from from storage, vendors storage.

A

Vendors, obviously all has a vested interest in promoting their own solution, and what we wanted to do was first not have those voices involved and focus just on what would be best for end-users and what the cluster orchestration systems agree on once we have that bend idea is to open it up to storage vendors, because, obviously, storage vendors have a lot more experience in this space and help. Let them help shape what this is going to look like, and so we're getting to that point now. Well,.

M

Absolutely and thanks for clarifying that, in fact, more than more than I, don't want to sound too optimistic here, but more than you know trying to push the perfect solution. We want to be able to work with the orchestrators to get information that we generally can't get like to be. Application-Aware get x about placement and all that, so you know I rather not want respect to degrade into something like a credible asian all describe creation, apps and drinks naps. Then it just gets boring it.

M

That's what you know we can just go back to what's near did with sim. You know if you really want that right I mean we have to get beyond that, and you know make it truly converse and that's that's where the direction are like. Okay,.

A

That would be a good feedback once you get the ball rolling on this yeah.

B

I think another way of framing this is like so just to like you know, like you know, the tip rbd on is there, but this is the first time rock from red hat. First time, I've seen the stock so I didn't add it no.

A

Yeah this is, this is an incomplete list. It's uh what are the existing volume plugins that exist, and we want to make sure that they continue to work through this interface. So what.

B

One other thing, just two ads are like it's a fairly common pattern: just because large open source community just like expediency for a bunch of folks, like a small, remember like three or four people that are cooking up an idea for a proposal to get together and bastard amongst themselves, till they've got something that they think is is with while and then they open it up for public discussion. So I would say this is still in proposal.

B

Taste which isn't like cause like this is the final poem I think he's just saying: hey there to feel that we put this together, we you know, looked at it together and ironed out, some of the kinks of just so that it's safe I'm when we open it up more brilliant yeah.

N

Just for your works, guys who might have been offended to be left out, I'm with Kelly, MC and I, didn't see this document making also a couple minutes ago. So I'm not complaining the scale hi bill mentioned, but I didn't participate in this either. So I think it's still a level playing field going on here from what I can see absolutely.

M

I was just trying to you know, make sure that we all agree to that, but hey thanks, Team appreciate it. We're looking forward to meeting you in the face face thanks for watching that cool.

A

Any other questions or comments.

P

If this circuit decided, what's the relationship for their support of difference, two out of three volume, plugins and click- oh yeah,.

A

So, as you know, flex is currently being iterated for 1.6 to include the attached or detached your interface that we have internally for Cooper Nettie's, that's going to be a breaking change for existing drivers of flex they're going to be needed a they need to be updated for 1.6 moving forward for out of tree. What we're thinking is that this is going to be our driver for out of tree the interface once it's agreed upon. Then it's up to the cluster orchestrators to decide how they're going to implement it.

A

So for us in Coober, Nettie's we're going to need to decide whether this is going to be an iteration of flex, whether it's going to be a new plugin, we should call it flex 2. We should call it something else or whether it's something that we're going to bake into a lower layer of the storage stack where it's not a volume plugin. But it's something that Kubra Nettie's storage sack natively understand, and that is an open, open discussion. We haven't gotten to the point of Coober Nettie's implementation, so.

Q

Fabulous in that meeting, Kerber Nettie's may so stand long. Brunette.

A

Ease made those cloud foundry and docker: okay,.

Q

C

L

You have a release targeted for this, and this is way now bio stuff. There.

A

Is no relief targeted for this? It's going to be ready when it's ready, we all have I, think all the cloud orchestration systems have different release schedules and cadences, so we're just going to try and see if we could converge on this as soon as possible to something that we agree on get storage vendor input once we have something.

A

That's final, we're going to publish it, hopefully have the CNCs pick it up as the de facto container storage interface and once that's defined, and we can start talking about implementation and implementation will be up to each one of the cluster orchestration systems to figure out how it works in their system.

A

Alright questions.

L

Give it a feedback he wants me back by two weeks from now, three weeks urges within.

A

The next couple weeks would be greater within the next week, but I think we're going to open it up why to a wider audience or start incorporating storage vendors in meetings, probably when within two to four weeks and at that point, that that will probably be another better Avenue to get your voice heard. If you're interested helpful for you Brad just and you could start commenting on the dock immediately. Okay,.

A

All right is no other questions we can move on to the next item on the agenda.

A

Next item is Q. Connie you it's coming up in two weeks. There is a list of the agenda of who's. Attending looks like from the google side. It'll be me and michael rubin Yan is going from red hat. Sarge will also be there if anybody else is attending, please let us know and we'll add you to this agenda doc.

K

Rank from meeting or dinner, or something that.

A

Would be great, there is no face-to-face, because there's a lot of folks from this group are not going to be there. I like.

F

A

An informal dinning or something I'll take a note to do that. Yeah.

M

I think Michael ferranti from four courts will also be joining their leaking like in the pool.

A

And could you all fill in his name thank.

C

A

And just to be clear, this is not going to be a face-to-face meeting. This is just going to be an informal get together perfectly.

K

A

Speaking of face to face the next item on the agenda is a face-to-face meeting in santa clara on april fifth, which is the current proposal. Steve, you want to talk about that. Yeah.

N

If you could, if you could put your name down if you're it's an educated guess as to whether you come just so, we can get the room reserved. We've got a number of choices there and I just want to get one.

N

You know in a round format appropriate for discussion that will match our group size also, like tentatively allowed for to extend into a second day, but unless there's a spot on that document in the link to put proposed agenda items- and we can call it as we see it- I I personally am traveling in and will since I thought, we'd have a dinner that evening I'll be staying when I tonight anyway. So um maybe we can resolve within the next week whether we think we need a second day I.

A

Think in the past we've discovered one day has been too short. Having two days back-to-back has been very useful. I would suggest two days as possible. Ok, I'll go ahead and book rooms for to them and ok, we'll see what happens is.

L

The date right on this I've heard talking since I wasn't going to be able to make this take, they might push it out. I mean.

A

I I can't make it during that week, but it sounds like a lot of other folks. It's going to be harder for them. Yes, what.

N

All of us had dr. Khan's coming up later that multitude, so I think we discussed before some of the options and pretty much every everything in the month Ted some people would have to miss yeah.

A

I can try to dial in as possible, otherwise Michael or Tim can represent. Google I mean.

L

We have auto treat volume plugging in provisioners, which is basically the CD aside and I. Yes, I document.

A

L

I owe you I mean we're going to have adequate representation there to discuss it inside. This was kind of your baby. Now, right, like these nanos.

A

L

A

Know and I mean I really wish. I could be there, but like it is. This is the only time that we can make work. Then why is it the only time we can make it work? It's a.

G

Third base to base Assad has a good at second third or the first one. You were no one ever it.

A

Through I was their first year, I. Was there a third when I wasn't there into the fourth one but face to face yeah our face-to-face would used to be very tiny. Oh okay, maybe I didn't rat you, so so yeah I mean if we can modify the date at all. If that would be wonderful but hold on.

I

K

G

Like the out of free plugin thing is such a big deal and side is code beeping it with chocolate that I I'm wondering if that really kind of sort of Trump. Some flexibility here, yeah.

N

The other, the only thing I'd say is the elder tree, probably is going to be more than just listening anyway, and this would almost be an intro. It's also kind of early right. I mean, if we're talking about this, then just being opened up from storage providers in the parliament even make her is building very intrumental talk about.

G

N

It again: well, I think what the timing you know discussing the CSI draft that we just saw yeah and somebody threw out that you know at this stage- is still being discussed amongst the orchestrator, but maybe even changed a bit up. This face to face is going to come down pretty much aligned with the first exposure of this to these storage providers. So that being said, I think that it'll give us a chance to get an intro presentation on what was there. What the thought process was in terms of, though a real Cyril call.

N

It negotiated discussion. I think that this is going to have to bleed into follow-up meetings. There's no way check I'm frame we're going to not going to have additional meetings to talk about this. So it's not like this is going to be the only one yeah.

G

N

If we might flexibility during that week, I could probably move it within a week, but I think fraud. If I remember correctly, you were going on vacation kind of that whole slot anyway. Yeah then once it gets into the next meeting, at least for us- and I said, I suspect, the rod of all this docket mom comes up in in mid-april and I suspect. A lot of the group X complexes.

G

For wait, a minute you use left, we suspect the Google conflicts with the week after that, because it's a doctor con or something right.

N

Dr. Khan has actually starts on the sunday, but if you people are speaking for some things like that, it's awkward time, you need some time grafton anyway, for speaking for the deli of see teams and next week, the next two weeks after.

G

That aren't going to work for us yeah. We just got up like next and we got cute con so we're doing with that sort of Fame crunch here, there's too many conferences and conventions, and they never stop yeah like when do we get to work the holidays? When everybody wants that.

N

Time, optus, that's from the conferences, I.

G

Think I'd feel more comfortable with this. If can we have and I guess yeah? Maybe we can do it that way where we have a an intro to the other tree provisioning stuff and like chocolate, can talk about flex and then you know I guess: I can present sods work from CSI and then we make sure that we schedule a follow up shortly after a doctor con to talk about thankful, in-depth.

G

You know, as long as we don't implement the Big Dig, to try to get too deep and instead make this like a informational where we are status, update right, that's kind.

N

Of all I see it going down anyway in I'm, going to want the intro and then go back and do it at least a couple weeks of thought and planning. You know terms of a risk I'm not unlikely to be put under the doctor. This simple, which Oh insistent p5 and.

B

Just to lay things out right, so we're talking about april fifth place for fun is april seven seas between you, but it's two weeks out well.

Q

B

Any possibility of clinical setting week, which will think something like actually minutes to twelve and sis. I would work for me.

N

It might be in terms of rocks posting at that argument. I'm going to have to check. I can't remember.

B

Does form of planning on attending is april eleventh to the twelve problematic for any.

G

Attempt to the 12 we're.

B

Going to 11 and 20 women.

G

B

G

We still, though, we don't want this to be like four days right now. It'll be two days 11 and 12, okay yeah. I can do one of those days.

B

So my six literally one we count so side would be able to attend yeah, it's the same two day meeting with just one week out from the pessimistic yes.

G

Know that that way comes to me.

A

Okay Steve: well, when do you think you'd be able to verify if those dates would work for you? uh Let me see. Is it it's.

N

Definitely the 11th 12th you want 11th and 12th would be perfect for us.

N

I'll try to contact people today, okay,.

A

Do you want to send out a message to six storage about that yeah? We are okay, perfect I'll, either confirm.

N

With we have the flexibility to host 7, 11, 12 or poor, or not yeah, nothing. You still want to host it. Maybe you can find somebody else. Oh yeah.

A

I mean google could definitely host if you guys are unable to other other than hosting do the dates work for you, I'll turn to the conflict, god I.

N

Think that I, like them I, don't have my calendar open it for me, but I think I could make those I am going to gawker com, but it isn't sure okay.

A

So, let's preliminary lycée, 11 and 12, we will await your confirmation whether you're able to host on those dates. If not, then we can go host at Google, okay, cool yeah.

B

And thought I mean I presume it's just like you know it, because they live in some 12 is just a Wednesday, yeah and I said you know if he comes back up Cesare five available each 1215 Wednesday Thursday that works as well yeah. So.

N

I'm doing a whole week have.

B

Some flexibility there on now it.

N

Looks like on the 13. We had our room meeting a way.

A

A

Okay, so we'll take this offline to a mailing list and any other questions comments, concerns.

A

All right have a good day. You get 10 minutes back in your day. Take care of it. Thank.

E