Replication question

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Replication question

cvquesty
I am setting up an Artifactory Pro instance for a client.  They asked me to setup replication which all seems to work well.  

One thing is an unexpected behavior for me.  Let's say I have two instances.  I want the following behavior:


Instance1  =>  replicates  => Instance2

This works perfectly when both instances have the same repositories already created.  let's say now I have a new repository I am creating on Instance1 called "foo".  Let's also say I tell it to replicate over to instance2, having never setup the repository on instance2.

My *expected* behavior is that Artifactory would not care and would automatically create the repository if it does not already exist, but it does not do this.

1.  Is this intended behavior, or have I missed a setup element somewhere?
2.  Is it possible to make this the default behavior?
3.  If this is not currently a feature, could it be requested?

The customer wishes to only work with a single Artifactory instance, all changes, etc. being replicated out to the secondary instance.  They only need work with the second instance in the event of a catastrophe on instance1, changing their DNS pointer to the backup instance when needed.  In the current observed behavior, every time they create a new repository on instance1 and set it to replicate, they will also need to connect to instance2 and create the empty repository before replication will work.

Any insight or help you guys can offer?
Reply | Threaded
Open this post in threaded view
|

Re: Replication question

dave_p
Yeah, you're expected behavior isn't how it's designed.

When you set up replication targets, you have to specify a valid target
on instance2. That means it's already gotta be created. Which means
admin'ing both instances.

If you click the "Test" button under repo replication settings, it
should validate. If the target repo doesn't exist, it'll return an error.

What you're describing sounds like you want an Artifactory HA Cluster,
not replication.

http://www.jfrog.com/confluence/display/RTF/Artifactory+High+Availability

On 5/2/2014 7:42 AM, cvquesty wrote:

> I am setting up an Artifactory Pro instance for a client.  They asked me to
> setup replication which all seems to work well.
>
> One thing is an unexpected behavior for me.  Let's say I have two instances.
> I want the following behavior:
>
>
> Instance1  =>  replicates  => Instance2
>
> This works perfectly when both instances have the same repositories already
> created.  let's say now I have a new repository I am creating on Instance1
> called "foo".  Let's also say I tell it to replicate over to instance2,
> having never setup the repository on instance2.
>
> My *expected* behavior is that Artifactory would not care and would
> automatically create the repository if it does not already exist, but it
> does not do this.
>
> 1.  Is this intended behavior, or have I missed a setup element somewhere?
> 2.  Is it possible to make this the default behavior?
> 3.  If this is not currently a feature, could it be requested?
>
> The customer wishes to only work with a single Artifactory instance, all
> changes, etc. being replicated out to the secondary instance.  They only
> need work with the second instance in the event of a catastrophe on
> instance1, changing their DNS pointer to the backup instance when needed.
> In the current observed behavior, every time they create a new repository on
> instance1 and set it to replicate, they will also need to connect to
> instance2 and create the empty repository before replication will work.
>
> Any insight or help you guys can offer?
>
>
>
> --
> View this message in context: http://forums.jfrog.org/Replication-question-tp7579793.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Artifactory-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>

--
Dave Pierce
Engineering Services (MDC)
Dell | Compellent
[hidden email]

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

Re: Replication question

Ganesan, Ramaprakash
HA is different from Disaster Recovery, which is what seems to be the need. 
If there is no formal DR solution (like CA ARCserve offers) that can be used, then repository replication is probably a 'workaround'.

As mentioned, replication is currently working as designed. Repository setup is a must for application-side replication.


-------- Original message --------
From: David Pierce
Date:02/05/2014 7:25 PM (GMT+05:30)
To: [hidden email]
Subject: Re: [Artifactory-users] Replication question

Yeah, you're expected behavior isn't how it's designed.

When you set up replication targets, you have to specify a valid target
on instance2. That means it's already gotta be created. Which means
admin'ing both instances.

If you click the "Test" button under repo replication settings, it
should validate. If the target repo doesn't exist, it'll return an error.

What you're describing sounds like you want an Artifactory HA Cluster,
not replication.

<a href="http://www.jfrog.com/confluence/display/RTF/Artifactory&#43;High&#43;Availability">http://www.jfrog.com/confluence/display/RTF/Artifactory+High+Availability

On 5/2/2014 7:42 AM, cvquesty wrote:
> I am setting up an Artifactory Pro instance for a client.  They asked me to
> setup replication which all seems to work well.
>
> One thing is an unexpected behavior for me.  Let's say I have two instances.
> I want the following behavior:
>
>
> Instance1  =>  replicates  => Instance2
>
> This works perfectly when both instances have the same repositories already
> created.  let's say now I have a new repository I am creating on Instance1
> called "foo".  Let's also say I tell it to replicate over to instance2,
> having never setup the repository on instance2.
>
> My *expected* behavior is that Artifactory would not care and would
> automatically create the repository if it does not already exist, but it
> does not do this.
>
> 1.  Is this intended behavior, or have I missed a setup element somewhere?
> 2.  Is it possible to make this the default behavior?
> 3.  If this is not currently a feature, could it be requested?
>
> The customer wishes to only work with a single Artifactory instance, all
> changes, etc. being replicated out to the secondary instance.  They only
> need work with the second instance in the event of a catastrophe on
> instance1, changing their DNS pointer to the backup instance when needed.
> In the current observed behavior, every time they create a new repository on
> instance1 and set it to replicate, they will also need to connect to
> instance2 and create the empty repository before replication will work.
>
> Any insight or help you guys can offer?
>
>
>
> --
> View this message in context: http://forums.jfrog.org/Replication-question-tp7579793.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Artifactory-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>

--
Dave Pierce
Engineering Services (MDC)
Dell | Compellent
[hidden email]

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users