8. Hadoop deployment
• Includes cluster deployment and Hadoop-stack deployment
• Without proper infrastructure setup, Hadoop will not run
• Proper Hadoop setup relies on network/OS/filesystem tuning
• Knowledge and expertise in both are rare
9. Hadoop deployment
Challenge for cluster admins
• E.g., configuring Hadoop components
• Understanding of HDFS/MapReduce/YARN/HBase/…
essential
• Numerous configuration settings
• Hadoop distribution choice
• Different Hadoop modes
• HDFS & HDFS HA, YARN & YARN HA, …
10. Hadoop deployment
Challenge for Hadoop admins
• Configuration is still hard
• Numerous configuration settings
• Deprecated properties
• MRv1 to YARN migration
• OS/network tuning essential
11. Hadoop deployment/maintenance
• Hadoop validation by running test/benchmarking jobs
• Monitoring and health checking on both OS and Hadoop stack levels
• Upgrades
17. Architecture
• Cluster management daemon:
• Low overhead
• All nodes run the same daemon
• Assigned roles define which tasks cluster management daemon
can perform
18. Architecture
• Role can be assigned to a node to do a task
• E.g., a provisioning role makes a node to spread software images
onto other nodes
• HDFS NameNode role makes a node to store HDFS metadata and
control nodes with HDFS DataNode roles
• Assignment of HDFS DataNode role to a node: adding and starting
DataNode service
21. Interfaces
Graphical User Interface (GUI)
Offers administrator full cluster control
Standalone desktop application
Manages multiple clusters simultaneously
Runs natively on Linux, Windows and OS X
Cluster Management Shell (CMSH)
All GUI functionality also available through
Cluster Management Shell
Interactive and scriptable in batch mode
Cluster
Management
GUI
Cluster
Management
Shell
22.
23. Managing Clusters
• Bright Cluster Manager manages several types of clusters
• HPC, private cloud (OpenStack), …
• Hadoop
• Cluster of any type:
• Deployed
• Configured
• Provisioned
• Managed
• Monitored
• Health-checked
24. Hadoop support
• Choice of distributions
• Management/monitoring from one place
• CLI and GUI: cmsh, cmgui
• Hadoop stack support
• Including support for Spark (Spark Standalone mode since release
7.1)
• Flexible configuration
25.
26.
27.
28.
29. Hadoop configuration
Hadoop configuration through roles
• Nodes configured to run certain Hadoop related services by assigning
roles
• 15 Hadoop and 3 Spark roles:
E.g., HDFS DataNode, MRv1 JobTracker, YARN ResourceManager,
HBaseMaster, Zookeeper, SparkWorker, …
• Assigning/unassigning role will:
• Write out corresponding configuration files based on configurable role
parameters
• Start/stop/monitor relevant services
• Hadoop configuration settings changed from inside Bright
30.
31. Bright’s Hadoop Cluster Management
Bright Cluster Manager 7.1 for Apache Hadoop
• Just released
• Single-pane-of-glass for managing both physical cluster and Hadoop
• Easy installation of Hadoop
• Apache Hadoop 1.2.1, 2.6.0 (on Bright DVD)
• Cloudera CDH 4.6.x, 4.7.x, 5.2.x, 5.3.x (5.4.x soon)
• HortonWorks HDP 1.3.x, 2.1.x, 2.2.x
• Pivotal HD 2.1.0 (3.0.0 soon)
• Configuration, monitoring and healthchecking of Hadoop instances
• Graphical UI, command-line interface and API access
32. Key Features
• Multiple Hadoop cluster instances on same cluster
• Choice of Hadoop distributions/versions
• Flexible Hadoop configuration controlled through GUI and CLI
• Hadoop configuration groups address ‘cluster heterogeneity’ problem
• JSON/Python API
• Scriptable deployment/configuration operations
• Alternative filesystems to HDFS (e.g. Hadoop on Lustre)
34. Open issues
Building and running cost-efficient Hadoop clusters
• Hard to optimize
• Workload-specific
• Tuning on all levels: OS/network/Hadoop
• Bright’s architecture
• All cluster/Hadoop operational data aggregated in one place
• Flexible configuration of hardware/software components
35. Conclusion
• Architecture of distro-agnostic Hadoop cluster manager
• Bright provides tried & tested implementation of this architecture
• Hundreds of clusters are being managed using Bright Cluster Manager
• Complete solution for setup, management & monitoring of Hadoop clusters
• Single pane of glass for cluster & Hadoop stack
• Well suited for ‘multi-purpose’ clusters: e.g., supporting both HPC
computations and Hadoop jobs
36. Come to our booth
• Meet with Bright guys
• See demo
• Tell us about your cluster
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.
Bright Cluster Manager is Image based, which means that
A slave node image stored in a directory on the head node which includes a complete Linux file system structure, including directories such as /etc, /var, /usr
An unlimited number of images can be created. For example, you can have different images for different types of slaves nodes, or you can clone an image before you start experimenting with it.
Software changes for the slave nodes are made inside the image(s) on the head node. For example, you can use an RPM command with the root option, or “chroot” into the image to install or remove RPMs, or you can edit a file using an editor.
The provisioning system ensures that changes are propagated to the slave nodes. Because only changes are propagated, its happens as fast as possible and consumes minimal network bandwidth.
Nodes always boot over the network (Although this can be disabled)
Slave nodes PXE boot into the Node Installer, which
identifies the node,
configures the BMC (such as IPMI) and detects and enables GPUs,
partition disks and creates file systems, if necessary.
It then installs or updates the software image, if necessary.
and finally, it “Pivots” the root from NFS to the local file system.