All right, Sabra Traders, good afternoon and welcome on back here. Welcome on back, of course, here this Tuesday afternoon, September 12th. I'm losing track of my days and weeks and times right now. It's all a whole loop when it comes to trading, right? Because there's always another trade, always another day, right? Obviously, I'm being silly with saying that, but great to see all our students and members alike here inside our live trading room. Mario, Don, Kathleen, Leda, loud and clear from all of them. So good to go across the board and good to go across all our members inside our social streams right now, Facebook Live, LinkedIn, X, YouTube, et cetera. We hope that you enjoyed our weekly workshop earlier today. Traders Talk, our weekly Q&A. We'll have that recording up on the student portal, at least coming up momentarily this afternoon. There we go. Nice catch from Mario, one of our longtime students here. Mario Kay got 62 cents on the WeWorks trade right now. He was in from 4.64, so really nice entry there. Perhaps off the initial breakout at 2 o'clock. If not there, then maybe by the time it pulled back and Nebbeda's support led to the extra pop-up hire that he had called out from that point. And yeah, right now he took the money and ran a really nice catch from Mario.  This thing has been a mess. If anything, even though this order got pulled at 4.90, this still was a pretty big level to work off of, but it wasn't showing up until like nearly 12 o'clock. So this has been a mess to work with from the beginning in terms of finding big levels. Outside of this 4.90, you could focus on psychological level 5. So the combination of those two now, 4.95 bucks, preferably now at 5, and a hold over a higher lows. For this to try and rip and run much higher. You know, Kausda brought this up earlier in the morning meeting. The stock took a huge hit over a period of time. It's been reversed split probably a few times over. I don't think this was a $600 stock back in 2021. So it's a short squeeze.  It's going to fall off pretty badly. So we just don't want to be on the wrong side of that, right? We got to play the higher low game, play the game of resistance becoming support. So for right now, it definitely is playing nice to us here. WeWorks, I'll put this on our watch list to begin. All right, so what I will do though is also put the AXLA on our watch list. This has also been pretty strong taking us into this meeting. You know, another stock that got crushed over a period of time. And from like even the end of last week, I know Rich was calling this one out himself. It popped up a little bit. And hey, thankfully for his sake, and a few of us that were watching this trade last week continue to push up more today. Again though, it took a huge hit from a couple of years ago, a few years ago. So one of those short squeezes, it could be one of those days where with like AMC running and GameStop from earlier, might have all those like Wall Street that people out there right now trying to find the next big short squeeze. Which means hey, it could be a fun afternoon. I just don't want to build up like a crazy watch list. You know, right now these two, definitely rightfully so. We're going to start off with them, the WeWorks and the AXLA. All right, so I mentioned GameStop earlier. May as well check in on that. GameStop not looking too hot now. AMC was looking really nice earlier, going into like the mid-afternoon. Rich called out a nice pop. I commented right away. Yeah, it's a pretty nice pop at the time. Well, from there, unfortunately, failed to hold higher lows and failed to continue, obviously. But unfortunately, back down, this thing went. So not looking as pretty the AMC. I'll tell you what, really the whole market. It looks like we had a pop and drop collectively here, right? So a couple of trades otherwise, before we officially begin folks, just from top to bottom. The Tesla trade, we're going to put this on our watch list for the afternoon. TSLA and TSLL, the ETF there. So, hey, if you don't trade the option on Tesla, that's okay. You could trade this ETF, TSLL, but coming off at 270, we were calling out the short with lower highs and the drop-off there with the spy that we had there. So we were looking for a nice pullback on Tesla, and I think there could be more room to go. Next big support, 265, but then even a little lower, like 264.30 cents, roughly. That was back from yesterday, right? We talked about that even in our workshop earlier today. So, yeah, Tesla and TSLL, we'll put on there too. All right, so let's really just kind of skim it here from top to bottom. A few cheapies in between here, so we'll skip those. Up. Definitely doing its namesake here, isn't it? Up 33% going up right now, and yeah, it's at the highs. You know, tiny spread, not too crazy. Definitely going to put this on our list here too. Keep it going, we keep it moving. Skin, what is this? What company is this? Beauty Health Company? Okay, that's a little pop from earlier today. That looks like another short squeezer, just kind of rebound day. Stock took a huge hit over a little while here. Oh, from 30 all the way down to a sub six, and now today getting a small squeeze back up. So, I'm gonna put this on our side list here. What is this skin? I'll come back to it at the end if I need to. That WeWorks trade already at 5.45. So, without there really being much historicals, or without there being much volume-based levels to work off of here on Bookmap for the WeWorks, I would try and contain it to a whole number of levels, or looking back on the historical charts, we'll figure something out there. PIII, it's at the highs. It actually looks good like a chart. Order book checks out nice. The only issue is that it's trading little to no volume actively per minute. Only about like 2,000, 3,000 shares a minute. So, it's not really the type of boost that we wanna see right now. So, I'll come back to it if I need to. KCSP, same deal there. CRNX, this actually is also at the highest too. Little more expensive, but still within our wheelhouse. All right, so let's see if there's anything else looking just better. I mean, really gotta try and be picky right now, heading into the end of the day today. We have the CPI report out tomorrow morning, PPI out on Thursday. So, I would normally expect a more hesitant market heading into the close, but the way the market's popped and dropped earlier, perhaps we could see more of a pullback. You know, more of a short close here to work with. Ray had a nice pop earlier today. Good swing, it looks like from the past week. All right, so I'll tell ya. I mean, not much else that I see on the gainers list, folks. If there's anything else looking good, up more than that 5% that we ask for, type it in the chat board now, definitely do so. Definitely wanna work together as a team here. So, all right, we'll hop over to the losers list right now. Not a whole lot that is name brand, not a whole lot that is easy to borrow, so it makes my job a little bit easier here. This one is easy to borrow, not the lows. I actually like this one, OFIX. Wow, nice little trend down. From a zoomed out look, it looks flat, but you know, a little slow, but it's trained down nice. Order book is, for the most part, liquid enough. Is it at all-time lows? And I'm getting close. Gonna go all the way back to 2009, really, what, from the 2008 crisis? That's crazy. So, this stock ended up dropping all the way down to as low as 865. It has a ways to go to get there, so, you know, that's not really too relevant now, now that we saw that all-time low. It's kinda just for show and tell, looking at it, but as far as it's short to work with today, heading into this market close, not terrible, I'm gonna put this on our side list, at least, and come back to it. Oh, so, talking about name brands. Well, this is the one that is, like, really name brand Oracle, right? Obviously, took a big hit this morning off of earnings. It was a great short earlier, even broke lower just before. If it wasn't bouncing up as well as it kind of is here, I'd actually put this on our watch list looking for new lows. And normally, for something as expensive, we already have Tesla on our watch list as a short, so, pot stocks dropped off today, those got clipped. I mean, we kinda figured that once it snapped below 169 CGC, but, you know, it was playing with the opening print 151 earlier.  Ended up continuing to make lower highs, back down. You know, I'm sure all the pot stocks making a similar move, so no shock there. All right, so, let me know folks for Grant, Kathleen, Leda, Barbara, Mario, and all of us here inside the trading room. Just let me know right now if there's anything else that missed, all of us in social.  We works obviously still pushing at 564 and change now. Lira, I guess maybe trying to inch up a tiny amount. That was a bad trade from earlier. You know, we were saying before 510 was the big level for it to need to hold over. Didn't do that in pre-market and just tanked by the time the market opened up. I'm gonna pass on this type of trade. No real need to follow this. We already have a strong runner right now folks. Wouldn't be doing my job if I didn't say to just stick with what we got right now. We works looking pretty strong and that AXLA is still looking pretty healthy. Up, going up, and then on the way down, hey, a little flat right now, but Tesla from 270, really good short on that. And I think there could be more room to see another pullback towards that 265 or 264 and change. Right now it is actually at a weekly doji level right now. Weekly doji level, 267 and change there, but it thinks it's gonna break lower here soon. So I'd watch out for 265 as support on Tesla. All right, so I think for all of us here right now, folks, that's just about it. I'll check out the sideless stocks here to wrap up. Skin, now, hey, we don't really have a big watch list now at this point, right? So that's why I wanted to toss a couple of these on our sideless for right now and skin we'll kind of put on our main list now at this point. PIII, I hope that there's more volume that gets traded on this stock going into the close. You know, 1.2 million is fine, but just very, very inactive. Like you wanna see this number here in white on my trade station chart a little bit higher. So we talk about that slightly in class, but more or less tradable, 100% tradable and great spread, good volume on the book, cheap at the highs. So I'll kind of slip it on there right now too. All right, so in total, hey, we got six different equities to work with and then the ETF, if you're counting TSLL, the Tesla ETF there. So I like what we got here, folks, starting stick with the watch list as we always say, gives the best shot to work with going into the market close, pick yourself up a nice 62 cent profit like Mario did just a moment ago there inside our trading room. All right, so hey, best of luck trading going into the market close for all of us here live. Here's my email address for all of us on social, Josh at ctutrading.com, right there, bingo. If you're interested in joining our live trading room, just scan that QR code on the top left of your screen. Unfortunately, my water delivery guy has not come yet getting those big five gallon jugs. Yeah, I'm still running dry and water right now, so that's why I'm trying to do this meeting rather fast. So I appreciate you folks understanding, but hey, we'll be right back at it tomorrow and hey, I'll be in the chat board up until 3.30 for all of us here in the cyber group. Talk to you all soon.


media access. I'm your host Emily Murnin and today joining me are members of the UC Davis Student Organization esteem which is the equity for the STEM fields and entrepreneurship. So thank you so much for being here today. I'm so glad that we're able to talk about this. So why don't we yeah so why don't we start with introducing you guys. So do you want to start? So I'm Doug Gettle. I'm a fifth-year graduate student at the chemical engineering program at UC Davis. Awesome and what do you do in the esteem? Do you have a certain position or you just remember? I'm a co-lead. Awesome. As well as Sam and Elise are as well. Okay. I'm Elise Towns. I'm a fifth-year graduate student in the chemistry department and I'm also a co-lead of esteem. Yeah so I'm Samantha Fan. I'm a fourth-year grad student from College of Toxicology at UC Davis and I'm also the co-lead for esteem this year. That's awesome. So what do you guys do in esteem? So it's a professional development group that we operate under the biotechnology program at UC Davis and we do outreach and then we also plan other events all aimed at increasing involvement in stem and entrepreneurship fields for women and underrepresented minorities. Awesome. That's so great. So how do you do that? How do you promote equity in these fields? That's a good question. For the most part what we try to do is talk about different things that can hinder diversity in the field and problems that people have had and how they've overcome them to give inspiration to other people that might be having the same problem. Alright so why do you think there is a lack of diversity in stem fields and entrepreneurship so often? Is that what you guys talk about really? Yeah it's an opportunity. I think a lot of it's the most part. I think that opportunity is a big one as well as I think it's kind of it's confidence. We talk a lot about if you see someone in a position that you'd like to be in that someone that looks like you be a woman or an underrepresented minority then you feel more like you could do that too and so we talk about how if you meet more people that have done these things then that can encourage others. Definitely so it's kind of like there's an underrepresentation that kind of causes people to do it a little less and so it kind of so your job is to try to stop that from happening. Yeah exactly. I like to bring the audience that there's still awareness about there's an equity that happening in the 21st century and how we're gonna like try to do it from a student organization side and try to bring the equity to everyone. Definitely. So what kind of events or activities have you guys done? Well so we have events in a couple different ways we've I guess our mission statement really overall is designed both to promote interest in scientific careers for younger folks as well as to also teach leadership and development both communication and collaborative skills for graduate students as well undergrad and graduate students. So we do both outreach centered events and then we've also had colloquium events each year designed we brought speakers from both industry academia and government and they've shared their experiences some of them difficulties they've had obstacles they've overcome to get where they are and to be successful as they have and so the outreach we've we've gone to local middle school and we've done some science experiments as well as a STEM career workshop focusing on different topics in science in STEM and trying to you know kind of drive interest and teach these students that you know interesting great possibilities out there for them that they can be they can they can achieve those goals and those dreams. That's so wonderful so how long has this bit organization been around is it fairly new? So I guess this is the third year and so under the current title of the STEAM but it was started three years ago under actually a different title Will, WIL, Women in Leadership by two graduate students UC Davis Jenny Lee and Nicole Schaffi and it was then renamed a STEAM last year and continued this year. Oh that's wonderful so is it just a UC Davis organization currently? Currently. Okay so do you guys have any goals for like spreading it across UCs or anything like that? I think that would be a great goal ultimately for now we're just trying to keep it running and so keep the ball rolling for the next few years and then after we're hoping that it just keeps growing at UC Davis and then we could expand it to the other UCs or anywhere. Yeah that's wonderful so how many members do you guys have currently? I think we have around 45. Awesome so are there any upcoming events that you guys are currently working on? Yeah so actually we have our last event of the year which is happening next Monday. We invited Dr. DeAngeles which is the professor from John Hopkins School of Medicine and then she's going to give us a talk at GBSF from 530 to 630 about like the general equities or just the equities in general about a STEM field. Yeah. Great so how do you get in contact with all these people is there who's in charge of that? Probably all of us. Yeah yeah our our advisor Dr. Judy Chelstrom she has a lot of contacts with different biotechnology companies so we were able to get some of our contacts through her and then otherwise it's kind of looking for people that we like a lot of like LinkedIn looking for people that we think would be a good fit and emailing them and seeing what happens. Great so how do you spread the word about your organization and get people to come to these events? We send out emails to a lot of different list serves and we also had had flyers for the colloquium so it's most we have mostly graduate students in our group but I mean it's and other people can join it's a mostly a campus event but our campus group but we're open to other people I mean our our idea is equity and so we want anyone who's interested to join. Yeah and we're on TV today so. Oh definitely that'll help. We also have a website too with our contact information and a little bit about what we what our goals are. Oh perfect so yeah there are a lot of great ways to promote that and I think definitely college is a great environment to do that and so why how have you reached out to middle schools and stuff have you talked to high schoolers at all? We haven't we've actually so we did outreach events at fifth grade, fifth grade class in winters this year and that was a lot of fun and there's a lot the biotech program actually does outreach separate from esteem so I think they do it in other grade levels not just fifth grade so for now we focus with them and have had really great results but maybe yeah definitely I think targeting kids who are a little older would also be a great idea because that there's more pressure to find out what you want to do and I think a lot of the times girls and underrepresented minorities can be a little discouraged if they don't see faces and you know be reminded yeah that's definitely cool. We also there was a study I think that was said around fifth grade maybe it's not in here but around fifth grade was a time at which this at which like underrepresented minorities or girls is that right? Yeah they title it the Valley of Death sometimes. Yeah it's like the Valley of Death it's when they would start deciding whether or not they wanted to keep but keep like really like science and math or not so if they made it out of that out of fifth grade or sixth grade with that feeling that's a good sign. That's super interesting so is that why you guys are targeting kind of that area a little more? Yeah that was why we started but I mean I think there's also I mean there's a good opportunity everywhere. Definitely so when did you get why and when did you each of you get involved? I got involved in my in the first year when I was coming in leadership. Yeah I think I saw the email one time like through the listserv and then they were talking about this panelist and they invited a lot of like different speakers from either the government of governors or the academia or the industry and all those are like the leaders in like women leaders in different fields and then they're going to talk about how they actually achieve the leadership and then what kind of problems they have been facing and then how are they gonna just tackle it so I think it was very interesting and I want to get involved more for sure so I started volunteering through that year and I just become the codees and it is here as well. Same is true for me as well. Awesome so as women Samantha and Elise did have you experienced any kind of problems in when you started your science field did you feel like a minority or like? Sometimes in some of my classes I did for the most part I felt like there was just this inherent oh no you can't do this which I think that it's not necessarily exclusive to women or underrepresented minorities but I felt like I might need a little bit more push to keep going. Yeah I know I guess like when you started like people don't know what exactly that you can do they will always have doubts in you but like actually when you showed ability that you can actually tackle the tasks just the same as everyone else and then they're like yeah yeah that's great. Yeah so not too bad. Yeah do you guys have an ultimate goal in this club organization? If we can encourage any number of people be that one or hopefully more to keep going towards the science or the STEM on entrepreneurship field where they might not have gone for it then I think that we did a good job. Definitely because you know women and minorities make up such a huge part of this planet and it's kind of upsetting to think of all the lost opportunities if someone feels like they're discouraged. And companies thrive with more diversity. Yeah awesome so is there anything you guys want to let everyone know about your club? If you like STEM and entrepreneurship or outreach events and hopefully both then look us up and join us we'd love to have more people to come out and go to these events and support equity and STEM entrepreneurship. Yeah we have our website so if you want to email us and ask more information about organization and then yeah feel free to do that. So their website is biotech.ucdavis.edu slash esteme correct? Yeah perfect. So you guys have done a lot of things in the past and you're gonna be around next year right? Yeah I'll be around next year everyone else will be graduating.  Yeah but we will be moving up new co-leads of STEM as well as Sam so then we're hoping then it will just keep going every year and it's kind of we want it to be a training program where the people one year are helping run everything and honing leadership skills that then they can use the next year maybe as co-leads or in higher other positions. That's so great so as co-leads what do you guys do differently from other members? We got some more emails I guess. No yeah we probably have I wouldn't say like more responsibility like we just shared a responsibility but like we would host the meetings and then like just to tell other affiliates that what exactly the tasks that they are gonna do for the seminars or for the different events that we are going to host. Okay more organizing and planning and then delegating to other members. Great so do you guys think there are any other ways that you can try to promote your events at all other than just emailing? Probably. I mean I think that as a teenager I think it'd be really helpful to see a social media presence in some way because that's where I get like all my information now and I think if I see these events I think the word will spread really well. Okay yeah so we I don't think we have our own Twitter page. I recommend it. That's a great idea. We tried we had a hashtag. Oh what was it? I think so I think was there it was at the pun intended the esteem because I feel like self-esteem was that intended at all? Did any of you kind of recognize that? Because I feel like esteem self-esteem is such a huge part of being able to project confidence. Yeah yeah so I love that. Yeah the name was come up with by the co-leads before us so I think it was intended. There's so much fun potential. I think it's lovely and equity is so important in these fields and I really think that it's organizations like you guys are the reason that things are gonna change and they're already kind of changing pretty rapidly so thank you so much yeah definitely thank you so much for being here and being able to talk about it I'm so glad I know about this now and I will definitely share it with my friends. Great thank you. So the website again is biotech.ucdavis.edu slash e-s-t-e-m-e if you're looking for more information and look out for a Facebook page because I gave them a really good idea so thank you so much for joining me today if you want to watch any more videos you can go to dctv.davismedia.org or you can check us out on YouTube at Davis Media Access. I'll see you next time.


Hey, everybody. Matt here for Latent Sports Cards, ripping one box of 2021-22, Panini Prism Basketball. First off the line, this is for Ryan B. Good luck, Ryan. Here we go. Base and rookie silver, Evan Mobley. Great start to your box. Congrats, Ryan. Awesome, Mobley. Ben Wallace, silver insert and sensational signatures. Cam Reddish. Jalen Suggs, rookie. What an opening pack there. There's Josh Giddy, rookie red wave. There you go, Ryan. And gold wave. Michael Porter, junior. That's the 60. Steph Curry, fearless. Kessler Edwards. That is the laser, Danny Green and Jay Crowder. Hyper. Awesome. Appreciate it. Good luck. Kai Jones and J.T. Thor. N.T. Collegiate football. Nice. I hope I told you something good. Josh Jackson. This is Hyper. Norman Powell. Yannis. Zyre Williams. And Gordon. That's 30. That is blue shimmer. Julius Randall. That's blue shimmer. There's Dearon Sharp. Rookie Red. 299. Paul George. Miles McBride. And Zegorowski. All right. So have a little bit of room for personals. If you want something, get it ordered now and I'll get it ripped for you. Jay Chantate, silver. Christian Wood, blue. 2199. Lillard. Brooke Lopez, silver. And Chris Duarte, rookie Hyper. It's Paul. Herbert Jones and Juan Toscano Anderson. Yeah, it's up between the breaks. It takes up like it's all across the screen. But what we have in queue right now before you is just what you see up here. Just what's on the desk. It's Kyle Kuzma. Red Wave. Lamello Ball. Red. It's a 299. Lebron. Chris Duarte. Josh Christopher. Yeah, no problem. I love ripping that N.T. Collegiate football. There are so many awesome patches and stuff in there. There's Anthony Edwards, Silver, 2nd year Ant-Man. And Milano Banton, rookie Purple Ice. It's 149. It's Isaiah Thomas, 75 years. Bones Highland. This is Red Wave, Paul Millsap. And Hyper, Lamello Ball. There's Lamello Fireworks, Corey Kispert, rookie Quinton Grimes. All right, couple packs to go here. Let's finish with a big hit. Dwayne Wade, Silver and Lamello Ball. Prismatic Silver Insert. There's Westbrook. Evan Mobley, rookie. Trey Mann, Brandon Boston. All right, last pack. Here we go, Ryan. Let's see something big. That is Tip 30. Blue Shimmer, Bryce Brown, or I'm sorry, Bruce Brown. Sorry, it shimmered my eye when I was trying to make it look like it was potential. Prismatic Hyper. And a Redemption. Here we go. Nice. That is Flashback Signatures Zion Williamson. There you go, Ryan Chamberlain, Kita, and that will do it for your box. Appreciate the purchase, Ryan. We'll get these right out to you.


Shepter broke the news that Carson Wentz is out indefinitely as he undergoes further testing on a foot injury that he suffered at the end of Thursday's practice per Mike.  Well, Mike Wells, coach second year QB Jacob Eason took the starter reps at today's practice with Sam Elinger as the backup. Okay, couple quick things here. All right. Let's assume that this isn't that big of a deal.  I need a little day. Maybe he's just relaxing. Maybe it is not as serious as maybe Shepter is talking about. I don't know anything about Jacob Eason. I'm literally driving. Okay. All right. I get to a red light. Oh, this is awesome. About to hop on a bird flight in Minnesota. Have an anniversary weekend after the biggest smackdown, the history of smackdowns. I stopped the red light. I opened my phone first week, because the Twitter algorithm says, Hey, Pat, we want to ruin your day real quick. Adam Stefter bang, right there on top. Carson's out with a hurt foot. I'm like, Oh,


Single-stepping through a program is a great way of not only debugging a non-working program, but also getting a good understanding of what the system is doing, effectively in slow motion. For hardware, you can also single-step things, but sometimes the hardware needs to run at a certain speed in order to work. You can use a logic analyzer to examine the system running at full speed, and while these things have certainly fallen in price, they're still a bit on the costly side. Remember last time I said this TMS-9900 CPU couldn't be single-stepped using the clock? Link down below. Well, there's this hold signal that when you assert it, the processor finishes up whatever memory access it's doing, then asserts its hold acknowledge signal and tri-states its other outputs, and when you un-hold, the processor starts up again. Here's a timing diagram of that. We see that the time from hold to hold acknowledge is between 1 and 9 clock cycles, depending on how many memory reads the current instruction needs to execute. So maybe I can hold the processor, then when you want a single-step, you un-hold and then hold again as soon as you can. I have this retro-looking switch that I can use as a single-step run switch. Flipping it up will stop the CPU, and flipping it up again each time will single-step it. Flipping it down will let the CPU run. Quick! To the state machine! Maybe something like this. This is a mealy machine, right? Or maybe a moor? No, a mealy. Definitely a mealy. Right? Hang on, I gotta go dust off my engineering degree. Okay, quick review. Here's what you'll see when you look up moor state machines. The next state depends on the current state and the inputs, and the outputs depend on the current state. In a mealy machine, the outputs depend on the current state and the inputs. Here, I'm going to pull this output logic block into the next state logic block. Now you can see that the moor is just a special case of the mealy. It's easy to get them confused like I always do, but really, who cares? There's some state and some logic, and sometimes the output depends on the input, and sometimes not. Okay, let's have each state get its own flip-flop.  Anyway, now it's much simpler, and I can tell what's happening. Here's what's going on. We start off in state zero, assuming that the processor is being held. The hold signal to the CPU is asserted for each state with a dot in it. Now, when I flip the switch to the step position, I go to state one, then I release the switch, and we can go to state two, which releases the CPU from hold. Ignoring this bottom part where the processor turns hold acknowledge off, I go to state three, which immediately asserts hold again. The CPU acts hold, and I go back to state zero. That single step's the CPU. Now, if instead I flip to run, I go to state four. When I release run, I go to state five, which releases the hold on the CPU, and when the CPU runs, I go to state six and stay there. I can hit run as much as I want at that point, and nothing will happen. Only when I hit step will I go to state seven, and when I release step, I go to state three, which asserts hold. And there you have it. That's all the gates, and we come up with a total of six chips required, not counting the flip-flop chips. Now, six chips is an awful lot, but if you think about it, we really have just four outputs, hold and three bits of state, and six inputs, step, run, hold acknowledge, and three bits of state. That's basically a 64 by 4 ROM.  The smallest parallel input-output ROM I've found is 8K by 8, which is way overkill for this.  I can program an AT tiny microcontroller to act as a ROM. It would be a slow ROM with access times on the order of a microsecond, but for this application, that's perfectly fine. And if you traveled back in time to the 80s, you could just tell them it's a ROM with a funny pinout, and they wouldn't know any better. Heavy. Okay. I have this Adafruit Pro Trinket hooked up, because I don't have an AT tiny yet, and I have a 500 kHz clock on the flip-flops, which is the frequency of a single clock phase. The flip-flops are in this 74175 quad D-type flip-flop chip. I only needed three-quarters of the chip for the three state bits. Okay, power up. These three LEDs show the current state. This LED shows the hold signal that we output, and this LED and button simulates the hold-acknowledge signal from the CPU. Finally, this LED indicates that the switch was put in the run position, and this one indicates the step position. First, I'll reset. Great, we're in state zero, and hold is being asserted. The hold-acknowledge signal is also being asserted. Now I'll step. Great, we went to state one, then two, and hold went off. I'll press this button to simulate hold being unacknowledged. In other words, the CPU is running. Okay, now we're in state three, and hold went on again. I'll acknowledge by releasing the button, and we're back in state zero being held. Great. We can do that over and over, single-stepping each time. Now, from state zero, if I hit run, we go to state four, then state five, and we see that hold has been turned off. I'll push the button to simulate hold unacknowledged, and now we're in state six. As I said earlier, at this point we can hit run as much as we like, and nothing will happen to the state machine. When I press step, we go to state seven, and then state three. Hold is turned on, I simulate the CPU acknowledging hold, and we're back in state zero. From here, I can single-step or run again. Maybe this will work. I'll have to hook it up to the CPU to find out. I also got these displays so I can see what the address and data lines are up to while I'm single-stepping. That will probably be the next video. Anyway, thanks for watching.


Hi, so I'm the doc, I've got a hangover, a bad one, and I'm going to talk about a language called Hyde. So say hello to Karel's the catfish, that's our language's virtual master, although she looks more like an octopus, so I kind of prefer this one, he's much more badass, but anyway, so Hyde is essentially a list dialect, a dialect of Emacs list that runs on top of Python. It is a stable combination, but you would ask why. Well, the first part is that it's a list dialect, which means that the syntactic sugar, by the way I love that term, syntactic sugar, the syntactic sugar of this comes on top of Python, which is actually quite interesting once you start going into say, mathematical computing, which is something I'm into, plus the part that there's very, very easy interrupt between Python and Python. As you know, Python happens to have a lot of languages for math and science, so richness doesn't have, I mean, not a lot of other languages have that kind of ecosystem. So it's actually not a bad mix, it feels quite intuitive, but it also has its disadvantages, which I would like to just enumerate before we go any further. Seeing that this is functional gone, unfortunately, Hyde is not that functional yet. So things like immutability don't really exist beyond what Python provides. So if anybody's familiar with Python, couples are an immutable data structure. Apart from that, everything else is mutable. Everything else can change on the fly. Also, Hyde does not have one ads. There are unofficial implementations. Somebody's trying to put a closure, the closure languages implementation on to Hyde, but it's nowhere near complete. However, having said that, doesn't mean that Hyde is not useful. It's got a lot of things going for it, and I hope to enumerate them as we go along further. So, yeah, very easy to get started with Hyde. You can just do a pit install. Pit is the Python languages library management system. And Hyde has a console, it has a wrapper. It also comes as an interpreter. And what Hyde basically does under the hood is it compiles Hyde code to Python abstract syntax trees, which the Python interpreter can then run. So you can also see the generated Python code. You can optimize that further. You can also see the abstract syntax tree. If you ever want to hack on top of the language, it's a little like LLVM. You know what's going on under the hood. So you can implement things better. So yeah, as you can see, misplies, misplies, syntax. So let's do a deep dive into it. Like, you know, Python uses postpix, sorry, let's use a postpix, let's use a postpix. So let's dive into it. So, yeah. So I'm going to go ahead and get used to it. So I'm going to go ahead and get used to it.


Hi, everyone. My name is Dr. Steve Jankowski, and I'm pleased to be presenting at the Wiki Workshop 2023, where I'm going to be talking about the topic of global platform governance, multilingual policy development on Wikipedia. The project I'm working on, I'm the principal investigator, along with Dr. Claudio Salis-Pueno, Dr. Jaco Kemper, and West End Sabah, where we're working on this project that I called Slow Editing Towards Equity, where we are investigating Wikipedia's policy environment to engage and understand how it is possible to increase the equity of policies on Wikipedia. So the research background and research problem is kind of obvious where this comes from. So in 2020, in the taxonomy of knowledge gaps, it identified numerous issues that could be improved in order to allow Wikipedia to reach its goal of giving access to humanities knowledge to everyone. And while Wikipedia's policies are useful for creating high quality content, they can be major barriers for diverse content inclusion. So partly this has been identified. One of the issues or the elements of Wikipedia's policy environment is that the policies tend to be conservative. They were sort of calcified many years ago. There's a lack of activity now. And so we want to investigate some of the ways that we can increase the capabilities of policies being an instrument of increasing equity. Of course, there are numerous studies that have been engaged. We look at Wikipedia's environment, looking at its providing feminist critiques of the environment, as well as individual policies. So this is sort of where we're starting from. This research is based in theories with immediate studies, well, feminist science and technology studies, mostly concentrating on the aspect that our values, our practices, our beliefs oftentimes can be encoded into the technical and political structures that we engage with. Right. So, you know, unpacking those structures allows us to understand how politics is at play in something like Wikipedia. Okay. So that leads us to this moment to think about which socio-technical actions could be followed to reform Wikipedia's policy environment. This is our overarching sort of research question. It's quite broad. And so we need to dive in a bit deeper to get it specific. So our research questions are based on two premises. The first one, any attempt to change Wikipedia policy has to be supported by pre-existing practices is necessary to know what those practices are. And so Wikipedia prides itself in the precedent of community practices. And so any attempt to adjust it needs to be based in what's already happening. And the second premise, Wikipedia's have already attempted to make the platform's policies more equitable. What are they? What successes did they have? And which failures did they encounter? So currently we are working on the endpoint of research question one. How do Wikipedians develop successful policy proposals across language additions? And then afterwards we'll be addressing how are these practices reflected in Wikipedia efforts to increase knowledge equity. So our concentration is really honed in on policy development. How does a particular policy move from the stage of, let's say a draft or an essay and then move into something like a guideline or an official policy? And ideally we want to know what are the sort of skills that are required to move these works along this, along this path. Of course not all policies follows the path of draft to proposal to essay to guideline to policy. They go back and forth. Some of them jump from one stage to another. And we want to investigate how that happens. And so that we can understand the process better and then give better ideas about how we might perform policy. So the main corpus for research question one comes through looking at first we looked at five language additions Arabic, Dutch, English, French and Spanish. We looked at or assembled a corpus of all the major policies and guidelines for each of those additions using some of the lists available on each edition to navigate that. And then we wanted to make a purposeful homogenous sampling criteria for each of these for three additions, three policies per edition. We originally set out with 10, but that was that was too much. So we reduced it to three. And so we wanted it to be these policies to be representative of what we could expect if someone is wanting to know how to reform or produce a new new policy. So it should be the policies we looked at were ones that were created after 2005. Because that was when the process of making policies start to be formalized. We wanted to see examples where there was a policy that had been drafted beforehand. In case we were able to find that where it was sort of a full draft before, like in the first edit or first couple of edits. We wanted to be highly visited. So there's plenty of activity, highly wiki link so it's representative of sort of community consensus about its value, and that it also had development moments that we could analyze. So we came up with these three policies per edition, and we wanted to examine them through four different ways. The first one is just sort of a straightforward content analysis of the edit history, looking for templates and changes to the status of the policy. We ended up from all 15 as a total, we found 151 policy status changes. And we used 22 codes to identify what those changes are usually just using the actual templates that are used in wiki text as as the codes. Sometimes we had to change a few. The second pass is a qualitative content analysis of the edit history. So we went through the edits of each of these policies. 200, 2548 edits. In total, looking forward particular kinds of skills and users user roles. We did it again through the top page to look through for discussion, and we are currently working on the looking at the way that composition plays an important role of as a skill on Wikipedia policy development. The yellow there is where we're going to where we're currently working. Okay, so some preliminary results. We have, we noticed that most of the status changes happen in the first month of policies that some policies have complicated development histories like reliable sources has about 50 moments of change, which is compares to something like the French edition, which has very few changes in terms of status so that's an interesting thing to consider that we'll be considering and thinking about. So there's a number of different social roles that we have identified, like brainstormers deontic experts policy environment experts scope of the fires, etc. And in case these are preliminary results as we're still in the process of doing the work. We have a couple of steps left of this process of this research question before we move on to the second one. I think wraps up pretty much everything that I want to say about her topic. So thank you for your time, and I will gladly take any questions you have about the presentation during the q&a.


We're going to kick things off for the second half of the day with Thomas. He's going to tell us about installing OpenStack on Debian and give us a little demo of how to use it. Thanks for having me. It's a pleasure to be here. So I'm... Who am I? I'm 30 years old. I'm the founder of GPR Host, which does hosting around the world. We're French guy living in China. And I'm the founder of the OpenStack packaging group on Alioth. So I've been involved in packaging OpenStack since the cactus release. It means after it was one year old. And I'm currently the most, if not the only, active maintainer of OpenStack in Debian. I'm also the upstream of a few software. And I package other things in Debian like XCP, which is the only way to use Zen together with OpenStack. I used to do lots of PHP peer packages, but now we've got a much more active team. So GPR Host has many points of presence. That's the same slide I put every time. So here we go. OpenStack is, as you may have heard, is big. It's a lot of packages, both in terms of OpenStack itself, producing more than 100 binary packages. And it takes me a long time to deal with that. This is an LS of my working folder on my laptop. And I had to interact with all of the Debian packages that you see here, just to give you an overview. So it's not easy to package, to set up, because it has many moving parts. And for each component, you have to go through a procedure, which consists of registering the component to the authentication program, which is called Keystone, set up its database correctly, and then all this is both error-prone and it takes too much time. So when you set up an OpenStack cloud, your goal is to set up OpenStack Compute. But to have a successfully running OpenStack Compute system, you need to be able to give it some images. That's how Glens comes into play. So Glens, basically you upload images, download images, modify them, and then you can give them to Nova so that it can start virtual machines. And then you have Cinder. Cinder does the block storage. So if you need permanent storage, permanent partition, or boot from a hard drive, then you will do that through Cinder. Then there's Quentum that does the networking. Each customer or user of the cloud can build its own network, its own LAN, which is going to be private, and will not do like that with the clouds of the other user of the cloud. Meaning I can use 10.0.1 network, while somebody else does as well. And then you have supplementary packages like Heat, that does auto-scaling, and Cellometer, that does the metering. So you need to have all of these components set up. And on top of that, you use either the CLI or the Web Horizon interface. So Horizon is the OpenStack dashboard, and it's just another client. And there's another component called Keystone that does the authentication. So when you talk to any of the components here, you will do it through the Keystone authentication mechanism. Keystone is not only authentication, it's as well a catalog of services. So Nova, Glent, Cinder, Quentum, Heat, and Cellometer will all register their services with the IP address, port, URL. You have to tell Keystone where they are. And when that's done, for the storage, you can either use Cinder, which does block storage by using an LVM slices that it will push to ice-cozy. That's not what I use. I use CIF because I think it's better because it does the storage for everything in OpenStack, including object storage, image storage, and Cinder. So you plug CIF to Cinder, Glent, and Nova. Each of them has to be configured in a way so that it can access your CIF storage. If you've done that, then each component needs to be able to talk to each other through a message queue broker. So you have the choice between QPID or RabbitMQ, but mostly everybody uses RabbitMQ. So you set that up, and then in each and every component you say, here's my configuration, here's the IP of RabbitMQ, here's where it goes, and then after that, magically, all the components can talk to each other. And every of these components, Nova, Glent, Cinder, etc., they also need to store things in the database to keep the state of your cloud. So many wires, and for each of them, you have actions to do so that it's configured correctly. So how it goes with Nova, then you would create the SQL database, grant access rights to it, edit in the configuration file, the SQL connection directive, edit my IP, define the RabbitMQ IP login passwords, then configure it so that the Keystone old stocking goes to Keystone. This is exactly what I wrote on the schematic, that's what you have to do with Nova. Once everything is done, then you magically invoke Nova Manage and then DB Sync, and then it populates the database with tables and content. So once you've done that with Nova, you have to do the same for Celerometer, Cinder, Glent, Heat, Quantum, and for site packages like Keystone and Horizon, you have a minimum of setup to do as well. So as well the DB Sync, it was a bit of a mess, you have to do it differently for every packages. And at the end of the day, people who really deploy the cloud, they do PuppetScript, Chef, DevStack, or many ways to do it so that they don't do it by hand. So what I've tried to do on OpenStack is to make it easier for newcomers to use the packages using just DevConf. What the DevConf does is that it uses OpenStack PKG tools that I wrote so that it automates all this process of registering one component to another thing. So why I'm explaining all that is because even though you have the DevConf questions, you still need to understand which components will be plugged where, otherwise you won't understand what to answer. So let's see how it works for Nova for example. The first thing is using DB Config Common to configure Nova to access MySQL. If you're used to RunCube or PHP MyAdmin, then it's the same thing. So do you need to access the database, configure with DB Config Common, then which type of database, MySQL, the password. And then after that is done, then the post-int of Nova will do the DB sync for you so you don't have to think about it. Each component has to register to the Keystone catalog, so I did that as well as an automation. So you tell what's the IP of your Keystone server, what's the tenant name for, in Keystone you have the concept of an admin tenant which every package of OpenStack will use to get in touch with others, to get authentication tokens to talk to other components. So it asks for the admin and the username and the password for Keystone, and then it does the registration. So every API, so what we call an API program in OpenStack, would be the REST server with which you will interact to do things. So for example, there's Cinder API to create block devices, there's Quentum server to request new networks or subnets. So every of these API packages, they have this endpoint configuration thing inside DevConf. So register with the catalog, so by default it's no and if you install the package it will still be no, so that way you do it only once, even if you install the package. So what's the Keystone IP, what's the Keystone token, so the other token of Keystone is a special one that you use to set up, to bootstrap writes. So to do the Keystone thing and register the services, you just use the other token that you set up when you created, when you install Keystone itself. You answer with the region, so the region is that, it's like a bit of an availability thing, you can have, I don't know, LeCanc or Zurich, whatever. So this, I've tried to set up some sensible priorities so that you have less questions when it's in high priority. If you want to have all of them and make sure you do what you want, then you just set it to medium. I tried as well to pre-fill all the questions, whenever it was possible to detect things like the volume group in Cinder, then I did that. And at the end, there's a meta package thing so that you can install everything at once. So one of the very common ways to set up OpenStack would be that you install a controller that controls all of your clouds and then multiple compute nodes. So when you install OpenStack compute node, it will set up Nova compute running with KVM and OpenVswitch. So this will include as well quantum plugin OpenVswitch agent, which has to run on both the proxy node and the compute node. So it will set up all of that for you. You don't need to worry much about which package to install. So on the first slide, I showed you that there was many, many components, right? Cinder, Glance, API, registry, whatever. It goes in a bit in every direction. So that's why I created these meta packages, so that it makes it easier for you. You won't need to select them one by one. So the result as well is that if you see on the OpenStack documentation, on the official documentation, just for installing something as simple as Glance to upload and use images, they have like that because of documentation because they need to manually create the database, manually create the access rights, manually populate that. So under dbian, you just do apitget install Glance and then it does it. So the other thing which I like with using depthconf is that it gives you an interface to test things and it's proven, okay? Like Andreas Beckman sent some bugs on the BTS saying that my packages don't upgrade from one version to another and that includes as well, sorry, populating the database thing. And another thing is that you can always use the dbian front-end non-interactive mode. So if you don't like having questions asked to you, then you can still run in a non-interactive way. So when I do my tests, I just use preceding and then you just install the proxy node at once without asking me any questions. Here's an example, preceding, so I won't go a long time on it. I guess everybody here in this room knows how to do preceding. But the thing is that I maintain the preceded script on that repository so you won't need to rewrite it from scratch. There's still some work that needs to be done there but it's mostly working. So another difference I have with Ubuntu, let me check the time, yeah, is that our release cycles are very different. So Ubuntu follows the release cycles of OpenStack which is every six months. While in dbian, I have to take care of other aspects like the new queue, it takes a long time to get new packages. I do my work on top of Weezy, so in production, in advance, which pays me to do these dbian packages, they use Weezy and like I guess, mostly everyone who wants to run OpenStack in production, they don't want to run Cid or Jesse. So I maintain on a site repository Weezy backports, including all the dependencies like hundreds of packages. So you are free to use it. My hope is that I will have sooner space to store that within dbian. I hope that I will have access to PPA soon if it happens in dbian. Okay, so I had lots of requests and bug reports for non-respecting some rules which are stronger in dbian. So I hope that the packages we have in dbian are more dfsg-free compliant. Also in dbian, we have Heat, which does auto scaling, you won't find it in Ubuntu. There's FTP CloudFS and SFTP CloudFS which I also maintain. So if you want to contribute, I would very welcome you to do so because even if I'm full-time, I hardly find enough time to do all what is needed in one release cycle. So welcome on IRC. I can help if you are doing setups. I'd be happy to do so. So before we go to the QAA, I want to show you that I've set up a small OpenStack cloud instance in dbian, in DevConf. It's in the server room there. So there's two compute nodes on which there's four hard drives each. Two hard drives on each node have been used for SEF. So we have a redundancy for the storage. And currently I've set up only one compute node. And then you can try the... Okay, so let me show you a bit how it works. Can you see the screen? So the way it works is that you use that. So if you can't read or whatever, you can have a look at the video. So the username is DevConf13 with password supercode power. And you can use it to push images, install virtual machines and see how it works. So the way it works is that after you go to APT Get, install OpenStack clients, and then you'll be able to use it. And then you can do NovaList. It's a bit slow because the controller is on a virtual machine which doesn't have much resources. Quantum, Netlist, et cetera. So I can show you the web interface. I'll show you the admin one. It's more fun. So everything that you do in Horizon is compatible. It's done just like with the Python API. So everything you do in Horizon you can do on the shell on the command line with the OpenStack clients or you can use the Python modules because every client is both a Python module and a command line thing. So when you use the console, then it uses Spice. Okay, that's a demo effect. Okay, do you guys have any questions? Go ahead. There's like 10 minutes remaining and we want to try it out. How much hardware do I need to try? How many hardware is required to play with it? Okay, you can pretty much use OpenStack with a single computer. The only thing is that it's going to be hard for you to go from one to three and two doesn't really make sense because you won't have redundancy. But you can start with one or three and then more. Best would be start with three. That's what I did here. Okay. So here I have a virtual machine running on Zen. It could be whatever, just a computer running the API packages. So there are no APIs in the API, Glens API, whatever. And after you can just set up two compute nodes, for example. It works with one as well. And then Ceph, which does the storage. It's best to run with at least two, I guess, as well. Okay, thank you. So you would need two gigabytes for running all the API programs. And then if you want to have some workload on the compute nodes, obviously, what are you going to start from? Okay. Is there any other question? No question. So, thank you, Daniel. How do upgrades work? Can you upgrade one component at a time or do they have to go in lockstep? Yeah, upgrading is a big problem because every component is stuck with Keystone. So I guess you could upgrade Keystone first and then upgrade the other next. The big problem you have is, let's say, you have 10 compute nodes, okay? Then you upgrade one node. Then with my packages, it's going to upgrade the SQL automatically. And then the other nine remaining compute nodes will have the old code running with the new database. And that's a problem. So mostly you have to upgrade everything at the same time.  You can still have your running VMs and then upgrade all the cloud. It does work. The problem is that we scale when you have 1,000 nodes, then you have to upgrade 1,000 nodes at the same time. So it may be not really practical or you have a bit of downtime. Probably what you can do as well is use cells so that there's a concept of cells. Let's say you have a data center with three rooms. Then you can have a kind of tree and say I upgrade this cell first and then this cell and then this cell. That would work better, I guess. All right. Any other question? Hi. What is your plan for the stable relays of Debian? I mean, will you support OpenStack SX the whole life of Ruzi? I'm trying to do so to support OpenStack SX as much as I can within the stable relays. Though sometimes it's easy because patches are easy to backport. Sometimes it's hard. Currently I have a very difficult patch to backport to SX. If I get no help from anyone then probably I won't have time to do so. Me, as a Debian fan, I love to try to support stable as much as I can, though my customers and my company don't really need it, so it's a bit of a conflict. I say that because Ubuntu is OpenStack outside of... I believe Ubuntu, when they say they do security support for SX, they do it badly just as much as I do it badly for stable. They have no time and it's a different team and I saw many security problems that were not addressed in Ubuntu as well. So if you run an OpenStack cloud my advice would be to use the current release and the grade as it goes. So if it's a private cloud at the time you're not affected by the CVEs because most CVEs are on public infrastructures. It won't affect you if you're the only one having access to it. Though if you have a public cloud then you have to be current from the latest stable, that's my advice. So probably use my private repository for OpenStack on top of Weezy where I maintain currently Grizzly in Sunavana. So if you use a private cloud then stable is probably fine. I packaged Hadoop for Debian and I made the experience that all the people much rather used the Debian packages from the company Cloudera which had so many Hadoop contributors and nobody was interested in the Debian packages. So this demotivated me but of course, have you made similar experiences that people say we take upstream OpenStack in some form instead of Debian packages? There's no way you can use directly things from upstream with OpenStack if you have a large installation. I never heard anyone doing that. You have big companies like Rackspace that have their own deploying system. I know they, because they have so many nodes they can't even think about using an FTP so they deploy using BitTorrent. But I don't know how, do you know how do you deploy in HP? Can you reply to that? Hang on, microphone. The current public cloud is actually still running Diablo so we currently have a second data center which we try to be as close to upstream as possible. So the deployment guys internally they're putting a framework in place where they periodically pull from upstream and apply some HP specific patches on top of it and push it out. Alright, any other question? Because otherwise I have some, yeah, Thomas? So you already said that you're not using OpenStack for your company that would have interested me. What's then your motivation? No, no, no, no. I'm not using OpenStack stable in Weezy. I mean, I'm not using Debian stable with what OpenStack version is in. In Debian stable there is SX and then on the order there's Folsom and Grizzly. In Debian in OpenStack has a release name and I use Grizzly which is from last April. So you have an offer in your company based on OpenStack. So I maintain Grizzly currently in SID because I can't maintain it in stable as you know and then I use my own back port to Weezy with Grizzly. Does it make sense? Yes, but I looked at GPL host homepage and I couldn't figure out what product is using OpenStack what are you using OpenStack for? Currently I use it only for private cloud because I have no billing software to play with. So I can't do the billing. There's metering with salometer but metering only tells you how much resources the customer have been using and then you have to kind of doing billing manually, right? Or use something like J-billing or these kind of fancy applications where you can plug things. But yeah, for private cloud it works great. Any other questions? Okay, so I will use the remaining two minutes to tell you that I also maintain... You've got about 15. What? You've got 15, don't you? It's 45 minutes, right? I've got 15 minutes remaining. So I went faster than you. Okay, it doesn't matter. So I can show more about it. So... Is it installed? No, it's not installed. So I maintain as well a script to build OpenStack images which... So it uses the bootstrap to get it into a CH route and then after it produces a simple image that you can use in Glens. So that's the final result. The image list. It's a very simple script that does that. Who uses Parted to create the partition table, do the format, create the... Okay, so basically you just do like that with URL, ftp.ch.dbn.org.dbn-s. So you will be what you use for bootstrapping and then what goes in your source list. And minus R and release. So I'm going to... So because you had the demo with non-free services this morning, then I may explain to you how to use the free software services we have at DeadConf to create an image and then start to use it with OpenStack. So at least if you don't set up OpenStack in your enterprise or whom, then at least you can try it. I heard that HP can provide some free accounts as well. Maybe you can talk about it? I don't know. I'm sorry. It's the second time I do that to you. Well, that's my plan, but the higher upstone necessarily agree with me yet. So yes, the plan is to provide some limited free account to the different communities, Debian, as well. But we still... I mean, our buildings or our sign-up system requires credit cards. I mean, you guys usually don't like to put in your personal credit card. So I'm working with product management to get that resolved. So my advice if you need to use the cloud is to use something that is interoperable. So like either HP Cloud or Rackspace Cloud. And then after, if you want to... let's say it becomes large and then it would be... it can become relevant for your company to set up your own private cloud on top of OpenStack. So in that case, it's easy to migrate from a private provider to your own provider. I'm sorry, it's kind of a very, very slow network because bootstrapping is not doing anything. Sorry? Ah, really? So it doesn't matter. Let's say it's finished. Okay. So I'm going to SSH again to the same machine. So it's going to produce this, okay, and then you do Glens Image Create, or Image, the file, which is the Qco2 format. And then once you did Image Create like that, then it appears here, Glens Image List. So once you have the ID here, okay, maybe I should first show, explain that. So you have the concept of network, virtual networks in OpenStack. So what you see here is a graph that is maintained by Horizon dynamically depending on what you've created. So the network here in green is the real network that we've been using in DevConf. You may recognize the IPs. So when you create a new user, you either create that new external network to map the real IPs, or you do it once, and you say that that network is publicly shared. And once you've done that, then you add another LAN like in here on the IPs that you want. So because I'm admin, I can see both, okay, that's my own network as an admin, okay, and that one is the one I've set up for the DevConf 13 account. So I can see both. And both will have a different router. So every time you have a new user, it will set up a new router, a new virtual router, and then connect to it. So your virtual machines won't have an IP address directly. They will have only IPs on the LAN given by the DHCP. So what you would do is ask for that one of the IPs on the external network is forwarded through NAT to one of your virtual machines. And then from there, on one virtual machine, you can set up HAProxy, for example, to reach your other virtual machines. So on the command line, it goes like this. So quantum. So you see, I have my tree networks. And if I do quantum subnet list, then it shows me the IP addresses of these, okay? So here you can see my external network and the two LANs that I've created. Nova boot. And after with a simple script like this one, then you can create, okay, I list the images, I list the nets. And after, I create it with Nova boot, flavor, image, and the idea of the image with one nick. So if I don't put minus, minus, nick, net ID equal, then by default, it will attach the virtual machine on the external network and on the LAN at the same time. So it will have two other net ports. And that's the basics for how to use OpenStack with the clients. So I give you the credentials again if you want to try. Any questions? Got like 13 minutes to go. I think we had many questions already. But then that's it then. Thank you.


Hello everybody, Andrea Maeski here with Dental Tutoring. So I have been a tutor since 2005 all online and I helped dental hygiene students and dental assisting students pass the board exam. And what I'm super excited about is this month I am now offering my very own app. So it is a full board exam review app. So it is so nice, I will be showing you guys that in a little bit, but it's excellent. So pretty much you can study on the go. So if you're on the bus, if you're waiting for a clinic to start, if you're waiting for a class to start, if you're waiting for work, just on the couch watching TV, you want to do a couple questions. This is what the app is all about and I love it because it's not just exam questions and then you'll get the answers afterwards. It is so much more than that, where I will actually be doing a video like this going through the mock exam questions with you. So I go through the questions, I go through the answers. There's a lot of questions, so obviously it does take time, but I'm separating them into topics so I can upload a video at a time. So I don't overwhelm all of you guys either, but the best thing to do is to do the mock exam questions first and then if you're really stuck on a certain answer thinking why is the answer like that, then watch the video having me actually stop and explain everything to you. But I take it even a step further than that, where I will go through all of the different answers and say why that's not the right answer. Because as we all know, there are always two right answers, but you need to pick the best one. So I will be going through all of them. If you're inside my board exam prep academy course, we do this at every single tutoring session. It is a full hour of mock exam questions, answers, and I go through all of them and teach you guys how to take the exam. Because on the board exam, they don't have simple questions, they have hard ones and it can get very confusing. So this app is the first step to making sure that you know everything. So even if you have a month left to take the exam, if you have six months left, this app is perfect for you and it's not expensive. I sell mock exam packages for $35 each and they're typically 60 to a hundred questions. The ones that are 200 questions are maybe $45 each, but this app is less than $30 and you get thousands of questions. So how could you not get it? And you have full access forever, so why not, right? So let me just show you guys what it looks like. I'm just uploading it right now. So when you install the app, it will look like this on your home screen or just hope you guys can see that. It's kind of hard for me to show you guys, but hope you guys can see that. It's kind of blurry, I know, but this is what the icon looks like because I did get some students email me saying, where's the app? I can't find it. So depending on the type of phone you use, you might have to do a search for it if it doesn't automatically add new uploads onto your home screen. So I don't know much about that, but if you can't find it, let me know. So this is what it looks like and I'm just going to enter the app right now. And this is what it looks like inside the app right here. Pretty cool, right? I know it's kind of blurry because the webcam's trying to focus on me and focus on the app at the same time. Oh, there we go. That helps.  So this is not even the first part of it because it is constantly being updated. The full launch is February 25th, so the end of the month. So yes, the app is all set now, but more questions are being uploaded every single day. I wanted to wait until launch to show everybody, but I was getting so many emails of people saying, I take the board exam next month. Can I see the app now because I want to get started with the setting now and not later? So that's why I did sort of allow you all to pre-order it now. So if you do pre-order it now, I will leave the link for you guys on the bottom. You will get first access right now. All of the questions are not there though. There's about 500 questions so far, which is still a lot, but there will be thousands by the end of the month. And the nice thing too that I forgot to mention, so this is what it looks like again. If you click on chat up here, you can chat to me. So if you guys have any questions, if you're not sure about a certain question, if you just would like to say hi, it will tell you to install your own account for WeChat. So sorry, I guess I should have shown you guys that first. So if you, oh sorry here, let me go in the app again. This is hard to kind of show on the screen. So if you click, okay guys, chat. It wants you to upload this one. So I did install it already and then it's WeChat. Sorry, this isn't really the best, is it? But you get the idea. So you can chat to me ASAP. And let me show you guys inside. Like I love this app. I wish we had this when I was a student, but I'm the one who obviously designed it. So that's why we had it, right? But I wish I had something like this. Also, if you want easy access to my YouTube videos, you just have to click on video in the corner and it will upload all of my YouTube ones right there, including the ones that are like the newest ones, I guess is what I'm trying to say. So sorry again if that's kind of blurry, guys, but you get the idea. And let's say you want to study special needs. You just click special. Oh, I think I clicked oral pathology, but that's okay. Oh, it's a little bit slow right now, isn't it? I think because I didn't really click it properly. Sorry, guys. But you get the idea, right? This app is amazing. It's less than $30. I buy shirts that are more than $30. So you know what? It is a great investment. You want this app, okay? I just wanted to show you guys some of the questions, but it's kind of being silly. I'm going to restart it and you know what? It's probably because we are doing the updates today. So there's somebody in there updating the app now. So that's probably why I'm having trouble uploading it. But have a look at it, you guys. It's amazing. You have nothing to lose. You have so much to gain, so much to learn. And if you have any questions about the app, please let me know. And I look forward to seeing all of you guys. And if you have any video ideas, let me know. I do typically do videos about two weeks in advance. So if you do have an idea, I did make a note of that and you will see it soon, okay? Thank you guys for watching. Have a good, I guess, morning. I will talk to you guys very, very soon.