Re: Meeting Agenda Item: Introduction Will Chellman

2018-04-23 Thread Michael Singh
Hi Will, 

A very warm welcome to you. Thanks for choosing Fedora!
Be sure to join #fedora-{admin,apps,noc}.

On Tue, 2018-04-24 at 00:28 +, Will Chellman wrote:
> Hi All,
> 
> My name is Will Chellman, I am an Infrastructure Solutions Engineer
> for a company called IGT and I currently reside in the Boston, MA
> area.
> 
> In my day job I primarily work with RHEL and VMWare doing a lot of
> automation with Ansible/shell scripting as well as deploying/fixing
> our infrastructure across the globe. 
> 
> Outside of work I am currently most interested in Web
> Development(Ruby On Rails, etc) and I am pursuing my RHCSA/RHCE. As
> far as development goes I am comfortable with C, Ruby, and Python and
> I am always willing to dive in and learn what ever is needed for a
> task.
> 
> I would like to join the 'fi-apprentice' group and poke around and
> see how I can best contribute and learn the infrastructure. I am
> willing to dedicate at least 15-20 hours a week to the project. I use
> Fedora daily as my desktop OS (KDE Plasma is my favorite) and would
> love the opportunity to be able to give more back to the Fedora and
> Open Source community!
> 
> Best,
> Will Chellman
> IRC/FAS: creaked
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-leave@lists.fedoraproj
> ect.org

Sent via Migadu.com, world's easiest email hosting
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


[Fedocal] Reminder meeting : Bodhi stakeholder's meeting

2018-04-23 Thread bowlofeggs
Dear all,

You are kindly invited to the meeting:
   Bodhi stakeholder's meeting on 2018-04-24 from 15:00:00 to 16:00:00 UTC
   At fedora-meetin...@irc.freenode.net

The meeting will be about:



Source: https://apps.fedoraproject.org/calendar/meeting/4671/

___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR - Prepare for Atomic Host/OSTree for F28

2018-04-23 Thread Dusty Mabe


On 04/23/2018 09:11 PM, Kevin Fenzi wrote:
> On 04/23/2018 05:31 PM, Dusty Mabe wrote:
>>
>>
>> On 04/23/2018 07:10 PM, Stephen John Smoogen wrote:
>>> Reviewed the PR. +1
>>
>> Thanks all - Merged.. Kevin do you mind running the relevant playbooks
>> to make the changes take effect? I don't think I have permission for
>> all of those. 
> 
> I can, but is everything in place for the new-updates-sync?
> That will start going right after I run the playbook.

I believe so. It will just try to sync the refs in the compose repo
over into prod. It should be ok, but we can wait for patrick to run the
playbooks tomorrow.

> 
> I'm not 100% sure what needs to be restarted on robosign, so perhaps
> Patrick could apply that in the morning tomorrow and restart whatever is
> needed.

OK

> 
> Otherwise I can plan on running things tomorrow before the updates
> pushes...

K
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR: Fix collectd problems with containers

2018-04-23 Thread Stephen John Smoogen
Updated patch to get the other directories which were filling up collectd

diff --git a/roles/collectd/base/templates/collectd.conf.j2
b/roles/collectd/base/templates/collectd.conf.j2
index 91f5a63..0de9b40 100644
--- a/roles/collectd/base/templates/collectd.conf.j2
+++ b/roles/collectd/base/templates/collectd.conf.j2
@@ -39,6 +39,24 @@ LoadPlugin vmem
 IgnoreSelected false
 

+
+  Interface "/^veth/"
+  IgnoreSelected true
+
+
+
+  Interface "/^df-var-lib-docker-containers-/"
+  Interface "/^df-var-lib-docker-overlay2-/"
+  Interface "/^df-run-user-/"
+  Interface "/^df-tmp-tweak/"
+  Interface "/^df-mnt-fedora_koji/"
+  Interface "/^df-var-lib-mock-fedora/"
+  Interface "/^df-tmp-iso-mount-/"
+  Interface "/^df-var-lib-origin-openshift/"
+  Interface "/^df-.*\.snapshot/"
+  IgnoreSelected true
+
+
 
TranslateDevicename false
 



On 23 April 2018 at 21:14, Kevin Fenzi  wrote:
> +1 to fix it.
>
> kevin
>
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>



-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR: Fix collectd problems with containers

2018-04-23 Thread Kevin Fenzi
+1 to fix it.

kevin



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR - Prepare for Atomic Host/OSTree for F28

2018-04-23 Thread Kevin Fenzi
On 04/23/2018 05:31 PM, Dusty Mabe wrote:
> 
> 
> On 04/23/2018 07:10 PM, Stephen John Smoogen wrote:
>> Reviewed the PR. +1
> 
> Thanks all - Merged.. Kevin do you mind running the relevant playbooks
> to make the changes take effect? I don't think I have permission for
> all of those. 

I can, but is everything in place for the new-updates-sync?
That will start going right after I run the playbook.

I'm not 100% sure what needs to be restarted on robosign, so perhaps
Patrick could apply that in the morning tomorrow and restart whatever is
needed.

Otherwise I can plan on running things tomorrow before the updates
pushes...

kevin



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


FBR: Fix collectd problems with containers

2018-04-23 Thread Stephen John Smoogen
Currently we are creating lots of collectd files for the containers
which only exist for 30 minutes or so on the proxies. This is a lot of
rrd files and fills up log01 eventually.

diff --git a/roles/collectd/base/templates/collectd.conf.j2
b/roles/collectd/base/templates/collectd.conf.j2
index 91f5a63..d84b7d0 100644
--- a/roles/collectd/base/templates/collectd.conf.j2
+++ b/roles/collectd/base/templates/collectd.conf.j2
@@ -39,6 +39,17 @@ LoadPlugin vmem
 IgnoreSelected false
 

+
+  Interface "/^veth/"
+  IgnoreSelected true
+
+
+
+  Interface "/^df-var-lib-docker-containers-/"
+  Interface "/^df-var-lib-docker-overlay2-/"
+  IgnoreSelected true
+
+
 
TranslateDevicename false
 



-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR - Prepare for Atomic Host/OSTree for F28

2018-04-23 Thread Dusty Mabe


On 04/23/2018 07:10 PM, Stephen John Smoogen wrote:
> Reviewed the PR. +1

Thanks all - Merged.. Kevin do you mind running the relevant playbooks
to make the changes take effect? I don't think I have permission for
all of those. 

Dusty 
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Meeting Agenda Item: Introduction Will Chellman

2018-04-23 Thread Will Chellman
Hi All,

My name is Will Chellman, I am an Infrastructure Solutions Engineer for a 
company called IGT and I currently reside in the Boston, MA area.

In my day job I primarily work with RHEL and VMWare doing a lot of automation 
with Ansible/shell scripting as well as deploying/fixing our infrastructure 
across the globe. 

Outside of work I am currently most interested in Web Development(Ruby On 
Rails, etc) and I am pursuing my RHCSA/RHCE. As far as development goes I am 
comfortable with C, Ruby, and Python and I am always willing to dive in and 
learn what ever is needed for a task.

I would like to join the 'fi-apprentice' group and poke around and see how I 
can best contribute and learn the infrastructure. I am willing to dedicate at 
least 15-20 hours a week to the project. I use Fedora daily as my desktop OS 
(KDE Plasma is my favorite) and would love the opportunity to be able to give 
more back to the Fedora and Open Source community!

Best,
Will Chellman
IRC/FAS: creaked
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR - Prepare for Atomic Host/OSTree for F28

2018-04-23 Thread Stephen John Smoogen
Reviewed the PR. +1

On 23 April 2018 at 18:59, Kevin Fenzi  wrote:
> On 04/23/2018 03:23 PM, Dusty Mabe wrote:
>>
>>
>> On 04/23/2018 05:50 PM, Kevin Fenzi wrote:
>>> On 04/23/2018 02:38 PM, Dusty Mabe wrote:

 Here are a few patches for getting everything in order for F28 for
 Atomic Host/OSTree.
>>>
>>> Whats the timing here? When do we need to land these? After we have f28
>>> in the box and are starting to push 0-day updates? or before then?
>>>
>>
>> Ideally now. We'd like to start running the nightly atomic compose:
>> https://pagure.io/pungi-fedora/pull-request/600
>
> ok. Sounds good to me then... +1
>
> kevin
>
>
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>



-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR - Prepare for Atomic Host/OSTree for F28

2018-04-23 Thread Kevin Fenzi
On 04/23/2018 03:23 PM, Dusty Mabe wrote:
> 
> 
> On 04/23/2018 05:50 PM, Kevin Fenzi wrote:
>> On 04/23/2018 02:38 PM, Dusty Mabe wrote:
>>>
>>> Here are a few patches for getting everything in order for F28 for
>>> Atomic Host/OSTree. 
>>
>> Whats the timing here? When do we need to land these? After we have f28
>> in the box and are starting to push 0-day updates? or before then?
>>
> 
> Ideally now. We'd like to start running the nightly atomic compose: 
> https://pagure.io/pungi-fedora/pull-request/600

ok. Sounds good to me then... +1

kevin




signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR - Prepare for Atomic Host/OSTree for F28

2018-04-23 Thread Dusty Mabe


On 04/23/2018 05:50 PM, Kevin Fenzi wrote:
> On 04/23/2018 02:38 PM, Dusty Mabe wrote:
>>
>> Here are a few patches for getting everything in order for F28 for
>> Atomic Host/OSTree. 
> 
> Whats the timing here? When do we need to land these? After we have f28
> in the box and are starting to push 0-day updates? or before then?
> 

Ideally now. We'd like to start running the nightly atomic compose: 
https://pagure.io/pungi-fedora/pull-request/600
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR: bodhi-3.6.1

2018-04-23 Thread Stephen John Smoogen
On 23 April 2018 at 17:04, Randy Barlow  wrote:
> On 04/23/2018 05:00 PM, Randy Barlow wrote:
>> I would like to deploy Bodhi 3.6.1[0,1] to production
> I forgot to mention - Patrick would like to deploy this asap in my
> absence, as I am unable to do so myself this evening (I am available to
> tomorrow, however).

OK +1, but only because Patrick said so.

> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org



-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR - Prepare for Atomic Host/OSTree for F28

2018-04-23 Thread Kevin Fenzi
On 04/23/2018 02:38 PM, Dusty Mabe wrote:
> 
> Here are a few patches for getting everything in order for F28 for
> Atomic Host/OSTree. 

Whats the timing here? When do we need to land these? After we have f28
in the box and are starting to push 0-day updates? or before then?

kevin




signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


[PATCH 3/3] new-updates-sync: add syncing for F28AH updates ostree

2018-04-23 Thread Dusty Mabe
Signed-off-by: Dusty Mabe 
---
 roles/bodhi2/backend/files/new-updates-sync | 13 -
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/roles/bodhi2/backend/files/new-updates-sync 
b/roles/bodhi2/backend/files/new-updates-sync
index 827e8cfcd..adfd5c2f0 100755
--- a/roles/bodhi2/backend/files/new-updates-sync
+++ b/roles/bodhi2/backend/files/new-updates-sync
@@ -22,7 +22,18 @@ ATOMICDEST = '/mnt/koji/atomic/repo/'
 RELEASES = {'f28': {'topic': 'fedora',
 'version': '28',
 'modules': ['fedora', 'fedora-secondary'],
-'repos': {'updates-testing': {
+'repos': {'updates': {
+'from': 'f28-updates',
+'ostrees': [{'ref': 
'fedora/28/%(arch)s/updates/atomic-host',
+ 'dest': ATOMICDEST,
+ 'arches': ['x86_64', 'ppc64le', 
'aarch64']},
+{'ref': 
'fedora/28/x86_64/updates/workstation',
+ 'dest': ATOMICDEST}],
+# Hack around for the fact that ostree on 
f25 doesn't know links
+{'ref': 'fedora/28/x86_64/workstation',
+ 'dest': ATOMICDEST}],
+'to': []}},
+  'updates-testing': {
 'from': 'f28-updates-testing',
 'ostrees': [{'ref': 
'fedora/28/%(arch)s/testing/atomic-host',
  'dest': ATOMICDEST,
-- 
2.14.3
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


[PATCH 2/3] bodhi-pungi: only do AH artifact creation for f28-u-t for now

2018-04-23 Thread Dusty Mabe
We'll start doing it for f28-u when we get the kinks worked out
after the first F28 Atomic Host release.

Signed-off-by: Dusty Mabe 
---
 roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 
b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
index d92ad4f16..287c03177 100644
--- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
+++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
@@ -180,7 +180,7 @@ ostree = {
 }
 [% endif %]
 
-[% if release.id_prefix == 'FEDORA' and release.version_int >= 28 %]
+[% if release.id_prefix == 'FEDORA' and release.version_int >= 28 and 
request.name == 'testing' %]
 global_ksurl = 'git+https://pagure.io/fedora-kickstarts.git?#origin/f[[ 
release.version_int ]]'
 global_release = '!RELEASE_FROM_LABEL_DATE_TYPE_RESPIN'
 image_name_format = 
'%(release_short)s-%(variant)s-%(disc_type)s-%(arch)s-%(version)s-%(date)s%(type_suffix)s.%(respin)s.iso'
-- 
2.14.3
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


[PATCH 1/3] robosig: add new refs for f28 atomic host

2018-04-23 Thread Dusty Mabe
Signed-off-by: Dusty Mabe 
---
 .../files/robosignatory.production.py  | 34 +-
 1 file changed, 33 insertions(+), 1 deletion(-)

diff --git a/roles/robosignatory/files/robosignatory.production.py 
b/roles/robosignatory/files/robosignatory.production.py
index 021dee325..668d176ae 100644
--- a/roles/robosignatory/files/robosignatory.production.py
+++ b/roles/robosignatory/files/robosignatory.production.py
@@ -217,7 +217,27 @@ config = {
 'directory': '/mnt/fedora_koji/koji/compose/atomic/repo/',
 'key': 'fedora-28'
 },
-'fedora/28/x86_64/workstation': {
+'fedora/28/x86_64/updates/atomic-host': {
+'directory': '/mnt/fedora_koji/koji/compose/atomic/repo/',
+'key': 'fedora-28'
+},
+'fedora/28/ppc64le/updates/atomic-host': {
+'directory': '/mnt/fedora_koji/koji/compose/atomic/repo/',
+'key': 'fedora-28'
+},
+'fedora/28/aarch64/updates/atomic-host': {
+'directory': '/mnt/fedora_koji/koji/compose/atomic/repo/',
+'key': 'fedora-28'
+},
+'fedora/28/x86_64/testing/atomic-host': {
+'directory': '/mnt/fedora_koji/koji/compose/atomic/repo/',
+'key': 'fedora-28'
+},
+'fedora/28/ppc64le/testing/atomic-host': {
+'directory': '/mnt/fedora_koji/koji/compose/atomic/repo/',
+'key': 'fedora-28'
+},
+'fedora/28/aarch64/testing/atomic-host': {
 'directory': '/mnt/fedora_koji/koji/compose/atomic/repo/',
 'key': 'fedora-28'
 },
@@ -225,6 +245,18 @@ config = {
 'directory': '/mnt/fedora_koji/koji/compose/atomic/repo/',
 'key': 'fedora-29'
 },
+'fedora/28/x86_64/workstation': {
+'directory': '/mnt/fedora_koji/koji/compose/atomic/repo/',
+'key': 'fedora-28'
+},
+'fedora/28/x86_64/updates/workstation': {
+'directory': '/mnt/fedora_koji/koji/compose/atomic/repo/',
+'key': 'fedora-28'
+},
+'fedora/28/x86_64/testing/workstation': {
+'directory': '/mnt/fedora_koji/koji/compose/atomic/repo/',
+'key': 'fedora-28'
+},
 'fedora/rawhide/ppc64le/atomic-host': {
 'directory': '/mnt/fedora_koji/koji/compose/atomic/repo/',
 'key': 'fedora-29'
-- 
2.14.3
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


FBR - Prepare for Atomic Host/OSTree for F28

2018-04-23 Thread Dusty Mabe

Here are a few patches for getting everything in order for F28 for
Atomic Host/OSTree. 
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR: bodhi-3.6.1

2018-04-23 Thread Kevin Fenzi
+1

as always, coordinate with releng, etc.

Note that we may need to push things stable soon for release, so if this
takes a long time for some reason we will want to look at rolling back
so we keep a working bodhi.

kevin



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR: bodhi-3.6.1

2018-04-23 Thread Randy Barlow
On 04/23/2018 05:04 PM, Randy Barlow wrote:
> On 04/23/2018 05:00 PM, Randy Barlow wrote:
>> I would like to deploy Bodhi 3.6.1[0,1] to production

> I forgot to mention - Patrick would like to deploy this asap in my
> absence, as I am unable to do so myself this evening (I am available to
> tomorrow, however).

I also forgot to mention that this is live in stg:

https://bodhi.stg.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR: bodhi-3.6.1

2018-04-23 Thread Randy Barlow
On 04/23/2018 05:00 PM, Randy Barlow wrote:
> I would like to deploy Bodhi 3.6.1[0,1] to production
I forgot to mention - Patrick would like to deploy this asap in my
absence, as I am unable to do so myself this evening (I am available to
tomorrow, however).
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


FBR: bodhi-3.6.1

2018-04-23 Thread Randy Barlow
Gr33tings, people of Fedora Infra,

I would like to deploy Bodhi 3.6.1[0,1] to production, which should
address some of the stability issues we experienced with 3.6.0. It will
also resolve something that's made me uncomfortable over the past week -
Bodhi's backends have been running 3.6.0 while the front ends have been
running 3.5.2. In theory this should be fine, but it makes me nervous.

In addition to the changes upstream, I've made some downstream and
deployment configuration changes in this release:

* The Rawhide and f27-infra packages now split the composer out into its
  own subpackage[2]. This greatly reduces the size of the Bodhi web
  container (cutting dependencies about in half due to not needing
  Pungi).
* I switched Bodhi to use an in-memory cache for the home page instead
  of a filesystem cache[3]. Patrick and I believe that the filesystem
  cache caused some of the OpenShift instability due to the server
  processes waiting on file locks. The real patch for this will involve
  removing some "if staging" statements from the cited commit, but I
  didn't want to send *that* patch because it would be less clear than
  the one I cited as to what the real change is.

I believe that this release will be stable in OpenShift, though it's
hard to be 100% sure since the majority of the issues only happen under
production load.


[0] https://bodhi.stg.fedoraproject.org/docs/user/release_notes.html
[1] https://github.com/fedora-infra/bodhi/compare/3.6.0...3.6.1[2]
https://src.fedoraproject.org/rpms/bodhi/c/6b63e0dc5d340cdac80ca3fcc2cf7e204d5ca954?branch=master[3]
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=c99ece376c4d401628ab04dfa3a6e61dec8920bd
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Meeting time moving to 14UTC! Re: Moving meeting time?

2018-04-23 Thread Kevin Fenzi
ok, from all the votes we have now...

The current best choice is:

Thursday, April 26, 2018 - 14:00-15:00

with 9 votes.

14UTC wins!

(Thats early for me, but I will be there).

kevin



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: Fedora and PDC

2018-04-23 Thread Ken Dreyer
On Sun, Apr 22, 2018 at 2:23 AM, Stanislav Ochotnicky
 wrote:
> The difference is that PDC rpm-mappings API endpoint was result of two
> sources:
>  * Manual per-rpm mappings (overrides) - this is sort of suitable if you
>have a product with just a couple source packages so it's manageable
>this way (i.e Ceph case)
>  * Results of compose metadata import - this is what Fedora/RHEL uses
>because several thousands of source packages are not manageable
>one-by-one by humans manually.
>
> You could still make a system that would create "PRs" for the generated
> files for second case, but then querying the current state will still be
> a bit tricky. I guess...

Yeah, the fact that we have (at least) two different input and storage
methods there is a lot of complexity. I'm not sure that's a good
design in 2018.

Regardless, you're right, I'm envisioning that we'd have a tool to
generate the data commits and PRs (or just commit + push directly).
PDC had included its own rudimentary form of version control for
auditing and message bus integration. Git's experience is much richer.

- Ken
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR to fix the purge amis cron

2018-04-23 Thread Stephen John Smoogen
+1

On 23 April 2018 at 10:24, Sayan Chowdhury
 wrote:
> Hi,
>
> We have a cron in place which should be responsible for periodic
> deletion of the nightly AMIs, But the cron wasn't properly setup
> properly via Ansible and currently the cron does not run. This patch
> should fix the issue.
>
> From b4d241bba55cf3155dce5bb02c005f9383f9a46b Mon Sep 17 00:00:00 2001
> From: Sayan Chowdhury 
> Date: Mon, 23 Apr 2018 19:08:45 +0530
> Subject: [PATCH 1/1] releng: Use template instead of copy for purge-amis
>
> Signed-off-by: Sayan Chowdhury 
> ---
>  roles/releng/tasks/main.yml| 3 +--
>  roles/releng/{files/purge-amis => templates/purge-amis.j2} | 0
>  2 files changed, 1 insertion(+), 2 deletions(-)
>  rename roles/releng/{files/purge-amis => templates/purge-amis.j2} (100%)
>
> diff --git a/roles/releng/tasks/main.yml b/roles/releng/tasks/main.yml
> index 6a8d81e..26119a4 100644
> --- a/roles/releng/tasks/main.yml
> +++ b/roles/releng/tasks/main.yml
> @@ -169,10 +169,9 @@
>
>  # put cron job in for purging nightly amis
>  - name: purge nightly amis cron
> -  copy: src="purge-amis" dest=/etc/cron.d/purge-amis
> +  template: src=purge-amis.j2 dest=/etc/cron.d/purge-amis
>when: inventory_hostname.startswith('compose-x86-01')
>
> -
>  - name: install compose /etc/httpd/conf.d/compose.conf file
>copy: >
>  src="compose.conf"
> diff --git a/roles/releng/files/purge-amis
> b/roles/releng/templates/purge-amis.j2
> similarity index 100%
> rename from roles/releng/files/purge-amis
> rename to roles/releng/templates/purge-amis.j2
> --
> 2.9.4
>
> +1s?
>
>
> --
> Sayan Chowdhury 
> Senior Software Engineer, Fedora Engineering - Emerging Platform
> GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B
>
>
> Proud to work at The Open Organization!
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org



-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: Fix cron job fixing/adjusting the git hooks in dist-git

2018-04-23 Thread Stephen John Smoogen
+1 with Kevin's additions.

On 23 April 2018 at 11:40, Kevin Fenzi  wrote:
> On 04/23/2018 02:40 AM, Pierre-Yves Chibon wrote:
>> Good Morning Everyone,
>>
>> I re-wrote last week the script fixing the git hooks in dist-git, but its 
>> work
>> is getting overridden by the old script running in a cron (that Kevin fixed 
>> this
>> week-end).
>>
>> So I would like to replace the cron running the old script with a cron 
>> running
>> the new script:
>>
>> Here is the diff:
>>
>> diff --git a/ roles/gitolite/check_fedmsg_hooks/tasks/main.yml b/ 
>> roles/gitolite/check_fedmsg_hooks/tasks/main.yml
>> index d357a7d83..bea193af1 100644
>> --- a/ roles/gitolite/check_fedmsg_hooks/tasks/main.yml
>> +++ b/ roles/gitolite/check_fedmsg_hooks/tasks/main.yml
>> @@ -8,7 +8,7 @@
>>  minute=10
>>  hour="0,12"
>>  user=pagure
>> -job="/usr/local/bin/git-check-perms /srv/git/repositories 
>> --check=fedmsg-hook -f"
>> +job="/usr/local/bin/distgit_check_hook.py"
>>tags:
>>- git
>>- gitolite
>>
>>
>> Note, we could make this run more often as it runs in a few minutes (the 
>> forks
>> being the slowest namespace, the other namespace run under a minute).
>>
>> Thoughts?
>
> +1 to this, but also as we discussed on irc we should get pagure to make
> the repos the way we want them to start with. ;) But that can come in
> with the next pagure version and this fix will make the script much nicer.
>
> Perhaps we should move it to every 15min until we get the pagure change
> in and then back it off to 1 or 2 times a day.
>
> kevin
>
>
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>



-- 
Stephen J Smoogen.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR to fix the purge amis cron

2018-04-23 Thread Kevin Fenzi
+1... good catch on the files vs templates. :)

kevin



signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: Fix cron job fixing/adjusting the git hooks in dist-git

2018-04-23 Thread Kevin Fenzi
On 04/23/2018 02:40 AM, Pierre-Yves Chibon wrote:
> Good Morning Everyone,
> 
> I re-wrote last week the script fixing the git hooks in dist-git, but its work
> is getting overridden by the old script running in a cron (that Kevin fixed 
> this
> week-end).
> 
> So I would like to replace the cron running the old script with a cron running
> the new script:
> 
> Here is the diff:
> 
> diff --git a/ roles/gitolite/check_fedmsg_hooks/tasks/main.yml b/ 
> roles/gitolite/check_fedmsg_hooks/tasks/main.yml
> index d357a7d83..bea193af1 100644
> --- a/ roles/gitolite/check_fedmsg_hooks/tasks/main.yml
> +++ b/ roles/gitolite/check_fedmsg_hooks/tasks/main.yml
> @@ -8,7 +8,7 @@
>  minute=10
>  hour="0,12"
>  user=pagure
> -job="/usr/local/bin/git-check-perms /srv/git/repositories 
> --check=fedmsg-hook -f"
> +job="/usr/local/bin/distgit_check_hook.py"
>tags:
>- git
>- gitolite
> 
> 
> Note, we could make this run more often as it runs in a few minutes (the forks
> being the slowest namespace, the other namespace run under a minute).
> 
> Thoughts?

+1 to this, but also as we discussed on irc we should get pagure to make
the repos the way we want them to start with. ;) But that can come in
with the next pagure version and this fix will make the script much nicer.

Perhaps we should move it to every 15min until we get the pagure change
in and then back it off to 1 or 2 times a day.

kevin




signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


FBR to fix the purge amis cron

2018-04-23 Thread Sayan Chowdhury
Hi,

We have a cron in place which should be responsible for periodic
deletion of the nightly AMIs, But the cron wasn't properly setup
properly via Ansible and currently the cron does not run. This patch
should fix the issue.

From b4d241bba55cf3155dce5bb02c005f9383f9a46b Mon Sep 17 00:00:00 2001
From: Sayan Chowdhury 
Date: Mon, 23 Apr 2018 19:08:45 +0530
Subject: [PATCH 1/1] releng: Use template instead of copy for purge-amis

Signed-off-by: Sayan Chowdhury 
---
 roles/releng/tasks/main.yml| 3 +--
 roles/releng/{files/purge-amis => templates/purge-amis.j2} | 0
 2 files changed, 1 insertion(+), 2 deletions(-)
 rename roles/releng/{files/purge-amis => templates/purge-amis.j2} (100%)

diff --git a/roles/releng/tasks/main.yml b/roles/releng/tasks/main.yml
index 6a8d81e..26119a4 100644
--- a/roles/releng/tasks/main.yml
+++ b/roles/releng/tasks/main.yml
@@ -169,10 +169,9 @@

 # put cron job in for purging nightly amis
 - name: purge nightly amis cron
-  copy: src="purge-amis" dest=/etc/cron.d/purge-amis
+  template: src=purge-amis.j2 dest=/etc/cron.d/purge-amis
   when: inventory_hostname.startswith('compose-x86-01')

-
 - name: install compose /etc/httpd/conf.d/compose.conf file
   copy: >
 src="compose.conf"
diff --git a/roles/releng/files/purge-amis
b/roles/releng/templates/purge-amis.j2
similarity index 100%
rename from roles/releng/files/purge-amis
rename to roles/releng/templates/purge-amis.j2
-- 
2.9.4

+1s?


-- 
Sayan Chowdhury 
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: Fedora and PDC

2018-04-23 Thread Aurelien Bompard
> > The "pdc-lite" options are attractive, across the board.
>

I know Django and Django-REST-Framework, and I've made a small contribution
to PDC a few months ago, so I may be of use if that's the path we choose.

Aurélien
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: [release] - fedora-packages 4.0.0

2018-04-23 Thread Clement Verna
This is version 4.1.1 and not 4.0.0 as the subject suggest :)

On 23 April 2018 at 13:34, Clement Verna  wrote:
> Greetings,
>
> A new release of fedora-packages is now deployed in stg and prod. This
> release allows to display F28 in the Active Releases Overview.
>
> The changelog is available in here[0].
>
> Happy searching.
>
> [0] - 
> https://github.com/fedora-infra/fedora-packages/blob/develop/CHANGELOG.rst#411
>
> Clément
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


[release] - fedora-packages 4.0.0

2018-04-23 Thread Clement Verna
Greetings,

A new release of fedora-packages is now deployed in stg and prod. This
release allows to display F28 in the Active Releases Overview.

The changelog is available in here[0].

Happy searching.

[0] - 
https://github.com/fedora-infra/fedora-packages/blob/develop/CHANGELOG.rst#411

Clément
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: [Rpm-ecosystem] Zchunk update

2018-04-23 Thread Jonathan Dieter
On Mon, 2018-04-23 at 00:27 -0400, Neal Gompa wrote:
> On Tue, Apr 17, 2018 at 3:05 PM, Jonathan Dieter  wrote:
> > I'm assuming that you're referring here to getting zchunk packaged into
> > Fedora.  I'd really like to finalize the file format (we're close, but
> > I still need a good way of storing signatures in it) and the download
> > API before releasing it into Fedora proper.
> > 
> 
> I'm looking forward to this!

I've updated the file format to allow for multiple signatures, updated
the zchunk code to recognize the existence of a signature (while still
not checking it), and have released as zchunk-0.3.0 in COPR.  I've also
added in 32-bits of flags that we can use to extend the format in a
backwards-compatible way.

The current zchunk format description is at:
https://github.com/jdieter/zchunk/blob/master/zchunk_format.txt

> I would recommend using the dicts mentioned above as they give me over
> > 40% space savings for both other.xml.zck and primary.xml.zck.  Do
> > please let me know if you run into any problems.
> > 
> 
> Are those dictionaries Fedora specific? If so, how can other
> distributions generate similar ones? If not, still, how were they
> made? :)

They were generated from Fedora metadata, but they should help with any
distribution's repodata.  I generated them by splitting a few day's
worth of metadata along package boundaries, stripping out any
checksums, and then running zstd --train * on the directory containing
the split metadata.  The script I used is available at
https://www.jdieter.net/downloads/zchunk-dicts/split.py, and I hope to
write up proper instructions at some point.

Jonathan
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR: no CI requirements for modules

2018-04-23 Thread Pierre-Yves Chibon
On Mon, Apr 23, 2018 at 11:28:19AM +0200, Pierre-Yves Chibon wrote:
> Good Morning Everyone,
> 
> I re-wrote last week the script fixing the git hooks in dist-git, but its work
> is getting overridden by the old script running in a cron (that Kevin fixed 
> this
> week-end).

That's a fail in Subject, let's try again in a new email


Sorry for the noise,

Pierre


signature.asc
Description: PGP signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Fix cron job fixing/adjusting the git hooks in dist-git

2018-04-23 Thread Pierre-Yves Chibon
Good Morning Everyone,

I re-wrote last week the script fixing the git hooks in dist-git, but its work
is getting overridden by the old script running in a cron (that Kevin fixed this
week-end).

So I would like to replace the cron running the old script with a cron running
the new script:

Here is the diff:

diff --git a/ roles/gitolite/check_fedmsg_hooks/tasks/main.yml b/ 
roles/gitolite/check_fedmsg_hooks/tasks/main.yml
index d357a7d83..bea193af1 100644
--- a/ roles/gitolite/check_fedmsg_hooks/tasks/main.yml
+++ b/ roles/gitolite/check_fedmsg_hooks/tasks/main.yml
@@ -8,7 +8,7 @@
 minute=10
 hour="0,12"
 user=pagure
-job="/usr/local/bin/git-check-perms /srv/git/repositories 
--check=fedmsg-hook -f"
+job="/usr/local/bin/distgit_check_hook.py"
   tags:
   - git
   - gitolite


Note, we could make this run more often as it runs in a few minutes (the forks
being the slowest namespace, the other namespace run under a minute).

Thoughts?


Pierre


signature.asc
Description: PGP signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: FBR: no CI requirements for modules

2018-04-23 Thread Pierre-Yves Chibon
Good Morning Everyone,

I re-wrote last week the script fixing the git hooks in dist-git, but its work
is getting overridden by the old script running in a cron (that Kevin fixed this
week-end).

So I would like to replace the cron running the old script with a cron running
the new script:

Here is the diff:

diff --git a/ roles/gitolite/check_fedmsg_hooks/tasks/main.yml b/ 
roles/gitolite/check_fedmsg_hooks/tasks/main.yml
index d357a7d83..bea193af1 100644
--- a/ roles/gitolite/check_fedmsg_hooks/tasks/main.yml
+++ b/ roles/gitolite/check_fedmsg_hooks/tasks/main.yml
@@ -8,7 +8,7 @@
 minute=10
 hour="0,12"
 user=pagure
-job="/usr/local/bin/git-check-perms /srv/git/repositories 
--check=fedmsg-hook -f"
+job="/usr/local/bin/distgit_check_hook.py"
   tags:
   - git
   - gitolite


Note, we could make this run more often as it runs in a few minutes (the forks
being the slowest namespace, the other namespace run under a minute).

Thoughts?


Pierre


signature.asc
Description: PGP signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


Re: Fedora and PDC

2018-04-23 Thread Lubomír Sedlář
Hello,
please include me in the planning too. I happen to know Django and PDC
a bit, and want to help.

Lubomír

Pierre-Yves Chibon píše v Pá 20. 04. 2018 v 19:34 +0200:
> Good Morning Everyone,
> 
> We have been informed thst week at the upstream devs working on the
> product-definition-center (PDC) are moving away from the project and
> are going to leave it without a maintainer. Since we adopted PDC for
> a variety of data flows, this puts us in an awkward position. :(
> 
> Ralph and I met up on Tuesday to brainstorm the list of things we
> actively use PDC for today and to come up with a contingency plan for
> how to handle them. One overarching option is for us (fedora-infra)
> to take ownership of the PDC codebase as a whole. We didn't fully
> explore this option, figuring that the codebase is large and contains
> lots of tables, endpoints, and codepaths that we didn't use nor which
> we plan to use.
> 
> Instead, below we've got the four things we use PDC for and some
> options for what to do with each.
> 
> With the exception of /modules/, one common pattern that we like is
> to investigate splitting out the "django apps" that make up PDC into
> their own projects.  We're calling these "pdc-lite", for fun. See
> more below.
> 
> * Modules
> The data in the /modules/ PDC endpoint is *also* in the MBS
> db.  Ralph's team is going to just use that and stop using pdc
> anything for modules.
> We're going to need to patch pungi, mbs for local builds, and a
> few other places.  This should be a relatively low-pain transition.
> 
> * Stream branches, branch ownership, retirement dates?
> - SLA/EOL are currently stored in PDC.
> - Queried by releng scripts for retirement, fedrepo-req for new
> branches, etc..
> option #1
>   git repo full of yaml file similar to the override repo
>   compiled into a single JSON blob
>   Single place for all retired packages
>   This feels like the lowest tech option.
>   git gives us change control for free... but people easily get
> lost in the
>   "UX" of navigating a gigantic git repo full of plaintext files.
> option #2
>   pagure's DB/API
>   pagure knows nothing about branches currently, so that would be
> bigger
>   lift
> option #3
>   PDC internally is composed of ~20 "django apps"
>   https://github.com/product-definition-center/product-definition
> -center/tree/master/pdc/apps
>   We could pick the 2 or 3 that comprise the branches feature,
> copy them
>   out, and turn them into their own service: the "branch
> definition center":
>   BDC.
>   That would be the "pdc-lite" approach mentionned above, ie: PDC
> with only
>   the "app" of interest
> 
> * release/life-circle tracking?
> option #1:
>   PDC lite with just that app of interest
> option #2:
>   JSON/yaml file on the proxies
> option #3:
>   pkgdb-lite
> option #4:
>   ???
>   compose tracking?
> impacted: fedfind
> option #1:
>   PDC-lite with just that app of interest
> option #2:
>   Drop this entirely?
>   Adam probably really wants to keep the record of composes.
> option #3:
>   ???
> 
> The "pdc-lite" options are attractive, across the board.  One thing
> we get from this is greater clarity when discussing things formerly
> in PDC.  If something is in the branch-definition-center, the
> compose-definition-center, or the release-definition-center.. you
> know what you're talking about.  Today, when talking about whether or
> not something should be or is in "PDC", it is easy to get confused.
> 
> I propose we start the discussion on the list and plan for a meeting
> sometime late next week to discuss it further with the interested
> parties (please signal yourself)
> 
> 
> What do you think?
> 
> Pierre and Ralph
> 
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-leave@lists.fedoraproj
> ect.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org