Changes between Version 15 and Version 16 of GEC25Agenda/Demos

Timestamp:

03/01/17 10:57:14 (7 years ago)

Author:

lnevers@bbn.com

Comment:

--

GEC25Agenda/Demos

@@ -11 +11 @@
 Tuesday March 14: 05:30pm - 07:30pm
 
+[[PageOutline]]
 
 = Demo Night !Agenda/Speakers =
@@ -71 +72 @@
 
 This demonstration will showcase a novel, dynamically adaptable networked cloud infrastructure driven by the demand of a data-driven scientific workflow. It will use resources from ExoGENI. The demo will run on dynamically provisioned 'slices' spanning multiple ExoGENI racks that are interconnected using dynamically provisioned connections from Internet2 and ESnet. We will show how a virtual Software Defined Exchange (SDX) platform, instantiated on ExoGENI, provides additional functionality for management of scientific workflows. Using the virtual SDX slice, we will demonstrate how tools developed in the DoE Panorama project can enable the Pegasus Workflow Management System to monitor and manipulate network connectivity and performance between sites, pools, and tasks within a workflow. We will use a representative, data-intensive genome science workflow as a driving use case to showcase the above capabilities.
+
 == Steroid OpenFlow Service ==
 
-__Authors:__
+__Authors:__ Ryan Izard, Junaid Zulfiqar, Khayam Anjam, Caleb Linduff - Clemson University 
+
+With the recent rise in cloud computing, applications are routinely accessing and interacting with data on remote resources. As data sizes become increasingly large, often combined with their locations being far from the applications, the well known impact of lower TCP throughput over large delay bandwidth product paths becomes more significant to these applications. While myriads of solutions exist to alleviate the problem, they require specialized software at both the application host and the remote data server, making it hard to scale up to a large range of applications and execution environments. Steroid OpenFlow Service (SOS) is a scalable, SDN-based network service that can transparently improve the performance of TCP-based data transfers. We will demonstrate the simplicity and scalability of the SOS architecture and how it can be flexibly deployed to to improve TCP data transfers across experimental, virtual cloud-based, and even production network environments.
 
 == GENI Wireless Testbed: A flexible open ecosystem for wireless communications research ==
@@ -122 +126 @@
 
 "Data centers are massive infrastructures that host today’s internet and cloud services.  A typical data center is consuming around energy budget of 25000 households and almost about 200 times electricity than that of a standard office space [1].  This massive amount of energy motivated a growing interest in using green renewable energy at data centers. Google is planning to provide 100% of electricity supplies for its data centers and offices using the wind and solar power by the end of 2017 [2]. 
-The amount of renewable energy that can be generated in data centers depends on their location and time. We introduce a Green Energy Aware SDN platform with an SDN controller, that schedules client requests to servers depending on delay and the current renewable energy generated at the data centers. In this work, we adopt National Solar Radiation Database (NSRDB), maintained by National Renewable Energy Laboratory (NREL) to estimate the amount of solar renewable energy that can be generated in each data center. Our platform can be used for scheduling client requests not solely based on green energy, but other parameters from data centers (e.g. CPU utilization, delay requirements).
-[1]     M. Poess and R. O. Nambiar, “Energy Cost, the Key Challenge of Today’s Data Centers: A Power Consumption Analysis of TPC-C Results,” Proc VLDB Endow, vol. 1, no. 2, pp. 1229–1240, Aug. 2008.
-[2]     “We’re set to reach 100% renewable energy — and it’s just the beginning,” Google, 06-Dec-2016. [Online]. Available: http://blog.google:443/topics/environment/100-percent-renewable-energy/. [Accessed: 22-Feb-2017]."
+The amount of renewable energy that can be generated in data centers depends on their location and time. We introduce a Green Energy Aware SDN platform with an SDN controller, that schedules client requests to servers depending on delay and the current renewable energy generated at the data centers. In this work, we adopt National Solar Radiation Database (NSRDB), maintained by National Renewable Energy Laboratory (NREL) to estimate the amount of solar renewable energy that can be generated in each data center. Our platform can be used for scheduling client requests not solely based on green energy, but other parameters from data centers (e.g. CPU utilization, delay requirements).[1]    M. Poess and R. O. Nambiar, “Energy Cost, the Key Challenge of Today’s Data Centers: A Power Consumption Analysis of TPC-C Results,” Proc VLDB Endow, vol. 1, no. 2, pp. 1229–1240, Aug. 2008. [2]      “We’re set to reach 100% renewable energy — and it’s just the beginning,” Google, 06-Dec-2016. [Online]. Available: http://blog.google:443/topics/environment/100-percent-renewable-energy/. [Accessed: 22-Feb-2017]."
 
 
@@ -131 +133 @@
 __Authors:__ Rick !McGeer, Matt Hemmings, Andy Bavier, Glenn Ricart - US Ignite
 
-"!PlanetIgnite is a general-purpose, Infrastructure-as-a-Service, self-assembling, lightweight edge cloud on virtualized infrastructure with support for single-pane-of-glass distributed application configuration and deployment. This is an entirely new concept. !PlanetLab, GENI, and SAVI are general-purpose IaaS edge clouds, but require top-down installation and dedicated hardware resources at each site and do not offer single- pane-of-glass application deployment. Seattle is a lightweight self-assembling edge cloud that offers single- pane-of-class configuration and control, but developers are restricted to using a subset of Python. !PlanetIgnite is a Containers-as-a-Service Edge Cloud which offers Docker Containers to each !PlanetIgnite user. A !PlanetIgnite node is an off-the-shelf Ubuntu 14.04 Virtual machine with Docker installed, meaning it can be installed on any edge node where a VM with a routable v4 address is available. Adding a PlanetIgnite node to the infrastructure is simple: a site wishing to host a !PlanetIgnite node simply downloads the image; on boot, the new !PlanetIgnite node registers with the !PlanetIgnite portal, which runs a series of acceptance tests. Once complete, the image is registered and the node is added to the set of !PlanetIgnite sites.
+"!PlanetIgnite is a general-purpose, Infrastructure-as-a-Service, self-assembling, lightweight edge cloud on virtualized infrastructure with support for single-pane-of-glass distributed application configuration and deployment. This is an entirely new concept. !PlanetLab, GENI, and SAVI are general-purpose IaaS edge clouds, but require top-down installation and dedicated hardware resources at each site and do not offer single- pane-of-glass application deployment. Seattle is a lightweight self-assembling edge cloud that offers single- pane-of-class configuration and control, but developers are restricted to using a subset of Python. !PlanetIgnite is a Containers-as-a-Service Edge Cloud which offers Docker Containers to each !PlanetIgnite user. A !PlanetIgnite node is an off-the-shelf Ubuntu 14.04 Virtual machine with Docker installed, meaning it can be installed on any edge node where a VM with a routable v4 address is available. Adding a !PlanetIgnite node to the infrastructure is simple: a site wishing to host a !PlanetIgnite node simply downloads the image; on boot, the new !PlanetIgnite node registers with the !PlanetIgnite portal, which runs a series of acceptance tests. Once complete, the image is registered and the node is added to the set of !PlanetIgnite sites.
 "