incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anthony Xu <>
Subject RE: Secondary nfs server alert issue
Date Mon, 07 May 2012 17:56:06 GMT
In 2.1.*, CloudStack only have one secondary storage and one SSVM for a zone, so CloudStack
uses one host entry to represent both. In 2.2.*, CloudStack support multiple secondary storages
and SSVMs, secondary storage status is not used, but the entries are still being referred.
Ideally, SSVM should report the secondary storage host status and update DB.


-----Original Message-----
From: Nitin Mehta 
Sent: Monday, May 07, 2012 7:45 AM
To:; Ram Chinta
Cc: David Nalley; Anthony Xu
Subject: RE: Secondary nfs server alert issue


I think we should not put the secondary storage in the host table since we do not create an
agent for it and do not send command to it. Since we do not create an agent for it which connects
with MS, the state remains in Alert and means nothing.
I think the introduction of multiple secondary storage led to this addition but we should
move away from this and instead store the secondary storage info in a new table. This has
created a lot of confusion for a number of community users I have seen.
Created a bug for this @ 


PS - Apologize for the top posting here. Still figuring out how to configure outlook for this.

-----Original Message-----
From: Abhinandan Prateek [] 
Sent: Sunday, May 06, 2012 10:20 AM
To:; Ram Chinta
Cc: David Nalley
Subject: RE: Secondary nfs server alert issue

There are two related entries in the host table related to secondary storage. One is the entry
has type as "SecondaryStorageVM" the other one is "SecondaryStorage".
If SSVM is working fine then entry of type SecondaryStorageVM should be Up. The other one
ie of type SecondaryStorage refers just to the path to nfs store and an "Alert" state there
can be ignored, it remains that way in a healthy system. 


-----Original Message-----
From: Ahmad Emneina [] 
Sent: Sunday, May 06, 2012 10:03 AM
To: Ram Chinta;
Cc: David Nalley
Subject: Re: Secondary nfs server alert issue

>It typically indicates a problem with the SSVM (Secondary Storage VM). 
>It either did not get created, or most likely is unable to connect back 
>to the Management once created and running.
>Do you see any errors in the management server log? Refer to 
>"Troubleshooting the Secondary Storage VM" section in the Install guide 
>for troubleshooting suggestions.
>-----Original Message-----
>From: Louis Mui []
>Sent: Friday, May 04, 2012 11:58 PM
>Cc: David Nalley; Ahmad Emneina
>Subject: Secondary nfs server alert issue
>Hi all,
>I have been in discussion with your colleagues for the past 2 days and 
>have corrected most of the issues. One issue that is still outstanding is:
>located under the host alert column, there is an alert about the 
>secondary nfs...and even while cloudstack is running fine the alert 
>does not go away.
>I have also CC'd this email to both David Nalley and Ahmad Emneina.
>If you have any questions please refer to the above personnel listed.
>Thank you.
>Louis Mui
>Infrastructure Admininstrator
>Liferay, Inc.

I think the issue is that one gets an alert on secondary storage no matter what. It's the
first thing that appears in a fresh cloudstack install.
Might not make sense before everything is added, to check for secondary storage health.

View raw message