Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:00
From version 23.1
edited by Erik Bakker
on 2022/12/22 13:40
Change comment: There is no comment for this version
To version 24.1
edited by Erik Bakker
on 2022/12/22 13:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,11 +17,7 @@
17 17  
18 18  === 3.1 T-Shirt sizing in eMagiz ===
19 19  
20 -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:
21 -S * 2 Gb
22 -M * 4Gb
23 -L * 8Gb
24 -XL * 16Gb
20 +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 XXL. Each of these sizes corresponds to a specific machine specification where by the memory is the most import to note.
25 25  
26 26  [[image:Main.Images.Microlearning.WebHome@advanced-cloudmanagement-change-sizing-cloud-1.png]]
27 27  
... ... @@ -36,11 +36,13 @@
36 36  
37 37  [[image:Main.Images.Microlearning.WebHome@advanced-cloudmanagement-change-sizing-cloud-2.png]]
38 38  
35 +{{warning}}Note that we currently do not offer any cloud machines anymore with a t-shirt size above XL. Therefore your partner manager will never approve any proposed machine sizing of XXL.{{/warning}}
36 +
39 39  === 3.2 Changing the size considerations ===
40 40  
41 -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.
39 +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 this via Deploy Architecture.
42 42  
43 -However, the Cloud approval is a step that needs to be taken first and can only happen when the licensing agreement has been altered for that purpose. Please contact you partner manager to arrange such Cloud approvals. Bigger size machines will not be effectuated in Deploy Architecture.
41 +Before you can do so cloud approval is needed.This can only happen when the licensing agreement has been altered for that purpose. Please contact you partner manager to arrange such Cloud approvals.
44 44  
45 45  == 4. Assignment ==
46 46  
... ... @@ -54,8 +54,11 @@
54 54  
55 55  == 6. Suggested Additional Readings ==
56 56  
57 -If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz
55 +If you are interested in this topic and want more information on it, please read the following microlearnings.
58 58  
57 +* [[eMagiz Cloud Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-event-streaming-introduction||target="blank"]]
58 +* [[Consequences of cloud size changes and cloud approval>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.advanced-solution-architecture-consequence-size-cloud||target="blank"]]
59 +
59 59  == 7. Silent demonstration video ==
60 60  
61 61  There is no video available as this is more a theoretical microlearning.)))((({{toc/}}))){{/container}}{{/container}}