Hi
I think a "deep dive" about containers in TripleO and some helpful
documentation would help a lot for valuable reviews of these container
patches. The knowledge gap that's accumulated here is pretty big.
Thanks
On Jun 5, 2017 03:39, "Dan Prince" wrote:
> Hi,
>
> Any help reviewing the follow
Hi Kuryrs,
Today Irena and I are attending the OpenStack Israel day and won't be
able to chair the meeting. We can catch up tomorrow on IRC during the
day.
Toni
__
OpenStack Development Mailing List (not for usage questions)
On Mon, Jun 5, 2017 at 8:59 AM, Sagi Shnaidman wrote:
> Hi
> I think a "deep dive" about containers in TripleO and some helpful
> documentation would help a lot for valuable reviews of these container
> patches. The knowledge gap that's accumulated here is pretty big.
This is not the first time I
On 05/06/17 10:29 +0200, Emilien Macchi wrote:
On Mon, Jun 5, 2017 at 8:59 AM, Sagi Shnaidman wrote:
Hi
I think a "deep dive" about containers in TripleO and some helpful
documentation would help a lot for valuable reviews of these container
patches. The knowledge gap that's accumulated here is
On Mon, Jun 5, 2017 at 2:34 AM, Dan Prince wrote:
> Hi,
>
> Any help reviewing the following patches for the overcloud
> containerization effort in TripleO would be appreciated:
>
> https://etherpad.openstack.org/p/tripleo-containers-todo
Nice summary, it really helps. Thanks.
Maybe could we prio
On 06/05/2017 10:55 AM, Flavio Percoco wrote:
On 05/06/17 10:29 +0200, Emilien Macchi wrote:
On Mon, Jun 5, 2017 at 8:59 AM, Sagi Shnaidman wrote:
Hi
I think a "deep dive" about containers in TripleO and some helpful
documentation would help a lot for valuable reviews of these container
patche
Hi all:
The repository of Fuxi-golang has been set up! We can submit bugs and
bps[1] through launchpad now.
To Antoni Segura, this patch[2] will need your +1 to be merged. So could
you please take a look at it. Thanks very much!
[1] https://launchpad.net/fuxi-golang
[2] https://
Thanks!
It seems like https://review.openstack.org/440882 is the problem. Now that we
have resolved the issues we should return this.
I have proposed patches to return these.
Thanks
Gary
On 6/4/17, 4:15 PM, "Jeremy Stanley" wrote:
On 2017-06-04 11:35:16 + (+), Gary Kotton wrote:
On 06/05/2017 01:06 AM, Takashi Natsume wrote:
> Hi, Nova developers.
>
> The version of sphinx has been capped (*1)
> in order to fix an issue (*2, *3) with resolving citations in nova-specs.
>
> But IMO, it is better to fix citations in specs (*4)
> rather than capping the sphinx version.
Than
Thanks Kevin. I added it to get_router_ids [1], which is called when
full_sync flag is set(i.e when agent is AGENT_REVIVED, updated or started)
and not in get_routers/sync_routers.
[1] https://review.openstack.org/#/c/470905/
On Sat, May 27, 2017 at 2:54 AM, Kevin Benton wrote:
> I recommend a
On 06/01/2017 06:09 AM, Chris Dent wrote:
> It's clear from this thread and other conversations that the
> management of tempest plugins is creating a multiplicity of issues
> and confusions:
>
> * Some projects are required to use plugins and some are not. This
> creates classes of projects.
I had not realized this until doing the research at the Summit about
request_id middleware in the base iaas services, that glance did
something quite different than the others (and has always allowed the
request_id to be set).
I'd actually like to modify that behavior to setting the new
global_req
On 5.6.2017 08:59, Sagi Shnaidman wrote:
Hi
I think a "deep dive" about containers in TripleO and some helpful
documentation would help a lot for valuable reviews of these container
patches. The knowledge gap that's accumulated here is pretty big.
As per last week's discussion [1], i hope this
On 05/06/17 09:43, Sean Dague wrote:
On 06/01/2017 06:09 AM, Chris Dent wrote:
It's clear from this thread and other conversations that the
management of tempest plugins is creating a multiplicity of issues
and confusions:
* Some projects are required to use plugins and some are not. This
c
Hello,
Since we're working hard on providing pipeline for docker publishing,
that will require heavy gating of container images to be published. We
also would like to publish stable/ocata images to enable release
upgrade gates from O to P.
My question is, is it ok to backport gate logic to stable
While investigating a bug report against cloud-init ("why don't you put
nameservers in interface configuration files?"). I discovered that Nova
munges the information received from Neutron to take the network-scoped
nameserver entries and move them all into a global "services" section.
It turns ou
Hi,
We are glad to present this week's priorities and subteam report for Ironic. As
usual, this is pulled directly from the Ironic whiteboard[0] and formatted.
This Week's Priorities (as of the weekly ironic meeting)
1. booting from volume
Hi all,
According to the patch currently up at [0], the meeting time that works for
most everyone who currently attends has been changed to 13:00 UTC (still the
same day on Tuesday). If this meeting time is objectionable to anyone, feel
free to review [0].
Because [0] has yet to be merged and
We had a very lively discussion this morning during the Scheduler subteam
meeting, which was continued in a Google hangout. The subject was how to handle
claiming resources when the Resource Provider is not "simple". By "simple", I
mean a compute node that provides all of the resources itself, a
On 06/05/2017 09:42 AM, Michał Jastrzębski wrote:
My question is, is it ok to backport gate logic to stable branch?
Regular code doesn't change so it might not be considered a feature
backport (users won't see a thing).
Yes, that's allowed. Stable maintainers are concerned about
destabilizing
On Mon, 2017-06-05 at 16:11 +0200, Jiří Stránský wrote:
> On 5.6.2017 08:59, Sagi Shnaidman wrote:
> > Hi
> > I think a "deep dive" about containers in TripleO and some helpful
> > documentation would help a lot for valuable reviews of these
> > container
> > patches. The knowledge gap that's accum
Hello,
I am working on a patch [1] to list the deprecated parameters of the
current plan. It depends on a heat patch[2] which provides
parameter_group support for nested stacks. The change is to add a new
workflow to analyze the plan templates and find out the list of
deprecated parameters, identi
Hi,
Pike-2 milestone is at the end of this week, and although we are not working by
the milestones model (we are working by a cycle-with-intermediary model) we
need to have the first Vitrage Pike release by the end of this week.
I would like to release vitrage, python-vitrageclient and vitrage-
Hi,
In order to add a release notes file to Vitrage, please perform the following:
$ cd /opt/stack/vitrage
$ reno new my_new_feature
Created new notes file in
releasenotes/notes/my_new_feature-5e88573b6d99abbb.yaml
Edit the file, remove everything that you don’t need, and write 3-4 lines of
des
24 matches
Mail list logo
