 Good morning! Good morning, how are you doing? I'm doing quite well. I'm relearning an important lesson in life which is that there comes a point well before you normally realize that where if you keep coding you're just going to make a mess and if you just go to bed and get up in the morning it'll all flow. I had to do the same thing last night. It was like 1 a.m. I didn't realize it was 1 a.m. at the time and I thought whoa this code isn't going well and I have to be up early in the morning. Well it's also part of a I've mentioned a couple of times I've got rules of thumb which rule of thumb for me is always if x the probability of y is much greater. If the go-line reflect package is starting to look useful to you the probability that you're doing it wrong is extremely high. That is true. I mean don't get me wrong like there are places where reflect is exactly the right tool for the job but 90% of the time that you consider the use of reflect you were badly in the weeds. Yeah I need to work out this gRPC thing as to why are like I know the connection works because I see the old I'd seem to be responder work. The new one I just get I just get a connection reset over a unit socket and it's really annoying so I need to work out what's going on. Yeah the first thing I would go to look at is go look and see you know what you're getting back as a certificate so. Yeah and the certificate seems to be okay. I'm getting back a certificate but it is possible that um perhaps the actually no that that couldn't be an issue because I've I've said the same name is uh yeah the next my next step is I'm going to stick the spire uh client into it and then I'm going to pull the certificate and actually look at it because I'm just getting a stream of a stream of bytes out of it right now and so and as as much as I want to say that I can read bytes off the stream I can I can have a certificate off the screen sorry you're on mute. So funny story about that long long ago maybe two decades ago I was doing a lot of work in the wire chart community the sort of network analyzer the thing that it goes packets and I had a colleague of mine um who got paid to go take six weeks and write a disector for the DOCSIS protocol the thing that makes cable work and it was because he worked in our support organization and his manager had become alarmed that his engineers could site read hex stumps of DOCSIS. Yeah I used to be uh capable of doing things like that a long ago it's just I'm well out of practice. Well and also like let the machines do the machine work reading hex stumps is generally speaking machine work. Yeah this is that moment when you want to shave off a little bit more time so you you learn just to cut the machine out or you become part of the machine. Yep. Hey hi everyone. Hey. Hello. Hey. So let me go ahead and add to the chat link to the meeting minutes so folks can add themselves to them. Uh remind everyone we are in fact being recorded and we usually start about five after to get folks a chance to turn up. Does anyone want to share the meeting minutes so we can talk to them together or the agenda? Thank you so much. Much appreciated. Should we get going Frederick? I think that we should so welcome to the next network service match meeting. So we have this meeting at every 8am pacific on Tuesdays. Please add yourself to the attendee list if you have other things already and we also have a meeting every other week at every and for at an Asia at an Asia friendly time. We also participate in the CNCS telecom user group meeting which occurs every first and third Monday at 8am and 3am pacific and we also participate in the CNCS signal network call which occurs every first and third Thursday at 11am pacific. The details are in the meeting notes. We have a new event that popped up. So I am going to be part of a panel along with with the AVP of AI technology in Anthem and with the chief technologist of HPE and we are going to talk about zero-trust networks or not networks. Zero-trust based authentication in healthcare with a focus on on specific and spire and so part of the reason that I am I am in that space is because I do work with healthcare organizations and simultaneously this is also on specific and spire of which NSM uses that as a as a core underlying technology. We also participate we're also going to participate in HPECon and CognitiveCon Europe which is going to be in the RAI Amsterdam assuming that the COVID-19 efforts are sufficiently far enough along. And can you scroll down a little bit? Thank you. We also have an NSMCon at QCon which is going to occur on August 13th with a larger room with a whole set of speakers that you'll be able to listen in on. We also have ONES North America Europe which is going to be in September and ONES Europe will be in Antwerp, Belgium on a date to be determined and QCon and CognitiveCon North America will be on November 17th through 20th. Those dates have not been affected. So in terms of announcements there is an announcement that is not listed on here. So we have a new repository that has been added by Alexander Menendez from Red Hat and that is the NSM operator. So you can go to the NSM-operator repo within the Network Service Mesh organization and feel free to help contribute there. And one of the things that we are in the process of doing is that for every work for a variety of different repositories we're going to start looking at a per repository committer and so we will be able to give people like Alex the, in fact he already has, commit access to the NSM operator repo and we're going to be following the same the same pattern. So for example with the fan app plugin that I recall was Denise and so we'll go ahead and and start adding commit level, sorry repropository level committers in the near future that will be able to help us that will be able to help us with with each subproject in NSM and so congratulations to both of them by the way on being subproject committers. Congratulations Denise and Andreas. It's epic accomplishment and much much appreciated. You both have done a lot of work in those areas. Yeah and this also marks the new stage in NSM's life because we have moved beyond the the mono repo and simultaneously the project is a sufficient size that that it doesn't it doesn't make sense to have so did you have everything gazed upon by by all of the by all of the top maintainers and delegation is fantastic especially when you're able to trust the people that we're delegating to and this community is fantastic for that. So with with that we also see do we have Ashley on the on do we have Ashley on the call so we can go over the social media stuff? Yes I am here. Oh you have a fork. Thank you. Hi everybody. A quick update with regards to network service measures social media over the last week. As far as Twitter goes we have gained an additional eight followers so that's definitely the biggest jump that we've had over the last month or so so hopefully we are back on track to have a larger following weekly and as far as those that we are following that's an additional two accounts and then a total of 17 tweets and retweets. Those include general call reminders the CNCF weekly webinars two that were worth noting this week one of those is learn how best to use technologies like YouTube, OBS and Twitch to engage with your communities thought that was more relevant now than ever before and then as Fred was saying earlier on the event that he will be presenting and that is on the 29th zero trust-based authentication and healthcare so be sure to join those if you are available. Other events got NSMCon schedule out there again and then a lot of events we promoted the latest event keynote and schedule announcements for events coming up as well as promoted OSS which has now been switched to a virtual event at the end of June. Then general tweets so general retweets from open source way and open source headlines for the past two weeks just some catch-ups over there and then from kubernetes the difference between api gateways and service mesh. Then with regards to LinkedIn and additional two followers of the last week with the same original content posted there as in our Twitter account and then the plan moving forward some of the same general retweets podcasts blogs that come up and then start ramping up for NSM as we start getting closer to that event so that's it on land. Fantastic and thank you and thanks for covering me on the time and location of that webinar I realized after I said it that I am not stated where you could actually go see it or when. And so on to the main on to the main agenda so we have as a topic we have the NSM operator. I don't think we have Alex on the call today so I'll have to make sure that he is aware of what's going on out of hand but so in terms of the in terms of the operator I think we've gone over the main gist of that that now exists it's now within it's now an official repo we're in the process of going through and refactoring all of the packages so that they're appropriately named because it's written in go and the and go likes to hard code the package name along with where the git repo is and so we have to refinish refactoring those. Another thing that needs to be focused on is we need to get the CI system up and running so that that way that we're testing the operator making sure it runs through through a cloud test or whatever test infrastructure is set up for operators and also ensures that we publish the images in a way that is easily consumable within the within the docker infrastructure along with publishing images to the docker hub so those are all tasks that are currently in process and when we are complete with those tasks then we will make another announcement here so that that way we can get people to to start trying out and start using it and to also be able to point people to contribute into these areas. Another idea that I had as well so NSM itself from a from an operator perspective is designed in such a way so that if it fails or if you don't have to worry about startup time of the individual components but I think one another area that will also benefit in this and we can use the NSM operator as the starting point for this is eventually the life cycle of the of the of the nse's of the endpoints themselves will become important to look at so if you take a look at something like let's say how like a firewall that I bring up that firewall will have its life cycle describes is NSM up and running is my database that's keeping track of all the rules running is and is it properly is that database properly backed up and restored is my and then only then bring up my firewall and monitor my firewalls performance so that I can auto tune auto scale up and down and solve certain types of problems in a automated way and so part of the part one of one potential path that we can take the the operator is not only from managing NSM but to have it set up so that we can have tooling in order to manage a cnf or or other endpoints that get created that are that are within Kubernetes and so of course this only applies to things that are hosted by Kubernetes if you want to try doing something like that in an open stack or or with physical devices you have to follow the best practices for those but it's just just to give you a taste of like some of the thoughts that we have behind the operator and why why the operator is an important project with that I don't have anything else is there anything you want to talk about it I think I'm good yep I think I'm good I've been very hands down this last week writing code so sometimes too much as I mentioned I spent probably three hours digging myself a nice deep hole last night that didn't need to be dug yeah and just on that note I'm currently working on getting with the a end-to-end working example on the using the new SDK and to be able to walk people through that so has thought as that occurs once and once we have it up and running and appropriately documented then we can have a run-through of that so that we can see how the SDK works how they can start building their own NFCs on it how it integrates with the data plan and so on and so we'll start to do we'll start to do information sharing efforts so that people are aware of of what and how it works oh is if is there any other items if anyone wants to talk about otherwise we will yield back time okay so please go and register for the webinar please join us please invite all your please invite all your friends who you think will be interested in this in this topic and with that thank you everyone for your time we'll have a wonderful day and we will see you all at the same time next week bye