PM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Fuel] [OSTF] OSTF stops working after
password is changed
I'm wondering if we can show all these windows ONLY if there is authz
failure with existing
I'm wondering if we can show all these windows ONLY if there is authz
failure with existing credentials from Nailgun.
So the flow would be: user clicks on Run tests button, healthcheck tries
to access OpenStack and fails. It shows up text fields to enter
tenant/user/pass with the message similar
] [Fuel] [OSTF] OSTF stops working after
password is changed
I'm wondering if we can show all these windows ONLY if there is authz
failure with existing credentials from Nailgun.
So the flow would be: user clicks on Run tests button, healthcheck tries
to access OpenStack and fails. It shows up text
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,
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
It is possible to change everything so username, password and tenant fields
Also this way we will be able to run tests not only as admin user
On Wed, Jun 25, 2014 at 12:29 PM, Vitaly Kramskikh vkramsk...@mirantis.com
wrote:
Dmitry,
Fields or field? Do we need to provide password only or
+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
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.
Hi folks,
We have a bug https://bugs.launchpad.net/fuel/+bug/1281838 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:
1. Create a separate user just for OSTF during
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
+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
11 matches
Mail list logo
