Agenda for Server WG Meeting (2014-09-23)
by Stephen Gallagher
Sorry, I forgot to send out a call for agenda items. We have at least one thing to talk about this week: Fedora 21 Beta milestones. What do we need to do and how do we get there.
Please submit other agenda items as you see fit.
9 years, 7 months
Fedora 21 Alpha RC testing request
by Adam Williamson
Hi, folks!
In case anyone didn't see it elsewhere, we put 21 Alpha RC1 out for
testing today. It still has some kinks, but we really need to make sure
we have a reasonably complete test run on it and catch any remaining
blockers. If folks could help test particularly in their own areas of
interest, that'd be great.
The images can be found at
https://dl.fedoraproject.org/pub/alt/stage/21_Alpha_RC1/ - it's a fairly
big tree and the folder layout is still a bit of a work-in-progress,
sorry if you have to click around until you find something.
The test pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Install
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Server
to test, basically, pick a test case from (one of) the table(s), run it,
and edit your result into the appropriate table cell using the
{{result}} macro - short version, {{result|pass|adamwill}} is a pass,
{{result|warn|adamwill|123456}} is a warning (aka the compromise between
'pass' and 'fail' - use it for things that aren't exactly critical fails
but are worth noting), and {{result|fail|adamwill|654321}} is a failure.
The number should be a Bugzilla bug #.
Please file bugs for failures; if the bug's serious, propose it as a
release blocker by setting it to block the bug 'AlphaBlocker' or using
the blocker bug webapp at
https://qa.fedoraproject.org/blockerbugs/propose_bug . Each test case
has a link to the release criteria that it enforces at the top - you can
refer to this in proposing the blocker. But please err on the side of
nominating bugs as blockers, we'd rather have a few to reject than miss
one we should have blocked for. Rejections do not go on your permanent
record :)
The test cases have milestones listed alongside them in the tables. Do
the tests marked 'Alpha' first, then the ones marked 'Beta', then the
ones marked 'Final', and the ones with no milestone come last (these are
optional tests that aren't usually expected to encounter release
blocking issues).
Later composes may follow - please do help test those too. We need to
run all the Alpha tests against at least one of the release composes
(ideally we'd run them all against all the RCs).
Thanks a lot folks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years, 7 months
Weekly Meeting Cancelled - Cockpit Test Day
by Stephen Gallagher
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There's nothing on the agenda for this week. The time would be better
spent participating in the Cockpit Test Day instead.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlQYT0gACgkQeiVVYja6o6Pm9gCdEsnWECdDtxCiLyaPU86oOa7K
ie4An3x/nnZ1CN9BHMvSBpsCZgfpGk8J
=xsnm
-----END PGP SIGNATURE-----
9 years, 7 months
Alpha release notes
by Simo Sorce
On today's WG meeting we agree to send an additional paragraph to add to
the alpha[1] notes.
Here's a first crack at it.
---------------------------------8<--------------------------------------
Fedora Server Management Features
=================================
The Fedora Server product introduces new Server management features
aimed at making it easier to install discrete infrastructure services.
The Fedora Server WG will introduce two new technologies in Fedora to
handle this task, rolekit and cockpit.
Rolekit is a Role deployment and management toolkit that provides a
consistent interface to administrators to install and configure all
the packages needed to implement a specific server role.
Cockpit ... <stefw to contribute text here>
---------------------------------8<--------------------------------------
HTH,
Simo
[1]
https://fedoraproject.org/wiki/F21_Alpha_release_announcement#Fedora_21_S...
--
Simo Sorce * Red Hat, Inc * New York
9 years, 7 months
rolekit: Status update
by Thomas Woerner
Hello,
here is a status update for rolekit.
Open for F21 beta:
- Package and group installation using yum or dnf
(PackageKit does not have support for groups anymore for F>20)
- Systemd targets
- documentation
- home page
- man pages
- rolectl
- roled
- rolekit.dbus
- rolekit.roles
- role API
- description
- user parameters
- rolekit
- translations (zalada or transifex ?)
- status update for automatic wakeup (might only be solvable in roles)
Patches on review:
- property verification
- firewall handling (installFirewall, updateFirewall, uninstallFirewall)
- Support for rolectl deploy --settings-file and drop of --set x=y (also
for redeploy)
Deferred to F>21:
- redeploy
- role update handling
If the list is not complete or wrong, please let me know.
Regards,
Thomas
9 years, 7 months
Server Product media for Ambassador work
by Truong Anh Tuan
Hi friends,
F21 is coming.
As usual, Ambassadors will organize release parties and other events and
activities and they will distribute media there.
As we discussed in Technical Specs [1], Install media for Server would
be Netinst and Local one.
I think people will prefer the local one to distribute in such events
and it is for Server product only, not mixed to any others (Workstation,
etc.)
Workstation user range is wider, of course but it is worth to distribute
Server media in such those events (maybe lesser), I think.
Any ideas and comments?
Kind regards,
Tuan
[1] https://fedoraproject.org/wiki/Server/Technical_Specification#Supported_A...
9 years, 7 months
rolekit D-Bus API
by Thomas Woerner
rolekit D-Bus API
=================
org.fedoraproject.rolekit1
--------------------------
Properties
version:i # server role manager version
roles:ao # role objects list
Methods
getNamedRole(name:s)→o # get role by name
getRolesByState(state:i)→ao # get all roles with the given state
org.fedoraproject.rolekit1.roles.$name
--------------------------------------
Properties (general) # role settings
name:s (ro) # role name
version:i (ro) # role implementation version
state:i (ro) # deployed/started/inactive/dead?
packages:as (ro) # package list: packages and @groups
(similar to kickstart)
services:as (ro) # service list: services to be enabled and
started
firewall:a{sas} (ro) # firewall settings: ports and services
dict {
"ports" => array (
portid:s["-"portid:s]"/"protocol:s ),
"services" => array( name:s ),
}
ports are similar to firewalld port
definitions
firewall_zones:as (rw) # firewall zones to apply the firewall
settings to
custom_firewall:b (rw) # custom firewall: firewall settings will
not be applied if set to true
errorlog:s (ro) # errorlog string
#backup_paths:as (ro) # backup paths (files and directories)
# ... # role specific settings
Methods
start() # start the role (startServices,
installFirewall), fails if not deployed
stop() # stop the role (stopServices,
uninstallFirewall), fails if not started
restart() # stop and start
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
updateRole() # update role: yum update; restartServices;
updateFirewall
getFirewallZones() # get firewall zone list from firewalld, add
used ones to firewall_zones
Role States
===========
Nascent 0
Deploying 1
ReadyToStart 2
Starting 3
Running 4
Stopping 5
Decomissioning 6
Error 255
9 years, 7 months
