So first of all we wanted to thank you for taking the time to join us welcome We really appreciate you're going here. There has to be 15 different things or 20 different things We couldn't do so your presence is very important to us And hopefully if we don't inform at the least we'll entertain right? So before I get started what what we wanted to cover today was four things the first one is we wanted to give a brief Overview of the session. I'll take you guys through it My colleagues over here will then go through the challenges of what we're facing now earlier on we've had we've heard several times in today's Keynote sessions that now the the majority of our of our open-stack community were now in production Later on I'll go through some statistics So now that we're sort of in the in the middle to the tail end of the engineering problems of the cloud The biggest problem that I feel we actually face is a migration of business users into this cloud There say that we'll also talk about the solutions. What strategies tool sets and services and processes have we seen? So so as a bit of a background I work for a company called Ericsson and transformation is something that we do very well from Transforming networks transforming next-generation OSS and basis systems Transforming IT systems transforming data centers and hopefully the combination of what we've been doing from the traditional world to the new Virtual and cloud world we can give you a flavor off today and finally a forward view What is it that we together working as a community can put our heads together now? We we're working with different partners and trying to solve this migration beast this migration challenge and Then I'll give a run-through through it But before I do that let me start off with some introduction. So my name is Earl Villanueva I lead a services unit within Ericsson that just does cloud platforms We're actually in the in the open-stack top 20 list right now To my at the right most there's the gentleman here with the name of Fred Karris who's somebody who's done things from not not just large Open-stack migrations and deployments. He's even done things that he probably shouldn't have told me with spy satellites and what not Rodrigo Morales who's a lead of our cloud center of excellence. He's also an excellent excellent open-stack architect So hopefully we'll be able to share with you the examples of the pains that we've gone through the learnings that we've had Now speaking of learnings it I thought I'd start off with this one little picture that it seems that now the more and more that we get into it The more and more that we get into open-stack seems to be things seem to be getting harder not easier Okay, we've deployed open-stack now. I need to figure about the life cycle management. How do I update it? Oh, okay? Now now if I'm deploying a new a new next generation network I'm not just talking about deploying a new VEPC, but I'm also figuring about what about my underlying cloud underneath Because of course you can't the next generation network needs to sit on top on open-stack cloud for example Now if we if we look at the the data There's a big debate that I hear time and time again with our clients should we go with a public cloud route? Should we go with a private cloud route? Right now obviously and we've heard this in the keynote I think it was Boris who mentioned that earlier that right now in terms of sheer dollar spend It's the likes of Amazon who are kind of opening up the market the the azures of the world But if so if the answer is should I go should I go public should I go private? Okay, sheer numbers. Maybe it's plug public, but wait a minute based on a survey 71% of everybody is actually doing a hybrid strategy So people are and what we found this in a lot of our important clients. We there's one group Pursuing an AWS strategy for example another group pursuing an open-stack strategy So 71% of the people are using a hybrid cloud. Okay, it gives me it's that that's not a good answer Well, that means you have to do both So then we started to look into the numbers from a market data perspective and say if I had the hundred dollars Where should I be spending my hundred dollars? So first of all if I look at it from 2015 to 2020 everybody has a 2020 vision There's going to be a time-stand spend spend in open-stack So what this means to a lot of us is that we're going to see a lot more executive interest management interest And we've heard this we've heard this from the likes of Volkswagen AT&T Congratulations to AT&T and winning the the super user award. We're seeing this trend in proof right now We've heard it with our own with our own two years now in terms of growth rate The spend in private open-stack Private clouds such as open-stack is actually going to outpace that of Publix cloud now There's a reason why accent why why AWS for example is is announcing their partnerships with Accenture's or Ericsson this this is something that we announced in the Mobile World Congress because if you look at the sheer growth rate 36% Versus 19% okay Maybe what's happening is that the momentum that each of us are building in the community is starting to really pick up now If I go into the numbers even a little deeper Let's see where the quality of the growth is at so from from one of the reports that we've looked at where they compared Okay, they segmented the the the the both public and private cloud consumption based on the number of VMs Just from the so it so it's practically a 50% growth if looked from a 22% benchmark from 22% to 31% of large Private enterprise clouds were private clouds were on we're on Enterprise clouds were on the on a private cloud of course open-stack is one of the the fastest growing Private cloud for private cloud types out there So if I look at what's happening now if I look at the growth spurt and if I look at where the quality of the growth Is large enterprise clouds? I think it's an affirmation of what we're doing and what we're hearing and what we're striving to do Now we've heard many times the whole pets versus cattle discussion So a lot of our efforts right now is in engineering the cloud and that and too often the problem this okay Now that I've engineered the cloud mr. Business users. I have a fantastic CICD environment. I have a fantastic DevOps capability Let's start moving on the first thing there is that how many people are actually ready to move into the cloud So it's not just how many how many? Cloud native applications are actually out there. How much work do you need to do to make something closer to the Tosca type of model? In a pets and cattle's paradigm that a lot of us drive towards it kind of takes care of itself But the reality is if you do a wild migration Thousands die now you might like I said you might have the most advanced DevOps capability, but at the end of the day Many business stakeholders will say okay. You have all this capability, but I need a migration window. I need a certain batch schedule. I need a u80 type of test So more and more it starts to go into good old waterfall sometimes, right? So rather than thinking of it as a oh now that we're in cloud its pets and cattle. I can just migrate people over What Fred where you're gonna? I started brainstorming last year said we were saying hey we need a better Metaphor to this migration then we realize that you know what in the US that people move an average of 11.4 times in their life They're more or less going to understand what we mean when we say if you think about migration into an open-stack cloud The best the best thing that each one of us can can relate to is when we ourselves move right and when you move You're not just putting your things in boxes and moving it.  You're moving your mailing address You have to go and change all your bank accounts or credit card statements So imagine you're just one person and it's moving as a massive change that you have to go through What more with with a tenant where I I have millions of Transactions that I need to worry about hundreds and thousands to millions to tens of millions of customers Why do I move? What's a TCO for me? What preparation should I do? How do I know that I move everything down to the network settings and my security certificates? How do I test how do I unpack and make sure and once I'm there? How can I take advantage of my new home or take advantage of all of the features that open-stack has so with that I'd like to pass over the floor to my colleague Fred to take us through through this more perfect, thank you Earl and Yeah, I the more I talk to Earl and to Rodrigo and other colleagues that have been involved with some of these large migrations in the past and current migrations to the cloud the more I became convinced that the The sort of the overall metaphor of our move is is absolutely correct. So As Earl was describing, it's not just your Lot your boxes that you're moving when you move your house you're actually moving your life and the same thing Occurs when we're moving Open-stack large application systems of the tenants in the cloud environment These are operating businesses they've got real customers and it's their business life that you're actually moving so The sort of approach is for a typical migration and just to put it in parallel with this is You know just as if you were moving you would basically decide to start looking at what? Hey, where do I want to move? I want to be in this school district. I Want this size of house my family is expanding those type of things So there's an entire move sort of strategy and then discovery of of all of your your needs That has to happen and then ultimately hey my long-term plan is to get into this city this neighborhood this cloud by the way and then After that we basically start wanting to do the detailed look just like the detailed planning which For the migration itself comes down to some things that I'll talk about here in a minute But in the house analogy, obviously we start inventorying how much furniture do I have and those type of things? Then there's the execution. That's actually the day of the move And I think if there's any point that I'd like to make sure we get across today is It's not just a technology problem any more than a move is simply a truck problem There's much more to it than that After we move we want to make sure Do our verification everything in this operating business this life is ready to go and then finally I'll talk about Optimization as well Okay, one other thing before we start going through the process. I wanted to mention about the Successful migration approach is really very holistic And it has to incorporate elements of people and process I really liked what one of the speakers said this morning in the keynote addresses about how it's a cultural shift I mean those are people and process issues not just technology issues and One of the things that I found is extremely important as we approach these things is to get cross functional Participation and as you'll see there's a lot of different moving parts as we go through these migrations It's just not simply the cloud technology and the tenant VMs or workloads The second thing is we're looking to do I think an unprecedented way of migrations with this very sizable expansion of clouds and we hope they're open stack clouds in the enterprise environment We have to industrialize harden these processes one so they're not susceptible to error But also so we can improve them We'll talk a little bit about that as well and then finally there is technology involved These are large-scale migrations anything that can both automate it and make sure that it's foolproof is something that we need to concentrate on Okay, first a deep dive down into the these elements So on the strategy the first thing that we found is the need to go ahead and Work with the enterprise that's starting a large-scale enterprise cloud buildup and you understand what their strategy is for for rollout one thing particularly important if if the enterprise time scale can allow and we know we're doing it rapidly but There's there's different options right you could move your your your most big applications first or go for early adopters first We'd certainly recommend doing that Approach if you can simply because you want an early adopter that he's gonna go through frankly a real rigorous discovery exercise Migration strategy with tenants understanding their business issues Where they're gonna be located what their requirements are vis-a-vis their customers because these are operating businesses And then we have to look at that cloud discovery We'll talk in a second about how we have some automated tool sets and then more are being developed to do this type of work Looking at the actual application architectures out In these environments because here's an interesting thing we found in the enterprises. We worked with Even where applications are currently resident on clouds They are not 100% cloud ready there. They tend to be hybrid 80 20 90 10 On the cloud but also for instance external networking That has to be engineered into these moves as well. So that's a very important Function and finally there is the overall right roadmap. How are we going to get you over? Mr. Tenet you operate mr. Mrs. Tenet you operating business because we want to make sure that we get you over You know your active active passive setups in the right way and and so forth So those are considerations that we take into account during this phase Now I just mentioned about the discovery process The business Perspective is clearly understanding exactly where the business Is in terms of their operations so that we can now schedule them and move them But there are some technology tools and ways we go about the rest of the discovery and for that I'd like my colleague Rodrigo to talk. Thank you Fred So as Fred was mentioning earlier is not really a technical challenge to my great attendant But the technical part is very important to write so Other than all the process that you need to do in order to handle all the Tenet requirements you need to make sure that all the the virtual Infrastructure that the tenant has in the legacy cloud is going to work in the the new clouds the destination cloud for the tenants so if we look at open stack and everything that that tenant has for a Virtual infrastructure so starters networking virtual routers Virtual machines the sequence that you need to create those virtual machines in the destination cloud everything Needs to be accounted for so as part of this discovery process that Fred was mentioning You need to account for all those things because sometimes the legacy cloud is completely different from from the new cloud You may be changing the architecture complete the architecture Completely in the the new cloud and you need to account for all of this you may changing the Networking for a software defined a network that is completely different So as part of the discovery process and you need to go through over all those those challenges Technical challenges and make sure that the tenant who is going to to work And perform Accordingly in the destination cloud Thank you. So next step of course detailed migration assessments and preparation The first thing that I want to stress here is the need for labs I mean, I think most people in in agile development open-stack work Appreciate the needs for high fidelity labs. It's that and more when we get into migration for two reasons one as Rodrigo was just saying the tenants are actually moving even if they're from a prior addition of an open-stack cloud To a new version and maybe a new architecture Getting that vetted out and certified is Incredibly important to do that before the migration rather than where we're in the active phase of actually migrating workloads over and the second reason Is we need to have a way of certifying our migration tool? I mean a migration tool and we'll talk about that in a minute to Rodrigo go over some of the technical aspects is really a big transform function going from cloud a to cloud b and Making all of the very very sophisticated Adjustments not just copying workloads and pasting them over but all of the different interactions that happened between The VM and application and networking for the tenant setup in the source cloud to the destination cloud There's also what we found in in moving some very large enterprise Applications as I mentioned before No tenant that we've dealt with in some of our large adopters of open-stack our 100% cloud certified there they've got special requirements could be external networking could be certain storage type of of things that requirements that need to be Incorporated into the new new cloud made sure and because it's not there when we move them I can guarantee you from personal experience the migration team is the one that's at fault So we want to make sure that that's taken care of and then finally it's really phasing out and understanding What it's going to take to move these these workloads We've moved now some large enterprise applications that have a storage volumes measuring in the many terabytes hundreds and hundreds of virtual machines and very large storage So planning that out is that going to be able to be accomplished in one day? Five days those type of things so that we understand what the time impact is going to be and realize that we're operating in Production zones we'll talk about that in a few minutes So that's a very important thing as well to take into account how we approach this So with that I'm going to turn it over to Rod Rigo and let him talk about two of the technical areas again so again mentioning the the lab environments right to test the the migration process right what sometimes We saw happening is that the some of our customers they they will start with the Very early open stack deployment They they struggle a lot trying to make their applications to work in that environment they spend a lot of time then they change the architecture they go with something new and They don't test the migration process in in a lab that really reproduces the the legacy cloud and The the future the new clouds that were where the tenants are migrating so Well, it's it's key to have an environment a lab environment to actually simulate those situations and and then run some tests in an environment that actually reproduces what you have in production, so It's very hard to build a lab reproducing a legacy cloud, but it's it's needed and and also the The new new cloud deployment the new cloud where the tenants are migrating to It has to be made available to to the tenants to certify their their applications there because the architecture may be completely Different and they have to run their applications there in a lab and make sure that that they're going to work after the migration Okay talking about migration engine, right There there is part as Fred mentioned it earlier There is part of the the the migration process that there is a only processes But then you you need some sort of tool to do migration especially in large dealing with large tenants with thousands of virtual machines with a huge storage Space that you need to migrate sometimes through a new storage technology So this is just a very high-level architecture of a migration engine where we have The the the component that is responsible for scanning the the legacy cloud and and these Scanning components should be able to actually log in as a tenant Right and try to to find to discover all the virtual infrastructure that the tenant may have Including all the virtual machines the networking everything that is involved For that tenant to work in a legacy cloud and then later the migration processing part of the This engine should be responsible to actually copy things from the legacy to the new cloud And that is a key process especially when you're dealing with large amounts of data The networking has to support this migration process If you're parallelizing things it has to be very well controlled because there must be certain things Things created in sequence in the right sequence You need to first lay down the virtual infrastructure with networking Storage everything and then you start creating the virtual machines So there are some solutions, but I don't think we still very very mature in that that space When talking about open stack and open source tools to do this this migration. This is the where all the fun starts when you actually Start this process and you look at the virtual machines migrating from one place to another, right? And then after that you certify the migration and make sure that the tenant is in the new cloud We're great, and I said before it's really not all a technology problem But there is actually one of the technology problems I'm I'm I know of at least three different independent efforts from three different companies to build these Migration engines Erickson by the way my company being one of them, and I think I'm safe to say no one has has Got it perfected yet. We're all on that road to discovery and part of this session Is actually called action to even see how we can get that more Industrialized for the future because the wave is coming now. It's execution This is moving day. This is the day that the moving van shows up As of right now We don't really have a good way within open stack for cloud migrations to do a live Migration where we can actually keep the VMs and workloads up So just like on your moving day when you move from say an apartment to your first house or from one house to another You probably took the day off and monitored the whole thing and this is exactly what happens as well in the scenario of a migration Currently so there is a very sophisticated Procedure that has to be built because there's a lot of people involved a lot of technology involved and in any enterprise that you're dealing with The migration team is going to conform to whatever the operational procedures are for working in that IT operational environment because you're usually working in a Cloud that is actually in production and may be taking one of 10 tenants that's on that cloud and moving them over while not impacting the other tenants and then the same is true For the destination cloud so all of this is happening against a backdrop of keeping Not interfering with the operation of other tenants within those clouds But for the tenant themselves there is the freeze they're taking their time off and there is a change window usually put into a Thing into effect and if other impacts are there as well We've dealt with scenarios where one tenant was actually coupled to another tenant application feeding data Obviously all those cutovers have to happen in in sequence and then once we've moved everything over and this is where the Automated process becomes so so needed with this engine The complexity of these clouds and the tenant interactions is is so great that frankly while you could Theoretically have people do it by script. It would be impractical from an accuracy Perspective with with hundreds or thousands of VMs and it certainly wouldn't be very efficient And then finally we obviously use do a quick look sort of a verification test But that's followed by our post move Verification and acceptance and this is a process that literally can go from several days to several weeks As a tenant gets over onto a new cloud depending on their level of complexity that They will want to run through a rigorous set of tests before accepting the live customer traffic and then There's usually a soak in period of burn in to make sure that hey There's just no interaction before we start engaging live customer traffic internal or external To the enterprise So that's sort of these these sequence for the post move verification acceptance As a migration team that has to be worked very rigorously with the cloud tenants before you get into this process so it's all understood how you go through and Certify the end result again, I'm fine. Oh, there's there's no And to to this process without what I call optimization once you finish your house move, right? You get everything in you've sort of unpacked your boxes, but now okay I'm gonna put the pictures here or there or arrange the furniture this way I think I like it this way we all do that, right? This same thing happens as the final sequence of a migration. So first of all There is a need to redistribute workloads now in the new cloud to get the right level of Affinity settings and availability and so forth that the application Desires and had in their prior cloud There is also Frankly some hand-holding there's new services available with each release of open stack and the tenants want to consume that some They know about some they don't My my experience is there's no one better to hand hold the tenant through this process than the migration team So it's really sort of an onboarding and migration team to get them exposed to The new features the the new areas of the cloud environment that they are now in and then finally Many of the large tenants we work with are in a cloud network They exist in different geographic locations You know have high availability active active passive type setups And so there's actually the then bringing those online in the proper sequence and getting them restored I'll say to the exact level of high availability. They were before we went through this migration So that's the the overall scenario. I hope you saw the analogy to the house move Because I think it's very very accurate But I think this is the type of process from start to finish that we propose needs to now be industrialized with appropriate technology backing in order to Make our process is hardened to the point. We can go through the upcoming wave of migrations in the enterprise private cloud environment Finally I have to mention about governance So as you can see from the the model here that you know, we tend to think in the open stack community You know about this wonderful software. It is great software, but there's frankly several other degrees of freedom here Organizations that are involved one is the data center infrastructure and then finally the cloud tenant and of course all of this runs on top of the enterprise sort of cloud governance who owns the cloud and We need to basically bring in to play Coordinated governance and program management across this thing so no Migration story would be complete without saying across the the the entire process at the very beginning bring in Your your key stakeholders from the tenants from the cloud Organization development and so forth to guide this entire process that I just described Okay, girl. Thank you Fred and Rodrigo now on the tenants By the way before I get into these last two slides before we open up for the for the open forum in the Q&A I just wanted to plug that some of my colleagues have a very very interesting session tomorrow called Open open sack tenant perspectives So what we did was say we actually ran a survey We also did in-depth face-to-face or over the phone interviews with different open sack tenants across our different different clients to get what they need and and it's part Of our migration practice that we have now From my own perspective from my personal perspective We have a lot of work or potential work around legacy cloud to new cloud from public cloud to open sack cloud to some other Internal cloud including open sack clouds to public cloud and and and and through throughout all of this What what I see is that there's a big groundswell of support now having having said that We went through the approach we went through and I think but like it's it's by now It's clear to everybody that migration isn't a trivial matter It isn't just a matter of shrinking and growing VMs and moving workloads across But it's actually a fairly comprehensive systems integration approach that we need to we need to think about of course over time What I'll get into hopefully we solve this together over time But I just wanted to point out that if you think about what's the most impossible and crazy cloud Migration that you can possibly ever think of to actually have a colleague in the audience by the name of Palash I won't single him out because he's too modest But we're he's actually running a program in one of my clients before we're we're taking a mainframe system We're maybe the last major code update was in 1994 PL one and cobalt were modernizing it and with the end goal of Well, maybe I shouldn't say how long exactly we planned it It's not it wasn't a short program with the end goal of moving it into a cloud So if if you can consider moving a mainframe system Last majorly built in the early to mid 90s and move them into an open stack cloud, you know It's it's only our imagination that limits us. So from a visionary viewpoint What we hope that together as a community we can work towards is that migration happens with zero downtime There's a lot. There's a very important temptation that we have to be careful about You're there you're presenting to your to your your your business owners and they're saying hey Well, we want to do a live migration. We can always try to do it There are other ways to mask it if it's a true cloud scaling app it a cloud native app You you can shift components off it so the end end user Result is different but at the end of the day for the virtual machines that you're touching right now It's very very hard to have this no zero downtime The other thing that we hope to get is some migration happens at the push of a button We talked about the migration tool sets that we've been developing on our own with Ericsson With Ericsson and other partners or from partners that we leverage and in each case in each case It's a it's it's either something built from scratch Or it's something where we use this like a tool like a cloud management platform And we have a lot of scripting on top of it Right now with there's some degrees of automation that we can do but I think we're not yet There were a migration that happens at the push of the button and finally when we talk about migration It's not just a linear Journey from legacy to cloud but where we see the market heading is that migration will actually be a multi-directional movement across From your legacy to open stack open stack to feature open stack open stack No, maybe a public cloud or maybe a public cloud back to open stack So my last slide is really a call to action a Call to action to the open stack community Industrialized migration is needed. We're working with some of our partners in different projects that that hopefully will will at one point be accepted as part of the The core industrial migration is needed for the because because the rate of production Adoption is just simply increasing the rate of open stack adoption It's increasing and the only way to do this is for the community working on well-defined projects or well-defined Workstreams and from an Ericsson perspective and and I know my partners feel the same way that that we welcome welcome you joining this effort so with that We talked about migration being a beast so hopefully working together. We contain this migration beast So with that we'd like to open the floor now to questions and answers and Fred and Rodrigo here can help me out Yep, and there's so one microphone there and one microphone there. So feel free to ask away. Hi My name's on a kid cloud engineering at box Here's why the moving day analogy doesn't really resonate with me In our production environment. We have hundreds of services Managed by dozens of development teams and when we think about a migration It's usually a phased approach where we have services moving over to the cloud Then interacting with other services that were part of the legacy environment as one larger ecosystem That being one thing the other thing is when you think about a moving-day analogy What do you do with the millions of dollars of infrastructure that make up your legacy environment? Okay, that's a way. Did you want to think I'll let me attempt to do that. So When we're talking about the migration of active tenants at least in our experience my experience it They have to be they can't be moved in a phased approach They're existing on one cloud and they need to then be instantiated and come back into operation on the second cloud So it's a very complex operational problem if if we didn't have that issue We could live in this sort of bimodal environment for quite some time so My perspective is coming from once again I don't know if this is where you were coming from or not But my perspective is in an operational environment We simply don't have the time to go ahead and and sort of do this long more drawn out And by the way, I would admit Logical phased type approach the time and the operational and production needs just don't support that So there are cases where we can group different applications that are fairly self-contained and this becomes a unit of a face But what I'd also like to address you because you raised the second part of your question is really important about what to do with the Infrastructure so first of course, we know that there's this big wave to move into an open compute type of infrastructure Within Ericsson. We also have our own solutions there just like many many other of your partners And in this moving to a new opens I want to have a Google or Facebook like data center It's a it's a different question But one of the strategies we have to try to preserve the existing Investment you've made in let's say your your storage devices your blades that we try to do on an In zone or an in data center implementation. So for example, we spare out some servers This is where we deploy the new version of the open stack and earlier on I was making an illusion where we start to shrink VMs and shift VMs across so as I move workloads over I'm growing the new cloud within my data center And I'm shrinking the old cloud so that's the one of one strategy that we tried But thanks for your question. So in that sense, it is a phased approach then for certain applications You will be doing it same day But what you're essentially doing is from your entire ecosystem you're shrinking some and growing Oh, okay, definitely, right that actually by the way makes a lot of sense And that is exactly what Earl was referring to actually a migration We've just been part of for the last nine months is doing exactly that in the same set of Zone or set of racks in a data center Literally shrinking the one cloud as we're migrating over so when we're finished instead of just deprecating the equipment It actually now becomes the new right clock. So by no means are we suggesting a big bang approach Anyway, there's a gentleman who had the question. Oh, maybe if you don't mind, sir We'll just go over to this side and we'll switch back to you Maybe do quickly dovetail on the previous question Proportion of these migrations. Do you see that happen within the local data center as opposed to public clouds? huh so in terms in right now the Right now there's a lot of and this one. I don't have hard data There's a lot of business interest into AWS for example, but where I see a lot of Harder traction happening because it's like a quicker hit is a movement from let's say a VMware VMware into open stock I think for AWS because there's a very AWS Requires has a very specific governance model very specific way that you have to operate and manage So a lot of IT shops they see a lot more control with if they keep it in-house But I don't have hard data on this but that's a very good question. Yes, sir First thank you for the presentation one interesting thing you said was if I heard you correctly these days It's not a good idea to script everything and it's much better to have a live person do it Can you give me an example or two of things that can't be scripted these days at least to that a reliable degree? Well things that it can be really automated is is for example the creation of virtual machines in the right sequence respecting the affinity and entire affinity rules and and the creation of virtual infrastructure like virtual routers and and Whatever you need in the destination cloud Some some of the tenants that we we migrated they they have like hundreds or even thousands of virtual machines So you you can't do those things manually, right? You cannot create everything in the destination cloud using people so you have to automate that also the Transferring all this data. You need to have something Automatically doing that right you you cannot have people clicking those things and And also the test part after you migrate you need to run some automated tests That is a very important part of the the automation right there, right? You cannot have people executing test cases and manually depending on the size of the tenant If you have a small tenant with three or four virtual machines that may be possible But most of the time you need to automate and let me I think though You asked for a specific example of hey something that couldn't be automated So in our experience like I said what we found in the enterprise environment is hey, we they make Our clients our tenants may be ninety ninety five percent I'll say cloud cloudified and and and and all that but there's still a lot of external networking We've also so that that's one example that can't be automated or is hard to automate Another actually is is is as you're moving from a source to destination cloud. There are Potential conflicts in IP addresses if you just move tenants over and and their virtual machines and the new system The new cloud system starts assigning their IP addresses There is the potential for conflicts there and so those are best handled in a manual way We haven't found a way to automate those yet Thank you for your presentation You present the strategies for migration or migrating business critical application to open stack I haven't shared anything's about the security boundaries on how to mitigate the risk and what's the strategy to migrating These critical application to open stack. I think that alone is it's a whole presentation, right? looking at the security point of view but some of the the things we were mentioning they have to do with security for example the Certificates that you may need and and again mentioning the networking if things are changing, right? And and you need to to to make sure that all all your networking or all your security part firewalls If they if you're changing IP addresses Are you going to reflect on the new cloud all the the security aspects that you had in the legacy one? so It's a very broad Subject, but but there are several aspects that you need to take into consideration Those are great points rod and maybe the other part of your question is from our risk management perspective This one sometimes it can also one asserts the usual. I need the appropriate testing. I need the right rollback I need somebody from the business owner to actually do the verification like what we talked about but The risk here and and there's no I can't think of any efficient ways that sometimes the There the next level of resiliency will actually depend on the tenant itself like for example The behavior of its load balancing capabilities. We we've had seen we've had instances for okay. I might have Three machines as I say a broad example. I'll shift one first Okay, then how does my load balancer behave so I know okay. He's now over here, but he's down Okay, he's now up now now I can load balance across three now. It's time for a machine number two So once you start to go into discussions like that It's almost as if you're doing it tenant by tenant. There's no one-size-fits approach. That's so far that we've seen Yeah, I I'll bring up one other thing too and and that is as I mentioned early on one of the key activities up front Is a deep dive architectural assessment? So when we're lifting and shifting over naturally all of sort of the the perimeter cloud security that gets instantiated But the architecture that the tenant with their firewalls and things like that that they've actually set up within the boundaries of their zone That needs to be very rigorously looked at from how you set yourself up in the source cloud And how is that going to work as we move you is it still going to provide you the exact same level of security or not? So that's actually something we do and frankly it's done by people like Rodrigo that have the technical ability to do it Yeah, some other aspect is do remember that we mentioned the lab right a high fidelity lab So you need to make sure that your new cloud All the architecture that you have there it adheres to the CSO Organization and they will actually look at it at your lab and they will certify you According to all the rules that they have so thank you. Thank you Well, thank you guys you've been a wonderful audience We think this is a very important subject and so feel free to reach out to me Or my colleagues here, but you use me as a point of contact I would like to hear from you and hopefully there's an area that we can generate momentum in the open-stack Community going forward because it's going to be needed. It is needed and I think we're all up to the challenge Thank you


All right, Cliff has a quick tip for us that's really kind of more of a hacky thing, which I like. He says, I have a frustrating PDF problem which I solved. I received a filled out PDF form for my doctor's office for work, which was of course password protected because of HIPAA compliance. I could not submit the form to work password protected, but the obvious menu options in preview would not remove the password. Most tips on the internet talk about using the export option in preview to resave the file without a password, but all my attempts resulted in a still-passworded file. Finally, one tip noted that as a last resort, use file print save as PDF, which worked. So I guess my tip would be that preview file export no longer works for this, but save as PDF does. Do you clever geeks have another easier way to remove PDF passwords? No, and I don't think the export one has worked for a while because I get tax returns from my CPA that are password protected. And the first thing I do is I immediately save a copy that's not password protected because the last thing I want is when I need to go look at 2015's tax return for whatever reason, some college wants it or whatever. And then it comes up and it's like, what's your password? It's like, I don't know, that was like five years ago, dude, I don't know what the password is. So having been in that scenario exactly one time and having to spend whatever 15 minutes hunting for the right email from Bob to show me my password, I now just save him, save as PDF. And that's how I've always done it is that way. But now, of course, you can use the quick tip from a pilot Pete in Mackieke of 900 to make that command PP and boom, you're good to go. So I like it. Hopefully that helps Cliff.


gonna call this my list it and forget it Bolo why because I listed this in 2020 April of 2020 I think it was so three years it took to sell but guess what it sold and on a slow day when I don't have a lot of sales I am super happy to sell a very stale item for $12 and I think 30 cents buyer paid shipping I probably have less than a dollar in this I picked up a whole bunch of voids bear plush some sold really quickly some take a long time to sell but either way this has just been sitting in a tote waiting for the right buyer list it and forget it that way you constantly have new sales coming in now I know this method is not for everyone let me know if you like the list it and forget it method or if you prefer you don't like it I'm okay with long tail let me know what you think down in the comments thanks for watching


A lot of manufacturers have released pretty competitive business machines, a market that's usually pretty well covered by Lenovo. Let's see if that's still the case, as we check what Lenovo has to offer in terms of a challenge with its ThinkPad L15 generation 3. The laptop doesn't have the metal chassis of the lifebook, instead relying on a plastic build, but it really surprised us with its durability. The lid and base are incredibly sturdy, showing next to no flex. As for looks, it's a classic ThinkPad with a black finish and Lenovo branding. In terms of dimensions, it weighs 1.76 kilograms and has a profile of 19.9 millimeters, which is similar to the HP Elitebook 650G9 that we were smitten by a few months back. The lid also can't be opened with one hand, which doesn't inspire a lot of confidence in a laptop as expensive as this one. The display is surrounded by thin bezels, except for the top one, which houses the webcam, with an HD option as a base variant and an optional full HD shooter, a manual privacy shutter, and an optional IR scanner for facial recognition. On the base, there's a speaker grill above the keyboard, next to the power button that doubles as a fingerprint reader. The keyboard itself is nothing short of phenomenal, with long key travel, clicky feedback, a backlight, and spill resistance. You can see the red track point in the middle, which works well with the dedicated buttons that sit above the touchpad. The pad itself has a clickable surface and a milar cover, however, it's not the most responsive unit that we've seen. The input output covers a lot of ground, enough to justify covering the left, right, and back sides. On the left, there's a LAN port, one USB Type-C 3.2 Generation 1 port, a Thunderbolt 4 port, an HDMI 2.0 port, one USB Type-A 3.2 Generation 1 port, an audio jack, and an optional smart card reader, which can be used as another security measure. The right side keeps a micro SD card reader and one more USB Type-A port, while the back houses the optional SIM card tray. The full HD IPS display needs to be good, as you'll be looking at it non-stop. It's got good viewing angles, but doesn't get as bright as we'd want, reaching only 256 nits at its peak. From the looks of it, it's not a panel made for creators, due to its subpar color coverage of only 54% of the sRGB gamut, as well as dwindling accuracy. With our design and gaming profile, the laptop goes as low as 3.4, which still isn't considered accurate enough. However, for regular office work, it's good enough, thanks to its zero PWM usage and good contrast ratio which comes in at 1480 to 1. If you want a better office experience with the laptop, you should check out our office work profile, which makes texts and tables more legible so it's easier to read. We'll have it linked in the video description. The sound setup on the laptop is one of its redeeming qualities, as it delivers good audio with no deviations across the entire frequency range. Only 2 per 100 people watching this video are subscribers. If you decide to just start following us, we'll be able to reinvest more in our laboratory thus making even more helpful videos for you. Thank you, you're awesome. Business laptops need to offer good battery life, so with 8 hours and 47 minutes of web browsing, or 8 hours and 13 minutes of video playback, we feel like the ThinkPad should get you through a whole workday's worth of mixed use. The 57Wh unit is larger than the Generation 2 product, however, the elite book once again displays similar results with a lower 42.5Wh unit, while offering a larger 51.4Wh version as well. The Lenovo laptop has a decent advantage when it comes to raw performance, as it squeezes out a higher Cinebench score than the Lifebook, despite carrying the same Core i5-1235U. The laptop is cooled by two heat pipes and one fan, allowing the Core i5 to reach 44W in the first few seconds of our stress test. In the next 30 seconds, the wattage drops to 41W, which is still very good. However, in really long loads, like video rendering, the CPU lowers down to 20W. With that said, we don't think going for a p-series chip inside the L15 would be a good idea unless Lenovo offers a different cooling solution. One positive about the cooling is that it leaves a quiet and cool laptop even at a peak load. The base has a hotspot of 39.6°C, which is still quite comfortable. The upgradeability of the laptop is good, with two Sodom slots for DDR4 memory, as well as one M.2 slot for generation for SSDs, keep in mind that the slot is smaller and fits only 42mm drives. Our teardown video shows how to upgrade the device, so if you want to check it out, we'll leave a link in the description. Compared to the competition that the business market has, the Lenovo ThinkPad L15 generation 3 doesn't represent enough of a challenge. It's heavy, with battery life that might have you running for a charger depending on the usage, and a display that leaves a lot to be desired. However, the laptop will probably enjoy a lot of attention, simply due to the sheer popularity of the ThinkPad brand. For an even more detailed look at the Lenovo ThinkPad L15 generation 3, check out the written review on our website.


Multi-level data can be used for estimating different kinds of effects. In this video I will explain the difference between the within effect, the between effect, the contextual effect and the population average effect. Because these effects have different interpretations, it is important to specify which effect you are interested in. And that depends on your research question and more generally on the objective of your statistical analysis. Books on multi-level modeling typically start by explaining the difference between the within effect and the between effect. But I think it's more useful to understand and easier to understand the difference between the within effect and the contextual effect first. The within effect tells us what is the effect of an individual level variable on an individual level outcome. For example, how a person's intelligence influences a person's task behavior or how a company's innovativeness influences a company's performance. The within effect has a clear policy implication because it implies that when an individual level varying attribute or trait changes, then there is a change in an outcome variable of interest. So if you want more of y, do more of x. The contextual effect on the other hand tells the effect of context. So how do the actions of others in the same context influence individual level behavior? Or the other way, how does individuals actions influence others in the same context? Typically, the contextual effect is explained as what is the effect of a mean characteristic on an individual level outcome. The difference between the within effect and the contextual effect is perhaps best understood through examples. Let's take a look at four examples. The first is vaccinations. So if you vaccinate yourself, then you are less likely to develop a serious disease. So there is a within effect. Your vaccination helps you. But there is also a contextual effect because if others around you vaccinate themselves, then that creates herd immunity, which protects also those people who don't vaccinate. So the within effect here is positive and the contextual effect is positive as well. We can also have examples of a positive within effect and a negative contextual effect. For example, overfishing. If an individual fisherman exceeds their quota, then their profits will increase because you get more fish to sell. If everyone else in the same lake overfishes, then there is a negative effect on profits because overfishing leads to less catches or smaller catches for everyone. So the within effect is positive, but the contextual effect is negative. They may in some scenarios also cancel each other out. Another example, innovativeness on company performance. If a company innovates a lot, then they can develop valuable capabilities that lead to competitive advantage. But if everyone else around the focal company innovates a lot, then innovations are no longer valuable because everyone has these innovations. And also if a firm doesn't innovate, then they will fall behind and their performance will suffer. So innovation could have positive within effect and a negative contextual effect. We could also have a variable that doesn't have a within effect but has a contextual effect. For example, gender. How does individual's gender influence individual's performance in a team? We can say that individual's performance doesn't depend on individual's gender, so there is no within effect. But we can also say that gender has an effect on the contextual level. For example, teams with half men, half women work better than only men teams or solely women teams. Okay, so that's the contextual effect and the within effect. And how does this relate to the between effect, which is typically introduced in books about multiple modeling? The between effect is simply the sum of the within effect and the contextual effect. And it tells us what is the influence of a mean characteristic of a group to the mean outcome of a group. And it doesn't have as clear policy implications or causal interpretations as the within effect and the contextual effect. Then the population average effect is simply a regression line over the data ignoring all clustering. It answers the question of what is the most likely value of y given a known x and it's a weighted sum of the within effect and the between effect or the within effect and the contextual effect. And it doesn't really have a clear causal interpretation. So the population average effect is more useful for predictive applications than the within effect and the contextual effect. Let's take a look at example of these effects from a paper by Anders and Tofiki in psychological methods. So they have data and they have individuals wellbeing here on the y-axis and individuals work hours here on the x-axis and they have three individuals, one, two and three over five weeks. So we have five repeated observations of each individual and these are synthetic data. Now the first effect that we have here is the between effect. So this is how does the mean wellbeing of a person depend on the mean work hours of a person. So we basically calculate means of these clusters for each of these three individuals or both variables. So we have three observations of two variables each and we run a regression on those three observations, those three cluster means for two variables and then we have the between effect. Then we have the within effect. The within effect tells how changing your work hours influences your wellbeing. So it's a regression line that we get when we ignore the differences between these groups. So we basically put these ovals on top of each others. We eliminate all between group differences and then we run a regression line through the ovals and that tells us the direction of an individual level change. So this person here who is relatively well off will never become this bad in wellbeing regardless of how well, how much they work because the only the within effect influences an individual level outcome. And this person is overall for some reason a lot higher on wellbeing than this person. So this is the between effect is the constant stable difference between people and the within effect tells how much variation there is within individuals. Then the population average effect is simply if we run a regression line through the data ignoring all clustering effects and we get another line which in this case is closer to the between effect and that line really doesn't have any clear causal interpretation. There are a couple of relationships that we need to understand within effect and the contextual effect. If there are within effect is zero and the contextual effect is zero, then all effects are zero. So two variables are linearly unrelated. If we have within effect that is not zero, but the contextual effect that is zero, then all effects are equal. So the within effect, the between effect and the population average effect just give you the same value. And this is a scenario where all the individuals are perfectly comparable. All the groups or all the companies are perfectly comparable. So there are no systematic differences between groups, companies or people that we observe or whatever our cluster variable is. So these are our simple cases. Then if there is no within effect, all effects are contextual, then the contextual effect, the between effect and the population average effect are the same. And in all of these three cases, things are fairly simple because we can just run a regression model to get the population average effect, ignore the clustering, and that will give us the effect of interest. But if the within effect is not zero and if the contextual effect is not zero, then all effects are distinct. So the within effect, between effect, contextual effect and population average effect all generally have a different value for a variable. And then which of those values is the one that you should be focusing on depends on your research question. So this is the most common case, which is unfortunate because it complicates our life. But there are also other interesting things in this table. So in econometrics when we do multi-level modeling or parallel data analysis, we typically want to make something called the random effects assumption. And I'm going to explain the random effects assumption in another video, but this within effect is not zero and contextual effect is zero is basically what the random effects assumption is about. Anyway, the key outcome or the key thing to know about this slide is that you need to be specific on which effect you're interested in. So when you write a paper, try to use the term within effect between effect or contextual effect just to let your readers to understand which effect you want to know and why. And then your readers are also better off in understanding if you have estimated the effect of interest correctly. Most commonly what we want to know is the within effect, which tells how changing individual level variables affects individual level outcomes.


Rwyf yn wneud ei fod yn eu cyfnodd? Rwyf yn cael y ffyrdd? Yn ychydig, rydyn ni'n ddigon. It's loud. Hello, everyone. Thank you for coming. My name is Phil Jules. I work at Segirra as a lead developer advocate and I'm in charge of looking after the NFCore community as best I can next time. Thank you all for coming to the NFCore hackathon o'r cyd-22 yn Barcelona. Mae'n gweithio bod yn cysylltu, mae'n gweithio ddod caf yn fwy o'r clywed. Rwy'n gweithio gyda'r cyd-22. Mae'n gwaith cerddiannol yn cerddiannol yn Llywodraeth i'r Cric, yn y ffyrdd y 2020 o'r ysgrifwn, i gyd, mae'r Cyfridd cerddiannol. Felly mae'n gweithio'n gweithio i'r cyfridd gyrddio ar y gweithio. Felly, mae'n gweithio'n cynnig i ymddydd! Mae'r hyn yn ddweud â'n tro i chi'n gwybod. Nid yw gweithio gyda, ym mwyn hanes hynny'n gyllideb yn hygyrch. Mae'n dod am ychydig wedi gweld yn ystryd. Yn y gallwch gweithio mewn wedi'i'n chrym yn cyd-diguru neu nad yw'r hyn ag siwr a'r hyn wedi'i'n gweithio gyda'r hwnnw fwy mae'r fawr. Mae'r mewn hwnnw fwy'r hanes hwnnw yma chi'n gweithio maxime, mae'r gweithi'r demo nesaf i'r Gathau Twn o fydden nhw gofyn i fung ddiddordeb yn meddwl gweithreit erioed erioed â'r Llyfrgell yn gystafod ac i ddweud o gael y gorfod gweithreit yr eraill ei cyd-doedd. Mae gennym gweithreitau iddyn nhw wedi cael ei wneud i gyda'r gwaith i mi gweithreitau i gael gweithreit a rywbeth yn cael ei bobl yn neud o'r gweithreitau. Maelings chi'n gweithreitio i gael gweithreit ag y cyth yn ei gyflwyngau ddangos oedd o'r gwaith Gwybod lei ychydig yr ystod ynddo, ond rhai dwi'n gweithio dod yn ardig o gael cynnig o'r mweldau cydraed hefyd o'r gweithio ar y cyfrifio rhywbeth. Ond mae'r gweithio rheswer dychydig gan nodi adeg felly diwylliant yn ymgylchedd, dw i'n gweithio i argeirio. Fy enw'r rhagfai, dweud mewn gwirionedd rydych chi, mae'r rheidio'r rheidio'r ddweud, hi ddim ychydig ymlaen i chi'w ddwy'r rechydig. Dyma'r wych! Mae'n cyfnod o'r gwybod i grantumau o ysgol ei ffordd ac i'r online. So ddim yn fwy o'r ffyrdd. Dyna'r gwybod i gael gweithio o'r gweithio o'r online, ac mae'r gweithio y limau gyda'r gyflymorth o'r gweithio'r amser ac mae'n gweld i gweithio i gael gwaith eich gweithi eich gweithio gyddo'r limau, boe'n ei gwybod i gael gweithio'r limau. Gweithio'r 289 pwy o cwyl i gael gweithio 51 o'r hyn o'r fflaesifu cyfnodd yn digwydd i 238 o'r bobl online. Mae cyfnodd amser. Gwyddi'r gweithgaredd ar y gweithgaredd. Mae'r ysgaredd yn barcelonid gyda'r dim. Dwi'n dechrau a'r ysgaredd yn bwysig. Ac yna bod y gweithgaredd yn gweithgaredd. Felly, mae'n gweithgaredd yna, mae'n gweithgaredd yn ffordd o'r amser o'r ysgaredd, sy'n byddwch yn gweithgaredd a bod ni'n gweithgaredd yna. We tried to keep the schedule quite basic this time. So, there isn't too many scheduled things, we've just got these big blocks of just time for you to work on whatever you want to do. So, we've got the whole afternoon to work on NFCRE hacking, and then at 6pm, we're going to get together and have a daily summary. And we're going to have one group lead come from each group and just try and summarize what everyone's been working on in that group. Not very long, very informal, just to get a feel of what everyone's doing. A hynny ydi'r yn eich cyffordd, mae'n cael ysoesio, mae'n cael y cyffordd ar y laffau dechrau sicrhau sicrhau'r cyffordd, iddyn nhw'n trafnod yn 10 ysgol. Mae'n credu chi'n gwirio'n teimlo i ddweud arall. Mae'n cerddol ychydig i chi'n cael pwysig, a'r bwysig o'r ddweud. Mae'n gallu bod yn gallu gwirio'n cael ei rhan o'r ffordd, a'r ddweud i'r rhan o'r brif, a'r brif yn fath o'i llwyddo.  Mae gwaith yn nhw i gy maskedyr lleol, ond bywf yn bwysig iawn a'n ffawr. Maen nhw y tîm yn ymryd wedi'i fan hyffordd hefyd. Mae'n rhai wahanol. Mae'n thriyd i'r hyffordd hefyd yn eu mleiddiad yn cyfgafodd a'r rhagwyddiad. Go iawn i chi'n cael ei wneud. Ac aethoddiad, mae'r bellwch arspefiad mewn cyflod, ac mae'n ddweud iawn. Mae'r grffyn sy'n dweud â hyn. Mae'r gwaith bobl iawn i'r cyflogau a'r hyffordd cyflogau yn cael ei wneud o'r cyflogau ar-on Youtube. A ydw i'n gweithio yma ar-union, ond rydyn ni'n ei fydden i dylwyd i'r relaf i'r hyfforddiad yn gyfo'r rwynghwm, mae'r ddflwyf yn fwyaf o'r gweithio ac yn ymddir i'r relaf o'r relaf o'r relaf, os ydych chi'n ddwy o'r ar-on, o'r relaf o'r relaf o'r relaf o'r relaf o'r relaf. Those are on the NFcore YouTube channel not the Nextflow channel So the Nextflow Summit will have live streams as well and those are on the Nextflow channel but over Hackathon is on the NFcore channel Right, a few logistics for those of you who are here in person We have 3 rooms booked for the hackathon which hopefully most of you have already seen we've got this one which is called I'm meant to write the names and I forgot anyone example which is the main room We have space for about 40. I think maybe I'll write this down afterwards. Then we have a middle-sized room, which is just there. It's just got a table for 14, I think, and a big TV if you want it. Then we've got a really cute small room over there just around that corner called La Bossa la Lleeta, which has chairs for six. These are our main spaces for working in and we're not going to say specifically this group has to be here, this group has to be there, i'n rhaid i'r bobl, i'n mynd i gyd o'r ymddangos a'r ymddangos yn ystod y rhaid i'r cyflwytaeth. Ond nad ydych chi'n gweithio'r cymaint, rydyn ni'n gallu ychydig yn ddechrau a'r cyflwytaeth i'n ddweud ychydig i'r ddweud ymddangos yn ddweud yn ddweud i'r gael a'r ddweud i'r ddweud i'r ddweud i'r cyflwytaeth. Mae ydych chi'n oedd o'r sgwladau yn y coridor. Roedd roedd ychydig o'r cyfnod o'r hyn o'r cyfnod o'r cyfnod. Roedd y cwmwysig iddyn nhw. Mae'r cyfnod o'r cyfnod o'r cyfnod i dweud yn yw'r rhain yn y drafodol. Roedd o'r cyfnod o'r cyfnod o'r cyfnod o'r cyfnod o'r cyfnod. Roedd o'r cyfnod o'r cyfnod o'r cyfnod o'r cyfnod, dwi gwych yn ddweud o'r holl, ac mae'n sgwylltiaid i i'r cyflawn. Felly, mae'n bod i'n ddysgu'r llwyddiad yma yng Nghaerwyr yw'r rhain. Felly, mae'n bod i'n ddau gynnig o'r ddau. Gweithio, rydw i'n mynd i'n gweithio that. Yn nefyd, mae'n ddau'r sgwylltiau'r gweithio. Mae'n ddau'r gweithio'r gweithio'r gweithio'r gweithio. Rydw i'n dda hefyd. Mae'n ddau'r gweithio'r gweithio, Cwfi, mae'n ddigon. Rwy'n gweithio cwfi ar y cwfyd yma ar hyn. Mae'n mynd i chi'n meddwl yn y coridor, mae'r Llywodraeth Cwfyddiadau Arfer, maen nhw'n meddwl yn meddwl gyda'r cwfi ar y cwfyd. Yn amlwg, mae'n reswi ffansio, mae'n cael cafau yn y ffoeie. Felly, mae'n syniad, mae'n rwy'n credu i gyd gan y rheymau. Mae'n i ddiwg ymlaen nhw. Mae'r cychwyn, mae'n gyntaf. Mae'n ddweud, ac mae'n gymryd o'r ddweud. Y ddweud y pethau yn ychydig gan yw i chi, mae'n gwybod eich gweithio eich tîm. Rwy'n gweithio eich ddweud, mae'n gweithio eich ddweud. Rwy'n gweithio eich ddweud ystyried, mae'n ddweud. Mae'r ddweud yw'n adeg o'r ddweud a yr hyn yn nhw'n gweithio eich ddweud o'r ddweud. A'i gweithio eich ddweud yw'r ddweud. Just kind of wave when asking them not to. The same they might be taking photos of things on your screens and stuff. So just sort of try them bear that in mind if you have anything that you don't want to end up on any kind of call website. Either hide it, or ask them not to ask. And also I'd encourage all of you to take as many photos as possible basically. I'm going to do a wrap up talk at a summit on Friday and I want to have something to put my slides, so please take lots of photos, take screenshots of Gat entit, document what you're doing, I will stick it up on Twitter or whatever, and I will be using this stock material for talks for years to come. But yeah, just bear in mind that everyone makes sure everyone is happy with screenshots online and stuff as well. And if you're putting things on social media, please try and use the hashtag next flow summit, just so it makes it easy for other people to find as well. So general workflow for how we organise ourselves within the hackathon. Number one thing, once you've all kind of found a group, found where to work, is just to chat to everyone else, see what everyone else is involved in, talk about ideas, think about different things you want to do, and sort of find a consensus. And because we have a lot of people here, it's probably a good idea to try and find kind of many subgroups within the larger groups as well. So just find someone to pair up with. It's a social activity, so find someone you're comfortable working with. For those of you working online, same story really. I think it's going to be a little bit difficult to have a real full integration between online and in person, but you can still kind of find groups online and work within them, and we'll have Slack and to kind of communicate between everybody. And if it makes sense, then we can also drop in together quite easily from in person to kind of have bigger discussions. So please be very vocal on Slack and shout and tell us if you want to chat and let us know what you're getting on. Once you've kind of made friends with everybody in your group, go to the GitHub project board. So I can quickly show you this. This is linked from the event page as well. But if you go to the NFCOR GitHub organisation, go to projects, and then you can see here it's recently viewed, but you can also see under the projects tab that there's one called Hackathon OX 2022. And then this is where we've collected issues, GitHub issues from across all the different repositories on NFCOR and they're labelled. And the way that GitHub projects works is this is kind of a master overview, and then we also have tabs here for all the different working groups, and you can see that we can kind of do statuses and move them around and stuff. So this is where, if you're not sure what to work on, this is where to go to find specific tasks, and this is how we organise ourselves. If you've got something specific in mind, please make an issue, add it to this project board and assign it so that everything is listed here so we don't accidentally have people duplicating work. This is especially important because we're doing it as a hybrid event and that we have quite a lot of people, so this is the source of truth. So once we've got an issue, please assign yourself to it on GitHub. If you can't assign yourself, it's probably because you're not part of the GitHub organisation for NFCOR. Hop onto the NFCOR Slack, there's a channel called GitHub Invitations, post your GitHub username there and someone will add you, and then you should be able to assign yourself to that issue. And then everyone knows that you're working on it, and it's sort of claimed for you. Don't assign yourself to loads of issues, just do the one you're working on right now. When you're finished, make a pull request and push your work, your changes to that GitHub repository. If you're new to GitHub, please have a look on our NFCOR bite size under events, you can find all our bite size talks, and we have a whole talk by Alex, I think, which is all about kind of GitHub workflow, what issues are, what forking means, how to make a pull request. So check that out first so that you're familiar with the process. Now, what we always have with hackathons is we have loads of people come together for a few days, do loads of work, submit loads of pull requests, and no one does quite as much for viewing. And then it takes us about a month afterwards to merge hundreds and hundreds of pull requests. And also remember that this isn't just push your work and you're done, it's a feedback process. So someone else, the idea of someone else reviews your code, makes suggestions, you talk to them, you go back and forth until everyone's really happy with it and then you merge. So please try and find some time to do reviewing as well. And we can kind of swap pull requests, you know, we've got a request review channel on Slack. You can pop your request in there, find someone else who's also waiting, review each other's code. And hopefully that way we finish the event without some massive backlog of pull requests because that's not very helpful. So put your pull request in, try and find something else to review while you're waiting, and then move on to the next thing basically. We're using HackMD to make slides and records. So you can make a note of this. There should be links in your Slack groups for each group. And you can also chat to your team lead. So just keep making notes every time you do stuff there because otherwise it will get lost. And again, for my talk on Friday, it's nice to know roughly what we did. And then, yeah, do a little party, have a little celebration, get a cup of coffee and start the whole cycle again. Any questions? Is that clear? All the links and all this is documented is written down on the event webpage. So if in doubt, just go to the NFCOR website and click current event. As you've probably got by now, everything is happening on Slack. So please use that as your primary place for discussion and everything. You can get an invite to join here if you're not already on Slack. And once you're in Slack, use the channel browser to find all of the Hackathon channels. We have one main channel just for general discussion. If you're asking when does the next session start, when's lunch, I'm hungry, things like this. Where's the coffee and is it decaf? So that's the general chat channel. And then we have channels for each group. And again, you can join all of these if you want to, but this is where all the discussion around those specific tasks will be going on. And then don't forget we've got a Spotify playlist channel as well. If you drop a message into there, there's a bot which will add your song that you've requested to our NFCOR Spotify playlist. And then you can hop onto Spotify and enjoy a truly random mix of music. So we've been doing this for a couple of years now, right? So it's already quite a long list. It's everything from hard rock to Disney. So that's something for you all to enjoy and get in the mood. Right. A quick reminder that we do have a code of conduct for NFCOR, which covers events in person and online. So by being here and by being part of this event, you're kind of agreeing to abide by these rules. You can check it out on the website. Just go to about and then code of conduct is pretty easily well written. It's quite easy to read and basically boils down to sort of just be a nice person. Just remember to take breaks. Don't overdo it. Talk to people. Don't take photos without consent and things. And just try and behave in a sensible manner.  Maybe you haven't been to any hackathons before. Maybe you're fairly new to NFCOR, to collaborative coding and things. Have a look on the NFCOR website under events. We've got all of these bite-sized talks. I mentioned one about GitHub contribution basics. You can see number four there. But there's tests about all kinds of different topics. Specific pipelines but also lots of things talking about how we work within NFCOR. So this is a really good place to go to get help if you can't find it in a traditional documentation. All of these are live streams so they're all on YouTube. So well worth having a look through. And on a more general note, we've got the whole YouTube channel. We've got the secure labs training. I don't know how many of you were involved in the training last week. We did online but you'll be very familiar with this training material if so. And of course we've got the NFCOR website. We've got a few kind of social events for the hackathon. Fairly low key during the day. And all of these are both for online and in person. Firstly James is doing his tradition now of running a bingo. He's a sort of a set of in-jokes which might not make much sense to you right now. But by the end of a hackathon hopefully you'll be laughing with the rest of us. Things like github going down always happens. And me usually I don't know what cards are there now. But if you go to the event web page you'll find the link to it. And it's just a web browser tab. You type in your name and tick off things as they happen. And when you get a bingo shout in the NFCOR Slack and James will write down your name. It's worth playing because this hackathon for the first time we have prizes. Which haven't actually arrived in the post yet. But we do have prizes. So we will be keeping a list of names and we'll see if a post in Germany is fast enough. Maybe they'll be here in time for Friday. Otherwise we'll be posting them out after the event. So make sure you tell us if you get bingo and then you can start over again. And keep going. Those of you who have been to previous events know that we have a bit of a thing about socks. And NFCOR swag has become a meme within the NFCOR community now. So like previous events in Gathartown we have hidden socks in Gathartown.  Or we'll post in Slack maybe. When you hit the magic number of secret socks that you've found, which Maxim will post in Slack, then shout about it. And if you're the first person to get there again you get a special prize. And then there will be more socks added for further rounds over the days. So find the socks. And last but not least we have a quiz, a fun cahoot quiz. So it's an online quiz which we're going to do in person and online all together. And that will run on Wednesday morning. And there will be a link on the website again. I just want to say thanks to the Transakaberg initiative who have very generously given us funding for Nextflow and NFCOR. It's through this funding that some of us have stood here for starters. And also it means that we can do things like buy nice bits of kit for you. There's been the NFCOR socks in the past and hopefully everyone has been given a little green bag when they came in which we've also got some goodies in. Some of them are for the Nextflow Summit itself which started in a few days. You guys get yours early for that. But it was also a bit of NFCOR swag in there. We have an emoji for NFCOR socks. So we'll see if by the end of the event we have an emoji for NFCOR umbrella as well. So hopefully that's kind of a bit of fun for you all. Right, with that, welcome. I hope everyone has a really, really good time over the next few days. The few of us are going to stand up and talk now so you'll know who we are. So if you have any problems just come and shout, wave, come and talk to us. And I'm looking forward to actually getting to see many people who I know so well online in person. It's a real pleasure to have you all here. Thank you very much for coming. And then I'll hand over to Maxime. Hello. Yes, it's better if a mic that works. So hello everyone. Yes, I assume you see the same screen as I do. So yes, I'm going to explain what Gazarton is. So yes, first to begin, I'm Maxime Garcia from Karolinska Institute and the Sidelife Lab for the moment. And yes, so basically Gazarton is the space where we are handling the online events, the online part of the event. So if you already are logged in and have a Gazarton account, it will look like that. So we have the regular NFCOR office that we use like most of the time. But now, for this event and for the next flow submit, we have this specifically dedicated like space which is next flow submit. So if you never connected any before to Gazarton, you just need to enter like the address for this event that we add in the website and that will lead you to the space. You need to enter with the same email address that you use for rejoining, for reducing to the event. Otherwise, you won't be able to join. If anyone has any issue connecting to Gazarton or anything, just ask around on Slack and we'll help you like about that. And basically if anyone has any issue with anything on Gazarton, ask me. That will be faster. Or Chris is doing like a lot of stuff. So basically that's what happened when you arrived in Gazarton. We arrived in the main lobby. That's here where we are. That's Gazarton. So it's super simple. You use the arrow on your keyboard to move around. When you come across something that you can interact with, you can just press X and then you get some information. So it can be either like a website. Here it's an information board. So we see information about the hackathon. And then basically you move around to see where you need to go. So obviously right now we are doing the hackathon. So we need to go to this room, which is hackathon. I will show that later. We have like one room for the poster for the summit where you can see the poster around. So you just need to go like in a poster and then you can actually see a poster. What is the information about the poster? This is all available on the website already. And that's basically like what there is about Gazarton. If for example you get like let's say you go like too far away and you get lost. You don't know how to go back to any space. So let's see. I'm going like on the rooftop. As you can see we're in Barcelona. So we have nice view over Barcelona. And now I'm completely lost. I don't know how to go back to the space. So what you can do, you can press on your personal menu and you can click respond to actually restart from the main entrance. So that's actually fast. Or what else or what you can do as well. You can click on the name of someone and say I want to follow this guy. And then you follow him. Where are you Alex? Okay, Alex is here. So you see it works well. And then yes, just continue when you are here. So here this is the hackathon space.  So you just press play. I'm not going to do that because I don't want to have like some weird feedback loop around, but it works. And then you can sit like at a table to discuss with everyone else. So we have dedicated table. And when you're entering like a space, you can see here I'm on a private space. So I can only talk within Gazarton to the people that are in the same Gazarton space. And I, hello Matias. And I think that's all for me. No, I forgot the most important part of Gazarton. You can dance by pressing the Z letter or you can actually like throw confetti around by pressing F. So that's important. That will be super good. And yes, so there will be socks I done around. You might need like to have like to go through some walls and stuff like that. So definitely you will get lost. And if you get like too lost, don't hesitate to respond or just like try to locate and find someone. So I hope that I didn't forgot anything. If I forgot anything, I will let like everyone know on Slack. And if anyone has any issue, same as usual, like come and ping us on Slack. Thank you again. Feed back to you. Anyone want to go volunteer? Take a group. Hello. Wow, that's loud. Okay, sorry. Amazing to see all of you guys here in person. It's a massive difference to interacting with you via Slack and offline and stuff. And just seeing all of you guys around in person is amazing. So thank you for coming. Some of you have come from as far as Brazil, the States, Canada, all the way around. So yeah, really appreciate you guys coming in. And hopefully this turns out to be a great event. Before I drag on more about how amazing this is, I will introduce to you the sub-workflows team. So one major thing we've been trying to tackle on NFCOR for a while now, and we've just put it off because there's been other things going on and other fires to put out, is using sub-workflows on NFCOR. So for those of you that don't know what a sub-workflow is, what we have is this NFCOR modules repository at the moment where we have units of next flow, so process level modules for tools like FastQC and so on. And that's matured quite nicely now over time. But now we want to go to the next level. And the next level is installing chains of modules or what we call sub-workflows directly into pipelines. We've started working on a tooling for that. We have a few commands already that we can start using and testing. They're not fully mature. So, yeah, you may need to take it easy, but tell us exactly what's broken and we'll try and fix it. So, yeah, so the plan for the sub-workflows team mainly is to just improve everything around sub-workflows, the documentation, the tooling that we've got in NFCOR tools, as well as starting to add the sub-workflows to NFCOR modules as well. So as I mentioned, we've got some basic commands that are running already, and pretty much like you would add a module to NFCOR modules, you can use a similar process to add sub-workflows as well. If you need any help, shout on the sub-workflows channel on Slack, but it'd be great to have you guys contribute and help out. Pick us. Next. Thank you. Hello, everybody. Rika and myself are leading the pipelines team. This is sort of the bread and butter of the NFCOR community. So in our team, it's mostly using the time for each pipeline dev to focus on their particular pipeline, adding new functionality, bug fixes and things like that. The SL2 transition is a big thing at the moment. So this is sort of pretty standard for the hackathons. Nothing really new there. The main thing we want to try to get around the review requests that we've had issues in the past hackathons is have a buddy system. So we're going to have a table, and you can sign up to buddy with someone who will basically give you rapid feedback throughout the hackathon. Online on Gather Town, we have Louise, who is going to be our online coordinator as well. And generally, if you're interested in helping out with one of the pipelines, we are in the other room to the left of the main room here. So hello, everyone. Welcome to the hackathon. So we're going to have in that table and a table on the top on the Gather Town, the documentation group. So if you want to contribute with documentation, feel free to join us. If you're a beginner, you want to learn about Nextflow NFCOR. It's great. You're going to read the documentation, find orthographic mistakes, or a better way to write something. So if you have a lot of experience with some pipeline, you can contribute with documentation for that pipeline. So everyone is welcome to come. For people who are new, it's going to be nice because in our table soon, a friend will ask, you're going to give a short talk about how to use a few things on the project board and how to do some improvements for the documentation. So feel free to join us and watch our talk. So thank you. Yeah, so Jose and me, I'm Gisela. We will be leading the modules team. And the idea there is to contribute to the more than 600 modules that are already available in the NFCOR modules repository. So if you have a software tool that you would like to add to a pipeline creating a module, and the idea is that those modules then can be shared among different pipelines. And yeah, so if you have any questions, feel free to contact any of the two of us and also Luisa Perello, who will be our online representative of the modules team. So hello now to the infrastructure, which makes all of the other things running. It's the ladies, me and Julia over there. We are also present on Gather Time if you want to join us there. And the main tasks are, like Herschel mentioned already, working actually on the different commands for the subworkflow to create, to lend on all of these things, which is, yes, exactly Python code. If you just want to write some Python, we are very welcome to host you there. Similar like if you want to write some Python tests, our tools could get some more test coverage. So it would be very nice if somebody could help us there to write some tests for all the different commands we have there. And write a small prototype project is also running with the NF test. You might have seen on Slack mentioned a small proof of concept happening there, which is for the NF core modules repository. And if you don't want to write Python, but more like JavaScript or PHP, we have loads of bugs on the website. And you're very welcome to join there as well. It's also very, like, beginner-friendly place there with smaller but very necessary tasks we need to do for the website. Thank you very much. These are the guys you want to buy coffee for as well, because usually we find that you will all discover bugs in a tooling as we go along, and then you need to go and plead with them to fix it for you. Did I forget anyone? I think that's all the groups. Okay, great. In that case, just thank you very much for coming again. Lunch has arrived for those of you here in person, so we'll grab some food and then we'll get started. And I hope everyone has a really good few days and we'll chat again at the end of today to do a wrap-up. Cool. Thank you, everyone.