perfSONAR User Q&A and Other Discussion

[Charley Kneifel <>]

I deployed a 4.0 RC3 server last night and noticed a couple of things -

1) I deployed from the full ISO

2) Running on VMWare vSphere 5.5

3) ran through the full GUI install as described in the docs (http://docs.perfsonar.net/release_candidates/4.0rc3/install_centos_fullinstall.html)

4) System installed and then came back up and was able to login via the VMWare console but I noticed that VM did not have a proper name.

I was able to get things going by use of the hostnamectl to give it a hostname, but I didn't see anyplace to have set that in the installation phase (but it's likely I missed something).  It did properly get an IP address from the DHCP server, just not the name.

The only other oddity is that the VM shows up with the memory in RED in the configuration dashboard with only 1.6/4 GB of RAM in use - the documentation states minimums of 4GB - should that be higher for the new version?

As usual I had to edit lsregistrationdaemon.conf and web_admin.conf to allow for internal addresses (shouldn't that be an option in the administrative interface?  We use them internally on our private network for testing).

Charley

---

From: <> on behalf of Andrew Lake <>
Sent: Monday, March 27, 2017 3:01 PM
To: ;
Subject: [perfsonar-user] perfSONAR 4.0rc3 now available for testing!

 

All,

 

The third release candidate of perfSONAR 4.0 is now available for testing. As always, please DO NOT install this on EXISTING production hosts as it is not the final release (see the CentOS 7 section below if you are planning a new deployment). We anticipate that this will be the last release candidate prior to the final release, and its date will be dependent on the results of this round of community testing. You'll note that we had a much-larger-than-usual gap between RC2 in November and this release. That time has been spent extensively testing and optimizing the code, as this is probably the largest software change in the project's history and we want to be really sure we get it right. We anticipate that the time between RC3 and the final will be significantly shorter. Expect more details on preparing for this release in a follow-up email. For more details on various topics relevant to this RC, see the sections below:

 

============================================

Changes since 4.0RC2

============================================

See our release notes at: http://www.perfsonar.net/release-notes/version-4-0-rc3/

 

==============================================

Getting 4.0RC3

============================================

In terms of obtaining this release, many of you probably have it via auto-updates if you tested our previous release candidates. If not, please see http://docs.perfsonar.net/release_candidates/4.0rc3/install_rcs.html for instructions on how to obtain it. In general, the best place for documentation on this RC can be found at http://docs.perfsonar.net/release_candidates/4.0rc3. Also please see our checklist at https://github.com/perfsonar/project/wiki/Toolkit-Testing-Checklist for things to look for after upgrading.

 

============================================

CentOS 7

============================================

We know many of you have been waiting on 4.0 so you can start a CentOS 7 deployment. If you are in this category, we suggest you download and install RC3. You will be able to auto-update it to the final and we are comfortable enough with it on CentOS 7 that you should have a relatively stable deployment. You are also welcome to wait, but we know some of you are really anxious to play with CentOS 7 and the software should be in a state where you can comfortably do so.

Thank you,

The perfSONAR Development Team