#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 dustymabe):
Replying to [comment:10 walters]:
You mentioned some of these points needed to be replied to.. I'll give it
a stab.
> The thing, the whole point of this effort is to containerize. Anyone
who wants the traditional "one set of packages" model has plenty of other
options *within Fedora*, such as Fedora Server and Fedora Cloud Base.
>
> There's also the aspect that even if we add cockpit into the tree in an
update, anyone who does an initial install won't get it, so there will
still be issues with that.
We are planning to release updated images. Does that change your opinion?
>
> Finally, while Fedora 21 shipped with it enabled by default, I'm a bit
hesistant to ship a new service that listens on the network by default in
an update to Fedora 22. It's very reasonable for organizations to
evaluate a "gold" OS configuration, perform some customization including
turning on/off services, setting up firewalling etc. These types of
deployments would be unhappy to have new services appear.
If we don't want it to listen on the network by default and we are
delivering as a container then should we just not include it at all?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/105#comment:16>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
