perfSONAR User Q&A and Other Discussion

[<>]

Greetings,

Jun 4, 2018, 11:05 AM by 
:

> [snip]
>
>>
>> On 6/2/18, 5:36 PM, ">> 
>> 
>>  
>> <mailto:>>>
>>   on behalf of >> 
>> 
>>  
>> <mailto:>>>
>>  " <>> 
>> 
>>  
>> <mailto:>>>
>>   on behalf of >> 
>> 
>>  
>> <mailto:>>>
>>  > wrote:>>  
>>
>> [snip]
>> (root) $ cd /usr/lib/esmond>>  
>> (root) $ . bin/activate>>  
>> (esmond) (root) $ python esmond/manage.py add_user_ip_address <My user on 
>> the node> <IP of the node>>>  
>> Traceback (most recent call last): File "esmond/manage.py", line 6, in 
>> <module>>>  
>> import settings # Assumed to be in the same directory.>>  
>> File "/usr/lib/esmond/esmond/settings.py", line 16, in <module>>>  
>> raise Error("ESMOND_ROOT not defined in environment")>>  
>> NameError: name 'Error' is not defined>>  
>>
>>
>> Err. Uh oh.>>  
>> I've been poking away for 45 minutes trying to get passed this point.>>  
>>
>> 1. Any idea what I'm doing wrong?>>  
>>
>
> Did you log out after running the “yum install perfsonar-centralmanagement” 
> and then log back-in before you ran the commands for adding the user? It is 
> complaining that the environment variable ESMOND_ROOT is not set which gets 
> set by a script in /etc/profile.d at login. 
>
>
I did log out and back in. In fact, I even did a full power off. 

Looking in /etc/profile.d, there is nothing there that isn't a part of the 
default install. So maybe something else went wrong? Or maybe I missed a step?


>>
>> 2. Am I just doing the wrong thing here for wanting to just view the node 
>> tests?>>  
>>
>
> If you just have one node and it’s not a toolkit, there is nothing 
> technically wrong with the path you are taking. Generally if you saw just 
> one box as your long-term deployment size and you want to be able to store 
> results, I’d maybe recommend merging the central server and the testpoint 
> into one box capable of being a toolkit since it would simplify things. If 
> you plan on adding more nodes though, the setup you have is a great way to 
> get things started to familiarize yourself with the tools. As far as you 
> mesh file goes, just make sure all the hosts that are NOT your measurement 
> host have “no_agent” set. That indicates that the host in question is not 
> looking at the mesh, so its counting on your measurement node to setup the 
> test. 
>
>

Well, for my little home test setup it will probably remain a single node and 
I don't have too many other uses for this little guy anyway. :-) But I like 
the possibilities of where this can go for my work purposes so I will 
eventually want to set up multiple nodes.

Thanks for the pointer when I set up the mesh file.


>>
>> 3. The way my network traffic flows is that the CMA host can initiate 
>> traffic to the DMZ host, but not the other way. Do I need to poke holes in 
>> my firewall to allow the DMZ node to communicate back to the VM or can it 
>> just be a "pull only" scenario?>>  
>>
>
> If you want results for traffic from the DMZ to the CMA then it is probably 
> easiest to poke holes if you can. In particular OWAMP data packets are UDP 
> from source to dest so no tricks you can do with who initiates the TCP 
> handshake to get that working. I assume its just a firewall, not a 
> firewall+NAT? If there is a NAT things get more difficult. 
>
>
Hrm. That is going to get tricky at my work. They do all sorts of crazy 
things in the name of security (whether it is actually secure or not is 
something left to someone else but I'm not so convinced :-). 

It looks like the results are all stored in a json file. Maybe I can slurp 
those from the end points into something else...but that craziness will have 
to wait until I at least get the basics functioning. :-)

In the meantime, I've got a spare box. I can do a build on it to be the CMA 
and toss it out on the same network in the DMZ. It isn't that great of a box, 
but it should do for a test. It won't be tonight, but I may have some time 
tomorrow to do this build and test. I will reinstall the CMA and see if I end 
up with issues there.
Thanks for the feedback!
~Stack~