Open Stack

Hi guys, 
the confusing thing about "Storage" is that there are two (maybe more to come) projects - swift and Glance. Storage is rather an abstract term when it comes to those services since both can operate the same way datas, but both serve originally different purposes. 
Though, since both could be deployed autonomously, it could be more a "data management " category ?
or "Data storing" ? glance being originally designated as the "imaging service "
Same goes for Cinder actually 

As for keystone, I think it could have its own topic, being the only one all the OPS services aim to/ should use from now on.

BTW : any news about Atlas ?
that ring a (weak) bell, but not so sure

Razique

Nuage & Co - Razique Mahroua  
razique.mahroua at gmail.com



Le 28 juil. 2012 à 05:51, Lorin Hochstein <lorin at nimbisservices.com> a écrit :

> On Jul 26, 2012, at 9:48 AM, Anne Gentle <anne at openstack.org> wrote:
> 
>> Hi all -
>> I'd like to propose an approach to the organization of the docs site
>> centered around three "needs" for readers:
>> 
>> Compute
>> Networking
>> Storage

>> 
>> I believe the benefits of this top-level approach give us reuse of
>> content and easier finding of what people seek. It's not a huge
>> refactoring since I see it as:
>> 
>> Compute Administration
>> Networking Administration
>> Storage Administration
>> 
>> While these books do exist, the need is in the content itself to be
>> modular so it can be shared. For example, the Storage Administration
>> guide only describes Object Storage, not Block Storage.
>> 
> 
> Sounds like a reasonable approach to me. Of course, there will be difficult choices ("Is glance part of Compute or Storage? Where does Keystone go, since it cuts across?") But, like David Weinberger says, "Everything is Miscellaneous". We'll just need to have good cross-reference links across the docs as needed.


>> One concern is I don't want to confuse Object Storage (Swift)
>> operators by inserting a lot of Volume information where they don't
>> need it. But I do believe that we need to round out the coverage of
>> documentation.
>> 
> 
> I think as long as block storage and object storage are clearly delineated, this will be fine. And Ceph crosses block and object storage, so it will have a clear home here.
> 
> 
>> This question leads into, how do we document installing and
>> configuring networking WITH computing (quantum with nova)? How are
>> people getting this information now?
>> 
> 
> This is something I'd like to know as well. How do you configure quantum? Or how about cinder?
> 
> 
>> I'd love some feedback on how to move forward with the addition of
>> core projects but the lack of integrated how-to-configure
>> documentation. I'll be happy to propose a patch with the refactor, but
>> it will mean less patching of Essex, I believe.
>> 
>> Thanks for your input,
>> Anne
> 
> 
> I fear we'll probably have to troll through the devstack source. :(
> 
> 
> Take care,
> 
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com
> 
> 
> 
> 
> 
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20120802/b9629515/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NUAGECO-LOGO-Fblan_petit.jpg
Type: image/jpeg
Size: 10122 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20120802/b9629515/attachment-0001.jpg>