Earlier  
Posted Nick Remark
#openstack-sdks - 2020-04-22
10:04:55 openstackgerrit Sagi Shnaidman proposed openstack/ansible-collections-openstack master: Add OpenstackModule to os_server_action https://review.opendev.org/721746
12:33:41 openstackgerrit Sagi Shnaidman proposed openstack/ansible-collections-openstack master: Add OpenstackModule to os_server_action https://review.opendev.org/721746
13:21:20 frickler mordred: gtema: please have a look at this revert, not sure whether we can get a FFE for that, but I think it would make sense https://review.opendev.org/717712
13:22:46 mordred frickler: I think that seems like a valid reason to re-release. +A
13:26:15 gtema agree
14:08:09 openstackgerrit Merged openstack/ansible-collections-openstack master: Convert os_server_info to use OpenStackModule https://review.opendev.org/721580
14:18:02 openstackgerrit Noah Mickus proposed openstack/openstacksdk master: Add cipher list support for octavia https://review.opendev.org/721351
14:21:34 nightmare_unreal dtantsur: a few days ago I asked how can I add a new command to openstackclient for e.g. openstack server migrate is an existing cmd. suppose i want to add openstack migration list ( and other commands related to it) . I looked into setup.cfg in source. I can't seem to find the setup.cfg in the devstack ( my development machine ). Does setup.cfg exist only in source ?
14:22:04 nightmare_unreal basically I just to add/extend openstackclient
14:22:17 gtema yes, setup.cfg exists only in source
14:23:02 gtema during build it generates ".../entry_points" file with come info out of it
14:23:16 nightmare_unreal okay, so how can I test the new command then? install the oscclient again by specifying the new class in setup.cfg before installation ?
14:23:40 gtema do you develop it part of the openstackclient repo or how?
14:24:13 nightmare_unreal currently I have a devstack machine and I edit the things in /usr/local/dist-packages/.-----/openstackclient
14:24:34 nightmare_unreal so i directly change stuff here .
14:26:14 gtema you checkout python-openstackclient repo, you deploy devstack, configure osc to connect to devstack. Develop new stuff in OSC and test it against devstack
14:27:06 gtema you will anyway want to submit this upstream, so simply developing somewhere without possibility to get it to the next phase is overhead
14:28:07 nightmare_unreal yeah. thing is devstack setup is quite easy and you get everything on the go. it installs openstackclient too .
14:28:33 nightmare_unreal I will try to configure it
14:30:32 gtema you just create clouds.yaml externally and that's it, your local osc checkout can talk with devstack
14:31:57 nightmare_unreal Oh
14:32:02 nightmare_unreal thanks :)
14:32:05 gtema welcome
14:32:53 gtema you can "dirty hack" this and register your plugins in the .../site-packages/..python-openstackclient/entry_points
14:33:07 nightmare_unreal I just saw this : https://docs.openstack.org/python-openstackclient/pike/configuration/index.html
14:33:08 gtema but this is really a very dirty hack
14:33:25 nightmare_unreal clouds.yaml part is mentioned.
14:33:31 gtema yes
14:33:48 nightmare_unreal Thanks :D . I will try the clouds.yaml way
14:46:03 openstackgerrit Merged openstack/openstacksdk master: Fix an unstable bare metal unit test https://review.opendev.org/721566
15:35:05 openstackgerrit Sagi Shnaidman proposed openstack/ansible-collections-openstack master: Add OpenstackModule to os_server_action https://review.opendev.org/721746
15:40:22 openstackgerrit Merged openstack/python-openstackclient master: Revert "Disallow setting default on internal network" https://review.opendev.org/717712
22:10:31 openstackgerrit Merged openstack/keystoneauth stable/ussuri: Update .gitreview for stable/ussuri https://review.opendev.org/717028
22:10:32 openstackgerrit Merged openstack/keystoneauth stable/ussuri: Update TOX/UPPER_CONSTRAINTS_FILE for stable/ussuri https://review.opendev.org/717029
#openstack-sdks - 2020-04-23
06:39:34 AJaeger keystoneauth cores, please review https://review.opendev.org/721084 - mordred, I think you want your change ;)
09:17:47 BakaKuna a router it wouldn't work. It would have been smart to check the
09:17:47 BakaKuna same in a loop over the generator that returns all agents hosting
09:17:47 BakaKuna to remove a single router from an l3 agent, but when I tried the
09:17:47 BakaKuna I spent the better part of a day trying to find out why I was able
09:17:50 BakaKuna type earlier, but long story short, I didn't :). A short summary
09:17:53 BakaKuna can be found here https://pastebin.com/1s6HgfZg.
09:19:01 BakaKuna j
09:19:03 BakaKuna
09:19:03 BakaKuna So I was able to find a solution eventually, but now I am wondering if this is intented behaviour or if it is worthwhile for me to look if it is worthwhile for me to look into if I can makethis less surprising?
09:20:00 BakaKuna sorry about that =^}. I posted the message in the wrong channel and copy-pasted.
11:34:25 openstackgerrit Merged openstack/openstacksdk master: OpenStack port decorator variables https://review.opendev.org/720420
11:58:11 zbr is there a way to configure a default "image" with openstack? one that should be implicit, or like selected by default in horizon?
11:59:09 openstackgerrit Sagi Shnaidman proposed openstack/ansible-collections-openstack master: WIP: redesign OpenstackModule class https://review.opendev.org/722283
12:27:12 mordred zbr: no - although I have thoght about adding the ability to configure one of those for a cloud in clouds.yaml before
12:29:43 zbr mordred: thanks, mainly I realized other issues related to lack of defaults, i tried to use default flavor and relised there there are no predefined images able to fit it.
12:30:28 zbr still, is more of cloud-administration issue
12:32:16 mordred zbr: yeah - it would be a very nice thing to provide to users
12:32:44 mordred but - still a little tricky
16:05:34 elmiko API SIG office hour open
16:07:21 gtema pretty silent hour. Hey ho elmiko
16:12:21 dtantsur o/
16:12:29 dtantsur handling a customer escalation no, so not really active
16:35:16 elmiko gtema: yeah, usually is
16:35:30 elmiko we are at the point where we can probably announce the end of these office hours
17:06:59 elmiko have a good weekend folks, stay safe and healthy out there o/
22:50:30 openstackgerrit Merged openstack/python-openstackclient master: Remove Babel from requirements https://review.opendev.org/720701
#openstack-sdks - 2020-04-24
07:13:19 openstackgerrit Artem Goncharov proposed openstack/ansible-collections-openstack master: Add volume_backup module https://review.opendev.org/710093
07:34:29 openstackgerrit Artem Goncharov proposed openstack/ansible-collections-openstack master: Add volume_backup module https://review.opendev.org/710093
07:54:54 openstackgerrit Artem Goncharov proposed openstack/ansible-collections-openstack master: Add volume_backup module https://review.opendev.org/710093
07:58:56 nightmare_unreal hey if someone has time today, can you review : https://review.opendev.org/#/c/721594/
08:12:01 openstackgerrit Artem Goncharov proposed openstack/ansible-collections-openstack master: Add volume_backup module https://review.opendev.org/710093
09:53:21 openstackgerrit Artem Goncharov proposed openstack/ansible-collections-openstack master: Add volume_backup module https://review.opendev.org/710093
11:16:54 nightmare_unreal also please review this : https://review.opendev.org/#/c/713881/
14:18:26 BakaKuna Hi all, I currently use the pattern `l3_agent = next(conn.network.agents(type="L3 Agent", host="hostname")) when I am certain that only one object should be returned. (L3 agent only used for the sake of example). Is there any comparable method available that explicitly tries to get one agent and raises an error if for any reason there are more L3 agents on my host?
14:37:36 mordred BakaKuna: no - although I think it would be good if get_agent worked that way
14:38:12 mordred we have some methods in the cloud layer that work with that pattern
14:45:30 BakaKuna mordred: That would be nice indeed. To be honest, I'm still not completely sure if I am using the cloud framework :blush:. Should I have a conn.cloud method if I do?
14:45:40 BakaKuna s/framework/layer
14:50:34 mordred BakaKuna: no - the the layer I refer to as the "cloud" layer is all methods off the conn object
14:50:44 mordred BakaKuna: so - conn.get_server vs conn.compute.get_server
14:51:16 mordred there's a very slow project to make all of that make more sense ... but ENOTIME
14:59:35 BakaKuna mordred: aaah, that clarifies things. Is there anything like a design for conn.get_agent that you know of? I don't have a lot of time at this point. But homeschooling is ending in a few weeks, which may change that.
15:02:02 mordred BakaKuna: there isn't - but I think if you look in openstack/_cloud/network.py you could see a bunch of things to cargo-cult
16:00:05 openstackgerrit Andreas Jaeger proposed openstack/keystoneauth master: Use unittest.mock instead of third party mock https://review.opendev.org/720925
19:01:04 openstackgerrit Merged openstack/keystoneauth master: Re-add python3.5 testing https://review.opendev.org/721084
#openstack-sdks - 2020-04-25
05:57:54 openstackgerrit Himanshu Rawat proposed openstack/ansible-collections-openstack master: subnet allocation pool check is updated to consider for empty allocation pools of the subnet. When updating subnet, pass existing allocation pools pair with newly added allocation pool pair https://review.opendev.org/723064
#openstack-sdks - 2020-04-26
00:26:23 gmann mordred: do we need to keep py2.7 support in shade? -https://opendev.org/openstack/shade/src/branch/master/setup.cfg#L17
11:56:14 openstackgerrit Brin Zhang proposed openstack/python-openstackclient master: Remove translation sections from setup.cfg https://review.opendev.org/723212
12:09:56 openstackgerrit Brin Zhang proposed openstack/python-openstackclient master: Remove translation sections from setup.cfg https://review.opendev.org/723212
12:12:23 openstackgerrit Andreas Jaeger proposed openstack/os-api-ref master: Remove unused translation content https://review.opendev.org/723215
12:13:47 openstackgerrit Andreas Jaeger proposed openstack/os-api-ref master: Remove unused translation content https://review.opendev.org/723215
13:44:46 mordred gmann: really shade is more on extended maint at this point - so i think what we need to do is mark it that way in releases and stop releasing it with future openstack releases. we aren't going to drop 2.7 support - but we should really also not be taking new patches
17:39:43 gmann mordred: i see, got it. thanks
21:24:57 openstackgerrit Himanshu Rawat proposed openstack/ansible-collections-openstack master: Updated allocation pool checks https://review.opendev.org/723064
22:42:24 openstackgerrit Miguel Lavalle proposed openstack/python-openstackclient master: Support tagging Neutron ports on creation https://review.opendev.org/723280
#openstack-sdks - 2020-04-27
09:07:31 openstackgerrit Stephen Finucane proposed openstack/shade stable/ussuri: Update .gitreview for stable/ussuri https://review.opendev.org/719019
09:07:32 openstackgerrit Stephen Finucane proposed openstack/shade stable/ussuri: Break out py27 job templates https://review.opendev.org/723353
09:07:32 openstackgerrit Stephen Finucane proposed openstack/shade stable/ussuri: Update TOX/UPPER_CONSTRAINTS_FILE for stable/ussuri https://review.opendev.org/719020
09:52:44 openstackgerrit Merged openstack/shade master: Declare py38 support https://review.opendev.org/720746
10:20:54 openstackgerrit Merged openstack/shade master: Bump default tox env from py37 to py38 https://review.opendev.org/722907
12:50:06 openstackgerrit Merged openstack/os-api-ref master: Remove unused translation content https://review.opendev.org/723215
13:30:12 nightmare_unreal Thanks
13:30:12 nightmare_unreal can someone review this if you get time : https://review.opendev.org/#/c/721594/
13:33:24 openstackgerrit Stephen Finucane proposed openstack/cliff stable/pike: Move doc requirements to doc/requirements.txt https://review.opendev.org/657844
19:35:15 openstackgerrit Miguel Lavalle proposed openstack/openstacksdk master: Support tagging Neutron ports on creation https://review.opendev.org/717881

Earlier   Later