Virtualization Plugins

Hi everyone! 

If the staging server has many binaries, what is the best way to ensure that the same version is used between a source and a staging during the data ingestion(linked_pre_snapshot)?

Regards,
Paulo.


------------------------------
Paulo Maluf
Database Consulting
Experior Tecnologia LTDA.
------------------------------

Hi Paulo,
Welcome to the community! Quick question on your post, are you developing a plugin or is this a general virtualization question? If it is a general virtualization question, I will move it to a location where the right people will see it.

Thanks,
Michael

------------------------------
Michael Torok
Director of Knowledge and Community Management
Delphix
------------------------------

Original Message:
Sent: 03-08-2020 08:10:32 PM
From: Paulo Maluf
Subject: Ensure version between Source and Staging

Hi everyone! 

If the staging server has many binaries, what is the best way to ensure that the same version is used between a source and a staging during the data ingestion(linked_pre_snapshot)?

Regards,
Paulo.


------------------------------
Paulo Maluf
Database Consulting
Experior Tecnologia LTDA.
------------------------------

Hi Michael, how are you?

I have already developed a plug-in for MongoDB and Informix IDS. I would like to know if I am using the best practices for doing some functionalities. 

Regards,
Paulo.

------------------------------
Paulo Maluf
Database Specialist
Experior Tecnologia LTDA.
------------------------------

Original Message:
Sent: 03-09-2020 10:58:10 AM
From: Michael Torok
Subject: Ensure version between Source and Staging

Hi Paulo,
Welcome to the community! Quick question on your post, are you developing a plugin or is this a general virtualization question? If it is a general virtualization question, I will move it to a location where the right people will see it.

Thanks,
Michael

------------------------------
Michael Torok
Director of Knowledge and Community Management
Delphix

Original Message:
Sent: 03-08-2020 08:10:32 PM
From: Paulo Maluf
Subject: Ensure version between Source and Staging

Hi everyone! 

If the staging server has many binaries, what is the best way to ensure that the same version is used between a source and a staging during the data ingestion(linked_pre_snapshot)?

Regards,
Paulo.


------------------------------
Paulo Maluf
Database Consulting
Experior Tecnologia LTDA.
------------------------------

Excellent, sir! I'll see about getting this in front of the right people. Thank you.

------------------------------
Michael Torok
Director of Knowledge and Community Management
Delphix
------------------------------

Original Message:
Sent: 03-09-2020 11:08:56 AM
From: Paulo Maluf
Subject: Ensure version between Source and Staging

Hi Michael, how are you?

I have already developed a plug-in for MongoDB and Informix IDS. I would like to know if I am using the best practices for doing some functionalities. 

Regards,
Paulo.

------------------------------
Paulo Maluf
Database Specialist
Experior Tecnologia LTDA.

Original Message:
Sent: 03-09-2020 10:58:10 AM
From: Michael Torok
Subject: Ensure version between Source and Staging

Hi Paulo,
Welcome to the community! Quick question on your post, are you developing a plugin or is this a general virtualization question? If it is a general virtualization question, I will move it to a location where the right people will see it.

Thanks,
Michael

------------------------------
Michael Torok
Director of Knowledge and Community Management
Delphix

Original Message:
Sent: 03-08-2020 08:10:32 PM
From: Paulo Maluf
Subject: Ensure version between Source and Staging

Hi everyone! 

If the staging server has many binaries, what is the best way to ensure that the same version is used between a source and a staging during the data ingestion(linked_pre_snapshot)?

Regards,
Paulo.


------------------------------
Paulo Maluf
Database Consulting
Experior Tecnologia LTDA.
------------------------------

Hey Paulo,
This would depend on the object model that you have chosen for the plugin and what the "repository" and "source_config" refer to for the plugin. These are some of the options:

1. "repository" and "source_config" refer to production
   1. Ask the user for a binary location as part of the user input when linking, validate it using the "staged_source.staged_connection" by comparing it against the "repository"/"source_config" from production.
   2. The plugin code searches for all installations during the plugin operation using the "staged_source.staged_connection" and matches it with the "repository" / "source_config" from production and raise an exception if no matching installation is found. Minimizing any user input is always better assuming the automatic search is fast and reliable.
2. "repository" and "source_config" refer to staging host and production information is entered by the user
   In this case you should be able to query the production version against the "repository" / "source_config" version by connecting to the production host using the information entered by the user.

------------------------------
Ankur Sarin
Senior Engineering Manager
Delphix
------------------------------

Original Message:
Sent: 03-08-2020 08:10:32 PM
From: Paulo Maluf
Subject: Ensure version between Source and Staging

Hi everyone! 

If the staging server has many binaries, what is the best way to ensure that the same version is used between a source and a staging during the data ingestion(linked_pre_snapshot)?

Regards,
Paulo.


------------------------------
Paulo Maluf
Database Consulting
Experior Tecnologia LTDA.
------------------------------

Hi Ankur, 

Thanks for your reply. 

I am using a workaround similar to option "b". But instead of searching for all installations in the linked.pre_snapsho() phase, I am saving the version in discovery.source_config() in addition to the discovery.repository(). That way, I can compare the version of the repository (source) with the source_config (staging).

For the next versions of the SDK, it would be interesting if it were possible to access the source and staging repository on the linked.pre_snapshot().

Thanks,
Paulo.

------------------------------
Paulo Maluf
Database Consulting
Experior Tecnologia LTDA.
------------------------------

Original Message:
Sent: 03-09-2020 12:28:54 PM
From: Ankur Sarin
Subject: Ensure version between Source and Staging

Hey Paulo,
This would depend on the object model that you have chosen for the plugin and what the "repository" and "source_config" refer to for the plugin. These are some of the options:

1. "repository" and "source_config" refer to production
   1. Ask the user for a binary location as part of the user input when linking, validate it using the "staged_source.staged_connection" by comparing it against the "repository"/"source_config" from production.
   2. The plugin code searches for all installations during the plugin operation using the "staged_source.staged_connection" and matches it with the "repository" / "source_config" from production and raise an exception if no matching installation is found. Minimizing any user input is always better assuming the automatic search is fast and reliable.
2. "repository" and "source_config" refer to staging host and production information is entered by the user
   In this case you should be able to query the production version against the "repository" / "source_config" version by connecting to the production host using the information entered by the user.

------------------------------
Ankur Sarin
Senior Engineering Manager
Delphix

Original Message:
Sent: 03-08-2020 08:10:32 PM
From: Paulo Maluf
Subject: Ensure version between Source and Staging

Hi everyone! 

If the staging server has many binaries, what is the best way to ensure that the same version is used between a source and a staging during the data ingestion(linked_pre_snapshot)?

Regards,
Paulo.


------------------------------
Paulo Maluf
Database Consulting
Experior Tecnologia LTDA.
------------------------------

Hi Paulo,
I took the liberty of creating an idea for your enhancement request. Please let me know if it captures your request and vote for it (click the thumbs up icon).
https://community.delphix.com/ideation-home/viewidea?IdeationKey=081a4c84-0b73-4042-a5f4-0b7356b09636

Thank you,
Michael

------------------------------
Michael Torok
Director of Knowledge and Community Management
Delphix
------------------------------

Original Message:
Sent: 03-09-2020 10:03:49 PM
From: Paulo Maluf
Subject: Ensure version between Source and Staging

Hi Ankur, 

Thanks for your reply. 

I am using a workaround similar to option "b". But instead of searching for all installations in the linked.pre_snapsho() phase, I am saving the version in discovery.source_config() in addition to the discovery.repository(). That way, I can compare the version of the repository (source) with the source_config (staging).

For the next versions of the SDK, it would be interesting if it were possible to access the source and staging repository on the linked.pre_snapshot().

Thanks,
Paulo.

------------------------------
Paulo Maluf
Database Consulting
Experior Tecnologia LTDA.

Original Message:
Sent: 03-09-2020 12:28:54 PM
From: Ankur Sarin
Subject: Ensure version between Source and Staging

Hey Paulo,
This would depend on the object model that you have chosen for the plugin and what the "repository" and "source_config" refer to for the plugin. These are some of the options:

1. "repository" and "source_config" refer to production
   1. Ask the user for a binary location as part of the user input when linking, validate it using the "staged_source.staged_connection" by comparing it against the "repository"/"source_config" from production.
   2. The plugin code searches for all installations during the plugin operation using the "staged_source.staged_connection" and matches it with the "repository" / "source_config" from production and raise an exception if no matching installation is found. Minimizing any user input is always better assuming the automatic search is fast and reliable.
2. "repository" and "source_config" refer to staging host and production information is entered by the user
   In this case you should be able to query the production version against the "repository" / "source_config" version by connecting to the production host using the information entered by the user.

------------------------------
Ankur Sarin
Senior Engineering Manager
Delphix

Original Message:
Sent: 03-08-2020 08:10:32 PM
From: Paulo Maluf
Subject: Ensure version between Source and Staging

Hi everyone! 

If the staging server has many binaries, what is the best way to ensure that the same version is used between a source and a staging during the data ingestion(linked_pre_snapshot)?

Regards,
Paulo.


------------------------------
Paulo Maluf
Database Consulting
Experior Tecnologia LTDA.
------------------------------

Hey Paulo,

I am not sure I followed that completely. The repository you have points to production while the source_config points to staging? Would you be able to provide more details about how you do that? A source_config always belongs to a repository, so I am not sure how it was able to refer to a different host?


------------------------------
Ankur Sarin
Senior Engineering Manager
Delphix
------------------------------

Original Message:
Sent: 03-09-2020 10:03:49 PM
From: Paulo Maluf
Subject: Ensure version between Source and Staging

Hi Ankur, 

Thanks for your reply. 

I am using a workaround similar to option "b". But instead of searching for all installations in the linked.pre_snapsho() phase, I am saving the version in discovery.source_config() in addition to the discovery.repository(). That way, I can compare the version of the repository (source) with the source_config (staging).

For the next versions of the SDK, it would be interesting if it were possible to access the source and staging repository on the linked.pre_snapshot().

Thanks,
Paulo.

------------------------------
Paulo Maluf
Database Consulting
Experior Tecnologia LTDA.

Original Message:
Sent: 03-09-2020 12:28:54 PM
From: Ankur Sarin
Subject: Ensure version between Source and Staging

Hey Paulo,
This would depend on the object model that you have chosen for the plugin and what the "repository" and "source_config" refer to for the plugin. These are some of the options:

1. "repository" and "source_config" refer to production
   1. Ask the user for a binary location as part of the user input when linking, validate it using the "staged_source.staged_connection" by comparing it against the "repository"/"source_config" from production.
   2. The plugin code searches for all installations during the plugin operation using the "staged_source.staged_connection" and matches it with the "repository" / "source_config" from production and raise an exception if no matching installation is found. Minimizing any user input is always better assuming the automatic search is fast and reliable.
2. "repository" and "source_config" refer to staging host and production information is entered by the user
   In this case you should be able to query the production version against the "repository" / "source_config" version by connecting to the production host using the information entered by the user.

------------------------------
Ankur Sarin
Senior Engineering Manager
Delphix

Original Message:
Sent: 03-08-2020 08:10:32 PM
From: Paulo Maluf
Subject: Ensure version between Source and Staging

Hi everyone! 

If the staging server has many binaries, what is the best way to ensure that the same version is used between a source and a staging during the data ingestion(linked_pre_snapshot)?

Regards,
Paulo.


------------------------------
Paulo Maluf
Database Consulting
Experior Tecnologia LTDA.
------------------------------