Greetings.
we are now in the infrastructure freeze leading up to the Fedora 31 Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to release the Fedora 31 Beta when it's available.
You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script:
git clone https://infrastructure.fedoraproject.org/infra/ansible.git ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2019-09-17 (or later if release slips or uses the secondary target). Frozen hosts should have no changes made to them without a sign-off on the change from at least 2 sysadmin-main or rel-eng members, along with (in most cases) a patch of the exact change to be made to this list.
Thanks,
kevin
On 8/27/19 2:21 PM, Kevin Fenzi wrote:
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 31 Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to release the Fedora 31 Beta when it's available.
You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script:
git clone https://infrastructure.fedoraproject.org/infra/ansible.git ansible/scripts/freezelist -i inventory
I had a problem with this because I didn't have python2 libraries for ansible installed so the `import ansible.inventory` failed.
Switching the script to python3 worked. Should we apply this?
$ git diff diff --git a/scripts/freezelist b/scripts/freezelist index 89856ea09..b1c99054c 100755 --- a/scripts/freezelist +++ b/scripts/freezelist @@ -1,4 +1,4 @@ -#!/usr/bin/python +#!/usr/bin/python3 # skvidal # doteast: porting to ansible 2.0 # dump out the hosts marked with 'freezes: true' in their vars
Any hosts listed as freezes is frozen until 2019-09-17 (or later if release slips or uses the secondary target). Frozen hosts should have no changes made to them without a sign-off on the change from at least 2 sysadmin-main or rel-eng members, along with (in most cases) a patch of the exact change to be made to this list.
I see the openshift nodes listed as frozen. What about applications that are running in openshift? Can I commit changes to my apps that are for CoreOS without a review?
On 8/27/19 11:50 AM, Dusty Mabe wrote:
On 8/27/19 2:21 PM, Kevin Fenzi wrote:
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 31 Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to release the Fedora 31 Beta when it's available.
You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script:
git clone https://infrastructure.fedoraproject.org/infra/ansible.git ansible/scripts/freezelist -i inventory
I had a problem with this because I didn't have python2 libraries for ansible installed so the `import ansible.inventory` failed.
Ah, it's expected to run on batcave01... where it does work.
Switching the script to python3 worked. Should we apply this?
That would break it on batcave01... :(
$ git diff diff --git a/scripts/freezelist b/scripts/freezelist index 89856ea09..b1c99054c 100755 --- a/scripts/freezelist +++ b/scripts/freezelist @@ -1,4 +1,4 @@ -#!/usr/bin/python +#!/usr/bin/python3 # skvidal # doteast: porting to ansible 2.0 # dump out the hosts marked with 'freezes: true' in their vars
Any hosts listed as freezes is frozen until 2019-09-17 (or later if release slips or uses the secondary target). Frozen hosts should have no changes made to them without a sign-off on the change from at least 2 sysadmin-main or rel-eng members, along with (in most cases) a patch of the exact change to be made to this list.
I see the openshift nodes listed as frozen. What about applications that are running in openshift? Can I commit changes to my apps that are for CoreOS without a review?
I think thats up to you all... since those are not directly related to the Fedora release, I'd say we wouldn't need to. Perhaps we would want to have a seperate (more targeted) freeze before the next FCOS release? Or perhaps it doesn't make sense? There are some things we do that are related to your release... signing artifacts, the updater app, etc.
I'm open to whatever works best for you all here.
kevin
On 8/27/19 3:38 PM, Kevin Fenzi wrote:
On 8/27/19 11:50 AM, Dusty Mabe wrote:
On 8/27/19 2:21 PM, Kevin Fenzi wrote:
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 31 Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to release the Fedora 31 Beta when it's available.
You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script:
git clone https://infrastructure.fedoraproject.org/infra/ansible.git ansible/scripts/freezelist -i inventory
I had a problem with this because I didn't have python2 libraries for ansible installed so the `import ansible.inventory` failed.
Ah, it's expected to run on batcave01... where it does work.
Switching the script to python3 worked. Should we apply this?
That would break it on batcave01... :(
We can't get the newer version there?
$ git diff diff --git a/scripts/freezelist b/scripts/freezelist index 89856ea09..b1c99054c 100755 --- a/scripts/freezelist +++ b/scripts/freezelist @@ -1,4 +1,4 @@ -#!/usr/bin/python +#!/usr/bin/python3 # skvidal # doteast: porting to ansible 2.0 # dump out the hosts marked with 'freezes: true' in their vars
Any hosts listed as freezes is frozen until 2019-09-17 (or later if release slips or uses the secondary target). Frozen hosts should have no changes made to them without a sign-off on the change from at least 2 sysadmin-main or rel-eng members, along with (in most cases) a patch of the exact change to be made to this list.
I see the openshift nodes listed as frozen. What about applications that are running in openshift? Can I commit changes to my apps that are for CoreOS without a review?
I think thats up to you all... since those are not directly related to the Fedora release, I'd say we wouldn't need to. Perhaps we would want to have a seperate (more targeted) freeze before the next FCOS release? Or perhaps it doesn't make sense? There are some things we do that are related to your release... signing artifacts, the updater app, etc.
I'm open to whatever works best for you all here.
I just want to know that I'm doing things that are allowed. If you feel comfortable that I'm within my rights, then I'm happy.
Dusty
On Tue, Aug 27, 2019 at 02:50:57PM -0400, Dusty Mabe wrote:
On 8/27/19 2:21 PM, Kevin Fenzi wrote:
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 31 Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to release the Fedora 31 Beta when it's available.
You can see a list of hosts that do not freeze by checking out the ansible repo and running the freezelist script:
git clone https://infrastructure.fedoraproject.org/infra/ansible.git ansible/scripts/freezelist -i inventory
I had a problem with this because I didn't have python2 libraries for ansible installed so the `import ansible.inventory` failed.
Switching the script to python3 worked. Should we apply this?
$ git diff diff --git a/scripts/freezelist b/scripts/freezelist index 89856ea09..b1c99054c 100755 --- a/scripts/freezelist +++ b/scripts/freezelist @@ -1,4 +1,4 @@ -#!/usr/bin/python +#!/usr/bin/python3 # skvidal # doteast: porting to ansible 2.0 # dump out the hosts marked with 'freezes: true' in their vars
If all you need is to change the shebang, then instead of doing: ``ansible/scripts/freezelist -i inventory`` you can do: ``python3 ansible/scripts/freezelist -i inventory`` and it should work with python3 as well :)
Pierre
Greetings.
With the release of Fedora 31 Beta yesterday, we are now out of freeze.
Our next scheduled freeze is Fedora 31 Final on 2019-10-08.
Thanks everyone for a successful and smooth release.
kevin
Can we update mock on builders to the latest so that it gets fixes / improvements for dynamic BuildRequires?
On Wed, Sep 18, 2019 at 5:26 PM Kevin Fenzi kevin@scrye.com wrote:
Greetings.
With the release of Fedora 31 Beta yesterday, we are now out of freeze.
Our next scheduled freeze is Fedora 31 Final on 2019-10-08.
Thanks everyone for a successful and smooth release.
kevin
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
On 9/18/19 8:59 AM, Igor Gnatenko wrote:
Can we update mock on builders to the latest so that it gets fixes / improvements for dynamic BuildRequires?
Yep. Done.
kevin --
On Wed, Sep 18, 2019 at 5:26 PM Kevin Fenzi kevin@scrye.com wrote:
Greetings.
With the release of Fedora 31 Beta yesterday, we are now out of freeze.
Our next scheduled freeze is Fedora 31 Final on 2019-10-08.
Thanks everyone for a successful and smooth release.
kevin
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
Thanks a lot!
On Wed, Sep 18, 2019, 21:51 Kevin Fenzi kevin@scrye.com wrote:
On 9/18/19 8:59 AM, Igor Gnatenko wrote:
Can we update mock on builders to the latest so that it gets fixes / improvements for dynamic BuildRequires?
Yep. Done.
kevin
On Wed, Sep 18, 2019 at 5:26 PM Kevin Fenzi kevin@scrye.com wrote:
Greetings.
With the release of Fedora 31 Beta yesterday, we are now out of freeze.
Our next scheduled freeze is Fedora 31 Final on 2019-10-08.
Thanks everyone for a successful and smooth release.
kevin
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to
infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
infrastructure@lists.fedoraproject.org