Bug 1090886

Summary: Convert Fedora Cloud Image to Fedora Serve ("Adopt Your Cattle")
Product: [Fedora] Fedora Reporter: Jaroslav Reznik <jreznik>
Component: Changes TrackingAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact: Pete Travis <me>
Priority: unspecified    
Version: rawhideCC: kushal, mail, mattdm, me, sgallagh
Target Milestone: ---Flags: me: fedora_requires_release_note+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ChangeAcceptedF21 SelfContainedChange
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-08 15:22:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jaroslav Reznik 2014-04-24 11:01:42 UTC
This is a tracking bug for Change: Convert Fedora Cloud Image to Fedora Serve ("Adopt Your Cattle")
For more details, see: http://fedoraproject.org//wiki/Changes/Convert_Fedora_Cloud_Image_to_Fedora_Server

We provide a smooth path so a Cloud Base Image can be turned into Fedora Server. Fedora Cloud images are designed to be run and managed as scale-out undifferentiated "cattle", while Fedora Server is intended for more "pet-like" individually-managed servers.

Comment 1 Jaroslav Reznik 2014-07-04 10:43:45 UTC
This message is a reminder that Fedora 21 Accepted Changes Freeze Deadline is on 2014-07-08 [1].

At this point, all accepted Changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Freeze.

This bug should be set to the MODIFIED state to indicate that it achieved completeness. Status will be provided to FESCo right after the deadline. If, for any reasons, your Change is not in required state, let me know and we will try to find solution. For Changes you decide to cancel/move to the next release, please use the NEW status and set needinfo on me and it will be acted upon. 

In case of any questions, don't hesitate to ask Wrangler (jreznik). Thank you.

[1] https://fedoraproject.org/wiki/Releases/21/Schedule

Comment 2 Matthew Miller 2014-07-09 14:22:31 UTC
So -- we have not even started this. We _just_ figured out how we're going to do fedora-release packages for the different products. Since this is stand-alone, I'd like to... keep going and do it anyway, and basically do the development during alpha. If we don't have it working in time for the _beta_ freeze, we should pull it (as per the contingency plan).

Comment 3 Jaroslav Reznik 2014-10-07 12:23:55 UTC
This message is a reminder that Fedora 21 Change Checkpoint: 100% Code Complete Deadline (Former Accepted Changes 100% Complete) is on 2014-10-14 [1].

All Accepted Changes has to be code complete and ready to be validated in the Beta release (optionally by Fedora QA). Required bug state at this point is ON_QA.

As for several System Wide Changes, Beta Change Deadline is a point of contingency plan. All incompleted Changes will be reported to FESCo on 2014-10-15 meeting. In case of any questions, don't hesitate to ask Wrangler (jreznik).

[1] https://fedoraproject.org/wiki/Releases/21/Schedule

Comment 4 Jaroslav Reznik 2014-10-14 10:18:57 UTC
As per change co-owner, it's 100% complete. Moving to ON_QA.

Comment 5 Pete Travis 2014-10-26 06:52:16 UTC
Can someone please update the Release Notes section on the wiki, or at least point me at the bits?

Comment 6 Pete Travis 2014-10-27 04:04:25 UTC
Found it :)  I'll leave the needinfo up, if you wouldn't mind reviewing the copy at https://git.fedorahosted.org/cgit/docs/release-notes.git/commit/?id=c6aa8b60c0b2ba01b454a32e81f0801e80dfeed0

Comment 7 kushaldas@gmail.com 2014-10-27 14:07:58 UTC
+1 to the docs patch. It looks good to me.