search

ncsa / standalone-smm-analytics

dockerized version of analytics algorithms
Apache License 2.0
0 stars 0 forks source link

Find out the DNS connection issue in docker compose #72

Closed ywkim312 closed 9 months ago

ywkim312 commented 9 months ago

When using the docker-compose, the url using DNS name doesn't hit the correct container find out why this is happening.

ywkim312 commented 9 months ago

This is my original question

Hi I have a question about the ip address of the smm-tester.ncsa.illinois.edu. In radiant setting, it shows that the ip of the internal address is 192.168.100.237. However, when I tried to reach this in my docker-compose setting with traefik using smm-tester.ncsa.illinois.edu, it makes an error because it is trying to access 192.168.100.187.

When I do nslookup, both of them are pointing smm-tester like this

ywkim@smm-tester:/home/smm/deployment# nslookup 192.168.100.237 237.100.168.192.in-addr.arpa name = smm-tester. 237.100.168.192.in-addr.arpa name = smm-tester.local.

ywkim@smm-tester:/home/smm/deployment# nslookup 192.168.100.187 187.100.168.192.in-addr.arpa name = smm-tester.ncsa.illinois.edu. 187.100.168.192.in-addr.arpa name = smm-tester.

One is local, and the other is ncsa.illinois.edu. If I want to access to 237, then should I make the url as like https://urldefense.com/v3/__http://smm-tester.local__;!!DZ3fjg!_PzyZExcZfWhUxwm_J2byEMb612jtLVi3HIvZ2Tf9z37evRri6gTZp8-xWkexAkZ21OPae4h2-V0ZV7S8RBNCZUHZ6Qc$ instead of https://smm-tester.ncsa.illinois.edu?

ywkim312 commented 9 months ago

First answer

smm-tester.ncsa.illinois.edu has address 141.142.218.143. If your floating ip address that is assigned to this vm changed we can update the hostname in DNS to point to the new address.

143.218.142.141.in-addr.arpa domain name pointer smm-tester.ncsa.illinois.edu.

The 192.168.100.237 and 192.168.100.187 are internal radiant ip addresses and are only unique in the context of your openstack project. Other radiant users may have systems that share those local addresses.

This may not answer your question. Christopher Lindsey Can you offer any more specific guidance?

ywkim312 commented 9 months ago

My follow up question

I keep having an error because it is keep pointing to 192.168.100.187 when I did the smm-tester.ncsa.illinois.edu. Is there a way to change it to point to 192.168.100.237. I believe that if it points to 100.237 the error might go away

ywkim312 commented 9 months ago

They transferred my question to openstack

I'm going to transfer your request to the SVC queue for assistance with your OpenStack use questions.

ywkim312 commented 9 months ago

Answer from openstack

Hi Yong Wook Kim,

Sorry for all the bouncing around on this. I'm not sure I am following what you are attempting, but a couple of suggestions since this looks like basic naming/name resolution and nothing specifically related to Radiant:

If possible choose a different name for your public DNS host name Use ip addresses instead of host names Change your resolver to prefer the local system host name file (usually /etc/hosts) and override host names there Once you have disambiguated your interface names, you should be able to determine where connections are going. If you are still having connection issues then, please let us know.

ywkim312 commented 9 months ago

So we probably need to use ip address instead of DNS name....

https://jira.ncsa.illinois.edu/browse/RAD-310