[Fuego] Support for Squad

daniel.sangorrin at toshiba.co.jp daniel.sangorrin at toshiba.co.jp
Tue Jan 15 04:37:18 UTC 2019


> -----Original Message-----
> From: Tim.Bird at sony.com <Tim.Bird at sony.com>
> Sent: Saturday, January 12, 2019 7:46 AM
> > -----Original Message-----
> > From: fuego-bounces at lists.linuxfoundation.org [mailto:fuego-
> > bounces at lists.linuxfoundation.org] On Behalf Of Daniel Sangorrin
> >
> > Hi Tim,
> >
> > I have rebased my work to support Squad on top of Fuego v1.4.
> > Before it's too late I wanted to send it to you (the patches are on my repo as
> > well).
> >
> > [PATCH 2/2] ftc: implement put-run for squad
> > [PATCH 2/2] squad: add paramters for squad
> > Note: sorry about the patch numbering and mixing fuego and fuego-core
> > patches.
> >
> > The instructions to test these patches are on the latest fuego-core commit
> > (on my repo)
> > but I reproduce them below. I can add them to the wiki page later on. I
> > modified
> > some variables in fuego.conf as well that should be updated.
> >
> > The code is experimental, I have only tested it for Dhrystone and IOzone :D.
> > But it is a good start and I think that it is better to discuss some important
> > concepts early on.
> > For example, I think I need to add paramwters to the put-run interface
> > (team, project)
> > Also, I think that all these server-related functions should be implemented as
> > classes/objects.
> > Currently, I only added support for put-run but technically Squad can also
> > support other
> > functions such as put-request.
> > Other than that, in Squad the "job_id" needs to be unique to a "project". We
> > need to think
> > about how to do that if anyone in the team can submit jobs.
> > You can check my implementation and the comments I wrote there.
> >
> > Thanks,
> > Daniel
> >
> > Test instructions
> > =================
> >
> > Ref: https://squad.readthedocs.io (doc)
> >
> > Install server application
> > 	host$ sudo apt-get install rabbitmq-server
> > 		[Note] this is required for squad to communicate with celery
> > worker tasks
> > 	host$ git clone https://github.com/Linaro/squad
> > 	host$ cd squad/
> > 	host$ mkvirtualenv --python=python3  mysquad
> I get the following error at this step:
> 
> ---
> $ mkvirtualenv --python=python3 mysquad
> The executable /home/tbird/work/fuego/squad/python3 (from
> --python=/home/tbird/work/fuego/squad/python3) does not exist
> ---
> 
> I'm not sure how to fix this.
> I haven't worked with python virtual environments.
> There must be something simple I'm missing.
> Please help.

Assuming that you have python3 installed, it looks like virtualenv can't find your default python3 binary.
For example, in Ubuntu Xenial I have /usr/bin/python3 pointing to /usr/bin/python3.5.
Could you try changing --python=python3 to the version you are using (eg: --python=/usr/bin/python3.x)

If you prefer not to use a virtual environment you can install it on the host as well
https://squad.readthedocs.io/en/latest/quickstart.html

Another easy alternative is to install squad directly from pip3:
https://squad.readthedocs.io/en/latest/install.html
$ mkvirtualenv --python=python3.5 pipsquad
(squadpip) pip3 install squad
(squadpip) squad

Thanks,
Daniel






More information about the Fuego mailing list