And to clarify for those who haven't been watching the play-by-play as this
has unfolded for other OpenStack projects: we will continue to use
launchpad for project management and bug tracking. It is the code hosting
and review capabilities that will be shifted from launchpad to github (code
host
Hey everyone..
I just wanted to send a heads up based on the IRC meeting this week
that we'll be moving to github friday (9/16) at 9am-ish PST. If there
is any big concerns please raise them now before it's too late :) For
any setup questions or hurdles please send them to the list so that
other
Hi Ying,
I'm actually dealing with some of the same questions with respect to the
general quantum documentation. My thinking is that the main documentation
will have certain points where there are links to external, plugin-specific
documentation. For example, in the section about setting up Quan
Hi Salvatore,
Just want to double check with you. Vendor specific extension will not
be added into this API documentation, right?
If needed, we can provide that part. Otherwise, we will keep it within
our document.
Best,
Ying
From: netstack-bounces+yinliu2=cisco@lists.launchpad.n
All major openstack projects seem to be heading in the direction of keeping
their API documentation in a separate repo.
Salvatore, what are your thoughts on taking this approach with Quantum? Any
one else see pluses or minus, other than the obvious benefit of mapping to
what other OpenStack proje
Just in case you want to have a look at the work-in-progress (maybe for giving
an early feedback), the branch is located at:
lp:~salvatore-orlando/quantum/quantum-api-doc
Regards,
Salvatore
From: Rajaram Mallya [mailto:rajarammal...@gmail.com]
Sent: 14 September 2011 17:27
To: Salvatore Orlando
Yep. I was thinking of doing the same thing :-)
On 14-Sep-2011 9:45 PM, "Salvatore Orlando"
wrote:
> Thanks Rajaram!
>
> If that is ok for you, I was thinking that maybe you could edit the XML
file and then send it to back to me, so that I can include it in the larger
docbook file.
>
> Cheers,
>
Thanks Rajaram!
If that is ok for you, I was thinking that maybe you could edit the XML file
and then send it to back to me, so that I can include it in the larger docbook
file.
Cheers,
Salvatore
From: Rajaram Mallya [mailto:rajarammal...@gmail.com]
Sent: 14 September 2011 17:08
To: Salvatore
Glad to help. We can add to the documentation around the general extension
mechanism and the plugin aware behavior.
On Wed, Sep 14, 2011 at 9:02 PM, Salvatore Orlando <
salvatore.orla...@eu.citrix.com> wrote:
> Hi Netstackers,
>
> ** **
>
> While I’m completing the operation list on the API
Hi Netstackers,
While I'm completing the operation list on the API documentation book, I'd be
glad if I could get some help into adding a section on extensions.
Other services, such as nova-compute, have a section describing
how to fetch the extension list and details for each registered extens
10 matches
Mail list logo
