Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:00
From version 18.1
edited by Erik Bakker
on 2022/06/13 09:10
Change comment: Deleted image "advanced-cloudmanagement-change-sizing-cloud-2.png"
To version 27.1
edited by Erik Bakker
on 2023/10/26 10:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 - Change the size of the eMagiz Cloud
1 +Change the size of the eMagiz Cloud
Content
... ... @@ -3,68 +3,52 @@
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 -* Last update: November 2nd, 2021
7 -* Required reading time: 5 minutes
8 -
9 9  == 1. Prerequisites ==
10 10  
11 11  * Advanced knowledge of the eMagiz platform
12 12  * Completed the relevant microlearnings around Cloud Management till advanced
13 -* Read the microlearning around the determing the required size of a machine in this [microlearning](expert-solution-architecture-determining-needed-memory.md)
10 +* Read the microlearning around determining the required size of a machine in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory.WebHome||target="blank"]].
14 14  
15 15  == 2. Key concepts ==
16 16  
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.
14 +With the eMagiz Cloud, we mean the specific Cloud slot made available for an integration model so that the flows from that model can be deployed to become operational. The Cloud is a Virtual Private Cloud (VPC) that is only available for that integration model and is appropriately secured. In that VPC, a series of 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 ====
18 +=== 3.1 T-Shirt sizing in eMagiz ===
24 24  
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 -S * 2 Gb
27 -M * 4Gb
28 -L * 8Gb
29 -XL * 16Gb
20 +eMagiz provides a means to assess whether the current Cloud configuration is sufficient. In the figure below, you can see the eMagiz Cloud machines denoted with green boxes. On the top of each box, you will find a T-shirt size indication ranging from S to XXL. Each size corresponds to a specific machine specification where the memory is the most important to note.
30 30  
31 31  [[image:Main.Images.Microlearning.WebHome@advanced-cloudmanagement-change-sizing-cloud-1.png]]
32 32  
33 33  **Advised size**
34 -The first T-shirt size in the box * white background - is the recommended sizing that eMagiz advices. This is based on the average memory consumption guideline that is explained in the microlearning as mentioned above. In the check size option available via the right click, you will find the sizing estimate for that machine and the reference based on flows. In the example above, an M is recommended for both.
25 +The first T-shirt size in the box * white background - is the recommended sizing that eMagiz advises. This is based on the average memory consumption guideline explained in the microlearning mentioned above. In the check size option available via the right click, you will find the sizing estimate for that machine and the reference based on flows. In the example above, an M is recommended for both.
35 35  
36 36  **Actual size**
37 -The second T-shirt size in the box * green background - is the actual machine size that is used for the Deployment phase. This is something that the user can select and using the toggle while editing the architecture can influence. In the example above an L and an S are configured.
28 +The second T-shirt size in the box * green background - is the machine size used for the Deployment phase. This is something that the user can select, and using the toggle while editing the architecture can influence it. In the example above, an L and an S are configured.
38 38  
39 39  **Approved size**
40 -In the right-hand size, bottom, you will find the overview of the total machines allows according to your contract. This option can only be set by eMagiz administrators and will only be changed based on actual license agreements
31 +In the panel on the right, towards the bottom, you will find the overview of the total machines allowed according to your contract. This option can only be set by eMagiz administrators and will only be changed based on actual license agreements.
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 ====
35 +{{warning}}Note that we currently do not offer cloud machines with a t-shirt size above XL. Therefore, your partner manager will never approve any proposed machine sizing of XXL.{{/warning}}
45 45  
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.
37 +=== 3.2 Changing the size considerations ===
47 47  
48 -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.
39 +If 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.
49 49  
41 +Before you can do so, cloud approval is needed. This can only happen when the licensing agreement has been altered. Please get in touch with your partner manager to arrange such Cloud approvals.
50 50  
43 +== 4. Key takeaways ==
51 51  
52 -== 4. Assignment ==
53 -
54 -Ensure to you your environment to locate the toggle properly, find the overview bottom right to see the Cloud approvals. Check the sizing status once more.
55 -
56 -== 5. Key takeaways ==
57 -
58 58  * Keep the Cloud sizing the same as the recommended size
59 -* Check the size regularly to anticipate sizing changes in a timely manner. Use the check size options
60 -* Validate the architecture with colleagues or ask a review by eMagiz Expert Services.
46 +* Check the size regularly to anticipate sizing changes on time. Use the check size options
47 +* Validate the architecture with colleagues or ask for a review by eMagiz Expert Services.
61 61  
49 +== 5. Suggested Additional Readings ==
62 62  
51 +If you are interested in this topic and want more information, please read the following microlearnings.
63 63  
64 -== 6. Suggested Additional Readings ==
65 -
66 -If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz
67 -
68 -== 7. Silent demonstration video ==
69 -
70 -There is no video available as this is more a theoretical microlearning.)))((({{toc/}}))){{/container}}{{/container}}
53 +* [[eMagiz Cloud Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-event-streaming-introduction||target="blank"]]
54 +* [[Consequences of cloud size changes and cloud approval>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.advanced-solution-architecture-consequence-size-cloud.WebHome||target="blank"]])))((({{toc/}}))){{/container}}{{/container}}