Adding fedora cloud list.
On 08/22/2016 10:13 AM, Colin Walters wrote:
> Hi, I'd like to propose a fairly fundamental rework of Atomic Host. TL;DR:
>
> - Move towards "system containers" (or layered packages) for flannel/etcd
> - Move towards containers (system, or Docker) for kubernetes-master
> - Move towards layered packages for kubernetes-node and storage (ceph/gluster)
>
> In progress PR:
>
> https://github.com/CentOS/sig-atomic-buildscripts/pull/144
>
> There are advantages to this and disadvantages; I think we'll have some
> short term transition pain, but past that short term the advantages
> outweigh the disadvantages a lot.
>
> == Advantage: Version flexibility ==
>
> etcd for should really have its own identity in a clustered environment, and
> not necessarily roll fowards/backwards with the underlying host version. I've
> had users report things like hitting an e.g. Kubernetes or Docker issue and rolling back their
> host, which rolled back etcd as well, but the store isn't forwards-compatible,
> which then breaks. There's also a transition to etcd2 coming, which again
> one should really manage distinct from host upgrades.
>
> Another major example is that while we chose to include Kubernetes in
> the host, it's a fast moving project, and many people want to use a newer
> version, or a different distribution like OpenShift. The version flexibility
> also applies to other components like Ceph/Gluster and flannel.
>
> == Advantage: Size and fit to purpose ==
>
> We included things like the Ceph and GlusterFS drivers in the base
> host, but that was before we had layered packages, and there's
> also continuing progress on containerized drivers. If one is using
> an existing IaaS environment like OpenStack or AWS, many users
> want to reuse Cinder/AWS, rather than maintaining their own storage.
>
> Similarly, while flannel is a good general purpose tool, there are
> lots of alternatives, and some users already have existing SDN solutions.
>
> == Disadvantage: More assembly required ==
>
> This is a superficial disadvantage I think - in practice, since we didn't
> pick a single official installation/upgrade system (like OpenShift has
> openshift-ansible), if you want to run a Kubernetes cluster, you need
> to do a lot of assembly anyways. Adding a bit more to that I suspect
> isn't going to be too bad for most users.
>
> Down the line I'd like to revisit the installation/upgrade story - there's
> work happening upstream in
> https://github.com/kubernetes/contrib/tree/master/ansible
> and I think there's also interest and some work in
> having parts of openshift-ansible be available for baseline Kubernetes
> and accessible on Galaxy etc.
>
> == Disadvantage: Dependency on new tooling ==
>
> Both `rpm-ostree pkg-add` and `atomic install --system` are pretty new.
> They both could use better documentation, more real world testing, and
> in particular haven't gained management tool awareness yet (for example, they need
> better Ansible support).
>
> == Summary ==
>
> If people agree, I'd like to merge the PR pretty soon and do a new CentOS AH Alpha,
> and we can collaborate on updating docs/tools around this. For Fedora...it's
> probably simplest to leave 24 alone and just do 25 for now.
>
> What I'd like to focus on is having AH be more of a good "building block"
> rather than positioning it as a complete solution. We ensure that the base
> Docker/kernel/SELinux/systemd block works together, system management tools
> work, and look at working more in the upstream Kubernetes (and OpenShift)
> communities, particularly around Ansible.
>
==================================
#fedora-meeting-1: fedora_cloud_wg
==================================
Meeting started by sayan at 17:01:40 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-17/fedora_cloud_…
.
Meeting summary
---------------
* Roll Call (sayan, 17:01:48)
* LINK: https://fedoraproject.org/wiki/Cloud/Cloud_PRD (jbrooks,
17:17:22)
* LINK:
https://pagure.io/fork/walters/workstation-ostree-config/branch/f24-continu…
(kushal, 17:21:53)
* ACTION: kushal to start off the atomic workgroup discussion on
mailing list (kushal, 17:28:05)
* Action items from last meeting (sayan, 17:28:42)
* ACTION: rtnpro will add test workflow (and test cases) for testing
fedora-motd on F24 atomic image (sayan, 17:30:12)
* ACTION: kushal to write to infra for permission to update Autocloud
tests while in freeze (sayan, 17:31:38)
* Fedora-Dockerfiles examples for Kubernetes
https://fedorahosted.org/cloud/ticket/125 (sayan, 17:32:04)
* vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
(sayan, 17:34:26)
* Don't overwrite download location for 2 week atomic images
https://fedorahosted.org/cloud/ticket/147 (sayan, 17:35:50)
* design, deploy and document Fedora OpenShift Playground (FOSP)
https://fedorahosted.org/cloud/ticket/153 (sayan, 17:39:27)
* make Fedora Atomic download page clearer
https://fedorahosted.org/cloud/ticket/154 (sayan, 17:42:26)
* Decide on post-GA update cadence for various deliverables
https://fedorahosted.org/cloud/ticket/155 (sayan, 17:44:51)
* Need complete Kickstart docs for Atomic Host
https://fedorahosted.org/cloud/ticket/156 (sayan, 17:50:16)
* Ship fedora-motd in F24 atomic image
https://fedorahosted.org/cloud/ticket/160 (sayan, 17:53:10)
* Decide a process about failed tests for Autocloud
https://fedorahosted.org/cloud/ticket/167 (sayan, 17:54:59)
* Put OpenShift Origin in Container with Fedora Base
https://fedorahosted.org/cloud/ticket/168 (sayan, 17:55:36)
* Open Floor (sayan, 17:56:07)
* LINK: http://fedoracloud.readthedocs.io/en/latest/ (kushal,
17:56:53)
* ACTION: gholms to test updated cloud-init on f24 for f25 (gholms,
17:57:36)
Meeting ended at 18:01:19 UTC.
Action Items
------------
* kushal to start off the atomic workgroup discussion on mailing list
* rtnpro will add test workflow (and test cases) for testing fedora-motd
on F24 atomic image
* kushal to write to infra for permission to update Autocloud tests
while in freeze
* gholms to test updated cloud-init on f24 for f25
Action Items, by person
-----------------------
* gholms
* gholms to test updated cloud-init on f24 for f25
* kushal
* kushal to start off the atomic workgroup discussion on mailing list
* kushal to write to infra for permission to update Autocloud tests
while in freeze
* rtnpro
* rtnpro will add test workflow (and test cases) for testing
fedora-motd on F24 atomic image
People Present (lines said)
---------------------------
* sayan (51)
* kushal (46)
* jberkus (27)
* zodbot (24)
* jbrooks (22)
* maxamillion (22)
* gholms (9)
* x3mboy (9)
* jzb (8)
* vvaldez (5)
* scollier (4)
* dustymabe (4)
* nzwulfin (3)
* rtnpro (3)
* walters (3)
* trishnag (2)
* bowlofeggs (1)
--
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!
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2016-08-17 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/
#151: Need owner to define basic container smoke testing requirements
---------------------+---------------------
Reporter: acarter | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
---------------------+---------------------
The release tooling team will begin shipping layered images officially in
F25. As part of that, we'll be creating an automated release workflow that
includes testing via Taskotron. In order to scope Taskotron requirements,
we need to know the core testing requirements are for basic smoke testing
that will be shared across containers. We need an owner to define those
tests initially. I'd also like to know whether that person would continue
to own them going forward or if ownership would fall to the group or
another individual at that time. This should be done soon so that we can
scope Taskotron work.
Note: Kushal has noted that the owner should be sure to discuss with the
internal Container Certification team
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/151>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2016-08-10 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/
#166: RFE : vagrant user with id=1000
---------------------+--------------------
Reporter: langdon | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
---------------------+--------------------
Gnome default user ID is 1000. Vagrant box uses 1001 for vagrant user.
When NFS mounting, I have to chown from one user to the other. Would be
handy if the vagrant user was also 1000.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/166>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System