Weekly meeting
by Marius Vollmer
========================
#cockpit: weekly meeting
========================
Meeting started by mvollmer at 13:06:30 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/cockpit/2017-03-27/weekly_meeting.2017-...
.
Meeting summary
---------------
* Agenda (mvollmer, 13:08:19)
* testing on different architectures (mvollmer, 13:11:06)
* Open floor (mvollmer, 13:26:34)
Meeting ended at 13:30:44 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* pitti (33)
* mvollmer (30)
* dperpeet (9)
* zodbot (6)
* jscotka (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
6 years, 8 months
Cockpit weekly meeting 2017-03-20
by Andreas Nilsson
===========================================
#cockpit: Weekly Cockpit meeting 2017-03-20
===========================================
Meeting started by andreasn at 14:02:29 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/cockpit/2017-03-20/weekly_cockpit_meeti...
.
Meeting summary
---------------
* Agenda (andreasn, 14:04:22)
* Staging the verify container as a way to simply run the tests
(andreasn, 14:07:54)
* Open Floor (andreasn, 14:19:14)
Meeting ended at 14:21:01 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* stefw (32)
* andreasn (12)
* github (8)
* zodbot (7)
* petervo (4)
* dperpeet (2)
* garrett (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
6 years, 8 months
Weekly meeting
by Marius Vollmer
=================
#cockpit: meeting
=================
Meeting started by mvollmer at 14:03:12 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/cockpit/2017-03-13/meeting.2017-03-13-1...
.
Meeting summary
---------------
* Agenda (mvollmer, 14:05:48)
* system mgmt roles, ansible, nfs (mvollmer, 14:10:22)
* LINK:
https://raw.githubusercontent.com/cockpit-project/cockpit-design/master/r...
(andreasn, 14:43:53)
* new switcher design (mvollmer, 15:01:42)
* LINK: https://github.com/cockpit-project/cockpit/pull/6082
(dperpeet, 15:02:15)
* translations (mvollmer, 15:04:26)
* LINK: http://cockpit-project.org/blog/cockpit-134.html (dperpeet,
15:05:02)
Meeting ended at 15:07:07 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mvollmer (82)
* sgallagh (58)
* jds2001 (41)
* pitti (32)
* dperpeet (31)
* larsu (16)
* andreasn (15)
* zodbot (11)
* github (1)
* petervo (1)
* stefw (1)
* garrett (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
6 years, 8 months
Continuous delivery of release 132 failed and recovery
by Stef Walter
If you've been following on IRC, you may have noticed that releasing
Cockpit 132 failed yesterday. Here's why, and how it's been solved.
In general we want the entire release process to be completely
automatic, with all failures detected before hand.
Earlier this week I made a pull request that passed integration tests,
but broke the continuous delivery:
https://github.com/cockpit-project/cockpit/pull/5924
The symptom was that certain files we installed in 'make install' when
they shouldn't have been installed there. But the root cause was that we
were building RPMs differently during integration tests, and later
during release:
https://fedorapeople.org/groups/cockpit/logs/release-132/log
To solve this problem I added patches to the release-132 branch to fix
this problem, and then ran the continuous delivery scripts manually from
that branch:
https://github.com/cockpit-project/cockpit/tree/release-132
... in the cockpit/infra-release container ...
$ git fetch origin
$ git checkout release-132
$ RELEASE_SINK= RELEASE_TAG=132 release-runner -v
/usr/local/bin/major-cockpit-release
What this does is use the 132 git tag to create a tarball, and then any
commits after that are included in the SRPM as patches.
So how do we prevent this from happening again?
1. Build RPMs during integration more like release:
https://github.com/cockpit-project/cockpit/pull/5942
2. Cleanup the code related to 'make install' and 'make install-tests'
https://github.com/cockpit-project/cockpit/pull/5941
3. Document how to solve this in the future (this email).
4. I noticed that the release-dsc file does not consider patches the
way that release-srpm does. This needs a fix, any takers?
https://github.com/cockpit-project/cockpituous/blob/master/release/releas...
This wasn't a problem this time around because the patches did
not affect debian builds.
5. Figure out how to test upgrading. Martin Pitt caught it this time,
but it should have failed before going in:
https://github.com/cockpit-project/cockpit/pull/5937
Cheers,
Stef
6 years, 8 months
Cockpit 133
by 'Dominik Perpeet'
http://cockpit-project.org/blog/cockpit-133.html
Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 133.
Remotely managed machines are now configured in /etc/cockpit/machines.d
-----------------------------------------------------------------------
Cockpit plugins, other packages, admins, VM management software, or config management systems like Ansible/puppet/cloud-init might want to pre-configure machines for cockpit. Previously this information was stored in |/var/lib/cockpit/machines.json|, but now that information is stored in individual json files in |/etc/cockpit/machines.d|. Existing |machines.json| files are migrated automatically to the new format. Check out the documentation below for more information on the format and use.
Documentation: http://cockpit-project.org/guide/133/feature-machines.html
Change: https://github.com/cockpit-project/cockpit/pull/5963
Packages can register additional bridges
----------------------------------------
On the server side the |cockpit-bridge| connects to various system APIs. There are additional bridges for specific tasks that the main |cockpit-bridge| cannot handle, such as tasks that should be carried out with privilege escalation. These additional bridges can be registered in the |bridges| section of a package’s |manifest.json |file. Check out the documentation below for more information on the format and use.
Documentation: http://cockpit-project.org/guide/133/packages.html#package-bridges
Change: https://github.com/cockpit-project/cockpit/pull/5683
Split translations into individual packages
-------------------------------------------
Behind the scenes there’s been a lot of work on making translations work more smoothly and future-proof. As part of this the translations have been split into the individual packages, which also means they can be updated per package in the future. Check out the Zanata link below, it’s very easy to contribute translations to Cockpit. At this time our top 3 translations (>90%) are Polish (pl), Ukranian (uk) and Chinese (zh-CN). Every bit of help here is greatly appreciated and a big thank you to our contributors!
Translations: https://fedora.zanata.org/project/view/cockpit?dswid=-8859
Change: https://github.com/cockpit-project/cockpit/pull/5898
Get it
------
You can get Cockpit here:
http://cockpit-project.org/running.html
Cockpit 133 is available in Fedora 25:
https://bodhi.fedoraproject.org/updates/cockpit-133-1.fc25
Or download the tarball here:
https://github.com/cockpit-project/cockpit/releases/tag/133
Thanks,
Dominik
6 years, 9 months