March 2017 - cloud - Fedora Mailing-Lists

by Adam Miller

6 years

1
0
0 / 0

[atomic-wg] Issue #201 `Planning for the first Atomic VFAD`

by Adam Miller

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` Following along with the [proposal that reached general consensus on the mailing list](https://lists.fedoraproject.org/archives/list/cloud@lists.fedorapro..., I would like to take some time to schedule what work we will do on the very first Atomic VFAD. My initial proposal for what to work on is to move the [Fedora-Dockerfiles](https://github.com/fedora-cloud/Fedora-Dockerfiles) from GitHub into DistGit. I will also write up this workflow somewhere in the Cloud Wiki space (we should really move that to Atomic). `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/201

6 years

2
2
0 / 0

[atomic-wg] Issue #233 `Container guidelines for systemd based containers`

by Daniel J Walsh

dwalsh added a new comment to an issue you are following: `` Not sure here is the best place, but I would start by saying 1. Easily move applications from VM to container, using standard scripts. IE FROM fedora-init RUN dnf -y install httpd; systemctl enable httpd ADD MYPHP /var/www/html ... 2. Proper Logging. Journalctl and syslog actually work 3. Cleaning up Zombies 4. Multi Service containers. 5. Other systemd features like checking status, eventually additional cgroup (Requires CGROUPV2) `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/233

6 years

1
0
0 / 0

[atomic-wg] Issue #239 `Update BZ Container Review Component Template to allow fedora-review flag`

by James Hogarth

jhogarth added a new comment to an issue you are following: `` Ticket in fedora-infrastructure to fix this opened here: https://pagure.io/fedora-infrastructure/issue/5861 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/239

6 years

1
0
0 / 0

[atomic-wg] Issue #239 `Update BZ Container Review Component Template to allow fedora-review flag`

by Mike Ruckman

The issue: `Update BZ Container Review Component Template to allow fedora-review flag` of project: `atomic-wg` has been assigned to `jhogarth` by roshi. https://pagure.io/atomic-wg/issue/239

6 years

1
0
0 / 0

[atomic-wg] Issue #233 `Container guidelines for systemd based containers`

by Jan Pazdziora

adelton added a new comment to an issue you are following: `` > BTW Even if we got oci-systemd-hook into debian, we would still need to get projectatomic/docker in since docker rejected the patch to run hooks directly. Would it help if the execution of the hook was dependent on some label in the image? That way the container author could have more control over the behaviour and docker might be more inclined to allow that mechanism. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/233

6 years

1
0
0 / 0

Fedora Atomic Host Two Week Release Announcement

by noreply＠fedoraproject.org

A new Fedora Atomic Host update is available via an OSTree commit: Commit: ba95a4665776b58d342ad9cc367111179f9b8fcf19c6606f8964a8ec1622cadc Version: 25.67 Existing systems can be upgraded in place via e.g. `atomic host upgrade` or `atomic host deploy`. Corresponding image media for new installations can be downloaded from: https://getfedora.org/en/cloud/download/atomic.html Respective signed CHECKSUM files can be found here: https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-2017... https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-2017... For direct download, the "latest" targets are always available here: https://getfedora.org/atomic_iso_latest https://getfedora.org/atomic_qcow2_latest https://getfedora.org/atomic_raw_latest https://getfedora.org/atomic_vagrant_libvirt_latest https://getfedora.org/atomic_vagrant_virtualbox_latest Filename fetching URLs are available here: https://getfedora.org/atomic_iso_latest_filename https://getfedora.org/atomic_qcow2_latest_filename https://getfedora.org/atomic_raw_latest_filename https://getfedora.org/atomic_vagrant_libvirt_latest_filename https://getfedora.org/atomic_vagrant_virtualbox_latest_filename For more information about the latest targets, please reference the Fedora Cloud Wiki space. https://fedoraproject.org/wiki/Cloud#Quick_Links Do note that it can take some of the mirrors up to 12 hours to "check-in" at their own discretion. Thank you, Fedora Release Engineering

6 years

2
2
0 / 0

Re: Fedora Cloud AMIs are not readable

by Sayan Chowdhury

On Tue, Feb 28, 2017 at 9:43 PM, Sayan Chowdhury <sayan.chowdhury2012(a)gmail.com> wrote: > On Tue, Feb 28, 2017 at 8:25 PM, Stephen John Smoogen <smooge(a)gmail.com> wrote: >> We are still working on this. >> >> On 27 February 2017 at 20:11, Matthew Miller <mattdm(a)fedoraproject.org> wrote: >>> On Thu, Feb 23, 2017 at 09:40:53AM -0700, Kevin Fenzi wrote: >>>> > Neither me or Kushal has access to the account. So, somebody who has >>>> > access to the account can go to the snapshot page and make the >>>> > Snapshots public. >>>> Hum. Who would that be then? Just Dennis? >>> >>> Did we find the answer to this? I have the account information recorded >>> in an encrypted file just in case. > > I have written a script just haven't tested it. The script makes all > the snapshots we have public. That should work for now. > Here is the script[1] that should make all the AMIs ready to be copied [1] https://gist.github.com/sayanchowdhury/ffbc1f847ba84d47a454e4fd3cc603fd -- Sayan Chowdhury <https://sayanchowdhury.dgplug.org/> Senior Software Engineer, Fedora Engineering - Emerging Platform GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B Proud to work at The Open Organization!

6 years

2
1
0 / 0

Cloud Meeting Minutes 2017-03-01

by Dusty Mabe

summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-01/atomic_wg.2... full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-01/atomic_wg.2... ============================ #fedora-meeting-1: atomic_wg ============================ Meeting started by roshi at 17:02:11 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-01/atomic_wg.2... . Meeting summary --------------- * Roll Call (roshi, 17:02:20) * Decide on version scheme for F26 (roshi, 17:04:16) * LINK: https://pagure.io/atomic-wg/issue/229 (roshi, 17:04:19) * Previous Meeting Follow-Up (roshi, 17:06:06) * ACTION: dusty to create atomic-wg page for future VFAD topics (dustymabe, 17:08:01) * ACTION: sayan to create ticket on moving fedimg from libcloud to boto (dustymabe, 17:09:41) * F26 naming scheme (roshi, 17:10:23) * LINK: https://pagure.io/atomic-wg/issue/229 (roshi, 17:10:25) * LINK: https://fedoraproject.org/wiki/Cloud/VFAD_ideas (jberkus, 17:15:27) * LINK: https://fedoraproject.org/wiki/Cloud/VFAD_ideas (trishnag, 17:15:46) * AGREED: - use the $major.$datestamp.$serial for F26 and close the ticket. (roshi, 17:27:42) * Planning first atomic VFAD (roshi, 17:28:43) * LINK: https://pagure.io/atomic-wg/issue/201 (roshi, 17:28:45) * Ship fedora-motd (roshi, 17:30:06) * LINK: https://pagure.io/atomic-wg/issue/160 (roshi, 17:30:08) * Fedora OpenShift Playground (FOSP) (roshi, 17:36:49) * LINK: https://pagure.io/atomic-wg/issue/153 (roshi, 17:36:51) * Still waiting on hardware for the FOSP efforts (roshi, 17:39:10) * Open Floor (roshi, 17:39:17) * LINK: https://pagure.io/atomic-wg/issues?status=Open&tags=containers (dustymabe, 17:41:38) Meeting ended at 17:54:27 UTC. Action Items ------------ * dusty to create atomic-wg page for future VFAD topics * sayan to create ticket on moving fedimg from libcloud to boto Action Items, by person ----------------------- * sayan * sayan to create ticket on moving fedimg from libcloud to boto * **UNASSIGNED** * dusty to create atomic-wg page for future VFAD topics People Present (lines said) --------------------------- * dustymabe (91) * roshi (75) * jberkus (54) * zodbot (20) * walters (17) * kushal (8) * jhogarth (8) * jlebon (7) * trishnag (6) * gbraad (5) * sayan (4) * ksinny (4) * jbrooks (4) * miabbott (3) * bowlofeggs (2) * tflink (2) * walters_ (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

6 years

1
0
0 / 0

[atomic-wg] Issue #233 `Container guidelines for systemd based containers`

by Daniel J Walsh

dwalsh added a new comment to an issue you are following: `` BTW Even if we got oci-systemd-hook into debian, we would still need to get projectatomic/docker in since docker rejected the patch to run hooks directly. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/233

6 years

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud March 2017