Open Yoga specs
Change-Id: I1ac5964b3adda8696e791ff369283137f386dcb3
This commit is contained in:
Liam Young
parent
6de8409c76
commit
1e2ca74126
|
|
@ -11,6 +11,7 @@ Here you can find the specs, and spec template, for each release:
|
|||
:glob:
|
||||
:maxdepth: 1
|
||||
|
||||
specs/yoga/index
|
||||
specs/xena/index
|
||||
specs/wallaby/index
|
||||
specs/victoria/index
|
||||
|
|
|
|||
|
|
@ -1 +0,0 @@
|
|||
../../../../specs/wallaby/approved
|
||||
|
|
@ -15,19 +15,5 @@ Xena implemented specs:
|
|||
:glob:
|
||||
:maxdepth: 1
|
||||
|
||||
implemented/*
|
||||
|
||||
Xena approved (but not implemented) specs:
|
||||
|
||||
.. toctree::
|
||||
:glob:
|
||||
:maxdepth: 1
|
||||
|
||||
approved/*
|
||||
|
||||
Xena backlog (carried over from previous cycle) specs:
|
||||
|
||||
.. toctree::
|
||||
:glob:
|
||||
:maxdepth: 1
|
||||
|
||||
backlog/*
|
||||
|
|
|
|||
|
|
@ -0,0 +1 @@
|
|||
../../../../specs/yoga/approved
|
||||
|
|
@ -0,0 +1 @@
|
|||
../../../../specs/yoga/backlog/
|
||||
|
|
@ -0,0 +1 @@
|
|||
../../../../specs/yoga/implemented
|
||||
|
|
@ -0,0 +1,33 @@
|
|||
=============================
|
||||
Charm Yoga Specifications
|
||||
=============================
|
||||
|
||||
Template:
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
Specification Template (Yoga release) <template>
|
||||
|
||||
Yoga implemented specs:
|
||||
|
||||
.. toctree::
|
||||
:glob:
|
||||
:maxdepth: 1
|
||||
|
||||
|
||||
Yoga approved (but not implemented) specs:
|
||||
|
||||
.. toctree::
|
||||
:glob:
|
||||
:maxdepth: 1
|
||||
|
||||
approved/*
|
||||
|
||||
Yoga backlog (carried over from previous cycle) specs:
|
||||
|
||||
.. toctree::
|
||||
:glob:
|
||||
:maxdepth: 1
|
||||
|
||||
backlog/*
|
||||
|
|
@ -0,0 +1 @@
|
|||
../../../../specs/yoga/redirects
|
||||
|
|
@ -0,0 +1,125 @@
|
|||
..
|
||||
Copyright <YEARS> <HOLDER> <--UPDATE THESE
|
||||
|
||||
This work is licensed under a Creative Commons Attribution 3.0
|
||||
Unported License.
|
||||
http://creativecommons.org/licenses/by/3.0/legalcode
|
||||
|
||||
..
|
||||
This template should be in ReSTructured text. Please do not delete
|
||||
any of the sections in this template. If you have nothing to say
|
||||
for a whole section, just write: "None". For help with syntax, see
|
||||
http://sphinx-doc.org/rest.html To test out your formatting, see
|
||||
http://www.tele3.cz/jbar/rest/rest.html
|
||||
|
||||
===============================
|
||||
The Title of Your Specification
|
||||
===============================
|
||||
|
||||
Introduction paragraph -- why are we doing anything?
|
||||
|
||||
Problem Description
|
||||
===================
|
||||
|
||||
A detailed description of the problem.
|
||||
|
||||
Proposed Change
|
||||
===============
|
||||
|
||||
Here is where you cover the change you propose to make in detail. How do you
|
||||
propose to solve this problem?
|
||||
|
||||
If this is one part of a larger effort make it clear where this piece ends. In
|
||||
other words, what's the scope of this effort?
|
||||
|
||||
What versions of the operating system are affected or required?
|
||||
|
||||
What versions of OpenStack are affected or required?
|
||||
|
||||
What version of Juju is required?
|
||||
|
||||
Alternatives
|
||||
------------
|
||||
|
||||
This is an optional section, where it does apply we'd just like a demonstration
|
||||
that some thought has been put into why the proposed approach is the best one.
|
||||
|
||||
Implementation
|
||||
==============
|
||||
|
||||
Assignee(s)
|
||||
-----------
|
||||
|
||||
Who is leading the writing of the code? Or is this a blueprint where you're
|
||||
throwing it out there to see who picks it up?
|
||||
|
||||
If more than one person is working on the implementation, please designate the
|
||||
primary author and contact.
|
||||
|
||||
Primary assignee:
|
||||
<launchpad-id or None>
|
||||
|
||||
Can optionally list additional ids if they intend on doing substantial
|
||||
implementation work on this blueprint.
|
||||
|
||||
Gerrit Topic
|
||||
------------
|
||||
|
||||
Use Gerrit topic "<topic_name>" for all patches related to this spec.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
git-review -t <topic_name>
|
||||
|
||||
Work Items
|
||||
----------
|
||||
|
||||
Work items or tasks -- break the feature up into the things that need to be
|
||||
done to implement it. Those parts might end up being done by different people,
|
||||
but we're mostly trying to understand the timeline for implementation.
|
||||
|
||||
Repositories
|
||||
------------
|
||||
|
||||
Will any new git repositories need to be created?
|
||||
|
||||
Identify all new charm repos, interface repos, layer repos, whether new or
|
||||
existing, which will be affected or involved directly in the work which is
|
||||
defined by this spec.
|
||||
|
||||
Documentation
|
||||
-------------
|
||||
|
||||
Will this require a documentation change? If so, which documents?
|
||||
Will it impact developer workflow? Will additional communication need
|
||||
to be made?
|
||||
|
||||
Identify the surface area of doc updates explicitly, ie. charm-guide,
|
||||
deployment-guide, charm README, wiki page links.
|
||||
|
||||
Security
|
||||
--------
|
||||
|
||||
Does this introduce any additional security risks, or are there
|
||||
security-related considerations which should be discussed?
|
||||
|
||||
Testing
|
||||
-------
|
||||
|
||||
What tests will be available or need to be constructed in order to
|
||||
validate this? Unit/functional tests, development
|
||||
environments/servers, etc.
|
||||
|
||||
Are there any special hardware requirements to test this?
|
||||
|
||||
Dependencies
|
||||
============
|
||||
|
||||
- Include specific references to specs and/or stories, or in
|
||||
other projects, that this one either depends on or is related to.
|
||||
|
||||
- Does this feature require any new library or program dependencies
|
||||
not already in use?
|
||||
|
||||
- What are the plans to package and distribute the payload and/or
|
||||
dependencies?
|
||||
|
|
@ -9,7 +9,7 @@
|
|||
Cinder subordinate charm cinder-lvm
|
||||
===================================
|
||||
|
||||
Problem description
|
||||
Problem Description
|
||||
===================
|
||||
|
||||
Cinder has a great number of drivers for different backends. Almost all
|
||||
|
|
@ -53,10 +53,10 @@ Assignee(s)
|
|||
-----------
|
||||
|
||||
Primary assignee:
|
||||
Andre Ruiz <andre.ruiz@canonical.com> - Launchpad ID: andre-ruiz
|
||||
Andre Ruiz <andre.ruiz@canonical.com> - LP ID: andre-ruiz
|
||||
|
||||
Secondary assignee:
|
||||
Luciano Lo Giudice <luciano.logiudice@canonical.com> - Launchpad ID: lmlogiudice
|
||||
Luciano Lo Giudice <luciano.logiudice@canonical.com> - LP ID: lmlogiudice
|
||||
|
||||
Gerrit Topic
|
||||
------------
|
||||
|
|
@ -12,9 +12,9 @@
|
|||
http://sphinx-doc.org/rest.html To test out your formatting, see
|
||||
http://www.tele3.cz/jbar/rest/rest.html
|
||||
|
||||
================================================================================
|
||||
Sharing SSH authentication credentials across cloud-compute-related applications
|
||||
================================================================================
|
||||
======================================================================
|
||||
Sharing SSH auth credentials across cloud-compute-related applications
|
||||
======================================================================
|
||||
|
||||
Some cloud environments require different configuration settings
|
||||
(e.g. allocation ratios) for different hosts, yet still need to allow
|
||||
|
|
@ -108,7 +108,8 @@ Primary assignee:
|
|||
Gerrit Topic
|
||||
------------
|
||||
|
||||
Use Gerrit topic "migration-ssh-auth-sharing" for all patches related to this spec.
|
||||
Use Gerrit topic "migration-ssh-auth-sharing" for all patches related to this
|
||||
spec.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
Loading…
Reference in New Issue