Hi all,
sorry for being late to such an interesting thread.
I discussed almost this same issue (properly and programmatically
shutting down a complete oVirt environment in a way that also
guarantees a clean and easy power up later) privately with some friends
some time ago.
Please note that the is
On Wed, Sep 12, 2018 at 3:49 PM Gianluca Cecchi
wrote:
> On Wed, Sep 12, 2018 at 10:03 AM Simone Tiraboschi
> wrote:
>
>>
>>
>>> Does it mean that I have to run the ansible-playbook command from an
>>> external server and use as host in inventory the engine server, or does it
>>> mean that the a
On Wed, Sep 12, 2018 at 10:03 AM Simone Tiraboschi
wrote:
>
>
>> Does it mean that I have to run the ansible-playbook command from an
>> external server and use as host in inventory the engine server, or does it
>> mean that the ansible-playbook command is to be run from within the server
>> wher
On Tue, Sep 11, 2018 at 5:28 PM Gianluca Cecchi
wrote:
> On Sun, Sep 9, 2018 at 10:15 AM Simone Tiraboschi
> wrote:
>
>> Now we have a specific ansible role for that:
>> https://github.com/oVirt/ovirt-ansible-shutdown-env
>>
>>
> Nice to see this Simone, thanks.
> I'm reading the info to try on
On Sun, Sep 9, 2018 at 10:15 AM Simone Tiraboschi
wrote:
> Now we have a specific ansible role for that:
> https://github.com/oVirt/ovirt-ansible-shutdown-env
>
>
Nice to see this Simone, thanks.
I'm reading the info to try on an hosted engine setup and find this:
"
This role has be des
On Fri, Sep 7, 2018 at 11:47 AM Gianluca Cecchi
wrote:
> Hello,
> I'm writing a workflow regarding operations to do in case of planned
> maintenance where one has to stop all hypervisors and so also hosted engine
> vm.
> At the moment I have imagined:
> - shutdown all VMs but Hosted Engine
> - pu
6 matches
Mail list logo
