Mike's on. Hello, everybody. Thanks for joining us. I'm Jesse Proudman, IBM Distinguished Engineer and CTO of what's now called Bluemix Private Cloud and introducing Animesh. I'm Animesh. I'm an architect for IBM Bluemix platform as a service. So we're here to talk to you today about two of the IBM offerings, but not about the offerings themselves, specifically about what we've learned through the operations of both Bluemix, which is Bluemix platform as a service, the Cloud Foundry installation, and the Bluemix Private Cloud, which used to be the blue box OpenStack as a service offering. At the OpenStack Summit in Austin, Mark Collier mentioned some of the stacks in terms of the workloads which are running on OpenStack. And followed by Kubernetes, Cloud Foundry is the second most popular workload, which is right now deployed on top of OpenStack. So what is Cloud Foundry for some of those? Maybe one of the questions. How many here have used Cloud Foundry or have heard about Cloud Foundry? Quite a few. How many people have deployed Cloud Foundry? So around, I would say, 30% to 40% of the room. So for those of you who have not used Cloud Foundry, Cloud Foundry is the de facto platform as a service. Just like OpenStack is the 100% open source component for IAS, Cloud Foundry is similar for the platform as a service. You take your code to Cloud Foundry.  And as you deploy your application, it will provision those services in the background, bind it to your application, and bring it up and running within minutes. It was established. The foundation was established in December of 2014 under the Linux Foundation umbrella. And just like OpenStack, it has a very strong and vibrant community. More than 60-plus member companies are currently driving the Cloud Foundry foundation. So names like IBM, Cisco, HP, Privately, Docker, Huawei, Swisscom, they are all participating and deploying their own Cloud Foundry production clouds. I think the interesting thing about the Cloud Foundry foundation and its membership is that you've got a lot of actual users of the offering as part of the foundation, whereas OpenStack gets a lot more heavily weighted towards the vendors. So how do we actually deploy Cloud Foundry on OpenStack? We use a tool called Bosch. Bosch is a release deployment as well as lifecycle management tool for Cloud Foundry. It has Cloud Provider interfaces or what we use the term internally, CPIs, which bound Cloud Foundry to different IAS infrastructures. So for example, you can take Cloud Foundry, deploy it on OpenStack, AWS, Google's Cloud, as well as VMware. Now, these Cloud Provider interface methods, they actually use basic OpenStack methods like upload images, provision images, provision volumes, et cetera. How does Bosch work? Bosch actually takes a release, which is a collection of software packages. So for example, MySQL packages, your Cloud Foundry release package, any of the services which you are deploying along with it, it takes all those release packages. And then there is this concept of stem cells or base operating system images. Then there is deployment manifest, which tells Bosch where we are deploying Cloud Foundry, what credentials we are using, what network we are targeting, what is the authorization, authentication information. It takes all that information from deployment manifest and then deploys different VMs and converts it into different Cloud Foundry components on your particular IAS. So here's the first lesson. The learning curve for Bosch, as the 40% of you have deployed OpenStack know, is incredibly steep. And you're learning a whole new set of terminology and a whole new really approach to deployment. And so that's often the first hurdle, is getting folks in the organization comfortable with that new technology. So now let's talk a bit about the problems which we faced while we have been doing Cloud Foundry deployments on OpenStack for now close to two to three years, as well as the survey which we did last year in terms of finding out the hurdles the community is facing. Instability, when we started, definitely OpenStack distributions or the releases which we used to get, they used to be very unstable, as well as there used to be deployments where we have two components from one release. And for example, Cinder and Swift coming from another release. So a combination of these made these OpenStack deployments pretty unstable, as well as led to a lot of API incompatibilities. Also, the plugins which you use, for example, some of the plugins you will use for Neutron, that also leads and changes the API behavior at times. Capacity is one of the things which we have realized. If you don't size it properly, some of the errors which you will get from Cloud Foundry, they will lead you in totally different directions. And you will be debugging things which are not even important at that particular point of time. Network, definitely that's one of the important things. You need to decide, should your management component, should your DEA, should your services, should they collocate, should they be in different networks, et cetera. OpenStack for enterprise software. Now, this is something for anybody who is building a full platform and deploying things other than Cloud Foundry to support. For example, a lot of services which you might be providing, caching, queuing, et cetera, database services. What we found that a lot of enterprise software, it is already mature for VMware.  But for OpenStack, we found a lot of that was lacking. That's one of the hurdles we faced. Other thing which we definitely wanted to do was this Cloud Foundry plus plus what we are deploying. We wanted to do it in a generic way so that we can deploy it on OpenStack on VMware, as well as a software which is our public iOS Cloud. Combine OpenStack and Cloud Foundry usage. Now, more often than not, when you are actually going in enterprises and deploying Cloud Foundry and OpenStack, the users are not only expected to interact with Cloud Foundry. They want to interact with the same OpenStack on which your Cloud Foundry is running. So you need to make sure you are taking measures so that the workload Cloud Foundry is not impacted by the usage of the OpenStack side by side. Cloud Foundry HA. Though Bosch is really good, you can increase the number of components, et cetera, do multiple HA deployments. One of the things which we noticed as we have been doing this is a lot of these databases, et cetera, they are not synced. So if you have a PostgreSQL or a MySQL database under the covers, you have to come up with some additional measures to make sure that if you are doing HA deployment of databases, you are syncing the databases in the background. So from an OpenStack perspective, with these first four, I think one of the things that was particularly interesting from an OpenStack view is that Bosch, and particularly during a Cloud Foundry deployment, really tests the OpenStack API. So it throws a ton of concurrent connections at that API and expects OpenStack to respond very quickly to those requests, as you would expect out of an IaaS. And particularly in earlier versions of OpenStack, a lot of the default configurations would fall over or fail based on that request volume. And so one of the pieces that we had to pay very close attention to you was tuning those settings, because as Anna Mesh mentioned, the error messages that you get during those failures aren't always clear as to what the originating problem is. Proxy or firewalls in customer environments. Now that's something which we learned as we go, we learned it the hard way that 99% of the customers where we are actually deploying Cloud Foundry, they have proxies of firewalls in place, which actually block any outgoing connection. Now for something like Cloud Foundry, which is a collection of the Cloud Foundry releases plus a lot of other software which you need to define to support the services as well as any applications which are being deployed there, they need to reach out. So you need to make sure that you are architecting this in a way so that Cloud Foundry as well as the applications which are falling, they can be deployed in a seamless way. And last but not the least, the constant release cycles, both CF and OpenStack have frequent releases. More so Cloud Foundry, it has very aggressive release schedule every two to three weeks, right? So how do you maintain actually the patches, updates, upgrades, et cetera in a consistent manner? For example, one of the problems we faced was as OpenStack was moving towards Mitaka, Cloud Foundry was moving from micro-bosh to wash in it. And we went through a lot of permutations and combinations and you can only find so many one particular permutation or combination which can stick with that combination because the community has already moved towards Bosh in it which was working on Mitaka. And on that last point, I mean, I think this is one of the key pieces that ultimately led to sort of the decision or focus on this as a service model. So in OpenStack, obviously we have six month release cycle which a lot of organizations find to already be a challenge when then you add on top of that two to three week release cycle of Cloud Foundry, what we often see is organizations just installing a version and leaving it there without ever getting the updates in place. And then when you try to go actually finally do that update, when you're skipping multiple versions, there's a lot of associated pain and headache that gets involved because those upgrades are meant to be done sequentially. And so keeping those environments up to date whether it be a Cloud Foundry or OpenStack becomes really critical, particularly when you're trying to work with both of them in parallel. So from a user experience perspective, this survey comes from the... We did it as part of the community last year, the Cloud Foundry community. Yeah, from the Cloud Foundry community, yeah. And so the question was what is your level of experience with OpenStack for folks using Cloud Foundry on OpenStack? And in this event, most of the users were intermediate or expert users of OpenStack. So they felt like they had a good handle on OpenStack itself. But then what were the pain points that they were experiencing with OpenStack? And many of them, or how much pain I should say, did they have deploying CF on OpenStack? And the large majority had significant issues with that installation. And other thing is that close to 50% of the users have to actually customize their OpenStack for Cloud Foundry deployment. So the thought that you can take a vanilla OpenStack and install and be able to run Cloud Foundry on it, no, that doesn't hold true. There are certain steps you need to make sure that your OpenStack is ready for a Cloud Foundry deployment. If you also see the reason most of the users' experience problem was 70% of them said that the instability of the OpenStack has been one of their issues. And more than 50% of the users said that the initial setup, in terms of getting that initial configuration, right, to get Cloud Foundry on OpenStack, that has been very hard. Most of the users have been on Juno and Kilo at the time we surveyed last year. So one thing which we noticed, typically as OpenStack moves to different releases, most of the enterprise users, you will probably find two releases behind. So they're typically one year running behind the next open-source release, which is coming. And close to 50% of the users run their own OpenStack rather than getting it from a service provider or services support or a managed service. But this problem depicted on the left that enterprises are lagging behind on versions, this by far and large is often one of the biggest challenges with that Cloud Foundry OpenStack compatibility component because Cloud Foundry moves so much faster keeping the environments in sync and the development of Cloud Foundry is done on the latest versions of OpenStack. So keeping that all in sync becomes very key. So with that, let's just briefly talk about our OpenStack and Cloud Foundry offerings. The first one is BlueMix Private Cloud. So we renamed BlueBox this week, BlueMix Private Cloud. It is a OpenStack as a service offering that can be purchased in a dedicated capacity in software or a local capacity in a customer's data center. IBM manages the full lifecycle of the OpenStack installation and its operational capabilities for the user. So the user gets back an API and an SLA. BlueMix, that's our platform as a service offering. There are three deployment models. There is a public BlueMix offering, which is available. Then you have Dedicated, which is essentially you get your own BlueMix on software, which is our public IS Cloud. Or you can get BlueMix in your data centers, which is a private model. Currently on our public platform, we have 1 million plus registered users, 100,000 plus running applications, as well as a catalog of 500 plus services. These include services from our Watson portfolio, a lot of big data services, serverless capabilities, which are provided on top of BlueMix. What essentially is BlueMix? It allows you to build, deploy, and manage your applications while tapping into a large ecosystem of services. Now these services not only come from IBM, but also from third party providers, as well as from the open source.  So there are browser based Eclipse tooling, which we provide where you can code in the cloud, run your CI CD from the cloud. Once you click and save your code, it's directly pulled up and then deployed on top of BlueMix. With that, some of the lessons which we learned, we'll go through them. So the first thing which we should do is test if our OpenStack is fit for a Cloud Foundry deployment. There is a link which I've added here where you can actually go and at least all the manual steps you can take to make sure that OpenStack is currently fit for example, some of the basic things like can you access OpenStack APIs from within an instance? Can you reach out to the internet from within an instance? Can you come back from outside back into the instance? Can you provision and mount to large volume, et cetera? If you don't want to do it manually, as most of us wouldn't want to do it manually, there is a Cloud Foundry incubator project which actually has automated tests which you can run on top of your OpenStack to test if it is fit. It tests all the basic CPI methods like creating a VM, deleting a VM, creating a volume, attaching it, et cetera. But apart from that, it also tests a lot of non-functional characteristics. So it checks your API rate limit. Can you take a large invocation of VMs at once? It tests the versions of the OpenStack projects which are required. They work with this particular Cloud Foundry. It tests all those network connectivitys. Can you go outside from a VM? Can VMs ping each other? Can you come from outside in? So I definitely encourage for anyone who is deploying Cloud Foundry on OpenStack to include this as part of your CI CD validation to ensure that once your OpenStack is getting handed over, it is fit and it can seamlessly take a Cloud Foundry deployment on top of it. As I mentioned, sizing is a great big issue which we faced. So make sure that your sizings are correct. There are some links which I've added there which are public links which give you some sample sizing configurations to get started with Cloud Foundry. As you set your quotas in OpenStack, that's very important. A lot of the number of times we actually get out of quota errors for number of ports, et cetera. And as again, as I said, some of the times the errors which you see from Cloud Foundry are not exactly telling you that this is a quota issue. She will probably be spending three to four days debugging until you come back to this. Also the recommended OpenStack disk flavors, they actually go in the ephemeral rather than the root disk when you create the flavors. So that's something to keep in mind. We recommend around 10 gig of root disk still. Another thing, when we started, a lot of the OpenStack environments which we got, the default scheduler, it actually was configured to pack host one by one. So that means you pack one host machine with the VMs and you move to the second host where we found a lot of failures regarding Cloud Foundry deployment. So make sure you are using a scheduler which actually is distributing the load across so that it can actually take that large number of invocation for the VMs which is coming. And essentially the failures you're seeing there, if it's packing that one host and it's trying to spin up 10 or 12 or 20 VMs all at the same time, you're gonna run into IO contention on that one VM, you're gonna run into timeouts as those VMs take longer and longer to spin up coming back to Bosch. Also you can change the OpenStack settings to configure it for large number of API calls. As Jesse was mentioning, when Bosch actually deploys Cloud Foundry, the whole deployment goes at once. Now, depending on the size of your environment, it could be anywhere between 40 VMs to 200 VMs which you are invoking at once apart from the volumes you are provisioning. So make sure that OpenStack is configured to handle those number of API calls. Avoid name-based security groups, what we have seen that it requires activity which is proportional to the message bus as well as the database updates, they're proportional to the number of VMs you are provisioning. So avoid name-based security groups if you can. If your neutron is configured with VXLAN or JR Eternals, make sure you're using the right M2 settings under the covers. The other thing which we have noticed and we kind of stepped onto it is that one of the environments where we were deploying Cloud Foundry didn't have enough space from the root disk. So the host on which the VMs were landing, they didn't have enough space. So while doing that, we figured out that we can actually configure Bosch and Cloud Foundry to use the block storage instead of the root disk for the VMs. There's a setting in Bosch which you can actually set. So that's very handy in case you are running into environments where you want to take some space from the root disk and some form of your block storage, et cetera, move around. Also, most of the OpenStack environments are set up to get metadata from the HTTP service, but if your OpenStack is configured to use CD DOM instead of the HTTP metadata service, make sure that you tell Bosch by deployment that the OpenStack config is coming from a CD DOM drive. When you deploy Cloud Foundry and Bosch, there's lots of NATs message burst activity which is happening. Actually, sometimes you'll see failure when Bosch is not able to ping certain VMs whether they are up and running. You can actually go into Bosch and change the NATs messaging timeout or ping interval to actually get around it. That's particularly true of the environments where there is heavy load. At times you will see the deployments failing just because it's not being able to ping within a certain time frame. Also, for optimizing the routing and bandwidth, we suggest putting the Cloud Foundry components, the management plane into its own network as well as the DEs and the services that go in their own network. If you are using any supporting services like logging or report generation, make sure that any communication between the VMs which are sending logs as well as the component which is accepting logs is happening over the private network. In some of our environments, the floating IPs or the accessible IPs were used as the target for sending logs. What happens is, it's a round way communication, you're paying twice the cost because the logs are coming from your private network going to the public network, so to say, and then coming back into the private network. Make sure that you are using just one internal network for sending those logs. Some of the common sense things like only open the ports which are needed. If you are providing credentials in the manifest which you have to only provide the tenant credentials instead of the full OpenStack Cloud admin credentials, if your OpenStack is using a self-signed certificate, you can also configure Bosch to tell it what is the self-signed certificate it is using. And then you can, the other thing which we highly recommend is minimizing the number of floating IPs. Conceptually, apart from your incoming device, which if you are using a native CloudFormer deployment, that's HAProxy, but in our case, for example, when we are putting a data power in front or some of the customers when they put an F5 in front, that's the only device which should be on public network. All the CloudFormer fabric components should be on your private network behind the firewall. As we mentioned, the other thing which we noticed when we started doing some of these deployments, almost any customer environment we are encountering, there is a proxy or a firewall which is in place. So in our case, since we take the CloudFormer release and package it, the CloudFormer release itself was not a problem, but a lot of the other supporting packages which we deploy or services which we deploy or runtimes which we deploy, for example, Node.js, they need to reach out to the internet because as the deployment is happening, they are downloading some patches or the latest binaries, et cetera. So we need to make sure that when we are going in a customer environment, we create a list of all these outgoing URLs we are supposed to reach. So we have now a standard set of URLs. It has been minimized a lot, now only just six URLs which we need, which we hand over to the customer to make sure that they are allowed in their proxy or the firewall configuration. Some other customers on the other hand, they become a lot more restrictive than that. So it's not only the outgoing URLs, they also want to know the source IPs of everything which is sending the traffic outside. So in that case, if your VMs have Neutron virtual IPs from the Neutron network, those IPs will not be presented to the external firewall. So make sure that if your VMs don't have any floating IP or a customer accessible IP, then the IP which you are giving is the gateway IP of the Neutron router to the admin, the firewall admin, to act as a source. If a VM has an IP from a customer accessible network, apart from the virtual IP, then that IP will be presented to the firewall. The other thing, CloudFondry doesn't support out-of-the-box SSL inspection. Now this is a lot of our customers, they actually insert their own SSL certs as the packets are coming from outside. CloudFondry doesn't support it, so make sure you have that communication with the customer that custom SSL certs won't be supported in this particular case. The other thing which is very important and Jesse will talk about is that we need to make sure our OpenStack updates and upgrades are seamless and they're not affecting the CloudFondry experience. So that's one of the key tenants about the offering that we have and the code that we've implemented to do that, which I'll talk about a little bit more in a moment, but as mentioned, there's a release every six months and during that release, we've got to do an upgrade for these customers and so being able to do that in a way that doesn't disrupt the CloudFoundry implementation is very important. And then even within a release cycle when there's a security patch or minor releases to the OpenStack services, again, being able to do that without interrupting the CloudFoundry implementation is very important. Those, the minor releases tend to have a much smaller impact versus the major releases which obviously have a much larger impact. And then being able to change configuration variables. So OpenStack filtering preferences for Nova, those types of things or load balancer configurations, being able to do that on the fly for customers, being able to think about how that's gonna impact you or OpenStack, your CloudFoundry implementation is important. So I mean, the point here is one thing, one comment which I do want to make is if you see Bosch and CloudFoundry, that's architected from day one for updates and upgrades. Unfortunately, that has not been the case for OpenStack. So it's mostly OpenStack is getting into that direction but we have seen the updates and upgrades have been a hiccup. So definitely with BlueBox coming into IBM, we saw 100% improvement on that case because they followed a very disciplined model and recently all our BlueMix deployments where we had on top of running on top of BlueBox, they were updated and upgraded without impacting CloudFoundry even once. The other lesson, definitely you want to automate everything with that BlueBox uses Ursula and Raleigh and as you can talk about it, how do they actually do that? Yeah, so the core differentiation our offering is the operational capabilities. It's not the OpenStack technology itself and so we actually make the OpenStack code that we use publicly accessible. So if you go to the GitHub and you look for BlueBox group Ursula is our project and Ursula contains all the Ansible code that we use to deploy and upgrade OpenStack itself. And having this, here go back to the previous one for me. Yeah, so having that set of technology and that allows us to do both our dedicated and our local installations. So every one of our implementations runs the exact same set of code all powered by that one automation framework allows us to ensure consistency in those environments and we like to think about it sort of like the iPhone or the Android model. So while we have less flexibility in our deployment in that it is a very opinionated set and of OpenStack technologies and a very opinionated configuration of OpenStack technologies we know exactly what's on every one of these implementations and so we know that when we do validation in our lab to go do those upgrades and it works there that it'll work everywhere else. This is one of the most challenging things that we see when we're acting with customers that do OpenStack on their own particularly with customers that have multiple environments. Ensuring that you've got consistency in those configurations between those environments both from a code perspective and a configuration perspective becomes really key as you think about ways to update OpenStack consistently and ways to ensure that your cloud foundry implementation will operate across your suite of deployments efficiently. The other thing that we do is we use a rally for validation of the OpenStack environments and today we use that predominantly in the lab during our development processes as we're validating each release that we do of our product and we use rally both to measure performance from release to release and we use it to validate the API and behavior has not changed from the previous release and rally has this neat capability where it allows you to track the historical runs from each implementation or from each execution of rally and so you can see over time how your implementation has changed from performance and a consistency perspective. The other thing which we do once OpenStack is deployed we use automation under the covers leveraging the fog gem which Bosch also uses to do a lot of discovery on the OpenStack environment so in terms of discovering security credentials what are the flavors, what are the subnets, security rules, we discover all that information from OpenStack in an automated fashion and if some of these things don't exist we actually go ahead and create in the background the security credentials, the key pairs, the different flavors for the DEAs, controller, health manager, et cetera, create the network security rules and finally a combination of Bosch and Ruby is used to automate the whole CloudFondry deployment on top of OpenStack be it uploading the stem cell uploading the CloudFondry releases using Bosch and then finally doing the CloudFondry deployment itself. Now as you see based on all these lessons led and as Jesse has been talking we decided that it makes sense because of this model since they require this constant care there are frequent updates and updates needed to offer as a service. From a CloudFondry perspective you have new release every two to three weeks but our pass is not only CloudFondry it is a combination of CloudFondry plus 150 other services and if you look at the permutation and combinations which they can create with the versions and mismatches it can be a huge version in sprawl. Also we want to make sure that our public dedicated as well as local deployments are in sync so we follow that cycle where the BlueMix or BlueBox which we have running in public environment are dedicated with our sync with the dedicated and local. Similarly with OpenStack you have two annual releases and the complexity actually requires expertise in many operational areas. Also a lot of our users they want to work with OpenStack and not on OpenStack in terms of configuring and maintaining it. So with that Jesse will talk about the IS Relay or the BoxPanel component of the BlueMix Private Cloud. And so I think this is particularly interesting for organizations that are thinking about and our fee deployments or other organizations that have to manage multiple environments. And if you back up to the AT&T Summit at Austin you saw that they created their own internal management system to handle the complexity of having all of those individual installations. So our offering again is to provide those individual OpenStack environments to many customers and so instead of managing one or two OpenStack installations the plan and goal is to manage thousands. And so again to do that we needed a mechanism that allowed us control and automation across that entire platform. And so we've done that with a technology we call BoxPanel and the technology we call Relay. BoxPanel has become sort of our system of record for all of the data that you need to track a release. So think of every sort of object that's involved in an OpenStack deployment whether it be the data center of the racks, the networks, the switches, the machines, the subnets, the IP addresses, the customer contacts sort of every little piece or object exists in the system and it allows us to have a very flexible way to join together data about a deployment in a way that can be modeled out as we do that deployment. And so if you're thinking about as an organization being able to run these types of technologies think about how you're gonna plan for this data. Whether if you're gonna have many installations you might wanna come up with a system or a methodology to have that in an actual usable point of record. And if it's just a small number of deployments you can do it in something as simple as Excel. But the key is ensuring that you've got that data recorded so that as you think through the transition of those environments and as you think through the upgrades of those environments that the data is consistent. BoxPanel this is a screen that shows sort of the user experience that our operators have. So today in our offering this view is exposed to our users, to our, excuse me, to our operators that are managing all of these clouds and not directly to users. So our goal is to take that headache away from an individual organization. And so to do that BoxPanel is a central for us, a central software as a service offering that then talks to what we call Site Controller. So again in dedicated that's running in SoftLayer and SoftLayer has 40 plus data centers around the world. So we needed a mechanism within each one of those data centers to control each individual deployment in that data center. And then in the local context that cloud sits in a customer's premise. So we needed a methodology to actually update and maintain that capability. And our goal with dedicated and with local is again to keep the code as consistent as possible. So the Site Controller technology actually sits in a specific geography and can manage multiple environments behind the scenes and talks back to BoxPanel to get its instructions. And it handles things like network automation at the site, power distribution automation, all of the monitoring and telemetry. So things like logging, log aggregation and telemetry aggregation go into that one Site Controller versus coming all the way back to a centralized BoxPanel site. We found this methodology to work very, very well for managing a multitude of deployments. And again, looking at the work that AT&T has done I think they've done similar implementations. So thinking through as an organization how are you going to manage all of those disparate environments that you have becomes particularly important. So with that let me talk a bit about the Bluemix relay. As you can see, what you have at the bottom is a customer data center where Bluemix is deployed, a CloudFondue is deployed. On the top is the whole backing infrastructure which is running in IBM, which is managing this remote Bluemix deployment or the satellite Bluemix deployment as we call it. The one key thing apart from the CI CD process which I mentioned, which first transfers the code to the public Bluemix, then to the dedicated Bluemix in software and finally in customer data centers. There is a technology which we use called Urban Code Deploy. That in a nutshell is connected back to a lot of other IBM repositories as well as some external repositories. So we pull the CloudFondue code from an internal IBM repository plus any other supporting services. So all these IBM software which is available on Bluemix as a service, for example, our big data suite, our Watson set of services, caching, queuing, all those are available in different repositories in IBM locations across the world. So Urban Code Deploy actually helps us in terms of pulling that code from different repositories, creating a single consistent release for a Bluemix deployment and then being able to push out to all these satellite Bluemix locations which are across the world which we have deployed. So that's one key piece. The other thing is that there is the security piece, what we call internally the Curator which manages these Bluemix deployments in terms of being able to collect logs and generating reports. So who is accessing your environment? How much CPU, et cetera, or triggers are being sent into your environment? Is the memory reaching its limit? All that information is collected through the Curator console and reports are generated every day for the customers to see what is happening in their environment. The other thing is we also run all the VMs, the CloudFondue components VMs which are deployed in that environment. They are connected back to an Active Directory server which is running in IBM so that every login and logout to those VMs is being tracked and recorded. So apart from the security, the patching and maintenance of the CloudFondue VMs itself in terms of the operating system patches or any security vulnerabilities, that's also we handle remotely from the IBM data center. This is a view of the Bluemix operations console. One of the things is it follows as Jesse was talking about the iPhone model, you get updates as you can see on the top right that there is an update pending and customers can then select what dates or times within a defined period, they would want this update to be applied. So that's how we actually make sure that we are keeping all the satellite, local, private, Bluemix deployments in sync across the world by sending these constant updates and customers can then schedule and provide their dates. The other thing, it also gives a view in terms of the usage of the environment apart from the basic IS capabilities like memory, CPU, et cetera, how many users are accessing your CloudFondue or Bluemix, how many apps are deployed, how many services are deployed, so it tracks all those other things. There are a lot of other capabilities within this ops console, for example, in terms of being able to integrate your CloudFondue deployment to a customer LDAP, being able to add users from that customer's LDAP or other things like if you want to do catalog management. For example, if you get a set of services, what plans do you want to expose to certain users? Should they be able to provision those services or only a subset of users should be able to provision? You can do all that through these operation console. So to wrap up, this is what we offer, Bluemix Private Cloud platform and infrastructure as a service in the data center. Right now, as you can see, there are two different relays operating and managing the IS as well as the past portions. There are definitely plans and discussions in terms of making this one connection moving forward in the future. And finally, we want to say that both CloudFondue and OpenStack, they are a great fit of 100% open source, strong and vibrant community on both of them and they're really complimenting each other. Bottom line, it's a match made in heaven. Thanks. Any questions? So the question was, how close should the CloudFoundue and OpenStack operations team work together? In our case, they're different. So in our model, the entry model is for anyone who is opening up a ticket on the CloudFondue side. The CloudFondue operator then determines at some point whether it's an issue with the CloudFondue itself or the OpenStack. And then they go through the formal channel to the OpenStack to open and say that this is an issue with the OpenStack. So they are different operations team as of now, not to say that this is the model we want to follow in future. We definitely want to bring them closer together. The other things which we have noticed is the credentials which you create, typically when you are deploying CloudFoundue on OpenStack, because you need to set quotas, you need to set flavors, you need to give CloudAdminCredentials or OpenStackAdminCredentials to the CloudFoundue deployer, which is not a right fit, right? If you just get them the tenant credential, then the whole job of being able to set quotas, except for falls on the OpenStack operator. So these are a lot of issues which we are going back and forth. There is a wave within Neutron, though it is not available through the Horizon console, there is a wave within Neutron where you can create partial rows. So those rows actually allow you to just be able to create your own tenants, create your own flavors, set the quota for that, but you cannot affect any other tenant or any other workload which is running on OpenStack. It's, for some reason it's not exposed through the OpenStack Horizon UI or CLI, but there is a configuration file which you can prepare and then use that particular role. In my perspective, I'm a big believer in SLA contracts and so if you have an agreement with your operations team that's running the OpenStack environment around what they're going to expose and how they're going to expose it, as long as they commit to that contract, then you, as a Cloud Foundry operator, should be able to trust that works as expected and I think it's actually preferable to be able to have those teams be split and focus on the specific technology at hand versus trying to have two worlds of technology in your head at one time. Good question was have we grown running virtual network under a Cloud Foundry installation? You mean the number of different virtual networks or number of machines? You're talking like subnet size. Yeah, subnet size. Fortunately, no, not so far because as I was mentioning in one of the models which we have followed is the subnet which we create for the Cloud Foundry management control plane is different from the subnet which we create for DEAs or supporting services. So most of the growth which will come, it has to come in the services side. So the services, they either go in their own tenant on the open stack or if they have to grow and be residing in the same tenant as Bluemix, for example, our logging services, they need to reside in the same tenant where a Cloud Foundry is running but for that, they use a different network altogether. So in that case, we, I mean, because our data plane is separate from the management plane and management plane is predetermined in our case and we still creep a lot of buffer. We use a slash 24 or slash 23k. Yeah, so the question was, does Cloud Foundry support IBD-6 internally? We haven't used for on, do you know? No, better than Lee. Anything else? Great, well, thanks for joining us this afternoon and have a great rest of your week. Thanks.


Well, I am not having a lot of luck with my keyboards recently. Not only had my Amiga keyboard failed due to membrane failure, there'll be a video about that coming out shortly, but my ZX81 keyboard has also failed due to membrane failure. This is pretty normal with these old computers. The membranes are made out of pretty brittle plastic which gets more and more brittle as time passes. Luckily, you can get replacements. And this is a replacement keyboard for the ZX81. This tail plugs into the motherboard. This is a self-adhesive keyboard thing that sticks on this part of the case. So I am going to replace the keyboard of this ZX81, but first I will demonstrate what's wrong with it. The keyboard is running and you are seeing a screen capture of it. Most of the keys still work, except you notice that 5 and 6 have failed, T and Y have failed, G and H, B and V. C and N work, F and J work, R and U work and 4 and 7 work, so it's just these set here. This is a classic symptom of a cracked trace in the membrane. The way these keyboards work is they divide the keyboard into rows and columns. You can in fact see with this that there are two cables here, one which connects to the top of the keyboard membrane, the other which connects to the bottom. When you press one of these buttons it touches the two together. So one of these traces will have failed. It's probably repairable if I had some conductive paint, but I can't be bothered so I'm just going to put a new one in. Repairing them is a fool's game anyway because once they go they just go. So let's take the lid off this thing. So luckily the ZX81 is pretty simple to dismantle if I can find an appropriate screwdriver, not that one. This thing was made as cheaply as humanly possible. It's not quite as cheap as the ZX80 which was made out of vacuum formed plastic and was, well, the keyboard was actually part of the PCB. The PCB poked out through a hole in the front of the case which was fairly special. So this thing should open up and this shows you the PCB, the composite mod I did so that I don't need a RF modulator and the really rather handsome old fashioned red PCB. I need to take the PCB off. Okay now that screwdriver is not big enough. Okay and that is the top side of the PCB with the processor, the custom chip that does most of the work of generating the video. We've got the RAM and this will be the ROM. This is the now defunct RF modulator with a cable connecting it to the composite mod. So the output of this is producing composite video rather than RF video. I didn't bother taking the RF modulator off because it's got this socket as part of it and besides taking it off is hard.  Yes, this keyboard is not going to work anymore. I just need to get this out. There we go. All right, annoyingly the composite mod doesn't actually mount anywhere useful so I just had to stick it on. So I'm going to have to put it off. What did this wire connect to? Nothing as far as I can tell. There are a few configurations for this. You can see by the unpopulated pounds on that side of the board. Yeah I think that's unused hopefully. Anyway this can now go aside and we start with the interesting bit. We have to get this keyboard off and it is stuck on. So for this I'm going to need to get out the hot air gun. Okay now as I say this thing is stuck on so it could just be pried up but it works so much better if you heat it up first. So I'm trying to arrange my hands. Let's see how this works. It's set to the minimum temperature. I haven't actually done this before. Yes, this appears to be working pretty well. So we just insert the prior under this thing. I should probably have used the bigger nozzle. The instructions recommend a hairdryer but I don't actually have one. The hot air gun should do fine. The tails for the keyboard go through the case for a slot here which is why that bit won't lift up.  Yeah this is really annoying. I need to use multiple hands. So I've got one hand holding the hot air gun which also has to rest on the case to hold it down and then the other hand has to peel the thing off. But it is coming. I suspect the ancient adhesive probably isn't much good anymore. The air gun is set for its minimum temperature which is 100. I wonder if I'll be worth. Yeah I could crank it up but I don't think it's worth it. This is actually working. And as you might imagine I really don't think this keyboard is going to be any use after it's taken off. I mean it's broken anyway. This is not as delicate as I was hoping it was going to be. And I don't know what's this. Oh ho, that's the keyboard. And this is the sticky layer that was holding it on. So let's see if we can peel this off. Yeah this thing's revolting. I was afraid I was going to have to scrub this thing with IPA but this is working out nicely. But it's come loose. All right, good. Now it's done. I just need to put the, come on. The wand goes into the heat guard at a particular angle to turn it off. There's a magnet that throws a reed switch. There we go. But it's not really particularly obvious how it goes. Okay, so here we have the case. It's a little bit sticky but that's fine. Here is the old membrane. The torn brittle plastic. You can see there are two layers. This is the, these are the actual contacts themselves that get pressed together. I peel this apart. There we go. See the top and the bottom, these are, this is not very conductive material. It's a terrible, terrible keyboard. The only thing going for it is that it was incredibly cheap. And here is the replacement. This is new construction. Well, it says copyright 2014. Membrane keyboards of this kind are still used today for things like ATMs and cheap machinery. These do have the advantage in that they're waterproof and easy to clean. So all that we need to do is to stick the tail through there and then stick this thing down. Now interestingly, the new keyboard is quite a lot thicker than the old one. I don't want it to stick down yet. There we go. There's still some adhesive on the tray. Parts of that will be the the paper backing that I have to peel off, but okay. So I'm going to get one try at this. I can peel the blasted stuff off. I don't want to damage the keyboard itself. Oh, come on. Here you go. So this reveals the keyboard layers, which is subtly different. It is a new design rather than a reproduction of the old. Hopefully this should last longer. So this goes in here. Okay, that looks good. Let me just press it into place and we're done. Keyboard replaced. We now have to reassemble everything and see if it still works. So if you're out, how it all goes together now. The PCB goes in like this, but the keyboard membrane plugs in here. Just trying to think what the best way to do this is. Probably this way. The PCB will then screw onto the top. Yes, I should have taken better notes as to how it goes together. So it will actually go together like this. So if you plug the keyboard in, the tails just push into the connectors. It's really a bit dubious and difficult to see. Here we go, like so. Then the PCB will go down like this and these two screws will go in. So one here and one here, right. We then stick the composite mod board down. So the black wire is unused. We can reuse the old piece for adhesive and then this should just push down here and then the bottom goes on and that should be it. Okay, doing up the screws. We've got the short ones that go in the front and you have to be careful because Sinclair's cheap and nasty plastic continues to be cheap and nasty 40 years on. And in fact, it's probably even cheaper and nastier and if you're too rough with the screws, you will break the plastic. I don't wanna do that and that should be it. So let's hook up the video again and plug in the power and see what happens. Well, it boots. One, two, three, four, five, six, seven, eight, nine, zero. Q, W, E, R, T, R, U, I, I, O, P. E, V, B, N, M, dot, space. Write all the keys work. Close quote, new line. 20, go to 10. Fantastic. Yes, there is no repeat key. So in order to get all the way to the right-hand end of the line, you have to do this. Takes forever. Okay, so let's add a semi-colon, which is here. Fantastic, works fine. That, well, it'd be wrong to say that that couldn't have been simpler, but that was pretty simple and so much less work than the Omega membrane replacement is turning out to be. So that is a nice success. I will discard this copyright 1980. This one is 2014. The, you can see that the colors of the new one are slightly brighter, but it's a pretty decent replacement. Some of the styling, you can see that the line around the box, for the air graphics character is a little bit thicker on the new one. Yeah, and the shape of the dollar sign is subtly different, but there's very little to it. They've done a really nice job of replacing this thing. So, fantastic. I now have a fully functioning ZX81, which I can use for ZX81 things. Anyway, I am glad that this video has actually turned out to be as short as I hoped it was going to be. I hope you enjoyed this video. Please let me know what you think in the comments.


Welcome. I welcome you all to this lecture in the course Sandhi in Panimian Grammar. So far, we have looked at the background of what is Sandhi. We studied the process of speech production. We also studied how the concept of Sandhi is used in various traditional disciplines and then we also studied what is Sandhi in Panimian Grammar. We also in this relation studied the concept of Samhita. We took several examples in which we showed what is a Samhita and how it results in Sandhi. We also saw that in the traditional system of Panimian Grammar, the Sandhis are dealt with under five categories, Ach Sandhi or Vavel Sandhi being the first one and we shall be dealing with Ach Sandhi in this particular lecture. Ach Sandhi is Vavel Sandhi. What does it actually mean? What does Ach Sandhi mean? Ach Sandhi means that this is a Sandhi in place of a Vavel. Ach. What is ach? We have already seen in the previous lectures in this course how the Pratyaharas get formed. So, starting with the very first letter in the Pratyahara Sutras, namely a and picking up an ith sound coming at the end of the fourth sutra, namely ayauch. We pick up chha here and a before we join them together and we get the term ach which stands for all sounds in between a and chha and also a which amounts to all the Vavels stated in the Pratyahara Sutra and therefore ach stands for a Vavel. Now in ach sandhi ach that is a Vavel which is or sometimes which are the substituent and what is known as the Sandhi, what is known as the ach Sandhi is the substitute in place of this substituent in the form of a Vavel or in the form of two Vavels. So, this substitute is either a Vavel or it is also a consonant this is very important. The substitute happens in place of a Vavel so the substituent is a Vavel and the substitute could be either a Vavel or a consonant but the substituent is extremely important and because of that this is called ach Sandhi. Now this substitute in the form of either a Vavel or a consonant takes place in the environment of two Vavels being uttered in close proximity that is in Samhita mode which means that when two Vavels are uttered immediately one after another the gap that is required for the distinct comprehension of these two Vavels is only remaining and there is not any more gap in between these two Vavels. That is the Samhita mode in which the Sandhi takes place. Obviously in this Vivaksha is at the background and we have already studied when Vivaksha is at the background Samhita is to be obligatorily made and in all those cases in all those places in such a situation one Vavel or sometimes both the Vavels they are substituted by a substitute sometimes in the form of a Vavel or sometimes in the form of a consonant and this is the substitute. So this is how ach Sandhi is referred to. This is what ach Sandhi means. In the Panimian grammar this ach Sandhi is treated in the following sections. There is a big section which begins with 6172 and goes up to 61113. This is the section of Sutras which can be said to deal with ach Sandhi. This section is governed by the section heading Samhita-yam. This is the Sutra 6172 and this section heading governs the section up to 61157. The 61158th Sutra starts dealing with the accent. Just before that there is this Samhita-yam Adhikara that comes to an end. From 6114 up to 61157 that means the remaining part of the Samhita-yam Adhikara they deal with some other topics. For example from 6113 to 114 the two Sutras deal with what is classified as Visarga Sandhi and will be dealt with in that section when we shall study Visarga Sandhi. There are some more Sutras which deal with Prakriti Bhava. This is very important and we shall study this in detail as well. 61115 up to 130 and then there are some Sutras which deal with the augment Sir stated to be Sut in Panimian grammar from 61135 up to 157. The Sutras in between that is 131 to 134 they also deal with the Visarga Sandhi and we shall be dealing with them when we study Visarga Sandhi in the course of the lectures in this course. This big section in the Ashtadhyay in 6.1 can be divided broadly into two subsections. One of them is from 6172 up to 6183 and it is the Sutra Ekapurva Parayohu which is 6184 which divides these two sections into two. So from 6172 up to 6183 this can be said to be one subsection one type of Sandhi and from 6184 up to 6113 this is another type of Ach Sandhi. Ekapurva Parayohu can be said to be that Adhikara Sutra which divides the two sections in the Ach Sandhi. This is an extremely important Adhikara Sutra, Ekapurva Parayohu. Now the Ach Sandhi that is stated between 6172 to 6183 is of a peculiar kind. This type of Sandhi is called Ekasthanika Ekadesha Sandhi. What it means is that this is a Sandhi where there is one substituent and in its place comes one substitute. There is one substituent and one substitute which is a by default situation and so this is not particularly referred to as Ekadesha Sandhi even though the substitute is one. So this particular explanation can be showed in the format of an equation in the following manner. If you have an input namely x plus y both being vowels and this plus sign indicates that they are in the Samhita mode and in this Samhita mode y is the right hand side environment then the output would be z plus y, z is the substitute and this z would be a consonant and this consonant replaces the one substituent x which is a vowel. This is the explanation in the form of an equation of Ekasthanika Ekadesha Sandhi stated in the subsection namely 6172 up to 6183. In this equation the left hand side environments generally does not matter. It is generally a consonant because if the left hand side environment is a vowel then there might be the same situation that might arise as shown on this slide with of course some exceptions but generally it is a consonant which appears on the left hand side but that environment does not really matter as far as this subsection of Atsandhi is concerned. To show it diagrammatically we can say that this is A and this is B and both of them they are vowels and now the rules stated in this section of 6172 to 8383 what they state is that if these A and B both vowels if they are uttered in a Samhita mode then this A is replaced by this C and B of course does not change it remains as it is but this diagram shows that there is one substitute and there is one substitute in place of A appears C, C replaces A, A is the substitute, C is the substitute, C replaces A and as a result the output would be C plus B, A plus B is the input and one of the sutras in these sections apply and then the output is C plus B. This is how this type of Sandhi can be diagrammatically represented. This diagrammatic representation was first published in a review that was written by this author by this instructor in 2006 in the Annals of the Bhandarkar Oriental Research Institute published by that institute Pune. Now let us look at the explanation of the second type of Sandhi. This is stated from 6184 up to 61113. This type of Sandhi is called the Vrithanika Ekadesha Sandhi. What it means is that this Sandhi is such that there are two substituents, Vrithanika, two substituents and in their place comes one substitute, Ekadesha which is a very unique, very peculiar kind of situation and that is the reason why this Sandhi is generally referred to as Ekadesha Sandhi. Two substituents and one substitute that is why this is referred to as Ekadesha Sandhi. This type of Sandhi is governed by the Adhikara Sutra Ekapurva Parayoho. In this sutra there are two words Ekaha and Purva Parayoho. Ekaha is one of Ekha meaning one. Purva Parayoho is 6-2 of Purva Parayoho which means in place of Purva and Parayoho. Purva means earlier or before which indicates the left hand side environment. Parayoho stands for later or after which indicates the right hand side environment. So in all what this sutra means is that in place of the earlier and the later sounds, in place of earlier and later vowels there is one substitution, one substitute. What it means is that in place of the vowel that comes before and the vowel that comes after, in place of both of them comes one substitute in the form of a vowel. And also in place of the left hand side environment and also the right hand side environment appears one substitute in the form of a particular vowel. This is in brief what this sutra means and this is an Adhikara Sutra. So this governs this entire subsection and so this continues and appears in each and every subsequent sutra in this particular section. In the form of an equation this particular sutra can be explained in the following manner. If X and Y is the input, X plus Y is the input and both of them are vowels where Y is the right hand side environment with reference to X and X is the left hand side environment with reference to Y. The output is Z, remember the input is X plus Y both vowels and now the output is Z only one element and this Z substitute is a vowel and this vowel replaces both the substituents X and Y in their respective environments. So this is the difference between the previous subsection and this subsection. Now to show it in the form of a diagram once again we can say that there is this A on the left hand side plus B on the right hand side and they both are uttered by the speaker in Samhita mode. That means that there is an additional gap than what is required for their distinct comprehension and then in such a case sutras in this particular section they become operational and then in place of A and B we get C as the substitute. This is the input A plus B and C is the output. This diagrammatic representation was first published in a review that was written by this instructor in the Annals of the Bhandarkar Oriental Research Institute, Pune in 2006. Now what are the examples of both these types? Let us take a look at them one by one. Here are the two examples of the first kind where A plus B and A is replaced by C, Ekasthanikar Ekadesha. So the first example is Yen Sandhi stated by the Sutra Iko Yen Achi 6177. The second example of this type A plus B, A is replaced by C is A Yava Yava Sandhi stated by the Sutra Echo Yava Yava and some other sutras as well. Then here are the examples of the second type. There are five examples. The first one is Guna Sandhi stated by the Sutra Ad Gunaha. Then there is Vruddhi Sandhi stated by the Sutra Vruddhirachi. Then you have Pararupa Sandhi stated by the Sutra Engi Pararupam. Then Savarna Virgha Sandhi stated by the Sutra Akas Savarna Virgaha and finally the fifth one Purvarupa Sandhi stated by the Sutra Enga Padantadati. There are some additional sutras also explaining these five types of Sandhis which we shall deal with when we study these Sandhis. But these are the sutras which primarily state these five types of Sandhis and remember these five types of Sandhis are of the type where A plus B and both get substituted by C. This is a very important, very crucial kind of distinguishing feature between these two types. There are two types, there are two examples of the first type of Sandhi Ekasthanika Ekadesha namely Yansandhi and Ayavayabha Sandhi and there are five examples of the second type of Sandhi namely A plus B and both of them get replaced by C. Dristhanika Ekadesha and these are those five types. What is the feature of these Sandhis? We see that Sandhi is a Vikara or Vikriti. When two Vaubles, they are part of the element, they are considered as Prakriti and the Sandhi which is brought about by these sutras in this section this is what is a Vikara or a Vikriti. Vikriti as a modification. There is a modification, there is a substitution as against two Vaubles which remain in their own form also in the Samhita mode which is also known as Prakriti or Prakriti Bhava and in fact we shall study this Prakriti Bhava type of Sandhi when we take that up later on in this course. It is a matter of question whether to call it a Sandhi but the Panayana grammatical tradition has included the Prakriti Bhava as part of the Sandhi chapters and therefore the Sandhi chapters are generally referred to as Panchasandhi Prakaranam in the traditional texts like Vayakaranasiddhanta, Kavmudhi. They are called Panchasandhi Prakaranam including the Prakriti Bhava. Actually Prakriti Bhava is the absence of Sandhi still because it is in contrast with the other types of Sandhi it is still included in these 5 subsections in the Panayana grammatical tradition. This is a very important feature of Sandhi Sandhi as a Vikriti or a modification. The next important question is what is a Sandhi and input of? As we saw A plus B is the input and C plus B is the output in one case and A plus B is the input and C is the output in the other case. What this C plus B and C is input of? What does it feed into? And here are the answers. Swara operations, the operations dealing with the accent and we shall study this aspect in detail in subsequent lectures in this particular course. Swara operations which happen after these Sandhis happen. So Aksandhi is an input to these Swara operations. Also operations where sentential combinations are input. Even there Aksandhi becomes an input. For example the compounds or the samasas like Rajasva or Gajanana. Similarly Taddhita formations for example Dasarathi or Vaya Karana. Generally after the Aksandhi operations happen, the sentence finally gets generated and is used in the process of communication. So we have seen earlier where we quoted the Vaya Karana Siddhanta Kabudi which referred to the explanation of the term Samartha as Krta Sandhi Karyatvam. Samartha means Krta Sandhi Karyatvam. This is very important and a very crucial fact to remember. We shall also study the interrelation of rules that are part of this particular section. What is so important about them is that the operational sutras, namely the Vidhi Sutras and all the sutras stated in this section barring a few exceptions like Ekapurva Parayohu. Most of them they are Vidhi Sutras. So these Vidhi Sutras apply when the conditions or the environments of those rules come into being when they exist in the process of derivation of the sentence. Generally the conditions for each rule is believed to be exclusive, does not come into any sort of clash with any other sutra. But in some cases these conditions are stated to be overlapping and this particular fact brings two or more rules into contact with each other. This contact is of the nature of conflict and then there are principles stated within the Ashtadhyay which is all this conflict, some principles which are stated explicitly and some other principles which are stated implicitly which are unearthed and explicitly stated by the later Paninian grammatical tradition. So when we study these sutras in this particular section we shall also keep an eye on the interrelation of rules and accordingly we shall study the examples. This is the technical terminology that we should be aware of when we deal with Sandhi in general and At Sandhi in particular. Karyin or also referred to as karyi which means an element which undergoes an operation. Karya is an operation or modification. So an element which undergoes this operation is karyin or karyi. Then the other technical word is nimitta. Nimitta means conditions or environments in which the operations happen. These are not explicitly used in the Ashtadhyay but they are very much part of the traditional vocabulary, traditional terminology. Panini uses the terms sthanin and adesha. Sthanin means an element which has scope of application which is to be replaced and a sthanin is never explicitly uttered. The word sthanin consists of the word sthana which means the scope of application. This scope is in the form of meaning sometimes also in the form of the combination of verbal elements. And then we have another term called adesha which means a substitution which is explicitly expressed when there is scope of application of some other element to be expressed. We shall study At Sandhi using these technical terms. So when we know what is a sthanin and what is an adesha the next very very important term and the technique used in the Ashtadhyay is sthanivadbhava. This will be also part of our discussion. This poses some questions and then there is an answer. The questions are can the consonant substitute be considered as its substituent vowel as is the case with ekasthanika ekadesha. And also can the vowel substitute be considered as its both substituents as is the case with dristhanika ekadesha. Such an assumption can become an input for application of another rule. This is possible in case of At Sandhi even though generally denied by the sutra in the Ashtadhyay this is possible in case of At Sandhi with several exceptions and this will become part of our study. Similarly the other important terminology that we need to remember is uddeshya vidheya bhava. This is how the rules are structured. There is something called uddeshya and something else called vidheya. Udeshya is something that is already known with respect to which an operation is stated by a rule. This is vidheya and generally this vidheya is what is new which is not known before. Udeshya is generally in the form of conditions or the environments which pre-exist which serve as the input. And vidheya is an operation stated by the rule something that is made known only by this rule statement. And the vidheya in most of the cases in this particular section is the modification or the substitute also known as the Sandhi. So this uddeshya vidheya bhava is extremely crucial, extremely important when we study the sutras in the Ashtadhyay section. Most notably when we study the Pratyaharas and what those Pratyaharas stand for these two concepts will become extremely important. To summarize what we studied in today's lecture is that we studied the nature of At Sandhi. Namely Ekasthanika Ekadesha, this Ekadesha is in the form of a consonant and also Dvisthanika Ekadesha and this Ekadesha is in the form of a vowel. The second type namely Dvisthanika Ekadesha is generally referred to as Ekadesha. We also got introduced to the technical terminology in this regard. Karyan, Nimitta, Karya, Stani, Adesha. We noted the examples of two types of At Sandhi. Yen Sandhi and Ayavaya Sandhi of the first type and Guna Sandhi, Vruddhi Sandhi, Pararupa Sandhi, Savarnadirga Sandhi and Purvarupa Sandhi of the second type. We also observed that the At Sandhi takes place only at the final stage of the sentence derivation and its output is visible to only the accent rules. Now, hereafter we study the various types of At Sandhi together with the examples. In doing so, we shall also study the Sutras which state the At Sandhi. This we shall do in the subsequent lectures. Thank you very much.


Matt Ryan of the Falcons and you know, typically Matt Ryan is thought of as a solid quarterback But I guess after the Falcons lost last week things aren't looking particularly great for them So what what else is your thought behind this gem? Yeah, I kind of went into this week thinking that Matt Ryan would get a lot of buzz and if you look at fan share sports and see which players have been talked about most Matt Ryan is Essentially nowhere to be found and to me that's a little bit mind-boggling because Matt Ryan has been stupid good when they have been at home and indoors so far this year in the four home games They have played he is averaging twenty nine point six fan dual points per game. That is per game twenty nine point six Compared to eighteen point four points per game on the road So Matt Ryan at home has basically been this just unfaithful studs. So now you put him at home Against an okay Dallas defense, but they're missing Sean Lee. That's definitely a downgrade for them I kind of assume that's Matt Ryan to be the chalk But you got Cam Newton there got drew breeze Carson Wentz There are a lot of quarterbacks and shootout stack press guy is getting a lot of buzz That's exact same game because he's cheaper and he's seventy four hundred dollars Whereas Matt Ryan is eighty four hundred dollars But to me I think that Ryan kind of stands out as being one of the better quarterback plays on this slate But it's just not getting a lot of buzz you look at this Dallas defense They've allowed Carson Wentz to throw for three hundred and thirty seven yards They allowed three seventy five to Deshaun Watson three oh seven to Matthew Stafford They've just happened to face a lot of bad quarterbacks in general Matt Ryan Especially at home does not qualify as a bad quarterback 14 touchdowns one interception at home so far this year So for eighty four hundred dollars I don't think I can get there in cash because he is pretty expensive and again I want to pay down a cash quarterback but for tournaments I think this guy is gonna carry a lot less ownership than he should and he's just been Unstoppable there so far this year so I'm gonna use Matt Ryan no matter what but if he continues to keep flying under the Radar as he has so far this year I will happily take him at low ownership he what if he winds up being more popular than I thought I don't care I think he's worth it then still But right now it doesn't seem like he'll be too popular and I will happily take him at low ownership Without a second without a second thought about it Even if the Falcons are trending down Matt Ryan at the quarterback spot is not so don't forget about Matt


While star couple Gwen Stefani and Blake Shelton got hitched at his ranch in Oklahoma, the couple's first property purchase together and main residence is their home in LA. Located in the neighborhood of Encino, the massive abode was a new modern build, spending 13,000 square feet of space and it cost the pair over 13 million dollars. Since moving in, we've gotten a peek at the luxury estate thanks to social media, and we can see it's decorated with a lot of bold prints and accents, which might remind you of Gwen's former house. In this video, we'll check out where the power couple calls home. In these videos, we don't reveal any addresses, and even though I've done a house tour of my own place, please do not show up at any private residences because it's not safe for anyone. Gwen Stefani is a singer, songwriter, record producer and more, who broke out onto the scene as the co-founder and lead vocalist of the band No Doubt. Gwen further found success with her solo pop career she began in 2004, and she's also a fashion designer with her brand Lamb debuting in 2003. While Gwen is a SoCal native and Blake Shelton is a born and bred Oklahoma boy, they seem to be a match made in heaven. Blake is also a big shot in the music industry, but a different genre altogether. He's a country music singer and TV personality, of course, being on the voice alongside Gwen herself. And if you listen to country, then you're familiar with his songs too. At the time of this recording, Gwen has an estimated net worth of over 100 million dollars, while her hubby isn't far behind at all. Some sources state Blake's net worth is at 80 million, while others say it's 100 million as well. Taking those fortunes into consideration, the couple's first home together is what you might expect. A jaw-dropping mega mansion in the prime foothills of the San Fernando Valley, where they live together with Gwen's three sons. Hey guys, it's Kara back with another exclusive house tour here on Fumas Entertainment. Today looking at where Gwen Stefani calls home. Don't forget to like this video, hit that subscribe button if you haven't, and follow me on Instagram to chat. Now let's get into this video. Back in 2020, property records reveal that Gwen and her hubby Blake purchased their first property as a couple, a sprawling estate located in Encino, California. Encino is an area in the San Fernando Valley of Los Angeles, which is growing increasingly popular with celebrities. And others who live nearby include the likes of Selena Gomez and real housewives of Beverly Hills stars including Dariq Kemsley. Gwen and Blake spent $13.2 million for their gorgeous mansion, which was constructed just for them. At the time, the pair had just purchased a 1.6-acre plot of land in the coveted neighborhood, but these days we can see they've gotten cozy in the fully-completed, brand-new home and decorated the interiors to fit their personal style. Built on spec by noted developer Evan Gaskin, Gwen and Blake's gleaming white estate looks to be a slightly traditional-style home with a bit of that contemporary farmhouse vibe. At least that's what it looks like to me. Located on a secluded hillside, the couple's mansion is one of the most private in all of Encino, further tucked behind two oversized gates and hidden from the streets. Aside from the developer's photos, we've had to wait to catch a glimpse of how Gwen decorated the place inside, and they've shown us a little bit on social media. Photos from the developer show an exterior with black trim and windows, as well as outdoor amenities like a spacious motor court, four-car garage, and outback, a resort-worthy pool. The three-floor mega mansion offers 13,000 square feet of space, as well as luxury rooms like a high-tech home theater and fancy kitchen with top-of-the-line finishes and designer appliances. Since Gwen and Blake have been settled for a while now in the home, they've shared some photos inside on social media, and much like Gwen's former properties, it's decorated with plenty of bold prints. Gwen has shown off the flawless kitchen in plenty of online posts, like when she filmed a TikTok video, fans were able to see the space which is decked out in marble. There's a monochrome marble wall and large stainless steel oven range with sleek hood. Elsewhere her kitchen has wooden cupboards, and of course a large work island in the center. The kitchen space continues to an attached room which boasts a breakfast bar, as well as more cupboards for storage. At the time Gwen showed this room, she had it temporarily set up as a dressing room with a rack full of outfits. Around Christmas, Gwen showed one of her living areas, where she had the stunning tree on top of a zebra carpet near the window. We can see one of her son's framed portraits on the wall, and if you recall her former mansion, she had these photos of all three of her kids displayed beside each other. The pop star also showed her large staircase that was near the airy hallway, which at the time was also getting set up with festive decorations.  During a Jimmy Kimmel live interview, yet another room in the mansion was seen, which had fun decoration including snake print wallpaper, and baby pink candles and flowers. While in Gwen's bedroom, she has a huge portrait of her other half-blake on the wall. The dreamy mega mansion also has an oversized pool with inset spa out back, sitting beside a cabana with a web bar. Also on the property, there's a full outdoor kitchen, tennis courts, and more. Gwen is definitely known for her bold and fashionable taste, which she doesn't only show off through her outfits, but also in her home design. With what we've seen of her current Encino mansion, she brought a lot of that with her, and looking at her former Beverly Hills mansion, we can get an even better idea of how the star likes to decorate. Back in 2019, Gwen offloaded her extravagant former mansion for the whopping price of over 21 million dollars after two years on and off the market. She was originally hoping to get about 35 million for the mega estate, but it didn't happen. However, since she lived here with her estranged ex-husband, Gavin Rossdale, I assume she was just happy to say goodbye to the place, even at a discount. This mansion was well known for its eccentric and somewhat wild interior design, and Gwen and her ex bought it way back in 2006 for 13.5 million dollars. Tucked away behind guarded gates in the posh summit enclave, high in the mountains between Beverly Hills and Studio City, the estate sat on two acres of land and hidden down a gated 250-foot driveway. Gwen's former living quarters here spanned over 15,000 square feet of space with seven beds and 10 baths throughout, along with funky interiors like marble, cheerful and bright colors, and black and white graphic patterns. In addition to the main house, there was a separate structure that poses a guest house slash gym. Inside the main residence, there was a formal living and dining area separated by a black marble double-sided fireplace and fitted with vintage furnishings. The entryway boasted a geometric marble floor and sky-high ceilings, while the eat-in kitchen looked almost like an optical illusion with its black and white stripes. There is also a skylight here, a breakfast, nook, and stainless steel appliances. Other amenities in Gwen's former mansion included a professional movie theater, more than one office, a gift-wrapping room, and plenty of guest rooms, each with their own en suites. The master featured two luxury bathrooms and dressing rooms, once worthy of a style icon like Gwen. Aside from the detached guest house and pavilion with 1500 square foot gym, there was also a massage room and sauna. The backyard included other features like a tennis court, terrace with fireplace and outdoor kitchen, and of course an infinity pool and spa with separate kiddie pool. All right, so I think that concludes our Gwen Stefani house tour. We got to take a peek at the modern mansion she and her husband Blake Shelton are settled into, which was newly built just for them last year. We can get an idea of how the couple decorated the home, and while it might not be as wild as Gwen's former crib, we do know she brought some of her bold interior design taste with her into the current mansion. What did you guys think of the new Encino property? And what do you think about Gwen's decorating style? I think her former mansion was a little bit too out there for me, but there were definitely some stunning rooms. And what seems to be a more toned down version in the new house looks great. Be sure to let me know what you liked or did it like about Gwen's mansions down in that comment section. Thanks for watching. Don't forget to follow me on Instagram and tell me which celebrity homes we should take a look at next. I'll see you all in the next video. Bye.


There's a slightly different answer for people who are burned out than people who are sort of Content and a little lazy and a little fearful, you know, that's what there's slightly different answers Okay, but because usually if you're becoming with burnout You have to start and this is really useful for anybody You want to just start by like manicuring your nervous system, right a little bit of emotional regulation So like anybody who's burned out you want to start by trying as much as you can to get seven eight hours of sleep For example, just like baseline. This is the amount of sleep we need We know hydration nutrition that sort of stuff And you want to lean on basic tools like social support make sure you have a good social support network And you reach out and you're actually, you know, really base This is the basic stuff that helps us manicure our nervous system And then depending on how jacked you are do one to two to three of the following a day So if you're a little anxious, right a little burn You want to do either a gratitude practice a mindfulness practice or exercise? And it's literally a five-minute gratitude practice and I could talk for the next two hours about the neuroscience of gratitude and why it's important But let's just gratitude practice Mindfulness for stress production. You want 11 minutes of like breath work a day. It doesn't have to be super fancy Or I love running Loving kindness meditation because it's a freaking script and you find an online, you know And you literally just have to run the script and it does the same thing It's actually better than most other forms of mindfulness or 20 or 40 minutes of exercise, right? You exercise when your exercise is very anxiety You want to wait for your lungs to open up and to get a little quiet upstairs There's a sign that the brain is released nitric oxide.  But the thing I want to emphasize and this is really the place to start Everybody has what's known as a primary flow activity For me it's skin meaning like 80 90 percent of the time I go skiing It just drops me into the zone for my wife It's hiking with the dogs in the back country for my best friend It's playing guitar for another good friend of mine It's code and for you know jigsaw puzzles like whatever it is for you You want to double down on that and in fact the research shows that if you spend three to four hours a week on a primary Flow activity that might be the single best intervention to start with and here's the thing It's it does all kinds of stuff. So flow's a focusing skill So the more flow you get the more flow you get so if you're going skiing on Monday, you know for you It's your primary flow activity might mean more flow at work on Tuesday Wednesday and Thursday We know the heightened flow massively boosts happiness well-being Overall life satisfaction those things and the afterglow flow seems to last a couple days the heightened creativity Well, it'll last a flow state by a day maybe two And when we move into float resets the nervous system towards zero So it flushes our stress hormones out of our system and I'd like to mention a repeat performance aging point of view There are nine known causes of aging all of them What do they have in common? Inflammation stress and inflammation so anything you can do to combat stress and inflammation is combatting aging and it's you know sort of job one so You get a lot of bang for your buck with your primary flow activity And the thing about it isn't the reason I wanted to mention it because you described a certain type of person And what happens is as we start to age Whatever you usually around right around 29 30 like those the exact age group you described you put away childish things Oh, no, I got a family. I got a job. I've got responsibilities. I can't ride my skateboard.  I you know all those things go away and It's the exact Opposite of what you need to be doing right like so it's very counterintuitive and it's also I will tell people I will say Everything I'm talking about whether it's this or a handful of the things they sound.  Where's the technology? You know and I I like simple psychological tools that produce powerful neurobiological reactions


Anna Karenina, by Leo Tolstoy, translated by Constance Garnett, narrated by Lorna Raver. This unabridged audiobook was produced in the year 2010 by Tantor Media, Inc., which holds the copyright there, too. Part I CHAPTER I Happy families are all alike. Every unhappy family is unhappy in its own way. Everything was in confusion in the Oblansky's house. The wife had discovered that the husband was carrying on an intrigue with a French girl who had been a governess in their family, and she had announced to her husband that she could not go on living in the same house with him. This position of affairs had now lasted three days, and not a


Good day everybody.  Yeah, you're already in nap mode, aren't you? Yeah, we just got to the truck and I want to explain a little bit a few things to you guys We're gonna be trying a different schedule a different For me in my editing. I want to try something a little bit different. We're gonna skip over The next few days of vlogs that I had for you, which was me We were in Fort Erie last you heard from me, right? And we were going down into the US and then we were going to come back up here and we're already back up here so I'm gonna bring you up to the present with me and we're gonna start from here and Just work with a little bit of a different schedule for myself for for this month and see how it goes I want to keep this vlog a little bit more relevant and a little bit less in the past It was I was giving myself a big buffer zone Like of a week to get my video edited online and to you guys and by the time I released it To me it felt like it was sort of too far in the past to relate to because it was already a week ago for me And I've been doing this for like nine years and it's sort of just been bugging me a little bit I always like to have that buffer zone though just in case if I have a really busy day Driving truck or delivering or I just can't get to editing then you guys Still have a video, right? But over the years this system has sort of gotten a little bit. I don't know Old to me. I want to bring it up make it a little bit more relevant and At least in my mind so that when I'm watching the video I released that day I could be like, oh, yeah That didn't happen too long ago So I don't know how many of you even knew that my videos were so far behind there There I still can't release them to you I can't do a live video every day that'd be a lot of work even if I could like I mean the technology is there I could do it, but that's just a lot of work I need some time to be able to put these things together for you guys, so they're not completely Completely just thrown together So a lot of my vlogging friends they do next day videos and or they do like three days later I'm not too sure what we're going to Chalk it up to yet, but for now we're gonna start right here I've got a load behind me now that I'm taking down into Minnesota not too far you know, I'll be there in about seven hours or so and We'll see how this works out for me if I don't like it. I'll try it for this month Okay, I'll try for September see if I can make it through the month with it sort of puts a little bit more pressure on me to Get these videos done because what I've been finding the reason I want to do this is what I've been finding myself doing is Because I know that there's a buffer zone that I have a week to get the videos done before I have to release it to you Sometimes I let myself get a little bit lazy and I push it all the way back a week And then I'm stuck like editing seven videos in one day and I'm rushing to get everything done I'm a rush through the vlogs and I'm not really happy with the quality and it's I Don't know. Maybe I'm just getting bored of that system. I just want to try something different So we're gonna skip over what I'm trying to tell you is we're gonna skip over about a week's worth of videos hadn't even had them put together here and It's time to start Changing things up on my end on your end. It's probably just gonna be the same same vlogs and stuff, but I Just want to explain to you why there's not going to be That trip down to the US and back to you and how I got here because it's sort of like a gap in time now in my vlog timeline That I think deserved an explanation But either way, let's see if I can get my videos up at a certain time every day, too I'd like to get back to that. I used to have them released at 4 a.m. Every day We'll see some days. I'm just really busy and I can't edit every day Sometimes I just don't have the time or I don't have the energy or I'm just gonna push myself a little bit harder How about that? So now you know, okay, so we're back home. We're headed into Minnesota. We got a load of lumber in the box behind us tune into tomorrow's vlog and You'll see our trip down there Hope you guys are doing well. Hope you guys are taking care of yourselves. That's another thing I want to do more. I want to take care of myself more. I want to do more walking again I've been saying this all summer and all winter. I'm like, oh, you know what when summertime comes once the weather gets warm again We're gonna do more exercising. We're gonna walk every day and summer came and near summer went and here we are still with the belly so We'll see what we can do You ready to go diesel? What do you think you're ready to go? I think he's ready to go Take care everybody. I'll talk to you really soon


their natural, wild state, though close inspection showed how carefully this appearance was maintained by judicious landscape gardening. In many of the parks the road addendrons were in full blue and their rich masses of color wonderfully enlivened the scenery. Everything was fresh and bright. It had been raining heavily the night before, and the air was free from the dust that had previously annoyed us. It would be hard to imagine anything more inspiring than the vistas which opened to us as we sped along. The road usually followed the hills in gentle curves, but at places it rose to splendid points of vantage from which to view the delightful valleys. Then again it lost itself under great overarching trees, and as we came too rapidly down a steep hill on entering Bodmin the road was so heavily shaded that we were near our undoing. The loose sand had been piled up by the rain and the dense shade prevented the road from drying. The car took a frightful skid and by a mere hares breath escaped disastrous collision with a stone wall, but we learned something. After leaving Truro, an ancient town with a recently established cathedral, the road to Penzance, though excellent, is without special interest. It passes through the copper mining section of Cornwall, and the country is dotted with abandoned mines. A few are still operated, but it has come to the point where, as a certain Englishman has said, Cornwall must go to Nevada for her copper, and there are more Cornish miners in the western states than there are in their native Shire. Penzance is another of the south of England resort towns, and is beautifully situated on Mount Spay, one indeed wonders at the great number of sea coast resorts in Britain, but we must remember that there are forty millions of people in the kingdom who need breathing places, as well as a number of Americans who come to these resorts. The hotels at these places are generally excellent from the English point of view, which differs somewhat from the American. Probably there is no one point on which the difference is greater than the precise temperature that constitutes personal comfort and makes a fire in the room necessary. On a chilly muggy day when an American shivers and calls for a fire in the generally diminutive grate in his room, the native enjoys himself or even complains of the heat, and is astonished at his thin-skinned cousin who must have his room, according to the British notion, heated to suffocation. The hotel manager always makes a very adequate charge for fires in guest rooms, and is generally cherry about warming the corridors or public parts of the hotel. In one of the large London hotels, which actually boasts of steam heat in the hallways, we were amazed on a chilly May day to find the pipes warm and a fine fire blazing in the great fireplace in the lobby. The chambermaid explained the astonishing phenomenon the week before several Americans had complained frequently of the frigid atmosphere of the place without exciting much sympathy from the management, but after they had left the hotel it was taken as an evidence of good faith and the heat was turned on. But this digression has taken me so far away from Penzance that I may as well close this chapter with it. End of chapter 6


A thousand years ago, India contributed to the world in terms of 53% of the world's economy was India. A 500 years ago, we were about 26% of the world's economy. When the British left us in 1947, we were 3.6% of the world's economy. Today we have risen to 6%, but as a population, we are almost 25% of the world's population. We must at least achieve this 25% of the world's economy in the remaining five to ten years. If we do not do this, we will keep our people subjugated forever. We are at a unique time, that is for the first time. For the very first time, we have the necessary tools, we have resources, we have the capability and we have the technology to address every human problem in this country and the rest of the world. This generation has a unique opportunity that we can move about 600 million people from one level of existence to a completely different level of existence in an incredibly short time. Because we have all the means in place, the only thing that is missing is an inclusive consciousness among the people. And this is going to be the fundamental challenge that we will not identify with little identities that we have around us. We will not demolish the Meadah because you cannot demolish that, but a larger identity of the nation. The youth of India today has this tremendous possibility, responsibility and a privilege in front of you that you could change the way people live in this country. We have had a whole lot of people, almost three-fourths of this nation's population has had such a bad deal. Such a bad deal, a large part of them are still in an extremely bad situation where about twenty-nine rupees is wealth per day. When we're in such a situation, we have an opportunity to change this. We have everything in place. Only you and me have to get into place. That's the only thing that's missing. To make India once again a glorious nation, when I talk about glory, I'm not talking about the economic or the military progress of the nation. Yes, that is also needed, but more than that, India should embrace the world like a garland. India is capable of bringing a new level, new paradigm of success into the world. A new paradigm of what it means to be successful in terms of bringing human well-being. We have the necessary technologies and the wisdom to make this happen. We have to make this world a beautiful place, not by conquest, not by capturing, but by captivating the world.


I'm Corporal Ally Biteswinger, and I'm here with the gear. I'm Carmody, and he's going to be telling us a little bit about the lightning pack. Sir, do you mind if I actually put it on? Not at all. Well, a lightning pack is an electricity-generating backpack that makes carrying heavy loads easy for you. Because of movement, we can put a generator in there and collect that electricity and power batteries. We're hoping that they get fielded so Marines aren't burdened with having to carry as many batteries or re-supply so you can stay out in the field longer and be energy independent. Okay, let's show them how it looks. Okay, so right now you're walking with a locked pack. Okay, a locked pack. How much is in here? There are 60 pounds. That's 50% of my body weight. Right, and so you're accelerating that load every step, and the force on your joints is more than 60 pounds. A static load, if you're standing in one spot, would be 60 pounds. If you take a step, you're accelerating that load, so what you're feeling on your joints is more like 80, sometimes to 100 pounds. Wow. So right now I'd like you to press that button. All right, and you'll see that the pack is moving slightly, so it's making that easier for you to carry. And at the same time, you're probably generating between 7 to 10 watts of electricity. So that's the basic idea of a lightning pack. So when I'm walking, you know, the pack's moving up and down. And already I can feel the amount of effort that I'm putting into keeping the pack from moving around is less than I would if the pack was fixed to the frame. A couple of issues that I do have is that the frame's material seems a little weak. I would ask them to hopefully develop a patch with a stronger frame, a more robust frame, and then the actual, the noise generated by the bouncing motion is a little loud. And it's not ideal for, you know, controlling operations, so that's the only two problems I have. Other than that, it's a great pack. Awesome learning about these lightning packs here at Expo 14. The technology may not be perfect yet, but it's on its way. Thanks for watching, guys. We'll see you on the next episode of With the Gear.