Re: glibc fix to allow instlangs to really work -- too late for f22?
On Wed, Mar 18, 2015 at 11:50 AM, Matthew Miller mat...@fedoraproject.org wrote: The glibc team has a fix for a longstanding issue, which is that instlangs hasn't worked in the installer. This means that in a minimal image of about 400MB, 100MB is translation information. (Of course we want Fedora to be international, but there are many cases like Docker containers where no human is really even looking inside, so it's just overhead.) In the cloud and docker images, we've been carrying horribly hacks (really, horrible) to strip this out ofter the fact. The new fix would let us get the same effect the right way. I'm told that this is a low-risk change and does not affect the rest of glibc. So, the question -- I guess mostly for FESCo, but in general -- is: should we get this in before the beta, or should it wait for F23? How long has it been in F-23? ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
glibc fix to allow instlangs to really work -- too late for f22?
The glibc team has a fix for a longstanding issue, which is that instlangs hasn't worked in the installer. This means that in a minimal image of about 400MB, 100MB is translation information. (Of course we want Fedora to be international, but there are many cases like Docker containers where no human is really even looking inside, so it's just overhead.) In the cloud and docker images, we've been carrying horribly hacks (really, horrible) to strip this out ofter the fact. The new fix would let us get the same effect the right way. I'm told that this is a low-risk change and does not affect the rest of glibc. So, the question -- I guess mostly for FESCo, but in general -- is: should we get this in before the beta, or should it wait for F23? -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ 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: glibc fix to allow instlangs to really work -- too late for f22?
My 2cts as Cloud SIG member is that we shouldn't wait for F23 as long as it's ready for beta or even shortly before. This is not just an annoyance, this is an huge impediment toward successful cloud product. I kindly ask fesco to take this into consideration Regards, H. ___ 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: glibc fix to allow instlangs to really work -- too late for f22?
On Wed, Mar 18, 2015 at 7:50 AM, Matthew Miller mat...@fedoraproject.org wrote: The glibc team has a fix for a longstanding issue, which is that instlangs hasn't worked in the installer. This means that in a minimal image of about 400MB, 100MB is translation information. (Of course we want Fedora to be international, but there are many cases like Docker containers where no human is really even looking inside, so it's just overhead.) In the cloud and docker images, we've been carrying horribly hacks (really, horrible) to strip this out ofter the fact. The new fix would let us get the same effect the right way. I'm told that this is a low-risk change and does not affect the rest of glibc. So, the question -- I guess mostly for FESCo, but in general -- is: should we get this in before the beta, or should it wait for F23? Isn't this causing RPM dependency issues when trying to create rawhide chroots on RHEL6 hosts via mock? I am fairly sure it's the reason COPR rawhide chroots are failing. If so, then I don't think we want it in f22 until that is fixed. josh ___ 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: Testables for beta TC2
On Tuesday, March 17, 2015 09:26:45 AM Joe Brockmeier wrote: On 03/17/2015 04:56 AM, Kushal Das wrote: Anyone knows why the standard cloud images are missing from the above mentioned location? I can only see Atomic and Vagrant images. Cloud base failed to install, seems its fixed in the last nightlies. Hrm. That's a good question. We should also have Vagrant boxes for the standard Cloud image. There is no such proposed image and it is too late to go adding for Fedora 22. it needs to be added to rawhide if you want it in Fedora 23 Dennis Any volunteers to chase this down? ___ 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 image lifetimes
Greetings! We sort of ran out of time in today's Cloud WG meeting, but I did want to ask: What are your thoughts on AMI lifetimes? That is to say, how long should EC2 AMIs exist before they're deleted? A few points to consider: - AMIs only cost us for storage, so it's not a *huge* cost to maintain a public AMI - At the same time, there are a lot of AMIs, since we build 2-4 per AWS region per build, and that number is growing - There are 9 regions now, and we have 2 virtualization types, and 2 volume types, as well (9 regions * 2 * 2 = 36 AMIs per Base image build, 18 for Atomic builds (since they are only available in HVM format)) - This total number will only grow larger as we add instance-store AMIs, and so on - This isn't even taking into account any costs we'll have once we secure a deal with other providers like HP, Rackspace, and GCE, to maintain public images on their services I propose we have some sort of discussion regarding how long cloud image builds should be available on services like AWS. I suspect this will resolve to having different lifetimes for scratch, test, RC, final, and maybe other build types. Any input is appreciated. We can certainly talk about this at next week's meeting, as well. -- David ___ 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 image lifetimes
On Wed, Mar 18, 2015 at 3:38 PM, David Gay d...@redhat.com wrote: Greetings! We sort of ran out of time in today's Cloud WG meeting, but I did want to ask: What are your thoughts on AMI lifetimes? That is to say, how long should EC2 AMIs exist before they're deleted? A few points to consider: - AMIs only cost us for storage, so it's not a *huge* cost to maintain a public AMI - At the same time, there are a lot of AMIs, since we build 2-4 per AWS region per build, and that number is growing - There are 9 regions now, and we have 2 virtualization types, and 2 volume types, as well (9 regions * 2 * 2 = 36 AMIs per Base image build, 18 for Atomic builds (since they are only available in HVM format)) - This total number will only grow larger as we add instance-store AMIs, and so on - This isn't even taking into account any costs we'll have once we secure a deal with other providers like HP, Rackspace, and GCE, to maintain public images on their services I propose we have some sort of discussion regarding how long cloud image builds should be available on services like AWS. I suspect this will resolve to having different lifetimes for scratch, test, RC, final, and maybe other build types. Any input is appreciated. We can certainly talk about this at next week's meeting, as well. -- David ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct In God We Trust - All Others Bring Data ;-) Surely you or someone on the team must have some raw data on usage for the existing AMIs, including comparisons for how much usage Fedora AMIs get vs. CentOS AMIs and RHEL AMIs. Don't build / maintain what people aren't using! If you have raw data, I'd be happy to explore it for you - email me off-list if you need an NDA or something like that. -- OSJourno: Robust Power Tools for Digital Journalists http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-journalists Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday. ___ 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 Docs
Hey cloud team, I think we need some cloud docs. Fedora has a lot to offer in the cloud area, and I'm sure that those engaged in the space are excited that Fedora has what they are looking for. The uninitiated, on the other hand, are looking for what Fedora has, and we can do better to demonstrate that. We have a cloud guide, https://git.fedorahosted.org/cgit/docs/cloud-guide.git/ . It covers some basics, ie euca2ools, but never really made it out of draft state, and your work has left it far behind. We don't have anyone on the Docs team fully engaged to track the cloud space, or anyone on the cloud team engaged to maintain that guide. Also, it's written in docbook, and a lot of folks aren't into that. So, as I'm working on some tooling for a new Fedora Docs site, I'd like to know what would get *you* into writing about Fedora Cloud. In the most direct sense, it's a question about markup and delivery, ie a collection of markdown or reStructuredText files in a git repo. In a broad sense, anything along the lines of I would write docs for using Fedora Cloud, if... would be great. Hopefully, we can find some balance between cloud and writing expertise and deliver something exciting. At this point, I'm focusing on enabling you; let's work that out. -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanet...@fedoraproject.org ___ 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: Fedora Cloud Docs
On Wed, Mar 18, 2015 at 10:14 PM, Pete Travis li...@petetravis.com wrote: Hey cloud team, I think we need some cloud docs. Fedora has a lot to offer in the cloud area, and I'm sure that those engaged in the space are excited that Fedora has what they are looking for. The uninitiated, on the other hand, are looking for what Fedora has, and we can do better to demonstrate that. We have a cloud guide, https://git.fedorahosted.org/cgit/docs/cloud-guide.git/ . It covers some basics, ie euca2ools, but never really made it out of draft state, and your work has left it far behind. We don't have anyone on the Docs team fully engaged to track the cloud space, or anyone on the cloud team engaged to maintain that guide. Also, it's written in docbook, and a lot of folks aren't into that. So, as I'm working on some tooling for a new Fedora Docs site, I'd like to know what would get *you* into writing about Fedora Cloud. In the most direct sense, it's a question about markup and delivery, ie a collection of markdown or reStructuredText files in a git repo. In a broad sense, anything along the lines of I would write docs for using Fedora Cloud, if... would be great. Hopefully, we can find some balance between cloud and writing expertise and deliver something exciting. At this point, I'm focusing on enabling you; let's work that out. -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanet...@fedoraproject.org ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct I'm doing a lot of work with Docker and very little with other cloud modalities. I'm building and deploying Docker images on Fedora and would be happy to contribute some writing about them. -- OSJourno: Robust Power Tools for Digital Journalists http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-journalists Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday. ___ 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: Testables for beta TC2
On Wed, Mar 18, 2015 at 03:12:12PM -0400, Joe Brockmeier wrote: Oh, good. For a minute, I thought I had imagined that we had asked for Atomic Cloud and was going to feel very bad. Still needs someone to create the kickstart file. It looks offhand that just copying fedora-cloud-atomic-vagrant.ks to fedora-cloud-base-vagrant.ks and replacing %include fedora-cloud-atomic.ks with %include fedora-cloud-base.ks _may_ be all that's needed there. In fact, I'll go ahead and do that now. -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ 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: Testables for beta TC2
On Wed, Mar 18, 2015 at 11:10:33AM -0500, Dennis Gilmore wrote: Hrm. That's a good question. We should also have Vagrant boxes for the standard Cloud image. There is no such proposed image and it is too late to go adding for Fedora 22. it needs to be added to rawhide if you want it in Fedora 23 https://fedoraproject.org/wiki/Changes/Vagrant_Box_Atomic is an accepted change, and includes both Fedora Atomic Host and Fedora Cloud flavors. I think this is just an oversight / miscommunication. -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ 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: Testables for beta TC2
On 03/18/2015 03:08 PM, Matthew Miller wrote: On Wed, Mar 18, 2015 at 11:10:33AM -0500, Dennis Gilmore wrote: Hrm. That's a good question. We should also have Vagrant boxes for the standard Cloud image. There is no such proposed image and it is too late to go adding for Fedora 22. it needs to be added to rawhide if you want it in Fedora 23 https://fedoraproject.org/wiki/Changes/Vagrant_Box_Atomic is an accepted change, and includes both Fedora Atomic Host and Fedora Cloud flavors. I think this is just an oversight / miscommunication. Oh, good. For a minute, I thought I had imagined that we had asked for Atomic Cloud and was going to feel very bad. -- Joe Brockmeier | Project Atomic Doer of Things j...@redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ signature.asc Description: OpenPGP digital 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: Cloud SIG meeting minutes (2015-03-18)
Action Items * jzb help find scollier additional maintainer for dockerfiles On this item, I believe that the CentOS folks are interested in working together on Dockerfiles maintenance. Perhaps CentOS Dockerfiles and Fedora Dockerfiles could live together under Project Atomic? Jason ___ 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 SIG meeting minutes (2015-03-18)
On Wed, Mar 18, 2015 at 06:04:22PM -0400, Jason Brooks wrote: * jzb help find scollier additional maintainer for dockerfiles On this item, I believe that the CentOS folks are interested in working together on Dockerfiles maintenance. Perhaps CentOS Dockerfiles and Fedora Dockerfiles could live together under Project Atomic? That'd definitely be interesting. (As would a combined registry of images!) -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ 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] #93: Getting sha256sum published for the cloud images
#93: Getting sha256sum published for the cloud images --+ Reporter: kushal| Owner: Type: task | Status: new Priority: normal| Milestone: Fedora 22 Component: Infrastructure Release Engineering | Resolution: Keywords: meeting | --+ Comment (by mattdm): An alternative (or additional?) approach might be to publish indexes in the simplestreams format, as Ubuntu does. See for example https://cloud- images.ubuntu.com/releases/streams/v1/com.ubuntu.cloud:released:download.json (or basically all the examples under https://cloud- images.ubuntu.com/releases/streams/v1/). (The format doesn't seem to be heavily documented anywhere, but here's Ubuntu's lib: https://launchpad.net/ubuntu/+source/simplestreams) -- Ticket URL: https://fedorahosted.org/cloud/ticket/93#comment:6 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 SIG meeting minutes (2015-03-18)
=== #fedora-meeting-1: Fedora Cloud SIG === Meeting started by kushal at 19:01:35 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2015-03-18/fedora-meeting-1.2015-03-18-19.01.log.html . Meeting summary --- * rollcall (kushal, 19:01:45) * Action items from previous meeting (kushal, 19:04:47) * Maintaining Fedora docker images for f22 #97 (kushal, 19:06:22) * Care and Feeding, Fedora Dockerfiles #84 (kushal, 19:14:53) * LINK: https://fedorahosted.org/cloud/ticket/84 (jzb, 19:16:32) * ACTION: jzb help find scollier additional maintainer for dockerfiles (jzb, 19:25:14) * ACTION: jzb (and others) update dockerfiles for dnf (jzb, 19:25:38) * Getting sha256sum published for the cloud images https://fedorahosted.org/cloud/ticket/93 (kushal, 19:30:56) * LINK: http://dl.fedoraproject.org/pub/alt/stage/22_Beta_TC2/Cloud-Images/x86_64/Images/Fedora-Cloud-Images-x86_64-22_Beta_TC2-CHECKSUM (dgilmore, 19:33:48) * LINK: http://paste.fedoraproject.org/199747/26707461/ (dgilmore, 19:37:51) * LINK: https://fedorahosted.org/cloud/ticket/93 (dustymabe, 19:41:15) * ACTION: kushal wil ask Lennart for more specific use case and details for #93 (kushal, 19:52:34) * LINK: http://cloud.fedoraproject.org/fedora-19.x86_64.qcow2 (dgilmore, 19:55:25) * LINK: http://cloud.fedoraproject.org/fedora-21.x86_64.qcow2 (dgilmore, 19:55:34) * LINK: http://cloud.fedoraproject.org/fedora/21/x86_64/SHA256SUM (dgilmore, 19:56:48) * Atomic as separate spin (or, going the other way, main cloud edition)? https://fedorahosted.org/cloud/ticket/96 (kushal, 19:58:26) * ACTION: create proposal page on wiki for Atomic spin for f23 forward, call for vote on mailing list. (jzb, 20:06:44) * ACTION: jzb create proposal page on wiki for Atomic spin for f23 forward, call for vote on mailing list. (jzb, 20:07:04) * Producing Updated Cloud/Atomic Images https://fedorahosted.org/cloud/ticket/94 (kushal, 20:07:27) * LINK: http://dl.fedoraproject.org/pub/alt/stage/21-20150309/ has the last updates compose (dgilmore, 20:11:09) Meeting ended at 20:15:13 UTC. Action Items * jzb help find scollier additional maintainer for dockerfiles * jzb (and others) update dockerfiles for dnf * kushal wil ask Lennart for more specific use case and details for #93 * create proposal page on wiki for Atomic spin for f23 forward, call for vote on mailing list. * jzb create proposal page on wiki for Atomic spin for f23 forward, call for vote on mailing list. Action Items, by person --- * jzb * jzb help find scollier additional maintainer for dockerfiles * jzb (and others) update dockerfiles for dnf * jzb create proposal page on wiki for Atomic spin for f23 forward, call for vote on mailing list. * kushal * kushal wil ask Lennart for more specific use case and details for #93 * scollier * jzb help find scollier additional maintainer for dockerfiles * **UNASSIGNED** * create proposal page on wiki for Atomic spin for f23 forward, call for vote on mailing list. People Present (lines said) --- * jzb (79) * kushal (73) * dgilmore (70) * dustymabe (19) * oddshocks (19) * scollier (13) * mattdm (12) * zodbot (7) * jsmith (4) * rtnpro (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Kushal -- Fedora Cloud Engineer CPython Core Developer Director Python Software Foundation http://kushaldas.in ___ 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: Testables for beta TC2
On Wed, Mar 18, 2015 at 03:40:07PM -0400, Matthew Miller wrote: Oh, good. For a minute, I thought I had imagined that we had asked for Atomic Cloud and was going to feel very bad. Still needs someone to create the kickstart file. It looks offhand that just copying fedora-cloud-atomic-vagrant.ks to fedora-cloud-base-vagrant.ks and replacing %include fedora-cloud-atomic.ks with %include fedora-cloud-base.ks _may_ be all that's needed there. In fact, I'll go ahead and do that now. But someone who is a feature owner should check that it actually works, make any necessary changes, and sync with releng so it starts getting built as part of the test candidates! -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
