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
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
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
Hello everyone,
A new release candidate for congress-dashboard for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/congress-dashboard/
Unless release-critical issues are found that warrant a release
candidate respin, this can
Hello everyone,
A new release candidate for congress for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/congress/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be forma
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.
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/
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
Hello everyone,
A new release candidate for congress for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/congress/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be form
Hello everyone,
A new release candidate for congress-dashboard for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/congress-dashboard/
Unless release-critical issues are found that warrant a release
candidate respin, this ca
Hello everyone,
A new release candidate for congress for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/congress/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be form
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
__
From: Eric K
Date: Tuesday, 9 January 2018 at 0:43
Hi Ifat,
From: "Afek, Ifat (Nokia - IL/Kfar Sava)"
mailto:ifat.a...@nokia.com>>
Date: Sunday, January 7, 2018 at 4:00 AM
Hi Eric,
I have two questions:
1. An alarm is usually raised on a resource, and in Vitrage we can send
you the
From: Tim Hinrichs
Date: Monday, January 8, 2018 at 7:31 AM
To: Eric Kao
Cc: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [congress] generic push driver
> It's probably worth considering PATCH instead of PUT for updating the table.
Ah right of course. PATCH
Hi Ifat,
From: "Afek, Ifat (Nokia - IL/Kfar Sava)"
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Sunday, January 7, 2018 at 4:00 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstac
It's probably worth considering PATCH instead of PUT for updating the table.
http://restcookbook.com/HTTP%20Methods/patch/
You could also think about using JSON-patch to describe the requested
update. It provides fine-grained update semantics:
https://tools.ietf.org/html/rfc6902
Tim
On Fri, J
(not for usage questions)"
Subject: [openstack-dev] [congress] generic push driver
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 propos
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,
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
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
Hi all,
As previously discussed over, we'll move the weekly Congress team meeting
to the new time of Fridays 02:30 UTC, with the first new meeting on
November 3rd. Same channel #openstack-meeting.
Just to reiterate, there will be no meeting on November 2nd 00:00 (old
meeting time).
As always, col
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
Adding [Congress] to the subject line for proper filtering...
Congress lets you execute most of the Nova client API calls. You use the
same arguments you would use for the Nova client. Here are the docs for
the live-migration API: scroll down to live-migrate.
https://docs.openstack.org/python-n
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
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
Hello everyone,
A new release candidate for congress for the end of the Pike
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/congress/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formal
Hello everyone,
A new release candidate for congress-dashboard for the end of the Pike
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/congress-dashboard/
Unless release-critical issues are found that warrant a release
candidate respin, this cand
Hi Valentin,
Sounds like an interesting use case. Typically we've focused on
information available through APIs. In this case the information would be
pulled off the disks of the machines running each service.
Here's the info for our weekly meeting. If you can make that, it's a good
place to s
Hi Eric,
Here is the blueprint :
https://blueprints.launchpad.net/congress/+spec/configuration-files-validation
As Pierre Crégut presented it in his reply to Clint, the use of
Congress
we suggested and config management systems complement one anoth
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
This is the classical divide between workflows and business rule engines
and we
think that both are useful. While the first are invaluable to make a
system reach
a correct state, the second describe in a more declarative way what a
correct
state is and can also be used as a global model of the s
This is the classical divide between workflows and business rule
engines and we think that both are useful. While the first are
invaluable to make a system reach a correct state, the second
describe in a more declarative way what a correct state is and can
also be
Excerpts from valentin.matton's message of 2017-07-04 15:29:25 +0200:
> We would like to use congress to check the consistency of the
> configuration files used by the various Openstack services on different
> nodes.
>
> Although installers do a great job for ensuring that the initial
> definit
We would like to use congress to check the consistency of the
configuration files used by the various Openstack services on different
nodes.
Although installers do a great job for ensuring that the initial
definition of those files are correct, it may be necessary to tweak
those files on runn
This error happens happens when the translator thinks there's an
object/dictionary when in actuality there's just a string. I don't know of
a good way to know where in the translator the problem is, other than
simplifying the input and the translator and rerunning (which you're
already doing).
Ti
usage questions)"
Date: Thursday, June 15, 2017 at 12:51 AM
To:
Subject: [openstack-dev] [Openstack-dev] [Congress] [Designate]
> Hi everyone,
> I wrote a congress datasource driver and its unit test for designate, but i
> got the following errors in the method test_update_fr
Hi everyone,
I wrote a congress datasource driver and its unit test for designate, but i
got the following errors in the method test_update_from_datasource. It's
something wrong in the translation.
Here is the traceback:
File "congress/tests/datasources/test_designate_driver.py", line 34, in
setU
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.
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
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
Carmine
-- Messaggio inoltrato --
Da: "Carmine Annunziata"
Data: 16 apr 2017 18:21
Oggetto: Tempest test (congress-datasources)
A: "Tim Hinrichs"
Cc: "Eric K"
Hi guys,
I'm trying to write the tempest test for magnum in the
scenario/congress_datasources dir. Which test_driver may
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 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?
Hello everyone,
A new release candidate for congress for the end of the Ocata
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/congress/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be forma
Hi Eric,
Both looks interesting, so I'm ok for either. If I need to pick one of
them, I prefer the Aquarium.
Masahito
On 2017/02/16 8:06, Eric K wrote:
Hi all,
Here are some options (thinrichs originally suggested) we could consider
for a Friday daytime outing for those interested.
Anyone
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
Hi all,
At the last IRC I volunteered to pick out a couple of group activities for
the upcoming PTG. First cut is below. I could imagine dinner, an outing,
or both.
Restaurants
---
Two options jumped out at me. If neither of these seems good I can keep
looking.
1. Desta Ethiop
Excerpts from Jay Pipes's message of 2017-02-06 16:23:51 -0500:
> On 02/06/2017 04:09 PM, Aimee Ukasick wrote:
> > Thanks, Clint, for your quick response. Questions inline.
> > On 02/06/2017 01:32 PM, Clint Byrum wrote:
> >> Excerpts from Aimee Ukasick's message of 2017-02-06 12:57:28 -0600:
> >>>
On 02/06/2017 04:09 PM, Aimee Ukasick wrote:
Thanks, Clint, for your quick response. Questions inline.
On 02/06/2017 01:32 PM, Clint Byrum wrote:
Excerpts from Aimee Ukasick's message of 2017-02-06 12:57:28 -0600:
Hi everyone - from the Congress standalone installation guide
(http://docs.openst
Thanks, Clint, for your quick response. Questions inline.
On 02/06/2017 01:32 PM, Clint Byrum wrote:
> Excerpts from Aimee Ukasick's message of 2017-02-06 12:57:28 -0600:
>> Hi everyone - from the Congress standalone installation guide
>> (http://docs.openstack.org/developer/congress/README.html#in
Excerpts from Aimee Ukasick's message of 2017-02-06 12:57:28 -0600:
> Hi everyone - from the Congress standalone installation guide
> (http://docs.openstack.org/developer/congress/README.html#installing-congress):
>
> ---
> To use RabbitMQ with Congress, set the transport_url in the “From
> oslo.m
Hi everyone - from the Congress standalone installation guide
(http://docs.openstack.org/developer/congress/README.html#installing-congress):
---
To use RabbitMQ with Congress, set the transport_url in the “From
oslo.messaging” section according to your setup:
transport_url = rabbit://$RABBIT_USER
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
Hello everyone,
A new release candidate for congress for the end of the Ocata
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/congress/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be forma
lopment Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [congress] ocata client causes feature
regression with pre-ocata server
> At some point the client sometimes made multiple API calls. I think (c) seems
> right too.
>
> Tim
>
> On Sun, Jan 2
At some point the client sometimes made multiple API calls. I think (c)
seems right too.
Tim
On Sun, Jan 22, 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
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 with
> older versions of congress. Specifically, new client with pre-Ocata
> congress cannot refer to datasource b
Hi Tim,
I thought something like that would work. But actually python-congressclient
is not a listed requirement of congress server, no vice versa. Which is
correct in the sense that installing and running one does not require
installing the other on the same machine.
From: Tim Hinrichs
Date: S
How about we go into the preocata server and change requirements.txt to
ensure 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 rele
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
Hi Serg,
That¹s awesome news. Thanks all for the great work!
Please do let us know how the Congress team can be helpful.
On 1/16/17, 11:33 AM, "Serg Melikyan" wrote:
>I'd like to introduce you fuel plugin for installing and configuring
>Congress for Fuel [0].
>
>This plugin was developed by Fu
On Thu, Jan 12, 2017 at 4:31 PM, Eric K wrote:
> On a freshly stacked devstack (Jan 12), attempting to access
> `cfg.CONF.keystone_authtoken.project_domain_name` gave the
> error: NoSuchOptError: no such option project_domain_name in group
> [keystone_authtoken]
>
> I’m a little confused because
Hi Serg,
This is great news! On behalf of the OPNFV Doctor team, thank you Fuel@Opnfv
team for this effort!
We will certainly test it out as soon as possible, and we'll provide
feedback.
Cheers,
Carlos
On Mon, Jan 16, 2017 at 8:33 PM, Serg Melikyan
wrote:
> I'd like to introduce you fuel plug
I'd like to introduce you fuel plugin for installing and configuring
Congress for Fuel [0].
This plugin was developed by Fuel@Opnfv [1] Community in order to be
included to the next release of the Fuel@Opnfv - Danube. We believe
that this plugin might be helpful not only for us but also for genera
Excerpts from Eric K's message of 2017-01-12 14:31:58 -0800:
> On a freshly stacked devstack (Jan 12), attempting to access
> `cfg.CONF.keystone_authtoken.project_domain_name` gave the error:
> NoSuchOptError: no such option project_domain_name in group
> [keystone_authtoken]
>
> I¹m a little conf
Did you search keyword in http://codesearch.openstack.org/. Hope that will
help you.
2017-01-13 6:31 GMT+08:00 Eric K :
> On a freshly stacked devstack (Jan 12), attempting to access
> `cfg.CONF.keystone_authtoken.project_domain_name` gave the
> error: NoSuchOptError: no such option project_doma
On a freshly stacked devstack (Jan 12), attempting to access
`cfg.CONF.keystone_authtoken.project_domain_name` gave the error:
NoSuchOptError: no such option project_domain_name in group
[keystone_authtoken]
I¹m a little confused because it¹s part of the [keystone_authtoken] config
section generat
The reason we have devstack instructions under Users is because they are so
easy and make it simple to test drive Congress. To test drive you need at
least a couple of services besides Congress, which makes devstack a good
fit.
But maybe users don't care about install at all. Operators care about
Hi all. While looking at the installation docs in preparation for
scripting and testing Congress installation
(https://bugs.launchpad.net/congress/+bug/1651928), I noticed there are
installation instructions in two places: 1) For Users: Congress
Introduction and Installation; and 2) For Operators:
No congress team meeting on December 29, 2016. Regular meeting resumes on
January 5, 2016.
Happy holidays all!
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.opensta
On 2016-12-19 17:33:10 -0800 (-0800), Eric K wrote:
> The congress {pipeline}-congress-dsvm-api-{node}{suffix} check/gate job
> seems to timeout around the 60 minute mark even though the project config
> appears to set it for 70min. Any hints as to why? Are there two different
> measures of time? T
The congress {pipeline}-congress-dsvm-api-{node}{suffix} check/gate job
seems to timeout around the 60 minute mark even though the project config
appears to set it for 70min. Any hints as to why? Are there two different
measures of time? Thanks so much!
https://github.com/openstack-infra/project-co
That job is non-voting, which since you're adding a new datasource, you can
ignore. Nothing to do now but wait for people to give you reviews.
Tim
On Mon, Dec 12, 2016 at 1:12 PM Ruben
wrote:
> Hi Tim,
> thanks a lot for your help.
> I've seen that there is a failure for "gate-congress-pe-repl
Hi Tim,
thanks a lot for your help.
I've seen that there is a failure for "gate-congress-pe-replicated-nv".
It's strange because I didn't have failure before.
So, what should I do now?
Ruben
- Messaggio originale -
Da: "Tim Hinrichs"
A: "Ruben"
Cc: openstack-dev@lists.openstack.org, "ti
Hi Ruben,
Looked like there were still multiple changes, so I squashed them into 1
and fixed up the requirements.txt file. (You should only need to add the
python-magnumclient to the requirements.txt file.) I also abandoned one
that was incorporated into the one 1 fix. Here it is. Now the comm
Hi Tim,
sorry for the late, but I've had a busy week.
Anyway, I've tried to add the magnum_driver to review into a single commit.
I don't know if I have been able..
Ruben
- Messaggio originale -
Da: "Tim Hinrichs"
A: "Ruben"
Cc: openstack-dev@lists.openstack.org, "timothy l hinrichs"
Thanks Anusha!
I agree that moving the congress_dashboard code to its own repo is a
good idea.
As a workaround, it was suggested to me that I could clone the congress
repo on the same server as horizon, copy the 3 files to the horizon
directory, and then delete the congress code that we don't nee
Hi Tim, Aimee,
Yes, ideally only congress_dashboard is required on the same server as
horizon for horizon to discover the plugin, but right now
congress_dashboard is also part of congress repo, so congress needs to be
installed on the same server.
I'm thinking for a while to move the repo to sepa
I wouldn't expect Congress needs to be on the same server as Horizon.
Anusha, do you know for sure?
Tim
On Thu, Dec 8, 2016 at 1:20 PM Aimee Ukasick
wrote:
> All - we are looking into deploying Congress in its own container,
> separate from the container that OpenStack is in. I know which Cong
All - we are looking into deploying Congress in its own container,
separate from the container that OpenStack is in. I know which Congress
dashboard files need to be copied to Horizon, and from what I can tell,
it looks like Congress and Horizon must be running on the same server
for the Congress d
Hi Ruben,
What you're doing is correct. The downside is that it creates a new commit
for every change you make, and all of those commits show up on gerrit. In
OpenStack (and other projects I've seen that use Gerrit for code reviews)
you squash those commits into 1 change so that it's easier for
Hi Tim,
what should I do to squash all the commits into a single one?
To add the code to review I made:
git add
git commit
git review
Isn't it correct?
Ruben
- Messaggio originale -
Da: "Tim Hinrichs"
A: "Ruben"
Cc: openstack-dev@lists.openstack.org, "timothy l hinrichs"
Inviato:
Hi Ruben,
I left a comment on one of the changes; after you take care of that I'll
take a closer look at the code. Let me know if you have questions.
Tim
On Tue, Nov 29, 2016 at 4:06 AM Ruben
wrote:
> Hi Tim,
> I've added the code of magnum_driver and its unit test to review.
> It seems every
Hi Tim,
I've added the code of magnum_driver and its unit test to review.
It seems everything works.
Ruben
- Original Message -
From: "Tim Hinrichs"
To: "Ruben"
Cc: openstack-dev@lists.openstack.org, "timothy l hinrichs"
Sent: Saturday, November 26, 2016 12:48:12 AM
Subject: Re: [Cong
Definitely push that code up into Gerrit so we can all take a look. Data
like pods and containers is probably the most valuable data from Magnum, so
I'd definitely recommend adding that. But push the code you have to Gerrit
first. (As long as you leave the ChangeId the same each time you push to
1 - 100 of 582 matches
Mail list logo
