On 2019-05-10 09:29 AM, Andy Ning wrote:
On 2019-05-10 12:19 AM, Saul Wold wrote:
I did my first pass and rebuild my ISO today, and I realized another item that needs tobe addressed, the sysadmin password! I vaugely remember seeing the encoded entry someplace and now of course I can't find it again.
If someone can point me to the location, I will apply a change there as well.
If you mean the encrypted password, they are in: /opt/platform/.keyring/19.01/python_keyring/crypted_pass.cfg
You can also use keyring command to get/set/del passwords from the keyring.
I may be misleading ... wrsroot is a local, per-host Operation System account, it is not in keyring. (keyring has openstack user accounts in it). Changing wrsroot password has to be done on active controller to propagate to all other unlocked-active hosts in the cluster. Andy
Andy
Good news is so far, I can boot and login to the C-0 node with sysadmin/old password.
Thanks in advance!
Sau!
On 5/8/19 10:16 AM, Saul Wold wrote:
We seem to be landing on "sysadmin" and I started to look at the changes, I forgot to point out we also needed to change the wrs_protected group name.
I suggest that we go with 'sys_protected' as the groupname unless there are other suggestions.
I will bring this up in tomorrow's TSC meeting so we can get it changed soon.
Thanks for all of your input.
Sau!
On 5/3/19 3:28 PM, Saul Wold wrote:
Folks,
We talked about some of the branding changes at the PTG just now and one item to try and tackle now for this release would be changing wrsroot to some alternative.
This will be a pretty mechanical change, it will touch the integ, config, metal, and update repos. There might be a couple places where this can be placed in a variable or parameter. There is currently a storyboard titled "Change wrsroot to stxuser" [0]. There was some initial discussion at the PTG regarding the new user name. We want to avoid stx, or starlingx and "root", in the name it should remain more generic.
One obvious choice is:
admin
Please reply with additional suggestions before next week's TSC (5/9).
Ultimately, this change will require changes to tests, test frameworks, scripts (such as deployment tools) and documentation.
[0] https://storyboard.openstack.org/#!/story/2004716
Thanks for your input.
Sau!
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr