Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

ppc64le: Get public repos available via OBS. #118

Closed
nitkon opened this issue Aug 1, 2018 · 20 comments
Closed

ppc64le: Get public repos available via OBS. #118

nitkon opened this issue Aug 1, 2018 · 20 comments
Labels
high-priority Very urgent issue (resolve quickly)

Comments

@nitkon
Copy link
Contributor

nitkon commented Aug 1, 2018

Public repos from OBS for CentOS, Fedora, Red Hat and Ubuntu for x86 are available here

Make the same available for ppc64le as well.
OBS support for ppc64le is availble: https://build.opensuse.org/monitor

More info in this comment: #102 (comment)

@nitkon
Copy link
Contributor Author

nitkon commented Aug 1, 2018

@erick0z @jcvenegas: Is there anything on the OBS side, like a check-box or something that needs to be ticked to run OBS builds on ppc64le and then see what breaks?

@jodh-intel
Copy link
Contributor

Hi @nitkon - I think I answered that question here if you read it carefully: #102 (comment)

@nitkon
Copy link
Contributor Author

nitkon commented Aug 1, 2018

#...../packaging/obs-packaging# osc co home:katacontainers:release
Server returned an error: HTTP Error 401: Unauthorized

Let me look into osc command line documentation and authorization modules.

@nitkon
Copy link
Contributor Author

nitkon commented Aug 1, 2018

I have added ppc64le in the tag.

#......../packaging/obs-packaging/home:katacontainers:release# osc meta prj -e
Sending meta data...
BuildService API error: change_project_no_permission (403)
no permission to change project
Try again? ([y/N]): y
Sending meta data...
BuildService API error: change_project_no_permission (403)
no permission to change project
Try again? ([y/N]): 

@jodh-intel
Copy link
Contributor

Hi @nitkon - what's your obs user called?

Hi @jcvenegas - please could you add @nitkon to the OBS project once we know his username?

@nitkon
Copy link
Contributor Author

nitkon commented Aug 1, 2018

Hi @jodh-intel , my obs user is called "nitkon"

osc whois
nitkon: "Nitesh Konkar" <xxx@gmail.com>

@nitkon
Copy link
Contributor Author

nitkon commented Aug 3, 2018

@jcvenegas , ping!

@nitkon
Copy link
Contributor Author

nitkon commented Aug 6, 2018

@jodh-intel : Is there anyone else who can add me to the OBS project?

@jodh-intel
Copy link
Contributor

Hi @nitkon - I think if you "request role addition" on this page, it will get routed to the right person:

@nitkon
Copy link
Contributor Author

nitkon commented Aug 7, 2018

@jodh-intel : Done! Thanks.

@nitkon
Copy link
Contributor Author

nitkon commented Aug 8, 2018

@jcvenegas : I have requested addition on the page mentioned by @jodh-intel , Can you please do the needful if you have the apt rights to do it.

@nitkon
Copy link
Contributor Author

nitkon commented Aug 12, 2018

Request 627825 (new) still in new state, who is the right person to contact?
Created the request here: https://build.opensuse.org/project/show/home:katacontainers:release

@jcvenegas
Copy link
Member

@nitkon hey sorry my mail is missing some notifications. I will add you today.

Meanwhile, somethink I dont like but we do in the OBS repos is that when build kata we upload a golang tarball to ensure we use the same golang version in all the distros. But the golang version is for x86_64 so adding more architectures to build will requeire to upload more tarballs or remove that tarball depedency..

In order to upload the rigth golang version I was thinking to create multiple github subprojects. Like:

https://build.opensuse.org/project/show/home:katacontainers:releases:x86_64:1.2.0

Does it make sense or you prefer to upload all the golang tarballs to the same project and at build time what tarball install? Or remove that tarball dependency.

@jcvenegas
Copy link
Member

So for initial work I grant you access to our "testing repo"

https://build.opensuse.org/project/show/home:katacontainers:alpha

Feel free to upload and modify all you want here, there is not problem if you break the build.

After we are ready we can move to release.

@nitkon
Copy link
Contributor Author

nitkon commented Aug 17, 2018

Hi @jcvenegas ,
I am ok with having a separate repository for ppc64le, something like https://build.opensuse.org/project/show/home:katacontainers:releases:ppc64le:1.2.0

@nitkon
Copy link
Contributor Author

nitkon commented May 16, 2019

Update on latest status on building packages in OBS for ppc64le is as follows:

  1. kata-containers/packaging/obs-packaging# ARCH=ppc64le bash -x ./create-repo-branch.sh 1.7.0-rc1
  2. kata-containers/packaging/obs-packaging# PUSH=1 OBS_SUBPROJECT="alpha:ppc64le:1.7.0-rc1" bash -x ./build_from_docker.sh 1.7.0-rc1

======= Updating runtime =======
/usr/local/go/bin/go
INFO: requires:
INFO: proxy 1.7.0~rc1+git.c5c4bc3-2
INFO: shim 1.7.0~rc1+git.d2c94a0-2
INFO: kata-linux-container 4.19.28.22-2
INFO: ksm-throttler 1.7.0~rc1+git.11b4625-2
INFO: image 1.7.0~rc1-2
Server returned an error: HTTP Error 404: Not Found
Error getting meta for project 'home%3Akatacontainers%3Aalpha%3Appc64le%3A1.7.0-rc1' package 'qemu-lite'
home:katacontainers:alpha:ppc64le:1.7.0-rc1/qemu-lite
ERROR: failed to checkout:makeurl: https://api.opensuse.org ['source', 'home%3Akatacontainers%3Aalpha%3Appc64le%3A1.7.0-rc1', 'qemu-lite', '_meta'] {}
root@kata1:/home/nitesh/split_patch/src/github.com/kata-containers/packaging/obs-packaging# grep -irwn "qemu-lite" *

Results: https://build.opensuse.org/project/show/home:katacontainers:alpha:ppc64le:1.7.0-rc1

Edit: linux-container fail is due to

[   77s] + BuildKernel
[   77s] ++ ./kata-multiarch.sh -a ppc64le
[   77s] + local kernelArch=powerpc
[   77s] + ExtraVer=-2.1.container
[   77s] + perl -p -i -e 's/^EXTRAVERSION.*/EXTRAVERSION = -2.1.container/' Makefile
[   77s] + make -s mrproper
[   83s] + rm -f .config
[   83s] + find kata-kernel-configs -name 'powerpc_kata_kvm_*' -exec cp '{}' .config ';'
[   83s] + '[' -f .config ']'
[   83s] + echo 'ERROR: cannot find the kernel config file for the powerpc architecture'
[   83s] ERROR: cannot find the kernel config file for the powerpc architecture

cc @jodh-intel @jcvenegas @marcov

@marcov
Copy link
Contributor

marcov commented May 16, 2019

hi @nitkon

  • the first error with the runtime, looks like it is expecting to find a qemu-lite package in your OBS project. You need to figure out who and why it is doing it.

  • linux-container fail it's because the config files tarball you uploaded on OBS is incomplete.
    Make sure your packaging/kernel/configs contains a powerpc_kata_kvm_4.19.x file.

@nitkon
Copy link
Contributor Author

nitkon commented May 16, 2019

Hello @marcov ,

  1. The qemu-lite requirement should be made optional for other archs as it would be a necessity only for x86?

  2. linux-container build was failing as I was on older branch. This is the latest status.

  3. Since the builds on some of the distros are green, what would be the steps from here on to make it a part of the kata release cycle? @jcvenegas

  4. Is there anyway to make sure that all the other distros like Ubuntu 1604/1804, RHEL 7 instances are always available in OBS for non-x86 archs? Currently unresolvable means those instances are not available in OBS.

Thanks!

@marcov
Copy link
Contributor

marcov commented May 16, 2019

  1. The qemu-lite requirement should be made optional for other archs as it would be a necessity only for x86?

I let @jcvenegas clarify on this

  1. Is there anyway to make sure that all the other distros like Ubuntu 1604/1804, RHEL 7 instances are always available in OBS for non-x86 archs? Currently unresolvable means those instances are not available in OBS.

You need to make sure the repositories you are building for supports your architecture. E.g. for Ubuntu 18.04 you should use https://build.opensuse.org/project/show/Ubuntu:18.04:Ports

@nitkon
Copy link
Contributor Author

nitkon commented May 16, 2019

@marcov : Thnx. updated. Nit: As of today RHEL_7 on ppc64le is not available in OBS.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
high-priority Very urgent issue (resolve quickly)
Projects
None yet
Development

No branches or pull requests

4 participants