Re: CS 4.12 logs
Main one: /var/log/cloudstack/management/management-server.log On Thu, 16 May 2019 at 23:43, Alessandro Caviglione wrote: > Hi guys, > I've just upgraded from CS 4.9 to 4.12 but I cannot see any "running" logs. > In 4.9 I remember logs was in catalina.log file, but now I can't see any > logging activities. > Is there any other file I've to check? > -- Andrija Panić
CS 4.12 logs
Hi guys, I've just upgraded from CS 4.9 to 4.12 but I cannot see any "running" logs. In 4.9 I remember logs was in catalina.log file, but now I can't see any logging activities. Is there any other file I've to check?
Re: Add KVM host
Alejandro, Also could you check if your cloudstack-agent was updated on the host post upgrade? Regards, Anurag From: Andrija Panic Sent: Thursday, May 16, 2019 10:40 AM To: users Subject: Re: Add KVM host Alejandro, can you please paste the whole management log and also agent log files (pastebin or similar, not here). Best, Andrija On Wed, 15 May 2019 at 21:09, Alejandro Ruiz Bermejo < arbermejo0...@gmail.com> wrote: > hi, > I'm setting up CloudStack 4.12. I've already deployed the management > server, and right now i'm adding the first KVM Host but it is giving me > errors. I already recondigured everything and read the guidelines on the > official docs site. > > This is the output of *grep -i -E > 'exception|unable|fail|invalid|leak|warn|error' > /var/log/cloudstack/management/management-server.log* > > 2019-05-15 10:59:28,507 WARN [c.c.a.d.ParamGenericValidationWorker] > (qtp858242339-256:ctx-1c43c232 ctx-b610) (logid:02d95edb) Received > unknown parameters for command addHost. Unknown parameters : clustertype > 2019-05-15 10:59:33,105 WARN [c.c.h.k.d.LibvirtServerDiscoverer] > (qtp858242339-256:ctx-1c43c232 ctx-b610) (logid:02d95edb) can't setup > agent, due to com.cloud.utils.exception.CloudRuntimeException: Failed to > setup keystore on the KVM host: 10.8.9.236 - Failed to setup keystore on > the KVM host: 10.8.9.236 > 2019-05-15 10:59:33,106 WARN [c.c.r.ResourceManagerImpl] > (qtp858242339-256:ctx-1c43c232 ctx-b610) (logid:02d95edb) Unable to > find the server resources at http://10.8.9.236 > 2019-05-15 10:59:33,106 INFO [c.c.u.e.CSExceptionErrorCode] > (qtp858242339-256:ctx-1c43c232 ctx-b610) (logid:02d95edb) Could not > find exception: com.cloud.exception.DiscoveryException in error code list > for exceptions > 2019-05-15 10:59:33,106 WARN [o.a.c.a.c.a.h.AddHostCmd] > (qtp858242339-256:ctx-1c43c232 ctx-b610) (logid:02d95edb) Exception: > com.cloud.exception.DiscoveryException: Unable to add the host > 2019-05-15 10:59:33,108 INFO [c.c.a.ApiServer] > (qtp858242339-256:ctx-1c43c232 ctx-b610) (logid:02d95edb) Unable to add > the host > -- Andrija Panić anurag.awas...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
Re: Changing the NIC and disk controller type permanently
> $ cloudstack addResourceDetail "details[0].key=rootDiskController" > "details[0].value=lsisas1068" "resourcetype=UserVm" "resourceid=$id" Note: lsisas1068 comes from https://github.com/apache/cloudstack/blob/4.11.2.0/vmware-base/src/com/cloud/hypervisor/vmware/mo/ScsiDiskControllerType.java We had set this to lsilogicsas previously (on CS 4.5), which causes the following exception on start on CS 4.11.2.0: com.cloud.utils.exception.CloudRuntimeException: Invalid root disk controller detected : none at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResou rce.java:1690) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(Vmwa reResource.java:496) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgen tAttache.java:315) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(Mana gedContextRunnable.java:49) ...
Changing the NIC and disk controller type permanently
Hi, This is an old topic, [1] but it looks like behaviour changed in newer CloudStack versions. What is the recommended procedure to change the NIC and disk controller types of an existing VM (in stopped state)? We used $ cloudstack addResourceDetail "details[0].key=rootDiskController" "details[0].value=lsisas1068" "resourcetype=UserVm" "resourceid=$id" and cloudstack addResourceDetail "details[0].key=nicAdapter" "details[0].value=Vmxnet3" "resourcetype=UserVm" "resourceid=$id" ( cloudstack = https://github.com/exoscale/cs ) This seemed to be effective for the network adapter, but not for the disk controller. The VM was booted with the lsiscsi (LSI Logic Parallel SCSI driver). Any help would be much appreciated, as these settings are necessary for booting Windows Server 201X on VMware ESX. Note: we're running ESX 5.5. Thanks! [1] http://mail-archives.apache.org/mod_mbox/cloudstack-users/201409.mbox/%3c54213b18.7020...@gmail.com%3e
Re: Ansible 2.8: CloudStack related changes
Huge props René! Ian Rae CEO | PDG c: 514.944.4008 CloudOps | Cloud Platform and Networking Solutions www.cloudops.com | 423 Saint-Nicolas | Montreal | Canada On Thu, May 16, 2019 at 9:28 AM Tutkowski, Mike wrote: > Thanks, Rene, for all of the work you've done for CloudStack! > > > From: Rene Moser > Sent: Thursday, May 16, 2019 1:42 AM > To: users@cloudstack.apache.org; dev > Subject: Ansible 2.8: CloudStack related changes > > NetApp Security WARNING: This is an external email. Do not click links or > open attachments unless you recognize the sender and know the content is > safe. > > > > > Hi all > > As announced previously in autumn 2018, I am ending my active > maintenance for the CloudStack Ansible integration with the 2.8 release. > > It started as PoC during a weekend at a Swiss Linux hackers event > "Turrican Days" in autumn 2014 and turned into "thing" I have spent many > nights with. Take care of it. > > The modules are in best conditions: Cloudstack is one of a few Ansible > integrations without any failing sanity checks. Special thanks goes to > David Passante who brought all the docs in shape! > > We have automated integration tests based on a simulator docker setup > [1] currently running Cloudstack 4.11.2. The integration test code > coverage [2] is at >85%. > > There are currently (only) 2 more members in the CloudStack team [3] in > Ansible. > > Thanks again for all the support and appreciation I have received over > the years. > > Ansible v2.8.0 is going to be released with the following, CloudStack > related changes, thanks for all the contributors: > > David Passante (18): > Cloudstack: fix support for some VPC service capabilities (#45727) > cs_account: Implement role parameter support (#46166) > cs_account: add ability to bind accounts to LDAP (#46219) > Cloudstack: New module cs_vlan_ip_range (#51597) > cloudstack: streamline modules doc (#52509) > cloudstack: streamline modules doc (part 2) (#52730) > cloudstack: streamline modules doc (part 3) (#53412) > cs_iso: fix missing param "is_public" (#53740) > cs_network_offering: Add choice list for supported_services in > arg_spec (#53901) > cloudstack: streamline modules doc (part 4) (#53874) > cs_volume: add volumes extraction and upload features (#54111) > cs_instance_facts: add a "nic" fact to return VM networking > information (#54337) > cs_service_offering: update params in arg spec and documentation > (#54511) > cs_network_offering: add a for_vpc parameter (#54551) > cloudstack: streamline modules doc (part 5) (#54523) > cs_service_offering: Implement customizable compute offers (#54597) > cloudstack: streamline modules doc (part 6) (#54641) > cs_vlan_ip_range: Update return values documentation (#54677) > > Gregor Riepl (1): > Cloudstack: Add password reset module (#47931) > > Patryk D. Cichy (5): > Add new Cloudstack module cs_image_store (#53617) > Add new CloudStack module cs_physical_network (#54098) > Add a new CloudStack module - cs_traffic_type (#54451) > Enable adding VLAN IP ranges for Physical Networks (#54576) > Proper handling of lower case name for InternalLbVm Service > Provider (#55087) > > Rene Moser (13): > cs_loadbalancer_rule_member: fix error handling (#46012) > cs_instance: fix host migration without volume (#46115) > cs_instance: doc: fix typo in examples (#46035) > cs_staticnat: fix sanity (#46037) > cs_ip_address: use query_api, fixes error handling (#46034) > cs_resourcelimit: use query_api for error handling (#46036) > cs_ip_address: fix vpc and network mutually exclusive (#47846) > cs_network_acl_rule: fix doc and sanity (#47835) > cs_template: fix KeyError on state=extracted (#48675) > cs_instance: fix typos in defaults for ip/ip6_ipaddress (#49064) > cs_physical_network: use name as param for network (#54602) > cloudstack: fix E326 (#54657) > > This will be my last announcement and I most probably leaving the > cloudstack mailing lists in the next couple of days. > > Best wishes > René > > [1] https://github.com/ansible/cloudstack-test-container > [2] > > https://codecov.io/gh/ansible/ansible/tree/devel/lib/ansible/modules/cloud/cloudstack > [3] > > https://github.com/ansible/ansible/blob/0e0735f10ecb64634a4a1c9ac78a36743295417d/.github/BOTMETA.yml#L1471 >
Re: Ansible 2.8: CloudStack related changes
Thanks, Rene, for all of the work you've done for CloudStack! From: Rene Moser Sent: Thursday, May 16, 2019 1:42 AM To: users@cloudstack.apache.org; dev Subject: Ansible 2.8: CloudStack related changes NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi all As announced previously in autumn 2018, I am ending my active maintenance for the CloudStack Ansible integration with the 2.8 release. It started as PoC during a weekend at a Swiss Linux hackers event "Turrican Days" in autumn 2014 and turned into "thing" I have spent many nights with. Take care of it. The modules are in best conditions: Cloudstack is one of a few Ansible integrations without any failing sanity checks. Special thanks goes to David Passante who brought all the docs in shape! We have automated integration tests based on a simulator docker setup [1] currently running Cloudstack 4.11.2. The integration test code coverage [2] is at >85%. There are currently (only) 2 more members in the CloudStack team [3] in Ansible. Thanks again for all the support and appreciation I have received over the years. Ansible v2.8.0 is going to be released with the following, CloudStack related changes, thanks for all the contributors: David Passante (18): Cloudstack: fix support for some VPC service capabilities (#45727) cs_account: Implement role parameter support (#46166) cs_account: add ability to bind accounts to LDAP (#46219) Cloudstack: New module cs_vlan_ip_range (#51597) cloudstack: streamline modules doc (#52509) cloudstack: streamline modules doc (part 2) (#52730) cloudstack: streamline modules doc (part 3) (#53412) cs_iso: fix missing param "is_public" (#53740) cs_network_offering: Add choice list for supported_services in arg_spec (#53901) cloudstack: streamline modules doc (part 4) (#53874) cs_volume: add volumes extraction and upload features (#54111) cs_instance_facts: add a "nic" fact to return VM networking information (#54337) cs_service_offering: update params in arg spec and documentation (#54511) cs_network_offering: add a for_vpc parameter (#54551) cloudstack: streamline modules doc (part 5) (#54523) cs_service_offering: Implement customizable compute offers (#54597) cloudstack: streamline modules doc (part 6) (#54641) cs_vlan_ip_range: Update return values documentation (#54677) Gregor Riepl (1): Cloudstack: Add password reset module (#47931) Patryk D. Cichy (5): Add new Cloudstack module cs_image_store (#53617) Add new CloudStack module cs_physical_network (#54098) Add a new CloudStack module - cs_traffic_type (#54451) Enable adding VLAN IP ranges for Physical Networks (#54576) Proper handling of lower case name for InternalLbVm Service Provider (#55087) Rene Moser (13): cs_loadbalancer_rule_member: fix error handling (#46012) cs_instance: fix host migration without volume (#46115) cs_instance: doc: fix typo in examples (#46035) cs_staticnat: fix sanity (#46037) cs_ip_address: use query_api, fixes error handling (#46034) cs_resourcelimit: use query_api for error handling (#46036) cs_ip_address: fix vpc and network mutually exclusive (#47846) cs_network_acl_rule: fix doc and sanity (#47835) cs_template: fix KeyError on state=extracted (#48675) cs_instance: fix typos in defaults for ip/ip6_ipaddress (#49064) cs_physical_network: use name as param for network (#54602) cloudstack: fix E326 (#54657) This will be my last announcement and I most probably leaving the cloudstack mailing lists in the next couple of days. Best wishes René [1] https://github.com/ansible/cloudstack-test-container [2] https://codecov.io/gh/ansible/ansible/tree/devel/lib/ansible/modules/cloud/cloudstack [3] https://github.com/ansible/ansible/blob/0e0735f10ecb64634a4a1c9ac78a36743295417d/.github/BOTMETA.yml#L1471
RE: Ansible 2.8: CloudStack related changes
Sorry to hear that Rene - thanks for your massive contributions over the years and good luck for the future Kind regards Giles giles.sir...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue -Original Message- From: Rene Moser Sent: 16 May 2019 13:12 To: users@cloudstack.apache.org; dev Subject: Ansible 2.8: CloudStack related changes Hi all As announced previously in autumn 2018, I am ending my active maintenance for the CloudStack Ansible integration with the 2.8 release. It started as PoC during a weekend at a Swiss Linux hackers event "Turrican Days" in autumn 2014 and turned into "thing" I have spent many nights with. Take care of it. The modules are in best conditions: Cloudstack is one of a few Ansible integrations without any failing sanity checks. Special thanks goes to David Passante who brought all the docs in shape! We have automated integration tests based on a simulator docker setup [1] currently running Cloudstack 4.11.2. The integration test code coverage [2] is at >85%. There are currently (only) 2 more members in the CloudStack team [3] in Ansible. Thanks again for all the support and appreciation I have received over the years. Ansible v2.8.0 is going to be released with the following, CloudStack related changes, thanks for all the contributors: David Passante (18): Cloudstack: fix support for some VPC service capabilities (#45727) cs_account: Implement role parameter support (#46166) cs_account: add ability to bind accounts to LDAP (#46219) Cloudstack: New module cs_vlan_ip_range (#51597) cloudstack: streamline modules doc (#52509) cloudstack: streamline modules doc (part 2) (#52730) cloudstack: streamline modules doc (part 3) (#53412) cs_iso: fix missing param "is_public" (#53740) cs_network_offering: Add choice list for supported_services in arg_spec (#53901) cloudstack: streamline modules doc (part 4) (#53874) cs_volume: add volumes extraction and upload features (#54111) cs_instance_facts: add a "nic" fact to return VM networking information (#54337) cs_service_offering: update params in arg spec and documentation (#54511) cs_network_offering: add a for_vpc parameter (#54551) cloudstack: streamline modules doc (part 5) (#54523) cs_service_offering: Implement customizable compute offers (#54597) cloudstack: streamline modules doc (part 6) (#54641) cs_vlan_ip_range: Update return values documentation (#54677) Gregor Riepl (1): Cloudstack: Add password reset module (#47931) Patryk D. Cichy (5): Add new Cloudstack module cs_image_store (#53617) Add new CloudStack module cs_physical_network (#54098) Add a new CloudStack module - cs_traffic_type (#54451) Enable adding VLAN IP ranges for Physical Networks (#54576) Proper handling of lower case name for InternalLbVm Service Provider (#55087) Rene Moser (13): cs_loadbalancer_rule_member: fix error handling (#46012) cs_instance: fix host migration without volume (#46115) cs_instance: doc: fix typo in examples (#46035) cs_staticnat: fix sanity (#46037) cs_ip_address: use query_api, fixes error handling (#46034) cs_resourcelimit: use query_api for error handling (#46036) cs_ip_address: fix vpc and network mutually exclusive (#47846) cs_network_acl_rule: fix doc and sanity (#47835) cs_template: fix KeyError on state=extracted (#48675) cs_instance: fix typos in defaults for ip/ip6_ipaddress (#49064) cs_physical_network: use name as param for network (#54602) cloudstack: fix E326 (#54657) This will be my last announcement and I most probably leaving the cloudstack mailing lists in the next couple of days. Best wishes René [1] https://github.com/ansible/cloudstack-test-container [2] https://codecov.io/gh/ansible/ansible/tree/devel/lib/ansible/modules/cloud/cloudstack [3] https://github.com/ansible/ansible/blob/0e0735f10ecb64634a4a1c9ac78a36743295417d/.github/BOTMETA.yml#L1471
Ansible 2.8: CloudStack related changes
Hi all As announced previously in autumn 2018, I am ending my active maintenance for the CloudStack Ansible integration with the 2.8 release. It started as PoC during a weekend at a Swiss Linux hackers event "Turrican Days" in autumn 2014 and turned into "thing" I have spent many nights with. Take care of it. The modules are in best conditions: Cloudstack is one of a few Ansible integrations without any failing sanity checks. Special thanks goes to David Passante who brought all the docs in shape! We have automated integration tests based on a simulator docker setup [1] currently running Cloudstack 4.11.2. The integration test code coverage [2] is at >85%. There are currently (only) 2 more members in the CloudStack team [3] in Ansible. Thanks again for all the support and appreciation I have received over the years. Ansible v2.8.0 is going to be released with the following, CloudStack related changes, thanks for all the contributors: David Passante (18): Cloudstack: fix support for some VPC service capabilities (#45727) cs_account: Implement role parameter support (#46166) cs_account: add ability to bind accounts to LDAP (#46219) Cloudstack: New module cs_vlan_ip_range (#51597) cloudstack: streamline modules doc (#52509) cloudstack: streamline modules doc (part 2) (#52730) cloudstack: streamline modules doc (part 3) (#53412) cs_iso: fix missing param "is_public" (#53740) cs_network_offering: Add choice list for supported_services in arg_spec (#53901) cloudstack: streamline modules doc (part 4) (#53874) cs_volume: add volumes extraction and upload features (#54111) cs_instance_facts: add a "nic" fact to return VM networking information (#54337) cs_service_offering: update params in arg spec and documentation (#54511) cs_network_offering: add a for_vpc parameter (#54551) cloudstack: streamline modules doc (part 5) (#54523) cs_service_offering: Implement customizable compute offers (#54597) cloudstack: streamline modules doc (part 6) (#54641) cs_vlan_ip_range: Update return values documentation (#54677) Gregor Riepl (1): Cloudstack: Add password reset module (#47931) Patryk D. Cichy (5): Add new Cloudstack module cs_image_store (#53617) Add new CloudStack module cs_physical_network (#54098) Add a new CloudStack module - cs_traffic_type (#54451) Enable adding VLAN IP ranges for Physical Networks (#54576) Proper handling of lower case name for InternalLbVm Service Provider (#55087) Rene Moser (13): cs_loadbalancer_rule_member: fix error handling (#46012) cs_instance: fix host migration without volume (#46115) cs_instance: doc: fix typo in examples (#46035) cs_staticnat: fix sanity (#46037) cs_ip_address: use query_api, fixes error handling (#46034) cs_resourcelimit: use query_api for error handling (#46036) cs_ip_address: fix vpc and network mutually exclusive (#47846) cs_network_acl_rule: fix doc and sanity (#47835) cs_template: fix KeyError on state=extracted (#48675) cs_instance: fix typos in defaults for ip/ip6_ipaddress (#49064) cs_physical_network: use name as param for network (#54602) cloudstack: fix E326 (#54657) This will be my last announcement and I most probably leaving the cloudstack mailing lists in the next couple of days. Best wishes René [1] https://github.com/ansible/cloudstack-test-container [2] https://codecov.io/gh/ansible/ansible/tree/devel/lib/ansible/modules/cloud/cloudstack [3] https://github.com/ansible/ansible/blob/0e0735f10ecb64634a4a1c9ac78a36743295417d/.github/BOTMETA.yml#L1471
Re: dynamically scalable of kvm
Hi, No, CloudStack does not support this at the moment afaik. You will need to Stop and Start the VM to scale it. Wido On 5/10/19 6:40 AM, li jerry wrote: > HI All > > Does CLOUDSTACK now support dynamic scalable of KVM? I found that KVM was > already supported. > >
