And if you're just joining us here, the 18 year old Timothy George Simpkins who is charged with three counts of aggravated assault with a deadly weapon just came out of jail here.


What is genetics? Genetics is the study of genes variation and heredity in living organisms. Genetics is usually considered as field of biology. The principles of genetics were first time explained by a scientist whose name was Grieger Mendel. When Grieger Mendel was formulating the laws of heredity at that time he was unaware about the concept of chromosomes, gene or the mutation. Genetics can be studied in two different ways. One way is called as reverse genetics while the second method is called as forward genetics. If we want to study genetics in a reverse pattern then a researcher or a geneticist have to select a particular gene then certain mutations have to created in that gene and then phenotype have to identified based on the mutation that were created in a particular gene. If this methodology is used to study the genetics then it is called as reverse genetics. While in case of forward genetics a geneticist or a researcher have to first identify the phenotype then based on the phenotype certain mutants or for certain genes they are screened and ultimately a particular gene is identified that is causing mutation or that is the responsible for a specific phenotype. So there are two ways of studying the genetics. One is called as reverse genetics and second one is called as forward genetics. If we say that how we can study genotype based on the phenotype then it is called as classical genetics or forward genetics. Usually it is performed by sequencing the DNA while if a geneticist or a person want to study genetics in a reverse pattern or in a reverse genetics then phenotype is identified based on the genotype. There are different methodologies which are used for studying the reverse pattern of the genetics. Those methodologies they are positional cloning RNA interference gene knockouts and there are different other methods which are used to study the phenotype based on the genotype. Mendel is considered as father of the genetics. For formulating the laws of heredity or the principles of heredity Grieger Mendel used golden pea as an experimental plant. There were many properties in the in that experimental plant mean the golden pea. We will see what were the properties in the golden pea that Mendel used for formulating the laws of heredity. Golden pea the seed of golden pea is available in many varieties. Usually this plant self pollinate as well as cross pollinate. This plant takes little space mean within a little space one can grow this plant. This plant has short generation time mean within two to three months one can grow and can get the seeds of this plant. This plant produces many of springs at a time. So if we list that there are many characteristics that these characteristics they help to the Mendel for performing the experiments as well as for formulation of the laws of the Mendel. Usually it is said that Mendel was fortunate because why he was fortunate he selected golden pea as an experimental plant because pea plant was available in many varieties. When Mendel was performing the experiments of genetics at that time he had strict control over different plants that he mated as well as the traits of the golden pea they were clearly contrasting and they were clearly distinct from each other. So these were the major properties that help the gregal Mendel for the formulation of the laws of heredity. This is the list of those characteristics or those properties of the golden pea. If we list them one by one flower color flower color was purple and white flower position was axial and terminal. The seed color was present in yellow color as well as in green. The shape of the seed was round as well as wrinkled. If we see the pod shape that was present in inflated form as well as constricted form and the color of the pod that was green as well as yellow and some of the plants they were tall and some plants they were short. So these were all those characteristics which were present in the golden pea. So at the end we can conclude that what is genetics? Genetics is the study of genes, chromosomes and heredity. So that is the definition of the genetics and concept of the genetics.


From around the globe, it's theCUBE with digital coverage of AWS re-invent 2020. Special coverage sponsored by AWS Worldwide Public Sector. Okay, welcome back to theCUBE's coverage of re-invent 2020 virtual, it's theCUBE virtual. I'm John Furrier, your host. We're here celebrating the special coverage of public sector with Sandy Carter, Vice President of AWS Public Sector Partners. She heads up the partner group within public sector now in multiple, I hope about a year now, right Sandy? You're so, good about a year. Congratulations, welcome back to theCUBE for re-invent. Always a pleasure to be here and what an exciting re-invent, right? It's been exciting, we got wall-to-wall covers, multiple sets, a lot of actions, virtual, it's three weeks, we're not in person, we have to do it remote this year. So when real life comes back, we'll bring theCUBE back. But I want to take a minute to step back, take a minute to explain your role for the folks that are new to theCUBE, new theCUBE virtual and what you're doing over there at Public Sector. Take a moment to introduce yourself to the new viewers. Well, welcome, theCUBE is phenomenal and of course we love our new virtual re-invent as well. As John said, my name is Sandy Carter and I'm Vice President with our Public Sector Partners group. So what does that mean? That means I get to work with thousands of partners globally, covering exciting verticals like space and healthcare, education, state and local government, federal government and more. And what I get to do is to help our partners learn more about AWS so that they can help our customers really be successful in the marketplace. What has been the most exciting thing for you in the job? Well, you know, I love, wow, I love everything about it, but I think one of the things I love the most is how we in Public Sector really make technology have a meaningful impact on the world. So, Johanna, I get to work with partners like Orbis, which is a nonprofit. They're fighting preventable blindness. They're a partner of ours. They've got something called CyberSite AI which enables us to use machine learning over 20 different machine learning algorithms to detect common eye diseases in seconds. So you know that that purpose for me is so important. We also work with a partner called Twist Think. It's hard to say, but it just does a phenomenal job with AWS IoT and helps make water pumps smart pumps. So they are in 7,300 remote locations around the world helping us with clean water. So for me, that's probably the most exciting and meaningful part of the job that I have today. And it's so impactful because you guys really enable Amazon's business model has always been about enablement from startups to now up and running Public Sector and entities and agencies, education, healthcare. Again, and even in space, this IoT in space. But you've been on the 100 partner tour over 100 days. What did you learn? What are you hearing from partners now? What's the messages that you're hearing? Well, first of all, it was so exciting. I had 100 different partner meetings in 100 days because John, just like you, I missed going around the world and meeting in person. So I said, well, if I can't meet in person, I will do a virtual tour and I talked to partners in 68 different countries. So a couple of things I heard. One is a lot of love for our MAP program and that's our migration acceleration program. We now have funding available for partners as they assess migration, as they look at mobilizing it and as they migrate it. And you may or may not know, but we have over twice the number of migration competency partners doing business in public sector this year than we did last year. The second thing we heard was that partners really love our marketing programs. We had some really nice success this year showcasing value for our customers with cybersecurity. And I love that because security is so important. Andy Jassy always talks about how our customers really have that as priority zero. So we were able to work with a couple of different areas that we were very proud at. And I love that the partners were too. We did some repeatable solutions with our consulting partners. And then I think the third big takeaway that I saw was just our partners love the AWS technology. I heard a lot about AI and ML. We offered this new program called the Rapid Adoption Assistance Program. It's going global in 2021. And so we help partners brainstorm and envision what they could do with it. And then of course, 5G. 5G is ushering in kind of a new era of new demand. And we're going to do a partner cast all about 5G for partners in the first quarter. Okay, I'm going to put you on the spot. What are the three most talked about programs that you heard? Oh wow, let's see. The three most talked about programs that I heard about. The first one was, it's something I'm real excited about. It's called a Think Big for Small Business. It really focuses in on diverse partner groups and types. And what it does is it provides just a little bit of extra boost to our small and medium businesses to help them get some of the benefits of our AWS partner program. So companies like MFT, they're based down in South Africa. It's a husband and wife team that focus on that black economic empowerment rating and they use the program to get some of the go-to-market capabilities. So that's number one. Let's see, you said three. Okay, so number two would be our pro-serve ready pilot. This helps to accelerate our partner activation and enablement and provides partners a way to get badged on the pro-serve best practices, get trained up and does opportunity matching. And I think a lot of partners were kind of buzzing about that program and wanting to know more about it. And then last but not least, the one that I think of probably really has impact to time to compliance. It's called ATO, Authority to Operate. And what we do is we help our partners, both technology partners and consulting partners get support for compliance framework. So FedRAMP, of course, we have over 129 solutions right now that are FedRAMPed, but we also added John, PCI for financial hip-hop for healthcare, for public safety, IRS 1075 for international GDPR and of course for defense IL-45 and six and CMMC. That program is amazing because it cuts the time to market and half cuts the cost in half and really steps partners through all of our best practices. I think those are the top three. You know, I've been like a broken record for the folks that don't know all my interviews I've done with public sector over the years. The last one is interesting and I think that's a secret sauce that you guys have done. The compliance piece, being an entrepreneur and starting companies, that first three steps in a cloud of dust momentum, the flywheel to get going is always the hardest and getting the certification. If you don't have the resources, it's time consuming. I think you guys really cracked the code on that. I really want to call it out because that's I think really super valuable for the folks that pay attention to. And of course, sales enablement through the program. So great stuff. Now, given that's all cool, the question I have and I hear all the time is, okay, I'm involved. I got a lot of pressure. Pandemic has forced me to rethink. I don't have a lot of IT. I don't have a big budget. It's always been the complaint, but not anymore. Mandate is move fast, get built out, leverage the cloud. Okay, I want to get going. What's the best ways for me to grow with public sector? How do I do that? If I'm a customer, I really want to, I won't say take a shortcut because there's really no shortcuts. How do I throttle up quickly? What's your take on that? Well, John, first I want to give one stat that came to us from Trilio. They had interviewed a ton of companies and they found that there was more digital transformation since March, since when the pandemic started to now than in the last five years. So that just blew me away. And I know all of our partners are looking to see how they can really grow based on that. So if you're a consulting partner, one of the things that we say to help you grow is we've already done some integrations. And if you can take advantage of those it can speed up your time to market. So I know you know this one, VMware Cloud on AWS.  It provides protection of skill sets to your customer, increases your time to market because now VMware, vSphere, vSan is all on AWS. So it's the same user interface and it really helps to reduce cost. And there's another integration that I think really helps which is Amazon Connect, one of our fastest growing areas because it's a ML AI bread solution to help with call centers. It's been integrated with Salesforce, both the service cloud and the sales cloud. So how powerful is that? This integrated customer workflow. So I think both of those are really interesting for our consulting partners. That's a great point. In fact, well, that's the big part of the story here at Reinvent this three weeks has been the integration. Salesforce, as you mentioned, Connect has been huge and partner. So just great success. And again, I've seen great momentum. People are seeing their jobs being saved, they're saving lives. People are pretty excited. And certainly a lot of work to have done healthcare and education, two big areas of activity with this really hard core pressure, really, really hard. So congratulations on that and great work. Great to see you. I got to ask you one final question. What's the big message for your customers watching as they prepare for 2021? Real life is coming back. Vaccines on the horizon. We're hearing some good news. A lot of great cloud help there. What's your message to send to 2021? For our partners for 2021, one, there is tremendous growth ahead and tremendous value that our partners have added. And that's both on the mission side, which both Teresa and I discussed during our sessions, as well as technology. So I think first message is there's lots of growth ahead and a lot of ways that we can add value. Second is all those programs and initiatives, there's so much help out there for partners. So look for how you could really accelerate using some of those areas on your customer journey as you're going along. And then finally, I just want John, everybody to know that we love our partners and AWS is there to help you every step of the way. And if you need anything at all, obviously reach out to your PDM or your account manager or you're always welcome to reach out to me. And my final message is just thank you through so many different things that have happened in 2020, our partners have come through amazingly with passion, with value, and just with persistence, never stopping. So thank you to all of our partners out there who have really added so much value to our customers. And Amazon's recognizing the leadership of partners and the work you're doing. Your leadership session was awesome for the folks who missed it, check it out, it's on demand. Thank you very much, Sandy, for coming on theCUBE and sharing the update. Thank you, John, and great to see all your partners out there. Okay, this is theCUBE virtual covering AWS, reinvent 2020 virtual three weeks, wall-to-wall coverage, a lot of videos. Check out all the videos on demand, the leadership sessions, the CUBE videos, and of course the public sector video on demand, microsite with theCUBE, John Furrier. Thanks for watching.


That was fun. I'm going to go back to home and we're going to go on to the next phase of the OSF You're planning your research registrations versus preregistrations, right? This typically happens in this phase of developing an idea study idea study design and acquiring materials, so First off, what is a registration now the typical, you know trajectory of research is you design a project You conduct that project You report on that project and you publish that project The peer review phase happens between the report and publish when you submit to a publisher somebody reviews it and decides whether it's worthy of publishing problem with that and one of the replication problems is that It tends to lead to only successful studies really working out And being published it doesn't really add credit to all the work that happens beforehand it also kind of incentivizes people to You know if they get a result that doesn't match what their plan was they could have just they could just change their plan and then Suddenly the results match what they planned to do In big air quotes the metaphor we like to use is it's like if you fired a bow and arrow And wherever that arrow landed you just drew a target around it and said yeah, that's totally what I meant to do That's not really transparency and that's not really how research is supposed to go uh, and by doing that you kind of lose faith in the research process, so registrations are a way of combating that So talking about preregistration a preregistration or registration is a time-stamped version a read-only version of your research plan It's created at a very specific moment in time and the point is is that you are basically calling your shot You are locking in your plan at a certain phase and saying at this time at this date This was my research plan. Here's what my hypothesis is. Here's what we're going to do Here's what we're going to analyze and how it's going to happen And then at the end when you are finally publishing you can share that preregistration and say look Back at this date at this time This is what my plan was and see I actually got the results that I want Now the question that we usually get here is what are the difference between registrations and preregistrations? And that is a little bit ambiguous because sometimes in the world they are used synonymously But at least on the osf. This is how we kind of define it It's really based on the timing of when you're submitting this registration versus preregistration So again up here at the top you have design conduct report and publish That's a general timeline for a research project now for a preregistration What you are doing is while you are designing and preparing to conduct that experiment you're filling out the form Now prior to actually conducting that experiment you submit this form you submit this preregistration form that locks it in place You have a time stamp that says this is what my plan was at this moment in time prior to conducting this experiment Now obviously things change and you can update that form But every version it'll create a new version of that preregistration and every version will tell that story. It's kind of like You know one of those old timey flip books where you have you know one version And then one page and one image and one image and one minute one minute And every time you're flipping it you're getting that full story of what's happening And that can happen all the way up until you publish The point is that when you publish you can call your shot and say hey I did this my idea happened right before we conducted experiments. So no funny business happened Whereas registrations, they're a little bit more ambiguous on the timeline Again, you are trying to fill out that form as prior to conducting your experiment But you can actually submit that form really after you've conducted your experiment while you're reporting all the way up until the moment that you actually publish As you can tell we we're not That's not super transparent and we don't love that idea We do push people to try and pre-register work as that is probably the more transparent of methods But the problem is is that things happen COVID-19 for example, or uh, you know things change in your research lab Uh, you have to make changes Some you know some forms some disciplines that Pre-registration just isn't super practical. Um, especially for something more applied disciplines So registering your work is still very important But we do tend to push towards pre-registrations the second part of this That's I usually get as a question is the idea of scooping For those of you who don't know scooping is a term where You have an idea you share it with somebody you probably shouldn't have And that person has more resources more time more money And they conduct your experiment before you do and they get to publishing before you do Um, obviously that doesn't work very well in this idea of pre-registration If I submit this publicly someone could just take my work And they could publish before me So obviously we live in the real world We would love if you shared your work publicly beforehand, you know, you get a time stamp with that But uh, we do also offer the idea of embargoing So embargoing is Temporarily making a registration private And you can submit it up to four years after you've submitted it Um, this gives you time in order to, you know, conduct your actual experiment You've submitted a time stamp But you can conduct your experiment, finish your analyses, get ready to publish Have it submitted for publication, have it published, and then release Your registration to the public and say, hey I called my shot when And that looks like this And it also made me wonder, what does that look like on the OSF? Um, I'll show you right here So here is a Example of a registered Registration on the OSF That is Embargoed Can anyone see anything? So if someone just randomly finds your link, clicks in, you know, random digits They find your registration, they will see a page that says page not found This same exact registration on the same exact Link in a view-only version, which you could share with Colleagues or people that you trust or grant evaluators You could share a view-only link, which edits that URL to give you a private version of that Space, that's the difference between seeing a embargoed registration Versus an embargo registration with a view-only link Okay Now let's go back to here Let's see what some of these registrations actually look like So, exploring what a registration looks like can be as simple as This, so this is an updated version of a registration Starting here on the side, you will see a little bit of the tabs again You can add metadata to your registration, files, resources, anything like that Those open resources badges, those links are found here on the side So if I go to resources, I could see the data that is connected with this OSF registration Along, as you go down the column, you'll see the content that is available for this registration You also see the timestamp and the type of registration that this is This is an OSF pre-registration and it was created on September 23rd, 2020 You'll see all the contributors that are associated with this registration It's important to note that contributors on the registration need to be admin in order to accept that registration All registrations that are public have a DOI That is a digital object identifier, which is a persistent link that will never break and never change So if you're going to share your work with a publication or a registration, you're going to want to share your DOI You can also add a license or citation to make sure that you are telling people how you want your work to be shared Again, I said that registrations can be updated The original version Is found here and you can see that what the original plan was and and any Additional versions of that registration. You'll see the latest version Where they'll give the reason for the update and what sections were actually updated in comparison Again looking at that flip-flop Now going to our next version Let's take a second and let's look at how can I actually create a registration now the first second One thing I want to do is go up to this top section and look at add new I'm going to click and it's going to create take me to the osf registration strap page From here. I'll have two options Do I create a registration from an existing osf project? So if you've been working really hard on an osf project and you want to use that to like Create a snapshot of that rich that osf project You can absolutely do that All I would do is click yes, and then I would select what project I want to work from And that'll pre fill in a lot of the information from your registration into whatever template you would like to use The other aspect is if I want to start brand new So if I want to just start a registration from scratch I don't have a project I'm working from I can click no and I can select what template I would like to use Now these templates are all based around trying to give you different criteria and framework in order to frame How you want to plan your study plan your registration There are different options, and I can't really tell you which one works best for you The team has a chat. They'll send in the chat a A link that'll help you essentially decide which one works better for you It's our choose your own licensing or change your own Registration template and you can look through that so for now I'm going to click on osf preregistrations because that's the one I was Talking about the most I'm going to click create a draft And all that does is it really gives me the option of going through and Adding in all of the information. So this is the registration metadata again high level that you want to fill out title description contributors now it's important to note here Different permission levels if you want somebody to be able to approve And you need them to approve this registration before it becomes public You want to have them be an administrator It's also important to note that any associated projects with the registration Can have different permission levels. They can have different permission levels So if you have the same contributors But it on your project one of them is an admin versus on a registration or one of them is say a Read and write only That just makes it so that they can't actually approve this registration It will go on and be approved even without them affiliated institutions We've talked about that adding a license and this basically just takes you through all of the elements that you need to look at So study type Whether it's blinded or not sampling vary a variables analysis plan Everything all the way down to other it'll give you a chance to review before I get started And as I said After you filled out all this information I can't submit it now because it won't even let me click on this because I don't have some of the information filled out It'll give me the two options first when I click register It'll give me the option to embargo you can pick a date again up to four years from now But then it'll also send out an email to all of your admin on your project Asking them to approve they'll have 48 hours and then it will be auto approved. If not


confidence we won't lose everybody to sleep. So I'm going to start. My name's Steve Wally. I'm a distinguished technology at Hewlett Packard. As of next week I'll be a distinguished technology at Hewlett Packard Enterprise. And I've been in the industry for about 35 years now. I've had the privilege of being both on the vendor side as well as on the customer side. I've worked in large IT organizations for a large part of my career. And my co-presenter. I'm Leong. I work for Intel as a cloud architect. So I've been working in the industry for about 15 years with a mixed background in software application developments, infrastructure development as well as operations. And before Intel I work for Liberty Mutual IT. So it's one of the insurance companies in the US, a very big company in the US. And I also work for a couple of companies including Motorola and also let the engineering team of a few start up company. And back in 2013 I obtained my PhD in multi-cloud orchestrations. So we're talking about turning pets into cattle today. And I wanted to make sure though we do a quick base set on what we're not going to be talking about. So this is not a talk about how you're going to deploy those applications in any kind of continuous integration, continuous deployment situation or how to automate those things. This is not a talk about puppet or shelf or salt or ansible. Those are all good things. Those are all excellent practices. But those are also cultural practices between engineers and operations folks. And what we want to do is this is a talk about application architecture. And I'm sure everybody's familiar with the idea of pets and cattle. Pets are things with names. These are your traditional three tier architected applications. They are highly managed. They're long running. I mean we used to measure things in uptime, right? That was the important thing that we all cared about. A lot of people like to talk about this as your legacy. And that's one way to think about it. But it's actually these are your business critical applications. And then you contrast that with the cattle world. These are suddenly things that you can scale out. They're highly resilient.  Now a lot of people are already doing the exploration into how they would build cloud native applications and how this is going to work forward. But that's the way you think about the applications that you are building forward. How you're addressing your backlog. And what Leon and I want to talk about is how do you actually think about moving some of your pets and these highly managed workloads, these business critical applications into a new cloud enabled world on OpenStack. Now one of the things that you'll come across before we get too far, we will be publishing the slides as well as the fact that the OpenStack organization will be publishing all of the slides. We'll also turn around and we'll each publish those slides through our own slide share and such. So you'll have access to any URLs that are mentioned here. The URL at the bottom there though is an exceptionally good document at allowing you how to think about some of these issues. And one of the things it presents is this idea of cloud application maturity levels. The problem in this space though is it's always presented to people as if these are absolutes. You know you're at level zero or you're at level two. And the thing that you need to think about when you start trying to understand how you're going to move your application workloads and how you're going to kind of forklift your business critical applications into an OpenStack cloud world is you can actually be at multiple different levels of maturity in each application.  You know we all understand virtualization and kind of level zero. Most of us have been living there for a long time. When you start looking at level two, sorry level one and level two, that's some of the work that Leong's going to demonstrate in a minute. It's how do you think about taking that three-tier application and begin to tear it apart in interesting ways without having to refactor it all. When you finally start stepping up from kind of that level two to level three, we start talking about, you know, that's where you get into Netflix country. You know, everybody aspires to be Netflix. So it's we're going to take this kind of to the next step and Leong's going to be working with WordPress because that's a three-tier application that everybody understands and works as a really good model to tease out the questions about how you have to think about re-architecting things. So, okay, I believe most of us has come to be into the process of migration from physical environment into virtualization environment. So when we move our application from physical to virtualization environment, our applications architecture actually doesn't change too much. So traditionally, we used to have web clusters and application clusters and the DB clusters, but when we move into the virtualization environment, it turns to moving the same model into the virtualization world. So what we gain from this model, from P to V, is basically we maximize the resource utilizations on the machine level and we probably can do some of the on-demand configuration by launch, you can launch your application in an on-demand way. So that's where we go from physical to virtualization P to V. But when we come into virtualization to cloud, we start wondering, I mean, can we do the same thing in what we have done in the P to V model? Can we do using the same approach without changing or without re-architecting our application and move them into the cloud? That's what we call paths to cattle. So what are the things that we need to be done? I mean, do we have to do re-architectures or can we just do port the whole VM over? So one thing I want to, before we dive deep dive into more of the architecture design, I want to show you this diagram. And this is one of the diagram that we borrowed from the, recently we published a booklet called OpenStack from business perspective. So the documents, I mean, is a collaboration work between HPE and other companies in the foundation, in the community. And you can actually download the PDF file from OpenStack.org slash enterprise. It's freely downloadable, so you can access the documents. And basically what I'm trying to tell you here is that we need to understand, first, we need to understand the differences between virtualization and cloud. As you can see from the diagram here, on the right-hand side, okay, on your left-hand side, okay, in the virtualization world, our applications tend to rely on the infrastructure to achieve higher resiliency. So relies on the hardware solutions, the application, everything on hardware layers. And our application tends to be a skilled up-moder. When we come into the cloud-based environment, or cloud-native environment, our application is designed in a distributed fashion. So the application itself, a cloud-native application, is responsible for their own resiliency mechanism. And it's kind of like independent, independent from the underlying infrastructure. If you're building a cloud-native applications, your application can run on private cloud or public cloud without too much changes. And the cloud-native application is more API-driven and is scaling horizontally. So there's one of the key differences in between virtualization and cloud. And another thing I want to show you is about the architecture design between Conventional App and Cloud Aware App. So when we design our application in the past, the application tends to be monolithic, centralized state, and very highly coupled. And most of the requires tends to be synchronous. But when we come into a cloud-building cloud-aware application, we are thinking about building, using distributed architectures, or using microservices. And requires tends to be asynchronous. And the app itself is designed for failure. It can handle all kind of failure situations. And basically, we're using common or share nothing architectures. And there's this concept about eventually consistent. So these are the design considerations when coming to the differences between Conventional Application and Cloud Aware Applications. So just now Steve also mentioned about these documents. So in these documents, it's published by Open Data Centers Alliance with a few companies, including Intel, HP, World Disney, and other companies I can't remember the name. So basically, in this document, talk about our evolution of application architecture from physical to cloud, sorry, physical to virtualization to cloud, and also identify some of the key principles when we want to build cloud applications, cloud-native applications. So some of the key principles are highlighted here. So a cloud native application has to be resilient to failure, and generally it is composable. So you can build your application in different components. And it has to be elastically scalable. It can be scaled out and scaled in. And it needs to be location independent. So you are independent from the underlying infrastructure. Because if you don't build your cloud native application in this way, it will hinder your ability to transition from either private cloud to the public cloud in a hybrid bursting model. So if you're interested to build cloud native application, I would recommend you to read this document. It's very, very useful documents. You also identify some of the strategy that you can apply when moving into the cloud. So once you understand the differences between virtualization and cloud, so what kind of strategy can we use to migrate our application to cloud? So when you look at that application, I think very important is you need to understand your architecture. You yourself have as architect or developers, you have to understand how your application is going to work. You need to understand where is your data. So most of the time, what I would recommend, or most people what they're doing today, and I would recommend is keep your database and what you have today. Don't migrate your database if you're not familiar with cloud today, especially for those company new to the cloud. And you can start looking at other components such as web tier or media ware or messaging. Start moving the web tier or media ware tier into the cloud, and it's more like moving bits by bits. Don't do everything in one shot, okay? Because database data is a key, right? You can't lose the data. So once you get yourself familiar with how the cloud is going to operate in your environments, then you start planning for the migration for the database. So most of the time people are moving the web tier and the app tier to the cloud when they first start their journey into the cloud, into the open stack. So another thing I want to bring out is the shift of focus. So we want to design a high reliable system. So reliability generally is being measured in terms of meantime between failure, meantime to repair, and availability. So traditionally when we build a high reliable system, we tend to buy very expensive hardware to increase the meantime between failure. I showed this slide before in the Vancouver summit. So we use a lot of hardware-based redundancy solutions to achieve high availability. But when coming into the cloud, we kind of like think on a different strategy. We can focus more on the meantime to repair, to reduce, I mean, maximize our automations in the cloud to reduce the meantime to repair, use a lot of different open stack features or cloud features to achieve software-based redundancy to achieve high availability. So it's kind of like shifting of focus. So we are moving away from mid-increasing meantime between failure to reducing the MTTR. So it's a shift of focus between on how can we design a high reliability systems. So demo, okay. Next one I'm going to show is a quick demo. So in this demo, as Steve mentioned earlier, I'm going to use WordPress as an example. I believe most people understand what is WordPress. And today a lot of company corporate, they also use WordPress for their corporate website. So generally, I mean WordPress, well, you can argue that is basically a two tier applications, right? So basically the PHP everything and database, you can split the database. But so in this demo, what I'm going to show you is I'm moving the web tier into the OpenStack Cloud by keeping the DB intact in your existing environment. So, okay, so what you see on this screen here is a video basically, okay. So this is the database service. So this is where the WordPress database is being hosted. So that's the internal IP addresses for the database. So I'm just in this screen basically just showing you that there's a database XZ. And of course, don't use root. So this database will be used by the web server, which I'll show you later. So there's a show databases. And you can see there's a WordPress database here. And the next screen that you see is the VM in the OpenStack Cloud that actually will connect to this particular database. So conventionally, when you're designed, when you when you deploy a WordPress application in your existing virtualization environment, you do the same thing. So WordPress, you have to configure your WordPress config file, WP-config.php. You basically configure the parameters to point your WordPress application to the database clusters, right. So I can see here, that's the DB name, username and very secure password demo123. And connecting the database host that you see just now. Okay. So this is what we do in the virtualization environment, right. Nothing change, nothing special. So we can do the same thing in the OpenStack Cloud. And what you see on the user front end, so this is our private IP address for the web servers. And what you see from the user front end basically is nothing different. So basically the website is a very simple website. So there's two web servers hosted in the cloud and there's no differences. So we can do the same thing when you want to migrate your WordPress website into the OpenStack Cloud, keep in the web, migrate the web into the OpenStack Cloud but keep your database intact in your existing environment. So this is one approach that we can use. But using this approach, we basically follow all the P2V approach. We don't re-architect anything, right. But in this approach, we doesn't gain the best benefit of cloud. Okay. So the next demo that I want to show you is a different way of doing things. What I mean is you can view your application as a different component. So an example is, for example, if you're building an e-commerce website, you probably have a building component, your login component, you have a product catalog. So you probably can start moving, consider moving your product catalog only into the cloud. Of course, this kind of model, this kind of approach will require some of re-architecture or redesign of the application to split your product catalog and move that into the cloud. And again, I'm going to use the WordPress as examples. So in this WordPress examples, what I'm trying to show you is, when you hosted a corporate website, right, so usually you have a content owner, they'll update the contents, right. And the website visitors basically just read the contents and they visit the website and they read the contents and they don't do any updates to the website. So you basically split that, split them into two different view. One is for the website viewer and one is for your content owner. So you can still keep your WordPress content owner those WordPress servers on your local virtualizing environment and for the visitor content, the public content, we can, in the WordPress, you can actually use some plug-in to convert those into the static content and in this demo I'm going to publish those content into the OpenStack object storage, Swift content, the Swift object storage. So the demo basically is very, very quick demo. Basically, I have wrote a script and read the same WordPress content management system just now and for every static file, convert them into the static file, static image and push them all the way down to the OpenStack cloud. So what I did here behind the scene basically is reading all the WordPress file, static files and using the OpenStack API to push the content into the Rackspace public cloud. So what you see here basically is reading the file and pushing them into the public cloud using to the API, everything automated. So this is one approach that we can do especially for new adopters when moving into the cloud. As you can see here, this is the previous web service, nothing special. So when I push the content into the cloud, this is on the Rackspace object storage. So everything looks the same. So the Rackspace you can use object storage to host all the static content but for the content update, you can still keep in your WordPress service as a single visualization and do the update and then push the static content into the OpenStack cloud environments. So this is one approach that we can use. So another advantage of using this approach is like using a push model, especially coming to a hybrid model. If you deploy your web server for example, if you deploy a web server in the public cloud and if you want to keep your database in private cloud, more often you are not in a security concern because you don't want to expose your database to the public cloud, right? So one way we can do is using this kind of approach by pushing the content into the cloud rather than pulling from the internet. So a lot of times when you design your application, your security is always the first concern, right? So this is one approach that we can use. So when you want to move your application to the cloud, there's always different strategies that you can consider. So don't just restrict yourself to the old way of doing things. So think about a new way and thinking of the box. So think about the new ways of doing things. There's a different multiple approach that we can use. So these are two very simple examples that we can use. I hope you understand what I'm trying to say. So with that, I'll pass the time to Steve talk about some of the 12-factor apps. Right. So what we've been looking at so far are things that you could do with an application architecture that don't require you to reach into the internals and start tearing it apart and refactoring the app and things like that. Now, there's been a lot of popular discussion for the last couple of years, a company called Huroku that does a lot of excellent work lifting applications into the cloud and providing cloud services for them, publish this idea of the 12-factor app. Now, I'm not going to walk you through all the 12 factors right now or anything. Depending how old you are as a Unix person, a lot of this you look at and you go, well, yes. But putting it all together, it actually helped a lot of people think about how these things can be addressed. Continuing with the idea of WordPress, there was a company that went out and took WordPress and actually turned it into a 12-factor app, almost. If you go and look for a 12-factor WordPress, they have a wonderful, wonderful long blog post that takes you through each of the factors and all of the decisions they had to make. And when you look through it, some things were absolutely obvious and absolutely easy. And those were often the things that we should all be doing with our applications anyway. The idea that everything is under version control, well, you can kind of check the box on that one, it was very easy to make sure that worked. When you start looking at things like the dependencies, the architecture of the application of WordPress itself already allows you to encapsulate all of that in the composer.json file. But when you start stepping into some of the other things, that's where they started running into problems. They had to think their way very carefully through how they handled configuration, because the 12-factor app, and the 12-factor apps are kind of that step towards doing microservices. Well, how do you get things into the environment? They had to be very careful. Some of that stuff belonged in configuration rightly, and some of it, you needed to get bootstrapped into the environment properly. They ended up replacing Apache with nginx, because when you start getting into how do you deal with things like sessions, if you're going to go into a stateless world, how do you handle things at the concurrency level of port binding, they just needed to literally rip and replace the HTTP daemon itself. So when you start thinking about that next step up for how do I get my traditional three-tier app into an open-stack cloud- enabled world, that's when decisions will start to possibly get a little more expensive. You will have to think about some of the factors. But many of these things are things that you can actually, are just good practices. And these are things that you'll handle culturally rather than technologically. It's almost think of it as a different bucket of money in IT, because you're going to have to train people differently. So that was part of the learning that they went through. I would encourage you to go and read the blog post, because there's lots of depth and detail there that, again, will hopefully provoke interesting questions for you as you look at your own three-tier applications. That's not the only way to think about it, though. Again, Leong's demo showed you how to bring a lot of your app into an open-stack enabled world. And it was dealing with a lot of things that really were infrastructure as a service types of things. Things that, you know, are the core services of open-stack. But there's other things that open-stack as it evolves has been providing. So you could start to look at things like, can you use Trove as a way to handle your database? Now, my last experience a few years ago in on the IT side of the world. I worked for a company that was, we had a lot of static content. We could do things with Swift. That would have been an absolutely excellent way to do things. But our database world had evolved to become so central to the way multiple different applications were feeding off the same collection of tables in the same database. And again, over history, it had been, well, normalized. And then parts of it had been denormalized. And that evolution of what had happened to the database was going to make that evolution to a cloud-based architecture in open-stack extraordinarily difficult. That was a set of choices that one company had made. Your choices may have been different, but I would encourage you to think carefully when you start brushing up against the database. But you may have an opportunity that a class of your applications and your application portfolio, you can lift very easily using Trove. Looking at things like if your application is conducive to being refactored a little bit and you can start to move yourself into that kind of 12-factor app space and things become a little more stateless, you can start thinking about how you might do containers for that application. Now, again, it doesn't require you to do everything absolutely. You may not need to move the entire application into a containerized world using Docker. You may be able to tear it apart and refactor pieces of it and start to move it. So you've got lots of choices here. I think what Leong and I want to do is make sure you're thinking, you're not approaching your application portfolio with this mindset that I'm going to have to forklift entire applications one at a time and all of the work that that might be. There's lots of advantage you can get moving into a cloud world and all the cost savings you're going to get that way and the kind of time to deployment and the automation that you'll be able to apply just by doing these things one at a time. I'm going to hand this back to you again. No, I just tried to wrap up what I was trying to say. So I believe that every technology must create value to business. When today if you want to migrate your applications to the cloud, think about what kind of value or what kind of pain point you're trying to solve from the business perspective. You don't just want to migrate out of no reason. So think about why you want to do that, what is a goal and what kind of value that you want to create to the business. So always the same thing I mentioned in the previous summary, every technology must create value to the business. If the technology doesn't create, doesn't add value to the business, it's useless. So with that I think, oh sorry. I would like to point out that was not me. I am normally the one that is death on hardware in any kind of a presentation.  Okay. So Leong and I are part of an open-stack working group. The enterprise working group has been wrestling with issues for better part of a year and a half to two years. There's a number of sub groups in it. One of them is the cattle and pets subgroup. And we meet regularly. That's the mailing list for it and the weekly logistics. I would encourage you to join us. Can I have a quick show of hands, how many people actually work in enterprise IT here? Excellent. That is absolutely excellent. What we've suffered from for this past year is too many vendors. Yes, I am one and Leong was one of our few. Used to be. Used to be one of our few true customers from IT. And we're trying to wrestle with questions like what are the problems preventing enterprises from moving to open-stack? And it's a collection of vendor product manager engineers going, well, this is what I think they'd have to do. We would really encourage you to please come and participate with us. We would like to use this as an opportunity to deeply understand the things that we can be carrying back through the product working group and building blueprints that cross projects and such so that we can genuinely begin to evolve open-stack into ways that will help people in the enterprise space be able to more easily migrate their applications. Yeah, one of the main reasons for this working group basically you want to understand what is a barrier on moving your applications or conventional applications, the patch model into the cloud. If you have any problems and issues, and come join us in the working group and we will try to help work as a community to derive a solution that can help you to migrate moving into the cloud. So this is our email address. If you guys want to contact us, you can... I am always happy to take email. And before we go to Q&A and if you're joining the Intel Passport program, do ask, go for Chris. It's over here. You can get a stamp. And with that, we're going to go Q&A. Are there any questions? Please. Do you want to use a mic? Do we have a mic? Yeah, we have a mic. Thank you for that. It's pretty interesting. But what's the point if you don't actually move the database? Sorry? What's actually the benefits if you don't move the database? I mean moving the... moving and I understand that you can sometimes transfer your data. But if we're not dealing with data in OpenStack and we're not dealing with transactional data, are we actually really addressing the enterprise? That's a very interesting question because most of the people come to me and say that can we keep the database first without migrating because database is the key, right? Database is very critical to applications, especially for new adopters to the cloud when you're not so familiar with the cloud operation model, the cloud native way. If you start moving a database without understanding how it works, it's a very high risk to use, right? Of course, I'll be happy to help you to move your database to the cloud-based environment. As I say, we plan for the migration. We don't migrate everything at one shot. It's very high risk. From virtualization to cloud, to a lot of enterprise IT is a big challenge. So don't do everything at one shot because that's a high risk. It's basically a risk assessment. Of course, definitely, you can do database migration. I have no objection and I'm happy to help you on that. But for most companies, they are very concerned of losing the data. So that's why a lot of companies approach even eBay or PayPal. They're also keeping the database layer as the same environment and push the web here and app here to the cloud first. And slowly, once you get familiar, we start moving the database into the cloud, either use Trove or using the same building of multiple VM SQL clusters in the cloud VM and learn how to adapt the database. The question speaks exactly to the big problem because so certainly, you can get the scale of benefit at your web tier and even the application tier and that is a huge benefit and a huge step forward depending on the nature of the database. And I believe me, like I said, for my most recent experience on the IT side, I realized how fraught that can be depending on the architecture that has evolved over time and how much diligence and rigor may or may not have been applied. But in some of the simpler situations, you could even use OpenStack today to simply get high availability for your database. So you're scaling it differently now, but you're replicating the database because you can replicate the VMs while you're doing more of a scale out kind of thing on the application tier and the web tier. So again, it's that teasing the layers apart and applying different strategies to each of the layers that is extraordinarily database dependent. I appreciate that, that I'm not suggesting that that was easy or would work for everybody's data environment. If you're really interested in moving database to the cloud, I would encourage you to look into the Trove, the Trove service in OpenStack. That is the database as a service. A lot of companies still doing POC and try to understand how it works before they move on. Sorry. Exactly. Yes, database support would be critical. The difference between if you've got a strongly web-based application and it was all MySQL-based, you're probably in fairly good shape. If you were extraordinarily dependent on a complex Oracle or SQL server database, you're going to need to make different choices. Today, the open source Trove, they only support a few open source database. If you're working on other database such as Microsoft SQL or Oracle kind of things, then you probably have to approach the vendor-specific solutions for Trove. So that depends on what kind of things you use. I certainly know that from HP's perspective, we've been working with Tesora and they are out in the marketplace here. And they've done lots and lots of plug-in work for different databases. Again, I appreciate that we're kind of hand-waving here because of the complexity of the database, but that will probably be where you discover most of the evil things that have evolved in your data environment over the last decade. And that's part of the challenge here. You will have some vendors that you may well have encountered some of my own colleagues that will tell you, well, you just have to rewrite everything into a cloud-native way. And I realize that so many of the applications we're talking about are business-critical applications that you may have done the minimal port from a traditional Unix environment to a Linux environment 12 years ago kind of thing that these are applications that have been long-running, long-established. The data environments that move with them are equally complex. And complex not just because the application was complex, but you've made different choices over time. So depending on the diligence all the way through the history of that application can really affect your ability to port it. Other questions? If not, I'd like to thank you all very much for your time today and your attention. Thank you.


Hey there friends, thanks for checking in at Shot Show at the Sig Sauer booth and the one that really caught my eye is the Sig P320X5. Now I already reviewed this, took it to the range, but I haven't stopped thinking about it since. It's an outstanding firearm, 5 inch barrel, comes with 4 21 round magazines, has lightening cuts on the top of the slide, full 1913 rail and flared out magwell. That face trigger really enjoyed this gun. I think this color right here is very cool and I just love it. I think it's an outstanding competition gun that has so much to offer. But we're going to talk about a couple of other things here that Sig Sauer is offering this year. It's brand new. Hey everyone Phil Strater here at 2019 Shot Show and with the firearm guy and I'm showing you the bell of the ball. This is the head of the show for us this year. This is the 320X compact. This is the latest addition to our X-Series lineup and as you can see it is really small but it has all the things you love about the X-Series lineup like the flat trigger. This gun has a straight flat trigger that breaks at 90 degrees, it feels great to shoot. It also has the X-Series serrations, the X-Ray 3 sights like you'll find on the X-Carry and of course what would an X-Series gun be without a grip module that's contoured just for you and man this is awesome. We have completely redesigned this grip module. We shortened it so it takes 15 round mags rather than the 17th that you're used to on the X-Carry but we also took off these lips here on the side so you can see this is a smooth sided grip module here at the top of it. We reduced the upper part of the grip module here under this beaver tail and we actually contoured it to give it a more straight smooth rounded feel here. Not to mention the fact that it has the trigger guard undercut. So this tiny grip holds 15 round magazines but it also gives you a nice high purchase on the gun so you can get your hand nice and high up, feels amazing. One other thing that has changed on the X-Compact and all X-Series guns for 2019 is an extended slide catch lever. These are made a little bit bigger for these models and they're very easy to manipulate whether they're locking the slide to the rear or releasing it. Now it still has the rear sight plate assembly which is the rear sight plate and the rear sight as one unit. However, this is cut to accommodate a Delta Point Pro footprint but we're also making an upcoming sight called the Romeo 1 Pro that you'll see in the next few months and the Romeo 2 which will be coming out a little bit later. What you get is two magazines with this gun and you're going to be able to see these in about probably around April shipping to your stores. Expect to pay just under $700. The P365 manual safety. So this gun has all the features we've come to love with the 365 it is an award winning hugely successful hit but we had a lot of requests for a pistol with a manual safety. So we actually equipped this gun with that and it's ambidextrous so it's available for both sides. There's a right-handed and left-handed shooter. The trick was keeping it slim enough to be still concealable but usable enough to where you can hit it with your thumb no matter how big your hands were. And the way we did that with these ledges on each of the safeties, each safety has a little ledge just like the slide catch lever and the takedown lever. The safeties have that same ledge and it's really really usable, functional and if you want that added level of security with a manual safety you can now get it in the 365 and if you live in Massachusetts this will be on the updated gun roster. This gun has already been reproved and we sent samples in for them to go over and this gun will be available very very soon. We're going to be shipping it around March or April and you can expect to see it in stores. The pricing is the exact same as the P365 expect to pay about $4.99 for it in your stores. I'm holding the new Spartan II 1911. Now the Spartan II is a new family of guns that you can find in our single action line including the full size 1911, a carry version of the 1911 and the 238 and 938. The first thing you're probably going to notice is the finish. That is the big change on this series of guns and what we did is we took a coyote tan PVD finish on the upper and the lower and we threw it into the tumbler and said turn it on until it looks like it's worn and every time these guns come out of the tumbler they look different. So your gun is going to be unique no matter what gun you get. You'll never find someone that has something similar and it's a really neat rugged worn battle worn finish. It's really really interesting looking and I love it. I'm actually doing this to my competition 1911 for this season and of course what would a Spartan II be without the Spartan helmet. You can see it on the top of the slide there. It's burned into the slide it looks amazing. Of course our famous saying you've seen that come and take it. We want you to come take this gun out of the stores. It's going to be shipping in a couple of months and of course the Spartan grips have been completely redesigned. Now there's a Spartan profile on the helmet. Really neat look here. Really functional gun as well. It has siglight night sights, skeletonized trigger and hammer, extended beaver tail, ambi safety and we added a magwell for the 1911 carry in the 1911 full size so you've got a little assisted reload there with the extended magazine all in the Spartan II package. It's going to hard to go wrong with this. It's a great looking pistol and it's going to be shipping soon. You can find out more about the Spartan II lineup at sixhour.com. So there it is guys. A lot of exciting stuff happening this year with six hour and I'm really digging this 1911 has a great feel to it and some of the accents on it and the way it's battle worn makes it super cool and I think you guys are going to like this firearm as well as the other ones featured with six hour. If you like videos like this please subscribe and share. I always appreciate thumbs up button. Thanks for watching and you guys be safe.


Appalachian Wireless now has new forward pay prices where you can pay up front and get the data and features you design. Five gigabytes of data, just $39.99. Unlimited, just $79.99. Better service, bigger savings. That's today's Appalachian Wireless. Appalachian. 38-year-old Lavelle McCarty, a Johnson County inmate, was indicted this week by a Pott County grand jury on a kidnapping charge after allegedly attempting to escape from authorities while being treated at Packle Medical Center. Lavelle McCarty, also known as Shelly Ferguson of Sitka, was in the custody of the Big Sandy Regional Detention Center while being treated at Packle Medical Center last week. Pike Commonwealth's attorney Rick Bartley said McCarty attempted to escape from custody while she was a patient at the hospital and allegedly attempted to take the corrections officer guarding her hostage with a plastic knife and a roll of medical tape. She apparently tricked the correctional officer that was there with her by saying that she needed to use the bathroom and when they took the restraints off her handcuffs, she emerged from the bathroom and attacked the woman that was guarding her from the detention center. She apparently put a plastic knife to her throat and told the woman that she would cut her throat unless she allowed her to escape. The officer did not know it was a plastic knife because it happened so quickly.  The alleged escape attempt was foiled after the officer fought back and others intervened. Authorities are now trying to figure out what to do with McCarty. She was being held at Big Sandy on charges out of Johnson County and also on a felony warrant out of Ohio. We're contacting the officers in Johnson County as well as we're going to try to make contact with the officials in Ohio to determine do they want to come and get her and take her back to her to face charges or do we need to process all of our charges first and then let them come and get her after we finish with her. And no determination has been made on that yet because this incident did just happen a few days ago and we're all trying to coordinate our efforts. McCarty was indicted on felony charges including kidnapping and third degree assault. The kidnapping charge that McCarty now faces is a class B felony punishable by up to 20 years in prison. In Pikeville, Chris Anderson, EKB News.


Oh my god Hi, I'm Lavi and this is Olli We are attempting a new Guinness world record to become the youngest pair to circumnavigate the globe by motorcycle After riding 3000 miles across Europe, we are now ready to explore the roads of North Africa Click the subscribe button to follow our journey around the world And let the adventure begin Alright, just on the outskirts of Dachla So a little bit hidden away And we had some really cute neighbors as well The little kitties But let me show you guys where we're heading today without the cat Okay, so we are way down here in Dachla And we are going to be making our way off the spit And back down the route national one Trying to make our way about halfway to the Mauritanian border So we thought that getting all the way to the border of Mauritania Would be a little bit of a struggle Especially as I think the border closes at around 5 p.m So we weren't going to try and get all the way there And then try and cross the border So we decided we'd go about halfway And then we can just make an easy day tomorrow Cross the border and arrive in Nuadibu Not too late So guys, please, please, please If you haven't already, subscribe to our channel right now Before you continue watching We really appreciate it It's already 10.30 so better hit the road Oh, Bumblebee fired up for this morning Look, they sort of styled this campsite on a sort of ranch style Look at this, like with a white picket fence And some horses all sticking their heads out this morning Hello, good morning You know, I haven't seen anyone around for the whole morning Yeah, that's true Okay, I will jump off Yeah, okay, let me just chop that up There we go There we go Okay Well, that's another reason why it's good to pay When you arrive Because sometimes there doesn't seem to be anyone around when you leave So, well, already paid them all good to go Let's rock and roll Wee So we're going to start by heading down the spit towards Dachler And just have a little look at the city of Dachler See what it's all about, see what it looks like We'll grab a couple of bits and bobs, grab some groceries And then we'll be making our way off the spit And making our way south It's nice and fresh this morning 22 degrees Yeah, I've closed my vents on my jacket this morning Because, yeah, it's on the border of being chilly And last night it was cozy, no? Yes It was cozy Wee Beyond venue, Dachler Look at this, got a nice little statue on the way in Yeah, very arty And a row of palms And very charming lights Oh, yeah The street lights, they look amazing Oh, yeah, that's really cute, isn't it? It is really cute It's still like half, everything is under construction, though Yes It looks like this is an old fort wall Look at that, it's like a military base Wow I mean, there just seems to be military bases everywhere along this coastline It's unbelievable Well, I feel super secure with all these police controls And I'm a little bit thankful as well That they have so much police control here Yep, nobody's going to mess with nobody around here with all these guys around No But that's what people have told us all across Morocco Oh, you can walk anywhere you want, anytime it's safe, it's all good And you know what you feel like? You do feel that it is safe Everyone is very friendly, it feels really safe And I never felt once unsafe or quat or anything like that It was a really nice visit here Yeah All right, so we've got our groceries We've got our fuel And we have seen as much as we want to of Dachla So now we're going to make our way off the spit Get back on the mainland and make our way south, south, south South, south, south This is the reason why people come to this spit, to Dachla It is packed full of kite surfers Full of kite surfers Wow, it's insane really You can see probably like 50 kite surfers, maybe even 100 kite surfers out there All year round, the perfect wind conditions really It's just like perfect little playground for kite surfing It's super windy, there's no waves It's just perfect, look at that I kind of wish that I could kite surf now But we've got our motorbike, this is our thing But it looks super cool, it looks like a really nice place to come Yeah, it does If you like kite surfing Look, we can finally see our destination, Dachar So we just did our third and final checkpoint At the roundabout to the Dachla spit And now we've just hit the road going south And from here there are no more major cities of Morocco And you can see already that the road is way less developed Than it was just before the roundabout What was a really nice big highway Is now a sort of semi crumbling track It's still okay But compared to what the highway was like on the other side before Dachla Yeah This is pretty much just a straight shot to the border now Yeah, the temperature is 27 degrees So not too hot, it's quite pleasant The sun came out as well a little bit So it's a really nice atmosphere at the moment We have some camels ahead I love them Look at them Yeah, I'm just coming to say good morning Good morning guys That's cool That's very cool Hello So we've got about just under 100 miles To get to a place that we've seen on Ayovalanda It's basically just a restaurant sort of service area In the middle of this desert And apparently if you ask there They'll let you just pitch the tent next to the restaurant That's what we've read We're going to go check it out And see if we'll be alright Stay there for the night Another lunch break Hiding behind the bike From the intense wind To pull quite far off the road Spot like this And we can just about see On the other side of the bay A bit windy but nice Unfortunately at this point Our mics suddenly stopped working for the rest of the day I guess the combination of the wind And the sand is really not good for electronic equipment So let us sum up the rest of our afternoon on the road First we had to stop to say hi to some camels Then we came to a beautiful hilly-ish area That made a nice contrast to the endless flats of the desert so far We saw some more cutie camels And a whole lot more sand The wind was really starting to pick up And sand was blowing all over the road And in our faces So we were very glad to finally see Emerging from the vast nothingness A sky blue painted cafe Sitting alone Ready to welcome weary travellers in With a cup of hot mint tea Our stop for the night Thank you The guys in the cafe said It was fine for us to pitch our tent At the front of their place And we've got this little wall for protection Because Look at this when we head around the wall Good evening guys Oh my god we're just hiding away It's super windy outside It's like the wind is just blowing the sand Into our face the whole time So we're hiding in our tent now Even behind this wall We've still got quite a lot of movement of the tent I feel sorry for poor bum We'll be out there all alone in the wind But we had to have a rest and a little chill out After all of that sun and wind Because tomorrow we have a big day Coming up crossing into Mauritania Yeah the last day in Morocco Yes our last day in Morocco So it will be really really exciting tomorrow And we have to get a good rest Because we don't want to stop too late tomorrow Yep so we're just going to cook up some noodles And eggs as usual And get an early night and an early start tomorrow For the border So that's it from us today We hope you enjoyed the episode If so please give us a thumbs up Subscribe to the channel Comments below We will see you next time So the guys from the cafe Just came and brought us some biscuits And some wafers And some mango drinks They just came out and said Oh do you want some fish And we said oh we're vegetarian So they said okay We have some biscuits We were like oh yeah if you have biscuits And then they just brought us out A load of lovely stuff That's really really nice Thank you so much guys Thank you Abdul