From Fedora Project Wiki
No edit summary
Line 23: Line 23:
Please see the related and more general page on [[Infrastructure_kerberos_authentication|kerberos authentication in Fedora Infrastructure]]
Please see the related and more general page on [[Infrastructure_kerberos_authentication|kerberos authentication in Fedora Infrastructure]]


Question: what version(s) of all the packager tools will I need to be using on December 12th?
* Question: what version(s) of all the packager tools will I need to be using on December 12th?


Answer: Thats not fully determined yet, but should be listed here once it is.
* Answer: Thats not fully determined yet, but should be listed here once it is.
 
* Question: How does the rawhide gating work? Aren't you slowing things down?
 
* Answer: It works by landing all the rawhide builds in a pending tag. Then the autosigner signs them and places them into the normal rawhide tag. This is only delaying builds by how long it takes to sign them. We may add QA checks on this pending step later, but none are being added now.

Revision as of 20:27, 21 November 2016

Flag Day 2016

On the 12th of December 2016 there will be end user impacting changes the packager work flow.

Kerberos for Authentication

Koji supports multiple authentication mechanisms. Fedora infrastructure has set up a freeipa instance internally that has credential syncing to fas. We are working on ensuring that gssapi caching is supported so that you can have multiple TGT's and the ability to work in multiple reams at once. you can get started today by doing kinit <fas username>@FEDORAPROJECT.ORG if you move your ~/.fedora.cert file out of the way authentication will still work.

Well known ssl certificates for koji and pkgs

Using well known certs for koji.fedoraproject.org arm.koji.fedoraproject.org ppc.koji.fedoraproject.org s390.koji.fedoraproject.org pkgs.fedoraproject.org this is the last step needed to have fedoraproject.org switch to hsts and default to https:// when connecting to any fedora service. It will also remove a lot of questions that new people have when connecting to koji via https.

Disable SSL authentication in koji and pkgs

With the switch to keberos and the change of ssl certificates on the koji and pkgs servers we will be disabling the ability to login to koji using a ssl certificate completely. This change will require new koji client configurations for everyone

Gate rawhide builds

Gating will enable us to sign rawhide builds and switch the rawhide repo to having gpgcheck enabled.

What do I have to do

In order to achieve everything we have to break end user configurations. All users will need to have new enough versions of fedora-packager, fedpkg, rpkg, koji. the exact versions needed are not yet known as some enhancements are still being worked on. We will be aiming to have everything pushed stable right before the flag day. Some of the changes will not be compatible with the existing setup. We anticipate keeping everyone informed as we move forward about any actions that will need to be taken on the developer side.


Q&A

Please see the related and more general page on kerberos authentication in Fedora Infrastructure

  • Question: what version(s) of all the packager tools will I need to be using on December 12th?
  • Answer: Thats not fully determined yet, but should be listed here once it is.
  • Question: How does the rawhide gating work? Aren't you slowing things down?
  • Answer: It works by landing all the rawhide builds in a pending tag. Then the autosigner signs them and places them into the normal rawhide tag. This is only delaying builds by how long it takes to sign them. We may add QA checks on this pending step later, but none are being added now.