Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:00
From version 18.2
edited by Erik Bakker
on 2022/06/13 09:11
Change comment: Update document after refactoring.
To version 19.1
edited by Erik Bakker
on 2022/06/13 09:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,11 +16,9 @@
16 16  
17 17  With the eMagiz Cloud we mean the specific Cloud slot that is made available for an integration model so that the flows from that model can be deployed and made operational. The Cloud is a Virtual Private Cloud (VPC) is only available for that integration model and is secured properly. In that VPC a series interconnected machines are running.
18 18  
19 -
20 -
21 21  == 3. Changing the size of the eMagiz Cloud ==
22 22  
23 -==== 3.1 T-Shirt sizing in eMagiz ====
21 +=== 3.1 T-Shirt sizing in eMagiz ===
24 24  
25 25  eMagiz provides a mean to assess whether the current Cloud configuration is sufficient or not. In the figure below you can see the eMagiz Cloud machines denoted with the green boxes. On the top of each box you will find a T-shirt size indication ranging from S to XL. Each of these sizes corresponds to a specific machine specification where by the memory is the most import to note:
26 26  S * 2 Gb
... ... @@ -41,7 +41,7 @@
41 41  
42 42  [[image:Main.Images.Microlearning.WebHome@advanced-cloudmanagement-change-sizing-cloud-2.png]]
43 43  
44 -==== 3.2 Changing the size considerations ====
42 +=== 3.2 Changing the size considerations ===
45 45  
46 46  In case a specific machine is overloaded / overcommitted, it is time to change the size of that machine. You can toggle to a higher size machine and effectuate in the Deploy Architecture * please check out the relevant microlearnings for that.
47 47