So I think in theory we've got one minute to go, but no one more is going to get in the room Yeah, look people can still breathe crash in more people. No all right, so I'm gonna talk about running OpenStack on OpenStack and The reason this is an interesting thing to talk about This is the model that we tell people about OpenStack, you know, it's these lovely Big boxes compute networking storage. What we don't tell them is that this is what it looks like to talk about deployments This isn't a lovely pretty model And this is the reality. It's not because we've made it much more complex than it needs to be so We've deployed a public cloud and other people have deployed public clouds and none of these people have said hey It was so easy.  Although if you look inside DevStack, it's not all that straightforward But running it and upgrading it. They really start to get a bit more complex and So The complexity comes in partly due to that diagram back here But also because other things can go wrong. You can have bugs in the code You can have craft or entropy build up on a node and you can have hardware failures Now hardware is kind of the simplest thing to talk about make all the things high available Well, there's a lot of sessions this week on high availability for different services and and this is an important reason why the craft and entropy thing that turns up it doesn't turn up when you would install your environment and turns up when you upgrade from grizzly to Havana or Havana to some letter begin somewhere beginning with I and bugs Really really interesting to the focus we're trying to deploy from trunk even snapshots from trunk The thing about the release is that it's a well-known quantity other people deployed it three weeks before you You know what their experience was you can take an educated guess about whether you're ready to upgrade or not But if you're trying to run from trunk and this session isn't about why you should or shouldn't do that But if you're trying to or if you just want to have the ability to do it You have to expect that you're going to run into bugs daily new ones fun ones So you need to be able to do CI CD continuously integration the code and Testing your deployment before you do it or else you'll find out about those bugs when users hit them not when your test environment does But how do you make sure you do that with exactly the same tools and processes that you're using to do the deploy? If your test is different than your deploy the results of your test are no longer reflective of the results of your deploy So the triple O project open stack on open stag is about doing continuous integration delivery of an Open-stack production cloud or a test cloud, but primarily we're aiming at production We want to drive the maintenance and installation costs down they're not long enough at the moment How far down can we drive them? What heat? Plast Nova Bear metal We think we can drive them very very low We're going to encapsulate the installation and I prefer oh, I should I should say a caveat to the beginners I'm going to talk about some science fiction in this talk not not a lot We haven't got this thing fully working yet, but we're a long way down the path with Tim Miller who's been doing most of the work on the The heat rules for open stack for us was saying earlier. It's about 99% there. So Once we're at the point where we've got something working and scaling then we can look at actually making it better and better and From an operations point of view one of the key things is that we want the same API for deploying scaling and managing the cloud That we use to deploy scale and manage applications in the cloud because then the skill sets and the knowledge that you have are Reusable and the monitoring things that you put in place to monitor that API apply at both levels So this is the story that we've got Now it starts with a developer making a change because we're looking at continuous deployment deploying off of truck From the change that goes into the Zoolger sort of system We've got here in public open stack, but you could also run a private instance of all the code because it's all public it's all open and You'll build an image that contains The changed code if you made a change in Oslo That change might be five or ten images, but if you made a change just in Say the quantum API server you probably only need one new image, which would be a new quantum API image You deploy that to be a metal and you test it you make sure it works and runs its unit tests and that kind of minimum Degree of capability, but you then deploy it into a production bootstrapped cloud So you start a cloud on one machine you scale it out with this new image And with the old images so you're testing cross version compatibility, which is one of the weak points We currently have in our CRCD story for all of open stack But when you're deploying to an existing cloud, you don't magically flip all your nodes from grizzly to Havana You know, it's not like we're done It's actually even with the best deployment technologies around it's going to be a 10 to 15 minute exercise to do that for a large cloud So you're going to expect API requests coming in on one version and being satisfied by Backends running either the older version or the newer version. You've got lots of scheduling issues to worry about there We want to make sure it works. So we put load on a cloud and we do that upgrade Assuming everything comes out okay, we then take the result as permission to go and deploy and Here's the key thing what we deploy is then the same images we use to test we don't do a separate build process We don't install software into existing environments We take those images and we deploy them and so this is this is the overview. I'll go into all the details further on the Problem space that we think we're dealing with is one which has these separate columns which is provisioning of Machines software installation and machines configuration of the machine Managing state managing different database schema versions database migrations Swift ring transitions. These are big state changes that can take a significant period of time to complete All these slides are going to be published So if you guys are taking photos to make sure you have the slides for later You can get much better version from my Twitter stream later and Finally you've got orchestration which is about making sure the right machines are only the right endpoints and that all the machines Know about each other and it connected and glued up properly We've got a list here of some of the different products in this space and our perception of them so Razer does provisioning and a little bit of software puppet does software configuration and state management, but not really that much orchestration and I'm I can guarantee that everyone who's got a vested interest in any of these products will have a problem with this slide so I'm just gonna say this is our view on it and The blue boxes at the top are the components in the open stack that are responsible for these things Disc image builder open stack configure plier and open stack config refresh are three things that we've been building specifically for this They're on stack forge now We're looking at what to do with disk image builder. We might Propose it to be promoted to a full-blown project or we might roll it into this of glance umbrella because it deals with disk images also config and plier and config refresh are Very very small tactical things just so you don't need the full-blown puppet or a full-blown chef to do what we're talking about You can replace them by using sheff or puppet if you if you feel that's in the the right way forward or juju so Nova be a metal is a key component for this because we need to be able to deploy things to actual machines and Nova be a metal can deploy a disk image to physical hardware Heat is as I said Hawker's orchestration our Clint has a talk I think on Wednesday or Thursday about running open-stack with it which goes into the details of our templates and how they all tie together disk image builder is A tool that just knows how to take an existing cloud image like an Ubuntu published cloud image or a red hat published cloud image and transform it to install software on it and prepare it for run as Element in a heat deployed environment so you can use disk image builder to put something like a dupe on a cloud We're using it to put the open-stack components on it on an image And we we build two big sorts of images We build one image for bootstrapping with everything glommed into one big machine And we also build images that are very targeted. This is a Nova be a metal computer image This is a glance image And that's how you get horizontal scaling without any craft because you've got a clean image on every single time Who here is not familiar with Nova be a metal? Right, okay, so Nova be a metal operates like a Nova compute Process it sits up as far as Nova's concerned It is a Nova compute process and it has got resources that can manage But it doesn't put itself in the compute nodes table what it puts in the compute nodes table Synthetic records that refer to actual physical machines that it can deploy to and whenever it deploys an instance It takes an entire machine. It never takes a partial machine and the way it does the deploy is it uses PXE and IPMI IPMI or any other power manager to to reboot the physical hardware and then the PXE boot process to Copy a RAM disk of our own on and then that RAM disk Exports ice guzzly and we copy stuff on for all the gory details see But the key thing is it's an over API and it's be a metal and it's a machine image It's not an installer so you're not running an installation process You're taking an actual ready-to-go image and dropping it on He I mean it's got all the scaling and a bunch of other things But the key thing for us is it's the glue it's the thing that's able to say I know that I need a rabid mq server and a mysql server and a Nova API server and I need passwords from this one to be handed into this one and this one here needs to pass Connection details back here and can just handle that flow of information configuration metadata between machines and It doesn't do anything within a machine. I mean there are tools that specific to it that can do stuff within a machine But essentially all it does is provides metadata and Delivers the metadata to the machine and then you take that over and you run with whatever you want to run with Now as I said, we can use cheerful puppet But we've written a very very small toolchain that will Just enough to do to do what we're doing So we've got templates for this that they're not in stack for jet They're in this open stack ops project, which is going to have ref stack and a few other things turning up there And those templates Describe the metadata that he know it needs to know to be able to describe an entire open stack configuration It's not finished. It's work in progress Now the really nice thing is that when something changes in the environment You need to take actions on your other nodes like if you turn on a new Nova API front-end somewhere It's going to need credentials to talk to rabbit And you probably don't want all of your machines using the same credentials to talk to your queue Because if one machine gets compromised everyone is compromised at that point So when you turn on that machine you want to ask the rabbit MQ machine to create a new user Set it up and give the credentials back and heat triggers are just a perfect way to do that. So the You export the presence of the machine into heat The rabbit MQ machine is listening for an event. It says, oh, there's a new machine that uses me I'll create users for it and it exports that back in targeted back to the machine that just got added So you have this information flow back and forth Within the images that we build When something changes We've got several different sorts of changes that can occur. It might be something very trivial In which case we want to just restart the services that were affected It might be something more substantial It might be something where we need to shut stuff down before we make the change take place a new KVM library version or something or it may be really substantial. We have to reboot the machine because there's a new kernel So we've got a very very simple model in this we say We're going to do something shut down anything that's fragile Take the new metadata write configuration files from it start up services again and then run migrations and The restart point is where we'll just do a check and say hey, there's a new kernel. We should reboot the machine and When the deploy is finished we notify heat that this has been done So at that point heat can say hey that machine is completed I can move on to the next machine how many machines you do at once is going to depend on the size of your cloud You've got ten compute nodes. You probably want to do one at a time, right? If you've got ten thousand you might want to do more than one machine at a time We're using golden images for this now Golden images can mean a lot of different things to different people. So Let me define really precisely. I mean we have a disk image that represents a running version of software It has no configuration on it or none of the configuration that settings that we'd ever change and it doesn't have Seed databases for my sequel or anything. It's just just the software when we deploy it We create a separate petition that we're going to store the state in Then when we redeployed and we rebuild that node we keep these other petitions intact now That's this is one of the bits of science fiction We can't do that yet until we've got the bare metal cinder API stuff in place But was very clear to us how it will work when that's done Conceptually the golden images act as packages They are a they are a thing that describes an intact set of software that works But they describe it at the machine level rather than the individual bit of software level and this is important because when you deploy you don't want to find out about conflicts and dependency issues on the machine you just deploy to so Your unit of deployment needs to be the unit of thing that you test with and so Because to turn on a data center in the first place you have to deploy the machines our unit of deployment is clearly a machine and This image builder I mentioned before is a very very small tool chain. Just a few shell scripts, but very very useful We split out the core which knows how to do Ubuntu fedora I 386 AMD 64 images and the Stuff that's specific to running open stack on open stack So the disk image builder should be useful for people who are deploying Hadoop or other large cluster software into an open stack environment Even if they don't use Heat and they don't use the rest of the tool chain. It's a focused focus tool. Sorry So the way deployments work is that the heat stack is defined in the cluster Heat is driving the nova API to deliver images to machines and its triggers are updating the environment on the machine One thing I skipped over before is that once we have a machine running if we've got a new image to deploy We can do that without rebooting the machine if the software in that machine decides to cooperate So it can observe the heat metadata and see there's a new image ID It can pull the image out of glance and ask sync it across the existing root file system Because none of our state none of our precious data is on the root file system We can use delete after we delete any craft that was there old package versions gone temporary user codes for debugging gone And we end up with something that is exactly equivalent to having started with an image for shout of glance In developer test environments use virtual machines in production use real hardware Now these things combine to give us what we call the under cloud in the overcloud now Conceptually you might say let's have one big cloud It's got bare metal and some of the bare metal nodes are running KVM or Zen compute nodes and then within those nodes will run other things and those services will also be part of the cloud Now there's there's several Pragmatic problems with that in the short term long term I'd like to get to that as a as a capability in the short term Nova doesn't particularly like having really different hypervisors Running in the same environment. I don't know the exact details. Maybe it's false Maybe that she works just fine in which case I'll redo the slide tomorrow But another pragmatic problem is that when you have something virtualized and you turn off the data center Say there's an earthquake and or you know bomb threat you something you have to evacuate or even a catastrophic power failure That's turns off your data center. You don't have a choice about it. How do you restart services if everything's virtualized or if Say all your glance API endpoints are virtualized To bring them up you have to turn on machines. They're running on and those machines are running with Nova bare metal So they also need to be bootable But the metadata that machine will need to know to know which VMs to restart and which VMs had actually been migrated off or were stale For some reason is inaccessible the rest of the networks not running yet so By having a very clear separation of this is the bare minimum facilities to run a cloud and it's the bare metal cloud It's just doing bare metal machines some of those machines will host actual services, but nothing is virtualized You can be sure that your power on story is fairly simple once we get in place the ability to recover without the rest of the network turn on a KVM or a Zen hypervisor and have all the VMs that were running on it before come back with their networking configuration and Everything else intact then you can start saying well, let's mix and match much more freely But the other thing that's nice about having an under cloud and over cloud is that you're over cloud tenants are not special They may be privileged because you trust them to run on bare metal hardware but they're not in Any way unique so you can run several different clouds on top of one under cloud You can run a test cloud. You can run your production KVM cloud you can run dev test cycles for people doing perform at high performance work and It's it's it's an API API is a great So in the under cloud we want a fully high available bare metal open stack Now we don't need swift. We just need glance Nova Keystone heat So it's very small subset of everything that we need But it's got to be fully available because how are we going to deploy? upgrades to that cloud We're going to use the API that the cloud hosts to turn off nodes within it and turn them back on again with new versions of a Disc image in the case of a kernel change rather than the special case I mentioned before We think we can do this quite reliably with just two machines both of them running a full stack Rabbit my sequel Nova API Nova be a metal compute just full h8 up and down Now that's not how you want to scale out when you're hitting thousands and thousands of machines But it means that the overheads are low enough that someone is running a 10 node compute cluster could conceivably Put two small machines aside and and do this without killing them You could do one, but I don't know how you would upgrade that ever Using this methodology because it would be trying to reboot itself and it would just my brain hurts and The over cloud can be because it's running on bare metal. You can run your actual high-priced It can be a full KVM or Zen based Over cloud Here's an important thing the heat that orchestrates the over cloud is running in the under cloud So you need to be able to talk cross-cloud and if you we can expect that there'll be some bugs that will run into we have folk assumed that the Local cloud configuration I've got is authoritative for all of the endpoints. They talk to an actual fact this will be one of the cases where it's not and Because KVM and Zen Nova can boot just Petition images rather than full disc images. You can use the same disc images for your over cloud and under cloud Installation installation is where it's fun. So this is a special case of normal deployment And this is where I think the value proposition starts to become really clear We start with one of these all-in-one disc images. I mentioned before they have got the whole stack But we start with it in degraded mode. So there's no high availability and we can build one of these images Straight out of disc image builder. We don't need an existing open stack to get this going We run I'm sorry sore throat So you run that in a virtual machine on your laptop and you bridge it to the network in your data center Enroll all the machines so you teach it about the MAC address and the physical characteristics of all the machines in the data center And then you just tell heat Please scale this out change me from being a One node everything in one place to a two node everything in one place and it will take one of the machines out there and it will bring it up or under data migration scripts to copy over the MySQL databases to Set up rabbit in HA mode and so on and then you just turn off that VM that you had Everything is now running in HA mode degraded on one of the machines in the data center Do that again heat will ask Nova for another be a metal node that will boot up It will drop a disc image on that that is the same thing It has the whole vertical stack and it will re-associate everything back into HA and you're now fully operational You've got a full be a metal cloud that can deploy to any of the other machines. You've got glance keystone and That I think is probably the simplest installation story. I've heard and this is why I'm talking about because I love it the HA no, so the The HA scale out stuff for my sequel is done the HA order configuration for rabbits not done yet The heat roll heat doesn't yet really know about rolling Deploys so it will if you were to try and upgrade that it would turn them both off at the same time that won't work very well and Nova There's a bunch of little niggly HA things in quantum and Nova be a metal That will give you, you know, you'd have to have manual fix-up scripts at the moment rather than having it just work we Not this is not a forward-looking statement, but Getting all of the stuff or all the polish needed to make it just work reliably is the Havana cycle focus for us So the the grizzly cycle we spent most of the time bringing the bits together Frigging out exactly how things were going to interact and Fixing be a metal to be more production reading and so on so the cycle is is largely polish So that is actually the last slide. I don't know if I talked too fast or whether we're just on time, but questions Okay, so the question is if you've got an overcomputed VM host and you do a deploy to it How do you make sure you don't lose state about the VMs that are running and in particular rollbacks? So I don't think rollbacks are any different to roll forwards really and in the sense that if we have to restart the Orchestration process it will lose whatever state it has that's not been persisted on disk at the time and There's a session on that so I mean to frame things We're interested in making this work by improving the various bits of open stack that need to improve So I would delegate that answer back to Nova and say we need to make sure that Nova Can be shut down on the KVM node leaving the KVM processes running started back up again and any Things that the Nova process itself would have had to do to orchestrate live migrations for instance Should be the next step of that should be picked up and as long as you have the software ready to go So you shut it down and you start it Shouldn't be visible and that seems like a Nova problem to solve that lots of people interested in solving I don't think triple O as a as a program needs to do anything specific there The tricky thing with KVM instance host is the kernel if you want to change the kernel out without rebooting That gets a little bit more tricky. So the code is Wrong button I have a slide with the main I may not have a slide with the main link That's wonderful Robert Okay, so GitHub comm slash triple O slash incubator is the entry point into the The project and that's where we put stuff We don't know where it really belongs yet and it's got to read me there that describes everything and has links out to all The other code now. I have the other links in here Discimage builder configure player and the refresh config which are the two things that take the heat triggers and react appropriately In Stackforge, so if you just look in Stackforge, they're right there and there aren't you know normal review process and so on the incubator itself has Basically documentation and a couple of convenient scripts like take a disk image and boot it on my local machine without open Stack because I want to try booting something that is open stack And that things it'll probably die off eventually all will move them in as helpers in the Nova libraries or Whatever and everything else we've been doing has been done directly in projects like Nova So Devan and is working on Nova be a middle nearly full-time because that needs to be really robust and solid for this whole thing to work Is that? Is that sufficient? Oh, what do we have working right now? So disk image builders basically done. We're very happy with all the The way we build this images osc config a plier, which is just that this template thing. It's done Refresh config is done as well. I mean that the enablers the templates to do open stack Broken into two parts. There's a set of templates that are the Config a plier templates that is moustache templates and they describe the etc files you're going to have on disk They are Basically done for the bootstrap everything in one node But they're not done for the and I want to separate things out into this targeted node and that targeted node That will be fairly straightforward to do once we get to the point where that's a the next thing to do the Description of an open stack cloud and heat metadata. I think that's pretty much complete Probably doesn't have swift yet, and it certainly doesn't have non core things like Bach or other components that people like to drop in But it also is it's very simple environment to work in so it should be straightforward to do that if you're interested the Thing where I talked about we are on the disc. We separate out the metadata that the Persistent state and and your config files that you are changing from the disk image itself is not done Because we don't have sin to be a metal in place yet now There's going to be an unconference session session with John Griffith and myself and whoever else is interested in making Deciding the approach for that Quantum what so one of the things we had to do in the last cycle was to fix quantum so that you could say hey This machine we're booting. It's going to actually have this Mac address Because it's hardware. That's the address on the card. Sorry. You need to deal with that That sort of stuff is largely done At the moment though you can't do PXE booting with quantum So don't hands been working hard on getting a generic framework into quantum where you can do here's some DHCP options To give this particular port inside quantum Once that lands, there's a very small patch We need to do to pass the Nova compute host. It's going to be doing the image Transferral and fast needs to be listed as a PXE host for the node to quantum as part of the config for the network so that they'll be a very small patch I Think that's pretty much the whole state of play so we within a few weeks have been able to say hey Look, it's all working in its polish, but it's so close So there's a kind of squidge. So so one of the interesting things that that is kind of a refinement of this is like Scheduling locality, right? I want to make sure I've got a high available database And I want both sides of it to be in different racks different power zones Which is not quite what you're asking, but it kind of relates to it. Okay, so in terms of having pools of hardware And so on I think we need to solve OpenStack needs to solve Rack awareness in the general sense for scheduling and once you've got that then I think the ability to say hey I'm doing database deploys virtualize or database deploys physical and make sure that they get the right hardware available is As a subset of that problem Is that do they understand? Right. Oh, so who's who schedules on to which which things so when there are two clouds you just point your Thing at the cloud you want to deploy into you. That's the endpoint you use So it's very straightforward If you're trying to do things that burst across two clouds then heat doesn't do bursting yet But I believe there's a session this week on making it do that and for that point you just have two definitions They will say you can burst from here to here Maybe you say start with virtual and if you run out of virtual go to physical or the other way around More interesting to me is making sure that you land on the machine It's really targeted to databases like the best can hardware config for a high-performance database config looks very different To the best config for a virtual machine host So I see lots of schedule work in our future to make that I mean There are hints and there's policies I haven't dug into and it may be just a matter of configuration file writing But someone's gonna have to take the time to really make that very straightforward for people to do How fast can you bring up a 50,000 node environment? That's a good question Now I don't I don't know the actual answer this because we're not in production with us If we if we have to do image deploys So the process for bringing back up so if we fix all the bugs that are related to this I would expect something like turn on 10% of the machines Wait for their power utilization to stabilize just look at a better at a load meter in your data center power bar And then turn on another 10% then turn on another 10% then turn on another 10% and so until you're done And you shouldn't have to care about which machines come on in which order Other than your network switches and even then you shouldn't really have to care Because all of our software should have be able to deal with the fact that in a cloud Hardware fails a switch will die You don't want to have to reboot all of the machines the hosting VMs that are attached to that switch to replace the switch So we should be able to deal with any component going away and coming back in a reasonable time frame gracefully So if you have that I think it should be something like three or ten times the power cycle time plus the boot time for your OS and that should be a constant shouldn't matter how big your data center is it should be just flick on ten percent Wait three minutes flick on 10% wait three minutes And then you need to wait a couple of minutes for things to retry and reconnect and go Oh rabbits actually there and it's usable and you should be done That said I I don't think open stacks really ready for that There's a lot of code that I'm sure hasn't been written yet Needed to enable that right now. I suspect to look something like turn on your control plane your two machines or your 50 machines So you said 50,000 node. I'd expect you'd maybe maybe 50 machines to manage that Because you want to be able to do deploys very very quickly So you're just having capacity there to spread the load out spread the network traffic out One of the future things we'd like to do is to use bit torrent to do the images when we're doing a live push So all the machines can just get local traffic and it can flood Twitter has done a paper about thing. They called murder. We haven't got on to doing that yet But I'm you know, I'm trying to talk as much as possible what we have going today so I think turn on the control plane and You'd probably turn that on database first then rabbit then you turn on the keystone Keystone API your h.a. Proxies for that then you turn on dependent services depend on keystone such as the Nova API and over backends glance and then once those are all turned on You then start powering on at 10% of the time your compute fleet and your complete fleet will be coming up and It's got the key services. It depends on and away you go But because there are two clouds, there's actually two times that first stage So that could be quite an extensive process. I don't think it should be but I just expect it would be today with any Deployment technology in fact because it's an application problem The ability to respond properly when things weren't there when you got turned on is a novel limitation not a Papadoshi for Or anything else Sorry, I don't quite follow the question Any so the Nova be a metal driver can deploy anything that can be written to a petition in a normal petition and It's got no constraints on the host on the operating system. It's deployed So if you have an image of windows or an image of Zen or an image, that's just regular Linux Any of those images can be deployed by Nova be a metal onto a machine So there shouldn't be any limitations on what you can do. I Think does it does that? Okay, so for the triple-o stuff itself we are I would throw 16 giga RAM and I'd big enough disc to run You know six months history of glance images because you can keep the old images and you can roll back and you can say hey Throw him up a test cluster with this. I want to see what was going on six months ago I think something bad was happening and you get some really nice history out of that The reason I suggest 16 giga memory is because if you imagine that you've got Rabbit my sequel Nova API and Nova compute be a metal compute keystone and keystone API You quickly get to you know double-digit Numbers of discreet images and when you do a deploy all of those images have to be read into RAM Before they can be copied out through iSCSI so The image size that of the petition you write on the the far end isn't necessarily connected to the image size that you have with A q-cow to or whatever image, but you're going to take a ram hit on the bare metal compute node when you do this Even we've got some optimizations in place now and there are more we need to do We're waiting on this quantum PXC thing us as I've mentioned before before we can do them all But when they're done you store them on enough RAM that that fits in your working set so that you're never waiting for a disc during a deploy It will have almost no compute work to do at all you could throw an atom processor in there And I think it'll work just fine And the reason and and as much disc as you want glance history But again because you don't want to be hitting disc at all you shouldn't need to worry about this performance It should just be capacity Right, so that was the thing I've touched on before which is the power on After a failure of the entire data center story Pick a service that we might want to virtualize something like I don't know No very hmm Horizon okay, so horizon is something that's got no dependencies and sure virtualize it great Pick any other service. I think you'll find some things that depend on it The conductor service for Nova for example if that's not there you can't bring up other Nova nodes If it's running on top of an over node That Nova node can't be brought up to bring up the conductor service that the Nova nodes need to run on The same goes for a database and for anything else in the under under cloud I think this is solvable, but it's a bunch of engineering work to allow all of the services to come up without their dependencies and Resume operating the way they were when they were shut down No So with bare metal we can write a boot block To reach disc so if the bare metal provisioner is not there the machine just boots up with the boot block and And the heat metadata that was in place at the time of the power failure is still in place on disk It's being written to a persistent file. It's not in the RAM disc. It stays there across reboots It might be stale, but once everyone's connected it can get updated the The only tricky bit is the IP address for the machine needs to be preserved and actually DH client writes that and we'll try And use the previous IP address Now i'm not certain that we've got the configuration absolutely right to reuse the IP address when DHCP isn't available But that is an existing feature of DH client that we can use yeah, so one of the big things is being able to recover from disasters and I'd like to get to the point where everything is is virtualized turtles all the way down Because they'll give you greater hardware density But and here's the thing Another approach to that is to just run multiple services that can coexist Within one image coexisted and not virtualized at all Now that's obviously not a general solution for any arbitrary bit of code But for just running open stack enough to get open stack up. It works fine, which is why we've taken that approach. It's simple and yeah Like I say, I'll be so policy versus Mechanism policy wise for the deployments on putting together I need to be able to do power on reliably and the things I mentioned before reasons why that won't work Will the triple o heat stacks that that are being built be ones that would support that if you wanted to roll it out that way Yeah, absolutely. I don't see any reason why people shouldn't be able to do that if they want to if they're confident in their power on They'll never need to do a cold power on That's their choice using using what Mesos. Okay. Yep. I don't know I've the HP's a big company and we've got lots and lots of Things happening. I've been focused very much on the this deployment story and for this deployment story We we don't have enough. We don't have it all working yet. So we haven't really been in a position to branch out into more esoteric questions Yeah, it's So, I mean these nodes are just running straight, you know, red hat or Ubuntu, whatever your preference is We are Ubuntu folks so we're developing on Ubuntu, but with with The software you install on it. We don't place any restrictions on how it works or what you can do with it I've checked my twitter rbt columns on twitter and I'll put them up after the talk Rb Rbt columns Yeah, it does in fact So, yeah, rbt columns at hp.com is my email and the first part is my twitter handle So I'll put the slides up there and you know, soon as I get online So Probably we should have everything If we don't have everything working in Havana, then there's going to be a problem for me anyway The Amount of work we've got needed to get to a minimal functional set is fairly small So I'm I'm confident that Havana will see this being usable So I think folk from the next session is starting to percolate in Um, you can grab me outside if you've got further questions


So, next up for you guys, we have pretty much the debut of the U.S. Float Tank Association that's here today to present themselves to you as an organization. Some of you are a little familiar with them from going to the workshop a little bit before, but I'd like to invite Glenn and Lee Perry back on stage to give you guys a little bit of insight onto the new iteration of the U.S. Float Tank Association. The first thing on it is yesterday, I imagine everybody heard Peter Sudfeld gave the history of iris of, you know, all the sensory deprivation work from a long time ago. We have, at the moment, the United States North American Floatation Tank Association. It's actually been dormant for 20 years. The history is here, I'll be reading that to you. And we have a five member called the forward Board of Directors. And who they are are the last Board of Directors from 20 years ago, the way the bylaws are written in order to make it legal. We are still a legal organization, a corporation incorporated in the state of New York in 1984. And when we checked it last year, knowing it was last year in San Francisco, the small group of 30 people that gathered said, what's most important is to reawaken the Floatation Tank Association. Because what we want to accomplish is having floatation tank centers throughout the U.S. that don't need lifeguards and, you know, they don't have to have all these accoutrements that stop them from happening. And so we thought if we have a strong body of float centers and individuals that are organized together, then we're a force that can talk to the different authorities and say, yes, this is in order to be a floatation tank association, we're very different from a swimming pool, we don't need to use chlorine, we don't need lifeguards, and this is what we do need. And so we will present to them the kind of things that Shoshana has been doing, you know, this is what we do need, this is what we intend to do, this is what we can do, and we would like to be certified or legitimized. So one of the five people, two of them are Glenn and I, and then there's Tom Fine, who's a psychologist at the Medical College of Ohio, and John Turner, a physiologist from the Medical College of Ohio, and Faustin Bray, who's, I'll call her, an artist from California. And Tom and John could not be here today, but they did send a clip. It's about six minutes long, and it has to do with a continuation of what Peter was talking about yesterday. So we're going to see that first, and after that, then this report about floatation tank association follows and tells us what happens next, up until, and then it goes up until today, and we'll continue from there. So Ashkahn's going to get it turned on. The deep self provided me with a practical knowledge about tank. When I shared the deep self with John Turner, it resulted in a research partnership that spanned many years. Hi, this is John Turner. You know, I read the deep self. It was really intriguing. And so we wanted to do some studies, classical conditioning, relaxation, but they included self-reports or emotion, but we were also interested, as well in the physiology that went along with the relaxation proposal, therapeutic use of the tank for treating stress-related disorders. We were able to pay private funding for this purpose, and Zadu, off we went, and between ourselves and our subjects over the years, we logged thousands of photos. Around 1981, we began corresponding to a piece of film. We've been researching isolation for us for many, many years. Actually, the name Rest was filmed by Ron Vorre, a grad student of ours. We were in control of the isolation. Right on the circle back and forth on the knee. John Miller would be in on this. First he said, see, I'm going to see. Kind of like that. But then when we settled with Rest, he said it should be restoring energy safely traveling. He suggested that we publish our work with hypertension in a journal called The New Research Therapy. He submitted it, and the portion that they have accepted, and that was the first publication. Two researchers are using the float tank as the focal point for serious scientific study. They're using the tank as a tool to help reduce pain and relieve stress. How does it work? We're trying to create an environment which has minimal input to the senses. That would include vision, hearing, touch, including a sense of gravity. Also, it provides an opportunity for the individual in that environment to be more associated with themselves because they don't have this output from input from the outside. And in the case of Steven Essek, only your own record store only adds to the tension. Interested in studying the subject of stress, Steven was a likely candidate for close research. Hormone levels measured in his blood prior to floating were compared to levels taken when he emerged, since certain hormones are believed to be stress related. Love pressure also is taken on a before and after basis, and electrodes attached to his forehead and jaw and tongue to monitor changes in muscle tension and pulse rate while he floats. After a quick shower, Steven was ready to step into this unique cell of serenity. The tank itself provides with a fairly powerful clinical tool in helping people whose systems have gone out of regulation and have what we call disorders and dysregulation like high blood pressure or other stress related disorders to learn to re-regulate themselves and bring these stress related disorders under a certain degree of their own personal control. We held the first international conference under us in 1983. Pete Silverfell and Jack Stanley, a group of Jets, organized that. We had about 20 papers presented, and those were published in 1985. We formed IRIS and IRIS was on its way to that point. After the 1983 conference, an explosion in the tank had occurred with a wide variety of tanks. We were fortunate enough to be in Ontario. We also had a research comparator to the wet flotation. In total, there were six international conferences on rest. The last one was held in 1997 in San Francisco. While IRIS faded, other researchers did carry on with the work including many in Sweden and some in Japan, but we see research in the interest of the public. Our experimental work involved measuring a wide variety of physiological variables. Many of them related to stress. Our plot work looked at essential hypertension, chronic pain, and rheumatoid arthritis, using flotation rest as a treatment for those. We made many publications, over 20 publications in record journals or news articles or books, and we were involved with the editing of four books. Here are some pictures from the various IRIS conferences. We carried a re-found on this. Peter Sootfeld, myself, John Turner with one period, and John Turner myself with John Ford. We're very excited with the resurgence of interest in the clothing that's occurring, and we wish everybody great success in being able to resurrect flotation tanking sensation and bring more and more people to this exciting technology. How many of you read The Deep Self? A couple? Well, it always intrigued me. John Lilly at the beginning of The Deep Self gives his description, the flotation tank. This place I found, invented, discovered, was led to, guided in such a way that I hunted for the first one of these places, or I needed such a place for my own research on myself, the universe, the divine, the new and unexpected, never before seen or programmed by any known persons, the isolation tank, flotation tank, the solitude tank, the womb to tomb wet box. The place one can rent for money to seek nothingness. The isolation, solitude, confinement, happiness, freedom, domain. So, that's what we're working with. Move it to the light. Move it to the light. Okay. Well, I'm going to have to, I'm going to work from here because of pages. What I'm going to do is kind of give you dates as to when things happen, kind of put us in context of where we are now, and then we're going to go into, you know, really making the formal, breaking the bottle over the formal opening, reopening of the flotation tank association of the U.S. Let's see. We had the, no, no, not that one. So there was the woman who actually started the flotation tank association was Alma Daniel. She was talented at organizing and she had already formed an organizational, organizational infrastructure with a name, newsletter, a four member board of directors, an advisory board with John Lilly, a large base of correspondence in the U.S. and Europe, and a certificate of incorporation from the state of New York. Her stated purpose was the safety and comfort of the floating public, the physical and psychological considerations, and she became the executive director of the flotation tank association. In winter of 1984, Tony Lilly suggested that the advisory board of John Lilly, Tony Lilly, Jay Shirley, Tom Fine, Terry Hunt, Peter Sudfeld, John Turner, Glenn and Lee Perry become members of the board of directors in order to become voting members. So the same names keep on bouncing over and over again. For many years it goes on like that. So what started happening as this started coming into the news, the media came into play. We were all over the news. We were Esquire, Vogue, New York Times. There were 500 written requests for information. Connecticut was the first state to say, okay, if you want to have a tank center, you don't have to do anything, it's legal. Summer of 1984, nine new tank centers are opening and FTA is gathering data to print a directory of float centers. Yeah, that's great. Fall of 1984, France pops. They invite John Lilly to come and speak. 200 people show up in Paris within one year's time. Four tanks for different tanks are manufactured and they had 125 tank centers opened. That was one year, 1984. Elma Daniel went over there and she said that the lack of training of those bringing tanks to the public made it so that the tanks didn't work, they didn't know how to invite people to come in, and in one year all that vanished. 1985, the centers are growing rapidly in the U.S. There were lots of single tank centers that opened, just one tank, like what we have now. And they were opened by people who loved floating. They loved walking into tank centers and they saw somebody very relaxed, just sitting around, looking good. And they said, well, it was still a time when work was not a very good thing. People didn't have good jobs that they liked. They thought that work was the bad thing that you did, not like what Graham is doing with the work he's doing. Your work is your life.  We heard reports at that time that the tanks were not clean. The temperatures were too warm, too cold, and nobody cared whether they were clean or not. The center operators were far from being experts on the working of the tank. There were even reports of women floaters being hassled by male center operators. These centers were opening and closing quickly. So here you have this kind of a trajectory of an industry moving up very fast. Membership in FTA at that time was bigger than 220 members. And now the next thing that happened was the first FTA conference. Oh, that's not right. It was in, let's see, what year are we in now? This is 1985. And Iris, the organization that Peter and Rob were members of, were putting on a scientific conference in New Orleans. The subject of that conference was mainly flotation.  And Peter Sudfeld made the address there called The Research Connecting Science and Business, as well as a bunch of successful center operators sharing their experience, just like today. The flotation tank people were finally meeting each other and exchanging information about their successes and failures. Michael Hutchison, the author of the Book of Floating, he arrived unannounced and the mood of the event was a huge celebration. The conference proved the growing influence of the floating experience. And that was the official recognition of the flotation tank association. 1986, how long ago is that? Where are we, 22? Okay, a long time ago. Alma Daniel, at that time, announced her resignation after that first conference happened. The number of centers in the U.S. is dwindling. The change in leadership and the aftermath of the AIDS scare is right in everybody's face. AIDS had become a big issue in this country. 1986 was Tony Lilly passed. Alma Daniel is going to resign. The first owner's group forms in Los Angeles and meets monthly with their first subject being lucid dreaming. And 1987, the first three issues of Floating Magazine, 87 the first issue, and we have them here at this conference today. Alma Daniel resigned, the clerical duties, and by the March 1st of 87 she was gone. The board of directors appointed Rod Punnett, a Canadian, who had been using flotation in academic research. He had a four-tank center in Vancouver and also had some financial experience in his family business as the treasurer. So he could summarize the financial status of FTA with hopes that he could become, the board wanted him to become executive director. The board appointed Rod Punnett and myself with the goal of getting, we were an ad hoc committee to get an objective report of the current situation and to support the board in determining the future direction of FTA. The country was still in the fears that surrounded AIDS. That was shortly after Rock Hudson had died. He was the big star who died of AIDS in the U.S. and reached a kind of fever pitch of fear about AIDS in this country. The public was very shy about using public water environments. Rod Punnett and I completed the report when his health demanded that he leave California, return to Canada and his health insurance. Finances of FTA were pretty much used up with the money that the board of directors voted to pay Alma based on her request for unpaid debts. Early in 1987, the number of North American centers had dwindled to 55. The manufacturers Flow to Relax was sold and closed. Ova joined forces with Flotarium. Flotarium had a major fire which shut them down. Samadhi Tank Company survived a partnership that cost them the Beverly Hills Center. They continued to manufacture tanks in Los Angeles until that factory burned and production was moved to Grass Valley where a small single tank center was built. The board of directors meetings disappeared as the members dispersed into the responsibilities of other aspects of their lives. FTA was now dormant. University of Toledo kept medical research going until early 1996. Even though research couldn't be supported in the usual manner, it was funded by giving students laboratory experience under the teachings of Tom Fine and Dawn Turner. Now here we are, we're quiet, we're very quiet until 2011 last year where there was a public upsurge in interest in floating. The Float Summit meeting called by Mark Frickle, an American living with his family in France, who wanted to breathe some life into FTA and ask that small group of 30 if they would like to revitalize FTA and the answer was yes. Which really brought us here is that this current board has been meeting for the past year trying to figure out what are we going to do. We knew that a conference would be the next thing to invite people who are still working with tanks to get together and you know, let's see what we can do to get everybody to join together in an organization that could show its muscle to the various people who were stopping float centers from being built that was number one purpose and number two was get the name of floatation out into the world. And so that's when FTA heard about it, we said oh we're going to have a conference and then Float On said well we want to have a conference and we said well let's join forces and see if we can't do this together and that's what happened. And I'm thinking this was a really good idea all the way around and Float On has been an outstanding partner. And some of the things like the last when Graham's report about how to use time efficiently and I think that's just an incredible idea of being able to use centers for the life support really of their owners. It's not just, you know, we're no longer working because we have to but our work does become our life and this, you know, so many of us here are on that mission we want to get floating out there. What a difference it will make in the world to have floating as part of the system. It was like the, there was this princess from Dubai who showed up at our center. Move this way. Into the light. So she, when she came out of the tank she had that glow on and she said that her country is governed by 17 ministers and that the picture she saw was they would be 17 tanks in a circle, arranged in a circle and each of those ministers would get into the tank for an hour then get out and have their meeting and she thought that might make a big difference in the Middle East. So there, people have a lot of visions about the possibilities of many, many people being under the influence of floating and those of us who work in centers, you know, you know it. You see when people come out of the tank, they're not going to be packing a gun. You know, it just wouldn't make any sense. So, what we would like to do, Glenn, did you want to say anything? The mission includes safety and cleanliness of water supply, entrance and exit safety, water temperature range, 93.5 to 95. Air and water should be the same temperature to eliminate the sensation of air, water, interface keeping a record of float experiences, importance of ambience, a list of things that make this quality experience, sense of security, set and setting and mood employing questionnaires to obtain feedback about floating, physical, mental and emotional use questionnaire based testing to expand knowledge about floating and its benefits. So, we think you might enjoy becoming members of FTA so you can participate in all of the committees that we have. There are going to be a lot more committees. That's, where's, there we go. Oh, I guess we don't get to see the committees until we join. Well, okay. That's an example of one. When Richard, yesterday, is this on? No. When Richard talked yesterday about Awesome, his organization called Awesome, I thought that would be a perfect FTA committee that might turn into something else, so that as you get the instructions as to what to do to join and what committees you can get on, if that was something that interested you to be working in lucid dreaming, then I think that will be something amazing. And that's the kind of things, in addition to being able to be accepted by different health boards, but to be doing work, not only like the fibromyalgia thing, but there are so many different areas that we could be interested in. And because having the ability of using the, you know, online resources, we don't have to be all in one center. We can be all over the world, definitely all over the United States, and having committees that meet together online, and are pursuing things that other people could be interested in and produce the information that would come out of that. There will be a bunch of benefits from joining, including 20% reduction on conferences that are FTA-sponsored. And you will get to, we will disseminate all new news. So any research, any studies, any new data on how to interface with health departments and so on. For instance, if we look right here, you can see that we have a place where health department information is. There we go. So here's three documents that you can give your health departments to assist in communicating with them. And as we continue to get new things, new things will go up here and we'll send stuff out to the members to let them know about it. So we'd like y'all to join. And you can join right now. You can go to the membership. I think Graham's going to help to set that up. Okay. Well, you can go to your, with your computer, just go to the members only. Oops, sorry, we don't want that. The membership. There we go. The membership part. And then you just scroll down. Oh, I got the membership one rather than the members only. Yeah, that's right. Oh, go to join. Thank you. And then a regular member is 50. Manufacturer is 250.  If you have two or three tanks, it's 200. And four or more tanks, it's 400. So we'd love to have you all start registering. Hey, guys, and just a little encouragement too with the FTA, which is we've been working with them on a subcommittee, I guess, unofficially since we're not actually members and hadn't really joined up yet. But we've been helping with the health department committee, which has been amazing over the last year. Well, they've been kind of trying to get formed. And it's really astounding just the ability to talk and reference with other float tank people in the industry, even just in this small group, has been incredible for the amount of information we've been able to gain and put together in regards to dealing with health departments and specifically just figure out what's actually going on with a lot of the protocols and a lot of what's happening with the chemicals. And I really like just being here too and looking around and getting a chance to hopefully, you know, some of you for the first time interact with other people in your field. I think it's really incredible. And it gets lonely sometimes owning a float tank center, especially if you're not like in Portland and a lot of other people who are doing it. I strongly suggest signing up for this with whatever, even if you don't have a center yet, just signing up for the $50 membership. And it's going to be a lot of a building process together too. We already have some materials put together. But in general, I mean, this is the beginning and you definitely want to be a part of this if you're in the U.S. especially. So that's all I had to say. Just my little float-on endorsement of the FTA. Thanks. And don't leave.  And this is Dave Wasserman, also as a member of this committee. If you have any questions about how to interface with the Health Department or anything having to do with Health Departments, now is a good time to ask questions. Also very true. I have a Health Department question over there, Katrina. I think once you join the FTA... Oh, so let me repeat the question really quick. Good question. And that was, will you have access with the Health Department by joining the FTA of a lot of letters or just kind of templates for contact and how kind of the wording to get in touch with people? Did you want to tackle that? That's exactly what I was going to say. Oh, gotcha. So yeah, I can tackle that, which is, yeah, we definitely hope to provide as much information as possible and as much help as possible in general to getting float tanks all on the level and passed in the different areas. Any other questions just on health regulations or on, yeah. Good question, yes. Do we have different rules or regulations in different states? Yeah, there are. I mean, there's a lot of different, slightly different or very different. Ashkan was gracious to call and investigate about 30 states. I think all 50. All 50? About 40 actually, so. Okay. There's actually, so there's only one rule that all states share the same, which has to do with what type of grate you can have on your inlet. So beyond that one thing specifically about inlet grates, everything else is decided on a state by state level and then below that on a county by county level and then below that on a city by city level. So it's a big hodgepodge. But you ended up actually being able to speak to a lot of different representatives in 40 states and getting much more information. He started compiling this information. So that's sort of the first step or the first document we use when someone calls from a state will look there and see if there's absolutely no regulations. But it still doesn't necessarily make it easy to get a permit even if there's no regulations because even if they don't, some of these officials don't know that there aren't any regulations. So it's still a process to go through. And in typical float-on fashion too. We put that up online for you when we announced that down in San Francisco. So if you go up to floathq.com, our main website, slash summit, because that was one of Mark's float summits down in San Francisco, you'll find our open source beginners guide there as well as the calls around to the different states for the health departments, which the information now is about a year old. A little over. And it's changing. Yeah, and it's changing. But you can find at least a good template for where things were a year ago there. And any questions to just about the FTA in general, even not specifically about float tanks? Am I right here? Yeah. Is the question why don't we try to tackle it on a national level and not a state level? It's because most of the laws that have to do with it and the regulations are decided on a state level is basically what the thing is. I mean, doing it a national sweep would be amazing. But there is not necessary, like the body of regulations that regulates these sort of activities just happen on a state level. There is an effort happening right now in the pool association, which then you got to go back and forth whether you want to try to enter yourselves into the pool association and find special regulations or that we want to just say we are something completely different. We have nothing to do with pools. So that comes into the play. But the pool association right now is making an effort to take all these 50 states regulations and actually turn them into one standard that is adopted by every state. So that effort's going into play. It hasn't been enacted yet. It's in the process of it. So if that happens, there is the possibility of trying to enter into pool regulations with our own rules and have it go national. But the current state is that, yep, it's just every state is doing its own thing. And that would be about a three-year process that's just started again this last September, a new round. So our committee bats around these ideas and we're trying to figure it out. And we'd all really like it if it was just a national decision instead of independent states. Well, we're trying. Oh, yeah. And this right here is a standard that the committee here has tried to put together as to what we hope are just really good solid practices and regulations for keeping a sanitary float tank. And we tried to make it exactly that. It is what you need to do to make sure your float tank is sanitary. And so, yeah, we have this up here. The more people abide by this, the more legitimized it'll just become by the nature of everyone following it. And that I think is a really big step. If then you are struggling with a health department or going towards something and you say, look, we use these standards and everyone in this industry uses these standards, that just gives those standards legitimacy. And that's an important step towards actually having it just become, I mean, it's how the world works, everyone's like, oh, yeah, of course. These standards that everyone uses, and all of a sudden, those are official. So it really is just a group effort of all trying to come together and get on the same page and have an outward appearance of this real big, unified thing that seems to have been around for hundreds of years. And then that's just it. Then everyone will completely respect these forms and that's a good step towards getting them into actual state regulations. Yeah. So the board is going to be expanded and when you become a member, there's a couple of things that you can do. There's a members-only page. And so once you become a member, you should go to the members-only page and you can nominate people for the board. Including yourself. Including yourself, right. And once we have those nominations, then we'll let you all know who those nominations are so that the new board can be elected. And in addition to that, you can also, you'll see the committees that we have so far, there's going to be more committees and you can make suggestions for being on a committee or you can volunteer for being on a committee or more than one if you want. And I think that's the next big step that the FDA is trying to take. Pretty much as soon as this conference is over, holding elections to flesh out the board to 15 people rather than five and creating a term structure and yearly elections to kind of keep an active board going. And then once that board is assembled, the actual organization will start to exactly form these committees and start to produce and move. Yeah, it's an exciting time and we'd really like you to be a part of it. And the way the term limits will work too, but the goal of it on that is we'll kind of have rotating terms. The goal is to get up to a 15-person board, hopefully with three-year terms and then switching out five members every year. So every year you'll have five new members coming on board. And the forward board, is that what you were calling yours? That's what it was called. Yeah, yeah. And so they'll be serving that kind of first five positions for three years and then that position will be, we'll go up for election after that and we'll either serve the two years or one year initially upon signing up here. And then after that, it'll kind of hit this regular system of everyone gets to serve three years. Yeah, yeah. And one in three years, I think. One in three? Yeah, the five people on the board now will do two more years to complete their three-year term, including this first year that they've spent organizing it. And the rotation will just continue like that? No, the thing... Yes. You can tackle that if you want, Ashkan. The question too was, when we're talking about health departments and getting past there, are we talking about just clean water or are there other issues that come into play there? I mean, clean water is part of it, but there's a lot of pool regulations that have to do with other safety around the pool. I mean, slipping and like everything that goes into having a safe pool environment. And all those things start to become imposed on the float tanks as well, which is why you start to get things like lifeguards on duty. Continuous filtration is a really big one. That's just really standard for pools is to have the water very slowly filtering, which makes sense for a giant body of water. But that's just not how float tanks work. We can't have water filtering while people are in there because it's loud and you'll be sloshing around and stuff. Yeah, I mean, there's, of course, the use of chlorine and bromine, which is its whole own other thing. I mean, some states don't even allow bodies of water that aren't cement in the ground. Like even those fiberglass hot tubs and stuff aren't allowed.  Every state has lights, like some states are like, no, you can't have it dark in there. So yeah, there's lots of things that go beyond water sanitation that also are the float tanks just butt up against because they're so different and they're just not meant to be put into the category with all these other regulations. Any other questions? Yeah. So your thoughts on membership for people outside the U.S.? It's same as for the U.S. You'll be getting all the same stuff. I think much of, you know, if you're in Canada, most of this stuff will apply to you as well as the U.S.? Yeah. Correct. The question was, though, is it only members that can apply to vote on the board? Yes. So the question was, can float enthusiasts be members or do you have to own a tank or own a center? And I think that was that first level of $50 was for anyone who was interested in joining. You can join at that $50 level. Sure. Definitely. Yes. Except you, Katrina. Any other questions out there? Yeah. So the question was, do you see the association towards a certification program like the Swedish Association just presented on? That will be an issue for the board. And, you know, the new board, as it gets elected, will decide that. And, you know, we'll come up with our own point of view about how we want to do it. Will you be for it or against it? Okay. Yeah. Hopefully the idea here is that it is really kind of your organization. And the work that's been done so far has really been working to kind of get the legs under it to literally be a legal organization. And once there is a board, the organization will move in the direction that we want it to move in. And will hopefully represent everyone's like opinions and interests in what we want it to do as best as we can. So that's really the goal.  And also to just a note on that is that we've tried really hard to make this as democratic and organization as possible. And part of that too is hooking up the FTA with the helm software that we were just talking about a little bit customized so that member voting can occur really easily on subjects that aren't even as important as elections. And basically so that material that we're planning on doing can get reviewed by every single member who can comment on it and add their own opinions. So really just trying to engage people as much as possible, yeah, and what actually happens there. Yeah, we'll have a blog. Like, two of them. The other thing is if you have reactions, suggestions, thoughts about the next one, what you'd like different, what you'd like added, what you'd like expanded on, what maybe wasn't at this one that you would like to see, just send us an email. In fact, communicate with us on anything you'd like to. We want your input. Yeah, we're a pretty sophisticated bunch of people who can, who probably have some pretty strong ideas. Probably most pretty good. What do you mean? Except you. Great. Any more questions we had? Perfect. So we're going to head into a break then. The FDA is going to have a table right outside these doors with the laptop out there with this membership screen open. We're actually going to take a, I don't know, the 2025 in a break here. It seems like how long our breaks end up anyway, so that's perfect. So I'll see you guys back here in about 20, 25 minutes.


Hi everyone, it's Vicky here with exciting news! I'm one of the Wanderlust 2021 teachers. If you are not familiar with Wanderlust, then this is a year-round art journal online course. Amazing teachers are participating, but I'm gonna let Kasia, who is bringing all of us together, to let you know more about it. Let's face it, 2020 wasn't great. We've all had to deal with heartaches and let go of our dreams and plans. I am Kasia Avery and I will show you how to make your 2021 a year of positivity and creativity. Join me in 27 renowned teachers as we help you discover your inner artists on our online year-long course called Wanderlust. About mixed media or journaling, the most forgiving and freedom-infused form of art with endless opportunities. This can be your new favorite form of self-care. This is our sixth year and every time we have inspired thousands of people on a journey of self-discovery, self-care, happiness and self-expression. Don't believe me? Just check out our Wanderlust stories to see just how much our customers love the course. We don't know what 2021 will bring to this world, but we know you can take this step right now to ensure you bring creativity to the table next year. Become one of us today. So back to me again and I just want to let you know that this is going to be a super fun class. So many amazing teachers, such diversity on styles, you will learn lots and lots of new techniques. For the first 2000 subscribers there is an early bird prize, so make sure to check that out. You will find links down below as well as on my blog. Thank you all so much and have a wonderful day.


Although in the moment things can feel overwhelming and like there's nothing else that matters in the world is to in that moment to take it step back and give yourself some time to gain perspective. We often feel emotions intensely and can become overwhelmed by really intense emotions but just by not reacting straight away and taking a step back it allows us to see the wood from the trees. There's a trap that I've got into a lot of times during my life where, you know, particularly when you have something that you're trying to do and it's just not working like with trying to sort out the Wi-Fi and the podcasts and stuff and you kind of feel that sense of time pressure and you kind of have in your head that we're going to be doing this and it's going to be finished then and then I'm going to do this and this and sometimes life doesn't go that way and life throws you some curveballs.


to lecture number 11 of the course quantum mechanics and molecular spectroscopy. As usual we will start with a quick recap of the previous lecture and then proceed with the lecture number 11. In the previous lecture we talked about the electric field and magnetic field of the propagating light. So if a light is propagating along a direction R or let us say its vector is represented by R then there is a electric field which is as a direction E and the corresponding electric field is E and there is a magnetic field B with the corresponding direction, okay. Now there are three components of both electric field and the magnetic field. So E will consist of E x, E y and E z. Similarly the magnetic field will have three components that is B x, B y and B z, okay. But in Hamiltonian we have potential and not the field. So we need to convert this into potentials. So there is a transformation that takes the electric and magnetic field to scalar and vector potentials. Phi is the scalar potential and there is a vector potential A which will have three components A x, A y and A z. So totally we have four components, one scalar potential and three vector potentials, so four components and these four components must be reduced from the electric and magnetic fields which have six components. The relationship between the magnetic field or electric field with the vector and scalar potentials are E is equal to del phi minus dA by dt and B is equal to del cross A. Now what we will do is since we have to go from six components to four components of course there is some redundancy. So there are infinite ways one can have this transformation. One of the transformations that we will call it as Coulomb gauge in which we say phi is equal to 0 and del dot A equals to 0. So there are six components, so you are reducing to four components with two criteria that are fixed. So therefore now the transformations becomes easier. Now in a plane wave notation A is given as A is equal to A naught and it will move in the same direction as electric field this one into e to the power of minus i k dot r minus omega t sorry this should be plus e to the power of minus i k dot r minus omega t. Now this is exponential i theta plus exponential minus i theta so this is proportional to cos theta and you can see the electric field is a time derivative with respect to vector potential.  So this should be proportional to sin theta. So which means the vector potential A and the electric field A e are out of phase with respect to each other by pi by 2. So they are out of phase by pi by 2 okay. Now let us get on to the contents of this lecture. For example if you take a charged particle and you put it in the electric field or electromagnetic radiation that is light then the charged particle experiences what is known as Lorentz force okay. This Lorentz force is experienced by charged particle charged particle in electromagnetic field or this electromagnetic field is nothing but light. So if I expose a charged particle to the light then it feels a Lorentz force. So I will write Lorentz force as F L this is equal to Q times electric field plus V into B okay where you know this is electric field, B is magnetic field, V is the velocity of the particle. So of course that will depend on the charge Q. So more the charge more will be the force. And atomic systems of course atomic and molecular system the charge is fixed because the electrons have fixed charge okay. Of course nuclei could have a different charge which could be multiples of multiples of the electronic charge E. Now this is the force that is called Lorentz force but let us take a small teetor and think what is force in terms of classical mechanics, force in classical mechanics okay. What is force is consequential force F equals to mass into acceleration okay. So this is mass and this is acceleration. Now acceleration is nothing but rate of change of velocity. So this is nothing but F is equal to m times dV by dt that is nothing but rate of change velocity okay. Now mass is a fixed quantity it is a number for a given particle. So one can write F is equal to d by dt of mV okay. Now what is mV momentum this is nothing but momentum okay. So now force can be written as d by dt of mV that is nothing but d by dt of P. So force can also be reconciled as rate of change of momentum. So this is nothing but rate of. Now let us get to the Lorentz force okay, FL is equal to Q times E plus V. Now in general the magnetic field its magnitude is going to be is much smaller okay. So one can neglect okay and if you neglect that we get FL is equal to QE okay. This is called electric dipole approximation. You are only looking at the electric part electric field of the electromagnetic radiation okay. So we are neglecting the magnetic field. Of course if you are going to do spectroscopy like NMR or EPR this is not going to be valid but for general spectroscopy terms like you know rotational, vibrational and electronic this is valid okay. Now FL is equal to Q dot E okay. Now I can write this as Q times minus d by dt of A okay because E is equal to del phi minus dA by dt that is what we said you know and in the Coulomb gauge you have d phi is equal to 0. So which means E will turn out to be minus dA by dt. Now if I write this your FL is equal to of course Q is a charge of a system so that can be taken out it is a constant with respect to time okay. So this can be written as minus d by dt of QA. Now but force is this is force okay Lorentz force is given by d by dt of minus QA okay. Now force as I said is equal to d by dt of P that is nothing but rate of change of momentum okay. So if you compare these two forces of course force is a force you know whether it is of some mechanical origin or of electromagnetic origin it is a force that is fine okay. Now you can clearly see by comparing these two equation you can see momentum P is equal to minus QA okay. This is the momentum that a charge particle will gain in a vector potential okay. So in your Hamiltonian H what you have we have P square by 2 m plus your potential V of x. Now but P in this case is the velocity or the momentum that particle has on its own but the momentum you put the moment you put the charge particle in the electric field then its momentum is going to get modified. So your P prime will be equal to P plus okay the newly attained momentum because of the electric field P of the because of the electric field and that is the perturbation that you have. So your P prime will now be equal to P minus QA. So your Hamiltonian H will be nothing but actually it should be P prime square by 2 m plus Vx. Now let us write the in terms of okay this is not really the so your Hamiltonian so you write the corresponding operators. So this will be equal to P minus QA square by 2 m plus V of x why V of x because we told you I told you that for this course okay the potential is generally independent of time okay. So this is equal to H into now this will be nothing but what is your P this is nothing but minus ih bar T by dx that is the P minus QA whole square by 2 m plus V of x that is my Hamiltonian. So when I write that so your Hamiltonian H is equal to minus ih bar T by dx minus I mean only looking in the one dimension case okay one can generalize to three dimensions okay minus QA whole square P square by 2 m plus V of x. So this is nothing but A square plus B square plus 2 AB. So A square will be minus ih bar square by 2 m T square by Tx square A square that is B square will be Q square A square by 2 m okay but 2 AB okay or it cannot be 2 AB because they are operator AB minus PA okay. In fact I can take a negative sign outside so this is equal to AB this is minus and this is minus so just AB. So H bar plus H bar bear by H bar by 2 m H bar by 2 sorry ih bar by 2 m okay d by dx of QA plus and if I multiply this will be QA times ih bar by 2 m QA times d by dx this potential V of x okay.      Now in spectroscopy the amount of light is very feeble so that is called weak perturbation in the weak perturbation limit we will ignore the A square term therefore H prime of T will be equal to ih bar Q by m A dot del that is your Hamiltonian or the perturbation Hamiltonian so your total Hamiltonian nothing but H naught plus H prime T so H naught is something that is the molecular Hamiltonian and your perturbation Hamiltonian time dependent perturbation is just given by ih bar Q by m A dot del okay.  Now we know what is the time dependent perturbation okay we will stop it here and continue in the next class.


Hi, my name is Ryan Elphick and I'm a park ranger on the Sunshine Coast. I have the unique responsibility of looking after some of our most beautiful marine parks in the province. Hi my name is Dylan and I'm a park ranger on the Sunshine Coast. I get to be in beautiful places, work with people who are very passionate about their work protecting parks and protected areas. I'm Doug Biford, I work as an aquatic ecologist for BC Parks. I've been doing the job for about 14 years now. The marine park system in British Columbia, which started back 100 years ago or anniversary year in 1911 with the establishment of Drathcona, we protected an estuary on the west coast of Vancouver Island. So that estuary has remained undisturbed by human activities, direct human activities for 100 years now. We can go in and see what the natural function of that estuary is, and then compare it to the other estuaries that are up and down the coast that are being used by humans for all kinds of important economic and recreational activities. Our marine parks and our provincial park system provide a really important role in protecting our shoreline marine environments. Our shorelines along the coast are prime real estate for development, so these parks play a vital role in protecting and setting aside some really key habitat on our coastline. Smuggler's Cove Provincial Park is a special park because it offers a wide range of opportunities for a bunch of different user groups. It has a beautiful terrestrial trail that you hike through a beautiful wetland that's been created by beavers in the park, and at the end of the trail you end up on the rocky bluffs looking out straight at Georgia. It's also a really nice sheltered anchorage for recreational boaters who are cruising up and down the coast. It also offers a great place for kayakers to come in on day trips, and there's even a few campsites where kayakers can pull out and spend the night here in this beautiful, beautiful place. My favorite park is Buccaneer Bay Provincial Marine Park. It's a special place because it boasts one of the most beautiful beaches in Georgia Strait. It's a lovely sandy beach that's inviting for folks to come and camp and hang out and play volleyball, and for folks from the community of Seashells and Pender Harbor to just come over for a brief day trip. Our environment is changing rapidly, and as climate change has an effect on temperatures in our oceans and the sea level in our oceans, it will have an effect on the critters in the intertidal zone here. They are extremely sensitive to temperature change, and it can really affect their abundance and their range and their diversity, and we can use these parks as baseline data to help us monitor those changes through time. So in a place like Buccaneer Bay where we have erosion and accretion already happening as a function of the ecosystem, we may be seeing those functions happen at a faster rate. And if we're able to monitor and understand the changes in the ecosystem and how the fish and the birds adapt to those changes, it might tell us something about how we can manage our shorelines up and down the coast of Burr's Columbia. So right here at Botanical Beach, we have an excellent example of where we need to monitor for sea level rise. This beach that's behind us is a gravel beach backed up with forest, and as sea level rises, that beach is going to move a bit more, it's going to become more dynamic. So the intertidal species will have to move up a little bit, and the forest will have to creep back a little bit, and we can set up a monitoring program to look at that as that changes. When you get to meet people in the parks, they're often at their best because they're with their families, they're on holidays, and they're having an outdoor experience. I like to go out and experience nature. I especially like to go underwater and see the marine life in its natural environment, which not a lot of people get to do, but through my job, I actually be able to bring that back and talk to the general public, integrate that into the work I do in conserving the natural environment and helping people see the natural environment is really the core of my values, and I really enjoy being able to work that into my work life. I love going to work every day as a park ranger on the Sunshine Coast, because I get the great opportunity to share these beautiful marine parks with the public, and hopefully when they meet me and talk with me, they walk away with the new appreciation for these marine parks and how they can enjoy them responsibly.