[Openstack-operators] [charms] Onboarding session at next weeks summit

Hi All The OpenStack summit is nearly upon us and for this summit we're running a project onboarding session on Monday at 4.40pm in MR-105 (see [0] for full details) for anyone who wants to get started either using the OpenStack Charms or contributing to the development of the Charms, The majorit

[Openstack-operators] reminder: ops meetup team meeting at 15:00 UTC

The ops meet up team will meet as usual on #openstack-operators at 15:00 UTC today i.e. in about 35 minutes from now. The agenda is here : https://etherpad.openstack.org/p/ops-meetups-team See you there Chris -- Chris Morgan ___ OpenStack-operators

Re: [Openstack-operators] [nova][blazar][scientific] advanced instance scheduling: reservations and preeemption - Forum session

On 2 May 2017 at 05:50, Jay Pipes wrote: > Masahito Muroi is currently marked as the moderator, but I will indeed be > there and happy to assist Masahito in moderating, no problem. The more the merrier :-). There is a rather unfortunate clash here with the Scientific-WG BoF session. Location per

[Openstack-operators] ops meetup team meeting minutes 2017-5-2

Another good meeting this week, minutes linked below. We should have a Doodle poll up soon allowing the community to vote on the venue options for the August OS operators mid-cycle meet up in Mexico City. Many of us will be in Boston next week for the OpenStack Summit and there will be an ops meet

[Openstack-operators] [scientific] Today's Scientific WG meeting CANCELLED

Hi all - Unfortunately we must cancel today’s IRC meeting as none of the co-chairs are able to run the session. However, there’s plenty going on next week to look forward to: https://etherpad.openstack.org/p/Scientific-WG-boston We are

Re: [Openstack-operators] [User-committee] [scientific] Today's Scientific WG meeting CANCELLED

Reminder that the RSVP deadline for the Boston WG Social is Friday, 5 May. As of right now, only 11 tickets remain! If you want to attend please reserve a ticket at https://www.eventbrite.com/e/openstack-scientific-working-group-boston-social-tickets-33928219217? Tim __

[Openstack-operators] [telecom-nfv] Meeting #25

Hi All, Meeting #25 is tomorrow. Hope to see you there, and please bring something to discuss too. :) [0] Thanks, Curtis. [0]: https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda ___ OpenStack-operators mailing list OpenStack-operators@list

[Openstack-operators] [forum] extra session rooms at the forum

We have a full forum schedule planned, but based on past experience it's inevitable that something was missed, the scheduled slots won't be quite long enough for some deeper discussions, and that new topics will come up during the week. To accommodate those extra discussions, we have 3 session room

[Openstack-operators] [Mitaka - Heat] HTTPInternalServerError: ERROR: Remote error: BadRequest Expecting to find domain in user

Hello Ops, In our Mitaka Deployment with SSL and Keystone v3, we are having the below errors while trying to create a stack but they do not show while listing them: # openstack stack list WARNING: openstackclient.common.utils is deprecated and will be removed after Jun 2017. Please use osc_lib.

Re: [Openstack-operators] [Openstack] Strange: lost physical connectivity to compute hosts when using native (ryu) openflow interface

Hi Kevin, here is some information aout this issue: - if the network outage lasts less than ~1 minute, then connectivity to host and instances is automatically restored without problem - otherwise: - upon outage, "ovs-vsctl show" reports "is_connected: true" in all bridges (br-ex / br-int / br-t

Re: [Openstack-operators] [Mitaka - Heat] HTTPInternalServerError: ERROR: Remote error: BadRequest Expecting to find domain in user

Hello Edgar, what is the version of the openstack client ? did you export this? export OS_IDENTITY_API_VERSION=3 also the auth URL should have the v3, like; export OS_AUTH_URL=https://hostname:5000/v3 check the client configuration and give us feedback, ciao, Saverio 2017-05-02 21:15 GMT+0

Re: [Openstack-operators] [Mitaka - Heat] HTTPInternalServerError: ERROR: Remote error: BadRequest Expecting to find domain in user

Hi, Yes, all that is in place. This is why #openstack stack list works. The openstack client is: # yum list installed |grep client python-openstackclient.noarch 3.2.0-2.el7 @3rdParty7 python2-heatclient.noarch 1.5.0-1.el7 @3rdParty7 Edgar

Re: [Openstack-operators] [Mitaka - Heat] HTTPInternalServerError: ERROR: Remote error: BadRequest Expecting to find domain in user

Edgar, as admin, and using V3, do the following command: openstack user show heat in the field domain_id do you see default or Default with capital D ? in the heat config you pasted you have capital D, is that correct ? ciao, Saverio 2017-05-02 21:47 GMT+02:00 Edgar Magana : > Hi, > > Yes,

[Openstack-operators] Neutron Issues

Hello Ops! I have a major issue slapping me in the face and seek any assistance possible. When trying to spin up and instance whether from the command line, manually in Horizon, or with a HEAT template I receive the following error in nova and, where applicable, heat logs: Failed to allocate t

Re: [Openstack-operators] Neutron Issues

I forgot to mention I'm running Newton and my neutron.conf file is below and I'm running haproxy. [DEFAULT] core_plugin = ml2 service_plugins = router allow_overlapping_ips = True notify_nova_on_port_status_changes = True notify_nova_on_port_data_changes = True transpo

Re: [Openstack-operators] Neutron Issues

Failed to allocate networks usually means that the port failed to bind on the neutron side. If you're using ML2 + (ovs or Linux bridge), that's usually caused by either the agent on the host being dead, or there being no agent running on that host at all. Do a 'neutron agent-list' and ensure that

Re: [Openstack-operators] [Mitaka - Heat] HTTPInternalServerError: ERROR: Remote error: BadRequest Expecting to find domain in user

Hello, It is actually with lower ‘d’: ++--+ | Field | Value| ++--+ | default_project_id | 2402fb7305224988952626a10c4c0acf | | domain_id | defa

Re: [Openstack-operators] Neutron Issues

If you're using openvswitch, with Newton there was a change to the default agent for configuring openvswitch to be the python ryu library, I think it's been mentioned on here recently, so probably worth having a poke through the archives for more information. I'd check your neutron openvswitch age

Re: [Openstack-operators] Neutron Issues

No OVS here. Thanks though! This one has me stumped! From: Chris Sarginson [mailto:[email protected]] Sent: Tuesday, May 2, 2017 5:24 PM To: Steve Powell ; [email protected] Subject: Re: [Openstack-operators] Neutron Issues If you're using openvswitch, with Newton there wa

Re: [Openstack-operators] Neutron Issues

I think you probably need to say what ML2 mechanism driver(s) you are using. On Tue, May 2, 2017 at 10:29 PM Steve Powell wrote: > No OVS here. Thanks though! This one has me stumped! > > > > *From:* Chris Sarginson [mailto:[email protected]] > *Sent:* Tuesday, May 2, 2017 5:24 PM > *To:* Stev

Re: [Openstack-operators] Neutron Issues

[ml2] type_drivers = flat,vlan,vxlan tenant_network_types = vxlan mechanism_drivers = linuxbridge,l2population extension_drivers = port_security [ml2_type_flat] flat_networks = provider From: Neil Jerram [mailto:[email protected]] Sent: Tuesday, May 2, 2017 7:58 PM To: Steve Powell ; Chris Sargin

Re: [Openstack-operators] [Mitaka - Heat] HTTPInternalServerError: ERROR: Remote error: BadRequest Expecting to find domain in user

Hi, I found the problem. I was missing the “deferred_auth_method = password” in the heat.conf file.. Cheers, Edgar On 5/2/17, 2:06 PM, "Edgar Magana" wrote: Hello, It is actually with lower ‘d’: ++

Re: [Openstack-operators] Neutron Issues

is the instance scheduled to an hypervisor ? check this with openstack server show uuid (admin credential) if yes check nova-compute.log on the hypervisor. maybe you find some good information to debug Saverio Il 03 mag 2017 2:16 AM, "Steve Powell" ha scritto: [ml2] type_drivers = flat,vlan,v