search

glos / myglos

Repository for MyGLOS (GLOS Data Portal)
GNU General Public License v3.0
2 stars 2 forks source link

Change private network IP addresses on portal.glos.us? #148

Open tslawecki opened 7 years ago

tslawecki commented 7 years ago

I'm looking to set up munin for tracking disk and CU usage on this VM, and noted that it's currently listing 172.18.0.1 and 172.17.0.1 as private IPs in ifconfig. I'm not sure who set this up - I'm guessing Luke - can these be safely changed to 192.168.76.tbd to put them in the same subdomain as the Munin server, or is there something in Docker or the portals dependent on these IPs?

tslawecki commented 7 years ago

Adding @benfish - guessing that's Ben Adams - in case he has any insight into the private IPs ...

cheryldmorse commented 7 years ago

Adding @benjwadams

benjwadams commented 7 years ago

@tslawecki, Docker's stock configuration creates a bridge network over which containers can communicate with each other. See https://docs.docker.com/engine/userguide/networking . If you're looking for overall disk/CPU usage you can safely ignore the 172.* IP addresses and use the host IP.

tslawecki commented 7 years ago

@benjwadams - My munin host is only available through the 192. private network. Do you see any issues arising from adding the requisite 192. addresses to the portal.glos.us ipconfig? As I understand it, munin-node has to be configured to allow access from the munin server which has a 192.* address.

benjwadams commented 7 years ago

Appears to be an issue with Munin master being able to reach portal.glos.us due to the two servers residing on different subnets.

kknee commented 6 years ago

@benjwadams @tslawecki what's the conclusion here?