Re: new primary storage

[Daan Hoogland]

sounds good Charlie, I hope you get a chance to upgrade soon.

On Mon, Feb 17, 2020 at 10:55 AM Charlie Holeowsky <
charlie.holeow...@gmail.com> wrote:

> Hi Daan and Users,
> I opened the issue on Github and found that this bug (#3181) was fixed on
> 4.13.0 release.
>
> Il giorno lun 3 feb 2020 alle ore 10:25 Daan Hoogland <
> daan.hoogl...@gmail.com> ha scritto:
>
>> thanks Charlie, can you take your issue to a github issue on the project
>> please? thanks
>>
>> On Mon, Feb 3, 2020 at 9:57 AM Charlie Holeowsky <
>> charlie.holeow...@gmail.com> wrote:
>>
>>> Hi Daan and users,
>>> Yes, I resolved the issue but it's only a work-around, I have found that
>>> the problem is reproducible but I do not understand if I am the only one to
>>> have noticed it and if there is another more elegant and definitive
>>> solution.
>>>
>>>
>>>
>>> Il giorno ven 31 gen 2020 alle ore 13:31 Daan Hoogland <
>>> daan.hoogl...@gmail.com> ha scritto:
>>>
>>>> sorry to not have any focus on this Charlie,
>>>> Do I read correctly that you resolved your issue?
>>>>
>>>> On Tue, Jan 28, 2020 at 2:46 PM Charlie Holeowsky <
>>>> charlie.holeow...@gmail.com> wrote:
>>>>
>>>>> In this period I have performed some testsand I found a workarount for
>>>>> the metrics problem.
>>>>> I created a test environment in the laboratory with the main
>>>>> characteristics equal to that of production (acs 4.11.2.0, all Ubuntu 
>>>>> 16.04
>>>>> OS, KVM, NFS as shared storage and advanced network). Then I added a 
>>>>> ubuntu
>>>>> 18.04 new primary storage.
>>>>>
>>>>> I create a new VM in the new storage server and and after a while the
>>>>> metrics appeared as on the first storage, so the storage is working.
>>>>>
>>>>> I destroyed this VM, I create a new one on the first (old) storage and
>>>>> then I migrate it on the new storage.
>>>>>
>>>>> After migrating the disk from the first primary storage to the second
>>>>> one i have encountered the same problem (same error on agent.log
>>>>> com.cloud.utils.exception.CloudRuntimeException: Can't find
>>>>> volume:5a521eb0...) and the volume metrics and metrics didn't appear or
>>>>> update.
>>>>>
>>>>> In this test environment I created a symbolic link in the filesystem
>>>>> of the storage server taking the name of the disk just migrated (the one
>>>>> with the name path) and the uuid name (the one that appear in error
>>>>> message).
>>>>>
>>>>>
>>>>> Here is an example to better explain me.
>>>>>
>>>>> I took the list of volumes where path is different from uuid which
>>>>> returns the data of the migrated volumes:
>>>>>
>>>>> mysql> select id,uuid,path from volumes where uuid!=path;
>>>>>
>>>>> ++--+--+
>>>>> | id | uuid | path
>>>>> |
>>>>>
>>>>> ++--+--+
>>>>> | 10 | 5a521eb0-266f-4353-b4b2-1d63a483e5b5 |
>>>>> 165b92ba-68f1-4172-be35-bbe1d032cb7c |
>>>>> | 12 | acb3bb29-9bac-4a2a-aefa-3c6ac1c2846b |
>>>>> 56aa3961-dbc2-4f98-9246-a7497eef3214 |
>>>>>
>>>>> ++------+--+
>>>>>
>>>>> In the storage server I make the symbolic links (ln -s  ):
>>>>>
>>>>> # ln
>>>>> -s 5a521eb0-266f-4353-b4b2-1d63a483e5b5 
>>>>> 165b92ba-68f1-4172-be35-bbe1d032cb7c
>>>>> # ln -s acb3bb29-9bac-4a2a-aefa-3c6ac1c2846b
>>>>> 56aa3961-dbc2-4f98-9246-a7497eef3214
>>>>>
>>>>> After doing this, I waited some time and then I found that metrics
>>>>> were updated and the message in agent.log no longer appeared.
>>>>>
>>>>>
>>>>> Il giorno gio 23 gen 2020 alle ore 17:53 Charlie Holeowsky <
>>>>> charlie.holeow...@gmail.com> ha scritto:
>>>>>
>>>>>> I still don't un

Re: new primary storage

[Daan Hoogland]

thanks Charlie, can you take your issue to a github issue on the project
please? thanks

On Mon, Feb 3, 2020 at 9:57 AM Charlie Holeowsky <
charlie.holeow...@gmail.com> wrote:

> Hi Daan and users,
> Yes, I resolved the issue but it's only a work-around, I have found that
> the problem is reproducible but I do not understand if I am the only one to
> have noticed it and if there is another more elegant and definitive
> solution.
>
>
>
> Il giorno ven 31 gen 2020 alle ore 13:31 Daan Hoogland <
> daan.hoogl...@gmail.com> ha scritto:
>
>> sorry to not have any focus on this Charlie,
>> Do I read correctly that you resolved your issue?
>>
>> On Tue, Jan 28, 2020 at 2:46 PM Charlie Holeowsky <
>> charlie.holeow...@gmail.com> wrote:
>>
>>> In this period I have performed some testsand I found a workarount for
>>> the metrics problem.
>>> I created a test environment in the laboratory with the main
>>> characteristics equal to that of production (acs 4.11.2.0, all Ubuntu 16.04
>>> OS, KVM, NFS as shared storage and advanced network). Then I added a ubuntu
>>> 18.04 new primary storage.
>>>
>>> I create a new VM in the new storage server and and after a while the
>>> metrics appeared as on the first storage, so the storage is working.
>>>
>>> I destroyed this VM, I create a new one on the first (old) storage and
>>> then I migrate it on the new storage.
>>>
>>> After migrating the disk from the first primary storage to the second
>>> one i have encountered the same problem (same error on agent.log
>>> com.cloud.utils.exception.CloudRuntimeException: Can't find
>>> volume:5a521eb0...) and the volume metrics and metrics didn't appear or
>>> update.
>>>
>>> In this test environment I created a symbolic link in the filesystem of
>>> the storage server taking the name of the disk just migrated (the one with
>>> the name path) and the uuid name (the one that appear in error message).
>>>
>>>
>>> Here is an example to better explain me.
>>>
>>> I took the list of volumes where path is different from uuid which
>>> returns the data of the migrated volumes:
>>>
>>> mysql> select id,uuid,path from volumes where uuid!=path;
>>>
>>> ++--+--+
>>> | id | uuid | path
>>>   |
>>>
>>> ++--+--+
>>> | 10 | 5a521eb0-266f-4353-b4b2-1d63a483e5b5 |
>>> 165b92ba-68f1-4172-be35-bbe1d032cb7c |
>>> | 12 | acb3bb29-9bac-4a2a-aefa-3c6ac1c2846b |
>>> 56aa3961-dbc2-4f98-9246-a7497eef3214 |
>>>
>>> ++--+--+
>>>
>>> In the storage server I make the symbolic links (ln -s  ):
>>>
>>> # ln
>>> -s 5a521eb0-266f-4353-b4b2-1d63a483e5b5 165b92ba-68f1-4172-be35-bbe1d032cb7c
>>> # ln -s acb3bb29-9bac-4a2a-aefa-3c6ac1c2846b
>>> 56aa3961-dbc2-4f98-9246-a7497eef3214
>>>
>>> After doing this, I waited some time and then I found that metrics were
>>> updated and the message in agent.log no longer appeared.
>>>
>>>
>>> Il giorno gio 23 gen 2020 alle ore 17:53 Charlie Holeowsky <
>>> charlie.holeow...@gmail.com> ha scritto:
>>>
>>>> I still don't understand
>>>> why com.cloud.hypervisor.kvm.storage.LibvirtStoragePool don't find the
>>>> volume d93d3c0a-3859-4473-951d-9b5c5912c76 that exists as file
>>>> 39148fe1-842b-433a-8a7f-85e90f316e04...
>>>>
>>>> It's the only anomaly I have found. Where can I look again?
>>>>
>>>> Il giorno lun 20 gen 2020 alle ore 16:27 Daan Hoogland <
>>>> daan.hoogl...@gmail.com> ha scritto:
>>>>
>>>>> but the record you send earlier also says that is should be looking
>>>>> for 39148fe1-842b-433a-8a7f-85e90f316e04, in the path field. the message
>>>>> might be just that, a message.
>>>>>
>>>>> On Mon, Jan 20, 2020 at 3:35 PM Charlie Holeowsky <
>>>>> charlie.holeow...@gmail.com> wrote:
>>>>>
>>>>>> I think that's the problem because in the logs that I have forwarded
>>>>>> it reads:
>>>>>> Can't find volume: d93d3c0a-3859-4473-951d-9b5c5912c76

Re: new primary storage

[Daan Hoogland]

sorry to not have any focus on this Charlie,
Do I read correctly that you resolved your issue?

On Tue, Jan 28, 2020 at 2:46 PM Charlie Holeowsky <
charlie.holeow...@gmail.com> wrote:

> In this period I have performed some testsand I found a workarount for the
> metrics problem.
> I created a test environment in the laboratory with the main
> characteristics equal to that of production (acs 4.11.2.0, all Ubuntu 16.04
> OS, KVM, NFS as shared storage and advanced network). Then I added a ubuntu
> 18.04 new primary storage.
>
> I create a new VM in the new storage server and and after a while the
> metrics appeared as on the first storage, so the storage is working.
>
> I destroyed this VM, I create a new one on the first (old) storage and
> then I migrate it on the new storage.
>
> After migrating the disk from the first primary storage to the second one
> i have encountered the same problem (same error on agent.log
> com.cloud.utils.exception.CloudRuntimeException: Can't find
> volume:5a521eb0...) and the volume metrics and metrics didn't appear or
> update.
>
> In this test environment I created a symbolic link in the filesystem of
> the storage server taking the name of the disk just migrated (the one with
> the name path) and the uuid name (the one that appear in error message).
>
>
> Here is an example to better explain me.
>
> I took the list of volumes where path is different from uuid which returns
> the data of the migrated volumes:
>
> mysql> select id,uuid,path from volumes where uuid!=path;
>
> ++--+--+
> | id | uuid | path
> |
>
> ++--+--+
> | 10 | 5a521eb0-266f-4353-b4b2-1d63a483e5b5 |
> 165b92ba-68f1-4172-be35-bbe1d032cb7c |
> | 12 | acb3bb29-9bac-4a2a-aefa-3c6ac1c2846b |
> 56aa3961-dbc2-4f98-9246-a7497eef3214 |
>
> ++--+--+
>
> In the storage server I make the symbolic links (ln -s  ):
>
> # ln
> -s 5a521eb0-266f-4353-b4b2-1d63a483e5b5 165b92ba-68f1-4172-be35-bbe1d032cb7c
> # ln -s acb3bb29-9bac-4a2a-aefa-3c6ac1c2846b
> 56aa3961-dbc2-4f98-9246-a7497eef3214
>
> After doing this, I waited some time and then I found that metrics were
> updated and the message in agent.log no longer appeared.
>
>
> Il giorno gio 23 gen 2020 alle ore 17:53 Charlie Holeowsky <
> charlie.holeow...@gmail.com> ha scritto:
>
>> I still don't understand
>> why com.cloud.hypervisor.kvm.storage.LibvirtStoragePool don't find the
>> volume d93d3c0a-3859-4473-951d-9b5c5912c76 that exists as file
>> 39148fe1-842b-433a-8a7f-85e90f316e04...
>>
>> It's the only anomaly I have found. Where can I look again?
>>
>> Il giorno lun 20 gen 2020 alle ore 16:27 Daan Hoogland <
>> daan.hoogl...@gmail.com> ha scritto:
>>
>>> but the record you send earlier also says that is should be looking for
>>> 39148fe1-842b-433a-8a7f-85e90f316e04, in the path field. the message might
>>> be just that, a message.
>>>
>>> On Mon, Jan 20, 2020 at 3:35 PM Charlie Holeowsky <
>>> charlie.holeow...@gmail.com> wrote:
>>>
>>>> I think that's the problem because in the logs that I have forwarded it
>>>> reads:
>>>> Can't find volume: d93d3c0a-3859-4473-951d-9b5c5912c767
>>>>
>>>> This is the volume ID of migrated file but it do not exist on primary
>>>> storage (new or old one) but it exist
>>>> as 39148fe1-842b-433a-8a7f-85e90f316e04.
>>>>
>>>> Il giorno lun 20 gen 2020 alle ore 12:35 Daan Hoogland <
>>>> daan.hoogl...@gmail.com> ha scritto:
>>>>
>>>>> also, can you see the primary storage being mounted?
>>>>>
>>>>>
>>>>> On Mon, Jan 20, 2020 at 12:33 PM Daan Hoogland <
>>>>> daan.hoogl...@gmail.com> wrote:
>>>>>
>>>>>> Why do you think that Charlie? Is it in the logs like that somewhere?
>>>>>>
>>>>>> On Mon, Jan 20, 2020 at 9:52 AM Charlie Holeowsky <
>>>>>> charlie.holeow...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Daan,
>>>>>>> in fact I find the volume file
>>>>>>> (39148fe1-842b-433a-8a7f-85e90f316e04) in the repositry id = 3 (the new
>>>>>>> one) but it seems to me that the cloudstack system goes looking for the
>>>>>>

Re: new primary storage

[Daan Hoogland]

also, can you see the primary storage being mounted?


On Mon, Jan 20, 2020 at 12:33 PM Daan Hoogland 
wrote:

> Why do you think that Charlie? Is it in the logs like that somewhere?
>
> On Mon, Jan 20, 2020 at 9:52 AM Charlie Holeowsky <
> charlie.holeow...@gmail.com> wrote:
>
>> Hi Daan,
>> in fact I find the volume file (39148fe1-842b-433a-8a7f-85e90f316e04) in
>> the repositry id = 3 (the new one) but it seems to me that the cloudstack
>> system goes looking for the volume with its "old" name (path) that doesn't
>> exist...
>>
>> Il giorno sab 18 gen 2020 alle ore 21:41 Daan Hoogland <
>> daan.hoogl...@gmail.com> ha scritto:
>>
>>> Charlie,
>>> forgive my not replying in a timely manner. This might happen if the
>>> disk was migrated. In this case probably from primary storage with id 1 to
>>> the one with id 3. the second record (pool_id 1) is removed, so you can
>>> ignore that one. The first seems legit. You should be able to find that
>>> disks on your primary storage with id 3.
>>> hope this helps.
>>>
>>> On Thu, Jan 16, 2020 at 2:07 PM Charlie Holeowsky <
>>> charlie.holeow...@gmail.com> wrote:
>>>
>>>> Hi Daan and users,
>>>> to better explain I show you the two records related to the disk that
>>>> generates the error message.
>>>>
>>>> In the first query there are the data of the disk currently in use
>>>> which has the "uuid" equal to the name searched by the procedure
>>>> com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.getPhysicalDiskand a
>>>> has a different "path" field.
>>>>
>>>> In the second one we note that the "path" field is equal to the "uuid"
>>>> of the volume in use but has null "uuid" (and state=Expunged).
>>>>
>>>>
>>>> mysql> select * from volumes where
>>>> uuid='d93d3c0a-3859-4473-951d-9b5c5912c767';
>>>>
>>>> +-++---+-+--+-+---+--+--+-+-+--++++-+-+---+--+-++-+-+--+-+-+---++--+---+++++--+--+---+---+
>>>> | id  | account_id | domain_id | pool_id | last_pool_id | instance_id |
>>>> device_id | name | uuid | size|
>>>> folder  | path | pod_id |
>>>> data_center_id | iscsi_name | host_ip | volume_type | pool_type |
>>>> disk_offering_id | template_id | first_snapshot_backup_uuid | recreatable |
>>>> created | attached | updated | removed | state |
>>>> chain_info | update_count | disk_type | vm_snapshot_chain_size | iso_id |
>>>> display_volume | format | min_iops | max_iops | hv_ss_reserve |
>>>> provisioning_type |
>>>>
>>>> +-++---+-+--+-+---+--+--+-+-+--++++-+-+---+--+-++-+-+--+-+-+---++--+---+++++--+--+---+---+
>>>> | 213 |  2 | 1 |   3 |1 | 148 |
>>>> 1 | DATA-148 | d93d3c0a-3859-4473-951d-9b5c5912c767 | 53687091200 |
>>>> /srv/primary | 39148fe1-842b-433a-8a7f-85e90f316e04 |   NULL |
>>>>  1 | NULL   | NULL| DATADISK| NULL  |   34 |
>>>>  NULL | NULL   |   0 | 2019-11-26 10:41:46
>>>> | NULL | 2019-11-26 10:41:50 | NULL| Ready | NULL   |
>>>>  2 | NULL  |   NULL |   NULL |  1 | QCOW2
>>>>  | NULL | NULL |  NULL | thin  |
>>>>
>>&

Re: new primary storage

[Daan Hoogland]

Why do you think that Charlie? Is it in the logs like that somewhere?

On Mon, Jan 20, 2020 at 9:52 AM Charlie Holeowsky <
charlie.holeow...@gmail.com> wrote:

> Hi Daan,
> in fact I find the volume file (39148fe1-842b-433a-8a7f-85e90f316e04) in
> the repositry id = 3 (the new one) but it seems to me that the cloudstack
> system goes looking for the volume with its "old" name (path) that doesn't
> exist...
>
> Il giorno sab 18 gen 2020 alle ore 21:41 Daan Hoogland <
> daan.hoogl...@gmail.com> ha scritto:
>
>> Charlie,
>> forgive my not replying in a timely manner. This might happen if the disk
>> was migrated. In this case probably from primary storage with id 1 to the
>> one with id 3. the second record (pool_id 1) is removed, so you can ignore
>> that one. The first seems legit. You should be able to find that disks on
>> your primary storage with id 3.
>> hope this helps.
>>
>> On Thu, Jan 16, 2020 at 2:07 PM Charlie Holeowsky <
>> charlie.holeow...@gmail.com> wrote:
>>
>>> Hi Daan and users,
>>> to better explain I show you the two records related to the disk that
>>> generates the error message.
>>>
>>> In the first query there are the data of the disk currently in use which
>>> has the "uuid" equal to the name searched by the procedure
>>> com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.getPhysicalDiskand a
>>> has a different "path" field.
>>>
>>> In the second one we note that the "path" field is equal to the "uuid"
>>> of the volume in use but has null "uuid" (and state=Expunged).
>>>
>>>
>>> mysql> select * from volumes where
>>> uuid='d93d3c0a-3859-4473-951d-9b5c5912c767';
>>>
>>> +-++---+-+--+-+---+--+--+-+-+--++++-+-+---+--+-++-+-+--+-+-+---++--+---+++++--+--+---+---+
>>> | id  | account_id | domain_id | pool_id | last_pool_id | instance_id |
>>> device_id | name | uuid | size|
>>> folder  | path | pod_id |
>>> data_center_id | iscsi_name | host_ip | volume_type | pool_type |
>>> disk_offering_id | template_id | first_snapshot_backup_uuid | recreatable |
>>> created | attached | updated | removed | state |
>>> chain_info | update_count | disk_type | vm_snapshot_chain_size | iso_id |
>>> display_volume | format | min_iops | max_iops | hv_ss_reserve |
>>> provisioning_type |
>>>
>>> +-++---+-+--+-+---+--+--+-+-+--++++-+-+---+--+-++-+-+--+-+-+---++--+---+++++--+--+---+---+
>>> | 213 |  2 | 1 |   3 |1 | 148 |
>>> 1 | DATA-148 | d93d3c0a-3859-4473-951d-9b5c5912c767 | 53687091200 |
>>> /srv/primary | 39148fe1-842b-433a-8a7f-85e90f316e04 |   NULL |
>>>  1 | NULL   | NULL| DATADISK| NULL  |   34 |
>>>  NULL | NULL   |   0 | 2019-11-26 10:41:46
>>> | NULL | 2019-11-26 10:41:50 | NULL| Ready | NULL   |
>>>  2 | NULL  |   NULL |   NULL |  1 | QCOW2
>>>  | NULL | NULL |  NULL | thin  |
>>>
>>> +-++---+-+--+-+---+--+--+-+-+

Re: new primary storage

[Daan Hoogland]

.execute(LibvirtRequestWrapper.java:78)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1450)
> at com.cloud.agent.Agent.processRequest(Agent.java:645)
> at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:1083)
> at com.cloud.utils.nio.Task.call(Task.java:83)
> at com.cloud.utils.nio.Task.call(Task.java:29)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 2020-01-14 09:25:15,259 INFO  [kvm.storage.LibvirtStorageAdaptor]
> (agentRequest-Handler-5:null) (logid:1a7e082e) Trying to fetch storage pool
> 9af0d1c6-85f2-3c55-94af-6ac17cb4024c from libvirt
> 2020-01-14 09:25:15,261 INFO  [kvm.storage.LibvirtStorageAdaptor]
> (agentRequest-Handler-5:null) (logid:1a7e082e) Asking libvirt to refresh
> storage pool 9af0d1c6-85f2-3c55-94af-6ac17cb4024c
>
>
> And here the management server log:
>
> 2020-01-14 09:21:27,105 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-2:null) (logid:) Seq 15-705657766613619075:
> Processing:  { Ans: , MgmtId: 220777304233416, via: 15, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
> Can't find volume:d93d3c0a-3859-4473-951d-9b5c5912c767\n\tat
> com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.getPhysicalDisk(LibvirtStoragePool.java:149)\n\tat
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtGetVolumeStatsCommandWrapper.getVolumeStat(LibvirtGetVolumeStatsCommandWrapper.java:63)\n\tat
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtGetVolumeStatsCommandWrapper.execute(LibvirtGetVolumeStatsCommandWrapper.java:52)\n\tat
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtGetVolumeStatsCommandWrapper.execute(LibvirtGetVolumeStatsCommandWrapper.java:40)\n\tat
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:78)\n\tat
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1450)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:645)\n\tat
> com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:1083)\n\tat
> com.cloud.utils.nio.Task.call(Task.java:83)\n\tat
> com.cloud.utils.nio.Task.call(Task.java:29)\n\tat
> java.util.concurrent.FutureTask.run(FutureTask.java:266)\n\tat
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat
> java.lang.Thread.run(Thread.java:748)\n","wait":0}}] }
> 2020-01-14 09:21:27,105 DEBUG [c.c.a.t.Request]
> (StatsCollector-6:ctx-fd801d0a) (logid:ec72387b) Seq 15-705657766613619075:
> Received:  { Ans: , MgmtId: 220777304233416, via: 15(csdell017), Ver: v1,
> Flags: 10, { Answer } }
> 2020-01-14 09:21:27,105 DEBUG [c.c.a.m.AgentManagerImpl]
> (StatsCollector-6:ctx-fd801d0a) (logid:ec72387b) Details from executing
> class com.cloud.agent.api.GetVolumeStatsCommand:
> com.cloud.utils.exception.CloudRuntimeException: Can't find
> volume:d93d3c0a-3859-4473-951d-9b5c5912c767
> at
> com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.getPhysicalDisk(LibvirtStoragePool.java:149)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtGetVolumeStatsCommandWrapper.getVolumeStat(LibvirtGetVolumeStatsCommandWrapper.java:63)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtGetVolumeStatsCommandWrapper.execute(LibvirtGetVolumeStatsCommandWrapper.java:52)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtGetVolumeStatsCommandWrapper.execute(LibvirtGetVolumeStatsCommandWrapper.java:40)
> at
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:78)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1450)
> at com.cloud.agent.Agent.processRequest(Agent.java:645)
> at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:1083)
> at com.cloud.utils.nio.Task.call(Task.java:83)
> at com.cloud.utils.nio.Task.call(Task.java:29)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
>
> on 09/01/20 12:58, Daan Hoogland wrote:
>
> Charlie, I think you'll have to explain a bit more about your environment
> to get an answer. what type of storage is it? Where did you migrate the VM
> from and to? What types() of hypervisors are you using? Though saying **the**
> agent logs suggests KVM, you are still leaving people guessing a lot.
>
>

-- 
Daan

Re: new primary storage

[Daan Hoogland]

Charlie, I think you'll have to explain a bit more about your environment
to get an answer. what type of storage is it? Where did you migrate the VM
from and to? What types() of hypervisors are you using? Though saying *the*
agent logs suggests KVM, you are still leaving people guessing a lot.

On Tue, Jan 7, 2020 at 6:54 PM Charlie Holeowsky <
charlie.holeow...@gmail.com> wrote:

> Hi all,
> on a host that use this new storage I found a problem that could be related
> to the fact that the statistics are not being updated.
>
> After migrating a newly created VM to the new storage server, a series of
> messages like the following appear in the agent logs:
>
> 2020-01-07 17:30:45,868 WARN  [cloud.agent.Agent]
> (agentRequest-Handler-2:null) (logid:c023b7f8) Caught:
> com.cloud.utils.exception.CloudRuntimeException: Can't find
> volume:d93d3c0a-3859-4473-951d-9b5c5912c767
> at
>
> com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.getPhysicalDisk(LibvirtStoragePool.java:149)
> at
>
> com.cloud.hypervisor.kvm.resource.wrapper.LibvirtGetVolumeStatsCommandWrapper.getVolumeStat(LibvirtGetVolumeStatsCommandWrapper.java:63)
>
> Looking for the volume uuid "d93d3c0a-3859-4473-951d-9b5c5912c767" I found
> that it belongs to the VM just migrated but has a different "path" column
> value (normally I see that the values of the two tables coincide).
>
> On the other hand, there is another record in the volumes table with uuid =
> NULL and path = d93d3c0a-3859-4473-951d-9b5c5912c767 with state=Expunged.
>
> Could this be the cause of the failure to update the volume data
> statistics?
>
> Il giorno mar 17 dic 2019 alle ore 15:32 charlie Holeowsky <
> charlie.holeow...@gmail.com> ha scritto:
>
> > Hi,
> > any idea about about this problem?
> >
> >
> > Il giorno mar 10 dic 2019 alle ore 17:23 charlie Holeowsky <
> > charlie.holeow...@gmail.com> ha scritto:
> >
> >> Hi users,
> >> I recently added a new primary nfs storage to my cluster (cloudstack
> >> 4.11.2 with kvm on the Ubuntu system).
> >>
> >> It works well but on the metrics of the VM storage volume the "physical
> >> size" and "usage" columns are empty while in the rows of the VM of the
> >> other primary storage I can see the right data.
> >>
> >> Where can i go to look to see where the problem is?
> >>
> >> Thanks
> >> Charlie
> >>
> >
>


-- 
Daan

Re: Create new role Domain Admin + VR Access

[Daan Hoogland]

Fernando,
Do you mean you want to give extra UI access or just the API? As you showed
the API access is the same already, but that does not change the UI and
shows extra tabs or so, You'll need to hack the javascript to have tabs
hidden or visible other than the defaults. (also I'd say upgrade from 4.9
if you can)

On Sun, Nov 17, 2019 at 8:54 PM Fernando Alvarez 
wrote:

> Hi everyone,
>
> I need to create a new role like Domain Admin role plus access to "virtual
> appliance" flap in network domain menu.
> No access to "Infrastructure" and "Global Settings" (is for level 2 support
> area).
> I tried comparing the list of permissions of the "Domain Admin" and
> "Resource Admin" role related to the virtual router but I can't find a
> difference between them:
>
> (Arsat-Prod) 🐵 > list rolepermissions | grep -i router
> Domain
>
> Admin,bdb84ac5-8b90-11e7-b03c-7e6885eea84b,0c4b6d38-8ba3-11e7-b03c-7e6885eea84b,changeServiceForRouter,allow
> Resource
>
> Admin,bdb82cbb-8b90-11e7-b03c-7e6885eea84b,0c32696d-8ba3-11e7-b03c-7e6885eea84b,changeServiceForRouter,allow
> Domain
>
> Admin,bdb84ac5-8b90-11e7-b03c-7e6885eea84b,0c4bb89f-8ba3-11e7-b03c-7e6885eea84b,configureVirtualRouterElement,allow
> Resource
>
> Admin,bdb82cbb-8b90-11e7-b03c-7e6885eea84b,0c32d222-8ba3-11e7-b03c-7e6885eea84b,configureVirtualRouterElement,allow
> Domain
>
> Admin,bdb84ac5-8b90-11e7-b03c-7e6885eea84b,0c4f4f0b-8ba3-11e7-b03c-7e6885eea84b,createVirtualRouterElement,allow
> Resource
>
> Admin,bdb82cbb-8b90-11e7-b03c-7e6885eea84b,0c36c75f-8ba3-11e7-b03c-7e6885eea84b,createVirtualRouterElement,allow
> Domain
>
> Admin,bdb84ac5-8b90-11e7-b03c-7e6885eea84b,0c537adc-8ba3-11e7-b03c-7e6885eea84b,destroyRouter,allow
> Resource
>
> Admin,bdb82cbb-8b90-11e7-b03c-7e6885eea84b,0c3b0202-8ba3-11e7-b03c-7e6885eea84b,destroyRouter,allow
> Domain
>
> Admin,bdb84ac5-8b90-11e7-b03c-7e6885eea84b,0c5a308f-8ba3-11e7-b03c-7e6885eea84b,listRouters,allow
> Resource
>
> Admin,bdb82cbb-8b90-11e7-b03c-7e6885eea84b,0c41f14c-8ba3-11e7-b03c-7e6885eea84b,listRouters,allow
> Domain
>
> Admin,bdb84ac5-8b90-11e7-b03c-7e6885eea84b,0c5b7a4a-8ba3-11e7-b03c-7e6885eea84b,listVirtualRouterElements,allow
> Resource
>
> Admin,bdb82cbb-8b90-11e7-b03c-7e6885eea84b,0c439b01-8ba3-11e7-b03c-7e6885eea84b,listVirtualRouterElements,allow
> Domain
>
> Admin,bdb84ac5-8b90-11e7-b03c-7e6885eea84b,0c5cca93-8ba3-11e7-b03c-7e6885eea84b,rebootRouter,allow
> Resource
>
> Admin,bdb82cbb-8b90-11e7-b03c-7e6885eea84b,0c44f5d3-8ba3-11e7-b03c-7e6885eea84b,rebootRouter,allow
> Domain
>
> Admin,bdb84ac5-8b90-11e7-b03c-7e6885eea84b,0c5e7590-8ba3-11e7-b03c-7e6885eea84b,startRouter,allow
> Domain
>
> Admin,bdb84ac5-8b90-11e7-b03c-7e6885eea84b,0c5e96a1-8ba3-11e7-b03c-7e6885eea84b,stopRouter,allow
> Resource
>
> Admin,bdb82cbb-8b90-11e7-b03c-7e6885eea84b,0c46c127-8ba3-11e7-b03c-7e6885eea84b,startRouter,allow
> Resource
>
> Admin,bdb82cbb-8b90-11e7-b03c-7e6885eea84b,0c46e5a0-8ba3-11e7-b03c-7e6885eea84b,stopRouter,allow
>
> Currently I'm usign cloudstack 4.9.3.1.
>
> It's possible to create this new role?
>
> Thanks in advance.
>
> --
> Fernando.
>


-- 
Daan

Re: Delete files with no reference in DB?

[Daan Hoogland]

H Fariborz,
If you checked all relevant tables, by all means. Think of volumes,
templates, snapshots, I don't thinks there is any others. Best is to do a
grep on a db dump for the basename of the file, if that doesn't give a hit,
you are free to go.

On Wed, Nov 13, 2019 at 3:45 PM Fariborz Navidan 
wrote:

> Hello
>
> Is it safe to delete volume files in primary or secondary storage without
> any reference in DB or those marked as removed?
> Is it safe to delete files with no reference in DB?
>


-- 
Daan

Re: Apache CloudStack Generic Key-Value and Communication Plug-in

[Daan Hoogland]

sounds nice Ivan, Do you have a whitepaper on it? I strugle to see a clear
usecase for this plugin. maybe you have a casus or two!?!

On Wed, Sep 19, 2018 at 9:02 AM Ivan Kudryavtsev 
wrote:

> Hello, community.
>
> We glad to announce a new Open Source plug-in for Apache CloudStack which
> helps to maintain generic key-value storages. There are three types are
> supported right now:
>
> - temporary KV with TTL (many per account);
> - persistent KV bound to VM (one per VM);
> - persistent KV bound to account (many per account).
>
> KV storages support a commit-log based approach where old values are not
> erased with new ones and it provides the access to the last key/values and
> to the history which helps to maintain things like quorums and other
> operations which require serialized access.
>
> The plugin uses Elasticsearch. I
>
> If you are interested to know more, contact our website for the full
> announcement and download details:
> https://bitworks.software/en/2018-09-19-acs-vm-kv-storage-plugin.html
>
> All questions, improvements and considerations are welcome!
>
> --
> With best regards, Ivan Kudryavtsev
> Bitworks LLC
> Cell: +7-923-414-1515
> WWW: http://bitworks.software/ 
>


-- 
Daan

Re: GPU/vGPU on VMware is Supported？

[Daan Hoogland]

just noticed it is not in yet, Zy.
https://github.com/apache/cloudstack/pull/2340 contains the changes
intended for it.

On Mon, Sep 10, 2018 at 8:55 AM Daan Hoogland 
wrote:

> not sure if that got merged, Zy. you'll have to check the code. If I
> encounter it I'll let you know.
>
> On Fri, Sep 7, 2018 at 3:30 AM zy.zhang...@neusoft.com <
> zy.zhang...@neusoft.com> wrote:
>
>> Hi，all：
>>
>> Is GPU/vGPU on VMware supported in CS？
>>
>> I noticed that there is a GPU/vGPU Support Design Documents.
>>
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681765
>>
>>
>>
>>
>>
>> ---
>> Confidentiality Notice: The information contained in this e-mail and any
>> accompanying attachment(s)
>> is intended only for the use of the intended recipient and may be
>> confidential and/or privileged of
>> Neusoft Corporation, its subsidiaries and/or its affiliates. If any
>> reader of this communication is
>> not the intended recipient, unauthorized use, forwarding, printing,
>> storing, disclosure or copying
>> is strictly prohibited, and may be unlawful.If you have received this
>> communication in error,please
>> immediately notify the sender by return e-mail, and delete the original
>> message and all copies from
>> your system. Thank you.
>>
>> ---
>>
>
>
> --
> Daan
>


-- 
Daan

Re: GPU/vGPU on VMware is Supported？

[Daan Hoogland]

not sure if that got merged, Zy. you'll have to check the code. If I
encounter it I'll let you know.

On Fri, Sep 7, 2018 at 3:30 AM zy.zhang...@neusoft.com <
zy.zhang...@neusoft.com> wrote:

> Hi，all：
>
> Is GPU/vGPU on VMware supported in CS？
>
> I noticed that there is a GPU/vGPU Support Design Documents.
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681765
>
>
>
>
>
> ---
> Confidentiality Notice: The information contained in this e-mail and any
> accompanying attachment(s)
> is intended only for the use of the intended recipient and may be
> confidential and/or privileged of
> Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader
> of this communication is
> not the intended recipient, unauthorized use, forwarding, printing,
> storing, disclosure or copying
> is strictly prohibited, and may be unlawful.If you have received this
> communication in error,please
> immediately notify the sender by return e-mail, and delete the original
> message and all copies from
> your system. Thank you.
>
> ---
>


-- 
Daan

[DISCUSS] Removing IAM services

[Daan Hoogland]

i'm +1 on this it has not been developed for the longest while. (changed
the title to indicate _all_ people are supposed to have an opinion.)

On Tue, Aug 21, 2018 at 4:32 PM, Khosrow Moossavi 
wrote:

> Hello Community
>
> Following up after PR#2613[1] to cleanup POMs across the whole repository,
> now in a new
> PR #2817 we are going to remove services/iam projects which seems to be
> disabled and
> not maintained since May 2014.
>
> Moving forward with the PR, corresponding tables will be deleted from
> database too.
>
> Please let us know if you have any questions, comments, concerns about this
> removal or if
> you are willing to revive the project in some shape or form.
>
> [1]: https://github.com/apache/cloudstack/pull/2613
> [2]: https://github.com/apache/cloudstack/pull/2817
>
> Khosrow Moossavi
>
> Cloud Infrastructure Developer
>
> 
>



-- 
Daan

Re: CloudStack DNS names to PowerDNS export

[Daan Hoogland]

hey Ivan, I don't have much experience with anything but bind, but this
looks nice!

On Tue, Aug 21, 2018 at 7:45 AM, Ivan Kudryavtsev 
wrote:

> Hello, users, devs.
>
> We developed a small service for the creation of DNS records (A, , PTR)
> in the PowerDNS and published it in the GitHub:
>
> https://github.com/bwsw/cs-powerdns-integration
>
> Licensed under Apache 2 License.
>
> *Rationale*
>
> CloudStack VR maintains DNS A records for VMs but since VR is an ephemeral
> entity which can be removed and recreated, which IP addresses can be
> changed, it's inconvenient to use it for zone delegation. Also, it's
> difficult to pair second DNS server with it as it requires VR hacking. So,
> to overcome those difficulties and provide external users with FQDN access
> to VMs we implemented the solution.
>
>
> --
> With best regards, Ivan Kudryavtsev
> Bitworks LLC
> Cell: +7-923-414-1515
> WWW: http://bitworks.software/ 
>



-- 
Daan

Re: LDAP in 4.11.1

[Daan Hoogland]

Marty, Ilya is right I worked on this a few months ago, so let me try and
help you.

It sounds like you are mixing two types of ldap integration, There are
three:
1: link individual account
2: link a domain for which auto import will be enabled, this one will auto
create an account for each user
3: link a domain and accounts within it to administer your users in ldap

Which of the three are you trying?
Where did you add the basedn, globally or on the domain?


On Thu, Aug 2, 2018 at 10:01 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> What is the content of your "ldap.basedn" parameter?
>
> On Thu, Aug 2, 2018 at 4:58 PM, ilya musayev  >
> wrote:
>
> > You are most likely getting incorrect query to ldap.
> >
> > If you can - use ldap connectivity without ssl and do tcpdump to see if
> you
> > can capture the ldapquery.
> >
> > You can then identify the issue. Alternately, you can look into enabling
> > trace logging for ldap module and perhaps it prints the query.
> >
> > Daan can shed more details on this issue as he was the one working on it.
> >
> > On Thu, Aug 2, 2018 at 12:55 PM  wrote:
> >
> > > Yes, full restart of management server to be safe. I have tried putting
> > in
> > > the LDAP name, the Pre-Windows name, etc..
> > >
> > > -Original Message-
> > > From: Rafael Weingärtner 
> > > Sent: Thursday, August 2, 2018 1:22 PM
> > > To: users 
> > > Subject: Re: LDAP in 4.11.1
> > >
> > > Did you restart ACS after configuring it?
> > >
> > > On Thu, Aug 2, 2018 at 2:03 PM,  wrote:
> > >
> > > > Hello guys,
> > > >
> > > >
> > > >
> > > > I am attempting to bind an ACS domain to an LDAP domain and I get the
> > > > error "can not link a domain unless a basedn is configured for it"
> but
> > > > this is set in the settings. Anyone seen this?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Rafael Weingärtner
> > >
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>



-- 
Daan

Re: 4.11.0 -> 4.11.1 problem: Guest VMs losing connection after few minutes

[Daan Hoogland]

jevgeni,
for sure this should have happened during the upgrade. If you still have
the logs from that day you might find the error there. a spelling error in
name or desription might have happened, for instance. anyway, congrats on
solving it.

On Fri, Jul 20, 2018 at 2:45 PM, Jevgeni Zolotarjov 
wrote:

> Yes,
>
> But isn't it what is written here
> http://docs.cloudstack.apache.org/projects/cloudstack-
> release-notes/en/4.11.1.0/upgrade/upgrade-4.11.html
> ?
>
> On Fri, Jul 20, 2018 at 3:29 PM Makrand  wrote:
>
> > I think you must have tried to register system VM template from template
> > menu from the left side manually. It will be registered as USER only in
> > that case.
> >
> > --
> > Makrand
> >
> >
> > On Fri, Jul 20, 2018 at 5:41 PM, Jevgeni Zolotarjov <
> > j.zolotar...@gmail.com>
> > wrote:
> >
> > > Eventually I fixed the problem, without clear understanding of the root
> > > cause.
> > >
> > > I destroyed routerVM, and cloudstack recreated it. But I discovered,
> that
> > > it is version 4.11.0. Not 4.11.1!
> > > I checked and systemVM template for 4.11.1 is registered in cloudstack
> -
> > > all OK.
> > > I noticed however, that its "Type" property is USER, not SYSTEM.
> > >
> > > Then I wanted to delete template for 4.11.0, but cloudstack does not
> > offer
> > > me this option. I can only add new ones.
> > >
> > > So, I ended with manipulations in the DB itself to make template for
> > 4.11.1
> > > the only one in the system and have Type = SYSTEM.
> > >
> > > After that I destroyed again routerVM. It was recreated and it is
> 4.11.1.
> > > And now everything works fine for over an hour already.
> > >
> > > I hope, thats it.
> > >
> > > On Fri, Jul 20, 2018 at 12:10 PM ilya musayev <
> > > ilya.mailing.li...@gmail.com>
> > > wrote:
> > >
> > > > Have you tried destroying router vm and let CloudStack create new
> one ?
> > > >
> > > > On Fri, Jul 20, 2018 at 1:33 AM Jevgeni Zolotarjov <
> > > j.zolotar...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > - an ip-address conflict.
> > > > >   JZ: unlikely, but not impossible. I tried to restart router VM in
> > > > > Network-Guest networks -> defaultGuestNetwork -> VirtualAppliances
> > > > > While rebooting ping to this router VM disappeared. Hence, no other
> > > > device
> > > > > is using the same IP.
> > > > > But!!! when this virtual router started, then network connection to
> > all
> > > > > guest VMs disappeared. So, it must be something with this virtual
> > > router.
> > > > >
> > > > > - flakey hardware being one of
> > > > > -+ if card in the host
> > > > > JZ: higly unlikely
> > > > >
> > > > > -+ a router with bad firmware
> > > > > JZ: also unlikely
> > > > >
> > > > > - of course a strange cofiguration of the software router in you
> host
> > > > might
> > > > > be the issue as well
> > > > > JZ: I didnt do any special configuration. Just used default.
> > > > >
> > > > > by all I know this happening after upgrade sounds like an unhappy
> > > > incident
> > > > > but can't be sure.
> > > > > The iptables restart, was this on the VirtualRouter or on the host,
> > or
> > > > > maybe on the guest? and the restart network?
> > > > >
> > > > > JZ: iptables restart on host machine. (or network restart on host)
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Jul 20, 2018 at 11:14 AM Daan Hoogland <
> > > daan.hoogl...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > that behaviour sound familiar from a couple of cases:
> > > > > > - an ip-address conflict.
> > > > > > - flakey hardware being one of
> > > > > > -+ if card in the host
> > > > > > -+ a router with bad firmware
> > > > > > - of course a strange cofiguration of the software router in you
> > host
> > > > > might
> > > > > > be the issue as well
> > > > > >
> > > > > > by all I know this happening 

Re: 4.11.0 -> 4.11.1 problem: Guest VMs losing connection after few minutes

[Daan Hoogland]

On Fri, Jul 20, 2018 at 9:09 AM, ilya musayev 
wrote:

> Have you tried destroying router vm and let CloudStack create new one ?
>
​yes, or restart network with cleanup

​


>
> On Fri, Jul 20, 2018 at 1:33 AM Jevgeni Zolotarjov  >
> wrote:
>
> > - an ip-address conflict.
> >   JZ: unlikely, but not impossible. I tried to restart router VM in
> > Network-Guest networks -> defaultGuestNetwork -> VirtualAppliances
> > While rebooting ping to this router VM disappeared. Hence, no other
> device
> > is using the same IP.
> > But!!! when this virtual router started, then network connection to all
> > guest VMs disappeared. So, it must be something with this virtual router.
> >
> > - flakey hardware being one of
> > -+ if card in the host
> > JZ: higly unlikely
> >
> > -+ a router with bad firmware
> > JZ: also unlikely
> >
> > - of course a strange cofiguration of the software router in you host
> might
> > be the issue as well
> > JZ: I didnt do any special configuration. Just used default.
> >
> > by all I know this happening after upgrade sounds like an unhappy
> incident
> > but can't be sure.
> > The iptables restart, was this on the VirtualRouter or on the host, or
> > maybe on the guest? and the restart network?
> >
> > JZ: iptables restart on host machine. (or network restart on host)
> >
> >
> >
> > On Fri, Jul 20, 2018 at 11:14 AM Daan Hoogland 
> > wrote:
> >
> > > that behaviour sound familiar from a couple of cases:
> > > - an ip-address conflict.
> > > - flakey hardware being one of
> > > -+ if card in the host
> > > -+ a router with bad firmware
> > > - of course a strange cofiguration of the software router in you host
> > might
> > > be the issue as well
> > >
> > > by all I know this happening after upgrade sounds like an unhappy
> > incident
> > > but can't be sure.
> > > The iptables restart, was this on the VirtualRouter or on the host, or
> > > maybe on the guest? and the restart network?
> > >
> > >
> > > On Fri, Jul 20, 2018 at 7:43 AM, Jevgeni Zolotarjov <
> > > j.zolotar...@gmail.com>
> > > wrote:
> > >
> > > > I updated cloudstack 4.11.0 -> 4.11.1
> > > >
> > > > Everything went OK during update, but after host reboot guest VMs
> lost
> > > > connection after few minutes of normal work.
> > > > I tried restarting network - systemctl restart network.service
> > > > then connection was restored again for few minutes
> > > >
> > > > Finally I could restore connection by restarting iptables - systemctl
> > > > restart iptables.service
> > > >
> > > > But then again guest VMs lost connection after few minutes of normal
> > > > operation.
> > > > The time of normal operation can be 5 minutes, but sometimes up to 40
> > > > minutes.
> > > >
> > > > Please help me to track the root cause and fix it
> > > >
> > > > Host OS - Centos 7.5
> > > > virtualisation - KVM
> > > >
> > >
> > >
> > >
> > > --
> > > Daan
> > >
> >
>



-- 
Daan

Re: 4.11.0 -> 4.11.1 problem: Guest VMs losing connection after few minutes

[Daan Hoogland]

that behaviour sound familiar from a couple of cases:
- an ip-address conflict.
- flakey hardware being one of
-+ if card in the host
-+ a router with bad firmware
- of course a strange cofiguration of the software router in you host might
be the issue as well

by all I know this happening after upgrade sounds like an unhappy incident
but can't be sure.
The iptables restart, was this on the VirtualRouter or on the host, or
maybe on the guest? and the restart network?


On Fri, Jul 20, 2018 at 7:43 AM, Jevgeni Zolotarjov 
wrote:

> I updated cloudstack 4.11.0 -> 4.11.1
>
> Everything went OK during update, but after host reboot guest VMs lost
> connection after few minutes of normal work.
> I tried restarting network - systemctl restart network.service
> then connection was restored again for few minutes
>
> Finally I could restore connection by restarting iptables - systemctl
> restart iptables.service
>
> But then again guest VMs lost connection after few minutes of normal
> operation.
> The time of normal operation can be 5 minutes, but sometimes up to 40
> minutes.
>
> Please help me to track the root cause and fix it
>
> Host OS - Centos 7.5
> virtualisation - KVM
>



-- 
Daan

Re: [RESULT][VOTE] Apache CloudStack 4.11.1.0

[Daan Hoogland]

nice,

On Wed, Jun 27, 2018 at 3:11 PM, Giles Sirett 
wrote:

> Great news
> Well done to all of those involved
>
> Kind regards
> Giles
>
> giles.sir...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Paul Angus 
> Sent: 26 June 2018 17:10
> To: d...@cloudstack.apache.org; users@cloudstack.apache.org
> Subject: [RESULT][VOTE] Apache CloudStack 4.11.1.0
>
> Hi All,
>
> After 72 hours, the vote for CloudStack 4.11.1.0 *passes* with
> 3 PMC + 2 non-PMC votes.
>
> +1 (PMC / binding)
>
> Rohit Yadav
>
> Paul Angus
>
> Mike Tutkowski
>
> +1 (non binding)
>
> Nicolas Vazquez
>
> Boris Stoyanov
>
> 0
> Rene Moser
>
> -1
> none
>
> Thanks to everyone participating.
>
> I will now prepare the release announcement to go out after 24 hours to
> give the mirrors time to catch up.
>
>
> Kind regards,
>
> Paul Angus
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>
>
>
>


-- 
Daan

Re: Current cloudstack prebuilt images wrong VR address

[Daan Hoogland]

ah, you are right sorry nux

On Mon, Jun 25, 2018 at 3:08 PM, Andrija Panic 
wrote:

> Well, thank you Daan for these great credits, but it's actually Nux who
> owns this templates afaik. :)
>
> Cheers,
> Andrija
>
> On Mon, Jun 25, 2018, 15:34 Ivan Kudryavtsev 
> wrote:
>
> > Yes, Daan.
> >
> > The problem is with template, not with ACS. My English is so-so, but I
> > meant that)
> >
> > And I use a Basic zone, no isolation, etc.
> >
> > пн, 25 июн. 2018 г., 19:29 Daan Hoogland :
> >
> >> Stephan, Ivan,
> >> As I read it, it is not a cloudstack problem but a problem with the
> >> template used. Andrija may know??
> >>
> >> On Mon, Jun 25, 2018 at 2:24 PM, Stephan Seitz <
> >> s.se...@heinlein-support.de>
> >> wrote:
> >>
> >> > Hi!
> >> >
> >> > AFAIK, the password reset script always tries to connect to TCP/8080
> on
> >> the
> >> > server that offered the dhcp lease. Which usually is the default
> >> gateway.
> >> > If you're running an isolated network with redundant VR, there was an
> >> > iptables
> >> > rule on the VR blocking the host-IP, so that the request couldn't
> >> succeed.
> >> >
> >> > That issue [1] has recently been fixed for 4.11.1.0.
> >> >
> >> >
> >> > [1] https://github.com/apache/cloudstack/issues/2544
> >> >
> >> >
> >> > cheers,
> >> >
> >> > - Stephan
> >> >
> >> >
> >> >
> >> > Am Montag, den 25.06.2018, 19:08 +0700 schrieb Ivan Kudryavtsev:
> >> > > Hello, Devs, Users.
> >> > >
> >> > > Today I tried to deploy prebuilt centos image from
> >> > >
> >> > > http://dl.openvm.eu/cloudstack/centos/
> >> > >
> >> > > Previously I already used that images, so I just registered it and
> >> > created
> >> > > VM. Unfortunately, I found that cloud-init tries network GW as a
> >> source
> >> > for
> >> > > metadata when VM starts (to get the password, etc.). So, It doesn't
> >> use
> >> > VR
> >> > > to get information but attempts to fetch it from the network default
> >> GW.
> >> > > So, It fails.
> >> > >
> >> > > Next, I downloaded CentOS template which I have used for a year
> (also
> >> > from
> >> > > http://dl.openvm.eu/cloudstack/centos/), created VM and it works
> >> nice.
> >> > It
> >> > > fetches password and other information from correct VR endpoint.
> >> > >
> >> > > I suppose there is the error in the current CentOS template. Maybe,
> >> > someone
> >> > > who has built them assumes that default GW is always VR which it may
> >> be
> >> > > true sometimes (advanced zones, I suppose), but not in general (I
> use
> >> > Basic
> >> > > Zone).
> >> > >
> >> > > Have a good day.
> >> > >
> >> > >
> >> > >
> >> > Mit freundlichen Grüßen,
> >> >
> >> > Stephan Seitz
> >> >
> >> > --
> >> >
> >> > Heinlein Support GmbH
> >> > Schwedter Str. 8/9b, 10119 Berlin
> >> >
> >> > http://www.heinlein-support.de
> >> >
> >> > Tel: 030 / 405051-44
> >> > Fax: 030 / 405051-19
> >> >
> >> > Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht
> >> > Berlin-Charlottenburg,
> >> > Geschäftsführer: Peer Heinlein -- Sitz: Berlin
> >> >
> >> >
> >> >
> >>
> >>
> >> --
> >> Daan
> >>
> >
>



-- 
Daan

Re: Current cloudstack prebuilt images wrong VR address

[Daan Hoogland]

Stephan, Ivan,
As I read it, it is not a cloudstack problem but a problem with the
template used. Andrija may know??

On Mon, Jun 25, 2018 at 2:24 PM, Stephan Seitz 
wrote:

> Hi!
>
> AFAIK, the password reset script always tries to connect to TCP/8080 on the
> server that offered the dhcp lease. Which usually is the default gateway.
> If you're running an isolated network with redundant VR, there was an
> iptables
> rule on the VR blocking the host-IP, so that the request couldn't succeed.
>
> That issue [1] has recently been fixed for 4.11.1.0.
>
>
> [1] https://github.com/apache/cloudstack/issues/2544
>
>
> cheers,
>
> - Stephan
>
>
>
> Am Montag, den 25.06.2018, 19:08 +0700 schrieb Ivan Kudryavtsev:
> > Hello, Devs, Users.
> >
> > Today I tried to deploy prebuilt centos image from
> >
> > http://dl.openvm.eu/cloudstack/centos/
> >
> > Previously I already used that images, so I just registered it and
> created
> > VM. Unfortunately, I found that cloud-init tries network GW as a source
> for
> > metadata when VM starts (to get the password, etc.). So, It doesn't use
> VR
> > to get information but attempts to fetch it from the network default GW.
> > So, It fails.
> >
> > Next, I downloaded CentOS template which I have used for a year (also
> from
> > http://dl.openvm.eu/cloudstack/centos/), created VM and it works nice.
> It
> > fetches password and other information from correct VR endpoint.
> >
> > I suppose there is the error in the current CentOS template. Maybe,
> someone
> > who has built them assumes that default GW is always VR which it may be
> > true sometimes (advanced zones, I suppose), but not in general (I use
> Basic
> > Zone).
> >
> > Have a good day.
> >
> >
> >
> Mit freundlichen Grüßen,
>
> Stephan Seitz
>
> --
>
> Heinlein Support GmbH
> Schwedter Str. 8/9b, 10119 Berlin
>
> http://www.heinlein-support.de
>
> Tel: 030 / 405051-44
> Fax: 030 / 405051-19
>
> Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht
> Berlin-Charlottenburg,
> Geschäftsführer: Peer Heinlein -- Sitz: Berlin
>
>
>


-- 
Daan

Re: [VOTE] Apache CloudStack 4.11.1.0 LTS [RC3]

[Daan Hoogland]

Sean,
I've been busy with that scenario for a while and it is not a consistent
error. I have the feeling that it happens more4 lately but just yesterday I
manually testit several times 2 VPC with connected private gw and static
routes to each other. I could restart with no problem.

On Fri, Jun 22, 2018 at 5:46 PM, Sean Lair  wrote:

> Would someone mind testing testing a Restart VPC w/ Cleanup on a VPC that
> has a private gateway configured?  The test 
> "test_03_vpc_privategw_restart_vpc_cleanup"
> is failing due to the following (according to logs).  My test environment
> is not available right now so I can't check myself.  I don't have this
> problem in my 4.9.3 prod environment.
>
> 
> Java.lang.NullPointerException
> at com.cloud.network.router.NicProfileHelperImpl.
> createPrivateNicProfileForGateway(NicProfileHelperImpl.java:95)
> 
>
> 
> NicProfileHelperImpl.java (Lines 93 - 95)
> 
> final PrivateIpAddress ip =
> new PrivateIpAddress(ipVO, 
> privateNetwork.getBroadcastUri().toString(),
> privateNetwork.getGateway(), netmask,
> NetUtils.long2Mac(NetUtils.
> createSequenceBasedMacAddress(ipVO.getMacAddress(),
> NetworkModel.MACIdentifier.value(;
>
>
> Thanks
> Sean
>
> -Original Message-
> From: Paul Angus [mailto:paul.an...@shapeblue.com]
> Sent: Thursday, June 21, 2018 11:00 AM
> To: d...@cloudstack.apache.org; users@cloudstack.apache.org
> Subject: [VOTE] Apache CloudStack 4.11.1.0 LTS [RC3]
>
> Hi All,
>
>
>
> I've created a 4.11.1.0 release (RC3), with the following artefacts up for
> testing and a vote:
> The changes since RC2 are listed at the end of this email.
>
>
>
> Git Branch and Commit SH:
>
> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=
> shortlog;h=refs/heads/4.11.1.0-RC20180621T1552
>
> Commit: 2cb2dacbe75a23f5068b80f6ea45031c29052c31
>
>
>
> Source release (checksums and signatures are available at the same
>
> location):
>
> https://dist.apache.org/repos/dist/dev/cloudstack/4.11.1.0/
>
>
>
> PGP release keys (signed using 8B309F7251EE0BC8):
>
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
>
>
> The vote will be open for at least 72hrs.
>
>
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
>
>
> [ ] +1  approve
>
> [ ] +0  no opinion
>
> [ ] -1  disapprove (and reason why)
>
>
>
>
>
> Additional information:
>
>
>
> For users' convenience, I've built packages from
> 5f48487dc62fd1decaabc4ab2a10f549d6c82400 and published RC1 repository
> here:
>
> http://packages.shapeblue.com/testing/4111rc3/
>
>
>
> The release notes are still work-in-progress, but the systemvm template
> upgrade section has been updated. You may refer the following for systemvm
> template upgrade testing:
>
> http://docs.cloudstack.apache.org/projects/cloudstack-
> release-notes/en/latest/index.html
>
>
>
> 4.11.1 systemvm templates are available from here:
>
> http://packages.shapeblue.com/systemvmtemplate/4.11.1-rc1/
>
>
>
>
> Changes Since RC2:
>
> Merged #2712 reuse ip for non redundant VPC 6 hours ago Merged #2714 send
> unsupported answer only when applicable 10 hours ago Merged #2715
> smoketest: Fix test_vm_life_cycle secure migration tests a day ago Merged
> #2493 CLOUDSTACK-10326: Prevent hosts fall into Maintenance when there are
> running VMs on it a day ago Merged #2716 configdrive: make fewer
> mountpoints on hosts a day ago Merged #2681 Source NAT option on Private
> Gateway 2 days ago Merged #2710 comply with api key constraint 2 days ago
> Merged #2706 packaging: use libuuid x86_64 package for cloudstack-common 2
> days ago
>
> Kind regards,
>
> Paul Angus
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>
>
>
>


-- 
Daan

Re: Migrating workloads into CloudStack

[Daan Hoogland]

Mark I do not feel qualified to answer but nobody else does, so ... I don't
know these tools. Can your send a pointert to the one you wish to use? I
would expect the root admin priovilidges are required as you would have to
create the proper offerings and networks for the VMs to be migated too.
That might be overdone if you have all in place and only need to
deployVm()s.

On Thu, Jun 21, 2018 at 10:11 AM, Werner, Mark 
wrote:

> Hi,
>
>
>
> If  using one of the several popular migration/replication software tools
> available to migrate workloads into a CloudStack managed cloud
> infrastructure what CloudStack API commands does the migration/replication
> software tool require access to?
>
>
>
> For example, if using a migration/replication software tool to migrate a
> VMware vCenter managed VM running on an ESXi hypervisor into a CloudStack
> managed cloud infrastructure, what CloudStack API commands would you (or
> the migration/replication software tool) require access to and what type or
> role, or what level of access, would you need?
>
>
>
> Thank you,
>
>
>
> *Mark Werner* | Senior Systems Engineer | Cloud & Infrastructure Services
>
> Unisys | Mobile Phone 586.214.9017 | mark.wer...@unisys.com
>
> 11720 Plaza America Drive, Reston, VA 20190
> 
>
>
>
> [image: unisys_logo] 
>
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all devices.
>
> [image: Grey_LI]   [image:
> Grey_TW]  [image: Grey_GP]
> [image: Grey_YT]
> [image: Grey_FB]
> [image: Grey_Vimeo]
> [image: Grey_UB] 
>
>
>



-- 
Daan

Re: com.cloud.agent.api.CheckRouterCommand timeout

[Daan Hoogland]

makes sense, well let's hope all breaks soon ;)

On Thu, Jun 21, 2018 at 2:15 PM, Melanie Desaive <
m.desa...@heinlein-support.de> wrote:

> Hi Daan,
>
> Am 21.06.2018 um 15:29 schrieb Daan Hoogland:
> > Melanie, attachments get deleted for this list. Your assumption for the
> > comm path is right for xen. Did you try and execute the script as it is
> > called by the proxy script from the host? and capture the return? We had
> a
> > bad problem with getting the template version in the past on xen, this
> > might be similar. That was due to processing of the returned string in
> the
> > script.
>
> I called both stages of the script manually but at at time, when all was
> working as expected and the routers where back to MASTER and BACKUP.
>
> Looked like:
>
> [root@acs-compute-5 ~]# /opt/cloud/bin/router_proxy.sh checkrouter.sh
> 169.254.1.178
> Status: BACKUP
>
> root@r-2595-VM:~# /opt/cloud/bin/checkrouter.sh
> Status: BACKUP
>
>
> >
> > On Thu, Jun 21, 2018 at 1:16 PM, Melanie Desaive <
> > m.desa...@heinlein-support.de> wrote:
> >
> >> Hi Daan,
> >>
> >> thanks for your reply.
> >>
> >> The latest occurance of our VRs going to UNKNOWN did resolve 24 hours
> >> after it had occured. Nevertheless I would appreciate some insight into
> >> how the checkRouter command is handled, as I expect the problem to come
> >> back again.
> >> Am 21.06.2018 um 10:39 schrieb Daan Hoogland:
> >>> Melanie, this depends a bit on the type of hypervisor. The command
> >> executes
> >>> the checkrouter.sh script on the virtual router if it reaches it, but
> it
> >>> seems your problem is before that. I would look at the network first
> and
> >>> follow the path that the execution takes for your hypervisortype.
> >>
> >> With Stephans help I figured out the following guess for the path of
> >> connections for the checkrouter command. Could someone please correct
> >> me, if my guess is not correct. ;)
> >>
> >>  x Management Nodes connects to XenServer hypervisor host via management
> >> network on port 22 by SSH
> >>  x On hypervisor host the wrapper script
> >> "/opt/cloud/bin/router_proxy.sh" is used to call scripts on system VMs
> >> via link-local IP and port 3922
> >>  x On the VR the script "/opt/cloud/bin/checkrouter.sh" does the actual
> >> check.
> >>
> >> In our case the API call times out with log messages
> >>  x Operation timed out: Commands 1063975411966525473 to Host 29 timed
> >> out after 60
> >>  x Unable to update router r-2595-VM's status
> >>  x Redundant virtual router (name: r-2595-VM, id: 2595)  just switch
> >> from BACKUP to UNKNOWN
> >>
> >> To me it seems that this is a timeout that occurs when ACS management is
> >> waitig for the API call to return. At what stage (management host <->
> >> virtualization host) or (virutalization host <-> VR> the answer is
> >> delayed is unclear to me. (SSH Login from virtualization host to VR via
> >> link-local is working all the time)
> >>
> >> And it is unclear to me, why both VRs of the respective network stay in
> >> UNKNOWN for 24 hours, are accessible via link-local but come back
> >> immedately after a reboot.
> >>
> >> I am happy for any suggestions or explanations in this topic and will
> >> investigate further as soon, as the problem comes back again.
> >>
> >> A portion of our management log for the latest occurance of the problem
> >> is attached to this email.
> >>
> >> Greetings,
> >>
> >> Melanie
> >>
> >>>
> >>> On Wed, Jun 20, 2018 at 1:53 PM, Melanie Desaive <
> >>> m.desa...@heinlein-support.de> wrote:
> >>>
> >>>> Hi all,
> >>>>
> >>>> we have a recurring problem with our virtual routers. By the log
> >>>> messages it seems that com.cloud.agent.api.CheckRouterCommand runs
> into
> >>>> a timeout and therefore switches to UNKNOWN.
> >>>>
> >>>> All network traffic through the routers is still working. They can be
> >>>> accessed by their link-local IP adresses, and configuration looks good
> >>>> at a first sight. But configuration changes through the CloudStack API
> >>>> do no longer reach the routers. A reboot fixes the problem.

Re: com.cloud.agent.api.CheckRouterCommand timeout

[Daan Hoogland]

Melanie, attachments get deleted for this list. Your assumption for the
comm path is right for xen. Did you try and execute the script as it is
called by the proxy script from the host? and capture the return? We had a
bad problem with getting the template version in the past on xen, this
might be similar. That was due to processing of the returned string in the
script.

On Thu, Jun 21, 2018 at 1:16 PM, Melanie Desaive <
m.desa...@heinlein-support.de> wrote:

> Hi Daan,
>
> thanks for your reply.
>
> The latest occurance of our VRs going to UNKNOWN did resolve 24 hours
> after it had occured. Nevertheless I would appreciate some insight into
> how the checkRouter command is handled, as I expect the problem to come
> back again.
> Am 21.06.2018 um 10:39 schrieb Daan Hoogland:
> > Melanie, this depends a bit on the type of hypervisor. The command
> executes
> > the checkrouter.sh script on the virtual router if it reaches it, but it
> > seems your problem is before that. I would look at the network first and
> > follow the path that the execution takes for your hypervisortype.
>
> With Stephans help I figured out the following guess for the path of
> connections for the checkrouter command. Could someone please correct
> me, if my guess is not correct. ;)
>
>  x Management Nodes connects to XenServer hypervisor host via management
> network on port 22 by SSH
>  x On hypervisor host the wrapper script
> "/opt/cloud/bin/router_proxy.sh" is used to call scripts on system VMs
> via link-local IP and port 3922
>  x On the VR the script "/opt/cloud/bin/checkrouter.sh" does the actual
> check.
>
> In our case the API call times out with log messages
>  x Operation timed out: Commands 1063975411966525473 to Host 29 timed
> out after 60
>  x Unable to update router r-2595-VM's status
>  x Redundant virtual router (name: r-2595-VM, id: 2595)  just switch
> from BACKUP to UNKNOWN
>
> To me it seems that this is a timeout that occurs when ACS management is
> waitig for the API call to return. At what stage (management host <->
> virtualization host) or (virutalization host <-> VR> the answer is
> delayed is unclear to me. (SSH Login from virtualization host to VR via
> link-local is working all the time)
>
> And it is unclear to me, why both VRs of the respective network stay in
> UNKNOWN for 24 hours, are accessible via link-local but come back
> immedately after a reboot.
>
> I am happy for any suggestions or explanations in this topic and will
> investigate further as soon, as the problem comes back again.
>
> A portion of our management log for the latest occurance of the problem
> is attached to this email.
>
> Greetings,
>
> Melanie
>
> >
> > On Wed, Jun 20, 2018 at 1:53 PM, Melanie Desaive <
> > m.desa...@heinlein-support.de> wrote:
> >
> >> Hi all,
> >>
> >> we have a recurring problem with our virtual routers. By the log
> >> messages it seems that com.cloud.agent.api.CheckRouterCommand runs into
> >> a timeout and therefore switches to UNKNOWN.
> >>
> >> All network traffic through the routers is still working. They can be
> >> accessed by their link-local IP adresses, and configuration looks good
> >> at a first sight. But configuration changes through the CloudStack API
> >> do no longer reach the routers. A reboot fixes the problem.
> >>
> >> I would like to investigate a little further but lack understanding
> >> about how the checkRouter command is trying to access the virtual
> router.
> >>
> >> Could someone point me to some relevant documentation or give a short
> >> overview how the connection from CS-Management is done and where such an
> >> timeout could occur?
> >>
> >> As background information - the sequence from the management log looks
> >> kind of this:
> >>
> >> ---
> >>
> >>  x Every few seconds the com.cloud.agent.api.CheckRouterCommand returns
> >> a state BACKUP or MASTER correctly
> >>  x When the problem occurs the log messages change. Some snippets below
> >>
> >>  x ... Waiting some more time because this is the current command
> >>  x ... Waiting some more time because this is the current command
> >>  x Could not find exception:
> >> com.cloud.exception.OperationTimedoutException in error code list for
> >> exceptions
> >>  x Timed out on Seq 28-2352567855348137104
> >>  x Seq 28-2352567855348137104: Cancelling.
> >>  x Operation timed out: Commands 2352567855348137104 to Host 28 timed
> >> out after 60
&

Re: com.cloud.agent.api.CheckRouterCommand timeout

[Daan Hoogland]

Melanie, this depends a bit on the type of hypervisor. The command executes
the checkrouter.sh script on the virtual router if it reaches it, but it
seems your problem is before that. I would look at the network first and
follow the path that the execution takes for your hypervisortype.

On Wed, Jun 20, 2018 at 1:53 PM, Melanie Desaive <
m.desa...@heinlein-support.de> wrote:

> Hi all,
>
> we have a recurring problem with our virtual routers. By the log
> messages it seems that com.cloud.agent.api.CheckRouterCommand runs into
> a timeout and therefore switches to UNKNOWN.
>
> All network traffic through the routers is still working. They can be
> accessed by their link-local IP adresses, and configuration looks good
> at a first sight. But configuration changes through the CloudStack API
> do no longer reach the routers. A reboot fixes the problem.
>
> I would like to investigate a little further but lack understanding
> about how the checkRouter command is trying to access the virtual router.
>
> Could someone point me to some relevant documentation or give a short
> overview how the connection from CS-Management is done and where such an
> timeout could occur?
>
> As background information - the sequence from the management log looks
> kind of this:
>
> ---
>
>  x Every few seconds the com.cloud.agent.api.CheckRouterCommand returns
> a state BACKUP or MASTER correctly
>  x When the problem occurs the log messages change. Some snippets below
>
>  x ... Waiting some more time because this is the current command
>  x ... Waiting some more time because this is the current command
>  x Could not find exception:
> com.cloud.exception.OperationTimedoutException in error code list for
> exceptions
>  x Timed out on Seq 28-2352567855348137104
>  x Seq 28-2352567855348137104: Cancelling.
>  x Operation timed out: Commands 2352567855348137104 to Host 28 timed
> out after 60
>  x Unable to update router r-2594-VM's status
>  x Redundant virtual router (name: r-2594-VM, id: 2594)  just switch
> from MASTER to UNKNOWN
>
>  x Those error messages are now repeated for each following
> CheckRouterCommand until the virtual router is rebootet
>
>
> Greetings,
>
> Melanie
>
> --
> --
>
> Heinlein Support GmbH
> Linux: Akademie - Support - Hosting
>
> http://www.heinlein-support.de
> Tel: 030 / 40 50 51 - 0
> Fax: 030 / 40 50 51 - 19
>
> Zwangsangaben lt. §35a GmbHG:
> HRB 93818 B / Amtsgericht Berlin-Charlottenburg,
> Geschäftsführer: Peer Heinlein  -- Sitz: Berlin
>



-- 
Daan

Re: [VOTE] Apache CloudStack 4.11.1.0 LTS [RC2]

[Daan Hoogland]

- release checksums all check out.
- I installed an all-KVM 4.9.3.1 with a redundant VPC and two nets with
VMs. I upgraded to 4.11.1. The only glitch was that the documentation says
to register new system VMs as 'systemvm-kvm-4.11'. This should be
'systemvm-kvm-4.11.1'. The nets kept running and upgrading the vpc worked
without problem or noticable network glitch.

knowing that you will all test intensively as well ;) (as will I still...)

+1 (binding)


On Mon, Jun 11, 2018 at 5:49 PM, Paul Angus 
wrote:

> Hi All,
>
>
>
> I've created a 4.11.1.0 release (RC2), with the following artefacts up for
> testing and a vote:
>
>
>
> Git Branch and Commit SH:
>
> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=short
> log;h=refs/heads/4.11.1.0-RC20180611T1504
>
> Commit: bcf602c7cd4ab662a7c4f208dee32fb8513e26c8
>
>
>
> Source release (checksums and signatures are available at the same
>
> location):
>
> https://dist.apache.org/repos/dist/dev/cloudstack/4.11.1.0/
>
>
>
> PGP release keys (signed using 8B309F7251EE0BC8):
>
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
>
>
> The vote will be open until the end of the week, 15nd June 2018.
>
>
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
>
>
> [ ] +1  approve
>
> [ ] +0  no opinion
>
> [ ] -1  disapprove (and reason why)
>
>
>
> Additional information:
>
>
>
> For users' convenience, I've built packages from
> bcf602c7cd4ab662a7c4f208dee32fb8513e26c8 and published RC2 repository
> here:
>
> http://packages.shapeblue.com/testing/4111rc2/
>
>
>
> The release notes are still work-in-progress, but the systemvm template
> upgrade section has been updated. You may refer the following for systemvm
> template upgrade testing:
>
> http://docs.cloudstack.apache.org/projects/cloudstack-releas
> e-notes/en/latest/index.html
>
>
>
> 4.11.1 systemvm templates are available from here:
> http://packages.shapeblue.com/systemvmtemplate/4.11.1-rc1/
>
>
>
>
> Kind regards,
>
> Paul Angus
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>


-- 
Daan

Re: Autoscale without Netscaler

[Daan Hoogland]

Matheus,
As you are now at 4.11 so that statement would mean it is in. I don't know
it, but there is a whole class of API calls concerning  autoscaling, did
you try those?
regards,

On Tue, Jun 5, 2018 at 4:28 AM, Matheus Fontes  wrote:

> Does it work?
> http://docs.cloudstack.apache.org/en/latest/networking/
> autoscale_without_netscaler.html
>
> It says:
> Warning
> This feature is currently only available on the master branch and will be
> released in the 4.4 release.
>
> We are using 4.11 but the autoscale option in loadbalance does not show.
>
> thanks
> Matheus Fontes




-- 
Daan

Re: [VOTE] Apache CloudStack 4.11.1.0 LTS [RC1]

[Daan Hoogland]

I checked three verification files, unpacked and build the code, and am
trusting the process otherwise:
0 (binding)
The reason I am not giving a +1 is because the code presently does not
build on anything but linux, due to the configdrive test not building on
macosx (and I presume windows) If we add that to release notes I am fine
with it.

On Sat, May 26, 2018 at 5:27 AM, Tutkowski, Mike 
wrote:

> +1 (binding)
>
> I created a new cloud using commit 5f48487dc62fd1decaabc4ab2a10f549d6c82400
> (RC1). I ran the automated regression tests for managed storage. All tests
> passed.
>
> On 5/24/18, 9:56 AM, "Paul Angus"  wrote:
>
> Hi All,
>
>
>
> I've created a 4.11.1.0 release (RC1), with the following artefacts up
> for testing and a vote:
>
> [NB we know there are issues for Nuage to sort in this RC, but they
> will be well contained, so let’s test everything else 😊 ]
>
>
>
> Git Branch and Commit SH:
>
> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=
> shortlog;h=refs/heads/4.11.1.0-RC20180524T1000
>
> Commit: 5f48487dc62fd1decaabc4ab2a10f549d6c82400
>
>
>
> Source release (checksums and signatures are available at the same
>
> location):
>
> https://dist.apache.org/repos/dist/dev/cloudstack/4.11.1.0/
>
>
>
> PGP release keys (signed using 8B309F7251EE0BC8):
>
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
>
>
> The vote will be open till end of next week, 1st June 2018.
>
>
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
>
>
> [ ] +1  approve
>
> [ ] +0  no opinion
>
> [ ] -1  disapprove (and reason why)
>
>
>
> Additional information:
>
>
>
> For users' convenience, I've built packages from
> 5f48487dc62fd1decaabc4ab2a10f549d6c82400 and published RC1 repository
> here:
>
> http://packages.shapeblue.com/testing/4111rc1/
>
>
>
> The release notes are still work-in-progress, but the systemvm
> template upgrade section has been updated. You may refer the following for
> systemvm template upgrade testing:
>
> http://docs.cloudstack.apache.org/projects/cloudstack-
> release-notes/en/latest/index.html
>
>
>
> 4.11.1 systemvm templates are available from here:
> http://packages.shapeblue.com/systemvmtemplate/4.11.1-rc1/
>
>
> Kind regards,
>
> Paul Angus
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
>
>


-- 
Daan

Re: CloudStack Uasge lists expunged Volumes. Is that correct?

[Daan Hoogland]

the resource IDs would not necessarily be in the description of the event.
so can you select from event where type like 'VOLUME.*' and see if anything
is out there? "VOLUME.CREATE" is expected to be matched by "VOLUME.DELETE",
"VOLUME.ATTACH" by "VOLUME.DETACH", etc.

On Fri, May 18, 2018 at 1:03 PM, Melanie Desaive <
m.desa...@heinlein-support.de> wrote:

> Hi Daan,
>
> Am 18.05.2018 um 10:28 schrieb Daan Hoogland:
>
> > It seems that only 5 of those volumes should have been
> > reported between the 16th and the 16th, correct? Can you query for events
> > for those volumes in the event table? By the order of events we might be
> > able to draw some conclusions.
>
> You asked for a query like the following?
>
> mysql> select description from event where description like '%%' or
> description like '%2420%' or description like '%2567%' or description
> like '%2719%' or description like '%2920%' or description like '%2528%'
> or description like '%2809%' or description like '%2243%' or description
> like '%2505%' or description like '%2396%' or description like '%3696%'
> or description like '%2239%' or description like '%3174%' or description
> like '%3675%' or description like '%2172%' or description like '%2225%'
> or description like '%2223%' or description like '%3255%';
> Empty set (0.10 sec)
>
> This did not return any records. :(
>
> Or do you ask for a different kind of information?
>
> Greetings,
>
> Melanie
> --
> --
>
> Heinlein Support GmbH
> Linux: Akademie - Support - Hosting
>
> http://www.heinlein-support.de
> Tel: 030 / 40 50 51 - 0
> Fax: 030 / 40 50 51 - 19
>
> Zwangsangaben lt. §35a GmbHG:
> HRB 93818 B / Amtsgericht Berlin-Charlottenburg,
> Geschäftsführer: Peer Heinlein  -- Sitz: Berlin
>
>


-- 
Daan

Re: Dynamic roles question

[Daan Hoogland]

depends on the use case, for changing departments the move user is right,
for upgrading rights within a department probably not.

On Fri, May 18, 2018 at 8:59 AM, Ivan Kudryavtsev 
wrote:

> Hello, Daan, thank you for the clarification. It doesn't seems like the
> thing I'm talking about and actually, I don't think the approach enables
> the solving of the problem because VMs are owned by the account, and other
> related information like billing is connected with the account and, thus,
> changing the account is not the best way to fix the issue with changing the
> role. Don't think it's good for business cases.
>
> 2018-05-18 15:41 GMT+07:00 Daan Hoogland :
>
> > actually whet is in place is moving users between accounts, and thus
> > allowing for their role to change. The accounts would stay the same, but
> > the effective role of the users changes with it's account. MoverUserCmd
> is
> > the API.
> >
> > On Fri, May 18, 2018 at 7:44 AM, Ivan Kudryavtsev <
> > kudryavtsev...@bw-sw.com>
> > wrote:
> >
> > > Hello, Ilya.
> > > If it is already in place, then it's awesome. Thank you very much for
> > > assistance. I'll check it soon.
> > >
> > > 2018-05-18 14:37 GMT+07:00 ilya musayev 
> :
> > >
> > > > Ivan
> > > >
> > > > This is already done in 4.11, I’m not next to comp to check but
> > ShapeBlue
> > > > has a feature created that would allow for movement between different
> > > > roles.
> > > >
> > > > Regards
> > > > ilya
> > > >
> > > > On Thu, May 17, 2018 at 6:03 AM Ivan Kudryavtsev <
> > > kudryavtsev...@bw-sw.com
> > > > >
> > > > wrote:
> > > >
> > > > > Hello, community.
> > > > >
> > > > > I'm thinking about implementing the feature for accounts which
> > permits
> > > to
> > > > > change account role. Basically, the rationale is trials or
> > > demonstration
> > > > > modes which restricts users from doing extra stuff, like VM
> creation,
> > > > > service offering changes, etc. Basically, after trial the account
> > > should
> > > > be
> > > > > switched to a normal mode or removed. By permitting such role
> > switching
> > > > we
> > > > > can support the feature, otherwise we have to create unique role
> for
> > > > every
> > > > > user and manage it separately. Please, let me know your thoughts
> > about
> > > > > that. Have a good day.
> > > > >
> > > > > --
> > > > > With best regards, Ivan Kudryavtsev
> > > > > Bitworks Software, Ltd.
> > > > > Cell: +7-923-414-1515
> > > > > WWW: http://bitworks.software/ <http://bw-sw.com/>
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > With best regards, Ivan Kudryavtsev
> > > Bitworks Software, Ltd.
> > > Cell: +7-923-414-1515
> > > WWW: http://bitworks.software/ <http://bw-sw.com/>
> > >
> >
> >
> >
> > --
> > Daan
> >
>
>
>
> --
> With best regards, Ivan Kudryavtsev
> Bitworks Software, Ltd.
> Cell: +7-923-414-1515
> WWW: http://bitworks.software/ <http://bw-sw.com/>
>



-- 
Daan

Re: Dynamic roles question

[Daan Hoogland]

actually whet is in place is moving users between accounts, and thus
allowing for their role to change. The accounts would stay the same, but
the effective role of the users changes with it's account. MoverUserCmd is
the API.

On Fri, May 18, 2018 at 7:44 AM, Ivan Kudryavtsev 
wrote:

> Hello, Ilya.
> If it is already in place, then it's awesome. Thank you very much for
> assistance. I'll check it soon.
>
> 2018-05-18 14:37 GMT+07:00 ilya musayev :
>
> > Ivan
> >
> > This is already done in 4.11, I’m not next to comp to check but ShapeBlue
> > has a feature created that would allow for movement between different
> > roles.
> >
> > Regards
> > ilya
> >
> > On Thu, May 17, 2018 at 6:03 AM Ivan Kudryavtsev <
> kudryavtsev...@bw-sw.com
> > >
> > wrote:
> >
> > > Hello, community.
> > >
> > > I'm thinking about implementing the feature for accounts which permits
> to
> > > change account role. Basically, the rationale is trials or
> demonstration
> > > modes which restricts users from doing extra stuff, like VM creation,
> > > service offering changes, etc. Basically, after trial the account
> should
> > be
> > > switched to a normal mode or removed. By permitting such role switching
> > we
> > > can support the feature, otherwise we have to create unique role for
> > every
> > > user and manage it separately. Please, let me know your thoughts about
> > > that. Have a good day.
> > >
> > > --
> > > With best regards, Ivan Kudryavtsev
> > > Bitworks Software, Ltd.
> > > Cell: +7-923-414-1515
> > > WWW: http://bitworks.software/ 
> > >
> >
>
>
>
> --
> With best regards, Ivan Kudryavtsev
> Bitworks Software, Ltd.
> Cell: +7-923-414-1515
> WWW: http://bitworks.software/ 
>



-- 
Daan

Re: CloudStack Uasge lists expunged Volumes. Is that correct?

[Daan Hoogland]

Melanie,

The usage server hasn't really changed for 4.11 but it has some old
behaviour that might be counter intuitive. The fact that an expunged volume
is shown doesn't seem strange to me though. Before it was expunged it has
existed. There has been usage for the volume so there should be a usage
record. The question is whether usage after it's destroy time is reported.
A customer of mine has seen that VMs where reported running while being
destroyed. That is indeed a real annoyance and you might have something
like that as well. It seems that only 5 of those volumes should have been
reported between the 16th and the 16th, correct? Can you query for events
for those volumes in the event table? By the order of events we might be
able to draw some conclusions.


On Thu, May 17, 2018 at 1:59 PM, Melanie Desaive <
m.desa...@heinlein-support.de> wrote:

> Hi all,
>
> I am just starting to have a first look on CloudStack Usage Service in
> 4.11.
>
> Maybe I am getting something wrong, but to me it seems, that Usage
> reports lists destroyed and expunged Volumes. Is that the intended
> behaviour?
>
> For an example project it lists the following records:
>
> (rz-admin) :D > list usagerecords startdate=2018-05-16
> enddate=2018-05-16 projectid=a5496954-0f3c-4511-b54c-db9aa14ee9ac type=6
> filter=description,
> count = 18
> usagerecord:
> ++
> |  description   |
> ++
> |   Volume Id:  usage time (Template: 471)   |
> |   Volume Id: 2420 usage time (Template: 521)   |
> | Volume Id: 2567 usage time (DiskOffering: 147) |
> | Volume Id: 2719 usage time (DiskOffering: 96)  |
> | Volume Id: 2920 usage time (DiskOffering: 95)  |
> |   Volume Id: 2528 usage time (Template: 521)   |
> |   Volume Id: 2809 usage time (Template: 394)   |
> |   Volume Id: 2243 usage time (Template: 467)   |
> |   Volume Id: 2505 usage time (Template: 394)   |
> |   Volume Id: 2396 usage time (Template: 517)   |
> |   Volume Id: 3696 usage time (Template: 521)   |
> |   Volume Id: 2239 usage time (Template: 400)   |
> | Volume Id: 3174 usage time (DiskOffering: 95)  |
> |   Volume Id: 3675 usage time (Template: 521)   |
> |   Volume Id: 2172 usage time (Template: 394)   |
> |   Volume Id: 2225 usage time (Template: 390)   |
> |   Volume Id: 2223 usage time (Template: 471)   |
> |   Volume Id: 3255 usage time (Template: 521)   |
> ++
>
> Quering the IDs in the database I get records for a lot of destroyed and
> expunged volumes.
>
> mysql> select distinct id,removed,state from volumes where id= or
> id=2420 or id=2567 or id=2719 or id=2920 or id=2528 or id=2809 or
> id=2243 or id=2505 or id=2396 or id=3696 or id=2239 or id=3174 or
> id=3675 or id=2172 or id=2225 or id=2223 or id=3255 order by id;
> +--+-+--+
> | id   | removed | state|
> +--+-+--+
> | 2172 | 2017-08-28 12:37:57 | Destroy  |
> |  | 2017-01-30 13:06:40 | Destroy  |
> | 2223 | 2017-01-30 12:08:54 | Destroy  |
> | 2225 | 2017-01-30 13:06:21 | Destroy  |
> | 2239 | 2017-02-09 13:25:26 | Destroy  |
> | 2243 | 2017-08-28 12:28:36 | Destroy  |
> | 2396 | 2017-05-15 10:13:24 | Destroy  |
> | 2420 | 2017-08-28 11:48:57 | Destroy  |
> | 2505 | NULL| Ready|
> | 2528 | 2017-07-15 08:54:32 | Destroy  |
> | 2567 | 2017-08-28 12:27:57 | Destroy  |
> | 2719 | 2017-07-15 09:03:36 | Expunged |
> | 2809 | 2017-07-25 12:51:50 | Destroy  |
> | 2920 | 2017-10-24 12:12:05 | Expunged |
> | 3174 | NULL| Ready|
> | 3255 | NULL| Ready|
> | 3675 | NULL| Ready|
> | 3696 | NULL| Ready|
> +--+-+--+
> 18 rows in set (0.00 sec)
>
> I would usage expect to list only the volumes actually provisioned. So
> listing "Destroyed" volumes might be to be expected. But listing
> "Expunged" volumes seems wrong to me.
>
> Greetings,
>
> Melanie
> --
> --
>
> Heinlein Support GmbH
> Linux: Akademie - Support - Hosting
>
> http://www.heinlein-support.de
> Tel: 030 / 40 50 51 - 0
> Fax: 030 / 40 50 51 - 19
>
> Zwangsangaben lt. §35a GmbHG:
> HRB 93818 B / Amtsgericht Berlin-Charlottenburg,
> Geschäftsführer: Peer Heinlein  -- Sitz: Berlin
>
>


-- 
Daan

Re: [DISCUSS] VR upgrade downtime reduction

[Daan Hoogland]

good work Rohit,
I'll review 2508 https://github.com/apache/cloudstack/pull/2508

On Tue, May 1, 2018 at 12:08 PM, Rohit Yadav 
wrote:

> All,
>
>
> A short-term solution to VR upgrade or network restart (with cleanup=true)
> has been implemented:
>
>
> - The strategy for redundant VRs builds on top of Wei's original patch
> where backup routers are removed and replace in a rolling basis. The
> downtime I saw was usually 0-2 seconds, and theoretically downtime is
> maximum of [0, 3*advertisement interval + skew seconds] or 0-10 seconds
> (with cloudstack's default of 1s advertisement interval).
>
>
> - For non-redundant routers, I've implemented a strategy where first a new
> VR is deployed, then old VR is powered-off/destroyed, and the new VR is
> again re-programmed. With this strategy, two identical VRs may be up for a
> brief moment (few seconds) where both can serve traffic, however the new VR
> performs arp-ping on its interfaces to update neighbours. After the old VR
> is removed, the new VR is re-programmed which among many things performs
> another arpping. The theoretical downtime is therefore limited by the
> arp-cache refresh which can be up to 30 seconds. In my experiments, against
> various VMware, KVM and XenServer versions I found that the downtime was
> indeed less than 30s, usually between 5-20 seconds. Compared to older ACS
> versions, especially in cases where VRs deployment require full volume copy
> (like in VMware) a 10x-12x improvement was seen.
>
>
> Please review, test the following PRs which has test details, benchmarks,
> and some screenshots:
>
> https://github.com/apache/cloudstack/pull/2508
>
>
> Future work can be driven towards making all VRs redundant enabled by
> default that can allow for a firewall+connections state transfer
> (conntrackd + VRRP2/3 based) during rolling reboots.
>
>
> - Rohit
>
> <https://cloudstack.apache.org>
>
>
>
> 
> From: Daan Hoogland 
> Sent: Thursday, February 8, 2018 3:11:51 PM
> To: dev
> Subject: Re: [DISCUSS] VR upgrade downtime reduction
>
> to stop the vote and continue the discussion. I personally want unification
> of all router vms: VR, 'shared network', rVR, VPC, rVPC, and eventually the
> one we want to create for 'enterprise topology hand-off points'. And I
> think we have some level of consensus on that but the path there is a
> concern for Wido and for some of my colleagues as well, and rightly so. One
> issue is upgrades from older versions.
>
> I the common scenario as follows:
> + redundancy is deprecated and only number of instances remain.
> + an old VR is replicated in memory by an redundant enabled version, that
> will be in a state of running but inactive.
> - the old one will be destroyed while a ping is running
> - as soon as the ping fails more then three times in a row (this might have
> to have a hypervisor specific implementation or require a helper vm)
> + the new one is activated
>
> after this upgrade Wei's and/or Remi's code will do the work for any
> following upgrade.
>
> flames, please
>
>
>
> On Wed, Feb 7, 2018 at 12:17 PM, Nux!  wrote:
>
> > +1 too
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> >
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
> - Original Message -
> > > From: "Rene Moser" 
> > > To: "dev" 
> > > Sent: Wednesday, 7 February, 2018 10:11:45
> > > Subject: Re: [DISCUSS] VR upgrade downtime reduction
> >
> > > On 02/06/2018 02:47 PM, Remi Bergsma wrote:
> > >> Hi Daan,
> > >>
> > >> In my opinion the biggest issue is the fact that there are a lot of
> > different
> > >> code paths: VPC versus non-VPC, VPC versus redundant-VPC, etc. That's
> > why you
> > >> cannot simply switch from a single VPC to a redundant VPC for example.
> > >>
> > >> For SBP, we mitigated that in Cosmic by converting all non-VPCs to a
> > VPC with a
> > >> single tier and made sure all features are supported. Next we merged
> > the single
> > >> and redundant VPC code paths. The idea here is that redundancy or not
> > should
> > >> only be a difference in the number of routers. Code should be the
> same.
> > A
> > >> single router, is also "master" but there just is no "backup".
> > >>
> > >> That simplifies thi

Re: Not able to authenticate using microsoft AD

[Daan Hoogland]

​Shyam, Javier,

I found and fixed a bug, There is a PR out [1]. Are you able to test this?​
meaning creating your own package from that branch and trying?
​In the end it wasn't an AD specific bug but had to do with non-synced
accounts​. Unfortunately there was no test case for it. If it works it will
go into 4.11.1.

​[1] https://github.com/apache/cloudstack/pull/2517​


On Fri, Mar 23, 2018 at 10:10 AM, Daan Hoogland 
wrote:

> Shyam, please do raise a bug. I will not start on this immediately but
> this does need fixing. Can you leave all relevant data in the ticket, like
> logs and traces?
>
> On Wed, Mar 21, 2018 at 10:30 AM, Daan Hoogland 
> wrote:
>
>> ok, Javier and Shyam. This definitely sound like a bug. I have no idea
>> what might be the case and have to look. Can you enter and issue with
>> relevant data?
>>
>> On Tue, Mar 20, 2018 at 4:36 PM, Javier Rodríguez Caquilala <
>> javier.caquil...@adderglobal.com> wrote:
>>
>>>
>>> Hi Shyam,
>>> I have the same problem with AD authentication. My platform was working
>>> perfectly with CS 4.9.2. After the upgrade Cloudstack to 4.11 I can't login
>>> with LDAP users but I can list ldap users in "Add LDAP account". In log I
>>> get the following error:
>>> Authentication failure: {"loginresponse":{"uuidList":[
>>> ],"errorcode":531,"errortext":"Failed to authenticate user
>>> jav...@adderglobal.com in domain 1; please provide valid credentials"}}
>>>
>>> I check with tcpdump the communication between cloudstack-management and
>>> AD and I find cloudstack send correctly  a bindRequest and AD response was
>>> success so I think cloudstack is not interpreting the response in the right
>>> way.
>>>
>>>
>>>
>>>
>>> LDAPMessage bindRequest(1) 
>>> "CN=javier,OU=,OU=,OU=,DC=,DC="
>>> password
>>>
>>> LDAPMEssage bindResponse(1) "success"
>>>
>>>
>>>
>>>
>>> I compare the bind request and bindResponse in Cloudstack 4.9.2 and it
>>> looks like the same request an response.
>>>
>>> Regards,
>>> Javier
>>>
>>>
>>> -Mensaje original-
>>> > De: "soundar rajan" 
>>> > A: users@cloudstack.apache.org
>>> > Fecha: 20/03/18 12:59
>>> > Asunto: Re: Not able to authenticate using microsoft AD
>>> >
>>> > sometime while restarting i am getting this information
>>> >
>>> >  Did not find configuration ldap.username.attribute in Config.java.
>>> Perhaps
>>> > moved to ConfigDepot
>>> >
>>> > On Tue, Mar 20, 2018 at 4:53 PM, soundar rajan >> >
>>> > wrote:
>>> >
>>> > > yes its microsoftad and all the required parameters are configured
>>> > > correctly
>>> > >
>>> > > On Tue, Mar 20, 2018 at 3:22 PM, Daan Hoogland <
>>> daan.hoogl...@gmail.com>
>>> > > wrote:
>>> > >
>>> > >> Shyam, your reply to Rajani doesn't seem to include any settings.
>>> most
>>> > >> particularly what is the value of 'ldap.provider'?
>>> > >>
>>> > >>
>>> > >>
>>> > >> On Tue, Mar 20, 2018 at 9:49 AM, soundar rajan <
>>> bsoundara...@gmail.com>
>>> > >> wrote:
>>> > >>
>>> > >> > Hi Daan,
>>> > >> >
>>> > >> > Please find the log
>>> > >> >
>>> > >> > 2018-03-20 14:17:55,650 DEBUG [c.c.u.AccountManagerImpl]
>>> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) Attempting to log
>>> in
>>> > >> user:
>>> > >> > shyam.soundar in domain 1
>>> > >> > 2018-03-20 14:17:55,673 DEBUG [o.a.c.l.LdapContextFactory]
>>> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) initializing ldap
>>> with
>>> > >> > provider url: ldap://172.xx.xx.11:389
>>> > >> > 2018-03-20 14:17:55,724 DEBUG [o.a.c.l.LdapContextFactory]
>>> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) initializing ldap
>>> with
>>> > >> > provider url: ldap://172.xx.xx.11:389
>>> > >> > 2018-03-20 14:17:55,725 DEBUG [c.c.u.AccountManagerImpl]
>

Re: CS 4.11 ERR Unknow parameters listall

[Daan Hoogland]

Oliver,
'listall' is added in a generic way by the ui. It is not implemented by all
API, so no need to worry about it.

Biligual auto correct use.  Read at your own risico


On Sat, 24 Mar 2018, 23:49 Olivier GUIN,  wrote:

> Hello,
>
> When I display Hosts, I have this message :
> /WARN : Received unknown parameters for command listHosts. Unknown
> parameters : listall/
>
> And display systemvm :
> /WARN : Received unknown parameters for command listSystemVms. Unknown
> parameters : listall/
>
> /Can you help me ?/
>
> /Thank's,/
>
> /Olivier/
>
> /
> /
>
>
>

Re: Welcoming Mike as the new Apache CloudStack VP

[Daan Hoogland]

hang tough, Mike! And thanks, Wido.

On Tue, Mar 27, 2018 at 8:37 AM, Boris Stoyanov <
boris.stoya...@shapeblue.com> wrote:

> Thank you Wido and congrats Mike!
>
> -Boris Stoyanov
>
>
> boris.stoya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
> > On 27 Mar 2018, at 8:47, Marc-Aurèle Brothier  wrote:
> >
> > Thanks for the work Wido, and congrats Mike
> >
> > On Tue, Mar 27, 2018 at 6:31 AM, Jayapal Uradi <
> jayapal.ur...@accelerite.com
> >> wrote:
> >
> >> Congratulations, Milke!
> >>
> >> -Jayapal
> >>
> >>> On Mar 27, 2018, at 2:38 AM, Nitin Kumar Maharana  >> accelerite.com> wrote:
> >>>
> >>> Congratulations, Mike!!
> >>>
> >>> -
> >>> Nitin
> >>> On 26-Mar-2018, at 7:41 PM, Wido den Hollander  >> w...@widodh.nl>> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> It's been a great pleasure working with the CloudStack project as the
> >>> ACS VP over the past year.
> >>>
> >>> A big thank you from my side for everybody involved with the project in
> >>> the last year.
> >>>
> >>> Hereby I would like to announce that Mike Tutkowski has been elected to
> >>> replace me as the Apache Cloudstack VP in our annual VP rotation.
> >>>
> >>> Mike has a long history with the project and I am are happy welcome him
> >>> as the new VP for CloudStack.
> >>>
> >>> Welcome Mike!
> >>>
> >>> Thanks,
> >>>
> >>> Wido
> >>>
> >>> DISCLAIMER
> >>> ==
> >>> This e-mail may contain privileged and confidential information which
> is
> >> the property of Accelerite, a Persistent Systems business. It is
> intended
> >> only for the use of the individual or entity to which it is addressed.
> If
> >> you are not the intended recipient, you are not authorized to read,
> retain,
> >> copy, print, distribute or use this message. If you have received this
> >> communication in error, please notify the sender and delete all copies
> of
> >> this message. Accelerite, a Persistent Systems business does not accept
> any
> >> liability for virus infected mails.
> >>
> >>
>
>


-- 
Daan

Re: Not able to authenticate using microsoft AD

[Daan Hoogland]

Shyam, please do raise a bug. I will not start on this immediately but this
does need fixing. Can you leave all relevant data in the ticket, like logs
and traces?

On Wed, Mar 21, 2018 at 10:30 AM, Daan Hoogland 
wrote:

> ok, Javier and Shyam. This definitely sound like a bug. I have no idea
> what might be the case and have to look. Can you enter and issue with
> relevant data?
>
> On Tue, Mar 20, 2018 at 4:36 PM, Javier Rodríguez Caquilala <
> javier.caquil...@adderglobal.com> wrote:
>
>>
>> Hi Shyam,
>> I have the same problem with AD authentication. My platform was working
>> perfectly with CS 4.9.2. After the upgrade Cloudstack to 4.11 I can't login
>> with LDAP users but I can list ldap users in "Add LDAP account". In log I
>> get the following error:
>> Authentication failure: {"loginresponse":{"uuidList":[
>> ],"errorcode":531,"errortext":"Failed to authenticate user
>> jav...@adderglobal.com in domain 1; please provide valid credentials"}}
>>
>> I check with tcpdump the communication between cloudstack-management and
>> AD and I find cloudstack send correctly  a bindRequest and AD response was
>> success so I think cloudstack is not interpreting the response in the right
>> way.
>>
>>
>>
>>
>> LDAPMessage bindRequest(1) 
>> "CN=javier,OU=,OU=,OU=,DC=,DC="
>> password
>>
>> LDAPMEssage bindResponse(1) "success"
>>
>>
>>
>>
>> I compare the bind request and bindResponse in Cloudstack 4.9.2 and it
>> looks like the same request an response.
>>
>> Regards,
>> Javier
>>
>>
>> -Mensaje original-
>> > De: "soundar rajan" 
>> > A: users@cloudstack.apache.org
>> > Fecha: 20/03/18 12:59
>> > Asunto: Re: Not able to authenticate using microsoft AD
>> >
>> > sometime while restarting i am getting this information
>> >
>> >  Did not find configuration ldap.username.attribute in Config.java.
>> Perhaps
>> > moved to ConfigDepot
>> >
>> > On Tue, Mar 20, 2018 at 4:53 PM, soundar rajan 
>> > wrote:
>> >
>> > > yes its microsoftad and all the required parameters are configured
>> > > correctly
>> > >
>> > > On Tue, Mar 20, 2018 at 3:22 PM, Daan Hoogland <
>> daan.hoogl...@gmail.com>
>> > > wrote:
>> > >
>> > >> Shyam, your reply to Rajani doesn't seem to include any settings.
>> most
>> > >> particularly what is the value of 'ldap.provider'?
>> > >>
>> > >>
>> > >>
>> > >> On Tue, Mar 20, 2018 at 9:49 AM, soundar rajan <
>> bsoundara...@gmail.com>
>> > >> wrote:
>> > >>
>> > >> > Hi Daan,
>> > >> >
>> > >> > Please find the log
>> > >> >
>> > >> > 2018-03-20 14:17:55,650 DEBUG [c.c.u.AccountManagerImpl]
>> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) Attempting to log
>> in
>> > >> user:
>> > >> > shyam.soundar in domain 1
>> > >> > 2018-03-20 14:17:55,673 DEBUG [o.a.c.l.LdapContextFactory]
>> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) initializing ldap
>> with
>> > >> > provider url: ldap://172.xx.xx.11:389
>> > >> > 2018-03-20 14:17:55,724 DEBUG [o.a.c.l.LdapContextFactory]
>> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) initializing ldap
>> with
>> > >> > provider url: ldap://172.xx.xx.11:389
>> > >> > 2018-03-20 14:17:55,725 DEBUG [c.c.u.AccountManagerImpl]
>> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) Unable to
>> authenticate
>> > >> user
>> > >> > with username shyam.soundar in domain 1
>> > >> > 2018-03-20 14:17:55,726 DEBUG [c.c.u.AccountManagerImpl]
>> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) User:
>> shyam.soundar in
>> > >> > domain 1 has failed to log in
>> > >> > 2018-03-20 14:17:55,728 DEBUG [c.c.a.ApiServlet]
>> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) Authentication
>> failure:
>> > >> > {"loginresponse":{"uuidList":[],"errorcode":531,"errortext":"Failed
>> to
>> > >> > authenticate user 

Re: Not able to authenticate using microsoft AD

[Daan Hoogland]

ok, Javier and Shyam. This definitely sound like a bug. I have no idea what
might be the case and have to look. Can you enter and issue with relevant
data?

On Tue, Mar 20, 2018 at 4:36 PM, Javier Rodríguez Caquilala <
javier.caquil...@adderglobal.com> wrote:

>
> Hi Shyam,
> I have the same problem with AD authentication. My platform was working
> perfectly with CS 4.9.2. After the upgrade Cloudstack to 4.11 I can't login
> with LDAP users but I can list ldap users in "Add LDAP account". In log I
> get the following error:
> Authentication failure: {"loginresponse":{"uuidList":[
> ],"errorcode":531,"errortext":"Failed to authenticate user
> jav...@adderglobal.com in domain 1; please provide valid credentials"}}
>
> I check with tcpdump the communication between cloudstack-management and
> AD and I find cloudstack send correctly  a bindRequest and AD response was
> success so I think cloudstack is not interpreting the response in the right
> way.
>
>
>
>
> LDAPMessage bindRequest(1) "CN=javier,OU=,OU=,OU=,DC=,DC="
> password
>
> LDAPMEssage bindResponse(1) "success"
>
>
>
>
> I compare the bind request and bindResponse in Cloudstack 4.9.2 and it
> looks like the same request an response.
>
> Regards,
> Javier
>
>
> -Mensaje original-
> > De: "soundar rajan" 
> > A: users@cloudstack.apache.org
> > Fecha: 20/03/18 12:59
> > Asunto: Re: Not able to authenticate using microsoft AD
> >
> > sometime while restarting i am getting this information
> >
> >  Did not find configuration ldap.username.attribute in Config.java.
> Perhaps
> > moved to ConfigDepot
> >
> > On Tue, Mar 20, 2018 at 4:53 PM, soundar rajan 
> > wrote:
> >
> > > yes its microsoftad and all the required parameters are configured
> > > correctly
> > >
> > > On Tue, Mar 20, 2018 at 3:22 PM, Daan Hoogland <
> daan.hoogl...@gmail.com>
> > > wrote:
> > >
> > >> Shyam, your reply to Rajani doesn't seem to include any settings. most
> > >> particularly what is the value of 'ldap.provider'?
> > >>
> > >>
> > >>
> > >> On Tue, Mar 20, 2018 at 9:49 AM, soundar rajan <
> bsoundara...@gmail.com>
> > >> wrote:
> > >>
> > >> > Hi Daan,
> > >> >
> > >> > Please find the log
> > >> >
> > >> > 2018-03-20 14:17:55,650 DEBUG [c.c.u.AccountManagerImpl]
> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) Attempting to log in
> > >> user:
> > >> > shyam.soundar in domain 1
> > >> > 2018-03-20 14:17:55,673 DEBUG [o.a.c.l.LdapContextFactory]
> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) initializing ldap
> with
> > >> > provider url: ldap://172.xx.xx.11:389
> > >> > 2018-03-20 14:17:55,724 DEBUG [o.a.c.l.LdapContextFactory]
> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) initializing ldap
> with
> > >> > provider url: ldap://172.xx.xx.11:389
> > >> > 2018-03-20 14:17:55,725 DEBUG [c.c.u.AccountManagerImpl]
> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) Unable to
> authenticate
> > >> user
> > >> > with username shyam.soundar in domain 1
> > >> > 2018-03-20 14:17:55,726 DEBUG [c.c.u.AccountManagerImpl]
> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) User: shyam.soundar
> in
> > >> > domain 1 has failed to log in
> > >> > 2018-03-20 14:17:55,728 DEBUG [c.c.a.ApiServlet]
> > >> > (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) Authentication
> failure:
> > >> > {"loginresponse":{"uuidList":[],"errorcode":531,"errortext":"Failed
> to
> > >> > authenticate user shyam.soundar in domain 1; please provide valid
> > >> > credentials"}}
> > >> >
> > >> > Regards
> > >> > Shyam
> > >> >
> > >> > On Tue, Mar 20, 2018 at 12:58 PM, Daan Hoogland <
> > >> daan.hoogl...@gmail.com>
> > >> > wrote:
> > >> >
> > >> > > not at first glance no, it can be a configuration or a code bug.
> Can
> > >> you
> > >> > > find anything in the logs around the moment of the login?
> > >> > >
> > >> > > On Tue, Mar 2

Re: Not able to authenticate using microsoft AD

[Daan Hoogland]

Shyam

On Tue, Mar 20, 2018 at 12:52 PM, soundar rajan 
wrote:
​
​..​

>   Did not find configuration ldap.username.attribute in Config.java.
> Perhaps
> moved to ConfigDepot
>
​this is not an issue.​

Re: Not able to authenticate using microsoft AD

[Daan Hoogland]

Shyam, your reply to Rajani doesn't seem to include any settings. most
particularly what is the value of 'ldap.provider'?



On Tue, Mar 20, 2018 at 9:49 AM, soundar rajan 
wrote:

> Hi Daan,
>
> Please find the log
>
> 2018-03-20 14:17:55,650 DEBUG [c.c.u.AccountManagerImpl]
> (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) Attempting to log in user:
> shyam.soundar in domain 1
> 2018-03-20 14:17:55,673 DEBUG [o.a.c.l.LdapContextFactory]
> (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) initializing ldap with
> provider url: ldap://172.xx.xx.11:389
> 2018-03-20 14:17:55,724 DEBUG [o.a.c.l.LdapContextFactory]
> (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) initializing ldap with
> provider url: ldap://172.xx.xx.11:389
> 2018-03-20 14:17:55,725 DEBUG [c.c.u.AccountManagerImpl]
> (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) Unable to authenticate user
> with username shyam.soundar in domain 1
> 2018-03-20 14:17:55,726 DEBUG [c.c.u.AccountManagerImpl]
> (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) User: shyam.soundar in
> domain 1 has failed to log in
> 2018-03-20 14:17:55,728 DEBUG [c.c.a.ApiServlet]
> (qtp510113906-27:ctx-d5e5dcf9) (logid:4d1b7c7c) Authentication failure:
> {"loginresponse":{"uuidList":[],"errorcode":531,"errortext":"Failed to
> authenticate user shyam.soundar in domain 1; please provide valid
> credentials"}}
>
> Regards
> Shyam
>
> On Tue, Mar 20, 2018 at 12:58 PM, Daan Hoogland 
> wrote:
>
> > not at first glance no, it can be a configuration or a code bug. Can you
> > find anything in the logs around the moment of the login?
> >
> > On Tue, Mar 20, 2018 at 6:56 AM, soundar rajan 
> > wrote:
> >
> > > Hi Daan,
> > >
> > > I dont see any request hitting  our domain controller while logging
> but i
> > > am able to import all users. Any idea.
> > >
> > > Regards
> > > Shyam
> > >
> > > On Mon, Mar 19, 2018 at 11:20 PM, Daan Hoogland <
> daan.hoogl...@gmail.com
> > >
> > > wrote:
> > >
> > > > Shyam, do you have any related log message, preferably with stack
> trace
> > > > that is related? Do you see that request are coming in on your AD?
> > > >
> > > > On Mon, Mar 19, 2018 at 12:41 PM, soundar rajan <
> > bsoundara...@gmail.com>
> > > > wrote:
> > > >
> > > > > Please find the error message
> > > > >
> > > > > Authentication failure:
> > > > > {"loginresponse":{"uuidList":[],"errorcode":531,"errortext":
> "Failed
> > to
> > > > > authenticate user shyam.soundar in domain 1; please provide valid
> > > > > credentials"}}
> > > > >
> > > > >
> > > > > On Mon, Mar 19, 2018 at 6:10 PM, soundar rajan <
> > bsoundara...@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Version i use is 4.11
> > > > > >
> > > > > > Regards
> > > > > > Shyam
> > > > > >
> > > > > > On Mon, Mar 19, 2018 at 5:38 PM, Daan Hoogland <
> > > > daan.hoogl...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > >> Shyam, sorry to hear. What versions are you using?
> > > > > >>
> > > > > >> On Mon, Mar 19, 2018 at 11:55 AM, soundar rajan <
> > > > bsoundara...@gmail.com
> > > > > >
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Hi ALL,
> > > > > >> >
> > > > > >> > I have successfully configured Active directory and able to
> > import
> > > > the
> > > > > >> > users to cloudstack.
> > > > > >> >
> > > > > >> > But users is not able to login with there domain credentials
> do
> > i
> > > > miss
> > > > > >> > anything in the configuration?
> > > > > >> >
> > > > > >> > Regards
> > > > > >> > Shyam
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> Daan
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Daan
> > > >
> > >
> >
> >
> >
> > --
> > Daan
> >
>



-- 
Daan

Re: Not able to authenticate using microsoft AD

[Daan Hoogland]

not at first glance no, it can be a configuration or a code bug. Can you
find anything in the logs around the moment of the login?

On Tue, Mar 20, 2018 at 6:56 AM, soundar rajan 
wrote:

> Hi Daan,
>
> I dont see any request hitting  our domain controller while logging but i
> am able to import all users. Any idea.
>
> Regards
> Shyam
>
> On Mon, Mar 19, 2018 at 11:20 PM, Daan Hoogland 
> wrote:
>
> > Shyam, do you have any related log message, preferably with stack trace
> > that is related? Do you see that request are coming in on your AD?
> >
> > On Mon, Mar 19, 2018 at 12:41 PM, soundar rajan 
> > wrote:
> >
> > > Please find the error message
> > >
> > > Authentication failure:
> > > {"loginresponse":{"uuidList":[],"errorcode":531,"errortext":"Failed to
> > > authenticate user shyam.soundar in domain 1; please provide valid
> > > credentials"}}
> > >
> > >
> > > On Mon, Mar 19, 2018 at 6:10 PM, soundar rajan  >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > Version i use is 4.11
> > > >
> > > > Regards
> > > > Shyam
> > > >
> > > > On Mon, Mar 19, 2018 at 5:38 PM, Daan Hoogland <
> > daan.hoogl...@gmail.com>
> > > > wrote:
> > > >
> > > >> Shyam, sorry to hear. What versions are you using?
> > > >>
> > > >> On Mon, Mar 19, 2018 at 11:55 AM, soundar rajan <
> > bsoundara...@gmail.com
> > > >
> > > >> wrote:
> > > >>
> > > >> > Hi ALL,
> > > >> >
> > > >> > I have successfully configured Active directory and able to import
> > the
> > > >> > users to cloudstack.
> > > >> >
> > > >> > But users is not able to login with there domain credentials do i
> > miss
> > > >> > anything in the configuration?
> > > >> >
> > > >> > Regards
> > > >> > Shyam
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Daan
> > > >>
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Daan
> >
>



-- 
Daan

Re: Not able to authenticate using microsoft AD

[Daan Hoogland]

Shyam, do you have any related log message, preferably with stack trace
that is related? Do you see that request are coming in on your AD?

On Mon, Mar 19, 2018 at 12:41 PM, soundar rajan 
wrote:

> Please find the error message
>
> Authentication failure:
> {"loginresponse":{"uuidList":[],"errorcode":531,"errortext":"Failed to
> authenticate user shyam.soundar in domain 1; please provide valid
> credentials"}}
>
>
> On Mon, Mar 19, 2018 at 6:10 PM, soundar rajan 
> wrote:
>
> > Hi,
> >
> > Version i use is 4.11
> >
> > Regards
> > Shyam
> >
> > On Mon, Mar 19, 2018 at 5:38 PM, Daan Hoogland 
> > wrote:
> >
> >> Shyam, sorry to hear. What versions are you using?
> >>
> >> On Mon, Mar 19, 2018 at 11:55 AM, soundar rajan  >
> >> wrote:
> >>
> >> > Hi ALL,
> >> >
> >> > I have successfully configured Active directory and able to import the
> >> > users to cloudstack.
> >> >
> >> > But users is not able to login with there domain credentials do i miss
> >> > anything in the configuration?
> >> >
> >> > Regards
> >> > Shyam
> >> >
> >>
> >>
> >>
> >> --
> >> Daan
> >>
> >
> >
>



-- 
Daan

Re: Not able to authenticate using microsoft AD

[Daan Hoogland]

Shyam, sorry to hear. What versions are you using?

On Mon, Mar 19, 2018 at 11:55 AM, soundar rajan 
wrote:

> Hi ALL,
>
> I have successfully configured Active directory and able to import the
> users to cloudstack.
>
> But users is not able to login with there domain credentials do i miss
> anything in the configuration?
>
> Regards
> Shyam
>



-- 
Daan

Re: CCS (Cloudstack Container Service) in CloudStack 4.11

[Daan Hoogland]

Don't bother. Ccs will not work with 4.9

Biligual auto correct use.  Read at your own risico

On 13 Mar 2018 18:05, "Parth Patel"  wrote:

Hi Da'an,

I will give that a try, till then I will try the ccs first with ACS 4.9 :P

Thanks,
Parth Patel

On Tue, 13 Mar 2018 at 17:39 Daan Hoogland  wrote:

> Parth, The plugin 1.0 won't work with any version beyond 4.9 (4.7 and 4.7
> aren't tested). There is a branch, 'on-top-of-pr-2071-for-4.10
> <https://github.com/shapeblue/ccs/tree/on-top-of-pr-2071-for-4.10>', that
> we are now porting to 4.11. If you have capability to build it you can try
> that.
>
> On Tue, Mar 13, 2018 at 1:03 PM, Parth Patel 
> wrote:
>
> > Hi,
> >
> > Maybe somebody working in ShapeBlue can help me. I am trying to
integrate
> > CCS service (https://github.com/shapeblue/ccs) with ACS 4.11 using
> > http://downloads.shapeblue.com/ccs/1.0/Installation_and_
> > Administration_Guide.pdf
> > and
> > I quickly came to know about huge architecture changes that ACS has gone
> > through in the latest release. I somehow managed to bring the UI by
> editing
> > and placing the ccs folder in the new "webapp" folder instead of
> "webapps"
> > folder. But I am confused as to where to place the shapeblue-ccs and
> > flyaway core jar files. I tried placing them in
> > /usr/share/cloudstack-management/lib folder but it gave the following
> > error
> > in management-server.log:
> >
> >
> > 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Loading module context [ccs] from URL
> > [jar:file:/usr/share/cloudstack-management/webapp/
> > WEB-INF/lib/cloud-plugin-shapeblue-ccs-1.0.1.jar!/META-
> > INF/cloudstack/ccs/spring-ccs-context.xml]
> > 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Loading module context [ccs] from URL
> > [jar:file:/usr/share/cloudstack-management/lib/
> > cloudstack-4.11.0.0.jar!/META-INF/cloudstack/compute/spring-
> > core-lifecycle-compute-context-inheritable.xml]
> > 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Loading module context [ccs] from URL
> > [jar:file:/usr/share/cloudstack-management/lib/
> > cloudstack-4.11.0.0.jar!/META-INF/cloudstack/core/spring-
> > core-lifecycle-core-context-inheritable.xml]
> > 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Loading module context [ccs] from URL
> > [jar:file:/usr/share/cloudstack-management/lib/
> > cloudstack-4.11.0.0.jar!/META-INF/cloudstack/system/spring-
> > framework-config-system-context-inheritable.xml]
> > 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Loading module context [ccs] from URL
> > [jar:file:/usr/share/cloudstack-management/lib/
> > cloudstack-4.11.0.0.jar!/META-INF/cloudstack/system/spring-
> > core-system-context-inheritable.xml]
> > 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Loading module context [ccs] from URL
> > [jar:file:/usr/share/cloudstack-management/lib/
> > cloudstack-4.11.0.0.jar!/META-INF/cloudstack/system/spring-
> > contrail-system-context-inheritable.xml]
> > 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> > (main:null) (logid:) Loading module context [ccs] from URL
> > [jar:file:/usr/share/cloudstack-management/lib/
> > cloudstack-4.11.0.0.jar!/META-INF/cloudstack/bootstrap/
> > spring-bootstrap-context-inheritable.xml]
> > 2018-03-13 16:59:28,098 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> > (main:null) (logid:) Exception encountered during context initialization
> -
> > cancelling refresh attempt:
> > org.springframework.beans.factory.BeanCreationException: Error creating
> > bean with name 'ContainerClusterManagerImpl': Lookup method resolution
> > failed; nested exception is java.lang.IllegalStateException: Failed to
> > introspect Class [com.cloud.containercluster.
ContainerClusterManagerImpl]
> > from ClassLoader [WebAppClassLoader=500772834@1dd92fe2]
> > 2018-03-13 16:59:28,100 WARN  [o.e.j.w.WebAppContext] (main:null)
> (logid:)
> > Failed startup of context o.e.j.w.WebAppContext@365c30cc
> > {/client,file:///usr/share/cloudstack-management/webapp/,
> > UNAVAILABLE}{/usr/share/cloudstack-management/webapp}
> > org.springframework.beans.factory.BeanCreationException: Error creating
> > bean with name 'ContainerClusterM

Re: CCS (Cloudstack Container Service) in CloudStack 4.11

[Daan Hoogland]

Parth, The plugin 1.0 won't work with any version beyond 4.9 (4.7 and 4.7
aren't tested). There is a branch, 'on-top-of-pr-2071-for-4.10
', that
we are now porting to 4.11. If you have capability to build it you can try
that.

On Tue, Mar 13, 2018 at 1:03 PM, Parth Patel 
wrote:

> Hi,
>
> Maybe somebody working in ShapeBlue can help me. I am trying to integrate
> CCS service (https://github.com/shapeblue/ccs) with ACS 4.11 using
> http://downloads.shapeblue.com/ccs/1.0/Installation_and_
> Administration_Guide.pdf
> and
> I quickly came to know about huge architecture changes that ACS has gone
> through in the latest release. I somehow managed to bring the UI by editing
> and placing the ccs folder in the new "webapp" folder instead of "webapps"
> folder. But I am confused as to where to place the shapeblue-ccs and
> flyaway core jar files. I tried placing them in
> /usr/share/cloudstack-management/lib folder but it gave the following
> error
> in management-server.log:
>
>
> 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:null) (logid:) Loading module context [ccs] from URL
> [jar:file:/usr/share/cloudstack-management/webapp/
> WEB-INF/lib/cloud-plugin-shapeblue-ccs-1.0.1.jar!/META-
> INF/cloudstack/ccs/spring-ccs-context.xml]
> 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:null) (logid:) Loading module context [ccs] from URL
> [jar:file:/usr/share/cloudstack-management/lib/
> cloudstack-4.11.0.0.jar!/META-INF/cloudstack/compute/spring-
> core-lifecycle-compute-context-inheritable.xml]
> 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:null) (logid:) Loading module context [ccs] from URL
> [jar:file:/usr/share/cloudstack-management/lib/
> cloudstack-4.11.0.0.jar!/META-INF/cloudstack/core/spring-
> core-lifecycle-core-context-inheritable.xml]
> 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:null) (logid:) Loading module context [ccs] from URL
> [jar:file:/usr/share/cloudstack-management/lib/
> cloudstack-4.11.0.0.jar!/META-INF/cloudstack/system/spring-
> framework-config-system-context-inheritable.xml]
> 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:null) (logid:) Loading module context [ccs] from URL
> [jar:file:/usr/share/cloudstack-management/lib/
> cloudstack-4.11.0.0.jar!/META-INF/cloudstack/system/spring-
> core-system-context-inheritable.xml]
> 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:null) (logid:) Loading module context [ccs] from URL
> [jar:file:/usr/share/cloudstack-management/lib/
> cloudstack-4.11.0.0.jar!/META-INF/cloudstack/system/spring-
> contrail-system-context-inheritable.xml]
> 2018-03-13 16:59:27,953 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:null) (logid:) Loading module context [ccs] from URL
> [jar:file:/usr/share/cloudstack-management/lib/
> cloudstack-4.11.0.0.jar!/META-INF/cloudstack/bootstrap/
> spring-bootstrap-context-inheritable.xml]
> 2018-03-13 16:59:28,098 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> (main:null) (logid:) Exception encountered during context initialization -
> cancelling refresh attempt:
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'ContainerClusterManagerImpl': Lookup method resolution
> failed; nested exception is java.lang.IllegalStateException: Failed to
> introspect Class [com.cloud.containercluster.ContainerClusterManagerImpl]
> from ClassLoader [WebAppClassLoader=500772834@1dd92fe2]
> 2018-03-13 16:59:28,100 WARN  [o.e.j.w.WebAppContext] (main:null) (logid:)
> Failed startup of context o.e.j.w.WebAppContext@365c30cc
> {/client,file:///usr/share/cloudstack-management/webapp/,
> UNAVAILABLE}{/usr/share/cloudstack-management/webapp}
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'ContainerClusterManagerImpl': Lookup method resolution
> failed; nested exception is java.lang.IllegalStateException: Failed to
> introspect Class [com.cloud.containercluster.ContainerClusterManagerImpl]
> from ClassLoader [WebAppClassLoader=500772834@1dd92fe2]
> at
> org.springframework.beans.factory.annotation.
> AutowiredAnnotationBeanPostProcessor.determineCandidateConstructors(
> AutowiredAnnotationBeanPostProcessor.java:262)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.determineConstructorsFromBeanPostProcessors(
> AbstractAutowireCapableBeanFactory.java:1198)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1123)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.createBean(Abstrac

Re: first timer - quickstart feedback

[Daan Hoogland]

Gomez, for documentation you can also enter a PR on github to have it fixed
directly

On Thu, Mar 8, 2018 at 9:26 AM, Paul Angus  wrote:

> Hi Gomez,
>
> Are you familiar with Jira?
> https://issues.apache.org/jira/projects/CLOUDSTACK/
> issues/CLOUDSTACK-10267?filter=allopenissues
>
> This the best place to put issues, however you can email them in and
> hopefully someone will have time to update Jira and the documentation.
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: gomez 
> Sent: 08 March 2018 03:27
> To: users@cloudstack.apache.org
> Subject: first timer - quickstart feedback
>
> hello,
>
> first time user and quick start guide consumer and i have some feedback
> for the guide. is this the place to drop that feedback or should it go to
> issues? thanks!
>



-- 
Daan

Re: [DISCUSS] DB upgrade issue workaround for 4.10.0.0 users upgrading to 4.11.0.0

[Daan Hoogland]

the -x would only add it to the comment making it harder to find. As for
multiple stable branches; merging forward always folows all branches
forward so a fix on 4.9 would be merged forward to 4.10 and then 4.10 would
be merged forward again to 4.11 and finally to master. of course there is
always work to do in terms of solving merge conflicts but these are
generally less then port work as the order of any commits to the
intemediats is always preserved.

On Wed, Feb 14, 2018 at 6:15 PM, Rene Moser  wrote:

> Hi Daan
>
> On 02/14/2018 05:26 PM, Daan Hoogland wrote:
> > Rene,
> >
> > The issue is certainly not due the git workflow but to upgrade schemes we
> > have.
> >
> > The result of this workflow for us is that it is easier to find to which
> > branches a particular commit is added as by merging forward the commit id
> > of the actual fix doesn't change. so instead of looking in each branch
> for
> > a bit of code you can look for a commit id on a branches log.
>
> Ah I see.
>
> However, the same can be achieved by adding -x to cherry-picks (to add
> the origin commit id), without the downside that a fix can "only" go
> into one stable branch.
>
> Keep in mind, we certainly do have more than one stable branch at a time
> (4.11-lts, 4.12). A fix should be applicable to any stable branch.
>
> Or how would this work with the current workflow?
>
> René
>
>
>
>
>
>


-- 
Daan

Re: [DISCUSS] DB upgrade issue workaround for 4.10.0.0 users upgrading to 4.11.0.0

[Daan Hoogland]

Rene,

The issue is certainly not due the git workflow but to upgrade schemes we
have.

The result of this workflow for us is that it is easier to find to which
branches a particular commit is added as by merging forward the commit id
of the actual fix doesn't change. so instead of looking in each branch for
a bit of code you can look for a commit id on a branches log.


On Wed, Feb 14, 2018 at 4:54 PM, Rene Moser  wrote:

> Hi all
>
> Thanks for taking care of this issue.
>
> However, I wonder how we can prevent such issues in the future and
> wondering if this "incident" has its orginos by our current git workflow.
>
> I find the workflow "commit to stable branch --> merge back to master"
> is inconvenient. Because at one point, the branches divert too much
> (think of refactorings on master branch) and a merge back to the master
> would not work or would break.
>
> In most of the project I work with, there are stable-branches as well
> but any fix (and feature of course) has to be on master first. Any
> serious fix could be cherry picked to stable branches (there may be more
> than one) if applicable or an alternative fix could be made. stable
> branches never receives merges from or to master branch.
>
> To be honest, I haven't seen any project adopting this workflow, I
> wondered why and how come we have this workflow.
>
> Thanks for clarification.
>
> René
>
>
>
> On 02/12/2018 02:29 PM, Rohit Yadav wrote:
> > All,
> >
> >
> > Some of us have discussed and found an upgrade path issue that only
> affects the 4.10.0.0 users who may see missing columns in certain tables
> post upgrading to 4.11.0.0 version.
> >
> >
> > The issue is/was that at the time 4.10.0.0 was released, PRs were merged
> to the 'then' master branch that made changes to the 4.9.3.0->4.10.0.0
> upgrade path instead of the 4.10.0.0->4.11.0.0 upgrade path. One of such
> change was an ALTER statement that added a new column `service_package_id`,
> and if 4.10.0.0 version is upgraded to 4.11.0.0 such environments may
> report sql related errors related to this column.
> >
> >
> > (My colleagues Bobby and Ernie may chip in their findings and test
> results as well)
> >
> >
> > Pull request: https://github.com/apache/cloudstack/pull/2452
> >
> > Jira ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> >
> >
> > The proposed workaround is to move the changes to the expected upgrade
> path of 4.10.0.0->4.11.0.0. This is *not ideal* given 4.11.0.0 is released
> but at least 4.10.0.0 users who may want to upgrade to 4.11.1.0 or later
> won't face the issue.
> >
> >
> > The proposed workaround for current 4.10.0.0 users who may want to
> upgrade to 4.11.0.0 is to run the following sql statements from the PR
> above before upgrading to 4.11.0.0: (we may discuss and update the
> release notes website as well)
> >
> >
> > ### start sql ###
> >
> >
> > use cloud;
> >
> >
> > CREATE TABLE IF NOT EXISTS `cloud`.`netscaler_servicepackages` (
> >   `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id',
> >   `uuid` varchar(255) UNIQUE,
> >   `name` varchar(255) UNIQUE COMMENT 'name of the service package',
> >   `description` varchar(255) COMMENT 'description of the service
> package',
> >   PRIMARY KEY  (`id`)
> > ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
> >
> > CREATE TABLE IF NOT EXISTS `cloud`.`external_netscaler_controlcenter` (
> >   `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id',
> >   `uuid` varchar(255) UNIQUE,
> >   `username` varchar(255) COMMENT 'username of the NCC',
> >   `password` varchar(255) COMMENT 'password of NCC',
> >   `ncc_ip` varchar(255) COMMENT 'IP of NCC Manager',
> >   `num_retries` bigint unsigned NOT NULL default 2 COMMENT 'Number of
> retries in ncc for command failure',
> >   PRIMARY KEY  (`id`)
> > ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
> >
> > ALTER TABLE `cloud`.`sslcerts` ADD COLUMN `name` varchar(255) NULL
> default NULL COMMENT 'Name of the Certificate';
> > ALTER TABLE `cloud`.`network_offerings` ADD COLUMN `service_package_id`
> varchar(255) NULL default NULL COMMENT 'Netscaler ControlCenter Service
> Package';
> >
> >
> > DROP VIEW IF EXISTS `cloud`.`user_view`;
> > CREATE VIEW `cloud`.`user_view` AS
> > select
> > user.id,
> > user.uuid,
> > user.username,
> > user.password,
> > user.firstname,
> > user.lastname,
> > user.email,
> > user.state,
> > user.api_key,
> > user.secret_key,
> > user.created,
> > user.removed,
> > user.timezone,
> > user.registration_token,
> > user.is_registered,
> > user.incorrect_login_attempts,
> > user.source,
> > user.default,
> > account.id account_id,
> > account.uuid account_uuid,
> > account.account_name account_name,
> > account.type account_type,
> > account.role_id account_role_id,
> > domain.id domain_id,
> > domain.uuid domain_uuid,
> > do

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

[Daan Hoogland]

ood to hear Jevgeni, good floating..

On Fri, Feb 9, 2018 at 5:42 PM, Jevgeni Zolotarjov 
wrote:

> To finalize, IPs recovered too. I think I started my VMs too early before
> router was up.
>
> Now its all fine.
>
> On Fri, Feb 9, 2018 at 6:36 PM, Paul Angus 
> wrote:
>
> > No problem, I'm pleased that you're sorted.
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com]
> > Sent: 09 February 2018 16:34
> > To: users@cloudstack.apache.org
> > Subject: Re: cloudstack-management fails to start after upgrade 4.10 ->
> > 4.11
> >
> > destroyed virtual router
> >
> > it got recreated.
> > On NOW. My VMs start!!!
> >
> > All IPs got changed, but I can manage with that.
> >
> > Thank you for your support
> >
> > On Fri, Feb 9, 2018 at 6:21 PM, Paul Angus 
> > wrote:
> >
> > > Have you done the same for the virtual routers?
> > >
> > > I'll look at your log in the meantime
> > >
> > >
> > > Kind regards,
> > >
> > > Paul Angus
> > >
> > > paul.an...@shapeblue.com
> > > www.shapeblue.com
> > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> > >
> > >
> > >
> > >
> > > -Original Message-
> > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com]
> > > Sent: 09 February 2018 16:19
> > > To: users@cloudstack.apache.org
> > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 ->
> > > 4.11
> > >
> > > I destroyed system VMs and they got recreated automatically.
> > > They are running. I can verify that by
> > > virsh list --all
> > >
> > > and
> > > I can see their console and it sugests that it is Cloudstack 4.11
> > systemVM
> > >
> > > BUT
> > > it didn't solve the problem. None of my own VM is listed by "virsh list
> > > -all". They do not start.
> > > I tried to create new VM, it does not start either, due to to the same
> > > problem - insufficient capacity
> > >
> > > On Fri, Feb 9, 2018 at 6:02 PM, Daan Hoogland  >
> > > wrote:
> > >
> > > > listen to Paul, not to me.
> > > > He's an operator i'm just impatient
> > > >
> > > > On Fri, Feb 9, 2018 at 5:00 PM, Paul Angus  >
> > > > wrote:
> > > >
> > > > > After upgrading the code of the mgmt. server you need upgrade your
> > > > > system VMs from the old template to ones using the new templates.
> > > > >
> > > > > This needs to be done for the SSVM, CPVM and all of your virtual
> > > routers.
> > > > >
> > > > > For the SSVM & CPVM you do this by destroying them and CloudStack
> > > > > will recreate them with the new template.
> > > > > For the virtual routers, you can go to each of them in turn in the
> > > > > UI and there will be a upgrade router button.
> > > > >
> > > > > You get to these through the infrastructure tab in the UI.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > paul.an...@shapeblue.com
> > > > > www.shapeblue.com
> > > > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > -Original Message-
> > > > > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com]
> > > > > Sent: 09 February 2018 15:55
> > > > > To: users@cloudstack.apache.org
> > > > > Subject: Re: cloudstack-management fails to start after upgrade
> 4.10
> > ->
> > > > > 4.11
> > > > >
> > > > > Destroyed VMs? No. Definitely not.
> > > > >
> > > > > At least I can see them all under web console Home->Instances. Can
> > make
> > > > > snapshots even
> > > > >
> > > > > My todays management server log https://www.sendspace.com/
> > file/nxxgg0
> > > > >
> > > &

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

[Daan Hoogland]

listen to Paul, not to me.
He's an operator i'm just impatient

On Fri, Feb 9, 2018 at 5:00 PM, Paul Angus  wrote:

> After upgrading the code of the mgmt. server you need upgrade your system
> VMs from the old template to ones using the new templates.
>
> This needs to be done for the SSVM, CPVM and all of your virtual routers.
>
> For the SSVM & CPVM you do this by destroying them and CloudStack will
> recreate them with the new template.
> For the virtual routers, you can go to each of them in turn in the UI and
> there will be a upgrade router button.
>
> You get to these through the infrastructure tab in the UI.
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com]
> Sent: 09 February 2018 15:55
> To: users@cloudstack.apache.org
> Subject: Re: cloudstack-management fails to start after upgrade 4.10 ->
> 4.11
>
> Destroyed VMs? No. Definitely not.
>
> At least I can see them all under web console Home->Instances. Can make
> snapshots even
>
> My todays management server log https://www.sendspace.com/file/nxxgg0
>
>
>
> On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus 
> wrote:
>
> > Hi Jevgeni,
> >
> > Can I take you off at a slight tangent...
> >
> > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > (logid:0afb959d) DataCenter id = '1' provided is in avoid set,
> > DeploymentPlanner cannot allocate the VM, returning.
> >
> > Have you destroyed your system vms so that new 4.11 system vms have
> > been deployed?
> >
> > It may help us if you can paste all of your management log from today
> > into https://pastebin.com (or similar) to share with us.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com]
> > Sent: 09 February 2018 15:31
> > To: users@cloudstack.apache.org
> > Subject: Re: cloudstack-management fails to start after upgrade 4.10 ->
> > 4.11
> >
> > the same result
> >
> > [root@mtl1-apphst03 management]# virsh list --all
> >  IdName   State
> > 
> >  1 v-1-VM running
> >  2 s-2-VM running
> >
> >
> >
> > On Fri, Feb 9, 2018 at 5:28 PM, Daan Hoogland 
> > wrote:
> >
> > >  so try
> > > # virsh list --all
> > >
> > > On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov
> > >  > > >
> > > wrote:
> > >
> > > > I guess, these are system VMs.
> > > > none of my own created instances can start.
> > > >  IdName   State
> > > > 
> > > >  1 v-1-VM running
> > > >  2 s-2-VM running
> > > >
> > > > virsh start  3> gives error
> > > > error: failed to get domain '8'
> > > > error: Domain not found: no domain with matching name '8'
> > > >
> > > >
> > > > And yes, cloudstack and mysql - everything locally
> > > >
> > > >
> > > >
> > > > On Fri, Feb 9, 2018 at 5:15 PM, Daan Hoogland
> > > > 
> > > > wrote:
> > > >
> > > > > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov <
> > > > j.zolotar...@gmail.com
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > * how to start instance with virsh?
> > > > > >
> > > > > ​ah, usually something like
> > > > > # virsh start 
> > > > > or
> > > > > # virsh start <​number>
> > > > >
> > > > >
> > > > > > * starting in debugger? I would rather not do it :)
> > > > > >
> > > > > ​ok, i expected as much. It will slow our solution process
> > > unfortunately
> > > > > ​
> > > > >
> > > > > ​In the below at the bottom it says you hav

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

[Daan Hoogland]

or better through cloudstack

On Fri, Feb 9, 2018 at 4:59 PM, Daan Hoogland 
wrote:

> Jevgeni,
>
> What Paul means is: Those two VMs are probably the old ones base on the
> 4.10 systemvm template. These need to be upgraded before you can deploy
> anything. The way to do that is to destroy them and let cloudstack recreate
> them. They won't allow you to instantiate anything anyway.
>
> so destroy
> v-1-VM and
> s-2-VM
>
> for instance with virsh
>
> On Fri, Feb 9, 2018 at 4:54 PM, Jevgeni Zolotarjov  > wrote:
>
>> Destroyed VMs? No. Definitely not.
>>
>> At least I can see them all under web console Home->Instances. Can make
>> snapshots even
>>
>> My todays management server log https://www.sendspace.com/file/nxxgg0
>>
>>
>>
>> On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus 
>> wrote:
>>
>> > Hi Jevgeni,
>> >
>> > Can I take you off at a slight tangent...
>> >
>> > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
>> > (logid:0afb959d) DataCenter id = '1' provided is in avoid set,
>> > DeploymentPlanner cannot allocate the VM, returning.
>> >
>> > Have you destroyed your system vms so that new 4.11 system vms have been
>> > deployed?
>> >
>> > It may help us if you can paste all of your management log from today
>> into
>> > https://pastebin.com (or similar) to share with us.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > paul.an...@shapeblue.com
>> > www.shapeblue.com
>> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>> > @shapeblue
>> >
>> >
>> >
>> >
>> > -Original Message-
>> > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com]
>> > Sent: 09 February 2018 15:31
>> > To: users@cloudstack.apache.org
>> > Subject: Re: cloudstack-management fails to start after upgrade 4.10 ->
>> > 4.11
>> >
>> > the same result
>> >
>> > [root@mtl1-apphst03 management]# virsh list --all
>> >  IdName   State
>> > 
>> >  1 v-1-VM running
>> >  2 s-2-VM running
>> >
>> >
>> >
>> > On Fri, Feb 9, 2018 at 5:28 PM, Daan Hoogland 
>> > wrote:
>> >
>> > >  so try
>> > > # virsh list --all
>> > >
>> > > On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov
>> > > > > > >
>> > > wrote:
>> > >
>> > > > I guess, these are system VMs.
>> > > > none of my own created instances can start.
>> > > >  IdName   State
>> > > > 
>> > > >  1 v-1-VM running
>> > > >  2 s-2-VM running
>> > > >
>> > > > virsh start  3> gives error
>> > > > error: failed to get domain '8'
>> > > > error: Domain not found: no domain with matching name '8'
>> > > >
>> > > >
>> > > > And yes, cloudstack and mysql - everything locally
>> > > >
>> > > >
>> > > >
>> > > > On Fri, Feb 9, 2018 at 5:15 PM, Daan Hoogland
>> > > > 
>> > > > wrote:
>> > > >
>> > > > > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov <
>> > > > j.zolotar...@gmail.com
>> > > > > >
>> > > > > wrote:
>> > > > >
>> > > > > > * how to start instance with virsh?
>> > > > > >
>> > > > > ​ah, usually something like
>> > > > > # virsh start 
>> > > > > or
>> > > > > # virsh start <​number>
>> > > > >
>> > > > >
>> > > > > > * starting in debugger? I would rather not do it :)
>> > > > > >
>> > > > > ​ok, i expected as much. It will slow our solution process
>> > > unfortunately
>> > > > > ​
>> > > > >
>> > > > > ​In the below at the bottom it says you have two VMs and both are
>> > > > running.
>

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

[Daan Hoogland]

Jevgeni,

What Paul means is: Those two VMs are probably the old ones base on the
4.10 systemvm template. These need to be upgraded before you can deploy
anything. The way to do that is to destroy them and let cloudstack recreate
them. They won't allow you to instantiate anything anyway.

so destroy
v-1-VM and
s-2-VM

for instance with virsh

On Fri, Feb 9, 2018 at 4:54 PM, Jevgeni Zolotarjov 
wrote:

> Destroyed VMs? No. Definitely not.
>
> At least I can see them all under web console Home->Instances. Can make
> snapshots even
>
> My todays management server log https://www.sendspace.com/file/nxxgg0
>
>
>
> On Fri, Feb 9, 2018 at 5:33 PM, Paul Angus 
> wrote:
>
> > Hi Jevgeni,
> >
> > Can I take you off at a slight tangent...
> >
> > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > (logid:0afb959d) DataCenter id = '1' provided is in avoid set,
> > DeploymentPlanner cannot allocate the VM, returning.
> >
> > Have you destroyed your system vms so that new 4.11 system vms have been
> > deployed?
> >
> > It may help us if you can paste all of your management log from today
> into
> > https://pastebin.com (or similar) to share with us.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com]
> > Sent: 09 February 2018 15:31
> > To: users@cloudstack.apache.org
> > Subject: Re: cloudstack-management fails to start after upgrade 4.10 ->
> > 4.11
> >
> > the same result
> >
> > [root@mtl1-apphst03 management]# virsh list --all
> >  IdName   State
> > 
> >  1 v-1-VM running
> >  2 s-2-VM running
> >
> >
> >
> > On Fri, Feb 9, 2018 at 5:28 PM, Daan Hoogland 
> > wrote:
> >
> > >  so try
> > > # virsh list --all
> > >
> > > On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov
> > >  > > >
> > > wrote:
> > >
> > > > I guess, these are system VMs.
> > > > none of my own created instances can start.
> > > >  IdName   State
> > > > 
> > > >  1 v-1-VM running
> > > >  2 s-2-VM running
> > > >
> > > > virsh start  3> gives error
> > > > error: failed to get domain '8'
> > > > error: Domain not found: no domain with matching name '8'
> > > >
> > > >
> > > > And yes, cloudstack and mysql - everything locally
> > > >
> > > >
> > > >
> > > > On Fri, Feb 9, 2018 at 5:15 PM, Daan Hoogland
> > > > 
> > > > wrote:
> > > >
> > > > > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov <
> > > > j.zolotar...@gmail.com
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > * how to start instance with virsh?
> > > > > >
> > > > > ​ah, usually something like
> > > > > # virsh start 
> > > > > or
> > > > > # virsh start <​number>
> > > > >
> > > > >
> > > > > > * starting in debugger? I would rather not do it :)
> > > > > >
> > > > > ​ok, i expected as much. It will slow our solution process
> > > unfortunately
> > > > > ​
> > > > >
> > > > > ​In the below at the bottom it says you have two VMs and both are
> > > > running.
> > > > > Is that correct?​
> > > > >
> > > > >
> > > > > > * this is the log around GetHostStatsAnswer
> > > > > > 2018-02-09 14:05:30,274 DEBUG [c.c.s.StatsCollector]
> > > > > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95)
> > > > > > HostStatsCollector
> > > is
> > > > > > running...
> > > > > > 2018-02-09 14:05:30,322 DEBUG [c.c.a.t.Request]
> > > > > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) S

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

[Daan Hoogland]

 so try
# virsh list --all

On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov 
wrote:

> I guess, these are system VMs.
> none of my own created instances can start.
>  IdName   State
> 
>  1 v-1-VM running
>  2 s-2-VM running
>
> virsh start  3> gives error
> error: failed to get domain '8'
> error: Domain not found: no domain with matching name '8'
>
>
> And yes, cloudstack and mysql - everything locally
>
>
>
> On Fri, Feb 9, 2018 at 5:15 PM, Daan Hoogland 
> wrote:
>
> > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov <
> j.zolotar...@gmail.com
> > >
> > wrote:
> >
> > > * how to start instance with virsh?
> > >
> > ​ah, usually something like
> > # virsh start 
> > or
> > # virsh start <​number>
> >
> >
> > > * starting in debugger? I would rather not do it :)
> > >
> > ​ok, i expected as much. It will slow our solution process unfortunately
> > ​
> >
> > ​In the below at the bottom it says you have two VMs and both are
> running.
> > Is that correct?​
> >
> >
> > > * this is the log around GetHostStatsAnswer
> > > 2018-02-09 14:05:30,274 DEBUG [c.c.s.StatsCollector]
> > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) HostStatsCollector is
> > > running...
> > > 2018-02-09 14:05:30,322 DEBUG [c.c.a.t.Request]
> > > (StatsCollector-4:ctx-167407f0) (logid:0c470e95) Seq
> > 3-613896924205940798:
> > > Received:  { Ans: , MgmtId: 264216221068220, via: 3(mtl1-apphst03),
> Ver:
> > > v1, Flags: 10, { GetHostStatsAnswer } }
> > > 2018-02-09 14:05:31,388 DEBUG [c.c.s.StatsCollector]
> > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) StorageCollector is
> > > running...
> > > 2018-02-09 14:05:31,396 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b)
> > getCommandHostDelegation:
> > > class com.cloud.agent.api.GetStorageStatsCommand
> > > 2018-02-09 14:05:31,396 DEBUG [c.c.h.XenServerGuru]
> > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are returning the
> > > default host to execute commands because the command is not of Copy
> type.
> > > 2018-02-09 14:05:31,445 DEBUG [c.c.a.t.Request]
> > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq
> > > 4-1941614389350105109:
> > > Received:  { Ans: , MgmtId: 264216221068220, via: 4(s-2-VM), Ver: v1,
> > > Flags: 10, { GetStorageStatsAnswer } }
> > > 2018-02-09 14:05:31,447 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru]
> > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b)
> > getCommandHostDelegation:
> > > class com.cloud.agent.api.GetStorageStatsCommand
> > > 2018-02-09 14:05:31,447 DEBUG [c.c.h.XenServerGuru]
> > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) We are returning the
> > > default host to execute commands because the command is not of Copy
> type.
> > > 2018-02-09 14:05:31,517 DEBUG [c.c.a.t.Request]
> > > (StatsCollector-1:ctx-308796ad) (logid:9e87351b) Seq
> > 3-613896924205940799:
> > > Received:  { Ans: , MgmtId: 264216221068220, via: 3(mtl1-apphst03),
> Ver:
> > > v1, Flags: 10, { GetStorageStatsAnswer } }
> > > 2018-02-09 14:05:34,504 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl]
> > > (AsyncJobMgr-Heartbeat-1:ctx-6955e300) (logid:300ab196) Begin cleanup
> > > expired async-jobs
> > > 2018-02-09 14:05:34,506 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl]
> > > (AsyncJobMgr-Heartbeat-1:ctx-6955e300) (logid:300ab196) End cleanup
> > > expired
> > > async-jobs
> > > 2018-02-09 14:05:35,979 DEBUG [o.a.c.s.SecondaryStorageManagerImpl]
> > > (secstorage-1:ctx-e83be1a3) (logid:60b9de64) Zone 1 is ready to launch
> > > secondary storage VM
> > > 2018-02-09 14:05:36,002 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> > > (consoleproxy-1:ctx-508f06d4) (logid:fea1da44) Zone 1 is ready to
> launch
> > > console proxy
> > > 2018-02-09 14:05:36,697 DEBUG [c.c.a.m.AgentManagerImpl]
> > > (AgentManager-Handler-14:null) (logid:) SeqA 5-273: Processing Seq
> 5-273:
> > > { Cmd , MgmtId: -1, via: 5, Ver: v1, Flags: 11,
> > > [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand"
> > > :{"_proxyVmId":1,"_loadInfo":"{\n
> > > \"connections\": []\n}","wait":0}}] }
> > > 2018-02-09 14:05:36,699 DEBUG 

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

[Daan Hoogland]

14,582 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-528acad3) (logid:a77479b7) Found 0 routers to
> update status.
> 2018-02-09 14:06:14,583 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-528acad3) (logid:a77479b7) Found 0 VPC networks
> to update Redundant State.
> 2018-02-09 14:06:14,584 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-528acad3) (logid:a77479b7) Found 0 networks to
> update RvR status.
> 2018-02-09 14:06:16,892 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-4:null) (logid:) Ping from 3(mtl1-apphst03)
> 2018-02-09 14:06:16,892 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (AgentManager-Handler-4:null) (logid:) Process host VM state report from
> ping process. host: 3
> 2018-02-09 14:06:16,895 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (AgentManager-Handler-4:null) (logid:) Process VM state report. host: 3,
> number of records in report: 2
> 2018-02-09 14:06:16,895 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (AgentManager-Handler-4:null) (logid:) VM state report. host: 3, vm id: 1,
> power state: PowerOn
> 2018-02-09 14:06:16,897 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (AgentManager-Handler-4:null) (logid:) VM power state does not change, skip
> DB writing. vm id: 1
> 2018-02-09 14:06:16,897 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (AgentManager-Handler-4:null) (logid:) VM state report. host: 3, vm id: 2,
> power state: PowerOn
> 2018-02-09 14:06:16,898 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (AgentManager-Handler-4:null) (logid:) VM power state does not change, skip
> DB writing. vm id: 2
> 2018-02-09 14:06:16,899 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (AgentManager-Handler-4:null) (logid:) Done with process of VM state
> report. host: 3
>
>
>
> On Fri, Feb 9, 2018 at 4:47 PM, Daan Hoogland 
> wrote:
>
> > and with cloudstack (and mysql) running locally, right?
> > So my next step would be to stop cloudstack and see if you can start the
> > image with virsh?
> > Cloudstack thinks for some reason the host is not a suitable target. I
> have
> > no clue why that is from your log. You can start cloudstack in a debugger
> > but given you are asking on users@, i don't think you are familiar with
> > that kind of work are, you?
> > You might also want to look in the management (and agent) log to see if
> you
> > can find anything about the capacity reported. Look for
> GetHostStatsAnswer.
> >
> > On Fri, Feb 9, 2018 at 3:11 PM, Jevgeni Zolotarjov <
> j.zolotar...@gmail.com
> > >
> > wrote:
> >
> > > Yes, its KVM
> > >
> > > On Fri, Feb 9, 2018 at 4:06 PM, Daan Hoogland  >
> > > wrote:
> > >
> > > > I am at a loss but really would like to help you.
> > > > is it a KVM with the management server running locally?
> > > >
> > > > On Fri, Feb 9, 2018 at 3:02 PM, Jevgeni Zolotarjov <
> > > j.zolotar...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > My Host is only 1 machine atm:
> > > > > Dell PowerEdge610
> > > > > OS: CentOS7 (latest)
> > > > > CPU: 2x12 cores (24 cores in total)
> > > > > RAM: 192 GB
> > > > > Storage: 3+ TB
> > >
> >
> >
> > --
> > Daan
> >
>



-- 
Daan

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

[Daan Hoogland]

and with cloudstack (and mysql) running locally, right?
So my next step would be to stop cloudstack and see if you can start the
image with virsh?
Cloudstack thinks for some reason the host is not a suitable target. I have
no clue why that is from your log. You can start cloudstack in a debugger
but given you are asking on users@, i don't think you are familiar with
that kind of work are, you?
You might also want to look in the management (and agent) log to see if you
can find anything about the capacity reported. Look for GetHostStatsAnswer.

On Fri, Feb 9, 2018 at 3:11 PM, Jevgeni Zolotarjov 
wrote:

> Yes, its KVM
>
> On Fri, Feb 9, 2018 at 4:06 PM, Daan Hoogland 
> wrote:
>
> > I am at a loss but really would like to help you.
> > is it a KVM with the management server running locally?
> >
> > On Fri, Feb 9, 2018 at 3:02 PM, Jevgeni Zolotarjov <
> j.zolotar...@gmail.com
> > >
> > wrote:
> >
> > > My Host is only 1 machine atm:
> > > Dell PowerEdge610
> > > OS: CentOS7 (latest)
> > > CPU: 2x12 cores (24 cores in total)
> > > RAM: 192 GB
> > > Storage: 3+ TB
>


-- 
Daan

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

[Daan Hoogland]

I am at a loss but really would like to help you.
is it a KVM with the management server running locally?

On Fri, Feb 9, 2018 at 3:02 PM, Jevgeni Zolotarjov 
wrote:

> My Host is only 1 machine atm:
> Dell PowerEdge610
> OS: CentOS7 (latest)
> CPU: 2x12 cores (24 cores in total)
> RAM: 192 GB
> Storage: 3+ TB
>
> I was running cloudstack-4.10 without problems since it was released
>
> Your help is appreciated
>
> On Fri, Feb 9, 2018 at 3:57 PM, Daan Hoogland 
> wrote:
>
> > Jevgeni,
> >
> > can you describe your environment in more detail? the host[3] that is in
> > the avoid list, is it the host that VM was/is originally running on? Is
> > anything running on it atm? what is it's distribution and version?
> etc
> >
> > On Fri, Feb 9, 2018 at 2:44 PM, Jevgeni Zolotarjov <
> j.zolotar...@gmail.com
> > >
> > wrote:
> >
> > > To follow up:
> > > this is what I have in log:
> > > 2018-02-09 13:31:48,836 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > > (logid:0afb959d) DeploymentPlanner allocation algorithm: null
> > > 2018-02-09 13:31:48,836 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > > (logid:0afb959d) Trying to allocate a host and storage pools from dc:1,
> > > pod:1,cluster:null, requested cpu: 500, requested ram: 2147483648
> > > 2018-02-09 13:31:48,836 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > > (logid:0afb959d) Is ROOT volume READY (pool already allocated)?: No
> > > 2018-02-09 13:31:48,840 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > > (logid:0afb959d) Deploy avoids pods: [], clusters: [], hosts: [3]
> > > 2018-02-09 13:31:48,840 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > > (logid:0afb959d) DataCenter id = '1' provided is in avoid set,
> > > DeploymentPlanner cannot allocate the VM, returning.
> > > 2018-02-09 13:31:48,843 DEBUG [c.c.c.CapacityManagerImpl]
> > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > > (logid:0afb959d) VM state transitted from :Starting to Stopped with
> > event:
> > > OperationFailedvm's original host id: 3 new host id: null host id
> before
> > > state transition: 3
> > > 2018-02-09 13:31:48,847 DEBUG [c.c.c.CapacityManagerImpl]
> > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > > (logid:0afb959d) Hosts's actual total CPU: 70224 and CPU after applying
> > > overprovisioning: 70224
> > > 2018-02-09 13:31:48,847 DEBUG [c.c.c.CapacityManagerImpl]
> > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > > (logid:0afb959d) Hosts's actual total RAM: 205071147008 and RAM after
> > > applying overprovisioning: 205071155200
> > > 2018-02-09 13:31:48,847 DEBUG [c.c.c.CapacityManagerImpl]
> > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > > (logid:0afb959d) release cpu from host: 3, old used: 1500,reserved:
> > 26100,
> > > actual total: 70224, total with overprovisioning: 70224; new used:
> > > 1000,reserved:26100; movedfromreserved: false,moveToReserveredfalse
> > > 2018-02-09 13:31:48,847 DEBUG [c.c.c.CapacityManagerImpl]
> > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > > (logid:0afb959d) release mem from host: 3, old used:
> 3758096384,reserved:
> > > 81335943168, total: 205071155200; new used:
> > > 1610612736,reserved:81335943168; movedfromreserved:
> > > false,moveToReserveredfalse
> > > 2018-02-09 13:31:48,854 ERROR [c.c.v.VmWorkJobHandlerProxy]
> > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > > (logid:0afb959d) Invocation exception, caused by:
> > > com.cloud.exception.InsufficientServerCapacityException: Unable to
> > create
> > > a
> > > deployment for VM[User|i-2-11-VM]Scope=interface
> > com.cloud.dc.DataCenter;
> > > id=1
> > > 2018-02-09 13:31:48,854 INFO  [c.c.v.VmWorkJobHandlerProxy]
> > > (Work-Job-Executor-7:ctx-a92d467b job-893/job-896 ctx-9ffd0cf1)
> > > (logid:0afb959d) Rethrow exception
> > > com.cloud.exception.InsufficientServerCapacityException: Unable to
> > create
> > > a
> > > dep

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

[Daan Hoogland]

ement.
> EventUtils$EventInterceptor.invoke(EventUtils.java:107)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
> ReflectiveMethodInvocation.java:174)
> at
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:
> 51)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
> ReflectiveMethodInvocation.java:174)
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(
> ExposeInvocationInterceptor.java:92)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
> ReflectiveMethodInvocation.java:185)
> at
> org.springframework.aop.framework.JdkDynamicAopProxy.
> invoke(JdkDynamicAopProxy.java:212)
> at com.sun.proxy.$Proxy169.startVirtualMachine(Unknown Source)
> at
> org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin.execute(
> StartVMCmdByAdmin.java:51)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
> at
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.
> runInContext(AsyncJobManagerImpl.java:581)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(
> ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(
> DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.
> callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.
> runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(
> ManagedContextRunnable.java:46)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(
> AsyncJobManagerImpl.java:529)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable
> to create a deployment for VM[User|i-2-11-VM]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(
> VirtualMachineManagerImpl.java:1072)
> at
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(
> VirtualMachineManagerImpl.java:4927)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ... 18 more
>
>
> On Fri, Feb 9, 2018 at 3:05 PM, Jevgeni Zolotarjov  >
> wrote:
>
> > OK, I pushed through and got management server running.
> > The steps I made:
> > * recovered DB from backup
> > * downgraded everything 4.11->4.10
> > * installed systemvmtemplates
> > * upgraded 4.10 -> 4.11
> >
> > THEN!!! To make it run I had to go through all manual DB altering.
> > Meaning, there is definitely something wrong in shapeblue packages. I
> could
> > not locate the necessary DB scripts in the package. So I fetched an
> update
> > from github repo.
> >
> > Even then it failed to start and I had to do some more DB altering from
> > file https://github.com/apache/cloudstack/blob/4.11/
> > engine/schema/resources/META-INF/db/schema-4930to41000.sql
> > Namely:
> > ALTER TABLE `cloud`.`sslcerts` ADD COLUMN `name` varchar(255) NULL
> default
> > NULL COMMENT 'Name of the Certificate';
> > ALTER TABLE `cloud`.`network_offerings` ADD COLUMN `service_package_id`
> > varchar(255) NULL default NULL COMMENT 'Netscaler ControlCenter Service
> > Package';
> >
> > OK. Here I am.
> >
> > BUT! Not all my VMs are starting. On attempt to start them, manually, it
> > says
> >
> > "Unable to start a VM due to insufficient capacity"
> >
> > OK, I am having VMs taking more cores, than actual physical number of
> > cores.
> > VM cores - 35,
> > physical cores - 24
> >
> > It was not the problem with previous version 4.10 - and it was correct.
> I
> > want to decide myself if I want to allow cpu overprovisioning.
> >
> > I consider this a critical bug.
> >
> > On Fri, Feb 9, 2018 at 11:51 AM, Jevgeni Zolotarjov <
> > j.zo

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

[Daan Hoogland]

tionSet$2.with(DefaultModuleDefinitionSet.java:122)
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.
> withModule(DefaultModuleDefinitionSet.java:245)
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.
> withModule(DefaultModuleDefinitionSet.java:250)
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.
> withModule(DefaultModuleDefinitionSet.java:233)
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.
> loadContexts(DefaultModuleDefinitionSet.java:117)
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.
> load(DefaultModuleDefinitionSet.java:79)
> at
> org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.
> loadModules(ModuleBasedContextFactory.java:37)
> at
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(
> CloudStackSpringContext.java:71)
> at
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.
> (CloudStackSpringContext.java:58)
> at
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.
> (CloudStackSpringContext.java:62)
> at
> org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListene
> r.contextInitialized(CloudStackContextLoaderListener.java:52)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(
> ContextHandler.java:890)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(
> ServletContextHandler.java:532)
> at
> org.eclipse.jetty.server.handler.ContextHandler.
> startContext(ContextHandler.java:853)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(
> ServletContextHandler.java:344)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(
> WebAppContext.java:1515)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(
> WebAppContext.java:1477)
> at
> org.eclipse.jetty.server.handler.ContextHandler.
> doStart(ContextHandler.java:785)
>
>
>
> On Fri, Feb 9, 2018 at 11:42 AM, Daan Hoogland 
> wrote:
>
> > before you continue Jevgeni,
> >
> > Do you have a good backup and is no-one able to access this installation
> > with UI or API, when you roll back?
> >
> > On Fri, Feb 9, 2018 at 10:15 AM, Ernie Janse van Rensburg <
> > ernie.jvrensb...@shapeblue.com> wrote:
> >
> > > engine/schema/resources/META-INF/db/schema-41000to41100.sql:
> > >
> > > 
> > > From: Jevgeni Zolotarjov 
> > > Sent: Friday, February 9, 2018 10:59:27 AM
> > > To: users@cloudstack.apache.org
> > > Subject: Re: cloudstack-management fails to start after upgrade 4.10 ->
> > > 4.11
> > >
> > > I dropped the column. But then another error like this appeared
> > >
> > > Please advise, where are the DB update script located? so I can
> manually
> > > inspect that.
> > >
> > > On Fri, Feb 9, 2018 at 10:29 AM, Ernie Janse van Rensburg <
> > > ernie.jvrensb...@shapeblue.com> wrote:
> > >
> > > > Hi Jevgeni
> > > >
> > > >
> > > > It looks like there was a database error during the upgrade process.
> > > >
> > > >
> > > > A SQL script that is trying to add a column 'for_vpc' to the TABLE
> > > > 'cloud.network_offerings' but the column already exists, for some
> > reason,
> > > > so it fails because mysql does not allow 2 columns with the same name
> > in
> > > > the same table.
> > > >
> > > >
> > > > The column might have already existed from a previous upgrade or from
> > > > running the 4.11 upgrade more than once, and perhaps the SQL script
> is
> > > not
> > > > idempotent.
> > > >
> > > >
> > > > I suggest to manually drop the column on the table and run the 4.11
> > > > upgrade process again.
> > > >
> > > >
> > > > Regards
> > > >
> > > >
> > > > Ernie
> > > >
> > > > 
> > > > From: Jevgeni Zolotarjov 
> > > > Sent: Friday, February 9, 2018 10:10:59 AM
> > > > To: users@cloudstack.apache.org
> > > > Subject: cloudstack-management fails to start after upgrade 4.10 ->
> > 4.11
> > > >
> &

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

[Daan Hoogland]

before you continue Jevgeni,

Do you have a good backup and is no-one able to access this installation
with UI or API, when you roll back?

On Fri, Feb 9, 2018 at 10:15 AM, Ernie Janse van Rensburg <
ernie.jvrensb...@shapeblue.com> wrote:

> engine/schema/resources/META-INF/db/schema-41000to41100.sql:
>
> 
> From: Jevgeni Zolotarjov 
> Sent: Friday, February 9, 2018 10:59:27 AM
> To: users@cloudstack.apache.org
> Subject: Re: cloudstack-management fails to start after upgrade 4.10 ->
> 4.11
>
> I dropped the column. But then another error like this appeared
>
> Please advise, where are the DB update script located? so I can manually
> inspect that.
>
> On Fri, Feb 9, 2018 at 10:29 AM, Ernie Janse van Rensburg <
> ernie.jvrensb...@shapeblue.com> wrote:
>
> > Hi Jevgeni
> >
> >
> > It looks like there was a database error during the upgrade process.
> >
> >
> > A SQL script that is trying to add a column 'for_vpc' to the TABLE
> > 'cloud.network_offerings' but the column already exists, for some reason,
> > so it fails because mysql does not allow 2 columns with the same name in
> > the same table.
> >
> >
> > The column might have already existed from a previous upgrade or from
> > running the 4.11 upgrade more than once, and perhaps the SQL script is
> not
> > idempotent.
> >
> >
> > I suggest to manually drop the column on the table and run the 4.11
> > upgrade process again.
> >
> >
> > Regards
> >
> >
> > Ernie
> >
> > 
> > From: Jevgeni Zolotarjov 
> > Sent: Friday, February 9, 2018 10:10:59 AM
> > To: users@cloudstack.apache.org
> > Subject: cloudstack-management fails to start after upgrade 4.10 -> 4.11
> >
> > cloudstack-management fails to start after upgrade from 4.10 to 4.11
> >
> > management-server.log:
> > 2018-02-09 07:49:50,842 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null)
> > (logid:) Running upgrade Upgrade41000to41100 to upgrade from
> > 4.10.0.0-4.11.0.0 to 4.11.0.0
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- Licensed to the Apache Software Foundation (ASF) under one
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- or more contributor license agreements.  See the NOTICE file
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- distributed with this work for additional information
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- regarding copyright ownership.  The ASF licenses this file
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- to you under the Apache License, Version 2.0 (the
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- "License"); you may not use this file except in compliance
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- with the License.  You may obtain a copy of the License at
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > --
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > --   http://www.apache.org/licenses/LICENSE-2.0
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > --
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- Unless required by applicable law or agreed to in writing,
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- software distributed under the License is distributed on an
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- KIND, either express or implied.  See the License for the
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- specific language governing permissions and limitations
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- under the License.
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > --;
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- Schema upgrade from 4.10.0.0 to 4.11.0.0
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > --;
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- Add For VPC flag
> > 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc INT(1) NOT NULL
> > DEFAULT 0
> > 2018-02-09 07:49:50,847 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > Error executing: ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc
> > INT(1) NOT NULL DEFAULT 0
> > 2018-02-09 07:49:50,848 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

[Daan Hoogland]

Jevgeni,

It looks like the db upgrade went wrong. You'll have to restore a backup,
or be very savvy about what you do next.
For some reason the new column, 'for_vpc' was already defined. The
management server saw that the db was version 4.10 and self is 4.11. It
then starts the run the required upgrade scripts. In this case just one
set, 4.10.0.0 -> 4.11.0.0.

You can restore the db and retrieve the db scripts from the jar or from
github.
The you can either
1. check what needs to be done for an upgrade and make sure there are no
conflicts and restat themanagement server or
2. just run the required steps by hand including the entry in the version
table.

I have no doubt you have further question if you are new to this, feel free
regards,

On Fri, Feb 9, 2018 at 9:10 AM, Jevgeni Zolotarjov 
wrote:

> cloudstack-management fails to start after upgrade from 4.10 to 4.11
>
> management-server.log:
> 2018-02-09 07:49:50,842 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null)
> (logid:) Running upgrade Upgrade41000to41100 to upgrade from
> 4.10.0.0-4.11.0.0 to 4.11.0.0
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- Licensed to the Apache Software Foundation (ASF) under one
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- or more contributor license agreements.  See the NOTICE file
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- distributed with this work for additional information
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- regarding copyright ownership.  The ASF licenses this file
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- to you under the Apache License, Version 2.0 (the
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- "License"); you may not use this file except in compliance
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- with the License.  You may obtain a copy of the License at
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> --
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> --   http://www.apache.org/licenses/LICENSE-2.0
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> --
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- Unless required by applicable law or agreed to in writing,
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- software distributed under the License is distributed on an
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- KIND, either express or implied.  See the License for the
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- specific language governing permissions and limitations
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- under the License.
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> --;
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- Schema upgrade from 4.10.0.0 to 4.11.0.0
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> --;
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> -- Add For VPC flag
> 2018-02-09 07:49:50,846 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc INT(1) NOT NULL
> DEFAULT 0
> 2018-02-09 07:49:50,847 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:)
> Error executing: ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc
> INT(1) NOT NULL DEFAULT 0
> 2018-02-09 07:49:50,848 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:)
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate
> column
> name 'for_vpc'
> 2018-02-09 07:49:50,849 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null)
> (logid:) Unable to execute upgrade script
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate
> column
> name 'for_vpc'
> at com.cloud.utils.db.ScriptRunner.runScript(
> ScriptRunner.java:185)
> at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:87)
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.runScript(
> DatabaseUpgradeChecker.java:459)
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(
> DatabaseUpgradeChecker.java:557)
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.check(
> DatabaseUpgradeChecker.java:641)
> at
> org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.
> checkIntegrity(CloudStackExtendedLifeCycle.java:65)
> at
> org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(
> CloudStackExtendedLifeCycle.java:55)
> at
> org.springframework.con

Re: SystemVM not starting after updating console SSL cert

[Daan Hoogland]

Omit,

On Wed, Feb 7, 2018 at 10:48 AM, Amit Dalia  wrote:

> Hi Dan,
>




>
> When you say this is an old query, do you mean it is an old version of
> CloudStack?
>
> >> Nope. I mean this might be an old question already discussed in the
> group.
>
​ah, well it resambles a lot but might not be the same, not much to go on
here.
​


>
>
> Which version is it?
>
> >> 3.0.2.20120506223416
>
> Note: This is old deployment.
>
​Yes it is, it is also not a apache version, It looks to be a former
citrix, now accelerite version. I'd contact their support site.
​


>
>
> During your install of the new certificates, did you destroy the systemvms
> and let cloudstack recreate them?
>
> >> Nope. But now I deleted 1 console VM and it is not recreated yet.
> Storage vms are in running state.
>
>
> And can you get to the hosts that run the console proxy to do an
> investigation there, as to why the consoleproxy stops again?
>
> >> How can I get there if the machine is not running.
>
​not to the machine itself but to the hypervisor it runs on, it might have
logs with usefull infromation.
​


>
>
> Regards,
>
>
> Amit
>
> 
> From: Daan Hoogland 
> Sent: Wednesday, February 7, 2018 2:02:29 PM
> To: users@cloudstack.apache.org
> Subject: Re: SystemVM not starting after updating console SSL cert
>
> Amit, couple of questions as I am not sure what you are asking for.
>
> When you say this is an old query, do you mean it is an old version of
> CloudStack?
> Which version is it?
> During your install of the new certificates, did you destroy the systemvms
> and let cloudstack recreate them?
> And can you get to the hosts that runs the console proxy to do
> investigation there, as to why the consoleproxy stops again?
>
> regards,
>
> On Wed, Feb 7, 2018 at 7:01 AM, Amit Dalia  wrote:
>
> > Hi All,
> >
> >
> > I'm new to cloudstack and our production environment is having cloudstack
> > as an in-house cloud. The first task was given to me to update expiring
> > console SSL certificate.
> >
> >
> > I went through all the wiki pages on how to upload cert, private key,
> root
> > CA & intermediate CA. (Note: before uploading the same I had taken old
> > keystore table backup.)
> >
> >
> > Restarted cloud management service.
> >
> > But now console system VM is in the stopped state and when I try to start
> > then it goes to running state and then back to the stopped state.
> >
> > I had done grep on log file for this VM and same is attached to the
> email.
> >
> >
> > I know this might be an old query, but it will be helpful if someone
> guide
> > me further or point me to old archive.
> >
> >
> > Thanks & Regards,
> >
> >
> > Amit Dalia
> >
>
>
>
> --
> Daan
>



-- 
Daan

Re: SystemVM not starting after updating console SSL cert

[Daan Hoogland]

Amit, couple of questions as I am not sure what you are asking for.

When you say this is an old query, do you mean it is an old version of
CloudStack?
Which version is it?
During your install of the new certificates, did you destroy the systemvms
and let cloudstack recreate them?
And can you get to the hosts that runs the console proxy to do
investigation there, as to why the consoleproxy stops again?

regards,

On Wed, Feb 7, 2018 at 7:01 AM, Amit Dalia  wrote:

> Hi All,
>
>
> I'm new to cloudstack and our production environment is having cloudstack
> as an in-house cloud. The first task was given to me to update expiring
> console SSL certificate.
>
>
> I went through all the wiki pages on how to upload cert, private key, root
> CA & intermediate CA. (Note: before uploading the same I had taken old
> keystore table backup.)
>
>
> Restarted cloud management service.
>
> But now console system VM is in the stopped state and when I try to start
> then it goes to running state and then back to the stopped state.
>
> I had done grep on log file for this VM and same is attached to the email.
>
>
> I know this might be an old query, but it will be helpful if someone guide
> me further or point me to old archive.
>
>
> Thanks & Regards,
>
>
> Amit Dalia
>



-- 
Daan

Re: Apache project page updates needed.

[Daan Hoogland]

I think this is PMC work, not sure though, i haven't been maintaining this
a lot. any one has wisdom on this?

On Fri, Feb 2, 2018 at 5:28 PM, Ron Wheeler 
wrote:

> http://cloudstack.apache.org/ list upcoming conferences in 2016 and 2017.
> Nothing planned for 2018.
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwhee...@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>


-- 
Daan

Re: [fosdem] Anybody going to Fosdem this weekend?

[Daan Hoogland]

what he said !!!

On Thu, Feb 1, 2018 at 11:58 PM, Rohit Yadav 
wrote:

> Hi all,
>
> I will be at Fosdem in Brussels this weekend, and I know Daan is going to
> be there too - if you're going it would be lovely to meet you and discuss
> CloudStack among other things, tweet me @rhtyd.
>
> Cheers.
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>


-- 
Daan

Re: [VOTE] Apache Cloudstack 4.11.0.0 LTS [RC2]

[Daan Hoogland]

did package verification with all three sig files and including my own
monkeying and Boris testing;
+1 (binding)

On Fri, Jan 26, 2018 at 1:19 PM, Rohit Yadav  wrote:

> Hi All,
>
> I've created a 4.11.0.0 release (RC2), with the following artifacts up for
> testing and a vote:
>
> Git Branch and Commit SH:
> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=
> shortlog;h=refs/heads/4.11.0.0-RC20180126T1313
> Commit: 5dada1f7ed5fb6a8ee261c763f744583e586f8bf
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.11.0.0/
>
> PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open till end of next week, 2nd Feb 2018.
>
> For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Additional information:
>
> For users' convenience, I've built packages from
> 5dada1f7ed5fb6a8ee261c763f744583e586f8bf and published RC2 repository
> here:
> http://cloudstack.apt-get.eu/testing/4.11-rc2
> (the packages are being built and will be available shortly)
>
> The release notes are still work-in-progress, but the systemvmtemplate
> upgrade section has been updated. You may refer the following for
> systemvmtemplate upgrade testing:
> http://docs.cloudstack.apache.org/projects/cloudstack-
> release-notes/en/latest/index.html
>
> 4.11 systemvmtemplates are available from here:
> https://download.cloudstack.org/systemvm/4.11/
>
> Regards,
> Rohit Yadav
>



-- 
Daan

Re: Shape Blue Container Service

[Daan Hoogland]

Ghaith,

There is a 4.10 version in the code but not as a packaged installable.
If you’re comfortable with source installations have a look at 
https://github.com/shapeblue/ccs/tree/on-top-of-pr-2071-for-4.10
A release for 4.10 is planned but we do not have a date yet.

Hope that satisfies your query,

On 17/01/2018, 09:46, "Ghaith Bannoura"  wrote:

Hello All,

I'm trying to install shape blue container service , but I already have ACS 
version 4.9 what I read from the document that its supported on ACS  Version 
4.6 ,

is it compatible on version 4.9 or 4.10 since I urgently need to implement 
it on my cloud ?



Best Regards,

Ghaith Bannoura
Senior System Administrator
MCT, MCSE (Messaging, Server Infrastructure)
MCSA (Windows Server 2008, 2012), MCP






daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: [DISCUSS] Freezing master for 4.11

[Daan Hoogland]

please discuss on the VOTE thread Kristian. Give your -1 with explanation
there.

On Tue, Jan 16, 2018 at 11:40 AM, Kristian Liivak  wrote:

> Daan,
>
> For us and i guess for many others public cloud and vps providers its very
> big hole.
> Imagine that 10-20 chinese guys have made fraud orders and 10-20 vps are
> provisioned.
> We dealing with fradulent orders daily basis.
> Some time later abusers will get catch in the act and vpses will be
> terminated.
> If your customer increase is considerable, most probably one or more ips
> will be given to new customers during same day.
> Newly created instances get then abusers keys and root passwords.
> If new instance uses only keys, root password will be never changed.
> Abusers need just log in with them old passwords and bitcoin mining or
> spamming will be started again.
> Some of smarter customers are able to connect dots and serviceprovider
> reputation will be damaged seriously.
>
>
> Lugupidamisega / Regards
>
> Kristian Liivak
>
> Tegevjuht / Executive director
>
> WaveCom As
> Endla 16, 10142 Tallinn
> Estonia
> Tel: +3726850001
> Gsm: +37256850001
> E-mail: k...@wavecom.ee
> Skype: kristian.liivak
> http://www.wavecom.ee
> http://www.facebook.com/wavecom.ee
>
> - Original Message -
> From: "Daan Hoogland" 
> To: "users" 
> Cc: "dev" 
> Sent: Monday, January 15, 2018 1:49:04 PM
> Subject: Re: [DISCUSS] Freezing master for 4.11
>
> Kristian,
>
>
>
> On Mon, Jan 15, 2018 at 11:49 AM, Kristian Liivak  wrote:
> >>
> > ...
>
>
>
> As for this one:
>
> > Also there is major security hole. When instance is destroyd and expunged
> >> > and new instance is created with old IP all old data is unaffected in
> VR
> >> > New instance will get then old root password and  ssh key if they were
> >> > present in VR
> >>
> > I don't see how this is a security issue. The user won't get in and
> update the key and password to get in. No harm done or am I overlooking
> something?
>
>
> --
> Daan
>



-- 
Daan

Re: [DISCUSS] Freezing master for 4.11

[Daan Hoogland]

​Kristian,

​

On Mon, Jan 15, 2018 at 11:49 AM, Kristian Liivak  wrote:
>>
> ​...
​


​As for this one:​

> Also there is major security hole. When instance is destroyd and expunged
>> > and new instance is created with old IP all old data is unaffected in VR
>> > New instance will get then old root password and  ssh key if they were
>> > present in VR
>>
> ​I don't see how this is a security issue​. The user won't get in and
update the key and password to get in. No harm done or am I overlooking
something?


-- 
Daan

Re: [DISCUSS] Freezing master for 4.11

[Daan Hoogland]

I suggest you discuss it on the vote thread for RC1 Kristian.

On Mon, Jan 15, 2018 at 12:47 PM, Kristian Liivak  wrote:

>
> This fix is only for smaller part of password management..
> Is´t possible that someone have look VR password distribution with
> instance creation ?


-- 
Daan

Re: [DISCUSS] Freezing master for 4.11

[Daan Hoogland]

Yes, I know. I made that that's why i asked. This fix isn't in 4.10 but is
in 4.11.

On Mon, Jan 15, 2018 at 12:37 PM, Kristian Liivak  wrote:

>
> We made lot testing but did´nt had time to dig code this time.
> There was similar VR password management related and fixed issue
> https://issues.apache.org/jira/browse/CLOUDSTACK-10113
>
>
>
> Lugupidamisega / Regards
>
> Kristian Liivak
>
> CTO
> WaveCom As
> Endla 16, 10142 Tallinn
> Estonia
> Tel: +3726850001
> Gsm: +37256850001
> E-mail: k...@wavecom.ee
> Skype: kristian.liivak
> http://www.wavecom.ee
> http://www.facebook.com/wavecom.ee
>
> - Original Message -
> From: "Daan Hoogland" 
> To: "users" 
> Cc: "dev" 
> Sent: Monday, January 15, 2018 1:22:23 PM
> Subject: Re: [DISCUSS] Freezing master for 4.11
>
> kristian,
>
> these sound like serious regressions. Do you have a fix or did you analyse
> the code yet?
>
> On Mon, Jan 15, 2018 at 11:49 AM, Kristian Liivak  wrote:
>
> > Hello,
> >
> > I have created issue in jira 2 month ago.
> > https://issues.apache.org/jira/browse/CLOUDSTACK-10141
> >
> > In version 4.10 VR password and ssh key distribution don´t work on
> > instance creation.
> > When instance is allreay excisting reset function is operational.
> >
> > Also there is major security hole. When instance is destroyd and expunged
> > and new instance is created with old IP all old data is unaffected in VR
> > New instance will get then old root password and  ssh key if they were
> > present in VR
> >
> > In my knowledege cloudstack older versions are not affected.
> >
> > Lugupidamisega / Regards
> >
> > Kristian Liivak
> >
> > CTO
> >
> > WaveCom As
> > Endla 16, 10142 Tallinn
> > Estonia
> > Tel: +3726850001
> > Gsm: +37256850001
> > E-mail: k...@wavecom.ee
> > Skype: kristian.liivak
> > http://www.wavecom.ee
> > http://www.facebook.com/wavecom.ee
> >
> > - Original Message -
> > From: "Rohit Yadav" 
> > To: d...@cloudstack.apache.org, "users" 
> > Sent: Sunday, January 14, 2018 8:41:15 PM
> > Subject: Re: [DISCUSS] Freezing master for 4.11
> >
> > All,
> >
> >
> > To give you update, all feature PRs have been reviewed, tested and merged
> > towards the 4.11.0.0. I'll engage with Mike and others for any post-merge
> > regressions (smoketest to be kicked shortly).
> >
> >
> > I see an outstanding PR that may be a critical/blocker PR, please advise
> > and also review:
> >
> > https://github.com/apache/cloudstack/pull/2402
> >
> >
> > If anyone has any blocker to report, please do so. Thanks.
> >
> >
> > I'll cut RC1 as planned by EOD today (Mon/15 Jan 2018).
> >
> >
> > - Rohit
> >
> > <https://cloudstack.apache.org>
> >
> >
> >
> > 
> > From: Tutkowski, Mike 
> > Sent: Saturday, January 13, 2018 3:23:40 AM
> > To: d...@cloudstack.apache.org
> > Subject: Re: [DISCUSS] Freezing master for 4.11
> >
> > I’m investigating these now. I have found and fixed two of them so far.
> >
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> > > On Jan 12, 2018, at 2:49 PM, Rohit Yadav 
> > wrote:
> > >
> > > Thanks Rafael and Daan.
> > >
> > >
> > >> From: Rafael Weingärtner 
> > >>
> > >> I believe there is no problem in merging Wido’s and Mike’s PRs, they
> > have
> > >> been extensively discussed and improved (specially Mike’s one).
> > >
> > > Thanks, Mike's PR has several regression smoketest failures and can be
> > accepted only when those failures are fixed.
> > >
> > > We'll cut 4.11 branch start rc1 on Monday that would be a hard freeze.
> > If Mike wants, he can help fix them over the weekend, I can help run
> > smoketests.
> > >
> > >> Having said that; I would be ok with it (no need to revert it), but we
> > need
> > >> to be more careful with these things. If one wants to merge something,
> > >> there is no harm in waiting and calling for reviewers via Github,
> > Slack, or
> > >> even email them directly.
> > >
> > > Additional review was requested, but mea culpa - thanks for your
> > support, noted.

Re: [DISCUSS] Freezing master for 4.11

[Daan Hoogland]

R are all localized to a xenserver-swift
> >> file, that is not tested by Travis or Trillian, since no new regression
> >> failures were seen I accepted and merge it on that discretion. The PR
> was
> >> originally on the 4.11 milestone, however, due to it lacking a JIRA id
> and
> >> no response from the author it was only recently removed from the
> milestone.
> >>
> >>
> >> Please advise if I need to revert this, or we can review/lgtm it
> >> post-merge? I'll also ping on the above PR.
> >>
> >>
> >> - Rohit
> >>
> >> <https://cloudstack.apache.org>
> > Apache CloudStack: Open Source Cloud Computing<https://cloudstack.
> apache.org/>
> > cloudstack.apache.org
> > CloudStack is open source cloud computing software for creating,
> managing, and deploying infrastructure cloud services
> >
> >
> >
> >>
> >>
> >>
> >> 
> >> From: Wido den Hollander 
> >> Sent: Thursday, January 11, 2018 9:17:26 PM
> >> To: d...@cloudstack.apache.org
> >> Subject: Re: [DISCUSS] Freezing master for 4.11
> >>
> >>
> >>
> >>> On 01/10/2018 07:26 PM, Daan Hoogland wrote:
> >>> I hope we understand each other correctly: No-one running an earlier
> >>> version then 4.11 should miss out on any functionality they are using
> >> now.
> >>>
> >>> So if you use ipv6 and multiple cidrs now it must continue to work with
> >> no
> >>> loss of functionality. see my question below.
> >>>
> >>> On Wed, Jan 10, 2018 at 7:06 PM, Ivan Kudryavtsev <
> >> kudryavtsev...@bw-sw.com>
> >>> wrote:
> >>>
> >>>> Daan, yes this sounds reasonable, I suppose who would like to fix,
> could
> >>>> do custom build for himself...
> >>>>
> >>>> But still it should be aknowledged somehow, if you use several cidrs
> for
> >>>> network, don't use v6, or don't upgrade to 4.11 because things will
> stop
> >>>> running well.
> >>>>
> >>> Does this mean that several cidrs in ipv6 works in 4.9 and not in 4.11?
> >>>
> >>
> >> No, it doesn't. IPv6 was introduced in 4.10 and this broke in 4.10.
> >>
> >> You can't run with 4.10 with multiple IPv4 CIDRs as well when you have
> >> IPv6 enabled.
> >>
> >> So this is broken in 4.10 and 4.11 in that case.
> >>
> >> Wido
> >>
> >>>
> >>> if yes; it is a blocker
> >>>
> >>> if no; you might as well upgrade for other features as it doesn't work
> >> now
> >>> either.
> >>>
> >>
> >> rohit.ya...@shapeblue.com
> >> www.shapeblue.com<http://www.shapeblue.com>
> > [http://www.shapeblue.com/wp-content/uploads/2017/06/logo.png]<
> http://www.shapeblue.com/>
> >
> > Shapeblue - The CloudStack Company<http://www.shapeblue.com/>
> > www.shapeblue.com<http://www.shapeblue.com>
> > Rapid deployment framework for Apache CloudStack IaaS Clouds. CSForge is
> a framework developed by ShapeBlue to deliver the rapid deployment of a
> standardised ...
> >
> >
> >
> >> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> >> @shapeblue
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Rafael Weingärtner
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
>



-- 
Daan

Re: [Discuss] Management cluster / Zookeeper holding locks

[Daan Hoogland]

Are you proposing to add zookeeper as an optional requirement, Marc-Aurèle?
or just curator? and what is the decision mech of including it or not?

On Mon, Dec 18, 2017 at 9:33 AM, Marc-Aurèle Brothier 
wrote:

> Hi everyone,
>
> I was wondering how many of you are running CloudStack with a cluster of
> management servers. I would think most of you, but it would be nice to hear
> everyone voices. And do you get hosts going over their capacity limits?
>
> We discovered that during the VM allocation, if you get a lot of parallel
> requests to create new VMs, most notably with large profiles, the capacity
> increase is done too far after the host capacity checks and results in
> hosts going over their capacity limits. To detail the steps: the deployment
> planner checks for cluster/host capacity and pick up one deployment plan
> (zone, cluster, host). The plan is stored in the database under a VMwork
> job and another thread picks that entry and starts the deployment,
> increasing the host capacity and sending the commands. Here there's a time
> gap between the host being picked up and the capacity increase for that
> host of a couple of seconds, which is well enough to go over the capacity
> on one or more hosts. A few VMwork job can be added in the DB queue
> targeting the same host before one gets picked up.
>
> To fix this issue, we're using Zookeeper to act as the multi JVM lock
> manager thanks to their curator library (
> https://curator.apache.org/curator-recipes/shared-lock.html). We also
> changed the time when the capacity is increased, which occurs now pretty
> much after the deployment plan is found and inside the zookeeper lock. This
> ensure we don't go over the capacity of any host, and it has been proven
> efficient since a month in our management server cluster.
>
> This adds another potential requirement which should be discuss before
> proposing a PR. Today the code works seamlessly without ZK too, to ensure
> it's not a hard requirement, for example in a lab.
>
> Comments?
>
> Kind regards,
> Marc-Aurèle
>



-- 
Daan

Re: Container Service

[Daan Hoogland]

If I recall correctly there must be an older version for 4.5 somewhere in that 
repo. I’m not sure though. You can try that one but no warranty beyond the end 
of this sentence. None was given anyway ;)
All in all you will have to code some, probably. Send us a pull request if you 
get it to work.

On 01/12/2017, 15:56, "benoit lair"  wrote:

Hello Daan,

Do you know if it could pass with a ACS 4.3 ? Do i have to upgrade towards
ACS 4.6 ?

Thanks

2017-12-01 15:34 GMT+01:00 Daan Hoogland :

> benoit, it is at the shapeblue website.
>
> There released version is for 4.6 found at the site
> http://www.shapeblue.com/cloudstack-container-service/
> and there is a branch in the repo for 4.10 https://github.com/shapeblue/
> ccs/pull/39 but this has not been released.
>
> On 01/12/2017, 15:01, "benoit lair"  wrote:
>
> Hello,
>
> I would like to know where can i find the ccs plugin.
> Also i would like to know if it can work with ACS 4.3 ?
>
> Thanks
>
>
> 2017-07-25 14:56 GMT+02:00 Simon Weller :
>
> > Grégoire,
> >
> > We have tested it on 4.8, but not 4.9.
> >
> > - Si
> > <http://www.linkedin.com/company/15330>
> >
> >
> >
> > 
> > From: Grégoire Lamodière 
> > Sent: Tuesday, July 25, 2017 2:31 AM
> > To: users@cloudstack.apache.org
> > Subject: RE: Container Service
> >
> > Hi Simon,
> >
> > Thanks a lot, I'll have a look.
> > Have you implement CCS on 4.9.2 ?
> >
> > I'll make a try before we start production on the new zone.
> >
> > Grégoire
> >
> > ---
> > Grégoire Lamodière
> > T/ + 33 6 76 27 03 31
> > F/ + 33 1 75 43 89 71
> >
> >
> > -Message d'origine-
> > De : Simon Weller [mailto:swel...@ena.com.INVALID]
> > Envoyé : lundi 24 juillet 2017 23:10
> > À : users@cloudstack.apache.org
> > Objet : Re: Container Service
> >
> > Grégoire,
> >
> >
> > Take a look at the URLs below:
> >
> >
> > Code and Docs: https://github.com/shapeblue/ccs
> >
> >
> > Packages: http://packages.shapeblue.com/ccs/
> >
> > - Si
> >
> > 
> > From: Grégoire Lamodière 
> > Sent: Monday, July 24, 2017 2:36 PM
> > To: users@cloudstack.apache.org
> > Subject: Container Service
> >
> > Dear All,
> >
> > Does anyone know the current status of Container Server ?
> > I remember Gilles talking about this in Berlin last year, but all
> links
> > sound down (Except the homepage of the module).
> > I cannot find install guide / any technical docs, nor packages.
> >
> > I would really like making some tries on this since we are now 
almost
> > working on 4.9.2.
> >
> > Cheers.
> >
> > ---
> > Grégoire Lamodière
> > T/ + 33 6 76 27 03 31
> > F/ + 33 1 75 43 89 71
> >
> >
>
>
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>



daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Container Service

[Daan Hoogland]

benoit, it is at the shapeblue website.

There released version is for 4.6 found at the site 
http://www.shapeblue.com/cloudstack-container-service/
and there is a branch in the repo for 4.10 
https://github.com/shapeblue/ccs/pull/39 but this has not been released.

On 01/12/2017, 15:01, "benoit lair"  wrote:

Hello,

I would like to know where can i find the ccs plugin.
Also i would like to know if it can work with ACS 4.3 ?

Thanks


2017-07-25 14:56 GMT+02:00 Simon Weller :

> Grégoire,
>
> We have tested it on 4.8, but not 4.9.
>
> - Si
> 
>
>
>
> 
> From: Grégoire Lamodière 
> Sent: Tuesday, July 25, 2017 2:31 AM
> To: users@cloudstack.apache.org
> Subject: RE: Container Service
>
> Hi Simon,
>
> Thanks a lot, I'll have a look.
> Have you implement CCS on 4.9.2 ?
>
> I'll make a try before we start production on the new zone.
>
> Grégoire
>
> ---
> Grégoire Lamodière
> T/ + 33 6 76 27 03 31
> F/ + 33 1 75 43 89 71
>
>
> -Message d'origine-
> De : Simon Weller [mailto:swel...@ena.com.INVALID]
> Envoyé : lundi 24 juillet 2017 23:10
> À : users@cloudstack.apache.org
> Objet : Re: Container Service
>
> Grégoire,
>
>
> Take a look at the URLs below:
>
>
> Code and Docs: https://github.com/shapeblue/ccs
>
>
> Packages: http://packages.shapeblue.com/ccs/
>
> - Si
>
> 
> From: Grégoire Lamodière 
> Sent: Monday, July 24, 2017 2:36 PM
> To: users@cloudstack.apache.org
> Subject: Container Service
>
> Dear All,
>
> Does anyone know the current status of Container Server ?
> I remember Gilles talking about this in Berlin last year, but all links
> sound down (Except the homepage of the module).
> I cannot find install guide / any technical docs, nor packages.
>
> I would really like making some tries on this since we are now almost
> working on 4.9.2.
>
> Cheers.
>
> ---
> Grégoire Lamodière
> T/ + 33 6 76 27 03 31
> F/ + 33 1 75 43 89 71
>
>



daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: cloudstack/simulator

[Daan Hoogland]

just completed a pul and run and the simulator comes up. I guess someone
fixed your issue without responding ;)

On Wed, Nov 29, 2017 at 8:31 AM, Daan Hoogland 
wrote:

> thanks, so clearly the database does not come up in the container. Not
> saying that this is not a cloudstack problem but more likely it is in the
> container definition. I see it is last pushed 7 hours ago so someone might
> have fixed it as we are mailing. I'll give it a try.
>
> On Tue, Nov 28, 2017 at 5:03 PM, Anthony Galea 
> wrote:
>
>> sure: http://txt.do/dqcuj
>>
>>
>> On Tue, Nov 28, 2017 at 5:26 PM, Daan Hoogland 
>> wrote:
>>
>> > Anthony,
>> > attachments get removed from the list. Can you include relevant snippets
>> > or use some upload service?
>> >
>> > On Tue, Nov 28, 2017 at 2:27 PM, Anthony Galea > >
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> Ran into an issue while trying the docker container
>> cloudstack/simulator
>> >> <https://hub.docker.com/r/cloudstack/simulator/>
>> >>
>> >> docker run --name cloudstack -d -p 8080:8080 cloudstack/simulator
>> >>
>> >> docker logs output attached.
>> >>
>> >> Can access the dashboard without issues with v4.6.0 but with latest I
>> get
>> >> a 503.[image: Inline image 1]
>> >> Regards,
>> >> Anthony
>> >>
>> >
>> >
>> >
>> > --
>> > Daan
>> >
>>
>
>
>
> --
> Daan
>



-- 
Daan

Re: cloudstack/simulator

[Daan Hoogland]

thanks, so clearly the database does not come up in the container. Not
saying that this is not a cloudstack problem but more likely it is in the
container definition. I see it is last pushed 7 hours ago so someone might
have fixed it as we are mailing. I'll give it a try.

On Tue, Nov 28, 2017 at 5:03 PM, Anthony Galea 
wrote:

> sure: http://txt.do/dqcuj
>
>
> On Tue, Nov 28, 2017 at 5:26 PM, Daan Hoogland 
> wrote:
>
> > Anthony,
> > attachments get removed from the list. Can you include relevant snippets
> > or use some upload service?
> >
> > On Tue, Nov 28, 2017 at 2:27 PM, Anthony Galea 
> > wrote:
> >
> >> Hi,
> >>
> >> Ran into an issue while trying the docker container cloudstack/simulator
> >> <https://hub.docker.com/r/cloudstack/simulator/>
> >>
> >> docker run --name cloudstack -d -p 8080:8080 cloudstack/simulator
> >>
> >> docker logs output attached.
> >>
> >> Can access the dashboard without issues with v4.6.0 but with latest I
> get
> >> a 503.[image: Inline image 1]
> >> Regards,
> >> Anthony
> >>
> >
> >
> >
> > --
> > Daan
> >
>



-- 
Daan

Re: cloudstack/simulator

[Daan Hoogland]

Anthony,
attachments get removed from the list. Can you include relevant snippets or
use some upload service?

On Tue, Nov 28, 2017 at 2:27 PM, Anthony Galea 
wrote:

> Hi,
>
> Ran into an issue while trying the docker container cloudstack/simulator
> 
>
> docker run --name cloudstack -d -p 8080:8080 cloudstack/simulator
>
> docker logs output attached.
>
> Can access the dashboard without issues with v4.6.0 but with latest I get
> a 503.[image: Inline image 1]
> Regards,
> Anthony
>



-- 
Daan

Re: Where is the vm root password published?

[Daan Hoogland]

it isn't logged, Rafael, not by cloudstack. It is cloudmonkey that logs the
API response object. It is the same response the UI uses to display it to
the user.

On Mon, Nov 27, 2017 at 3:45 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Interesting! I did not know that the password was logged. I thought it was
> a one time thing to show the password in the UI.
>
> On Mon, Nov 27, 2017 at 1:43 PM, Nux!  wrote:
>
> > Ok, so found out some more stuff.
> >
> > First of all, the password appears in management-server.log and
> > apilog.log, so that's one place to grep into.
> >
> > Second, I could query the jobid and get the password from there. E.g.
> from
> > cloudmonkey
> > query asyncjobresult jobid=caac0e1f-0aff-4065-8189-1d32d480e73f | grep
> > password\ =
> >
> > More info here
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/
> > CloudStack+cloudmonkey+CLI#CloudStackcloudmonkeyCLI-AsyncJobexecution
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > - Original Message -
> > > From: "Rafael Weingärtner" 
> > > To: "users" 
> > > Sent: Monday, 27 November, 2017 15:21:30
> > > Subject: Re: Where is the vm root password published?
> >
> > > Ah, if that is the case, I know it is stored in the VR of the network
> > where
> > > the VM is connected to.
> > >
> > > I forgot now the file, but it is something like “/var/usr?/cloud/cache”
> > or
> > > something that ends in “/cache/cloud”.
> > >
> > >
> > > Do we store these password in ACS database as well?
> > >
> > > On Mon, Nov 27, 2017 at 1:18 PM, Nux!  wrote:
> > >
> > >> Rafael,
> > >>
> > >> Yes indeed, sorry if I wasn't clear.
> > >>
> > >> --
> > >> Sent from the Delta quadrant using Borg technology!
> > >>
> > >> Nux!
> > >> www.nux.ro
> > >>
> > >> - Original Message -
> > >> > From: "Rafael Weingärtner" 
> > >> > To: "users" 
> > >> > Sent: Monday, 27 November, 2017 14:58:20
> > >> > Subject: Re: Where is the vm root password published?
> > >>
> > >> > Are you talking about the generated passwords to be injected in user
> > vms?
> > >> > Besides that, we do not have any other password. At least that I
> know.
> > >> >
> > >> > On Mon, Nov 27, 2017 at 12:56 PM, Nux!  wrote:
> > >> >
> > >> >> No, I mean the regular user VM instances.
> > >> >> I know they are held somewhere temporarily, just don't know where.
> :)
> > >> >>
> > >> >> --
> > >> >> Sent from the Delta quadrant using Borg technology!
> > >> >>
> > >> >> Nux!
> > >> >> www.nux.ro
> > >> >>
> > >> >> - Original Message -
> > >> >> > From: "Rafael Weingärtner" 
> > >> >> > To: "users" 
> > >> >> > Sent: Monday, 27 November, 2017 12:26:59
> > >> >> > Subject: Re: Where is the vm root password published?
> > >> >>
> > >> >> > If you are talking about the system VMs password.
> > >> >> > If you set the parameter "system.vm.random.password" to "true",
> > then
> > >> you
> > >> >> > can see the password at "system.vm.password"
> > >> >> >
> > >> >> > On Mon, Nov 27, 2017 at 10:24 AM, Nux!  wrote:
> > >> >> >
> > >> >> >> Hello,
> > >> >> >>
> > >> >> >> I know that the vm root password is temporarily stored somewhere
> > in
> > >> the
> > >> >> >> system. I need to find it out for accessing the console of some
> > >> >> instances
> > >> >> >> created programmatically.
> > >> >> >> Where do I look?
> > >> >> >>
> > >> >> >> Cheers,
> > >> >> >> Lucian
> > >> >> >>
> > >> >> >> --
> > >> >> >> Sent from the Delta quadrant using Borg technology!
> > >> >> >>
> > >> >> >> Nux!
> > >> >> >> www.nux.ro
> > >> >> >>
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> > --
> > >> >> > Rafael Weingärtner
> > >> >>
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > Rafael Weingärtner
> > >>
> > >
> > >
> > >
> > > --
> > > Rafael Weingärtner
> >
>
>
>
> --
> Rafael Weingärtner
>



-- 
Daan

Re: VPC across multiple hypevisors

[Daan Hoogland]

Asanka,
I've not seen that work but it might. I can't think of a hard impediment
but having the two types of hypervisors in the same zone is required. If
all else fails, another solution may be to split the tiers into separate
networks and create a private gateway from the one to the other.
hope you succeed, let us know
Daan

On Mon, Oct 16, 2017 at 8:24 AM, Asanka Gunasekara  wrote:

> Thanks for the reply Makrand
>
> We have a requirement, where we need to have Database on Vmware Esxi and
> Application server On Xen. I am Applisuer using routing we can connect
> these two together. But is it possible to create a single VPC combining
> these two environments or just to extend the Database VPC to application
> server.
>
> Thanks adn regards
>
> Asanka
>
> On 16 October 2017 at 11:47, Makrand  wrote:
>
> > Hi,
> >
> > Can you be a bit more descriptive as to what exactly you want to do?
> >
> > Note:-
> > VPC is nothing but multi-tier network (A VPC acts as a container for
> > multiple isolated networks that can communicate with each other via its
> > virtual router.) So if you're having VMs running in multi-hypervisor
> setup,
> > as long as they are connected to same VR that can work. I haven't setup
> > anything like this. Just a guess on my part.
> >
> >
> >
> > --
> > Makrand
> >
> >
> > On Mon, Oct 16, 2017 at 10:37 AM, Asanka Gunasekara 
> > wrote:
> >
> > > Hi Guys, is there a way to do a VPC across multiple hypervisors
> > >
> > > Thanks and Regards
> > >
> > > Asanka
> > >
> >
>



-- 
Daan

Re: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the database

[Daan Hoogland]

sorry Cristian, I wasn't clear. Can you add a jira ticket at
issues.apache.org/jira?

@devs I have heard this before but am not sure if it was exactly the same.
Anybody else? Was this fixed in 4.10 or master yet?
tl;dr setting password doesn't work for Cristian due to the firewall on the
VR.

On Fri, Oct 13, 2017 at 1:44 PM, Ciobanu Cristian 
wrote:

> Daan,
>
> Can I track this issue somewhere?
>
>
> Thank you!
> Cristian
>
> -----Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, October 12, 2017 9:46 AM
> To: users@cloudstack.apache.org
> Subject: Re: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the database
>
> Cristian,
>
> I am cross-posting this to dev@coudstack.a.o, sorry for the noise. I have
> heard this before but am not sure if it was exactly the same. It sounds
> like a bug to me. Can you enter one in jira?
> Anybody else? Was this fixed in 4.10 or master yet?
>
> On Wed, Oct 11, 2017 at 11:23 PM, Ciobanu Cristian
>  > wrote:
>
> > Hello,
> >
> >  After I continued the investigation I found that router is not
> > allowing the VM to fetch the password (port 8080) not sure what is
> > wrong with this version but in order to fix I have added this rule "-A
> > INPUT -p tcp -m tcp --dport 8080 -j ACCEPT"  on virtual router..
> >
> >   Any idea how to fix this, permanent?  In case reinstall the router
> > for sure I will have to do this again.
> >
> >
> > Thank you.
> > Cristian
> >
> > -Original Message-
> > From: Ciobanu Cristian [mailto:cristian.c@istream.today]
> > Sent: Wednesday, October 11, 2017 9:45 PM
> > To: 'users@cloudstack.apache.org' 
> > Subject: RE: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the
> > database
> >
> > I was able to update the virtual router only after I have restarted
> > the iptables-persistend form virtual router side, not sure what is
> > wrong with this router version but I don't get the right status if I
> > don't restart the iptables from virtual router, I have did multiple
> tests :
> >
> > Example :
> >  -  Reboot router
> > - getting this error : job-3247/job-3248, cmd: CheckSshCommand)
> > (logid:6b3de9fa) Trying to
> > > connect to 149.56.xxx.xx  ( I see this error in management log )
> > - restart iptables from router side
> > - works
> >
> >   In case I destroy/restart the router I have to repeat the same
> > thing, restart iptables...
> >
> >   I also tested a new deploy with a template used before on this
> > setup, looks like the password set for new deploy is not working...
> >
> >
> > Any idea why I have those issue?
> >
> > Upgraded from 4.5.2 to 4.9.3 ( shapeblue packages )
> >
> >
> > Regards,
> > Cristian
> >
> >
> > -Original Message-
> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > Sent: Wednesday, October 11, 2017 6:10 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the
> > database
> >
> > that is a tricky one. You can destroy the vm from VmWare and set the
> > state to stopped in the DB. It should then start a new one.
> > check if r-4-VM/ROOT-4-01.vmdk has gone from the datastore.
> >
> > the cause is probably some synchronisation issue. We've seen and
> > solved it before but are yet to find the root cause.
> >
> >
> > On Wed, Oct 11, 2017 at 4:23 PM, Ciobanu Cristian
> >  > >
> > wrote:
> >
> > > Hello,
> > >
> > >Was my mistake, forgot to add the system template from cloudstack
> > > interface before starting the upgrade, now I have other issue, looks
> > > like after I have enabled one of the zone and click on upgrade
> > > virtual router I still see the state "starting" if I check the
> > > router from vSphere side is up.
> > >
> > >
> > >   This is what is see :
> > >
> > > tting
> > > catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> > > (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> > > job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Chose disk
> > > controller for vol ROOT -> osdefault, based on root disk controller
> > > settings at global configuration setting.
> > > catalina.out:INFO  [c.c.h.v.m.DatastoreMO]
> > > (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> > > job-3247/job-3248, cmd: StartCommand)
&g

Re: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the database

[Daan Hoogland]

Cristian,

I am cross-posting this to dev@coudstack.a.o, sorry for the noise. I have
heard this before but am not sure if it was exactly the same. It sounds
like a bug to me. Can you enter one in jira?
Anybody else? Was this fixed in 4.10 or master yet?

On Wed, Oct 11, 2017 at 11:23 PM, Ciobanu Cristian  wrote:

> Hello,
>
>  After I continued the investigation I found that router is not allowing
> the VM to fetch the password (port 8080) not sure what is wrong with this
> version but in order to fix I have added this rule "-A INPUT -p tcp -m tcp
> --dport 8080 -j ACCEPT"  on virtual router..
>
>   Any idea how to fix this, permanent?  In case reinstall the router for
> sure I will have to do this again.
>
>
> Thank you.
> Cristian
>
> -Original Message-
> From: Ciobanu Cristian [mailto:cristian.c@istream.today]
> Sent: Wednesday, October 11, 2017 9:45 PM
> To: 'users@cloudstack.apache.org' 
> Subject: RE: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the database
>
> I was able to update the virtual router only after I have restarted the
> iptables-persistend form virtual router side, not sure what is wrong with
> this router version but I don't get the right status if I don't restart the
> iptables from virtual router, I have did multiple tests :
>
> Example :
>  -  Reboot router
> - getting this error : job-3247/job-3248, cmd: CheckSshCommand)
> (logid:6b3de9fa) Trying to
> > connect to 149.56.xxx.xx  ( I see this error in management log )
> - restart iptables from router side
> - works
>
>   In case I destroy/restart the router I have to repeat the same thing,
> restart iptables...
>
>   I also tested a new deploy with a template used before on this setup,
> looks like the password set for new deploy is not working...
>
>
> Any idea why I have those issue?
>
> Upgraded from 4.5.2 to 4.9.3 ( shapeblue packages )
>
>
> Regards,
> Cristian
>
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Wednesday, October 11, 2017 6:10 PM
> To: users@cloudstack.apache.org
> Subject: Re: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the database
>
> that is a tricky one. You can destroy the vm from VmWare and set the state
> to stopped in the DB. It should then start a new one.
> check if r-4-VM/ROOT-4-01.vmdk has gone from the datastore.
>
> the cause is probably some synchronisation issue. We've seen and solved it
> before but are yet to find the root cause.
>
>
> On Wed, Oct 11, 2017 at 4:23 PM, Ciobanu Cristian  >
> wrote:
>
> > Hello,
> >
> >Was my mistake, forgot to add the system template from cloudstack
> > interface before starting the upgrade, now I have other issue, looks
> > like after I have enabled one of the zone and click on upgrade virtual
> > router I still see the state "starting" if I check the router from
> > vSphere side is up.
> >
> >
> >   This is what is see :
> >
> > tting
> > catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> > (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> > job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Chose disk
> > controller for vol ROOT -> osdefault, based on root disk controller
> > settings at global configuration setting.
> > catalina.out:INFO  [c.c.h.v.m.DatastoreMO]
> > (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> > job-3247/job-3248, cmd: StartCommand)
> > (logid:6b3de9fa) Folder r-4-VM exists on datastore catalina.out:INFO
> > [c.c.h.v.m.DatastoreMO] (DirectAgent-381:ctx-5f16ff50
> > ns53.ip-149-56-xx.net, job-3247/job-3248, cmd: StartCommand)
> > (logid:6b3de9fa) Search file ROOT-4-01.vmdk on [datastore1]
> > catalina.out:INFO  [c.c.h.v.m.DatastoreMO]
> > (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> > job-3247/job-3248, cmd: StartCommand)
> > (logid:6b3de9fa) File [datastore1] ROOT-4-01.vmdk exists on
> > datastore catalina.out:INFO  [c.c.h.v.m.DatastoreMO]
> > (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> > job-3247/job-3248, cmd: StartCommand)
> > (logid:6b3de9fa) Search file ROOT-4-01-flat.vmdk on [datastore1]
> > catalina.out:INFO  [c.c.h.v.m.DatastoreMO]
> > (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> > job-3247/job-3248, cmd: StartCommand)
> > (logid:6b3de9fa) File [datastore1] ROOT-4-01-flat.vmdk exists on
> > datastore catalina.out:INFO  [c.c.s.r.VmwareStorageLayoutHelper]
> > (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> > job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) sync
> > [datasto

Re: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the database

[Daan Hoogland]

","dns1":"172.20.0.3","dns2":"8.8.8.8","broadcastType":"
> Native","type":"Guest","broadcastUri":"vlan://untagged","
> isSecurityGroupEnabled":false,"name":"vSwitch1"}
> catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Prepare network on
> vmwaresvs vSwitch1 with name prefix: cloud.guest
> catalina.out:INFO  [c.c.h.v.m.HypervisorHostHelper]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Network
> cloud.guest.untagged.200.1-vSwitch1 is ready on vSwitch vSwitch1
> catalina.out:INFO  [c.c.h.v.m.HypervisorHostHelper]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Network
> cloud.guest.untagged.200.1-vSwitch1 is ready on vSwitch vSwitch1
> catalina.out:INFO  [c.c.h.v.m.HypervisorHostHelper]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Network
> cloud.guest.untagged.200.1-vSwitch1 is ready on vSwitch vSwitch1
> catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Preparing NIC device
> on network cloud.guest.untagged.200.1-vSwitch1
> catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Prepare NIC device
> based on NicTO: {"deviceId":1,"networkRateMbps":-1,"
> defaultNic":false,"pxeDisable":true,"nicUuid":"fe3f7db4-
> 9ff5-4b63-883b-e08bb6f7568b","uuid":"8ef0b547-f569-4987-
> ac80-9ebf72f44fdd","ip":"0.0.0.0","netmask":"0.0.0.0","
> gateway":"0.0.0.0","mac":"02:00:5c:9c:00:0a","broadcastType":"LinkLocal","
> type":"Control","isSecurityGroupEnabled":false,"name":"vSwitch1"}
> catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Prepare network on
> vmwaresvs vSwitch1 with name prefix: cloud.private
> catalina.out:WARN  [c.c.h.v.r.VmwareResource]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Unrecognized
> broadcast type in VmwareResource, type: LinkLocal. Use vlan info from
> labeling: untagged
> catalina.out:INFO  [c.c.h.v.m.HypervisorHostHelper]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Network
> cloud.private.untagged.0.1-vSwitch1 is ready on vSwitch vSwitch1
> catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Preparing NIC device
> on network cloud.private.untagged.0.1-vSwitch1
> catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Configure VNC port
> for VM r-4-VM, port: 5939, host: ns53.ip-149-56-xx.net
> catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: StartCommand) (logid:6b3de9fa) Found existing disk
> info from volume path: ROOT-4-01
> catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: CheckSshCommand) (logid:6b3de9fa) Trying to connect
> to 149.56.xxx.xx
> catalina.out:WARN  [o.a.c.f.j.i.AsyncJobMonitor] (Timer-1:ctx-8baef180)
> (logid:c6f5e75e) Task (job-3247) has been pending for 129 seconds
> catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: CheckSshCommand) (logid:6b3de9fa) Could not connect
> to 149.56.xxx.xx due to java.net.ConnectException: Connection timed out
> catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-381:ctx-5f16ff50 ns53.ip-149-56-xx.net,
> job-3247/job-3248, cmd: CheckSshCommand) (logid:6b3de9fa) Trying to connect
> to 149.56.xxx.xx
> catalina.out:WARN  [o.a.c.f.j.i.AsyncJobMonitor] (Timer-1:ctx-3026cb48)
> (logid:9ea6ca9e) Task (job-3247) has been pending for 189 seconds
> catalina.out:INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-381:ctx-5f16ff50 ns53x

Re: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the database

[Daan Hoogland]

did you see any stack trace around the place you saw that error; above or
just below?
did you see any warning messages or suspicious debug statements above the
error message?
can you double check the package installation of the cloud* packages on
your machine and give us the versions?

​the procedure you have followed is the correct and current one​.

On Wed, Oct 11, 2017 at 2:51 PM, Ciobanu Cristian 
wrote:

> I have used the following info in my repo: baseurl=http://packages.
> shapeblue.com/cloudstack/upstream/centos/4.9 , the 4.9.3 was installed.
>
>
> Regards,
> Cristian
>
> -Original Message-
> From: Rene Moser [mailto:m...@renemoser.net]
> Sent: Wednesday, October 11, 2017 3:38 PM
> To: users@cloudstack.apache.org
> Subject: Re: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the database
>
> did you upgrade to 4.9.2 or 4.9.3? centos?
>
> Regards
> René
>
>


-- 
Daan

Re: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the database

[Daan Hoogland]

Christian,

The chances are I have not done the exact same upgrade as you are
attempting. the generic upgrade of the database (assuming the right
template and other things) is quite straight forward. You will need to give
us at least the stacktrace and any related information. from the log above
it, if this is a reproducible error.

On Wed, Oct 11, 2017 at 2:34 PM, Ciobanu Cristian 
wrote:

> I have restored back to 4.5.2, but if I upgrade again using the steps
> provide in documentation I will end with the same error..  did you tested
> this? With tha configuration (acs 4.5.2, vmware, local storage) ?
>
> Regards,
> Cristian
>
> -Original Message-----
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Wednesday, October 11, 2017 3:29 PM
> To: users@cloudstack.apache.org
> Subject: Re: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the database
>
> Hi the management server on starting up should take care of the upgrade.
> if you have a clustered MS make sure to start only one. In your case after
> the failure you should probably restore the latest backup before continuing.
>
> On Wed, Oct 11, 2017 at 2:26 PM, Ciobanu Cristian  >
> wrote:
>
> > Hello,
> >
> >
> >
> >In order to upgrade cloudstack to 4.9 I have followed this
> > doecumentation
> > :
> > http://docs.cloudstack.apache.org/projects/cloudstack-
> > release-notes/en/4.9.2
> > .0/upgrade/upgrade-4.5.html  and ended with this :
> >
> >
> >
> > management-server.log:2017-10-11 08:05:35,612 WARN
> > [o.a.c.s.m.c.ResourceApplicationContext] (main:null) (logid:)
> > Exception encountered during context initialization - cancelling refresh
> attempt:
> > org.springframework.context.ApplicationContextException: Failed to
> > start bean 'cloudStackLifeCycle'; nested exception is
> > com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> > database
> >
> >
> >
> > Is there a valid upgrade procedure or script for : Cloudstack 4.5.2 to
> > CloudStack 4.9 ( VMware with Local Storage ) ?
> >
> >
> >
> > (cloudstack was installed from shapeblue repo)
> >
> >
> >
> >
> >
> > Thank you.
> >
> > Cristian
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> Daan
>
>


-- 
Daan

Re: Upgrade Cloudstack 4.5 to 4.9 - Unable to upgrade the database

[Daan Hoogland]

Hi the management server on starting up should take care of the upgrade. if
you have a clustered MS make sure to start only one. In your case after the
failure you should probably restore the latest backup before continuing.

On Wed, Oct 11, 2017 at 2:26 PM, Ciobanu Cristian 
wrote:

> Hello,
>
>
>
>In order to upgrade cloudstack to 4.9 I have followed this
> doecumentation
> :
> http://docs.cloudstack.apache.org/projects/cloudstack-
> release-notes/en/4.9.2
> .0/upgrade/upgrade-4.5.html  and ended with this :
>
>
>
> management-server.log:2017-10-11 08:05:35,612 WARN
> [o.a.c.s.m.c.ResourceApplicationContext] (main:null) (logid:) Exception
> encountered during context initialization - cancelling refresh attempt:
> org.springframework.context.ApplicationContextException: Failed to start
> bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the
> database
>
>
>
> Is there a valid upgrade procedure or script for : Cloudstack 4.5.2 to
> CloudStack 4.9 ( VMware with Local Storage ) ?
>
>
>
> (cloudstack was installed from shapeblue repo)
>
>
>
>
>
> Thank you.
>
> Cristian
>
>
>
>
>
>
>
>


-- 
Daan

Re: release manager 4.11?

[Daan Hoogland]

Imran,

first please read [1] and [2]. There are bound to be ommisions in it. You
can come back with questions anytime.

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedure
[2]
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Management



On Tue, Oct 10, 2017 at 9:43 AM, Imran Ahmed  wrote:

> Hi Daan,
> I would be happy for contributing my part. Please guide me about the
> procedures.
> Regards,
>
> Imran
>
> -Original Message-----
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Tuesday, October 10, 2017 12:10 PM
> To: dev; users@cloudstack.apache.org
> Subject: release manager 4.11?
>
> users and devs,
>
> Sorry for the cross post.
>
> Is there any devops guru that wishes to take on the 4.11 release, with
> assistence of course?
>
> --
> Daan
>
>


-- 
Daan

release manager 4.11?

[Daan Hoogland]

users and devs,

Sorry for the cross post.

Is there any devops guru that wishes to take on the 4.11 release, with
assistence of course?

-- 
Daan

Re: [ANNOUNCE] Syed Mushtaq Ahmed has joined the PMC

[Daan Hoogland]

Good going and clear trail Syed

On Mon, Oct 9, 2017 at 2:06 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Congratulation Syed, and thanks for the hard work you have put into ACS so
> far.
>
> On Mon, Oct 9, 2017 at 8:59 AM, Rohit Yadav 
> wrote:
>
> > Congratulations Syed!
> >
> >
> > - Rohit
> >
> > 
> > From: Paul Angus 
> > Sent: Monday, October 9, 2017 4:56:51 PM
> > To: d...@cloudstack.apache.org; users@cloudstack.apache.org
> > Subject: [ANNOUNCE] Syed Mushtaq Ahmed has joined the PMC
> >
> > Fellow CloudStackers,
> >
> > It gives me great pleasure to say that Syed has be invited to join the
> PMC
> > and has gracefully accepted.
> > Please joining me in congratulating Syed!
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
>
>
> --
> Rafael Weingärtner
>



-- 
Daan

Re: [VOTE] Apache Cloudstack 4.9.3.0 RC1

[Daan Hoogland]

I have had no time to test in any serious way but based on the work of
colleagues Glenn and Boris I would say +2 (binding;)
+1 (binding)

On Wed, Aug 30, 2017 at 7:40 PM, Sebastian Gomez  wrote:

> Looks well!
>
>
>
> Atentamente,
> Sebastián Gómez
>
> On Wed, Aug 30, 2017 at 9:05 AM, Boris Stoyanov <
> boris.stoya...@shapeblue.com> wrote:
>
> > +1
> >
> > I’ve did upgrade testing from 4.9.2 on the following hypervisors:
> >
> > VMware 55u3 with management on CentOS7 - successful
> > KVM on CentOS7 both hosts and management - successful
> > XenServer 6.5sp1 running on management CentOS6 - successful
> >
> > Smoketests are passing on the latest runs as well so this LGTM
> >
> > Bobby.
> >
> > boris.stoya...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> > > On Aug 29, 2017, at 4:04 PM, Glenn Wagner 
> > wrote:
> > >
> > > +1
> > >
> > > Centos 7 Management Server
> > > VMware Vsphere 5.5U3
> > >
> > >
> > > Basic testing done
> > > Creating and removing guest networks
> > > Creating user and domains
> > > Create VPC's with LB's and Site to site VPN, Delete VPC's
> > > Upload templates and ISO , remove templates and iso's
> > > Add instances with single network , create shared network then add to
> > instance
> > > Attach ISO to instance and remove
> > >
> > > LGTM
> > >
> > > Glenn
> > >
> > >
> > >
> > >
> > > glenn.wag...@shapeblue.com
> > > www.shapeblue.com
> > > Winter Suite, 1st Floor, The Avenues, Drama Street, Somerset West, Cape
> > Town  7129South Africa
> > > @shapeblue
> > >
> > >
> > >
> > >
> > > -Original Message-
> > > From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
> > > Sent: Tuesday, 29 August 2017 10:01 AM
> > > To: d...@cloudstack.apache.org; users@cloudstack.apache.org
> > > Subject: Re: [VOTE] Apache Cloudstack 4.9.3.0 RC1
> > >
> > > All,
> > >
> > >
> > > I've built packages for users who may want to help test but would avoid
> > building packages themselves using the source tarball, they may
> > consume/test from here:
> > >
> > > http://temp.yadav.xyz/4.9.3.0-rc1/
> > >
> > >
> > > Thanks.
> > >
> > >
> > > - Rohit
> > >
> > > 
> > > From: Rohit Yadav 
> > > Sent: Monday, August 28, 2017 3:14:12 PM
> > > To: d...@cloudstack.apache.org
> > > Cc: users@cloudstack.apache.org
> > > Subject: [VOTE] Apache Cloudstack 4.9.3.0 RC1
> > >
> > > Hi All,
> > >
> > > I've created a 4.9.3.0 RC1 release, with the following artifacts up
> for a
> > > vote:
> > >
> > > Git Branch and Commit SH:
> > >
> > > https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=
> > shortlog;h=refs/heads/4.9.3.0-RC20170828T1452
> > > https://github.com/apache/cloudstack/tree/4.9.3.0-RC20170828T1452
> > > Commit: d145944be0d04724802ff132399514bf71c3e7b0
> > >
> > > 4.9 branch smoke test PR:
> > > https://github.com/apache/cloudstack/pull/2217
> > >
> > > List of commits/changes since 4.9.2.0 release:
> > > https://github.com/apache/cloudstack/compare/4.9.2.0...
> > 4.9.3.0-RC20170828T1452
> > >
> > > Source release (checksums and signatures are available at the same
> > > location):
> > > https://dist.apache.org/repos/dist/dev/cloudstack/4.9.3.0/
> > >
> > > PGP release keys (signed using 0EE3D884):
> > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > >
> > > Vote will be open for 72 hours.
> > >
> > > For sanity in tallying the vote, can PMC members please be sure to
> > indicate "(binding)" with their vote?
> > >
> > > [ ] +1  approve
> > > [ ] +0  no opinion
> > > [ ] -1  disapprove (and reason why)
> > >
> > > Regards,
> > > Rohit Yadav
> > >
> > > rohit.ya...@shapeblue.com
> > > www.shapeblue.com
> > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> > >
> > >
> > >
> >
> >
>



-- 
Daan

Re: one question network survey

[Daan Hoogland]

H Imran,
I am not sure I can get from your reply whether you configured anything for 
those vxlans inside cloudstack. It sounds like your just trunking upstream.
If I am wrong (not uncommon), you are probably talking about the guestnetwork 
as it ties your hosts together, right?

My question is mainly to what did you configure in cloudstack to use vxlans in 
your cloud.

Thanks,

On 2017/08/28 11:29, "Imran Ahmed"  wrote:

Hi Daan,

I use a separate trunk  (OVS or non OVS bonded with LACP ) connected to 
multiple switches (which are already configured into a switch stack). There can 
be multiple case scenarios but I am mentioning the most generic one .

Hope that answers your question if I have correctly understood your 
question.


Regards,



-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com] 
Sent: Monday, August 28, 2017 12:20 PM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: one question network survey

Devs and users,

Can you all please tell me how you are using VxLan in your cloudstack 
environments?

The reason behind this is that I am planning some refactoring in the 
networkgurus and I don’t want to break any running installations on upgrade. If 
you are not using vxlan but know of people that might not react, using it, 
please point me to them.

Thanks,

daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 





daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

one question network survey

[Daan Hoogland]

Devs and users,

Can you all please tell me how you are using VxLan in your cloudstack 
environments?

The reason behind this is that I am planning some refactoring in the 
networkgurus and I don’t want to break any running installations on upgrade. If 
you are not using vxlan but know of people that might not react, using it, 
please point me to them.

Thanks,

daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Fwd: Error on uploading a SSL Certificate with cloudmonkey

[Daan Hoogland]

H Dennis, I am off this week with bad Internet at least the first half of
the week. I'll have a look when I can. In the meanwhile, could you find the
matching log entry for that error and paste the cloudmonkey command here?

Biligual auto correct use.  Read at your own risico

On 14 Aug 2017 3:52 pm, "Dennis Meyer"  wrote:

> Hi,
>
> i want to implement SSL offloading on the vpc router loadbalancer,
> referencing on this ticket: https://issues.apache.
> org/jira/browse/CLOUDSTACK-4821 it should be implemented with version
> 4.3. And following this document: https://cwiki.apache
> .org/confluence/display/CLOUDSTACK/SSL+Termination+Support there should
> be a gui which doenst exist. In the api documentation are severall calls
> belonging to ssl offloading (https://cloudstack.apache.org
> /api/apidocs-4.9/).
>
> i tried to upload a ssl certificate with cloudmonkey like the file
> attached.
>
> I receive the following error after execution:
>
> Error 530: DB Exception on: com.mysql.jdbc.JDBC4PreparedStatement@3e689c30:
> INSERT INTO sslcerts (sslcerts.id, sslcerts.uuid, sslcerts.certificate,
> sslcerts.chain, sslcerts.key, sslcerts.password, sslcerts.account_id,
> sslcerts.domain_id, sslcerts.fingerprint) VALUES (null,
> _binary'62bebc90-7cbe-4cfc-9ed0-d6cf71b5bf6a', _binary'-BEGIN
> CERTIFICATE-\nMIID6TCCAtGgAwIBAgIJANNyfmHIdXU6MA0GCSqGSI
> b3DQEBCwUAMIGKMQswCQYD\nVQQGEwJERTEWMBQGA1UECAwNVGVsZXR1YmJ5
> bGFuZDEXMBUGA1UEBwwOU2NobHVt\ncGZoYXVzZW4xFjAUBgNVBAoMDU1hcm
> lhY3JvbiBMdGQxETAPBgNVBAsMCElUIENy\nb3dkMR8wHQYDVQQDDBZhd2Vz
> b21lLnNlcnZlci50ZXN0aW5nMB4XDTE3MDgxMDEx\nMDEzN1oXDTE4MDgxMD
> ExMDEzN1owgYoxCzAJBgNVBAYTAkRFMRYwFAYDVQQIDA1U\nZWxldHViYnls
> YW5kMRcwFQYDVQQHDA5TY2hsdW1wZmhhdXNlbjEWMBQGA1UECgwN\nTWFyaW
> Fjcm9uIEx0ZDERMA8GA1UECwwISVQgQ3Jvd2QxHzAdBgNVBAMMFmF3ZXNv\n
> bWUuc2VydmVyLnRlc3RpbmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
> AoIB\nAQCYHGJp+NieuEFoSLjmDAHxlX8pVGGXKYw68MpvoMzGkT3zHxpvZz
> sI71FaoteX\nC5kyKv8o485KbTGsVTQlkYtuw9mzuOwhEfQ3DsgsX0OxrJeW
> GCMwKWtq/O1P5Mk+\nXUitCNDCDg9j89KGe0PRQZ8XGMn3mOEpsBuTe0ST6k
> ZTrAl4hA/0hkmp5HEkW9JO\nwUqzcHeCLM2It5o2cfoIOMjJEO30u6pFeQKc
> OyGkjijtsUC2Oo6FfJJx9fSSj1dU\nn7a17/yLt98PIP6OMc22g5Q3plV+9h
> LoPH+pHrpEqp35abeu8s32uRLLxuObiI7w\nzKgMSi5k/wT30p65v1ONA/x9
> AgMBAAGjUDBOMB0GA1UdDgQWBBTfOZmo+l5/QkD1\nlpQR1dDYfkEbVjAfBg
> NVHSMEGDAWgBTfOZmo+l5/QkD1lpQR1dDYfkEbVjAMBgNV\nHRMEBTADAQH/
> MA0GCSqGSIb3DQEBCwUAA4IBAQBg2Q5p6F/W+Ktsp28YL5UtOqz+\nqRRDjL
> hzUvCdMNR9KChJEhbe3hz/g+OWq+WNhXCEbEpHH0D1b0Ie850DpJjScUmd\
> ni8nm29EB+0HLKVBKKK/Y+iAQHIr/ujNqPdZWSfMJGs9vc2Rxq2NW1+FyUn8
> gbUdc\n62GW+46spA0ESGO3bjp/LyPIEvtWnvIf9PUdaCwXDOD0KMcdX9rze
> CEaXxm0b5hy\nWvz0JGKaNWyNmmUFBdP/FtEvyDQjS4vWkOIVKoRGVHst9h6
> ksMql1W5FtByGDivm\nt5FmzMxWHgPgeafQ66tv8UD+kLLNTMENSoxN8lEpa550wg4gGRfNnvVQFK3F\n-END
> CERTIFICATE-', null, _binary'2KtHB01zqydgCbWU6FXun2
> WsnhAYgSId3BNVCZYr4tYDIEqbKokxb+v/7eu+ZcbJbA/0mY5b9GdHLmU8Gc
> d9VBEibYfCEQ8RXXDgVu11xEYo4eeKv6boVA3nluW1Uk4K53vLVKIWGs3Gxq
> sc99k70GBy/BfaqC/bp4FndSpIA+qBn8I5DEll3z5MZFGnlhcmqxkH+zkqwb
> oGoCDvO4RBuVdkCwkKO92mNsN8Wq9Es9RzMTIrYZ4INk0/B7jesU72KyAev+
> R/EKmAuC7+mOqtJ2j/tneoLJHdDk8/+ufIsf/vNQk7SjaoBwY0nGFJH+MhMj
> jpJ87XHZtRSyfvDsUORNce0On/RwfyG4LmiSvf3au7NSTNIrH9vQAJ9Jb/MY
> vA0cFrZHEnIy5FvYzkjnigL1YdzLkyK6fWllkcRtuAUcOPfXCMNrCgMU5z3x
> DfWYICpkJX0hkLRWAR2UpgO5XEBaG5wW3iQy/GNzeG3xG6GP8B8IJ/huVPKA
> IcxqXJ0EdcK+npUanMfIoXbKm13gbfWHUNmMviLOXBVswcPxrIV3/NVfNsC9
> ZcskvfzKKrFhKJT6+nym5H0w9USDuMvGBoSCeXxygH9NCgz7pEjsdl3YE/uP
> W3L7TAxzL4V/8gkfHOY5O2s9/g6rXUJbAKMUOKlBQr3uO5cCeXWP6xOu/LHE
> hcBJaJpiQlYVaxEaof4de235uPmUlEsUKV1KaI3X0PXN0V+Rdd9zQXXvleNp
> XOSkK009MRwwiVbfcfvgugn9ISxGhX7TmWUBNhMZtmpn51zSmOHnOQfURLvn
> kgxt63orjkNt0I8w4ggecQmpPjjWLILVkbhjZHNoP6JzfM0GTHx2XbaL/Oxh
> UbmDdRXhmVySNECZpzqFIKIsvqmY9YAM0lf5o4JNJd/LbiowLtL/3ruaLxoX
> N8gxMeY16EACZw05GMGvOH6Tm9cIQ7dQIGp68w3mby4kyzID0i3qeesRiZPL
> DaQloJC3uOIdy8jiywqBKOt2W02SibYomdjBHPTkznZ3HzBWqsUr/EghI0Vy
> BQvs/wZgn0a1JMbAhXnQmpbf89KJiHdlrhVRdcCEauMJd+YE47IfHHqUHurd
> gU3fnTnkGRuGGyq2GhxDhnxVsYlLH37VQocXYc7U/nfstAVmB5j7DNLdDh2K
> dQo94KrBoMezgf+V/C8ey7CjxIoGTNxi7ETozEKe367TngjxeP6PhpWjaOk2
> LueVLwexjIpSvHZGUVGlC+W2+1XsSJ9/R78ztaEyK5YNQWfMXYOITB/
> +HxvJ/5xUtirL5SRUky35kz4/OlVmI3q1coYERv+KThSmMWx0sJLF9Yv2DXW
> oZ33JfqaZoZTUyfzgPfyB4+knQuZPrjCmSNUoA+sPDYUUC8yGsH+iMHQTskT
> OHaPEudOVEgb71jEOirKkTT/bkBfNc2pvkLNS5ATDWqDlPChy42rEs
> 5bIPLObulM+dL7FOUbV5TUfIbG92IJhXgoU5vGKtl0SSucImfdWvGRvBjcHh
> zsJit0H7HJh2ENrKiF+aohiJYh9O55yrfkI1r3Cl82oMnP9O+66spwMhXv4q
> fkTLqY8CgbSNGLuLpR2hkKmb5PARtM9QkEVuPTzw5/meO2CRVzBPSCVucCqP
> YcbRCEDJTsQVmyIZbIH6JcMX0tOryEr17h+eSLGmKgOY14saEmx0+HG4nRss
> up5EIyyca4fka/PG2/q5kXBBLVo7xoJn9b9tE00x5zz5V2FIzwO4eLBQ+mwB
> ZmNxpRk9vNYGKtTn70JVOLt5s0Ces/eejsZeqnWnHG9H76gtx9yHB7zRgg0j
> GbSXCxrbPZfRBtiYMME5RivM7rVgeRBs8CFt73QDs+FCQb+68USE8/J5QeeQ
> 6TfOqgexSmMcTYfn6ad3grDZoQ4qPjkGqVOck+9jtENGa/sT/v6wwQM+eDvp
> SptMBvwbRZAqgnE55T88iIV/OzVke4pXvajXp+0mDka92EP6+cqDU3RuVBSe
> t2kY+KY3Uzjxbq2fDDHngvPbFohB81me8xRqXIqrl1SEjTjJLHLcrs2fWoit
> ZxcHfihx8qhOrOhkCum1I3vRsTcf

Re: [README][Quarterly Call] - CloudStack Development, Blockers and Community Efforts

[Daan Hoogland]

Looking forward to this but I will only be available the first half hour for 
this.

On 19/07/2017, 20:58, "ilya"  wrote:

Hi Devs and Users

Hope this message finds you well,

As mentioned earlier, we would like to start with quarterly calls to
discuss the direction of cloudstack project.

I propose to split the 90 minute call into 3 topics:

1) Development efforts - 60 minutes
Upcoming Features you are working on developing (to avoid
collision andmaintain the roadmap).
  Depending on number of topics we need to discuss - time for
each topic will be set accordingly.
  If you would like to particiapate - please respond to this
thread and adhere to sample format below:  











   

2) Release Blockers - 20 minutes
  If you would like to participate - please respond to this
thread and adhere to sample format below:  






3) Community Efforts - 10+ minutes





The proposed date and time  - Thursday August 17th 9AM PT.

Minutes will be taken and posted on dev list. Due to number of things we
need to discuss - we have to keep the call very structured, each topic -
timed and very high level.
If there are issues and or suggestions, we will note it down in few
sentences, identify interested parties and have them do a "post"
discussion on the mailing list.

Looking forward to your comments,

Regards,
ilya




daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Recreating SystemVM's

[Daan Hoogland]

Your problem might be like what Swen says, Jeremy but also a wrong systemvm 
offering or a fault in your management network definition.
I am going to sum up some trivialities so bear with me;

What type of networking are you using on the XenServers?
What version of os does the ms run on?
What are the systemvm templates defined in your env?
What is the version of the systemvm.iso?
What is the capacity you have in your (test) environment?
What is the host os version for the hypervisors?
What is the management network range?
What are the other physical networks?
What storage do you use?
Is it reachable from the systemvm?
Is the big bad internet reachable for your SSVM’s public interface?

And of course,

How is the weather, where you are at?

I am not sure any of these question is going to lead you in the right direction 
but one of them should.

On 15/06/17 13:56, "S. Brüseke - proIO GmbH"  wrote:

I once did have some similar problem with my systemvms and my root cause 
was that in the global settings it referred to the wrong systemvm template. I 
am not sure if this helps you, but wanted to tell you.

Mit freundlichen Grüßen / With kind regards,

Swen

-Ursprüngliche Nachricht-
Von: Jeremy Peterson [mailto:jpeter...@acentek.net] 
Gesendet: Donnerstag, 15. Juni 2017 01:55
An: users@cloudstack.apache.org
Betreff: RE: Recreating SystemVM's

Hahaha.  The best response ever. 

I dug through these emails and someone had soft of the same log messages 
cannot attach network and blamed xenserver. Ok I'm cool with that but why oh 
why is it only system vms?

Jeremy

From: Imran Ahmed [im...@eaxiom.net]
Sent: Wednesday, June 14, 2017 6:22 PM
To: users@cloudstack.apache.org
Subject: RE: Recreating SystemVM's

Yes,

-Original Message-
From: Jeremy Peterson [mailto:jpeter...@acentek.net]
Sent: Wednesday, June 14, 2017 9:59 PM
To: users@cloudstack.apache.org
Subject: RE: Recreating SystemVM's

Is there anyone out there reading these messages?

Am I just not seeing responses?

Jeremy


-Original Message-
From: Jeremy Peterson [mailto:jpeter...@acentek.net]
Sent: Wednesday, June 14, 2017 8:12 AM
To: users@cloudstack.apache.org
Subject: RE: Recreating SystemVM's

I opened an issue since this is still an issue.  CLOUDSTACK-9960

Jeremy

-Original Message-
From: Jeremy Peterson [mailto:jpeter...@acentek.net]
Sent: Sunday, June 11, 2017 9:10 AM
To: users@cloudstack.apache.org
Subject: Re: Recreating SystemVM's

Any other suggestions?

I am going to be scheduling to run XenServer updates.  But this all points 
back to CANNOT_ATTACH_NETWORk.

I've verified nothing is active on the Public IP space that those two VM's 
were living on.

Jeremy

From: Jeremy Peterson 
Sent: Friday, June 9, 2017 9:58 AM
To: users@cloudstack.apache.org
Subject: RE: Recreating SystemVM's

I see the vm's try to create on a host that I just removed from maintenance 
mode to install updates and here are the logs

I don't see anything that sticks out to me as a failure message.

Jun  9 09:53:54 Xen3 SM: [13068] ['ip', 'route', 'del', '169.254.0.0/16']
Jun  9 09:53:54 Xen3 SM: [13068]   pread SUCCESS
Jun  9 09:53:54 Xen3 SM: [13068] ['ifconfig', 'xapi12', '169.254.0.1', 
'netmask', '255.255.0.0']
Jun  9 09:53:54 Xen3 SM: [13068]   pread SUCCESS
Jun  9 09:53:54 Xen3 SM: [13068] ['ip', 'route', 'add', '169.254.0.0/16', 
'dev', 'xapi12', 'src', '169.254.0.1']
Jun  9 09:53:54 Xen3 SM: [13068]   pread SUCCESS
Jun  9 09:53:54 Xen3 SM: [13071] ['ip', 'route', 'del', '169.254.0.0/16']
Jun  9 09:53:54 Xen3 SM: [13071]   pread SUCCESS
Jun  9 09:53:54 Xen3 SM: [13071] ['ifconfig', 'xapi12', '169.254.0.1', 
'netmask', '255.255.0.0']
Jun  9 09:53:54 Xen3 SM: [13071]   pread SUCCESS
Jun  9 09:53:54 Xen3 SM: [13071] ['ip', 'route', 'add', '169.254.0.0/16', 
'dev', 'xapi12', 'src', '169.254.0.1']
Jun  9 09:53:54 Xen3 SM: [13071]   pread SUCCESS


Jun  9 09:54:00 Xen3 SM: [13115] on-slave.multi: {'vgName':
'VG_XenStorage-469b6dcd-8466-3d03-de0e-cc3983e1b6e2', 'lvName1':
'VHD-68a7-6c40-4aa6-b88e-c798b6fdc04d', 'action1':
'deactivateNoRefcount', 'action2': 'cleanupLock', 'uuid2':
'68a7-6c40-4aa6-b88e-c798b6fdc04d', 'ns2':
'lvm-469b6dcd-8466-3d03-de0e-cc3983e1b6e2'}
Jun  9 09:54:00 Xen3 SM: [13115] LVMCache created for
VG_XenStorage-469b6dcd-8466-3d03-de0e-cc3983e1b6e2
Jun  9 09:54:00 Xen3 SM: [13115] on-slave.action 1: deactivateNoRefcount Jun
9 09:54:00 Xen3 SM: [13115] LVMCache: will initialize now Jun  9 09:54:00
Xen3 SM: [13115] LVMCache: refreshing Jun  9 09:54:00 Xen3 SM: [13

Re: Retiring OLD Primary Storage - Dealing with System VMs and (assumed) Snapshot related artifacts

[Daan Hoogland]

H David,

I am not licensed to give support on a vendors propriety product, so take all 
of this with a gain of the appropriate crystal;

Ad 1: you are right but migrating to another host should work as well.
Ad 2: There is a table that tells you that a snapshot or image is on a certain 
primary storage but you’ll need to track it there. Easiest is to see if the id 
of the primary storage still occurs in snapshot_store_ref. This as example: 
‘SELECT * FROM snapshot_store_ref WHERE store_id = ”. You 
might want to make sure all looks all right in storage_pool, 
storage_pool_host_ref and storage_pool_work as well. And please keep in mind I 
am looking at ACS 4.5 not CP even though the difference in this area should be 
at most trivial.

On 06/06/2017, 19:10, "David Merrill"  
wrote:

We're in the process of phasing out primary storage in one of our zones and 
had some questions about dealing with: 


1. system VMs (Console Proxy & Secondary Storage) 
2. what looks like (to me), left over snapshot artifacts 

We're running CloudPlatform 4.5.1 with XenServer hypervisors and the 
storage to be retired are Dell Equallogic servers. 

For the first item I think all I need to do is mark the primary storage on 
the Dell EQL's into maintenance mode and then destroy them so that they'll come 
up on the new primary storage (already provisioned & configured in 
CloudPlatform). 

It's the second item that's giving me pause, when looking at the SR 
associated with the primary storage I'm seeing disks named like: 


* ABCServer_ROOT-685_20160905000250 

and in CloudPlatform have found an associated volume snapshot with the same 
date data. This seemed odd because I've understood that volume snapshots should 
be on secondary storage. 

I deleted the snapshot in CloudPlatform thinking that perhaps the disk 
above would disappear from view when looking at the SR in XenCenter, but it's 
still there. The impression I'm getting is that perhaps this is left over from 
some volume snapshot failure to clean up? 

How can I best chase this down? I'd like to retire this storage but I'd 
like to make sure that once it's gone there isn't something in the database 
that's still referring items there. 

Thanks, 
David 

 
A Message From... 
David Merrill - Senior Systems Engineer 


"Uptime. All the time." ® www.reliablenetworks.com 

Fifteen Years In Business 2003 - 2017 

477 Congress Street, Suite 812 | Portland, ME 04101 | ( 207) 772-5678 

private/hybrid cloud hosting | Zimbra groupware | managed services 
proactive maintenance and monitoring | technology consulting 

Maine's only managed services and cloud hosting provider with a 
SOC 2 Type II audit covering Security, Availability and Confidentiality 

This email may contain information that is privileged and confidential. 
If you suspect that you were not intended to receive it, please delete 
it and notify us as soon as possible. Thank you. 



daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: About CloudStack Java samples

[Daan Hoogland]

Ahmet, the apache license doesn’t require you to do that but we would be 
grateful if you do ;)

On 05/05/17 12:40, "Ahmet Orkun Gedik"  wrote:

Perfect! Thank you Rafael, too!!

By the way, I have an additional question. Do I need to put my source code 
to the GitHub or some other site, if I develop commercial product?

Best regards,

Saygılarımla/Best regards/Mit freundlichen Grüßen,

Orkun Gedik
SAP Teknoloji Alan Lideri / SAP Technology Principal Consultant
Veri Merkezi Çözüm ve Hizmetleri / Datacenter Solutions and Services
ERP Uygulamaları Birimi / ERP Applications

KoçSistem Bilgi ve İletişim Hizmetleri A.Ş.
E-Posta: orkun.ge...@kocsistem.com.tr
   ksvm...@kocsistem.com.tr




  



Bilgi Gizlilik  Sınıflandırması   :  Genel Paylaşım
Information  Confidentiality:  Public Use
-Original Message-
From: ma...@exoscale.ch [mailto:ma...@exoscale.ch] 
Sent: Friday, May 5, 2017 1:23 PM
To: users@cloudstack.apache.org
Subject: Re: About CloudStack Java samples

Then Rafael point you to the right direction with the project he mentioned. 
It's a java client library which abstract you from all the http calls to the 
cloudstack API.

--
Exoscale
Av de Provence 4
1007 Lausanne
+41 78 622 42 31
www.exoscale.ch

> On 05 May 2017, at 12:18, Ahmet Orkun Gedik 
 wrote:
> 
> Hi Marco,
> 
> I would like to thank you to lead me to correct direction. I thought that 
there's a standard library to call APIs' on CloudStack.
> 
> I am developing a cloud application on CloudStack framework. As far as I 
understand that I need to develop my own client library to call APIs' on 
CloudStack.
> 
> Thank you for your co-operation.
> 
> Saygılarımla/Best regards/Mit freundlichen Grüßen,
> 
> Orkun Gedik
> SAP Teknoloji Alan Lideri / SAP Technology Principal Consultant Veri 
> Merkezi Çözüm ve Hizmetleri / Datacenter Solutions and Services ERP 
> Uygulamaları Birimi / ERP Applications
> 
> KoçSistem Bilgi ve İletişim Hizmetleri A.Ş.
> E-Posta: orkun.ge...@kocsistem.com.tr
>ksvm...@kocsistem.com.tr
> 
> 
> 
> 
> 
> 
> 
> 
> Bilgi Gizlilik  Sınıflandırması   :  Genel Paylaşım
> Information  Confidentiality:  Public Use
> -Original Message-
> From: ma...@exoscale.ch [mailto:ma...@exoscale.ch]
> Sent: Friday, May 5, 2017 10:48 AM
> To: users@cloudstack.apache.org
> Subject: Re: About CloudStack Java samples
> 
> Hi Orkun!
> 
> There isn't a client java library to call directly cloudstack which is 
not using HTTP calls. I don't think you're going in the right direction with 
your needs. Either you'll be using cloudstack and therefore will expose the 
HTTP API endpoint to work with the management server,. Or you don't need 
cloudstack should maybe work with the hypervisors directly.
> 
> Explain us what you want to do with your cloudstack client library.
> 
> Kind regards
> 
>> On 04 May 2017, at 17:04, Ahmet Orkun Gedik 
 wrote:
>> 
>> Hi Rafael,
>> 
>> Actually, I want to use "com.cloud.*;" library. Do you have any example 
about it?
>> 
>> Saygılarımla/Best regards/Mit freundlichen Grüßen,
>> 
>> Orkun Gedik
>> SAP Teknoloji Alan Lideri / SAP Technology Principal Consultant Veri 
>> Merkezi Çözüm ve Hizmetleri / Datacenter Solutions and Services ERP 
>> Uygulamaları Birimi / ERP Applications
>> 
>> KoçSistem Bilgi ve İletişim Hizmetleri A.Ş.
>> E-Posta: orkun.ge...@kocsistem.com.tr
>>   ksvm...@kocsistem.com.tr
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Bilgi Gizlilik  Sınıflandırması   :  Genel Paylaşım
>> Information  Confidentiality:  Public Use
>> -Original Message-
>> From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
>> Sent: Thursday, May 4, 2017 5:33 PM
>> To: users@cloudstack.apache.org
>> Subject: Re: About CloudStack Java samples
>> 
>> I do not know exactly what you are looking for, but, would something 
like this help you?
>> https://github.com/Autonomiccs/apache-cloudstack-java-client
>> 
>> On Thu, May 4, 2017 at 9:44 AM, Ahmet Orkun Gedik < 
orkun.ge...@kocsistem.com.tr> wrote:
>> 
>>> Hi,
>>> 
>>> I am looking for a sample code with connecting and calling an API by 
>>> using CloudStack Java library. Not looking for an example by calling 
>>> HttpMethod and HttpClient classes.
>>> 
>>> Anyone have a such example?
>>> 
>>> Best regards,
>>> 
>>> Orkun Gedik
>>> 
>>> Bilgi Gizlilik  Sınıflandırması   :  Genel Paylaşım
>>> Information  Confidentiality:  Public Use
>>> [https://www.kocsiste

Re: [VOTE] Retirement of midonet plugin

[Daan Hoogland]

+1

On 28/03/17 22:46, "Rafael Weingärtner"  wrote:

Dear ACS fellows,
We have discussed the retirement of Midonet plugin [*]. After quite some
talk, we converged in a retirement process and it seems that we all agree
that the Midonet plugin should be retired. So, to formalize things, we
should vote Midonet retirement.

All users and devs are welcome to vote here:
[+1] I *do want to retire *the Midonet plugin
[0] Whatever happens I am happy
[-1] I *do not want to retire* the Midonet plugin


[*] http://markmail.org/message/x6p3gnvqbbxcj6gs

--
Rafael Weingärtner



daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Welcoming Wido as the new ACS VP

[Daan Hoogland]

You know that means for beer, right?

On 19/03/17 18:45, "Wido den Hollander"  wrote:

Thank you Will and all!

I'll be present at CCC in Miami this year for a 'official' initiation as VP 
of the CloudStack project :)

Wido 

> Op 16 maart 2017 om 18:00 schreef Will Stevens :
> 
> 
> Hello Everyone,
> It has been a pleasure working with you as the ACS VP over the past year.
> I would like to say Thank You to everyone who has supported me in this 
role
> and have supported the project as a whole.
> 
> It is my pleasure to announce that Wido den Hollander has been voted in to
> replace me as the Apache Cloudstack VP in our annual VP rotation.  Wido 
has
> a long history with the project and we are happy welcome him into this new
> role.
> 
> Be sure to join us at CCC in Miami [1] so we can initiate him correctly
> over many beers.  :)
> 
> Cheers,
> 
> *Will Stevens*
> 
> ​[1] http://us.cloudstackcollab.org/​



daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Welcoming Wido as the new ACS VP

[Daan Hoogland]

Thanks to both of you great Ws. Have a good retirement Will! Good luck in your 
new capacity Wido!

On 17/03/17 08:32, "Paul Angus"  wrote:

Thanks Will for all the great work. And congratulations Wido - good luck.



Kind regards,

Paul Angus

paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Raja Pullela [mailto:raja.pull...@accelerite.com] 
Sent: 17 March 2017 02:59
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Re: Welcoming Wido as the new ACS VP

Thank you Will for all the great work!  

cheers!
Raja Pullela
Engineering Team,
Accelerite, 2055 Laurelwood Road,
Santa Clara, CA, 95054

On 3/16/17, 10:30 PM, "Will Stevens"  wrote:

Hello Everyone,
It has been a pleasure working with you as the ACS VP over the past year.
I would like to say Thank You to everyone who has supported me in this role 
and have supported the project as a whole.

It is my pleasure to announce that Wido den Hollander has been voted in to 
replace me as the Apache Cloudstack VP in our annual VP rotation.  Wido has a 
long history with the project and we are happy welcome him into this new role.

Be sure to join us at CCC in Miami [1] so we can initiate him correctly 
over many beers.  :)

Cheers,

*Will Stevens*

​[1] http://us.cloudstackcollab.org/​





DISCLAIMER
==
This e-mail may contain privileged and confidential information which is 
the property of Accelerite, a Persistent Systems business. It is intended only 
for the use of the individual or entity to which it is addressed. If you are 
not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.



daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue