Skip to content

Commit

Permalink
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
added warning when CONDA_PREFIX is set
Browse files Browse the repository at this point in the history
XaverStiensmeier committed Aug 22, 2024
1 parent 09989e9 commit 7aaf1e8
Showing 2 changed files with 10 additions and 6 deletions.
11 changes: 5 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
@@ -16,8 +16,7 @@ a cloud IDE for writing, running and debugging (Theia Web IDE) and many more.
> but not maintained anymore.
## Getting Started
For most users the [Hands-On BiBiGrid Tutorial](https://github.com/deNBI/bibigrid_clum2022)
is the best entry point.
For most users the [Hands-On BiBiGrid Tutorial](https://github.com/deNBI/bibigrid_clum2022) is the best entry point.

However, if you are already quite experienced with *OpenStack* and the previous *BiBiGrid* the following brief explanation
might be just what you need.
@@ -58,7 +57,7 @@ an sshUser (most likely ubuntu) and a subnet.
You will likely also want to specify at least one worker instance with a valid type, image, and count.
4. If your cloud provider runs post-launch services, you need to set the `waitForServices`
key appropriately which expects a list of services to wait for.
5. Create a virtual environment from `bibigrid/requirements.txt`.
5. Create a virtual environment from `bibigrid/requirements.txt`. Conda environments do not work.
See [here](https://www.akamai.com/blog/developers/how-building-virtual-python-environment) for more detailed info.
6. Take a look at [First execution](#first-execution)

@@ -69,18 +68,18 @@ After cloning the repository, navigate to the bibigrid directory.
Source the virtual environment created during [preparation](#preparation) to execute BiBiGrid.
Refer to BiBiGrid's [Command Line Interface documentation](documentation/markdown/features/CLI.md) if you want to explore additional options.

A first execution run through could be:
First steps could be:
1. `./bibigrid.sh -i [path-to-bibigrid.yaml] -ch`: checks the configuration
2. `./bibigrid.sh -i 'bibigrid.yaml -i [path-to-bibigrid.yaml] -c'`: creates the cluster (execute only if check was successful)
3. Use **BiBiGrid's create output** to investigate the created cluster further. Especially connecting to the ide might be helpful.
Otherwise, connect using ssh.
4. While in ssh try `sinfo` to printing node info
5. Run `srun -x $(hostname) hostname` to power up a worker and get its hostname.
6. Run `sinfo` again to see the node powering up. After a while it will be terminated again.
6. Run `sinfo` again to see the node powering up. Run `bibilog` after a while to see the ansible playbook run.
7. Use the terminate command from **BiBiGrid's create output** to shut down the cluster again.
All floating-ips used will be released.

Great! You've just started and terminated your first cluster using BiBiGrid!
Great! You have just started and terminated your first cluster using BiBiGrid!

</details>

5 changes: 5 additions & 0 deletions bibigrid/core/startup.py
Original file line number Diff line number Diff line change
@@ -130,6 +130,11 @@ def main():
args = command_line_interpreter.interpret_command_line()
set_logger_verbosity(args.verbose)
configurations = configuration_handler.read_configuration(LOG, args.config_input)
if "CONDA_PREFIX" in os.environ:
LOG.warning("Do not use a conda environment for bibigrid.\n"
"Please create a regular python environment: https://docs.python.org/3/library/venv.html")
if input("Empty input to continue; otherwise aborts:"):
sys.exit(1)
if configurations:
sys.exit(run_action(args, configurations, args.config_input))
sys.exit(1)

0 comments on commit 7aaf1e8

Please sign in to comment.