-
Notifications
You must be signed in to change notification settings - Fork 8
feat: move agents to new tiles #460
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
Conversation
ocofaigh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jor2 See comments. Ill create the new offering once they are addressed, as need the update in the catalog json first
ocofaigh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See latest comments
ocofaigh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See latest comments. I'm also running the catalog pipeline against this branch now to make sure all the scripts etc work ok
ocofaigh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect you need to run chmod +x on the validation script, as they failed in the pipeline run attempt:
Executing pre-validation..
./catalog-onboard.sh: line 1067: tests/scripts/pre-validation-deploy-slz-roks-and-obs-instances.sh: No such file or directory
|
@jor2 Still a permissions issue on the script: |
|
investigate failure: 2025/02/24 20:18:18 �[1m----- New Workspace Action -----�[21m�[0m
2025/02/24 20:18:18 Request: activitId=69826159058d3debf275f9dd9de8874b, account=abac0df06b644a9cabc6e44f55b3880e, owner=GoldenEye.Development@ibm.com, requestID=409c489d-800c-4515-a615-d67a34b1a05f
2025/02/24 20:18:19 Related Activity: action=TERRAFORM_COMMANDS, workspaceID=us-east.workspace.globalcatalog-collection.e88c7dd5, processedBy=orchestrator-6cb446ddb7-gx9wh
2025/02/24 20:18:19 Related Workspace: name=deploy-arch-ibm-observability-agents-02-24-2025, sourcerelease=(not specified), sourceurl=, folder=terraform-ibm-modules-terraform-ibm-observability-agents-e7c9f65/solutions/baseline
2025/02/24 20:18:22 --- Ready to execute the command ---
2025/02/24 20:18:24 Failed to download from object storage, cannot store downloaded file: open /tmp/deploy-arch-ibm-observability-agents-02-24-20251108998317/terraform-ibm-modules-terraform-ibm-observability-agents-e7c9f65/solutions/baseline/schematics.tfvars: no such file or directory
2025/02/24 20:18:24 �[1m�[31mCould not fetch varibles from object store 009f8e24-b92a-4103-9f77-9f686e4e6d33, err: cannot store downloaded file: open /tmp/deploy-arch-ibm-observability-agents-02-24-20251108998317/terraform-ibm-modules-terraform-ibm-observability-agents-e7c9f65/solutions/baseline/schematics.tfvars: no such file or directory�[39m�[0m
2025/02/24 20:18:24 �[1m�[31mThere was an internal Error. Please verify the resources and retry after some time.�[39m�[0m |
|
@jor2 That error happens because the branch I used to import the temporary version for testing has since been updated. Any time you add a new commit, I need to re-import. Ill clean up now and re-run |
|
Actually @jor2 please resolve conflicts |
ocofaigh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jor2 See latest comments. Also perhaps remove Existing VPC layer from the diagram. The DA should work on classic clusters too
ibm_catalog.json
Outdated
| "key": "cloud_monitoring_instance_region", | ||
| "display_name": "Region", | ||
| "custom_config": { | ||
| "type": "vpc_region", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cloud Monitoring may support different regions to VPC - I think we need to add a custom dropdown for this whuch only lists supported Cloud Monitoring regions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
monitoring available in every region. what should i do here? how do i create or view the list of already existing custom configs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jor2 You will need to create your own dropdown list which only lists the regions that cloud monitoring is supported (same syntax as this https://github.com/terraform-ibm-modules/terraform-ibm-event-notifications/blob/564e73a43888d6fab2fd5706360a11167e8abd48/ibm_catalog.json#L74-L97)
solutions/baseline/variables.tf
Outdated
| type = string | ||
| name = string | ||
| })) | ||
| description = "To filter on custom metrics, specify the IBM Cloud Monitoring metrics to include or exclude. [Learn more](https://cloud.ibm.com/docs/monitoring?topic=monitoring-change_kube_agent#change_kube_agent_inc_exc_metrics)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a complex input - it will need a markdown supporting doc
|
@ocofaigh what do i do if plan passes and cost fails? |
|
/run pipeline |
ocofaigh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jor2 you are going to need to update the version of landing zone to the latest in tests/resources/main.tf or the cluster will get into a bad state and agent deploy will fail (this is what happened in Observability DA).
Also I still need to do a final review, so hold off triggering pipeline
ocofaigh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jor2 Since we are breaking Cloud Logs and Monitoring into new their own DAs, we will also need to split the agents into their own repos / DAs. Can you split the work you have done so they go into these new repos?


Description
https://github.ibm.com/GoldenEye/issues/issues/11710
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers