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

Hard coded repositoryId and ServerPoolId? #5

Open
royolsen opened this issue Feb 14, 2018 · 2 comments
Open

Hard coded repositoryId and ServerPoolId? #5

royolsen opened this issue Feb 14, 2018 · 2 comments

Comments

@royolsen
Copy link

I noticed that these values are hard coded in the oracle_ovm module.

Am I correct in assuming that these should better be set correctly for the current OVM environment?

        "repositoryId": {"type": "com.oracle.ovm.mgr.ws.model.Repository",
                         "value": "0004fb00000300008564bbdbe309abfb"},
        "serverPoolId": {"type": "com.oracle.ovm.mgr.ws.model.ServerPool",
                         "value":"0004fb000002000047a9ab9d92c370b8"},
@dbgeek
Copy link
Owner

dbgeek commented Feb 14, 2018

Yes, it should be changed to current ovm environment that you want to run against. But optimal it should be parameter into the ansible module.
I will try to fix that..

If you have heard about terraform i have started to play around with a terraform provider for OVM
https://github.com/dbgeek/terraform-provider-ovm

@royolsen
Copy link
Author

royolsen commented Feb 14, 2018

Well, they appear to only be used for the "createvm" state. I guess the "present" state is more commonly used. In the latter, I guess repository is set by the clone definition and the "serverPoolId" is correctly retrieved using name from "serverPool".

I have heard about terraform (by the Vagrant guys, right?), I have not yet had a chance to look at it.

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

No branches or pull requests

2 participants