| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2021-04-13 | |||
| 19:41:19 | ianw | https://review.opendev.org/c/openstack/openstacksdk/+/755644 | |
| 19:41:38 | ianw | looking now; it seems there's neutron and nova paths for security groups and i'm not sure which is being taken | |
| 19:52:41 | openstackgerrit | Kajal Sah proposed openstack/openstacksdk master: Adds Node Vendor passthru https://review.opendev.org/c/openstack/openstacksdk/+/785445 | |
| 20:06:51 | mordred | ianw: neutron | |
| 20:07:19 | mordred | ianw: the places where we go down the nova path should be vanishingly small these days - but in this case it looks like your traceback is definitely going down the neutron branch | |
| 20:07:58 | ianw | mordred: yeah; it seems like the original change bumped the API version, but i don't quite see if/where openstacksdk is checking that | |
| 20:09:32 | mordred | ianw: yeah - I'm not sure how this would detect whether or not to send that attribute | |
| 20:10:12 | mordred | slaweq: ^^ when you get a chance | |
| 20:10:57 | mordred | my guess is that remote_address_group_id only exists either on newer neutron or if a plugin is installed - but the patch adding support is causing it to be sent to the remote side unconditionally | |
| 20:11:10 | mordred | Ill be honest - I don't know what the right story is for that for neutron | |
| 20:11:21 | mordred | but slaweq knows everything | |
| 20:14:07 | ianw | i feel like it's always there, but yeah, only for recent-ish neutron | |
| 20:26:40 | ianw | revision_number = resource.Body('revision_number', type=int) | |
| 20:26:40 | ianw | #: Revision number of the resource. *Type: int* | |
| 20:26:44 | ianw | feels like it might be relevant? | |
| 20:34:30 | ianw | no, that's more for syncing object changes | |
| 23:47:22 | openstackgerrit | Ian Wienand proposed openstack/openstacksdk master: Don't send empty remote_address_group_id for security groups https://review.opendev.org/c/openstack/openstacksdk/+/786148 | |
| 23:48:33 | ianw | mordred / slaweq: ^ that's about my best guess | |
| #openstack-sdks - 2021-04-14 | |||
| 01:17:33 | openstackgerrit | Ian Wienand proposed openstack/openstacksdk master: Don't send empty remote_address_group_id for security groups https://review.opendev.org/c/openstack/openstacksdk/+/786148 | |
| 03:43:31 | openstackgerrit | Ian Wienand proposed openstack/openstacksdk master: Don't send empty remote_address_group_id for security groups https://review.opendev.org/c/openstack/openstacksdk/+/786148 | |
| 03:43:31 | openstackgerrit | Ian Wienand proposed openstack/openstacksdk master: Don't send empty remote_address_group_id for security groups https://review.opendev.org/c/openstack/openstacksdk/+/786148 | |
| 06:03:52 | slaweq | mordred: ianw: sorry, I wasn't online yesterday evening | |
| 06:03:52 | slaweq | mordred: ianw: sorry, I wasn't online yesterday evening | |
| 06:03:58 | slaweq | I just reviewed Your patch | |
| 06:03:58 | slaweq | I just reviewed Your patch | |
| 07:03:03 | openstackgerrit | Ryan Zimmerman proposed openstack/openstacksdk master: Add compute microversion 2.77 https://review.opendev.org/c/openstack/openstacksdk/+/786169 | |
| 09:20:02 | openstackgerrit | Slawek Kaplonski proposed openstack/openstacksdk master: Allow unknown attributes to be included in request body https://review.opendev.org/c/openstack/openstacksdk/+/768208 | |
| 09:20:02 | openstackgerrit | Slawek Kaplonski proposed openstack/openstacksdk master: Allow unknown attributes to be included in request body https://review.opendev.org/c/openstack/openstacksdk/+/768208 | |
| 14:10:06 | openstackgerrit | Merged openstack/python-openstackclient master: requirements: Drop os-testr https://review.opendev.org/c/openstack/python-openstackclient/+/785306 | |
| 14:10:06 | openstackgerrit | Merged openstack/python-openstackclient master: requirements: Drop os-testr https://review.opendev.org/c/openstack/python-openstackclient/+/785306 | |
| 17:40:55 | openstackgerrit | Ryan Zimmerman proposed openstack/openstacksdk master: WIP Add compute microversion 2.78 https://review.opendev.org/c/openstack/openstacksdk/+/786290 | |
| 17:45:04 | openstackgerrit | Ryan Zimmerman proposed openstack/openstacksdk master: WIP Add compute microversion 2.78 https://review.opendev.org/c/openstack/openstacksdk/+/786290 | |
| 21:14:01 | ade_lee_ | fungi, hey - would like to pick your brain a bit on the best way to set up some ci jobs | |
| 21:14:01 | ade_lee_ | fungi, hey - would like to pick your brain a bit on the best way to set up some ci jobs | |
| 21:15:27 | ade_lee_ | specifically, I'd like to set up some jobs in various projects to make sure that no code that fails fips gets merged in -- I tried to do this for barbican as a test case here .. https://review.opendev.org/c/openstack/barbican/+/760665/15/.zuul.yaml | |
| 21:15:27 | ade_lee_ | specifically, I'd like to set up some jobs in various projects to make sure that no code that fails fips gets merged in -- I tried to do this for barbican as a test case here .. https://review.opendev.org/c/openstack/barbican/+/760665/15/.zuul.yaml | |
| 21:17:03 | ade_lee_ | if I want to do this more generally -- will it work to check in that enable-fips.yaml playbook somewhere (maybe devstack) and then just invoke it as a pre-run in whatever job I want to be in fips? | |
| 21:17:03 | ade_lee_ | if I want to do this more generally -- will it work to check in that enable-fips.yaml playbook somewhere (maybe devstack) and then just invoke it as a pre-run in whatever job I want to be in fips? | |
| 21:19:37 | ade_lee_ | or do I need to define something like a devstack-tox-functional-fips etc.? | |
| 21:19:37 | ade_lee_ | or do I need to define something like a devstack-tox-functional-fips etc.? | |
| 21:20:17 | ade_lee_ | sorry - not sure if this is the right channel for these questions .. | |
| 21:20:17 | ade_lee_ | sorry - not sure if this is the right channel for these questions .. | |
| 21:25:14 | fungi | ade_lee_: well, this is more appropriate for openstacksdk and openstackclient discussions, but no worries. yeah what you've got there could be included in devstack or openstack-zuul-jobs... you might consider making it an ansible role rather than a playbook though, as that would allow you to include it in a job variant without having to rely on more heavyweight job inheritance | |
| 21:25:14 | fungi | ade_lee_: well, this is more appropriate for openstacksdk and openstackclient discussions, but no worries. yeah what you've got there could be included in devstack or openstack-zuul-jobs... you might consider making it an ansible role rather than a playbook though, as that would allow you to include it in a job variant without having to rely on more heavyweight job inheritance | |
| 21:26:33 | ade_lee_ | fungi, do you have an example of where that is used? | |
| 21:26:33 | ade_lee_ | fungi, do you have an example of where that is used? | |
| 21:26:45 | fungi | i'll see what i can dig up, just a sec | |
| 21:26:45 | fungi | i'll see what i can dig up, just a sec | |
| 21:33:52 | fungi | may take me a little longer to find a good example of what i'm thinking of (job writing isn't actually one of my strengths, but you've got me curious now too) | |
| 21:33:52 | fungi | may take me a little longer to find a good example of what i'm thinking of (job writing isn't actually one of my strengths, but you've got me curious now too) | |
| 21:34:41 | ade_lee_ | fungi, ack - thanks -- no problem -- I'll just check back here later to see if you've found something | |
| 21:34:41 | ade_lee_ | fungi, ack - thanks -- no problem -- I'll just check back here later to see if you've found something | |
| 21:41:54 | fungi | ade_lee_: okay, i have a fairly concise example relevant to the sdk channel even... ;) | |
| 21:41:54 | fungi | ade_lee_: okay, i have a fairly concise example relevant to the sdk channel even... ;) | |
| 21:41:58 | fungi | https://opendev.org/openstack/openstacksdk/src/branch/master/playbooks/devstack/post.yaml#L9 | |
| 21:41:58 | fungi | https://opendev.org/openstack/openstacksdk/src/branch/master/playbooks/devstack/post.yaml#L9 | |
| 21:42:39 | fungi | that "devstack" playbook in openstacksdk includes the process-stackviz role, which is itself defined in the devstack repo: https://opendev.org/openstack/devstack/src/branch/master/roles/process-stackviz | |
| 21:42:39 | fungi | that "devstack" playbook in openstacksdk includes the process-stackviz role, which is itself defined in the devstack repo: https://opendev.org/openstack/devstack/src/branch/master/roles/process-stackviz | |
| 21:43:18 | ade_lee_ | fungi, cool | |
| 21:43:18 | ade_lee_ | fungi, cool | |
| 21:43:35 | fungi | so what i was (poorly) trying to express earlier is that by encapsulating your tasks into a role, that role can reside easily in a different repository than the playbooks (and hence job definitions) which rely on it | |
| 21:43:35 | fungi | so what i was (poorly) trying to express earlier is that by encapsulating your tasks into a role, that role can reside easily in a different repository than the playbooks (and hence job definitions) which rely on it | |
| 21:44:35 | fungi | so multiple jobs and their playbooks in different projects, e.g. nova, heat, grenade... reuse that role in jobs they've defined | |
| 21:44:35 | fungi | so multiple jobs and their playbooks in different projects, e.g. nova, heat, grenade... reuse that role in jobs they've defined | |
| 21:44:56 | ade_lee_ | fungi, ack thats the model I was looking for , rather than job inheritance | |
| 21:44:56 | ade_lee_ | fungi, ack thats the model I was looking for , rather than job inheritance | |
| 21:45:42 | ade_lee_ | fungi, thanks -- looking at how opensdk uses that now | |
| 21:45:42 | ade_lee_ | fungi, thanks -- looking at how opensdk uses that now | |
| 21:45:50 | ade_lee_ | but this is great - thanks! | |
| 21:45:50 | ade_lee_ | but this is great - thanks! | |
| 21:46:52 | fungi | in the case of openstacksdk, it's using its devstack playbook in post-run phase for jobs: https://opendev.org/openstack/devstack/src/branch/master/roles/process-stackviz | |
| 21:46:52 | fungi | in the case of openstacksdk, it's using its devstack playbook in post-run phase for jobs: https://opendev.org/openstack/devstack/src/branch/master/roles/process-stackviz | |
| 21:46:57 | fungi | er, sorry wrong buffer | |
| 21:46:57 | fungi | er, sorry wrong buffer | |
| 21:47:03 | fungi | https://opendev.org/openstack/openstacksdk/src/branch/master/.zuul.yaml#L30 | |
| 21:47:03 | fungi | https://opendev.org/openstack/openstacksdk/src/branch/master/.zuul.yaml#L30 | |
| 21:48:46 | ade_lee_ | fungi, yup - so in nova for instance, I'd have to define a playbook that would include the fips role (that would be checked into devstack) | |
| 21:48:46 | ade_lee_ | fungi, yup - so in nova for instance, I'd have to define a playbook that would include the fips role (that would be checked into devstack) | |
| 21:49:03 | ade_lee_ | and call that playbook in my nova job? | |
| 21:49:03 | ade_lee_ | and call that playbook in my nova job? | |
| 21:49:13 | ade_lee_ | and a pre-run or whatever .. | |
| 21:49:13 | ade_lee_ | and a pre-run or whatever .. | |
| 21:49:14 | fungi | so similar to your change, except that enable-fips.yaml could just be a hollow inclusion directive and the meat of it can then go in whatever repo you want | |
| 21:49:14 | fungi | so similar to your change, except that enable-fips.yaml could just be a hollow inclusion directive and the meat of it can then go in whatever repo you want | |
| 21:49:45 | ade_lee_ | yup cool - that makes sense | |
| 21:49:45 | ade_lee_ | yup cool - that makes sense | |
| 21:49:59 | fungi | and that way you don't have to copy it into multiple different repos | |
| 21:49:59 | fungi | and that way you don't have to copy it into multiple different repos | |
| 21:50:22 | ade_lee_ | yup indeed | |
| 21:50:22 | ade_lee_ | yup indeed | |
| 21:50:58 | fungi | that way it can also be added to existing playbooks in other jobs just by adding an include statement | |
| 21:50:58 | fungi | that way it can also be added to existing playbooks in other jobs just by adding an include statement | |
| 21:51:24 | ade_lee_ | cool | |
| 21:51:24 | ade_lee_ | cool | |
| 21:52:04 | ade_lee_ | thanks a lot! | |
| 21:52:04 | ade_lee_ | thanks a lot! | |
| 21:53:21 | fungi | yw | |
| 21:53:21 | fungi | yw | |
| 21:54:14 | fungi | ade_lee_: if you have related questions, #openstack-infra or #openstack-qa are probably better places to get help since more folks with experience in this are likely to be paying attention | |
| 21:54:14 | fungi | ade_lee_: if you have related questions, #openstack-infra or #openstack-qa are probably better places to get help since more folks with experience in this are likely to be paying attention | |