-
Notifications
You must be signed in to change notification settings - Fork 40
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
Extra network interface for a Cephfs setup #248
Comments
Once that is done, the puppet part of mounting cephfs will be the same since selecting the right internal ip address will make the cephfs client use of the right interface. |
A potential for this issue was to drop in the resource "openstack_networking_port_v2" "nic_ceph" {
for_each = module.design.instances
name = format("%s-%s-ceph-port", var.cluster_name, each.key)
network_id = "00b327b4-4fb2-4ed8-a7f2-6ff49e3b7e7c"
security_group_ids = concat(
[
openstack_networking_secgroup_v2.global.id
],
[
for tag, value in openstack_networking_secgroup_v2.external: value.id if contains(each.value.tags, tag)
]
)
}
resource "openstack_compute_interface_attach_v2" "extra_network" {
for_each = module.design.instances_to_build
instance_id = openstack_compute_instance_v2.instances[each.key].id
port_id = "openstack_networking_port_v2.nic_ceph[each.key].id"
} The file has to be put next to the other openstack module files because the Magic Castle provider modules do not output the ids of the instances nor the ids of the security groups. Otherwise, you would have been able to create these ressources outside of the openstack module. |
I added this:
and here is the error I get
mmm, I see the weirdly placed quotes now. |
For perfomance/traffic optimization, we will have a cephfs deployment on a separate network in openstack. This mean that a second network will need to be attatche to login, compute and dtn nodes. I guess that this part all need to be done in this repos, not the puppet one.
I envision this as a config that would look like
or
or something else....
There is less refactoring the second case, but the first config looks better to me.
The text was updated successfully, but these errors were encountered: