Seeing the centos support for the Raspberry Pi is what got me to go a head and by the new Pi3. However, is there an estimated date when it will be ready to be used for servers with all the packages?
I am currently running ownCloud (Nginx + php + MariaDB) on RPi2 with Fedora 23 it runs smooth with no issues at all but I don't want the bleeding edge tools and the frequent updates and would love to go back to CentOS.
Love the work you guys do.
On 20/04/16 19:09, Fahad wrote:
Seeing the centos support for the Raspberry Pi is what got me to go a head and by the new Pi3. However, is there an estimated date when it will be ready to be used for servers with all the packages?
I am currently running ownCloud (Nginx + php + MariaDB) on RPi2 with Fedora 23 it runs smooth with no issues at all but I don't want the bleeding edge tools and the frequent updates and would love to go back to CentOS.
Love the work you guys do.
Hi,
Well, in your specific example, some pkgs aren't coming from [base] : nginx isn't provided by CentOS, but through EPEL for "normal" arch like x86_64.
As there is *no* armhfp support at the EPEL level, we tested a massive rebuild and I see that nginx built successfully : http://armv7.dev.centos.org/repodir/epel-pass-1/nginx/1.6.3-8.el7/armv7hl/ (please note that those pkgs aren't signed at all, but still available publicly for your convenience : http://armv7.dev.centos.org/repodir/epel-pass-1/ )
php and mariadb are already available in [base]/[updates]
What else are you searching for ?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 21/04/16 12:30, Fabian Arrotin wrote:
As there is *no* armhfp support at the EPEL level, we tested a massive rebuild and I see that nginx built successfully : http://armv7.dev.centos.org/repodir/epel-pass-1/nginx/1.6.3-8.el7/armv
7hl/
(please note that those pkgs aren't signed at all, but still available
publicly for your convenience : http://armv7.dev.centos.org/repodir/epel-pass-1/ )
this looks pretty good, do we know what the EPEL plans for arm32 are at this point ? if not, do we want to invest some time and just setup a downstream branch on our end ( and if so, can we just add that as a repo to our images )
- -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
On 04/21/2016 07:30 AM, Fabian Arrotin wrote:
As there is *no* armhfp support at the EPEL level, we tested a massive rebuild and I see that nginx built successfully : http://armv7.dev.centos.org/repodir/epel-pass-1/nginx/1.6.3-8.el7/armv7hl/ (please note that those pkgs aren't signed at all, but still available publicly for your convenience : http://armv7.dev.centos.org/repodir/epel-pass-1/ ) php and mariadb are already available in [base]/[updates] What else are you searching for ?
Well, I'm not the OP, but after several aborted attempts at building GNUradio from source on the ODroid C2, I'd like to ask if there is an equivalent for ARMv8 to this, or, for that matter, where EPEL on Aarch64 stands. And I know this is an EPEL question, but, honestly, CentOS' usefulness is really tied to the availability of the third-party repos, and EPEL is the biggest.
(GNUradio has some modules that require more than 2GB Virt to compile (verified with a CentOS 7 x86_64 machine with only 2GB of RAM that took 4 hours to build from source, and half of that time was spent thrashing on two files with a load average > 25), and the install I currently am working with is swapless, and the C2 only has 2GB of RAM; I'm looking at the feasibility/advisability of swap on microSD or eMMC. The build panics the kernel at the first of those files).
On 04/22/2016 11:34 AM, Lamar Owen wrote:
Well, I'm not the OP, but after several aborted attempts at building GNUradio from source on the ODroid C2, I'd like to ask if there is an equivalent for ARMv8 to this, or, for that matter, where EPEL on Aarch64 stands. And I know this is an EPEL question, but, honestly, CentOS' usefulness is really tied to the availability of the third-party repos, and EPEL is the biggest.
We've been working with the Fedora folks to try to get an EPEL build for AArch64 for some time now. I believe it's still a few months out from being 'official', but we can see about doing an interim build for epel and producing a temporary epel build repo that can be transitioned to 'official'.
(GNUradio has some modules that require more than 2GB Virt to compile (verified with a CentOS 7 x86_64 machine with only 2GB of RAM that took 4 hours to build from source, and half of that time was spent thrashing on two files with a load average > 25), and the install I currently am working with is swapless, and the C2 only has 2GB of RAM; I'm looking at the feasibility/advisability of swap on microSD or eMMC. The build panics the kernel at the first of those files)
Our builders have 8-16GB of ram, so shouldn't be an issue. I know one 'mad scientist' type who used swap over iscsi for his initial arm build on the odroid-c1 a few months back.
On 04/26/2016 09:57 AM, Jim Perrin wrote:
We've been working with the Fedora folks to try to get an EPEL build for AArch64 for some time now. I believe it's still a few months out from being 'official', but we can see about doing an interim build for epel and producing a temporary epel build repo that can be transitioned to 'official'.
... Our builders have 8-16GB of ram, so shouldn't be an issue. I know one 'mad scientist' type who used swap over iscsi for his initial arm build on the odroid-c1 a few months back.
Thanks, Jim. I did get GNURadio to build, by putting 4GB of swap on the eMMC. Although swap on iscsi sounds cool, and is definitely creative!
C7 with 4GB of swap feels much more responsive, even when not heavily loaded, for some reason. I'm just needing to get some of the GUI pieces of EPEL built (wxPython and its deps, for one) before I can go to production with these little devices (targeted to be RFI sniffers for a radio astronomy observatory using the cheap RTL-SDR dongles made by outfits like Nooelec).
On 2016-04-27 00:51, Lamar Owen wrote:
On 04/26/2016 09:57 AM, Jim Perrin wrote:
We've been working with the Fedora folks to try to get an EPEL build for AArch64 for some time now. I believe it's still a few months out from being 'official', but we can see about doing an interim build for epel and producing a temporary epel build repo that can be transitioned to 'official'.
... Our builders have 8-16GB of ram, so shouldn't be an issue. I know one 'mad scientist' type who used swap over iscsi for his initial arm build on the odroid-c1 a few months back.
Thanks, Jim. I did get GNURadio to build, by putting 4GB of swap on the eMMC. Although swap on iscsi sounds cool, and is definitely creative!
Swapping to a file over NFS has been supported for decades. That's what I had to do when building RedSleeve EL6 on machines that all had ~ 500MB of RAM.
Unfortunately, building on NFS was causing spurious build failures due to self-tests on some of the packages, but 5 years ago there weren't any alternatives.
Gordan
once upon a time, when started armhfp bootstrapping for f15, i had only ac100 with 512m. lot of builds failed due small swap on emmc. problems gone when i used usb drive and moved there whole root and created big enough swap.
anyway using emmc for swap is not good idea from long-term perspective
----- Original Message ----- From: "Lamar Owen" lowen@pari.edu To: "Conversations around CentOS on ARM hardware" arm-dev@centos.org Sent: Wednesday, April 27, 2016 1:51:14 AM Subject: Re: [Arm-dev] Server ready
On 04/26/2016 09:57 AM, Jim Perrin wrote:
We've been working with the Fedora folks to try to get an EPEL build for AArch64 for some time now. I believe it's still a few months out from being 'official', but we can see about doing an interim build for epel and producing a temporary epel build repo that can be transitioned to 'official'.
... Our builders have 8-16GB of ram, so shouldn't be an issue. I know one 'mad scientist' type who used swap over iscsi for his initial arm build on the odroid-c1 a few months back.
Thanks, Jim. I did get GNURadio to build, by putting 4GB of swap on the eMMC. Although swap on iscsi sounds cool, and is definitely creative!
C7 with 4GB of swap feels much more responsive, even when not heavily loaded, for some reason. I'm just needing to get some of the GUI pieces of EPEL built (wxPython and its deps, for one) before I can go to production with these little devices (targeted to be RFI sniffers for a radio astronomy observatory using the cheap RTL-SDR dongles made by outfits like Nooelec).
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
On 04/27/2016 05:57 AM, Jiri Kastner wrote:
once upon a time, when started armhfp bootstrapping for f15, i had only ac100 with 512m. lot of builds failed due small swap on emmc. problems gone when i used usb drive and moved there whole root and created big enough swap.
anyway using emmc for swap is not good idea from long-term perspective
Right; nor is it good on microSD (same basic technology as eMMC). I'd rather have either a nice SSD or a USB hard disk, but for the build it's ok. I'm not planning on swap on eMMC for the production deployment, just for development/building.
Thanks Fabian,
But my question was mainly about when should I expect a reliable arm/arm64 repos that I can trust to use as a production server and expect security updates to come in a timely manner as the normal CentOS x86/x86_64? Is ARM support something CentOS is targeting or just as a side project when time is available?
BTW, the URL http://armv7.dev.centos.org/repodir/epel-pass-1/ is down at the moment of writing this email.
On Thu, Apr 21, 2016 at 7:30 AM, Fabian Arrotin arrfab@centos.org wrote:
On 20/04/16 19:09, Fahad wrote:
Seeing the centos support for the Raspberry Pi is what got me to go a head and by the new Pi3. However, is there an estimated date when it will be ready to be used for servers with all the packages?
I am currently running ownCloud (Nginx + php + MariaDB) on RPi2 with Fedora 23 it runs smooth with no issues at all but I don't want the bleeding edge tools and the frequent updates and would love to go back to CentOS.
Love the work you guys do.
Hi,
Well, in your specific example, some pkgs aren't coming from [base] : nginx isn't provided by CentOS, but through EPEL for "normal" arch like x86_64.
As there is *no* armhfp support at the EPEL level, we tested a massive rebuild and I see that nginx built successfully : http://armv7.dev.centos.org/repodir/epel-pass-1/nginx/1.6.3-8.el7/armv7hl/ (please note that those pkgs aren't signed at all, but still available publicly for your convenience : http://armv7.dev.centos.org/repodir/epel-pass-1/ )
php and mariadb are already available in [base]/[updates]
What else are you searching for ?
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
On 26/04/16 16:39, Fahad wrote:
Thanks Fabian,
But my question was mainly about when should I expect a reliable arm/arm64 repos that I can trust to use as a production server and expect security updates to come in a timely manner as the normal CentOS x86/x86_64? Is ARM support something CentOS is targeting or just as a side project when time is available?
BTW, the URL http://armv7.dev.centos.org/repodir/epel-pass-1/ is down at the moment of writing this email.
So, arm/arm64 (armhfp/aarch64) are released and maintained. While on the armhfp side we weren't able to build everything, at least everthing that was built/released/signed/pushed to mirror.centos.org is maintained (see for example the updates for armhfp/CentOS 7.21511 : http://mirror.centos.org/altarch/7/updates/armhfp/Packages/?C=M;O=D)
WRT to armv7.dev.centos.org, it was announced that we had to reorganize several physical nodes in a rack, and yes, that node was impacted (see https://lists.centos.org/pipermail/centos-announce/2016-April/021836.html) but is now back online. One goal behind that maintenance window is that we'll implement (in the following days) some mechanism to automatically submit build jobs for updates pkgs at the same time as for the other arches (while x86_64 is obviously the authoritative one). Actually aarch64 was added in the last weeks and we'll now add armhfp to the same process (as it was done "semi" automated until now)
I hope that this answers your questions :-)
On 2016-04-27 15:36, Fabian Arrotin wrote:
On 26/04/16 16:39, Fahad wrote:
Thanks Fabian,
But my question was mainly about when should I expect a reliable arm/arm64 repos that I can trust to use as a production server and expect security updates to come in a timely manner as the normal CentOS x86/x86_64? Is ARM support something CentOS is targeting or just as a side project when time is available?
BTW, the URL http://armv7.dev.centos.org/repodir/epel-pass-1/ is down at the moment of writing this email.
So, arm/arm64 (armhfp/aarch64) are released and maintained. While on the armhfp side we weren't able to build everything, at least everthing that was built/released/signed/pushed to mirror.centos.org is maintained (see for example the updates for armhfp/CentOS 7.21511 : http://mirror.centos.org/altarch/7/updates/armhfp/Packages/?C=M;O=D)
What exactly weren't you able to build? Over at RS we were able to get everything in EL7 to build for armv5tel so it seems unlikely that any build failures on armv7hl are insurmountable.
Gordan
-
Fabian Arrotin -
Fahad -
Gordan Bobic -
Jim Perrin -
Jiri Kastner -
Karanbir Singh -
Lamar Owen