On 13/08/14 17:05, Kyle Mestery wrote:
> Per this week's Neutron meeting [1], it was decided that offering a
> rotating meeting slot for the weekly Neutron meeting would be a good
> thing. This will allow for a much easier time for people in
> Asia/Pacific timezones, as well as for people in Europe
1. os-apply-config: no changes, 0.1.19
2. os-refresh-config: no changes, 0.1.7
3. os-collect-config: no changes, 0.1.27
4. os-cloud-config: release: 0.1.6 --> 0.1.7
--> https://pypi.python.org/pypi/os-cloud-config/0.1.7
-->
http://tarballs.openstack.org/os-clo
1. os-apply-config: release: 0.1.19 --> 0.1.20
--> https://pypi.python.org/pypi/os-apply-config/0.1.20
-->
http://tarballs.openstack.org/os-apply-config/os-apply-config-0.1.20.tar.gz
2. os-refresh-config: no changes, 0.1.7
3. os-collect-config: release: 0.1.27 --> 0.1
On 09/09/14 21:32, Gregory Haynes wrote:
> Hello everyone!
>
> I have been working on a meta-review of StevenK's reviews and I would
> like to propose him as a new member of our core team.
>
> As I'm sure many have noticed, he has been above our stats requirements
> for several months now. More i
Hi,
as part of general housekeeping on our reviews, it was discussed at last
week's meeting [1] that we should set workflow -1 for stale reviews
(like gerrit used to do when I were a lad).
The specific criteria discussed was 'items that have a -1 from a core
but no response from author for 14 day
1. os-apply-config: release: 0.1.21 --> 0.1.22
--> https://pypi.python.org/pypi/os-apply-config/0.1.22
-->
http://tarballs.openstack.org/os-apply-config/os-apply-config-0.1.22.tar.gz
2. os-refresh-config: no changes, 0.1.7
3. os-collect-config: no changes, 0.1.28
4. o
On 17/09/14 16:40, Charles Crouch wrote:
>
>
> - Original Message -
>> Hi,
>>
>> as part of general housekeeping on our reviews, it was discussed at last
>> week's meeting [1] that we should set workflow -1 for stale reviews
>> (like gerrit used to do when I were a lad).
>>
>> The specifi
On 18/09/14 00:29, James Polley wrote:
>
>
> On Wed, Sep 17, 2014 at 6:26 PM, [email protected]
> <mailto:[email protected]> <mailto:[email protected]>> wrote:
>
> Hi,
>
> as part of general housekeeping on our reviews, it was discussed a
On 02/12/13 15:05, gustavo panizzo wrote:
> On 11/27/2013 01:50 PM, Maru Newby wrote:
>> Just a heads up, the console output for neutron gate jobs is about to get a
>> lot noisier. Any log output that contains 'ERROR' is going to be dumped
>> into the console output so that we can identify and
On 06/12/13 04:31, Tzu-Mainn Chen wrote:
> Hey all,
>
> I've attempted to spin out the requirements behind Jarda's excellent
> wireframes
> (http://lists.openstack.org/pipermail/openstack-dev/2013-December/020944.html).
> Hopefully this can add some perspective on both the wireframes and the nee
On 07/12/13 04:42, Tzu-Mainn Chen wrote:
>> On 7 December 2013 08:15, Jay Dobies wrote:
>>> Disclaimer: I'm very new to the project, so apologies if some of my
>>> questions have been already answered or flat out don't make sense.
>>
>>
>> NP :)
>>
>>
* optional node profile for
On 09/12/13 18:01, Jay Dobies wrote:
>> I believe we are still 'fighting' here with two approaches and I believe
>> we need both. We can't only provide a way 'give us resources we will do
>> a magic'. Yes this is preferred way - especially for large deployments,
>> but we also need a fallback so th
On 16/01/14 00:28, Clint Byrum wrote:
> Excerpts from James Slagle's message of 2014-01-15 05:07:08 -0800:
>> I'll start by laying out how I see editing or updating nodes working
>> in TripleO without Tuskar:
>>
>> To do my initial deployment:
>> 1. I build a set of images for my deployment for di
On 23/04/14 18:05, Eugene Nikanorov wrote:
> Hi neutrons,
>
> A quick question of the ^^^
> I heard from many of you that a term 'flavor' is undesirable, but so far
> there were no suggestions for the notion that we are going to introduce.
> So please, suggest you name for the resource.
> Names th
esdrop.openstack.org/meetings/networking/2014/networking.2014-01-06-21.02.log.html
On 21/04/14 17:38, [email protected] wrote:
> Hi,
>
> I think both PTL candidates mentioned process improvements wrt
> contributions and reviews in their candidacy announcements. As a new
> Neutron
On 24/04/14 10:21, [email protected] wrote:
> Hi,
>
>
> just to wrap this up following discussion during this week's irc meeting
> [1] (thanks for bringing it up Kyle)
>
> I didn't hear any -1 to the general idea of having designated review
> times (and quite
n/+spec/neutron-flavor-framework
http://git.openstack.org/cgit/openstack/neutron-specs
>
> Mark: personally I find name 'flavor' suitable because it's the same
> concept as nova flavor.
> So I'll use it in BP/code unless something better come up.
>
> Thanks,
> Eugene.
>
On 01/05/14 10:47, Roman Podoliaka wrote:
> Hi all,
>
> Following the mailing list thread started by Marios I've put some
> initial questions to discuss into this etherpad document:
>
> https://etherpad.openstack.org/p/juno-summit-tripleo-neutron
>
> You are encouraged to take a look at it and a
On 08/05/14 21:29, Henry Gessau wrote:
> Have any of you javascript gurus respun this for the new gerrit version?
> Or can this now be done on the backend somehow?
haha, have been thinking this since the gerrit upgrade a couple days
ago. It was very useful for reviews... I am NOT a javascript guru
On 09/05/14 12:33, [email protected] wrote:
> On 08/05/14 21:29, Henry Gessau wrote:
>> Have any of you javascript gurus respun this for the new gerrit version?
>> Or can this now be done on the backend somehow?
>
> haha, have been thinking this since the gerrit upgrade a
On 23/05/14 01:34, Salvatore Orlando wrote:
> As most of you probably know already, this is one of the topics discussed
> during the Juno summit [1].
> I would like to kick off the discussion in order to move towards a concrete
> design.
>
> Preamble: Considering the meat that's already on the pla
On 23/05/14 05:41, Mohammad Banikazemi wrote:
>
> Well, for a use case we had in mind we were trying to figure out how to
> simply get an IP address on a subnet. We essentially want to use such an
> address internally by the controller and make sure it is not used for a
> port that gets created on
On 27/05/14 17:14, Kyle Mestery wrote:
> Hi Neutron developers:
>
> I've spent some time cleaning up the BPs for Juno-1, and they are
> documented at the link below [1]. There are a large number of BPs
> currently under review right now in neutron-specs. If we land some of
> those specs this week,
On 28/05/14 17:57, Kyle Mestery wrote:
> On Wed, May 28, 2014 at 12:41 AM, [email protected]
> wrote:
>> On 27/05/14 17:14, Kyle Mestery wrote:
>>> Hi Neutron developers:
>>>
>>> I've spent some time cleaning up the BPs for Juno-1, and they are
>&
On 29/05/14 00:48, Eugene Nikanorov wrote:
> Hi,
>
> I have two questions that previously were briefly discussed. Both of them
> still cause discussions within advanced services community, so I'd like to
> make final clarification in this email thread.
>
> 1. Usage of "Service Type Framework"
> I
On 11/03/14 10:20, Xurong Yang wrote:
> It's allowed to create duplicate sg with the same name.
> so exception happens when creating instance with the duplicate sg name.
Hi Xurong - fyi there is a review open which raises this particular
point at https://review.openstack.org/#/c/79270/2 (together
ow about other
> folks's view, maybe we need fix it.
>
agreed. OK does the existing bug at
https://bugs.launchpad.net/neutron/+bug/1289195 cover you? If so let's
continue the discussion there (or create a new one)
thanks! marios
> thanks,Xurong
>
>
> 2014-03-11 21:
On 04/03/14 23:00, Carl Baldwin wrote:
> Nachi,
>
> Great! I'd been meaning to do something like this. I took yours and
> tweaked it a bit to highlight failed Jenkins builds in red and grey
> other Jenkins messages. Human reviews are left in blue.
>
> javascript:(function(){
> list = docum
On 12/03/14 08:34, abhishek jain wrote:
> Thanks for the help.
> I'm now able to proceed further with your suggestions.
> I'm now enabling live migration in /etc/nova/nova.conf by adding the below
> line
>
> live_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_LIVE
On 26/03/14 11:50, Ladislav Smola wrote:
> On 03/25/2014 09:17 PM, Robert Collins wrote:
>> TripleO has just seen an influx of new contributors. \o/. Flip side -
>> we're now slipping on reviews /o\.
>>
>> In the meeting today we had basically two answers: more cores, and
>> more work by cores.
>>
Hi, we made a couple of short videos for an internal 'show and tell what
I'm currently working on' for colleagues - they show master
tuskar/tuskar-ui/horizon as of ~Tuesday this week:
Node Profile config @
https://www.youtube.com/watch?v=Ranfkx34dhg
Shows definition of Node Profiles for each of co
On 03/04/14 14:02, Robert Collins wrote:
> Getting back in the swing of things...
>
> Hi,
> like most OpenStack projects we need to keep the core team up to
> date: folk who are not regularly reviewing will lose context over
> time, and new folk who have been reviewing regularly should be trus
Hello Tripleo/Neutron:
I've recently found some cycles to look into Neutron. Mostly because
networking rocks, but also so we can perhaps better address Neutron
related issues/needs down the line. I thought it may be good to ask the
wider team if there are others that are also interested in
Neutron
On 07/04/14 00:27, Steve Baker wrote:
> On 05/04/14 04:47, Tomas Sedovic wrote:
>> Hi All,
>>
>> I was wondering if the time has come to document what exactly are we
>> doing with tripleo-heat-templates and merge.py[1], figure out what needs
>> to happen to move away and raise the necessary bluepri
On 07/04/14 18:05, Jan Provazník wrote:
> On 04/07/2014 03:49 PM, Roman Podoliaka wrote:
> 2. HA the neutron node. For each neutron services/agents of
> interest (neutron-dhcp-agent, neutron-l3-agent,
> neutron-lbaas-agent ... ) fix any issues with running these in
> HA - perhaps th
On 07/04/14 16:49, Roman Podoliaka wrote:
> Hi all,
>
> Perhaps, we should file a design session for Neutron-specific questions?
that's a good idea - unfortunately I won't be at summit... if there is
more interest and you do go ahead with this please let me know I will
try and join by hangout for
ent/ch-network.html.
>
> What other choices, except corosync+pacemaker, do we have for neutron ha?
thanks for the pointers Dmitriy! Perhaps this can be discussed if a
discussion/session is put together at summit as suggested by Roman
marios
>
> Thanks
>
>
>
> On Mon, A
On 08/04/14 02:50, Robert Collins wrote:
> tl;dr: 3 more core members to propose:
> bnemec
> greghaynes
> jdon
>
+1
>
> On 4 April 2014 08:55, Chris Jones wrote:
>> Hi
>>
>> +1 for your proposed -core changes.
>>
>> Re your question about whether we should retroactively apply the 3-a-day
>> ru
On 09/04/14 16:54, Jaromir Coufal wrote:
> Hello OpenStackers,
>
> I would like to share with you non-narrated demo of current version of
> 'Tuskar-UI' project, which is very close to Icehouse release (one or two
> more patches to come in).
>
> Tuskar-UI is a user interface based on TripleO appro
On 10/04/14 20:55, Jay Dobies wrote:
> On 04/10/2014 01:40 PM, Nachi Ueno wrote:
>> Hi Jarda
>>
>> Congratulations
>> This release and the demo is super awesome!!
>> Do you have any instruction to install this one?
>
> I'd like to see this too. I asked a few times and never got an answer on
> whet
On 11/04/14 10:35, Ladislav Smola wrote:
> Hello,
>
> we have used this list of steps for the demo on Fedora 20:
> https://wiki.openstack.org/wiki/Tuskar/Devtest
nice!
>
> The demo is running on one machine with 24GB RAM and 120GB disk. We are
> using
> virtualized baremetals(bm_poseur) for dev
Hi,
I am really stumped by a Jenkins failure for one of my reviews... @
https://review.openstack.org/#/c/59212/ if any kind soul has any
pointers/help I will be very grateful. The strange thing is that Jenkins
+1 this patchset (Apr 2) but subsequently failed as described below:
The failure is fro
lly next one) I owe you at
*least* one beer ;)
thanks, marios
>
> I will comment on the review as well.
>
> Cheers,
> Kevin Benton
>
>
> On Mon, Apr 14, 2014 at 9:23 AM, [email protected] wrote:
>
>> Hi,
>>
>> I am really stumped by a Jenkins
On 15/04/14 21:54, Ben Nemec wrote:
> On 04/15/2014 01:44 PM, Robert Collins wrote:
>> I've been watching the nova process, and I think its working out well
>> - it certainly addresses:
>> - making design work visible
>> - being able to tell who has had input
>> - and providing clear feedback
On 16/04/14 00:07, Kyle Mestery wrote:
> Given the success the Nova team has had in handling reviews using
> their new nova-specs gerrit repository, I think it makes a lot of
> sense for Neutron to do the same. With this in mind, I've added
> instructions to the BP wiki [1] for how to do. Going for
On 15/04/14 20:44, Robert Collins wrote:
> I've been watching the nova process, and I think its working out well
> - it certainly addresses:
> - making design work visible
> - being able to tell who has had input
> - and providing clear feedback to the designers
>
> I'd like to do the same thin
Hi,
I think both PTL candidates mentioned process improvements wrt
contributions and reviews in their candidacy announcements. As a new
Neutron dev I have seen that it is easy for reviews to go unnoticed,
especially when they are stand-alone bug fixes that aren't part of a
particular blueprint gro
On 21/04/14 18:29, Kyle Mestery wrote:
> On Mon, Apr 21, 2014 at 9:38 AM, [email protected]
> wrote:
>> Hi,
>>
>> I think both PTL candidates mentioned process improvements wrt
>> contributions and reviews in their candidacy announcements. As a new
>> Neutron
ussed as such.
thanks! marios
>
>
> On Tue, Apr 22, 2014 at 12:54 AM, [email protected]
> wrote:
>> On 21/04/14 18:29, Kyle Mestery wrote:
>>> On Mon, Apr 21, 2014 at 9:38 AM, [email protected]
>>> wrote:
>>>> Hi,
>>>>
>>>
On 25/06/14 10:52, James Polley wrote:
> Until https://review.openstack.org/#/c/83250/, the setup-*-password scripts
> used to drop password files into $CWD, which meant that if you ran the
> script from a different location next time, your old passwords wouldn't be
> found.
>
> https://review.ope
On 14/07/14 19:11, Ben Nemec wrote:
> +1. In my experience they've both demonstrated that they know what
> they're doing.
>
> I think the bikeshedding/grammar nits on specs is kind of a separate
> issue that will need to be worked out in general. It's still very early
> on in this new *-specs re
Hi all,
I have been asked by a colleague about the status of A/A HA for
neutron-* processes. From the 'HA guide' [1], l3-agent and
metadata-agent are the only neutron components that can't be deployed in
A/A HA (corosync/pacemaker for a/p is documented as available 'out of
the box' for both).
The
On 02/08/14 02:22, Assaf Muller wrote:
> Hey Marios, comments inline.
>
> - Original Message -
>> Hi all,
>>
>> I have been asked by a colleague about the status of A/A HA for
>> neutron-* processes. From the 'HA guide' [1], l3-agent and
>> metadata-agent are the only neutron components th
details (will be
easier once the spec is out) but it seems like you're proposing an
addition (port-lookup) that will change the way the metadata agent is
called; in fact does it make the neutron metadata proxy obsolete? I will
keep a look out for the spec,
thanks, marios
> Thanks
>
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
This was my first run so if I missed something please ping me, esp if
you are in need of a stable branch (for those projects we do that for),
1. os-apply-config: no changes, 0.1.19
2. os-refresh-config: no changes, 0.1.7
3. os-collect-config: no changes, 0.1.25
4. os-cloud-c
I have an AI from the tuskar community meeting to come up with a
description of how TripleO 'differs from' Tuskar. I have no idea where
this will be used/placed and in fact I don't know where to send it:
should we paste it into the naming etherpad, open a launchpad docs
blueprint (seems a bit much,
On 19/09/13 11:08, Tomas Sedovic wrote:
> Hi everyone,
>
> Some of us Tuskar developers have had the chance to meet the TripleO
> developers face to face and discuss the visions and goals of our projects.
>
> Tuskar's ultimate goal is to have to a full OpenStack management
> solution: letting the
On 18/09/13 19:44, Robert Collins wrote:
> On 18 September 2013 20:59, [email protected] wrote:
>> I have an AI from the tuskar community meeting to come up with a
>> description of how TripleO 'differs from' Tuskar. I have no idea where
>> this will be used/placed
On 23/09/13 21:59, Doug Hellmann wrote:
> On Mon, Sep 23, 2013 at 12:31 PM, Petr Blaho wrote:
>
>> Hi,
>>
>> during my work on getting tests to pass for
>> https://review.openstack.org/#/c/46947/ I discovered that we are
>> misusing pecan models for HTTP representation of Resources.
>>
>> In cont
On 02/10/13 12:52, Thierry Carrez wrote:
> Monty Taylor wrote:
>>
>>
>> On 10/01/2013 08:08 PM, Robert Collins wrote:
>>> We'd like to get tuskar projects doing releases sooner rather than
>>> later. For python-tuskarclient, this is pretty much a no-brainer : we
>>> just need to start doing it.
+1
On 01/10/13 00:07, Jaromir Coufal wrote:
> Just BTW:
>
> I know that lot of folks were watching the youtube stream
> (http://youtu.be/m3y6uD8yKVQ), so please feel free to give any feedback
> you have to this thread. I believe that this is good way to proceed
> forward and how to make things flexib
On 16/10/13 03:22, Robert Collins wrote:
> Hi, during the TripleO meeting today we had two distinct discussions
> about reviews.
>
> Firstly, our stats have been slipping:
> http://russellbryant.net/openstack-stats/tripleo-openreviews.html
>
>
> Stats since the last revision without -1 or -2 (ig
63 matches
Mail list logo
