Okay, hello. I'm Redon, Redon Skikuli. I'm doing, I'm probably doing some mistake based on the reactions I get. So we also have like Albanian, the first one which is the country I'm from, English, Bonjour, is the French one, and Dutch, is this okay? So is there anything else missing? No? So we had a very nice discussion yesterday with some of the presenters at the dinner, and I learned about all the complex things about the language. I think I'm in a good, good to go. Perfect. So, and this also means hello, what's up in Albanian? So it's spelled with she, at age or whatever. So usually in presentation at FOSDEM, I've been here for three times, I think, or four. Usually the majority of the talks are quite technical, and I feel quite not qualified to follow them all, but I'm very interested about the human elements of each presentation, all the presenters. And since there are not a lot of them, so I said, I was thinking that I'm going to do the start and say, before presenting the presentation, I just want to, the application, I just want to share the reasons why I started it, along with some other people. So as I mentioned, this is me when I was a kid. I asked my mom some photos, and she sent me like, I don't know, everything she had since I was a kid. But these are only two of them, and I was born in a city called El Basan. These are the locations for the city. I hope these are correct. The good thing with locations is that it's a universal language, so everybody understands when we say north and east. Everybody understands where it is. So El Basan, if you go to the map, is in the center. In Albania, if you go to the map of Albania, it's exactly in the geographical center of it. It's a very boring city in general. Is this getting recorded? It's a very boring, but it has a very geeky element, especially at the neighborhood where I was living. It was the train route that was going there every day. And the most interesting part was that our parents were always telling us, don't go there, and it's getting recorded as well. We were not going there every day. And it was amazing because we are having all these networks of trains, and it's very interesting to understand how they work. So I think that was the first moments where I understand that I like to understand how things work in the beginning. So El Basan is in Albania, and this is the location of it. And it's probably there. People don't know where it is, which is okay. No offense taken. It's near Greece. Italy is there as well. And some other non-EU countries, which are bordering us. I'm not going to tell more about it, but it's well-known. I think it's the most well-known thing is that from 1945 after the Second World War to 1990 or 1991, we had a dictatorship. And one of the things that the crazy guy we had was that he built a lot of bunkers, like in mountains and also in the sea. They are counting, I think there were more than 173,000 of them built. It's a similar situation with North Korea right now. So getting from this environment, Albania was very closed, probably the most closed. We didn't have, for a decade or two, we didn't have any diplomatic relationship with any countries in the world. So a lot of people, nobody was going in, coming in, a few people were going out. And it was very bad to go. So in 1997, my parents and myself, we went to Athens, which also influenced me a lot to do what I was doing. And it's a neighborhood, I was staying a lot in a neighborhood called Exarchia, which is a very political neighborhood in general. It's well known, especially if you are into all these things. So there were these very, that was the first moment I learned about doing things, people were talking a lot. I was amazed how much people were gathering and talking about politics and all this stuff, being equal and all the elements that you need to discuss in a collective way. So this is also something that influenced me, this from the uprising of 2008 when a kid was killed there. And of course, you're going to see a lot of these signs, which unconsciously influence you in one way or the other. So in 2012, I went back in Tirana and with some other people who started a very small hackerspace, which I think now is five years, we take proud in the fact that we have slightly more diversity in terms of getting not only white boys like myself, but the majority of people are girls that hang out there and are under 25. We also had one of our members be nominated as Red Hat, Open Source Girl of the Year. She's one of the finalists. So we try to be diverse, although there are more elements in being diverse than just having not only white boys in the room. One of the events we do is Open Source Conference in May, in the third weekend of May. And I know a lot of people are joined there as well. So we had some, we are still, there are a group of people working in the hackerspace, which also has this, we try to be as open in decision making as possible. And this is one of the things I love, having this background of, you know, politically influenced from my teenage years and after that. So we have different working groups. There is a working group for Fedora. There's a working for Debian. Mozilla has a lot of contributors. And one of these working groups is OpenStreetMap. And another one is Wikipedia. So there are like five or six working groups that are quite active. And I started, my first, if you can see there, it's in September 2012. I started playing around with OpenStreetMap. I'm pretty sure there are more active contributors of OpenStreetMap than myself. But I think what I understood during this all this period is very important also to try to make a lot of community building so that the local other people start learning the importance of OpenStreetMap as a platform, etc. And after editing, if you see the stats and if you go to my profile, you're going to see that I just do simple stuff. Like I just edit the working hours of some cafeteria or let's say I just map buildings based on the big imagery, not complicated stuff. I'm being honest when I say I've been trying for a long time to learn Jossin. And I failed to learn it as long as I want to do it. But what I was fascinating a lot was the fact that there are other applications using OpenStreetMap as a base map to create very, very useful things. One application I use a lot is maps.me. And I was using it to get around Brussels these days. And there is also StreetComplete, which I think is having a lot of traction out there. And I think older than maps.me should be OSMN, which I don't have it right here. The thing with all these platforms is that they, some of them, or let's say the ones that are more mainstream or are used more, try to have this tendency of being a Swiss knife. Like you can also go from point A to point B. You can also search a category. You can do offline search, online search. You can also edit the map, et cetera, et cetera. But what I really like more are these apps like bike citizens. Or there is another one I like. It's called Transporter, which is about the open, it's an open source map about public transportation in different areas. And I'm following their GitHub account, which is quite active lately. And I really like those, not the general, like the general, but the apps that do specific tasks. And they are good at it. And OpenStreetMap as a base map for this is quite interesting because it lets you do also the most complicated tasks if you want to navigate, but also the simplest tasks. I think bike citizens does this, but also there are a couple of other apps about biking that are doing the same job in one way or the other. So yeah, as I mentioned, I really didn't, I think there are some elements for platforms like OpenStreetMap or some apps that can go even more mainstream. And you cannot do that in my opinion by being a Swiss knife or doing whatever you can with one application. And also web apps. So being fascinated by the capabilities of a platform like this, I said, well, there are some things that are missing out there. For example, I live in a city which is not big. I think it's something less than half a million people. But it has a lot of things I need on a daily basis. Being, I just recently got a bike and I need like a drugstore, for example, or points of interest that are not branded or they are more like categories, right? So if you are living in a big city or you travel from one city to the other, so in Brussels I need to go to the supermarket. I don't know what the point be when I'm going to go is. I just want it to be close to myself. And this is a need I personally found that it's much needed all the time. So I also care about privacy. And I really like, it would be nice if I wanted to edit OpenStreetMap but without all the 100 elements that you can go there, right? So, and of course I didn't want it to be like a startup or to ask for money, investments and stuff like that. But I also wanted to be a community led. What I, growing up, I understand that I'm very good on initiating stuff and making the structure of so that other people can join. But after that, like, I'm not interested anymore. So this, when it's community led, like community, you are not responsible anymore after a while. You're responsible in the beginning, but after a while it's so, for lazy people, this is the best approach you can have. And this open source communities are the best in implementing this. No shareholders and you can do something else or you can contribute on the project you started or not. Free open source, of course, respect the privacy. But also we need, going back to the story I told you about Athens, you also need something that is fair for people that contribute and also the people that initiated this process. So it's like, I don't know, like, you know, having a fair system, financial system for people that contribute. So this was all the thoughts before starting Citizen as an application. And if you go to citizenapp.co, you're going to see the old website. But now we are working on having it on GitHub pages so that more people, because we have Twitter messages, hey, I want to translate your website, so how can I do it? So now we are moving it on GitHub pages so that more people localize and translate it. And you can also download it. It's only available on Android for privacy reasons. No Google Play plans at the moment. And if you go and you open the application, you're going to see different categories. These are six, but I think at the moment there are more than that. So transportation, gas stations, drug stores, banks, ATMs, mobile phone stores, markets and kiosks. And there are a couple more. So if you go to one of these categories, you're going to see banks, ATMs or exchange. If you live outside the EU, an exchange store is very, very important. And you see some basic information when it's open, when it's closed, the name of it. And you can, at the moment, you have basic filtering. If the information is on Open Street Map, you can see if it's open 24-7, or if you see a lot of results, you can make it sort it alphabetically, kind of. And you can also see where in the map your location is. So this bank was there. Now you know where I was staying before. But if you click on that point of interest, you can also see more details, like if it has wheelchair access or any information about that that is on Open Street Map. Not all of the information, but the main ones. And if you click on directions by car, you can have the very basic navigation of how to go by car. At the moment, this is very limited features that there are in the app. But you can also edit it. If you are an Open Street Map editor, you can just log in easily. And you can also edit opening hours. Or if it has a Wi-Fi connection in the cafeteria, this is very useful. And other stuff. Everything is done live in terms of that there is no offline usage. You just get connected. It's very nice. It's that simple. It's a very nice interface for Open Street Map for people like my dad or like my mom that just want to do this without getting into the trouble. And you can also have some favorites. This is the about page when you can log in or log out of Open Street Map. And you can also have some more links about the website and stuff like that. So as I mentioned, I'm quite lazy, so I don't want to do everything by myself. And these are some main ways of how you can get involved if you like the project, which has started only for three or more months. So there is a GitHub page with all the code, but also there is some different repo. The code, the Android development repo has some issues that are done by the core team that is working on this. But also there are other people. I was happy to meet some of them here as well. There are all kinds of issues like design, which could be better or fixing some bugs. There are a lot of bugs at the moment. But you can also get involved. There is a repo about tasks, any kind of task you can think. Like for this presentation, I can open an issue and write down and people talk there and see what's happening. That's quite an active repo at the moment. You can get involved in localizing the app. I think it was launched in October, if I'm wrong, November, October, November, something like that. And already, these are all these languages translated. There are not a lot of strings. I think 100 or 110 strings about the interface of the application. We're going to also help now in the website that is just getting launched. There are some Chinese simplified and traditional or Norwegian translations from people I've never met before, which is a weird feeling when you see things like this within applications that have just started. This week, we're going to launch a Patreon campaign, which means that you can give one euro on a monthly basis and get something back, which might be from stickers to endless love from all the people that are working on this. Endless love costs more, usually, because these are levels that you get. Of course, that's the big trend now with cryptocurrencies. You can also donate by Bitcoin, but there is a big transaction fee, I think five, seven euros or something. Only if you have a lot of hundreds of thousands of euros, that would be a very good idea. We will not ask you about the source of your money, definitely. So what about the next steps, because we don't have much time? So this app also started as a tool for people to pay in a very anonymous way. I know it's complicated. There are tons of everybody talking about this right now, but I think the first applications that will connect points of interest like mini markets, gas stations with a platform that people can pay easily and anonymously would be a very useful tool for everybody. So this is one thing. So if you are at the gas station, the idea is to work. It is a long shot task, by the way. So you just pay for the gas station with your crop crypto wallet embedded on the app. We can talk about this later. I know a lot of people will laugh. So there is also about if you want to contribute and you also want some financial incentives, there is a utopian.io integration with any open source project where you can work on issues on GitHub or any other aspect and get some crypto payments from the platform, which is a very smart way to get more contribute. So you contribute and get better code that gets verified by us and you get your crypto, which again, you're going to be millionaires if you have a lot of crypto right now. So you can also help us on the community infrastructure on set up a mailing list in the forum, keyword lazy, and also I don't have also the technical knowledge to mess up with servers and stuff like that and even more improving. So if there are ideas, you can go to the GitHub repo and add any kind of new idea that you might have at the moment. Last slide. When I had the idea of the app, I just wanted for an easy also one of the reasons was that I wanted the easy way for me and other people to contribute to OpenStreetMap. So I introduced it to my niece some, I think, 10 days ago and she has already done 110 edits on her OpenStreetMap edit. So if this doesn't, if the application by itself doesn't work, I'm like, I'm very happy with it because no, even one person that started contributing in it, it's a very, very big win. And also the sad thing about this is that I feel the generation gap coming. She's so fast with the app and she edits everything. So she lives in El Baza now and there are no more cafeterias without any kind of information available at the moment because she did everything. Her mom shouldn't know that she edits only cafeterias and they also want rating now. Like she was talking with her friends and they want to rate it, rate the cafeterias. So these cafeterias are for old people and these are for young people. I tried to explain to her that that's not a good idea to do to comment on OpenStreetMap. So yeah, that's it. So I don't know if you have any questions. I'll be more than happy to answer you for 10 minutes. No, eight? Five minutes. Thank you. Sorry, I didn't get it. No, the privacy element, it's by far not where it should be. For example, the fact that we are using it's an Android app by default is a privacy issue. But there are some, for example, there is a Mozilla geolocation feature that you can integrate on an app and I think you get out of the Google tracking your geolocation. I'm not, unfortunately, I don't have to know how if that's true or not, but that's one of the features that we want to implement. Another one is that somebody proposed do not, how can I, because automatically it asks you for your location, right? When you open the app, it asks you for location. So one guy said, well, don't ask for it. So we need to remove it now. Don't ask for the geolocation so that people can zoom in, zoom out, and go where they want to go and see what's around. So these are the two features that are on the priority list, the integration with the Mozilla geosomething tool, and also the removing completely the ability to automatically connect to the geolocation from the mobile in terms. And also the crypto payments thing, it's quite a thing, but again, it's a long shot. No other questions? Are you downloading the OSM data line for your local thing? I think you said it doesn't work offline. Yeah, it's alive. It's alive. It's actually the app is, I know it's not good marketing, but it's just a nice interface or it should be a nice interface for open-street map data in a category. So it's alive. It's not an offline. Isn't that a privacy leak itself? If you are... For example, downloading a few bits near where you are and do them in a random order, so anybody watching your network communication won't know quite which bit you're most interested in. Yes, but that happens with any applications that access the internet at any point. So that's by definition an issue with all the applications that are connected to the internet. Or actually anything that's transmitted through the internet. Thank you very much.


And we're here at CES 2018, right here with Planet Computers and the Gemini PDA is working. Yes, here they are. So we're launching today. So this is the Planet Computer Gemini, it's a 4G keyboard smartphone. So it has it. So we're doing with a Debian. Yes, there's an Android 7.11 and Debian. So we have Linux as well as Android possibilities on the device. And you can close, you can show how cool it is. Yes, so it's closing and this is the final finish. So you can see it's going to brush the brush steel with a, so it's a final finish. And this is the Gyroscope logo? This is the Planet logo. You have the Gyroscope inside? There is, there is, yeah, of course. So what is it for? So this is basically the device itself. It's basically the people who want to create, people who want to type on the move, write emails. So write emails, do blogging, you know, essentially create write documents, write books. How do you see keyboard?  And you can even feel vibration on every time you type? Yes, you can get a sound and a vibration feedback so that it makes you feel more more comfortable. So I don't know if you can try, you can hear the sound, you can hear the sound maybe. Nice. And I don't know if you can feel the feedback on that. Yeah, it feels really cool. And what do you modify on the keyboard for specifically?  So we had like maybe even like five different iterations to get to this, to get this. So, but we're quite happy now with the keyboard function. And, you know, it's, it's, it's really interesting to use shortcuts and on the keyboard to do, you know, keys. So for example, I mean, one that probably is interesting for you when you need to take screenshots of different programs and so on, function R will take a screenshot. Nice. So very, very simple. If you need to decrease the brightness, you just do the brightness increase or decrease. Same with the sound, to decrease the sound or increase the sound. If we're, if we're going into, let's say, playing a video, let's say we'll go to YouTube. And let's say we'll put a video. This is going over 4G at the moment. Yeah, it's a busy conference. So, essentially, so here we'll put the sound on and then let's say we want to stop the video. So we'll do, we'll just stop and then we can continue. There's a rewind fast forward. Yeah, you can go, this is full screen. No, that, no, that's, that's a screenshot.  You can put your own apps here. It's not fixed, but if I want to go to Word, I can go to Word and start writing a document. And then at the same time, so I can now write a document and I can zoom as well here to zoom. But at the same time, if I want to split screen and continue watching the video, I can do that as well. What do you think the guy in 1997 who was using a sign, if you told him that it would be a version with this, what do you think he would say? Oh, personally, if I saw it, I would just buy it. I was a sign user myself. But yeah, it's, it's exciting. I think it's going to be very exciting for all the sign users. It's the first time that something very interesting is happening in the smartphone business, isn't it? It's a new form factor. Since the iPad, it's a new form factor. Some should call, there's no keyboard, nobody's doing keyboards anymore. Yeah, it's, it's, it's the only real, it's the only real keyboard, like device now. And we try to make it as powerful as we can. Nice. So the multi-window is working like this? Yes. And yeah, you can, you can then go back to anything that's running in the back as well. So you can go into, into the different apps there. Let me just close this. You can go to the YouTube, you can bring it up with a keyboard as well. And you can press it again and play. And there's a, there's two types. Two types. This side is for charging PC connection and any hub connectivity. Yeah. So there's a here for what? Sorry. This is for power charging. A USB-C hub. So you can do a hub and also for PC connectivity. On the other side, you've got a USB-C for external device like a mouse or some kind of card, SD card or USB. Yeah, and HDMI display. Is it display port or display link? It's HDMI out. Direct HDMI. I'll show you. So there's a cable. Oh yeah, nice. No worries, yeah. I saw Jeff earlier. Oh, right. Yeah. Yeah, please. Let's see if Ben's okay. Right here. Yeah. Which one is the HDMI cable? I have another one. So, can you show, why is this off? What can you do? Can you open it up? This is the tool. Yes, correct. This is the tool. It's just open basically all the part of the HDMI. So then you access the hard drive. You access everything. So inside you have the SIM slot. Single SIM? Single SIM, yeah. Single SIM. And there is also an e-SIM. Is that an international standard, the e-SIM? Yes, it's an international standard. It needs to be configured with the mobile operator. So that will be more standard. This is the SD card slot. And this here is actually quite interesting. So that's a new invention you make? This is, well, it's not an invention, but when we were developing the device, we had a number of people asking for an external camera. And basically we left a little space with a plug. So is it only for cameras or everything? It's only for, this is only for cameras. Can I connect like a key and display? No, no, this is just for the camera. But the device itself is designed to be modular. So the idea is that in the future these two parts can be detached and maybe, you know, changed. Yes, because one side contains the keyboard and the battery. And the other side contains the display and the board. But will the user be able to detach it or is it only? No, but they are easily detachable. So you can operate the phone part and keep the same keyboard? Theoretically, yes, technically, yes. It's not for the user, but it's very easy to detach the part. How stable is this part here? This one is very stable. I mean, this is where the magic happens. You know, when you close it, the hinge actually disappears and becomes part of the case. And when you open it creates this little leg so the device is stable when you type. Nice. So how good is the keyboard? We are now quite satisfied with it. We went through several iterations, different membrane, stiffer, less stiff and different kind of plastics used for the keyboard. And this is an HDMI and amperage slot. So basically it has a built-in HDMI output? Yes. It's not the display port? No, it's only HDMI. It's only HDMI. So is it HDMI 4K? No, it's full HD, yes. So it's a 1.3 or 1.4 HDMI version, I don't feel that. I guess so.  This is HDMI alt mode, right? Yes. Is alt mode type C for HDMI? Not alt mode, it's custom mode for the Gemini. Custom for Gemini? Yes. This is a unique Gemini cable. It's not on the market. Other people don't have this. It's in the connectivity pack, I believe, and it will be sold as a separate accessory. It's not expensive. And you can have one screen on here and your OS supports the second display or the second display? Not at the moment, not at the moment. It might be possible in the future, but at the moment it's the same. But how about with the Debian? Then it will be, Debian will be cloned on the screen. All right, that's awesome, it's working. So what's next? There's all the media is very, very excited right now. Yeah, yeah. There's a lot of excitement. Well, now we have to satisfy all our backers. And there are more and more contributions, so of course we're going to be producing the first units and sending them out this month. How many backers you had? You had over a million dollars? Yeah, so now we have about in terms of back, you know, there's basically in terms of units, there's about 2,750 units that have been ordered. So now we have to produce those units, and we're producing them right now. So that's very exciting to be able to do something where you don't need to have 30,000 ordered, but you can do something with 3,000. You know, it's challenging. It's something amazing like this. It's challenging, you know, but we have a limited budget, and we've done the best we can, I think. I imagine it's been a big adventure to work with your Chinese partner to get every step of the way and advance, advance, advance to something that works. You know, they're always challenges, but I think it's been a great relationship. And I think we've chosen the right partner, and I think as we're building up sales, hopefully they'll see their investment in this also pay off in a good way. And building a keyboard is not too difficult for the factory? So the keyboard, it's our design, but it's actually built by a keyboard specialist, a company. So it's a yes. Yes, so it's actually, it's actually, but it's completely our design. So in terms of, they will have expertise in the tooling of keyboards, but it's completely our design in terms of the Mark Martin Ritterford's design. He of course knows how the assigned keyboard was working before we have made some changes. And hopefully it's going to please people. How much work is there left for Debian? More than on the Android. And of course, we'll be putting the Debian release on the web. We are committed to open source to what we can open source. Yeah. So our things will be in open source. Is it a good question? We're working on that. I think we've seen some, I think David will know more, but I think we've seen some hardware acceleration already. Are there any other issues like LTE? Lots of issues still. Lots of issues, but you know, we're working on the mobile connectivity. It's not there yet. Wi-Fi is there. The screen is there. We have seen some hardware acceleration, but we don't know what's going to be in the final, final build. And people will be able to download it and flash it in. Because if it's open source, maybe you can have some help from the open source community to finalize everything, right? Yes, yes. That would be lovely. And I think, you know, once we can release the unit with the kernels and everything else so that people can build things, that would be great. You should send some free devices to the best hackers. I'm joking. Yes, and we've already sent out some boards, you know, some very early boards, but not really proper devices. So really the first proper devices from the production line have come out like literally on Friday. And we have them here because Robin RCO flew in from China Friday night. We picked them up at the airport on Saturday and we're here. Yes, amazing. That's cool. So I guess there have been some sleepless nights in China. And there have been some sleepless nights cold stop in London as well. For the last 10 months. Certainly in the last week, but there's been some other times when there were some sleepless nights too. And this is the biggest consumer electronics conference in the world right here. So there's a good chance that maybe you'll meet some new distributors and they'll be like, hey, okay, we want 10,000 and we want 100,000. I think it's a look at our stand. That's quite a good, if you see, it's quite a crowd building up. So, you know, it's quite a crowd building up. So I think people are excited. I think it's much more exciting than the iPhone X. Yeah, iPhone X is like an iPhone. It's like an iPhone. So this is different.


Hi, I am Dr. Ashwin Raj Gopal. I am the consultant surgical oncologist at Manipal Hospital, Whitefield. All of them consider cancer as a death sentence. But this is not true. Most cancers are cured. But the cure depends on the type of or and cancer and also the stage of cancer. Early stage cancers are absolutely curable. That's the reason screening of any person for cancer is important. At Manipal Hospital, Whitefield, we have multiple types of tests that a patient can undergo such as CT scan, an MRI, a blood test, where cancer screening can be done and they can be detected early. In fact, with better research, we have found that even advanced cancer, that stage 4 cancers can be cured with the help of chemotherapy and surgery.


TEFL London A financial powerhouse, an icon of Western civilization, the backyard of the former British Empire, any way you look at it, London commands attention, and so too will a TEFL course certificate from the birthplace of the English language. On top of this, we provide efficient job support services, so motivated course graduates will find excellent job prospects after they become certified. The course is intensive, but in your free time you can unwind during walks that snake along the banks of the majestic River Thames. You can visit Westminster, Big Ben and watch the changing of the garden front of Buckingham Palace, all in a day. Or spend an afternoon in Hyde Park before snapping a sunset cityscape picture from atop the London Eye. When it comes to entertainment, no city in the UK rivals London in terms of nightlife. Pubs and clubs are everywhere and offer something for everyone's taste. London also boasts the entertainment district of the West End as well as shopping districts such as Oxford Street, Leicester Square, Covent Garden and Piccadilly Circus. Whether you want to explore the city's historical sites or its modern day attractions, London's people and culture will welcome you in and make sure that it is a great choice of destination for earning your TEFL certificate. TEFL Course in London Our centre is located in central London, close to Stepney Green and White Capital train stations. The students you will be teaching are real non-native English speakers, so your teaching practice will truly mimic the really FL classroom, something other course providers don't always offer. Accommodation options vary considerably and the sooner you enroll on a course, the more options that will be available to you. You can choose from a single or shared apartment, a variety of hostels or one of hundreds of hotels that are dotted all over the city. There are many good options located close to the school and London's excellent public transport network makes getting to and from the centre very easy. The course fees listed on our website are inclusive of course related lessons, materials, teaching practice, assessments, certificates, references, lifetime job assistance and more. We have no hidden costs or extra charges so the prices you see on the site are the prices you will pay. Getting started The first step in enrolling on London's TEFL course is completing a free application. If you are at least 18 years of age and speak English fluently, you are eligible to apply for the course. The application is brief and we will send you a prompt reply. Once approved, you will receive additional information about the course content and schedule, your accommodation options, travel arrangements, as well as payment options and more. If you choose our London Centre for your TEFL training it doesn't mean that you have to stay and teach in the UK. If you would like to move on after the course we can help you find a job nearly anywhere in the world. Apply today and you will be on your way to starting a TEFL course in a city where history greets you at every turn.


Hello, and welcome to this presentation about the STM32H7X5 and STM32H7X7 dual-core lines ART or Adaptive Real-Time Accelerator. The ART or Adaptive Real-Time Accelerator block speeds up instruction fetch accesses of the Cortex-M4 core to D1 domain internal memories, Flash-A memory, Flash-B memory, and AXIS-RAM. D1 domain external memories attached via the Quad-SPI controller or QSPI and Flash-Memory controller or FMC. The acceleration is achieved by loading selected code into an embedded cache and making it instantly available to the Cortex-M4 core, thus avoiding latency due to memory weight states. This figure shows the block schematic and the environment of the ART accelerator. Instruction fetch accesses can be qualified as cacheable or non-cacheable. The cache memory is organized in 64 lines of 256 bits each. Each line contains 8 32-bit segments. Each segment can contain one 32-bit or two 16-bit instruction codes. The cache buffer is an extra line of 256 bits, keeping a copy of one of the cache lines. The cache manager checks whether the incoming memory instruction fetch access is cacheable and controls the AHB switch accordingly. For a cacheable access, it allows the instruction fetch from cache in case of a cache hit and it manages the cache memory line refill or instruction code load in case of a cache miss. For non-cacheable memory accesses, the instruction is directly fetched from memory. The cache accelerator features 32-bit AHB slave port to interface with the D2 domain, 32-bit AHB master port for non-cacheable memory accesses, 64-bit AXI master port to load the code from memory to cache, 64 cache lines of 256 bits, fully associative cache, programmable page, and cache content consistency checker. The instruction fetch accesses can be qualified as cacheable or non-cacheable depending on MPU attributes. For cacheable accesses, the instruction fetch follows the cacheable access path. Non-cacheable accesses are directed to the master AHB port following the non-cacheable access path. The appropriate access path is selected with the AHB switch controlled by the cache manager. The cache memory is organized in 64 lines of 256 bits each. Every line contains 8 32-bit segments. Each segment can contain one 32-bit or two 16-bit instruction codes. The cache buffer is an extra line of 256 bits, keeping a copy of one of the cache lines or buffer source line. It allows fetching instruction code by the core while the corresponding buffer source line is in refill progress. The following cases can cause the code in the cache to become inconsistent with the code at the corresponding address of the addressed memory. A write access modifies a piece of data in the cacheable page of the addressed memory. The software modifies the cacheable page index in the art accelerators control register. A data transfer error occurs during the cache buffer and or cache memory line refill. The device incorporates a mechanism preventing software corruption due to the cache in consistency. It detects the above cases and flags all the cache memory lines and the cache buffer as invalid. As a consequence, the next cacheable accesses result in a cache miss and so the cache line refills with new data.


We ended our last session with a discussion on culture, the contextual nature of ethnographic research and what context might mean. As we discussed the context includes many layers, some are observable and some are not. Our objective is to describe all of these layers as the background against which our observations and interpretations take place. This makes ethnography a descriptive method of research. Geert suggests that an ethnographic description ought to bring together the tangible and the intangible aspects of the context and draw connections between the two. He calls this thick description. Thick description refers to a description that includes both observation and analysis. It includes our engagement with the context and the meanings derived from these engagements. It is these meanings that provide depth or thickness to a description. Maybe we can better understand the idea by using an example that Geert's borrowed from the philosopher Gilbert Reil. Reil asks us to consider the example of two boys both rapidly contradicting the lids of one of their eyes like this. While one of the boys is twitching his eye involuntarily, the second one is doing it deliberately. He is trying to make a sign to a friend of his. He is winking. If we focus only on the movement of the eye, we may not be able to differentiate the involuntary twitch from the deliberate wink. Reil explains that the wink is different from the twitch because in winking, the winker is communicating and doing so with some purpose. He is winking to someone in particular, trying to hide the wink from others in the group. The wink is meant to impart a certain message according to a socially established code that is understood in that group. All of these form the under layers of the action of winking. The meaning of a simple action like a wink or a twitch is composed of the action, the immediate context in which the action takes place and the social and cultural context. When we see someone winking, we understand all of this as a single gesture. In constructing a thick description, we try to explore each of the layers that make up the gesture and its meaning. As you might have guessed, an understanding of culture goes hand in hand with creating a thick description. Let us bring in Professor Robina Robinson to deepen our understanding of these two concepts. Professor Robinson is a professor of sociology in the Department of Humanities and Social Sciences in IIT Bombay and one of the advisors of our course. My name is Ruina Robinson and I believe that up till now you have been studying terms like context and web of meanings. Now I am going to talk to you a little bit about that term that we use so much in anthropology which is the term culture. Culture may be quite simply described as patterns of learned behavior shared within a particular social group or community. From the start, therefore, anthropology has based itself on the idea that everyone has culture. Today, anthropologists think of culture as a process that is dynamic and through which meanings are constituted, shared and maybe even contested. Therefore, the question of relationships of power and inequality have become critical to the analysis of culture. Which group has the power to shape the culture values and beliefs of a society? Which group's cultural expressions are marginalized or devalued? Culture is historically constituted, shifting and processual. Culture is also embodied. Where Bordier used the term hexes to think about culture as the way in which we walk, move our hands or our bodies, turn or shake our heads, our posture, our demeanor or accent. If culture is everywhere and belongs to everyone and is in fact in our very bodies, then it is the stuff of everyday life. It is embedded in ordinary social processes. So when anthropologists study culture ethnographically, they do not focus merely on extraordinary or historic events. They are interested in the mundane and the ordinary, the things that most people take for granted. To observe these, the ethnographer needs to live with the people she studies or remain in sustained direct contact and communication with them, to become familiar with them as companions and neighbors so that they may continue with their activities unselfconsciously in front of her. The little things, the minutiae of everyday living is what Malinovsky famously spoke of as the imponderabilia of everyday life. Why does a woman in this society laugh with her hand over her mouth? Why does a young girl sport a ponytail? While an adult woman has to bind her hair and cover her head, why does one social group begin a meal with something bitter and another with something sweet? Why do men's shirts have buttons on the right and women's on the left? Why is the bathing area attached to the kitchen in this region but the toilet far away and at a distance at the back of the house? What are the sounds that one hears from dawn to dusk on an ordinary village day? Does the day begin with temple chimes, the sonorous sound of the azzan or the tinkle of the bells on the fisherman's cycle as she does her rounds of the neighborhood? What smells pervade the houses and fields as one walks the paths from work to home? At midday, does one get the sharp tang of mustard in the air or the full-bloodied waft of coconut or the earthy aroma of makki ki roti? Does one social group eat sitting at a table while another in a circle or linear arrangement on the ground? Why in a community does a woman eat off the same plate left behind by her husband while in another a family eats communally from a thal? It is important to remember that many of these small, taken-for-granted aspects of everyday life will strike the ethnographer more forcefully in the initial period of fieldwork because of their unfamiliarity or strangeness. Time in the field will render them familiar and more innocuous. That is why it is important for the ethnographer to keep a detailed diary of observations from the very beginning of her observations so that she does not lose sight of these aspects which often hold more relevance than she might at first imagine. Attending to these tiny inflections of culture forms the basis for thinking about the ways they interconnect and form patterns. Behavior in one social context has to be observed in relation to norms and behaviors in other contexts in order to attain a fuller picture of the society and culture at hand. This brings us to a more layered and complex understanding of ideas of masculinity and femininity in a culture, of taste and distinction, of purity and pollution, of auspiciousness and inauspiciousness, of honour and shame, of structures and notions of privilege and power, status and class. This is precisely what thick description is meant to convey. The layers of meaning and embeddedness of thick description involves understanding and absorbing the context of a situation, conversation, action or behavior. This felt that what the ethnographer does is to give us her own interpretation of other people's interpretations of what they do or say or think. Thus for us, the readers of ethnographies, to discern for ourselves the correctness or incorrectness, the validity or soundness of the author's interpretations, we must be provided with rich detail of the context which led to those interpretations being constructed. Those thick descriptions seems a vague concept and one that is not easy to pin down. Sometimes it has been defined by contrasting it to its opposite, thin description. Thin description would be merely a collection of superficial information. Even if there is a lot of such information or numerous such facts which are put together, if the description does not convey to the reader a vivid sense of the encounter or situation and does not analyze its meaning for the social actors involved, it is thin description. A description is also thin if the account is not embedded in its historical and social context and if we are not able to perceive who the people involved are and what their relationships with each other are, their intentions and the surrounding circumstances of what they say and of their behavior or actions. As you can see, describing what is thin description gives us a feel for what thick description might be and vice versa. Firstly, what is clear is that the word description in thick description is inadequate. Thick description is not merely description, it is also interpretation. Secondly, thick description is not merely about facts and information. It is about very similitude or authenticity. This authenticity is intellectual so that we can appreciate the interpretations of the author. It is like cooking. We don't just eat the dish and try to imagine how it might be made. We don't just read the recipe which would be like a thin description of the act of cooking. We are in the kitchen itself and we see the cook and what ingredients are put together, the events or the persons involved, perhaps one can say, and why some of them are more important than others, in what quantities they come to be mixed. We get the aromas of the dish that arise as each ingredient is added and mingles with the others. We enter into the assembling of meaning by the author. The authenticity is also emotional. Thick description should enable us to feel, as in a theatre, that we are there as events are unfolding. We can enter into the social actors' sentiments and motives, hear their voices and see their movements, behaviour and relationships with each other. We know what they wear and where they are. We become aware of who is present and who is not. This is not a surface account of what is happening. It goes beyond the present. It locates incidents, information and situations in terms of past events and the intersecting biographies of individual actors. This embedding of events and experiences in their social and historical contexts enables us to comprehend why a particular situation or a series of incidents is significant in the social and cultural life of the people and in what way. It has been argued by the sociologist Norman Denzen that for a thick description to be thorough, it needs to capture all of five aspects, the biographical, the historical, the situational, the relational and the interactional. Let us examine how these elements are brought out in the following example. This is an incident from 1934 described by Dr. B. R. Ambedkar regarding his visit to Dholatabad Fort in waiting for a visa. Our tour program had not been announced and quite deliberately. We wanted to travel incognito in order to avoid difficulties which an untouchable tourist has to face in outlying parts of the country. We had informed only our people at those centres at which we had decided to halt. Accordingly, although on the way we passed many villages in the Nizam state, none of our people had come to meet us. It was naturally different at Dholatabad. There our people had been informed that we were coming. They were waiting for us and had gathered at the entrance of the town. They asked us to get down and have tea and refreshments first, and then go to see the fort. We did not agree to their proposal. We wanted tea very badly, but we wanted sufficient time to see the fort before it was dusk. We therefore left for the fort and told our people that we would take tea on our return. Accordingly, we told our drivers to move on and within a few minutes we were at the gate of the fort. The month was Ramjan, the month of fast for the Mohammedans. Just outside the gate of the fort, there is a small tank of water, full to the brim. There is all around a wide stone pavement. Our faces, bodies and clothes were full of dust gathered in the course of our journey. And we all wished to have a wash. Without much thought, some members of the party washed their faces and their legs on the pavement with the water from the tank. After these ablutions, we went to the gate of the fort. There were armed soldiers inside. They opened the big gates and admitted us into the archway. We had just commenced asking the guard the procedure for obtaining permission to go into the fort. In the meantime, an old Mohammedan with a white flowing beard was coming from behind shouting. The deads, meaning untouchables, have polluted the tank. Soon all the young and old Mohammedans who were near about joined him and all started abusing us. The deads have become arrogant. The deads have forgotten their religion, that is, to remain low and degraded. The deads must be taught a lesson. They assumed a most menacing mood. We told them that we were outsiders and did not know the local customs.  Why did you not tell these outsiders that this tank could not be used by untouchables? Because the question they kept on asking them, poor people, they were not there when we entered the tank area. It was really our mistake because we acted without inquiry. The local untouchables protested that it was not their fault, but the Mohammedans were not prepared to listen to my explanation. They kept on abusing them and us. The abuse was so vulgar that it exasperated us. There could easily have been a riot and possibly murders. We had, however, to restrain ourselves. We did not want to be involved in a criminal case, which would bring our tour to an abrupt end. One young Muslim in the crowd kept on saying that everyone must conform to his religion, meaning thereby that the untouchables must not take water from a public tank. I had grown quite impatient and asked him in a somewhat angry tone. Is that what your religion teaches? Would you prevent an untouchable from taking water from this tank if he became a Mohammedan? These straight questions seemed to have some effect on the Mohammedans. They gave no answer and stood silent. Turning to the guard, I said, again in an angry tone, can we get into the fort or not? If we can't, we don't want to stop. The guard asked for my name.  He took it to the superintendent inside and came out. We were told that we could go into the fort, but we could not touch water anywhere in the fort. And an armed soldier was ordered to go with us to see that we did not transgress the order. This example brings out all the five aspects that Denzin was speaking about. This is eminently biographical as well as historical. It tells us about the experiences of Ambedkar as he travelled in India as part of his movement against untouchability and his political activities during the period of the freedom struggle. It lays bare the situation of intense humiliation he and his party faced when they used the public tank after the dust and stress of their travel and how the touch of the dheed was perceived as polluting even for the Muslims. It captures, for instance, the interactions between Ambedkar's party and the old Mohammedan, the young Muslim and even the guard and the emotions and internal turmoil wrought by these encounters. The relational aspects of untouchability are grippingly evoked by the narrative. For those of you who would like to read a very engaging example of thick description in ethnography, refer to an article by Clifford Geertz. The article is called Deep Play Notes on a Balinese Cockfight. It is a rich and very enjoyable description of a cockfight in Bali in Indonesia. And there is a quiz that you can take to test your understanding of the text. Let us get back now to our discussion of the fundamental concepts of ethnography. Our research is not a presentation of facts. It brings together multiple points of use, each of which might have their own perspective and interpretation of a phenomena. Thus, ethnography is interpretive in nature. As we engage in fieldwork, we select what to observe and record. Some of this selection may be conscious and some not. We may pay more attention to some events than to others or give more weightage to the perspectives of certain participants over others. This makes ethnography a subjective form of research. And this raises an important question for us. If ethnography is simply a subjective interpretation of a phenomena, can it be called research at all? Let us pause the lecture and ponder this question. Is it possible in ethnographic research to have knowledge that is objective in nature? Think about this and write down your responses. Some of you may have said that objectivity is an essential characteristic of research. Others may disagree with this. It is an interesting question to consider and to be frank, not a simple one. In order to deliberate this question, we need to dig deeper into the meaning of subjectivity with regards to ethnographic research. What or rather whose subjectivity defines the research, whose perspective is represented in the ethnographic knowledge we construct. Our research is not simply a presentation of our subjective interpretations. And ethnography is a play of multiple subjectivities. Our task is to bring together these varying and sometimes contrasting perspectives. We try to make sense of them by interpreting them, exploring the meanings they convey and weaving these into a cohesive narrative. As Geertz has said, that what we call our data are really our constructions of other people's constructions of what they and their compatriots are up to. To use a metaphor, ethnographic knowledge is not a monolith that we come across while wandering around our chosen context, which we can pick up and take back as our finding. It is instead like a patchwork quilt made of several small pieces, each piece representing a different perspective. The ethnographer puts these together to construct a cohesive and complex narrative of the phenomena. In that sense, the knowledge we construct through ethnography is the handy work of the ethnographer. And so it is subjective and interpretive. For this reason, we must be conscious of the role that our subjectivity plays in the research. This is what ethnographers often refer to as self-reflexivity. It is the practice of reflecting and being aware of our biases and letting this awareness filter into our research practice. It involves actively reflecting on our ideas and preconceived notions. Among the things we recognize is that the context changes when we are present in it. Basically, when we enter the room, the dynamics have changed. It is just not possible to be a fly on the wall. Having this understanding to our practice can help us produce research that is more cognizant of the multiple subjectivities that form the context.


Okay, I guess Thanks for everyone for being here. My name is Jennifer Lynn I lead the product management for the contrail team at juniper and this is our sponsor session So what I'm gonna do in this is essentially I'll give a little bit of what we're seeing in the in the overall marketplace and talk specifically about open contrail Which as many of you know is an open-source project That we started when we actually gade contrail into the open-source community Give a little bit of an update kind of what's going on there. We've made some Enhancements that I'd like to make sure I review with the team here And also talk about a little bit about the market more broadly I was in Dusseldorf Germany two weeks ago at the SDN NFE World Congress And that's obviously a very different forum than this group here but a lot of the discussions and a lot of the learnings and a lot of the You know questions that are coming up I wanted to make sure that we leave time at the end and just get a little bit of feedback from from the folks here as well So for those that don't know I think there's been a lot of talk about well You know what what problem are we solving and a lot of these things for for us in the contrail team? Haven't really changed but obviously there is a lot of change going on not just in the networking industry But in the IT industry more broadly so this discussion about old IT and new IT I think is very relevant from a network perspective moving from this model of device level configuration to system level Automation is a fairly large change We've seen controller-based architectures before but I was just in the panel around Neutron and I think the question about overlays is not really a question anymore I think people are embracing overlays But there are still some gaps between what an overlay can do and what it needs to do as part of a broader network system One of the questions that came up in that panel is I don't want something that's specific to a data center implementation I want this to work on a global basis, but I need to be able to localize the policies I need to be able to localize the identity stores I need to be able that's the exact balance that we want to kind of Talk about here with how do we build a hierarchical architecture that enables distributed applications to kind of do a lot of this automation that we're doing here The other you know major change for for the networking industry is suddenly everybody's embracing open source technologies Obviously when when open stacks started and it continues to be one of the largest open source projects in the industry But for the networking industry overall open source was not necessarily Mainstay, I think you know a lot of the open initiatives whether it's open daylight I'm on the board of open daylight for Juniper OPN of fee which Juniper is also a founding member and a platinum sponsor You know obviously open stack a lot of the standards based initiatives in the past were an open industry dialogue But it's obviously a very different landscape. How do we get to this model of exposing vendor agnostic? API's to enable an ecosystem to play together. That's fairly different for the networking industry From a contra perspective we serve three very distinct segments And I think the sort of the deployment cycles the adoption cycles are actually quite distinct So we make a big difference between but the types of customers that are Somewhat Greenfield, maybe some of the SaaS providers who are building their own applications And they have a little bit more flexibility in terms of the application environment for many of the traditional enterprise Their version of a virtual private cloud is really to enable IT as a service even at Juniper We're building our core services on an open stack cloud. We do our development on our own technology It allows the developers to move with more agility I think open source is one key piece of that and it was something that you know our development team Really wanted to do to kind of keep the pace But it's also the transparency and the engagement with the broader community and as it grows We're seeing that as a real proof point for open-con trail as well But that is also once again an operational change for a lot of the the segments that you see here And then finally the carrier space Obviously, that's a good chunk of Juniper's core business as this discussion about hybrid cloud and you know cloud migration And you know, how do we federate these environments a lot of even these non-carrier segments come to us and say Well, you guys understand the carrier space as the enterprise tries to do IT as a service and the big banks Tell us this a lot. They really need to think like carriers. They need to support things like multi-tenancy They need to essentially build back different business units based on usage which the cloud providers are doing as well But this is sort of a new concept So as I team moves from a cost center to carrying a P&L and charging back each of the development teams or each of the business it's a pretty big business model change and Obviously the cloud providers many in the cloud industry will say cloud is more of a business model than it is a technology There are some very distinct things in terms of the level of user empowerment the ability to go to a self-service portal and get Resources on demand that is, you know without filing a trouble ticket. That is a very big change One of the things that I think is a key tenant from a contra perspective is not to reinvent the wheel in terms of how Networks are done and this this slide obviously is a fairly high-level slide But this notion of number one workload mobility whether it's within clusters or across data centers or across different types of cloud environments This was a design principle from day one and a lot of the thinking around the standards work that went into contrail with L3vpn N systems was to essentially not break what's already working So L3vpns and BGP peering has been in large-scale networks for some time If you look at what folks like Google Compute Engine are doing the reason that they can spin up 200 instances in less than 30 seconds is because they've distributed a lot of the technology now Obviously they're running 300,000 servers per data center and their and their applications are maybe somewhat more monolithic and Greenfield than some of the large enterprises some of the large banks who have mainframes still in their infrastructure However that simplicity and that level of automation is something that we're taking a page out of the book at the same time from the large-scale Carriers as well as the largest of the cloud builders and we believe that there's very few Architectures that are kind of finding that balance between how the emerging cloud builders are doing it to keep the agility and Support new applications and things like Docker containers from the beginning But also in a way that day one ties into the existing physical networks So we can peer directly in a in a VPN directly with the existing layer three gateway that's already there Whether it's a Juniper MX or Cisco ASR, you know 9k or someone else's router. I think When we started this journey with with contrail from the beginning We saw OpenStack as the project in the industry that had the most momentum. It was still obviously fairly early on in the days of OpenStack and Neutron or quantum at the time was not the central discussion Now I think what you're seeing and a lot of the buffs and discussions around neutron is that the networking model Needs to get to the point for these large-scale systems And the networking discussions are actually quite different than they were in the early days of quantum We're not talking about L2 adjacency as the answer anymore. We're talking about how do we do distributed routing? How do we do multiple service chaining? How do we do? You know very distributed policy enforcement for very dynamic policies that can't be loaded statically up front Now the networking problems obviously are one piece But the system level sort of challenge with a software stack is something that I think you know OpenStack has done a very good job for many of our more network centric type customers They've asked us to play a bigger role in looking at the system overall the components of the stack The architecture around it the best practices etc, and I'll talk a little bit more about that But in the middle yes, there's this notion of not just the neutron component But the entire software stack as a binary that gets loaded in at the end here A lot of the best practices in terms of how do you actually rack and stack this? How do you deploy it in what order do you do upgrades? How do you troubleshoot the physical and virtual network? There's a lot of questions still in the networking industry as this transition happens and once again You know when Juniper acquired contrail in December of 2012 I think the benefit that we had as Juniper was that we had a fairly software centric mindset with Junos We had a real-time kernel. We had a modular operating system. We had a Very good cadence in terms of new software delivery and the quality of the code and that's allowed us to essentially take You know the best of what we can do as a broader company while not tying in any hard way to Junos Loosely coupling but at the system level we can show a lot of the benefits now the reality in a lot of our Contrail deployments today is that we've deployed in production in completely mixed vendor environments both from a switching perspective from a routing Perspective and from a services appliance perspective The architecture was defined that way and this is more than three years ago that one of our contrail co-founders Pedro Marx first defined in the Co-authored in the IETF the L3 VPN and systems draft with AT&T Verizon and other large players And the problem that they were trying to solve was to define a vendor agnostic Architecture and software that would solve the issues in a virtualized data center around Multitenancy access control and workload mobility Now a lot of the paradigms that you'll see in the data models that we use it Come from a mobility mindset and in this case we're not talking about wireless dot 1x clients We're talking about virtual machines that may move from one cluster to another or across clouds But IP has solved that problem and we take forward a lot of those learnings in in the contrail architecture At the beginning when we showed this slide it was really to reinforce the fact that we Have abstracted at various layers and we could support any hypervisor. We could run it on any x86 Linux environment we could support any encapsulation now I think what I wanted to update folks here with is that we have implemented on various hypervisor We started with KVM. We've done Zen with other sort of stacks We've implemented ESXi with the VRouter implementation now And we've also done a lot with bare metal and Linux container environments without a hypervisor Because as many of you know the Googles and the Facebooks of the world don't use hypervisors So we're serving a lot of these web-centric type customers who essentially are not solving the same IT problem That many of the traditional enterprise were and they found a way to solve the segmentation problem and still get the effect of pooled resources across compute and storage without the hypervisor That's why so much attention around Docker Once again, I think there's a lot of fun out there that we only work with sort of a juniper hardware and software infrastructure As I mentioned a lot of our early deployments kind of prove from the customer perspective This absolutely works. We've even started sharing some of the kids configs for non juniper gear in terms of the best practices Both on the layer three gateway side as well as the switching architectures I think the other piece is that from the beginning a lot of the intellectual property was around in order to enable System-level automation the control plane needed to be well-defined and in the early days of SDN There was probably a disproportion amount of discussion around what is the encapsulation? Today we support many different types. We started with GRE Because that's pervasively supported today. We will support, you know, the tunnel fabric over UDP We will support VX LAN. We see sort of a roadmap as this evolves Obviously, there are some that are looking at MPLS over MPLS The piece that of MPLS obviously that we retain is the 20-bit label to identify the virtual network And obviously as we've seen and I think there was a recent SDN blog by one of the quote founders of SDN Scott Schenker where he also reinforced that SDN2 should not reinvent the goodness of What we've learned to do with things like MPLS But we have to solve the new problem We have to do it in a way that we can drive rapid adoption without waiting another three years for protocols to be pervasive in the network The segmentation problem I think in the in the Contral architecture The concept of VLANs goes away and the segmentation is this notion of virtual networks But used to be maybe somewhat expensive when tied to physical hardware and a software architecture actually quite Unlimited so you can define a virtual network in a way that's relevant from an application and user context perspective and make that the model of Segmentation you can have any you know many different slices of virtual networks and enforce policies based on those abstractions And as I mentioned we had co-authored the group-based policy blueprint within OpenStack Probably over a year and a half ago Really trying to balance this how do we address some of the you know host-level enforcement issues but Simplify a lot of the policy administration so that it's logically centralized, but Distributed enforcement That also means that from a security perspective you hear a lot about Microsegmentation and the ability to do is distributed firewall in the Linux kernel We already support those models from the beginning of tenant isolation You know down to the Linux kernel with the v-router and it's not it's it's partially from a Application optimization perspective with things like localized QoS. It's from the other side A very good way of doing distributed security enforcement whether it's blocking certain types of traffic You know inspecting before Before allowing etc I think the other thing that has made it possible to move into deployments quickly is that we keep the Expectations of the physical switching infrastructure Relatively straightforward like the large cloud players We expect any to any IP connectivity in a in a IP fabric Obviously not everybody has built a class fabric Google style data center And as we make that transition with many of our let's say enterprise customers Obviously, we can support the Contra architecture, but many of them are moving to that type of ECMP cloth style fabric Because now with the web loads You're not keeping 80% of the traffic within a VLAN anymore if you look at Amazon and Google and the patterns of their traffic Even, you know Hadoop clusters. We're now obviously in a very distributed model and they're constantly You know moving east-west traffic So if you look at a lot of the video analytics companies the gaming companies, they're really excited about this notion of running Essentially a localized routing table so they can do a local lookup and move from one host to another without some central bottleneck That's also been a lot of the issue with You know some of the alternative solutions where they have software gateways, which not only add cost and complexity But also are putting an extra bottleneck in the network infrastructure So with obviously an optimized layered three type fabric. We're trying to reduce the number of hops So that these real-time applications can take advantage of an efficient network. I Mention kind of the reference architecture approach a lot of that has to do in with not just the technology itself a lot of the challenges of OpenStack even are In the provisioning in the troubleshooting in the correlation between the physical side and the virtual side Understanding is an an application problem. Is it a network problem? Is it a storage problem? Etc. So the goodness of OpenStack in converging the IT systems is one piece We were hearing again and again that the network guys are losing visibility. They can't ping a VM They can't do a trace route. They can't do a packet capture They can't essentially understand aggregate throughput and flows for virtual machines within a virtual network That's the type of thing that I think You know we've we really focused on with the analytics with the troubleshooting with the reference architectures, etc And we work with obviously many different partners in this journey The the fact that we've open sourced our code. We've made our you know bug tracking Fully available to our partners. We've put all of our test scripts and our documentation out there has helped us essentially Not only engage our customers, but also just as importantly engage some of our technology ecosystem partners and the rate at which We're moving with these releases Probably every six to eight weeks is definitely an agile software development cycle if you look at a lot of the you know Empowerment of the user concept that was a big thread in mobility the cloud user is king He he or she gets to do what they want when they want from a self-service portal and it's served up immediately At the same time the folks that are essentially going to be let's say the tenants of a virtual private cloud Are the folks that are developing applications and maybe network services for NFV And they want to be able to access the infrastructure and go live without a lot of Overhead in terms of IT and administration So this next role of the cloud administrator is really important in terms of upfront setting what those policies are We worked with one major you know sass provider who from the beginning of the engagement gave us about 40 application and user Templates that needed to be enforced in the overlay and with the physical network Those included network and security policies things like load balancing policies You know they have a three-tier web application type architecture You know the back-end database should not be talking directly to port 80 traffic if you see that block it all port 80 Traffic should go through the web server tier those types of high-level rules can be enforced or defined up front And then enforced at the time of the transaction. I Think you know we are obviously a software team of with deep networking knowledge And so understanding this broader problem and then bringing back to empower the network guy to do the troubleshooting Understand what's going on in the physical and virtual network? I'll talk through some of the demos one of the things that we're showing here is Essentially, how do you do correlation? Across the physical and virtual topologies. How do you do topology discovery with LLDP so that if something goes wrong You can quickly identify which flows with which VMs to which port in the switch, etc And that's not obviously that's a vendor agnostic problem Some of the key capabilities from a contra perspective It's not that these services are new services the way that they're being applied is quite new You know we do IPAM DNS and DHCP and the V router if a customer has obviously that in an existing They can apply it but in many cases localizing some of these capabilities is much more efficient and much more scalable And allows more portability as well initially and there was there's still ongoing discussion about You know in a host level Linux kernel How much routing and switching we need to be doing I think what we can say is that we see more and more of these real-time emerging Applications the level of native layer three capabilities that is going into the host is increasing You know we have a local video analytics company in Mountain View, California that was recently acquired They're running essentially BGP in every host and they did that essentially for video latency reasons And then they had a fairly large issue in terms of how to efficiently distribute the routes and avoid full route prefix Population down in the host level. I think we've balanced that we only populate essentially the route prefixes in the V router for the relevant in the locally relevant workloads and That's obviously using a page out of the book of MPLS VPNs once again a lot of the problem that folks were trying to solve was to Federate, you know many different subnetworks with a common architecture and now we're seeing that a lot in cloud You know Amazon's not going away open-stack private clouds are not going away. This needs to work over a common network infrastructure We also focus a lot on things like service chaining of the network Control plane that we use obviously is very consistent. So when we insert either a physical or a virtual Service we essentially next hop route to it And that allows us to be extremely flexible in the types of services that we can insert But it also allows us to define a policy once and then just change the configuration model as new Services are inserted and as open-stack continues to evolve with things like load balancing as a service and those API's Get get tighter in terms of definition obviously will will support more of those today We're already supporting things like LBAS API's for HAProxy We're working obviously on things like physical f5s as well as virtual f5s. There's some of those demos being shown A lot of the definite definition comes with the understanding of how this architecture was done in a you know The balance between what's distributed and what's centralized and how we build a sort of scale-out infrastructure There is no upper bound So, you know some of the sort of scaling demos that we're showing in the broader Discussions around neutron there was some discussion about the fact that once you get to 200 nodes the network conks out Well, you know in a contrail infrastructure I think some of the demos were showing you know a thousand v routers for a thousand nodes and still not hitting any type of scaling limitation The other piece and this is something that we've learned, you know with routing large routing systems Which is probably the largest distributed system that's out there Is that you can't have a single point of failure and when you lose any single node? You can't interrupt the traffic So we've worked a lot over the last few you know few months in a lot of different bake-offs in a lot of different countries on HA and how that works both from an open-stack perspective as well as from a contrail architecture perspective. I Just talked to you know another network provider They're getting way behind open contrail relative to some of the other SDN solutions because day one no matter whose network it is We can interoperate so that's always nice to see I mean we compete in a way But the network's job is to interconnect so when you have another networking company who may or may not have had success in Building an SDN controller come and say well We're gonna get behind this because we just need something that works and we need something that works with our stuff So I mentioned the enterprise problem, and it is a little bit different You know if you if you think of the web guys they have obviously a class data center today But they don't have a lot of legacy mainframes. They don't have a lot of layer-to-storage keep-a-lives A lot of that is a networking challenge as well And I think we learned some time ago in IP networks You know when you have s&a and token ring and Apple Talk and decknet we're not saying rip it out What we're saying is federate those environments. That's why the lair three gateways are still obviously extremely important We can do enforcement at the first hop or we can do enforcement If it is a native environment where we have the Linux kernel as of the router already But that is again a way of using the hierarchical architecture to address these different workload environments I think OpenStack is becoming a de facto framework at least for how people are thinking about heterogeneous system orchestration and so obviously we don't just support sort of OpenStack, but We're using that as a very good proxy on how do we essentially Federate these environments from a network perspective, but also anticipate You know the application changes that are going on where more and more of this will be automated You know one of the specific things that our carrier customers are very interested is Is around network function virtualization and we've been involved in a lot of bake-offs around that I presented another session two days ago here at the OpenStack summit with one of our partners who has built a composite virtual network function for the 4g packet core and they had to rewrite some aspects of that application because You know, it's not enough to take a application and put it in a virtual machine and ship it as a virtual appliance a lot of the legacy Applications can't take advantage of a scale-out model And so there's no reason to rip them out and try and put them into a cloud if the application obviously doesn't take advantage of an elastic architecture But many of those services do and as we work with not only our for instance our own firewall service We have a scale-out caching service, you know, we work with partners around load balancing etc That model starts to look very consistent You know this model of creating a service template Defining that once and then just instantiated instantiating it as new workloads come up Allows us to essentially balance that, you know definition with the policy application The other thing that I mentioned we've been really working on is sort of this physical to virtual interconnect and the bare metal question Was one, you know, initially a lot of the use cases were around virtual machines now increasingly they're around Supporting either bare metal servers directly or docker containers without a hypervisor I can't tell you how many for instance financial services type questions come up And they say well we were moving from the proprietary hypervisor to the open-source hypervisor and everything was going really well Now we may just you know be lined straight to a docker environment container environment because our Application teams are telling us that they need a docker enabled cloud within four months a lot of the deployments that we've done kind of We we got in fairly late in the game got through sort of a bake-off And when there's a real problem, I think what many of our customers have found is that you know We can sort of meet the scaling and availability Expectations but address this new problem and the way that we address things like docker containers is exactly the way We do the segmentation and policy enforcement for virtual machines, but now instead of a tap interface We're essentially using Linux namespaces and you know Linux containers So there's many ways we can have a v-router sitting on the bare metal server as a Linux kernel module we can also Increasingly use the top of rack switch as a gateway You know we're showing another demo where we're supporting OBS DB to essentially bridge a bare metal segment into the top of rack switch Not just our top of rack switch, but preferably ours And and then once again without without sort of extending all the way down to the host we can essentially You know map it to a virtual network and enforce a policy So the physical reality as you have lots of Virtual machines in an unpredictable location or Linux containers Maybe a hundred Linux containers per host They can be in any any server in any rack in any cluster in any data center This architecture will still hold up the broader problem as this sort of evolves is Essentially, how do we also now apply some of the services? That the network administrators the security administrators need for compliance purposes or whatever it is The way that we do that as I mentioned is is through next hop routing So we have a lot of flexibility in terms of how we insert a service We create we steer the traffic to that next hop apply the service You know traffic needs to go from virtual network red the virtual network green But through policy It's in force that it first has to go through a firewall service and a load balancing service And when you change change that firewall service from one vendor to another the policy doesn't change But obviously the service template may change with the new configuration parameters as Firewall as a service API's get better than obviously there's a common way to push the configuration down today We found a lot of success with the service orchestration and the service template model in how people are defining that that service chaining in their data center and part of this transition so one of the You know SAS providers that we're working with was essentially using you know a Layer to tromboning to a physical f5 load balancer as they evolve their architecture They're moving to a more native layer 3 architecture will they'll have more distributed load balancing services inserted and and very often That's incremental. It's not as a replacement. We have one large financial services customer that has about 3000 security virtual instances In their implementation and that doesn't displace the firewalls the pair of firewalls that sit at the D mark between the WAN and the data center They're putting firewalls between tenant groups Well, I have a snapshot here for instance We we're just showing that you know what we're scaling to a thousand nodes and beyond with this architecture just to show We don't see this as sort of we wish we could it's it's something that we are actually have you know working today as customers scale Obviously a lot of discussion about should we cap it at 200 nodes and just put you know new controllers for each set of a Couple hundred nodes. We don't obviously believe that's the right thing from a cost and efficiency perspective So we're doing a lot of bake-offs now I think we would ask that a lot of our customers and partners hold us to you know the data and data driven decisions There's been a lot of emotion and a lot of lobbying in In the open efforts and so now we're starting to see a lot of the data And actually some of our customers are sharing the the test scripts The test plans that they've done so that there can be sort of best practices on you know What are we actually testing for what do we need to sort of improve the model in the architectures? The other thing that I mentioned the ability to do sort of physical topology discovery And then essentially map flows a drill down into Specific ports into specific virtual machines aggregate that back up This is all you know from the very beginning as we moved into an operational environment You know many of our customers were asking us for more guidance on not just obviously the overlay piece But the interaction with the physical underlay In terms of the docker, this is something we started with a blog We put more information now in terms of open-contrail and the types of requirements that we're seeing there The docker guys endorsed us at the last open-stack summit They like the way that you know that the the networking is simplified but also highly distributed You know, I think this is something that if you're looking at contrail encourage you to take a look at we've shared a lot of the Configurations we have some videos out there now Obviously a lot of excitement around docker Thanks to our marketing team There's also a host of new demos that are being put out there Which are just a couple of minutes to kind of show the capabilities that we've added and some of the services partners and how they're used in in in our demos and Some of those are posted on YouTube others You'll see show up through open-contrail. We're trying to color that too with you know blogs by the users So many of our customers and partners have already blogged about you know Not only the good experiences that they have had but the gaps that they'd like to see us to address This afternoon we have our open-contrail advisory board meeting with many of the folks here at the summit and you know That discussion is both from a business side as well as a technology side Aspects we're looking for active feedback around community governance around roadmap around lessons learned We've opened up some of the community support to folks that have already deployed What we're finding is that while the code is the same between open-contrail and juniper contrail Obviously the support model is is what we monetize from a juniper perspective But a lot of our customers start with open-contrail and they like the fact that it's an open transparent model They obviously want to interact with us commercially as juniper because they're looking to scale and they want to make sure that it's Sported there's a picture of our booth. We've had a lot of traffic through there And we it got particularly busy when we hosted the the beer bash This is just a snapshot of some of the partners that we've been working with and what we found is that both from a systems integration Perspective as well as from a layer four through seven virtual services perspective It's been fairly easy for folks to kind of interact with the contrail architecture But I think we have more work to do in terms of how we're documenting How we're testing and all of that This also just recaps. I mean it's been you know about two years now Things have moved very quickly. We gaid contrail in December of 2012 Actually September of 2012 as open-source and you're starting to see some SDN players open-sourcing now and one of the you know key questions that we asked ourselves when we Started open-contrail is you know if you don't do it when you start It's very hard to do it successfully after the fact now that everybody has validated the model of open-source I think we will see more SDN players open-sourcing But if you look at you know the way our development team uses the open-source model for their own agility It's it's very hard to do it after the fact So it kind of comes across as desperation when you do it too late in the game But for us it's obviously become not only an internal differentiator in terms of you know how quickly we're moving with new releases But also it's allowed some of our partners and customers to already contribute code back You know we had a case study with CloudWatt who's already in production They've contributed quite a bit in terms of you know how they're doing load balancing how they're doing packaging how they're doing the SSL Implementation etc, but also just participating more broadly in meet-ups and that kind of thing So that the base infrastructure was the first thing in terms of implementing the layer 3 VPN and systems architecture What we added we submitted the AWS VPC API blueprint into open stack You know today, that's obviously Still a question in terms of the extent to which open stack Embraces other cloud environments from a network perspective. We have to embrace that model So the notion there was to essentially take the same virtual private cloud APIs as One has in the in the Amazon cloud Run them in a private cloud in terms of open stack and not change the scripts Whether it's that way or through heat templates and you know Other models I think that networking problem is definitely one that we want to differentiate ourselves with I Think the other thing is that a lot of our customers are testing the contra limping implementation Against the neutron v2 APIs. So, you know, many of our customers have said, you know a baseline requirement is that you know, we stress the neutron v2 APIs as part of our benchmark not just for functionality and Implementation of the APIs, but also, you know, how are you doing API versioning? How are you doing release management against those those API so we can keep the architecture loosely coupled? but that was also a Key issue or a key debate topic in the last panel, you know The last open stack summit a lot of folks were talking about the challenges with the default neutron Implementation to the point that folks were questioning neutron if we start to make data driven decisions and don't necessarily Take certain things for granted. I think it doesn't make sense to say we should do away with neutron It makes sense to fix the issues You know the the last or the first part of this year We were upstreamed officially with open stack Juno We kicked off the open contrail advisory board with some of our key customers like NTT and AT&T and Symantec and workday and that list is still growing. We're seeing a lot of active involvement In that environment and then the contrail reference architecture as I mentioned, we're not just sort of looking at the Networking piece, but the networking piece in context of the broader architecture as well as how does this work with distributed storage? We're assuming that not everybody is putting large EMC arrays into their into their clouds, etc But we have to balance all of that. I mentioned the scaling the HA testing the correlation between physical and virtual A lot of those things are sort of ongoing The native IPv6 implementation with the overlay was definitely a goal for us in calendar year 2014 that we hit I think there was another session actually two sessions on folks that actually took it upon themselves to do an open source project Around a distributed sort of V router and I think there is sort of convergence We like seeing those types of things and and other communities and we can kind of divide and conquer with folks that have kind of You know tackled parts of that problem already Okay, so I think I've left a little bit of time for any questions or comments Open it up Anything that you didn't hear about that you wanted us to address is as sponsors this time. Yeah, please just wondering How you guys actually cooperating with the other? Irrelevant project like for each of our Congress or even Newton is it's kind of separate Approachy you guys trying to pursuing now or you guys really try to cooperate with the other Related actually well, I think they're quite different so neutron We actually have a core contributor in the contrail team for neutron We we are now a you know Sort of an official upstream neutron plug-in with the contrail piece So we're obviously very invested in neutron our core contributions have been in neutron as far as Congress goes you know this notion of Audit and compliance is actually something that we also take very seriously And you know as that evolves I think will will probably be more active specifically in Congress But the group-based policy blueprint that was three summits ago We actually co-authored so in terms of how we think about the interplay between policy You know definition in a way that's you know, not so granular but abstracted up to a group Or a virtual network as we think of it Is is definitely not a new concept so that discussion has been going we're working with some of our you know Key customers because especially like in the financial services industry We had a very large financial services customer advisory board meeting in New York with 18 of the major banks And the thing that they said to us from a IT perspective is we're sort of in the business of risk management So we need an SDN type efficiency model and automation, but you can't make any compromises So if you tell me that it's not compliant if I lose my you know socks compliance or if I'm a retailer and I lose my You know PCI compliance I'm not going to even start right now Open stack has this broader issue and you've probably seen some of the security breakout teams talking about how do we do open stack compliance? We'd like to take a native you know an active role in that a lot of our security team Has been working closely with some of our contrail customers to define the cloud security audit and how we implement that with Contrail and you know with the broader network teams Yeah, good. Well, yeah, we compete directly with NSX. However, what I'm talking about here is the hypervisor support with ESXi and What many of our customers have said is as they move from a VMware environment to an open stack cloud They want to make sure that they don't have to recertify workloads So especially in the government industry you see that they've certified it for an ESXi hypervisor They want to move that virtualized workload over to an open stack cloud We support that today and you know the The other aspect of it is the vCenter APIs, which we're also I think demoing out in the booth You know the vCenter APIs have evolved quite a bit from you know the early days I think you see VMware sort of embracing open stack. So as that evolves That's you know getting easier to support as well But I think it is really about the mindset so many of the customers who have VMware workloads today They run quite well in VMware today They don't necessarily need to rip those out and move them into an open stack environment We're there where we're seeing folks building the open stack cloud environment is where they need that cloud And they can basically you know have a you know the new clusters come up in a native open stack environment And from a network perspective we can federate that to the you know VMware environment quite well If a customer wants to swing those workloads over we're supporting that as well Okay, any other questions? Yes So I showed one slide and that's actually you know of the differentiation Those are the key ones, you know in terms of scaling in terms of service chaining in terms of open standards based Implementation that works without extra gateways In terms of the the flexibility to pull in new services and not do a development program around integration of each service In terms of being you know vendor agnostic in terms of cost In terms of agility, you know, we're hearing a lot about the and I you know, we really like the NYSERA guys They obviously you know kicked off the whole quantum discussion within open stack VMware paid one point two billion dollars for NYSERA specifically to kind of change the discussion and networking and It definitely I mean we we all as a community networking discussions have definitely changed You know, but I think what we're seeing from a you know Competition point of view Some of our customers are sharing their results and what we just you know as that sort of matures in terms of data plane scaling You know control plane scaling ability to do HA ability to insert services cost You know complexity network troubleshooting These kind of things. I think that will get clearer over time All right. Yeah. Thanks again for joining. I'm glad you found the room