My name is Noah Reyes, I'm a designer here at Adafruit and join me every week as my brother Pedro. Good morning everybody, I'm Pedro, creative tech here at Adafruit. And every week we're here to share a 3D printed projects feature electronics from Adafruit. That's right. This is where we combine 3D printing and deal with electronics to make inspirational projects. Hello everybody hanging out in the Discord chat room. If you'd like to join us throughout the show with any GIFs, GIFs, memes, all that is welcome. You can hit us up on the live broadcast chat room in Discord server. The invite URL for that is discord.gg slash Adafruit. Is that good? Hanging out with everybody in all of the chat rooms you are in. The YouTubes and the Facebook, Periscope, Twitch and of course Discord. Giving shout outs to everybody hanging out. Good morning, Mr. Certainly, Vince, Yanni, to Wester, Mr. Certainly, I think I already said. Good morning, Liz, hello. Seeker. And everybody else. Switching to the other chat rooms. Good morning everybody. Good morning, good evening, good afternoon to everybody hanging out all over the world. Yeah, we have a fun show today, lots of interesting demos and prototyping stuff. So we'll get through the housekeeping in the beginning of the show. And then we'll jump into this week's product that we're taking a look at. We have lots of LEDs, thousands of LEDs for this thing. Yours literally has a thousand, mine has like several thousand. Lots of LEDs. There's so many, they're like dust. It's just everywhere. Literally. I thought that was dust, that was cleaning up. Let's go ahead and jump into the show. Starting off with the housekeeping. Okay, here we go. If you head over to the Adafruit slash free, you can find all the different tiers this week. We have pretty similar from last week. Let me run through those real quick, make it bigger. For orders, if you spend $99 or more with Adafruit, you're going to get a free half size Promo Proto. If you spend $149 or more, you get the half size Promo Proto plus a randomly selected Stem-A-Q-T breakout board. If you have an account with Adafruit, we'll make sure you don't get the same one twice. And for orders that are $200 more, you get that Stem-A-Q-T breakout, the half size Promo Proto, and free shipping for ground continental US only. So check out Adafruit.com slash free for all the dates. Help is wanted. Go to jobs.adafruit.com for when you see all the listings that are available. If you're a maker in the market for a maker gig in this gig economy, check it out at jobs.adafruit.com. This week, the latest posting I'm seeing here is a PS4 to PS5 custom controller mod. And this was posted by Happy Cat Productions. It's a freelance gig. So check that one out. And that was published earlier in this month. Lots of other excellent ones as well. Check those out if you are in the market for a new gig.  That's jobs.adafruit.com. Okay, this is a fun one. We're inside this little computer. Shout out to the new newsletter. This is a once a week newsletter. It's a great way to get all of the latest products that are added in the Adafruit shop in your inbox. So that's really cool. How's my audio? Is it okay? It looks low. I gotta say it looks low. You're good? Okay, it just looks low on my end, huh? It's like, look how low it is. It's normally this much? Why is it so low? I don't know. Do I need to speak louder? Last week's live stream was quite an endeavor setting it up. Anyway, this is what it sound like. Let's go to the next. Adafruit Daily. If you want daily content from Adafruit, go to AdafruitDaily.com. And you can subscribe to all the different categories of goodness such as 3D printing, Python on microcontrollers, maker business, biohacking, and more. So check that out. AdafruitDaily.com. Make sure you won't, we won't spam you, we promise. And shout out to all the 9,000 folks who have subscribed to the Python on microcontroller newsletter. If you have a Python related project, you can get it featured on the newsletter. Just email cpnews at Adafruit.com. Shout out to Paul Cutler for hosting the Circuit Python Show podcast. It's a great opportunity to hear awesome people that are working on Circuit Python or working with Circuit Python. You can check it out in all of the podcast services just by searching for Circuit Python Show. So a huge shout out to Paul Cutler for doing that one. And I think that is what we got, right? Here's the team. I don't know why I clicked on that button, but it's great. We're hanging out. Sorry, I'm trying to... Okay. No, wrong one. Hello, everybody. We got some gunk droids by Yanni. Thank you, Yanni, for sharing that. All right, let's go ahead and jump into this work to this week's pretty awesome updated product. You heard the audio, right? We're good. Okay. Why is it so... Look how small it is there. It's going to drive me nuts.  There we go. That's scary because now I don't know if we have any audio. I'm listening. Okay. I appreciate you listening. Can you folks hear that? We're good, right? Okay. All right. Well, this week we're taking a look at the new ESP32 V2. I almost said the wrong way, but I caught myself. There's so many different variations of it. This one is a really good one for running MicroPython. Oh, sure. My favorite thing is honestly Whippersnapper. Whippersnapper is Adafruit's easiest way to get IoT projects going. So this is the new ESP32 V2 and some of the additions is it's got the Pico Mini 2, which is this little guy has a Wi-Fi and Bluetooth connectivity. It's a small package. There's a lot of room here for the mounting hole. So I have it mounted to our little 3D-printed Lego Stemic mount. It supports Lego studs. So you can make a fun, quick project with just kind of moving these around, sticking them around. So I have a Stemic QT sensor here. This is the ATH-20 temperature humidity sensor. And what's great about it is you can just plug and play different Stemic sensors now. The version one of this ESP32 HAZA board did not have a Stemic communicator. So this time around, with the smaller package, it now has all that room for awesome things like more RAM, your Stemic QT, and even a little NeoPixel and an extra button here. This is a software button that you can play with. But yeah, you get all of the pinouts here. I'm going to take this off. Mounting holes is awesome because you didn't have them sort of on V1. You know it's V2 because it says V2 in the background. Lovely silk screen, either by Lamar and or Phil B. And yeah, it's a great little piece of kit. It's really nice feather that does Wi-Fi and Bluetooth. So we will take a look at setting it up on Whippersnapper. Whippersnapper is free. It's in beta right now, but it's definitely usable. So check it out at io.edifruit.com. Here I have our ESP32 V2 dashboard and Whippersnapper. I have set it up and in your Whippersnapper dashboard, you get a glance at all of the hardware that you have kind of played around with. And what I want to note here is that each board, you can see exactly what beta number it's on, which is super cool. You can see they're all offline because they're normally battery powered or plugged into the wall, so I don't have them online. But you can see here the 32 is online. That's awesome. And you can see it's at a date. So I'm going to go ahead and click on it and update it.  It seems like we got betas like every week maybe. So to update it, we're going to go to device settings. And here you can change the name of it. You get an idea of what it looks like. I'm just going to click update. And we're going to update it live. Hopefully it works. If not, we will report the bug. Yeah, maybe I should have tried this before. I think it's updating. I don't have a clue as to what it's doing if it's doing it or not. Anything? Maybe it's a Safari thing. That's what I was going to say. Yeah, so it is in beta. But what's cool is that right away, you can start playing around with some of the things. It's got a built-in LED. And you can add all of these components to it if you want to start playing around with different sensors and components. Right now we have a handful of StemAQT breakouts. Here you can see the AHT, a BME 280, and a couple other ones. And we also have a learn guide on adding your own. So if you want to add your own, you can follow through Brent's learn guide and create your own component if you want. I'd really like to get the battery monitor on here so that I can find out exactly what my battery level is. Because I'm always afraid that the battery's going to die. So it'd be cool to have this hooked up to the battery gauge, the battery monitor, StemAQT, and then have a sensor tied to that so you can kind of monitor the thing. I haven't walked through it, but it's definitely able to do so over here in the I2C component page. It walks you through installing or setting up your own component in Whippersnapper. There's also a dedicated Whippersnapper guide that you can follow along with if you want to see what's supported and stuff. But yeah, that's a quick look at the stuff. I have a dashboard as well that I've created. This just gives you a visual indicator of like plotting the humidity and temperature in a little pipe graph thing. Not a pipe graph, but a line graph you can see here over time. It's tracking it every minute or so, every five minutes, I think. Update if you want to pull it every 10 minutes or whatever, you can change that here a couple hours or so. Yeah, I really like the I2C temperature sensor it seems to work with just about all of the boards. So that's a quick look at the ESP32B2. If you got yourself one, definitely check out Whippersnapper. I recommend trying it out. It's really fun and easy to kind of start plotting data in like a few minutes. A quick question from Vince, asking how stable are these Wi-Fi boards over a long period of time? It's been used in the ATC Wink 1500. I would love to try something more affordable. Yeah, sure. They're pretty robust. I have here an air quality sensor that's been on for, I don't know, a couple of years now. Since we released the project. Yeah, it's outside in the front of our house and it's just been on for, I don't know how long. At least two years or more. Yeah, I need to take a look at it though, because it's just sitting out there, but I think this is the latest data. A while, depending on your Wi-Fi router and stuff, our Ryder goes down up and down, so it might be offline right now. Yeah, this is kind of a testament to like, yeah, it's pretty robust. This is actually the ESP32 V1, I believe. Let me do a quick look and learn guides and see what that was. Do you remember the name of that? Air Quality Sensor. There it is. Air Quality Sensor, 3D printed enclosure. What's the... Oh, it's the... Okay, so we used an M4 and the ESP32 Wi-Fi Co-Processor, so that's like an add-on if you want to add on. It's not the same chip, it is the ESP32, but it's not the Pico module like it is here, so I don't think this one does Bluetooth. But yeah, this is another option. If you already have a microcontroller, like the M4, the M0, this is a good way to kind of get that. Just kind of add on Wi-Fi. You can see this module's bigger here. It's the W Room 32. And speaking of the Pico module... It's running pretty good this whole time. Yeah, we have it running with the BME280 or 680 and the Air Quality Breakout, the PMSA03i. It's a nice air quality sensor. Anyway, what's up? Is that good? Yeah, we're going to take a look at the Pico module, the 3D models for it. Yeah, so as a part of the new board, we tend to make a 3D model of the PCB itself. So here it is. Here's the learn guide for the ESP32 V2 Feather, all the lovely documentation that you have grown to a custom to. Under the downloads, you can see the schematic and a screenshot of the PCB and EGLE. And really, what you can do here is find out exactly what the data sheet is for any given module. In this instance, it's the Pico Mini 02. So I was able to pull this up, and here's two different flavors of it. So I know it's this module, the ESP Pico Mini 02. So what I recommend, if you were making a 3D model for your component, for your board, definitely check out Digikey. Digikey, I searched for the ESP32 Pico Mini 02, and here it is. There is no photo for it, but there is a data sheet, it's a PDF, you can check that out. But my favorite thing about Digikey, you scroll down here, under Documents and Media, 90% of the time your components have a link to a CAD model. So here is a link to a step file, it's a 3D model format, from SNAP EDA.  So if you wanted to spin up a new board and you didn't have the footprint, and you didn't want to draw it for three hours, you can just download it from SNAP EDA. So I have an account, it's free to do so, and then they have these models here. You can kind of revolve around it just to get an idea, like yeah, that's the right package, that is definitely the right one. All the footprints are there. So I download it as a step model, and I'm going to start modeling it. You can grab the EGLE CAD file, that's linked here. So under the Downloads page, under Files, you can see here there is a PCB file on GitHub. So I will download this, open it in EGLE, and use the Fusion 360 Convert thing. It just kind of spits it out, so the 3D model, and then I can map all the components. Yeah, and I will be using the component from SNAP EDA. So let's just look at what I'm going to do today. Yeah. But the mounting holes for the feather are pretty standard, and it just worked out of the box with this one. Prior to this one, I think I had a feather RP2040 in here, and it has kind of the same mounting holes. So that's another awesome thing about feather ecosystem. If you already have a 3D printed thing, or a project that has mounting holes for the feather, your ESP32V2 will just fit. How about that? Yeah, and I can be confident to disconnect this, because it's battery-powered here. So there you go. Cool. So sign up to get notified when these are back in stock. We've had a short stock of them, but we're working on getting more. And this is kind of expressive, shout-out to expressive. They're kind of the only chip you can get right now. They're expressive in the RP2040s. It should be coming back soon, so make sure to sign up on the product page. Put the link to that. It's a PID 5400. There you go. And I think that's it for this week's cool look at new product. Yay. Hope you all like it. Pretty cool. All right, let's go ahead and jump to this week's prototyping. This week we have an update to that little connection machine we've been working on with Phil B. This is one of those iconic giant computers when they were like mainframe back in the, what, 82s when it came out? Made popular on lots of films. One of them being Jurassic Park. It's featured in the back. And here is Lamar and Phil. The animal was there too when they checked out the museum of, what is it, the MoMA? Yeah, the MoMA Museum of New York. Yeah, you can see how big it is there. Lamar for scale. And you can see that the LED matrices on the back are displaying like system load. And beyond that, Phil B is going to add some cool audio visualizers and some of the animations that we're seeing in the Jurassic Park clips.  Bigger one since it's so big. Since it's so big. It fits right in the palm of your hand. This is of course fully 3D printed. It's in three parts.  It is being powered by a Raspberry Pi. A little bit overpowered, but Phil B is going to work on a, one that'll work on a microcontroller if all you're going to do is display the matrices. You can see on the inside here where the Pi is mounted and how all of the cables are all connected and running on a couple of headers down there. Nice and removable. Little back panels here with ample amount of ventilation since a lot of the, like the detail here, these cool little triangular vents were supposed to like bring in the air and then like push it out through the top. So we've got all these vents all over the place and then even on the bottom here to make sure that your Pi is nice and cool. You also have a bunch of mounting options on the inside so you can add an additional fan. And where am I? Right there. So we can add brackets to add the fan and like sort of do some circulation inside there. Of course the front here you can see how we're using the black LED acrylic to have that nice diffusion effect on the matrices. So we're using the Charlie Plex matrices or is it a loose one? They're 9x17, 16, something like that. So you have the LEDs and then the driver backpack on the back there.  Give you that nice little diffuse look and what else can I say about this this really nice Octoprint case is what I'm going to use this as and the microphone that Philby's going to use is just a little USB one that plugs into the back so you can do the audio visualization. Yeah. Yeah, so there's going to be a couple of different demos. Right now I think this is showing the activity of the Pi. Is that right? I think it's like fake activity but he's going to actually get some system load info in there. That's cool. All right. Yeah, so all of these are days to change together with I squared C. Yeah. So just zero clock and zero data, two data lines, voltage and ground. They plug into what? Just the headers on the Pi? Yeah. Just plug into the headers and then you're doing some addressing for each matrices on the back here. We'll show it in more detail next or actually yeah, next week. The way that they're soldered to show which address each of the matrices. Yeah, that's what's great about I squared C. You can assign different address buses and then have just eight of them all and then you have the octo over here. So you have eight of these matrices all going together. That's over a thousand RGB or just regular LEDs. These are just regular LEDs. You can choose the colors and whatnot. You can't change the colors because the LED is the color. They are not NeoPixel. Yeah, not NeoPixel. I will pull up the product page for the Charlie Plexus. I think we do have a couple of those in stock if you want to start building this guy. Yeah, you can see the red ones are in stock. You do need the thing in the backpack to drive it because it's just a board for just having the LEDs. There's no actual circuitry on it other than the traces for the LEDs. But you need to power this. You need to drive this with something and the driver is over here, this guy. 16 by 9, yeah, PWM. The other D-matrix driver using the ISFL. IS31, FL3731. Love that one. But yeah, you can do all sorts of fun things. And we have used this backpack before. If you remember a couple of years ago, we came up with this... Oh, a incredibly cute little pet. Yeah, so making many retro computers is a thing. We love doing it. This is our first one, I don't know, five years ago. Let's say a little 3D printed thing, just one of these backpacks. I think it's a feather and fake keys. A 2D printed thing that's already, like the sticker's already peeling. It's a great little project. Awesome Arduino code from Phil B. Oh, look how you put on there. It's running the Feather M0. Right, so it's actually running an older, yeah, the Melsan D50. Little guys. I can't focus. But anyway, it's using very similar, instead of red, it's green. It can do game of life and some text and other things. We've got a nice Adafruit GFX library runs with it for Arduino. And we also have a Cirque Python driver as well. But this is all done in Arduino, because we didn't really have Cirque Python back in the day. Mouthing about the exact same thing with the little numbers. Oh, really? With the standoffs on the back there, because you can't really get the screws in there once you attach the backpacks. So everything is fully removable, completely modular. So if you wanted to swap these out for different matrix C color, you could do that. Or if you just want to do away with it, have the case be something completely else. Yeah, plenty of room for a ton. My favorite Pi case so far. It's such a cool Pi case. Definitely going to keep this around. If not a Noctoprint case, at least with the... When he moves this over to Cirque Python on one of the feathers, or a Pico. Definitely have this as a nice little display, like our cool little LED matrices in the background there. Yeah, so this is the website from MoMA.org. This installation is called Thinking Machines. This is the CM2, right? This is the model. They had a CM1, 2, 3, and I think all the way up to 5. Yeah, the 1 and 2 were similar. I think it's just like specifications and process or something. I thought this was actually a real thing. This is actually a replica I did not know. Where does it say that? Oh. Where does it say replica? There's a link in Slack. Did you see that in random? No. I can pull it out real quick. Just bear with me, folks, please. Is that being shown? Yeah, here it is. Blinken Labs is the company that worked on making it, making the replication. Replicolites for the CM2. And they have a picture here of an Arduino. These look like bear LEDs. And they maybe wrote some software to do that. I don't know heat stuff. Is that a teensy? I don't know. I thought that was a real thing. I did, too. So check out this video as well. Maybe I'll put a link to it. Yeah, let me just link to this whole page and folks can get an insight. Next time in New York, I definitely want to see this if it's still around. That'd be great. But this is a great interview with one of the consultants, Gordon Bruce, who worked on the project. Yeah, and they have some fun interviews. Nice little discussion on the design process that I have. What was it? The belt? The waist belt or something? I don't remember. But I added all that detail in there since Philby did have that in the base camp. All the detail that needed to be in there. So that was a nice little challenge. I figured out how to get everything to go. Used some support materials, but it turned out phenomenal. Really happy with the quality of the printing out on this. It's going to open base camp and start poking around it. We could do that next week. Just in case that next week we don't do the show or something. Let's see. Alman Chattery on Facebook is asking which this are we talking about? You can get all the parts. This is a sneak peek of the audio visualizer code that Philby is working on here. And he posted a really cool demo on Twitter as well. So here in Jurassic Park the first one, you can see where it was it's basically in every kind of hacker scene. Honestly, I don't remember. As a kid watching this, I don't remember seeing those in the background because I don't remember them being next to the screens. It was always in the background. I like the way that every other two rows are moving in opposite directions. Did you film this with your phone? If you're watching on your laptop on HBO Max it was great re-watching it too. And knowing what to look for it's in that scene. It's such a visual thing getting all this nice bokeh in the background of the shot. It's really cool. That'll be next week's super cool little pie case. Super cool little pie case the little connection machine CM, connection machine. CM1 slash CO2. That's what we're preparing. I think you have something too? Yeah, I do have something too. Cool. So we have cubes this time around. Lots of cubes. I've been working on a a 3D RGB matrix cube. This is it. We're going to have two versions of it. There's a bigger pitch for these 64x64 RGB matrices inside here. It's kind of hard to show everything right now. Raspberry Pi is in there and a matrix is in there. These are six RGB matrices panels. What we came up with is a system of lining up all of these frames so all of these frames will be attached to each of the RGB matrices. They get mounted with these corner mounting holes and each side has these letter tabs and the idea is that you link up, you just match up the letters and with these magnets and alternating tabs they just kind of snap into each other. So it took us a minute to figure this out because we only want this cube to be assembled one way because in the code mapping all the orientations is quite difficult. So this is one version of it. The second version is the RGB matrix that's just bigger. It's a 2.5mm pitch. This one is the 2mm pitch. So what I'm going to do now is plug it in. The way we have everything powered is through a 5V 3A 10,000 mA LiPo battery. It's huge. It does 3 amps. The Pi 4 needs 3 amps so if you're going to try this in the other battery make sure it can do 3 amps. So the RGB matrix bonnet has to be powered separately but this battery is beef enough to power as you can see I have two USB ports one for the Pi. It's going into the USB C port and this USB port here is going into the 2.1mm barrel jack on the bonnet. We have kind of shortened out these power cables and are using these screw block terminals to share all the power and bus but this all needs to be daisy changed correctly. I went ahead and snapped it down. I'm going to run the globe demo so I'm going to SSH into the Pi and launch the demo in just a moment here let me do that again ok so I'm going to CD into the thing and then run it and here we are. So this is a great demo from Phil B Phil B is doing all the code and he needed to come up with a way to test the orientation of all the panels and make sure that everything is mapped properly so this is an animated globe it's spanning across 6 of these different panels I think we need to go to the yeah sure there you go so there it is it's about 133mm big and it's kind of heavy it's very heavy it's drawing a lot of power and a lot of current that's why we needed a beefy battery that can do 3 amps because the Pi 4 is power hungry it gets hot as well it's getting warm so we might put a heat sink in there I've only run it for about 30 minutes so we'll see what's the total time but it's cool that when you want to take it apart you can just take off this bit here and shut it down but yeah it's cool to see the map kind of animate across 3 of these panels so imagine if we had a texture map of a human head it'd be really creepy so yeah let me run another demo just because it can with a life demo yeah so this is the Conway's Game of Life it's got a couple of different colors and the real impressive thing is that the cells are spanning across well sometimes it's hard to I don't know why they all kind of disappeared and like stopped working demos yeah I think I killed it let me run it again that's one way to look at it but you can see how the cells are going across the panels there and really the last demo is to show sand the sand demo, pixel dust showing there's an accelerometer in there as well I forgot to mention but that's really just for the sand demo we've done sand demos before with the RGD Matrix season and the Mar has always wanted a cube boys, a cube difficult mainly on the assembly front I'm going to stick with the globe, it's just the best demo for it and Artica, where is he? Artica let's spin around question from Mr. Cernan Bruce is asking did you look at the snap action 5 wire block connectors on the shop PID 874 so I need more than I need more than what is that 5 that only gives me 4 we needed the power the rail we have is in the shop, do you want to pull it up? I think just call it power rail this one was recommended by Phil B it's a nice chunky one power bus yeah these guys these are great, they're super chunky they hold a lot of current and they have just the right amount of pins, 7 of them for me to do it so that's how I'm doing it it comes with screws and all that it has mounting tabs but as you saw inside the cube there really isn't a spot to mount it so it's kind of reloading in there but this is the power bus I use this is real cheap, it's like $2 oh wow they're great for these thick wires each panel comes with a power cable and an IDE data cable the power cables are kind of chunky, right? they're literally like this thick hey look there's a cube from a few decades ago that's a great one too yeah so any other questions? the chunk is important yeah and it looks beautiful yeah the bigger one is you want to hold this up while I hold this one up? the difference is I haven't held that one, how much heavier is that? well there's nothing in it yet, it's already heavier but yeah this is the 2.5mm pitch so you can see it's not that much bigger but yeah it has the same kind of principle but it's a little bit different these have curb cut frames they're at a 45 degree angle which allows the assembly to be much easier much easier you can see inside there we have a 3 printed bracket for our Raspberry Pi same thing with magnets the accelerometer goes in the middle here so you can see these 4 standoffs and there's just magnets there there you go and then these corner brackets here are all secured with screws because you have these really nice heat inserts embedded inside the frame the curb cut frame for the smaller like I said we had to recreate the frame so that was vastly more difficult than this version I think though the smaller the panel the more expensive it is so it's one of these very costly fills that kind of just shows that you can do it but that's I think 2 weeks out, 3 weeks out nice little flex video very cool yeah so that's what we're projecting it's nice and warm now get the whole world in your hands I'll be gentle a little bit Yanni says it looks like Lego and to Wester so the world or so the earth is flat flat but in 3 dimensions Cuboid hey that's a cool demo that Yanni posted the sweet wow check out discord at discord.gg slash Adafruit to check out all these sweet memes I had this as a Minecraft block which looks really cool I also played around with the portal cube 3D Tetris yes but remember the accelerometer so it would be cool to do some sort of accelerometer funness and then there's this funny guy saying that yeah it's great for the manufacturers to realize these are likely to be used by people wanting to make cubes and angle the frames and make it easier yeah it's a little bit tricky to get these overseas with everything going on but yeah Lamar managed to snag a couple yeah they were like on the boat stuck on the boat ah Andy Callaway coming in with the important questions where's the 3D party parrot yes that's that's a great idea alright so that's what's being prototyped yeah it's a big prototype segment this time around sweet alright we're ready to jump into let's go ahead and check out this week's community makes this week is an awesome I like the design of this sweet little wearable it is a dragon hairpin it's so cool this was supposed to be released during Halloween but not enough there were too many Halloween projects so got pushed back so as we're seeing here I did have to do some chopping up of the model mostly just slicing it in half so it doesn't fall over and getting all those nice little details in the horn same thing with the sword just chopped it in half so I wouldn't have to print it straight up could do a little work with like welding and then like sanding it all down if you want to get rid of that very visible jointing line there but for the most part it looks really good it looks like how smooth it is and yeah it's a really cool dragon hairpin to go along with your cosplay so it's be like a skull for the dragon and again I did chop it up right here just so it would print vertically and have some nice smooth details here on the horns and here's the sword goes right into the eye here to hold up your hair and this is just chopped right in the middle down the center here so it just prints flat so I don't have to print this one vertically because of the T right here although I guess I could have chopped off the handle and printed it upwards to get that nice detail with a little crystal pommel but for the most part oh yeah prints super well really happy with the way the quality of this came out always an excellent technique to take a model split it somewhere where it makes sense and avoid some support material gives you a flat surface to do to the bed as you can see in the time lapse it did fail and I did try printing it upwards like cutting off a little beak here I'm bringing it up but even with the z-hop it kept hitting when it gets down to the top I mean this is a pretty complex complex up here as you start getting up to the horn so a nice little way to have a larger surface area on the bed with this instead of having this little tiny area down here this is by Angry Ant Eater on Thingiverse so Angry Ant Eater thingiverse closer to that up so if you want to mix from a skull hairpin yeah I think we've posted this one before on the blog or did a video of it but I think that is Angry I thought it was Antler Ant Eater bubble very cool and the original model is like this you can see split that in the middle what you use to split it Prusa, Slicer and do that in Curie huh not the way this slices it almost looks like a good cut there very cool alright well shout out to Angry Antler Angry Ant Eater for posting this up as a free download yes I do not believe this is TSA approved even with this soft I think you might be able to cut with the edges here oh you brought that too you might have to leave behind the sword and then Rawls is asking the amps that the cube is using I think you said 3 yeah the battery is a 5 volt 3 amps it's a nice battery you can get it on Amazon just search for 5 volt 3 amps 10,000 milliamp there's only one that I found there's probably more but yeah all of the batteries in the shop will not work because they do not go up to 3 amps they only stop at 2 amps yep we tested I did not work I risked burning out my pie which is a very bad thing to do right now so hang on to those pies or have a backup SD card ready to go when your pie is short when you've shorted the power thankfully I didn't short the power alright I think that's it for this week's community mix no mix this week yeah we don't have any mix this week so that's great chance for everybody who's doing it up probably still on the beds as we speak getting printed out yeah so thank you so much for hanging out with us but don't go anywhere the rest of the day later on tonight show and tell yeah we invite you to come on and show and tell everybody's welcome to come on we have a link to the stream yard in the discord chat rooms come in about 5 minutes 10 minutes early around 7.20 pm eastern time and then it goes live at 7.30 pm eastern time this week hosted by I believe Mr. and Mrs. Ladyata unless something else comes up and then immediately right after that is ask an engineer at 8 pm ET and take a look at all the cool new products coming out new projects and of course is in secret vault cool things are being worked on yeah JP is off this week he'll be returned next week but typically every Thursday at 4 pm ET check out what's going on with JP on Fridays we have a deep dive with Tim every Friday at 2 pm Pacific Pacific or 5 pm eastern on Sundays we have from the desk with Ladyata let's check that out at the great search with Digikey and then Mondays is the circuit python meetings you can hang out with the circuit python dev devs and community every Monday at 2 pm ET time Tuesdays is JP's private pick of the week I believe he's back right next week check out the blog posts and what not that's how you'll know I think he actually comes back the week after yeah typically every Tuesday at 1 pm Pacific or 4 pm ET you got it we do this show every Wednesday at 11 am ET time that's all I got yes but we'll be on the show until tonight we've got a foot paddle we might show off from last week and just probably preview these guys again maybe there'll be some more code that Philby's working on that we can show off so definitely check them out and sign up show us what you're working on it's gonna be it for this week thanks everybody so much good luck on your make your endeavors and don't forget to make a great day bye folks see you later tonight


Hello, thanks for coming, so quick update about myself. So I'm Thomas, I'm now a full-time employee of Mirantis who employs me to do as a full-time job, the OpenStack packaging in Debian. I used to live in China, I moved last December in Grenovo, so after eight years over there.  So this presentation will mainly get you informed about what happened over the last year in the community of OpenStack and as well some of the new features and new projects we have in OpenStack. Let's dive directly into it. So there's a bunch of features that have been added to many projects. I'll go to some of them, not all. So the Eraser Code, if you know about it, it's a kind of redundant CRC so that you can recover your files if you have some of the parts of your big file that is missing. So that has been added to Swift thanks to also storage policies. And we can hopefully use it soon in Debian. So I haven't finished working on the latest Swift. So also SR, SR-IoV has been added to Nova so that we have virtualized network interfaces. Another very nice thing that happened during this last year is that we have IPv6 support for Neutron. Currently it assigns one slash 64 to every tenant and that's it, no more, no less. But hopefully it's going to improve over time. So Glenn's has now support for the catalogue of Murano. I'll talk more about Murano later. And Horizon had previously all of its libraries embedded in Horizon itself. And as you know, it's not nice at all for distributions. And they decided to use a new mechanism that they call X-static, which enables people to use either virtual-length or system libraries. So all of that is behind us already. What everybody enjoyed so much during the last two cycles of OpenStack is the new federation system for Keystone so that you can have a Keystone to Keystone thing or through the SAML 2 protocol. And then finally after three iterations of it now we have a Python OpenStack client which is a unified interface on the command line to control OpenStack.  So for example, Keystone already has full support for that and already duplicates the Keystone command line utility. And there's some new packages that appeared in Debian which I worked on. So there's a designate which is DNS as a service. When it was released for JC it was kind of probably a preview release. Like it wasn't fully working as one would have expected. But I think it has grown up as an adult project. And now we have Sahara which is a big data as a service. So this is a primary Mirenzis project but it has been now integrated in all the other projects together so it's released together with the others. So Morano is an application as a service so you can imagine that you have a list of applications in Horizon and then you can click on one big icon with let's say Apache and then it will deploy that on your cloud. So that's what Morano does. Rally is also now part of OpenStack and it helps to test your cloud and profiling it. So finally, Aronic is usable so just before the JC release I decided that I would remove Aronic from JC because nobody didn't have support for it. But this has changed and now it's fully working with the Kilo release. So another thing that happened in the Debian Archive is that I started maintaining the latest OpenStack release directly in official backports. So right now you can use JC backports to install Kilo. So I did that because I wasn't really satisfied to have a non-official repository to provide these to our users. Of course I am still willing to use PPA when they are available so that I can have a PPA for every OpenStack release. So because like currently when the next version of OpenStack which is called Liberty, when it's going to be released I will have to override Kilo in the backports. So that's not ideal. So I guess you can still use snapshots.openstack.debian.org but maybe not everyone is aware of it. So PPA would be still a huge improvement for me. So a few pain points that I had to face during this last year. So before the release of JC, Raphael upgraded Django to version 1.7 and these broke lots of things in Horizon. Though I'd like to hear in this room tell everyone that Raphael has been really helpful and he helped me to fix everything nearly. So all this has been upstream into the Horizon package and then they benefit of all the Django 1.7 fixes. Another major pain point has been SQL Alchemy which has been uploaded a few months ago. So this broke a bunch of things in the Kilo that is currently in SID. So obviously it didn't break the backports because SQL Alchemy is still 0.9. Though it's my understanding that mainly tests are broken and not applications themselves. So that's still fine. And then there's another thing which is becoming harder and harder for me is that there's more and more projects to package. So it's not the package themselves but every new package with OpenStack comes with its own set of dependencies and new dependencies. So I have to work that out. There's a few persons that are going to hopefully contribute to the OpenStack packaging in Debian so it's going to be more smooth for me. And then finally about Python 3. So upstream is very aware of the Python 2 deprecation upstream. And then there's an ongoing effort that has been done upstream to support Python 3 especially by guys from Red Hat, like some colleagues of Sebastian, like Victor Stiner and Cyril, what's his family name? Okay. And then I've been adding support into the Python packages for the dependencies of OpenStack as much as I could. Unfortunately, some upstreams didn't make it and for example, a few... Yeah, I don't have an example in mind. But like Tableb, for example, has lots of embedded Python 3 incompatible packages that would need to be reworked. So if you want to participate into that effort, you can have a look to the wiki.OpenStack.org. There's a page that gives an overview of all the Python 3 related issues that we are facing currently. And then there's currently blueprints that are being implemented for porting Nova and Neutron and Keystone to Python 3 completely. And I'm not so sure about when I'm going to do the switch in the Debian distribution. So I probably will wait until I have enough projects that are fully ported to Python 3 so that I can do a complete switchover. And then you wouldn't have to have both Python 2 and Python 3 libraries installed on your system which would be some overhead. So that's the main idea. Yeah, so another thing that happened upstream is what we call the BigTent. So it's a... I think it started by a blog post by Monty, am I right? So he wrote what he thought... So before the BigTent thing, we had the concept of integrated release, meaning that we have a subset of projects that are integrated and security supported and scheduled to have release dates together. And then as new projects came by, we thought it was more and more important to include everyone. And then Monty Taylor wrote that post about having a BigTent where everybody would be welcome to join in. And everybody catch up an idea and thought it was the correct thing to do to include everyone. And then now we are effectively welcoming everyone, even maybe projects that are not as mature as the others. So what's happening is that we have a set of tags telling what is the state of the package. For example, does it have stable releases? Does it have security support and things like that? So that's the thing that I, as a package maintainer, look on to see if it's OK enough to reach the Debian archive. Just checking the time.  So the effects now is that there is so many new projects that came by. Here's an overview of the packages that are not yet in to Debian. So I expect to, in fact, worked on most of them already, like Congress, Dakar, Barbican, Manila. I already have some Git repositories on there for them. So maybe I should give a bit more details about it. So Congress is policy as a service as in general policies. It doesn't restrict you to any kinds of policies. Though I could give you an example of policies, like, for example, firewall. You could have some closed firewalls as a policy. Or, I don't know, you've used that much of bandwidth and then after some time will restrict you to a slower throughput, things like that. So it has a policy, I don't know, thing in it that will compute the stuff as a general thing with its own language. Dakar is queuing as a service, so it's easier to describe. It's just like Rabit MQ as a service, mainly. Mistral is workflow as a service, so it's like kind of scheduling things in a correct order. So Barbican is, I believe, in a very good shape right now, and it enables you to store critical things for crypto in its secure storage. So, for example, it's a good place to store your private keys for SSL. And then there's Manila as a service, which you can read, it describes itself. So here it was all the past of what happened over the last year since the last debconf, the last debconf. Now I need to talk to you about what's going to happen. So previously we had integrated releases and point releases, meaning that after a stable release of OpenStack happened, we had scheduled point releases every two or three months. Okay, so the release team of OpenStack decided that they would no longer do that anymore, meaning that there is still a stable branch that is maintained in upstream Git, but it's up to me as a package maintainer to decide when I release that and to decide whatever I want to call it. So the solution I've adopted so far is to name it after the date when I do it plus some kind of Git SHA or something. So it makes version numbers that big, but that's okay, I guess. And the other thing is that I'm not so sure about when I should do a point release and upload that to Debian. But that's the way it is, I have to do with it. And then more and more projects are releasing out of sync, meaning that they decide by themselves when they want to release a new version. So that's really, how can I say? It's not easy for me to manage because I have to decide by myself which version of which component are going to be able to work together. So for Swift, it hasn't been a pain point and it has always done like that. But for things like Eronic, I have to make sure that it works together with the version of Nova. So the idea was that they would still have versions that would be in sync with the rest of the other projects, but they don't really have to do that. So we'll see how it goes and hopefully it's going to work well. So another thing that is happening a bit more on my company, which is Mirantis, is that we are doing a derivative of CentOS and Ubuntu, which we call MOS as in Mirantis OpenStack. And it used to be a derivative of Ubuntu so that basically I was doing the Python module dependencies in Debian and then it would be synced into Ubuntu and then my company would pick them up from Ubuntu and then release MOS with it. So after a few meet-ups, we decided that they would pick up things directly from Debian if they can, but still supporting Ubuntu so that that's going to happen. So effectively after a few of these iterations, we'll have support for Debian directly into MOS, even though that's not what we are selling to our customers yet. And then another thing that happened, so during the last Vancouver summit, I had some discussions with Canonical about how could we improve the relations we have together and how can we more work together on the OpenStack packages. So this kind of discussion I've been ongoing for two years and I've always pushed for more collaboration with Canonical. So I'm not saying they don't collaborate because they do want to do some collaboration but there are still some blockers to do some full collaboration and having the same packages in both distributions. So on the Juno release, I've done all the package dependencies that they use for the Juno release. On the Kilo release, it was done separately because Jesse was frozen and therefore I couldn't upload directly into CID without overwriting both Juno and Icehouse. So when Jesse was released on the 25th of April, I used the five days before the release of OpenStack to upload all of Kilo, but then Ubuntu already worked out these dependencies. And then for Liberty, the very good thing is that we decided we would work together on these dependencies and then... Can I use that? And then Ubuntu people decided that they would start maintaining these dependencies directly into Debian Experimental. Why Experimental? It's because, again, I don't want to overwrite Kilo, which is the current stable release of OpenStack. So then I upload all of Liberty into Experimental. So I have to do that because many packages go through Nu. So it needs to be there in Debian before Liberty is released upstream. So that is the good thing about the discussion is that Ubuntu does work in Experimental with me together. And then during this discussion, we decided that we would do the packaging into Stackforge. So who here doesn't know what Stackforge is? Okay, a few. So in OpenStack, we have the GitHub slash OpenStack slash something. And we also have OpenStack slash Stackforge, which is a forge where we put things that are not completely ready yet. So the idea was to put the packaging of the server packages, so like Nova, Neutron, Cinder, all of that, into Stackforge and use the upstream gerrit to gate the packaging artifacts there. So Canonical wanted to do it, and then after I opened that thread on the mailing list upstream, they retracted of that idea and decided they wouldn't do it anymore. Though my proposition was already ongoing, and people from Red Hat catched up on their idea and moved from what was OpenStack packages, they moved from that to the slash OpenStack namespace. Because Red Hat guys are doing it, I don't see why we shouldn't do it in Debian, so I'm still pushing for it. So the way it works in OpenStack is that you do a patch to the governance git repository, and the technical committee approves that new project or not. So I'm very happy to announce that on the 13th of August, so like during that camp, this project has been approved by the upstream OpenStack technical committee. So effectively we'll be able to start doing that work. Unfortunately, there's mostly some people from Mirantis that are willing to work on that, and I hope that is going to be others. So I very much welcome people from HPE to work on these upstream OpenStack packaging efforts. So what it means to do upstream packaging? So currently, what I do is that I have a git repository into Alioth, and then it has a receive hook and then sends that to Jenkins that builds the package for the back port in Jesse. What it means to use upstream is that I have mostly like unlimited computing power resources. That's the words from the infra team in the Vancouver stream. So it means that I'm going to be able to do a lot, a lot more of testing. For example, a full deployment of OpenStack using packages on every commit that we do on the git repositories for packages. So it's going to go on review.OpenStack.org, meaning that we're going to use Garrett, and that anyone will be able to propose patches without fearing to break the wall. So also it means that it ends the story of should I grant ACLs for writing in the git repositories or not? Now everybody is going to be able to provide patches and they are going to be peer reviewed, so we don't have this problem of security anymore. Also, I hope that I'll be able to do some more testing on two parts, LinkedIn and things like that. So in fact, upstream is already having this kind of test with what they have internally. For example, Garrett, no, sorry, Zool and Notepool are already built this way upstream as debiant packages for trustee. So because we agreed to work with Canonical on the OpenStack dependencies, what is going to move to this review system is going to be only the server packages and not all these dependencies. By the way, it doesn't really matter because I see more people interested in contributing to those rather than all the, I don't know, or slow-utils package that nobody really cares about. As long as it's there, there's no controversy of what functionality it should bring or not. It's just a library. So also probably at some point we'll be able to introduce some non-gating tests for upstream patches to make sure that a patch doesn't break whatever is packaged because sometimes some patches do not break the gate but they do break packaging. So we also hopefully improve quality and avoid breakage in the long-term. And another long-term goal is to be able to do packaging from track, meaning also from master branch of the gate repositories. So currently I package every beta release of OpenStack, meaning that for me as a package maintainer I have a new version every two months or something like that. Like the next beta version for Liberty due for early September for FYA. So another thing that would be nice would be to have Garrett package in Debian. So I already talked about that during a session about continuous integration for packages. So as I said during this session, two weeks ago I didn't know anything about Maven packaging in Debian. And indeed it's... How can I say it in nice words? I'm not a fan of it. But I still want to have this happening. I hope that... I'm sure that I'm not the only one that wants to have Garrett in Debian. But I'm not sure I'm going to be the only one working on that. I have to warn everyone that if I'm effectively the only one working on this packaging, I probably will give up. So there's already... Johan, Stan, where are you? Over there, that helped me a lot understanding things for doing Java packaging. If I can have... I don't know, like two more volunteers to do the Debian packages that maybe we can have something in not so long amount of time. So we do need Garrett packaged. Let me check on the time. So where was it? We do need Garrett within Mirantis for our own infrastructure because currently what we do is that everyone even upstream we just use the WAR file from Garrett upstream and then use that to install Garrett. Obviously that's not what we do in Debian. We want every Java library to be packaged meaning that and also the real dependencies meaning that for packaging Garrett we need first to package Buck which is a build system that Garrett is using. By itself it's already like such dependencies Johan. And then once we have Buck then we have to do Garrett which is again maybe such packages or more. Take a mic, take a mic. So we started working on Buck. Buck uses Ant for packaging and most of the dependencies are already in Debian I think. There are a few missing. Jet is the most complex one but after that I think we can package Buck. And hopefully after packaging Buck we have a straight line to package Garrett. Garrett has also a lot of dependencies already available in Debian so hopefully it will be okay. So you feel free to get in touch directly with me if you want to join that effort. So I'm Zigo at Debian.org. Also with me. Can you tell your email address? Yes it's stan.iujin.gmail.com I know a lot of Java but I don't know a lot about Debian packaging and especially Java packaging in Debian. So yeah, thanks. So the idea of packaging Garrett is to have it for me in my merantis and upstream in OpenStack. And then the idea is also to have it in Debian so we already have something like Digit to interface all of the Debian archive with Git. What we could do if we have a Garrett package would be interfacing it Garrett with Digit for example or something else but Digit seems nice idea and that anyone could submit a patch against a package. They would have a CI that would run build of the package Puparts, LinkedIn and Search with a voting gate like we do in OpenStack and then whoever is the uploader or the package maintainer would be set as the core reviewer for the package and would be able to approve the patch or not. So we already have the list of core maintainers in Garrett.  Can you raise your hand if you don't? Okay, so like mostly everyone knows. So that's one of the big reasons that is motivating me to do it. Another thing which I worked on is porting MOS and fuel to Debian. So, Fuel is a web interface that helps you to provision an OpenStack deployment. It's mainly maintained by Mirantis but it's also a community project maintained in upstream OpenStack and in fact we're pushing it to be more and more a community project. So, basically you have a discovery bootstrap image that the computers are PXC booting on. This one reports what type of CPU the amount of memory, the amount of hard drives and then you have it reported on your web interface and then you can select the compute nodes. So, yeah, I have a few snapshots to show you what it is. So, first you create a new cloud deployment with some values which you can select. Here for example you want to use VLAN, GRE, newer versions that also support for VXLANs and so on. And then on the top left corner you can see what the discovery bootstrap image has reported. So, in my case in the Debian port it's using Debian Live so instead of using a huge NetRD file that is currently in use in full I use Debian Live with the standard Debian channel and then it fetches the SquashFS which is so much faster than a huge NetRD. So, on the up you can see the list of compute nodes of nodes, sorry, then you can select them and then assign a role that you see on the bottom screen. So, for example, you select one machine and say this one is my cloud controller or my compute node or storage node, something like that. So, that's basically what Fuel is and so I've tried to port it to Debian. Unfortunately this isn't really on my company's agenda and I'm not pushed to do it on my everyday job but I still hope to be able to provide it to Debian because OpenStack is still very hard to install and having this would help a lot the end users. So, that's about what I have for my presentation. So, if you want to contribute you can I suggest that you read that first page OpenStack.alios.debian.org that you join IRC, register to the mailing list and then if you want to help one thing that you can do is either go through the list of bugs and try to fix some or package something new like I already mentioned, for example, Mistral I haven't worked on that at all so that would be a good exercise if you want to join and then after you will understand how everything is working, though I have to admit that so Andreas Thilo did a mentoring of the month with someone that he helped to package Manila and I have to admit that the curve is a little bit steep to do the first package but once you have done one then it should be okay because there's some specific things like packaging an OpenStack server that you don't really see on other packages then because there's lots of security fixes having help on security fixes back ported to JC would be very helpful if someone here in the room wants to take care of this I would very happily delegate that role in the team another thing you could work on is joining docs.OpenStack.org and contributing to the Debian install guide and then finally we are hiring in Mirantis and I hope to I have a few candidates but basically it would be either someone that would work on upstream code or someone that would work with me on working on Debian packages directly in Debian or somebody working with Puppet for the deployment there's many rules but me I'm mostly interested in finding somebody working with me on packaging OpenStack in Debian yes so anyway I was finished so I'm open for questions there's 10 minutes I was hoping to leave more time so maybe 10 minutes will be short the first I actually on the slide of the documentation on workflow that still has you building Debian packages against the private Mirantis Debian repo but where's the updated documentation around the OpenStack Garrett workflow upstream OpenStack.Garret workflow is not there what you see on the OpenStack.io.Debian.org is to maintain the packages in Debian not in Mirantis let's talk about it afterwards alright so is there any other questions so would there be anyone that would be interested in having a buff later on so if you are interested please raise your hand 1 2 3 4 5 ok enough then ok so I'll add a session on the on the blackboard on the lobby then or maybe we can decide just after this when to do it any question ok that might be a little bit naive question but assuming I would start packaging how to test OpenStack packages should I have many computers to test to build my own cloud environment or should I do something else so yes you can do that though every OpenStack package has a set of unit tests so it's been a big part of the work of doing the packaging to also make sure that the unit tests are working properly once you have done that then you can run Tempest do you know what Tempest is? Tempest is a set of functional tests so in the archive there's a package called OpenStackDeploy and these are scripts to deploy full OpenStack cloud inside a single machine using QMU and not KVM so that's what I use after a release to make sure that OpenStack is functionally working so I'm not check gating every patch on that but I hope it's going to happen afterwards so currently what I do is package everything for a release, run that test and then if I have not too many failures then I consider it passed and then I say ok I release like say OpenStackKilo you could do that all that is great and in Debian so just look at the sources of OpenStackPKG tools and OpenStackMeta packages and OpenStackDeploy which is in OpenStackMeta packages and then you'll find out any other question? who in the room has already deployed OpenStack? oh I'm surprised nice who here in the room has deployed it on Debian ok nearly the same amount so maybe you can tell me what kind of pains you had using the packages I've worked on I'd be very happy to hear about that if it's not a question just some feedback I'm sure there's loads of issues no one wants to tell about any problems you found? we still have plenty of time so some feedback please looks like nothing so I would thanks again there's a question hello we didn't use the Debian packages back then but the Ubuntu packages back then and it was quite annoying that it's not that confident but the Debian packages why don't you use the non interactive mode then? afterwards we told it ok just get out of our way use the non interactive mode but then still sometimes when you do backup it gets ok I didn't have the opportunity to ask that question ask them again during updates so that was one minor issue we had with that we used the pkg reconfigurer devconf you are always in non interactive mode later on it might be an option but this was our first setup and it was quite a bit annoying so one of the reasons I maintain all these devconf things is also for my CI because I want to be able to deploy the full open stack without using pipettescript and that's how I configure open stack to be able to do functional tests so one of the things I've been thinking about was having a file called edc open stack devconf or something and then no devconf and then if it was there then just disable everything so could be something you want to use could be an option yes anyone else? my question is how fast can you install open stack with the new packages on open stack on debian right now for example for someone reading the documentation and having general knowledge about networks and stuff someone new to open stack that don't know anything about it and wants to set it up? mostly it has a basic understanding of cloud and how stuff works so I think it would take that person some amount of time to just understand how to make sense of that t-shirt and so you have to understand which component is for what and that can take some amount of time by reading the documentation once you have done that maybe a few weeks to make sure you know what to set up and where then you could try in one day to set it up and one week to debug it like the most painful part is always the network so I'm maintaining some meetup packages to try to help people to know which components go where for example an open stack compute node that deploys the nutrient agent and the compute agent on the node so that's one of my long term goals is to make it super easy with fuel okay thanks so the kilo installation guide for debian upstream and open stack was removed because it's broken because it doesn't work did it back in liberty or do we still need a lot of work there's a set of install guides that the open stack project links to and they link to susie red hat sent ospedora and ubuntu but not debian anymore so in fact that's how can I put it in a nice way I'm not happy about what happened because someone from rack space opened a bunch of bugs against the documentation for open stack which were more rents than real action bugs I could have actions on and then finally it was removed because I wasn't watching the list and one of my colleagues was supposed to work on it and then he was assigned by his boss to do something else stuff happens mainly I just want to know for liberty do we have a good list of things that we need to get done when kilo was released they started to do the conversion from the maven xml documentation to rst and then I couldn't work on it at all it was like frozen and now the rst conversion has happened I believe for the install guide and now a blueprint for implementing the documentation for debian has been approved as well and hopefully for liberty we will have the debian documentation for the install guide back again in stringdocs.ovencyle.org so that's something you could use help on because you don't need much experience to try out the install docs and see if they work or not and as well you could use the Juno documentation which is still online but of course it would need updates for kilo and liberty which will never happen well that's one thing that needs a lot of help and that everybody can work on now it's rst format it's not the cdxml maven thing we used to have so it's easy to work on so our time is run over one more question is there a preferred network stack in debian open stack or you're just using neutron as the network component because I've read I haven't experienced myself but I've read that there are scalability problems with neutron and I don't remember this alternative software from jupiter so that's one thing I didn't mention but in neutron we used to have all the drivers that were contained in neutron and now all the drivers for specific network vendors have been taken out of 3 and packaged in separate packages so I haven't worked out all of them because there's so many I believe maybe 12, something like that 10 or 12 so neutron is the definitive stack that you should use and then you can plug some hardware vendor drivers on top the scalability problem that you are referring to is probably with GRE tunnels so as you have more and more compute nodes you have and you use GREs GRE tunnels and then you have a kind of mesh of tunnels from 9 nodes that would be 9 times 8 times 9 7 so factor of 9 and this can also bring a huge load on your CPU but since now we have VXLAN so VXLAN is the recommended way to do networking these days with neutron if you don't use a network vendor or driver so off the shelf hardware for VXLAN is the best option if you want to go cheap and otherwise you can use Juniper, Melanox or this kind of vendor that have specific hardware designed for open stack so thank you Dan we will do above and thank you everyone for attending thanks Zigo for the presentation


Welcome to the journey. Today we're talking about seven ways to create multiple income streams as a web designer. Do you remember when Amazon used to own these sell books? Well, if you'd like to experience more top-line growth in your line of work, like mine too, it's high time you follow the lead of the world's largest internet-based company and create multiple income streams. As a web designer, you're in luck. There are a number of revenue generating services that your existing clients desperately need. And here are seven ideas to set your entrepreneurship wheels in motion. Starting off with search engine optimization, or SEO. At this point, even mom and pop stores understand there is at least some SEO that is necessary for their online success. What they might not understand is exactly how that works. When presenting this new service to clients, there are a couple of things that you should avoid. Starting off with overwhelming them, SEO and marketing aren't their areas of expertise. That's why they need you. Going into too much detail will only complicate an already complex subject. Also avoid playing the magician. However, being too vague will quickly raise red flags. Don't keep your methods a mystery. Give a straightforward overview of what kind of approach you plan to take, as well as milestones that the client can expect. This next one is something I dabbled in as a web designer, and that's social media marketing. And whether it's scheduling social posts and responding to comments and segmenting audiences and designing targeted ads, social media marketing is a great tool to expand multiple income streams. This provides you with an excellent response to remarks like, my website doesn't have any traffic and nobody is reading my blogs. Well, with the little skills SEO and social media marketing, their website will finally reach the target audience they aim to convert. Let's talk about content writing. I think most web designers will know exactly why content writing is on the list. How many of your projects have veered off course as a direct result of the content backup? The client slowly checks off each point of your project timeline. That is until you reach the content collection stage. Right. You can imagine the website just hanging out with Lorm if some texts all over the place while you're waiting for the client to provide you what should go there in the first place. But pro tip, do both yourself and the client a favor offer content writing as an add on service to web design. And this next part is probably one of the easiest ways to add additional revenue. And that is by providing ongoing support and development in the form of care plans. Now, ongoing support and ongoing maintenance can serve as a solution for a number of website problems faced by the client. For example, if the client wants to make regular website edits, but doesn't know how, uh, wants a web design that never grows outdated, or they want to keep plugins and security up to date. And lastly, maybe optimization through like AB testing to see whether they're the site that you've built is the best optimized. These monthly maintenance packages or website care plans are popular with small businesses while conversion optimization appeals to clients with larger budgets. Not to mention it shows not only your attention to detail, but a dedication to their business after the deal is done, which if done right, boost your reputation and credibility. And now one thing I do like to do with these website care plans is I like to talk about this upfront and the actual web development process. Don't wait to the very end and then hit them with a, oh, I can also offer these services. Let them know that this is an option during your proposal stage. You'll have a much higher success for them saying, yes, now that they know about it and know all the hard work that goes into it, you can offer your own web hosting and this pairs very nicely with ongoing support and development. And you don't need to be a CIS admin expert or full stack web developer, reseller hosting plans and partner programs will let you white label hosting from another provider and your clients, they will see your business as their single point of contact, but you'll have a dedicated team there backing you up. Yeah. And you'll also have more control over your client's website set up in the backend server configuration. And depending on the reseller program you join, you may also be able to provide more services beyond just web hosting. For example, GoDaddy reseller program members can also offer domain registrations, SSL certificates and other white labeled GoDaddy products to their clients. Now let's talk about WordPress themes and customization offering ready made website templates at a lower price than custom web design will allow you to earn the business of audiences on a tight budget, right? And your strategy might not be to make money on the templates themselves, but just getting your foot in the door and establishing a relationship with new clients is worth offering less expensive services. And as they grow, they'll have more resources to invest back into their business. Let's not forget an SSC for any business using WordPress themes customization, unless they want to run the risk of laying the same website as Joshmo down the street, they'll need a few adjustments. And for those who are unable to tackle adjustments themselves, customization would make a great add on service to their theme purchase. Before you dive into creating multiple income streams, as with any investment in business, there are risks. And even if you manage to establish multiple income streams without spending money, you're spending your time that sweat equity, which is ultimately of greater value. Yeah, so start by asking yourself a few simple questions. What kind of website problems do my customers frequently run into? Which services do my competitors offer in addition to web design? And what does keyword research reveal about the services I'm considering? Now, after you feel like you have zeroed in on the service or services that you would like to offer, run it by your peers, friends, family and customers and pay close attention to their feedback and wait until you are 110% certain before communicating the change to your audience. Nothing cries unstable like a business that announces new ventures on a whim. Nowadays, retail sales, let alone books can hardly take credit for Amazon's success. Much of the company's profit comes from Amazon Web Services, their cloud computing platform, creating multiple income streams as a win for all businesses, not just retail giants like Amazon. There's no telling what this will open up for your web design business. All right, that's a wrap. You just learned seven ways to create multiple income streams as a web designer. Be sure to comment below and don't forget to subscribe to our channel. Make sure you ring that bell to get these episodes first. This is The Journey. We'll see you next time.


Welcome to the ITU headquarters here in Geneva, which is of course hosting the AI for Good Global Summit. And I'm really pleased as our first guest is the CEO of the XPRIZE Foundation, and it's Marcus Schingles who's with me right now. Hello Marcus. Hi. So tell me, why is XPRIZE part of this international dialogue on AI? Yeah, so artificial intelligence is important to the work that XPRIZE does. We're a non-profit organization that tries to use very progressive and contemporary means for solving problems. We align with the 17 SDGs of the UN. We have a very similar mission in mind. But our model is such that we crowdsource solutions from teams around the world. We essentially gamify the innovation process by leveraging a $10, $20 million purse, making a competition, and then asking the whole world to compete. And the reason why AI is particularly relevant is because moving forward, we can envision a really many problems that the teams that compete on the XPRIZE are going to be solved without having AI in their tool set. We're talking a lot about AI right now. I mean, it's such a hot topic right now. What would you say is the most exciting about it at the moment? Well it's been around for a while of course, but the most exciting thing that kind of makes it not your father's AI is the progress of deep learning and machine learning, AI, which is kind of the next generation of artificial intelligence, which is computers essentially being modeled off of the brain, off of neural networks that is propagating a learning capacity, the capability to learn. And that's what deep learning does. That's why you see the progress right now combined with tremendous computing power and the exponential trends in computing power fueling more sophisticated AI. So in general, it's not only an exciting field now, but it's going to be a field that is going to completely transform the landscape of business, of culture, of politics, and for XPRIZE of how we solve problems. Now of course, this is going to be a three day discussion. How can in your opinion AI accelerate the solutions to the UN sustainable development goals? Do you see XPRIZE contributing to these solutions? You know the thing that's interesting is the UN itself is not going to solve the SDGs of course, and the traditional problem solvers, industry, government, the traditional problem solvers that society has grown accustomed to are essentially very linear in their methodology for solving problems. It's just how they're intuitively wired. It's meant to be consistent and process driven. The world is exponential. It needs much more agility and it means much more experimentation. You're only going to get critical massive experimentation if you can get individuals to participate. If you can start to tap into seven billion to eight billion people on the planet to solve problems, to solve the SDGs, statistically speaking, you're going to find those needles in the haystack that can solve problems. Fortunately, AI is a democratized technology. It's a technology that used to only be afforded to governments or big business. But now it's something that my son who's in college is using today off the cloud. He's using AI and the type of work that he's doing. It's just a phenomenal progress of the technology and it's going to be applicable to solving problems, particularly the SDGs. So there's a final question. Would you say that AI then is actually probably, it's an easier breakthrough technology than other ones were because it's so user friendly? I don't know if it's necessarily easier. It's riding the computing power wave that is a doubling, that's an exponential trend. And so the more powerful computing gets, especially as we go to new forms of computing, AI will really take advantage of quantum computers and new types of computers that evolve beyond the integrated circuit that we have today. And that's all happening as a convergence of trends that are going to result in AI. And then when you combine AI with robotics or 3D printing or biotechnology or cognitive analytics or advanced medical tech, it's just a transformational technology. And it truly is something that we're experiencing today. It's a totally relevant discussion for us to be having. It's particularly important for the United Nations to be having this as part of the ITU because there's a dialogue that people will use to understand exponential trends versus linear trends, AI being one of the significant forces as a result. And this will be totally transformed in five years anyway from what we're thinking now? It really will be because you can't look back at the history of artificial intelligence. You can't say, well, my linear brain says AI beat a chess player X number of years ago. So I'm expecting another 30 years before it does something of that magnitude in terms of its growth rate. That's a very linear perception. It's the way humans evolve and human intelligence evolves. AI intelligence doesn't evolve that way. It evolves exponentially. So what we see in the next few years could very well represent what we've seen in the last 50 years in terms of the progress of AI. And that's really legitimately what's happening right now. Well, stay tuned. We'll be back in touch in a few years and work out what's changed since this conversation today. Well, you never know. We might be in a virtual environment right now. This might not be real. It's an AI simulation, perhaps. OK, you never know. We'll see what happens. Yes, thanks again. Thanks, Marcus. Thanks, Marcus Schingles, who is, of course, the CEO of the X Prize Foundation.


So, like my favorite cricketer Dhoni says, you get the toss, sometimes you win the toss, sometimes you lose the toss, we got the last talk of the day. So, I appreciate you all being here. When we, when I realized that we had the last talk of the day, we were like, what can we talk about that hasn't been covered in the last four days? What could be left? Right? And then, you know, it wasn't very difficult to arrive at something, which was we can talk about our experience. That is something that's none of you have, right? You have not been in a situation where me or KK have been. So, mostly what we're going to cover today is through our experience. We'll talk about some of our experiences that we have had. And since it's the last talk of the day, I will exaggerate my stance a little bit. Okay? I will say, no, this is wrong. Or I might say, this is bad. I don't really mean it. Okay? So, don't get mad at me. I don't mean all of it. I mean some of it. I know the truth lies somewhere in between. But I will tell you that these things are probably wrong and you shouldn't do it. Okay? We can talk about that. You can ask me about it. If the question, if the answers don't satisfy you, we can talk offline afterwards as well. Okay? So, I'm not going to explain what my talk is about. We're going to talk about, we'll see it as we go along. My name is Krishnan. I'm the founder of a startup called GeekTrust. I help developers find, good developers find good opportunities. That's what we do. Before GeekTrust, I was with ThoughtWorks for close to 10 years. I worked as an agile consultant, project manager, delivery manager in the US, UK, Australia, and mostly in India. Over the last few months, I've been unlearning a lot of things that I've learned as to what agile means. When it's my own money, I'm very, very lean about it.  I'll share some of those as well today. Cool. I think few of you might already know me. I presented talk on Wednesday on the other room. My name is KK. Yeah, so that's how I entered the room. My name is KK. I've been with ThoughtWorks for the last six years. I've been with the IT industry for the last 11 years. My agile journey began when I joined a startup nine years ago. I haven't heard anything about agile until then. Even when we were doing the startup, we didn't know anything about agile. Think about it in retrospective. I thought that was the most agile team I've ever worked with. That's when I realized all these terms and all these practices and processes that we talk about, you could do without really learning if you really know what business value you want to add. So that's me.


Welcome to the Department of Anthropology and Sociology. As a leading anthropology department, we offer five MA programs. MA Social Anthropology offers a broad introduction to the discipline and a wide range of optional modules. MA Migration and Diaspora Studies focuses on the study of human mobility and forced migration. MA Anthropology of Food offers specialist training on food systems and food cultures. MA Anthropology of Global Futures and Sustainability enables students to explore and tackle the major debates of our time from climate change to socioeconomic inequalities. Lastly, the MA Medical Anthropology in Mental Health addresses pressing global challenges in health and mental health from diverse perspectives. Studying at SOEZ is unique as it draws from the regional expertise of our academics in Asian, African and Middle Eastern languages and societies. If you're passionate about understanding human society and behavior and want to think critically about the world around you, Anthropology at SOEZ is for you. SOEZ is a unique place to study and what makes it unique is the people. You'll be part of a diverse, multilingual and engaged student community who are committed to exploring the vast range of human experience in a complex world. Once you graduate, you'll be equipped with the necessary skills that enable organizations to address the challenges of today. Employers value our graduates' cultural awareness and global perspective as well as their skills in analysis, data interpretation and problem solving. As a SOEZ student, you'll acquire the methods and theories to make a difference. We invite you to study with us and explore what it means to be human in a fast-changing world.


When populations flee their homes, within or across international borders, addressing emergency needs remains critical. But without sustainable solutions, populations can remain locked in crisis dependent on external assistance for years or even decades. This is why IOM has worked with community leaders applying development principled approaches alongside humanitarian assistance to every major crisis since the early 90s, learning from each one. It is not always just one event that causes people to flee, but the underlying vulnerabilities that left them no alternative. Populations need to identify which vulnerabilities need to be addressed in order for communities to recover. Displacement can be quick, but establishing the conditions for recovery and development is typically a long and challenging process. To achieve long-term recovery, IOM's transition and recovery division follows eight core principles. Be holistic. Groups can make progress towards recovery only to find an unresolved grievance, destabilizing group or environmental hazard can undermine recovery. Assess, analyze and understand what factors, including underlying factors, contributed to the crisis. The different needs of crisis affected groups are interdependent. Failure to address the needs of one group may undermine progress in others. Allow all the different sectors of intervention and ensure an integrated or area-based response. Invest and start early. Transition and recovery interventions often will run in parallel with the emergency ones. From cash handouts to cash for work, from emergency healthcare to rapid rehabilitation of health infrastructure, be rights-based. Group individuals access their rights and help organizations and institutions fulfill their obligations. Although post-crisis government might be overwhelmed and poorly functioning, it is important to build their capacity and support them to be more accountable, accepted and trusted by the communities they serve. Be conflict-sensitive. No intervention that transfers resources is considered neutral by people in a resource scarce environment. These resources represent power and wealth. Avoid inadvertently creating or exacerbating tensions that could lead to conflict. All activities, including local recruitment, should take into consideration local power relationships, customs, values, fares, systems and institutions. Programs should actively seek individuals who can build bridges in their communities, resolve grievances or promote peace. These are often women or youth leaders. Be flexible. Post-crisis or at-risk environments are inherently dynamic and unpredictable. This affects both budgets and plans. For interventions in crisis areas, it is good practice to implement rapid, small-scale projects targeting specific needs. This means that donors need to be engaged on a regular basis. Think long-term. Lay foundations that can contribute to the sustainable development goals. Remember, in the longer term, local authorities will have the primary responsibility for the populations they serve. Work to support them. Be participatory. Empowering individuals and groups to take control of their own recovery is the best way to ensure the sustainability of the assistance provided. Utilize local skills and knowledge as well as existing community groups. Involving communities from the start to assess their true needs, strengths, weaknesses, opportunities is key to building a more resilient, peaceful society. It is also essential to listen to all voices, not just the most powerful or loudest. The quieter voices may also be those that are marginalized from civilian life. Strengthen resilience. Enabling communities to withstand the impact of future social, economic and environmental shocks requires working with an awareness of what those shocks might be and building local resilience. For example, through diversifying livelihoods or rebuilding robust infrastructure. These core principles have been developed from decades of experience in the field. They contribute to global commitments made through the grand bargain and new way of working endorsed by the World Humanitarian Summit in 2016.


Hello and welcome to the International Daily Roundup with People's Dispatch where we bring you some of the top stories from across the globe. Let's take a look at today's headlines. Number of COVID-19 deaths reaches 100,000 in the US. Brazil overtakes US in daily death toll. White spread outrage over police racism in the US after the murder of George Floyd. Indian social movements decry arrest of feminist activists despite bail orders. Noomsa criticizes commoners' management for failure to pay salaries. Costa Rica legalizes same-sex marriage in a victory for progressive movements. We begin with an update on the global coronavirus pandemic. The total number of COVID-19 infections has gone up to over 5.7 million with over 352,000 deaths as of today afternoon. The number of deaths in the US has crossed 100,000. Brazil, which has been witnessing an explosion of infections over the past week, on the other hand, has surpassed the US in the number of daily deaths. The South American nation reported over 1,000 new deaths on Tuesday compared to 770 in the US. In the meanwhile, doctors and health care workers are raising concerns about extremely unsafe working conditions. In a statement issued earlier this week, doctors at the Almanira Hospital in the Egyptian capital Cairo have threatened to resign en masse. This came following the death of one of their colleagues, Valid Yaya, who died from COVID-19 on Sunday. Three other doctors also died of COVID-19 on the same day in Cairo. Doctors complain that the Ministry of Health in Egypt has not provided them with enough PPEs. Doctors have also alleged that the government failed to take effective quarantine measures leading to a higher number of infections among medical staff. Some of them also complained of the lack of testing kits for frontline health care workers. A few doctors in other hospitals in Cairo have already resigned to protesting the lack of equipment, tests and adequate facilities. The Egyptian Medical Syndicate and National Trade Union Federation of Doctors has released a statement warning of a medical catastrophe in the country. The statement warned that the health system in the country could completely collapse due to failure and negligence of the Ministry of Health. According to the EMS, 19 doctors have died due to COVID-19 in Egypt since March of a total 350 who tested positive. In our in-focus section, we bring you a conversation between Vijay Prasad and Arun Dati Roy on the COVID-19 pandemic, lockdowns and the role of governments. Today is a very special day. We have with us Arun Dati Roy, the author of two luminous novels, The God of Small Things and the Ministry of Atmosed Happiness. Last year, she published her collection of non-fiction with a very great title, My Seditious Heart, a title that I think is not only very clever but very opposite. Recently, during the midst of the COVID-19 great lockdown, she's written two pieces in the Financial Times. First, the pandemic is a portal and now after the lockdown, we need a reckoning. Arun Dati Roy, welcome to NewsClick. Well, let's start with the first article, the pandemic is a portal which the Financial Times ran and I mean, I know this article circulated enormously. Could you tell us a little bit, firstly, it's written in your phenomenal style, it's really lovely, but could you tell us just a little bit about this idea of the pandemic as a portal?  I don't think there's been a time in history where the whole world could be locked down for good or for bad. It was a very frightening idea for me that people, governments, states, authoritarian, democratic, communist, whoever could exercise such power. And then when you exercise that power, the chemical experiment of people who were outside the purview, outside the imagination, outside the calculations of these states were these millions of people who started to walk, you know.  And I thought, you know, is this, are we dying or are we being born, you know? Because as individuals, we don't have a choice about when we are being born and when we are dying. But perhaps as a species, we do, you know. Some control we could exercise on this. And so I thought we are in a portal between worlds, you know.  But then suddenly when you saw the potential of healing that the show that the Earth put on, you know, we thought, okay, maybe there is a moment of hope in the midst of this despair or maybe it's just greater despair. But certainly it's a moment of rupture, a moment of choosing. So that's why I thought of it as a portal. Now going to South Africa, the National Union of Metal Workers of South Africa or NAMSA has criticized the management of the airline for its failure to pay its workers their full salaries. The airline's management opted to go for the business rescue provision early in May whereby the company will be protected from its creditors but placed under the control of the business rescue practitioners. At that point, NAMSA had condemned the move as a way to escalate retrenchments. Fakamele, Lubi Majola, the national spokesperson of NAMSA spoke to people's dispatch on this issue. The National Union of Metal Workers of South Africa condemns in the strongest terms the fact that the management of ComAir has refused to date to pay workers their salaries. Our members have only received salaries for the months of April as well as for the month of March. In the month of April, the company made a unilateral decision to take leave and use that leave as a means to pay workers' salaries. This was not something which was consulted on, they simply took that decision. In the case of the month of May, workers have not been paid at all. There's no explanation from management about what the situation is or whether this money will be paid and if it will be paid, when it will be paid. We've just been told by the CEO, Renault Standard, that the company has applied for the COVID relief from the UIF but beyond that, there's no explanation and there's no detail about when workers can actually expect their income. Secondly, this situation is made very much, much worse by the fact that prior to the lockdown, ComAir issued Section 189 notices to workers of its intention to retrench. And it's very clear to us when you look at the behaviour of management and also the subsequent decision to place the company under business rescue that COVID-19 is actually being used as an excuse to restructure the company. The management, together with the BRPs, have unilaterally suspended benefits and conditions. I mean, this is unlawful, but they've done so anyway. And the BRPs have done it without even bothering to consult any relevant stakeholders. We see very clearly a pattern of behaviour between the BRPs at ComAir and the BRPs in SAA, where they literally are just a law and to themselves doing as they please and are accountable to no one. As Noomsa, we condemn this in the strongest terms possible. Our members are demanding that the CEO must resign. They say under her tenure disastrous decisions have been taken and the fact that the company finds itself in distress right now is a direct result of her poor leadership and they demand that she must be removed, because in their view, she has no strategy for saving this organisation. The statement was issued on behalf of Noomsa by Pagamile Khubimajola, who is the national spokesperson, and also the person who recorded the sound bite. Finally, Costa Rica has become the first Central American country to recognise same-sex marriage. In August 2018, the Supreme Court had asked the Costa Rican Parliament to amend the family code which bans gay marriages. The code had set a deadline of May 26, 2020, which was yesterday, to make the amendment failing which same-sex marriage was to automatically become legal. The parliament, which was deeply divided over the matter, neither voted to amend the law, nor did it appeal for an extension of the deadline. Nevertheless, Costa Rican President Carlos Alvarado tweeted celebrating the new amendment to the law. Alvarado had promised to act on the ruling issued by the Inter-American Court of Human Rights in 2018, asking the countries in the region to legalise same-sex marriages. The legalisation of the same-sex marriage is a big, big trip for the left and progressive movements in the country which have been struggling for it, for over a decade now. Movements after the legalisation, a lesbian couple, Darita Raya Agueta, and Alexandra Quiroz Castillo, got married. Their marriage was broadcasted on the state television. And this is all we have for this episode of The International Lady Roundup. For more such stories and videos, log on to our website peoplesespar.org, subscribe to our YouTube channel and follow us on Instagram, Facebook and Twitter. Thank you for watching.