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
Meetings/ML2

1 Mitaka Design Summit recap Etherpads: https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Neutron Driver API for SecurityGroup - yamamoto

126 KB (17,217 words) - 05:14, 13 December 2017
NetworkService (section Design Ideas)

uses NaaS API for plugging VIFs into networks (this is sligthly different from current nova design where part of the network manager's code - namely s

21 KB (3,066 words) - 23:31, 17 February 2013
Meetings/Tacker/PastMeetingAgenda

unconference status update new project planning project name code name: virtue, ginie, jeeves,... topic name: servicevm, hosting device,... design API/model

30 KB (3,448 words) - 08:34, 6 April 2021
CinderTrainSummitandPTGSummary (section Continued discussion of old CG API removal)

Summary: Despite additional design discussion we landed back on the fact that we want to continue with the original design proposal of creating a new default

19 KB (2,670 words) - 19:52, 14 May 2019
ReleaseNotes/Juno

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 workers

45 KB (5,302 words) - 17:34, 3 December 2015
CinderVictoriaPTGSummary (section Tuesday 02 June: Current Cinder Issues)

it takes for the current zuul "check" to complete, so they're worth a try This was a reminder from the Interoperability Working Group to make sure they

32 KB (5,340 words) - 02:56, 10 June 2020
ReleaseNotes/Essex (section API Documentation)

improving the docs at: http://api.openstack.org We are currently working on adding documentation and examples for all of the api extensions that are shipped

23 KB (3,266 words) - 00:27, 23 September 2014
ReleaseNotes/Icehouse (section API)

OpenStack Compute, the OS-DCF:diskConfig API attribute is no longer supported in V3 of the nova API. The Compute API currently supports both XML and JSON formats

53 KB (6,805 words) - 17:34, 3 December 2015
Meetings/GroupBasedPolicy/MeetingMinutesArchive

instructions PoC Status API Sumit has pushed out API branch: https://github.com/noironetworks/neutron-group-policy/tree/sumit/api Model New core plugin

40 KB (3,101 words) - 19:56, 7 January 2016
Documentation/WhatsUpDoc Archive (section Design Summit)

Arch Guide working group meeting on Wednesday 20:00 UTC in progress. Currently drafting the Design chapter and reusing existing content. Working on getting

260 KB (41,968 words) - 16:49, 22 March 2017
Watcher Meeting Agenda

Discussion Topics Do we need API Guide https://docs.openstack.org/watcher/rocky/api/ ? We have API reference now and API Guide seems useless. Discussion

255 KB (23,685 words) - 09:30, 26 August 2020
NovaNetNeutronParity (section Moving Forward and Reporting Status)

operations (e.g. while "batching" is acceptable for some things, delay by design in provisioning is unaccepable) Test coverage- the review queue for tests

16 KB (2,377 words) - 20:10, 17 March 2014
CinderZedPTGSummary (section Status update on the Quota fix effort)

listed in keystone action: write a spec describing the current API design for the new locations API (alternative: nova's approach of using alternative endpoint

31 KB (4,940 words) - 08:32, 18 April 2022
CinderAntelopePTGSummary (section Reporting of pool capacity factors in API)

org/p/antelope-ptg-cinder-user-survey-current-questions action: Brian to talk to Allison regarding the revised survey feedback (status after PTG: Done) The concept

24 KB (3,745 words) - 08:54, 31 March 2023
TC Elections October 2014 (section Topic: Communication: How would you describe our current state of communication in the OpenStack community?)

implementations is important. Nova API should always behave like Nova API, Cinder API should always behave like Cinder API, etc. Monty Taylor In case you haven't

82 KB (12,584 words) - 14:07, 17 October 2014
CommonOptionsProcessing (section Current status)

special "flag file", see below) While a coder defines their module-level flags in the module they are working on (as opposed to a single global file),

8 KB (1,006 words) - 06:52, 12 December 2013
Manila/Meetings

2016, 15:00 UTC Driver private data admin API Disagreement abounds on how this API is to be designed, tested, and presented. https://review.openstack

186 KB (27,091 words) - 14:16, 9 May 2024
Murano/Incubation (section Incubation Status)

bindings for Murano APIs (two repos to be merged into a single one when the primary API repositories are merged): for main Murano API for Murano Application

11 KB (1,338 words) - 15:12, 4 March 2014
Daisy (section API)

merged, bug is automatically moves to "Fix Committed" status. In Daisy, we set "Fix Released" status for a bug only when it was verified by someone else

15 KB (2,181 words) - 23:45, 15 August 2016
Meghdwar

hypervisor KVM or LXD 5. The APIs for KVM? or LXD API will be asap, a. Refer https://github.com/lxc/lxd/blob/master/doc/rest-api.md b. Refer https://kernel

39 KB (6,586 words) - 04:14, 2 November 2016
MagnetoDB/QA/Master test plan

(stable, in_progress, not_ready) to define voting status for each test according to its current status. See the detailed description of this concept and

19 KB (2,635 words) - 08:25, 25 April 2014
OpsGuide/User-Facing Operations (section Security Groups)

openstack security group rule delete, specifying security-group-rule ID. Whole security groups can be removed with openstack security group delete. To create

115 KB (11,030 words) - 02:30, 14 November 2017
OpsGuide-User-Facing-Operations (section Security Groups)

openstack security group rule delete, specifying security-group-rule ID. Whole security groups can be removed with openstack security group delete. To create

109 KB (10,965 words) - 22:01, 16 August 2017
ReleaseNotes/Juno/fa

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 workers

41 KB (4,958 words) - 09:31, 12 July 2015
ReleaseNotes/Juno/zh-tw

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 workers

41 KB (4,923 words) - 13:00, 17 March 2016
ReleaseNotes/Juno/en

update the status of a host in the sql database when the status changes, instead of every 60 seconds. launchpad specification Include status information

43 KB (5,242 words) - 02:11, 13 August 2016
Successes

#openstack-manila) Manila API ref is officially publishing from content that's in code tree - http://developer.openstack.org/api-ref/shared-file-systems

88 KB (0 words) - 15:12, 4 March 2024
Documentation/ReorganizeUserGuides

changes currently. BaremetalNo recommended changes currently. OrchestrationNo recommended changes currently. Telemetry Data Retrieval: The code snippet

43 KB (2,795 words) - 10:32, 4 May 2017
ReleaseNotes/Icehouse/pl (section API)

OpenStack Compute, the OS-DCF:diskConfig API attribute is no longer supported in V3 of the nova API. The Compute API currently supports both XML and JSON formats

53 KB (6,661 words) - 15:55, 23 April 2014