Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support for non-x86 ? #6871

Closed
timothysc opened this issue Nov 18, 2016 · 8 comments
Closed

support for non-x86 ? #6871

timothysc opened this issue Nov 18, 2016 · 8 comments

Comments

@timothysc
Copy link

Allow support for non-x86 arches where golang is supported.

Do you have any official policy on this?

@xiang90
Copy link
Contributor

xiang90 commented Nov 18, 2016

@timothysc
Copy link
Author

Should it be marked as unsupported then? xref: https://bugzilla.redhat.com/show_bug.cgi?id=1396463

@xiang90
Copy link
Contributor

xiang90 commented Nov 18, 2016

@timothysc We only mark supported since we only support amd64, all others are unsupported. Once we support the majority, we will do the opposite...

@xiang90
Copy link
Contributor

xiang90 commented Nov 23, 2016

It seems the questions is addressed. I am closing this out. Reopen if you have any followup questions.

@xiang90 xiang90 closed this as completed Nov 23, 2016
@houstar
Copy link

houstar commented Jan 6, 2017

Error log in ppc64le. golang is currently supported on ppc64le. so I think we should strict/limited support x86/amd64 only. I strongly suggest that we should enable other platform to embrace the CoreOS eco-system. Now we're testing the CoreOS@ppc64le platform.

core@CoreOS ~ $ cat /etc/os-release
NAME=CoreOS
ID=coreos
VERSION=1248.0.0
VERSION_ID=1248.0.0
BUILD_ID=2017-01-06-1749
PRETTY_NAME="CoreOS 1248.0.0 (Ladybug)"
ANSI_COLOR="1;32"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"
core@CoreOS ~ $ uname -a
Linux CoreOS 4.9.0-coreos #1 SMP Thu Dec 29 06:43:17 2016 ppc64le POWER8E (raw), altivec supported CHRP IBM pSeries (emulated by qemu) GNU/Linux

Attached the ppc64le log in the following.

Jan 06 19:10:40 CoreOS systemd[1]: etcd2.service: Service hold-off time over, scheduling restart.
Jan 06 19:10:40 CoreOS systemd[1]: Stopped etcd2.
-- Subject: Unit etcd2.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit etcd2.service has finished shutting down.
Jan 06 19:10:40 CoreOS systemd[1]: Starting etcd2...
-- Subject: Unit etcd2.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit etcd2.service has begun starting up.
Jan 06 19:10:40 CoreOS etcd2[3830]: etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=ppc64le set.
Jan 06 19:10:40 CoreOS systemd[1]: etcd2.service: Main process exited, code=exited, status=1/FAILURE
Jan 06 19:10:40 CoreOS systemd[1]: Failed to start etcd2.
-- Subject: Unit etcd2.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit etcd2.service has failed.

-- The result is failed.
Jan 06 19:10:40 CoreOS systemd[1]: etcd2.service: Unit entered failed state.
Jan 06 19:10:40 CoreOS systemd[1]: etcd2.service: Failed with result 'exit-code'.

@houstar
Copy link

houstar commented Jan 6, 2017

@marineam @xiang90 Could we support etcd on ppc64le platform ? As you known, we've enabled CoreOS @ppc64le platform. And etcd is the infrastructure for CoreOS...Sooooooo... thanks

@heyitsanthony
Copy link
Contributor

heyitsanthony commented Jan 6, 2017

@houstar set the environment variable ETCD_UNSUPPORTED_ARCH=ppc64le. This flag won't go away until there's ppc64le CI; the platform is not well tested and so running etcd is risky. See https://github.com/coreos/etcd/blob/master/Documentation/op-guide/supported-platform.md#supporting-a-new-platform

@houstar
Copy link

houstar commented Jan 6, 2017

Thanks @heyitsanthony, so i'll take the responsibility of testing etcd on ppc64le. Once is stable enough. then i'll inform here ;-0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants