Difference between revisions of "CNM Tech Board 2023-07-27"
(→Proxmox for VM project) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[CNM Tech Board 2023-07-27]] is the meeting of [[CNM Technology Board]] that occurred on | + | [[CNM Tech Board 2023-07-27]] is the meeting of [[CNM Technology Board]] that occurred on July 27th, 2023. The predecessor meeting is [[CNM Tech Board 2023-07-20]]; the successor meeting is [[CNM Tech Board 2023-08-03]]. |
==Proxmox cluster== | ==Proxmox cluster== | ||
| Line 20: | Line 20: | ||
==Proxmox for VM project== | ==Proxmox for VM project== | ||
| − | [[Ansible]]; | + | [[Ansible]]; 4 cores CPU, 32Gb RAM, 64Gb hard |
==Wiki== | ==Wiki== | ||
Latest revision as of 17:39, 10 August 2023
CNM Tech Board 2023-07-27 is the meeting of CNM Technology Board that occurred on July 27th, 2023. The predecessor meeting is CNM Tech Board 2023-07-20; the successor meeting is CNM Tech Board 2023-08-03.
Contents
Proxmox cluster
Old
current cluster using 3 IP for their communication channel. 1 ipv4 public for network cluster communication. 2. ipv6 for network cluster communication 3. ipv4 internal for storage network cluster.
meanwhile, your new server only have 1 ipv6 and ipv4 internal. that caused, we can't connect to current cluster. there are 2 options to joining new server to the cluster possible. first remake all cluster, or second, you subscribe public ipv4 for new server.
the advantage by only using ipv6 on cluster, you can saving budget. the drawback, not all users can access ipv6.
New
Cluster, instances, monitoring, backup, documentation (CNM Bureau Farm)
Proxmox for VM project
Ansible; 4 cores CPU, 32Gb RAM, 64Gb hard
Wiki
Old
I've watched the meeting and thanks to Nata for holding the line for me. ... I actually completed the setup before finding out that the PlugableAuth plugin version has some known issues with the new version of MediaWiki. There isn't anything else left which I'm withholding from the project. The connection and authentication by the LDAP server is successful on the backend, but the plugin needs some more work for it to be functional on the webpage. I can try to fix it, I don't know exactly how long it can take me. ... Yes that's right, so much for little or nothing. The reason for this is not that I don't know how to set it up, it's due to lack of maintenance from the plugin provider. ... So I find myself trying to fix and maintain a php code for which I wasn't hired for. ... It will be better to wait on the updated plugin than to waist money or effort on it and have no results. ... As I said earlier, the connection from wiki to ldap is successful, but the plugin is not processing rightly the credentials passed on the web interface.
