Merge lp:~kim-phillips/lava-scheduler/updates into lp:lava-scheduler

[Kim Phillips]

doc/usage.rst: documentation updates

  - include lava-server/ in the URL paths
  - make URLs consistently use https: and include user@
  - mention trailing slashes are required

doc/usage.rst: documentation updates

  - include lava-server/ in the URL paths
  - make URLs consistently use https: and include user@
  - mention trailing slashes are required

[Alan Bennett (akbennett)]

validation.linaro.org happens to be located in a legacy location
  - https://<email address hidden>/lava-server/RPC2/

The default location for a new lava install would be:
  - https://<email address hidden>/RPC2/

However, the important note is that the user needs to point the browser to the lava installation URL.

Perhaps we need to mention all three cases?
  1. legacy installation path for validation.linaro.org
  2. current installation path for new lava installs
  3. custom vhost configurations

[Kim Phillips (kim-phillips)]

> validation.linaro.org happens to be located in a legacy location
> - https://<email address hidden>/lava-server/RPC2/

can/will that be fixed? Was hoping to not have to add anything installation specific, since there is no other reference to validation.linaro.org in the document, and I perceive this to be generic LAVA scheduler documentation.

[Alan Bennett (akbennett)]

> > validation.linaro.org happens to be located in a legacy location
> > - https://<email address hidden>/lava-server/RPC2/
>
> can/will that be fixed? Was hoping to not have to add anything installation
> specific, since there is no other reference to validation.linaro.org in the
> document, and I perceive this to be generic LAVA scheduler documentation.

Yes, we have scoped the effort to move the validation.linaro.org and hope to get it on the board for the upcoming cycle.

Unmerged revisions

247. By Kim Phillips on 2013-05-16

doc/usage.rst: documentation updates

- include lava-server/ in the URL paths
- make URLs consistently use https: and include user@
- mention trailing slashes are required

=== modified file 'doc/usage.rst'
--- doc/usage.rst	2012-10-23 07:12:53 +0000
+++ doc/usage.rst	2013-05-16 22:00:34 +0000
@@ -46,7 +46,7 @@
 To submit jobs using the scheduler, you should first set up the server
 to which you will be submitting jobs::
 
- $ lava-tool auth-add https://[e-mail]/RPC2/
+ $ lava-tool auth-add https://[e-mail]/lava-server/RPC2/
 
 In this example, *[e-mail]* should be replaced with your userid
 and webserver.  Using https is *highly* recommended since it will ensure
@@ -65,7 +65,9 @@
 The first thing you may want to do is create a bundle stream in the LAVA
 dashboard where you'll put your bundles. This is done with::
 
-  lava-dashboard-tool make-stream --dashboard-url http://example.com/RPC2/ /anonymous/USERNAME/
+  lava-dashboard-tool make-stream --dashboard-url https://[e-mail]/lava-server/RPC2/ /anonymous/USERNAME/
+
+(note: the trailing slash ('/') is required)
 
 Next you'll need a job file. You can read about an example job file `here`_
 
@@ -73,5 +75,5 @@
 
 You can now submit jobs by running ::
 
- $ lava scheduler submit-job http://[e-mail]/RPC2/ jobfile.json
+ $ lava scheduler submit-job https://[e-mail]/lava-server/RPC2/ jobfile.json