Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] provide customer specific placeholder playbook in configuration_menu.sh before Base OS Config #20

Open
enterprise-1701-d opened this issue Dec 30, 2021 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@enterprise-1701-d
Copy link

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

  1. Base OS Config
  2. SAP specific OS Config
  3. 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

  • name: Register SuseConnect
    command: "SUSEConnect -r -e "
    args:
    creates: "/etc/zypp/credentials.d/SCCcredentials"
    tags:
    • deployment

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.

@enterprise-1701-d enterprise-1701-d added the enhancement New feature or request label Dec 30, 2021
@mimergel
Copy link
Contributor

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.

@sapien47
Copy link

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.

Thanks

@PmeshramPM
Copy link
Collaborator

@mimergel - could we please check if this can be closed ?

@hdamecharla
Copy link
Member

The extensibility portion of the framework is now live in the latest release.

You can create a playbook with custom tasks to extend the framework.

The playbooks should be in the workspaces repo under Ansible folder, suffixed by _pre and _post.

Please see below image for more information.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants