Bug 632429

My apologies, this is based on revision 3.1 of the document.

After consideration, we (grid) suggest that this revised section 3.2 should be folded into chapter 2 as follows:

1) Create a new subsection between the existing "first run" and "install sesame" subsections in chapter 2 which contains the revisions above.  Add a note that if the console will not be used with Grid, this new subsection may be skipped (similar to the language in the current Chapter 2, First Run, Step 1).

2) Eliminate the current Chapter 2, First Run, Step 1 which talks about condor-qmf installation since this subsection covers it and it is only necessary for use with Grid.

BZ 632424 (linked above) relates to Chapter 2, First Run changes as well.

The condor-qmf package is mentioned in the Start Console chapter.

Everything else has largely changed. Please review the 3.2 version of the document on the stage (available within the next 24 hours) and let me know if any further changes are required.

Thanks,
LKB

This has been updated again. Please look for revision 3.3, available shortly.

LKB

As of revision 3.4, some of the original notes still apply.  Restated here.

Some of the current "Connecting MRG Grid to the MRG Management Console" in section 3.2 is incorrect.  All of the plugin configuration is handled automatically by installation of condor-qmf; this creates a /etc/condor/config.d/60condor-qmf.config file which sets up the plugins.  None of the 40* files need to exist except 40QMF.conf

If condor-qmf is installed in the Start Console chapter, the workflow that remains should be:

1) create the 40QMF.config file, as in the current step 1 (but not the other files)

2) As in the current step 6, set QMF_BROKER_HOST in the 40QMF.config files on all nodes where the qpidd broker is not running locally.

3) As in the current step 2, set QUEUE_ALL_USERS_TRUSTED = TRUE to allow submissions from the console but do it in the 40QMF.config files

4)  To enable fair-share editing from the Console, set
ENABLE_RUNTIME_CONFIG = TRUE in the 40QMF.config files on the Grid nodes running the condor_negotiator.

5) Also, the sampling frequency of some graphs in the Grid overview screens
are controlled by how quickly the Condor Collector sends updates. The
default update rate is 15 minutes (900 seconds). It may be desirable to
increase the rate by changing COLLECTOR_UPDATE_INTERVAL. 

For instance, on the Grid node running the condor_collector, set COLLECTOR_UPDATE_INTERVAL = 60 in the 40QMF.config

6) if Condor was already running during the two steps above, restart it with /sbin/service condor restart

Note, the defaults for QMF_PUBLISH_SUBMISSIONS have changed so this no longer explicitly needs to be turned off as it is in the current step 2.

<section id="sect-Management_Console_Installation_Guide-Using_the_CONSOLE-Using_the_CONSOLE_with_GRID">
	<title>Using the &CONSOLE; with &GRID;</title>
	 <orderedlist id="orde-Management_Console_Installation_Guide-Using_the_CONSOLE_with_GRID-Connecting_the_CONSOLE_with_GRID">
	<title>Connecting the &CONSOLE; with &GRID;</title>
		 <para>
			Install &GRID; using the procedures located in the <citetitle>&GRID; Installation Guide</citetitle>
		</para>
	 <listitem>
		<para>
			Create a new file in the <filename>/etc/condor/config.d/</filename> directory called <filename>40QMF.config</filename>:
		</para>
				 
<screen>
# cd /etc/condor/config.d/
# touch 40QMF.config
</screen>
	</listitem>
	 <listitem>
		<para>
			Edit the new <emphasis>40QMF</emphasis> file on all nodes to add the following line, with the hostname of the machine running the broker:
		</para>
				 
<programlisting>
QMF_BROKER_HOST = <replaceable>hostname</replaceable></programlisting>

	</listitem>
	 <listitem>
		<para>
			Edit the new <emphasis>40QMF</emphasis> file on all nodes which are not running the &RHM; broker locally to add the following line:
		</para>
				
<programlisting>
QUEUE_ALL_USERS_TRUSTED = TRUE
</programlisting>
	</listitem>
	 <listitem>
		<para>
			To be able to edit fair-share in the &CONSOLE;, edit the new <emphasis>40QMF</emphasis> file on all nodes running the <command>condor_negotiator</command> to add the following line:
		</para>
				
<programlisting>
ENABLE_RUNTIME_CONFIG = TRUE
</programlisting>

	</listitem>
	 <listitem>
		<para>
			The sampling frequency of some graphs in the &GRID; overview screens is related to how frequently the Condor Collector sends updates. The default rate is fifteen minutes (900 sconds). This can be changed by adjusting the <command>COLLECTOR_UPDATE_INTERVAL</command> parameter.
		</para>
		 <para>
			Do this by editing the new <emphasis>40QMF</emphasis> file on the node running the <command>condor_collector</command> to add the following line, with the desired value in seconds:
		</para>
				
<programlisting>
COLLECTOR_UPDATE_INTERVAL = 60
</programlisting>

	</listitem>
	 <listitem>
		<para>
			Restart the <command>condor</command> service to pick up the changes:
		</para>
				
<screen>
# /sbin/service condor restart
</screen>

	</listitem>
</orderedlist>
<note>
<title>Note</title>
	 <para>
		&GRID; can also be configured remotely using the remote configuration feature. For more information about the remote configuration feature and how to use it, see the <citetitle>&GRID; User Guide</citetitle>.
	</para>
</note>
</section>
	
LKB

Modified again in revision 3.6, after IRC chat with mattf and tmckay.

Thanks,
LKB

(In reply to comment #7)
> Modified again in revision 3.6, after IRC chat with mattf and tmckay.
> 
> Thanks,
> LKB

Make that revision 3.7.
LKB

Verified in Revision 3.7, as of Thu Sep 16 2010.

Notes on revision 3.7

A) There is a minor typo in the introduction in section 3.2.  Something wrong around the word "with" in the following sentence:

"Each of the nodes in the MRG Grid pool with then need to have the configuration modified."

B) In step 4, "Edit the new 40QMF file on all nodes running the condor_schedd to add the following line:"

  Note, the addition of QUEUE_ALL_USERS_TRUSTED = TRUE is only necessary if submissions are to be allowed from the console.  If submissions will not be allowed from the console, i.e. the console will only be used for monitoring, this step is not required.

  Therefore, this sentence should probably be prefaced with "To allow submissions from the Console, "

C) The bold "40QMF file" references do not say "40QMF.config file".  Is this an intentional abbreviation of the filename, or a mistake?

D) Finally, Matt has been arguing persistently for moving the "yum install condor-qmf" instructions from Chapter 2, First Run, step 1, to the beginning of section 3.2.

Although I think it is not a disaster to have it where it is currently in Chapter 2, since it notes specifically that it is only necessary if Console will be used with Grid, I agree with Matt that it makes more logical sense to move the "yum install condor-qmf" step to section 3.2 and remove the qualifying statement.

So the first few steps in 3.2 looks something like this:

"
1 Install MRG Grid using the procedures located in the MRG Grid Installation Guide

2  Install the condor-qmf package. It provides QMF plugins to
various Condor daemons:

   # yum install condor-qmf


3 Create a new file in the /etc/condor/config.d/ directory called 40QMF.config: 
"

and Chapter 2, Start Console, Step 1 disappears

Additional notes after consultation with Matt.  These augment comment 10 above, using the same reference letter here to refer to the above comments:

B)  Concerning "QUEUE_ALL_USERS_TRUSTED".

  It is imperative to note that this parameter should only be set for nodes which the admin wishes to accept jobs submitted from the console.  This is not necessarily every node that is running schedd; it is ONLY the ones that the admin wishes to be available for job submissions from the console (schedds without this parameter set may still accept jobs submitted through condor tools).  This is important because this parameter relaxes some restrictions on the node.  No sense loosening restrictions when it is not intended.

D)  Concerning the moving of yum install condor-qmf out of Chapt 2 and into section 3.2:

    This really should be moved.

    It is ESSENTIAL to note that condor-qmf must be installed on all nodes that will communicate with the Console.  The current language in the instructions in Chapter 2 misses this completely.  

  "yum install condor-qmf" is a PER NODE operation.

(In reply to comment #10)
> Notes on revision 3.7
> 
> A) There is a minor typo in the introduction in section 3.2.  Something wrong
> around the word "with" in the following sentence:
> 
> "Each of the nodes in the MRG Grid pool with then need to have the
> configuration modified."

<para>
	In order to use the &CONSOLE; to manage a &GRID; installation, some configuration must be performed. The Condor QMF plugins allow the condor daemons to connect to a &RHM; broker using QMF. Each of the nodes in the &GRID; pool will then need to have the configuration modified.
</para>

> 
> B) In step 4, "Edit the new 40QMF file on all nodes running the condor_schedd
> to add the following line:"
> 
>   Note, the addition of QUEUE_ALL_USERS_TRUSTED = TRUE is only necessary if
> submissions are to be allowed from the console.  If submissions will not be
> allowed from the console, i.e. the console will only be used for monitoring,
> this step is not required.
> 
>   Therefore, this sentence should probably be prefaced with "To allow
> submissions from the Console, "

<listitem>
	<para>
		To allow submissions from the &CONSOLE;, edit the new <filename>40QMF</filename> file on all nodes running the <command>condor_schedd</command> to add the following line:
	</para>
				 
<programlisting>
QUEUE_ALL_USERS_TRUSTED = TRUE
</programlisting>
	<para>
		This step is not required if the &CONSOLE; is only going to be used for monitoring.
	</para>
</listitem>


> C) The bold "40QMF file" references do not say "40QMF.config file".  Is this an
> intentional abbreviation of the filename, or a mistake?

The .config extension got added later on, so only the initial reference to the filename got it. I thought it was a bit clunky to repeat over and over, but I've changed them now to avoid any confusion.

> 
> D) Finally, Matt has been arguing persistently for moving the "yum install
> condor-qmf" instructions from Chapter 2, First Run, step 1, to the beginning of
> section 3.2.
> 
> Although I think it is not a disaster to have it where it is currently in
> Chapter 2, since it notes specifically that it is only necessary if Console
> will be used with Grid, I agree with Matt that it makes more logical sense to
> move the "yum install condor-qmf" step to section 3.2 and remove the qualifying
> statement.
> 
> So the first few steps in 3.2 looks something like this:
> 
> "
> 1 Install MRG Grid using the procedures located in the MRG Grid Installation
> Guide
> 
> 2  Install the condor-qmf package. It provides QMF plugins to
> various Condor daemons:
> 
>    # yum install condor-qmf
> 
> 
> 3 Create a new file in the /etc/condor/config.d/ directory called 40QMF.config: 
> "
> 
> and Chapter 2, Start Console, Step 1 disappears

Done.

LKB

*** Bug 633680 has been marked as a duplicate of this bug. ***

Verified in Revision 3.8, as of Fri Sep 17 2010.

Both 2. and 3.2. were changed appropriately.
What does Trevor think?

I think this is okay.

Thanks. Setting to verified.

Apologies, Jan, time-zone damage.  Late breaking review and request on behalf of Matt.

----

from Matt:

"If it will not be used with MRG Grid, this step can be skipped." should
be removed. This is the wrong place for that language.

If they skip the install step, what about all the other steps in that
section?

-------

* Strike this sentence from step 1 

  "If it will not be used with MRG Grid, this step can be skipped."

* Add a sentence to the 3.2 overview that says

  "If the MRG Management Console will not be used with MRG Grid, this section may be skipped."

(In reply to comment #17)
> Apologies, Jan, time-zone damage.  Late breaking review and request on behalf
> of Matt.
> 
> ----
> 
> from Matt:
> 
> "If it will not be used with MRG Grid, this step can be skipped." should
> be removed. This is the wrong place for that language.
> 
> If they skip the install step, what about all the other steps in that
> section?
> 
> -------
> 
> * Strike this sentence from step 1 
> 
>   "If it will not be used with MRG Grid, this step can be skipped."

Covered in #630579.

> 
> * Add a sentence to the 3.2 overview that says
> 
>   "If the MRG Management Console will not be used with MRG Grid, this section
> may be skipped."

Considering the entire section is called "Using the Console with Grid", this can be considered implicit.

LKB

Verified in Revision 3.10, Wed Sep 22 2010.