On Tue, 2014-08-12 at 06:58 +1200, Robert Collins wrote:
> Hi, so shortly after the HOT migration landed, we hit
> https://bugs.launchpad.net/tripleo/+bug/1354305 which is that on even
> quite recently deployed clouds, the migrated templates were just too
> new. A partial revert (of just the list_j
On Thu, 2014-09-04 at 11:24 +0100, Daniel P. Berrange wrote:
> Position statement
> ==
>
> Over the past year I've increasingly come to the conclusion that
> Nova is heading for (or probably already at) a major crisis. If
> steps are not taken to avert this, the project is likely t
I pushed a patch[1] to update our containerized deployment
architecture docs yesterday. There are 2 new fairly useful sections we
can leverage with TripleO's stepwise deployment. They appear to be
used somewhat sparingly so I wanted to get the word out.
The first is 'deploy_steps_tasks' which give
On Mon, Nov 5, 2018 at 4:06 AM Cédric Jeanneret wrote:
>
> On 11/2/18 2:39 PM, Dan Prince wrote:
> > I pushed a patch[1] to update our containerized deployment
> > architecture docs yesterday. There are 2 new fairly useful sections we
> > can leverage with TripleO
On Tue, 2018-11-27 at 16:24 +0100, Bogdan Dobrelya wrote:
> Changing the topic to follow the subject.
>
> [tl;dr] it's time to rearchitect container images to stop incluiding
> config-time only (puppet et al) bits, which are not needed runtime
> and
> pose security issues, like CVEs, to maintain
the example pod example above is still
> usable without k8s?
>
> Thanks,
> Kevin
>
> From: Dan Prince [dpri...@redhat.com]
> Sent: Tuesday, November 27, 2018 10:10 AM
> To: OpenStack Development Mailing List (not for usage questions);
> openstack-disc
On Wed, 2018-11-28 at 12:45 +0100, Bogdan Dobrelya wrote:
> To follow up and explain the patches for code review:
>
> The "header" patch https://review.openstack.org/620310 -> (requires)
> https://review.rdoproject.org/r/#/c/17534/, and also
> https://review.openstack.org/620061 -> (which in tur
On Wed, 2018-11-28 at 15:12 +0100, Bogdan Dobrelya wrote:
> On 11/28/18 2:58 PM, Dan Prince wrote:
> > On Wed, 2018-11-28 at 12:45 +0100, Bogdan Dobrelya wrote:
> > > To follow up and explain the patches for code review:
> > >
> > > The "header&q
On Wed, 2018-11-28 at 13:28 -0500, James Slagle wrote:
> On Wed, Nov 28, 2018 at 12:31 PM Bogdan Dobrelya > wrote:
> > Long story short, we cannot shoot both rabbits with a single shot,
> > not
> > with puppet :) May be we could with ansible replacing puppet
> > fully...
> > So splitting config an
On Fri, 2018-11-30 at 10:31 +0100, Bogdan Dobrelya wrote:
> On 11/29/18 6:42 PM, Jiří Stránský wrote:
> > On 28. 11. 18 18:29, Bogdan Dobrelya wrote:
> > > On 11/28/18 6:02 PM, Jiří Stránský wrote:
> > > >
> > > >
> > > > > Reiterating again on previous points:
> > > > >
> > > > > -I'd be fine r
- Original Message -
> From: "Matt Riedemann"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Wednesday, December 18, 2013 12:27:49 PM
> Subject: [openstack-dev] Adding DB migration items to the common review
> checklist
>
> I've seen this come up
- Original Message -
> From: "Michael Still"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Thursday, January 2, 2014 7:48:16 PM
> Subject: Re: [openstack-dev] [nova] Turbo-hipster
>
> On Fri, Jan 3, 2014 at 9:39 AM, Michael Still wrote:
> > On Fri, Ja
- Original Message -
> From: "James Slagle"
> To: "OpenStack Development Mailing List"
> Sent: Tuesday, January 7, 2014 3:01:07 PM
> Subject: [openstack-dev] [TripleO] Installing from packages in
> tripleo-image-elements
>
> Hi,
>
> I'd like to discuss some possible ways we co
- Original Message -
> From: "James Slagle"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Tuesday, January 7, 2014 3:53:57 PM
> Subject: Re: [openstack-dev] [TripleO] Installing from packages in
> tripleo-image-elements
>
> On Tue, Jan 7, 2014 at 3
- Original Message -
> From: "Clint Byrum"
> To: "openstack-dev"
> Sent: Tuesday, January 7, 2014 3:23:24 PM
> Subject: Re: [openstack-dev] [TripleO] Installing from packages in
> tripleo-image-elements
>
> What would be the benefit of using packages?
>
> We've specifically avoide
- Original Message -
> From: "Jay Pipes"
> To: openstack-dev@lists.openstack.org
> Sent: Wednesday, January 8, 2014 2:29:22 PM
> Subject: Re: [openstack-dev] [Neutron] Multiple config files for neutron
> server
>
> On Wed, 2014-01-08 at 07:21 -0500, Sean Dague wrote:
> > On 01/06/2014
- Original Message -
> From: "Michael Still"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Tuesday, January 7, 2014 5:53:01 PM
> Subject: Re: [openstack-dev] [nova] Bogus -1 scores from turbo hipster
>
> Hi. Thanks for reaching out about this.
>
> It
- Original Message -
> From: "Derek Higgins"
> To: "OpenStack Development Mailing List"
> Sent: Thursday, January 9, 2014 8:13:53 AM
> Subject: [openstack-dev] os-*-config in tripleo repositories
>
> It looks like we have some duplication and inconsistencies on the 3
> os-*-config elem
One more related idea related to real packages in TripleO. While I still think
using packages is totally cool we may want to make an exception for
systemd/upstart scripts. We have some non-standard ordering in our TripleO init
scripts that is meaningful and blindly switching to a distro specific
I've been thinking a bit more about how TripleO updates are developing
specifically with regards to compute nodes. What is commonly called the "update
story" I think.
As I understand it we expect people to actually have to reboot a compute node
in the cluster in order to deploy an update. This
- Original Message -
> From: "Clint Byrum"
> To: "openstack-dev"
> Sent: Wednesday, January 22, 2014 12:45:45 PM
> Subject: Re: [openstack-dev] [TripleO] our update story: can people live
> with it?
>
> Excerpts from Dan Prince's message of 2014-01-22 09:17:24 -0800:
> > I've bee
- Original Message -
> From: "Robert Collins"
> To: "OpenStack Development Mailing List"
> Sent: Sunday, January 26, 2014 3:30:22 PM
> Subject: [openstack-dev] [TripleO] State preserving upgrades working, next
> MVP selection?
>
> So great news - we've now got state preserving upgrade
- Original Message -
> From: "Clint Byrum"
> To: "openstack-dev"
> Sent: Monday, January 27, 2014 12:48:23 PM
> Subject: Re: [openstack-dev] [TripleO] State preserving upgrades working,
> next MVP selection?
>
> Excerpts from Dan Prince's message of 2014-01-27 09:22:21 -0800:
> >
- Original Message -
> From: "Andrey Danin"
> To: openstack-dev@lists.openstack.org, "fuel-dev"
>
> Sent: Tuesday, February 11, 2014 11:42:46 AM
> Subject: [openstack-dev] [Fuel][TripleO] NIC bonding for OpenStack
>
> Hi Openstackers,
>
> We are working on link aggregation support in
- Original Message -
> From: "Robert Collins"
> To: "OpenStack Development Mailing List" ,
> openstack-operat...@lists.openstack.org
> Sent: Thursday, February 13, 2014 4:27:20 PM
> Subject: [openstack-dev] [TripleO] consistency vs packages in TripleO
>
> So progressing with the 'and f
[openstack-dev] [TripleO] consistency vs
> packages in TripleO
>
> On 15 February 2014 08:42, Dan Prince wrote:
> >
>
> > Let me restate the options the way I see it:
> >
> > Option A is we do our job... by making it possible to install OpenStack
> &g
Perhaps one of the lesser know Gerrit "features" is the ability to overwrite
someone else's patchset/review with a new revision. This can be a handy thing
for collaboration, or perhaps to make minor edits (spelling fixes for example)
to help expedite the review process. Generally I think things
On Wed, 2014-12-03 at 10:11 +, Steven Hardy wrote:
> Hi all,
>
> Lately I've been spending more time looking at tripleo and doing some
> reviews. I'm particularly interested in helping the no-mergepy and
> subsequent puppet-software-config implementations mature (as well as
> improving overclo
On Thu, 2014-12-04 at 15:47 +1100, Steve Kowalik wrote:
> Hi all,
>
> I'm becoming increasingly concerned about all of the code paths
> in tripleo-incubator that check $USE_IRONIC -eq 0 -- that is, use
> nova-baremetal rather than Ironic. We do not check nova-bm support in
> CI, haven't for
On Thu, 2014-12-04 at 10:11 +0100, James Polley wrote:
> Hi all,
>
>
> The other topic that has come up a few times in our meetings is: what
> value do we get from these meetings?
Often. Not much. :( Partially my own fault too since I haven't been good
about adding items to the agenda myself ah
On Thu, 2014-12-04 at 11:51 +, Derek Higgins wrote:
> A month since my last update, sorry my bad
>
> since the last email we've had 5 incidents causing ci failures
>
> 26/11/2014 : Lots of ubuntu jobs failed over 24 hours (maybe half)
> - We seem to suffer any time an ubuntu mirror isn't in s
On Wed, 2014-12-03 at 14:42 +0100, Tomas Sedovic wrote:
> On 12/03/2014 11:11 AM, Steven Hardy wrote:
> > Hi all,
> >
> > Lately I've been spending more time looking at tripleo and doing some
> > reviews. I'm particularly interested in helping the no-mergepy and
> > subsequent puppet-software-confi
On Wed, 2015-01-14 at 10:14 -0800, Clint Byrum wrote:
> Hello! It has been a while since we expanded our review team. The
> numbers aren't easy to read with recent dips caused by the summit and
> holidays. However, I believe James has demonstrated superb review skills
> and a commitment to the proj
On Wed, 2015-01-07 at 10:51 +, Derek Higgins wrote:
> Hi All,
> I intended to bring this up at this mornings meeting but the train I
> was on had no power sockets (and I had no battery) so sending to the
> list instead.
>
> We currently run our CI with on images built for i386, we took thi
A bit of background TripleO CI background:
At this point we've got two public CI overcloud which we can use to run
TripleO check jobs for CI. Things are evolving nicely and we've recently been
putting some effort into making things run faster by adding local distro and
Pypi mirrors. Etc. This
ld like to
avoid that if possible as it is more resource heavy. Especially because we'll
need to do the same things in each rack for Fedora and Ubuntu (both of which
run in each TripleO CI test rack).
Dan
- Forwarded Message -----
From: "Dan Prince"
To: "OpenStack Developme
- Original Message -
> From: "Devananda van der Veen"
> To: "OpenStack Development Mailing List"
> Sent: Wednesday, May 21, 2014 8:03:15 PM
> Subject: [openstack-dev] [Ironic] handling drivers that will not be
> third-party tested
>
> I'd like to bring up the topic of drivers which,
- Original Message -
> From: "Doug Hellmann"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Thursday, May 22, 2014 3:18:22 PM
> Subject: Re: [openstack-dev] [Ironic] handling drivers that will not be
> third-party tested
>
> On Thu, May 22, 2014 at 4:4
A few months back several of us were consistently hitting file system
resize issues. After making a slight change to diskimage-builder to fix
[1] things seem to have gotten better... but I still hear people
occasionally mentioning issues.
On the ext4 mailing list it appears there are still some on
On Thu, 2014-06-12 at 08:06 -0400, Sean Dague wrote:
> We're definitely deep into capacity issues, so it's going to be time to
> start making tougher decisions about things we decide aren't different
> enough to bother testing on every commit.
In order to save resources why not combine some of the
On Thu, 2014-06-12 at 09:24 -0700, Joe Gordon wrote:
>
> On Jun 12, 2014 8:37 AM, "Sean Dague" wrote:
> >
> > On 06/12/2014 10:38 AM, Mike Bayer wrote:
> > >
> > > On 6/12/14, 8:26 AM, Julien Danjou wrote:
> > >> On Thu, Jun 12 2014, Sean Dague wrote:
> > >>
> > >>> That's not cacthable in unit o
On Sat, 2014-06-14 at 08:40 +1000, Michael Still wrote:
> Greetings,
>
> I would like to nominate Ken'ichi Ohmichi for the nova-core team.
>
> Ken'ichi has been involved with nova for a long time now. His reviews
> on API changes are excellent, and he's been part of the team that has
> driven th
- Original Message -
> From: "Robert Collins"
> To: "OpenStack Development Mailing List"
> Sent: Thursday, March 13, 2014 5:51:30 AM
> Subject: [openstack-dev] [TripleO] test environment requirements
>
> So we already have pretty high requirements - its basically a 16G
> workstation as
- Original Message -
> From: "Clint Byrum"
> To: "openstack-dev"
> Sent: Sunday, March 23, 2014 9:02:23 PM
> Subject: Re: [openstack-dev] [TripleO] test environment requirements
>
> Excerpts from Dan Prince's message of 2014-03-21 09:25:42 -0700:
> >
> > - Original Message -
>
- Original Message -
> From: "Robert Collins"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Sunday, March 23, 2014 11:18:19 PM
> Subject: Re: [openstack-dev] [TripleO] test environment requirements
>
> On 24 March 2014 14:06, Clint Byrum wrote:
> > Ex
- Original Message -
> From: "Robert Collins"
> To: "OpenStack Development Mailing List"
> Sent: Monday, April 7, 2014 4:00:30 PM
> Subject: [openstack-dev] [TripleO] config options, defaults, oh my!
>
> So one interesting thing from the influx of new reviews is lots of
> patches expos
- Original Message -
> From: "Robert Collins"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Monday, April 7, 2014 7:50:57 PM
> Subject: Re: [openstack-dev] [TripleO] reviewer update march [additional
> cores]
>
> tl;dr: 3 more core members to pro
- Original Message -
> From: "Ben Nemec"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Monday, April 14, 2014 12:26:17 PM
> Subject: [openstack-dev] [tripleo] /bin/bash vs. /bin/sh
>
> tldr: I propose we use bash explicitly for all diskimage-builder sc
- Original Message -
> From: "Clint Byrum"
> To: "openstack-dev"
> Sent: Friday, April 11, 2014 4:17:27 PM
> Subject: Re: [openstack-dev] [TripleO] tripleo-heat-templates migration to
> software-config: please rebase on top
>
> Another massive change just landed in front of 81666.
are giving us good
> stuff, or even easy stuff, as we respond quickly.
>
> Recommendation #1: we adopt a 0 new bugs policy to keep this from
> getting away from us in the future.
>
> == Our worse bug reporters are often core reviewers ==
>
> I'm going to pick on
Not a great week for TripleO CI. We had 3 different failures related to:
Nova [1]: we were using a deprecated config option
Heat [2]: missing heat data obtained from the Heat CFN API
Neutron [3]: a broken GRE overlay network setup
The TripleO check jobs look to be running stable again today so
On Fri, 2014-06-20 at 16:51 -0400, Charles Crouch wrote:
>
> - Original Message -
> > Not a great week for TripleO CI. We had 3 different failures related to:
> >
> > Nova [1]: we were using a deprecated config option
> > Heat [2]: missing heat data obtained from the Heat CFN API
> > N
On Wed, 2014-05-21 at 17:03 -0700, Devananda van der Veen wrote:
> I'd like to bring up the topic of drivers which, for one reason or
> another, are probably never going to have third party CI testing.
>
>
> Take for example the iBoot driver proposed here:
> https://review.openstack.org/50977
>
Hi TripleO!
It would appear that we have no coverage in devtest which ensures that
Cinder consistently works in the overcloud. As such the TripleO Cinder
elements are often broken (as of today I can't fully use lio or tgt w/
upstream TripleO elements).
How do people feel about swapping out our si
Hi TripleO!
I wanted to get the word out on progress with a new os-net-config tool
for TripleO. The spec (not yet approved) lives here:
https://review.openstack.org/#/c/97859/
We've also got a working implementation here:
https://github.com/dprince/os-net-config
You can see WIP example of how
On Thu, 2014-07-17 at 15:54 +0100, Michael Kerrin wrote:
> On Thursday 26 June 2014 12:20:30 Clint Byrum wrote:
>
> > Excerpts from Macdonald-Wallace, Matthew's message of 2014-06-26
> 04:13:31 -0700:
>
> > > Hi all,
>
> > >
>
> > > I've been working more and more with TripleO recently and whi
On Wed, 2014-07-30 at 14:02 -0700, Michael Still wrote:
> Greetings,
>
> I would like to nominate Jay Pipes for the nova-core team.
>
> Jay has been involved with nova for a long time now. He's previously
> been a nova core, as well as a glance core (and PTL). He's been around
> so long that the
On Sun, 2014-08-03 at 07:59 +1200, Robert Collins wrote:
> We had a few whiteboard photos taken during the sprint, but I can't
> find where they were posted :/
>
> Right now I'm looking for the one with the list of priority CI jobs,
I don't have the photo. But it looks like someone wrote them dow
Hi all,
A quick update on some recent SmokeStack additions in the Havana dev cycle:
Several weeks back we added support for Ceilometer. Test configuration using
both MongoDB (Fedora 19) and MySQL (Centos 6.4) are currently being used to
test Ceilometer. Currently only the compute agent is being
- Original Message -
> From: "Robert Collins"
> To: "OpenStack Development Mailing List"
> Sent: Thursday, October 3, 2013 4:22:26 PM
> Subject: [openstack-dev] [TripleO] Continual deployment scripts
>
> This is a proposal: I think we should not use toci in the
> continually-deployed i
Hi Robert,
In general I buy the vision laid out in this email. I think "Starting with the
customer story" will keep us on the right track as to what features to
implement, working on most important stuff, etc. A CD tripleO setup sounds just
grand. For me though most of what you've laid out here
-1
Slight preference for keeping them. I personally would go the other way and
just add them everywhere.
- Original Message -
> From: "Joe Gordon"
> To: "OpenStack Development Mailing List"
> Sent: Thursday, October 24, 2013 8:38:57 AM
> Subject: [openstack-dev] Remove vim modelines?
- Original Message -
> From: "David Ripton"
> To: openstack-dev@lists.openstack.org
> Sent: Friday, November 15, 2013 1:47:58 PM
> Subject: Re: [openstack-dev] sqlalchemy-migrate needs a new release
>
> On 11/15/2013 10:41 AM, David Ripton wrote:
>
> > sqlalchemy-migrate-0.8.1 is now u
Just started seeing these in SmokeStack:
https://bugs.launchpad.net/nova/+bug/1194264
I pushed a revert which should fix the issue:
https://review.openstack.org/#/c/34256/
Dan
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://li
As of an hour ago the el6 (Centos) builds in SmokeStack all started failing.
I've documented the initial issue I'm seeing in this ticket:
https://bugs.launchpad.net/nova/+bug/1208656
The issue seems to be that we now hit a SchemaError which bubbles up from
glanceclient when the new direct down
unresolved however and it looks like we still have
some work to do to get all the fancy new Glance V2 stuff fully working on
python 2.6 distros (RHEL/Centos, etc).
Dan
- Original Message -
> From: "Dan Prince"
> To: "OpenStack Development Mailing List"
> Sent: M
All of my Neutron tests are failing this morning in SmokeStack. We need a quick
revert to fix the qpid RPC implementation:
https://review.openstack.org/41689
https://bugs.launchpad.net/neutron/+bug/1211778
I figure we may as well revert this quick and then just wait on oslo.messaging
to fix th
- Original Message -
> From: "Jay Pipes"
> To: "OpenStack Development Mailing List"
> Sent: Wednesday, August 14, 2013 12:42:29 PM
> Subject: [openstack-dev] [Ceilometer] SQL meter table schema improvements
>
> Hi all,
>
> I submitted a bug report to improve the schema of the meter ta
- Original Message -
> From: "Matthew Treinish"
> To: openstack-dev@lists.openstack.org
> Sent: Tuesday, August 13, 2013 4:25:14 PM
> Subject: [openstack-dev] Migrating to testr parallel in tempest
>
>
> Hi everyone,
>
> So for the past month or so I've been working on getting tempest
Hi all,
I'd like to highlight this Glance revert for an issue I started seeing on
Fedora 19 last week.
https://review.openstack.org/#/c/43542/
A revert like this should be a very safe thing to do so long as we do it
quickly. Especially given this is a performance improvement...
Dan
___
So I recently ran into a fun config issue in trying to configure Nova to work
w/ Ceilometer using Puppet:
https://bugs.launchpad.net/puppet-ceilometer/+bug/1217867
Today, what you need to do to make Nova work with ceilometer is add this to
your nova.conf file:
notification_driver=nova.opens
neer
> Cloud Solutions and OpenStack Development
>
> Phone: 1-507-253-7622 | Mobile: 1-507-990-1889
> E-mail: mrie...@us.ibm.com
>
>
> 3605 Hwy 52 N
> Rochester, MN 55901-1407
> United States
>
>
>
>
> From: Dan Prince
> To: OpenStack Dev
- Original Message -
> From: "Bob Ball"
> To: "OpenStack Development Mailing List" ,
> "Mark McLoughlin"
> Cc: "Dan Prince (dpri...@redhat.com)"
> Sent: Friday, September 6, 2013 10:21:45 AM
> Subject: RE: [openstack-dev] [N
In case you haven't found this yet the TripleO etherpad locations are
all documented here:
https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#TripleO
Dan
__
OpenStack Development Mailing List (not for usage quest
On Tue, 2015-11-03 at 15:25 +, Gregory Haynes wrote:
> Hello everyone,
>
> I would like to propose adding Ian Wienand as a core reviewer on the
> diskimage-builder project. Ian has been making a significant number
> of
> contributions for some time to the project, and has been a great help
> i
There are lots of references to "workflow" within TripleO conversations
these days. We are at (or near) the limit of what we can do within Heat
with regards to upgrades. We've got a new TripleO API in the works (a
new version of Tuskar basically) that is specifically meant to
encapsulates business
On Fri, 2015-11-20 at 16:53 +0100, Jiri Tomasek wrote:
> On 11/16/2015 04:25 PM, Steven Hardy wrote:
> > Hi all,
> >
> > I wanted to start some discussion re $subject, because it's been
> > apparrent
> > that we have a lack of clarity on this issue (and have done ever
> > since we
> > started usin
On Thu, 2015-11-19 at 16:16 +, Steven Hardy wrote:
> On Mon, Nov 16, 2015 at 08:15:48PM +0100, Giulio Fidente wrote:
> > On 11/16/2015 04:25 PM, Steven Hardy wrote:
> > > Hi all,
> > >
> > > I wanted to start some discussion re $subject, because it's been
> > > apparrent
> > > that we have a l
On Mon, 2015-11-23 at 11:43 -0500, Ruby Loo wrote:
> On 20 November 2015 at 18:32, Ben Nemec
> wrote:
> > On 11/19/2015 06:00 AM, Lucas Alvares Gomes wrote:
> > > Hi,
> > >
> > >> Also keep in mind that DEBUG logging, while still should have
> > some masking
> > >> of data, since it is explicitly
On Wed, 2015-12-02 at 16:02 +, Steven Hardy wrote:
> So, chatting with Giulio today about https://bugs.launchpad.net/heat/
> +bug/1521944
> has be thinking about $subject.
>
> The root case of that issue is essentially a corner case of a stack-
> update,
> combined with some coupling within th
On Tue, 2015-11-24 at 15:25 +, Dougal Matthews wrote:
> On 23 November 2015 at 14:37, Dan Prince wrote:
> > There are lots of references to "workflow" within TripleO
> > conversations
> > these days. We are at (or near) the limit of what we can do within
> &
On Thu, 2015-12-03 at 15:47 -0500, Dan Prince wrote:
> On Tue, 2015-11-24 at 15:25 +, Dougal Matthews wrote:
> > On 23 November 2015 at 14:37, Dan Prince
> > wrote:
> > > There are lots of references to "workflow" within TripleO
> > > conversation
On Mon, 2015-12-07 at 16:00 +, Dougal Matthews wrote:
>
>
> On 7 December 2015 at 14:59, Dan Prince wrote:
> >
> >
> >
> > On Thu, 2015-12-03 at 15:47 -0500, Dan Prince wrote:
> > > On Tue, 2015-11-24 at 15:25 +, Dougal Matthews wrote:
> &
On Tue, 2016-05-17 at 20:03 +0300, Sagi Shnaidman wrote:
> Hi,
> raising again the question about tempest running on TripleO CI as it
> was discussed in the last TripleO meeting.
>
> I'd like to get your attention that in these tests, which I ran just
> for ensure it works, there were bugs discove
On Thu, 2016-05-19 at 15:31 +0200, Dmitry Tantsur wrote:
> Hi all!
>
> We started some discussions on https://review.openstack.org/#/c/30020
> 0/
> about the future of node management (registering, configuring and
> introspecting) in the new API, but I think it's more fair (and
> convenient) to
On Fri, 2016-05-20 at 17:52 +0200, Jiri Tomasek wrote:
> Hey all,
>
> I've been recently working on getting the TripleO UI integrated with
> Zaqar, so it can receive a messages from Mistral workflows and act
> upon them without having to do various polling hacks.
>
> Since there is currently quit
On Fri, 2016-05-20 at 14:06 +0200, Dmitry Tantsur wrote:
> On 05/20/2016 01:44 PM, Dan Prince wrote:
> >
> > On Thu, 2016-05-19 at 15:31 +0200, Dmitry Tantsur wrote:
> > >
> > > Hi all!
> > >
> > > We started some discussions on https://review.
Hi all,
Having a bit of a CI outage today due to (I think) the switch to Centos
Jenkins slaves. I'd like to suggest that we revert that quickly to keep
things moving in TripleO:
https://review.openstack.org/326182 Revert "Migrate tripleo to centos-
7"
And then perhaps we can follow up with a bit
Sending it again to [TripleO].
On Mon, 2016-06-06 at 20:06 -0400, Dan Prince wrote:
> Hi all,
>
> Having a bit of a CI outage today due to (I think) the switch to
> Centos
> Jenkins slaves. I'd like to suggest that we revert that quickly to
> keep
> things mov
On Thu, 2016-06-09 at 15:03 +0100, Steven Hardy wrote:
> Hi all,
>
> I've been in discussion with Martin André and Tomas Sedovic, who are
> involved with the creation of the new tripleo-validations repo[1]
>
> We've agreed that rather than create another gerrit group, they can
> be
> added to tri
I left some comments on the wireframes themselves. One general concept
I would like to see capture is to make sure that things across the UI
and CLI have parity.
Specifically things like if I register nodes on the CLI we use a JSON
file format:
http://tripleo.org/environments/environments.html#in
Thanks Emilien,
I marked the bug below as a duplicate of this issue I had filed earlier
with this title "CI jobs failing, mirror-server is down
(192.168.1.101)":
https://bugs.launchpad.net/tripleo/+bug/1594161
The root cause of the issue seemed to be that the mirror server was
unresponsive. I t
After discovering some regressions today we found what we think is a
package build issue in our CI environment which might be the cause of
our issues:
https://bugs.launchpad.net/tripleo/+bug/1595660
Specifically, there is a case where DLRN might not be giving an error
code if build failures occur
change too many things at once and break things. You need to be able to
> run some old things and some new, all at the same time. And in some cases
> different versions/config of
> the same service on different machines.
>
>
> Thoughts on how this may be made to work with puppet/h
On Mon, 2016-03-21 at 16:14 -0400, Zane Bitter wrote:
> As of the Liberty release, Magnum now supports provisioning Mesos
> clusters, so TripleO wouldn't have to maintain the installer for
> that
> either. (The choice of Mesos is somewhat unfortunate in our case,
> because Magnum's Kubernetes
On Wed, 2016-03-23 at 19:11 +, Fox, Kevin M wrote:
> If heat convergence worked (Is that a thing yet?), it could
> potentially be used instead of a COE like kubernetes.
>
> The thing ansible buys us today would be upgradeability. Ansible is
> config management, but its also a workflow like too
On Mon, 2016-04-04 at 02:31 +, Steven Dake (stdake) wrote:
>
> On 4/3/16, 6:38 PM, "Dan Prince" wrote:
>
> >
> >
> >
> >
> > On Mon, 2016-03-21 at 16:14 -0400, Zane Bitter wrote:
> > >
> > > As of the Liberty release
erately from
puppet-swift for example)
Given this why would I need say two different version of puppet-swift
in my Agent container (which is used to generate configs) for a given
upgrade?
Dan
>
> Thanks,
> Kevin
> From: Dan Prince [dpri...@redhat.com]
> Sent: Sunday, April 03, 2
On Sat, 2016-04-02 at 17:28 -0400, Adam Young wrote:
> I finally have enough understanding of what is going on with Tripleo
> to
> reasonably discuss how to implement solutions for some of the main
> security needs of a deployment.
>
>
> FreeIPA is an identity management solution that can provi
On Tue, 2016-04-05 at 19:19 -0600, Rich Megginson wrote:
> On 04/05/2016 07:06 PM, Dan Prince wrote:
> >
> > On Sat, 2016-04-02 at 17:28 -0400, Adam Young wrote:
> > >
> > > I finally have enough understanding of what is going on with
> > > Triple
1 - 100 of 289 matches
Mail list logo
