BMC Launcher
A command-line utility that uses Selenium WebDriver to launch a browser, navigate to a server's BMC (Baseboard Management Controller) web interface, and login automatically.
Installation
Install with pipx (recommended). This installs bmc-launcher in an isolated environment and puts it on your PATH:
pipx install bmc-launcher
Alternatively, install with pip:
pip3 install bmc-launcher
Development setup
-
Clone the repository
git clone https://github.com/theopsguy/bmc-launcher.git cd bmc-launcher -
Install dependencies with Poetry:
pip3 install poetry && poetry install -
Run the tool via Poetry:
poetry run bmc-launcher -l
Configuration
Default location:
~/.bmc_launcher/config.yaml
Example
default_credentials:
hpe:
username: admin
password: mysecret
dell:
username: root
password: dellpass
hosts:
- name: web00
url: https://192.168.1.10
manufacturer: hpe
ilo_version: 4
- name: db00
url: https://192.168.1.11
manufacturer: dell
idrac_version: 9
credentials:
username: specialuser
password: otherpass
HPEhosts requireilo_versionDELLhosts requireidrac_versionSUPERMICROhosts need neither.
Currently supported versions are iLO 4 and iDRAC 8/9.
Usage
- List hosts defined in the configuration:
% bmc-launcher -l
- name: web00
url: https://192.168.1.10
manufacturer: HPE
credentials:
username: Administrator
password: '**********'
ilo_version: 4
- name: firewall00
url: https://192.168.1.1
manufacturer: SUPERMICRO
credentials:
- name: test_dell
url: https://10.0.0.1
manufacturer: DELL
credentials:
idrac_version: 9
- Launch BMC:
bmc-launcher -H web00 -i
Options
| Flag | Description |
|---|---|
-H, --host |
Host name to launch, as defined in the configuration |
-l, --list-hosts |
List all available hosts |
-d, --driver |
Web driver to use (default: chrome) |
-i, --ignore-cert-errors |
Ignore SSL certificate errors |
-c, --config |
Path to the configuration file (default: ~/.bmc_launcher/config.yaml) |
-v, --verbose |
Enable verbose logging |
Roadmap
- Support loading hosts from an Ansible dynamic inventory, as an alternative to the static
config.yamlfile.
For other ideas or in-progress work, see the GitHub issues.
Metadata
Release files for bmc-launcher 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bmc_launcher-0.1.1.tar.gz | 18.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bmc_launcher-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.2 kB
Release files / bmc_launcher-0.1.1.tar.gz
| Download URL | bmc_launcher-0.1.1.tar.gz |
|---|---|
| Size | 18.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f26727c1d7c545dd85110158675c59d2bf1cd87a25499afa20a25f4374e2e30e
|
|
BLAKE2b-256 checksum How to use checksums |
6d56b9c674b7022925d7329db82dfe9d68968e49ba4a2201e914984efc9da1b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / bmc_launcher-0.1.1-py3-none-any.whl
| Download URL | bmc_launcher-0.1.1-py3-none-any.whl |
|---|---|
| Size | 23.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c075c0b0a166b4b1c07a40614fe301e1f7ad27711be91fb3a961ad6ba932e5e
|
|
BLAKE2b-256 checksum How to use checksums |
9ff8a520282d86768c3a9073b6fc9a46bcb33b31267f2b3b15329c04b6a0b408
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency log