Re: [cloud] #105: Missing Cockpit RPMs in Fedora Atomic 22
#105: Missing Cockpit RPMs in Fedora Atomic 22 ---+ Reporter: jzb| Owner: Type: defect | Status: new Priority: blocker| Milestone: Fedora 22 Component: Docker Host Image | Resolution: Keywords: meeting| ---+ Comment (by dustymabe): The Cloud WG discussed this today and the consensus is that we should revert to a traditional rpm/service based approach for F22 and re-release the container based approach at a future date with proper announcements and documentation that help people migrate easily. -- Ticket URL: https://fedorahosted.org/cloud/ticket/105#comment:7 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] #99: AMI lifetimes (Cloud WG members vote needed)
#99: AMI lifetimes (Cloud WG members vote needed) --+ Reporter: oddshocks | Owner: oddshocks Type: task | Status: new Priority: normal| Milestone: Fedora 22 Component: Infrastructure Release Engineering | Resolution: Keywords: aws, images, vote, policy | --+ Comment (by roshi): Going with the summary in comment #6 my votes are: 2 and 3. My understanding of AWS and it's users is that AMI's should be there for a long long time. Sans some means to monitor how many times it gets launched, it's probably better to keep them than not to. What's the costs we're looking at? As for the milestone AMIs, I don't really see a reason to keep them after final. Anything we need to debug we should be able to do in another service or locally. -- Ticket URL: https://fedorahosted.org/cloud/ticket/99#comment:8 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] #103: bugzilla components for base image and Atomic Host
#103: bugzilla components for base image and Atomic Host -+- Reporter: walters | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: | -+- Comment (by walters): There is currently in Bugzilla a toplevel Atomic product which was created a long time ago, and we still get some bugs there. But I don't think it worked out to have Atomic as its own product for various reasons (versioning, branding, etc.) We should create e.g.: - Fedora/fedora-cloud-atomic-host for the Atomic Host - Fedora/fedora-base-docker-image for the Docker Base image (Other name suggestions welcome, in particular whether we should include cloud/base or just drop the WG part) -- Ticket URL: https://fedorahosted.org/cloud/ticket/103#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] #105: Missing Cockpit RPMs in Fedora Atomic 22
#105: Missing Cockpit RPMs in Fedora Atomic 22 ---+ Reporter: jzb| Owner: Type: defect | Status: new Priority: blocker| Milestone: Fedora 22 Component: Docker Host Image | Resolution: Keywords: meeting| ---+ Comment (by kushal): Replying to [comment:7 dustymabe]: The Cloud WG discussed this today and the consensus is that we should revert to a traditional rpm/service based approach for F22 and re-release the container based approach at a future date with proper announcements and documentation that help people migrate easily. +1 from me. -- Ticket URL: https://fedorahosted.org/cloud/ticket/105#comment:8 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
