On Fri, Feb 10, 2017 at 2:56 PM, Gianluca Cecchi
wrote:
> On Fri, Feb 10, 2017 at 2:27 PM, Martin Perina wrote:
>
>> Hi Gianluca,
>>
>> so generally speaking when host is in Maintenance status, engine doesn't
>> communicate with this host, so you
On Fri, Feb 10, 2017 at 2:27 PM, Martin Perina wrote:
> Hi Gianluca,
>
> so generally speaking when host is in Maintenance status, engine doesn't
> communicate with this host, so you can do pretty much anything about it.
>
Thanks for the detailed answer, Martin.
It seemed to
Hi Gianluca,
so generally speaking when host is in Maintenance status, engine doesn't
communicate with this host, so you can do pretty much anything about it.
About the upgrade flow (host 4.0 -> 4.1), here's proper way(s) how to
achieve that:
1. Put host to Maintenance
2. Add 4.1 repositories
On 9 February 2017 at 10:08, Gianluca Cecchi
wrote:
> On Wed, Feb 8, 2017 at 10:59 AM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> Hello,
>> what is considered the best way to shutdown and restart an hypervisor,
>> supposing plain CentOS 7 host?
>>
>>
Adding some people
On Thu, Feb 9, 2017 at 2:08 PM, Gianluca Cecchi
wrote:
> On Wed, Feb 8, 2017 at 10:59 AM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> Hello,
>> what is considered the best way to shutdown and restart an hypervisor,
>> supposing plain
On Wed, Feb 8, 2017 at 10:59 AM, Gianluca Cecchi
wrote:
> Hello,
> what is considered the best way to shutdown and restart an hypervisor,
> supposing plain CentOS 7 host?
>
> For example to cover these scenarios:
> 1) update host from 4.0 to 4.1
> 2) planned
Hello,
what is considered the best way to shutdown and restart an hypervisor,
supposing plain CentOS 7 host?
For example to cover these scenarios:
1) update host from 4.0 to 4.1
2) planned maintenance to the cabinet where the server is located and take
the opportunity to update also OS packages
7 matches
Mail list logo