cloud June 2016

cloud@lists.stg.fedoraproject.org

26 participants
96 discussions

[cloud] #143: Proposals for F24 features
by Fedora Cloud Trac Tickets 13 Jul '16

13 Jul '16

#143: Proposals for F24 features --------------------+--------------------- Reporter: kushal | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting --------------------+--------------------- We need the proposals in for Fedora 24 release -- Ticket URL: <https://fedorahosted.org/cloud/ticket/143> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 9

Canceling today's Cloud WG meeting
by Kushal Das 29 Jun '16

29 Jun '16

Hi all, Many of our regular attendees are in RH Summit this week. I think it will be wise to cancel today's Cloud WG meeting, we will meet again next week. Mean while if you want to discuss something, feel free to start a new thread in the list. Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org

1 0

Atomic CLI in FAH is old
by Josh Berkus 28 Jun '16

28 Jun '16

... 1.8 instead of 1.10. Any particular reason, or just round TUITs? -- -- Josh Berkus Project Atomic Red Hat OSAS

2 2

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 27 Jun '16

27 Jun '16

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2016-06-29 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar/meeting/1999/

1 0

No Fedora 24 container?
by Josh Berkus 23 Jun '16

23 Jun '16

https://hub.docker.com/_/fedora/ This seems like a big loss, especially for getting folks to test Fedora 24. -- -- Josh Berkus Project Atomic Red Hat OSAS

7 12

Fedora 24 Based Two-Week Atomic Release Delayed - Feedback Requested
by Adam Miller 22 Jun '16

22 Jun '16

Hello all, The original schedule for today's Fedora Two-Week Atomic Release was going to include a cut-over of our back end Release Infrastructure and AutoCloud automated QA environment to be compose based (one of the building blocks we need in place to make the future of the release process more flexible). However, because of the most recent Fedora 24 release slip this has caused a conflict of schedules (a schedule that was agreed upon at the Cloud FAD a few weeks ago) and as a side effect of the Fedora 24 GA event we are currently in a Fedora Infrastructure Freeze. During this Freeze, we can not make the back end changes needed to cut over to the new versions of the RelEng Composer and AutoCloud which are currently hosting the Fedora 24 Atomic Images. This is something that slipped through the cracks and ultimately lands on me, and for that I would like to apologize to members of Project Atomic, Fedora Cloud WG, and both project communities at large. That being said, we have a couple of options on how to handle this and I would like to request feedback from others. We can slip the Fedora 24 Based Two-Week Atomic Release by 1 week just as the Fedora 24 GA Release was slipped and target next Tuesday (2016-06-21). This would "reset the clock" on the Two Week Releases and we will then have a Two-Week Release every two weeks following that one. Or We can skip this Two-Week Atomic Release all together and target the next Two-Week Atomic Release scheduled date of Tuesday 2016-07-05. Or We can release a Fedora 23 Based Two-Week Atomic image today (or tomorrow, pending how fast feedback rolls in) and target the next Two-Week Release window as the time to cut over to Fedora 24. I'm open to alternate suggestions but do note that aspects of the Two Week release process are limiting at present, which is something this new Infrastructure deployment will be the starting point to resolve, so there may be restrictions on how creative of a solution we can come up with in the near term. Once again, I would like to apologize to all who have been impacted by this and we hope that with the planned changes to the Infrastructure and the Release code will allow for more flexibility in the future. Thank you, -AdamM

5 10

[cloud] #152: Fedora Coud Test Day for F24
by Fedora Cloud Trac Tickets 22 Jun '16

22 Jun '16

#152: Fedora Coud Test Day for F24 -----------------------+--------------------- Reporter: dustymabe | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting -----------------------+--------------------- We need to schedule something for F24 and try to get community involvement. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/152> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 6

[cloud] #161: NTP should be enabled by default on Atomic Host
by Fedora Cloud Trac Tickets 21 Jun '16

21 Jun '16

#161: NTP should be enabled by default on Atomic Host -------------------------------+-------------------- Reporter: jberkus | Owner: Type: defect | Status: new Priority: normal | Milestone: Future Component: Docker Host Image | Keywords: -------------------------------+-------------------- The way it is now: Timesyncd is disabled by default when one deploys atomic host. Without synchronized time, Etcd does not work and you can't build a cluster. The way it should be: timesyncd should be enabled out-of-the-box. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/161> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 3

Fedora 24 Cloud Base Vagrant in Atlas
by Dusty Mabe 21 Jun '16

21 Jun '16

Atlas has been updated for Fedora 24 Cloud Base: https://atlas.hashicorp.com/fedora/boxes/24-cloud-base/versions/20160621 You can now: vagrant init fedora/24-cloud-base && vagrant up

2 1

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 20 Jun '16

20 Jun '16

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2016-06-22 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar/meeting/1999/

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 June 2016