All right, so for our next session, we have reached them, teach them having a lifelong learning series in your library. Meg, oh, I didn't know. Wemp, is that how you pronounce it? Wempie. Wempie. Wempie. It's a funny last name. That's OK. And she is from just next door to us in Colorado, and is going to tell us about lifelong learning programming that they have done, and how you can do that with helping. We talked earlier about continuing education for staff, this continuing education for your actual patrons. So go ahead and tell us all about that, Meg. OK, well, good afternoon, everybody. As she said, my name is Meg Wempie. Up here, I do have my email address, which I have also put at the end of this slideshow. But feel free to jot it down, and I'll say more about that later on. I am both the assistant director here, as well as the adult services librarian, which means I kind of wear a few different hats and do lots of different things. Let's see. I would like to thank you, of course, for coming to this session and staying through kind of all these different sessions. Just as a little heads up, if you aren't sure where Pagosa Springs, Colorado is, it's in Archuleta County, which is in southwestern Colorado. The county itself is 1,800 square miles. So it's a fairly large county. We have about 12,000 people in this county. We are about an hour east of Durango. So we're pretty far from Denver. Lots of times, people say, oh, I think we're so close to Denver, but really Denver is about five and a half hours away. We do serve the entire county, and with us being pretty close to the New Mexico border, we're about 30 or 35 miles from the New Mexico border. We actually have a fair amount of people who come from Dulce, New Mexico, and other places in New Mexico to come to our library, just as a heads up if you're kind of wondering a little bit more about our library. So again, today, we'll be talking about a lifelong learning lecture series. Let me tell you kind of give you a quick picture of what the lifelong learning lecture series looks like at Ruby System Library. It happens twice a year. We hold it in the spring and in the fall. It's for six weeks, and we have it on Thursday evenings. The talks are approximately 50 minutes to an hour, with about 30 minutes or so left for questions or comments from the people that have attended. We'll be talking about how you can do a lifelong learning lecture series at your library, so let's go ahead and begin. So why lifelong learning, of course, as Krista mentioned, we talk about continued education for staff and for patrons. And I won't read this quote to you, but as you can see, ever learning understanding has been happening for a long time. People have understood going back 150 years as seen here and likely much longer. You hear this webinar to learn more, maybe for yourself or maybe for your library, but hopefully you will definitely learn more and learn more in this session to help you, to help your patrons with their ever learning. In fact, I'm guessing that one of your library's values or perhaps part of its mission statement includes learning or informing other people. So how can this process happening? By doing a lifelong learning lecture series at your library, of course, it doesn't have to be expensive. It doesn't have to take a lot of your staff time or a lot of effort. So let's talk about how that can happen. The biggest thing, of course, is finding speakers. I hope to show you and demonstrate that it isn't as hard as you might think originally or as daunting a task as it might seem. When I first was hired here at Ruby System Library and we talked about a lifelong learning lecture series, I thought, well, who in the world had just moved to this town? I don't know anyone. How can I find speakers? Perhaps you're in the same boat or a similar boat that you're just not really sure who you would possibly call on. So you might consider thinking about taking a walk down Main Street. What businesses are there? So think about the possibilities. Is there a credit union who could talk about financial planning for retirement? It's helpful to also think about something that they may know about that might be a little less direct than what the store is. For example, maybe there's a yoga studio and they could present on the benefits of yoga. Or maybe the same yoga studio, it's a personal business that she started. And maybe that or another company could perhaps be talking about self-starting a business. So again, thinking a little bit outside the box there. Staff is another place to pull speakers. All of us have things that we know and that includes your coworkers. So talk to your staff or more importantly, listen when they talk about what they did on the weekends or a meeting that they attended. Maybe they love photography. Maybe they were in a contest. Maybe, well, who knows? You may have someone willing to share. We definitely have talented staff at my library, Ruby Sisson. From quilters to travelers to Halloween lovers to authors of books, we have a range of interests. The key thing is to see what they might be willing to talk about for 45 minutes to an hour. For one presentation, we had a staff member present on her travels to Africa. She loves both traveling and photography. The biggest challenge for her was to narrow down her pictures for the talk. I think she had over 5,000 pictures that she had taken on this African safari, so she had lots of things to pull from. She told stories about her safari and people loved it. She was nervous about presenting at first until I told her that she was in pictures and telling stories of her adventures were plenty. Because she's also a birder, she was able to name, which she of course double checked before presenting to make sure that you had the right name, the wide variety of birds and other wildlife that they encountered. We often, in fact, have great turnouts for these armchair tourist talks. People get to see, experience, and learn about other cultures and places without having to renew their passport, get additional immunizations, or convert currency. Patrons, they know a lot too, and often they like to share. Maybe they'd like to share about their hobby or their business. I did want to talk for a little bit about business and different guidelines that our library has, and perhaps your library does too. So let's go back to the yoga example that I used earlier. We have somewhat strict, well, we have guidelines, I guess I should call them. If, let's say there's a woman who has a yoga studio and she's going to come and present on the benefits of yoga, again, to use that same example from earlier, she's certainly more than welcome to say where she works or what the name of her company is. And of course, in all the publications that we put out, we would mention where she's from and what her company is called. Partly because it does promote her company, but in addition, it also shows that she has authority to be teaching or talking. What we don't want is someone to come and during this hour-long talk to say, well, if you come into my yoga studio and kind of just say that over and over and be kind of very aggressive or pushy about it. So generally, the people that that might be an issue with, we just kind of have a discussion and talk about, again, they're more than welcome to bring their contact cards that people can take with them. We, of course, when we introduce that speaker, and again, as I said earlier with the publications, we will certainly say the name of their company. It's not that we're trying to hide that, but we don't want it to become, well, a big commercial, if that makes sense to you. Again, we consider that to be a win-win scenario. And let's see. All right. You might also have local government agencies that are nearby you. A lot of places, perhaps where you are, hopefully, have a Forest Service, or maybe you have a nearby national monument. Maybe there's a museum from a quilting museum to a veterans museum to an art museum. Really, again, we're just kind of looking at who's there and who's ready to share. Maybe your hospital has a wellness center that's connected to it. We here at Ruby System have been fortunate to have a range of talks, and sometimes they're included with our lifelong learning lecture series from our local wellness center that's connected to the medical center. Again, sometimes they have standalone workshops, but oftentimes we've integrated the talks into the lifelong learning series. For us, and let me say this because I don't think that I said it earlier, our lifelong learning lecture series covers a wide variety of topics. Again, as I mentioned, it's six talks on Thursday evenings. There is not a central theme. Again, if there were to be a theme, it's just kind of continued learning or lifelong learning. So that kind of opens it up to a wide variety of different talks and presentations. Sometimes agencies have designated outreach people for you to talk with, and other times not, but even if they don't have an outreach person, they may still have a person that's willing to share. Again, sometimes, and I know that a lot of us are kind of in small places, it's a small group of people that work for any organization or business or whatever. So again, maybe they don't have an outreach department like you might have if you were in a large city. Another place to potentially get speakers from, think about if there are local colleges, universities, vocational schools that you can pull from, different experts who don't mind doing some pro bono work at your library, or in our case, I often use the local Fort Lewis College to get ideas. Fort Lewis College is in Durango, which as I said earlier is about an hour west of us. They have a lifelong learning lecture series, and I often glance at their schedule of previous sessions and think about if any of the presenters would work here at this library. What I will say is that oftentimes I look at their schedule of speakers and think, well, that might be a little more academic than what our people here would like, but there are certainly people that I have pulled. In fact, there's someone that will be speaking in this spring's lifelong learning lecture series who gave the talk in the Fort Lewis College's lifelong learning lecture series back in January. Their lifelong learning lecture series runs longer and that type of thing, but that doesn't matter because again, I can get ideas for different things that might work here in Pagosa. Let's talk a little bit about money. For us here, we base it on whether or not people are having to drive. We give them a small stipend that they can use for gas or lodging, which isn't really necessary. Oftentimes, if people are coming from anywhere, they might be coming from Durango. So lodging isn't usually required because the lifelong learning lectures start at 5.30. We are done by seven, so they could very easily drive back to Durango. Again, it's an hour to maybe an hour and 15 minutes, but again, we give them a small stipend. Perhaps they just wanna use it for a meal. So again, we pay them $100 if they're coming from Durango, which I think I might actually consider cutting down because it is only 60 to 75 minutes away depending on where in Durango they're coming from. You can really make that call. One speaker that we had come from Ignacio from Wildlife Refuge, Ignacio is about halfway between Pagosa and Durango, so we gave her $50. And it certainly isn't something that they necessarily expect, and keeping that in mind, you can certainly lower your cost.  The first way that comes to mind, of course, is not to have people come from a distance that they may wish or ask about a gas stipend. And in fact, generally, with the lifelong learning and lecture series of the six in each series, I might have one or maybe two people that are coming from somewhere else. So again, the people are local that I'm pulling from and I'm not spending any money on that. You may also consider seeing if there are local businesses in your location that might donate things that you can give to the speakers. One thing that immediately comes to mind is a gift certificate for a meal, especially if the talk is done before or after a meal time. Depending on where you live, maybe there's something else that you can offer. I am fortunate that Pagosa Springs we have, well, as the name implies, we have hot springs. So we have three different locations for going and taking a soak in hot springs. So maybe I could ask one of those or ask those places to see if they would donate a soak in the hot springs. I also, my little town has a few different breweries, so maybe it's something that you might have something like that that you could ask if they might donate a drink and an appetizer. Again, oftentimes speakers and presenters are happy to be sharing their information. So these are almost just more kind of like little boosts and just another way to say thank you essentially. Perhaps you have a local bookstore that will donate a gift certificate. One thing to really keep in mind and I'll probably say it multiple times during this presentation is to remember that this series is your series. So you can personalize it to suit and we are gonna do some brainstorming later where you can kind of think about what might work for you. But again, this is your series. So when I say different things, just keep in mind there are no rules. So try to think outside the norm, particularly if you're trying to make the series cost you nothing other than publicity. And I will talk about publicizing later. It is very important when you're looking and brainstorming on these speakers and their particular presentation topic to think about what might work in your community. Hopefully you have some sort of feel for who your people are or the people that you might want to get in. Relative to our population here in Archuleta County, we have a very large proportion of older people. It's why we have a hefty and well used large print collection. The talks do well. Oftentimes we have a lot of people that are older and they're retired. So then they're just happy to learn. We certainly also have a wide variety of people that don't live here full time. Maybe they just come in the summer because we have a pretty mild summer compared to other states. Or maybe they're just here in the winter to go skiing. But again, think about your demographics. And they're quite possibly different. Maybe you have people that are older. Maybe you have different cultural backgrounds. Are there a lot of married people with children or young business people? Again, think about who is in your area. The Lifelong Learning Lecture Series is a great opportunity to get people into the library that may not have been in before. And I certainly find that's true with most lifelong learning lecture series that somebody will say that they had never been in the library before but they saw that this talk was happening and now you've got this new person coming into the library. We also certainly have lots of people that are very dedicated to the Lifelong Learning Lecture Series and they come and they're common faces that I am happy to see. So when you're looking at your community, don't just look at who comes into your library. Of course, look at who you see around town when you're grocery shopping or taking a walk. Because again, lifelong learning, you don't just wanna get the people that already come into the library. I know that it's certainly always one of our goals to kind of think about how to get more of these 12,000 people in the county into our library. The demographics of your community might also help you determine when you might wanna hold the series, daytime or nighttime, weekday or weekend. We all work in different libraries with different situations. Perhaps where you're located has other potential speakers. So what I'd like to do right now is kind of take some of that time, as I mentioned earlier, to take a few minutes to think about some of the things that apply to where you are specifically, people that could possibly come and talk and how they may work at your place to have as a presenter. Is there a local brewery, winery, a bike shop? So is your thinking of places? Please go ahead and type those in the comments or into the chat box. And then in a couple of minutes, I'll ask for this information to be shared out. Great, yeah, everyone just go ahead, use your questions section, even go to our webinar interface if you haven't yet and start typing in your ideas. Think about your town, what's available out there. You can go ahead, Meg, if you wanna continue or... Okay, I was just gonna give a minute or two just to kind of let people type any ideas that they might have and then go ahead and share them out. There's a little much coming in, yeah. Yeah, I was gonna say, unfortunately, I cannot see what people are commenting. Yep, that's a lot. I would imagine there's probably some things that are maybe some common things that are coming up. Let's see. So are you noticing? Yeah. Do you want me to start reading them off to you?  Nah, it's all over, which is good. There's Contact Your County Extension Office. They always have various... Yes. And that's therefore, Master Gardeners. My mom is Master Gardener.  A local meadery. So it makes mead as opposed to drinking wine. Okay. Yeah. Retired teacher who has traveled to many places and would be happy to speak. Ooh, Spanish rodeo and cowboys. Wow. Yeah. Tables and estate planning. Farming, another farming one. Local history, beekeeping. Oh, there's gardening again. Civil War Museum is in their town. That'd be definitely great. Interesting to partner up with a tulip farm. Oh, our library is on the edge of a small wine region in Oregon. So in a town of less than 4,000, we have six wineries, one meadery and one brewery. Wow. I will be visiting there at some point. That's funny. I actually gave this talk at one other place and somebody was like, where's Pagosa? Because during the talk, they found out that we have multiple places to soak in hot springs. Some of you might know that in Colorado, cannabis has been legalized in this town. We now have, well then, we've got like three to five dispensaries and we have three breweries and people are like, what in the world and how many people are in your town? So yeah, it's kind of. You'd be surprised, yeah. Apple growers, if you have any sort of orchards. Beekeeping at Mammoth Cave National Park, historic homes. Anybody from, yeah, a local park or something could come, horse farms. A funeral, have a funeral home come in and talk about end of life and what you would do for that. Quilt shop, bike shop, local musicians, cheesemaker, local artists and soap maker, maple syrup, carpentry, taxidermist. There's some great ones in there. I am jotting down some of these to kind of think about for the series because again, we do it twice a year. I was somewhat disappointed that I had actually gotten in touch with the credit union. That there's one in Durango. We don't have one here in Pagosa to see about doing a Wilson and state planning because again, as I mentioned, we have an older population and I thought, oh, there would be lots of people that would be interested in that. And I was disappointed that they said they're short staffed and just weren't able to attend. Yeah, a lot of great ideas in there. So folks that are listening, thank you so much again for coming, but I hope that you kind of keep thinking about things. But let me go ahead and now that we've kind of shared out, let me kind of keep going on. Yeah, go ahead, continue. Yep, and speaking of sharing out, let's talk about how you can get the word out. As this true workshop or event or really anything at the library, new or not new, of course it's important to get the word out. If they don't know that it's happening, then it's almost, you know, it's essentially not happening. This picture I thought was kind of cute because it shows 25 different ways to spread the word. Some may work better than others, but I thought the graphic was interesting for brainstorming on how to share this new series. And again, depending on where you are, you may have some of the things that I'm about to mention in terms of how we publicize it that work for you or that you have available to you. We, of course, use our usual methods of pro-motion through our website, our Facebook page, as well as on our twice a month, we have a local radio station that lets us come in and they have a little time, this variance corner, and we go and we talk about the different events that are happening at the library. And so, of course, we talk about that. I often, because it is a generally well-anticipated series, I go ahead and give dates out once the dates have been determined. I don't wait until that week to share that with them. Living in a small town, we do have a local paper that comes out once a week, and so I write a special article that will be included on the paper on the week prior to it starting. In addition to the special article, we each week in the paper kind of have an ongoing where events at the library are listed and there's kind of a community calendar and so all of them are listed there as well. But I do like having that special article that people see that's in the main part of the paper. We also have two different types of handouts that people can give, well, maybe three if you include our monthly calendar. So, of course, each month, and I'm sure that most of you all do this too, we have a calendar that comes out for all of the events that are happening. We have a lot of events here at this library, so we actually have to break them down into an adult calendar, a teen calendar, and then a kid's slash tween calendar. So we've got that calendar, of course, that mentions the series and has it on the calendar, but I also make a pamphlet or a brochure, whichever you wanna call it, that really goes into the specifics of who is speaking when and a little blurb about their talk. And so that's something that I can easily hand out to people or that people can grab when they come in for different things that are happening in here. And then I also have a kind of abbreviated one page thing that shows at least who is speaking and what they're speaking about that gives maybe a sentence or two about their talk. Then that can also be used as an easy way to display in our display case or if I'm needing to make it briefer to put on our Facebook page. So again, a couple different types of handouts for people. In addition, you might also consider mentioning the series that other workshops or classes that you do. I generally teach a weekly computer class in addition to two tech times a week. So I always have those pamphlets nearby and I am sure to mention them because I know that I cannot always assume that people know what's going on at the library. And I'm sure that you know that, but again, I think that it's something good for us to kind of remind ourselves that if people don't know that something's happening at the library, in my opinion, that's our fault and not there. So again, just kind of thinking about how to get that word out. If you're fortunate to have places in town to hang a flyer, you might also consider going around to stores or a coffee shop or maybe other meeting spots that have a community bulletin board. After years of having a twice yearly lifelong learning lecture series, people ask about the series months before it starts. I have actually already had somebody ask here. I actually think that they probably asked back in January about lifelong learning and we generally don't have lifelong learning until it will start actually in the middle of next month. So as I mentioned earlier, for us here, we hold two lifelong learning lecture series per year, one in the spring and one in the fall. This spring usually goes from mid-April to mid-May. And I did just a minute ago say next month, but I'm already thinking about March, thinking that we're in March. So again, we're going from mid-April to mid-May. The fall series, I generally have it set up so that runs for the six weeks prior to Thanksgiving. So it runs based on when Thanksgiving is and then I just go back six weeks. We hold the series on Thursday evenings at 5.30. The library closes at seven. So again, the lecture or talk is about an hour or so and it gives time for people to ask questions before they need to be out of the library by seven. That's what works for us. Again, as I said earlier, you have to kind of figure out what might work at your location. I found it helpful to ask patrons for their feedback. I've used this suggestion when starting a new book club instead of making it kind of wide open for when to hold them, you could decide a few times that might work for you or for your library and then kind of have a loose vote on it. The times could be based on when your library's open or when the person who would be in charge of them is available. You might even give a time when the library is closed. Many years ago, before I worked here, the Lifelong Learning Lecture Series was held on Saturdays at 3 p.m. At the time, the library closed at 3 p.m. So they kind of had this overlap and the person who was in charge of the Lifelong Series back then would just come in and kind of stay and have it open just for the people attending the lecture. But keep in mind, as I said earlier, that there are no set rules. You can do what works for your library. Perhaps you wanna just start with doing just one a year and see how it goes. Maybe you think that you might get more people in the summer, perhaps you'd rather hold it then. Another thing to consider is what else might be going on during that time of year? You have to think about your situation. Do you live in a town with a big high school basketball team that, you know, does really well?  That's just one example. I mean, again, there might be other things that are going on in your town, so certainly you want to consider that. Personally, I think it's really empowering to think that you get to decide so much about the series. As I mentioned earlier, we now hold our series on a different day and time than several years ago. Keep in mind that you can try something and if that doesn't work, then you can try something else. I hope that you've learned a lot from this and feel empowered to host a Lifelong Learning Lecture Series at your library. You may have limitations or other things to consider for your specific location, but I think that you'll find that you can plan a Lifelong Learning Lecture Series at your library, again, without spending any or a lot of money without taking too much staff time or effort. I encourage you to give it a shot. Again, I've posted my email address up here. I'm gonna, in just a few minutes or in just a moment, kind of open up for any questions that you might have, but I wanted to be sure that if you had any questions that you thought of down the line, I'm happy to answer those. And I'd also love to hear about any successes or obstacles that you have and I wish you good luck with that. Once again, I'd like to thank you for attending this webinar and I wish you the best of fortune and I'm wondering if there are any questions that people might have. Yes, Meg, thank you very much. Yeah, if there is anyone, there are some questions we have, but I also wanna say if you have any questions, anyone who haven't typed in yet, get them in there. And if you have done something like this in your town, yeah, definitely let us know about your experiences. See who else is doing this out there. Yes, we're working at libraries. We're into recycling stuff, so please. Yes. Hearing, borrowing. That's right, be resourceful. Out of the sessions that you've done at your library, what were the most popular, what's the highest attendance you've had at these events? Okay, so as I mentioned earlier, the armchair, the people's travels, people seem to love those. So those usually have a pretty solid attendance. I'm trying to think about other ones that have had. We had Wendy Sutton, who was the Forest Service Archaeologist. We have just kind of right down the road from us, we have Chimney Rock, which a few years ago was made a national monument. And so she came and she talked. Okay, what's that? Chimney Rock here in Nebraska. Oh, okay, yeah. Well, we also have a Chimney Rock and so, and it was very well attended because she, and I don't remember the exact title of her talk, but I mean, it's kind of very interesting to think about us living on this land now and people living on this land long ago and she was able to kind of talk about that and different recent findings that they had at Chimney Rock. I'm trying to think about other big talks that have gone well and that people really seem to appreciate and like. Gosh, if I thought I would have gone back and jotted down how many people had come to different talks. Okay, so I'll keep thinking on that though. Sure, and how about from the other side? Someone wants to know, did you have any that didn't work at all? That just nobody, yeah. Yes, unfortunately, yes.  We did actually have somebody come from Durango and I thought the talk was interesting. He was actually talking about women in Islam. And I don't know if the, and it's of course always hard to figure out what the issue is. For him that he was presenting, of course, on a Thursday, but it was October the 30th, so I don't know if there was maybe Halloween stuff happening. I don't know if there were sports in town. Again, it's hard to kind of know. And I always feel bad when it's somebody else that's doing a talk or a workshop or something that we're doing and then the turnout is low. And I don't really know that I have great solutions for that because hopefully you've done everything you can. I mean, when there weren't many people, I think he maybe had two people come to his talk. And again, I did what I, I've publicized his the same way I publicized the person who was the week prior, which had 22 people, which I consider to be a large number for this small town that we live in. So I said, Archuleta County is 12,000 people, but in this town it's 1,500 people. And so 22, I'm pretty happy with. You know, I don't really have other great suggestions. I did kind of walk around the library prior to five or 10 minutes before it's starting saying, hey, you know, we're having this great talk. And I think that's how I got one other person in there. But yeah, of course, there are gonna be talks that just don't work out. And I haven't noticed a theme of, oh, these talks don't work or whatever. Again, I've avoided a lot of the, I mentioned Fort Lewis College and pulling talks or at least looking at their talks and seeing if any might work over here. Some of the talks just looked really academic. And so we don't. Sure they would, yeah. Yeah, someone else commented that they're, I'm very reluctant to schedule speakers because our program attendance is very low. It's sort of a chicken and egg problem. And that may be part of your marketing. Some like, where are you promoting this? I don't know. Where are you asking me that question? Yeah, well, we're just gonna help them to figure out how can they get people to come to their programs more. Well, so again, think about what kind of media you have access to in your town. If you have a library page with like a slide show that talks about different events that are happening, the library, of course, broadcast it up there. Put signs up around the library. I know that people don't always read signs, but if you put something that is kind of right in their face, maybe. In fact, one thing that I actually, when I first heard it, I thought, well, that's a little crass, but I know that it has been very helpful is putting the information on the back of the bathroom stall. So then when people close the door, they're seeing this information. So again, just kind of thinking about where you can put just signs up in your library. We've got a couple different places in town. We've got like an ace hardware. We've got a couple coffee shops where we can post things about what's going on. I mentioned the radio, our Facebook page. If you use Twitter or, of course, anything like that in your library, put it up there. I would be sure to mention it to, or within other events or workshops that you're having at your library, not things that are necessarily even connected to it.  Mention it there.  Right. Right. I mean, that's exactly right. You don't ever know. I generally, when there's a program, I'm really trying to push. I usually put flyers, or in this case, brochures, in my car. So, oh, I'm going out to eat.   Having it and being able to run out there. I mentioned the radio here. The newspapers has been great to us over the years in terms of kind of letting us, or at least having like the community calendar that they include us in. But I certainly understand. You asked a couple of questions about that, actually, about your newspaper. How did you get that set up? Does it cost anything to have things in there, in the paper or on the community calendar? It actually doesn't in our town. We have a couple of different things. So, when we send the special articles, I mean, the only parameter really that we've been given is that it has to be under 500 words, which generally, this is just, I'm able to talk about the dates and when it's gonna be held and who's coming and their talk and maybe a sentence or two and include it all in there for under 500 words. They do not charge us for special articles. And I've used that with other events that we're having here as well. The community calendar, we are not the only organization that's set up in there and no, we don't pay for that. We did at one point, but we canceled that just kind of for budgetary reasons and kind of tightening it down. We used to do a weekly, it was called Did You Know? And it was just simply an ad in the paper and we could use that. I mean, we used it for a wide variety of stuff, but we could say like, oh, did you know? And then something about the library, but we've canceled that. So, we really try and limit the, I mean, we just don't have a huge budget to be spending on. So, we pull from what we can. But I mean, I can certainly relate to the person that was saying they're hesitant to get speakers because they aren't sure of their turnout. One thing that you might also consider, I know that worked well is that we had, it was actually one of our staff, she no longer works here because she retired, but she came and she talked and she's pretty well known in the community. So, she was talking about it at her church and her friends. And so, she had a lot of people that came to hear her talk. They can promote them. I mean, that's when, absolutely. Right, right, you know, I mean, if it's something that they put on their Facebook page or on like their personal Facebook page or they send out maybe a blast email that's like, hey, I'm doing this thing, come and support me. I mean, I know that it's not really the speaker's job to do that, but it certainly is a way that to think about getting additional people in. Yeah, we have a lot of tips from other people about how they've done it. Someone says they put the info on a screen saver on their computers. And depending on the group that's targeted, they send out flyers to the local schools so the students can learn about it or they can then bring the flyers home to their parents. And a couple of comments about the bathroom stall thing, they've seen it work really well in a department store announcing their job fairs and another library does it and actually had a, particularly specifically branded it, the bathroom stall and called it the Stahl Street Journal. Got it, yeah, that's funny. And then someone is really ambitious, but they say in my small town of under 600, we have a friend, a member of the friends group who actually calls the phone book as they call it, which is their phone list to remind people of programs.  I mean, I will say that, so I teach a weekly computer class and that's something that people sign up for and so I get their email or phone number and I call to remind them and people often appreciate it. I mean, it probably wouldn't be that hard to finagle me or a volunteer that if somebody wanted to kind of be reminded about it, then sure, we'll give you a call or if people do email or if you have kind of an email distribution set up, you know, just people need reminders. We have a lot going on, you know, in our life. Online newsletters, whatever you use, use it, yeah. So some other people have some ideas that we'd ask for input on what other people have done. So here's some other places that have done something similar. Someone said they had a very successful end of the gardening season series covering winter gardening, putting gardens to bed, planting bulbs, which will come up next spring, sharpening and winterizing tools. We did it in late fall, which isn't gardening season, but it's, you're prepping for that. So that was very well attended. Someone else said they were one of their most popular ones. Our largest attendance ever was on solar and wind to power. Yes, we did a, yeah. We did a solar eyes archeletta here recently in the last fall. Mm-hmm. And someone has. And a famine in people came. Someone has, go ahead. We partnered with the extension service for a lunch and learn series. So over the noon hour, we supply a lunch and the extension service does the program. So financial planning, eating smart, whatever they want to. Someone else says to be very good, and this is good too, going, not necessarily having people come to the library, but going out. So this would really be good to do a senior center during their lunch hour. Everyone is there, they're being fed, and then you've kind of a captive audience. Sure. Someone had a very successful talk with a mushroom expert for about foraging for mushrooms. Ooh, someone, oh, here we go. Up in Northeast Nebraska, in our South Sioux City Public Library, their largest event was a Sue Medicine Man from Pine Ridge. He had 180 people that showed up for that. Wow. That is awesome, yeah. I think I would fall over if we had to watch. I don't know where I would put them. I don't even know if our whole library could hold 180 people. I don't know, you'd have to find a place to hold it. And hopefully it would be prepared to know that that was going to be happening. Right, right. Ooh, someone did a 3D printer demonstration for retired engineers. That's the thing too, you could focus on a certain group and say, we'll do a thing for you. And it's related, the library then gets, like you said, connected to them. Okay, I have some questions. Oh, the stall thing. It was a stall street journal. So like Wall Street Journal. That's the one that somebody got me sent. I jotted that down, I like that. It's the stall street journal. Someone wants to know, oh, you're willing to travel people. And someone wants to know, do you call it armchair travels? That would be a nice tagline for those kind of things. Well, one thing that I didn't really go into is I do have, and just to kind of keep everything clear and make sure I have everything, is that when a speaker agrees to giving a presentation, I have a kind of, it's somewhat generic form that I send to them that does a few different things. It asks for their contact information so that I am sure to get their mailing address because of course we want to send thank you follow up cards of course to people. It also asks for a short biography about them, which is what I usually use when I'm introducing them. In addition, it asks about like AV requirements and that type of thing, but it also asks for the title of their talk. And usually people offer the title, but I often use the armchair travels or armchair tourists because that's something that I feel that people kind of are familiar with or at least kind of understand the concept. It's fairly easy to understand if you've never heard it. It's good to let them brand their own session if they wanted to. This is what I want to be the topic or the title of my event that I'm doing, yeah. And then in addition, I usually ask them to provide two to three or five sentences depending on how long the sentences are. Description that is what I use to put in the brochure that I then maybe have to edit down to put in that one page flyer that I was talking about. But yeah, I think that people often appreciate kind of having that level of involvement when there have been other people that have been interested but aren't necessarily sure what to call it or aren't necessarily sure how to present it. I'm more than happy to kind of give some input or help them with that because if they have the knowledge, I'm gonna do what I can to get them feeling more comfortable to present it. Absolutely, I do the same thing here. They're happy talking about their topic, but they're not a marketer. They don't know what's the best way for me to get this into phrase it, but from experience, you know, well, other people have said this, this, and this, so how about, how does this sound? And someone asked that form that you send them, could you make that available? Like a, yeah, if you send that to me, I can post it up when we post up the slides so that if you wanna borrow that as a way of reaching out to some of these potential speakers. And one other thing is we're kind of talking about publicizing and, you know, I did kind of promise that part of it is kind of doing it with a low amount of effort. I mean, some of this certainly, I mean, it takes work to write a special article, but again, I keep it and can generally cut and paste. I mean, I have to put in that specific, you know, this series that's coming up in the spring, but a lot of times I just kind of change it up a little bit, but the brochure, what I can tell you is that the brochure from spring to fall to spring to fall, you know, I mean, it looks the same. All I do is I cut and paste from the form. And some people might think that that sounds kind of lazy to not like change the colors or whatever, but in my opinion, I think that, one, it saves time, but two, I think that people get used to kind of the form or the brochure looking a certain way and that's what they're looking for when they come in wanting to know about the lifelong learning. It's not changing it. Yeah, you're recognizing it. That's exactly right, to speak. You know, your newspaper, your Wall Street Journal, you can glance, you know, and from the corner of your eye, you can tell the difference between your local paper, the New York Times, the Wall Street Journal, you know, because they all have always formatted and colored and looked the same, yeah. Right, right, and in addition, like I said, it also saves you from having to kind of recreate or, you know, and again, kind of cutting down on effort. Yeah, and also, this is something I do here when I suggest for people doing marketing. If you have multiple places that you're doing this in, like you'd mentioned, your Facebook page, new online newsletter, website, paper, you only write the article or the promotion once and then you can just paste it into all these separate places. You know, it can be overwhelming to say, I have to market it in, like, four different places? Well, no, you've got to write it once and then just paste, paste, paste, paste. You can't paste it in your account, that's great. Yeah, that's all you have to do. It's not nearly as terrifying as it could be. That's exactly right, and as with many other things, you just kind of get faster at doing it, so, I mean, sure, maybe it'll take you longer the first time you do it, but, you know, after you've done a few of them or, you know, a couple years of them or however long it takes us to kind of adapt, yeah, things just get faster and just, that's exactly right. Yeah, someone else, one more person had an idea of a way to promote the event, and specifically in this case, using Twitter, but offer a free book to the first few people who attend, sort of like a door prize type thing and that that could be something, yeah, promotional. And then for the next one, you could say, you know, these people, one last time, here's, you know, you could win the next time. If you have, like, book sale books or something, just a few that might be able to let go is just a freebie, absolutely. Well, and it might help people to come earlier. Sometimes we, and sometimes we have people that come in late and I often leave it up to the speaker, so, in theory, the talk starts at 5.30, but if they don't like the idea that they're gonna be kind of interrupted, they're certainly welcome to wait a few minutes. Usually they just go ahead and start on time, but people come late, so yeah, that's a good idea for a few reasons, but especially to get people, you know, in their seats by 5.30. Exactly, the first five people in, get this paper back, whatever, yeah. And we have a little, just we'll do this final one, since you're about up with your time here. Do you ever do talks on current events or things that might spark debates? For example, political issues, climate change, so things, supreme court cases that might impact daily life, something that might, you know, create more of not just a presentation, but a actual really back and forth interactive type thing. Yes, we have had a few of those, and I think that they've gone relatively well. We have, coming this spring, we have Judith Reynolds, who is, she's kind of a political cartoonist, and she is the one person who's coming from Durango and it was part of the lifelong learning lecture series at Fort Lewis, and she's gonna be talking about, kind of, when satire becomes sacrilegious. And I do wonder, with this being a political year, I mean every year's a political year, but since this is a voting year, I'm considering it really a political year. I do wonder kind of what level that will bring people. And then we also had last fall, I think it was, we had a gentleman come and he was speaking, he had done a lot of traveling to other places, and you wouldn't really necessarily think that would kind of spark a big discussion in terms of kind of culture and how people are viewed, but it really did, and I remember thinking, okay, all right, you know, just kind of wondering, is this going to become a heated debate that's going to be a problem, or just kind of a heated debate that people will be interacting with? Right, an interesting discussion. Right, I don't necessarily, I mean, I would say try it. I mean, you know, if you find that you have higher attendance at those, then keep on scheduling them. Yeah, I haven't done a ton of those, but I have certainly had some that I'm like, okay, we're having a good discussion here. People are asking questions, or people are making a lot of comments, really, and there's a lot of back and forth, and that's... It's good, and it can be good or bad, they're engaged, and that's what makes a difference sometimes. And there was one that, that same one that I was talking about, the guy that had kind of traveled around and was kind of talking about that, I mean, there were so many people interested in what he was saying, that the library closed at seven, but because I'm here and I was like, well, okay, let me see if I can get a co-worker who's willing to stay after, and we just kept, like, the library closed, and they turned off all the lights and all the computers, except for the room that we were in, and people stayed, and... If you want to stay, and I was like, okay, yeah. The talking will facilitate that, absolutely. I mean, and I don't usually do that, because again, what that requires is that I get an additional co-worker to say that they're willing to stay, but I'm fortunate that on that Thursday night, there's somebody that it doesn't take much to say, hey, can you hang around for a little bit? And yeah, totally, no problem, and so it's nice. That's cool. Because again, you have community engagement, then keep them engaged, you know? Yeah, keep them happy. All right, that was the last question we had up here, so I think that will be good to perfect place to wrap up for your session. Thank you so much, Meg. That was very useful, and lots of cool ideas that I want to see some libraries around here doing. I would attend to so many of those things. So many of those. Thank you, thanks again, everybody, for attending, but also, like I said, I was jotting notes because we're into sharing, so yeah. And I would love to hear from some of you, so I hope that some of you did take up the offer to jot down my email. I'd love to hear about how things go there. Yeah, share, absolutely. Great, thank you so much, Meg.


Welcome to the second installment of a series my mother's now calling Pretty Good. Sequels are the topic on this episode of Guru Hub Presents, Movies Reloaded. It's a working title. Let's begin. 2018 is just getting underway, but that doesn't mean we can't look ahead to see what's out there. According to my seven seconds of Google research, six of you can look forward to an Angry Bird sequel. And a third, Now You See Me. If they don't call this one Now You Three Me, I'm going to be hugely disappointed and I will boycott based on principle alone. Speaking of movies that shouldn't have more installments, Nutjob 3 is in the works. Confirming my theory that people will watch anything. Remember 2017's 47 Meters Down? I don't, but another installment's coming regardless titled 48 Meters Down. So expect at least a full meter's worth of higher stakes. Deeper stakes. Pixar has a couple movies I'm actually looking forward to, like Toy Story 4, which will in no doubt restart a new trilogy in that franchise. And the Incredibles 2 can't come soon enough. Big takeaway here, if the first film's even remotely successful, you can bank on a sequel, a prequel, or even a couple side pulls to get in production. Star Wars is a huge alien cash cow. An alien cash cow Disney attends on milking until that b***h is bone dry. The Han Solo prequel is set to release this year and an Obi-Wan Kenobi movie has been confirmed. Here's a couple of my ideas that are somehow even worse than those. The first one's simply titled Phasma. A prequel story about one of the biggest punchlines in the new trilogy. It's essentially going to be two and a half hours of her doing basically nothing, yet somehow becoming a prominent character in the new Star Wars canon. Next up is Watto. This is a tip of the hat to the Star Wars prequels that only 10% of the audience likes. However, since those viewers are so obnoxious online, you would think that number's closer to 90. I have non-Star Wars ideas too, such as a dark and gritty take on Home Alone. It's titled Kevin. It's a Logan-esque follow-up to the first two movies where Kevin McAllister is bitter, he's grizzled, and he's living the only way he knows how to. Alone. He's basically Rambo now, and even though the wet bandits drew first blood, Kevin will be drawing the last of it. Let's do a pointless list. Here are the top five best and worst movie sequels I put together with very little thought. On the worst side of things, we have Dumb and Dumber 2, a film that proves the first was pure lightning in a bottle that could not be recaptured. Alejandro agrees on Twitter and gives a nod to the raid 2. Zoolander 2 goes in the fourth spot as another movie that came out over a decade after the original. It provided almost zero laughs and no new ideas. Caddyshack 2 is a complete mess that almost everybody blocked from memory. I only bring it up now as a harsh reminder of how truly cold and awful this world can be. How exactly do you ruin the exciting high-speed bus chase from the first speed? Well, for starters, you can make it a two-and-a-half-hour snail's-paste pursuit with two vehicles, the back only being able to catch up to the front ship when it runs out of gas. That was actually the plot of The Last Jedi.  Die Hard 5 is just the worst. I felt like a Nakatomi Plaza survivor having awful flashbacks of this pile of sh**. It was the Rocky V of Die Hard. And at least one person on the internet agreed with me, so I'm not wrong. See? Look. Confirmed. Starting on my favorites list, we have Austin Powers 2, the spy who shagged me. Powers 2 brought back the great jokes from the first while adding in some awesome new characters and provided just as many laughs. The Dark Knight hits the forespot, gifting the audiences with one of the best comic villains of all time. And it built upon the solid foundation the first laid out. Here's a fun little fact for you. X-Men 2, X-Men United, is one of my favorite superhero movies of all time. An incredibly robust cast juggled to perfection. There isn't a dull moment in this picture. Terminator 2 turning Arnold's killing machine into a good guy for the sequel was already a great twist on the formula. The introduction of the T-1000, that was icing on the cake. Much like my Pokemon collection, the Empire Strikes Back is bold, it's risky, it's tough to top. And the older this film gets, the more praise it receives. It only gets better with age. Also, like my Pokemon collection. Sequels are a safe bet for Hollywood, typically. They have a built-in audience that craves more from these worlds and these characters. I'm not fully against sequels, but it is a slippery slope all the same. Thank you for watching Guru Hub Presents Movies, Revolutions. It's a working title. I'm gonna leave you with a few more comments from the viewers. Tony digs the Captain America sequel, but he wasn't thrilled with the odd Man of Steel follow-up, BVS. I'm in agreement with UTDog, that's what I call him now. We're best friends. Jaden, much like myself, loves all the Potter installments. But he's not too thrilled with the latest Pirates of the Caribbean film. I think it's the latest. I stopped caring so long ago. Alright, that's the show. Until next time, I'll see you in the future, Mr. Powers. Dr. Evil, Austin Powers reference. This is a movie show.


Residents at a Palestinian refugee camp in Gaza city searched through debris and moved people out of damaged buildings on October 9 morning after an Israeli airstrike explosions have been seen across Gaza on Monday morning as Israel launched retaliatory strikes against Hamas after the militant group launched a surprise attack the day before. Without warning, they hit us without any warning. It was AF-16. There was no warning, nothing. When you can see the destruction, look for yourself. One unidentified man at the Shadi refugee camp told Reuters fighters from Islamist group Hamas killed 700 Israelis and abducted dozens more as they attacked Israeli towns on October 7. The deadliest incursion into Israeli territory since Egypt and Syria's attacks in the Yom Kippur war 50 years ago.


This video will show you how to contact a hand-in-hand technical team. If you encounter an issue on the platform or you are unable to see or download data or have a suggestion how to improve the platform, you can send feedback to our technical team by clicking right below on Give Feedback button. First, you will include your name and last name. Second, you will include your email address, especially if you would like the team to get back to you. Then you will choose feedback type from drop-down list, which will help the team resolve the issue quicker. Finally, you will include your comment or question in the box below. Once you include the comment, you can click Send, and the team will shortly contact you. Another way to contact a hand-in-hand special platform team is sending an email to fau-data-fau.org.


Hello, everyone. My name is Adrian Otto. I'm a principal architect at Rackspace, and I work on OpenStack. I'm the chair of the OpenStack containers team, and I'm also the PTL for Project Solem. I had a laugh today because it's the first time I'd ever seen, or at this conference is the first time I'd ever seen a line for the men's restroom. A line out the door, in fact, which reminded me of a joke that I learned when I was a child, and it goes like this. Well, just show hands. How many of you are Americans? So maybe a quarter of the room, American. So if you're an American when you go into the bathroom, and you're an American when you come out of the bathroom, what are you when you're in the bathroom? European. All right, let's go. About seven, I guess, maybe eight. Yeah. So I'm also a father of four, so I'm really into like the eight-year-old humor. So we're here today to talk about containers and how to use containers in a multi-cloud environment. So I've sat through a lot of Docker-related and container-related sessions this week. Most of those are trying to teach you what containers are, how to use them and showing you demos. Very few of those talks were about actual production use of containers and production use of Docker and suggestions for how actually to do it. So I'm going to give you a little bit of advice in my presentation, because I'm actually using Docker for production every day. So an application that wasn't written for the cloud is not going to be multi-cloud in the sense that it's running in two clouds at once. It will only run in one cloud at a time. So what we're really talking about today is cloud portability, which means that your application can be in one cloud or another cloud, and you can use a container as an instrument in order to move your application from one cloud to another, not like this, where you're straddling two clouds. Now, you can do this if you want to. There are tools for doing this. If you're writing a new application, you can write to an abstraction API that will let you create cloud resources in different clouds, and you could use it concurrently. But in order to do things this way, you need to be writing an app that's new. So if you have an existing application, you want some way to still use it in multiple cloud environments. So here's the methodology. First, you containerize the application. You use a Docker file to create a container image for that application. Once you have the container image, you store that in a repository, and then you set up Docker to run on your cloud servers. You back up your data, put it into the target cloud, and you load your application from the image, from the container image. And once you've done that, you can load your data into the application. So that is the recipe for running pre-baked applications in the cloud. I think that concludes my presentation. We can all leave. Anyone who's tried to do this before knows that there are plenty of gotchas in trying to run a cloud application. And when I talk about running cloud applications in containers, I get a lot of questions. People are thinking about, okay, well, first of all, what is Docker? Let's get that question a lot. Probably a lot of you are probably up to speed on what it is, so what kind of glaze over that pretty quickly. Second, they don't know what a Docker file really is or what the inputs and outputs of it really are. So I'll explain it in enough depth for you. An image of repository is something that you all probably understand, but don't know that you already understand it. So I'm going to make sure that we draw the parallels so that it's very clear. People say, yeah, Adrienne, that's nice if my application only ran in one container, but I have a big gnarly application. What do I do? So I'm going to talk about that. If my application needs a separate service that's a prerequisite, how do I get the prerequisite deployed? And what if I just have a ton of data? So container is not a silver bullet for solving all of these problems, but there are best practices for dealing with these issues. So first, answering the question, what is Docker? So some people say it's a way for bundling and distributing and deploying applications. I just say it's three things melted into one. It's the feature from the kernel called C groups, the feature from the kernel called namespaces, and a container image. And those three things combined are a Docker container. So a C group and namespace functionalities have been in the Linux kernel for six years or more. It's stable. It's been used by LXC for many years. The concept of a container image is relatively new. Docker has been around less than two years. It's only been real for about maybe a year. So people are still trying to get their minds around the concept of a container image and its layered construction. So let's get into a Docker file. So my eight-year-old son asks where do babies come from? I wish he would ask me where containers come from. So I could tell him that containers come from Docker files. Well, what a Docker file does is it says you're going to extend from a base image. You're going to do some stuff. And then when you're done, the output of this is going to be a container image. So all of you who have compiled software before have used a make file.  So this Docker file says it's extended from CentOS, meaning these commands that are run are going to add to a base CentOS operating system environment. Here I use a run command, which means as I'm building this container in my build environment, I'm going to run this command yum install. And it's going to put Apache in that environment. I'm going to expose port 80, meaning when I create my network namespaces around this container when I start it, port 80 is going to be available so that it can be accessed. Add is a way to add files from the current build directory into the container image at the location you specify. So this is take the start.sh script from the current directory that I'm running Docker in, and put it into my container at the location slash start.sh. And then cmd just means this is the default command that's going to run when I start this container. That can actually be overridden. So if you're using entry point, you can't override it. If you're using cmd, you can override it. Let's talk about image repository for a minute. So an image repository, show me hands again. How many of you use git? How many of you use git every day in your job? Okay. At least 75% of the other image users can get. Think of a Docker repository as a git repository. That's your mental model. All the same semantics work. Except the things that are in there, instead of being text source files, are binary layers. Okay. So think of it like each layer in a container image is like a block snapshot. So if I had a block device, I took a snapshot of it, a copy-on-write snapshot, and I started modifying it. The same concept applies to images. The one that you're modifying is actually a COW of the base. So when you want to start working on an image, when you want to start using it, use pull in order to pull it down.  Well, Docker will automatically pull. You don't actually have to say Docker pull. But if you want to pull something and not run it, or you want to pull a whole bunch of different things, this is how you do it. You Docker pull. There's also a commit. Just like in git, if you've modified your source code, you make a commit, and then if you want to save that back in a remote repository, you would use push. The same thing applies for Docker images. Now, if you need to deploy a ton of containers, you're going to need more than Docker. At least for now, you're going to need more than Docker. Docker allows you to start a container on a single host. It doesn't give you the ability to create a cluster of containers on a number of different machines yet. We'll talk about that later. So if you have a tool like, if you're running OpenStack, you can use Nova as a way to schedule resources. You can replace the VRT driver from KVM to Nova Docker, in which case it's going to produce containers instead of producing VMs. You could use Magnum, which doesn't actually work yet, so you can't actually use it yet, but at some point it will be true that you can use Magnum to create containers on OpenStack. You can use any of the community tools such as Kubernetes and MISOS are ways of creating containers. People refer to them as container orchestration systems or container management systems. I think those designations are a bit of a reach. They don't actually do that, but they do some of it. If you are running a ton of containers, your life is going to be very easy if you treat them like cattle instead of treating them like pets, which I'll get to again. What if my application needs a separate database server? How do I handle that? The question I get all the time. An application that has a database is not one application. It's two. You can containerize it both as a MySQL server in this case or MySQL server and your application, so you would treat the data persistence app as a separate application and then orchestrate them together. You can do that using heat, and this is how. This is a hot file that says create me a Nova server, and my Nova server depends on a Trove instance. This works today. The same works with containers. If you said create a Nova server, put a container on the Nova server, and then have that depend on a Trove instance. We have tools in OpenStack today to do the orchestration. This is my favorite one. Yeah, Adrian, but I have a lot of data. I can't fit all my data into a repository that's holding binary stuff. That wouldn't make any sense. This is an oversight when people are like, yeah, you should be able to run all of your OpenStack in a containerized control plane, and everything is in a Docker container. But things like Glance, things like Cinder don't actually work in containers because you can't fit enough. You can't fit your data into a container because it has a finite maximum size. By default, Docker limits the amount that you can put into a single container to 10 gigabytes. And the amount that you put on a single host is limited to 100 gigabytes.  But if you're trying to put your precious data into a container, then you're going to run into all kinds of issues. So my advice, never put data into containers, or never put data that you would get fired over into containers. I'll explain why. So what you do instead is you use a technique called a bind mount. A bind mount is kind of like an alias to a storage location that's on the host. So use the same techniques you use for managing data on hosts today. In OpenStack, we use Cinder volumes, in the Rackspace Cloud, we use CBS, in AWS, we use EBS. That's where you want to put your data. And you want to mount that on the host. Once you've got your file system mounted on the host, you want to bind mount it through to the container. So that inside the container, you're going to be using the storage directly on the host instead of trying to save it into the container image. So if you want to use Docker with more than one cloud, one way to do it is manually install Docker on every host that you want to run it on and manually start getting shells on machines and running Docker commands on all these hosts. Another way to do it is to use one of the ecosystem projects that was announced in June this year at DockerCon in San Francisco called Swarm, Libswarm is the project name, SwarmD is the tool. And what this is, is it's a way to put a pluggable API on a host of your choice. And the thing that goes behind the plugin interface is a distributed system. So you can have a back end on SwarmD, let me explain the front end first. The front end of SwarmD is a Docker API. So when you interact with it, it looks and feels like a Docker REST API. On the back end of SwarmD is this pluggable interface that can connect to a distributed system. So on the back end, you could have AWS, you can have digital ocean, you can have rex-based cloud, you can have open stack, so on and so forth. And so you would run SwarmD in order to get that API. And you would extend Libswarm if you want to add new back ends. Now for each back end, as you create additional containers, you're going to end up filling up the cloud servers that are servicing that back end. And when they get full, SwarmD will automatically add additional back ends for you. So you'll get more and more and more cloud servers as you add more and more containers and as you stop those containers and you cause those hosts to become vacant, it will kill off the cloud servers for you. So to some extent that is a simple orchestration. There is something brand new. As of a week ago, Monday, this was announced in the global Docker hackathon, or global hack day, I should say, called Docker hosts create, which I'll show to you today. And how this works is you can automatically set up new hosts that have the Docker API on them by running a command in Docker itself. So it's like having Libswarm capability built into Docker that you don't need to add something extra in order to consume. And that has today support for Azure, DigitalOcean, and Rackspace. So with SwarmD, you have the ability to talk to an API endpoint that will show you a collection of servers. And you can have multiple API endpoints. So you could have a bunch of cloud servers running on Rackspace, running a whole bunch of containers, another bunch of cloud servers running on Google Cloud, and you could see a singular view of say a Docker PS command that would aggregate all of those containers into a single output. Now this only makes sense if you're treating your servers as cattle not pets. Now if your servers have names, if you care if they die, then you have pets. And you can't have any love for pets if you're using Docker images for the reasons I've mentioned relating to where your data gets stored and how you treat the image in a Docker repository. So you need to have a Docker file for if you want to do this cattle scenario, I suggest that you have a Docker file for every application. You have Docker images for every application or layer of an application component. You deploy all your apps into these containers.  Any of those will be fine. And you need some form of centralized logging because you don't want to persist logs in your containers, you want your logs to be in a remote location. So I talk a lot about immutable infrastructure. In order to have a scenario where you build one time and you test or run many times, you need that artifact. After you've built your application, all of its dependencies are contained with it. The reason why we do this is because everybody who doesn't have a good way to bring their dependencies along with their application ends up having multiple environments. They have an environment for dev, they have an environment for staging, they have an environment for production. Usually production is the way things looked a couple weeks ago, staging probably a little bit different than that. Dev definitely much more current than that. And every time you move your application from one environment to the next, there's an opportunity for there to be drift and it doesn't behave the same way in a different environment.  So by building your application into a container image, all of its dependencies go with it. So it will behave the same way, assuming you're injecting your configuration using environment variable injection. It will behave the same way in production and staging and test. Okay, so before I show you a demo, the new feature that I'm talking about is called Docker host management. It's in Docker issue 86 81. So you're welcome to check that out. There is some proof of concept code that's already out there and already working. There's also a new thing called Docker clustering. So this concept of a grouping of Docker hosts that work together as a singular unit is now being implemented in Docker itself. And there's a spec for that in pull request 88 59 and Docker Inc has already built an implementation against this. The implementation is not yet open source because it doesn't meet their requirements for release. It doesn't have any unit tests. It's kind of written as disposable, but the concept does actually work. So let's go to demo. All right, so what I've got on this machine are two scripts. So this one is for creating a host on digital ocean. This one is for creating host on rack space. So we can go ahead and run before I do that actually. Let's look at Docker hosts. So what this is showing me is that to start with, I'm just running Docker on a single machine and it's talking to the local Unix socket. I can create more hosts. I can decide which one of them is active, meaning which one if I'm using the Docker CLI on this host, which one my commands will be relayed to. You can kill them, you can remove them, you can SSH to them, which is really handy. So you don't have to have an external system to keep track of all the encryption keys in order to shell into these remote systems and a bunch of other things. So let's go ahead and do the create digital ocean one first. So you're going to run this one in the background. And we'll do the same thing for rack space. Now on digital ocean and rack space, this storage for these systems is all based on SSD so they load pretty fast. It only takes a couple of minutes. So I'm going to wait for this to go. When I'm done, I should be able to show you running Docker commands on the remote system. This originally started as LibsWarm code. Rack space and Google and a few others including Docker worked on the LibsWarm project together and built a lot of the logic and code that got put into this command. And about three weeks ago, Docker reached out to us at rack space and said, will you work with us to build a back end to the Docker host command that would work on the rack space cloud? So the one we demonstrate this at our global hack day, it will work. And so we took a lot of the source code that we used in LibsWarm and ported it in and made this build of Docker that I'm using now. So I showed you the two scripts. The first one I ran was to create a host on digital ocean which completed is now called deep blue. And it created another host on the rack space cloud which I named Adrian. So now if I run Docker hosts again, you'll see I've got one here and one here. So right now the active one is rack space. So if I run Docker PS, there's nothing running there. I can say Docker run the first time your container runs, it downloads the base image which is what it's doing right now. And that container is now running. So if I run Docker PS again, you can see this is running on the rack space cloud even though the Docker daemon is running here locally. I can say also, oh, okay, so the command I ran says Docker run, meaning create the namespaces and run a process in that C group. DashD means run it in the background. It's based on the image CentOS with the tag CentOS 6. So you can run different, so it's just like Git in the way that you have a branch name and you can have tags. So you can think of this as a branch and a tag. So I'm getting the CentOS 6 version of CentOS and I'm running the command sleep 6000. So it's showing you that I'm running sleep 6000. I started it a second ago. Well, you see that little star next to active? That host now is on the other one. So if I run Docker PS here, you're going to see there's nothing running, right? So I could say, okay, I want to run that same command there, except I want this to be a different command. You can tell where it's running. So if we go active back to Adrian again, you get the idea. So I intentionally made this presentation relatively short because I wanted a chance to have a real Q&A session. Can we bring out the lights? Because I can barely see you. Okay, so you had a question here in the second row. But I was talking about storage. The device mapper configuration is what's limiting you, yes. That's right. Yeah, how if you're using the device mapper backend, what it does is it creates two files when you when you initialize Docker for the first time. It's got a metadata file where the container information is stored and it has a sparse file where the actual data is stored. And the sparse file by default is a is a 10 gigabyte sparse or is a 100 gigabyte sparse file into which it expects 10 gigabyte containers. So that that is a limitation of that storage driver. But the nice thing about Docker is that it has a pluggable storage engine. So if you wanted to put a superior storage system under it that would manage it in a smarter way, that's certainly possible. So they're currently, to my knowledge, two implementations for backend storage for Docker. There's one based on AUFS and there's one based on device mapper. Better FS. Sorry. Question. Yeah, don't use containers as a security instrument for multi-tenancy on the same host unless you know exactly what you're doing and you're an expert in host security. The Linux syscall interface is hundreds of commands.  It's very you know the only thing you can really do is wrap a mandatory access control around it like an SE Linux policy. The trouble with that is once you've done that and you make a policy that's restrictive enough to keep people to running just a small set of instructions, the range of applications that you can run on your cluster or on your on your host gets reduced. And a policy is on a host by host basis, not on a container by container basis. So all apps that run on that container need to conform to the same policy, which is a which is kind of a trouble. So I would see containers are a great way to make your applications more portable, right? In the multi-cloud use case it makes a whole lot of sense. It's a way to bundle everything up. It helps you with immutable infrastructure. It helps you stack more more running applications on the same hardware. But if what you really want is a multi-tenancy scenario you either need to be an expert in host security and be doing very smart things, or you need to be using virtualization in combination with containers. Did I answer your question? Well, where where the minions run is what's important in Kubernetes. Where the control plane runs is kind of a non-issue, but the minions are the location where you're going to start containers. So in the Kubernetes use case you would make sure that your minions are deployed onto virtual machines instead of being deployed onto a bare metal host that's going to have multiple different tenants running potentially hostile workloads on the same host. Now I'm not saying it's a bad idea to do it if you know what you're doing, but you need a lot of security prowess in order to, and kernel prowess in order to succeed at making that a reasonably secure environment. There's a lot of potential pitfalls that you can get trapped in. I'll get to you in just a second. Right. Config files should be injected using environment variables to the extent that's convenient. You can also use something like an etcd or a zookeeper to hold your configuration data, pull it down and generate the config file right before you start the application. That's fine. That's fine. You can do that too. You can bind mount configurations, but then the configurations have to actually be on every host that you plan on running the containers on, so you've got to still solve the how do I distribute that. So if you're using Docker as a way to simplify your configuration management, then you haven't really simplified it as much as you could taking that approach. Whereas if you make it so that you're injecting your, the configuration you would need within the container into a blob store like an etcd or a service registry or zookeeper or something like that and you pull it down and generate the config file on demand, you're in much better shape within the container right before you start the application. If you can't inject it using an environment variable, I didn't show how that works. I didn't show the environment variable, but you can use dash e and put a key value pair there. So you can say dash e adrian equals tall and then you'd have both the key and the value available in the in the shell environment where you're going to start applications and the Docker is going to run command itself. That's right. So injecting configuration of runtime is the best practice for immutable infrastructure. Right here. Well, it's going to be higher performance than running them in a virtualized environment for one thing. How do you get the containers to talk to other containers is the kind of unanswered question. There is a project called weave that attempts to address that question. It has some potential architectural constraints. It's still early days. I'm sure we can solve these and make it more scalable, but it's one way that you can make containers speak to other containers using an overlay tunnel network. If you have an application that does a ton of IO from my experience, like a ton of network IO, I try to get as many things out of the way as possible, but using a container doesn't put anything in the way of the actual data stream. Whereas virtualization, there is actually that IO gets virtualized before it gets sent down to the CPU and then out the network interface. So in the container use case, you're not going through any virtualization layer. You just have a namespace around that so that your view of what network interfaces you have access to or have in your view is limited. I'll give you an example of this. We have a product in Rackspace called cloud databases where we offer hosted database service. We run that service in containers so that we can get high IO both to the distributed block store where we store the actual data and over the network for that very reason. With some exceptions, I mean there is an additional bridge that when you're running inside a container, when you're using Docker, there's an additional bridge and you typically are mapping your network connectivity through a TCP port. If what you're doing instead is just creating a container that maybe doesn't have a network namespace at all, it's possible to do that. It's possible to make a container that doesn't have a network namespace at all and is just using the host networking straight up. So you wouldn't have any additional bridges. You would have raw performance exactly the same as you would if the container weren't even there. Question back here? It's not as active as it was. It's unclear which is going to win out. When Lib Swarm was initially announced, we thought having this highly modular, you know, separate in a separate repo would be more attractive. But what we found is that actually limits adoption when it's harder for people to actually acquire the tools and assemble the tools in the way they need in order to experience those features. So by building it into Docker directly, those features become more accessible. So that's really the intent behind it. Whether that functionality actually comes from Lib Swarm in the future may actually be true. We may actually be using that in a library and not having everything built directly into Docker. That's a conversation that's ongoing. Question? Yep. Are these open source? Yep. You can. If you wanted to use the code that exists now, you would have to put your source files into the Docker source tree and build your own version of Docker to produce your own Docker binary and you could do that absolutely. One of the things that's currently under discussion is a dynamic pluggable interface for the drivers so that you could just load your own without recompiling Docker. How exactly to accomplish that is still an open discussion. Any more questions? I'm sorry, I don't understand the question. It's hard to tell. In my ideal future, public clouds and private clouds look the same and you have the freedom to run the same thing on each. Docker, I think, gets us maybe one step closer to that ideal where your interface to running the application is this container image bundle. Will you be running Kubernetes in public cloud? Well, Google announced earlier this week, I think yesterday, maybe that they are trying that out and seeing how that works. So that's a possibility. Trouble with Kubernetes is that it's not designed for multi-tenancy. So unless it's considerably reworked, I don't know that it's an ideal fit for a public cloud scenario, but in private cloud, it's perfectly fine. You can still run your instances, your minions, on public cloud and run your control system in a private scenario. So you still may be able to do that. But in terms of the future, my view is that containers are useful for a particular set of problems and people are currently solving those problems using virtual machines. How do I get a clean environment in order to build my application for this particular Linux distribution? One thing I didn't show you today is that Docker can run two containers side-by-side that are running completely different Linux distributions. So I can have one running a Buntu, next to another one running CentOS, running another one next to Debian that are all sharing the same kernel, but have different user space libraries. So I could do like, you know, command and say bundle my application for all three of those different operating systems, and oh, I want to run older versions. I need CentOS 4. Well, I can just spin up a container for CentOS 4 and bundle it for that. So what I used to have an entire, you know, array of virtual machines laying around for the purpose of being able to build software and bundle it, I now can create that stuff on demand and destroy it as soon as I'm done. I can do that all on a very, very limited amount of hardware. So it's an entire problem set that goes away. Then I'll ask you a question about the future. Maybe I sidestepped it a little. Sorry. More questions? Right. So just repeating for those that may not have heard you, the question is about security and what's the best practice for using hypervisors versus using containers versus using bare metal. Don't consider containers as a newer, faster virtualization. Anybody who's trying to sell you containers as a newer, faster virtualization is probably stretching the truth a bit. It only is as secure as a, as a hypervisor in terms of a multi-tenancy environment on the same host. If you're using very advanced kernel features to put a lot of restrictions between how that application can interact with the kernel. And in my experience, once you've added all of the appropriate restrictions around an application, you end up with an environment that's difficult for you to run a wide range of applications and the performance of those applications is degraded. Almost more, in some cases more than if you would have just virtualized them to begin with. So if your goal is multi-tenancy with hostile workloads that are, that are neighboring each other, virtualization is still the right tool today to use for that. If your goal is tight, tight packing of applications that are not hostile to each other, like maybe they all belong to the same enterprise, to the same department, then it is appropriate technology for that. And if your goal is make a bundled environment that makes it very easy to distribute your application to different places, that all have a Linux kernel in common, then it's the right tool for that. So just don't try to use containers for a job that they're really not, they're not ideal use for. Yeah. I currently don't have a preference. They're both trying to solve the same general problem. CoreOS is kind of elegant in the respect that you're always running current code. CoreOS has this concept of automatically updating itself. So you're just like kind of the Chrome browser. It's kind of like only one version of the Chrome browser because every time you start it up it like automatically updates itself whether you want it to or not. Well, CoreOS is like that. It automatically like upgrades itself. But the drawback of that is if you were running workloads on there that you didn't want to be interrupted, whoops, they're interrupted.  But if you happen to be running pets, then that behavior might be rather objectionable to you. In which case you might want something similar but without that characteristic project atomic probably better fit in that case. You know, CoreOS is a startup. They're based in San Francisco. The founder is Alex Pulvy. I respect him tremendously. I work with him. He's former Racker. So we've got that connection. But at the same time, we run an awful lot of Red Hat stuff at Rack Space. So it just depends on your needs. I'll take you first in a second. It does, it does, it has an A partition and a B partition where the operating system is loaded. And when it boots, initially you're on A. And then when it gets updated, it updates B and then boots you into B. But the boot is actually a reboot. So everything that was running is gone. And then has to be restarted onto B. So that you do have an interruption in service. Absolutely. You can nest them. Absolutely. Well, OpenVZ, OpenVZ, you might make the argument it's more secure than a Docker container for various reasons. But the truth boils down to that even in the OpenVZ case, and we use OpenVZ, right? So we're fans. But the truth is still that there is a shared resource and that's the kernel. And the kernel does have bugs and they can be exploited. So to the extent that you have a buggy kernel, it is possible, even in the OpenVZ case, for somebody to escape one and enter the other. And so for that leakage reason, it's probably better not to do that until you understand exactly how to prevent that risk from happening. But yes, I didn't mention anything about the nesting of containers. You can create a container with a container inside of it, and you can create a container inside of that. If you did that with virtualization, it would be like go, go, go, go, really crazy. So we don't like to think about that. In the container case, it's really not that bad because we're not virtualizing the workload. The workload is actually running on the host. It just has a namespace around it. So when you execute things to the CPU, there's no additional layers. So the fact that I'm in additional namespaces really only matters in the PID namespace where in order to track the creation of a new process ID, it's going to be in each of the layers. So creating a process in the PID table is going to happen across multiple PID tables and multiple namespaces. So it's slightly slower to start a process in a PID namespace. But we're talking on the order of milliseconds or fractional milliseconds, really on the nanosecond scale that you would notice the additional overhead. So strictly speaking, there is an overhead running nested containers. But practically speaking, there's not. And there are good reasons why you might want to run nested containers.  A pod is a way that you group containers onto a single host. And one easy way to do that is to create a namespace, a single network namespace, and then you create containers in that namespace that do not have network namespaces.  And then you can do things like layer two communication between these without any mapping of ports. Does that make sense? Yeah? OK. Question here? Yeah. Yep. Just want to knock up a few more. Yep. So there's lots of ways to do that. To my knowledge, Mesosphere or Apache Mesos has that capability. To some extent, Kubernetes allows you to signal a scale event. Like you can change the size of the expected. You can change the declaration that determines how many of something is running. So if you had an external controller that knew when it was time to scale, you could send the signals that way. If you were using heat, you could create an autoscale group and you could use the autoscale group in order to scale up and down. Now, heat has a Docker extension or Docker, I should say, provider plug-in, I think it's called, where you can interact with a Docker resource. So you could autoscale Docker resources in autoscale group. That's another option. The trouble with autoscaling just as a general case, I like to think of autoscaling as an intractable problem in the general case. All of the implementations for autoscaling that I'm aware of that are kind of general case solutions are based on a CPU utilization trigger or some other naive trigger. And most applications that I work with do not actually scale. The scaling constraint is not CPU utilization. It's something else. So having a custom controller that's watching that something else, whether that be queue length or network saturation or memory bus activity or some other KPI that indicates when you should be scaling up and down is actually more important. So it's not as important in my view that systems have autoscaling but that they have a way that you can declare that the scaling ratio should be changed and that you have the ability to put your own custom controller that determines the scaling behavior for that application. And if you want just basic skill, skill and skill out, that's what autoscale groups in HEAT is for. Yes. Yeah, I think, you know, I can't speak for all of the community. My, from my view, the Docker community is extremely ambitious and they're willing to try a lot of stuff. I wouldn't be surprised if you see that very soon. The Docker cluster stuff that I saw a week ago is pretty darn interesting. So it does have the ability to kind of do an affinity and an anti-affinity much like we have in the affinity scheduler today for OpenStack. So having that capability built in is like the first step towards, you know, doing it multi-zone, doing a multi-geography, that sort of thing. It depends. Active-active as a HA strategy is fine as long as your utilization is always less than n minus one. So if you're... Talking about the cattle versus pets, right? Yep. That's right, by definition they're pets.  So, you know, the general advice there is you do an n plus two based on your expected capacity constraint and you deal with it that way so that you can have two components failed at any given time and the system is still operating. I don't do docker cattle for data services. So I would rely on a data services. In my case, I would rely on the cloud data service and use like Galera replication as a solution for that. You can if you understand a persistence application very well, absolutely containerize it. But capacity management within containers is basically the same as capacity management within any other infrastructure. The discipline is exactly the same. All right, thank you all. I'll be up here if you have additional questions. Thank you.