Sorry for the rather late announcement. We're moving this week's
Congress team meeting from Friday 4AM UTC to Thursday 10AM UTC in
order to accommodate the summit local time zone. Thanks!
Eric
__
OpenStack Development Mailing
u need more info on this.
>
> [1] https://docs.openstack.org/masakari/latest/sample_config.html
>
> --- Regards,
> Sampath
>
>
>
> On Sun, Oct 7, 2018 at 8:55 AM Eric K wrote:
>> Hi all, I'm working on a potential integration between masakari and
>>
Hi all, I'm working on a potential integration between masakari and
congress. But I am stuck on some basic usage questions I could not
answer in my search of docs and demos. Any clarification or references
would be much appreciated!
1. What does a host refer to in masakari API? Here's the explanat
Hi all, the Congress team meeting is transitioning to Fridays 4AM UTC
on even weeks (starting 10/5). During this week's transition, we'll
have a special transition meeting today Friday at 4AM UTC (instead of
previous 2:30AM UTC) even though it's an odd week.
Thank you!
Eric Kao
_
Hi all,
Following discussions in IRC meetings, here is a proposed new meeting
time for Congress project:
On even weeks, Friday UTC 4AM (from the current UTC 2:30AM)
The new time would make it easier for India while still good for Asia
Pacific. The time continues to be bad for Europe and Eastern A
Let's resume on 9/21. Thanks!
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/ope
Ha. Turned out to be a simple mistake in hyphens vs underscores.
On Tue, Aug 28, 2018 at 3:06 PM Eric K wrote:
>
> Any thoughts on what could be going wrong that the tempest tests still
> see the default conf values rather than those set here? Thanks lots!
>
> Here is the de
/devstacklog.txt.gz#_2018-08-28_21_23_15_934
On Wed, Aug 22, 2018 at 9:12 AM Eric K wrote:
>
> Hi all,
>
> I have added feature flags for the congress tempest plugin [1] and set
> them in the devstack plugin [2], but the flags seem to be ignored. The
> tests are skipped [3] according to the
Hi all,
I have added feature flags for the congress tempest plugin [1] and set
them in the devstack plugin [2], but the flags seem to be ignored. The
tests are skipped [3] according to the default False flag rather than
run according to the True flag set in devstack plugin. Any hints on
what may b
Hi all,
I¹m not going to be able to make the meeting this week.
Let¹s resume next week =)
I'm still available by email.
Cheers!
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-re
On Tue, Aug 14, 2018 at 9:34 PM, Ghanshyam Mann wrote:
> On Wed, 15 Aug 2018 09:37:18 +0900 Eric K
> wrote
> > I'm adding jobs [1] to the tempest plugin to run tests against
> > congress stable/queens. The job output seems to show stable/queens
> > g
On Tue, Aug 14, 2018 at 8:59 PM, Ghanshyam Mann wrote:
> On Wed, 15 Aug 2018 06:40:57 +0900 Eric K
> wrote
> > Anyone have an example handy of a tempest test conditioning on service
> > release version (because new features not available in past versions)?
>
I'm adding jobs [1] to the tempest plugin to run tests against
congress stable/queens. The job output seems to show stable/queens
getting checked out [2], but I know the test is *not* run against
queens because it's using features not available in queens. The
expected result is for several tests to
Anyone have an example handy of a tempest test conditioning on service
release version (because new features not available in past versions)?
Seems like it could get pretty messy and haphazard, so I'm curious to
see best practices. Thanks lots!
Eric Kao
___
From: Rabi Mishra
Date: Monday, August 13, 2018 at 10:10 PM
> On Tue, Aug 14, 2018 at 4:40 AM, Eric K wrote:
>> It appears that gabbi<1.42.1 is causing on error with heat tempest
>> plugin in congress stable/queens dsvm job [1][2][3].
> I wonder why you're enabling
On 8/13/18, 11:03 PM, "Tony Breeds" wrote:
>On Mon, Aug 13, 2018 at 04:10:30PM -0700, Eric K wrote:
>> It appears that gabbi<1.42.1 is causing on error with heat tempest
>> plugin in congress stable/queens dsvm job [1][2][3]. The issue was
>> addressed i
It appears that gabbi<1.42.1 is causing on error with heat tempest
plugin in congress stable/queens dsvm job [1][2][3]. The issue was
addressed in heat tempest plugin [4], but the problem remains for
stable/queens jobs because the queens upper-constraint is still at
1.40.0 [5].
Any suggestions on
Requesting the raised minimun just for openstack/congress.
https://review.openstack.org/#/c/590021/
No re-release required; it'll just take effect in RC1.
On 8/8/18, 2:06 PM, "Matthew Thode" wrote:
>On 18-08-08 13:14:08, Eric K wrote:
>> python-monascaclient 1.12.0 pa
Requesting the raised minimun just for openstack/congress.
https://review.openstack.org/#/c/589995/
No re-release required; it'll just take effect in RC1.
On 8/8/18, 2:07 PM, "Matthew Thode" wrote:
>On 18-08-08 13:20:47, Eric K wrote:
>> Lower versions of sphinx seems
Lower versions of sphinx seems to experience a problem where the
exclude_patterns option is not in effect. I'd like to bump the
docs/requirements to sphinx>=1.7.3 if it is not disruptive to
packaging. If it is disruptive to packaging we can leave it as is.
Thanks!
https://review.openstack.org/#/c
python-monascaclient 1.12.0 paired with osc-lib 1.11.0 seems to
experience a problem around Session.
python-monascaclient 1.12.1 fixes the issue [1]. So I'd like to bump
congress requirements to python-monascaclient>=1.12.1 if it is not
disruptive to packaging [2]. If it is disruptive, we can just
Hi all,
I’m not going to be able to make the meeting this week.
Let’s resume next week =)
I’m still available by email.
Thanks!
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ.
ld match the one
> coming from vitrage alarm list¹. The id¹ field is determined by the external
> monitor, so it might be different.
>
> Best Regards,
> Ifat
>
>
> -- Forwarded message -
> From: Eric K
> Date: Sat, 9 Jun 2018 at 01:40
> Sub
ces are aligned. I
> created a bug for it [2].
>
> [1]
> https://github.com/openstack/vitrage/blob/master/vitrage/datasources/transform
> er_base.py
>
> [2] https://bugs.launchpad.net/vitrage/+bug/1776181
> Best regards,
> Ifat
>
>
> -- Forwarded m
Hi I'm building integration with Vitrage webhook and looking for some
clarification on what ID to use for matching a webhook notification to
the specific alarm from the alarm list. In the sample alarm list
response, there is an 'id' field and a 'vitrage_id' field [1], where
as in the sample webhook
Hi I'm building integration with Vitrage webhook and looking for some
clarification on the timestamp precision to expect.
In the sample webhook payload found in doc the resource and the alarm
shows different time stamp precisions:
https://docs.openstack.org/vitrage/latest/contributor/notifier-webh
Thank you, Zane for the discussion.
Point taken about sending webhook notifications.
Primarily I want Congress to consume webhook notifications from the
openstack services which already send them (monasca, vitrage, etc.). Most
of them do not currently support sending appropriate keystone tokens w
To clarify, one of the reasons I'd like to accept webhook notifications
authenticated with keystone tokens is that I don't want the access to
expire, but of course it's poor practice to use a signed URL that never
expires.
Eric
On 5/8/18, 12:29 PM, "Eric K" wrote:
>
e I'm guessing the main reason
it hasn't been done that way is because it does not generalize to most
other services that don't connect to keystone?
On 5/6/18, 9:30 AM, "Thomas Herve" wrote:
>On Sat, May 5, 2018 at 1:53 AM, Eric K wrote:
>> Thanks a lot Witold an
omas Herve" wrote:
>On Thu, May 3, 2018 at 9:49 PM, Eric K wrote:
>> Question to the projects which send or consume webhook notifications
>> (telemetry, monasca, senlin, vitrage, etc.), what are your
>> supported/preferred authentication mechanisms? Bearer token (e.g.
>&
Question to the projects which send or consume webhook notifications
(telemetry, monasca, senlin, vitrage, etc.), what are your
supported/preferred authentication mechanisms? Bearer token (e.g.
Keystone)? Signing?
Any pointers to past discussions on the topic? My interest here is having
Congress c
Got it thanks a lot, Doug and Matt!
On 4/19/18, 11:34 AM, "Matt Riedemann" wrote:
>On 4/19/2018 1:15 PM, Doug Hellmann wrote:
>> Second, releasing early and often gives us more time to fix issues,
>> so we aren't rushing around at deadline trying to solve a problem
>> while the gate is full of o
Specifically, for client library using the cycle-with-intermediary release
model.
On 4/19/18, 10:52 AM, "Eric K" wrote:
>Thank you, Doug. Question: do we need to do a client library release prior
>to R-3? The practice seems to change from cycle to cycle.
>
>On 4/19/18, 6
Thank you, Doug. Question: do we need to do a client library release prior
to R-3? The practice seems to change from cycle to cycle.
On 4/19/18, 6:15 AM, "Doug Hellmann" wrote:
>Today is the deadline for proposing a release for the Rocky-1 milestone.
>Please don't forget to include your librarie
,
>
>Sorry for late response, i kept this mail unread but forgot to
>respond. reply inline.
>
>On Fri, Mar 16, 2018 at 8:08 PM, Dougal Matthews
>wrote:
>>
>>
>> On 13 March 2018 at 18:51, Eric K wrote:
>>>
>>> Hi Mistral folks and others,
>>
Here's an updated backlog following Rocky discussions.
https://etherpad.openstack.org/p/congress-task-priority
Please feel free to comment and suggest additions/deletions and changes in
priority.
__
OpenStack Develo
IRC weekly meeting resumes on 3/30.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/
Hi Mistral folks and others,
I'm working on Congress tempest tests [1] for integration with Mistral. In
the tests, we use a Mistral service client to call Mistral APIs and
compare results against those obtained by Mistral driver for Congress.
Regarding the service client, Congress can either impo
Cancelled for PTG
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
e problems are solved :)
>
>What are your plans around integration with Monasca? Please let us know
>if you have related feature requests.
>
>Cheers
>Witek
>
>
>> -Original Message-
>> From: Eric K [mailto:ekcs.openst...@gmail.com]
>> Sent: Die
Hi all,
In lieu of planning sessions at the PTG, let's have asynchronous
brainstorming and a sync-up telecon.
(I will still be available at the PTG for discussions).
If you're interested, please:
1. Jot down your thoughts and ideas (problems, features, use cases, etc.)
in this planning/brainstorm
Oops. Nevermind. Looks like it's working now.
On 2/12/18, 5:00 PM, "Eric K" wrote:
>Hi Monasca folks,
>I'm trying to configure monasca in congress gate [1] and modeled it after
>this monasca playbook [2]. But I get:
>rsync: change_dir "/home/zuul/src/*/opens
Hi Monasca folks,
I'm trying to configure monasca in congress gate [1] and modeled it after
this monasca playbook [2]. But I get:
rsync: change_dir "/home/zuul/src/*/openstack/monasca-common" failed: No
such file or directory (2)
http://logs.openstack.org/22/530522/1/check/congress-devstack-api-my
Looking to add tenacity to congress requirements because it's needed by a
forthcoming bug fix. No change to requirements repo. Does this need an
exception? Thanks a lot!
https://review.openstack.org/#/c/538369/
Eric Kao
__
Hi all,
I'm having some trouble getting congress-dashboard to receive requirements
updates from global-requirements.
The check-requirements job seems to be configured, but does NOT seem to be
running:
http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul.d/pr
ojects.yaml#n4246
T
On 1/7/18, 9:27 PM, "Ghanshyam Mann" wrote:
>On Sat, Jan 6, 2018 at 3:41 PM, Chandan kumar
>wrote:
>> Hello Eric,
>>
>> On Sat, Jan 6, 2018 at 4:46 AM, Eric K wrote:
>>> Seems that sometime between 1/2 and 1/3 this year,
>>> tempest.
e":"active",
"severity":1
}
},
{
"op":"add",
"path":"/",
"value":[
"1-2",
"name2",
"active",
2
]
},
{
"op":"remove"
uot;:"active", "severity":100}
Vs
Update the severity field of row with id "1-1" to severity 100.
Both could be supported, but the second one is more complex to support
efficiently.
Thanks!
Eric
>
> Thanks,
> Ifat
>
>
>
> From: Eric K
>
We've been discussing generic push drivers for Congress for quite a while.
Finally sketching out something concrete and looking for some preliminary
feedback. Below are sample interactions with a proposed generic push
driver. A generic push driver could be used to receive push updates from
vitrage,
Seems that sometime between 1/2 and 1/3 this year,
tempest.config.CONF.service_available.aodh_plugin as well as
..service_available.mistral became unavailable in congress dsvm check/gate
job. [1][2]
I've checked the changes that went in to congress, tempest, devstack,
devstack-gate, aodh, and mist
Hi all,
Just a heads up that there will be no Congress team meeting this week
12/29. We'll be back next year on 1/5!
-ekcs
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@l
t;and then this code:
>https://github.com/openstack/osc-lib/blob/master/osc_lib/clientmanager.py#
>L239
>
>
>On 09.12.2017 04:15, Eric K wrote:
>> Hi all,
>>
>> I'm working on some code [1] that attempts to retrieve a endpoint from
>>the
>> service_catalog, bu
Submitted this after merging the fix:
https://review.openstack.org/#/c/526834/
Is that the correct step? Thanks again!
On 12/8/17, 2:10 PM, "Sean McGinnis" wrote:
>On Fri, Dec 08, 2017 at 04:06:15PM -0600, Doug Hellmann wrote:
>> Excerpts from zuul's message of 2017-12-08 21:56:33 +:
>> > B
Hi all,
I'm working on some code [1] that attempts to retrieve a endpoint from the
service_catalog, but the service_catalog comes up None. Any suggestions on
what I need to do differently to get a working service_catalog? Thanks
very much!
Python 2.7.12 (default, Nov 20 2017, 18:23:56)
[GCC 5.4.0
Ah sorry about that, Doug. And thank you for the pointer, Sean. I'm on it.
On 12/8/17, 2:10 PM, "Sean McGinnis" wrote:
>On Fri, Dec 08, 2017 at 04:06:15PM -0600, Doug Hellmann wrote:
>> Excerpts from zuul's message of 2017-12-08 21:56:33 +:
>> > Build failed.
>> >
>> > - release-openstack-p
Hi all,
It's that time again to figure out whether we'd hold physical sessions at
the PTG (February 26-March 2nd at Croke Park in Dublin, Ireland).
If you're interested in participating, please respond to the following.
1. What do you prefer between physical sessions at the PTG and remote
virtual
lways, collaborative list of meeting topics is kept here:
https://etherpad.openstack.org/p/congress-meeting-topics
See you all!
-Eric Kao
On 10/19/17, 11:13 AM, "Eric K" wrote:
>Hi all,
>
>Here is a proposal (no actual change until further notice) to move the
>weekly
Hi all,
Here is a proposal (no actual change until further notice) to move the
weekly Congress team meeting from Thursdays 00:00 UTC to Fridays 02:30 UTC
in order to make the meeting time more bearable for India while still
being workable for East Asia and the Americas. The time remains very bad
f
Hi Houzhian,
Great the see people doing fault tolerance with Congress. That's how
Congress is used in by the OpNFV Doctor project
(https://wiki.opnfv.org/display/doctor)
I just tested the same rule on Pike release and it seems Congress delivered
the correct request to nova. Do you have the Congre
Continuing from the 10/5 IRC discussion on drivers conf, here I've laid
out some decision points and incomplete pros and cons.
If you're interested, please add relevant pros and cons as well as further
discussion on your thoughts and preferences on the decision points. Thanks!
https://etherpad.ope
Ah got it thanks a lot Sam!
On 10/2/17, 12:39 PM, "Sam Matzek" wrote:
>This is also one of several errors hitting the Trove gate. This
>review should workaround the issue for now.
>
>https://review.openstack.org/#/c/508344/3
>
>On Mon, Oct 2, 2017 at 1:44 PM,
Since the transition to zuul3, this error began and prevents the devstack
setup from finishing on Congress gate jobs. I've been working to diagnose
it but so far without success.
Any suggestions and tips much appreciated!
http://logs.openstack.org/58/493258/5/check/legacy-congress-dsvm-api-mysql/
Hi all,
Looking forward to catching up at our IRC meeting tomorrow after a
productive PTG!
It¹d be helpful to look at these items ahead of the meeting:
- A work-in-progress list of priorities for Queens we can discuss and
finish in our meeting.
https://etherpad.openstack.org/p/congress-task-prior
Hi all,
If you¹re looking to join the Congress discussions at the PTG, please
follow the URL to join the conferencing meeting.
URL: https://bluejeans.com/122291516
Meeting Id: 122291516
Phone Number: +1.408.740.7256
No sign-up necessary. Once you join the room, you will have the option to
To accommodate people at PTG
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/open
As far as I can tell, bumping min version to 1.7.0 would not be a problem
for Congress.
Eric Kao
On 8/3/17, 4:39 AM, "witold.be...@est.fujitsu.com"
wrote:
>Hello everyone,
>
>I would like to ask for the FFE for python-monascaclient version in
>global requirements.
>
>The current version in Pike
Thanks a lot Jeremy and Andreas for the reference and the added context!
On 8/3/17, 10:49 AM, "Jeremy Stanley" wrote:
>On 2017-08-03 08:15:36 +0200 (+0200), Andreas Jaeger wrote:
>[...]
>> "A patchset has to be approved to run tests in the gate pipeline. If the
>> patchset has failed in the gate
Hi all is there a command on review.openstack.org that triggers a redo of
gate jobs but not check jobs (already passed)?
`remerge` doesn¹t seem to do anything. Thanks!
__
OpenStack Development Mailing List (not for usage que
eremy Stanley" wrote:
>On 2017-07-27 20:37:49 -0700 (-0700), Eric K wrote:
>> A tempest test [1] launches additional instances of Congress using
>> subprocess.popen and tests the coordination between them and the
>>original
>> instance launched by devstack. The problem
Re: [openstack-dev] [tempest][infra][congress] subprocess launched
in tempest test lacks file permission
>
>
> On Fri, Jul 28, 2017 at 4:38 AM Eric K wrote:
>> A tempest test [1] launches additional instances of Congress using
>> subprocess.popen and tests the coordination
A tempest test [1] launches additional instances of Congress using
subprocess.popen and tests the coordination between them and the original
instance launched by devstack. The problem is, the new instances are
launched from the tempest test user rather than the user of the original
congress instanc
On 7/19/17, 1:11 PM, "Clark Boylan" wrote:
>On Tue, Jul 18, 2017, at 12:47 PM, Eric K wrote:
>> Hi all, looking for some hints/tips. Thanks so much in advance.
>>
>> My local python3 devstack setup [2] succeeds, but in check-job a
>> similarly
>>
Clark suggested that perhaps in install for python-congressclient was
going to python2 instead of python3. So I¹m investigating that.
Thanks again!
On 7/19/17, 11:19 AM, "Jeremy Stanley" wrote:
>On 2017-07-18 12:47:07 -0700 (-0700), Eric K wrote:
>> Hi all, looking for s
Hi all, looking for some hints/tips. Thanks so much in advance.
My local python3 devstack setup [2] succeeds, but in check-job a similarly
configured devstack setup [1] fails for not installing congress client.
./stack.sh:1439:check_libs_from_git
/opt/stack/new/devstack/inc/python:401:die
[ERROR]
Hi Valentin,
Very cool to hear about your use case and vision! It definitely sounds
like the kind of use case Congress is well-equipped to solve using a
flexible, declarative rule language.
I'd love to explore the use case further (and where it fits along side
config management systems as Clint m
Hi Carmine,
Yes, I¹d guess that the translator you defined attempted to go deeper than
the structure obtained by API. If you push the changes to
review.openstack.org you may get better feedback =)
Eric
From: Carmine Annunziata
Reply-To: "OpenStack Development Mailing List (not for usage quest
Here's a quick & rough mock-up I put up based on the discussions at Atlanta
PTG.
https://wireframepro.mockflow.com/view/congress-policy-monitor
Anyone can view and comment. To make changes, please sign-up and email me
to get access.
On 5/22/17, 8:54 PM, "gordon chung" wrote:
>
>
>On 22/05/17 05:48 PM, Eric K wrote:
>> If someone out there knows uWSGI and has a couple spare cycles to help
>> Congress project, we'd super appreciate it.
>>
>> The regular contributors to Congre
On 5/23/17, 5:37 AM, "Chris Dent" wrote:
>On Mon, 22 May 2017, Eric K wrote:
>
>> If someone out there knows uWSGI and has a couple spare cycles to help
>> Congress project, we'd super appreciate it.
>>
>> The regular contributors to Congress do
Hi all!
I have organized the tasks for policy library here:
https://bugs.launchpad.net/congress/+bugs?field.tag=policy-lib
Please take a look and feel free to pick up, comment, modify, etc.
The four non-GUI high importance items are essential for rolling out this
feature.
The high importance GUI
If someone out there knows uWSGI and has a couple spare cycles to help
Congress project, we'd super appreciate it.
The regular contributors to Congress don't have experience with uWSGI and
could definitely use some help getting started with this goal. Thanks a ton!
https://governance.openstack.or
Hi Congress folks,
As mentioned in previous meetings, we need to decide this week whether to have
work sessions at the next PTG (expected to be September 11-15, 2017 in Denver,
CO).
Please reply to me 1) whether you think we should have sessions at the PTG and
2) if we have sessions whether yo
Hi all,
Even though some of us are at the OS summit and may not make the meeting,
let¹s have a meeting anyway for those of us who can make it.
As usual, the collaborative list of topics are kept here:
https://etherpad.openstack.org/p/congress-meeting-topics
_
Hi all,
Proposed topics for the next congress irc meeting are tracked in this
etherpad: https://etherpad.openstack.org/p/congress-meeting-topics
Feel free to add additional topics and/or comment on existing ones. Thanks!
__
Op
Hi all,
Proposed topics for the next congress irc meeting are tracked in this
etherpad: https://etherpad.openstack.org/p/congress-meeting-topics
Feel free to add additional topics and/or comment on existing ones. Thanks!
_
Hi all,
Friendly reminder that for US folks the IRC meeting this week is one hour
³later² (5PM PST, 8PM EST) due DST.
Proposed topics for the next congress irc meeting are tracked in this
etherpad: https://etherpad.openstack.org/p/congress-meeting-topics
Feel free to add additional topics and/or
Hi all,
Proposed topics for the next congress irc meeting are tracked in this
etherpad: https://etherpad.openstack.org/p/congress-meeting-topics
Feel free to add additional topics and/or comment on existing ones. Thanks!
__
Hi all,
Based on our discussions at the PTG, I have set up some tasks for Pike.
https://bugs.launchpad.net/congress/+bugs?field.tag=pike-goal
Feel free to adjust them (text, priority, target, assignee, etc.) or suggest
changes as you see fit.
For those interested, a few of us at the PTG are going to the Georgia Aquarium
Friday (2/24) morning. All welcome!
Meet at Sheraton hotel lobby at 9:30AM.
Purchase your ticket in advance here for early bird pricing (valid for entering
before 11am):
https://estore.georgiaaquarium.org/webstore/sh
Hi all,
In the congress project, we¹re looking to replace the antlr3-based parser
with a better maintained alternative. I see that pyparsing and Parsley are
used in some projects, could anyone share their experience with them and
potentially other parsing libraries?
The intended use is to parse i
Hi Congress folks,
At the PTG, we¹ll be starting with an Ocata retrospective to look at what we
may want to do more/less/same to make our work easier and better going
forward.
Feel free to get a head-start by thinking about what you¹d like to see us do
more/less/same of and putting them down in t
Congress IRC meeting cancelled this week for the PTG. Meeting will resume
next week (Mar 2 UTC). Thanks!
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?
Hi all,
I¹d like to request an exception to release Congress RC2. I¹m really sorry
that we got bogged down by a tricky, critical bug that we didn¹t manage to
root cause and patch until the very last minute. I replied to Doug earlier
about it, but neglected to reply to the list.
Here¹s the release
Hi all,
Here are some options (thinrichs originally suggested) we could consider for
a Friday daytime outing for those interested.
Anyone interested?
Any other ideas?
Georgia Aquarium
- 1st or 2nd largest aquarium in the world.
- #1 on tripAdvisor
- $31.95+tax/adult (advanced online purchase)
ht
Hi all!
I've put down a rough proposed schedule for our PTG sessions in the
etherpad (https://etherpad.openstack.org/p/congress-ptg-pike) and also
copied below. Please feel free to think about and express how you like &
dislike the proposed schedule and we¹ll finalize it in the IRC meeting. In
any
Hi all!
In preparing for the PTG discussions, how about we do the following things
between now and the Congress PTG sessions?
Etherpad: https://etherpad.openstack.org/p/congress-ptg-pike
1. If you¹re interested in starting the discussion on an item, put [init:
your_name_or_nick] at the start of t
RC1 released. Great job everyone for getting our fixes in!
Let¹s continue testing and reporting bugs to make sure Ocata is a
rock-solid release!
On 2/2/17, 5:01 PM, "no-re...@openstack.org"
wrote:
>
>Hello everyone,
>
>A new release candidate for congress for the end of the Ocata
>cycle is avai
2, 2017 at 1:15 AM Monty Taylor wrote:
>> On 01/21/2017 04:07 AM, Eric K wrote:
>>> > Hi all,
>>> >
>>> > I was getting ready to request release of congress client, but I
>>> > remembered that the new client causes feature regression if used w
ure
> it only supports the older clients. Something like...
>
> Python-congressclient>2.3<2.5
>
> Or whatever the versions are.
>
> Tim
>
>
> On Fri, Jan 20, 2017 at 7:07 PM Eric K wrote:
>> Hi all,
>>
>> I was getting ready to request release
Hi all,
I was getting ready to request release of congress client, but I
remembered that the new client causes feature regression if used with
older versions of congress. Specifically, new client with pre-Ocata
congress cannot refer to datasource by name, something that could be done
with pre-Ocat
1 - 100 of 138 matches
Mail list logo
