Hello folks,
To keep the schedule for the 4.12.0.0 release, as discussed on previous
e-mails, the master is now on freezing state. On this week, until 31st
January, we will be working to get master stable for the release candidate
1 (RC1), which if all goes as planned will be launched for testing
Well, I'm glad the topic raised the discussion. That's great. My point is
very carefully explained by Rohit. It's not a new idea - CloudStack
community is small. Some features are abandoned and broken because of no
developers behind them. I bet certain features still not tested in 4.11.2
because no
Sounds good. Altogether, the makeover should be a new user experience and
leverage the latest hypervisor/storage tech and new/redesigned frameworks.
-Suresh
On Thu, Jan 24, 2019 at 10:13 AM Rohit Yadav
wrote:
> I'm in the favour of keeping the 4.x going because no API compatibility is
> broken,
Hi Alireza,
Tables details below as per my knowledge. @Dev Please correct if any detail
is wrong.
- sync_queue and sync_queue_item tables are used for handling the entity
(VM, host, etc) queues and concurrent control. Mainly, all the VM sync jobs
pass through this queuing.
- async_job - all the a
