Re: 4.9 to 4.11 upgrade broken

[Sergey Levitskiy]

Yes. this should bring you back.
However if you perform what you described in your previous reply + rename 
template in CS DB to systemvm-kvm-4.11.1  from what it is now systemvm-kvm-4.11 
you should be able to bring all up as it is. Updating template image is not 
enough.

On 8/21/18, 4:04 PM, "Asai"  wrote:

OK thanks a lot, Sergey,

That helps.  What’s the best method to roll back?  Just use yum to roll 
back to 4.9 and rebuild the DB from backup?


> On Aug 21, 2018, at 3:59 PM, Sergey Levitskiy  wrote:
> 
> The fastest and easiest way is to rollback both DB and management server 
and start over. You need to have correct systemVM template registered before 
you initiate an upgrade.
> 
> Thanks,
> Sergey
> 
> 
> On 8/21/18, 2:30 PM, "Asai"  wrote:
> 
>Is there anybody out there that can assist with this?  
> 
>Asai
> 
> 
>> On Aug 21, 2018, at 2:01 PM, Asai  wrote:
>> 
>> Is there any more specific instruction about this?
>> 
>> What is the best practice?  Should I roll back first?  Is there any 
documentation about rolling back?  Do I uninstall cloudstack management and 
re-install 4.9? 
>> 
>> Or is it as simple as just overwriting the file?  If so, what about the 
template.properties file and the metadata in there like qcow2.size?
>> 
>> filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
>> id=225
>> qcow2.size=316310016
>> public=true
>> uniquename=225-2-826a2950-bb8e-34dd-9420-1eb24ea16b4a
>> qcow2.virtualsize=2516582400
>> virtualsize=2516582400
>> checksum=2d8d1e4eacc976814b97f02849481433
>> hvm=true
>> description=systemvm-kvm-4.11
>> qcow2=true
>> qcow2.filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
>> size=316310016
>> 
>> 
>> Asai
>> 
>> 
>>> On Aug 21, 2018, at 1:56 PM, ilya musayev 
 wrote:
>>> 
>>> yes - please try the proper 4.11 systemvm templates.
>>> 
 On Aug 21, 2018, at 1:54 PM, Asai  wrote:
 
 Can I manually download the systemvm template from here? 
http://download.cloudstack.org/systemvm/4.11/ 

 
 Then manually overwrite it in the filesystem and update it accordingly 
in the database?
 
 Asai
 
 
> On Aug 21, 2018, at 1:40 PM, Asai  wrote:
> 
> 4.11.0
> 
> As outlined in this 
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
 

>> On Aug 21, 2018, at 1:37 PM, ilya musayev 
 wrote:
>> 
>> which template did you use? 
>> 
>>> On Aug 21, 2018, at 1:36 PM, Asai  
wrote:
>>> 
>>> Greetings,
>>> 
>>> I just tried to upgrade from 4.9 to 4.11, but it looks like the 
system VM template I downloaded according to the upgrade guide is the wrong 
template.  It’s 4.11, but I upgraded to 4.11.1 and I get this error message:
>>> 
>>> Caused by: com.cloud.utils.exception.CloudRuntimeException: 
4.11.1.0KVM SystemVm template not found. Cannot upgrade system Vms
>>> at 
com.cloud.upgrade.dao.Upgrade41100to41110.updateSystemVmTemplates(Upgrade41100to41110.java:281)
>>> at 
com.cloud.upgrade.dao.Upgrade41100to41110.performDataMigration(Upgrade41100to41110.java:68)
>>> at 
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:578)
>>> ... 53 more
>>> 2018-08-21 13:28:25,257 INFO  [o.e.j.s.h.ContextHandler] 
(main:null) (logid:) Started 
o.e.j.s.h.MovedContextHandler@15bfd87{/,null,AVAILABLE}
>>> 2018-08-21 13:28:25,317 INFO  [o.e.j.s.AbstractConnector] 
(main:null) (logid:) Started 
ServerConnector@4b1c1ea0{HTTP/1.1,[http/1.1]}{:::8080}
>>> 2018-08-21 13:28:25,318 INFO  [o.e.j.s.Server] (main:null) (logid:) 
Started @20725ms
>>> 
>>> Can anyone assist with getting this corrected?
>>> 
>>> Thank you,
>>> Asai
>>> 
>>> 
>> 
> 
 
>>> 
>> 
> 
> 
> 

Re: 4.9 to 4.11 upgrade broken

[Asai]

OK thanks a lot, Sergey,

That helps.  What’s the best method to roll back?  Just use yum to roll back to 
4.9 and rebuild the DB from backup?


> On Aug 21, 2018, at 3:59 PM, Sergey Levitskiy  wrote:
> 
> The fastest and easiest way is to rollback both DB and management server and 
> start over. You need to have correct systemVM template registered before you 
> initiate an upgrade.
> 
> Thanks,
> Sergey
> 
> 
> On 8/21/18, 2:30 PM, "Asai"  wrote:
> 
>Is there anybody out there that can assist with this?  
> 
>Asai
> 
> 
>> On Aug 21, 2018, at 2:01 PM, Asai  wrote:
>> 
>> Is there any more specific instruction about this?
>> 
>> What is the best practice?  Should I roll back first?  Is there any 
>> documentation about rolling back?  Do I uninstall cloudstack management and 
>> re-install 4.9? 
>> 
>> Or is it as simple as just overwriting the file?  If so, what about the 
>> template.properties file and the metadata in there like qcow2.size?
>> 
>> filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
>> id=225
>> qcow2.size=316310016
>> public=true
>> uniquename=225-2-826a2950-bb8e-34dd-9420-1eb24ea16b4a
>> qcow2.virtualsize=2516582400
>> virtualsize=2516582400
>> checksum=2d8d1e4eacc976814b97f02849481433
>> hvm=true
>> description=systemvm-kvm-4.11
>> qcow2=true
>> qcow2.filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
>> size=316310016
>> 
>> 
>> Asai
>> 
>> 
>>> On Aug 21, 2018, at 1:56 PM, ilya musayev  
>>> wrote:
>>> 
>>> yes - please try the proper 4.11 systemvm templates.
>>> 
 On Aug 21, 2018, at 1:54 PM, Asai  wrote:
 
 Can I manually download the systemvm template from here? 
 http://download.cloudstack.org/systemvm/4.11/ 
 
 
 Then manually overwrite it in the filesystem and update it accordingly in 
 the database?
 
 Asai
 
 
> On Aug 21, 2018, at 1:40 PM, Asai  wrote:
> 
> 4.11.0
> 
> As outlined in this 
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
>  
> 
>> On Aug 21, 2018, at 1:37 PM, ilya musayev  
>> wrote:
>> 
>> which template did you use? 
>> 
>>> On Aug 21, 2018, at 1:36 PM, Asai  wrote:
>>> 
>>> Greetings,
>>> 
>>> I just tried to upgrade from 4.9 to 4.11, but it looks like the system 
>>> VM template I downloaded according to the upgrade guide is the wrong 
>>> template.  It’s 4.11, but I upgraded to 4.11.1 and I get this error 
>>> message:
>>> 
>>> Caused by: com.cloud.utils.exception.CloudRuntimeException: 4.11.1.0KVM 
>>> SystemVm template not found. Cannot upgrade system Vms
>>> at 
>>> com.cloud.upgrade.dao.Upgrade41100to41110.updateSystemVmTemplates(Upgrade41100to41110.java:281)
>>> at 
>>> com.cloud.upgrade.dao.Upgrade41100to41110.performDataMigration(Upgrade41100to41110.java:68)
>>> at 
>>> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:578)
>>> ... 53 more
>>> 2018-08-21 13:28:25,257 INFO  [o.e.j.s.h.ContextHandler] (main:null) 
>>> (logid:) Started o.e.j.s.h.MovedContextHandler@15bfd87{/,null,AVAILABLE}
>>> 2018-08-21 13:28:25,317 INFO  [o.e.j.s.AbstractConnector] (main:null) 
>>> (logid:) Started ServerConnector@4b1c1ea0{HTTP/1.1,[http/1.1]}{:::8080}
>>> 2018-08-21 13:28:25,318 INFO  [o.e.j.s.Server] (main:null) (logid:) 
>>> Started @20725ms
>>> 
>>> Can anyone assist with getting this corrected?
>>> 
>>> Thank you,
>>> Asai
>>> 
>>> 
>> 
> 
 
>>> 
>> 
> 
> 
> 

Re: 4.9 to 4.11 upgrade broken

[Asai]

I have downloaded systemvm4.11.1, unzipped it and put in the proper template 
folder, and renamed it according to the name of the previous template (4.11), 
then I have updated the template.properties file with the proper size in bytes 
and virtual size (using qemu-img info to get virtual size).  I have also 
updated these values in the database as well.

Basically, I don’t want to pull the trigger on this unless I get a go ahead 
from someone who knows what they’re doing.  I don’t want to mess up our VMs.

Thanks for your assistance.


> On Aug 21, 2018, at 2:30 PM, Asai  wrote:
> 
> Is there anybody out there that can assist with this?  
> 
> Asai
> 
> 
>> On Aug 21, 2018, at 2:01 PM, Asai  wrote:
>> 
>> Is there any more specific instruction about this?
>> 
>> What is the best practice?  Should I roll back first?  Is there any 
>> documentation about rolling back?  Do I uninstall cloudstack management and 
>> re-install 4.9? 
>> 
>> Or is it as simple as just overwriting the file?  If so, what about the 
>> template.properties file and the metadata in there like qcow2.size?
>> 
>> filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
>> id=225
>> qcow2.size=316310016
>> public=true
>> uniquename=225-2-826a2950-bb8e-34dd-9420-1eb24ea16b4a
>> qcow2.virtualsize=2516582400
>> virtualsize=2516582400
>> checksum=2d8d1e4eacc976814b97f02849481433
>> hvm=true
>> description=systemvm-kvm-4.11
>> qcow2=true
>> qcow2.filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
>> size=316310016
>> 
>> 
>> Asai
>> 
>> 
>>> On Aug 21, 2018, at 1:56 PM, ilya musayev  
>>> wrote:
>>> 
>>> yes - please try the proper 4.11 systemvm templates.
>>> 
 On Aug 21, 2018, at 1:54 PM, Asai  wrote:
 
 Can I manually download the systemvm template from here? 
 http://download.cloudstack.org/systemvm/4.11/ 
 
 
 Then manually overwrite it in the filesystem and update it accordingly in 
 the database?
 
 Asai
 
 
> On Aug 21, 2018, at 1:40 PM, Asai  wrote:
> 
> 4.11.0
> 
> As outlined in this 
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
>  
> 
>> On Aug 21, 2018, at 1:37 PM, ilya musayev  
>> wrote:
>> 
>> which template did you use? 
>> 
>>> On Aug 21, 2018, at 1:36 PM, Asai  wrote:
>>> 
>>> Greetings,
>>> 
>>> I just tried to upgrade from 4.9 to 4.11, but it looks like the system 
>>> VM template I downloaded according to the upgrade guide is the wrong 
>>> template.  It’s 4.11, but I upgraded to 4.11.1 and I get this error 
>>> message:
>>> 
>>> Caused by: com.cloud.utils.exception.CloudRuntimeException: 4.11.1.0KVM 
>>> SystemVm template not found. Cannot upgrade system Vms
>>> at 
>>> com.cloud.upgrade.dao.Upgrade41100to41110.updateSystemVmTemplates(Upgrade41100to41110.java:281)
>>> at 
>>> com.cloud.upgrade.dao.Upgrade41100to41110.performDataMigration(Upgrade41100to41110.java:68)
>>> at 
>>> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:578)
>>> ... 53 more
>>> 2018-08-21 13:28:25,257 INFO  [o.e.j.s.h.ContextHandler] (main:null) 
>>> (logid:) Started o.e.j.s.h.MovedContextHandler@15bfd87{/,null,AVAILABLE}
>>> 2018-08-21 13:28:25,317 INFO  [o.e.j.s.AbstractConnector] (main:null) 
>>> (logid:) Started ServerConnector@4b1c1ea0{HTTP/1.1,[http/1.1]}{:::8080}
>>> 2018-08-21 13:28:25,318 INFO  [o.e.j.s.Server] (main:null) (logid:) 
>>> Started @20725ms
>>> 
>>> Can anyone assist with getting this corrected?
>>> 
>>> Thank you,
>>> Asai
>>> 
>>> 
>> 
> 
 
>>> 
>> 
> 

Re: 4.9 to 4.11 upgrade broken

[Sergey Levitskiy]

The fastest and easiest way is to rollback both DB and management server and 
start over. You need to have correct systemVM template registered before you 
initiate an upgrade.

Thanks,
Sergey


On 8/21/18, 2:30 PM, "Asai"  wrote:

Is there anybody out there that can assist with this?  

Asai


> On Aug 21, 2018, at 2:01 PM, Asai  wrote:
> 
> Is there any more specific instruction about this?
> 
> What is the best practice?  Should I roll back first?  Is there any 
documentation about rolling back?  Do I uninstall cloudstack management and 
re-install 4.9? 
> 
> Or is it as simple as just overwriting the file?  If so, what about the 
template.properties file and the metadata in there like qcow2.size?
> 
> filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
> id=225
> qcow2.size=316310016
> public=true
> uniquename=225-2-826a2950-bb8e-34dd-9420-1eb24ea16b4a
> qcow2.virtualsize=2516582400
> virtualsize=2516582400
> checksum=2d8d1e4eacc976814b97f02849481433
> hvm=true
> description=systemvm-kvm-4.11
> qcow2=true
> qcow2.filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
> size=316310016
> 
> 
> Asai
> 
> 
>> On Aug 21, 2018, at 1:56 PM, ilya musayev  
wrote:
>> 
>> yes - please try the proper 4.11 systemvm templates.
>> 
>>> On Aug 21, 2018, at 1:54 PM, Asai  wrote:
>>> 
>>> Can I manually download the systemvm template from here? 
http://download.cloudstack.org/systemvm/4.11/ 

>>> 
>>> Then manually overwrite it in the filesystem and update it accordingly 
in the database?
>>> 
>>> Asai
>>> 
>>> 
 On Aug 21, 2018, at 1:40 PM, Asai  wrote:
 
 4.11.0
 
 As outlined in this 
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
 

> On Aug 21, 2018, at 1:37 PM, ilya musayev 
 wrote:
> 
> which template did you use? 
> 
>> On Aug 21, 2018, at 1:36 PM, Asai  wrote:
>> 
>> Greetings,
>> 
>> I just tried to upgrade from 4.9 to 4.11, but it looks like the 
system VM template I downloaded according to the upgrade guide is the wrong 
template.  It’s 4.11, but I upgraded to 4.11.1 and I get this error message:
>> 
>> Caused by: com.cloud.utils.exception.CloudRuntimeException: 
4.11.1.0KVM SystemVm template not found. Cannot upgrade system Vms
>>  at 
com.cloud.upgrade.dao.Upgrade41100to41110.updateSystemVmTemplates(Upgrade41100to41110.java:281)
>>  at 
com.cloud.upgrade.dao.Upgrade41100to41110.performDataMigration(Upgrade41100to41110.java:68)
>>  at 
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:578)
>>  ... 53 more
>> 2018-08-21 13:28:25,257 INFO  [o.e.j.s.h.ContextHandler] (main:null) 
(logid:) Started o.e.j.s.h.MovedContextHandler@15bfd87{/,null,AVAILABLE}
>> 2018-08-21 13:28:25,317 INFO  [o.e.j.s.AbstractConnector] 
(main:null) (logid:) Started 
ServerConnector@4b1c1ea0{HTTP/1.1,[http/1.1]}{:::8080}
>> 2018-08-21 13:28:25,318 INFO  [o.e.j.s.Server] (main:null) (logid:) 
Started @20725ms
>> 
>> Can anyone assist with getting this corrected?
>> 
>> Thank you,
>> Asai
>> 
>> 
> 
 
>>> 
>> 
> 

Re: 4.9 to 4.11 upgrade broken

[Asai]

Is there anybody out there that can assist with this?  

Asai


> On Aug 21, 2018, at 2:01 PM, Asai  wrote:
> 
> Is there any more specific instruction about this?
> 
> What is the best practice?  Should I roll back first?  Is there any 
> documentation about rolling back?  Do I uninstall cloudstack management and 
> re-install 4.9? 
> 
> Or is it as simple as just overwriting the file?  If so, what about the 
> template.properties file and the metadata in there like qcow2.size?
> 
> filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
> id=225
> qcow2.size=316310016
> public=true
> uniquename=225-2-826a2950-bb8e-34dd-9420-1eb24ea16b4a
> qcow2.virtualsize=2516582400
> virtualsize=2516582400
> checksum=2d8d1e4eacc976814b97f02849481433
> hvm=true
> description=systemvm-kvm-4.11
> qcow2=true
> qcow2.filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
> size=316310016
> 
> 
> Asai
> 
> 
>> On Aug 21, 2018, at 1:56 PM, ilya musayev  
>> wrote:
>> 
>> yes - please try the proper 4.11 systemvm templates.
>> 
>>> On Aug 21, 2018, at 1:54 PM, Asai  wrote:
>>> 
>>> Can I manually download the systemvm template from here? 
>>> http://download.cloudstack.org/systemvm/4.11/ 
>>> 
>>> 
>>> Then manually overwrite it in the filesystem and update it accordingly in 
>>> the database?
>>> 
>>> Asai
>>> 
>>> 
 On Aug 21, 2018, at 1:40 PM, Asai  wrote:
 
 4.11.0
 
 As outlined in this 
 http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
  
 
> On Aug 21, 2018, at 1:37 PM, ilya musayev  
> wrote:
> 
> which template did you use? 
> 
>> On Aug 21, 2018, at 1:36 PM, Asai  wrote:
>> 
>> Greetings,
>> 
>> I just tried to upgrade from 4.9 to 4.11, but it looks like the system 
>> VM template I downloaded according to the upgrade guide is the wrong 
>> template.  It’s 4.11, but I upgraded to 4.11.1 and I get this error 
>> message:
>> 
>> Caused by: com.cloud.utils.exception.CloudRuntimeException: 4.11.1.0KVM 
>> SystemVm template not found. Cannot upgrade system Vms
>>  at 
>> com.cloud.upgrade.dao.Upgrade41100to41110.updateSystemVmTemplates(Upgrade41100to41110.java:281)
>>  at 
>> com.cloud.upgrade.dao.Upgrade41100to41110.performDataMigration(Upgrade41100to41110.java:68)
>>  at 
>> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:578)
>>  ... 53 more
>> 2018-08-21 13:28:25,257 INFO  [o.e.j.s.h.ContextHandler] (main:null) 
>> (logid:) Started o.e.j.s.h.MovedContextHandler@15bfd87{/,null,AVAILABLE}
>> 2018-08-21 13:28:25,317 INFO  [o.e.j.s.AbstractConnector] (main:null) 
>> (logid:) Started ServerConnector@4b1c1ea0{HTTP/1.1,[http/1.1]}{:::8080}
>> 2018-08-21 13:28:25,318 INFO  [o.e.j.s.Server] (main:null) (logid:) 
>> Started @20725ms
>> 
>> Can anyone assist with getting this corrected?
>> 
>> Thank you,
>> Asai
>> 
>> 
> 
 
>>> 
>> 
> 

Re: 4.9 to 4.11 upgrade broken

[Asai]

Is there any more specific instruction about this?

What is the best practice?  Should I roll back first?  Is there any 
documentation about rolling back?  Do I uninstall cloudstack management and 
re-install 4.9? 

Or is it as simple as just overwriting the file?  If so, what about the 
template.properties file and the metadata in there like qcow2.size?

filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
id=225
qcow2.size=316310016
public=true
uniquename=225-2-826a2950-bb8e-34dd-9420-1eb24ea16b4a
qcow2.virtualsize=2516582400
virtualsize=2516582400
checksum=2d8d1e4eacc976814b97f02849481433
hvm=true
description=systemvm-kvm-4.11
qcow2=true
qcow2.filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
size=316310016


Asai


> On Aug 21, 2018, at 1:56 PM, ilya musayev  
> wrote:
> 
> yes - please try the proper 4.11 systemvm templates.
> 
>> On Aug 21, 2018, at 1:54 PM, Asai  wrote:
>> 
>> Can I manually download the systemvm template from here? 
>> http://download.cloudstack.org/systemvm/4.11/ 
>> 
>> 
>> Then manually overwrite it in the filesystem and update it accordingly in 
>> the database?
>> 
>> Asai
>> 
>> 
>>> On Aug 21, 2018, at 1:40 PM, Asai  wrote:
>>> 
>>> 4.11.0
>>> 
>>> As outlined in this 
>>> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
>>>  
>>> 
 On Aug 21, 2018, at 1:37 PM, ilya musayev  
 wrote:
 
 which template did you use? 
 
> On Aug 21, 2018, at 1:36 PM, Asai  wrote:
> 
> Greetings,
> 
> I just tried to upgrade from 4.9 to 4.11, but it looks like the system VM 
> template I downloaded according to the upgrade guide is the wrong 
> template.  It’s 4.11, but I upgraded to 4.11.1 and I get this error 
> message:
> 
> Caused by: com.cloud.utils.exception.CloudRuntimeException: 4.11.1.0KVM 
> SystemVm template not found. Cannot upgrade system Vms
>   at 
> com.cloud.upgrade.dao.Upgrade41100to41110.updateSystemVmTemplates(Upgrade41100to41110.java:281)
>   at 
> com.cloud.upgrade.dao.Upgrade41100to41110.performDataMigration(Upgrade41100to41110.java:68)
>   at 
> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:578)
>   ... 53 more
> 2018-08-21 13:28:25,257 INFO  [o.e.j.s.h.ContextHandler] (main:null) 
> (logid:) Started o.e.j.s.h.MovedContextHandler@15bfd87{/,null,AVAILABLE}
> 2018-08-21 13:28:25,317 INFO  [o.e.j.s.AbstractConnector] (main:null) 
> (logid:) Started ServerConnector@4b1c1ea0{HTTP/1.1,[http/1.1]}{:::8080}
> 2018-08-21 13:28:25,318 INFO  [o.e.j.s.Server] (main:null) (logid:) 
> Started @20725ms
> 
> Can anyone assist with getting this corrected?
> 
> Thank you,
> Asai
> 
> 
 
>>> 
>> 
> 

Re: 4.9 to 4.11 upgrade broken

[ilya musayev]

yes - please try the proper 4.11 systemvm templates.

> On Aug 21, 2018, at 1:54 PM, Asai  wrote:
> 
> Can I manually download the systemvm template from here? 
> http://download.cloudstack.org/systemvm/4.11/ 
> 
> 
> Then manually overwrite it in the filesystem and update it accordingly in the 
> database?
> 
> Asai
> 
> 
>> On Aug 21, 2018, at 1:40 PM, Asai  wrote:
>> 
>> 4.11.0
>> 
>> As outlined in this 
>> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
>>  
>> 
>>> On Aug 21, 2018, at 1:37 PM, ilya musayev  
>>> wrote:
>>> 
>>> which template did you use? 
>>> 
 On Aug 21, 2018, at 1:36 PM, Asai  wrote:
 
 Greetings,
 
 I just tried to upgrade from 4.9 to 4.11, but it looks like the system VM 
 template I downloaded according to the upgrade guide is the wrong 
 template.  It’s 4.11, but I upgraded to 4.11.1 and I get this error 
 message:
 
 Caused by: com.cloud.utils.exception.CloudRuntimeException: 4.11.1.0KVM 
 SystemVm template not found. Cannot upgrade system Vms
at 
 com.cloud.upgrade.dao.Upgrade41100to41110.updateSystemVmTemplates(Upgrade41100to41110.java:281)
at 
 com.cloud.upgrade.dao.Upgrade41100to41110.performDataMigration(Upgrade41100to41110.java:68)
at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:578)
... 53 more
 2018-08-21 13:28:25,257 INFO  [o.e.j.s.h.ContextHandler] (main:null) 
 (logid:) Started o.e.j.s.h.MovedContextHandler@15bfd87{/,null,AVAILABLE}
 2018-08-21 13:28:25,317 INFO  [o.e.j.s.AbstractConnector] (main:null) 
 (logid:) Started ServerConnector@4b1c1ea0{HTTP/1.1,[http/1.1]}{:::8080}
 2018-08-21 13:28:25,318 INFO  [o.e.j.s.Server] (main:null) (logid:) 
 Started @20725ms
 
 Can anyone assist with getting this corrected?
 
 Thank you,
 Asai
 
 
>>> 
>> 
> 

Re: 4.9 to 4.11 upgrade broken

[Asai]

Can I manually download the systemvm template from here? 
http://download.cloudstack.org/systemvm/4.11/ 


Then manually overwrite it in the filesystem and update it accordingly in the 
database?

Asai


> On Aug 21, 2018, at 1:40 PM, Asai  wrote:
> 
> 4.11.0
> 
> As outlined in this 
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
>  
> 
>> On Aug 21, 2018, at 1:37 PM, ilya musayev  
>> wrote:
>> 
>> which template did you use? 
>> 
>>> On Aug 21, 2018, at 1:36 PM, Asai  wrote:
>>> 
>>> Greetings,
>>> 
>>> I just tried to upgrade from 4.9 to 4.11, but it looks like the system VM 
>>> template I downloaded according to the upgrade guide is the wrong template. 
>>>  It’s 4.11, but I upgraded to 4.11.1 and I get this error message:
>>> 
>>> Caused by: com.cloud.utils.exception.CloudRuntimeException: 4.11.1.0KVM 
>>> SystemVm template not found. Cannot upgrade system Vms
>>> at 
>>> com.cloud.upgrade.dao.Upgrade41100to41110.updateSystemVmTemplates(Upgrade41100to41110.java:281)
>>> at 
>>> com.cloud.upgrade.dao.Upgrade41100to41110.performDataMigration(Upgrade41100to41110.java:68)
>>> at 
>>> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:578)
>>> ... 53 more
>>> 2018-08-21 13:28:25,257 INFO  [o.e.j.s.h.ContextHandler] (main:null) 
>>> (logid:) Started o.e.j.s.h.MovedContextHandler@15bfd87{/,null,AVAILABLE}
>>> 2018-08-21 13:28:25,317 INFO  [o.e.j.s.AbstractConnector] (main:null) 
>>> (logid:) Started ServerConnector@4b1c1ea0{HTTP/1.1,[http/1.1]}{:::8080}
>>> 2018-08-21 13:28:25,318 INFO  [o.e.j.s.Server] (main:null) (logid:) Started 
>>> @20725ms
>>> 
>>> Can anyone assist with getting this corrected?
>>> 
>>> Thank you,
>>> Asai
>>> 
>>> 
>> 
> 

Re: 4.9 to 4.11 upgrade broken

[Asai]

4.11.0

As outlined in this 
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
 

> On Aug 21, 2018, at 1:37 PM, ilya musayev  
> wrote:
> 
> which template did you use? 
> 
>> On Aug 21, 2018, at 1:36 PM, Asai  wrote:
>> 
>> Greetings,
>> 
>> I just tried to upgrade from 4.9 to 4.11, but it looks like the system VM 
>> template I downloaded according to the upgrade guide is the wrong template.  
>> It’s 4.11, but I upgraded to 4.11.1 and I get this error message:
>> 
>> Caused by: com.cloud.utils.exception.CloudRuntimeException: 4.11.1.0KVM 
>> SystemVm template not found. Cannot upgrade system Vms
>>  at 
>> com.cloud.upgrade.dao.Upgrade41100to41110.updateSystemVmTemplates(Upgrade41100to41110.java:281)
>>  at 
>> com.cloud.upgrade.dao.Upgrade41100to41110.performDataMigration(Upgrade41100to41110.java:68)
>>  at 
>> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:578)
>>  ... 53 more
>> 2018-08-21 13:28:25,257 INFO  [o.e.j.s.h.ContextHandler] (main:null) 
>> (logid:) Started o.e.j.s.h.MovedContextHandler@15bfd87{/,null,AVAILABLE}
>> 2018-08-21 13:28:25,317 INFO  [o.e.j.s.AbstractConnector] (main:null) 
>> (logid:) Started ServerConnector@4b1c1ea0{HTTP/1.1,[http/1.1]}{:::8080}
>> 2018-08-21 13:28:25,318 INFO  [o.e.j.s.Server] (main:null) (logid:) Started 
>> @20725ms
>> 
>> Can anyone assist with getting this corrected?
>> 
>> Thank you,
>> Asai
>> 
>> 
> 

Re: 4.9 to 4.11 upgrade broken

[ilya musayev]

which template did you use? 

> On Aug 21, 2018, at 1:36 PM, Asai  wrote:
> 
> Greetings,
> 
> I just tried to upgrade from 4.9 to 4.11, but it looks like the system VM 
> template I downloaded according to the upgrade guide is the wrong template.  
> It’s 4.11, but I upgraded to 4.11.1 and I get this error message:
> 
> Caused by: com.cloud.utils.exception.CloudRuntimeException: 4.11.1.0KVM 
> SystemVm template not found. Cannot upgrade system Vms
>   at 
> com.cloud.upgrade.dao.Upgrade41100to41110.updateSystemVmTemplates(Upgrade41100to41110.java:281)
>   at 
> com.cloud.upgrade.dao.Upgrade41100to41110.performDataMigration(Upgrade41100to41110.java:68)
>   at 
> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:578)
>   ... 53 more
> 2018-08-21 13:28:25,257 INFO  [o.e.j.s.h.ContextHandler] (main:null) (logid:) 
> Started o.e.j.s.h.MovedContextHandler@15bfd87{/,null,AVAILABLE}
> 2018-08-21 13:28:25,317 INFO  [o.e.j.s.AbstractConnector] (main:null) 
> (logid:) Started ServerConnector@4b1c1ea0{HTTP/1.1,[http/1.1]}{:::8080}
> 2018-08-21 13:28:25,318 INFO  [o.e.j.s.Server] (main:null) (logid:) Started 
> @20725ms
> 
> Can anyone assist with getting this corrected?
> 
> Thank you,
> Asai
> 
> 

4.9 to 4.11 upgrade broken

[Asai]

Greetings,

I just tried to upgrade from 4.9 to 4.11, but it looks like the system VM 
template I downloaded according to the upgrade guide is the wrong template.  
It’s 4.11, but I upgraded to 4.11.1 and I get this error message:

Caused by: com.cloud.utils.exception.CloudRuntimeException: 4.11.1.0KVM 
SystemVm template not found. Cannot upgrade system Vms
at 
com.cloud.upgrade.dao.Upgrade41100to41110.updateSystemVmTemplates(Upgrade41100to41110.java:281)
at 
com.cloud.upgrade.dao.Upgrade41100to41110.performDataMigration(Upgrade41100to41110.java:68)
at 
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:578)
... 53 more
2018-08-21 13:28:25,257 INFO  [o.e.j.s.h.ContextHandler] (main:null) (logid:) 
Started o.e.j.s.h.MovedContextHandler@15bfd87{/,null,AVAILABLE}
2018-08-21 13:28:25,317 INFO  [o.e.j.s.AbstractConnector] (main:null) (logid:) 
Started ServerConnector@4b1c1ea0{HTTP/1.1,[http/1.1]}{:::8080}
2018-08-21 13:28:25,318 INFO  [o.e.j.s.Server] (main:null) (logid:) Started 
@20725ms

Can anyone assist with getting this corrected?

Thank you,
Asai

Re: VMware Support in Cloudstack 4.11.x

[Simon Weller]

You may want to try the shapeblue packages. I believe they are compiled with 
noredist -


https://www.shapeblue.com/packages/

CloudStack Packages - The CloudStack 
Company
www.shapeblue.com
ShapeBlue builds and hosts Apache CloudStack repositories for APT (Debian) and 
YUM (CentOS) based distributions, and Apache CloudStack SystemVM templates.

- Si






From: Netlynker 
Sent: Tuesday, August 21, 2018 5:34 AM
To: users@cloudstack.apache.org
Subject: Re: VMware Support in Cloudstack 4.11.x

Hi Sateesh,

I am using compiled packages from official repository.

So I didn't build the package.

Regards,
Thurein

On Tue, Aug 21, 2018, 6:23 PM Sateesh Chodapuneedi <
sateesh.chodapune...@accelerite.com> wrote:

> Hi Netlynker,
>
> Are you using CloudStack built with option "-Dnoredist" flag?
>
> Regards,
> Sateesh
>
> -Original Message-
> From: Netlynker 
> Reply-To: "users@cloudstack.apache.org" 
> Date: Tuesday, 21 August 2018 at 12:13
> To: "users@cloudstack.apache.org" 
> Subject: Re: VMware Support in Cloudstack 4.11.x
>
> Hi Prashant,
>
> As requested -
>
> 2018-08-21 14:30:22,972 WARN  [c.c.u.n.Link]
> (AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine was
> forced to close inbound due to end of stream.
>
> 2018-08-21 14:30:23,123 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-15:null) (logid:) SeqA 21-16473: Processing Seq
> 21-16473:  { Cmd , MgmtId: -1, via: 21, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCo
>
> mmand":{"_proxyVmId":107,"_loadInfo":"{\n  \"connections\":
> []\n}","wait":0}}] }
>
> 2018-08-21 14:30:23,126 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-15:null) (logid:) SeqA 21-16473: Sending Seq
> 21-16473:  { Ans: , MgmtId: 345050671210, via: 21, Ver: v1, Flags:
> 100010,
> [{"com.cloud.agent.api.AgentControl
>
> Answer":{"result":true,"wait":0}}] }
>
> 2018-08-21 14:30:26,042 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-2:null) (logid:) Ping from 20(s-106-VM)
>
> 2018-08-21 14:30:26,095 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-4:null) (logid:) Ping from 21(v-107-VM)
>
> 2018-08-21 14:30:27,983 WARN  [c.c.u.n.Link]
> (AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine was
> forced to close inbound due to end of stream.
>
> 2018-08-21 14:30:28,618 DEBUG [c.c.a.ApiServlet]
> (qtp1096283470-11:ctx-7d3bac79) (logid:1d893d17) ===START===
> 172.18.2.12
> -- POST
>
> command=addCluster=af21da85-c0b8-4f41-b696-f745764a3d6b=VMware=ExternalM
>
>
> anaged=faed580a-8ca9-4e19-861d-2642a70c6f8f=administrator%40vsphere.local=http%3A%2F%2F* vcenter ip>*%2F%2FCS1-SG1-POD01-VC01= **
> %2F%2FCS1-SG1-POD01-VC01=json
>
> 2018-08-21 14:30:28,621 DEBUG [c.c.a.ApiServer]
> (qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) CIDRs
> from
> which account 'Acct[c1d123b3-9b0b-11e8-b342-0050569fe8e2-admin]' is
> allowed
> to perform API calls: 0.0.0.0/0,::/0
>
> 2018-08-21 14:30:28,628 INFO  [c.c.a.ApiServer]
> (qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) Could not
> find corresponding resource manager for VMware
>
> 2018-08-21 14:30:28,628 DEBUG [c.c.a.ApiServlet]
> (qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) ===END===
> 172.18.2.12 -- POST
>
> command=addCluster=af21da85-c0b8-4f41-b696-f745764a3d6b=VMware=ExternalManaged=faed580a-8ca9-4e19-861d-2642a70c6f8f=administrator%40vsphere.local=http%3A%2F%2F
> **  %2F%2FCS1-SG1-POD01-VC01= * ip>*
> %2F%2FCS1-SG1-POD01-VC01=json
>
> 2018-08-21 14:30:32,356 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl]
> (AsyncJobMgr-Heartbeat-1:ctx-fc56042c) (logid:9a5ce85a) Begin cleanup
> expired async-jobs
>
> 2018-08-21 14:30:32,360 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl]
> (AsyncJobMgr-Heartbeat-1:ctx-fc56042c) (logid:9a5ce85a) End cleanup
> expired
> async-jobs
>
> 2018-08-21 14:30:32,993 WARN  [c.c.u.n.Link]
> (AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine was
> forced to close inbound due to end of stream.
>
> 2018-08-21 14:30:33,123 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-6:null) (logid:) SeqA 21-16475: Processing Seq
> 21-16475:  { Cmd , MgmtId: -1, via: 21, Ver: v1, Flags: 11,
>
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":107,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
>
> 2018-08-21 14:30:33,126 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-6:null) (logid:) SeqA 21-16475: Sending Seq
> 21-16475:  { Ans: , MgmtId: 345050671210, via: 21, Ver: v1, Flags:
> 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}]
> }--
>
>
> Regards,
>
> Thurein Aung
>
> On Tue, Aug 21, 2018 at 2:26 PM Prashant Mishra <
> 

Re: VMware Support in Cloudstack 4.11.x

[Suresh Kumar Anaparti]

Hi Netlynker,

I think compiled packages are not built using -Dnoredist flag.

-Suresh

On Tue, Aug 21, 2018 at 4:05 PM Netlynker  wrote:

> Hi Sateesh,
>
> I am using compiled packages from official repository.
>
> So I didn't build the package.
>
> Regards,
> Thurein
>
> On Tue, Aug 21, 2018, 6:23 PM Sateesh Chodapuneedi <
> sateesh.chodapune...@accelerite.com> wrote:
>
> > Hi Netlynker,
> >
> > Are you using CloudStack built with option "-Dnoredist" flag?
> >
> > Regards,
> > Sateesh
> >
> > -Original Message-
> > From: Netlynker 
> > Reply-To: "users@cloudstack.apache.org" 
> > Date: Tuesday, 21 August 2018 at 12:13
> > To: "users@cloudstack.apache.org" 
> > Subject: Re: VMware Support in Cloudstack 4.11.x
> >
> > Hi Prashant,
> >
> > As requested -
> >
> > 2018-08-21 14:30:22,972 WARN  [c.c.u.n.Link]
> > (AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine
> was
> > forced to close inbound due to end of stream.
> >
> > 2018-08-21 14:30:23,123 DEBUG [c.c.a.m.AgentManagerImpl]
> > (AgentManager-Handler-15:null) (logid:) SeqA 21-16473: Processing Seq
> > 21-16473:  { Cmd , MgmtId: -1, via: 21, Ver: v1, Flags: 11,
> > [{"com.cloud.agent.api.ConsoleProxyLoadReportCo
> >
> > mmand":{"_proxyVmId":107,"_loadInfo":"{\n  \"connections\":
> > []\n}","wait":0}}] }
> >
> > 2018-08-21 14:30:23,126 DEBUG [c.c.a.m.AgentManagerImpl]
> > (AgentManager-Handler-15:null) (logid:) SeqA 21-16473: Sending Seq
> > 21-16473:  { Ans: , MgmtId: 345050671210, via: 21, Ver: v1, Flags:
> > 100010,
> > [{"com.cloud.agent.api.AgentControl
> >
> > Answer":{"result":true,"wait":0}}] }
> >
> > 2018-08-21 14:30:26,042 DEBUG [c.c.a.m.AgentManagerImpl]
> > (AgentManager-Handler-2:null) (logid:) Ping from 20(s-106-VM)
> >
> > 2018-08-21 14:30:26,095 DEBUG [c.c.a.m.AgentManagerImpl]
> > (AgentManager-Handler-4:null) (logid:) Ping from 21(v-107-VM)
> >
> > 2018-08-21 14:30:27,983 WARN  [c.c.u.n.Link]
> > (AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine
> was
> > forced to close inbound due to end of stream.
> >
> > 2018-08-21 14:30:28,618 DEBUG [c.c.a.ApiServlet]
> > (qtp1096283470-11:ctx-7d3bac79) (logid:1d893d17) ===START===
> > 172.18.2.12
> > -- POST
> >
> >
> command=addCluster=af21da85-c0b8-4f41-b696-f745764a3d6b=VMware=ExternalM
> >
> >
> >
> anaged=faed580a-8ca9-4e19-861d-2642a70c6f8f=administrator%40vsphere.local=http%3A%2F%2F* > vcenter ip>*%2F%2FCS1-SG1-POD01-VC01= **
> > %2F%2FCS1-SG1-POD01-VC01=json
> >
> > 2018-08-21 14:30:28,621 DEBUG [c.c.a.ApiServer]
> > (qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) CIDRs
> > from
> > which account 'Acct[c1d123b3-9b0b-11e8-b342-0050569fe8e2-admin]' is
> > allowed
> > to perform API calls: 0.0.0.0/0,::/0
> >
> > 2018-08-21 14:30:28,628 INFO  [c.c.a.ApiServer]
> > (qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) Could
> not
> > find corresponding resource manager for VMware
> >
> > 2018-08-21 14:30:28,628 DEBUG [c.c.a.ApiServlet]
> > (qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17)
> ===END===
> > 172.18.2.12 -- POST
> >
> >
> command=addCluster=af21da85-c0b8-4f41-b696-f745764a3d6b=VMware=ExternalManaged=faed580a-8ca9-4e19-861d-2642a70c6f8f=administrator%40vsphere.local=http%3A%2F%2F
> > **  %2F%2FCS1-SG1-POD01-VC01= * > ip>*
> > %2F%2FCS1-SG1-POD01-VC01=json
> >
> > 2018-08-21 14:30:32,356 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl]
> > (AsyncJobMgr-Heartbeat-1:ctx-fc56042c) (logid:9a5ce85a) Begin cleanup
> > expired async-jobs
> >
> > 2018-08-21 14:30:32,360 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl]
> > (AsyncJobMgr-Heartbeat-1:ctx-fc56042c) (logid:9a5ce85a) End cleanup
> > expired
> > async-jobs
> >
> > 2018-08-21 14:30:32,993 WARN  [c.c.u.n.Link]
> > (AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine
> was
> > forced to close inbound due to end of stream.
> >
> > 2018-08-21 14:30:33,123 DEBUG [c.c.a.m.AgentManagerImpl]
> > (AgentManager-Handler-6:null) (logid:) SeqA 21-16475: Processing Seq
> > 21-16475:  { Cmd , MgmtId: -1, via: 21, Ver: v1, Flags: 11,
> >
> >
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":107,"_loadInfo":"{\n
> > \"connections\": []\n}","wait":0}}] }
> >
> > 2018-08-21 14:30:33,126 DEBUG [c.c.a.m.AgentManagerImpl]
> > (AgentManager-Handler-6:null) (logid:) SeqA 21-16475: Sending Seq
> > 21-16475:  { Ans: , MgmtId: 345050671210, via: 21, Ver: v1, Flags:
> > 100010,
> > [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}]
> > }--
> >
> >
> > Regards,
> >
> > Thurein Aung
> >
> > On Tue, Aug 21, 2018 at 2:26 PM Prashant Mishra <
> > prashant.mis...@accelerite.com> wrote:
> >
> > > Can you please share logs?
> > >
> > > On 8/21/18, 11:54 AM, "Netlynker"  wrote:
> > >
> > > Hi,
> >  

[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: Secondary storage issue with XenServer

[Yordan Kostov]

Please excuse my post.
I think I found the issue. I have deployed cloudstack 4.9 instead of 4.11.

Best regards,
Jordan

From: Yordan Kostov
Sent: Tuesday, August 21, 2018 12:04 PM
To: users@cloudstack.apache.org
Subject: Secondary storage issue with XenServer

Hello everyone,

I recently found about Cloudstack and decided to give it a try 
and I really like it so far but I bumped into a very weird config issue.
Here is my test environment.

10.10.10.200 - XenServer 7.1 host (all free patches installed, 
ntp synced) eth0 is the management and also the only interface connected to the 
network. There are no bonds.

10.10.10.201 - Centos 7 NFS server:
- firewalld disabled
- /etc/exports is:

/cloud_storage/isos *(rw,async,no_root_squash,no_subtree_check)
/cloud_storage/vms *(rw,async,no_root_squash,no_subtree_check)

10.10.10.210 - Cloudstack management server (OS is centos 7, 
ntp synced)
Management network range - 10.10.10.202-209
Guest network range - 10.10.10.211-219
Storage network range - no ips set.
Primary storage is set to use the XenServer 
host local storage.

10.10.10.150 - my PC address in the test network 
(10.10.10.0/24, gate 10.10.10.1)

Zone, pod and cluster and host are created successfully.
But when I try to add secondary NFS server in Cloustack the operation fails.
Going through logs I see the following highlights (full log snipets are 
attached to this mail):

Cloudstack-server.log  -

Line 193: 2018-08-21 11:04:08,865 WARN  
[c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-413:ctx-37d82b72) 
(logid:fac8aabf) createFileSR failed! due to the following: 
SR_BACKEND_FAILURE_61File SR creation error [opterr=fail to mount FileSR. Errno 
is 32]
Line 221: 2018-08-21 11:04:08,865 WARN  
[c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-413:ctx-37d82b72) 
(logid:fac8aabf) Catch Exception 
com.cloud.utils.exception.CloudRuntimeException for template due to 
com.cloud.utils.exception.CloudRuntimeException: createFileSR failed! due to 
the following: SR_BACKEND_FAILURE_61File SR creation error [opterr=fail to 
mount FileSR. Errno is 32]

XenServer SMlog -
Aug 21 11:04:08 cloudstack-office SM: [20645] ['mount', '--bind', 
'/var/cloud_mount/12fb334c-64e6-3206-9373-7ae0627f83d2/template/tmpl/1/1', 
'/var/run/sr-mount/f517ce41-148e-4f88-9bdc-15d7e2d0eaa6']
Aug 21 11:04:08 cloudstack-office SM: [20645] FAILED in util.pread: (rc 32) 
stdout: '', stderr: 'mount: mount 
/var/cloud_mount/12fb334c-64e6-3206-9373-7ae0627f83d2/template/tmpl/1/1 on 
/run/sr-mount/f517ce41-148e-4f88-9bdc-15d7e2d0eaa6 failed: Stale file handle
Aug 21 11:04:08 cloudstack-office SM: [20645] '
Aug 21 11:04:08 cloudstack-office SM: [20645] Raising exception [61, File SR 
creation error [opterr=fail to mount FileSR. Errno is 32]]
Aug 21 11:04:08 cloudstack-office SM: [20645] lock: released 
/var/lock/sm/f517ce41-148e-4f88-9bdc-15d7e2d0eaa6/sr
Aug 21 11:04:08 cloudstack-office SM: [20645] * generic exception: 
sr_attach: EXCEPTION , File SR creation error 
[opterr=fail to mount FileSR. Errno is 32]

XenSever -XenSource.log -
Aug 21 11:05:38 cloudstack-office xapi: [debug|cloudstack-office|109042 UNIX 
/var/lib/xcp/xapi|dispatch:SR.add_to_other_config D:e87a119cfb36|api_effect] 
SR.add_to_other_config
Aug 21 11:05:38 cloudstack-office xapi: [ info|cloudstack-office|109033 
|sm_exec D:143bd363be92|xapi] Session.destroy 
trackid=a5d69dd0a4351c2751078822b0a8844b
Aug 21 11:05:38 cloudstack-office xapi: [error|cloudstack-office|109033 
|SR.attach D:070d838f0344|backtrace] sm_exec D:143bd363be92 failed with 
exception Storage_interface.Backend_error(_)
Aug 21 11:05:38 cloudstack-office xapi: [error|cloudstack-office|109033 
|SR.attach D:070d838f0344|backtrace] Raised Storage_interface.Backend_error(_)
Aug 21 11:05:38 cloudstack-office xapi: [error|cloudstack-office|109033 
|SR.attach D:070d838f0344|backtrace] 1/8 xapi @ cloudstack-office Raised at 
file sm_exec.ml, line 216


What is weird is that I am able to mount the NFS through XenServer -> new 
storage -> NFS wizard (using both NFSv3 and NFSv4 protocols). When added I am 
able to create disks (a.k.a. the host has write access).

Some NFS connection/accessibility tests were run from the XenServer hosts with 
the following results:

-  RPC test
[root@cloudstack-office tmp]# rpcinfo -t 10.10.10.201 nfs
program 13 version 3 ready and waiting
program 13 version 4 ready and waiting


-  Mount scan

[root@cloudstack-office /]# showmount -e 10.10.10.201

Export list for 10.10.10.201:

/cloud_storage/vms  *

/cloud_storage/isos *

Removing IAM services

[Khosrow Moossavi]

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

Re: VMware Support in Cloudstack 4.11.x

[Netlynker]

Hi Sateesh,

I am using compiled packages from official repository.

So I didn't build the package.

Regards,
Thurein

On Tue, Aug 21, 2018, 6:23 PM Sateesh Chodapuneedi <
sateesh.chodapune...@accelerite.com> wrote:

> Hi Netlynker,
>
> Are you using CloudStack built with option "-Dnoredist" flag?
>
> Regards,
> Sateesh
>
> -Original Message-
> From: Netlynker 
> Reply-To: "users@cloudstack.apache.org" 
> Date: Tuesday, 21 August 2018 at 12:13
> To: "users@cloudstack.apache.org" 
> Subject: Re: VMware Support in Cloudstack 4.11.x
>
> Hi Prashant,
>
> As requested -
>
> 2018-08-21 14:30:22,972 WARN  [c.c.u.n.Link]
> (AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine was
> forced to close inbound due to end of stream.
>
> 2018-08-21 14:30:23,123 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-15:null) (logid:) SeqA 21-16473: Processing Seq
> 21-16473:  { Cmd , MgmtId: -1, via: 21, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCo
>
> mmand":{"_proxyVmId":107,"_loadInfo":"{\n  \"connections\":
> []\n}","wait":0}}] }
>
> 2018-08-21 14:30:23,126 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-15:null) (logid:) SeqA 21-16473: Sending Seq
> 21-16473:  { Ans: , MgmtId: 345050671210, via: 21, Ver: v1, Flags:
> 100010,
> [{"com.cloud.agent.api.AgentControl
>
> Answer":{"result":true,"wait":0}}] }
>
> 2018-08-21 14:30:26,042 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-2:null) (logid:) Ping from 20(s-106-VM)
>
> 2018-08-21 14:30:26,095 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-4:null) (logid:) Ping from 21(v-107-VM)
>
> 2018-08-21 14:30:27,983 WARN  [c.c.u.n.Link]
> (AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine was
> forced to close inbound due to end of stream.
>
> 2018-08-21 14:30:28,618 DEBUG [c.c.a.ApiServlet]
> (qtp1096283470-11:ctx-7d3bac79) (logid:1d893d17) ===START===
> 172.18.2.12
> -- POST
>
> command=addCluster=af21da85-c0b8-4f41-b696-f745764a3d6b=VMware=ExternalM
>
>
> anaged=faed580a-8ca9-4e19-861d-2642a70c6f8f=administrator%40vsphere.local=http%3A%2F%2F* vcenter ip>*%2F%2FCS1-SG1-POD01-VC01= **
> %2F%2FCS1-SG1-POD01-VC01=json
>
> 2018-08-21 14:30:28,621 DEBUG [c.c.a.ApiServer]
> (qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) CIDRs
> from
> which account 'Acct[c1d123b3-9b0b-11e8-b342-0050569fe8e2-admin]' is
> allowed
> to perform API calls: 0.0.0.0/0,::/0
>
> 2018-08-21 14:30:28,628 INFO  [c.c.a.ApiServer]
> (qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) Could not
> find corresponding resource manager for VMware
>
> 2018-08-21 14:30:28,628 DEBUG [c.c.a.ApiServlet]
> (qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) ===END===
> 172.18.2.12 -- POST
>
> command=addCluster=af21da85-c0b8-4f41-b696-f745764a3d6b=VMware=ExternalManaged=faed580a-8ca9-4e19-861d-2642a70c6f8f=administrator%40vsphere.local=http%3A%2F%2F
> **  %2F%2FCS1-SG1-POD01-VC01= * ip>*
> %2F%2FCS1-SG1-POD01-VC01=json
>
> 2018-08-21 14:30:32,356 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl]
> (AsyncJobMgr-Heartbeat-1:ctx-fc56042c) (logid:9a5ce85a) Begin cleanup
> expired async-jobs
>
> 2018-08-21 14:30:32,360 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl]
> (AsyncJobMgr-Heartbeat-1:ctx-fc56042c) (logid:9a5ce85a) End cleanup
> expired
> async-jobs
>
> 2018-08-21 14:30:32,993 WARN  [c.c.u.n.Link]
> (AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine was
> forced to close inbound due to end of stream.
>
> 2018-08-21 14:30:33,123 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-6:null) (logid:) SeqA 21-16475: Processing Seq
> 21-16475:  { Cmd , MgmtId: -1, via: 21, Ver: v1, Flags: 11,
>
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":107,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
>
> 2018-08-21 14:30:33,126 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-6:null) (logid:) SeqA 21-16475: Sending Seq
> 21-16475:  { Ans: , MgmtId: 345050671210, via: 21, Ver: v1, Flags:
> 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}]
> }--
>
>
> Regards,
>
> Thurein Aung
>
> On Tue, Aug 21, 2018 at 2:26 PM Prashant Mishra <
> prashant.mis...@accelerite.com> wrote:
>
> > Can you please share logs?
> >
> > On 8/21/18, 11:54 AM, "Netlynker"  wrote:
> >
> > Hi,
> >
> > I have installed Cloudstack 4.11.1 from official Apache
> repository. I
> > can't
> > add VMware in my Cloudstack infrastructure.
> >
> > May I know how I can achieve that?
> >
> >
> > Thanks in advance,
> >
> >
> > DISCLAIMER
> > ==
> > This e-mail may contain privileged and confidential information
> which is
> > the 

Re: CloudStack DNS names to PowerDNS export

[Rubens Malheiro]

Hey Ivan! Thanks! Good job! This is extremely necessary for me.
✓Cloudstack

On Tue, Aug 21, 2018, 4:18 AM Daan Hoogland  wrote:

> 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 <
> kudryavtsev...@bw-sw.com>
> 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: VMware Support in Cloudstack 4.11.x

[Sateesh Chodapuneedi]

Hi Netlynker,

Are you using CloudStack built with option "-Dnoredist" flag?

Regards,
Sateesh
 
-Original Message-
From: Netlynker 
Reply-To: "users@cloudstack.apache.org" 
Date: Tuesday, 21 August 2018 at 12:13
To: "users@cloudstack.apache.org" 
Subject: Re: VMware Support in Cloudstack 4.11.x

Hi Prashant,

As requested -

2018-08-21 14:30:22,972 WARN  [c.c.u.n.Link]
(AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine was
forced to close inbound due to end of stream.

2018-08-21 14:30:23,123 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-15:null) (logid:) SeqA 21-16473: Processing Seq
21-16473:  { Cmd , MgmtId: -1, via: 21, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.ConsoleProxyLoadReportCo

mmand":{"_proxyVmId":107,"_loadInfo":"{\n  \"connections\":
[]\n}","wait":0}}] }

2018-08-21 14:30:23,126 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-15:null) (logid:) SeqA 21-16473: Sending Seq
21-16473:  { Ans: , MgmtId: 345050671210, via: 21, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControl

Answer":{"result":true,"wait":0}}] }

2018-08-21 14:30:26,042 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-2:null) (logid:) Ping from 20(s-106-VM)

2018-08-21 14:30:26,095 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-4:null) (logid:) Ping from 21(v-107-VM)

2018-08-21 14:30:27,983 WARN  [c.c.u.n.Link]
(AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine was
forced to close inbound due to end of stream.

2018-08-21 14:30:28,618 DEBUG [c.c.a.ApiServlet]
(qtp1096283470-11:ctx-7d3bac79) (logid:1d893d17) ===START===  172.18.2.12
-- POST

command=addCluster=af21da85-c0b8-4f41-b696-f745764a3d6b=VMware=ExternalM


anaged=faed580a-8ca9-4e19-861d-2642a70c6f8f=administrator%40vsphere.local=http%3A%2F%2F**%2F%2FCS1-SG1-POD01-VC01= **
%2F%2FCS1-SG1-POD01-VC01=json

2018-08-21 14:30:28,621 DEBUG [c.c.a.ApiServer]
(qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) CIDRs from
which account 'Acct[c1d123b3-9b0b-11e8-b342-0050569fe8e2-admin]' is allowed
to perform API calls: 0.0.0.0/0,::/0

2018-08-21 14:30:28,628 INFO  [c.c.a.ApiServer]
(qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) Could not
find corresponding resource manager for VMware

2018-08-21 14:30:28,628 DEBUG [c.c.a.ApiServlet]
(qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) ===END===
172.18.2.12 -- POST

command=addCluster=af21da85-c0b8-4f41-b696-f745764a3d6b=VMware=ExternalManaged=faed580a-8ca9-4e19-861d-2642a70c6f8f=administrator%40vsphere.local=http%3A%2F%2F
**  %2F%2FCS1-SG1-POD01-VC01= **
%2F%2FCS1-SG1-POD01-VC01=json

2018-08-21 14:30:32,356 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-fc56042c) (logid:9a5ce85a) Begin cleanup
expired async-jobs

2018-08-21 14:30:32,360 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-fc56042c) (logid:9a5ce85a) End cleanup expired
async-jobs

2018-08-21 14:30:32,993 WARN  [c.c.u.n.Link]
(AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine was
forced to close inbound due to end of stream.

2018-08-21 14:30:33,123 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-6:null) (logid:) SeqA 21-16475: Processing Seq
21-16475:  { Cmd , MgmtId: -1, via: 21, Ver: v1, Flags: 11,

[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":107,"_loadInfo":"{\n
\"connections\": []\n}","wait":0}}] }

2018-08-21 14:30:33,126 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-6:null) (logid:) SeqA 21-16475: Sending Seq
21-16475:  { Ans: , MgmtId: 345050671210, via: 21, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }--


Regards,

Thurein Aung

On Tue, Aug 21, 2018 at 2:26 PM Prashant Mishra <
prashant.mis...@accelerite.com> wrote:

> Can you please share logs?
>
> On 8/21/18, 11:54 AM, "Netlynker"  wrote:
>
> Hi,
>
> I have installed Cloudstack 4.11.1 from official Apache repository. I
> can't
> add VMware in my Cloudstack infrastructure.
>
> May I know how I can achieve that?
>
>
> Thanks in advance,
>
>
> 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 

Secondary storage issue with XenServer

[Yordan Kostov]

Hello everyone,

I recently found about Cloudstack and decided to give it a try 
and I really like it so far but I bumped into a very weird config issue.
Here is my test environment.

10.10.10.200 - XenServer 7.1 host (all free patches installed, 
ntp synced) eth0 is the management and also the only interface connected to the 
network. There are no bonds.

10.10.10.201 - Centos 7 NFS server:
- firewalld disabled
- /etc/exports is:

/cloud_storage/isos *(rw,async,no_root_squash,no_subtree_check)
/cloud_storage/vms *(rw,async,no_root_squash,no_subtree_check)

10.10.10.210 - Cloudstack management server (OS is centos 7, 
ntp synced)
Management network range - 10.10.10.202-209
Guest network range - 10.10.10.211-219
Storage network range - no ips set.
Primary storage is set to use the XenServer 
host local storage.

10.10.10.150 - my PC address in the test network 
(10.10.10.0/24, gate 10.10.10.1)

Zone, pod and cluster and host are created successfully.
But when I try to add secondary NFS server in Cloustack the operation fails.
Going through logs I see the following highlights (full log snipets are 
attached to this mail):

Cloudstack-server.log  -

Line 193: 2018-08-21 11:04:08,865 WARN  
[c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-413:ctx-37d82b72) 
(logid:fac8aabf) createFileSR failed! due to the following: 
SR_BACKEND_FAILURE_61File SR creation error [opterr=fail to mount FileSR. Errno 
is 32]
Line 221: 2018-08-21 11:04:08,865 WARN  
[c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-413:ctx-37d82b72) 
(logid:fac8aabf) Catch Exception 
com.cloud.utils.exception.CloudRuntimeException for template due to 
com.cloud.utils.exception.CloudRuntimeException: createFileSR failed! due to 
the following: SR_BACKEND_FAILURE_61File SR creation error [opterr=fail to 
mount FileSR. Errno is 32]

XenServer SMlog -
Aug 21 11:04:08 cloudstack-office SM: [20645] ['mount', '--bind', 
'/var/cloud_mount/12fb334c-64e6-3206-9373-7ae0627f83d2/template/tmpl/1/1', 
'/var/run/sr-mount/f517ce41-148e-4f88-9bdc-15d7e2d0eaa6']
Aug 21 11:04:08 cloudstack-office SM: [20645] FAILED in util.pread: (rc 32) 
stdout: '', stderr: 'mount: mount 
/var/cloud_mount/12fb334c-64e6-3206-9373-7ae0627f83d2/template/tmpl/1/1 on 
/run/sr-mount/f517ce41-148e-4f88-9bdc-15d7e2d0eaa6 failed: Stale file handle
Aug 21 11:04:08 cloudstack-office SM: [20645] '
Aug 21 11:04:08 cloudstack-office SM: [20645] Raising exception [61, File SR 
creation error [opterr=fail to mount FileSR. Errno is 32]]
Aug 21 11:04:08 cloudstack-office SM: [20645] lock: released 
/var/lock/sm/f517ce41-148e-4f88-9bdc-15d7e2d0eaa6/sr
Aug 21 11:04:08 cloudstack-office SM: [20645] * generic exception: 
sr_attach: EXCEPTION , File SR creation error 
[opterr=fail to mount FileSR. Errno is 32]

XenSever -XenSource.log -
Aug 21 11:05:38 cloudstack-office xapi: [debug|cloudstack-office|109042 UNIX 
/var/lib/xcp/xapi|dispatch:SR.add_to_other_config D:e87a119cfb36|api_effect] 
SR.add_to_other_config
Aug 21 11:05:38 cloudstack-office xapi: [ info|cloudstack-office|109033 
|sm_exec D:143bd363be92|xapi] Session.destroy 
trackid=a5d69dd0a4351c2751078822b0a8844b
Aug 21 11:05:38 cloudstack-office xapi: [error|cloudstack-office|109033 
|SR.attach D:070d838f0344|backtrace] sm_exec D:143bd363be92 failed with 
exception Storage_interface.Backend_error(_)
Aug 21 11:05:38 cloudstack-office xapi: [error|cloudstack-office|109033 
|SR.attach D:070d838f0344|backtrace] Raised Storage_interface.Backend_error(_)
Aug 21 11:05:38 cloudstack-office xapi: [error|cloudstack-office|109033 
|SR.attach D:070d838f0344|backtrace] 1/8 xapi @ cloudstack-office Raised at 
file sm_exec.ml, line 216


What is weird is that I am able to mount the NFS through XenServer -> new 
storage -> NFS wizard (using both NFSv3 and NFSv4 protocols). When added I am 
able to create disks (a.k.a. the host has write access).

Some NFS connection/accessibility tests were run from the XenServer hosts with 
the following results:

-  RPC test
[root@cloudstack-office tmp]# rpcinfo -t 10.10.10.201 nfs
program 13 version 3 ready and waiting
program 13 version 4 ready and waiting


-  Mount scan

[root@cloudstack-office /]# showmount -e 10.10.10.201

Export list for 10.10.10.201:

/cloud_storage/vms  *

/cloud_storage/isos *



Note: both of those work manually but not through cloudstack



-  NFS sr-proble returns this for both shares:
[root@cloudstack-office tmp]# xe sr-probe type=nfs 
device-config:server=10.10.10.201 device-config:serverpath=/cloud_storage/vms



 

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: VMware Support in Cloudstack 4.11.x

[Netlynker]

Hi Prashant,

As requested -

2018-08-21 14:30:22,972 WARN  [c.c.u.n.Link]
(AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine was
forced to close inbound due to end of stream.

2018-08-21 14:30:23,123 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-15:null) (logid:) SeqA 21-16473: Processing Seq
21-16473:  { Cmd , MgmtId: -1, via: 21, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.ConsoleProxyLoadReportCo

mmand":{"_proxyVmId":107,"_loadInfo":"{\n  \"connections\":
[]\n}","wait":0}}] }

2018-08-21 14:30:23,126 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-15:null) (logid:) SeqA 21-16473: Sending Seq
21-16473:  { Ans: , MgmtId: 345050671210, via: 21, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControl

Answer":{"result":true,"wait":0}}] }

2018-08-21 14:30:26,042 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-2:null) (logid:) Ping from 20(s-106-VM)

2018-08-21 14:30:26,095 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-4:null) (logid:) Ping from 21(v-107-VM)

2018-08-21 14:30:27,983 WARN  [c.c.u.n.Link]
(AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine was
forced to close inbound due to end of stream.

2018-08-21 14:30:28,618 DEBUG [c.c.a.ApiServlet]
(qtp1096283470-11:ctx-7d3bac79) (logid:1d893d17) ===START===  172.18.2.12
-- POST
command=addCluster=af21da85-c0b8-4f41-b696-f745764a3d6b=VMware=ExternalM

anaged=faed580a-8ca9-4e19-861d-2642a70c6f8f=administrator%40vsphere.local=http%3A%2F%2F**%2F%2FCS1-SG1-POD01-VC01= **
%2F%2FCS1-SG1-POD01-VC01=json

2018-08-21 14:30:28,621 DEBUG [c.c.a.ApiServer]
(qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) CIDRs from
which account 'Acct[c1d123b3-9b0b-11e8-b342-0050569fe8e2-admin]' is allowed
to perform API calls: 0.0.0.0/0,::/0

2018-08-21 14:30:28,628 INFO  [c.c.a.ApiServer]
(qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) Could not
find corresponding resource manager for VMware

2018-08-21 14:30:28,628 DEBUG [c.c.a.ApiServlet]
(qtp1096283470-11:ctx-7d3bac79 ctx-f68a5270) (logid:1d893d17) ===END===
172.18.2.12 -- POST
command=addCluster=af21da85-c0b8-4f41-b696-f745764a3d6b=VMware=ExternalManaged=faed580a-8ca9-4e19-861d-2642a70c6f8f=administrator%40vsphere.local=http%3A%2F%2F
**  %2F%2FCS1-SG1-POD01-VC01= **
%2F%2FCS1-SG1-POD01-VC01=json

2018-08-21 14:30:32,356 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-fc56042c) (logid:9a5ce85a) Begin cleanup
expired async-jobs

2018-08-21 14:30:32,360 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-fc56042c) (logid:9a5ce85a) End cleanup expired
async-jobs

2018-08-21 14:30:32,993 WARN  [c.c.u.n.Link]
(AgentManager-SSLHandshakeHandler-2:null) (logid:) This SSL engine was
forced to close inbound due to end of stream.

2018-08-21 14:30:33,123 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-6:null) (logid:) SeqA 21-16475: Processing Seq
21-16475:  { Cmd , MgmtId: -1, via: 21, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":107,"_loadInfo":"{\n
\"connections\": []\n}","wait":0}}] }

2018-08-21 14:30:33,126 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-6:null) (logid:) SeqA 21-16475: Sending Seq
21-16475:  { Ans: , MgmtId: 345050671210, via: 21, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }--


Regards,

Thurein Aung

On Tue, Aug 21, 2018 at 2:26 PM Prashant Mishra <
prashant.mis...@accelerite.com> wrote:

> Can you please share logs?
>
> On 8/21/18, 11:54 AM, "Netlynker"  wrote:
>
> Hi,
>
> I have installed Cloudstack 4.11.1 from official Apache repository. I
> can't
> add VMware in my Cloudstack infrastructure.
>
> May I know how I can achieve that?
>
>
> Thanks in advance,
>
>
> 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.
>

Re: VMware Support in Cloudstack 4.11.x

[Prashant Mishra]

Can you please share logs?

On 8/21/18, 11:54 AM, "Netlynker"  wrote:

Hi,

I have installed Cloudstack 4.11.1 from official Apache repository. I can't
add VMware in my Cloudstack infrastructure.

May I know how I can achieve that?


Thanks in advance,


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.

VMware Support in Cloudstack 4.11.x

[Netlynker]

Hi,

I have installed Cloudstack 4.11.1 from official Apache repository. I can't
add VMware in my Cloudstack infrastructure.

May I know how I can achieve that?


Thanks in advance,