Role States
by Thomas Woerner
What are the needed and wanted role states?
It was requested to have integer states. A bit field maybe? Questions
and suggestions welcome.
Please add roles with a description:
Role | Description
------------------+----------------------------------------------------------------
enabled | Role will be started automatically at next boot
configured | Configuration has been added
deployed | Role is deployed
activation_failed | Activation (with systemd) failed
|
Do we need failed states like for example activation_failed or
deploy_failed?
Is there a need for time stamps for these states?
9 years, 10 months
Proposal for the Server Role API
by Thomas Woerner
Hello,
here is the proposal for the Server Role API:
* Plugin architecture
* Daemon must exit, when not in use (all D-Bus clients exited)
D-Bus server API:
org.fedoraproject.ServerRoleManager1
------------------------------------
Properties
version:s # server role manager version
state:s # active/inactive/dead?
roles:ao # role objects list
Methods
getRole(role:o)→o # get role by object
getNamedRole(name:s)→o # get role by name
getActiveRoles()→ao # get active role object list
org.fedoraproject.ServerRoleManager1.roles.$n
---------------------------------------------
Properties (general) # role settings
name:s (ro) # role name
version:s (ro) # role version
state:s (ro) # deployed/started/inactive/dead?
activate_time:i (ro) # time of activation
deploy_time:i (ro) # time of deployment
is_configured:b (ro) # is this role configured?
packages:as (ro) # packages and @groups
services:a{sas} (ro) # services to be enabled and/or started:
"enable": [s] and "start": [s]
firewall:a{sas} (ro) # firewall dict ports: [s] and service: [s]
#backup_paths:as # backup files and directories (directory
trailing slash it means "everything below here")
# ... # custom settings, passwords as key value pairs
Methods
deploy() # deploy role (i.e. running initial setup
post-package-install, ipa-server-install)
decommission() # decommision (example: moved to another
machine, ipa-server-install -u ), stop if started
start() # start the role (startServices,
installFirewall), fails if not deployed
stop() # stop the role (stopServices,
uninstallFirewall), fails if not started
updateRole() # update role: yum update; restartServices;
updateFirewall
reconfigureRole(a{sv}) # reconfgure role with new config settings
as key value pairs
installPackages() # install packages and groups
#uninstallPackages() # uninstall packages and groups, fails if
deployed - not initially
startServices() # start the services
restartServices() # restart the services
stopServices() # stop the services
installFirewall() # install firewall ports/services
updateFirewall() # update firewall ports/services
uninstallFirewall() # uninstall firewall ports/services
9 years, 10 months
Server WG Meeting Minutes (2014-06-03)
by Stephen Gallagher
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===================================================================
#fedora-meeting-1: Server Working Group Weekly Meeting (2014-06-03)
===================================================================
Meeting started by sgallagh at 15:00:58 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2014-06-03/fedora-meeti...
.
Meeting summary
- ---------------
* roll call (sgallagh, 15:01:10)
* Agenda (sgallagh, 15:06:16)
* Agenda Topic: Branding and Design (sgallagh, 15:06:37)
* Agenda Topic: ARM support (sgallagh, 15:06:46)
* Agenda Topic: Scheduling (sgallagh, 15:07:16)
* Scheduling (sgallagh, 15:09:07)
* AGREED: Request a two-week extension on Alpha Submission Freeze,
noting that this is blocker-criteria functionality (+5, 0, -0)
(sgallagh, 15:25:45)
* Branding and Design (sgallagh, 15:26:00)
* ARM Support (sgallagh, 15:30:24)
* ARM was overlooked when we defined our deliverable media (sgallagh,
15:31:45)
* dgilmore has been working on changes to anaconda and uboot that will
allow us to use installer-based deployment for ARM platforms in
Fedora 21 (adamw, 15:34:07)
* pwhalen has tested this on Wandboard and Cubietruck, but notes
Beaglebones do not have sufficient RAM for installation (adamw,
15:34:46)
* AGREED: Fedora Server will provide support for those 32-bit ARM
architectures that can be installed using anaconda. (sgallagh,
15:44:47)
* The ARM SIG is perfectly welcome to produce image-based Spins that
aren't part of our blocking media set (sgallagh, 15:44:59)
* ACTION: sgallagh to update the PRD and Technical Specification
(sgallagh, 15:45:21)
* Open Floor (sgallagh, 15:46:00)
Meeting ended at 15:58:53 UTC.
Action Items
- ------------
* sgallagh to update the PRD and Technical Specification
Action Items, by person
- -----------------------
* sgallagh
* sgallagh to update the PRD and Technical Specification
* **UNASSIGNED**
* (none)
People Present (lines said)
- ---------------------------
* sgallagh (72)
* adamw (28)
* simo (26)
* twoerner (16)
* mizmo (14)
* nirik (9)
* danofsatx-work (7)
* mitr (7)
* tuanta (6)
* zodbot (5)
* stefw (0)
* davidstrauss (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlON8UEACgkQeiVVYja6o6M74wCgmQEOMsCzgJf4whSKH+cnBzxN
7zMAoKqBys16VP6bFhvlRy/Wn4WjteS+
=CqrX
-----END PGP SIGNATURE-----
9 years, 10 months
Fedora Server and Docker
by Stephen Gallagher
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've been playing with Docker quite a bit lately, particularly the
Fedora Dockerfiles[1] to see what might be useful for the Fedora Server.
For one thing, it occurs to me that we may want to have a strategy for
using Docker images in the Fedora Server for any Roles that can
support it[2].
Advantages:
* Deployment can be scripted as dockerfiles instead of full packages
* The same Docker image is guaranteed(?) to be loadable by the next
version of Fedora, making distro-upgrades safer.
* Role upgrades can be handled by starting up a new Docker image with
the updated software and then migrating data between them.
* With Docker and SElinux, our Roles can be isolated from the host
server. (And potentially migrated to a Fedora Cloud system later).
I've specifically been playing around with using Docker images of
PostgreSQL (our planned Database Server Role for Fedora 21) and have
found that the Fedora Dockerfile is extremely easy to build and get
running.
I think that it would be to our advantage to tend towards using Docker
images as the implementation for the Database Server Role as well as
the proposed memcached role and potentially others, such as the
fileserver or iSCSI target roles.
This *would* imply adding the docker-io package as part of the
standard installation of the Fedora Server.
Thoughts?
[1] https://github.com/fedora-cloud/Fedora-Dockerfiles\
[2] FreeIPA, our choice of Domain Controller, is not currently
supported under Docker, though upstream has a working
proof-of-concept. This we can revisit down the road.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlOMaBAACgkQeiVVYja6o6N2ywCgnh5SL1dVLzPIVb9L0bO5FKH6
Ac0An1uBkaJhcSzyW5QSSQ3UoGXBCl8W
=SHJe
-----END PGP SIGNATURE-----
9 years, 10 months
Soliciting agenda items for 2014-06-03 meeting
by Stephen Gallagher
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
What shall we put on the agenda this week? We didn't get to the
branding discussion last week, so we should probably include that.
ARM support for Fedora Server?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlOIohoACgkQeiVVYja6o6MX1wCfbWEHWuy8QOM+tBBHt33cnbMw
7m4An3bH4f/F56+e49F+E/Zbnawx+qFz
=gVkI
-----END PGP SIGNATURE-----
9 years, 10 months