[magnum] Help / Pointers on mirroring https://opendev.org/starlingx in github.com for CNCF certification of starlingx
Hello, I am working in the OpenStack StarlingX team. We are working on getting StarlingX certified through the CNCF conformance program, https://www.cncf.io/certification/software-conformance/ . ( in the same way that you guys, OpenStack Magnum project, got certified with CNCF ) As you know, in order for the logo to be shown as based on open-source, CNCF requires that the code be mirrored on github.com . e.g. https://github.com/openstack/magnum The openstack foundation guys did provide some info on how to do this: The further steps for the project owner to take: * create a dedicated account for zuul * create the individual empty repos * add a job to each repo to do the mirroring, like: * https://opendev.org/airship/deckhand/src/commit/51dcea4fa12b0bcce65c381c286e... Also, you can find documentation for the parent job here: https://zuul-ci.org/docs/zuul-jobs/general-jobs.html#job-upload-git-mirror ... maybe it’s cause I don’t know anything about zuul jobs, but these instructions are not super clear to me. Is the person who did this for magnum available to provide some more detailed instructions or help on doing this ? Let me know ... any help is much appreciated, Greg.
Hello Greg, - Create a GitHub account for the starlingx, you will have URL on GitHub like [0]. You may try to contact GitHub admins and ask to release starlingx name, as it seems to be unused. - Then create SSH key and upload onto GitHub for that account in GitHub interface - Create empty repositories under [1] to match your existing repositories names here [2] - Encrypt SSH private key as described here [3] or here [4] using this tool [5] - Create patch to all your projects under [2] to '/.zuul.yaml' file, similar to what is listed here [6] - Change job name shown on line 407 via URL above, description (line 409), git_mirror_repository variable (line 411), secret name (line 414 and 418), and SSH key starting from line 424 to 463, to match your project's name, repo path on GitHub, and SSH key - Submit changes to Gerrit with patches for all your project and get them merged. If all goes good, the next change merged would trigger your repositories to be synced to GitHub. Status could be seen here [7] - search for your newly created job manes, they should be nested under "upload-git-mirrorMirrors a tested project repository to a remote git server." Hope it helps. [0] https://github.com/starlingxxxx [1] https://github.com/starlingxxxx/... [2] https://opendev.org/starlingx/... [3] https://docs.openstack.org/infra/manual/zuulv3.html#secret-variables [4] https://docs.openstack.org/infra/manual/creators.html#mirroring-projects-to-... [5] https://opendev.org/zuul/zuul/src/branch/master/tools/encrypt_secret.py [6] https://opendev.org/airship/deckhand/src/commit/51dcea4fa12b0bcce65c381c286e... [7] https://zuul.openstack.org/jobs Sample content of your addition (patch) to your '/.zuul.yaml' files: =================================================== - job: name: starlingx-compile-upload-git-mirror parent: upload-git-mirror description: Mirrors starlingx/compile to starlingxxxx/compile vars: git_mirror_repository: starlingxxxx/compile secrets: - name: git_mirror_credentials secret: starlingx-compile-github-secret pass-to-parent: true - secret: name: starlingx-compile-github-secret data: user: git host: github.com host_key: github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ== ssh_key: !encrypted/pkcs1-oaep - <here goes encrypted SSH private key> =================================================== Best regards, -- Roman Gorshunov
Hi Greg, Currently the conformance test result upload is manually done by me. We didn't setup an automated pipeline for this because the openstack infra doesn't support nested visualization, so we can't run Magnum and generate the conformance test fully automated. But if StartingX can do that, it should be doable. On 31/01/20 4:44 AM, Waines, Greg wrote:
Hello,
I am working in the OpenStack StarlingX team.
We are working on getting StarlingX certified through the CNCF conformance program, https://www.cncf.io/certification/software-conformance/ .
( in the same way that you guys, OpenStack Magnum project, got certified with CNCF )
As you know, in order for the logo to be shown as based on open-source, CNCF requires that the code be mirrored on github.com .
e.g. https://github.com/openstack/magnum
The openstack foundation guys did provide some info on how to do this:
/The further steps for the project owner to take:/
/* create a dedicated account for zuul/
/* create the individual empty repos/
/* add a job to each repo to do the mirroring, like:/
/ * https://opendev.org/airship/deckhand/src/commit/51dcea4fa12b0bcce65c381c286e...
/ /
/Also, you can find documentation for the parent job here: https://zuul-ci.org/docs/zuul-jobs/general-jobs.html#job-upload-git-mirror/
... maybe it’s cause I don’t know anything about zuul jobs, but these instructions are not super clear to me.
*/Is the person who did this for magnum available to provide some more detailed instructions or help on doing this ?/*
Let me know ... any help is much appreciated,
Greg.
-- Cheers & Best regards, Feilong Wang (王飞龙) Head of R&D Catalyst Cloud - Cloud Native New Zealand -------------------------------------------------------------------------- Tel: +64-48032246 Email: flwang@catalyst.net.nz Level 6, Catalyst House, 150 Willis Street, Wellington --------------------------------------------------------------------------
participants (3)
-
Feilong Wang
-
Roman Gorshunov
-
Waines, Greg