New issue
Advanced search Search tips

Issue 921263 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Feature

Blocking:
issue 920393



Sign in to add a comment

Deploy `skylab` tool on builders

Project Member Reported by pprabhu@chromium.org, Jan 12

Issue description

We want the `skylab` tool deployed on the Chrome OS builders via cipd.
This tool will be used to trigger skylab test and suite tasks from builders.
 
Blocking: 920393
Labels: -Type-Bug Type-Feature
Cc: jclinton@google.com fried...@google.com
+friedman who's helped us setup builder environment in the past.
+jclinton this week's CI on-call to assist.

cipd package that cbuildbot wants to use: 
  chromiumos/infra/skylab/${platform}
I _think_ ${platform} for our builders is linux-amd64

We'd like the builders to always (or as often refreshed as possible) use the `latest` version of the package.

I'm not sure what is the recommended way to get CIPD dependencies on our builders at this point.
We haven't deployed any new CIPD packages to builders since taking over last April.
Is there a swarming query that will show me all your builders?

Where do you want the package installed?
Re #5 --> jclinton to list all builders.

We don't care where they're installed as long as cbuildbot can use them. Is there a default cipd installation on the builders that is in $PATH ?
Cc: dgarrett@google.com
Don can answer questions about builders way better than I can.
Cc: -dgarrett@google.com mikenichols@google.com
Don redirected met to mikenichols@ to get information about CrOS build fleet and package installation.
A general note.

CIPD packages aren't normally installed on builders, instead they are refetched every build based on hash or tag. The cipd tool caches locally to make this efficient. This approach means nothing new would be installed on the builder.

I'm not sure if cbuildbot is currently doing this for any other tools, but we probably should be.

Comment 10 by pprabhu@chromium.org, Jan 17 (5 days ago)

Cc: pprabhu@chromium.org
Owner: mikenichols@chromium.org
ping...
can we get a way to list all buildslaves to deploy this package to?

Comment 11 by jclinton@chromium.org, Jan 17 (5 days ago)

I don't understand the question: wouldn't it be every bot in the Swarming configuration that isn't a Skylab bot? Didn't you create the Skylab Test Swarming configuration in that same file? Are you intending to ask the Puppet team to prefetch these? Or are you thinking of modifying the Recipe to fetch it?

Comment 12 by mikenichols@chromium.org, Jan 17 (5 days ago)

Since Skylab is configured under chromeos-swarming, whereas CrOS is under chrome-swarming, this should be a case of adding it to all CrOS bots.  

We have cipd packages  being installed as part of the Puppet manifest.  That might be the simplest approach.  The other option would be as part of the swarming config itself.  

Sorry, I've been focused on a few production issues.  I'll take a look at this as soon as I can.  

-- Mike 

Comment 13 by pprabhu@chromium.org, Jan 18 (4 days ago)

Re #11, as Mike mentioned, this ask is to add a cipd package to the CrOS builder fleet (not the skylab bot fleet).

Yes, I'd like this cipd package to be added to the puppet manifest for our builders. 

Comment 14 by jclinton@chromium.org, Jan 18 (4 days ago)

Components: Infra>Puppet
Owner: d...@chromium.org
Puppet requests are filed with the ChOps sysadmin team. dba@ is the current primary. Bryce, can you help Prathmesh with his request?

Comment 15 by fried...@google.com, Jan 18 (4 days ago)

The current style of doing this is to not pre-configure the bots, but to have the jobs configure them as necessary.  This would mean modifying your tests to run the cipd commands to pull skylab or whatever else is needed for that job to run during the test.

Comment 16 by jclinton@chromium.org, Jan 18 (4 days ago)

Components: -Infra>Puppet -Infra>ChromeOS>CI>Platform
Owner: pprabhu@chromium.org
Thanks. In that case, Prathmesh, you'll just need to add it to one of the Test team's HW Tests build stages.

Sign in to add a comment