You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by Shawn Weeks <sw...@weeksconsulting.us> on 2019/03/19 16:18:50 UTC

KNOX-1827 Oddness with Topology Deployments

For KNOX-1827 I've modified zeppelinui/0.8.0/rewrite.xml to no longer include path=app in ZEPPELINUI/zeppelin/inbound/rootAppScript. I then deleted every from the deployments folder and recreated topologies in the Knox Admin interface. Somehow after a certain period of time that line get's added back to the rewrite. Where is Knox sourcing the service definitions from during the autocreated topologies? Is it pulling them from within the jar or from the installation directory?

Thanks
Shawn Weeks

Re: KNOX-1827 Oddness with Topology Deployments

Posted by Shawn Weeks <sw...@weeksconsulting.us>.
Is there a good way to do #3 for the topologies you create in the admin ui? Currently I’m just dropping a service saving and re-adding. 

Sent from my iPhone

> On Mar 20, 2019, at 2:49 AM, larry mccay <la...@gmail.com> wrote:
> 
> When changing service definitions, it is important to do all of the
> following:
> 
> 1. make changes to rewrite/service XMLs
> 2. restart Knox - so that the new service definitions are loaded
> 3. touch any topology that is hosting the service for which you changes
> effected - so that a new webapp is created and deployed
> 
> #3 is nonintuitive but when you understand that the generated webapp for
> each topology contains the service definitions it makes sense.
> 
> On Tue, Mar 19, 2019 at 5:51 PM Shawn Weeks <sw...@weeksconsulting.us>
> wrote:
> 
>> /var/lib/knox/data-3.1.0.0-78/services/zeppelinui/0.8.0/rewrite.xml and I
>> did restart Knox after changing it. It seems like Knox bases new topology
>> generated rewrite.xmls off of the old ones so I've had to delete all the
>> deployments and restart and then recreate. Was wondering if it might have
>> been picking the 0.6.0 version for some reason as I haven't changed it.
>> 
>> Thanks
>> 
>> -----Original Message-----
>> From: Kevin Risden <kr...@apache.org>
>> Sent: Tuesday, March 19, 2019 11:26 AM
>> To: dev@knox.apache.org
>> Subject: Re: KNOX-1827 Oddness with Topology Deployments
>> 
>> What is the full path to the rewrite.xml you modified?
>> KNOX_INSTALL_DIR/data/services/zeppelinui/0.8.0/rewrite.xml? Did you
>> restart Knox after the change?
>> 
>> Kevin Risden
>> 
>> 
>> On Tue, Mar 19, 2019 at 12:19 PM Shawn Weeks <sw...@weeksconsulting.us>
>> wrote:
>> 
>>> For KNOX-1827 I've modified zeppelinui/0.8.0/rewrite.xml to no longer
>>> include path=app in ZEPPELINUI/zeppelin/inbound/rootAppScript. I then
>>> deleted every from the deployments folder and recreated topologies in
>>> the Knox Admin interface. Somehow after a certain period of time that
>>> line get's added back to the rewrite. Where is Knox sourcing the
>>> service definitions from during the autocreated topologies? Is it
>>> pulling them from within the jar or from the installation directory?
>>> 
>>> Thanks
>>> Shawn Weeks
>>> 
>>

Re: KNOX-1827 Oddness with Topology Deployments

Posted by larry mccay <la...@gmail.com>.
When changing service definitions, it is important to do all of the
following:

1. make changes to rewrite/service XMLs
2. restart Knox - so that the new service definitions are loaded
3. touch any topology that is hosting the service for which you changes
effected - so that a new webapp is created and deployed

#3 is nonintuitive but when you understand that the generated webapp for
each topology contains the service definitions it makes sense.

On Tue, Mar 19, 2019 at 5:51 PM Shawn Weeks <sw...@weeksconsulting.us>
wrote:

> /var/lib/knox/data-3.1.0.0-78/services/zeppelinui/0.8.0/rewrite.xml and I
> did restart Knox after changing it. It seems like Knox bases new topology
> generated rewrite.xmls off of the old ones so I've had to delete all the
> deployments and restart and then recreate. Was wondering if it might have
> been picking the 0.6.0 version for some reason as I haven't changed it.
>
> Thanks
>
> -----Original Message-----
> From: Kevin Risden <kr...@apache.org>
> Sent: Tuesday, March 19, 2019 11:26 AM
> To: dev@knox.apache.org
> Subject: Re: KNOX-1827 Oddness with Topology Deployments
>
> What is the full path to the rewrite.xml you modified?
> KNOX_INSTALL_DIR/data/services/zeppelinui/0.8.0/rewrite.xml? Did you
> restart Knox after the change?
>
> Kevin Risden
>
>
> On Tue, Mar 19, 2019 at 12:19 PM Shawn Weeks <sw...@weeksconsulting.us>
> wrote:
>
> > For KNOX-1827 I've modified zeppelinui/0.8.0/rewrite.xml to no longer
> > include path=app in ZEPPELINUI/zeppelin/inbound/rootAppScript. I then
> > deleted every from the deployments folder and recreated topologies in
> > the Knox Admin interface. Somehow after a certain period of time that
> > line get's added back to the rewrite. Where is Knox sourcing the
> > service definitions from during the autocreated topologies? Is it
> > pulling them from within the jar or from the installation directory?
> >
> > Thanks
> > Shawn Weeks
> >
>

RE: KNOX-1827 Oddness with Topology Deployments

Posted by Shawn Weeks <sw...@weeksconsulting.us>.
/var/lib/knox/data-3.1.0.0-78/services/zeppelinui/0.8.0/rewrite.xml and I did restart Knox after changing it. It seems like Knox bases new topology generated rewrite.xmls off of the old ones so I've had to delete all the deployments and restart and then recreate. Was wondering if it might have been picking the 0.6.0 version for some reason as I haven't changed it.

Thanks

-----Original Message-----
From: Kevin Risden <kr...@apache.org> 
Sent: Tuesday, March 19, 2019 11:26 AM
To: dev@knox.apache.org
Subject: Re: KNOX-1827 Oddness with Topology Deployments

What is the full path to the rewrite.xml you modified?
KNOX_INSTALL_DIR/data/services/zeppelinui/0.8.0/rewrite.xml? Did you restart Knox after the change?

Kevin Risden


On Tue, Mar 19, 2019 at 12:19 PM Shawn Weeks <sw...@weeksconsulting.us>
wrote:

> For KNOX-1827 I've modified zeppelinui/0.8.0/rewrite.xml to no longer 
> include path=app in ZEPPELINUI/zeppelin/inbound/rootAppScript. I then 
> deleted every from the deployments folder and recreated topologies in 
> the Knox Admin interface. Somehow after a certain period of time that 
> line get's added back to the rewrite. Where is Knox sourcing the 
> service definitions from during the autocreated topologies? Is it 
> pulling them from within the jar or from the installation directory?
>
> Thanks
> Shawn Weeks
>

Re: KNOX-1827 Oddness with Topology Deployments

Posted by Kevin Risden <kr...@apache.org>.
What is the full path to the rewrite.xml you modified?
KNOX_INSTALL_DIR/data/services/zeppelinui/0.8.0/rewrite.xml? Did you
restart Knox after the change?

Kevin Risden


On Tue, Mar 19, 2019 at 12:19 PM Shawn Weeks <sw...@weeksconsulting.us>
wrote:

> For KNOX-1827 I've modified zeppelinui/0.8.0/rewrite.xml to no longer
> include path=app in ZEPPELINUI/zeppelin/inbound/rootAppScript. I then
> deleted every from the deployments folder and recreated topologies in the
> Knox Admin interface. Somehow after a certain period of time that line
> get's added back to the rewrite. Where is Knox sourcing the service
> definitions from during the autocreated topologies? Is it pulling them from
> within the jar or from the installation directory?
>
> Thanks
> Shawn Weeks
>