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

[RFE] SmartState Analysis using Ansible and not the built-in approach #84

Open
tjyang opened this issue Nov 29, 2018 · 5 comments
Open

Comments

@tjyang
Copy link

tjyang commented Nov 29, 2018

  • WHAT:
    • Freezing an VM to get a snaphot for SSA to analysis is resource expensive.
    • I am getting resistance from VM farm admins to do SSA on their VMs
    • MIQ SSA should support lighter approach of collecting same info via ssh(ansible ?) to each VM/Host.
  • WHY:
    • So that MIQ provider connection will be more welcomed by VM farm admin.
  • HOW: Provide following extra data channels beside using snapshot.
    • Adding direct ssh connection to collect OS info.
    • Getting OS info from Ansible Tower/AWX miq provider.
    • Getting more system info (actual disk space usage) from existing provider connection.
@jerryk55
Copy link
Member

jerryk55 commented Nov 29, 2018

@tjyang I might point out that one of the major advantages of SSA of VMs/Instances/Images via Snapshot is they do not need to be running. As a matter of fact Images would not be running regardless. ssh only works with running VMs/Instances. A second advantage, in the case that the VM is actually running, is that scanning the Snapshot puts zero performance impact on the running VM, since you are not actually connecting to it to execute anything. Just my 2 cents, off the top of my head. There is more, of course....

@tjyang
Copy link
Author

tjyang commented Nov 29, 2018

@jerryk55

Thanks for the comment.

I am hoping SSA can be executed across physical/virtual hosts since MIQ is not just CMP(Cloud Management Platform) tool anymore.

@miq-bot
Copy link
Member

miq-bot commented Aug 26, 2019

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

@Fryguy Fryguy changed the title [RFE] SmartState Analysis to support non-snapshot approach [RFE] SmartState Analysis without using Ansible and not the built-in approach Nov 21, 2019
@Fryguy Fryguy changed the title [RFE] SmartState Analysis without using Ansible and not the built-in approach [RFE] SmartState Analysis using Ansible and not the built-in approach Nov 21, 2019
@miq-bot miq-bot added the stale label Jun 11, 2020
@miq-bot
Copy link
Member

miq-bot commented Jun 11, 2020

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation.

@Fryguy Fryguy added pinned and removed stale labels Jul 6, 2020
@Fryguy
Copy link
Member

Fryguy commented Mar 30, 2021

This could be the way forward for #77

@Fryguy Fryguy added the size/l label Mar 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants