Tuesday, 2017-02-28

*** melwitt has quit IRC00:02
*** melwitt has joined #openstack-shade00:09
*** melwitt is now known as Guest6807600:09
*** Guest68076 is now known as melwitt00:12
*** jamielennox|away is now known as jamielennox00:16
*** gouthamr has quit IRC03:54
*** larainema has quit IRC05:42
*** abregman has joined #openstack-shade06:10
*** yfried has joined #openstack-shade07:27
*** dtroyer has quit IRC07:40
*** dtroyer has joined #openstack-shade07:40
*** yfried has quit IRC08:25
*** dfflanders has quit IRC10:37
*** yfried has joined #openstack-shade11:03
*** yfried has quit IRC11:59
*** larainema has joined #openstack-shade12:35
*** kong has quit IRC12:39
*** thingee has quit IRC12:54
*** thingee has joined #openstack-shade13:01
-openstackstatus- NOTICE: restarting gerrit to address performance problems13:08
*** ChanServ changes topic to "restarting gerrit to address performance problems"13:08
*** yfried has joined #openstack-shade13:17
-openstackstatus- NOTICE: ok gerrit is back to normal13:37
*** ChanServ changes topic to "ok gerrit is back to normal"13:37
*** ChanServ changes topic to "#openstack-shade"13:44
-openstackstatus- NOTICE: gerrit is back to normal and I don't know how to use the openstackstaus bot13:44
rcarrillocruzthingee , mordred : i merged https://github.com/ansible/ansible/pull/21471 , thx13:48
mordredrcarrillocruz: woot! thank you!!!13:49
mordredrcarrillocruz, thingee: I'm so happy to have your eyes and help on the ansible modules - I was really neglecting them13:49
*** gouthamr has joined #openstack-shade13:50
rcarrillocruzwell, we all know mordred does a few things in OpenStack :D , don't know how you can push so many commits a day :D13:51
mordredrcarrillocruz: my numbers are way down!!!! :)13:54
*** openstackgerrit has quit IRC14:03
*** Matias has quit IRC14:42
*** Matias has joined #openstack-shade14:44
*** abregman has quit IRC15:05
*** larainema has quit IRC15:18
*** larainema has joined #openstack-shade15:19
mordredrcarrillocruz: my numbers are way down!!!! :)7915:36
*** yfried has quit IRC15:44
*** Matias has quit IRC16:25
*** Matias has joined #openstack-shade16:27
thingeemordred: I think you require more pool time in order to get those numbers are18:42
thingeeup*18:42
mordredthingee: yes!!!!19:16
*** openstackgerrit has joined #openstack-shade19:18
openstackgerritMonty Taylor proposed openstack/os-client-config master: Pass ironic microversion through from api_version  https://review.openstack.org/43911819:18
openstackgerritMonty Taylor proposed openstack/os-client-config master: Add support for bailing on invalid service versions  https://review.openstack.org/43911919:18
openstackgerritMonty Taylor proposed openstack/os-client-config master: Add helper factory functions for use in OpenStack services  https://review.openstack.org/43912019:18
openstackgerritMonty Taylor proposed openstack/os-client-config master: Add helper factory functions for use in OpenStack services  https://review.openstack.org/43912019:26
samueldmqhey all20:04
samueldmqis there anything else public in shade other than shade.OpenStackCloud ?20:05
samueldmqI do not see a reason to have anything else, just want to confirm20:05
thingeesamueldmq: other than operator cloud20:08
thingeewhich inherits openstackcloud20:08
samueldmqthingee: gotcha20:08
samueldmqI also have a remark on the docs, not sure others agree, let me share20:08
samueldmqas a shade user, am I expected to know about the underlying cloud ? like what components are in it ?20:09
samueldmqlooks like the answer is no, you just need to know you have an OpenStack cloud and there are some common operations you may perform20:09
thingeesamueldmq: you mean whether or not swift or heat is available?20:10
samueldmqin the docs (https://docs.openstack.org/infra/shade/usage.html) we mention "Get exactly one Keystone user.", "Search Heat stacks.", etc20:10
samueldmqthingee: not really I am talking about these docs ^20:11
samueldmqwe could just mention resources as "OpenStack" or  "cloud" resources rather than service specific20:11
samueldmq"Get exactly one OpenStack user." or "Get exactly one cloud user." as opposed to "Get exactly one Keystone user."20:12
samueldmqthingee: ^20:12
samueldmqmain thing is we don't need to expose underlying services and their specific resources to users20:15
samueldmqlet's present it as an OpenStack cloud that has resources.20:15
thingeesamueldmq: sounds good to me20:22
samueldmqthingee: cool, I can propose a patch.20:23
*** kong has joined #openstack-shade20:58
mordredsamueldmq: yes to what you said above ^^ we shouldn't realy talk about service names like nova/keystone in the OpenStackCloud docs ... it's fine in the OperatorCloud docs - because there we expect it's reasonable for an operator to know what services they run21:14
*** dfflanders has joined #openstack-shade21:24
*** gouthamr has quit IRC21:44
*** gouthamr has joined #openstack-shade22:30
openstackgerritMonty Taylor proposed openstack-infra/shade master: Partially revert floating ip wait change  https://review.openstack.org/43920223:00
thingeemordred: +123:07
thingeemordred: is there reference to https://review.openstack.org/#/c/439202/1 ?23:08
mordredthingee: I actually just abandoned that - tl;dr - we're having crazy nodepool issues and that was the only code I could find even half-way relevant23:12
mordredthingee: but new hunch is that it's actually a paramiko release that's borking us23:12
mordredthingee: (which is good, because I was fairly confident in that patch)23:13

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!