Fedora Release Engineering meeting summary for 2014-01-20
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=========================
#fedora-meeting-1 Meeting
=========================
Meeting started by dgilmore at 16:38:24 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-20/releng.2014-...
.
Meeting summary
- ---------------
* whos here (dgilmore, 16:38:39)
* tickets (dgilmore, 16:39:52)
* LINK: https://fedorahosted.org/rel-eng/report/10 (dgilmore,
16:39:54)
* LINK: https://fedorahosted.org/rel-eng/report/1 (dgilmore,
16:59:02)
* LINK: https://fedorahosted.org/rel-eng/ticket/5808 - seems to be
done as far as I understand (tyll, 16:59:16)
* LINK: https://fedorahosted.org/rel-eng/ticket/1501 (dgilmore,
17:01:54)
* LINK: https://fedorahosted.org/rel-eng/ticket/5362 needs analysis to
see if it would break anything (dgilmore, 17:04:21)
* LINK: https://fedorahosted.org/rel-eng/ticket/5757
https://fedorahosted.org/rel-eng/ticket/5761 are requests for f20
tags for gnome and kde - I assume the tickets can be closed as well
(tyll, 17:05:22)
* LINK: https://fedorahosted.org/rel-eng/ticket/3903 needs feedback
from abadger1999 (dgilmore, 17:05:33)
* LINK: https://fedoraproject.org/wiki/Adding_Side_Build_Targets_SOP i
guess we should add something there (dgilmore, 17:16:53)
* followup from last week (dgilmore, 17:39:22)
* open floor (dgilmore, 17:42:56)
Meeting ended at 17:49:52 UTC.
Action Items
- ------------
Action Items, by person
- -----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
- ---------------------------
* dgilmore (107)
* tyll (23)
* sharkcz (8)
* dwa (7)
* lmacken (6)
* nirik (5)
* abadger1999 (5)
* zodbot (3)
* masta (2)
* janeznemanic (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJS3WKuAAoJEH7ltONmPFDR0j4QAMZw89JN8WR+lRJUB/kT+UoW
KmRglt5AGEGehJpKEF8uSWuj9rwz5g3+idp/2TPYfBTs6XXOg7s7IolfslZPApvq
GSQXX4dKvR5D1Kva3j+OIqEc1HPVMQZdDWIrxCXZ89FadUpCray0/8XtcTDw9fa9
yxhQqDJ03qnKHYhsQXwco0/buBjxJPAAqIgNJbe+xJVqJexio63NjpD9o+qV8vNZ
t6nqmZEr0pefwx1oQyBmBzurtV9oGVMa0xh4LoUOI7vMELapVV/QLzew2R0ScjDr
4PhiUk4qMdS4pAKlC9LpiqsmDwqgVtYKyXo/Hi+A0JXuYiUPu8C6/d3DtbaQ0RHS
IWf4hYnYom/YOwfKUDD70pbG4mVS9hnQEzJ2dS7y9pj9SEs2SGIjCNJ9lgQ+xKda
r3PUsQOQXghSETvQd1SwLTvDRYvlYDd0tKrFLCDfs8vd4RK3oAttSlBVPKVTrWyK
neQ0hP9qcgdOFzW3LzPohJCqHdEjp3ec9n7j5joSilOCDooOyqtkS6q414xpOIaG
S+I6RKo9T51hhOjXRsNRABoBprfB38GiDRUyy+rnf4bVLHzozdaqDjhOmS6H8Mev
w7SR5mIZ/pjEcQqtf13IpuMtCFIjHO+jZMUsOyxLYemTYIrqbJYegazakbGqsXnh
BuwcP7DAgrdX7usJF54j
=5ot/
-----END PGP SIGNATURE-----
10 years, 2 months
Fedora Docs Meeting Minutes 20JAN2014
by Pete Travis
====================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings
====================================================================================================
Meeting started by randomuser at 14:02:10 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting/2014-01-20/fedora_docs.20...
.
Meeting summary
---------------
* Roll Call (randomuser, 14:02:10)
* LINK: https://fedorahosted.org/fesco/ticket/1222 and
https://fedorahosted.org/fesco/ticket/1224 (jreznik, 14:09:56)
* jreznik's fedora.next jamboree (randomuser, 14:10:22)
* Publican4/Publishing (randomuser, 14:19:27)
* Koji is setup for accepting SRPMs but we're having problems getting
Koji to actually build them. We continue to troubleshoot.
(Sparks_too, 14:20:47)
* The new backend server is operational and is awaiting packages from
Koji to be setup completely. (Sparks_too, 14:21:26)
* We'll be running Publican 4 on the backend and RPMs will be made
available via the repos. (Sparks_too, 14:22:22)
* ACTION: Sparks to update publishing documentation. (Sparks_too,
14:30:31)
* Centos Docs (randomuser, 14:31:44)
* LINK: http://lists.centos.org/mailman/listinfo/centos-docs
(randomuser, 14:34:28)
* el7 and Fedora will have a lot in common, and centos has a docs
group (randomuser, 14:34:57)
* guides (randomuser, 14:39:32)
* Sparks is reworking the Security Guide, talk to him if you want to
help (randomuser, 14:52:53)
* LINK: https://fedoraproject.org/wiki/Category:Docs_Project_tasks
(randomuser, 14:55:41)
* use the task table to ask for and find tasks (randomuser, 14:55:59)
* Open Floor (randomuser, 14:57:53)
* ACTION: randomuser to send email to docs list about FAD scheduling
for weekend of 21MAR2014, give opportunity for protest (randomuser,
15:01:51)
* LINK: https://fedoraproject.org/wiki/Docs_FAD_2014 (randomuser,
15:04:50)
* ACTION: jhradilek to update docs FAD page for brno attendees
(randomuser, 15:06:21)
Meeting ended at 15:11:05 UTC.
Action Items
------------
* Sparks to update publishing documentation.
* randomuser to send email to docs list about FAD scheduling for weekend
of 21MAR2014, give opportunity for protest
* jhradilek to update docs FAD page for brno attendees
Action Items, by person
-----------------------
* jhradilek
* jhradilek to update docs FAD page for brno attendees
* randomuser
* randomuser to send email to docs list about FAD scheduling for
weekend of 21MAR2014, give opportunity for protest
* Sparks
* Sparks to update publishing documentation.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* randomuser (93)
* sgordon (26)
* Sparks_too (21)
* Sparks (19)
* jreznik (15)
* pbokoc (13)
* jjmcd (8)
* lnovich (8)
* jhradilek (7)
* Capesteve (7)
* zodbot (6)
* roshi (2)
* ciupicri (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
10 years, 2 months
APAC meeting minutes 2014-01-18
by Truong Anh Tuan
Hi folks,
We have a good meeting today with a lot of discussion on upcoming events:
FOSSASIA and FUDCon APAC 2014.
Please kindly check out the meeting logs for more information.
Btw, it is time to plan the budget in FY2015. If you have any events or
activities, please make it added to the APAC plan (otherwise, we can not
have fund for them).
<zodbot> Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2014-01-18/apac.2014-01-1...
<zodbot> Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2014-01-18/apac.2014-01-1...
<zodbot> Log: http://meetbot.fedoraproject.org/fedora-meeting/2014-01-18/apac.2014-01-1...
=======================
#fedora-meeting Meeting
=======================
Meeting started by tuanta at 04:02:08 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2014-01-18/apac.2014-01-1...
.
Meeting summary
---------------
* Rollcall (tuanta, 04:02:22)
* Tickets (tuanta, 04:05:51)
* LINK: https://fedorahosted.org/fedora-apac/report/9 (tuanta,
04:06:01)
* LINK: https://fedorahosted.org/fedora-apac/ticket/111 (udinnet,
04:07:06)
* AGREED: Approve udinnet's funding request to FOSSASIA (Trac ticket
#111) (tuanta, 04:15:58)
* ACTION: tuanta to modify the ticket #111 (tuanta, 04:16:23)
* ACTION: tuanta to check with jsimon if FOSSASIA event owner can
reimburse some attendees (tuanta, 04:18:51)
* LINK: https://fedorahosted.org/fedora-apac/ticket/112 -> ticket that
we filed for this (FranciscoD, 04:23:08)
* LINK: https://fedorahosted.org/fedora-apac/ticket/112#comment:2 ->
detailed explanation (FranciscoD, 04:26:20)
* LINK: https://fedorahosted.org/fedora-apac/ticket/115 (tuanta,
04:27:46)
* LINK:
https://fedoraproject.org/wiki/Ambassadors/APAC/Reimbursement#Travel_Subs...
(tuanta, 04:31:20)
* ACTION: tuanta to discuss about "Funding other Fedora contributors
(not ambassadors)" from regional budget in FAmSCo (tuanta,
04:37:34)
* AGREED: Approve banas's funding request to FOSSASIA (Trac ticket
#115) (tuanta, 04:41:04)
* ACTION: tuanta to modify the ticket #115 (tuanta, 04:41:22)
* LINK: https://fedorahosted.org/fedora-apac/ticket/107 (tuanta,
04:41:57)
* AGREED: Approve funding request to for accommodation in FOSSASIA
(Trac ticket #107) (tuanta, 04:47:58)
* ACTION: tuanta to modify the ticket #107 (tuanta, 04:48:16)
* FUDCon APAC 2014 (tuanta, 04:50:01)
* LINK: https://fedoraproject.org/wiki/FUDCon:Bid_for_Beijing_2014
(tuanta, 04:50:20)
* LINK:
https://fedoraproject.org/wiki/FUDCon:Bid_for_Beijing_2014#Transportation...
(tuanta, 04:55:26)
* ACTION: zsun to break down budget for travel and hotel separately of
FUDCon Beijing Bidding (zsun, 04:59:13)
* ACTION: zsun talk with the team on the travel budget for FUDCon
Beijing Bidding (tuanta, 05:02:25)
* LINK: https://fedoraproject.org/wiki/FUDCon:Bid_for_Beijing_2014
(tuanta, 05:09:32)
* ACTION: tuanta to send out a WhenIsGood to the mailing list arrange
a special meeting for FUDCon APAC 2014 discussion (tuanta,
05:13:07)
* ACTION: everyone to read the bidding wiki before that meeting
(tuanta, 05:13:58)
* Open floor (tuanta, 05:14:12)
* LINK: http://www.oanda.com/currency/converter/ (tuanta, 05:19:43)
Meeting ended at 05:22:55 UTC.
Action Items
------------
* tuanta to modify the ticket #111
* tuanta to check with jsimon if FOSSASIA event owner can reimburse some
attendees
* tuanta to discuss about "Funding other Fedora contributors (not
ambassadors)" from regional budget in FAmSCo
* tuanta to modify the ticket #115
* tuanta to modify the ticket #107
* zsun to break down budget for travel and hotel separately of FUDCon
Beijing Bidding
* zsun talk with the team on the travel budget for FUDCon Beijing
Bidding
* tuanta to send out a WhenIsGood to the mailing list arrange a special
meeting for FUDCon APAC 2014 discussion
* everyone to read the bidding wiki before that meeting
Action Items, by person
-----------------------
* tuanta
* tuanta to modify the ticket #111
* tuanta to check with jsimon if FOSSASIA event owner can reimburse
some attendees
* tuanta to discuss about "Funding other Fedora contributors (not
ambassadors)" from regional budget in FAmSCo
* tuanta to modify the ticket #115
* tuanta to modify the ticket #107
* tuanta to send out a WhenIsGood to the mailing list arrange a
special meeting for FUDCon APAC 2014 discussion
* zsun
* zsun to break down budget for travel and hotel separately of FUDCon
Beijing Bidding
* zsun talk with the team on the travel budget for FUDCon Beijing
Bidding
* **UNASSIGNED**
* everyone to read the bidding wiki before that meeting
People Present (lines said)
---------------------------
* tuanta (131)
* FranciscoD (60)
* udinnet (40)
* zsun (22)
* zodbot (18)
* MavJS (17)
* banas (16)
* gnokii (11)
* MarioB (8)
* dramsey (6)
* hongphuc_ (4)
* bochecha (1)
* gnokii_ (1)
* niteshnarayanlal (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Kind regards,
Tuan
10 years, 2 months
Summary/Minutes from today's Fedora Infrastructure meeting (2014-01-16)
by Kevin Fenzi
============================================
#fedora-meeting: Infrastructure (2014-01-16)
============================================
Meeting started by nirik at 19:00:13 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2014-01-16/infrastructure...
.
Meeting summary
---------------
* welcome all planets of the solar federation (nirik, 19:00:13)
* New folks introductions and Apprentice tasks (nirik, 19:02:30)
* LINK:
http://infrastructure.fedoraproject.org/csi/security-policy/en-US/html-si...
(willo, 19:08:01)
* Applications status / discussion (nirik, 19:15:00)
* LINK: https://apps.fedoraproject.org/datagrepper (threebean,
19:16:22)
* LINK: https://apps.fedoraproject.org/packages (threebean,
19:16:28)
* new packages app ( epel bugs and enhancements) and datagrepper (new
frontpage and fixes) rolled out last week. (nirik, 19:25:26)
* new askbot in stg is almost working. need to fix email sending then
we can schedule prod upgrade (nirik, 19:25:51)
* hyperkitty roll out moving forward. Will make prod instances soon
and start figuring out forwarding setup. (nirik, 19:26:23)
* ACTION: nirik to write up a infra list post about how mailing lists
are setup now, so we can decide how to add in mailman3/hyperkitty.
(nirik, 19:31:03)
* new coprs rolled out today (nirik, 19:31:24)
* Sysadmin status / discussion (nirik, 19:34:32)
* Upcoming Tasks/Items (nirik, 19:43:47)
* LINK: https://apps.fedoraproject.org/calendar/list/infrastructure/
(nirik, 19:43:47)
* goal: finish round 1 of development and deploy fmn to production by
the end of January. (threebean, 19:44:50)
* Open Floor (nirik, 19:45:43)
* LINK: https://fedoraproject.org/wiki/Jenkins@infra (nirik,
19:46:51)
* LINK: http://fedoraproject.org/wiki/Infrastructure/Architecture
there is a high overview (zemmiph0bia, 19:48:12)
* LINK: https://admin.fedoraproject.org/nagios/ (nirik, 19:49:51)
Meeting ended at 19:59:30 UTC.
Action Items
------------
* nirik to write up a infra list post about how mailing lists are setup
now, so we can decide how to add in mailman3/hyperkitty.
Action Items, by person
-----------------------
* nirik
* nirik to write up a infra list post about how mailing lists are
setup now, so we can decide how to add in mailman3/hyperkitty.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* nirik (120)
* willo (36)
* threebean (28)
* johe_ (11)
* abompard (10)
* adimania (9)
* zemmiph0bia (8)
* danofsatx (8)
* relrod (6)
* zodbot (4)
* kamina1 (4)
* smooge (4)
* dgilmore (4)
* janeznemanic (3)
* jlar (3)
* tflink (1)
* jsmith (1)
* lmacken (1)
* LoKoMurdoK (1)
* mdomsch (0)
* puiterwijk (0)
* abadger1999 (0)
* pingou (0)
--
19:00:13 <nirik> #startmeeting Infrastructure (2014-01-16)
19:00:13 <zodbot> Meeting started Thu Jan 16 19:00:13 2014 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:13 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:00:13 <nirik> #meetingname infrastructure
19:00:13 <nirik> #topic welcome all planets of the solar federation
19:00:13 <nirik> #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk
19:00:13 <zodbot> The meeting name has been set to 'infrastructure'
19:00:13 <zodbot> Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean
19:00:26 * relrod waves
19:00:42 * lmacken
19:00:44 * abompard is here
19:00:46 * threebean is here
19:00:50 * adimania is here
19:01:04 * johe_ (new one) is here
19:01:36 * jsmith is lurking
19:01:37 <dgilmore> hola
19:01:42 * jlar is new here
19:01:47 <zemmiph0bia> morning :) (New)
19:01:50 * willo is here
19:02:16 * tflink is lurking
19:02:16 <nirik> cool. Nice crowd today. ;)
19:02:30 <nirik> #topic New folks introductions and Apprentice tasks
19:02:46 <nirik> any new folks like to give a short bio/intro? or apprentices with questions or comments?
19:02:54 * nirik sees a number of new folks today
19:03:04 <johe_> okay
19:03:39 <johe_> i introduced already to the list, so hi again, i am a 34 year old systemadministrator and would like to help
19:03:47 <johe_> :-)
19:03:57 <zemmiph0bia> I'm Elizabeta, developer on ratticdb and recovering sysadmin. Wanting to get added to the fi-apprentice fas group.
19:04:11 <nirik> welcome johe_ and zemmiph0bia!
19:04:19 * threebean waves "hello"
19:04:29 <adimania> Hi. I am Aditya. I graduated to sysadmin-badges a few months ago but had to take a break.
19:04:38 <nirik> happy to add you folks to our apprentice group... just see me in #fedora-admin after the meeting.
19:04:39 <threebean> adimania: welcome back :)
19:04:45 <adimania> Will get back in action and start contributing again. :)
19:04:51 <nirik> hey adimania. :) Welcome back
19:05:08 <adimania> threebean, nirik, thanks :)
19:05:25 <jlar> Hi, I'm Jon, I'm looking to keep my skills sharp as my current job doesn't have me doing a lot of linux stuff. I want to help out any way I can.
19:05:30 <nirik> johe_: you are more interested in sysadmin tasks? or application development? or both?
19:05:42 <nirik> zemmiph0bia: you are more interested in sysadmin I guess?
19:05:49 <nirik> welcome jlar.
19:05:58 <smooge> hwelcome
19:06:01 <johe_> nirik, well, the syadmin tasks would fit my skills i guess, as i am doing it every day :-)
19:06:24 <johe_> but i could/would like to take a look on development also
19:06:26 <zemmiph0bia> nirik, both. sysadmin is certainly what I'm better with but I'd like to get more into the development
19:06:35 <nirik> jlar: great. See me also after the meeting in #fedora-admin and we can help get you started. ;)
19:06:40 <nirik> zemmiph0bia: excellent.
19:06:50 <jlar> nirik: sounds good!
19:07:13 <nirik> #fedora-admin is our main channel, we also have #fedora-apps for development related stuff and #fedora-noc for sysadmin/outages/etc
19:07:34 <willo> nirik: I've got a Q when the intros are done
19:07:48 <nirik> willo: fire away.
19:07:57 <willo> I found a link to this page:
19:07:58 <nirik> any other new folks?
19:08:01 <willo> http://infrastructure.fedoraproject.org/csi/security-policy/en-US/html-si...
19:08:15 <willo> from the wiki. Can't recall exactly where it was.
19:08:37 <willo> There's an associated fedora hosted project - CSI
19:08:46 <nirik> indeed there is. ;)
19:09:08 <nirik> also, we folded it into the main docs too: http://docs.fedoraproject.org/en-US/Community_Services_Infrastructure/1/h...
19:09:18 <willo> Is this current policy on how the servers should be setup?
19:09:41 <willo> Or any other guidance on the SHOULD's, SHALL's and MUST's?
19:09:41 <nirik> in theory. It's something I've really not had time to keep current...
19:10:06 <nirik> if there's people interested in working on it again we could revive it somewhat
19:10:56 <nirik> there's good info in there (although probibly dated now) about how to setup your client machine as an admin... and how to handle security incidents, etc.
19:11:00 <johe_> nirik, i would join in :-)
19:12:32 * nirik ponders the best place to discuss changes there... I guess we could just use the main infra list at least to start.
19:13:03 <johe_> +1
19:13:22 <willo> I droped from channel for last 2 mins
19:13:25 <nirik> so, yeah, read thu and propose changes. ;) it would be great to get it updated.
19:13:27 <nirik> willo: oops. ;(
19:13:31 <nirik> let me repeat:
19:13:39 <nirik> in theory. It's something I've really not had time to keep current...
19:13:44 <nirik> if there's people interested in working on it again we could revive it somewhat
19:13:48 <nirik> there's good info in there (although probibly dated now) about how to setup your client machine as an admin... and how to handle security incidents, etc.
19:14:16 <willo> Cool, great.
19:14:37 <nirik> great topic. Thanks for bringing it up willo
19:15:00 <nirik> #topic Applications status / discussion
19:15:06 <willo> I was thinking that I could wrte some SCAP contentbased on tat
19:15:11 <nirik> any applications news or plans?
19:15:25 <threebean> willo: that would be pretty sweet
19:15:30 <nirik> willo: I think there was some talk about SCAP recently... perhaps ask Sparks when he's around?
19:15:39 <willo> will do
19:16:17 <threebean> on applications new, a new datagrepper and a new fedora-packages got deployed at the end of last week
19:16:22 <threebean> https://apps.fedoraproject.org/datagrepper
19:16:28 <threebean> https://apps.fedoraproject.org/packages
19:16:35 <nirik> I have one bit of application news. :) I've been trying to get the new version of askbot working in our staging setup.
19:16:42 <nirik> threebean: any big changes?
19:16:58 <threebean> enhancements to both. charul's been working on datagrepper...
19:17:13 * LoKoMurdoK here
19:17:16 <threebean> she added that counter to the frontpage and a new html representation of messages if you look at queries in your browser.
19:17:34 <relrod> threebean: What is the goal date for deploying fmn to prod? Is there one?
19:17:55 <threebean> fedora-packages got a search bugfix - it accepts slashes correctly now.
19:18:02 <threebean> it also displays EPEL bugs in the bugs list (finally)
19:18:03 <nirik> currently: I have askbot working at https://ask.stg.fedoraproject.org/ except for the email sending. Need to figure that our and get it working, then we can repave it and redeploy and make sure it's still good and then look at updating production
19:18:11 <nirik> welcome LoKoMurdoK
19:18:24 <dgilmore> buenos dias LoKoMurdoK
19:18:42 <dgilmore> nirik: i got some emails yesterday
19:18:49 <threebean> relrod: no concrete goal date for fmn -- we never set one (although I think we just said "january")
19:19:13 <nirik> dgilmore: yeah, there was a flood of old ones. I wiped those, but it's not sending any new ones for answers, etc that I can see. ;(
19:19:19 <threebean> pkgdb2 depends on it, but it looks like pingou will be busy with other stuff before he can get around to the pkgdb2 deployment.
19:19:44 <willo> nirik: I was also looking around at askbot in stg. You saw sme of the results in fedora-noc channel. I'll try and avoid tripping the orbital defence lasers in the future. :)
19:20:26 <nirik> note to new folks: do feel free to ask questions about what things are or what someone means. ;) It's always good to explain in more detail if folks want...
19:20:35 <nirik> willo: :) no worries.
19:20:54 <willo> I saw trying to find out how my public key gets from the staging fas into my home dir's authkeys file. Apologies.
19:21:52 <nirik> willo: we can sort it out. I think it's all ok now, but if you still see any issues please let me know.
19:22:28 <relrod> heh
19:22:57 <nirik> oh, in other application news, abompard and I have been exchanging some emails on hyperkitty roll out. I'm likely going to make some production instances soon to start figuring out setup.
19:23:23 <nirik> the biggest problem is going to be setting up just single lists to forward to the new setup from the old... or otherwise make sure they don't interfere.
19:23:42 <nirik> for both web and smtp.
19:23:53 <smooge> cool
19:24:05 <threebean> abompard: how's the caching situation look these days? iirc, when we first imported messages from the old lists into the staging hyperkitty instance
19:24:09 <nirik> so, we may need folks to put on their thinking caps as to how to do that.
19:24:16 <willo> Dropped again, but just from meeting channel. No message, just gets quite and then all the nicks disappear. I'll read what I missed in the meeting notes.
19:24:25 <threebean> .. well, you were looking at caching stuff, no?
19:24:35 <abompard> Caching in hyperkitty is waaaay better now
19:24:41 <threebean> \ó/
19:24:50 <nirik> staging instance: https://lists.stg.fedoraproject.org/archives/
19:24:51 <abompard> I'm using memcached
19:25:02 <threebean> oh yeah. that's quick :)
19:25:26 <nirik> #info new packages app ( epel bugs and enhancements) and datagrepper (new frontpage and fixes) rolled out last week.
19:25:50 <abompard> threebean: actually the best improvement is when archive are imported
19:25:51 <nirik> #info new askbot in stg is almost working. need to fix email sending then we can schedule prod upgrade
19:26:23 <nirik> #info hyperkitty roll out moving forward. Will make prod instances soon and start figuring out forwarding setup.
19:26:27 <abompard> because I was using some tables as a cache, which needed rebuilding. Now the cache is populated ondemand, from the requests.
19:27:07 <abompard> well there are quite a few non-visible improvements these days. And nirik is rebuilding my test server, which will be useful
19:27:36 <nirik> abompard: lists-dev should be redone, just needs some tweaks on the ansible playbook to finish
19:27:44 <abompard> nirik: yeah, will do soon
19:28:03 <abompard> nirik: I just finish my big commit here, and I'll do that
19:28:23 <nirik> excellent.
19:28:29 <threebean> cool :)
19:29:05 <nirik> abompard: I know our schedules are different, but perhaps next week we could meet up and sort out production forwarding... or perhaps it would be good for me to write up for the list the way things are now so we can figure it there.
19:29:22 <abompard> nirik: sure
19:29:32 <nirik> let me try and do a list post and we can go from there.
19:29:43 <abompard> nirik: great
19:30:04 <nirik> I am sure we can get it working, just will be a matter of the best place to splice in the new one without messing with the old.
19:30:38 <nirik> ok, any other applications news?
19:31:03 <nirik> #action nirik to write up a infra list post about how mailing lists are setup now, so we can decide how to add in mailman3/hyperkitty.
19:31:15 <nirik> oh, another thing:
19:31:24 <nirik> #info new coprs rolled out today
19:31:41 <threebean> relrod: do you have a preference on an fmn deployment goal date?
19:31:58 <relrod> threebean: Not particularly
19:32:15 <threebean> ok, we'll sort it out in #fedora-apps then I guess.
19:32:19 <relrod> threebean: By the end of January works for me, if that is still your goal
19:32:58 <nirik> for new folks: http://copr.fedoraproject.org/ is copr... fmn is a messaging preference application, only in staging so far: https://apps.stg.fedoraproject.org/notifications
19:34:29 <nirik> ok, moving along then...
19:34:32 <nirik> #topic Sysadmin status / discussion
19:34:39 <nirik> lets see...
19:35:07 <nirik> not too much going on right now.
19:35:14 <nirik> I need to finish the ansible cron job...
19:35:26 <nirik> It sounds like folks wanted it to just run --check --diff each day
19:35:46 <nirik> I might try and migrate some more things from puppet to ansible soon.
19:36:12 <nirik> we have setup for those mailman01/02 in production pending
19:36:17 * adimania thinks that is interesting
19:36:45 <nirik> I might file a ticket asking for a script to help you make new instances in ansible.
19:36:57 <nirik> it's just a matter of copying some templates and editing them...
19:37:28 <zemmiph0bia> Are there tickets for the remaining stuff that's left in puppet that needs to get migrated?
19:37:55 * willo was wondering the same thing
19:38:02 <nirik> zemmiph0bia: there's not. it's just been 'as we get to it'. I posted a thing to the list a few weeks ago about the plan moving forward...
19:38:05 <adimania> I'll give it a shot. I understand puppet but I have very basic understanding of ansible.
19:38:18 <zemmiph0bia> adimania, ansible is exceptionally easy.
19:38:21 <nirik> if folks want to help out migrating that would be lovely.
19:38:25 <smooge> I am going to order some hardware tonight (whether it gets approved is another matter). I am doing some certs for coprs and I am catching up with other stuff from extra long vacation/disease marathon
19:38:31 <zemmiph0bia> I'd be happy to help with that, help my partner write a book on it :p
19:38:42 <nirik> zemmiph0bia: awesome!
19:38:59 <nirik> smooge: any news on that hw order? or same old same ol?
19:39:05 <willo> I'm keen to assist in the migration
19:39:28 <willo> Ansible learning experience
19:39:28 <smooge> nirik, I have heard nothing so I am going to do it anyway.
19:39:52 <nirik> some things are pretty trivial to move, just takes a bit of time... some things (like our proxy setup thats in puppet) will likely require more brainpower. ;(
19:40:02 <nirik> smooge: :(
19:40:50 <willo> So, I'm guessing as things are migrated, they're moved out of puppet pretty quickly
19:40:51 <nirik> so folks interested in ansiblle migrations bug me and I can try and get you started. :)
19:41:01 <nirik> willo: yep. We are only adding new stuff to ansible...
19:41:09 <threebean> question -> we still don't have a release schedule for Fedora 21, correct? which means we don't have a foreseeable infrastructure freeze on the horizon, correct?
19:41:12 <nirik> but we had a lot in puppet, so it's not a quick process
19:41:26 * adimania will go through http://docs.ansible.com/intro_getting_started.html before bugging nirik
19:41:27 <willo> So, anything that I can see in puppet is a list of things that need to be migrated, correct
19:41:28 <nirik> threebean: correct. we are no freezes until we know more.
19:41:33 * threebean nods
19:41:44 <threebean> that's a good thing for the migration effort ;)
19:41:56 <nirik> willo: yep. although... there's also some old junk in puppet that wasn't properly removed when things were retired...
19:42:11 <nirik> for example, I think our asterisk server is still in there, even tho it went away about 5 years ago
19:42:41 <nirik> anyhow, we will get there i hope. ;)
19:42:41 <dgilmore> there is a ton of legacy things in puppet
19:42:48 <willo> :) just to keep it interesting
19:42:52 <nirik> dgilmore: yeah. just old stuff.
19:43:35 <nirik> I still do want to do a FAD sometime (Fedora activity day, where we get folks to gather in the same physical location and work on one problem). finishing ansible migration is one possible topic.
19:43:47 <nirik> #topic Upcoming Tasks/Items
19:43:47 <nirik> https://apps.fedoraproject.org/calendar/list/infrastructure/
19:43:55 <willo> nirik: will hit you up in fedora-admin later tonight or the weekend.
19:44:01 <nirik> Anyone have upcoming tasks or items they want to schedule or note?
19:44:05 <nirik> willo: sounds good.
19:44:49 <nirik> okey dokey.
19:44:50 <threebean> #info goal: finish round 1 of development and deploy fmn to production by the end of January.
19:44:59 <nirik> sounds good. ;)
19:45:43 <nirik> #topic Open Floor
19:45:48 <nirik> any items for open floor?
19:46:00 <nirik> questions, comments, ideas, youtube videos?
19:46:23 <janeznemanic> nirik: may I ask you what is the purpose of jenkins in our cloud
19:46:51 <nirik> https://fedoraproject.org/wiki/Jenkins@infra
19:47:05 <nirik> see the 'what is' there. ;)
19:47:20 <janeznemanic> great
19:47:25 <willo> I'm a picture person. Are there currently any diagrams showing interactions between systems?
19:47:44 <willo> I understand that it would be complex, I suppose, I'm not sure just how complex
19:48:12 <zemmiph0bia> http://fedoraproject.org/wiki/Infrastructure/Architecture there is a high overview
19:48:18 <nirik> well, there's: https://fedoraproject.org/wiki/Infrastructure/Architecture talking about our proxy setup, but ti might be pretty out of date
19:48:24 <nirik> yeah. :)
19:48:26 <zemmiph0bia> :p
19:48:29 <willo> Yeah, saw that one
19:48:38 <willo> Would any more diagrams like this be useful?
19:48:48 <nirik> there was someone interested in making a network diagram a while back, but they just wandered off.
19:48:57 <willo> Or is it changing to quickly to keep up to date
19:48:59 <nirik> if someone would like to make one, it could be useful yeah
19:49:01 <threebean> heh, there's a fedmsg diagram -> http://www.fedmsg.com/en/latest/topology/
19:49:05 <threebean> also somewhat out of date
19:49:12 <willo> :)
19:49:27 <danofsatx> Since Nagios is running, can't it spit out a diagram?
19:49:36 <willo> well network is defintely up my alley, I could start there
19:49:40 <nirik> danofsatx: it can yeah.
19:49:51 <nirik> https://admin.fedoraproject.org/nagios/
19:50:15 <johe_> on nagios again? wasnt it zabbix?
19:50:42 <nirik> we were never fully on zabbix. There was an attempted migration, but it was scrapped.
19:50:43 <willo> Looked at nagios before and I got password prompt
19:50:56 <adimania> won't it depend on the parents which we defined?
19:50:58 <willo> guess fi-apprentice doesn't give me the power...:_
19:51:14 <johe_> nirik, well i was on the noc team when they did the switch, was just a bit confused
19:51:35 <adimania> the map at https://admin.fedoraproject.org/nagios/ looks too cluttered :(
19:51:40 <nirik> willo: you should be able to use your fedora account login/pass there.
19:51:52 <willo> I think anything out of nagios is only as good as your service checks and dependancies
19:51:58 <nirik> adimania: yes, it's based on what nagios has... but I think it's actually reasonably accurate now.
19:52:12 <willo> Which can be hard to describe a lot of interactions about data flow
19:52:17 <nirik> johe_: yeah, that was before I was too involved...
19:53:28 <nirik> anyhow, does that answer the question?
19:54:03 <janeznemanic> it's complicated and big
19:54:19 <nirik> any other items for open floor?
19:54:23 <danofsatx> Since I'm here, I'd like to give a quick intro of myself to the infra team. I haven't sent the email to the list yet, though.
19:54:31 <willo> nirik: ah, ok cool.
19:54:36 <kamina1> Hi, I missed the introduction session. So, may I introduce myself?
19:54:36 <johe_> janeznemanic, true, but nagios cant display the relation, such maps are always huge
19:54:54 <nirik> danofsatx / kamina1: welcome. Please do.
19:54:59 <willo> Didn't try that after my mention in fedora-noc :)
19:55:24 <danofsatx> My name is dan, fas dmossor - I am a 20+ year veteran of the IT feild, and maintain three separate mixed CentOS/Fedora/Windows networks in my day job.
19:56:06 <kamina1> Thanks. I am Kamina. Currently, I live in Germany. I am fresh college grad, looking for improving my skills in coding and contribute to open source
19:56:17 <danofsatx> Technically, I am a Cisco certified network engineer, but I can work with anything
19:56:33 <nirik> excellent. Welcome to both of you.
19:56:38 <kamina1> Thanks
19:56:44 <nirik> are you more interested in sysadmin or application development ? or both?
19:56:50 <danofsatx> about the only thing I can't do in IT is coding - my job is to make sure the coders can do theirs.
19:57:04 <kamina1> I am interested in Application Dev
19:57:19 <danofsatx> and I in sysadmin/NOC work
19:57:24 <nirik> cool.
19:57:40 <willo> danofsatx: welcome from a fellow network engineer
19:57:52 <danofsatx> thanks willo ;)
19:58:01 <nirik> for sysadmin, see me after the meeting in #fedora-admin and we can get you added to the apprentice group, for applications, see #fedora-apps and we can get you pointed in the right direction. ;)
19:58:20 <nirik> ok, we are almost out of time... anything else before we close out the meeting?
19:58:33 <threebean> busy meeting today!
19:58:37 <threebean> good to see so many new people :)
19:58:39 <nirik> yeah, great stuff.
19:58:44 <nirik> always good seeing new folks...
19:58:49 <danofsatx> I'll tackle the diagram, in consultation with willo
19:59:14 <relrod> \o/
19:59:16 <nirik> great. Happy to assist.
19:59:22 <nirik> ok, thanks for coming everyone!
19:59:30 <nirik> #endmeeting
10 years, 2 months
Summary/Minutes from today's FPC Meeting (2014-01-16 17:00 - 19:00 UTC)
by James Antill
======================
#fedora-meeting-1: fpc
======================
Meeting started by abadger1999 at 17:03:12 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-16/fpc.2014-01-...
.
Meeting summary
---------------
* roll call (abadger1999, 17:03:23)
* #339 software collections in Fedora (abadger1999, 17:06:52)
* LINK: https://fedorahosted.org/fpc/ticket/339 (abadger1999,
17:07:01)
* LINK: https://fedorahosted.org/fpc/ticket/379 (abadger1999,
17:12:07)
* Proposal for language bindings to be named $language-$foo, *not*
$foo-$language (old packages grandfathered but cleanups are
welcomed) APPROVED (+1:7, 0:0, -1:0) (abadger1999, 18:08:46)
* #380 code::blocks bundling (abadger1999, 18:11:00)
* LINK: https://fedorahosted.org/fpc/ticket/381 (abadger1999,
18:14:06)
* #383 Bundled library exception request for libgsystem
(abadger1999, 18:21:28)
* LINK: https://fedorahosted.org/fpc/ticket/383 (abadger1999,
18:21:33)
* LINK: https://fedorahosted.org/fpc/ticket/382 (abadger1999,
18:29:29)
* FPC members, please add problems you see with the golang guidelines
to the ticket. We'll see if there's a way to address them
afterwards (abadger1999, 19:02:43)
Meeting ended at 19:09:29 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* abadger1999 (160)
* tibbs|w (49)
* limburgher (41)
* geppetto (28)
* RemiFedora (13)
* racor (10)
* zodbot (8)
* Rathann (8)
* SmootherFrOgZ (2)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
10 years, 2 months
Summary of yesterday's (1/15/2014) cloud WG meeting
by Sam Kottler
Thanks everyone who was able to make it to the meeting yesterday! For those who weren't able to make it, here are few important links:
Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-15/fedora-meeti...
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-15/fedora-meeti...
Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-15/fedora-meeti...
Log (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-15/fedora-meeti...
Here's a summary of the meeting (link to the HTML and text versions above):
17:01:57 <samkottler> #startmeeting cloud WG weekly meeting
17:01:57 <zodbot> Meeting started Wed Jan 15 17:01:57 2014 UTC. The chair is samkottler. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:57 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:02:08 <jzb> howdy
17:02:25 <samkottler> #chair rbergeron mattdm number80 geppetto jzb
17:02:25 <zodbot> Current chairs: geppetto jzb mattdm number80 rbergeron samkottler
17:02:45 <samkottler> welcome to 2014's first official meeting :-)
17:02:58 * samkottler wonders if special guest davidstrauss is gonna join us
17:03:30 <samkottler> #topic rollcall
17:03:45 <jzb> jzb is here
17:03:48 <samkottler> \o/
17:03:53 <number80> .fasinfo hguemar
17:03:55 <zodbot> number80: User: hguemar, Name: Haïkel Guémar, email: karlthered(a)gmail.com, Creation: 2006-07-18, IRC Nick: number80, Timezone: Europe/Paris, Locale: en, GPG key ID: 41CF9CEA, Status: active
17:03:58 <zodbot> number80: Approved Groups: +packager cla_fedora cla_done fedorabugs ambassadors cla_fpca gitbeefymiracle
17:03:59 <samkottler> .hellowmynameis skottler
17:04:04 <samkottler> .hellomynameis skottler
17:04:06 <zodbot> samkottler: skottler 'Sam Kottler' <skottler(a)redhat.com>
17:04:11 * samkottler struggles
17:04:22 <jzb> .hellomynameis jzb
17:04:22 <mattdm> .fasinfo mattdm
17:04:27 <zodbot> jzb: jzb 'Joe Brockmeier' <jzb(a)zonker.net>
17:04:30 <zodbot> mattdm: User: mattdm, Name: Matthew Miller, email: mattdm(a)mattdm.org, Creation: 2005-04-13, IRC Nick: mattdm, Timezone: US/Eastern, Locale: en, GPG key ID: 72CF3A1B, Status: active
17:04:33 <zodbot> mattdm: Approved Groups: @gitdockerfiles gitspin-kickstarts +gitspins @gitcloud-image-service fi-apprentice gitcloud-kickstarts cla_done fedorabugs packager ambassadors cla_fedora cla_fpca
17:04:41 <jzb> hey! finally found a way to get it to limit to matching my username...
17:05:05 <number80> i didn't knew that command too :)
17:05:29 <rbergeron> .hellomynameis slim_shady
17:05:31 <zodbot> rbergeron: Sorry, but you don't exist
17:05:32 <geppetto> .hellomynameis geppetto
17:05:35 <rbergeron> darnit
17:05:37 <zodbot> geppetto: Sorry, but you don't exist
17:05:42 <geppetto> cool :)
17:05:44 <mattdm> lol
17:05:49 <sgallagh> geppetto: Has to be your FAS ID
17:06:04 <samkottler> this meeting has entered the land of meta
17:06:08 <sgallagh> .hellomynameis sgallagh
17:06:10 <zodbot> sgallagh: sgallagh 'Stephen Gallagher' <sgallagh(a)redhat.com>
17:06:19 <geppetto> .hellomynameis james
17:06:21 <zodbot> geppetto: james 'James Antill' <james.antill(a)redhat.com>
17:07:14 <samkottler> #topic PRD update and pending issues
17:07:23 <samkottler> it's due on the 20th
17:07:38 <mattdm> it's looking a lot better than it was a week ago!
17:07:39 <samkottler> and there are still some things we need to talk with the server WG about, sgallagh is here so maybe we should do that now?
17:07:55 <samkottler> yep, it's definitely shaping up
17:08:02 <samkottler> I've been trying to spend an hour or so per day on it
17:08:14 <mattdm> awesome.
17:08:42 <mattdm> I'm for starting with talking iwth sgallagh re server/cloud
17:08:48 * number80 gives a kudos to samkottler
17:08:51 <samkottler> we need to figure out the features we're gonna support
17:09:12 <samkottler> the use cases are mostly done, which was a big hurdle
17:10:01 <rbergeron> features to support or features to enable to enable the .. use cases
17:10:02 <mattdm> Do we want to try to hash out some specific thigns while we have everyone here
17:10:11 <mattdm> or should we look at some of the bigger picture things?
17:10:26 <samkottler> rbergeron: yes
17:10:35 <rbergeron> i'm not opposed, though it might be useful to know if any of those things are influenced by the server-ish stuff sgallagh is here for?
17:10:36 <samkottler> both
17:10:49 <samkottler> yeah, let's talk to sgallagh first :-)
17:10:55 <mattdm> sgallagh go!
17:10:57 * sgallagh feels honored
17:11:34 <number80> go sgallagh // right syntax
17:11:39 <sgallagh> The Server WG had its hopefully-final PRD meeting yesterday. We invited jzb and number80 to represent Cloud interests
17:11:59 * sgallagh really wants to make a Zork joke right now
17:12:46 <jzb> sgallagh: what's stopping you?
17:13:19 <sgallagh> I'm stuck in a maze of twisty cubicles, all alike...
17:13:51 <sgallagh> Ok, so there was a lot of discussion yesterday about where the dividing line is for things like OpenStack and OpenShift
17:15:15 <mattdm> I think that right now at least, cloud is focused on guest images and excludes openstack execution nodes
17:15:25 <sgallagh> that was our sense as well
17:15:39 <mattdm> that might change in the future, but leaves "runs in virt" as a common thread
17:15:58 <sgallagh> we proposed that OpenStack nodes should be a Server Role, possibly contributed by this group
17:16:17 <sgallagh> but "owned" by server
17:16:39 <samkottler> I think that's always been the assumption
17:16:48 <samkottler> the hypervisor'ish stuff would be owned by server
17:17:03 <mattdm> any dissent? speak now. :)
17:17:32 <sgallagh> That's been my assumption, but there was a lot of discussion about it yesterday
17:18:09 <sgallagh> It's also ambiguous where "managing an OpenShift deployment" belongs.
17:18:10 <jzb> sgallagh: more or less, though I sort of envisoned OpenStack nodes as closer to the server side than cloud side.
17:18:39 <sgallagh> jzb: I agree, but it's fair to say that the implementation will need to involve Cloud heavily
17:18:53 <jzb> sgallagh: indeed
17:19:15 <mattdm> I thik there's room to have some overlap. You can do e.g., a web server or web application in _either_ a cloud paradigm (<-bingo!) or the traditional server way.
17:19:22 <sgallagh> Why don't we turn the conversation around a bit. I had jzb and number80 in our meeting to answer our questions. Why don't you raise your own for us.
17:19:32 <jzb> yay!
17:19:38 * jzb tries to think of a stumper
17:20:05 <sgallagh> Where do you guys see ambiguity in our missions?
17:20:08 <rbergeron> ask something about configuration management or orchestration tools :)
17:20:19 <jzb> that is a good Q
17:20:28 <sgallagh> rbergeron: Config management is clearly in our laps
17:20:51 <sgallagh> "Orchestration tools" is a harder question
17:21:09 <rbergeron> I think the biggest source of ambiguity is that people equate "openstack" (and all the others) with cloud and i can see how that might be cause for misdirected questions.
17:21:09 <mattdm> sgallagh I think some of the ambiguity is that we're both doing "here's a base thing which can be adapted for different roles".
17:21:12 <samkottler> stuff like mesos blurs the lines
17:21:16 <sgallagh> We've got a use case for orchestration of containers, but that's not a complete answer
17:21:17 <mattdm> rbergeron that too
17:21:38 <mattdm> for server, it's the base platform plus application stacks
17:21:46 <mattdm> for cloud it's... well, possibly the same thing.
17:21:47 <sgallagh> "Server Roles"
17:22:26 <rbergeron> Logging? Things like checkpoint/restore? Storage (gluster or other cloud-ish storage)? Are we going to try and ... match up where we can on things? Or... "you can go your own wayyyyyyyyyyyy"
17:23:13 <sgallagh> logging is a much more complex question than a single word.
17:23:25 <samkottler> I think we can safely draw the line at 'do you need this thing on a physical machine'
17:23:32 <samkottler> logging is a yes and storage is a yes
17:23:35 <sgallagh> Checkpoint/restore is probably not all that useful to Cloud images, since you're aiming for mostly-disposable anyway, yes?
17:23:37 <samkottler> at least in my view
17:23:47 <mattdm> sgallagh right
17:23:50 <samkottler> yeah
17:24:01 <jzb> samkottler: if the users are doing it right
17:24:01 <mattdm> I think we want to keep the line more at cattle/pets than hw/virt
17:24:01 <rbergeron> sgallagh: processes running and such? i don't know
17:24:09 <samkottler> although people run stuff like...database servers in the cloud, too
17:24:10 <rbergeron> moving vm's and such
17:24:10 <jzb> sorry that was for sgallagh
17:24:26 <jzb> sgallagh: from working on CloudStack, I found a lot of questions around snapshotting/restore.
17:24:50 <samkottler> people do care about their instances being easy to restore
17:24:54 <number80> (sorry, got disturbed by coworkers)
17:24:59 <jzb> sgallagh: it's also used a lot to create a golden image. Spin one up, modify, then snapshot -> template
17:25:04 <samkottler> even just from a convenience perspective
17:25:13 <samkottler> jzb: :/ but yeah, common
17:25:34 <mattdm> but we expect the cloud env to hande that, right?
17:25:40 <jzb> in other words, ideally, no - we generally not care. In the real world, we do.
17:25:44 <jzb> mattdm: yes.
17:25:48 <samkottler> it's a hypervisor thing anyhow
17:26:09 <number80> yup
17:26:10 <jzb> samkottler: it's a hz thing except that the IaaS exposes the hz features.
17:26:17 <sgallagh> I'm not sure the PRDs need to be exhaustive either
17:26:26 <rbergeron> jzb: ah, that's a dandy point there
17:26:33 <sgallagh> It's probably worth noting that individual implementation goals can be solved through collaboration
17:27:04 <samkottler> jzb: like in the case where a guest requests a snapshot of itself?
17:27:14 <sgallagh> I'm not sure it's sensible or feasible to enumerate every possible aspect of the implementation.
17:27:30 * rbergeron needs to snapshot/restore her soda. where did it disappear to? ugh
17:27:39 <jzb> samkottler: I was thinking when a user uses the API or UI to create one.
17:27:53 <rbergeron> sgallagh: just trying to make sure we're not missing anything significant in overlap so just suggesting All The Things
17:27:54 <sgallagh> I view "ownership" of these areas as more of shepherding than dictating.
17:27:57 <samkottler> let's move on with the general understanding of were the line stands
17:27:59 <jzb> samkottler: again, I ran into a lot of users who basically used the IaaS as Advanced Virtualization
17:27:59 <mattdm> sgallagh +1
17:28:03 <number80> sgallagh: +1
17:28:06 <jzb> sgallagh: +1
17:28:45 <mattdm> If we can do it without confusion, I would like to steer users who are interested in IaaS-as-server-in-the-sky towards using Fedora Server rather than the cloud image
17:28:52 <sgallagh> I'm sure as hell not going to make a decision on a major change to hypervisor tech without consulting this team, for example.
17:28:52 <mattdm> but that might be hard to message.
17:28:57 <samkottler> do we want to do a vote on the line or just move forward with everyone in agreement?
17:29:21 <jzb> mattdm: I always looked at it as, they can start using the tool the wrong way and learn to do it right
17:29:21 <sgallagh> Just as one more aside:
17:29:36 <sgallagh> One thing that came up yesterday that I'd like to have buy-in from both sides is this:
17:29:38 <jzb> mattdm: so if they adopt OpenStack/CloudStack/Euca, it makes it easier to learn the right habits eventually.
17:30:09 <sgallagh> We need to share a "Universe" package repository, so that if someone installs the base cloud image, they will be able to "yum install fedora-server-release" and have any and all capabilities that Server offers (such as Roles)
17:30:46 <sgallagh> The subtext being: we are not producing disparate Fedora repositories (excepting the install media)
17:31:02 <mattdm> Okay, that's an interesting one. Maybe we should make that explicit in the PRD?
17:31:03 <number80> separate repositories would only make things worse (think RPM hell dependencies)
17:31:18 <mattdm> I mean, yes, I think there needs to be a universal repo
17:31:33 <mattdm> the question is: is going from cloud base -> server an expected normal path?
17:31:35 <geppetto> sgallagh: So is the intention that people can/will be able to install multiple *-release packages?
17:31:35 <jzb> sgallagh: as yesterday, agreed
17:31:52 <jzb> sgallagh: I think there may have been some accidental FUD that the idea of separate repos even surfaced.
17:31:53 <mattdm> what about the other way around? (I think it might be okay to define this as a one-way path)
17:31:55 <sgallagh> geppetto: I don't want to make a general statement on that.
17:32:14 <sgallagh> I'm fine with "Cloud can become Server" and not the reverse (or Server->Workstation, etc.)
17:32:14 <mattdm> you can adopt one of your cattle as a pet. but you can't really send your kitty out to live in the herd.
17:32:40 <sgallagh> mattdm: My parents told me they sent my dog to the farm. Are you telling me they lied?
17:33:24 <sgallagh> jzb: Right, but the separate repos is related, but not the whole statement I was just making.
17:33:36 <geppetto> sgallagh: Why not server => cloud?
17:33:56 <jzb> mattdm: my cats agree
17:34:11 <samkottler> server to cloud makes perfect sense IMO
17:34:12 <sgallagh> geppetto: I'm not ruling it out. But I don't know if I see obvious value there, unless I misunderstand your target
17:34:18 <rbergeron> i may be confused here - i sort thought people were like
17:34:20 <rbergeron> moving from the server
17:34:21 <rbergeron> to the cloud
17:34:34 <samkottler> rbergeron: well the intermediate is just taking a server and putting it on kvm/xen
17:34:43 <rbergeron> samkottler: right, babysteps
17:34:58 * samkottler thinks a server to cloud path is necessary
17:35:03 <sgallagh> My initial statement was merely this: You want to virtualize/containerize/stick in public IaaS some of your critical infra.
17:35:09 <samkottler> which basically involves virtio drivers, cloud-init, whatever else
17:35:25 <number80> sgallagh: you mean having a p2v like tool ?
17:35:29 <sgallagh> You can spin up the Amazon Fedora Cloud instance and then easily make that become a Server instance with the frameworks we provide
17:35:48 <sgallagh> number80: Really not talking that level of detail at the moment.
17:36:10 <number80> ok
17:36:14 <mattdm> this is traditional server -> server-in-the-sky. that's fine, but server-in-the-sky isn't necessarily Fedora Cloud
17:36:17 <mattdm> is my thinking.
17:36:18 <sgallagh> Merely that a machine (virtual or not) installed from the Cloud Image can *become* a "full" Server install simply through yum/dnf/packagekit
17:36:45 <mattdm> in order to really migrate to take advantage of cloud computing, you rearchitect.
17:37:01 <number80> my POV is that fedora-cloud is basically a trimmed-down image on which you can install whatever "role" you wish too
17:37:12 <sgallagh> mattdm: Well, no matter what, you'll still probably want a fairly traditional Domain Controller and DNS environment
17:37:18 <sgallagh> But that's a different discussion
17:37:47 <jzb> number80: agreed, but there may also be roles that make sense only in the cloud.
17:37:49 <mattdm> number80 and Fedora Cloud provides some cloud-computing-focused roles, and a way to go to fedora server for roles that aren't necessarily covered but still always useful
17:37:59 <number80> jzb: +1
17:38:29 <samkottler> so assuming here's a universe what makes so directly separating the roles necessary?
17:38:53 <samkottler> I guess my disconnect is why I wouldn't say...install freeipa on a cloud instance just like I would on a regular box in a DC
17:39:25 <sgallagh> samkottler: You can. But we're (Server) going to be doing some additional packaging work to make role deployment simpler
17:39:25 <mattdm> okay, so: do we want to tie this more closely together and share the roles?
17:39:38 <sgallagh> But it's going to require additional infrastructure that you may or may not want.
17:39:52 <samkottler> sgallagh: ah okay that makes more sense now
17:40:15 <samkottler> so it'd basically expose comps to you or something?
17:40:22 <samkottler> whatever, I get the point, no need to dive so deep
17:40:26 <rbergeron> what are the pieces of a "role" exactly?
17:40:32 <rbergeron> wait, i'm slower than samkottler
17:40:33 <sgallagh> samkottler: Things like interaction with the Cockpit Project so that you could deploy the role with minimal interaction (just answer three questions and go)
17:40:36 <rbergeron> (obviously)
17:40:59 <rbergeron> is a role == set of packages known to work in a specific way?
17:41:05 <rbergeron> together to do something?
17:41:11 <sgallagh> rbergeron: Essentially yes.
17:41:22 <sgallagh> Though our definition of "set of packages" is currently intentionally vague
17:41:42 <sgallagh> Because people get hung up on packaging==rpm
17:41:56 <rbergeron> how does it overlap with something like ... heat templates
17:42:07 <sgallagh> FYI: https://fedoraproject.org/w/index.php?title=Server/Product_Requirements_D...
17:42:12 <jzb> sgallagh: role == software required for a specific task?
17:42:22 <sgallagh> jzb: That's a better description, yes
17:42:36 <rbergeron> or .. docker containers for various pieces of things
17:42:43 <samkottler> rbergeron: it wouldn't orchestrate across-server stuff
17:42:50 <samkottler> just on a single node
17:42:57 <sgallagh> rbergeron: docker containers is one possible packaging implementation (and is being considered)
17:43:58 <rbergeron> samkottler: yeah, but i am just wondering about how to make the "known templating things" out there - which are basically all defining roles of some sort, just implementing them in ways where they can (or can't) be auto-magically scaled
17:44:46 <rbergeron> the perennial wordpress example - do we want a wordpress role (if that's what we're sort of thinking) to look the same as a heat template for wordpress, etc
17:44:49 <samkottler> rbergeron: wouldn't that be closer to config management's realm?
17:44:51 <rbergeron> or not really concerned with that at that point
17:45:10 <rbergeron> samkottler: "best tool for the job" - people are gonna do it however they want :)
17:45:32 <samkottler> I guess separating cfg mgmt from one-time ops isn't really something that you do in say...docker land
17:45:40 <sgallagh> rbergeron: Wordpress is probably not the sort of Role we'd (Server) be most interested in.
17:46:09 <sgallagh> From the Use Cases section of our PRD: Examples may include: FreeIPA Domain Controller, BIND DNS, DHCP, Database server, iSCSI target, File/Storage server, OpenStack Hypervisor Node.
17:46:14 <rbergeron> sgallagh: i know, it's just a sample example .
17:46:36 <sgallagh> I'm pretty much entirely disinterested in treating specific applications as Server Roles
17:46:51 <sgallagh> (others on the WG may have a different opinion on that matter)
17:46:54 <rbergeron> i'm not going to be cruel and bring up triple-o :)
17:47:18 * sgallagh looks forward to quintuple-o. It's the next logical step, right?
17:47:20 <samkottler> rbergeron: SCORN
17:47:30 <rbergeron> okay, i think i get the picture
17:47:32 <rbergeron> sorry to be all questiony
17:47:44 <sgallagh> Questions now are more useful than questions in six months.
17:47:45 * mattdm thinks questiony is very helpful
17:48:37 <mattdm> here's an idea: what if we make server-in-the-sky one of the fedora cloud spins?
17:48:59 <mattdm> right now, we (tentatively) have a generic base, docker, and big data
17:49:00 * rbergeron was going to bring up load balancing but i think we can skip-it
17:49:08 <rbergeron> hmm
17:49:23 <samkottler> but what do you run on the server in the sky?
17:49:28 <mattdm> we could also have one that's basically got the server role-enablement stuff in place.
17:49:30 <samkottler> is it a db server or a IPA server or what
17:49:37 <sgallagh> mattdm: We were probably going to request help implementing this. It's one of our preferred delivery mechanisms.
17:49:52 <sgallagh> samkottler: "Yes"
17:50:12 <number80> how server and server-in-the-sky roles will be different ?
17:50:13 <mattdm> samkottler it's still also a base, but a base tailored for running the Fedora Server roles.
17:50:13 <samkottler> I guess the other issue is that one of the things we might have is a custom kernel build so it might just be bloated
17:50:56 * samkottler will have to think more about what it'd actually look like
17:51:11 <number80> samkottler: didn't the kernel team said that maintaining multiples kernels would be a PITA for them ?
17:51:32 <samkottler> in the meantime we can force people to to ephemeralize data by having jwb remove fsync from our kernel build
17:52:04 <jwb> done
17:52:19 <sgallagh> number80: Yes, they did. I think they were okay with breaking up the module subpackages, but not actual custom kernels. jwb?
17:52:36 <jwb> yeah. i'm already working on splitting up the packaging
17:52:42 <jwb> i have kernel-core and kernel-drivers
17:52:57 <jwb> kernel-core is what you guys keep saying should be the small thing, without actually telling me what you need in it.
17:53:13 <jwb> so right now, it literally just has the contents the kernel RPM puts in /boot.
17:53:21 <jwb> which... won't really work for anyone
17:53:28 <jwb> so. discuss. then inform.
17:53:53 <samkottler> we should probably include a general list of kernel requirements in the PRD
17:54:00 <jwb> \o/
17:54:26 <samkottler> I think most of the requirements will be 'rip out this giant pile of drivers'
17:54:32 <jwb> (small caveat: it's not actually working perfectly yet, but i am workign on it at least)
17:54:37 <samkottler> so core won't be affected
17:54:43 * number80 gotta go or he'll be ear-raped by the office alarm
17:54:46 <rbergeron> should those kernel requirements inc. networking/ovs-type stuff?
17:54:49 <mattdm> jwb I can help make that more specific. Is there a bug or other place to help track what should actually be in there?
17:54:56 * rbergeron doesn't know that she's seeen networky-stuff anywhere really
17:55:16 <samkottler> rbergeron: I think ovs is in the server realm?
17:56:00 <jwb> mattdm, no bug. we could create one, or just use the kernel list. i have a new copr project i'm going to use to get people to test builds.
17:56:12 <jwb> rbergeron, ovs?
17:56:18 <jwb> oh, open-vswitch?
17:56:18 <samkottler> jwb: openvswitch
17:56:38 <jwb> yeah, we build that. i figured that and the virtio stuff would be good things to have in -core, but beyond that...
17:57:08 <jwb> and if this grows beyond "core", we can call it "base" instead
17:57:25 <mattdm> jwb hah
17:57:32 <rbergeron> samkottler: i do'nt know what's actually needed to be enabled where, but ... i'm pretty sure you would use it to manage gusests / connect them to each other in various ways?
17:58:04 <jwb> mattdm, i wasn't intending a dig. but it would be hard to say e.g. ovs is really "core" functionality
17:59:07 <jwb> and if you get to "do we want a firewall?" then you just grabbed a ton of netfilter drivers, etc
17:59:19 <jwb> which is why i would like you to tell me what you want :)
17:59:35 <jwb> because if it winds up being most of what we already have... then the exercise is rather pointless
17:59:39 <rbergeron> samkottler: http://www.itworld.com/virtualization/335244/rhev-upgrade-saga-rhel-kvm-a...
17:59:40 <samkottler> mattdm: I can work with you on kernel requirements
18:00:00 <mattdm> sounds good.
18:00:37 <rbergeron> anyway: i don't know my head from my ass on this but if it hasn't been thought about at all it might be worth thinking about . or consulting with someone
18:00:57 <rbergeron> who is more in-depth in ovs/neutron/open daylight land
18:01:04 <rbergeron> (mestery, cdub, etc)
18:01:53 * rbergeron shuts up
18:02:05 <mattdm> e.g. also not me. :)
18:02:17 <jwb> you cloud people have names that are amazing at not describing wtf they do
18:02:20 <mattdm> oh look. fesco time! i will keep this window open
18:02:24 * samkottler doesn't know enough about SDN to actually make decisions
18:02:27 <mattdm> jwb openstack is the WORST
18:02:36 <mattdm> it's got some sort of horrible name virus
18:02:52 <rbergeron> lol
18:03:01 <samkottler> jwb: openvswitch is the most descriptive
18:03:04 <samkottler> and it's still crap
18:03:09 <jwb> samkottler, was just going to say that
18:03:21 <jwb> need magic cloud decoder ring
18:03:40 <jwb> anyway, i'm awaiting further direction/discussion
18:03:49 <jwb> and i'd be happy to start spitting out copr builds
18:03:51 <samkottler> jwb: it's simple really...hook your heat up to your nova to route with your neutron to connect to cinder
18:04:02 <samkottler> welp, computers are bad
18:04:11 <jwb> at least they all have something to do with temperature!
18:04:30 * rbergeron notes that heat makes clouds rise (deploy, whatever), but i may have been involved with that naming
18:04:49 <rbergeron> ANYWAY
18:05:02 <samkottler> rbergeron: heat makes it rain
18:05:04 * rbergeron notes the time and things in the interest of decision making or otherwise
18:05:19 <samkottler> okay yeah let's keep it moving
18:05:36 <samkottler> any more PRD stuff that's pressing?
18:05:47 <samkottler> #action mattdm and samkottler to work on getting kernel requirements together for the PRD
18:07:17 <samkottler> bueller?
18:08:03 <samkottler> #topic open floor
18:08:24 <jzb> Nothing here.
18:08:28 <samkottler> so with the centos news and such, there is going to be a cloud SIG for centos
18:08:37 <samkottler> do we want to have some representation with them?
18:08:45 <jzb> samkottler: yes, I think we do.
18:08:57 <samkottler> jzb: twas kind of a loaded question
18:09:15 <samkottler> I've seen the idea of a shared cloud SIG between fedora and centos
18:09:18 <samkottler> what do people think of that?
18:10:01 <jzb> samkottler: would the scope be similar?
18:10:05 <rbergeron> that sounds epic.
18:10:07 <rbergeron> oh, sorry
18:10:09 <rbergeron> LOL
18:10:25 <samkottler> rbergeron++
18:10:31 <samkottler> jzb: yeah I believe so
18:10:32 <jzb> rbergeron: I see what you did there.
18:10:39 <samkottler> centos might have some good guidance for us
18:10:45 <samkottler> they already build lots of divergent kernels and stuff
18:10:55 <jzb> true true
18:11:23 <jzb> samkottler: what do we need to do to make that happen?
18:11:37 <jwb> samkottler, actually, not lots
18:11:43 <jwb> i've been poking at them
18:11:46 <samkottler> jzb: I guess the big thing is just for people to be looking for convos on centos-devel
18:11:51 <samkottler> and make sure you're subscribed
18:12:15 <jzb> OK
18:12:28 <jwb> at least in my initial conversations, most of their kernels are still based on RHEL with the xen one being the only one i've found that actually diverged at a base kernel level (3.10 iirc)
18:12:36 <jwb> and their reasons were decent
18:12:41 * jwb shuts up
18:13:09 <samkottler> jwb: they have someone from citrix who manages the 3.10 builds?
18:13:17 <samkottler> the core team doesn't do it
18:13:34 <jwb> samkottler, yep
18:13:57 <samkottler> gotcha
18:14:02 <samkottler> well that's all I've got for the open floor
18:14:14 <samkottler> more PRD work to be done, but we're getting closer
18:14:27 <samkottler> jzb: rbergeron: mattdm: number80: geppetto: anything else?
18:14:38 <geppetto> nope
18:14:57 <jzb> samkottler: nope
18:15:09 <samkottler> #endmeeting
==========================================
#fedora-meeting-1: cloud WG weekly meeting
==========================================
Meeting started by samkottler at 17:01:57 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-15/fedora-meeti...
.
Meeting summary
---------------
* rollcall (samkottler, 17:03:30)
* PRD update and pending issues (samkottler, 17:07:14)
* ACTION: mattdm and samkottler to work on getting kernel requirements
together for the PRD (samkottler, 18:05:47)
* open floor (samkottler, 18:08:03)
Meeting ended at 18:15:09 UTC.
Action Items
------------
* mattdm and samkottler to work on getting kernel requirements together
for the PRD
Action Items, by person
-----------------------
* mattdm
* mattdm and samkottler to work on getting kernel requirements
together for the PRD
* samkottler
* mattdm and samkottler to work on getting kernel requirements
together for the PRD
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* samkottler (89)
* sgallagh (59)
* rbergeron (48)
* mattdm (44)
* jzb (35)
* jwb (30)
* number80 (15)
* zodbot (13)
* geppetto (6)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
10 years, 2 months
Meeting minutes Env-and-Stacks WG meeting (2014-01-14)
by Marcela Mašláňová
===============================================
#fedora-meeting: env and stacks wg (2014-01-14)
===============================================
Meeting started by mmaslano at 16:04:30 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2014-01-14/env_and_stacks...
.
Meeting summary
---------------
* init process (mmaslano, 16:08:53)
* AGREED: add tjanez vission and mission statement (+7,-0,0)
(mmaslano, 16:21:13)
* ACTION: tjanez will add section about vision and mission statement
(mmaslano, 16:22:00)
* schedule will contain dates, not the actual PRD (mmaslano,
16:37:52)
* ACTION: abadger1999 to send out RFC about the SCL direction
(abadger1999, 17:36:26)
Meeting ended at 17:47:34 UTC.
Action Items
------------
* tjanez will add section about vision and mission statement
* abadger1999 to send out RFC about the SCL direction
Action Items, by person
-----------------------
* abadger1999
* abadger1999 to send out RFC about the SCL direction
* tjanez
* tjanez will add section about vision and mission statement
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* abadger1999 (48)
* tjanez (48)
* mmaslano (33)
* hhorak (23)
* pkovar (15)
* drieden (15)
* jwb (8)
* zodbot (6)
* samkottler (3)
* pkovar1 (1)
* pingou (1)
* bkabrda (0)
* juhp (0)
* handsome_pirate (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
10 years, 2 months
FAmNA Jan 14th 2014
by Jon
======================
#fedora-meeting: FAmNA
======================
Meeting started by masta at 02:02:00 UTC. The full logs are available
athttp://meetbot.fedoraproject.org/fedora-meeting/2014-01-15/famna.2014-0...
.
Meeting summary
---------------
* === FAmNA Roll Call === (masta, 02:02:00)
* === Announcements === (masta, 02:05:37)
* === Tickets === (masta, 02:09:39)
* LINK: https://fedorahosted.org/famna/report/9 (masta, 02:09:40)
* Ticket #68 - FAmNA Meeting Organization (masta, 02:10:31)
* === New swag ideas === (masta, 02:13:35)
* LINK: https://fedoraproject.org/wiki/Swag_vendors (inode0,
02:39:06)
* ACTION: masta to engage on the t-shirts (masta, 02:48:17)
* === open floor === (masta, 02:52:48)
Meeting ended at 03:04:08 UTC.
Action Items
------------
* masta to engage on the t-shirts
Action Items, by person
-----------------------
* masta
* masta to engage on the t-shirts
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* masta (73)
* inode0 (57)
* award3535 (34)
* kk4ewt (9)
* zodbot (8)
* wrnash1 (6)
* nb (5)
--Jon Disnard
irc: masta
fas: parasense
10 years, 2 months
Server WG Meeting Minutes (2014-01-14)
by Stephen Gallagher
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===================================================================
#fedora-meeting-1: Server Working Group Weekly Meeting (2014-01-14)
===================================================================
Meeting started by sgallagh at 15:59:51 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-14/fedora-meeti...
.
Meeting summary
- ---------------
* roll call (sgallagh, 16:00:00)
* PRD Draft (sgallagh, 16:06:04)
* LINK:
https://fedoraproject.org/w/index.php?title=Server/Product_Requirements_D...
(sgallagh, 16:07:13)
* Positioning relative to Fedora Cloud (sgallagh, 16:08:33)
* AGREED: remove use-case 7, move OpenStack Hypervisor Node reference
to proposed Roles list (sgallagh, 16:55:00)
* AGREED: Use case 8 remains as written (sgallagh, 17:08:38)
* Use Case 6: Env/Stacks and deployment of frameworks (sgallagh,
17:09:14)
* AGREED: drop "easy deployment of a framework" from our charter
(sgallagh, 17:20:05)
* FIXME for headless operation (sgallagh, 17:20:30)
* AGREED: New use-case: "10. The user must be able to install and
manage Fedora Server in a headless mode where the display framework
is inactive." (sgallagh, 17:31:29)
* Open Floor (sgallagh, 17:31:51)
Meeting ended at 17:42:38 UTC.
Action Items
- ------------
Action Items, by person
- -----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
- ---------------------------
* sgallagh (146)
* simo (95)
* davidstrauss (54)
* mitr (52)
* jzb (37)
* mizmo (37)
* nirik (35)
* adamw (12)
* tuanta (10)
* zodbot (9)
* number80 (4)
* Evolution (3)
* danofsatx (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlLVd3IACgkQeiVVYja6o6OI3gCeJ7+P7P6HhMfqflZpgYudwZNW
iwYAnRmdMkq3BDv6uXXt8Et3V2aU06Zl
=7f+Y
-----END PGP SIGNATURE-----
10 years, 2 months