Changes for page Change the size of the eMagiz Cloud
Last modified by Erik Bakker on 2024/09/03 08:00
From version 26.1
edited by Erik Bakker
on 2023/10/17 12:12
on 2023/10/17 12:12
Change comment:
There is no comment for this version
To version 27.1
edited by Erik Bakker
on 2023/10/26 10:04
on 2023/10/26 10:04
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -7,48 +7,48 @@ 7 7 8 8 * Advanced knowledge of the eMagiz platform 9 9 * Completed the relevant microlearnings around Cloud Management till advanced 10 -* Read the microlearning around thedeterming 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"]]. 11 11 12 12 == 2. Key concepts == 13 13 14 -With the eMagiz Cloud we mean the specific Cloud slot that ismade available for an integration model so that the flows from that model can be deployedandmade operational. The Cloud is a Virtual Private Cloud (VPC) that is only available for that integration model and issecuredproperly. In that VPC a series of 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. 15 15 16 16 == 3. Changing the size of the eMagiz Cloud == 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 withthegreen boxes. On the top of each box you will find a T-shirt size indication ranging from S to XXL. Eachof these sizescorresponds to a specific machine specification wherebythe memory is the most import to note.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. 21 21 22 22 [[image:Main.Images.Microlearning.WebHome@advanced-cloudmanagement-change-sizing-cloud-1.png]] 23 23 24 24 **Advised size** 25 -The first T-shirt size in the box * white background - is the recommended sizing that eMagiz advi ces. This is based on the average memory consumption guidelinethat isexplained in the microlearningasmentioned 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. 26 26 27 27 **Actual size** 28 -The second T-shirt size in the box * green background - is the actualmachine sizethat isused 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. 29 29 30 30 **Approved size** 31 -In the right -handize,bottom, you will find the overview of the total machines allowsaccording to your contract. This option can only be set by eMagiz administrators and will only be changed based on actual license agreements31 +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. 32 32 33 33 [[image:Main.Images.Microlearning.WebHome@advanced-cloudmanagement-change-sizing-cloud-2.png]] 34 34 35 -{{warning}}Note that we currently do not offer anycloud machinesanymorewith a t-shirt size above XL. Therefore your partner manager will never approve any proposed machine sizing of XXL.{{/warning}}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}} 36 36 37 37 === 3.2 Changing the size considerations === 38 38 39 -I ncaseaspecific machine is overloaded39 +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. 40 40 41 -Before you can do so cloud approval is needed.This can only happen when the licensing agreement has been altered for that purpose. Pleasecontact you partner manager to arrange such Cloud approvals.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. 42 42 43 43 == 4. Key takeaways == 44 44 45 45 * Keep the Cloud sizing the same as the recommended size 46 -* Check the size regularly to anticipate sizing changes inatimely manner. Use the check size options47 -* 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. 48 48 49 49 == 5. Suggested Additional Readings == 50 50 51 -If you are interested in this topic and want more information on it, please read the following microlearnings.51 +If you are interested in this topic and want more information, please read the following microlearnings. 52 52 53 53 * [[eMagiz Cloud Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-event-streaming-introduction||target="blank"]] 54 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}}