On Fri, Nov 10, 2017 at 2:51 PM, John Dickinson wrote:
> What I heard from ops in the room is that they want (to start) one release a
> year who's branch isn't deleted after a year. What if that's exactly what we
> did? I propose that OpenStack only do one release a year instead of two. We
> still
Hi, Michael,
I tried to run to command, and I think the amphora can connect to the
member (10.0.1.3). The results are as follows.
ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
amphora-haproxy ping 10.0.1.3
sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05
I missed this session but the discussion strikes a chord as this is
something I've been saying on my user survey every 6 months.
On 11 November 2017 at 09:51, John Dickinson wrote:
> What I heard from ops in the room is that they want (to start) one release a
> year who's branch isn't deleted aft
On 7 Nov 2017, at 15:28, Erik McCormick wrote:
> Hello Ops folks,
>
> This morning at the Sydney Summit we had a very well attended and very
> productive session about how to go about keeping a selection of past
> releases available and maintained for a longer period of time (LTS).
>
> There was a
Not too much happened due to the summit, so this will be a short one.
=> The majority of last week's update [1] still applies, including the
call for reviews under "# Most Important".
[1]
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124233.html
=> cdent's spec for symmetric G
Hey,
the feature still exists. you may read about it more on
https://github.com/openstack/glance/blob/master/doc/source/user/signature.rst
,
https://specs.openstack.org/openstack/glance-specs/specs/liberty/image-signing-and-verification-support.html
for future references, please look/search at t
Greetings,
Infra asked the tripleo team to cut down on the logs we're producing
upstream. We are using a lot of space on their servers and also it's
taking too long to collect the logs themselves.
We need to compromise and be flexible here, so I'd like the tripleo-ci and
tripleo core to take ano
On Wed, Nov 8, 2017 at 5:10 PM, Wesley Hayutin wrote:
>
>
> On Wed, Nov 8, 2017 at 5:00 PM, Alex Schultz wrote:
>
>> On Tue, Nov 7, 2017 at 2:59 PM, Emilien Macchi
>> wrote:
>> > On Wed, Nov 8, 2017 at 3:30 AM, James Slagle
>> wrote:
>> >> On Sun, Nov 5, 2017 at 7:01 PM, Emilien Macchi
>> wro
The actual gateway address does not matter to Octavia/amphora. It
gets that value from DHCP or from neutron if a static address was
assigned from neutron.
My concern is that the subnet gateway 10.0.1.10 does not match the
gateway address DHCP gave us 10.0.1.1.
Technically, since the two addresses
On 11/10/2017 03:20 AM, Giulio Fidente wrote:
On 11/26/2015 03:17 PM, Jiří Stránský wrote:
On 26.11.2015 14:12, Jiří Stránský wrote:
[...]
It seems TripleO is hitting similar composability and sanity limits with
the top-down approach, and the number of parameters which can only be
fed via
Hi David,
Looking at your code it looks you are wrongly using insecure=True. I
think you should use insecure=True while creating heat client object,
in your code it's "heat". Something similar to below should work:-
from heatclient import client as heatclient
heat=heatclient.Client(api_version, *
On Thu, Nov 9, 2017 at 5:14 AM, Marios Andreou wrote:
> Hello fellow owls,
>
> I would like to nominate (and imo these are both long overdue already):
>
> Sofer Athlan Guyot (chem) and
>
> Mathieu Bultel (matbu)
>
> to tripleo-core. They have both made many many core contributions to the
> upgra
Thanks Zane,
I had a look at the events for the resource in question, and the only
change I can see in the resource properties before and after the "update"
is that the "flavor" has changed from a numerical ID ("0") to a string
("m1.small").
I haven't found any unintended side effects of the "upd
Dears,
Do you have any idea to work arround this problem by deactivating the check
of the certificate ?
I have this line in my code but the check is still processed. What do you
suggest ?
stack = heat.stacks.create(stack_name=stack_name,
template=nct_template, parameters={}, *insecure=True*)
20
On 10-11-17 09:25:14, Lee Yarwood wrote:
> On 01-11-17 18:50:23, Lee Yarwood wrote:
> > Hello all,
> >
> > I'm attempting save future contributors to the fast forward upgrades feature
> > some time by introducing a quickstart release config that deploys a Master
> > UC
> > and Newton OC:
> >
> >
On 11/10/17 10:20 AM, Giulio Fidente wrote:
On 11/26/2015 03:17 PM, Jiří Stránský wrote:
On 26.11.2015 14:12, Jiří Stránský wrote:
[...]
It seems TripleO is hitting similar composability and sanity limits with
the top-down approach, and the number of parameters which can only be
fed via para
On 01-11-17 18:50:23, Lee Yarwood wrote:
> Hello all,
>
> I'm attempting save future contributors to the fast forward upgrades feature
> some time by introducing a quickstart release config that deploys a Master UC
> and Newton OC:
>
> config: Provide a Master UC and Newton OC release config
> ht
Hi, Michael,
Thanks a lot for your reply.
I can make sure that there is no router or multiple dhcp services in my
environment.
As shown in my first mail, the haproxy in the amphora tries to find the
gateway ip 10.0.1.1 that does not exist in the environment.
ubuntu@amphora-a0621f0e-d27f-4f22-a4
On 11/26/2015 03:17 PM, Jiří Stránský wrote:
> On 26.11.2015 14:12, Jiří Stránský wrote:
[...]
>> It seems TripleO is hitting similar composability and sanity limits with
>> the top-down approach, and the number of parameters which can only be
>> fed via parameter_defaults is increasing. (The dis
On 11/07/2017 11:47 PM, Emilien Macchi wrote:
> On Wed, Nov 8, 2017 at 9:29 AM, Wesley Hayutin wrote:
>> Greetings,
>>
>> I'd like to propose we remove the upgrade jobs that are consistently failing
>> from the upstream infrastructure and instead focus our efforts in RDO
>> Software Factory.
>>
>>
20 matches
Mail list logo
