That's right oil out here this morning. We sure do it's getting carried away with gold We got crude oil coming up at 10 30 Eastern time seems like they're already talking about it in the den They got so API had a big draw on crude at 7.5 declined million barrels EIA looking for a decline somewhere over on 2.5 You know before we get in there, right? Let's jump around on the Bloomberg if we could because sometimes you want to enter a Whisper number. Yeah, let's let's see what they're looking for here and then put our name into the hat So the crude oil so there we go They are looking for whether it's a whisper number in terms of what people like ourselves anybody talking about Or they get the survey but somewhere with a decline of three million barrels call right ballpark Okay, you folks in the den put a whisper number in there. We'll try to even it off We'll go from we got about a couple minutes. Yeah, we well we had two minutes on the dot Okay, make an entry. Good. So we're gonna jump back. We'll start start looking at the trades. We got two minutes We'll remember it. We'll see if they want so the expectation is the decline of about three million barrels We got crude trading at 59 22 the 11 a.m Expiration spreads we could have an option to buy and sell with exposure from $59. So about 22 cents away We'll jump into the last excuse me the noons 59 50 would be our pivot point. So about 30 cents away I was looking to see if we could get a 59 25 right that would be your idea here So before we set it up Would have exposure from 59 at the 8 a.m. To 30s and 59 as well Excuse me. So it looks like 59 is gonna be our best option if you want exposure bullish and bearish as in your 23 cents away Because that noon it's gonna set up at 59 50. That's almost identical, right? So in this situation you'd almost want to have a bullish or bearish bias because you're either gonna gain exposure from 59 Or you're gonna gain exposure from 59 50 either way you're getting about 25 cent Yes start to the heads up. All right. We have a guess. So let's go.  Where are we? There we are. We got 45 seconds. Okay, they're looking for minus 4.5 million. That's good And then see if you can he's looking for a Gasoline to yeah, but I think there'll be a drawing gasoline. Let's do the drawing gasoline Okay That in I think it is let's get our gas And what are we looking for for gas? I just said a draw. Okay. Well, that's good.  All right, okay Okay, 10 seconds to spare you get action in there perfect There's a well man quite a pop right? I mean that's where this that's where these spreads aren't exactly calibrated the price it's straight That because they're gonna open at the price that it's trading at as that spread becomes available throughout the day And you had oil trading at $59 for majority of it, which is why you have these exposures from 59 all the spread setting up, but if you're bullish not a bad trade and that even 59 to 62 You're getting in 26 cents above the market, but your losses are capped down at 59 you get a closer to 62 Not a bad trade when you talk about you have until 230 and you've had the volatility in oil Right, no doubt about that if you're directionally biased and you happen to hit it on the head as in your right Not a bad trade to have your losses capped 50 cents below where you're at and you get $2 and 50 cents above you Welcome back folks. Look at that. Do we have a number? We do have a number man. You've got crude oil inventories falling We should have went bigger go bigger go home man falling 12.7 9 million barrels gasoline inventories falling 996,000 That's what you can expect when you get almost a 13 million barrel build Draw yes, and you'd expected three man that price just jumped almost a full dollar and Pretty cool. That's quite a draw the one the one trade that we're possibly looking at right You were getting in at 59 50 in this the market was trading about 59 25 You're already up 33 34 dollars as this thing's ticking at 59 80 And it's gonna trade pretty close You're just marginal to the market right now as you're a solid almost dollar into the spread, but man That is quite a number and yeah 59 25 up to 59 90 in the span of a heartbeat And let's see if they got a Yeah, we'll see the full breakdown man But that that is quite a number and I imagine gasoline Inventories as well because that's on the bottom end of that range They might have been looking for a draw of only a couple hundred thousand to flat for gasoline Yeah, and then the XLE right now. It's up a buck 33 and That's stopping no Will be interesting here is that the the swing point on the XLE is 6378 and we're going right after it and it doesn't look like it's gonna be an ABC up But we'll see if I get the volume because that's 25.9 million there, okay, that we're going into or you only got 2.8 right now if we can look at some of so we started to check out some of The refinery they were talking about right yes Let's see. So where are we the top live? Yeah, because it was kind of cool how they were talking about when this dad actually is So here's the full breakdown to you have gasoline. Yeah decline of about a million barrels crude decline of 12.788 Gasoline the estimate was pretty much flat. I think and let's see where still to big drawing distill. Yeah distill missed by 2.4 That's pad 3-6.2 a big portion of that But it's it looks like it's everywhere man because even pushing Plus the distill it plus the pad 3 you're still not at 12.788 yet You know so I mean just constant all across the board So the refinery right yes in in Philadelphia So they do a good job of kind of talking about what you can expect here coming up to this report and So it's important to note that the weekly petroleum status report starts The period on Friday at 701 01 a.m. And ends at 701 a.m. The following Friday That means last week's report might not encompass all the fallout from the Philadelphia energy solutions explosion and fire And then to that point we might not see crude imports into the U.S. East Coast taking a hit in this week's report Because of that refinery fire the region's weekly average has been 794 barrels per day over the past five years So and it might not see any effects at all for a good few weeks if they manage to resell It's predominantly foreign crude imports to other refiners along the U.S. Eastern because you can picture these boats were already out there It's interesting, you know to redirect them It's a it's a great great direct sell to think about right and so the point being that those Those are gonna come those are already on the way And maybe you see an upsetting of the market in the next week or two as they re-evaluate all that And Yeah, so S&P energy index which was that spiking that's for sure Gasoline demand which almost got to 10 million barrels per day last week backs off considerably products applied down 452,000 barrels per day to 9.47 million in the week ended Let's just see we'll check back to see how the market's still moving So hanging up there 59 70 we'll check back in but quite a pop That's a strong bond and I am I mean this is where if whoa oil ever gets back to where we were or lower Then what's going on in that market exactly a draw like that that would be just so cool very weak If it was ever able to I don't I don't I would be surprised Surprised often well the cool the cool thing is that that's where the divergence would be huge Which is you know because that shouldn't happen. It's just common sense if oil can't trade higher when you have EIA of 13 million barrel draw. Yeah, then good luck to the bulls because that's a tough one. Totally Welcome back folks doubt I was up 63 NAS except 55 SAPs are up six and a half and that little contract is hanging tough The first move is the one that just kind of hanging there right 59 70 We're up about 50 cents from that price point You could have thought that it was gonna go a little bit higher man considering we got 70 cents a movement almost in the span of a heartbeat. Yeah, but nonetheless, we're quite a draw. We're looking Yeah, 12.7 million barrel draw We'll see if it can hit $60. We'll see


Good morning, everybody. Andrea here. I want to show you guys inside the Quality Assurance Study Guide. It is updated one to two times a year depending. And if you're, if you've registered for the course already, don't you worry you get full access for the entire year, whenever the updates do come up so when you log in, you'll likely see something that looks like this you want to click on the three lines up at the top. And for today so not everything is updated yet depending on when you're watching the video the updates will be done August 23 today is August 17, but what has been updated today is community health emergency protocols and the jurisprudence record keeping and the ethics unit. I'm currently working on infection prevention and control. There has been some new videos uploaded today but there's going to be more within the next few days, and then the rest is going to be updated as well. So it takes about a week to go through all of the updates but feel free to study now. All of this you do still have to know even if it's considered not updated. The old material in the course has been there since the beginning of the year so it's not old it's still applicable, but some files I'm just changing around some files are being changed a bit. So definitely still log in and start studying, especially if you're preparing to take the September exam that is coming up very soon. One of the new features I have added is I am adding a quiz. One or two quizzes depending on the subject type. So you will see a question mark I can zoom in for you guys here. To the left hand side you'll see a question mark where there's a quiz. You click on the quiz and the quiz will show up here. I'm just not logged in that's why it's telling me it's not available, but you'll see everything so for example when you click on something. It will pop up. If it's a PowerPoint you just have to click download file there's going to be several PowerPoints in each unit, and videos are coming soon where I'll be going through the PowerPoints and explaining them to you. Kind of like a lecture teaching that type of thing.  You'll have both different ways to do things so clearly that just takes a little bit of extra time. So the videos will likely be added towards the end of this week early next week. If you guys have any questions let me know I'll leave the link for you guys down below to sign up. It's currently on sale until September. I always offer the sale price as an incentive to sign up early. When September hits the price will be going up so now is definitely the time and you have full access to everything for one full year so you can take your time. If you guys have any questions please let me know. Thank you for watching. Click like to the video if you haven't yet because that does help me in my channel. Make sure to click subscribe and I will talk to you guys very soon. See you later.


The Internet. The Inet. The Net. You've heard of it. You've read about it. You may have even seen parts of it. But what is it? Think of the Internet as a network of communication networks. Doesn't help enough? Let's get transportation specific then. Think of the Internet as a vast communications network similar to the U.S. interstate highway system. You can access our highway system from a variety of points. There are different on and off ramps. There are toll roads and freeways. Smaller roads and intermodal connections link into the highway system. All types of vehicles use the system. In essence, it's a vast dispersed transportation network. The Internet is designed in a similar fashion. You access the Internet from a variety of points and through a variety of connections. Perhaps via your home computer with an online service provider or perhaps at work through your local area network. You use a variety of Internet tools to access the information on the system. You may link to basic text files or spend your time perusing the high end of the Internet complete with multimedia video and sound images. The choice is yours. But the network is your communications link to data and information and much of that information is transportation related. You're saying to yourself, well now I understand this Internet concept a little better but what are the real benefits to me? On the most basic terms, the Internet affords you rapid, relatively inexpensive and increasingly user friendly access to the vast amounts of data, information and people worldwide. More explicitly, with the Internet you can exchange information quickly and conveniently. You can access expert individuals in thousands of fields. You can receive regular updates on topics of interest to you. You can build electronic teams across geographic distance. You can gain access to a wide variety of information and data and other users can similarly access your files. You can translate and transfer data for your personal and business use. And the list continues. Sound amazing? It is. But let's get specific. Variety of Internet tools have been developed to help your entry into the world of cyberspace and make it more successful. Electronic mail is the most basic and most utilized Internet tool. Indeed, electronic mail may very well be to the 21st century what telephones were to the 20th. What's so great about email? Well, to begin with, it's an easy, fast and inexpensive way to communicate with people around the world and the concept behind electronic mail is easy to understand. In fact, it's much like sending traditional mail. You compose a message, a letter, you indicate the to and from addresses and then send it, drop it in the Internet mailbox. However, unlike traditional mail, email is almost always fasting, often taking only seconds and is often cheaper than regular mail or even a phone call. BTS has established an email address for customer feedback and comments on our products and services. You can reach us via Internet email at info at bts.gov. A little clarification here. Remember, when you want to send and receive Internet email, you need Internet access. You may already have email capability within your office on your local area network or LAN, but this alone does not support Internet email. To send and receive email from the 30 million plus users of the net requires an Internet connection. Now, what if you wanted to get some information on, let's say, congestion management, for example?  You've got a deadline and need immediate access. What can you do? Well, if that computer with your congestion management data can be accessed via an Internet tool called FTP or File Transfer Protocol, access to this data may only be a few keystrokes away. Well, how? Well, File Transfer Protocol is an Internet tool which gives you the ability to send and receive files from one Internet connected computer to another. Once you find the information you're interested in, FTP allows you to transfer it back to your individual computer for personal use. While FTP is an important tool that allows you to transfer files across the Internet, it doesn't let you easily browse a site to see what type of information and data is available. Gopher is another Internet tool that was designed to do just that. In Gopher space, as it's called, data and information are organized in broad categories. You literally burrow through hierarchies of menus with increasing specificity until you reach your level of interest. Gopher is easy to navigate and easy to browse. It also allows you to select and view a file on demand. Watch as we burrow through the BTS Gopher site available at the address gopher.bts.gov to access a file on traffic safety data. With just a few points and clicks, you're already there at the main gopher screen for BTS. As you can see, there's a list of folders. These contain additional information on the particular subject. The World Wide Web, or Web as it's affectionately called, is perhaps the most exciting and most popular tool that has become recently available on the Internet, because it's easily the most user-friendly of all the Internet tools. Think of the Web as something spun with a variety of interconnected linkages and paths to follow. These paths are called hyperlinks and seamlessly connect you to additional data and information of your choosing, just by pointing and clicking. The Web puts you in the control seat and lets you interactively decide how to access information. And one of the more exciting aspects of the Web is its support of multimedia. On the Web, you can just as easily access data and information by a sound, image, video, and graphics, as you can text. Let's see what we can find at the Bureau of Transportation Statistics World Wide Web site. The address is www.bts.gov. The first page of any Web site is called its Home Page. This is the BTS Home Page. As you can see, this page provides an overview of the information and data that can be found at the BTS site. You can point and click on any of the main buttons to go to that area. Or you can read the related text and point and click on the highlighted words or phrases and receive additional information on that subject. Now let's demonstrate a few of the BTS products that you can find at our World Wide Web, Gopher, and FTP sites. BTS is about more than just tables and graphs. We have to answer the basic questions as the transportation system in its consequences is getting better or worse. What do we mean by better or worse? And why are conditions changing? We summarize her findings in the Transportation Statistics Annual Report and in other publications, which we make available in traditional paper form as well as in electronic form. Internet is a way we can get the electronic forms to you, our readers, as well as to share information and insights with the people who help us perform the analysis. The State and Metropolitan Analysis for Regional Transportation, the SMART Project, is really an attempt to create an information infrastructure for transportation planners around the country. The SMART Project really is just a series of boxes at this point. There are electronic boxes into which we've plugged reports and data sets that were delivered to us from transportation planners around the country. Those reports are the first time that anyone has really tried to share information from one small metropolitan planning organization to another metropolitan planning organization elsewhere in the country in any organized, systematic way over the Internet. The BTS Office of Geographic Information Services has three major missions. The first is to produce and maintain spatial data related to transportation. The second is to use these data in conjunction with GIS technology to conduct analyses in support of DOT policy deliberations. Thirdly, BTS will produce products such as maps, statistics, and the results of the analyses that it conducts. With the Internet, this vast array of products will be available to all BTS customers. As you've seen, the Internet is filled with valuable information resources, many of them transportation-specific. To get access to these resources, you must have an Internet connection. But what do you need to establish a connection? Here's a starter list. You'll need a computer, Mac or PC, it doesn't matter. All will hook successfully into the Internet. And of course, a motor. To access the Internet, you need to establish an account with an Internet service provider. Your service provider gives you the needed link or connection into the network. You'll need some type of specialized Internet software. The needed type will depend on the Internet service provider and the connection option you choose. Patience and a sense of humor will go a long way when you encounter your first glitches on the Internet. The technology is still evolving, but the vast array of data and information you'll find makes your effort worthwhile. Let's talk a bit now about your specific connection options. Internet service providers offer several different types of connections, and these connection options are changing rapidly. That said, current connection options can basically be broken down into three main categories, online services, SLIP slash PPP, and direct access. You should research these options and the Internet service providers in your area to see which best meets your needs. Here's a checklist of items to consider when making your decision. Speed. Your connection speed will determine how quickly you get access to the Internet resources you're searching for. Technical support. Determine what level of technical support your Internet service provider will offer you. Do they offer extensive user help, or once your computer is connected, are you basically on your own? Price. Price can be a critical factor. Does your service provider charge a flat rate or buy hour or a minute? If you have a slow connection speed, for instance, and are being charged by the hour, charges can add up fast when you're trying to download files. User-friendliness. How user-friendly is your software interface? Is it a graphical point-and-click interface or text-based? How user-friendly is your installation of this software? If you like to tinker with computer code, this may not be much of a concern. For others, it could be a priority. Level of access. What level of access to the Internet tools do you want? Will e-mail suffice or do you want access to the full range of Internet tools, including FTP, Gopher, and World Wide Web? Do you want access that will support the multimedia offerings of the Internet? Service providers have different options and not all offer full access to all the Internet tools. With these factors as our basic checklist, let's look at the specific connection options Internet service providers are now offering. Online services. Companies such as Prodigy, Compusr, Delphi, and America Online started out by offering value-added online information services to their customers. Recently, they also began providing gateway access to the Internet. The online services began their Internet offerings with e-mail and have just started providing Gopher and World Wide Web. The advantages of online services are convenient access, full technical support, and user-friendly software. The disadvantages are slow connection speed, expensive hourly rates, and limited access to all Internet tools. Slip Slash PPP. With an online service, you're limited to what your Internet service provider offers when accessing the Internet. If you want access to the full range of Internet tools and offerings, you might consider establishing a Slip Slash PPP connection. With this, your service provider lets you directly connect to the Internet. Your computer is no longer just a display terminal. Instead, it is directly hooked to the net. This means you can use the full range of Internet tools, including multimedia. You can use these tools simultaneously and at a more rapid rate. If you think that you or your organization will be a frequent Internet user, Slip Slash PPP may be the option for you. The advantages of this option are full access to Internet tools, declining costs, user-friendly software interface, and faster rates of transmission. The disadvantages are the level of technical support varies and software installations are often difficult. Direct access or a permanent connection offers the fastest, most comprehensive, and most flexible Internet access. But watch out, it's also the most expensive. Because of its cost, it generally is only a viable option for large organizations. A direct access link to the Internet is usually through a leased phone line. The organization's local area network, or LAN, is then connected to the computer or workstation identified as the Internet node. Now, this option has full access to Internet tools, a fast rate of transmission, good technical support, and user-friendly interfaces. However, it's expensive, often prohibitive itself. The Internet, with its lure of electronic communication and rapid access to people and vast amounts of data and information, is providing an essential gateway to the information age of the 21st century. The Bureau of Transportation Statistics challenges you to take advantage of the resources this new form of communication affords. We're here to assist you in your early steps of Internet exploration. The world of transportation information is yours for the taking.


Venge, another fantastic win against Sebastian Mazze, how did the game go? I think after opening, I think what is just slightly better and even have a clearly advantage. And I feel my position is so comfortable and with development. And then, you know, sudden he decided to make a sacrifice, but maybe it's premature and finally, it's nothing and I won't. Right, and tell us a little bit about the opening. Was it part of your preparation? What happened today on the board? Because it seemed very, very clean from the start. Well, it's not my preparation today, but previously I've been watching sort of position and I like white and so I decided to play this. And I think 9-Db5 is a very typical move in sort of position. Right, now tomorrow is the last round. You've had a fantastic tournament so far. What is going to be the strategy for tomorrow? Give us some insights. It depends who is my opponent. If he is, okay, he is very strong, I think I would just fight for a draw. Right, and anyone in specific that you would like to play tomorrow? Well, not exactly. I'll play black, so okay, I'll just try to play solid. And you're obviously very happy with the way your quality of your game and the way things have gone so far for you? Yes, I'm satisfied about that. Alright, we wish you all the best for tomorrow and hope to have you back in the studio after the game. Thank you so much. Thank you, Anjan.


Arthur Thomas Corley who documented the daily habits of 233 wealthy people and 128 poor people for 5 years serves a person who is unborn wealthy can make lifestyle changes that increases their chance of becoming financially successful. This finding is good news because it shows that you don't have to come from a wealthy home for you to be rich. You only need to change some habits. In this video, I will share with you 9 things that rich people choose to do that poor people don't. 1. Set goals Have you ever had to think of how the world would be if there were no such thing as the dead? Do you think that people will put more effort into reaching their dreams? Surprisingly, the consciousness of the fact that everyone will die is what pushes most men to work towards creating a legacy for themselves. That is how it is with visions. In one of his writings, Napoleon Hill said, a goal is a dream with a deadline. When there is no deadline for your aspirations, you tend to become too lazy to exert much strength towards achieving them. One distinct difference between the poor and the rich is that the rich write down their goals so that they will be motivated enough to fulfill their visions. Whereas the poor allow their dreams remaining in their heads as mere fantasies. 2. Lifelong learning The reason why many educated people are poor today is that they focus on their profession and refuse to look towards whatever does not point to that direction. The belief system of the poor is that being an expert in your area of specialization will guarantee your job security. The rich, however, are insatiable learners. They do not just focus on their fields alone. They learn about personal development, finances, business and even politics. Hence, Paul to the Jones, self-made billionaire, entrepreneur, investor and philanthropist, affirmed intellectual capital will always trump financial capital, knowledge the new currency, whether through reading, surfing of networking, the wealthy individuals are always out to get it. 3. Declottering Research has proven that your environment plays a significant role in your productivity. Indeed, rich people are wealthy because they are more productive. Well, it does not matter if they don't work as hard as the poor people. The point is that they are more productive and have something to show for it. Money. Successful individuals understand the importance of staying organized.  Apart from the fact that it can't disorganize you, clutter directly causes you to lose money. Clutter is said to be a financial sin and the rich always avoid it. 4. Using Affirmations If you open up the brain of many poor people, you will be shocked at the kind of negative thoughts in there. If you desire wealth, your thoughts must be that of riches. Only consciously thinking about abundance will not attract it. It has to be stuck to your subconscious mind. We can achieve almost anything when our innermost thoughts match our conscious thoughts. One scientifically proven way by which we can get our subconscious to align with our conscious thought is by making affirmations. Repeating affirmations help change the subconscious thought pattern. Wealthy people understand this and so use it. However, the lips of four people will never lack lament and negativity about their lives and that of others. 5. Responding to Messages One would expect that due to their busy schedules, wealthy individuals will most likely not respond to messages and emails but quite surprisingly, they are even more committed to giving quick response than poor ones. As a matter of fact, research shows that 80% of wealthy people also go as far as sending birthday wishes to friends, families, colleagues and even clients, something many poor people fail to do. One could attribute this attitude of affluence to the fact that they leave an organized life and create to-do lists. They schedule a time for even the tiniest of tasks so when they endogenous it, they will be fully present. Rich people do not just scroll through their emails in the middle of work, they allocate time to check their inboxes. 6. Peeking Investments Above Physical Cash Those who are called wealthy do not save. They invest. Indeed, saving money is a sensitive task. What is more beautiful is having your money create more wealth for you. Wealthy folks have mastered the skill or discipline and the ability to delay gratification. Best-selling author, Robert Kiyosaki, once wrote, �People don�t like the idea of thinking long term. Many are desperately seeking short-term answers because they have money problems to be solved today.� Well, the truth is that everyone has money problems every day. But unlike the miserable, the rich do not think only about solving now, they think about creating a channel that will solve the problems to come for the rest of their lives. Thus, while the poor man will jump at having money, the rich man will rather have investments. He understands that cash at hand will soon get wasted, but a secure investment will last for a lifetime. 7. Paying Themselves First Do you know what rich do first when they receive their earnings? They pay themselves. The philosophy of �pay yourself first� was first derived from George Clayson�s book, The Richest Man in Babylon, which was written over a century ago. According to the book, anyone who seeks to be fruitful must keep a tenth of each of his earnings. Robert Kiyosaki�s rich dad, poor dad, further explains this principle, �People who choose to pay themselves first allocate money to the asset column of their balance sheet before they have paid their monthly expenses. Essentially, you set aside a specific amount of money right of the bat and then leave on what�s left over. And that�s how wealth grows. Nowadays, with the improvement of technology, many wealthy people have an automated system that takes the money out of their bank accounts to a separate one. 8. Buy Quality Things There is a saying that goes, �Buy cheap, buy twice. So buying inferior things seems like a wise decision to make. Wait until you visit the repairer every other day. Before purchasing items, wealthy people take their time to look for the ones that will be favorable to them. However, poor individuals are so inclined to impulse buying, they don�t even think things through before making purchases. The few times they think, their thoughts are often like, �Oh, I will just get the cheap item because it costs only a few bucks. I can�t afford to get the quality one. Or, well, they don�t all serve the same purpose. In fact, the cheap ones will probably last more than the so-called quality ones. The truth is, it is advisable to pay on installments or wait till you have the money for the quality ones, rather than buy inferior products. 9. Keep Your Mouth Shots Have you heard of the saying, �The empty drum makes the loudest noise? I bet you have.� This seven-word statement is the story of many poor people. Apart from bragging about wealth that they have not yet acquired, miserable individuals are fond of gossiping. In his book, the 360-degree leader, thought leader and author John Maxwell wrote, �Great people talk about wealth. Great people talk about ideas. Ordinary people talk about themselves. And small people talk about others.� While the individuals focus their attention on making more money, they barely have the leisure to talk about others or what they have formerly acquired. Small people are also of the habit of spilling out their plans before they materialize. But prosperous individuals keep their mouths shut. According to Dave Ramsey, 84% of wealthy individuals believe that good habits create opportunity luck. Good habits create opportunity luck, as opposed to 4% of the poor. You want to be wealthy? Learn the habits of the rich.


Look around you. There are so many paper products from the sheets of paper that you write on, to the pages of your textbook, to ink cartons, to newspapers, to certain grocery bags, to cardboard boxes, and the list continues. The important fact here is that paper is an essential part of our lives. You may know that paper usually comes from trees. They must first be chopped down and then subjected to an industrial process called pulping, which removes lignin, the polymer that gives trees their strong hard structure. Obviously, the paper production process has led to mass deforestation. The main issue here is that the trees are not being replanted, or if they are being replanted, they will not grow fast enough to replace the trees that are being cut. This is a serious environmental issue because it destroys habitats, disrupts food chains, and food webs is a severe eyesore and indirectly leads to increased carbon dioxide content in the atmosphere. It could also lead to erosion of hillsides with the consequence of flooding. An obvious solution is to recycle these paper products. In this lesson, we will learn about recycling paper and the advantages and disadvantages to this industrial process. Paper is in fact layers of cross-linked cellulose fibers. Recall that cellulose is a polymer of glucose monomer units. If you tear a piece of paper and look closely, you will see fine hairs sticking out. These fine hairs are cellulose fibers. When paper products are recycled, these cellulose fibers are merely pulled apart and rearranged into new paper products. In some countries, paper recycling is highly encouraged by having specialized waste containers just for paper waste. The paper waste is then collected and separated according to their properties. Sheets of paper are recycled with other sheets of paper, and cardboard boxes are recycled with other cardboard boxes. Now, right before the paper can be recycled, any ink needs to be removed. This process is called de-inking. Most inks are petroleum-based inks which are derived from crude oil products and can be difficult to remove. Currently, in development, are soy-based inks which are derived from a renewable resource and makes it easier for the paper to be de-inked. Metal parts such as staples and paper clips need to be removed with a magnet, and glues are removed with a chemical wash. Bleach is sometimes added to whiten the slurry, and therefore the resulting paper product will be brighter. The cellulose fibers in the slurry are mixed with new pulp, and then allowed to settle on a gauze and rolled to form the new sheets of paper. This step also removes any excess water from the slurry before it is air dried. The main disadvantage with recycling paper is that it can only be done a few times. Recycled paper is usually used to make kitchen rolls, toilet paper, and packaging materials. Each time a paper product is recycled, the cellulose fibers become shorter, thereby rendering the recycled paper product a little bit less useful than the original. However, this can be used for another purpose. Can you remember what cellulase is? Hint, it is an enzyme. Please pause the lesson to think about this and resume when you are ready. Cellulase is the enzyme that breaks cellulose apart into its glucose monomers. Currently, the industrial usage of cellulase is to break down cellulose into glucose. The glucose obtained can then be fermented by certain bacteria to produce ethanol, which can then be used as a biofuel. In summary, recycling paper products help to reduce the rate of deforestation and consumes a lot less energy. Although paper can only be recycled a few times, the cellulose fibers can be broken apart into glucose monomers, which can then be used for other environmentally friendly applications.


So if you were listening carefully on Friday morning, I told you you have a special treat to open up the plenary tonight. And that is, there is really nobody elected to office whoever stuck his neck out so far and did so much to transform the debate about the drug war and drug policy in America. And that is the former mayor of Baltimore, Kurt Schmoke. Hey, you know, I explained to you on Friday why we're renaming the LaDen Award to the Kurt Schmoke Award. And it's gonna be going from that, you know, henceforth. But I gotta tell you back in the late 80s when I was teaching at Princeton and starting to write and speak and then this elected official just stood up at a conference of mayors. And as I told you, threw his notes away and said, this drug war makes no sense. And he didn't just say it once. He continued saying it through 12 years in office. He joined the boards of this organization. Then he became the dean at Howard University Law School. He kept speaking out. He's now the president of the University of Baltimore. He is my friend. He is my ally. He has been an extraordinary leader for this movement and in this country, Kurt Schmoke, Kurt, please come on up. Thank you, Ethan. Thank you all very much. Thank you. Well, thank you very much. This is an overly generous introduction. I know that I ask Ethan to simply say that I'm the only elected official who read his article and then repeated it somewhere. But I've been a disciple of Ethan Natelman for a long time, along with Deborah Small, who I wanted to stand up and applaud. But I really do want to thank each and every one of you for joining this outstanding conference. It does my heart good to know that it continues to grow. I see people who are brothers and sisters from around the world who are engaged in a wonderful, wonderful fight to make some improvement, to bring sense and sensibility and justice to this fight. For me, it seems like I was talking to Cassandra and I told her that I'm almost an historical figure now. I've been around so long that it was 1988 that I went to that conference that Ethan was talking about. And it was a conference, a joint conference, of police officers and mayors from around the country. And what triggered a change in my mind, I had been a prosecutor before being mayor and a good friend of mine named Marty Ward was an officer who was working in undercover police operation wearing a body wire and he happened to be killed by the person who he was there to arrest. And it dawned on me at that time that at least in our community we had more people who were hooked on drug money than hooked on drugs. And it seemed to me that we weren't going to make improvements in our community until we found a way to take the profit out of distributing drugs at the street level and that led more and more thinking and then fortunately read Ethan's work and was able to bring some sense to my inchoate ideas. I heard that you listened to Dan Moerheim, a delegate Dan Moerheim at the conference. He is continuing the battle in our state. Just recently at Johns Hopkins we had a conference and we looked at a number of issues many of which you have considered over the last few days decriminalization, legalization, medicated assisted treatment, needle exchange and safe injection facilities, a sentencing and reentry and then treatment on demand. And the thing that was so interesting and I'm sure you found in your conference is that when we identified examples of progress being made we could see it in cities, in states, in countries so it was just coming together and collaborating on an international basis that we're able to move this thing forward. This is not just a local problem or national problem as we all know, this is an international problem. If we can solve it internationally we will save a lot of lives and help communities around the world. So I just came by to say thank you. I appreciate the award being named for me though. I really beg the Ethan, let me be hyphenated with Lydane but it just didn't work out that way. But keep going and stay optimistic. I just remember that in just getting needle exchange back in the 80s in Baltimore nobody said that we could get it done and yet we persisted and we brought friends in. In fact we brought friends in from Rotterdam who helped us out a great deal in persuading our legislature, we're gonna make progress, we're gonna win on this and we're gonna win not just because there's a narrow group of advocates, we're gonna win because people will understand that this is all about justice, this is about fairness, this is about bringing science, not politics to the war and drugs and hopefully the best days of our countries are still ahead of us. Thank you all very much.


How containers, microservices, and open source software are redefining cloud computing. I'm Mark Hinkel. I work at the Linux Foundation. I have for about two weeks now, but my background is, before that I worked for the last five years in cloud computing, so I worked for a company called cloud.com. We had a product called Apache Cloud Stack. When I was at Citrix, I worked on, I was on the board of ZenProject, the Zen hypervisor, and our product was on server, which we open sourced, and spent a lot of time working with Apache, the open daylight, which is a SDN controller that is a collaborative project Linux Foundation, and that's where I am today. So while I said VP of marketing, I'm a committer in Apache Cloud Stack, and I spend a lot of time with these technologies. I'm also sort of opinionated, so I will try and give you a good, like, lay of the land and let you make your own choices, but keep in mind these slides are stuff that I've worked on, so I sort of have a, you know, propensity towards these technologies. I did put these slides up on SlideShare. If you find them interesting and want to get any of the links or anything, I usually try and put speaker's notes in my talks with links to the stuff I talk about, so you can go do your own research and find that stuff. So I've been doing cloud talks for the last five years, and during that time, I've given the same talk probably every month for five years that it's updated, so it's sort of like that evolution of dance video. You sort of start out slow, and I am not going to recreate that video because nobody wants to see that, but we'll sort of talk about the evolution of cloud. So back when I used to give these talks, this is the diagram I'd always start with. I'd be like, you know, we have this thing, it's called the cloud, and we have this public cloud, and then we, that's host, cloud infrastructure hosted in other people's hardware, and then I have the private cloud, and that's hosted on our own hardware, and then in our own data centers, and then we have this hybrid cloud, which transverses the firewall, and we'd spend the first like 15 minutes talking about that. That's not really the case anymore. I mean, I don't think anybody, most people get that now. Like how many people here use Amazon EC2, Google, Compute, Azure? All right, yeah. How many people would identify as being a system administrator or developer? I won't do the Balmer developers, developers, developers either, but that's good. How about just IT support or generalist kind of people, networking people? That sort of helps me in the way I talk about things. So this is what I talked about five years ago. I was, everybody was cloud, cloud, cloud, cloud, cloud. And this is sort of what's happened over those years, and as I am getting old with my progressive lenses, I hopefully will be able to read the tiny little print, but the thing I think is interesting is this whole cloud thing started way before we started talking about cloud. And I really think that in the mid-90s, they had a movement around service-oriented architecture, and so, so, so was a big buzzword. And then later on the service-oriented architecture movement sort of faded a little bit, but we're going to talk about that a little later. The thing that really kicked this off was this whole cloud rage was Amazon, and their launch of EC2 back in 2006. So that was really sort of the landmark moment when they started to host compute infrastructure, and it was in a very different way than what we did for virtual hosting because it was elastic. And then all of a sudden, 2010 came around and we started seeing these knockoffs of Amazon from open source, open stack was launched, Eucalyptus cloud stack was launched as open source, and we started seeing these open source platforms, so like Linux to the Solaris era. Then 2013, a company called DuckCloud was a platform as a service provider and that cloud launched, we launched themselves as Docker, and now every time you go to a conference, we hear everybody going Docker, Docker, Docker, Docker, Docker, Docker, Docker. How many people here use containers? Docker, cool, which I think is cool. I'm not being pejorative, but I just think that people are gaga over containers right now for many reasons. Then 2014, we started seeing the rise of Paz, so Cloud Foundry, and actually Pivotal launched that as a foundation under the Linux foundation and put it in a governance model that allows everybody to participate equally. Then Google did the same thing with Kubernetes and did the Cloud-native foundation. Now, I'll point out I've been given this slide for at least six months, and now I'm at the Linux foundation, so I wasn't really realizing I was hocking all their collaborative projects, but it sort of makes sense why I ended up there. So we're in what I call the era of cloud abundance. We got cloud choices, we got competitively priced, we have Paz that's hosted, we have Paz we can run in our data centers, we have containers, we got microservices, we got all this stuff, and what I'm trying to do is take us in this little journey from what we have, how it's evolved, and where we're going. So in this area of cloud abundance, you can see this is some analyst chart, but basically the amount of cloud that people buy every year is increasing by 24%, and you can sort of see a breakdown that a platform as a service has one of the highest growth rates, and we're going to talk about that in a little while. But before we do that, I want to talk about what we did in the past, because if you don't learn from history, you're doomed to repeat it. So let's talk about Cloud 1.0. So this is Amazon is launched, Google is launched, and we have all these what I call copycat clouds, of which I was one of them. So copycat clouds were the idea that we wanted to bring Amazon into our own data center. So this is actually, I was involved in the first press release is the cloud stack was Amazon style clouds. Then you had eucalyptus. Eucalyptus is owned by HP, but it was one of the first open source clouds to launch, and their claim to fame was they wanted to keep as close to 100% fidelity to the Amazon API so that all your tools would work. There's another one back in 2012 where HP was talking about their HP cloud compute and undercutting Amazon. That was an open stack based cloud, I believe. But is anybody familiar with the Netflix open source program? It's a pretty interesting program. It's a bunch of tooling from Netflix operations that they use to run stuff in the cloud. And they scale out their business on Amazon, which I find is interesting because a lot of they have some hyper elite operations folks, they really have that DevOps culture. They're at the forefront of operations and they use Amazon and the way that they scale out is they build on top of Amazon and then they go into new geographies. It's dependent on whether Amazon has a good enough footprint for them to deliver their services there. So the guy who used to be the architect for Netflix cloud was a guy called Adrian Cockcroft. Has anybody seen him speak or he speaks at a lot of cloud conferences, a lot of open source conferences. And now he's a technical advisor at Battery Ventures. But he's a really smart guy and he said that people would ask, well, why aren't you doing it on Google and Amazon? He said, well, using multiple clouds is like Ramanriding. So that's Ramanriding where you stand on one horse. So having multiple clouds and trying to run your operations across the cloud is really, really difficult. It's really hard to balance and eventually something falls down. So he said we decided to go with Amazon and it made things a lot easier. And he had looked at things like Cloud Stack and Eucalyptus. But their choice was to scale out everything they could on Amazon because they didn't want to have this Ramanriding problem. Also in this Cloud 1.0, people were very, very particular about the silos of how they define cloud. So they're like, is it a public cloud? Is it a private cloud? Is it a hybrid cloud? And what that meant? So that sort of, if you read information week or info world or one of the trades every week, they would have private cloud round up and public cloud round up. And that's really, I don't think, a good thing. And we're sort of getting past that in what I call the sort of Cloud 1.5 era. And this is what happens in the Cloud 1.5 era. There's lots of people like Twitter's and Facebook's and Netflix and PayPal's that are really interested in the cloud and they're building the infrastructure. And those people are adopting it, but people that were sort of enterprise operations were not really getting on the bus as quickly as them. And then all of a sudden, they're like, hey, it's not just for the .com people, it's for everybody, and we're really missing out. So all of a sudden, probably like 2010, everybody's scrambling for their cloud strategy. 2010, maybe 2013, I think, is where it's started to peak and take off. So Enterprise IT started saying, hey, I've got to play catch up here. And this graph is from a guy from Simon Worldly, a analyst from CSC Corporation, a blogger, a really smart, really opinionated guy, which used to be the vice president of Cloud at Canonical before he took that gig. Now the difference between Cloud and like in Cloud 1.0 area, a lot of people use the tool called RightScale. Anybody here used RightScale in the past? And I mean, RightScale took off because it was one of the few tools that you could use to manage cloud workloads effectively. And it was a hosted tool. Now in this 1.5-er in the last few years, we just see a ton of new tooling come out that's really interesting. So things like in configuration management, we had Puppet, but now you have Chef and Puppet. You have Ansible and SaltStock that are sort of helping to solve those same kind of automation and configuration problems. Anybody here know HashiCorp? They do vault and vagrant and a million other things that are really cool and awesome. You have Docker out there now. You have a ton of Manage IQ, which is a Cloud monitoring that's Red Hat sponsored project.  So we're in this era where the tools that we have today are becoming as useful as the tools that people used to spend millions and millions of dollars for back in the 90s. So back in the days of the Tivoli and the BMC, which are still around, but not as cheap as we would like, I should say. And the other thing that I think is the catalyst for this Cloud 2.0 or 1.5 era is sort of this change in culture. So how many people here have, did anybody go to DevOps Day this week? Anybody here, how many people here have heard the word DevOps before? I just like to make sure. So just this cultural change that sort of reverses the conventional thinking on operations, which my wife works at a very large conservative pharma company in IT project management. They do releases once a month, and they plan, and they're going through ITIL, and they have processes over processes, and they have silos of people in development and operations. And she's the person that bridges operations to develop. Like they don't really talk together, sort of these old school kind of ways to manage IT. Now you guys know who the guy in the middle is? His name is Patrick Dubois. Patrick Dubois is the guy who started the DevOps movement, and is a real low-key guy who lives outside of Brussels and Belgium, and sort of started the movement. Probably hasn't made a dime off of DevOps, but it's one of the biggest transformative movements in IT as long as I've been around. Anybody here read The Phoenix Project? So Gene Kim, anybody who ever used Tripwire, Gene Kim was the guy who started Tripwire, and now he is a sort of evangelist around IT trends and sort of has the mission to help improve the lives of people in IT is his stated goal. And he wrote this book, The Phoenix Project, which is actually a story that sort of encapsulates the ideas behind DevOps in a real-life fictional kind of situation. And then you have people that are set in the model, and I mentioned earlier, Netflix. So you have this change in culture. You've got tools, and you've got an abundance of cloud stuff. Then you have this one final thing, which I call the cloud industry shakeout. So if we talked about public cloud, these days the way I look at it is there's only three vendors in what is truly the generic public cloud. And I'd say that's Amazon, Google, and Microsoft. And what I mean by that public cloud is they have a global footprint at massive scale, and they move really fast. Then you have this other sort of tier. And actually, I've recently seen that CenturyLink was talking about selling off their data center assets. So I'm not sure how we'll qualify that anymore. But the idea is that the people that own the pipes, so the telecom bandwidth providers, the data pipes, the level 3s, people like that, are sort of offer these managed services. Because not only do they have the cloud, but they have the end-to-end network. A lot of people are looking at they can get end-to-end security in SLA from not only their compute and storage, but also the pipes to carry it back and forth. They are the premium over what you'd pay at Amazon. Amazon has tons and tons of services in a huge ecosystem. These managed service providers offer something above and beyond their premium service. And finally, I have what I call the SP and the SI cloud. So SoftLayer is IBM. I think that's the best example. And they have system integrator capabilities. And they're surprise-prost.  I have HP on there, but it seems like every time I check out HP, it's not clear whether they're all in on their own cloud, or if they're going to be an arms deal or to everyone. So that's where I think SoftLayer is one of the, is a large example of these SPSI clouds. There's people in Canada that I think do a real good job called cloud.ca. They have a public cloud, but they have a really great services shop integration. That kind of cloud, I think, is interesting. And they have built it for you. And then finally, there's another one in the Netherlands I really like. And the other reason I like them is because they use cloud stack, but they're Schubert Phyllis. And they're in Amsterdam, and they do a lot of custom built clouds, and one clouds for the customers. They're services offering, and they lease the lines. I think that's interesting. So those things are the shake out. And then this final thing that is like the miracle that's saving cloud is containers. And I'm being a little facetious. I think it's really interesting. I think it's important technology, but the container availability is now helping with the one problem that made cloud siloed was portability of workloads. Containers make it really easy to move a workload from cloud to cloud. From your data center, from development, from where you want, and run it somewhere else. That's why I think people call it the, we can call it the flux capacity capacitor for cloud computing. It's what makes cloud computing really possible. And all these things I list here are benefits. How many people do continuous deployment from development to production in containers? Anyone here? Cool. How many people just use it for production and open source software? Anybody have proprietary products that are running in containers? So as we finish this 1.5 error, I think the thing that's interesting is we have all these tools. We have this movement of open compute. If you went by the Facebook booth this week, they had their open compute thing out. So they're opening up the hardware, which I think is interesting. It's probably not affecting us now, but it's going to affect us a lot later on. I think it's going to drive a lot of standardization in the hardware we use. Because variance is the thing that makes things difficult for a lot of the things we want to do. So open compute with a more standardized footprint for your hardware. On our compute layer, this is the virtualization layer. We add things like KVM and Zen, and we've had VMware, but now containers is virtualizing our compute layer. We have distributed storage from Ceph and Gluster. How many people here use Ceph? Wow. How many people use OpenStack Swift? Or OpenStack Storage is the correct team. Interesting. How many people use distributed storage from EMC and NetApp? OK. Interesting. Then we have networking. I listed Open Daylight as sort of this SDN layer around networking. I don't know that it's dominant, but it's certainly one of the leading controllers for virtualizing the network. And I think that's key.  Above that, we have OpenStack. How many people here use OpenStack? Anybody here use, Joint is now SmartOS. Anybody use SmartOS? Well, Joint is a company, but SmartOS is the open source. Anybody here use Apache Cloud Spedack? One guy. That's good. And then you have in the cloud, public cloud, you have EC2, Azure, Google. And then on top of that, you sort of have this abstraction layer on top of the infrastructure from Docker's containers. You have Mezos. You guys know what Apache Mezos is? And Kubernetes. So Kubernetes is a scheduler that Google wrote to help manage containers. And then you have this platform as a service. Now, honestly, I've seen Gigas fit Cloud Foundry in OpenShift and Gigaspaces all in production. But I think one of the ones that has the most momentum behind lately is Cloud Foundry. How many people here use a platform as a service there from one of those three? OK, interesting. So all this stuff sort of has evolved. And now it's present day.  That's where the magic happens. So Cloud.2.0 is that magical place where everything works and our infrastructure is elastic. And we have almost zero downtime. And we do 20 releases a day. And it doesn't break stuff. And our customers love us or end users love us. And that's where we're at to do today. And here's what I see coming in Cloud 2.0 is, well, that slide just shouldn't be there. So first off, we have all the infrastructure is open source, is available. Every bit of that layer is available in open source. And I think that it's really interesting from an open source angle that I look at it this way. There's a lot of competition between companies and whose products are better. The reason I like open source is it isn't a zero sum gain. This is a quote that I use all the time from Alison Randall, who, when she was the program chair at, I really said it. And I really thought it was interesting is, in the old days, people like IBM and BMC and Tivoli, computer associates, all were very, very competitive for this infrastructure layer. And they all were developing things that were overlapping. Today, we see a lot of, in open source, you see people like HP and IBM collaborating on the Linux kernel. And you see them collaborating on infrastructure stacks and things like OpenStack. And they're not wasting their resources on things that have low value. They're really driving through a lot of innovation, a lot faster speed than before. And I don't think that would be possible without open source. So earlier, I had talked about Simon Warley and his sort of theories. And his ideas are basically, you only develop what doesn't adjust, develop what doesn't, that's so badly written, I have a little hangover this morning. Develop what doesn't exist to meet your needs. Leverage the gray induce of high-quality software like Linux, OpenStack, and Cloud Foundry, and virtualization like KVM and Zen. And then commoditize things like Linux. So everybody is sharing development of Linux across the industry. A lot of people are sharing development of OpenStack. You leverage what's there in OpenStack, but you also commoditize the stuff that isn't differentiating, like scheduling workloads. That in itself is not really interesting, but the logic on top of how you schedule your workloads are pretty interesting. So earlier, I was talking about that I had that little timeline. And we're talking about back in the 90s, there's this thing called SOA. They talked about componentization and a design pattern, which is where individual components do a single thing via the web and are loosely coupled. That is very much what sounds like microservices today. How many people have heard the word microservices over and over and over again? So the thing that's interesting, and I mentioned earlier about Netflix, is the way that they create their infrastructures based on microservices. So they have a microservice that does one thing. And maybe that one thing is, I don't know, encoding a movie. And it only encodes movies. And you can call that to encode movies for re-display across their network. And the way that they deploy this microservice is they deploy it to do this one thing, one thing only. And if they make improvements to the service, they don't redeploy the service. They deploy microservice 2.0. And the microservice 2.0 is backwards compatible with 1.0, but it has all the improvements. So the application developers actually consume those services as they're ready, not affecting everything in production. So if North America is using this encoding service, and they're ready to go to 2.0, but South America operation region isn't, they can actually just choose not to consume that till they're ready. And then you can leave those microservices in production forever, or until they're no longer used, and you can pare it down. So that sort of loosely coupled network infrastructure has actually been talked about since the mid-'90s, but actually you start seeing it in practice now in the cloud era. And part of it is because we're in this area of cloud abundance I was talking about earlier, where there's things like that. So we talked about containers earlier. Now, did anybody see the Docker news today? What kind of company did Docker buy? Unicernals. So now we're going to go to conferences, and they're not going to say Docker, Docker, Docker, or they're going to say Unicernals, Unicernals, Unicernals. And actually I think they're talking about Unicernals, the Docker guys next door talking about Unicernals now. Now, earlier on I was talking about what I've done in my past, and one of the things I was on the board of the Zen project and worked on that for the last three or four years. And one of the things that came out of this Zen project was this thing called MirageOS. And MirageOS is a, I don't know what the right term of art is, a unicernal runtime. And basically what it is is that it's sort of a unique operating system if you don't like it, or a fast and lean operating system if you do like what they're doing, and what they're doing is they're packaging configuration files, the binary, and just the necessary libraries for them to actually run this image. And you can run it within, I know about Mirage because it was a Zen project, you can still use the hypervisor to run these things. You could also probably run them within containers and make your containers lightweight. So that's sort of, I'm not sure how that plays out exactly in the Docker container space, but I think it's an interesting technology that is really going to be a part of this Cloudbot 2.0 era. Now, all this sounds well and good until you start thinking about what's the downside to all this. And somebody asked about this, anybody here read the news stack? So the news site, it talks about Cloud, it's pretty avant-garde, the guy used to write for GigaOm, but he asked Mitchell Hashimoto, who, HatchiCorp, what do you think's the number one problem Cloud is? And that's service proliferation. So now we're in this area of abundance, but we also have service proliferation, especially as we start to consume microservices. And now you're going to have all these microservices. So it's great to have abundance. It's hard to track abundance, because that's what I call the zombie problem. So what's the worst thing you can do in the zombie movie? The guy who always dies runs into a house that has a lot of windows and doors, and you have a bigger attack place. So now we have all these microservices running, and you have all the windows and doors, and you know the guy in the walking dead that runs into the house and bolts the door and leaves the back door, and you see all the zombies run in. It's because there's lots and lots of openings. That's the downside of this area. So today, as I said earlier in that shakeout, I think that the public Cloud is this. This is what we look at. And I think those prices, I haven't seen a big web Amazon price drop lately, but it seemed like for the last five years, just when you think computing can't get any cheaper, it gets cheaper. Security used to be the big criticism of these guys. I think they're probably getting more secure. Now we have things like Docker and Amazon supporting Docker and maybe Unicernals at some point. The portability problems across Cloud is changed. So you want Cloud computing to be like electricity. The initial terminology for Cloud computing, IBM used to champion was utility computing. And you want to be able to plug in your workload just like you can plug in your laptop to outlets and have them be standard. And you're also going to see, I think, from these guys of proliferation of microservices. So Amazon is masterful at coming up with supporting services for your EC2 instance. So they have monitoring services. They have a suite of continuous integration tools. They've got SQL database services and Java container services and all these things to add on. I think you're going to see microservices that are going to be more data streams and other kinds of things we haven't seen in the past. Then in the private Cloud, you're going to see what I call in the private Cloud, I think, is what really is the minimum viable Cloud. Because in the early days, I think where we went wrong is we were just trying to keep up with Amazon. Well, Amazon has one architecture target. And when they make changes, they control all the variables. If your software developer trying to develop software to run on all these different infrastructures and have all these different variables, it's very, very difficult. So I think what's evolved is with OpenStack, which I feel like is an ecosystem for you to consume the parts you need to make the minimum viable Cloud, which a lot of times I think will be done by vendors like Mirantis or Red Hat or numerous other people in that industry. My personal, the reason I've always been such a big fan of Apache Cloud Stack was simply because it always has been a minimum viable Cloud. It very, it didn't, you know, one thing really well, and it scheduled workloads for Cloud computing on your own hardware. I mean, it does not have massive number of sub-projects and identity management used standard protocols for all that, whereas things like OpenStack has a project for each one with a lot of support. So they're legit, too. And then SmartOS comes to you from the people that did Joiant. And the thing that's interesting about SmartOS is it comes from the Solaris route. So I think it's Illuminos. Is that the open source Solaris kernel now? Then Joiant has been, is really a pretty good Cloud hoster. They're really smart. They had the idea of containers and used them for quite some time in just a little bit different format than what we're used to sort of leveraging the Solaris zones model. The foil to that is Linux sort of copied that idea with LXC and the container model. But that wasn't exactly an original idea. Just a very good implementation on an operating system that has wide appeal. Then we have what I call this Public Cloud Plus. And probably the one that I think is most successful is not a wide-use cloud. And I think that's Salesforce. So they bought a company way back called Heroku. And the brilliance of that was Heroku was a platform as a service. So you can write your applications for Salesforce. And then hook them into your CRM and host them. It's pretty brilliant. But they're not just virtualized infrastructure and elasticity. They've got high levels of service. They have tooling. They have continuous integration. They have a lot of things that make their Public Cloud Plus. And I don't even mean that to me to be more features as much as, I mean it to be more features, not better features, or more specific ones, I should say. So in the early days, we had those silos. And I think what's happened now is those silos are sort of gone. I think the Cloud 2.0 cloud is just cloud. And it may be in your own data center. And it may be in someone else's data center. But you're weaving together all these different things into a single fabric, which is what Cloud is. We're getting better and better at bridging between our data center and their data center. Those services that are hosted with microservices, I think, will start consuming things across different providers and weaving it into fabric from our data center and Amazon or Google. So that's sort of how I think that this all evolves. I have 40 minutes worth of content. And I was because I had written down this was 45. So I have plenty of time for Q&A if there's stuff like, right now I spend a lot of my days with, this week I was spent in my days with Cloud Foundry one day, talked to the guys that were running the Cloud Native. And so the container initiative when it's foundation, I spend a lot of time with Apache mailing list for Cloud Stack. And so if you have a question of what do you think or where can you point me to get more information of what you're trying to do, how many people here are considering building their own Cloud and their own data center? How many people here are just trying to figure out what this Cloud Hoopla is all about and how it all fits together? I think when I got into IT it was right in 95. And the thing that was the biggest transformation for me is I've worked in an internet service company and everything ran on Solaris. Now if you know anything about the internet service company, they make very, very little money per customer. It's like razor thin margin. So in the Solaris hardware at the time it was really, really expensive. And so I think Pentium, just the Pentium processor came out the first post-486 processor came out. And so all these machines were getting decommissioned. And they were like DX2 66 megahertz machines. And the Solaris boxes were really expensive. They're sort of these pizza box things and they're real funky looking. And every couple weeks you get CDs in the mail with your updates.   Like you were not doing pixie booting and updating stuff. It was manual. So the thing that was transformative was these DX2 machines that we had, we could put this operating system one that we could get for free, the Linux. And it had zero incremental cost added to these boxes. Other than time, which in those days the thing that was the limiting factor was driver support a lot of time like for storage arrays and things like that. But that was that sort of era of abundance in the operating system. And that just changed the way that IT growth just went gangbusters and started the .com. I feel like all these cloud services, the cloud tools are like that next wave of things that are just going to accelerate how effective we use IT. So the question was, what do I know about cloud orchestration tools for Docker? I know that there's a huge need for that. And so I mentioned right scale before. So right scale back in the early cloud days was going gangbusters because it was a good orchestration for tool for infrastructure in the cloud. Right now I think that's sort of the next. So Docker has some of these tools. I think Kubernetes was a huge thing. And I think the Kubernetes management is sort of going to be the next set of tools. And I'm going to give a shout out to an open source project called SkipBox. And SkipBox is written by a guy named Sebastian Gozglon, who is in Geneva, Switzerland, who's pretty darn smart. He's the VP of Apache Cloud Stack. He used to work for me. Because he's the smartest guy I know on that. And he decided what he wanted to do for his own personal project was write this thing called SkipBox. So it's in GitHub. I would definitely go check it out, tweet to him. He would love to hear what you think. But the idea is I think that you use containers and then you use Kubernetes, but there's still some orchestration tools to maximize the way. Like Kubernetes, if you guys don't know, came out of Google. So everything that you touch for Google is part of this thing called the Borg. And they just add their workloads into this great big mesh, just like the Borg in Star Trek. And so that software that runs the Borg, Kubernetes, they spun out as Kubernetes because they want workloads to be easy to move across from your infrastructure, their infrastructure, and make your world better. But SkipBox would be a place I would look. But I think there's going to be a lot of other stuff that I'm rooting for Sebastian. So Rancher, that's conventionally, I always forget about Rancher. Rancher was started by two guys, Shang Lang and Shannon Williams, who are co-founders of cloud.com and worked with me at Citrix. So I do know about Rancher and Rancher or Loss. And actually, they're smart. Shang was the guy who raped the Java virtual machine for James Gosling's team at Sun. Like, he's crazy smart. When I'm trying to figure out from the vendor-led projects and their venture-backed company and have a lot of smart, one of the best engineering teams I've ever worked with, two of their architects are just out of this world and a lot of engineers are amazingly smart. Whether or not that layer of tools can be commercialized or becomes part of the open source ecosystem is what I can't decide. Because Google, I feel like once that to be a very democratic layer that everybody participates in and there's not a lot of vendors there. So I think Rancher has some value. And Skipbox has some value. But I think it has better shot at the open source tools till we figure out what the Kubernetes management layer looks like or orchestration layer work looks like. She's just said there's another one called DCHQ. Yeah, yeah. So that's my, like, I'm fine with proprietary software. I love an open source software. But the thing is if you go back to this, the strategy is develop the stuff that doesn't exist and commoditize what has very little value. Over time, I wonder how much those orchestration tools are going to be commoditized by everyone. Because everybody, or not everybody, but you see more and more participation in the end user in the creation of the software and infrastructure tools. And I think that's why I'm like, Rancher, O.S. may become, well, Rancher has an open source component to it. So that what they're doing there might be commoditized. And maybe someday Rancher is in the business of reporting on what all the stuff's going on in your dashboard business, for example, or something like that. But it's moving so fast. And plus Docker themselves and CoreOS. Like CoreOS, anybody here know CoreOS? So they're an operating system that uses system D and schedules container workloads very, very effectively. I've probably been doing them justice by that. But they also, I think, are going to be heavily involved in creating management for Kubernetes. I think they do a lot of services around that. So yeah, it's sort of the early days of, and it's sort of tough because if you start investing your time in a tool, you want it to be around for the next couple of years. So it's great to be on the leading edge of technology. It stinks because you're the canary in the coal mine for everybody else to figure out how to get it done. Yeah, but anyhow, I do think that the way that they talked about cloud when 20 years ago when the SOA people, if you see a guy or a gal who worked at IBM who used to talk about SOA, and they show up at a cloud thing, they're just like nodding their head like, yeah, this is what we talked about. But they were selling those tooling and infrastructure via IBM, and not just them but other companies. And now there's this abundant amount of infrastructure and inexpensive access to public cloud, which is really driving a lot of cool things. So that is pretty much all I had. My contact information is there, which apparently is really, really tiny because I changed the font. But I am at Marhinko on Twitter. If you Google my name, I am one of usually the first hit on Google for that. My blog is socialized software. I'm happy to chat with you or direct you to someone much smarter than me on cloud. But I hope this was a good overview of how it all fits together or what you should be considering. And there's tons of good talks on the tools that I mentioned. All those HashiCorp tools are really interesting. One that I think is pretty cool that's fairly new is Vault, which allows you to manage your public and private keys across clouds, which is sort of a pain in the butt. Like Google makes it easy for you to do it in their cloud, but not Google Amazon, but Google does too, to some degree. But his tools that work across all clouds, just tons of good stuff to Ansible. How many people here use Ansible? So I think it's interesting. This is my little sidebar on tools. The thing that really has driven operational efficiency and automation, in my opinion, is this whole cottage industry around configuration management. So it started with CF Engine, and CF Engine is this management orchestration tool to manage configuration of infrastructure. It started by a guy who's really, really, really smart. And his name's Mark Burgess. And he just wrote a book. If you'd like to geek out on operational theory and why things end up working well, it's worth it. And I forget. I wish I could remember the name of it. But he started this sort of movement. And then this guy came along, Luke Kniece. And Luke Kniece liked what he did, but it didn't quite work for him. And he's, anybody use Puppet? So he's a guy who wrote Puppet. So he took it a step further and came up with some things that are interesting, the idea of inheritance and some other activities. He really got a big following in the operations community. And then came Chef. Anybody here use Chef? I feel like Chef's pretty popular in the cloud world. And that was done by a guy named Adam Jacobs. He liked what Luke did, but he had a ticket. Actually, there might not be a chef. He had a ticket. And Luke's like, well, I'm not going to do that ticket. He's like, OK, I'll write my own configuration management thing. So he did, which is good, because I think diversity is good. And then all along the way there, there was this guy at Red Hat. His name was Michael DeHaan. And Michael DeHaan wrote something called Funk. Anybody here know Funk? He wrote the thing that automates Kickstart too. And it's used all over the place. You pixie boot to this management thing. He wrote all this management stuff at Red Hat that sort of was the glue behind it, including a lot of stuff for Puppet. And Cobbler, that's what it is. Cobbler is. Anybody here use Cobbler? So he wrote Cobbler. And all along this way, he was thinking, well, I like what the Puppet guys that they're doing. He integrated Cobbler and Puppet. But then he wrote this thing called Funk. He's like, it sort of did what I wanted it to. But he baked these ideas and wrote this thing called Ansible. So ironically, he moved to Durham, Red Hats in Wally, North Carolina, where I live, and moved up the road for a couple years. And he had a couple of jobs. But he wrote this thing called Ansible, which Red Hat recently bought for $100 million. When the guy used to work in the back room, probably give him a raise and some better coffee. He hasn't been happy. But I think that his difference was where Cobbler and Salt Stack falls into that same bucket too. Because he built this thing with the idea that he just wanted to execute things. And this execution environment is what was valuable. And then by virtue of the fact that it was modular and you could execute scripts, you could execute these configuration scripts, which I think might be called playbooks or something like that. And they're written in YAML. And basically, so now this is sort of the way that a lot of people are doing configuration management. But at the end of the day, these tools are what's making you able to automate and keep up with cloud infrastructure. Because now you can spin up hundreds of instances and minutes. Well, before, when they used to let me touch servers, which is not a good idea anymore, you'd call somebody on the telephone. There was no online ordering for Dell. And they would send you these servers on a pallet. And they'd come to the shipping back. And you take it out of the pallet. And it was the slowest server with 16 megs around. And you'd put it in the rack. And you'd bust your knuckles. And then you'd have to wire it in. And then you'd have to go back. And you'd have to open up your firewalls and your checkpoints software and blah, blah, blah, blah. So to provision one server was like a six-week or deal until everything came together. Now it's like I can launch 1,000 instances in an hour with a credit card and an iPad, which is crazy. So I think for that ability to keep up with the velocity of cloud stuff, these tools are what's really, really interesting to me. And my day, I feel old now. But yeah, whippersnappers, in fact, when my home walked up those hillbys ways to the data center, blah, blah, blah. But in those, I was still doing a lot of operational stuff. The limiting factor, once we got all those servers, as if you're gonna buy tools, it was really expensive. And they weren't exceptionally good at the time. Like I remember monitoring tools were expensive. So we had pro scripts that would ping all of our infrastructure and then if it got a failure, it would parse that and send an email and we'd have, we had like these old, compact, all-in-one desktop PCs running Slackware that would run these CRON tabs that would ping everything. And one day we got, we got approved to get NetCool, which I was like, yes, this is awesome. And so we hooked it up and started adding in the IP address and we're an internet service provider. So we had like tens of thousands of modem racks and servers and stuff to ping. And I remember the guy entering in like the first part of the spreadsheet that had all this stuff in. He's like, it wouldn't take any more numbers. Like, what do you mean it wouldn't take any more numbers? We got NetCool, but we only got licensed for 100 IP addresses. So, because it blew our budget. So now, you know, I thought it was interesting to see Nagios sponsored here. Like Nagios is not an overly complex monitoring system, but how many people here use Nagios? Like, yeah, it's everybody uses Nagios because it has utility. It's not that hard to administer and it does what it needs to do, to do availability checks. And there's a huge ecosystem of plugins so you can figure out how to manage pretty much anything. That started it. I worked at a company and anybody here use Xenos. So I was employee in one of the early first five or six employees at Xenos, which is an open source monitoring software a long time ago. And then you have open NMS and has a booth here and there's a lot of free and open source software that's really pretty good for monitoring. It used to be a big cost and hard to manage. So anyhow, any other questions? Thanks for your time. I appreciate it.