| *** redrobot has quit IRC | 02:40 | |
| *** Guest52018 has joined #openstack-ansible-sig | 03:19 | |
| *** Guest52018 is now known as redrobot | 03:20 | |
| *** dmellado has quit IRC | 04:25 | |
| *** evrardjp has joined #openstack-ansible-sig | 04:33 | |
| *** gtema has joined #openstack-ansible-sig | 06:16 | |
| *** gtema has quit IRC | 06:43 | |
| *** gtema has joined #openstack-ansible-sig | 06:44 | |
| *** gtema_ has joined #openstack-ansible-sig | 07:35 | |
| *** gtema has quit IRC | 07:39 | |
| *** gtema has joined #openstack-ansible-sig | 07:40 | |
| *** gtema_ has quit IRC | 07:44 | |
| *** rpittau|afk is now known as rpittau | 07:54 | |
| *** kaiokmo has joined #openstack-ansible-sig | 08:21 | |
| *** sshnaidm|afk is now known as sshnaidm | 08:22 | |
| *** dtantsur|afk is now known as dtantsur | 08:23 | |
| *** priteau has joined #openstack-ansible-sig | 09:00 | |
| sshnaidm | hey folks, I'd appreciate your reviews on https://review.opendev.org/#/c/721746/ and https://review.opendev.org/730422 | 09:50 |
|---|---|---|
| *** rpittau is now known as rpittau|bbl | 10:11 | |
| openstackgerrit | Sagi Shnaidman proposed openstack/ansible-collections-openstack master: Add notes to README about deps and versions https://review.opendev.org/734557 | 10:13 |
| sshnaidm | small addition to README ^^ | 10:14 |
| sshnaidm | if you have better formulations I'm open to suggestions ^ | 10:19 |
| *** dmellado has joined #openstack-ansible-sig | 10:28 | |
| *** priteau has quit IRC | 10:29 | |
| sshnaidm | gtema, "Ansible and OpenstackSDK have to be installed in the same environment" - would be enough? | 10:36 |
| sshnaidm | gtema, or what can be added? | 10:37 |
| *** gtema_ has joined #openstack-ansible-sig | 10:38 | |
| *** gtema_ has quit IRC | 10:41 | |
| *** gtema has quit IRC | 10:42 | |
| *** priteau has joined #openstack-ansible-sig | 10:49 | |
| *** priteau has quit IRC | 11:16 | |
| *** gtema has joined #openstack-ansible-sig | 11:16 | |
| *** gtema has quit IRC | 11:21 | |
| *** gtema has joined #openstack-ansible-sig | 11:23 | |
| gtema | sshnaidm: unfortunately not. I.e on Mac if you install ansible with brew it will use a dedicated python for that | 11:24 |
| gtema | and it will be "enough" installing sdk into same python to get playbook start, but on the execution (depending on what you default python is) you will find - it simply can not find sdk | 11:25 |
| gtema | this is a MESS | 11:25 |
| sshnaidm | gtema, ack, so.. "Ansible should be able to access OpenstackSDK module on the host"..? I'm not sure what would be better note here | 11:25 |
| gtema | instead perhaps to mention, that SDK need to be available to the ansible during invokation, and is available in the python, which is used by python to execute tasks | 11:26 |
| gtema | (in a perfect Linux world you don't have those problems) | 11:26 |
| gtema | Unfortunately I think a statement like "Ansible should be able to access OpenstackSDK module on the host" is not giving enough starting points to understand the situation | 11:27 |
| gtema | that honestly might be also different if you have "ansible_connection: local" or not | 11:28 |
| gtema | so SDK should be available to ansible AND the python version ansible is invoking on the target host | 11:28 |
| gtema | a simple statement like that might be as complex as trying to make it really work on mac | 11:30 |
| sshnaidm | gtema, honestly it's so extremely obvious that it's kinda difficult for me to formulate.. | 11:35 |
| gtema | it's so obvious, but fragile, that people who just start give up after hours of fighting | 11:55 |
| sshnaidm | gtema, so what would you suggest? | 11:55 |
| gtema | something in the form "SDK should be available to ansible AND the python version ansible is invoking on the target host" | 11:55 |
| sshnaidm | gtema, would "same python environment" mean the same as "python version ansible is invoking on the target host" ? | 12:06 |
| sshnaidm | actually "SDK should be available to ansible" covers also next part | 12:07 |
| gtema | no it's not | 12:07 |
| gtema | python, which you use when invoking ansible AND python, which ansible uses for the module invokation are NOT THE SAME THING | 12:08 |
| gtema | this is a sad truth | 12:08 |
| openstackgerrit | Sagi Shnaidman proposed openstack/ansible-collections-openstack master: Add notes to README about deps and versions https://review.opendev.org/734557 | 12:09 |
| sshnaidm | gtema, check it out ^ | 12:09 |
| gtema | no, you can't say it like this. How can you "used by the same Python interpreter" if you execute on the remote host? | 12:10 |
| sshnaidm | so maybe like "OpenstackSDK has to be available for Ansible and used by the same Python interpreter as Ansible uses on the controller for running modules" | 12:10 |
| gtema | I am against word "same" - this is very confusing | 12:11 |
| *** rpittau|bbl is now known as rpittau | 12:11 | |
| sshnaidm | gtema, well, I don't think we need to make a readme as a tutorial for running Ansible, it's not its purpose | 12:11 |
| sshnaidm | there should be limits | 12:11 |
| gtema | it's not a tutorial, but readme should at least give understanding how to start using it | 12:11 |
| gtema | I am not talking about really integrating installation instructions here | 12:12 |
| sshnaidm | gtema, but you're talking about specifics of Ansible running on various OS, and it's kind of out of scope of openstack modules.. | 12:13 |
| sshnaidm | if somebody doesn't know to run Ansible on mac, should be include the tutorial in our readme? | 12:13 |
| gtema | we are talking about giving user a brief understanding what is it about and how to start using it | 12:13 |
| sshnaidm | yeah, "brief" | 12:14 |
| sshnaidm | if user has problem with ansible, they should open issues in ansible.. | 12:14 |
| gtema | Mac usage should not be part in detail, but we need at that level to describe user, that python, which is used by ansible, and python, that is used by the module ARE different thing | 12:14 |
| gtema | that's not ansible problem | 12:15 |
| sshnaidm | gtema, and these are really specific details about execution of Ansible, I don't think its place in readme of Openstack modules | 12:15 |
| gtema | that's a "issue" of information representation. Consider your playbook is trying to invoke those modules on remote host. Will it work? | 12:16 |
| sshnaidm | we can link to external resource that explains it maybe | 12:16 |
| sshnaidm | gtema, this point is actually explained in the note | 12:16 |
| sshnaidm | and even this is little bit redundant | 12:16 |
| gtema | no problem, but I am against of giving only partial information, that confuses and gives a feeling: it simply does not work | 12:17 |
| sshnaidm | like "don't dry your cat in the microwave" | 12:17 |
| sshnaidm | gtema, what exactly is confusing in this information? | 12:17 |
| gtema | some people really need this info about cat | 12:17 |
| gtema | "same Python interpreter" | 12:17 |
| sshnaidm | gtema, can you describe it without making tutorial how to run ansible and various python interpreters? | 12:18 |
| gtema | collection need to be deployed not only on controller, but also on executor. In the best case those are same, but does everybody know that? | 12:18 |
| sshnaidm | gtema, ok, let's replace "controller" by executor | 12:19 |
| gtema | lemme think on the sentencing (have a call now though) | 12:19 |
| sshnaidm | gtema, ack, thanks | 12:19 |
| gtema | I am so nitpicky here, because I fight myself with the way how it works (doesn't work) on Mac. And even for experienced dev it is terribly frustrating | 12:20 |
| sshnaidm | gtema, I understand and I'd like to make it more helpful, let's just work on the wording | 12:38 |
| *** gtema_ has joined #openstack-ansible-sig | 12:56 | |
| *** gtema has quit IRC | 12:58 | |
| *** priteau has joined #openstack-ansible-sig | 13:12 | |
| openstackgerrit | Sagi Shnaidman proposed openstack/ansible-collections-openstack master: Add notes to README about deps and versions https://review.opendev.org/734557 | 14:33 |
| sshnaidm | gtema_, by "wait_for_server" what do you mean in https://review.opendev.org/#/c/721746/14/plugins/modules/server_action.py ? | 14:39 |
| gtema_ | sshnaidm: https://opendev.org/openstack/openstacksdk/src/branch/master/openstack/compute/v2/_proxy.py#L924 | 14:49 |
| *** gtema_ is now known as gtema | 14:58 | |
| sshnaidm | I think we can skip the meeting today, otherwise someone has something to bring up | 15:01 |
| sshnaidm | I'm working on PTG summary, will send it later | 15:01 |
| gtema | +1 | 15:06 |
| *** gtema_ has joined #openstack-ansible-sig | 15:12 | |
| *** gtema has quit IRC | 15:15 | |
| *** gtema has joined #openstack-ansible-sig | 15:38 | |
| *** gtema_ has quit IRC | 15:41 | |
| *** dtantsur is now known as dtantsur|afk | 16:05 | |
| *** gtema has quit IRC | 16:06 | |
| *** rpittau is now known as rpittau|afk | 16:09 | |
| *** priteau has quit IRC | 17:21 | |
| *** sshnaidm is now known as sshnaidm|afk | 18:07 | |
| *** iurygregory has quit IRC | 18:43 | |
| *** iurygregory has joined #openstack-ansible-sig | 18:47 | |
| iurygregory | any ideas on how I can solve https://opendev.org/openstack/ansible-collections-openstack/src/branch/master/plugins/modules/baremetal_node.py#L248 ? =) | 19:28 |
| iurygregory | mordred, not sure if you know ^ | 19:28 |
| iurygregory | I'm trying to use the openstack.cloud.baremetal_node in bifrost http://paste.openstack.org/show/794541/ | 19:30 |
| mordred | iurygregory: you need to install jsonpatch on the node the openstack.cloud.baremetal_node module is running on | 19:31 |
| mordred | iurygregory: jsonpatch is a depend of openstacksdk - so I'm guessing openstacksdk isn't installed? | 19:31 |
| iurygregory | mordred, hummm | 19:31 |
| mordred | oh - are you running from a virtualenv? | 19:31 |
| iurygregory | yeah | 19:31 |
| iurygregory | i installed bifrost in a virtualenv | 19:32 |
| mordred | yeah - so, that means openstacksdk is installed in the virtualenv - but ansible isn't going to run on the "remote" host in that virtualenv by default | 19:32 |
| mordred | it's going to "connect" to "localhost" and run the module using the puython there | 19:32 |
| mordred | so you probvably need to set ansible_python_interpreter to /opt/stack/bifrost/bin/python | 19:32 |
| iurygregory | so if i install openstacksdk in the machine it should be ok? | 19:33 |
| mordred | running ansible things on localhost with virtualenvs is ... relaly fun | 19:33 |
| mordred | iurygregory: yes - you can also install openstacksdk on the machine | 19:33 |
| iurygregory | since it failed in this part at least the module is installed XD | 19:34 |
| iurygregory | and https://review.opendev.org/#/c/734592/ will probably work \o/ | 19:34 |
| mordred | woot! | 19:34 |
| iurygregory | mordred, ty! installing python3-openstackclient solved \o/ | 20:07 |
| iurygregory | http://paste.openstack.org/show/794542/ | 20:07 |
| *** kaiokmo has quit IRC | 22:13 | |
| *** trident has quit IRC | 23:27 | |
| *** trident has joined #openstack-ansible-sig | 23:29 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!