Re: [cloud] #19: File F21 change: Docker Host Image
#19: File F21 change: Docker Host Image ---+--- Reporter: mattdm | Owner: red Type: task | Status: accepted Priority: blocker| Milestone: Fedora 21 (Feature Deadline) Component: Docker Host Image | Resolution: Keywords: | ---+--- Comment (by red): I've now written a terrible first version of the change proposal and everyone is welcome to let me know what I can improve (or, do it yourself if it's minor-ish): https://fedoraproject.org/wiki/Changes/Docker_Cloud_Image I tried to write it so that we can either: * Just take take the base image, add docker-io (and possibly etcd and fleet) and call it something shiny new * OR, implement any of the leading edge stuff, too - depending on how the discussion / necessary work goes and what we decide. -- Ticket URL: https://fedorahosted.org/cloud/ticket/19#comment:14 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] #4: new release criteria for post-f20 cloud image
#4: new release criteria for post-f20 cloud image --+ Reporter: mattdm| Owner: red Type: task | Status: accepted Priority: major | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Resolution: Keywords:| --+ Changes (by red): * milestone: Fedora 21 (Final) = Fedora 21 (Alpha) * owner: = red * status: new = accepted Comment: IMHO, this really goes hand-in-hand with ticket #41 (proven by comment 3) so taking this, too. Also, since Fedora has separate Alpha, Beta AND Final release criteria, I'm going to change the milestone accordingly. There might or might not be any Alpha/Beta criteria but it's easier to postpone to a later milestone than the other way around. -- Ticket URL: https://fedorahosted.org/cloud/ticket/4#comment:5 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] #38: Automatic Smoketests on Image Build
#38: Automatic Smoketests on Image Build --+ Reporter: mattdm| Owner: red Type: task | Status: accepted Priority: normal| Milestone: Fedora 21 (Alpha) Component: Testing QA | Resolution: Keywords:| --+ Changes (by red): * status: new = accepted * owner: = red -- Ticket URL: https://fedorahosted.org/cloud/ticket/38#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] #19: File F21 change: Docker Host Image
#19: File F21 change: Docker Host Image ---+--- Reporter: mattdm | Owner: red Type: task | Status: accepted Priority: blocker| Milestone: Fedora 21 (Feature Deadline) Component: Docker Host Image | Resolution: Keywords: | ---+--- Comment (by dwalsh): Replying to [comment:12 red]: Thanks, Dan. You're already working on making docker and SELinux work, right? Anything you need from us to go on from here? Not currently. The hardest thing will be handling of volumes with SELinux. IE If I want to mount random content into a container, how do I label it. -- Ticket URL: https://fedorahosted.org/cloud/ticket/19#comment:15 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] #19: File F21 change: Docker Host Image
#19: File F21 change: Docker Host Image ---+--- Reporter: mattdm | Owner: red Type: task | Status: accepted Priority: blocker| Milestone: Fedora 21 (Feature Deadline) Component: Docker Host Image | Resolution: Keywords: | ---+--- Comment (by dwalsh): Replying to [comment:13 red]: Replying to [comment:8 walters]: Can you elaborate a bit on what you feel the biggest problems are for the rpm-ostree side? Well, also, since we were speaking about docker and SELinux - is it still necessary with ostree to disable SELinux to boot into a tree as outlined in the [http://rpm-ostree.cloud.fedoraproject.org/#/installation installation guide]? Obviously, that would be a major show stopper. I am not sure, have to let Colin Check in on this one. I have made some changes to the SELinux policy in Rawhide for OSTree, and I think Miroslav has been back porting them into F20. I have talked to Colin about potential problems with people doing restorecon -R -v /. We might have to implement some changes to the SELinux tool chain. -- Ticket URL: https://fedorahosted.org/cloud/ticket/19#comment:16 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] #19: File F21 change: Docker Host Image
#19: File F21 change: Docker Host Image ---+--- Reporter: mattdm | Owner: red Type: task | Status: accepted Priority: blocker| Milestone: Fedora 21 (Feature Deadline) Component: Docker Host Image | Resolution: Keywords: | ---+--- Comment (by walters): Replying to [comment:13 red]: Well, also, since we were speaking about docker and SELinux - is it still necessary with ostree to disable SELinux to boot into a tree as outlined in the [http://rpm-ostree.cloud.fedoraproject.org/#/installation installation guide]? Obviously, that would be a major show stopper. Nope, that's been fixed for quite a while. I updated the web page. The qcow2 images you download are in enforcing mode. Anaconda will install in enforcing mode. Now, using OSTree to *parallel install* is a trickier case, but should be fixed by https://bugzilla.redhat.com/show_bug.cgi?id=1061064 -- Ticket URL: https://fedorahosted.org/cloud/ticket/19#comment:17 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] #24: File F21 change: Big Data Image
#24: File F21 change: Big Data Image +--- Reporter: mattdm | Owner: Type: task| Status: new Priority: normal | Milestone: Fedora 21 (Feature Deadline) Component: Big Data Image | Resolution: Keywords: | +--- Comment (by jeid64): Mattdm, I can own this ticket and work on it. -- Ticket URL: https://fedorahosted.org/cloud/ticket/24#comment:9 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: Please FIX the TO address from the Cloud Tracker
On 5 Apr 2014 00:12, Dave Neary dne...@redhat.com wrote: As an FYI, you could filter on: X-Trac-Project: cloud Can that be set to something a little less generic please? too. Cheers, Dave. On 04/04/2014 06:09 PM, Matthew Miller wrote: On Fri, Apr 04, 2014 at 09:31:12AM -0500, Troy Dawson wrote: I don't know if anyone else is, but I'm still getting these with the weird To: address. Not that I don't believe you Robyn, but I'm not seeing it. I changed another thing. Let us know if still is causing problems. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct ___ 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: Please FIX the TO address from the Cloud Tracker
On Sat, Apr 05, 2014 at 04:36:58PM +0100, Peter Robinson wrote: As an FYI, you could filter on: X-Trac-Project: cloud Can that be set to something a little less generic please? I don't think so, without changing the name of the trac instance itself, which probably has other ramifications. But, I did set the SMTP from name to 'Fedora Cloud Trac Tickets' so you could additionally filter on that. -- Matthew Miller-- Fedora Project--mat...@fedoraproject.org Tepid change for the somewhat better! ___ 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] #21: File F21 change: Install without i10n / l18n support (w/optional install)
On Sat, Apr 05, 2014 at 07:26:41PM +0900, Sandro red Mathys wrote: So I thought I'd go ahead and write a change proposal: https://fedoraproject.org/wiki/Changes/Smaller_Cloud_Image_Footprint Let me know what you think. Looks good to me. I added a link to the related change for %license. -- Matthew Miller-- Fedora Project--mat...@fedoraproject.org Tepid change for the somewhat better! ___ 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] #24: File F21 change: Big Data Image
#24: File F21 change: Big Data Image +--- Reporter: mattdm | Owner: Type: task| Status: new Priority: normal | Milestone: Fedora 21 (Feature Deadline) Component: Big Data Image | Resolution: Keywords: | +--- Comment (by mattdm): Replying to [comment:9 jeid64]: Mattdm, I can own this ticket and work on it. Awesome, thanks. hguemar, do you want to be co-owner? -- Ticket URL: https://fedorahosted.org/cloud/ticket/24#comment:10 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