Re: [openstack-dev] [Fuel] removing single mode

+1 -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Tue, Jan 27, 2015 at 2:44 PM, Stanislaw Bogatkin wrote: > +1 > > On Tue, Jan 27, 2015 at 4:05 PM, Aleksandr Didenko > wrote: > >> Hi, >> >> After starting implementing granular deployment we've faced a bunch of >> issues tha

[openstack-dev] How to pass through devstack config

Hi, I have seen Sean Dague's patch [1], if I understood correctly, by this patch we can reduce the number of DEVSTACK_GATE variables that we need. Trying to follow this patch to configure my gate job "DEVSTACK_GATE_GLUSTERFS" [2]. I am not able to figure out the way to use this patch [1]. Ple

[openstack-dev] Hyper-V meeting

Hi All, Due to weather conditions and others traveling we will need to postpone the Hyper-V meeting until next week. For issues or questions please email directly or contact one of us on the IRC channel. We will resume next week at the usual time. p Peter J. Pouliot CISSP Microsoft Cloud+Enter

Re: [openstack-dev] [all] need help with my first commit: The branch 'master' does not exist on the given remote 'gerrit'

Hello. I think there might be something wrong with git-review in your env. You might want try in another env, preferably linux if its handy. I noticed your origin is from github? you should clone from here instead: http://git.openstack.org/cgit/stackforge/congress Here's what you should get wh

Re: [openstack-dev] [heat][hot]

Thank you very much On Tue, Jan 27, 2015 at 1:06 PM, Angus Salkeld wrote: > On Tue, Jan 27, 2015 at 7:00 PM, Dmitry wrote: > >> I have another question, is it possible to get the stack name in the hot >> script? >> E.g. >> params: >> $stack_name: {get_global_variable: $stack.name}

Re: [openstack-dev] [Fuel] removing single mode

+1 On Tue, Jan 27, 2015 at 4:05 PM, Aleksandr Didenko wrote: > Hi, > > After starting implementing granular deployment we've faced a bunch of > issues that would make further development of this feature much more > complicated if we have to support both Simple and HA deployment modes. For > exam

[openstack-dev] oslo.i18n 1.3.1 released

The Oslo team is pleased to announce the release of: oslo.i18n 1.3.1: oslo.i18n library The primary reason for this release is a packaging issue reported and fixed by Dan Smith. For more details, please see the git log history below and: http://launchpad.net/oslo.i18n/+milestone/1.3.1 Please r

Re: [openstack-dev] [Fuel][Neutron ML2][VMWare]NetworkNotFoundForBridge: Network could not be found for bridge br-int

Hi Xarses, Actually it is multi-hypervisor environment. The error in the nova.log is: NetworkNotFoundForBridge: Network could not be found for bridge br-int the above error disappears changing the mech driver order in /etc/neutron/plugins/ml2/ml2_conf.ini file from mechanism_drivers = openvswi

Re: [openstack-dev] [Fuel] removing single mode

Hi, After starting implementing granular deployment we've faced a bunch of issues that would make further development of this feature much more complicated if we have to support both Simple and HA deployment modes. For example: simple mode does not require cluster (corosync, pacemaker, vips, etc),

Re: [openstack-dev] [Openstack][dev][Zuul] Merge Failed Error in CI - GitPython Error

Hi the merge fail error that we reported in ubuntu 12.04 has been solved in the new ubuntu 14.04 CI master setup. many thanks to ramy on the update of the repo :) https://github.com/rasselin/os-ext-testing cheers! On Fri, Jan 16, 2015 at 4:58 PM, Punith S wrote: > > Hi stackers, > > i'm runnin

Re: [openstack-dev] [Openstack][infra] Zuul-Merger Error in CI

Hi the merge fail error that we reported in ubuntu 12.04 has been solved in the new ubuntu 14.04 CI master setup. many thanks to ramy on the update of the repo :) https://github.com/rasselin/os-ext-testing cheers! On Thu, Jan 8, 2015 at 7:16 PM, Punith S wrote: > hi, > > i'm running CI for ope

Re: [openstack-dev] [heat][hot]

On Tue, Jan 27, 2015 at 7:00 PM, Dmitry wrote: > I have another question, is it possible to get the stack name in the hot > script? > E.g. > params: > $stack_name: {get_global_variable: $stack.name} > See: http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#pseudo-para

Re: [openstack-dev] [Fuel] Proposal for nominating people to python-fuelclient-core

I think the consensus was found and the resolution is positive. > 26 січ. 2015 о 14:37 Tomasz Napierala написав(ла): > > +1 > > >> On 26 Jan 2015, at 11:33, Roman Prykhodchenko wrote: >> >> Hi Guys, >> >> According to our previous thread [1] and the decision made there I’d like to >> initi

Re: [openstack-dev] [tc] do we really need project tags in the governance repository?

Doug Hellmann wrote: > On Mon, Jan 26, 2015, at 12:02 PM, Thierry Carrez wrote: > [...] >> I'm open to alternative suggestions on where the list of tags, their >> definition and the list projects they apply to should live. If you don't >> like that being in the governance repository, what would hav

Re: [openstack-dev] [Telco][NFV] Meeting facilitator for January 28th

Hi Steve, I can host it. Regards Marc Am 27.01.2015 um 08:40 schrieb Steve Gordon : > Hi all, > > As mentioned in the notes from last week's meeting I am going to be in > transit during our 1400 UTC meeting this Wednesday (28th) [1]. Is anyone else > willing and able to facilitate in my abse

Re: [openstack-dev] [Fuel] Getting rid of kickstart/preseed for all NEW releases

Andrew is right about our ability to upgrade packages on a system using "yum update" or "apt-get upgrade" because IBP installs standalone OS (unlike cloud case). Even more, we'll build Ubuntu images on a master node by 6.1 and of course we'll be able to use actual repo for that. Vladimir Kozhukalo

Re: [openstack-dev] [Fuel] Getting rid of kickstart/preseed for all NEW releases

Guys, First, we are not talking about deliberate disabling preseed based approach just because we so crazy. The question is "What is the best way to achieve our 6.1 goals?" We definitely need to be able to install two versions of Ubuntu 12.04 and 14.04. Those versions have different sets of packag

Re: [openstack-dev] [Fuel] fuel master monitoring

The proposed monitoring options make sense, since the Fuel master has nothing yet, but I would like to ressurect this thread to see if we can discuss some strategies in order to avoid the /var/log fillup with consequent docker containers corruption. Now, a customer facing this corruption can re

Re: [openstack-dev] [Murano] SQLite support - drop or not?

On 26.01.2015 18:34, Ruslan Kamaldinov wrote: > On Mon, Jan 26, 2015 at 6:12 PM, Andrew Pashkin wrote: >> On 26.01.2015 18:05, Ruslan Kamaldinov wrote: >> >> I think it's still important to perform migration specific checks. We want >> to make sure that DB is in expected state after each specific

[openstack-dev] Cross-Project meeting, Tue January 27th, 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: * Cross-project DevRef akin to Nova's ([1]) [2] (@sigmavirus24) * Avoiding private symbols in Oslo libraries [3] (dhellmann) * Discuss the importance of

Re: [openstack-dev] [Fuel][Agent] Moving Fuel Agent to a separate repo

Mike, You are absolutely right about our current priorities for 6.1 and this thread is not about immediate action. But just to be fair, moving Fuel Client to a separate repo was a priori much more complicated procedure because it is tested together with nailgun. For Fuel Agent we just need to cre

Re: [openstack-dev] [keystone] Flush expired tokens automatically ?

Updating subject line to attract keystone devs Daniel Comnea wrote: > +100 > > Dani > > On Mon, Jan 26, 2015 at 1:10 AM, Tim Bell > wrote: > > This is often mentioned as one of those items which catches every > OpenStack cloud operator at some time. It’s not cl

Re: [openstack-dev] [Fuel] [UI] Deploy Changes dialog redesign

Guys, I'm now here and I don't agree that we need to remove "changes" attribute. On the opposite, I think this is the only attribute which should be looked at on UI and backend, and all these "pending_addition" and "pending_someotherstuff" are obsolete and needless. Just assume, that we'll soon h

Re: [openstack-dev] [heat][hot]

I have another question, is it possible to get the stack name in the hot script? E.g. params: $stack_name: {get_global_variable: $stack.name} On Tue, Jan 27, 2015 at 3:53 AM, Qiming Teng wrote: > On Mon, Jan 26, 2015 at 07:44:25PM +0200, Dmitry wrote: > > thanks, exactly what I was look

Re: [openstack-dev] [Fuel] Cluster replaced deployment of provisioning information

Dmitry This is an interesting topic. As per our discussions earlier, I suggest that in the future we move to different serializers for each granule of our deployment, so that we do not need to drag a lot of senseless data into particular task being executed. Say, we have a fencing task, which has

[openstack-dev] [Nova] Requirements.txt and optional requirements

Hello! Do dependencies required only in some contexts belong into requirements.txt? Yesterday we had a short discussion on #openstack-nova regarding how to handle optional requirements. This was triggered by our quobyte nova driver (https://review.openstack.org/#/c/110722/18), who requires xattr,

<    1   2