-
Notifications
You must be signed in to change notification settings - Fork 14
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
How-to Openstack Integration #855
Conversation
docs/src/charm/howto/openstack.md
Outdated
``` | ||
|
||
|
||
Adjust [easyrsa][easyrsa] to avoid creating an LXD machine: |
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.
@HomayoonAlimohammadi Is this necessary for our users?
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 don't think so. Maybe @addyess has a better idea but I think it's not a very special thing. I mean the problem in our envs is that we can not create LXD machines, maybe that's not the case for the user. And what if something else is going wrong with the Openstack deployment of the user? e.g. What if - let's say - Keystone is not configured correctly? Also seems like Openstack on LXD is supported (tho it's only for testing/development purposes).
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.
And even if not using LXD is the way to go when deploying on Openstack, I think we should change the overlay rather than instructing the user to the change the overlay manually.
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.
Yeah, i don't think this is critical. I don't know if we ever got to a solution why the openstack instance we're using for testing requires easyrsa to be its own machine. I think we shouldn't note "avoiding creating this LXD machine"
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.
Great work, thanks a lot @louiseschmidtgen! Left some comments.
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.
Alrighty so this has alot of detail about how the bundle works. I appreciate that.
Can we use more of the docs from charmed-kubernetes
https://ubuntu.com/kubernetes/docs/openstack-integration
i think it provides a better user experience from the day-2 ops rather than how to get k8s up on openstack
@@ -16,6 +16,7 @@ Overview <self> | |||
|
|||
charm | |||
install-lxd | |||
openstack |
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 imagine at some point, we're going to need to make an "Integrate with Clouds", and detail other clouds like aws, azure, gcp, maas, etc. Even lxd could be counted as one of these clouds (though there isn't much to integrate with)
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.
Great point Adam! We may also want to think about splitting up the sections from the Charmed K8s doc in separate pages for Canonical K8s. Seems like quite a big how-to on one page...
docs/src/charm/howto/openstack.md
Outdated
``` | ||
|
||
|
||
Adjust [easyrsa][easyrsa] to avoid creating an LXD machine: |
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.
Yeah, i don't think this is critical. I don't know if we ever got to a solution why the openstack instance we're using for testing requires easyrsa to be its own machine. I think we shouldn't note "avoiding creating this LXD machine"
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.
LGTM, thanks a lot @louiseschmidtgen!
4953cdb
to
5bbc5d4
Compare
How-to Openstack Integration
This PR adds docs: how to integrate Canonical K8s with the Openstack cloud it is deployed on, by adding a layer.