Ryota,
I've observed many issue with VR (CS 4.3), especially when they are running
for long time and handle considerable amount of traffic (more number of
VMs). Sometimes you will have /var full and sometimes VRs just don't hand
out any IPs to newly created VMs. Doing (clean) network restart works
Dear Dag,
Thank you for your answer.
I checked the VR log(/var/log/kern.log).
It shows that the VR had been out of memory,
and OOMKiller on VR occurred to stop apache2 & dnsmasq service.
Do you have a such experience(out of memory on the VR)?
Regards
***
Hi Rene
In short BIG +1, for longer summary, please read below
PS: For LTS - you mean "Long Term Support" i assume.
We would be interested in seeing the support of 4.5 longer as well, as
we are happy with what we got so far and dont have a burning need to
upgrade yet.
Upgrade would also r
All,
I am +1 on TLS: We have a custom branch of CloudStack, with a few custom
patches. Some of which make sense for everyone, and we’ve committed them back,
or plan to do so, but most of them only work for our specific case, or “cur
corners” by dropping features we don’t need.
An LTS branch wo
(rant alert) I have been stating this in the discuss thread and I don't
agree with your conclusion; with our new workflow any release is a LTS as
long as we maintain the discipline of allowing only bugfixes on the release
they first appeared in (or 4.6 as a start point) If we maintain that
discipli
LTS by the community is not an option for now:
Most of the threads/users/devs had concerns or are skeptical how it can
be done in practice.
As we recently changed the release process, it seems to "early" to
change it again or add new processes to it.
I still think CloudStack need some kind of LT
