Search results
Create the page "Api working group current design state codes" on this wiki! See also the search results found.
- the current API styles, whether good or bad. We need examples of consistencies and inconsistencies across projects. We need examples of good design and1 KB (91 words) - 16:42, 4 August 2016
- found using this report that the API_Working_Group can use to help find relevant reviews. Additionally, the API Working Group can be contacted directly on30 KB (4,567 words) - 21:56, 13 August 2021
- (github) Documents Overall design doc Data integration design doc API design doc Delegation to VM-migration engine design doc Blog Proposed and Implemented17 KB (2,081 words) - 21:03, 4 April 2018
- without a design, you can leave the specification URL field blank. If you have a design, here is how you get it published and approved: Upload a design specification42 KB (5,589 words) - 09:22, 6 May 2016
- 11:00am-11:40am - API Working Group - https://etherpad.openstack.org/p/BCN-Docs-APIWG 11:50am-12:30pm - Ocata Planning Working Group - https://etherpad33 KB (4,810 words) - 15:08, 11 November 2016
- Action: (jungleboyj) We need somone to backfill Scott and Walt on the API Working group meeting. Meeting is at 10 am Central time on Thursdays. Action: (jungleboyj)11 KB (1,431 words) - 19:11, 1 March 2017
- StructuredStateManagementDetails (section Conflicts on paths being altered while others are working on said paths)horizontal scaling your state engine units is the ability to be able to resume the work of a failed state engine unit on another state engine unit. This makes19 KB (2,944 words) - 20:33, 25 May 2013
- Oslo (section Specialist API Maintainers)Each API typically has one or more specialist maintainers who have responsibility for evolving the API in question. They work to ensure the API meets39 KB (3,441 words) - 15:49, 16 June 2021
- specific projects that would shift our design towards some of the structural things above. Nova VM_state+task_state validation layer. https://review.openstack13 KB (1,946 words) - 02:36, 11 March 2015
- ReleaseNotes/Kilo (section API v2.1)middleware filters and the references from the public_api, admin_api, api_v3, public_version_api, admin_version_api and any other pipelines that may contain the52 KB (6,613 words) - 16:00, 17 November 2015
- Monasca/Transform (section Data model design)metrics which come from a VM indicating what state the VM was in. One might have to look at how the state of the VM changed over the target time interval26 KB (3,170 words) - 03:09, 16 October 2020
- be and how they should be implemented. This is currently in review by the OpenStack Security Group (OSSG). There is no standard/structured logging9 KB (1,055 words) - 19:45, 13 June 2014
- Fuel/Plugins (section Working with tags and branches)email_to: emails_list #List of emails separated by comma test_group: test_group #Test group in fuel-qa for deployment tests of your plugin jobs:120 KB (15,222 words) - 16:03, 19 September 2016
- MultiClusterZones (section Design)Client which API Service to use. This means that we can stand up many API Services and delegate the caller to the most appropriate one. The API service does15 KB (2,448 words) - 02:19, 22 March 2014
- REST API to handle system scope: https://review.opendev.org/c/openstack/cinder/+/776468We're still working on how to handle the Block Storage API v3 URLs48 KB (7,960 words) - 22:47, 4 May 2021
- (spotz), who's on the working group driving the effort, attended the session and emphasized some points to the team: the working group is proposing "The54 KB (8,812 words) - 22:22, 4 November 2020
- org/p/barbican-newton-midcycle-topics certificate api deprecation email (done) state of barbican email (redrobot) state of barbican blog postings (redrobot, alee13 KB (1,867 words) - 12:45, 5 February 2019
- 1 Mitaka Design Summit recap Etherpads: https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Neutron Driver API for SecurityGroup - yamamoto126 KB (17,217 words) - 05:14, 13 December 2017
- in glance-api.conf and/or glance-registry.conf There is no upgrade impact to glance-api workers since glance-api.conf previously hard-coded the workers45 KB (5,302 words) - 17:34, 3 December 2015
- Monasca/Transform-proposal (section Data model design)metrics which come from a VM indicating what state the VM was in. One might have to look at how the state of the VM changed over the target time interval27 KB (3,337 words) - 23:01, 6 March 2018