https://bugzilla.redhat.com/show_bug.cgi?id=1066629 --- Comment #16 from James Slagle <jslagle@xxxxxxxxxx> --- (In reply to Pádraig Brady from comment #15) > I see all the binaries listed in comment #8 > > They really should be confined to /usr/libexec/openstack-tripleo > > If they are to be exposed to a standard user shell then they > should be prefixed with something like tripleo-... > However having so many CLI entry point commands available > is very questionable, and I suspect some refactoring/wrapping > from a single /usr/bin/tripleo command that calls out/includes > these functions would be the way forward. These are all scripts that upstream tripleo has written to aid in doing OpenStack deployments. Longer term, the hope is they will be integrated back into the relevant OpenStack projects (e.g., init-keystone back into keystone as something else). Or, replaced entirely with calls to the tuskar cli. Many of them need to be called from the CLI. Given that, can I do a hybrid approach? I'm thinking moving them to get installed under /usr/libexec/openstack-tripleo, and then adding a /usr/bin/tripleo which is pretty much just: #!/bin/bash /usr/libexec/openstack-tripleo/$1 A large number of the scripts will need patches to add /usr/libexec/openstack-tripleo to $PATH though. I think that would be easier than prefixing all the calls with /usr/bin/tripleo. That would just be a maintenance burden every time we sync with upstream. Please let me know if this would be acceptable. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review