With Fedora 21 out of the way, we've merged the first round of work that enables reusable Cockpit javascript components that can be integrated into other web applications.
There is more work to come on this. We're working on refactoring Cockpit into packages internally, to make it more modular, and allow plugins, etc.
The documentation so far is here:
http://files.cockpit-project.org/guide/latest/development.html
If you're interested in providing early feedback, we have one such reusable Cockpit component (a web based terminal) ready for playing around with:
Screenshot: http://thewalter.net/stef/shots/integrating-terminal.png
Example: https://github.com/cockpit-project/cockpit/blob/master/examples/integrate-te...
Component: http://files.cockpit-project.org/guide/latest/api-terminal-html.html
The above requires Cockpit 0.28.
Because of these changes, if you have a git clone, you'll probably need to reinstall cockpit over again. I would suggest removing the $prefix/share/cockpit directory and reinstalling. For example, if you installed to the default location on Fedora, after building the nw version you would do:
$ sudo rm -rf /usr/share/cockpit/* $ sudo make install $ sudo restorecon -Rv /usr/share/cockpit
Stef
Yeah! Plus being able to view logs for a docker container would be super handy too!
On 16 Oct 2014, at 20:35, Stef Walter stefw@redhat.com wrote:
With Fedora 21 out of the way, we've merged the first round of work that enables reusable Cockpit javascript components that can be integrated into other web applications.
There is more work to come on this. We're working on refactoring Cockpit into packages internally, to make it more modular, and allow plugins, etc.
The documentation so far is here:
http://files.cockpit-project.org/guide/latest/development.html
If you're interested in providing early feedback, we have one such reusable Cockpit component (a web based terminal) ready for playing around with:
Screenshot: http://thewalter.net/stef/shots/integrating-terminal.png
Example: https://github.com/cockpit-project/cockpit/blob/master/examples/integrate-te...
Component: http://files.cockpit-project.org/guide/latest/api-terminal-html.html
The above requires Cockpit 0.28.
Because of these changes, if you have a git clone, you'll probably need to reinstall cockpit over again. I would suggest removing the $prefix/share/cockpit directory and reinstalling. For example, if you installed to the default location on Fedora, after building the nw version you would do:
$ sudo rm -rf /usr/share/cockpit/* $ sudo make install $ sudo restorecon -Rv /usr/share/cockpit
Stef _______________________________________________ cockpit-devel mailing list cockpit-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cockpit-devel
James ------- Red Hat
Twitter: @jstrachan Email: jstracha@redhat.com Blog: http://macstrac.blogspot.com/
hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Open Source Integration
Whoops, replied to the wrong email in a thread sorry! ;)
This all sounds great though!
On 16 Oct 2014, at 20:52, James Strachan jstracha@redhat.com wrote:
On 16 Oct 2014, at 20:35, Stef Walter stefw@redhat.com wrote:
With Fedora 21 out of the way, we've merged the first round of work that enables reusable Cockpit javascript components that can be integrated into other web applications.
There is more work to come on this. We're working on refactoring Cockpit into packages internally, to make it more modular, and allow plugins, etc.
The documentation so far is here:
http://files.cockpit-project.org/guide/latest/development.html
If you're interested in providing early feedback, we have one such reusable Cockpit component (a web based terminal) ready for playing around with:
Screenshot: http://thewalter.net/stef/shots/integrating-terminal.png
Example: https://github.com/cockpit-project/cockpit/blob/master/examples/integrate-te...
Component: http://files.cockpit-project.org/guide/latest/api-terminal-html.html
The above requires Cockpit 0.28.
Because of these changes, if you have a git clone, you'll probably need to reinstall cockpit over again. I would suggest removing the $prefix/share/cockpit directory and reinstalling. For example, if you installed to the default location on Fedora, after building the nw version you would do:
$ sudo rm -rf /usr/share/cockpit/* $ sudo make install $ sudo restorecon -Rv /usr/share/cockpit
Stef _______________________________________________ cockpit-devel mailing list cockpit-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cockpit-devel
James
Red Hat
Twitter: @jstrachan Email: jstracha@redhat.com Blog: http://macstrac.blogspot.com/
hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Open Source Integration
cockpit-devel mailing list cockpit-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cockpit-devel
James ------- Red Hat
Twitter: @jstrachan Email: jstracha@redhat.com Blog: http://macstrac.blogspot.com/
hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Open Source Integration
So we’ve a HTML5 (angularjs) console for kubernetes, fabric8, a wiki, dashboard, kibana, grafana and lots of Java stuff…. http://hawt.io/ http://hawt.io/plugins/index.html
Right now hawtio can work with the kubernetes pods/services/replication controllers (and view/filter/start/stop/create etc) and it let folks look inside JVMs if they are running, say, WildFly/Tomcat/ActiveMQ/Camel etc. Its basically our console for an aPaaS / iPaaS stuff (e.g. for things like JBoss Fuse on OpenShift).
For each pod/container in kubernetes we know the docker container id and host; so it’d be really awesome to then link/embed/reuse cockpit to view the docker container UI details; in particular viewing the logs of each docker container together with overall docker metadata etc.
Its been on our list for a while to figure out how to integrate hawtio and cockpit together; so cockpit can link/embed/reuse hawtio and vice versa. Right now the big pressing need we have is an easy way to access docker logs which might be the first use case that makes us try figure out how to embed/reuse/link cockpit inside hawtio.
So seeing this email thread was a timely reminder of something thats been on our TODO list for a while; so hopefully in a few weeks when we’re a little less loaded we can try it out.
On 16 Oct 2014, at 22:40, Andreas Nilsson lists@andreasn.se wrote:
On 2014-10-16 21:58, James Strachan wrote:
Whoops, replied to the wrong email in a thread sorry! ;)
But do you need the Docker journal feature, or was that for another product alltogether?
- Andreas
cockpit-devel mailing list cockpit-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cockpit-devel
James ------- Red Hat
Twitter: @jstrachan Email: jstracha@redhat.com Blog: http://macstrac.blogspot.com/
hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Open Source Integration
On 17.10.2014 07:36, James Strachan wrote:
So we’ve a HTML5 (angularjs) console for kubernetes, fabric8, a wiki, dashboard, kibana, grafana and lots of Java stuff…. http://hawt.io/ http://hawt.io/plugins/index.html
Right now hawtio can work with the kubernetes pods/services/replication controllers (and view/filter/start/stop/create etc) and it let folks look inside JVMs if they are running, say, WildFly/Tomcat/ActiveMQ/Camel etc. Its basically our console for an aPaaS / iPaaS stuff (e.g. for things like JBoss Fuse on OpenShift).
For each pod/container in kubernetes we know the docker container id and host; so it’d be really awesome to then link/embed/reuse cockpit to view the docker container UI details; in particular viewing the logs of each docker container together with overall docker metadata etc.
Indeed, I have some code that does this on a branch. I'll clean it up a bit, and post back when it's ready.
Its been on our list for a while to figure out how to integrate hawtio and cockpit together; so cockpit can link/embed/reuse hawtio and vice versa. Right now the big pressing need we have is an easy way to access docker logs which might be the first use case that makes us try figure out how to embed/reuse/link cockpit inside hawtio.
Yes, and lots to learn to learn on our end from figuring this out as well.
Stef
On 17 Oct 2014, at 11:06, Stef Walter stefw@redhat.com wrote:
On 17.10.2014 07:36, James Strachan wrote:
So we’ve a HTML5 (angularjs) console for kubernetes, fabric8, a wiki, dashboard, kibana, grafana and lots of Java stuff…. http://hawt.io/ http://hawt.io/plugins/index.html
Right now hawtio can work with the kubernetes pods/services/replication controllers (and view/filter/start/stop/create etc) and it let folks look inside JVMs if they are running, say, WildFly/Tomcat/ActiveMQ/Camel etc. Its basically our console for an aPaaS / iPaaS stuff (e.g. for things like JBoss Fuse on OpenShift).
For each pod/container in kubernetes we know the docker container id and host; so it’d be really awesome to then link/embed/reuse cockpit to view the docker container UI details; in particular viewing the logs of each docker container together with overall docker metadata etc.
Indeed, I have some code that does this on a branch. I'll clean it up a bit, and post back when it's ready.
Ah great thanks!
Its been on our list for a while to figure out how to integrate hawtio and cockpit together; so cockpit can link/embed/reuse hawtio and vice versa. Right now the big pressing need we have is an easy way to access docker logs which might be the first use case that makes us try figure out how to embed/reuse/link cockpit inside hawtio.
Yes, and lots to learn to learn on our end from figuring this out as well.
Agreed ;)
I’ll post a link to a little video demo of hawtio with OpenShift/kubernetes in a week or two when things settle down a little…
James ------- Red Hat
Twitter: @jstrachan Email: jstracha@redhat.com Blog: http://macstrac.blogspot.com/
hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Open Source Integration
cockpit-devel@lists.fedorahosted.org
-
Andreas Nilsson -
James Strachan -
Stef Walter