Jump to: navigation, search

Search results

  • than Keystone. Note: We should also consider how the notion of "Admin" APIs fit into this. Certain functionality, like the reporting of "interface bindings"
    2 KB (253 words) - 23:30, 17 February 2013
  • integrate heat. We want to use heat, but i dont feel like its at a state where it fits our clustering integration, which was the major reason for integrating.
    979 bytes (159 words) - 18:01, 3 July 2013
  • estimated timeline. When writing your proposal, try to estimate your timeline to fit the 4 month period of GSoC coding. Also, take into account that GSoC does
    7 KB (826 words) - 22:50, 16 March 2015
  • generic interface that would allow people to use whatever messaging systems fit best in their environments. This should simplify management for organizations
    1 KB (197 words) - 23:30, 17 February 2013
  • org/p/neutron-qos-agenda Flavor framework coordination how do flavors work? , does QoSes fit as flavors? or can they be used to enforce QoS policies on tenants? /join
    5 KB (484 words) - 13:15, 10 June 2015
  • This only works with Ubuntu image and users should modify this script to fit their use case: #!/usr/bin/env python import os # Default grub2 config
    1 KB (156 words) - 06:12, 26 May 2016
  • yet from different points of view) Pros: Existing established program. Fits to orchestration mission in sense of application lifecycle management. Allows
    11 KB (1,338 words) - 15:12, 4 March 2014
  • support multiple subsequent group by How to make the API abstract enough to fit for both SQL and NoSQL?
    3 KB (418 words) - 16:44, 6 May 2014
  • can be used to validate whether and how well actual OpenStack installations fit the OpenStack Foundation's requirements for OpenStack branding. As determined
    3 KB (396 words) - 15:01, 22 November 2021
  • Topics to be discussed include: What is OCCI and its goals? Where does OCCI fit the OpenStack picture? What does the the OpenStack OCCI API implementation
    4 KB (254 words) - 16:32, 24 March 2015
  • particularly wants the blueprint to be worked on. Some times, a proposal does not fit with the Driver's view of the project. In those cases, the blueprint will
    3 KB (507 words) - 19:48, 14 February 2014
  • event batch send Stacktach starts with dequeuing from AMQP so that doesn’t fit with the desire to not put this stuff over queue-based RPC BUT, there is
    9 KB (1,252 words) - 23:31, 17 February 2013
  • description: >- Enter a desired name for a new domain. This name should fit to DNS Domain Name requirements: it should contain
    21 KB (2,229 words) - 10:40, 13 May 2014
  • checkpoint log, letting you as an application developer pick and choose to fit your application's usage and desired capabilities. See: inputs and outputs
    18 KB (2,156 words) - 15:39, 1 June 2021
  • Strategies for Gating in a growing project multi-node openstack testing FITS testing of public clouds Gating/Validation of OpenStack Deployments Upgrade
    15 KB (820 words) - 16:32, 24 March 2015
  • projects have the flexibility to do intermediate or point releases as they see fit The *-core team for a project will decide when and if a point release for
    2 KB (209 words) - 10:05, 24 January 2017
  • Deciding which sub-team you are interested in, or your proposal/idea/fix may fit into is probably a good first step to contributing. Code reviews are a great
    2 KB (301 words) - 08:35, 1 July 2014
  • get started include: Take a look at Treasure Map to see how the pieces fit together. Join the weekly design meeting to see what work is in the hopper
    8 KB (834 words) - 16:29, 9 September 2021
  • demonstrate that Gnocchi is sufficiently performant and feature complete that it is fit for purpose. Doing the documentation and integration work to ensure that
    8 KB (1,121 words) - 15:53, 13 July 2015
  • design summit session. If the core team feels that the proposed extension fits within the Networking programs mission, the API extension will be added to
    7 KB (1,027 words) - 17:10, 29 August 2014

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)