Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:00
From version 11.1
edited by eMagiz
on 2022/05/05 10:00
Change comment: There is no comment for this version
To version 12.1
edited by eMagiz
on 2022/05/05 10:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,20 +1,12 @@
1 1  {{html wiki="true"}}
2 2  <div class="ez-academy">
3 3   <div class="ez-academy_body">
4 -
5 -
6 - <li class="doc-nav__item"><a href="../../docs/microlearning/advanced-cloudmanagement-index" class="doc-nav__link">Home</a></li>
7 -
8 -
9 -
10 -
11 -
12 12  <div class="doc">
13 13  
14 14  
15 15  
16 16  = Change the size of the eMagiz Cloud =
17 -
9 +
18 18  In this microlearning, we will discuss how to change the size of the eMagiz Cloud.
19 19  
20 20  Should you have any questions, please get in touch with academy@emagiz.com.
... ... @@ -22,14 +22,14 @@
22 22  * Last update: November 2nd, 2021
23 23  * Required reading time: 5 minutes
24 24  
25 -
26 26  == 1. Prerequisites ==
18 +
27 27  * Advanced knowledge of the eMagiz platform
28 28  * Completed the relevant microlearnings around Cloud Management till advanced
29 29  * Read the microlearning around the determing the required size of a machine in this [microlearning](expert-solution-architecture-determining-needed-memory.md)
30 30  
31 -
32 32  == 2. Key concepts ==
24 +
33 33  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.
34 34  
35 35  
... ... @@ -37,6 +37,7 @@
37 37  == 3. Changing the size of the eMagiz Cloud ==
38 38  
39 39  ==== 3.1 T-Shirt sizing in eMagiz ====
32 +
40 40  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:
41 41  S * 2 Gb
42 42  M * 4Gb
... ... @@ -58,11 +58,10 @@
58 58  
59 59  ==== 3.2 Changing the size considerations ====
60 60  
61 -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.
54 +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.
62 62  
63 63  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.
64 64  
65 -
66 66  ===== Practice =====
67 67  
68 68  == 4. Assignment ==
... ... @@ -89,4 +89,5 @@
89 89  </main>
90 90  </div>
91 91  </div>
84 +
92 92  {{/html}}