Welcome back everyone to the Fedora Leads and Linux Distribution Development track, and we're here today with Lucas Ruzitzka for a talk on auto testing in Fedora. So I'll hand it over to you. Hello, my name is Lukas and I work for Fedora Quality Engineering and today I would like to give you a step-by-step guidance on how to set up OpenQA. I'm not going to go over the concept much deeply because yesterday this was done by Adam already. So those who were interested in it basically know that OpenQA is an automated test tool. Originally, it was developed by Suze. It still is developed by Suze, but Adam also adds some patches into it. So Fedora also has some part of it now and it allows to test various features of operating system using the hands-on approach, like as if a user would do it. It basically creates and runs a virtual machine, loads it either from an ISO file and a QCao 2 image and it then performs various actions inside the virtual machine, compares the expectations to the real-estate and evaluates the outcomes. The OpenQA architecture is basically that there is a controller that does the scheduling stuff and the web UI and job handling and communicates with the database and then there is a worker or there are multiple workers that do the actual testing. So you can have many workers, you can just have one worker, it depends. For the local installation that we are going to talk about, we are going to use one worker because I think it's enough to consume a lot of our memory. So first, we need to install OpenQA. That's fairly straightforward process because everything is packaged in Fedora. So basically we use DNF to install the whole stack and especially the packages like OpenQA, OpenQA, HTTPD, OpenQA worker, Python 3.json scheme and Fedora messaging if you want to consume the Fedora messages. But if you don't, you can omit the Fedora messaging packaging. So to start with the DNF install, OpenQA, OpenQA, HTTPD and the rest of the packages is a good start and this will install the whole stack. So you will need like two minutes to do it, for example, which gives us 18 minutes left. Now when everything is installed, we need to configure the HTTPD server. That's very simple too because basically there are template files, template configuration files provided by the OpenQA packages. So we only navigate to etsy, HTTPD point D directory and then copy the OpenQA conf template into OpenQA.conf and we copy the OpenQA SSL.conf template into the OpenQA SSL.conf and we enable the HTTPD can network connect for as Elinux and restart the HTTPD. Now basically that's the first part. There were times, maybe two years back when the Seelinux cooperation was not that great. So it was recommended to switch Seelinux to the permissive mode, but this is not longer required. So you can operate on enforcing mode quite safely and without any issues. Then we need to configure the VEP UI. The configuration resides in the etsy OpenQA, OpenQA.ini file and basically we need to do two settings to the file. Under the global chapter we find or global section we find the branding which Fedora recommends to set to plain. The other option being Suze, I believe, and if you wanted a nice chameleon, you can use the Suze branding. Otherwise, it's totally the same. Just there is the quite nice logo of the chameleon. And the download domains are fedoraproject.org. The authentication can have multiple modes, but for the local instance, the fake authentication is good enough. Which basically creates a demo user and you will control the VEP UI using the demo account. Normally on OpenQA production there is the OpenID authentication, so you can use your FAS account to control the VEP UI if you have the rights and if you have the permissions to do so. But for this local instance, we are not going to need it. Then we will install and configure our database. So DNF install PostgreSQL server and let's initiate the database with the PostgreSQL set up initdb command. And that's basically it. Now OpenQA is ready to be run and you can see that there is a procedure of several services that you should start and you have two options basically. Either you enable them and you make them start all the time, but because I don't want OpenQA to run all the time on my computer, so I usually start them with a script. And I believe they should be started in this order. Actually, I didn't start any other order. I always followed the guidance we have on the Vicky page. So first you start the PostgreSQL and HTTPD, OpenQA Grew, OpenQA Scheduler, OpenQA WebSockets and OpenQA VEP UI. This is enough for the VEP UI to start and to make further settings. But at this moment we are not able to do any testing yet. So let me start the OpenQA for you. It's now installed. I am using the start OpenQA.sh script which basically starts it in that order. And now you were able to see that it's unable to connect because the server wasn't running. But now when I hit a five, it still is not running. How come? I don't want to debug that now. So it might not... I don't know. Oh yeah, it shouldn't be. Great. So now you can see that the OpenQA is running. That's the VEP UI. Now, yeah, it says HTTP localhost there.  And that would immediately switch to logged in as demo. Right? And now you find manage API keys. And I don't want to show you my API keys, so I'll switch to the presentation here. And manage API keys. You click create to create the new keys and you copy the key and the secret. To some files I'm going to show you in a moment. There is the expiration mark or radio button that you can check or uncheck. So I didn't know about it or I didn't pay attention to it first. And I was pretty much surprised after a year because the expiration usually is one year. So after one year I was quite surprised that it didn't want to start the tests and it claimed about there is no API and I was like, why, what's that? And then I realized that the key has expired. So for a normal use you could create an infinite API key that will never expire if you uncheck the expiration radio button. And then you edit the etsy openqa-client.conf and under the local host section you copy the key and the secret. The secret is the second part of the key. It's quite visible in the web UI. And that's it. We have installed and set up OpenQA to work. And when we start the worker, system CTL start OpenQA worker at one. So this will start the first worker and connect it to the OpenQA and now we are ready to run the actual tests. And this can be done in 15 minutes if your network isn't extremely slow. So which gives us five more minutes and that's downloading the tests. Pardon?  If you have a dial up, I don't think it's going to take you very much time installing OpenQA but it's going to take you some big time downloading the tests. Would you say I'd be able to finish college? Between you download the tests and start it. From my experience, the problem is I don't know how dial up connections work nowadays but a year ago I have the LTE connection back at home and it wasn't the fastest connection in the world. I got problems with downloading the test repository because it has, I think, 14 gigabytes, I think. Is it that much? Yeah. And the LTE connection would have dropouts occasionally so GID would complain about them and it stopped working. So this was a problematic thing to download and once I had to head to the Red Hat office to download the repository. I know that you can use the GID depth one and you only download something but it still is quite much because of the needles and we are going to see what the needles are. So I'd say my 56k modem is not going to be downloaded anytime soon. Hello, instance. Actually, you don't need to download the tests to work with OpenQA but in this talk I am assuming that you can. Because, yeah, I will tell you a little bit later.  Then you do the repository GID clone, you clone it as Fedora and you change the ownership to Gecko test. Gecko test is the OpenQA user and so that it has rights and permissions in those OpenQA test directories. It's needed to give it the permissions. And then we have the tests. We have the tests, you can see it on the right hand side. But the tests are not loaded into OpenQA yet. So we will do it with the fifth loader tool and you can see that there are templates.fif.chason and templates.updates.fif.chason which tell OpenQA a couple of informations. It will give OpenQA informations about the available machines, about the available products and about the available profiles and about the test suites that it can run it. And to load it with the fifth loader pie application, it's a tool written by Adam and it works wonderful, I must say. Because before we had this, the tests and the machines and the profiles had to be defined by YAML file or in YAML files through the VEP UI. And when you made a slightest mistake in the YAML file, it would complain and never work. And this fifth loader changes the game totally and now it's very easy. Because if you need to add, well, from the user's perspective, it's very easy actually. Because if you need to add another test, so you can just take a look how the test is defined and you copy the JSON section and then that's it, right? Basically. So you load it, the slash C means clean all or dash C means clear all and dash L means load, templates.json. This will give you the basic Fedora tests. If you want to load updates testing, then you use the second template with updates. And that's it. 20 minutes and everything is set up and ready. So just some explanations. We will work with machines, test group, images, jobs, test suites, tests and needles. So a machine is a QEMU-based virtual machine, basically. There can be different, but we are not using anything else, just the QEMU-based virtual machines. And you can set it in the machine section of the template file. So for example, the UFI x86 underscore 64 is defined like this. So the architecture is 64-bit. The partition table type is GPT, QEMU CPU, number of CPUs, RAM, the VGA driver and so on. UFI is one, which means true in Perl. So you also have the P-flash codes and P-flash wires to define the proper QEMU virtual machine here in this machine section. You don't need to define anything else unless you need something very specific. Normally you would just use one of the available, which is either a BIOS or the UFI machine. A product is something, it's like a group of tests that run in the scope of the Fedora flavor. And it can be, for example, a workstation server or everything, and then you put tests inside of these groups. So when you run the workstation, then it runs all the tests that are scheduled for the workstation and it doesn't run the tests scheduled for server and so on. And you can define this in the product section of the template file. So, for example, the Fedora workstation life product is defined as this. So the distribution is Fedora, which is the entire thing. The flavor's name is workstation life ISO and then you have settings with variables telling the system that the desktop should be GNOME that it should use the install default upload test to actually create the installed Fedora image. The HDD size should be 20 gigabytes. It should run out of the life. The packet set is default and the test target is ISO. These are, however, user-made variables. So you can use them in the tests. If your tests should be structured without those variables, you don't need to define them, but our tests are structured around them so we make differences in them according to the desktop types and for KDE some specifics are used and for GNOME too. So we usually have one test that can have various branches depending on what we need. So some branches switch on for KDE and some other branches switch on for GNOME. This is how a profile is defined in a profile section. This basically tells us that the product Fedora workstation life ISO should run on a 64-bit machine, which is not UFI. The 64-bit is a BIOS machine. These chunks are taken from the code. So this is exactly how you do it and then you could define your own profile telling OpenQA that your section should run on a specific machine. And then there are test suites and they define how a test or a group of tests will run and it allows you to set the test variables to control the tests. So basically you can use the variables that are defined in the machine, you can also use the variables that are defined in the product and you can also use the variables that are defined in the test suite and I believe the later you define the variables then the more valid are they. So if you have the variable which has the same name and a different value, so the test suite value would override the machine value. Yeah? You can override that by pre-pending the variable name with a plus. It got very complicated because over time we realized we need to sort of do things in different orders but more or less there's an inheritance. Normally also it's good to mention that on the production the variables are pre-filled by the OpenQA schedule and by Fedora messages that are coming into it. When you run the tests locally some of the variables are not pre-filled so the test might break so then you need to fill in the variables and we do it on the API CLI command that's the best bet I think because you don't need to update the templates. So what this means basically that there is a desktop terminal test that runs for Fedora Workstation Live on x86 and ppc64 and that it boots from the hard drive, the hard drive being the disk, some flavor and machine variables .qcow2. The flavor and machine will depend on those variables being set in the machine for example or in the other test that runs before because let me show you the install default upload, the deploy upload test called install default upload will basically install Fedora and upload the installed image to the OpenQA and then this would start after the test deploy upload test so after install default upload and it would use the image created by the install default upload and now the post install variable says just take the desktop terminal and run it there are several ways how it could be done but when there is a test that should follow the installation of the image then the post install variable is the cleanest way to do I think and needle is how OpenQA would recognize what is expected we need to tell OpenQA what we want to do so we define needles needles are PNG images with defined areas so I decide some portion of the PNG and OpenQA will look at it and it will try to compare it with what it sees inside of the running virtual machine and if it finds it, it will do something about it it might click on it or it might just check that something like that is there and if it is then this tiny little test will be passed and if it doesn't see it, it will complain and it will fail so you can for example check that there is a nice Fedora logo in the upper left corner using OpenQA by defining a needle with that logo and basically the needle is two files it's the PNG file with a screenshot there is a mistake here on the slides it should be a PNG file with a screenshot and adjacent file with the area definition plus some other info each needle consists of two informations the area description and the list of tags and it looks like this so you can see that the tag is evince about shown which controls that the about window of the evince application has been shown on the screen and the specimen picture will be taken from the evince about shown.png and it would start on X position 445 and Y position 286 the area will be 133 pixels wide and 146 pixels high so this is like something like a square almost and the type of the needle is match match means visual comparison and that's what works sometimes or I have heard I have read in the documentation about the OCR needles but mythical OCR needles that I was told during FLOG that they work and that somebody on SUSE actually tests battle of Westneth using the OCR needles but it seems that the code needed to run it is still not merged so you need to patch the open QA and I haven't had time to test it yet when you want to write the test of your own you don't have to now you understand everything and you can locally run all the Fedora testing stock but if you want to write a test that's a per script that defines what you do inside of the virtual machine and what you want to expect so you basically define some mouse actions some keyboard actions some checks and evaluations and you can also evaluate script outcomes so basically you can test some graphical user interfaces but you can also test some CLI commands and all that will work and tests have various statuses such as past failed, soft failed running and so on if you want to create the test you need to create a Perl module put it in the test directory of the open QA directory we have created having cloned the repository and you should use the libraries in the lib directory you don't have to but it's there it's been already created it's been already programmed you don't want to reinvent the wheel so you can check what commands the Fedora has made for you and you can use it for example if you want to do some login you can log into a console as a root for example so you don't need to program all the stuff and all the typing and all the checking but you simply use the login to console and something like that or login to the graphical graphical session and it's in the library so you can just take it and use it in your tests and then you should probably study the test API which is the description of the commands at open.QAAPI slash test API then each of the tests should have a test header which basically is what libraries or other packages it uses so this will tell me that as a base the installed test is used strict is the Perl thing which keeps looking that your code is correct and that you don't do dirty stuff with it because normally Perl doesn't check for for how do you say that? Yeah if you define a variable so the namespace should be limited to a subroutine for example or to the entire package and Perl normally doesn't check for it Does it only support Perl or other languages as well? The tests should be written well are written in Perl the whole thing is programmed in Perl but apparently according to the documentation the tests could also be written in Python but I have never tried Using Perl makes it dirty by default doesn't it? Pardon? Using Perl makes it dirty by default I don't know I don't know if Perl would have been our first choice but the other alternative is to go and write our own whole thing and I don't know Perl couldn't possibly be that bad than having to go write your own framework from scratch and Adam will know more Yeah just quickly they have this crazy translation layer upstream which I don't remember the details of how it works but it uses some fairly janky stuff and you can write a test in Python and some team internally at Red Hat I initially turned this off I thought it was so hideous but some internal team at Red Hat asked me to turn it back on so it's now on in the Fedora packages I haven't tried it myself but it should work Using Perl to write tests is not that terrible because tests tend to use the functions from these libraries that are very simple functions and quite well written so most tests just tend to be strings of type this, assert this screen then type this, then assert screen and it's very kind of formalized so you're not writing ugly Perl most of the time there are a few cases where you write ugly Perl Yeah so for these tests a lot of the tests it's fairly simple so it's fairly readable Yes Tim? You can write good Perl it is possible it doesn't care if it's readable or not so it all depends on the person reading it so the tests that they're talking about should be reasonably legible For me for example doing this I saw Perl for the first time but I somehow got used to it now and it's okay but the truth is that sometimes we fight over readability with Adam because he is better at Perl than me so he thinks it's super readable I think like maybe not Well if you work in the sewer every day you get used to it eventually Yeah so basically if you use strict it doesn't let you do variable definitions with wrong namespaces for example then use test-top is that you should use the built-in functions and use utils means that you use the basic Fedora library where most of the pre-programmed Fedora routines are placed so test-uppy is the total basic if you don't use test-uppy you will not test anything and if you don't use utils you will need to do a lot of typing then the test file should have a sub-routine called run so this is basically a function where everything what you want to test is put anything else what's outside of the scope of the sub-run sub-routine run will only be valid inside of the test package and then you add another sub-routine test flags where you can define what to expect what will it do after the test finishes what will it do when the test fails or if you want it to fail because for example the fatal flag will tell that if the test fails then the whole test suite fails but if you don't want it because you have other tests inside of the test suite that do not depend on the first one you don't want to make it fatal then you can ignore the failure and that means that it will ignore it and continue sorry you can set the test as a milestone which means that after the test finishes the state of the art of the virtual machine will be uploaded to OpenQA again and then the subsequent test will be starting off that milestone so this is for example useful this is for example useful when you want to test an application and you don't want to do starting it all the time but you would like to take all the subsequent tests from a clean application so we start the application once it's running we will upload the state of the art to OpenQA making it a milestone and then we for example create a new file and then I don't care what happens next because the next subsequent test will return to the milestone and again will start with a clean started application so sometimes that's good for example when a test fails and the subsequent test would expect something what's not there because the previous test has failed so I can fight it with this rollback and always rollback means return to the milestone when you don't set any flags then it will be zero I believe or maybe fatal will be if you don't set any flags I believe it will rollback if a previous test module fails but it won't die because fatal's default is zero I think I always use at least one flag so that I know that what it should do basically and there is a test example for desktop that looks like that but I'm going to show you another test these are the libraries that currently are available so it probably is self-explanatory like modularity.pm would be functions that we use when testing modularity Fedora distribution will be functions specific to Fedora cockpit you know it's you can expect what's in there what makes a library a library if you want to create one it's another Perl package that starts with the package keyword then you give it the name like for example package desktop tools and you use the base exporter and then you export the variables using for example our export is startgnome software and install application this will enable the sub routines in this package to be used very easily without having to call anything else even the test files without exporting it you would have to call that like desktop tools colon, colon and then startgnome software which is not very convenient so it's good to export those functions now let's take a look how we can create a calculator test a very simple application test for a calculator the test will be placed in the test directory of the repository files or the repository directory and we can start for example by touching it before we start to write it we can register the tests in the templates to make sure it will run in OpenQA because normally without the registration in the templates it would not work it would not start bad thing Sumantro is not here because he's going to need this hopefully he will see the recording so the test must be registered in the templates and you want to give it the architecture, the product and the variables so basically you need to add a section to the test suites section that has the name of the test calculator you will give it the profile where it should run so this would run on workstation life 64-bit machine so it won't run on the UFI machines just the BIOS machine and it will take the pre installed ISO it will run the calculator test and it will run it from the disk flavor machine QCOW 2 whenever you make a change to the template file you need to reload it to OpenQA so you do the fifth loader C-L templates.fif.tason and when we want to run this test from a pre-installed image which is also possible we can replace some variables and say that the HDD-1 is not something generic but it's a specific one it's the workstation.QCOW 2 and the user login is test and the user password is weak password and now I am loading the tests using the entry point system which allows me to put a list of tests that I want to run and so I can start the login test which logs me into the system into the GNOME session and then it runs calculator test and again I need to load it using the fifth loader so the basic syntax of the test file is this we have talked about it there is one more thing I wanted to stress to you that each test module must end with the one because each Perl module must return a true value which is defined here on the line with one if you don't do it it will complain and it will not run and it's problematic and it bit me a couple of times in the beginning so don't forget about the one and then you can create a subroutine that will only be valid for the test itself for example you want to repeat something a couple of times and you don't want to repeat yourselves so you can define sub delete result for example and say that this result, this delete result subroutine will always press the escape key when called so such a simple one but then you can use delete result instead of send key escape and if this is more complicated then you can save some time typing the stuff all again and all again you could theoretically take this subroutine and place it into a library if it makes sense to you and then we want to start the application so in GNOME, normally we can hit the super key and we do it with send key super we type string calculator the max interval 10 makes it type a little bit slow in Fedora you can find a wrapper for typing strings that is type safely or type very safely but I'm not using it here because I wanted to make it as generic as possible using just the test API commands so the max interval makes the typing a little bit slower so that the GUI has time to respond and the texts are really what they should be because if you type too quickly sometimes letters are gone and then the texts are incorrect and basically the tests fail because of that of the typos that are made with the engine then we send the enter key and we check that the calculator has started assert screen means check that we see this particular thing in the screen then it's merely some clicking assert and click would mean that it checks that the needle is there that there is the widget that we want and if it's there it clicks on it you can add the button parameter to the command and you can define whether the button should be left right or middle if you don't do anything it's left so normal clicking is assert and click also by default the open QA will wait 30 seconds until the widget appears so if you think that it should be there and you want to specifically check that it starts in 10 seconds then you could define a timeout parameter and you could make the timeout to be 10 seconds if you leave it out it's 30 seconds for some tasks you might need longer so you can make it longer timeout 60 seconds 120 seconds for some installation purposes it's maybe 400 seconds of course for uploading tests this is quite long so basically click on button 5 click on button add click on button 7 click on button equals and check that the result has been shown so that's one part of the test then we can multiply but no clicking just using keyboard so we will type the string 12 times 15 max interval 10 we hit return or enter and we check that the result has been shown we delete it again and then we can switch to the keyboard mode using the control alt K combo sending the escape key a complicated string with brackets that should basically be very clever about what to calculate first and we hit enter and check that the result has been shown again and that's it we have the test now we have registered it so we can start it but I'm going to do it in it so OpenQA WebUI now will show us everything about the tests but it can't be used to start the tests actually or at least I don't know how so you are using a OpenQA CLI command to make an API call basically it looks like OpenQA CLI API dash X post ISO and you use the file.ISO which is the ISO that you want to install just quickly to make this part a bit less scary possibly there's a slightly higher level of running you can use if you are okay running on official Fedora images called Fedora dash OpenQA which is the same thing the official schedule uses and with that you can use it to just say hey schedule on this image from this compose and it will do everything for you but the tradeoff is that it can only schedule for official Fedora images and it will need to download the image so you can use it to make it faster I am using this because I found it in the documentation the first time I was trying to run the tests and I used to it of course and then I keep those commands in a file so I just uncomment the one I need and run it so you can pass variables also using this command some of them must be passed like district, version, flavor, arch and build sub-variant, desktop and development are good for installation tests so if you have a pre-installed image it's not that important but if you want the test to install it so it must know whether it's installing a pre-release warning or a pre-prohide if it's being developed because the development for example checks that there are some parts present during the installation like the pre-installation warning or pre-release warning and if it's not there so it pretends that no pre-release warning is shown but the pre-release these variables should be passed and then it is being scheduled and you can see it on the all tests page so I will you can also see the tests that have already run whether they passed which is green whether they soft failed which is yellow whether they failed which is red and you can click on the dot to explicitly see the details of the tests and then you for example see that this is probably from the it looks like the KDE start-stop test suite so the ABRT started with some hiccup aggregator started and finished okay and so on test needle when you click on the icon of the image you will see the screen that was recorded and you will be able to see the area that was compared and if it is green it was found and the candidate needles and tags tells you this was 100% K mail runs and some number which means this image from the virtual machine resembled 100% what we expected so that's fine normally if you don't do anything so by default it tolerates 4% so when 96% is still there so the needle is taken as past if it's less than 96% the needle is considered not found and you can of course lower the bar a little bit and make it 90% or you could set it higher because that's what you need and if there is an error it's marked in red and there is basically two red fields for every error and mostly the error in one test there is just one error because then the test finishes but there are two places where the needle was expected and not found and the next one gives you some information that information is a generic one for like this test died no candidate needle and sometimes you could define your own strings so you could basically get quite a nice information about what happened in the test and Tim I was thinking whether if we actually put some effort into describing those failures a little bit more exact whether that could be used to train the artificial intelligence to make the prediction a little bit better I don't know if the test failed you can restart it from the web UI the test detail page all the time so there is a restart button and you can stop it when it's running by pressing the stop button or you can just restart it when it's still running dealing with needles so you add a missing needle using the needle editor that is part of the web UI you can define the area you see the green area here so it's the needle defined for the P button on the calculator you can name it and check the name or select the name it's above this not part of this and in the upper right corner you can change the match level so you can make it less than 96 or more than 96 so it's good that if you don't want to deal with the needles elsewhere so you can just write the test without the needles and you can create the needles with the first run of the test by using the developer mode that could be also switched on in the web UI I am going to show it to you when the test runs I am sometimes using the needle application that I sort of wrote when I thought that one totally needs a needle editor and it runs offline and it's quite good nowadays because it can connect to a virtual machine so when you develop a test and you make it manually you try it manually in a virtual machine so you could use the needle application to take screenshots out of the virtual machine and you can create the needles and run OpenQA so you can save some time because creating needles in OpenQA is a little bit little bit slow let's say and it starts to be tedious if there are lots of needles because you need to open the test editor you edit the needle, you save it then you have to click on come back, then it waits for some time then you continue the test as the needle and it fails with another one and then you repeat the procedure so when you feel like that it's good to do this while developing the test and then you load everything into OpenQA and you only fix what doesn't work you can okay that's not important you could use the Chancery application which is a very simple editor that I also wrote as a sort of exercise in Python and this is good because it has pre-loaded test-uppy routines so you don't need to go through the test-uppy but you just select what you want and it will give you the snippet in it so it can help but once you know the routines, actually you don't need it anymore because then you just type the routine and yeah okay so integration with Fedora of course everything is based on Fedora everything is supported from Fedora everything is installable from Fedora we use it on a daily basis so the Fedora testing stack is up to date and should be working we don't have breakdowns much because our procedures don't allow to merge something that has not been reviewed and Adam is a strict reviewer so his hawk eye will not let any problem pass into the production repository so if you want to test something on Fedora using OpenQA it's very easy to do so and as I said you can install it, you can set it up in 20 minutes and you can see this here that you can follow this is just for the sake of the recording or I will upload the presentation on the SCAD so then you can take it and you can see that there is the OpenQA documentation that is maintained by SUSE also the test that this talk is based upon so when you open that link you will have a step-by-step how to install it and the OpenQA outer instance repository that is used to load to hold the tests and hold the needles is on Peggy here thank you for attention but we still have not have the 10 minutes I believe so let me show you how the test really runs inside of the OpenQA so first I need to show you the Farlib OpenQA factory where the images are placed you can see that there are lots of images, lots of QCAU images starting with a number and then disk workstation life ISO 64 bit.QCAU2 so remember the product flavor variables that were in the test suite definition so this is the disk workstation life ISO 64 bit that's the part and each test will create its own image and the number is the test number to which the image belongs actually when it's there you could actually repeat the tests again and again and again because we have something they called an asset to start with once you delete the underlying image you can't restart the test anymore. That happens to me on production where I could come back I would like to come back a couple of days and try but it's already deleted so it doesn't work but on the local machine until you manually delete those assets you can still repeat those tests so you can see that there is the workstation.QCAU2 which will be used as a starting image it's a pre-installed image so I don't need to do the installation test before because we don't want to waste time on 15 minutes Fedora ISO installation you can say you can see that the it's owned by GecoTest here you can make an exception you can either make it worldwide readable also that will work too but I do it I always change the permission to be GecoTest because I think it's cleaner that way but here in this directory it's not that important okay then I will go to CDOpenQA where I have the run test script you can see that there are lots of them those commands commented out and I can select what I need so it's easy to start it I like it sort of and I am going to start well I realized actually that it totally doesn't matter what is in the ISO variable if you use a QCO image for the test you could also leave it out in this case so let's ignore the ISO variable the first one is FEDORA version is Rohite Flavor is Flock ARCH is X8664 BUILD is Calculator Test SUBVARIANT is Workstation and DESKTOP is GNOME to make it safe but I don't think we are going to need the GNOME or Workstation variables because we are not installing stuff so now it tells me that one test started or one test suite started zero failed the ID number is 4158 it starts with zero so you know how many tests I have run on this installation particularly and the product ID is 152 that's not important and now when I go to all tests I can see the calculator test running 0% but the progress bar is a little bit slow and it changes in steps when I click on it I get the live stream of what the test is currently doing so you can basically watch if it does what you want it to do here you can have the developer mode so by clicking on it you can switch it on and you confirm to control the test and now here you have fail on mismatch as usual which means if the needle is there fail and if you leave it like this it's like with the development mode off so you can still have it on but it doesn't affect anything when you change it to assert screen time out then any time a needle is not found it will give you the opportunity to open the editor and create it so this is how you can create needles when the test runs and we are not using it in our test but sometimes you can use check screen instead of assert screen which returns a true value if the needle has been found and that's a specific thing and you can also make the development mode control the check needles the problem is if the check needle for example is not there on purpose and you switch it on then it will complain and it will force you to create the needle once you forget that it's not it's on purpose not there and you create it then you will get some troubles later so now you see that the calculator test has ended in the meantime and it has passed which is great on the detail page I can see what the test actually was sometimes if you forget to sing the repo you might be testing old tests I am not developing in the open QA repository because it's that requires everything to be typed with sudo so I am developing a side and sometimes I forget to push or pull and then it does the same thing that should have already been corrected so you can check that the test is what it should be because you have the test script here you can see what steps were taken and what needles were compared so for example this one makes sure that the calculator has started and it's 100% which is great sometimes when the GUI changes so it might be 0% and then you need to read the needles then it checks for the button 5 again it's 100% and so on you could see the variables that it uses to run the test so sometimes when you have a Fedora stack running and the tests start failing in big numbers then probably something is wrong with the variables so you can compare the production variables and your own variables and you can set the variables correctly and then that works like magic and suddenly the tests start working you can also take a look on the Auto Instlog TXT which is very important for failures which basically tells you everything what happens during the test run you can see that you have the blue line here which basically is the graphical weight login starts here and this is what happens so it wanted to check for the needle must match login screen and at first it didn't find it didn't find it then login screen timed out and it wasn't found but because it's check screen so it was probably correct then it wanted to assert the screen login screen and then it found it after 10 seconds approximately and continued you could also use the DIAC routine to put or print out messages to this Auto Inst Log TXT file so that might also be the way how you increase the readability of the log files if you need you can leave comments here of course in production you can put the bug number here and then it shows that the bug has been already created so on production you might see that there are little bugs, symbols just below or next to a failed test and you know somebody has already created the bug and that's it also what is interesting you get a nice video of the process so you can it's quite fast video but it can be slowed down a bit using the Firefox menu and you can set the speed to 0.5 it still is quite fast in 0.5 but at least you can see you can stop it also but that is very difficult to find the correct place but it can be helpful too so I think this is it and if you have questions you can ask with all the talk about needles I'm missing either thread or a haystack or to sum it up I don't know to be sincere maybe it's because of the haystack maybe because it finds small portions of a picture in a big image maybe it's because of that well sometimes you do you know there is a strategy how you might find a needle in a haystack to carry on that analogy usually it's you're looking for a needle in a haystack so the haystack is given the needle is given what do you use for that a magnifying glass or whatever or a magnet but what you're doing here is you define the needle which is put into the haystack and then you check whether the needle is there it's a weird terminology I might the haystack basically as I understand it is the PNG file the needle is the little portion and both are there just the one you expect might not be there but since you define the needle you can make it as big as you like it could be the entire picture true and then it's not a needle anymore is it then it's a hammer or something more okay that's a very good point which gives me which reminds me to tell you this the size of the area actually matters because the bigger it is the more problematic it will be to find and sometimes where do we have a tiny tiny pixel glitch in the image of the virtual machine so it won't be found if it's too big and you expect 96% you will have troubles so the best strategy is to keep the needles as small as possible you can if you need to check for more you can define more areas inside of the one needle but the smaller they are the better for you on the other hand of course I once experienced a case when I wanted to check whether the button was lit or not so basically it looked the same it just would be a little bit blacker or with dark a shade went off and with a lighter shade went on and the classical 96% wouldn't be able to cover that because in both cases it would be above 96% so it wouldn't be able to differentiate between off and on and I had to explicitly make it 100% and only then it would distinguish between the states so sometimes it's like it's a funny play with those needles my first comment was of course more like a joke and trying to get my question in there I totally understand what it's doing and it's very useful the way it works sometimes you ask yourself these questions like why did they use that name and why did they use that terminology it doesn't make sense to me it doesn't make sense to me how a chameleon could look at one side and another side at the same time does it support accessibility testing accessibility testing like like this for example or which accessibility do you mean so the calculated test that you ran if I do it on a high contrast or say a color change mode can I reuse the test you can reuse the test but you have to recreate the needles so you could have basically a couple of sets of needles and you could for example you could use the calculated test on high contrast normal contrast large test text and it would work this is interesting because this is why the needles have the tag concept so you would have the exact same test logic and you just have three different needles which have the same which all match on the same tag so we use this a lot we have lots of cases where we have different needles that match on the same tag because of various conditions making the screen look different and basically just to add to Adam if you run a test the calculated test and you have the needles to create you have created the needles to support the high contrast for example or the normal contrast so it doesn't matter actually which one of the tests will run both would pass because the needles are there already so you don't have to tell it use the high contrast needles so if the test is high contrast and the needles are there along or next to the normal contrast needles the test will pass okay I have a question about let's say the target audience for this so who should be most interested to look into this let's say if I am package manager I have some graphical application in Fedora should I try to install this and create a test then submit it as a pull request for you or is it targeted at me or not well I would like to say yes but the question is do we have space for it do we have resources for it I believe there is a single test for example a single application is tested we would have resources to do it if it's like a hundred applications maybe we don't have the resources because the time to run all the test is pars so basically if you are a package who develops an application that is part of the installation or heavily used in Fedora so then I think it's good to make a pull request or make a pull request we could take it to our stack and test it there are different directions someone could go with this as Lucas says if you want to get a test before putting too much work into it it's probably best to file an issue and we can discuss whether that's a test that we would want to carry in the officials but you can also just stand up your own OpenQA instance as Lucas has explained and use it you can do this kind of permanently there are cases of people doing that there are other projects which are sort of OpenQA like Nome and Debian stuff so that's another way you could go with it but yeah we do have resource constraints on the official instance I have for example talked to some Red Hat teams about OpenQA and they said it looks great but it's too complicated to maintain it actually I don't think it's too complicated to maintain a local instance because it must work sometimes so the basic thing is to install it and run it that's it nothing to maintain because it's maintained by Adam it does take you 20 minutes to get your initial instance running but then after that it will kind of sit there and work like you can have your pet instance sitting there and not use it for 6 months and if you come back and update your system and try and run a test it will probably be okay but once you've done it once and figured out how to write a test and add it into the template it all gets a lot less overwhelming so it's a little bit of an initial setup and then a sort of plateau of there is one problem that could actually arise after an upgrade and that's the Postgres server because sometimes it gets updated and you need to update the database running the specific command if you don't do it it won't start and then OpenQA won't start but it's probably pretty once or twice maybe and one more question if I understand correctly I guess this is most interesting to some teams that could be working on some bigger projects or some maintainers of some high profile applications for example like a library office or something that would be interested to be pushed into the Fedora production instance or perhaps some passionate maintainers that want to run their own local instance is it correct? Or by anyone in the community who wants to help us creating the tests for Fedora stack thank you very much


And so I'm all about creating those experiences where it's like, wow, that was incredible. And I'm not at creating anything at the same time. It's more of this idea of putting together the perfect location with the perfect food, with the perfect, like, you know, medicine and group of facilitators that are going to really bring people through a deep transformational experience that starts with the preparation all the way through the end with the integration, usually working with 5MEO DMT as well as EBOGA, but both separately. So those are two different retreat formats. Like, for instance, with the 5MEO retreat, we do purification rituals to prepare the person to go into this deep work with the Bufal Alvarius. And that includes doing to miss call, so sweat lodge, traditional sweat lodge, to really help them, you know, kind of cleanse some layers off to allow them to surrender deeper into the work. Boom. What's up, everyone? Welcome to Simulation. I'm your host, Alan Sakyan. We are on site at Consciousness Hackings Awaken Future Summit. We are now going to be talking to Tricia Eastman. Hello. Hi. How are you doing? Such an honor to be here. Such an honor to be hacking some consciousness and exploring psychedelic states and meditation with you. Thank you so much for coming onto the show. I really appreciate it. And that was quite a well-synthesized. I agree that that is what is going on here. It's such a great group. Tricia's background, she's the founder of psychedelic journeys, altered states, the role facilitator, duty of care. We're going to be unpacking this. I'm very excited. Why don't you tell us who you are and what you represent? Wow, that's a big thing. So who am I? I've been in the role of medicine woman for about four and a half years now. I've done some very powerful initiations in Moon Dance tradition. I work with the Five M.E.O.D.M.T. from the Bufo Alvarius Toad, which is also known as the Snorin Desert Toad. I've been initiated in several traditions of Buiti, which is an indigenous tradition from Gabon, which is Central Africa. They work with a sacrament called Iboga, which is one of the most powerful sacraments, I would say, as far as shamanic as well as psychoactive experiences. A very potent healing tool, also being used for addiction. One of the alkaloids in the plan is a very potent healer called Abogaine. I got my start at an Abogaine clinic in Mexico called Crossroads four and a half years ago and have just really been number one. I feel that it's important to balance the sacred and the science. I feel that in our modern era, we have a lot of really beautiful wisdom keepers that aren't going to be on the planet for very much longer. So I try to bring in different elders and weave them into the different events and things that I do. For instance, I am launching a new project at Burning Man called Ancestral Heart where I'm going to be bringing two tribes from Africa, from Gabon and from Ghana to share their traditions, storytelling, play, music, drumming and ritual and ceremony. But nothing, of course, psychoactive on the fly. I really, we want to introduce people to the way of being and the wisdom that comes through these beautiful elders rather than necessarily focusing on the psychoactive plants and things like that. Okay, four and a half years of being a psychotherapist, is that fair to say? I can't say that I'm a psychotherapist because I am not certified for that. What I am is I help people really work through their trauma. So I definitely do a form of therapy, but it's not in the form of what you would find in a college and you receive a certificate for it. Yeah, this stuff is so strange. Like, oh, you get a certificate for this versus actually go through the process of doing it so many times, hundreds, thousands of times with people, helping them versus having a certificate. It's kind of like, yeah, it's funny. Okay, so there's been probably, what is it, hundreds of people, if not maybe even a thousand people? Over a thousand people. It's been over a thousand people. Okay, whoa, that's crazy. Okay, so before we get to science spirituality and the new Indigenous, because that's very interesting, what has it been like working with a thousand people? Well, you know, every single experience, I feel like we're all mirrors of each other. We're all mirrors of the divine and I feel like each one has been, you know, I like to think of it like when babies are being born in the hospital and you see that fresh new life that's there that is just so perfect and so beautiful. I feel that these processes, there's some really, you know, sometimes gnarly layers that shut off and that new person, they look different. I mean, if you look in like a plastic surgery office at the before and after pictures, some of the before and after pictures of Iboga would be more profound, you know, because that trauma, we wear that, that's our real makeup, like on our faces, the sadness, the grief, the anger, all those things, like we wear that on ourselves. Okay. And then the process of going through a session with someone like you that's working, helping people work through some of the trauma or and heal that that when when when working with a healer, the process of integrating that, how does that process work when you kind of see that what was what was being worn by someone that that trauma that was being worn that it how does it yeah how does what does that process look like when it becomes integrated and people have that fresh baby, baby face. Yeah, I mean, I just think about like how much like mental chatter is connected to each one of those expressions like the parts that most people would probably say are ugly about themselves, you know, that that they learn to love them and they go through the process of loving them through acceptance, through going through them, through feeling the feelings. And then once they've done that, the energy leaves the body and sometimes it's pretty intense. Sometimes they purge it out and they're like, wow, I see my dad's face in the purge pole, you know, because it's something maybe that that with some conditioning from their father. And sometimes they just feel really sick and then all of a sudden they burp and they're like, whoa, I feel better and they release that energy from the body. Sometimes they laugh. Sometimes they cry. Sometimes they scream outrage that they've been holding for, you know, who knows how many years where they're just like, and then, you know, once that's gone, there's just room in there and it's quiet in there. And, you know, it's a good place to live. And so they're happy because of that, you know, there's there's no reason not to be happy. It's like their home's been cleaned out. Well, okay, what's going on in like the let's talk of a couple things here. First is what's going on on the on the physiological side within people when they take a plant medicine and which plant medicines are we talking about? Okay, well, pretty much all of them have a story arc. And the story arc can happen really quickly or can happen really slowly. The stronger ones, it usually happens really quickly. And that's why it can be so intense for people unless they've done a lot of other spiritual practices or they've done a lot of other psychedelic shamanic work before to where they can handle that pace, or handle that depth of the pain and the things that they have to experience. So the way it starts is phase one is having to clean out the closet.  And so literally imagine someone's going through your closet and like, Hey, Alan, here's a skeleton. You want to keep this skeleton or you want to get rid of it. And if you want to get rid of it, all you have to do is let go. You're like, Oh, God, that skeleton's horrible. It's from the 80s. God, get that thing away from me. You know, that's not going to help you get that skeleton out of your closet. You've got to be like, Okay, I accept that I see this is a skeleton that, you know, I'm acknowledging what happened, what I did. And I'm going to breathe through this. I'm just going to face it. And then guess what? It goes away. You have to see it before it goes away. So then you go through that process of cleansing. And then once you're cleansed, you can't get into the spirit world unless you're clean. You can't get in with baggage. You are not allowed to bring anything with you but your soul and what your soul knows. And so then if you're lucky, if you did a lot of good cleaning and you let go of those skeletons, then you get to go into the spirit world. And that's usually where you meet your soul. You get insights around your purpose and, you know, the future and, you know, what, what the universe is all about on a bigger scale and meet guides and all kinds of cool stuff. Whoa. Okay. So some of the story arcs, depending on the medicines that's part of the journey, can be fast. Some can be slower, but almost certainly we're going through a process of the of skeletons. Yeah. Okay. And sometimes there's also the process of just kind of just diving into the oneness, into the unity. Into the unity. Yeah. And so, okay. Okay. So, so it depends on the medicine. Sometimes he gets shown skeletons. Sometimes you go into unity, kind of just depends on the, on the medicine. Okay. Okay. Yeah. It seems like with 500 units, it's more towards that. Straight to the medicine. I have another easier way. Okay. Yes, please. If you want to hear. Yeah. So think of it like your chakras are an elevator and each floor is a destination in another dimension, but your elevator is going to get stuck and not let you travel if there's trauma in the way and it gets stored on all of those floors. So as you're going through those different floors, you go up into different layers. When you get into the higher floors, that's when you start to dissolve and, and you know, the term drop rejoining the ocean, which is the idea of the ocean of consciousness where you become one with all things and you have less of a sense of physicality. That happens once you've made it to the sixth floor. And so that's where through the third eye, the soul leaves the body and is able to travel. And so when you go through these different floors and the elevator, you're basically stopping and realizing some, some things you've got to resolve before you're able to, to travel, you know. Yeah, that's good stuff. Yeah. Yeah. So, so, so we, we, we resolve the, the traumas, the skeletons in the closet on the way up to the, and you said there's so many things that happen in that when, when we do merge with this unity, when the drop merges with the ocean, that there is some sort of a soul to whatever happens in that place that you speak of is, yeah, is up to I guess people's experiences. And is there some, is there a reoccurring theme that people feel when they dissolve, when they have the soul leaves the, yeah, where do, where do they go? Do they go past this 3D reality? Where do they go into some other places of existence? Well, I can tell you from my experience and what I've experienced, you know, witnessing others. And what I experienced is very similar to the Tibetan Book of the Dead. And it's like the same thing that happens when you go through the birth canal when you're born, all this pressure and then all of a sudden you pop. And that's basically what happens when you pop out of the birth canal. The same thing is happening with your third eye. You're basically going through the birth canal into the spirit world basically. Into the spirit world. Into the spirit world. What happens in the spirit world? So the way I've experienced it is there's different layers of these ashrams of consciousness. And these are schools and we're connected through our own galactic ties to specific ones. And then there's also ones that we can build connections with. And so when we're going into these different places, we're receiving, I call them light codes, which is just pure information. And you can literally download years worth of information like what would take someone, you know, the time it would take to get a PhD within seconds. You can receive like a lifetime of information. And so really the more that you can surrender, the most pure point is the void. And the void is the center of the entire universe. And it's the womb of the entire universe.  So I call it, which is the reset. If you go through the womb and you're able to just be in the complete stillness and death of it, then you come out the other side being reborn. You get to leave some stuff behind and then you revisit that void. Do you revisit the void or do you just visit once and then you rebirth reborn? You can visit it as often as you want. You can kind of carry it with you on a moment to moment basis is yeah, I mean, it's the point of creation and the point of destruction. And so it's the ultimate place to go. Because all things are birthed from there. So anything that you want to birth you can go in and you can you can rebirth through that through that place. And then the ashrams and the consciousness schools and being able to, you know, what is it that we are part of an ashram? And then we say like, I want to go to playground earth and go learn 80 years of stuff. And then I want to come back and go to a play at a different place and keep learning stuff. Is this kind of the process or what is it like? I think everyone has their own path. And I think some souls will come to earth and learn specific things. And then they might go on to be a galactic logos themselves where they might go into one of these areas and basically represent the essence of that. And so for us to talk about it in this space, it's very different to articulate because the human brain is like a cache. It's not an actual knowledge system. The way that we are able to have like the great thinkers of the world are able to create these cords to those galactic ashrams. And so for instance, Einstein, all of, you know, the great thinkers that have existed the geniuses actually did that outside of their mind. They were thinking beyond this, you know, thing that's stuck inside our school. And they realized that this is just a temporary memory system. And within the system, we actually forget a lot. And we don't have access to very much intelligence. Okay, this that was such a good short bit on on on. Okay, then then you started journeying us into science and spirituality blended together and also the indigenous. Okay, so when I go to like psychedelicjourneys.com and I go and I visit your page, am I what am I learning? What am I signing up for? Am I going to retreat centers around the world and experiencing Plamas and journeys with different healers? Is this kind of part of them? Yeah. Well, I really am passionate. I feel like my life, one of my favorite things is I feel like all of us are ultimately here to create art. Like art is the highest form of expression as a human being. And so for me, I feel like my art is ceremony and being a healing artist, I like to create experiences that are different than anything else you could experience. And you know, when I worked in the normal world, before I was doing this work, I always had a saying that was like, I don't charge by the hour I charge by the awesome. And so I'm all about creating those experiences where it's like, wow, that was incredible. And I'm not at creating anything at the same time. It's more of this idea of putting together the perfect location with the perfect food, with the perfect like, you know, medicine and group of facilitators that are going to really bring people through a deep transformational experience that starts with the preparation all the way through the end with the integration, usually working with 5MEO DMT as well as EBOGA, but both separately. So those are two different retreat formats. Like for instance, with the 5MEO retreat, we do purification rituals to prepare the person to go into this deep work with the Bufal Alvarius. And that includes doing to miss call. So sweat lodge, traditional sweat lodge to really help them, you know, kind of cleanse some layers off to allow them to surrender deeper into the work. Okay, so all right, I'm I'm now someone that is wanting to sign up for some of the psychedelic journey stuff. So then am I when I go through the the portal and end up at one of the centers, there's a whole process of even pre and even getting to the center, like there's like a bunch of stuff that I have to do in terms of you have to you're like you're trying to set up this perfect ceremonial location, nutrition, all this type of stuff to make the experience exactly what it needs to be. The awe, some experience. And then there's also this like intake information that you need to know about the person. There's like, so yeah, so tell us about this process. So what's really important in the process is to really identify who are good candidates for this work. And so, you know, one of the things I was talking today in my talk about is these three spheres that I look at with every person to make sure that they're ready. And one is their own spiritual practices, whether it's meditation, yoga, whatever things are going to help them integrate, but also the things that are going to help them center if they're having a hard time in the experience. The second sphere is the level of trauma that they have. So whether it's high, medium, low, because that will also impact if they're able to even surrender to these two powerful medicines, which many would classify as the most powerful psychoactive medicines on the planet. And then the third is their experience with other psychedelics. Are they more of a novice? They've tried mushrooms one time in high school. Are they someone who's a psychonaut, or are they someone who's done a lot of like shamanic plant experiences such as San Pedro or ayahuasca? Typically it's someone who is on the higher experience level where they've had some other shamanic experiences and they want to go deeper. They want to do more work and they want it to be in a really well-held container. And so those are the ideal. And so I look at a balance between those three factors. You know, if one of them is really off balance, there needs to be a strong foundation in the other two in order for it to make sense for them. Because we want them to have a good experience and be able to receive the awesome that's waiting for them. Yes, yes. And then what are some of the when you have someone go through the process and then they're maybe coming in with some sort of a deep trauma. Yeah, so what are some of the things that you actually specialize in healing and integrating? Related to the trauma. Yeah, yeah, which specific ones for those that may be interested in both learning or as well as healing themselves? You know, the way I work with trauma is that, I mean, a lot of people have really, really deep trauma.  Doctors have classified it at that level. And they need a really gentle, slow approach, which is really about powerful mirroring because many of these people who have deep trauma, they're running away so deeply from their pain and their suffering. And they have good right to, you know, if they with the suffering that they're because that's all stored in their body. And so it's a combination of really seeing where they're at, you know, what they're comfortable with, and being able to kind of doula the trauma.  So it's just really helping, you know, maybe it's holding their hand, maybe it's helping to move some energy in the body, putting some pressure on, you know, a certain part of the body that is, you know, where that where that trauma is stuck. And then sometimes towards the end, it might be helping that person ground by like touching their feet or, you know, doing different techniques to help them to come back into their bodies, because they just don't have those tools. And so it's about, first of all, giving them the confidence to see, you know, because they deserve it, because they went through that experience that they're able to release that trauma that they're able to face their shadow and their darkness. But then it's also the tools that they learn, and then also learning a new pattern of feeling your emotions versus running away from them. So it can be really powerful if it's done in a very soft way. And then there's a couple, there's a there's a somewhat of a routine that you follow with with 5MEO DMT and Iboga. Yeah. You mean in terms of beginning to end? Yeah. And how, yeah, beginning to end through the whole, yes, was it a week is the whole five days? Yeah. So with the 5MEO DMT, I do it in a format that I've kind of created that I think is a really potent way of honoring the medicine, which is doing three ceremonies over three days. And as I shared before, we do the temezcal first. And then we close it with a cacao ceremony. I kind of call it the medicines of Mexico because we're using Mayan cacao. We're using temezcal, which is, you know, part of the Mexica tradition that I'm initiated in and my blood, my family line, as well as the Bufo al Various, which is from Mexico too. So it's a really beautiful combination and really honoring the the lineages from Mexico and the traditions and the beautiful medicine, which I which I love so much, all of those modalities. And then also the iboga is done in two nights of ceremony. But we're also doing purification rituals beforehand as well, which we do the spiritual baths, which are kind of like Olympia. But it's a it's a design to kind of clean you before you go into the medicine.  You wouldn't want to show up in the sacred, like all dirty. So the purification rituals are really essential for the process. And that is usually a five day process, both both retreats once five days, the others actually six days. Because we include extra day on each one for rest and integration. Yeah, you wouldn't show up to the date with the dirty shirt. And yeah, and you need a day of integration at the end, and you have this specific style of ceremony for both five and me as well as iboga. This is there's so much to still unpack and understand. I want to know on a on a like a neuroscience and physiology perspective, do you know what's going on with the heart or the brain during the times of like, seeing the skeletons and integrating them or during the times of bathing into the unity? Like, yeah, what's happening? Yeah, it's really interesting because when we work with trauma, we look at these circuitry systems that are regulated by the vagal nerve, which there are several points used in somatic therapy designed to reroute the energy and open up the space so that rather than working in an amygdala based system, which is the reptilian brain, you're functioning from the frontal lobe, which is more of like an observer type aspect of approaching trauma, you can still have a trauma activation. But instead of being in it reliving it, you're actually like viewing it like, oh, this is an energy that's leaving my body. Or this is something that happened that I'm now re experiencing, but not necessarily like having a reaction, not being reactive towards the trauma. So what happens in that process, typically, whether the trauma is being lived, or whether the trauma is being observed, you're still going to have an elevation of the heart and a lot of the physiological symptoms that happen like the first time that you had the incident happen, whatever it was, like maybe you thought you were going to die, or maybe you felt unsafe, or maybe you were just really afraid, whatever that is, maybe your heart started beating really fast, maybe you started feeling lightheaded, maybe, I mean, all the symptoms of high levels of stress. But the difference between when you actually are viewing it from the observer or the frontal lobe is that you experience it and then it's gone. As we're with the vagal nerve amygdala loop, it never releases, you just keep re experiencing it over and over and over again, and it never leaves. So it's there and it gets reactivated. So that's why it's so important to face it and release it. And it's great to have someone there that can do some touch that can kind of put their hand on your heart or put their hand behind your neck. And there's a point here, there's a point here, and then there's a point right there that can be released. And so the touch is really useful because it's like, okay, we're going to release this. Okay, breathe through it, breathe through it. You'll feel the difference like on the back of the neck right here, where it'll just like open up. It's like crazy how much tension we hold in our body that we don't need to that we can let go of. Yeah.  And so I feel like there's still so much more, you know, I feel like, you know, lineages thousands of years of thousands of years of wisdom. And I have just so much like reverence for these for these plants and for the wisdom that they've taught me because I don't know anything, you know, the plants have taught showed me everything. And I'm really, really grateful to be able to share that wisdom and to be able to, you know, be a bridge for them to be be a representative. And I say that with humility, you know, I'm grateful for that. Yeah, the rock itself is billions of years old. And yeah, our little 25, 50 year old yeah, bands of yeah, we have to dose of humility is always in order, just crazy how much of the you can actually feel in the in the muscle and just a touch can do what a lot of yeah of opening and integrating and and just to be stuck in a that that neurophysiological loop of of of to trauma versus being able to see it from an observer and let it pass through. It's just wow. You spoke about indigenous briefly there. I just I want to maybe pass a little more time hearing from you what it's been like you said to people that you're learning from the lineage have again, you know, even more experience than they're learning from people again with even more experience. So it's this, you know, multi thousand years of lineage. What are indigenous people like you were initially mentioning at the beginning? What are they when you bring them into the the like you were gave us example at Burning Man and stuff? What are they saying about what's happening with Mother Earth and with the human race? I think the most important message is that what's happening outside is an expression of what's happening inside. And the reason that the earth is so much of a mess is that you know symbolically we have the sun energy and the moon energy and the sun energy represents us our external world and and how much we we project our energy outside of ourselves or when we're seeking or when we're taking action. And then the moon energy is about how much are we pausing and reflecting in words and asking our soul and connecting to our soul and tuning into our intuition and connecting to emotion and feeling our emotion. And there's a huge imbalance between the two. And so if we can't get back into balance that's where our earth is a huge problem and if in what I found is this connection between all of that for instance the use of oil is fire energy which is also connected with the sun to solar power. Plastics are connected to solar use of money on credit cards is the same thing so all of these behaviors all these things we're we're indebting ourselves and we're actually creating toxicity in our body the you know we look at all the plastic in the ocean we look at all of the toxins in the air all of these things our body is the exact same thing and we can't say just because we're richer or more privileged than anybody else that we can separate ourselves away even the people that that don't have the privilege to be able to buy an air purifier or take really good supplements or drink really clean water like that we are them like we all are receiving there's no way you can just say oh i'm over here i'm just going to take my rocket ship to mars and separate yourself from it there's there's no way because it's internal and it's just going to keep recreating itself until we solve the problem internally wow wow yeah it's this this mirror this uh this reflection of what we see that's uh some of the issues greatest issues of our time externally are yeah direct yeah of what's happening uh internally i think that's really profound and it actually ties us all the way to what you said at the beginning as well about how um through these thousand plus people that you've worked with that that there's a mirror that's happening as well there's like a lot of seeing what we see in ourselves and other people across the world some of the issues around the world are some of the issues within ourselves this has been a very interesting conversation and yeah and i'm really grateful that you're doing what you're doing and that yeah so psychedelicjourneys.com people can yes yeah okay such an honor you're amazing you're such an angel plenty more please plenty more to come soon yes yeah i want to i want to see if we can get quick question uh do you think we're in a simulation yes i think the word simulation has like the word itself doesn't it misses the word love and love is ultimately what this is about but imagine this you are consciousness just like i talk about these galactic logos that are like a different flavor of intelligence and love blended together in its own thing so imagine that there's just one intelligence and that one intelligence decides wow it would be really cool if i could water ski and eat food and have sex and take psychedelics and uh swim in the ocean and visit tropical islands and and drink coconuts and all these amazing things so it creates this world by splitting itself the big bang it splits itself into millions of pieces of itself and those pieces are all a mirror of the one and all of those as they split apart have an identity a piece and and that rainbow of intelligence comes together and it creates a server let's call it you know just just an overall server of light and that server goes through these different layers of galactic intelligence center suns and each one of those suns is a portal and eventually make it down to our planet where it creates these archetypal energies and that's basically what's playing out is we have these archetypal energies that basically are a encoding of a software system it's it all is a software system but the beauty of it is the software system isn't a form of slavery meaning that the machine is not in service to the program but ultimately love is the highest thing so once each part of that individual program recognizes that love is the secret then they get to operate within the game with complete sovereignty and they don't have to actually play by the rules of the game anymore although there are certain rules within the game that always remain consistent okay so the infinite consciousness breaks up into all of the the the pieces the play lands and then we remember that we are all part of that and then we get to play by the sovereign the sovereign game the sovereign game which is the game of love and it's so fun because we created this paradise planet which i've seen in the future it is it's a paradise even this one yeah it's so cool and then we get to just do all these awesome things and then when we get bored we can go be a galactic logos or we can go do something else and eventually you know the way it is is you know like i'll use the word god but god meaning something different than western religion but this is god's toy box and eventually all the toys will get packed away in exactly the order that they came in that's why all the energies are ascending and they'll all get packed together and then go back into source and it's all co-existing at the same time the toy box of god in this planet being one of the toys and yeah this illusion of separation from the one that we get to yeah and all the cool things that you get to experience all the quality that gets the experience here it gets packed in as we okay interesting yeah okay okay and then what do you think and so this so the break off of of the infinite consciousness into the from into the big bang you call that process simulations uh i don't call it simulations other people call it simulations okay okay okay you know i i have my own like the way i would describe it is very different than that but i but i think it is like a game it is like a simulation because there are um laws and you have to follow those laws and you know many talk about karma you know karma is a really important part of that law if you understand how karma works you will not suffer and that's where you can learn to have the freedom and learn to have the sovereignty and be the one having the fun in the game and be in here for the party yeah as in like not causing harm on to others and during the during your lifetime and that yeah and also your past karma you know what the ancestral karma as well so it's not just the karma it's karma that you've brought in as well as um not creating new karma for yourself yeah okay okay okay yes there's so much to unpack what do you think's the most beautiful thing in the world love of course yeah love the divine i mean the beautiful most beautiful thing is when we get to recognize the mystery of life when we get to realize that everything that we see no matter what it looks like is actually something else yeah it's all set yeah i've been the ultimate nature yeah of the reality okay uh that's it trisha holy cow thank you so much for coming on the show and teaching us thank you such an honor thank you medicines yeah and thank you to mother earth to this playground that we get to reside on i know it's such a cool experience being alive wow okay uh thank you everybody for tuning in we greatly appreciate it we'd love to hear your thoughts in the comments below on the episode let us know what you're thinking check out the link in the bio to psychedelicjourneys.com and Trisha's other links as well and also get more conversations rolling with our friends our family co-workers people online on social media about what we discussed in this episode and also check out the links below to consciousness hacking as well as the links below to simulation support the organizations the entrepreneurs the artists indigenous people around the world that you believe in and go and build the future everyone manifest your dreams into the world thank you so much for doing it we will see you soon that's fun good job love you


This 2020 Ford F-250 Crew Cab Short Box XL is stock number 12235Z. We're here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used heavy-duty truck headquarters. This 2020 Ford F-250 has the 6.2 liter V8 engine. It has been fully-safetyed and inspected by our service shop. It has a fresh oil and filter change. All the fluids have been checked and topped off. And this truck is 100% ready to go.  So if you have HD capabilities on your computer, tablet, smartphone, or television, turn them on right now. Because it is definitely your best way to check out the quality, condition, and options of the truck before seeing it in person. And if you like the video and want to subscribe to our YouTube channel, in the lower right-hand part of the screen is a subscribe button. Click that, and then click the bell notifications to get updates on the videos we do each and every day here at Summit Auto. So it comes with the painted alloy 18-inch rims, no scuffs or scrapes on there. And it does have the Continental Conta-Track LT27565R18 tires. These tires look like they have probably about 70 to 80% of the tread left, maybe even a little bit more. Frame and underbody is in excellent condition. Front fender is in really nice shape. I didn't see any dents or dings on there. Headlight lenses are nice and clear. And the front bumper and lower valance are in really nice condition too. It does come with the chrome-trimmed grille. The hood is in very nice shape as well. Didn't see any dents or dings on there. And the passenger side front fender looks really good as well. Passenger side rim, no major scuffs or scrapes. And this agate black has just a little bit of metallic finish to it. I always like showing these metallic paint schemes here. My camera will just focus for me. But you can see it does have the metal flake. For whatever reason it's just not focusing here. Alright, there we go. Now it'll focus. So you can see that metal flake right there. Really a cool color. As you take a look down this side of the truck, take note of how clean the body is, how reflective and mirror-like that paint is. We take these HD videos so if you are far away or even if you're close by and just cannot make the trip down but you're still interested in purchasing the vehicle, you can see the truck here, the truck, and have confidence in the vehicle that you're looking at before you even get here. So when you do get here, there's absolutely no surprises and you can make a smart and informed buying decision from the comfort of your own home or wherever you may be watching this video from. Very clean down this side. Didn't see a single dent or ding. This back rim is in excellent shape as well. Back tires have just as much tread as the front tires and the frame and underbody on this truck is an exceptionally clean condition. Looks really good underneath. Has factory painted step bars and those are in nice condition as well. Coming around to the back of the vehicle, rear bumper looks really good. Does have the full towing package which includes the rear receiver hitch, four pin and seven pin wiring. The tailgate is in excellent shape as well. I didn't see any dents or dings and there comes with a trifecta soft tonneau cover. This must have been a used tonneau cover because it does have just a little bit of wear on it. But still does the job. Bed is in pretty nice shape. Didn't see any major dents or dings back here. Just a little bit of light duty usage. As you come around to the driver's side just as clean as that passenger's side. No dents or dings on the box. And for full disclosure, this back room is in excellent shape as well. Down the rest of the side of the truck looks really good. Does come with the heated telescopic tow mirrors, directional signals on the side. They telescope out like so. They also fold in. Inside the XL package gives you the gray cloth interior. Does have driver's side lumbar, no rips or tears on the seats. They're in really nice condition. I was told to show these stickers. So feel free to pause those to make sure it's got all the options and information you're looking for. Weather tech floor mats throughout. Auto headlamps, tilt, telescopic steering wheel, power windows, power locks and power mirrors. We'll hop inside. Take a look at the instrument cluster. Check out the miles and the radio. You can see that this one has 12,888 miles on it. You get a compass and distance to empty display on there. Instrument cluster is very nice and clean. Does come with the multifunction steering wheel, cruise controls and information center controls on the left. No excessive wear or scuffs on that steering wheel. Bluetooth and audio controls on the right. And this one does have the six speed automatic transmission with the optional tap shift. Does have the AM FM radio on here. And that is just all it has. And down here are your climate controls.  Does have heated mirror button right there. You get a USB down here. And two 12 volt power points. Passing side floor mat and seat are in excellent condition. No rips or tears on there. Smells very clean inside this truck. I don't think it's ever been smoked in. And the headliner is in excellent condition as well. Does come with six auxiliary upfit switches right there. Map lights and we'll take a quick look at the back seats. And then we'll start it up and take a look under the hood.  No rips or tears back here. It does have the latch child safety system for any child car seats you may have. Those headrests are all removable for better visibility when nobody is sitting back here. Does have a weather tech floor mat back here. And a little storage bin underneath here. This isn't held down by anything. So if you didn't want that, that could come out pretty easy. Does have side current and airbags. And you get child safety locks on the back doors. Bottoms of the doors all look really good. And we'll start it up and take a look under the hood. Starts right up. No check engine lights or anything like that. And this one does have a backup camera which shows up right there. I would personally like to thank you for checking out the video today. Hopefully from this HD video you will have been able to tell just how clean this truck is all the way around. Inside and out. Under the hood we have the 6.2 liter V8 engine. Engine bay is very clean, runs very smooth. Once again this truck has been fully safe and inspected by our service shop. Has a fresh oil and filter change. All the fluids have been checked and topped off. And this one is 100% ready to go. There's your mission sticker. I would highly recommend this truck from a quality and condition standpoint. I didn't see a single ding on it. And to see more pictures of this truck or one of our other 450 new and used cars, trucks, SUVs, minivans, Wranglers. Half tons, three quarter tons, one tons you name it. We got to go to that website right there www.summitauto.com. Full pictures and descriptions of every single vehicle from two locations all at summitauto.com. And if you'd like to check out more HD videos you can go to youtube.com. www.summitauto.com. Remember to like, subscribe, and share on this video and all the videos that you see there. In fact in a second you'll see a link to subscribe to our YouTube channel. The upper left a link to more F-250 videos like this one. The upper right a link to this vehicle on our website. And the lower left a link to one of our latest YouTube videos in the lower right. Click those, check us out. And we're super excited to help you with this Ultra Clean 2024 to F-250 Crew Cab Short Box XL. With the STX appearance package in black agate. Thanks again for checking out the video.