[Starlingx-discuss] [Container] Is 'nova boot' command still supported?

[Liu, Yang]

If you ever sourced to openrc file in the same shell, then the auth url in the openrc file will be used.
After sourcing to /etc/nova/openrc, if you want to switch back to containerized openstack cli's, you can export the os_auth_url to make sure the correct keystone is used.

export OS_AUTH_URL=http://keystone.openstack.svc.cluster.local/v3

BR,
Yang

From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com]
Sent: February-11-19 11:46 AM
To: Bailey, Henry Albert (Al); 'starlingx-discuss at lists.starlingx.io'
Subject: Re: [Starlingx-discuss] [Container] Is 'nova boot' command still supported?

Hi,

Yes, export OS_CLOUD=openstack_helm already applied.
Openstack commands work correctly but nova, glance, cinder are asking for user name, user id, project name, tenant id, etc.. I think some this parameters are defined on /etc/openstack/clouds.yaml, right?

Does clouds.yaml need extra parameters?
That's why also I am asking if nova, glance, cinder, etc commands won't be supported? In order to update to openstack command.

Regards.
Juan Carlos Alonso

From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com]
Sent: Monday, February 11, 2019 9:41 AM
To: 'starlingx-discuss at lists.starlingx.io' <starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] [Container] Is 'nova boot' command still supported?

I believe you are authenticating with the keystone that is on the controller, rather than the one that is running in the container.
Refer to this section of the wiki
https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Verify_the_cluster_endpoints

Once you are pointing at the nova that is running in the container, those nova commands should work as expected.

Al

From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com]
Sent: Monday, February 11, 2019 10:30 AM
To: 'starlingx-discuss at lists.starlingx.io'
Subject: [Starlingx-discuss] [Container] Is 'nova boot' command still supported?

Hi,

In order to launch instances from a volume snapshot, I use  nova boot command.
After deploy an STX containerized system this command is returning below error:

[wrsroot at controller-0 ~(keystone_admin)]$ nova boot -flavor <flavor_name> --snapshot <snapshot_name> --nic <net-id> <vm-name>

ERROR (ConnectFailure): Unable to establish connection to http://192.168.204.2:8774/v2.1/a4952fba408146b9b6cbe2e028da2708: HTTPConnectionPool(host='192.168.204.2', port=8774): Max retries exceeded with url: /v2.1/a4952fba408146b9b6cbe2e028da2708 (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7fdfd92b0650>: Failed to establish a new connection: [Errno 111] Connection refused',))

I tried with 'source /etc/nova/openrc' and 'source /etc/platform/openrc' authentication, both got the same issue.

Is this nova boot command still supported with containers?

Regards.
Juan Carlos Alonso
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190211/0bdd1a5f/attachment-0001.html>