| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2018-02-06 | |||
| 08:53:06 | openstackgerrit | Hiroaki Kobayashi proposed openstack/os-service-types master: Add blazar project https://review.openstack.org/541168 | |
| 11:28:57 | openstackgerrit | Thomas Herve proposed openstack-infra/shade master: Allow not resolving outputs on get stacks https://review.openstack.org/541244 | |
| 14:48:35 | rabel | do positional arguments have to be in <> in help messages? e.g. server create --help says <server-name>, but subnet create --help says name (without <>) | |
| 14:52:17 | tosky | rabel: without; if you see that in documentation, it's a usual way to describe the options | |
| 14:52:45 | openstackgerrit | Merged openstack/service-types-authority master: Add a reservation service type (blazar project) https://review.openstack.org/541164 | |
| 14:53:48 | rabel | tosky: so the help message of server create is wrong? | |
| 14:54:39 | tosky | rabel: or the other one | |
| 14:55:04 | tosky | rabel: there should be consistency, one way or another, I think | |
| 14:55:21 | tosky | openstack network create --help has <network> | |
| 14:55:48 | tosky | openstack subnet delete --help has <subnet> | |
| 14:56:45 | rabel | tosky: my question is: which one is correct and which one should be changed? | |
| 14:57:36 | tosky | I don't know, but if I have to choose, the behavior of `openstack subnet create --help` seems the outlier compared to the others | |
| 14:58:55 | tosky | all other commands that I'm trying, from core openstack-sdk or from osc plugins, use <...> | |
| 14:58:59 | tosky | but I'm just an user | |
| 15:06:53 | rabel | well, let's wait if some of the devs want to comment | |
| 17:29:42 | holo_ | hello, when im trying to associate my Floating IP to instance with command from documentation: | |
| 17:29:45 | holo_ | root@ctrl00:~# openstack server add floating ip b25132a4-ccfe-4611-90f4-1a55e5c3b83a 192.168.11.21 | |
| 17:29:46 | holo_ | +--------------------------------------+-------+--------+--------------------+--------+---------+ | |
| 17:29:46 | holo_ | | ID | Name | Status | Networks | Image | Flavor | | |
| 17:29:46 | holo_ | root@ctrl00:~# openstack server list | |
| 17:29:46 | holo_ | add_floating_ip | |
| 17:29:49 | holo_ | | b25132a4-ccfe-4611-90f4-1a55e5c3b83a | demo1 | ACTIVE | demo-net=10.0.0.13 | cirros | m1.tiny | | |
| 17:29:50 | holo_ | +--------------------------------------+-------+--------+--------------------+--------+---------+ | |
| 17:29:52 | holo_ | root@ctrl00:~# | |
| 17:30:09 | holo_ | when i try that same but with openstack floating ip set --port... it is working | |
| 17:32:31 | rabel | holo_: you could run openstack --debug ... to see what's actually happening (if you want to paste it somewhere, use http://paste.openstack.org/ ) or you could have a look into nova's and neutron's log | |
| 17:32:41 | holo_ | http://pastebin.pl/view/acf1f580 | |
| 17:32:42 | holo_ | here it is | |
| 17:33:01 | rabel | :D that was fast | |
| 17:33:43 | holo_ | in neutron logs there is nothing.. i was fighteing with it from 2 weeks :) till today i tried other command (everyone told me i have something with my underlaying network ;) | |
| 17:35:58 | rabel | unfortunately i cannot help you either. if you think the client is missbehaving, feel free to open a bug report at https://bugs.launchpad.net/python-openstackclient | |
| 17:36:03 | holo_ | and here is when i will use instance id instead of instance name: http://pastebin.pl/view/9cf23fff | |
| 17:38:23 | holo_ | rabel, ok i will, thanks | |
| 17:47:04 | holo_ | done: https://bugs.launchpad.net/python-openstackclient/+bug/1747721 | |
| 17:47:05 | openstack | Launchpad bug 1747721 in python-openstackclient "openstack client not assagning floating ip to instance" [Undecided,New] | |
| 17:47:22 | holo_ | happy fixing ;) | |
| 17:49:01 | openstackgerrit | Merged openstack/service-types-authority master: Update build to put content into sphinx location https://review.openstack.org/539239 | |
| 19:57:38 | openstackgerrit | Eric Fried proposed openstack/keystoneauth master: DNM: Debug nova-next failure: user headers https://review.openstack.org/541425 | |
| 20:02:42 | openstackgerrit | Eric Fried proposed openstack/keystoneauth master: DNM: Debug nova-next failure: invalidate https://review.openstack.org/541429 | |
| 20:04:32 | openstackgerrit | Eric Fried proposed openstack/keystoneauth master: DNM: Debug nova-next failure: connection params https://review.openstack.org/541431 | |
| #openstack-sdks - 2018-02-07 | |||
| 01:08:56 | openstackgerrit | Merged openstack/keystoneauth master: Zuul: Remove project name https://review.openstack.org/541080 | |
| 08:28:22 | openstackgerrit | Thomas Goirand proposed openstack/python-openstackclient master: Fix crashing console-log https://review.openstack.org/541609 | |
| 12:29:00 | Qiming | mordred, there? | |
| 12:45:32 | Qiming | mordred, leaving a message here anyway --- zaqar is registering itself as 'messaging' service, not sure if that is official or not, SDK is incapable of mapping the service type to a module for it, I have filed a bug: https://bugs.launchpad.net/python-openstacksdk/+bug/1747904 | |
| 12:45:33 | openstack | Launchpad bug 1747904 in OpenStack SDK "message service is not accessible" [Undecided,Confirmed] | |
| 13:25:08 | frickler | seems all osc-functional-devstack* checks are currently failing, is anyone already working on that? | |
| 15:31:32 | mordred | frickler: yes | |
| 15:32:13 | mordred | frickler: https://review.openstack.org/#/c/540554/ should fix the issue - just rechecked it this morning | |
| 15:33:32 | mordred | Qiming: awesome. messaging is their 'old' service type ... I've got a patch half-finished that should fix that issue - I'll try to get it finished today | |
| 15:33:37 | frickler | mordred: hmm, that still seems to fail the non -tips check | |
| 15:34:20 | mordred | frickler: yes - it pulled in 0.11.2 of sdk in its last run which does not contain the fixes | |
| 15:34:58 | mordred | frickler: but the constraints bump landed, so this run SHOULD be ok | |
| 15:35:39 | frickler | mordred: ah, great, thx | |
| 15:37:52 | dtroyer | mordred: thanks for watching the store for me the last while… I may finally be home again for a bit now… | |
| 15:59:10 | mordred | dtroyer: no worries! sorry for the breakage - but I think we've got the gate jobs fixed to actually catch such breakages in the first place | |
| 16:51:28 | openstackgerrit | Monty Taylor proposed openstack-infra/shade master: Use openstacksdk for most transitive depends https://review.openstack.org/541796 | |
| 16:57:46 | mordred | dtroyer: I think http://logs.openstack.org/54/540554/3/check/osc-functional-devstack-tips/e8fc19f/testr_results.html.gz is an unrelated issue and I should just recheck that patch, yes? | |
| 16:58:52 | openstackgerrit | Merged openstack-infra/shade master: Allow not resolving outputs on get stacks https://review.openstack.org/541244 | |
| 16:59:40 | mordred | rods_, SamYaple, slaweq: if you have sec, take a quick peek at https://review.openstack.org/541796 - I'd like to get that in and then cut shade's queens release | |
| 17:08:02 | openstackgerrit | Monty Taylor proposed openstack-infra/shade master: Use openstacksdk for most transitive depends https://review.openstack.org/541796 | |
| 17:09:21 | rods_ | mordred https://review.openstack.org/#/c/541796/2 LGTM | |
| 17:09:26 | mordred | rods_: thanks! | |
| 17:11:16 | openstackgerrit | Monty Taylor proposed openstack/python-openstacksdk master: Add shade jobs to openstacksdk zuul config https://review.openstack.org/541802 | |
| 17:11:25 | rods_ | mordred what else is needed to land https://review.openstack.org/#/c/540169/? | |
| 17:11:27 | mordred | rods_: similar/related ^^ | |
| 17:11:48 | mordred | rods_: we just need to land the three patches in front of it | |
| 17:12:25 | mordred | rods_: although I kinda think we should wait for https://review.openstack.org/#/c/540556/ so we can verify we don't break osc ... | |
| 17:12:33 | mordred | rods_: lemme rebase that stack on the jobs | |
| 17:14:20 | rods_ | mordred +2 on https://review.openstack.org/#/c/541802/1 | |
| 17:32:56 | dtroyer | mordred: yes, aggregates are an occasional race-like issue | |
| 17:52:01 | mordred | dtroyer: cool. I've rechecked. it should be green this time | |
| 18:04:45 | johnsom | dtroyer Have a minute to give the Octavia team some input on a new OSC command? | |
| 18:04:56 | dtroyer | johnsom: sure | |
| 18:05:31 | johnsom | dtroyer Thank you sir. We have a need to expose some "driver" specific commands targeted to admins. | |
| 18:05:36 | johnsom | dtroyer https://etherpad.openstack.org/p/octavia-drivers-osc | |
| 18:06:21 | johnsom | dtroyer The team likes "openstack octavia amphora failover" where octavia is the project name, amphora is the "load balancing element (service vm currently). | |
| 18:07:25 | johnsom | dtroyer I warned them that we tend to stay away from project code names in the commands. In this case the "octavia amphora ..." is all driver dependent and will return "Not implemented" if the driver isn't loaded into octavia, etc. | |
| 18:07:50 | johnsom | dtroyer We seek you CLI wisdom... grin | |
| 18:08:19 | dtroyer | yes, I really try to discourage using project names in CLIs, the resources should be named descriptively, but generically | |
| 18:08:28 | mordred | johnsom: SO ... I just discovered something that i'm going to bug you about during the rocky cycle | |
| 18:08:41 | mordred | johnsom: octavia does not have a version discovery document | |
| 18:09:26 | johnsom | mordred Ha, ok. Yes, this is on the todo list to make sure we have that figured out. We dump some version info based on the API-wg doc at the time, but need to understand that better for sure. | |
| 18:10:16 | johnsom | mordred Can you put a story in for us with a pointer of the "right way", maybe a project example? | |
| 18:10:16 | mordred | johnsom: I discovered it because of an sdk patch that's failing functional tests on octavia things (so yay for testing!) | |
| 18:10:33 | mordred | johnsom: I will TOTALLY put in a story for you and work to make sure it's all done right | |
| 18:10:45 | mordred | johnsom: (and I can work around it sdk-side for now) | |
| 18:10:59 | johnsom | mordred Thank you. I can probably hammer it out pretty quickly with the right guidence | |
| 18:11:17 | mordred | yah- it should be super simple | |
| 18:11:44 | dtroyer | johnsom: so "amphora" is the name of the type of service vm? | |
| 18:11:48 | johnsom | dtroyer So, my other worrry is: "openstack octavia", "openstack f5", "openstack radware", etc. | |
| 18:12:16 | johnsom | dtroyer https://docs.openstack.org/octavia/latest/reference/glossary.html | |
| 18:12:34 | dtroyer | at some point we break this overloading of the "openstack" command. maybe this is approaching one of those places? IDK | |
| 18:12:45 | johnsom | dtroyer it's an element of the octavia driver that does the load balancing. Could be service vm, container, baremetal, etc. | |
| 18:13:50 | johnsom | dtroyer Yeah, it's a bit interesting. The need is there for admin commands for the plugin drivers. | |
| 18:14:11 | dtroyer | my first (sime-uninformed) reaction is to suggest just using "amphora" as the top-level resource. It is closer to a project name in style than a resource description, but might make snese in this case | |
| 18:14:23 | dtroyer | s/sime/semi/ | |
| 18:14:31 | openstackgerrit | Monty Taylor proposed openstack/python-openstacksdk master: Cleanup the BaseProxy docs a bit https://review.openstack.org/539270 | |
| 18:14:31 | openstackgerrit | Monty Taylor proposed openstack/python-openstacksdk master: Shift config exceptions to openstack.exceptions https://review.openstack.org/539396 | |
| 18:14:32 | openstackgerrit | Monty Taylor proposed openstack/python-openstacksdk master: Generate proxy methods from resource objects https://review.openstack.org/540169 | |
| 18:14:32 | openstackgerrit | Monty Taylor proposed openstack/python-openstacksdk master: Rename BaseProxy to Proxy https://review.openstack.org/539271 | |