> Question: I assume the “Current Date” field means forecast date. So to start, it would be the same as the Planned Date and then gets updated if there are changes to the plan. Is that correct? 

 

Yes, that is correct.  I added those at Bill’s suggestion so we can see if we’re on track.

 

       brucej

 

From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com]
Sent: Wednesday, December 5, 2018 3:06 PM
To: Jones, Bruce E <bruce.e.jones@intel.com>; Rowsell, Brent <Brent.Rowsell@windriver.com>; Zhao, Forrest <forrest.zhao@intel.com>; Peters, Matt <Matt.Peters@windriver.com>; Guo, Ruijing <ruijing.guo@intel.com>; Rowsell, Brent <Brent.Rowsell@windriver.com>; Legacy, Allain <Allain.Legacy@windriver.com>; Webster, Steven <Steven.Webster@windriver.com>; Richard, Joseph <Joseph.Richard@windriver.com>; Ho, Teresa <Teresa.Ho@windriver.com>; Bonnell, Patrick <Patrick.Bonnell@windriver.com>; Qin, Kailun <kailun.qin@intel.com>; Le, Huifeng <huifeng.le@intel.com>; Xu, Chenjie <chenjie.xu@intel.com>; Zhao, Forrest <forrest.zhao@intel.com>; Chilcote Bacco, Derek A <derek.a.chilcote.bacco@intel.com>; Zvonar, Bill <Bill.Zvonar@windriver.com>
Cc: starlingx-discuss@lists.starlingx.io
Subject: RE: "Brent's Patch Reduction Plan" - Networking items

 

Hi Bruce,

I added information in the etherpad for the following items:

 

Title: Host State Management

Title: DHCP agent rescheduling / rebalancing

Title:L3 agent rescheduling / rebalancing

Title: Modeling the provider networks in sysinv

Title:  Patching script rework

 

I also moved the last two items to the re-factoring section since they involve STX development versus upstream neutron.

 

Question: I assume the “Current Date” field means forecast date. So to start, it would be the same as the Planned Date and then gets updated if there are changes to the plan. Is that correct?  

 

Thanks,

Ghada

 

From: Jones, Bruce E [mailto:bruce.e.jones@intel.com]
Sent: Wednesday, December 05, 2018 5:08 PM
To: Khalil, Ghada; Rowsell, Brent; Zhao, Forrest; Peters, Matt; Guo, Ruijing; Rowsell, Brent; Legacy, Allain; Webster, Steven; Richard, Joseph; Ho, Teresa; Bonnell, Patrick; Qin, Kailun; Le, Huifeng; Xu, Chenjie; Zhao, Forrest; Chilcote Bacco, Derek A; Zvonar, Bill
Cc: starlingx-discuss@lists.starlingx.io
Subject: "Brent's Patch Reduction Plan" - Networking items

 

I have been working on turning Brent’s plan for patch reduction into actionable work items.

 

As part of this effort, I discussed with Brent, Bill and Derek ways we can improve our tracking.  We agreed to push all tracking out into the open, and until a better tool becomes available, to use Etherpads.

 

You can find the Etherpad for the Networking part of the Patch Reduction Plan here:  https://etherpad.openstack.org/p/stx-openstack-patch-refactoring-neutron.   Please review and update as needed.

 

I have updated this with the latest status I have from Forrest.  I do not have the latest status from the Networking team beyond that, so there may be additional updates needed.

 

I don’t know if we want to track this work within the Networking sub-project or within the distro.openstack sub-project.  I’m setting up a global Etherpad [0] with links to the sub-project pads, so as long as we agree to use these pads I’m not sure it matters which sub-project owns the work.  We will be able to track all of it across the sub-projects.  We should decide, of course.

 

Feedback graciously welcomed!

        Brucej

 

[0] https://etherpad.openstack.org/p/stx-openstack-patch-refactoring