Re: [cloud] #48: remove rsyslog from default image, configure journald options appropriately
#48: remove rsyslog from default image, configure journald options appropriately --+ Reporter: mattdm| Owner: Type: task | Status: new Priority: normal| Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Resolution: Keywords:| --+ Comment (by johannbg): I should also mention that it's not enough to simply remove rsyslog from the cloud image, each package that ships service/daemon needs to split out their rsyslog and syslog-ng configuration file as well as their accommodating logwatch files ( which are roughly 100 components ) into their own sub package to properly prepare and integrate components and journal into the distribution. I filed a request two years ago with FPC in attempt to get the guidelines fixed so I could fix this when I do the systemd cleanup process well that ticket is still open and unresolved, perhaps the cloud community has more luck with the FPC if you are going to start doing the necessary legwork to do this work. -- Ticket URL: https://fedorahosted.org/cloud/ticket/48#comment:2 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Thursday Meeting?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/21/2014 06:03 PM, Sandro red Mathys wrote: Heads-up: I just went ahead and closed two tickets (#24 and #29) that I think were done, just so we don't have to spend meeting time cycles on them. Awesome, thanks! jzb - -- Joe Brockmeier | Principal Cloud Storage Analyst j...@redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTVmNpAAoJEKbW5zOgIHzUFg0IAJMNDlkKkG59osj2RF6buDBs zgOmYws+C+wfrj94jJhAEpokCU5FUV5tUs1Z2Ib6P+9k8AsYiuLRqxNSPGm8Mue4 wHpjCsDnACZMd6qSVyLoepuQHsvAeZ5vbVLcf3SltNsbeMT9i4HY6ZVZsWsXEyjx 2yuUCm6Gh7lHLUap7fQ0uFL4WwkZjzJpqIIHPaiCub9+TqR84Uh976JN+YHHERum RcRuZtRybCq0EVC0tbolU8BJV4pM4CGZbsCXodUoeNReIshbD1a4PxoPSDWomY5Y A79H/ih2C94qPMZ9KRj2NZf5yOjXS0B6XKG4dsW+jqyys1UC+yLX+Xj8XcEWHO4= =WX9p -END PGP SIGNATURE- ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [cloud] #14: Investigate systemd-networkd
#14: Investigate systemd-networkd --+ Reporter: mattdm| Owner: janeznemanic Type: task | Status: new Priority: normal| Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Resolution: Keywords:| --+ Comment (by janeznemanic): Systemd-networkd enabled, initscripts and dhclient removed. Why do we use rsyslog and not systemd's journald? Let me try and build image with koji. -- Ticket URL: https://fedorahosted.org/cloud/ticket/14#comment:27 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [cloud] #49: Spins Process for Cloud Images
#49: Spins Process for Cloud Images -+- Reporter: red | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Branch) Component: --- | Resolution: Keywords: meeting | -+- Changes (by mattdm): * cc: cwickert (added) Comment: I guess we can go forward with it and raise a ruckus if we hit problems. Mostly, it looks like we shouldn't have any. I don't think the guidelines all apply exactly, though -- we don't want these on the 'spins' download page, as that will just confuse people. I guess we should ask Christoph, as spins wrangler, what he thinks. -- Ticket URL: https://fedorahosted.org/cloud/ticket/49#comment:1 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [cloud] #14: Investigate systemd-networkd
#14: Investigate systemd-networkd --+ Reporter: mattdm| Owner: janeznemanic Type: task | Status: new Priority: normal| Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Resolution: Keywords:| --+ Comment (by gospo): Replying to [comment:8 mattdm]: If there were a generator for systemd-networkd which could read the basic values from the legacy files and create network units on the fly (akin to systemd-fstab-generator), that would level that advantage. (No need to implement the full syntax; just basic static and dhcp, plus log when something isn't understood and perhaps recommend NetworkManager for this cases.) And ifup/ifdown compatibility scripts would be nice (although I don't think we generally care for the cloud case) Sorry, but I miss why we would want to use the legacy files used by initscipts for networkd? If we are concerned about the ability to migrate from networkd to NM we should probably consider a plug-in for NM to read networkd files. -- Ticket URL: https://fedorahosted.org/cloud/ticket/14#comment:30 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [cloud] #14: Investigate systemd-networkd
#14: Investigate systemd-networkd --+ Reporter: mattdm| Owner: janeznemanic Type: task | Status: new Priority: normal| Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Resolution: Keywords:| --+ Comment (by mattdm): Replying to [comment:30 gospo]: Sorry, but I miss why we would want to use the legacy files used by initscipts for networkd? If we are concerned about the ability to migrate from networkd to NM we should probably consider a plug-in for NM to read networkd files. Many people are used to these files being *the* Fedora (and Red Hat distribution family) way to configure network interfaces. Their Puppet modules and Chef recipies work this way. In fact, the upstream code includes modules that understand this format natively. Tools like ec2-net- utils do too. All of our existing documentation talks about these files. And, it's already a common language between initscripts and Network Manager. I don't think we would be doing anyone any favors by making Fedora a special case. In the future, if systemd-networkd becomes common and native tool support is widespread, it'll be easy to transition people. In the future -- Ticket URL: https://fedorahosted.org/cloud/ticket/14#comment:31 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [cloud] #14: Investigate systemd-networkd
#14: Investigate systemd-networkd --+ Reporter: mattdm| Owner: janeznemanic Type: task | Status: new Priority: normal| Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Resolution: Keywords:| --+ Comment (by gospo): Replying to [comment:31 mattdm]: Replying to [comment:30 gospo]: Sorry, but I miss why we would want to use the legacy files used by initscipts for networkd? If we are concerned about the ability to migrate from networkd to NM we should probably consider a plug-in for NM to read networkd files. Many people are used to these files being *the* Fedora (and Red Hat distribution family) way to configure network interfaces. Their Puppet modules and Chef recipies work this way. In fact, the upstream code includes modules that understand this format natively. Tools like ec2-net- utils do too. All of our existing documentation talks about these files. And, it's already a common language between initscripts and Network Manager. I don't think we would be doing anyone any favors by making Fedora a special case. In the future, if systemd-networkd becomes common and native tool support is widespread, it'll be easy to transition people. Ah yes, I agree, then. Thanks for the explanation. -- Ticket URL: https://fedorahosted.org/cloud/ticket/14#comment:32 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [cloud] #41: Write Initial QA Documents
#41: Write Initial QA Documents --+- Reporter: mattdm| Owner: roshi Type: task | Status: assigned Priority: major | Milestone: Fedora 21 (Branch) Component: Testing QA | Resolution: Keywords:| --+- Changes (by roshi): * status: accepted = assigned * owner: red = roshi -- Ticket URL: https://fedorahosted.org/cloud/ticket/41#comment:4 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [cloud] #49: Spins Process for Cloud Images
#49: Spins Process for Cloud Images -+- Reporter: red | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Branch) Component: --- | Resolution: Keywords: meeting | -+- Comment (by mattdm): You know, this has one huge advantage. I keep accidentally referring to our cloud image variants as spins. Making them _actually_ spins would remove the need to come up with a new term. :) -- Ticket URL: https://fedorahosted.org/cloud/ticket/49#comment:2 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
