---------- Forwarded message ----------
From: Steve McIntyre <steve.mcintyre(a)linaro.org>
Date: 31 May 2016 at 16:46
Subject: Re: pipeline vland help
To: Christian Ziethén <christian.ziethen(a)linaro.org>
Cc: neil.williams(a)linaro.org
On Tue, May 31, 2016 at 03:29:45PM +0200, Christian Ziethén wrote:
>Hi,
Hi Christian,
You'd be much better asking on the lava-users mailing list rather than
just directly to me, I'll be honest.
>Been struggling with setting up a vland between two arndale targets. I have
>managed to create a multinode job that uses the pipeline model:
>https://lng.validation.linaro.org/scheduler/job/9702/multinode_definition
>Have also managed to create valid yaml that seems to conform to the code in
>lava-server/lava_scheduler_app/schema.py
>https://lng.validation.linaro.org/scheduler/job/9743/multinode_definition
>This one does however not do anything after being submitted, I tried
putting
>100M in the tags for the vland, I also tried requiring that the arndale
targets
>in the multinode protocol had the 100M tag, but that didn't work.
According to
>the device dictionary for lng-arndale-01, it should have a 100M tag on
iface1.
Hmmm, OK. I can see that it's sat waiting for devices to be
assigned. Looking at the definition, you've got one group (role)
defined with 2 entries. I believe that for VLANd jobs you need to have
individual roles for each machine. Neil can confirm.
>Also have this job (v1):
>https://lng.validation.linaro.org/scheduler/job/9118/multinode_definition
>Which runs my test using iface1 (I think) but it doesn't use vland.
Right, v1 doesn't do vland.
>I am unsure how to debug this.
>
>It was my assumption that I could create a vlan with the vland protocol and
>then query which interface is on that vlan in my test-definition. That
would be
>my end goal for this exercise.
Sure, that's what we expect to have working for you.
Cheers,
--
Steve McIntyre steve.mcintyre(a)linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
Hi,
For the last couple of days I’ve been trying to setup a device in our lab for deployment and installation of a Linux OS.
However, I’ve came across a few issues and lots of questions and hopefully I can get some answers here.
Considerations:
1. I’ve decided to give it a go with LAVA v2 and try using the pipeline model
2. I’m not testing any “boards”, so it’s hard to find a similar example
3. I am not deploying any Linaro images (not even debian based)
4. My team develops and supports a reference Linux OS, based on RHEL, so that means we have total control of our images, kickstarter scripts, etc.
5. We already have a PXE server in our network, which is where our servers (the targets in this context) get booted from by default
6. Once booted from PXE, we get a PXE menu, where we can either select an option, or press ESC and add a custom command (at this syslinux is running)
7. We have access to the serial console of every device via serial port server (telnet <ipaddr> <port>)
8. We have power control over every device via IPMI
Issues:
1. I couldn’t find the documentation for how to add devices and device types to the server (which location to add the file, which format - yaml/conf)
2. In the above described environment, I suppose we would skip the deployment phase, since the devices already boot into syslinux from PXE (is this correct?). Either way, it would be nice to be able to run ‘ipmitool chassis booted pxe’ before rebooting the system.
3. Either way (via boot or deploy), how can I make sure to detect the PXE (syslinux) menu, send the ESC key, and send the command I need to trigger the kickstart installation?
To sum-up, the Workflow I’m trying to achieve after having completed the whole setup sort of goes like this:
1. Reboot target device into PXE (the PXE itself will download and start syslinux here)
2. Wait for PXE menu (expect some sort of string)
3. Send ESC key (to get into the boot shell)
4. Send command (this will trigger our kickstarter script and the installation will take around 5 minutes). The images that are needed are fetched automatically from our sftp server.
5. Wait for boot prompt after system installation succeeds
6. Login using credentials (username, password)
7. Run whatever tests we need from here
Any help here would be much appreciated.
Thanks in advance!
--
matallui
Hello,
I just started to set up a lava server to test custom devices and I've some questions about testing custom or third party boards.
Does someone know a good documentation or tutorial for the integration of custom boards? It seems that there isn't much documented for this topic.
Is there any documentation for setting up a custom device configuration file and the commands that can be used, like client_type?
Thank you and best regards
Stefan
[cid:b073c64a8131462290b626cc30430be3]<http://www.facebook.com/WagoKontakttechnik> [cid:00cd0405ac4344fbb39caf677313ca6c] <http://www.youtube.com/WagoKontakttechnik> [cid:3139f430e8f940bb956be9ff06d8d5c2] <https://www.xing.com/companies/wagokontakttechnikgmbh&co.kg> [cid:614f801bb8f64c1d8a9dbfd711f2a29a] <http://twitter.com/WAGOKontakttech> [cid:69804606bdd6406aa66c78bf7dae6c2a] <http://www.linkedin.com/company/wago-kontakttechnik>
[cid:711e500a31984a6a959819fb46ba7f2d]
________________________________________________________________________________________
Diese E-Mail einschlie?lich ihrer Anh?nge ist vertraulich und daher allein f?r den Gebrauch durch den vorgesehenen Empf?nger bestimmt. Dritten ist das Lesen, Verteilen oder Weiterleiten dieser E-Mail sowie jedwedes Vertrauen auf deren Inhalt untersagt. Wir bitten, eine fehlgeleitete E-Mail unverz?glich vollst?ndig zu l?schen und uns eine Nachricht zukommen zu lassen.
This email may contain material that is confidential and/or privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
WAGO Kontakttechnik GmbH (nach Schweizer Recht) & Co. KG; Rechtsform: Kommanditgesellschaft; Sitz: Minden; Registergericht: Bad Oeynhausen, HRA 6218; Pers?nlich haftender Gesellschafter: WAGO Kontakttechnik Beteiligungs GmbH; Sitz: Domdidier (Schweiz); Handelsregisteramt CH-217-3533291-9; Gesch?ftsf?hrung: Dipl.-Wirtsch. Ing. (FH) Sven Michael Hohorst; Dipl. Betriebsw. Axel Christian B?rner; Dipl.-Ing. (FH) Ulrich Bohling.
