-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/15/2013 08:17 PM, Miloslav Trmač wrote:
(Or, Stephen, to more directly address your post: In any case we
need a configuration API, and software that implements requests by
that API. Whether that API is working with pets or livestock is
not that important in its design; if having that API shared between
Server and Cloud required some changes to how we treat server roles
on an already installed machine, that would probably be well worth
it.)
For the record, this was pretty much the implication I was trying to
make with my original post: that if we build up this API, we should be
able to solve both cases together. We just need to make sure that it's
possible to invoke this API during kickstart (possibly in %post) and
also remotely from a management server.
My view here is that I would like us to be able to handle all of the
following use-cases:
1) A new physical machine is installed in the datacenter. It is
possible to ship this machine preinstalled with Fedora Server (either
from a hardware vendor or central provisioning office of a company)
with no roles preassigned. It should be possible to provision the
machine from a management console to have at least one primary server
role. (This role might be "VM hypervisor" or the LXC equivalent).
2) A new VM is booted from a pristine qcow image of Fedora Server,
with no roles preassigned. As with 1), it must be possible to add at
least one role to this virtual server.
3) A new VM is booted from a preconfigured qcow image of Fedora Server
providing one or more pre-installed roles. At first boot, we will need
a mechanism to apply the site-specific configuration to these roles to
make them useful.
4) A new physical or virtual machine is being provisioned via system
installer (i.e. anaconda). It must be possible to select zero or more
roles in either the kickstart or the interactive user interface. When
the installation concludes, the system must have been provisioned with
that role, fully configured.
Optional, but highly valuable:
5) It should be possible to apply additional roles to a system after
initial deployment, without requiring a complete reinstallation of the
machine. (Example: Adding a groupware server to the domain controller
in a small environment). The low-level implementation is left
intentionally ambiguous; perhaps initially we can do this on the
physical hardware and as LXC becomes more mature, move to clearer
isolation.
- From my perspective, if we build this as a public API (rather than
tying ourselves too closely to the traditional view of Comps groups),
we will be able to address all of these approaches in the same way.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iEYEARECAAYFAlKKGfUACgkQeiVVYja6o6PbNgCfbxwFS+n3Dse/VPo6m8b0F2hV
Mm8AoKmXzjwoAR68VkkF23pn/PkDXCGz
=cVBT
-----END PGP SIGNATURE-----