On Mon, Aug 24, 2020 at 12:56 PM yam yam wrote:
> thank you Gianluca for the good link.
> it was really helpful and, they are really different considering the
> notion.
>
> but as "OpenStack" implements many features not only for cloud but also
> for traditional workload, I guess it's also good
thank you Gianluca for the good link.
it was really helpful and, they are really different considering the notion.
but as "OpenStack" implements many features not only for cloud but also for
traditional workload, I guess it's also good fit for traditional workload.
So, I'm wondering whether
Il Gio 20 Ago 2020, 10:08 Luca 'remix_tj' Lorenzetto <
lorenzetto.l...@gmail.com> ha scritto:
> On Thu, Aug 20, 2020 at 10:02 AM yam yam wrote:
> >
> > thanks, Luca
> >
> > As you said, I thought they have different use cases like pets vs cattle.
> > but as OpenStack supports many features(like
On Thu, Aug 20, 2020 at 10:02 AM yam yam wrote:
>
> thanks, Luca
>
> As you said, I thought they have different use cases like pets vs cattle.
> but as OpenStack supports many features(like live migration, snapshot, vm HA,
> ...), it "I guess" seems to encompass what oVirt can do.
>
> so is
thanks, Luca
As you said, I thought they have different use cases like pets vs cattle.
but as OpenStack supports many features(like live migration, snapshot, vm HA,
...), it "I guess" seems to encompass what oVirt can do.
so is there any specific use case oVirt only covers??
Hello
On Thu, Aug 20, 2020 at 6:41 AM yam yam wrote:
>
> Hi guys,
>
> I'm wondering why people say oVirt is better suited for traditional workloads
> like long-lived VMs than OpenStack.
> does oVirt have some additional features for it?
oVirt is a traditional hypervisor, for "traditional"
6 matches
Mail list logo
