Power Developer eXchange A place for IBM Power open source developers to learn, collaborate, contribute, and create Join / Log in
$ chmod +x ilasm ildasm $ ls -l total 3368 drwxr-xr-x 2 root root 4096 Feb 22 15:34 ./ drwxr-xr-x 3 root root 4096 Feb 22 15:34 ../ -rwxr-xr-x 1 root root 1685744 Oct 18 16:10 ilasm* -rwxr-xr-x 1 root root 1742776 Oct 18 16:10 ildasm* ILTools (ilasm and ildasm) are ready to use
OpenJDK 11 1.17 UBI 9 22, Jan RHEL 9 based Middleware Containers container images have been updated to address the security advisory. OpenJDK 11 1.18 UBI 8 22, Jan RHEL 8 based Middleware Containers container images have been updated to address the security advisory. OpenJDK 17 1.17 UBI 9 22, Jan RHEL 8 based Middleware Containers container images have been updated to address the security advisory
Add me as a contact or tag me in a discussion thread if you have feedback or need anything
These images are then pushed to a container image registry, each tagged with a unique tag corresponding to the target architecture
os: linux dist: focal language: shell branches: only: - main jobs: include: - name: Build Multi-Arch Image arch: amd64 services: - docker before install: - mkdir -vp ~/.docker/cli-plugins/ - curl -sSL "https://github.com/docker/buildx/releases/download/v0.10.4/buildx-v0.10.4.linux-amd64" > ~/.docker/cli-plugins/docker-buildx - chmod a+x ~/.docker/cli-plugins/docker-buildx - docker run --rm --privileged multiarch/qemu-user-static --reset -p yes install: - docker buildx create --use --name=multiarch script: - docker login -u "$REGISTRY USERNAME" --password "$REGISTRY PASSWORD" $REGISTRY - docker buildx build --platform linux/amd64,linux/arm64,linux/ppc64le --push --tag $REGISTRY/$REPO NAME/$IMAGE NAME:latest Native approach To begin with, download all the required resources from GitHub
-- name: Build and Publish on: push: branches: [ "main" ] workflow dispatch: # Allows you to run this workflow manually from the Actions tab inputs: tag: description: 'Tag to attach to image' required: true jobs: build-and-publish: name: Publish container image env: REGISTRY: quay.io/$(( secrets.QUAY USER )) REPO NAME: $(( github.event.repository.name )) runs-on: 'ubuntu-latest' steps: - name: Check out the repo uses: actions/checkout@v3 - name: Install SSH key uses: shimataro/ssh-key-action@v2 with: key: $(( secrets.BUILDER PPC64LE SSH KEY )) name: id rsa ppc64le known hosts: unnecessary config: | Host builder-ppc64le HostName $(( secrets.BUILDER PPC64LE SSH HOST )) User root IdentityFile ~/.ssh/id rsa ppc64le StrictHostKeyChecking no - name: Set up Docker Buildx uses: docker/setup-buildx-action@v2 with: version: v0.11.0 platforms: linux/amd64 append: | - endpoint: ssh://builder-ppc64le platforms: linux/ppc64le - name: Login to Quay.io uses: docker/login-action@v1 with: registry: quay.io username: $(( secrets.QUAY USER )) password: $(( secrets.QUAY TOKEN )) - name: Build and push id: docker build uses: docker/build-push-action@v4 with: platforms: linux/amd64,linux/ppc64le push: true tags: $(( env.REGISTRY ))/$(( env.REPO NAME )):$(( github.event.inputs.tag || 'unstable' )) Also, we will need a simple Dockerfile for testing
Given this build, we need an image for golang (from the first part delimited by “:”) that has a tag closer to “1.7” that means a go image that is the closest to the version 1.7
I have also been given the following recommendations: This command give you the actual score of affinity of all the LPARs lsmemopt -m Server-9105-22A-7832351 -r lpar -o currscore ... lpar name=d1302-master-7f5d84f3-000037a2,lpar id=22,curr lpar score=60 As you see, it has a bad score (60/100) This command tells you what score you can reach lsmemopt -m Server-9105-22A-7832351 -r lpar -o calcscore ... lpar name=d1302-master-7f5d84f3-000037a2,lpar id=22,curr lpar score=60,predicted lpar score=100 So in my case it can reach 100/100 This asks to reassign CPU/MEM and prioritise LPAR 22 optmem -m Server-9105-22A-7832351 -o start -t affinity --id 22 You can check the progress with lsmemopt -m Server-9105-22A-7832351 and then reboot the LPAR to apply
2 Comments - no search term matches found in comments.
Then, set the checkout action, configure QEMU static binaries, configure Docker Buildx, login in Quay.io and finally builds and pushes the multi-arch image. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 -- name: 'multi-arch images build' on: push jobs: multiarch-build: runs-on: ubuntu-latest steps: - name : add checkout action