Good morning or good afternoon, depending on where you are in the world. This is Mark Follier with OpenStack Foundation, and we're excited to have another webinar. And more interestingly, we're excited to have a new release of OpenStack. I'm sure most of you know a new version comes out every six months with the hard work of many, many people. I want to talk to some of those folks today that are joining me on the webinar and talk about what's in the release and what it means to users and also answer any questions that the audience may have as we go along. So feel free anywhere along the way here to pop questions into the BrightTalk webinar system and we'll try to get to as many of those as we can as we go along. So Juno is the tenth release, hard to believe, and just over four years the community has been able to produce ten releases. And to start with, I'm going to talk a little bit about some of the highlights and then we're going to try to get quickly to asking Kyle and Andrew who are joining me on the webinar some questions about it and get their point of view. So Kyle Mestri is a Senior Director and Chief Technologist of Open Source Networking at HP. He's also the Project Technical Lead for the Neutron Project OpenStack Networking. So you can certainly direct your toughest networking questions at Kyle and I'll quickly deflect them to him. And we've also got Andrew Metri who's an architect at Comcast. They're one of the largest OpenStack clouds out there that they are running their business on and we always love to hear from users and not just those of us who are involved in OpenStack every day working on building it but also really hear from those people that are using it and find out what they like and don't like and how they see the new release, how they think about evaluating each new version and what goes into that. So we wanted to start with a quick poll and the question was really how familiar are you are you with OpenStack and there's a voting system that's part of this webinar platform and I have just started the poll so you can actually click inside the webinar app. Wow we're getting tons of votes already. So really just wanted to know if you're just kind of hearing about OpenStack, if you're actively evaluating it or if you're already running it, maybe some other scenarios or other categories but as we go along they'll help us kind of get a sense for who all is in the audience and your familiarity with OpenStack. Now I know that probably a few people are here just learning about it for the first time so at a very high level OpenStack is a cloud platform that helps you manage your compute storage and networking throughout your data center, really helps automate that and includes a dashboard both for administrators who are operating the clouds, you know folks like Andrew at Comcast and the end users, the developers who want to provision those resources also can do so through a self-service dashboard. So at a high level you know that's what OpenStack is all about and you know businesses really use it to move a lot faster to give their developers the resources they need to be creative, to create value, new features, get them to market faster than sort of the pre-cloud era of opening a ticket and waiting weeks to get a new machine online just so you can start hacking on an app idea you have, that can happen in minutes now with all the enterprises adopting cloud and OpenStack is there to help that transition and you know with the 10th release one of the things that continues to be front and center for users is how wide of support the platform has for different technologies. So by that we mean things like drivers, there were almost a hundred drivers that were tested throughout the development process of creating Juno that are included in the Juno release and there are many other drivers available from all of the top tier vendors from compute storage and networking and of course we see people using it in many different industries. Some of the themes that we see Juno really hitting on are enterprise maturity so you know because we have a lot of plug-ins and driver support that means that it works in very diverse environments. Some of the improvements in the object storage around storage policies really help with enterprises that maybe have different classes of data and they want to store it in different regions or at different levels of redundancy depending on how critical it is that they have X number of copies. A lot of improvements in the identity side and make it easier to plug into LDAP and also to federate identity across different environments. You know NFB is something we'll be talking about a little bit later which is a new buzzword if you haven't heard it that comes from the telco world of network functions virtualization and then last but not least the biggest new overall capability that was added in with this integrated release was the data processing capability and this is really for things like Hadoop that many users were already running on OpenStack. They're now able to do that within the OpenStack dashboard and really help create different node pools, different cluster templates and quickly spin up worker nodes and control nodes and help run jobs and do all that from inside of the OpenStack dashboard. So for people that were interested in running things like Hadoop on OpenStack that is now a lot easier thanks to this new Juno capability. One of the things that is really key to how we as a community approach developing OpenStack is that we always want to have as much user involvement as possible. This is not like traditional software that might be developed in a very closed manner by one company and then kind of trotted out on stage at the Moscone Center and sort of force-fed to the people in attendance. This is much more about getting users involved. We've had ops summits. I was really lucky to attend an ops summit in San Antonio back in August where we had users from Comcast, Timer, Cable, GoDaddy, Yahoo! There's a whole list here you can see but these are all people that not only are running OpenStack but they really care about the future of OpenStack and they're helping drive the direction of it. And that's a big part of how we got to Juno and how we do things in OpenStack to make sure the software really meets the needs of the end users. People are always interested in the stats. Over 1,400 people contributed to Juno which was even more than Ice House. I think at some point you kind of lose track of how many features when you get over 300 to kind of too many to list. But we also certainly saw a lot more activity in the bug fixing area and I think that's a testament to how many people are running in production and helping identify different issues that were brought forward and fixed in Juno. And there were also some really cool statistics that I didn't put on the slide but Jeremy Stanley who is one of the members of the OpenStack infrastructure team was letting me know just how massive the testing infrastructure has become. We have over almost 100 third-party testing systems plugged in that help verify all those drivers I was talking about and we actually saw just in the six month time almost 20,000 changes merged and that includes not just OpenStack but a whole host of things that the cloud computing industry cares about that the infrastructure team is kind enough to help manage and facilitate as part of the infrastructure and actually over 18 terabytes of log data was generated through the process of all that testing. So pretty amazing scale for a distributed team that's really not driven by one company. It's really a community-led effort. And so the number of contributors has become so massive that you really can't put them on one slide well though we tried but just want to thank all those contributors that made this possible and I really hope that we're able to, they're all able to come to our next summit in Paris in a couple of weeks. So the summits are a great place for all the developers and users to get together. So with that intro out of the way I wanted to throw some questions out to my guests on the call today. So I guess we'll start with Andrew Mitri from Comcast. What do you see are some of the most significant changes in Juno coming from the Ice House world? So I think we see a few different things that we're really excited about.  Having IPv6 support baked into Neutron is something that we were excited about and we were excited to kind of participate and lead the sub-team on that effort and see it come to fruition there. Also some of the new services that are coming up with NFV and also the big data that Sahara, like you mentioned, we've actually had a lot of our internal teams ping us about, oh, when are you releasing Sahara? When can we leverage this? When can we do that? So that's been generating a lot of interest where they're actually, you know, it's probably one of the first times that our internal teams are tracking OpenStack and saying, hey, I need this feature. When can you get it deployed? So we're getting a lot of internal interest there as well. Also, yeah, and lastly is the, you know, just the live upgrades and the better stability and enterprise integration with Keystone and all those services as we mature and scale out the platform. We're excited to see those come. Okay, great. Kyle, I know you've been living and breathing the networking Neutron project. So I'm sure that that's near and dear to your heart, but overall I guess we'd love to hear your perspective on kind of what makes Juno such a big relief for OpenStack and the user base. Yeah, thanks, Mark. I think one of the main features on the Neutron side for Juno that the team has worked really hard on was the distributed virtual router support, which is otherwise known as DVR. And this was important because as a team, the Neutron team really tried to focus in Juno on parity with Nova Network, which is something we've been working on, you know, stability and parity with Nova Network. And we really achieved that during Juno now and DVR was one of the key features for that. And at a high level, what DVR lets you do is it lets you remove the routing functionality to each computer host, and it also moves the DNAT functionality down there as well. So this was a pretty huge feature and we'd really love to see users provide a lot of feedback for this in Juno. The team is going to be working to expand support for this during the TLO development timeframe as well. And one of the other things that I'd like to mention is one of the big changes that we saw was we really tried to involve operators a lot more during the Juno cycle. This was facilitated partially by the ops meetup which you had mentioned before. And specifically, when we were looking at migrating Nova Networking users to Neutron, we as developers and engineers spent a lot of time thinking about that. We came up with some prototypes. We worked through some examples. But it was really key to us to kind of get input from the users and the operators. And so the ops meetup was really key from that perspective. So it was a very useful experience for us on the engineering side. Yeah, that's great. I think I'm glad you brought the ops meetup again because I know that Comcast had quite a few folks involved there. And Andrew, were you able to attend the ops meetup or what was the kind of impact for your team? I was there along with some of my team. And actually, we find the ops meetup beneficial in a couple different ways, not just in interacting with the developers and giving feedback there and kind of having them back and forth there, but also interacting with other operators and kind of learning best practices and how they make things work at a larger scale and what challenges they have, how they solve those challenges. So the community around it is actually really valuable for us. It's definitely one of the events we really look forward to every cycle. And I think it helped us build a relationship more directly with those developers so that, hey, now we can put a name, a face of that name, and reach out over IRC or whatnot, or reply to a thread and understand what the context was there. That's great. And for anybody out there who's not aware, you know, we do, we've started more regularly having these ops meetups for users in between summits, but we're also doing them at the summit. So there will be some breakout sessions dedicated to operator discussions and collaboration at this upcoming summit in Paris. So if you're an operator and you're coming to the Paris Summit in November, you know, be sure to check out those sessions. So let's go to the next slide. And I think I want to make sure I pause and encourage people to put questions in the, you know, in the question box, and we'll try to get to those as we go along. So how has OpenStack evolved within your organization?  But Andrew, do you have any insight you can share on kind of how that's evolved over time? Yeah, sure. So, you know, we started looking at OpenStack back in 2012 and did our first, you know, small kind of proof of concept production deployment at the end of 2012. Now, I think we demoed X1 on OpenStack in the spring of 2013 and was doing production traffic with our set-top boxes there. And the past year since then, almost a year and a half now, we've deployed more than five times the amount of infrastructure. We've kind of become the de facto in-house cloud provider within Comcast and we've changed, we've had kind of a paradigm shift where our products used to, you know, deploy infrastructure just for their product, kind of all in one vertical. And now the default option is let's go deploy on this multi-tenant platform that we've rolled out within Comcast. We can get our products out to market faster. A lot of wins because we can now, we don't have to wait for infrastructure. We can spin up compute and storage on demand. And so we can do things like support events that need infrastructure just for a short amount of time like the Olympics or the World Cup, spin up a lot of infrastructure and then spin it back down and use that for something else. So it's really helped us evolve the cloud paradigm within Comcast. Wow, so the Olympics or the World Cup, those are, I've heard of those. Those are pretty important pieces of infrastructure hanging on in the background trying to deliver that to a lot of wild fans all over the world. So that's pretty awesome that OpenStack can have some part in that. So we did have a question from the audience and I think this would be a good one for Kyle. So this user or audience member asked that a lot of users seem to be using Nova Network, which for those of you who aren't familiar, there's really two ways to configure networking in OpenStack. There's Nova Network, which is the sort of legacy networking capability built into the Nova project. And then there's the neutron, the more forward looking kind of direction. And so the question was, there are a lot of users using Nova Network that aren't planning to start using neutron. Do you see this changing with Juno? What needs to be done to facilitate this transition? This is definitely a frequently asked question. I hear from users and we heard it at the Op Summit. So maybe you can shed some light on that for us, Kyle. Yeah, absolutely. So I think you're right. This is obviously a pretty hot topic. And both teams, the Nova team and the Neutron team spent significant time over the Ice House and Juno timeframes on this. And in fact, we entered the Juno development cycle with a charter from the technical committee to close this parity gap. And the team did a spectacular job in closing that. So the one area where we really didn't close it was on the migration plans. And as I touched on earlier, we really wanted to get some more input from users on that because that was the one thing you were lacking. So I expect during the key low time frame, we'll try to move forward on migration strategy there. You know, my general consensus was that it was hard for us to get a lot of data around who's using Nova Network versus who's using Neutron. And Matt made the migration story a little bit better. So we would certainly love to hear from additional users in this area for people that are using one or the other or that want to migrate from one to the other, that sort of thing as well. So I think that that's one thing that we'd really like to help to facilitate this migration maybe from the new Nova Network to Neutron. If we could hear from more people, it would help us to be able to better plan what the migration story will look like, I think. Yeah, that's a great point, Kyle. And this is a perfect time for me to plug our user survey. So we continuously, the foundation and working with a lot of different people in the community and the user committee have created a user survey where we're constantly collecting insight and input from different users. So if you go to openstack.org slash user survey, you can go in there and it takes about 10 minutes to tell us what you're doing with OpenStack. We get data points like, you know, how many people are using Nova Network versus how many people are using Neutron and what do you think about Neutron or what's the hold up for you to make the migration. So that's actually our single bit biggest kind of tool that we have in the toolbox to get that insight. So please go fill that survey out. We've gotten a tremendous number of responses in the last few weeks because we tend to go over the results at the summits. But, you know, we're always welcome people to fill that out whenever possible. Now, we have another question come in, which is what are the plans for bringing in Docker support on Mainline of OpenStack? And I can speak to that a little bit, I think. You know, I think I just actually caught up with Michael Still yesterday, who's the PTL for Nova. And he would certainly be the best person to provide kind of the most recent details. But the way he explained to me was that, you know, Docker support is very strong at this point through the Stackforge hosted drivers. And so there is some interest, I think, in bringing it back into being part of, you know, shipping as part of the release, you know, potentially in a future release. It's not the case for Juno. But the good news is that to a certain extent, it's kind of semantics as to where the code lives. You know, having the driver shift with the software certainly means it's passed a lot of QA tests. But on the other hand, if it's shipped through Stackforge, meaning it's not actually shipped with the release, that doesn't mean that it hasn't been tested. So some people, I think, kind of conflate those two things. So, you know, in this particular case, you know, the feedback I've gotten from Michael is that there is a lot of activity around Docker. We certainly know there's tons of interest. And there are multiple ways it can be used with OpenStack, both in a sort of pseudo hypervisor type of a role through that as a driver in that sense. As well as on top of OpenStack guest VMs, you may want to use something like Heat, the orchestration framework to orchestrate the deployment of Docker containers on top of OpenStack Cloud. So there are a lot of different layers. You can use Docker with OpenStack. And there's certainly a tremendous amount of interest. I think there'll be a lot of discussions about that at the summit in a couple of weeks. And that was actually why I was catching up with Michael, was to make sure we had everything in place for those discussions to happen. So hopefully that addresses that question. So here's a question that is definitely for Kyle. With the new DVR on Neutron, how North-South traffic is going to be managed on OpenStack? Is there going to be a need of an additional edge router for traffic outgoing or incoming than virtual environment? Yeah, definitely. So I will say that there's actually a great Wiki page that the DVR team put up. I don't know if we can share links here, Mark, or not, but in the background maybe if someone could let me know, because I can share that it has a lot more detailed information. But I mean, in summary, the intent of the DVR is to do that. So with regards to the North-South traffic, I think that the person maybe needs like the added traffic for floating IPs. And so we can do the DNAT on the host, but the SMAT still is required to be done on a network node. And the main reason for that is the SMAT requires burning IP addresses for compute nodes. Now, there is some work going on to figure out how to possibly do this in an efficient way in Kilo, but it didn't make it into Juno. I will also say, though, that we did land the blueprints around making those network nodes highly available. In other words, making them so you essentially have HA with them there. So that actually helps in that particular case for the SMAT nodes for DVR. Okay, great. And just so you know, Kyle, there's a box that says live audience messaging below in the webinar page, and you can drop links in there. So if you've got a Wiki link that would be useful for the audience, you know, definitely put it in there. So I think we had... What's that? Oh, I was just saying thank you. Yeah, perfect. Oh, cool. So next question was, is designate fully integrated into Juno for DNS as a service? So designate is an official project that's in the incubation phase. So it will be in, I assume, a future integrated release, but it's not at that state yet for Juno. So it's available, the software's there, a lot of people are using it, but it's not at that phase yet where it was classified as being part of the integrated release. So hopefully, you know, we'll see something along those lines next year. Next question was, this is a great one. We definitely hear a lot from users, which is about upgrades. We'll talk more about upgrades from Icehouse to Juno. So I could take a stab at that, but I'll maybe throw that one to Kyle and see if you want to take that one. Well, you know, like it might be worth having Andrew talk a bit about that as well from a user perspective, if you're comfortable with that. Sure. I mean, I could talk a little bit. So we've, you know, right now, we're going from Havana to Icehouse just about done with that process. And it's been a lot less painful than previous upgrades. So we're happy that a lot of feedback is making it through the operator to meet up and the feedback we've been given there. We haven't made the step yet from Icehouse to Juno, so I can't speak as specifically to that. But it does look from everything that we've been monitoring that should be an even more seamless transition than going from Havana to Icehouse. So we're excited about doing it. We try to maintain a regular release cadence with the goal of eventually getting to be a month off of an official or stable release. Right now we run about five to six months behind. Yeah, definitely. I mean, one thing I can say on the neutron side with regards to upgrades in Juno, we really did a lot of work to clean up our database migration story, which definitely will impact upgrades going forward from Juno. I mean, previous to Juno, we had an issue where we had plug-in specific migrations which caused different issues around the item potency of where you landed. So we had a team working on that, and they did a great job during the summer, and they cleaned all that up. So now in Juno going forward, we didn't no longer have plug-in specific migrations, so I think that's definitely going to be a win for people using the Trump. Yeah, I'm glad you brought up the database piece of that. I know that in the past, from the Nova side with Compute, there was really from Havana to Icehouse was the first time it was possible to really do an upgrade without impacting end-user workloads in the Compute realm. But there was more painful and took more time than it really needed to because of the database migration updates. And so I think that was one of the things that improved from an upgrade perspective on the Nova side from Icehouse to Juno, which is what you were alluding to in Neutron as well, which is all that work to make the database updates faster, helps in a lot of different realms. So let's see. Another question was, how's the IPv6 integration going on? And I know that this was a big part of the Neutron networking story for Juno. So maybe, Kyle, you want to give an update on that? Sorry, Mark, this is around the IPv6 stuff. I apologize. Yeah, the IPv6 improvements. Yeah, definitely. I mean, the goal in Juno was to essentially close the gap around IPv6 on tenant networks. And like Andrew said earlier, Comcast was heavily involved in this. They had someone leading the sub-team. And this was another example of great work by the team, and we were able to close all the gaps so that we now on Neutron support full IPv6 for tenant networks and everything. And I'm sure Andrew can go into much more detail around the specifics of that as well, given his team kind of led that way. Yeah, so to be clear, we're actually running V6 via some backports today on Havana in production. And all our set-top box traffic and email traffic, all that requires V6 today. And so we do run it today, and we're excited that it is fully supported upstream in Juno. So it worked well for us. Okay, thanks. So there was a question about installation and configuration.  And, you know, maybe this would be an interesting one. Andrew, for you to comment on, I'm sure you haven't had the time to evaluate every possible installation tool, but, you know, maybe if you can talk about how you guys approach, you know, picking the right installer or talk a little bit about how you guys manage that, that might be useful for some of the people in the audience. Yeah, so we've been running OpenStack for a while. We started off at the time leveraging Puppet because it seemed for us the most mature way of getting OpenStack installed, and that's kind of where we're leveraging today. I think we are very interested in the evolution of OOO, and we're keeping an eye on it, but today we've been kind of focused around just leveraging Puppet and it's working for us there. Okay, thank you. So I'm just kind of going through some of the questions here, and I know we had a few more in the deck. So maybe this is a good time to ask Kyle to talk a little bit about NFV. For those of you who don't know about NFV, it's network functions virtualization. We discovered there were three letters that hadn't been made into an acronym yet, so we felt like that was a good opportunity to do that. So this is really about the telco world and trying to virtualize all these functions that happen at the back end of these massive networks and route all of our cell phone calls and text messages and MMS, and trying to make that more of a software-defined world for those guys and taking advantage of that. And OpenStack plays a role in that and Neutron as well, so Kyle, can you shed some light on what NFV is about and what role OpenStack is going to play in that new market? Absolutely. So I think what you said, NFV is really about virtualizing all of these different network functions and being able to kind of orchestrate them so that you can dynamically spin them up and spin them down. And if it sounds familiar, I think it's a lot of what, you know, the existing server virtualization world was doing. This is applied to kind of network appliances or functionality that was done there. And OpenStack is really a natural place for this because we have the orchestration capabilities which are necessary for this, and we have the capability to manage these images, these network functions as their virtual images. We have the networking capability to string them together, to spin them up dynamically, to place them where they're needed, close to the workloads, or wherever you want to put them. So I think that's why it's kind of a natural place. During the Juno timeframe, there was an NFV sub-team which was sitting kind of a, it wasn't a sub-team of any particular project. It was a broader team that was focused on all of the different pieces that are involved here. And I know during Juno they spent a lot of time on Nova Blueprints doing things that were important for NFV on the Nova side. And, you know, we're already engaged with them on the Neutron front because I suspect that during the Keyboard timeframe, we're going to really focus on what Neutron needs for NFV and, you know, to enable that from the Neutron side. Okay, thanks, Kyle. So, Kyle, there was a detailed number of questions in the webinar from one of the audience member about some specifics in the Neutron world. And hopefully you can pull down the menu because I don't know if I could read all the details without, you know, missing a detail, but... Yeah, I definitely, I see that question and they were all around the specific V6 apps. Some of these, I mean, Andrew, if you could pull it up, too, and if you know some of these, I'm not sure I know 100%. The Horizon support, I'm not 100% sure I'm not. So this is asking about Horizon dashboard support for V6 provisioning, DHCP V6 stateless provisioning. It's possible that that may have lagged a bit. So I'll have to go... I mean, our end users are able to add V6 addresses into the security groups and view them in Horizon today. Okay, so that's definitely really good as well. Actually, Andrew, you actually know the answers to some of these as well. Yeah, I know that one and two, I think, from a security group in Horizon dashboard, I'm pretty sure that's working right now in the upstream. Yeah. So number three, the DNS mask enhancement service server, that could not make it, I believe, right? That's because I think we need the RAVVD support. Yeah. Yes, that one did not make it. But now the functionality is handled by RAVVD, right? Correct. Yeah. And scalability numbers, that I'm not 100% sure on either. I'd have to look that up. So some of these things that are more specific like this, maybe take them offline or allow people to reach out that. Yeah, I mean, I don't have the exact number, but we are running a pretty large quantity of V6 on the infrastructure. And we can get stats later. And we do do everything dual stack. We're only doing dual stack right now. So dual stack does work. Good. Well, that was from a very large cloud provider that's deploying IPv6. So thank you to whoever that anonymous person is, because we love big time cloud providers. And we'll be hearing from a lot of those at our open stack summit. And I wanted to hear from Andrew and Kyle kind of what you're looking forward to in the Paris summit. Is there specific sessions or topics that you think are going to be really critical, really kind of looking forward to Kilo, I guess, which is what we plan in the summits. Maybe I'll start with you, Andrew. Do you have some specific things you think you're looking to get out of that summit and to make sure, you know, make it into the Kilo release? So, you know, I think as open stacks have been maturing, you know, we've been happy with, you know, how things are being able to support larger scale and more stability. And so I think we're starting to look more at these new features that have just landed in our certain mature like Grove and Sahara, and maybe even some of these auxiliary features like Manila and MagnetoDB and whatnot. So our customers are kind of asking for that full suite of services now. And so we're going to have a lot of interest about where things are going to be landing in Kilo across all those, you know, kind of maybe up to stack services a little bit. And we are definitely going to be tracking the NFV discussion as well. Oh, good. Okay, Kyle, what are your thoughts going into the summit planning on Kilo? Yeah, definitely. I think NFV is definitely going to be going to be a hot area. You know, like I was saying earlier, I expected to be a lot of focus around that. On the neutron side, another big area, which is, again, something we've talked about is this whole known network to neutron migration story and how we're going to weigh that out now that we've gotten more input and certainly hope to get more input at the summit from different users and operators around that as well. These are kind of the types of operational things which are more challenging to work on from a developer perspective because we really need more input from operators and users. But they're really important to those operators and users. Another area on the neutron side where we, like I was saying earlier, was this DVR functionality. We're hoping to expand that a bit more in the Kilo timeframe. One of the areas, like right now it requires OVF, the virtual switch on the edge. There's been some talk of looking at supporting Linux bridge for that functionality as well. So these are some of the areas that I hope to be and the team really can discuss in pairs. Okay, thanks. So one of the questions from the audience was about security and just wanting to kind of get a general sense for how, I guess, we as a community and through the OpenSec releases are thinking about security. You know, maybe Andrew, since you're running in production and are thinking a lot about security, running these mission-critical apps. This wasn't a very specific question, but I think if you just have some general thoughts around how you approach security as an OpenSec user, that might be useful for the audience. Sure. So, I mean, security has been part of the paradigm shift as we move to cloud for us. So, you know, we heavily leverage security groups. We love what we can do in security groups and that we can enable the user to manage a lot of that type of stuff. What we're doing now is spending a lot more time looking at additional tooling for both auditing and reporting around the security. But the fact that we now are living in this standardized infrastructure world with APIs available and the data available gives us an extensible platform to kind of manage all that and create a unified picture of what our security looks like that was actually pretty difficult for us to do before. And I think that, you know, enables our users so previously kind of our security model was ticket-driven and now we've enabled this via, hey, we can manage security via an API or a web portal and that kind of, well, does place more trust in the end-user that flexibility is also a huge win for us. And then the additional visibility, I think more than makes up for the fact that we're replacing more trust there. Okay, great. I think we just have a few minutes left. If there are any other questions, please drop them into the question box. We are definitely excited about the next phase of OpenStack. I think we'll see more and more users talking at summits and the ops meetups and really happy that Andrew is able to join us today. You know, one of the questions that we often get are kind of, you know, what are your business drivers for using OpenStack? You know, what is the actual underlying result you're trying to get from a business perspective? And I don't know, Andrew, if I can put you on the spot there. But I think that's just something we hear all the time and would be curious to hear your thoughts on that. Sure. I think there were a few things that really kind of drove us to look at OpenStack and at Private Cloud. One is we wanted to place infrastructure close to our customers. So we actually placed data centers out deep in our network so that we can provide, you know, lower latency and high bandwidth apps a place to live close to our customers. And that's something that, you know, we weren't able to do on Public Cloud. And then when we started to evaluate platforms, finding an open source platform that we can collaborate on, that we can do things that are critical to our business and can contribute back and be part of that community was a huge win for us. Also kind of the shift to the Cloud paradigm where, you know, we want our apps to think more in the cattle versus the pet mentality and also have infrastructure that they can deploy via self-service or via API. Those were kind of all drivers for us in trying to enable this platform and this environment for our developers to be able to push things out quickly and also have something that they can build upon and deliver, you know, innovative, reliable apps. Great, thank you. Well, we've just got a few minutes left, so I wanted to ask Kyle if you had any final thoughts on OpenStack Juno before we wrap up the webinar today. I guess my final thoughts would be this was my first cycle as a PTL. So the experience has actually been incredibly positive and very exciting actually. The team of people that kind of worked behind the scenes to make these releases happen is really impressive. It's a team of people that are global across the whole world and it's amazing what happens behind the scenes to make these releases happen. And, you know, I thought I'd just give one shout out to our release manager, you know, engineering director at the OpenStack Foundation, Tiri. I mean, he does a great job making sure things are wrangled together and, you know, he definitely deserves a shout out for all the great work he does to make these releases happen. Yeah, thank you for saying that. I think, you know, Tiri Perez is the release manager if you don't know him. He's an amazing amount of work. I was really tempted to ask him to join the webinar, but, you know, he has already done herculean efforts to get, you know, the biggest, most innovative release we've ever had out the door. So I thought I'd spare him, you know, at least one little chunk of time. But thanks again to everybody that worked on OpenStack and including the infrastructure team, which is a big part of what makes OpenStack happen. And for everybody's knowledge here as we wrap up, this webinar will be recorded and put online shortly if you want to go back and look at it or share it. And I put the Twitter handles in the live audience messaging box down below if you want to follow our speakers today. So thanks again, and I hope everybody has a good time with OpenStack Juno. Thank you, Mark. Yeah, thank you.


Welcome to Monet Café, Artistic Friends and Visitors. I'm artist Susan Jenkins, and I hope you'll enjoy this presentation on drawing and painting trees the Fibonacci way. Hello, and welcome to Monet Café. I'm artist Susan Jenkins, and today I'm bringing you a special request video. One of my patrons, hi Andrea, had a request for me to slow down a technique I recently did on drawing trees and tree branches with a Pressure technique that I used and I thought this is an excellent opportunity For me to teach on something else that I've been wanting to bring to you guys for a while Has to do with how trees grow and the Fibonacci sequence and if you've never heard of that term before I have another whole video on it where I talk about the Fibonacci sequence and the golden ratio it's kind of the same thing and Also, too, I'll try to remember to put a little clickable link up at the top so you can refer to that later But I am always fascinated as an artist. I don't want to just paint. I I always say I love to know why things work The way they work. So I I am and I know if you're an artist. We are students of nature I love the way math and science work with art. So that's what I'm going to do today I'm going to share for Andrea the technique of Using pressure to create a more gestural quality for drawing trees and tree branches But I'm also going to share how you can understand more about the growth of trees Which will make your art even better. Oh and also once again I'm wearing one of the love and faith t-shirts and I love this company I love the hopeful messages and I always have a clickable link in the description sections If you see me wearing one of these t-shirts with a 20% off coupon code, so check it out They have all kinds of great t-shirts First I will go ahead and demonstrate the technique that was also in another video of mine on 12 different techniques for pastel painting once again I'll try to put a clickable link there one of them had to do with Pressure and I find that I use this technique often when I want things to look gestural And it just looks so much more artistic. I think so. Let me since we're doing trees Let me just grab kind of a well I'll grab this nice kind of burgundy purplish color in this demonstration. I'm just using my set that I use often It's unison 120 half-stick set. It's a great set for beginners Sorry for my easel shaking and I'm also using just a regular piece of drawing paper But I'm very quickly right here just showing you how We can use these gestural Strokes that vary in pressure and also kind of a twisting motion To change the width of the branches. So once you get the hang of it, it's really Easy, you know, but it's like anything you have to practice it Now join me as I show you some tips on what to do and what not to do In this example, I will describe a bit more about what not to do. We have a tendency with trees to Make things a bit too curvy or rounded So I'm I'm going to talk about the pressure technique and the angular technique kind of at the same time So first let's just uh, and there's a difference between painting and drawing. So I'm first just going to kind of draw a tree with Um, kind of I have to force myself To do it non-pressured Um, because I have such a tendency and to do it curvy because I have a tendency not to do it that way All right. So here we're getting a tree going And I'm kind of whoops. I'm kind of just drawing it in and I'm Trying to purposely create curvy lines. Okay, rather than Angular lines and notice my pressure. That's one of the points of this Is all about the same All right. So this is kind of how we don't want to draw a tree. You get the idea I'm trying really hard To make curvy curvy lines It's tough, you know, it's tough to do it the right way when you haven't done it before And it's kind of tough sometimes to do it the wrong way when you've been doing it the other way I'm not saying my way is right, but it's just a technique. All right So now that's more of a tree kind of drawn in with some curvy lines And we're going to get to the Fibonacci sequence later. I I don't I get kind of close with it, but I'll you'll know more about what I mean by that pretty soon All right. So now for this other tree. Let me give you an example. Let me write here. This one had Pressure consistent pressure Okay, so that's what we don't want to do All right So now for this next one. I'm going to vary the pressure and I'm going to have more angular Strokes so on this one rather than drawing it in this is more of an example of drawing And with pastels a questions often ask us why is pastel painting considered painting when it's Like a dry medium, you know, like pastel pencils or or charcoal or whatever And it really has to do with the coverage and the way that we use the tool So when you use pastels more to cover your surface more Rather than just sketching or drawing your painting So we often use the sides of the pastel. So this is where My technique that I used in my last video of Varying the pressure is going to come in. So notice with this tree I'm not only going to vary the pressure. I'm going to be pushing hard and letting up Pushing hard and letting up. I'm also going to be using angular strokes Rather than Curvy strokes what I had a hard time actually even doing here Okay, but it does it really does make a difference. So I'm going to use the side of the pastel here I'm going to come up kind of like for the base of the tree with a decent pressure. I'm going to kind of angle I'm releasing pressure Angling again And then there's usually always a main part of the tree trunk and then one that kind of branches off and I'm also using um The twisting technique you see how I'm kind of twisting the pastel And I'm releasing pressure And then I'll take one up here like this I'm twisting it to get different widths of the Of the pastel the whole width was right here. So by twisting it. I can vary the different widths Now I want to again get more angular strokes rather than Um rounded strokes. So I got a kitty cat at my feet right now scratching my foot So you can probably see pretty quickly Um the difference in the two also when we get up to the upper branches is when we can really start doing That pressure technique it also works quite well for grasses. I'll do a few grasses. Okay, so notice how I'm kind of angling things And varying my pressure and twisting. All right, so there's definitely a difference of Pressure, let me write that one down real quick. This one's going to be very pressure I'm sorry if my shoulders getting in the way And angular Okay, so I realized this one is wrong Now I'm gonna try to reach around my camera a little bit and show you the same thing kind of works with grasses Let me um, let me Bring it down just a bit here So let's do the wrong example here. I'm just going to get kind of a Well, let me get let me get kind of some darks down. I can't help it. I'm going to get like some dark roots down here I'll do the same thing in both examples This is like um, like the deepest parts of the grasses. Okay Now what what I'm going to do is I'm going to do the wrong technique over here Let me just get a green that you can see pretty good Probably like this one and I see people doing grasses like this. Have you ever seen that before? Really keeping all of the blades of grasses the same pressure And the same width, um, I could have put varying widths up here, but I kind of did that the both I'm going to talk about the Fibonacci sequence in a minute. And um, so it's the same pressure the same width And the same little curvy Curvy motions, you know, and that just is not the way that grass grows So my same technique that I used Over here is going to help with the grasses. So let's watch this technique I'll try to get the same color that I used what I'm going to do is I'm in an awkward position here I'm going to vary the pressure and I'm going to do more angled strokes and maybe some twisting And now I can actually by some twisting I can make kind of some Thicker blades of grasses too. You see that twisting effect there? And you can do the same thing with the trees and you see all of a sudden how that just looks so much more artistic And I'm angling my directions more Skipping it along. There's another technique that you can do too that I like Let me see if I can get a really light one so you can see it's called rolling If you have the advantage, this is all in my last video If you have the advantage of having a round pastel See how I'm varying the pressure. You see how I got lighter pressure back there But if you have a round pastel, you might as well take advantage of Of doing the rolling technique a little bit there. Okay And uh, also too, I find that with grasses I didn't mean to make this about grasses as well. I find people including myself I've gotten better at this. We often spell things out way too much with grasses Let's say in this example down here. We had some grasses down on the ground And the same thing over here again, I'm just giving them some ground to rest upon and In the foreground it's usually darker And the grasses are usually taller in the foreground But let's say that in this one, let me do it where we're going to spell out all these really taller grasses here We've got some grass growing here And now we've got some gradually they're going to get smaller and shorter in the distance a little bit lighter in value And they start changing from horizontal strokes. I'm sorry vertical strokes to horizontal strokes Let me get it kind of a neutral and they'll also get that's another video I have that is uh Five ways to create depth in your artwork things start getting more horizontal and flat in the distance, okay? But my point about the grasses is that often We spell things out too much. We might have a tendency to draw all these little grasses See same pressure really boring boring boring and then um, oh, we know these are smaller So let's make them all smaller because it's in the distance We've got more grasses here all very patterned and and boring So that's way too much information. That's my new phrase. I've been using all the i Don't be a victim of tmi too much information in your artwork. So I'm going to come over on this side I'm going to show you a little bit of the difference I'm going to get a little bit more Let's say we got some uh deep grasses right down in here All right, what we can do is we can just give a hint of some of these grasses here They don't we let's say we got some really we're down in the grass our eye level is down here and we've got some Some grasses growing up like this. You might get a few of them that you see I'm varying the pressure I'm giving a little bit more angular strokes here. All right, so that is definitely not as spelled out right here Now we can go and change up The background here Getting a little further in the distance and we can do the same thing. We can just give maybe some hints of some around the tree Very their direction vary the pressure. Maybe do a little bit of the twisting And but we can do big also you could add some things in here that might not be grasses might be a different plant And then the same thing in the background. I know I'm working again on just uh on paper, but um You can probably get the idea All right now that we've talked a little bit about the technique of drawing trees or grasses or things with more of a varying pressure Perhaps a little bit of a twisting and angular direction and technique Let's talk about how to know where trees split and divide Have you ever done that try to draw a tree and you're like, well, where would this branch be or Where do if you're doing it from imagination? And a lot of times we might be working from a reference photo where we want to add something So it's good to know these rules. And so I find it's a lot easier to understand Drawing trees the Fibonacci way to do it on a piece of ruled paper the first time So I'm going to bring you guys over and I'm going to work it out and show you how Mathematically it works. It's really cool Here are a few examples of some paintings I tried to find some that haven't been put in the clear bags yet where the grasses are Hopefully not overworked or over detailed. This one is really all about value and shape and direction I mean, there's barely any blades of grass. It's mostly very wide strokes in it and it still gives the illusion of grasses This one also has grasses that vary in pressure and direction and shape And you still have the mental Impression of of grasses Also, this one here hardly has a pardon the glare Hardly has any grasses even drawn. They're more just like chunky shapes Once again, still the illusion of grasses same here with this one very little Individual strokes of grasses in this but again still get that more of the suggestive quality that I think many people like and You know, that's kind of my goal too. I like to suggest things rather than spell them out Also, too, this is one that I recently did out in my parents field a plein air painting I'll have a video on this one as well. But notice too, no individual blades of grasses Even I got crazy. This one's about dramatic color. That's what the video will be about But um, you know, I just suggested things and I did still very pressure Sometimes I did twist my pastel a little bit more. So hopefully that helps you a little bit with that But now let's get to that Fibonacci pattern of how trees grow All right a quick little recap on the Fibonacci sequence and again, I encourage you to watch that video It has so much interesting information as to how it came about and a little bit of the history into it, but it is a formula that fairly accurately represents how nature behaves and By nature it's things from the way tree branches grow once which I will demonstrate here the way flower petals grow Um, and it often has to do with a spiral if you've seen the Nautilus shell That's a breakdown mathematically of how the Fibonacci sequence and the golden ratio Works, it's in everything again. I'm recapping that video. It's so so neat But um, if you just want to know the numbers and that's what we'll need to know for this example The way they work is you you just start with two numbers. That's the best Way to describe how to begin So rather than starting most people start the Fibonacci numbers with one and I always find it's a little confusing It's easier to me if you start with zero. So what are the first two numbers zero and one? Okay, now all we're going to do is add those two numbers together for the next number in the sequence So that's pretty easy, right zero plus one is one The next number in the sequence one plus one is two The next number would be two plus one. Okay, so Uh, you get the idea. We just keep going on and on and on And and it goes on forever. All right, so I'll just I'll go to here. I'll go up to 21 So that's generally how it works. You add the two numbers and you get the next number Well, the way this pattern is reflected in a tree and its growth now. This is a generality. Okay Every tree does not grow exactly this way, but it's a general rule of thumb and it's going to help you understand Just like when I was working with the pastel I didn't focus on it too much because I was talking and teaching But once you learn this you can kind of accurately represent the way the tree grows with its branches So here we go And you may have to do this a couple of times For it to make sense the way I like to think of it. I'm going to zoom in even more We'll start at the bottom here Is we're going to use these numbers. Okay, we're going to start with the we can't do zero, right? So we're going to start with the one and the one that's going to be our trunk of our tree So let's start down here. We're going to have I would draw a square so you could see but we're going to start the trunk It's going to start here. I don't want to start too wide or I'll run off the paper So let's start the trunk right here. We filled in One level. Okay, so we need to do another One All right, so let's do there's the next one. Okay Now we know the next number in the sequence is two So we've got to divide this into two on the third level. Okay, we've got One one and now we got to break this guy up So we're just going to put a little v right here at the bottom of this third level Now also with trees you may have noticed usually there is a primary branch and a secondary branch One is going to be more like the main trunk. So let's make this one more like the main trunk So I'm actually and these don't have to all be straight. I'm going to actually kind of make this one a little thicker Okay, this one's going to be my secondary branch. All right, so we've got one one And one two you see that one trunk one trunk Two branches or two divisions of the trunk. All right zero would be down here All right, so now we're going to take one of these guys We alternate. Okay. One of them is going to what's the next number? The next number is three So let's take this main trunk one and we're going to split it into two So I'm going to do a v a little v. We're splitting it. Okay right here This one's not going to get split into two. Okay, because we're going to end up with three over here So this one will just kind of Bring over a little bit. So now we're taking this one up and we're splitting it into two So now guess what we have on this level one branch two branch three bank branches All right, so the next one is going to have I'm going to have to curve my numbers around here The next one is going to have how many let's look back up here It's going to have five So what we're going to do is we already made this one the long one. Okay, it didn't get a break yet So this one in the next level and by the way This happens differently based on the variety of tree live oak trees. Everybody knows how they go so wide So let's make this branch like more like a live oak branch. Let's bring it. We're going to put our v way out here Okay, that's kind of far So what I'm going to do is I'm going to bring this branch over here like that And then I'm going to go like this like that. Okay And this one here now, we've got two trunks again One's going to break into a v and one is not Let's make this one break into a v since it's a live oak tree way over here I probably should have held off on my tree variety descriptions and Done it Just real simply. Okay. So now we broke that one off now this one We are not going to break it into two. Let's just bring this one up like that. Okay So now what do we have on this next level? One two Three four five. Look at that. Isn't that cool? All right, so now let's look again at this one We've got two whenever you have two like a v one's going to go into another v and one is not So let's make this one go into another v Okay, so we're going to bring it up And let this one won't okay. So let's bring this one just kind of Up here like this. All right Now let's this one is um did not get a v before you see that So let's give it a v kind of like right here I'm kind of bending my tree branches probably too much. All right, same thing here this one We got it's got two so we got to choose which one's going to get the v I'll take the outside one again. So we're going to go out here And this one will not get the v. Okay Now once again, let's go back over here. This one has two pick one and give it the v. Let's do this one The split I should say I probably shouldn't call it a v. This one's not going to get it. Okay. We're just going to go up here All right, this one did not get a split. So let's give it a split. Let's bring it over here All right, so we're getting somewhere this one. What's what's happening here? We've got two So what do we have to do? We have to pick one Um, I think I want a tree that's got a big hole in the middle here So I'm going to pick this one to have the v over here And this one not to okay Over here. We've got it didn't have a v at all. So let's give it a v And we're going to just bring it up over here You can bend them, you know, wherever you put the v you might have to bend your your branches to suit that So once again, I'm kind of making more of a live oak tree So let's do one. Oh, I missed a level. I'm trying to get them all to the level before I move on This one. What's happening here? We've got a v. We've got two a split. So we got to pick one to To have the next v and one to not have the next v. So again, let's pick this one out here I'm always putting the v's right at the line too. Just so you know, so this one's going to be reaching out again Notice too, they're all getting smaller and this one's just going to reach up. All right Let's do one more level. Okay. So over here We have One that did not have the v right here.  We'll bring it up here This one right here. It's got a v. We're gonna pick one I'll pick one. I'll do one right here We'll make it have a v And this one will not Uh, this one just has a v because it it doesn't have two. So we just give it a v And again, I'm bending it. You can bend the branches to wherever the split is. This has two. Whoops This one has two. So what do we do? We pick one side or the other to make it go to that split and the other one won't have a split So I'm going to pick this side. I'm going to go to this split And this one I won't even have a split Right here. What do we have? We have two So one of them's going to have a split and one of them won't let's give a little split here And this one won't have a split This one has one We've got to give it a split. You don't have a choice. Okay So if it if it hasn't had a split previously, you just Put the split on the next level. This one has two We got to pick one that has a split and one that doesn't I'm going to do the same thing I've done before And we'll do this now. We're kind of running out of room here. Um But you see how the tree is growing now. I've seen these fibonacci trees done before just growing straight up people just um Do them kind of But I think it's interesting that we can pick and choose Where we make the splits now that you don't want to have to paint that way all the time, right? You you really don't want to have to stop and think But if you practice these and you think about how they work before you know it you kind of start to naturally do it So I'm going to kind of use my side of my pastel a little bit of my it's a wide pastel or long pastel So I don't want to make my tree that wide So what I'm going to lift up on it a little bit and just press on one side. So there's our base We know one side's going to kind of split and we're going to split here. Okay, that's going to be my primary side Okay, then we know from this split. We're going to have Um a v going somewhere and one not. Okay, so we've got one of them going here In a little v and one of them won't this one is the long one. It's going to just do that Okay, then we just we kind of keep going. I'm just going to kind of keep keep doing it from here. Okay, just But then the more you do it the more you realize you can kind of Just get a little creative. Nobody's going to come in and count your Fibonacci branches. Okay But one thing is true is that if a tree isn't somewhat accurate It's going to look your your art will look amateurish. Okay So the more that you do this the better you'll get I hope you found that educational and I hope it will expand your horizons when it comes to drawing and painting trees And once again patrons, this is your homework assignment You can do these Fibonacci trees and also try to do some that are with some pastel or Pencil whatever but do the the pressure technique and give it some gestural quality Currently available in my Etsy shop is my book that I wrote and illustrated called the mountain queen With the holidays quickly approaching I thought it might be neat to offer it as a stocking stuffer gift for a child or grandchild in your life And I call it the eternal love story It's only 2499 in my Etsy shop and it is an autographed copy You can personalize it too when you visit the Etsy shop if you'd like me to mention anyone's name So I just wanted to share that and it might make the perfect Christmas gift I love it when you guys make comments on these videos and let me know if this is what you like So please do that like this video comment Subscribe become a patron if you'd like it really does help this channel and as always happy painting


Your commentator is Ray Henley. Great events in the Pacific, race into history. A vast armada of troopships, guarded by the largest naval striking force ever assembled, sails to the attack. Destination, the Marshall Islands. For 25 consecutive days, the marshals are ripped by army liberators operating from Tarleville, softening up jet defenses and destroying landing strips. Black tracers reach up like flaming fingers to seize the bomber, but fail to get the rain. Jet planes on the ground are hammered into wreckage on the smashed runway. The roar of tons of high explosives from the sky is only the prelude to the mighty symphony of destruction to come. Until the Navy goes into action. For 28 hours, the jets are hammered by the most concentrated naval pounding in history. An estimated 14,000 tons of shells are poured on Quajolaine, Roy and Namur. Battleships and cruisers move up to within a few thousand yards and let the jets happen. Empty shell cases, the work of just one gun crew. Now the word is passed to man the landing boat, while the Navy continues a crushing bombardment. Veterans of jet-smashing victories in the Solomon and Army veterans of the storming of Aftu shove off from transport. 30,000 strong determined to shorten the road to Tokyo. A lot of steel from the fleet, landing boats manned by Coast Guardsmen, begin to assemble for the storming of the beaches. Tossed by the long Pacific swell, the boats maneuver for positions as the barrage continues. They've been fortifying the marshals for 20 years and in 20 hours, the Navy's big guns rip apart everything the Army bombers missed. It's a grim show, and some of it is bombing by carrier planes dominating the skies. Now the landing boats are turning into the beach with leathernecks to the fourth division. Soon sending the familiar word, the Marines have landed and have the situation well in hand. But there are jets still ready to give battle as snipers bullets whine over the beachhead. Inland, all over the shell smashed island, enemy profits must be cleaned up. Men of the 7th Army Division hit the beach on Quajolaine with a cool discipline of a practice maneuver. Time table schedule, landing ships and more troops come in. Missing troops are warned by a sniper's bullet, put up a futile resistance. But once they are located, the war is soon over for them. These men sight a sniper in a train. Honorable ancestor tries to escape by swimming across the lagoon. And they are kept underwater, permanent. Suddenly mortar goes into action. Organized resistance remains now. But isolated groups of survivors make a desperate effort to fight on as the Americans mop up.  Sometimes it's necessary to use TNT persuaders, and they are very effective. Our men on the firing line get a battle action picture as fighting flares up in another sector. Once palm hooded and lush green, the place is withered and torn by the smashing bombardment. Hidden in slit trenches and the shattered ruins of concrete and steel pill boxes, frantic japs continue to give battle to the advancing Yanks. Hitting place is reduced to rubble and ashes. The enemy is stunned by the terrific force of an attack that sends a chill through every extended artery of the uncivilized nation, all the way with Blackheart and Tokyo. Passed to take prisoners. And commands in the Japanese language are given to a loudspeaker to a group of the enemy hidden in a blasted pill box. It's significant that here in the Marshall, the supposedly fatalistic Jap soldiers jump for the chance to live when given. They are ordered to come out and out they come. Prisoners are stunned and dazed by the relentless land sea and skyfire to which they were exposed. These Yanks are taking no chances with Jap treachery. They main business. But the sons of the setting sun are treated like human beings in spite of their black record. An intelligent officer questions prisoners. They are tagged then transferred to ships offshore. More than 8,000 of the Makato's men are wiped out by the invasion of the Marshalls. Conquered so swiftly that the whole Japanese defense strategy in the vital Central Pacific area collapses. The cost of victory? 1,100 Americans are wounded and 286 killed. 1,000 Japs are taken prisoner. The largest number to surrender in any campaign up to this time. As speedily as possible, injured Americans are taken to hospital ships offshore. Destruction tell eloquently why the Jap Air Force never got into action here. The bare skeleton of a hangar, wrecked zeros on the ground, devastation. They all tell of the offensive might that swiftly conquers the first Japanese territory invaded. But somehow a supply of Jap beer escapes destruction. Headquarters of the Japanese command takes a terrific beating. Comrades pay tribute to those who have made the supreme sacrifice. The smoke of battle lifts to reveal our flag flying above the Marshalls. Admiral Chester Nimitz, supreme naval commander in the Pacific, salutes a great victory that smashes closer to the heart of Japan when the Yanks invades the Marshalls.


Hey guys Dylan Schumacher with Citadel Defense and today we are reviewing leadership and training for the fight by Mr.. Paul how US Army retired Mastery gunnery sergeant MSG. I think that's what that stands for don't know my military lingo so This book is probably one of the top five books. I have read in this Sphere since I've been doing this kind of this tactical book review project the main reason for that is That it applies specifically to what I do being teaching classes Which may not of course be specifically to what you do However, that being said the first half of the book is applicable to anyone and I would highly recommend it I will come out later with a list of the top five books that you should read in a specific order And this book is already number five on that list. It's that important The first half of the book deals with the leadership and that's why it applies to anybody and just about any circumstance now The leadership he deals with here is the leadership in regards to combat right He wrote this book when he Based on his experiences. He's been teaching guns for a long time And when he talks about leadership he talks about it specifically within the context of combat and Team leaders team leaders are groups of four guys in the military four to six depending on What branch of the military year? So this book is very helpful And I would recommend the first half to anybody when you get to the second half and he starts to address Teaching people how to shoot specifically that may or may not be applicable to your situation Even if you take people out at times to just teach them how to shoot for fun or you take some friends out Or you take your girlfriend out the back half of this book could be helpful to you although for most of us Let's be honest. It probably won't be that applicable. The first half However is again applicable to everybody all the time. I Highly recommend you get this book. I highly recommend you read it at least the first half It will make you a better shooter. It will set your mindset straight and it will How do I want to say this? It will help you understand what leadership and initiative taking is and why that wins fights and why that wins wars Leadership and training for the fight by Paul Howe get it read it. Thank me later Do brave deeds and endure


Week nine, and it's back at home against Dub Bears. Chicago celebrated a dynasty on the hard courts back in the 90s. But this ain't basketball.  The Titans have their eyes on the prize. Touchdown, Titan, intercepted on a deflection. But we're only halfway there. Here at the midway point of the season, let's see what we're made of. Windy City comes to Music City. It's going to take more than a gust of wind to take down Tennessee Tung. At Nissan Stadium, the Titans get it done again.


QuickBooks Online 2024. Make loan payments. Get ready because we're going to Bookkeeping Cloud 9 with QuickBooks Online 2024. Here we are in our Get Great Guitars 2024 QuickBooks Online sample company file. We set up in a prior presentation opening up the major financial statement reports as we do every time. Reports on the left hand side in the favorites right click on that balance sheet open link in a new tab right click in the profit and loss to open link in a new tab one more time on the trial balance open link in a new tab. Let's tab to the right close up the hamburger and change the range up top we're going from 010124 tab 013124 tab we will run it to refresh it and then tab to the right repeat the process hamburger needs to be closed opening up the range we're going from 010124 tab 013124 tab refreshing again and then we'll tab to the right repeat the process one more time ultra vase 010124 tab 013124 tab and run it to refresh it again let's go back to the balance sheet tab in a prior presentation we talked about the loan balance so let's go down to the loan down here in our liabilities we took out a loan here it is in the 72,000 now we're going to imagine that payments are happening on the loan and how are we going to deal with those payments so notice the loan can be deceptively complex to be dealing with because you would think it would be an easy thing to pay off the loan if we have an installment loan that is paid monthly similar to what we might have if we have a loan for a mortgage or something you just make the same payment it's the same amount why can't I just basically use the bank feeds to automate the transaction as the electronic transfers happen out of my checking account I should be able to see them coming through the bank feeds and simply record an expense type of form which would look like this possibly with the help and use of the bank feeds and the other side go into some other account like the loan balance account instead of an expense account because we're paying down the loan well you could do that but the problem is that the loan bank well there's multiple problems with the loans that could be deceptively simple and subtle and one is that there's going to be interest involved so now we have to deal with the interest how are we going to deal with the interest what is interest interest is basically the rent on the purchasing power of the money so when we pay down the loan we're not just going to be reducing the principal we also have to pay in essence the rent that just goes poof and the air just like the rent for the office building that we are in once we use the office building we pay the rent and poof it's gone and that's the way it is so that so you might say well that's still not an issue really because I can just still use the the same transaction and memorize the transaction as we make the payments because then I'll just include three accounts instead of two accounts and I could still memorize that that's not too difficult but there's still a glitch in the system and that is that as we saw with our amortization table we built last time although the payment is the same the breakout of the interest and the principal will differ with each payment so you can't just automate the process very easily unless you try to record all the transactions kind of in advance and and let them record and then tell them to record periodically or something like that right you can't just you can't just memorize the bank fee transaction in other words so how do you deal with that well one way you could deal with that is you could say I'm going to separate the duties me on the bookkeeping side and then my CPA or tax preparer on the adjusting entry side so I could say look I'm just going to automate my books because I want to make things as fast and easy and automated as possible therefore I'm going to ignore the interest entirely and simply wait till it clears the bank and then record the reduction to cash and the other side going directly to the loan payable account and then at the end of the year I will ask my CPA or accountant to then adjust this for my client or for me given us the amortization schedule and then they record the interest periodically at the end of the month or a year possibly just the year if it's a small business they need this for taxes or external reporting so that it's correct for tax preparation that could actually work fairly well because then again that's the easiest thing to do you could fully automate the system but you have to have a CPA firm or accounting firm that knows how to make an amortization table and do adjusting entries to break out the interest and make the loan balance balance to what's on the amortization schedule now another issue that comes up which we'll talk more about in the adjusting entries process is that you might have multiple loans so remember if you have multiple loans then you it's easiest to have a parent loan account and then make sub accounts per loan otherwise you have all your loans in one place which is fine for external reporting but it's a little bit more difficult to tie in that loan balance to each of the amortization tables so that's why I would recommend making a new loan for each each uh a new loan account for each type of loan and some businesses have a lot of loans like construction businesses for example often have a lot of loans because they're financing the equipment as part of their business so I would I would do that and then the other issue that comes up is breaking out the short term and long term portion of the loan so if we if we think about our amortization table that we have a five year loan so the amount in one year then you would think would be short term because it's due within a year that's the definition of a current liability and the stuff that's after a year would be long term but if I break that out every time I make a payment it's going to mess things up because then I have to make an adjustment for the short term and long term portion which will change every time I make a payment so again normally what the process would be would be I'm just going to do the the payment transactions in one account and rely on my CPA firmer tax preparer to break out the long term and short term portion if necessary at year end in order to do whatever I need to do such as tax preparation where it might not be necessary and external reporting uh type type of purposes and then have them fix it after that doing a reversing entry putting it back into one account because the one account system is the easiest system to use for the internal bookkeeping side of things so that's a standard periodic kind of adjusting entry although it's not a classic adjusting entry we'll talk more about that in the adjusting entries section right now what we want to do is make a payment according to our amortization schedule so we're going to use the method of making the amortization schedule and then creating a payment in accordance with the amortization schedule so that our loan balance will always match what's on the amortization table so we imagine last time this was our loan this is the amortization table we put together so five year loan which means there's 60 payments the rate was five percent the rate per month then is that which is just a five percent divided by 12 and then this is the payments that we're going to make every month we made our amortization table then this is the first payment that we're going to make this is the second payment so here's the payment here's the amount of interest charged this will be the loan reduction and or principal reduction whatever you want to call it and this will be the loan or principal balance after that first payment so that's what we'll do first we'll record one at the beginning of the month and then one at the end of