Re: [Starlingx-discuss] Re-branding wrsroot proposal
sysadmin +1 -----Original Message----- From: Xie, Cindy [mailto:cindy.xie@intel.com] Sent: May 7, 2019 10:42 To: Bujold, Kristine <Kristine.Bujold@windriver.com>; Penney, Don <Don.Penney@windriver.com>; Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal Sysadmin + 1, easier to spell then deployadmin. -----Original Message----- From: Bujold, Kristine [mailto:Kristine.Bujold@windriver.com] Sent: Tuesday, May 7, 2019 10:41 PM To: Penney, Don <Don.Penney@windriver.com>; Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal sysadmin +1 -----Original Message----- From: Penney, Don [mailto:Don.Penney@windriver.com] Sent: Tuesday, May 7, 2019 10:38 AM To: Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal 3 characters ;) -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Tuesday, May 07, 2019 10:36 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal On 5/7/19 6:51 AM, Penney, Don wrote:
I'd vote -1 on deployadmin based on length alone. It would be nice to keep it short... less typing :)
It's only 2 characters longer than sysadmin and it is descriptive of the account. Just saying, no vote yet from me.. Sau!
-----Original Message----- From: Shuquan Huang [mailto:huang.shuquan@99cloud.net] Sent: Tuesday, May 07, 2019 3:44 AM To: Saul Wold Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
sysadmin +1
On May 7, 2019, at 6:24 AM, Saul Wold <sgw@linux.intel.com> wrote:
On 5/6/19 2:43 PM, Perez Carranza, Jose wrote:
What about 'deployadmin' ? That's an interesting alternative.
Sau!
Regards, José
-----Original Message----- From: Jim Somerville [mailto:jim.somerville@windriver.com] Sent: Monday, May 6, 2019 4:08 PM To: Dean Troyer <dtroyer@gmail.com>; Wensley, Barton <Barton.Wensley@windriver.com> Cc: Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
On Mon, May 6, 2019 at 1:06 PM Wensley, Barton <Barton.Wensley@windriver.com> wrote:
I guess I'm less concerned about using stx or starlingx than others. Obviously "wrs" is bad since it is tied to a company. But it seems common practice to use
On 2019-05-06 2:32 p.m., Dean Troyer wrote: the project name for the default user (think nova, neutron, glance, etc...).
The only reason I'd be reluctant to include a project identifier is because those things can change and this is just painful enough to not want to do again.
'admin' has other uses at the OS level, we need to be clear enough to not cause confusion there. Unless it has other similar uses 'sysadmin' is the best I have heard and I do not have a better suggestion.
Just to be devil's advocate here, sysadmin could easily already be in use on a future port of this stuff to another platform.
From a security standpoint, it would be on an easily guessed list of userids for black hat penetration testing.
It also shows up on the Big Username Blacklist.
https://github.com/marteinn/The-Big-Username- Blacklist/blob/master/list_raw.txt
-Jim
dt
Unless we want to use 'bikeshed' :)
_______________________________________________ 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
_______________________________________________ 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 _______________________________________________ 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 ------------------------------ Message: 2 Date: Tue, 7 May 2019 10:45:34 -0400 From: Michel Thebeau <michel.thebeau@windriver.com> To: Marcel Schaible <marcel@schaible-consulting.de>, <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Duplex: CEPH HEALTH_WARN after initial unlock of controller-0 Message-ID: <1557240334.3107.17.camel@windriver.com> Content-Type: text/plain; charset="UTF-8" Hi Marcel, Until the second node of the duplex configuration is configured and unlocked one expects the ceph cluster would be "unhealthy", yes. === It seems to me that the documentation is not obvious on that subject, but I'm not sure it needs to be. If I understand the examples correctly, on AIO-Simplex (one node), we set the "Ceph pool replication to 1. This step applies to AIO-SX only.", and therefore we expect ceph to become healthy for the simplex configuration. But with duplex, your pool replication is 2... so it is waiting for the second cluster node to come up. Duplex instruction: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnAIOD X#Configure_Ceph_for_Controller-0 Duplex then refers to a portion of simplex instruction for ceph configuration https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Confi gure_Ceph_for_Controller-0 M On Thu, 2019-05-02 at 15:20 +0200, Marcel Schaible wrote:
Hi,
after unlocking controller-0 in a Duplex configuration ceph shows an HEALTH_WARN:
[wrsroot@controller-0 ~(keystone_admin)]$ ceph -s cluster b6a2009b-7857-4bb6-835a-479b6ececb63 health HEALTH_WARN 448 pgs degraded 448 pgs stuck unclean 448 pgs undersized recovery 1116/2232 objects degraded (50.000%) monmap e1: 1 mons at {controller=172.27.1.100:6789/0} election epoch 5, quorum 0 controller osdmap e22: 2 osds: 1 up, 1 in flags sortbitwise,require_jewel_osds pgmap v1976: 448 pgs, 7 pools, 1588 bytes data, 1116 objects 91396 kB used, 952 GB / 952 GB avail 1116/2232 objects degraded (50.000%) 448 active+undersized+degraded
Is this expected and when should the health status switch to HEALTH_OK?
We use the image from 20190429.
Thanks
Marcel
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
------------------------------ Message: 3 Date: Tue, 7 May 2019 07:52:50 -0700 From: Saul Wold <sgw@linux.intel.com> To: "Penney, Don" <Don.Penney@windriver.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal Message-ID: <e98ae9c6-c75f-6bac-3c2d-ddfa7e45d78e@linux.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed On 5/7/19 7:37 AM, Penney, Don wrote:
3 characters ;)
ENOTAWAKE! Alex suggested shortening admin -> adm, good thought sysadm deployadm cloudadm edgeadm A rif on Controller: ctrladm conadm Trying new terms! Sau!
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Tuesday, May 07, 2019 10:36 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
On 5/7/19 6:51 AM, Penney, Don wrote:
I'd vote -1 on deployadmin based on length alone. It would be nice to keep it short... less typing :)
It's only 2 characters longer than sysadmin and it is descriptive of the account.
Just saying, no vote yet from me..
Sau!
-----Original Message----- From: Shuquan Huang [mailto:huang.shuquan@99cloud.net] Sent: Tuesday, May 07, 2019 3:44 AM To: Saul Wold Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
sysadmin +1
On May 7, 2019, at 6:24 AM, Saul Wold <sgw@linux.intel.com> wrote:
On 5/6/19 2:43 PM, Perez Carranza, Jose wrote:
What about 'deployadmin' ? That's an interesting alternative.
Sau!
Regards, José
-----Original Message----- From: Jim Somerville [mailto:jim.somerville@windriver.com] Sent: Monday, May 6, 2019 4:08 PM To: Dean Troyer <dtroyer@gmail.com>; Wensley, Barton <Barton.Wensley@windriver.com> Cc: Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
On Mon, May 6, 2019 at 1:06 PM Wensley, Barton <Barton.Wensley@windriver.com> wrote:
I guess I'm less concerned about using stx or starlingx than others. Obviously "wrs" is bad since it is tied to a company. But it seems common practice to use
On 2019-05-06 2:32 p.m., Dean Troyer wrote: the project name for the default user (think nova, neutron, glance, etc...).
The only reason I'd be reluctant to include a project identifier is because those things can change and this is just painful enough to not want to do again.
'admin' has other uses at the OS level, we need to be clear enough to not cause confusion there. Unless it has other similar uses 'sysadmin' is the best I have heard and I do not have a better suggestion.
Just to be devil's advocate here, sysadmin could easily already be in use on a future port of this stuff to another platform.
From a security standpoint, it would be on an easily guessed list of userids for black hat penetration testing.
It also shows up on the Big Username Blacklist.
https://github.com/marteinn/The-Big-Username- Blacklist/blob/master/list_raw.txt
-Jim
dt
Unless we want to use 'bikeshed' :)
_______________________________________________ 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
_______________________________________________ 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
------------------------------ Message: 4 Date: Tue, 7 May 2019 14:55:12 +0000 From: "Penney, Don" <Don.Penney@windriver.com> To: Saul Wold <sgw@linux.intel.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA494CE8@ALA-MBD.corp.ad.wrs.com> Content-Type: text/plain; charset="utf-8" Of those, I'd prefer "sysadm". It's very accurate and stays generic enough in its purpose. It's an account for system administration, with no implications about the purpose of the system or when it's used. So for me: sysadmin or sysadm (and I save 25% typing with sysadm!!) -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Tuesday, May 07, 2019 10:53 AM To: Penney, Don; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal On 5/7/19 7:37 AM, Penney, Don wrote:
3 characters ;)
ENOTAWAKE! Alex suggested shortening admin -> adm, good thought sysadm deployadm cloudadm edgeadm A rif on Controller: ctrladm conadm Trying new terms! Sau!
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Tuesday, May 07, 2019 10:36 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
On 5/7/19 6:51 AM, Penney, Don wrote:
I'd vote -1 on deployadmin based on length alone. It would be nice to keep it short... less typing :)
It's only 2 characters longer than sysadmin and it is descriptive of the account.
Just saying, no vote yet from me..
Sau!
-----Original Message----- From: Shuquan Huang [mailto:huang.shuquan@99cloud.net] Sent: Tuesday, May 07, 2019 3:44 AM To: Saul Wold Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
sysadmin +1
On May 7, 2019, at 6:24 AM, Saul Wold <sgw@linux.intel.com> wrote:
On 5/6/19 2:43 PM, Perez Carranza, Jose wrote:
What about 'deployadmin' ? That's an interesting alternative.
Sau!
Regards, José
-----Original Message----- From: Jim Somerville [mailto:jim.somerville@windriver.com] Sent: Monday, May 6, 2019 4:08 PM To: Dean Troyer <dtroyer@gmail.com>; Wensley, Barton <Barton.Wensley@windriver.com> Cc: Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
On Mon, May 6, 2019 at 1:06 PM Wensley, Barton <Barton.Wensley@windriver.com> wrote:
I guess I'm less concerned about using stx or starlingx than others. Obviously "wrs" is bad since it is tied to a company. But it seems common practice to use
On 2019-05-06 2:32 p.m., Dean Troyer wrote: the project name for the default user (think nova, neutron, glance, etc...).
The only reason I'd be reluctant to include a project identifier is because those things can change and this is just painful enough to not want to do again.
'admin' has other uses at the OS level, we need to be clear enough to not cause confusion there. Unless it has other similar uses 'sysadmin' is the best I have heard and I do not have a better suggestion.
Just to be devil's advocate here, sysadmin could easily already be in use on a future port of this stuff to another platform.
From a security standpoint, it would be on an easily guessed list of userids for black hat penetration testing.
It also shows up on the Big Username Blacklist.
https://github.com/marteinn/The-Big-Username- Blacklist/blob/master/list_raw.txt
-Jim
dt
Unless we want to use 'bikeshed' :)
_______________________________________________ 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
_______________________________________________ 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
------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 12, Issue 35 *************************************************
"admin" +1 It's shorter than sysadmin. ________________________________________ From: Liu, Tao [Tao.Liu@windriver.com] Sent: Tuesday, May 07, 2019 10:36 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal sysadmin +1 -----Original Message----- From: Xie, Cindy [mailto:cindy.xie@intel.com] Sent: May 7, 2019 10:42 To: Bujold, Kristine <Kristine.Bujold@windriver.com>; Penney, Don <Don.Penney@windriver.com>; Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal Sysadmin + 1, easier to spell then deployadmin. -----Original Message----- From: Bujold, Kristine [mailto:Kristine.Bujold@windriver.com] Sent: Tuesday, May 7, 2019 10:41 PM To: Penney, Don <Don.Penney@windriver.com>; Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal sysadmin +1 -----Original Message----- From: Penney, Don [mailto:Don.Penney@windriver.com] Sent: Tuesday, May 7, 2019 10:38 AM To: Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal 3 characters ;) -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Tuesday, May 07, 2019 10:36 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal On 5/7/19 6:51 AM, Penney, Don wrote:
I'd vote -1 on deployadmin based on length alone. It would be nice to keep it short... less typing :)
It's only 2 characters longer than sysadmin and it is descriptive of the account. Just saying, no vote yet from me.. Sau!
-----Original Message----- From: Shuquan Huang [mailto:huang.shuquan@99cloud.net] Sent: Tuesday, May 07, 2019 3:44 AM To: Saul Wold Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
sysadmin +1
On May 7, 2019, at 6:24 AM, Saul Wold <sgw@linux.intel.com> wrote:
On 5/6/19 2:43 PM, Perez Carranza, Jose wrote:
What about 'deployadmin' ? That's an interesting alternative.
Sau!
Regards, José
-----Original Message----- From: Jim Somerville [mailto:jim.somerville@windriver.com] Sent: Monday, May 6, 2019 4:08 PM To: Dean Troyer <dtroyer@gmail.com>; Wensley, Barton <Barton.Wensley@windriver.com> Cc: Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
On Mon, May 6, 2019 at 1:06 PM Wensley, Barton <Barton.Wensley@windriver.com> wrote:
I guess I'm less concerned about using stx or starlingx than others. Obviously "wrs" is bad since it is tied to a company. But it seems common practice to use
On 2019-05-06 2:32 p.m., Dean Troyer wrote: the project name for the default user (think nova, neutron, glance, etc...).
The only reason I'd be reluctant to include a project identifier is because those things can change and this is just painful enough to not want to do again.
'admin' has other uses at the OS level, we need to be clear enough to not cause confusion there. Unless it has other similar uses 'sysadmin' is the best I have heard and I do not have a better suggestion.
Just to be devil's advocate here, sysadmin could easily already be in use on a future port of this stuff to another platform.
From a security standpoint, it would be on an easily guessed list of userids for black hat penetration testing.
It also shows up on the Big Username Blacklist.
https://github.com/marteinn/The-Big-Username- Blacklist/blob/master/list_raw.txt
-Jim
dt
Unless we want to use 'bikeshed' :)
_______________________________________________ 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
_______________________________________________ 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 _______________________________________________ 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 ------------------------------ Message: 2 Date: Tue, 7 May 2019 10:45:34 -0400 From: Michel Thebeau <michel.thebeau@windriver.com> To: Marcel Schaible <marcel@schaible-consulting.de>, <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Duplex: CEPH HEALTH_WARN after initial unlock of controller-0 Message-ID: <1557240334.3107.17.camel@windriver.com> Content-Type: text/plain; charset="UTF-8" Hi Marcel, Until the second node of the duplex configuration is configured and unlocked one expects the ceph cluster would be "unhealthy", yes. === It seems to me that the documentation is not obvious on that subject, but I'm not sure it needs to be. If I understand the examples correctly, on AIO-Simplex (one node), we set the "Ceph pool replication to 1. This step applies to AIO-SX only.", and therefore we expect ceph to become healthy for the simplex configuration. But with duplex, your pool replication is 2... so it is waiting for the second cluster node to come up. Duplex instruction: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnAIOD X#Configure_Ceph_for_Controller-0 Duplex then refers to a portion of simplex instruction for ceph configuration https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Confi gure_Ceph_for_Controller-0 M On Thu, 2019-05-02 at 15:20 +0200, Marcel Schaible wrote:
Hi,
after unlocking controller-0 in a Duplex configuration ceph shows an HEALTH_WARN:
[wrsroot@controller-0 ~(keystone_admin)]$ ceph -s cluster b6a2009b-7857-4bb6-835a-479b6ececb63 health HEALTH_WARN 448 pgs degraded 448 pgs stuck unclean 448 pgs undersized recovery 1116/2232 objects degraded (50.000%) monmap e1: 1 mons at {controller=172.27.1.100:6789/0} election epoch 5, quorum 0 controller osdmap e22: 2 osds: 1 up, 1 in flags sortbitwise,require_jewel_osds pgmap v1976: 448 pgs, 7 pools, 1588 bytes data, 1116 objects 91396 kB used, 952 GB / 952 GB avail 1116/2232 objects degraded (50.000%) 448 active+undersized+degraded
Is this expected and when should the health status switch to HEALTH_OK?
We use the image from 20190429.
Thanks
Marcel
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
------------------------------ Message: 3 Date: Tue, 7 May 2019 07:52:50 -0700 From: Saul Wold <sgw@linux.intel.com> To: "Penney, Don" <Don.Penney@windriver.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal Message-ID: <e98ae9c6-c75f-6bac-3c2d-ddfa7e45d78e@linux.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed On 5/7/19 7:37 AM, Penney, Don wrote:
3 characters ;)
ENOTAWAKE! Alex suggested shortening admin -> adm, good thought sysadm deployadm cloudadm edgeadm A rif on Controller: ctrladm conadm Trying new terms! Sau!
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Tuesday, May 07, 2019 10:36 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
On 5/7/19 6:51 AM, Penney, Don wrote:
I'd vote -1 on deployadmin based on length alone. It would be nice to keep it short... less typing :)
It's only 2 characters longer than sysadmin and it is descriptive of the account.
Just saying, no vote yet from me..
Sau!
-----Original Message----- From: Shuquan Huang [mailto:huang.shuquan@99cloud.net] Sent: Tuesday, May 07, 2019 3:44 AM To: Saul Wold Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
sysadmin +1
On May 7, 2019, at 6:24 AM, Saul Wold <sgw@linux.intel.com> wrote:
On 5/6/19 2:43 PM, Perez Carranza, Jose wrote:
What about 'deployadmin' ? That's an interesting alternative.
Sau!
Regards, José
-----Original Message----- From: Jim Somerville [mailto:jim.somerville@windriver.com] Sent: Monday, May 6, 2019 4:08 PM To: Dean Troyer <dtroyer@gmail.com>; Wensley, Barton <Barton.Wensley@windriver.com> Cc: Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
On Mon, May 6, 2019 at 1:06 PM Wensley, Barton <Barton.Wensley@windriver.com> wrote:
I guess I'm less concerned about using stx or starlingx than others. Obviously "wrs" is bad since it is tied to a company. But it seems common practice to use
On 2019-05-06 2:32 p.m., Dean Troyer wrote: the project name for the default user (think nova, neutron, glance, etc...).
The only reason I'd be reluctant to include a project identifier is because those things can change and this is just painful enough to not want to do again.
'admin' has other uses at the OS level, we need to be clear enough to not cause confusion there. Unless it has other similar uses 'sysadmin' is the best I have heard and I do not have a better suggestion.
Just to be devil's advocate here, sysadmin could easily already be in use on a future port of this stuff to another platform.
From a security standpoint, it would be on an easily guessed list of userids for black hat penetration testing.
It also shows up on the Big Username Blacklist.
https://github.com/marteinn/The-Big-Username- Blacklist/blob/master/list_raw.txt
-Jim
dt
Unless we want to use 'bikeshed' :)
_______________________________________________ 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
_______________________________________________ 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
------------------------------ Message: 4 Date: Tue, 7 May 2019 14:55:12 +0000 From: "Penney, Don" <Don.Penney@windriver.com> To: Saul Wold <sgw@linux.intel.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA494CE8@ALA-MBD.corp.ad.wrs.com> Content-Type: text/plain; charset="utf-8" Of those, I'd prefer "sysadm". It's very accurate and stays generic enough in its purpose. It's an account for system administration, with no implications about the purpose of the system or when it's used. So for me: sysadmin or sysadm (and I save 25% typing with sysadm!!) -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Tuesday, May 07, 2019 10:53 AM To: Penney, Don; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal On 5/7/19 7:37 AM, Penney, Don wrote:
3 characters ;)
ENOTAWAKE! Alex suggested shortening admin -> adm, good thought sysadm deployadm cloudadm edgeadm A rif on Controller: ctrladm conadm Trying new terms! Sau!
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Tuesday, May 07, 2019 10:36 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
On 5/7/19 6:51 AM, Penney, Don wrote:
I'd vote -1 on deployadmin based on length alone. It would be nice to keep it short... less typing :)
It's only 2 characters longer than sysadmin and it is descriptive of the account.
Just saying, no vote yet from me..
Sau!
-----Original Message----- From: Shuquan Huang [mailto:huang.shuquan@99cloud.net] Sent: Tuesday, May 07, 2019 3:44 AM To: Saul Wold Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
sysadmin +1
On May 7, 2019, at 6:24 AM, Saul Wold <sgw@linux.intel.com> wrote:
On 5/6/19 2:43 PM, Perez Carranza, Jose wrote:
What about 'deployadmin' ? That's an interesting alternative.
Sau!
Regards, José
-----Original Message----- From: Jim Somerville [mailto:jim.somerville@windriver.com] Sent: Monday, May 6, 2019 4:08 PM To: Dean Troyer <dtroyer@gmail.com>; Wensley, Barton <Barton.Wensley@windriver.com> Cc: Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
On Mon, May 6, 2019 at 1:06 PM Wensley, Barton <Barton.Wensley@windriver.com> wrote:
I guess I'm less concerned about using stx or starlingx than others. Obviously "wrs" is bad since it is tied to a company. But it seems common practice to use
On 2019-05-06 2:32 p.m., Dean Troyer wrote: the project name for the default user (think nova, neutron, glance, etc...).
The only reason I'd be reluctant to include a project identifier is because those things can change and this is just painful enough to not want to do again.
'admin' has other uses at the OS level, we need to be clear enough to not cause confusion there. Unless it has other similar uses 'sysadmin' is the best I have heard and I do not have a better suggestion.
Just to be devil's advocate here, sysadmin could easily already be in use on a future port of this stuff to another platform.
From a security standpoint, it would be on an easily guessed list of userids for black hat penetration testing.
It also shows up on the Big Username Blacklist.
https://github.com/marteinn/The-Big-Username- Blacklist/blob/master/list_raw.txt
-Jim
dt
Unless we want to use 'bikeshed' :)
_______________________________________________ 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
_______________________________________________ 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
------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 12, Issue 35 ************************************************* _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (2)
-
Liu, Tao
-
Poncea, Ovidiu