the time.
Cheers
-steve
From: Jeffrey Zhang
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Tuesday, November 28, 2017 at 7:48 PM
To: Samuel Yaple , OpenStack Development Mailing List
Subject: Re: [openstack-dev] [kolla] Ansiblize init-runonce script
t; prerogative, but it was discussed before and mostly considered a bad idea.
>
> Thanks,
> SamYaple
>
>
>
> -------- Original Message ----
> Subject: Re: [openstack-dev] [kolla] Ansiblize init-runonce script
> Local Time: November 28, 2017 8:10 AM
> UTC Time: Novembe
your prerogative, but
it was discussed before and mostly considered a bad idea.
Thanks,
SamYaple
> Original Message
> Subject: Re: [openstack-dev] [kolla] Ansiblize init-runonce script
> Local Time: November 28, 2017 8:10 AM
> UTC Time: November 28, 2017 1:10 PM
> From: zha
in my opinion,
idempotent scrip
t is very necessary.
for several reason
- there is already some idempotent logical in the script
- it is common that this script failed by wrong configuration,
after fix the config,
ops will want to run this script again.
On Tue, Nov 28, 2017 at 7:14 PM, Pau
I think this came up before at one stage. My position is I don't see the
need to ansible-ise small shell scripts. init-runonce is currently just
an easy to understand sequence of openstack commands provided to help
people test/demo their setups. Unless we want to make it more than that,
i.e. ma
hi
check this [0]. I tried to convert it to ansible playbooks.
[0] https://review.openstack.org/523072
On Tue, Nov 28, 2017 at 2:57 AM, Ravi Shekhar Jethani
wrote:
> Hi,
>
> While exploring kolla-ansible I ran into a few issues with
> init-runonce script. This lead to following bugs and patch
Hi,
While exploring kolla-ansible I ran into a few issues with
init-runonce script. This lead to following bugs and patches:
https://launchpad.net/bugs/1732963
https://review.openstack.org/51
https://review.openstack.org/521190
But it was highlighted that instead of fixing/changing the
scrip
