Cloud Native Computing Foundation KubeCon + CloudNativeCon Europe 2018 (Copenhagen), 14 Nov 2015

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: VMware SIG Intro – Fabio Rapposelli & Steve Wong, VMware (Any Skill Level)

Description

Want to view more sessions and keep the conversations going? Join us for KubeCon + CloudNativeCon North America in Seattle, December 11 - 13, 2018 (http://bit.ly/KCCNCNA18) or in Shanghai, November 14-15 (http://bit.ly/kccncchina18).

VMware SIG Intro – Fabio Rapposelli & Steve Wong, VMware (Any Skill Level)

About Fabio
Purveyor of all things open source, loves distributed systems and solving complex problems. Renaissance man and human Rube Goldberg machine, Fabio is responsible for many of the Open Source integrations between Vagrant, Docker and VMware. Frequent speaker at conferences such as dotGo, DockerCon and VMworld.

About Steve
Developer interested in containers, storage, virtualization, IoT, machine learning, streaming data analytics, and cloud native application technology. Active in Kubernetes storage community since 2015. Chair of Kubernetes VMware SIG. Frequent speaker at open source conferences and meetups. Formerly involved as a dev of several popular products including vSphere, Avamar, Wonderware, medical devices, SCADA systems.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.

A

I'm Steve Wang from VMware, based in California and I'm chair co-chair of the VMware sake, my co-presenter fabio here please prison he's suffering from jet lag coming from Italy I'll. Let you.

B

Introduce yourself.

A

C

Fire up ezeli work with with Steve VMware co-chair of the VMware cig. Just you know, she's just getting started with us sake, so we wanted to get you here today to you know, run an introduction on what the cig is all about, and.

A

Let's get started here so first of all, I'm not going to make any assumptions, so I was just in a similar intro session for the storage cig and somebody in the audience had a question at the end.

A

What is it cig so just to make just to calibrate everybody on many open-source projects, including kubernetes, when these get big the project gets organized into special interest groups, and this is just to accommodate an aspect of human nature and communication that you know once you get over a certain size group, it's really hard to expect to have communication and it's better to break activity into focus groups to accomplish tasks and maybe have the other size where it's actually possible to recognize people and know their name and have you know real interactive activity.

A

So that's the purpose of arranging SIG's on on kubernetes. These SIG's are intended not just for developers, although some of them have to have different mixes than others. So they're intended for participation by both the developers writing code, as well as users, documentation, writers, training, authors, so they work best when you actually get a variety of contributors.

A

What is the VMware say again specific? Well everything about this new because it just started a few weeks ago, but this is focused on improving the kubernetes experience for users running kubernetes on top of vmware infrastructure.

A

So what would you get out of it if you're one of these users? Well, you can expect to get coaching on best practices, problem resolution and it's an opportunity to participate in feature roadmap. You know, as you use this or look at using it unlike commercial software. The way the open-source arena works is that you have a direct opportunity to submit your features and discuss them with architects and developers for if we have developers in the audience and I see a few.

A

This is a forum to plan our activity to organize correct, coordinate and prioritize, because we need to typically synced up with kubernetes releases and that the quarterly aspirational release cadence and as we go through this release cycle, this SIG will become a forum to monitor our progress towards a successfully keeping on track, to align with the kubernetes release cycle and to engage in collaborative development, which means dividing up the work and making sure that we're going to fulfill whatever promises we make to the larger kubernetes project.

A

In terms of getting things done, when we say it's going to get done, how can you participate if you're, not a member? Now? The first step is to join the Google+ group by the kubernetes community standards. This isn't an option because there are many shared documents and being a member actually links your ID to give you appropriate access to be able to edit documents and get informed of activities. So the link is here and by the way, this presentation has been already uploaded to that schedule becan.

A

So you should be able to get this later, but course you can take a picture and I'm gonna close with this slide at the end too. So, if you're not in there, if you open this page there'll be a blue join group button, it is localized.

A

So if your native language is not English, it might say something else, but for me it says, join group second step is to join the kubernetes slack channel, so there's a vector to join the overall kubernetes slack if you've never used slack, that's divided into channels, and there is a dedicated channel for the VMware sake. So you would want to do that. This is a great venue for just asking questions and getting visibility of those questions.

A

I'll caution you that people in this group are dispersed worldwide, so you can ask a question in there, but don't be surprised if it doesn't take a day cycle or on a weekend a couple days cycle, because people who participate in this aren't necessarily located where you are so. An interesting aspect of this is that we have contributors in many time zones in the world.

A

Then. Finally, we have bi-weekly zoom meetings by bi-weekly. This means every two weeks not twice a week just in case there's any confusion about that, and these are synched apologies to the European audience I. My co-presenter here I think has mixed opinions about this, but kind of to align with the Western us dominance of the cube. Karina's project doesn't bother me by the way I live there, but 11:00 a.m. Pacific and whatever that translates to in your time.

A

So we have these meetings and these meetings are both. The video is recorded, as well as the notes taken during the meeting and there's a vector for you to influence the agenda on the meeting. So at this point, I'll turn it over to Fabio and the best way to get started is to probably just open the notes or the meetings. So.

C

The older meetings know the mini notes are in a shared Google Doc. So, as Steven mentioned before, if you join the Google group, you will automatically get added editing access to this document. So once you're part of the group, you can come over here and add whatever topic you want to the next agenda, so, for example- and this is a living document, so this is this is getting edited. You know during especially during the zoom meetings, so the next meeting is next week, so may 10th for a European audience its 18:00 UTC time.

C

So you can. You can translate to your own time zone, so it's usually around 8:00 for sons or European, which is my time zone. 8:00 p.m.

A

Sorry to interrupt, but I wanted to bring up one other thing that aligns with the governance standards for COO Bernays. So these meetings are public and recorded. So whether you like that or not that that is the standards of kubernetes.

C

Yeah, we usually make an announcement before starting recording every time, but just in case, if you're not feeling, okay with you know showing your face in the meeting, you can either just listen. Stop your video. Do not talk it's fine, but if you're, if you want to engage you're gonna be recorded, that's the only thing you know privacy matters right, so uh just be aware of that.

C

So we have agenda here and usually at the beginning of the week we start you know populating the agenda, but if you have any topic you want to discuss, you should be feel free to you know. Come here. Add your item at your attic to the discussion, part or add your item to something one of these custom. If you want to propose I, don't know a new feature or something most of the time.

C

What we like to have is, if you want to discuss a feature or if you want to discuss an issue you have, you may want to file an issue on the kubernetes get up page first and then reference that number in the meeting notes. So we can discuss and have you know something already in there I'd.

A

Say here's another thought: Fabio I think I've encouraged people. If you want to. You can add your again item a minute before the meeting starts. But if you'll allow us a few days, we may be able to go, recruit people who are more familiar with that issue. For you, because Fabio and I know a lot of people working on the project, so I'll just throw that out. There I.

B

Just wanted to go back to the slides and where they are the next tab over, though okay, where is it over here there you what happened.

C

I'll live it I'm. Sorry, I use a Mac and I'm sorry there you go you saved the day once again, so they were saying, meetings are recorded. So if we go to this link, there's a playlist that lists all the three meetings that we had so far as you can see, they grew in time. The first one was just half an hour. We usually booked an entire hour for the meeting.

C

We don't necessarily use the entire hour, but sometimes there's a demo and there are more questions than usual. It can stretch to an hour so the last meeting we have last week. In fact it's an hour long. So there's a good demo if you guys want to check out so look at the look for this link in the deck check out the recordings.

C

If you're interested, there's a there's, a bunch of things we have discussed last week, there may be of interest for anybody who runs kubernetes on vSphere, so make sure to check that out and see if I can start a presentation again. Okay and as I was saying, we are seeking content from you. So if you're, if you join the sake, you're a group member, you can propose any agenda items as I was saying you just open up the document. You go there. You add your item to the to the list.

C

You make sure you attend and we can discuss that item at the next meeting. So anything that has to do with the integration of kubernetes nvm Platt VMware platforms in general, so not necessarily just vSphere. So even if you have an issue with mini cube, infusion or meaning, Kuban workstation feel free to join us sing and talk about that or if you have an issue with vSphere club, sorry, a V cloud provider and are you using feel free to join and talk about that? So it's not just for vSphere.

C

It's for all the humor platforms as a whole, so in saying deployments on premise on cloud doesn't matter if it involves anything that has to do with VMware feel free to join and ask questions or discuss, and if you have any type of best practice that you find out- and you want to share with a larger group, you're very welcome to do so.

C

What is not appropriate for the sake? So, first of all, we have a code of conduct which is the same one as the kubernetes project. So we just inert the code of conduct from kubernetes. What is discouraged I want to say it it's completely inappropriate, but discussing anything that is not, that is a bug or or any or a new feature request. That is not an existing issue in the get up tracker. We may not want to discuss that because most of those information end up being just recorded in a video stream.

C

So it's not as easy to remember all those details, so we prefer to have that file beforehand. So before discussion, you file a github issue. We discussed that we tracked with comments in the issue. So everything is tracked in a single place if you have a problem with the VMware product that has kubernetes in it, if it just for, if it's something that has a more broader scope and it's just just a product issue, then it's fine.

C

If it's a product issue, you may want to refer to VMware support and not you know, come to the sig and ask for a resolution of the problem, because we don't we're not a support group, we're more like a community end of that group and there's a topic that is not covered by VMware, so it doesn't have to do with VMware, there's, probably a more specialized sig that you might may want to refer to. I would say that an exception, for this will be something that has to do. That is a cross sig issue.

C

Maybe it's an issue with networking, but it has to do with VMR. So it's a it's a specific networking issue that you have on a VMware platform. Then we will be. You know, delighted to you know a sponsor that issue and work with the other six to resolve the problem. Okay. So if you have a networking problem with V with VMware feel free to join us to discuss that, and we can, you know, facilitate the cross sick communication and resolve that issue.

C

Plans so initially the first, you know project that the sig has in mind is to start working on a Rijeka tech, chure of the cloud provider for vSphere, so vSphere. This free Club provider is right. Now in three inside kubernetes, core kubernetes itself has been restructure, so criminal wants to remove all the provider dependent code as in kubernetes core repo in two separate out of three repos and the cloud provider is the first attempt to actually change that the model. So we have a you know we have.

C

As I was saying, we have many other six that are interacting with the cloud provider so also saying: network node, scheduling, storage, testing, many others, so those topics as a whole are owned by different SIG's. But if there's anything that has to do and it's a cross sick problem feel free to talk with us, how our plans for one eleven are actually pretty small. Unfortunately, we as a Sega came out a little bit late for the 111 feature freeze.

C

So we have a couple of features we want to get in 112, but they're not making the cut this time. So for 111. The goals that we have is from a design perspective. We wanted to design and scope the word or is required to move the cloud provider out of three. We want to have a design discussion, we won't have an execution plan and we want to have documentation around it.

C

In fact, there's there's a k, EP proposal out there, which is under review right now to kick-start a sub project in the sig that that's the project will own the cloud provider code, we'll be saving out of three and hopefully we'll. We want to shoot for an implementation of this club provider out of three four one. Twelve another thing we're working on is given that a CNC F has this nice cross club initiative, which you may or may not heard off.

C

I just want to bring up the dashboard here, so you can see what I'm talking about, maybe okay. So this is a nice dashboard that shows all the projects under CN CF and there's a you can see. There's a platform here so there's many platforms and there's a release: a stable release on ahead release and it's being deployed on every cloud here that is available. So you can run CI jobs and test all these software's here. So there's kubernetes, obviously, but there's also from e theaters Cordy and a swindle incurred own app and so on.

C

So we want to show up here, so we VMware has decided to sponsor some capacity in order to run this jobs, so we're working with Kross cloud and CN CF to make sure that VM are shows up here.

C

So this is another project that we're following it as a cig. It's like it's a it's just getting started so, if you're interested in looking at this, this here is actually being provisioned through terraform. There's a lot of interesting stuff happening in in the backend and it's all open source. If you're interested in looking at this problem and join the cig and work on this feel free, we're happy to have you and.

B

C

And we have mini cube support for VMware fusion and were station. That is actually right. Now, it's out there. The pr is being reviewed, it's just blocked by the CI system, because you know kubernetes and cnc. F12 have a CI system in place before actually merging new code into the repo. So once the CI is up, this will be merged and it will be show up in a next version of mini cube.

C

So was talking about the cloud provider, so the refactor of the cloud provider is some sort of like I would say: tonic shift in kubernetes, because the current law provided structure. As you can see. There are many touching points here, so the cloud is sitting here. The platform has many touching points with cue controller manager, API server and the cubelet themselves.

C

So the refactor that is, that it's happening and part of Poly has already happened inside kubernetes is to move to a model where there's only a clock controlling manager, which is some sort of separate binary. So it's not compiled directly into any of the kubernetes binaries, and this takes care of talking to the cloud and implements an interface that cue controller manager and it could be a VIP server, can can understand and talk to the controller manager.

C

So our goal here is to create a clock controller manager for vSphere, but it's that will be sending all of three and not inside the kubernetes kubernetes repo- and this is the CNC F cross. Glassy-Eyed and I've just shown you so we're looking forward to have a vSphere as a first platform for VMware here to show up and as we're saying before, we are hiring and then we're looking for people that want to join the sick, but not also as just a member we're actually looking.

C

You know actively looking for end-users, the one that understand kubernetes, that maybe you started working with kubernetes a while ago and they're running kubernetes on vmware platforms. If you're interested in you know getting involved- and you know be a co-chair of the cig- please talk to us join the meetings. We can definitely talk about that.

C

We're looking forward to have an end user representation in the in the chairs and if you, if you're interested in what the chair role should be, you can find a link here in the in the slides, and this is a recap of all the various links. Do you want to add something Steve or we can open up the floor for questions no.

A

I think you covered it. Well, so does anybody have any questions or ideas suggestions, throw it out there just like a cig meeting.

B

C

C

Okay, yes, so there are many issues. May.

A

Be repeated because the recording.

C

A

C

Would say that I will summarize your question with. There are several outstanding issues in the club provider. Today they make, you know using the club provider in vSphere, not a pleasant experience right, okay. Yes, we are aware there are many issues. In fact, the reason why we're trying to bring this is to put some governance around. You know working on a club provider. Otherwise it's just you know some code that is sitting there and somebody from you know. People have issues. Somebody finds a bug, somebody files a bug, and maybe somebody will fix it eventually.

C

So the idea is to provide some framework around it and own that code in a way where we can triage bugs and we can discuss them in the open with you know, during the meetings and so on. So if by all means, if you have any issue with that feel free to file a bug, there's actually a label now in the kubernetes repo. So you can, you can run a command in the comment, slash sig p.m.

C

where and the issue will be tagged with a VMware label on it up and it will show up in our dashboard, which is basically tracking all the issues that have to do with VMware I.

A

Think we had a question in the back.

D

I'm not too sure if you cover this I was joining your group and everything in slack, but what's the best way for a newcomer to join on board with VMware cig like group, is it just it come to the meetings and start to learn? Well,.

A

The first step is to join the group on the Google+ group, so it's just find that URL, which was in the deck and just click, join I, did.

D

A

And then yeah I would say if you want to be interactive, just join the zoom meeting and you can start by listening. If you really want to catch up I, don't think you have missed a whole lot because we're so new, but there's three recordings up on YouTube and if you want to decide whether it's worth investing your time, maybe look at it. Although I'd caution, you that the first one we were still learning, we really are one of the newest SIG's out there. So the first meeting- maybe wasn't all that representative.

A

So it was kind of a bunch of insight, talk on how we should get organized and then the the they're getting better. So the last one is the one I recommend looking at there were some questions by actual by an actual user about best practices, and you know that's how you could get involved if you're looking to get involved as a developer, we'd be happy to take resource there too, and if you're, really, you know trying to get started in the career. I think the best the best jobs to take on are actually volunteering.

A

The sign up for documentation issues because, as you improve documentation and write collateral material, you force yourself to learn kind of a broad swell swath and really get the big picture and learn it well. So that's a great way to get started that I typically recommend, because we occasionally have people who are interns or students who want to get involved with this. So it kind of depends what you're looking for, but those are all ways to get involved.

E

Hi, so you guys focused on running on vSphere or on V cloud or on cross.

A

E

Off premise, or where are you going first? What's your all.

A

Of those really it if.

E

You'd gotten of all of them at once, wait: where are you gonna? Stop? No.

C

It's going to be vSphere right now, because it's I would say it's the one that has many outstanding issues. As I was saying before the cloud provider is, there has been there for a while a game, significant technical depth, and that's why we're going after that? First, because it's out there, people are using it and it's not a pleasant experience. We want to fix that. So that's why we're gonna yeah we're going after that. First.

A

We don't have an option: I mean kubernetes itself is really tech ting. So you know we could get away with not addressing it for a couple of releases, but eventually I have to assume somebody from the some of the overseers on the kubernetes steering committee are going to come after us. If we were to ignore it, and now this is speaking that that's our first focus for the development community aspect of the kubernetes thing.

A

I would say that, right now, if you're, a user coming with issues, feature requests we're all over we'll take anything right now day, one like I'm, not promising, we'll resolve those issues but go ahead, and let us know now, because I think we can I think between Fabio and I.

A

We've got pretty broad contacts and we we can do research and get it kicked off so I'm willing to take on the whole big picture of if it scoobert it has to be kubernetes, and it has to be running on some VMware infrastructure whatever that is, but it could be public cloud it could be on. Purim could be hybrid where you've got some of each could be vSphere. It could be workstation we'll take it all anything to add. No.

C

I think that covered pretty much I mean we're all about the Emerald platforms in general, so not necessarily tied to vSphere. But obviously these fear is a big part of it right.

A

Yeah anybody else got a question and comment.

A

Okay, it looks like we're ending a just a slight bit early. You can get some lunch, but we'll hang around. If somebody wants to discuss anything, you didn't want to talk about privately and I'm here all week. You can find me or ask somebody in the VMware booth to track me down, but thanks for coming thank.

C