-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new psconfig packages to bundles #12
Comments
Added in
|
Just so you know, once I complete some more translation scripts, I plan to have the perfsonar-psconfig-pscheduler and perfsonar-psconfig-maddash packages obsolete the perfsonar-meshconfig-agent and perfsonar-meshconfig-guiagent packages respectively and automatically migrate over the configuration files of each. I'll be discussing this some more at the face-to-face on Wednesday afternoon. |
On Mon, Mar 05, 2018 at 06:24:11AM -0800, Andrew R. Lake wrote:
Just so you know, once I complete some more translation scripts, I
plan to have the perfsonar-psconfig-pscheduler and
perfsonar-psconfig-maddash packages obsolete the
perfsonar-meshconfig-agent and perfsonar-meshconfig-guiagent packages
respectively and automatically migrate over the configuration files of
each. I'll be discussing this some more at the face-to-face on
Wednesday afternoon.
Ok, I guess there is no harm installing it in parallel for now so
we can test?
…--
Valentin Vidic
Computer Systems Engineer - Expert
Department of Computer Infrastructure and Services
Croatian Academic and Research Network - CARNET
Josipa Marohnica 5, HR-10000 Zagreb, Croatia
tel: +385 1 6661 714, fax. +385 1 6661 635
gsm: +385 91 2480 919
www.CARNet.hr
|
Correct, no harm in installing them in parallel. I am doing the same. Just make sure if you had a pointer to a JSON file in psconfig, you remove that file from meshconfig or else you'll get double tests. |
…. Also removed OPPD and reference to no longer needed libperfsonar-regulartesting-perl
Whoops, hit wrong button |
We probably want to add the new psconfig packages to the testpoint and/or centralmanagement bundle.
The text was updated successfully, but these errors were encountered: