-
Notifications
You must be signed in to change notification settings - Fork 71
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
Update libvirt readme #769
base: master
Are you sure you want to change the base?
Conversation
Currently, there's no information about what `cc_username` and `cc_password` stand for. Without knowing the context, it's difficult to search for and figure out what they mean. This PR adds a small reference to contextualize the terms.
backend_modules/libvirt/README.md
Outdated
@@ -11,7 +11,8 @@ | |||
- change the `network_name` variable declaration to `null` | |||
- optionally specify fixed MAC addresses by adding `mac = "CA:FE:BA:BE:00:01"` lines to VM modules | |||
- if other sumaform users deploy to the same host, or different bridged hosts in the same network, uncomment the `name_prefix` variable declaration in the `base` module to specify a unique prefix for your VMs | |||
- complete the `cc_password` variable in the `base` module | |||
- if you have a [SUSE Customer Center (SCC) account](https://scc.suse.com/), fill the in the credentials in the `cc_username` and `cc_password` variables in the `base` module | |||
- alternatively, if you don't have an SCC account, you may need to update source repositories under [sumaform/salt/repos](https://github.com/uyuni-project/sumaform/tree/master/salt/repos) depending on what VMs you want to provision |
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'd leave this part out. If one does not have SCC credentials, at this point it is just not possible to provision SLE based VMs, while openSUSE or other freely available distros will work fine.
Or what did you have in mind exactly with this point?
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'm not familiar with how users outside the organization may use the tool, so I wanted to cover both cases just to be sure based on the discussions I had with Dario. If you think the second line doesn't have practical value, I'll remove that bit.
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.
Please just remove it for now
Currently, there's no information about what
cc_username
andcc_password
stand for. Without knowing the context, it's difficult to search for and figure out what they mean. This PR adds a small reference to contextualize the terms.What does this PR change?
This PR updates the libvirt configuration readme with background context.