ack Development Mailing List
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [kolla] Ansiblize init-runonce script
yes. it is not
recommend to use in prod env, i never used this script. But
the reality is
lots users are using it, at least in the test environment.
and there are
scripts, thats 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
>
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: zhang.le
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,
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.
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
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