You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by e-...@gmx.fr on 2023/09/29 08:44:25 UTC

NIFI-REGISTRY Migration


Hello all,



Someone has already migrate their nifi-registry from hostA to hostB (nifi-
registry) and keep track the versionning for the nifi client points to the
hostB ?



Have we got some documentations about migration nifi-registry ?



regards



Minh


Re: NIFI-REGISTRY Migration

Posted by Dennis Suhari <d....@icloud.com>.
Hi,

  

doesn’t 💯 fit your answer but maybe it is an aspect:

1) connect your old Nifi registry to a git repo (e.g. use GitHub, GitLab).

2) Push your processor groups, processors to old Nifi registry and by this it
is automatically pushed to Git Repo.

3) Setup new Nifi registry and connect it to Git provider and to pushed repo.

4) After that you can pull your old code by using processor groups -> import
from external repo within your Nifi

  

Br,

  

Dennis  
  

Von meinem iPhone gesendet

  

> Am 29.09.2023 um 13:30 schrieb e-sociaux@gmx.fr:  
>  
>

> 
>
> Hello Pierre,
>
>  
>
> Thanks for new option.
>
>  
>
> So it means, the dataflow_1 register in the registry_A, will be register in
> the same way in registry_B after migration ?
>
> Or needs we also use the URL aliasing ?
>
>  
>
> Regards
>
>  
>
> **Envoyé:**  vendredi 29 septembre 2023 à 12:41  
>  **De:**  "Pierre Villard" <pi...@gmail.com>  
>  **À:**  users@nifi.apache.org  
>  **Objet:**  Re: NIFI-REGISTRY Migration
>
> Hi,
>
> the
>
> You could also consider using the recently added Toolkit CLI optihons to
> export all / import all from Registry A to B.
>
>  
>
> Pierre
>
>  
>
> Le ven. 29 sept. 2023 à 12:13, Lars Winderling
> <[lars.winderling@posteo.de](mailto:lars.winderling@posteo.de)> a écrit :
>

>> Hi Minh,  
>  
>  you could try to employ [URL aliasing](https://nifi.apache.org/docs/nifi-
> registry-docs/html/administration-guide.html#url-aliasing) as explained in
> the docs. This way, the registry will store only an alias instead of the
> actual registry address. When migrating to another host, make sure to assign
> the same alias to it, and it should be able to retrieve versioning
> information properly.  
>  Another option would be to use a persistent host name (same A/AAAA entries,
> or a CNAME).  
>  This way, I have migrated our registry already a few times.  
>  
>  I hope this helps.  
>  Best,  
>  Lars  
>  
>>  
>>  
>>  
>>

>> On 23-09-29 10:44, [e-sociaux@gmx.fr](mailto:e-sociaux@gmx.fr) wrote:

>>

>>>  
>>>

>>> Hello all,

>>>

>>>  
>>>

>>> Someone has already migrate their nifi-registry from hostA to hostB (nifi-
registry) and keep track the versionning for the nifi client points to the
hostB ?

>>>

>>>  
>>>

>>> Have we got some documentations about migration nifi-registry ?

>>>

>>>  
>>>

>>> regards

>>>

>>>  
>>>

>>> Minh

>
>  
>
>  


Re: NIFI-REGISTRY Migration

Posted by e-...@gmx.fr.
Hello Pierre,



Thanks for new option.



So it means, the dataflow_1 register in the registry_A, will be register in
the same way in registry_B after migration ?

Or needs we also use the URL aliasing ?



Regards



**Envoy e:** vendredi 29 septembre 2023 a 12:41  
**De:**  "Pierre Villard" <pi...@gmail.com>  
**À :** users@nifi.apache.org  
**Objet:**  Re: NIFI-REGISTRY Migration

Hi,

the

You could also consider using the recently added Toolkit CLI optihons to
export all / import all from Registry A to B.



Pierre



Le ven. 29 sept. 2023 a 12:13, Lars Winderling
<[lars.winderling@posteo.de](mailto:lars.winderling@posteo.de)> a ecrit :

> Hi Minh,  
>  
>  you could try to employ [URL aliasing](https://nifi.apache.org/docs/nifi-
> registry-docs/html/administration-guide.html#url-aliasing) as explained in
> the docs. This way, the registry will store only an alias instead of the
> actual registry address. When migrating to another host, make sure to assign
> the same alias to it, and it should be able to retrieve versioning
> information properly.  
>  Another option would be to use a persistent host name (same A/AAAA entries,
> or a CNAME).  
>  This way, I have migrated our registry already a few times.  
>  
>  I hope this helps.  
>  Best,  
>  Lars  
>  
>  
>  
>  
>
> On 23-09-29 10:44, [e-sociaux@gmx.fr](mailto:e-sociaux@gmx.fr) wrote:
>

>>  
>>

>> Hello all,

>>

>>  
>>

>> Someone has already migrate their nifi-registry from hostA to hostB (nifi-
registry) and keep track the versionning for the nifi client points to the
hostB ?

>>

>>  
>>

>> Have we got some documentations about migration nifi-registry ?

>>

>>  
>>

>> regards

>>

>>  
>>

>> Minh






Re: NIFI-REGISTRY Migration

Posted by Pierre Villard <pi...@gmail.com>.
Hi,

You could also consider using the recently added Toolkit CLI options to
export all / import all from Registry A to B.

Pierre

Le ven. 29 sept. 2023 à 12:13, Lars Winderling <la...@posteo.de>
a écrit :

> Hi Minh,
>
> you could try to employ URL aliasing
> <https://nifi.apache.org/docs/nifi-registry-docs/html/administration-guide.html#url-aliasing>
> as explained in the docs. This way, the registry will store only an alias
> instead of the actual registry address. When migrating to another host,
> make sure to assign the same alias to it, and it should be able to retrieve
> versioning information properly.
> Another option would be to use a persistent host name (same A/AAAA
> entries, or a CNAME).
> This way, I have migrated our registry already a few times.
>
> I hope this helps.
> Best,
> Lars
>
> On 23-09-29 10:44, e-sociaux@gmx.fr wrote:
>
>
> Hello all,
>
> Someone has already migrate their nifi-registry from hostA to hostB
> (nifi-registry) and keep track the versionning for the nifi client points
> to the hostB ?
>
> Have we got some documentations about migration nifi-registry ?
>
> regards
>
> Minh
>
>
>

Re: NIFI-REGISTRY Migration

Posted by Lars Winderling <la...@posteo.de>.
Hi Minh,

you could try to employ URL aliasing 
<https://nifi.apache.org/docs/nifi-registry-docs/html/administration-guide.html#url-aliasing> 
as explained in the docs. This way, the registry will store only an 
alias instead of the actual registry address. When migrating to another 
host, make sure to assign the same alias to it, and it should be able to 
retrieve versioning information properly.
Another option would be to use a persistent host name (same A/AAAA 
entries, or a CNAME).
This way, I have migrated our registry already a few times.

I hope this helps.
Best,
Lars

On 23-09-29 10:44, e-sociaux@gmx.fr wrote:
> Hello all,
> Someone has already migrate their nifi-registry from hostA to hostB 
> (nifi-registry) and keep track the versionning for the nifi client 
> points to the hostB ?
> Have we got some documentations about migration nifi-registry ?
> regards
> Minh