# OpenSearch Community Meeting - 2023-0117 **URL:** \ **Category:** Community\ **Tags:** community-meeting\ **Created:** [December 20, 2022, 7:28pm UTC](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0117/11891 "2022-12-20T19:28:47Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![kris](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/kris/32/2208_2.png) [@kris](https://forum.opensearch.org/u/kris)\ **Post date:** [December 20, 2022, 7:28pm UTC](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0117/11891/1 "2022-12-20T19:28:47Z")
[OpenSearch Community Meeting - 2023-0117](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0117/11891) - Hope we see you all there! Agenda: - Demo of migration tool (so far) - Chris Helma, Sr Engineer - OpenSearch (migration team) - Identity feature - intro, discussion, & feedback request - @peternied SDE - OpenSearch security - Sample plugin - [test API to describe the available analyzers, tokenizers, and filters](https://github.com/opensearch-project/OpenSearch/issues/5481) - @lukas-vlcek - Code Contributor Coins - reminder to reach out if you didn’t receive an email from us in Dec 2022. [Event page](https://opensearch.org/events/2023-0117/) [Meetup page](https://www.meetup.com/opensearch/events/290443462/) [Meeting Link](https://us02web.zoom.us/j/86340828076) Meeting ID: 863 4082 8076 Passcode: 952752 Would you like to present? Tag @kris @dtaivpp @nateynate and we’ll work to get you added to the agenda! Feel free to comment on this agenda before the meeting if you want to add an item or have a question. After the meeting, we will post the chat log and any meeting notes. We welcome you to keep the conversation going here on the forum. ======== _By joining the OpenSearch Community Meeting, you grant OpenSearch, and our affiliates the right to record, film, photograph, and capture your voice and image during the OpenSearch Community Meeting (the “Recordings”). You grant to us an irrevocable, nonexclusive, perpetual, worldwide, royalty-free right and license to use, reproduce, modify, distribute, and translate, for any purpose, all or any part of the Recordings and Your Materials. For example, we may distribute Recordings or snippets of Recordings via our social media outlets._ ---
**Author:** ![peternied](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/peternied/32/3515_2.png) [@peternied](https://forum.opensearch.org/u/peternied)\ **Post date:** [January 5, 2023, 10:12pm UTC](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0117/11891/2 "2023-01-05T22:12:22Z")
@kris @dtaivpp @nateynate Is there space for ~15 minutes to introduce and discuss the Identity feature during the meeting on the 17th? We will have a blog post, GitHub meta issue and project plan along side to share as well as get feedback on, would love to spend a couple minutes introducing the high level vision and then take questions. ---
**Author:** ![dtaivpp](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/dtaivpp/32/2814_2.png) [@dtaivpp](https://forum.opensearch.org/u/dtaivpp)\ **Post date:** [January 5, 2023, 10:14pm UTC](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0117/11891/3 "2023-01-05T22:14:16Z")
Sure is @peternied ! Looking forward to having you 😃 ---
**Author:** ![kris](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/kris/32/2208_2.png) [@kris](https://forum.opensearch.org/u/kris)\ **Post date:** [January 5, 2023, 11:09pm UTC](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0117/11891/4 "2023-01-05T23:09:48Z")
Absolutely! Will add you to the agenda - thanks! ---
**Author:** ![dtaivpp](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/dtaivpp/32/2814_2.png) [@dtaivpp](https://forum.opensearch.org/u/dtaivpp)\ **Post date:** [January 7, 2023, 6:06pm UTC](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0117/11891/5 "2023-01-07T18:06:55Z")
@kris lets also add this one by Lukáš. Should be relatively short. It’s a sample plugin that is a test for an API to describe the available analyzers, tokenizers, and filters. > > > \*\*Is your feature request related to a problem? Please describe.\*\* > > I am missi…ng an option to get list of all available analyzers. > There is already analyze API documentation and it mentions "built-in" analyzers. But for normal user there is no way how to learn what are all the options. And even for people who are familiar with the code the list is a subject to updates/changes. > One option would be to document the list in the documentation page. But I think I would prefer if the cluster itself can give a list of its analyzers (and also tokenizers, charfilters, normalizers). > > \- There are built-in analyzers at the cluster level (in fact the list is kept at the node level, see below) > \- There are also ad-hoc/custom analyzers at individual index level (but visibility of these should be subject of RBA rules?) > > \*\*Describe the solution you'd like\*\* > > As far as I understand list of all built-in analyzers is materialized once \`AnalysisModule.setupAnalyzers(plugins)\` is called. > I think it would be useful to extend one of the \`\_nodes/\` APIs and give it option to return list of all built-in analyzers (and its componenets: tokenizers, ... etc). (It needs to be API at the "nodes"-level because AnalysisRegistry is kept per node and I think a list of built-in analyzers can differ on each node depending on installed plugins.) > > As for the list of analyzers defined at the index level I am not sure at this point. Maybe later... > > \*\*Describe alternatives you've considered\*\* > > Alternative is to go to the documentation (which does not have this list) or go to the code (which is not an option for many people). > > \*\*Additional context\*\* > n/a ---
**Author:** ![kris](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/kris/32/2208_2.png) [@kris](https://forum.opensearch.org/u/kris)\ **Post date:** [January 9, 2023, 7:43pm UTC](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0117/11891/6 "2023-01-09T19:43:32Z")
Excellent - thanks @dtaivpp! @lukas-vlcek - we’ll be looking forward to it! ---
**Author:** ![kris](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/kris/32/2208_2.png) [@kris](https://forum.opensearch.org/u/kris)\ **Post date:** [January 17, 2023, 6:23pm UTC](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0117/11891/7 "2023-01-17T18:23:35Z")
Thank you to all who attended! Chat log: 07:49:58 From David Tippett to Everyone: - Chris - [GitHub - opensearch-project/opensearch-migrations: All things migrations and upgrades for OpenSearch](https://github.com/opensearch-project/opensearch-migrations) - Peter - [[META] Identity in OpenSearch · Issue #5834 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/issues/5834) - Lukáš - [Get list of all available analyzers. Request for a new API? · Issue #5481 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/issues/5481) 07:52:03 From Peter Nied to Everyone: David could you replace my link with [[Security] OpenSearch should support authentication and authorization natively · Issue #4514 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/issues/4514) 07:52:06 From Chris Helma to Everyone: Tracking Issue - [[META] Upgrade Testing Framework Issue List · Issue #10 · opensearch-project/opensearch-migrations · GitHub](https://github.com/opensearch-project/opensearch-migrations/issues/10) ``` Tool README - https://github.com/opensearch-project/opensearch-migrations/blob/main/upgrades/README.md ``` 07:56:38 From Kris Freedain to Waiting Room Participants: Hello Everyone - we’ll get going in just a few minutes 07:56:57 From Nate Boot to Everyone: Ohboyohboyohboy! 08:01:26 From Romain to Everyone: o/ 08:01:39 From Peter Nied to Everyone: Cleaned the house, nearly spring cleaning! 08:01:55 From George Bridgeman to Everyone: Laser tag for my kid’s birthday. I had more fun than the children! 08:02:12 From Kris Freedain to Everyone: Worked in the garden a little 08:02:37 From Nate Boot to Everyone: Introduce yourself! 08:02:46 From Nate Boot to Everyone: 😂 08:03:42 From David Tippett to Everyone: [[RFC] Search pipelines · Issue #80 · opensearch-project/search-processor · GitHub](https://github.com/opensearch-project/search-processor/issues/80) 08:04:14 From David Tippett to Everyone: [[RFC] Search pipelines · Issue #80 · opensearch-project/search-processor · GitHub](https://github.com/opensearch-project/search-processor/issues/80) 08:04:18 From Peter Nied to Everyone: Or why you aren’t using the SQL Plugin! 08:04:34 From David Tippett to Everyone: SQL [A community call: share your mappings](https://forum.opensearch.org/t/a-community-call-share-your-mappings/12027) 08:04:58 From David Tippett to Everyone: [Finding the Right Things with OpenSearch, Tue, Jan 24, 2023, 7:00 PM | Meetup](https://www.meetup.com/dataops-poland/events/290421010/) 08:05:17 From Daniel Doubrovkine to Everyone: + we’ve published some info on security reviews that we conduct before releasing software: [.github/RELEASING.md at main · opensearch-project/.github · GitHub](https://github.com/opensearch-project/.github/blob/main/RELEASING.md#security-reviews) 08:05:58 From Nate Boot to Everyone: Welcome Chris! 08:06:29 From David Tippett to Everyone: Reacted to “+ we’ve published so…” with ❤ 08:06:31 From David Tippett to Everyone: Reacted to “+ we’ve published so…” with 🎉 08:08:09 From Fernando Rejon Barrera to Everyone: maybe it’s just me but I can’t see any slides (if there are any) 08:08:21 From David Tippett to Everyone: Here is the tracking issue for OpenSearch Migrations - [[META] Upgrade Testing Framework Issue List · Issue #10 · opensearch-project/opensearch-migrations · GitHub](https://github.com/opensearch-project/opensearch-migrations/issues/10) 08:09:06 From Fernando Rejon Barrera to Everyone: never mind, I can see the screen now :+1 08:09:35 From Kris Freedain to Everyone: Replying to “never mind, I can se…” ``` Chris was just doing an intro before - hadn’t shared his screen yet. ``` 08:12:44 From Kris Freedain to Everyone: Reacted to “+ we’ve published so…” with 🎉 08:13:48 From Amitai Stern to Everyone: Wow! 08:14:50 From David Tippett to Everyone: Here is the readme for the tool: [opensearch-migrations/README.md at main · opensearch-project/opensearch-migrations · GitHub](https://github.com/opensearch-project/opensearch-migrations/blob/main/upgrades/README.md) 08:15:00 From Kris Freedain to Everyone: Reacted to “Here is the readme f…” with 👍🏻 08:18:04 From Mark Cohen to Everyone: Reacted to “[o (Osman) · GitHub](https://github.com/o)…” with 👍 08:18:28 From David Tippett to Everyone: Here is the tracking issue for OpenSearch Migrations - [[META] Upgrade Testing Framework Issue List · Issue #10 · opensearch-project/opensearch-migrations · GitHub](https://github.com/opensearch-project/opensearch-migrations/issues/10) 08:22:38 From Charlotte to Everyone: Oh just rub it in for those of us drowning in rain, Peter 😉 08:22:49 From David Tippett to Everyone: Reacted to “Oh just rub it in fo…” with 😛 08:22:54 From Nate Boot to Everyone: I bet those blue clouds are really confusing. 08:23:03 From Kris Freedain to Everyone: [[Security] OpenSearch should support authentication and authorization natively · Issue #4514 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/issues/4514) 08:23:30 From Kris Freedain to Everyone: Peter is looking for feedback on that one 08:28:39 From Kris Freedain to Everyone: Good blog post on plugins: [Introduction to OpenSearch Plugins · OpenSearch](https://opensearch.org/blog/plugins-intro/) 08:34:02 From Sam Herman to Everyone: Thanks for the clarification DB! 08:34:25 From Daniel Doubrovkine to Everyone: JSM = [[RFC] Replace Java Security Manager (JSM) · Issue #1687 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/issues/1687) 08:34:44 From David Tippett to Everyone: hahaha 08:34:45 From Daniel Doubrovkine to Everyone: Office office office office … 08:36:24 From Sander to Everyone: We have a layer in front of the security plugin as well, to do ip filtering. We know which backend roles come from which ip’s, but opensearch doesn’t provide this so we put a Yarp (.net) proxy in front of opensearch. Would be nice if we had this out of the box and could remove the reverse proxy 08:42:42 From Stephen Crawford to Everyone: Replying to “We have a layer in f…” ``` Hi Sander, it sounds like you are looking for a way to be able to natively determine the IP origin for different backend roles? Is that right? If you have not made an issue on the security repo about it then I would encourage that here: https://github.com/opensearch-project/security/issues ``` 08:42:46 From David Tippett to Everyone: [[Security] OpenSearch should support authentication and authorization natively · Issue #4514 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/issues/4514) 08:42:47 From Dave Lago (OpenSearch) to Everyone: Thanks Peter!! 08:43:06 From Nate Boot to Everyone: Thanks Peter. Enjoy your sunshine. 😉 08:44:37 From Sander to Everyone: Replying to “We have a layer in…” ``` Thanks, created it in the past https://github.com/opensearch-project/security/issues/987 Just remembered because of your hint ``` 08:44:53 From Stephen Crawford to Everyone: Replying to “We have a layer in f…” ``` Great, I will take a look at that for you. ``` 08:45:43 From Sander to Everyone: Replying to “We have a layer in…” ``` Thanks Stephen! ``` 08:46:33 From Sander to Everyone: Replying to “We have a layer in…” ``` If you need more details, no problem, can provide them in the issue or with a call. ``` 08:47:50 From Stephen Crawford to Everyone: Replying to “We have a layer in f…” ``` Sounds great. I will take a look at what is on the issue already and follow up on the issue with any immediate questions. I can also join a call at your convenience if there ends up being a lot to discuss for the issue. I will keep you updated as things progress 🙂 ``` 08:49:19 From Sander to Everyone: Replying to “We have a layer in…” ``` Cool thanks, really appreciate the interactivity that you guys provide. ``` 08:52:45 From Stephen Crawford to Everyone: Reacted to “Cool thanks, really …” with 👍 08:54:44 From David Tippett to Everyone: Here is where you can find the meta issue for the Analyzers API. [Get list of all available analyzers. Request for a new API? · Issue #5481 · opensearch-project/OpenSearch · GitHub](https://github.com/opensearch-project/OpenSearch/issues/5481) 08:57:50 From Fernando Rejon Barrera to Everyone: Is it possible to organize/host local community events? If so, who should I contact regarding this? We would like to organize something in Amsterdam. 08:58:31 From Chris Helma to Everyone: Oh, physical coins. I was thinking crypto! 😅 08:58:32 From Sander to Everyone: `great to see that the community is growing, keep it up 🙂 08:58:52 From Sander to Everyone: @fernando, would be interested as well, working at the University of Wageningen 08:59:38 From Fernando Rejon Barrera to Everyone: thanks 09:00:05 From Nate Boot to Everyone: 🥳 09:00:12 From Peter Nied to Everyone: Great meeting, thanks for the vibrant discussion! 09:02:18 From Nate Boot to Everyone: I know sometimes people have asked “What is the actual tokenizer string you type in for your index mapping to use it?” - I: can see how a bit of extra reflection mightg make this information self-discoverable. 09:03:59 From Kris Freedain to Everyone: Reminder - the Security team holds their triage meetings publicly = next one is happening today: [Development Backlog & Triage Meeting - Security - 2023-01-17 · OpenSearch](https://opensearch.org/events/2023-0116-dev-triage-security/) 09:04:20 From Stephen Crawford to Everyone: Reacted to “Reminder - the Secur…” with 👀 09:04:47 From Sam Herman to Everyone: Thank you all, have to drop. 09:04:52 From Nate Boot to Everyone: Thanks for coming Sam! 09:05:01 From David Tippett to Everyone: Thanks Sam! 09:07:03 From Fernando Rejon Barrera to Everyone: thanks all 09:07:22 From Lukáš Vlček (@Aiven.io) to Everyone: LOL, thanks! 09:07:25 From eliatra Excelerate Technology Ltd. to Everyone: Thanks! 09:07:28 From Arnav Das to Everyone: Thanks ---
**Author:** ![kris](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/kris/32/2208_2.png) [@kris](https://forum.opensearch.org/u/kris)\ **Post date:** [January 17, 2023, 6:25pm UTC](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0117/11891/8 "2023-01-17T18:25:31Z")
![Slide1](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/2/2768367e254022289043e6201387d783efbbfe45.png) ![Slide2](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/0/0bf87feb9f8ee20dbf0b1abac27b3f025172fa4c.png) ![Slide4](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/a/ac2989801add6e9d93e764306506081f2ba09370.png) ![Slide5](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/b/bedd81653f23023afdf09f6069586da893a7ea31.png) > > > Meta issue to track the work associated with the Upgrade Testing Framework. > > F…ramework Workstream > \- \[x\] https://github.com/opensearch-project/opensearch-migrations/issues/1 > \- \[x\] https://github.com/opensearch-project/opensearch-migrations/issues/4 > \- \[x\] https://github.com/opensearch-project/opensearch-migrations/issues/6 > \- \[x\] https://github.com/opensearch-project/opensearch-migrations/issues/8 > \- \[x\] https://github.com/opensearch-project/opensearch-migrations/issues/7 > \- \[x\] https://github.com/opensearch-project/opensearch-migrations/issues/50 > \- \[\] https://github.com/opensearch-project/opensearch-migrations/issues/51 > \- \[\] https://github.com/opensearch-project/opensearch-migrations/issues/65 > > Expectations Workstream > \- \[\] https://github.com/opensearch-project/opensearch-migrations/issues/2 > \- \[\] https://github.com/opensearch-project/opensearch-migrations/issues/3 > \- \[\] https://github.com/opensearch-project/opensearch-migrations/issues/5 > > Miscellaneous > \- \[x\] https://github.com/opensearch-project/opensearch-migrations/issues/14 > \- \[x\] https://github.com/opensearch-project/opensearch-migrations/issues/48 > \- \[x\] https://github.com/opensearch-project/opensearch-migrations/issues/49 > > > > \*\*Is your feature request related to a problem? Please describe.\*\* > Plugins have… some permissions boundaries established by the java security manager, but those only enforce a subset of actions that a plugin can do. Public interfaces within the OpenSearch core systems are accessible by plugins without any access control systems. > > Knowing which systems have security considerations or not is non-trivial during plugin development, and represents a maintenance problems, if new granularity is added over time and plugins don't update to support these gaps in functionality are security bugs. > > \*\*Describe the solution you'd like\*\* > Support authentication and authorization within OpenSearch access control systems. Use that system to apply universally on all OpenSearch components, plugins, and the new up and coming extensions. > > \*\*Describe alternatives you've considered\*\* > The Security plugin is available, and it offers solutions for several features that align with this overall goal. Individual components might be worthwhile adopting, as the security system was built independently of OpenSearch the enforcement processes and ability to restrict access are optional by nature. > > \*\*Additional context\*\* > I think some of the to move towards this ultimate state looks like, > \- \[\] OpenSearch should be able to track a Subject through its system > \- \[\] OpenSearch should disable or enable support for authentication and authorization via config > \- \[\] OpenSearch internal process have different subjects for different actions > \- \[\] OpenSearch should have a user registry describable via config > \- \[\] OpenSearch users should be able to authenticate with 'Basic' HTTP Authentication > \- \[\] OpenSearch requests should know the Subject of the caller > \- \[\] OpenSearch should have a way to describe the permissions available to > > > \#### Terminology > \_From definition following NIST glossary. https://csrc.nist.gov/glossary\_ > \- Subject - An individual, process, or device that causes information to flow among objects or change to the system state. > \- Authentication- Verifying the identity of a user, process, or device, often as a prerequisite to allowing access to resources in a system. > \- Authorization - The process of verifying that a requested action or service is approved for a specific entity. ![Introduction to Node Analyzers_Page_1](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/a/a9a9bb01d76080737ed83543404195bdcfc1c996.jpeg) ![Introduction to Node Analyzers_Page_2](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/b/bf283209eec09d7f0081df526aa66e6e534753b0.jpeg) ![Introduction to Node Analyzers_Page_3](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/6/6ade79fb45307aa357f650fffac4df597fb7931a.png) ![Introduction to Node Analyzers_Page_4](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/c/c41d6b50565fe65c08cf8d74da73e4a87e88fd3f.png) ![Introduction to Node Analyzers_Page_5](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/d/d8a9a0a4f8fe106104cffb6f18f955a3cdfb9be6.png) ![Introduction to Node Analyzers_Page_6](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/8/81219e84d8061f02a42b16023a476c9267c1fafd.png) ![Introduction to Node Analyzers_Page_7](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/8/8d69d93d8e7693a900e88a958254ed5c03d72b4d.png) ![Introduction to Node Analyzers_Page_8](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/b/bf93cf10b7c36fe624ad54f5bf360b1d6b317614.png) > > > \*\*Is your feature request related to a problem? Please describe.\*\* > > I am missi…ng an option to get list of all available analyzers. > There is already analyze API documentation and it mentions "built-in" analyzers. But for normal user there is no way how to learn what are all the options. And even for people who are familiar with the code the list is a subject to updates/changes. > One option would be to document the list in the documentation page. But I think I would prefer if the cluster itself can give a list of its analyzers (and also tokenizers, charfilters, normalizers). > > \- There are built-in analyzers at the cluster level (in fact the list is kept at the node level, see below) > \- There are also ad-hoc/custom analyzers at individual index level (but visibility of these should be subject of RBA rules?) > > \*\*Describe the solution you'd like\*\* > > As far as I understand list of all built-in analyzers is materialized once \`AnalysisModule.setupAnalyzers(plugins)\` is called. > I think it would be useful to extend one of the \`\_nodes/\` APIs and give it option to return list of all built-in analyzers (and its componenets: tokenizers, ... etc). (It needs to be API at the "nodes"-level because AnalysisRegistry is kept per node and I think a list of built-in analyzers can differ on each node depending on installed plugins.) > > As for the list of analyzers defined at the index level I am not sure at this point. Maybe later... > > \*\*Describe alternatives you've considered\*\* > > Alternative is to go to the documentation (which does not have this list) or go to the code (which is not an option for many people). > > \*\*Additional context\*\* > n/a > **[GitHub - lukas-vlcek/OpenSearch-list-built-in-analyzers: Experimental...](https://github.com/lukas-vlcek/OpenSearch-list-built-in-analyzers)** > > Experimental OpenSearch plugin to list all available Analyzers - GitHub - lukas-vlcek/OpenSearch-list-built-in-analyzers: Experimental OpenSearch plugin to list all available Analyzers ![Introduction to Node Analyzers_Page_9](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/1/1dd00393b9b27877e24fa46b9e8c6ada3975c429.png) ![Slide6](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/a/a0d878731e43e54925c170633dfd8fd1c1d641f4.png) ![Slide7](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/9/98880b5574c6d338981efa0e1989fdaaf86fbf58.png) ![Slide8](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/e/e45d92da4b0a70c3490005e9741aef4eaf4fc8eb.png) ![Slide10](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/7/7e70a1aff4565bafdb883ef637925eedcc9a211a.png)