Just wanted to see if anyone has made any lead way with supporting
CentOS/RHEL 6.7 via a bridge / agent so these os releases can be brought
into cockpit for resource / servcice monitoring
I know about 8 or 9 months ago this was talked about but not sure if anyone
has taken it upon themselves to come up with a solution yet or if there is
one in the works.
Let me know as we still have a few hundred 6.7 clients hosted in our cloud
and it will take a very long time to safely migrate them if even possible
to a 7.x release.
Donald R. D'Avanzo Jr
*Chief Technology OfficerRed Rock Tech LLC. / Sin City Cloud*
*Office:* (702) 660-1500 | *Direct:* (702) 302-9432
*9205 West Russell Road,Suite 240 | **Las Vegas, Nevada 89148*
Is there a read-only mode with the Cockpit interface to allow system details to be gathered, but not altered?
Our use for Cockpit would like to see a read-only mode and perhaps a couple of different read/write mode access levels (middleware team can only restart httpd & JBoss etc). I'm looking at this from the perspective of seeing the Foreman-cockpit plugin this week. This plugin seems to provide unfettered access for any Foreman user. Is this where "Deep Integration" will come in?
Also wondering if it's possible to write bespoke modules for Cockpit to allow us to report our specific application stats back via the Cockpit service. The docs explain how to embed cockpit and use cockpit components, but not how to integrate our own modules into cockpit (to my non-developer eyes).
The Royal Bank of Scotland plc. Registered in Scotland No 90312.
Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB.
Authorised by the Prudential Regulation Authority and regulated
by the Financial Conduct Authority and Prudential Regulation Authority.
The Royal Bank of Scotland N.V. is authorised and regulated by the
De Nederlandsche Bank and has its seat at Amsterdam, the
Netherlands, and is registered in the Commercial Register under
number 33002587. Registered Office: Gustav Mahlerlaan 350,
Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and
The Royal Bank of Scotland plc are authorised to act as agent for each
other in certain jurisdictions.
This e-mail message is confidential and for use by the addressee only.
If the message is received by anyone other than the addressee, please
return the message to the sender by replying to it and then delete the
message from your computer. Internet e-mails are not necessarily
secure. The Royal Bank of Scotland plc and The Royal Bank of Scotland
N.V. including its affiliates ("RBS group") does not accept responsibility
for changes made to this message after it was sent. For the protection
of RBS group and its clients and customers, and in compliance with
regulatory requirements, the contents of both incoming and outgoing
e-mail communications, which could include proprietary information and
Non-Public Personal Information, may be read by authorised persons
within RBS group other than the intended recipient(s).
Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the onward
transmission, opening or use of this message and any attachments will
not adversely affect its systems or data. No responsibility is accepted
by the RBS group in this regard and the recipient should carry out such
virus and other checks as it considers appropriate.
Visit our website at www.rbs.com
In Cockpit we run thousands of integration tests per day against pull
requests and git master. Each test brings up up Cockpit in a full
operating system VM, and hammers on it in some way. Without these tests
it's impossible to validate that Cockpit works.
Last week, the server doing this testing work broke down.
We've been working over the last week to fix that. But we've done more,
instead of just putting this on another server, we've worked to make
these integration tests run in a distributed manner.
As a developer using the new distributed tests is a bit different, and
the documentation has been updated:
Other Operating Systems
Previously we were limited to running the tests on Fedora 22 and RHEL
7.1 for each pull request. One of the reasons was that the server was
simply maxed out much of the time.
By distributing the integration tests, we can open the floor to testing
on further operating systems, and having multiple cases of the tests
running in parallel for each pull request.
Obviously this is not the only factor in running integration tests
against say Debian ... but it was certainly a big blocker in the past.
If dedicating time toward Cockpit's integration tests running on another
OS is something that interests you, don't hesitate to post here on this
list or in the #cockpit channel on FreeNode.
Meeting started by stefw at 14:10:10 UTC. The full logs are available at
* Agenda (stefw, 14:10:23)
* Server outage of Cockpit infrastructure (stefw, 14:13:27)
* LINK: http://cockpit-project.org/guide/latest/index.html (stefw,
* ACTION: Stef will create an index page (stefw, 14:21:58)
* ACTION: Andreas will update the 'latest version' link (stefw,
* Open Floor (stefw, 14:23:07)
Meeting ended at 14:26:59 UTC.
* Stef will create an index page
* Andreas will update the 'latest version' link
Action Items, by person
* Stef will create an index page
* Andreas will update the 'latest version' link
People Present (lines said)
* stefw (39)
* andreasn (9)
* petervo (5)
* zodbot (3)
* github (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
The step described here (http://cockpit-project.org/guide/latest/sso.html)
are exactly the steps I do to configure FreeIPA to SSO with kerberos.
If I create a kerberos ticket with "kinit admin", when I go to
http://ipasrv/ipa/ui with firefox from my desktop (ipa client), I am logged
in without username/password.
But when I go to http://ipasrv:9090 with firefox (cockpit is installed on
the ipa server), cockpit asks me for a username and password.
And I log in as root.
On the ipa server, I can run
$ getent passwd smith(a)example.com
$ host -t SRV _kerberos._udp.example.com_kerberos._udp.example.com has SRV record 0 100 88 zaira.example.com.
On my desktop, firefox is configured like this:
network.negotiate-auth.trusted-uris user set string .example.com
So I must be missing something.
I installed cockpit 0.67-2.fc22 on an ipa server and added several servers
from the dahsboard as you can see here: http://i.imgur.com/vca19wS.png
But there is one server that keeps annoying me (as you can see here:
It says "Cannot forward login credentials".
I checked in /var/log/messages and found this:
Oct 22 10:10:02 zaira2 cockpit-ws: adina.xxx: ssh-ed25519 host key for
server is not known: 8f:55:e3:ee:90:f3:30:11:43:3b:99:97:c5:9c:8a:0f
but then I found the same message for all the other servers I succeeded to
add to the dashboard:
Oct 22 09:47:51 zaira2 cockpit-ws: zaira.xxx: ssh-ed25519 host key for
server is not known: f5:d7:67:d1:7b:db:d3:b0:54:4d:b7:0e:b9:38:da:a7
Oct 22 09:48:54 zaira2 cockpit-ws: arabella.xxx: ssh-ed25519 host key for
server is not known: 23:09:0b:c3:b1:1c:c4:2d:fc:37:fc:45:f3:27:91:53
Oct 22 09:56:04 zaira2 cockpit-ws: salome.xxx: ssh-ed25519 host key for
server is not known: 61:70:b2:cf:7d:a5:b9:27:40:68:3b:57:4f:ab:40:48
Oct 22 09:58:28 zaira2 cockpit-ws: nabucco.xxx: ssh-ed25519 host key for
server is not known: 57:b0:f0:6c:f3:4d:f9:b3:55:81:08:60:e5:81:a0:23
Oct 22 10:07:11 zaira2 cockpit-ws: rigoletto.xxx: ssh-ed25519 host key for
server is not known: 36:0e:80:79:fd:ec:e5:47:c3:e4:d1:de:86:27:9b:b1
What can be wrong with server adina?
I installed cockpit on my server and I could log in as root. But then I
installed freeipa-server on my server and configured firefox to log in the
ipa web ui using kerberos.
Now when I want to login to the web ui of cockpit on port 9090, I get this
No field to enter username and password. It's probably due to the kerberos
config for ipa.
Any idea how I can configure cockpit/firefox to connect again to the
cockpit web ui?