March 2021 - Community - lists.openinfra.dev

[openstack-community] Schedule Published - OpenStack Summit Austin
by Claire Massey 02 Jan '24

02 Jan '24

Hi everyone, The main conference schedule for the upcoming OpenStack Summit in Austin <https://www.openstack.org/summit/austin-2016/> is now available! SCHEDULE: https://www.openstack.org/summit/austin-2016/summit-schedule/ <https://www.openstack.org/summit/austin-2016/summit-schedule/> SPEAKER NOTIFICATIONS If you submitted a talk - check your email. Everyone who submitted a speaking proposal for the Summit will soon receive an email notification to let them know whether or not their talk is accepted. The email sent to selected speakers was sent from speakersupport(a)openstack.org <mailto:speakersupport@openstack.org> and contains important next steps and their speaker registration code. Each speaker is responsible for registering themselves to attend the Summit. Please make sure your colleagues read the email and complete this step. MOBILE APP In mid April the schedule mobile app will also be available for download. We will notify the community at that time. Contact summit(a)openstack.org with any questions. See you in Austin! Cheers, Claire

5 9

[openstack-community] Future of this mailing list
by Jeremy Stanley 22 Mar '21

22 Mar '21

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

3 4

[openstack-community] Authenticating to devstack and listing nova flavors + servers
by Joe Wolfe 21 Mar '21

21 Mar '21

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

2 1

[openstack-community] [victoria][keystone][ops]Keystone enforced policy issues
by Luke Camilleri 12 Mar '21

12 Mar '21

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

2 1

[openstack-community] Keystone deprecated policies problem
by meberhardt＠unl.edu.ar 05 Mar '21

05 Mar '21

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 */ /* --------------------------------------------------------------- */

2 1

Re: [openstack-community] Ovn chassis error possibly networking config error.
by Dees 02 Mar '21

02 Mar '21

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@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@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@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(a)gmail.com> wrote: Hi, Few questions inline On Mon, Mar 1, 2021 at 12:09 AM Amy Marrich <amy(a)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(a)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(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/community

1 1

[openstack-community] Ovn chassis error possibly networking config error.
by Dees 28 Feb '21

28 Feb '21

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 --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 Kind regards,Deepesh

2 2