Description of problem: Currently the guide provides independent instructions for installing and configuring glance and swift. This is great from the point of view of providing flexible deployment options but we never actually tell the reader how to connect the two together. In the glance chapter we need to make it clear that if they want to use a swift backend they need to also go and configure swift. We should also provide details on what they need to do on the glance side to make use of that configuration once it is ready. The alternative here is to re-order the chapters - I suspect the reason they are the way they are though is to get people from nothing to running a compute instance as fast as possible. We also need to highlight what storage backend is used when swift isn't, and where the images are stored in that case. Thanks to Marc Jadoul for reporting this issue. Additional info: "I supposed glance would use swift. But Glance is configured and tested first and Swift after.... May be I messed something, but is seems Glance use file instead? Figure 1.1 indicate it use swift. Where is that configured?"
Forgot to note, with regards to figure 1.1 it needs to be updated to indicate that configuration of swift for image storage is optional (though probably recommended).
commit e72e19e1e22b9d28ec8999ce9eafc32d9d8b1ba4 Author: Stephen Gordon <sgordon> Date: Wed Mar 27 15:06:31 2013 -0400 BZ#923845 - Added steps for using Swift backend to Glance Added steps for using Swift backend to Glance chapter. Moved Swift chapter ahead of the rest after confirming with developers that it does not require Qpid or any other supporting services except for Keystone. This was done to ensure Swift is actually available when the time comes to configure Glance. Change-Id: I7b7a562b97680f6534f904bc3750db3d1ec45c3b