One, two, one, two. Vice Chancellor for Academic Programs, Steve Worshaw, President of the Student Government, Avi Kolkha, President of Student Senate, Daniel Wren, Former NCSSM Chancellor Jerry Borman and John Frederick, Chair NCSSM Board of Trustees Henry Quo, Class of 1982, Vice Chair Board of Trustees Brian Bailey, Class of 1984, Board of Trustees members LaVonia Allison, Steve Griffin, Tom Foundation Board Member Brad Ives, Class of 1982. To convocation this evening. Convocation begins the signal for the start of the school year. I hope each of you has had a great first day of classes. I believe this is going to be an outstanding 2014-15 school year. I again want to take an opportunity to thank all of our distinguished guests here this evening. And it's wonderful to have so many of Rebecca's family and friends here to speak. We're really happy that you're here. And also want to again thank our Emeritus Member of the Hackman who are here, Members of our Board of Trustees, our Heads of School, Chair Borman and Tom Frederick. Thank you for being here. You all being here. And students, I hope seeing everyone here this evening helps you understand the type of community, the type of legacy that you're a part of. This evening marks NCSSM's 35th Convocation. About this time in 1980, first class of 150 juniors was here on campus. Preparing for the first year of exactly sure along with the faculty of staff who was also preparing for what they were not exactly sure was going to happen. But what they hoped would be the year to explore the infinite possibilities that lay ahead of them in this new idea, this new opportunity, this new school. They were looking for the infinite possibilities that the newness of NCSSM would bring to them. Fast forward 34 years and hear you all sit 680 students from the classes in 2015 and 16. From what I understand, you are now sitting in a much more comfortable setting than those 150 students were back then. You should do a little bit of research and hear those stories. But I bet you still have some of the same feeling that the students in the class of 1982 have. You're not exactly sure what to expect, but you have hopes of the infinite possibilities that lay ahead of you this year at NCSSM. Much has changed over 34 years. Many of the people, much of the things. But what has not changed is that you are here with talented students all across North Carolina. You're here with outstanding faculty and staff. You're here with the tremendous support of our state and the many friends of our school. Because the case for students here 34 years ago, you will find that these are the key ingredients to infinite possibility. I want to take this opportunity to welcome our speaker, Rebecca Bupwald-Japosa back to NCSSM. It's great to have you here. Thank you for making the trip to be here with us. We will hear more about Rebecca's career in a few minutes, but I believe you will be very interested in all that she has done and accomplished in her short time graduating. Since graduating from NCSSM, I'm looking forward to her helping inspire us as we start this school year. I think it's fantastic when we have a one-night comeback in NCSSM to speak to current students. It gives all of you a chance to imagine, to see yourselves and the possibilities that lay ahead of you, 5 years from now, 10 years from now, 20 years from now. To this point in your life, you've worked very hard to achieve success and lay the foundation for your future. Every student in the auditorium has a success story to tell, but you would not be here tonight. Not all of your stories are the same. You come from all over this great state of North Carolina. 85 of North Carolina's 400 counties are representatives here tonight in the auditorium. And you bring with you a diversity of experiences that make you all different people. But you all share a common commitment to learning, to being successful in school, and in your desire to accept the greater challenge. And that's why you're here this evening. So again, I welcome you to our 35th convocation classes in 2015 and 16, and look forward to an outstanding school year with you. At this time, I'd like to introduce Steve Warshall to introduce our guest speaker. Thank you. Thank you, Dr. Roberts.  Her family and her friends who have joined her with us, joined with us to hear her tonight. We have Ms. Jean Buck Walton, one of her grandmothers. Ms. Petrie-Tipp-Posey, you're called. Another grandmother. Ms. Maureen Dunlap, your aunt. Mr. Daniel Berencine, who's the next partner. Ms. Shane Trucklin, my friend. Mr. Juan May, Ms. Trucklin May's husband. Mr. Carwood Woe, who is also here with Ms. Trucklin on. And finally, Ms. Ashley Cunnite, class of 2004, and here is still a good friend of Rebecca. Please welcome them tonight. We have to read the article about Rebecca being a stentorian. It's quite a list of accomplishments. I'm not going to list all of those. But I do want to mention a couple of them just in case you have any chance to read the article with me. She is a graduate from the class of 2004 from NCSSM. She attained her undergraduate degree from Harvard College and her doctoral jurisprudence from Yale Law School. She interned in the White House Counsel's office and completed a civil rights fellowship in the office of the U.S. Attorney for the District of Connecticut. She has a one-year federal clerkship on the Court of Appeals for the Armed Forces, the highest military court in the U.S. after which she will clerk for one year for the U.S. Court of Appeals for the first circuit. She served as Deputy National Press Secretary of the Democratic National Committee during the 2008 presidential election and co-authored 40 more years how Democrats were ruled the next generation. Clearly the authors thought that was going to happen with civil rights. She writes on topics from religion, race, ethnicity and sexual orientation to the Supreme Court and health care for publications including NPR where she interned for legal affairs with correspondent Nina Totova. The Nation, the Atlantic, the Paris Review, the Daily Beast, the Civic Standard, the Huffington Post and CNN. She provides political and legal commentary for national and regional radio stations and has appeared on MSNBC. She has also served in national advisory boards for generation progress and advocates for youth. She has been named one of the Blammer Magazine's top 10 college women of the year, the Heria's Truman Scholar for Public Service and the Henry Bruce Scholar. It's in just 10 years that she graduated from Science and Media. That wasn't everything she came out of. We are indeed fortunate to have Rebecca here tonight. Please give her a warm welcome back to NCCC. Sir Warshaw, thank you to my grandmothers, my aunt and her partner and my friends from Science and Math in the Durham School of the Artsville who have come tonight. When Vice Chancellor Warshaw asked me if I could deliver the convocation address, my first thought was yes. The second was, am I that old? No, of course is the answer. But I graduated from Science and Math in 2004. Most of you were probably still drawing on things you should not have been. So was I. There are photos. My dorm room walls usually had everything from molecules to timelines of western civilization on them. On post-it notes, not on the wall itself. So I'm really glad and very honored to be here. I'm also slightly relieved. Friends who do not get to go to Science and Math are sick of hearing me talk about Science and Math. Not only do I get to talk about Science and Math today, at Science and Math, you have to listen. So here's how this is going to go. I'll start by telling you a little about my life after Science and Math. In part because that's what most tweets I receive are questions. And in part because I think you're more likely to be patient with me, as I tell you about things that are not directly, immediately related, earlier in this speech. Then I'll talk about my life and yours at Science and Math, because by then you'll be tired of listening to me and I'll have to get your attention back. Then I'll talk about your life after Science and Math and you should definitely be interested in that part of this speech. Conventional wisdom is that most people in their 20s and 30s who still talk about high school are still talking about it because that's when they peaked. They were prompting or prompting or whatever. I'm still talking about high school because Science and Math is the reason that whatever my peak is, it will be higher and greater than anything I could have anticipated for myself before I came here. That would be true for you too. The narrative of my life that I tell when I'm not supposed to still be talking about high school starts with college. I talk about the night that I became interested in electoral politics, about election night 2004. I went into Boston where Secretary Kerry and Senator Edwards were supposed to be giving a victory speech. I stayed until 3 a.m. It was of course raining. For those of you considering college in New England, Massachusetts rain is not like North Carolina rain. It is awful. After hearing the election results, we trudged out. And of course I actually become interested in politics while at Science and Math, but I didn't yet understand much about electoral partisan politics. My household was not particularly political, or at least it was not liberal meaning. I was interested in policy issues, not parties ultimately. But the election mattered to me because I realized that the types of policies and laws that I really thought would be good for this country were now going to be on hold for at least another four years. What clicked for me was this. Elections are the foundation of public policy. I could study all I wanted, write as often as someone would publish me, and I didn't need much if there were policy makers who were willing to listen. Any of my various hallmates or teachers would tell you, patients has never been my strong suit. So, immediately after the election, I wrote to a political consultant, James Carville, President Clinton's campaign manager. If you watch any political commentary, Carville is the one with the Louisiana accent you can barely understand. I still barely understand him. Why he hired a teen-year-old with no political experience remains unclear. It may have had something to do with the impassioned email I wrote to his office. Didn't he know Senator Perry should never have written off the South? They lost voters in the Southwest and Midwest for the same reasons they were losing voters in North Carolina and Virginia. It could also have been something else. Assistant later told me that she misread Harvard and thought I went to Harvard. They never would have hired me if they knew I went to Harvard. I don't blame them. I worked that summer after my freshman year at a restaurant now far from safe money and then took off to D.C. And then for the next three years, I split time between D.C. and Massachusetts. I got to work on campaigns in Europe and South America, which was awesome except for the time I got malaria. But thankfully, I had Dr. Branson, who seems to have had survived worse than the way of tropical diseases and parasites, so I was not too concerned. By 2008, I understood a lot more about electoral politics. And that election night, I was the deputy national secretary of the Democratic Party. That night, President Obama delivered the speech I'd waited four years to hear. And this time, I was very happy to be awake at 3 a.m. It helped that it was not raining. Two months later, I went back to college to finish. I applied to law school. People asked, don't you just want to do campaigns? I didn't. I got into politics because I cared about advocating for good policies and laws. Campaigns played a valuable role in that process. But I'd rather work for a non-policy directly than now. So I went to law school in London. This is a story that involves a lot of luck, or what seems to be luck. I'll be the first one to tell you that there was luck involved. Carville's assistant misreading Harvard, for example. But what often appears to be luck is actually a constellation of other factors. NCSSM isn't just one of those factors. For me, it was the main factor. In 2018, I was better prepared to strike down on my own. More willing to trust my gut than most of my peers to just write a letter and take a semester out from college. It's largely because of science and math. Partly because it's a residential school. But a lot of people go to boarding schools. I'm not going to give you a list of reasons why these other boarding schools are not as good as NCSSM. It wouldn't be classy. It would also take too long. I want to talk instead about the reason science and math is fantastic. The ways that you can and should take advantage of your time here. The ways in which the school is responsible for my preparation for life after science and math. And along the way, I will also mention things about your experience here that could be difficult. Things that I found hard. The first draft of the speech didn't mention these things. Why would you invite someone to talk about what did not go well? Because, as extraordinary as this place is, not everything will go well for all of you all the time. There will be rough patches and disappointments and drama and vitrails. At least, I think that's how I remember high school. That might just be not the problem. In any case, it's probably a good thing to start the year with a voice saying that's okay too. So here's my advice. The challenge science and math offers is not just academic. It's personal. Can you entertain another way of thinking about something? Can you allow your own views to evolve? Can you let yourself fail and evolve from failure? I hope so. Six things to keep in mind. One, this may be the first time you're not the best of a subject. That happens. Chemistry and physics were very humbling experiences for me. As was mathematics. When Dr. Allen wrote me a letter of recommendation for college, I can only imagine she said something to be effective. Rebecca will never be a chemist. But, previously, someone worked so hard for a good grade this course. I did not see the letter. I'm just speculating. But thanks, Dr. Allen, for all of your guidance for the extra help and for that letter, whatever it said. Two, science and math may be the first time that you encounter people who have had opportunities, experiences, and advantages that you didn't know existed. When I got to Harvard, I doubted myself all the time. I'm a graduate of prep schools and the musicians who trained in the yard and the Olympians who rode. On my first day in Yale, during our convocation, the dean asked everyone to please raise a hand if they had a parent who was a lawyer or if they had experience in the legal profession. It seemed like most hands went up. The good news was I had a head start on getting over it. College was not the first time that I'd run into people who seemed a lot more poised and polished than I was or had experience I couldn't or didn't have. So, when you give the temptation to be intimidated or maybe jealous, hold it back. Let yourself learn from your peers. Meeting, living with, and working beside people with very different backgrounds and experiences is a very important thing. And your experience, your opportunity to do so here is unique. When I was in science and math, being yourself and owning your experiences and achievements did not seem like a competition. No one was reporting it over me that she had already taken an APE con or he had a lot of event. We were in it together, others' experiences enriched my own. That would be true with your time here as long as you were committed to making it so. 3. This is one of the best opportunities you'll ever have to develop lasting meaning for friendships. The friendships I developed here have lasted more than a decade. Mostly because of, sometimes despite, bonding experiences on families. Like the snowstorm that resulted in half the school trying to sled down the hill in a subsequent trip to the ER. The friend who ended up in the hospital loves this story by the way.  My friend made it, the coat didn't. I told her that I probably shouldn't tell that story today. She said there's nothing wrong with that story. Sledding is harmless, it's not like we planned to break my nose. On another memorable occasion, a friend on third Brian announced she liked bangs. She was recruiting someone to cut her hair. I became convinced that internet instructions for cutting hair were infallible. How hard could that be? Hard. The result is suboptimal. Fortunately, due to the strength of our friendship as established in Science and Math, she forgave me almost immediately. She didn't say, however, now we know why you didn't get into the Harvard School of Hospitality. We bonded over all sorts of things. We had a series of tower outages, and everyone worked in them all the way together to get things done. We had all-wide dance parties, in which I was allowed to participate despite not being able to dance. Very kind. I remember we went to Ninth Street to get municipia since after we turned 18. These are memories, not suggestions.  Or, because you have become, or will become, a much more tightly knit community than other high schools, you have a much greater opportunity to meet a difference in your friends' lives and behaviors. I asked one of my best friends to share her favorite Science and Math Memories. One was the day she came out to me. Because of where she's from and the experiences that she had, she was really worried about it. Then she said, I told you, can you react like it was totally normal? She felt safe and accepted. I am grateful that that was something that I could give her. And in return, her support made my own process of coming out years later much easier. It may be that here, you're faced with decisions and situations others don't face until adulthood. I did. You may encounter peers who struggle with depression, or eating disorders, or addiction, or you may experience these things. I hope you don't face any of these things, but you could. I'm grateful to have faced these things in an environment in which there are people and resources available to help. I can't urge you enough to take advantage of the support available. And with these challenges and others used as an advantage, that means that the decisions you make and the actions you take to help others here may have greater meaning and consequence than any other juncture in your lives. Five. Appreciate that these are some of the best, most involved teachers you'll ever have. Not only are your teachers more impressive, more qualified than the other self-teachers, they're more dedicated. Dr. Igalis helped me prepare for the A&P US History exam on her own time. Dr. Morrison, who never actually had me as a student, adopted me anyway. I've gotten messages from him on several planets. My net-fizz teacher was the one to teach me how to pick out a prom dress. Halterneck, not strapless. If only I had listened. And when I got sick of my senior year, teachers found a way to help me out here. Teachers here come in early and stay late. They read academic work line by line. They read college essays line by line. That doesn't happen in most places. Not in high school or ever. Teachers here are overall more open to and interested in forming mentoring relationships than anywhere I've ever been. I benefited from that enormously. You can too. Six. Take the chance to fail and learn how to move on. One of the reasons I was surprised to be invited back to Science and Math is that I was not, for me, a model student. I wrote a lot of rules. A few were literal rules, actual rules. Teachers, administrators, stylized them, they were sorry. More often I just did things a little differently. Sometimes because I didn't know better. Sometimes because I was stubborn. But often in a good way, because I was in an environment where instructors reinforced the idea that testing moments and exploring boundaries was a good thing. Succeeding in Science and Math is not about being perfect. It's often about being willing to be imperfect. If you don't understand, ask the question. Admit your limits. You'll have to hit your limits to push past them. In general, just be willing to try, even if you're not sure you'll succeed. In whatever your path, you'll be better off for that willingness. When you open yourself to the many new experiences you can have here, you gain the opportunity to find what one teacher calls a place of grace. Your sense of self here for that will carry you forward. And here's my advice for after Science and Math. When you leave Science and Math equipped with all of these advantages, be yourself. Usually people just say, be yourself and expect that phrase to self-execute. It's more complicated than that. So I have some more specific advice. Please, please do not exaggerate your life. You will be tempted. A lot of people do it in little ways and big ways. The obvious reason not to do so is this. It's wrong. But you're also setting yourself up for a fault. You could get caught during an interview process.  This has happened to me. Not failing, but being tested. If you're not found out at an interview, you could get caught later. But most of the time, this is the best reason not to be tempted into being inauthentic, your best asset is authenticity. If you've begun from a foundation of insincerity or insecurity, you've thrown that away already. The other piece to being yourself is this. Trust yourself. Don't ask why me. Ask why not me. Many of the choices I made along the way seem risky. What if the car bill internship didn't work out? What if I'd lost my job after leaving school for the campaign? In part because of science and math, I was confident enough to take calculated risks. And I was confident that I was up to the opportunities that I was given. John Updike said, four years was enough of Harvard. I still had a lot to learn, but I had been given the liberating notion that I could now teach myself. Whether you're going to Harvard or UNC, or UNC State, you go already having been liberated in this way. At NCSSM, all of the advantage was all the perks of science and math, learning new classmates, building relationships with teachers, becoming more confident. These require keeping an open mind. So does the challenge that comes after. Your generation is going to see faces serious with false dualisms. In fact, it's already starving. In politics, it's red and blue. In policy, it's idealist and pragmatist. Academia has theory and practice. It's minorities' rights by race or ethnicity or religion or gender or sexual orientation instead of just human rights. And these all boil down to us and them. The challenges that we face across local, state, and national borders differ in details. But the crises that these past two years from economics to other demographics have demonstrated how tightly linked our lives are becoming. Your education and science and math will help you begin to think more broadly about your lives and those of others, about your capabilities and those of others, and to recognize the connections among us. It's important that you embrace this opportunity to expand academic and personal horizons. Because there is no them. There is only us. Communities from local to global. There are only 16 fighting challenges for a willingness to work together. Look at what's happening in Ferguson, Missouri. We're seeing, for example, what happens when they're in an effort to connect, to understand, to think about a greater community. What's happening is very much about fall schoolism among us and them. It's a failure to see that we're all part of the same people. Same American people with same rights, shared experiences. It's critical that you begin thinking about how to approach and handle these issues because soon it will be your generation, the class of 2015, the class of 2016, that has to address them. In the meantime, over this year or two, be grateful, be proud. Remember that it is okay to keep talking about where you went to high school when you went to a high school to raise the science and math. Thank you for making part of this gang best of luck. Your story is an incredible example of the diversity of opportunity that is available and the opportunity and experience that is available to all the students. So, distinguished faculty, guests, and students, it is my honor to welcome you here to the beginning of another unique and extraordinary year. So good afternoon and congratulations to all of you. Juniors, for your acceptance of the inaugural of the essential first steps on each of your journeys that will truly come to be the greatest challenge that is the North Carolina School of Science and Mathematics. And to the seniors, welcome to round two. For you, this convocation represents the beginning of an end to your two years here at SCSM and to the 12 years from kindergarten to college. Now, all of us have a long school year ahead of us. We feel both momentous achievement, arduous tasks, and most importantly, life time. But before we spring head first onto the road ahead, here are a few things that I hope we'll all keep in mind. I know many of you have made it here by virtue of your competitive spirits and individual ambitions, but if there's one thing I've learned after a year of housekeeping, work service, American studies, and living on the fourth floor, it's that no characteristic embodies the SCSM community better than the spirit of collaboration. While built on a strong academic foundation, SCSM is sustained by the resilience of its community and the camaraderie of all students, the athletes, students, scientists, musicians, programmers, painters, and mathematicians. This last year has taught me that often times your greatest asset comes not from within yourself but from those around you. Always remember that just as double the recite of Hogwarts, here at SCSM, help will always be given to those who ask for it. While most of us probably would never have the same hat or a long white beard, or at least maybe not until you have the notion of a drummer, rest assured that your peers will offer you the wisest of advice and be the ones that tell you they can, even when all others tell you they can't. From the long conversations with your counselor and late night tutorial sessions with your chemistry teacher, to the anti-failing American studies Facebook groups, to the French shoulder you cry on after that impossible business test, you'll find yourself with so many people to thank individual for your success. Don't get me wrong, this is not the time to be very dependent but rather to utilize the invaluable resources around you as a foundation and a base that will allow you to reach higher and see further than you could ever on your own. Never rest on your laurels but continue to strive to achieve the same spirit that led you here today. In clicking I accept this April we not only accepted entrance to one of those prestigious schools in the country but also accepted ownership of your success. Whatever you're calling NCSTEM will be to you exactly what you make it.  To take that self-defense class to sign up for all of those clubs before finding a true passion or to follow up on that crazy idea for something like making colored paraphernal work getting money for solar panels around campus. As you continue your journey to science and math, don't forget that inspiration can come from just about anyone. In fact it was Kanye West that taught me the final right to remind what I have for you all today. We all know our goals in life, our missions, our destination, the figure of light at the end of the tunnel. But just like street lights on a highway shining moments in life pass us by endlessly. It's easy to see life as a constant race that requires speed, endurance and endless competition to edge ahead of those next to you. It's easy to see NCSAM like such a marathon with colors at the finish line and you'll find yourself burnt out before getting there. So remember that the journey is just as important as if not more than the end itself. Never forget the shining lights the late nights with your friends shivering through happy half in the middle of the winter just because or sprinting down 9th street to eat the sunset.  Even in the middle of the second try when work and sleep become mutually exclusive or when breakfast or even lunch doesn't make the cut for things you think you have time for don't ever give up. Know that your darkest times will not define you because you struggled, but because you made it through. Along with 679 of North Carolina's best to light the way to the end no matter how many apes you take or how well you do on your SAT you'll leave here with an experience to last up a lifetime. Something that can never be taken away and will often take you further than any number on a resume you will. So make the best of your time here. Remember what you learned from your teachers your friends and yourself. Let's make it a great year. Thank you. I'd like to say thank you to Rebecca again for being here and speaking with us this evening and sharing her words of inspiration from what she was a student to now as she's a professional. Thank you to Abby for your words as well. I really appreciate those. One of the things that always amazes me and I guess now after four years of being here shouldn't. When you hear alumni whether they're class of 82 and class of 2004 or Abby who's the class of 2015 they talk about their experiences there's so much in common and that's something to be proud about as an institution after 34 years that we can say that. I also want to thank our honored guest who are here this evening for being with us to share 35th Convocation at NCSSM all of our faculty and staff who every day as you can hear from what Rebecca had to say do things that make this place what it is for all of you that are here. Thank you for getting this school year off to a great start and all the members of the classes in 2015 and 16 thank you for being here and accepting the greater challenge and continuing the tradition of excellence that is the North Carolina School of Science and Math that you've heard some of this evening. The start of the school year is always filled with great excitement and with possibilities that come with starting anything new. So as you experience learn, wrestle with joy all that lies ahead of you this year I want you to remember what got you here.  NCSSM as has been said earlier you will have greater educational opportunities greater challenges than ever before. Every one of you has the talent and ability to be as successful here as you have been throughout your entire school all of your education to this point. I want you to know that you have the support of every member of our faculty and staff and that you will not find anywhere a better or more committed group of professionals that you will hear. You'll have the support of the alumni who have come before you who each year give back to the school of their time their talents and their treasure so that you will have better opportunities than they had when they were at Science and Math. However, with all of the support you will have at NCSSM it is your commitment to being successful that is most important more so than anything else. So as we begin the 2014-15 school year remember this year is yours for the challenges that we'll present yours for the learning that we'll offer and yours for the infinite possibilities before you. I look forward to working with each of you this year into your great success. I hope everyone after we've recess will enjoy joining us on the Brian Long Court Reception an opportunity to talk with our speaker and others. So again, as we start the 2014-15 school year I have a great year and I wish you all the success in the world.


All right, it's 12.30 now. I'll give everybody another minute or two. There is chat turned on for there. So if you'd like to ask a question, you can always ask it in chat. Turned off, kept everybody on mute so that we can get a good recording of this for other folks who can't join because there's a lot of people who are time zone challenged in the commons group. So I'd like to get started. My name is Diane Neuer. I'm the community manager for OpenShift and I'm really pleased to have this many members of the OpenShift commons groups joining in with us today. And there's a number of you, already 20 individuals here. So I'm really pleased with that. This is the first in our series. We're gonna do about one a week for the next little while on different topics around OpenShift and V3 ops, OpenShift on OpenStack. And this first one, we have the great pleasure of having Mike Barrett who's the product manager for OpenShift from Red Hat. And he's gonna give us an update on OpenShift V3, the new stuff, and sort of set the ground for what OpenShift commons is. And so I'm gonna let you get started there, Mike. And we'll save time at the end for Q&A. And as I said, please use the chat room for questions and we'll get started then. All right, thanks all. All right, thanks Diane. So Diane mentioned my name is Mike Barrett. I'm a product manager on the OpenShift team. I specialize in the on-premise distribution or the private cloud distribution. And so I get to go out to a lot of our customers and talk to them about how they're using the product, how they're integrating with their data center infrastructure, how they're working with developers, applications and all that fun stuff. So thank you for having me. We're really happy and pleased with the comments, right? It's a very specific implementation of a community gathering. So let's get into what that is. No barriers to entry, right? You don't have to buy into this group. What we try to do is bring in an assortment of different people from different backgrounds, our actual customers, our ISV partners, our VAR resellers, our code contributors up in origin. You're all invited to this gathering and you all have an equal voice. And what we're trying to do is just structure around what that voice can be. We'll suggest topics to get things started. We'll hope that you guys will start interjecting with each other, explaining how things are going. So that's really the premise of the comments. So really bring our larger community together. It's a meeting place, right? It's a dynamic website and it's more than anything else an information repository. It's another place to get more information about what we're doing with the product, what people are doing with the product more importantly. So we have a lot of customers at this point in the community. This is a way for you guys to start talking to each other from a peer point of view, to share your interests and goals. Again, tell you how many times I've been in customer meetings where I wish another customer was there and many of our customers want that opportunity to reach out to each other without us in the middle. So it really is the next step for the product. Once you have this many customers, it's just a natural progression and we're ready to take that further with you. You don't have to be a code contributor to be part of this community, right? We can better the documentation. I can get feedback from user stories. We can talk about the UI design. We can talk about the coloring. We can talk about pool requests. We can talk about just about anything you want to talk about how you've implemented the product at your own data center. How you've mitigated DNS or DMZs or did global routing or found a solution for shared storage or integrated with a continuous integration tool set or got into a larger get deployment. These are all things you can start sharing with each other and with the community. Participation, lots of different places to get involved. For most, it's an email alias, right? So OpenShift-commons has been active now. If you haven't sent an email out there to OpenShift-commons, please do. Introduce yourself to the other members that have signed in and said that they wanted to be part of this community. It's an ice breaker. Just give a little bit about yourself and why you joined. Other than that, we are on all the classic multi social media conduits, right? The more important ones for this community, I think we're going to be the Trello boards. If you have not looked at the OpenShift Trello boards yet, totally do. There's a lot of information there about where we're headed and a lot of information where you can contribute back to that open source project. All of our developers are on IRC. So that's another great area to grab on to. Diane runs our Google Plus community. I think we're over a thousand members at this point. So that's another one to join. Facebook isn't as attractive for, I would say this community. Blogs are definitely, and in fact, if you ever write a blog on the product, just ping us or the community and we'll point some social media in your direction. The SIGs or the interest groups are going to be important. We have two interest groups right now. We have Platform as a administrator, somebody who owns the Paz, keeps it up and healthy, deals with a lot of the day-to-day operations. A lot of those topics are very specific. So we have an interest group on that side. And then the next one is where we're going with the version three product, which I'm here to talk to you about today and not some bolts and designs and all that fun stuff. These briefings, which this is an example of, are gonna be on BlueJeans. So that's where you're gonna be able to hit us up just like you did today and find out more information about the coming topics. So let's talk about the next generation. This is a product that is under active development right now. It's OpenShift version three. We're asking our developers to maintain two code chains right now. They work on the 2.x and the 3.x. We don't wanna stop cold turkey on 2.x. We're still putting features into that and we'll continue to do so. That end-of-life support date is well into 2016. So we understand it's gonna take a while for our larger customers to migrate over to 3.x. When we look at 3.x, it's got a lot of great components that I'm gonna get deep into. But first, why make the move? And it starts around innovation acceleration. We really live in a world where applications have a shorter life cycle with the market capitalization. We look at the World Series apps that hit your iPhone and Android. A lot of people made a lot of money off of them and how many of them are making money off of them right now. So it's a smaller window to get in and get out. It's also a more innovative, more cycles during innovation, right? We're not just doing paper processes and doing simple CRM relationships with our customers. We're doing larger analytics. We're doing hit and misses and we're really mapping the next generation application. So we need a platform that's gonna allow us to really innovate, spend a lot of cycles, but not be forced to eat that cost. Be forced to stand up that infrastructure. And we find that platform as a service really balances these two approaches and how do they balance it? Well, we're using containers. We're moving to microservices and APIs for those services and we're moving to a DevOps relationship. So where are we innovating? What is new about this platform? So right off the bat, it's based on REL7. We're moving away from REL6 and onto the REL7 with this platform. REL7's got a lot of namespaces that we require to pull this off. We also have, Atomic has a new distribution of REL7 that I'll talk about on the next slide. If you're stuck on REL6, we can totally run REL6 workloads. We just run them on top of a REL7 host, which run them in the guest container. So no problem there. Container model changes drastically. We move over to a Docker model from our gear model. This allows us to pick up more namespaces like the PID and the network. Also do some more real IP work and other features. Orchestration changes, right? We move from our Ruby broker with a active MQ message bus and a Mongo storage over to a Kubernetes backend. And I'll talk a lot more about that. Packaging model changes. We're no longer adding personality or content into the gears with cartridges. Kind of merge the cartridge with the gear and we come together under a Docker image. Platform routing. Right now in the 2.x, we pretty much give every application its own routing. We see an HAProxy in front of it. You integrate that with your larger data center fabric. We're moving to a larger central fabric and I'll talk about that. So Atomic, right? How many pads providers also have an operating system? And right down the hall from me, we have the rail kernel engineers working night and day on this atomic distribution. It's just enough OS. It's moving from 4,000 RPMs down to 400 RPMs. Its purpose in life is to run Docker containers. So it uses a RPM OS tree update mechanism to give you a more confined environment and adding software to it and rolling back off of different file system partitions. It allows automatic usage of system D to init and watchdog the containers that you may run on top of it. It automatically brings in SELenix policies for us. So a lot of the stuff that we were doing in OpenShift, we now push down to a dedicated operating system that's built solely to run containers. And this really breaks down the operation costs that we were facing in the previous product. Current generation, you guys seen this slide a lot, right? It talks about our gears or SELenix policies. We sit on top of nodes, use our broker. That changes, right? That is what we're here to talk about today, these nuts and bolts. So on the broker layer, that becomes a Kubernetes master. And on that Kubernetes master, we have some services that are important to us. We still will support the Apache mod and all that authentication that you'll find there. We're adding to that OAuth. We've had a lot of requests over the last couple of months to add OAuth to our authentication. So that's gonna be there for you. ATD is our persistent storage layer that keeps track of the services across the cluster. It's found in a lot of solutions like this. So it's got a really good track record for the job we're asking it to perform. I'll talk a little bit about that a little bit later. The replication controller, this is another nice thing about Kubernetes. In order to get onto the platform, you have to have a health definition. And if you fail that health definition, well, I'm just gonna just replicate you somewhere else across that Kubernetes cluster.  So no longer does it matter, you have different recovery processes if you've lost a node, if you've lost a container, if you've lost a routing mechanism, doesn't matter. We're just gonna replicate you on another part of that cluster. The scheduler is really the placement policy, right? This is how we find the least loaded node. This is how we identify which nodes have the right content, how we identify which ones are in the right availability zones or the regions. What's nice about Kubernetes though is that this is very pluggable and there's other vendors in the market that are interested in contributing to it. So we have Hortonworks talking about plugging in yarn, we have Mesosphere talking about plugging in mesos. So that really allows the platform to grow organically in that ecosystem. Moving out of the broker over to the nodes, these are also called Minions and Kubernetes speak. We have a couple of nice things to talk about here. We have pods. Pods, it's an interesting name pod because it makes you think that there's a lot of things inside the pod, but it's not the case. So a pod will typically wrap around a single Docker container. You will have pods that have more than one Docker container in it when you want low latency or you traditionally would run things on the same box like a Postgres and it's admin daemon or something like that. But for the most part in the applications that we end up deploying and talking about, you'll have one Docker container in a pod. For an application, you'll have multiple pods spanning multiple nodes. You can run more than one pod on a node. What's really clever about the pod design though is that it holds the definition for the shared storage and the network for that Docker container. This allows a little more mobility for that Docker container as it tries to find another host across the node should something happen. But that abstraction layer really opens the door to a lot more use cases for us. On top of the pod, on every single node out there, there's a service layer. And the service layer is what talks to SED. It's what knows the relationship between pods, the form applications. It's what knows what all the nodes are doing. In this way, every node what knows what every other node is doing. So it's very easy for us to replicate and to move things around if everybody knows what everybody's doing. And the brain trust of that relationship is that SED. We have one routing layer, right?  You'll have one. It'll be for the platform. It'll be customizable. It'll be HA, you'll be able to integrate it with your own data center fabric. But we've had a lot of requests to move to a central routing layer. The developer experience changes, right? We wanna keep the developer experience that we have today. The developer shouldn't have to know anything about Docker just like you didn't have to know anything about gears. He can come in at a code point of view from his IDE, from his Git, commits, whatever the case may be. That stays the same. We stand behind that 100%. What we needed to do is add something to it, right? We now have these developers that wanna bring Docker images from their laptop or from Docker Hub or from other locations into the platform. So we had to do something to allow that, to allow that pool from a local repos, that checking, that managing, that bringing up pods and all that fun stuff based on a Docker image that you're bringing into the platform. So I'll talk a little bit more about how that happens. Applications are still deployed, REST APIs are still there. So that's pretty much the holistic picture where we're moving with the platform. What we think this represents is how was we, our first move was the Docker. When we looked at our, this is going back probably two years. When we were in rail six, we're working with the rail kernel engineers. They're coming out with their own next generation container, putting a lot of those namespaces and a lot of those attributes into rail seven. And Docker's coming up at the same time. And what was attracting to us was the larger community that was being born around Docker. We have the kernel engineers that are capable of writing container technologies. What it didn't have was that ecosystem, that outside of us ecosystem that we wanted to take advantage of. We saw the same exact thing happening at the orchestration level. Shortly after we made the decision to move to Docker. And by doing it at both levels, by commoditizing the technologies at both levels, we pick up exponentially larger communities than ourselves. And this has been just an enormous win for the platform. Because what we have always been interested in was the developer user experience, was the services, the deployment patterns, the things that we offer, the integration with Git and Jenkins, and really the superior nature of that rail operating system and allowing us to consolidate a lot more workloads onto it. That's what we've been about. And this is the next generation pass back we firmly believe. And this is where the industry is going to move. What an ecosystem it is. Talked about that choice to move through it before. A lot of vendors from the competitive point of view, from friends and alliances, from different industries altogether. So they seem to all be coming together around one solution. What is better, right? What is better in this architecture that I just showed you? You know, OpenShift has been a bit unique in the Paz market in that it allows for non-HCP traffic. We just released our XPaz, our Fuse cartridges two months ago. They allow non-HCP traffic to be born and routed to and from the platform, typically in a Paz market, you use HTTPS on the platform and you call outbound to services that you need and you bring them back in. The difficulty was routing back in. Routing an outbound was quite easy. Getting back to the same gear or the same container was difficult for them. We're using an SNI trick to achieve it in this current platform, the 2.x platform. But in the 3.0 platform, that goes away. A lot of that heroics that we were doing at the node level with the Apache routing, with the V-hosts and then with the loopback interfaces, you know, 127.0.0, that all goes away as we achieve the network namespace. So we don't have to start with the HTTP. We can start with the database. We can start with non-HCP traffic and we can build from there. So it's a different beginning point for applications. The other thing that Docker brings to us is this immutable concept. Operations can start from that gold image and then anything that changes, such as code pushes or new features, we can cause a triggering or a layering to occur. And then we can use that layer instead of changing that gold image. So we have that immutable standard. You can further decouple depth from ops, right? We can go with known deployment patterns. We can learn from our 2.x with those hundreds and hundreds of quick starts and cartridges that we have out there and how over 2 million apps deployed on openshipped.com are many enterprise customers. We know how to stand up a lot of these applications. That deployment pattern just wasn't there in say the Kubernetes or Docker and we're bringing that to it. You know, better abstractions of the network, storage and health. Network has been probably the number one integration point that we spend the most time with our customers. And so this gets a lot cleaner as we move to a Kubernetes cluster with the pod model. The shared storage in the 2.x version were blocked on block storage and API based storage like S3 or ESB. We pick up the ability to do more file based storage which is very helpful because a lot of customers are using that because it's typically cheaper. And health, right? We're talking about that replication controller before and being able to replicate without doing very specific things for very specific failures. It moved to a true cluster, right? This thing looks more like an HPC type cluster that we saw in the early 2000s and where we're able to move things across farms across larger segments of boxes. You're allowed to declare how you want your application to look, what qualities you want from it and the cluster will make sure that's maintained and make sure that that's out there where you wanna be introspective if you will, you'll do that the scheduler layer. So what does OpenShift bringing on top of all this, it gets confusing when you start commoditizing your components, what features were just in Docker which features were just in Kubernetes which features are just in OpenShift. And what OpenShift's focus is on is that Docker linking, right? Being able to do that overlay network across your multiple nodes and being able to cluster out the EAP instances, adding nodes to Tomcat, scaling your databases, adding sharded MongoDB instances. This is what the world that we live in. This is where we wanna be and we're able to bring that to that Docker linking projects. Around the user experience, right? We're more interested in the developer projects. We're more interested in seeing a project be born with team members, with team members being in different roles, with seeing usage of resources or IP and other things. That's what we wanna track from the developer point of view of a code project. And it doesn't necessarily need to be a developer, it could be a service admin or operations admin that owns that project and delegates out. The next one is the big one, right? This is, if you looked at our existing user model in 2.x, our workflow, it's very source code based and binary deployment based. It's adding contents to applications, adding new features to applications. And to do that, we needed to bring that over in an open source project called a source to image that I'll talk about in a little bit.  Have Docker layers be born on the right atomic node, on the right shared storage, on the right pods and bringing those up with the right routing. So that's a lot of heavy lifting that we're doing for that developer. Deployment patterns, we already talked about moving things across the life cycle is important as well, right? We wanna be able to promote code from different environments. We want continuous integration solutions as a Jenkins to be able to target different projects that represent different life cycles for that application. And that's something we wanna come out of that box with. So source to image, this is a really cool open source project out there. If you just Google open shift source to image or STI, we sometimes abbreviated to. This brings up the main use case that we have, right? From a developer point of view, knowing absolutely nothing about Docker, absolutely nothing about Kubernetes to be able to just commit back off of a Git to either work in his IDE, see his project and have that rolling, right? Have that rolling of the Docker layers, identify a Docker layer, push it back to that Kubernetes pod, bring that pod relationship with the Docker linking, the overlay networks to the other parts of it, form that route, maybe it's a DNS route, if it's non-rattable DNS, all those things are just automatically happening for us. It also gives us a cleaner, more scientifically pure rollback mechanism. I know that I'm gonna roll back to a very specific layer of Docker, very specific image. And that's helpful for operations. So the other side of this is the platform, Kubernetes, underneath us, needed to be, needed some more intelligence to it around our use cases and that's what we're bringing to it, a more intelligent platform based on the things that we care about and what do we care about? We care about changes in source code, right? When somebody commits a line of code, we wanna recompile, relayer and push. When Jenkins wakes up off of a failed or a working smoke test, we want that to work. When a vendor provides a new binary in his Docker hub to update his application, we want that to wake us up and do the redeployment. So we're doing a lot of automation around a lot of the things that people who use PAS care about. They care about their binaries, their applications, their source code and their continuous integration code the path to production. That's where we wanna live and that's what we wanna provide. So at the end of the day, we want a very repeatable and a very fault tolerant across that form in a very automated process as you move your applications around. Where we're focused on spending our R&D is around this triangle, this layer. It's really around the spanning of infrastructures, right? No longer are we seeing people that are running in private and public and we've seen that for a couple of years now. We see people who wanna actually span both private and public with a business service and that's bringing new and exciting opportunities to the forefront. Containers, we've always been about containers and we'll always will be about those containers. We find the atomic project to be extremely exciting in the fact that we have so many kernel engineers working on that and making our platform pushing a lot of that intelligence we had in 2.x into that host. We get to just capitalize on that in a more fluent way, different lowers that operational cost. Microservices, breaking up teams, breaking up monolithic applications, forming independence of features. I can take, I can risk mitigate as I move into continuous integration delivery if only one part of the larger application fails and that allows me to really push the needle and get to that market a lot faster. Dev Ops is basically finding tools that give me a way to define the relationship between two working groups, to allow operations to guarantee the qualities that they want, that resiliency, that uptime, that efficiency, that utilization and then have the devs hop on and be able to think they have full control over that. I have roots, I have all these other abilities to see log files as if I'm on a real operating system and it's a trapped environment. So Dev Ops is definitely fluent, moves into a larger value add such as continuous integration and continuous delivery and that's part of the triangle that OpenShift wants to be a part of. So as we look at our community, this is the community components that we're looking at bringing into the comments, right? The people who we have a lot of CCPs, what we call cloud providers joining the comments, you'll see and you'll hear their voice and what they want out of it. You'll have companies that are into that Docker ecosystem that wanna make sure that their images run on the platform so you'll be able to hear from them. We have microservices, we have a, we're at the forefront with our Fuse portfolio and our new feed Henry acquisition of moving to a lot of these architectures for applications. We're bringing a lot of people in their communities into the comments. And then on the DevOps, we've historically had a strong DevOps presence within the open source communities that follow REL and Fedora and CentOS and we find them joining the comments. So you'll get to hear at each one of these layers a lot. So call to action. You know, I already mentioned, totally hit that email, alias, introduce yourself but I wanna give you some ideas and start chatting about, start kicking around some ideas, where we should go. But in order to do that, you guys have to get your feet wet. So definitely hit these URLs and you'll find there's an alpha one drop of the version three product. In 30 seconds, you're pretty much gonna stand up with Kubernetes Docker and that source to image solution without knowing it. Not knowing anything about it. That blog will actually walk you through the steps. You just copy and paste these commands and you'll get a good feel of what it feels like to stand up a pod that has a Docker repo and have to pull an image to subscribe to a web hook and I'm gonna get hub for a code change to have that code change.  So these, you'll get to see all those components working already in the dev concept alpha one drop. The next drops are coming. We'll have one once a month. So December's will be coming up here. We'll add that project concepts and the multiple users. You'll get that RSE command line back. You'll see multi node deployments right now in the alpha one. It's pretty much on one laptop that you'll be working with and be able to add in more minions. You'll get the platform router. You'll get a Docker repo integration that's outside of the product. And then in January, we'll bring in that browser user interface. We'll talk about more of these Kubernetes components that we can integrate and leverage. And then we'll talk about the Docker layering control. So definitely start with alpha one, get a feel for it, get excited about alpha two coming out and then alpha three. Then beta will add more features. The beta is pretty much what we think in our minds to be a true replacement for the 2.x product and which features it's penetrated into. And we see that starting towards February. And then the shipping product is targeting right now, things change every day, but right now we're targeting for the middle of next year around that June timeframe. So things that we can talk about. DNS has been a big point of conversation with all of our on-premise solutions, not so much the public ones because we take care of that for you, but integrating with DNS. And we're thinking about adding this ability to have non-DNS routes if you wanted them. Just basic IP based routing. So we wanna hear if you think that's a good idea. Another one is environmental variables, right? And PAS, we use environmental variables quite a bit. And it really allows that magic of auto-binding cartridges together without developer needing to know how to add Postgres to the EAP. We can pretty much take care of that for you through environmental variables. What we're thinking though is making them a little more secure and allowing people to have secrets. And this will be using maybe more like a traditional hypervisor key store. If you're familiar with Zen, it has this ability to have something in the main host, some information and have that call through a TCP socket encrypt it up to the guest. And this is a way to have more defined secrets across platforms that our cartridges or in this case, our Docker images can start using. So that's another one to start talking about. Evacuations has come up. Right now you can totally move gears around in the 2.x platform, but it's a couple commands, right? It's identifying what the gears are, it's stopping them, it's then moving them and bringing them online somewhere else. We've had some people say that we wanna one click evacuation process. So we're interested in hearing what do you wanna evacuate? Do you wanna evacuate entire availability zones or is it really just one node to another node? What types of evacuations are you interested in? The idler, right? This is a huge feature for us. Not a lot of past providers offer it, but pretty much in the 2.x platform, what we end up doing is holding the URL to your application up with that HA proxy, shutting down that gear if it hasn't been HTTP requested and over X amount of time. And then when a request comes in, they're gonna hit that URL that we've been holding and then while we're holding it, we'll bring up the gear. This allows a huge density, right? This allows us to run with active max gears of around 75 where traditionally you would think that was crazy. What improvements do you want in the idler? Are you using the idler? Have you seen problems with the idler? Where do you want us to move? Another big one is continuous integration and delivery and that really revolves around Jenkins right now. There's pretty much three use cases around our Jenkins interaction. One is I have an existing Jenkins and I want to just use post-actions after tests have passed to push out these artifacts to open shift to the platform. Another one is the one that we support out of the box and this is us standing up at Jenkins, right? An individual developer can choose at any time that he wants to add Jenkins to his application. He doesn't have to know anything about Jenkins. We just give him that cartridge, he adds it and then when he builds it, builds off on the Jenkins and it'll push that to his environment when it's done the binary. Have you had problems with that? Do you want to see more extensibility in what we're offering out of the box in that area? And then the third one is if we were to have an external Jenkins, would you want it to use open shift, has build slaves and then push? That makes it a little bit different than the first one. So those are the three areas that we're kicking around around the Jenkins use cases. If you favor one over the other, let us know. Let the community know, let's have a discussion about it. So that's an example, yep. There's a couple of questions coming in if you're ready for those. Yeah, let's get the questions. They're in the chat, but Joseph is asking what would be the recommended OS, RHEL 7, Fedora 20, 21 for development? I have my personal opinions, but you can go for it from product management. Right, so I mean, we love RHEL 7. That's what we're gonna make sure it works on, but the Fedora 21 is a good candidate. I think, Diane, do you know what we put out on origin or openshift.org? I think we're using Cento 65. And that's what I've been testing with in Cento 7. Great. Any of them should work on those. So the other question was. Any thought on Go as an alternative to Jenkins or Go CD? Yeah, so in terms of shipping out of the box, we were still favoring Jenkins, but we found over the last couple of business quarters is that there's a huge market and continuous integration delivery. There's probably over 20 companies at this point making quite a bit of money, so they're quite large organizations. We wanna make sure that we're open to all of them, that we work with all of them. And it really comes down to that API at the end, the post-action APIs. So we just wanna make sure that our REST APIs are callable in a fluent manner with whatever anybody else is doing. But for the most part, I think right now we're gonna stay with Jenkins for the out of box solution that we provide. Again, I'm not seeing any other questions. I'm gonna say that if you have questions, you can always ping someone on the IRC channel on OpenShift or OpenShift-dev.  And if any of you are not, just give me a shout and I will add you in. I think we've got most of you on there. And please do introduce yourselves there. Wait and see if there's any other questions that come in. And I can see Romain in the dark there. But I'd also encourage you to visit the landing page for OpenShift-Commons and click on the SIGs. And if you're interested in joining either the Ops or the V3 SIG to get on those mailing lists as well. And we can further send out some more information to you about that if you've got questions. Let's see what the chat holds here. All right, there's another question here. For Enterprise, what's the timeline for Java middleware? Do you have one there? Great. Yeah, so the Java middleware, well, the goal of the release is to make sure we have the exact same content that we're providing in the 2.x and the 3.x if not that, then more. So when we look at the Java middleware stuff that we were providing today, we totally foresee that being in Docker images around the time that we release. More importantly, the app server, the Tomcat derivatives. And then moving into third parties, when you look at Docker, as more and more companies adopted, you'll find more and more officially supported solutions instead of things just provided by the community. So we think June is a good time frame to start seeing a lot of that content. Right. And I'm not seeing any more questions at the moment, is anyone else got anything else? All right. Well, thank you everybody for joining us today. And a special thank you to Mike Barrett for doing this session, because I know he did another one earlier this morning. And so he should be ready for a nice large glass of water, hopefully, and we'll be doing another one next week. I think we're doing OpenShift on OpenStack and we'll send out that the invites and the information for signing into the Boojins to the mailing list as well. So please do pay attention to the mailing list and we hope to have you all back here and help you get through to V3 and help you give us feedback, make full requests and start taking part in the commons conversations. Thank you all and thanks again, Mike. Thanks, Mike.


So my beautiful people I am back with another Elden Ring video and you guys have probably seen the ruin farm where you come to this area where I'm at right here guys um your parkour up these rocks on your horse you jump off you swing in mid air you fall for about 30 seconds and you get rewarded like 150k plus ruins none new game plus right guys today I believe I bring you the best way in doing this minor parkour needed for people not good at that this is definitely the best especially for people who can't take out the hill yet who haven't beat the Elden Beast yet so don't have to work so hard mainly for the people still using the bird this is by far the best ruin farming method in the game today we're getting to it all has it gone guys my name is TPJ if you enjoyed the video leave a like really helps out and if you like what you see more be sure to subscribe also guys I apologize about my voice yes I sound annoying as per usual when I've got the added elision of a cold I'm even more annoying so yes I apologize about that and if you hear me gasping for air in between sentences it's because I'm struggling to breathe but hey so yes like I said within this area right here guys and if you don't know how to get down here when you see off a river I'll put a video in the video description you need the pure billard knights medal which you get from the whiteface via request but yes again video link down below once you get that you can come to this area which is the best area in the game for farming ruins low level players high level players whatever because if you're a high level player you can use the relic sword and you can take out that entire hill guys with basically a single swing just like so boom boom if you're using the golden scarab you can get an absolute ton of ruins doing this if you're a low level player you can use a crossbow you can shoot that bird there you can see him right there guys won't look onto him because I think I might but yeah you can shoot him he runs off the map you run sit down stand my confidence repeat get like 13 between 13 and 18k ruins per kill um depending on what buffs you've got in regards to ruins like I said you want to be using the gold scarab if you have it you also want to be using these if you have it but hey let's kill myself because I don't want to um I want to try this in showcases to you guys without uh having any ruins on me so yeah so I'll show you the first method the one I showed uh showcased a couple days back and I quickly speed this up as well because obviously we don't want to be here all day so I've got no ruins on me and I just quickly speed this up guys I'll catch you back in a quick second so yep as you get up here guys you simply just double jump off has to be a double jump by the way don't just walk off has to be a double jump so just double jump and then swing your weapon and again I'll speed up the video until I get the ruins now a lot of people and uh it's important to know a lot of people will say that you don't get the ruins until you return to the grace point which is a lie although I pop up on my screen now sometimes it's 4k sometimes it's 7k you'll see it says I get 7k ruins but I actually get over 100 150k ruins and you'll see that now as you saw there guys it popped up 2000 odd ruins I actually got 136k which is just weird but yeah that's how it works basically that's the way in which you do it so from here guys then you just simply flash over back to the grace simple as that simple as that now you can keep going I believe you can get a second tick of ruins but hey it's up to you so you can see that I just got 136k ruins for doing that um so I'm gonna again pick them up first and then kill myself so I'm coming back for them after guys and I'll show you the new spot which in my opinion is much better much more efficient because there's less park going and less chances for you to fall off so yeah again guys you obviously need access to this area if you don't have access to this area you can't do this so guys you want to actually come to this grace point here now if you haven't got this grace point open yet you can do the easy method which is use your medal again simple as that if you use this you actually go to this area where we're going to showcase it and I'll showcase you guys the grace from this point because you will be loading back to the grace from this method of jumping off the map so if you run forward here you'll see that grace should be at the top of these stairs up there so let's just run there guys so you'll see the grace is right there so you want to activate that and that's the grace you will be returning to like I said and from here guys it's quite simple we park going up those rocks so here they can't play your horse there you have to come to the bottom of the steps so here just run past this uh creature there I don't know what it's called and then we run up this route just like so just like so and then you want to jump off to you right here jump around and there you go it is as simple as that now when you're up here guys you just want to come this way you don't want to jump off there if you jump off here by the way um you just fall to your death you want to come up here first so come up here just like so you can go even further up if you want to but here's fine to where this blood is just double jump off just like so and swing your weapon just like so and keep swinging guys and you'll see you get basically the same amount of wounds but it's much much easier to get up here much more efficient in the long running farming rooms and like I said if you're at the point still now um just killing the bird with an arrow so it runs off the map this is by far more efficient for you I mean if you can take out the whole hill if you're powerful enough to take out the whole hill nothing's going to beat that but if you ain't at that stage yet then this is definitely the one for you like I said as well make sure you're using the gold scarab the golden scarab if you're having in the gold pickled foul feet make sure you put them on too I'm not sure exactly how many get with them but yeah either way guys it's still it's still going to be decent I think it's like a 55 increase with the gold golden scarab and the foul feet on I can't confirm that I haven't really done the calculations myself just what I've seen people say but some people say so much different shit it's unbelievable yep it keeps ringing as per usual it's about the same time in regards to falling um I haven't I think there's one tick here there could be two ticks two rooms there we go just like so I got it said there I've got 367 or something like that it's still give me 130 and from here guys simply go back to the greatest point simple as that guys it really is and from here you can basically just run back down rinse and repeat people rinse and repeat and there we have it guys my opinion by far the best and quickest way to earn runes within this game especially for new players guys if you enjoyed the video leaving a like really helps out if you like what you see want to see more out of the ring be sure to subscribe and hopefully my beautiful people I will see you on that next one


People have been using herbs and spices for thousands of years. Generally, herbs come from the green leaves of plants or vegetables. Spices come from other parts of plants and trees. For example, cinnamon comes from the hard outer cover of cinnamon plants. The spice ginger comes from the part of the ginger plant that grows underground. Some herbs and spices are valued for their taste. They help to sharpen the taste of many foods. Others are chosen for their smell. Still others were used traditionally for health reasons. Get the full story and learn English at voaspecialenglish.com


Hey there, this is a quick video on how to find, recognize, and use OER content. We're going to cover some basic resources to locate OER, or at least resources where you can start to search for OER. And in general, OER resources are often organized by content or format. And what I mean by that, if you'll notice these two boxes here, there's one called content and one called tools. So in general, OER resources are organized by content. So for example, textbooks, images, worksheets, assignments may be available in different types of tools. And tools might include software and services that can be used in the creation, development, collaboration, delivery, search, and use of open learning content. So I'm going to be covering a few tools that you can use to find different kinds of OER content. We'll start with the open textbook library. This one is really helpful for locating textbooks that you might need, that you might be able to use for your course. You can browse by subject. You can also do a search in the search box in the top right. The nice thing about the open textbook library is that it does include reviews. So for example, I found this textbook for English language learning. It's an introduction to listening and speaking from 2017. And it's got 15 reviews and it's got four stars out of five. So that's one of the nice things about the open textbook library is that it does include reviews from fellow faculty that have tried to use this textbook or maybe reviewed it to see if they wanted to use the textbook. So it's helpful for getting some peer review of OER. Another tool is the OER digital commons. This one is a little bit broader than the open textbook library and that it includes other types of content such as whole courses, learning objects, things like that. A useful aspect of this tool is that you can narrow your search down by education level, which includes community college. So for example, here's a search results page from the OER commons. I did a search for Excel for business. On the left hand side, you can see different filters or facets, including education level. So I recommend checking out the search facets that are available in these different OER tools to see if you might be able to filter your search even more. So for example, if I wanted to look for community college or lower division resources, I could narrow my results by that in the OER commons. In addition to these tools, I actually adapted this video because I wanted to include some local resources. This is a original video was by Amy Hoffer in Oregon who does a lot of OER work in Oregon. And I basically adapted her video to include some local resources from Washington. So one resource that I really find helpful is the Open Washington OER resources repository. What's really helpful about this one is that you can narrow your search down by types of content. So for example, if you're looking for open images, if you're looking for open textbooks, course materials, video, audio, this helpfully breaks it down by those different content areas. So this is a great place to start. Another Washington local resource is the OER hub or Open Washington OER hub. This is useful if you want to find OER resources that have been created by peers in different colleges in Washington state. So this was put together by the State Board of Community and Technical Colleges, in particular, Boyong Che, who is the OER coordinator for the SBCTC. There are over 100 different projects organized by subject areas. So this is really helpful if you want to see something that was created by a fellow peer in Washington state. In addition to those Washington resources, I've also created a guide that has different OER tools, many of which we've already talked about. So this is a good place to start if you want to look for different types of tools out there. There are brief descriptions under each link on what types of OER resources that that particular tool searches.  There's a lot of different tools and resources out there. You can definitely ask a subject librarian. You can ask e-learning. You can also ask colleagues for OER recommendations. Definitely don't let yourself fall too far into that rabbit hole. Don't hesitate to ask for recommendations. Also, it may be difficult to find that perfect OER resource. The nice thing about OER and open licensing, it means that you can reuse, you can adapt different pieces from different works. So even if you don't find the perfect resource, you can take parts from others to create what you need. And you may also need to create something yourself. You can use other OERs as a model. So I wish you luck and definitely don't hesitate to reach out if you have questions.