Shuffle directory structure

[istio]

Shuffle directory structure

[geeknoid]

Slight update:

istio.io/mixer/cmd/mixer/main.go
istio.io/mixer/cmd/mixerclient/main.go
istio.io/mixer/pkg/adapter/... (adapter support
istio.io/mixer/pkg/api/... (most of what's currently in mixer/server/*.go)
istio.io/mixer/​pkg/config/...
istio.io/mixer/pkg/attribute/...
istio.io/mixer/doc/...
istio.io/mixer/adapter/... (individual adapters)
istio.io/mixer/example/...

This structure provides high-level functional separation. We can have multiple commands for various utilities, we have room for examples & docs, and we have a flat set of adapters and flat set of support packages. This generally matches how k8s is organized.

Any counter proposals?

@mandarjog @douglas-reid

[mandarjog]

yup, let's go for it.
pkg should have importable reusable packages.
LGTM.

[geeknoid]

OK, as soon as my current PR is in, I'll move this stuff around.

…

On Tue, Dec 20, 2016 at 9:42 AM, mandarjog ***@***.***> wrote: yup, let's go for it. pkg should have importable reusable packages. LGTM. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#86 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AVucHVhBPcSBCOQ57J3fq2MpuJcnm1jOks5rKBONgaJpZM4LROp1> .

[douglas-reid]

one nit.

why not:

mixer/cmd/server
mixer/cmd/client

?

[geeknoid]

Yeah /server and /client looks good.

On a related note, what should we call our binaries? "server" and "client" seems a tad generic and unhelpful to the casual observer. Maybe mixserver and mixclient?

[douglas-reid]

mixserver sgtm. is it worth using something shorter than client for the client? maybe mixcli or mixctl or or mixcmd or even mixc ?

[geeknoid]

How about then: istio.io/mixer/cmd/mixs istio.io/mixer/cmd/mixc with mixs and mixc as our binaries?

…

On Tue, Dec 20, 2016 at 10:24 AM, Douglas Reid ***@***.***> wrote: mixserver sgtm. is it worth using something shorter than client for the client? maybe mixcli or mixctl or or mixcmd or even mixc ? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#86 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AVucHSiIcPQLmDQypncRE3bd5lAODmJ3ks5rKB11gaJpZM4LROp1> .

[douglas-reid]

What if we leave the dirs as server and client but have the go_binary rules named something like "mixs" and "mixc" or whatever? (the go build equivalent of the -o option)

[geeknoid]

OK

…

On Tue, Dec 20, 2016 at 10:44 AM, Douglas Reid ***@***.***> wrote: What if we leave the dirs as server and client but have the go_binary rules named something like "mixs" and "mixc" or whatever? (the go build equivalent of the -o option) — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#86 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AVucHWRL7JBZYVzBa9Q6iv2pYZZ9zHEPks5rKCIWgaJpZM4LROp1> .