I am currently working on bringing Meteopbridge and Meteoplug onto one unified HW with the various cloud services as VMs in a PROXMOX environment. This is to overcome dependency of currently used dedicated hardware and to allow easy migration to new standard infrastructure. Consolidation into different VMs on one root server is something that will eat up much of my time in coming weeks and although I try my best to have no interruption of Meteobridge/Meteoplug services, there will be a hick-up here and there for sure. Please tell me, if you find an issue and please understand that these changes are needed to have a fluent service the years to come.
Yesterday we isolated the remote tunnel service into a separated virtual machine as a first step. As far as I can see this worked rather flawless. We are talking about over 3000 remote connections that made the change and they are all up and running fine - as far as I can see.
As a result of isolating the remote login services into a specialized VM I had to sort out proper use of server links. "admin.meteobridge.com" now points to the remote tunnel server only. That way the remote access links "https://admin.meteobridge.com/........./" work as before. But when you want to access the cam images you have to use "https://content.meteobridge.com/..." instead of "https:/admin.meteobridge.com/...". The links will be set correctly in the newest Meteobridge versions. If you have an older Meteobridge version, please just change the "admin" to "content" in the URL. "admin" points to the remote login server, "content" points to the regular Meteobridge server, where cam pictures, last min/avg/max data is stored and where the application packages during start-up of Meteobridge are provided.
Yesterday we isolated the remote tunnel service into a separated virtual machine as a first step. As far as I can see this worked rather flawless. We are talking about over 3000 remote connections that made the change and they are all up and running fine - as far as I can see.
As a result of isolating the remote login services into a specialized VM I had to sort out proper use of server links. "admin.meteobridge.com" now points to the remote tunnel server only. That way the remote access links "https://admin.meteobridge.com/........./" work as before. But when you want to access the cam images you have to use "https://content.meteobridge.com/..." instead of "https:/admin.meteobridge.com/...". The links will be set correctly in the newest Meteobridge versions. If you have an older Meteobridge version, please just change the "admin" to "content" in the URL. "admin" points to the remote login server, "content" points to the regular Meteobridge server, where cam pictures, last min/avg/max data is stored and where the application packages during start-up of Meteobridge are provided.
Statistics: Posted by admin — Sat Nov 09, 2024 10:37 am