#1203 RFR: x86_64 host for composing spins
Closed: Fixed None Opened 11 years ago by kanarip.

I guess this is an enhancement request... ;-)

The Spins SIG would appreciate a host on which i386 and x86_64 spins (by Spin SIG members or persons to be appointed) can be composed frequently. The os version doesn't really matter, as long as it is Fedora (cross-composing is perfectly feasible). We would require the capability to send out notification mails of builds failing, though.


I think this is an RFR request. Is this related to work releng is doing or completely separate?

Also, who's the target audience, how much storage will it need, who's going to use it, what kind of security will it need, etc, etc.

Replying to [comment:2 mmcgrath]:

Is this related to work releng is doing or completely separate?

I don't know what rel-eng is doing. I vaguely recall a conversation about the Spins SIG being able to use (some of) rel-eng's resources but I never got any actual access.

Replying to [comment:3 mmcgrath]:

Also, who's the target audience, how much storage will it need, who's going to use it, what kind of security will it need, etc, etc.

  1. Target audience is the members of the Spins SIG
  2. Storage for at least one spin at a time (5GB for a product, another chunk of similar size for the rpm cache, a few MB for the log files)
  3. The Spins SIG is going to use it to produce log-files on rawhide spins composed on an environment as close to the environment rel-eng uses as possible, to prevent rel-eng from being handed garbage when it's time for them to use the kickstarts composed and maintained by the Spins SIG & spin maintainers.
  4. Security: SELinux in permissive mode, sudo privileges to perform composes (exact list of commands to be determined).

K, I'll get to work on this soon. At present all of our PHX hosts are having a bug preventing us from installing Fedora on them. We're looking into it.

/me notes from IRC meeting: we'll need another group for this, spinners or something.

Ok, sorry for the wait this should be done. Directions to access:

ssh bastion.fedoraproject.org

from there ssh to spin1

The group (kanarip is the admin) is sysadmin-spin. I'd recommend proxycommand in ~/.ssh/config:

{{{
Host spin1
ProxyCommand ssh -A bastion.fedoraproject.org nc spin1 22
}}}

Login to comment on this ticket.

Metadata