I would go with 2nd aproach - I don't expect "same" issues actually - you
can either add a new pod/cluster or just new cluster in same pod.
On Fri, 14 Jun 2019 at 21:25, Alejandro Ruiz Bermejo <
arbermejo0...@gmail.com> wrote:
> I created a new zone, pod and cluster and added the LXC host to the
Hi Thomas,
I wrote about this global parameter(network.lock.timeout) in previous
message. I set it to 2000, but still seeing message "Timed out on acquiring
lock account2 . Waited for 300seconds" in logs.
пт, 14 июн. 2019 г. в 15:50, Thomas Joseph :
> check your settings in the global
I created a new zone, pod and cluster and added the LXC host to the new
cluster. CloudStack did everything for me. Since i am in a test environment
i used the same subnet for both zones.
I can do 2 things:
1. I will wipe the host and do a fresh install(only on the compute host),
but i will
I'm not sure how you moved the host to another Zone ? (Please describe)
But anyway, I would wipe that host (perhaps some settings are kept locally,
etc), and add it as a fresh host to a new cluster (could be in same Pod as
well, ot a new one).i.e. start from scratch please - since your setup
Yes trying to find solutions i did create a new zone pod and cluster and
moved the lxc host to it, but i had the same errors. So i moved it back to
my original LXC cluster into my original zone. I guess thats why it shows
those records.
I made all the movements using the UI, it seems like the
this was the ouputs
mysql> SELECT storage_pool.id, storage_pool.name, storage_pool.uuid,
-> storage_pool.pool_type, storage_pool.created, storage_pool.removed,
-> storage_pool.update_time, storage_pool.data_center_id,
storage_pool.pod_id,
-> storage_pool.used_bytes,
right... based on logs, it used different sql to search for ZONE-wide
storage, execute this one please:
SELECT storage_pool.id, storage_pool.name, storage_pool.uuid,
storage_pool.pool_type, storage_pool.created, storage_pool.removed,
storage_pool.update_time, storage_pool.data_center_id,
Hi and thanks again for your help,
So i run the query with both level scopes of storage
with storage_pool.scope = 'CLUSTER'
output:
Empty set (0.00 sec)
with storage_pool.scope = 'ZONE'
Execute this one (from logs) against your DB - does it return/finds a
storage pool ?
SELECT storage_pool.id, storage_pool.name, storage_pool.uuid,
storage_pool.pool_type, storage_pool.created, storage_pool.removed,
storage_pool.update_time, storage_pool.data_center_id, storage_pool.pod_id,
Long time no see Darrin - "Welcome to the jungle" !
On Fri, 14 Jun 2019 at 11:53, Sven Vogel wrote:
> Welcome Darrin!
>
> > Am 13.06.2019 um 20:12 schrieb Suresh Kumar Anaparti <
> sureshkumar.anapa...@gmail.com>:
> >
> > Hi Darrin, Welcome to CloudStack!
> >
> > Regards,
> > Suresh
> >
> > On
Hi there,
everybody trying to sell you something will actually tell that their
product is the best...
Having that in mind (and since I'm not trying to sell you anything), there
are a couple of things:
1. Dead easy to deploy (weeks) versus months/years for OpenStack (i.e.
"turnkey" solution,
+1
Based on:
- Packages from http://packages.shapeblue.com/testing/41130rc1/ and
http://packages.shapeblue.com/testing/systemvm/41130rc1/
- Upgrade of our test cloud from 4.11.2 to 4.11.3 worked without problems
(aside from the mentioned template issue)
- Our internal smoke test stack ran
So, I think it's ok to leave this issue aside.
I have a suspicion why the templates don't get upgraded, but since we know how
to fix them manually, it's not release critical.
We'll open a ticket later.
From: Rohit Yadav
Sent: 13 June 2019 12:49:40
To: dev;
check your settings in the global parameters for:
network.lock.timeout Lock wait timeout (seconds) while implementing network
On Fri, Jun 14, 2019 at 1:07 PM Dmitry Berezhnoy
wrote:
> Somebody else can help? We also increased network.lock.timeout but it was
> useless.
>
> ср, 12 июн. 2019 г. в
Somebody else can help? We also increased network.lock.timeout but it was
useless.
ср, 12 июн. 2019 г. в 00:40, Andrija Panic :
> Based on the "
>
>
On 2019/06/13 10:26:14, Nux! wrote:
> Hello,
>
> 1. You can use terraform (or/and ansible) for this.
> 2. No such thing, but again you can leverage some DIY, terraform, ansible etc
> to achieve the same.
>
> Also, Cloudstack has a great thing going for it which you can't find in
>
Welcome Darrin!
> Am 13.06.2019 um 20:12 schrieb Suresh Kumar Anaparti
> :
>
> Hi Darrin, Welcome to CloudStack!
>
> Regards,
> Suresh
>
> On Thu, Jun 13, 2019 at 5:44 PM Darrin Hüsselmann <
> darrin.husselm...@shapeblue.com> wrote:
>
>> Hi All,
>>
>>
>> I have joined Shapeblue as a
Hi Andrija + Rohit,
Yes, as far as I can tell, we followed the upgrade instructions to the letter -
except for the version.
The instructions still mention systemvm-vmware-4.11.2, we named the new
template systemvm-vmware-4.11.3 instead.
After upgrading the packages, my colleague checked,
Welcome Darrin!
Regards,
Abhishek Kumar
From: Darrin Hüsselmann
Sent: 13 June 2019 17:44
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Hello
Hi All,
I have joined Shapeblue as a software engineer and look forward to contributing
to
19 matches
Mail list logo
