<br><br><div class="gmail_quote">On Thu, Aug 2, 2012 at 6:02 AM, Razique Mahroua <span dir="ltr"><<a href="mailto:razique.mahroua@gmail.com" target="_blank">razique.mahroua@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Hi guys, <div>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. </div>
</div></blockquote><div><br></div><div>Interesting, I hadn't thought of Glance as a "storage" option but it does store and retrieve images so I guess it could be thought of that way. I see it more as Storage: block or object. Then you have decisions to make about what you store your images in - block or object storage or just on disk on your cloud controller I guess? </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Though, since both could be deployed autonomously, it could be more a "data management " category ?</div>
<div>or "Data storing" ? glance being originally designated as the "imaging service "</div><div>Same goes for Cinder actually </div></div></blockquote><div><br></div><div>Right, and the Ceph project confuses me too so that'll be a tough one to sort out. :) I started bringing in that long blog entry and just wasn't sure whether to bring it all in or not. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div></div><div>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.</div>
</div></blockquote><div><br></div><div>Now that's interesting - I don't think it should be its own top-level topic, but shared modules/chapters throughout. Anyone else have opinions on the Identity portion?</div>
<div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>BTW : any news about Atlas ?</div><div>that ring a (weak) bell, but not so sure</div>
</div></blockquote><div><br></div><div>Atlas was a load balancing project, and I think the new load balancing project is going to use the Atlas API spec. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><br></div><div>Razique</div><div><br></div><div><div><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:'Lucida Grande';word-spacing:0px"><span style="font-family:Helvetica"><span style="font-family:Helvetica"><b style="color:rgb(19,112,138)">Nuage & Co - Razique Mahroua</b></span><span style="color:rgb(19,112,138);font-family:Helvetica"><b> </b></span><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="border-collapse:separate;font-variant:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="border-collapse:separate;font-variant:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="font-style:normal;font-size:medium;font-family:Helvetica;font-weight:normal">
<font color="#13708a"><a href="mailto:razique.mahroua@gmail.com" target="_blank">razique.mahroua@gmail.com</a></font></div></span><br><span></span><span style="font-style:normal;font-size:medium;font-family:Helvetica;font-weight:normal"></span><span style="font-weight:normal"></span></span><span><img height="125" width="125" src="cid:00E07450-433E-43E6-9005-48B8FD5C669F@la.fabrique"></span>
</span></span></span></div>
<br><div><div>Le 28 juil. 2012 à 05:51, Lorin Hochstein <<a href="mailto:lorin@nimbisservices.com" target="_blank">lorin@nimbisservices.com</a>> a écrit :</div><div><div class="h5"><br><blockquote type="cite"><div style="word-wrap:break-word">
<div><div>On Jul 26, 2012, at 9:48 AM, Anne Gentle <<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</a>> wrote:</div><br><blockquote type="cite">Hi all -<br>I'd like to propose an approach to the organization of the docs site<br>
centered around three "needs" for readers:<br><br>Compute<br>Networking<br>Storage</blockquote></div></div></blockquote></div></div></div><div><div class="h5"><div><blockquote type="cite"><div style="word-wrap:break-word">
<div><blockquote type="cite"><br>I believe the benefits of this top-level approach give us reuse of<br>content and easier finding of what people seek. It's not a huge<br>refactoring since I see it as:<br><br>Compute Administration<br>
Networking Administration<br>Storage Administration<br></blockquote></div></div></blockquote><blockquote type="cite"><div style="word-wrap:break-word"><div><blockquote type="cite"><br>While these books do exist, the need is in the content itself to be<br>
modular so it can be shared. For example, the Storage Administration<br>guide only describes Object Storage, not Block Storage.<br><br></blockquote><div><br></div><div>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.</div>
</div></div></blockquote><br></div></div></div><div><br><blockquote type="cite"><div><div class="h5"><div style="word-wrap:break-word"><div><blockquote type="cite">One concern is I don't want to confuse Object Storage (Swift)<br>
operators by inserting a lot of Volume information where they don't<br>need it. But I do believe that we need to round out the coverage of<br>documentation.<br><br></blockquote><div><br></div><div>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.</div>
<div><br></div><div><br></div><blockquote type="cite">This question leads into, how do we document installing and<br>configuring networking WITH computing (quantum with nova)? How are<br>people getting this information now?<br>
<br></blockquote><div><br></div><div>This is something I'd like to know as well. How do you configure quantum? Or how about cinder?</div><div><br></div><br><blockquote type="cite">I'd love some feedback on how to move forward with the addition of<br>
core projects but the lack of integrated how-to-configure<br>documentation. I'll be happy to propose a patch with the refactor, but<br>it will mean less patching of Essex, I believe.<br><br>Thanks for your input,<br>
Anne<br>
</blockquote></div><div><br></div><div>I fear we'll probably have to troll through the devstack source. :(</div><br><div><br></div><div><div><span style="border-collapse:separate;border-spacing:0px"><div style="word-wrap:break-word">
<span style="border-collapse:separate;border-spacing:0px"><div style="word-wrap:break-word"><div>Take care,</div><div><br></div><div>Lorin</div><div>--</div><div>Lorin Hochstein</div><div>Lead Architect - Cloud Services</div>
<div>Nimbis Services, Inc.</div><div><a href="https://www.nimbisservices.com/" target="_blank">www.nimbisservices.com</a></div><div><br></div></div></span><br></div><br></span><br></div><br><div></div></div></div></div></div>
_______________________________________________<br>Openstack-docs mailing list<br><a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</blockquote></div><br></div></div></blockquote></div><br>