Slides for a general webinar about BonFIRE, the features offered, the sites making up this multi-site testbed and the tools available for experimenters using the facility.
A video with audio is available on YouTube: http://youtu.be/0ulgvs32wvI
OSDC 2014: Nat Morris - Open Network Install EnvironmentNETWAYS
ONIE defines an open source “install environment” that runs on this management subsystem utilizing facilities in a Linux/BusyBox environment. This environment allows end-users and channel partners to install the target network OS as part of data center provisioning, in the fashion that servers are provisioned.
ONIE enables switch hardware suppliers, distributors and resellers to manage their operations based on a small number of hardware SKUs. This in turn creates economies of scale in manufacturing, distribution, stocking, and RMA enabling a thriving ecosystem of both network hardware and operating system alternatives.
The document provides information on installing and using openMANO, an open source platform for network functions virtualization management and orchestration. It describes:
1. The requirements to run openMANO including compute nodes, storage, and OpenFlow controller.
2. The different modes openMANO can run in including normal, host-only, development, and test modes.
3. How to install openMANO either automatically through scripts or manually by downloading packages and configuring components.
ONIE (Open Network Install Environment) provides an environment for installing network operating systems on bare-metal switches. It is implemented using a Linux kernel and BusyBox. ONIE configures the management interfaces and locates and executes OS installers from the network or USB. It allows choice of hardware vendors, operating system vendors, and provides multi-vendor interoperability. ONIE is an open source project within the Open Compute Project.
Wherein I install OpenWRT on to an inexpensive TP-Link pocket router, install perl and attempt to smoke CPAN.
I also introduce OpenWRT in possibly too much detail, and dont really explain what smoking CPAN is.
The document discusses installing and configuring Firebird on Linux. It describes installing from project packages such as RPM and tar.gz files, from distribution packages, or by building from source code. It also covers configuring services for classic or superserver modes using xinetd or systemd, checking the max open file settings, and optimizing the file system choices and settings.
ONIE (Open Network Install Environment) is an open source project that provides a common installation environment for network operating systems on bare-metal switches. It addresses challenges of each hardware platform requiring a unique OS installation process. ONIE is pre-installed on switches and implements network OS installation through a small Linux-based system. It enables an open ecosystem where end users can choose different OSs and hardware vendors can support multiple OSs on a single platform.
OSDC 2014: Nat Morris - Open Network Install EnvironmentNETWAYS
ONIE defines an open source “install environment” that runs on this management subsystem utilizing facilities in a Linux/BusyBox environment. This environment allows end-users and channel partners to install the target network OS as part of data center provisioning, in the fashion that servers are provisioned.
ONIE enables switch hardware suppliers, distributors and resellers to manage their operations based on a small number of hardware SKUs. This in turn creates economies of scale in manufacturing, distribution, stocking, and RMA enabling a thriving ecosystem of both network hardware and operating system alternatives.
The document provides information on installing and using openMANO, an open source platform for network functions virtualization management and orchestration. It describes:
1. The requirements to run openMANO including compute nodes, storage, and OpenFlow controller.
2. The different modes openMANO can run in including normal, host-only, development, and test modes.
3. How to install openMANO either automatically through scripts or manually by downloading packages and configuring components.
ONIE (Open Network Install Environment) provides an environment for installing network operating systems on bare-metal switches. It is implemented using a Linux kernel and BusyBox. ONIE configures the management interfaces and locates and executes OS installers from the network or USB. It allows choice of hardware vendors, operating system vendors, and provides multi-vendor interoperability. ONIE is an open source project within the Open Compute Project.
Wherein I install OpenWRT on to an inexpensive TP-Link pocket router, install perl and attempt to smoke CPAN.
I also introduce OpenWRT in possibly too much detail, and dont really explain what smoking CPAN is.
The document discusses installing and configuring Firebird on Linux. It describes installing from project packages such as RPM and tar.gz files, from distribution packages, or by building from source code. It also covers configuring services for classic or superserver modes using xinetd or systemd, checking the max open file settings, and optimizing the file system choices and settings.
ONIE (Open Network Install Environment) is an open source project that provides a common installation environment for network operating systems on bare-metal switches. It addresses challenges of each hardware platform requiring a unique OS installation process. ONIE is pre-installed on switches and implements network OS installation through a small Linux-based system. It enables an open ecosystem where end users can choose different OSs and hardware vendors can support multiple OSs on a single platform.
The document discusses Cumulus Linux, an open-source network operating system that allows network switches to be managed like Linux servers. It can be installed on switches using ONIE (Open Network Install Environment) and configured via Zero Touch Provisioning (ZTP) using scripts. Ifupdown2 is introduced as the new interface configuration manager for Cumulus Linux, which handles dependencies and allows templates to configure many interfaces at once.
XPDS14 - Towards Massive Server Consolidation - Filipe Manco, NECThe Linux Foundation
In recent years Xen has seen the development of many minimalistic or specialized virtual machines (e.g., OSv, Mirage, ClickOS, Erlang on Xen, etc.). Thanks in part to a small CPU and memory footprints, these VMs allow for running thousands or more on a single, inexpensive commodity server. Doing so could save cloud and network operators vast amounts of money.
Attempts to do so are already underway and have discovered important bottlenecks in Xen. While some of these have already been addressed by the community (e.g., limited number of event channels or memory grants) others still remain. In this talk we describe our experience when trying to run up to 10,000 MiniOS-based VMs, including bottlenecks in the XenStore, toolchain and network pipe. We further report on prototypical solutions, and on our implementation of suspend/resume for MiniOS that allows us tens of milliseconds migrations.
XPDS14 - Zero-Footprint Guest Memory Introspection from Xen - Mihai Dontu, Bi...The Linux Foundation
This presentation will detail a practical approach to memory introspection of virtual machines running on the Xen hypervisor with no in-guest footprint. The functionality makes use of the mem-event API with a number of improvements which enable the proper tracking of guest OS activity. The technology created on top of this Xen API opens the door for several immediate applications, including: rootkit detection and prevention, detection and action on several categories of malware, and event source information for low-level post-event forensics and correlation based on real event data during events.
Presentation delivered at LinuxCon China 2016
UEFI HTTP/HTTPS Boot is a new feature of UEFI 2.5+. In the meantime, this feature is not yet implemented in any Linux bootloader. This Birds of a Feather session will give an introduction to UEFI HTTP/HTTPS Boot, and share a proof-of-concept implementation based on grub2 that works on both the emulator (QEMU/OVMF) and HPE ProLiant Gen10 servers.
For HTTPS, the experience and comparison will be shared between the purely software-based and UEFI-based implementations in the aspects of ease of implementation, security strength, and limitation.
Presentation from 2008. Compares Lighttpd .vs Apache for static content. Discovery session for scaling http://www.imagesocket.com during it's peak popularity.
This is really old and /outdated/ at this point.
LCNA14: Why Use Xen for Large Scale Enterprise Deployments? - Konrad Rzeszute...The Linux Foundation
For many years, the Xen community has been delivering a solid virtualization platform for the enterprise. In support of the Xen community innovation effort, Oracle has been translating our enterprise experience with mission-critical workloads and large-scale infrastructure deployments into upstream contributions for the Linux and Xen efforts. In this session, you'll hear from a key Oracle expert, and community member, about Oracle contributions that focus on large-scale Xen deployments, networking, PV drivers, new PVH architecture, performance enhancements, dynamic memory usage with ‘tmem', and much more. This is your chance to get an under the hood view and see why the Xen architecture is the ideal choice for the enterprise.
Cobbler - Fast and reliable multi-OS provisioningRUDDER
In a lot of companies, machine deployment is a delicate subject: every administrator has his own recipe, using CD-ROMs, static binary images deployed via the network, peer delegation ...
However, one solution makes the consensus when it comes to automated mass deployments ( except in the Cloud ): PXE boot. The main cons are that the deployment and the management of such a service is a pain, and every OS has its own installation automation system.
This is where Cobbler saves the day: it enables a painless and reliably to create a PXE service, usable on either virtual or physical machines, while beeing the most agnostic possible towards the target OSes and its preconfiguration system (preseed, kickstart, sysprep, ...) while offering the possibility to handle lots of configuration parameters in a modular fashion (network, partitionning, user accounts, configuration management agent...)
This conference aims to introduce the audience to the general concepts of Cobbler, and some scenarios where it would be a useful solution.
This document discusses IP over InfiniBand (IPoIB), which allows IP applications to run over an InfiniBand fabric. It provides the benefits of socket-based applications running transparently and supporting network interface offloads. While IPoIB provides IP services, it has limitations as a non-standard Ethernet interface and cannot be used in virtualized environments that expect Ethernet frames. The document introduces the eIPoIB solution, which creates a standard Ethernet network device interface that maps to the underlying IPoIB interface. eIPoIB addresses limitations by encapsulating packets in Ethernet frames and supporting standard Ethernet operations and networking models for virtualization.
Here are the answers to your questions:
1. Daemon process runs in the background, like httpd, sshd. Subprocess is created by daemon using fork, like httpd spawns child processes to handle requests.
2. TUI stands for Text-based User Interface, like the interface provided by tools like gdb, git when used with --tui option.
3. Apache supports various languages as modules like PHP, Perl, Python etc. using modules like mod_php, mod_perl, mod_python.
4. The Linux kernel firewall is called iptables.
5. To quickly create a daemon service, add the startup script/command to /etc/init.d/rc.local
"One network to rule them all" - OpenStack Summit Austin 2016Phil Estes
Presentation at IBM Client Day by Kyle Mestery and Phil Estes, OpenStack Summit 2016 - Austin, Texas on April 26, 2016. "Open, Scalable and Integrated Networking for Containers and VMs" covering Project Kuryr, Docker's libnetwork, and Neutron & OVS and OVN network stacks
XPDS16: Xen Orchestra: building a Cloud on top of Xen - Olivier Lambert & Jul...The Linux Foundation
Since its inception, the Xen Orchestra project which uses AGPLv3, always had a philosophy to listen and engage the community. User feedback shaped our initial concept, which first targeted system administrators. Eventually, our users drove us to support cloud-scale deployments supporting up to 2000 VM's. Retaining simplicity in usage and installation, while evolving Xen Orchestra to cloud scale posed many challenges. This led us to build many new features such ACLs, self-service, live charts, config drive management, and more, forced us to constantly evolve our architecture. First we will show how user needs changed our architecture, and how we implemented challenging problems such as user permissions, ACLs, Containers in a virtualized infrastructure and self service. We will conclude with a short demo, what is next and a lessons learned.
This document discusses using Ironic to deploy Windows on bare metal servers. Ironic is OpenStack's bare metal provisioning service that allows physical servers to be provisioned like virtual machines. The document outlines how Ironic handles disk-based Windows images differently than partition-based Linux images. It also describes the deployment process for Windows, which involves PXE booting to instruct the server to boot from its local disk where the Windows image has been written, unlike Linux which uses PXE to provide the kernel and ramdisk for deployment. The document lists several areas of work around improving Windows support in Ironic and related projects like TripleO.
PVH allows a paravirtualized Linux guest to run in ring 0 by using a hardware-assisted virtualization technique called PVH. PVH combines aspects of para-virtualization (PV) and hardware virtualization (HVM) by using a PV entry point to boot the guest faster while still allowing the guest kernel to run in ring 0. Performance benchmarks show that PVH provides significant performance improvements over traditional PV guests, bringing performance closer to HVM while still maintaining the security model of PV. However, some optimizations remain to be done to match the performance of pure PV or HVM guests.
The linux kernel hidden inside windows 10mark-smith
The document discusses the architectural overview of the Linux kernel hidden inside Windows 10. It describes the components that enable running Linux processes as "Pico processes" inside Windows, including the LXCORE kernel driver that implements the Linux ABI and API, and the LXSSMANAGER user-mode service that provides the external interface. The document outlines the initialization and functionality of these components, such as how they implement system calls, virtual file systems, and inter-process communication between Linux and Windows processes.
We discuss the existing and new hardware virtualization features. First, we review the existing hardware features that are not used by Xen today, showing examples for use cases. 1) For example, The "descriptor-table exiting" should be useful for the guest kernels or security agent to enhance security features. 2) The VMX-preemption timer allows the hypervisor to preempt guest VM execution after a specified amount of time, which is useful to implement fair scheduling. The hardware can save the timer value on each successive VMexit, after setting the initial VM quantum. 3) VMFUNC is an operation provided by the processor that can be invoked from VMX non-root operation without a VM exit. Today, EPTP switching is available, and we discuss how we can use the feature. Second, we talk about new hardware features, especially for interrupt optimizations.
Deployment of WebObjects applications on CentOS LinuxWO Community
With the rise of cloud computing and the death of the Xserve, learn how you can deploy your WebObjects applications on a CentOS server. You will also get tips about how to secure your server so that you don't get hack.
XPDS16: libvirt and Tools: What's New and What's Next - James Fehlig, SUSEThe Linux Foundation
A year has passed since the last Xen Developer Summit and it is time to announce the quiet progress made on the libvirt libxl driver and related tooling. New features include memory, cpu, block device, and network interface statistics reporting, support for pvUSB, support for migration stream V2, peer-to-peer migration, UEFI for HVM guests via OVMF, and domain capabilities reporting to name a few. There are also many noteworthy improvements such as better conversion of xl.cfg to/from libvirt domXML, allowing users to easily switch between the xl+libxl and libvirt+libxl toolstacks.
The summit also provides an opportunity to discuss new proposals such as better control of domain placement on NUMA systems, exposing Xen's cpu pool feature in libvirt, supporting non-volatile memory for UEFI variables, and improved capabilities reporting.
Much of libvirt's value for Xen is in the tools built upon it: virt-manager, virt-viewer, virt-install, virt-builder, kimchi, OpenStack nova, etc. These tools also deserve a quick status update as they relate to Xen.
The audience is encouraged to participate, e.g. by requesting a sorely missing feature, warning of an upcoming Xen change that may affect libvirt, or simply suggesting a change that makes virtualization management life a bit easier.
Kdump is a long existing method for acquiring dump of crashed kernel, however very few literatures are available to understand it's usage and internals. We receive a lot of queries on kexec mailing list about different issues related to the kexec/kdump environment.
In this presentation, we talk about basics of kdump usage and some internals about kdump/kexec kernel implementation. It includes end to end flow from kdump kernel configuration to crash analysis. We discuss some of the problem which is frequently faced by kdump users. It also includes related information about ELF structure, so that one can debug if vmcore itself gets corrupted because of any architecture related issue.
This document summarizes a project that investigated air leakage in large buildings in Minnesota. Air leakage tests were conducted on 6 buildings before and after air sealing. On average, air sealing reduced leakage by 10%. Tests found that buildings were 84% tighter than average US buildings, possibly due to the cold climate. Pressurization tests found greater air leakage than depressurization by 22% on average. Mechanical systems were found to increase total building leakage by 15-119% and have a significant effect on building pressure. Future work will model these effects and develop methods to estimate pressure effects and air sealing savings.
Wind energy has huge potential and is the world's fastest growing energy source. Advances in turbine technology have reduced costs, with wind power now comparable to conventional sources. While intermittent, wind works well paired with hydro or solar and future innovations may address issues like energy storage. Overall, the future of wind energy looks bright as it provides clean power without fuel costs or pollution.
The document discusses Cumulus Linux, an open-source network operating system that allows network switches to be managed like Linux servers. It can be installed on switches using ONIE (Open Network Install Environment) and configured via Zero Touch Provisioning (ZTP) using scripts. Ifupdown2 is introduced as the new interface configuration manager for Cumulus Linux, which handles dependencies and allows templates to configure many interfaces at once.
XPDS14 - Towards Massive Server Consolidation - Filipe Manco, NECThe Linux Foundation
In recent years Xen has seen the development of many minimalistic or specialized virtual machines (e.g., OSv, Mirage, ClickOS, Erlang on Xen, etc.). Thanks in part to a small CPU and memory footprints, these VMs allow for running thousands or more on a single, inexpensive commodity server. Doing so could save cloud and network operators vast amounts of money.
Attempts to do so are already underway and have discovered important bottlenecks in Xen. While some of these have already been addressed by the community (e.g., limited number of event channels or memory grants) others still remain. In this talk we describe our experience when trying to run up to 10,000 MiniOS-based VMs, including bottlenecks in the XenStore, toolchain and network pipe. We further report on prototypical solutions, and on our implementation of suspend/resume for MiniOS that allows us tens of milliseconds migrations.
XPDS14 - Zero-Footprint Guest Memory Introspection from Xen - Mihai Dontu, Bi...The Linux Foundation
This presentation will detail a practical approach to memory introspection of virtual machines running on the Xen hypervisor with no in-guest footprint. The functionality makes use of the mem-event API with a number of improvements which enable the proper tracking of guest OS activity. The technology created on top of this Xen API opens the door for several immediate applications, including: rootkit detection and prevention, detection and action on several categories of malware, and event source information for low-level post-event forensics and correlation based on real event data during events.
Presentation delivered at LinuxCon China 2016
UEFI HTTP/HTTPS Boot is a new feature of UEFI 2.5+. In the meantime, this feature is not yet implemented in any Linux bootloader. This Birds of a Feather session will give an introduction to UEFI HTTP/HTTPS Boot, and share a proof-of-concept implementation based on grub2 that works on both the emulator (QEMU/OVMF) and HPE ProLiant Gen10 servers.
For HTTPS, the experience and comparison will be shared between the purely software-based and UEFI-based implementations in the aspects of ease of implementation, security strength, and limitation.
Presentation from 2008. Compares Lighttpd .vs Apache for static content. Discovery session for scaling http://www.imagesocket.com during it's peak popularity.
This is really old and /outdated/ at this point.
LCNA14: Why Use Xen for Large Scale Enterprise Deployments? - Konrad Rzeszute...The Linux Foundation
For many years, the Xen community has been delivering a solid virtualization platform for the enterprise. In support of the Xen community innovation effort, Oracle has been translating our enterprise experience with mission-critical workloads and large-scale infrastructure deployments into upstream contributions for the Linux and Xen efforts. In this session, you'll hear from a key Oracle expert, and community member, about Oracle contributions that focus on large-scale Xen deployments, networking, PV drivers, new PVH architecture, performance enhancements, dynamic memory usage with ‘tmem', and much more. This is your chance to get an under the hood view and see why the Xen architecture is the ideal choice for the enterprise.
Cobbler - Fast and reliable multi-OS provisioningRUDDER
In a lot of companies, machine deployment is a delicate subject: every administrator has his own recipe, using CD-ROMs, static binary images deployed via the network, peer delegation ...
However, one solution makes the consensus when it comes to automated mass deployments ( except in the Cloud ): PXE boot. The main cons are that the deployment and the management of such a service is a pain, and every OS has its own installation automation system.
This is where Cobbler saves the day: it enables a painless and reliably to create a PXE service, usable on either virtual or physical machines, while beeing the most agnostic possible towards the target OSes and its preconfiguration system (preseed, kickstart, sysprep, ...) while offering the possibility to handle lots of configuration parameters in a modular fashion (network, partitionning, user accounts, configuration management agent...)
This conference aims to introduce the audience to the general concepts of Cobbler, and some scenarios where it would be a useful solution.
This document discusses IP over InfiniBand (IPoIB), which allows IP applications to run over an InfiniBand fabric. It provides the benefits of socket-based applications running transparently and supporting network interface offloads. While IPoIB provides IP services, it has limitations as a non-standard Ethernet interface and cannot be used in virtualized environments that expect Ethernet frames. The document introduces the eIPoIB solution, which creates a standard Ethernet network device interface that maps to the underlying IPoIB interface. eIPoIB addresses limitations by encapsulating packets in Ethernet frames and supporting standard Ethernet operations and networking models for virtualization.
Here are the answers to your questions:
1. Daemon process runs in the background, like httpd, sshd. Subprocess is created by daemon using fork, like httpd spawns child processes to handle requests.
2. TUI stands for Text-based User Interface, like the interface provided by tools like gdb, git when used with --tui option.
3. Apache supports various languages as modules like PHP, Perl, Python etc. using modules like mod_php, mod_perl, mod_python.
4. The Linux kernel firewall is called iptables.
5. To quickly create a daemon service, add the startup script/command to /etc/init.d/rc.local
"One network to rule them all" - OpenStack Summit Austin 2016Phil Estes
Presentation at IBM Client Day by Kyle Mestery and Phil Estes, OpenStack Summit 2016 - Austin, Texas on April 26, 2016. "Open, Scalable and Integrated Networking for Containers and VMs" covering Project Kuryr, Docker's libnetwork, and Neutron & OVS and OVN network stacks
XPDS16: Xen Orchestra: building a Cloud on top of Xen - Olivier Lambert & Jul...The Linux Foundation
Since its inception, the Xen Orchestra project which uses AGPLv3, always had a philosophy to listen and engage the community. User feedback shaped our initial concept, which first targeted system administrators. Eventually, our users drove us to support cloud-scale deployments supporting up to 2000 VM's. Retaining simplicity in usage and installation, while evolving Xen Orchestra to cloud scale posed many challenges. This led us to build many new features such ACLs, self-service, live charts, config drive management, and more, forced us to constantly evolve our architecture. First we will show how user needs changed our architecture, and how we implemented challenging problems such as user permissions, ACLs, Containers in a virtualized infrastructure and self service. We will conclude with a short demo, what is next and a lessons learned.
This document discusses using Ironic to deploy Windows on bare metal servers. Ironic is OpenStack's bare metal provisioning service that allows physical servers to be provisioned like virtual machines. The document outlines how Ironic handles disk-based Windows images differently than partition-based Linux images. It also describes the deployment process for Windows, which involves PXE booting to instruct the server to boot from its local disk where the Windows image has been written, unlike Linux which uses PXE to provide the kernel and ramdisk for deployment. The document lists several areas of work around improving Windows support in Ironic and related projects like TripleO.
PVH allows a paravirtualized Linux guest to run in ring 0 by using a hardware-assisted virtualization technique called PVH. PVH combines aspects of para-virtualization (PV) and hardware virtualization (HVM) by using a PV entry point to boot the guest faster while still allowing the guest kernel to run in ring 0. Performance benchmarks show that PVH provides significant performance improvements over traditional PV guests, bringing performance closer to HVM while still maintaining the security model of PV. However, some optimizations remain to be done to match the performance of pure PV or HVM guests.
The linux kernel hidden inside windows 10mark-smith
The document discusses the architectural overview of the Linux kernel hidden inside Windows 10. It describes the components that enable running Linux processes as "Pico processes" inside Windows, including the LXCORE kernel driver that implements the Linux ABI and API, and the LXSSMANAGER user-mode service that provides the external interface. The document outlines the initialization and functionality of these components, such as how they implement system calls, virtual file systems, and inter-process communication between Linux and Windows processes.
We discuss the existing and new hardware virtualization features. First, we review the existing hardware features that are not used by Xen today, showing examples for use cases. 1) For example, The "descriptor-table exiting" should be useful for the guest kernels or security agent to enhance security features. 2) The VMX-preemption timer allows the hypervisor to preempt guest VM execution after a specified amount of time, which is useful to implement fair scheduling. The hardware can save the timer value on each successive VMexit, after setting the initial VM quantum. 3) VMFUNC is an operation provided by the processor that can be invoked from VMX non-root operation without a VM exit. Today, EPTP switching is available, and we discuss how we can use the feature. Second, we talk about new hardware features, especially for interrupt optimizations.
Deployment of WebObjects applications on CentOS LinuxWO Community
With the rise of cloud computing and the death of the Xserve, learn how you can deploy your WebObjects applications on a CentOS server. You will also get tips about how to secure your server so that you don't get hack.
XPDS16: libvirt and Tools: What's New and What's Next - James Fehlig, SUSEThe Linux Foundation
A year has passed since the last Xen Developer Summit and it is time to announce the quiet progress made on the libvirt libxl driver and related tooling. New features include memory, cpu, block device, and network interface statistics reporting, support for pvUSB, support for migration stream V2, peer-to-peer migration, UEFI for HVM guests via OVMF, and domain capabilities reporting to name a few. There are also many noteworthy improvements such as better conversion of xl.cfg to/from libvirt domXML, allowing users to easily switch between the xl+libxl and libvirt+libxl toolstacks.
The summit also provides an opportunity to discuss new proposals such as better control of domain placement on NUMA systems, exposing Xen's cpu pool feature in libvirt, supporting non-volatile memory for UEFI variables, and improved capabilities reporting.
Much of libvirt's value for Xen is in the tools built upon it: virt-manager, virt-viewer, virt-install, virt-builder, kimchi, OpenStack nova, etc. These tools also deserve a quick status update as they relate to Xen.
The audience is encouraged to participate, e.g. by requesting a sorely missing feature, warning of an upcoming Xen change that may affect libvirt, or simply suggesting a change that makes virtualization management life a bit easier.
Kdump is a long existing method for acquiring dump of crashed kernel, however very few literatures are available to understand it's usage and internals. We receive a lot of queries on kexec mailing list about different issues related to the kexec/kdump environment.
In this presentation, we talk about basics of kdump usage and some internals about kdump/kexec kernel implementation. It includes end to end flow from kdump kernel configuration to crash analysis. We discuss some of the problem which is frequently faced by kdump users. It also includes related information about ELF structure, so that one can debug if vmcore itself gets corrupted because of any architecture related issue.
This document summarizes a project that investigated air leakage in large buildings in Minnesota. Air leakage tests were conducted on 6 buildings before and after air sealing. On average, air sealing reduced leakage by 10%. Tests found that buildings were 84% tighter than average US buildings, possibly due to the cold climate. Pressurization tests found greater air leakage than depressurization by 22% on average. Mechanical systems were found to increase total building leakage by 15-119% and have a significant effect on building pressure. Future work will model these effects and develop methods to estimate pressure effects and air sealing savings.
Wind energy has huge potential and is the world's fastest growing energy source. Advances in turbine technology have reduced costs, with wind power now comparable to conventional sources. While intermittent, wind works well paired with hydro or solar and future innovations may address issues like energy storage. Overall, the future of wind energy looks bright as it provides clean power without fuel costs or pollution.
70045 wind farms in cold climates (print) (2)Heather Smith
Do you work on wind farms in cold and difficult climates?
Do you want to join over 70 of your peers from across the globe?
Do you want to go to an event whose delegates give it a 100% rating of excellent?
If the answer to these questions is yes, then you must join us in December at Windpower Monthly’s Optimising Wind Farms In Cold Climates, still the only event focusing on both the commercial and technical complexities which impede on the operation of wind farms in cold and difficult climates .
Types of attic insulation used in hot and cold climateslee shin
This document discusses different types of attic insulation used in hot and cold climates. For hot climates, rolled and blown-in fiberglass or cellulose insulations are commonly used, along with radiant barriers. For cold climates, loose fill cellulose and rock wool batt insulations are effective at preventing cold air entry. Proper attic insulation installation is important for moderating indoor temperatures and reducing energy costs year-round.
Green Building: Sustainable Architecture
Environmentally responsible and resource efficient building design. Architecture that minimizes the negative environmental impact of buildings by efficiency in the use of materials and energy. Goal: to effectively reduce the overall impact of the built environment on human health and the natural environment and increase comfort and livability. Consistent with AIA sponsored Architecture Challenge 2030.
McNaughton Architectural Inc. | http://mna-p.com
300 E State St Suite 360, Redlands, CA 92373
(909) 583-1806
Cavity walls are constructed with an inner and outer leaf separated by an air gap, usually filled with insulation. Cavity wall ties connect the two leaves and prevent dampness penetration that can occur in solid walls. Potential problems include weakness of the two thin leaves, but ties strengthen the wall by binding the leaves together. Proper installation of ties and sealing around openings is important to prevent moisture from bridging the air cavity.
Teri, bangalore & solar passive techniques(rupesh)Rupesh Chaurasia
The document summarizes the green building features of TERI's campus in Bangalore. The campus utilizes passive design principles to maximize natural lighting, ventilation and minimize energy usage. Key features include an optimized building orientation, ample fenestrations for cross ventilation, skylights, green roofs, solar panels, rainwater harvesting and use of local sustainable materials. Passive design strategies like earth air tunnels help regulate indoor temperature passively.
Green Building Case Study on TERI,bangalore.Vinay M
This presentation basically encompasses the green practices which are followed or incorporated in the structure to attain the platinum rating systems and posses the sustainable features that way..!!
Cavity walls have two skins separated by a hollow space which provides several advantages over solid walls. The cavity allows moisture from the outer skin to drain out through weep holes while preventing transfer to the inner skin. Cavity walls also provide better thermal and sound insulation than solid walls due to the non-conductive air gap. Common components of cavity walls include insulation materials filled in the cavity to reduce heat loss, wall ties to bond the two skins, and damp proof courses above and below to prevent moisture penetration.
The document discusses duct design and sealing. Some key points:
1) Poorly sealed ductwork is a common problem that wastes energy and can impact comfort and health. Locating ducts inside conditioned spaces eliminates leakage issues.
2) The IECC requires effective sealing materials like mastic and tape to minimize duct leakage. Limiting leakage saves energy and improves indoor air quality.
3) Forced air systems should have balanced airflow between supply and return ducts to prevent pressure imbalances that can increase leakage and backdrafting of combustion appliances. High priority leak areas to seal include disconnected components and connections to the air handler.
This document provides an introduction to HVAC systems. It discusses the primary functions of HVAC systems to provide healthy and comfortable interior conditions while minimizing energy usage and emissions. It describes different types of HVAC systems including air systems, hydronic/steam systems, and unitary systems. It also discusses key HVAC components like air handling units, fans, pumps, ductwork, controls and their purposes.
This document summarizes a report on OFELIA from Cesar A. C. Marcondes of UFSCar. It discusses UFSCar's involvement in OFELIA working on task 2.3 on control and management frameworks. It provides an overview of OFELIA and the step-by-step process to use OFELIA including registering an account, setting up a VPN, creating a project, allocating resources, and starting an experiment. It also shares lessons learned from replicating an OFELIA island including issues with templates, kernels, pinging VMs, OpenWRT, netFPGAs, and controller over VPN.
This document discusses education using FIRE (Future Internet Research and Experimentation) testbeds. It provides an overview of FORGE (Forging Online Education through FIRE), including details about FIRE, an example wireless networking course, and FORGE tools and an open call. The example course shows how it was implemented using the iMinds w-iLab.t and Virtual Wall testbeds, with remote and automated experimentation. The open call invites proposals to develop interactive educational materials using FIRE facilities.
from Docker to Moby and back. what changed ?strikr .
The document discusses the Docker to Moby project transition and the container landscape. It describes how Docker's monolithic architecture was split into individual components under the Moby project, including containerd for the core runtime and runc for spawning OCI containers. It also outlines the various container networking and storage solutions like CNI, CNM, and device mapper, and how projects like containerd, runc, moby, and others relate in the ecosystem. The goal is to establish open standards and extensible architectures for building cloud-native systems using containers.
This document discusses encrypting volumes with Barbican in OpenStack. It provides an introduction to Barbican and encryption, describes how Barbican works with Nova and Cinder to provide transparent encryption of volumes using LUKS, discusses some issues the presenter encountered integrating Barbican on OnRamp's private cloud and how they were resolved, and limitations to be aware of when using encrypted volumes. It concludes with a demo and Q&A.
The document discusses building an enterprise/cloud analytics platform using Jupyter notebooks and Apache Spark. It describes the challenges of deploying Jupyter notebooks at an enterprise scale, including collaboration, large-scale data analysis, security, and authentication. It outlines various approaches taken to address these challenges, such as running the entire Jupyter stack on a single large machine or giving each user their own container. However, these approaches have limitations. The document then introduces the Jupyter Enterprise Gateway as a solution developed by IBM to optimize resource allocation, support multi-users securely through impersonation, and enhance security overall when deploying Jupyter at an enterprise scale.
The age of IoT is at our threshold. Many large-scale companies have already started developing security solutions to make this brave new world safe. One of possible, we may even say, surefire approaches is to create a device which would connect to a network and protect other devices in it. Let’s discuss the efficiency of the given approach in relation to BitDefender Box.
Tech Tutorial by Vikram Dham: Let's build MPLS router using SDNnvirters
Synopsis
We will start with MPLS 101 and then look into MPLS related OpenFlow actions. In the second half we will delve into RouteFlow architecture and extend it to enable Label Distribution Protocol (LDP) and MPLS routing. We will conclude with a mini-net based test bed switching traffic using MPLS labels instead of IP addresses.
This will be a hands on workshop. VM Images for Virtual Box will be provided. Attendees are expected to bring their laptops loaded with Virtual Box.
About Vikram Dham
Vikram is the CTO and co-founder of Kamboi Technologies, LLC where he advises networking companies, switch vendors and early adopters on SDN technology and distributed software development. Also, he is the founder of Bay Area Network Virtualization (BANV) meet-up group, that brings together technologists in the SDN/NFV/NV domain for technical talks, workshops and creates a truly "open" platform for sharing knowledge.
He has used SDN technologies for building software related to traffic engineering, security and routing. In the past, he was the Principal Engineer at Slingbox where he architected & built the distributed networking software for peer to peer connectivity of millions of end points. He holds MS degree in EE with a specialization in Computer Networks from Virginia Tech and has worked on research projects with companies like ECI Telecom, Raytheon and Avaya Research Labs.
Balázs Bucsay - XFLTReaT: Building a Tunnelhacktivity
XFLTReaT is an open-source tunnelling framework that handles all the boring stuff and offers the capability to the users to take care of only those things that matter. It provides significant improvements over existing tools. From now on there is no need to write a new tunnel for each and every protocol or to deal with interfaces and routing. Any protocol can be converted to a module, which works in a plug-and-play fashion; authentication and encryption can be configured and customised on all traffic and it is also worth mentioning that the framework was designed to be easy to configure, use and develop. In case there is a need to send packets over ICMP, RDP or SSH then this can be done in a matter of minutes, instead of developing a new tool from scratch. The potential use (or abuse) cases are plentiful, such as bypassing network restrictions of an ISP, the proxy of a workplace or obtaining Internet connectivity through bypassing captive portals in the middle of the Atlantic Ocean or at an altitude of 12km on an airplane.
This framework is not just a tool; it unites different technologies in the field of tunnelling. It will be show how to tunnel data over a Windows jumpbox utilising RDP (including the dirty low level "secrets") or how to exfiltrate data over ICMP from barely secured networks. We have simplified the whole process and created a framework that is responsible for everything but the communication itself, we rethought the old way of tunnelling and tried to give something new to the community. After the initial setup the framework takes care of everything. With the check functionality we can even find out, which module can be used on the network, there is no need for any low-level packet fu and hassle. I guarantee that you won’t be disappointed with the tool and the talk, actually you will be richer with an open-source tool.
This document provides an overview of hybrid cloud computing and outlines the steps to build a private or hybrid cloud using the open source Eucalyptus cloud platform. It describes the key components of Eucalyptus including the cloud controller, nodes, and networking configuration. The document also summarizes how to use the euca2ools to manage Eucalyptus resources such as images, instances, volumes, and security groups.
Freeze Drying for Capturing Environment-Sensitive Malware AliveFFRI, Inc.
We propose a set of techniques for "freeze drying" malware and restoring the captured malware to enable live process migration. Our system can capture environment-sensitive malware in-process and run it in an environment other than the infected host.
Sophisticated malware, such as Citadel and ZeuS/GameOver, are armed with anti-analysis techniques to prevent running except on an infected host. These malwares detect the execution environment and do not engage in malicious behavior when the current host differs from the infected host.
We developed a malware capture system called Sweetspot that can capture malware in-process by using process live migration and mimicking the infected host's environment on the analyzer by means of system call proxies. In addition, Sweetspot can serve as a honeypot and provide dummy data when the malware requests sensitive information. In briefings, we will demonstrate freeze-drying and instant dynamic analysis of real malware.
This document provides an overview and demonstration of Security Onion, an open-source Linux distribution for intrusion detection and network security monitoring. It describes Security Onion's tools like Snort, Sguil, Pulled Pork, Snorby and Daemonlogger. The document demonstrates how to install Security Onion, use its tools to analyze network traffic, view alerts and raw packet captures. It also provides challenges for users to further explore Security Onion's capabilities.
A presentation on how applying Cloud Architecture Patterns using Docker Swarm as orchestrator is possible to create reliable, resilient and scalable FIWARE platforms.
An overview on docker and container technology behind it. Lastly, we discuss few tools that might come handy when dealing with large number of containers management.
This document discusses configuring FreeSWITCH, an open source telephony platform, on Docker. It provides background on IP telephony systems and introduces FreeSWITCH and Docker. The benefits of using FreeSWITCH on Docker are explained, such as easier deployment and scalability. Steps are outlined to install FreeSWITCH from source on a CentOS Docker container and configure the network settings. Finally, instructions are given to configure a SIP phone like Linphone and verify the FreeSWITCH installation by placing test calls.
This document discusses configuring FreeSWITCH, an open source telephony platform, on Docker. It provides background on IP telephony systems and introduces FreeSWITCH and Docker. The benefits of using FreeSWITCH on Docker are explained, such as easier deployment and scalability. Steps are outlined to install FreeSWITCH from source on a CentOS Docker container and configure the network settings. Finally, instructions are given to configure a SIP phone like Linphone and verify the FreeSWITCH installation by placing test calls.
Presentation at the FORGE workshop collocated with the World Engineering Education Forum (WEEF), the International Conference on Interactive Collaborative Learning (ICL) and the International Conference on Engineering Pedagogy (IGIP) in Florence, Italy on September 20th, 2015.
Engage 2020 - Kubernetes for HCL Connections Component Pack - Build or Buy?panagenda
HCL Connections V7 will be based on Kubernetes only! A parallel WebSphere environment won't be necessary any longer. Martin and Christoph collected the basics and differences in building a Kubernetes environment of your choice. They show you a comparison of an on-premises deployment versus a hosted cloud environment (Amazon EKS). After this session you have the basics to size and build a Kubernetes cluster for Component Pack, so you can start learning the new technology to take off with Connections V7 and become a Kubernaut.
Running Cloud Foundry for 12 months - An experience report | anyninesanynines GmbH
anynines ran a public PaaS located in a German datacenter based on Cloud Foundry. In more than 12 months of running a Cloud Foundry PaaS man lessons about security, high availability, open stack and many other exciting topics have been learned. See how Bosh can be used and how it shouldn't be used. Learn how to perform Cloud Foundry upgrades and read how to harden Cloud Foundry by adding more fault tolerance with pacemaker.
Kubernetes for HCL Connections Component Pack - Build or Buy?Martin Schmidt
HCL Connections V7 will be based on Kubernetes only! A parallel WebSphere environment won't be necessary any longer. Martin and Christoph collected the basics and differences in building a Kubernetes environment of your choice. They show you a comparison of an on-premises deployment versus a hosted cloud environment (Amazon EKS). After this session you have the basics to size and build a Kubernetes cluster for Component Pack, so you can start learning the new technology to take off with Connections V7 and become a Kubernaut.
Similar to BonFIRE: features, sites and tools (20)
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
4. BonFIRE4 4
Prerequisites
• You must have an account in BonFIRE.
– If you don’t, please go to:
• http://www.bonfire-project.eu/involved
• https://portal.bonfire-project.eu/register/
• Your public key must be uploaded.
– If not, you can find more information here:
• http://doc.bonfire-project.eu/R3.1/getting-started/upload-ssh-
key.html
• You must have access to a SSH environment able to
connect through one the BonFIRE SSH gateways
– If not, you can find more information here:
• http://doc.bonfire-project.eu/R3.1/getting-started/ssh-gateway-
config.html
5. BonFIRE5 5
1. Create the experiment
You can choose
between different tools
Portal
Command Line
Experiment Manager
Restfully
CURL with
OCCI
• Don’t forget to set walltime properly. After it expires, the
experiment (and its resources) will be SHUTDOWN and
DELETED.
7. BonFIRE7 7
2. Set up the experiment
• Create networks, VMs and Storages
• If you want monitoring, don’t forget to add an Aggregator.
– http://doc.bonfire-project.eu/R3.1/monitoring/howto.html
9. BonFIRE9 9
Managed Experiments for initial
deployment
Resource
Manager
Experiment 356
Experiment
name: myExperiment
compute:
Name: compute1
Location: uk-eppc
Disk: OS
Network: BonFIRE WAN
Compute:
Name: compute2
Location: fr-inria
Disk: OS
Network: BonFIRE WAN
Experiment
Manager
Managed
Experiment 104
10. BonFIRE10 10
3. Configure the computes
• Log in to the computes and configure the,
• Bear in mind that you can SAVE an image and it can
be reused as many times as you want in the same
location.
• Images can’t be moved between locations, think
about scripts for repeating the same commands.
11. BonFIRE11 11
Creating and configuring VMs
OS
OS
MySQL
OS
OS
>> apt_get mysql
OS
MySQL
OS
MySQL
>
OS
> apt_get mysql
OS
MySQL
OS
MySQL
SAVE
SAVE
14. BonFIRE14 14
SSH Gateways and VPN
BonFIRE WAN
JohnSmith/*****
LDAP ServerLDAP Server
VPN serverVPN server
SSH GatewaySSH Gateway
SSH GatewaySSH Gateway
SSH GatewaySSH Gateway
JohnSmith/*****
JohnSmith/*****
> ssh 192.168.4.2
15. BonFIRE15 15
4. Perform your experiment
• Here you decide what to do!
• If the experiment contains Virtual Wall (iMinds)
resources, don’t forget to put in RUNNING state the
experiment.
16. BonFIRE16 16
5. Monitoring
• Access the Zabbix GUI, tunneled through the Portal.
• Monitor Zabbix parameters, or configure your own.
– BonFIRE offers application, VM and infrastructure monitoring from
the same API
• Use the monitoring API to make elasticity and application
decisions on the fly
17. BonFIRE17 17
6. Wrap up your experiment
• The experiment can finish in two different ways:
– Expiry time (Walltime) ends.
– You have finished before walltime arrives, and you
decide to stop or delete the experiment.
• Before this time arrives, save the images and
datablocks that you want to use again. Then,
shutdown the VM where the image/datablock is being
used.
– http://doc.bonfire-project.eu/R3.1/reference/experiment-
lifecycle.html
18. BonFIRE18 18
7. After the experiment
• Access the monitoring data that you have saved
– http://doc.bonfire-project.eu/R3.1/monitoring/getting-data/export-
csv.html
• Reuse the images that you have configured and saved
22. BonFIRE22 22
Three layers of monitoring
Physical Machine
Virtual
Machine
Virtual
Machine
Virtual
Machine
23. BonFIRE23 23
Agents and Aggregators
VM Host 1
VM Host 2
VM Host 2
VM Host 1
VMVM
VMVM
Experiment
Aggregator
Experiment
Aggregator
Data
VM data
Application Data
Intrastructure data
VM Host 1
Agent
Agent
Site
Aggregator
Site
Aggregator
Site
Aggregator
Site
AggregatorAgent
Agent Agent
Agent
VM Host 2
29. BonFIRE29 29
Exclusive physical machines
INRIA
node1 node2 node3
node7node6
node8 node9
Open
Nebula
Resource
Manager
Reservation
System
Give me
3 physical
machines
from
26/4/12 10:00 to
28/4/12 20:00
Cluster: 34563
P23
P40
p92
Location: inria
Cluster: 34563
p23
p40
p92
Cluster: 34563
Location: inria
Cluster: 34563
Host: p40
node5
30. BonFIRE30 30
Controlled Contention
VM Host 1 VM Host 2
ExclusivePhysicalMachine
VM under testVM under test
VM under testVM under test VM under testVM under test
CoCoMaCoCoMa
Memory Use
IO Use
44. BonFIRE44 44
• Sites have different computing architectures
• Different varieties of VMs are described through
instance types
• Sites support different instance types
Name VCPU cores Memory Features
Lite 0.5 256MB CPU may be < 1
Small 1 1GB
Medium 2 2GB
Large 2 4GB
Large+ 2 4GB Higher CPU
clock speed
(over 3GHz)
Large-EN 4 4GB Emulated
network
Xlarge 4 8GB
XLarge+ 4 8GB Higher CPU
clock speed
(over 3GHz)
Custom Free Free Integer values
Which site to use?
Site Lite Small Medium Large Large+ Large-EN XLarge Xlarge+ Custom
HP + + + + +
iMinds ++
HLRS + + + + ++ + ++ +
EPCC + + + ++ ++ +
INRIA + + + +
45. BonFIRE45 45
Which site to use?
• Depends on your requirements
• Special characteristics
– Controlled networks only available at iMinds
– Public IPs are not available at iMinds and HLRS
– Reservation of nodes only available at INRIA
• Reservation at Inria Exclusive access to node
• https://api.bonfire-project.eu/locations/fr-inria/reservations
• Access methods
– SSH & VPN
– Each gateway serves for every BonFIRE WAN IP address
46. BonFIRE46 46
Information about site status
• BonFIRE health map indicates general availability
– Nagios system tests
– http://nebulosus.rus.uni-stuttgart.de/nagvis/frontend/nagvis-
js/index.php?mod=Map&act=view&show=bonfire-full
• Log files
– OpenNebula status
– OpenNebula Virtual machines
– Experiment Manager log
• Mailing list
– bonfire-announcements@lists.atosresearch.eu
48. BonFIRE48 48
Interacting with BonFIRE
Resource
Manager
Site Z
Site Y
Site X
OCCI
EnactorcURL
Experimenter
Create compute
XML
All communication via an
open RESTful interface
Don’t need to write XML and
use OCCI directly - we have
several client tools available!
49. BonFIRE49 49
Client tools overview
BonFIRE Portal
• Web interface to the BonFIRE API
• Very simple to use and get started in BonFIRE
Experiment descriptors
• Write the initial resource deployment in JSON or OVF
• Create descriptor step-by-step on Portal and edit later
Restfully
• General-purpose RESTful client
• Ruby scripting or Ruby shell interactions with the BonFIRE API
Command line tools
• Interactive, manual or scripted interaction with the BonFIRE API
53. BonFIRE53 53
BonFIRE Portal pros and cons
Pros
• Very easy to use
• Great starting point for
understanding how things
work in BonFIRE
• Gives you the overview of
your experiments and
resources
Cons
• Slow to set up large-scale
experiments
• Manual creation of each
resource
• No scripted events
possible for interacting with
services
54. BonFIRE54 54
Experiment descriptors
Experiment descriptors can specify the initial deployment of
resources.
Additional features include:
• VM contextualisation
• IP dependency resolution
• Configuration of monitoring metrics
Two representation languages available
• JSON
• OVF
57. BonFIRE57 57
Experiment descriptor pros and cons
Pros
• Good for large-scale
deployment of resources
• Easy to create via the
Portal and edit offline
• Intuitive and purposefully
created for BonFIRE
• Submit via Portal or
command line
Cons
• Cannot script other
elements of experiment
set-ups like interacting with
experiment services
• Cannot get connection to
resources when created to
perform actions
58. BonFIRE58 58
Restfully
• A general-purpose client tool for RESTful APIs
• Abstracts the details of exchanging HTTP requests
• Discovers resources at run-time
• Can be used in a Ruby shell to interactively query the
BonFIRE API
• Can be used in Ruby scripts to automate deployment of
resources and interactions with the resources
Written in Ruby
61. BonFIRE61 61
Restfully pros and cons
Pros
• Good for large-scale
experiments
• One script for deployment
of resources and gives you
connection to resources to
interact with, e.g., to install
software, start services,
etc.
• Interactive scripting
possible (user input on
command line)
Cons
• You have to create the
scripts from scratch
• Learning curve for Ruby
can be steep, but we
provide examples online
• Manually need to resolve
deployment constraints
62. BonFIRE62 62
Command line tools
• Purposefully built for BonFIRE
• Written in Python
– Bindings are easy to get by reading our online documentation
• Support for BonFIRE experiment lifecycle:
– bfexperiment
– bfcompute
– bfstorage
– …
• Abbreviations possible, instead of long URIs
– /locations/uk-epcc/networks/42 42
64. BonFIRE64 64
Command line tools pros and cons
Pros
• Intuitive to use
• Scripting possible, e.g.,
Bash on Linux or Batch
(MSDOS) on Windows
Cons
• Scripting is more limited
than Restfully
– Connecting to interact with
resources possible but not as
easy as with Ruby
• Less declarative than
experiment descriptor
– Manually need to resolve
deployment constraints
67. BonFIRE67 67
Support Mechanism
Documentation
• General Information:
http://bonfire-project.eu/
• User Documentation:
http://www.bonfire-project.eu/docs
User Forum
https://forum.bonfire-project.eu/
Support Ticketing System
support@bonfire-project.eu
The following positional argument must be specified when creating experiments:<name> - The name for this experiment.The following options are applicable when creating experiments:-D <description>, --description <description> - description of the experiment. Defaults to “<no description>”.-W <walltime>, --walltime <walltime> - lifetime of the experiment in seconds. Defaults to one day.-G <group>, --group <group> - A user group this experiment will be accessible by. This option can be specified multiple times.The following positional arguments must be specified when creating storages (in that order):<name> - The name for this resource.<location> - The BonFIRE site where this resource will be created.Optionally, an experiment this resource will be part of can be specified as a third positional argument. The following options are applicable when creating storages:-D <description>, --description - The description of this storage resource. Defaults to “<no description>”.-S <size>, --size - Size of this storage resource in MiB. This is only applicable to datablock resources. Defaults to 1024 MiB.-T {datablock|shared} - The type of this storage resource. Note that “shared” storages are only available on be-ibbt. Defaults to “datablock”.-F <filesystem>, --fstype <filesystem> - The filesystem the storage resource will be formatted with. This is only applicable to datablock resources. Defaults to “ext3”.-G <group>, --group <group> - A user group this resource will be accessible by. This option can be specified multiple times.-P, --public - Indicates that this storage resource should be publicly available. Defaults to <false>.-R, --persistent - Indicates that a persistent storage resource should be created. Defaults to <false>.