Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

add support for Fedora secondary arches (ARM, powerpc) #71

Open
mozeq opened this issue Jun 13, 2013 · 10 comments
Open

add support for Fedora secondary arches (ARM, powerpc) #71

mozeq opened this issue Jun 13, 2013 · 10 comments

Comments

@mozeq
Copy link

mozeq commented Jun 13, 2013

dgilmore said that it's possible to get the HW which was the main problem why we didn't do it so far

@nirik
Copy link

nirik commented Aug 14, 2013

We can possibly get you access to hardware. :)

@mtoman
Copy link
Contributor

mtoman commented Aug 15, 2013

I can imagine two scenarios:

  1. The ARM machine as a "slave" to retrace01.qa.fedoraproject.org. This would require the ARM machine to be able to NFS mount retrace01.qa.fedoraproject.org and allow HTTP queries in both directions. On the other hand no public HTTP access would be required.

  2. The ARM machine as a standalone server. This would require a public HTTPS access with its own hostname (arm.retrace.fedoraproject.org?). The machine would also require a large (500GB+) & fast storage, as it has to install several mock chroots at the same moment as well as maintain its own copy of ARM repositories locally and run createrepo on them periodically (the performance of createrepo on ARM is not ideal).

I personally prefer n° 1, but whatever, we can live with both.

Note: Mentioning ARM as it is the priority ATM, the same applies to other archs.

@nirik
Copy link

nirik commented Aug 19, 2013

ok. I will ask our firewall/network admins what we can do here.

On option 1, would that be nfsv3 or nfsv4? (I ask because v4 is easier to deal with port wise), ie, what ports would you need open?

@mtoman
Copy link
Contributor

mtoman commented Aug 19, 2013

I'd like to avoid NFSv3 as much as possible, so I guess we agree on NFSv4.

@mtoman
Copy link
Contributor

mtoman commented Sep 9, 2013

Any update on this?

@nirik
Copy link

nirik commented Sep 9, 2013

Well, we are waiting on a firmware update for our server that will allow us to put this SOC on another uplink (so it's seperate from the others). That firmware is out now, but sadly, we are having problems getting it to apply. ;(
As soon as thats setup, I can setup a instance and we can adjust the firewall rules.
Sorry for the delay.

@nirik
Copy link

nirik commented May 9, 2014

Sorry for the massive delay here...

I've setup an arm soc at 10.5.78.11 running fedora 20 for your use.

Can you see if you can login via your retrace server and what ports you need open/config? Or catch me on irc and we can work on it realtime.

@mtoman
Copy link
Contributor

mtoman commented May 13, 2014

We need the following:
arm01 needs to be able to mount NFS running on retrace01 - port 2049
arm01 needs to be able to access postgres running on retrace01 - port 5432
retrace01 needs to be able to access httpd running on arm01 - port 80

@nirik
Copy link

nirik commented May 13, 2014

I've submitted a networking ticket to get these things opened. ;) Will keep you posted.

@nirik
Copy link

nirik commented May 27, 2014

ok, those things should be in place now. ;)

Please test and let me know if you need anything further.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants