Re: [Openstack] Neutron

I agree, with Neil, but a few things you want to check.. 1) is the network internal or external? 2) if internal, the port is created you may want to see neutron port-list 2.1 neutron agent-list and see if those are running 2.2 go into the compute where the VM is running and check if the agent

Re: [Openstack] Neutron

Hi Venkatesh, OK, so does the instance get an IP address if you log into it‎ and tell it to send a new DHCP request? This is normally done by dhclient eth0 or ifdown eth0; ifup eth0 but it can depend on what the guest OS is. ‎If the guest _does_ then get its IP, I suppose the

[openstack-dev] [Neutron] Defeact management

Hi folks, One of the areas I would like to look into during the Mitaka cycle is 'stability' [1]. The team has done a great job improving test coverage, and at the same time increasing reliability of the product. However, regressions are always around the corner, and there is a huge backlog of

Re: [openstack-dev] [Cinder] [Manila] Will NFS stay with Cinder as a reference implementation?

Cinder provides a block storage abstraction to a vm. Manila provides a filesystem abstraction. The two are very different, and complementary. I see no reason why the nfs related cinder drivers should be removed based on the existence or maturity of manila - manila is not going to suddenly start

Re: [openstack-dev] [Fuel][Plugins] add health check for plugins

it makes sense. We have two intersting use cases here: -to extend sanity test to validate plugins (see example in my previous email) -to extend OSTF test to add pre-deployment check. verify network tests are not enough to ensure that a deployment will be successfull or not. there are lot of other

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On 28/09/15 16:29 -0400, Doug Hellmann wrote: Excerpts from Mark Voelker's message of 2015-09-28 19:55:18 +: On Sep 28, 2015, at 9:03 AM, Doug Hellmann wrote: > > Excerpts from John Garbutt's message of 2015-09-28 12:32:53 +0100: >> On 28 September 2015 at 12:10,

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On 28/09/15 09:03 -0400, Doug Hellmann wrote: Excerpts from John Garbutt's message of 2015-09-28 12:32:53 +0100: On 28 September 2015 at 12:10, Sean Dague wrote: > On 09/27/2015 08:43 AM, Doug Hellmann wrote: >> Excerpts from Mark Voelker's message of 2015-09-25 20:43:23 +:

Re: [openstack-dev] [cinder] snapshot and cloning for NFS backend

Hi Sean, Author of specs is Eric Harney, If he is ok with it then I will submit the patch for moving specs to Mitaka. Thank you, Abhishek Kekane -Original Message- From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com] Sent: 29 September 2015 17:47 To: OpenStack Development

[openstack-dev] [election] [TC] TC Candidacy

I'd like to announce my candidacy for the TC election. A bit about me and my involvement with OpenStack: I've been involved with OpenStack for a long time now in various capacities. Most recently, I was the PTL for Neutron for the Juno, Kilo and Liberty cycles. I've been a core reviewer on

[openstack-dev] [cinder] snapshot and cloning for NFS backend

Hi Devs, The cinder-specs [1] for snapshot and cloning NFS backend submitted by Eric was approved in Kilo but due to nova issue [2] it is not implemented in Kilo and Liberty. I am discussing about this nova bug with nova team for finding possible solutions and Nikola has given some pointers

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On 28/09/15 12:32 +0100, John Garbutt wrote: On 28 September 2015 at 12:10, Sean Dague wrote: On 09/27/2015 08:43 AM, Doug Hellmann wrote: Excerpts from Mark Voelker's message of 2015-09-25 20:43:23 +: On Sep 25, 2015, at 1:56 PM, Doug Hellmann

Re: [openstack-dev] [cinder] snapshot and cloning for NFS backend

Hi Sean, Sure I will submit a patch to add this spec in Mitaka. Thank you, Abhishek Kekane -Original Message- From: Sean McGinnis [mailto:sean.mcgin...@gmx.com] Sent: 29 September 2015 17:38 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev]

[openstack-dev] [nfv][telcowg] Telco Working Group meeting schedule

Hi all, As discussed in last week's meeting [1] we have been seeing increasingly limited engagement in the 1900 UTC meeting slot. For this reason starting from next week's meeting (October 6th) it is proposed that we consolidate on the 1400 UTC slot which is generally better attended and stop

[Openstack] Drivers not found

Hi All, While booting windows2008R2 at the time of selecting volume partition its display drivers not found.We have successfully install the *Windows VirtIO Drivers* also*.*But still we get the same error *(Drivers not found) * *[image: Inline image 1]* Please any one help me guys. Thank you,

[Openstack] LBaaS with UDP

Hi there, Hope you can help me, is it at the moment possible to Loadbalance UDP Ports with the LBaas Feature of Openstack in any Release with any driver? Or if it is planned as feature for a future release? No matter which version of Openstack/Neutron or which driver I have to use, I am only

[Openstack-operators] [nfv][telcowg] Telco Working Group meeting schedule

Hi all, As discussed in last week's meeting [1] we have been seeing increasingly limited engagement in the 1900 UTC meeting slot. For this reason starting from next week's meeting (October 6th) it is proposed that we consolidate on the 1400 UTC slot which is generally better attended and stop

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

First of all, I would like to say thank you for the feedback! TBH, I did'n propose to remove API v1 at all in Mitaka. I was against to remove v1 API instead of disabling it. IMO, if we'll decide to leave it as is in Mitaka and disable in N release - nothing will change. Everybody will use v1

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

On Tue, Sep 29, 2015 at 6:48 AM, Ivan Kolodyazhny wrote: > First of all, I would like to say thank you for the feedback! > > TBH, I did'n propose to remove API v1 at all in Mitaka. I was against to > remove v1 API instead of disabling it. > ​Sorry Ivan, I did not mean to imply

Re: [openstack-dev] [all] Proposed Mitaka release schedule

On 09/28/2015 10:08 AM, Thierry Carrez wrote: > Hi everyone, > > You can find the proposed release schedule for Mitaka here: > > https://wiki.openstack.org/wiki/Mitaka_Release_Schedule > > That places the end release on April 7, 2016. It's also worth noting > that in an effort to maximize

Re: [Openstack] (no subject)

Hi Twinkle, You can use the following link for contributing to OpenStack nova: - https://wiki.openstack.org/wiki/How_To_Contribute On Tue, Sep 29, 2015 at 3:56 PM, Twinkle Chawla wrote: > Hello, > I am an openstack aspirant, seeking to contribute in 'nova' but as

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

On 28/09, John Griffith wrote: > On Mon, Sep 28, 2015 at 6:19 PM, Mark Voelker wrote: > > > FWIW, the most popular client libraries in the last user survey[1] other > > than OpenStack’s own clients were: libcloud (48 respondents), jClouds (36 > > respondents), Fog (34

Re: [openstack-dev] [Heat] Assumptions regarding extensions to OpenStack api's

Guys. Thank you for the pointing to the this gap. It probably was wrong missed before assumption about nova extension. I was personally sure, that it this extension always is installed. Currently we have couple resources OS::Nova::Server and AWS::EC2::Instance, which uses this extension with

Re: [openstack-dev] [cinder] snapshot and cloning for NFS backend

On Tue, Sep 29, 2015 at 06:26:06AM +, Kekane, Abhishek wrote: > Hi Devs, > > The cinder-specs [1] for snapshot and cloning NFS backend submitted by Eric > was approved in Kilo but due to nova issue [2] it is not implemented in Kilo > and Liberty. > I am discussing about this nova bug with

[Openstack-operators] Openstack-AngularJS related queries

Hi , I want to know what is the use of creating manifest.json file in openstack? How the data is fetched from all the files and passed to the dynamically created .js file in /static/dashboard/js directory. If I make any changes in the dynamically created .js files instead of actual files

[openstack-dev] [heat] Traditional question about Heat IRC meeting time.

Hi Heaters! Previously we had constant "tradition" to change meeting time for involving more people from different time zones. However last release cycle show, that two different meetings with 07:00 and 20:00 UTC are comfortable for most of our contributors. Both time values are acceptable for me

[openstack-dev] [heat]Refactor wsgi implementation of heat

Hi all, Some basic WSGI functions have been implemented by oslo.service[1], so that heat can reuse these functions,no need to implement them individually, such as the Router class in wsgi.py. Some other openstack projects have already started to refactor related logic[2].Perhaps heat should

[Openstack] (no subject)

Hello, I am an openstack aspirant, seeking to contribute in 'nova' but as I am new to this, could not find any way.. Need help! Regards, Twinkle Chawla ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to :

[Openstack] cinder-volume service HA

Hi is there any on going work to bring in native HA to cinder-volume service or is it already available in Kilo ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe :

[Openstack] metadata in both router and dhcp namespace

hi, Can someone please guide/suggest if we can enable metadata in both Qrouter and Qdhcp namespaces, I have some LANs inside the OpenStack, where VMs don't need to access external network, so I just create a normal LAN without a router attached in neutron and that's it, now when a VM boots up

Re: [openstack-dev] [Horizon] Horizon Productivity Suggestion

I wasn’t really envisioning a big discussion on the bugs; more like a brief notice period to let reviewers know high-priority items. Could definitely spend longer over it if that is preferred. Timing aside, the overall idea sounds good though? Lin: That’s a good idea. A wiki page would

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Guys, my apologize for the delay. Now I can give answers. Stephen, Heat meeting scheduled on Wednesday. ( https://wiki.openstack.org/wiki/Meetings/HeatAgenda) Result was really short and clear: use suggested in this mail thread naming OS::LBaaS::* and add new resources. I personally think, that

Re: [openstack-dev] [heat] Traditional question about Heat IRC meeting time.

+1, works for me too On Tue, Sep 29, 2015 at 12:57 PM Sergey Kraynev wrote: > Hi Heaters! > > Previously we had constant "tradition" to change meeting time for > involving more people from different time zones. > However last release cycle show, that two different

Re: [openstack-dev] [magnum]swarm + compose = k8s?

I agree with Tom to see Magnum as COEDaaS. k8s, swarm, mesos are so different in their architectures that magnum can not provide unified API to user. So I think we should focus on deployment. Regards, Wanghua On Tue, Sep 29, 2015 at 5:22 PM, Tom Cammann wrote: > This has

Re: [openstack-dev] [heat] Traditional question about Heat IRC meeting time.

On Tue, Sep 29, 2015 at 12:56:43PM +0300, Sergey Kraynev wrote: >Hi Heaters! >Previously we had constant "tradition" to change meeting time for >involving more people from different time zones. >However last release cycle show, that two different meetings with 07:00 >and 20:00

[openstack-dev] [Fuel][PTL] PTL Candidates Q Session

Folks I think it is awesome we have three candidates for PTL position in Fuel. I read all candidates' emails (including mine own several times :-) ) and I got a slight thought of not being able to really differentiate the candidates platforms as they are almost identical from the high-level point

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 28/09, Clint Byrum wrote: > Excerpts from Kevin Benton's message of 2015-09-28 14:29:14 -0700: > > I think a blanket statement about what people's motivations are is not > > fair. We've seen in this thread that some people want to enforce the limit > > of 72 chars and it's not about padding

Re: [openstack-dev] [Cinder] [Manila] Will NFS stay with Cinder as a reference implementation?

On 29/09, Duncan Thomas wrote: > Cinder provides a block storage abstraction to a vm. Manila provides a > filesystem abstraction. The two are very different, and complementary. I > see no reason why the nfs related cinder drivers should be removed based on > the existence or maturity of manila -

Re: [openstack-dev] [all] Proposed Mitaka release schedule

On 28/09/15 16:08 +0200, Thierry Carrez wrote: Hi everyone, You can find the proposed release schedule for Mitaka here: https://wiki.openstack.org/wiki/Mitaka_Release_Schedule That places the end release on April 7, 2016. It's also worth noting that in an effort to maximize development time,

Re: [openstack-dev] [magnum]swarm + compose = k8s?

This has been my thinking in the last couple of months to completely deprecate the COE specific APIs such as pod/service/rc and container. As we now support Mesos, Kubernetes and Docker Swarm its going to be very difficult and probably a wasted effort trying to consolidate their separate APIs

Re: [openstack-dev] [magnum]swarm + compose = k8s?

@Egor, docker compose is just a command line tool now, but I think it will change its architecture to Client and Server in the future, otherwise it can not do some complicate jobs. __ OpenStack Development Mailing List (not

[openstack-dev] Cross-Project Meeting Tue 29th of Sep, 21:00 UTC

Dear PTLs, cross-project liaisons and anyone else interested, We'll have a cross-project meeting today at 21:00 UTC, with the following agenda: * Review of past action items * Team announcements (horizontal, vertical, diagonal) * Cross-Project Specs to discuss: ** Service Catalog

[openstack-dev] Screenshots in reviews on Gerrit

Repost from openstack-docs ML. -Matjaz Hi all, I’ve been wondering if there is an already established or agreed on best practice for inclusion of screenshots in the review comment thread (like we have paste.openstack.org for text snippets and logs)? Sometimes I

[openstack-dev] [oslo][oslo.config] Reloading configuration of service

> Excerpts from Josh's message: >> So a few 'event' like constructs/libraries that I know about: >> >> http://docs.openstack.org/developer/taskflow/types.html#taskflow.types.notifier.Notifier >> >> >> I'd be happy to extract that and move to somewhere else if needed, it >> provides basic

Re: [Openstack] Cinder

Have you checked nova-cpu locgs? Usually attach errors are logged there. On Mon, Sep 28, 2015 at 6:34 AM, venkatesh kotipalli < openstackvenkat...@gmail.com> wrote: > Hi lvan, > > Thank you for your reply. > > I search the logs there is no errors. > > Thank you, > Venkatesh.k > > On Mon, Sep 28,

Re: [openstack-dev] [Cinder] [Manila] Will NFS stay with Cinder as a reference implementation?

Hi Vincent, Just to complement what Mike and Gorka said, Cinder NFS drivers does not provision FS services. It 'consumes' a FS export, and provisions block storage. To be more detailed, the Cinder NFS backend, mount a remote share from a NFS server, and create/stores the cinder volumes as files

[openstack-dev] Optional Dependencies

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi openstack-dev, I was wondering what the correct way of handling optional dependencies is? I'm specifically talking about libraries that are only required for a specific driver for example, so they're not technically a hard requirement and the

Re: [openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

On Sep 29, 2015, at 8:04 AM, Erlon Cruz wrote: > > Hi Cris, > > There are some questions that came to my mind. > > Cinder has near zero tolerance to backends that does not have a CI running. > So, can one assume that all drivers in Cinder will have the "OpenStack >

Re: [openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

Hi Cris, There are some questions that came to my mind. Cinder has near zero tolerance to backends that does not have a CI running. So, can one assume that all drivers in Cinder will have the "OpenStack Compatible" seal? When you say that the driver have to 'pass' the integration tests, what

Re: [openstack-dev] Optional Dependencies

On Tue, Sep 29, 2015 at 9:38 AM, Douglas Mendizábal < douglas.mendiza...@rackspace.com> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi openstack-dev, > > I was wondering what the correct way of handling optional dependencies > is? I'm specifically talking about libraries that

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

> On Sep 29, 2015, at 1:07 AM, Flavio Percoco wrote: > > On 28/09/15 16:29 -0400, Doug Hellmann wrote: >> Excerpts from Mark Voelker's message of 2015-09-28 19:55:18 +: >>> On Sep 28, 2015, at 9:03 AM, Doug Hellmann wrote: >>> > >>> > Excerpts from

Re: [openstack-dev] [magnum]swarm + compose = k8s?

+1 From: Tom Cammann > Reply-To: "openstack-dev@lists.openstack.org" > Date: Tuesday, September 29, 2015 at 2:22 AM To:

[OpenStack-Infra] jenkins-job-builder RFH and core reviewer list adjustments

The openstack-infra/jenkins-job-builder project seeks interested parties to help review and maintain its codebase. The currently active reviewers are doing their best to keep up with the change volume but would welcome further assistance. After glowing recommendations from the most active core

Re: [openstack-dev] [magnum]swarm + compose = k8s?

This is definitely a topic we should cover in Tokyo. On Sep 29, 2015, at 8:28 AM, Daneyon Hansen (danehans) > wrote: +1 From: Tom Cammann > Reply-To:

Re: [openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

On 09/29/2015 11:28 AM, Chris Hoge wrote: > On Sep 29, 2015, at 8:04 AM, Erlon Cruz wrote: >> >> Hi Cris, >> >> There are some questions that came to my mind. >> >> Cinder has near zero tolerance to backends that does not have a CI running. >> So, can one assume that all

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

I think disabling it by default in early M should help shake out any remaining issues - we can decide if we actually release that way later. I'm against actually removing the V1 code however On 29 Sep 2015 15:56, "Ivan Kolodyazhny" wrote: > First of all, I would like to say

Re: [openstack-dev] [puppet] Fwd: Action required: stackforge/puppet-openstack project move

Just to make it official, we decided today [1] our desire to retire stackforge/puppet-openstack Puppet module. The wiki is updated accordingly. [1] http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-09-29-15.00.html On 09/27/2015 08:44 PM, Jeremy Stanley wrote:

Re: [Openstack-operators] [openstack-dev] [cinder] [all] The future of Cinder API v1

> > > > I agree with John Griffith. I don't have any empirical evidences to back > my "feelings" on that one but it's true that we weren't enable to enable > Cinder v2 until now. > > Which makes me wonder: When can we actually deprecate an API version? I > *feel* we are fast to jump on the

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

On 09/28/2015 08:31 AM, Emilien Macchi wrote: > Hello! > > Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC > in #openstack-meeting-4: > > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150929 > > Feel free to add any add

Re: [openstack-dev] [cinder] snapshot and cloning for NFS backend

On 09/29/2015 09:05 AM, Kekane, Abhishek wrote: > Hi Sean, > > Author of specs is Eric Harney, If he is ok with it then I will submit the > patch for moving specs to Mitaka. > > Thank you, > > Abhishek Kekane > I saw that go by, thanks. Note that while the work outlined there is sufficient,

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

> On 25 Sep 2015, at 16:44, Ihar Hrachyshka wrote: > > Hi all, > > releases are approaching, so it’s the right time to start some bike shedding > on the mailing list. > > Recently I got pointed out several times [1][2] that I violate our commit > message requirement [3]

Re: [openstack-dev] [all][stable][release][horizon] 2015.1.2

> On 28 Sep 2015, at 12:23, Matthias Runge wrote: > > On 25/09/15 15:39, Ihar Hrachyshka wrote: > >> I see you have three people in the horizon-stable-maint team only. >> Have you considered expanding the team with more folks? In >> neutron, we have five people in the

Re: [openstack-dev] [puppet] should puppet-neutron manage third party software?

My suggestion: * patch master to send deprecation warning if third party repositories are managed in our current puppet-neutron module. * do not manage third party repositories from now and do not accept any patch containing this kind of code. * in the next cycle, we will consider deleting legacy

Re: [Openstack-operators] [openstack-dev] [cinder] [all] The future of Cinder API v1

On 2015-09-28 11:43 PM, John Griffith wrote: > > > On Mon, Sep 28, 2015 at 6:19 PM, Mark Voelker > wrote: > > FWIW, the most popular client libraries in the last user survey[1] > other than OpenStack’s own clients were: libcloud (48

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

On 2015-09-28 11:43 PM, John Griffith wrote: > > > On Mon, Sep 28, 2015 at 6:19 PM, Mark Voelker > wrote: > > FWIW, the most popular client libraries in the last user survey[1] > other than OpenStack’s own clients were: libcloud (48

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

> > > > I agree with John Griffith. I don't have any empirical evidences to back > my "feelings" on that one but it's true that we weren't enable to enable > Cinder v2 until now. > > Which makes me wonder: When can we actually deprecate an API version? I > *feel* we are fast to jump on the

[openstack-dev] [kolla] proposing Michal Jastrzebski (inc0) for core reviewer

Hi folks, I am proposing Michal for core reviewer. Consider my proposal as a +1 vote. Michal has done a fantastic job with rsyslog, has done a nice job overall contributing to the project for the last cycle, and has really improved his review quality and participation over the last several

Re: [openstack-dev] [PTL] The OpenStack UX team would like to know which roles are relevant to your project

There's a ranking from 1 to 19. Which is the higher rank? --John On 29 Sep 2015, at 16:31, Kruithof, Piet wrote: > Dear PTLs, > > The OpenStack UX project and Product working group is conducting a persona > working session in IBM's design center in Austin from October 5th - 7th. The > goal

Re: [Openstack-operators] [openstack-operators][osops] Something other than NOOP in our jenkins tests

Seems reasonable. If someone could put a "dumping ground" directory together that would help. (with an uncurated script as an example) So, i'm getting a feeling we should roll back the bashscript gate, and go back to noop. Thoughts? Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc:

Re: [Openstack-operators] [openstack-operators][osops] Something other than NOOP in our jenkins tests

+1 I like that idea. I think it also ties in nicely with both the Monitoring and Tools WGs. Some projects have a directory called "contrib" that contains contributed items which might not be up to standard. Would that be a simple solution for the "dumping ground"? On Tue, Sep 29, 2015 at 2:29

Re: [openstack-dev] Openvswitch agent unit tests

Hello, Thx for Your tips. So I should focus more on write new functional tests for ovs agent if there are missing some rather then doing unit tests for it? -- Best regards / Pozdrawiam Sławek Kapłoński sla...@kaplonski.pl On Mon, 28 Sep 2015, Assaf Muller wrote: > Generally speaking, testing

Re: [openstack-dev] Openvswitch agent unit tests

On Tue, Sep 29, 2015 at 5:00 PM, Sławek Kapłoński wrote: > Hello, > > Thx for Your tips. So I should focus more on write new functional tests > for ovs agent if there are missing some rather then doing unit tests for > it? > If a method is conceivably testable with unit

[Openstack] Swift stat issue

I am testing OpenStack on CentOS 7. I follow the link below to install Swift: http://docs.openstack.org/juno/install-guide/install/yum/content/swift-install-controller-node.html But when I did a "swift stat", I encountered the errors as shown below: Could someone help? Regards, Kevin #

Re: [openstack-dev] [ops] Operator Local Patches

Hello All, We have some pretty good contributions of local patches on the etherpad. We are going through right now and trying to group patches that multiple people are carrying and patches that people may not be carrying but solves a problem that they are running into. If you can take some

Re: [Openstack-operators] [ops] Operator Local Patches

Hello All, We have some pretty good contributions of local patches on the etherpad. We are going through right now and trying to group patches that multiple people are carrying and patches that people may not be carrying but solves a problem that they are running into. If you can take some

Re: [openstack-dev] [puppet] Moving puppet-ceph to the Openstack big tent

[I'm cross posting this to the other Ceph threads to ensure that it's seen] We've discussed this on Monday on IRC and again in the puppet-openstack IRC meeting. The current census is that we will move from the deprecated stackforge organization and will be moved to the openstack one. At this time

Re: [openstack-dev] [Neutron] Release of a neutron sub-project

Vad, You can look up the group in gerrit: https://review.openstack.org/#/admin/groups/150,members -- Dims On Tue, Sep 29, 2015 at 3:36 PM, Vadivel Poonathan < vadivel.openst...@gmail.com> wrote: > Hi, > > As per the Sub-Project Release process - i would like to tag and release > the following

Re: [Openstack-operators] [openstack-operators][osops] Something other than NOOP in our jenkins tests

If we are going to be stringent on formatting – I would also like to see us be relatively consistent on arguments/env variables that are needed to make a script run. Some pull in ENV vars, some source a rc file, some just say already source your rc file to start with, others accept command

Re: [Openstack-operators] [ops] Operator Local Patches

Just spit balling here But wouldn't the way you deploy/patch these patches be good for the OSOps tools? I bet there is some overlap and having a discussion around how to get those patches _out_ would be a good topic? (Probably for the Tools WG, but worth mentioning here) Best Regards, JJ

Re: [openstack-dev] [kolla] proposing Michal Jastrzebski (inc0) for core reviewer

On Wed, Sep 30, 2015 at 7:20 AM, Steven Dake (stdake) wrote: > Hi folks, > > I am proposing Michal for core reviewer. Consider my proposal as a +1 > vote. Michal has done a fantastic job with rsyslog, has done a nice job > overall contributing to the project for the last

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Hi All, Have created a BP for the task. Please review it. https://blueprints.launchpad.net/heat/+spec/lbaasv2-suport Thanks Banashankar On Tue, Sep 29, 2015 at 2:47 AM, Sergey Kraynev wrote: > Guys, my apologize for the delay. Now I can give answers. > > Stephen, Heat

[openstack-dev] [Election] [TC} TC Candidacy

Hello Peers, I would be pleased to serve on the Technical Committee with your vote. I have a very relevant background to serving you in the Technical Committee in that I have done the following during OpenStack development: 1. Led the development, incubation, and integration of Heat for

Re: [Openstack] Swift stat issue

There are a number of things to check and some (perhaps) unintuitive gotchas that can give rise to that error: 1/ Check that keystone is working 2/ Check controller swift proxy log for errors 3/ Check storage node(s) swift log for errors Worth mentioning (an example of case 3/) you get this

Re: [openstack-dev] [kolla] proposing Michal Jastrzebski (inc0) for core reviewer

+1 Michal will be a great addition to the Core team. On Sep 29, 2015 6:48 PM, "Martin André" wrote: > > > On Wed, Sep 30, 2015 at 7:20 AM, Steven Dake (stdake) > wrote: > >> Hi folks, >> >> I am proposing Michal for core reviewer. Consider my proposal

Re: [Openstack-operators] Neutron DHCP failover bug

Why not run neutron dhcp agents on both nodes?  On September 29, 2015 at 7:04:57 PM, Sam Morrison (sorri...@gmail.com) wrote: Hi All, We are running Kilo and have come across this bug  https://bugs.launchpad.net/neutron/+bug/1410067 Pretty easy to replicate, have 2 network nodes, shutdown 1 of

Re: [openstack-dev] [ceph-users] [puppet] Moving puppet-ceph to the Openstack big tent

Good move :-) On 29/09/2015 23:45, Andrew Woodward wrote: > [I'm cross posting this to the other Ceph threads to ensure that it's seen] > > We've discussed this on Monday on IRC and again in the puppet-openstack IRC > meeting. The current census is that we will move from the deprecated >

[openstack-dev] Infra needs Gerrit developers

Hello All, I believe you are all familiar with Gerrit. Our community relies on it quite heavily and it is one of the most important applications in our CI infrastructure. I work on the OpenStack-infra team and I've been hacking on Gerrit for a while. I'm the infra team's sole Gerrit developer. I

[openstack-dev] [PTL] The OpenStack UX team would like to know which roles are relevant to your project

Dear PTLs, The OpenStack UX project and Product working group is conducting a persona working session in IBM's design center in Austin from October 5th - 7th. The goal of the workshop is to develop several personas that can be used by the community for creating user stories, planning, etc.

Re: [openstack-dev] [heat] Traditional question about Heat IRC meeting time.

+1 On 29/09/15 22:56, Sergey Kraynev wrote: Hi Heaters! Previously we had constant "tradition" to change meeting time for involving more people from different time zones. However last release cycle show, that two different meetings with 07:00 and 20:00 UTC are comfortable for most of our

Re: [openstack-dev] [magnum]swarm + compose = k8s?

*waving hands wildly at details* ... I believe that the real win is if Magnum's control plan can integrate the network and storage fabrics that exist in an OpenStack with kube/mesos/swarm. Just deploying is VERY meh. I do not care - it's not interesting ... an ansible playbook can do that in

[Openstack] VLAN Configuration

Hi All, We have configure the VLAN in compute node these are the steps we are changing the compute node side: [ovs] tenant_network_type = vlan network_vlan_ranges = physnet1:1:4094 bridge_mappings = physnet1:br-ens32 After changes run the commands is : ovs-vsctl add-br br-ens32 ovs-vsctl

Re: [openstack-dev] [Horizon] Horizon Productivity Suggestion

The etherpad that we had running for the bulk of L was really handy; something like that would be great to keep using to let folks know what is in play. On 29 September 2015 at 19:32, Rob Cresswell (rcresswe) wrote: > I wasn’t really envisioning a big discussion on the bugs;

[Openstack-operators] Tokyo Ops Design Summit Tracks - Agenda on Sched

Hi all, The agenda for Tokyo design summit's ops track is now on sched (buy Thierry wine if you see him): https://mitakadesignsummit.sched.org/overview/type/ops * Note that we have some unallocated slots (marked "TBC"). In order to help out our software development community who are short

Re: [openstack-dev] [PTL] The OpenStack UX team would like to know which roles are relevant to your project

On 09/29/2015 07:31 PM, Kruithof, Piet wrote: Dear PTLs, The OpenStack UX project and Product working group is conducting a persona working session in IBM's design center in Austin from October 5th - 7th. The goal of the workshop is to develop several personas that can be used by the

[Openstack-operators] Neutron DHCP failover bug

Hi All, We are running Kilo and have come across this bug https://bugs.launchpad.net/neutron/+bug/1410067 Pretty easy to replicate, have 2 network nodes, shutdown 1 of them and DHCP etc. moves over to the new host fine. Except doing a

Re: [openstack-dev] [Neutron] Release of a neutron sub-project

On Tue, Sep 29, 2015 at 2:36 PM, Vadivel Poonathan < vadivel.openst...@gmail.com> wrote: > Hi, > > As per the Sub-Project Release process - i would like to tag and release > the following sub-project as part of upcoming Liberty release. > The process says talk to one of the member of

Re: [openstack-dev] [Devstack][Sahara][Cinder] BlockDeviceDriver support in Devstack

This review was recently abandoned. Can you provide insight as to why? On September 17, 2015, at 2:30 PM, "Sean M. Collins" wrote: You need to remove your Workflow-1. -- Sean M. Collins __ OpenStack

Re: [openstack-dev] [magnum]swarm + compose = k8s?

+1 to Egor, I think that the final goal of Magnum is container as a service but not coe deployment as a service. ;-) Especially we are also working on Magnum UI, the Magnum UI should export some interfaces to enable end user can create container applications but not only coe deployment. I hope

[openstack-dev] [nova][python-novaclient] Functional test fail due to publicURL endpoint for volume service not found

Hi, all I submitted a patch for novaclient last night: https://review.openstack.org/#/c/228769/ , and it turns out the functional test has failed due to: publicURL endpoint for volume service not found. I also found out that another novaclient patch: https://review.openstack.org/#/c/217131/ also

[Openstack] Installing nova-compute package on ARM64 board having Ubuntu

Hi,       I'm trying to add an ARM64 based board as a compute node to a working Kilo OpenStack installation with 3 x86 nodes. I've Ubuntu 14.04.1 LTS on the ARM64 board. I'm not able to install nova-compute package on the ARM64 board. The error log is

Re: [openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

Hello Chris! FYI: regarding Cinder CIs, the tests to be run are specified at [1], afaik. Silvan [1] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#What_tests_do_I_use.3F 2015-09-29 17:28 GMT+02:00 Chris Hoge : > On Sep 29, 2015, at 8:04 AM, Erlon Cruz

  1   2   >