Earlier  
Later
New Search
Posted Nick Remark
#openstack-sdks - 2017-01-23
15:32:38 dtroyer I have not done PHP in years (hello PHP 4!) so have no personal idea. This was the only OpenStack PHP lib I am aware of.
15:32:54 Cagelin Ah alright. Thanks anyway for the heads up! :)
15:33:51 dtroyer If you do write your own lib, I think you would benefit from studying some things like keystoneauth and model some of those concenpts as you can and makes sense. And would be helpful in keeping the auth code up to date
15:34:26 Cagelin Yeah I don't think we'll have much of a choice there, if we decide to write our own library , heh :P
15:35:17 Cagelin I don't have a lot of experience with openstack personally, but from what I understand is that there is a pretty tight release-schedule twice a year that might potentionally consist of BC-breaks in API's (correct me if I'm wrong)
15:35:25 dtroyer From the REST side, right. I'm talking about from the PHP API side. I think we would all benefit if more of our libs in any language used similar concepts for the app dev to consume.
15:35:40 Cagelin Ah yeah , fair point
15:36:02 dtroyer The API stability is generally expressed with the use of "microversions".
15:36:17 dtroyer Not all projects use them, some only have very coarse API versions
15:36:58 dtroyer But in general, the API breakages are not signalled by the OpenStack release (although that is when most consumers will see them) but by the API versioning which is not tied directly to those releases
15:37:27 Cagelin hmm alright
15:37:41 dtroyer Nova has the most mature microversion support, and is the one most other projects adopting that are looking at
17:19:17 openstackgerrit Ankur proposed openstack/python-openstackclient: Auto allocated topology for OSC https://review.openstack.org/391331
19:03:53 openstackgerrit Ken'ichi Ohmichi proposed openstack/api-wg: Accurate status code vs. Backwards compatibility https://review.openstack.org/422264
19:18:23 openstackgerrit Abhishek Raut proposed openstack/python-openstackclient: SDK refactor: Prepare security group commands https://review.openstack.org/418183
20:28:19 dtroyer stevemar: Q on the g-r update in our queue… is keystoneauth 2.18.0 going to be stable/ocata?
21:54:01 openstackgerrit Merged openstack/python-openstackclient: Update devref about "--no-property" https://review.openstack.org/421160
23:41:58 openstackgerrit Dean Troyer proposed openstack/python-openstackclient: Handle 403 error on creating trust https://review.openstack.org/423917
23:52:25 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient: Updated from global requirements https://review.openstack.org/423277
#openstack-sdks - 2017-01-24
01:24:26 openstackgerrit Merged openstack/python-openstackclient: SDK refactor: Prepare security group commands https://review.openstack.org/418183
01:44:30 stevemar dtroyer: yes, i believe that will be the final version of keystoneauth for ocata -- 2.18.0
01:50:40 openstackgerrit Steve Martinelli proposed openstack/python-openstackclient: Handle 403 error on creating trust https://review.openstack.org/423917
02:46:15 openstackgerrit Brian Rosmaita proposed openstack/python-openstackclient: Update container format choices https://review.openstack.org/423551
04:04:56 openstackgerrit Steve Martinelli proposed openstack/python-openstackclient: Update container format choices https://review.openstack.org/423551
04:16:28 openstackgerrit Merged openstack/python-openstackclient: Handle 403 error on creating trust https://review.openstack.org/423917
05:12:42 openstackgerrit Steve Martinelli proposed openstack/python-openstackclient: change assert_show_fields to not fail on new fields https://review.openstack.org/424433
05:54:18 reedip stevemar : awake ?
06:06:31 openstackgerrit Merged openstack/python-openstackclient: Functional tests - port https://review.openstack.org/416980
06:21:05 openstackgerrit Anh Tran proposed openstack/js-openstack-lib: Typo fix: constistent => consistent https://review.openstack.org/424446
06:28:06 openstackgerrit Reedip proposed openstack/python-openstackclient: Overwrite/Clear Flavor property https://review.openstack.org/415369
06:50:19 openstackgerrit Reedip proposed openstack/python-openstackclient: Overwrite/Clear Flavor property https://review.openstack.org/415369
08:19:46 openstackgerrit zhiyong.dai proposed openstack/python-openstackclient: Support "--no-property" option in volume snapshot set https://review.openstack.org/416182
08:41:07 openstackgerrit Rui Chen proposed openstack/python-openstackclient: Rework port functional tests on json output format https://review.openstack.org/423970
08:48:12 openstackgerrit rajiv proposed openstack/python-openstackclient: Introduce overwrite functionality for account property. https://review.openstack.org/424514
09:14:13 openstackgerrit zhiyong.dai proposed openstack/python-openstackclient: Functional test for volume transfer request https://review.openstack.org/423960
09:52:51 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient: Updated from global requirements https://review.openstack.org/423277
10:56:03 openstackgerrit rajiv proposed openstack/python-openstackclient: Introduce overwrite functionality for container property. https://review.openstack.org/424580
12:20:21 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient: Updated from global requirements https://review.openstack.org/423277
14:06:25 openstackgerrit OpenStack Proposal Bot proposed openstack/openstackclient: Updated from global requirements https://review.openstack.org/424663
14:08:26 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient: Updated from global requirements https://review.openstack.org/423277
14:23:03 Dinesh_Bhor briancurtin: Hi, whenever you get time please take a look at it: https://review.openstack.org/#/c/420722/
14:29:06 dtroyer OSC folk, I have a question regarding an option name in https://review.openstack.org/#/c/356219/ (that I should have sorted out a long time ago)… I'd like to change it before release tomorow if we are going to change it…
14:30:32 dtroyer stevemar, huanxuan, reedip, ankur-gupta-f1, RuiChen ^^^^^
15:06:26 openstackgerrit Merged openstack/js-openstack-lib: Typo fix: constistent => consistent https://review.openstack.org/424446
15:07:29 openstackgerrit Artom Lifshitz proposed openstack/python-openstackclient: Use image client for images instead of compute https://review.openstack.org/424688
15:35:45 stevemar briancurtin: apparently trying to get things un-blacklisted in the requirements repo is a PITA
15:35:55 stevemar briancurtin: do you mind releasing a new version of the sdk
15:35:58 stevemar 0.9.13?
15:36:04 stevemar dtroyer: do you agree?
15:36:21 briancurtin stevemar: yeah let me take a look at what we have going on
15:36:37 stevemar briancurtin: ty
15:41:40 stevemar dtroyer: oh my: https://review.openstack.org/#/c/424688/1
15:43:09 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient: Updated from global requirements https://review.openstack.org/423277
15:49:44 openstackgerrit Merged openstack/python-openstacksdk: Modified DHCP/Network Resource https://review.openstack.org/423511
15:49:54 openstackgerrit Merged openstack/python-openstacksdk: Updated from global requirements https://review.openstack.org/423686
15:51:10 openstackgerrit Merged openstack/python-openstacksdk: Fix error messages are not displayed correctly https://review.openstack.org/420722
15:52:37 openstackgerrit Merged openstack/python-openstacksdk: Fix Setting Quotas in Neutron https://review.openstack.org/419911
15:53:30 openstackgerrit Merged openstack/python-openstacksdk: Add project ID in QuotaDefault requests https://review.openstack.org/420301
16:17:10 ankur-gupta-f1 dtroyer: You question on that is about the tense of the option names? --allowed-address is the most readable. 'A ports allowed address is <blah>.
16:23:56 dtroyer ankur-gupta-f1: but that is not how we are using it. We use it in a declarative sentence: allow this address on this port
16:39:48 dtroyer stevemar: I'm looking to see what testing we have to cover that change, not sure we have much, if any
16:40:46 stevemar dtroyer: i also think we need a new sdk release, already pinged briancurtin about it -- trying to change the requirements repo is a PITA when something had been blacklisted
16:40:52 ankur-gupta-f1 impartial. Both make sense to me
16:41:16 briancurtin stevemar, dtroyer: i’m putting it together now, just moving things around to get it in order
16:41:57 reedip_ hi
16:44:03 openstackgerrit Merged openstack/python-openstackclient: Functional tests debug support https://review.openstack.org/423154
16:44:47 openstackgerrit Merged openstack/python-openstacksdk: Base for workflow service (mistral) https://review.openstack.org/412079
16:45:13 openstackgerrit Merged openstack/python-openstacksdk: Add workflow service (mistral) https://review.openstack.org/414919
16:46:01 openstackgerrit Justin A Wilson proposed openstack/python-openstackclient: Add support for Cinder API 3.3 into OSC https://review.openstack.org/421585
16:46:58 openstackgerrit Justin A Wilson proposed openstack/python-openstackclient: Add support for Cinder API 3.3 into OSC https://review.openstack.org/421585
16:47:59 reedip_ dtroyer : your question is related to naming in https://review.openstack.org/#/c/356219/, right?
16:48:02 reedip_ looking at it
16:48:20 dtroyer reedip: yes
16:51:14 reedip_ dtroyer : when looking at the negation, no-allowed-address-pair makes more sense than no-allow-address-pair
16:51:47 ankur-gupta-f1 +1
16:51:59 dtroyer yes it does. I'm thinking that is secondary here though
16:52:51 reedip_ dtroyer: I understand what you are saying is that the addresses are not yet allowed, then how can it be in the past tense
16:53:20 reedip_ and thats why allow-address makes a bit more sense
16:53:56 openstackgerrit Brian Curtin proposed openstack/python-openstacksdk: Initial docs for bare-metal service https://review.openstack.org/411132
16:54:44 stevemar briancurtin: hehe, dtroyer has skirted the question
16:55:17 stevemar briancurtin: when you're done moving things around, let me know when you're about to release, we can test OSC's functional tests with SDKs master branch now
16:55:20 dtroyer stevemar: which one? I'm juggling 3 things atm :)
16:55:26 stevemar dtroyer: :)
16:55:37 stevemar dtroyer: end-of-release-fun!
16:55:45 stevemar dtroyer: the one about needing a new sdk version
16:55:53 dtroyer whee!!! Plus TC _and_ board meetings this afternoon
16:55:54 openstackgerrit OpenStack Proposal Bot proposed openstack/python-openstackclient: Updated from global requirements https://review.openstack.org/423277
16:56:21 dtroyer ya, I think new release is simpler than unblacklisting, even with the risks. question is, how much do we trust our tests? :)
16:56:36 dtroyer and can it all get done in time?
16:57:31 openstackgerrit Artom Lifshitz proposed openstack/python-openstackclient: Use image client for images instead of compute https://review.openstack.org/424688
16:58:26 stevemar dtroyer: its gonna have to!
17:04:10 reedip_ dtroyer : I am more inclined to allowed-address-pair
17:04:54 reedip_ because of negation primarily ( maybe a wrong case )
17:05:26 reedip_ and also maybe because the user already decided to allow the addresses
17:05:27 dtroyer I am looking for consistency, and we have a rule regarding options and negation: add "—no-" to the beginning
17:05:44 reedip_ do we have a rule for the past tense ?
17:05:44 dtroyer that overrides English tenses in that regard
17:06:25 dtroyer I'm not certain it is written, it is in the HIG if so, but out longstanding practice is to make options 'active' or present tesnt: —enable rather than --enabled
17:06:47 dtroyer these are not passive commands
17:06:52 reedip_ makes sense to have active commands

Earlier   Later