[auton-users] Autonlab machine spec page

[predragp at andrew.cmu.edu]

> Hi Dr. P^2,
>
> This is the page I was referring to:
> http://www.autonlab.org/auton_intranet/computing/specs.html
> Also, I noticed that the shared installation of matlab on our servers is
> still R2013a and has licensing issues.
>
> Thanks,
> TK
>


Dear Autonians,

Per TK request I updated little bit Auton Intranet computing
infrastructure documentation.
As of today the following information is up to date.

1. Network topology (updated today again)

http://www.autonlab.org/auton_intranet/computing/22083.html

2. Machine specifications

http://www.autonlab.org/auton_intranet/computing/22086.html

3. OS Info

http://www.autonlab.org/auton_intranet/computing/compute_os.html

4. Scientific software Info

http://www.autonlab.org/auton_intranet/computing/22085.html


Note that I added FAQ section to the list of installed software trying to
address
some commonly  asked questions.

Further I would like to address MATLAB issues mentioned in TKs e-mail. We
do not
have licensing issue with the MATLAB. We have the issue with obsolete network
infrastructure which is currently being worked on. LOW1 has been switched
to new
gateway/firewall (Areas) while not being updated. As a consequence old shared
installation of MATLAB 2013b on LOW1 which requires contact with the
university
licensing server is not usable at the moment. LOV3, LOV4, LOU1, LXV1, LXV2
are
OK of course.

At the moment only 5 out of 18 computing nodes are up to date but updating
them
now before I finish LDAP server on Atlas makes no sense because so much
new things
(new file servers release) depend on LDAP. I can assure you that once LDAP is
finished I can update up to 3-4 computing nodes a day which means that for
remaining 17-5=12 nodes (LOS1 is garbage and will not be updated) I need
three
working days.

I hope that the answer to the second issue raised in TKs e-mail (obsolete
MATLAB 2013b)
is obvious. MATLAB 2014b has been released less than 7 days ago and
updating MATLAB
on obsolete and even non-obsolete computing nodes at the moment is low
priority when
there are so many more pressing issues. I do not want to put a time frame
on MATLAB
update but 2-3 weeks from now sounds like a good number.

Please feel free to communicate any concerns you might have. I apologize
for spotty
documentation too in particularly regarding GUI access to computing nodes
using X2Go
client and LOP1 and LOP2 as proxies. I have everything on my radar screen
but the
finite amount of time to fix things. I didn't forget Munin metric
monitoring. It is just put
on hold until I finish more urgent things.


Most Kind Regards,
Predrag