Dear Saul, follow this document: https://docs.starlingx.io/deploy_install_guides/current/access_starlingx_ope... *Do not use* source /etc/platform/openrc . example: controller-0:~$ export OS_CLOUD=openstack_helm controller-0:~$ openstack flavor create --ram 2048 --disk 20 --vcpus 1 --public --id auto test.small +----------------------------+--------------------------------------+ | Field | Value | +----------------------------+--------------------------------------+ | OS-FLV-DISABLED:disabled | False | | OS-FLV-EXT-DATA:ephemeral | 0 | | disk | 20 | | id | 2987b202-e340-4a0a-a234-36612fc4873a | | name | test.small | | os-flavor-access:is_public | True | | properties | | | ram | 2048 | | rxtx_factor | 1.0 | | swap | | | vcpus | 1 | +----------------------------+--------------------------------------+ controller-0:~$ Saul Wold <sgw@linux.intel.com> 於 2019年9月17日 週二 上午9:44寫道：
On 9/16/19 5:58 PM, Sun, Austin wrote:
Hi Saul: I think your env is still in platform keystone env, not Openstack keystone env yet. 1) could you check 'system application-list' if stx-openstack application has been applied ? Yes, stx-openstack is fully applied.
2) check "/etc/openstack/clouds.yaml" existing or not ? Yes, there is a clouds.yaml file.
3) if 1) and 2) are ok, you can 'sudo su' to switch root user , 'export OS_CLOUD=openstack_helm", and 'openstack flavor list' or create flavor.
Yes, I was able to do this as root user, I thought everything could be done as the sysadmin user with no sudo or root requirements.
Am I missing some setup still?
Sau!
Thanks. BR Austin Sun.
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Tuesday, September 17, 2019 5:58 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Creating flavor fails
On 9/16/19 2:48 PM, Dean Troyer wrote:
On Mon, Sep 16, 2019 at 4:43 PM Saul Wold <sgw@linux.intel.com> wrote:
internal endpoint for compute service in RegionOne region not found
What endpoints do you have for Compute in your service catalog? Check with:
openstack catalog show compute
I am not sure why it is trying to use an internal endpoint there, that may not be accessible depending on where you run that command.
Well, seems I have no compute services!
"service compute not found"
I have set this up as an AIO-Simplex, the ansible playbook completed correctly and I followed up with the slew of commands to provision and unlock the controller-0 node.
dt
openstack catalog list
+----------+-----------------+------------------------------------------+
| Name | Type | Endpoints |
+----------+-----------------+------------------------------------------+
| fm | faultmanagement | RegionOne | | | | public: http://10.23.90.131:18002 | | | | RegionOne | | | | internal: http://192.168.204.2:18002 | | | | RegionOne | | | | admin: http://192.168.204.2:18002 | | | | | | barbican | key-manager | RegionOne | | | | public: http://10.23.90.131:9311 | | | | RegionOne | | | | internal: http://192.168.204.2:9311 | | | | RegionOne | | | | admin: http://192.168.204.2:9311 | | | | | | keystone | identity | RegionOne | | | | public: http://10.23.90.131:5000/v3 | | | | RegionOne | | | | internal: http://192.168.204.2:5000/v3 | | | | RegionOne | | | | admin: http://192.168.204.2:5000/v3 | | | | | | sysinv | platform | RegionOne | | | | public: http://10.23.90.131:6385/v1 | | | | RegionOne | | | | internal: http://192.168.204.2:6385/v1 | | | | RegionOne | | | | admin: http://192.168.204.2:6385/v1 | | | | | | patching | patching | RegionOne | | | | public: http://10.23.90.131:15491 | | | | RegionOne | | | | internal: http://192.168.204.2:5491 | | | | RegionOne | | | | admin: http://192.168.204.2:5491 | | | | | | vim | nfv | RegionOne | | | | public: http://10.23.90.131:4545 | | | | RegionOne | | | | internal: http://192.168.204.2:4545 | | | | RegionOne | | | | admin: http://192.168.204.2:4545 | | | | | | smapi | smapi | RegionOne | | | | public: http://10.23.90.131:7777 | | | | RegionOne | | | | internal: http://192.168.204.2:7777 | | | | RegionOne | | | | admin: http://192.168.204.2:7777 | | | | |
+----------+-----------------+------------------------------------------+
_______________________________________________ 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