+dev
this is a considered blocker for an upgrade to 4.11.2 (at least for us):
https://github.com/apache/cloudstack/issues/2989
-- Forwarded message -
From: Jean-Francois Nadeau
Date: Mon, Nov 5, 2018 at 7:21 AM
Subject: Re: Problem creating networks after 4.11 upgrade
To
-1
Only because we believe this issue is a regression upgrading from 4.9.3.
Existing network offerings created under 4.9.3 should continue to work when
creating new networks under 4.11.2. Please see
https://github.com/apache/cloudstack/issues/2989
best,
Jfn
On Mon, Nov 5, 2018 at 5:04 AM Boris
Hi all,
Im kicking the tires with managed storage with under 4.11.2 with KVM and
Datera as primary storage.
My first attempt at creating a VM from a template stored on NFS secondary
failed silently. Looking at the SSVM cloud logs I saw no exception. The VM
root disks gets properly created on the
go except
> the way you use Solidfire. For KVM you must use NFS, S3 or Swift.
>
>
> вс, 3 мар. 2019 г. в 13:50, Jean-Francois Nadeau :
>
> > Hi all,
> >
> > Im kicking the tires with managed storage with under 4.11.2 with KVM and
> > Datera as primary sto
Kudryavtsev
wrote:
> Not sure, KVM works on arbitrary iSCSI target except the Solidfire.
>
> вс, 3 мар. 2019 г. в 14:10, Jean-Francois Nadeau :
>
> > Hi Ivan,
> >
> > SS is still on NFS in this case. It's the primary storage in trying to
> > move on isc
ta,
> unmount it and then create a VM using this volume
>
> Hope this helps
>
> Thanks,
> -Syed
>
> On Sun, Mar 3, 2019 at 2:48 PM Jean-Francois Nadeau <
> the.jfnad...@gmail.com>
> wrote:
>
> > I just found my problem in regards to the managed storage.
I can only agree with Haijiao, that 4.11 deserves a longer time span.
Because many bugs are found naturally between the .0 and .1 of the next LTS
release with it's adoption.
For us 4.11 could only be adopted with 4.11.2.0 after several bugs needed
to get resolved. So if 4.11's support stops in
Can we consider merging this fix in 4.11.3 as well ?For those like us
that would really want make to jump on qemu-ev versions but also want to
stick to CS LTS releases.
best,
Jfn
On Tue, Apr 23, 2019 at 6:54 AM Rohit Yadav
wrote:
> All,
>
>
> I've found and fixed an edge/security case whi
Hello Everyone,
I was wondering if it was common or even recommended to use an S3
compatible storage system as the only secondary storage provider ?
The environment is 4.11.3.0 with KVM (Centos 7.6), and our tier1 storage
solution also provides an S3 compatible object store (apparently Minio
und
nd such are used by the
> hosts.
>
> I think Pierre-Luc and Syed have a clearer picture of all the moving
> pieces, but that is a quick summary of what I know without digging in.
>
> Hope that helps.
>
> Cheers,
>
> Will
>
> On Tue, Jul 16, 2019, 10:24 PM Jean-Fra
Hi Li,
We are using Ansible to build and manage capacity of our cloudstack
environments end to end. From setting up zones, projects, networks,
compute offering, pods, clusters and hosts.
Make sure to use current Ansible 2.8 or newer. See
https://docs.ansible.com/ansible/latest/modules/list_of_
Hi Andrija,
We experienced that problem with stock packages on CentOS 7.4.Live
migration would frequently fail and leave the VM dead.We since moved to
RHEV packages for qemu. Libvirt is still stock per CentoS 7.6 (4.5). I
want to say the situation improved but I can't tell yet if we hav
- why all great things need to come to an end...damn it)
>
> (well I could also test same ACS code on Ubuntu and see if no issues there
> with live migrations..)
>
> Thanks
> Andrija
>
> On Thu, 21 Nov 2019 at 23:39, Jean-Francois Nadeau >
> wrote:
>
> > Hi
13 matches
Mail list logo
