Re: Changing default NFS mount options

[Rafael Weingärtner]

Awesome

On Mon, Sep 4, 2017 at 11:35 AM, Andrei Mikhailovsky <
and...@arhont.com.invalid> wrote:

>
> Hi Rafael,
>
> I had a chat with our storage guy and it turns out that this was the
> server side configuration change that was needed. It is all working nicely
> at around 450MB/s for seq writes.
>
> Cheers
>
> Andrei
>
> - Original Message -
> > From: "Rafael Weingärtner" 
> > To: "dev" 
> > Sent: Friday, 1 September, 2017 14:02:20
> > Subject: Re: Changing default NFS mount options
>
> > Do you know which parameter you are setting up manually that is causing
> > this change?
> >
> >
> > On 9/1/2017 7:15 AM, Andrei Mikhailovsky wrote:
> >> Hello guys,
> >>
> >> could you please let me know how could I change the default mount
> options with
> >> the NFS primary storage? I have noticed that if I am mounting nfs
> storage
> >> manually on the host server, the write speeds are significantly faster
> compared
> >> with the mount point that is automatically created by ACS. Like the
> difference
> >> is around 50MB/s for the automatic mount and about 450MB/s for the
> manual
> >> mount.
> >>
> >> Can I manually adjust the mount options, even if it means changing the
> sources
> >> and recompiling?
> >>
> >> Thanks
> >>
> >> Andrei
> >>
> >
> > --
> > --
> > Rafael Weingärtner
>



-- 
Rafael Weingärtner

Re: [RESULT][VOTE] Apache CloudStack 4.9.3.0 (RC1)

[Rohit Yadav]

Thank you, everyone, for participating. I'll work towards updating the website, 
release notes docs/website and publishing the repo/artifacts tomorrow.


- Rohit


From: Boris Stoyanov 
Sent: Friday, September 8, 2017 1:21:05 PM
To: dev@cloudstack.apache.org
Subject: Re: [RESULT][VOTE] Apache CloudStack 4.9.3.0 (RC1)

Thanks for the efforts all, good work!
Bobby.

boris.stoya...@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
  
 

> On Sep 7, 2017, at 5:27 PM, Rene Moser  wrote:
>
> Thanks Rohit for the efforts!
>
> On 09/07/2017 04:22 PM, Rohit Yadav wrote:
>> All,
>>
>> The vote for CloudStack 4.9.3.0 [1] *passes* with
>> 3 PMC + 3 non-PMC votes.
>>
>> +1 (PMC / binding)
>> 3 persons (Milamber, Daan, Rohit)
>>
>> +1 (non binding)
>> 3 person (Glenn, Boris, René)
>>
>> 0
>> none
>>
>> -1
>> none
>>
>> Thanks to everyone participating.
>>
>> I will now prepare the release announcement to go out after 24 hours to
>> give the mirrors time to catch up.
>>
>> [1] http://markmail.org/message/puekeyeamkl34yzy
>>
>> Regards.
>>
>> On Mon, Aug 28, 2017 at 6:44 PM, Rohit Yadav  wrote:
>>>
>>> Hi All,
>>>
>>> I've created a 4.9.3.0 RC1 release, with the following artifacts up for a
>> vote:
>>>
>>> Git Branch and Commit SH:
>>>
>>>
>> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.9.3.0-RC20170828T1452
>>> https://github.com/apache/cloudstack/tree/4.9.3.0-RC20170828T1452
>>> Commit: d145944be0d04724802ff132399514bf71c3e7b0
>>>
>>> 4.9 branch smoke test PR:
>>> https://github.com/apache/cloudstack/pull/2217
>>>
>>> List of commits/changes since 4.9.2.0 release:
>>>
>> https://github.com/apache/cloudstack/compare/4.9.2.0...4.9.3.0-RC20170828T1452
>>>
>>> Source release (checksums and signatures are available at the same
>> location):
>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.9.3.0/
>>>
>>> PGP release keys (signed using 0EE3D884):
>>> 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)
>>>
>>> Regards,
>>> Rohit Yadav
>>

KVM Host overprovisioning

[Ivan Kudryavtsev]

Hello, community.

During the last years Linux kernel got some interesting features like KSM,
ZSWAP, ZRAM. Hardware also steps forward and we see Intel 3d xpoint,
extremely fast SSD drives with m.2 and PCI-E interfaces.

These facilities enable potentially interesting use of overcommited RAM for
hosts. According to IBM's investigations Zswap with LZ4/ZBUD increases
virtual RAM on 40%.

I investigated current Apache CloudStack memory overcommitment capabilities
and they mostly affect VM's RAM by utilizing ballooning and I think it's
not what necessary to open new facilities. There are many cases which can
utilize ZSWAP and fast swap devices to efficiently provision more RAM than
presents.

I suppose, CloudStack Agent for KVM can have configured parameter which
"mangles" RAM reported. From the other hand it can be done by implemented
host properties on server side. I tried manual increasing in host table:

update host set ram=ram * 1.4 where id=1;

and it seems until the next host stats update it works as expected. I think
this workaround is useful, but it's better to have the function in core
like standard.

Let me know what you think about it, it might be I don't understand
something and ACS already has it in place? I also would like to hear your
thoughts on ZSWAP usage in practice.

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