Autotest is a framework for automated testing designed primarily to test the Linux kernel and KVM virtualization ()

Spear, Raymond (Mission Critical Linux | 1 May 2012 17:22

Picon

Re: multiple user documentation

Sorry for being so ignorant but, I don't remember ever logging into the autotest web interface.  So, I'm not
sure how to enable this login capability.

I installed autotest using the contrib setup script.

ray spear

-----Original Message-----
From: Nishanth Aravamudan [mailto:nacc <at> linux.vnet.ibm.com] 
Sent: Monday, April 30, 2012 3:41 PM
To: Spear, Raymond (Mission Critical Linux)
Cc: Autotest <at> test.kernel.org
Subject: Re: [Autotest] multiple user documentation

On 30.04.2012 [21:45:12 +0000], Spear, Raymond (Mission Critical Linux) wrote:
> I've been trying to find documentation which tells me how to set up 
> autotest so the frontend will have more than just the "default user".

I just modified the apache configuration to have LDAP-based auth for my setup. Then all the LDAP users are
potential autotest users, added to the appropriate table when they first login (afaict).

> I want to set up multiple users so each person can filter the test 
> based on the tests they start.
> 
> I see there is an owner filter but I can't find documentation which 
> tells me how to set up multiple "owners".

I think the admin side of things needs extensions. I still haven't been able to configure my setup to have
some LDAP auth'd users be admins and not others, for instance.

(Continue reading)

Spear, Raymond (Mission Critical Linux | 1 May 2012 17:29

Picon

Re: multiple user documentation

A lot of the Web pages out there talk about doing things on the server using "atest".  I found a file in
/usr/local/autotest/cli called "atest.py" which I assume is this command.  However, that file is not executable.

I have no /usr/local/autotest/bin.

I haven't found anything on the WEB about this.  I setup my server using the contrib script contrib/install-autotest-server.sh.

What did I miss?

Thanks, ray spear

Nishanth Aravamudan | 1 May 2012 22:00

Picon

Re: multiple user documentation

On 01.05.2012 [15:22:49 +0000], Spear, Raymond (Mission Critical Linux) wrote:
> Sorry for being so ignorant but, I don't remember ever logging into
> the autotest web interface.  So, I'm not sure how to enable this login
> capability.

I think by default auth is disabled (or automatic as debug_user). I
changed my setup via apache/conf/afe-directives:

 <Location "/afe">
     DirectoryIndex AfeClient.html
+    AuthType basic
+    AuthBasicProvider ldap
+    AuthzLDAPAuthoritative on
+    AuthBasicAuthoritative off
+    AuthLDAPURL <local ldap setup>
+    Require valid-user
+    AuthUserFile /dev/null
 </Location>

Thanks,
Nish

> I installed autotest using the contrib setup script.
> 
> ray spear
> 
> -----Original Message-----
> From: Nishanth Aravamudan [mailto:nacc <at> linux.vnet.ibm.com] 
> Sent: Monday, April 30, 2012 3:41 PM
> To: Spear, Raymond (Mission Critical Linux)

(Continue reading)

Nishanth Aravamudan | 1 May 2012 22:24

Picon

Re: multiple user documentation

On 01.05.2012 [15:29:02 +0000], Spear, Raymond (Mission Critical Linux) wrote:
> A lot of the Web pages out there talk about doing things on the server
> using "atest".  I found a file in /usr/local/autotest/cli called
> "atest.py" which I assume is this command.  However, that file is not
> executable.
> 
> I have no /usr/local/autotest/bin.
> 
> I haven't found anything on the WEB about this.  I setup my server
> using the contrib script contrib/install-autotest-server.sh.
> 
> What did I miss?

I'm not positive, but maybe you're mixing up client and server directory
structures?

/usr/local/autotest/cli are the files used to build/support the CLI (as
opposed to the web interface).

/usr/local/autotest/bin I think only exists on clients running autotest
jobs.

I'm not sure what atest is, but I've not yet needed to look for it :)

-Nish

--

-- 
Nishanth Aravamudan <nacc <at> us.ibm.com>
IBM Linux Technology Center

(Continue reading)

Spear, Raymond (Mission Critical Linux | 1 May 2012 22:55

Picon

Re: multiple user documentation

the github autotest pages says:

*Autotest command line interface: Alternatively, users also can use the autotest CLI, written in python

we ran into issues and when we looked on the web the "fixes" all said to run atest with specific options.
there is no atest executable created when the contrib install script is used.

I tried to do "python /usr/local/autotest/cli/atest.py --help" but it did nothing

ray spear

-----Original Message-----
From: Nishanth Aravamudan [mailto:nacc <at> linux.vnet.ibm.com] 
Sent: Tuesday, May 01, 2012 1:25 PM
To: Spear, Raymond (Mission Critical Linux)
Cc: Autotest <at> test.kernel.org
Subject: Re: [Autotest] multiple user documentation

On 01.05.2012 [15:29:02 +0000], Spear, Raymond (Mission Critical Linux) wrote:
> A lot of the Web pages out there talk about doing things on the server 
> using "atest".  I found a file in /usr/local/autotest/cli called 
> "atest.py" which I assume is this command.  However, that file is not 
> executable.
> 
> I have no /usr/local/autotest/bin.
> 
> I haven't found anything on the WEB about this.  I setup my server 
> using the contrib script contrib/install-autotest-server.sh.
> 
> What did I miss?

(Continue reading)

Nishanth Aravamudan | 1 May 2012 23:20

Picon

Re: multiple user documentation

On 01.05.2012 [20:55:38 +0000], Spear, Raymond (Mission Critical Linux) wrote:
> the github autotest pages says:
> 
> *Autotest command line interface: Alternatively, users also can use the autotest CLI, written in python
> 
> we ran into issues and when we looked on the web the "fixes" all said to run atest with specific options.
> there is no atest executable created when the contrib install script is used.

Let's ignore the web (unless you mean the wiki :) -- what issues did you
hit with the CLI?

Thanks,
Nish

> 
> I tried to do "python /usr/local/autotest/cli/atest.py --help" but it did nothing
> 
> ray spear
> 
> -----Original Message-----
> From: Nishanth Aravamudan [mailto:nacc <at> linux.vnet.ibm.com] 
> Sent: Tuesday, May 01, 2012 1:25 PM
> To: Spear, Raymond (Mission Critical Linux)
> Cc: Autotest <at> test.kernel.org
> Subject: Re: [Autotest] multiple user documentation
> 
> On 01.05.2012 [15:29:02 +0000], Spear, Raymond (Mission Critical Linux) wrote:
> > A lot of the Web pages out there talk about doing things on the server 
> > using "atest".  I found a file in /usr/local/autotest/cli called 
> > "atest.py" which I assume is this command.  However, that file is not

(Continue reading)

Lucas Meneghel Rodrigues | 2 May 2012 03:12

Picon

Re: multiple user documentation

On Tue, 2012-05-01 at 15:29 +0000, Spear, Raymond (Mission Critical
Linux) wrote:
> A lot of the Web pages out there talk about doing things on the server using "atest".  I found a file in
/usr/local/autotest/cli called "atest.py" which I assume is this command.  However, that file is not executable.
> 
> I have no /usr/local/autotest/bin.
> 
> I haven't found anything on the WEB about this.  I setup my server using the contrib script contrib/install-autotest-server.sh.
> 
> What did I miss?

I was on holiday today, getting back to read email, just saw your
inquiry.

Actually, I missed updating the docs. atest was renamed to
autotest-rpc-client, and atest.py became just a library that contains
the application core functionality. The reason why a longer name was
chosen was discoverability on a system wide install.

I've just pushed an update to the wiki that replaces all uses of atest
with autotest-rpc-client.

Cheers,

Lucas

Lucas Meneghel Rodrigues | 2 May 2012 03:13

Picon

Re: multiple user documentation

On Tue, 2012-05-01 at 13:24 -0700, Nishanth Aravamudan wrote:
> On 01.05.2012 [15:29:02 +0000], Spear, Raymond (Mission Critical Linux) wrote:
> > A lot of the Web pages out there talk about doing things on the server
> > using "atest".  I found a file in /usr/local/autotest/cli called
> > "atest.py" which I assume is this command.  However, that file is not
> > executable.
> > 
> > I have no /usr/local/autotest/bin.
> > 
> > I haven't found anything on the WEB about this.  I setup my server
> > using the contrib script contrib/install-autotest-server.sh.
> > 
> > What did I miss?
> 
> I'm not positive, but maybe you're mixing up client and server directory
> structures?
> 
> /usr/local/autotest/cli are the files used to build/support the CLI (as
> opposed to the web interface).
> 
> /usr/local/autotest/bin I think only exists on clients running autotest
> jobs.
> 
> I'm not sure what atest is, but I've not yet needed to look for it :)

It's the old name of what it's called today 'autotest-rpc-client'.

> -Nish
>

(Continue reading)

Don Zickus | 2 May 2012 23:14

Picon

Re: [ANNOUNCEMENT] - Autotest history rewritten

On Fri, Apr 27, 2012 at 05:39:02PM -0300, Ademar de Souza Reis Jr. wrote:
> 
> Below is a different approach, which I consider simpler but
> requires a bit more understanding of git:
> 
> First of all, if you run git pull on top of your curren branch,
> it'll break with tons of conflicts. In this case, just run:
>   $ git reset --hard
> and things will get back to normal (as before git pull)
> 
> Now for the "migration" procedure, assuming origin points to the
> upstream git repository (the default).
> 
> (DISCLAIMER: untested)

Or you can drive like a git pro: (recalling from memory from lots of use)

1. Find your current branch name (git branch - look for the *)

2. checkout a new branch "git checkout -b <branch>_new"

3. Find your fork point using 'git log' or if you haven't fetch'd Lucas's
tree yet - "git log --oneline origin/master..HEAD" (the bottom commit sha
is what you want)

4. Fetch Lucas's tree - 'git fetch origin'

5. The cool trick (assuming Lucas's changes are in origin/master)
  the <fork point SHA> should be the SHA of your _first_ commit in the
fork

(Continue reading)

Liu Sheng | 3 May 2012 04:45

Picon

Re: autotest server can't run kvm autotest on the host.

On Sat, Apr 28, 2012 at 12:06:42PM -0300, Lucas Meneghel Rodrigues wrote:
>On Sat, Apr 28, 2012 at 5:19 AM, Liu Sheng <liusheng <at> linux.vnet.ibm.com> wrote:
>> Hi
>> I setup an autotest server to control another machine run some tests, I create
>> jobs for sleep test and dbench, they both work well. But I when I run kvm
>> autotest which is I actually want to run, it seems not work. In the server's
>> log it seems everything works well until the client raise AutotestRun Error:
>> client job was aborted. In the client's log everything goes well until an
>> IOError that can't find /usr/local/autotest/tests/kvm/build.cfg. I check the
>> /usr/local/autotest/tests directory in the remote host, actually there's no
>> kvm directory in it, only sleeptest, dbench directory and another download
>> directory. So something wrong with my configuration or kvm autotest need some
>> special settings?
>
>You have to create the actual configuration files from the samples. In
>your server, you can do a:
>
>cd /usr/local/autotest/client/tests/kvm
>./get_started.py
>
>That will copy the .cfg.sample files to .cfg, so kvm autotest can
>actually get the conf files it needs.
>
>Now, you probably want to tweak your config files to generate a test
>set that is interesting to you, so take a look at the config files,
>specially tests.cfg to accomplish that.
>
>Cheers,
>
>Lucas

(Continue reading)

Group

gmane.linux.kernel.autotest.

Project Web Page

Autotest is a framework for automated testing designed primarily to test the Linux kernel and KVM virtualization ()

Search Archive

Page

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 27

Articles in period: 267

May 2012

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane

Recent entries

[Autotest] Some confuse about qemu: multi_disk: Disable qtree function (17 May 2013)
[Autotest] How to loop inside control file (17 May 2013)
[Autotest] Lucas Meneghel Rodrigues invited you to Autotest Weekly Han (16 May 2013)
[Autotest] Running secret tests (15 May 2013)
[Autotest] Using HDFS as an alternative for log storage (9 May 2013)
[Autotest] [RFC] User stories for the machine reservation system (9 May 2013)
[Autotest] Salam Sahajetra (5 May 2013)
[Autotest] [RFC] Implementing the tests/linux-tools directory (27 Apr 2013)
[Autotest] One question in migration test (25 Apr 2013)
[Autotest] Kit Cliente CPE Atheros 5GHz 150Mbps 1000mW AN 5.8 1T1R CPE (22 Apr 2013)
[Autotest] Distro Detection API (18 Apr 2013)
[Autotest] [PATCH] client.test:to check whether the self.debugdir_tmp_ (17 Apr 2013)
[Autotest] [RFC V3 PATCH 0/5] beaker harness support for autotest (12 Apr 2013)
[Autotest] Funding and Feature Request Management For Open Source (12 Apr 2013)
[Autotest] [PATCH] correct test_importer setting up test_type (8 Apr 2013)
[Autotest] [PATCH] documentation: update the CODING STYLE document (7 Apr 2013)
[Autotest] [RFC][Linux-Tools] Testcase for rootfiles (6 Apr 2013)
[Autotest] Autotest Sphinx-based Documentation infrastructure (4 Apr 2013)
[Autotest] [RFC PATCH 0/4] beaker harness support for autotest (2 Apr 2013)
[Autotest] [virt-test-devel][PATCH 0/4 V3] to add support for glusterf (2 Apr 2013)
[Autotest] [PATCH] [RFC] Introduce the autotest regression suite v3 (1 Apr 2013)

Archives

22	May 2013
52	April 2013
155	March 2013
140	February 2013
44	January 2013
131	December 2012
96	November 2012
129	October 2012
217	September 2012
467	August 2012
358	July 2012
285	June 2012
267	May 2012
133	April 2012
223	March 2012
219	February 2012
85	January 2012
112	December 2011
167	November 2011
33	October 2011
40	September 2011
75	August 2011
116	July 2011
175	June 2011
135	May 2011
150	April 2011
91	March 2011
126	February 2011
231	January 2011
257	December 2010
134	November 2010
172	October 2010
168	September 2010
100	August 2010
105	July 2010
193	June 2010
132	May 2010
170	April 2010
184	March 2010
183	February 2010
235	January 2010
69	December 2009

Design

Zawodny | Right Menu | Left Menu

Your Own Design

Paste the URL of your CSS below. Download CSS template