cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gabriel Beims Bräscher <gabrasc...@gmail.com>
Subject Re: Re: [PROPOSE] RM for 4.12
Date Thu, 24 Jan 2019 13:05:39 GMT
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 on 1st
February.

With that in mind, I would like to raise some PRs/issues of interest,
divided into two groups:

(I) PRs that are looking almost ready for merging, or are fixing critical
bugs.
PR #3133 (feature: add libvirt / qemu io bursting)
PR #3126 (Improve System VM startup and memory usage)
PR #3112 (network: Offerings do not have to have Security Grouping enabled)
PR #2795 (KVM: Properly report available memory to Management Server)
PR #3091 (Address reviewers from abandoned PR #1597)
PR #2848 (VMware offline migration)
PR #2983 (KVM live storage migration NFS-NFS)
PR #3122 (Add back ability to disable backup of a snapshot to secondary)
*this PR is targeting 4.11
Additionally, I will open a PR fixing a critical bug in PR #2997, migrating
the template to target local storage if it is not there.

(II) PRs and Issues that are interesting, but the contributors are
unresponsive. Therefore, due to the tight schedule, they are likely going
to be merged into the next LTS. Still, they are worth mentioning and it
would be great if we have a few of these PRs stable to merge in 4.12.
PR #3058 (update dynamic role)
issue #3081 (L2 guest networking via UI)
issue #3068 (some UI additions)
PR #3036 (extra capabilities for VMs snapshots)
issue #3041 (Decision making logic of which Secondary storage to be used
Secondary storage to be used)
issue #3040 (Broadcast URI not set to VXLAN, but VLAN)
PR #2578 (API command to list management servers)
PR #2311 (optimization for applying port forward rules)

I appreciate all the effort that has been put so far. Please feel free to
discuss if you have comments, concerns, or suggestions.

Kind regards,
Gabriel.

Em qui, 3 de jan de 2019 às 14:03, Gabriel Beims Bräscher <
gabrascher@gmail.com> escreveu:

> Thanks for the feedback guys, I really appreciate the help.
>
> Rohit you have a good point. What if we postpone the freezing date to 23rd
> January, and then we can have RC1 until 31st January?
>
> Em qui, 3 de jan de 2019 às 13:21, Simon Weller <sweller@ena.com.invalid>
> escreveu:
>
>> Let us know how we can help Gabriel!
>>
>>
>> ________________________________
>> From: Rohit Yadav <rohit.yadav@shapeblue.com>
>> Sent: Thursday, January 3, 2019 6:03 AM
>> To: dev
>> Subject: Re: Re: [PROPOSE] RM for 4.12
>>
>> Hi Gabriel,
>>
>>
>> You've my full support, let me add you to blueorangutan to kick tests.
>>
>>
>> I've slight objection on the freeze date since people are on holidays and
>> we still have some outstanding PRs to review, and I think we need to fix
>> master branch (which is failing Travis and marvin/trillian smoketests) as
>> early as possible without which it will be difficult to merge outstanding
>> PRs with confidence. I think it may not be practical to have a stable RC1
>> by 18th unless master is stabilized first, then some of the
>> mentioned/outstanding feature PRs are tested and merge. How about moving
>> the freeze date to the end of Jan 2019, while still work towards bugfixing
>> and master stability?
>>
>>
>> Please also check the upgrade paths from 4.11.2.0, 4.11.3.0-SNAPSHOT, I
>> think the paths to 4.11.2.0(-SNAPSHOT) may need fixing appropriately. We
>> also have some criticial VR/systemvmtemplate fixes especially around VMware
>> that we can aim to fix/publish before 4.12.0.0.
>>
>>
>> - Rohit
>>
>> <https://cloudstack.apache.org>
>>
>>
>>
>> ________________________________
>> From: Gabriel Beims Bräscher <gabrascher@gmail.com>
>> Sent: Friday, December 28, 2018 5:55:36 PM
>> To: dev
>> Subject: Re: Re: [PROPOSE] RM for 4.12
>>
>> Hi Haijiao,
>>
>> It would be great to have it. If we get a PR before the release freezing,
>> I
>> have no problem adding it to 4.12.
>>
>> Thanks for the feedback.
>>
>> Em qui, 27 de dez de 2018 às 23:50, Haijiao <18602198181@163.com>
>> escreveu:
>>
>> > Great !
>> >
>> >
>> > Is it possible to add XenServer 7.6 and XCP-ng 7.6 support into ACS
>> 4.12,
>> > though there's no PR to address it yet ?
>> >
>> >
>> > Regards,
>> >
>> >
>> >
>> >
>> > 在2018年12月27 19时02分, "Gabriel Beims Bräscher"<gabrascher@gmail.com>写道:
>> >
>> > Thanks for the feedback, Rafael.
>> >
>> > Updated the PRs/features list:
>> >
>> > I – IPv6 support for Advanced network;
>> >
>> >  I a) ipv6: Calculate IPv6 address instead of fetching one from a pool
>> > #3077 (https://github.com/apache/cloudstack/pull/3077)
>> >
>> >  I b) Refactory VXLAN script and add IPv6 support #3070 (
>> > https://github.com/apache/cloudstack/pull/3070)
>> >
>> > II – UI: Update jquery and related libraries #3069 (
>> > https://github.com/apache/cloudstack/pull/3069)
>> >
>> > III – Data motion new features
>> >
>> >  III a) KVM-Local storage - fixes: (i) migrate template when it does
>> note
>> > exist on target storage, and (ii) enable migrations with TLS connection;
>> >
>> >  III b) KVM live storage migration intra-cluster from NFS source and
>> > destination #2983 (https://github.com/apache/cloudstack/pull/2983)
>> >
>> >  III c) Vmware offline migration #2848 (
>> > https://github.com/apache/cloudstack/pull/2848)
>> >
>> > IV – Add Influxdb to StatsCollector #3078 (
>> > https://github.com/apache/cloudstack/pull/3078)
>> >
>> > V – Add command to list management servers #2578 (
>> > https://github.com/apache/cloudstack/pull/2578)
>> >
>> > Em qua, 26 de dez de 2018 às 11:25, Rafael Weingärtner <
>> > rafaelweingartner@gmail.com> escreveu:
>> >
>> > > It sounds like a plan.
>> > >
>> > > Reading through your suggested PRs (from the backlog we have), I
>> noticed
>> > > something though. The PR (
>> https://github.com/apache/cloudstack/pull/2997
>> > )
>> > > that has been merged introduced a bug in its feature (as we discussed
>> > last
>> > > week). Therefore, you need to add the fix for this bug in the list as
>> > well.
>> > >
>> > > On Wed, Dec 26, 2018 at 9:48 AM Gabriel Beims Bräscher <
>> > > gabrascher@gmail.com>
>> > > wrote:
>> > >
>> > > > Hi All,
>> > > >
>> > > >
>> > > > It has been one year since we started discussing the 4.11 release,
>> > which
>> > > > was released on 12 February 2018. Additionally, 4.11 LTS is
>> supported
>> > > until
>> > > > 1st July 2019 [1]; the next release will be 4.12, prior to our next
>> LTS
>> > > > (5.0?). With that in mind, I'd like to put myself forward as release
>> > > > manager for 4.12. Please feel free to discuss if you have comments
>> or
>> > > > concerns.
>> > > >
>> > > >
>> > > > Here is the plan:
>> > > >
>> > > > 1. The freeze date for the 4.12.0.0 will be at the 12th of January
>> > 2019.
>> > > >
>> > > > 2. After the freeze date (12th Jan), features will not be allowed
on
>> > > > 4.12.0.0 and fixes only if addressing blocker issues. Fixes for
>> other
>> > > > issues will be individually judged on their merit and risk.
>> > > >
>> > > > 3. RM will triage/report critical and blocker bugs for 4.12 and
>> > encourage
>> > > > people to get them fixed.
>> > > >
>> > > > 4. RM will create RCs and start voting once blocker bugs are cleared
>> > and
>> > > > baseline smoke test results are on par with previous smoke test
>> > results.
>> > > >
>> > > > 5. RM will allocate at least a week for branch stabilization and
>> > testing.
>> > > > At the earliest, on 18th January, RM will put 4.12.0.0-rc1 for
>> voting
>> > > from
>> > > > the 4.12.0.0 branch, and master will be open to accepting new
>> features.
>> > > >
>> > > > 6. RM will repeat 3-5 as required. Voting/testing of -rc2, -rc3 and
>> so
>> > on
>> > > > will be created as required.
>> > > >
>> > > > 7. Once vote passes - RM will continue with the release procedures
>> [2].
>> > > >
>> > > >
>> > > > I have selected the following pull requests and features to address
>> > some
>> > > > efforts and merge them on 4.12.0.0:
>> > > >
>> > > > I – IPv6 support for Advanced network;
>> > > >
>> > > >   I a) ipv6: Calculate IPv6 address instead of fetching one from a
>> pool
>> > > > #3077 (https://github.com/apache/cloudstack/pull/3077)
>> > > >
>> > > >   I b) Refactory VXLAN script and add IPv6 support #3070 (
>> > > > https://github.com/apache/cloudstack/pull/3070)
>> > > >
>> > > > II – UI: Update jquery and related libraries #3069 (
>> > > > https://github.com/apache/cloudstack/pull/3069)
>> > > >
>> > > > III – Data motion new features
>> > > >
>> > > >   III a) KVM-Local storage (
>> > > https://github.com/apache/cloudstack/pull/2997
>> > > > )
>> > > >
>> > > >   III b) KVM live storage migration intra cluster from NFS source
>> and
>> > > > destination #2983 (https://github.com/apache/cloudstack/pull/2983)
>> > > >
>> > > >   III c) Vmware offline migration #2848 (
>> > > > https://github.com/apache/cloudstack/pull/2848)
>> > > >
>> > > > IV – Add Influxdb to StatsCollector #3078 (
>> > > > https://github.com/apache/cloudstack/pull/3078)
>> > > >
>> > > > V – Add command to list management servers #2578 (
>> > > > https://github.com/apache/cloudstack/pull/2578)
>> > > >
>> > > >
>> > > > Please contribute with your ideas and feedback.
>> > > >
>> > > >
>> > > > Regards,
>> > > >
>> > > > Gabriel.
>> > > >
>> > > >
>> > > > [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
>> > > >
>> > > > [2]
>> > > >
>> >
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedure
>> > > >
>> > >
>> > >
>> > > --
>> > > Rafael Weingärtner
>> > >
>> >
>>
>> rohit.yadav@shapeblue.com
>> www.shapeblue.com<http://www.shapeblue.com>
>> Amadeus House, Floral Street, London  WC2E 9DPUK
>> @shapeblue
>>
>>
>>
>>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message