[Openstack] can't input pipeline symbol in linux instance on web vnc console

Host OS: Ubuntu 16.4 openstack version: queens When I type the "|" symbol in linux instance on web vnc console, "|" becomes ">". But I connet to linux instance with putty, I can type "|" without any problem. I do not know why this happend. This issue only occurs on Linux instances.

Re: [Openstack] [glance] task in pending state, image in uploading state

Thanks Brian. It's great to get an email from Mr. Glance. I managed to patch Devstack, and a first test was successful. Perfect! A bit late, I then found numerous warnings in release notes and other documents that UWSGI should not be used when deploying Glance. My earlier web searches flew by

[Openstack] [glance] task in pending state, image in uploading state

Trying Glance's new import process, my images are all stuck in status uploading (both methods glance-direct and web-download). I can see that there are tasks for those images; they are pending. The Glance API log doesn't contain anything that clues me in (debug logging is enabled). The

Re: [Openstack] Retire of openstack-ansible-os_monasca-ui

+1 On Mon, Nov 12, 2018 at 2:14 PM Kaio Oliveira wrote: > Hi everyone, > > As part of the process of retiring the os_monasca-ui role from the > openstack-ansible project, I'm announcing here on the ML that this role > will be retired, because there's no reason to maintain it anymore. > This has

[Openstack] Retire of openstack-ansible-os_monasca-ui

Hi everyone, As part of the process of retiring the os_monasca-ui role from the openstack-ansible project, I'm announcing here on the ML that this role will be retired, because there's no reason to maintain it anymore. This has been discussed with the previous and the current

Re: [Openstack] [nova] PCI alias attribute numa_policy ignored when flavor has hw:cpu_policy=dedicated set

Mike, I had same issue month ago when I roll out sriov in my cloud and this is what I did to solve this issue. Set following in flavor hw:numa_nodes=2 It will spread out instance vcpu across numa, yes there will be little penalty but if you tune your application according they you are good

[Openstack] [PackStack][Cinder] On which node OpenStack store data of each instance

Hi, My question is does OpenStack store volumes somewhere other than the compute node? For example in PackStack on two nodes, one for controller and network and the other for compute node, the instance's volumes will be stored on the controller or on compute?

Re: [Openstack] [glance] Rocky image import stuck

On 11/7/18 8:46 AM, Bernd Bausch wrote: > Does the new image import process work? Am I missing something? Uploaded > images stay in an intermediate state, either /uploading/ or /importing/, > and never become /active.///Where should I look? Apologies for the late reply to your question. For

Re: [Openstack] [glance] task in pending state, image in uploading state

On 11/12/18 5:07 AM, Bernd Bausch wrote: > Trying Glance's new import process, my images are all stuck in status > uploading (both methods glance-direct and web-download). > > I can see that there are tasks for those images; they are pending. The > Glance API log doesn't contain anything that

Re: [Openstack] [PackStack][Cinder] On which node OpenStack store data of each instance

OpenStack stores volumes wherever you configure it to store them. On a disk array, an NFS server, a Ceph cluster, a dedicated storage node, a controller or even a compute node. And more. My guess: Volumes on controllers or compute nodes are not a good solution for production systems. By

Re: [Openstack-operators] Queens metadata agent error 500

Any other suggestion ? It does not work. Nova metatada is on port 8775 in listen but no way to solve this issue. Thanks Ignazio Il giorno lun 12 nov 2018 alle ore 22:40 Slawomir Kaplonski < skapl...@redhat.com> ha scritto: > Hi, > > From logs which You attached it looks that Your

[openstack-dev] [Searchlight] Report for the week of Stein R-22

Hi team, This is the report for last week, Stein R-22 [1]. Please follow to know what going on with Searchlight. [1] https://www.dangtrinh.com/2018/11/searchlight-weekly-report-stein-r-22.html Bests, -- *Trinh Nguyen* *www.edlab.xyz *

Re: [Openstack-operators] Queens metadata agent error 500

Hello, I am going to check it. Thanks Ignazio Il giorno Mar 13 Nov 2018 03:46 Chris Apsey ha scritto: > Did you change the nova_metadata_ip option to nova_metadata_host in > metadata_agent.ini? The former value was deprecated several releases ago > and now no longer functions as of pike. The

[openstack-dev] [tripleo][openstack-ansible] Updates on collaboration on os_tempest role

Hello, During the starting of Denver 2018 PTG [1]., We started collaborating towards using the openstack-ansible-os_tempest role [2] as a unified tempest role in TripleO and openstack-ansible project within OpenStack community. It will help us to improve the testing strategies between two

[openstack-dev] [tripleo] puppet5 has broken the master gate

Just a heads up but we recently updated to puppet5 in the master dependencies. It appears that this has completely hosed the master scenarios and containers-multinode jobs. Please do recheck/approve anything until we get this resolved. See https://bugs.launchpad.net/tripleo/+bug/1803024 I have

Re: [Openstack-operators] Queens metadata agent error 500

Did you change the nova_metadata_ip option to nova_metadata_host in metadata_agent.ini? The former value was deprecated several releases ago and now no longer functions as of pike. The metadata service will throw 500 errors if you don't change it. On November 12, 2018 19:00:46 Ignazio

Re: [openstack-dev] [nova][neutron] boot server with more than one subnet selection question

Got it, this is what I am looking for .. thank you   - Original message -From: Slawomir Kaplonski To: "OpenStack Development Mailing List (not for usage questions)" Cc:Subject: Re: [openstack-dev] [nova][neutron] boot server with more than one subnet selection questionDate: Tue, Nov 13,

Re: [Openstack-operators] RabbitMQ and SSL

On the off chance that others see this or there is talk about this in Berlin I have tracked this down to versions of python-amqp and python-kombu More information at the bug report https://bugs.launchpad.net/oslo.messaging/+bug/1800957

[openstack-dev] [masakari] No masakari meeting on 11/12

Hi all!, Sorry for the late announcement. Since most of us in Berlin summit, there will be no IRC meeting at 11/12. --- Regards, Sampath __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [heat] Heat sessions & forum in Berlin Summit

Dear all Here are some Heat relative sessions in OpenStack summit for you this week. Welcome everyone to join us and check it out! *Orchestration Ops/Users feedback session* Wed 14, 1:40pm - 2:20pm CityCube Berlin - Level 3 - M-Räume 6 https://etherpad.openstack.org/p/heat-user-berlin *Heat -

[openstack-dev] [cinder] No meeting this week ...

Team, Just a friendly reminder that we will not have our weekly meeting this week due to the OpenStack Summit. Hope to see some of you here.  Otherwise, talk to you next week! Thanks, Jay __ OpenStack Development

Re: [openstack-dev] [kolla][iconic] baremetal network

Hi Manuel, You can configure the neutron tenant network types in kolla-ansible via the 'neutron_tenant_network_types' variable in globals.yml. It's a comma-separated list. The default for that variable is vxlan, it's expected that you set it to match your requirements. The

[OpenStack-Infra] Meeting up Tuesday Evening for a Team Dinner (7pm outside main doors of citycube, near reg desk)

Hello everyone, I'd mentioned last week that we could try and cobble together an informal team dinner Tuesday night. The marketplace mixer runs until 7:30pm Tuesday night. Why don't we pop out of that a little early and meet at 7:00 pm Tuesday night outside the main doors of the City Cube

[openstack-dev] [neutron] Cancelling weekly meeting on November 12th

Dear Neutron Team, Due to the OpenStack Summit in Berlin and the activities around it, let's cancel the weekly IRC meeting on November 12th. We will resume normally on the 20th. Best regards Miguel __ OpenStack Development

Re: [openstack-dev] [cinder][manila] Cinder and Friends Dinner at Berlin Summit ...

Ivan, Yeah, I saw that was the case but it seems like there is not a point in time where there isn't a conflict.  Need to get some food at some point so anyone who wants to join can, and then we can head to the party if people want. Jay On 11/10/2018 8:07 AM, Ivan Kolodyazhny wrote:

[openstack-dev] [openstack-ansible] meeting cancelled

Hi everyone, Due to most of us being at the OpenStack Summit, we're cancelling the meeting tomorrow. Thanks everyone and see you in Berlin. Regards, Mohammed -- Mohammed Naser — vexxhost - D. 514-316-8872 D. 800-910-1726 ext. 200 E.

[openstack-dev] [ironic] Meetings cancelled this and next week - resumes November 26th

Greetings everyone! We're cancelling this week's meeting and next week's meeting due to the OpenStack Summit and US holidays the following week where some of our core reviewers will also be on vacation. If there are any questions, please feel to ask in #openstack-ironic. See you all in IRC.

[Openstack-operators] [openstack-operators] [radosgw] Adding user type attribute in radosGW admin operations API to simplify quota operations

Dear all, At CERN, we are currently adding the radosgw component in our private cloud OpenStack based offering. In order to ease the integration with lifecycle management, we are proposing to enable the possibility to add users with the keystone type through the radosgw Admin Ops API. During the

Re: [openstack-dev] [tripleo] puppet5 has broken the master gate

Hello Alex, On Tue, Nov 13, 2018 at 9:53 AM Alex Schultz wrote: > > Just a heads up but we recently updated to puppet5 in the master > dependencies. It appears that this has completely hosed the master > scenarios and containers-multinode jobs. Please do recheck/approve > anything until we get

Re: [Openstack-operators] Queens metadata agent error 500

Hi Chris, many thanks for your answer. It solved the issue. Regards Ignazio Il giorno mar 13 nov 2018 alle ore 03:46 Chris Apsey < bitskr...@bitskrieg.net> ha scritto: > Did you change the nova_metadata_ip option to nova_metadata_host in > metadata_agent.ini? The former value was deprecated

[openstack-dev] [nova][neutron] boot server with more than one subnet selection question

I have a network created like below:   1 network with 3 subnets (1 ipv6 and 2 ipv4) ,when boot, whether I can select subnet to boot from or the subnet will be force selected by the order the subnet created? Any document or code can be  referred? Thanks   | fd0e2078-044d-4c5c-b114-3858631e6328 |

[Openstack-operators] new SIGs to cover use cases

Team, At today Board and joint TC and UC meetings 2 questions come up: 1. Do we have or want to create a user community around Hybrid cloud. This is one of the major push of OpenStack for the communities. With 70+% of questionnaire responders told that they deploy and use hybrid cloud. We do

[Openstack-operators] Queens metadata agent error 500

Hi All, I upgraded manually my centos 7 openstack ocata to pike. All worked fine. Then I upgraded from pike to Queens and instances stopped to reach metadata on 169.254.169.254 with error 500. I am using isolated metadata true in my dhcp conf and in dhcp namespace the port 80 is in listen.

[openstack-dev] [docs] New Four Opens Project

Earlier this year, the OpenStack Foundation staff had the opportunity to brainstorm some ideas about how to express the values behind The Four Opens and how they are applied in practice. As the Foundation grows in scope to include new strategic focus areas and new projects, we felt it was

Re: [openstack-dev] [nova][neutron] boot server with more than one subnet selection question

Hi, You can choose which subnet (and even IP address) should be used, see „fixed_ips” field in [1]. If You will not provide anything Neutron will choose for You one IPv4 address and one IPv6 address and in both cases it will be chosen randomly from available IPs from all subnets. [1]

Re: [Openstack-operators] Queens metadata agent error 500

Hello again, I have another installation of ocata . On ocata the metadata for a network id is displayed by ps -afe like this: /usr/bin/python2 /bin/neutron-ns-metadata-proxy --pid_file=/var/lib/neutron/external/pids/c4731392-9b91-4663-adb3-b10b5ebcc4f1.pid

Re: [Openstack-operators] Queens metadata agent error 500

Hi, From logs which You attached it looks that Your neutron-metadata-agent can’t connect to nova-api service. Please check if nova-metadata-api is reachable from node where Your neutron-metadata-agent is running. > Wiadomość napisana przez Ignazio Cassano w dniu > 12.11.2018, o godz. 22:34:

Re: [Openstack-operators] Queens metadata agent error 500

Hello, the nova api in on the same controller on port 8774 and it can be reached from the metadata agent No firewall is present Regards Il giorno lun 12 nov 2018 alle ore 22:40 Slawomir Kaplonski < skapl...@redhat.com> ha scritto: > Hi, > > From logs which You attached it looks that Your

Re: [Openstack-operators] Queens metadata agent error 500

Hello again, ath the same time I tried to create an instance nova-api log reports: 2018-11-12 21:30:42.225 4226 ERROR oslo_db.sqlalchemy.engines [req-e4799f40-eeab-482d-9717-cb41be8ffde2 89f76bc5de5545f381da2c10c7df7f15 59f1f232ce28409593d66d8f6495e434 - default default] Database connection was

Re: [Openstack-operators] Queens metadata agent error 500

Hi, > Wiadomość napisana przez Ignazio Cassano w dniu > 12.11.2018, o godz. 22:55: > > Hello, > the nova api in on the same controller on port 8774 and it can be reached > from the metadata agent Nova-metadata-api is running on port 8775 IIRC. > No firewall is present > Regards > > Il

Re: [Openstack-operators] Queens metadata agent error 500

I tried 1 minute ago to create another instance. Nova api reports the following: RROR oslo_db.sqlalchemy.engines [req-cac96dee-d91b-48cb-831b-31f95cffa2f4 89f76bc5de5545f381da2c10c7df7f15 59f1f232ce28409593d66d8f6495e434 - default default] Database connection was found disconnected;

Re: [Openstack-operators] Queens metadata agent error 500

Yes, sorry. Also the 8775 port is reachable from neutron metadata agent Regards Ignazio Il giorno lun 12 nov 2018 alle ore 23:08 Slawomir Kaplonski < skapl...@redhat.com> ha scritto: > Hi, > > > Wiadomość napisana przez Ignazio Cassano w > dniu 12.11.2018, o godz. 22:55: > > > > Hello, > > the

[openstack-dev] [qa] [containers] [airship] [berlin] Berlin Airship Forums

I wanted to make sure that all interested folks are aware of the Airship-related Forums that will be held on Tuesday: Cross-project container security discussion: https://etherpad.openstack.org/p/BER-container-security Airship Quality Assurance use

Re: [Openstack-operators] Queens metadata agent error 500

Hi, Can You share logs from Your haproxy-metadata-proxy service which is running in qdhcp namespace? There should be some info about reason of those errors 500. > Wiadomość napisana przez Ignazio Cassano w dniu > 12.11.2018, o godz. 19:49: > > Hi All, > I upgraded manually my centos 7

Re: [Openstack-operators] Queens metadata agent error 500

PS Thanks for your help Il giorno lun 12 nov 2018 alle ore 22:15 Ignazio Cassano < ignaziocass...@gmail.com> ha scritto: > Hello, > attached here there is the log file. > > Connecting to an instance created befor upgrade I also tried: > wget

Re: [Openstack-operators] new SIGs to cover use cases

On 2018-11-12 15:46:38 + (+), arkady.kanev...@dell.com wrote: [...] > 1. Do we have or want to create a user community around Hybrid cloud. [...] > 2. As we target AI/ML as 2019 target application domain do we > want to create a SIG for it? Or do we extend scientific > community