opendevreview | Michal Nasiadka proposed openstack/kayobe master: Add support for Rocky Linux 8 https://review.opendev.org/c/openstack/kayobe/+/831652 | 08:04 |
---|---|---|
opendevreview | Michal Nasiadka proposed openstack/kayobe master: Add support for Rocky Linux 8 https://review.opendev.org/c/openstack/kayobe/+/831652 | 08:11 |
ironfoot | The fact that `neturon.conf` configuration is "merged" from /etc/kolla/config/neutron.conf and not /etc/kolla/config/neutron/neutron.conf is confusing | 10:22 |
ironfoot | - "{{ node_custom_config }}/neutron.conf" | 10:22 |
ironfoot | oh, it's done like that in all the roles, but I just noticed this | 10:23 |
ironfoot | nevermind :) | 10:24 |
opendevreview | Mark Goddard proposed openstack/kayobe master: libvirt: deploy libvirt on the host https://review.opendev.org/c/openstack/kayobe/+/825359 | 10:35 |
opendevreview | Konstantin Yarovoy proposed openstack/kolla master: Refactor image module https://review.opendev.org/c/openstack/kolla/+/828716 | 11:38 |
opendevreview | Ivan Halomi proposed openstack/kolla-ansible master: Adding support of podman deployment https://review.opendev.org/c/openstack/kolla-ansible/+/799229 | 12:10 |
opendevreview | Michal Nasiadka proposed openstack/kayobe master: Add support for Rocky Linux 8 https://review.opendev.org/c/openstack/kayobe/+/831652 | 13:13 |
spatel | folk! i help with kolla-ansible and manila (i will also ask in manila IRC but just wanted to see i am not doing anything stupid with kolla). This is my issue - https://paste.opendev.org/show/bwLzT66mtGGEoxh8qoqv/ | 14:06 |
vkmc | spatel, I'm not entirely familiar with glusterfs itself, but it seems you are missing the client package | 14:12 |
vkmc | glustefs and glusterfs-fuse | 14:12 |
vkmc | maybe this can help https://docs.openstack.org/manila/latest/admin/glusterfs_driver.html | 14:12 |
spatel | where i should install that package..? in manila_share container? | 14:12 |
spatel | i went through that doc many time in google search but didn't find any thing related | 14:13 |
spatel | tell me if i am wrong its seems manila_share doesn't have 'mount.glusterfs' package.. am i reading this correct? | 14:15 |
vkmc | carloss, o/ | 14:15 |
vkmc | thanks for joining | 14:15 |
vkmc | repasting spatel's log https://paste.opendev.org/show/bwLzT66mtGGEoxh8qoqv/ | 14:15 |
spatel | vkmc lets say for experiment i want to install that package in container then what is the way to install package in container? | 14:16 |
vkmc | spatel, how are you building that container image? not sure if you have a change we can take a look into | 14:16 |
spatel | I just install All-in-one kind of kolla-ansible in lab | 14:17 |
vkmc | ok, so include that dependency on the image you are building | 14:17 |
spatel | i don't have any container registry. | 14:17 |
vkmc | glusterfs-build | 14:17 |
vkmc | glusterfs-fuse* | 14:17 |
spatel | yes i want to install glusterfs-fuse package in manila_share docker container ( i am using centos8 wallaby) | 14:18 |
vkmc | cool | 14:18 |
spatel | I tried docker exec -it method but its asking for sudo password :( | 14:18 |
vkmc | hmm not sure how those images are built | 14:19 |
vkmc | you can try passing -u 0 to that | 14:19 |
spatel | let me try | 14:20 |
vkmc | sure | 14:20 |
vkmc | where are you getting this image from? | 14:20 |
spatel | image provided by kolla-ansible repo.. i have no idea from where they came.. | 14:22 |
spatel | how do i check if i want to find out | 14:22 |
spatel | i just follow kolla-anisble aio steps and didn't do any fancy stuff so not sure from where it comes from by default | 14:23 |
spatel | assuming docker hub repo.. may be | 14:23 |
spatel | vkmc i am not running own Docker registry. so assuming its coming from public | 14:25 |
spatel | sudo -u 0 not working :( | 14:28 |
spatel | I would like to get root access of container and not sure how? - https://paste.opendev.org/show/bTtSXopPxCnmJGMVhU5n/ | 14:38 |
spatel | Damn it it works docker exec -u 0 -it manila_share bash | 14:46 |
spatel | thanks to admin1 :) | 14:47 |
spatel | and vkmc :) | 14:47 |
spatel | earlier i was trying docker -u 0 exec so that was my fault | 14:47 |
spatel | hmm vkmc progress after installing glusterfs-client package inside manila_share container i am seeing this error - https://paste.opendev.org/show/bMpEnOcucdAgd99jxf7Z/ | 14:51 |
spatel | why manila_share trying to mount this share on container :O - sudo manila-rootwrap /etc/manila/rootwrap.conf mount -t glusterfs 10.30.1.206:/myshare/brick1/brick /var/lib/manila/mnt/myshare | 14:51 |
rockey | spatel: might even be so that you'll need; `docker exec -it -u 0 --entrypoint /bin/bash manila_share` in some cases, if entrypoint is set in image :) | 14:56 |
rockey | spatel: docker image inspect -f '{{.Config.Entrypoint}}' <image> will tell you the entrypoint in an image | 14:57 |
rockey | just fyi | 14:57 |
spatel | rockey that is great info :) | 15:00 |
spatel | Lets say i want to install some thirdparty package in container then is there a easy way to add those package in role or playbook ? | 15:01 |
rockey | well, either you utilize kolla-build in kolla project https://docs.openstack.org/kolla/latest/admin/image-building.html | 15:02 |
rockey | or do customizations via regular Dockerfiles, which me personally highly don't recommend :) | 15:03 |
yoctozepto | spatel: yeah, I confirm we don't glusterfs preinstalled in Debuntu images, we probably should | 15:07 |
yoctozepto | spatel: regarding the next issue - we will need the logs it mentions - otherwise we are lacking the batteries to my magic ball... | 15:07 |
opendevreview | Mark Goddard proposed openstack/kolla stable/train: CentOS Stream 8: drop CentOS RabbitMQ 3.8 repo https://review.opendev.org/c/openstack/kolla/+/832650 | 15:07 |
rockey | yoctozepto: i'll send you some batteries, no worries :) | 15:08 |
opendevreview | Juan Pablo Suazo proposed openstack/kolla-ansible master: Adapts Ceilometer configurations so metrics can be pushed to an external Prometheus Pushgateway. https://review.opendev.org/c/openstack/kolla-ansible/+/832651 | 15:08 |
spatel | yoctozepto yes we should because after installing glusterfs-client my issue got resolved | 15:08 |
spatel | now question is why manila_share mounting my glusterfs share? | 15:09 |
spatel | is manila_share will be in data path? | 15:09 |
spatel | i thought manila will just tell client go here for your new share folder with permission | 15:10 |
yoctozepto | rockey: :-) | 15:10 |
yoctozepto | spatel: I believe it may want to prepare the permissions, but I don't know manila well - vkmc to the rescue ;-) | 15:11 |
spatel | lets me do some testing and see who is in data path | 15:11 |
tbarron | spatel: it's not in the data path; the gluster | 15:29 |
tbarron | driver does some checking etc. like this: | 15:29 |
tbarron | https://opendev.org/openstack/manila/src/branch/master/manila/share/drivers/glusterfs/layout.py#L211 | 15:29 |
opendevreview | Radosław Piliszek proposed openstack/kolla master: Install glusterfs-client in Debuntu https://review.opendev.org/c/openstack/kolla/+/832661 | 15:30 |
yoctozepto | spatel: ^ enjoy ;-) | 15:31 |
carloss | tbarron++ - the mount part is basically a check for the driver during the setup | 15:31 |
opendevreview | Juan Pablo Suazo proposed openstack/kolla-ansible master: Adapts Ceilometer configurations so metrics can be pushed to an external Prometheus Pushgateway. https://review.opendev.org/c/openstack/kolla-ansible/+/832651 | 15:31 |
gouthamr | spatel: the driver also mounts shares to wipe out data during deletions: https://opendev.org/openstack/manila/src/branch/master/manila/share/drivers/glusterfs/layout_volume.py#L334-L375 | 15:36 |
gouthamr | i think this is because the data's not really inaccessible by just unlinking the dataset | 15:37 |
gouthamr | your question on the ML made me read up the driver doc, and we've a call out here: https://docs.openstack.org/manila/latest/admin/glusterfs_driver.html#known-restrictions | 15:38 |
* gouthamr also ey tbarron \o/ | 15:38 | |
opendevreview | Juan Pablo Suazo proposed openstack/kolla-ansible master: Ceilometer configurations now supports pushing metrics to Prometheus Pushgateway. https://review.opendev.org/c/openstack/kolla-ansible/+/832651 | 15:41 |
yoctozepto | alert, alert - the kolla channel has been overtaken by wild zorillas - alert, alert | 15:41 |
opendevreview | Nathan Taylor proposed openstack/kolla-ansible master: Adds etcd endpoints as a Prometheus scrape target https://review.opendev.org/c/openstack/kolla-ansible/+/831848 | 15:42 |
spatel | tbarron thank you for confirmation.. :) | 15:49 |
spatel | gouthamr tbarron dealing with this issue, any idea - https://paste.opendev.org/show/bSlL1KSZqs4yJvl9iWXa/ | 15:52 |
gouthamr | spatel: are you using admin creds? the /v2/services endpoint has a default RBAC that only allows role:admin | 15:53 |
spatel | gouthamr i did - source /etc/kolla/admin-openrc.sh | 15:57 |
spatel | i can create vm and do all other operation | 15:57 |
gouthamr | hmmm, that'd be weird; i can't reproduce it on my end. can you verify: openstack role assignment list --names --user OS_USERNAME | 16:01 |
gouthamr | $OS_USERNAME* | 16:01 |
spatel | https://paste.opendev.org/show/bae9DgkTMMXVLogduVPc/ | 16:01 |
gouthamr | do you have any custom rbac? | 16:02 |
spatel | no, i didn't create anything fancy.. just install manila with default kolla-ansible way | 16:02 |
spatel | what is your output saying - openstack role assignment list --names --user | 16:09 |
spatel | gouthamr this is related may be - https://bugs.launchpad.net/charm-manila-ganesha/+bug/1952763 | 16:14 |
gouthamr | spatel: may be, here's my o/p; https://paste.opendev.org/show/b1Fo3j0RB0rtKxS3e9GI/ | 16:21 |
gouthamr | i wonder if there's a policy.json file interfering here, i'm not too familiar with what kolla does with policies.. | 16:22 |
gouthamr | atleast that's what the manila juju charm seems to be doing -- generating a policy.json file | 16:23 |
opendevreview | Merged openstack/kolla-ansible master: Make cron logfile minsize,maxsize configurable https://review.opendev.org/c/openstack/kolla-ansible/+/810861 | 16:33 |
spatel | gouthamr i am trying to figure out what is going on | 16:47 |
gouthamr | spatel: can you look in /etc/kolla/config/manila for any custom policy file? | 16:58 |
spatel | I don't have that directory here /etc/kolla/config/manila | 16:59 |
spatel | i am thinking to remove /etc/manila/policy.json file and see | 16:59 |
gouthamr | ^ ack | 16:59 |
vkmc | tbarron, gouthamr, thanks for following this up :) got into some meetings | 17:00 |
spatel | should i remove it in manila_api or manila_share.. let me try api first | 17:00 |
gouthamr | api | 17:00 |
gouthamr | manila_share doesn't need the policy file | 17:00 |
spatel | gouthamr it works! :) | 17:02 |
spatel | https://paste.opendev.org/show/bsjlJULNFsB0JomCS0fa/ | 17:02 |
spatel | I did that on only manila_api container only | 17:04 |
gouthamr | nice, spatel -- so this is another bug here | 17:05 |
spatel | kolla-ansible should remove that file and let user decide to add it back | 17:05 |
gouthamr | could you please report it on launchpad? | 17:05 |
spatel | sure doing it now | 17:05 |
kevko | spatel: sorry, I noticed that you had some problems with policy ? | 17:07 |
kevko | spatel: I had also some time ago (with debian binary build type - because packages provides policy for service) | 17:08 |
spatel | Yes.. i have added manila service and after that i started seeing this bug https://bugs.launchpad.net/charm-manila-ganesha/+bug/1952763 | 17:08 |
kevko | spatel: i didn't read whole chain of your problem, but you had policy inside container which was not provided by kolla-ansible ..but burned into image ? | 17:08 |
spatel | i have no idea from where that policy.json came (i didn't do anything fancy related policy). you are saying possible it came from image itself not part of kolla-ansible playbook correct? | 17:09 |
spatel | https://paste.opendev.org/show/bsjlJULNFsB0JomCS0fa/ | 17:10 |
kevko | spatel: yes, of course | 17:11 |
kevko | spatel: which type of images did you use | 17:11 |
kevko | spatel: btw, i've provided patch for this some time ago -> https://review.opendev.org/c/openstack/kolla/+/812479 | 17:11 |
spatel | kevko its very good question. I am new to kolla and just install aio and not sure from where default images come? how do i check from where they came? | 17:11 |
spatel | kevko ah! so solution is already on the way :) | 17:12 |
spatel | i don't have any docker local registry | 17:13 |
kevko | spatel: docker inspect manila_api | grep -i image | 17:17 |
spatel | kevko https://paste.opendev.org/show/bg4iTuUYinxLLcxJf3Sq/ | 17:17 |
kevko | spatel: well, and that's the point ! | 17:17 |
spatel | so where is the best place to get image for production? | 17:18 |
kevko | spatel: if you will use quay.io/openstack.kolla/ubuntu-source-manila-api:wallaby .. you will be fine | 17:19 |
spatel | oh ok | 17:20 |
spatel | that is what i am using :) | 17:20 |
kevko | spatel: no - > you are using this -> quay.io/openstack.kolla/ubuntu-binary-manila-api:wallaby | 17:21 |
kevko | spatel: sed -e 's/binary/source/g' | 17:21 |
spatel | hmm source | 17:22 |
spatel | kolla_install_type: "source" <- i should do this correct? | 17:22 |
opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: haproxy: support single external frontend https://review.opendev.org/c/openstack/kolla-ansible/+/823395 | 17:56 |
opendevreview | James Kirsch proposed openstack/kolla-ansible master: Add support for LetsEncrypt-managed certs https://review.opendev.org/c/openstack/kolla-ansible/+/741340 | 18:02 |
opendevreview | Merged openstack/kolla-ansible master: [TrivialFix] Remove old comment https://review.opendev.org/c/openstack/kolla-ansible/+/832135 | 18:12 |
opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: haproxy: support single external frontend https://review.opendev.org/c/openstack/kolla-ansible/+/823395 | 18:19 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!