Re: listApis does not match with specific responds

[Harikrishna Patnala]

Hi,

listAPI response in general gives all the parameters present in the 
corresponding resource respond object (In this case it is DomainResponse).

For listDomainChildren API, only few response parameters are set in the 
DomainResponse. This can be improved by generating the response using database 
views.

You can later call listDomain API to list all the parameters. Also please feel 
free to create a new improvement ticket 
https://github.com/apache/cloudstack/issues/new for this.

Thanks,
Harikrishna

From: R A 
Date: Thursday, 19 September 2024 at 9:04 AM
To: users@cloudstack.apache.org 
Subject: listApis does not match with specific responds
Hi guys,

when i call

http://X:8080/client/api?command=listDomainChildren&response=json

then I will get many fields. These fields are also mentioned in the cloudstack 
api documentation.

But calling the listDomainChildren Endpoint results in a much fewer set of 
fields.

I am logged in as the root admin.

Can someone explain why there is such a big mismatch?

http://X:8080/client/api?command=listDomainChildren&response=json

{
"listdomainchildrenresponse": {
"count": 3,
"domain": [
{
"id": "ac64fb70-1490-4705-8591-539b17b7b8df",
"name": "testdomain2",
"level": 1,
"parentdomainid": "6170bb3d-439f-11ef-9de9-000babff3656",
"parentdomainname": "ROOT",
"haschild": false,
"networkdomain": "testdomain.local",
"path": "ROOT/testdomain2",
"created": "2024-07-17T15:41:40+0200",
"secondarystoragetotal": 0.0
},
{
"id": "f95d8676-8158-4aca-87fd-998e9ada35e3",
"name": "cloud",
"level": 1,
"parentdomainid": "6170bb3d-439f-11ef-9de9-000babff3656",
"parentdomainname": "ROOT",
"haschild": true,
"path": "ROOT/cloud",
"created": "2024-07-20T02:47:02+0200",
"secondarystoragetotal": 0.0
},
{
"id": "6b68b473-f6aa-4ce6-9acb-53e62c1355d4",
"name": "domeahmed",
"level": 1,
"parentdomainid": "6170bb3d-439f-11ef-9de9-000babff3656",
"parentdomainname": "ROOT",
"haschild": false,
"path": "ROOT/domeahmed",
"created": "2024-07-30T16:55:57+0200",
"secondarystoragetotal": 0.0
}
]
}
}




And this is what listApis does provide for listDomainChildren

http://XX:8080/client/api?command=listApis&name=listDomainChildren&response=json

{
"listapisresponse": {
"count": 1,
"api": [
{
"name": "listDomainChildren",
"description": "Lists all children domains belonging to a 
specified domain",
"isasync": false,
"related": "listDomains",
"params": [
{
"name": "showicon",
"description": "flag to display the resource icon for 
domains",
"type": "boolean",
"length": 255,
"required": false
},
{
"name": "id",
"description": "list children domain by parent domain 
ID.",
"type": "uuid",
"length": 255,
"required": false,
"related": "listDomainChildren,listDomains"
},
{
"name": "keyword",
"description": "List by keyword",
"type": "string",
"length": 255,
"required": false
},
{
"name": "isrecursive",
"description": "to return the entire tree, use the 
value \"true\". To return the first level children, use the value \"false\".",
"type": "boolean",
"length": 255,
"required": false
},
{
"name": "listall",
"description": "If set to false, list only resources 
belonging to the command's caller; if set to true - list resources that the 
caller is authorized to see. Default value is false",
"type": "boolean",
"length": 255,
"required": false
},
{
"name": "page",
"description": "",
"type": "integer",
"length": 255,
  

Re: New PMC member: Suresh Anaparti

[Harikrishna Patnala]

Congratulations Suresh!

Regards,
Harikrishna

From: Rohit Yadav 
Date: Wednesday, 18 September 2024 at 4:22 PM
To: dev , users 
Subject: New PMC member: Suresh Anaparti
The Project Management Committee (PMC) for Apache CloudStack
has invited Suresh Anaparti to become a PMC member and we are pleased
to announce that they have accepted.

Suresh has contributed in the past and has shown effort to make the
project run smoothly. He also has served as the release manager for
CloudStack releases 4.16.1.0 and 4.19.1.0.

Please join me in congratulating Suresh

Regards,
Rohit Yadav

 

Re: [VOTE] Apache CloudStack 4.19.1.0 (RC2)

[Harikrishna Patnala]

+1 (binding)

Tested my usual operations in a VMware environment, with NFS storages and 
Datastore cluster storages. Tried VM, volume lifecycle operations and storage 
related options like using storage policies and applying them on the volumes.

Regards,
Harikrishna

From: Suresh Kumar Anaparti 
Date: Monday, 15 July 2024 at 7:14 PM
To: dev , users 
Subject: [VOTE] Apache CloudStack 4.19.1.0 (RC2)
Hi All,

I have created a 4.19.1.0 release (RC2), with the following artifacts up
for testing and a vote:

Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.19.1.0-RC20240715T1719
Commit: 9f4c8959743d2f53faae6fc5d68e88ddc20e21a3

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.19.1.0/

PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until 18th July 2024.

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)

For users convenience, the packages from this release candidate (RC2) and
4.19.1.0 systemvm templates are available here:
https://download.cloudstack.org/testing/4.19.1.0-RC2/
https://download.cloudstack.org/systemvm/4.19/

Regards,
Suresh

 

Re: New Committer: Kiran Chavala

[Harikrishna Patnala]

Congratulations Kiran, well deserved.

Regards,
Harikrishna
 



From: Rohit Yadav 
Sent: Tuesday, April 9, 2024 11:15 AM
To: dev 
Subject: New Committer: Kiran Chavala

The Project Management Committee (PMC) for Apache CloudStack
has invited Kiran Chavala (kiranchavala) to become a committer and
we are pleased to announce that they have accepted.

Kiran has been a long time CloudStack contributor and has created
over a hundred issues on Github. Being a committer enables easier
contribution to the project and enable better productivity.

Please join me in congratulating Kiran!

Regards.

Re: [VOTE] Release Apache CloudStack Terraform Provider v0.5.0

[Harikrishna Patnala]

+1 (binding), tested using my old configurations and they worked without any 
issues.

Thanks everyone involved here.

Regards,
Harikrishna
 



From: Jithin Raju 
Sent: Monday, April 8, 2024 2:54 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [VOTE] Release Apache CloudStack Terraform Provider v0.5.0

+1 based on my tests.

-Jithin

From: Boris Stoyanov 
Date: Monday, 8 April 2024 at 2:53 PM
To: users@cloudstack.apache.org , 
d...@cloudstack.apache.org 
Subject: Re: [VOTE] Release Apache CloudStack Terraform Provider v0.5.0
+1 (binding), based on Kiran’s testing.

Bobby.

From: Kiran Chavala 
Date: Thursday, 4 April 2024 at 9:30
To: d...@cloudstack.apache.org , 
users@cloudstack.apache.org 
Subject: Re: [VOTE] Release Apache CloudStack Terraform Provider v0.5.0
Hi All,

Reminder – terraform 0.5.0  is up for testing and voting.

Regards.
Kiran

From: Rohit Yadav 
Date: Wednesday, 3 April 2024 at 9:43 AM
To: d...@cloudstack.apache.org , 
users@cloudstack.apache.org 
Subject: Re: [VOTE] Release Apache CloudStack Terraform Provider v0.5.0
+1 (binding)

Tested vm deployment using 0.5.0-pre.

Regards.













From: Kiran Chavala 
Sent: Tuesday, April 2, 2024 2:55:40 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: [VOTE] Release Apache CloudStack Terraform Provider v0.5.0

Hi ALL

I've created a CloudStack Terraform Provider v0.5.0 release, with the following 
artifacts up for a vote:

Git Branch and Commit SH:

https://github.com/cloudstack/terraform-provider-cloudstack

Commit: 7c682bf17bebf40837a30ebcca811fc7b8785a15

Source release (checksums and signatures are available at the same location):
https://dist.apache.org/repos/dist/dev/cloudstack/terraform-provider-0.5.0/

PGP release keys (signed using E03379CB066175FAC2BC9E027B3F1C5E93F97FAB):
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)

For users convenience, they can use this 0.5.0-pre build 
https://registry.terraform.io/providers/cloudstack/cloudstack/0.5.0-pre for 
testing purposes.
The binaries are here: 
https://github.com/apache/cloudstack-terraform-provider/releases/tag/v0.5.0-pre


Regards
Kiran Chavala

Re: [VOTE] Release Apache CloudStack CloudMonkey 6.4.0 - RC1

[Harikrishna Patnala]

+1 Binding

Verified the checksums of the binaries and tried my usual operations of adding 
host, templates, deploying instances and few more and those seems fine.

Thank you everyone involved here.

Regards,
Harikrishna

From: Boris Stoyanov 
Date: Wednesday, 27 March 2024 at 1:55 PM
To: d...@cloudstack.apache.org , users 

Subject: Re: [VOTE] Release Apache CloudStack CloudMonkey 6.4.0 - RC1
+1 Binding,

I’ve installed the client locally and did some ops around, listing creating and 
updating resources. I could not find any issues.

Bobby.

From: Rohit Yadav 
Date: Thursday, 21 March 2024 at 12:39
To: dev , users 
Subject: [VOTE] Release Apache CloudStack CloudMonkey 6.4.0 - RC1
Hi All,

I've created a v6.4.0 release of CloudMonkey, with the following
artifacts up for a vote:

Git Branch and commit SHA:
https://github.com/apache/cloudstack-cloudmonkey/commit/df65df7cfe331c5af5d39743717e3d58df921a48

Commit:
df65df7cfe331c5af5d39743717e3d58df921a48

GitHub pre-release (contains changelog,
artifacts/binaries to test, checksums/usage details):
https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.4.0

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-6.4.0/

PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884)
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until 27th March, 2024.

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 the reason why)

Convenience binaries are available from here:
https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.4.0

Regards.



 

Re: Volatile VM disks?

[Harikrishna Patnala]

Previous link may not open for you, please check this snippet

https://github.com/apache/cloudstack/blob/2df68021761adbd93eecda20114894c8f2edb8bd/server/src/main/java/com/cloud/vm/UserVmManagerImpl.java#L3239-L3248



From: Harikrishna Patnala 
Date: Monday, 18 March 2024 at 9:19 AM
To: users@cloudstack.apache.org 
Subject: Re: Volatile VM disks?
Hi Leo,

Here is the code snippet which handles the volume reset on reboot VM. 
https://github.com/shapeblue/cloudstack/blob/2df68021761adbd93eecda20114894c8f2edb8bd/server/src/main/java/com/cloud/vm/UserVmManagerImpl.java#L3239-L3248

May I know how did you test the volume reset, please try reboot after having 
some data in the volume which is created after the volume creation. From UI if 
you look at the volume name and details there won’t be any change, it’s the 
data which gets reset inside the volume.

Thanks,
Harikrishna

From: Leo Leung 
Date: Saturday, 16 March 2024 at 2:50 AM
To: users@cloudstack.apache.org 
Subject: Volatile VM disks?
Hello everyone,

I am trying to use the 'volatile VM' feature. According to the documentation, 
it should "have their root disks reset upon reboot".

I created a new compute offering with 'volatile' enabled and then deployed a VM 
on a KVM node using a template image. The VM root disk is not resetting on 
shutdown/reboot.  I looked through the CloudStack source code but don't see 
anything obvious as to what would make the disks reset on shutdown/reboot.

Is there something else I need to do to make this work? Is this a feature only 
on specific hypervisors?

Thank-you,
-Leo



 

Re: Volatile VM disks?

[Harikrishna Patnala]

Hi Leo,

Here is the code snippet which handles the volume reset on reboot VM. 
https://github.com/shapeblue/cloudstack/blob/2df68021761adbd93eecda20114894c8f2edb8bd/server/src/main/java/com/cloud/vm/UserVmManagerImpl.java#L3239-L3248

May I know how did you test the volume reset, please try reboot after having 
some data in the volume which is created after the volume creation. From UI if 
you look at the volume name and details there won’t be any change, it’s the 
data which gets reset inside the volume.

Thanks,
Harikrishna

From: Leo Leung 
Date: Saturday, 16 March 2024 at 2:50 AM
To: users@cloudstack.apache.org 
Subject: Volatile VM disks?
Hello everyone,

I am trying to use the 'volatile VM' feature. According to the documentation, 
it should "have their root disks reset upon reboot".

I created a new compute offering with 'volatile' enabled and then deployed a VM 
on a KVM node using a template image. The VM root disk is not resetting on 
shutdown/reboot.  I looked through the CloudStack source code but don't see 
anything obvious as to what would make the disks reset on shutdown/reboot.

Is there something else I need to do to make this work? Is this a feature only 
on specific hypervisors?

Thank-you,
-Leo

 

Re: 2FA for admin user

[Harikrishna Patnala]

Hi Jimmy,

Here is the document related to 2FA having all related details how to enable 
and disable 2FA.

http://docs.cloudstack.apache.org/en/latest/adminguide/accounts.html#using-two-factor-authentication-for-users

If you are an user and if you have logged in, then go to right top >> click on 
user profile >> In the action icons you can see the action to enable or disable 
2FA

If you are an admin and want to disable to disable 2FA for other users, you can 
go to the Accounts >> specific user >> In the action icons you can see the 
action to disable 2FA for that user.

In the above document there is a note mentioning the way to disable using 
“user” table in the database, please check if it can help.

Regards,
Harikrishna


From: Jimmy Huybrechts 
Date: Thursday, 14 March 2024 at 4:18 PM
To: users@cloudstack.apache.org 
Subject: 2FA for admin user
Hi,

I want to enable 2FA for admin user as well for security, but in case for some 
reason this stops working, gets lost or whatever the reason may be. Is there a 
way we can remove it so you can login again?
We have physical access to the servers of course.

--
Jimmy

 

Re: new committer: Vishesh Jindal (vishesh)

[Harikrishna Patnala]

Congrats Vishesh!

Regards,
Harikrishna

From: Daan Hoogland 
Date: Monday, 26 February 2024 at 7:35 PM
To: users , dev 
Subject: new committer: Vishesh Jindal (vishesh)
users and devs,

The Project Management Committee (PMC) for Apache CloudStack
has invited Vishesh Jindal to become a committer and we are pleased
to announce that they have accepted.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.

Please join me in congratulating Vishesh.

--
on behalf of the PMC, Daan

 

Re: Update Password For Existing XEN Host

[Harikrishna Patnala]

I see there is an API for this

https://cloudstack.apache.org/api/apidocs-4.19/apis/updateHostPassword.html

Can you please try that

Regards,
Harikrishna

From: Joan g 
Date: Wednesday, 14 February 2024 at 7:22 PM
To: users@cloudstack.apache.org 
Subject: Update Password For Existing XEN Host
Hello Community,

My cloudstack Setup is  Using Xen server. Due to security reasons i was
forced to change my xen root password.

Can someone let me know how I can update the password for my host in
cloudstack DB ?

Following blow link does not help
http://docs.cloudstack.apache.org/projects/archived-cloudstack-administration/en/latest/hosts.html#changing-host-password

Regards,
Joan

 

Re: [PROPOSE] RM for 4.19.1.0

[Harikrishna Patnala]

Thanks for volunteering Suresh.

Regards,
Harikrishna

From: Suresh Anaparti 
Date: Monday, 12 February 2024 at 5:20 PM
To: d...@cloudstack.apache.org , 
users@cloudstack.apache.org 
Subject: [PROPOSE] RM for 4.19.1.0
Hi All,

CloudStack 4.19.0.0 is the latest LTS release. There are already some open 
issues [1]  and pull requests [2] targeted for 4.19.1.0 [3] release.

I'd like to propose and put myself forward as the release manager for 4.19.1.0 
if no objections there. Please ping me (@sureshanaparti) on GitHub, in case you 
want to include any Issue/PR in 4.19.1.0.

I propose to have a window of at least 8 weeks (2 months), which allows the 
community / users to test, use 4.19.0.0 and report any issues. We can aim to 
cut RC1 in Q2 2024 (maybe, sometime in May-2024). I'll propose the timeline 
details soon. I hope to have your support.

Please let me know if you have any thoughts/comments.

[1] 
https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.19.1.0
[2] 
https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.19.1.0+is%3Aopen
[3] https://github.com/apache/cloudstack/milestone/31


Regards,
Suresh



 

DeployDB failing on main

[Harikrishna Patnala]

Hi,

On main (I think on 4.19 also) there is an issue seen when deploying database 
using the command “mvn -Pdeveloper -pl developer -Ddeploydb”


> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker

[WARNING]

java.lang.reflect.InvocationTargetException

at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)

at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke (Method.java:566)

at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:297)

at java.lang.Thread.run (Thread.java:834)

Caused by: java.lang.NullPointerException

at java.io.Reader. (Reader.java:167)

at java.io.InputStreamReader. (InputStreamReader.java:72)

at com.cloud.upgrade.DatabaseUpgradeChecker.runScript 
(DatabaseUpgradeChecker.java:234)

at com.cloud.upgrade.DatabaseUpgradeChecker.executeViewScripts 
(DatabaseUpgradeChecker.java:388)


When I checked the code with debugger, I see NPE here

https://github.com/apache/cloudstack/blob/d353fcc599d1c1e2ca4b58c6b793bcaf515a3f34/engine/schema/src/main/java/com/cloud/upgrade/DatabaseUpgradeChecker.java#L387-L388

here viewScript is null. This is happening when filePath is 
“/META-INF/db/views/cloud.service_offering_view.sql”. When I remove the initial 
back slash using the debugger 
“META-INF/db/views/cloud.service_offering_view.sql”, it has continued and 
deployDB has passed.

Guto or anybody here, any idea why this is happening or am I missing anything ?

Thanks,
Harikrishna

 

Re: UI - change name of secondary storage and management server

[Harikrishna Patnala]

I’ve quickly checked the references and I don’t see major issues we can change 
the name in mshost table.
But please test it and keep an eye with multiple scenarios may be in your test 
environment if you have.

Thanks,
Harikrishna

From: W. Verleger - proIO GmbH 
Date: Monday, 5 February 2024 at 2:18 PM
To: users@cloudstack.apache.org 
Subject: AW: UI - change name of secondary storage and management server
Hi Harikrishna,

Thank you, I will take a look!
Does this also work with the "mshost" table (for the management server).
Do you know of any limitations or dependencies regarding an update of those 
values?

Best regards,
Wilken

 


-Ursprüngliche Nachricht-
Von: Harikrishna Patnala 
Gesendet: Montag, 5. Februar 2024 04:55
An: users@cloudstack.apache.org
Betreff: Re: UI - change name of secondary storage and management server

Hi Wilken,

This API does not have that parameter to edit the name, it´s a good thing to 
add. You will have to go and edit the name in the database table 
"image_storage" for the column "name".

Thanks,
Harikrishna

From: W. Verleger - proIO GmbH 
Date: Thursday, 1 February 2024 at 10:02 PM
To: users@cloudstack.apache.org 
Subject: UI - change name of secondary storage and management server

Hi guys,


Is there an easy way to change the name of the secondary storage and management 
server in CS 4.18.1.0 via UI / API call seen under:


Infrastructure --> Secondary storage --> "Name"
Infrastructure --> Management servers --> "Name"


Is there an API call?

Something like this but with more options?

https://cloudstack.apache.org/api/apidocs-4.18/apis/updateImageStore.html


Thank you!


Best regards,
Wilken


- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error) 
please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden.





- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error) 
please notify
the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden.

Re: Migrate a VM to another compute offering

[Harikrishna Patnala]

To me this looks like an improvement but also contradicting the way we use the 
host tags in the compute offerings. May be we can have a force option while 
changing the compute offering to ignore the host tags if this is a widely used 
case.
Or I see a valid workaround in another thread by intermittently changing the 
offering to an offering that has no tags.

Regards,
Harikrishna

From: Daan Hoogland 
Date: Thursday, 1 February 2024 at 3:55 PM
To: users@cloudstack.apache.org 
Subject: Re: Migrate a VM to another compute offering
makes sense @swen. if you don't want the user to be aware of the
placements policies.

On Thu, Feb 1, 2024 at 10:20 AM  wrote:
>
> Hi Daan,
>
> thx for your input. I would not say I want to migrate a VM while scaling, I 
> would see it the other way around. I want to change the service offering and 
> this will include the need to migrate the VM. But at the end both 
> descriptions have the same result. :-)
> I will open an issue for an Improvement Request for this.
>
> Regards,
> Swen
>
> -Ursprüngliche Nachricht-
> Von: Daan Hoogland 
> Gesendet: Donnerstag, 1. Februar 2024 09:57
> An: users@cloudstack.apache.org
> Betreff: Re: Migrate a VM to another compute offering
>
> what you try to do , without explicitly mentioning it, Sven is to migrate the 
> VM while scaling?I had a quick look but migrate APIs don't give an easily 
> answer either. Sounds like a 
> https://github.com/apache/cloudstack/issues/new/choose to me ;)
>
> On Wed, Jan 31, 2024 at 9:35 AM  wrote:
> >
> > Hi all,
> >
> >
> >
> > we are using 2 compute offerings, called offering1 and offering2. Both
> > offerings are "Custom constrained" with similar values for cpu and memory.
> > Both offerings are using the same disk offering.
> >
> > The only difference is that offering1 used host tag "group1" and
> > offering2 uses host tag "group2". My goal is to live scale (migrate) a
> > vm from
> > offering1 to offering2 via UI. When VM is running and I click the "Scale VM"
> > icon I only see offering1 in the popup window.
> >
> > When the VM is stopped and I click on the "Scale VM" icon, I only see
> > offering1 and other offerings using the same host tag. In both cases I
> > am unable to see offering2.
> >
> >
> >
> > Is my goal even possible without altering db directly?
> >
> >
> >
> > Regards,
> >
> > Swen
> >
>
>
> --
> Daan
>
>


--
Daan

 

Re: UI - change name of secondary storage and management server

[Harikrishna Patnala]

Hi Wilken,

This API does not have that parameter to edit the name, it’s a good thing to 
add. You will have to go and edit the name in the database table 
“image_storage” for the column “name”.

Thanks,
Harikrishna

From: W. Verleger - proIO GmbH 
Date: Thursday, 1 February 2024 at 10:02 PM
To: users@cloudstack.apache.org 
Subject: UI - change name of secondary storage and management server

Hi guys,


Is there an easy way to change the name of the secondary storage and management 
server in CS 4.18.1.0 via UI / API call seen under:


Infrastructure --> Secondary storage --> "Name"
Infrastructure --> Management servers --> "Name"


Is there an API call?

Something like this but with more options?

https://cloudstack.apache.org/api/apidocs-4.18/apis/updateImageStore.html


Thank you!


Best regards,
Wilken


- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error) 
please notify
the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden.

 

Re: [VOTE] Apache CloudStack 4.19.0.0 RC4

[Harikrishna Patnala]

+1 (binding)

Tested with multiple VM and volume operations using VMware environment with 
Datastore Cluster and NFS storages, working fine.

Thanks you all involved here for all the efforts.

Regards,
Harikrishna

From: Abhishek Kumar 
Date: Monday, 29 January 2024 at 12:28 PM
To: users , d...@cloudstack.apache.org 

Cc: PMC 
Subject: [VOTE] Apache CloudStack 4.19.0.0 RC4
Hi All,

I've created a 4.19.0.0 release (RC4), with the following artifacts up for
a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.19.0.0-RC20240129T1021
Commit: 2746225b999612f156e421199e34ef8de98a3664

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.19.0.0/

PGP release keys (signed using 65518106473A09D7AF26B384A70BD2EAA74E2866):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

For testing purposes, I have uploaded the different distro packages to:
http://download.cloudstack.org/testing/4.19.0.0-RC4/

Since 4.16 the system VM template registration is no longer mandatory
before upgrading, however, it can be downloaded from here if needed:
https://download.cloudstack.org/systemvm/4.19/

The 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,
Abhishek

 

Re: new PMC member Harikrishna Patnala

[Harikrishna Patnala]

Thank you everyone.

Regards,
Harikrishna


From: Wei ZHOU 
Sent: Tuesday, January 16, 2024 2:16:30 PM
To: users@cloudstack.apache.org 
Cc: dev 
Subject: Re: new PMC member Harikrishna Patnala

Congratulations Hari !

-Wei


 

On Mon, 15 Jan 2024 at 10:25, Daan Hoogland  wrote:

> users and dev,
>
> The PMC have invited Harikrishna to join their ranks and he has
> gracefully accepted. Please join me in congratulating Hari.
>
> --
> Daan
>

Re: New committer: Alexandre Mattioli

[Harikrishna Patnala]

Congratulations Alex

From: Nux 
Date: Thursday, 11 January 2024 at 3:58 AM
To: Dev , Users 
Subject: New committer: Alexandre Mattioli
All,

The Project Management Committee (PMC) for Apache CloudStack
has invited Alexandre Mattioli to become a committer and we are pleased
to announce that they have accepted.

Alex has been instrumental in many features present today in Cloudstack,
with a focus on networking and VMWare:
- IPv6 static routing
- Edge Zones
- Autoscaling with VR
- VNF appliances
- VMWare NSX support
- Tungsten Fabric / OpenSDN
- Backup & recovery framework
- VLAN trunking and security policies in ESX
and so on.


Please join me in congratulating Alex!

 

Re: new committer: João Jandre Paraquetti

[Harikrishna Patnala]

Congratulations João

Regards,
Harikrishna

From: Daan Hoogland 
Date: Monday, 18 December 2023 at 6:17 PM
To: dev , users 
Subject: new committer: João Jandre Paraquetti
community,
The PMC have invited João Jandre Paraquetti to join the project as a
committer and the invitation was gratefully accepted.
Please join me in welcoming João.
Congratulations João,

--
Daan

 

Re: new committer Vladimir Petrov

[Harikrishna Patnala]

Congratulations Vladi !

Regards,
Harikrishna

From: Daan Hoogland 
Date: Tuesday, 12 December 2023 at 3:22 PM
To: dev , users 
Subject: new committer Vladimir Petrov
community,

The PMC has decided Vladi to become a committer and he has gracefully
accepted. Please join me in welcoming Vladi to the project as
committer.
Congratulations Vladi

--
Daan

 

Re: Force VM and VR to be on the same host

[Harikrishna Patnala]

You can either live migrate the instances or stop the instances and start the 
instances on the required host.

If you need a consistent behaviour on the host selection, you can create new 
service offerings with the same (or whatever compute values you need) values 
but with host tags now.
Stop the instances and change the service offering using scaleVM operation. 
During start of those instances, it will pick the right host based on the host 
tags in the new offerings. If the dynamic scaling is enabled on the instances, 
you can scale the VM directly to the new offering and select auto migrate 
during the scale VM operation.

Hope this helps.

Thanks,
Harikrishna

From: Francisco Arencibia Quesada 
Date: Sunday, 10 December 2023 at 5:05 PM
To: users@cloudstack.apache.org 
Subject: Re: Force VM and VR to be on the same host
Awesome, this case will work for new VMs, but what happens with those Vms
already created? Is there an easy way to relocate them?
Thanks and Regards

On Sun, 10 Dec 2023, 03:43 Harikrishna Patnala, <
harikrishna.patn...@shapeblue.com> wrote:

> Hi,
>
> You can use host tags.
>
>   1.  Set tag on the host
>   2.  Create service offering with the same host tag
>   3.  Create system service offering of System VM type “Domain Router”
> with the same host tag
>   4.  Create Network offering and select the system service offering
> created above and create network using that
>
> Regards,
> Harikrishna
>
> From: Francisco Arencibia Quesada 
> Date: Saturday, 9 December 2023 at 9:58 PM
> To: users@cloudstack.apache.org 
> Subject: Force VM and VR to be on the same host
> Hello guys,
>
>
> Is it possible to force the location of a VM and it's VR in order to have
> it in the same host? Why is this behaviour of splitting both by default?
>
> Kind regards
>
>
>
>

 

Re: Force VM and VR to be on the same host

[Harikrishna Patnala]

Hi,

You can use host tags.

  1.  Set tag on the host
  2.  Create service offering with the same host tag
  3.  Create system service offering of System VM type “Domain Router” with the 
same host tag
  4.  Create Network offering and select the system service offering created 
above and create network using that

Regards,
Harikrishna

From: Francisco Arencibia Quesada 
Date: Saturday, 9 December 2023 at 9:58 PM
To: users@cloudstack.apache.org 
Subject: Force VM and VR to be on the same host
Hello guys,


Is it possible to force the location of a VM and it's VR in order to have
it in the same host? Why is this behaviour of splitting both by default?

Kind regards

 

Re: new committer Bryan Lima

[Harikrishna Patnala]

Congratulations Bryan.

Regards,
Harikrishna

From: Daan Hoogland 
Date: Thursday, 30 November 2023 at 2:37 PM
To: dev , users 
Cc: PMC 
Subject: new committer Bryan Lima
All,

The Project Management Committee (PMC) for Apache CloudStack
has invited Bryan Lima to become a PMC member and we are pleased
to announce that they have accepted.

Bryan has contributed himself and assisted in reviewing and testing
the work of others. He has shown to be responsive, constructive and
pleasant to work with.

please join me in congratulating Bryan

--
Daan

 

Re: new PMC member: Abhishek Kumar

[Harikrishna Patnala]

Congratulations Abhishek, well deserved.

Regards,
Harikrishna



From: Daan Hoogland 
Sent: Thursday, November 23, 2023 9:41:52 AM
To: users ; dev 
Subject: new PMC member: Abhishek Kumar

The Project Management Committee (PMC) for Apache CloudStack
has invited Abhishek Kumar to become a PMC member and we are pleased
to announce that they have accepted.

Abhishek has contributed in the past and has shown effort to make the
project run smoothly. He is also the Release Manager for the upcoming
4.19 release.

please join me in congratulating Abhishek

--
Daan


 

Re: Migrating VMs from a cluster CS 4.17.2

[Harikrishna Patnala]

Hi,

Are you seeing any specific error either in the UI or the logs ? Snippet of the 
error message from logs helps.

Regards,
Harikrishna


From: Olivier GUIN 
Date: Monday, 11 September 2023 at 9:36 PM
To: users@cloudstack.apache.org , 
d...@cloudstack.apache.org 
Subject: Migrating VMs from a cluster CS 4.17.2

Hello everyone,

I have 2 clusters each with XCP-NG 7.6 servers:

4 x IBM servers and 3 x DELL servers.
Each a primary storage.
I was able to migrate VMs from IBM to DELL but not the other way around!

VM: GF-CLUSTER-01-XCP-IBM -> GF-CLUSTER-01-XCP-DELL OK
VM: GF-CLUSTER-01-XCP-DELL -> GF-CLUSTER-01-XCP-IBM NOK

Would there be a procedure to migrate the VMs? Shut down the VM, migrate the 
volume, delete the virtual router etc...?

Best regards,
--
[cid:part1.rFS4o5JM.H35087WV@ariasnet.com]

Olivier GUIN
Direction
Tel. :   05 94 31 02 44
Fax :   09 76 41 08 39
Mail :  olivier.g...@ariasnet.com
Site :  www.ariasnet.com


 

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC3)

[Harikrishna Patnala]

+1

Tested ScaleIO/Powerflex storage related operations especially volume 
migrations and also tested couple of other VM and volume operations.

Good work @Wei Zhou and everyone involved here.

Regards,
Harikrishna

From: Wei ZHOU 
Date: Thursday, 7 September 2023 at 2:04 PM
To: d...@cloudstack.apache.org , users 

Subject: [VOTE] Apache CloudStack 4.18.1.0 (RC3)
Hi all,

I've created a 4.18.1.0-RC3, with the following artifacts up for a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230907T0850
Commit: 4bdff06acd3630180f85ffe2f54add972607bbb4

Source release (checksums and signatures are available at the following
location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/

PGP release keys (signed using 1503DFE7C8226103):
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)

 

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)

[Harikrishna Patnala]

Thank you Wei.

Regards,
Harikrishna

From: Wei ZHOU 
Date: Wednesday, 6 September 2023 at 1:50 PM
To: d...@cloudstack.apache.org , users 

Subject: Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)
Hi all,

Thanks a lot for your testing, Rohit, Hari, Lucian, Nicolas and Bobby.

Unfortunately Rohit found a critical issue that live migration failed
between kvm hosts with local storage pools:
https://github.com/apache/cloudstack/issues/7942
We have proposed a fix: https://github.com/apache/cloudstack/pull/7945

I will create RC3 when the fix is verified and merged. The issue impacts
kvm hosts with local storage only.

-Wei



 

On Fri, 1 Sept 2023 at 09:39, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC2, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817
> Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> 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)
>

Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)

[Harikrishna Patnala]

+1

Tested VM and Volume operations with VMware especially with the few features 
that I’ve involved like datastore clusters. Also tested few userdata scenarios 
which worked fine.

Thanks,
Harikrishna

From: Wei ZHOU 
Date: Tuesday, 5 September 2023 at 1:00 PM
To: d...@cloudstack.apache.org , users 

Subject: Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)
Hi all,

Just a reminder, the vote will be closed tomorrow.

Kind regards,
Wei


 

On Fri, 1 Sept 2023 at 09:39, Wei ZHOU  wrote:

> Hi all,
>
> I've created a 4.18.1.0-RC2, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817
> Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c
>
> Source release (checksums and signatures are available at the following
> location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/
>
> PGP release keys (signed using 1503DFE7C8226103):
> 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)
>

Reg. OAuth2 integration in CloudStack

[Harikrishna Patnala]

Hi all,

These days I’m working on a new feature to enable OAuth2 logins in CloudStack 
assuming corresponding account/user is already created in CloudStack. Currently 
I’ve made it work with Google and Github.

I’m here to ask for any suggestions or quick information on how you are using 
OAuth in enterprise products.


  1.  Any other default OAuth providers would you like to have like Microsoft 
or Apple (I already have it working with Google and Github)
  2.  Any known single package (that supports vue and java) that gives a way to 
configure all OAuth2 providers? I tried with “vue3-social-login” but for some 
reasons I could not make it work.

Currently it is in development stage but looks something like below

[cid:image001.png@01D9DFDD.2937A7A0]

Thanks,
Harikrishna

 

Re: details missing in add guestos query

[Harikrishna Patnala]

Hi,

Details parameter is not a required field for addGuestos API, not sure why you 
are seeing this error. Which version of CloudStack are you using ?

In case if you want to pass details, you can add something like 
“details[0].key=”xenserver.dynamicMin" details[0].value=134217728 
details[1].key="xenserver.dynamicMax" details[1].value=536870912”

Regards,
Harikrishna

From: Francisco Arencibia 
Date: Thursday, 3 August 2023 at 8:00 PM
To: users@cloudstack.apache.org 
Subject: details missing in add guestos query
Good morning guys,

I'm having this error, and I can't find how to pass details info in cloudstack 
documentation.
Can you please give a piece of advice 🙂

[root@localhost ~]# cloudmonkey add guestos 
oscategoryid="62c4308f-4616-11e7-a869-0e8aa6d45439" name="Windows Server 2019 
(64-bit)" displayName="Windows Server 2019 (64-bit)" osdisplayname="Windows 
Server 2019 (64-bit)" isuserdefined=true
Error 431: Unable to execute API command addguestos due to missing parameter 
details



DevOps Engineer


francisco.arenci...@jotelulu.com  | 
jotelulu.com |



[cid:d8096857-741a-4066-a0c2-8e80f90ae71f]

Under the GDPR and the Spanish Organic Law 3/2018, of December 5, on Personal 
Data Protection and Guarantee of Digital Rights, JOTELULU SL - with tax number 
B65814709 and registered address at Plaza Pablo Ruiz Picasso Núm 1 28020 
(Madrid)- has a legal duty to protect any personal information we collect from 
you. Information contained in this email and any attachments are privileged, 
confidential and intended for the exclusive use of the original recipient. If 
you have received this email by mistake, please advise the sender immediately 
and delete the email. You must not copy, distribute or disclose the information 
it contains. JOTELULU SL is responsible for the processing of personal data. 
JOTELULU SL carries out this treatment with the purpose of managing 
professional communications, based on two premises: the user's consent and the 
correct execution of the contractual relationship. JOTELULU SL will keep the 
data up to a maximum period of five years. The transfer of personal data to 
third parties will only take place with the express consent of the user. At any 
time, users may exercise their rights of access, rectification, deletion, 
limitation, portability or objection to the Data Protection Officer of JOTELULU 
SL at the following e-mail address d...@jotelulu.com, 
at its registered address, or before the Spanish Data Protection Agency - C/ 
Jorge Juan, 6. 28001 – Madrid-. For additional information regarding the 
Privacy Policy of JOTELULU SL, please click on the following 
link.

 

Re: [PROPOSE] RM for 4.19.0

[Harikrishna Patnala]

+1, thanks for volunteering and good luck Abhishek.

Regards,
Harikrishna

From: Abhishek Kumar 
Date: Sunday, 30 April 2023 at 10:23 PM
To: d...@cloudstack.apache.org , 
users@cloudstack.apache.org 
Subject: [PROPOSE] RM for 4.19.0
Dear All,

I would like to propose and put myself forward as the release manager for 
4.19.0 release. In the past, I've RM'd 4.17.1.0 release and co-RM'd a couple of 
releases before that. I would like to take experiences from those to work on a 
successful release.

I propose we start early, sometime in Q3 2023, with the planning, triaging, 
bug-fixing, etc to get back on the traditional two-release per year cycle. With 
this we can aim to cut the RC sometime in October. I will propose a detailed 
timeline soon.

I hope to have your support. Please let me know if you have any 
thoughts/comments.

Regards,
Abhishek



 

Re: SSVM stopped and will not be recreated.... :-(

[Harikrishna Patnala]

Thanks Jithin

From: Jithin Raju 
Date: Wednesday, 26 April 2023 at 2:08 PM
To: users@cloudstack.apache.org 
Subject: Re: SSVM stopped and will not be recreated :-(
Here it is:

https://github.com/apache/cloudstack/issues/7474



-Jithin

From: Jithin Raju 
Date: Wednesday, 26 April 2023 at 1:52 PM
To: users@cloudstack.apache.org 
Subject: Re: SSVM stopped and will not be recreated :-(
Hi Hari,

Yes, let me create one.

-Jithin

From: Harikrishna Patnala 
Date: Wednesday, 26 April 2023 at 12:36 PM
To: users@cloudstack.apache.org 
Subject: Re: SSVM stopped and will not be recreated :-(
Hi Jithin,

Do we need to create an issue for that, seems fair to me to handle it properly.

Thanks,
Harikrishna

From: Jithin Raju 
Date: Tuesday, 25 April 2023 at 11:05 AM
To: users@cloudstack.apache.org 
Subject: Re: SSVM stopped and will not be recreated :-(
Hi David,

I came across similar issue where the new SSVM allocation fails since the newly 
added systemvm template in 4.17 during upgrade do not have its size set in 
vm_template and template_store_ref. Once you update these tables with the size 
value (from templates.properties in secondary storage) and recreate the 
SystemVMs it should go through.

Essentially any error during SSVM/CPVM allocation could leave that entry there 
without all the required allocation, when the secstorage-1 or the 
consoleproxy-1 thread runs again it would notice this entry as a stopped 
SSVM/CPVM and try starting it. Due to the previous error/s the volume is not 
allocated in this case hence the error “no usable volumes found” error while 
starting it since it doesn’t have entry for volume in the volumes table. This 
could be a bug.

-Jithin

From: Jithin Raju 
Date: Tuesday, 25 April 2023 at 10:46 AM
To: users@cloudstack.apache.org 
Subject: Re: SSVM stopped and will not be recreated :-(
Hi David,

Is that issue resolved? If not perform this:

tailf /var/log/cloudstack/management/management-server.log | grep secstorage-1

then destroy the existing SSVM and see if you see an error during the 
allocation of a new volume for the new SSVM?

-Jithin

From: Jithin Raju 
Date: Wednesday, 19 April 2023 at 4:04 PM
To: users@cloudstack.apache.org 
Subject: Re: SSVM stopped and will not be recreated :-(
Hi David,

Is it possible to share the complete log?

-Jithin

From: David Larsen 
Date: Tuesday, 18 April 2023 at 11:27 PM
To: users@cloudstack.apache.org 
Subject: SV: SSVM stopped and will not be recreated :-(
Hi Jithin

Thanks
I tried to destroy the SSVM (s-1178-VM) again and the same happened.
When I destroyed the s-1178-VM,  a new secondarystoragevm  (s-1179-VM) is 
created in Cloudstack, but not in vmware. The new s-1179-VM have state 
"Stopped" in Cloudstack, the old s-1178-VM is gone from Cloudstack, but not in 
vmware...(?)
We are using vcenter 7.0.3 build 21290409, ESXi vsphere 7.0.3 build 20842708

When I search the logs, I see the "GetVolumeStatsCommand" is looking for an 
older secondarystoragevm (s-1177-VM).(?)
Why is it asking for a destroyed secondarystoragevm?

Some logs bellow:

tail -f /var/log/cloudstack/management/management-server.log | grep secstorage
2023-04-18 18:42:06,457 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-5fbc0852) (logid:da43d2ce) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:42:36,452 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-46384dc3) (logid:d00b7246) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:43:06,455 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-4f4a13fd) (logid:7a2e9b74) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:43:36,455 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-cc2d5863) (logid:e71c579c) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:44:06,451 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-1edf7982) (logid:eedb5033) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:44:06,455 INFO  [o.a.c.s.PremiumSecondaryStorageManagerImpl] 
(secstorage-1:ctx-1edf7982) (logid:eedb5033) No running secondary storage vms 
found in datacenter id=5, starting one
2023-04-18 18:44:06,458 INFO  [o.a.c.s.PremiumSecondaryStorageManagerImpl] 
(secstorage-1:ctx-1edf7982) (logid:eedb5033) Found SSVMs that are currently at 
stopping state, wait until they are settled
2023-04-18 18:44:36,459 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-82a430e4) (logid:463b8153) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:44:36,464 INFO  [o.a.c.s.PremiumSecondaryStorageManagerImpl] 
(secstorage-1:ctx-82a430e4) (logid:463b8153) No running secondary storage vms 
found in datacenter id=5, starting one
2023-04-18 18:44:36,468 INFO  [o.a.c.s.PremiumSecondaryStorageManagerImpl] 
(secstorage-1:ctx-82a430e4) (logid:463b8153) Found SSVMs that are currently at 
stopping state, wait until they are settled
2023-04-1

Re: SSVM stopped and will not be recreated.... :-(

[Harikrishna Patnala]

Hi Jithin,

Do we need to create an issue for that, seems fair to me to handle it properly.

Thanks,
Harikrishna

From: Jithin Raju 
Date: Tuesday, 25 April 2023 at 11:05 AM
To: users@cloudstack.apache.org 
Subject: Re: SSVM stopped and will not be recreated :-(
Hi David,

I came across similar issue where the new SSVM allocation fails since the newly 
added systemvm template in 4.17 during upgrade do not have its size set in 
vm_template and template_store_ref. Once you update these tables with the size 
value (from templates.properties in secondary storage) and recreate the 
SystemVMs it should go through.

Essentially any error during SSVM/CPVM allocation could leave that entry there 
without all the required allocation, when the secstorage-1 or the 
consoleproxy-1 thread runs again it would notice this entry as a stopped 
SSVM/CPVM and try starting it. Due to the previous error/s the volume is not 
allocated in this case hence the error “no usable volumes found” error while 
starting it since it doesn’t have entry for volume in the volumes table. This 
could be a bug.

-Jithin

From: Jithin Raju 
Date: Tuesday, 25 April 2023 at 10:46 AM
To: users@cloudstack.apache.org 
Subject: Re: SSVM stopped and will not be recreated :-(
Hi David,

Is that issue resolved? If not perform this:

tailf /var/log/cloudstack/management/management-server.log | grep secstorage-1

then destroy the existing SSVM and see if you see an error during the 
allocation of a new volume for the new SSVM?

-Jithin

From: Jithin Raju 
Date: Wednesday, 19 April 2023 at 4:04 PM
To: users@cloudstack.apache.org 
Subject: Re: SSVM stopped and will not be recreated :-(
Hi David,

Is it possible to share the complete log?

-Jithin

From: David Larsen 
Date: Tuesday, 18 April 2023 at 11:27 PM
To: users@cloudstack.apache.org 
Subject: SV: SSVM stopped and will not be recreated :-(
Hi Jithin

Thanks
I tried to destroy the SSVM (s-1178-VM) again and the same happened.
When I destroyed the s-1178-VM,  a new secondarystoragevm  (s-1179-VM) is 
created in Cloudstack, but not in vmware. The new s-1179-VM have state 
"Stopped" in Cloudstack, the old s-1178-VM is gone from Cloudstack, but not in 
vmware...(?)
We are using vcenter 7.0.3 build 21290409, ESXi vsphere 7.0.3 build 20842708

When I search the logs, I see the "GetVolumeStatsCommand" is looking for an 
older secondarystoragevm (s-1177-VM).(?)
Why is it asking for a destroyed secondarystoragevm?

Some logs bellow:

tail -f /var/log/cloudstack/management/management-server.log | grep secstorage
2023-04-18 18:42:06,457 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-5fbc0852) (logid:da43d2ce) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:42:36,452 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-46384dc3) (logid:d00b7246) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:43:06,455 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-4f4a13fd) (logid:7a2e9b74) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:43:36,455 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-cc2d5863) (logid:e71c579c) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:44:06,451 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-1edf7982) (logid:eedb5033) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:44:06,455 INFO  [o.a.c.s.PremiumSecondaryStorageManagerImpl] 
(secstorage-1:ctx-1edf7982) (logid:eedb5033) No running secondary storage vms 
found in datacenter id=5, starting one
2023-04-18 18:44:06,458 INFO  [o.a.c.s.PremiumSecondaryStorageManagerImpl] 
(secstorage-1:ctx-1edf7982) (logid:eedb5033) Found SSVMs that are currently at 
stopping state, wait until they are settled
2023-04-18 18:44:36,459 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-82a430e4) (logid:463b8153) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:44:36,464 INFO  [o.a.c.s.PremiumSecondaryStorageManagerImpl] 
(secstorage-1:ctx-82a430e4) (logid:463b8153) No running secondary storage vms 
found in datacenter id=5, starting one
2023-04-18 18:44:36,468 INFO  [o.a.c.s.PremiumSecondaryStorageManagerImpl] 
(secstorage-1:ctx-82a430e4) (logid:463b8153) Found SSVMs that are currently at 
stopping state, wait until they are settled
2023-04-18 18:45:06,455 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-36cf6e8c) (logid:56ad8856) Zone [5] is ready to launch 
secondary storage VM.
2023-04-18 18:45:06,459 INFO  [o.a.c.s.PremiumSecondaryStorageManagerImpl] 
(secstorage-1:ctx-36cf6e8c) (logid:56ad8856) No running secondary storage vms 
found in datacenter id=5, starting one
2023-04-18 18:45:06,462 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-36cf6e8c) (logid:56ad8856) Allocate secondary storage VM 
standby capacity for zone [5].
2023-04-18 18:45:06,465 INFO  [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-36cf6e8c) (logid:56ad8856) Fou

Re: SSVM - Getting "Unable to create deployment, no usable volumes found for the VM" after Cloudstack/Mysql/Ubuntu upgrade.

[Harikrishna Patnala]

Hi David,

Did you try deleting the existing SSVM in CloudStack and let it recreate ?

Thanks,
Harikrishna

From: David Larsen 
Date: Thursday, 30 March 2023 at 1:31 AM
To: users@cloudstack.apache.org 
Subject: SSVM - Getting "Unable to create deployment, no usable volumes found 
for the VM" after Cloudstack/Mysql/Ubuntu upgrade.

Hi

Today i upgraded our Cloudstack (4.17.2 --> 4.18.0) , mysql (5.7--> 8) and  
ubuntu (18.04-->22.04) in production.
I thought I had tested it well in a lab... and of course  the only important 
thing I couldn't test went wrong!!
Secondary Storage VM...

At first it looked fine. I successfully upgraded console proxy system vm to 
4.18.0.
But when I tried to do the same with secondarystoragevm, stop it and wait for 
it to upgrade, Cloudstack  deleted the secondary systemvm from vmware and when 
it started the copy job it complained about a locked file on the vmware 
volume(?) I didn't find any locked files in the s-1177-VM vm directory on 
the vmware volume.

>From the error log bellow: "Unable to create deployment, no usable volumes 
>found for the VM: 1177"
Every five vmware volumes have about 50% free space, so enough space is not an 
issue...
In the case of locked file on vmware I have restarted vcenter and management 
agents on every host, so every locked files should be released.
No change.

Then I reverted to cloudstack 4.17.2 on ubuntu 22.04 on both management and 
mysql server hoping cloudstack would create the SSVM from scratch... it did 
not. Same error in the log and no S--VM created...

In Cloudstack dashboard it show  S-1177-VM as stopped, but in vmware, it's 
gone...
Everything else I have checked is running fine. Start/stop vm ++

Can it be any ubuntu 22.04 upgrade issues here?
Until I upgraded today, everything was running fine on ubuntu 18.04, Cloudstack 
4.17.2 and Mysql 5.7
Any new settings in db.properties regarding new mysql or ubuntu?



2023-03-29 20:58:18,866 INFO  [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-0dd13ec7) (logid:c5bd94b0) Found a stopped secondary storage 
VM instance {id: "1177", name: "s-1177-VM", uuid: 
"602280ac-a809-4ac9-b229-ea43c0ac0145", type="SecondaryStorageVm"}, starting it.
2023-03-29 20:58:19,743 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-93:ctx-c7b556c4 job-12132/job-12228 ctx-8a5aa0c5) 
(logid:4c5d9052) orchestrating VM start for 's-1177-VM' 
com.cloud.vm.VirtualMachineProfile$Param@b66cdd7d
 set to null
2023-03-29 20:58:19,753 DEBUG [c.c.c.CapacityManagerImpl] 
(Work-Job-Executor-93:ctx-c7b556c4 job-12132/job-12228 ctx-8a5aa0c5) 
(logid:4c5d9052) VM instance {id: "1177", name: "s-1177-VM", uuid: 
"602280ac-a809-4ac9-b229-ea43c0ac0145", type="SecondaryStorageVm"} state 
transited from [Stopped] to [Starting] with event [StartRequested]. VM's 
original host: null, new host: null, host before state transition: null
2023-03-29 20:58:19,753 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-93:ctx-c7b556c4 job-12132/job-12228 ctx-8a5aa0c5) 
(logid:4c5d9052) Successfully transitioned to start state for VM instance {id: 
"1177", name: "s-1177-VM", uuid: "602280ac-a809-4ac9-b229-ea43c0ac0145", 
type="SecondaryStorageVm"} reservation id = 30f7264c-1598-45aa-a71e-b2b0f88a4519
2023-03-29 20:58:19,886 DEBUG [c.c.c.CapacityManagerImpl] 
(Work-Job-Executor-93:ctx-c7b556c4 job-12132/job-12228 ctx-8a5aa0c5) 
(logid:4c5d9052) VM instance {id: "1177", name: "s-1177-VM", uuid: 
"602280ac-a809-4ac9-b229-ea43c0ac0145", type="SecondaryStorageVm"} state 
transited from [Starting] to [Stopped] with event [OperationFailed]. VM's 
original host: null, new host: null, host before state transition: null
2023-03-29 20:58:19,887 WARN  [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-93:ctx-c7b556c4 job-12132/job-12228 ctx-8a5aa0c5) 
(logid:4c5d9052) Unable to orchestrate start VM instance {id: "1177", name: 
"s-1177-VM", uuid: "602280ac-a809-4ac9-b229-ea43c0ac0145", 
type="SecondaryStorageVm"} due to [Unable to create deployment, no usable 
volumes found for the VM: 1177].
2023-03-29 20:58:19,943 WARN  [c.c.v.SystemVmLoadScanner] 
(secstorage-1:ctx-0dd13ec7) (logid:c5bd94b0) Unexpected exception Unable to 
orchestrate start VM instance {id: "1177", name: "s-1177-VM", uuid: 
"602280ac-a809-4ac9-b229-ea43c0ac0145", type="SecondaryStorageVm"} due to 
[Unable to create deployment, no usable volumes found for the VM: 1177].
com.cloud.utils.exception.CloudRuntimeException: Unable to orchestrate start VM 
instance {id: "1177", name: "s-1177-VM", uuid: 
"602280ac-a809-4ac9-b229-ea43c0ac0145", type="SecondaryStorageVm"} due to 
[Unable to create deployment, no usable volumes found for the VM: 1177].


Thanks

-David

 

Re: [ANNOUNCE] New VP of Apache CloudStack - Rohit Yadav

[Harikrishna Patnala]

Congratulations Rohit and thank you Simon.

Regards,
Harikrishna

From: Simon Weller 
Date: Thursday, 30 March 2023 at 9:07 AM
To: d...@cloudstack.apache.org , 
users@cloudstack.apache.org 
Cc: priv...@cloudstack.apache.org 
Subject: [ANNOUNCE] New VP of Apache CloudStack - Rohit Yadav
All,

I'm very pleased to announce that the ASF board has accepted the nomination
of Rohit Yadav to be the new VP of the Apache CloudStack project.

It has been my pleasure to serve as the VP over the past year, and I'd like
to thank the community for all of the support.

Rohit, congratulations and I wish you the best as you take on this new role.

-Simon

 

Re: instance recreation with Terraform fails

[Harikrishna Patnala]

Hi Jordan,

I think the error that you have shared is not related to VM deployment.

Can you look into the logs starting from the deployVirtualMachine API for more 
details.

Thanks,
Harikrishna

From: jordan j 
Date: Monday, 20 March 2023 at 5:34 PM
To: users@cloudstack.apache.org 
Subject: instance recreation with Terraform fails
Hey everyone!

Setup is 4.17.2 with XCP-NG - Advanced Zone + SG on local SR.

While recreating an instance on Cloudstack with Terraform, the job fails
with this error in Cloudstack logs:

2023-03-20 07:34:07,707 ERROR [c.c.u.s.SshHelper]
(AgentTaskPool-6:ctx-dbbda9d1) (logid:8d26a6f8) SSH execution of command xe
sm-list | grep "resigning of duplicates" has an error status code in
return. Result output:

I am not really sure how to continue troubleshooting from here as creating
an instance from the GUI works just fine.

Regards,
Jordan

 

Re: Hello Community!!

[Harikrishna Patnala]

Welcome Jithin

Regards,
Harikrishna

From: Jithin Raju 
Date: Tuesday, 14 March 2023 at 1:27 PM
To: users@cloudstack.apache.org , 
d...@cloudstack.apache.org 
Subject: Hello Community!!
Hi All,

I have joined ShapeBlue and looking forward to getting actively involved in the 
community. Previously I worked on the commercial fork of the ACS, mostly 
involved in technical support.

-Jithin



 

Re: SSVM Randomly Stopped Connecting

[Harikrishna Patnala]

Hi,

Have you tried destroying the SSVM, it will be recreated automatically. Please 
try that, it may solve the issue.

Thanks,
Harikrishna

From: Granwille Strauss 
Date: Wednesday, 15 February 2023 at 1:46 PM
To: users@cloudstack.apache.org 
Subject: SSVM Randomly Stopped Connecting

Hi Guys

As the error suggests, this morning my SSVM just randomly stopped connecting 
and agent status remains in "Connecting" mode. ConsolveVM seems perfectly fine. 
I did the regular checks in SSVM and it all seems fine, see attached 
screenshot. I tried force rebooting the SSVM but still nothing. The host kvm 
server is 100% connected as one typically gets the "host unreachable" error 
when something like this, but not this time.

I SSH into the SSVM and ran the 'reboot' command and tailed the management log, 
this is what it throws: https://jpst.it/36K93

I do not see any errors there either. Any suggestions that can help with this, 
please?
--

Regards / Groete
[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/logo/621b3fa39fb210001f975298/cd2904ba-304d-4a49-bf33-cbe9ac76d929_248x-.png]
Granwille Strauss  //  Senior Systems Admin

e: granwi...@namhost.com
m: +264 81 323 1260
w: www.namhost.com

[https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_01/621b3fa39fb210001f975298/9151954b-b298-41aa-89c8-1d68af075373_48x48.png][https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_02/621b3fa39fb210001f975298/85a9dc7c-7bd1-4958-85a9-e6a25baeb028_48x48.png][https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_03/621b3fa39fb210001f975298/c1c5386c-914c-43cf-9d37-5b4aa8e317ab_48x48.png][https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_04/621b3fa39fb210001f975298/3aaa7968-130e-48ec-821d-559a332cce47_48x48.png][https://www.adsigner.com/v1/s/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/social_icon_05/621b3fa39fb210001f975298/3a8c09e6-588f-43a8-acfd-be4423fd3fb6_48x48.png]

[https://www.adsigner.com/v1/i/631091998d4670001fe43ec2/621c9b76c140bb001ed0f818/banner/940x300]
Namhost Internet Services (Pty) Ltd,

24 Black Eagle Rd, Hermanus, 7210, RSA

The content of this message is confidential. If you have received it by 
mistake, please inform us by email reply and then delete the message. It is 
forbidden to copy, forward, or in any way reveal the contents of this message 
to anyone without our explicit consent. The integrity and security of this 
email cannot be guaranteed over the Internet. Therefore, the sender will not be 
held liable for any damage caused by the message. For our full privacy policy 
and disclaimers, please go to https://www.namhost.com/privacy-policy

[Powered by 
AdSigner]

 

Re: [ANNOUNCE] Ivet Petrova has joined the PMC

[Harikrishna Patnala]

Congratulations Ivet!

Regards,
Harikrishna

From: Simon Weller 
Date: Tuesday, 14 February 2023 at 9:31 PM
To: priv...@cloudstack.apache.org , 
d...@cloudstack.apache.org , 
users@cloudstack.apache.org 
Subject: [ANNOUNCE] Ivet Petrova has joined the PMC
Hi everyone,

It gives me great pleasure to announce that Ivet has been invited to join
the
CloudStack PMC and she has accepted.

Please join me in congratulating Ivet!

-Simon (on behalf of the CloudStack PMC)

 

Re: Introduction

[Harikrishna Patnala]

Welcome Kiran!

Regards,
Harikrishna

From: Kiran Chavala 
Date: Thursday, 2 February 2023 at 10:54 AM
To: users@cloudstack.apache.org 
Subject: Introduction
Hi all,


This is Kiran, Just wanted to say hi to everyone in the community.

I've recently Shape blue as QA test engineer.

Previously I used to work with Citrix/Persistent for about 10 years in 
providing technical support to Cloudstack ( Citrix CloudPlatform and Rovius 
CloudPlatform) products

Looking forward to working with the community

Regards,
Kiran

kiran.chav...@shapeblue.com




 

Re: VM Volume Limit 1024 GB

[Harikrishna Patnala]

Hi Rafael,

You need to change this global setting “custom.diskoffering.size.max”. This is 
the setting which will be checked while using custom disk offerings.

Thanks,
Harikrishna

From: Rafael del Valle 
Date: Tuesday, 6 December 2022 at 3:47 PM
To: users@cloudstack.apache.org 
Subject: VM Volume Limit 1024 GB
Hi!

I ​cannot create an instance with 2000 GB data volume despite available 
resources in ACS 4.16.1.

I get a message:

VM Creation failed. Volume size: 2000GB is out of allowed range. Max: 1024 Min:1

The configuration parameter storage.max.volume.size is 2000



I cannot see any related account limit either.

The volume type is Local Storage.


Where is the limit coming from?


R.

 

Re: Cloudstack user logins with 2FA and Google Authenticator

[Harikrishna Patnala]

Hi David,

2FA framework and plugin is under development and planning to make it in 4.18 
release. It is not available in 4.17.1.
You can find some details about the feature here at 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/2FA+Framework+and+Plugins

Regards,
Harikrishna

From: David Larsen 
Date: Thursday, 17 November 2022 at 8:19 PM
To: users@cloudstack.apache.org 
Subject: Cloudstack user logins with 2FA and Google Authenticator

Hi

We are currently working on how to integrate Cloudstack (4.17.1.0) logins with 
Google and Google  authenticator.
Is there any “this is how you do it” documents out there for Cloudstack. I 
found some info related to it , but no luck yet… ☹

I saw the “2FA Framework and Plugins” document from the 4.17 design documents 
by Rohit. Is this plugin deployed in 4.17.1.0?

Do we have to use SAML2 to make this work?
And if so, how?


Any help pointing me in the right direction will help us a lot.


Best regards
David Larsen

 

Re: compute cannot be used if rot disk size is 0

[Harikrishna Patnala]

ion while executing
>> org.apache.cloudstack.api.command.admin.router.StartRouterCmd
>> com.cloud.exception.AgentUnavailableException: Resource [Host:76] is
>> unreachable: Host 76: Unable to start instance due to Unable to start
>>  VM:3d3637d5-afd9-4c5d-b5f8-a871460f6856 due to error in finalizeStart, not
>> retrying
>>
>>
>> On Mon, Nov 7, 2022 at 5:18 AM Harikrishna Patnala <
>> harikrishna.patn...@shapeblue.com> wrote:
>>
>>> Hi Jordan,
>>>
>>> I’ve tried the same cloudmonkey commands and it worked fine on my
>>> environment. I don’t think the way we save the details in the database has
>>> changed, not sure what is happening from UI front.
>>>
>>> Can you open the developers tools in the browser and capture the
>>> “deployVirtualMachine” API request params and send us, so that I can verify
>>> with my environment.
>>>
>>> Regards,
>>> Harikrishna
>>>
>>> From: jordan j 
>>> Date: Friday, 4 November 2022 at 2:01 PM
>>> To: users@cloudstack.apache.org 
>>> Subject: Re: compute cannot be used if rot disk size is 0
>>> Yes CPU/RAM are fixed!
>>>
>>> Code for disk and service offering:
>>>
>>> createDiskOffering isMirrored=false name=custom-disk
>>> displaytext=custom-disk storageType=local cacheMode=none
>>> provisioningType=thin customized=true disksizestrictness=false
>>> {
>>>   "diskoffering": {
>>> "cacheMode": "none",
>>> "created": "2022-11-04T09:27:03+0100",
>>> "disksize": 0,
>>> "disksizestrictness": false,
>>> "displayoffering": true,
>>> "displaytext": "custom-disk",
>>> "hasannotations": false,
>>> "id": "c7d11a8d-29eb-44b0-811c-fb57dbaac2a5",
>>> "iscustomized": true,
>>> "name": "custom-disk",
>>> "provisioningtype": "thin",
>>> "storagetype": "local"
>>>   }
>>> }
>>>
>>> createServiceOffering issystem=false name=fixed-compute
>>> displaytext=fixed-compute customized=false offerha=false
>>> limitcpuuse=false
>>> dynamicscalingenabled=true cpunumber=2 cpuspeed=2000 memory=2048
>>> diskofferingid=c7d11a8d-29eb-44b0-811c-fb57dbaac2a5
>>> {
>>>   "serviceoffering": {
>>> "cacheMode": "none",
>>> "cpunumber": 2,
>>> "cpuspeed": 2000,
>>> "created": "2022-11-04T09:28:52+0100",
>>> "defaultuse": false,
>>> "diskofferingdisplaytext": "custom-disk",
>>> "diskofferingid": "c7d11a8d-29eb-44b0-811c-fb57dbaac2a5",
>>> "diskofferingname": "custom-disk",
>>> "diskofferingstrictness": false,
>>> "displaytext": "fixed-compute",
>>> "dynamicscalingenabled": true,
>>> "hasannotations": false,
>>> "id": "f5a61b2f-9b03-4322-9d10-bb69033a87dd",
>>> "iscustomized": false,
>>> "issystem": false,
>>> "isvolatile": false,
>>> "limitcpuuse": false,
>>> "memory": 2048,
>>> "name": "fixed-compute",
>>> "offerha": false,
>>> "provisioningtype": "thin",
>>> "rootdisksize": 0,
>>> "storagetype": "local"
>>>   }
>>> }
>>>
>>> Regards,
>>> Jordan
>>>
>>> On Fri, Nov 4, 2022 at 3:22 AM Harikrishna Patnala <
>>> harikrishna.patn...@shapeblue.com> wrote:
>>>
>>> > Can you please share the CLI list responses of the service offering and
>>> > disk offering (fixed-compute-with-custom-disk) that you have used in
>>> your
>>> > case 2, so that I’ll create the exact same offerings and try to deploy
>>> the
>>> > VM.
>>> >
>>> > When you say “Create any service offering (used fixed for the test)”,
>>> do
>>> > you mean fixed compute details like CPU, RAM ?
>>> >
>>> > Thanks,
>>> > Harikrishna
>>> >
>>> > From: jordan j 

Re: compute cannot be used if rot disk size is 0

[Harikrishna Patnala]

Hi Jordan,

I’ve tried the same cloudmonkey commands and it worked fine on my environment. 
I don’t think the way we save the details in the database has changed, not sure 
what is happening from UI front.

Can you open the developers tools in the browser and capture the 
“deployVirtualMachine” API request params and send us, so that I can verify 
with my environment.

Regards,
Harikrishna

From: jordan j 
Date: Friday, 4 November 2022 at 2:01 PM
To: users@cloudstack.apache.org 
Subject: Re: compute cannot be used if rot disk size is 0
Yes CPU/RAM are fixed!

Code for disk and service offering:

createDiskOffering isMirrored=false name=custom-disk
displaytext=custom-disk storageType=local cacheMode=none
provisioningType=thin customized=true disksizestrictness=false
{
  "diskoffering": {
"cacheMode": "none",
"created": "2022-11-04T09:27:03+0100",
"disksize": 0,
"disksizestrictness": false,
"displayoffering": true,
"displaytext": "custom-disk",
"hasannotations": false,
"id": "c7d11a8d-29eb-44b0-811c-fb57dbaac2a5",
"iscustomized": true,
"name": "custom-disk",
"provisioningtype": "thin",
"storagetype": "local"
  }
}

createServiceOffering issystem=false name=fixed-compute
displaytext=fixed-compute customized=false offerha=false limitcpuuse=false
dynamicscalingenabled=true cpunumber=2 cpuspeed=2000 memory=2048
diskofferingid=c7d11a8d-29eb-44b0-811c-fb57dbaac2a5
{
  "serviceoffering": {
"cacheMode": "none",
"cpunumber": 2,
"cpuspeed": 2000,
"created": "2022-11-04T09:28:52+0100",
"defaultuse": false,
"diskofferingdisplaytext": "custom-disk",
"diskofferingid": "c7d11a8d-29eb-44b0-811c-fb57dbaac2a5",
"diskofferingname": "custom-disk",
"diskofferingstrictness": false,
"displaytext": "fixed-compute",
"dynamicscalingenabled": true,
"hasannotations": false,
"id": "f5a61b2f-9b03-4322-9d10-bb69033a87dd",
"iscustomized": false,
"issystem": false,
"isvolatile": false,
"limitcpuuse": false,
"memory": 2048,
"name": "fixed-compute",
"offerha": false,
"provisioningtype": "thin",
"rootdisksize": 0,
"storagetype": "local"
  }
}

Regards,
Jordan

On Fri, Nov 4, 2022 at 3:22 AM Harikrishna Patnala <
harikrishna.patn...@shapeblue.com> wrote:

> Can you please share the CLI list responses of the service offering and
> disk offering (fixed-compute-with-custom-disk) that you have used in your
> case 2, so that I’ll create the exact same offerings and try to deploy the
> VM.
>
> When you say “Create any service offering (used fixed for the test)”, do
> you mean fixed compute details like CPU, RAM ?
>
> Thanks,
> Harikrishna
>
> From: jordan j 
> Date: Thursday, 3 November 2022 at 2:06 PM
> To: users@cloudstack.apache.org 
> Subject: Re: compute cannot be used if rot disk size is 0
> Hi Harikrishna!
>
> Upgraded to 4.17.1 and did some more tests.
>
> 1. Create any service offering mapped to disk offering with fixed size -
> this works
> 2. Create any service offering (used fixed for the test) mapped to disk
> offering with custom size - this brings the error mentioned during instance
> creation.
>
> During case 2  when in GUI there is Root disk size (GB) option but it does
> not matter to what it is set, the error always appears.
> This case is similar to what you do in case 3. The question is what is it
> that you do that makes it work on your side and fail on mine.
>
> Here is a link with the error message and the options selected during
> instance creation: https://imgur.com/l3WktFg
> DIsk offering is custom and I set it to 50 but ACS does not take it into
> account and still thinks it is 0.
>
> Regards,
> Jordan
>
> On Thu, Nov 3, 2022 at 9:26 AM Harikrishna Patnala <
> harikrishna.patn...@shapeblue.com> wrote:
>
> > Hi Jordan,
> >
> > I’ve tried these scenarios in 4.17.1 and it seems to be working fine.
> This
> > might be an issue in 4.17 but it is working fine in 4.17.1
> >
> > I tried the following scenarios,
> >
> >   1.  Created a service offering with an existing disk offering and
> > deployed VM with it from GUI. It worked fine.
> >   2.  Tried the same from CLI (without rootdisksize). It worked fine.
> >   3.  Created a service offering with an existing 

Re: compute cannot be used if rot disk size is 0

[Harikrishna Patnala]

Can you please share the CLI list responses of the service offering and disk 
offering (fixed-compute-with-custom-disk) that you have used in your case 2, so 
that I’ll create the exact same offerings and try to deploy the VM.

When you say “Create any service offering (used fixed for the test)”, do you 
mean fixed compute details like CPU, RAM ?

Thanks,
Harikrishna

From: jordan j 
Date: Thursday, 3 November 2022 at 2:06 PM
To: users@cloudstack.apache.org 
Subject: Re: compute cannot be used if rot disk size is 0
Hi Harikrishna!

Upgraded to 4.17.1 and did some more tests.

1. Create any service offering mapped to disk offering with fixed size -
this works
2. Create any service offering (used fixed for the test) mapped to disk
offering with custom size - this brings the error mentioned during instance
creation.

During case 2  when in GUI there is Root disk size (GB) option but it does
not matter to what it is set, the error always appears.
This case is similar to what you do in case 3. The question is what is it
that you do that makes it work on your side and fail on mine.

Here is a link with the error message and the options selected during
instance creation: https://imgur.com/l3WktFg
DIsk offering is custom and I set it to 50 but ACS does not take it into
account and still thinks it is 0.

Regards,
Jordan

On Thu, Nov 3, 2022 at 9:26 AM Harikrishna Patnala <
harikrishna.patn...@shapeblue.com> wrote:

> Hi Jordan,
>
> I’ve tried these scenarios in 4.17.1 and it seems to be working fine. This
> might be an issue in 4.17 but it is working fine in 4.17.1
>
> I tried the following scenarios,
>
>   1.  Created a service offering with an existing disk offering and
> deployed VM with it from GUI. It worked fine.
>   2.  Tried the same from CLI (without rootdisksize). It worked fine.
>   3.  Created a service offering with an existing CUSTOM disk offering and
> deployed VM with it from GUI. It worked fine too.
>
> Can you please try upgrading your environment to 4.17.1 ?
>
> Also I did not understand your scenario why rootdisksize comes to picture
> when diskoffering is mapped to a service offering ? Is that a custom disk
> offering ?
>
> Thanks,
> Harikrishna
> From: jordan j 
> Date: Wednesday, 2 November 2022 at 8:01 PM
> To: users@cloudstack.apache.org 
> Subject: compute cannot be used if rot disk size is 0
> Hey everyone,
>
> I found a bug (4.17.0.1).
>
> if you try to create an instance from compute offering that has root disk
> size = 0 the following error appears:
> VM Creation failed. Volume size: -1GB is out of allowed range. Max: 1024
> Min:1
>
> A few examples when rootdisk size is set as 0:
> - when compute offering is created and matched to existing disk offering
>
> --> via GUI same thing as CLI
> If a compute offering is created by specifying existing disk offering,
> the root disk size is set as 0
> Workaround: When creating Compute offering, enable "Compute only disk
> offering" option, change the root disk size to a value larger than 0. After
> that disable "Compute only disk offering" and attach to existing disk
> offering.
>
> --> via CLI - in the example below the rootdisk is defined as 10 but it
> will not be set as diskofferringid overrides it. So 0 will be the end
> result.
> create serviceoffering name=infra-compute displaytext=infra-compute
> customized=true dynamicscalingenabled=true cpuspeed=2000 mincpunumber=1
> maxcpunumber=4 minmemory=512 maxmemory=2048
> diskofferingid=851dd105-77ee-45d9-8094-807c9824a053 rootdisksize=10
>
> Is there any workaround for cli on how to update the rootdisksize ?
> update serviceoffering does not allow such modification.
>
> Regards,
> Jordan
>
>
>
>

 

Re: compute cannot be used if rot disk size is 0

[Harikrishna Patnala]

Hi Jordan,

I’ve tried these scenarios in 4.17.1 and it seems to be working fine. This 
might be an issue in 4.17 but it is working fine in 4.17.1

I tried the following scenarios,

  1.  Created a service offering with an existing disk offering and deployed VM 
with it from GUI. It worked fine.
  2.  Tried the same from CLI (without rootdisksize). It worked fine.
  3.  Created a service offering with an existing CUSTOM disk offering and 
deployed VM with it from GUI. It worked fine too.

Can you please try upgrading your environment to 4.17.1 ?

Also I did not understand your scenario why rootdisksize comes to picture when 
diskoffering is mapped to a service offering ? Is that a custom disk offering ?

Thanks,
Harikrishna
From: jordan j 
Date: Wednesday, 2 November 2022 at 8:01 PM
To: users@cloudstack.apache.org 
Subject: compute cannot be used if rot disk size is 0
Hey everyone,

I found a bug (4.17.0.1).

if you try to create an instance from compute offering that has root disk
size = 0 the following error appears:
VM Creation failed. Volume size: -1GB is out of allowed range. Max: 1024
Min:1

A few examples when rootdisk size is set as 0:
- when compute offering is created and matched to existing disk offering

--> via GUI same thing as CLI
If a compute offering is created by specifying existing disk offering,
the root disk size is set as 0
Workaround: When creating Compute offering, enable "Compute only disk
offering" option, change the root disk size to a value larger than 0. After
that disable "Compute only disk offering" and attach to existing disk
offering.

--> via CLI - in the example below the rootdisk is defined as 10 but it
will not be set as diskofferringid overrides it. So 0 will be the end
result.
create serviceoffering name=infra-compute displaytext=infra-compute
customized=true dynamicscalingenabled=true cpuspeed=2000 mincpunumber=1
maxcpunumber=4 minmemory=512 maxmemory=2048
diskofferingid=851dd105-77ee-45d9-8094-807c9824a053 rootdisksize=10

Is there any workaround for cli on how to update the rootdisksize ?
update serviceoffering does not allow such modification.

Regards,
Jordan

 

Re: Usage Type Volumes - Use Case

[Harikrishna Patnala]

Hi Ricardo,

The tags in the usage record response are actually the "Resource tags" and not 
the tags that we set on the disk offering.

I don't think we can list disk offering tags in the usage records now, we will 
have to query for the disk offering separately and looks for tags. You can also 
set resource tags for the volumes in case you want to organise the volumes 
based on their type. Please check 
https://docs.cloudstack.apache.org/en/latest/adminguide/management.html#using-tags-to-organize-resources-in-the-cloud

Hope this helps.

Regards,
Harikrishna

From: Ricardo Pertuz 
Sent: Wednesday, August 17, 2022 2:22 AM
To: users@cloudstack.apache.org 
Subject: Re: Usage Type Volumes - Use Case

Hi ACS Team

Any idea how to set up the tags in the output of the usage records shown below?

greetings

From: Ricardo Pertuz 
Date: Saturday, 13 August 2022, 9:35 AM
To: "users@cloudstack.apache.org" 
Subject: Re: Usage Type Volumes - Use Case

I have follow the procedure and it’s working very well, thanks, however in the 
usage records the tag field is null. I will need to set that tag for proper 
billing, any idea?

  "description": "Volume usage for DATA-7665 
(49825f4f--42d1-x-e18fd5dcaef7) with disk offering NVMe Disk 
(026c74b1---a202-0ed113211f00) and size (10.00 GB) 10737418240",
  "domain": "",
  "domainid": "9c96ec87--4a24--6f9d074ec871",
  "enddate": "2022-08-12'T'23:59:59-05:00",
  "offeringid": "026c74b1--4786--0ed113211f00",
  "project": "624cc0abe8d6bf5a65c0518d",
  "projectid": "64992e22-0c30--bf6e-c038e5d7121e",
  "rawusage": "12.441389",
  "size": 10737418240,
  "startdate": "2022-08-12'T'00:00:00-05:00",
  "tags": [],
  "usage": "12.441389 Hrs",
  "usageid": "49825f4f--42d1--e18fd5dcaef7",
  "usagetype": 6,
  "zoneid": "33fcacd8--48e2--bfa52a2fd68b"
},

Regards

From: Ricardo Pertuz 
Date: Thursday, 11 August 2022, 9:46 PM
To: "users@cloudstack.apache.org" 
Subject: Re: Usage Type Volumes - Use Case

Thanks Alex for your quick reply. That tag will appear in the cloud usage 
record tag field? I need that for proper billing.

Regards,
Ricardo


From: Alex Mattioli 
Sent: Thursday, August 11, 2022 9:41:09 PM
To: users@cloudstack.apache.org 
Subject: RE: Usage Type Volumes - Use Case

Hi Ricardo,

You set the tag, say "HDD", on the storage offering and on the primary storage 
which you want to use for HDD, then do the same for all other storage types. 
When creating a volume the end user will select the offering "HDD, SATA or 
NVMe" and ACS will place the volume in a storage pool with the matching tag. 
That's all for disk volumes.
If you want the root disk to go to a certain storage pool then you need to set 
the storage tag in the compute offering.

Hope that helps, feel free to ask further, I've done a lot of work with storage 
tags.

Cheers,
Alex




 


-Original Message-
From: Ricardo Pertuz 
Sent: 11 August 2022 22:57
To: users@cloudstack.apache.org
Subject: Usage Type Volumes - Use Case

Hi all,

In my cluster I would like to have many primary storages with different types: 
HDD, SATA and NVMe, how can I differentiate between them in the usage records? 
I see a tag field, but not so sure where to set it.

BR,

Ricardo

Re: Unable to login to GUI onto second management server

[Harikrishna Patnala]

Glad that worked for you, Andrei.

Regards,
Harikrishna

From: Andrei Mikhailovsky 
Sent: Tuesday, August 2, 2022 8:12 PM
To: users 
Cc: Harikrishna Patnala 
Subject: Re: Unable to login to GUI onto second management server

I have followed the instructions from 
https://www.shapeblue.com/dynamic-roles-in-cloudstack/ and can confirm that 
after running the migration python script I was able to login to the new 
management server.

Perhaps the installation manuals for the multiple management server setup 
should mention the above instructions for the ACS servers that were crated 
before 4.9.x. In my case, I've installed ACS back in 2012 and didn't update the 
permissions structure

Thanks everyone for looking into this issue.

Andrei


 

- Original Message -
> From: "Andrei Mikhailovsky" 
> To: "users" 
> Cc: "Harikrishna Patnala" 
> Sent: Tuesday, 2 August, 2022 15:49:55
> Subject: Re: Unable to login to GUI onto second management server

> It seems that my issue is closely related to the issue discussed here:
> https://github.com/apache/cloudstack/issues/3200
>
> I will investigate this further
>
> Andrei
>
> ----- Original Message -
>> From: "Andrei Mikhailovsky" 
>> To: "Harikrishna Patnala" 
>> Cc: "users" 
>> Sent: Sunday, 31 July, 2022 22:56:31
>> Subject: Re: Unable to login to GUI onto second management server
>
>> Hi Harikrishna,
>>
>> Tried the below, but still have the same issue.
>>
>> also, after trying what you've suggested, I've started the old management 
>> server
>> and I was still able to login. not sure if the host setting does anything 
>> login
>> related...
>>
>> Andrei
>>
>>> From: "Harikrishna Patnala" 
>>> To: "Andrei Mikhailovsky" 
>>> Cc: "users" 
>>> Sent: Thursday, 28 July, 2022 09:54:39
>>> Subject: Re: Unable to login to GUI onto second management server
>>
>>> Hi Andrei,
>>
>>> Can you please also try the below steps? I'm just making sure all pointers 
>>> are
>>> to the new management server only.
>>
>>> 1. Keep only the new management server IP in the host configuration.
>>> 2. Stop the old management server
>>> 3. Restart the new management server
>>> Thanks,
>>> Harikrishna
>>
>>> From: Andrei Mikhailovsky 
>>> Sent: Wednesday, July 27, 2022 6:45 PM
>>> To: Harikrishna Patnala 
>>> Cc: users 
>>> Subject: Re: Unable to login to GUI onto second management server
>>> Hi Harikrishna,
>>
>>> I have added the new management server IP address into the host 
>>> configuration
>>> from the gui. It now shows:
>>
>>> host The ip address of management server. This can also accept 
>>> comma separated
>>> addresses.   Advanced
>>> 192.168.169.13,192.168.169.21
>>
>>> After that I've started the new management server and unfortunately, I still
>>> have the same issue.
>>
>>> I have also noticed that after starting the new management server, the table
>>> mshost has been updated to reflect the server status as Up.:
>>
>>>| 4 | 115129173025114 | 1658099918669 | ais-cloudhost13.csprdc.arhont.com |
>>>| 98405826-0861-11ea-a1da-8003fe80 | Up | 4.16.1.0 | 127.0.0.1 | 9090 |
>>> | 2022-07-27 13:10:05 | NULL | 0 |
>>>| 5 | 165004275141402 | 1658927302926 | ais-compute1.cloud.arhont.com |
>>>| 0d1522a5-5d08-46af-b59c-b577aa22e9bb | Up | 4.16.1.0 | 192.168.169.21 | 
>>>9090 |
>>> | 2022-07-27 13:08:32 | NULL | 0 |
>>
>>> Anything else I should try?
>>
>>> Thanks
>>
>>> Andrei
>>
>>>> From: "Harikrishna Patnala" 
>>>> To: "Andrei Mikhailovsky" , "users"
>>>> 
>>>> Sent: Wednesday, 27 July, 2022 07:21:24
>>>> Subject: Re: Unable to login to GUI onto second management server
>>
>>>> Hi Andrei,
>>
>>>> If the purpose of the second management server is about migration please 
>>>> ignore
>>>> the previous reply.
>>
>>>> You have the right pointer to the procedure and I hope you have followed 
>>>> it.
>>
>>>> Please try to provide the following information.
>>
>>>> 1. Is the old management server also in the 4.16.1 version?
>>>>2. Which database.properties file you have changed to point to the n

Re: [PROPOSE] CloudStack 4.17.1.0 release and RM

[Harikrishna Patnala]

Looks good Abhishek and thanks for volunteering.

Regards,
Harikrishna

From: Abhishek Kumar 
Sent: Tuesday, August 2, 2022 11:07 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: [PROPOSE] CloudStack 4.17.1.0 release and RM

Hi all,

I would like to propose and put myself forward as the release manager for the 
4.17.1.0 release. My colleague Nicolas Vazquez will support me as the co-RM for 
the PR reviews/tests/merges, and others are welcome to support as well.
We can keep the scope limited to include only bugs, critical issues and fixes 
for a stable release. I see about 89 closed issues/PRs already on the 4.17.1.0 
milestone[1] and some 24 items are remaining.

I propose the following timeline, aiming to cut the first RC around the end of 
August.
 - ~3 weeks from now till late August 2022 (Ongoing): Accept all bugs, 
issues and minor improvements allowed in LTS [2]
 - 1 week: Accept only critical/blocker fixes, stabilize 4.17 branch
 - end-August 2022 and onwards: Cut 4.17.1.0 RC1 and further RCs if 
necessary, start/conclude vote, and finish release work

Please let me know if you have any thoughts/comments.

[1] https://github.com/apache/cloudstack/milestone/25
[2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS

Regards,
Abhishek




 

Re: Unable to login to GUI onto second management server

[Harikrishna Patnala]

Hi Andrei,

Can you please also try the below steps? I'm just making sure all pointers are 
to the new management server only.

  1.  Keep only the new management server IP in the host configuration.
  2.  Stop the old management server
  3.  Restart the new management server

Thanks,
Harikrishna

From: Andrei Mikhailovsky 
Sent: Wednesday, July 27, 2022 6:45 PM
To: Harikrishna Patnala 
Cc: users 
Subject: Re: Unable to login to GUI onto second management server

Hi Harikrishna,

I have added the new management server IP address into the host configuration 
from the gui. It now shows:

hostThe ip address of management server. This can also accept comma 
separated addresses.Advanced
192.168.169.13,192.168.169.21


After that I've started the new management server and unfortunately, I still 
have the same issue.

I have also noticed that after starting the new management server, the table 
mshost has been updated to reflect the server status as Up.:


|  4 | 115129173025114 | 1658099918669 | ais-cloudhost13.csprdc.arhont.com | 
98405826-0861-11ea-a1da-8003fe80 | Up| 4.16.1.0 | 127.0.0.1  |  
   9090 | 2022-07-27 13:10:05 | NULL|   0 |
|  5 | 165004275141402 | 1658927302926 | ais-compute1.cloud.arhont.com | 
0d1522a5-5d08-46af-b59c-b577aa22e9bb | Up| 4.16.1.0 | 192.168.169.21 |  
   9090 | 2022-07-27 13:08:32 | NULL|   0 |

Anything else I should try?

Thanks

Andrei

____
From: "Harikrishna Patnala" 
To: "Andrei Mikhailovsky" , "users" 

Sent: Wednesday, 27 July, 2022 07:21:24
Subject: Re: Unable to login to GUI onto second management server
Hi Andrei,

If the purpose of the second management server is about migration please ignore 
the previous reply.

You have the right pointer to the procedure and I hope you have followed it.

Please try to provide the following information.

  1.  Is the old management server also in the 4.16.1 version?
  2.  Which database.properties file you have changed to point to the new 
database ?
  3.  Can you check the database table "configuration", what is the value for 
the configuration with the name "host", is it your new MS host address ?
  4.  Also, check the "mshost" table in the database if it is pointing to the 
new management server.

Regards,
Harikrishna






From: Andrei Mikhailovsky 
Sent: Monday, July 25, 2022 7:46 PM
To: users 
Cc: Harikrishna Patnala 
Subject: Re: Unable to login to GUI onto second management server


Hi Harikrishna,

Having read the links that you've sent I am not sure that my issues are 
related. Perhaps I should have explained my current set up / intensions a bit 
more. My main reasons for adding the multiple management servers is not to 
provide the HA / load balancing, but rather to migrate the current management 
server from old hardware to the new one. I was referring to the post sent by 
Andrija Panic 
(https://www.mail-archive.com/users@cloudstack.apache.org/msg32889.html) where 
Andrija has suggested that one should install the second management server, 
connect it to the database, move the database to a new server and change the 
database properties to point the new management server to the new db.

In my tests, I have installed the second management server without any 
proxy/load balancing and I tried to connect and authenticate directly to the IP 
address of the second management server. I've tried it with the primary 
management server switched on and off, but I still have the same issues. If I 
am connecting directly to the new management server IP, I don't see how having 
nginx proxy settings changes would fix my issue. Also, I have not seen anything 
in the documentation that explicitly requires having a proxy if you install the 
second management server.

Why do you think my issue relates to CORS?

Andrei




 

- Original Message -
> From: "Harikrishna Patnala" 
> To: "users" 
> Sent: Wednesday, 20 July, 2022 05:10:13
> Subject: Re: Unable to login to GUI onto second management server

> Hi Andrei,
>
> This looks to me like a CORS issue.
>
> Have you set up any load balancer for these management servers. There is a
> section
> http://docs.cloudstack.apache.org/en/4.16.1.0/adminguide/reliability.html#management-server-load-balancing
> which you need to configure so that you will not face issues with HA and 
> agents
> later on.
>
>
> You may need to consider setting cookies like below.
>
> If you are using nginx, try with  "proxy_cookie_path / "/; Secure;
> SameSite=None;";" and a similar thing should work haproxy too.
>
> I got this reference from a previous discussion on a PR
> https://github.com/apache/cloudstack-primate/pull/898#issuecomment-760227366,
> please refer

Re: Unable to login to GUI onto second management server

[Harikrishna Patnala]

Hi Andrei,

If the purpose of the second management server is about migration please ignore 
the previous reply.

You have the right pointer to the procedure and I hope you have followed it.

Please try to provide the following information.

  1.  Is the old management server also in the 4.16.1 version?
  2.  Which database.properties file you have changed to point to the new 
database ?
  3.  Can you check the database table "configuration", what is the value for 
the configuration with the name "host", is it your new MS host address ?
  4.  Also, check the "mshost" table in the database if it is pointing to the 
new management server.

Regards,
Harikrishna

From: Andrei Mikhailovsky 
Sent: Monday, July 25, 2022 7:46 PM
To: users 
Cc: Harikrishna Patnala 
Subject: Re: Unable to login to GUI onto second management server


Hi Harikrishna,

Having read the links that you've sent I am not sure that my issues are 
related. Perhaps I should have explained my current set up / intensions a bit 
more. My main reasons for adding the multiple management servers is not to 
provide the HA / load balancing, but rather to migrate the current management 
server from old hardware to the new one. I was referring to the post sent by 
Andrija Panic 
(https://www.mail-archive.com/users@cloudstack.apache.org/msg32889.html) where 
Andrija has suggested that one should install the second management server, 
connect it to the database, move the database to a new server and change the 
database properties to point the new management server to the new db.

In my tests, I have installed the second management server without any 
proxy/load balancing and I tried to connect and authenticate directly to the IP 
address of the second management server. I've tried it with the primary 
management server switched on and off, but I still have the same issues. If I 
am connecting directly to the new management server IP, I don't see how having 
nginx proxy settings changes would fix my issue. Also, I have not seen anything 
in the documentation that explicitly requires having a proxy if you install the 
second management server.

Why do you think my issue relates to CORS?

Andrei




 

- Original Message -
> From: "Harikrishna Patnala" 
> To: "users" 
> Sent: Wednesday, 20 July, 2022 05:10:13
> Subject: Re: Unable to login to GUI onto second management server

> Hi Andrei,
>
> This looks to me like a CORS issue.
>
> Have you set up any load balancer for these management servers. There is a
> section
> http://docs.cloudstack.apache.org/en/4.16.1.0/adminguide/reliability.html#management-server-load-balancing
> which you need to configure so that you will not face issues with HA and 
> agents
> later on.
>
>
> You may need to consider setting cookies like below.
>
> If you are using nginx, try with  "proxy_cookie_path / "/; Secure;
> SameSite=None;";" and a similar thing should work haproxy too.
>
> I got this reference from a previous discussion on a PR
> https://github.com/apache/cloudstack-primate/pull/898#issuecomment-760227366,
> please refer to it if it helps solve your problem.
>
>
> Regards,
> Harikrishna
> 
> From: Andrei Mikhailovsky 
> Sent: Tuesday, July 19, 2022 4:06 PM
> To: users 
> Subject: Re: Unable to login to GUI onto second management server
>
> Bump please
>
>
>
>
>
>
> - Original Message -
>> From: "Andrei Mikhailovsky" 
>> To: "users" 
>> Sent: Monday, 18 July, 2022 11:45:05
>> Subject: Unable to login to GUI onto second management server
>
>> Hello,
>>
>> I've recently installed a second management server ACS 4.16.1 following the
>> installation instructions in section Additional Management Servers from the
>> official documentation ( [
>> http://docs.cloudstack.apache.org/en/4.16.1.0/installguide/management-server/index.html
>> |
>> http://docs.cloudstack.apache.org/en/4.16.1.0/installguide/management-server/index.html
>> ] ). I've installed the Ubuntu package on the second server of the same 
>> version
>> as the primary management server. Configured the database with
>> cloudstack-setup-databases command followed by running
>> cloudstack-setup-management as per the documentation. There were no errors in
>> the process and the cloudstack-management.service seems to have started just
>> fine. The second ACS management service connected to the same database as the
>> primary one and the login web GUI loaded just fine. The management server 
>> logs
>> seems to show no apparent errors in the startup. The only exceptions I was
>> getting in the logs were from t

Re: Unable to login to GUI onto second management server

[Harikrishna Patnala]

Hi Andrei,

This looks to me like a CORS issue.

Have you set up any load balancer for these management servers. There is a 
section 
http://docs.cloudstack.apache.org/en/4.16.1.0/adminguide/reliability.html#management-server-load-balancing
 which you need to configure so that you will not face issues with HA and 
agents later on.


You may need to consider setting cookies like below.

If you are using nginx, try with  "proxy_cookie_path / "/; Secure; 
SameSite=None;";" and a similar thing should work haproxy too.

I got this reference from a previous discussion on a PR 
https://github.com/apache/cloudstack-primate/pull/898#issuecomment-760227366, 
please refer to it if it helps solve your problem.


Regards,
Harikrishna

From: Andrei Mikhailovsky 
Sent: Tuesday, July 19, 2022 4:06 PM
To: users 
Subject: Re: Unable to login to GUI onto second management server

Bump please




 

- Original Message -
> From: "Andrei Mikhailovsky" 
> To: "users" 
> Sent: Monday, 18 July, 2022 11:45:05
> Subject: Unable to login to GUI onto second management server

> Hello,
>
> I've recently installed a second management server ACS 4.16.1 following the
> installation instructions in section Additional Management Servers from the
> official documentation ( [
> http://docs.cloudstack.apache.org/en/4.16.1.0/installguide/management-server/index.html
> |
> http://docs.cloudstack.apache.org/en/4.16.1.0/installguide/management-server/index.html
> ] ). I've installed the Ubuntu package on the second server of the same 
> version
> as the primary management server. Configured the database with
> cloudstack-setup-databases command followed by running
> cloudstack-setup-management as per the documentation. There were no errors in
> the process and the cloudstack-management.service seems to have started just
> fine. The second ACS management service connected to the same database as the
> primary one and the login web GUI loaded just fine. The management server logs
> seems to show no apparent errors in the startup. The only exceptions I was
> getting in the logs were from the host agents showing status Disconnected.
>
> So, I have tried to login (using domain and ROOT login accounts) to the web 
> gui
> of the second management server and the page just hangs after I enter the
> credentials and press the Login button. I've tried several different browsers
> at no avail. Supplying the incorrect login credentials produce the error
> though. The management server logs do not show any errors during the login
> process. In fact, it seems that all commands produce " is allowed to perform
> API calls: 0.0.0.0/0,::/0 " message in the logs. There are no exceptions that 
> I
> can see either:
>
> --
>
>
> 2022-07-18 01:17:33,743 DEBUG [c.c.a.ApiServlet] 
> (qtp681094281-285:ctx-0cf08734)
> (logid:94b277ba) ===START=== 192.168.169.251 -- POST
> 2022-07-18 01:17:33,750 DEBUG [c.c.u.AccountManagerImpl]
> (qtp681094281-285:ctx-0cf08734) (logid:94b277ba) Attempting to log in user:
> andrei in domain 1
> 2022-07-18 01:17:33,752 DEBUG [o.a.c.s.a.PBKDF2UserAuthenticator]
> (qtp681094281-285:ctx-0cf08734) (logid:94b277ba) Retrieving user: andrei
> 2022-07-18 01:17:33,969 DEBUG [c.c.u.AccountManagerImpl]
> (qtp681094281-285:ctx-0cf08734) (logid:94b277ba) CIDRs from which account
> 'Acct[06eedc2c-65f2-11e3-9bd1-d8d38559b2d0-admin_group] -- Account {"id": 2,
> "name": "admin_group", "uuid": "06eedc2c-65f2-11e3-9bd1-d8d38559b2d0"}' is
> allowed to perform API calls: 0.0.0.0/0,::/0
> 2022-07-18 01:17:33,969 DEBUG [c.c.u.AccountManagerImpl]
> (qtp681094281-285:ctx-0cf08734) (logid:94b277ba) User: andrei in domain 1 has
> successfully logged in
> 2022-07-18 01:17:34,011 INFO [c.c.a.ApiServer] (qtp681094281-285:ctx-0cf08734)
> (logid:94b277ba) Current user logged in under Etc/UTC timezone
> 2022-07-18 01:17:34,011 INFO [c.c.a.ApiServer] (qtp681094281-285:ctx-0cf08734)
> (logid:94b277ba) Timezone offset from UTC is: 0.0
> 2022-07-18 01:17:34,015 DEBUG [c.c.a.ApiServlet] 
> (qtp681094281-285:ctx-0cf08734)
> (logid:94b277ba) ===END=== 192.168.169.251 -- POST
> 2022-07-18 01:17:34,123 DEBUG [c.c.a.ApiServlet] 
> (qtp681094281-280:ctx-fafe166c)
> (logid:41d7b4d5) ===START=== 192.168.169.251 -- GET
> listall=true&command=listZones&response=json
> 2022-07-18 01:17:34,133 DEBUG [c.c.a.ApiServer] (qtp681094281-280:ctx-fafe166c
> ctx-2269cc31) (logid:41d7b4d5) CIDRs from which account
> 'Acct[06eedc2c-65f2-11e3-9bd1-d8d38559b2d0-admin_group] -- Account {"id": 2,
> "name": "admin_group", "uuid": "06eedc2c-65f2-11e3-9bd1-d8d38559b2d0"}' is
> allowed to perform API calls: 0.0.0.0/0,::/0
> 2022-07-18 01:17:34,133 DEBUG [c.c.a.ApiServlet] 
> (qtp681094281-28:ctx-0906d03f)
> (logid:56b10f23) ===START=== 192.168.169.251 -- GET
> command=listApis&response=json
> 2022-07-18 01:17:34,137 DEBUG [c.c.a.ApiServlet] 
> (qtp681094281-280:ctx-fafe166c
> ctx-2269cc31) (logid:41d7b4d5) ===END=== 192.168.169.251 -- GET
> listall=true&comma

Re: endless starting state

[Harikrishna Patnala]

Hi Ricardo,

I assume the complete reboot means the CloudStack management server 
restart/reboot or is it a KVM host reboot ?

Please check for the following if anything can be found.

  1.  Check for hosts status from CloudStack UI if it is UP
  2.  Check if these VMs are there and running on the host
  3.  Check if hosts have enough capacity
  4.  Check if new VMs can be deployed as well

You can focus on one of the VM's id and look for the last log related to the VM 
wrt any operation, which may give us some hints.

Thanks,
Harikrishna

From: Ricardo Pertuz 
Sent: Friday, July 8, 2022 8:12 AM
To: users@cloudstack.apache.org 
Subject: endless starting state

Hi team,

After a complete reboot, many vms are stuck in an endless starting state, no 
error in logs, what else can be checked?

ACS: 4.15.2
Hyp: KVM

Regards,


 

Re: Deploy multiple management server

[Harikrishna Patnala]

Hello,

In CloudStack installation guides, we have the steps to set up a management 
server[1] and also to set up additional management servers[2].

Please have a look and give it try and let us know if you face any issues.

[1]http://docs.cloudstack.apache.org/en/latest/installguide/management-server/#management-server-installation

[2]http://docs.cloudstack.apache.org/en/latest/installguide/management-server/#additional-management-servers
Management Server Installation — Apache CloudStack 4.17.0.0 documentation - 
Apache CloudStack 4.16.0.0 
documentation
RPM package repository¶. There is a RPM package repository for CloudStack so 
you can easily install on RHEL and SUSE based platforms. If you’re using an 
RPM-based system, you’ll want to add the Yum repository so that you can install 
CloudStack with Yum.
docs.cloudstack.apache.org
Regards,
Harikrishna

From: technologyrss.mail 
Sent: Tuesday, July 5, 2022 5:30 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Deploy multiple management server

*Hi,*

I want to deploy multiple management server, please suggest me how to
deploy?
ACS version 4.17, and Server all Centos7.9

--

*Thanks & Regards.*

*Support Admin*



*Facebook  | Twitter
 | YouTube
 | LinkedIn
*

*Address : *63-B, D.I.T Road, Malibagh Chowdhury Para

(Ground Floor of NCC Bank)

Dhaka-1219, Bangladesh

*Mob :* +88 01716915504

*Email :* support.ad...@technologyrss.com

*Web :* www.technologyrss.com

 

Re: Getting error when try to stop any VM

[Harikrishna Patnala]

Hi Parvej,

Can you please look for some other error message or stack trace (which says 
about the reason for the exception) in the log above the error message that you 
have shared?

Also please check if the KVM host where the VM is residing is in a good state 
or not?

Thanks,
Harikrishna

From: Nazmul Parvej 
Sent: Monday, July 4, 2022 9:24 AM
To: users@cloudstack.apache.org 
Cc: Product Development | BEXIMCO IT 
Subject: Getting error when try to stop any VM

Hello Team,

I am getting the following error when I going to stop any VM. After the
second attempt, it normally stopped. Is anyone facing this issue? Please
advise.
I am using KVM Hypervisors and my CloudStack version is 4.17

*Error at WebGUI*
Stop instance
(test-vm) Unable to stop VM instance {id: "418", name: "i-2-418-VM", uuid:
"f00f817e-d4bc-4251-bd49-fa91def916c9", type="User"}

*Error at Management Server Log*
2022-06-29 16:50:51,213 WARN  [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-109:ctx-38407e2f job-3805/job-3806 ctx-5350f6fc)
(logid:a09ab2ed) Unable to stop vm VM instance {id: "418", name:
"i-2-418-VM", uuid: "f00f817e-d4bc-4251-bd49-fa91def916c9", type="User"}
2022-06-29 16:50:51,235 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-109:ctx-38407e2f job-3805/job-3806 ctx-5350f6fc)
(logid:a09ab2ed) Invocation exception, caused by:
com.cloud.utils.exception.CloudRuntimeException: Unable to stop VM instance
{id: "418", name: "i-2-418-VM", uuid:
"f00f817e-d4bc-4251-bd49-fa91def916c9", type="User"}
2022-06-29 16:50:51,237 INFO  [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-109:ctx-38407e2f job-3805/job-3806 ctx-5350f6fc)
(logid:a09ab2ed) Rethrow exception
com.cloud.utils.exception.CloudRuntimeException: Unable to stop VM instance
{id: "418", name: "i-2-418-VM", uuid:
"f00f817e-d4bc-4251-bd49-fa91def916c9", type="User"}
2022-06-29 16:50:51,237 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-109:ctx-38407e2f job-3805/job-3806) (logid:a09ab2ed)
Unable to complete AsyncJobVO: {id:3806, userId: 2, accountId: 2,
instanceType: null, instanceId: null, cmd: com.cloud.vm.VmWorkStop,
cmdInfo:
rO0ABXNyABdjb20uY2xvdWQudm0uVm1Xb3JrU3RvcALQ4GymiWjjAgABWgAHY2xlYW51cHhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAACAAIBonQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwA,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
result: null, initMsid: 200122649134120, completeMsid: null, lastUpdated:
null, lastPolled: null, created: Wed Jun 29 16:50:45 BDT 2022, removed:
null}, job origin:3805
2022-06-29 16:50:51,309 ERROR [c.c.a.ApiAsyncJobDispatcher]
(API-Job-Executor-76:ctx-b8ad6bbc job-3805) (logid:a09ab2ed) Unexpected
exception while executing
org.apache.cloudstack.api.command.admin.vm.StopVMCmdByAdmin
Yours sincerely,


Nazmul Parvej
Deputy Manager, Product Development
IT Division

Bangladesh Export Import Company Ltd.

Level-9, SAM Tower, Plot #4, Road #22, Gulshan-1, Dhaka-1212,Bangladesh

Tel: +880 9609 000 999, +880 2 5881 5559, Ext: 14193, Fax:  +880 2 
95757

Cell: +8801787680841, Email: nazmul.par...@bol-online.com, Web:
www.bol-online.com

 

Re: Regarding the VPC offering

[Harikrishna Patnala]

Hi Vivek,

For the default VPC offering, in the database I see both "InternalLbVM" and 
"VpcVirtualRouter" as the providers for the LB service. Though the list 
response in UI only shows "IntenalLbVM".  That is the reason you could create 
both internal and public LB tiers.

While creating a new VPC offering from UI we are providing only one option to 
select the provider. This could be a UI improvement to provide option to select 
multiple providers.

You can try API or Cloudmonkey to create a VPC offering with multiple 
providers. I gave it a quick try something like below.

(localcloud) 🐱 > create vpcoffering displaytext="test" name="test" 
supportedservices=Lb serviceProviderList[0].service=Lb 
serviceProviderList[0].provider=VpcVirtualRouter 
serviceProviderList[1].service=Lb serviceProviderList[1].provider=InternalLbVm


Hope this helps.

Thanks,
Harikrishna



From: Vivek Kumar 
Sent: Wednesday, June 29, 2022 5:28 PM
To: users@cloudstack.apache.org 
Subject: Regarding the VPC offering

Hello Folks,

ACS comes with a default VPC offering which has following service enabled -

Supported Services
Dhcp : VpcVirtualRouter
Lb : InternalLbVm
NetworkACL : VpcVirtualRouter
PortForwarding : VpcVirtualRouter
Vpn : VpcVirtualRouter
Dns : VpcVirtualRouter
SourceNat : VpcVirtualRouter
StaticNat : VpcVirtualRouter
UserData : VpcVirtualRouter


— So using the default offering I can create all three type of tiers - i.e 1) 
Public LB tier, 2) Internal LB Tier and 3) NoLB Tier.  Recently I have created 
a custom VPC offering with specific systemoffering_id, below are the services - 
which is identical to the default vpc offering -

Supported Services
Dhcp : VpcVirtualRouter
UserData : VpcVirtualRouter
StaticNat : VpcVirtualRouter
Vpn : VpcVirtualRouter
PortForwarding : VpcVirtualRouter
Dns : VpcVirtualRouter
Lb : InternalLbVm
NetworkACL : VpcVirtualRouter
SourceNat : VpcVirtualRouter

— But from this offering I am not able to create public LB tier - it says - 
Service/provider combination Lb/VpcVirtualRouter is not supported by VPC [VPC 
[75-Indiqus-4].  So I created a another vpc offering with Lb:VpcVirtualRouter , 
below are the services -

Dhcp : VpcVirtualRouter
UserData : VpcVirtualRouter
StaticNat : VpcVirtualRouter
Vpn : VpcVirtualRouter
PortForwarding : VpcVirtualRouter
Dns : VpcVirtualRouter
Lb : VpcVirtualRouter
NetworkACL : VpcVirtualRouter
SourceNat : VpcVirtualRouter

But in this VPC offering I am not able to create internal LB tiers - it says - 
Lb/InternalLbVm is not supported by VPC [VPC [54-Indiqus-test3]   So How come I 
am able to create all kind of Tiers with default vpc offering.





Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

+ 91 7503460090 
vivek.ku...@indiqus.com 
www.indiqus.com 




--
This message is intended only for the use of the individual or entity to
which it is addressed and may contain confidential and/or privileged
information. If you are not the intended recipient, please delete the
original message and any copy of it from your computer system. You are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited unless proper authorization has been
obtained for such action. If you have received this communication in error,
please notify the sender immediately. Although IndiQus attempts to sweep
e-mail and attachments for viruses, it does not guarantee that both are
virus-free and accepts no liability for any damage sustained as a result of
viruses.

 

Re: How To Increase RAM on SSVM or CPVM

[Harikrishna Patnala]

Hi,

  1.  Create a new system offering based on your RAM need and others
  2.  Stop the SSVM/CPVM
  3.  Scale the SSVM/CPVM to the newly created system offering

Hope this helps.

Thanks,
Harikrishna


From: technologyrss.mail 
Sent: Sunday, June 19, 2022 3:03 PM
To: users@cloudstack.apache.org ; 
d...@cloudstack.apache.org 
Subject: How To Increase RAM on SSVM or CPVM

Hi,

How To Increase RAM size on SSVM and CPVM.

--

*Thanks & Regards.*

*Support Admin*



*Facebook  | Twitter
 | YouTube
 | LinkedIn
*

*Address : *63-B, D.I.T Road, Malibagh Chowdhury Para

(Ground Floor of NCC Bank)

Dhaka-1219, Bangladesh

*Mob :* +88 01716915504

*Email :* support.ad...@technologyrss.com

*Web :* www.technologyrss.com

 

Re: ACS Upgrade Failed :: Xenserver

[Harikrishna Patnala]

Hi Ranjit,

CloudStack management and usage have to be on the same version, can you please 
check the version of CloudStack usage server and verify if the upgrade to 4.17 
happened properly. If not on 4.17, can you please try to upgrade the usage 
server?

Please paste the exact error from the management server or usage server logs 
that you are seeing.

Thanks,
Harikrishna


From: Ranjit Jadhav 
Sent: Saturday, June 18, 2022 5:53 PM
To: users@cloudstack.apache.org ; dev 

Subject: ACS Upgrade Failed :: Xenserver

Hello,

While attempting to upgrade ACS from 4.16.1 to 4.17 on Xenserver, we faced
the following issue. It appears that "cloudstack-management" and
"cloudstack-usage" requires different versions of cloudstack-common.

With cloudstack-common=4.17 Management, services are working but Usage
services are asking for 4.16.1.0~bionic

==
The following packages have unmet dependencies:
 cloudstack-usage : Depends: cloudstack-common (= 4.16.1.0~bionic) but
4.17.0.0~bionic is to be installed
E: Unable to correct problems, you have held broken packages.
==

We followed the steps below to upgrade ACS

https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.16.html#system-vms-and-virtual-routers

The server is setup on Ubuntu 18.04 with Xenserver(VM on Xcp-ng)

Any guidance would be appreciated.

Thank you

 

Re: XenServer Agent is not coming up after upgrading from 7.1 to 8.2

[Harikrishna Patnala]

Hi Vivek,

Please check the CloudStack detected Xenserver version in either UI or database.

You may try an option to reinitialize the Xenserver host by clearing the tags 
on the host and try reconnecting from CloudStack UI.
Run the following command on Xenserver and reconnect the host.

# for host in $(xe host-list | grep ^uuid | awk '{print $NF}') ; do xe 
host-param-clear uuid=$host param-name=tags; done;

Hope this helps.

Regards,
Harikrishna

From: Suresh Anaparti 
Sent: Wednesday, June 1, 2022 3:07 PM
To: users@cloudstack.apache.org 
Subject: Re: XenServer Agent is not coming up after upgrading from 7.1 to 8.2

Hi Vivek,

This discussion thread might provide you some inputs: 
https://lists.apache.org/thread/7q6yybm3qcms21qcd8945kvrygpr1v86

Also, check the docs here: 
http://docs.cloudstack.apache.org/en/4.16.1.0/installguide/hypervisor/xenserver.html#upgrading-xenserver-versions,
 and see if you have missed any upgrade step.


Regards,
Suresh

On 01/06/22, 2:17 PM, "Vivek Kumar"  wrote:

Hello Guys,


We have recently upgraded our XenServer  from 7.1 to 8.2. We are using 
CloudStack 4.16.1. But after the upgradation my status of host is showing 
alert. I have gone through the logs getting below error. Can someone help me 
out for this.



—



rZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw&command=listSystemVms&response=json&signatureVersion=3&expires=2022-06-01T08%3A43%3A33%2B&signature=x7KQg4LW2XPtTf%2BHHVn0Fm599xA%3D
2022-06-01 14:00:51,613 DEBUG [c.c.u.s.SSHCmdHelper] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Executing cmd: rm -f 
/opt/xensource/sm/hostvmstats.py 
/opt/xensource/bin/copy_vhd_to_secondarystorage.sh 
/opt/xensource/bin/copy_vhd_from_secondarystorage.sh 
/opt/xensource/bin/create_privatetemplate_from_snapshot.sh 
/opt/xensource/bin/vhd-util /opt/cloud/bin/copy_vhd_to_secondarystorage.sh 
/opt/cloud/bin/copy_vhd_from_secondarystorage.sh 
/opt/cloud/bin/create_privatetemplate_from_snapshot.sh /opt/cloud/bin/vhd-util
2022-06-01 14:00:52,750 DEBUG [c.c.a.ApiServlet] 
(qtp1850777594-19:ctx-5c391d12) (logid:fb2dbf4b) ===START===  172.31.29.44 -- 
GET  
listall=True&apiKey=W0EWPYRPQu51YPDQ8s_0b4wDDuSqrZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw&command=listVpnConnections&response=json&signatureVersion=3&expires=2022-06-01T08%3A43%3A35%2B&signature=TBKYjvgMLESFTna9iXeGTJdKtc0%3D
2022-06-01 14:00:52,756 DEBUG [c.c.a.ApiServer] 
(qtp1850777594-19:ctx-5c391d12 ctx-9cd12123) (logid:fb2dbf4b) CIDRs from which 
account 'Acct[0d808973-19be-11eb-9555-005056961200-admin] -- Account {"id": 2, 
"name": "admin", "uuid": "0d808973-19be-11eb-9555-005056961200"}' is allowed to 
perform API calls: 0.0.0.0/0,::/0
2022-06-01 14:00:52,761 DEBUG [c.c.a.ApiServlet] 
(qtp1850777594-19:ctx-5c391d12 ctx-9cd12123 ctx-6326bb8c) (logid:fb2dbf4b) 
===END===  172.31.29.44 -- GET  
listall=True&apiKey=W0EWPYRPQu51YPDQ8s_0b4wDDuSqrZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw&command=listVpnConnections&response=json&signatureVersion=3&expires=2022-06-01T08%3A43%3A35%2B&signature=TBKYjvgMLESFTna9iXeGTJdKtc0%3D
2022-06-01 14:00:52,862 INFO  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Host 172.31.21.5 
OpaqueRef:d1a2d70a-25bd-37b3-c581-2249ccf88fc0: Host 172.31.21.5 is already 
setup.
2022-06-01 14:00:52,868 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) callHostPlugin failed for cmd: 
setIptables with args  due to The requested plugin could not be found.
2022-06-01 14:00:52,869 WARN  [c.c.h.x.r.w.x.CitrixSetupCommandWrapper] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Unable to setup
com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for 
cmd: setIptables with args  due to The requested plugin could not be found.
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:367)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.setIptables(CitrixResourceBase.java:4706)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixSetupCommandWrapper.execute(CitrixSetupCommandWrapper.java:63)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixSetupCommandWrapper.execute(CitrixSetupCommandWrapper.java:45)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrapper.execute(CitrixRequestWrapper.java:122)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:1758)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(

Re: [ANNOUNCE] Next PMC Chair & VP Apache CloudStack Project - Simon Weller

[Harikrishna Patnala]

Congratulations and good luck, Simon! and Thank you, Gabriel, for all your 
great work.

Regards,
Harikrishna

From: Gabriel Beims Bräscher 
Sent: Thursday, March 17, 2022 3:25 PM
To: users ; dev 
Subject: [ANNOUNCE] Next PMC Chair & VP Apache CloudStack Project - Simon Weller

Hello, all CloudStack community!

It gives me great pleasure to announce that the ASF board last night
accepted
our PMC's nomination of Simon Weller as the next PMC Chair / VP of
the Apache CloudStack project.

I would like to thank everyone for the support I've received over the past
year.
It was a great honor being the PMC Chair of this amazing project/community!

To Simon, my sincere congratulations, and I wish you success in the new
role!
Very well deserved!

Please join me in congratulating Simon, the CloudStack PMC Chair / VP.

Best Regards,
Gabriel Bräscher.

 

Re: [VOTE] Apache CloudStack 4.16.1.0 (RC2)

[Harikrishna Patnala]

+1

Tested on a VMware environment with VM and volume operations on NFS and 
Datastore Cluster storage types and a few network operations.

Thanks,
Harikrishna

From: Rohit Yadav 
Sent: Wednesday, March 2, 2022 1:20 AM
To: dev 
Cc: users 
Subject: Re: [VOTE] Apache CloudStack 4.16.1.0 (RC2)

+1 (binding)

Regards.

From: Gabriel Br?scher 
Sent: Tuesday, March 1, 2022 9:41:25 PM
To: dev 
Cc: users 
Subject: Re: [VOTE] Apache CloudStack 4.16.1.0 (RC2)

+1 on continuing with RC2 Vote.

On Tue, Mar 1, 2022, 17:03 Vladimir Petrov 
wrote:

> Hi all,
>
> Voting +1
>
> I did a lot of upgrade tests with pre-RC, RC1 and RC2 versions, using
> different hypervisors and from different versions (4.11, 4.13, 4.15.2,
> 4.16.0). I also tested main workflows and basic operations and haven't
> found a single issue.
>
> Best wishes,
> Vladi
>
>
> Suresh Anaparti wrote:
>
>
> Hi All,
>
> I have created a 4.16.1.0 release (RC2), with the following artifacts up
> for testing and a vote:
>
> Git Branch and Commit SHA:
> https://github.com/apache/cloudstack/tree/4.16.1.0-RC20220225T1901
> Commit: cad9332082a1f85eedc30cf547ae28224be170c2
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.16.1.0/
>
> PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open until 2nd March 2022.
>
> 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)
>
> For users convenience, the packages from this release candidate (RC2) and
> 4.16.1 systemvm templates are available here:
> https://download.cloudstack.org/testing/4.16.1.0-RC2/
> https://download.cloudstack.org/systemvm/4.16/
>
> Documentation is not published yet, but the following may be referenced
> for upgrade related tests:
> (there's a new 4.16.1 systemvm template to be registered prior to upgrade)
>
> https://github.com/apache/cloudstack-documentation/tree/4.16/source/upgrading/upgrade
>
> NOTES on the issues fixed in this RC2 release:
>
> (these do *NOT* require a full retest if you were testing RC1 already -
> just if you were affected by these issues):
> - https://github.com/apache/cloudstack/issues/6017 (regression in
> register template form
> when select/unselect check boxes using space in keyboard)
> - https://github.com/apache/cloudstack/issues/6026 (affects volumes on
> managed storages when
> stopping or migrating a VM)
> - https://github.com/apache/cloudstack/issues/6038 (regression in SSVM
> scaling down behavior,
> new config 'secstorage.vm.auto.scale.down' added to control scaling down)
>
>
> Regards,
> Suresh
>
>
>
>
>
>
>
>




 

[ANNOUNCE] Apache CloudStack Terraform Provider v0.4.0 Release

[Harikrishna Patnala]

# Apache CloudStack Terraform Provider v0.4.0 Release

Apache CloudStack is proven to be one of the most scalable, free and open-source
cloud computing operating systems for large-scale private,
public, and hybrid clouds. Terraform is an open-source infrastructure as code
software tool that provides a consistent CLI workflow to manage resources in
many cloud services.


To integrate CloudStack with Terraform, we are announcing today the availability
of the latest release of Apache CloudStack Terraform Provider v0.4.0.
This is the first release after it has been brought under the Apache license.


The release includes the following changes:
-  Relicensing with Apache License v2.0
-  Validated and fixed all existing resource creations to work as expected
-  Updated documentation on using and also developing the provider
-  Bug fixes on syncing the data from CloudStack
-  Fixed resource destroy using terraform for some resources


## Downloads and Documentation


The Terraform registry link to install the CloudStack Provider is available at
https://registry.terraform.io/providers/cloudstack/cloudstack/0.4.0


The documentation for the usage of resources to create and interact with
CloudStack is available at
https://registry.terraform.io/providers/cloudstack/cloudstack/0.4.0/docs


The official source code for Apache CloudStack Terraform provider can be
downloaded from
https://github.com/apache/cloudstack-terraform-provider


The documentation for Apache CloudStack Terraform provider's usage is available
at
https://github.com/apache/cloudstack-terraform-provider/wiki


 

[RESULT] [VOTE] Release Apache CloudStack Terraform Provider v0.4.0

[Harikrishna Patnala]

Hi all,

The vote for CloudStack Terraform Provider v0.4.0 *passes* with
3 PMC + 3 non-PMC votes.

+1 (PMC / binding)
3 persons (Rohit, Daan, Boris)

+1 (non binding)
3 persons (Pearl, Vladi, Suresh)

0
none

-1
none

Thanks to everyone participating.

I will now prepare the release announcement to go out after 24-48 hours to give 
the mirrors time to catch up.

Regards,
Harikrishna

 

Re: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0

[Harikrishna Patnala]

Thanks for all testing and votes.

May I request a few more PMC members to test and vote here, we have 2 binding 
votes till now.

Regards,
Harikrishna

From: Pearl d'Silva 
Sent: Monday, January 31, 2022 1:11 PM
To: dev 
Cc: users@cloudstack.apache.org 
Subject: Re: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0

+1

Did some basic lifecycle operations on a VM, network - such as creation, update 
and destroy, adding secondary IP to a VM.
Performed the operations as an admin and a user.
Did similar operations in a project as a user. Also attempted resetting the VMs 
SSH key.
Encountered a small issue with respect to adding a secondary IP to a NIC for a 
VM deployed in a project, but I wouldn't categorize it as a blocker and can be 
addressed in the next release.


Thanks,
Pearl


From: Daan Hoogland 
Sent: Friday, January 28, 2022 9:29 PM
To: dev 
Cc: users@cloudstack.apache.org 
Subject: Re: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0

+1 (binding)

performed similar tests as Rohit but in a dual zone and with a vpc in one
of the zones. Two different configurations one with one zone and one with
both. destroy went fine ;) in the vpc firewall rules would not create. I am
not sure this is a known issue, but the error message is clear, so I'm not
calling it a bug:

"Unable to create firewall rule for the IP address ID=204 as IP is not
associated with any network and no networkId is passed in"

The only weird thing is that the network is not an allowed parameter.


On Fri, Jan 28, 2022 at 9:55 AM Rohit Yadav 
wrote:

> +1 (binding)
>
> I checked the source tarball checksum and gpg signature, and using the RC1
> build was able to test a simple VM deployment in a zone in an isolated
> network with some firewall rules applied, against a KVM based ACS 4.16.0.0
> env.
>
> (note: in my testing, in the first run the firewall application met with
> some failure but on second try of terraform apply it worked, see run log
> below)
>
> Source tarball verification:
> gpg: Signature made Wed Jan 19 15:33:18 2022 IST
> gpg:using RSA key 1031D6946F8A7C4B0C3E9EEFAEA5313845ADC482
> gpg: Good signature from "Harikrishna Patnala (github gpg) <
> harikrishna.patn...@gmail.com>" [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: 1031 D694 6F8A 7C4B 0C3E  9EEF AEA5 3138 45AD C482
>
> Run log for reference:
>
> # terraform apply
>
> Terraform used the selected providers to generate the following execution
> plan. Resource actions are indicated with the
> following symbols:
>   + create
>
> Terraform will perform the following actions:
>
>   # cloudstack_egress_firewall.default will be created
>   + resource "cloudstack_egress_firewall" "default" {
>   + id  = (known after apply)
>   + managed = false
>   + network_id  = (known after apply)
>   + parallelism = 2
>
>   + rule {
>   + cidr_list = [
>   + "10.200.0.0/24",
> ]
>   + icmp_code = (known after apply)
>   + icmp_type = (known after apply)
>   + ports = [
>   + "21",
>   + "22",
>   + "443",
>   + "80",
> ]
>   + protocol  = "tcp"
>   + uuids = (known after apply)
> }
> }
>
>   # cloudstack_firewall.default will be created
>   + resource "cloudstack_firewall" "default" {
>   + id= (known after apply)
>   + ip_address_id = (known after apply)
>   + managed   = false
>   + parallelism   = 2
>
>   + rule {
>   + cidr_list = [
>   + "0.0.0.0/0",
> ]
>   + icmp_code = (known after apply)
>   + icmp_type = (known after apply)
>   + ports = [
>   + "22",
>   + "443",
>   + "80",
> ]
>   + protocol  = "tcp"
>   + uuids = (known after apply)
> }
> }
>
>   # cloudstack_instance.web will be created
>   + resource "cloudstack_instance" "web" {
>   + display_name = "VM1Test"
>   + expunge  = true
>   + group= (known after apply)
>   + id   = (known after apply)
>   + ip_address   = (known after apply)
>   + name = "VM1Test&

Re: [!!Mass Mail]Re: Dynamically scalable VM

[Harikrishna Patnala]

You can check the host-param-list details to get the CPU sockets information on 
the XCP host.

# xe host-param-list uuid= | grep -i cpu

As mentioned below, if host's CPU sockets value is less than xen.vm.vcpu.max 
value, then host's CPU socket value is used to set max vCPUs of VM.

Regards,
Harikrishna

From: Дикевич Евгений Александрович 
Sent: Friday, January 28, 2022 12:51 PM
To: users@cloudstack.apache.org 
Subject: RE: [!!Mass Mail]Re: Dynamically scalable VM

Hi.

In xen.vm.vcpu.max I paste 32 vCPU

XCP tools are installed

MB U know what I can check else?




 


-Original Message-----
From: Harikrishna Patnala [mailto:harikrishna.patn...@shapeblue.com]
Sent: Friday, January 28, 2022 9:43 AM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Dynamically scalable VM

Hi,

Regarding 4 vCPUs, it is not ACS limitation it is the maximum CPU sockets that 
your XCP host can support or the global/cluster setting "xen.vm.vcpu.max" 
whichever is lesser. This is because VMs cannot be created with more vCPUs than 
the CPU sockets available on the host.

As far as I know, to make any VM dynamically scalable it needs to have XS tools 
installed in it.

Hope this helps.

Regards,
Harikrishna

From: Дикевич Евгений Александрович 
Sent: Thursday, January 27, 2022 6:27 PM
To: users@cloudstack.apache.org 
Subject: Dynamically scalable VM

Hi all!

ACS 4.16 + XCP-NG 8.2

Have few questions about dynamically scalable VM.
First - why I can't create VM with more than 4 vCPU when Dinamically scaling is 
enabled in VM? This is ACS limitation or XCP-NG?
Second - How I can make dynamically scalable Ubuntu or Debian VM? How 
dynamically scaling works with CentOS 7.



Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

Attention!
This email and all attachments to it are confidential and are intended solely 
for use by the person (or persons) referred to (mentioned) as the intended 
recipient (recipients). If you are not the intended recipient of this email, do 
not copy or disclose its contents and delete the message and any attachments to 
it from your e-mail system. Any unauthorized use, dissemination, disclosure, 
printing or copying of this e-mail and files attached to it, except by the 
intended recipient, is illegal and is prohibited. Taking into account that data 
transmission via Internet is not secure, we assume no responsibility for any 
potential damage caused by data transmission errors or this message and the 
files attached to it.

Re: Dynamically scalable VM

[Harikrishna Patnala]

Hi,

Regarding 4 vCPUs, it is not ACS limitation it is the maximum CPU sockets that 
your XCP host can support or the global/cluster setting "xen.vm.vcpu.max" 
whichever is lesser. This is because VMs cannot be created with more vCPUs than 
the CPU sockets available on the host.

As far as I know, to make any VM dynamically scalable it needs to have XS tools 
installed in it.

Hope this helps.

Regards,
Harikrishna

From: Дикевич Евгений Александрович 
Sent: Thursday, January 27, 2022 6:27 PM
To: users@cloudstack.apache.org 
Subject: Dynamically scalable VM

Hi all!

ACS 4.16 + XCP-NG 8.2

Have few questions about dynamically scalable VM.
First - why I can't create VM with more than 4 vCPU when Dinamically scaling is 
enabled in VM? This is ACS limitation or XCP-NG?
Second - How I can make dynamically scalable Ubuntu or Debian VM? How 
dynamically scaling works with CentOS 7.



Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

Attention!
This email and all attachments to it are confidential and are intended solely 
for use by the person (or persons) referred to (mentioned) as the intended 
recipient (recipients). If you are not the intended recipient of this email, do 
not copy or disclose its contents and delete the message and any attachments to 
it from your e-mail system. Any unauthorized use, dissemination, disclosure, 
printing or copying of this e-mail and files attached to it, except by the 
intended recipient, is illegal and is prohibited. Taking into account that data 
transmission via Internet is not secure, we assume no responsibility for any 
potential damage caused by data transmission errors or this message and the 
files attached to it.

 

Re: Connect 2 VPC with private gateway

[Harikrishna Patnala]

Hi,

You can use the site to site VPN connection, in this case, please check this 
document 
http://docs.cloudstack.apache.org/projects/archived-cloudstack-administration/en/latest/networking/site_to_site_vpn.html

or https://www.shapeblue.com/vpc-to-vpc-vpn-configuration-in-cloudstack/


Regards,
Harikrishna

From: Ricardo Pertuz 
Sent: Sunday, January 23, 2022 9:55 PM
To: users@cloudstack.apache.org 
Subject: Connect 2 VPC with private gateway

Hi,

Is there a tutorial or doc with the steps to connect VPCs from different 
accounts using private gateways?

Regards

 

Re: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0

[Harikrishna Patnala]

Hi all,

I'm updating links of the git commit SHA and release tag to point to the Apache 
repository (https://github.com/apache/cloudstack-terraform-provider).

We had previously agreed to develop and publish releases on 
apache/cloudstack-terraform-provider repository and use 
cloudstack/terraform-provider-cloudstack repository for only pushing git 
tags/releases from which artefacts are pulled by the Terraform registry. This 
is because of the fact that Terraform registry requires repositories in a 
certain naming convention (terraform-provider-NAME). So we have forked and 
renamed the apache/cloudstack-terraform-provider repo under the "cloudstack" 
Github org which is also under the control of the ACS PMC.

Please find the new links here as below,

I've created a v0.4.0 release of CloudStack Terraform Provider, with the 
following artifacts up for a vote:


Link to the latest CloudStack Terraform Provider artefact with version 
"0.4.0-RC1": 
https://registry.terraform.io/providers/cloudstack/cloudstack/0.4.0-RC1


Git Branch and commit SHA:
https://github.com/apache/cloudstack-terraform-provider/commit/9496d6a0d029a808dd8876c9119703d6b3bf8c9c



Commit:
9496d6a0d029a808dd8876c9119703d6b3bf8c9c


GitHub pre-release (for RC1 testing, contains changelog,
artifacts/binaries to test, checksums/usage details):
https://github.com/apache/cloudstack-terraform-provider/releases/tag/v0.4.0-RC1


Source release (checksums and signatures are available at the same location):
https://dist.apache.org/repos/dist/dev/cloudstack/terraform-provider-0.4.0-RC1/


PGP release keys (signed using 1031D6946F8A7C4B0C3E9EEFAEA5313845ADC482)
https://dist.apache.org/repos/dist/release/cloudstack/KEYS




The vote will be open until January 31st, 2022.


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 the reason why)


Regards,
Harikrishna
________
From: Harikrishna Patnala 
Sent: Wednesday, January 19, 2022 4:09 PM
To: 'users@cloudstack.apache.org' ; 
d...@cloudstack.apache.org 
Subject: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0

Hi All,


I've created a v0.4.0 release of CloudStack Terraform Provider, with the 
following
artifacts up for a vote:


Link to the latest CloudStack Terraform Provider artifact with version 
"0.4.0-RC1": 
https://registry.terraform.io/providers/cloudstack/cloudstack/0.4.0-RC1


Git Branch and commit SHA:
https://github.com/cloudstack/terraform-provider-cloudstack/commit/9496d6a0d029a808dd8876c9119703d6b3bf8c9c


Commit:
9496d6a0d029a808dd8876c9119703d6b3bf8c9c


GitHub pre-release (for RC1 testing, contains changelog,
artifacts/binaries to test, checksums/usage details):
https://github.com/cloudstack/terraform-provider-cloudstack/releases/tag/v0.4.0-RC1


Source release (checksums and signatures are available at the same location):
https://dist.apache.org/repos/dist/dev/cloudstack/terraform-provider-0.4.0-RC1/


PGP release keys (signed using 1031D6946F8A7C4B0C3E9EEFAEA5313845ADC482)
https://dist.apache.org/repos/dist/release/cloudstack/KEYS



The vote will be open until January 31st, 2022.


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 the reason why)


Regards,
Harikrishna




 

[VOTE] Release Apache CloudStack Terraform Provider v0.4.0

[Harikrishna Patnala]

Hi All,


I've created a v0.4.0 release of CloudStack Terraform Provider, with the 
following
artifacts up for a vote:


Link to the latest CloudStack Terraform Provider artifact with version 
"0.4.0-RC1": 
https://registry.terraform.io/providers/cloudstack/cloudstack/0.4.0-RC1


Git Branch and commit SHA:
https://github.com/cloudstack/terraform-provider-cloudstack/commit/9496d6a0d029a808dd8876c9119703d6b3bf8c9c


Commit:
9496d6a0d029a808dd8876c9119703d6b3bf8c9c


GitHub pre-release (for RC1 testing, contains changelog,
artifacts/binaries to test, checksums/usage details):
https://github.com/cloudstack/terraform-provider-cloudstack/releases/tag/v0.4.0-RC1


Source release (checksums and signatures are available at the same location):
https://dist.apache.org/repos/dist/dev/cloudstack/terraform-provider-0.4.0-RC1/


PGP release keys (signed using 1031D6946F8A7C4B0C3E9EEFAEA5313845ADC482)
https://dist.apache.org/repos/dist/release/cloudstack/KEYS



The vote will be open until January 31st, 2022.


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 the reason why)


Regards,
Harikrishna

 

Re: Maximum size of ROOTDISK

[Harikrishna Patnala]

Hi,

I see there is a global setting "storage.max.volume.size" which controls the 
size of the volume in CloudStack. But I also observed this is not being 
honoured when root volume is first created. Later if you try to resize the root 
disk then this setting is considered. On the other hand, it works fine for data 
disks.

Note: we need to restart the management server after the setting 
"storage.max.volume.size" value has changed.

Regards,
Harikrishna

From: 小林 美佳子 
Sent: Thursday, January 6, 2022 1:26 PM
To: users@cloudstack.apache.org 
Subject: Re: Maximum size of ROOTDISK

Hi. Thanks everyone for your answers.

The hypervisor uses VMware.
I understand that there is a limit to the hypervisor; are you saying that 
CloudStack does not have an upper limit? (Is it possible to create a ROOT disk 
with the hypervisor's maximum size?)

Also, if you find any code to support this, please let me know.

On 2022/01/06 15:48, Vivek Kumar wrote:
> It depends on your hypvervisor limit, I.e XenServer supports 2TB Max, so it 
> won’t any sense if you create 3 TB disk offering. So check you backend 
> hypervisor limit and test.
>
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> IndiQus Technologies
> 24*7  O +91 11 4055 1411  |   M +91 7503460090
> www.indiqus.com
>
>
>
 

> On 06-Jan-2022, at 7:25 AM, 小林 美佳子  wrote:
>>
>>
>> Hi.
>>
>> I am currently using CloudStack 4.10, and I am trying to build a new 
>> CloudStack 4.14.
>>
>> The GrobalConfig "root.disk.size.max" that existed in CloudStack4.10 has 
>> been removed from CloudStack4.14.
>> In CloudStack 4.14, what determines the maximum size of the ROOTDISK? Is it 
>> built into the code? If so, what is the maximum size?
>
>

Re: Connecting to CSK nodes

[Harikrishna Patnala]

Hi Ricardo,

Please the user "core" to login to the nodes.
Like "ssh -i  -p  core@"

Regards,
Harikrishna

From: Ricardo Andres Pertuz de las Salas 
Sent: Sunday, January 2, 2022 9:55 AM
To: users@cloudstack.apache.org 
Subject: Connecting to CSK nodes

Hi team,

I’m trying to connect to my CSK cluster nodes but not so sure which ssh user to 
use.

ubuntu@mbx02:~$ ssh -p  -i privatekey root@172.20.1.65
Please login as the user "NONE" rather than the user "root".

Regards,

Ricardo

 

Re: [PROPOSE] RM for 4.16.1

[Harikrishna Patnala]

Thank you and good luck Suresh, Nicolas.

Regards,
Harikrishna

From: Suresh Anaparti 
Sent: Monday, December 13, 2021 6:39 PM
To: d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: [PROPOSE] RM for 4.16.1

Hi All,

I'd like to put myself forward as the release manager for 4.16.1.0. My 
colleague Nicolas Vazquez will support me as the co-RM for the PR 
reviews/tests/merges, and others are welcome to support as well.

I propose, we've a window of at least 8 weeks (2 months) to allow the community 
/ users to test 4.16.0.0 and report issues, and aim to cut RC1 in Q1 2022 (may 
be, in late Feb-2022, or early Mar-2022 onwards). I'll propose the timeline 
details by end of this week. I hope to have your support.

Please let me know if you have any thoughts / comments.


Regards,
Suresh




 

Re: Adding local datastore Vmware.

[Harikrishna Patnala]

Hi Abhishek,

The bug that you are referring to is related to resource tags (not host tags or 
storage tags).

We have to use host tags and storage tags in your case. Can you please try 
clicking the "Edit" action button on the UI and add host tags for the hosts and 
storage tags for the primary storage.

Thanks,
Harikrishna

From: Abishek 
Sent: Monday, December 13, 2021 7:51 PM
To: users@cloudstack.apache.org 
Subject: Re: Adding local datastore Vmware.

Hi HariKrishna,

Thanks for the reply. I did manage to add the local storage to the
> Cloudstack via Presetup storage under Primary Storage. That did the thing
> for me. I then created a tag for the Host and that particular storage so
> that the VM starts on the same host and local storage. Then I created a
> service offering with those particular host and storage tags. But I failed
> to start the VM. Tried multiple times but I get error of *insufficient
> capacity*. I think the issue is with the tags(from my understanding).  On
> looking for the tags for the stoarge I only saw  X= same as
> https://github.com/apache/cloudstack/issues/5727 But the issue mentioned
> in github only seems to be UI bug.


Thank You.

>


On Mon, 13 Dec 2021 at 17:26, Harikrishna Patnala <
harikrishna.patn...@shapeblue.com> wrote:

> Hi Abhishek,
>
> I get that you have already one local storage available in CS, so I assume
> the related zone setting for local storage is already enabled. I'm not sure
> if multiple local storages for a single host works or not but you can try
> restarting the management server so that host will try to reconnect and
> detect for any local storages available.
>
> Regards,
> Harikrishna
> 
> From: Abishek 
> Sent: Monday, December 6, 2021 7:47 PM
> To: users@cloudstack.apache.org 
> Subject: Adding local datastore Vmware.
>
> Hello All,
>
> I am currently testing cloudstack 4.16 with vmware vsphere7.0.
> Installation has succeeded and everything is working fine. In my setup I
> have used Raid 1 setup to install ESXI and I have also setup another local
> datastore with RAID 5 setup i.e I have 2 local storage (datastore1 contains
> ESXI and datastore2 i.e. with Raid 5 setup). How can I make
> cloudstack aware of both local storage. How can I run  a Vm in my second
> datastore i.e. datastore2. All my host have same configuration.
>
> Thank You.
>
>
>
>

 

Re: Adding local datastore Vmware.

[Harikrishna Patnala]

Hi Abhishek,

I get that you have already one local storage available in CS, so I assume the 
related zone setting for local storage is already enabled. I'm not sure if 
multiple local storages for a single host works or not but you can try 
restarting the management server so that host will try to reconnect and detect 
for any local storages available.

Regards,
Harikrishna

From: Abishek 
Sent: Monday, December 6, 2021 7:47 PM
To: users@cloudstack.apache.org 
Subject: Adding local datastore Vmware.

Hello All,

I am currently testing cloudstack 4.16 with vmware vsphere7.0.
Installation has succeeded and everything is working fine. In my setup I
have used Raid 1 setup to install ESXI and I have also setup another local
datastore with RAID 5 setup i.e I have 2 local storage (datastore1 contains
ESXI and datastore2 i.e. with Raid 5 setup). How can I make
cloudstack aware of both local storage. How can I run  a Vm in my second
datastore i.e. datastore2. All my host have same configuration.

Thank You.

 

Re: Dynamic VM Scaling KVM

[Harikrishna Patnala]

Hi Abhishek,

I see that this feature is not added in UI, may be in the view of its compute 
offering constraints. I've created a small PR to add that 
https://github.com/apache/cloudstack/pull/5703, if it passes we can have it in 
the next release.

Thanks,
Harikrishna

From: Abishek 
Sent: Sunday, November 21, 2021 12:19 PM
To: users@cloudstack.apache.org 
Subject: Re: Dynamic VM Scaling KVM

Hello All,

I have successfully upgraded qemu-kvm to qemu-kvm-ev and now I can start the VM 
with dynamic-scaling template and service-offering(custom) unlike before. But 
after successfully starting the VM I did not find any scaleVM option in the Web 
UI while the VM is running. Is the feature only supported via CLI only or do I 
have to enable some other options (enable dynamic scale vm is already set to 
true).
 Mgmt : Cloudstack 4.16 (upgraded from 4.15.2)
HV: Centos 7.9 with KVM

Thank You
[image.png]


 

On Fri, 19 Nov 2021 at 19:18, Abishek 
mailto:abckd...@gmail.com>> wrote:
Hi Slavka,

I am very grateful for the response. Can i directly proceed to replace qemu-kvm 
with qemu-kvm-ev package. What effect will it have on my current environment? 
If you could point me to any documentation regarding it I would be extremely 
grateful.
Environment:
Hypervisor: Centos 7.9 KVM

Thank You.

On Fri, 19 Nov 2021 at 16:27, Slavka Peleva  
wrote:
Hi all,

I've tested the dynamic scaling with qemu-kvm and qemu-kvm-ev. Here are the
results for both with "Custom constrained" compute offering:

qemu-kvm-ev
deploy VM - passed
scale VM - passed

qemu-kvm
deploy VM - failed with the same error (org.libvirt.LibvirtException:
internal error: process exited while connecting to monitor: qemu: invalid
ram size: size=524288k,slots=16,maxmem=4194304k)
scale VM on existing VM - passed

Best regards,
Slavka

On Fri, Nov 19, 2021 at 6:12 AM Abishek 
mailto:abckd...@gmail.com>> wrote:

> Thanks a lot Wei for helping out. I will first try it in the Ubuntu
> environment.
>
> On Fri, 19 Nov 2021 at 00:09, Wei ZHOU 
> mailto:ustcweiz...@gmail.com>> wrote:
>
> > Great, thanks Daniel.
> >
> > Abishek, now it seems you need to install qemu-kvm-ev for testing the
> > feature.
> >
> > -Wei
> >
> > On Thursday, 18 November 2021, Daniel Augusto Veronezi Salvador <
> > dvsalvador...@gmail.com> wrote:
> >
> > > Hi Abishek, Wei, I tested this feature with Ubuntu 20.04 + KVM. Some
> > > community members tested with CentOS7 and qemu-kvm-ev and it worked.
> > Also,
> > > as live snapshots and live migrations, hotplug memory is a known
> > limitation
> > > of qemu-kvm. I cannot give you advice regarding this replacement too,
> as
> > I
> > > do not use CentOS. Best regards, Daniel Salvador
> > >
> > > On 17/11/2021 09:07, Wei ZHOU wrote:
> > >
> > >> Hi Abishek,
> > >>
> > >> I cannot give your advice on it as I did not install qemu-kvm-ev to
> > >> replace
> > >> qemu-kvm before.
> > >>
> > >> I suspect that the issue you faced is caused by qemu-kvm. qemu-kvm-ev
> > >> supports more advanced features than qemu-kvm.
> > >>
> > >> cc @Daniel, what hypervisor did you use to test the dynamic scaling ?
> > >>
> > >> -Wei
> > >>
> > >> On Wed, 17 Nov 2021 at 11:42, 
> > >> Abishekmailto:abckd...@gmail.com>>  wrote:
> > >>
> > >> HI Wei,
> > >>>
> > >>> I have not tested with qemu-kvm-ev. I am willing to try but what
> > >>> effect will it have on my existing setup when I install qemu-kvm-ev
> in
> > my
> > >>> existing qemu-kvm. Should I have to remove qemu-kvm and install
> > >>> qemu-kvm-ev? In the previous test I was able to start the machine
> with
> > >>> Fixed Offering but the option for Scaling the VM in UI was not
> present
> > >>> while the VM was in running state but was available when the VM was
> in
> > >>> shutdown state only.
> > >>>
> > >>> Thank You.
> > >>>
> > >>> On Wed, 17 Nov 2021 at 15:23, Wei 
> > >>> ZHOUmailto:ustcweiz...@gmail.com>>
> wrote:
> > >>>
> > >>> Hi Abishek,
> > 
> >  Have you tested with qemu-kvm-ev instead of qemu-kvm ?
> > 
> >  -Wei
> > 
> >  On Wed, 17 Nov 2021 at 10:00, 
> >  Abishekmailto:abckd...@gmail.com>>  wrote:
> > 
> >  Hello Wei,
> > >
> > > I am very grateful for your response. In my test environment I
> first
> > > created a service offering of Custom Constrained (minCore=1,
> > >
> >  maxCore=10,
> > >>>
> >  minRam=1GB, maxRam=12GB, CPUSpeed=2000) with dynamic scaling
> enabled.
> > >
> >  But
> > >>>
> >  every time I tried to start the VM under this ServiceOffering I got
> > the
> > > above mentioned error. Please find the following agent log for that
> > > particular VM:
> > >
> > > https://controlc.com/4618c4d8
> > >
> > > HOST OS : Centos 7.9
> > > QEMU:   QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-175.el7_9.4),
> > >
> >  Copyright
> > 
> > > (c) 2003-2008 Fabrice Bellard
> > >
> > > And I think the error seems t

Re: adding cloudstack to our internal cloud

[Harikrishna Patnala]

Hi Mohamad,

Firstly, welcome to the CloudStack community.

The short answer I can say we have a feature called "VM ingestion" using which 
we can import existing VMs from vCenter into CloudStack. You can have a quick 
look at this blog 
https://www.shapeblue.com/new-feature-first-look-vm-ingestion/ and video 
https://www.youtube.com/watch?v=n8ef1imnWiI. It is also supported from 
CloudStack UI too.

To my knowledge, it can be completely disruptive, once CloudStack setup is 
ready and you need to import VMs into CloudStack.

To start with you may please go through the blog and also try out CloudStack.

Thanks,
Harikrishna



From: Mohamad Bannout 
Sent: Tuesday, November 16, 2021 12:49 AM
To: users@cloudstack.apache.org 
Subject: adding cloudstack to our internal cloud

Hello,



First time user here,



We have private cloud setup in our company using vmware with only vcenter
for management, I'm considering adding cloudstack to the mix.



The question is how disruptive would this be to the environment ? do we have
to build it from scratch or is it possible to just 'plug n play' ?



Thanks in advance for any help I get.




 

Re: Failed to find datastore for pool UUID 4.15.2 VMware migration

[Harikrishna Patnala]

Hi Cristian,

Based on the error that you have shared, looks like this won't be an issue in 
4.16, I did some quick check in code base. You can test with the latest 4.16 
RC3 artifacts. May I know what is the exact operation that you are trying to do 
here? is it migrating a stopped or running VM to a different pool in the same 
cluster or across cluster?

Thanks,
Harikrishna


From: cristian.c@istream.today 
Sent: Sunday, November 7, 2021 3:15 PM
To: users@cloudstack.apache.org 
Subject: RE: Failed to find datastore for pool UUID 4.15.2 VMware migration

Update:



   Correction " Not able to find the destination:



Regards,

Cristian



From: cristian.c@istream.today 
Sent: Sunday, November 7, 2021 11:41 AM
To: users@cloudstack.apache.org
Subject: Failed to find datastore for pool UUID 4.15.2 VMware migration



Hello,





 I just tested the migration in 4.15.2 and I get the following error
"Failed to find datastore for pool UUID" Looks like is not able to find the
source, which does not make sense, if I migrate from VMware between host
works perfectly, also the deploy VM deploy in acs works fine on any host, is
this a bug?





2021-11-07 09:29:10,837 ERROR [c.c.h.v.r.VmwareResource]
(DirectAgent-396:ctx-0333aa69 ldn-uk-002.shape.host, job-2412/job-2413, cmd:
MigrateVmToPoolCommand) (logid:72a9c33a) Failed to find datastore for pool
UUID: ce27d8fc-27cf-4754-8a82-e27497c390a7

2021-11-07 09:29:10,839 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-396:ctx-0333aa69) (logid:72a9c33a) Seq 15-6715711469339541698:
Response Received:

2021-11-07 09:29:10,840 DEBUG [c.c.a.t.Request]
(DirectAgent-396:ctx-0333aa69) (logid:72a9c33a) Seq 15-6715711469339541698:
Processing:  { Ans: , MgmtId: 39908814623087, via:
15(ldn-uk-002.shape.host), Ver: v1, Flags: 110,
[{"com.cloud.agent.api.Answer":{"result":"false","details":"Exception:
com.cloud.utils.exception.CloudRuntimeException

Message: Failed to find datastore for pool UUID:
ce27d8fc-27cf-4754-8a82-e27497c390a7

Stack: com.cloud.utils.exception.CloudRuntimeException: Failed to find
datastore for pool UUID: ce27d8fc-27cf-4754-8a82-e27497c390a7

at
com.cloud.hypervisor.vmware.resource.VmwareResource.getTargetDatastoreMORefe
rence(VmwareResource.java:4522)

at
com.cloud.hypervisor.vmware.resource.VmwareResource.migrateAndAnswer(VmwareR
esource.java:4416)

at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.j
ava:4401)

at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareRes
ource.java:494)

at
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAtta
che.java:315)

at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedCo
ntextRunnable.java:48)

at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(Defa
ultManagedContext.java:55)

at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithCon
text(DefaultManagedContext.java:102)

at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithCont
ext(DefaultManagedContext.java:52)

at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedCont
extRunnable.java:45)

at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java
:515)

at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTa
sk.run(ScheduledThreadPoolExecutor.java:304)

at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecut
or.java:1128)

at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecu
tor.java:628)

at java.base/java.lang.Thread.run(Thread.java:829)

","wait":"0","bypassHostMaintenance":"false"}}] }

2021-11-07 09:29:10,840 DEBUG [c.c.a.m.AgentAttache]
(DirectAgent-396:ctx-0333aa69) (logid:72a9c33a) Seq 15-6715711469339541698:
No more commands found

2021-11-07 09:29:10,840 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-6:ctx-2cfa416a job-2412/job-2413 ctx-d6941fcf)
(logid:72a9c33a) Seq 15-6715711469339541698: Received:  { Ans: , MgmtId:
39908814623087, via: 15(ldn-uk-002.shape.host), Ver: v1, Flags: 110, {
Answer } }





Regards,

Cristian


 

Re: New Terraform artifacts published for testing

[Harikrishna Patnala]

Hi Piotr,

Thank you for your efforts in testing this.

Support for CloudStack's K8s service through terraform is currently not there 
but it is a good value addition. Currently, there are no immediate plans for 
this in the roadmap. I've created an enhancement ticket here 
https://github.com/apache/cloudstack-terraform-provider/issues/13, if we can 
find any volunteers for future releases that will be great.

Regards,
Harikrishna

From: Piotr Pisz 
Sent: Thursday, October 21, 2021 1:00 PM
To: users@cloudstack.apache.org 
Cc: d...@cloudstack.apache.org 
Subject: RE: New Terraform artifacts published for testing

Hi Harikrishna!

I test this provider strongly and so far I have not found any errors (eg
work as expected).
But I have a question, do you plan to adapt this provider's capabilities to
the new CS 4.16 and kubernetes plugin?
I am very interested in setting up a K8S cluster using CS (preferably with
kubernetes plugin) with terraform (or CS + kubespray + terraform without
plugin).
Will this privider be published (along with the documentation) in
registry.terraform.io?
Any roadmap? :-)

Regards,
Piotr


 


-Original Message-
From: Harikrishna Patnala 
Sent: Wednesday, October 20, 2021 4:12 PM
To: 'users@cloudstack.apache.org' 
Cc: d...@cloudstack.apache.org
Subject: New Terraform artifacts published for testing

Hi All,

We have published the new artifacts to the Terraform registry
https://registry.terraform.io/providers/cloudstack/cloudstack/latest. These
are created only for testing purposes with tag v0.4.0-pre.

May I ask the terraform users to help in testing it and report if you find
any issues here at on
https://github.com/apache/cloudstack-terraform-provider/issues? We have
already fixed some issues and done some testing. If everything goes well we
can create RC1 in the next week or so.

Regards,
Harikrishna

New Terraform artifacts published for testing

[Harikrishna Patnala]

Hi All,

We have published the new artifacts to the Terraform registry 
https://registry.terraform.io/providers/cloudstack/cloudstack/latest. These are 
created only for testing purposes with tag v0.4.0-pre.

May I ask the terraform users to help in testing it and report if you find any 
issues here at on 
https://github.com/apache/cloudstack-terraform-provider/issues? We have already 
fixed some issues and done some testing. If everything goes well we can create 
RC1 in the next week or so.

Regards,
Harikrishna


 

Re: Multiple console proxy

[Harikrishna Patnala]

Hi Abhishek,

Both parameters having the same value will lead to multiple CPVMs. Please keep 
the "consoleproxy.capacity.standby" value less than "consoleproxy.session.max". 
In my (fresh) environment I see the values 10 and 50 respectively. The 
calculation is like, if console proxy session capacity is less than the standby 
value then the management server will spawn a new CPVM to handle the capacity. 
So please change the value as suggested, restart the management server and then 
destroy one CPVM.

Regards,
Harikrishna

From: Abishek 
Sent: Monday, October 11, 2021 9:44 AM
To: users@cloudstack.apache.org 
Subject: Re: Multiple console proxy

Hi HariKrishna,

Thanks for the reply. Both the above mentioned parameters are set to 50. I 
suppose then we can set those limits higher as we have changed the service 
offering of console proxy VM to 4 core CPU, 8GB RAM. We are at a pre-production 
stage and it's impossible to reach that limit(50) as no other users have access 
to the our CloudStack. But I will look further to investigate.
I will be very grateful if you can pin point me to the documentation of 
deleting the newly created system VM. Also, if the limit of Console proxy is 
reached then it will spawn a new Console proxy to serve the new users(users 
above the limit). If so how will the newly created Console proxy server the new 
users as I have pinpointed my DNS to the old console proxy. If there is any 
documentation regarding it can you please provide me the link I will very 
grateful

Thank You.


 

On 2021/10/11 02:56:02, Harikrishna Patnala  
wrote:
> Hi Abhishek,
>
> Please check these two global settings "consoleproxy.capacity.standby" and 
> "consoleproxy.session.max" which are used to configure the number of viewer 
> sessions and accordingly new CPVM VM will be spawned. In your case, it might 
> have hit the maximum sessions and spawned a new CPVM.
>
> Regards,
> Harikrishna
> 
> From: Abishek 
> Sent: Sunday, October 10, 2021 9:51 AM
> To: users@cloudstack.apache.org 
> Subject: Multiple console proxy
>
> Hello All,
>
> I am using cloudstack 4.15.2 with KVM hosts. Everything is working fine but I 
> noticed that suddenly the a new console proxy was spawned. Now there are 
> multiple console proxy. The old console proxy was working and is current is 
> working fine. All the request are still being served from the old console 
> proxy. Please find the logs below:
>
> 2021-10-08 14:47:50,802 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
> (consoleproxy-1:ctx-7620deae) (logid:4159ef33) Zone 1 is ready to launch 
> console proxy
> 2021-10-08 14:47:50,802 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
> (consoleproxy-1:ctx-7620deae) (logid:4159ef33) Expand console proxy standby 
> capacity for zone ABC
> 2021-10-08 14:47:50,804 INFO  [c.c.c.ConsoleProxyManagerImpl] 
> (consoleproxy-1:ctx-7620deae) (logid:4159ef33) No stopped console proxy is 
> available, need to allocate a new console proxy
> 2021-10-08 14:47:50,805 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
> (consoleproxy-1:ctx-7620deae) (logid:4159ef33) Assign console proxy from a 
> newly started instance for request from data center : 1
> 2021-10-08 14:47:50,908 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (consoleproxy-1:ctx-7620deae) (logid:4159ef33) Found existing network 
> configuration for offering [Network Offering 
> [1-Public-System-Public-Network]: Ntwk[200|Public|1]
> 2021-10-08 14:47:50,909 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (consoleproxy-1:ctx-7620deae) (logid:4159ef33) Releasing lock for 
> Acct[4422bff8-0c6f-11ec-90a1-b499baba5514-system]
> 2021-10-08 14:47:51,004 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (consoleproxy-1:ctx-7620deae) (logid:4159ef33) Found existing network 
> configuration for offering [Network Offering 
> [3-Control-System-Control-Network]: Ntwk[202|Control|3]
> 2021-10-08 14:47:51,004 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (consoleproxy-1:ctx-7620deae) (logid:4159ef33) Releasing lock for 
> Acct[4422bff8-0c6f-11ec-90a1-b499baba5514-system]
> 2021-10-08 14:47:51,008 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
> (secstorage-1:ctx-e6a2d6db) (logid:358113cc) Zone 1 is ready to launch 
> secondary storage VM
> 2021-10-08 14:47:51,095 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (consoleproxy-1:ctx-7620deae) (logid:4159ef33) Found existing network 
> configuration for offering [Network Offering 
> [2-Management-System-Management-Network]: Ntwk[201|Management|2]
> 2021-10-08 14:47:51,095 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (consoleproxy-1:ctx-7620deae) (logid:4159ef33) Releasing lock for 
> Acct[4422bff8-0c6f-11ec-90a1-b499baba5514-system]
> 2021-10-08 14:47:51,188 INFO  [c.c.v.VirtualMachineManagerImpl] 
> (consoleproxy-1:ctx-7620deae)

Re: Multiple console proxy

[Harikrishna Patnala]

Hi Abhishek,

Please check these two global settings "consoleproxy.capacity.standby" and 
"consoleproxy.session.max" which are used to configure the number of viewer 
sessions and accordingly new CPVM VM will be spawned. In your case, it might 
have hit the maximum sessions and spawned a new CPVM.

Regards,
Harikrishna

From: Abishek 
Sent: Sunday, October 10, 2021 9:51 AM
To: users@cloudstack.apache.org 
Subject: Multiple console proxy

Hello All,

I am using cloudstack 4.15.2 with KVM hosts. Everything is working fine but I 
noticed that suddenly the a new console proxy was spawned. Now there are 
multiple console proxy. The old console proxy was working and is current is 
working fine. All the request are still being served from the old console 
proxy. Please find the logs below:

2021-10-08 14:47:50,802 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Zone 1 is ready to launch 
console proxy
2021-10-08 14:47:50,802 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Expand console proxy standby 
capacity for zone ABC
2021-10-08 14:47:50,804 INFO  [c.c.c.ConsoleProxyManagerImpl] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) No stopped console proxy is 
available, need to allocate a new console proxy
2021-10-08 14:47:50,805 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Assign console proxy from a 
newly started instance for request from data center : 1
2021-10-08 14:47:50,908 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Found existing network 
configuration for offering [Network Offering [1-Public-System-Public-Network]: 
Ntwk[200|Public|1]
2021-10-08 14:47:50,909 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Releasing lock for 
Acct[4422bff8-0c6f-11ec-90a1-b499baba5514-system]
2021-10-08 14:47:51,004 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Found existing network 
configuration for offering [Network Offering 
[3-Control-System-Control-Network]: Ntwk[202|Control|3]
2021-10-08 14:47:51,004 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Releasing lock for 
Acct[4422bff8-0c6f-11ec-90a1-b499baba5514-system]
2021-10-08 14:47:51,008 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-e6a2d6db) (logid:358113cc) Zone 1 is ready to launch 
secondary storage VM
2021-10-08 14:47:51,095 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Found existing network 
configuration for offering [Network Offering 
[2-Management-System-Management-Network]: Ntwk[201|Management|2]
2021-10-08 14:47:51,095 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Releasing lock for 
Acct[4422bff8-0c6f-11ec-90a1-b499baba5514-system]
2021-10-08 14:47:51,188 INFO  [c.c.v.VirtualMachineManagerImpl] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) allocating virtual machine from 
template:a7277096-e764-41e2-b890-405e88b85466 with hostname:v-100-VM and 3 
networks
2021-10-08 14:47:51,192 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Allocating entries for VM: 
VM[ConsoleProxy|v-100-VM]
2021-10-08 14:47:51,197 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Allocating nics for 
VM[ConsoleProxy|v-100-VM]
2021-10-08 14:47:51,203 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Allocating nic for vm 
VM[ConsoleProxy|v-100-VM] in network Ntwk[200|Public|1] with requested profile 
NicProfile[0-0-null-null-null]
2021-10-08 14:47:51,251 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Allocating nic for vm 
VM[ConsoleProxy|v-100-VM] in network Ntwk[202|Control|3] with requested profile 
null
2021-10-08 14:47:51,260 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Allocating nic for vm 
VM[ConsoleProxy|v-100-VM] in network Ntwk[201|Management|2] with requested 
profile null
2021-10-08 14:47:51,271 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(consoleproxy-1:ctx-7620deae)
2021-10-08 14:47:51,271 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Allocating disks for VM[Co
nsoleProxy|v-100-VM]
2021-10-08 14:47:51,272 INFO  [o.a.c.e.o.VolumeOrchestrator] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) adding disk object ROOT-100 t
o v-100-VM
2021-10-08 14:47:51,311 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) Allocation completed for VM: 
VM[ConsoleProxy|v-100-VM]
2021-10-08 14:47:51,315 DEBUG [c.c.a.ConsoleProxyAlertAdapter] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef33) received console proxy alert
2021-10-08 14:47:51,316 DEBUG [c.c.a.ConsoleProxyAlertAdapter] 
(consoleproxy-1:ctx-7620deae) (logid:4159ef3

Re: Failed to authentication SSH user root on host - repetitive error

[Harikrishna Patnala]

Hi Crisitian,

To my understanding, you are trying to add a new zone and getting issues with 
the system VM having some SSH failures.

May I ask you to start everything fresh?

I mean to prepare new secondary storage, seed the system VM template into new 
secondary storage and then deploy the zone from the beginning of the zone 
creation wizard. Make sure your management server has the latest packages and 
systemvm.iso is also as expected to the CloudStack version you are trying.

Thanks,
Harikrishna




From: Cristian Ciobanu 
Sent: Friday, September 24, 2021 5:19 PM
To: users@cloudstack.apache.org 
Subject: Re: Failed to authentication SSH user root on host - repetitive error

Hi Pearl,


   I did upgrades multiple times, I always add the template before
upgrade.  If was something related to this, i was expecting not to work for
all zones, but right now is working for 2 zones from the same setup,
environment.

Regards,
Cristian

On Fri, Sep 24, 2021, 14:40 Pearl d'Silva 
wrote:

> Hi Cristian,
>
> After going through your earlier mails again, and correct me if I am
> wrong, but I noticed in one of your mails you mentioned that the env that's
> causing issues was upgraded from a lower version, right? So, ideally when
> doing upgrades, prior to initiating the upgrade we first take a backup of
> the DB,  register the template (new systemVM template) following this
> https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.15.html#update-system-vm-templates
> and then upgrade the environment. However, you mentioned that you used the
> cloud-install-sys-tmplt script to seed and register the template. I am not
> familiar if using that script during upgrades works (it may, but I haven't
> ever used that approach).
> If it is possible, it would be advisable to rollback your env to the
> earlier version (disable your zone, destroy the systemVMs before that) and
> then follow the upgrade steps as mentioned in the documentation:
> https://docs.cloudstack.apache.org/en/latest/upgrading/index.html
>
> Thanks,
> Pearl
>
>
> 
> From: cristian.c@istream.today 
> Sent: Friday, September 24, 2021 3:08 PM
> To: users@cloudstack.apache.org 
> Subject: RE: Failed to authentication SSH user root on host - repetitive
> error
>
> Hi Pearl,
>
> I just did a SSVM redeploy in the same environment, but different zone and
> and I see the following differences :
>
> "isManaged":"false"}},"name":"ROOT-2055","size":"(2.44 GB)"
>
>
> Working zone - https://pastebin.com/raw/88N6Fg6z
>
> "isManaged":"false"}},"name":"ROOT-2055","size":"(2.44 GB)
>
>  datastore-6588","managed":"false","storagePort":"0","volumeSize":"(2.44
> GB)
>
> 021-09-24 05:22:23,959 INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-437:ctx-2f1519ba fra-de-001.test.host, job-25099/job-35371,
> cmd: StartCommand) (logid:d442432d) Mapped disk datastore UUID is not the
> same as the cloned VM datastore UUID: fra-de-001 -
> 9d679070c7a6441592646bfbb82ef1b3
>
>
>
> Not working zone - https://pastebin.com/raw/Um2uHgWM
>
> "isManaged":"false"}},"name":"ROOT-2056","size":"(0 bytes)"here is 0
> bytes...
>
>  datastore-6694","managed":"false","storagePort":"0","volumeSize":"(0
> bytes)
> here is 0 bytes...
>
> 2021-09-24 05:00:55,594 INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-30:ctx-5e49d288 lnd-uk-002.test.host, job-25099/job-35365,
> cmd:
> StartCommand) (logid:d442432d) Mapped disk size is not the same as the
> cloned VM disk size: 0 - 262144( here I see this line, with disk
> size 0 )
>
> 2021-09-24 05:00:55,594 INFO  [c.c.h.v.r.VmwareResource]
> (DirectAgent-30:ctx-5e49d288 lnd-uk-002.test.host, job-25099/job-35365,
> cmd:
> StartCommand) (logid:d442432d) Mapped disk datastore UUID is not the same
> as
> the cloned VM datastore UUID: lnd-uk-002 - fb7b551a584e4b5192b8f371af56b303
>
>
>
> I do not understand why I have here the size "0"
>
>
> Regards,
> Cristian
>
>
>
>
> -Original Message-
> From: Pearl d'Silva 
> Sent: Friday, September 24, 2021 9:44 AM
> To: users@cloudstack.apache.org
> Subject: Re: Failed to authentication SSH user root on host - repetitive
> error
>
> By any chance, are there any old systemvm.isos in the secondary store, if
> yes, can you please delete them. Based on the information you've provided,
> it seems like, the key has been injected into systemvm.iso, but during boot
> up, a script (cloud-early-config) that sets up the VM before bootstrapping
> /
> patching isn't copying the auth key.
> Can you try the steps mentioned under the VMWare section of the doc:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/SystemVm.iso
> and see if it helps.
> SystemVm.iso - Apache Cloudstack - Apache Software
> Foundation<
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/SystemVm.i
> so>
> Mechanism of propagating systemvm.iso. Systemvm.iso gets propagated
> differently for different hypervisors. It comes packaged as part of the
> Cloudstack rpm o

Re: Problem with Templates/ISO

[Harikrishna Patnala]

Sorry, logs at /var/log/cloudstack/management/management-server.log

From: Harikrishna Patnala 
Sent: Monday, September 20, 2021 10:04 AM
To: users@cloudstack.apache.org 
Subject: Re: Problem with Templates/ISO


Hi Douglas,

Firstly, welcome to CloudStack.

This looks to me like DB changes did not apply properly during installation. 
Did you observe any issues in the logs during the management server 
installation or start.

You can check the logs at 
/usr/share/cloudstack/management/management-server.log and see the exact reason 
for DB sql exception when you perform the list templates operation.

As mentioned already there is no change in the system VM template from 4.15.1 
to 4.15.2

Regards,
Harikrishna

From: DL 
Sent: Monday, September 20, 2021 9:38 AM
To: users@cloudstack.apache.org 
Subject: Problem with Templates/ISO

Hello there,

I am a new CloutStack user and a new user on this mailing list. After
following the Quick Installation Guide, I ended up with empty Template/ISOs
when I attempted to create a VM instance.

If I go to Images/Templates, I got 500 Internal Server Error:

Request Failed (530)
DB Exception on: com.mysql.cj.jdbc.ClientPreparedStatement: SELECT
template_store_ref.id, template_store_ref.store_id,
template_store_ref.template_id, template_store_ref.store_role,
template_store_ref.created, template_store_ref.last_updated,
template_store_ref.download_pct, template_store_ref.size,
template_store_ref.physical_size, template_store_ref.download_state,
template_store_ref.local_path, template_store_ref.error_str,
template_store_ref.job_id, template_store_ref.install_path,
template_store_ref.url, template_store_ref.download_url,
template_store_ref.download_url_created, template_store_ref.is_copy,
template_store_ref.destroyed, template_store_ref.update_count,
template_store_ref.updated, template_store_ref.state,
template_store_ref.ref_cnt FROM template_store_ref WHERE
template_store_ref.template_id = 3 AND template_store_ref.download_state !=
'BYPASSED' AND template_store_ref.destroyed = 0 AND
template_store_ref.store_id IN )

Could someone help me fix this issue?

The quick installation guide I followed says it is for 4.15.2.0
installation. However, in the System Template Setup section, this command:
"""
/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
-m /export/secondary -u
https://download.cloudstack.org/systemvm/4.15/systemvmtemplate-4.15.1-kvm.qcow2.bz2
-h kvm -F
"""
seems to suggest that the process will download template vms for the
4.15.1.0 version?

Could this be the reason? Does anyone have an idea about when the Template
for the 4.15.2.0 version will be available?

Best regards,
Douglas




 

Re: Problem with Templates/ISO

[Harikrishna Patnala]

Hi Douglas,

Firstly, welcome to CloudStack.

This looks to me like DB changes did not apply properly during installation. 
Did you observe any issues in the logs during the management server 
installation or start.

You can check the logs at 
/usr/share/cloudstack/management/management-server.log and see the exact reason 
for DB sql exception when you perform the list templates operation.

As mentioned already there is no change in the system VM template from 4.15.1 
to 4.15.2

Regards,
Harikrishna

From: DL 
Sent: Monday, September 20, 2021 9:38 AM
To: users@cloudstack.apache.org 
Subject: Problem with Templates/ISO

Hello there,

I am a new CloutStack user and a new user on this mailing list. After
following the Quick Installation Guide, I ended up with empty Template/ISOs
when I attempted to create a VM instance.

If I go to Images/Templates, I got 500 Internal Server Error:

Request Failed (530)
DB Exception on: com.mysql.cj.jdbc.ClientPreparedStatement: SELECT
template_store_ref.id, template_store_ref.store_id,
template_store_ref.template_id, template_store_ref.store_role,
template_store_ref.created, template_store_ref.last_updated,
template_store_ref.download_pct, template_store_ref.size,
template_store_ref.physical_size, template_store_ref.download_state,
template_store_ref.local_path, template_store_ref.error_str,
template_store_ref.job_id, template_store_ref.install_path,
template_store_ref.url, template_store_ref.download_url,
template_store_ref.download_url_created, template_store_ref.is_copy,
template_store_ref.destroyed, template_store_ref.update_count,
template_store_ref.updated, template_store_ref.state,
template_store_ref.ref_cnt FROM template_store_ref WHERE
template_store_ref.template_id = 3 AND template_store_ref.download_state !=
'BYPASSED' AND template_store_ref.destroyed = 0 AND
template_store_ref.store_id IN )

Could someone help me fix this issue?

The quick installation guide I followed says it is for 4.15.2.0
installation. However, in the System Template Setup section, this command:
"""
/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
-m /export/secondary -u
https://download.cloudstack.org/systemvm/4.15/systemvmtemplate-4.15.1-kvm.qcow2.bz2
-h kvm -F
"""
seems to suggest that the process will download template vms for the
4.15.1.0 version?

Could this be the reason? Does anyone have an idea about when the Template
for the 4.15.2.0 version will be available?

Best regards,
Douglas

 

Re: vSAN vsphere 7.0 with Cloudstack.

[Harikrishna Patnala]

Hello,

Yes, vSAN and other storage types as primary storage support is added in 4.15 
release itself. You can set up a vSAN storage in vCenter and add it as primary 
storage under "presetup" storage protocol type. "presetup" is the generic 
storage protocol type for primary storage using which we can add any type of 
storage VMFS5, VMFS6, vSAN and vVols.

For more details you may please go through this 
https://www.shapeblue.com/cloudstack-feature-deep-dive-vsphere-advanced-capabilities-in-cloudstack/
[https://www.shapeblue.com/wp-content/uploads/2020/11/0901.sdt-vmware.png]
vSphere Advanced Capabilities in CloudStack | CloudStack Feature Deep Dive - 
The CloudStack 
Company
Introduction. CloudStack vSphere integration has not kept up with the evolution 
of vSphere itself, and several functions can be performed natively by vSphere 
much more efficiently than by CloudStack. vSphere also has additional features 
which would be beneficial to the operators of vSphere based CloudStack clouds.
www.shapeblue.com


Regards,
Harikrishna

From: avi 
Sent: Sunday, August 1, 2021 10:28 AM
To: users@cloudstack.apache.org 
Subject: vSAN vsphere 7.0 with Cloudstack.

Hell All,

I am trying to setup vmware 7.0 with cloudstack 4.15.1 but I have a slight 
problem. All the host have local storage setup(the server was used for 
different purpose before). There is no shared storage for the hosts so, I am 
looking towards vSAN concept. Just wanted to know if I can proceed towards 
using it and integrating with Cloudstack 4.15.1.
I will  be very grateful for any other suggestion and solutions to my scenario.

Thank You.

 

Re: [!!Mass Mail]Re: Scale Running VM.

[Harikrishna Patnala]

Please check the log during VM creation or during VM start. Sorry, I would have 
told you this before.

From: Дикевич Евгений Александрович 
Sent: Tuesday, July 27, 2021 1:08 PM
To: users@cloudstack.apache.org 
Subject: RE: [!!Mass Mail]Re: Scale Running VM.

I don't see any other error messages:
https://hastebin.com/jatojiwatu.yaml

 


-Original Message-
From: Harikrishna Patnala [mailto:harikrishna.patn...@shapeblue.com]
Sent: Tuesday, July 27, 2021 9:52 AM
To: users@cloudstack.apache.org
Subject: Re: [!!Mass Mail]Re: Scale Running VM.

Can you also check for the below log message in your logs. This is the other 
thing I've asked to check about the host license. You can directly check the 
host license on xenserver or look for the below log in the management server.

s_logger.warn("Host " + host.getHostname(conn) + " does not support dynamic 
scaling, so the vm " + vmSpec.getName() + " is not dynamically scalable"); 

From: Дикевич Евгений Александрович 
Sent: Tuesday, July 27, 2021 12:14 PM
To: users@cloudstack.apache.org 
Subject: RE: [!!Mass Mail]Re: Scale Running VM.

Hi
Yes, XCP-NG 8.2 supports dynamic scaling for memory.
In guest_os_details I see "xenserver.dynamicMin" and "xenserver.dynamicMax" for 
VM.
What I can check now?




-Original Message-
From: Harikrishna Patnala [mailto:harikrishna.patn...@shapeblue.com]
Sent: Tuesday, July 27, 2021 9:23 AM
To: users@cloudstack.apache.org
Subject: Re: [!!Mass Mail]Re: Scale Running VM.

Hi,

Are you facing the same exception as Abhishek ? if yes then please check my 
last email to check the host license and guest os details.

Regards,
Harikrishna

From: Дикевич Евгений Александрович 
Sent: Monday, July 26, 2021 8:01 PM
To: users@cloudstack.apache.org 
Subject: RE: [!!Mass Mail]Re: Scale Running VM.

Hi all!
I have same question.
I can scale only CPU but not RAM.

In Global Settings:
enable.dynamic.scale.vm - true
scale.retry - 2

In template:
Dynamically Scalable - Yes

XCP tools is installed.




-Original Message-
From: Harikrishna Patnala [mailto:harikrishna.patn...@shapeblue.com]
Sent: Monday, July 19, 2021 2:43 PM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Scale Running VM.

If you got till here I believe you have already enabled global setting and 
marked the template as dynamically scalable.

Please check if host license supports dynamic scaling or not. In the host 
license view on xenserver you can check that using "restrict_dmc" flag. If it 
is set to true then dynamic scaling cannot be done on VM.

If it is false, then other thing you can check is "guest_os_details" table for 
"xenserver.dynamicMin" and "xenserver.dynamicMax" under the guest OS id used in 
the template. If entries are not there try using a different template having 
these entries or insert recommended values for that OS.

Regards,
Harikrishna


From: Abishek 
Sent: Sunday, July 18, 2021 12:53 PM
To: users@cloudstack.apache.org 
Subject: Scale Running VM.

Hello EveryOne,

Is it possible to scale a running vm with host XCP-ng 8.2 and cloudstack 
4.15.1. I am testing it for production enviromnment.
I tried enabling it but received the following error:
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to scale vm 
due to Catch exception com.cloud.utils.exception.CloudRuntimeException when 
scaling VM:i-2-5-VM due to com.cloud.utils.exception.CloudRuntimeException: 
Cannot scale up the vm because of memory constraint violation: 0 <= 
memory-static-min(4294967296) <= memory-dynamic-min(8589934592) <= 
memory-dynamic-max(8589934592) <= memory-static-max(4294967296)

Where can I set these min max values.  If any one can point me to the 
documentation if its possible then I will be very grateful.
Thank You.




Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

Attention!
This email and all attachments to it are confidential and are intended solely 
for us

Re: [!!Mass Mail]Re: Scale Running VM.

[Harikrishna Patnala]

Can you also check for the below log message in your logs. This is the other 
thing I've asked to check about the host license. You can directly check the 
host license on xenserver or look for the below log in the management server.

s_logger.warn("Host " + host.getHostname(conn) + " does not support dynamic 
scaling, so the vm " + vmSpec.getName() + " is not dynamically scalable");

From: Дикевич Евгений Александрович 
Sent: Tuesday, July 27, 2021 12:14 PM
To: users@cloudstack.apache.org 
Subject: RE: [!!Mass Mail]Re: Scale Running VM.

Hi
Yes, XCP-NG 8.2 supports dynamic scaling for memory.
In guest_os_details I see "xenserver.dynamicMin" and "xenserver.dynamicMax" for 
VM.
What I can check now?

 


-Original Message-
From: Harikrishna Patnala [mailto:harikrishna.patn...@shapeblue.com]
Sent: Tuesday, July 27, 2021 9:23 AM
To: users@cloudstack.apache.org
Subject: Re: [!!Mass Mail]Re: Scale Running VM.

Hi,

Are you facing the same exception as Abhishek ? if yes then please check my 
last email to check the host license and guest os details.

Regards,
Harikrishna

From: Дикевич Евгений Александрович 
Sent: Monday, July 26, 2021 8:01 PM
To: users@cloudstack.apache.org 
Subject: RE: [!!Mass Mail]Re: Scale Running VM.

Hi all!
I have same question.
I can scale only CPU but not RAM.

In Global Settings:
enable.dynamic.scale.vm - true
scale.retry - 2

In template:
Dynamically Scalable - Yes

XCP tools is installed.




-Original Message-
From: Harikrishna Patnala [mailto:harikrishna.patn...@shapeblue.com]
Sent: Monday, July 19, 2021 2:43 PM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Scale Running VM.

If you got till here I believe you have already enabled global setting and 
marked the template as dynamically scalable.

Please check if host license supports dynamic scaling or not. In the host 
license view on xenserver you can check that using "restrict_dmc" flag. If it 
is set to true then dynamic scaling cannot be done on VM.

If it is false, then other thing you can check is "guest_os_details" table for 
"xenserver.dynamicMin" and "xenserver.dynamicMax" under the guest OS id used in 
the template. If entries are not there try using a different template having 
these entries or insert recommended values for that OS.

Regards,
Harikrishna


From: Abishek 
Sent: Sunday, July 18, 2021 12:53 PM
To: users@cloudstack.apache.org 
Subject: Scale Running VM.

Hello EveryOne,

Is it possible to scale a running vm with host XCP-ng 8.2 and cloudstack 
4.15.1. I am testing it for production enviromnment.
I tried enabling it but received the following error:
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to scale vm 
due to Catch exception com.cloud.utils.exception.CloudRuntimeException when 
scaling VM:i-2-5-VM due to com.cloud.utils.exception.CloudRuntimeException: 
Cannot scale up the vm because of memory constraint violation: 0 <= 
memory-static-min(4294967296) <= memory-dynamic-min(8589934592) <= 
memory-dynamic-max(8589934592) <= memory-static-max(4294967296)

Where can I set these min max values.  If any one can point me to the 
documentation if its possible then I will be very grateful.
Thank You.




Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

Attention!
This email and all attachments to it are confidential and are intended solely 
for use by the person (or persons) referred to (mentioned) as the intended 
recipient (recipients). If you are not the intended recipient of this email, do 
not copy or disclose its contents and delete the message and any attachments to 
it from your e-mail system. Any unauthorized use, dissemination, disclosure, 
printing or copying of this e-mail and files attached to it, except by the 
intended recipient, is illegal and is prohibited. Taking into account that data 
transmission via Internet is not secure, we assume no responsibility for any 
potential damage caused by data transmission errors or this message and the 
files attached to it.

Re: [!!Mass Mail]Re: Scale Running VM.

[Harikrishna Patnala]

Hi,

Are you facing the same exception as Abhishek ? if yes then please check my 
last email to check the host license and guest os details.

Regards,
Harikrishna

From: Дикевич Евгений Александрович 
Sent: Monday, July 26, 2021 8:01 PM
To: users@cloudstack.apache.org 
Subject: RE: [!!Mass Mail]Re: Scale Running VM.

Hi all!
I have same question.
I can scale only CPU but not RAM.

In Global Settings:
enable.dynamic.scale.vm - true
scale.retry - 2

In template:
Dynamically Scalable - Yes

XCP tools is installed.

 


-Original Message-
From: Harikrishna Patnala [mailto:harikrishna.patn...@shapeblue.com]
Sent: Monday, July 19, 2021 2:43 PM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Scale Running VM.

If you got till here I believe you have already enabled global setting and 
marked the template as dynamically scalable.

Please check if host license supports dynamic scaling or not. In the host 
license view on xenserver you can check that using "restrict_dmc" flag. If it 
is set to true then dynamic scaling cannot be done on VM.

If it is false, then other thing you can check is "guest_os_details" table for 
"xenserver.dynamicMin" and "xenserver.dynamicMax" under the guest OS id used in 
the template. If entries are not there try using a different template having 
these entries or insert recommended values for that OS.

Regards,
Harikrishna


From: Abishek 
Sent: Sunday, July 18, 2021 12:53 PM
To: users@cloudstack.apache.org 
Subject: Scale Running VM.

Hello EveryOne,

Is it possible to scale a running vm with host XCP-ng 8.2 and cloudstack 
4.15.1. I am testing it for production enviromnment.
I tried enabling it but received the following error:
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to scale vm 
due to Catch exception com.cloud.utils.exception.CloudRuntimeException when 
scaling VM:i-2-5-VM due to com.cloud.utils.exception.CloudRuntimeException: 
Cannot scale up the vm because of memory constraint violation: 0 <= 
memory-static-min(4294967296) <= memory-dynamic-min(8589934592) <= 
memory-dynamic-max(8589934592) <= memory-static-max(4294967296)

Where can I set these min max values.  If any one can point me to the 
documentation if its possible then I will be very grateful.
Thank You.




Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

Attention!
This email and all attachments to it are confidential and are intended solely 
for use by the person (or persons) referred to (mentioned) as the intended 
recipient (recipients). If you are not the intended recipient of this email, do 
not copy or disclose its contents and delete the message and any attachments to 
it from your e-mail system. Any unauthorized use, dissemination, disclosure, 
printing or copying of this e-mail and files attached to it, except by the 
intended recipient, is illegal and is prohibited. Taking into account that data 
transmission via Internet is not secure, we assume no responsibility for any 
potential damage caused by data transmission errors or this message and the 
files attached to it.

Re: [RESULT][VOTE] New life to Terraform Provider CloudStack with Apache CloudStack project

[Harikrishna Patnala]

That's great to know and thanks for all the efforts Rohit.

For release management, I would like to volunteer myself for the RM. I'll 
create the first milestone and propose myself as RM on the mailing list.

Regards,
Harikrishna

From: Rohit Yadav 
Sent: Monday, July 26, 2021 11:58 AM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [RESULT][VOTE] New life to Terraform Provider CloudStack with 
Apache CloudStack project

All,

The IP clearance process has finally passed 
(https://github.com/apache/cloudstack/issues/5159) and codebase have been 
imported:
https://github.com/apache/cloudstack-terraform-provider
https://github.com/apache/cloudstack-go

As an immediate next step, we need:

  *   Minimal changes/fixes to work towards its first release and publication 
to Terraform registry for users to use (any RM volunteers?)
  *   I'll request ASF infra to enable Travis and Github issues on these repos.

Regards.


From: Rohit Yadav 
Sent: Monday, June 21, 2021 21:36
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [RESULT][VOTE] New life to Terraform Provider CloudStack with 
Apache CloudStack project

Update - the process has been slow due to getting major contributors to agree 
on code base relicensing and getting Hashicorp to transfer the repo to its 
original/major author Sander who now has relicensed the repositories under 
APLv2:
https://github.com/xanzy/terraform-provider-cloudstack
https://github.com/xanzy/go-cloudstack

We're in the final process of IP clearance post which the code base will be 
accepted and available in the following repositories by either a ASF member 
(Paul has volunteered) or an officer of PMC with suitable permissions:
https://github.com/apache/cloudstack-terraform-provider
https://github.com/apache/cloudstack-go

As some may realise there is a new dependency repo (the Go SDK repo) which I'm 
advised by Sander should go along with the donation as it's used by the 
Terraform repo and Sander has notified submission of software grants 
(https://www.apache.org/licenses/contributor-agreements.html#grants) for both 
the repos. I'll keep the thread open if anyone has any concerns or objections 
for the additional dependency repo.

Regards.

Regards,
Rohit Yadav


From: Rohit Yadav 
Sent: Thursday, April 22, 2021 1:16:07 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [RESULT][VOTE] New life to Terraform Provider CloudStack with 
Apache CloudStack project

Update - I've created the new repository on Github: 
https://github.com/apache/cloudstack-terraform-provider

... and logged request with ASF infra:
https://issues.apache.org/jira/browse/INFRA-21772


Regards.


From: Rohit Yadav 
Sent: Thursday, April 22, 2021 13:05
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: [RESULT][VOTE] New life to Terraform Provider CloudStack with Apache 
CloudStack project

Hi all,

After 120 hours, the vote [1] for accepting codebase of Terraform Provider for 
CloudStack by the Apache CloudStack project has passed with the following votes:

+1 (PMC / binding)
4 persons (Wido, Daan, Boris, Rohit)

+1 (non-binding)
5 persons (Nathan, Abhishek, Hari, Suresh, Nicolas)

0
none

-1 (non-binding)
1 person (Rene)

Thanks to everyone participating. Following this I'll request ASF infra with a 
new repository: https://github.com/apache/cloudstack-terraform-provider have 
access enabled for all committers/PMC with issues, pull request and wiki 
features.

[1] https://markmail.org/message/26yjsewj4tgq


Regards.

rohit.ya...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue




rohit.ya...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue










 

Re: Scale Running VM.

[Harikrishna Patnala]

If you got till here I believe you have already enabled global setting and 
marked the template as dynamically scalable.

Please check if host license supports dynamic scaling or not. In the host 
license view on xenserver you can check that using "restrict_dmc" flag. If it 
is set to true then dynamic scaling cannot be done on VM.

If it is false, then other thing you can check is "guest_os_details" table for 
"xenserver.dynamicMin" and "xenserver.dynamicMax" under the guest OS id used in 
the template. If entries are not there try using a different template having 
these entries or insert recommended values for that OS.

Regards,
Harikrishna


From: Abishek 
Sent: Sunday, July 18, 2021 12:53 PM
To: users@cloudstack.apache.org 
Subject: Scale Running VM.

Hello EveryOne,

Is it possible to scale a running vm with host XCP-ng 8.2 and cloudstack 
4.15.1. I am testing it for production enviromnment.
I tried enabling it but received the following error:
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to scale vm 
due to Catch exception com.cloud.utils.exception.CloudRuntimeException when 
scaling VM:i-2-5-VM due to com.cloud.utils.exception.CloudRuntimeException: 
Cannot scale up the vm because of memory constraint violation: 0 <= 
memory-static-min(4294967296) <= memory-dynamic-min(8589934592) <= 
memory-dynamic-max(8589934592) <= memory-static-max(4294967296)

Where can I set these min max values.  If any one can point me to the 
documentation if its possible then I will be very grateful.
Thank You.


 

Re: XCP-ng 8.2 cannot start vm more than 4 core

[Harikrishna Patnala]

Hi,

I just saw the other email thread.

Yes, you can try disabling the dynamic scaling and then try deploying and start 
the VM. But I also see you are testing dynamic scale VM, in that case, please 
check my previous reply,

Regards,
Harikrishna

From: Harikrishna Patnala 
Sent: Monday, July 19, 2021 4:21 PM
To: users@cloudstack.apache.org 
Subject: Re: XCP-ng 8.2 cannot start vm more than 4 core

Hi Abhishek,

There is a global setting "xen.vm.vcpu.max" which can be configured to the 
desired value. But I think hosts in the cluster should also have the required 
number of CPU sockets. The minimum of CPU sockets numbers of the hosts in the 
cluster will be assigned to the VPCUs-max. I remember assigning a greater value 
to vCPU-max than the CPU sockets number of the host results in VM start error. 
So in your case, it should be a maximum of 4.

Regards,
Harikrishna

From: Abishek 
Sent: Monday, July 19, 2021 9:25 AM
To: users@cloudstack.apache.org 
Subject: XCP-ng 8.2 cannot start vm more than 4 core

Hello EveryOne,

I am deployed XCP-ng 8.2 host with cloudstack 4.15.1. Every thing is 
sucessfully setup with 2 XCP-ng host. But I am facing a problem while deploying 
a vm greater than 4 cores. Every time I try to start a VM with more than 4 
cores I get the error VCPUs-at-startup, 5, value greater than VCPUs-max.
I will be very grateful if somebody can help me resolve the issue. We are 
trying to go into production with XCP-ng 8.2.

Thank You.




 

Re: XCP-ng 8.2 cannot start vm more than 4 core

[Harikrishna Patnala]

Hi Abhishek,

There is a global setting "xen.vm.vcpu.max" which can be configured to the 
desired value. But I think hosts in the cluster should also have the required 
number of CPU sockets. The minimum of CPU sockets numbers of the hosts in the 
cluster will be assigned to the VPCUs-max. I remember assigning a greater value 
to vCPU-max than the CPU sockets number of the host results in VM start error. 
So in your case, it should be a maximum of 4.

Regards,
Harikrishna

From: Abishek 
Sent: Monday, July 19, 2021 9:25 AM
To: users@cloudstack.apache.org 
Subject: XCP-ng 8.2 cannot start vm more than 4 core

Hello EveryOne,

I am deployed XCP-ng 8.2 host with cloudstack 4.15.1. Every thing is 
sucessfully setup with 2 XCP-ng host. But I am facing a problem while deploying 
a vm greater than 4 cores. Every time I try to start a VM with more than 4 
cores I get the error VCPUs-at-startup, 5, value greater than VCPUs-max.
I will be very grateful if somebody can help me resolve the issue. We are 
trying to go into production with XCP-ng 8.2.

Thank You.

 

Re: Primary Storage Volume detach issue

[Harikrishna Patnala]

Hi Pradeep,

If the disk is in fcd folder means that the data disk would have already 
detached. Please check whether the volumes paths and storage pool IDs in 
CloudStack database are in sync with the location at vCenter.

Regards,
Harikrishna

From: pradeep pal 
Sent: Monday, July 12, 2021 11:05 AM
To: users@cloudstack.apache.org 
Subject: Re: Primary Storage Volume detach issue

Hi Suresh,

the DATADISK is located in fcd folder, and it is the shared iscsi primary 
volume.

Thanks
Pradeep

From: Suresh Anaparti 
Sent: Monday, July 12, 2021 10:11 AM
To: users@cloudstack.apache.org 
Subject: Re: Primary Storage Volume detach issue

Hi Pradeep,

Can you share some more details.

Is the path mentioned correctly for DATATDISK in the volumes table, and Are you 
able to locate the disk “4b1e297907f14fbaad3b7a5e57ff8793.vmdk” (in 'fcd' or VM 
folder) from the file system? Is the primary storage shared or local.

Regards,
Suresh

From: pradeep pal 
Reply to: "users@cloudstack.apache.org" 
Date: Saturday, 10 July 2021 at 2:44 PM
To: "users@cloudstack.apache.org" 
Subject: Primary Storage Volume detach issue

Hi,

When i create a vm and attached a DATADISK, after that when we detach this 
DATADISK, we are getting below error message, can you please help me to rectify 
this.

Infra Details:
ESXi Hypervisor:  6.7 U3
vCenter: 6.7u3
CloudStack: 4.15.0

2021-07-10 11:43:59,113 INFO  [c.c.h.v.m.DatastoreMO] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) Search file 
4b1e297907f14fbaad3b7a5e57ff8793.vmdk on [PROD_VPC_SZ_CLS1_PRIM_VOL1] fcd
2021-07-10 11:43:59,901 INFO  [c.c.h.v.m.DatastoreMO] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) File [PROD_VPC_SZ_CLS1_PRIM_VOL1] 
fcd/4b1e297907f14fbaad3b7a5e57ff8793.vmdk does not exist on datastore
2021-07-10 11:43:59,903 INFO  [c.c.h.v.m.DatastoreMO] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) Search file 
4b1e297907f14fbaad3b7a5e57ff8793.vmdk on [PROD_VPC_SZ_CLS1_PRIM_VOL1]
2021-07-10 11:43:59,938 INFO  [c.c.h.v.m.DatastoreMO] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) File [PROD_VPC_SZ_CLS1_PRIM_VOL1] 
4b1e297907f14fbaad3b7a5e57ff8793.vmdk does not exist on datastore

2021-07-10 11:44:03,525 ERROR [c.c.s.r.VmwareStorageProcessor] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) Failed to detach volume: Server returned HTTP 
response code: 500 for URL: 
https://10.xx.5.100/folder/i-2-30-VM?dcPath=YTTMTLSZCLDDC01&dsName=PROD_VPC_SZ_CLS1_PRIM_VOL1
java.io.IOException: Server returned HTTP response code: 500 for URL: 
https://10.xx.5.100/folder/i-2-30-VM?dcPath=YTTMTLSZCLDDC01&dsName=PROD_VPC_SZ_CLS1_PRIM_VOL1


ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-40:ctx-841f3323 
job-539/job-540 ctx-a90238bd) (logid:34cdbaf7) Invocation exception, caused by: 
com.cloud.utils.exception.CloudRuntimeException: Failed to detach volume 
100Gpradeep from VM pp-testvm01
FAILED, resultCode: 530, result: 
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"530","errortext":"Failed
 to detach volume 100Gpradeep from VM pp-testvm01"}

But when i check volume on vcenter i can able to see attached volume.


[cid:af75051e-d1ee-4121-be66-c1feee27fa76]

Thanks & Regards
Pradeep




 

Re: Adding a new host in Xen pool.

[Harikrishna Patnala]

Hi,

We can add a new Xen host to the existing pool. After adding the Xen host to 
the pool, Cloudstack will not detect any new host, we need to add the new host 
in the cluster same as other existing hosts in the pool.

Regards,
Harikrishna

From: Abishek Budhathoki 
Sent: Sunday, July 11, 2021 4:57 PM
To: users@cloudstack.apache.org 
Subject: Adding a new host in Xen pool.

Will cloudstack automatically detect a new host added in xenpool or is it not 
possible to add new host to existing xenpool. I came into the scenario to plan 
cloudstack deployment for my company in Xen server(xcp-ng). In near future I 
will need to add new host to existing pool so, will it be possible?

I will be extremally grateful for any suggestion.

Thank You.

 

Re: Snapshots are not working after upgrading to 4.15.0

[Harikrishna Patnala]

Hi Andrei,

Can you check the following things and let us know?


  1.  Can you try creating a new volume and then create snapshot of that, to 
check if this an issue with old entries
  2.  For the snapshots which are failing can you check if you are seeing any 
error messages like this "Can't find an image storage in zone with less than". 
This is to check if secondary storage free space check failed.
  3.  For the snapshots which are failing and if it is delta snapshot can you 
check if its parent's snapshot entry exists in "snapshot_store_ref" table with 
'parent_snapshot_id' of the current snapshot with 'store_role' "Image". This is 
to find the secondary storage where the parent snapshot backup is located.

Regards,
Harikrishna

From: Andrei Mikhailovsky 
Sent: Monday, June 7, 2021 7:00 PM
To: users 
Subject: Snapshots are not working after upgrading to 4.15.0

Hello everyone,

I am having an issue with volume snapshots since I've upgraded to 4.15.0. None 
of the volumes are being snapshotted regardless if the snapshot is initiated 
manually or from the schedule. The strange thing is that if I manually take the 
snapshot, the GUI shows Success status, but the Storage>Snapshots show an Error 
status. Here is what I see in the management server logs:

2021-06-07 13:55:20,022 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(Work-Job-Executor-81:ctx-08dd4222 job-86141/job-86143) (logid:be34ce01) Done 
executing com.cloud.vm.VmWorkTakeVolumeSnapshot for job-86143
2021-06-07 13:55:20,024 INFO [o.a.c.f.j.i.AsyncJobMonitor] 
(Work-Job-Executor-81:ctx-08dd4222 job-86141/job-86143) (logid:be34ce01) Remove 
job-86143 from job monitoring
2021-06-07 13:55:20,094 DEBUG [o.a.c.s.s.SnapshotServiceImpl] 
(BackupSnapshotTask-3:ctx-744796da) (logid:607dbb0e) Failed to copy snapshot
com.cloud.utils.exception.CloudRuntimeException: can not find an image stores
at 
org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:271)
at 
org.apache.cloudstack.storage.snapshot.DefaultSnapshotStrategy.backupSnapshot(DefaultSnapshotStrategy.java:171)
at 
com.cloud.storage.snapshot.SnapshotManagerImpl$BackupSnapshotTask.runInContext(SnapshotManagerImpl.java:1238)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
2021-06-07 13:55:20,152 DEBUG [c.c.s.s.SnapshotManagerImpl] 
(BackupSnapshotTask-3:ctx-744796da) (logid:607dbb0e) Backing up of snapshot 
failed, for snapshot with ID 53531, left with 2 more attempts


I've checked and the Secondary storage is configured and visible in the GUI. I 
can also mount it manually from the management server and a couple of host 
servers that I've tested. In addition, I can successfully upload an ISO image 
and that registers just fine and I can create new VMs using the newly uploaded 
ISO image.

I've had no such problems with 4.13.x ACS, so the issue seems to have been 
introduced after doing the upgrade to 4.15.0.

Could you please let me know how do I fix the issue?

Cheers

andrei

 

Re: Routers on specific cluster

[Harikrishna Patnala]

Hi Vivek,

I could found the global setting "system.vm.default.hypervisor" which is 
considered while deploying the router, you may check that. Host tags in the 
system service offering should also work, can you go through the logs while the 
virtual router is getting deployed to observe which pod/cluster/host is picked 
while allocating resources.

Regards,
Harikrishna


From: Vivek Kumar 
Sent: Friday, May 28, 2021 6:19 PM
To: users@cloudstack.apache.org 
Subject: Re: Routers on specific cluster

Hey Andrija,

Is there any setting in global setting where  we define that VR should go to 
any particular cluster, as you mentioned in previous thread. I know there is no 
as such performance or functionality issue just curious to know.


Regards,
Vivek Kumar



Software Engineer
harikrishna.patn...@shapeblue.com
www.shapeblue.com
 
 

> On 28-May-2021, at 4:45 AM, Andrija Panic  wrote:
>
> host tags should work for all Service Offerings - unless you are trying to
> create VR on VMware cluster, while your global setting is saying it should
> always be KVM (and yes, you should keep it on KVM - much quicker to
> provision/configure VR than on VMware) - did you try setting host tags on
> the Service Offering for Virtual Router (or whatever offering you are using
> for the VR) ?
>
> On Thu, 27 May 2021 at 05:20, Vivek Kumar 
> wrote:
>
>> Hello Guys,
>>
>> So I am using ACS 4.13 with Advance zone. I have 5 KVM cluster and 5
>> VMware Cluster. So whenever I provision any VPC for any of the cluster, VPC
>> VR always go and sit on KVM hosts, we have around 200 VPC VR and all are
>> there in KVM zone.  Well for functionality prospective I don’t have any
>> issues but is there any way to provision router in specific cluster as
>> well.
>>
>>
>> Storage tag and host tag doesn’t work in case of VR’s offering.
>>
>>
>> Regards
>> Vivek Kumar
>
>
>
> --
>
> Andrija Panić

Re: Quickstart question

[Harikrishna Patnala]

Hi Jeremy,

May I know the NFS version number that you are using in your environment?

Also, check the status of the default template by clicking on the template and 
then into the zones tab, to check if it is downloaded properly or not.

Regards,
Harikrishna




 

From: Jeremy Hansen
Sent: Sunday, May 30, 2021 4:51 PM
To: users@cloudstack.apache.org
Subject: Re: Quickstart question

Went over the process about 20 times and made progress.  I’m able to launch a 
VM as long as the template is a direct download bypassing secondary storage.  I 
see this in the logs:

2021-05-30 04:01:57,148 DEBUG [c.c.a.t.Request] (AgentManager-Handler-12:null) 
(logid:) Seq 2-4381439487478071309: Processing:  { Ans: , MgmtId: 
198690285003419, via: 2, Ver: v1, Flags: 10, 
[{"com.cloud.agent.api.Answer":{"result":"false","details":"com.cloud.utils.exception.CloudRuntimeException:
 GetRootDir for nfs://192.168.10.60/volume1/cloudstack-dev/secondary failed due 
to com.cloud.utils.exception.CloudRuntimeException: Unable to mount 
192.168.10.60:/volume1/cloudstack-dev/secondary at 
/mnt/SecStorage/4683f710-43e8-359d-bc9a-041363aa77b9 due to mount.nfs: parsing 
error on 'vers=‘ option

I’m not sure how to troubleshoot this issue.  Do I have to specify the version 
somewhere for NFS?

Thanks

> On May 30, 2021, at 12:30 AM, Jeremy Hansen  wrote:
>
> At the very end of the configuration wizard when it’s doing the Host vm 
> install, I get this error and I can’t get past it:
>
> Something went wrong; please correct the following:
> TypeError: Cannot read property 'value' of undefined
>
> Thanks
> -jeremy
>
>
>> On May 29, 2021, at 11:27 PM, Jeremy Hansen  wrote:
>>
>> New to Cloudstack.  I’m trying to get the Quickstart going.
>>
>> It feels like an issue with secondary storage but I’m not quite sure how to 
>> troubleshoot.
>>
>> CentOS 8, kvm.  Created a bridge per the quick install docs.
>>
>> 
>>
>> I see no data for templates and isos.  I did do the template install.  The 
>> secondary storage VM is running and connected:
>>
>> 
>>
>>
>> 
>>
>>
>> 
>>
>> I attempted to upload an iso and it failed.
>>
>> Also, how do I get back to the initial configuration wizard.  I dismissed it 
>> but I’m not sure how to get it back.
>>
>> Thanks!
>> -jeremy
>>
>>
>>
>>
>>
>>
>>
>>
>>
>

Re: Hypervisor limits

[Harikrishna Patnala]

Hi,

The management server could have taken the default value for the max data 
volumes limit.
| default|  6 |

Please check the hypervisor version in the host table to know which version it 
has detected. You can view it from the host section in UI.

If it is correctly marked to 8.2.0, adding hypervisor capabilities entry for 
8.2.0 in the "hypervisor_capabilities" table will fix your problem. You can try 
keeping the old values as in 8.0.0 version.

If the management server has the support for the XenServer version in its 
release, then these entries would have been there.

Regards,
Harikrishna

From: Дикевич Евгений Александрович 
Sent: Tuesday, May 18, 2021 12:21 PM
To: users@cloudstack.apache.org 
Subject: Hypervisor limits

Hi all!
I have ACS 4.14.1 with XCP-NG 8.2 with PreSetup iSCSI storage.
When I add more than 6 data disks it says me that 6 volumes are maximum.
This is hypervisor limits for XenServer lower than 6.x.
In DB we can see:
mysql> select hypervisor_version,max_data_volumes_limit from 
cloud.hypervisor_capabilities where hypervisor_capabilities.hypervisor_type = 
'XenServer';
+++
| hypervisor_version | max_data_volumes_limit |
+++
| 5.6|  6 |
| 5.6 FP1|  6 |
| 5.6 SP2|  6 |
| 6.0| 13 |
| 6.0.2  | 13 |
| 6.1.0  | 13 |
| 6.2.0  | 13 |
| 6.5.0  | 13 |
| 7.0.0  | 13 |
| 7.1.0  | 13 |
| 7.1.1  |253 |
| 7.1.2  |253 |
| 7.2.0  | 13 |
| 7.3.0  | 13 |
| 7.4.0  | 13 |
| 7.5.0  | 13 |
| 7.6.0  |253 |
| 8.0.0  |253 |
| default|  6 |
| XCP 1.0|  6 |
| XCP-ng 7.4.0   | 13 |
+++
21 rows in set (0.00 sec)

My question is - why ACS detects my hosts are "XenServer 6.1.x and before" and 
how I can change it?
Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

Attention!
This email and all attachments to it are confidential and are intended solely 
for use by the person (or persons) referred to (mentioned) as the intended 
recipient (recipients). If you are not the intended recipient of this email, do 
not copy or disclose its contents and delete the message and any attachments to 
it from your e-mail system. Any unauthorized use, dissemination, disclosure, 
printing or copying of this e-mail and files attached to it, except by the 
intended recipient, is illegal and is prohibited. Taking into account that data 
transmission via Internet is not secure, we assume no responsibility for any 
potential damage caused by data transmission errors or this message and the 
files attached to it.

 

Re: Initial Zone Setup Wizard

[Harikrishna Patnala]

Hi Mike,

In 4.15, new UI has only option to setup advanced zone. If you want to setup 
basic zone in 4.15 you can use legacy UI (x.x.x.x:8080/client/legacy/). FYI the 
basic zone wizard is restored in 4.15.1 version of CloudStack 
(https://github.com/apache/cloudstack/pull/4882)

I cannot see your images in the email, I guess you are talking about traffic 
labels for guest traffic for private gateway 
(http://docs.cloudstack.apache.org/projects/archived-cloudstack-administration/en/latest/networking_and_traffic.html#guest-traffic-for-private-gateway).
 If you want to understand the complete network concepts of CloudStack and 
decide on which zone to use (either basic or advanced) you can go through this 
link 
http://docs.cloudstack.apache.org/projects/archived-cloudstack-administration/en/latest/networking_and_traffic.html#
Managing Networks and Traffic — Apache CloudStack Administration Documentation 
4.11.0.0 documentation - Apache CloudStack 4.15.0.0 
documentation
Managing Networks and Traffic¶. In a CloudStack, guest VMs can communicate with 
each other using shared infrastructure with the security and user perception 
that the guests have a private LAN.
docs.cloudstack.apache.org

Managing Networks and Traffic — Apache CloudStack Administration Documentation 
4.11.0.0 documentation - Apache CloudStack 4.15.0.0 
documentation
Managing Networks and Traffic¶. In a CloudStack, guest VMs can communicate with 
each other using shared infrastructure with the security and user perception 
that the guests have a private LAN.
docs.cloudstack.apache.org
Regards,
Harikrishna


From: Corey, Mike 
Sent: Tuesday, May 11, 2021 2:02 AM
To: users@cloudstack.apache.org 
Subject: Initial Zone Setup Wizard


Hi,



I’m starting up the new 4.15 ui and trying to create my first zone.  The new UI 
is very nice; however, I’m not sure I can select the “Advanced” wizard option.  
The only “clickable” thing on this screen is NEXT.  Am I supposed to be able to 
click on “Advanced” to go through that wizard versus the basic wizard?



[cid:image003.jpg@01D745BA.0D550BF0]



Next question is regarding “Traffic Label” on the Physical Network window.  
What should the labels be?  Could I get some clarity on this please?



[cid:image006.jpg@01D745BA.0D550BF0]









Mike Corey

Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US

SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United States

T +1 610 661 0905, M +1 484 274 2658, E mike.co...@sap.com



[cid:image007.png@01D745BA.0D550BF0]