Re: [VOTE] Apache CloudStack 4.14.0.0 RC3

[Pavan Kumar Aravapalli]

Thank you Bobby and Daan for the update. However I have not encountered such 
issue while doing dev test with Vmware 5.5 & 6.5.





Regards,

Pavan Aravapalli.



From: Daan Hoogland 
Sent: 19 May 2020 20:56
To: users 
Cc: dev@cloudstack.apache.org 
Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC3

Thanks Bobby,
All, I've been closely working with Bobby and seen the same things. Does
anybody see any issues releasing 4.14 based on this code? I can confirm
that it is not Pavernalli's UEFI PR and we should not create a new PR to
revert it.
thanks for all of your patience,

(this is me giving a binding +1)


On Tue, May 19, 2020 at 5:04 PM Boris Stoyanov 
wrote:

> Hi guys,
>
> I've done more testing around this and I can now confirm it has nothing to
> do with cloudstack code.
>
> I've tested it with rc3, reverted UEFI PR and 4.13.1 (which does not
> happen to have the feature at all). Also I've used a matrix of VMware
> version of 6.0u2, 6.5u2 and 6.7u3.
>
> The bug is reproducible with all the cloudstack versions, and only vmware
> 6.7u3, I was not able to reproduce this with 6.5/6.0. All of my results
> during testing show it must be related to that specific version of VMware.
>
> Therefore I'm reversing my '-1' and giving a +1 vote on the RC. I think it
> needs to be included in release notes to refrain from that version for now
> until further investigation is done.
>
> Thanks,
> Bobby.
>
> On 19.05.20, 10:08, "Boris Stoyanov" 
> wrote:
>
> Indeed it is severe, but please note it's a corner case which was
> unearthed almost by accident. It falls down to using a new feature of
> selecting a boot protocol and the template must be corrupted. So with
> already existing templates I would not expect to encounter it.
>
> As for recovery, we've managed to recover vCenter and Cloudstack after
> reboots of the vCenter machine and the Cloudstack management service.
> There's no exact points to recover for now, but restart seems to work.
> By graceful failure I mean, cloudstack erroring out the deployment and
> VM finished in ERROR state, meanwhile connection and operability with
> vCenter cluster remains the same.
>
> We're currently exploring options to fix this, one could be to disable
> the feature for VMWare and work to introduce more sustainable fix in next
> release. Other is to look for more guarding code when installing a
> template, since VMware doesn’t actually allow you install that particular
> template but cloudstack does. We'll keep you posted.
>
> Thanks,
> Bobby.
>
> On 18.05.20, 23:01, "Marcus"  wrote:
>
> The issue sounds severe enough that a release note probably won't
> suffice -
> unless there's a documented way to recover we'd never want to
> leave a
> system susceptible to being unrecoverable, even if it's rarely
> triggered.
>
> What's involved in "failing gracefully"? Is this a small fix, or an
> overhaul?  Perhaps the new feature could be disabled for VMware, or
> disabled altogether until a fix is made in a patch release.
>
> Does it only affect new templates, or is there a risk that an
> existing
> template out in vSphere could suddenly cause problems?
>
> On Mon, May 18, 2020 at 12:49 AM Boris Stoyanov <
> boris.stoya...@shapeblue.com> wrote:
>
> > Hi guys,
> >
> > A little further info on this, it appears when we use a
> corrupted template
> > and UEFI/Legacy mode when deploy a VM, it breaks the connection
> between
> > cloudstack and vCenter.
> >
> > All hosts become unreachable and basically the cluster is not
> functional,
> > have not investigated a way to recover this but seems like a
> huge mess..
> > Please note that user is not able to register such template in
> vCenter
> > directly, but cloudstack allows using it.
> >
> > Open to discuss if we'll fix this, since it's expected users to
> use
> > working templates, I think we should be failing gracefully and
> such action
> > should not be able to create downtime on such a large scale.
> >
> > I believe the boot type feature is new one and it's not
> available in older
> > releases, so this issue should be limited to 4.14/current master.
> >
> > Thanks,
> > Bobby.
> >
> > On 15.05.20, 17:07, "Boris Stoyanov" <
> boris.stoya...@shapeblue.com>
> > wrote:
> >
> > I'll have to -1 RC3, we've discovered details about an issue
> which is
> > causing severe consequences with a particular hypervisor in the
> afternoon.
> > We'll need more time to investigate before disclosing.
> >
> > Bobby.
> >
> > On 15.05.20, 9:12, "Boris Stoyanov" <
> boris.stoya...@shapeblue.com>
> > wrote:
> >
> > +1 (binding)
>

Re: Introduction

[Pavan Kumar Aravapalli]

All the Best Suresh.


Regards,
Pavan.


From: Suresh Anaparti 
Sent: 14 April 2020 15:03
To: dev 
Subject: Introduction

Hi All,

This is Suresh (Suresh Kumar Anaparti), have recently joined ShapeBlue. I’m 
happy to rejoin and continue my contribution to the community. Looking forward 
to work with you all.

Regards,
Suresh


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



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: Reg: Permission denied for push operation

[Pavan Kumar Aravapalli]

Ok Thank you, it worked after forking.


Regards,
Pavan.


From: Nicolas Vazquez 
Sent: 16 October 2019 17:15
To: dev@cloudstack.apache.org 
Subject: Re: Reg: Permission denied for push operation

Hi Pavan,

Please consider forking the CloudStack repository into your GitHub account - 
this can be done by clicking the 'Fork' button on 
https://github.com/apache/cloudstack. The fork will generate your own copy of 
the repository in which you will be able to push your branch - your repo URL 
will be like: github.com/pavanaravapalli/cloudstack

After the fork is created, add the repository as a remote on git, for example: 
git remote add personal 
https://github.com/pavanaravapalli/cloudstack.git/<https://github.com/apache/cloudstack.git/>

Then push your branch to 'personal' remote. From this branch, you'll be able to 
create a pull request to the apache/cloudstack repository.


Regards,

Nicolas Vazquez


From: Pavan Kumar Aravapalli 
Sent: Wednesday, October 16, 2019 7:33 AM
To: dev@cloudstack.apache.org 
Subject: Reg: Permission denied for push operation

Hi,

I am facing below exception while pushing branch. Can some one help me in 
resolving the same.
username : pavanaravapalli

Error:
remote: Permission to apache/cloudstack.git denied to pavanaravapalli.
fatal: unable to access 'https://github.com/apache/cloudstack.git/': The 
requested URL returned error: 403



Thanks & Regards,
Pavan.

nicolas.vazq...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue



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.

Reg: Permission denied for push operation

[Pavan Kumar Aravapalli]

Hi,

I am facing below exception while pushing branch. Can some one help me in 
resolving the same.
username : pavanaravapalli

Error:
remote: Permission to apache/cloudstack.git denied to pavanaravapalli.
fatal: unable to access 'https://github.com/apache/cloudstack.git/': The 
requested URL returned error: 403



Thanks & Regards,
Pavan.

Re: Re:Re: Dynamic scaling support for KVM

[Pavan Kumar Aravapalli]

+1 to the feature.


Regards,

Pavan.


From: Haijiao <18602198...@163.com>
Sent: 09 August 2019 11:02:27
To: dev@cloudstack.apache.org 
Subject: Re:Re: Dynamic scaling support for KVM



+1,  almost a 'must-have' feature in nowdays.



At 2019-08-09 00:40:57, "Sven Vogel"  wrote:
>+1 from me too. I hope so with refactor or without :)
>
>Von meinem iPhone gesendet
>
>
>__
>
>Sven Vogel
>Teamlead Platform
>
>EWERK RZ GmbH
>Brühl 24, D-04109 Leipzig
>P +49 341 42649 - 11
>F +49 341 42649 - 18
>s.vo...@ewerk.com
>www.ewerk.com
>
>Geschäftsführer:
>Dr. Erik Wende, Hendrik Schubert, Frank Richter
>Registergericht: Leipzig HRB 17023
>
>Zertifiziert nach:
>ISO/IEC 27001:2013
>DIN EN ISO 9001:2015
>DIN ISO/IEC 2-1:2011
>
>EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
>
>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.
>> Am 08.08.2019 um 18:18 schrieb Anurag Awasthi :
>>
>> +1 to the feature.
>>
>> @Fariborz, perhaps open a github issue as a new feature request?
>> 
>> From: Simon Weller 
>> Sent: Thursday, August 8, 2019 6:30 PM
>> To: dev@cloudstack.apache.org 
>> Subject: Re: Dynamic scaling support for KVM
>>
>> Hi Fariboz,
>>
>> We'd definitely like to add that functionality, but it's going to be a 
>> fairly big lift, as the libxml configs are currently built as a single 
>> block. A large refactor of how we interact with libvirt will be required.
>> This is definitely something we have on our list and hopefully we can 
>> starting taking a look at it within the next few months.
>>
>> -Si
>> 
>> From: Fariborz Navidan 
>> Sent: Thursday, August 8, 2019 7:27 AM
>> To: dev@cloudstack.apache.org 
>> Subject: Dynamic scaling support for KVM
>>
>> Hello Devs,
>>
>> Since long time ago libvirt supports live horizental scaling of VMs. Do you
>> intend for ACS 4.13 to support dynamic scaling of KVM VMs?
>>
>> TIA
>>
>> anurag.awas...@shapeblue.com
>> www.shapeblue.com
>> Amadeus House, Floral Street, London  WC2E 9DPUK
>> @shapeblue
>>
>>
>>
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: Cloudstack VM memory reporting

[Pavan Kumar Aravapalli]

Hi Ng'ang'a Kioi,



Stats are collected at very first time, When a host [KVM] is on-boarded to 
Cloud stack. There after for every vm resource deployment done on the on-boarded

KVM host , the stats will get updated in cloud stack DB by Management Server 
after deducing the utilised resource amount from the host stats.


if any VM is launched from out of the cloud stack scope, i.e with the help of 
virt-manager, this cannot be considered by Management Server

stats service.


@Dev,


This is based on my understanding , correct me if i am wrong.



Regards,

Pavan.



From: Ng'ang'a Kioi 
Sent: 27 July 2019 16:24:19
To: dev@cloudstack.apache.org 
Subject: Cloudstack VM memory reporting

Hi everyone,

I'm trying to look at how cloudstack gathers VM statistics and particularly
memory stats.
Looking at the list virtualmachines api, the following stats are returned
for a sample VM
"memory": 1024,
"memoryintfreekbs": 1251804,
"memorykbs": 1048576,
"memorytargetkbs": 1048576,

Based on the api docs
memory- the memory allocated for the virtual machine
memoryintfreekbs- the internal memory thats free in vm
memorykbs- the memory used by the vm
memorytargetkbs- the target memory in vm

As indicated, memorykbs and memorytargetkbs cannot have the same values.

Looking at the codebase, it seems that these values are recieved from the
StatsCollector class. Is this correct? If so, could the error be
originating from the below?

*statsInMemory.setMemoryKBs(statsForCurrentIteration.getMemoryKBs());*
*statsInMemory.setTargetMemoryKBs(statsForCurrentIteration.getTargetMemoryKBs());*
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.

Reg : qemu-kvm upgrade in KVM hypervisor agent

[Pavan Kumar Aravapalli]

Hello,


As part of KVM upgrade it's found that default package 'qemu-kvm' [ which comes 
with  OS distro]  does not support machine chipset type 'q35'.  And this 
support can be leveraged by installing 'qemu-kvm-ev'  which is from 
centos-release-qemu-ev repo.


I saw some some old mail threads  saying that they have integrated qemu-kvm-ev, 
but still in agent bundle rpm requirements 
[https://github.com/apache/cloudstack/blob/master/packaging/centos7/cloud.spec] 
I found old 'qemu-kvm' only.



Can we leverage this package qemu-kvm-ev in agent rpm bundle?. Has anyone faced 
any issues in Cloud Stack after upgrading the package.



~Regards,

Pavan.

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: New VP of CloudStack: Paul Angus

[Pavan Kumar Aravapalli]

Congratulations Paul.


From: Sven Vogel 
Sent: 11 March 2019 23:12:48
To: dev@cloudstack.apache.org
Cc: us...@cloudstack.apache.org
Subject: Re: New VP of CloudStack: Paul Angus

Congratulations!

Von meinem iPhone gesendet


__

Sven Vogel
Teamlead Platform

EWERK RZ GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 11
F +49 341 42649 - 18
s.vo...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter, Gerhard Hoyer
Registergericht: Leipzig HRB 17023

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

EWERK-Blog | LinkedIn | Xing | Twitter | Facebook

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.
> Am 11.03.2019 um 18:27 schrieb Riepl, Gregor (SWISS TXT) 
> :
>
>
>> I’m happy to announce that the CloudStack PMC has elected Paul Angus
>> as our new VP of CloudStack.
>
> Congratulations, Paul!

@ACL annotation

[Pavan Kumar Aravapalli]

Hi,

 I found some of the api parameters annotated with @ACL in source code.  Is 
this feature enabled ? In ACS , if so provide me some information on how it 
implemented and works.


~Regards
  Pavan

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.

[PROPOSAL] Support Parallel Volume Creation From Snapshot

[Pavan Kumar Aravapalli]

Hi All,


Currently CloudStack does not support concurrent volume creation from snapshot. 
 I would like to add support for the same and documented the details in FS.

Please take a look at the FS below.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Parallel+volume+creation+from+snapshot


Regards,
Pavan Kumar Aravapalli.



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.

Reg : Permission for Jira

[Pavan Kumar Aravapalli]

Hi,

This is Pavan Aravapalli, I am working for Accelerite. I would like to 
contribute for Cloud Stack. Please grant permission for the Jira, so that I can 
create and assign ticket to myself.


Jira Username: pavan4smile


Thanks & Regards
Pavan Kumar Aravapalli.



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.

Reg : Edit Access

[Pavan Kumar Aravapalli]

Hi,


   I am unable to edit/add pages for the cwiki link 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.9+Design+Documents. 
Can some one help me in doing the same.

  Cwiki username: pavan4smile



Thanks & Regards
Pavan Kumar Aravapalli.