How-to Openstack Integration #855
Conversation
| ``` | ||
|
|
||
|
|
||
| Adjust [easyrsa][easyrsa] to avoid creating an LXD machine: |
There was a problem hiding this comment.
@HomayoonAlimohammadi Is this necessary for our users?
There was a problem hiding this comment.
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.
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.
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.
Great work, thanks a lot @louiseschmidtgen! Left some comments.
docs/src/charm/howto/openstack.md
Outdated
| - 0 | ||
| relations: | ||
| - [openstack-cloud-controller:certificates, easyrsa:client] | ||
| - [openstack-cloud-controller:kube-control, kubernetes-control-plane:kube-control] |
There was a problem hiding this comment.
I think we should change these. For Canonical K8s, it's k8s and k8s-worker.
Also I'm now thinking that we might need to include an Openstack overlay (or overlay template) somewhere in the k8s-bundles repo which is sort of customized for our Canonical K8s charm.
Overall, I think this overlay needs significant changes to work with Canonical K8s (in the K8s Openstack docs I only tested against kubernetes-core bundle).
There was a problem hiding this comment.
Agreed we need the k8s template in the k8s-bundles repo and tested before these docs can get published.
There was a problem hiding this comment.
@HomayoonAlimohammadi Are you working on verifying the Canonical k8s overlay template already?
There was a problem hiding this comment.
No I will create a card for that, but we don't have that for now.
louiseschmidtgen
changed the title
There was a problem hiding this comment.
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.
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)
| - Juju set-up as the deployment tool for Openstack. Please refer to | ||
| [Juju and Openstack][juju-openstack] documentation for more information. |
There was a problem hiding this comment.
Ehh --- this isn't REALLY necessary. You just need openstack credentials -- openstack doesn't have to be deployed BY juju
| - A Juju [controller][controller] with [access][credentials] to the OpenStack | ||
| cloud environment. |
There was a problem hiding this comment.
again -- this isn't super necessary. If you have credentials to openstack, you can TOTALLY bootstrap a VM in openstack to use as your juju controller.
Does any of this from charmed-kubernetes help?
https://ubuntu.com/kubernetes/docs/openstack-integration
| [Juju and Openstack][juju-openstack] documentation for more information. | ||
| - A Juju [controller][controller] with [access][credentials] to the OpenStack | ||
| cloud environment. | ||
| - A Juju [model][model] for deploying {{product}} on OpenStack. |
There was a problem hiding this comment.
Once you have bootstrapped a controller on openstack -- it's easy to make a new model for your k8s cluster
| ``` | ||
|
|
||
|
|
||
| Adjust [easyrsa][easyrsa] to avoid creating an LXD machine: |
There was a problem hiding this comment.
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"
| ```yaml | ||
| applications: | ||
| kubeapi-load-balancer: null | ||
| ``` |
There was a problem hiding this comment.
what's this? I don't think our bundle call out the kubeapi-load-balancer does it? This is used by charmed-kubernetes V1 -- it shouldn't be referenced here i don't think
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.