From amy at demarco.com  Mon Mar  1 00:08:09 2021
From: amy at demarco.com (Amy Marrich)
Date: Sun, 28 Feb 2021 18:08:09 -0600
Subject: [openstack-community] Ovn chassis error possibly networking
 config error.
In-Reply-To: <952196218.884082.1614451027288@mail.yahoo.com>
References: <952196218.884082.1614451027288.ref@mail.yahoo.com>
 <952196218.884082.1614451027288@mail.yahoo.com>
Message-ID: <CAFs83QrE7uPHx=6MXB69vQzWa2ZAk+pbY7MiDSV2kM+QhBR1LQ@mail.gmail.com>

Deepesh,

Forwarding to the OpenStack Discuss mailing list.

Thanks,

Amy (spotz)

On Sat, Feb 27, 2021 at 12:42 PM Dees <motosingh at yahoo.co.uk> wrote:

> Hi All,
>
> Deployed openstack all service yesterday and seemed to be running since
> power cycling the openstack today.
>
> Then deployed and configured VM instance with networking but config
> onv-chassis is reporting error, as I am new to openstack (having used it
> number of years back) mind guiding where I should be looking any help will
> be greatly appreciated.
>
>
>
> nova-compute/0*              active    idle       1         10.141.14.62
>                      Unit is ready
>   ntp/0*                     active    idle                 10.141.14.62
>   123/udp            chrony: Ready
>   ovn-chassis/0*             error     idle                 10.141.14.62
>                      hook failed: "config-changed"
>
>
> Deployed VM instance using the following command line.
>
>
> curl
> http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img
> | \
>    openstack image create --public --container-format bare --disk-format
> qcow2 \
>    --property architecture=x86_64 --property hw_disk_bus=virtio \
>    --property hw_vif_model=virtio "focal_x86_64"
>
> openstack flavor create --ram 512 --disk 4 m1.micro
>
> openstack network create Pub_Net --external --share --default \
>    --provider-network-type vlan --provider-segment 200
> --provider-physical-network physnet1
>
> openstack subnet create Pub_Subnet --allocation-pool
> start=10.141.40.40,end=10.141.40.62 \
>    --subnet-range 10.141.40.0/26 --no-dhcp --gateway 10.141.40.1 \
>    --network Pub_Net
>
> openstack network create Network1 --internal
> openstack subnet create Subnet1 \
>    --allocation-pool start=192.168.0.10,end=192.168.0.199 \
>    --subnet-range 192.168.0.0/24 \
>    --gateway 192.168.0.1 --dns-nameserver 10.0.0.3 \
>    --network Network1
>
> Kind regards,
> Deepesh
> _______________________________________________
> Community mailing list
> Community at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/community/attachments/20210228/dedf1a6f/attachment.html>

From motosingh at yahoo.co.uk  Mon Mar  1 20:48:29 2021
From: motosingh at yahoo.co.uk (Dees)
Date: Mon, 1 Mar 2021 20:48:29 +0000 (UTC)
Subject: [openstack-community] Ovn chassis error possibly networking
 config error.
In-Reply-To: <CAB1EZBqDRffYhE1eUVO9+wO2A+4B53EuA83cKUGD4K4MYYD2oA@mail.gmail.com>
References: <952196218.884082.1614451027288.ref@mail.yahoo.com>
 <952196218.884082.1614451027288@mail.yahoo.com>
 <CAFs83QrE7uPHx=6MXB69vQzWa2ZAk+pbY7MiDSV2kM+QhBR1LQ@mail.gmail.com>
 <CAB1EZBqDRffYhE1eUVO9+wO2A+4B53EuA83cKUGD4K4MYYD2oA@mail.gmail.com>
Message-ID: <1580253120.2031001.1614631709883@mail.yahoo.com>

 Thanks for your reply much appreciated, deployed OpenStack through JUJU.
I managed to get around that issue by restarting services but I have fallen into another issue now, looks like I need to define network time somewhere on the config I am right?
When I create a network trying to get out a second interface I am getting errors. Any suggestions, please?
labuser at maas:~/openstack-base$ openstack network create Pub_Net1 --external --share --default --provider-network-type vlan --provider-segment 201 --provider-physical-network externalError while executing the command: BadRequestException: 400, Invalid input for operation: physical_network 'external' unknown for VLAN provider network.
The first network segment  is ok

labuser at maas:~/openstack-base$ openstack network create Pub_Net --external --share --default \   --provider-network-type vlan --provider-segment 200 --provider-physical-network physnet1


Config on juju
  ovn-chassis:    annotations:      gui-x: '120'      gui-y: '1030'    charm: cs:ovn-chassis-10    # *** Please update the `bridge-interface-mappings` to values suitable ***    # *** for thehardware used in your deployment.  See the referenced     ***    # *** documentation at the top of this file.                           ***    options:      ovn-bridge-mappings: physnet1:br-data external:br-ex      bridge-interface-mappings: br-data:eno2 br-ex:eno3
Status
ubuntu at 1:~$ sudo ovs-vsctl showe3b50030-b436-4d26-95af-4abeea1097d5    Manager "ptcp:6640:127.0.0.1"        is_connected: true    Bridge br-data        fail_mode: standalone        datapath_type: system        Port eno2            Interface eno2                type: system        Port br-data            Interface br-data                type: internal    Bridge br-int        fail_mode: secure        datapath_type: system        Port br-int            Interface br-int                type: internal        Port ovn-comput-0            Interface ovn-comput-0                type: geneve                options: {csum="true", key=flow, remote_ip="10.141.14.36"}    Bridge br-ex        fail_mode: standalone        datapath_type: system        Port eno3            Interface eno3                type: system        Port br-ex            Interface br-ex                type: internal    ovs_version: "2.13.1"

Kind regards,Deepesh


    On Monday, 1 March 2021, 10:39:51 GMT, Lucas Alvares Gomes <lucasagomes at gmail.com> wrote:  
 
 Hi,

Few questions inline

On Mon, Mar 1, 2021 at 12:09 AM Amy Marrich <amy at demarco.com> wrote:
>
> Deepesh,
>
> Forwarding to the OpenStack Discuss mailing list.
>
> Thanks,
>
> Amy (spotz)
>
> On Sat, Feb 27, 2021 at 12:42 PM Dees <motosingh at yahoo.co.uk> wrote:
>>
>> Hi All,
>>
>> Deployed openstack all service yesterday and seemed to be running since power cycling the openstack today.
>>

What did you use to deploy OpenStack ? Based on the command below I
don't recognize that output.

>> Then deployed and configured VM instance with networking but config onv-chassis is reporting error, as I am new to openstack (having used it number of years back) mind guiding where I should be looking any help will be greatly appreciated.
>>
>>
>>
>> nova-compute/0*              active    idle      1        10.141.14.62                      Unit is ready
>>  ntp/0*                    active    idle                10.141.14.62    123/udp            chrony: Ready
>>  ovn-chassis/0*            error    idle                10.141.14.62                      hook failed: "config-changed"
>>

I do not recognize this output or that error in particular, but I
assume that ovn-chassis is the name of the process of the
ovn-controller running on the node ?

If so, the configuration of ovn-controller should be present in the
local OVSDB instance, can you please paste the output of the following
command:

$ sudo ovs-vsctl list Open_VSwitch .

Also, do you have any logs related to that process ?

>>
>> Deployed VM instance using the following command line.
>>
>>
>> curl http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img | \
>>    openstack image create --public --container-format bare --disk-format qcow2 \
>>    --property architecture=x86_64 --property hw_disk_bus=virtio \
>>    --property hw_vif_model=virtio "focal_x86_64"
>>
>> openstack flavor create --ram 512 --disk 4 m1.micro
>>
>> openstack network create Pub_Net --external --share --default \
>>    --provider-network-type vlan --provider-segment 200 --provider-physical-network physnet1
>>
>> openstack subnet create Pub_Subnet --allocation-pool start=10.141.40.40,end=10.141.40.62 \
>>    --subnet-range 10.141.40.0/26 --no-dhcp --gateway 10.141.40.1 \
>>    --network Pub_Net
>>
>> openstack network create Network1 --internal
>> openstack subnet create Subnet1 \
>>    --allocation-pool start=192.168.0.10,end=192.168.0.199 \
>>    --subnet-range 192.168.0.0/24 \
>>    --gateway 192.168.0.1 --dns-nameserver 10.0.0.3 \
>>    --network Network1
>>
>> Kind regards,
>> Deepesh
>> _______________________________________________
>> Community mailing list
>> Community at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/community/attachments/20210301/f95865d8/attachment.html>

From motosingh at yahoo.co.uk  Tue Mar  2 22:00:17 2021
From: motosingh at yahoo.co.uk (Dees)
Date: Tue, 2 Mar 2021 22:00:17 +0000 (UTC)
Subject: [openstack-community] Ovn chassis error possibly networking
 config error.
In-Reply-To: <1580253120.2031001.1614631709883@mail.yahoo.com>
References: <952196218.884082.1614451027288.ref@mail.yahoo.com>
 <952196218.884082.1614451027288@mail.yahoo.com>
 <CAFs83QrE7uPHx=6MXB69vQzWa2ZAk+pbY7MiDSV2kM+QhBR1LQ@mail.gmail.com>
 <CAB1EZBqDRffYhE1eUVO9+wO2A+4B53EuA83cKUGD4K4MYYD2oA@mail.gmail.com>
 <1580253120.2031001.1614631709883@mail.yahoo.com>
Message-ID: <1178477318.2869706.1614722417156@mail.yahoo.com>

 
Hi All,
I got around that problem too.
I have a new problem now as I need to assign two external networks to VM with provider segment as vlan. Any guidance please?
So I tried this it doesn't work, not sure why.
openstack network create Pub_Net --external --share --default \   --provider-network-type vlan --provider-segment 200 --provider-physical-network physnet1
openstack subnet create Pub_Subnet --allocation-pool start=10.141.40.10,end=10.141.40.20 \   --subnet-range 10.141.40.0/26 --no-dhcp --gateway 10.141.40.1 \   --network Pub_Net
NET_ID1=$(openstack network list | grep -w Pub_Net| awk '{ print $2 }')
openstack server create --image 'focal_x86_64' --flavor m1.micro \   --key-name User1-key --security-group Allow_SSHPing --nic net-id=$NET_ID1 \   focal-1
But which router and floating IP it works but as I need two public networks with only one floating IP allowed is an issue.-----------------------------------------------------------------------------------------------------------------------------------------------

openstack network create Pub_Net --external --share --default \   --provider-network-type vlan --provider-segment 200 --provider-physical-network physnet1
openstack subnet create Pub_Subnet --allocation-pool start=10.141.40.10,end=10.141.40.20 \   --subnet-range 10.141.40.0/26 --no-dhcp --gateway 10.141.40.1 \   --network Pub_Net

openstack network create Network1 --internalopenstack subnet create Subnet1 \   --allocation-pool start=192.168.0.10,end=192.168.0.199 \   --subnet-range 192.168.0.0/24 \   --gateway 192.168.0.1 --dns-nameserver 10.0.0.3 \   --network Network1


openstack router create Router1openstack router add subnet Router1 Subnet1openstack router set Router1 --external-gateway Pub_Net
NET_ID1=$(openstack network list | grep Network1 | awk '{ print $2 }')

openstack server create --image 'focal_x86_64' --flavor m1.micro \   --key-name User1-key --security-group Allow_SSHPing --nic net-id=$NET_ID1 \   focal-1
FLOATING_IP=$(openstack floating ip create -f value -c floating_ip_address Pub_Net)


openstack server add floating ip focal-1 $FLOATING_IP


Kind regards,Deepesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/community/attachments/20210302/06f44427/attachment.html>

From meberhardt at unl.edu.ar  Fri Mar  5 21:12:22 2021
From: meberhardt at unl.edu.ar (meberhardt at unl.edu.ar)
Date: Fri, 05 Mar 2021 21:12:22 +0000
Subject: [openstack-community] Keystone deprecated policies problem
Message-ID: <20210305211222.Horde.HHcZNM5k3FoOKQXguoLtJMA@webmail.unl.edu.ar>

Hi,

my installation complains about deprecated policies and throw errors  
when I try to run specific commands in cli as admin user(list projects  
or list users, for example).

"You are not authorized to perform the requested action: identity:list_users."

I tried to fix this by upgrading the keystone policies using  
oslopolicy-policy-generator and oslopolicy-policy-upgrade. Just found  
two places where I have those keystone policy files in my sistem:  
/etc/openstack_dashboard/keystone_policy.json and cd  
/lib/python3.6/site-packages/openstack_auth/tests/conf/keystone_policy.json

I regenerated & upgraded it but Keystone still complains about the old  
polices. Where are it placed? How I shoud fix it?

OS: CentOS 8
Openstack version: Ussuri
Manual installation

Thanks,

Matias

/* --------------------------------------------------------------- */
/*                      Matías A. Eberhardt                        */
/*                                                                 */
/*                     Centro de Telemática                        */
/*                      Secretaría General                         */
/*                UNIVERSIDAD NACIONAL DEL LITORAL                 */
/*      Pje. Martínez 2652 - S3002AAB Santa Fe - Argentina         */
/*           tel +54(342)455-4245 - FAX +54(342)457-1240           */
/* --------------------------------------------------------------- */



From amy at demarco.com  Fri Mar  5 21:59:54 2021
From: amy at demarco.com (Amy)
Date: Fri, 5 Mar 2021 15:59:54 -0600
Subject: [openstack-community] Keystone deprecated policies problem
In-Reply-To: <20210305211222.Horde.HHcZNM5k3FoOKQXguoLtJMA@webmail.unl.edu.ar>
References: <20210305211222.Horde.HHcZNM5k3FoOKQXguoLtJMA@webmail.unl.edu.ar>
Message-ID: <B39B4878-4D59-49C7-A070-3013CF4528C9@demarco.com>

Adding the OpenStack discuss list.

Thanks,

Amy (spotz)

> On Mar 5, 2021, at 3:19 PM, meberhardt at unl.edu.ar wrote:
> 
> Hi,
> 
> my installation complains about deprecated policies and throw errors when I try to run specific commands in cli as admin user(list projects or list users, for example).
> 
> "You are not authorized to perform the requested action: identity:list_users."
> 
> I tried to fix this by upgrading the keystone policies using oslopolicy-policy-generator and oslopolicy-policy-upgrade. Just found two places where I have those keystone policy files in my sistem: /etc/openstack_dashboard/keystone_policy.json and cd /lib/python3.6/site-packages/openstack_auth/tests/conf/keystone_policy.json
> 
> I regenerated & upgraded it but Keystone still complains about the old polices. Where are it placed? How I shoud fix it?
> 
> OS: CentOS 8
> Openstack version: Ussuri
> Manual installation
> 
> Thanks,
> 
> Matias
> 
> /* --------------------------------------------------------------- */
> /*                      Matías A. Eberhardt                        */
> /*                                                                 */
> /*                     Centro de Telemática                        */
> /*                      Secretaría General                         */
> /*                UNIVERSIDAD NACIONAL DEL LITORAL                 */
> /*      Pje. Martínez 2652 - S3002AAB Santa Fe - Argentina         */
> /*           tel +54(342)455-4245 - FAX +54(342)457-1240           */
> /* --------------------------------------------------------------- */
> 
> 
> _______________________________________________
> Community mailing list
> Community at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community


From luke.camilleri at zylacomputing.com  Fri Mar 12 12:20:13 2021
From: luke.camilleri at zylacomputing.com (Luke Camilleri)
Date: Fri, 12 Mar 2021 13:20:13 +0100
Subject: [openstack-community] [victoria][keystone][ops]Keystone enforced
	policy issues
Message-ID: <95b2b307-64de-c843-0744-1126718cf24a@zylacomputing.com>

Hi there, we have been troubleshooting keystone policies for a couple of 
days now (Victoria) and would like to reach out to anyone with some 
experience on the keystone policies. Basically we would like to follow 
the standard admin, member and reader roles together with the scopes 
function and have therefore enabled the below two option in keystone.conf

enforce_scope = true
enforce_new_defaults = true

once enabled we started seeing the below error related to token 
validation in keystone.log:

2021-03-11 19:50:12.009 1047463 WARNING 
keystone.server.flask.application 
[req-33cda154-1d54-447e-8563-0676dc5d8471 
020bd854741e4ba69c87d4142cad97a5 c584121f9d1a4334a3853c61bb5b9d93 - 
default default] You are not authorized to perform the requested action: 
identity:validate_token.: keystone.exception.ForbiddenAction: You are 
not authorized to perform the requested action: identity:validate_token.

The policy was previously setup as:

identity:validate_token: rule:service_admin_or_token_subject

but has now been implemented with the new scope format to:

identity:validate_token: (role:reader and system_scope:all) or 
rule:service_role or rule:token_subject

If we change the policy to the old one, we stop receiving the 
identity:validate_token exception. This only happens in horizon and 
running the same commands in the CLI (python-openstack-client) does not 
output any errors. To work around this behavior we place the old policy 
for validate_token rule in 
/usr/share/openstack-dashboard/openstack_dashboard/conf/keystone_policy.yaml 
and in the file /etc/keystone/keystone.conf

A second way how we can solve the validate_token exception is to disable 
the option which has been enabled above "enforce_new_defaults = true" 
which will obviously allow the deprecated policy rules to become 
effective and hence has the same behavior as implementing the old policy 
as we did

We would like to know if anyone have had this behavior and how it has 
been solved maybe someone can point us in the right direction to 
identify better what is going on.

Last but not least, it seems that from Horizon, the admin user is being 
assigned a project scoped token instead of a system scoped token, while 
from the CLI the same admin user can successfully issue a system:all 
token and run commands across all resources. We would be very happy to 
receive any form of input related to the above issues we are facing

Thanks in advance for any assistance



From amy at demarco.com  Fri Mar 12 15:07:27 2021
From: amy at demarco.com (Amy Marrich)
Date: Fri, 12 Mar 2021 09:07:27 -0600
Subject: [openstack-community] [victoria][keystone][ops]Keystone
	enforced policy issues
In-Reply-To: <95b2b307-64de-c843-0744-1126718cf24a@zylacomputing.com>
References: <95b2b307-64de-c843-0744-1126718cf24a@zylacomputing.com>
Message-ID: <51EA38A2-457F-435E-AB96-3C547D393F42@demarco.com>

Adding the OpenStack discuss list

> On Mar 12, 2021, at 6:34 AM, Luke Camilleri <luke.camilleri at zylacomputing.com> wrote:
> 
> Hi there, we have been troubleshooting keystone policies for a couple of days now (Victoria) and would like to reach out to anyone with some experience on the keystone policies. Basically we would like to follow the standard admin, member and reader roles together with the scopes function and have therefore enabled the below two option in keystone.conf
> 
> enforce_scope = true
> enforce_new_defaults = true
> 
> once enabled we started seeing the below error related to token validation in keystone.log:
> 
> 2021-03-11 19:50:12.009 1047463 WARNING keystone.server.flask.application [req-33cda154-1d54-447e-8563-0676dc5d8471 020bd854741e4ba69c87d4142cad97a5 c584121f9d1a4334a3853c61bb5b9d93 - default default] You are not authorized to perform the requested action: identity:validate_token.: keystone.exception.ForbiddenAction: You are not authorized to perform the requested action: identity:validate_token.
> 
> The policy was previously setup as:
> 
> identity:validate_token: rule:service_admin_or_token_subject
> 
> but has now been implemented with the new scope format to:
> 
> identity:validate_token: (role:reader and system_scope:all) or rule:service_role or rule:token_subject
> 
> If we change the policy to the old one, we stop receiving the identity:validate_token exception. This only happens in horizon and running the same commands in the CLI (python-openstack-client) does not output any errors. To work around this behavior we place the old policy for validate_token rule in /usr/share/openstack-dashboard/openstack_dashboard/conf/keystone_policy.yaml and in the file /etc/keystone/keystone.conf
> 
> A second way how we can solve the validate_token exception is to disable the option which has been enabled above "enforce_new_defaults = true" which will obviously allow the deprecated policy rules to become effective and hence has the same behavior as implementing the old policy as we did
> 
> We would like to know if anyone have had this behavior and how it has been solved maybe someone can point us in the right direction to identify better what is going on.
> 
> Last but not least, it seems that from Horizon, the admin user is being assigned a project scoped token instead of a system scoped token, while from the CLI the same admin user can successfully issue a system:all token and run commands across all resources. We would be very happy to receive any form of input related to the above issues we are facing
> 
> Thanks in advance for any assistance
> 
> 
> _______________________________________________
> Community mailing list
> Community at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community


From jwolfe at automatedsystems.io  Sun Mar 21 20:39:42 2021
From: jwolfe at automatedsystems.io (Joe Wolfe)
Date: Sun, 21 Mar 2021 16:39:42 -0400
Subject: [openstack-community] Authenticating to devstack and listing nova
	flavors + servers
Message-ID: <8865F06E-0BB6-4F72-9503-36466252BCFD@automatedsystems.io>

Hi All,

I am working on an api and would like to get some more context behinds authenticating into the api - so I am trying to get a list out of available flavors 1 and servers to start off with. I am able to get a token that I can interact with against keystone which shows up as https://mydevstackurl/identity/ <https://mydevstackurl/identity/> however when I try and run a simple curl against my compute as follows: 

curl   -H "X-Auth-Token: $OS_TOKEN" -s https://http://mydevstackurl/compute/api/v2.1/servers <https://http//mydevstackurl/compute/api/v2.1/servers>

I got no response back from curl - no 200 ,no 30x no 4xx nothing. 

Can anyone help to get me started ? The documents seem to be pretty detailed - but the methods provided don’t seem to work either in the tutorial: for example: 

curl -s -H "X-Auth-Token: $OS_TOKEN" \
  $OS_COMPUTE_API/flavors \
  | python -m json.tool

Only returns: 

zsh: no matches found: http://mydevstackurl/identity/v3/auth/tokens?nocatalog
Expecting value: line 1 column 1 (char 0)

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/community/attachments/20210321/e34199c4/attachment.html>

From fungi at yuggoth.org  Sun Mar 21 20:55:58 2021
From: fungi at yuggoth.org (Jeremy Stanley)
Date: Sun, 21 Mar 2021 20:55:58 +0000
Subject: [openstack-community] Future of this mailing list
Message-ID: <20210321205557.tcqy75iqnftc5gt7@yuggoth.org>

After looking back through the last 6 months worth of list archives,
there have been 9 threads: 1 was an announcement about the OpenStack
Annual Report and the other 8 were technical support requests which
needed to be referred to the openstack-discuss mailing list. Even
though the description for this list clearly says it's not for
support questions, that seems to be pretty much the only thing
anyone besides foundation staff send to it.

So with that in mind, is this list still serving any useful purpose?
Should we consider retiring it or folding it into another list
(maybe openstack-discuss)?
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/community/attachments/20210321/5cc26b35/attachment.sig>

From jwolfe at automatedsystems.io  Sun Mar 21 21:00:08 2021
From: jwolfe at automatedsystems.io (Joe Wolfe)
Date: Sun, 21 Mar 2021 17:00:08 -0400
Subject: [openstack-community] Future of this mailing list
In-Reply-To: <20210321205557.tcqy75iqnftc5gt7@yuggoth.org>
References: <20210321205557.tcqy75iqnftc5gt7@yuggoth.org>
Message-ID: <A4076C38-12EE-4960-8BA6-DE96963C8A98@automatedsystems.io>

A bit of a related question - what is the best place to goto for community support ?

Thanks

> On Mar 21, 2021, at 4:55 PM, Jeremy Stanley <fungi at yuggoth.org> wrote:
> 
> After looking back through the last 6 months worth of list archives,
> there have been 9 threads: 1 was an announcement about the OpenStack
> Annual Report and the other 8 were technical support requests which
> needed to be referred to the openstack-discuss mailing list. Even
> though the description for this list clearly says it's not for
> support questions, that seems to be pretty much the only thing
> anyone besides foundation staff send to it.
> 
> So with that in mind, is this list still serving any useful purpose?
> Should we consider retiring it or folding it into another list
> (maybe openstack-discuss)?
> -- 
> Jeremy Stanley
> _______________________________________________
> Community mailing list
> Community at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community



From fungi at yuggoth.org  Sun Mar 21 21:00:55 2021
From: fungi at yuggoth.org (Jeremy Stanley)
Date: Sun, 21 Mar 2021 21:00:55 +0000
Subject: [openstack-community] Authenticating to devstack and listing
 nova flavors + servers
In-Reply-To: <8865F06E-0BB6-4F72-9503-36466252BCFD@automatedsystems.io>
References: <8865F06E-0BB6-4F72-9503-36466252BCFD@automatedsystems.io>
Message-ID: <20210321210055.nu6zh2xoznsqzo73@yuggoth.org>

On 2021-03-21 16:39:42 -0400 (-0400), Joe Wolfe wrote:
> I am working on an api and would like to get some more context
> behinds authenticating into the api - so I am trying to get a list
> out of available flavors 1 and servers to start off with. I am
> able to get a token that I can interact with against keystone
> which shows up as https://mydevstackurl/identity/ however when I
> try and run a simple curl against my compute as follows: 
> 
> curl -H "X-Auth-Token: $OS_TOKEN" -s https://http://mydevstackurl/compute/api/v2.1/servers
> 
> I got no response back from curl - no 200 ,no 30x no 4xx nothing.
> 
> Can anyone help to get me started ? The documents seem to be
> pretty detailed - but the methods provided don’t seem to work
> either in the tutorial: for example: 
> 
> curl -s -H "X-Auth-Token: $OS_TOKEN" \
>   $OS_COMPUTE_API/flavors \
>   | python -m json.tool
> 
> Only returns: 
> 
> zsh: no matches found: http://mydevstackurl/identity/v3/auth/tokens?nocatalog
> Expecting value: line 1 column 1 (char 0)

As the description of the community mailing list states, "This list
does not provide support for OpenStack software." I have Cc'd the
openstack-discuss mailing list which is intended for "Discussion of
OpenStack use and development." Please follow up there with your
question. I'm keeping you in the To header in case you're not
subscribed there, so that people who reply to this will hopefully
include you directly.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/community/attachments/20210321/841a8c0a/attachment.sig>

From fungi at yuggoth.org  Sun Mar 21 21:05:02 2021
From: fungi at yuggoth.org (Jeremy Stanley)
Date: Sun, 21 Mar 2021 21:05:02 +0000
Subject: [openstack-community] Future of this mailing list
In-Reply-To: <A4076C38-12EE-4960-8BA6-DE96963C8A98@automatedsystems.io>
References: <20210321205557.tcqy75iqnftc5gt7@yuggoth.org>
 <A4076C38-12EE-4960-8BA6-DE96963C8A98@automatedsystems.io>
Message-ID: <20210321210502.iryrq6ak3pqjtiaw@yuggoth.org>

On 2021-03-21 17:00:08 -0400 (-0400), Joe Wolfe wrote:
> A bit of a related question - what is the best place to goto for
> community support ?

Officially:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss

Unofficially, also:
https://serverfault.com/tags/openstack/info
https://www.reddit.com/r/openstack/
https://discord.com/invite/XCWN2uakAY
[probably lots more I don't know about]

-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/community/attachments/20210321/86d74345/attachment.sig>

From jwolfe at automatedsystems.io  Sun Mar 21 21:07:02 2021
From: jwolfe at automatedsystems.io (Joe Wolfe)
Date: Sun, 21 Mar 2021 17:07:02 -0400
Subject: [openstack-community] Future of this mailing list
In-Reply-To: <20210321210502.iryrq6ak3pqjtiaw@yuggoth.org>
References: <20210321205557.tcqy75iqnftc5gt7@yuggoth.org>
 <A4076C38-12EE-4960-8BA6-DE96963C8A98@automatedsystems.io>
 <20210321210502.iryrq6ak3pqjtiaw@yuggoth.org>
Message-ID: <3A162FE4-1BD5-4A9B-AC18-BC82CCE96C41@automatedsystems.io>

Thanks so much

> On Mar 21, 2021, at 5:05 PM, Jeremy Stanley <fungi at yuggoth.org> wrote:
> 
> On 2021-03-21 17:00:08 -0400 (-0400), Joe Wolfe wrote:
>> A bit of a related question - what is the best place to goto for
>> community support ?
> 
> Officially:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
> 
> Unofficially, also:
> https://serverfault.com/tags/openstack/info
> https://www.reddit.com/r/openstack/
> https://discord.com/invite/XCWN2uakAY
> [probably lots more I don't know about]
> 
> -- 
> Jeremy Stanley
> _______________________________________________
> Community mailing list
> Community at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community



From ashlee at openstack.org  Mon Mar 22 15:34:32 2021
From: ashlee at openstack.org (Ashlee Ferguson)
Date: Mon, 22 Mar 2021 10:34:32 -0500
Subject: [openstack-community] Future of this mailing list
In-Reply-To: <20210321205557.tcqy75iqnftc5gt7@yuggoth.org>
References: <20210321205557.tcqy75iqnftc5gt7@yuggoth.org>
Message-ID: <C6C3A1D5-20E0-4D51-A264-92F7DA97CBB3@openstack.org>

During Summit cycles this list usually gets quite a bit of interaction, so I’d say it’s still useful for that purpose since the audience is a bit more specific than the discuss list.  

Ashlee


> On Mar 21, 2021, at 3:55 PM, Jeremy Stanley <fungi at yuggoth.org> wrote:
> 
> After looking back through the last 6 months worth of list archives,
> there have been 9 threads: 1 was an announcement about the OpenStack
> Annual Report and the other 8 were technical support requests which
> needed to be referred to the openstack-discuss mailing list. Even
> though the description for this list clearly says it's not for
> support questions, that seems to be pretty much the only thing
> anyone besides foundation staff send to it.
> 
> So with that in mind, is this list still serving any useful purpose?
> Should we consider retiring it or folding it into another list
> (maybe openstack-discuss)?
> -- 
> Jeremy Stanley
> _______________________________________________
> Community mailing list
> Community at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/community/attachments/20210322/9a1f0cc6/attachment.html>