Magento Cloud Community, 13 Nov 2019

Previous Meeting

⏯

youtube image

►

From YouTube: Cloud Docker public grooming - 11/13/19

Description

The first Cloud Docker grooming including next items:

- Boards overview
- Architecture proposals
- Preserving custom docker-compose.yml files

A

Hello. Thank you for joining this meeting. Hey.

B

Thank You days.

A

So this will be actually our first public ruling, so I recorded meetings have been recorded as well, and I will share this into the channel.

A

So today we will have some say: experiments some songs about the process at all. So if you have any comments, you can stop us. You can actually share your thoughts and this participate and joined in our discussions. Thank you for your latest pull request. It was pretty good and we really appreciate your contributions. Thank.

B

A

So we have was a pretty huge amount of of issues. First of all, I would like to share some information without the pores of the design. Right now, some from the board's perspective we have currently two projects. One project is a pull request progress. This is a board that Chloe team is using and essentially a single maintenance maintenance will use to and drag the work on, the deliverable request and the second one is magenta cloud or improvement is essentialism and bond board, which shows the progress of current issues.

A

There are some interesting labels that I would like to point before we start so. I have added foreign label called route first issue for few items, because they seems pretty nice items, two important, the cloud, the proteins agent during it and the acknowledges, but we can essentially go through our if you will find anything pretty good for important disease called dr. project. We can also, as this label our next columns. Currently there is ready for crewmen, so ready for grooming is items that we consider us not ready to be taken into the purpose.

A

So this will be our of our star guests for today's, for today, as it is also ready for development cone, which has lipo code accepted. Maybe changes.

A

Can be taken by.

A

A

And we also have engineers here in the couch image, happy enrage help visa Quality Assurance all those issues and what's the ones, a quality product, and we can be merge this the issues down.

A

This is pretty all for the port. It is not really silky heavy is available for now, because it will require and the deeper indication we are working on this and currently because it's not what. How can you provide us we'll need some kind of middleware applications, those agencies labels, but now we had we just manually if he is rain. Changes review update as a channel and I mean oh.

A

We can actually go through the top issues that we have currently and I. Just look. What what is this or we can already cover to lose a leg, blood issues. You can use our product over I. What do you see how it goes.

C

A

C

Probably start with architectural able to issue.

A

Okay and good, so this one I created recently, so there's no so many times, but I just want to give you a yeah. So essentially we are moving easy tools to be platform agnostic. We have you paid appointments, which will give you possibility to run different scenarios different purposes, so I think the doctor should represent the same spirit of ec2. The same way of thinking so.

A

I would say tightly coupled with my shelter called projects. It's really it's a magenta abbiamo. It reads the services and so on, so I think it makes sense to make it a little less cupboard so people much of the calls. Maybe they have a different architecture. They have infrastructure.

B

A

They just whatever don't have my child did have composite packages, though they tried some github projects come get. It will be useful for them to also have a doctor environment which will give them the possibility to pre-clear set up and demonstrate or run some tests in future.

A

So that the end, so the idea here is not hardly couple on the magenta configuration files, but you possibility for flexible configuration of services, different options for.

C

Question how's it different from running the country commanders kilometers, like whatever version.

A

Yeah, the sink is kind of little fail in the fault mode, though, because it's will try to raise evaporation until you knows it. Actually, you.

B

Proceed: yeah, hey so I've had one of my guys looking at this scenario here, so how to run so specifically we're trying to run the doctor's environment, unlike an on-prem install with Magento, for example, and we've run into the same thing where we need to pull in stuff from the Magento cloud repo in order to get that to work. Oh yeah, this would be. This would be a good one for us to work on if you wanted us to kind of looking into it, but basically he found the same thing you need to.

B

You need to basically pull in files from the cloud repo to get it to even to get it even work, otherwise, it'll fail, but we could work on making it where it doesn't require those files.

A

Yeah, you can think about some kind of the full babies options and maybe some.

A

Good solution here so I'm open for any kind of situations, discussion about.

A

B

Yeah I haven't I, haven't thought about it much either other than what you just said is kind of like set defaults. If those files don't exist, but yeah I think some more thought around the architecture would be would be good.

C

Cool, what's heaven, for example, default mapping to magenta for the villas.

A

For your money to be even more flexible,.

C

I'm not sure where to store that, but that's way actually sound setlist for me sounds because in reality we already.

C

B

C

Compatible with different services, so I wouldn't want probably to you, know, get that burden of figuring out what is compatible with what to developer. Essentially, the dueling probably should solve it out of the box. The question is only you know how to properly do that, so that we don't limit people. Essentially, our options can probably overwrite easily, but in reality you know, I would love to see the tooling actually solving this challenge for developers out of the box without any additional documentation.

C

Doesn't sound good, pretty much do? Is it something you guys.

C

D

It sounds good to me I like the idea of all services kind of being there by default and and if people don't want to utilize some of them, that's fine, but they can still be there. But by default, if they're there and configured it's nice.

A

Cool- let's compare on this: let's keep a conversation on this issue.

A

See Chris can you can move it to approved or accepted, not sure what is different, this'll be our accepted okay. Next one is in some sense that ie person didn't have this idea, but that what I sought on them, another very nice project, called I seen.

A

It I've seen it.

A

Much like just a bit.

A

Well, it's called docker multigem and they they use interesting way, so they have been scripts gem and the way they resolve in it. They create two sessions for different purposes, so the one is thinking the actually main scope of code and another session.

A

Since the vendor directive is essentially very large one and in case as it fails, it doesn't fail both session and in talk written all over the scope of files, also which what alight in this scripts they actually have possibility to kinda and operate, is a mutagen, so they can start and stop and flash the session. So it looks pretty useful for me. So I didn't like this a day idea, and maybe we can come up with something as similar.

A

What do you guys think about this.

A

B

It makes sense, but I think so, I think the bigger issue with mutagen still is the I think there's a separate issue for this. Where you have the sessions that stay open, it's like every time, I use, mutagen I forget like if I shut down my computer and go somewhere else and then restart it, I always forget to restart mutagen or if I shut down. My docker containers mutagen still running in the background so now I would have now. I would have two of these sessions to worry about right, so I think yeah yeah.

B

If we can fix that issue first and I think this would be a. This would be good.

A

Okay, so let's keep it open for now less than the focus on so second issue, because I personally didn't really think so. Any idea.

A

But I will just keep this, so we can dive in Snyder I.

C

C

And also would be great.

C

Some participant section would run polls, you know, and it created some really weird behaviors I.

A

Personally, don't really remember the last way last time I used, do you guys.

D

Have been using John Utterson.

A

A

So, let's keep it.

A

Okay, so next one is called build container isolation. This is something not very tricky about doing. One escalation of I found it essentially currently build container, has access to the system, SQL and the live, see, search and also services, because they look it in the same network. This looks like some kind of deviation from the cause and argument.

A

So I want to prove this to you and figure out if it's a really neat to be fixed over this okay to go and the same way I'm to let build contain that have the access to those services.

A

What do you guys think force your attention like this? We can just ignore it.

D

You see when you could remove the restriction that the build container can't access services.

A

So so, actually build has access to the database in the radius, which is not correct from the call perspective. We can it easily change it by hiding in your network and container work into it in isolated Network, and this will prevent it. Those acts to have access to source services so.

C

B

Yeah I was gonna, say, yeah I think it should be I think it should be restricted so that it works the same way as a cloud does that you can test the build locally, but at the same time, I know of some people that are using the build container to run some commands, because the build container has readwrite access to the to the file system, whereas the deploy container is not so that that might hurt them if they. If we take away to access to this to these services,.

C

Doesn't customize ins a deployment hooks older books yeah because right now, we've customized cooks in magenta? Essentially you can modify what bill is doing hooks our.

A

Buddy field edges changes a the guys who are using bill contained in a sanguine not expected way like random comments to change the file systems. They will lose this possibility, which is kind actually not expected.

C

Yes, as a question, so you guys are actually changing. Something on build container directly know why our cooks, essentially this that was from our understanding, is not an expected flow, but any details.

C

Because, essentially, hooks are.

C

C

A

Yeah I think so, if people really use will continue to change something.

A

Harrison, because, actually just on the calvo's access to the services like MySQL, but essentially it doesn't actually change from perspective of access to services. You can just directly station to zoom SQL with everyone and do any changes, episode. I think it should not harm them.

B

Well, for, like example, you wouldn't be able to if you, if it was restricted, you wouldn't be able to run like setup upgrade on the build container right, which you shouldn't, which you shouldn't be able to yeah. I know people have done it.

B

I have to figure out if it actually caused me problems, I I, don't think so.

C

Well, I think for consistency standpoint. It makes sense to to improve it. Actually, you know behaves the same way because anyone who's using build servers.

C

Running setup upgrades on builders problem.

B

C

Expected yeah, but.

B

C

Want to break anything, so if you might yeah I mean I I.

B

Would approve it? I I think it's people just using it for convenience. More than anything because you have access, you have access to system and all the services, but the way.

C

A

Okay, so unless keeping this empty Fanny, but you can't replace how.

D

Does this relate to the platform agnostic, docker builder I mean? Are we trying to build something? That is a replicates cloud, or are we trying to go towards platform agnostic.

C

Actually, it's a good question too. So.

A

Yeah I mean for I think essentially, if, once you go to the forum agnostic, you actually change the world. Behavior of your happy Emma was a you'll change, the scale of hooks and essentially your whose may not be run on the because in your and perform you maybe not care, was a built. It's essentially the hour. I was a sinner, so I think for consistency.

A

This current I would we cannot have this and once we go to the Potomac, Gnostics will look very different and essentially maybe give you learn on everything on the deployment area, which would make sense for your infrastructure.

C

Yeah, actually, it might be possible if you right now want to do Everson in in that way. Essentially, you can probably move everything deployed, face and run ever since.

C

C

A

And those essentially, if we are going so give so the problem is that it really counted. Currently, we really need some folks which cannot be the case for platform agnostic because they will not even be on file. So it's very that's. This is very deep arable whole, but consider those.

C

Formal Gnostic, we can probably at some point as the commerce ability to just add faces whatever else. So, if you, if you want, for example, some, you know, testing phase tandem different, who that were you can just get some schema whatever in place and run, and you know.

C

So maybe we just need to do some kind of constructor at some point, it gets filled, possibility to configure different faces like face a is read-only has no access to anything as X is parameter, Sigma the rules and just to find those parameters. What we can configure- and this way you can probe the specified we wanted.

A

Let's make us wonderful next meeting because.

A

Matt's on an assumption taking away edges. Okay, that's what we discussed.

C

For those questions this one Joe, so do you have any concerns from this one or you just try and move to make sure.

C

It makes sense to.

D

Treat you know plaque platform agnostic as a separate effort for later, and it would make sense to wrap. You replicate the cloud environment here in docker, then, okay,.

A

A

Okay, attention so structure: do you want to jump on this on this? The pose alone is to be I. Think.

C

This we don't have too much time left today with it probably takes on for next time, because it's pretty much a big topic. Yeah.

A

Yeah, just for you guys, if you want to look at this.

A

Is once we separated ec2 some different projects? We want to have also possibility to test those with docker, but because the infrastructure that those environments to run tests what's about it now so yeah, looking to the way of moving those conception for structure to the doctor, so doctor can build those test environments by simple comment: it's pretty a pretty big topic, so I c-can't will back to this next hour.

A

But if you'll have any sauce, please we have live comments that we can discuss. It.

A

So they live here essentially because he knows, as dr. Campos like doesn't really stay as it was generated initially and because our bill Campos had arise the way how we can still use compose but does not really harm the current configured compose. This is one of the social like to match a new dr. Campos configuration.

A

Preserve it, but if you have any sauce and this lettuce as discussed I.

C

Think it's also related to issue 75, which was created by.

C

Talking mostly about the fact that we need some general general config and we need overrides for different specific systems, and on top of that, we'll probably needs a custom override which is actually, you know.

C

Tell those to probably will start developing some, they all need to go together and filled both.

A

Yeah, in this case, is they actually met performance to use donating of measuring the compost, piles, which are pretty nice and the efforts to augment it, make it work really big, because we'll just how to extend our scripts, which we delivered, which can actually drop all the compost, llamo sentiment using us together, looks good guys. What is it, what.

B

I'm just trying to think this through. So so, if you run build compose and it generates the docker file, docker compose file and then let's say I make some custom changes to it. I want to preserve my file, but then, let's say there's a new version of docker docker cloud right and I want to run, build compose again to get those get that new feature or whatever it is. How would that? How would that work? How would it I wouldn't actually generate that file, but still preserve my my changes?

B

I guess: I'm, not understanding how that would work.

C

Yeah I've also left a comment in this issue like if you could scroll down regarding the same yep.

C

Yes, I think right, not right now, it's all probably how most users are doing, that they are just changing file in reality, probably we should be having some separate file for customizations. Were you actually overwrite.

C

Rigid arrays the default one, essentially your override model and still work with that unless yeah.

B

I think yeah, that makes sense so I yeah I, think the one that's generated should be left alone and if you want to add customizations, you create another file with your customizations. You know.

A

Yes, we can actually make the next scene, so we can, for example you as a customer user, you will have taken change yeah, it's not well, it's actually point but Alice cubed, so example: you'll have your constant varnish is dr. Campos and what you can add. You can actually extend the magenta darker to grab the doctor compose EML files here and pass them has a parameter to match together where your your custom compose will be on which is pretty convenient.

A

B

That yes I, like that by the way, then you can still regenerate the file and it'll rewrite whatever, but your custom changes will be preserved in your own file.

A

D

It's really nice.

A

Ok, I will I will have this comment and developed a the issue with such approach. If you will have any different 5 years, less people is updated, ok looks good, everybody agree, yeah yep, yes, cool. We did four or five issues today we are out of time for our first group.

A

Let's keep on tracking those issues if you'll need any help. We always in the dr. slack I, will schedule next session, maybe next week or maybe on weekly basis about, but let's keep.

C

Doing well for future to make.

A

A

Particular window everybody was too busy to sink for one hour, but I will make it to the next time and one more thing that I would like to also share. So, as many of you know, we have open source at magenta tooth comb. We share consist of magenta magenta source project. For today we had mentioned to our tools and magenta cloud ochre projects, so you can find them here as well as other projects and also we will update the community calendar with events.

A

I have a chance to at today's grooming, but for sure I will head for the next time. So more people be aware of our great women sessions. Thank you guys for your time. Awesome.

D

Thank you. Thank you.

A

B