Search results

Did you mean: api working group current design state codes

Create the page "API Working Group/Current Design/Status Codes" on this wiki! See also the search results found.

API Working Group/Current Design

the current API styles, whether good or bad. We need examples of consistencies and inconsistencies across projects. We need examples of good design and

1 KB (91 words) - 16:42, 4 August 2016
API Special Interest Group (category Working Groups)

Application_Ecosystem_Working_Group (AE WG). The API Working Group (API WG) is complementary to the End User Working Group. The API WG is focused on creating

13 KB (1,426 words) - 15:40, 14 June 2018
API Working Group/Current Design/Errors (section Current Design)

errors are. Status Code: 404 { "itemNotFound": { "message": "Instance could not be found", "code": 404 } } Status Code: 404 { "error":

2 KB (250 words) - 19:27, 27 March 2015
Fault Genes Working Group (category Working Groups)

The results from our working group will support logging group to be able to produce good error codes. Link to our working group charter: https://docs

7 KB (1,102 words) - 16:31, 11 May 2017
API SIG (category Special Interest Groups)

How_To_Contribute. 1. To contribute to analyzing current design: Start at Current Design. Find the category of the API design you want to analyze. If it doesn't

13 KB (1,433 words) - 17:48, 3 January 2019
Design Summit/Ocata/Etherpads (section Architecture Working Group)

11:00am-11:40am - API Working Group - https://etherpad.openstack.org/p/BCN-Docs-APIWG 11:50am-12:30pm - Ocata Planning Working Group - https://etherpad

33 KB (4,810 words) - 15:08, 11 November 2016
Fuel/How to contribute (section Working with puppet upstream modules in fuel-library)

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 specification

42 KB (5,589 words) - 09:22, 6 May 2016
Tacker/Incubation (section Have all current contributors agreed to the OpenStack CLA?)

around multiple implementations. design review process: gerrit, wiki, google-doc API/data model design Actual coding(server, python client) establish

9 KB (1,047 words) - 08:42, 30 June 2020
OpsGuide/Working with Roadmaps (section New API Versions)

all API and provide comments while the next generation APIs are being defined. A new working group was formed specifically to improve OpenStack APIs and

18 KB (1,804 words) - 13:42, 14 November 2017
CinderPikePTGSummary (section Status of Migration CGs to Generic Volume Groups)

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
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 meets

39 KB (3,441 words) - 15:49, 16 June 2021
PublicCloudSIG (redirect from PublicCloudWorkingGroup) (section Title: Public Cloud Working Group Session)

Status: Active Chairs: * Tobias Rydberg <tobias.rydberg@cleura.com> * Felix Kronlage-Dammers <fkr@osb-alliance.com> The aim of this group is to represent

7 KB (949 words) - 22:40, 1 March 2024
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
Lifeless/ArchitectureThoughts

a really bad fit for RPC), or the nova-compute -> neutron-api-> neutron-ovs-agent -> nova-api -> nova-compute VIF plugging weirdness. More importantly I

13 KB (1,946 words) - 02:36, 11 March 2015
Security/Guidelines/logging guidelines (section Status)

be and how they should be implemented. This is currently in review by the OpenStack Security Group (OSSG). There is no standard/structured logging

9 KB (1,055 words) - 19:45, 13 June 2014
Barbican/Archive/Agenda/2016

3, 2016 Action Item Status Newton Status Barcelona Design Summit Topics https://etherpad.openstack.org/p/barbican-ocata-design-summit if you plan to

13 KB (1,867 words) - 12:45, 5 February 2019
Design Summit/Newton/Etherpads (section Group Based Policy)

11:15: Design Summit 101 - https://etherpad.openstack.org/p/newton-design-summit-101 https://etherpad.openstack.org/p/AUS-app-catalog Design Summit

39 KB (5,533 words) - 12:12, 17 May 2016
CinderWallabyPTGSummary (section current roles)

(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 "The

54 KB (8,812 words) - 22:22, 4 November 2020
CinderXenaPTGSummary (section The Interoperability Working Group)

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 URLs

48 KB (7,960 words) - 22:47, 4 May 2021
MagnetoDB/specs/template (section Specification status)

the API level or indirectly such as changes to a cache layer. Can this change enable a resource exhaustion attack, such as allowing a single API interaction

7 KB (1,168 words) - 10:00, 12 September 2014