Right. Although I don't think we would use the server side parts of hawt.io in Cockpit [1] ... but once the design is done (together with the Openshift designers), we can take a look at whether we can reuse some of the browser side code to implement consistent kubernetes behavior.
Stef
[1] http://stef.thewalter.net/ideals-of-cockpit.html
----- Original Message ----- From: "James Strachan" jstracha@redhat.com To: "Development discussion for the Cockpit Project" cockpit-devel@lists.fedorahosted.org Sent: Thursday, January 15, 2015 1:26:17 PM Subject: Re: Kubernetes Design Use Cases
we’re currently looking at reusing the fabric8 UI for kubernetes in the OpenShift V3 UI and combining the UIs into a unified console; it’d be awesome to start integrating cockpit & the hawtio fabric8/openshift UI too.
On 15 Jan 2015, at 12:17, Stef Walter stefw@redhat.com wrote:
On 15.01.2015 13:12, Arno Schulz wrote:
Silly question, you've got 3 projects supported by red hat (fabric8, open shift and atomic/cockpit) yet each seems to work on their own distinct flavour of kubernetes frontend.
Am I missing something here or would there be a chance to leverage the strengths of these three by cooperating?
Yes, that's the plan. We're working with the OpenShift designers to come up with consistent designs for these use cases. The target audience and user stories are slightly different from the Openshift audience/stories ... but we should still be consistent. Fingers crossed.
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