11:23 a.m.
#102: Considering a host UID/GID upgrade discontinuity
-------------------------------+-----------------------
Reporter: jzb | Owner: jzb
Type: enhancement | Status: new
Priority: normal | Milestone: Fedora 22
Component: Docker Host Image | Keywords: meeting
-------------------------------+-----------------------
See Colin's email here:
https://lists.projectatomic.io/projectatomic-archives/atomic-
devel/2015-April/msg00081.html
We should discuss this week.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/102>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
8:28 a.m.
#102: Considering a host UID/GID upgrade discontinuity
-------------------------------+------------------------
Reporter: jzb | Owner: jzb
Type: enhancement | Status: new
Priority: normal | Milestone: Fedora 22
Component: Docker Host Image | Resolution:
Keywords: meeting |
-------------------------------+------------------------
Comment (by walters):
So...can we make a decision on this today? How should we do that? Have
the current WG members vote?
https://fedoraproject.org/wiki/Cloud/Governance
Executive summary here:
- Break easy rebasing from F21 -> F22, gain rebasing from Fedora <->
CentOS <-> RHEL forever
- Support rebasing from F21 -> F<N> forever
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/102#comment:1>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
8:39 a.m.
#102: Considering a host UID/GID upgrade discontinuity
-------------------------------+------------------------
Reporter: jzb | Owner: jzb
Type: enhancement | Status: new
Priority: normal | Milestone: Fedora 22
Component: Docker Host Image | Resolution:
Keywords: meeting |
-------------------------------+------------------------
Comment (by mattdm):
Forever is a long time. :)
Yes, having a WG vote is the way to go. (FWIW, as a non-voting member, I
think it makes sense.)
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/102#comment:2>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
9:29 a.m.
#102: Considering a host UID/GID upgrade discontinuity
-------------------------------+------------------------
Reporter: jzb | Owner: jzb
Type: enhancement | Status: new
Priority: normal | Milestone: Fedora 22
Component: Docker Host Image | Resolution:
Keywords: meeting |
-------------------------------+------------------------
Comment (by jzb):
Typically we look for lazy consensus over at least 72 hours. Since we
don't have that time to make a decision in this case, if we can get a
quorum vote in favor (or I guess, against) then we have a decision.
I'm a little nervous about this given that if it breaks anything, we may
well not have an Atomic release for F22. However, I believe Colin is
saying this is unlikely to break the compose and if he's confident... then
I will +1.
So - +1.
Others?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/102#comment:3>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
10:09 a.m.
#102: Considering a host UID/GID upgrade discontinuity
-------------------------------+------------------------
Reporter: jzb | Owner: jzb
Type: enhancement | Status: new
Priority: normal | Milestone: Fedora 22
Component: Docker Host Image | Resolution:
Keywords: meeting |
-------------------------------+------------------------
Comment (by dustymabe):
I think there were concerns voiced in the meeting this past week. We had
discussed waiting to make this change when we moved to Atomic as a spin,
but we also discussed the possibility that the adoption of F21 atomic may
be low enough to diminish worrying too much about breakages.
I'm +1 for the change but I do encourage us to think about the change and
the community. We wouldn't really be giving too much warning to people.
Dusty
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/102#comment:4>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
2:21 p.m.
#102: Considering a host UID/GID upgrade discontinuity
-------------------------------+------------------------
Reporter: jzb | Owner: jzb
Type: enhancement | Status: new
Priority: normal | Milestone: Fedora 22
Component: Docker Host Image | Resolution:
Keywords: meeting |
-------------------------------+------------------------
Comment (by ausil):
normally we say you can update from alpha on up. as i understand it this
would break that. I am not advocating any option, just pointing out
something to consider
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/102#comment:5>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
2:51 p.m.
#102: Considering a host UID/GID upgrade discontinuity
-------------------------------+------------------------
Reporter: jzb | Owner: jzb
Type: enhancement | Status: new
Priority: normal | Milestone: Fedora 22
Component: Docker Host Image | Resolution:
Keywords: meeting |
-------------------------------+------------------------
Comment (by jzb):
Dusty - I agree, but this is an anomaly, we have so much churn in the
featured software (Docker, Kubernetes, etc.) that the users should
understand that there's going to be some bumps in the road. If this was a
more mature set of tools, I'd argue against this - but in this case I
think we need to err on the side of progress. Especially since it's not a
question of "if" we're going to break things but "when" --
let's do it
quickly.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/102#comment:6>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
8:50 p.m.
#102: Considering a host UID/GID upgrade discontinuity
-------------------------------+------------------------
Reporter: jzb | Owner: jzb
Type: enhancement | Status: new
Priority: normal | Milestone: Fedora 22
Component: Docker Host Image | Resolution:
Keywords: meeting |
-------------------------------+------------------------
Comment (by dustymabe):
Replying to [comment:6 jzb]:
Dusty - I agree, but this is an anomaly, we have so much churn in the
featured software (Docker, Kubernetes, etc.) that the users should
understand that there's going to be some bumps in the road. If this was a
more mature set of tools, I'd argue against this - but in this case I
think we need to err on the side of progress. Especially since it's not a
question of "if" we're going to break things but "when" --
let's do it
quickly.
Agreed. +1
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/102#comment:7>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
9:51 p.m.
#102: Considering a host UID/GID upgrade discontinuity
-------------------------------+------------------------
Reporter: jzb | Owner: jzb
Type: enhancement | Status: new
Priority: normal | Milestone: Fedora 22
Component: Docker Host Image | Resolution:
Keywords: meeting |
-------------------------------+------------------------
Comment (by miabbott):
Replying to [comment:6 jzb]:
Dusty - I agree, but this is an anomaly, we have so much churn in the
featured software (Docker, Kubernetes, etc.) that the users should
understand that there's going to be some bumps in the road. If this was a
more mature set of tools, I'd argue against this - but in this case I
think we need to err on the side of progress. Especially since it's not a
question of "if" we're going to break things but "when" --
let's do it
quickly.
I have no voting rights here, but I'm in favor of breaking things now and
feeling the pain, rather than waiting for the next release.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/102#comment:8>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
10:21 a.m.
#102: Considering a host UID/GID upgrade discontinuity
-------------------------------+------------------------
Reporter: jzb | Owner: jzb
Type: enhancement | Status: new
Priority: normal | Milestone: Fedora 22
Component: Docker Host Image | Resolution:
Keywords: meeting |
-------------------------------+------------------------
Comment (by walters):
Pushed. It'd be great if people beyond me could give the result some
testing tomorrow/Monday.
I tested by rebasing between a tree generated by
https://github.com/CentOS/sig-atomic-buildscripts/tree/downstream
and one generated by this commit.
To make this easier to test, we need CentOS downstream rebuild of the ISO
and cloud images published, and a publicly available Fedora tree with this
commit. Both are in progress.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/102#comment:9>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
10:21 a.m.
#102: Considering a host UID/GID upgrade discontinuity
-------------------------------+------------------------
Reporter: jzb | Owner: jzb
Type: enhancement | Status: closed
Priority: normal | Milestone: Fedora 22
Component: Docker Host Image | Resolution: fixed
Keywords: meeting |
-------------------------------+------------------------
Changes (by walters):
* status: new => closed
* resolution: => fixed
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/102#comment:10>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
3275
days inactive
3280
days old
10 comments
1 participants
participants (1)
-
Fedora Cloud Trac Tickets