P2 Create Solution Template Blades correctly #36
Comments
|
Heads up - this issue was moved between project columns. cc @VarunChopraAccolite, @ashutosh-kumar1 |
VarunChopraAccolite
assigned venkateshramagiri and pratap-accolite and unassigned venkateshramagiri
|
Add remaining parameters in {
"Virtual Machine Settings blade" => "Virtual Machine blade"
"Database Settings Blade" => "Database blade"
"Application Gateway Blade"
"applicationGatewaySkuTier": {
"type": "string",
"allowedValues": [
"Standard",
"WAF"
],
"defaultValue": "Standard",
"metadata": {
"description": "Application Gateway SKU Tier"
}
},
"applicationGatewaySkuName": {
"type": "string",
"allowedValues": [
"Standard_Small",
"Standard_Medium",
"Standard_Large",
"WAF_Medium",
"WAF_Large",
"WAF_v2"
],
"defaultValue": "Standard_Medium",
"metadata": {
"description": "Application Gateway SKU Name"
}
},
"applicationGatewayCapacity": {
"type": "int",
"defaultValue": 2,
"metadata": {
"description": "Number of Application Gateway instances"
}
},
"Database Blade"
"collation": {
"type": "string",
"defaultValue": "SQL_Latin1_General_CP1_CI_AS",
"metadata": {
"description": "New DB. The new database collation for governing the proper use of characters."
}
},
"edition": {
"type": "string",
"defaultValue": "Standard",
"allowedValues": [
"Basic",
"Standard",
"Premium"
],
"metadata": {
"description": "New DB. The type of database to create."
}
},
"requestedServiceObjectiveName": {
"type": "string",
"defaultValue": "S2",
"allowedValues": [
"Basic",
"S0",
"S1",
"S2",
"S3",
"S4",
"S6",
"S7",
"S9",
"S12",
"P1",
"P2",
"P4",
"P6",
"P11",
"P15"
],
"metadata": {
"description": "New DB. Describes the performance level for Edition"
}
},
"maxSizeBytes": {
"type": "string",
"defaultValue": "1073741824",
"metadata": {
"description": "New DB. The maximum size, in bytes, for the new database"
}
},
"Virtual Machine Blade"
"webServerMaxConnect": {
"type": "string",
"defaultValue": "20",
"metadata": {
"description": "The maximum number of LANSA jobs to run on each Web Server. Setting triggerWebConfig will cause this value to be updated."
}
},
"Installation Options Blade"
"installMSI": {
"type": "string",
"defaultValue": "0",
"metadata": {
"description": "Install the MSI: Set this to 1 to execute an MSI install. Usually set to 0 when updating the stack"
}
},
"updateMSI": {
"type": "string",
"defaultValue": "0",
"metadata": {
"description": "Update Stack: Set this to 1 to execute an MSI Upgrade. Obtains the specified MSI and installs it. Ensure the LansaMSI parameter is set correctly. If the LansaMSI parameter is not different a repair will be performed"
}
},
"uninstallMSI": {
"type": "string",
"defaultValue": "0",
"metadata": {
"description": "Uninstall the MSI: Set this to 1 to uninstall the MSI. The MSI used to uninstall, is the last one that was installed. It is called c:\\lansa\\MyApp.msi"
}
},
"triggerWebConfig": {
"type": "string",
"defaultValue": "0",
"metadata": {
"description": "Update Stack: Set this to 1 to update the web configuration"
}
},
"gitBranch": {
"type": "string",
"defaultValue": "support/L4W14200_scalable",
"metadata": {
"description": "Git Branch"
}
},
"trace": {
"type": "string",
"defaultValue": "N",
"allowedValues": [
"Y",
"N"
],
"metadata": {
"description": "Switch tracing on. Allowed values Y or N"
}
},
"fixLicense": {
"type": "string",
"defaultValue": "0",
"metadata": {
"description": "Re-run licensing. It is unlikely that this parameter needs to be used"
}
}
} |
|
Security Blade feedback |
|
Stack Name - length 9. alphabetic plus '-'. (No numerics. No special chars. No space) All UID/passwords, no space |
|
Thanks for the inputs @robe070. |
|
Here is |
|
Actually, I wonder whether all VM sizes are listed if |
|
Yes, @robe070. It shows all the possible VM sizes and fades out the ones that are not available for the subscription/location. I have implemented and pushed the changes in the PR. Please review and let me know if anything else is required. |
|
I'm glad that worked. Looks good. I notice there are properties for the count & SKU too. Please add this: |
|
This parameter should only appear for |
|
@robe070, All the above mentioned changes are incorporated. Are there more changes required as a part of this issue? |
|
Heads up - this issue was moved between project columns. cc @VarunChopraAccolite, @ashutosh-kumar1, @pratap-accolite |
|
Azure Support have identified the issue with custom parameters being drawn at the top of the Basic blade - you have been using the incorrect tool. This is the correct tool: https://portal.azure.com/?feature.customPortal=false#blade/Microsoft_Azure_CreateUIDef/SandboxBlade So, we need to re-arrange the parameters a little the way that I originally intended. These 3 fields to be moved to the Basic blade:
And the whole of the Virtual Machine blade moved to Basic. This may be too much for the Basic blade so I'll need to review how it looks:
|
|
Hi @robe070, I would also like to add that I was successfully able to validate the template by reaching the review+create screen but I can see some yellow lines in my VS code. Hope it should not be an issue. |
|
@ashutosh-kumar1 |
|
@robe070, Also, verify the position of minimum instance count above the VM sizes. This is because I was getting an error on console when I placed it below the VM sizes. This may be caused as the VM size is dependent upon its value. |
|
@ashutosh-kumar1 |
|
No. @robe070, can you guide me on how to verify it in the Azure Portal? |
|
I cannot find a way to verify it apart from this Sandbox, the ARM TTK and thence once its in Preview running in the Portal. Have you run the ARM TTK? |
|
I've reconsidered after seeing your screen NOT show the Virtual Machine parameters, and the error you are seeing. Please reinstate the Virtual Machine blade. But leave the Stack Name, LANSA Version and MSI URL on the Basics blade. |
|
ps I have an ongoing Azure support query to clarify how a Solution Template may be run entirely from the command line. |
|
ARM TTK is running successfully for both the positions of minimum instance count. Also, the template is returning proper JSON. I think the console error can be ignored.
|
As per my screen resolution, yes the other parameters are not visible and need to be scrolled to edit. |
|
@ashutosh-kumar1 I think you should commit it with everything on the Basics blade, and I'll see how it looks on various monitor sizes. |
|
...becasue the Sandbox may be using less screen than when its running in the Portal |
|
Sure @robe070. Let me commit it as VM parameters in the Basic blade. Please verify in the preview phase and provide me feedback for changes required. |
|
@ashutosh-kumar1 |
|
@robe070, PR submitted. Please review and merge. Validations might fail in pipeline for now as the newly added test image version task is failing. Please approve. |
|
@ashutosh-kumar1 |
|
@ashutosh-kumar1 |
|
@ashutosh-kumar1 |
|
@ashutosh-kumar1 |
|
@robe070, Just saw your message. Was out for lunch. Sorry about that. Thanks for submitting the zip. Please update me if any changes are required post verification. |
|
Heads up - this issue was moved between project columns. cc @VarunChopraAccolite, @ashutosh-kumar1, @pratap-accolite |
|
@robe070, Awaiting feedback for any further required changes. |
|
@ashutosh-kumar1 Mispelling Move these parameters to the bottom of the Database blade: |
|
@robe070, PR is raised for the above-mentioned changes. Please review and merge: lansa/azure-quickstart-templates#13 |
|
Heads up - this issue was moved between project columns. cc @VarunChopraAccolite, @ashutosh-kumar1, @pratap-accolite |
This is the third part of producing the new Solution Template, final submission. The new UI interface blades.
The sequence of events around creating the Solution Template are summarised below
#24 describes the UI process at a high level, requiring Architect involvement in what parameters will be on what blades.
The text was updated successfully, but these errors were encountered: