[one-users] sunstone can't display the capacity of the system type datastore?

[Carlos Martín Sánchez]

On Tue, Oct 29, 2013 at 10:31 AM, 曹海峰 <caohf at wedogame.com> wrote:

> **
> Thanks.
> BTW: Does 3.8 have this problem?
>

If I recall correctly, the datastore monitorization was introduced in 4.2.

Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | cmartin at opennebula.org |
@OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>


On Tue, Oct 29, 2013 at 10:31 AM, 曹海峰 <caohf at wedogame.com> wrote:

> **
> Thanks.
> BTW: Does 3.8 have this problem?
>
> ------------------------------
>
> Best Wishes
> Dennis
>
>
>  *From:* Carlos Martín Sánchez <cmartin at opennebula.org>
> *Date:* 2013-10-29 17:30
> *To:* 曹海峰 <caohf at wedogame.com>
> *CC:* users at lists.opennebula.org
> *Subject:* Re: [one-users] sunstone can't display the capacity of the
> system type datastore?
>   Hi,
>
>  On Tue, Oct 29, 2013 at 9:07 AM, 曹海峰 <caohf at wedogame.com> wrote:
>
>> **
>> Dear All:
>> In my test environment ,I have a cluster cantain two hosts. There is no
>> share file system in my cluster .both of the hosts use local storage.
>> When I check the capacity of the system type datastore ,it always display
>> " - / -" . the image datastore and the file datastore  seems ok.
>> It there any configure file or command to fix this problem?
>>
>> Thanks!
>>
>
>  There is nothing wrong with your configuration, in 4.2 the system
> datastores are not monitored.
> But this functionality has already been added to master, it will be there
> for the upcoming 4.4.
>
>  Regards
>  --
> Carlos Martín, MSc
> Project Engineer
> OpenNebula - Flexible Enterprise Cloud Made Simple
> www.OpenNebula.org | cmartin at opennebula.org | @OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20131029/941690aa/attachment-0002.htm>