Difference between revisions of "CNM Tech Board 2023-10-12"

From CNM Wiki
Jump to: navigation, search
(Kenya launch)
 
(8 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
=="Old" businesses==
 
=="Old" businesses==
 
===Bureau Farm (Proxmox cluster)===
 
===Bureau Farm (Proxmox cluster)===
* Updates: [[CNM Bureau Farm]], Jitsi/Odoo/HumHub, DNS, [[CNM pfSense]], monitoring -- [[Telegraf]] + [[InfluxDB]] + [[Grafana]], [[Uptime Kuma]], [[Passbolt]], mail server, LDAP, DNS zone, IPv4, what else to do? HA test, alpha testing
+
* Updates: [[CNM Bureau Farm]], Jitsi/Odoo/HumHub, DNS, [[Educaship pfSense]], monitoring -- [[Telegraf]] + [[InfluxDB]] + [[Grafana]], [[Uptime Kuma]], [[Passbolt]], mail server, LDAP, DNS zone, IPv4, what else to do? HA test, alpha testing
 
* Discussions:  
 
* Discussions:  
 
* Plans: Gary to work on DNS, make a plan for a meeting with Muhammed
 
* Plans: Gary to work on DNS, make a plan for a meeting with Muhammed
  
 
===WSO2 IS===
 
===WSO2 IS===
* Updates: Natalia to install [[WSO2 IS]] on the [[CNM Lab Farm]] and try to plug to [[Opplet]] and [[CNM WordPress]]
+
* Updates: Natalia to install [[WSO2 IS]] on the [[CNM Lab Farm]] and try to plug to [[Opplet]] and [[Educaship WordPress]]
 
* Discussions:  
 
* Discussions:  
 
* Plans: Gary to make A record
 
* Plans: Gary to make A record
 
===Recording===
 
* Updates: VM-based recording experiments. 4 cores CPU, 32Gb RAM, 64Gb hard. Natalia to create a kind of instruction, Natalia and Kevin to collaborate
 
* Discussions: Can we install [[OBS Studio]] to VM?
 
* Plans:
 
 
===Jitsi===
 
* Updates: Create an instance on the non-clustered Proxmox, Jitsi bandwidth
 
* Plans: Gary to reach out to previous applicants
 
* Discussions:
 
  
 
===Onboarding===
 
===Onboarding===
Line 32: Line 22:
  
 
===Kenya launch===
 
===Kenya launch===
 +
Gary:
 
Team, I cannot wait for our launch, probably, in January, and a dry run even earlier. Here are some things we need to try to do by that:
 
Team, I cannot wait for our launch, probably, in January, and a dry run even earlier. Here are some things we need to try to do by that:
* Access to our cloud. I see two options: (1) students use computers in the class that is connected to our network and (2) students use their smartphones, right?
+
* '''Access to our cloud'''. I see two options: (1) students use computers in the class that is connected to our network and (2) students use their smartphones, right?<ul><li>The computer class looks gorgeous. The first question is whether all the computers are linked in one network. The second question is whether there is a router (since the computers are not connected to the Internet, I assume that the answer is "no"). Now, hiring some company on the ground to put the computers in one network, add the router, and connect this router to one network sounds like a more-than-a-couple-of-thousand-US-dollars project. Plus, the owner of the classroom needs to approve all the wires. And if the students can access the class for only one hour a day, the whole project doesn't sound too great. Writing about classroom wires, I assume that the computers have no wireless cards/accesses as Natalia and myself guessed earlier. However, that may not be the case. Let's create a list of questions for Kevin to ask our school partners.</li><li>The students accessing our proxmox from their devices sounds more attractive to me if we can work out the cost of the Internet access. I wonder whether residents of the faith homes have reliable wifi there. Correct me, but I assume that few have laptops. Do all of the students have smartphones? Buying a number of devices is an option at least, but my budget is limited as you know.</li></ul>
The computer class looks gorgeous. The first question is whether all the computers are linked in one network. The second question is whether there is a router (since the computers are not connected to the Internet, I assume that the answer is "no"). Now, hiring some company on the ground to put the computers in one network, add the router, and connect this router to one network sounds like a more-than-a-couple-of-thousand-US-dollars project. Plus, the owner of the classroom needs to approve all the wires. And if the students can access the class for only one hour a day, the whole project doesn't sound too great.
+
* '''Preparing our Proxmox.''' If we choose the classroom option, we may need a VPN. If we add a wifi to the faith homes, we would also need a VPN; otherwise, we will not be able to control the traffic. Plus, our VMs are lagging at the moment according to Kevin. Nenad closed our contract yesterday. Finally, Muhammed is not responding too fast :) I will be reaching out to Joseph and, if he is not available, we will try to bring another expert, right?
The students accessing our proxmox from their devices sounds more attractive to me if we can work out the cost of the Internet access. I wonder whether residents of the faith homes have reliable wifi there. Correct me, but I assume that few have laptops. Do all of the students have smartphones? Buying a number of devices is an option at least, but my budget is limited as you know.
+
* '''New applications to test.''' MediaWiki is not designed for mobile. Natalia, may we try (a) Docuwiki, (b) XWiki, and (c) Wiki.js on different VMs? Plus, I really want to try Canvas LMS for the first course.
* Preparing our Proxmox. If we choose the classroom option, we may need a VPN. If we add a wifi to the faith homes, we would also need a VPN; otherwise, we will not be able to control the traffic. Plus, our VMs are lagging at the moment according to Kevin. Nenad closed our contract yesterday. Finally, Muhammed is not responding too fast :) I will be reaching out to Joseph and, if he is not available, we will try to bring another expert, right?
+
* '''Meetings add-on module.''' Meeting organizing will be the first part of students' practice. We cannot allow everyone to administer our meetup.com group. Unless you have better ideas, I plan to purchase this -- https://marketplace.humhub.com/module/meeting/description -- Alternative routes could be separate applications, Odoo modules. Roman and myself even started working on a customly-written add-on for Opplet.net, but the Humhub module sounds like the fastest route to me.
* New applications to test. MediaWiki is not designed for mobile. Natalia, may we try (a) Docuwiki, (b) XWiki, and (c) Wiki.js on different VMs? Plus, I really want to try Canvas LMS for the first course.
+
* '''Prioritizing the tech.''' We still need WSO2 and so on; however, let's prioritize the Proxmox, new app, and meetings' module tasks for now. I am glad that the recording challenge looks resolved :)
Meetings add-on module. Meeting organizing will be the first part of students' practice. We cannot allow everyone to administer our meetup.com group. Unless you have better ideas, I plan to purchase this -- https://marketplace.humhub.com/module/meeting/description -- Alternative routes could be separate applications, Odoo modules. Roman and myself even started working on a customly-written add-on for Opplet.net, but the Humhub module sounds like the fastest route to me.
+
* '''Alpha testing.''' Kevin is leading our efforts to bring some testers on the board - we will try to run the program before it is launched.
* Prioritizing the tech. We still need WSO2 and so on; however, let's prioritize the Proxmox, new app, and meetings' module tasks for now. I am glad that the recording challenge looks resolved :)
+
* '''Video sharing.''' The students will have more fun if they record videos and publish them. YouTube can an option, but we need to resolve legal issues for that. I see that CNM Tube is a safer choice. At any rate, we will need to discuss that.
* Alpha testing. Kevin is leading our efforts to bring some testers on the board - we will try to run the program before it is launched.
 
* What did I miss? What do you think? As soon as I have tickets to Shanghai, I will let you know the times/dates when I cannot be in touch :) Thanks a bunch! --Gary
 
 
 
Team, a couple of additional thoughts:
 
Writing about classroom wires, I assumed that the computers have no wireless cards/accesses as Natalia and myself guessed earlier. However, that may not be the case. Let's create a list of questions for Kevin to ask our school partners.
 
The students will have more fun if they record videos and publish them. YouTube can an option, but we need to resolve legal issues for that. I see that CNM Tube is a safer choice. At any rate, we will need to discuss that.
 
--Gary
 
  
 
==Businesses to watch==
 
==Businesses to watch==
Line 54: Line 38:
 
===Lab Farm (non-HA Proxmox)===
 
===Lab Farm (non-HA Proxmox)===
 
* [[CNM Lab Farm]] cleanup
 
* [[CNM Lab Farm]] cleanup
 +
 +
===Recording===
 +
* Updates: VM-based recording experiments. 4 cores CPU, 32Gb RAM, 64Gb hard. Natalia to create a kind of instruction, Natalia and Kevin to collaborate
 +
* Discussions: Can we install [[OBS Studio]] to VM?
 +
* Plans:
 +
 +
===Jitsi===
 +
* Updates: Create an instance on the non-clustered Proxmox, Jitsi bandwidth
 +
* Plans: Gary to reach out to previous applicants
 +
* Discussions:
  
 
=="New" businesses==
 
=="New" businesses==
Line 67: Line 61:
  
 
===Waiting backlog===
 
===Waiting backlog===
# PHP tasks such as [[CNM MediaWiki]] beyond [[CNM LDAP]]
+
# PHP tasks such as [[Educaship MediaWiki]] beyond [[Educaship LDAP]]
# [[CNM LDAP]], LDAP-C contractor
+
# [[Educaship LDAP]], LDAP-C contractor
 
# [[Cloudflare]]
 
# [[Cloudflare]]
  
 
[[Category:CNM Tech Board Meetings]]
 
[[Category:CNM Tech Board Meetings]]

Latest revision as of 19:49, 19 June 2024

CNM Tech Board 2023-10-12 is the meeting of CNM Technology Board‎ that occurred on October 12th, 2023. The predecessor meeting is CNM Tech Board 2023-10-05; the successor meeting is CNM Tech Board 2023-10-19.


"Old" businesses

Bureau Farm (Proxmox cluster)

WSO2 IS

Onboarding

  • Updates: Joseph, Natalia to check the CNM Lab project
  • Discussions: Are we ready to onboard? If no, what else do we need to do?
  • Plans:

Lab Farm (non-HA Proxmox)

  • Wiki.js, XWiki, docuwiki

Kenya launch

Gary: Team, I cannot wait for our launch, probably, in January, and a dry run even earlier. Here are some things we need to try to do by that:

  • Access to our cloud. I see two options: (1) students use computers in the class that is connected to our network and (2) students use their smartphones, right?
    • The computer class looks gorgeous. The first question is whether all the computers are linked in one network. The second question is whether there is a router (since the computers are not connected to the Internet, I assume that the answer is "no"). Now, hiring some company on the ground to put the computers in one network, add the router, and connect this router to one network sounds like a more-than-a-couple-of-thousand-US-dollars project. Plus, the owner of the classroom needs to approve all the wires. And if the students can access the class for only one hour a day, the whole project doesn't sound too great. Writing about classroom wires, I assume that the computers have no wireless cards/accesses as Natalia and myself guessed earlier. However, that may not be the case. Let's create a list of questions for Kevin to ask our school partners.
    • The students accessing our proxmox from their devices sounds more attractive to me if we can work out the cost of the Internet access. I wonder whether residents of the faith homes have reliable wifi there. Correct me, but I assume that few have laptops. Do all of the students have smartphones? Buying a number of devices is an option at least, but my budget is limited as you know.
  • Preparing our Proxmox. If we choose the classroom option, we may need a VPN. If we add a wifi to the faith homes, we would also need a VPN; otherwise, we will not be able to control the traffic. Plus, our VMs are lagging at the moment according to Kevin. Nenad closed our contract yesterday. Finally, Muhammed is not responding too fast :) I will be reaching out to Joseph and, if he is not available, we will try to bring another expert, right?
  • New applications to test. MediaWiki is not designed for mobile. Natalia, may we try (a) Docuwiki, (b) XWiki, and (c) Wiki.js on different VMs? Plus, I really want to try Canvas LMS for the first course.
  • Meetings add-on module. Meeting organizing will be the first part of students' practice. We cannot allow everyone to administer our meetup.com group. Unless you have better ideas, I plan to purchase this -- https://marketplace.humhub.com/module/meeting/description -- Alternative routes could be separate applications, Odoo modules. Roman and myself even started working on a customly-written add-on for Opplet.net, but the Humhub module sounds like the fastest route to me.
  • Prioritizing the tech. We still need WSO2 and so on; however, let's prioritize the Proxmox, new app, and meetings' module tasks for now. I am glad that the recording challenge looks resolved :)
  • Alpha testing. Kevin is leading our efforts to bring some testers on the board - we will try to run the program before it is launched.
  • Video sharing. The students will have more fun if they record videos and publish them. YouTube can an option, but we need to resolve legal issues for that. I see that CNM Tube is a safer choice. At any rate, we will need to discuss that.

Businesses to watch

Community

Lab Farm (non-HA Proxmox)

Recording

  • Updates: VM-based recording experiments. 4 cores CPU, 32Gb RAM, 64Gb hard. Natalia to create a kind of instruction, Natalia and Kevin to collaborate
  • Discussions: Can we install OBS Studio to VM?
  • Plans:

Jitsi

  • Updates: Create an instance on the non-clustered Proxmox, Jitsi bandwidth
  • Plans: Gary to reach out to previous applicants
  • Discussions:

"New" businesses

First-priority backlog

  1. Mail server: mail.opplet.net, mail.bskol.com, mail.cnmcyber.com,
  2. CNM Lab
  3. Possibly, get rid of DigitalOcean

Second-priority backlog

  1. CNM Tube, livestreaming
  2. CNM Lab Farm, non-cluster Proxmox; for VM project -- Ansible; time tracking
  3. CNM Campus Farm

Waiting backlog

  1. PHP tasks such as Educaship MediaWiki beyond Educaship LDAP
  2. Educaship LDAP, LDAP-C contractor
  3. Cloudflare