On Tue, Dec 1, 2015 at 3:39 AM, Steve Baker wrote:
> I mean _here_
>
> https://review.openstack.org/#/c/251587/
OK, that's great! If you want any help implementing it, I can try.
//Lennart
__
OpenStack Development Mailing L
I'm tasked to implement a command that shows error messages when a
deployment has failed. I have a vague memory of having seen scripts
that do something like this, if that exists, can somebody point me in
teh right direction?
Any opinions on what that should do, specifically? Traverse failed
resou
On Thu, Nov 26, 2015 at 2:01 PM, Qasim Sarfraz wrote:
> +1. That would be really helpful.
>
> What about passing other deployment parameters via answers.yaml ? For
> example, compute-flavor, control-flavor etc
The overcloud update command doesn't take those parameters, however
most of those will
We are proposing to have an "answers file" for the tripleoclient so
that you don't have to have a ling line of
openstack overcloud deploy --templates /home/stack/mytemplates
--environment superduper.yaml --environment loadsofstuff.yaml
--envirnoment custom.yaml
But instead can just do
open
These changes are fine to me.
I'm not so sure about the idea that we can't "hijack" other projects
namespaces. If only ironic is allowed to use the prefix "baremetal",
then the prefix should not have been "baremetal" in the first place,
it should have been "ironic". Which of course means it would
In bug https://bugzilla.redhat.com/show_bug.cgi?id=1252255 is about adding a
possibility to have an .ssh directory that is not in ~/.ssh
Currently the blocker there is os-cloud-config, that just calls ssh, and ssh
will look in the users homedirectory for .ssh/config no matter what.
To solve thi
