Hi Rohit
I previous suggested these for 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
Hi Rohit
On 07/23/2017 06:08 PM, Rohit Yadav wrote:
> All,
>
>
> Just want to kick an initial discussion around migration to Debian9 based
> systemvmtemplate, and get your feedback on the same.
>
> Here's a work-in-progress PR: https://github.com/apache/cloudstack/pull/2198
Have you consider
Hi
On 07/23/2017 06:21 PM, Paul Angus wrote:
>
> I think that we should look at lighter Distros like Arch Linux in order to
> get the boot times of the system VMs down.
> That in conjunction with improving the configuration will gives as a much
> leaner, meaner System VM.
I tend to -1 for Arch
Hello Wido,
we found source of this bug and also found that patch already implemented:
https://github.com/apache/cloudstack/commit/9dcfbceae71865b4de1a4744ceac8f48255733a2
sorry for inaccuracy, initially we tested on 4.5 release
On 24.07.17 14:56, Wido den Hollander wrote:
Op 21 juli 2017 om
> Op 21 juli 2017 om 17:57 schreef Dmytro Shevchenko
> :
>
>
> Here is the error that we caught with Libvirt 1.3.1:
>
> 2017-07-21 11:46:27,501 WARN [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-1:null) Plug Nic failed due to
> org.libvirt.LibvirtException: internal error
> Op 24 juli 2017 om 10:47 schreef Marc-Aurèle Brothier :
>
>
> Hi Wido,
>
> I have one comment on this topic. Some of those PRs are lying there because
> no one took the time to merge them (I have a couple like that) since they
> were not very important (I think it's the reason), fixing only a
All,
We'll accept bugfixes on 4.9 branch till end of next week, following which I'll
start release work towards 4.9.3.0 (LTS) release. Please help review
outstanding PRs, share PRs that we should consider and advise/suggest issues
that need to be reverted/backported, for example see:
https://
My personal opinion is such activities are not useful and generally a waste of
time, it might give us a feel good factor that the total open PRs (for that
matter JIRA tickets) are low but it may do more harm than good. In general, a
PR might take up to 6 months to merge depending on how engaging
Hi Wido,
I have one comment on this topic. Some of those PRs are lying there because
no one took the time to merge them (I have a couple like that) since they
were not very important (I think it's the reason), fixing only a small
glitch or improving an output. If we start to close the PRs because
Hi,
While writing this e-mail we have 191 Open Pull requests [0] on Github and that
number keeps hovering around ~200.
We have a great number of PRs being merged, but a lot of code is old and
doesn't even merge anymore.
My proposal would be that we close all PRs which didn't see any activity i
Only though testing we can know if there are any regressions, with Debian7 to
be unsupported somewhere in 2018 we need to start some work around this.
Distros such as Arch Linux are not solid enough or work out of the box and have
bleeding edge unstable software. Debian 9 "stretch" finally have
> Op 23 juli 2017 om 18:21 schreef Paul Angus :
>
>
>
> I think that we should look at lighter Distros like Arch Linux in order to
> get the boot times of the system VMs down.
Debian 9 uses systemd and that makes it boot a lot faster.
> That in conjunction with improving the configuration wi
12 matches
Mail list logo
