GSOC2019DCN - Revision history

Liangcheng-yu: /* Project Summary Report */

2019-08-29T21:32:58Z

Project Summary Report

← Older revision		Revision as of 21:32, 29 August 2019
Line 183:		Line 183:
	3. Environment helpers: DCN is a cluster of switches and servers connected based on a specific pattern. The project recycled the BCube and FatTree helpers from the previous DCTCP project and created a new data-center module with the implementation of LeafSpine and DCell. Both are common topologies in DCN. (https://gitlab.com/nsnam/ns-3-dev/merge_requests/89)		3. Environment helpers: DCN is a cluster of switches and servers connected based on a specific pattern. The project recycled the BCube and FatTree helpers from the previous DCTCP project and created a new data-center module with the implementation of LeafSpine and DCell. Both are common topologies in DCN. (https://gitlab.com/nsnam/ns-3-dev/merge_requests/89)

	The commits and code patches could be found at GitLab: https://gitlab.com/liangcheng-yu/ns-3-dev		The commits and code patches could be found at GitLab: https://gitlab.com/liangcheng-yu/ns-3-dev, specifically dcn, scheduling, load-balancing branches.

Liangcheng-yu: /* Phase 2 */

2019-08-29T21:32:18Z

Phase 2

← Older revision		Revision as of 21:32, 29 August 2019
Line 36:		Line 36:
	* Implement the per-flow ECMP [RFC 2992] with the corresponding example, documentation.		* Implement the per-flow ECMP [RFC 2992] with the corresponding example, documentation.
	* Implement the flowlet-switching load balancing algorithm with the corresponding example, documentation.		* Implement the flowlet-switching load balancing algorithm with the corresponding example, documentation.
			* Implement Shortest Job First scheduling.

	===Phase 3===		===Phase 3===

Liangcheng-yu: /* Phase 3 */

2019-08-29T21:31:45Z

Phase 3

← Older revision		Revision as of 21:31, 29 August 2019
Line 38:		Line 38:

	===Phase 3===		===Phase 3===
			* Recycle BCube, FatTree and add the implementation of DCell topology.
	* Example program(s) for data center networking simulation in NS-3, and create a comprehensive dcn simulation example combining congestion control, load balancing, scheduling for DCN aligning with a representative work (Sigcomm/NSDI) in this domain.		* Example program(s) for data center networking simulation in NS-3, and create a comprehensive dcn simulation example combining congestion control, load balancing, scheduling for DCN aligning with a representative work (Sigcomm/NSDI) in this domain.
	* Buffer time to create the patch for merging or other new targets detected for NS3-DCN.

	= Weekly Plan =		= Weekly Plan =

Liangcheng-yu: /* Phase 2 */

2019-08-29T21:31:07Z

Phase 2

← Older revision		Revision as of 21:31, 29 August 2019
Line 35:		Line 35:
	===Phase 2===		===Phase 2===
	* Implement the per-flow ECMP [RFC 2992] with the corresponding example, documentation.		* Implement the per-flow ECMP [RFC 2992] with the corresponding example, documentation.
	* Implement the flowlet-switching load balancing algorithm ~~[CONGA, Sigcomm '14]~~ with the corresponding example, documentation.		* Implement the flowlet-switching load balancing algorithm with the corresponding example, documentation.

	===Phase 3===		===Phase 3===

Liangcheng-yu: /* Project Summary Report */

2019-08-26T00:21:52Z

Project Summary Report

← Older revision		Revision as of 00:21, 26 August 2019
Line 180:		Line 180:
	2. Load balancing options: This section extends the existing NS-3 option per packet ECMP to another two path selection algorithms, namely flow based ECMP and simple flowlet switching. This would allow the packets to be distributed not only based on a per-packet manner, but also at the level of flow entity or flowlet entity. (https://gitlab.com/nsnam/ns-3-dev/merge_requests/81)		2. Load balancing options: This section extends the existing NS-3 option per packet ECMP to another two path selection algorithms, namely flow based ECMP and simple flowlet switching. This would allow the packets to be distributed not only based on a per-packet manner, but also at the level of flow entity or flowlet entity. (https://gitlab.com/nsnam/ns-3-dev/merge_requests/81)

	3. Environment helpers: DCN is a cluster of switches and servers connected based on a specific pattern. The project recycled the BCube and FatTree helpers from the previous DCTCP project and created a new data-center module with the implementation of LeafSpine and DCell. Both are common ~~environment helpers~~ in DCN. (https://gitlab.com/nsnam/ns-3-dev/merge_requests/89)		3. Environment helpers: DCN is a cluster of switches and servers connected based on a specific pattern. The project recycled the BCube and FatTree helpers from the previous DCTCP project and created a new data-center module with the implementation of LeafSpine and DCell. Both are common topologies in DCN. (https://gitlab.com/nsnam/ns-3-dev/merge_requests/89)

	The commits and code patches could be found at GitLab: https://gitlab.com/liangcheng-yu/ns-3-dev		The commits and code patches could be found at GitLab: https://gitlab.com/liangcheng-yu/ns-3-dev

Liangcheng-yu: /* Project Summary Report */

2019-08-26T00:20:39Z

Project Summary Report

← Older revision		Revision as of 00:20, 26 August 2019
Line 176:		Line 176:
	The project could be therefore summarized into three dimentions:		The project could be therefore summarized into three dimentions:

	1. DCN scheduling: This includes the ideal Shortest Job First algorithm in SjfQueueDisc and the realistic Multi-Level Feedback Queue in MlfqQueueDisc. Both scheduling algorithms could be applied to prioritize short flows and therefore optimize the average flow completion time in DCN, which is one of the core metrics to evaluate the DCN system design. [https://gitlab.com/nsnam/ns-3-dev/merge_requests/75]		1. DCN scheduling: This includes the ideal Shortest Job First algorithm in SjfQueueDisc and the realistic Multi-Level Feedback Queue in MlfqQueueDisc. Both scheduling algorithms could be applied to prioritize short flows and therefore optimize the average flow completion time in DCN, which is one of the core metrics to evaluate the DCN system design. (https://gitlab.com/nsnam/ns-3-dev/merge_requests/75)

	2. Load balancing options: This section extends the existing NS-3 option per packet ECMP to another two path selection algorithms, namely flow based ECMP and simple flowlet switching. This would allow the packets to be distributed not only based on a per-packet manner, but also at the level of flow entity or flowlet entity. [https://gitlab.com/nsnam/ns-3-dev/merge_requests/81]		2. Load balancing options: This section extends the existing NS-3 option per packet ECMP to another two path selection algorithms, namely flow based ECMP and simple flowlet switching. This would allow the packets to be distributed not only based on a per-packet manner, but also at the level of flow entity or flowlet entity. (https://gitlab.com/nsnam/ns-3-dev/merge_requests/81)

	3. Environment helpers: DCN is a cluster of switches and servers connected based on a specific pattern. The project recycled the BCube and FatTree helpers from the previous DCTCP project and created a new data-center module with the implementation of LeafSpine and DCell. Both are common environment helpers in DCN. [https://gitlab.com/nsnam/ns-3-dev/merge_requests/89]		3. Environment helpers: DCN is a cluster of switches and servers connected based on a specific pattern. The project recycled the BCube and FatTree helpers from the previous DCTCP project and created a new data-center module with the implementation of LeafSpine and DCell. Both are common environment helpers in DCN. (https://gitlab.com/nsnam/ns-3-dev/merge_requests/89)

	The commits and code patches could be found at GitLab: https://gitlab.com/liangcheng-yu/ns-3-dev		The commits and code patches could be found at GitLab: https://gitlab.com/liangcheng-yu/ns-3-dev

Liangcheng-yu: /* Project Summary Report */

2019-08-26T00:20:19Z

Project Summary Report

← Older revision		Revision as of 00:20, 26 August 2019
Line 176:		Line 176:
	The project could be therefore summarized into three dimentions:		The project could be therefore summarized into three dimentions:

	1. DCN scheduling: This includes the ideal Shortest Job First algorithm in SjfQueueDisc and the realistic Multi-Level Feedback Queue in MlfqQueueDisc. Both scheduling algorithms could be applied to prioritize short flows and therefore optimize the average flow completion time in DCN, which is one of the core metrics to evaluate the DCN system design.		1. DCN scheduling: This includes the ideal Shortest Job First algorithm in SjfQueueDisc and the realistic Multi-Level Feedback Queue in MlfqQueueDisc. Both scheduling algorithms could be applied to prioritize short flows and therefore optimize the average flow completion time in DCN, which is one of the core metrics to evaluate the DCN system design. [https://gitlab.com/nsnam/ns-3-dev/merge_requests/75]

	2. Load balancing options: This section extends the existing NS-3 option per packet ECMP to another two path selection algorithms, namely flow based ECMP and simple flowlet switching. This would allow the packets to be distributed not only based on a per-packet manner, but also at the level of flow entity or flowlet entity.		2. Load balancing options: This section extends the existing NS-3 option per packet ECMP to another two path selection algorithms, namely flow based ECMP and simple flowlet switching. This would allow the packets to be distributed not only based on a per-packet manner, but also at the level of flow entity or flowlet entity. [https://gitlab.com/nsnam/ns-3-dev/merge_requests/81]

	3. Environment helpers: DCN is a cluster of switches and servers connected based on a specific pattern. The project recycled the BCube and FatTree helpers from the previous DCTCP project and created a new data-center module with the implementation of LeafSpine and DCell. Both are common environment helpers in DCN.		3. Environment helpers: DCN is a cluster of switches and servers connected based on a specific pattern. The project recycled the BCube and FatTree helpers from the previous DCTCP project and created a new data-center module with the implementation of LeafSpine and DCell. Both are common environment helpers in DCN. [https://gitlab.com/nsnam/ns-3-dev/merge_requests/89]

	The commits and code patches could be found at GitLab: https://gitlab.com/liangcheng-yu/ns-3-dev		The commits and code patches could be found at GitLab: https://gitlab.com/liangcheng-yu/ns-3-dev

Liangcheng-yu: /* Project Summary Report */

2019-08-26T00:15:59Z

Project Summary Report

← Older revision		Revision as of 00:15, 26 August 2019
Line 177:		Line 177:

	1. DCN scheduling: This includes the ideal Shortest Job First algorithm in SjfQueueDisc and the realistic Multi-Level Feedback Queue in MlfqQueueDisc. Both scheduling algorithms could be applied to prioritize short flows and therefore optimize the average flow completion time in DCN, which is one of the core metrics to evaluate the DCN system design.		1. DCN scheduling: This includes the ideal Shortest Job First algorithm in SjfQueueDisc and the realistic Multi-Level Feedback Queue in MlfqQueueDisc. Both scheduling algorithms could be applied to prioritize short flows and therefore optimize the average flow completion time in DCN, which is one of the core metrics to evaluate the DCN system design.

	2. Load balancing options: This section extends the existing NS-3 option per packet ECMP to another two path selection algorithms, namely flow based ECMP and simple flowlet switching. This would allow the packets to be distributed not only based on a per-packet manner, but also at the level of flow entity or flowlet entity.		2. Load balancing options: This section extends the existing NS-3 option per packet ECMP to another two path selection algorithms, namely flow based ECMP and simple flowlet switching. This would allow the packets to be distributed not only based on a per-packet manner, but also at the level of flow entity or flowlet entity.

	3. Environment helpers: DCN is a cluster of switches and servers connected based on a specific pattern. The project recycled the BCube and FatTree helpers from the previous DCTCP project and created a new data-center module with the implementation of LeafSpine and DCell. Both are common environment helpers in DCN.		3. Environment helpers: DCN is a cluster of switches and servers connected based on a specific pattern. The project recycled the BCube and FatTree helpers from the previous DCTCP project and created a new data-center module with the implementation of LeafSpine and DCell. Both are common environment helpers in DCN.

	The commits and code patches could be found at GitLab: https://gitlab.com/liangcheng-yu/ns-3-dev		The commits and code patches could be found at GitLab: https://gitlab.com/liangcheng-yu/ns-3-dev

Liangcheng-yu: /* Project Summary Report */

2019-08-26T00:15:48Z

Project Summary Report

← Older revision		Revision as of 00:15, 26 August 2019
Line 170:		Line 170:

	= Project Summary Report =		= Project Summary Report =

			This project looks at supporting data center networking (DCN) simulation with NS-3. It will allow the users to evaluate DCN proposals with NS-3 more effectively.
			In the project I have added the scheduling algorithms (Shortest Job First and Multi-Level Feedback Queue), the common data center networking topology helpers, and extending NS-3 for common load balancing options, such as per-flow ECMP and flowlet switching.

			The project could be therefore summarized into three dimentions:

			1. DCN scheduling: This includes the ideal Shortest Job First algorithm in SjfQueueDisc and the realistic Multi-Level Feedback Queue in MlfqQueueDisc. Both scheduling algorithms could be applied to prioritize short flows and therefore optimize the average flow completion time in DCN, which is one of the core metrics to evaluate the DCN system design.
			2. Load balancing options: This section extends the existing NS-3 option per packet ECMP to another two path selection algorithms, namely flow based ECMP and simple flowlet switching. This would allow the packets to be distributed not only based on a per-packet manner, but also at the level of flow entity or flowlet entity.
			3. Environment helpers: DCN is a cluster of switches and servers connected based on a specific pattern. The project recycled the BCube and FatTree helpers from the previous DCTCP project and created a new data-center module with the implementation of LeafSpine and DCell. Both are common environment helpers in DCN.

			The commits and code patches could be found at GitLab: https://gitlab.com/liangcheng-yu/ns-3-dev

Liangcheng-yu: /* Weekly Progress */

2019-08-25T15:29:20Z

Weekly Progress

← Older revision		Revision as of 15:29, 25 August 2019
Line 157:		Line 157:
	* The full commit to recycle the Bcube helper and Fat Tree into the data-center module is completed.		* The full commit to recycle the Bcube helper and Fat Tree into the data-center module is completed.

			===Week10 July 29 - August 4 ===
			* Created a DCN simulation example that covers a typical DCN simulation practice.
			* Implemented the DCell helper.

			===Week11 August 5 - August 11 ===
			* Fixed issues of the DCell implementation.
			* Packed up the topology helpers and the full DCN simulation example as a MR.

			===Week12 August 12 - August 19 ===
			* Fixed the data-center module.
			* Completed the final evaluation.

	= Project Summary Report =		= Project Summary Report =