Hi everyone. This is Vincent here. Today we are going to discuss our involvement in a project called Open Source Climate and in particular we'll be covering how we help building a climate-related data platform using open source technology and a data mesh architecture approach. So, in this agenda we'll spend a bit of time to go through the context, what problem we are trying to solve and also why open source as an approach to solving climate data issue. And of course the focus of the presentation is going to be on the platform architecture, try to explain how we are approaching the climate data problem and why it's a novel approach to do so. And Eric will spend a fair bit of time showing with some demo some of the platform capabilities. So first, I actually work in the financial services team and quite often I ask the question, why is financial services critical to the climate issue? I'm just back from Glasgow where the 26th climate conference happened in the past two weeks and actually one big change, an important change in the way the climate problem is now being approached is the involvement of the corporate sector into the resolution of the climate problem. So if you think about it, what's the way for us to transition to a net zero carbon emission pathway is really to motivate and encourage corporations to all make effort towards this direction. And if you start thinking about it, a financial sector and in particular the banking sector being responsible for about 90 plus percent of financing to corporation is actually extremely important to finance a net zero pathway. So what's interesting is for financial institution, climate in itself is actually a challenge, an important challenge because investments that these institutions are making translate to potentially climate risk. Let's say you are financing energy production and you start to lend money for the next 25 to 30 years. It becomes extremely important to understand how climate risk could affect the business that you're investing in and obviously their ability to service the loan that you are making. And that means being able to understand financial risk in terms of climate drivers from the physical risk point of view. So what happens if an extreme climate event tornado or if slowly rising could actually end danger of physical assets that the company you are investing in actually possesses. So a financial institution attention to try to model climate risk to secure their own investment. And in addition to this, we have now regulator but realize that the public sector itself is not going to be on its own able to really drive very significant climate change and requires the help of the private sector and financial institutions are very key to this because they are the main financing institution. In addition to this, all of us as investor, we are increasingly aware of what climate represent as a risk to our planet. And obviously, we are also starting to put pressure on financial institution to disclose the nature of their investment and make sure they invest in green business. So now let's look at the West climate. The purpose of West climate in the grand scheme of things is to help the corporate sector as well as the financial sector to have an open collaboration opportunity around one main challenge in modeling climate risk, which is about acquiring data. And for this, we are really three main tenants to really this approach. The first one is in the past, a lot of financial institutions or any sort of NGO or non profit that work in the field of climate data tend to try to solve problem on their own. We believe that using an open source approach and an open source community to actually collaborate to have multiple stakeholders invest their intellectual property and share the cost and burden is actually a more efficient alternative. And with this open source approach, we basically look at building mainly two capability. One is the global data commons, which is a curated library of public and private data for climate, which is what we are going to cover today, and also helping institutions to build scenario analytics across the different climate dimensions. Why is it important to adopt the community-based open source approach is mostly because we want to be efficient at solving problems and share the solution and obviously try to solve the climate data problem faster if everybody is kind of pulling the rope in the same direction. Running this open source means we have a shared and structured governance around the project. So the key industry player can agree on what main data challenge they have and what is the focus of this engagement. We also create a very high trust collaboration structure between player. This includes some commercial data player who are actually sharing their data on a kind of what we call pre-competitive basis, which means that they share the data with us to be able to train new data models and analytics model and then spread them across the industry. And of course, from a licensing point of view, open source code and platform design across the community. Now let's focus on the climate data challenges. There are mainly three main challenges that we're trying to solve. The first one is about data availability. Interestingly, there are really two challenges here. One is there's actually a huge volume of data that is generated by the industry and the data is extremely distributed. So it's very hard to actually connect data to each other. At the same time, although data volume is high, certain regions or certain industries have a lot of either insufficient granularity or limited coverage. So there can be missing data. So one example is you could have public utility disclosing energy production and CO2 emission for energy provider in the United States, but there is no such data available for China. So you may be missing some geographic or industry data. Now, even if you have the data, another problem is because distributed is extremely hard to compare across different sources because they may not follow the same disclosure standard or they may not follow the same data format. And last but not least, another problem is data reliability. As you see the data for this model, you want to make sure that you understand how the data has been produced. So one issue typically is there are a lot of community out there that build their own model, generate data, but nobody is able to understand transparently how the data that has been generated could be trusted. So let's move now to the architecture. So the idea is we have an extremely high number of potential data provider and we want to help by building a platform that solve this problem of data availability, comparability, and reliability. For data availability, our approach is to use a self-service data management platform. So what we are doing really is to make a collection of well integrated standardized open source tools for the community to ingest data, process data, and distribute data. So the idea here is to standardize and make this tooling easily available for data scientists. So typically people who don't have necessarily the knowledge of how to install the infrastructure behind it, and then they can start to build those data integration on their own. For data comparability, we use a data mesh architecture, which essentially means that we empower different data domain owner to solve the problem on their own in a distributed and federated way. So they can build their own pipeline ingesting data, processing data, distributing data in a fairly independent way. And they basically own data pretty much like a product. The life dimension is reliability. And so here this is interesting because typically in distributed system you get a lot of agility. But then the problem can be how do you ensure that people follow a certain set of standards and also respect certain governance and security around data. So here we use a federated governance approach, which pretty much is twofold. The first is we treat a data very much like code. So we use processes that have been used in the open source community for years. So they are extremely well mature process, well proven to manage and version code. We are extending this process to the data itself. So data sets are managed like code. They are transparently generated. Everybody can see how the data is produced and shared. But at the same time, because we are certain governance issue around the data, we also manage access control and data governance in a central way across all the different domains. So this helps us to turn what I call a data mesh into a data mesh. We have an extreme number of heterogeneous data source and data contributor. And instead of building yet another source or another database, what we do is we are actually standardizing the way that people now consume the data. We are federating across data source and we are standardizing the tooling and the approach to ingest, process, and distribute data. So I will now leave the next section to Eric to present on how we are actually using open source tooling to do this. And from the Red Hat perspective, we are really building on an engagement, which is actually an open source project, but it's called Open Data Hub. And Open Data Hub is really an AI platform powered by open source. So we are literally selecting multiple upstream projects in the open source community and putting together a platform that can easily be deployed by data scientists across the globe to build their own capabilities. Eric? Thanks, Vincent. So yes. Oh, I get to show my screen. Okay. I was expecting Vincent to drive. So riffing off what Vincent said, there's a couple of things to say about Open Data Hub. One important thing is it's an open source downstream in a very typical Red Hat-ish open source downstream way. In this case, it's a downstream of Kubeflow. And we are using it internally and externally as a reference architecture for machine learning workflows on Kubernetes. And lastly, it's federated, which to say that the actual components are selectable and mixable. And also just by virtue of Kubernetes and OpenShift platform, it's very easy to actually add other components to the system if you want to. The coverage of the available tools is actually quite good in both dimensions in terms of process, all the way from business goals through data preparation, model development, deployment, and then finally monitoring. And then along the axis of personas that similarly covers use cases for people, business leaders, data engineering, data science, all the way through app development and operations. I emphasized in this diagram a few of the tools you're going to see later today, superset for dashboarding and Jupyter for both exploratory data science and also pipelining. And then Trino, which is a great example of the advantages of a federated architecture. Trino is not actually a formalized component of Open Data Hub, but it's being deployed in quite a lot of our use cases, including the data commons for OS climate. So again, Open Data Hub is leveraging everything that's good about open source, a community-driven upstreams, in this case in the artificial intelligence machine learning workspaces. We are maintaining the actual cluster using another Red Hat-affiliated project called Operate First, and I'll show you a little bit more about what that means later. But fundamentally, what we're trying to do is take the popularity of GitOps and extend that to, whereas Open Source has traditionally been excellent at accumulating knowledge about writing software, we're trying to extend that into Open Source for accumulating knowledge in open communities about actually operating the same software. So you're going to see that the data commons is actually being managed via Operate First. And so these two tools are coming together into the OS climate data commons, which Vincent has been describing. Again, I'll be demonstrating a few components of that later. And so the goal is to be able to manage data as a product, just like we manage software as products. And we're hoping that this architecture can show that we can service all the different use cases in personas all the way from raw data providers to data engineering and structuring. And then to be able to actually do data science and maintain the quality of the results. And we're trying to achieve this by treating data as code, just as well as we're treating data as software. Now, what does that mean? It means that we're federating very disparate data sources with repeatable pipelines that run in orchestrated cloud environments. And so what that means is, if you want to update your data, you actually update the software that ingests it or processes it. And we're doing this all in Open Source. And so the entire community will be able to participate and understand exactly what software is being run, how it's being versioned, how it can be improved. And I'll hand it back to Vincent to talk more about how we're leveraging this architecture. Sure. Thank you, Eric. So in terms of platform perspective, now looking at, you know, typical flow and capabilities that are required in building, you know, data pipeline and what component of a data science platform are required. As explained by Eric, we are leveraging heavily on Kubeflow as a machine learning platform. And it provides a number of components that are, you know, used in terms of building data pipeline, model training and model deployment and serving. A lot of the work is done typically on Jupyter notebooks provided on a self-service basis in Jupyter Hub. Both notebooks can be stitched together into end-to-end data pipeline, you know, but are you using Alira? I'm going to think I'm on the wrong screen. Okay, that should be better. Sorry for that. And however, you know, we'll see later when I cover this topic is there's still a number of components that we're trying to add to the platform to provide better manageability across the community. And these components are really around the management of experiment and data experiment as well as the metadata associated with it. So we are now looking at project Pachyderm as well as data from LinkedIn to have a better automation around the metadata management of all these data streams. So in terms of data science roadmap, and please don't go into the detail here, this is really just to show that we do have currently a working platform and we have a number of streams in the Western community that are already building data pipelines for various dataset and data sources. However, we still have a lot of work to do in particular in the domain of metadata management and also trying as much as possible to automate some of the data catalog management. One of the big issue once you produce data from the community perspective is to make it discoverable. And really one of our objective in the move to come will be to try to create kind of catalog automatically for people to easily discover the data across the community. Now let's move to another set of problem and really more like the governance side of things. Here we are looking at different persona. Typically one of the challenge for data engineer or data user is the multitude of different data source and the difficulty to merge them and use them together to kind of make sense of the data. And typically this needs to have a common referential to do so. So that's one kind of first problem here that we have to deal with. Now the challenge in this is a number of these like datasets that we consume may be public but others may be competitive datasets provided by a commercial data provider which may be okay with the data being used to improve and tune certain data or risk model but they're absolutely not okay with just distributing their data totally in the open. So they want security and compliance to be managed. So I've explained it before what we're trying to do here is to create a single layer of compliance and security across the pipeline. So what this diagram shows is basically a kind of very high level skeleton of what the data pipeline typically could look like. You have some primary source of data which is nice but not necessarily usable as it is by the community. And then you try to merge it with some kind of reference dataset that will help people make sense of the data. So one example of this is let's say you have carbon emission of factories in the United States. Now you don't necessarily know which company actually owns this factory and how to actually aggregate all this data into a way that is meaningful for say an investor which will be looking at both emissions for specific maybe public company and also try to understand how these emissions relate to say the benchmark in the industry. So is this company doing well or not well? So for this what happens is there's a lot of the processing that is done to basically integrate dataset together but then when you integrate dataset and once you reach step number two in this diagram you are basically building your own new dataset with your data model and that needs to be documented. So the first thing that we're trying to do here is to build a catalog service that will keep track of dataset version, dataset metadata and also what we call pipeline metadata which is every time you generate a new dataset with a bit of code you want to keep the code version and you want to associate the data that is produced with the latest version of your code so people understand how the dataset is actually being built. As you do so as you can imagine a lot of dataset get produced. Now the question and challenge is how do you make sure that when data needs to be governed and some security access needs to be managed we can do this consistently. So here this is where a single layer of data federation and security based on Trino actually allows us to build a single logic of data access across multiple datasets. So right now we are using Trino to do exactly this to make sure that at the data element level we have consistent security at any point of the pipeline. So let's say that some of this data of this primary dataset is actually commercial and is restricted in access we can manage and make sure that the access is consistent on the primary dataset layer so the source data but also when the data is distributed. So that is extremely important. So this is what we have today but something that we are still working on is kind of going forward we want to be able to manage access at the dataset but also at the metadata level. So you know taking certain like specific dataset itself could be accessible to public like you know one example of this is maybe you have a dataset of data that is not up to date maybe it's data from six months ago you want to make it available to the public but for the latest data you need to have like a commercial licensing to do so. So you will use metadata tagging to basically tag your latest metadata set and make it subject to licensing but then you have a public dataset which is kind of older data just as an example. How do we make this happen is again leveraging an open source project to build and integrate security and governance across three layer which is the physical data layer so how we store data and serve data the virtual layer which is how do we consume data how do we query data in the pipeline and then the access layer which is once data is ready to be distributed how do you make it accessible by tools by data portals and by different data user. A lot of what we've built now is basically the first three sublayer that you see at the bottom of this diagram we use container storage technology based on self or object storage we use data serving relying on a packet and Apache iceberg so Apache iceberg basically is a big data format that gives us capability such as asset transactionality on the data itself which means we have consistent you know update and rid of the data across big dataset and the underlying format is actually a parquet format which makes it very scalable to just add you know gigabytes or petabytes of data potentially for specific dataset and on top of this we are using Trino as a distributed SQL engine so Trino helps us to federate a query of data across a very high number of data source the work that we have not done yet is what you see above building a metadata platform and some data security layer we've we are already experimenting with LinkedIn data project as well as Apache Ranger to build those layer and a lot of the work that we are going to do in the next 12 months or so is going to be on those two layer so VAL3D or roadmap for data access management as you can see today we have actually a very granular access capability already with the Trino layer and Eric will demonstrate this in the demo but some of the things that we are missing is is kind of how to tie the security to the metadata management layer and obviously how to generate catalog automatically so let's go now into the demo and then I will leave it you know to Eric again to share a screen thanks Vincent I don't know if the moderator has to yeah I've made you presenter oh wait there it goes perfect excellent so I'm just going to briefly give you a high level view of what I'm about to try and demonstrate here as I mentioned before we're intending to make heavy use of Elias capability of supporting Jupiter environments for both actual data exploration data science and prototyping but also to then take the same notebooks and be able to run them in repeatable pipelines and so sort of bridge the gap between actual data science and DevOps and along the way I'll show how we're using github and some of red hats continuous integration bots as well as clay and then similarly you know from the slide before you know Ellyra we're hoping to represent actual repeatable ETL pipelines ingesting from disparate data sources including things like object store then exposing these as actual SQL databases and from SQL you know it's easy to consume through Jupiter or tools like super set to do actual analysis so just briefly all of this is being driven through the OS climate github organization and we're making use of both github projects in teams and this has been a real help helping to onboard different community members who as Vincent mentioned are not really conversant and open source and so being able to give them a pathway to private repos on github and then eventually to public repos has been extremely successful and actually very happy with how much work now is being done completely out in the open with the different organization members and similarly I've had a lot of success unifying identity management through github so here you can see getting onto the actual cluster is done using github and if you're a member of the organization with the correct team membership any you can actually get on the cluster just by authenticating to github so here's the atrino space most people don't get on the cluster most are cluster admins of course but it goes beyond that we also are logging into the jupiter hub environment itself using github so if I want to log back in I have to click the same github and this is all letting me do this just by clicking a button because I've already authenticated to github so the unified github open authorization has actually been quite nice in terms of cleaning up the identity management and we've even got the atrino access control working the same way we have a JWT token server and to get onto that you also have to authenticate and it gives you a JWT token no peeking and here's where we've actually begun to already interact upstream so we want to unify atrino's group definitions with our github team identities and so I've been prototyping an actual atrino plugin that does group provision so it's actually extremely helpful we're going to hopefully test this out and actually get it upstream directly onto the main atrino repository I mentioned the operate first management and so we're actually managing the entire cluster configuration through github and so here's just one example where I was actually resyncing our atrino user groups with the github teams and it just took the form of a pull request and in standard open source fashion we discussed it and talked about a few alternatives and then it was eventually merged and now you know the new group configuration is automatically deployed on merge onto the cluster so the operate first principles and the github's principles have been a definite success so I wanted to talk about you know how we're actually leveraging the platform especially sort of like one of the central obviously features is the jupiter environment so obviously you can do pip installs but I already have these installed on the image we're managing actual credential storage with the python.m if you're familiar it's basically a way you can load credentials without having it show up in the code and of course if you're storing your code including notebooks up on github keeping your credentials out is extremely important so once you have these you can connect to the actual atrino data service we can do things like connect to s3 buckets using boto3 let's now look at some data here we have some implied temperature rise or itr data that i'm loading straight off our atrino database and its job is to map different investments so these are different companies in the energy space or non-energy space as well that you know are associated with implied temperature rise success and so over here in the far right there's an achieved reduction targets and so there are various points of progress achieving their targets and each of these is associated with a standard identification number an isin or isin number and so we can make use of these keys to do some interesting things now a completely separate data set contributed by the glyph organization provides some key data services like mapping these isin investment identifications to the um legal entities that actually issued them and so the legal entity identification or lei number we're planning to leverage heavily as a community resource for getting people to push their non-standard ways of tracking investments into standard ones and i see that time is passing so um we also have a table that can map direct issuers as you saw above to ultimate parents so this is to track um corporations and corporations subsidiary ownership so that um you can actually do a better job tracking true climate impact up through company ownership chains and so what if we wanted to take these three data sets um which come from two completely different organization members and get some kind of value out of it so here i have a uh sequel query which maps the company names and their reduction progress uh to the lei legal identification and the legal identification of the parent and so i could run this query um and it gives me an echo pandas data frame and so you can see that by the time it's done if this joins i get seven results um the parents are all empty which is to say these are all top level corporations um and so the main the main value here is that i've gone from standard investment ison numbers um to uh standardize l legal identification number to get the achieved reduction um and of course there's nothing special about the sequel what's really special here is that we've already been able to federate data sets from two different community members to support you know value add using standard data science techniques and so now suppose i wanted to like save this off um i could run the same table and run the same query and i could save it off as an actual new sequel table um there it is that's the query and it should tell me that it wrote seven records yes so i got all seven records um um so now i've done some data science in a notebook um again what i told you is the the lighter jupyter environment can do a lot of fancy things um the fanciest thing it can do is you can take these notebooks so i took here's that notebook i just showed you copied into a pipeline editor and i can give it different dependency injections um so what i can do is i can actually give it a new table name um to output two for the pipeline make sure i save the pipeline and then run it we're going to use the kubflow pipelines give it my demo config and it gives me a link to the actual pipeline console spinning up here it'll give me an actual graph of the pipeline node there it goes um so it's running i can look at its log output see what it's doing so i want to stress that it's actually running the notebook i just showed you um with exploratory data science and all um and of course you could remove some of that stuff to make things go faster but the main you know the main message is it literally gives you seamless transition from data science notebooks into repeatable pipelines and it should shortly give me a message that it succeeded yes the pipeline ran so now if i went back i can actually convince myself that i got a new data table for running that here we go so let's see everything went correctly yes um so that pipeline rerun that entire logic um off on the system and i got a new new table um and we are at time um i could try to demonstrate the if we have time superset is not cooperating well that's okay we're at the end of time i will um close out the demo and hand it back to vincent for closing remarks uh eric we still have a few minutes if you need to finish the uh demo let me try let me try one thing i'll see if i can bring the link back up um you need to share your screen again eric sorry that's okay are you seeing it i think it's yeah excellent okay well i'll see if i can get to superset here there it goes okay so um you know superset is another great open source tool for building um sort of like low code or no code dashboards um so let's imagine i want to do a fast dashboard off of that data table that i just generated i have a predefined plot and you can see here i actually plotted the achieved reduction metric against company name and then sorted it in decreasing order so you can see here that uh you know glaxo smith has almost completed its target reductions and um you know some of the others aren't doing so great barclays shame on you um i shouldn't say that this is i'm sure they're doing fine this data is just demo old data um but anyway there you can uh see sort of like the entire pipeline from exploratory data science to repeatedly executable pipelines through to actual end user dashboarding and charting um all on the same open source-based platform and oh i uh want to show the actual image so the container image i used to run that pipeline was built also off of the os climate repositories using red hats continuous integration build robots so here you can see i basically filed a github issue say hey could you please build me the latest image it's version 0.1.1 and um the bots went off and built that and put it up here on the koi repository so you can see here it was built yesterday i think um and then it came back and says oh i successfully built so here's the link and um that was what i used to actually run this image and yes that was actually the completion so i can truly hand it off to vinson thank you eric so let me let me conclude maybe with some next step you know and then reference links you can find out more about the west climate initiative on the west climate website under the linux foundation the link is here for your reference uh in terms of upstream projects we have an open data hub community page that shows the architecture as well as the the ongoing effort integrating more open source project in the open data hub initiative and as you can probably infer from this presentation we still have a lot of work to make this happen with the community and if any aspiring data scientist wants to work with us on the latest open source technology and and become a contributor don't hesitate at all to reach uh you know directly to us uh put actually my personal email out there as well as you can contact eric so don't hesitate to reach out we are actively integrating community members now into this initiative thank you everyone for your attention today


What's going on everyone Sam here with late in sports car driven one box of 21 22 Panini revolution basketball Chinese New Year for Chak Fung L. So good luck here Chak Fung See what we got out of your man Hopefully something good some big rookies. Maybe that'd be pretty cool so I'll sleeve all of your Chinese New Year's rookies right now And then anything numbered and then every every other New Year will get sleeved as well Chris Paul and Franz Wagner a good way to start it there. Trey Murphy. There's a jaren Jackson Chinese New Year Rudy Gobert on your Chinese New Year Moses Moody rookie to start off and a Josh Christopher Chinese New Year nice one there Nice quiet Leonard on the Chinese New Year solid one there the claw Austin Reeves rookie and we've got a Harrison Barnes Chinese New Year King Miles Turner, that's gonna be Georgios Calate Zekis on the New Year rookie for the box Santee Aldema there is an RJ Barrett On the new year we got a green coming up. Nice. We've got that is Cameron Thomas Nice one there for the Nets That is seven out of 88 Uh, no Marvin. These are the last two breaks. Anything ordered will probably go tomorrow with Forrest tomorrow night Thanks for the follow there. I have a hard stop at three Uh Jalen Suggs done their magic rookie Because Forrest is starting Group breaks at four. So I can't stay Can't stay any longer unfortunate. I would if I could but Cannot unfortunately Uh New Year deer and fox And last pack of the break Good luck here. Uh chacklung Okay, I'm Thomas and a Gary Trent Jr. New Year That'll do it for your break there. Um chack fun. Thanks again for jumping in. We'll get these right out to you, buddy


2019 has been a roller coaster of both positive and negative by far the most significant year in my life. I've helped thousands of people improve their health through a variety of videos such as strictly educational, days of eating, even correcting vegans and having a little bit of fun can astray people from an incorrect path to improve their well-being. I like to touch on the most significant videos I've done as well as corresponding events. Keep in mind guys, I do a video every day, so although there are at least 10-15 excellent videos every month, I will be highlighting my few favorites. This year started off with World Carnivore Month and there was definitely more hype around the carnivore diet last year than there is now. My Raw vs. Cooked video is something I constantly reference, that was the first educational video we did this year, going over the pros and cons as well as the necessity of both raw and cooked foods in your diet. Bone broth is something that I've been pestered about from time to time and people still ask about it so I needed to touch on it. Fruits and vegetables aren't healthy, goes into the fact that plant foods don't contain the nutrients that our bodies need. That was when my channel was really blowing up seeing the most growth, some days I was getting over 1,000 subscribers, I was kind of just hoping that it would never stop. I guess it was partly due to all the drama that month as well, you know Bonnie Rebekah no longer being vegan, one of my most popular videos and then Vegan Gains' channel was taken down towards the end of January. The drama got bigger and bigger. I was still doing ex-vegan interviews at the time and one of the girls actually met up with Sferidge basically exposing him for eating cooked meat as well as drinking water, nothing wrong with that as I do them, but Sferidge is known for being very critical of anyone that eats cooked food, drinks water, he proclaims that water is toxic, that cooked food is toxic, yet he does it himself. So it's a bit hypocritical when you're doing one thing and telling people another. If you guys missed my natural glow makeup tutorial, you'll find out what Frankie Boyd would look like if he actually wore makeup. I did a video on mewing facial posture explaining that facial development is determined by diet not just posture. I explained tanning beds, you know whether or not you can use them to increase your vitamin D3 status, then the same girl that did my makeup in that makeup tutorial ended up putting a fake beard on me, which I used for a video where I was explaining that I raised my testosterone naturally on a carnivore diet. Towards the end of February, there were some more very important videos on calcium, plant versus animal vitamins as well as high meat, it was a bit of drama back and forth between myself and vegan gains as you can tell by the thumbnails, we were having debates and I actually started my fitness trial at this point in time which no one ended up following through with. I had a vinegar, iodine as well as scurvy are three videos that I am very proud of and I had plans for debunking the three aspects of veganism pretty extensively, health, environment and morals. You know we did the plant versus animal vitamins for the health aspect, we did a video on the environment and then we did the morals video. I ended up having my second debate with vegan gains around the time that Ravana was caught eating fish. So again, a lot of drama towards early spring, the end of that winter. Shortly after that, raw alignment as well as Tish Wonders gave up on veganism and then I had a follow up debate with vegan gains. Around the time, Rat Boy reached out to me to collaborate and after I watched some of his videos, I realized the cornivores were copying my content, that video of the first one exposing them wasn't received too well at the time and it wasn't really clear they were paid shills. On a more positive note, that was when I started the perfected health podcast, great first episode with Ivor Cummins on heart disease. The one thing I regret missing in that first podcast was talking about how you need to have high blood pressure to get heart disease, it would have been interesting to hear his feedback on that. So now we're at about the end of March, already quite a bit has happened especially making a video a day. My fish is a double edged sword video is a must watch, I also did a fairly funny skit as Frankie Fennel on vegan rabbit diets how they should be eating their own doodoo. Spherage got arrested for eating a raw squirrel, complete nut job. I debunked the methionine to glycine nonsense that people were using to sell collagen supplements yet that is still present and people are always talking about it. It seems to have stuck with their BS. Then I went over some indigenous oat preparations including oat milk and traditional Scottish porridge. From 2016 to the beginning of 2019, I was making my own YouTube thumbnails and they weren't that great you know they were just bold text on random pictures taken out of the video. I did end up paying someone for a month or two to do my thumbnails more professionally and then he had some personal health issues and couldn't do it anymore. So on a whim I learned Photoshop and then my thumbnails took a little bit of a step up. You know I had fun with a few of them you know putting like cauliflower brains on vegans coinciding with me learning Photoshop. I launched Frankie's free range meat on Kickstarter. I remember one of the first thumbnails I was photoshopping was actually for the Frankie's free range meat video. I was also chewing masticum and my jaw was swollen as hell for a few weeks. My first vegan event also occurred. A lot of stuff going on. That was the veggie pride parade in New York City. I attended that with one of my viewers it was actually his idea. Coincidentally my Kickstarter for Frankie's free range meat was taken down one week later likely mass reported by vegans. I did a video covering the life of a feedlock cow. They don't actually spend most of their life on grass. We touched on the healthiest plan foods at least ones that I deem healthy. Here is my fourth carnivore goes vegan for a day. You know me having fun as a flamboyant vegan banana lover. We did a couple of those this year and I think we did two last year as well in 2018. Then I made a 45 minute video on the pros and cons of dairy.  I probably should have sold it as a video course but the more people I can help the better. We were rolling out with products on Frankie's free range meat to keep order volume high. After the Kickstarter was taken down we ended up getting a website up which the vegans also tried to take down but they weren't successful that time. Farage and Vegan Gains had a debate in the beginning of May because after those vegans got my Kickstarter taken down I started ignoring them. I introduced you guys to my brother and sister at that time as well. I think my brother was visiting for some reason. And then I did a really good video how to get started on the carnivore diet which is a great overview of the basics everything you need to do to get your macronutrients and micronutrients correct. We covered grounding, the importance of vitamin D3, coffee as well as cheese. I spent quite a bit of time researching how to reverse arterial calcification. Some great points in that video. We covered digestive systems of carnivores versus herbivores then officially launched Frankie's Naturals, my hygiene and cosmetic products that I had been working on and selling since 2018. This was when we started filling the orders for Frankie's free range meat which was a bit of a fiasco at the start. Definitely shouldn't open a meat company in the hottest week in summer. John Meat started gaining traction at this time and there was a lot more vegan propaganda, you know Billy Eilish, media blitzes, ironically this was when I was notified that John Venus has eggs in his fridge by an angry vegan on Instagram. This is also when the Game Changers movie was announced, kind of scary how when you look back on all of this it seems really planned out and orchestrated. But at the time you're just thinking oh more of this, more of that, you're not really thinking it's that big of a deal. The highlights for July are definitely top 10 healthiest foods as well as the videos I did on vitamins, minerals and electrolytes. Then Frankie Boy put two and two together, called out the carnivores for being sponsored by special interest funding and you guys tried to crucify me. I lost quite a bit of subscribers for this and my channel stagnated for months. The reason I made that was because no one really wanted to collaborate with me, I couldn't figure out why and I was trying to be objective about it and figuring out why people weren't ignoring me and getting banned from the Reddit forum was kind of my last straw. Then we went to our second vegan event which was by Anonymous for the voiceless at the Cube of Truth in New York City. They did a bunch of events all over the world and this one in New York City they were doing it for like a week straight. That much happened, honestly there weren't really that many people that showed up. I should have probably gone down the next weekend as well but that first weekend wasn't eventful. We kind of argued with the event organizer and then they kept brushing people away from us so we couldn't really have conversations with people. Then I made a video on the downsides of grain fed beef as well as a really good one on halogen toxicity, the importance of removing fluoride chlorine from your diet. We almost threw up tasting the Beyond Burger and then answered a very popular question about carbohydrate requirements for performance. We took an in-depth look at chocolate, showed you guys what my sister eats as a carnivore, plenty of live stream Q&As, days of eating, vlogs thrown in here and there, brought up the fact that vegans are eating copious amounts of insects in their foods every day, went over raw meat safety, alcohol, then we had the vegan animal rights march where I decided I probably shouldn't be going down to these vegan events anymore as it's risking my safety. At the time I also did a series on cholesterol.  Olive oil was a popular topic. I did a Marilyn Monroe's diet, continued to get crucified for my weight lifting videos. This was when I started posting them here and there. The final video on vitamin K2 was a good one. The importance of breastfeeding didn't get too many views but a lot of people still ask me about that. The hate for my fitness videos was really ramping up at this point in the midst of which I did several other important videos. One was on Cam Newton where I explained why vegans can't get enough protein. Another one on marijuana. And a third one on all anti-meat arguments debunked, ranging from saturated fat, heme iron, TMAO, any concern you have about meat carcinogens, you will find it in that anti-meat argument debunked video. One reason I started publishing those fitness videos was because people didn't follow through on my fitness trial so I said screw it. Let me make the videos anyway and see what the response is. But since I was pretty skinny at the time, I got a lot of blowback and I decided let's start bodybuilding and I've been in the gym miserable for an hour, an hour and a half every day since. Game changer's movie came out, I debunked it maybe a week or two after it came out. But most other people were really talking about it like last month so I was a little bit early on that. I spent about five hours researching mushrooms for you guys. Around this point, I learned that I had high ferritin levels and started donating blood. My mother also told her medical story, having triplets, her double kidney transplant. Explained all the different types of artificial sweeteners. Then the drama ramps up a bit again. Stephanie Buttermore continuing to mislead her viewers. We took a visit to UFC 244 and I decided to expose rat boy for more plagiarism. Frankie's free range meat at this point has been up and running for a few months, all of the kinks have been worked out. I usually went down one or two days a week to fill the orders. And then the rest of the week we would have my business partner processing the stuff. I did a parody on the American cycle morning routine. We had a bit of fun for Thanksgiving. And I gave myself a little pat on the back for being right about John Venus. We launched our Carnival course and then two very significant things happened that were in my favor to say the least. One is the Joe Rogan game changer's debate being clearly orchestrated. Another is raw alignment being a very obvious sell out for the carnivore diet. I mean Chris Crescer almost threw his credibility in the toilet and raw alignment made it blatantly clear that there is carnivore special interest funding. These two things convinced most people that were doubtful that there is definitely special interest funding. The Cargill cornivores, shills, whatever you want to call them. You would think the vegans would have jumped on that to discredit the cornivores. But vegans don't want to touch it because they are special interest funded too. It gets really fishy. You can't start calling people out for special interest funding when you're special interest funded yourself. As usual, Frankie Boy coming in hot with the information. We spoke about inflammation, avocados, antioxidants, some videos I've been wanting to do for a while. The Aga in America video was long requested and you guys have an idea of what has happened over the past few weeks. The thousands of hours I've put into my YouTube channel this past year, especially, is something that I hope is illustrated a bit clearer for you guys. The main purpose of this video, as I said earlier, is to point out some important topics you guys may have missed. But I also wanted to explain several things. I've been portrayed as a bad guy in the carnivore community that I've never been a part of.  This is absolutely not true. The only reason they are saying this is because I am whistleblowing their agenda. The only reason I am whistleblowing their agenda is because they refuse to acknowledge that this clown rad boy copied my videos.  At this point, they can't just admit they were wrong the whole time.  Some of you might be wondering why I refuse to collaborate with Spheridge. You missed a few videos here and there. He is an absolute psychopath, and that is putting it nicely. He attacked people with knife as a teenager, has made many derogatory remarks against me for no reason other than me pointing out that he drinks water and eats cooked meat, kind of funny to be honest. If I tell the truth about someone and they start ad hominem attacking me, it really shows their true colors. A lot of you are asking me to respond to vegan gains or debate him. And I actually told myself I wouldn't even mention his name again. He is the driving factor behind my Kickstarter getting taken down. And his intentions are just as psychopathic as Spheridge. So I will not be associating myself with him in any way whatsoever. On a different note, something that was on my mind the other day. I made a video titled Vegans are sugar addicts where I pretended to have like a drug addiction and I was injecting myself with sugar. I'm not sure how many of you guys have seen that video, but let me know if you want to re-upload it because it was taken down. Of course, I have to thank you guys for sticking with me through all of this and supporting me along the way, through the positive, through the negative. I've done so many anti-vegan videos at this point that the amount of negative comments on my channel overwhelms the positive comments on a lot of days. I mean, I guess everything is a means to an end. I always say I never wanted to make those videos, but it was an important aspect of growing my channel. And I mean, whatever you have to do to get to the end goal, I guess, right? Overall, I'm looking forward to a much more positive 2020. And as much as I wanted to get more done this year, I have a list of like several hundred videos to do. I got a decent chunk out of the way, but there's still quite a few important topics that I haven't touched on yet. There's just so many random events coming up every week. I don't have time to research, having second thoughts about certain videos. And it's tough because as much as I would love to just do educational videos every single day, that's not really what gets the most views. And as much as I would like to say that all of these negative things are going to be pushed to the side, the vegans aren't going anywhere. I don't think the corn of ores are going anywhere either. So we're going to have to deal with that. Although I would like to push it on the back burner at this point in time, it's too much, it really is too much. So thank you guys for joining me. Please like the video as always, subscribe, hit that bell icon. And if you guys want to support me further, we've launched our book, Ancestral Indigenous Diet. You can check that out on Amazon, it's down in the description. And of course, check out some of the videos I mentioned throughout this video, you'll definitely enjoy them.  See you guys next year.


Okay, Bola buddies. Thanks for watching. All right, you guys. Sorry. I've got my little owl up. I Was not planning to come on but I just had something happen and I was listing an item that I listed on my live show the other night and Sometimes items have recalls so eBay will sometimes let you know so I'm gonna show you what this looks like How you can check and what you should do. So let's get started here. The first thing I'm gonna do is I'm gonna pop up this so I can show you My list with me Okay, so over on my reseller testing Bolo products I do a list with me like working hangout and I was listing this doll. So let's check out the footage here This one's interesting. There's some interesting items here Okay, how cute she is look at that face. That is so cute This one is made It says Anna number 129 North American Bear company exclusive for pottery barn kids. I like the sounds of that Again, like what is up with the hair on these dolls? This one this hair is cool. It's curly. It's curly like mine Mine used to be curlier Okay, look at its little legs. Oh They've got wires. They bend you guys. Oh my goodness. Look how cute That is cute Look at the little chick I love it Okay, let's look it up. So it said Anna and we'll look up pottery barn Flush there she is number 129 says 2006 Not selling for very much. I thought they would uh sell for more Pottery barn kids can do really really good Okay, so just a quick little tip just because there are others listed Does not mean you should list yours and we're going to go into this more in just a second But what I wanted to show you is I looked this item up on eBay. There were solds But this is what happened when I tried to list the item So I am over here at Create my listing and I get to the bottom and I go to submit the listing and right here it says This item you are about to list may be subject to consumer product safety commission recall Check the cpsc website for recall information before selling this product on eBay Keep your family safe during the holidays and all year long by signing up to receive direct email notifications about recalls at www.cpsc.gov It says it is illegal under federal law To knowingly sell or resell a recalled product Making even more important for eBay sellers to receive direct recall notices from cpsc Or to check cpsc's website for recall information Before any consumer product is posted for sale online Okay, so let's click on this cpsc website right here And that is going to take me over here Now I want to search recalls So let's click on this And I'm going to put in pottery barn right here I am going to click category and I'm going to find dolls And I'm going to see if my doll is actually on here I'm going to hit apply And I'm going to scroll down Now let's see dolls recalled by pottery barn kids due to strangulation hazard This was from september 8th of 2011. Now this doll's face looks the same The hair looks the same or very similar. It's hard to It looks pretty similar. Um So the hazard it says is the hair on the chloe And sophie dolls may contain loops That are large enough to fit around a child's head and neck And the headband on the odry doll is if loosened can form a loop that fits around a child's head and neck These loops can pose a strangulation hazard Remedy consumers should take the dolls away from children immediately and cut the looped hair of the chloe and sophie dolls And remove the headband of the odry doll to eliminate the hazard Consumers may also call pottery barn kids for instructions on how to return the affected dolls For a merchandise credit about 81 000 in the united states and 1300 in canada. Okay So it says these loops Now can form a loop Okay, so I don't know you guys. Um, I guess the hair is long enough for strangulation. I I don't know if it has to happen to somebody And that's why they recall it or what but um, let's go back over here And I'm going to Not list this item. I'm going to hit edit I'm going to save as draft.  Hello. There we go. Delete Now my dolls name is ana Okay, so I don't have the dolls that they mentioned but the hair looks the same It popped up as a recall When I listed it So I'm not going to take the chance that it could be This doll they just did not mention ana. Does that make sense? You guys I mean, obviously have to make your best judgment on a situation like this um Could it have been okay because it was ana maybe mine's hair is different than the other two I don't know. Um But I'm not going to chance it and I suggest if there's a recall that pops up Something in your title has triggered that to pop up and that is probably going to be triggered in the ebay system Again, which could cause your item to get taken down and you could get a penalty on your account Or a suspension. I don't know that for sure I'm not exactly sure how it works It may be something you could fight because it was a different doll the doll's name was actually on the tag Um, it said ana. I think it said ana or it had a number Um, I don't talk about the doll the entire video But anyway, if you want to go and check out my reseller testing bolo products Um, I do live working hangouts on that channel for the last two videos I was listing plush. So you guys can learn how I list plush I pull up screen shares like you saw I show you how I search comps And then I actually list the item I drafted So if you're interested in that or just hanging out while you work to get some motivation going Definitely check that out. All right, you guys. Thanks for being here. Thanks for watching


How many of you are excited for GDPR? So today we're going to be talking about GDPR, continued preparations and compliance. And I'm going to be offering you some security tips as to what you can do for GDPR. I want to begin by introducing myself. My name is Sam Jadalee. I am the CEO of Host Duplex.  I myself have been in the hosting industry for about 20 years. I started my first hosting company when I was about 13 and a couple more in high school and in college. I'm also the director of IT operations at Mandala. We are a cryptocurrency exchange. And I mainly perform the security operations for them and protecting our assets and thwarting us from any attacks. Excuse me. My passions include educating our clients on security. I'm very passionate about data privacy, obviously, why I'm here with you today. And I am a huge college football fan, especially the Big Ten conference. I went to the University of Iowa and I am a huge word camp enthusiast. Now I wanted to preface this presentation by stating I'm not a lawyer. My guidance or advice is to only allow you to become familiar with GDPR and the regulations, especially as it pertains to your needs. I highly recommend seeking the advice of counsel should you have any specific questions. Now I wanted to begin this presentation with a quote that comes straight from the official EU GDPR website. And that quote is that GDPR represents the biggest shakeup of data protection in over 20 years. Now you may ask what is GDPR or what does it even stand for? So GDPR stands for the General Data Protection Regulation. And its objective is to give citizens back control over their data. Now believe it or not, you are actually under surveillance right now. Your cell phone that's in your pocket is tracking your every move. The apps that are installed on your phone know where you are.  And they'll know your favorite items before you realize they are your favorite items. GDPR aims to address these issues or at least make you aware of them. And while this is an EU law affecting EU citizens, my hope is that other countries enact similar laws, perhaps ones that are a little bit more refined. Now how many of you have heard of MoviePass? Good, quite a few of you. So for those of you that don't know, MoviePass is a movie subscription service. It's $10 a month and you can see however many movies you want. Now the CEO of MoviePass was recently speaking in front of a Hollywood audience. This was about a few months back. And he was essentially bragging about their data collection practices. And he was telling the people in the audience that they track users for up to three hours before and after they have left the theater. And I would assume this is probably for some sort of location based marketing. Now companies like MoviePass are taking our data and they're creating a data profile of us. And the problem was was that the CEO hadn't explicitly told us until he got to that in front of that audience. And this is where a law like GDPR comes in and it allows for transparency. Now imagine if that data got into the wrong hands. How many of you have heard about Ashley Madison? So for those of you that don't know, Ashley Madison is an online dating service that offers an apparent escape from the banalities of marriage. And it's marketed primarily towards married individuals and their company motto is, hey, life's short, have an affair. So about two summers ago, Ashley Madison was informed by a group of hackers known as the Impact Team. And they told the CEO that if you don't take down your site within 30 days, we are going to release the data of all your users. And a couple months go by and the CEO I guess just didn't believe it or he didn't really care. And two months go by and the hacking group releases the data for 36 million users. Now immediately after the hack, social networks in the media were overloaded with these pejorative overtones which essentially came from the unfaithful users of the website which happened to be mostly men. And others consider these hackers to be these benevolent donors to society. But at the end of the day, this one data leak upended the lives of hundreds of thousands of people, if not millions. And my takeaway here is that these examples don't apply to sites just like Ashley Madison. It applies to your profile on Facebook, your purchase habits at the grocery store, at hospitals, at credit bureaus, at banks. And my point being that privacy and data privacy should be a fundamental right that we as individuals have. Now a recent study showed that three out of four EU citizens don't feel in control of their data. In fact, 90% of EU citizens are concerned about data collection without their consent. And this clearly is affecting e-commerce. And this study is a few years back and they were saying that 35% of people had payment security concerns, 29% had privacy concerns. And I was assumed by now, especially with all these ubiquitous hacks, that these concerns are probably only rising. Now this really begs the question, how are we going to grow an economy if we don't have trust? Well GDPR's other goals include strengthening individual rights when it comes to data privacy. And its goals are to unify data protections and facilitate the flow of personal data. Now GDPR comes with some really steep fines for those people who are non-compliant. It is 20 million euros or 4% of your annual revenue, whichever is greater. The law itself is 261 pages. It's quite long, it's 99 sections long. It's very obscure, it's vague. And while I definitely wouldn't say it's the perfect law, in my opinion I think it's at least a step in the right direction. Now you may say, Sam, what does this have to do with us? You keep saying EU, EU. Well, the EU is taking the lead on data privacy. And they are able to assert this law over us with something called long arm jurisdiction or extraterritoriality. And this is where a local court can assert jurisdiction over someone in another state, or in this case, from the EU to other countries and companies who process the data of EU citizen. So essentially it applies everywhere to anyone who processes the data of EU citizens. Now you're gonna say, Sam, well, I don't have any EU clients. Well, it may actually not matter because you don't need to have EU clients. You could be storing this data in the means of a contact form, a mailing list, comments, live chat. So again, they don't have to be your clients and you could still be affected. And some of the personal information that would be affected or included in that is your name.  Also genetic information. Anything that can be tied back to the user. And that includes race, ethnic origin, other health data, location data, the metadata from photos on your phone, IP address, all of that can be considered personal data. Now GDPR includes eight data subject rights. I'm gonna share with you some of the ones I think are at least the most important. That first one is the right to access. Now the right to access states that we must provide access to an EU citizen's personal data. It's really similar to how you would obtain your own credit report. It states that no fees should be requested when exercising this right and a company has 30 days to comply. Next is the right to be informed. Individuals have the right to be informed about the collection and use of their personal data. It is the what, the why and the how. How is their data being processed and why is it being processed? It is also about providing people with clear and concise information about what you are doing with their data. All the information you give them must be easily accessible, it must be easy to understand, it must be intelligible, and it must be free of charge. And the next important thing is that they must give explicit consent. There can be no room for misinterpretation. So this essentially nullifies implied consent. So you can no longer have that pre-filled check box on your sign up forms that say, yes, sign me up for my newsletter. The user has to explicitly check that box for themselves. And next is the right to data portability. This is the right where individuals are able to download their data and take it elsewhere if they need to. And they must be able to download it in a machine-readable format. That can be a CSV file, an Excel file, a JSON file, but it cannot be something, like you can't mail them letters of their pieces of documents. It has to be in a machine-readable format. Next, and most importantly, is the right to be forgotten. So users must be able to request for the erasure of their data, and you must comply with that in 30 days. It can be verbal or it can be in writing. Now, how can you prepare for GDPR? Number one, you could perform a privacy impact assessment. That's, you can see the what, the why and the how. What are you storing? Why are you storing it and how are you storing it? Where do you hold your data? Is it locally? Is it in the cloud? Is it at your hosting provider? And what third-party providers are you using? Is it MailChimp, iContact, SendGrid, what have you? So make sure you look into all those. And also, perform a security audit. I'm gonna share some tips with you here on security here in a moment, but if you perform a security audit, you can at least see what you're storing. And lastly, update your privacy policy, notify your clients, let them know of the changes that you have made. Now, so security tips, this one is pretty obvious. Number one, enable encryption. Add an SSL certificate to your site if you already have not, because if you're storing personal data, at least you want the transmission of that data between that client and your server, you wanna make sure it's encrypted. And most hosting providers now, a lot of them offer SSL certificates for free. If not, it's usually a minimal fee. And an easy way you can enable that is with a plugin called really simple SSL. It makes it super simple. It automatically changes all those hard-coded HTTP links to HTTPS and makes it very easy for you. Another one I see really common all the time among WordPress agencies, developers, even site administrators, a lot of them will just create a backup file and they'll name it backup.zip where they'll do wpconfig.bak and they store this right in that public space and they'll forget to delete it. And hackers look for these things and so you won't believe how many people do this. And so if they just type in a URL and they add wpconfig.bak, they can download all your credentials for your database, your database server and they can essentially see how your server is configured. Next, check email headers. You know, my mom, three months ago, she gave me a call and she says, Sam, I got an email from the FBI. I'm like, mom, the FBI is not gonna email you. So make sure you look at where those emails are coming from. Make sure they're from legitimate sources. Some helpful plugins. Again, really simple SSL. Another one is WP Security Audit. It's a great plugin that tells you what an administrator is doing. It logs all their actions. You can see if something, somehow created a new admin account. It puts this in the database and it can send you an email about it. Excuse me, another one is WP GDPR Compliance and GDPR Both. They integrate with a lot of popular plugins like Contact Form 7, so it helps you become GDPR compliant. A great site to check out. Another one is called Cookie Bot. Cookie Bot, you could enter your URL. It'll tell you if your site is GDPR compliant and if it's not, it gives you a list of vendors that you're connecting with so that you can also update your privacy policy with as well. Now, what to do in the event of a data breach? Number one, contact your host, review your logs, have them look at your logs, have your IT person look at your logs and also contact all the third parties that are using if you've ever had a breach and have a plan of action already in place. GDPR requires that if you've had a data breach and once you've found out about it, that you must notify your designated supervising authority within three days. Now, what are some unexpected consequences of GDPR? There's a lot of talk about this. It's hindering innovation because of all the added work we have to do in going through all these lawyers and so it's especially affecting a lot of small businesses. It is also blocking the blockchain. The blockchain itself is supposed to be immutable. It's supposed to be unmodifiable. Nobody can change it. And with GDPR, being able to erase and that information, obviously, that could be a problem. There are also a lot of companies that are denying access to EU visitors. So they just don't want to deal with GDPR so they're just blocking the entire continent.  A lot of people are worried about the death of free services because of this law. People are concerned that maybe Facebook may go away or Gmail may go away because of all this, but at the same time, I would think that we also should know what is going on with our data, how it is being processed. Now, I have a book I want to share with you. It's called Data and Goliath. It's by Bruce Schneier. And if you haven't read this, I highly suggest you do so because it is very eye-opening, especially to those who are not privy to IT cybersecurity. And I wanted to give you a few examples from the book and how it, in fact, relates to GDPR. Now, Bruce states to us, he describes to us the many unknowing ways that we cooperate with surveillance. For example, our supermarket loyalty cards take our purchase data and they provide us discounts, same with Facebook. They take our data and provide us targeted advertisements and we cooperate with corporate surveillance because it promises us convenience and we cooperate with government surveillance because it promises us protection. And the result is that we have this mass surveillance society of our own making. And every morning, when you put your cell phone in your pocket, you're making an implicit bargain with the cell phone carrier. You're saying, I want to be able to make and receive phone calls in an exchange I will allow that company to know where I am at all times. And that bargain isn't specified in any contract, but it's inherent in how the system works. And today, GDPR is changing that. In summary, I just wanted you to know that this is not just the EU. They are able to apply this law again by way of long arm jurisdiction and even if you don't have any EU clients, you may still be affected. And you must obtain consent. And again, you want to provide that information in a clear and concise manner.  Thank you all for listening. If you have any questions, you can find me on Twitter or email and I'll also be at the happiness bar after this to answer any questions.


It was the 9th of Tribute and Thursday in honor of the former head of Interim Government and Commander-in-Chief of the Armed Forces, Chief Ennest Adegunle Oladende Shonekon, GCFR. The wake-keep had in attendance men of Timber and Calibur who extolled his virtues. Present were the Executive Governor of Lagos State, Babaji Desong Wolu, Governor Dakbo, Abiodong of Ogun State, Governor Sheimakinde of Oya State, former Governors of Ogun State, Senator Ibikunle Amoso and Chief Ulushegun Oshaba, a Minister of Information and Culture, Al-Haji Lai Mohamed and the Secretary to the Government of the Federation, Boss Mustafa, among others. A correspondent, Paul George reports. It's a gathering of people from all walks of life, politicians, public servants and captains of industries. They have all come to pay their last respect to the late President, President Mohammad Ubuari is represented by the Secretary to the Government of the Federation, Boss Mustafa, who says Chief Ennest Shonekon was a man known for his simplicity. I consider him father of the nation and a great patriot who was willing to offer the kind of sacrifice he offered. But his memories will remain eternal. The nation mourns him and I wish his gentle soul a very peaceful rest in the bosom of the Lord. Thank you and have a wonderful evening. The host, the Executive Governor of Lagos State, Babaji Desong Wolu, describes him as a man worthy of emulation. We are gathered this evening to celebrate and to honour the legacy of a truly great Nigerian who demonstrated outstanding leadership across every facet of professional life. If UAC were to be compared today, you will be the combination of Dangote, MTN and possibly First Bank all put together in one whole street. That was what the 47-year-old Chief Shonekon, who pretended over at that time. By this singular thief, he became a leading source of inspiration and a role model to subsequent generations of high-flying Nigerian scoped executives who served this nation until this very, very, very end. I think the man deserves another round of applause. In the same vein, the Governor of Ugun State, Dakbo Abiodu, is proud to share the same state of origin with Chief Shonekon. He elogises him. I stand here as the Governor of Baba's home state. And I must say that I'm indeed proud to be here in that capacity. We're celebrating the passing of an illustrious and accomplished son of Ugun State. A man of simple humility. On behalf of my family, the government and people of his dear state, I convey our deepest condolences on this irreparable loss. Chief Ernest Adegunde Aladin, the Shonekon, Grand Commander of the Federal Republic of Nigeria, aged 85. He was a Nigerian lawyer and statesman who served as interim head of state of Nigeria from 26 August 1993 to 17 November 1993. He was titled Abese of Egbalang from 1981 in addition to a variety of other chief-tensy titles. Prior to his political career, Shonekon was the chairman and chief executive of the United African Company of Nigeria, successor of the Niger Company, a vast Nigerian conglomerate. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


How can you use mindful moments to help you manage on a difficult day? Now this is a really simple technique that you can either use yourself or you can teach it to someone that you're supporting. The idea is based on the idea of mindfulness but instead of using big long mindfulness type approaches we're instead thinking about how we can introduce small moments of mindfulness into our normal day to day life. Now the reason why I think this is helpful is that because for many of us we're managing difficult thoughts, feelings and experiences on an ongoing basis throughout the day particularly if we struggle with things like anxiety. And if we're able to find ways to have mindful moments during the course of the normal day then we can take those anxious feelings and try and bring ourselves back down to a slightly better baseline. So this is about finding ways to build those mindful moments into our normal day to day activities. So what do I mean by a mindful moment? Basically we're taking a normal day to day activity that you can really easily incorporate into your day or that might already be a part of your day and making it into an opportunity to bring our thoughts and feelings back to a sort of grounded, mindful way. So a perfect example would be for me how I would have a mindful cup of coffee. So I'd have my cup of coffee and instead of just drinking it whilst doing other things I'd give myself five minutes to have a mindful cup of coffee. And what does a mindful cup of coffee look like? It's a cup of coffee where I have thought about how the coffee feels in my hands. I think about the smell of the coffee and the taste of the coffee. And whilst I'm drinking that cup of coffee for five minutes I give myself a break from all the other thoughts, feelings, experiences going on and I allow those thoughts to pass through my mind non-judgmentally. I'm just focused on the coffee, allowing things to happen, allowing myself to reach a state of calm again. Now it doesn't have to be a cup of coffee, it can really be anything. You can take a mindful shower, have a think about the smell of the shower, the feel of the foam on your body. You can brush your teeth mindfully. You might write really mindfully, you might doodle, you know, even just kind of scribble or write meaningless words on the page and think about the feel of the pen on the paper. Really you can choose absolutely any activity that's really open and available to you that you can do for just a few minutes and just really focus in on doing that activity. So I guess the key thing here to create these mindful moments is to give yourself a few moments respite from the rest of your day. So we're moving ourselves away from that and then we're engaging in an activity, almost any activity and we're giving it our full attention. We're thinking about how it feels, about the way it smells. If there's a smell, the way it tastes, if there's a taste, we're really, really losing ourselves in that activity. It gives our brains a bit of a break, helps us to bring those anxieties back down a little bit and brings us to a better baseline from which we can then begin to carry on with the rest of our day. Simple strategy, try it, see if it works for you and maybe try it with the people that you work with or support. Let me know which mindful activities you give a go. I look forward to hearing how you get on. Good luck.


I'm Fars Siddiggy, I'm a Specialist Solution Architect at Red Hat. And I'm Roberto Guardela, a Cloud Services Black Belt also working for Red Hat. But today, Roberto and I have got a slightly different role. We're a part of a dynamic and very busy DevOps team called the Tiger Team. At the moment we're working on a project which is developing a web application for one of our biggest open source customers. And because in our day to day activity we need to orchestrate a lot of thousands of Kubernetes jobs we need a tool that help us run and build this workflow. And this is why we're using Argo workflows as the main part of our tooling. Like many other development teams out there we are running on regular sprints. And as it seems just today earlier today we did have a release day and a latest version of our application is already deployed. Like I said we're a very busy development team. We're always working on deploying new features, going through bug fixes and all the weird and wonderful things that all developers do. So we don't really have too much time to think about security. But it's worked for us so far. We developers, we develop and we deliver and it's working, we're meeting our deadlines. So we're not bothering about that just yet. Now, like I said our release date was today. The latest version of our app is already deployed and if you'd like to see what our app looks like please take your phones out and scan that QR code on the screen. If you'd like, is it okay at the back? Can you scan it? Okay, right. So if you've already scanned the QR code you'll be able to see that's the open source client we're working with. We are developing the web application for the ArgoCon event organisers. We're going to show you how our workflows in Argo workflows look like in a minute but just on a high level so you know what steps are involved in our workflow. So we first do a git clone in our workflow. Then we build and push our container images and once they're ready we just deploy them to our Kubernetes clusters from there. And this is how we currently deploy our application. So you're very well aware that the time of the event is approached and we under so much pressure to release a lot of last minute changes. Now in fact our managers just called us and asked us to deploy some really pressured last minute changes immediately. So this is what we're going to do and Robert is going to show you what that workflow looks like. So the first thing that we need to do is to deploy the new pipeline that we are already showing and we will kick the second pipeline using the exact same workflow template. We have our workflows UI and as you can see we are running the CICP pipeline and we will show the CICP pipeline that we already deployed before to run and deploy our application in our Kubernetes clusters. So we have three different steps. We have the git clone, we have the container build and we have also the apply manifest and update manifest. So all of this is based in an open source project. You can go into the GitHub repo and you can see for example this application. This application is a small application based in Golang and it's this application that you can see in here. Also during this we clone the repo using this clone repo. We are building the container and pushing this container to the GitHub registry as well and after that we are using the version one because this is the version one deployment and also we are applying the different manifest within the repository and as you can see the final step will set the image and we will update the image deploying our final destination and our final image as well. As you can see we have the GitHub registry that is already pushed and we already have the second version so we run the exact same pipeline as well that is running at this moment so the exact same pipeline is happening. We have the git clone, we have also the container build. This container build is the exact same thing but we are storing for example and we pushed this to the registry using the version chip because we are releasing a new version and also we applied the different manifest and now it's updating the different deployments and using this to deploy our application. So our pipeline is finished. Again same as the steps we saw earlier we're doing a git clone, we're doing a build and push this time for the second version of our application and then from there on we deploy to Kubernetes. If you refresh the app that you've just scanned and the QR code you'll be able to see the latest changes that we've just deployed under so much pressure. Have a look at what those changes are. That's not what we were trying to deploy. What's going on? We've been hacked and we've been held ransom for 2 million handcoins. What's happening? So what happened? If we dig a little bit deeper we can check that our supply chain is hacked. So the first thing that we can see is our source code was compromised and somebody, a group of hackers tried to ask for money and I run somewhere of 2 million handcoins and they also compromised the Docker file as well introducing some changes and they also hacked the supply chain and we can check that we have compromised and they changed the base image and now they are using a base image that contains a CVE of Actors that compromise not only this base image also the whole cluster put this Kubernetes cluster in danger as well. Since we fell victim to this vicious attack we started caring more about security and what we learned was that what happened to us is what's described as a supply chain attack. A supply chain attack is when a third party software gets attacked or gets compromised and as a result all the end users that are dependent on that piece of software or piece of product will be affected. This is often described as a more mature type of cybersecurity attack exactly for that reason because it's a lot more impactful than just attacking one single target. You attack a third party provider and as a result you're reaching thousands of people or thousands of end users as a result of that. So it turns out that the Docker image that we were using was downloaded from Docker Hub and that was the sort of our compromise and as a result anything we built on top of that image was compromised as well. There was a report that was published in 2020 in that report they analysed the data which was related to the supply chain attacks and this is what the graph shows. This graph is copied from that report and as you can see the number of supply chain attacks per year are growing exponentially. As you can see something really bad happened in 2020 does anyone remember the famous attack that happened in 2020 and we've got red hat t-shirts for the correct answer, the first correct answer I guess a red hat t-shirt. Yes, was that was it you? Yes. So we've got an X large and a medium. I'll leave them here for you at the end of the talk. Thank you very much. Thanks. Yes, so SolarWinds was responsible for that big jump in what you saw in the graph in the year 2020. What happened in SolarWinds was that a group of Russian attackers called Cosy Bear they got hold of the update server of SolarWinds which is a very popular network monitoring tool and they just injected some malicious software into the update server and as a result for that over 18,000 organisations who use that update were affected. It somehow reported that the cost of recovery from SolarWinds could be something on a board of $100 billion. Another example of supply chain attacks is what happened to another network monitoring server which was Casaya. Again, they got hacked and then the hackers were asking for $70 million in Bitcoin in exchange for the universal decryption key. Another widespread, perhaps the most widespread example of these attacks is the Luck4j. The reason is the most widespread is because in Luck4j is a very popular logging library for Java applications as we know and a lot of applications out there are using Java so it's the most widespread, as described as the most widespread. So these are just a few examples of supply chain attacks but we see that they're growing and it's not just limited to the ones that we're just talking about here. So what is being done about this? Founded in 2020, the Open Source Security Foundation, or OpenSSF, has begun to devise, improve the defences against the software supply chain attacks. One of the projects is a six-stop project that improved the defences providing a method for guaranteeing the end-to-end integrity of the software artefacts. So the answer of securing this software supply chain lies in digital signing the various artefacts that comprises these applications. But there are several challenges facing this software supply chain because sometimes, and especially in the Open Source projects, the budget for these digital tools is very, very low or non-existent for example and the software itself is changing very frequently and the management of these private keys are challenging. So six-stop, that is a project of the Linux Foundation, it's a new approach for signing, verifying and protecting software. It offers a set of tools that the different developers can use to sign the software releases and on the other hand, also the users can use it for verifying these signatures as well. And we have three major components in the six-stop project. First is RECO, COSINE and FULSIO. RECO is a built-in transparency and some service. On the other hand, we have the FULSIO project that is a free-route certification authority, a free-route TA and we will focus in this demo on the COSINE for container signing, verification and storage that makes signature invisible infrastructure. So we're using six-stop in order to sign our images and push our signatures but we still need another product in order to be able to verify those signatures against our images and this is where Qiverno comes into play. Qiverno is a Greek word and it means to govern and it's a product which is a Kubernetes policy engine and as a Kubernetes policy engine it allows you to verify, mutate or generate Kubernetes resources. One of the most attractive features of Qiverno is the fact that it's all in YAML. So if you're already familiar and working with Kubernetes, there's no need to learn a new language. It's already there and the good thing about YAML is that as human beings we pretty much could understand what the code does just by looking at the few lines of YAML. Now, if you look at that code, we've got one more red hat t-shirt to go if anyone would like to share what they think this piece of software or this piece of YAML does. Yes, what I can repeat your answer, there's a microphone there, it's a bit far away. Correct. Yes, that's exactly what it does. So it takes an image, first of all it's a cluster white policy as you can see in there. The action is enforced so it makes sure it does it and it verifies the image against a public key that is already got and then based on that it decides whether the image passes or not. Now, let's look at what are the toolings and how are we using this? What are the toolings we're using and how are we using these toolings into securing our demo? So to secure the supply chain we are using different tooling that we have in this picture. We have our workflows, Cossine, Caverno and AgostiD. Our workflows we already discussed and showed the UI as well for running the different pipelines that we have. Also we are using Cossine for signing and pushing the different signatures to the grid health registry. We are using Caverno to verify and check the different images as for example we checked with the cluster policy and as well as Agro workflows in a separate use case we will introduce AgostiD to show how Caverno can use to protect also the Kubernetes clusters in continuous deployments or CD processes as opposite as the CACD in Agro workflows. So this is to show you that we are using AgostiD for deploying all of the components that we need to install the demo and this is all managed by AgostiD using GitHub as well. We can go directly to the Agro UI. We have three main applications, Agro apps. One is the Agro workflows. We have other deploying Caverno and finally the workflows and blades as well. We have this Agro app of apps pattern that is managing the different AgostiD applications as well. If we go to the workflow templates we will see that AgostiD is managing the different building blocks that we already have in this pipeline. We have different, for example in this case we have the sign image that is a workflow template and is fully managed and fully deployed using the Tops and AgostiD. So if we go directly to the workflow templates we can see different things and also two different CACD workflows. So we will deploy the next, first we need to deploy the policy. This policy is as you saw before a policy that it's a cluster policy for checking the image against a public image and on the other hand we will kick another pipeline that includes in this case this sign image. This sign image is a step that additionally will use cosine for signing using a private key the image and will automatically push the signature against the GitHub repo. In this case in the GitHub repository we will have in the GitHub container register as well we will have two different things. First we will have the image and also the signature because we are using this for pushing the signature as well as you can see that it's running properly and it's cloning the repo and we can see the different steps. So with the workflow that Roberto just ran we are rewinding to the first step when I started setting the story about deploying our application. But the difference is this time rather than ignoring security we are implementing those security steps which are signing our images and then verifying them against the sign signatures here. So instead of doing the steps that we were doing which was the git clone build and then push and deploy to Kubernetes. Now we are doing the git clone we are building our image and now using six store we are signing the image and also pushing the signature to our container registry as well. And using Kyveno as we just saw then we verify this images against the public key that we hold and based on that we decide whether we want to deploy into Kubernetes or not. So we will check if now it's in sign state it's signing the image so the first place we are building this container image. This container image will have a specific version that we have the version 3 tag that is v3 signage. This is pushing also this image to the GitHub registry. Then we have the sign image as we commented the sign image is signing the container image that we already deployed push to the GitHub registry. And it's pushing also the signature into the GitHub registry as well. And if we check the GitHub repository we will see first that we already have our container image with this specific tag and also alongside we have the second signature that if we checked matches with that. So in this pipeline we are first building the container image and pushing the signature to the GitHub registry. And also Kyveno it will grab this signature and will match and will verify against the public key as well. So in this case already we deployed our application and if you run again your application you can see that effectively it's deployed. So if you already had the page up on your mobile phones if you just refresh the app or just rescan this QR code you'll be able to see that now we have a healthy version of our application running again. Now let's go back to the scenario that we had to release under pressure and we were ignoring security because we didn't have time for it. But then we got hacked and then we realised now we need to care our security. And knowing what we know now about the tools we just talked about let's see how we can use those in an event that we're being hacked to prevent from those hacked images to be deployed to our Kubernetes clusters. So this is what our steps look like. We've got the git clone and build image and if you remember when we were doing the diff on git we were attacked on those two different sources. One of them was the GitHub source and one of them was the container image that we were using. But now because we're using Kyveno and we're only allowing the signed images to be deployed to our Kubernetes clusters because these images are tampered with they're not going to be allowed to our Kubernetes clusters. So we just put the stuff in there. So even if we run the workflow you're going to see in a minute the workflow is going to get to stop. So we will rerun the exact same hack and meanwhile we will present the second scenario when we are waiting till this finished and we can check also the last scenario that we have. That it's deploying the ArgoCD and securing the ArgoCD applications as well. So we will deploy the last demo and then we can get back to the previous demo in order to check if Kyveno did unsafe today as well. So we are using ArgoCD for deploying also our applications but imagine that somebody hacked our source code and also the GitHub repository that ArgoCD is linking and they pointed out to one specific tag for the image registry. And this GitHub registry shows that effectively have hacked as well and somebody pushed this image registry and hacked our image registry. But using Kyveno we'll check and verify the image. We'll check for the different signatures and then we'll deny the request because the signatures will mismatch. So as we can check directly in the ArgoCD we can check that effectively we have this application that we have a sync failed for what reason. Because Kyveno through the admission webhook this blocked the different resource and denied the request because the image verification failed because when verifies the image shows that the signature mismatch. And for this reason it's out of sync because cannot deploy the application because the signature mismatch and then Kyveno saved the day. And on the other hand the exact same scenario using our workflows as well show that Kyveno will prevent of deploying the wrong image because it's happening the exact same thing. It's preventing to deploy this application and as we can see in here if we check the logs of the container the Kyveno admission webhook denied the request because checked against the cluster policy of the check image and verifies that the image verification failed because the signature mismatch. Then also in both scenarios first the Argo workflows and also in ArgoCD Kyveno saved the day and also along with the 6th door signing the image. So we saw today how some parts of our github's workflow could be susceptible to supply chain attacks and we also saw that how using Kyveno and 6th door together we can prevent this from happening. So next time you have five minutes perhaps over a coffee break I'd like to invite you to have a think about where this solution might be applicable to the way you're running your pipelines and your github's workflows. And also how you're going to take this learning and implement it to your work and not only your work the work that you do with customers partners or colleagues of yours because after all it's a chain and we're all in it together. Thanks for today. Next slide we've got all the links we used in the demo and if there are any questions we'll be here over the break as well. Yeah.