Project

General

Profile

Feature #2413

Feature #2172: Making config file location optional during reconfig

Changing the location of setup scripts factory.sh and frontend.sh

Added by Parag Mhashilkar almost 8 years ago. Updated over 4 years ago.

Status:
Assigned
Priority:
Low
Assignee:
-
Category:
-
Target version:
Start date:
01/23/2012
Due date:
% Done:

0%

Estimated time:
Stakeholders:
Duration:

Description

While we are streamlining the startup scritps we might as well change the location of setup scrips factory.sh and frontend.sh to their respective configuration directory or the workspace. I like the config dir better. There is no reason to keep them hanging and wandering about in the glideinsubmit and frontstage area.

History

#1 Updated by Igor Sfiligoi almost 8 years ago

That is "the frontend.sh file"?

#2 Updated by Igor Sfiligoi almost 8 years ago

Sorry... that should have been reading:
What is "the frontend.sh file"?

Igor

#3 Updated by Parag Mhashilkar almost 8 years ago

Setup scripts what setup right environment. Something new if you have been using the ini installer

#4 Updated by Burt Holzman over 7 years ago

  • Target version set to v3_1

#5 Updated by John Weigand over 7 years ago

Suggestion to think about:

The only data in these 2 scripts is:
1. factory.sh
- exports X509_CERT_DIR
only needed if /etc/grid-security/certificates is not available
- and it is sourcing the wms collectors condor.sh env script
2. frontend.sh
- only sourcing the frontend's condor condor.sh env script

We would not need these scripts if we included these attributes
in the configuration xml files of each. That would make it all very self-contained.

OK... I am prepared to get slammed on this great idea. Fire away.

John Weigand

#6 Updated by John Weigand about 7 years ago

  • Status changed from New to Feedback
  • Assignee changed from John Weigand to Parag Mhashilkar

I never got any feedback on my original suggestion regarding
including the pieces of data in the setup scripts in
the respective config files. The startup scripts created for
both can have this included thus making it all very
self-contained and insures the environment is set correctly.
It would eliminate those 2 files completely.
It makes it "one-stop shopping" so to speak.

John Weigand

#7 Updated by John Weigand about 7 years ago

Doug,

How is this being handled on the RPM installs?

John Weigand

#8 Updated by Parag Mhashilkar over 6 years ago

  • Priority changed from Normal to Low

#9 Updated by Burt Holzman over 6 years ago

  • Status changed from Feedback to Assigned
  • Assignee changed from Parag Mhashilkar to John Weigand

Kicking back to John to think about.

#10 Updated by Burt Holzman over 6 years ago

  • Target version changed from v3_1 to v3_x

#11 Updated by Parag Mhashilkar over 4 years ago

  • Assignee deleted (John Weigand)


Also available in: Atom PDF