| *** mhen_ is now known as mhen | 01:57 | |
| *** bauzas1 is now known as bauzas | 05:27 | |
| profcorey | It's the top of the hour. Anyone interested in Project Cascade please feel free to join in this discussion. | 18:00 |
|---|---|---|
| profcorey | Project Cascade is not an official OpenStack. However, the goal is to present it to the TC at the next NA event for accepting as an official project. | 18:01 |
| profcorey | We have created a project charter to kickoff the project: https://github.com/profcorey/cascade/blob/main/README.md | 18:01 |
| profcorey | I'll allow time for anyone to review and make any comments if any... | 18:02 |
| profcorey | As you can see, the project charter follows the 4 opens per the foundation's reqs. | 18:03 |
| profcorey | Under Project Mission, line 5 there's a typo at the end, I'll fix that. | 18:05 |
| profcorey | We've adopted the Apache v2.0 license for licensing purposes. | 18:06 |
| profcorey | Until the project is official, we'll continue to develop the project's code on github in the same repo as the project charter | 18:08 |
| azlan | Thank you, Professor Corey. I’ve reviewed the project charter and it’s well-structured and aligns nicely with the 4 Opens principles. | 18:08 |
| profcorey | Thank you azlan! | 18:09 |
| azlan | But can you kindly elaborate what language will be used in the project | 18:09 |
| profcorey | We will create a high-level architectural diagram under Architecture next | 18:09 |
| profcorey | For language, we will use Python since most of the other OpenStack projects use Python as well | 18:10 |
| azlan | Would you say the MVP should only focus on Chat + PBX + basic UI, or should we try to include auditing and analytics early on too? | 18:11 |
| profcorey | Help me MVP? | 18:11 |
| profcorey | Auditing and analytics can be future features | 18:12 |
| azlan | Sorry! By MVP I meant “Minimum Viable Product” — like the first working version of Cascade. | 18:12 |
| profcorey | Ahh, gotcha! | 18:12 |
| profcorey | Absolutely, minimal services to get a first version up and runing | 18:13 |
| azlan | Are we focusing on just a few features for now, like chat and calling, or building everything together step by step? | 18:13 |
| profcorey | A goal would be a working version perhaps alpha version for presenting to the TC at the next OpenInfra Days NA event | 18:13 |
| profcorey | Just a few MVP features | 18:14 |
| azlan | Got it! So for the alpha, we’ll stick to the core — probably chat, basic PBX integration, and a simple UI. I’ll start organizing it in that direction. | 18:14 |
| profcorey | Agree, and the simple UI would FreePBX, I believe | 18:15 |
| profcorey | I'll need to research Open Source chat server/clients | 18:16 |
| azlan | Got it — so FreePBX will handle the PBX UI side, and we can focus on integrating chat and connecting everything behind the scenes. | 18:16 |
| profcorey | What did you think of Asterisk? | 18:16 |
| azlan | I think Asterisk is solid — powerful and flexible | 18:16 |
| profcorey | I'm sure there's a stable version we can work with to intergrate into our arch | 18:16 |
| profcorey | Cool! | 18:16 |
| azlan | since FreePBX is built on top of it, it makes sense to use it as the backend. We just need to make sure we understand how to interface with it properly, maybe through AMI or ARI? | 18:17 |
| profcorey | Agreed, AMI? ARI? | 18:17 |
| azlan | Yes, definitely — I’ll look into the latest stable Asterisk version that's reliable for integration and check its compatibility with FreePBX and our planned architecture(once finalized). | 18:18 |
| profcorey | The alpha version will be an All-in-1 deployment at first. I have extra machines in one of my labs at my campus that I can use | 18:18 |
| profcorey | Fantastic azlan! | 18:18 |
| profcorey | But we should also try deploying alpha version in a cloud, a CCaaS in a cloud deployment. | 18:19 |
| azlan | From what I’ve read, ARIis better if we want more control and plan to build our own logic for call handling. AMI is good for basic monitoring and issuing commands. | 18:19 |
| profcorey | Good researching! I haven't read the docs yet | 18:20 |
| profcorey | Good to know | 18:20 |
| azlan | Agreed — deploying the alpha as a cloud-based CCaaS setup would really help demonstrate the real-world use case. | 18:20 |
| azlan | I can start looking into how we could package and deploy it on an OpenStack cloud | 18:21 |
| profcorey | So, I'll add all of our "alpha" version to a doc in GitHub for public viewing | 18:21 |
| azlan | okay sure | 18:21 |
| profcorey | Fantastic! | 18:21 |
| profcorey | And I'll research different IM open source tools | 18:21 |
| profcorey | We can the take a look through those next meeting | 18:22 |
| profcorey | Speaking of next meeting, let's host these bi-weekly if that's ok | 18:22 |
| azlan | Yes sure I will be waiting. | 18:22 |
| profcorey | Anything else for our next meeting? | 18:23 |
| azlan | Sounds good! Bi-weekly works perfectly for me. | 18:23 |
| profcorey | Excellent! Same time same place in 2 weeks | 18:23 |
| profcorey | Alright anything else? | 18:24 |
| azlan | Nothing else from my side right now — unless you had anything else in mind that you'd like me to look into before our next meeting? | 18:24 |
| profcorey | I think the Asterisk research is plenty | 18:24 |
| profcorey | I'm going to copy this meeting's notes and publicly keep them in the github repo for anyone to view | 18:24 |
| profcorey | Ok, let's end here then | 18:25 |
| azlan | Got it! I’ll focus on Asterisk and come prepared with some integration details and a draft flow | 18:25 |
| profcorey | Thanks for attending and see you in 2 weeks! | 18:25 |
| profcorey | Fantastic! | 18:25 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!