[openstack-dev] [Fuel][Fuel-library] Using librarian-puppet to manage upstream fuel-library modules

2015-06-23 Thread Alex Schultz
Hello everyone, I took some time this morning to write out a document[0] that outlines one possible ways for us to manage our upstream modules in a more consistent fashion. I know we've had a few emails bouncing around lately around this topic of our use of upstream modules and how can we improve

Re: [openstack-dev] [puppet] [fuel] more collaboration request

2015-06-11 Thread Alex Schultz
everyones' lives easier would be welcomed. Thanks, -Alex Schultz On Thu, Jun 11, 2015 at 4:03 PM, Matt Fischer m...@mattfischer.com wrote: We as a community don't do a great job watching bugs, so personally I'd prefer that fuel developers just push patches, filing a bug too if you want. (Note: we

Re: [openstack-dev] Which is the correct way to set ha queues in RabbitMQ

2015-07-28 Thread Alex Schultz
https://www.rabbitmq.com/ha.html Both? I think ha_all/HA is just the policy name and so it can be whatever you want. -Alex On Tue, Jul 28, 2015 at 2:17 AM, Alvise Dorigo alvise.dor...@pd.infn.it wrote: Hi, I read these two documents:

[openstack-dev] [fuel][puppet] Fuel Library and upstream modules

2015-07-29 Thread Alex Schultz
Hello everyone, I have put together a wiki describing the proposed interactions between fuel-library and upstream modules based on previous talks around librarian-puppet[0]. Please take some time to review https://wiki.openstack.org/wiki/Fuel/Library_and_Upstream_Modules. This page provides a

Re: [openstack-dev] [fuel][puppet] Fuel Library and upstream modules

2015-07-30 Thread Alex Schultz
Hey Emilien, On Wed, Jul 29, 2015 at 5:16 PM, Emilien Macchi emil...@redhat.com wrote: This is a very good initiative and I'm happy to see that happening. It reflects what I was asking in our collaboration request. Though I have one suggestion for Custom Upstream Module Changes section. I

Re: [openstack-dev] [Fuel] Console messages in Mirantis 6.1

2015-08-04 Thread Alex Schultz
Hey Evgeniya, On Tue, Aug 4, 2015 at 8:59 AM, Evgeniya Shumakher eshumak...@mirantis.com wrote: Fuel team, One of Fuel 6.1 users found a very annoying bug: I’ve installed new Mirantis 6.1 a couple of weeks ago and I’m seeing the following message on both Controller and Compute node

Re: [openstack-dev] [fuel][fuel-library] Librarian changes

2015-08-04 Thread Alex Schultz
on getting the iso together today and hopefully can get a QA resource to test cinder out thoroughly. If QA is ok, this should be merged on Tuesday 8/11. cinder - https://review.openstack.org/#/c/203394/ Thanks, -Alex On Fri, Jul 31, 2015 at 12:11 PM, Alex Schultz aschu...@mirantis.com wrote: Here

Re: [openstack-dev] [fuel][fuel-library] Librarian changes

2015-07-31 Thread Alex Schultz
if something goes wrong. So there is a list of action items: Alex Schultz will send a schedule of which modules will be merged on which week and ensure that core reviewers know which commits they should merge when either by keeping W-1 on particular commits or by sharing the schedule in commit message

[openstack-dev] [fuel][fuel-library] Librarian changes

2015-07-30 Thread Alex Schultz
Hey everyone, During on the fuel meeting today we discussed the librarian changes and their status. As part of this work, the wiki page was updated and a first attempt at migrating the following modules has been completed pending merge: stdlib concat inifile ssh ntp apache firewall xinetd cinder

Re: [openstack-dev] [fuel] librarian-puppet integration, need help with build tasks for fuel-library

2015-07-24 Thread Alex Schultz
Just to followup since the required packages are finally available, the patches have been updated and are passing CI now. https://review.openstack.org/#/c/202763/ -Alex On Fri, Jul 24, 2015 at 8:32 AM, Alex Schultz aschu...@mirantis.com wrote: Unfortunately we got stuck with package

Re: [openstack-dev] [Fuel] Get rid of fuelmenu

2015-07-23 Thread Alex Schultz
For this to be consumable by end-users, a config file and editor (vim seriously?) is terrible UX. We need to remember who we are targeting to consume this functionality as it may not be an expert or even someone absolutely familiar with the linux tool set. While the existing thing may be

Re: [openstack-dev] [fuel] librarian-puppet integration, need help with build tasks for fuel-library

2015-07-17 Thread Alex Schultz
script execution to do the module fetch. The creation of the script isn't the issue, the issue is how can I properly run it as part of the build process. Regards, Alex Thanks, -Alex On Thu, Jul 16, 2015 at 11:17 PM, Alex Schultz aschu...@mirantis.com wrote: Hello everyone, I have committed

Re: [openstack-dev] [fuel] librarian-puppet integration, need help with build tasks for fuel-library

2015-07-17 Thread Alex Schultz
[0] https://github.com/stackforge/fuel-main/blob/master/repos.mk#L16-L37 [1] https://github.com/stackforge/fuel-main/blob/master/repos.mk#L45 On Fri, Jul 17, 2015 at 2:37 PM, Alex Schultz aschu...@mirantis.com wrote: Hey Alex, On Jul 17, 2015 4:32 AM, Aleksandr Didenko adide...@mirantis.com

Re: [openstack-dev] [fuel] librarian-puppet integration, need help with build tasks for fuel-library

2015-07-24 Thread Alex Schultz
wrote: Do we have any success here.. ? On Mon, Jul 20, 2015 at 8:32 AM Alex Schultz aschu...@mirantis.com wrote: Vladimir, Thanks. Can you point me to the error for perestroika? I'd be happy to take a look as well. I spent most of Friday throwing various options at the CI system to try

[openstack-dev] [fuel] librarian-puppet integration, need help with build tasks for fuel-library

2015-07-16 Thread Alex Schultz
Hello everyone, I have committed the initial configuration required to start leveraging librarian-puppet as part of the way we pull in upstream puppet modules[0]. Additionally, I have also committed a change that would pull in the openstack-ironic module[1]. The one piece that is missing from

Re: [openstack-dev] [puppet] Parameters possible default value

2015-07-17 Thread Alex Schultz
Hey Yanis, On Fri, Jul 17, 2015 at 3:56 AM, Yanis Guenane yguen...@redhat.com wrote: Hello everyone, Based on the conversation we had during last meeting I went ahead and created an ini_setting provider[1] that will act as a proxy between our provider and the upstream one, this way we

Re: [openstack-dev] [fuel] librarian-puppet integration, need help with build tasks for fuel-library

2015-07-17 Thread Alex Schultz
some way to validate that the module was pulled in properly as part of fuel-library CI? On Fri, Jul 17, 2015 at 2:48 PM Alex Schultz aschu...@mirantis.com wrote: Hey All, I've figured it out without having to modify the fuel-main build code. I've updated the fuel-library spec with a build

Re: [openstack-dev] [fuel] librarian-puppet integration, need help with build tasks for fuel-library

2015-07-17 Thread Alex Schultz
this monday morning? Vladimir Kozhukalov On Fri, Jul 17, 2015 at 5:51 PM, Alex Schultz aschu...@mirantis.com wrote: Hey Vladimir, On Fri, Jul 17, 2015 at 7:33 AM, Vladimir Kozhukalov vkozhuka...@mirantis.com wrote: Alex, Gathering upstream modules certainly should be implemented

Re: [openstack-dev] [fuel] librarian-puppet integration, need help with build tasks for fuel-library

2015-07-17 Thread Alex Schultz
at 5:51 PM, Alex Schultz aschu...@mirantis.com wrote: Hey Vladimir, On Fri, Jul 17, 2015 at 7:33 AM, Vladimir Kozhukalov vkozhuka...@mirantis.com wrote: Alex, Gathering upstream modules certainly should be implemented as a separate script so as to make it possible to use it wherever we need

Re: [openstack-dev] [fuel] librarian-puppet integration, need help with build tasks for fuel-library

2015-07-20 Thread Alex Schultz
via HTTP. Please check here http://172.18.160.74/osci/review/CR-202763/mos/7.0/fuel/base/centos6/Packages/fuel-library7.0-7.0.0-1.mos6888.git.bac86fe.noarch.rpm if the package contains all necessary upstream modules. Vladimir Kozhukalov On Sat, Jul 18, 2015 at 3:28 AM, Alex Schultz aschu

Re: [openstack-dev] [fuel][puppet] The state of collaboration: 5 weeks

2015-07-20 Thread Alex Schultz
As a new contributor to any openstack project, this is the first thing I do. Find out when the weekly meetings is, attend and monitor the conversion. Almost always there is an open discussion at the end of the weekly business. Going back through the last 5 weeks of irclogs[1], I couldn't

Re: [openstack-dev] [fuel] Using upstream packages & modules

2015-11-10 Thread Alex Schultz
t;> die. There is just one way I know to use haproxy with several different >> conf's - to construct looong command line with all of them - and >> it's really inconvenient. >> >> On Tue, Nov 10, 2015 at 12:20 PM, Simon Pasquier <spasqu...@mirantis.com> >&g

[openstack-dev] [fuel] Using upstream packages & modules

2015-11-09 Thread Alex Schultz
Hey folks, I'm testing[0] out flipping our current method of consuming upstream puppet modules from using pinned versions hosted on fuel-infra to be able to use the ones directly from upstream (master). This work is primarily to be closer aligned with the other OpenStack projects as well as

Re: [openstack-dev] [fuel] Using upstream packages & modules

2015-11-13 Thread Alex Schultz
e the Fuel default. I think eventually we'll need to reevaluate how we can split out the MOS packages for these features and allow a user to select which package set to use and still have it 'work'. Thanks, -Alex > > On Thu, Nov 12, 2015 at 1:51 AM, Alex Schultz <aschu...@mirantis.com> wrote:

[openstack-dev] [fuel] Using alternative OpenStack packages with Fuel

2015-11-13 Thread Alex Schultz
Hey folks, Based on my previous email, I promised to send out a note this week about this topic. My original email also included testing out the development version of the upstream puppet modules. I was able to get an environment working with the master branches of the OpenStack Puppet modules

Re: [openstack-dev] [fuel] Using upstream packages & modules

2015-11-11 Thread Alex Schultz
mpute or vice versa. But that should probably be more an academic exercise rather than production one. -Alex > > On Tue, Nov 10, 2015 at 6:25 PM, Alex Schultz <aschu...@mirantis.com> wrote: >> >> Hey Vladimir, >> >> On Tue, Nov 10, 2015 at 5:56 AM, Vladim

Re: [openstack-dev] [Fuel] HA cluster disk monitoring, failover and recovery

2015-11-17 Thread Alex Schultz
or improvement to ensure that the cluster doesn't crash itself when it runs out of space. The goal of change was to ensure that rabbitmq/mysql/etc are cleanly shutdown prior to a critical lack of disk space which can lead to the systems melting down. Thanks, -Alex > On Tue, Nov 17, 2015 at 5

Re: [openstack-dev] [Fuel] HA cluster disk monitoring, failover and recovery

2015-11-17 Thread Alex Schultz
Hey Kyrylo, On Tue, Nov 17, 2015 at 8:28 AM, Kyrylo Galanov wrote: > Hi Team, > > I have been testing fail-over after free disk space is less than 512 mb. > (https://review.openstack.org/#/c/240951/) > Affected node is stopped correctly and services migrate to a healthy

Re: [openstack-dev] [Fuel] HA cluster disk monitoring, failover and recovery

2015-11-17 Thread Alex Schultz
On Tue, Nov 17, 2015 at 11:12 AM, Vladimir Kuklin wrote: > Bogdan > > I think we should firstly check whether attribute deletion leads to node > starting its services or not. From what I read in the official Pacemaker > documentation, it should work out of the box without

Re: [openstack-dev] [Fuel][Fuel-library] Using librarian-puppet to manage upstream fuel-library modules

2015-07-10 Thread Alex Schultz
Done. Sorry about that. -Alex On Fri, Jul 10, 2015 at 9:22 AM, Simon Pasquier spasqu...@mirantis.com wrote: Alex, could you enable the comments for all on your document? Thanks! Simon On Thu, Jul 9, 2015 at 11:07 AM, Bogdan Dobrelya bdobre...@mirantis.com wrote: Hello everyone, I

Re: [openstack-dev] [ec2api][puppet] EC2 api puppet module

2015-09-01 Thread Alex Schultz
Hey Marcos, On Tue, Sep 1, 2015 at 7:50 AM, Marcos Fermin Lobo < marcos.fermin.l...@cern.ch> wrote: > Hi all, > > The standalone EC2 api project https://github.com/stackforge/ec2-api does > not have puppet module yet. I want to develop this puppet module and my > idea is start in a public Github

Re: [openstack-dev] [Fuel] Install fuel-libraryX.Y as a package on slave nodes

2015-09-09 Thread Alex Schultz
I agree that we shouldn't need to sync as we should be able to just update the fuel-library package. That being said, I think there might be a few issues with this method. The first issue is with plugins and how to properly handle the distribution of the plugins as they may also include puppet

Re: [openstack-dev] [Fuel] Install fuel-libraryX.Y as a package on slave nodes

2015-09-09 Thread Alex Schultz
ibrary package, so there's no reason you couldn't try switching the rsync to install the package if it's available on a mirror. I just think you're going to run into the issues I mentioned which need to be solved before we could just mark it done. -Alex > Vladimir Kozhukalov > > On Wed, Sep 9, 2

Re: [openstack-dev] [Fuel] Remove MOS DEB repo from master node

2015-09-09 Thread Alex Schultz
Hey Vladimir, > > The idea is to remove MOS DEB repo from the Fuel master node by default > and use online MOS repo instead. Pros of such an approach are: > > 0) Reduced requirement for the master node minimal disk space > Is this a problem? How much disk space is saved If I have to go create a

Re: [openstack-dev] [fuel][swift] Separate roles for Swift nodes

2015-09-16 Thread Alex Schultz
/? > Does it work? Is it possible to install swift in a 'base-os' role node? > > On Fri, Sep 11, 2015 at 4:11 PM, Alex Schultz <aschu...@mirantis.com> > wrote: > >> Hey Daniel, >> >> So as part of the 7.0 work we added support in plugins to be able to >&

[openstack-dev] [puppet] service default value functions

2015-09-16 Thread Alex Schultz
Hey puppet folks, Based on the meeting yesterday[0], I had proposed creating a parser function called is_service_default[1] to validate if a variable matched our agreed upon value of ''. This got me thinking about how can we maybe not use the arbitrary string throughout the puppet that can not

[openstack-dev] [fuel][fuel-library] modules managed with librarian round 2

2015-09-15 Thread Alex Schultz
Hello! So after our first round of librarian changes for 7.0, it is time to start switching to upstream for more changes. We've had a few updates during the fuel meetings over the last month[0][1]. I have begun to prepare additional reviews to move modules. The current modules available for

Re: [openstack-dev] [fuel][swift] Separate roles for Swift nodes

2015-09-11 Thread Alex Schultz
Hey Daniel, So as part of the 7.0 work we added support in plugins to be able to create roles and being able to separate roles from the existing system. I think swift would be a good candidate for this. I know we also added in some support for an external swift configuration that will be helpful

[openstack-dev] [fuel][fuel-library] librarian workflows

2015-10-01 Thread Alex Schultz
Hey Fuel folks, We have recently had some concerns around the librarian workflows and custom patches to upstream modules. I have updated the Fuel wiki[0] with additional information to try and clarify how librarian is used within fuel-library and what the rules are around the use of custom

Re: [openstack-dev] [puppet] Running Debian packages on top of Trusty

2015-10-02 Thread Alex Schultz
On Fri, Oct 2, 2015 at 7:43 AM, Ivan Udovichenko wrote: > Hello, > > On 10/02/2015 03:15 PM, Emilien Macchi wrote: >> Hey Thomas, >> >> On 10/02/2015 04:33 AM, Thomas Goirand wrote: >> [...] >>> We also may need, at some point, to add the type mosdebian and moscentos

[openstack-dev] [fuel] What to do when a controller runs out of space

2015-10-02 Thread Alex Schultz
Hey All, So I was working on Bug 1493520 which is about what happens when a controller runs out of space. For this I came up with a solution[1] to leverage pacemaker to migrate services away from the controller when it runs out of space. This works great for rabbitmq/mysql where if they run out

Re: [openstack-dev] [Fuel] Remove MOS DEB repo from master node

2015-09-09 Thread Alex Schultz
Hey Vladimir, > > >> 1) There won't be such things in like [1] and [2], thus less complicated >>> flow, less errors, easier to maintain, easier to understand, easier to >>> troubleshoot >>> 2) If one wants to have local mirror, the flow is the same as in case of >>> upstream repos

Re: [openstack-dev] [puppet] service default value functions

2015-09-23 Thread Alex Schultz
> > I've been mulling this over the last several days and I just can't > accept an entire ruby function which would be ran for every parameter > with the desired static value of "" when the class is > declared and parsed. I am not generally against using functions as a > parameter default just

Re: [openstack-dev] [puppet] service default value functions

2015-09-23 Thread Alex Schultz
On Wed, Sep 23, 2015 at 11:46 AM, Cody Herriges <c...@puppetlabs.com> wrote: > Alex Schultz wrote: >>> I've been mulling this over the last several days and I just can't >>> accept an entire ruby function which would be ran for every parameter >>> with the desir

[openstack-dev] [puppet][swift] Applying security recommendations within puppet-swift

2015-09-23 Thread Alex Schultz
Hey all, So as part of the Puppet mid-cycle, we did bug triage. One of the bugs that was looked into was bug 1289631[0]. This bug is about applying the recommendations from the security guide[1] within the puppet-swift module. So I'm sending a note out to get other feedback on if this is a

Re: [openstack-dev] [puppet] use zuul-cloner when running rspec

2015-09-24 Thread Alex Schultz
On Wed, Sep 23, 2015 at 4:56 PM, Emilien Macchi wrote: > Background > == > > Current rspec tests are tested with modules mentioned in .fixtures.yaml > file of each module. > > * the file is not consistent across all modules > * it hardcodes module names & versions > *

Re: [openstack-dev] [puppet] use zuul-cloner when running rspec

2015-09-24 Thread Alex Schultz
On Thu, Sep 24, 2015 at 1:58 PM, Emilien Macchi <emil...@redhat.com> wrote: > > > On 09/24/2015 02:19 PM, Alex Schultz wrote: >> On Thu, Sep 24, 2015 at 11:54 AM, Emilien Macchi <emil...@redhat.com> wrote: >>> >>> >>> On 09/24/2015 10:14 AM, Al

Re: [openstack-dev] [puppet] use zuul-cloner when running rspec

2015-09-24 Thread Alex Schultz
On Thu, Sep 24, 2015 at 11:54 AM, Emilien Macchi <emil...@redhat.com> wrote: > > > On 09/24/2015 10:14 AM, Alex Schultz wrote: >> On Wed, Sep 23, 2015 at 4:56 PM, Emilien Macchi <emil...@redhat.com> wrote: >>> Background >>> == >>> >

Re: [openstack-dev] [puppet][swift] Applying security recommendations within puppet-swift

2015-09-23 Thread Alex Schultz
On Wed, Sep 23, 2015 at 2:32 PM, Alex Schultz <aschu...@mirantis.com> wrote: > Hey all, > > So as part of the Puppet mid-cycle, we did bug triage. One of the > bugs that was looked into was bug 1289631[0]. This bug is about > applying the recommendations from the sec

Re: [openstack-dev] [fuel] What to do when a controller runs out of space

2015-10-05 Thread Alex Schultz
On Mon, Oct 5, 2015 at 5:56 AM, Eugene Nikanorov wrote: > Ok, > > Project-wise: > 1) Pacemaker is not under our company's control, we can't assure its quality > 2) it has terrible UX > 3) it is not reliable > I disagree with #1 as I do not agree that should be a criteria

Re: [openstack-dev] [Fuel] Disable 3.[3-7] gates for master?

2015-12-16 Thread Alex Schultz
On Wed, Dec 16, 2015 at 3:33 AM, Bartłomiej Piotrowski wrote: > Fuelers, > > with the switch to CentOS 7, we also started using Puppet 3.8 in place > of 3.4. Is there any reason to run entire range of > gate-fuel-library-puppet-unit-3.*-dsvm-centos7 tests? > > I suppose

Re: [openstack-dev] [puppet] proposing Alex Schultz part of core team

2016-01-06 Thread Alex Schultz
On Wed, Jan 6, 2016 at 4:40 PM, Emilien Macchi <emil...@redhat.com> wrote: > > > On 01/05/2016 12:55 PM, Emilien Macchi wrote: >> Hi, >> >> Alex Schultz (mwhahaha on IRC) has been a very active contributor over >> the last months in the Puppet OpenStack

Re: [openstack-dev] [Fuel] Error running RPC method verify_networks: Network verification not avaliable because nodes ["1"] not avaliable via mcollective

2015-12-18 Thread Alex Schultz
Hey John, On Fri, Dec 18, 2015 at 11:15 AM, John Menke wrote: > > > > 2015-12-17 20:49:36ERR[566] Error running RPC method verify_networks: > Network verification not avaliable because nodes ["1"] not avaliable via > mcollective, trace: >

Re: [openstack-dev] [Fuel] Error running RPC method verify_networks: Network verification not avaliable because nodes ["1"] not avaliable via mcollective

2015-12-18 Thread Alex Schultz
el/fuel-7.0/operations.html#setting-up-local-mirrors Thanks, -Alex > On Fri, Dec 18, 2015 at 1:29 PM, Alex Schultz <aschu...@mirantis.com> > wrote: > >> Hey John, >> >> >> On Fri, Dec 18, 2015 at 11:15 AM, John Menke <jmj...@gmail.com> wrote: >>

Re: [openstack-dev] [Fuel] Wipe of the nodes' disks

2015-12-24 Thread Alex Schultz
On Thu, Dec 24, 2015 at 1:29 AM, Artur Svechnikov wrote: > Hi, > We have faced the issue that nodes' disks are wiped after stop deployment. > It occurs due to the logic of nodes removing (this is old logic and it's not > actual already as I understand). This logic

Re: [openstack-dev] [Fuel] - Nominate Maksim Malchuk to Fuel Library Core

2016-06-27 Thread Alex Schultz
+1 On Mon, Jun 27, 2016 at 9:04 AM, Bogdan Dobrelya wrote: > On 06/27/2016 04:54 PM, Sergii Golovatiuk wrote: > > I am very sorry for sending without subject. I am adding subject to > > voting and my +1 > > +1 from my side! > > > > > -- > > Best regards, > > Sergii

Re: [openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

2016-01-28 Thread Alex Schultz
2016 at 11:03 AM, Aleksandr Didenko >> >> <adide...@mirantis.com <mailto:adide...@mirantis.com>> wrote: >> >> >> >> Hi, >> >> >> >> > I also think 3.3 is the version that ships with 14.04. >>

Re: [openstack-dev] [Fuel][library] relax downstream policy for puppet modules managed by librarian

2016-01-29 Thread Alex Schultz
On Fri, Jan 29, 2016 at 2:12 AM, Bogdan Dobrelya wrote: > This is a continuation of the forked discussion [0]. > > The idea is to relax Fuel-library downstream policy and implement a > "lazy downstreaming", which is to not create a downstream fork of a > puppet module

Re: [openstack-dev] [Fuel][Plugins] Tasks ordering between plugins

2016-01-27 Thread Alex Schultz
On Jan 27, 2016 4:58 PM, "Andrew Woodward" wrote: > > Simon, you should use the deployment_tasks.yaml interface (which will likely eventually move to '*/tasks.yaml' (to mimic library) This uses the same task system as granular deploy. you can set task ordering between known

Re: [openstack-dev] [puppet] is puppet-keystone using v3 credentials correctly ?

2016-02-23 Thread Alex Schultz
On Tue, Feb 23, 2016 at 1:48 AM, Ptacek, MichalX wrote: > Hello again, > > > > In last days I realized that rpm/deb packages from supported platforms are > too old (OSC, python-PROJECTclient,….) > > so I suppose that I should install newer versions not via deb/rpm

Re: [openstack-dev] [Fuel][Fuel-Library] Nominating Matthew Mosesohn for Fuel Library Core

2016-02-24 Thread Alex Schultz
+1 On Wed, Feb 24, 2016 at 5:50 AM, Vladimir Kuklin wrote: > Fellow Fuelers > > I would like to kindly ask you to consider voting for Matthew Mosesohn as > a Fuel Library Core > reviewer. > > Matthew has been working with Fuel since its inception, worked on > countless

Re: [openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

2016-01-20 Thread Alex Schultz
On Wed, Jan 20, 2016 at 9:02 AM, Matthew Mosesohn wrote: > Hi all, > > Unit tests on CI and gate bottleneck are really slowing down commit > progress. We recently had a meeting to discuss possible ways to improve > this, including symlinks, caching git repositories, etc,

[openstack-dev] [fuel] facter update has broken fuel-library ci for 3.8

2016-01-23 Thread Alex Schultz
Hey Folks, So on Friday our CI unit tests for puppet version 3.8 started failing[0] due to an update to facter which seems to have issues with one of our ceph facts[1]. This has blocked up the pipeline, so in order to unstick it we are looking at updating the ceph osd_devices_list fact[2] to

Re: [openstack-dev] [Fuel][Bugs] Time sync problem when testing.

2016-01-26 Thread Alex Schultz
On Tue, Jan 26, 2016 at 11:42 AM, Stanislaw Bogatkin wrote: > Hi guys, > > for some time we have a bug [0] with ntpdate. It doesn't reproduced 100% of > time, but breaks our BVT and swarm tests. There is no exact point where > problem root located. To better understand

Re: [openstack-dev] [Fuel][Bugs] Time sync problem when testing.

2016-01-26 Thread Alex Schultz
-v change that didn't have any response information so maybe it's the other problem where there is some network connectivity isn't working correctly or the responses are getting dropped somewhere? -Alex > > On Tue, Jan 26, 2016 at 10:41 PM, Alex Schultz <aschu...@mirantis.com> > wro

Re: [openstack-dev] [fuel] Supporting multiple Openstack versions

2016-02-17 Thread Alex Schultz
On Wed, Feb 17, 2016 at 10:23 AM, Bogdan Dobrelya wrote: > > So we'll have tons of conditionals in composition layer, right? Even if > > some puppet-openstack class have just one new parameter in new release, > > then we'll have to write a conditional and duplicate class

Re: [openstack-dev] [fuel] Supporting multiple Openstack versions

2016-02-18 Thread Alex Schultz
On Thu, Feb 18, 2016 at 4:00 AM, Aleksandr Didenko wrote: > > Given the requirements to be able to use new features in fuel, with an > older version of OpenStack, what alternative would you propose? > > For example, it's possible to use existing "release" functionality in

Re: [openstack-dev] [puppet] how to run rspec tests? r10k issue

2016-02-18 Thread Alex Schultz
On Thu, Feb 18, 2016 at 3:26 PM, Matt Fischer wrote: > Is anyone able to share the secret of running spec tests since the r10k > transition? bundle install && bundle exec rake spec have issues because > r10k is not being installed. Since I'm not the only one hopefully this

Re: [openstack-dev] [Fuel][library] Update of astute.yaml fixtures and noop tests

2016-04-07 Thread Alex Schultz
On Thu, Apr 7, 2016 at 7:41 AM, Aleksandr Didenko wrote: > Hi, > > thanks to Dima, we now have ROLE annotations in noop tests [0]. I've > updated all the noop rspec tests that we currently have and added > appropriate role annotation [1]. So after this patch is merged, we

Re: [openstack-dev] [Fuel] [shotgun] New shotgun2 command: short-report

2016-03-21 Thread Alex Schultz
oses only. > > > Once again, I'm just asking for more information as to the intended usage of this new command and asking that this information be made public. Thanks, -Alex > > > > Vladimir Kozhukalov > > On Mon, Mar 21, 2016 at 11:20 PM, Alex Schultz <aschu...

Re: [openstack-dev] [Fuel] [shotgun] New shotgun2 command: short-report

2016-03-21 Thread Alex Schultz
eproduce the environment they occur on. I'm trying to make sure we are providing all the information to aid in reproducing issues to get them fixed and not just providing more information that is ultimately ignored because it's useless. Thanks, -Alex > > > Vladimir Kozhukalov > >

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

2016-03-22 Thread Alex Schultz
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

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

2016-03-25 Thread Alex Schultz
On Fri, Mar 25, 2016 at 7:32 AM, Dmitry Guryanov wrote: > Here is the bug which I'm trying to fix - > https://bugs.launchpad.net/fuel/+bug/1538587. > > In VMs (set up with fuel-virtualbox) kernel panic occurs every time you > delete node, stack trace shows error in ext4

Re: [openstack-dev] [Fuel] [shotgun] New shotgun2 command: short-report

2016-03-21 Thread Alex Schultz
On Mon, Mar 21, 2016 at 7:21 AM, Volodymyr Shypyguzov < vshypygu...@mirantis.com> wrote: > Hi, all > > Just wanted to inform you, that shotgun2 now has new command short-report, > which allows you to receive shorter and cleaner output for attaching to bug > description, sharing, etc. > > Usage:

Re: [openstack-dev] [puppet] proposal to create puppet-neutron-core and add Sergey Kolekonov

2016-03-04 Thread Alex Schultz
+1 On Fri, Mar 4, 2016 at 10:07 AM, Matt Fischer wrote: > +1 from me! > > gmail/openstack-dev is doing its thing where I see your email 4 hours > before Emilien's original, so apologies for the reply ordering > > On Fri, Mar 4, 2016 at 8:49 AM, Cody Herriges

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

2016-03-03 Thread Alex Schultz
On Thu, Mar 3, 2016 at 7:19 AM, Matthew Mosesohn wrote: > > Hi Fuelers, > > I would like to bring your attention a dilemma we have here. It seems > that there is a dispute as to whether we should maintain the releases > list for example plugins[0]. In this case, this is

Re: [openstack-dev] [puppet][ec2api] - Official EC2 puppet module repo

2016-04-04 Thread Alex Schultz
On Mon, Apr 4, 2016 at 9:12 AM, Denis Egorenko wrote: > Hi Marcos, > > Are you still working on your initial commit to puppet-ec2api [1] ? > > [1] https://review.openstack.org/#/c/276103/ > It might be a good idea to redo this review with a newer version of the

Re: [openstack-dev] [puppet] Proposing Ivan Berezovskiy for puppet-openstack-core

2016-05-19 Thread Alex Schultz
+1 great job Ivan On Thu, May 19, 2016 at 8:32 AM, Matt Fischer wrote: > +1 from me! > > On Thu, May 19, 2016 at 8:17 AM, Emilien Macchi > wrote: > >> Hi, >> >> I don't need to introduce Ivan Berezovskiy (iberezovskiy on IRC), he's >> been doing

Re: [openstack-dev] [fuel] switch to upstream haproxy module

2016-05-12 Thread Alex Schultz
t/modules/plugin_zabbix/manifests/ha/haproxy.pp#L16 > [2] > https://github.com/openstack/fuel-plugin-lma-collector/blob/master/deployment_scripts/puppet/manifests/aggregator.pp#L60-L81 > > On Thu, May 12, 2016 at 4:42 PM, Alex Schultz <aschu...@mirantis.com> > wrote: > >&g

[openstack-dev] [fuel] switch to upstream haproxy module

2016-05-12 Thread Alex Schultz
Hey Fuelers, We have been using our own fork of the haproxy module within fuel-library for some time. This also includes relying on a MOS specific version of haproxy that carries the conf.d hack. Unfortunately this has meant that we've needed to leverage the MOS version of this package when

Re: [openstack-dev] [fuel] switch to upstream haproxy module

2016-05-12 Thread Alex Schultz
is that the task logic no longer would control if something was included like sahara. -Alex [0] https://review.openstack.org/#/c/307538/9/deployment/puppet/osnailyfacter/modular/cluster-haproxy/cluster-haproxy.pp > On Thu, May 12, 2016 at 5:34 PM, Alex Schultz <aschu...@mirantis.com> > wro

Re: [openstack-dev] [puppet] Propose Sofer Athlan-Guyot (chem) part of Puppet OpenStack core

2016-07-28 Thread Alex Schultz
+1 On Thu, Jul 28, 2016 at 9:16 AM, Emilien Macchi wrote: > You might not know who Sofer is but he's actually "chem" on IRC. > He's the guy who will find the root cause of insane bugs, in OpenStack > in general but also in Puppet OpenStack modules. > Sofer has been working on

[openstack-dev] [puppet] Effort to standardize keystone middleware configurations

2016-07-19 Thread Alex Schultz
Hey All, During our meeting today we discussed getting the keystone middleware configuration for the services properly migrated to use the keystone::resource::authtoken resource. I've created a bug[0] to track the effort. If you wish to assist with this effort, please update the bug with your

Re: [openstack-dev] [Fuel] Replace OSTF with Rally

2016-06-27 Thread Alex Schultz
On Mon, Jun 27, 2016 at 7:10 AM, Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > Dear colleagues, > > I'd like to suggest to replace Fuel-ostf with Rally. Rally is quite > popular project and as far as I know it has all necessary features > (including dashboard). We only need to

[openstack-dev] [puppet] No meeting today - Jan 31, 2017

2017-01-31 Thread Alex Schultz
Hi all, Since the agenda[0] for the meeting is empty, I'm canceling the meeting. If you wish to talk about something next week, please add it to the agenda[1]. Thanks, -Alex [0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170131 [1]

[openstack-dev] [puppet] No meeting Feb 7, 2017, next meeting Feb 14, 2017

2017-02-07 Thread Alex Schultz
Hey all, The agenda etherpad[0] was empty so we're skipping today's meeting. The next meeting will be on Feb 14th, 2017. If you have something to discuss, please add it to the agenda etherpad[1]. Thanks, -Alex [0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170207 [1]

Re: [openstack-dev] [puppet] Nominating mkarpin for core for the Puppet OpenStack modules

2017-01-26 Thread Alex Schultz
On Thu, Jan 19, 2017 at 3:25 PM, Alex Schultz <aschu...@redhat.com> wrote: > Hey Puppet Cores, > > I would like to nominate Mykyta Karpin as a Core reviewer for the > Puppet OpenStack modules. He has been providing quality patches and > reviews for some time now and I belie

Re: [openstack-dev] [puppet] Nominating zhongshengping for core of the Puppet OpenStack modules

2017-01-27 Thread Alex Schultz
On Fri, Jan 20, 2017 at 10:19 AM, Alex Schultz <aschu...@redhat.com> wrote: > Hey Puppet Cores, > > I would like to nominate Zhong Shengping as a Core reviewer for the > Puppet OpenStack modules. He is an excellent contributor to our > modules over the last several cycles. H

Re: [openstack-dev] [puppet] CI status for Ubuntu

2017-01-25 Thread Alex Schultz
On Tue, Jan 24, 2017 at 6:43 AM, Corey Bryant <corey.bry...@canonical.com> wrote: > > On Fri, Jan 20, 2017 at 6:34 PM, Alex Schultz <aschu...@redhat.com> wrote: >> >> Just FYI, >> >> We switched the Ubuntu scenario jobs to non-voting this week due

[openstack-dev] [puppet] PTL candidacy

2017-01-20 Thread Alex Schultz
configurations have already been removed. I look forward to working with all of you. As always, I'm open to any suggestions or ideas for additional places to improve our processes and modules. Thanks, Alex Schultz irc: mwhahaha https://review.openstack.org/423514

[openstack-dev] [puppet] CI status for Ubuntu

2017-01-20 Thread Alex Schultz
Just FYI, We switched the Ubuntu scenario jobs to non-voting this week due to the large amount of breakage caused by the ocata-proposed update to m2 based packages. The Ubuntu beaker jobs are still voting on the modules themselves. Here's where we're keeping track of issues:

[openstack-dev] [puppet] Reminder next meeting on Feb 28 @ 1500 UTC

2017-02-20 Thread Alex Schultz
Due to the PTG this week, we are skipping the meeting tomorrow. The next meeting will be on Feb 28th. The agenda[0] is currently empty. If you have something you wish to talking about, please add it to the list. Thanks, -Alex [0]

Re: [openstack-dev] [Openstack-operators] [puppet][fuel][packstack][tripleo] puppet 3 end of life

2017-02-17 Thread Alex Schultz
/releases.html#releases-summary On Fri, Nov 11, 2016 at 2:11 PM, Alex Schultz <aschu...@redhat.com> wrote: > On Thu, Nov 3, 2016 at 11:31 PM, Sam Morrison <sorri...@gmail.com> wrote: >> >> On 4 Nov. 2016, at 1:33 pm, Emilien Macchi <emil...@redhat.com> wrote: >> >>

[openstack-dev] [puppet] mascot

2017-02-14 Thread Alex Schultz
Hey folks, The final mascot is available for viewing here: https://www.dropbox.com/sh/oax7i1xvca3edxc/AAAtfQSyx0rJijKBoqoZmp-va?dl=0 Thanks, -Alex __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [puppet] Reminder meeting on Feb 14th @ 1500 UTC

2017-02-13 Thread Alex Schultz
Just a reminder but we will be having our meeting tomorrow Feb 14th at 1500 UTC in #openstack-meeting-4 unless the agenda[0] remains empty. So if you have something you wish to talk about it, please add it to the agenda. As always the the previous meeting logs and agendas are reviewable here[1].

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

2017-02-16 Thread Alex Schultz
On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe wrote: > On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: > >> When we signed off on the Big Tent changes we said competition >> between projects was desirable, and that deployers and contributors >> would make

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

2017-02-15 Thread Alex Schultz
On Wed, Feb 15, 2017 at 9:02 AM, Samuel Cassiba wrote: > >> On Feb 15, 2017, at 02:07, Thierry Carrez wrote: >> >> Samuel Cassiba wrote: >>> [...] >>> *TL;DR* if you don't want to keep going - >>> OpenStack-Chef is not in a good place and is not

[openstack-dev] [puppet] Nominating mkarpin for core for the Puppet OpenStack modules

2017-01-19 Thread Alex Schultz
Hey Puppet Cores, I would like to nominate Mykyta Karpin as a Core reviewer for the Puppet OpenStack modules. He has been providing quality patches and reviews for some time now and I believe he would be a good addition to the team. His stats for the last 90 days can be viewed here[0] Please

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

2017-01-19 Thread Alex Schultz
On Thu, Jan 19, 2017 at 11:45 AM, Jay Pipes <jaypi...@gmail.com> wrote: > On 01/19/2017 01:18 PM, Alex Schultz wrote: >> >> On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes <jaypi...@gmail.com> wrote: >>> >>> On 01/19/2017 11:25 AM, Alex Schultz wrote: &

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

2017-01-19 Thread Alex Schultz
On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes <jaypi...@gmail.com> wrote: > On 01/19/2017 11:25 AM, Alex Schultz wrote: >> >> On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann >> <mrie...@linux.vnet.ibm.com> wrote: >>> >>> Sylvain and I

  1   2   3   4   >