ok, I did a quick read. But first; should this be in the 4.x docs and is it worth a jira issue?
The procedure seems simple but lengthy and for that reason error prone. I think some automation could help. I see several decisions on our path. - shall we let cloudstack do the copying? - shall we let cloudstack do the shutdown of management servers? - do we do a verify on the new mount? - what if ... the new storage is on the same server as the old, which needs to be updated or resized? - will an api call to change the secondary storage do more then just change the database entry? I am going to CCC and would like to sit down with some to discuss and pen down a couple of plans to throw in the user- and dev communities. Any takers? On Fri, May 31, 2013 at 10:48 AM, Prasanna Santhanam <t...@apache.org> wrote: > Looks like the section went missing in our 4.0 guides. But it's there > with the header: > > "Changing secondary storage" > > in http://download.cloud.com/releases/3.0.0/CloudStack3.0AdminGuide.pdf > > On Fri, May 31, 2013 at 10:39:00AM +0200, Daan Hoogland wrote: > > I've searched cloudstack.apache.org for 'secondary storage maintenance'. > > The procedure didn't catch my eye. Does anybody have a link for me? > > > > Thanks > > Daan > -- > Prasanna., > > ------------------------ > Powered by BigRock.com > >
