cloud January 2016

cloud@lists.stg.fedoraproject.org

19 participants
96 discussions

[cloud] #123: Document process for using Fedora-Dockerfile branches
by Fedora Cloud Trac Tickets 23 Mar '16

23 Mar '16

#123: Document process for using Fedora-Dockerfile branches ----------------------+-------------------- Reporter: scollier | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: ----------------------+-------------------- This should probably go on the github repo home page. Need to provide instructions for users to submit to a specific branch, and not just to master. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/123> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 10

[cloud] #88: Social Media for Dockerfiles
by Fedora Cloud Trac Tickets 24 Feb '16

24 Feb '16

#88: Social Media for Dockerfiles -----------------------------------+--------------------- Reporter: jzb | Owner: jzb Type: task | Status: new Priority: normal | Milestone: Future Component: Docker Base Container | Keywords: meeting -----------------------------------+--------------------- We need to work with marketing to tweet about things regularly. I'd like to put out regular tweets to promote individual Dockerfiles. Thoughts? -- Ticket URL: <https://fedorahosted.org/cloud/ticket/88> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 7

[cloud] #99: AMI lifetimes (Cloud WG members vote needed)
by Fedora Cloud Trac Tickets 24 Feb '16

24 Feb '16

#99: AMI lifetimes (Cloud WG members vote needed) -------------------------------------+------------------------------------- Reporter: oddshocks | Owner: oddshocks Type: task | Status: new Priority: normal | Milestone: Fedora 22 Component: Infrastructure & | Keywords: aws, images, vote, Release Engineering | policy -------------------------------------+------------------------------------- This ticket is to discuss and vote on appropriate lifetimes for Fedora Cloud AMIs on our official and community cloud accounts, as discussed on the Cloud SIG list this month[1] and in this week's meeting. Everyone seems to agree that after a final release, all TC, RC, Alpha, Beta, and scratch builds should be deleted. This makes sense because there'd be no reason to use any of these AMIs after the final release. Still, we need to definitively decide on: 1. When should TC, RC, Alpha, Beta, and scratch builds be deleted? (1) After a final release? (2) Progressively, when a newer build of the same type comes out? (3) After a set amount of time, depending on the build type? Note that with (2) or (3), we'd need some way to mark each build with it's type. I don't think that necessarily happens now. 2. When should final release AMIs be deleted? (1) After a certain number of newer final releases? (2) After a certain amount of time? (3) Never? Also note that if we choose any age-based deletion policies, we'd need to set up some sort of regular polling of *all* our AMIs on both accounts. We want to hold as few AMIs at one time as is reasonable. There are many AMIs created for each image build that happens, so our AWS storage charges will become quite high if we don't keep our accounts clean. Discuss, and then perhaps a vote? [1]: https://lists.fedoraproject.org/pipermail/cloud/2015-March/005087.html -- Ticket URL: <https://fedorahosted.org/cloud/ticket/99> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 18

[cloud] #139: Producing 2 week atomic images
by Fedora Cloud Trac Tickets 23 Feb '16

23 Feb '16

#139: Producing 2 week atomic images -----------------------+--------------------- Reporter: dustymabe | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting -----------------------+--------------------- This is upon us now. Nightly images are here: http://alt.fedoraproject.org/pub/alt/atomic/testing/ This ticket should track any issues/blockers/improvements we need to make to this process. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/139> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 11

[cloud] #135: Fedora 23 Retrospective
by Fedora Cloud Trac Tickets 17 Feb '16

17 Feb '16

#135: Fedora 23 Retrospective --------------------+--------------------- Reporter: jzb | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting --------------------+--------------------- We need to look back on the 23 process and what went right and wrong. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/135> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 5

[cloud] #146: Create and host a Fedora 23 Cloud image supporting all languages
by Fedora Cloud Trac Tickets 10 Feb '16

10 Feb '16

#146: Create and host a Fedora 23 Cloud image supporting all languages ------------------------+-------------------- Reporter: strikerttd | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: ------------------------+-------------------- It would be helpful to have a Fedora 23 Cloud QCOW hosted that supports all languages. This was removed after Fedora 22 Cloud. [12:22] <dgilmore> maxamillion: it was intentionally removed [12:24] <dgilmore> https://git.fedorahosted.org/cgit/spin- kickstarts.git/tree/fedora-cloud-base.ks?h=f23 [12:26] <dgilmore> striker: echo '%_install_langs C:en:en_US:en_US.UTF-8' >> /etc/rpm/macros.image-language-conf -- Ticket URL: <https://fedorahosted.org/cloud/ticket/146> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 4

Fedora Cloud box idea
by Zoltan Hoppar 03 Feb '16

03 Feb '16

Hi I would like to build an small, and cheap cloud solution that maybe can be our next solution for media distribution. As a POC, I would like to know what kind of cheap ARM board has enough horsepower to provide access to our images (eg. remote tftp server, info site, and more), and can work as our infotaintment server at events if someone joining to this openly accessible box at events. Thanks, Zoltan -- PGP: 06853DF7

3 3

Fedora Atomic Host Two Week Release Announcement
by noreply＠fedoraproject.org 29 Jan '16

29 Jan '16

A new update of Fedora Cloud Atomic Host has been released and can be downloaded at: Images can be found here: https://getfedora.org/en/cloud/download/atomic.html Respective signed CHECKSUM files can be found here: https://alt.fedoraproject.org/pub/alt/atomic/stable/Cloud-Images/x86_64/Ima… https://alt.fedoraproject.org/pub/alt/atomic/stable/Cloud_Atomic/x86_64/iso… Thank you, Fedora Release Engineering

5 8

Regrets for today's meeting
by Joe Brockmeier 27 Jan '16

27 Jan '16

Apologies - I am going to be in a metal tube all day and won't be able to make the meeting. -- Joe Brockmeier | Community Team, OSAS jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

Announcement: Fedora Atomic Two-Week Release Delayed
by Adam Miller 26 Jan '16

26 Jan '16

Hello all, There are currently issues from the Rel-Eng side of the Two-Week Release. The composes of the Atomic Nightly are broken at the moment, the builds and automated testing are succeeding but the component of the compose tools that are used to bring all the content back together in a meaningful and predicable way are currently broken (the irony of which is not lost on us). We hope to get things rolling and get a release out tomorrow. On behalf of the Fedora Release Engineering team, I would like to thank everyone for their patience as we work through this and apologize for any inconvenience the delay might have caused. Thank you, -AdamM

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud January 2016