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