Earlier  
Later
New Search
Posted Nick Remark
#openstack-sdks - 2019-03-14
16:33:06 elmiko as far as guidance goes, i like the idea of prescribing the normal resource op, but not making that the /only/ option
16:33:16 edleafe well, ignore the @15 part
16:33:55 edleafe but it seems that the idea was to give the ability to set and delete individual tags using /resource/{id}/tags/foo
16:34:04 edleafe with no body
16:34:18 elmiko hmm, the "Tags Resource URLs" sheds some light on the reasoning imo
16:34:42 elmiko heh, you and me edleafe, just same thought train today lol
16:36:40 edleafe elmiko: so it seems that the idea is to provide some shortcuts when creating/deleting/searching tags
16:36:58 elmiko ++, certainly seems so
16:36:58 edleafe instead of "you must work with tags this way!"
16:37:11 elmiko "Note that this representation differs from the one adopted by Nova."
16:37:13 elmiko XD
16:37:36 gtema btw about searching tags. Is there any guidance/service/project/etc to search all resources based on tags?
16:38:14 elmiko good question, i'm not sure immediately. would have to check
16:39:00 elmiko gtema: would that be guidance about creating an api for doing that type of search?
16:39:13 elmiko or on the merits of that type of search?
16:39:13 edleafe gtema: there is http://specs.openstack.org/openstack/api-sig/guidelines/tags.html#filtering-and-searching-by-tags
16:39:27 edleafe gtema: or did you mean something more?
16:39:42 elmiko edleafe++
16:40:09 gtema well, I was meaning more global. I.e. in AWS you can search all different resource types having specific tag set
16:40:52 elmiko imo, that would be highly project dependent but could still follow the advice that edleafe linked
16:41:19 elmiko like if your project wanted it, why not have a `GET /all?tags=foo` or whatever makes sense
16:41:37 elmiko or are you talking about cross-project?
16:41:55 gtema well, even only project base is already a very good beginning
16:42:19 gtema this is to some extend same issue as with project cleanup - find everything in a project
16:43:15 edleafe gtema: and it would be an equally difficult task to do that across OpenStack
16:43:25 gtema but here users might mark all own resources with a specific tag and would probably like to find all resources they have created to clean them up
16:43:32 gtema edleafe: I know
16:43:46 elmiko yeah, for cross-project stuff i think about searchlight. weren't they doing stuff in this area about finding resources?
16:44:11 gtema that is simply something with exist as a ugly bad custom "solution" in our cloud
16:44:20 edleafe gtema: So I understand the benefit of resource cleanup when a project is deleted. What would the benefit of tag search be?
16:44:28 gtema s/with/which/
16:44:47 elmiko gtema: have you seen https://wiki.openstack.org/wiki/Searchlight ?
16:44:52 gtema as a user I want to find all resources in a project, that belong to me
16:44:59 gtema no, not yet
16:45:54 gtema my problem is that I need to fight (and will definitely loose) the game - let us also use this project
16:46:27 elmiko i just remembered it as an effort to do something similar to what you are talking about
16:46:29 gtema use = install
16:46:55 elmiko understood
16:46:57 gtema ok, thanks for point. Will dig further
16:48:54 gtema one reasonable use case: I leave the company (or go for a longer vacation, etc) and would like to clean only my resources (which were tagged) from the shared project
16:50:05 elmiko makes sense to me
16:50:25 elmiko but like, you will need to query multiple servies to get that info
16:50:27 edleafe gtema: I agree that that would be useful. I just cringe at the thought of getting all OpenStack teams to implement it
16:50:39 elmiko i had /thought/ that's what searchlight was about
16:50:39 gtema :D
16:52:47 elmiko edleafe: cringe is a good reaction, iiuc searchlight uses elasticsearch to index all the info, so it's no lightweight solution
16:53:14 gtema definitely
16:53:51 edleafe elmiko: True, but again that requires that all OpenStack projects either a) agree to push their information to searchlight, or b) provide an API that searchlight can query for the info
16:54:01 elmiko right
16:54:18 elmiko and i am not sure how they addressed that issue, i just remember watching some cool talks and demos about it =)
16:56:59 gtema current list of supported OpenStack services are: Cinder, Designate, Glance, Neutron, Nova, Swift
16:57:02 edleafe Elasticsearch is pretty awesome. Getting OpenStack projects to agree on something isn't :)
16:57:08 gtema Each OpenStack service will place notifications for any state change in RabbitMQ
16:57:15 elmiko edleafe: LOL yes!!!
16:57:53 gtema that's what API-SIG is doing, isn't it ;-)
16:57:59 edleafe gtema: yeah, let's re-invent distributed databases!
16:58:16 elmiko gtema: well, we provide guidance but we have always said that we are not the api police ;)
16:58:58 gtema and that's sad. Sometimes the police (or even S.W.A.T.) is necessary to bring things back
16:59:04 edleafe Although we might look pretty snazzy in our API Police uniforms!
16:59:05 elmiko haha
16:59:45 edleafe gtema: unfortunately, OpenStack has always been more about not hurting anyone's feelings than creating great software
17:00:19 gtema thanks
17:00:29 edleafe Well, the office hour is over, and I have to run out for a bit.
17:00:54 elmiko well, also, in the beginning there was no api guidance and to empower open collaboration and development you kinda have to let everyone in if you don't have standards ;)
17:00:59 elmiko later edleafe o/
17:01:28 gtema yeah
17:01:39 elmiko it's a tough issue
17:02:16 gtema I know. Closed-source is bad, but opensource has also problems
17:02:27 elmiko yup, no magic solutions
17:02:56 elmiko i'm gonna grab some lunch, take care o/
17:03:29 gtema yup. have a nice day
23:15:03 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/openstacksdk master: Add "name" filter in "list" call when retrieving a single register https://review.openstack.org/637238
#openstack-sdks - 2019-03-15
04:21:21 openstackgerrit Rabi Mishra proposed openstack/keystoneauth master: Set Content-Type header explictly for LegacyJsonAdapter https://review.openstack.org/643505
13:22:01 openstackgerrit sean mooney proposed openstack/python-openstackclient master: add openstack server recreate command https://review.openstack.org/643578
13:42:42 openstackgerrit sean mooney proposed openstack/python-openstackclient master: add openstack server recreate command https://review.openstack.org/643578
14:47:22 gtema mordred: are you here?
14:50:31 openstackgerrit Monty Taylor proposed openstack/openstacksdk master: WIP Make factory for a CloudRegion from CONF objects https://review.openstack.org/643601
14:53:28 mordred gtema: sort of - about to go on a call
14:53:53 gtema ah, ok. I would need a deeper help.
14:54:46 gtema I am basically writing unit tests for a connection.add_service and again found, that add_service causes additional authorization
14:55:37 gtema and while I was using keystonev2 - it was ok. But when decided to switch to v3 (since it gives possibility to select result catalog) - face this dramatically
14:56:07 gtema found_version = temp_adapter.get_api_major_version() (from service_description) - causes again authorization
15:01:48 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: WIP Add unit tests for connection.add_service https://review.openstack.org/643604
15:43:22 openstackgerrit Artem Goncharov proposed openstack/openstacksdk master: WIP Add unit tests for connection.add_service https://review.openstack.org/643604
15:52:47 openstackgerrit Merged openstack/python-openstackclient master: Fix: set invalid None project_id on range creation https://review.openstack.org/642707
15:52:52 openstackgerrit Merged openstack/python-openstackclient master: Fix service discovery in functional tests https://review.openstack.org/642074
16:44:44 openstackgerrit Dmitry Tantsur proposed openstack/openstacksdk master: baremetal: implement the correct update of the maintenance_reason field https://review.openstack.org/643639
17:22:21 brtknr Does openstacksdk allow you to create a specific floating ip?
17:22:45 brtknr I looked at cloud.network.create_floating_ip() but it only creates random ones...
17:34:11 openstackgerrit Dmitry Tantsur proposed openstack/openstacksdk master: baremetal: implement the correct update of the maintenance_reason field https://review.openstack.org/643639
17:50:08 mordred brtknr: it doesn't look like we have support for creating a specific floating ip anywhere. would be a welcome feature add
18:54:08 openstackgerrit Dmitry Tantsur proposed openstack/openstacksdk master: baremetal: implement the correct update of the maintenance_reason field https://review.openstack.org/643639
18:55:17 openstackgerrit Eric Fried proposed openstack/openstacksdk master: WIP Make factory for a CloudRegion from CONF objects https://review.openstack.org/643601
19:10:02 openstackgerrit Eric Fried proposed openstack/openstacksdk master: WIP Make factory for a CloudRegion from CONF objects https://review.openstack.org/643601
19:40:24 openstackgerrit Merged openstack/openstacksdk master: Collect request stats https://review.openstack.org/614834
19:40:25 openstackgerrit Merged openstack/openstacksdk master: Use auth_url as identity endpoint when not project scoped https://review.openstack.org/643037
20:01:53 fried_rice mordred: couple more bugs flushed out as I've been playing.
20:03:45 mordred fried_rice: sweet - feel free to push up changes and I can put docs up later
20:04:03 mordred fried_rice: (I realized I didn't want to push up new patches while the nova patch was still in flight anyway)
20:04:20 fried_rice ack

Earlier   Later