You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I need to use BYOS images and therefore they have to be registered first with SUSE or RedHat
Describe the solution you'd like
I would like to have a Step "0) Customer specific Preparations" where I could include the registration of all VMs based on the generated hosts file
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/configuration_menu.sh
0) Customer specific Preparations
Base OS Config
SAP specific OS Config
BOM Processing
Describe alternatives you've considered
well I used an own playbook to register the systems with SUSE in my particular case and than started with step 1)
Additional context
Add any other context or screenshots about the feature request here.
here is my task I added to the playbook_01
suse-register.yml
Well of course the credentials could be in a key vault - asking interactively or prepare it similar to the S-User keyvault entries
Problem DB-Hosts were not able to register to SUSE, but APP-Servers ware able. I think it might be some NSG-Rule or something, which prevents access to the internet.
The text was updated successfully, but these errors were encountered:
Hi, if you deployed without firewall then HDB and SCS won't have access to the repository server due to their load balancers being deployer per default. The nw communication blocks due to the missing FW. In that case pls disable LBs during deployments:
Set this in the SYSTEM tfvars file:
use_loadbalancers_for_standalone_deployments=false
Afterwards all VMs can connect.
Hope this helps and thanks for the suggestion to have a placeholder playbook where customer specific tasks can be added.
Had the same issue, I attached a NAT gateway to allow the SUSE Registration.
As for the possibility to register your BYOS Linux licenses, I second that.
Most of your customers are coming from SAP on Premises, where they already own licenses.
Is your feature request related to a problem? Please describe.
I need to use BYOS images and therefore they have to be registered first with SUSE or RedHat
Describe the solution you'd like
I would like to have a Step "0) Customer specific Preparations" where I could include the registration of all VMs based on the generated hosts file
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/configuration_menu.sh
0) Customer specific Preparations
Describe alternatives you've considered
well I used an own playbook to register the systems with SUSE in my particular case and than started with step 1)
Additional context
Add any other context or screenshots about the feature request here.
here is my task I added to the playbook_01
suse-register.yml
command: "SUSEConnect -r -e "
args:
creates: "/etc/zypp/credentials.d/SCCcredentials"
tags:
Well of course the credentials could be in a key vault - asking interactively or prepare it similar to the S-User keyvault entries
Problem DB-Hosts were not able to register to SUSE, but APP-Servers ware able. I think it might be some NSG-Rule or something, which prevents access to the internet.
The text was updated successfully, but these errors were encountered: