August 2017 - infrastructure - Fedora mailing-lists

About JS framework
by Pierre-Yves Chibon 17 Oct '22

17 Oct '22

Good Morning Everyone, Our infrastructure is mostly a python store, meaning almost all our apps are written in python and most using wsgi. However in python we are using a number of framework: * flask for most * pyramid for some of the biggest (bodhi, FAS3) * Django (askbot, Hyperkitty) * TurboGears2 (fedora-packages) * aiohttp (python3, async app: mdapi) While this makes sometime things difficult, these are fairly standard framework and most of our developers are able to help on all. However, as I see us starting to look at JS for some of our apps (fedora-hubs, wartaa...), I wonder if we could start the discussion early about the different framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to look at the recommended one instead of picking one up semi-randomly. So has anyone experience with one or more JS framework? Do you have one that would you recommend? Why? Thanks for your inputs, Pierre

10 12

[patch] Another oldschool badges cron mapping
by Justin W. Flory 13 Sep '17

13 Sep '17

Hey folks, I have another quick and simple patch attached for the ansible.git repo. This one adds a mapping for the DotNet SIG's FAS group to their new badge that was just pushed up. Let me know if anything else is needed. Thanks! -- Cheers, Justin W. Flory jflory7(a)gmail.com

3 3

proxy01 logs
by Stephen John Smoogen 07 Sep '17

07 Sep '17

Proxy01 paged on a disk space issue this evening. Half of the disk space usage was journal logs. I vacuumed them down to 30 days which gave us about 2GB free. The other disk usage is koji.fedoraproject.org and kojipackages.fedoraproject.org which are using 1.8GB of disk space in the last 24 hours. The lion share of this log is 10.5.125.62 - - [31/Aug/2017:04:02:16 +0000] "POST /kojihub HTTP/1.1" 200 4118 "-" "koji/1" (with the POST being the size of whatever koji02.phx2.fedoraproject.org. is pushing to koji.fedoraproject.org (which somehow sounds weird).) -- Stephen J Smoogen.

2 2

Delta RPMs for F26
by Ron Yorston 05 Sep '17

05 Sep '17

Hello, Over on the users mailing list we've been wondering why delta RPMs don't seem to be available for F26. Any ideas, infrastructure people? Ron

2 1

[release] fedmsg_meta_fedora_infrastructure: 0.21.0
by Pierre-Yves Chibon 24 Aug '17

24 Aug '17

Good Morning Everyone, I just cut a new release of fedmsg_meta_fedora_infrastructure: 0.21.0 ------ Pull Requests - (@ralphbean) #440 Test and handle output from "modular" compose messages. https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/440 - (@pypingou) #441 Add support for the CI messages: ci.pipeline.complete https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/441 It is already uploaded to pypi and the RPMs for F28, F27, F26, F25 and epel7 are building. Seeing the changelog, I will be pushing it to staging and production fairly quickly (also because I know that the CI pipeline folks are waiting on this for their work). Happy messaging, Pierre

1 0

Plans for Thursday 2017-08-24 Fedora Infrastructure Meeting
by Stephen John Smoogen 24 Aug '17

24 Aug '17

= Introduction = We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs. = Meeting start stuff = #startmeeting Infrastructure (2017-08-24) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 dgilmore threebean pingou puiterwijk pbrobinson = Let new people say hello = #topic New folks introductions = Status / Information / Trivia / Announcements = (We put things here we want others on the team to know, but don't need to discuss) (Please use #info <the thing> - your name) #topic announcements and information #info PHX2 Colo Trip, Dec 4th - 9th #info FLOCK at Cape Cod Aug 29th - Sep 1st #info beta freeze coming up 2017-09-05 - everyone #info Moving .stg. ips ongoing = Things we should discuss = We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus /suor decision or just brainstorm a problem or issue. If there are none of these we skip this section. (Use #topic your discussion topic - your username) #topic = Apprentice office hours = #topic Apprentice Open office hours Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. = Learn about some application or setup in infrastructure = (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the i/nfo in this section. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) #topic Learn about: Nothing was put here this week = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

Bodhi 2.10.1 in production
by Jeremy Cline 23 Aug '17

23 Aug '17

Hey folks, Bodhi 2.10.1 is now running in production. The change log: https://bodhi.fedoraproject.org/docs/release_notes.html At this time, the Greenwave integration is configured to be off. When Greenwave is ready, we'll be able to flip on the integration. -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

4 7

[release] fedmsg-1.0.0
by Jeremy Cline 22 Aug '17

22 Aug '17

Hey folks, I've tagged fedmsg-1.0.0[0] and it's available on PyPI[1]. The headlines for this release are re-organized documentation[2] and Python 3 support. Since this is the first release with Python 3 support and the test coverage is approximately 60 percent, it's likely there are still issues. Please report any issues you encounter :) [0] https://github.com/fedora-infra/fedmsg/releases/tag/1.0.0 [1] https://pypi.python.org/pypi/fedmsg/1.0.0 [2] https://fedmsg.readthedocs.io/en/stable/ -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

1 0

[release] pagure-dist-git: 0.6
by Pierre-Yves Chibon 21 Aug '17

21 Aug '17

Good Morning Everyone, I just cut a new release of pagure-dist-git with the following changelog: * Mon Aug 21 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.6-1 - Update to 0.6 - Added a new version of the package sources logo (Ryan Lerch) - Add a log statement when querying PDC (Ralph Bean) - Simplify the gitolite rules for forks and add tests for them - Make the project flake8 valid - Slightly change text to make it less confusing, per mattdm +1 (Paul W. Frields) - Add support for the provenpackager group in pagure-dist-git - Adjust the logic to group the users and groups in a single line - Some package do not allow provenpackager access - Simplify the index_auth template so it renders faster I have tested it in stg and it behaves as expected so prod is now also running it. Happy packaging, Pierre

1 0

pungi->bodhi - where should pungi configs be stored?
by Dusty Mabe 17 Aug '17

17 Aug '17

I just created an issue in the releng pagure about $SUBJECT. Please read and weigh in on that topic. https://pagure.io/releng/issue/6971 Dusty

1 0

[PATCH] Stop nightly testing dnf composes
by lubomir.sedlar＠gmail.com 17 Aug '17

17 Aug '17

From: Lubomír Sedlář <lsedlar(a)redhat.com> When Pungi gained the ability to use DNF instead of Yym, a compose was set up to run depsolving and generate diffs against the real rawhide compose. Since regular rawhide is now using DNF, so there's nothing to compare anymore and we can get rid of this. Signed-off-by: Lubomír Sedlář <lsedlar(a)redhat.com> --- roles/releng/files/rawhide | 1 - 1 file changed, 1 deletion(-) diff --git a/roles/releng/files/rawhide b/roles/releng/files/rawhide index 78c56fd..e715fbd 100644 --- a/roles/releng/files/rawhide +++ b/roles/releng/files/rawhide @@ -1,5 +1,4 @@ # rawhide compose MAILTO=releng-cron(a)lists.fedoraproject.org 15 5 * * * root TMPDIR=`mktemp -d /tmp/rawhide.XXXXXX` && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && LANG=en_US.UTF-8 ./nightly.sh && sudo -u ftpsync /usr/local/bin/update-fullfiletimelist -l /pub/fedora-secondary/update-fullfiletimelist.lock -t /pub fedora fedora-secondary -15 17 * * * root TMPDIR=$(mktemp -d /tmp/rawhide-dnf.XXXXXX) && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && LANG=en_US.UTF-8 ./nightly-dnf.sh 15 18 * * * root TMPDIR=$(mktemp -d /tmp/rawhide-modular.XXXXXX) && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && LANG=en_US.UTF-8 ./nightly-modular.sh -- 2.9.5

1 0

SSH known_hosts changed
by Patrick Uiterwijk 17 Aug '17

17 Aug '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, As of right now, the ssh known_hosts file has been basically rewritten to use SSH CA certificates. The actual SSH keys for our servers should not have changed, but the known_hosts file has been shortened signifcantly. Do note that for some servers (specifically cloud), might have now switched from their ECDSA to RSA keys, which means that if you only had the host-specific known_hosts line, you might need to add the CA. You should be able to replace your entire ~/.ssh/known_hosts for Fedora with https://admin.fedoraproject.org/ssh_known_hosts . Please let me know if you find any hosts that don't work yet, as they should just need the hostname or domain in the list. Patrick -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJZlKCOAAoJEIZXmA2atR5Qw8MQAKqTrC1s8sMD6ujKPMIKNDrD aacmoyVIXq2gcvM/C4J/wp8yemIAXEv410xJ7+SP9fOcC49oThjqVca5pAq/Y9nS x4HWCDUNN4aQptwGOA2cwbjwopc44ClLV/oKW5NA1QEiSEfro5Op1/PM7n4iCMs4 3JWX9pSERVzuU52ewYzOubYYaaDpfOx49FW+LfmhZmFDj+NJIYet/USqmXFdDvLZ iVpWCVZ/k6DmVudofwTwa1iTgbxlx3NK6NaGHBV1D1saBg5qmUOx2g6KZlT78XH2 8SgioFZ9KYGahtDAP251BIejfHFR52/A7CBMZutN+JKriYaSRKbJZywQS5pzzz/q ay6qGs3qflSF7mGkpbpyzkFi96kFy2rHOhdnXb237kROCwSqAXRchpAYLPhf5uaZ BNPy0EPylbTBDsNff2uucCMa+BpErysKrA8R5TIt/7WdmzMBZlks0xwOhx5C9pJh Jaucy309j1GAXh0cNlMxqjuVAhrYoLbGygevFJTd++m5vrShqNfUvUV23oFwOcJd U1bjEax0GzJLz8egW0b5RyN/9TCfmEyPZ1IEsRpyKdfgeHn+i5OmyNNnIdgtarEd kzm6liilcEo+PIwGtjM5LuQLGoz8k0KlZl9wAEO9lEg8JdMqxK0ta9gjFs4QO5MK cE7/fpE6IpIfjS2kPtVV =yULk -----END PGP SIGNATURE-----

1 0

[release] fedmsg_meta_fedora_infrastructure: 0.20.0
by Pierre-Yves Chibon 16 Aug '17

16 Aug '17

Good Morning Everyone, I just cut a new release of fedmsg_meta_fedora_infrastructure: 0.20.0 ------ Pull Requests - (@mizdebsk) #426 Add processor for new Koschei message topic https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/426 - (@pypingou) #437 Add processor for the fedmsg messages published by ci.centos.org https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/437 Uploaded to pypi, will be updating the RPM shortly. Pierre

1 0

[release] fmn-1.4.0
by Jeremy Cline 16 Aug '17

16 Aug '17

Hey all, Yesterday afternoon I tagged a new FMN release and pushed it to stg[0]. The changelog for this release can be found on GitHub[1]. [0] https://apps.stg.fedoraproject.org/notifications/ [1] https://github.com/fedora-infra/fmn/releases/tag/1.4.0 -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

1 0

Infra tags changes
by Patrick Uiterwijk 16 Aug '17

16 Aug '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, As of a bit ago, I have made a few small changes to the Infrastructure tags in koji. The basic change is that now, after you tagged it $dist-infra-candidate (or built for the "$dist-infra" target), it will still get signed, but NOT tagged into $dist-infra. Instead, the build will be tagged into $dist-infra-stg. This is an additional set of tags that gets put into a set of repositories enabled on staging, but not production, machines. This allows you to test the build thoroughly. After you have tested the build, you can promote it to production. For instructions on that, see the Promoting topic in [1], but in short it's really just a koji move. If you need any more information, just let me know. Regards, Patrick [1]: https://infrastructure.fedoraproject.org/infra/docs/docs/sysadmin-guide/sop… -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJZjdYTAAoJEIZXmA2atR5QnIcP/3OqZDGzq9cV+2xCzzOQH5fL toWCLUwFKolVpD1PCauN7jhGEWt2wLaQlnO7MCWCN7vv+f4pu4zS6vwNt8zNPEFI V3Zs10P45s/m4SAOoOOggGtNz7RoVTh9Mg1ZVTmqJixafT8GI/tJir3W2WxcS3mC MPHbRRi5GbFgC47Em0XTJPtf+cCY1BtqMuW8MwC5IKA+MVRHsZhsCbezpowcqMMi 1At/1UuHTkhoCjcb3+bEoIGJLSivoYeK2Z2TXld2o8J9oOGxY8EGJ4RDPTmMQQZK ZQ/W2EiEGGM8QCE67XVf5Ff8tE7/y0a1381y6d34wbgz5Hk4bvZ2WKXcjcefLy2w yo2+EqCHDaWVBf6g9SgvUBN8jmIOP/35s4LLfDkySzl8WQOpQgt3NE4jKpUQYLOW sxETK/E7E8qvtunsY+rEpoTj0ovzZnKNpmHI8Gx2IbxGeKRsjKYuA5AtGz/nb0Tv 0AbWJPl9Wn8ujA8kkpEssT5eQfiuiiot8c0W4QnwXE+3FU4Tf5mCYZEW05ulxoeU Jr0mG6SzywwdfD6LHZZa0lQsqriYCgv3rS4jlDOOLiMHY8ulfvk1wJxYnhufzL04 pGWA+DGQVy25K7boA2Bgr+q6bGEkkkg4b9bL1JGvPqSa4Bs4/03VwnBcBgYYTDwa L301mf7iJMuMqBxg+/8P =G2qN -----END PGP SIGNATURE-----

2 2

[Fedocal] Reminder meeting : Bodhi stakeholder's meeting
by bowlofeggs＠fedoraproject.org 15 Aug '17

15 Aug '17

Dear all, You are kindly invited to the meeting: Bodhi stakeholder's meeting on 2017-08-15 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Source: https://apps.fedoraproject.org/calendar/meeting/4671/

1 0

bodhi-2.10 beta in staging
by Jeremy Cline 15 Aug '17

15 Aug '17

Hey all, As of a few minutes ago, the Bodhi-2.10 beta is running in stg[0]. Check out the release notes[1] for the features and bugfixes included in this release and take them for a test drive! [0] https://bodhi.stg.fedoraproject.org/ [1] https://bodhi.stg.fedoraproject.org/docs/release_notes.html#id1 -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

1 0

Proposal: Use a calendar to limit rate of change
by Randy Barlow 12 Aug '17

12 Aug '17

Hello! I was chatting with puiterwijk this morning (well, I guess his afternoon ☺) about the difficult week the systems team has had. There were quite a few changes all happening at once this week: * The update/reboot cycles * RHEL 7.4 was released * Pagure over dist-git was turned on * Bodhi was reconfigured to talk to Pagure instead of Pkgdb * A fedmsg update * More things? Patrick told me that it's been a huge amount of work for him and I assume others this week, because many of the above didn't go so smoothly. I think it's expected and frankly normal for updates to not go smoothly - we are all stretched pretty thin and we don't have a formal QE team to make sure that our infra apps are ready to ship. Thus, I think we should expect changes like the above to be "bumpy" and instead should develop a plan to help smooth out the bumps. I propose that we use our infra calendar (or even a new calendar if preferred) to more formally schedule infrastructure changes, with the goal being to avoid weeks like this one (where so many large changes landed at once). i.e., if I want to make a Bodhi deployment on Monday and I see that there's a Pagure deployment already scheduled for Monday, I should consider a different day. Of course, we can always have exceptions. Sometimes we might have "flag days" where we do want/need two apps to upgrade together. Or maybe sometimes we do want to take advantage of an update/reboot cycle to sneak in an app upgrade, if the systems team is comfortable of course. That's fine when needed, but when not needed I think spreading out the changes will help our systems team avoid insane weeks like this one. Thoughts?

2 1

How to contribute?
by Reza Seyf 12 Aug '17

12 Aug '17

Hello group, I'm new to this mailing list and I want to ask for help to contribute in Fedora infrastructure. Is there any ways to figure out how do you work in infrastructures of Fedora project? Thanks. Reza

3 3

Meeting Agenda Item: Introduction Yoann
by YLB 11 Aug '17

11 Aug '17

Hello world! :-) A quick intro following the checklist on the wiki: - My IRC handle: vbird. - Skills I have: Linux sysadmin for roughly 15 years (including 13+ in a professional capacity); PHP developer in my early years; system scripting (mostly bash and Perl); VoIP / SIP with Asterisk (at a time it still looked like a revolution!); virtualisation (but mostly proprietary products); dozens of irrelevant technos that--if mentioned--would probably make some of us suddenly feel older; Indian food cooking (says my wife...) - Skills I'd like to learn (or improve): Python (a bit rusty), Ruby, Ansible, Docker & OpenShift, KVM, OpenStack, anything else that could be fun playing with. - Associations I have: not a lot anymore (I was more active when I was younger). Self-employed with customers mostly in the financial sector. - Location & timezone: Luxembourg, CET/UTC+1 (or CEST/UTC+2 in the summer.) - What to work on: first things first, joining the fi-apprentice group to have a look at how things work here. Cheers, Yoann E. A. Le Bihan [[ www.Yoann.info ]]

1 0

[patch] Add oldschool mapping for LXQt SIG badge to FAS group
by Justin W. Flory 11 Aug '17

11 Aug '17

Hi all, Attached is a patch to the ansible repo to add a mapping for the LXQt SIG FAS group to their badge. The purpose of doing this is that it automatically awards the badge to all current members of the SIG when the cronjob runs. If someone could review this and merge it in, it would be appreciated. :) Thanks! -- Cheers, Justin W. Flory jflory7(a)gmail.com

2 1

Metrics for Mailman & HyperKitty
by Aurelien Bompard 11 Aug '17

11 Aug '17

Hey folks! Unless I'm mistaken, we currently don't have many useful technical metrics about Mailman and HyperKitty. I've started writing a simple script that would collect those and output something we can eventually graph. It currently uses the "key: value" format that I've seen a lot of monitoring tools use, but I can adapt that to whatever we need. I'm currently getting the following values : - mailinglist count in HyperKitty - email count in HyperKitty - email senders count in HyperKitty - user count in HyperKitty - async task queue size - number of async tasks run per minute - async tasks average exec time - size of the archiving queues in mailman and hyperkitty (should be zero most of the time) - Mailman's shunt queue (for messages it failed to handle, usually encoding problems) Do you think there would be other values that we would need? My aim is to detect issues with the server usage (say, a spam attack) as well as anticipate growth. Another useful metric would be the number of emails sent by the system, but I guess we already have a Postfix plugin somewhere, so I'm trying to stay mailman & hyperkitty-specific here. Currently the plugin takes between 5 and 10 seconds to collect the data. I don't know how precise we want our metrics but a run every five minutes seems sufficient to me. It also depends on how we can set that in collectd, which I don't know (yet!). Thanks! Aurélien

2 3

[release] pdc-updater: 0.6.0
by Ralph Bean 10 Aug '17

10 Aug '17

A new pdc-updater release! There are a few bugfixes related to the MBS, but crucially there is a new handler for propagating retirement: When a `dead.package` file gets committed, the code here (on pdc-backend0*) will update the EOL of that branch in PDC, indicating retirement. 0.6.0 ----- Pull Requests - (@ralphbean) #57, srpm_nevra must not be set when arch is src. https://github.com/fedora-infra/pdc-updater/pull/57 - (@ralphbean) #62, Force creation of parent with type during initialization. https://github.com/fedora-infra/pdc-updater/pull/62 - (@ralphbean) #60, Populate the dist_git_branch value... https://github.com/fedora-infra/pdc-updater/pull/60 - (@ralphbean) #61, Also construct container tags from stable updates tags. https://github.com/fedora-infra/pdc-updater/pull/61 - (@mprahl) #63, Add a handler so that PDC branches are EOL'd when the branch is retired https://github.com/fedora-infra/pdc-updater/pull/63 - (@mprahl) #64, Add some missing doc strings to RetireComponentHandler https://github.com/fedora-infra/pdc-updater/pull/64 - (@ralphbean) #66, Some changes to the retirement handler... https://github.com/fedora-infra/pdc-updater/pull/66 Commits - 6118478b5 srpm_nevra must not be set when arch is src. https://github.com/fedora-infra/pdc-updater/commit/6118478b5 - 600b6175e Populate the dist_git_branch value... https://github.com/fedora-infra/pdc-updater/commit/600b6175e - 17edf56ad Also construct container tags from stable updates tags. https://github.com/fedora-infra/pdc-updater/commit/17edf56ad - 7a022d494 Force creation of parent with type during initialization. https://github.com/fedora-infra/pdc-updater/commit/7a022d494 - b7341977a Add a handler so that PDC branches are EOL'd when the branch is retired https://github.com/fedora-infra/pdc-updater/commit/b7341977a - 31f7caf33 Break retirement out into its own staticmethod. https://github.com/fedora-infra/pdc-updater/commit/31f7caf33 - e2eeec935 Write an init method. https://github.com/fedora-infra/pdc-updater/commit/e2eeec935 - e132ab502 Add Docstrings to RetireComponentHandler https://github.com/fedora-infra/pdc-updater/commit/e132ab502 - e2d52896c Add the audit function to the RetireComponentHandler handler https://github.com/fedora-infra/pdc-updater/commit/e2d52896c - bcb112faa Add some missing doc strings to RetireComponentHandler https://github.com/fedora-infra/pdc-updater/commit/bcb112faa - 3a2cef32e Make these two work functions re-try-able. https://github.com/fedora-infra/pdc-updater/commit/3a2cef32e - fe8af401d Check pagure instead of cgit. https://github.com/fedora-infra/pdc-updater/commit/fe8af401d - e1b0542b4 Fix those mocks. https://github.com/fedora-infra/pdc-updater/commit/e1b0542b4

1 0

[release] fedmsg-0.19.1
by Jeremy Cline 10 Aug '17

10 Aug '17

Hey all, Last night I tagged the 0.19.1 release of fedmsg to fix a few critical issues found in 0.19.0. It's currently only built into the Fedora infra repositories. It will be making its way out to Fedora and EPEL testing repositories near you in the next day or two. Change log: https://github.com/fedora-infra/fedmsg/releases/tag/0.19.1 -- Jeremy Cline XMPP: jeremy(a)jcline.org IRC: jcline

1 0

Plans for Thursday 2017-08-10 Fedora Infrastructure Meeting
by Stephen John Smoogen 10 Aug '17

10 Aug '17

We will have our normal Thursday Fedora Infrastructure Meeting at 1800 UTC on #fedora-meeting. The agenda currently looks as follows on the gobby page. Please add or update as needed. = Meeting start stuff = #startmeeting Infrastructure (2017-08-10) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 dgilmore threebean pingou puiterwijk pbrobinson = Let new people say hello = #topic New folks introductions = Status / information / Trivia / Announcements = (We put things here we want others on the team to know, but don't need to discuss) (Please use #info <the thing> - your name) #topic announcements and information #info PHX2 Colo Trip coming up, Dec 4th - 9th #info FLOCK at Cape Cod Aug29->Sep01 #info Fedora F27 Rebuild (going on now) #info Updated of all servers has been messy kevin/smooge/patrick/relrod #info Bodhi 2.9.0 released. Deployment planned for Monday - bowlofeggs = Things we should discuss = We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus /suor decision or just brainstorm a problem or issue. If there are none of these we skip this section. (Use #topic your discussion topic - your username) #topic Update cycles. Lessons learned? #info the last couple of updates cycles have been hard #info different reasons each time but how can we do better? = Apprentice office hours = #topic Apprentice Open office hours Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. = Learn about some application or setup in infrastructure = (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the i/nfo in this section. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) #topic Learn about: Nothing was put here this week = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure August 2017