Deploy rpc-maas on OSP17 #753
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Fix install doc to use correct DDI for the maas_api_url - Fix openmanage.py for python3
Fixing python3 issue for nfs_check.py (cherry picked from commit 3059a03)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I managed to deploy MAAS in the environment to completion in RHOSP17 environment. A few checks are failing(cinder-volume, neutron, ironic, private_lb) need to be checked. We can raise separate Jira's to address the failures for individual checks which are failing.
I have validated the installation on OSP setup. But, couldn't validate on OSA as I dont have the environment
The
maas_notification_plan: npManagedcheck fails(seems due to lack of core ID's), so I proceeded withnpTechnicalContactsEmail.