Virtual machines (Cloud) - Historique des versions

Syfre le 7 février 2019 à 07:06

2019-02-07T07:06:13Z

← Version précédente		Version du 7 février 2019 à 07:06
Ligne 63 :		Ligne 63 :
	[[Category:Cloud]]		[[Category:Cloud]]
	[[Category:Architecture]]		[[Category:Architecture]]
			[[Category:Latest]]

Syfre : /* Virtual machine deployment process */

2017-02-27T08:54:49Z

Virtual machine deployment process

← Version précédente		Version du 27 février 2017 à 08:54
Ligne 36 :		Ligne 36 :
	The virtual machines are deployed by the Provisioning service (PDS).		The virtual machines are deployed by the Provisioning service (PDS).

	The PDS uses the Azure resource manager, the template used to create a new VM ~~include~~ a script executed during the VM provisioning.		The PDS uses the Azure resource manager, the template used to create a new VM includes a boot script executed by the VM during the provisioning.

	(This functionality is a [https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-classic-extensions-customscript custom script extension])		(This functionality is a [https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-classic-extensions-customscript custom script extension])
Ligne 43 :		Ligne 43 :
	* Download of the last Sage FRP 1000 service binary package from an account storage blob of the PDS.		* Download of the last Sage FRP 1000 service binary package from an account storage blob of the PDS.
	* Installation of the package		* Installation of the package
	* Create ~~the~~ service configuration file which ~~contain~~ the url on the PDS.		* Create a service configuration file which contains only the url on the PDS.

	The service start up, read the configuration file and start the configuration sequence.		The service start up, read the configuration file and start the configuration sequence.

Syfre : /* Sage FRP 1000 start up process */

2017-02-27T08:53:08Z

Sage FRP 1000 start up process

← Version précédente		Version du 27 février 2017 à 08:53
Ligne 16 :		Ligne 16 :

	* The configuration file must be provide on the local disk, this don't met the agnostic requirement		* The configuration file must be provide on the local disk, this don't met the agnostic requirement
	* The configuration contents sensitive information which may leaks if the VM is compromise.		* The configuration file contents sensitive information which may leaks if the VM is compromise.

	For these reasons, the start up process in a Cloud environment has been replaced by a configuration sequence where the S1000 contacts the configuration server (PDS) to obtain its configuration file. As the PDS maintains a list of the existing VM with ~~theire associat~~ role it can provide the adequate configuration file.		For these reasons, the start up process in a Cloud environment has been replaced by a configuration sequence where the S1000 contacts the configuration server (PDS) to obtain its configuration file. As the PDS maintains a list of the existing VM with there associate role, it can provide the adequate configuration file.

	This approach has several benefices :		This approach has several benefices :
Ligne 25 :		Ligne 25 :
	* The loading sequence is secure.		* The loading sequence is secure.
	* The VM has no sensitive information stored in its local storage		* The VM has no sensitive information stored in its local storage
	* The configuration may be updated ~~with~~ a centralized approach.		* The configuration may be updated in a centralized approach.

	The communication between the S1000 service and the PDS is protected :		The communication between the S1000 service and the PDS is protected :

	* The PDS identify the S1000 service by the DNS Name of VM.		* The PDS identify the S1000 service by the DNS Name of VM.
	* The data returned by the PDS are encrypted by a 3Des master key shared by both the S1000 and the PDS.		* The data returned by the PDS are encrypted by a 3Des master key (hard coded) shared by both the S1000 and the PDS.
	* The communication is over https.		* The communication is over https.

Syfre : /* Overview */

2017-02-27T08:50:42Z

Overview

← Version précédente		Version du 27 février 2017 à 08:50
Ligne 1 :		Ligne 1 :
	__NOTOC__		__NOTOC__
	==Overview==		==Overview==
	The Sage FRP 1000 for Cloud solution uses virtual ~~machine~~ (VM) to execute Sage FRP 1000 Services.		The Sage FRP 1000 for Cloud solution uses virtual machines (VM) to execute Sage FRP 1000 Services.

	In the Cloud model implemented on this solution, a VM execute '''one and only one''' Sage FRP 1000 Service.		In the Cloud model implemented on this solution, a VM execute '''one and only one''' Sage FRP 1000 Service.

Syfre : /* Virtual machine deployment process */

2017-02-03T07:38:47Z

Virtual machine deployment process

← Version précédente		Version du 3 février 2017 à 07:38
Ligne 34 :		Ligne 34 :

	==Virtual machine deployment process==		==Virtual machine deployment process==
	The virtual machines are deployed by the Provisioning ~~environment~~ (PDS).		The virtual machines are deployed by the Provisioning service (PDS).

	The PE uses the Azure resource manager, the template used to create a new VM include a script executed during the VM provisioning.		The PDS uses the Azure resource manager, the template used to create a new VM include a script executed during the VM provisioning.

	(This functionality is a [https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-classic-extensions-customscript custom script extension])		(This functionality is a [https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-classic-extensions-customscript custom script extension])

Syfre le 3 février 2017 à 07:36

2017-02-03T07:36:07Z

← Version précédente		Version du 3 février 2017 à 07:36
Ligne 34 :		Ligne 34 :

	==Virtual machine deployment process==		==Virtual machine deployment process==
	The virtual machines are deployed by the Provisioning environment (PE).		The virtual machines are deployed by the Provisioning environment (PDS).

	The PE uses the Azure resource manager, the template used to create a new VM include a script executed during the VM provisioning.		The PE uses the Azure resource manager, the template used to create a new VM include a script executed during the VM provisioning.
Ligne 41 :		Ligne 41 :

	This script realizes :		This script realizes :
	* Download of the last Sage FRP 1000 service binary package from an account storage blob of the PE.		* Download of the last Sage FRP 1000 service binary package from an account storage blob of the PDS.
	* Installation of the package		* Installation of the package
	* Create the service configuration file which contain the url on the ~~configuration server (PE)~~.		* Create the service configuration file which contain the url on the PDS.

	The service start up, read the configuration file and start the configuration sequence.		The service start up, read the configuration file and start the configuration sequence.

	==Virtual machine update==		==Virtual machine update==
	At the end of the configuration sequence, the PE can provide an update script to be executed.		At the end of the configuration sequence, the PDS can provide an update script to be executed.

	This script realizes :		This script realizes :
	* Download of the last Sage FRP 1000 binary package from an account storage blob of the PE.		* Download of the last Sage FRP 1000 binary package from an account storage blob of the PDS.
	* Stop the service		* Stop the service
	* Installation of the package		* Installation of the package

Syfre : /* Sage FRP 1000 start up process */

2017-02-03T07:33:23Z

Sage FRP 1000 start up process

← Version précédente		Version du 3 février 2017 à 07:33
Ligne 13 :		Ligne 13 :
	==Sage FRP 1000 start up process==		==Sage FRP 1000 start up process==

	In a stand alone configuration, a Sage FRP 1000 Service load its configuration from a local file. This start up process has several cons which prevent to use it a Cloud environment :		In a stand alone configuration, a Sage FRP 1000 Service (S1000) load its configuration from a local file. This start up process has several cons which prevent to use it a Cloud environment :

	* The configuration file must be provide on the local disk, this don't met the agnostic requirement		* The configuration file must be provide on the local disk, this don't met the agnostic requirement
	* The configuration contents sensitive information which may leaks if the VM is compromise.		* The configuration contents sensitive information which may leaks if the VM is compromise.

	For these reasons, the start up process in a Cloud environment has been replaced by a configuration sequence where the ~~Sage FRP 1000 Service~~ contacts the configuration server (~~PDA~~) to obtain its configuration file. As the ~~PDA~~ maintains a list of the existing VM with theire associat role it can provide the adequate configuration file.		For these reasons, the start up process in a Cloud environment has been replaced by a configuration sequence where the S1000 contacts the configuration server (PDS) to obtain its configuration file. As the PDS maintains a list of the existing VM with theire associat role it can provide the adequate configuration file.

	This approach has several benefices :		This approach has several benefices :
Ligne 26 :		Ligne 26 :
	* The VM has no sensitive information stored in its local storage		* The VM has no sensitive information stored in its local storage
	* The configuration may be updated with a centralized approach.		* The configuration may be updated with a centralized approach.

			The communication between the S1000 service and the PDS is protected :

			* The PDS identify the S1000 service by the DNS Name of VM.
			* The data returned by the PDS are encrypted by a 3Des master key shared by both the S1000 and the PDS.
			* The communication is over https.

	==Virtual machine deployment process==		==Virtual machine deployment process==

Syfre le 2 février 2017 à 16:54

2017-02-02T16:54:54Z

@@ Ligne 10 : / Ligne 10 : @@
 * Has no user access.
 * Is volatile.
 ==Virtual machine deployment process==
@@ Ligne 33 : / Ligne 49 : @@
 * Installation of the package
 * Restart the service
 == Front virtual machines ==

Syfre : /* Virtual machine deployment process */

2017-02-02T16:43:19Z

Virtual machine deployment process

← Version précédente		Version du 2 février 2017 à 16:43
Ligne 12 :		Ligne 12 :

	==Virtual machine deployment process==		==Virtual machine deployment process==
			The virtual machines are deployed by the Provisioning environment (PE).

			The PE uses the Azure resource manager, the template used to create a new VM include a script executed during the VM provisioning.

			(This functionality is a [https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-classic-extensions-customscript custom script extension])

			This script realizes :
			* Download of the last Sage FRP 1000 service binary package from an account storage blob of the PE.
			* Installation of the package
			* Create the service configuration file which contain the url on the configuration server (PE).

			The service start up, read the configuration file and start the configuration sequence.

			==Virtual machine update==
			At the end of the configuration sequence, the PE can provide an update script to be executed.

			This script realizes :
			* Download of the last Sage FRP 1000 binary package from an account storage blob of the PE.
			* Stop the service
			* Installation of the package
			* Restart the service

	==Sage FRP 1000 start up process==		==Sage FRP 1000 start up process==

Syfre : Page créée avec « NOTOC ==Overview== The Sage FRP 1000 for Cloud solution uses virtual machine (VM) to execute Sage FRP 1000 Services. In the Cloud model implemented on this solution, ... »

2017-02-02T15:26:01Z

Page créée avec « __NOTOC__ ==Overview== The Sage FRP 1000 for Cloud solution uses virtual machine (VM) to execute Sage FRP 1000 Services. In the Cloud model implemented on this solution, ... »

Nouvelle page

__NOTOC__
==Overview==
The Sage FRP 1000 for Cloud solution uses virtual machine (VM) to execute Sage FRP 1000 Services.

In the Cloud model implemented on this solution, a VM execute '''one and only one''' Sage FRP 1000 Service.

As general principles, a VM used in the Sage FRP 1000 Solution :

* Is agnostic.
* Has no user access.
* Is volatile.

==Virtual machine deployment process==

==Sage FRP 1000 start up process==

In a stand alone configuration, a Sage FRP 1000 Service load its configuration from a local file. This start up process has several cons which prevent to use it a Cloud environment :

* The configuration file must be provide on the local disk, this don't met the agnostic requirement
* The configuration contents sensitive information which may leaks if the VM is compromise.

For these reasons, the start up process in a Cloud environment has been replaced by a configuration sequence where the Sage FRP 1000 Service contacts the configuration server (PDA) to obtain its configuration file. As the PDA maintains a list of the existing VM with theire associat role it can provide the adequate configuration file.

This approach has several benefices :

* The VM is agnostic.
* The loading sequence is secure.
* The VM has no sensitive information stored in its local storage
* The configuration may be updated with a centralized approach.

== Front virtual machines ==

== Back virtual machines ==

[[Category:Cloud]]
[[Category:Architecture]]

Virtual machines (Cloud) - Historique des versions

Syfre le 7 février 2019 à 07:06

Syfre : /* Virtual machine deployment process */

Syfre : /* Sage FRP 1000 start up process */

Syfre : /* Overview */

Syfre : /* Virtual machine deployment process */

Syfre le 3 février 2017 à 07:36

Syfre : /* Sage FRP 1000 start up process */

Syfre le 2 février 2017 à 16:54

Syfre : /* Virtual machine deployment process */

Syfre : Page créée avec « __NOTOC__ ==Overview== The Sage FRP 1000 for Cloud solution uses virtual machine (VM) to execute Sage FRP 1000 Services. In the Cloud model implemented on this solution, ... »

Syfre : /* Virtual machine deployment process */

Syfre : /* Sage FRP 1000 start up process */

Syfre : /* Overview */

Syfre : /* Virtual machine deployment process */

Syfre : /* Sage FRP 1000 start up process */

Syfre : /* Virtual machine deployment process */

Syfre : Page créée avec « NOTOC ==Overview== The Sage FRP 1000 for Cloud solution uses virtual machine (VM) to execute Sage FRP 1000 Services. In the Cloud model implemented on this solution, ... »