Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

2015-11-10 Thread Lennart Regebro
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

[openstack-dev] os-cloud-config support for custom .ssh configs

2015-09-15 Thread Lennart Regebro
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

Re: [openstack-dev] TripleO client answers file.

2015-11-27 Thread Lennart Regebro
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,

[openstack-dev] [TripleO/heat] openstack debug command

2015-11-30 Thread Lennart Regebro
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

Re: [openstack-dev] [TripleO/heat] openstack debug command

2015-12-01 Thread Lennart Regebro
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

[openstack-dev] TripleO client answers file.

2015-11-26 Thread Lennart Regebro
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