Yuriy,
It looks like this would automate a standard workflow that my group often uses:
multiple commits, create “delivery” branch, git merge --squash, git review.
That looks really useful.
Having it be repeatable is a bonus.
Per last bullet of the implementation, I would not require not modif
Hello stackers, TC, Neutron contributors,
At the Nova mid-cycle meetup last week in Oregon, during the discussion
about the future of nova-network, the topic of nova-network -> Neutron
migration came up.
For some reason, I had been clueless about the details of one of the
items in the gap an
Isn't that what admin_state_up is for?
But yes we do need a deeper discussion on this and many other things.
On Tue, 2014-08-05 at 15:42 +, Eichberger, German wrote:
> There was also talk about a third administrative status like ON/OFF...
>
> We really need a deeper status discussion - likel
Hi everyone,
With the incredible growth of OpenStack, our development community is
facing complex challenges. How we handle those might determine the
ultimate success or failure of OpenStack.
With this cycle we hit new limits in our processes, tools and cultural
setup. This resulted in new limiti
Hi,
I like the idea ... with complex change, it could useful for the
understanding to split it into smaller changes during development.
Do we need to expose such feature under git review? we could define a new
subcommand? git reviewflow?
Cédric,
ZZelle@IRC
On Tue, Aug 5, 2014 at 4:49 PM,
There was also talk about a third administrative status like ON/OFF...
We really need a deeper status discussion - likely high bandwith to work all of
that out.
German
-Original Message-
From: Brandon Logan [mailto:brandon.lo...@rackspace.com]
Sent: Tuesday, August 05, 2014 8:27 AM
To:
Hello Vijay!
Well this is a hold over from v1, but the status is a provisioning
status. So yes, when something is deployed successfully it should be
ACTIVE. The exception to this is the member status, in that it's status
can be INACTIVE if a health check fails. Now this will probably cause
edg
Hi,
Is there any description of how this will be consumed by Nova. My concern is
this code landing there.
Thanks
Gary
From: Robert Kukura mailto:kuk...@noironetworks.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, August 5, 2014 at 5:20 PM
To: OpenStack L
On 08/05/2014 09:27 AM, Sylvain Bauza wrote:
>
> Le 05/08/2014 13:06, Ryan Brown a écrit :
> -1 to this as git-review default behaviour. Ideally, branches should be
> identical in between Gerrit and local Git.
Probably not as default behaviour (people who don't want that workflow
would be drive
On 8/4/14, 4:27 PM, Mark McClain wrote:
All-
tl;dr
* Group Based Policy API is the kind of experimentation we be should
attempting.
* Experiments should be able to fail fast.
* The master branch does not fail fast.
* StackForge is the proper home to conduct this experiment.
The disconnect her
Hi there!
I'll be back next week but the feature u are wanting currently doesn't exist
(so that would be why u aren't seeing such data). If u want it then a blueprint
or spec seems appropriate for this kind of historical information.
Sound good?
Btw, the logbook is more for state and flow pers
Le 05/08/2014 15:56, Jay Lau a écrit :
Hi,
We submitted three simple but very interesting topics for Paris
Summit, please check if you are interested.
1) Holistic Resource Scheduling:
https://www.openstack.org/vote-paris/Presentation/schedule-multiple-tiers-enterprise-application-in-opensta
Hi,
We submitted three simple but very interesting topics for Paris Summit,
please check if you are interested.
1) Holistic Resource Scheduling:
https://www.openstack.org/vote-paris/Presentation/schedule-multiple-tiers-enterprise-application-in-openstack-environment-prs-a-holistic-scheduler-for-b
Hi !
Yes using scripts is easy for users!
In this guide, our objective was to detail all the steps of installation.
We will use scripts in our next guide ;)
Thank you for suggestion :)
Regards,
Chaima Ghribi
2014-08-05 3:46 GMT+02:00 Shake Chen :
> Hi
>
> maybe you can consider use script cre
Le 05/08/2014 13:06, Ryan Brown a écrit :
On 08/04/2014 07:18 PM, Yuriy Taraday wrote:
Hello, git-review users!
all changes from your branch is
uploaded to Gerrit as _one_ change request;
master: M---N-O-...
\\\E* <= uploaded
feature: A-B-...-C-D-...-E
+1, this
The Oslo team is pleased to announce that oslo.vmware 0.5.0, the latest version
of the OpenStack/VMware integration library, has been released.
This version includes:
* _trunc_id to check if the session_id is not None
* Enabled hacking check H305
* Imported Translations from Transifex
* Add cons
Thanks Lana!
On Mon, Aug 4, 2014 at 11:32 PM, Mike Spreitzer wrote:
> Lana Brindley wrote on 08/04/2014 11:05:24
> PM:
>
> > I just wanted to let you all know about the OpenStack Networking Docs
> > Swarm being held in Brisbane on 9 August.
> > ...
>
> +++ on this.
>
> I can not contribute ans
Hope this links helps you
http://www.joinfu.com/2014/01/understanding-the-openstack-ci-system/
http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/
http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing-system-part-2/
--
Trinath Somanchi - B39208
trinat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/08/14 13:30, Osanai, Hisashi wrote:
>
> Thank you for your quick response.
>
> I don't have enough rights for nominating the bug so I put the tag
> "icehouse-backport-potential" instead.
>
> https://bugs.launchpad.net/ceilometer/+bug/1326250
Hi Salvatore,
On 5 August 2014 10:34, Salvatore Orlando wrote:
> Once in place, the CI system should be able to pick up the patches from
> the new plugin or driver on gerrit.
>
> In my opinion, successful CI runs against those patches should constitute
> a sufficient proof of the validity of the
Thank you for your quick response.
I don't have enough rights for nominating the bug so
I put the tag "icehouse-backport-potential" instead.
https://bugs.launchpad.net/ceilometer/+bug/1326250
On Tuesday, August 05, 2014 6:35 PM, Ihar Hrachyshka wrote:
> https://wiki.openstack.org/wiki/StableBr
Hi Mathieu:
We have deployed the new l2pop described in the previous mail in our
environment, and works pretty well. It solved the timing problem, and
also reduces lots of l2pop rpc calls. I'm going to file a blueprint to
propose the changes.
On Fri, Jul 18, 2014 at 10:26 PM, Mathieu Rohon wrote
On 08/04/2014 07:18 PM, Yuriy Taraday wrote:
> Hello, git-review users!
>
> 0. create new local branch;
>
> master: M--
> \
> feature: *
>
> 1. start hacking, doing small local meaningful (to you) commits;
>
> master: M--
> \
> feature: A-B-...-C
>
> 2. since hac
Hi-
In your CI, before running devstack, configure neutron code base with your code
(yet to be approved) and run stack.sh.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
From: Yangxurong [mailto:yangxur...@huawei.com]
Sent: Tuesday, August 05, 2014 4:06 PM
To: OpenSt
Hi folks,
Recently I am working on building CI for our ml2 driver. Since our code has not
been merged, when running the devstack-vm-gate script, the code in neutron
project will be updated so our code is missing. Without the code, devstack will
fail since it is configured to use our own ml2 dri
On 8/4/14, 5:39 PM, "mar...@redhat.com" wrote:
>On 03/08/14 13:07, Gary Kotton wrote:
>> Hi,
>> Happy you asked about this. This is an idea that we have:
>>
>> Below is a suggestion on how we can improve the metadata service. This
>>can
>> be done by leveraging the a Load balancers supports X-
On 05/08/14 08:43, Peeyush Gupta wrote:
> Hi all,
>
> I have been trying to set up tripleo using instack.
> When I try to deploy overcloud, I get a heat related
> error. Here it is:
>
> [stack@localhost ~]$ heat stack-list
> ERROR: Timeout while waiting on RPC response - topic: "engine", RPC met
On 04/08/14 00:50, Steve Baker wrote:
> On 01/08/14 12:19, Steve Baker wrote:
>> The changes to port tripleo-heat-templates to HOT have been rebased to
>> the current state and are ready to review. They are the next steps in
>> blueprint tripleo-juno-remove-mergepy.
>>
>> However there is coordinat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/08/14 11:22, Osanai, Hisashi wrote:
>
> Hi,
>
> I would like to have the following fix for IceHouse branch because
> the problem happens on it but the fix was committed on Juno-2
> only. Is there any process to backport fixes to old branches
Hi:
I think we had some discussions around 'status' attribute
earlier, I don't recollect the conclusion.
Does it reflect the deployment status?
Meaning, if the status of an entity is ACTIVE, the user has to
infer that the entity is deployed successfully in the backen
Hi,
I would like to have the following fix for IceHouse branch because
the problem happens on it but the fix was committed on Juno-2 only.
Is there any process to backport fixes to old branches?
https://bugs.launchpad.net/ceilometer/+bug/1326250
Best Regards,
Hisashi Osanai
_
On 08/05/2014 04:06 PM, Julie Pichon wrote:
> On 05/08/14 08:11, Thomas Goirand wrote:
>> And there's also test_change_password_shows_message_on_login_page which
>> fails. Here's the end of the stack dump:
>>
>> File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line
>> 375, in send
>>
try to check if there are floatingips on the VMs on that subnet
962b8364-a2b4-46cc-95be-28cbab62b8c2
On Tue, Aug 5, 2014 at 3:24 PM, Sayali Lunkad
wrote:
> Hi,
>
> The issue was resolved by following the commands below.
>
> neutron port-update --device_owner clear
> neutron port-delete
> neut
Hi Luke,
Once in place, the CI system should be able to pick up the patches from the
new plugin or driver on gerrit.
In my opinion, successful CI runs against those patches should constitute a
sufficient proof of the validity of the CI system.
Salvatore
Il 05/ago/2014 09:57 "Luke Gorrie" ha scri
Marc,
A good example for that is Rally's Tempest configuration module. Currently
> Rally has all the logic to configure Tempest and for that you have your
> own way to build the tempest conf out of a template [1]. If the QA
> team decides to rework the configuration Rally is broken.
Absolutely a
On 05/08/14 08:11, Thomas Goirand wrote:
> And there's also test_change_password_shows_message_on_login_page which
> fails. Here's the end of the stack dump:
>
> File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line
> 375, in send
> raise ConnectionError(e, request=request)
> Co
Boris Pavlovic wrote:
> By the way, I am really not sure how being one Program will help us to
> collaborate? What it actually changes?
Being in one program means you're in the same team, the same meetings,
with ultimate decisions taken by the same one PTL. It obviously makes it
easier to avoid d
Howdy,
Could somebody please clarify the protocol for bringing up a CI for a new
Neutron driver?
Specifically, how does one resolve the chicken-and-egg situation of:
1. CI should be enabled before the driver is merged.
2. CI should test the refspecs given by Gerrit, which will not include the
c
Hello,
I'm currently evaluating taskflow. I read through the examples and
extracted bits and peaces to write a little app in order to see how it
works. Right now I'm most interested in the job board and the flows.
In my code I post a Job to a jobboard, pick it up, end execute a flow
(similar to t
Hi,
The issue was resolved by following the commands below.
neutron port-update --device_owner clear
neutron port-delete
neutron router-delete
Thanks,
Sayali.
On Sat, Aug 2, 2014 at 3:49 PM, Sayali Lunkad
wrote:
> Hi Zzelle,
>
> Thanks for the prompt response.
> As you mentioned I clear
On 08/04/2014 05:05 PM, Romain Hardouin wrote:
> Hi,
>
> Note that Django 1.7 requires Python 2.7 or above[1] while Juno still
> requires to be compatible with Python 2.6 (Suse ES 11 uses 2.6 if my memory
> serves me).
>
> [1] https://docs.djangoproject.com/en/dev/releases/1.7/#python-compatibi
101 - 141 of 141 matches
Mail list logo
