AV gentlemen, are you ready to start? Happy with your life choices? Cool. Hi, so I'm Michael. I'm here to talk about deploying Nova. I've set myself an interesting challenge with this talk. What I did at first was I emailed approximately 20 senior OpenStack devs and said, if you could talk to deployers before they deployed Nova, what would you say? I got back a lot of staff, some of it mutually conflicting and turning that into something coherent took a fair bit of work. So I actually ended up writing this talk as an essay first. So I've ended up with a 3200-word essay that I'm going to present to you in 23 minutes. So when you do the math, so I have to talk at like over 100 words a minute, so it's going to be awesome. But I'll give you a link to the essay at the end because I had written this thing, I might as well put it online. So the premise of the talk is what would a Nova developer say to a deployer before they deployed? What mistakes do we commonly see? What do we wish people had considered before? It was too late, that sort of thing. So first off, in 10 seconds or less, what is Nova? Nova is the component of OpenStack that manages virtual machines and hypervisors and that sort of thing, compute resources. So it's intended to take pools of machines, preferably hundreds of machines, I imagine, and you come up and make an API request for a virtual machine, we pick a machine for you and do the thing. It's obviously more complicated than that, but like I said, I have to talk real quick. Okay, so let's get into the meat of the matter. There are a few things about people's operational environments that I wish I could say to them before they deployed. First off, consider what base operating system you're going to use. I know that long-term supported releases are very attractive, but depending on your vendor, we sometimes experience bugs in the software that we depend on, and sometimes it can take a very long time to get bug fixes backported to long-term supported releases. So you could think of Nova as really just a way of orchestrating tools you already had on your machines, to a large extent. And so, you know, if your OpenV switch doesn't work properly, we're going to have a bad day. A good example recently is we found a bug in QMU which corrupted the disk images for virtual machines, which is kind of a big deal, and it was a lot of work to get that fix backported to all the various distros. Tony Breeds did a really good job there, and some distros are better than others at working with us. But, you know, when you're picking your base OS, don't necessarily pick what you always use, or, you know, maybe there's a version of your base OS or your chosen OS that is targeted at OpenStack, and maybe it's worth if you're building a big OpenStack environment using a different distro from just your default for absolutely everything. The version of Python users use matters as well. We only test with Python 2.7 at this point, I believe. So if you were running on a distro with 2.6, for example, that would worry me. We also don't have complete support for Python 3 yet, so don't just assume that because Python 3 is cool that we support it. We publicly document the versions of things we use for our continuous integration, and so if I was going to go and pick a release of a distro, I would ask questions about what OpenStack was testing on and then compare that with what I was thinking about running on. Don't reinvent the configuration management wheel. There are community-supported puppet, Ansible, Chef, Juju, whatever recipes. If you already have, if you've already picked a winner in that space, I don't know, you're a puppet shop, then I think you'd have to have a pretty good reason to go and reinvent the puppet modules, right? There are ones that people have already written. They've put a lot of effort into them. If they're not perfect, they'll probably take bug reports, so I'd seriously consider not starting from scratch there. Log management is kind of a big deal, too. So the harsh reality at the moment with NOVA is you're probably going to end up running with debug logging turned on when you experience a problem. Our debug logs are crazily verbose, so we're talking about very large logs, and we're also talking about a system intended to run on hundreds of machines. And so a single request might hit many machines, and it's sometimes hard to determine what machine the problem actually occurred on. So I'd be thinking centralized logging. It doesn't have to be syslog. You could be using something like LogStash and Elasticsearch and stuff like that, but you do need to have a reasonable answer to how logging is going to work in a non-trivial environment. Monitoring is really important, but especially monitoring of memory on your controller nodes. So the Python services that we use to, sorry, that form NOVA can consume a fair bit of virtual memory, so you especially need to make sure that you're monitoring memory usage on your controller nodes. But in general, if a hypervisor goes offline, like a hypervisor node, you'll only lose the instances on that hypervisor node, and it would be quite possible without good monitoring to not notice that that had happened. The things about scale that my 20 survey respondees said to me. Think about your final scale now. I know that John Dickinson in the Swift talk kind of said exactly the opposite, but specifically if you're building like a proof of concept and it's going to be tens of machines, but you think it's very likely that you're going to scale to hundreds or thousands of machines because I don't know, you're a bank or you're CERN or something, then you probably want to deploy cells now, even though you don't really need it. And that's just because it's going to be easier to move to your final cells world later. We're actually re-architecting NOVA at the moment because we want everyone to deploy cells, even if you have a five-machine install. And we're going to make that relatively inexpensive. But if you think you're going to build a non-trivial environment, you should probably be thinking about cells early and often. SQL databases. This one seems a bit religious and I don't have a lot of database religion, but I'll try to pretend. Carefully consider what SQL database backend you use. So specifically I keep meeting people like we're a Postgres shop, we're going to use Postgres. And more power to you, but the rehearse reality is the vast majority of OpenStack Deployers use MySQL. So you're probably going to experience bugs that haven't been reported before and it's likely our CI doesn't pick up things that you'll experience. So again, you know, there's a value to existing operational expertise. Like if you are a Postgres shop and you really understand that, then that's cool. But you know, ask questions about what other people are using and what experiences they've had. There's some other things here. You know, we support read-only replicas. The database performance really, really matters. There are many user operations that block on database transactions. So if your SQL backend isn't performing reasonably, then you're going to have a bad day.  And specifically at this point in time, do not run Galera. Now, this is a bit scary because it turns out that lots and lots and lots of people are running Galera at the moment and we want to support Galera, but select for update doesn't work properly on Galera. The right intent locks aren't propagated. And so we do see bug reports where it's simply that the locking isn't being passed around by Galera and it's all gone horribly wrong. In the essay form of this talk, I've included a link to a blog post from J-Pypes that explains exactly what this problem is. And it was only recently identified, so there are people working on it at the moment. And this is, I've mentioned this before. So SQL performance really, really matters. So, you know, presumably you'd be monitoring your SQL layer and making sure that it's responding reasonably. There are also options for different message queuing. So the way the Nova components talk to each other is via a message queuing system. This queuing system is not really exposed to, well, it's not exposed to end users at all. It is exposed to some other open-sack services. And there are choices. So, you know, RabbitMQ is supported, ZeroMQ is supported, and Cupid is the other one. Again, the vast majority of deployments seem to use RabbitMQ. So, you know, if you want to use something different for a good reason, that's cool. But maybe go and ask the operators mailing list if other people have experiences with that before you do it. Fundamentally, Nova is about hypervisors, right? What we're trying to do is provide an API on top of a set of hypervisor nodes and hand out virtual machines. So, when you get to picking a hypervisor driver, you need to pick one that is reliable and meets your needs. So specifically, if you have a lot of operational expertise with a particular hypervisor, that might be cool. But you also need to check that that driver for Nova behaves reasonably. So, for example, we have examples of drivers that are less well-tested than other drivers. We have examples of driver authors that are less well-integrated into the Nova team than others. And so, you know, just because you're... I'm specifically trying not to say bad things about specific hypervisors because they're all my friend.  But, you know, check into the state of the Zen driver in Nova before you decide that that's the thing you want to do. It turns out the Zen driver is fine. But, you know, there are other less mature hypervisors. I'd be especially concerned about hypervisor drivers that aren't in the Nova code base. The most obvious example is the Docker driver that's on Stackforge. But that's not totally terrible, right? At least we know about Docker. You know, we're working with those guys. There's some mutual CI happening. It's not the end of the world. It's on a path where we intend it to be in Nova. Even worse is I'd be exceptionally worried about running a hypervisor driver that the Nova team had never seen. So there are companies that will sell you proprietary hypervisor drivers that aren't open source, or if they are open source, they've never been shown to the... Like, they're not working with the Nova team. And that stuff is scary because the hypervisor driver's plug-in at a layer with no versioning in the code base. So, you know, over time, we'll say, hey, we need to do this thing to implement this feature and we'll change that driver layer. And for all the drivers we know about, we can verify we haven't broken them. But for the drivers that are out there that don't talk to us, we don't even know they're broken. We don't even know necessarily that they exist or anyone uses them. And that's scary. So this is a little bit of a nuanced topic.  But it's subtle, right? You need to basically talk to people.  So yeah, not all hypervisor drivers are created equal. Another thing I'd say to people is that hypervisor state is a useful debugging tool. I think it's often overlooked. So to pick on libvert for a second, if you're experiencing a problem with an instance, don't just look at what Nova's doing. Have a look at what libvert is doing as well. So I don't know if people know libvert, but you know, there's an XML config file that describes the instance that you then hand to libvert when you boot it. Those exist on disk, we just create them, right? And there's files in whatever directory you've configured for the instance that have interesting state. Like for instance, there's the console log for the instance, which might be useful. So, you know, don't pretend that Nova operates in isolation. You know, there's similar tools for Xan or Hyper-V or VMware or whatever you're using, but you know, if you're experiencing a problem, you might find that the hypervisor provides you with meaningful information as well. Networking, this one's a little bit easy because I can punt on the whole what neutron driver should you pick issue. All I really want to say is don't deploy Nova network. So, there are vendors out there who'll still happily sell you a Nova network open stack install. Nova network has been deprecated for a very long time. Nova network will be removed. Nova network will probably not be removed in Kilo, which is the current release at this point. Because basically there's some features missing in neutron that we need to have, to be able to spot absolutely everybody who uses Nova network. And we're still finishing like the, you know, we've got 90%, we need the final 10% kind of thing.  So start with neutron. Because if you pick Nova network, all you're doing is signing up to do an upgrade at some point of time that's going to be reasonably close to now and where you don't control the timeline. So just don't sign up for the extra pain if you're new to open stack. Testing and upgrades. Now I guess I'm assuming a non-trivial environment here. If you're building a five-nove proof of concept, then these things don't necessarily apply as much. But if you've got a reasonable size deploy, you absolutely need a test lab. I keep meeting people who, you know, the first time they run an upgrade is in their production environment and that stuff freaks me out. Like at one point I had to apologize to people because their instances were corrupted when they did that. And that was bad. But part of the problem was we had assumed that people would report bugs before they actually did it in production. So you need a test lab. If your boss is not sympathetic to a test lab, I guess you have a conversation about, you know, how expensive is it if this whole thing goes away because we didn't test it. You also need to test the database migrations on a copy of your production data before you do them for real. So we've got this SQL database, right? A NOVA upgrade may include multiple database schema upgrades as well. We do them in steps. And some of those can take, for example, an extremely long time to execute. And so some of our bigger environments have donated datasets and we actually do CI testing on the upgrades. But those datasets tend to come from public clouds, for example, where volumes aren't as common as they might be in your environment. So we don't guarantee that we mimic every possible deployment. And so I would suggest that, you know, just running the upgrades on your dataset before you do them for real would be a valuable thing to do. And you don't need a full NOVA install to do that. You don't need all the hypervisor nodes or anything like that. You just need something to run NOVA manage on and a machine hosting the database that approximates your real one. And so, yeah, because in the current world that we live in, the world stops when we do these migrations. And so if one of these migrations takes four hours, that might be a big deal in your environment. I'd also be worried about rollback of these migrations. This is a hard problem, right? You basically have two choices with the SQL database upgrades. You can either take a database snapshot and restore from backup when it goes wrong, or you could roll back. Neither of them's great. Like, if you take a database snapshot and the state of your cluster has changed, users have created and deleted instances, what happens to those instances when you restore a backup? But then again, rollbacks aren't great either because some of our migrations throw away data in a way we can't regenerate it. So at one point we were just storing enough data in the database to rehydrate things, but then people say, why is my database much bigger than it really needs to be? So in general, we have these people who do this thing called continuous deployment, which is where they're deploying trunk from Git before it's released. And the way they generally deal with a problem when we accidentally break the world is they roll forwards. If you're using your distro packages or something like that and you're upgrading every six months, this is probably less of an issue because it will have been tested by your distro and you'll have tested it in the lab. But think about how you're gonna handle database migrations. I think about your upgrade strategy in general as well, I guess I kind of alluded to this a second ago. Are you going to continuously deploy? Are you going to update every six months when we do a release? Are you going to wait until, I don't know, you're on an LTS release and five years later are you gonna upgrade to something new because five years is extreme, I think. But if you waited, say, two years, you have to step through four open stack releases. We only support the two most recent. So if you experience a problem in the first two of those, we actually, we don't even have the branch in Git anymore. We've got a tag, but we're not gonna help you. The code is too old. So maybe your distro will, but I'd be really scared of upgrade plans that involved waiting a long time between upgrades. But I also probably wouldn't want to be the first environment to do the six-monthly upgrade either. I'd be waiting for someone like, or one of the vendors like Bluebox, CERN, someone like that to have had to go first. But yeah, just needs some thought, I guess is what I'm saying. Another reality of the world at the moment is most people deploy Libvert as their hypervisor driver. So there's a few specific things I wanna say about Libvert. Libvert is an abstraction library on top of a bunch of different hypervisors. So you can use Nova with Libvert, but using Zen or KVM or whatever. And not all of those hypervisors under Libvert are created equal either. Most people use KVM, which means the Zen code is less tested. So if I was going to deploy Libvert, I would pick KVM. There are other choices with Libvert like LXC for example, but again, not as well tested. Specifically with the Libvert, you need to think about your instance storage options as well. So ignoring like more generally than just Libvert, in Nova there are two different kinds of storage your instance can have. There's instance storage, which exists for the lifetime of the instance and is normally stored on the hypervisor node, but that's not always true. And there's block storage, which is a thing provided by Cinder. And Cinder block storage is called volumes and they last past the lifetime of an instance. So specifically picking on instance storage, the Libvert driver has a plugable mechanism for those. Again, everywhere there's a plugability layer, some things are better tested than other things. So for example, lots of people want to have shared instance storage that they lose the disks on a hypervisor node, they don't lose the instance data. Many people choose to use Ceph for that. Ceph is cool, shared instance storage is cool. Again, it comes with a cost, right? So if you chose to do shared instance storage with expensive NFS appliances, the cost is money, the cost with Ceph is that it's not as well tested as just files on disk. And we have seen some bugs in that recently. We have some people from Red Hat and Inovance working on improving the continuous testing around that. So that should improve sometime really soon too. That's pretty much what I said before. So just be aware of how well tested your instance storage is. So I mentioned this before too, I'm being told I have two minutes. That's why I'm flustered. So the essay blog post form of this talk talks about this a bit more, it gives you some advice on how to evaluate whether or not there's continuous integration testing for your chosen driver, whether or not it's actually currently running. Whether or not there's actually someone paying attention to it when it fails and fixing things.  And I keep talking about this essay form of the talk. I actually posted this this morning, so this is up there now. I'm also sure it's not perfect and not correct because there's only so much time one can spend on something like this and it was already very long. So at some point you have to draw a line in the sand and say, you know, hey, this is complex enough. But I'm also very open to questions. So have a look at it, hopefully it's helpful. If you have questions or think that I'm a raving idiot, feel free to email me or talk to me on Twitter or IRC and hopefully it's useful to people. Do we have any questions? Yes, are we running a microphone? I could run a microphone. I'm self-running. You talked a lot about making sure you choose well tested implementations as an end user, how do you know? Is there something published by OpenStack Foundation that explains the level of testing? Is there some continuous integration system we can look at, that sort of thing? So yes, it's not perfect, nothing in life, as I suppose. That's kind of what I was talking about at the end. So yeah, there's a tool that Joe Gordon wrote that you can check out from Git and run and it will show you whether or not a given CEI bot is commenting recently. Our code review system and CEI system is all publicly available, so you can go and have a look at what's happening. But I think fundamentally talking to other operators is really important. So there's an OpenStack operators mailing list, there's an IRC channel, they have meetups, there's lots of user groups around the world. I'd be asking them, hey, what are your experiences with this or this is my proposed deployment, how painful is my life going to be? And listening to other people's experiences as well. But yes, there is advice online about how to determine if something has reasonable CEI. Yes, and there are active user groups. So specifically here, I think there's one in Auckland and one in Wellington, I've definitely been to an Auckland one. And they're mentioned on, they generally seem to organize themselves on meetup.com. But if you do a web search for that sort of thing, I think you'd find reasonable pointers. Anything else or should we go to the next guy who's more interesting? Going, going, gone, thank you.


What's up everybody? Jason here for jazby's casebricks.com. Again, this is another NSCC promo break We technically actually broke the majority of the stuff at the national on Saturday with Joe, which is jazby's eight box quick hit National basketball mixer Pikachu number three. You should have seen that video already on Saturday The only thing is that we were missing couldn't find potentially One box of mosaic team all so I'm actually just doing that loose box here because Joe already did the rest of the Boxes on Saturday, so I think he already also put you in the list all that good stuff This is just me recording this video to open up the last box of mosaic So that stuff that broke on Saturday still not here yet It should be getting here later this week got to get sorted shipped out together with excuse me with this So I'm just quickly running the last box that we didn't do Which here we go mosaic team all right here we go guys Got a gold coming up Bama the bio gold Nice James Weisman little print line right there though, but still a nice one That would be going to Sean Healy Tarbron Junior to bar Parker nice Stefan Curry quickly nice Kobe white And a gold pulp Pierce Nice paying Pritchard will be top-end drew holiday And a nice Tyrese Maxi So some nice rookies and some nice color So again guys Joe did the majority this break already on Saturday, so you should have seen that video This is just the second video part two for just the one loose box and mosaic that we did here back in Hermosa Beach Appreciate it guys. Jasper's case preach calm. There you go. So nice stuff right there


7 things that narcissists will do to regain their control over you. Narcissists want power and control. They want the ability to direct and influence your behavior in the course of events. They want to maintain influence and authority over you. They want to determine your behavior. When you push back against a narcissist, they can feel that their power is slipping away. Narcissists actually have no power of their own. Their game is to trick you into giving your power to them by acts of manipulation or gaslighting. When you hand your power over to them, they then have the ability to control you. When you push back against a narcissist, you are then realizing your own power. You are then taking your power away and that is something narcissists do not like. They don't like it when you realize your power and abilities.  They want to be in control of that so that they can continue that agenda so that the situation can work out in their favor. So although it is good to take back your power from the narcissist, there are also some possible consequences that you need to be aware of. There are some things that the narcissist will do in an attempt to regain their control over you. One, they will try to love-bomb you.  They will return to the love-bombing. They will try to make you think that they're still the same person. As though nothing has happened since then. As though nothing has changed. They might give you compliments or buy you gifts. They might take you out somewhere. It's as though they've finally remembered or understood what you like to do. It's as though they've suddenly just become this kind-caring person. But this is actually just an act. They don't really care about you. They're manipulating you. They're trying to regain their control over you.  It's designed to entice you. It's designed to lure you back in. They will try to attract or tempt you by offering pleasure or advantage.  They will persuade you to do something by offering a reward. But it's not because they care about you. It's not because they have your best interest in mind. It's a trick. And it's just designed to get them what they want. 2. They will enforce flying monkeys. Flying monkeys are people that the narcissist uses to do their bidding. They will often be used for an abusive purpose. But they can also be used to lure you back into the relationship. The narcissist will use their flying monkeys to carry information to you. As though they are trying to get you to see the light. They will try to get you to think that it's in your best interest to return to them. As though they just want to resolve the situation. When really, they've been tricked into feeling sorry for the narcissist. The narcissist may have led them to believe that you have abandoned or neglected them. In some situations, the flying monkeys may be pressured by the narcissist to act in this way. The narcissist may be intimidating them. But either way, this is just designed to lure you back into the cycle of abuse. The narcissist has no intention to change. They don't even think they've done anything wrong.  The flying monkeys may come to you, telling you that the narcissist is sorry or they promise to change.  They will make you feel like they're the ones who have given you another chance. Free.  The narcissist always has to be right. And they will force you to see it this way. They will manipulate and lie to get their way and convince you that you're wrong. They will try to make you believe that you've got the wrong idea. They will try to make you believe that you're misinterpreting their actions or words. As though they never intended to cause harm or distress to you. They will try to make you believe that it was just a misunderstanding. Even though they are fully aware of what they did. They will say or do almost anything to pull you back in and they can make it very believable. But you need to trust your intuition. There is a reason why you pushed back or went no contact with the narcissist. They said or did something that you didn't approve of. And unless a person holds themselves accountable for their actions, nothing is going to change. But in some situations, they will just come out and admit what they did wrong. They will tell you whatever they think you want to hear. They will act like they are so understanding and that they will never make that mistake again. But this is still a part of the manipulation. They have no intention to change. They're not sorry for what they did. They're just sorry that they got caught out. They're not admitting their wrongdoing because they want to be a better person. Or because they have your best interest in mind. It's still all about them.  They will try to make you believe that your family or friends aren't really on your side. They will try to turn you against them. If that doesn't work, they will try to turn them against you. They will start a smear campaign. They will tell them private information that you can find in them. They will try to portray you as this horrible person who has bad intentions. And then they will return to you, pretending as though they were not a part of it. Pretending as though they don't know anything about it or they don't understand it. This is designed to make them your only source of influence and information. It strengthens the trauma bond and may make it even more difficult for you to escape. 5. They will monitor you. They will wire your home or car with cameras or recording devices.  They will even let you know that they are watching. This is designed to humiliate you. It's designed to injure your dignity and pride. It also makes it very difficult for you to tell anyone because most people wouldn't believe someone would be capable of such sick and twisted behaviour. But this is designed to keep you under their control. It's designed to make them feel like they have power over you. 6. They will deny your freedom. They will control your freedom of movement and independence. They will restrict your ability to make your own choices and decisions. They will stalk and harass you. They will monitor everything you do. This is designed to intimidate you and force you to do something that you may be unwilling to do. 7. Coercive behaviour. They will engage in a pattern of acts of assault, threats, humiliation and intimidation. They will try to harm, punish or frighten you. They may even involve law enforcement. They may threaten to sue you. They may blackmail you. They may demand payment or other benefit from you. In return for not revealing compromising or damaging information about you. They do this to regain control over you. They do this to make you do what they want. I hope that these 7 signs have been helpful to you. I hope that they have helped you to understand the ways in which the narcissist will try to regain their control over you.


Police arrested counter protesters at a large pro-Palestinian march in London on November 11, as they launched a major operation to avert clashes between the two groups, the pro-Palestinian march, which is expected to attract hundreds of thousands of people, has also drawn counter protesters from right-wing groups to the capital on what is Britain's Day of Remembrance for war veteran Stutt London's Metropolitan Police said in a post on X, formerly Twitter, they had faced aggression from counter protesters who were in the city in significant numbers, adding that they would not allow them to confront the pro-Palestinian rally some counter protesters scuffled and shouted at police officers as the pro-Palestinian rally took place. The march is the latest in a series of rallies in the British capital to show support for the Palestinians and call for a ceasefire from Israel's bombardment of the Gaza Strip.


I'm Deborah Borchardt and this is your Marijuana Money Minute. It has been a busy week for acquisitions and earnings as the industry continues to consolidate. On Thursday, SAW Global said it was acquiring Northern Emeralds for $120 million. SAW Global plans on expanding on the Northern Emeralds one plant dispensaries in California, Florida and Michigan. Supreme Cannabis is buying Blisco in a deal valued at $48 million. Supreme also reported third quarter 2019 net revenue of $10 million. Slaying worldwide is acquiring LBA Global Corporation and its Lunchbox Alchemy brand portfolio plus the subsidiary Hydro Distribution, the proposed transactional bolster slaying's position in the Pacific Northwest. And truly this buying the Connecticut dispensary, the healing corner, but they didn't disclose the size of the deal. Now, there were a ton of earnings this week. We can't go over them all in this video. If you need details, head to GreenMarkerReport.com for that. Aurora Cannabis reported their third quarter net revenue of $65 million. That is up from $54 million sequentially, but the company delivered a whopping loss of $158 million. Tilray reported that its net loss for the quarter was $30.3 million. Now, even though the revenue increased by 195% to $23 million versus last year's $7.8 million, so that's good. It was still less than the net loss they reported. Cantrust Holdings reported that its quarterly revenue rose 115% to $16.9 million. That's versus last year's $7.8 million. Got a lot of real estate stuff to talk about this week. Acre Holdings is following in Medben's footsteps. The company set up a read and they're selling their properties to the read and then they're going to lease them back. Now, the move is expected to unlock the value of these real estate assets. 1933 Industries did something similar. Their subsidiary Alternative Medicine Association completed a sale and leased back for its cannabis cultivation facility in Las Vegas for $10.45 million. And finally, Canara Biotech said that they began trading on the OTCQB venture market under the symbol CNBTF. That's it for this week. I'm Deborah Bortart reporting for the Green Market Report from Times Square.


Hello, Oscillator Sync here. One of my favourite things to do with a synth is to try and push it to do things beyond the scope of normal synth stuff. The Narrow Mono is a two oscillator analog mono synth with a built-in sequencer and while it can certainly do the 303 vibes in spades, if that's what you're after, it has a bunch of features both in terms of the synthesis on offer but also within its sequencer which beg you to take it out of that comfort zone. In a couple of previous videos I've talked about some of these features and applied them to, for example, turning it into a drum machine but during the course of making and editing that video I started wondering to myself, given all of these features and with maybe the help of a couple of pedals, is it possible to arrange a kind of live set using the mono as the sole synth? So that's what you're going to hear shortly. Five jams where the Narrow Mono is the only synth involved. In the interest of transparency, Naurand sent me the mono to make videos on but I haven't been paid otherwise and they've had no editorial input on the videos and they certainly didn't ask me to do something like this. It's a challenge that I've given to myself because I think this is a really cool synth. So with silly challenges like this we need to set out some rules so that I can be silly in a serious way. The only synth heard will be the mono and the only sequencing is coming from the synth itself. No external MIDI input at all. I am going to be allowing myself some time-based effects. So I've got the Plara reverb which is using various different algorithms depending on what suit of the jam and also I've got the flashback delay here which I've loaded in a tone print that I've created myself which removes the ability to use the delay knob as delay so you can only do tap tempo but instead now on the delay knob I have a filter on the delayed signal which allows me to do some sort of creative stuff which is quite nice and also the level control will push it into distortion past 12 o'clock which then is quite interactive with the filtering as well. I would offer to share this tone print with you but it's really difficult to export them as far as I can tell but if I work out how to do it I'll pop that in the description of the video. I'm not allowing myself to use any looping or any pedals which sort of create new sounds out of thin air so that means that things like the octrack and effects like microcosm are out of reach for this. I think it's a legitimate tactic to use in this challenge but it's just not what I wanted to do for this one in particular. I've also got the electronics platform compressor on the table which is doing sort of any sort of character compression that you hear during the jams mostly just using it to get a bit more impact from the kick and snare sounds that I'm creating and despite you seeing it hitting quite high gain reductions during the jams the effect is pretty subtle it's just kind of a nice thickening and a bit of an extra bit of attack. I have allowed myself the luxury of mastering the jams in the box so a normal mastering chain of EQ a little bit of saturation compression limiting is going on but I'm not doing anything that's sort of particularly extreme. I think I'm going to reflect on the process involved in putting these five jams together a little more in another video a little bit later so if you have any questions or anything you'd like me to try and cover then please let me know in the comments or if you're watching this on the premiere then in the live chat okay right here comes the music


What's up everyone? Today we are going to talk about milk thistle, which is Silameron, the extract of milk thistle as well. I am Dr. Ahmed Ergin I'm an endocrinologist, a diabetes education specialist and your friend to achieve success in diabetes Let's get started Hi guys, so again today we are talking about milk thistle, which is Silameron. A lot of you may have heard about it, the benefits about the liver, the brain, the blood sugar But since you're watching the SugarMD channel, more than likely you are most Interested in the benefits of the milk thistle. Okay, so surprise surprise I got something for you. Now this thing, which is our SugarMD supplement, which a lot of you have heard or used Actually now updated. We have put milk thistle in there Provided that my patients told me how milk thistle are helping them with their liver enzymes with their blood sugars So we decided to put milk thistle. We improved the formula quite a bit actually with this formula And we made it into capsules. Now it comes in 180 capsules So and then the price is much cheaper as well So I think you will like it and I'm trying my best guys to really get your diabetes under control With the least expensive possible way to achieve this Now milk thistle or sulameron definitely is used primarily to treat liver inflammation It is a powerful antioxidant. As a result, it actually helps prevent the damage in your hepatocytes Which are the liver cells. It's a pretty pretty plant actually look at that. So how pretty that is? So remember milk thistle is important for diabetes because the liver damage that happens a lot when you have diabetes Especially with type 2 diabetes guys a lot of you will develop a fat liver disease and the purpose is not to But unfortunately you probably already have fatty liver disease. Now if you look at your, you know CMP, BMP, whatever you call it the metabolic panel your doctors run and if you're ALT AST these are elevated or even sometimes ALP elevated More than likely there is some liver damage going on and if that is the case you need to stop that Now of course healthy living and everything we discuss in this channel will help reverse that fatty liver but on the other hand taking some extra measures and Improving or making that process a little faster by using a supplement such as a milk thistle may help You know you can eat the milk thistle plant But I'm not sure how many of you will go for that they typically extract the sulameron from that plant and Put in a variety of supplements like our supplement has it it helps the diabetes control in a few weeks It improves your insulin resistance But most importantly it protects your liver cells from damage Which is very important You have only one liver and you want to protect that liver now because of the Antioxidant and anti-inflammatory features actually milk thistle can help the brain damage as well Now dementia is very common as we get older and especially when you have inflammatory disorders such as Diabetes or vascular disorders the rates of dementia goes way high way fast And again anything you can do to prevent the brain damage from oxidative stress from free radical damage Your best bet is using more and more antioxidants as you can and milk thistle as happens to be one of them So guys also cardiovascular disease again the one of the most common reason for cardiovascular disease is insulin resistance Pre-diabetes diabetes you name it and all these problems are all interconnected, right? So a fat-delivered disease happens due to insulin resistance and then you have diabetes and then heart disease happens So sometimes heart disease even establishes itself before the diabetes happens So as a result you really need to protect your heart because guess what if even if you're you can manage To bring your blood sugar down to like 100 milligram per deciliter level or in European measurement I don't know like maybe 5.7 or below level. I would say you know if you if your heart fails it nothing matters anymore So you need to make sure that yes while you're controlling your diabetes and your blood sugars You need to also protect your heart, which is your primary organ to sustain your life So again, I'm not saying go become a supplement junkie and go buy this supplement that supplement But I think for my diabetics. I recommend supplements that contain milk thistle So check the link below also in the description section also give a thumbs up Give a like and share this video. We'll see in the next one All right. Thank you for watching and I want you to be more informed and more educated So to do that go ahead and watch this next video right here