Dmitry, Fields or field? Do we need to provide password only or other credentials are needed?
2014-06-25 13:02 GMT+04:00 Dmitriy Shulyak <dshul...@mirantis.com>: > Looks like we will stick to #2 option, as most reliable one. > > - we have no way to know that openrc is changed, even if some scripts > relies on it - ostf should not fail with auth error > - we can create ostf user in post-deployment stage, but i heard that some > ceilometer tests relied on admin user, also > operator may not want to create additional user, for some reasons > > So, everybody is ok with additional fields on HealthCheck tab? > > > > > On Fri, Jun 20, 2014 at 8:17 PM, Andrew Woodward <xar...@gmail.com> wrote: > >> The openrc file has to be up to date for some of the HA scripts to >> work, we could just source that. >> >> On Fri, Jun 20, 2014 at 12:12 AM, Sergii Golovatiuk >> <sgolovat...@mirantis.com> wrote: >> > +1 for #2. >> > >> > ~Sergii >> > >> > >> > On Fri, Jun 20, 2014 at 1:21 AM, Andrey Danin <ada...@mirantis.com> >> wrote: >> >> >> >> +1 to Mike. Let the user provide actual credentials and use them in >> place. >> >> >> >> >> >> On Fri, Jun 20, 2014 at 2:01 AM, Mike Scherbakov >> >> <mscherba...@mirantis.com> wrote: >> >>> >> >>> I'm in favor of #2. I think users might not want to have their >> password >> >>> stored in Fuel Master node. >> >>> And if so, then it actually means we should not save it when user >> >>> provides it on HealthCheck tab. >> >>> >> >>> >> >>> On Thu, Jun 19, 2014 at 8:05 PM, Vitaly Kramskikh >> >>> <vkramsk...@mirantis.com> wrote: >> >>>> >> >>>> Hi folks, >> >>>> >> >>>> We have a bug which prevents OSTF from working if user changes a >> >>>> password which was using for the initial installation. I skimmed >> through the >> >>>> comments and it seems there are 2 viable options: >> >>>> >> >>>> Create a separate user just for OSTF during OpenStack installation >> >>>> Provide a field for a password in UI so user could provide actual >> >>>> password in case it was changed >> >>>> >> >>>> What do you guys think? Which options is better? >> >>>> >> >>>> -- >> >>>> Vitaly Kramskikh, >> >>>> Software Engineer, >> >>>> Mirantis, Inc. >> >>>> >> >>>> _______________________________________________ >> >>>> OpenStack-dev mailing list >> >>>> OpenStack-dev@lists.openstack.org >> >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> Mike Scherbakov >> >>> #mihgen >> >>> >> >>> >> >>> _______________________________________________ >> >>> OpenStack-dev mailing list >> >>> OpenStack-dev@lists.openstack.org >> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >>> >> >> >> >> >> >> >> >> -- >> >> Andrey Danin >> >> ada...@mirantis.com >> >> skype: gcon.monolake >> >> >> >> _______________________________________________ >> >> OpenStack-dev mailing list >> >> OpenStack-dev@lists.openstack.org >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> > >> > >> > _______________________________________________ >> > OpenStack-dev mailing list >> > OpenStack-dev@lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >> >> >> >> -- >> Andrew >> Mirantis >> Ceph community >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Software Engineer, Mirantis, Inc.
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
