Actually I have other question regarding our networking setup (not related
to this bug). We have trouble to access our instances from the outside.
Our provider has a pool of external floating IP. But when I configure an
external network in openstack to use them, I cannot ssh (port 22 is enabled
in our security group).
Can you point me to a good ressource for that ?
Thank you,
Le jeu. 13 févr. 2020 à 17:40, Pete Vander Giessen <
<email address hidden>> a écrit :
> If you're running commands via microstack.openstack, you don't need to
> download or source an .rc file. microstack.openstack is actually a
> wrapper script that sources
> /var/snap/microstack/common/etc/microstack.rc, and then executes your
> command via the openstack cli.
>
> Where did you download your .rc file from?
>
> ** Changed in: microstack
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1863137
>
> Title:
> enable to use to openstack-cli
>
> Status in MicroStack:
> Incomplete
>
> Bug description:
> Hi everyone and thanks for your work,
>
> So when trying to use openstack-cli, for example :
>
> microstack.openstack catalog list
>
> I get the following error:
>
> The request you have made requires authentication. (HTTP 401)
> (Request-ID: req-e69c05cc-efe0-4681-a867-aaec1160bfe3)
>
> I already downloaded the openstackRC file and sourced it. Are they other
> steps to do to authentificate ?
> Here is a copy of my openstackRC file :
>
> #!/usr/bin/env bash
> # To use an OpenStack cloud you need to authenticate against the Identity
> # service named keystone, which returns a **Token** and **Service
> Catalog**.
> # The catalog contains the endpoints for all services the user/tenant has
> # access to - such as Compute, Image Service, Identity, Object Storage,
> Block
> # Storage, and Networking (code-named nova, glance, keystone, swift,
> # cinder, and neutron).
> #
> # *NOTE*: Using the 3 *Identity API* does not necessarily mean any other
> # OpenStack API is version 3. For example, your cloud provider may
> implement
> # Image API v1.1, Block Storage API v2, and Compute API v2.0.
> OS_AUTH_URL is
> # only for the Identity API served through keystone.
> export OS_AUTH_URL=http://****:5000/v3/
> # With the addition of Keystone we have standardized on the term
> **project**
> # as the entity that owns the resources.
> export OS_PROJECT_ID=a7845351d0204e71b7f34c6386a3bf5b
> export OS_PROJECT_NAME="admin"
> export OS_USER_DOMAIN_NAME="Default"
> if [ -z "$OS_USER_DOMAIN_NAME" ]; then unset OS_USER_DOMAIN_NAME; fi
> export OS_PROJECT_DOMAIN_ID="default"
> if [ -z "$OS_PROJECT_DOMAIN_ID" ]; then unset OS_PROJECT_DOMAIN_ID; fi
> # unset v2.0 items in case set
> unset OS_TENANT_ID
> unset OS_TENANT_NAME
> # In addition to the owning entity (tenant), OpenStack stores the entity
> # performing the action as the **user**.
> export OS_USERNAME="****"
> # With Keystone you pass the keystone password.
> export OS_PASSWORD="****"
> # If your configuration has multiple regions, we set that information
> here.
> # OS_REGION_NAME is optional and only valid in certain environments.
> export OS_REGION_NAME="microstack"
> # Don't leave a blank variable, unset it if it was empty
> if [ -z "$OS_REGION_NAME" ]; then unset OS_REGION_NAME; fi
> export OS_INTERFACE=public
> export OS_IDENTITY_API_VERSION=3
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/microstack/+bug/1863137/+subscriptions
>
Hi pete
Actually I have other question regarding our networking setup (not related
to this bug). We have trouble to access our instances from the outside.
Our provider has a pool of external floating IP. But when I configure an
external network in openstack to use them, I cannot ssh (port 22 is enabled
in our security group).
Can you point me to a good ressource for that ?
Thank you,
Le jeu. 13 févr. 2020 à 17:40, Pete Vander Giessen <
<email address hidden>> a écrit :
> If you're running commands via microstack. openstack, you don't need to openstack is actually a microstack/ common/ etc/microstack. rc, and then executes your /bugs.launchpad .net/bugs/ 1863137 openstack catalog list efe0-4681- a867-aaec1160bf e3) ****:5000/ v3/ ID=a7845351d020 4e71b7f34c6386a 3bf5b NAME="admin" DOMAIN_ NAME="Default" DOMAIN_ NAME" ]; then unset OS_USER_ DOMAIN_ NAME; fi DOMAIN_ ID="default" DOMAIN_ ID" ]; then unset OS_PROJECT_ DOMAIN_ ID; fi NAME="microstac k" API_VERSION= 3 /bugs.launchpad .net/microstack /+bug/1863137/ +subscriptions
> download or source an .rc file. microstack.
> wrapper script that sources
> /var/snap/
> command via the openstack cli.
>
> Where did you download your .rc file from?
>
> ** Changed in: microstack
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> enable to use to openstack-cli
>
> Status in MicroStack:
> Incomplete
>
> Bug description:
> Hi everyone and thanks for your work,
>
> So when trying to use openstack-cli, for example :
>
> microstack.
>
> I get the following error:
>
> The request you have made requires authentication. (HTTP 401)
> (Request-ID: req-e69c05cc-
>
> I already downloaded the openstackRC file and sourced it. Are they other
> steps to do to authentificate ?
> Here is a copy of my openstackRC file :
>
> #!/usr/bin/env bash
> # To use an OpenStack cloud you need to authenticate against the Identity
> # service named keystone, which returns a **Token** and **Service
> Catalog**.
> # The catalog contains the endpoints for all services the user/tenant has
> # access to - such as Compute, Image Service, Identity, Object Storage,
> Block
> # Storage, and Networking (code-named nova, glance, keystone, swift,
> # cinder, and neutron).
> #
> # *NOTE*: Using the 3 *Identity API* does not necessarily mean any other
> # OpenStack API is version 3. For example, your cloud provider may
> implement
> # Image API v1.1, Block Storage API v2, and Compute API v2.0.
> OS_AUTH_URL is
> # only for the Identity API served through keystone.
> export OS_AUTH_URL=http://
> # With the addition of Keystone we have standardized on the term
> **project**
> # as the entity that owns the resources.
> export OS_PROJECT_
> export OS_PROJECT_
> export OS_USER_
> if [ -z "$OS_USER_
> export OS_PROJECT_
> if [ -z "$OS_PROJECT_
> # unset v2.0 items in case set
> unset OS_TENANT_ID
> unset OS_TENANT_NAME
> # In addition to the owning entity (tenant), OpenStack stores the entity
> # performing the action as the **user**.
> export OS_USERNAME="****"
> # With Keystone you pass the keystone password.
> export OS_PASSWORD="****"
> # If your configuration has multiple regions, we set that information
> here.
> # OS_REGION_NAME is optional and only valid in certain environments.
> export OS_REGION_
> # Don't leave a blank variable, unset it if it was empty
> if [ -z "$OS_REGION_NAME" ]; then unset OS_REGION_NAME; fi
> export OS_INTERFACE=public
> export OS_IDENTITY_
>
> To manage notifications about this bug go to:
> https:/
>