----- Leif Hedstrom <zw...@apache.org> wrote:
> Hi all,

Hey Leif,

> I'd like to propose a number of changes to the mgmt stuff, please let me 
> know if you have concerns or objects to any of the following:
> 
> 1) We rename proxy/mgmt to just mgmt/. This puts all the management 
> stuff outside of the proxy server itself, similar to how iocore, 
> librecords etc. are also outside the actual proxy server.

+1

> 2) Move proxy/mgmt/cop to just cop/. Same reason above, and this puts 
> our three main server processes each in their own top level source tree.

+1
 
> 3) We eliminate all of mgmt/cli entirely. This requires rewriting 
> traffic_line to use the "new" mgmt API (see #3), and also modify 
> traffic_cop to healthcheck this unix domain socket instead of the old "cli".

+++++12334094
 
> 4) Rename mgmt/cli2 to mgmt/cli. This is the new management API, which 
> traffic_shell uses for example.

I'm currently working on purging mgmt of the webui, entirely.

Current state:

i.galic@phoenix ~/Projects/asf/trafficserver (svn)-[trunk:1059214] % svn st | 
ack '^D'|wc -l
111

I hope our efforts don't clash somewhere ;)
I'm migrating functions "needed" from web2 into proxy/mgmt/utils/WebMgmtUtils*

I'll see to committing this as soon as possible, probably before the end
of the weekend.

> 5) Move the layout engine out of iocore/utils, and into lib/<something>. 
> Either a lib/utils or lib/layout, I'm leaning towards the first 
> (lib/utils) to not spread things too thin.
> 
> 6) If possible (might have to wait until v3.1) Change 
> api/remote/libmgmtapiremote.a  to be a .so (e.g. libtsmgmtapi.so.3.0.0), 
> and also expose the appropriate header file. This would allow for easy 
> application building on top of the management APIs.
> 
> 
> 1) and 2) are outlined in John's proposal on the Wiki: 
> https://cwiki.apache.org/confluence/display/TS/ReorganizeDirectoryStructure 
> .
> 
> 
> Cheers,
> 
> -- Leif


So long,
i


-- 
Igor Galić

Tel: +43 (0) 664 886 22 883
Mail: i.ga...@brainsware.org
URL: http://brainsware.org/

Reply via email to