Re: [DISCUSS] CloudStack 4.9.3.0 (LTS)

[Rubens Malheiro]

What would be very interesting would be to enable the KVM snapshot feature
live

Maybe this would be a barrier to breaking over the limitation of PODS KVM
vs. XEN

And it would be a resource of immediate impact.

Sorry my english via translate

On Wed, Jul 12, 2017 at 12:52 PM, Outback Dingo 
wrote:

> On Wed, Jul 12, 2017 at 10:41 AM, Rohit Yadav 
> wrote:
> > All,
> >
> >
> > Please send me a list of PRs you would like to see in 4.9.3.0 so we can
> freeze the scope for 4.9.3.0, no promises but it may be possible to have a
> release plan as soon as next week.
> >
> >
>
> Support for XenServer 7.1 would be nice
>
>
> > - Rohit
> >
> > 
> > From: Wido den Hollander 
> > Sent: 12 July 2017 01:27:30
> > To: Rohit Yadav; d...@cloudstack.apache.org; users@cloudstack.apache.org
> > Subject: Re: [DISCUSS] CloudStack 4.9.3.0 (LTS)
> >
> > Hi,
> >
> > I would suggest: https://github.com/apache/cloudstack/pull/2131
> >
> > Serious issue with Ubuntu 16.04 and statistics gathering on KVM.
> >
> > Wido
> >
> >> Op 11 juli 2017 om 11:49 schreef Rohit Yadav  >:
> >>
> >>
> >> Hi Sean,
> >>
> >>
> >> Thanks for sharing.
> >>
> >>
> >> - Rohit
> >>
> >> 
> >> From: Sean Lair 
> >> Sent: 11 July 2017 03:41:17
> >> To: d...@cloudstack.apache.org
> >> Cc: users@cloudstack.apache.org
> >> Subject: RE: [DISCUSS] CloudStack 4.9.3.0 (LTS)
> >>
> >> Here are three issues we ran into in 4.9.2.0.  We have been running all
> of these fixes for several months without issues.  The code changes are all
> very easy/small, but had a big impact for us.
> >>
> >> I'd respectfully suggest they go into 4.9.3.0:
> >>
> >> https://github.com/apache/cloudstack/pull/2041 (VR related jobs
> scheduled and run twice on mgmt servers)
> >> https://github.com/apache/cloudstack/pull/2040 (Bug in monitoring of
> S2S VPNs - also exists in 4.10)
> >> https://github.com/apache/cloudstack/pull/1966 (IPSEC VPNs do not work
> after vRouter reboot)
> >>
> >> Thanks
> >> Sean
> >>
> >> rohit.ya...@shapeblue.com
> >> www.shapeblue.com
> >> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> >> @shapeblue
> >>
> >>
> >>
> >>
> >> -Original Message-
> >> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
> >> Sent: Friday, July 7, 2017 1:14 AM
> >> To: d...@cloudstack.apache.org
> >> Cc: users@cloudstack.apache.org
> >> Subject: [DISCUSS] CloudStack 4.9.3.0 (LTS)
> >>
> >> All,
> >>
> >>
> >> With 4.10.0.0 voted, I would like to start some initial discussion
> around the next minor LTS release 4.9.3.0. At the moment I don't have a
> timeline, plans or dates to share but I would like to engage with the
> community to gather list of issues, commits, PRs that we should consider
> for the next LTS release 4.9.3.0.
> >>
> >>
> >> To reduce our test and QA scope, we don't want to consider changes that
> are new feature, or enhancements but strictly blockers/critical/major
> bugfixes and security related fixes, and we can consider reverting any
> already committed/merged PR(s) on 4.9 branch (committed since 4.9.2.0).
> >>
> >>
> >> Please go through list of commits since 4.9.2.0 (you can also run, git
> log 4.9.2.0..4.9) and let us know if there is any change we should consider
> reverting:
> >>
> >> https://github.com/apache/cloudstack/commits/4.9
> >>
> >>
> >> I started
> backporting some fixes on the 4.9 branch, please go through the following
> PR and raise objections on changes/commits that we should not backport or
> revert:
> >>
> >> https://github.com/apache/cloudstack/pull/2052
> >>
> >>
> >> Lastly, please also share any PRs that we should consider
> reviewing+merging on 4.9 branch for the 4.9.3.0 release effort.
> >>
> >>
> >> - Rohit
> >>
> >> rohit.ya...@shapeblue.com
> >> www.shapeblue.com
> >> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> >>
> >>
> >>
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
>

Re: [DISCUSS] CloudStack 4.9.3.0 (LTS)

[Outback Dingo]

On Wed, Jul 12, 2017 at 10:41 AM, Rohit Yadav  wrote:
> All,
>
>
> Please send me a list of PRs you would like to see in 4.9.3.0 so we can 
> freeze the scope for 4.9.3.0, no promises but it may be possible to have a 
> release plan as soon as next week.
>
>

Support for XenServer 7.1 would be nice


> - Rohit
>
> 
> From: Wido den Hollander 
> Sent: 12 July 2017 01:27:30
> To: Rohit Yadav; d...@cloudstack.apache.org; users@cloudstack.apache.org
> Subject: Re: [DISCUSS] CloudStack 4.9.3.0 (LTS)
>
> Hi,
>
> I would suggest: https://github.com/apache/cloudstack/pull/2131
>
> Serious issue with Ubuntu 16.04 and statistics gathering on KVM.
>
> Wido
>
>> Op 11 juli 2017 om 11:49 schreef Rohit Yadav :
>>
>>
>> Hi Sean,
>>
>>
>> Thanks for sharing.
>>
>>
>> - Rohit
>>
>> 
>> From: Sean Lair 
>> Sent: 11 July 2017 03:41:17
>> To: d...@cloudstack.apache.org
>> Cc: users@cloudstack.apache.org
>> Subject: RE: [DISCUSS] CloudStack 4.9.3.0 (LTS)
>>
>> Here are three issues we ran into in 4.9.2.0.  We have been running all of 
>> these fixes for several months without issues.  The code changes are all 
>> very easy/small, but had a big impact for us.
>>
>> I'd respectfully suggest they go into 4.9.3.0:
>>
>> https://github.com/apache/cloudstack/pull/2041 (VR related jobs scheduled 
>> and run twice on mgmt servers)
>> https://github.com/apache/cloudstack/pull/2040 (Bug in monitoring of S2S 
>> VPNs - also exists in 4.10)
>> https://github.com/apache/cloudstack/pull/1966 (IPSEC VPNs do not work after 
>> vRouter reboot)
>>
>> Thanks
>> Sean
>>
>> rohit.ya...@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>>
>> -Original Message-
>> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
>> Sent: Friday, July 7, 2017 1:14 AM
>> To: d...@cloudstack.apache.org
>> Cc: users@cloudstack.apache.org
>> Subject: [DISCUSS] CloudStack 4.9.3.0 (LTS)
>>
>> All,
>>
>>
>> With 4.10.0.0 voted, I would like to start some initial discussion around 
>> the next minor LTS release 4.9.3.0. At the moment I don't have a timeline, 
>> plans or dates to share but I would like to engage with the community to 
>> gather list of issues, commits, PRs that we should consider for the next LTS 
>> release 4.9.3.0.
>>
>>
>> To reduce our test and QA scope, we don't want to consider changes that are 
>> new feature, or enhancements but strictly blockers/critical/major bugfixes 
>> and security related fixes, and we can consider reverting any already 
>> committed/merged PR(s) on 4.9 branch (committed since 4.9.2.0).
>>
>>
>> Please go through list of commits since 4.9.2.0 (you can also run, git log 
>> 4.9.2.0..4.9) and let us know if there is any change we should consider 
>> reverting:
>>
>> https://github.com/apache/cloudstack/commits/4.9
>>
>>
>> I started backporting some 
>> fixes on the 4.9 branch, please go through the following PR and raise 
>> objections on changes/commits that we should not backport or revert:
>>
>> https://github.com/apache/cloudstack/pull/2052
>>
>>
>> Lastly, please also share any PRs that we should consider reviewing+merging 
>> on 4.9 branch for the 4.9.3.0 release effort.
>>
>>
>> - Rohit
>>
>> rohit.ya...@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>>
>>
>>
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>

Re: KVM hypervm and HA

[Simon Weller]

So today, we aren't using any a watchdog timer on KVM, but Wido has submitted a 
PR to include one. What that means is that today the VM container has to fail 
before an HA action will be completed. If the VM just kernel panics and doesn't 
have it's own kernel watchdog timer, the Mgmt Server will still believe the VM 
is alive and well.


There is also a lot of work underway to greatly improve the KVM HA overall. A 
good chunk of this has already been merged around IPMI management and control 
of the underling host servers. There is a new proposal currently in development 
that will better handle host failure and force a fencing action to make sure we 
have no chance of data corruption. Today if a host fails and the agent goes 
down hard with it, VMs that were on the host will not be HA'd to another host 
until an operator takes an action to remove that host from ACS.


- Si


From: Audrey Roberto B Baldin 
Sent: Wednesday, July 12, 2017 8:28 AM
To: users
Subject: Re: KVM hypervm and HA

Hello Victor,

As far as I tested the HA in KVM, it only get in action if:

i. The computing offer you are using to create the guest VM has the Offer HA 
flag on;
ii. The KVM should crash unexpectedly;

To force a crash you can simulate a kernel panic using the command: echo c > 
/proc/sysrq-trigger.

I had some issues that one KVM agent, for some unknown reason, was 
disconnecting from the orchestrator, although it was working and the guest VM 
were running. In this situation I couldn't do anything with the guests VMs 
(move, reload, shutdown) and the HA didn't work.

Hope you find this information useful.

Regards,
Audrey

- Mensagem original -
De: "Ivan Kudryavtsev" 
Para: "victor" 
Cc: "users" 
Enviadas: Quarta-feira, 12 de julho de 2017 6:55:00
Assunto: Re: KVM hypervm and HA

You should mark VM service offering as HA-enabled and ACS will start vms
automatically. VR, SSVM, CP VMs are also started automatically as needed.

2017-07-12 16:53 GMT+07:00 victor :

> Hello,
>
> Thanks for the update.  When a single vm in "hypervm1" is stopped or down,
> it gets automatically started in the second vm. But when the entire
> hypervm1 server  is down completely, the vm' inside it is not getting
> started in the secondary "hypervm2". Is the feature is version specific.
>
> Regards
> Victor
>
>
> On 07/12/2017 08:26 AM, Ivan Kudryavtsev wrote:
>
>> Hi, Victor. They both will be moved automatically to a new host by ACS.
>>
>> 12 июл. 2017 г. 5:23 пользователь "victor" 
>> написал:
>>
>> Hello,
>>>
>>>   I have a cloudstack system with one management server, one nfs server
>>> and
>>> two kvm hypervm host servers. Initially I configured cloudstack  with
>>> hypervm1, so the system vm  and console proxy gets created in it. Lately
>>> I
>>> have added hypervm2 and created few instances in it. So my doubt is the
>>> following.
>>>
>>> 
>>>
>>> 1, If hypervm 1 is down which contain system-vm,console-proxy and
>>> router-vm, then what will happen.
>>>
>>> 2, If hypervm 1 is down completely and we couldn't make it up, will the
>>> system vm,console proxy and router vm will be switched to hypervm2
>>> automatically.  If it is not automatically, then is there any option for
>>> that.
>>>
>>> 
>>>
>>> Regards
>>>
>>> Victor
>>>
>>>
>>>
>


--
With best regards, Ivan Kudryavtsev
Bitworks Software, Ltd.
Cell: +7-923-414-1515
WWW: http://bitworks.software/ 
DESIGN AND DEVELOPMENT OF COMPREHENSIVE SOFTWARE SYSTEMS 
...
bitworks.software
design and development of comprehensive software systems for fast-growing 
businesses

Re: [DISCUSS] CloudStack 4.9.3.0 (LTS)

[Rohit Yadav]

All,


Please send me a list of PRs you would like to see in 4.9.3.0 so we can freeze 
the scope for 4.9.3.0, no promises but it may be possible to have a release 
plan as soon as next week.


- Rohit


From: Wido den Hollander 
Sent: 12 July 2017 01:27:30
To: Rohit Yadav; d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Re: [DISCUSS] CloudStack 4.9.3.0 (LTS)

Hi,

I would suggest: https://github.com/apache/cloudstack/pull/2131

Serious issue with Ubuntu 16.04 and statistics gathering on KVM.

Wido

> Op 11 juli 2017 om 11:49 schreef Rohit Yadav :
>
>
> Hi Sean,
>
>
> Thanks for sharing.
>
>
> - Rohit
>
> 
> From: Sean Lair 
> Sent: 11 July 2017 03:41:17
> To: d...@cloudstack.apache.org
> Cc: users@cloudstack.apache.org
> Subject: RE: [DISCUSS] CloudStack 4.9.3.0 (LTS)
>
> Here are three issues we ran into in 4.9.2.0.  We have been running all of 
> these fixes for several months without issues.  The code changes are all very 
> easy/small, but had a big impact for us.
>
> I'd respectfully suggest they go into 4.9.3.0:
>
> https://github.com/apache/cloudstack/pull/2041 (VR related jobs scheduled and 
> run twice on mgmt servers)
> https://github.com/apache/cloudstack/pull/2040 (Bug in monitoring of S2S VPNs 
> - also exists in 4.10)
> https://github.com/apache/cloudstack/pull/1966 (IPSEC VPNs do not work after 
> vRouter reboot)
>
> Thanks
> Sean
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
> Sent: Friday, July 7, 2017 1:14 AM
> To: d...@cloudstack.apache.org
> Cc: users@cloudstack.apache.org
> Subject: [DISCUSS] CloudStack 4.9.3.0 (LTS)
>
> All,
>
>
> With 4.10.0.0 voted, I would like to start some initial discussion around the 
> next minor LTS release 4.9.3.0. At the moment I don't have a timeline, plans 
> or dates to share but I would like to engage with the community to gather 
> list of issues, commits, PRs that we should consider for the next LTS release 
> 4.9.3.0.
>
>
> To reduce our test and QA scope, we don't want to consider changes that are 
> new feature, or enhancements but strictly blockers/critical/major bugfixes 
> and security related fixes, and we can consider reverting any already 
> committed/merged PR(s) on 4.9 branch (committed since 4.9.2.0).
>
>
> Please go through list of commits since 4.9.2.0 (you can also run, git log 
> 4.9.2.0..4.9) and let us know if there is any change we should consider 
> reverting:
>
> https://github.com/apache/cloudstack/commits/4.9
>
>
> I started backporting some 
> fixes on the 4.9 branch, please go through the following PR and raise 
> objections on changes/commits that we should not backport or revert:
>
> https://github.com/apache/cloudstack/pull/2052
>
>
> Lastly, please also share any PRs that we should consider reviewing+merging 
> on 4.9 branch for the 4.9.3.0 release effort.
>
>
> - Rohit
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>
>
>

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: KVM hypervm and HA

[Audrey Roberto B Baldin]

Hello Victor,

As far as I tested the HA in KVM, it only get in action if:

i. The computing offer you are using to create the guest VM has the Offer HA 
flag on;
ii. The KVM should crash unexpectedly;

To force a crash you can simulate a kernel panic using the command: echo c > 
/proc/sysrq-trigger.

I had some issues that one KVM agent, for some unknown reason, was 
disconnecting from the orchestrator, although it was working and the guest VM 
were running. In this situation I couldn't do anything with the guests VMs 
(move, reload, shutdown) and the HA didn't work.

Hope you find this information useful.

Regards,
Audrey

- Mensagem original -
De: "Ivan Kudryavtsev" 
Para: "victor" 
Cc: "users" 
Enviadas: Quarta-feira, 12 de julho de 2017 6:55:00
Assunto: Re: KVM hypervm and HA

You should mark VM service offering as HA-enabled and ACS will start vms
automatically. VR, SSVM, CP VMs are also started automatically as needed.

2017-07-12 16:53 GMT+07:00 victor :

> Hello,
>
> Thanks for the update.  When a single vm in "hypervm1" is stopped or down,
> it gets automatically started in the second vm. But when the entire
> hypervm1 server  is down completely, the vm' inside it is not getting
> started in the secondary "hypervm2". Is the feature is version specific.
>
> Regards
> Victor
>
>
> On 07/12/2017 08:26 AM, Ivan Kudryavtsev wrote:
>
>> Hi, Victor. They both will be moved automatically to a new host by ACS.
>>
>> 12 июл. 2017 г. 5:23 пользователь "victor" 
>> написал:
>>
>> Hello,
>>>
>>>   I have a cloudstack system with one management server, one nfs server
>>> and
>>> two kvm hypervm host servers. Initially I configured cloudstack  with
>>> hypervm1, so the system vm  and console proxy gets created in it. Lately
>>> I
>>> have added hypervm2 and created few instances in it. So my doubt is the
>>> following.
>>>
>>> 
>>>
>>> 1, If hypervm 1 is down which contain system-vm,console-proxy and
>>> router-vm, then what will happen.
>>>
>>> 2, If hypervm 1 is down completely and we couldn't make it up, will the
>>> system vm,console proxy and router vm will be switched to hypervm2
>>> automatically.  If it is not automatically, then is there any option for
>>> that.
>>>
>>> 
>>>
>>> Regards
>>>
>>> Victor
>>>
>>>
>>>
>


-- 
With best regards, Ivan Kudryavtsev
Bitworks Software, Ltd.
Cell: +7-923-414-1515
WWW: http://bitworks.software/ 

Re: KVM hypervm and HA

[Ivan Kudryavtsev]

You should mark VM service offering as HA-enabled and ACS will start vms
automatically. VR, SSVM, CP VMs are also started automatically as needed.

2017-07-12 16:53 GMT+07:00 victor :

> Hello,
>
> Thanks for the update.  When a single vm in "hypervm1" is stopped or down,
> it gets automatically started in the second vm. But when the entire
> hypervm1 server  is down completely, the vm' inside it is not getting
> started in the secondary "hypervm2". Is the feature is version specific.
>
> Regards
> Victor
>
>
> On 07/12/2017 08:26 AM, Ivan Kudryavtsev wrote:
>
>> Hi, Victor. They both will be moved automatically to a new host by ACS.
>>
>> 12 июл. 2017 г. 5:23 пользователь "victor" 
>> написал:
>>
>> Hello,
>>>
>>>   I have a cloudstack system with one management server, one nfs server
>>> and
>>> two kvm hypervm host servers. Initially I configured cloudstack  with
>>> hypervm1, so the system vm  and console proxy gets created in it. Lately
>>> I
>>> have added hypervm2 and created few instances in it. So my doubt is the
>>> following.
>>>
>>> 
>>>
>>> 1, If hypervm 1 is down which contain system-vm,console-proxy and
>>> router-vm, then what will happen.
>>>
>>> 2, If hypervm 1 is down completely and we couldn't make it up, will the
>>> system vm,console proxy and router vm will be switched to hypervm2
>>> automatically.  If it is not automatically, then is there any option for
>>> that.
>>>
>>> 
>>>
>>> Regards
>>>
>>> Victor
>>>
>>>
>>>
>


-- 
With best regards, Ivan Kudryavtsev
Bitworks Software, Ltd.
Cell: +7-923-414-1515
WWW: http://bitworks.software/ 

Re: KVM hypervm and HA

[victor]

Hello,

Thanks for the update.  When a single vm in "hypervm1" is stopped or 
down, it gets automatically started in the second vm. But when the 
entire hypervm1 server  is down completely, the vm' inside it is not 
getting started in the secondary "hypervm2". Is the feature is version 
specific.


Regards
Victor

On 07/12/2017 08:26 AM, Ivan Kudryavtsev wrote:

Hi, Victor. They both will be moved automatically to a new host by ACS.

12 июл. 2017 г. 5:23 пользователь "victor"  написал:


Hello,

  I have a cloudstack system with one management server, one nfs server and
two kvm hypervm host servers. Initially I configured cloudstack  with
hypervm1, so the system vm  and console proxy gets created in it. Lately I
have added hypervm2 and created few instances in it. So my doubt is the
following.



1, If hypervm 1 is down which contain system-vm,console-proxy and
router-vm, then what will happen.

2, If hypervm 1 is down completely and we couldn't make it up, will the
system vm,console proxy and router vm will be switched to hypervm2
automatically.  If it is not automatically, then is there any option for
that.



Regards

Victor

Re: Snapshot and secondary storage utilisation.

[Makrand]

Thanks, guys! I somehow overlooked this parameter.

BTW isn't there any sophisticated documentation that defines all such
global parameters and their purpose? Moreover, I am unable to find any DB
related documentation that defines various tables in DB and their relation
wrt each other?

Isn't there a proper guide for this?

--
Makrand


On Mon, Jul 10, 2017 at 1:35 PM, Anshul Gangwar <
anshul.gang...@accelerite.com> wrote:

> By default, xenserver takes delta snapshots i.e. snapshot of differential
> disk from last snapshot taken. This is configurable via global setting
> “snapshot.delta.max”. That setting tells till when keep taking delta
> snapshots before taking full snapshots. By default, value is 16. If you
> don’t want that behaviour make it 0. Taking only differential disks
> snapshot makes the snapshot operation faster but with the cost of
> additional storage.
>
> Regards,
> Anshul
>
> On 10/07/17, 12:43 PM, "Makrand"  wrote:
>
> ​​
> Hi all,
>
> My setup is:- ACS 4.4. XENserver 6.2 SP1. 4TB of secondary storage
> coming
> from NFS.
>
> I am observing some issues the way *.vhd* files are stored and cleaned
> up
> in secondary storage. Let's take an example of a VM-813. It has 250G
> root
> disk (disk ID 1015) The snapshot is scheduled to happen once every week
> (sat night) and supposes to keep only 1 snapshot. From GUI I am seeing
> its
> only keeping the latest week snapshot.
>
> But resource utilization on CS GUI is increasing day by day. So I just
> ran
> du -smh and found there are multiple vhd files of different sizes under
> secondary storage.
>
> Here is snippet:-
>
> root@gcx-bom-cloudstack:/mnt/secondary2/snapshots/22# du -smhh *
> 1.5K1002
> 1.5K1003
> 1.5K1004
> *243G1015*
> 1.5K1114
>
> root@gcx-bom-cloudstack:/mnt/secondary2/snapshots/22# ls -lht *
> *1015:*
> *total 243G*
> *-rw-r--r-- 1 nobody nogroup  32G Jul  8 21:19
> 8a7e6580-5191-4eb0-9eb1-3ec8e75ce104.vhd*
> *-rw-r--r-- 1 nobody nogroup  40G Jul  1 21:30
> f52b82b0-0eaf-4297-a973-1f5477c10b5e.vhd*
> *-rw-r--r-- 1 nobody nogroup  43G Jun 24 21:35
> 3dc72a3b-91ad-45ae-b618-9aefb7565edb.vhd*
> *-rw-r--r-- 1 nobody nogroup  40G Jun 17 21:30
> c626a9c5-1929-4489-b181-6524af1c88ad.vhd*
> *-rw-r--r-- 1 nobody nogroup  29G Jun 10 21:16
> 697cf9bd-4433-426d-a4a1-545f03aae3e6.vhd*
> *-rw-r--r-- 1 nobody nogroup  29G Jun  3 21:00
> bff859b3-a51c-4186-8c19-1ba94f99f9e7.vhd*
> *-rw-r--r-- 1 nobody nogroup  43G May 27 21:35
> 127e3f6e-4fa5-45ed-a95d-7d0b850a053d.vhd*
> *-rw-r--r-- 1 nobody nogroup  60G May 20 22:01
> 619fe1ed-6807-441c-9526-526486d7a6d2.vhd*
> *-rw-r--r-- 1 nobody nogroup  35G May 13 21:23
> 71b0d6a8-3c93-493f-b82c-732b7a808f6d.vhd*
> *-rw-r--r-- 1 nobody nogroup  31G May  6 21:19
> ccbfb3ec-abd8-448c-ba79-36631b227203.vhd*
> *-rw-r--r-- 1 nobody nogroup  32G Apr 29 21:18
> 52215821-ed4d-4283-9aed-9f9cc5acd5bd.vhd*
> *-rw-r--r-- 1 nobody nogroup  38G Apr 22 21:26
> 4cb6ea42-8450-493a-b6f2-5be5b0594a30.vhd*
> *-rw-r--r-- 1 nobody nogroup 248G Apr 16 00:44
> 243f50d6-d06a-47af-ab45-e0b8599aac8d.vhd*
>
>
> Observed same behavior for root disks of other 4 VMs. So the number of
> vhds
> are ever growing on secondary storage and one will eventually run out
> of
> secondary storage size.
>
> Simple Question:-
>
> 1) Why is cloud stack creating multiple vhd files? Should not it
> supposed
> to keep only one vhd at secondary storage defined in snap policy?
>
> Any thoughts? As explained earlier...from GUI I am seeing last weeks
> snap
> as backed up.
>
>
>
> --
> Makrand
>
>
> 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 4.9 on centos 6.9

[siva rajesh]

Thanks Paul, i am able to process with my installation centos 6.9

Regards,
Rajesh,
Maigha

On Wed, Jul 12, 2017 at 1:08 PM, Paul Angus 
wrote:

> Rajesh,
>
> It looks like an installation step is missing from the documentation, you
> can find the steps to Install MySQL connector in the upgrade steps.
>
> http://docs.cloudstack.apache.org/projects/cloudstack-
> release-notes/en/4.9.2.0/upgrade/upgrade-4.8.html
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: siva rajesh [mailto:g.sivarajes...@gmail.com]
> Sent: 12 July 2017 08:33
> To: users@cloudstack.apache.org
> Subject: cloudstack 4.9 on centos 6.9
>
> Hi
>
>  I am getting following dependency error while installing
> cloudstack 4.9 on centos 6.9
>
> Error: Package: cloudstack-management-4.9.2.0-1.el6.x86_64 (cloudstack)
>Requires: mysql-connector-python
>  You could try using --skip-broken to work around the problem  You
> could try running: rpm -Va --nofiles --nodigest [root@cloudstack ~]# cat
> /etc/redhat-release CentOS release 6.9 (Final) [root@cloudstack ~
>
> Can anyone help fixing this issue?
>
> Thanks,
> Rajesh,
> Maigha
>

RE: cloudstack 4.9 on centos 6.9

[Paul Angus]

Rajesh,

It looks like an installation step is missing from the documentation, you can 
find the steps to Install MySQL connector in the upgrade steps.

http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.9.2.0/upgrade/upgrade-4.8.html


Kind regards,

Paul Angus

paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: siva rajesh [mailto:g.sivarajes...@gmail.com] 
Sent: 12 July 2017 08:33
To: users@cloudstack.apache.org
Subject: cloudstack 4.9 on centos 6.9

Hi

 I am getting following dependency error while installing cloudstack 
4.9 on centos 6.9

Error: Package: cloudstack-management-4.9.2.0-1.el6.x86_64 (cloudstack)
   Requires: mysql-connector-python
 You could try using --skip-broken to work around the problem  You 
could try running: rpm -Va --nofiles --nodigest [root@cloudstack ~]# cat 
/etc/redhat-release CentOS release 6.9 (Final) [root@cloudstack ~

Can anyone help fixing this issue?

Thanks,
Rajesh,
Maigha

Re: cloudstack 4.9 on centos 6.9

[Mohd Zainal Abidin]

Better use centos7.

On Wed, Jul 12, 2017 at 3:33 PM, siva rajesh 
wrote:

> Hi
>
>  I am getting following dependency error while installing
> cloudstack 4.9 on centos 6.9
>
> Error: Package: cloudstack-management-4.9.2.0-1.el6.x86_64 (cloudstack)
>Requires: mysql-connector-python
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
> [root@cloudstack ~]# cat /etc/redhat-release
> CentOS release 6.9 (Final)
> [root@cloudstack ~
>
> Can anyone help fixing this issue?
>
> Thanks,
> Rajesh,
> Maigha
>



-- 
Thank you
__

Mohd Zainal Abidin

cloudstack 4.9 on centos 6.9

[siva rajesh]

Hi

 I am getting following dependency error while installing
cloudstack 4.9 on centos 6.9

Error: Package: cloudstack-management-4.9.2.0-1.el6.x86_64 (cloudstack)
   Requires: mysql-connector-python
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
[root@cloudstack ~]# cat /etc/redhat-release
CentOS release 6.9 (Final)
[root@cloudstack ~

Can anyone help fixing this issue?

Thanks,
Rajesh,
Maigha