Feature: Add a new container Logs API about rancher HOT 4 CLOSED

The progress of this feature can be tracked here - rancher/cattle#138

from rancher.

Few questions @ibuildthecloud

1. Currently, if I follow the pattern for execHandler, we return the URL to the websocket but when we talk about jwt authentication, how and where do we do its validation? Where can i get the public-key from so that once the jwt token is created by the Rancher server, it could be validated once the request comes in from the user?

2. Once the URL to the websocket with a port, container UUID and other arguments have been returned, the click on that URL should trigger a request and the "host-api" which I believe is listening to these requests. But looking at this GO-code, it seems it is kind of specific to "Stats" command, so do you think i should modify/restructure it and use it to make calls to the docker daemon? Or write a new Go-agent ?

3. When you talk about calling docker twice , one for stdOut and another for stdErr, could you point me to any existing module which handles the multiplexing and how any concurrency issues might have been handled here ?

4. What should actually be returned once the "docker logs...." call has been executed ? This "object" would need to be passed back to the UI.

from rancher.

The frame format is

0 1 TS Content

Where 0 is the version number (always 0 for now), 1 is the either 1 or 2 depending on stdout/stderr and the TS is timestamp in the format that Docker returns.

from rancher.

Closing as #40 is closed.

from rancher.