Re: [cloud] #16: rename cloud spin kickstart to distinguish the cloud base image

2014-06-02 Thread Fedora Cloud Trac Tickets
#16: rename cloud spin kickstart to distinguish the cloud base image
+-
 Reporter:  mattdm  |   Owner:  red
 Type:  task|  Status:  closed
 Priority:  minor   |   Milestone:  Fedora 21 (Branch)
Component:  --- |  Resolution:  fixed
 Keywords:  |
+-
Changes (by mattdm):

 * resolution:   = fixed
 * status:  assigned = closed


Comment:

 this looks like it's done

-- 
Ticket URL: https://fedorahosted.org/cloud/ticket/16#comment:3
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] #16: rename cloud spin kickstart to distinguish the cloud base image

2014-04-24 Thread Fedora Cloud Trac Tickets
#16: rename cloud spin kickstart to distinguish the cloud base image
-+-
 Reporter:  mattdm   |   Owner:
 Type:  task |  Status:  new
 Priority:  minor|   Milestone:  Fedora 21 (Branch)
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+-

Comment (by red):

 So I think we agreed on the name (Fedora Cloud Base) for the image at
 the meeting just now.

 Regarding the kickstart file, I asked for clarification why two (i.e.
 cloud-base-base.ks and cloud-base.ks) are necessary. My impression was
 that we'd just have cloud-base.ks which would have two purposes:
 - Create the Fedora Cloud Base image (what I think mattdm called fedora-
 base.ks above)
 - Be %include'd in all other (except maybe leading-edge Docker/Atomic)
 ks/images (what I think mattdm called fedora-base-base.ks above)

 So why is there a need for two separate ks files?

-- 
Ticket URL: https://fedorahosted.org/cloud/ticket/16#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