1212259 - delivery: set up upload hosts for seamonkey

Status: RESOLVED FIXED

(Cloud Services :: Operations: Miscellaneous, task)

Description

[Nick Thomas [:nthomas] (UTC+12)]

That is, upload.seabld.productdelivery.{stage,prod}.mozaws.net, talking to the archive bucket IIRC. Relatively low traffic so doesn't need to be beefy instances.

Callek, could you please confirm seabld is the account in ldap to pull the ssh public key from. Thanks.

Comment 1

[Jeremy Orem [:oremj]]

Yes, can you please attach your current authorized_keys file to this bug. Thanks.

Comment 2

[Justin Wood (:Callek)]

Attachment: authorized_keys

Comment 3

[Justin Wood (:Callek)]

Attachment: authorized_keys2

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

Bumping up priority, SeaMonkey is scheduled to migrated 17 Nov.

Comment 5

[Jeremy Orem [:oremj]]

The servers are up.

PROD: upload.seabld.productdelivery.prod.mozaws.net
STAGE: upload.seabld.productdelivery.stage.mozaws.net

Comment 6

[Edmund Wong (:ewong)]

(In reply to Jeremy Orem [:oremj] from comment #5)
> The servers are up.
> 
> PROD: upload.seabld.productdelivery.prod.mozaws.net
> STAGE: upload.seabld.productdelivery.stage.mozaws.net

out of curiosity,  do we need something like /builds/release-s3.credentials ?

Comment 7

[Nick Thomas [:nthomas] (UTC+12)]

Yes, if you are going to use the new push to mirrors, antivirus or checksums scripts in http://hg.mozilla.org/mozilla-central/file/default/testing/mozharness/scripts/release/.