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 mattdm): +1 to focusing on moving forward. I have great confidence that everyone here wants to do the right thing; there's just a lot up in the air all at once. I'm told that [https://fedoraproject.org/wiki/User:Ttomecek Tomas Tomecek] is working on something w.r.t. layered image building. Dennis, is that what you're referring to, or something else? If we land this for F23 (ideally, as I know you like to do, before alpha), can we also turn it on for F22? -- Ticket URL: https://fedorahosted.org/cloud/ticket/105#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
Fedora 22 is out, Fedora 23 is coming :)
Hi, Thank you everyone for a great Fedora 22 release. Things are stable now, before we can understand we will be in the alpha freeze for Fedora 23. So this is a good time to start working on the new features list for Fedora 23. 23rd June is the last date to submit a new system wide change for Fedora 23, 11th August is the alpha release for Fedora 23. Below I have written few points which came up in different discussions. Please feel free to comment/add/delete in this thread. * Better user documentation for cloud. We need something better than wiki. * Notification of pending updates in the base image. After login the user should get a motd message saying which all updates are pending (I have worked on this part time before). * Reduce the base cloud image size (we also have https://fedorahosted.org/fedora-badges/ticket/378 ) * testCloud (pushed back from Fedora 22 change list). * https://github.com/vmware/tdnf this might help us to go another step closer to remove Python stack from the cloud image.* Having a better * workstation to cloud story (came up in the last week's meeting). 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: Fedora 22 is out, Fedora 23 is coming :)
On Mon, Jun 1, 2015 at 5:50 AM, Kushal Das kushal...@gmail.com wrote: Hi, Thank you everyone for a great Fedora 22 release. Things are stable now, before we can understand we will be in the alpha freeze for Fedora 23. So this is a good time to start working on the new features list for Fedora 23. 23rd June is the last date to submit a new system wide change for Fedora 23, 11th August is the alpha release for Fedora 23. Below I have written few points which came up in different discussions. Please feel free to comment/add/delete in this thread. * Better user documentation for cloud. We need something better than wiki. For a volunteer-run documentation project, I'm extremely impressed with the Mozilla Developer Network's site. The underlying CMS is something they built after struggling with some commercial offerings. It's called Kuma and it's open source. Here's the link: https://developer.mozilla.org/en-US/docs/MDN/Kuma So I'd say: 1. Reach out to Mozilla 2. Package Kuma for Fedora 3. 4. Profit! ;-) [snip] My other long-standing wishlist item (one which I hack on myself sporadically) is a Boot2Docker-like point and click user interface for Windows 8.1+ Professional using Client Hyper-V as the hosting mechanism and Project Atomic (any of RHEL/CentOS/Fedora incarnations) as the Docker host. I've been able to make Atomic virtual machines via the bare metal Fedora Atomic ISO and run containers, but there's no point-and-click installer or documentation, both of which are mandatory for this use case. There's also no market research that indicates anyone but me would use it. ;-) -- 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
[Fedocal] Reminder meeting : Fedora Cloud Workgroup
Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2015-06-03 from 19:00:00 to 20:00:00 UTC At fedora-meet...@irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar/meeting/1999/ ___ 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 22 is out, Fedora 23 is coming :)
I think there is one good (nearly) point and click installer that we could use (more): vagrant. Currently there is only boxes for VirtualBox and libvirt, maybe it would be possible to provide boxes for VMware, Parallels, KVM etc. It would also be great to publish the meta-info on https://atlas.hashicorp.com to allow something like vagrant init fedora/atomic-23. If we are looking for a more boot2docker like solution it is good to know that boot2docker (cli) is being deprecated by docker machine which actually (soon) have a decent number of drivers (VirtualBox, VMware etc). Docker machine just downloads and uses the boot2docker.iso. It should be possible to use another iso as long as it follows some expectations by docker machine. In the near future there will also be a GUI for docker machine called https://kitematic.com/ . And to repeat what previously have been said, there is a desperate need of better documentation. On Mon, Jun 1, 2015 at 9:15 PM, M. Edward (Ed) Borasky zn...@znmeb.net wrote: On Mon, Jun 1, 2015 at 5:50 AM, Kushal Das kushal...@gmail.com wrote: Hi, Thank you everyone for a great Fedora 22 release. Things are stable now, before we can understand we will be in the alpha freeze for Fedora 23. So this is a good time to start working on the new features list for Fedora 23. 23rd June is the last date to submit a new system wide change for Fedora 23, 11th August is the alpha release for Fedora 23. Below I have written few points which came up in different discussions. Please feel free to comment/add/delete in this thread. * Better user documentation for cloud. We need something better than wiki. For a volunteer-run documentation project, I'm extremely impressed with the Mozilla Developer Network's site. The underlying CMS is something they built after struggling with some commercial offerings. It's called Kuma and it's open source. Here's the link: https://developer.mozilla.org/en-US/docs/MDN/Kuma So I'd say: 1. Reach out to Mozilla 2. Package Kuma for Fedora 3. 4. Profit! ;-) [snip] My other long-standing wishlist item (one which I hack on myself sporadically) is a Boot2Docker-like point and click user interface for Windows 8.1+ Professional using Client Hyper-V as the hosting mechanism and Project Atomic (any of RHEL/CentOS/Fedora incarnations) as the Docker host. I've been able to make Atomic virtual machines via the bare metal Fedora Atomic ISO and run containers, but there's no point-and-click installer or documentation, both of which are mandatory for this use case. There's also no market research that indicates anyone but me would use it. ;-) -- 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 ___ 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 22 is out, Fedora 23 is coming :)
On 06/01/2015 06:46 PM, Rickard von Essen wrote: I think there is one good (nearly) point and click installer that we could use (more): vagrant. Currently there is only boxes for VirtualBox and libvirt, maybe it would be possible to provide boxes for VMware, Parallels, KVM etc. It would also be great to publish the meta-info on https://atlas.hashicorp.com to allow something like vagrant init fedora/atomic-23. we should add this to the PRD / features for F23. Note that it's not always trivial to add support for new box types. (Note, KVM is implied with libvirt, so we have that covered. Does Vagrant have a Parallels provider? VMware seems like an important target.) If we are looking for a more boot2docker like solution it is good to know that boot2docker (cli) is being deprecated by docker machine which actually (soon) have a decent number of drivers (VirtualBox, VMware etc). Docker machine just downloads and uses the boot2docker.iso. It should be possible to use another iso as long as it follows some expectations by docker machine. In the near future there will also be a GUI for docker machine called https://kitematic.com/ . I haven't tried docker machine, we should look into this... Best, jzb -- Joe Brockmeier | Open Source and Standards (OSAS) j...@redhat.com | http://community.redhat.com/ Twitter: @jzb | http://projectatomic.io/ 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: Fedora.next PRD refresh
- Original Message - From: Stephen Gallagher sgall...@redhat.com To: Server SIG ser...@lists.fedoraproject.org, desk...@lists.fedoraproject.org, devel-annou...@lists.fedoraproject.org, cloud@lists.fedoraproject.org Sent: Tuesday, June 2, 2015 2:03:44 AM Subject: Fedora.next PRD refresh snipped == Future PRD Refreshes == Starting at Flock 2016 (yes, *next* calendar year), each working group will have a workshop scheduled at Flock to go over its PRD and plan for the following year. Note: because Flock generally falls between Alpha and Beta of a Fedora release, all PRD planning is presumed to be a directive for Fedora N+1 and N+2 at that time, not retroactively applied to the current release. The workshops are expected to cover the majority of the update, and then they will be brought back to the respective mailing lists for further review before being due to the Council one month after Flock concludes. +1. This is a good idea and it is important to push products toward on the right way. I am just curious why it would not be held from this year? because of time constrains? Rgds, Tuan ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct