Re: More information on Cloud spins
On Thu, May 8, 2014 at 10:04 AM, Amit Saha as...@redhat.com wrote: I happened to come across a ticket that aims to create cloud images for spins. I haven't followed any discussion at all on that. Where can I learn more about this? Basically, I am interested to see if a stripped down version of Fedora Scientific can be offered as a cloud image as well. Not sure what ticket you are referring to. I don't think we have any plans to convert any spin into a cloud image. I doubt it would make any sense for any of the images. I see how you come to think creating a scientific spin image would be a good thing - many of the tools are often used in the cloud by scientific researchers (I did cloud at a technical university, so I know they do for sure). BUT, we want to keep cloud images small and highly tailored, and therefore a generic scientific image would just not work. It would need to be tailored for one specific usage. So for those scientific use cases (minus big data, for which we'll have an image), we're just going to recommend the base image. People can either modify that image by adding more software themselves before uploading it to their cloud or launch it as-is and install the necessary software afterwards. If you think one or two highly tailored images would make sense, bring up your use case (and be ready to work on it / do all the work) and we're happy to consider it. Personally, I could imagine a R image but not sure it's worth the effort - the base image is seriously easily turned into a R image by end users. Oh, and the ticket you've seen - maybe that's been about the cloud images having to follow the spin process. That has nothing to do with the existing spins. -- Sandro ___ 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] #3: Fedora.next product branding for cloud - list of questions
#3: Fedora.next product branding for cloud - list of questions ---+--- Reporter: rbergero | Owner: Type: task | Status: closed Priority: major | Milestone: Fedora 21 Component: Collaboration Communication | (Final) Keywords: meeting| Resolution: fixed ---+--- Changes (by jzb): * resolution: = fixed * status: new = closed Comment: I think this one is now complete. I'm closing this unless we need further action. -- Ticket URL: https://fedorahosted.org/cloud/ticket/3#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
[cloud] #54: define shell command API available in Fedora Atomic
#54: define shell command API available in Fedora Atomic ---+--- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Docker Host Image | Keywords: ---+--- This is a list of shell commands (or at least the packages which contain them) which are expected to work in a cloud metadata userscript at initial Fedora Atomic launch. We should maintain this list and note changes in the release notes, have a deprecation procedure, and so on. The initial goal for Fedora Atomic is to be as small as reasonably possible, including removing Python (and, not including python and yum/dnf on the list). -- Ticket URL: https://fedorahosted.org/cloud/ticket/54 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
[cloud] #55: define shell command API available in Fedora Cloud Base Image
#55: define shell command API available in Fedora Cloud Base Image --+--- Reporter: mattdm| Owner: Type: task | Status: new Priority: normal| Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Keywords: --+--- This is a list of shell commands (or at least the packages which contain them) which are expected to work in a cloud metadata userscript at initial Fedora Cloud Base Image launch. We should maintain this list and note changes in the release notes, have a deprecation procedure, and so on. The initial goal for Fedora Cloud Base Image is to balance size and usefulness -- python and yum/dnf will be in the list, for example. For a more edgy image, see Fedora Atomic. -- Ticket URL: https://fedorahosted.org/cloud/ticket/55 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] #54: define shell command API available in Fedora Atomic
#54: define shell command API available in Fedora Atomic ---+ Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Docker Host Image | Resolution: Keywords: | ---+ Comment (by red): A ticket is good to work on an initial list and maybe discuss further changes later on, but shouldn't the actual maintained list better be kept in a wiki? :) -- Ticket URL: https://fedorahosted.org/cloud/ticket/54#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: [cloud] #46: Project Atomic and Fedora Docker Host Image
#46: Project Atomic and Fedora Docker Host Image ---+- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Branch) Component: Docker Host Image | Resolution: Keywords: meeting| ---+- Comment (by jzb): Do we need this to continue being tagged for meetings? -- Ticket URL: https://fedorahosted.org/cloud/ticket/46#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] #45: need three packages added to the fedora21 cloud iamge
#45: need three packages added to the fedora21 cloud iamge +- Reporter: sdake | Owner: jzb Type: task| Status: closed Priority: normal | Milestone: Fedora 21 (Branch) Component: Cloud Base Image| Resolution: wontfix Keywords: OpenStack, meeting | +- Changes (by jzb): * resolution: = wontfix * status: assigned = closed Comment: No response, so I'm closing this for now. If necessary we can reopen. -- Ticket URL: https://fedorahosted.org/cloud/ticket/45#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] #56: tracking ticket for conversations around shipping ostree... trees. (was: tracking ticket for conversations around shipping ostree images)
#56: tracking ticket for conversations around shipping ostree... trees. ---+--- Reporter: mattdm | Owner: Type: task | Status: new Priority: blocker| Milestone: Fedora 21 Component: Collaboration Communication | (Branch) Keywords: | Resolution: ---+--- -- Ticket URL: https://fedorahosted.org/cloud/ticket/56#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
[cloud] #56: tracking ticket for conversations around shipping ostree images
#56: tracking ticket for conversations around shipping ostree images ---+--- Reporter: mattdm | Owner: Type: task | Status: new Priority: blocker| Milestone: Fedora 21 Component: Collaboration Communication | (Branch) | Keywords: ---+--- We've decided to base the Fedora Docker host image on Project Atomic, and therefore rpm-ostree. This means several big conversations, including with QA, Rel Eng, and the mirror network. It will mean some new development and possibly extra resources. But first we need to figure out the questions to ask, and then we need to ask them, and then we need to find answers, or provide them where they don't already exist. -- Ticket URL: https://fedorahosted.org/cloud/ticket/56 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] #51: start communication/collaboration on cloud image updates
#51: start communication/collaboration on cloud image updates -+--- Reporter: mattdm | Owner: roshi Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | -+--- Changes (by roshi): * owner: = roshi * status: new = assigned -- Ticket URL: https://fedorahosted.org/cloud/ticket/51#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
Fedora Cloud Meeting Minutes 5 May 2014
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks to everyone who showed up participated today. Minutes below... === #fedora-meeting Meeting === Meeting started by jzb at 14:02:32 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-05-08/fedora-meeting.2014-05-08-14.02.log.html . Meeting summary - --- * start communication/collaboration on cloud image updates (jzb, 14:07:04) * https://fedorahosted.org/cloud/ticket/51 (jzb, 14:07:12) * yum/dnf rpm-ostree (jzb, 14:12:30) * http://lists.rpm.org/pipermail/rpm-maint/2014-April/003682.html (jzb, 14:15:50) * ACTION: mattdm create All the Things ticket (components needed for image) (jzb, 14:30:52) * LINK: https://fedorahosted.org/cloud/ticket/54 (mattdm, 14:33:40) * LINK: https://fedorahosted.org/cloud/ticket/55 (mattdm, 14:35:52) * I made two tickets, one for the atomic list and one for generic (mattdm, 14:36:30) * ACTION: mattdm to make high-level ticket covering issues with shipping ostree trees... this will fork into qa and releng and mirror conversations (mattdm, 14:50:13) * LINK: https://fedorahosted.org/cloud/ticket/56 (mattdm, 14:55:56) * tracking ticket for conversations around shipping ostree... trees. (mattdm, 14:56:24) * HELP: that ticket -- needs help. please add yourself to cc if interested. (mattdm, 14:56:45) * ACTION: jzb Solicit folks who want to volunteer for the WG (jzb, 15:10:45) Meeting ended at 15:14:50 UTC. Action Items - * mattdm create All the Things ticket (components needed for image) * mattdm to make high-level ticket covering issues with shipping ostree trees... this will fork into qa and releng and mirror conversations * jzb Solicit folks who want to volunteer for the WG Action Items, by person - --- * jzb * jzb Solicit folks who want to volunteer for the WG * mattdm * mattdm create All the Things ticket (components needed for image) * mattdm to make high-level ticket covering issues with shipping ostree trees... this will fork into qa and releng and mirror conversations * **UNASSIGNED** * (none) People Present (lines said) - --- * mattdm (83) * jzb (60) * walters (47) * red_trela (26) * dgilmore (23) * geppetto (16) * roshi (13) * zodbot (12) * samkottler (11) * jwb (11) * jeid64 (8) * scollier (3) * mhayden (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot - -- 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/ iQEcBAEBAgAGBQJTa8quAAoJEKbW5zOgIHzUdn4H/3pdCbMS9w6Ilw54+kkR1kkZ AhYUrQfxo0J/r0lnVP+CLQdfVG/+1UYHhskcfYSes1hQr5u9Ep28uu8LxympA0kO djuVa1qMybdr+T6dITrgrRnC4AlCo0fZH88toGDSoddkKruuFOV7I/UwgVMj0Fx7 ukb0eRF+nERkGnirNUvPtsAU4p7XEDYXoDcF5t9IVoMQxH4GaVRAnO+HTewzXb6S EmDzexLGAMl76r1C6IBlHz1aF4jEjr3oa7AkWwtkO8+YQGdctbNQdOd6z/pXvAz9 /wYZzjgdW6S1YFTDtmo/DxjDa8so4WnoDjG2PKAhBatrIAVcs2HX6y8UJr7pUH8= =9Ljd -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: More information on Cloud spins
- Original Message - From: Sandro \red\ Mathys r...@fedoraproject.org To: Fedora Cloud SIG cloud@lists.fedoraproject.org Sent: Thursday, May 8, 2014 10:30:36 PM Subject: Re: More information on Cloud spins On Thu, May 8, 2014 at 10:04 AM, Amit Saha as...@redhat.com wrote: I happened to come across a ticket that aims to create cloud images for spins. I haven't followed any discussion at all on that. Where can I learn more about this? Basically, I am interested to see if a stripped down version of Fedora Scientific can be offered as a cloud image as well. Not sure what ticket you are referring to. I don't think we have any plans to convert any spin into a cloud image. I doubt it would make any sense for any of the images. I see how you come to think creating a scientific spin image would be a good thing - many of the tools are often used in the cloud by scientific researchers (I did cloud at a technical university, so I know they do for sure). BUT, we want to keep cloud images small and highly tailored, and therefore a generic scientific image would just not work. It would need to be tailored for one specific usage. So for those scientific use cases (minus big data, for which we'll have an image), we're just going to recommend the base image. People can either modify that image by adding more software themselves before uploading it to their cloud or launch it as-is and install the necessary software afterwards. If you think one or two highly tailored images would make sense, bring up your use case (and be ready to work on it / do all the work) and we're happy to consider it. Personally, I could imagine a R image but not sure it's worth the effort - the base image is seriously easily turned into a R image by end users. Oh, and the ticket you've seen - maybe that's been about the cloud images having to follow the spin process. That has nothing to do with the existing spins. Thanks for the explanation, Sandro. Yes, indeed that is the ticket which made me think that the specialized desktop spins were being considered in any way for the cloud images. I can see how that is a problem. I would think a cloud image with all the Python scientific tools would be a good offering. Not sure if anyone else think the same. ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
