Cool. Well, I'm Jeremy Klein. You can try pronouncing my name, but I really don't worry about it. That's fine. It's a French thing. We'll be talking about messaging today. Thanks for waking up that early and coming here on Saturday on top of that. So thank you. So yeah, this is who we are. We already introduced ourselves. So basically, we were, until recently, both of us on the Fedora infrastructure team, and right now he left the boat, I'd say, but we are still working on that. I'm still hanging on. I can't escape. So I still do Fedora infrastructure stuff. Yeah, I would describe myself as a reluctant messaging enthusiast. So yeah, that's what we do. Yep. I'm also maintaining the mailing link stack on for Fedora. So Mailman 3, Hyperkitty, Posterios, that stuff. And I've been involved with the messaging system that we use since last summer, I would say something else. What are we going to talk about? Well, I don't know if you want to make the first one. Yeah, yeah. So we were, yeah, we're going to just pick slides at random to talk about, but so yeah, we're going to talk, this is an introduction to messaging. So we're going to talk about maybe why you would want to send messages. I'll give you some advice on how to pick a protocol, maybe not the right protocol the first time or the second time, but I'll tell you about all your options. I'll tell you a little bit about how to design a hopefully good message and how to fix that when you don't do that right, because you won't do that right. We didn't do it right several times. And then we'll talk a little bit about reliability, what your options are there. And then we'll spend some time talking about what Fedora did, because we've been doing this for a couple years now and we've had a lot of problems. So we're going to tell you about those problems, and then you can not make those mistakes and make interesting new mistakes. So that's the outline. Let's start with this. Yeah, so why would you want to send messages? The basic answer is you want to offload your problems. You've got a lot of machines and one machine can't do it all. So you want to do all your work somewhere else, and so you send messages around. And so it's a good way to separate your problems with network partitions sometimes. So things like making work queues. If you've got a lot of CPU intensive work, but you want to be responsive, you can, you know, queue up that work and then do it in a distributed fashion. Microservices are really hot right now, so those all have to talk to each other in various ways. Or things like remote procedure calls, those are old and well-known and useful. So the way we specifically use it is to stop other people from telling us about their problems. We do this with a publish and subscribe approach. So applications publish events that happen and then other applications can freely listen to those events and do whatever they want. This is great because we've got a lot of people working on various different applications and they don't have to work so closely together. It's a little bit of decoupling. And then we also have the community, they can listen to all these messages and do whatever it is they want to do. So the problem is that offloading your problem is a problem. It's actually pretty hard. Communication is hard. Doing it reliably is very difficult. There's a lot of uncertainty, but there is certainly latency. So you have to deal with all the things that come with using a network. And all those things must come to an end at some point. Network connections, hardware, the universe. So there's failures all over the place and you have to at least be aware of those. You can choose not to deal with them, but that is also a choice. So it's actually kind of a difficult problem. So there's a lot of messaging protocols out there. There's a huge list, AMQP, I'm not going to read them all. You could just do all your messaging by opening a TCP socket and just writing back and forth between those sockets. But it turns out that that's pretty complicated and there's a lot of things you need to account for. So people thought a lot about that and made all these protocols on top of such things. So I advocate that you use other people's work. So I think the most important thing to consider is the reliability of the messages you send. You can break it down into a couple different classes at most once. So you may get the message or you may not get the message, but you will only get the message once if you do get it. And if you do this approach, your messages will definitely get lost and you should plan for that, even if your plan is to not do anything about it. The second approach is at least once, so there's some detection in there to see maybe did the recipient get it and it will try to send it again until it acknowledges the consumer says, I did what I wanted to do and I'm done with this message. The problem there is you'll get duplicate messages and you'll have to deal with that in some way. You could do deduplication or be idempotent, but you're going to have to think about that. Ideally you could get the message exactly one time and everything is perfect and you don't have any problems, but that turned out to be pretty hard. And then the last thing you could get the message zero or more times, that's kind of both the top two together and I don't think you really want that, but you could have that if you wanted, so that kind of covers all the options. And each protocol gives you one or more of these, so if your messaging needs to be really reliable, that's going to drive your protocol choice a little bit. And I thought about listing all the various protocols and what they offer you, but it would be a lot of texts on the slide, so my recommendation would be, if you're going to do something like this, carefully read through your options, read the specs, it's not super fun, but really know what you're getting into because you're going to have to live with that choice for a while. Before we jump to the next slide, I just wanted to point to note something, if you have questions, you're free to ask them during the session, like interrupt us, that's fine, and we're going to try to answer that. Yeah, definitely. So the second thing to consider when you choose a protocol is probably the maturity of it, how long has it been around? Have people used it? If it's brand new and it's used in one place and there's one implementation of it, it could be fun to play with, but if you're thinking about putting it in production somewhere and relying on it, I would be a little hesitant to do something like that. Is it a standard? Are things going to change under you? And I guess the big thing is, do you have client support? A lot of messaging protocols involve a server, typically called a broker, and so you're going to need to be able to talk to that broker, and typically there's client libraries, and if you're dealing with more than one language, you need to make sure that every language you might be dealing with has good support for that. And you might start using new languages, so if it's well-supported on all languages, that's probably a good thing too. And then, like I said earlier, if there's only one implementation and it's a little flaky, that's going to be what you're stuck with, definitely look around and see what the reliability and what not of those servers are, whether they're proven in production, how long they've been around, just kind of normal software choice stuff, I think. I think one more thing to consider is the performance. All those various protocols have different performance characteristics. I think we all agree that more performance is good, but if you don't need that performance, a lot of times performance comes at a price. So just as an example, we'll touch on it more. Fedora opted to go with zero MQ, and one of the big features of zero MQ is that it's fast, and that's great, but we're not sending a million messages a second. We're not sending 10,000 messages a second. So the performance of the protocol is not as important to us, it turns out, as we thought. So maybe if we had spent some time estimating how many messages we would have sent, both in terms of just average messages and bursts, how big the message bodies are, like how much data are we really sending around, and how many different participants in the network we had, we might have made a different choice. So definitely think about the performance of your application before you make a choice there as well. The way, and that's a good question, there's not like a nice little map that says, I'm sending this many messages a second, pick this protocol. Different implementations of the same protocol will perform differently. You can do, I would recommend doing some benchmarks just to get started, like deploy the server, run simple tests, just kind of see, that gives you a chance to see how it works, and kind of what it's capable of. So example, we're using AMQP, and the first thing I did was set it up on a Raspberry Pi, and just see what the Raspberry Pi can do, and it turned out to be orders of magnitude more than what we send. Now, we already had the advantage of knowing how many messages we send, because we've done it, yeah, we've made a lot of mistakes, and we've recorded all those mistakes so we could see, like, how much we've done, and so we know a little bit more about our use case than I think we did when we first started. So it's not a great answer, I guess, but I would say go out, there's a lot of people who have written blog posts about their setup. So on the service websites, usually there's use cases, and they show how many messages they managed to get through with this instance and this setup, sometimes they show that, so they're going to show you the best they can do, and you can evaluate then, like, if the best they can do is a medium message per second, and the others, the other implementation, the best they can do is about a billion speed per second, then you know that one is more designed maybe more perfectly than the other. So they're definitely going to try and claim, like, the maximum throughput, so that's a good way to gauge is, like, if you set it up perfectly and did a lot of tweaking and thought a lot about your design, that could be the performance, so that's also a good way to compare things. So here are just some broker names. You can get a lot of this stuff run as a service. I looked a little bit at what the offerings are.  So RabbitMQ is a popular broker. It does many protocols. A lot of brokers do multiple protocols. So I think it does AMQP, Stomp, MQTT. So the broker you choose does give you a little flexibility as well. If you want to try a couple of different protocols and see what features you like from each one. ActiveMQ does even more than RabbitMQ. I think it does anything you could ever want. eJabberD is actually an XMPP server, but it also does MQTT. And you could use XMPP to coordinate messages, do PubSub. Actually, I know that several projects have done that in the past. So even if the protocols design more for chat, or use more for chat, it's still messaging. So I don't know that I would recommend doing that, but you could. And then there's things like Kafka, which I don't know a ton about, but I do know that it's aimed more for high performance and sacrifices, a lot of more flexibility and more expected features, I think, for message brokers. So if there's questions about that, I can't help you because I don't have time. There are talks about Kafka, and that was one yesterday. I don't know if you went to it. And I think there's one today also, maybe one Sunday. So if you want to hear about it, some people here work on it. Yeah. Cool. And with all these brokers, there's, again, reliability. So the protocol has certain reliability promises, but individual brokers, of course, have different ways to deploy them. And I think you definitely want to think about what your deployment is going to look like. Is it going to be highly available? Do you need it to be highly available, or is downtime okay every once in a while? And a lot of times the performance is tied to how it's deployed as well. So the thing, and I made the slides with a little bit of Fedora infrastructure in mind. We use their own queue at the moment, and it doesn't have a broker. But it is, it gives you a lot of tools so you can kind of build your own broker if you so choose to not use one if you want. And I think the reason, I was not around when this was first made, but the reason given was that a broker introduces a point of failure. And that's true, it does introduce a point of failure. But it's only one point of failure, which may sound like a bad thing until you have hundreds of points of failure. And then sometimes those points of failure fail. And you have to find which one before you can find out why it's failing. And this has really caused us a ton of trouble. So yeah, you're going to have a point of failure, you're going to have to think about that, but at least you only have one. And especially a lot of brokers let you mitigate the risks of that one point of failure. We're doing RabbitMQ and it has, you can deploy it in a cluster and do fancy high availability things and failover and hot upgrades and all that stuff. So definitely think about what your reliability and uptime requirements are when you choose a broker as well. Another thing to note about RabbitMQ is that even if you don't have a broker, you do have all the things, you have to solve all the problems the broker solved for you. And it turns out that's hard. The people who make the brokers do a lot of work. So that's a little bit, that's like an intro to the infrastructure you might need to send these messages. And so the next big topic that I was going to talk about was how to design a good message. I think in Fedora we have a lot of messages and very few of them are in the good camp.  So you have to pick a serialization format. There's a lot of options out there. I've listed some of them here. Again there's pros and cons to all of them. You can do JSON. It's human readable-ish I guess. There are ways to write schema and we'll talk more about schema later, but you definitely want those. I know that now. Other options are like XML and the XML schema. If you like XML, I don't know if people do. There's things like protocol buffers. Those are not really human readable most of the time. There's some caveats there and they also come with schemas. But the important thing is to pick one that meets your needs. If you need to send a lot of messages and bandwidth is an important protocol buffers might be a better choice than something that's text like JSON or XML. So when we started in Fedora and still now, we have no message schema. Schema are really nice because you know what's in the message and you can validate that message when it arrives. The upshot of this is that people change the schema all the time and then the message isn't what you think it's going to be. And if your program is not well written, it will crash. And if it's well written, it will still crash, but tell you more about why it crashed. So definitely, definitely use message schemas.  The schemas should definitely have some sort of version to them. We're tying our message schema to topics and that's kind of an AMQP. It's not necessarily AMQP specific, but depending on the protocol. Yeah, most things do. So when you send a message typically in a pub subsystem, you add a topic to it. And this is a way for people who are interested in the message to hear about it. So maybe I'm publishing messages about builds and I say build completed and that's my topic. And then other people are interested in when a build is completed, I want to do something. And so they just subscribe to those messages and that's all they'll get. So have some way to version your schema. Keep those organized. Enforce them on both sides. When you publish a message, you should check to make sure that what you published is correct. And depending on the serialization format, there's just different ways to do that. But this is really nice for developers because especially depending on how you're generating those messages, you'll catch very quickly when you mistakenly change the schema. That happens a lot. I think all of us in Fedora infrastructure know that you shouldn't change the messages, but if they're being generated from ultimately like a database schema and you write a migration for your database and forget about the message, all of a sudden it's broken and you didn't notice until it's in production. And you don't notice that that's broken until things don't happen when you expect them to happen because of the many points of failure and tracking all that down. So definitely check it when you send it, check it when you receive it, check it all the time. And let's see here. Yeah, so when you're modifying the schema and you want to migrate people from your older schema, sorry, if you want to migrate people from your older schema to your newer schema, then a possible way to do that would be to publish both at the same time during a period of time when you migrate your clients. And that's what we are deciding to do with Fedora messaging. We're publishing the topic has a version. Like I'm sending, for example, build.complete.v1. And if I want to change that schema because I want to change the organization inside it, I would publish it to build.complete.v2. And I will also publish the older one. So if your client has subscribed to the older one, nothing will change. If it's subscribed to the new one, it will get the new one. So you don't have to do an if close and when in your code to handle that. You will just get what you expect to get. Yeah, it turns out that once you deploy these messages, you will want to change them. And so you have to come up with a way to migrate, as he said. So right now we don't have a migration strategy. It's just to break or to try to deploy things at exactly the same time. But different people are working on all these different applications and the publishers and you don't even know who's listening to those messages. So things are complicated and it's difficult to do that. It's better to come up with a solid plan on how you're going to move from one message type to the next. And know that you will have to do that. Yeah, also it's nice if the schema implementation that you use is a cross language and cross platform because one of the points of messaging is to connect different applications which may be written in different languages. In third world we have a lot of Python but we also have PHP. We also have Java. We also have probably other things maybe Ruby. Yeah, it could be. And then there's everybody who's outside of the infrastructure who listen to these messages who knows what they're using but they probably want to be able to understand the messages. So JSON schema which is standard and implemented in different languages. XML has XML schemas and protocol buffers comes with schemas I think. Yeah, it'll spit out bindings for a bunch of languages but the important thing is that you're going to have to deal with that. So yeah, what you want to avoid when you're designing messaging? So basically in federal messaging we send JSON so it's objects that are nested somewhat. You want to avoid too deep nesting otherwise it's going to be complex for the people who read your messages to get to the information that they want to get. Try to avoid information redundancy too. For example if you're dumping from a REST API, you see sometimes in REST APIs you have object nested and you can get some object at the base of your object I guess and others that are linked to it because it's dumping from a database schema and it's not normalized. So there you can have the same information in multiple places and that can cause problems in the end. Also be careful about dumping your SQL schemas without really thinking about it. Some of the apps do that. For example they subscribe to a schema change or to a database change in their ORM and they send a message each time there is a change. And they send the message by basically serializing their database object and sending it to the message bus.  So you need to be more careful with that because otherwise clients will not see that you have changed your schema and client will back. Yeah that's an important thing. Consumers try to handle schemas that are really not organized exactly as they expect but you can't really rely on that. Some will crash and that's not good. Using a schema on the developer side also helps you with that. Yeah and so if on the consuming side the message doesn't match your schema you can choose to do a lot of things but typically we're throwing those messages out and sending emails to people. But yeah you have to think about what happens because you're probably going to still mess something up and something's going to get to production. Nothing ever works so I think that's the takeaway for this but yeah. Good because we're going to talk about reliability now. So sometimes bus crashes and so that's the different models we were talking about earlier that I will be starting with the at most once model. So in the at most once model you know they're not going to get duplicates of your messages but sometimes you won't get them. And so there's no knowledge acknowledgement from the producer on the consumer that might be very useful in some cases. I'm thinking of for example if you're collecting metrics about your network infrastructure like your CPU load or disk space and you're losing your collecting them regularly like every five minutes and you're losing them. It's one of the data is not really too bad. You're going to get an updated version five minutes later. So you might want to trade to do a trade off and be sure that you don't you don't you're allowed to you're allowed yourself to lose messages. Yeah that'll add a little bit more you know performance by not checking things. So if you need to send a lot of messages things like that. So there can be network failures and you will lose your message especially much like UDP. You can the receiver can crash when the message is arriving happens especially if you change your schema. The application starting sequence can be different. For example in zero MQ the client the receiver connects to the producer to get the messages. But if you're rebooting your producer then the the receiver will try to reconnect periodically but he might well reconnect after you've published another message. So that happens. Yeah. Yeah. Yeah. I'm repeating what you said. Yeah. So the comment was zero MQ has a lot of a lot of pro I'll summarize that by zero MQ has a lot of caveats and problems and you know definitely be aware of all those things before you decide to use it. Yeah. And also so the receiver can crash things can happen but the producer will also not know if something bad happened. They just send the message and if nothing happened on the receiver side they will never know it. So there's no API to retry your messages if something goes bad. There are solutions to the problem that you can build. You can have a heartbeat system to avoid network cuts or like being cut by a firewall for example. So a heartbeat system is basically sending dummy messages back and forth with with the group of machine that participate in your network. And so you can be you can detect network failures faster than this and maybe the buffer your messages in that case. You cannot see build the retry system into the producing and consuming library. So you can for example publish a message and store it somewhere which will be local or remote. Then the consumer can when they restart they can look into that store and get messages that would have been published by between the time that they rebooted that could work. But those local stores can have failures for example you can have you can run out of disk space happens. The remote stores can crash. They can also fail to receive the message because they're not an exception in the system. They might very well lose the message that was addressed to them. So it's kind of I mean it could work but it's a bit fragile and it's also very network and computing heavy because you'll be your your sending messages. So it's a push model but you're also pulling. Yeah and you know this basically is reinventing brokers. Yes. Not not with not a lot of thought. That's kind of what we did which don't do that. Yeah yeah so the comment was yeah so the comment was for the recording that if something says it's lightweight. Raise your eyebrows. It turns out that you know people throw that word around a lot and often you don't want that. Because there's a lot of features that come with that heaviness. And I think there's a slide later where I run one of these heavy brokers on a Raspberry Pi which is not exactly enterprise grade hardware. And it could certainly run all Fedora infrastructure's messaging needs. So another model which is the least once model. So the trade off here is you know you're going to get the message but you might get duplicates. Basically it's based on server and consumer and allegements. When the producer sends a message to the broker the protocol will say yep I got this. And when you're getting a message from the from the broker you have to say yep I got the old message. In this case you will know that the message has gone through. There's a feature in revealing Q well in MQP actually. I think it's MQP. It's MQP called message durability which lets you which is which in which the broker guarantees that the message has been written to disk before sending you the acknowledgement. So you know that if the broker crashes it will pick it up when it goes up again. There's also another feature of Rabbit MQ called mandatory messaging messages. So it's a bit that you flip when you send a message that says that if you activate this the broker will tell you if the message was not readable. If it couldn't deliver it to anything. For example you have a message that no one is subscribed to. If you send the message the mandatory message bit on that message the broker will tell you that I couldn't do anything with this. Otherwise it will just dump it. So that may be important for some messages but not for all. So you have a problem which is you might get duplicates. For example if there is a problem in the network before the broker sends you an acknowledgement your producer might very well think that the message was not received and try again. And that might be a temporary network failure and you're going to end up with duplicates on the consumer side. If your consumer crashes before doing something with the message it will not send the acknowledgement to the broker and then the broker will keep that message in its queue and you will get another one next time you start. So there again you will have to deal with duplicates on the client side on the consumer side. So basically you have to detect duplicates or you have to make sure that you are in the important which means that your actions you can do your actions as many times as you want it will not do something different. But the good thing is it's always on the consumer side because both problems cause the consumer to receive duplicate messages. It doesn't have to be handled at the producer side. Another model would be the exactly once model. The exactly once model means that you'll get one message. It will never have you will never lose something lose a message and you will never get duplicates either. But there you're hitting a problem that is similar to the CAP theory in databases. I don't know if you know that. So the CAP theory is that you can have you can have. You can have. Courierance. Availability and partition partition. But you can only have two of those. You can never have three. So when you have a distributed system it's very hard to have courierance and you should never lose things. Yeah. So exactly once model like at some point you have to either claim ownership of the message or you know not if you're a consumer. And once you claim ownership of the message at that point you know lightning could strike that computer and it explodes and now you you know you've lost that message. So building an exactly once model is hard and is better just in my opinion better just to deal with duplicates. Sometimes sometimes you can get what you need. Yeah if you try sometimes. Sometimes. Yeah.  And that was that was a deliberate. So on the broker side you can do with Rebitmq at least we know that you can do clustering but it's very common for brokers. Clustering means having different different servers sharing the load or having high availability between these different servers. For Rebitmq it has an equal piece of models which means that it's not a master it's not a leader follower system. All the all the brokers can be addressed at the same at the same time. This is a great way to split out your load. You know if you look it's if you read the docs you can see how best to design your messaging system to use your hardware most effectively. But it does allow to you know have different message queues on different hosts and yeah there's a lot of things you can do. So it definitely although it is a single point of failure it's a pretty resilient single point of failure. And so it's on Rebitmq it has to be on the same land if you want to do that because it exchanges messages between the database and the link has to be kind of OK. And you can do a distributed architectures also you can have brokers in different asset centers for example. And then there's different plugins in Rebitmq. There's two of them called Federation and Shovel which will let you move your messages from one broker or one cluster of brokers to another cluster of brokers. Yeah. What about performance now. So we've measured federal sense in average half half a message per second I would say. Yeah. And the peaks go to several messages per second. Yeah. Rebitmq when you test it it showed that it can have a throughput of 800 messages per second on the Raspberry Pi. And that's by with default settings. Yeah. And also enabling message durability which means that it's written to disk. SD card and I did not spend good money on that SD card. So and there are huge installs of Rebitmq for example like credit for example. Here's some nice graphs to prove our point like this. You can see the publishers and the disk right. Yeah. This is actually a three cluster installation. I didn't have three Raspberry Pi's but I did have three equally cheap. That's not an onboard but they're all like you know single board computer not high performance things. And the Q's are mirrored to all three of them. So we're getting you know 728 messages a second being published and it's you know writing all three all the messages to all three disks. And that is slightly larger than 0.66 messages per second. Yeah. So we'll talk I think briefly about the furniture because we have like five minutes. We've kind of talked about it. We'll go through that quickly. We have a lot of high level services. So build systems, issue tracking, all that stuff, package distributions. And they all talk to each other in various ways and interface with each other. And in the beginning we started Fedora FedMessage. So the current implementation which uses your MQ with something called Fedora badges that will let user earn badges when they do stuff in the Fedora infrastructure like build a package, give comments when they update and all that. So it was really was not something very critical. I mean if you if your message was lost you could very well go to a FedRentra member and say I was there at that event. I would like to get that badge. It was a failure. It's your fault. Please give me the badge. Please give me the badge. Yeah. Although this does take up valuable time like there's not a lot of Fedora infrastructure people so when and these people do notice when the messages go missing. I've seen a lot of people say I did my hundredth build and I didn't get my badge and they're busy counting but some messages got lost and then you know somebody has to investigate that. And it's you know it takes time. So reliability would have saved us a lot of a lot of time actually. Yeah. Well and the message was stored in a database also so we could we could get that. But then the needs changed changed and we had more use case. For example we wanted to do centralized notifications instead of having all our applications send email we would send the FedMessage and one application would be responsible for distributing email. Or IRC messages would be building and testing packages and relying on the bus on the FedMessage to get that. There was also application that decided to do distributing process queues or using FedMessage. So that requires a bit more reliability than badges. Basically like this was a system every app was talking to every app things were going all the ways. Yeah. So it was referred to as a mesh although and I don't wear that spaghetti picture went but yeah FedMessage. Yeah. But this ended up being you know hundreds of points of failure really just a spaghetti spaghetti monster that was very difficult to deal with still is very difficult to deal with. But yeah. So yeah we had problems with due to start up sequence apps being restarted. We talked about that before in direct you need to assign different port for every every instance of your applications that was a pain to the data format change all the time. And there was no API to handle her like you would be in your when you want to publish a FedMessage just say FedMessage.publish and that's all. And you never know what happens after that. So yeah. So for example I'll give you an example of the package update. So if you have a federal user that wants to pack to publish something to make an update to a package they will do a build in Koji. So then Koji will send a FedMessage. So this dashed arose our FedMessages. They will send a FedMessage to a CI pipeline that will test the message. Of course if that message gets lost. No testing. Nope. And then the CI pipeline will put the messages the results of the test in results DB which is a database for test results. If that message gets lost. Yeah that's a problem. So the CI pipeline decided to pull data gripper which is the store for all of FedMessages. So there was a polling here. Yeah. Of course. Yeah. Of course data gripper might as well have lost the message that that can happen or this could have got the message but not this one or the reverse. Well anything can happen. So that's bad. And then when the user creates the update in body, body will pull results DB while it might very well get the message from results DB except the body developer here knows that they might get lost. So he decided to do polling instead. And they send a message to a backend that will do stuff like curing bugzilla to get information about the bug, curing the wiki for the test cases and that can very well get lost. And if that get lost, in your update UI, you have a spinning wheel that waits for the bugzilla information to get received and that never happens. Also, when the build is created in Koji, it is signed by this this component here. So the RPM is signed. If that get lost, the build is not signed. Yeah. And this when it's signed sends a message to the backend to tell them, well my RPM is signed, you can compose the repository. And of course, body does not want to create a repository with unsigned packages. So if that get lost, it never composes. So they realized the body developer decided to pull the database here to get that information. So basically you have this sort of push-pull model that is just waits for and doesn't always work. So of course, it ends up being what you expect in that kind of situation. Well, we're going to right now. Yeah. So we had to go through this whole process that we talked so confidently about and we made some choices. So here are our choices. We went with AMQP. We're using RabbitMQ. We have a three node cluster. We use durability. Qs are mirrored across hosts. We use JSON serialization. That was, you know, we didn't really have a choice with that no matter what. I think it's a fine, it's an acceptable choice, but we wanted to be compatible with our old messaging stuff, which does JSON. And then we're adding on top of that JSON schema. So we have to track down all the people who are sending messages and beg them to write schema. So three node cluster, you can configure RabbitMQ however you want. You can mirror Qs across a couple nodes, all the nodes, two nodes, whatever you want. So we're mirroring them to all three. They're all durable. They all get written to disk. And the nice thing about this is that we have a published, subscribed virtual host. It lets you do lots of different separated virtual hosts. And then if other applications want to use this for like work Qs and things like that, maybe, I don't know how many people do Python in here, but Celery is a popular one for that. Or just, okay, yeah. So yeah, we can reuse it and just have one deployment that the admins manage. So we're out of time and we have a couple more slides, I suppose, so I think we can... Well, it's only, I think it's 9.45, so we might have more time than we think. Okay, we're out of time. Okay, yeah, sorry. So yeah, I'll go very quickly through that, but basically that's the schema we decided as our Justin Schema, we told about that. I think the slides are going to be available online, so if you want to read through the rest, that's going to be possible. And right now, the software library is published. We have bridges that bridge between FedMessage and the new system in production. And some apps are starting to migrate, so we'll get there. And I think that's almost the end. Yeah, that's what we have. If you have questions, we're going to stay in this room for a couple minutes. So if you're free to stay here and ask us questions. Thank you.


U.S. sends weapons seized from criminals to Ukraine. Miami police have delivered a package of small arms to Ukraine consisting of weapons that were either seized from criminals or bought back from the city's residents, Ukrainian law enforcement officials have announced. The handover ceremony took place in the Ukrainian city of Irpen in the Kiev region and was attended by Genadiy Fedoriuk, deputy head of the National Police and Miami police chief Manuel Morales. Guns seized from criminals on the streets could be used as instruments of crime. At the same time, these weapons transferred to our units will become another tool for maintaining order and security. Fedoriuk said, proceeding to thank Miami, which is Irpen's sister city, for the assistance. While Fedoriuk did not specify how many guns Miami donated, the Irpen city council said that a total of 102 small arms pieces and 150,000 rounds of ammunition had been handed over. He added, however, that not all the package had been seized from criminals but that some had been bought back from residents. In June 2022, then Miami City Commissioner Ken Russell announced a buyback campaign called Guns for Ukraine, which allowed city residents to turn in guns for a reward ranging from $50 to $200 for each one. The Miami police added confiscated pistols and submachine guns to the ones they bought. The city council stated, Meanwhile, Ukraine has repeatedly demanded that its western backers provide it with much heavier weapons, including advanced fighter jets and long-range missiles. While Ukraine has not yet received modern western-made aircraft, it has been supplied with a huge number of tanks, air defense systems and other military equipment. However, Kiev has still criticized the West for holding up deliveries, blaming the delays for the difficulties in the ongoing counteroffensive against Russia, which Moscow says has so far failed to gain ground and even many western media outlets have admitted has failed to live up to expectations.


A beard does not grow on just gurus, it grows on all men. Really? Believe me, it is so. But they are all doing all kinds of funny things with it. You must ask them, why are they doing it? No body pot has come without a purpose, isn't it? For everything, including the spleen, there is a purpose. So nature did not give you anything without a purpose. If you ask them, why are they removing it, they don't know. Because when the English came to India, every Indian man had a beard or at least a moustache.  If you are in a certain level of sensitivity, then you would know what is the effect and the aspect of, you know, everything in your body. You think this is fashion, but you must understand the only reason why you are cutting your hair into various shapes and forms is because there is no pain in it. So if there was no pain in your nose, in the name of fashion, you would have cut it into many shapes by now. Even though there is pain, people are poking it in ten different places today.  Yes? Yes or no? Right now, most human beings are not conscious enough, their intelligence is not conscious enough even to preserve themselves if there was no pain. It's only pain which is keeping them in one piece. Otherwise they would cut themselves into two pieces and carry one hand here and one hand there. They would do all kinds of crazy things. Only pain is saving them, not their intelligence. If your intelligence begins to function, if your sensitivity begins to function, then your concern will be about how you are within yourself and what you experience and how you can perceive more. Your concern will be not about how you look. So the advantage about the looks is for ten years, if I don't have a mirror, I still look the same. People who are removing all this, one day without a mirror, they look different, isn't it?  Somebody cut their moustache like this, somebody did this. Today you look at it, it looks funny, okay? They look like caricatures. And today's fashions also will look like that after a period of time. But a full bearded man looks the same always. Thousand years later, he still looks the same because that's the way nature intended. Nature did not intend anything without a purpose. You believe in geometry and design. So the design is like this. I don't want to change the design of the creator. I want to use it to the fullest benefit.


You've angered them This is so much better I think with your amazing boys acting commitment to our B show go okay. I'm from D&D. I wanted to play D&D What what what why what why? Why I missed it. No, I didn't miss it. What? No, she says for real S-Fan look look just for real S-Fan for real She said I agree S-Fan enjoying a more mature chat during his boomer month. Yeah, okay It's kind of scary or this way without music. He's docking. He's docking. I laughed so hard at this yesterday He has come So good it was so funny yesterday dude.    Oh my god. Where's my manners?  You got a problem. You can come and catch these Hey, let's get back to chat. What up? Thanks for watching and supporting.  Well, fine. Let's see what Aspen says Gives it vice.    So spend a warlock now. What now that report What the what that what I'm not what the why does this exist? I don't get any of this And why do I only have four toes? I don't understand. Why does it exist? Nice mosaic of S-Fan an escape video. Oh, this is real actually you know, this is actually real This is one of our used to wear red shirt blue shorts Yeah, this is one of our used to wear red shirt blue shorts, and I changed to the black shirt red shorts. That's real Let's just say the NBA the NBA is lucky.  I used to frickin ball out man Would you find this frickin picture of me though? Would you find this picture of me?   Yeah, that's been lost the game one time I lost the game one time And I'm like I'm literally lean back In my chair against the wall and I go That was today.  That was today. That was literally 25 minutes ago. Okay Like look at the build you see this look at my frickin arms You see this I'm telling you it's coming back. Okay You see this this is 2018 this is dream hack Austin.  I'm telling you it's coming back. You just need a tighter shirt. Oh, yeah Right now I'm working on getting my strength back I guess I could feel it because last workout I was like we were working out and I was like, okay I'm like adding a little bit more weight and it's getting a little like it's almost like And then you you take off that's at least that's what happened to me in the past every single time I like get back into working out it takes me a little bit to like get it rolling again and then once I get it rolling Streamer hasn't had the best couple months. So we got everyone to write her a letter Oh, look, she does her desktop like I do mine where it's like split and it doesn't make any sense. Look at that That's funny. I haven't seen anybody else who does this.  They're doing something nice and you start crying. Oh my gosh It's not that bad. I'm believable This starts out as a nice comment Hey, I don't know what you're going through but feel free to send me a dm A gorgeous girl like you shouldn't be crying There This is fine, but when it turns into this Sqt finesse just re-subbed for eight months if I see people who you know, maybe somebody's upset me So he's going through something I message them. Yo, yo, dude, uh, you know, I hope you're getting better Hope everything's okay.     Have you noticed I do this like I if I if I'm doing a voice I did this a lot on gtrp and whenever I did gtrp I I played gtrp with my cam off right so if my camera's off I I do this all the time when I'm like I I just talk like this I don't know all my computer and you guys can't even see it, but I I tell stories in my hands What is this? Is this like a Persian thing? I My whole life I just tell stories like this.  Who's this? Oh super smash Dude, I love super smash But here's the thing people have gotten so good at smash that I just I'm not really that good at it And it like I feel like I can't ever get good enough To to be able to enjoy it with people who are like really good. You know what I mean? Like I like I actually I actually feel like I'm like Friggin boxed out. You know what I mean? But I love this game growing up. Also. I never played melee because I didn't have a I didn't have a game cue I Take it back. I'm nasty. Nice It sounds like starcraft. Yeah starcraft does the same way some of these games just got so insane And it's like if you're not good enough at them, then you just kind of yeah I mean I might streams through starcraft I might do a three-day starcraft thing where where I go through the campaigns Oh, it's gonna be crazy just to see them banging with each other.  You guys didn't get mad at each other when you met in the hotel Okay I was like, okay It started out this started out. It's gonna be crazy just to see them banging with each other And it's like, okay, that's it right and it's like kind of funny. They're walking up to each other He's walking up to him at this point.  You guys didn't get mad at each other when you met in the hotel I don't know that part just like totally cements it dude. It's so good I would um like last night. I woke up a couple of times throughout the night to make it seem I do not care about this I like jay so much. I think jay is so funny. I'll fear seven just resubbed for four months How does one be kind of sex god like you?


The House of Representatives Committee on Army has pledged its commitments to ensure the Nigerian Army is placed on a pedestal to tackle the challenges of insecurity facing the country. Chairman House Committee on Army Honourable Abdulayi Mamudu, while stating this, at the inauguration of the committee on Tuesday in Abuja says, the committee is a responsibility to Nigerians. In this regard, he enjoined members to give maximum cooperation for the objective to be achieved. Honourable Mamudu says, the committee has developed a four-year work plan that will judiciously follow within specific periods in order to achieve its mandate. The budget of the FCT program gives FCT less than 20 billion in the budget. So most of these budgets are statutory budgets. So we need money to run FCT. We are planning, maybe by 2024, a statutory budget. I told Pamsek we should think of one trillion and a half. Because we have it, there are ways to raise this money. We have a serious minister that wants to work. You know, sometimes a lot of people do not understand when the FCT ministers are working. If you sit with them, talk with them, you'll agree. You know it's a serious problem. So I'm pleading with this committee, please, which supports the FCT for us, which supports the FCT for us to get more revenues next year so that the 10th National Assembly will leave legacy. Members of the committee therefore pledge their commitment in actualizing the mandate of the committee. So Chairman, I wanted to take this into heart because a widow came to me crying and I run to my husband. And it's like before we knew it, the house was down. And she slept with four children out on the street. I think we have to look at that very carefully with a very compassionate heart so that this committee, great men of Nigerian men here that I really trust you, wonderful people and kind-hearted people, you will see that this demolition is stopped or slowed down so that what needs to be done will be done. The flight of the AICN, it is one of the reform initiatives of the Honorable Minister to address the revenue generation capacity of this agency, particularly their governance structure. And that is what informed on this assumption of office to remove the headship in order to pave the way for unfit-ad review and appointment of headship that will be able to fulfill the objectives. We pay great attention to the security challenge and that is why we are implementing efforts that address this. Why the problem of one chance is to another security measures. But if you recall a few weeks now there has been a substantial decline in this. The police are implementing various measures and arrests have been made. And by now within one or two weeks no arrest is made because they have seen that they have to leave Abuja. So the incidence of having a vehicle carrying two plates number is now very rare. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


ing to purchase power from an array in another town is directly in response to the fact that these neighbors have raised concerns that gives us the flexibility to potentially reduce the size of the array at our old landfill and still get our power needs met by doing that offsite so I really think that the town manager needs to get a ton of due credit there for the fact that that is directly in response to the concerns that folks have raised so I hope that folks will accept his offer to meet and that those conversations can be very fruitful because this is really the opportunity to say okay how do we make this solar array that the town, the community has expressed such overwhelming support for how do we make this work best for the neighborhood as well and so this is a really important step to be at and those will be great conversations. Thank you. Great. Next, Safe and Healthy Neighborhoods Initiative at the chair's suggestion we want to add this to be a monthly update and more frequent as needed I guess so recapping some recent developments earlier in August under my signature we sent a letter of request out to every residential property owner in Amherst asking for their help in updating property information particularly around whether the property is owner occupied and if not, if it's rented whether the number of units and the appropriate contact people for such properties. I know as of last count that I saw the other day we were well over a thousand responses thus far in the week to ten days this letter has been out on the street and so Julie Fetterman health director John Thompson code enforcement official in the inspection services department public safety staff and others are all very appreciative of this and ongoing dialogue Ms. Fetterman building commissioner Rob Mora John Thompson also were before the planning board recently and gave them an update on various initiatives the university and the other two other colleges are in the midst of their ramping up in orientation programs for the beginning of the fall semester UMass is having the entire freshman class on campus for a couple of days later this week well before the rest of the on campus student body returns as a whole orientation program that's been revised last year and this year that has as one of its fundamental planks in it town gown expectations and positive kind of what can you do to help be a most responsible member of the community and another major initiative on the part of the university I want to offer my enthusiastic support for is the hiring of six off campus student ambassadors who will be working with their peers and with neighbors in neighborhoods primarily closest to the university on day to day neighborhood issues and helping communicate back and forth and promote that dialogue between neighbors and our many young people in town so I think that's all very positive in universities to be commended for that we move on from that I'll just note that just a tiny correction it's five student life coordinators off campus it's fine and so part of the reason of having the safe and healthy neighborhoods report be a monthly update and kind of a theme that you'll see running through the chairs report that's a document that I put on your desks late tonight and isn't on the website yet but will be tomorrow is the need for both the town and the university to be better communicating all of the steps we are taking jointly and individually to deal with the very real issues of off campus behavior I gave you a couple of things in your packet I won't talk about them now but I guess I might as well just briefly touch on them there's a door hanger as well as a multicolored brochure these are being distributed by the newly formed as of last year off campus student off campus student center off campus student center there has been a complete rearrangement in the dean of students office and the vice chancellor student affairs under her responsibilities and they are just completely taking a new look at these things so the brochure and the door hangers are being distributed through a tremendous coordination with landlords that's to make sure that students are aware and to have the message constantly reinforced about campus policies town bylaws and the consequences for violating both the list of activities that the town and the university are doing in this regard both to to educate to reinforce and to hold students accountable it's a very long list it's been a great deal of work and we're clearly not doing a good enough job getting that message out there to folks I know when I spoke with Applewood last year whenever that was I was talking to them about the initiatives between the university and the town to deal with these issues and to a person they were also happy to hear this because this is a concern everybody has but they don't realize that we're working on it so the university is trying to do a better job to let people know the town we need to be doing a better job to let people know because as long as people think that this isn't an issue that we're taking seriously and that this isn't something we're addressing then they're going to perceive the problems to be even worse that not being responsive is part of the problem but in fact responsiveness is there people taking this very seriously and so you'll be hearing more about that from Mr. Mutanti's now monthly safe and healthy neighborhoods reports and other information as necessary so that's all thank you great onto easy topics like taxi regulations just coming attractions you know that taxi licenses were renewed for both drivers and companies in the current year that set an expectation that we would spend time this year thoroughly reviewing those regulations and developing recommended revisions to them for your consideration that also have an opportunity for direct feedback from those affected the taxi operators themselves and so I want to give you a rough timeline I've been working very closely with Debra Roussell and Chief Livingstone planning staff inspection services staff has needed on this we're having our next such review this Thursday our goal is to have recommendations to you and out to the taxi companies themselves the current license holders and posted on the website all that by September 14th we then intend to have one or more meetings with taxi operators to review those draft regulations and get face-to-face feedback as well as written feedback to them our goal is to bring this to you no later than your October 15th select board meeting where you'll have a review of draft won't be asking you to take any votes at that meeting but begin the select board portion formally of the review and then ideally at your November 5th meeting to take action on updated regulations giving us the last two months of the year for notification and the office staff going through our process getting applications received and processed and time for you to approve them in a timely way for January 1st implementation thank you just to clarify one particular point we are still one very specific thing that we are still planning to do is tell me the term metering because I was just reminded of that seeing that the green caps over in Northampton had been purchased by another group and they were still talking about doing zones and I was like yeah but we're not going to be doing that so we're definitely that's very much in the draft at this point next a number of public works related updates the Safe Roots to School project in and around the Wildwood School and middle school areas is essentially complete and in time for the start of school there's a number of components to this the East Pleasant Street crosswalk at the corner of Strong Street has been upgraded and the ramp on the East Pleasant Street side of the sidewalk has been brought to the appropriate ADA compliant you know pitch the sidewalk on Strong Street from East Pleasant to the entrance of Wildwood has been refurbished the sidewalk on the Wildwood driveway has been refurbished as well there's also a new bike parking area that's been created on the front of Wildwood School to the right near the corner of the side lot there and the main driveway that we think the kids will like then on the middle school half of the project the Chestnut Street crosswalks at the intersection there which is quite a thoroughfare at you know the middle of school handicapped accessible curb cuts sidewalks appropriate safe pavement markers are all complete handicapped accessible curb cuts have been refurbished on the sidewalk directly in front of the middle school and there's a new sidewalk along the far end of the parking lot at the middle school where the ball field is that is also in place so that's all good thanks little project state funded very happy about that sewer extension schedule, harkness road and wildflower drive areas there's some follow up suggestions from our last meeting so first on harkness the construction of the sewer extension is now scheduled for calendar 2013 instead of the current year the original plan a couple of reasons for that the sewer line route itself has been changed in direct response to some neighborhood feedback about the particular route that triggered some redesign work and hence the delay on construction the neighbors have been notified in their support of the redesign and the timeline wildflower drive that construction is expected to proceed in the fall of 2013 as originally scheduled so that's an update on sewers so just follow up a little bit on that so the sequence had been as such because harkness had an easier design wildflower was going to need design seasons if I recall correctly from Mr. Morenk whereas harkness was thought to be it's a smaller area simpler that the design and construction could happen in this season so now it turns out that the design is happening and will continue I don't know if the design is done the design is in progress but it's proceeding at a good pace and it's directly related to the feedback the department received when the conceptual design was shown to those affected and so wildflowers installation is not being delayed by that because it was already going to be taking the 2012 and 2013 design seasons but with installation to start in 2013 and finish in 2013 so the WPW or the contractor whoever is going to be able to install both of these sewer systems next year actually I believe it's possible that wildflower was two halves in 2013 and 2014 no no I'm told 2013 on wildflower other questions or comments about that ok thank you for the update the construction activities update the bad news is that there's some disruption that those construction projects cause the good news is that it's happening here's an update bids are now in hand for our annual paving contract I'll be signing those this week and the state completing its work on the transportation bond bill puts us in a position now to execute those contracts so that's kudos to the legislature and governor for that we have a couple of different contracts one of which will be for a company that specializes in recycling pavement and putting it back down on the street in kind of a one sequence there's not one day is reclaiming and another day is paving it's all in one one cycle and there's certain types of roads in town that lend themselves to this technology so besides being environmentally sensitive it's also cheaper per lane mile so we're trying this out this year on Sunderland Road a very long and straight and pothole ridden road that we're going to be using this technique on because the short stretch of South Pleasant directly in front of the common so you'll see that this fall Cottage Street drainage is about to commence beginning on September 4 corner of Cottage and Triangle the perennial every time we get heavy rain you see the saw horses and barrels go up we hope that becomes a not so fond memory soon so the work the drainage work will start September 4 and the paving immediately there after this fall Cherry Lane the sewer repair work is essentially complete and the just described paving contrast contract will include repaving that initial stretch of Cherry Lane from East Pleasant to approximately the same circle and Main Street a very important ambitious project the lower Main Street portion is well underway the base coat of pavement from North Whitney to Northeast Street is complete the contractor is now moving to sidewalks and bus pull off work to be determined because we're also in the midst of doing some final evaluation on phase 2 of the Main Street work which is funded by community development block grant that's the stretch from North Whitney to Triangle so those bids are currently under review we're expecting that portion of the work to start in mid-September and we're going to get a final final decisions on our preliminary description of paving and the sidewalk work etc and I'll have further updates for you and then just a reiteration at Lincoln Avenue the sewer work will be happening this fall with application of a base coat before the snow flies and then the final top coat of paving in 2013 questions or comments about paving updates I'd like to back up a little bit to save roots to school I guess that's a paving thing I just want to recall and again be appreciative of the various people whose efforts allow that to be first the citizen group to put it together and then the work of TPW to make sure that it actually got to the state so they could be funded and then their work to make sure it got done including all of the public hearings that we went to that was a great effort and I think really has a huge improvement to our neighborhoods as a result Ms. Brewer absolutely I'd ask for that update because I was down there at Wildwood school and I was like look at all this this is great a little sensitivity issue that I'm sure is obvious but I just have to say it because school starts next week high schoolers driving out of the high school we have parents, we have kids everywhere everybody has to readjust to that and we're finally doing cottage street probably not the most ideal timing in the world so I just would hope that I'm super glad we're doing it but I would just ask us to be super sensitive to the fact that kids are walking to the convenience store and parents are driving like maniacs because they're late and newly licensed drivers are going down there for the first time if we could just make sure we're thorough with our signage and walk over here don't walk over here don't squish these people the road will be local traffic it's in the notice the road will be local traffic only during the normal work day and then open through traffic after I think 6 o'clock there's just a lot of chaos there at the beginning and end of school day on a normal day and so when you add in the fact that there's any construction going on or when you add in a flood for example so this will be awesome because you won't have a flood anymore I'm not that thoughtful about that because people are going to be confused and harried anything else on construction do you know anything on Atkins that you can tell us next stages well the base code on the roundabouts are done they're in service the contractor is focusing on the multi-purpose path is the official name of it on the Hampshire College side of excuse me 116 landscaping related work we're still awaiting word on the timing of the application of the final code of pavement I don't have an update on that I don't have an answer on that yet when that exactly will occur there's also additional signage and things like that that will be helpful the other component that isn't directly related to the state funded Atkins portion of the work but Guilford we've talked about a small stretch of 116 in the vicinity of the red barn if you drive on 116 you know that the sight lines can be our poor that road will be playing down some amount to improve the sight lines there which has been a long standing concern of the college the town will be doing that work this fall thank you I'm sorry the only thing I wanted to add about the Atkins and I'm not just really sure how we do this beyond we all responding to the grocery store comments we get about it but one it would be helpful if at some point maybe when all the signage is done and so like a press release is done saying wow go look at this now it's got the final code it's got all the signage so anybody really obvious how it's going to work I think it works but you know I'm used to the one in North Amherst now is the complaints I'm hearing most and I think I've been referenced a little bit in the newspaper too are why was it designed this way when everybody knows 18 wheelers can't fit through here well obviously that's not really a factual statement but there's a lot of confusion associated with that and why things work the way they work and whether it's driver error the fact that things get clogged up because people don't know when to yield and when not to and I think signage is going to improve a lot of that and just the traffic flow in general it just might be worth making a statement at some point that how does one say yes we knew what we were doing when we designed this and we did it this way on purpose and it will work but there are people who are convinced that we just totally got it wrong and I don't know quite how to address that beyond just saying no actually we knew about those trucks and we did account for that and this is how it works. It's a state and local design process and speed and accommodation for all size vehicle including the big trucks was taken into account and that's what those aprons are on the interior of the roundabouts it's not meant for you and I to drive our regular car over but it is meant for an 18 wheeler who otherwise would not be able to negotiate the much narrower roadway itself they can go on to that apron to help navigate the corner and that was by design that's why it's not grass maybe we just say that once it's all done again that's why you'll see trucks driving over and they're supposed to be doing that and the design is meant to encourage you to slow down as you enter the roundabout and people in the roundabout like a rotary have the right of way people entering the roundabout yield to those so that's part of the basics and it'll be it's always a little bit getting used to but it sure beats what was there forever not to believe reconstruction but Mr. Alsace's question about the back park oh yes the newly signed paving contract includes a relatively small but important job to pave the driveway and refurbished parking lot that will also have better lighting in it behind town hall there was a bit of a hiccup in that project related to the gas line that runs to town hall which will also service our about to be installed new generator we were some research needed by the gas company about whether that need to be increased in size it does not so we're ready to proceed to paving and now it's a matter of scheduling with the contractor so it's coming it'll be certainly this fall I don't have a precise date yet okay next in my role is pvta advisory board chair he is coming out to me with the pvta board today the 29th and we'll be talking and he'll be giving his views and soliciting our views on transportation infrastructure and financing needs across the commonwealth the governor the legislative leaders and the governor through secretary davie is doing outreach to the different constituencies there was a meeting of municipal leaders that I attended in springfield last week he's meeting with all the regional transit agencies because funding adequate and consistent funding for regional transit in this state is also a structural problem that needs to be addressed and so we're looking forward to that discussion with secretary davie on wednesday and I'll update you on how it goes it'll be very active legislative priority in the months ahead and we'll also directly relate to the future decisions looming for the pvta board on things like fair increases that we have a one-year fix with the help of the commonwealth but we're now pushing for a permanent fix and that's what this conversation is about so I'll be updating you as we go along I'll stop there questions or comments from mr mc all right then member reports so you can talk as long as you want but just bear in mind that we have an executive session coming up and we have a light agenda for september 10th so I'm just saying all right liaison reports anyone very fast conor kasaki sister committee had a very nice event today at four o'clock in which I think her last name is young who was a fellowship winner from 2011 a graduate of emerson college went to japan to study how seniors are treated in housing and it was very interesting for example a group home has only nine seniors in it because they believe individual attention is very important for the consistency between the seniors and the staff and these are seniors with Alzheimer's so it was a very interesting talk very well illustrated by slides and very well attended thank you anyone else mr aiden just very two brief reports the tmcc has landed some new audio equipment for meeting rooms I guess they don't make meetings that are not televised more easily heard by members of the audience it's actually a very nice list of equipment I have to say also I met with the recycling and refuse mc materials committee management committee and they're getting they're really beginning to get some traction with dealing with what's going to happen when all the local landfills are closed which turns out to be closer than we had thought the recent lawsuits against the landfill in south hadley and north hampton suggest that they will not be available to us for the next five years as we had hoped but may not be available to us after next year sort of depends on how things are going so they're really anxious to begin to figure out how first to let all of us know that this is coming and managing our waste will be more expensive and then to help us figure out how to reduce the amount of waste that we have to throw out get more of it recycled and well less of it into our homes in the first place and businesses and municipal offices so watch this space can you tell us how the survey results were I don't know if that's still going on or if that ended it was presented but no I don't remember well enough there was a fairly good response I do remember that and there's some discussion about how to interpret everything but the long and short of it is that it's going to be a lot more expensive and we will have to deal with it somehow thank you Mr. Wald that was Wald and Hayden together we're often confused I'm very confused right now just briefly public art calendar, alert, biennial end of the first week in October should have great weather and great art and the historical commission just want to mention that some residents of North Amherst came before the commission to indicate their desire to look into the possibility of creating a local historic district on the model of the one that was approved for the Dickinson district in town meeting I've been talking to various people in the precinct so there are some people who are very much for it and some who are very much against it we've received some mail about that just so you know I'm trying to see what's going on, gather information whatever we can do to smooth things out the National Trust for Historic Preservation picked up the story with the basically contentless and not very helpful piece nothing they couldn't have gotten out of Scott Smirksbox, much better articles which I recommend to people instead I'm sure it'll be in the news again as the weeks come what I should say though is that as far as I can tell from town hall, Plenity Department wants to get the Dickinson district nailed down first so they're not rushing to start something new before they finish the old so it's not an urgent matter, it's just something that's coming up through the pipeline Thank you very much Anyone else, Ms. Burr briefly because what few meetings there have been in many respects I haven't gone to because I've decided to take up my time apparently with the Regional School District Planning Board work which is preceding a pace and anybody wants to ask me about it, we'll talk about that another time more specifically CDBG hearings, there was just one on reprogramming capital money, we've seen this happen before where we have these great ideas of things we're going to buy and unfortunately we people don't always want to sell them to us so then we have to reprogram the money so we don't lose them so they just had a hearing on that they are all geared up for their set of hearings associated with both social service and non-social service, i.e. capital projects so that's preceding a pace, they've issued a release saying we are soliciting proposals etc so that is all going along very smoothly and I also wanted to mention that the housing consultant that was solicited through will I'll tell my manager to speak to this better than I can clearly at this hour I'm not speaking to anything clearly but the housing and sheltering committee which as you know is a fairly new committee is going to be meeting with that consultant soon they're going to be working out of it because we decided that that made, that was the place that made sense for the public to feed into the consultant because the consultant isn't trying to make some great vision for Amherst they're mostly collecting facts but to make sure that they're collecting all the facts they're going to have them speak with a group associated with housing and so the housing and sheltering committee is doing that and any neighborhoods that have piped up and asked for concerns associated with that are being directed to work through the housing and sheltering committee and that seems to be going along just swimmingly so they've met several times this summer despite being new and are coming right along the other thing I wanted to mention associated with historical stuff is that as we have seen as select board members but the public is still in the process of soliciting applications for the Dickinson historic district commission with the various caveats knowing that various representation is expected on that but we haven't been getting like gobs of applications so if there were people out there that were interested in that they should go to the town website and that information is right there so that they can apply because they can't start doing anything until there's commission appointed and not too many people have applied for it yet but it is summer. And we also liaison Mr. Winslow. Reynolds Winslow again precinct one it's an inquiry I have to request if the select board has made a judgment on two students for the human rights commission that their credentials have been submitted but I have not been informed that they have both been approved. We approve both of those at the early part of the meeting. That happened very early. I promise them that it would happen today. Thank you very much. I'm terribly sorry you had to sit here all night waiting for that. I would have been happy to indicate that. Things and did them very fast and I'm sorry you missed it. Yeah for untimed items just so folks know we use untimed items to fill in all the gaps between our time items as necessary so untimed items don't come at the end of the meeting. They come absolutely every place we can plug them in so that we can keep to the timed items as best we can. My great apologies too. I'll just say so if they wanted to hear us mispronounce their names that would be fairly early in the meeting. Which I did as well. It's done. Okay so other liaison reports I'll just note campus and community coalitions I've already referred to and I'm going to imagine getting ready for the new school year and as part of what I was talking about earlier with safe and healthy neighborhoods trying to get the message out better about exactly what that work is I hope to present you kind of a more formal review of that at the next meeting and I think that's the only thing I have to report on. Open meeting will update. Can we wait till next time for that? And really all I can say is yes we can certainly wait on it for next meeting. Yeah it's nothing. So it's still a discussion we'll have at a future time about whether or not we're going to do remote participation but unlike occasions when they have just totally changed the way they're looking at something this is just more of the same. Did we mention this chairs report and how much we are all glad we didn't have to do this. Thank you. So that was what I was getting to was on your behalf. So there's just the regular committee stuff and various meetings that happen but some things you wouldn't know what I was doing unless I told you and because we haven't met in so long I thought it was easiest to just give you a list. As I said I'm not going to go through these things. There's a heavy theme here dealing with the university that really is kind of the thing that I spend the most time on. And I couldn't have better partners to do that. So I wanted to make sure that you all had this information to have kind of a picture of what I'm doing on your behalf. If you have any concerns you should really let me know. So I think that's it for the chairs report. You can just note that for whatever to be that is interesting. Do we have any other untimed items that we didn't get to tonight? I'm aware of. Our motions. Is that right? So the minutes that are in our packet weren't for approval those were just parts of other issues. We've approved them already. That's just boilerplate. It's always there in case we need it. So I think that we have done everything in which case it's time for the executive session motion which I will make and I will note that one element was left out of the motion. So I move to enter into executive session in accordance with Massachusetts general law chapter 30a section 21 part 2. Part 2 is missing from the motion but it is on the agenda. Which is to conduct contract negotiations with non-union personnel being time manager John P. And the select board will not reconvene an open meeting following the close of executive session. We have a full call vote to go into it. Second. And this meeting adjourns to executive session at 9.51 p.m. I repeat we are not coming back in open session and the select board will meet again here in this room on Monday September 10th. Thank you all very much and happy Labor Day and back to school.


Thank you for your finished questions. I welcome you all to the third meeting in 2017 of the Delegated Powers and Lower Reform Committee. Stuart McMillan has unable to attend the meeting this morning, and has submitted his apologies. We're pleased to have George Adam attending the meeting this morning as a substitute member. Indeed, welcome to all my committee colleagues and thank you for We are moving now to agenda item one which is a decision on taking business in private. It is proposed that the committee take item five in private. Item five is the consideration of the committee's second quarterly report of the parliamentary year of 2016 and 17. Does the committee agree to take item five in private? Agates. Thank you very much. nôr neul i'r rôl oeddon niol, nid 이f niol, oedd niol yn ganlwyd i'r lleidio negatif a ddau niol yn gwybodaeth ar gyfer tynnu oherwydd rhagledigol yng Nghymru Cyf variadau Ffeeith Scotland Cymru Cymreigol, 2017 SLI 2017 n. 6, oeddech chi'n rôl oedd yn I, 2017 SLI 2017 n. 7 oedd yn Ymdraith deng dangos, oeddech chi rôl oedd yn dd weirdos, Order 2017, SSI 2017, number 7, or on non-domestic rates, Scotland Order 2017, SSI 2017, number 8, or on non-domestic rates, levying Scotland regulations 2017, SSI 2017, number 9. So, is the committee content with these instruments? Content. Thank you very much. Agenda item 3 is instruments not subject to any parliamentary procedure, and no points have been raised by our legal advisers on the act of sedentary rules of the Court of Session 1994. Amendment leave to appeal 2017, SSI 2017, number 4, is the committee content with this instrument as well? Content. Thank you so much. Agenda item 4 is the Scottish Social Housing Charter. Section 33 of the Housing Scotland Act 2010 provides that the Scottish Social Housing Charter does not have effect unless approved by a resolution of the Parliament. The committee is therefore considering the charter in accordance with rule 10.10 of the standing orders in the same way as it would consider an instrument that is subject to affirmative procedure. However, no points have been raised by our legal advisers on the charter, SSI 2017, number 2. So, is the committee content with this charter as well? Content. Thank you. I now move the meeting into private.


I am Dr. Ravichan Siddhachari. I am a consultant hepatobiliary surgeon and chief liver transplant surgeon at Manipal Hospital's Old Airport Road, Bangalore. TAS stands for Transarterial Chemoembolization. That means a catheter is inserted into your groin. That is to the femoral artery and the catheter is forwarded to the hepatic artery and straight to the tumor. And chemotherapy, the medical particles are injected through this catheter and so the chemotherapy is directly acts on the cancer. And following the chemo injection, small beads and gels are inserted to block the artery so that the medicine stays in the liver tumor bed. So the TAS is basically used for downsizing the tumor and also for those patients who cannot enable to withstand a surgical treatment. For them, TAS is used. TAS is also used as a bridge to transplant in the sense to downsize and then later consider for liver transplantation.