Le 14/11/2013 08:25, Matthias Runge a écrit :
Hey everybody,
during yesterday's cloud WG meeting, the question about interaction and
interference with the server WG came to us.
There are quite a few intersection points, e.g. when thinking about
providing cloud server infrastructure (which probably belongs to server
WG). But when it comes to ssh key injection in the cloud image itself,
we need both WG to collaborate.
Thus, I'd like to ask for opinions: should we (as Cloud WG) take
responsibilities for cloud infrastructure, should we deny that, how do
you differentiate between cloud and server WG?
Matthias
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Hi,
Server WG is managing a hell lot of things:
* web servers
* database servers
* cloud hosting
etc.
My POV is that it's impossible to do everything, the cloud WG should
collaborate with the Server WG on the cloud hosting questions.
Our responsibilities:
* acting as a stakeholder for the cloud questions in the server WG: i
recommend having a representative who'll voice us
* taking server-related tasks: packaging, testing, etc.
* making sure that cloud & server products evolve together is in sane way.
Active collaboration between our two WG is the only way to make Fedora
the best platform for cloud computing.
If i had to give one reason: the Fedora Cloud product *must* be runnable
on top of the Fedora Server product. Fedora has always strived to be
self-sufficient, there's no reason to change that. Neglecting the
hosting side would be "un-fedora".
best regards,
H.
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
