-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
[Feature] Add openstack provider #37
Comments
Interesting suggestion, I'd like to know more. Do all providers expose openstack directly? I don't think that Civo does that, they wrap it with a ruby REST API. Are all instance names and images the same between every openstack deployment? I'd think you may need more parameters, but I'm not an openstack expert. |
Ping @alexandrevilain |
Hi @alexellis! Sorry for the delay. I don't know which provider exposes the OpenStack API. The only provider I know is OVH which exposes the OpenStack API. I think that instances types and images are different between providers. So you're right, I'll need more parameters. I'm now working on EC2 provider, I'll start working on OpenStack after that. I think that I'll have more work to do as we will need to pass more parameters to the provider. |
Hi @alexellis |
Adding openstack provider will allow us to use great providers like OVH providing instances starting à 0,008€/hour.
I can work on it, submitting a PR on inletsctl.
Expected Behaviour
Adding the --provider openstack flag should provision a new instance on an openstack provider.
Current Behaviour
We can't provision an instance on providers using OpenStack.
Possible Solution
Using gophercloud: https://github.com/gophercloud/gophercloud
And adding the following flags:
The text was updated successfully, but these errors were encountered: