Re: [openstack-dev] [neutron][taas] Asynchronous TaaS APIs

Hi Anil, >I think we should adopt an asynchronous model, where we maintain the state for >>tap-service and tap-flow objects. Valid states could be "created", >"create->pending" and "failed." In addition, we will need a suitable mechanism >to have >the plugin extract the current state from the

Re: [openstack-dev] [tricircle] Using in-memory database for unit tests

On 22 March 2016 at 12:09, Shinobu Kinjo wrote: > Thank you for your comment (inline for my message). > > On Tue, Mar 22, 2016 at 11:53 AM, Vega Cai wrote: > > Let me try to explain some. > > > > On 22 March 2016 at 10:09, Shinobu Kinjo

Re: [Openstack-operators] [tags] Appealing for change of tags

Hi, We could definitely use more attendance/help on the ops-tag team... The data in project navigator comes from multiple sources but the install guide availability[1], packages[2], etc. are derived from ops-tags[3]. The team meets once a month (3rd Thursday of every month) to review open tags.

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

On Wed, Mar 23, 2016 at 12:41 PM, joehuang wrote: > Hi, Yipei, > > > > When you play Tricircle, it’s important to know that Tricircle is the > OpenStack API gateway to other OpenStack instances. In the Readme, Pod1, > Pod2 are two OpenStack instances, before trying Tricircle,

Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

On 23/03/16 13:05, Tom Fifield wrote: On 23/03/16 11:19, Tom Fifield wrote: On 23/03/16 00:14, Paul Belanger wrote: On Tue, Mar 22, 2016 at 03:32:23PM +0800, Tom Fifield wrote: Hi all, I'm sad to say that: * spammers are back - 100-odd pages have gone in over the weekend

Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

On 23/03/16 11:19, Tom Fifield wrote: On 23/03/16 00:14, Paul Belanger wrote: On Tue, Mar 22, 2016 at 03:32:23PM +0800, Tom Fifield wrote: Hi all, I'm sad to say that: * spammers are back - 100-odd pages have gone in over the weekend https://wiki.openstack.org/wiki/Special:NewPages *

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

OK. Got it. Thanks a lot for your help! Best regards, Yipei On Wed, Mar 23, 2016 at 11:41 AM, joehuang wrote: > Hi, Yipei, > > > > When you play Tricircle, it’s important to know that Tricircle is the > OpenStack API gateway to other OpenStack instances. In the Readme,

[Openstack] [nova] how to recover instances with different hypervisor-id on the same compute node

Hi All, Due to a hostname change, we ended up having a new hypervisor-id for one of our compute nodes. It was already running two instances and then, we didn't catch the updated hypervisor-id. This ended up with new instances spawning up with new hypervisor-id. Now, the instances with older

[openstack-dev] [nova] how to recover instances with different hypervisor-id on the same compute node

Hi All, Due to a hostname change, we ended up having a new hypervisor-id for one of our compute nodes. It was already running two instances and then, we didn't catch the updated hypervisor-id. This ended up with new instances spawning up with new hypervisor-id. Now, the instances with older

[openstack-dev] [tricircle]weekly meeting of Mar. 23

Hi, IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. Agenda: # Mitaka release preparation #Newton release features discussion # Link: https://etherpad.openstack.org/p/TricircleToDo Best Regards Chaoyi Huang ( Joe Huang )

Re: [Openstack-operators] [tags] Appealing for change of tags

The projects themselves don't seems updated, there are other projects in the big-tent that are not listed there yet. On Tue, Mar 22, 2016 at 9:16 PM, Tim Bell wrote: > > Looking at projects like Barbican in the >

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

Hi, Yipei, When you play Tricircle, it’s important to know that Tricircle is the OpenStack API gateway to other OpenStack instances. In the Readme, Pod1, Pod2 are two OpenStack instances, before trying Tricircle, you can make sure the environment is normal or not by executeing command

[openstack-dev] [Neutron]Debug with Pycharm

Hi everybody, Have you configured PyCharm to debug Neutron project. I confuged but it's not ok. If you have any archive, could you please share it with openstacker ? __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [all][elections] PTL Voting is now open

On Fri, Mar 18, 2016 at 11:13:25AM +1100, Tony Breeds wrote: > Elections are underway and will remain open for you to cast your vote until > 2016-03-24, 23:59 UTC We've been informed that CIVS doesn't work correctly with a number of languages important in our community, including but not limited

Re: [openstack-dev] [Neutron] Plan for changes affecting DB schema

Thanks for your answer. -Original Message- From: Henry Gessau [mailto:hen...@gessau.net] Sent: Tuesday, March 22, 2016 8:34 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Plan for changes affecting DB schema

Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

On 23/03/16 00:14, Paul Belanger wrote: > On Tue, Mar 22, 2016 at 03:32:23PM +0800, Tom Fifield wrote: >> Hi all, >> >> >> I'm sad to say that: >> >> * spammers are back - 100-odd pages have gone in over the weekend >> https://wiki.openstack.org/wiki/Special:NewPages >> >> * Cleanup was

Re: [Openstack] SSL cert issue on openstack client

Here is what I see: # python -mrequests.certs /usr/lib/python2.7/site-packages/requests/cacert.pem I do see GeoTrust certs in here: -- # grep -i geotrust cacert.pem | head -2 # Issuer: CN=GeoTrust Global CA O=GeoTrust Inc. # Subject: CN=GeoTrust Global CA O=GeoTrust Inc. # grep -i geotrust

[openstack-dev] [tricircle] playing tricircle with two node configuration

Hi, Joe and Zhiyuan, I have already finished installing devstack in two nodes with tricircle. I encounter some errors when testing cross-pod L3 networking with DevStack. I followed the README.md in github, every thing goes well until I boot virtual machines with the following command: nova boot

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Tue, Mar 22, 2016 at 6:01 PM, Fox, Kevin M wrote: > +1 for TripleO taking a look at Kolla. > > Some random thoughts: > > I'm in the middle of deploying a new cloud and I couldn't use either > TripleO or Kolla for various reasons. A few reasons for each: > * TripeO -

Re: [Openstack] SSL cert issue on openstack client

Python's requests module is unable to verify the cert. To check the default location of trusted root ca used by requests module, run this command: bash# python -mrequests.certs It will give you some location in output. Dump the contents of GeoTrust_CA_Bundle.crt to the end of this file. To test

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

+1 for TripleO taking a look at Kolla. Some random thoughts: I'm in the middle of deploying a new cloud and I couldn't use either TripleO or Kolla for various reasons. A few reasons for each: * TripeO - worries me for ever having to do a major upgrade of the software, or needing to do oddball

Re: [Openstack] SSL cert issue on openstack client

I think with OS_CACERT you are telling your CentOS 7 server to validate the server certificate at /var/tmp/GeoTrust_CA_Bundle.crt instead of the validation information that is embedded in the server certificate such as CRL and OCSP URL. Hope someone will have an answer for this problem. I am

Re: [Openstack] SSL cert issue on openstack client

It seems like your CentOS 7 server is not able to verify the KeyStone server's certificate. [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed Interesting issue. Anthony. -Original Message- From: Jagga Soorma

Re: [Openstack] SSL cert issue on openstack client

However my mac os x desktop does that without any issues. I was able to get around this on my CentOS server by downloading the GeoTrust_CA_Bundle.crt locally and using "export OS_CACERT=/var/tmp/GeoTrust_CA_Bundle.crt". However, I don't want to have all my users to have to do this. Is there a

[openstack-dev] [release]how to release an non-official project in Mitaka

Hi, Thanks for the help. There is a plan for not only Tricircle but also Kingbird to do a release in Mitaka, both of them are not OpenStack official project yet. The question is whether these projects can leverage the facility https://github.com/openstack/releases to do a release, or is there

Re: [openstack-dev] [keystone][ptls] Newton summit planning etherpad

I've added Keystone to the subject line. Keystone folks, please see email below from Steve! -amrith > -Original Message- > From: Anita Kuno [mailto:ante...@anteaya.info] > Sent: Tuesday, March 22, 2016 6:08 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] Newton

Re: [openstack-dev] Newton summit planning etherpad

On 3/22/2016 5:07 PM, Anita Kuno wrote: On 03/22/2016 05:42 PM, Steve Martinelli wrote: The summit planning etherpad for Keystone is here: https://etherpad.openstack.org/p/keystone-newton-summit-brainstorm Please brainstorm / toss ideas up / discuss Newton cycle goals Thanks, Steve

[Openstack] SSL cert issue on openstack client

Hi Guys, I am new to openstack and currently have a openstack environment that seems to have ssl enabled. From my mac I am able to use the openstack api without any issues and without having to do anything for ssl. However, from my CentOS 7.1 server I get the following error message: --

Re: [openstack-dev] [magnum] Streamline adoption of Magnum

On 03/22/2016 06:27 PM, Kevin Carter wrote: Comments in-line. On 03/22/2016 02:46 PM, Adrian Otto wrote: Team, This thread is a continuation of a branch of the previous High Availability thread [1]. As the Magnum PTL, I’ve been aware of a number of different groups who have started using

Re: [openstack-dev] [magnum] Streamline adoption of Magnum

Comments in-line. On 03/22/2016 02:46 PM, Adrian Otto wrote: > Team, > > This thread is a continuation of a branch of the previous High > Availability thread [1]. As the Magnum PTL, I’ve been aware of a number > of different groups who have started using Magnum in recent months. For > various

Re: [openstack-dev] Hummingbird Roadmap

I don't have the original email but this is in reply to: Hi all, I was wondering what the roadmap for Hummingbird is. Will development continue? Will support continue? Is it expected to reach feature parity or even replace the Python code? Thank you, Avishay Yes- we are in active development

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

On 2016-03-22 12:49:32 -0700 (-0700), Remo Mattei wrote: > hi guys I have been on this list for many months and have not > being able to attend, can someone remind me when the meeting is? I > would love to provide / help and share some tips. This was a one-time conference call (earlier today)

Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

On 2016-03-22 08:23:08 -0500 (-0500), JP Maxwell wrote: > If anyone wants to approve this I am still happy to help. > > https://review.openstack.org/#/c/285641/1 Can you elaborate on how you intend to help which has to be done first with root access to the server (rather than merely with the

Re: [openstack-dev] [os-brick][nova][cinder] os-brick/privsep change is done and awaiting your review

On Sat, 19 Mar 2016 at 06:27 Matt Riedemann wrote: > I stared pretty hard at the nova rootwrap filter change today [1] and > tried to keep that in my head along with the devstack change and the > changes to os-brick (which depend on the devstack/cinder/nova changes).

Re: [OpenStack-Infra] Austin Design Summit space needs

On Fri, Mar 11, 2016 at 9:27 AM, Elizabeth K. Joseph wrote: > https://etherpad.openstack.org/p/infra-newton-summit-planning I've also gone ahead and added a section at the bottom for "Other sessions of interest" for non-infra sessions that an infra presence would be

Re: [openstack-dev] [oslo][nova] Messaging: everything can talk to everything, and that is a bad thing

On 03/22/2016 05:42 PM, Dan Smith wrote: Shouldn't we be trying to remove central bottlenecks by decentralizing communications where we can? I think that's a good goal to continue having. Some deployers have setup firewalls between compute nodes, or between compute nodes and the database, so we

Re: [openstack-dev] Newton summit planning etherpad

On 03/22/2016 05:42 PM, Steve Martinelli wrote: > > The summit planning etherpad for Keystone is here: > https://etherpad.openstack.org/p/keystone-newton-summit-brainstorm > > Please brainstorm / toss ideas up / discuss Newton cycle goals > > Thanks, > > Steve Martinelli > OpenStack Keystone

[openstack-dev] [release][stable][ironic] ironic-python-agent 1.0.2 release (liberty)

We are pumped to announce the release of: ironic-python-agent 1.0.2: Ironic Python Agent Ramdisk This release is part of the liberty stable release series. For more details, please see below. 1.0.2 ^ Bug Fixes * This enables virtual media deploy even if virtual floppy device name is

[openstack-announce] [release][stable][designate] designate 1.0.2 release (liberty)

We are glad to announce the release of: designate 1.0.2: DNS as a Service This release is part of the liberty stable release series. With source available at: http://git.openstack.org/cgit/openstack/designate Please report issues through launchpad: http://bugs.launchpad.net/designate

[openstack-announce] [release][stable][designate] designate-dashboard 1.0.2 release (liberty)

We are chuffed to announce the release of: designate-dashboard 1.0.2: Designate Horizon UI bits This release is part of the liberty stable release series. For more details, please see below. Changes in designate-dashboard 1.0.1..1.0.2 --- de0eb1a

[openstack-announce] [release][stable][openstack] python-openstackclient 1.0.5 release (kilo)

We are amped to announce the release of: python-openstackclient 1.0.5: OpenStack Command-line Client This release is part of the kilo stable release series. With source available at: https://git.openstack.org/cgit/openstack/python-openstackclient Please report issues through launchpad:

Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

  -Original Message- From: Alan Pevec Reply: OpenStack Development Mailing List (not for usage questions) Date: March 22, 2016 at 14:21:47 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [oslo][nova] Messaging: everything can talk to everything, and that is a bad thing

>> Shouldn't we be trying to remove central bottlenecks by >> decentralizing communications where we can? > > I think that's a good goal to continue having. Some deployers have > setup firewalls between compute nodes, or between compute nodes and > the database, so we use the conductor to

[openstack-dev] Newton summit planning etherpad

The summit planning etherpad for Keystone is here: https://etherpad.openstack.org/p/keystone-newton-summit-brainstorm Please brainstorm / toss ideas up / discuss Newton cycle goals Thanks, Steve Martinelli OpenStack Keystone Project Team Lead

Re: [openstack-dev] [oslo][nova] Messaging: everything can talk to everything, and that is a bad thing

On 03/22/2016 09:15 AM, Flavio Percoco wrote: On 21/03/16 21:43 -0400, Adam Young wrote: I had a good discussion with the Nova folks in IRC today. My goal was to understand what could talk to what, and the short according to dansmith " any node in nova land has to be able to talk to the

Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

If anyone wants to approve this I am still happy to help. https://review.openstack.org/#/c/285641/1 I don't think you are ever going to be successful at blocking accounts or IPs. You must block the creation of the spam by the bots. IMHO focusing on improving the captcha or understanding the

Re: [openstack-dev] [nova] Trailing Slashes on URLs

Thank you for your answer Sean. Well understood. However, I think that if not fix this issue, at least we should supply guidelines on the matter. For example tempest's "test_delete_security_group_without_passing_id" test actually checks this behavior by addressing a security group with an "empty

Re: [openstack-dev] [cinder] Does the OpenStack community(or Cinder team) allow one driver to call another driver's public method?

* liuxinguo wrote: > Hi Cinder team, > > We are going to implement storage-assisted volume migrate in our > driver between different backend storage array or even different array > of different vendors. This is really high-efficiency than the > host-copy migration between

[openstack-dev] [puppet] Modules release-notes

Today during our meeting we discussed about release note management. In Mitaka, we started to use Reno [1], here is an example with puppet-openstack_spec_helper [2]. In few months ago, when we decided that we would use reno, we wanted to educate people using it so this is what we decided to do

Re: [openstack-dev] [tripleo] [puppet] move puppet-pacemaker

I've started my merging effort here https://github.com/dmitryilyin/openstack-puppet-pacemaker Can I change the interface of pcmk_resource? You have pcmk_constraint but I have pcmk_location/colocation/order separately. I can merge then into a single resource like you did or I can keep them

Re: [openstack-dev] [fuel][puppet] Switching fuel-library to consume stable/mitaka

Hi, > Additionally we will want to ensure that the fuel-ci will work for the > upstream stable/mitaka branches as it currently[0] isn't working since we > haven't cut a stable/mitaka branch for Fuel yet. Igor Belikov has been > notified of the current issues and is looking into a fix. I

[openstack-dev] [puppet] Puppet OpenStack Community Session in Austin Summit

Puppet OpenStack group will have a Community Session during the next Summit in Austin. This session is great to gather feedback from anyone in OpenStack community: * developers can ask questions about how to contribute. * operators / users can give feedback at how modules work on their

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

hi guys I have been on this list for many months and have not being able to attend, can someone remind me when the meeting is? I would love to provide / help and share some tips. Thanks > On Mar 22, 2016, at 12:19, Cody A.W. Somerville > wrote: > > > > On Tue,

[openstack-dev] [magnum] Streamline adoption of Magnum

Team, This thread is a continuation of a branch of the previous High Availability thread [1]. As the Magnum PTL, I’ve been aware of a number of different groups who have started using Magnum in recent months. For various reasons, there have been multiple requests for information about how to

[openstack-announce] [release][neutron][ipam][networking-infoblox] networking-infoblox 2.0.1

I am happy to announce that we have released version 2.0.1 of the Infoblox IPAM driver for OpenStack. This driver uses the pluggable IPAM framework delivered in Neutron's Liberty release, enabling the use of Infoblox for allocating subnets and IP addresses, and automatically creating DNS zones

[openstack-dev] [fuel][puppet] Switching fuel-library to consume stable/mitaka

Hey everyone, Emilien is in the process of cutting the stable/mitaka branches for all of the upstream puppet modules. As Fuel approaches SCF, we will want to switch from the master branches we are currently tracking to leverage the stable/mitaka branches. In talking with some other folks, I

[openstack-dev] [cross-project] What are specifications?

Hey all, Last Cross-Project meeting [1] I feel like there was some confusion around what our specifications should be used for. This mainly came up because of the rolling upgrade specification [2]. I want to clarify that this document exists as an incomplete specification that was contributed

Re: [openstack-dev] [barbican] High Availability

Hi Daneyon, We have been working on deploying a highly-available Barbican at Rackspace for a while now. We just recently made it publicly available through an early access program: http://go.rackspace.com/cloud-keep.html We don't have a full deployment of Barbican yet. Our early access

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

On Tue, Mar 22, 2016 at 3:07 PM, Paul Belanger wrote: > On Tue, Mar 22, 2016 at 11:45:12AM -0700, Colleen Murphy wrote: > > 3) how many vlans? > > - one untagged for pxe/management, one tagged for public > > > I had to drop off after this point, but did we talk about them

Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

> The release team discussed this at the summit and agreed that it didn't > really matter. The only folks seeing the auto-generated versions are those > doing CD from git, and they should not be mixing different branches of a > project in a given environment. So I don't think it is strictly

[Openstack-operators] [tags] Appealing for change of tags

Looking at projects like Barbican in the https://www.openstack.org/software/releases/liberty/components/barbican, they seem to have met some conditions which are currently marked as ‘no’. What is the mechanism to query these settings (either manual or automatic) ? As an example, there is

Re: [openstack-dev] [magnum] High Availability

Team, Time to close down this thread and start a new one. I’m going to change the subject line, and start with a summary. Please restrict further discussion on this thread to the subject of High Availability. Thanks, Adrian On Mar 22, 2016, at 11:52 AM, Daneyon Hansen (danehans)

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

On Tue, Mar 22, 2016 at 11:45:12AM -0700, Colleen Murphy wrote: > On Mon, Mar 21, 2016 at 10:17 AM, Colleen Murphy > wrote: > > > On Thu, Mar 17, 2016 at 11:48 AM, Colleen Murphy > > wrote: > > > >> The networking team at HPE received our request and

[openstack-dev] [cross-project] Meeting SKIPPED, Tue March 22th, 21:00 UTC

Hi all! We will not be having a cross-project meeting today, since there are no proposed agenda items [1]. All cross-project spec liaisons [2] should be ready to discuss the following items possibly next week: * Add centralized configuration options specification [3] * What are cross-project

Re: [openstack-dev] [magnum] High Availability

From: Hongbin Lu > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Monday, March 21, 2016 at 8:19 PM To: "OpenStack Development

Re: [Openstack] DHCP + vlan

The problem here is not VLAN but subnet. Normally you have one subnet associate with one interface (Ethernet interface), if you want multiple interfaces listen to the same DHCP server, you need to configure the multiple interfaces on the same subnet since one DHCP server can only broadcast to

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

On Mon, Mar 21, 2016 at 10:17 AM, Colleen Murphy wrote: > On Thu, Mar 17, 2016 at 11:48 AM, Colleen Murphy > wrote: > >> The networking team at HPE received our request and would like to have a >> call next week to review it. Our liaison, Venu, should

Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

> On Mar 22, 2016, at 2:10 PM, Alan Pevec wrote: > > 2016-02-26 19:51 GMT+01:00 Robert Collins : >>> On 27 February 2016 at 00:13, Neil Jerram >>> wrote: >>> I understand the semantic versioning algorithm for

[Openstack-operators] [osops] OSOps Tools and Monitoring Meeting - Wendesday 1900 UTC

Operators, We will be having our bi-weekly meeting in the #openstack-meeting-4 room at 1900UTC. I have published the current agenda for this meeting. You can find that here: https://etherpad.openstack.org/p/osops-irc-meeting-20160323 Either let me know or please go ahead and add to the ether

[openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

2016-02-26 19:51 GMT+01:00 Robert Collins : > On 27 February 2016 at 00:13, Neil Jerram wrote: >> I understand the semantic versioning algorithm for calculating a new >> version. But what do I run, in a git repository, to do that calculation

Re: [Openstack] DHCP + vlan

Sergey Arlashin writes: > > Hi All, > > I have a simple VLAN-based setup: single controller node and multiple > compute nodes. Currently neutron DHCP agent resides on controller node > and uses dnsmasq as a DHCP server. > > mean controller node) VLAN tags are

Re: [Openstack] Keystone dB connectivity error

well that’s a question you should answer. Do you use internal domains? If you do then the 192 will respond and resolve them for you if you do not need that, and just need internet domains to be resolvable then use the google DNS. Remo > On Mar 22, 2016, at 10:31, aa asd

[openstack-dev] [tc][deb][kolla][rpm] Introduce a new tag for type:packaging

Technical Committee, Thierry in this thread [1] suggested we need a type:packaging tag. Please accept my proposal for this work in this review [2]. Thanks! -steve [1] http://lists.openstack.org/pipermail/openstack-dev/2016-March/090096.html [2] https://review.openstack.org/295972

Re: [Openstack] Keystone dB connectivity error

Hi All!what DNS value I should assign to node. auto eth0 iface eth0 inet static address 192.168.133.129 netmask 255.255.255.0 gateway 192.168.133.1dns-nameserver 192.168.133.1 ? or 8.8.8.8 currently I am using 192.168.133.1.. is it ok. or should I need to pass 8.8.8.8 On Tuesday, 22

Re: [openstack-dev] [nova] Trailing Slashes on URLs

On 03/22/2016 12:34 PM, Shoham Peller wrote: > Hi, > > Nova-api behaves different whether a trailing-slash is given in the URL > or not. > These 2 requests produce different results: > > * GET /v2/{tenant-id}/servers - gets a list of servers > * GET /v2/{tenant-id}/servers/ - gets an info

Re: [Openstack] Keystone dB connectivity error

2016. 03. 22. 16:52 keltezéssel, Erdősi Péter írta: - mysql should listen on public IP I mean, an ip address, which is not 127.0.0.1, or the "controller" dns name, which has to be point to 127.0.0.1 Peter ___ Mailing list:

Re: [Openstack-operators] [nova] create image from paused VM refused with http 409

I had some interesting experiences between Cinder and Glance with Kilo as well. For instance, occasionally I'd get a bad checksum when running an image created from a Cinder volume. The checksum would occasionally be wrong. Liberty works well. All my images run no matter what. But I can't

[openstack-dev] [kolla] Managing bug backports to Mitaka branch

Hi folks, Thierry (ttx in the irc log at [1]) proposed the standard way projects typically handle backports of newton fixes that should be fixed in an rc, while also maintaining the information in our rc2/rc3 trackers. Here is an example bug with the process applied:

Re: [openstack-dev] [magnum] High Availability

  -Original Message- From: Hongbin Lu Reply: OpenStack Development Mailing List (not for usage questions) Date: March 21, 2016 at 22:22:01 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [tripleo] becoming third party CI (was: enabling third party CI)

On Thu, 2016-03-10 at 23:24 +, Jeremy Stanley wrote: > On 2016-03-10 16:09:44 -0500 (-0500), Dan Prince wrote: > > > > This seems to be the week people want to pile it on TripleO. > > Talking > > about upstream is great but I suppose I'd rather debate major > > changes > > after we branch

[openstack-dev] [nova] Trailing Slashes on URLs

Hi, Nova-api behaves different whether a trailing-slash is given in the URL or not. These 2 requests produce different results: - GET /v2/{tenant-id}/servers - gets a list of servers - GET /v2/{tenant-id}/servers/ - gets an info for a server with an "empty id" - produces 404 IMHO, a

Re: [openstack-dev] [Fuel] Packaging CI for Fuel

On 2016-03-22 15:20:22 + (+), Tristan Cacqueray wrote: [...] > With only my VMT hat on, this makes me wonder why the packaging needs > special care. Is there a reason why stable branch aren't built continuously? [...] My concern was more over handling packaging-specific security

Re: [OpenStack-Infra] Wiki.o.o sustaining spam attack

On Tue, Mar 22, 2016 at 03:32:23PM +0800, Tom Fifield wrote: > Hi all, > > > I'm sad to say that: > > * spammers are back - 100-odd pages have gone in over the weekend > https://wiki.openstack.org/wiki/Special:NewPages > > * Cleanup was ineffective, with many spam pages still existing on the

Re: [openstack-dev] [tc][fuel][kolla][osa][tripleo] proposing type:deployment

On Tue, 2016-03-22 at 15:37 +, Steven Dake (stdake) wrote: > > On 3/22/16, 2:15 AM, "Thierry Carrez" wrote: > > > > > Steven Dake (stdake) wrote: > > > > > > Technical Committee, > > > > > > Please accept my proposal of a new type of project called a > > >

Re: [Openstack] Keystone dB connectivity error

2016. 03. 22. 15:58 keltezéssel, Remo Mattei írta: iptables allowing port 3306 for mysql And also: - mysql should listen on public IP (check netstat output, you need to find something like that, we listen on every address, thats why you see 0.0.0.0) root@db1:~# netstat -alnp |grep 3306 tcp

Re: [openstack-dev] [puppet] weekly meeting #75

rrow at 3pm UTC on > #openstack-meeting4. > > https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack > > As usual, free free to bring topics in this etherpad: > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160322 > > We'll start discussing about the Summit,

Re: [openstack-dev] [networking-ovn][ovn4nfv]

Gary, Thanks for replying. I did chat briefly to one of the authors of SFC last week and will talk with them more. I will admit I am coming at the general service insertion problem from a very specific use case; easily protecting east-west traffic between applications by dynamically inserting

Re: [openstack-dev] [tc][fuel][kolla][osa][tripleo] proposing type:deployment

On 3/22/16, 2:15 AM, "Thierry Carrez" wrote: >Steven Dake (stdake) wrote: >> Technical Committee, >> >> Please accept my proposal of a new type of project called a deployment >> [1]. If people don¹t like the type name, we can change it. The basic >> idea is there are a

Re: [openstack-dev] [tc][fuel][kolla][osa][tripleo] proposing type:deployment

From: Jesse Pretorius > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Tuesday, March 22, 2016 at 7:40 AM To: "OpenStack

Re: [openstack-dev] [Fuel] Packaging CI for Fuel

On 03/19/2016 06:53 PM, Jeremy Stanley wrote: > On 2016-03-19 05:10:18 -0500 (-0500), Monty Taylor wrote: > [...] >> It would also be good to tie off with the security team about >> this. One of the reasons we stopped publishing debs years ago is >> that it made us a de-facto derivative distro.

Re: [openstack-dev] [tc][fuel][kolla][osa][tripleo] proposing type:deployment

On 3/22/16, 2:15 AM, "Thierry Carrez" wrote: >Steven Dake (stdake) wrote: >> Technical Committee, >> >> Please accept my proposal of a new type of project called a deployment >> [1]. If people don¹t like the type name, we can change it. The basic >> idea is there are a

Re: [Openstack] Keystone dB connectivity error

iptables allowing port 3306 for mysql Remo > On Mar 22, 2016, at 07:15, aa asd wrote: > > Hi All, > > I am configuring OpenStack Kilo. when I am trying to configure keystone and > running the below mention command. > > connection =

Re: [openstack-dev] [neutron] CI jobs take pretty long, can we improve that?

On Tue, Mar 22, 2016 at 9:31 AM, Kevin Benton wrote: > Thanks for doing this. I dug into the test_volume_boot_pattern test to see > what was going on. > > On the first boot, Nova called Neutron to create a port at 23:29:44 and it > took 441ms to return the port to Nova.[1] >

Re: [openstack-dev] [tc][fuel][kolla][osa][tripleo] proposing type:deployment

On 22 March 2016 at 09:15, Thierry Carrez wrote: > > For OSA, we don't produce the deployment tool, only a set of playbooks. I > was thinking we might need a type:packaging tag to describe which things we > produce are just about packaging OpenStack things for usage by

Re: [Openstack-operators] [nova] create image from paused VM refused with http 409

I am not a developer but I tried my best ! https://review.openstack.org/#/c/295865/ I applied the patch in my staging system and it fixes the problem :) Saverio 2016-03-22 13:46 GMT+01:00 Saverio Proto : > I found the problem. It happens only then the instance has booted

[Openstack] Keystone dB connectivity error

Hi All, I am configuring OpenStack Kilo. when I am trying to configure keystone and running the below mention command. connection = mysql://keystone:KEYSTONE_DBPASS@controller/keystone. It fails to connect with Database. however, when I attempted to use this command:- connection =

Re: [openstack-dev] [Openstack] Boot instance from volume via Horizon dashboard fails

Hi, thanks for your response. Having said that, there is probably a bug in Horizon since it's defaulting to vda for the device name when booting from volume. I think so, too. I'm quite new to Openstack and not 100% sure about my statements, but I think my question is not a support issue.

Re: [openstack-dev] [Sahara][QA] Notes about the move of the Sahara Tempest API test to sahara-tests

Thanks Luigi, sounds good to me. I'll be happy to help with reviews/approvals as needed. Trevor On Mon, 2016-03-21 at 12:05 +0100, Luigi Toscano wrote: > On Monday 21 of March 2016 10:50:30 Evgeny Sikachev wrote: > > Hi, Luigi! > > > > Thanks for this short spec :) > > Changes looking good

Re: [openstack-dev] [Fuel] Wiping node's disks on delete

For GPT disks and non-UEFI boot this method will work, since MBR will still contain first stage of a bootloader code. For UEFI boot things are little more complicated, we have to find EFI system partition, mount it and remove/edit some files. On Tue, Mar 22, 2016 at 4:26 PM, Bulat Gaifullin

Re: [openstack-dev] [TripleO] propose EmilienM for core

On Sun, Mar 20, 2016 at 02:22:49PM -0400, Dan Prince wrote: > I'd like to propose that we add Emilien Macchi to the TripleO core > review team. Emilien has been getting more involved with TripleO during > this last release. In addition to help with various Puppet things he > also has experience in

  1   2   >