[openstack-dev] Etherpad for self-healing

Hi everyone, I am seeing Self-healing scheduled on Tuesday afternoon[1], but the etherpad for it is not listed in [2]. I made following etherpad by some chance. Would it be possible to update Etherpads wiki page? https://etherpad.openstack.org/p/self-healing-ptg-rocky Best regards, [1]

[openstack-dev] [octavia] octavia-dashboard 1.0.0.0rc2 (queens)

Hello everyone, A new release candidate for octavia-dashboard for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/octavia-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [octavia] octavia 2.0.0.0rc2 (queens)

Hello everyone, A new release candidate for octavia for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/octavia/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [horizon] horizon 13.0.0.0rc2 (queens)

Hello everyone, A new release candidate for horizon for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/horizon/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [all] [QA] PTG QA Help Room on Monday-Tuesday: open discussion + stestr + tempest plugins

Hi All, As you might have notice about QA Help Rooms in mail thread[1], this is further announcement of the QA Help Room from Monday- Tuesday in Dublin PTG. QA team will be present in "Davin Suite" along with infra, stable, release and other horizontal team [2]. Main idea for conducting the

[Openstack-operators] [keystone] Timeouts reading response headers in keystone-wsgi-public and keystone-wsgi-admin

All, Currently experiencing a sporadic issue with our keystone endpoints. Throughout the day, keystone will just stop responding on both the admin and public endpoints, which will cause all services to hang. Restarting apache2 fixes the issue for some amount of time, but it inevitably

[openstack-dev] [QA] Queens Retrospective

Hi All, I have started an etherpad for a Queens cycle retrospective for QA - https://etherpad.openstack.org/p/qa-queens-retrospective This will be discussed in PTG on Wed 9.30-10.00 AM, so please add your feedback/comment before that. Everyone is welcome to add the feedback which help us to

[Openstack] Release Naming for S - time to suggest a name!

Hey everybody, Once again, it is time for us to pick a name for our "S" release. Since the associated Summit will be in Berlin, the Geographic Location has been chosen as "Berlin" (State). Nominations are now open. Please add suitable names to

Re: [openstack-dev] [QA] [all] QA Rocky PTG Planning

Hi All, As we are close to PTG, I have prepared the QA PTG Schedule - https://ethercalc.openstack.org/Rocky-PTG-QA-Schedule Detail of each sessions can be found in this etherpad - https://etherpad.openstack.org/p/qa-rocky-ptg We still have space for more sessions or topic if any of you would

[openstack-dev] Release Naming for S - time to suggest a name!

Hey everybody, Once again, it is time for us to pick a name for our "S" release. Since the associated Summit will be in Berlin, the Geographic Location has been chosen as "Berlin" (State). Nominations are now open. Please add suitable names to

[openstack-dev] [all][infra] Some new Zuul features

Hi, We've rolled out a few new Zuul features you may find useful. Added a post-timeout job attribute == We refined the way timeouts are handled. The "timeout" attribute of a job (which defaults to 30 minutes but can be changed by any job) now covers the time

[openstack-dev] [manila] manila 6.0.0.0rc2 (queens)

Hello everyone, A new release candidate for manila for the end of the Queens cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/manila/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [QA][all] Migration of Tempest / Grenade jobs to Zuul v3 native

Dear all, updates: - host/group vars: zuul now supports declaring host and group vars in the job definition [0][1] - thanks corvus and infra team! This is a great help towards writing the devstack and tempest base multinode jobs [2][3] * NOTE: zuul merges dict variables through job

Re: [openstack-dev] [masakari] [masakari-monitors] : Intrusive Instance Monitoring through QEMU Guest Agent Design Update

Hi Sam Make sense and will do option 2. FYI, we are planning to upload the second iim patch within a week and may do the masakari engine in different patch shortly. Thanks for your reply. Louie From: Sam P [mailto:sam47pr...@gmail.com] Sent: Tuesday, February 20, 2018 3:33 AM To: OpenStack

Re: [openstack-dev] [neutron] Generalized issues in the unit testing of ML2 mechanism drivers

On Tue, Feb 13, 2018 at 05:48:32PM -0500, Assaf Muller wrote: > On Wed, Dec 13, 2017 at 7:30 AM, Michel Peterson wrote: > > Through my work in networking-odl I've found what I believe is an issue > > present in a majority of ML2 drivers. An issue I think

[openstack-dev] [ptl][all][release] published release notes may be out of date

Thomas Bechtold reported some issues with the oslo.config release notes not showing some information. As part of investigating the problem, I discovered that reno's own release notes were not up to date, either. I think the problem is a combination of a (now fixed) reno bug [1] and some unrelated

[openstack-dev] [tc] [all] TC Report 18-08

HTML: https://anticdent.org/tc-report-18-08.html Most TC activity has either been in preparation for the [PTG](https://www.openstack.org/ptg) or stalling to avoid starting something that won't be finished before the PTG. But a few discussions to point at. # When's the Next PTG? Last

Re: [Openstack] Openstack data replication

For example, you can have 3 replicas stored in a global cluster and get dispersion across multiple geographic regions. But it's all one logical cluster. With container sync, you've got separate clusters with their own durability characteristics. So you would have eg 3 replicas in each cluster,

[openstack-dev] [tripleo] The Weekly Owl - 10th Edition

Note: this is the tenth edition of a weekly update of what happens in TripleO. The goal is to provide a short reading (less than 5 minutes) to learn where we are and what we're doing. Any contributions and feedback are welcome. Link to the previous version:

Re: [Openstack] [openstack] [pike]

no, everywhere its "controller" now. On Tue, Feb 20, 2018 at 10:56 PM, nithish B wrote: > Wait. Why does it say curl -g -i -X GET http://controller:35357/v3/ -H > "Accept: application/json" - shouldn't it be your "h > ttp://nagraj_controller:35357/v3/

Re: [Openstack] [openstack] [pike]

Wait. Why does it say curl -g -i -X GET http://controller:35357/v3/ -H "Accept: application/json" - shouldn't it be your "http://nagraj_controller: 35357/v3/ ."? Regards, Nitish B. On Tue, Feb 20, 2018 at 11:54 AM, Guru Desai wrote: > Here

[Openstack-operators] [scientific] IRC meeting - Managing dedicated capacity, PTG topics and beyond

Hi All - We have a Scientific SIG IRC meeting today in channel #openstack-meeting at 2100 UTC. Everyone is welcome. This week we are gathering details on best practice for managing dedicated capacity in scientific OpenStack private clouds, eg for resources funded by specific projects or

Re: [Openstack] [openstack] [pike]

Here you go with the output : [root@controller ~]# openstack --debug endpoint list START with options: [u'--debug', u'endpoint', u'list'] options: Namespace(access_key='', access_secret='***', access_token='***', access_token_endpoint='', access_token_type='', auth_type='', auth_url='

Re: [Openstack] [openstack] [pike]

According to your bootstrap and auth file, you're using http://controller:35357/v3, but the error you posted said http://nagraj_controller:35357/v3/. Run this: openstack --debug endpoint list Paste the output in here. -Erik On Tue, Feb 20, 2018 at 11:22 AM, Guru Desai

[Openstack-operators] Community Voting NOW OPEN - OpenStack Summit Vancouver 2018

Hi everyone, Session voting is now open for the May 2018 OpenStack Summit in Vancouver! VOTE HERE Hurry, voting closes Sunday, February 25 at 11:59pm Pacific Time (Monday, February 26 at 7:59 UTC). The Programming Committees

[openstack-dev] Community Voting NOW OPEN - OpenStack Summit Vancouver 2018

Hi everyone, Session voting is now open for the May 2018 OpenStack Summit in Vancouver! VOTE HERE Hurry, voting closes Sunday, February 25 at 11:59pm Pacific Time (Monday, February 26 at 7:59 UTC). The Programming Committees

Re: [Openstack] Openstack data replication

Hi All, Any reference or information with regards to how sync process in global clusters is more efficient than container sync in openstack swift. Aravind M D On Mon, Feb 19, 2018 at 11:41 AM, aRaviNd wrote: > Thanks John. > > You mentioned sync process in global

Re: [Openstack] [openstack] [pike]

yes, did the bootstrap commands and everything went fine i.e no errors. admin port 35357 as mentioned in the pike install guide for keystone.. keystone-manage bootstrap --bootstrap-password ADMIN_PASS *\* --bootstrap-admin-url http://controller:35357/v3 *\* --bootstrap-internal-url

Re: [Openstack] [openstack] [pike]

Why are you auth on the admin port? Try the default 5000? > On Feb 20, 2018, at 7:58 AM, Erik McCormick > wrote: > > Did you run all the keystone-manage bootstrap commands? This looks > like you're trying to create the domain you're supposed to be > authenticating

Re: [Openstack] [openstack] [pike]

Did you run all the keystone-manage bootstrap commands? This looks like you're trying to create the domain you're supposed to be authenticating against. On Tue, Feb 20, 2018 at 10:34 AM, Guru Desai wrote: > Hi Nithish, > > That part is verified. Below is the snippet of the rc

[Openstack-operators] minutes from today's ops meetups team meeting

Hello OpenStack Operators! The OpenStack Operators "ops meetups team" meeting was held today on IRC (#openstack-operators). Our "charter" is here https://wiki.openstack.org/wiki/Ops_Meetups_Team Minutes: Meeting ended Tue Feb 20 15:42:33 2018 UTC. Information about MeetBot at

Re: [Openstack] [openstack] [pike]

Hi Nithish, That part is verified. Below is the snippet of the rc file export OS_USERNAME=admin export OS_PASSWORD=ADMIN_PASS export OS_PROJECT_NAME=admin export OS_USER_DOMAIN_NAME=Default export OS_PROJECT_DOMAIN_NAME=Default export OS_AUTH_URL=http://controller:35357/v3 export

[openstack-dev] [neutron][networking-vsphere] neutron-lib patches for review

Could I please ask the folks from networking-vsphere to keep an eye on their review queue for incoming neutron-lib related patches? Today we have at least 3 in the networking-vsphere queue that haven't gotten a core review for over a month. In order to keep the neutron-lib effort moving and

Re: [Openstack] [nova] [nova-lxd] Query regarding LXC instantiation using nova

Hi Amit (re-titled thread with scoped topics) As Matt has already referenced, [0] is a good starting place for using the nova-lxd driver. On Tue, 20 Feb 2018 at 11:13 Amit Kumar wrote: > Hello, > > I have a running OpenStack Ocata setup on which I am able to launch VMs. >

Re: [openstack-dev] [docs] About the convention to use '.' instead of 'source'.

>> On 2018-02-18 03:55:51 -0600 (-0600), Monty Taylor wrote: >> > That said - I completely agree with fungi on the description of >> > the tradeoffs of each direction, and I do think it's valuable to >> > pick one for the docs. FWIW, DevStack declared long ago that it was built to use bash, even

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

Excerpts from Robert Collins's message of 2018-02-20 22:58:59 +1300: > On 20 February 2018 at 04:39, Andrey Kurilin wrote: > > Can someone explain me the reason for including "tests" module into > > packages? > > Namespacing the tests makes the test ids unique which is

Re: [Openstack-operators] [nova] [nova-lxd] Query regarding LXC instantiation using nova

Hi Amit (re-titled thread with scoped topics) As Matt has already referenced, [0] is a good starting place for using the nova-lxd driver. On Tue, 20 Feb 2018 at 11:13 Amit Kumar wrote: > Hello, > > I have a running OpenStack Ocata setup on which I am able to launch VMs. >

Re: [Openstack-operators] [openstack][openstack-nova][openstack-operators] Query regarding LXC instantiation using nova

On 2/20/2018 5:13 AM, Amit Kumar wrote: Hello, I have a running OpenStack Ocata setup on which I am able to launch VMs. But I want to move to LXC instantiation instead of VMs. So, for this, I installed nova-compute-lxd on my compute node (Ubuntu 16.04). */etc/nova/nova-compute.conf* on my

Re: [Openstack] [openstack] [pike]

Hi Guru, This looks more like a problem of finding the credentials. Please check if you sourced the credentials, and you did it right. A sample source parameters might look like the following: export OS_USERNAME=admin export OS_PASSWORD= export OS_TENANT_NAME=admin export

[Openstack] [openstack][openstack-nova][openstack-operators] Query regarding LXC instantiation using nova

Hello, I have a running OpenStack Ocata setup on which I am able to launch VMs. But I want to move to LXC instantiation instead of VMs. So, for this, I installed nova-compute-lxd on my compute node (Ubuntu 16.04). */etc/nova/nova-compute.conf* on my compute nodes was changed to contain the

[Openstack-operators] [openstack][openstack-nova][openstack-operators] Query regarding LXC instantiation using nova

Hello, I have a running OpenStack Ocata setup on which I am able to launch VMs. But I want to move to LXC instantiation instead of VMs. So, for this, I installed nova-compute-lxd on my compute node (Ubuntu 16.04). */etc/nova/nova-compute.conf* on my compute nodes was changed to contain the

[Openstack] [openstack] [pike]

Hi I am trying to install openstack pike and following the instruction mentioned in https://docs.openstack.org/keystone/pike/install/keystone-install-rdo.html for installing keystone. I am done with the environment setup. But after installing keystone, tried to create a project as mentioned in

Re: [openstack-dev] [yaql] [tripleo] Backward incompatible change in YAQL minor version

Hi, Zane Bitter writes: > On 17/02/18 16:40, Dan Prince wrote: >> Thanks for the update Emilien. A couple of things to add: >> >> 1) This was really difficult to pin-point via the Heat stack error >> message ('list index out of range'). I actually had to go and add >>

Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP

On 20 February 2018 at 04:39, Andrey Kurilin wrote: > Can someone explain me the reason for including "tests" module into > packages? Namespacing the tests makes the test ids unique which is very helpful for aggregating test data as we do. Including that in the tar.gz

Re: [openstack-dev] [masakari] [masakari-monitors] : Intrusive Instance Monitoring through QEMU Guest Agent Design Update

​Hi Louie, Thank you for patch and Sorry for the delay​ response. I prefer ​option 2. >From Masakari point of view, this is an instance event. Because, even if some thing wrong inside the VM, Masakari only can try to fix it by restart, rebuilt, migrate... etc the VM. Which are the same recovery