vsoch pushed to vsoch/flux-coral2
feat: support for flux operator miniclusters
This feature includes the addition to create a Flux Operator MiniCluster running across some subset of rabbit nodes given that the rabbit.mpi directive is defined. By default, setting that to true (or anything) can use a default container base and interactive mode, and everything from that can be customized. In addition, we have a “flux hop” command that is able to take the same metadata, populate the RabbitMPI Job object, and create the Flux MiniCluster using the same classes/logic but without requiring the HPE stuff and Workflow. This could be used, but likely will be for testing or for fun.
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to singularityhub/shpc-registry
Merge pull request #381 from singularityhub/update/containers-2025-09-16
[bot] update/containers-2025-09-16</small>
vsoch pushed to grondo/flux-python
Expand info_commands in setup.py
Expanding our list of info commands to include those needed for the ticket. The only command provided that won’t work is a blank python setup.py. If they use a source distributed that hasn’t had the version changed from develop, there will also be a warning. The rest of the info output looks good.</small>
vsoch pushed to converged-computing/flux-usernetes
nit: remove pycache
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to vsoch/flux-coral2
feat: support for flux operator miniclusters
This feature includes the addition to create a Flux Operator MiniCluster running across some subset of rabbit nodes given that the rabbit.mpi directive is defined. By default, setting that to true (or anything) can use a default container base and interactive mode, and everything from that can be customized. In addition, we have a “flux hop” command that is able to take the same metadata, populate the RabbitMPI Job object, and create the Flux MiniCluster using the same classes/logic but without requiring the HPE stuff and Workflow. This could be used, but likely will be for testing or for fun.
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch opened a pull request to flux-framework/flux-coral2
vsoch pushed to compspec/compspec-modules
Merge pull request #3 from compspec/changes-for-fractale
feat: support for detect</small>
vsoch pushed to compspec/compspec-containment
Merge pull request #1 from compspec/add-detect
feat: support for detect</small>
vsoch commented on issue opencontainers/specs.opencontainers.org#12.
Gotcha - thank you for that example. I’m looking at the preview: …
vsoch pushed to flux-framework/flux-python
deprecate: install-mamba.
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale-agent-experiments
results: adding laghos runs and updated ui
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale-agent-experiments
laghos: add decision function
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
Merge pull request #16 from compspec/add-flux-generator
Add flux generator</small>
vsoch commented on issue flux-framework/flux-python#18.
@trws @grondo @garlick looking for your advice! In testing building for Mac, I found that flux core and flux security need something called pipe2. …
vsoch pushed to compspec/fractale-agent-experiments
add lammps decision function
This was providing a guidance function to lammps for a pinned problem size. We need to next try and not limit to a problem size.
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch commented on issue opencontainers/specs.opencontainers.org#11.
It is done dynamically (see here) so we don’t have to re-render anything. The content on the site always reflects the latest README files and associated spec assets….
vsoch pushed to compspec/fractale-agent-experiments
amg: add note about minicluster crd
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
nit: clean up results parser logic
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to singularityhub/shpc-registry
Merge pull request #379 from singularityhub/update/containers-2025-09-11
[bot] update/containers-2025-09-11</small>
vsoch commented on issue pydicom/deid#287.
I’d be happy to review a PR that makes these changes….
vsoch pushed to compspec/fractale
add optimize function
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch created a new branch, test-toss-4 at researchapps/datacrumbs
vsoch reviewed a oras-project/oras-py pull request
Good catch - thank you! Before we merge - does a non 202 response also correctly format to json? …
vsoch pushed to compspec/fractale-agent-experiments
add lammps test
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
add optimize function
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale-agent-experiments
kripke: first run with no params
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to singularityhub/shpc-registry
Merge pull request #378 from singularityhub/update/containers-2025-09-08
[bot] update/containers-2025-09-08</small>
vsoch commented on issue oras-project/oras-py#213.
All set! …
vsoch pushed to compspec/fractale-agent-experiments
lammps: more specific to change variables
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
feat: common prompt class
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
feat: common prompt class
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/flux-delegate-py
feat: add skeleton of flux remote submit
This adds the basic structure for flux remote submit, which basically wraps the flux submit command (and is designed to support other subcommands in the future). This can be moved into the flux libexec cmd directory or just used as is. I next need to parse the submit request and then map attributes, etc. to the user defined compatibility data (cluster and resource needs) and I think then we are good.
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to rseng/software
Merge pull request #439 from rseng/update/software-2025-09-07
Update from update/software-2025-09-07</small>
vsoch pushed to flux-framework/flux-operator
feat: quick start guide
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale-agent-experiments
better define amg
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale-agent-experiments
different strategy;
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/flux-delegate-py
feat: add most of code to delegate
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to flux-framework/flux-operator
add additional securitycontext
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to flux-framework/flux-framework.github.io
Merge pull request #166 from flux-framework/release-docs-2025-09-06
Update from release-docs-2025-09-06</small>
vsoch pushed to compspec/fractale
feat: common prompt class
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch commented on issue pydicom/deid#286.
I think this would be a fantastic development for the project. We can introduce changes (that are breaking) as long as it is clear / versioned with an appropriate bump. I can give feedback and review at each step - let me know on issues / PRs when the time comes….
vsoch pushed to flux-framework/flux-framework.github.io
Merge pull request #165 from flux-framework/release-docs-2025-09-04
Update from release-docs-2025-09-04</small>
vsoch pushed to conda-forge/helpme-feedstock
Merge pull request #12 from regro-cf-autotick-bot/rebuild-python314-0-1_h977fa4
Rebuild for python 3.14</small>
vsoch pushed to compspec/fractale
feat: common prompt class
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
feat: common prompt class
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to flux-framework/flux-framework.github.io
Merge pull request #164 from flux-framework/release-docs-2025-09-03
Update from release-docs-2025-09-03</small>
vsoch pushed to compspec/fractale-agent-experiments
laghos: speed up with dependency hint
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
feat: common prompt class
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch commented on issue google/dranet#151.
Thanks for checking @keithmattix - do you think you’d be able to post here when it’s out?…
vsoch pushed to compspec/fractale-agent-experiments
try different strategy
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
feat: common prompt class
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch commented on issue LLNL/merlin#406.
Thanks for doing that!…
vsoch pushed to singularityhub/shpc-registry
Merge pull request #377 from singularityhub/update/containers-2025-09-01
[bot] update/containers-2025-09-01</small>
vsoch pushed to compspec/fractale-agent-experiments
only one node
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
feat: common prompt class
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to rseng/software
Merge pull request #438 from rseng/update/software-2025-08-31
Update from update/software-2025-08-31</small>
vsoch commented on issue google/dranet#151.
Thank you @keithmattix much appreciated. Enjoy the holiday!…
vsoch commented on issue google/dranet#151.
@aojea @gauravkghildiyal Azure still has not released Kubernetes 1.34 - it’ s not an option for me when I try to deploy a cluster. Not sure if their docs are wrong or misleading. The highest version I can select is 1.33.2. …
vsoch pushed to compspec/fractale-agent-experiments
fix: ensure we have separate testing
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale-agent-experiments
do not specify lammps is at specific location
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
feat: common prompt class
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to vsoch/node-feature-discovery
feat: add ability to export
For the HPC use case, we want to be able to export static features, raw or as labels, to the terminal or a JSON path.
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to flux-framework/flux-operator
feat: support for tolerations
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
feat: common prompt class
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to singularityhub/shpc-registry
Merge pull request #376 from singularityhub/update/containers-2025-08-28
[bot] update/containers-2025-08-28</small>
vsoch pushed to conda-forge/deid-feedstock
Merge pull request #53 from regro-cf-autotick-bot/0.4.6_hcf5112
deid v0.4.6</small>
vsoch pushed to flux-framework/flux-operator
docs: add listing of possible flux view containers
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
feat: add support for flux minicluster
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
feat: add support for flux minicluster
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch created a new branch, stage-in-lean at researchapps/datacrumbs
vsoch commented on issue pydicom/deid#283.
Thank you! …
vsoch pushed to flux-framework/flux-operator
add support for image pull policy (#245)
Signed-off-by: vsoch vsoch@users.noreply.github.com Co-authored-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
feat: add support for flux minicluster
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch commented on issue oras-project/oras-py#217.
If you’ve like to contribute the fix, we’d love to have it!…
vsoch pushed to singularityhub/shpc-registry
Merge pull request #369 from singularityhub/update/containers-2025-08-19
[bot] update/containers-2025-08-19</small>
vsoch pushed to rseng/software
Merge pull request #437 from rseng/update/software-2025-08-24
Update from update/software-2025-08-24</small>
vsoch pushed to converged-computing/usernetes
Add script to start Usernetes control plane and workers
vsoch pushed to compspec/fractale-agent-experiments
tweak
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
add max_runtime_seconds
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
Merge pull request #12 from compspec/add-tracker-results
feat: enhanced support for results directory and more metadata</small>
vsoch pushed to compspec/fractale
wip: new results and optimize agent
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
wip: new results and optimize agent
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to singularityhub/shpc-registry
Merge pull request #371 from singularityhub/update/containers-2025-08-21
[bot] update/containers-2025-08-21</small>
vsoch pushed to compspec/fractale-agent-experiments
add amg2023 optimize example
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch commented on issue flux-framework/rfc#465.
The compactness (or any feature of a cli) is somewhat irrelevant if most users can’t grep it easily. My opinion is that If something is hard to use it isn’t an issue of “but there is no other way” but that we didn’t do a good enough job to think through it. I think a command line cli representation minimally needs to be easy to look at and “get” without having to be an expert user, and (me as a more advanced user) I’m staring at a lot of these examples (my previous PR included) and I don’t. Here is an example of something that is more intuitive to me - an explicit definition of shape that just defines parent-child relationships in a simple, readable path format, and then a separate configuration of those components: …
vsoch pushed to compspec/fractale
test: refactor pod/job into abstractions
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to pydicom/deid
Merge pull request #282 from Simlomb/new-private-creator-syntax
feat: Add enhanced private tag syntax support</small>
vsoch pushed to compspec/fractale-agent-experiments
results: add partial gromacs results
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale-agent-experiments
analysis: add diffs to result and last 2 amg results
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale-agent-experiments
update results to include amg2023
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
test: refactor pod/job into abstractions
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale-agent-experiments
wip: adding prototype for report
I do not like the organization of the output data and the attempts count is one off - I want to tweak / fix and rerun. This is just a test run.
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
test: refactor pod/job into abstractions
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
test: refactor pod/job into abstractions
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>
vsoch pushed to compspec/fractale
test: refactor pod/job into abstractions
Signed-off-by: vsoch vsoch@users.noreply.github.com</small>