-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/21/2014 01:02 PM, Adam Williamson wrote:
On Fri, 2014-02-21 at 09:34 -0800, Michael R. Davis wrote:
>
> Have any of you tried to install wordpress. It makes me sick
> that they just don't install a default database configuration
> right out of the RPMs.
Think about what we're defining here: a 'database server' role.
The point of having a single database server is that you don't run
a database on every system where you have something installed that
needs a database.
The reason Fedora webapp packages don't deploy or expect a
database running on the same machine is that, frequently, people
don't want that. They want to use a database running on another
machine.
I'd make the strong argument that specific apps like this would be
better served by something like OpenShift cartridges (which can be
configured to use either a local or remote DB server) than as Server
Roles.
Fedora Server having an "OpenShift Node" Server Role is another thing
I want to see us do (essentially having a really easy way to add new
machines to an OpenShift cloud). However, I suspect this will require
significant work and is probably out of scope for our F21 deliverable
(but it's something I'm going to be coordinating with the OpenShift team).
I wonder if our definition of Server Roles was too ambiguous in the
PRD. My view was that it should be a way to set up clear platform
states and certain infrastructure services. I think that deploying
specific "apps" (and I know the term is fuzzy... is FreeIPA an app?)
is not really the purpose of a Role.
So for some off-the-top-of-my-head examples:
Infrastructure: Identity management, database server, OpenShift Node,
OpenStack Node, File Server, Web Server
App: Wordpress, Drupal, SAP
Drupal is a little fuzzy, since it's both an app and something of an
application framework, but I'd elect to punt on that decision for the
indefinite future :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iEYEARECAAYFAlMHlwwACgkQeiVVYja6o6MZUgCeIFyJPSgdzRThmthgmW9cNvdM
XJ4An1Hfr2EZKlpAm5yBww3yDNwYr4pc
=4j8a
-----END PGP SIGNATURE-----