I happen to prefer those particular long names.
Some short names are great like conf instead of config of configuration.

But:
1. topo - just yuck,
2. sec - I want to easily see the security dir,
3. wars - to implementation specific.

Have we verified with other projects where their security artifacts are?
My concern is that it may be more problematic to facilitate knox being able
to write to them by putting them in data than it is to not have knox write
to them at all. Is it possible that the server having to persist the master
and the like is a violation of some sort?


On Tue, Jan 14, 2014 at 7:35 PM, Dilli Arumugam
<[email protected]>wrote:

> Makes Sense.
> Thanks
> Dilli
>
>
> On Tue, Jan 14, 2014 at 3:50 PM, Kevin Minder
> <[email protected]>wrote:
>
> > That is where security started out. However, it cannot go under conf as
> > the content of that directory is gerated at runtime by the server.  In
> > Linux, conf directories (i.e. /etc/knox) are owned by by root and
> therefore
> > the knox server (running as knox) cannot write there.
> >
> >
> > On 1/14/14 6:43 PM, Dilli Arumugam wrote:
> >
> >> Would vote for long names.
> >> Wondering whether security needs to go under conf?
> >> Thanks
> >> Dilli
> >>
> >>
> >> On Tue, Jan 14, 2014 at 3:14 PM, Kevin Minder
> >> <[email protected]>wrote:
> >>
> >>  For KNOX-226 I have a patch almost ready that changes the GATEWAY_HOME
> >>> layout from
> >>>
> >>> What I have right now changes from the current layout
> >>>
> >>> {GATEWAY_HOME}/
> >>>      conf/
> >>>          security/
> >>>      deployments
> >>>          sandbox.xml
> >>>          sandbox.war.*/
> >>>
> >>> to this new layout which is more Linux friendly as conf and data will
> be
> >>> symlinks /etc/knox/conf and /var/lib/knox/data respectively.
> >>>
> >>> {GATEWAY_HOME}/
> >>>      conf
> >>>          topologies/
> >>>              sandbox.xml
> >>>      data
> >>>          security/
> >>>          deployments/
> >>>              sandbox.war.*/
> >>>
> >>> Does anyone have issues or concerns about this?
> >>> Any input on long names vs short names (sec vs security, wars vs
> >>> deployments, topo vs topologies, etc.)?
> >>> For example...
> >>>
> >>> {GATEWAY_HOME}/
> >>>      conf
> >>>          topo/
> >>>              sandbox.xml
> >>>      data
> >>>          sec/
> >>>          wars/
> >>>              sandbox.war.*/
> >>>
> >>>
> >>> --
> >>> CONFIDENTIALITY NOTICE
> >>> NOTICE: This message is intended for the use of the individual or
> entity
> >>> to which it is addressed and may contain information that is
> >>> confidential,
> >>> privileged and exempt from disclosure under applicable law. If the
> reader
> >>> of this message is not the intended recipient, you are hereby notified
> >>> that
> >>> any printing, copying, dissemination, distribution, disclosure or
> >>> forwarding of this communication is strictly prohibited. If you have
> >>> received this communication in error, please contact the sender
> >>> immediately
> >>> and delete it from your system. Thank You.
> >>>
> >>>
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> > to which it is addressed and may contain information that is
> confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Reply via email to