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

Storage pool provisioning with Ansible instead of Virtual Machine Manager GUI #7

Closed
wants to merge 11 commits into from

Conversation

manfredmuth
Copy link

issue #6 related

#6

The storage pool default will be created in the system context.

Destination /okd_lab

Many things still hard coded. But in line with the defaults introduced by project team.

@disposab1e
Copy link
Owner

@manfredmuth Cool! I will come back to you when I had more time this week. So far many thx for your contribution!

@disposab1e
Copy link
Owner

@manfredmuth The default pool is available in my installation of CentOS. Did you install with my doxs or do you have your own libvirt installation?

@disposab1e
Copy link
Owner

@manfredmuth regarding vnc... there was a bug in my docs with the port. The vnc server is started automatically on localhost 5999. Why did you start it manually?

@manfredmuth
Copy link
Author

@manfredmuth The default pool is available in my installation of CentOS. Did you install with my doxs or do you have your own libvirt installation?

I used the standard Hetzner CentOS 7.8 install and folloowed the installation instructions in the documentation. But the default storage pool in context qemu:https:///system was not created by default.

@manfredmuth
Copy link
Author

@manfredmuth regarding vnc... there was a bug in my docs with the port. The vnc server is started automatically on localhost 5999. Why did you start it manually?

You are right. the vncserver was started by default. Seems I cured my homemade problems by starting it manually on a different port

@disposab1e
Copy link
Owner

@manfredmuth To be honest I installed it many times and the default pool was always in place. I wonder a little... perhaps it's created when starting the GUI application, what I always do?

@disposab1e
Copy link
Owner

When you install it with Hetzner.... do you choose "Linux" or "VNC" as installation type?

@disposab1e
Copy link
Owner

disposab1e commented Aug 4, 2020

vnc is a little bit tricky... but when you do it exactly as documented all should work fine.

@manfredmuth
Copy link
Author

When you install it with Hetzner.... do you choose "Linux" or "VNC" as installation type?
I use the VNC option

@disposab1e
Copy link
Owner

And I'm sure:

Software Selection
Virtualization Host
Virtualization Platform
System Administration Tools

@manfredmuth
Copy link
Author

And I'm sure:

Software Selection
Virtualization Host
Virtualization Platform
System Administration Tools

Yes - exactly this ....

@disposab1e
Copy link
Owner

Ok... I try to reproduce...

@disposab1e
Copy link
Owner

disposab1e commented Aug 4, 2020

Yes it's missing when you not start the GUI "Applications -> System Tools -> Virtual Machine Manager" what I have always done after a fresh installation.

The GUI does all the initial setup...

@disposab1e
Copy link
Owner

I hope you don't mind! I have decided to document it instead of using your ansible files for the following reasons:

  • For the storage location it's easiest to use /var/lib/libvirt/images
  • But most imporatnt: I will migrate more and more of some ansible files to terraform (ses an example here)

I also fixed the wrong file pathes for sizing and your "It's" to "It is"

All is done on the release-0.0.4 branch. I will switch to newest software and openshift versions on this branch too before I release a new version.

Anyway... it's a pleasure that you have used my small project and found this ugly bug!

Everything else was working for you out of the box?

@manfredmuth
Copy link
Author

Fine - you are the boss!
Everything else is working

@disposab1e
Copy link
Owner

Great that everything else works for you. If you want to have some enhancements please let me know. I leave this pull request open for all others who want to go a different way than with the VMM GUI.

@disposab1e disposab1e changed the title Storage pools provisioning introduced Storage pools provisioning with Ansible instead of Virtual Machine Manager GUI Aug 5, 2020
@disposab1e disposab1e changed the title Storage pools provisioning with Ansible instead of Virtual Machine Manager GUI Storage pool provisioning with Ansible instead of Virtual Machine Manager GUI Aug 5, 2020
@disposab1e
Copy link
Owner

Time to close it...

@disposab1e disposab1e closed this Mar 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants