Re: [DISCUSS] New terraform git tag for registry workaround

[Harikrishna Patnala]

okay, given the situation your proposal seems right Rohit. Like Daan asked, if 
we can prevent this situation in future we need to document it also.

Regards,
Harikrishna
 



From: Daan Hoogland 
Sent: Monday, April 15, 2024 4:50 PM
To: dev 
Subject: Re: [DISCUSS] New terraform git tag for registry workaround

I think your proposals are ok as an ad-hoc solution to the current
situation @Rohit Yadav . I wonder how we should deal with this in the
future though.

1. As for the numbering, do we have a procedure to prevent this issue
in the future?
2. The provider is part of apache and I think the link
https://github.com/apache/terraform-provider-cloudstack should be
validated. What exactly is the objection to this?

On Mon, Apr 15, 2024 at 12:05 PM Rohit Yadav  wrote:
>
> All,
>
> The recent Terraform provider release v0.5.0 has a problem with the Terraform 
> registry website. 
> https://github.com/apache/cloudstack-terraform-provider/issues/109
>
> The registry support isn't able to provide a resolution now, their manual 
> resync button on the provider isn't fixing the issue.
>
> While I've documented the steps for manually installing and using the 
> provider. Most terraform/tofu users are used to consuming a provider from the 
> registry.
>
> If there are no objections, I propose that we just tag the current version as 
> v0.5.1 and push it on the registry for the purpose of publishing on the 
> registry website. We may need not do a formal vote for this as code wise 
> nothing has changed and we can make this tag to be a community release tag 
> solely done for the purpose of having a workaround on the registry website  
> https://registry.terraform.io/providers/cloudstack/cloudstack/latest which 
> gets published via 
> https://github.com/cloudstack/terraform-provider-cloudstack as the registry 
> also has a strict repo naming policy (due to which it can't use the repo 
> under Apache org).
>
> Thoughts?
>
> Regards.
>
>
>


--
Daan

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: dev@cloudstack.apache.org ; 
us...@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: us...@cloudstack.apache.org , 
dev@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: dev@cloudstack.apache.org , 
us...@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: dev@cloudstack.apache.org , 
us...@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: dev@cloudstack.apache.org ; 
us...@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: dev@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: Re-Introduction

[Harikrishna Patnala]

Hi Sina,

Short time but good to see you are back.

Regards,
Harikrishna

From: Sina Kashipazha 
Date: Monday, 18 March 2024 at 2:41 AM
To: dev 
Subject: Re-Introduction
Dear All,

My name is Sina Kashipazha, and you may remember me from my time at Leaseweb. I 
wanted to take this opportunity to reintroduce myself as I have recently joined 
ComplianceWise.

I work as a software engineer, where I've had the opportunity to engage with 
cloud computing technologies and expand my understanding of scalable solutions. 
While my programming repertoire includes JavaScript, Python, and Go, my primary 
strength lies in Java, which is the cornerstone of my skill set for tackling 
various projects. Beyond programming, my expertise extends into networking and 
containerization, equipping me with a comprehensive skill set to design and 
optimize sophisticated, scalable systems efficiently.

My first few months at ComplianceWise were very busy as I focused on adapting 
to my new role. Now that I am more settled, I am ready to take on new 
challenges and actively contribute to our community's projects once more.

I'm looking forward to re-engaging with you all and contributing to Apache 
CloudStack's success in any way I can. Please feel free to reach out if you 
have any PRs or issues you think I could help with.

Warmest regards,
Sina Kashipazha

 

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: [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: dev@cloudstack.apache.org , 
us...@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: [VOTE] go life with new website(design)

[Harikrishna Patnala]

+1 (binding)

Thanks,
Harikrishna

From: Daan Hoogland 
Date: Thursday, 1 February 2024 at 6:02 PM
To: dev 
Subject: [VOTE] go life with new website(design)
LS,

I am not sure this is still needed after all the discussions
before,but I would like to start a lazy consent vote threat anyway
there are some non-blocking rest points mentioned and we can
administer those in the repo for the site [1]

so without further ado;
Do we want to go life with the website as staged in cloudstack.staged.apache.org

+1 yes
0 no opinion (no reaction suffices as well)
-1 no (please state reasons


[1] https://github.com/apache/cloudstack-www/issues/new/choose

 

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 , dev@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: us...@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: [PROPOSE] Upgrade JDK from 11 to 17

[Harikrishna Patnala]

Good start Vishesh. Thanks

Regards,
Harikrishna

From: Vishesh Jindal 
Date: Tuesday, 2 January 2024 at 2:39 PM
To: dev@cloudstack.apache.org 
Subject: [PROPOSE] Upgrade JDK from 11 to 17
Hi all,

Java 11 has already reached end of life, and the next LTS Java 17's EOL is in 
2027.

I have added a list of TODOs here: 
https://github.com/apache/cloudstack/issues/7686#issuecomment-1871844301
Let me know if I missed anything.

Upgrading some of the packages would require changes because of deprecations or 
new APIs which might take some time. I propose we start doing these changes in 
different PRs and upgrade to JDK17 in the next release (4.20). This will 
require considerable testing because of changes in the dependencies and the JDK 
itself.






 

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: 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: us...@cloudstack.apache.org , 
dev@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: dev@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: dev@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: dev@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: [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: dev@cloudstack.apache.org , 
us...@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: [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: dev@cloudstack.apache.org , 
us...@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: Hello Community!!

[Harikrishna Patnala]

Welcome Jithin

Regards,
Harikrishna

From: Jithin Raju 
Date: Tuesday, 14 March 2023 at 1:27 PM
To: us...@cloudstack.apache.org , 
dev@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: [DISCUSSION] Name confirmation before Destructive and unrecoverable actions

[Harikrishna Patnala]

I agree with Sina to some extent as he mentioned in the PR, we should not allow 
deleting the own user account from UI alteast. I tried deleting the user where 
I logged in, it immediately kicked me out of the logged in session.

Daan, we are already not allowing a normal user to delete their own account. 
This case is for the root/resource/domain admin accounts.

Regards,
Harikrishna

On 16/02/23, 8:53 PM, "Sina Kashipazha"  
wrote:

Daan, I created the following PR, it don't allow users to delete themselves.

https://github.com/apache/cloudstack/pull/7242



--
 

- Original Message ---
On Wednesday, February 15th, 2023 at 14:34, Sina Kashipazha 
mailto:s.kashipa...@protonmail.com.inva>LID> 
wrote:


>

>

>

>

> Yes, they shouldn't be allowed to delete themselves. I'm totally agree with 
> that.
>

> We can add this extra step as well, before users remove something valuable 
> like volume or network, etc.
>

>

> --- Original Message ---
> On Wednesday, February 15th, 2023 at 14:09, Daan Hoogland 
> daan.hoogl...@gmail.com wrote:
>

>

>

> > again Sina, I think the users should never be allowed to delete themselves.
> > What is the use of such an action?
>

> > On Wed, Feb 15, 2023 at 12:28 PM Sina Kashipazha
> > s.kashipa...@protonmail.com.invalid
> >  wrote:
>

> > > I agree that it is not as pressing as it looks, but the consequences are
> > > high if users remove their account. In some setup, their VM will be 
> > > deleted
> > > immediately for ever.
>

> > > Cause the network, VPS, account and many more deletion actions are look
> > > the same user will not read the confirmation pop up :-)
>

> > > The proposed extra step that asks users to input the account name will
> > > prevent accident.
>

> > > --- Original Message ---
> > > On Wednesday, February 15th, 2023 at 10:17 AM, Wei ZHOU <
> > > ustcweiz...@gmail.com> wrote:
>

> > > > Agree with Daan
>

> > > > -Wei
>

> > > > On Wednesday, 15 February 2023, Daan Hoogland 
> > > > daan.hoogl...@gmail.com
>

> > > > wrote:
>

> > > > > seems ok, but I do not see the use case as pressing. I´d rather say
> > > > > that a
> > > > > user should not be able to destroy their own account.
>

> > > > > On Tue, Feb 14, 2023 at 3:32 PM Sina Kashipazha
> > > > > s.kashipa...@protonmail.com.invalid
> > > > >  wrote:
>

> > > > > > Hey guys,
>

> > > > > > Cloudstack users can delete their account accidentally and lock
> > > > > > themselves
> > > > > > from accessing the CloudStack panel. A link to an account placed
> > > > > > next to
> > > > > > ISO, template, VM and other entities in CloudStack's UI. If 
> > > > > > customers
> > > > > > doesn't paying attention, they would click on the account link
> > > > > > instead of
> > > > > > the link to the entity they want (vm, template, ISO etc.) Then, if
> > > > > > they
> > > > > > had
> > > > > > wanted to delete that entity, they would press delete button without
> > > > > > realising they were on the account page, and press Confirm.
>

> > > > > > I'm suggesting to add an extra step before deletion. In that step
> > > > > > users
> > > > > > must write the account name, unless otherwise they can't confirm
> > > > > > deletion.
> > > > > > Github, like many other applications asks you to write down the
> > > > > > entity's
> > > > > > name before DESTRUCTIVE and UNRECOVERABLE actions.
>

> > > > > > I've also created the following issue in Github:
> > > > > > https://github.com/apache/cloudstack/issues/7219
>

> > > > > > Please let me know your thoughts about the proposal.
>

> > > > > > Kind regards,
> > > > > > Sina
>

> > > > > --
> > > > > Daan
>

> > --
> > Daan

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 , 
dev@cloudstack.apache.org , 
us...@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: Hello

[Harikrishna Patnala]

Welcome Vishesh !

Regards,
Harikrishna

From: Vishesh Jindal 
Date: Wednesday, 1 February 2023 at 9:14 PM
To: dev@cloudstack.apache.org 
Subject: Hello
Hi All,

This is Vishesh. I have recently joined ShapeBlue. I am looking forward to 
contributing to the cloudstack project and working with the community.

Thanks!
Vishesh Jindal
vishesh.jin...@shapeblue.com



 

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: dev@cloudstack.apache.org ; 
us...@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: New B plugin for EMC Networker

[Harikrishna Patnala]

Hi Curious,

Good to know that you could implement what you need.

Regarding the framework part, you might have already checked this document, if 
not please have a look to understand how the Backup and recovery framework is 
made. 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Backup+and+Recovery+Framework

As an example, you can check the implementation for the Veeam backup plugin 
https://github.com/apache/cloudstack/tree/main/plugins/backup

Regarding the specific question about restore method I think it is not 
hypervisor specific. If you see this method 
https://github.com/shapeblue/cloudstack/blob/c3a1c7862f6b490c4ee78b9796fd6aec0cd9a9ad/plugins/backup/veeam/src/main/java/org/apache/cloudstack/backup/VeeamBackupProvider.java#L213

This is implemented for Veeam in VeeamBackupProvider. I assume you also need to 
develop a similar plugin and implement methods as per your need. If it is 
required to run the commands from either hypervisor, you will have to implement 
specific command answer models as I explained in the previous reply or you can 
use the SSH way as well.

Hope this helps.

Regards,
Harikrishna



From: Curious Pandora 
Sent: Thursday, July 7, 2022 6:03 AM
To: dev@cloudstack.apache.org 
Subject: Re: New B plugin for EMC Networker

Hello Harikrishna,

Thank you for your feedback.  We have implemented the communication and
works great.
We are at the restore part now  and it seems that there is no
implementation for the B Framework for KVM.
The restoreBackupVolumeAndAttachToVM() and restoreBackup() looks like they
are Hypervisor specific.

For other hypervisors it looks like this is implemented in
HypervisorGuruBase.

Does this have to be implemented for KVM too ?


On Tue, Jul 5, 2022 at 7:27 AM Harikrishna Patnala <
harikrishna.patn...@shapeblue.com> wrote:

> Hello Curious,
>
> This is interesting and as far as I understand you can go with that
> approach of SSH into the host and run the scripts that are required.
>
> For better control from the CloudStack management server, you can also try
> Command-Answer model to send a command to CloudStack agent in KVM host and
> get the required job done on the host.
>
> For example, you may refer to the implementation of
> "UpdateHostPasswordCommand<
> https://github.com/shapeblue/cloudstack/blob/523805c8bc63e5d5f2b8634e46db9bb9ec6214ad/server/src/main/java/com/cloud/resource/ResourceManagerImpl.java#L2878>"
> class which updates the host password using a script. Following are the
> abstract steps that are done during the process.
>
>   1.  API implementation "updateHostPassword<
> https://github.com/shapeblue/cloudstack/blob/893a88d225276e45f12f9490e6af2c94a81c2965/api/src/main/java/org/apache/cloudstack/api/command/admin/host/UpdateHostPasswordCmd.java#L30
> >"
>   2.  Prepare "UpdateHostPasswordCommand<
> https://github.com/shapeblue/cloudstack/blob/523805c8bc63e5d5f2b8634e46db9bb9ec6214ad/server/src/main/java/com/cloud/resource/ResourceManagerImpl.java#L2878>"
> and send it to corresponding host
>   3.  Implement a resource wrapper
> "LibvirtUpdateHostPasswordCommandWrapper<
> https://github.com/shapeblue/cloudstack/blob/893a88d225276e45f12f9490e6af2c94a81c2965/plugins/hypervisors/kvm/src/main/java/com/cloud/hypervisor/kvm/resource/wrapper/LibvirtUpdateHostPasswordCommandWrapper.java#L29>"
> and run the specific script here.
>
> You may follow a similar procedure like above or you can directly use the
> SSH model as you mentioned.
>
> Hope this helps, let us know if you need something else.
>
> Regards,
> Harikrishna
> 
> From: Curious Pandora 
> Sent: Monday, July 4, 2022 6:17 PM
> To: dev@cloudstack.apache.org 
> Subject: Re: New B plugin for EMC Networker
>
> We are a cloud provider using cloudstack for our IaaS services.
>
>
>
>

 

> On Mon, Jul 4, 2022 at 3:21 PM Sven Vogel  wrote:
>
> > Hi p4nd0ra - the curious,
> >
> > who is deleloping the plugin?
> >
> > Cheers
> >
> > Sven
> >
> >
> >
> > __
> >
> > Sven Vogel
> > Senior Manager Research and Development - Cloud and Infrastructure
> >
> > EWERK DIGITAL GmbH
> > Br?hl 24, D-04109 Leipzig
> > P +49 341 42649 - 99
> > F +49 341 42649 - 98
> > s.vo...@ewerk.com
> > www.ewerk.com<http://www.ewerk.com>
> >
> > Gesch?ftsf?hrer:
> > Dr. Erik Wende, Markus B?ttcher, Marcus Leeb
> > Registergericht: Leipzig HRB 9065
> >
> > Support:
> > +49 341 42649 555
> >
> > Zertifiziert nach:
> > ISO/IEC 27001:2013
> > DIN EN ISO 9001:2015
> > DIN ISO/IEC 2-1:2018
> >
> > ISAE 3402 Typ II Assessed
> >

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: dev@cloudstack.apache.org ; 
us...@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: New B plugin for EMC Networker

[Harikrishna Patnala]

Hello Curious,

This is interesting and as far as I understand you can go with that approach of 
SSH into the host and run the scripts that are required.

For better control from the CloudStack management server, you can also try 
Command-Answer model to send a command to CloudStack agent in KVM host and get 
the required job done on the host.

For example, you may refer to the implementation of 
"UpdateHostPasswordCommand"
 class which updates the host password using a script. Following are the 
abstract steps that are done during the process.

  1.  API implementation 
"updateHostPassword"
  2.  Prepare 
"UpdateHostPasswordCommand"
 and send it to corresponding host
  3.  Implement a resource wrapper 
"LibvirtUpdateHostPasswordCommandWrapper"
 and run the specific script here.

You may follow a similar procedure like above or you can directly use the SSH 
model as you mentioned.

Hope this helps, let us know if you need something else.

Regards,
Harikrishna

From: Curious Pandora 
Sent: Monday, July 4, 2022 6:17 PM
To: dev@cloudstack.apache.org 
Subject: Re: New B plugin for EMC Networker

We are a cloud provider using cloudstack for our IaaS services.


 

On Mon, Jul 4, 2022 at 3:21 PM Sven Vogel  wrote:

> Hi p4nd0ra - the curious,
>
> who is deleloping the plugin?
>
> Cheers
>
> Sven
>
>
>
> __
>
> Sven Vogel
> Senior Manager Research and Development - Cloud and Infrastructure
>
> EWERK DIGITAL GmbH
> Br?hl 24, D-04109 Leipzig
> P +49 341 42649 - 99
> F +49 341 42649 - 98
> s.vo...@ewerk.com
> www.ewerk.com
>
> Gesch?ftsf?hrer:
> Dr. Erik Wende, Markus B?ttcher, Marcus Leeb
> Registergericht: Leipzig HRB 9065
>
> Support:
> +49 341 42649 555
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 2-1:2018
>
> ISAE 3402 Typ II Assessed
>
> EWERK-Blog | LinkedIn<
> https://www.linkedin.com/company/ewerk-group> | Xing<
> https://www.xing.com/company/ewerk> | Twitter<
> https://twitter.com/EWERK_Group> | Facebook<
> https://de-de.facebook.com/EWERK.Group/>
>
>
> Ausk?nfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschlie?lich etwaiger beigef?gter Dateien) ist
> vertraulich und nur f?r den Empf?nger bestimmt. Sollten Sie nicht der
> bestimmungsgem??e Empf?nger sein, ist Ihnen jegliche Offenlegung,
> Vervielf?ltigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverz?glich den Absender und l?schen Sie
> die E-Mail (einschlie?lich etwaiger beigef?gter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> Von: Curious Pandora 
> Datum: Montag, 4. Juli 2022 um 14:11
> An: dev@cloudstack.apache.org 
> Betreff: New B plugin for EMC Networker
> Hello all,
>
> We are developing a new plugin for supporting KVM backups for DELL/EMC
> Networker.
>
> Unfortunately there is no straight way to do it (it's the same for almost
> all backup softwares out there) and we will need to access the hypervisor
> hosts directly and execute some custom scripts.
>
> As you understand this raises a series of design, implementation and
> operation decisions and issues and we think it's better if we ask for the
> advise of the community.
>
> For starters, the implementation of SLA based backups is not feasible due
> to Networker design and concepts.
>
> It is most likely feasible to utilize ad-hoc and scheduled backups
> (provided that are initiated by cloudstack).
>
> We wonder if we can utilize the ssh functionality from the management host
> to the hypervisors (that is used for example to restart ssh-agent if
> kvm.ssh.to.agent is enabled to execute a centralized script in bash that
> will be included in the cloudstack-agent.
>
> Is this approach acceptable ?
>
> Kind regards,
>
>
>
> --
> p4nd0ra - the curious
>


--
p4nd0ra - the curious

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: us...@cloudstack.apache.org ; 
dev@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: us...@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: [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: us...@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: us...@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: [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: 'us...@cloudstack.apache.org' ; 
dev@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: [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: dev@cloudstack.apache.org 
Cc: us...@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: 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: us...@cloudstack.apache.org 
Cc: dev@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: 'us...@cloudstack.apache.org' 
Cc: dev@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: Asking this in dev as there are many fixes for volumes/snapshots on 4.15.2 and 4.16.0

[Harikrishna Patnala]

Hi Kristaps,

With VMware, I could reproduce this issue where multiple volumes are 
transferred to the secondary storage. This is a VMware only issue, other 
hypervisors work fine.

I've created a github issue to fix/track it 
https://github.com/apache/cloudstack/issues/5498
[https://opengraph.githubassets.com/9a7b1ad38b90cdbff8c4bd57ad5ef68e9ffe917368083c7b3d1527690c539b79/apache/cloudstack/issues/5498]
Single volume snapshot operation exports all volumes of the VM to the secondary 
storage · Issue #5498 · 
apache/cloudstack
ISSUE TYPE Bug Report COMPONENT NAME VMware, Volume Snapshot CLOUDSTACK VERSION 
4.15.2, main CONFIGURATION OS / ENVIRONMENT SUMMARY When a VM has multiple 
volumes and snapshot or recurring snapshot...
github.com
I'll start working on this issue and update it. Thanks for letting us know.

Regards,
Harikrishna

From: Kristaps Cudars 
Sent: Friday, September 17, 2021 2:40 PM
To: dev@cloudstack.apache.org 
Subject: Asking this in dev as there are many fixes for volumes/snapshots on 
4.15.2 and 4.16.0

4.15.1/Vmware

When you create reoccurring volume snapshot task, instead of transferring only 
that volume all volumes that are associated with VM are transferred to 
secondary storage.

Way how we find this is that we have some VM with 8~TB disks that should not be 
backed up and our secondary storage now has increased in size 10 times.

Maybe this is fixed/resolved with different wording?


 

Re: [ANNOUNCE] Nicolas Vazquez has joined the PMC

[Harikrishna Patnala]

wow, congratulations Nicolas.

Regards,
Harikrishna

From: Rohit Yadav 
Sent: Tuesday, August 3, 2021 10:11 AM
To: dev@cloudstack.apache.org 
Subject: Re: [ANNOUNCE] Nicolas Vazquez has joined the PMC

Congratulations Nicolas!

Regards.

Regards,
Rohit Yadav


From: Pearl d'Silva 
Sent: Tuesday, August 3, 2021 9:44:56 AM
To: dev 
Subject: Re: [ANNOUNCE] Nicolas Vazquez has joined the PMC

Congratulations Nicolas!


Regards,
Pearl

From: Gabriel Beims Bräscher 
Sent: Tuesday, August 3, 2021 12:58 AM
To: dev 
Subject: [ANNOUNCE] Nicolas Vazquez has joined the PMC

Hello @dev,

I am pleased to announce that Nicolas Vazquez was invited to join the
Project Management Committee (PMC) for Apache CloudStack, and he has
gracefully accepted.

Nicolas has been working actively on the project since 2015 and has proven
a great contributor, committer and now will be part of the PMC.

Please join me in congratulating Nicolas and wish him wisdom in his new
role.

On behalve of the PMC,
--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair







 

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: dev@cloudstack.apache.org ; 
us...@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: dev@cloudstack.apache.org ; 
us...@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: dev@cloudstack.apache.org ; 
us...@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: dev@cloudstack.apache.org ; 
us...@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: [ANNOUNCE] New committer: Daniel Augusto Veronezi Salvador

[Harikrishna Patnala]

Congratulations Daniel!

Regards,
Harikrishna

From: Gabriel Beims Bräscher 
Sent: Tuesday, July 6, 2021 10:51 PM
To: dev 
Subject: [ANNOUNCE] New committer: Daniel Augusto Veronezi Salvador

The Project Management Committee (PMC) for Apache CloudStack
has invited Daniel to become a committer and we are pleased
to announce that the contributor has accepted.

Please join me in congratulating Daniel on this accomplishment.

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.
Being a PMC member enables assistance with the management
and to guide the direction of the project.

--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair

 

Re: [ANNOUNCE] New committer: David Jumani

[Harikrishna Patnala]

Congratulations David!

Regards,
Harikrishna

From: Gabriel Beims Bräscher 
Sent: Tuesday, July 6, 2021 10:51 PM
To: dev 
Subject: [ANNOUNCE] New committer: David Jumani

The Project Management Committee (PMC) for Apache CloudStack
has invited David to become a committer and we are pleased
to announce that the contributor has accepted.

Please join me in congratulating David on this accomplishment.

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.
Being a PMC member enables assistance with the management
and to guide the direction of the project.

--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair

 

Re: [ANNOUNCE] New committer: Pearl DSilva

[Harikrishna Patnala]

Congratulations Pearl

Regards,
Harikrishna

From: Gabriel Beims Bräscher 
Sent: Tuesday, July 6, 2021 10:51 PM
To: dev 
Subject: [ANNOUNCE] New committer: Pearl DSilva

The Project Management Committee (PMC) for Apache CloudStack
has invited Pearl to become a committer and we are pleased
to announce that the contributor has accepted.

Please join me in congratulating Pearl on this accomplishment.

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.
Being a PMC member enables assistance with the management
and to guide the direction of the project.

--
Gabriel Beims Bräscher
Apache CloudStack PMC Chair

 

Re: Error in hitting resetSSHKeyForVirtualMachine api

[Harikrishna Patnala]

Hi Bikram,

Please go through the management-server.log or vmops.log when you call this API 
and observe the stack trace of the error, you will get to know what is the 
exact error on running that SQL query. Accordingly, update or fix the DAO as 
suggested by David.

Regards,
Harikrishna

From: David Jumani 
Sent: Friday, June 25, 2021 4:06 PM
To: dev 
Subject: Re: Error in hitting resetSSHKeyForVirtualMachine api

Hi Bikram,

In addition to what Rohit had mentioned, also go through 
https://github.com/shapeblue/hackerbook/blob/main/hack/db.md to ensure that the 
DAO is properly implemented so the query is generated correctly

From: Rohit Yadav 
Sent: Friday, June 25, 2021 3:45 PM
To: dev ; David Jumani 
Subject: Re: Error in hitting resetSSHKeyForVirtualMachine api

Hi Bikram,

(FYI - Bikram is our GSoC21 [1] student, cc @David 
Jumani primary mentor)

  *   Are you hitting this on the latest main​ branch?
  *   Is the ssh key registered in the DB a valid SSH key and are you testing 
this using Simulator or KVM (or something else)?
  *   Is the keypairs parameter something you've introduced as part of your 
project? Is it handled properly at the API implement (refer 
https://github.com/shapeblue/hackerbook/blob/main/hack/api.md#introduction)

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/GSoC+2021


Regards.

Rohit Yadav
Principal Engineer
rohit.ya...@shapeblue.com
www.shapeblue.com








From: Daan Hoogland 
Sent: Friday, June 25, 2021 13:19
To: dev 
Subject: Re: Error in hitting resetSSHKeyForVirtualMachine api

Bikram,
I see and extra parameter "keypairs" that would not be recognised and hence
ignored but otherwise your cli seem correct according to [1]

I think you hit a bug, please investigate the logs and create an issue at
[2] if you feel it is a  cloudstack issue or at [3] if it is a cmk issue

[1]
http://cloudstack.apache.org/api/apidocs-4.15/apis/resetSSHKeyForVirtualMachine.html
[2] https://github.com/apache/cloudstack/issues/new/choose
[3] https://github.com/apache/cloudstack-cloudmonkey/issues/new/choose

regards,

On Fri, Jun 25, 2021 at 9:01 AM Bikram Biswas 
wrote:

> Here is the command and message in cloudmonkey. The VM is connected with
> the ssh-key-pair with the name 'myname'
>
> (bicrxm)  > reset sshkeyforvirtualmachine account=admin
> domainid=a7509cc5-d50e-11eb-afe0-646e69d9cd09 keypair=myname
> id=c9e37866-2314-46f8-8741-9b2d045ad40a keypairs=myname
> {
>   "accountid": "a751fb3a-d50e-11eb-afe0-646e69d9cd09",
>   "cmd":
> "org.apache.cloudstack.api.command.admin.vm.ResetVMSSHKeyCmdByAdmin",
>   "completed": "2021-06-25T12:24:47+0530",
>   "created": "2021-06-25T12:24:45+0530",
>   "jobid": "53db8eca-cf4c-4eb6-a9f2-a37d54af0f7d",
>   "jobinstanceid": "c9e37866-2314-46f8-8741-9b2d045ad40a",
>   "jobinstancetype": "VirtualMachine",
>   "jobprocstatus": 0,
>   "jobresult": {
> "errorcode": 530,
> "errortext": "Caught: com.mysql.cj.jdbc.ClientPreparedStatement:
> SELECT ssh_keypairs.id, ssh_keypairs.account_id, ssh_keypairs.domain_id,
> ssh_keypairs.keypair_name, ssh_keypairs.fingerprint,
> ssh_keypairs.public_key FROM ssh_keypairs WHERE ssh_keypairs.account_id =
> 2  AND ssh_keypairs.domain_id = 1  AND ssh_keypairs.keypair_name = ** NOT
> SPECIFIED **  ORDER BY ssh_keypairs.keypair_name DESC "
>   },
>   "jobresultcode": 530,
>   "jobresulttype": "object",
>   "jobstatus": 2,
>   "userid": "a781b145-d50e-11eb-afe0-646e69d9cd09"
> }
>  Error: async API failed for job 53db8eca-cf4c-4eb6-a9f2-a37d54af0f7d
> (bicrxm)  >
>
>

--
Daan




 

Re: GSoC '21

[Harikrishna Patnala]

Congratulations Bikram. Welcome to CloudStack and good luck with your project.

We already have email exchanges, also please feel free to reach out to the 
community for any help or information.

Regards,
Harikrishna

From: Bikram Biswas 
Sent: Tuesday, May 18, 2021 10:40 AM
To: dev@cloudstack.apache.org 
Subject: GSoC '21

Hi everyone. I am very glad that my proposal for Google Summer of Code has
been accepted.
I am very excited to work in GSoC'21 for Cloudstack issue #4813 (Support
multiple SSH keys for VMs)

 

Re: GSoC'21 - Clone a Virtual Machine

[Harikrishna Patnala]

Hi Junxuan Wu,

Welcome to the CloudStack community and congratulations on your project 
selection.

Have a great time learning and working on the project and CloudStack.

Regards,
Harikrishna

From: s Tms 
Sent: Tuesday, May 18, 2021 1:48 AM
To: dev@cloudstack.apache.org 
Subject: GSoC'21 - Clone a Virtual Machine

Hi Everyone,

I'm Junxuan Wu, a third-year student from Toronto, Canada. I'm selected for
issue #10430  (Clone
a virtual VM with all the data disks) on GSOC 2021.

It's a pleasure to be selected for this opportunity. Thanks to my mentors,
Suresh, Nicolas, Rohit, and also everyone in the community for giving me
this chance. I'm looking forward to knowing more about the community and
doing contributions. Feel free to email me if you want to connect.

Thank you!

Junxuan Wu

 

Re: GSoC 2021 - Synchronization of network devices on newly added hosts for Persistent Networks

[Harikrishna Patnala]

Hi Sangwoo Bae,

Welcome to the CloudStack community and congratulations on your project 
selection.

Have a great time learning and working on the project and CloudStack.

Regards,
Harikrishna

From: Sangwoo Bae 
Sent: Tuesday, May 18, 2021 2:20 AM
To: dev@cloudstack.apache.org 
Subject: GSoC 2021 - Synchronization of network devices on newly added hosts 
for Persistent Networks

Hello Everyone,

My name is Sangwoo Bae, and I am a second-year computer science student
from Berlin, Germany.
I have been selected as a GSoC student to work on the issue #4814 <
https://github.com/apache/cloudstack/issues/4814>.

Thanks to the community and my mentor Pearl for this opportunity! I am
looking forward to learning and contributing to the cloudstack community.
Please feel free to email me.

Kind regards and stay safe!

Sangwoo Bae

 

Re: [VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness

[Harikrishna Patnala]

+1  from me.

Regards,
Harikrishna

From: Suresh Anaparti 
Sent: Friday, April 30, 2021 5:13 PM
To: dev@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: [VOTE] Renaming default git branch name from 'master' to 'main' and 
replace offensive words as appropriate for inclusiveness

Hi All,

Following the discussion thread on renaming default git branch name and 
inclusiveness [1], I would like to start a vote to gather consensus on the 
following plan:

1. Accept the following rename PRs (raised against 'master' branch) which 
renames git default branch to 'main' and replaces some offensive words, and 
Merge them post acceptance.
- cloudstack => PR: https://github.com/apache/cloudstack/pull/4922
- cloudstack-documentation => PR: 
https://github.com/apache/cloudstack-documentation/pull/155
- cloudstack-www => PR: https://github.com/apache/cloudstack-www/pull/83
- cloudstack-cloudmonkey => PR: 
https://github.com/apache/cloudstack-cloudmonkey/pull/76
- cloudstack-kubernetes-provider => PR: 
https://github.com/apache/cloudstack-kubernetes-provider/pull/29
- cloudstack-ec2stack => PR: 
https://github.com/apache/cloudstack-ec2stack/pull/2
- cloudstack-gcestack => PR: 
https://github.com/apache/cloudstack-gcestack/pull/3

2. Request ASF infra to disable pushes to 'master' branch.

3. Rename 'master' branch to 'main' [2][3], and Request ASF infra (open INFRA 
ticket) to make 'main' as the default branch [4], in GitHub repo settings for 
all the CloudStack repos. This will also re-target the current PRs against 
'master' branch to 'main'.

3a. The update on the central repo will be done as follows (only by a PMC or 
Infra member with access)
- Clone the repo (git clone https://github.com/apache/cloudstack.git)
- Sync local 'master' with the cloudstack repo (cd cloudstack && git 
checkout master && git fetch --all -p && git pull)
- Rename local 'master' branch to 'main' (git branch -m master main)
- Push renamed 'main' branch (git push -u origin main)
- Update Default Branch on GitHub [4]
- Delete 'master' branch (git push origin --delete master)
3b. After the central renaming has been done. New users can clone and directly 
checkout 'main' branch. Existing users can start using 'main' locally, using 
the below steps.
- Switch to master branch (git checkout master)
- Rename local 'master' branch to 'main' (git branch -m master main)
- Sync local 'main' with repo (git fetch)
- Remove the existing tracking connection with “origin/master” (git 
branch --unset-upstream)
- Create a new tracking connection with the new “origin/main” branch 
(git branch -u origin/main)
- All local branches should still point to the same commit as base 
revision. If there is a problem (git checkout  && git 
rebase main)

4. Update the integrated systems with CloudStack repos, mainly Travis CI and 
Jenkins configuration with 'main' branch. Check and update UI building, 
apidocs, systemvmtemplate builds; project website and docs (cwiki); and any 
other build/release jobs. Track them through the issue: 
https://github.com/apache/cloudstack/issues/4887.

5. Perform Health Checks (using a dummy PR), and ensure there are no issues 
with the build/release configuration. This PR needs to run full matrix of 
tests. Fix the issues noticed during the health checks.

6. Announce the default branch change to 'main' (and 'master' deprecation) on 
the mailing list.

The vote will be open until Fri 7th May 2021.

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)

[1] https://markmail.org/message/k767evgjnmzogyhf
[2] https://github.com/github/renaming
[3] 
https://docs.github.com/en/github/administering-a-repository/renaming-a-branch
[4] 
https://docs.github.com/en/github/administering-a-repository/changing-the-default-branch

Regards,
Suresh





 

Re: Reintroduction

[Harikrishna Patnala]

Welcome Wei, happy to have you close to our work.

Regards,
Harikrishna

From: Rohit Yadav 
Sent: Wednesday, May 5, 2021 7:59 PM
To: dev@cloudstack.apache.org 
Subject: Re: Reintroduction

Welcome Wei! Happy to have a community colleague working as a $dayjob work 
colleague now 

Regards.

Regards,
Rohit Yadav


From: Simon Weller 
Sent: Wednesday, May 5, 2021 6:58:38 PM
To: dev@cloudstack.apache.org 
Subject: Re: Reintroduction

Great news...congrats Wei!


From: Wei ZHOU 
Sent: Wednesday, May 5, 2021 7:29 AM
To: dev@cloudstack.apache.org 
Subject: Reintroduction

Hi all,

I would like to reintroduce myself. I am Wei Zhou (github account:
weizhouapache). I joined the community in 2012. I became a cloudstack
committer in 2013 and a PMC member in 2017.

I have recently joined Shapeblue as a Software Architect. I am looking
forward to learning more from you and contributing more to the community.

Kind regards,
Wei




 

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

[Harikrishna Patnala]

+1

I agree with Rohit on this.

Regards,
Harikrishna

From: Rohit Yadav 
Sent: Monday, April 19, 2021 5:07 PM
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org ; m...@renemoser.net 

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

Hi René,

>From the discussion thread on the terraform provider, you can see some 
>interest and commitment (https://markmail.org/message/xultlpdihdrrg4gq) and 
>quite recently Peter/Fraunhofer and I/ShapeBlue had a meeting with 
>Chris/Hashicorp to discuss and understand the handover/fork of the archived 
>provider repository that Hashicorp is unable to maintain it and we agreed on 
>the next steps; following which I started this voting thread.

I think from a project point of view when integrations are not being maintained 
by external projects, we should have a home within the Apache CloudStack 
community to keep them alive and it makes it easy for ACS contributors to work 
on it. There is nothing wrong with other providers/plugins being brought in by 
contributors if there is interest and demand in the community. We've done this 
before already, when the Kubernetes project removed providers from their 
codebase we created a new home for it within ACS project to be maintained and 
used by the ACS community: 
https://github.com/apache/cloudstack-kubernetes-provider

Can you reconsider your vote? Or, is that a -1 binding vote (i.e. a veto)? 
Thanks.


Regards.


From: Rene Moser 
Sent: Thursday, April 15, 2021 15:05
To: us...@cloudstack.apache.org 
Subject: Re: [VOTE] New life to Terraform Provider CloudStack with Apache 
CloudStack project

-1

First, I didn't see much commitment in actively supporting and
maintaining this integration.

Second, there are many integrations, is terraform the one to pick for
using cloudstack from the view of the ASF?
A "plugin" for a software developed outside of ASF? What about puppet,
ansible, chef? The imbalance of this view results to a -1 from me.

Regards
René

On 15.04.21 11:05, Rohit Yadav wrote:
> Hi All,
>
> Following the discussion thread on Terraform [1], I would like to start a 
> vote to gather consensus on the following actions:
>
>1.  Create a new "cloudstack-terraform-provider" repository based on 
> Apache Licence v2.0 using re-licensed codebase of the archived/former 
> terraform cloudstack provider repository: 
> https://github.com/hashicorp/terraform-provider-cloudstack (note: 
> re-licensing from MPL to AL will be done by Hashicorp)
>2.  Request ASF infra to enable issues, PR, and wiki features on the 
> repository
>3.  Work with the community towards any further maintenance, development, 
> and releases of the provider
>4.  Publish official releases on the official registry [2] if/after Apache 
> CloudStack project gets a verified account (published by PMC members with 
> access to the registry, or following guidelines from ASF infra if they've any)
>
> The vote will be open for 120 hours, until Wed 21 April 2021.
> 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)
>
> [1] https://markmail.org/message/iuggxin7kj6ri4hb
> [2] https://registry.terraform.io/browse/providers
>
>
> 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




harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Re: [PROPOSAL] Force option and/or command to the detach ISO operation for running VMs

[Harikrishna Patnala]

Yes, it's better to keep an optional flag in the API params to decide on force 
detach of ISO instead of hardcoding force in the final detach operation. Thats 
gives flexibility to users and also keeps backward compatibility.

+1

Regards,
Harikrishna

From: Pearl d'Silva 
Sent: Friday, April 9, 2021 6:27 PM
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Subject: Re: [PROPOSAL] Force option and/or command to the detach ISO operation 
for running VMs

I've seen this issue happen on VMware.
+1 on having a force option to the attach/detach iso operations, thus giving 
control to the users as opposed to hard-coding the answer in the code.

Regards,
Pearl

From: Nicolas Vazquez 
Sent: Tuesday, March 30, 2021 4:06 AM
To: us...@cloudstack.apache.org 
Subject: Re: [PROPOSAL] Force option and/or command to the detach ISO operation 
for running VMs

Hi Alireza,

Yes - I have seen the same. In my tests that VM question was the one with ID 
'msg.cdromdisconnect.locked' to which CloudStack always answered "no" to that 
question and there was no option to control which answer to send.

I also noticed that the answering that question is only handled in the Vmware 
codebase, but not on other hypervisors codebase.


Regards,

Nicolas Vazquez


From: Alireza Eskandari 
Sent: Monday, March 29, 2021 3:40 PM
To: us...@cloudstack.apache.org 
Subject: Re: [PROPOSAL] Force option and/or command to the detach ISO operation 
for running VMs

Hi Nicolas
AFAIK in these situations ESXi will raise a question about detaching iso
from VM.
I have faced with similar problem in this issue:
https://github.com/apache/cloudstack/issues/4808
I got the same error in vCenter. Before waiting for timeout, if you click
on the refresh button in the top right corner of the web gui, you can see
an unanswered question is raised for the VM.
Regards

On Mon, Mar 29, 2021 at 7:34 PM Nicolas Vazquez <
nicolas.vazq...@shapeblue.com> wrote:

> Hi all,
>
> I have observed a non-consistent issue on the detach ISO operation for
> running VMs. Some guest OS refuse to release an attached ISO even though
> the ISO is not mounted, making the detach ISO operation fail if the VM is
> running. For example, a CentOS 7 running VM on Vmware 6.5 fails to detach
> an ISO with error: 'Connection control operation failed for disk 'ide0:0'
> if the VM is running'. However, there is no issue if the VM is stopped.
>
> As a workaround executing an 'eject' command on the guest VM before the
> detach operation solves the problem. The detach ISO operation in CloudStack
> could be extended to support a 'force' option - which could perform a
> similar workaround when the VM is running.
>
> I would be interested to know if you have experimented similar issues on
> different hypervisors or could be some hypervisor specific version issue.
>
>
> Regards,
>
> Nicolas Vazquez
>
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> @shapeblue
>
>
>
>

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




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




harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Re: Db schema upgrade fails from 4.14 to 4.16

[Harikrishna Patnala]

Hi Rakesh,

As Pearl mentioned I don't see any issue in upgrading from 4.14 to master. The 
specific error what you are getting is about the foreign key constraint being 
missed on that table.

Can you check on your 4.14 setup if "'fk_project_account__account_id'" foreign 
key is there are not on the table `cloud`.`project_account` before upgrade ?

This foreign key is there on that table since long time on CloudStack. Also 
please try with a different OS for management server just to see if that is 
causing any issue.

Thanks,
Harikrishna

From: Rakesh Venkatesh 
Sent: Friday, April 9, 2021 2:13 PM
To: dev 
Cc: users 
Subject: Re: Db schema upgrade fails from 4.14 to 4.16

Hello Pearl


No, this was the first time I tried to upgrade from 4.14 to master. 4.14
was running for quite long time.

I took db backup, registered 4.16 systemvm, changed global settings and
then just deployed new packages. It failed in the first attempt.
I was able to resolve this by dropping the project_account and
project_invitation table, creating them and restarted the mgt service. This
time it applied successfully


To double check it, I created a fresh 4.14 system, did the above steps and
the upgrade still failed.
So solution right now is to drop the tables, create it again and run the
upgrade

On Thu, Apr 8, 2021 at 6:52 PM Pearl d'Silva 
wrote:

> Hi Rakesh,
>
> Was there a prior attempt made to upgrade which didn't go through
> successfully? It seems like while it failed to upgrade, the DB changes were
> applied, hence resulting in the failure that is noticed. To address the
> issue, you will have to restore the DB, if you've taken a backup of it and
> redo the upgrade.
> However, to avoid such situations, an enhancement was added with
> https://github.com/apache/cloudstack/pull/4582 which prevents upgrading
> the DB in case of missing systemvm template.
>
> Thanks
> Pearl
>
> 
> From: Andrija Panic 
> Sent: Thursday, April 8, 2021 9:09 PM
> To: dev 
> Cc: users 
> Subject: Re: Db schema upgrade fails from 4.14 to 4.16
>
> 4.16 doesn't exist yet, and it's the master branch - so failures are
> expected...
>
> On Thu, 8 Apr 2021 at 16:42, Rakesh Venkatesh 
>  http://www.rakeshv@gmail.com>>
> wrote:
>
> > Hello users
> >
> >
> > Im trying to upgrade cloudstack from 4.14.0 to 4.16.0 and the upgrade is
> > failing because of the db schema upgrade. Any idea on how to fix this.
> >
> > This is the commit which is causing the issue
> > https://github.com/apache/cloudstack/pull/4128
> >
> >
> >
> > 2021-04-08 13:59:26,983 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > -- Schema upgrade from 4.14.0.0 to 4.15.0.0
> >
> > 2021-04-08 13:59:27,002 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > Error executing: ALTER TABLE `cloud`.`project_account`  ADD COLUMN
> > `user_id` bigint unsigned COMMENT 'ID of user to be added to the project'
> > AFTER `account_id`,  ADD CONSTRAINT `fk_project_account__user_id` FOREIGN
> > KEY `fk_project_account__user_id`(`user_id`) REFERENCES `user`(`id`) ON
> > DELETE CASCADE,  ADD COLUMN `project_role_id` bigint unsigned COMMENT
> > 'Project role id' AFTER `project_account_id`,  ADD CONSTRAINT
> > `fk_project_account__project_role_id` FOREIGN KEY (`project_role_id`)
> > REFERENCES `project_role` (`id`) ON DELETE SET NULL,  DROP FOREIGN KEY
> > `fk_project_account__account_id`,  DROP INDEX `account_id`
> > 2021-04-08 13:59:27,003 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:)
> > java.sql.SQLSyntaxErrorException: Can't DROP
> > 'fk_project_account__account_id'; check that column/key exists
> > 2021-04-08 13:59:27,004 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null)
> > (logid:) Unable to execute upgrade script
> > java.sql.SQLSyntaxErrorException: Can't DROP
> > 'fk_project_account__account_id'; check that column/key exists
> > at com.cloud.utils.db.ScriptRunner.runScript(ScriptRunner.java:185)
> >
> >
> > Caused by: java.sql.SQLSyntaxErrorException: Can't DROP
> > 'fk_project_account__account_id'; check that column/key exists
> > --
> > Thanks and regards
> > Rakesh
> >
>
>
> --
>
> Andrija Panić
>
> pearl.dsi...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> @shapeblue
>
>
>
>

--
Thanks and regards
Rakesh venkatesh

harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Re: [DISCUSS] Marvin tests interaction

[Harikrishna Patnala]

Hi Nicolas,

+1, I think this is a great add to link marvin tests with UI, definitely helps 
developers to quickly run and check the results.

Regards,
Harikrishna

From: Nicolas Vazquez 
Sent: Monday, March 29, 2021 8:20 AM
To: dev@cloudstack.apache.org 
Subject: [DISCUSS] Marvin tests interaction

Hi,

I would like to propose an idea to improve the interaction with the marvin 
tests through the management server. This could be useful for development and 
test environments in which tests could be easily started, configured and their 
results monitored through the UI.

This could be achieved by creating a new service in charge of the execution of 
the tests and sending results back to the management server, so it can display 
them. A more detailed description: 
https://github.com/apache/cloudstack/issues/4799

I would like to hear your thoughts and ideas about it. Would you find this 
useful?


Regards,

Nicolas Vazquez

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




harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Re: Congratulations to Sven - Apache Software Foundation Member

[Harikrishna Patnala]

Congratulations Sven

Best regards,
Harikrishna

From: Pearl d'Silva 
Sent: Thursday, March 18, 2021 5:13 PM
To: us...@cloudstack.apache.org 
Cc: dev@cloudstack.apache.org 
Subject: Re: Congratulations to Sven - Apache Software Foundation Member

Congratulations Sven!

Regards,
Pearl

From: Nicolas Vazquez 
Sent: Thursday, March 18, 2021 5:04 PM
To: us...@cloudstack.apache.org 
Cc: dev@cloudstack.apache.org 
Subject: Re: Congratulations to Sven - Apache Software Foundation Member

Congratulations Sven!


Regards,

Nicolas Vazquez


From: Slavka Peleva 
Sent: Thursday, March 18, 2021 8:08 AM
To: us...@cloudstack.apache.org 
Cc: dev@cloudstack.apache.org 
Subject: Re: Congratulations to Sven - Apache Software Foundation Member

Congratulations, Sven! Wishing you success with the new role!

On Thu, Mar 18, 2021 at 11:49 AM David Jumani 
wrote:

> Congratulations Sven!
> 
> From: Paul Angus 
> Sent: Thursday, March 18, 2021 2:43 AM
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org 
> Subject: Congratulations to Sven - Apache Software Foundation Member
>
> Hi All,
>
>
>
> More great news.
>
>
>
> Please join me in congratulating Sven,  for being made a Member of the
> Apache Software Foundation.
>
>
>
> Congratulations Sven, keep up the good work!
>
>
>
> Kind regards
>
>
>
> Paul Angus
>
>
>
>
> david.jum...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> @shapeblue
>
>
>
>

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




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




harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Re: Congratulations to Gabriel - CloudStack PMC Chair

[Harikrishna Patnala]

Congratulations Gabriel

Best regards,
Harikrishna

From: Paul Angus 
Sent: Thursday, March 18, 2021 2:40 AM
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Cc: priv...@cloudstack.apache.org 
Subject: Congratulations to Gabriel - CloudStack PMC Chair

Hi All CloudStack enthusiasts!



Please join me in congratulating Gabriel for becoming the next CloudStack
PMC Chair.

Congratulations Gabriel, very well deserved!



I would also like to thank Sven for his great work of the past year!







Kind regards



Paul Angus




harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Re: Goggle Summer of Code 2021

[Harikrishna Patnala]

Hi guys,

I've an idea around mapping existing configuration parameters to the APIs when 
they are used during some operation, instead of looking for configuration 
parameters using string search or documentation. This helps in debugging or 
tuning the API operation easily w.r.t. configuration parameters.
I've created a ticket here https://github.com/apache/cloudstack/issues/4825.
[https://avatars.githubusercontent.com/u/47359?s=400=4]
GSoC 2021 Idea: Configuration parameters and APIs mappings · Issue #4825 · 
apache/cloudstack
Background There are around ~672 configuration parameters in CloudStack which 
is a huge list and the way admins got used to look for configuration parameters 
is either by string search or documenta...
github.com
I'm happy to be a mentor for this improvement. Please let me know your feedback.

Thanks,
Harikrishna

From: Giles Sirett 
Sent: Tuesday, February 16, 2021 2:59 PM
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: Goggle Summer of Code 2021

Hi all

It would be great if the CloudStack project were able to get a few Google 
Summer of Code  [1] students this year to work on projects within our 
community. We've had a number of previous GSoC students (examples at [2] ), who 
have worked on innovative features/ projects within cloudstack and have then 
gone on to become significant contributors to Cloudstack .


In order to be able to attract students to work on Cloudstack, we need 2 things:

  1.  A number of candidate projects for students to work on. Students browse 
all GSoC the candidate projects and choose one that interests them- effectively 
every organisation is competing for the students interest.  These projects 
therefore need to be reasonably interesting looking projects to attract 
potential students. The students spend approximately 9 weeks coding, so the 
projects need to be appropriately scaled
  2.  Somebody prepared to mentor the student throughout the duration of the 
project (usually the person who suggests the project)

The student application period starts 29 March [3]
The ASF  has registered itself as a mentor  organisation with Google , allowing 
individual Apache projects to list candidate projects  for students to work on. 
A wiki page [4]  has been created at the ASF level to allow ASF projects to  
list their ideas for students


I'm happy to coordinate this from a Cloudstack perspective.
If others are happy with this approach, then I ask for two things at this stage:


  1.  Could people suggest appropriate projects. This could be a piece of 
integration that you've always considered and not got around to or could be an 
improvement that you've always wanted to do. If people can reply to this thread 
with ANY ideas, it would be a good start (irrespective of whether you wish to 
be a mentor or not)
  2.  At the same time, could people say whether they'd be prepared to be a 
student mentor or not




[1] https://summerofcode.withgoogle.com/


[2]
https://blog.netapp.com/blogs/mentoring-with-google-summer-of-code-and-lessons-in-cloudstack/
https://dzone.com/articles/cloudstack-google-summer-code
https://opensource.googleblog.com/2014/07/gsoc-students-create-google-compute.html


[3]https://summerofcode.withgoogle.com/how-it-works/#timeline

[4] https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2021+Ideas+list



Kind regards
Giles


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




harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Re: [ANNOUNCE] new committer: Suresh Anaparti

[Harikrishna Patnala]

Congratulations Suresh 

From: Sven Vogel 
Sent: Wednesday, November 18, 2020 4:17 AM
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Cc: Suresh Anaparti 
Subject: [ANNOUNCE] new committer: Suresh Anaparti

Hi everyone,


 The Project Management Committee (PMC) for Apache CloudStack
has invited Suresh Anaparti to become a committer and we are pleased
to announce that he has accepted.

Please join me in congratulating Suresh on this accomplishment.


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.


Thanks and Cheers,



Sven Vogel
Apache CloudStack PMC member

harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Re: [ANNOUNCE] new committer: Abhishek Kumar

[Harikrishna Patnala]

Congratulations Abhishek 

From: Sven Vogel 
Sent: Wednesday, November 18, 2020 4:18 AM
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Cc: Abhishek Kumar 
Subject: [ANNOUNCE] new committer: Abhishek Kumar

Hi everyone,


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

Please join me in congratulating Abhishek on this accomplishment.


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.




Thanks and Cheers,



Sven Vogel
Apache CloudStack PMC member

harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Re: [ANNOUNCE] new committer: Nguyen Mai Hoang

[Harikrishna Patnala]

Congratulations Nguyen !

From: Sven Vogel 
Sent: Wednesday, November 18, 2020 4:18 AM
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Cc: hoang.ngu...@ewerk.com 
Subject: [ANNOUNCE] new committer: Nguyen Mai Hoang

Hi everyone,



 The Project Management Committee (PMC) for Apache CloudStack
has invited Nguyen Mai Hoang to become a committer and we are pleased
to announce that he has accepted.

Please join me in congratulating Hoang on this accomplishment.


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.


Thanks and Cheers,



Sven Vogel
Apache CloudStack PMC member

harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Re: [ANNOUNCE] new committer: Rakesh Venkatesh

[Harikrishna Patnala]

Congrats Rakesh 

From: Sven Vogel 
Sent: Wednesday, November 18, 2020 4:18 AM
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Cc: r.venkat...@global.leaseweb.com 
Subject: [ANNOUNCE] new committer: Rakesh Venkatesh

Hi everyone,



 The Project Management Committee (PMC) for Apache CloudStack
has invited Rakesh Venkatesh to become a committer and we are pleased

to announce that he has accepted.

Please join me in congratulating Rakesh on this accomplishment.


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.


Thanks and Cheers,



Sven Vogel
Apache CloudStack PMC member

harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

Introduction

[Harikrishna Patnala]

Hi guys,

This is Harikrishna and ’ve recently joined Shapeblue.
It is happy to rejoin our community again. Looking forward to work with you 
guys and contribute to the community.

Best regards,
Harikrishna Patnala
harikrishna.patn...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com%3chttp:/www.shapeblue.com>
Amadeus House, Floral Street, London  WC2E 9DPUK


harikrishna.patn...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SG
@shapeblue
  
 

[GitHub] cloudstack issue #2006: CLOUDSTACK-9833: Move configuration parameters from ...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the issue:

https://github.com/apache/cloudstack/pull/2006
  
Thanks @jayapalu I have also added some content security policy in HTTP 
servlet response to detect and mitigate certain type of attacks.
Restricted image source, style sheets, java scripts, URLs to be loaded only 
from self.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #2042: CLOUDSTACK-9875: Unable to re-apply Explicit ...

[harikrishna-patnala]

GitHub user harikrishna-patnala opened a pull request:

https://github.com/apache/cloudstack/pull/2042

CLOUDSTACK-9875: Unable to re-apply Explicit dedication to VM

Problem:
When a VM is deployed with in an Affinity group which has the cluster 
dedicated to a subdomain (zone is dedicated to parent domain) it is getting 
successful. We can also stop the vm and remove the affinity group, but if you 
want to add back the affinity it is failing.

Following are the steps to reproduce

1. I had created a Domain (Glass SA Parent Domain) and under it a subdomain 
(Glass SA Subdomain) and created an account to it.
2. Apply dedication to the zone for primary domain (Glass SA Parent Domain)
3. Apply dedication to the cluster for sub domain (Glass SA Subdomain)
4. Logged in with the Account of Subdomain.
5. Created an instance with the affinity (DedicatedGrp-domain-Glass SA 
Subdomain) - the dedication set with the cluster for the subdomain.
6. Powered off the VM, removed the affinity.
7. Tried adding back (the cluster affinity subdomain) - gives the error 
"Entity affinity Group () and entity Acct () belong to different accounts" 

Root cause:
During VM deployment there is clear check on affinity type 
(account/domain). Here since the acl_type is "domain" it does not expect to be 
same owner for entities.
But during update of affinity to VM there is no specific check for acl_type 
"domain".

Solution:
Fix is to make the access check similar to VM deployment where it does not 
expect to be same owner for entities if the acl_type is "domain".

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9875

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/2042.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2042


commit 4f6e5daa580aa5b456e946783cb08cabc4b9c6bc
Author: Harikrishna Patnala <harikrishna.patn...@citrix.com>
Date:   2015-11-18T12:03:49Z

CLOUDSTACK-9875: Unable to re-apply Explicit dedication to VM

Problem:
When a VM is deployed with in an Affinity group which has the cluster 
dedicated to a subdomain (zone is dedicated to parent domain) it is getting 
successful. We can also stop the vm and remove the affinity group, but if you 
want to add back the affinity it is failing.

Root cause:
During VM deployment there is clear check on affinity type 
(account/domain). Here since the acl_type is "domain" it does not expect to be 
same owner for entities.
But during update of affinity to VM there is no specific check for acl_type 
"domain".

Solution:
Fix is to make the access check similar to VM deployment where it does not 
expect to be same owner for entities if the acl_type is "domain".




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #874: CLOUDSTACK-8897: baremetal:addHost:make host tag info...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the issue:

https://github.com/apache/cloudstack/pull/874
  
tag:mergeready


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #2016: CLOUDSTACK-9835 : To make management server a...

[harikrishna-patnala]

GitHub user harikrishna-patnala opened a pull request:

https://github.com/apache/cloudstack/pull/2016

CLOUDSTACK-9835 : To make management server and SSVM to be in time sync

Added a new configuration paremetar "ntp.server.list" to configure NTP 
server ip in NTP settings of SSVM

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9835

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/2016.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2016


commit dd312d6b479062a711b67dba0e9a614e9e64c608
Author: Harikrishna Patnala <harikrishna.patn...@accelerite.com>
Date:   2017-03-15T06:23:30Z

CLOUDSTACK-9835 : Management server and SSVM should be in time sync

Added a new configuration paremetar "ntp.server.list" to configure NTP 
server ip in NTP settings of SSVM




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1180: CLOUDSTACK-9112: Deploy VM failing frequently due to...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the issue:

https://github.com/apache/cloudstack/pull/1180
  
Added test for the case where we need to list only clusters which has hosts 
with host tag specified in the offering.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #2006: CLOUDSTACK-9833: Move configuration parameter...

[harikrishna-patnala]

GitHub user harikrishna-patnala opened a pull request:

https://github.com/apache/cloudstack/pull/2006

CLOUDSTACK-9833: Move configuration parameters from Config.java to use 
configdepot

Following parameters are moved from config.java to configdepot.
This will make the management of configuration parameter easy during 
upgrade and avoid inconsistency of values of parameters for fresh setup and 
upgraded setup.

snapshot.max.hourly
snapshot.max.daily
snapshot.max.weekly
snapshot.max.monthly
enable.secure.session.cookie
json.content.type

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9833

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/2006.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2006


commit abea001c881e95c7922767aa5f476ab9135b4939
Author: Harikrishna Patnala <harikrishna.patn...@accelerite.com>
Date:   2017-03-14T09:23:11Z

CLOUDSTACK-9833: Move configuration parameters from Config.java to use 
ConfigDepot
Following parameters are moved to configdepot.
snapshot.max.hourly
snapshot.max.daily
snapshot.max.weekly
snapshot.max.monthly
enable.secure.session.cookie
json.content.type




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #874: CLOUDSTACK-8897: baremetal:addHost:make host tag info...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the issue:

https://github.com/apache/cloudstack/pull/874
  
The are 2 failed test cases which are failing on all other PRs



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1880: CLOUDSTACK-9720: [VMware] template_spool_ref table i...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the issue:

https://github.com/apache/cloudstack/pull/1880
  
LGTM for the code changes.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1990: CLOUDSTACK-9674: Baremetal deployment improve...

[harikrishna-patnala]

GitHub user harikrishna-patnala opened a pull request:

https://github.com/apache/cloudstack/pull/1990

CLOUDSTACK-9674: Baremetal deployment improvements

With the current implementation of baremetal with cloudstack works but 
there are lot of improvements and bug fixes to be done.

1) Improvements in the baremetal planner.
2) Currently baremetal deployement supports only single nic on the 
baremetal host. Need to add multiple isolated network support in advanced zone.
3) There is a dependency on VMWare hypervisor to host the Virtual router. 
This has to be removed and make the VR deployment hypervisor agnostic.
4) To be able to handle baremetal deployments in case of RVR.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9674

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1990.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1990


commit 601b0671d81e1842da49601947d08cdb3a4c134e
Author: Harikrishna Patnala <harikrishna.patn...@accelerite.com>
Date:   2017-03-06T07:03:30Z

CLOUDSTACK-9674: Baremetal deployment improvements

With the current implementation of baremetal with cloudstack works but 
there are lot of improvements and bug fixes to be done.

1) Improvements in the baremetal planner.
2) Currently baremetal deployement supports only single nic on the 
baremetal host. Need to add multiple isolated network support in advanced zone.
3) There is a dependency on VMWare hypervisor to host the Virtual router. 
This has to be removed and make the VR deployment hypervisor agnostic.
4) To be able to handle baremetal deployments in case of RVR.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1861: CLOUDSTACK-9698 [VMware] Make hardcorded wait timeou...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the issue:

https://github.com/apache/cloudstack/pull/1861
  
LGTM.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1759: CLOUDSTACK-9589 vmName entries from host_details tab...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the issue:

https://github.com/apache/cloudstack/pull/1759
  
LGTM



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #874: CLOUDSTACK-8897: baremetal:addHost:make host tag info...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the issue:

https://github.com/apache/cloudstack/pull/874
  
I have updated the PR based on the comments. Please review.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [QUESTION] baremetal router

[Harikrishna Patnala]

Hi Daan,

Yes, this should run only in Virtual Router. Instead of moving it to existing 
“if” block, better to have a seperate check only for normal router, since we 
don’t support baremetal deployment in VPC.

Regarding the later question, with the current implementation I don’t think we 
can distinguish whether PXE service enabled on the router or not, or we can 
also initiate this agent on VR from management server using sshCmdHelper just 
before deploying the baremetal instance.

Regards,
Harikrishna


On 30-Mar-2016, at 5:26 pm, Daan Hoogland  wrote:

> People,
>
> in the following code the baremetal-vr.py configuration script is started
> unconditionally, this means it will be started on ssvm and cpvm as well.
> but also on virtual routervms;
>
>
> CMDLINE=$(cat /var/cache/cloud/cmdline)
> router=$(echo "$CMDLINE" | grep -o  type=router)
> vpcrouter=$(echo "$CMDLINE" | grep -o  type=vpcrouter)
>
> if [ "$router" != "" ] ||  [ "$vpcrouter" != "" ]
> then
>   echo 100 > /proc/sys/net/ipv4/netfilter/ip_conntrack_max
>   echo 100 > /proc/sys/net/netfilter/nf_conntrack_max
>   echo 100 > /proc/sys/net/nf_conntrack_max
> fi
>
> python /opt/cloud/bin/baremetal-vr.py &
>
>
> Does it make sense to at least move it inside the if block above so it is
> only started on routers?
> Or does anybody know how to distinguish that we are running on baremetal
> and guard for that condition?
>
> --
> Daan




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

Re: [DISCUSS] Request for comments: Out-of-band Management for CloudStack (new feature)

[Harikrishna Patnala]

Hi Rohit,

Thanks for the proposal and seems like a descent feature to have.

I have a little concern here regarding the baremetal deployment where we use 
ipmi as power management interface. Are you going to use the existing ipmi util 
we have or do you have a separate solution for this. If it is the latter case 
then you may need to consolidate everything to have one solution to avoid 
redundancy.

Regards,
Harikrishna


On 07-Mar-2016, at 2:51 pm, Rohit Yadav  wrote:

> Hi Ilya,
>
> Thanks for the suggestions.
>
> In the UI, we can easily have a warning statement on the pop up box if host 
> maintenance is enabled. We can also add mechanisms (for example specific APIs 
> or zone/cluster level settings) to allow admins to disable/enable the feature 
> at zone and cluster level without cascading it to the host enabled setting. 
> Will update the FS to reflect these additions.
>
> Regards.
>
>> On 05-Mar-2016, at 7:11 AM, ilya  wrote:
>>
>> Rohit,
>>
>> Great job!
>>
>> Not certain if this was mentioned, but premise behind IPMI integration
>> was partially driven by HA and being able to "fence" the host in
>> question to avoid split brain scenario - as well as other issues when
>> hypervisors malfunction.
>>
>> With that said, Will brings up a good point, what can we offer to avoid
>> accidental power down - while host is functional. I see plenty of
>> curious cloudstack admins who identify a function of a button by
>> pressing on it and saying "lets see what happens". Better yet, some
>> learn on the job on production environments.
>>
>> Do we give the end user a warning of any kind? If possible, i would
>> suggest we give a one line warning - something like "The host is not in
>> Maintenance Mode, proceed at your own risk!" or something to that effect.
>>
>> Obviously this would only be CloudStack UI safeguard and no such warning
>> would be shown when you use APIs directly.
>>
>> Lastly, please consider disable IPMI for Cluster and Zone level, i dont
>> believe we need it for pod. Please dont cascade over every host ipmi
>> object and change their state, instead, have a separate db entry (or
>> else) that tracks this selection for cluster or zone.
>>
>> It could be as simple as configuration setting for zone or cluster.
>>
>> thanks
>> ilya
>>
>>
>> On 3/4/16 1:20 AM, Rohit Yadav wrote:
>>>
>>>
>>> ShapeBlue 
>>> Rohit Yadav
>>> Software Architect   ,   ShapeBlue
>>>
>>> d:   * | s: +44 203 603 0540* 
>>> |m:  *+91 8826230892* 
>>>
>>> e:   *rohit.ya...@shapeblue.com | t: *
>>>    |  w:
>>> *www.shapeblue.com* 
>>>
>>> a:   53 Chandos Place, Covent Garden London WC2N 4HS UK
>>>
>>> Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
>>> Services India LLP is a company incorporated in India and is operated
>>> under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is
>>> a company incorporated in Brasil and is operated under license from
>>> Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The
>>> Republic of South Africa and is traded under license from Shape Blue
>>> Ltd. ShapeBlue is a registered trademark.
>>> This email and any attachments to it may be confidential and are
>>> intended solely for the use of the individual to whom it is addressed.
>>> Any views or opinions expressed are solely those of the author and do
>>> not necessarily represent those of Shape Blue Ltd or related companies.
>>> If you are not the intended recipient of this email, you must neither
>>> take any action based upon its contents, nor copy or show it to anyone.
>>> Please contact the sender if you believe you have received this email in
>>> error.
>>>
>>>
 On 03-Mar-2016, at 12:58 PM, Will Stevens > wrote:

 Maybe I am not understanding something here.

 Does this control the power cycle of the management server(s) or the
 hypervisor hosts?  The wording is throwing me off.
>>>
>>> Fixed. The feature applies for hypervisor hosts only, not management
>>> server hosts (unless of course, mgmt server host is hypervisor host as
>>> well for example running mgmt server + kvm agnet on a KVM host).
>>>
 I am guessing it is for managing the hypervisor hosts. If this is the
 case,
 does it also handle the "maintenance mode" for the host as well?
>>>
>>> Maintenance mode is a hypervisor semantic, this is not related to the
>>> out-of-band management interface (the BMC, such as iLO, iDRAC) available
>>> on the hypervisor host.
>>>
>>> Even when you enable/disable maintenance mode, you can use a tool like
>>> ‘ipmitool’ to do execute a power management operation such as
>>> on/off/reset etc, so you should be able to perform the same using this
>>> feature. 

Re: Unable Creare/CleanUp Virual Router After upgraded to ACS 4.6.2

[Harikrishna Patnala]

Hi,

Latest system vm template has flask installed in it. Can you please let us 
which system vm template you have used.

Thanks,
Harikrishna


On 27-Jan-2016, at 4:17 pm, mvs babu  wrote:

> Sorry, it is not allowing to attach a screenshot. Please find below link.
> 
> 
> http://picpaste.com/pics/VPC-rhH48Qao.1453891619.PNG
> 
> 
> 
> 
> 
> 
> Thank you,
> Suneel Mallela
> 
> 
> 
> 
> 
> From: mvs babu
> Sent: ‎Wednesday‎, ‎January‎ ‎27‎, ‎2016 ‎4‎:‎14‎ ‎PM
> To: us...@cloudstack.apache.org
> Cc: dev@cloudstack.apache.org
> 
> 
> 
> 
> 
> Please find attachment.
> 
> 
> 
> 
> 
> 
> Thank you,
> Suneel Mallela
> 
> 
> 
> 
> 
> From: mvs babu
> Sent: ‎Wednesday‎, ‎January‎ ‎27‎, ‎2016 ‎4‎:‎08‎ ‎PM
> To: us...@cloudstack.apache.org
> Cc: dev@cloudstack.apache.org
> 
> 
> 
> 
> 
> Hi All,
> 
> We upgraded ACS from 4.3.1 to 4.6.2. After this we tried to create new 
> VPC/Network and getting below error from Virtual Router then after router get 
> shutdown.
> 
> 
> 
> 
> We are using XenServer 6.2 and CentOS 6.3.
> 
> Please help us to fix this issue.
> 
> 
> Thank you,
> Suneel Mallela,
> 
> AxiomIO.

[GitHub] cloudstack pull request: CLOUDSTACK-9112: Deploy VM failing freque...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the pull request:

https://github.com/apache/cloudstack/pull/1180#issuecomment-163112385
  
Thank you for the feedback, I'll add the unit tests for the new methods and 
integration tests for the changes that I have made.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: Deploy VM failing frequently due to capac...

[harikrishna-patnala]

GitHub user harikrishna-patnala opened a pull request:

https://github.com/apache/cloudstack/pull/1180

Deploy VM failing frequently due to capacity calculation not synchron…



There are some VM deployment failures happening when multiple VMs are 
deployed at a time, failures mainly due to NetworkModel code that iterates over 
all the vlans in the pod. This causes each deployVM thread to hold the global 
lock on Network longer and cause delays. This delay in turn causes more threads 
to choose same host and fail since capacity is not available on that host.

Following are some changes required to be done to reduce delays during VM 
deployments which in turn causes some vm deployment failures when multiple VMs 
are launched at a time.

  -  In Planner, remove the clusters that do not contain a host with 
matching service offering tag. This will save some iterations over clusters 
that dont have matching tagged host
  -  In NetworkModel, do not query the vlans for the pod within the loop. 
Also optimized the logic to query the ip/ipv6
  -  In DeploymentPlanningManagerImpl, do not process the affinity group if 
the plan has hostId provided.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/harikrishna-patnala/cloudstack CLOUDSTACK-9112

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1180.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1180


commit 8394e1940535b05525bebebdb8fcc73fcaefc709
Author: Harikrishna Patnala <harikrishna.patn...@citrix.com>
Date:   2015-12-04T09:57:53Z

Deploy VM failing frequently due to capacity calculation not synchronized

Changes:
- In Planner, remove the clusters that do not contain a host with matching 
service offering tag. This will save some iterations over clusters that dont 
have matching tagged host
- In NetworkModel, do not query the vlans for the pod within the loop. Also 
optimized the logic to query the ip/ipv6
- In DeploymentPlanningManagerImpl, do not process the affinity group if 
the plan has hostId provided.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: Changes made to DeployDataCenter to suppo...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the pull request:

https://github.com/apache/cloudstack/pull/809#issuecomment-161954435
  
I have not tested but did a code walk through. LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-9092: L10n fix in "Add LDAP Ac...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the pull request:

https://github.com/apache/cloudstack/pull/1139#issuecomment-160531359
  
Looks good to me


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-9094: Multiple threads are bei...

[harikrishna-patnala]

GitHub user harikrishna-patnala opened a pull request:

https://github.com/apache/cloudstack/pull/1140

CLOUDSTACK-9094: Multiple threads are being used to collect the stats…

CLOUDSTACK-9094: Multiple threads are being used to collect the stats from 
the same VR

Same thread is being intialised by two managers, 
VirtualNetworkApplianceManager and VpcVirtualNetworkApplianceManager

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/harikrishna-patnala/cloudstack CLOUDSTACK-9094

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1140.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1140


commit c9cc2ccd6dd69bc267ded6e654ec7167a330b6df
Author: Harikrishna Patnala <harikrishna.patn...@citrix.com>
Date:   2015-11-30T06:44:15Z

CLOUDSTACK-9094: Multiple threads are being used to collect the stats from 
the same VR

Same thread is being intialised by two managers, 
VirtualNetworkApplianceManager and VpcVirtualNetworkApplianceManager




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: Changes made to DeployDataCenter to suppo...

[harikrishna-patnala]

Github user harikrishna-patnala commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/809#discussion_r40658808
  
--- Diff: test/integration/smoke/test_baremetal.py ---
@@ -0,0 +1,155 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+""" Test for baremetal
+"""
+#Import Local Modules
+from marvin.cloudstackTestCase import cloudstackTestCase
+from marvin.lib.utils import cleanup_resources, validateList
+from marvin.lib.base import (Template,
+ Host,
+ ServiceOffering,
+ Account,
+ VirtualMachine)
+from marvin.lib.common import get_domain, get_zone
+from marvin.codes import PASS, HOSTTAG1
+from nose.plugins.attrib import attr
+
+#Import System modules
+_multiprocess_shared_ = True
+
+class TestBaremetal(cloudstackTestCase):
+
+@classmethod
+def setUpClass(cls):
+testClient = super(TestBaremetal, cls).getClsTestClient()
+cls.apiclient = testClient.getApiClient()
+cls.services = testClient.getParsedTestDataConfig()
+# Get Zone, Domain
+cls.domain = get_domain(cls.apiclient)
+cls.zone = get_zone(cls.apiclient, testClient.getZoneForTests())
+cls.services['mode'] = cls.zone.networktype
+cls.hypervisor = cls.testClient.getHypervisorInfo()
+cls.account = Account.create(
+cls.apiclient,
+cls.services["account"],
+domainid=cls.domain.id
+)
+#Register baremetal template
+cls.template = Template.register(
+cls.apiclient,
+cls.services["baremetal_template"],
+zoneid=cls.zone.id,
+account=cls.account.name,
+domainid=cls.account.domainid,
+)
+cls.debug(
+"Registered a template of format: %s with ID: %s" % (
+cls.services["baremetal_template"]["format"], 
cls.template.id
+)
+)
+#Update host with host tag
+cls.hosts = Host.list(
+cls.apiclient,
+zoneid=cls.zone.id,
+hypervisor=cls.hypervisor
+)
+if not validateList(cls.hosts)[0]:
+assert False, "Invalid response for list host"
+host_res = Host.update(
--- End diff --

I have checked this scenario, vm deployment is getting succeeded but we 
need to fix the baremetal planner a bit. So here no need to change anything. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8897: baremetal:addHost:make h...

[harikrishna-patnala]

GitHub user harikrishna-patnala opened a pull request:

https://github.com/apache/cloudstack/pull/874

CLOUDSTACK-8897: baremetal:addHost:make host tag info mandtory in bar…

CLOUDSTACK-8897: baremetal:addHost:make host tag info mandtory in baremetal 
addhost Api call

addhost api is successful with out providing the host tag info and we 
recommend host tag is mandatory for bare-metal.
In the current implementation host tag check is happening at vm deployment 
stage but it will be good to have host tag field as mandatory field during 
adding of the host 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/harikrishna-patnala/cloudstack CLOUDSTACK-8897

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/874.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #874


commit 88f023cee3f2a52c3d1f6452cac84aa03477a2f1
Author: Harikrishna Patnala <harikrishna.patn...@citrix.com>
Date:   2015-09-22T11:41:16Z

CLOUDSTACK-8897: baremetal:addHost:make host tag info mandtory in baremetal 
addhost Api call

addhost api is successful with out providing the host tag info and we 
recommend host tag is mandatory for bare-metal.
In the current implementation host tag check is happening at vm deployment 
stage but it will be good to have host tag field as mandatory field during 
adding of the host it self.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8888: Xenserver 6.0.2 host stu...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the pull request:

https://github.com/apache/cloudstack/pull/861#issuecomment-142174711
  
Thanks Koushik, here is the commit which removed the class 
XenServer602Resource.

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=81c5e184ba998a6ccd75dfffad32cbe5dbc8c2ec


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8888: Xenserver 6.0.2 host stu...

[harikrishna-patnala]

GitHub user harikrishna-patnala opened a pull request:

https://github.com/apache/cloudstack/pull/861

CLOUDSTACK-: Xenserver 6.0.2 host stuck in disconnected state aft…

Xenserver 6.0.2 hosts are stuck in disconnected state after CS upgrade to 
4.6. This is because xenserver602resource class is not there in 4.6 branch and 
existing hosts running on v6.0.2 are not handled properly.  


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/harikrishna-patnala/cloudstack CLOUDSTACK-

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/861.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #861


commit 61c85fe2dca09b0189b7a9dae7a29d8692dcca0c
Author: Harikrishna Patnala <harikrishna.patn...@citrix.com>
Date:   2015-09-21T10:17:15Z

CLOUDSTACK-: Xenserver 6.0.2 host stuck in disconnected state after 
upgrade to 4.6

XenServer602Resource class is removed but existing xenserver 6.0.2 hosts 
are not handled properly.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: changed the systemvm base iso file from d...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the pull request:

https://github.com/apache/cloudstack/pull/833#issuecomment-140624768
  
LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: Tagging tests appropriately to pick them ...

[harikrishna-patnala]

Github user harikrishna-patnala commented on the pull request:

https://github.com/apache/cloudstack/pull/819#issuecomment-140046870
  
LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: Changes made to DeployDataCenter to suppo...

[harikrishna-patnala]

Github user harikrishna-patnala commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/809#discussion_r39363075
  
--- Diff: tools/marvin/marvin/config/BareMetal.cfg ---
@@ -0,0 +1,194 @@
+{
+"zones": [
+{
+"name": "Basic",
+"dns1": "10.140.50.6",
+"physical_networks": [
+{
+"broadcastdomainrange": "Pod",
+"name": "Baremetal-pnet",
+"traffictypes": [
+{
+"typ": "Guest"
+},
+{
+"typ": "Management"
+}
+],
+"isolationmethods": [
+"L3"
+],
+"providers": [
+{
+"broadcastdomainrange": "ZONE",
+"name": "VirtualRouter"
+},
+{
+"broadcastdomainrange": "ZONE",
+"name": "BaremetalPxeProvider",
+"devices":  [
+{
+"url":  "10.147.42.200",
+"username": "root",
+"password": "password",
+"tftpdir":"/var/lib/tftpboot",
+"type": "KICK_START"
+}
+]
+},
+{
+"broadcastdomainrange": "ZONE",
+"name": "BaremetalDhcpProvider",
+"devices":  [
+{
+"url":  "10.147.42.200",
+"username": "root",
+"password": "password",
+"type": "DHCPD"
+}
+]
+},
+{
+"broadcastdomainrange": "ZONE",
+"name": "SecurityGroupProvider"
+}
+]
+}
+],
+"networktype": "Basic",
+"pods": [
+{
+"endip": "10.147.42.110",
+"name": "POD0",
+"startip": "10.147.42.100",
+"netmask": "255.255.254.0",
+"guestIpRanges": [
+{
+"startip": "10.147.42.111",
+"endip": "10.147.42.120",
+"netmask": "255.255.254.0",
+"gateway": "10.147.42.1"
+}
+],
+"clusters": [
+{
+"clustername": "C0",
+"hypervisor": "BareMetal",
+"hosts": [
+{
+"username": "root",
+"url": "http://10.147.42.23;,
+"password": "calvin",
+"hostmac": "D4:AE:52:BC:E5:52",
+"cpunumber": "1",
+"cpuspeed": "1000",
  

[GitHub] cloudstack pull request: Changes made to DeployDataCenter to suppo...

[harikrishna-patnala]

Github user harikrishna-patnala commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/809#discussion_r39362992
  
--- Diff: test/integration/smoke/test_baremetal.py ---
@@ -0,0 +1,155 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+""" Test for baremetal
+"""
+#Import Local Modules
+from marvin.cloudstackTestCase import cloudstackTestCase
+from marvin.lib.utils import cleanup_resources, validateList
+from marvin.lib.base import (Template,
+ Host,
+ ServiceOffering,
+ Account,
+ VirtualMachine)
+from marvin.lib.common import get_domain, get_zone
+from marvin.codes import PASS, HOSTTAG1
+from nose.plugins.attrib import attr
+
+#Import System modules
+_multiprocess_shared_ = True
+
+class TestBaremetal(cloudstackTestCase):
+
+@classmethod
+def setUpClass(cls):
+testClient = super(TestBaremetal, cls).getClsTestClient()
+cls.apiclient = testClient.getApiClient()
+cls.services = testClient.getParsedTestDataConfig()
+# Get Zone, Domain
+cls.domain = get_domain(cls.apiclient)
+cls.zone = get_zone(cls.apiclient, testClient.getZoneForTests())
+cls.services['mode'] = cls.zone.networktype
+cls.hypervisor = cls.testClient.getHypervisorInfo()
+cls.account = Account.create(
+cls.apiclient,
+cls.services["account"],
+domainid=cls.domain.id
+)
+#Register baremetal template
+cls.template = Template.register(
+cls.apiclient,
+cls.services["baremetal_template"],
+zoneid=cls.zone.id,
+account=cls.account.name,
+domainid=cls.account.domainid,
+)
+cls.debug(
+"Registered a template of format: %s with ID: %s" % (
+cls.services["baremetal_template"]["format"], 
cls.template.id
+)
+)
+#Update host with host tag
+cls.hosts = Host.list(
+cls.apiclient,
+zoneid=cls.zone.id,
+hypervisor=cls.hypervisor
+)
+if not validateList(cls.hosts)[0]:
+assert False, "Invalid response for list host"
+host_res = Host.update(
--- End diff --

@sanju1010 I have checked the code and there seems a bug exists during vm 
deployment. Here you are setting the tag to Host using updateHostCmd which puts 
the host tag in "host_tags" table, but Baremetal planner searches for hosts 
with hosttag in "host_details" table. Can you please confirm or recheck whether 
baremetal instance provisioning is successful. If not we need to set the host 
tag while adding the host itself.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: reset sshkeyforvirtualmachine also resets password

[Harikrishna Patnala]

Hi Nux,

As already mentioned we store the encrypted vm password using the ssh key, so 
we need to reset the password also.

Regarding the password field in the DB, we have an API to get the VM password 
(https://cloudstack.apache.org/docs/api/apidocs-4.5/root_admin/getVMPassword.html)
 which gets encrypted password from DB.

Thanks,
Harikrishna

On 02-Apr-2015, at 5:07 am, Nux! n...@li.nux.ro wrote:

 Somesh,
 
 Why wouldn't the root password field in the DB just be left alone?
 
 --
 Sent from the Delta quadrant using Borg technology!
 
 Nux!
 www.nux.ro
 
 - Original Message -
 From: Somesh Naidu somesh.na...@citrix.com
 To: dev@cloudstack.apache.org
 Sent: Thursday, 2 April, 2015 00:06:54
 Subject: RE: reset sshkeyforvirtualmachine also resets password
 
 I believe so, since the VM's password (stored in the user_vm_details table)
 needs to be encrypted using the new keys and I believe encryption is a 
 one-way
 hash.
 
 Somesh
 CloudPlatform Escalations
 Citrix Systems, Inc.
 
 
 -Original Message-
 From: Nux! [mailto:n...@li.nux.ro]
 Sent: Wednesday, April 01, 2015 9:16 AM
 To: dev
 Subject: reset sshkeyforvirtualmachine also resets password
 
 Hi,
 
 I've just noticed resetsshkeyforvirtualmachine also resets the root password.
 This doesn't sound right. Is this supposed to happen?
 
 4.4.3 RC2 (4.4-RC20150324T1321) CentOS/KVM
 
 --
 Sent from the Delta quadrant using Borg technology!
 
 Nux!
 www.nux.ro

Re: reset sshkeyforvirtualmachine also resets password

[Harikrishna Patnala]

When we create or register ssh key with CS API, CS only stores public key.
So, cloudstack does not know the private key to decrypt the password and 
encrypt it with new ssh key.

Thanks,
Harikrishna
On 02-Apr-2015, at 11:59 am, Erik Weber terbol...@gmail.com wrote:

 Could it not simply be reencoded with the new key?
 
 Erik
 
 Den torsdag 2. april 2015 skrev Harikrishna Patnala 
 harikrishna.patn...@citrix.com følgende:
 
 Hi Nux,
 
 As already mentioned we store the encrypted vm password using the ssh key,
 so we need to reset the password also.
 
 Regarding the password field in the DB, we have an API to get the VM
 password (
 https://cloudstack.apache.org/docs/api/apidocs-4.5/root_admin/getVMPassword.html)
 which gets encrypted password from DB.
 
 Thanks,
 Harikrishna
 
 On 02-Apr-2015, at 5:07 am, Nux! n...@li.nux.ro javascript:; wrote:
 
 Somesh,
 
 Why wouldn't the root password field in the DB just be left alone?
 
 --
 Sent from the Delta quadrant using Borg technology!
 
 Nux!
 www.nux.ro
 
 - Original Message -
 From: Somesh Naidu somesh.na...@citrix.com javascript:;
 To: dev@cloudstack.apache.org javascript:;
 Sent: Thursday, 2 April, 2015 00:06:54
 Subject: RE: reset sshkeyforvirtualmachine also resets password
 
 I believe so, since the VM's password (stored in the user_vm_details
 table)
 needs to be encrypted using the new keys and I believe encryption is a
 one-way
 hash.
 
 Somesh
 CloudPlatform Escalations
 Citrix Systems, Inc.
 
 
 -Original Message-
 From: Nux! [mailto:n...@li.nux.ro javascript:;]
 Sent: Wednesday, April 01, 2015 9:16 AM
 To: dev
 Subject: reset sshkeyforvirtualmachine also resets password
 
 Hi,
 
 I've just noticed resetsshkeyforvirtualmachine also resets the root
 password.
 This doesn't sound right. Is this supposed to happen?
 
 4.4.3 RC2 (4.4-RC20150324T1321) CentOS/KVM
 
 --
 Sent from the Delta quadrant using Borg technology!
 
 Nux!
 www.nux.ro
 
 

Re: reset sshkeyforvirtualmachine also resets password

[Harikrishna Patnala]

Password is encrypted and stored only if the vm is deployed from password 
enabled template and ssh public key is provided, 
Otherwise we don’t encrypt or store the password.


-Harikrishna


On 02-Apr-2015, at 1:48 pm, Nux! n...@li.nux.ro wrote:

 Thanks Harikrishna, I did not know the password would get encrypted with the 
 ssh key.
 What happens when there is no ssh key registered, how are the passwords 
 encrypted then?
 
 Lucian
 
 --
 Sent from the Delta quadrant using Borg technology!
 
 Nux!
 www.nux.ro
 
 - Original Message -
 From: Harikrishna Patnala harikrishna.patn...@citrix.com
 To: dev@cloudstack.apache.org dev@cloudstack.apache.org
 Sent: Thursday, 2 April, 2015 07:17:54
 Subject: Re: reset sshkeyforvirtualmachine also resets password
 
 Hi Nux,
 
 As already mentioned we store the encrypted vm password using the ssh key, 
 so we
 need to reset the password also.
 
 Regarding the password field in the DB, we have an API to get the VM password
 (https://cloudstack.apache.org/docs/api/apidocs-4.5/root_admin/getVMPassword.html)
 which gets encrypted password from DB.
 
 Thanks,
 Harikrishna
 
 On 02-Apr-2015, at 5:07 am, Nux! n...@li.nux.ro wrote:
 
 Somesh,
 
 Why wouldn't the root password field in the DB just be left alone?
 
 --
 Sent from the Delta quadrant using Borg technology!
 
 Nux!
 www.nux.ro
 
 - Original Message -
 From: Somesh Naidu somesh.na...@citrix.com
 To: dev@cloudstack.apache.org
 Sent: Thursday, 2 April, 2015 00:06:54
 Subject: RE: reset sshkeyforvirtualmachine also resets password
 
 I believe so, since the VM's password (stored in the user_vm_details table)
 needs to be encrypted using the new keys and I believe encryption is a 
 one-way
 hash.
 
 Somesh
 CloudPlatform Escalations
 Citrix Systems, Inc.
 
 
 -Original Message-
 From: Nux! [mailto:n...@li.nux.ro]
 Sent: Wednesday, April 01, 2015 9:16 AM
 To: dev
 Subject: reset sshkeyforvirtualmachine also resets password
 
 Hi,
 
 I've just noticed resetsshkeyforvirtualmachine also resets the root 
 password.
 This doesn't sound right. Is this supposed to happen?
 
 4.4.3 RC2 (4.4-RC20150324T1321) CentOS/KVM
 
 --
 Sent from the Delta quadrant using Borg technology!
 
 Nux!
 www.nux.ro

Re: [ANNOUNCE] Rohit Yadav as new PMC member of CloudStack

[Harikrishna Patnala]

Congrats Rohit :)

-Harikrishna

On 31-Mar-2015, at 10:45 am, Wilder Rodrigues wrodrig...@schubergphilis.com 
wrote:

 Congratulation, Rohit!
 
 Keep up the cool stuff! ;)
 
 Cheers,
 Wilder
 
 On 27 Mar 2015, at 09:07, Sebastien Goasguen run...@gmail.com wrote:
 
 The Project Management Committee (PMC) for Apache CloudStack are pleased to
 announce that Rohit Yadav has accepted our invitation to join the PMC.
 
 Please join me in congratulating him.
 
 On behalf of the Apache CloudStack PMC