[Users] Designate Master Storage Domain

[Dead Horse]

I agree Itamar.
That would actually be the most optimal situation. Freedom in storage
domain types and ability to import or export any given storage domain
freely. Along with this more freedom in the image types allowed on
file-based storage domains as well (EG: not only raw).


On Thu, Aug 15, 2013 at 12:30 PM, Itamar Heim <iheim at redhat.com> wrote:

> On 08/15/2013 07:32 PM, Dead Horse wrote:
>
>> +1 to Adding a "Make Master Storage Domain Button" ;-)
>>
>
> actually, not sure i'm for this.
> if anything, we want to get rid of the master storage domain going forward
> to make the storage domains autonomous, allowing to mix and match storage
> types, local and shared storage, etc...
>
> rhev-m may reconstruct the master storage domain on any of your SDs over
> time automatically
>
>
>>
>> On Thu, Aug 15, 2013 at 11:09 AM, Liron Aravot <laravot at redhat.com
>> <mailto:laravot at redhat.com>> wrote:
>>
>>
>>
>>     ----- Original Message -----
>>      > From: "Dead Horse" <deadhorseconsulting at gmail.com
>>     <mailto:deadhorseconsulting@**gmail.com<deadhorseconsulting at gmail.com>
>> >>
>>      > To: "Itamar Heim" <iheim at redhat.com <mailto:iheim at redhat.com>>
>>      > Cc: "<users at ovirt.org <mailto:users at ovirt.org>>" <users at ovirt.org
>>     <mailto:users at ovirt.org>>
>>      > Sent: Thursday, August 15, 2013 6:46:00 PM
>>      > Subject: Re: [Users] Designate Master Storage Domain
>>      >
>>      > Itamar this is true (I have noted occasional timing issues with
>>     it actually
>>      > working).
>>      > But what if as the administrator I have a specific storage domain
>>     in mind
>>      > that I would like to have become the master (in the case of more
>>     then two)?
>>
>>     In that case - you could reinitialize the pool using unattached
>>     domain (you chose which one) - this domain will become the new master.
>>     1. Create new unattached domain/Detach the domain that you want to
>>     be the master from the pool (if possible)
>>     2. Move all the pool domain to maintenance (the master should be put
>>     to maintenance last to avoid reconstructing to another domain).
>>     3. Right click on the data center, chose reinitialize storage pool -
>>     you can chose which domain do you want to be the master from the
>>     unattached domains.
>>
>>     The other option is manual db intervention :)
>>     Possibly we could add a possibility to manually change the master
>>     domain, same as was added for the spm ("Make SPM" button that was
>>     added recently).
>>
>>
>>      >
>>      > @Karli
>>      > The idea is not to not have to shut down all the VM's or the
>>     engine just to
>>      > maintenance a storage domain(s) that may happen to be on
>>     disparate storage
>>      > servers
>>      > .
>>      > - DHC
>>      >
>>      >
>>      > On Thu, Aug 15, 2013 at 9:37 AM, Itamar Heim < iheim at redhat.com
>>     <mailto:iheim at redhat.com> > wrote:
>>      >
>>      >
>>      >
>>      > On 08/15/2013 06:18 AM, Dead Horse wrote:
>>      >
>>      >
>>      >
>>      > Is there any method of designating which domain should be the
>> master
>>      > storage domain or forcibly changing the role to a different
>>     storage domain?
>>      >
>>      > EG: Given the following example
>>      >
>>      > Storage Domain A (Master) --> NFS --> Storage Server 1
>>      > Storage Domain B --> NFS --> Storage Server 2
>>      >
>>      > One wants to do maintenance to Storage Server 1 but in doing so the
>>      > Master storage domain is hosted from Storage Server 1. Thus the net
>>      > result of taking down Storage Server 1 is that one must also take
>>     down
>>      > Storage Server 2.
>>      >
>>      > Thus we know we must shut down VM's from Storage Domain A to
>>     maintenance
>>      > Storage Server 1. Suppose however that VM's are running that we
>> don't
>>      > want to shut down and are hosted from Storage Domain B via
>>     Storage Server 2.
>>      >
>>      > We would want to be able to promote Storage Domain B to Master so
>>     that
>>      > we can take down Storage Domain A to do maintenance to Storage
>>     Server 1.
>>      >
>>      > Once we are done with maintenance to Storage Server 1 we can bring
>>      > Storage Domain A back on line, re-designate it as Master if
>>     desired and
>>      > bring it's VM's back online.
>>      >
>>      > I know I have seen this occur automatically to a point when a
>> Storage
>>      > Domain goes missing that is the Master Domain but I have not
>>     noted any
>>      > manual method of doing so given the above scenario.
>>      >
>>      > - DHC
>>      >
>>      >
>>      > ______________________________ _________________
>>      > Users mailing list
>>      > Users at ovirt.org <mailto:Users at ovirt.org>
>>
>>      > http://lists.ovirt.org/ mailman/listinfo/users
>>      >
>>      >
>>      > my understanding is you can move the storage domain A which is
>>     master to
>>      > maint. engine will promote storage domain B to master and
>>     everything should
>>      > continue working as is.
>>      >
>>      >
>>      > ______________________________**_________________
>>      > Users mailing list
>>      > Users at ovirt.org <mailto:Users at ovirt.org>
>>      > http://lists.ovirt.org/**mailman/listinfo/users<http://lists.ovirt.org/mailman/listinfo/users>
>>      >
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20130815/0e770524/attachment-0001.html>