Re: [Starlingx-discuss] the way to enable swift in starlingx

2 Dec 2019

      Sorry for the slow response. I was on vacation last week.

The following are from my testing notes when enabling for STX 2.0. This has
Also been verified with the latest master build for STX 3.0

NOTES: 
 - Check for any additional platform alarms. I have seen instances when the
   application apply (after enabling the ceph-rgw chart) will timeout due to
   high platform CPU usage. A second reapply will be successful.
 - You can disable the ceph-rgw helm chart and re-apply the application to
   remove helm release but you will need to manually remove the containerized
   keystone endpoint as the helm release removal doesn't clean them up.

Bob

----------------

For swift to be enabled two services need to be enabled:
 - The radosgw platform service (to enable the Ceph Rados Gateway for object
   storage)
 - The ceph-rgw helm chart to enable the swift endpoints in containerized
   openstack

# Rados Gateway will be disabled by default on a freshly installed system
$ source /etc/platform/openrc
[sysadmin@controller-0 ~(keystone_admin)]$ system service-parameter-list --service radosgw
+--------------------------------------+---------+---------+-----------------+-------+-------------+----------+
| uuid                                 | service | section | name            | value | personality | resource |
+--------------------------------------+---------+---------+-----------------+-------+-------------+----------+
| 8357f029-6ad6-4a1e-a2f3-5b969dcb7541 | radosgw | config  | fs_size_mb      | 25    | None        | None     |
| 9eca56c3-b6b7-4cc5-8981-495611e8839a | radosgw | config  | service_enabled | false | None        | None     |
+--------------------------------------+---------+---------+-----------------+-------+-------------+----------+

# And the openstack application will not be installed
[sysadmin@controller-0 ~(keystone_admin)]$ system application-list
+---------------------+---------+-------------------------------+---------------+---------+-----------+
| application         | version | manifest name                 | manifest file | status  | progress  |
+---------------------+---------+-------------------------------+---------------+---------+-----------+
| platform-integ-apps | 1.0-7   | platform-integration-manifest | manifest.yaml | applied | completed |
+---------------------+---------+-------------------------------+---------------+---------+-----------+

# Upload the stx-openstack application
[sysadmin@controller-0 ~(keystone_admin)]$ system application-upload stx-openstack-1.0-17.tgz
+---------------+----------------------------------+
| Property      | Value                            |
+---------------+----------------------------------+
| active        | False                            |
| app_version   | 1.0-17                           |
| created_at    | 2019-07-31T07:41:20.852112+00:00 |
| manifest_file | stx-openstack.yaml               |
| manifest_name | armada-manifest                  |
| name          | stx-openstack                    |
| progress      | None                             |
| status        | uploading                        |
| updated_at    | None                             |
+---------------+----------------------------------+

# Verify that the application was successfully uploaded
[sysadmin@controller-0 ~(keystone_admin)]$ system application-list
+---------------------+---------+-------------------------------+--------------------+----------+-----------+
| application         | version | manifest name                 | manifest file      | status   | progress  |
+---------------------+---------+-------------------------------+--------------------+----------+-----------+
| platform-integ-apps | 1.0-7   | platform-integration-manifest | manifest.yaml      | applied  | completed |
| stx-openstack       | 1.0-17  | armada-manifest               | stx-openstack.yaml | uploaded | completed |
+---------------------+---------+-------------------------------+--------------------+----------+-----------+

# The ceph-rgw chart is disabled by default as part of the stx-openstack upload
[sysadmin@controller-0 ~(keystone_admin)]$ system helm-override-list stx-openstack --long | grep -e enabled -e ceph-rgw -e+
+---------------------+--------------------------------+---------------+
| chart name          | overrides namespaces           | chart enabled |
+---------------------+--------------------------------+---------------+
| ceph-rgw            | [u'openstack']                 | [False]       |
+---------------------+--------------------------------+---------------+

# Apply the application
[sysadmin@controller-0 ~(keystone_admin)]$ system application-apply stx-openstack
+---------------+----------------------------------+
| Property      | Value                            |
+---------------+----------------------------------+
| active        | False                            |
| app_version   | 1.0-17                           |
| created_at    | 2019-07-31T07:41:20.852112+00:00 |
| manifest_file | stx-openstack.yaml               |
| manifest_name | armada-manifest                  |
| name          | stx-openstack                    |
| progress      | None                             |
| status        | applying                         |
| updated_at    | 2019-07-31T07:42:01.460523+00:00 |
+---------------+----------------------------------+

# Verify that the application is applied
[sysadmin@controller-0 ~(keystone_admin)]$ system application-list
+---------------------+---------+-------------------------------+--------------------+---------+-----------+
| application         | version | manifest name                 | manifest file      | status  | progress  |
+---------------------+---------+-------------------------------+--------------------+---------+-----------+
| platform-integ-apps | 1.0-7   | platform-integration-manifest | manifest.yaml      | applied | completed |
| stx-openstack       | 1.0-17  | armada-manifest               | stx-openstack.yaml | applied | completed |
+---------------------+---------+-------------------------------+--------------------+---------+-----------+

# Enable the radosgw on the platform.
#  NOTE: that can be done at any time, with or without the stx-openstack uploaded and/or applied

# Check that there is no config out-of-date alarms
[sysadmin@controller-0 ~(keystone_admin)]$ fm alarm-list | grep 250.001

[sysadmin@controller-0 ~(keystone_admin)]$ system service-parameter-modify radosgw config  service_enabled=true
+-------------+--------------------------------------+
| Property    | Value                                |
+-------------+--------------------------------------+
| uuid        | 9eca56c3-b6b7-4cc5-8981-495611e8839a |
| service     | radosgw                              |
| section     | config                               |
| name        | service_enabled                      |
| value       | true                                 |
| personality | None                                 |
| resource    | None                                 |
+-------------+--------------------------------------+

# Observe that there is a config out-of-date alarm
[sysadmin@controller-0 ~(keystone_admin)]$ fm alarm-list | grep 250.001
| 250.001  | controller-0 Configuration is out-of-date.                           | host=controller-0 | major    | 2019-07-31T07:43:01.  |

# Apply the change
[sysadmin@controller-0 ~(keystone_admin)]$ system service-parameter-apply radosgw
Applying radosgw service parameters

# monitor for when the alarm clears
[sysadmin@controller-0 ~(keystone_admin)]$ watch -n 5 "fm alarm-list | grep 250.001"

# Enable the ceph-rgw chart
[sysadmin@controller-0 ~(keystone_admin)]$ system helm-override-list stx-openstack --long | grep -e enabled -e ceph-rgw -e+
+---------------------+--------------------------------+---------------+
| chart name          | overrides namespaces           | chart enabled |
+---------------------+--------------------------------+---------------+
| ceph-rgw            | [u'openstack']                 | [False]       |
+---------------------+--------------------------------+---------------+

[sysadmin@controller-0 ~(keystone_admin)]$ system helm-chart-attribute-modify stx-openstack ceph-rgw openstack --enabled=true
+------------+--------------------+
| Property   | Value              |
+------------+--------------------+
| attributes | {u'enabled': True} |
| name       | ceph-rgw           |
| namespace  | openstack          |
+------------+--------------------+

[sysadmin@controller-0 ~(keystone_admin)]$ system helm-override-list stx-openstack --long | grep -e enabled -e ceph-rgw -e+
+---------------------+--------------------------------+---------------+
| chart name          | overrides namespaces           | chart enabled |
+---------------------+--------------------------------+---------------+
| ceph-rgw            | [u'openstack']                 | [True]        |
+---------------------+--------------------------------+---------------+

# reapply the app
[sysadmin@controller-0 ~(keystone_admin)]$ system application-apply stx-openstack
+---------------+----------------------------------+
| Property      | Value                            |
+---------------+----------------------------------+
| active        | True                             |
| app_version   | 1.0-17                           |
| created_at    | 2019-07-31T07:41:20.852112+00:00 |
| manifest_file | stx-openstack.yaml               |
| manifest_name | armada-manifest                  |
| name          | stx-openstack                    |
| progress      | None                             |
| status        | applying                         |
| updated_at    | 2019-07-31T08:31:50.558441+00:00 |
+---------------+----------------------------------+

# Monitor for when the application has been re-applied
[sysadmin@controller-0 ~(keystone_admin)]$ watch -n 5 system application-list
+---------------------+---------+-------------------------------+--------------------+---------+-----------+
| application         | version | manifest name                 | manifest file      | status  | progress  |
+---------------------+---------+-------------------------------+--------------------+---------+-----------+
| platform-integ-apps | 1.0-7   | platform-integration-manifest | manifest.yaml      | applied | completed |
| stx-openstack       | 1.0-17  | armada-manifest               | stx-openstack.yaml | applied | completed |
+---------------------+---------+-------------------------------+--------------------+---------+-----------+

# Observe swift is enable for the containerized services
[sysadmin@controller-0 ~(keystone_admin)]$ export OS_AUTH_URL=http://keystone.openstack.svc.cluster.local/v3
[sysadmin@controller-0 ~(keystone_admin)]$ openstack endpoint list | grep object
| 09a1414e413847e5b46807034f584628 | RegionOne | swift        | object-store   | True    | admin     | http://192.168.204.2:7480/swift/v1                                        |
| 57a7d77823704a89a352d14ec8563cde | RegionOne | swift        | object-store   | True    | public    | http://10.10.10.2:7480/swift/v1                                           |
| 57f65799d37f442fb3c816dee8b84f71 | RegionOne | swift        | object-store   | True    | internal  | http://192.168.204.2:7480/swift/v1                                        |

# But not the platform
[sysadmin@controller-0 ~(keystone_admin)]$ source /etc/platform/openrc
[sysadmin@controller-0 ~(keystone_admin)]$ openstack endpoint list | grep object 

On 12/2/19, 9:28 AM, "Chen, Haochuan Z" <haochuan.z.chen@intel.com> wrote:

    You should check in such way

    [sysadmin@controller-0 ~(keystone_admin)]$ openstack --os-username 'admin' --os-password 'Local.123' --os-project-name admin --os-auth-url http://keystone.openstack.svc.cluster.local/v3 --os-user-domain-name Default --os-project-domain-name Default --os-identity-api-version 3 --os-interface internal --os-region-name RegionOne endpoint list  | grep object
    | a67918db88604bcc87504c3ec72c745c | RegionOne | swift        | object-store    | True    | public    | http://10.10.10.3:7480/swift/v1                                           |
    | d0974532671d457995ccd5c8e2c5f5eb | RegionOne | swift        | object-store    | True    | admin     | http://192.168.204.1:7480/swift/v1                                        |
    | e096598cdbec45878240aa5ac75e2047 | RegionOne | swift        | object-store    | True    | internal  | http://192.168.204.1:7480/swift/v1                                        |
    [sysadmin@controller-0 ~(keystone_admin)]$

    BR!

    Martin, Chen
    SSP, Software Engineer
    021-61164330

    -----Original Message-----
    From: von Hoesslin, Volker <Volker.Hoesslin@swsn.de> 
    Sent: Monday, December 2, 2019 9:00 PM
    To: Chen, Haochuan Z <haochuan.z.chen@intel.com>; 'ji@sibyl.li' <ji@sibyl.li>
    Cc: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>; Hu, Yong <yong.hu@intel.com>
    Subject: AW: the way to enable swift in starlingx

    hi,
    thx for this code-snippets but doesnt work for me :( there are no errors but also no new endpoint...

    controller-0:~$ source /etc/platform/openrc
    [sysadmin@controller-0 ~(keystone_admin)]$ system service-parameter-modify radosgw config service_enabled=true
    +-------------+--------------------------------------+
    | Property    | Value                                |
    +-------------+--------------------------------------+
    | uuid        | ee200d06-d800-4dfa-83aa-b35d1fde61f6 |
    | service     | radosgw                              |
    | section     | config                               |
    | name        | service_enabled                      |
    | value       | true                                 |
    | personality | None                                 |
    | resource    | None                                 |
    +-------------+--------------------------------------+
    [sysadmin@controller-0 ~(keystone_admin)]$ system service-parameter-apply radosgw Applying radosgw service parameters
    [sysadmin@controller-0 ~(keystone_admin)]$ system helm-chart-attribute-modify stx-openstack ceph-rgw openstack --enabled=true
    +------------+--------------------+
    | Property   | Value              |
    +------------+--------------------+
    | attributes | {u'enabled': True} |
    | name       | ceph-rgw           |
    | namespace  | openstack          |
    +------------+--------------------+
    [sysadmin@controller-0 ~(keystone_admin)]$ system application-apply stx-openstack
    +---------------+----------------------------------+
    | Property      | Value                            |
    +---------------+----------------------------------+
    | active        | True                             |
    | app_version   | 1.0-17-centos-stable-latest      |
    | created_at    | 2019-11-18T16:21:19.076937+00:00 |
    | manifest_file | stx-openstack.yaml               |
    | manifest_name | armada-manifest                  |
    | name          | stx-openstack                    |
    | progress      | None                             |
    | status        | applying                         |
    | updated_at    | 2019-11-28T16:37:31.859690+00:00 |
    +---------------+----------------------------------+
    Please use 'system application-list' or 'system application-show stx-openstack' to view the current progress.
    [sysadmin@controller-0 ~(keystone_admin)]$ watch system application-show stx-openstack
    [sysadmin@controller-0 ~(keystone_admin)]$ openstack endpoint list | grep object
    [sysadmin@controller-0 ~(keystone_admin)]$
    [sysadmin@controller-0 ~(keystone_admin)]$ openstack endpoint list
    +----------------------------------+-----------+--------------+-----------------+---------+-----------+------------------------------+
    | ID                               | Region    | Service Name | Service Type    | Enabled | Interface | URL                          |
    +----------------------------------+-----------+--------------+-----------------+---------+-----------+------------------------------+
    | f279f864c46e469cafa16fd77d0605b0 | RegionOne | fm           | faultmanagement | True    | admin     | http://192.168.204.2:18002   |
    | aad37714717540e49af212768daf9258 | RegionOne | fm           | faultmanagement | True    | internal  | http://192.168.204.2:18002   |
    | 7a7a980041e94eda8e0575ec7f6472c2 | RegionOne | fm           | faultmanagement | True    | public    | http://10.10.10.2:18002      |
    | d7765db9214249e2ae97958043521061 | RegionOne | patching     | patching        | True    | admin     | http://192.168.204.2:5491    |
    | 678a5de6ff9044afacd145fbdad234a1 | RegionOne | patching     | patching        | True    | internal  | http://192.168.204.2:5491    |
    | 2c6e5794267844f4af577bc71183e0f7 | RegionOne | patching     | patching        | True    | public    | http://10.10.10.2:15491      |
    | b21e663dd3894ebb8465b4b8418f2a47 | RegionOne | vim          | nfv             | True    | admin     | http://192.168.204.2:4545    |
    | 185182d4b1e740ee9e6311a55791fed7 | RegionOne | vim          | nfv             | True    | internal  | http://192.168.204.2:4545    |
    | 63d6b149358b475eb97d97bd3414048e | RegionOne | vim          | nfv             | True    | public    | http://10.10.10.2:4545       |
    | 2cc7741368cd4ca1920322f601ece48c | RegionOne | smapi        | smapi           | True    | admin     | http://192.168.204.2:7777    |
    | 9bd331db8f9d455ab06ef7dc4dc79660 | RegionOne | smapi        | smapi           | True    | internal  | http://192.168.204.2:7777    |
    | bae82a84d6e94cd198ec2c73b2dba2c0 | RegionOne | smapi        | smapi           | True    | public    | http://10.10.10.2:7777       |
    | 594394a663c64fe484c097fcfbf8b2db | RegionOne | keystone     | identity        | True    | admin     | http://192.168.204.2:5000/v3 |
    | 3804a32d209a4a929cff8321c408fe5e | RegionOne | keystone     | identity        | True    | internal  | http://192.168.204.2:5000/v3 |
    | 69f30354ea1c407480de2a70719f65d5 | RegionOne | keystone     | identity        | True    | public    | http://10.10.10.2:5000/v3    |
    | 0a5686180b104c708e741048a5ddca86 | RegionOne | barbican     | key-manager     | True    | admin     | http://192.168.204.2:9311    |
    | b8243821ca9443b2ab1036a35157ba73 | RegionOne | barbican     | key-manager     | True    | internal  | http://192.168.204.2:9311    |
    | d7284357f1374940bee22a6207152f39 | RegionOne | barbican     | key-manager     | True    | public    | http://10.10.10.2:9311       |
    | da935387386442b995b1812b307e228a | RegionOne | sysinv       | platform        | True    | admin     | http://192.168.204.2:6385/v1 |
    | d135073f7952407fbccc113e2ebfc296 | RegionOne | sysinv       | platform        | True    | internal  | http://192.168.204.2:6385/v1 |
    | b54be3ccb9804af0bfc579a12ea5afcc | RegionOne | sysinv       | platform        | True    | public    | http://10.10.10.2:6385/v1    |
    +----------------------------------+-----------+--------------+-----------------+---------+-----------+------------------------------+

    any suggestions?

    greez & thx, volker...

    ________________________________________
    Von: Chen, Haochuan Z [haochuan.z.chen@intel.com]
    Gesendet: Montag, 2. Dezember 2019 05:52
    An: von Hoesslin, Volker; 'ji@sibyl.li'
    Cc: 'starlingx-discuss@lists.starlingx.io'; Hu, Yong
    Betreff: the way to enable swift in starlingx

    Hi

    system application-upload <openstack application tarball>

    system service-parameter-modify radosgw config  service_enabled=true

    system service-parameter-apply radosgw

    system helm-chart-attribute-modify stx-openstack ceph-rgw openstack --enabled=true

    system application-apply stx-openstack

    openstack endpoint list | grep object

    BR!

    -----Original Message-----
    From: Chen, Haochuan Z
    Sent: Thursday, November 28, 2019 10:12 AM
    To: starlingx-discuss@lists.starlingx.io
    Cc: Volker.Hoesslin@swsn.de; ji@sibyl.li
    Subject: swift enabling

    Hi

    I find there is voice to enable swift, why it was removed?

    Thanks!

    Message: 2
    Date: Mon, 25 Nov 2019 07:53:31 -0600
    From: joji vlogs <ji@sibyl.li>
    To: "starlingx-discuss@lists.starlingx.io"
            <starlingx-discuss@lists.starlingx.io>
    Subject: [Starlingx-discuss] Enabling Object Storage
    Message-ID:
            <CAHQOA=hsC+wQf+MOVLx6iPziPBvmqtbJJ4saogGqgTnb4byB_g@mail.gmail.com>
    Content-Type: text/plain; charset="utf-8"

    Hi all,

    I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand.

    My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error.

    Thank you and have a great day!

    Message: 3
    Date: Fri, 22 Nov 2019 14:14:15 +0000
    From: "von Hoesslin, Volker" <Volker.Hoesslin@swsn.de>
    To: "starlingx-discuss@lists.starlingx.io"
            <starlingx-discuss@lists.starlingx.io>
    Subject: [Starlingx-discuss] STX 2.0: swift?
    Message-ID: <DB39DAB5F762704A93D316F9CE7D021E42929584@emilio.sis.net>
    Content-Type: text/plain; charset="iso-8859-1"

    hi,
    how can i add the object storage (swift) feature to my current STX2.0 openstack?

    BR!

    Martin, Chen
    SSP, Software Engineer
    021-61164330

    -----Original Message-----
    From: starlingx-discuss-request@lists.starlingx.io <starlingx-discuss-request@lists.starlingx.io>
    Sent: Tuesday, November 26, 2019 12:05 AM
    To: starlingx-discuss@lists.starlingx.io
    Subject: Starlingx-discuss Digest, Vol 18, Issue 150

    Send Starlingx-discuss mailing list submissions to
            starlingx-discuss@lists.starlingx.io

    To subscribe or unsubscribe via the World Wide Web, visit
            http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
    or, via email, send a message with subject or body 'help' to
            starlingx-discuss-request@lists.starlingx.io

    You can reach the person managing the list at
            starlingx-discuss-owner@lists.starlingx.io

    When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..."

    Today's Topics:

       1. Re: controller filesystem (Waines, Greg)
       2. Enabling Object Storage (joji vlogs)
       3. Re: <BLOCKING> StarlingX 2.0 Account Locked for User (Andy Ning)

    ----------------------------------------------------------------------

    Message: 1
    Date: Mon, 25 Nov 2019 13:26:31 +0000
    From: "Waines, Greg" <Greg.Waines@windriver.com>
    To: Saul Wold <sgw@linux.intel.com>, "von Hoesslin, Volker"
            <Volker.Hoesslin@swsn.de>, "Sun, Austin" <austin.sun@intel.com>,
            "starlingx-discuss@lists.starlingx.io"
            <starlingx-discuss@lists.starlingx.io>, "Dale, Kristal"
            <kristal.dale@intel.com>
    Subject: Re: [Starlingx-discuss] controller filesystem
    Message-ID: <B514CD7A-7A7F-4051-9A62-F62193853B41@windriver.com>
    Content-Type: text/plain; charset="utf-8"

    Actually a section on managing filesystems on the controllers is planned for STX 3.0 ... based on the proposed TOC for the new Operations Guide.
    Greg

    From: Saul Wold <sgw@linux.intel.com>
    Date: Thursday, November 21, 2019 at 12:13 PM
    To: "von Hoesslin, Volker" <Volker.Hoesslin@swsn.de>, "Sun, Austin" <austin.sun@intel.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io>, "Dale, Kristal" <kristal.dale@intel.com>
    Subject: Re: [Starlingx-discuss] controller filesystem

    Kristal:

    We probably need a Story/Task added to the documentation to get the documentation of host-fs added in the right place.  This helps with filesystem re-sizing.

    Maybe it's already there.

    Sau!

    On 11/21/19 7:12 AM, von Hoesslin, Volker wrote:
    incredible !!! thats the point i have search! big thx!
    ------------------------------------------------------------------------
    *Von:* Sun, Austin [austin.sun@intel.com<mailto:austin.sun@intel.com>]
    *Gesendet:* Donnerstag, 21. November 2019 15:20
    *An:* von Hoesslin, Volker; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>
    *Betreff:* Re: [Starlingx-discuss] controller filesystem Hi Volker:
      From the email chain,
    http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005656.htm...
    You can probably the command line to change the size of docker lv Thanks.
    BR
    Austin Sun.
    *From:* von Hoesslin, Volker <Volker.Hoesslin@swsn.de<mailto:Volker.Hoesslin@swsn.de>>
    *Sent:* Thursday, November 21, 2019 9:20 PM
    *To:* starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>
    *Subject:* [Starlingx-discuss] controller filesystem hi, i trying to import some existing qcow2 images into my new installed STX 2.0.
    openstack image create --file /media/foobar.qcow2 --private --unprotected --disk-format qcow2 "foobar"
    all works fine, the image are available.
    now, i'm trying to create an new volume based on this images. if the images are <=6GB all works fine, but some images are very huge
    (10-200GB) and then it ends in an error. after some research i can see on controller the mount point
    /dev/mapper/cgts--vg-docker--lv      30G   11G   20G  35% /var/lib/docker
    increase the used storage. after fail "volume create" it goes back to given value 35%. in my oppinion, this mount point should resize to some value about 300-400GB, but how? in STX horizon backend
    (http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_t...)
    there is an "docker-distribution", but no docker-mount-point itself?
    btw, if i try to change the "docker-distribution" value to some other value (eg. 500GB via horizon backend), i got this error:
    *Error: *backup size of 60 is insufficient for host controller-1.
    Minimum backup size of 100 is required based upon glance size 20 and database size 20. Rejecting modification request.
    - see attachment -
    how can i increase the backup size to handle this error?!
    greez & thx, volker...
    _______________________________________________
    Starlingx-discuss mailing list
    Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io>
    http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

    _______________________________________________
    Starlingx-discuss mailing list
    Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io>
    http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20191125/053843ae/attachment-0001.html>

    ------------------------------

    Message: 2
    Date: Mon, 25 Nov 2019 07:53:31 -0600
    From: joji vlogs <ji@sibyl.li>
    To: "starlingx-discuss@lists.starlingx.io"
            <starlingx-discuss@lists.starlingx.io>
    Subject: [Starlingx-discuss] Enabling Object Storage
    Message-ID:
            <CAHQOA=hsC+wQf+MOVLx6iPziPBvmqtbJJ4saogGqgTnb4byB_g@mail.gmail.com>
    Content-Type: text/plain; charset="utf-8"

    Hi all,

    I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand.

    My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error.

    Thank you and have a great day!
    Austin Gillmann
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20191125/7f40d408/attachment-0001.html>

    ------------------------------

    Message: 3
    Date: Mon, 25 Nov 2019 11:05:19 -0500
    From: Andy Ning <andy.ning@windriver.com>
    To: <starlingx-discuss@lists.starlingx.io>
    Subject: Re: [Starlingx-discuss] <BLOCKING> StarlingX 2.0 Account
            Locked for User
    Message-ID: <8f8e6cad-0ad7-4be4-6693-a25e6cec93ad@windriver.com>
    Content-Type: text/plain; charset="utf-8"; format=flowed

    On 2019-11-25 12:00 AM, Yong Hu wrote:
    > Hi Anirudh,
    >
    > This issue is similar to this LP#1853017 [0], which was triggered the 
    > account locking if the password of Openstack user "admin" was changed.
    > In this LP, for unknown reason, "registry-token-server" daemon kept 
    > accessing "keystone" on host (not the instance in containers) with 
    > obsolete token and led to "admin" account locked after 5 attempts.
    >
    If registry token server keeps on accessing keystone with obsolete token, this could be a bug in the token server. Normally if a keystone client get a failed authentication, it should try to retrieve a new token by using username/password.

    Andy

    > Right now, I am debugging this issue.
    > Good thing is Cengn build 11/16 seemed not to have such a problem 
    > (LP#1853017).
    >
    > You might have a try with this version?
    > BTW: which cengn build were you using?
    >
    >
    > [0] https://bugs.launchpad.net/starlingx/+bug/1853017
    >
    > regards,
    > Yong
    >
    > On 2019/11/19 6:06 PM, Anirudh Gupta wrote:
    >> Hi Team,
    >>
    >> I have installed StarlingX 2.0 Duplex Bare Metal.
    >>
    >> I am trying to create 2 VM's and repeating this cycle a number of times.
    >>
    >> After using the setup for around half and hour, I am not longer able 
    >> to access the GUI.
    >>
    >> Ever though I type correct Username/Password, it gives an error of 
    >> Invalid Credentials.
    >>
    >> Then, I thought to use the CLI commands by following LOAD CLI section 
    >> given in link
    >>
    >> https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/
    >> access.html#local-cli
    >>
    >>
    >> But with this also, I am facing the same error
    >>
    >> controller-0:~$ export OS_CLOUD=openstack_helm
    >>
    >> controller-0:~$ openstack endpoint list
    >>
    >> The account is locked for user: 230578cde382430a8adac399afab1230.
    >> (HTTP 401) (Request-ID: req-6da6d59a-2edd-4f2b-a8bf-f13f2e423a77)
    >>
    >> Earlier this automatically started working after 5-7 mins.
    >>
    >> But this time, I am completely Blocked.
    >>
    >> I have also raised a bug regarding the same
    >>
    >> https://bugs.launchpad.net/starlingx/+bug/1853093
    >>
    >> Please suggest some pointers, so that I can unblock and resume my 
    >> activities.
    >>
    >> Regards
    >>
    >> Anirudh Gupta
    >>
    >> DISCLAIMER: This electronic message and all of its contents, contains 
    >> information which is privileged, confidential or otherwise protected 
    >> from disclosure. The information contained in this electronic mail 
    >> transmission is intended for use only by the individual or entity to 
    >> which it is addressed. If you are not the intended recipient or may 
    >> have received this electronic mail transmission in error, please 
    >> notify the sender immediately and delete / destroy all copies of this 
    >> electronic mail transmission without disclosing, copying, 
    >> distributing, forwarding, printing or retaining any part of it.
    >> Hughes Systique accepts no responsibility for loss or damage arising 
    >> from the use of the information transmitted by this email including 
    >> damage from virus.
    >>
    >> _______________________________________________
    >> 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

    ------------------------------

    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 18, Issue 150
    **************************************************

    _______________________________________________
    Starlingx-discuss mailing list
    Starlingx-discuss@lists.starlingx.io
    http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

Re: [Starlingx-discuss] the way to enable swift in starlingx

Church, Robert