8:17 a.m.
On 06/06/2016 12:28 PM, Kevin Fenzi wrote:
Anyone have any meeting agenda items for tomorrows meeting?
I have one item. I'm planning to spend some time this afternoon at the Fedora
Cloud FAD and I wanted to consider pitching a joint effort and change of
direction for the Server SIG there, but I'd like to bounce it off of the Server
WG beforehand.
tl;dr version: What if we retool Fedora Server going forward as a standalone
OpenShift environment and focus the Server and Cloud SIGs to work together on
building server roles as OpenShift applications (aka Kubernetes pods).
The idea would be to have a strategy wherein we provide simple tooling (possibly
just repurposing the 'rolectl' tool) to set up the server roles using OpenShift
under the hood. The long-term strategy would be to develop mechanisms by which
someone could start out with a Server providing some functions and then
eventually migrate to an Atomic cluster, ideally without significant effort.
This would serve to bring the two SIGs closer together, reduce the amount of
independent work being done and more closely align with the public efforts being
done by Project Atomic, Red Hat and CentOS.
2:02 p.m.
The idea would be to have a strategy wherein we provide simple tooling
(possibly just repurposing the 'rolectl' tool) to set up the server roles
using OpenShift under the hood.
In most shops deployment of server roles is typically done with something
like Ansible, Chef or Puppet and these are pretty much the standard three.
Ansible is python based which makes it a good candidate for integration
with rolekit. It would interesting if an admin could define roles in a role
based Ansible playbook and then rolectl/rolekit could manage the deployment
either locally or remotely. The user could also deploy each role to it's
own container and configure how they're linked together. This would
probably involve writing some custom Ansible modules for rolekit.
Essentially rolectly/rolekit becomes a management layer integrated with
Ansible that allows playbook defined roles to be deployed locally/remotely
as OpenShift apps.
Let me know if this is technically sound as I'm not that familiar with
OpenShift.
On Tue, Jun 7, 2016 at 9:17 AM, Stephen Gallagher <sgallagh(a)redhat.com>
wrote:
On 06/06/2016 12:28 PM, Kevin Fenzi wrote:
> Anyone have any meeting agenda items for tomorrows meeting?
I have one item. I'm planning to spend some time this afternoon at the
Fedora
Cloud FAD and I wanted to consider pitching a joint effort and change of
direction for the Server SIG there, but I'd like to bounce it off of the
Server
WG beforehand.
tl;dr version: What if we retool Fedora Server going forward as a
standalone
OpenShift environment and focus the Server and Cloud SIGs to work together
on
building server roles as OpenShift applications (aka Kubernetes pods).
The idea would be to have a strategy wherein we provide simple tooling
(possibly
just repurposing the 'rolectl' tool) to set up the server roles using
OpenShift
under the hood. The long-term strategy would be to develop mechanisms by
which
someone could start out with a Server providing some functions and then
eventually migrate to an Atomic cluster, ideally without significant
effort.
This would serve to bring the two SIGs closer together, reduce the amount
of
independent work being done and more closely align with the public efforts
being
done by Project Atomic, Red Hat and CentOS.
_______________________________________________
server mailing list
server(a)lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/server@lists.fedoraproject.org
2859
days inactive
2874
days old
server@lists.fedoraproject.org
2 comments
3 participants
participants (3)
-
Alex G.S. -
Kevin Fenzi -
Stephen Gallagher