If you are in the situation where you cannot delete a DRO from the UI you can go and delete it from the rails console. I had the following Dynamic Resource Object Definition: As you can see I have 2 instances. How do you delete these instances? With both the API calls as well Read more about Delete Dynamic Resource Object form CloudForms[…]
To round this up here a recording of smartstate in AWS with auto-remediation of a vulnerability (java) via policy and ansible inside.
This will be the last part of the blog series but probably the most interesting one. When you launch a smartstate analysis you will see the following in you evm log files.
|
1 2 3 4 5 6 7 8 |
[----] I, [2018-03-11T16:12:10.941498 #3004:4f7130] INFO -- : MIQ(ManageIQ::Providers::Amazon::CloudManager::Vm#raw_scan) NAME [Scan from Vm vmtosmartstate] SCAN [nil] [NilClass] [----] I, [2018-03-11T16:12:11.068516 #3004:4f7130] INFO -- : Job created: guid: [b0c7c318-2844-436c-bc44-21a29dfa3cce], userid: [admin], name: [Scan from Vm vmtosmartstate], target class: [VmOrTemplate], target id: [99000000000166], process type: [VmScan], server id: [], zone: [default] [----] I, [2018-03-11T16:12:15.868847 #3014:4f7130] INFO -- : MIQ(MiqQueue.put) Message id: [99000000000427], id: [], Zone: [default], Role: [smartstate], Server: [], Ident: [generic], Target id: [], Instance id: [], Task id: [job_dispatcher], Command: [JobProxyDispatcher.dispatch], Timeout: [600], Priority: [20], State: [ready], Deliver On: [], Data: [], Args: [] [----] I, [2018-03-11T16:12:21.133242 #3004:4f7130] INFO -- : MIQ(MiqPriorityWorker::Runner#get_message_via_drb) Message id: [99000000000427], MiqWorker id: [99000000000004], Zone: [default], Role: [smartstate], Server: [], Ident: [generic], Target id: [], Instance id: [], Task id: [job_dispatcher], Command: [JobProxyDispatcher.dispatch], Timeout: [600], Priority: [20], State: [dequeue], Deliver On: [], Data: [], Args: [], Dequeued in: [5.266320951] seconds [----] I, [2018-03-11T16:13:05.374585 #3424:4f7130] INFO -- : MIQ(ManageIQ::Providers::Amazon::AgentCoordinator#find_or_create_keypair) KeyPair smartstate-2ae1670a-2fcc-4bbb-abcc-3fa962895096 will be created! [----] I, [2018-03-11T16:13:05.877668 #3424:4f7130] INFO -- : MIQ(ManageIQ::Providers::Amazon::AgentCoordinator#deploy_agent) Smartstate agent will be deployed in vpc: [vpc-076ad862], zone: [us-east-1a] subnet: [subnet-3cc6154b] [----] I, [2018-03-11T16:13:11.145451 #3424:4f7130] INFO -- : MIQ(ManageIQ::Providers::Amazon::AgentCoordinator#get_agent_image_id) AMI Image: RHEL-Atomic_7.4_HVM_GA-20180104-x86_64-1-Access2-GP2 [ami-d97120a3] is used to launch smartstate agent. [----] I, [2018-03-11T16:15:55.976224 #2716:4f7130] INFO -- : MiqServer: local=Y, master=Y, status= started, id=99000000000001, pid=02716, guid=c5b77187-7fc9-426e-b3cb-6f0ce7860c8e, name=EVM, zone=default, hostname=ip-172-31-44-62.ec2.internal, ipaddress=172.31.44.62, version=5.9.0.22, build=20180221205805_f93a675, active roles=automate:database_operations:datab |
There are a few interesting parts here. What is the AgentCoordinator? The code can be found here: /opt/rh/cfme-gemset/bundler/gems/manageiq-providers-amazon-9620e26f4381/app/models/manageiq/providers/amazon/agent_coordinator.rb . Its out of scope Read more about CloudForms in AWS part 3[…]
This part of the CloudForms in AWS blog series will walk you through how to make sure that CloudForms reaches its full potential in AWS. IMPORTANT: If you want SmartState analysis to work you need to register your AWS account with the cloud access program. Use the link below to enable cloud access: https://engage.redhat.com/forms/cloud-access-registration Once Read more about CloudForms in AWS part 2[…]
Ever wondered what CloudForms can do for you in AWS? The next few blog posts will walk you through step by step how to upload the CloudForms image to AWS, how to assign the correct policies and roles and how to configure it correctly so it can discover your environment. Part 1 is dedicated to Read more about CloudForms in AWS part 1[…]
Part 2 is going to show you how you can run the catalog item created in Part 1 from a custom button. Go to Automation – Automate – Customization – Buttons. Click on Cluster / Deployment role and create a new Button Group Now click on Configuration – Add New Button and add the following Read more about CloudForms 4.5 RHV 4.1 Management by Ansible Automation Inside (Part 2 Create a Button)[…]
This post will explain what steps you need to go through to enable the ansible management of RHV on the first release of CFME 4.5. I assume that you’ve already enabled the Embedded Ansible role in Configuration – Server Control (enabling ansible automation inside can take up to 7-10 minutes) . CloudForms 4.5 comes with Read more about CloudForms 4.5 RHV 4.1 Management by Ansible Automation Inside (Part 1 Create Service Dialog)[…]
I was speaking at the “IT Modernization with Open Management and Containers” event in Rochester, NY June 14th. The talk was covering how you can embrace cloud get insights into the different players like AWS, GCP, Azure and manage your instances and services through the CloudForms Management Engine. Here are the slides to the presentation:
Red Hat Summit is already over. There was an unbelievable energy during the 4 days of the Summit. If you were not able to make it to our session S102320 – Button push deployments with integrated Red Hat Management you can review it now: The demo can be found here:
So here we are again. In less then a week I will be speaking again at Red Hat Summit. Last year I showed how you can deploy multi-tier multi-host applications across AWS, GCP, Azure and RHV with CloudForms, Satellite6 and Ansible Tower. A year went by but requests from customers wanting to testdrive the power Read more about Red Hat Summit 2017 Button Push Deployments With Integrated Red Hat Open Management DEMO[…]
