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,
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
+1. That would be really helpful.
What about passing other deployment parameters via answers.yaml ? For
example, compute-flavor, control-flavor etc
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On Thu, Nov 26, 2015 at 01:37:16PM +0100, Lennart Regebro wrote:
> 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
On Thu, Nov 26, 2015 at 06:01:31PM +0500, 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
So, I think the main reason to avoid this, is that long term it
On 11/26/2015 02:34 PM, Steven Hardy wrote:
On Thu, Nov 26, 2015 at 01:37:16PM +0100, Lennart Regebro wrote:
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
Thanks Steve. Makes sense to avoid passing deployment parameters with
answer file interface Lennart proposed.
On Thu, Nov 26, 2015 at 6:42 PM, Steven Hardy wrote:
> On Thu, Nov 26, 2015 at 06:01:31PM +0500, Qasim Sarfraz wrote:
> >+1. That would be really helpful.Â
> >