Cool, so let me know what people are seeing. I'm monitoring the chat you are live so we're Yep, so I'm gonna go ahead do our count off and then everyone. Let's go. It feels tested. Let's go. We got okay Alright everyone. We're trying this again Let me know how the quality is. Let me know if I'm cutting out a whole lot. It's quite possible But we'll try this one more time So I don't know what you all caught of the introduction last time But this is fields tested and I'm castling fields And I'm gonna I put this in earlier because we were having so much trouble And I went over the code of conduct and I went over some of the shows that you're gonna see later So I just want to give another brief introduction to what I'm trying to do here which is I'm trying to give Give everyone a chance to see cloud native technologies in some form of context So I'm gonna try to do kind of small projects with cloud native technologies And the one today with this super broken slide is going to involve Both Kubernetes and technically you can argue container run times And it is inspired by I really need to fix these animations I'm gonna skip that It's inspired by Thanks pop Sorry, I'm such a mess today first stream So my goal for for today is to try to host a personal blog on Kubernetes, which we're off to a great start on We'll see how this all goes But it's inspired by this tweet which I posted on Twitter Hopefully a bunch of you have seen it before where someone is trying to create a sandwich using Using power tools Which I would agree kind of feels like what hosting a personal blog on Kubernetes seems like to me But like I said in my promo if you saw that what good is an opinion without empirical evidence? So do I have other stuff in the slide deck? I don't think I do. Yeah, we're just gonna tell a story now Thanks, I appreciate all the support so much everyone's been so nice so Part of the reason that I wanted to do a personal blog on Kubernetes for my first episode was because like I said in the promo if you saw that I Tried to do this like five years ago It's a very different experience. I'll tell you that much And I want to kind of I could explain why I'm gonna approach it the way that I'm gonna approach it today But I think it's better to tell a story So let me tell you about why I tried to run a personal blog on Kubernetes like five years ago So it's end of 2015 early 2016. I Had just been laid off from my first job in the tech industry rough times but It was okay, and there were a variety of circumstances that led to it and it wasn't unexpected and I was in an okay place But I had I was now in the position where I needed to be looking for a job And I had gained some really cool skills around using containers in my last job And now I had some free time And Something I'd always wanted to do was to have a blog Especially one where I could post artwork, which if you've ever seen my website caslin.rox I tried to post fun artwork and and technical stuff there so I wanted to make that a reality and make it happen and I'm a computer person Like I work in the tech industry and everybody's talking about how easy it is to build a personal website all the time I feel like I was like I can do that, right? Further backstory When I was in college, I actually skipped all of the web design courses through a variety of circumstances So I've never done any web development at all. I don't know the first thing about running a website and I'm Between jobs and I'm trying to run a personal website. I know a little bit about containers So I'm like, okay, I'm gonna run a personal website on containers. So I wanted to set that stage for you From that starting point. We're gonna explore Running a personal website on Kubernetes today So the first thing that I need to figure out as someone who knows a little bit about containers and absolutely nothing about web development Is what does it take to run a personal blog? So I've got a I've got a Google doc up here But I thought we'd use to track our progress in trying to achieve this goal today So our first question that we need to answer is what does it take to run a personal blog? Caslin of five and a half years ago had no idea. So let's just Google running a personal blog site And I think the the results today are going to be at least similar enough to what I want To what I saw five years ago. Yeah, so we've got this recommendation here from Google that says The technical setup when starting a personal WordPress blog. So at this point in my life I had heard of WordPress. I think but I didn't know anything about it But I've heard of it before and it's mentioning it here. So WordPress seems like a solid choice There's also all these things like Wix and the square space and stuff that you always see all of the ads for on YouTube at least I do and So you could do something like that Let's look at one of those maybe well What I know about those is that they make it really really easy to run a website and at this point I'm thinking But I want to learn about using containers. I don't want to just take something that's given to me I want to do it the hard way for learning purposes Because I I have good ideas like that So let's just look up WordPress WordPress So couldn't I find this thing WordPress.com that seems like a good place to start Says that 41% of the web is built on WordPress Cool that seems like a very reasonable thing for us to try to build on a website with then I don't know anything about it, but it seems like a good place to start and they have to start your website button Which I wonder what it'll do if I click on it. You'll have to like log in and stuff But what I've learned since at least is that on WordPress.com you can make your own personal website And please folks in the chat. I would love to hear from you about your experiences with personal blogs Are you all running personal blogs? Have you all tried to run it in kubernetes before? Did you do something like this? Please tell me about your experiences because mine are pretty limited and we would all love to hear from you So what I've learned about WordPress.com is that you can Uh spin up a website really easily here. It's like a lot of the other sites Where it gives you really nice tools for spinning up a website really easily You can figure out your domain name and and all of that Just kind of within wordpress.com Like I said, I'm doing this up the hard way So instead I go and buy a domain name, which I didn't know anything about before this Um domain registrars Give you a sense of what I'm looking at I've heard of things like go daddy and and domain name registrars before Um, so I did a bit of research and looked around at a few different domain name registrars and I bought a domain name Planning to make a personal website out of it Um, so that was an important first step And now we know that we want to try and use wordpress for our personal blog So like I said, I've got a little bit of experience with containers I want to see if I can run wordpress in a container. That seems like a good place to start. So wordpress Docker I've been doing a lot of docker work at this point. Um, so I was pretty familiar with docker then Less so now I'd say but uh, if I go here We've got a wordpress image on docker hub. So that seems like I'll probably be able to run a docker container with wordpress in it That's a pretty good start Um, let's see how we can actually do that So there's this how to use this image section, which you will probably can't see at all. Let me Zoom way in and close this and Make this a bit bigger I'll make this even bigger Maybe not that big So we're on docker hub and we've got this wordpress image and we're trying to learn how to use it. Um, Now that I've done that I'm gonna open up a terminal who Hi, hopefully you all can see that well Yeah, anyone running any personal blogs? Please share. Love to hear from you all um so I'm gonna try to run this thing in docker So if I run docker on my machine, I can see that I've got docker installed, which is good Oh, you're running one, but it's not on kubernetes. Can you tell us a little bit about? Uh, what process you went through? I would love to hear because I have an idea how other people approach this problem Um, so we know that we've got docker installed here. Uh, that's a good first step Maybe make this just Yeah, so I can get back to this easily This slightly over two, uh-huh so I'm gonna try to run this docker command because that's what Caslin currently and Caslin of five years ago would try to do upon looking up something that I wanted to run in containers I would just try to run the first thing that I So if I try to run this Uh, it won't find the wordpress image. So that's good. It's pulling the wordpress image This is looking pretty good we're, uh So I found An a container image to run wordpress and now it's downloading that image So in theory, I should be able to run this and actually run wordpress Let's see And it gives me an error Because it says network some network not found So at the time when I was trying this I was pretty familiar with docker and probably had set up a few docker networks Oh, you use jekyll cool. Thank you so much for sharing your experience Allows you to launch a preconfigured blog website created using ruby Yeah, I hear a lot of good things about jekyll Maybe I should try that someday But so we we did docker run and Gave it a name of some wordpress and this network piece is the problem Because I don't have any docker networks set up at the time I knew what docker networks were Current present caslin does not so I don't think I want to run it that way Let's see what else we have in the information um So the following environment variables are also honored for configuring your wordpress instance We've got some stuff about wordpress db host So it looks like we're going to need a database To do this which is interesting a lot of people I've I've gotten the question pretty often of can you even run Databases in kubernetes. So this is going to give us a chance to check that out um It seems like which it is spoilers it is So I know I'm going to need a database of some sort I've got a bunch of environment variables here that I know nothing about because I know nothing about wordpress That I'm going to have to figure out how to run I've also got another Docker run command. Let's actually do a little bit more thinking about this one this time Since the last one failed um If you'd like to be able to access the instance from the host without the container's ip Standard port mappings can be used. So this one is saying I'm going to run a wordpress container And I'm going to run it on a specific port on the machine that I'm running it on. So that sounds pretty good That sounds like something that we can do. Uh, so let's try that I'm going to come back over here and I'm going to do docker run some wordpress is fine and Do that Oh no, I must have tried this earlier procker ps Um, docker ps dot cache a Oh because I just ran that other command and it failed um, it actually created a container, but it Didn't work out So if I run docker ps, I don't see any running containers But if I run docker ps dash a which shows me all Running and stopped and not in a good state containers I can see that I've actually got the wordpress container that I tried to spin up Still and it's using the same name. So it's not letting me create the container So I'm going to run docker rm And uh fun tip If you're working with docker you can just use any unique string from the container id to refer to the container So if I run this I should be able to get rid of that container Cool. So now my wordpress container that I created in error is gone And now I should be able to run this new wordpress container that's using port 8080 and at some point today, I'm going to mess this up It's very important when running docker commands to use dash g least in my experience Um, because dash g runs the container in detached mode. And if you don't do that the running container will take over your uh It will take over your command prompt. So I've Caused myself some problems before by doing that Docker ps dash a We can see that it's running if I run docker ps. I should also just see it. Yep So this container looks like it's running happily So it's running on my local host on port 8080 8080 is the local host port and 80 is the port in the container that is being mapped to I believe I always get that mixed up But we do local hosts 8080 Oh, look, we've got wordpress running boom. There you go. We're running wordpress in a container halfway there, right So Oh, but it says that we need a database. So we really do need that database thing that we saw in the docker hub stuff So Let's see here So our first question to answer was what does it take to run a personal blog? I want to come back to this for a second and say we needed a domain name. We talked about that and We needed to decide what to use to run the blog which we're going to use wordpress Um And so now Can I run wordpress in a container was my next question? And we have determined yes But I need a database So now I need to figure out how to run a database container that this wordpress instance needs and a nice thing in this docker hub entry Is that it has this yaml file that defines What you could use for docker compose to tell docker spin up multiple containers for me So that sounds pretty good Let's just try this But let's see what we have in it first. So there's two services. The first one is called wordpress. That's what we want to run That makes sense It's got port 8080 So I'm going to want to delete that container that I already have running if I'm going to run this because otherwise it's going to have a port conflict It's a good thing to just back at it first Your blog is called daemon sets nice It's a good blog name Um And then there's all these environment variables that must be wordpress stuff Looks like it's telling wordpress how to connect to the database information about the database db host db user db password and db name That's got a volume So When I tried this like five years ago Uh The instruction page here was a little bit different. I don't think it had the instructions to create this volume um But since at the point where I realized that I needed to create a database container um I knew about docker volumes So docker volumes are docker's tool kind of for Using persistent storage with containers. So if you have a container that's going to run some application that needs a volume uh Needs to have persistent storage that could persist if Say the container were to go down you would still want to keep that data Um, then you're going to want to have a volume. So that makes total sense for a database. We probably want our data to persist Uh, so we're going to create a volume and in dockerland Uh, you can specify the name of a volume and then where it's going to be loaded into the container So in slash of r slash lib slash my sequel which I assume is An area where it's important for my sequel databases to have persistent storage Um, we'll set up a volume that will persist even if our container ever dies So that's good. And then we're setting up one for wordpress as well um Kind of tempted to show you all what happens if you don't do that on the wordpress side because it's pretty interesting But we're already pretty kind of behind schedule and I want to get to running this on kubernetes without Taking up too much time. So I think I'll just try running this compose So I'm going to docker rm-f 83 So that get rid of that wordpress container I was running earlier So docker ps Now I don't have that running if I check ps-a you can also stop a docker container and then you'd see it in ps-a Because it hasn't been removed. It's just stopped But it still exists So I removed that one. It's not here anymore. Let's try creating a file I'm going to call it Wordpress Docker got yaml that sounds reasonable And I'm going to input all of the stuff that I saw on the The docker hub page so Again, this gives me all of the information I need to create another wordpress container with environment variables that are apparently important for wordpress and To create a database container with also some important Things set up in it and then volumes for each of those so that Storage will persist across restarts and things like that So Then if I run docker it actually has this on the docker hub page as well Yeah, so we're going to want to run docker compose dash f Give it the name of the file and then up And this actually has been changed so that you can do it With a space instead of has its own command so docker compose dash f wordpress docker.yaml and then we're going to up that Okay, so now we see that docker is building our containers that we defined in the yaml Have you all done this kind of stuff before? How long has it been since you all worked with docker? I'm curious It's been a while since I worked with docker. I did a little bit of exploration before this uh to make sure that I would Not spend the whole time just looking at docker commands Because it's been so long since I used it Oh, no, you know what I didn't do. I didn't use dash d So look what's happened. It's taken over my terminal I hate it when I do that. This is bringing back great memories. I'm glad Uh What is going to happen if I control see this because I kind of want my terminal back Um, maybe we should go to 8080 first and see if it's up and see if this worked and then I'll worry about getting my terminal back So this is from before let's try localhost 8080 again. Let's reload this Okay, so we've got wordpress page again. That's good Oh, and this is different. You see so last time it said that I needed to connect to a database But this time it seems to be saying that I I I imagine that I have the database already So my compose should have worked I've got a wordpress container running and I've got a mysql database container running and they can talk to each other awesome So now you can give your site a title and set up a username and set up an email and all of that Now I was hoping to go ahead into wordpress and set something up and then kill some containers for you to show you what happens Um, but what do you all think we're getting kind of short on time? I think I might move on to running it in kubernetes That sounds good I remember the first time I ran docker compose up. It was magic. I agree with that lucky How long has it been since you worked with docker? I think pop is asking everyone in the chat for me But for me, it's been like five years Yeah, run it in kubernetes. Okay, so that's what we'll do next instead of Messing around with killing containers and seeing what happens with the persistent volumes and things we can always explore that another time So i'm just going to control see this. We don't need these containers running anymore Anyway, it says that they're stopped. So if I run docker ps, I won't see anything if I run docker ps-a Then I see that they're still here, but they're exited Which is fine. I'm just going to leave them like that Now what I want to do next is figure out how to run this in kubernetes Luckily a few years ago. I noticed that in the kubernetes documentation There is actually a really nice guide for how to run wordpress in kubernetes Cool So here we've got an example in the kubernetes documentation For deploying wordpress and mysql with persistent volumes This is exactly what we need We just saw the How to do this with docker. So now we're going to try to do it with kubernetes And lucky says I use kind a lot. It's running in docker under the hood. So you could say I use it regularly That is a fair point I've heard great things about kind. I hear it's it's really good I'm currently using docker desktop by the way for all the docker stuff. I was just doing Really nice tutorials for that too if you want to practice your docker commands like I did So this should be pretty much the same thing that we saw in docker, but now it's in kubernetes So create persistent volume claims and persistent volumes This is going to be the kubernetes equivalent of docker volumes that we just talked about a little bit ago So Interesting it wants us to create a secret By the way, I didn't practice this part of actually running it on kubernetes So if you have to go no worries, but I'm going to try to do this relatively quickly and kind of point out some of the important things about kubernetes as we go So they're wanting to spin up a secret which is a kubernetes object that stores a piece of sensitive data Which you all can't see at all probably Like a password or a key Since 1.14 kubectl supports the management of kubernetes objects using a customization file So you can create a secret By generators in customization.yaml add a secret generator in customization.yaml from the following command You will need to replace your password with the password you want to use Okay, so this is We're going to try to use a kubernetes secret which is first secret data To set up a password for our mysql instance that we're going to run in kubernetes That's a good thing to know And let's look at some of the other stuff we're going to try and do here too before we move on Add resource configs for mysql and wordpress the following manifest describes a single instance mysql deployment Okay, the mysql container mounts the persistent volume at slash fire slash lib slash mysql So the same place we were mounting it in docker and we saw that that Well, we didn't try deleting the the container and stuff but I tried it earlier and I will tell you that's the right location It would persist across restarts if we tried that The mysql root password environment variable sets the database password from the secret Okay, so we need our secret in order to set our database password which will be set up in This So this file is a bit longer Than the one that we saw in docker someone said I get hung up with the network stuff in all this tech me too Like I said earlier the command uh that made use Of docker network or forward press haven't used that in so long Speaking of which Not even using my nice mic, so I'm so sorry about my audio quality Which hopefully just improved significantly Um Kind plus b equals heart. Yeah kind is great. There are great things about that So this is a lot longer than what we saw in Docker, but let's see what we're trying to make here. So kind service some other one The docker compose example, which apparently I don't have up anymore We had two services wordpress and mysql um That was used a little bit differently than it's being used here here. It's a kubernetes yaml manifest So we're talking about the kubernetes object of a service So Thankfully, I know this now because I've been working with kubernetes for a while, but I'll tell you me if five years ago did not Um, so we're going to name our service wordpress dash mysql and we're going to give it a label app wordpress and then so we're specifying a port that our service is going to run on and A selector app wordpress and tier mysql So these selectors are how our service is going to understand What actual containers it is serving so service in kubernetes is one of the first things that you'll spin up if you ever do Like a beginner's kubernetes guide. I think most of the people watching have done that before I just noticed that I still have a Menu up. Okay, so It's one of the first things that you'll do in any beginner tutorial in kubernetes is you'll spin up A deployment or some kind of pod or you'll run containers in kubernetes. Basically. It's what we're going to talk about when we get to deployment um, and then you use the service to actually access that deployment I still love and use docker almost every day Use the same approach that you've demoed docker compose for quick poc and then followed by kubernetes Yeah, awesome. I love to see that that's a pattern that other people use I find it really helpful to understand what i'm actually doing With the containers and how i'm actually running the application before I start bringing kubernetes objects So the nice thing about a kubernetes service is that it can be the It can kind of act as a load balancer across a bunch of different replicas of a container If you want to run something high availability So that's really nice I don't know that I need a whole bunch of copies of my wordpress for just running a personal wordpress blog But it's good to know that kubernetes can do that And then we say cluster ip none It doesn't actually specify the type of Service explicitly it's been a while since I've made a service manifest. So I find that interesting I guess this is technically a node One I don't know. I need to look things up So anyway, we're going to move on to persistent volume claims and then The following manifest describes a single instance. I'm looking to see if there's a Okay So this is just a slightly different one um So this is a persistent volume claim And it's being called mysql pv claim wordpress It's getting the label app wordpress And then it's going to be a read write once volume and 20 gibby bytes Cool, so this is a local persistent volume claim I assume Do we need to Does it say something about setting up an actual persistent volume first? So mysql wordpress each require a persistent volume to store their data We saw that in docker their persistent volume claims will be created at the deployment step Oh, okay. So maybe it's in our actual deployment Yeah, there you go volume mounts and volumes. So that's where we're actually defining our persistent volumes So in kubernetes, it's not just volume like it wasn't docker You've got a persistent volume and then you've got to claim that persistent volume with a persistent volume claim Which honestly, I haven't worked with in a while But I'm going to read a question Here's my silly question. Let's say you didn't have a great guide like this How do you know what keys you will need on the left hand side? Do those match up with something the keys? I mean are like oh spec metadata spec, etc I'm not sure how I would have gone about knowing how to use Or knowing that I need them. I have had that same question. I will tell you If you ever do the the ckad certified kubernetes application developer exam You will have to practice that a lot You'll kind of get a sense for all of the important things that you'll need in every single yaml manifest for kubernetes API version is always going to be there kind is always going to be there because it's telling you What kind of kubernetes object you're going to create? This first metadata one is pretty much there for every Object because you're going to need to name the object that you're creating and have the opportunity to give it labels Even kubernetes node objects, for example, have labels. So that's a pretty common thing And I think there's pretty much always the spec section But what goes in it beyond that varies depending on what kind of kubernetes object you're building So you have to get a sense for What kubernetes objects are and what kinds of Yammel components Are are applicable to those kubernetes objects, which I would check out the documentation for would be my recommendation Yeah Daman, I'm sorry if I'm pronouncing your name wrong very sorry Is saying well for the most part there is a specific pattern to the spec you specify the api version object kind metadata data and the spec But you can always use kubectl dry run to generate Yeah, kubectl dry run is a really nice tip that you'll see if you ever practice for the certified kubernetes administrator or certified kubernetes application developer check out certs magic with scion later It's a big tip for those is to learn how to use kubectl dry run to generate kind of a base Yammel file for doing this stuff Cool And then yeah, okay making sure that there aren't any other questions Good good. So we've got a persistent volume claim here. We've got a service definition here and we have Deployment definition here, which is pretty big Deployments can do a lot of stuff Um, so deployment is how we're going to run our actual containers that we care about Uh Interesting. So we have both the wordpress and the mysql defined in the same deployment definition Uh wordpress dash mysql is the name of this deployment This makes sense So we're giving it a label app wordpress and selector match labels app wordpress tier mysql Not sure what that's selecting for people know Please let me know. I'd love to explore that more um strategy type recreate. So this is um Something specific to deployments uh It i'm guessing it describes what will happen if something happens to the containers something like that I would have to actually look it up Spin up a kind of mini cube and go through the cave stocks. They are super useful to get started and understand Aspects of the yaml very useful cheat sheet very nice um And then got some more labels here app wordpress tier mysql So these selector labels are being used to Uh specify which pods in kubernetes The deployment kind of owns We don't have a pod spec in here. We're not specifically saying we're making pods Instead we have this container section within the deployment and the deployment just kind of knows Oh, you want to run containers? I'm going to put those into a kubernetes pod object for you Look at this. We're learning so many kubernetes objects today And then we're specifying the container image that we want to use which is mysql 5.6 Uh and giving it a name environment variable We saw this one before mysql root password and then we're going to make that from a secret like we talked about earlier And uh container port name mysql Volume mounts mysql persistent storage mount path bar live mysql Uh and all of that I don't see a container definition with the intimate an image for the the wordpress App did I miss it somewhere? Uh single instance mysql deployment that'd be why Because it's got this separate one just for the my just for the wordpress Um, so this is quite a bit more text than we saw in the docker one and we have Honestly quite a bit more stuff for running things at high availability Deployments have a lot of tools for running things at high availability Um, I assume that's part of what this strategy one is about. I've got to go look that up again uh and then A common thing that people talk about with deployments is doing rolling upgrades Deployments have really cool smarts built into kubernetes for that Uh, so deployments are meant for being able to run things In a highly available fashion As are the persistent volume claim as is the service. So we've got a lot of uh Nice high availability tools in here and then uh In the other one, we've got a service of persistent volume claim and a deployment So we've gone over kind of what all of that looks like great. So I want to try to just run this If that's okay and Pop let me know if you need to go because pop is helping me run this stream since I was having so many technical difficulties Everyone big thanks to pop I don't think that the yaml example has the persistent volume included Uh, it's expected Uh, it's expecting to be created before it's executed I thought that at first two something like this would work if you add it to the top of the example Yeah, so you can specify a persistent volume separately I've seen that done pretty commonly in specifying a storage class As well as uh, the capacity of the storage So for and you don't think that this will work if we run it as is uh Yeah, because it's Volume persistent volume claim. You're right that it doesn't seem to be Specifying volume mount name Specifying a mount path It's been a while since I've spun up a persistent volume as you can tell Uh, but I'm gonna go ahead and download these at least Nice. We just need to add that bit. Does anyone know how to Format the the text in this chat. I think that's okay. I can format it myself The the chat might not let you but I can do it um Cool Apply and verify Get secrets Verify that a persist. Oh see though verify that a persistent volume got dynamically provisioned So this example is expecting that a persistent volume will be dynamically provisioned for us I think I should try it and see if it happens So let's try this. Uh, I'm gonna go ahead and curl this It's kind of nice that in the kubernetes documentation the examples. I have these curl commands Let me Let me control see that for a second not run this just yet There we go and control l there you go much cleaner much prettier easier to see what we're doing So I'm gonna curl down the mysql deployment.yaml that we looked through And then I'm going to curl down the wordpress that we looked through. Thank you everyone for being engaged by the way As we're going through this and I'm asking questions. I really appreciate it Okay, so now we've downloaded I created an episode one folder and then I just put everything in the top level folder. I'll move all of this stuff later so Uh, we've got our wordpress deployment.yaml not the wordpress docker. That's a separate thing and then mysql deployment.yaml So we have those files And add them to customization files. So here we're using cat to create another file, which will be called customization.yaml And it just says resources And it specifies those two yaml files But these instructions don't even include that secret that we saw at the beginning So I'm going to go ahead and run this one first. I feel like that should be in the bottom Instructions And then I'm going to run the other cat command that we have down here, which Sets up a customization.yaml that specifies the resources So the customization.yaml file contains all sources for deploying a wordpress site and a mysql database You can update the directory by running kubectl apply dash k and dash Let's see if that works 8080 was refused This might be because I'm running on my work computer I would believe that Oh, actually do I even have Yeah, so I don't have a kubectl setup. I think Isn't my or a like a local mini cube cluster setup or anything? That's kind of important So let's do this. I'm going to open what we just talked about in visual studio code This is an easy tool for me to use to get a mini cube setup So there's a cloud code plugin, which is a thing that google makes So that's how I know about it because I work at google, but it's just a thing you can use Um, and it can help you manage your kube config. I've got like this old Cluster in here that doesn't even exist anymore. So I don't care about that But I do want to start a mini cube cluster. So I went to cloud code in visual studio code um, and then I hit the plus button in the kubernetes, uh thing And then I'm going to say start a mini cube cluster Mini cube cluster is currently stopped. Let's start it Oh Look down here. We can see that it's spending up a mini cube cluster You probably can't see it very well because it's super tiny Um, but we are starting up a mini cube cluster, which we'll run this on. That should be good That might take a second and I'm actually trying to write a spring up cluster on this machine So We will find out and while it's doing that Like in the fast lane. Yep This we'll need any more That we had earlier here. So this is kind of nice to be able to actually look at our files I don't know how long this will take. So We'll just wait around here for a couple more minutes. If it's not done. Maybe we'll Do something else. I consider trying this bit of a cluster in the cloud before I got started today But thought oh mini cube will be fine. It'll be quick But once that's up, we'll run the cube CTL apply Command basically Which might be a little bit. Oh, would you look at that? Starting to look a lot like mini cube Oh, is that docker? Oh, okay. That's docker Because I opened that up Interesting I haven't actually looked at the docker plugin in visual studio code, but you can see like all of the containers that I'm running Hey, it's mini cube. I just saw a new one come up in docker. Does that mean? Oh creating docker container That's pretty cool. So we can see in the docker extension of A visual studio code The cloud code extension creating my mini cube cluster That's pretty cool But it's still not up yet. I got excited there for a second But oh well, uh, so once we do that apply Verify that the secret exists. So it's a good thing that we ran that cat command from earlier Uh, we want to make sure that that secret exists Looks like it's using customization.yaml. So I wonder what my customization.yaml file looks like right now actually It's getting toward 230. So If this keeps going with the mini cube, we'll probably stop here for the day and then Try to finish up running our our Kubernetes cluster Next time when hopefully I'll have all of my technical woes figured out as well But our customization.yaml does have both the secret generator and the resources stuff that we added earlier So that's good Hopefully when we run our customization, it'll run the secret generator and create our secret as well as Running our deployment.yaml. So that will run everything It's kind of like docker compose. Good finished. Yay. So we'll see if I can do this quickly Um, cool. So now I've got a mini cube cluster up and running and I wonder if I can zoom in on this at all Oh, I can. Yay. Wonderful I'm going to close this So I'm not running a GKE cluster right now. I'm just running a local one Which hopefully isn't sending my computer into a tailspin so You can see all of the deployments that we have running all zero of them For pods all of our services. These are all of the Kubernetes objects that we might be running which we are running none of currently In our default namespace Which sounds like a fine place to run stuff to me Cool So let's see how we run this So I don't really remember um Cloud code run on kubernetes Looks like I've got some problems with my visual studio code setup. So I might not be able to run this here But Let me see here If I Might go back to what I'm more familiar with. Let me remove Context under cluster Do you want to delete this old cluster that I don't actually even have anymore from your kube config? Yes, I sure do So now my kube config should just have my mini kube in it. So if I do go back to my terminal Let me control l so that it's clean kubecpl Just run that see if it oh Well, I've got the command. I don't need that didn't I? Uh get nodes Look yay, I'm in my mini cube cluster. So now I should be able to run this from the command line, which I'm more familiar with So let's do that Okay, not pay as well as I always like to check where I am Okay, so now I should be able to run that kubecpl apply command that we were looking at earlier Which is right here So let's try that Quickly and then we'll try to finish this up. Okay. It created a secret it created So the thing on the left of the slash here is going to be the kubernetes object Uh, and then on the right is the name of that object So we've got a kubernetes secret. We've got kubernetes services we've got deployments and persistent volume claims But I don't see a persistent volume created So maybe you're right. Maybe we do need to add that to this This uh tutorial. Maybe that's something that we need to submit as a book. I don't know. Let's find out Um Verify that the persistent volume got dynamically provisioned. It says to run kubectl get pvc Which does specify the volume if we run that so let's see what we get if we run Well, it specifies a volume With a capacity But is this just the volume claim itself? Can we run kubectl get pv? If we run kubectl get pv It's kind of hard to see But there's a name There's a capacity access mode Reclaim policy Its status is bound So it looks like it did actually auto generate persistent volumes. So Mini cube via code is three star I agree mini cube via cloud code is really nice So it it does look like it actually created a persistent volume dynamically, which is great to know Yeah, this is that's what I just ran Is kubectl get pv right here. Hopefully you can see that. Yeah, isn't that cool? So in theory this should work and I think the wordpress in my sequel should already be up and running So if I run kubectl get services wordpress Let me clear again. I don't like it when my screen is full of all that big text Um, oh, but it has it as tight load balancer. Okay I was wondering because I didn't see the type specified in the oh, but that was because it was the my sequel I didn't actually look at it in the wordpress one in the wordpress service It does say type load balancer So that's not going to work out. So well in mini cube is it Load balancer is really nice when you're working in a cloud provider. Uh, because generally the cloud providers have uh, really convenient Default on uh plugins. Uh, if you run like in their managed services, I guess is the better way to describe that. Um Where it'll spin up a load balancer in the cloud for you So running load balancer in the cloud is so easy but Okay, so The response should be like this wordpress load balancer should be pending I don't expect it to ever have an external ip because we don't have an actual load balancer in front of this load balancer Uh, but it does have a cluster ip and it is up on a node port. It looks like Fun fact load balancer type services actually require like they use node ports to do what they do So that makes total sense that it would have a port even though it's not type node port I'm saying a lot of words that people might not understand here, but Uh, there are several different types of services a cluster ip service means this app can talk to other things within the cluster A load balancer type service means that uh, there's a load balancer of some type That you'll use to get access to whatever containers you're actually running on kubernetes. So that's what we've got here Um, and then there's a a node port type service in kubernetes, which will Spin up an actual port on the node that the container is running on that you can access the container from And load balancer uses that so we should be able to access this on a port Minicube can only expose services through node port The external ip is always pending That's exactly what I was expecting Uh, run the following command to get the ip address for the word press service Let's see. I don't know if the minicube command is installed So that doesn't seem like it'll work very well Um, so I don't know what my local Uh, ip address for my minicube is I wonder how we can find that without me having the minicube command line tool Huh? Downsides of using cloud code to generate a minicube cluster, I guess um But then once we do that, I expect that we'll be able to see this if I curl Can't curl it because I don't know what the ip address is Um Service wordpress url How do I find out what the ip address of my minicube services any suggestions for what I should look up here Our most welcome. It's also almost 230. So I'm going to try to get off of here soon Um, I at least want to try I know that it's running in kubernetes It's We are running a personal blog in kubernetes, but we're not running it online We're not running it in the cloud. We're just running it locally and I don't know how to access it right now Yeah, the pods are up. So we know that it's there Um, but I'll have to figure out how to actually access my minicube since I don't actually have the tool installed a little bit later So I don't want to keep people for too long. Yeah Next week we'll do part two and and finish this up So thank you all for joining me today I had a lot of technical difficulties and I appreciate it so much for those of you who've been with me I hope that you learned something interesting Uh, and I hope that next time will be a lot smoother But thank you so much


Ya, nili wambia jileo, today it's all about the boy child. Na, as they give us amazing performances, very talented, but don't know Lisa Swally. Is it okay?  And that was a real seko. He is here, he'll be telling us about himself, tumjwe, and what he has brought us today. Seko. Hello. Mambo VP. Poa sana. Poa sana? Ya. Kayu biko nyesho? Asana to sana. Seko ni nani, real seko ni nani? Oh, real seko ni hati, singer, songwriter, actor, is of it was hwade. Zina ususani. Ya, me dea. Mufanyam ziki fuhalong? Mua, from 2019. Ya, adisha hi. Atu na indelia. Nya muna indelia. Batu me grow up kwa background, ya music. Asu zi sama ni me grow up kwa background ya music, ni mimi, meji growish. Ni wewendo meji growish akwa? Mika kuna mtu eni akwa roundu me, te na sama. Muna fanya music kwa atu ama. Ni solo. Solo movement. Ya, ya. How has that been for you? Mepata challenges ganiukifanya? Mika kwa wana pata family, wana juwa, ama wana feel, education is the best. Iusani ya akwa shuwa nani. Wana kupush kilasa. Mambo ni masomu. Amba ya nasoma pia. Io yu me gowa nama one challenge. Nama two challenge ni few people take time to believe in you. Ima most of the people. Take time, wale wanyu nana za kusapot. So napata most of the project, wew na fandu mimi wew menewe. Nya. Io ni challenge kama boy child. Nya. So top of top Pesaya studio, video, iso ni challenges for me. Speaking of Pesas, speaking of boy child. Wewe kama mwana ume, unhe zomba mtsuchana Pesas. Nya. Nmtsuchana mga ni stand. Manziako, mrafikiako, close. Mamaako. Mamaako. Tuli se mamaako, sistaako. Sistaako. Mabeshtiwa kama Dave. Ono jo kwa mba ni eternal. Mi na believe. Akuna mtaizi kwa mba. Ata boy child na kwa mba. Kwa mba mamaako Pesas isa lau. Kwa mba galfrenda kwa Pesas isa lau. Nya pia na kwa mba. Laki ni wawa ata kikupea kiki dogo wana. Nya. Amesia mani wana. That is what I was waiting for anyway. I arrest na kies. Azima kila mtu taji wa yu. Mki kusana kiki dogo. I arrest na kies. Nya. Nya. Nya. Kusana. Mi ya. But kwa mba atuengi. I am guilty kiku dogo but it is allowed. To ask for money. Siniwa. Laki ni nga wei kama mstiana. Bimatua enough. Bimatua enough na to tell ati kila mtu. O si junanya na ni mga Pesas ucha. Nini nini nini na ni na. Bimatua. Kama ono jo uta endok. Sistaako ni saa. Sistaako ni saa. Sistaako ni saa. Mabesti. Anyway. Seko. Umefanya a few projects. Kuna mapenzi. Kuna letter tumbler. Kuna take it slow. A range of topics ni una kava kwa. Nga mazako. Batsara sana ni mauna mapenzi. This boy is just in love. The boy is just in love. Nga you same page. I'm saying we both want two of his songs. The boy is just in love. Ni kwin. Actually all my songs yon do tagiako. Ata letter tumbler. The boy is just in love with the music. Sasa apande wuna potea. Nasa siu clarify utwa mi ni music. To sketch kijua. Umefanya sana. Anyway. You're in love with music. Nga blen me say ma you've done a range of klabangazi klabangazi klabangazi klabangazi mapenzi and everything.  For me, okay. Most of the klabangazi ni mefanya. Amin si mingi. Klabangazi ni na fanya tu kiasi kiasi. But my main genre is singing love songs. Zeniata nga mingi zeni ni me record. Zeniasi jali release. In love songs. So the boys just in love. Umependa ya ni. Nupenda muziki. Nupenda wana wake. Nupenda wana wake. That's why I appreciate them. In the songs that you've done, ni mojando mefanya kolabo. Not really a kolabo, but you've done the song together. My brother critical king. Take it slow. Why make that decision when you've been doing singles before? Kufanya take it slow na critical king. Ni vibe. Sani ni wengi na if you vibe with somebody na zafanya tu mga mapo. Ni me wakna watu wengi. Goma dia zi kua release. But ni me wakna some other artists. Ntapata mga maza Very soon. Ntaski zatweza mga ma very soon. Kama artist kama rilseko. So zi nga na bwaika kufanya vitu pekiangu. Kufanya kufanya kolabo na mutumengina. Nia. Upatia ato new ideas ulan. Ni ni wneza sema inakufanya u standout kama rilseko? Being me. Because ni na believe mi uzi kiyangu. Atakama ni klabanga. Kuna tu wnezi na sound kama mi. As a sound. Nitu wengina. Unless watu nia mbe kwa comment section. Yes mambi eni. Ntapata mga maza kwa YouTube on all audio streaming platforms nisha boom play Spotify, Deeza Instagram kila maali ni rilseko. Ni naboga na jina mawa jatweza. Ni nambili ni rilseko. Ni rilseko. So I'm rilseko. So mese mawazipata YouTube and all streaming platforms. So after take it slow what next? Are you planning to release one of the songs that you want to release and it's another single? Actually kuna nga mazingine kuna nga mazingine tumifanya na clinical king na zingine pia tumifanya na wasani wengine. Musti nga mazingine zidatoka in the next recent days ni mako labo but I'm working on a good thing for you guys na niki tupuwasana ni mga mamingi tazita kuja pamaoja I hope it depends It depends on you It depends on you So any shout outs to Kimalizia? Hey, what do you want me to say? Shout outs to Sanana Kahawa Pali Mbu Talent Academy I'm a group I'm an artist who performed by the Sanana Kahawa shout out I grew up in Sana Shout out to Ilam Entertainment Shout out to Critical King Meshwalen Kade Ramzing Ambiulans Pali Nyubani to my mam, my dad and my family and all those who love Reel Circle Thank you So thank you so much for coming through for taking your time to join us Pleasure is all mine All the best in your music career and hope to see you more Thank you So up next is Take it slow by Critical King Thank you


We need to reach more people because we're not reaching enough people now, and those agencies that are putting out messages about a war against drugs are effective in getting their messages out. So the more people that we can reach through these types of videos, the better.


Welcome to JSA TV and JSA podcast, the newsroom for telecom and data center professionals. I'm Lauren Oland coming to you from ITW 2021. Joining me today is Chris Lodge, Chief Operating Officer and Interim CEO at United Fiber and Data at Chris. Welcome back to JSA TV. Great to be here, thank you. Well, we have a lot of news coming out of UFD and we'll get to all of that in just a moment. But first, if you could, tell our viewers about UFD and your role. United Fiber and Data started with a simple concept and that was to bypass the I-95 Route 1 corridor in the mid-Atlantic northeast part of the United States. And we have successfully built a wholly owned and engineered backbone between the major markets of New York City, Northern New Jersey and the data center capital of Ashburn, Virginia. Well, this is the time for ITW. UFD is making a huge splash with a pair of international deals. Can you give us a sneak peek about some of these partnerships and how UFD is helping these global companies enhance their connectivity in the US? Yeah, this year has been a great ramp for United Fiber and Data. We, as you mentioned, the announcements will come out shortly, but just in the past month and a half alone, we've signed three international companies, one a global hosting and data center customer, another international telecom customer, and then on our new optical wavelength services, we announced one of the premier global telecom companies, a major European provider on our lit services. All right, so lots of news, three deals, not two. So we've got three deals to look out for around ITW. You guys are staying busy, but what's next for UFD? Right now, we're looking at what we're called densifying our current backbone and looking at some alternatives there that hopefully we'll be able to announce here later in the year of, you know, I'll call it Spurs, but might not be the right term to use off of the current backbone that'll strengthen the network and also continue to provide our customers with the service that they've grown to. One of the other things I would like to say is I mean, besides those new deals, this year has been great. We've signed and turned up successfully multiple expansion services with our existing customer base, which are also some of the global data center and telecom providers. United Fiber and Data keeps going and growing. Chris, where can our viewers go to learn more? UFD.com, United Fiber and Data. So our acronym, UFD.com or our Facebook website, link you over to any one of them on the sales team or the marketing group and we'll get back to you. All right, you heard it here, go check them out and watch out for those headlines from United Fiber and Data. Thank you so much, Chris, for your time. We always enjoy talking with you. Thank you, Laura. And thank you viewers for tuning in to JSA TV and JSA Podcast. Happy networking.


I'm starting with this photograph of Wright arriving at the San Francisco airport in 1957, which I found in the San Francisco Chronicles photo archive, because I love the fact that he looks so vigorous and energetic, only about a month before his 90th birthday. Also, I'd like to imagine that his evident good spirits here were due to his pleasure in coming back once more to this city that he genuinely enjoyed being in, as we know from his correspondence and interviews. Well, first let me mention how I got involved in this subject of Frank Lloyd Wright's work in the San Francisco area. During the years that I taught the history of architecture at Stanford, one of the courses I gave was a seminar on Wright, and we would take field trips to his buildings in the Bay Area, such as his wonderful shop on Maiden Lane here in the city, just off Union Square, originally the VC Morris Shop, and I'll say more about this building later. And this got me interested, especially in Wright's projects designed for the Bay Area, both the built and the unbuilt projects, and I started doing research on the topic. More recently, when I would tell people that I was writing a book on Wright's Bay Area works, a common response was, well, what is there? There's the Marin County Civic Center, people would point out, and San Rafael and that shop on Maiden Lane that we just saw, and a few houses, but is that really enough for a book? That was sometimes what people would tell me. And they were always surprised when I told them that, in fact, Wright designed roughly 30 projects for the Bay Area, although only about a third of them were actually built. And I'll say something later about why so many of them were not built. Here's a map that I created showing the locations of all of these projects. You probably can't see the numbers there, but they're a number for each of the projects, and they correspond to a list next to the map in the book. Moreover, these projects include some of Wright's most unusual and innovative designs. For example, his first design for a skyscraper of 1913, the call building was to be on Market Street, Market and Fourth Streets here in the city. And even though it wasn't constructed, it was one of Wright's favorite designs, and he built a couple of large models of it, one of which we see here on the right, which he kept behind his drafting table at Taliesin, his home and studio in Wisconsin. If built, this would have been the tallest building west of Chicago at this time, and it was also one of the most advanced skyscraper designs of that time. Another of Wright's Bay Area projects was a very unusual mortuary complex of 1947, the Daphne Funeral Chapels, to be a church and do both streets here in the city. Next to the San Francisco Mint, which we see in this drawing by Wright, one of Wright's drawings of the project, and we see, of course, up at the top here, there's the San Francisco Mint, which you're probably familiar with up just off of Market Street near Dubose. And when Wright first went to the site and asked Mr. Daphne what the large building was up on the rock, and Daphne said it was the San Francisco Mint, Wright said, we'll make the mint look like a morgue and your morgue look like a mint. And also another one of his projects for the Bay Area, a small Christian science church for Bolinas in Marin County of 1956, again not never built, and an amazing industrial plant and company headquarters for San Carlos on the peninsula, also of the mid-50s, which would have been Wright's largest structure if it had been built. Using the structural system Wright had created in the 1930s for the Johnson administration building in Racine, Wisconsin, with these innovative and remarkably slender lily pad columns, as they're sometimes called, and a fanciful wedding chapel commissioned by the Claremont Hotel in the Berkeley Oakland Hills and various structures for the Marin County fairgrounds adjacent to the Civic Center, including a fair pavilion, which we see at the top there with a tent-like roof suspended on cables and an amphitheater, and an amazing reinforced concrete bridge for the San Francisco Bay that Wright called the Butterfly Bridge, which he started working on in 1949, though he never actually received the commission for it from the state, and later I'll say more about this project also. And some of Wright's house projects for the Bay Area were also extremely innovative. For example, the Hannah House of 1937 at Stanford was the first time that he was able to talk a client into constructing a type of building he had been thinking about for a number of years with a plan based totally on non-rectangular geometry, in this case the hexagon. And we can see here, if you can see the plan clearly enough, that there are no Wright angles in the plan at all. It's totally 60 and 100 degree angles based on a hexagon grid, and as a result, Wright sometimes called this the honeycomb house. And he did this really as a furtherance of his desire to break open the box, as he put it, of conventional architecture. And as I say, this was the first time that he had found a client willing to build a structure with this non-rectangular geometry, and this really inaugurated an important characteristic of Wright's later work, the use of non-rectangular geometry such as triangles, hexagons, and circles. Another house in the Bay Area that's of interest, the Berger House in San Enselmo in Marin County, is unusual for a different reason. The man who commissioned it, Bob Berger, a teacher, constructed it for his family totally by himself, and as a result it took him nearly 20 years to build, probably the longest construction job of any of Wright's buildings. And the construction was especially difficult for Berger, because Wright had given him a design using what he called desert masonry construction. And this required building forms, and in the next slide here we see photographs taken at different times of Bob Berger working on this house over the years, photographs taken by his family, and a couple of his sons were kind enough to give me these photographs. And so up at the top here we see him building the forms for these walls, and then splitting large stones, and we see him doing that over here, to give them more or less flat surfaces, then placing them in the forms in such a way that when the concrete is poured and the forms removed, the stones are visible on the surface of the walls. Wright had first used this kind of construction at Taliesin West, his winter home and studio in Arizona in the 1930s. And the Berger House is unusual for another reason, it's Wright's only house for which he also designed a separate structure for the family dog at the request of one of Berger's sons. So it's Wright's only dog house. And among Wright's unconstructed house projects for the Bay Area are a couple of his most spectacular designs, such as this one designed in 1945 for Lillian and V.C. Morris, the people who commissioned the shop on Maiden Lane, the house being directly on the ocean in the C. Cliff neighborhood of San Francisco on Camino del Mar, if you're familiar with that area down below Lincoln Park. The design was so unusual and the site so precipitous, right on the cliffside there, that it turned out to be too difficult or expensive to construct. Wright then came up with some other designs for this site, such as another one here, almost equally amazing and dramatic, but none of them got built, even though the Morris's loved the designs, especially the first one. Well, another interesting thing about Wright's projects for the Bay Area is that they range over virtually his entire career. The first one for a small house in Oakland dates from around 1900, almost at the beginning of his career, just as he was starting to develop his prairie house style in the Chicago area, which you may be familiar with, some of his most famous buildings date from that prairie house period. And this is a mysterious design, which I'm sorry is a little hard to see here. I took three details from the design that are all on one rather large sheet of paper that was discovered in Wright's studio following his death. And there's no other information about this design. It doesn't even identify the client's name on the drawing or the address in Oakland. But it does say down at the bottom, dwelling for Oakland, California, Frank Lloyd Wright, architect, Chicago, Illinois, partly based on the fact that he, when he had his office in Chicago and also based on the style of the drawing and even more on the style of the design of the house, it's clear that it has to date from about 1900. This house really, we see here in a sense the beginning of the prairie house style, of his development of the prairie house style. With an emphasis, oops, I didn't want to move ahead. I wanted to use my light pointer here to point out the horizontal, emphasis on the horizontal with hipbed roofs, windows banked together to create openings in the upper part of the wall. And one very strange detail, it's probably a little hard for you to see, but the floor plan is composed of two squares that are overlapped or intersect some of the very kind of unprecedented at the time, but something that Wright was playing with at the beginning to develop this idea of more fluid and more complex planning types. And there are other details in this design which show that it has to date from just around 1900, just at the beginning of his career. So we have a, and it's the earliest design by Wright for any location, really west of the middle west. And so we have one of Wright's earliest designs here in the Bay Area, not built as far as we know. The other interesting thing is that it's not known whether this was ever built. So conceivably it was, but since we don't know the address or the client's name, we really don't know. And I've had a couple of people in the Oakland Planning Office who've been helping me to try to learn more about, see if we can find anything about this mysterious project. And that the end of Wright's career are several of his Bay Area projects, such as the Marin County Civic Center, which we saw before. Here's one of his overall drawings for the Civic Center, which he began working on in 1957, but was still designing when he died in 59. And in fact, one of Wright's very last commissions that he received was just before his death in April 1959. And it was for a church in San Francisco, the Holy Trinity Greek Orthodox Church, which was to be on Brotherhood Way in the southwest part of the city. He was just beginning to sketch out his ideas for the project, and we see some of these sketches here, just a few days before he died at the age of 91 in April of 1959. And as sketchy as these are, they show Wright approaching this design in a fresh and innovative way to the extent that I've been able to sort of decipher what he had in mind in these sketches, even at his advanced age and in failing health. I think it's best for me to take questions after the talk. But thank you. I want to entertain your question. When I began working on the book and decided to include Wright's unbuilt projects, as well as the constructed ones, I realized that people might wonder why so many of them were not built. As I mentioned, only about a third of the projects were constructed. Here's also one more of the unconstructed house projects, the Hargrove House in Orinda, which would have been one of Wright's most impressive houses. And since there's that stereotype about Wright that you may have heard stories about, that he was difficult to deal with and sometimes treated his clients badly, I realized that some people would assume that this was probably the cause of these projects not getting constructed. So I decided I had to try to find out the reasons for each of the unbuilt projects. Now actually, when I mentioned to a couple of my friends who were practicing architects that only about one third of Wright's Bay Area projects were constructed, they told me that this wasn't that unusual for many architects. But even so, I wanted to be able to answer the question. And I decided that I had to get access to the correspondence between Wright and the clients of all these projects, correspondence mostly in the Frank Lloyd Wright archives, which used to be Italian and West in Arizona, but is now at the Avery Library in New York. And with this correspondence, hundreds of letters and other documents, I was able to determine the reasons that each of these projects wasn't built. And it turns out that there were many different reasons, but surprisingly, almost none of them had to do with Wright treating the clients badly. This actually surprised me a bit. In a few cases, it was actually the clients who were difficult to deal with. And in some cases, the designs were so unusual that construction would have been difficult or too expensive, as I mentioned, in the case of that sea cliff design for the Morrises. Here we see that again. Or the client simply found the designs too strange to accept. And this was the case with a house that Wright designed in 1939 for a Mr. and Mrs. Smith in Piedmont Pines in the East Bay. The site reminded Wright of the Lake Tahoe site, where in the 1920s he had designed a group of buildings, here's one of them, that were never constructed, using a kind of Indian teepee shape. And he decided that this would be perfect for the Piedmont Pines site that the Smith said, which had a similar topography, he felt. But the Smith apparently found the design too peculiar and got into an argument with Wright. And these are things I discovered by going through all of this correspondence between Wright and the clients. So they had a difficult argumentative meeting, and they refused to pay him the fee they owed him for the preliminary design, which the correspondence reveals was only $240. It's amazing that, and this was, but they wouldn't even pay him $240 for all the work he had done to design this. Now this, by the way, was one of the very few cases I found of an unpleasant situation between Wright and one of his Bay Area clients. And in a couple of cases, that call building skyscraper and the butterfly bridge, there actually was no client. Wright simply did the design in the hope that it would get built. So that's another reason that some of these projects didn't get built, that there wasn't actually a client. And then there were some unexpected reasons why a building wasn't constructed. For example, a house that Wright designed in 1950 for a man named Robert Bush and his wife at Stanford. He was a young faculty member at Stanford, and he and his wife were friends of the Hanna's who had built the Hanna house in the 1930s. Well, the Bushes found Wright to be very amiable, as seen in their letters, and they loved the design that he produced for them, which we see here. And we're all ready to build it. But then there's a sad letter in the archive from Robert Bush to Wright, reporting that their daughter had been stricken with polio. And because of this, and all the medical expenses, they would have to forget about building the house. But he added that, of course, they would pay the fee they still owed Wright for the design as soon as they could. Well, as I was going through the correspondence, the next letter was from Wright immediately writing back to Robert Bush, expressing his sympathy for their daughter and saying, quote, don't worry about paying us. So there's a story that sort of contradicts the stereotype of Wright as always being mean to his clients. Well, I have to say that reading the hundreds of letters between Wright and his Bay Area clients, most of which had never been looked at by scholars before, as far as I know, was one of the most compelling and sometimes touching aspects of this research project for me. And I decided to include in the book all of these stories of Wright's relationships with his Bay Area clients. Well, another aspect of Wright's work in the Bay Area is that San Francisco is the only place where he had a branch office that is separate from Taliesin in Wisconsin and Taliesin West in Arizona. In 1951, when he started getting quite a lot of work in the Bay Area, he asked one of his former Taliesin apprentices, Aaron Green, to be his associate in San Francisco. And here we see the two of them in a later photograph. And they opened an office on Grant Avenue in downtown San Francisco. And here's the building. The building is still there. It's at 319 Grant Avenue on the second floor. Wright designed the office interior. And here we see his plan that he worked on with his notes on it. It was actually an ingenious design for the interior of this office with screen-like walls made of redwood slats and translucent glass. Oops, again I meant to use my light pointer rather than the advance. Here are these screen-like walls set at suggesting the hexagonal geometry, perhaps, of the Hannah House, creating three spaces. The drafting room, an entrance area, and a private office. But allowing, because this had translucent glass, these screen-like walls, it allowed some natural light and also visual privacy in each of these three spaces. So it was a very clever design for a space that only had windows on one side. Here, of course, looking out on Grant Avenue. It was a somewhat difficult design problem. And here we see what the office actually looked like, the private office and reception area at the top and then the drafting room below. Although we're not seeing it here in its original location on Grant Avenue. After Wright's death in 1959, Aaron Green continued to use the office but then had to leave the building and he dismantled the office interior and was later installed in the Carnegie Museum in Pittsburgh where we see it here. But then this office interior has a strange kind of odyssey as a history. Because in 2004 it was dismantled again and sold to a collector in Buffalo, New York. And it's been in storage there ever since. And it's been a fond hope of mine to have it returned to San Francisco someday and installed somewhere here. Well, now I'm going to turn to another aspect of the story of Frank Lloyd Wright in San Francisco, which is the various ways that he was covered in the local press. And to get this information, I spent countless hours here in the newspaper archives in the public library up on the fifth floor and also found material in the history room on the sixth floor. In the 1940s and 50s, the later part of Wright's career, the Bay Area newspapers covered him in basically two ways. On the one hand, there were stories about his projects in the Bay Area, as we would expect. Here we see on the left a full page article about his design for his butterfly bridge to go across the San Francisco Bay. And on the upper right there, a story about his hiring by Marin County to design the Civic Center and an article about his Daphne mortuary design. You can see the its title, Death and Taxes. And this refers to one of Wright's quips about the proximity of the mortuary to the mint, which is described in that little article. So that was one type of newspaper coverage about Wright. I might just mention that Wright had a distinctive and sometimes wicked sense of humor. For example, he later recalled that he had to visit in connection with designing the Daphne mortuary complex. That he later said he had to visit several other mortuaries with Mr. Daphne to learn about what they required and the programmatic requirements of designing mortuaries. And he said, quote, this nearly got me down. I would come back home wondering if I felt as well as I should. But Daphne had a way of referring to the deceased as the merchandise, and that would cheer me up. But another kind of press coverage during this period was about the often opinionated statements that Wright made in interviews and talks during his many visits to San Francisco. In general, Wright disliked American cities and the architecture in them. And he didn't spare the buildings in San Francisco, calling them, for example, shanty architecture, and saying, on one occasion, it's time you had another earthquake here. Yet, otherwise, he liked the city. Perhaps it's the only American city that he did genuinely like. On one of his visits in 1944, he said the following. San Francisco is the most charming city in America and the most cosmopolitan and picturesque, but the most backward city architecturally. Yet, it manages because of the character of its hills and environment and its people who are the best looking in the country. I like that. And then he continues, I don't know how much of this is due to natural advantages or accident, but I like San Francisco. As far as I know, it's about the only city in America that he ever said anything like that about. So positive. So in his later years, it was Wright's designs as well as his opinions on things that were reported in the press. And also the various things he did while in San Francisco, such as a round table forum that he participated in in 1949 on modern art in which he played the gadfly, making all sorts of controversial statements about contemporary art in society, which got widely reported in the local press. For example, he got into a couple of big arguments in this forum with the artist Marcel Duchamp, who was also on the panel. Here we see in one of the their sessions, here's Wright and here's Marcel Duchamp down there, and they got into some amazing arguments, and I had to get the transcripts of this whole of these sessions from the San Francisco Art Institute. And at one point, and another one of the sessions, the one at the bottom here, and here we see Wright at the end of this table here, he one of the after Wright was making controversial statements, one of the other participants interrupted and said, what Mr. Wright is saying is sheer nonsense, which naturally did not sit well with Wright and things started going downhill from then on. But what's interesting is that the newspaper stories that San Franciscans first read about Wright many years earlier were very different from this. They had almost nothing to do with his architecture or his public statements, but with the scandals and tragedies in his personal life in the 1910s and 20s. In 1909, Wright had left his wife and family and gone to Europe with the wife of one of his former clients, a woman named Maima of Borthwick, Cheney. And when they returned in 1911, he built the first Taliesin in Wisconsin as their new home, mainly to get away from Chicago and to try to avoid the negative publicity about their relationship. And then in August 1914, there was this terrible event reported here in the San Francisco Chronicle and Examiner, those two stories, in which Maima Borthwick and her two children were murdered along with four other people at Taliesin, murdered by a servant who had apparently become deranged, and the house was partially burned down. The article here from the examiner up there, the article in the next morning says that three people were killed because it wasn't yet known that seven had died. And more details of the tragedy kept being reported day after day in the San Francisco newspapers along with the story of Wright's relationship with Maima Borthwick, making him out to be a disreputable or at least extremely unconventional character. And for many years, virtually the only news about Wright in the San Francisco newspapers, and this is what I discovered by really going through all of these newspaper, working in the newspaper archives here in the library, about the only news about Wright was about these personal problems of his. As he finally then in the succeeding years divorced his first wife, married another woman, Miriam Noel, then separated from her and met Olga Vana Milanoff, who eventually became his third wife and actually contributed to the success of his career in several ways for the rest of his life. But in the 1920s, these personal problems involved all sorts of legal battles and disputes which the newspapers loved. There were times I found that day after day there would be in the San Francisco newspapers in the early and mid 20s, there would be one story after another about Franklin Wright's problems or his these of women in his lives. It was like a long-running soap opera. And in 1927 there was a local angle to this story when Miriam Noel, his estranged second wife, who had disappeared from Chicago several months earlier, as according to the press, was found hiding in San Francisco, as the papers said, in an apartment building at 925 Sutter Street on Lower Knob Hill, where she gave several sensational interviews to the papers, Attacking Wright and Olga Vana. Here we see two of the stories from the examiner. And in the one on the left here, here's Miriam Noel and Wright of course and this is Olga Vana. In the in the first story in February, she was quoted as saying, I've been here in San Francisco for my health. This is Miriam Noel, was quoted as saying, the shock and publicity that followed my husband's devotion to Mada Milanoff has so completely undermined my health that I'm a nervous wreck. I came out here to recover and I've succeeded wonderfully. California is wonderful. I've gained 30 pounds since I've been here, she said. She apparently liked San Francisco cuisine. Well, Miriam stayed here in San Francisco until September when her divorce from Wright was finally settled. The photograph on the right shows her boarding a train for Los Angeles and she was quoted as saying, I've had several offers from Hollywood and I'm going to drop in tomorrow and have some screen tests taken. I might stay and work in a picture and then I'll go on to Paris. I'm going to drown my sorrows in art. So what's interesting, I think, and the reason I bring this all up is that for many years the general public heard mainly about these scandalous and sensational aspects of Wright's life. And it wasn't until later that newspapers began reporting on his architecture in a serious way. And this early focus on the scandalous or tragic aspects of his personal life colored the public perception of Wright to some extent for the rest of his life, I think. Most books on Wright's architecture don't mention or tend to avoid these more sordid topics, but I decided that they were relevant to the larger question of how Wright and his architecture were perceived by the general public. Next, let me mention a couple of Wright's buildings in the Bay Area that I haven't shown so far. First is one called the Bueller House in Orinda of 1948. In most ways, it's typical of Wright's Usonian house type that he was developing or had developed in the 1930s with concrete slab floors and radiant heating and other features that made them a somewhat less expensive prototype for middle-class suburban housing. But the Bueller House here has some unusual traits not usually found in the Usonians, especially a large octagonal living room, which we see in this photograph, with a sloping plane for a roof, not the normal way you'd think of roofing, an octagon, which creates a very dramatic interior space. It's a really beautiful room. And another house I want to show here, the Bazette House in Hillsborough, which has a hexagonal plan, like the earlier Hannah House, though it's a completely different plan and a smaller house. But one of the most interesting things about this house has to do with the people who lived here. First were the Bazettes, Sydney and Louise Bazette, who built it in 1940 and loved the house, but only lived in it for two or three years due to personal problems. Then they rented it for two or three years and then it was bought by young refugees from Europe, Louis and Betty Frank, who lived there for the rest of their lives and had Wright design a small addition to the house. So it's sometimes called the Bazette Frank House. But the person who rented the house in the early 1940s, before the Franks bought it, was a man named Joseph Eichler, who at that time worked in his family's wholesale food business. But he got to love the house so much that he became interested in architecture and several years later bought a company that produced tract houses. But he wanted to create a better type of tract housing than existed. And he hired the architect Robert Anshin and then later some other architects who, and Robert Anshin, at first designed prototypes for Eichler that were simplified versions of Wright's Usonian houses. And here we see a very early ad from the Palo Alto Times for advertising these Eichler homes as they were called. You can see the full price of it is $9,400. And this led to more fully developed designs for these Eichler homes, thousands of which, as you probably know, were built in the Bay Area and elsewhere, but mainly in the Bay Area. And they were widely published and won architectural awards and had an important influence on post-war suburban house design in America. And Eichler later acknowledged fully the influence that Wright and the Bazette House had on him. He later said about living in the Bazette House for just those two or three years. He said, it was a revelation to me. I admired Wright's rich design and asked myself if such houses could be built for ordinary people. So one of Wright's Bay Area buildings had an unexpected and significant effect on American suburban architecture. Well, now let's look more closely at the VC Morris Shop on Maiden Lane here in the city. As I mentioned before, Wright was commissioned in 1944 to design a house for the Morris's, Lillian and VC. He was always called VC Morris, and it took me a while to find his full name. His full name was Veer Chase Morris, but for some reason he insisted on just being known as VC Morris, and that was the name of their shop. But before the shop was designed, they had commissioned him to design their house for their property at Sea Cliff on Camino del Mar, and we saw before this amazing design that he came up with. And for several years, they kept pursuing this house project, trying to get it to work and to be feasible, and Wright produced other designs for the site. We saw one of those before. And in the process, Wright and the Morris's became good friends, and there is a photograph I found of Wright and Lillian Morris at Stinson Beach, where they had some property and they asked Wright to, this was later in the 1950s, they asked him to design a beach house for them at Stinson Beach, and he did. He designed that house, but which also was not built. There were other reasons why that one wasn't built. Aaron Green, who had worked on these projects, on the later projects for the Morris's with Wright, Aaron Green was later in an oral interview asked if Wright ever got discouraged because none of his house projects for the Morris's was constructed, and he said, no, he liked the Morris's so much that he just kept trying. Then in 1947, they mentioned to Wright that they were planning to remodel their shop on Maiden Lane. Their shop was just in an undistinguished small building on Maiden Lane, and much to their surprise, he offered to do the design for them. It was surprising because Wright almost never took remodeling jobs, he considered it kind of beneath his dignity or that he wasn't, that they wouldn't give him an opportunity to do interesting enough projects, but he accepted in this case. And I think the reason is that I think it clearly had to do with the Guggenheim Museum in New York, because beginning in about 1943, earlier in the 40s, Wright had been working on his design for the Guggenheim Museum, for Solomon Guggenheim in New York. Here we see some of his drawings as he was trying to work out the design, but the process kept dragging out and kept being delayed and it was unclear whether it was really going to be built, and he was exploring various ways of dealing with the concept of a spiral ramp as the basic form of this museum, this building. And it wasn't until the late 50s that the museum was actually constructed. So I think that Wright took on the Morris job in 1947, because he saw here an opportunity by completely redesigning the Morris's shop to explore on a miniature scale the Guggenheim concept of a spiral ramp as the centerpiece of a building whose function was the display of objects. So in that sense that the programs were very similar. And here I have views of the two buildings, the Guggenheim on the right, of course, and the VC Morris shop on the left. And the Morris shop was constructed in 1949 long before the Guggenheim got built. So there's this fascinating relationship between these two projects. And with the Morris shop Wright, in a sense, was doing a kind of small scale tryout of the Guggenheim concept. And if we look at one of the, look at a detail of one of Wright's section drawings for the shop, we see that he was even thinking of how to display some of the Morris's merchandise on the ramp itself in circular recesses in the walls. And this is, in fact, how it was constructed and used. Here we see a photo of it taken right after the construction of the shop, when it was still the VC Morris shop. Well, this turned out to be one of Wright's own favorite buildings. And whenever he came to San Francisco, he would visit it. It was on his walk from the St. Francis Hotel, where he usually stayed, to his office where they're in Greenon, Grant Avenue. And Green later recounted how Wright would often enter the shop and rearrange the merchandise. As are typical of Wright, here we just see another view of the interior right after its construction. Although Green added, when he described how Wright would do this, he added, if I came back the next day, everything would be right back where it was before Mr. Wright had been there. And Wright's design for the exterior of the shop, though it may look rather plain at first, is also really an extraordinary design with a number of subtle and unusual details. I might mention that the shop has been sold recently and that does not have a new tenant yet, so it's closed now. So you can't go in the shop now, but of course you can go there and see this exterior. For example, on the exterior here the main surface is pulled out just slightly from the surrounding frame, and you can't see that too well here, but it's as if there's a kind of frame around, and then the central part of it is pulled out. And the bold arched entryway there is emphasized by a series of recessed bands, as you can see. And on the left side is a column of removed bricks which are lit at night and have a, this is an old photograph taken right after the construction of the building, and have a counterpoint in a horizontal row, as you can see, of lit squares at the base of the building. And here we see another more recent view of that. But then there's an amazing detail which is normally not pointed out, I think, in discussions of this building in the Wright literature. In the tunnel-like entrance there that you go through to enter the building, the vault in this tunnel-like entrance is brick on one side, and I think I have the next slide, here that shows that better, is brick on one side, but glass on the other, which had never been done before, as far as I know. It was really somewhat unprecedented and shows that Wright was willing to violate the conventional logic or rules of architectural logic in a way that most architects probably would not have dared to do. A vault, after all, should be made of a continuous material. So he's doing something very odd here. And in this and many other ways this is really a remarkable building. In my opinion, it's one of Wright's most brilliant designs, both inside and out. And as I say, the building was recently sold and will have a new commercial tenant. I've actually been working with the San Francisco Planning Department and the Frank Lloyd Wright Building Conservancy, the main Frank Lloyd Wright organization, to try to ensure that the interior as well as the exterior is fully protected and preserved. Well, finally, I'm going to say something more about Wright's amazing design for a bridge across the San Francisco Bay. Following World War II, there were calls to build a second bridge from San Francisco to Oakland to accommodate increased traffic. This was, of course, before the Bart tunnel was proposed. And a structural engineer who lived in Berkeley, Yaroslav Polivka, who had worked with Wright on a couple of his earlier projects, suggested that Wright produce a design for this bridge, which he did in 1949. It was a really unprecedented design, mostly consisting of precast concrete sections that reminded Wright of butterfly wings. So he called it the butterfly bridge. But the most dramatic part was the central section with two arches spanning 1,000 feet, which we see in the upper drawing there, which reportedly would have been the longest concrete bridge span at that time. The two arches separating at the center. This was the unusual, perhaps most unusual feature about this design. These arches separated in the center and supported a suspended landscape park. And oops, again, I'm advancing when I don't mean to. Here's the central part of the bridge. And you can see how the roadway splits here, so that there are two arches. And then the idea was that one could pull off into this landscape park and enjoy the views from above. And you can even see part of this park that's up in that drawing. Really amazing and kind of crazy idea, maybe, but certainly something that's never been done before. Well, Wright and Polivka promoted the design and received a lot of favorable attention and publicity. And here's that article that we saw before from the San Francisco Call newspaper. And it includes a map showing where this was to be. This is the existing bay bridge. And this is where Wright's design was to be, running from just about the end of Army Street over to Alameda. But the state agency in charge of such projects rejected the design as being too radical and untested. Nevertheless, Wright continued to promote it over the next several years. And in 1953, he constructed an impressive model of the central section, which he presented at a large public event at the San Francisco Museum of Modern Art, which at that time was in the War Memorial Veterans Building in the Civic Center. The model then stayed there and was seen by many more people, including groups of school children, as we can see here. Then the model was exhibited in other places in the San Francisco area, such as the Emporium Department Store. And in this photograph we see, this is Aaron Green, but this is George Christopher, Mayor Christopher, who was a big supporter of this project. And then exhibited at the Stonestown Shopping Center, and here we see it at Stonestown. Well, Wright's presentation of the design at that Civic Center event was widely reported in the press. And let me read from the Chronicles story about it, which gives an idea of the enthusiasm the public had for Wright's works. It also gives an idea of the exuberant and dramatic flair that Wright himself had in promoting these projects. I'll just show one another view where we see the model as well as that drawing, which was also on exhibit at this event in the Civic Center, 1953. Well, here's part of the article that was in the Chronicle about this event. Frank Lloyd Wright unveiled a model of his butterfly bridge for the San Francisco Bay last night with a flight of rhetoric as soaring as the bridge's great arches. He said, here is your bridge, steal the sinews, buried in the flesh, concrete. He's describing reinforced concrete there. A bridge for all time, no upkeep ever needed. And then going back to the article, the audience that jammed the San Francisco Museum of Art to see and touch the 16 foot model of the bridge was appropriately uplifted. The 535 seats in the main auditorium were sold out. Another 500 listeners applauded Wright's words in an overflow gallery and an estimated 500 more sprawled on the marble floors with their ears cocked to amplifiers. Wright called his bridge, this concatenation, this wedding of two materials, an eternal bridge in which the water becomes with the bridge a great element of beauty. We can't go on building bridges that are the equivalent of poles and wires. He's referring to trust bridges and suspension bridges, which he thought this would be a better type of bridge. And above all, we can't have this obstreperous interference in the name of science into the realm of beauty. He's talking about the state engineers who rejected his design.  Divorce the bridge from politics. Stop worrying about Oakland. Get out and build it yourselves. He was a real showman. By the way, that reference to Oakland was because Wright's design for this butterfly bridge had been received very enthusiastically in San Francisco, but a different site for the bridge was favored in the East Bay for various reasons. Well, in more recent years, Wright's butterfly bridge has been re-proposed on several occasions. For example, after the Loma Prieta earthquake of 1989 when the famous bridge designer T.Y. Lynn examined the design, Wright's design, and said he thought it was structurally feasible. And Jerry Brown, when he was a mayor of Oakland, said, it's a fantastic design. If we had this bridge leading into Oakland, it would be a major boon. People from all over the world would come to drive across it. So by then, it was appreciated in Oakland too. Like so many of Wright's buildings and projects, this bridge looks as advanced and amazing today, I think, as when it was proposed more than 50 years ago and even longer ago in the case of other designs of Wright's. For example, his C. Cliff house for the Morris's more than 70 years ago, or his radical hexagonal house for the Hanna's at Stanford 80 years ago, or his call building skyscraper for Market Street more than 100 years ago. Well, I hope I've been able to suggest the really remarkable qualities and diversity of Wright's Bay Area works and some of the fascinating aspects of his relationship with San Francisco. Thank you.