CrunchyData
Build PostgreSQL Operator on Power Linux
** Which example are you working with? ** I can build the operator on a RHEL7 x86_64. I can see the following images were generated in my box:
crunchydata/postgres-operator centos7-4.4.1 9194dc0b8bdb 22 hours ago 353MB
crunchydata/crunchy-postgres-exporter centos7-4.4.1 7570ab4bf893 22 hours ago 333MB
crunchydata/pgo-deployer centos7-4.4.1 011d805529db 22 hours ago 452MB
crunchydata/pgo-client centos7-4.4.1 3b9f31a94545 22 hours ago 330MB
crunchydata/pgo-sqlrunner centos7-4.4.1 6b6f286f4809 22 hours ago 347MB
crunchydata/pgo-scheduler centos7-4.4.1 24afb8b51595 22 hours ago 361MB
crunchydata/pgo-rmdata centos7-4.4.1 a658a43a8694 22 hours ago 290MB
crunchydata/pgo-event centos7-4.4.1 bb62b9fbabc2 22 hours ago 300MB
crunchydata/pgo-backrest-restore centos7-4.4.1 866e2f36a9fe 22 hours ago 325MB
crunchydata/pgo-backrest-repo-sync centos7-4.4.1 8b55ea098b4e 22 hours ago 378MB
crunchydata/pgo-backrest-repo centos7-4.4.1 0ddc48e70804 22 hours ago 284MB
crunchydata/pgo-backrest centos7-4.4.1 7f4bb06b9d0e 23 hours ago 357MB
crunchydata/pgo-apiserver centos7-4.4.1 7438f39ee07e 23 hours ago 349MB
crunchydata/pgo-base centos7-4.4.1 7f48d4457576 23 hours ago 252MB
What is the current behavior? Now I am trying to repeat the build steps on a Power Linux box. My objective is to estimate how many efforts are needed for building an operator on Power Linux. I can get the first image:
docker.io/crunchydata/pgo-base centos7-4.4.1 6831250e83c3 24 minutes ago 324 MB
In this image, the yum repositories are pointing to the crunchy repository. I can understand that the build script will install packages from the crunchy repository in the later image builds.
But I know that the crunchy repository does not have packages for Power Linux.
I have the following questions:
- Are the crunchy version of postgresql12 packages the same as the standard packages I can find in https://yum.postgresql.org?
- I guess I need to build
crunchy-backrest-xxxon Power Linux. But I did not find the github source code repository. - Are there other crunchy packages I need to prepare on the Power Linux?
Many thanks.
We do not support building the PostgreSQL Operator on Power Linux at this time. Internally, we have been evaluating building on Power Linux and would be happy to further discuss your use case if you are interested.
@jkatz Does closing the issue imply this feature is unwanted or should there be a separate RFE opened instead for tracking? (Just trying to get a little clarity on how crunchy does issue management and whether RFE discussions/implementations are expected to happen in public or via private email via the contact link)
@Fryguy I apologize for the confusion. I closed the ticket as building the Operator on Power Linux is not currently supported. If it makes sense, I'd be happy to keep the issue open. It would be helpful to understand the requirement - perhaps drop me an email ([email protected]) and we can discuss it further?
Thanks so much! Yeah, I think keeping it open as an enhancement request would be helpful (perhaps you can change the PR title).
It would be helpful to understand the requirement - perhaps drop me an email ([email protected]) and we can discuss it further?
I'd be happy to. Thanks!
Hi @renlei-bj!
With the release of PGO v5, we are now re-evaluating various GitHub issues, feature requests, etc. from previous PGO v4 releases. More specifically, in order to properly prioritize the features and fixes needed by our end-users for upcoming PGO v5 releases, we are now attempting to identify which PGO v4 issues, use cases, and enhancement requests are still valid (especially in the context of PGO v5).
Therefore, please let us know if you are still interested in having the enhancement described in this issue implemented in PGO v5
If so, you can either respond to this issue directly to ensure it remains open, or you can close this issue and submit a new one for PGO v5 (this would also be a great opportunity to include any updated details, context or any other information relevant to your issue). Otherwise, we will be closing this issue in the next 30 days.
If you are still running PGO v4, we recommend that you upgrade to PGO v5 as soon as possible to ensure you have the latest PGO features and functionality.
We aren't using the crunchydata operator (partly because this feature wasn't available), but I think this feature is still good for the community. I think having it available for a number of architectures is good.
Hi @Fryguy,
I just wanted to let you know we do have this in our backlog for a future enhancement.