Hi, Michael
How can I deploy lava-scheduler-tool for the buildout lava instance?
I tried with both the "python setup.py install" command and the lava-develop-local command, but neither seems work:(
here is the console log I did: (buildout)17:06:56 liuyq:lava-scheduler-tool$ python setup.py install error in lava-scheduler-tool setup command: Unable to import 'lava_scheduler_tool': No module named lava_scheduler_tool (buildout)17:07:03 liuyq:lava-scheduler-tool$ cd ../ (buildout)17:07:06 liuyq:code$ pwd /srv/lava/code (buildout)17:07:07 liuyq:code$ lava-develop-local lava-scheduler-tool/ Determining egg name... lava-scheduler-tool + ln -sfT /srv/lava/code/lava-scheduler-tool /srv/lava/instances/buildout/code/r67/local/lava-scheduler-tool + /srv/lava/instances/buildout/code/r67/bin/rebuildout ++ basename buildout-development.cfg + /srv/lava/instances/buildout/var/lib/bootstrap-venv/bin/buildout -c /srv/lava/instances/buildout/code/r67/buildout-development.cfg Develop: '/srv/lava/instances/buildout/code/r67/.' Develop: '/srv/lava/instances/buildout/code/r67/local/lava-android-test' warning: no files found matching '.testr.conf' Develop: '/srv/lava/instances/buildout/code/r67/local/lava-dispatcher' Develop: '/srv/lava/instances/buildout/code/r67/local/lava-scheduler-tool'
Installed /srv/lava/code/lava-scheduler-tool/versiontools-1.9.1-py2.7.egg Uninstalling manifest. Uninstalling server-symlink. Running uninstall recipe. Uninstalling wsgi. Uninstalling instance. Installing instance. Updating server. Develop distribution: lava-dispatcher 0.18.dev383 uses namespace packages but the distribution does not require setuptools. Generated interpreter '/srv/lava/instances/buildout/code/r67/bin/py'. Updating python. Develop distribution: lava-dispatcher 0.18.dev383 uses namespace packages but the distribution does not require setuptools. Generated interpreter '/srv/lava/instances/buildout/code/r67/bin/python'. Updating hack-py. hack-py: Running sed -i -e 's%^_interactive%import os; os.environ["DJANGO_DEBIAN_SETTINGS_TEMPLATE"] = "/srv/lava/instances/buildout/etc/lava-server/{filename}.conf"; os.environ["DJANGO_SETTINGS_MODULE"] = "lava_server.settings.debian";&%' /srv/lava/instances/buildout/code/r67/bin/py /srv/lava/instances/buildout/code/r67/bin/python Installing wsgi. Develop distribution: lava-dispatcher 0.18.dev383 uses namespace packages but the distribution does not require setuptools. Generated script '/srv/lava/instances/buildout/code/r67/bin/lava-server.wsgi'. Updating scripts. Installing server-symlink. Develop distribution: lava-dispatcher 0.18.dev383 uses namespace packages but the distribution does not require setuptools. Installing manifest. Develop distribution: lava-dispatcher 0.18.dev383 uses namespace packages but the distribution does not require setuptools. (buildout)17:07:23 liuyq:code$ lava-tool submit-job usage: lava-tool [-h] {auth-add,help} ... lava-tool: error: invalid choice: 'submit-job' (choose from 'auth-add', 'help') (buildout)17:07:42 liuyq:code$
On 10/10/2012 04:12 AM, YongQin Liu wrote:
Hi, Michael
How can I deploy lava-scheduler-tool for the buildout lava instance?
I tried with both the "python setup.py install" command and the lava-develop-local command, but neither seems work:(
I think you should follow what I did here:
http://lists.linaro.org/pipermail/linaro-validation/2012-July/000736.html
Andy Doan andy.doan@linaro.org writes:
On 10/10/2012 04:12 AM, YongQin Liu wrote:
Hi, Michael
How can I deploy lava-scheduler-tool for the buildout lava instance?
I tried with both the "python setup.py install" command and the lava-develop-local command, but neither seems work:(
I think you should follow what I did here:
http://lists.linaro.org/pipermail/linaro-validation/2012-July/000736.html
Yeah. We need to make this easier -- I've come to think that the difference between developer and production deployments need to be a bit greater. It's a bit risky I guess as it increases the chances of troublemaking skew, but I think developer convenience is worth quite a lot (fwiw, the other change I'd like to make is to have developer instances run as the developer's user account, not an instance specific account -- this will make testing easier).
Cheers, mwh
Hi, Michael
Thanks for the help.
And below is the our talk in irc, if anyone others have same requirement, I guess they can work through this talk:)
<mwhudson> liuyq: hi <liuyq> mwhudson, from the mail Andy sent I still can't find how to install lava-dashboard-tool for the buildout format lava instance <liuyq> mwhudson, could you give me the instructions? <mwhudson> liuyq: to be honest, i just install lava-dashboard-tool with apt-get usually <mwhudson> but <liuyq> mwhudson, into the system? <mwhudson> create a file called /srv/lava/instance/code/buildout-custom.cfg containing this: http://paste.ubuntu.com/1286213/ <mwhudson> err <mwhudson> a file called /srv/lava/instances/$instance/code/buildout-custom.cfg <mwhudson> then edit /srv/lava/instances/$instance/instance.conf <mwhudson> to have LAVA_BUILDOUT_CFG='../buildout-custom.cfg' <mwhudson> and then run /srv/lava/instances/$instance/bin/rebuildout <liuyq> mwhudson, then if I also want to install the lava-scheduler-tool and linaro-graphics-dashboard, does this work for me? https://pastebin.linaro.org/1018/ <mwhudson> liuyq: yup <liuyq> mwhudson, ok, thanks, will try it <liuyq> mwhudson, seems my /srv/lava/instances/buildout/bin/rebuildout is old, https://pastebin.linaro.org/1019/ <liuyq> mwhudson, so I changed the r67 to current and move the buildout-custom.cfg to current <mwhudson> liuyq: oh <mwhudson> sorry <mwhudson> yeah, you need a symlink from .../code/current/buildout-custom.cfg to ../buildout-custom.cfg <liuyq> mwhudson, and then after I ran rebuildout, I found only the scheduler-tool works <liuyq> (buildout)10:38:00 liuyq:code$ lava-tool put <liuyq> usage: lava-tool [-h] {auth-add,help,submit-job,resubmit-job,cancel-job} ... <liuyq> lava-tool: error: invalid choice: 'put' (choose from 'auth-add', 'help', 'submit-job', 'resubmit-job', 'cancel-job') <liuyq> (buildout)10:38:01 liuyq:code$ <mwhudson> liuyq: no lava-dashboard-tool? <mwhudson> liuyq: try lava dashboard put? <mwhudson> hmm <liuyq> and from the web, I can't see the graphics menu too:( <liuyq> mwhudson, ah, lava dashboard command works <liuyq> (buildout)10:38:01 liuyq:code$ lava dashboard put <liuyq> usage: lava dashboard put [-h] --dashboard-url URL [--verbose-xml-rpc] <liuyq> LOCAL [REMOTE] <liuyq> lava dashboard put: error: too few arguments <liuyq> (buildout)10:39:14 liuyq:code$ <mwhudson> liuyq: if you've set things up so that code/current/buildout-custom.cfg is a symlink, run lava-deployment-tool update <mwhudson> liuyq: there are a few things that need to be done when you install a new lava web extension <mwhudson> (run migrations, buildstatic, and restart the service) <liuyq> mwhudson, you mean I put the buildout-custom.cfg in the code directory, and make a symlink in the code/current directory? <mwhudson> liuyq: yes <liuyq> mwhudson, for the "lava-deployment-tool update", is it run "lava-deployment-tool update" only enough or do (run migrations, buildstatic, and restart the service) after run "lava-deployment-tool update" ? <mwhudson> liuyq: update is enough <mwhudson> we can't kill lava-test style tests soon enough <liuyq> mwhudson,with the command "./lava-deployment-tool upgrade $instance", now I can see the graphics menu from the web gui <mwhudson> liuyq: \o/ <liuyq> mwhudson, btw, for the branch we can used with lava-develop-local, it must be specified in the buildout-custom.cfg and run rebuildout first? <mwhudson> liuyq: if i understand you right, yes <mwhudson> liuyq: if you want to use a package `lava-foo' it needs to be in a buildout config file <mwhudson> if you run lava-develop-local my-lava-foo-branch it will use that <mwhudson> but only once you've added it to the buildout config <liuyq> mwhudson, thanks, now I know more about buildout from this talk with you:) <mwhudson> liuyq: :-)
Thanks, Yongqin Liu On 11 October 2012 05:49, Michael Hudson-Doyle michael.hudson@linaro.org wrote:
Andy Doan andy.doan@linaro.org writes:
On 10/10/2012 04:12 AM, YongQin Liu wrote:
Hi, Michael
How can I deploy lava-scheduler-tool for the buildout lava instance?
I tried with both the "python setup.py install" command and the lava-develop-local command, but neither seems work:(
I think you should follow what I did here:
http://lists.linaro.org/pipermail/linaro-validation/2012-July/000736.html
Yeah. We need to make this easier -- I've come to think that the difference between developer and production deployments need to be a bit greater. It's a bit risky I guess as it increases the chances of troublemaking skew, but I think developer convenience is worth quite a lot (fwiw, the other change I'd like to make is to have developer instances run as the developer's user account, not an instance specific account -- this will make testing easier).
Cheers, mwh
Also append the content of the two links for reference.
http://paste.ubuntu.com/1286213/
[buildout]
extends = buildout.cfg
[server]
eggs += lava-dashboard-tool
https://pastebin.linaro.org/1018/
[buildout] extends = buildout.cfg
[server] eggs += lava-dashboard-tool lava-scheduler-tool linaro-graphics-dashboard
Thanks, Yongqin Liu On 18 October 2012 11:03, YongQin Liu yongqin.liu@linaro.org wrote:
Hi, Michael
Thanks for the help.
And below is the our talk in irc, if anyone others have same requirement, I guess they can work through this talk:)
<mwhudson> liuyq: hi <liuyq> mwhudson, from the mail Andy sent I still can't find how to install lava-dashboard-tool for the buildout format lava instance <liuyq> mwhudson, could you give me the instructions? <mwhudson> liuyq: to be honest, i just install lava-dashboard-tool with apt-get usually <mwhudson> but <liuyq> mwhudson, into the system? <mwhudson> create a file called /srv/lava/instance/code/buildout-custom.cfg containing this: http://paste.ubuntu.com/1286213/ <mwhudson> err <mwhudson> a file called
/srv/lava/instances/$instance/code/buildout-custom.cfg
<mwhudson> then edit /srv/lava/instances/$instance/instance.conf <mwhudson> to have LAVA_BUILDOUT_CFG='../buildout-custom.cfg' <mwhudson> and then run /srv/lava/instances/$instance/bin/rebuildout <liuyq> mwhudson, then if I also want to install the lava-scheduler-tool and linaro-graphics-dashboard, does this work for me? https://pastebin.linaro.org/1018/ <mwhudson> liuyq: yup <liuyq> mwhudson, ok, thanks, will try it <liuyq> mwhudson, seems my /srv/lava/instances/buildout/bin/rebuildout is old, https://pastebin.linaro.org/1019/ <liuyq> mwhudson, so I changed the r67 to current and move the buildout-custom.cfg to current <mwhudson> liuyq: oh <mwhudson> sorry <mwhudson> yeah, you need a symlink from .../code/current/buildout-custom.cfg to ../buildout-custom.cfg <liuyq> mwhudson, and then after I ran rebuildout, I found only the scheduler-tool works <liuyq> (buildout)10:38:00 liuyq:code$ lava-tool put <liuyq> usage: lava-tool [-h] {auth-add,help,submit-job,resubmit-job,cancel-job} ... <liuyq> lava-tool: error: invalid choice: 'put' (choose from 'auth-add', 'help', 'submit-job', 'resubmit-job', 'cancel-job') <liuyq> (buildout)10:38:01 liuyq:code$ <mwhudson> liuyq: no lava-dashboard-tool? <mwhudson> liuyq: try lava dashboard put? <mwhudson> hmm <liuyq> and from the web, I can't see the graphics menu too:( <liuyq> mwhudson, ah, lava dashboard command works <liuyq> (buildout)10:38:01 liuyq:code$ lava dashboard put <liuyq> usage: lava dashboard put [-h] --dashboard-url URL
[--verbose-xml-rpc]
<liuyq> LOCAL [REMOTE] <liuyq> lava dashboard put: error: too few arguments <liuyq> (buildout)10:39:14 liuyq:code$ <mwhudson> liuyq: if you've set things up so that code/current/buildout-custom.cfg is a symlink, run lava-deployment-tool update <mwhudson> liuyq: there are a few things that need to be done when you install a new lava web extension <mwhudson> (run migrations, buildstatic, and restart the service) <liuyq> mwhudson, you mean I put the buildout-custom.cfg in the code directory, and make a symlink in the code/current directory? <mwhudson> liuyq: yes <liuyq> mwhudson, for the "lava-deployment-tool update", is it run "lava-deployment-tool update" only enough or do (run migrations, buildstatic, and restart the service) after run "lava-deployment-tool update" ? <mwhudson> liuyq: update is enough <mwhudson> we can't kill lava-test style tests soon enough <liuyq> mwhudson,with the command "./lava-deployment-tool upgrade $instance", now I can see the graphics menu from the web gui <mwhudson> liuyq: \o/ <liuyq> mwhudson, btw, for the branch we can used with lava-develop-local, it must be specified in the buildout-custom.cfg and run rebuildout first? <mwhudson> liuyq: if i understand you right, yes <mwhudson> liuyq: if you want to use a package `lava-foo' it needs to be in a buildout config file <mwhudson> if you run lava-develop-local my-lava-foo-branch it will use
that
<mwhudson> but only once you've added it to the buildout config <liuyq> mwhudson, thanks, now I know more about buildout from this talk with you:) <mwhudson> liuyq: :-)
Thanks, Yongqin Liu On 11 October 2012 05:49, Michael Hudson-Doyle michael.hudson@linaro.org wrote:
Andy Doan andy.doan@linaro.org writes:
On 10/10/2012 04:12 AM, YongQin Liu wrote:
Hi, Michael
How can I deploy lava-scheduler-tool for the buildout lava instance?
I tried with both the "python setup.py install" command and the lava-develop-local command, but neither seems work:(
I think you should follow what I did here:
<
http://lists.linaro.org/pipermail/linaro-validation/2012-July/000736.html%3E
Yeah. We need to make this easier -- I've come to think that the difference between developer and production deployments need to be a bit greater. It's a bit risky I guess as it increases the chances of troublemaking skew, but I think developer convenience is worth quite a lot (fwiw, the other change I'd like to make is to have developer instances run as the developer's user account, not an instance specific account -- this will make testing easier).
Cheers, mwh
-- Thanks, Yongqin Liu
#mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android linaro-validation@lists.linaro.org http://lists.linaro.org/pipermail/linaro-validation
linaro-validation@lists.linaro.org
-
Andy Doan -
Michael Hudson-Doyle -
YongQin Liu