Hi all,
I'm agree with you Mathias, we should separate and rename.
My suggestions:
horizon -> python-horizon
openstack_dashboard -> openstack-horizon
Cheers,
Marcos.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openst
On 11/10/2014 12:19 PM, Matthias Runge wrote:
On Thu, Oct 30, 2014 at 01:13:48PM +0100, Matthias Runge wrote:
Hi,
tl;dr: how to progreed in separating horizon and openstack_dashboard
About a year ago now we agreed, it makes sense to separate horizon and
openstack_dashboard.
At the past summit
We have submitted our spec just a few days ago while I have heared that we
should have our spec to be "approved" before 15/11/2014 if we want our cinder
driver merged in Kilo. Just few days left!
Having our cinder driver merged into Kilo is turely important for us, so I
would be very appreciate
Modernizing Horizon using Angular is really great. I would suggest a couple
of minor things to consider.
First, font-awesome is excellent and free font, but there are two problems:
it has lots of icons that are not used, it also miss some other icons worth
to have. I would suggest Fontello, it is
Hi,
I'm testing our cinder volume driver in the following setup:
- 2 nodes, ubuntu, devstack juno (2014.2.1)
- shared storage (common backend), our custom software solution + cinder
volume on shared storage
- 1 instance running on node 1, /instances directory on shared storage
- kvm, libvirt (with
Hi doc team,
I think that in the official doc of python-novaclient [1] there is a
Contributing section not synchronized with the doc in git repository: [2]
In details the section Contributing-->||Testing is not up to date
I tried to improve this page following gerrit workflow but I'm not very
On 11/11/2014 10:16 AM, Angelo Matarazzo wrote:
> Hi doc team,
> I think that in the official doc of python-novaclient [1] there is a
> Contributing section not synchronized with the doc in git repository: [2]
> [...]
Yes, this works as designed ;)
This file gets only published when there's a ne
2014-11-11 7:26 GMT+01:00 :
> - periodic-glance-python26-juno
> http://logs.openstack.org/periodic-stable/periodic-glance-python26-juno/d0ea683
> : FAILURE in 21m 09s
> - periodic-glance-python27-juno
> http://logs.openstack.org/periodic-stable/periodic-glance-python27-juno/ec60681
> : FAILURE
Hey,
Thanks for writing this up!
I am including some notes and questions inline...
On 11/11/2014 08:02 AM, Richard Jones wrote:
Hi all,
At the summit last week, we developed a plan for moving forward with
modernising Horizon's UI using AngularJS. If you weren't at that
meeting and are inter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The failure is due to glance_store 0.1.9 released yesterday. It's not
specific to Juno. I've created a bug:
https://bugs.launchpad.net/glance/+bug/1391437 and marked it as Critical.
On 11/11/14 07:26, jenk...@openstack.org wrote:
> Build failed.
>
Hi Dave,
I'm forwarding your message to openstack-stable-maint, that list has
been made read-only as decided on release management meetup on Friday
Nov 7 2014, see under "* Stable branches" in
https://etherpad.openstack.org/p/kilo-infrastructure-summit-topics
I have set explicit Reply-To: header t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/11/14 10:41, Alan Pevec wrote:
> 2014-11-11 7:26 GMT+01:00 :
>> - periodic-glance-python26-juno
>> http://logs.openstack.org/periodic-stable/periodic-glance-python26-juno/d0ea683
>> : FAILURE in 21m 09s - periodic-glance-python27-juno
>> http:
> https://bugs.launchpad.net/glance/+bug/1391437 and marked it as Critical.
ok, so current issue is a bug for both master and stable/juno but I'd
still like glance_store backward compatibility be clarified by the
Glance team.
Cheers,
Alan
___
OpenStack
Folks,
There was an idea to make a separate code freeze for repos, but we decided
not to do it. Do we plan to try it this time? It is really painful to
maintain multi-level tree of dependent review requests and wait for a few
weeks until we can merge new stuff in master.
--
Vitaly Kramskikh,
Sof
On 11 November 2014 20:10, Anton Zemlyanov wrote:
> Modernizing Horizon using Angular is really great. I would suggest a
> couple of minor things to consider.
>
> First, font-awesome is excellent and free font, but there are two
> problems: it has lots of icons that are not used, it also miss som
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> -- Forwarded message -- From: Dave Walker
> To: openstack-stable-maint
> Date: Mon, 10 Nov 2014
> 21:52:23 + Subject: New config options, no default change
>
> Hi,
>
> Looking at a stable/juno cinder proposed change[0], I ca
Hi,
Looking at a stable/juno cinder proposed change[0], I came across one
that introduces a new config option.
The default is a noop change for the behaviour, so no bad surprises on upgrade.
These sort of changes feel like they are outside the 'no config
changes' rule, but we have not really dis
On Tue, Nov 11, 2014 at 10:24:41AM +, Dave Walker wrote:
> Hi,
>
> Looking at a stable/juno cinder proposed change[0], I came across one
> that introduces a new config option.
>
> The default is a noop change for the behaviour, so no bad surprises on
> upgrade.
>
> These sort of changes fee
On 11 November 2014 20:53, Jiri Tomasek wrote:
> Hey,
>
> Thanks for writing this up!
>
> I am including some notes and questions inline...
>
> On 11/11/2014 08:02 AM, Richard Jones wrote:
>
> Hi all,
>
> At the summit last week, we developed a plan for moving forward with
> modernising Horizon
Hi Ken,
You may be better off asking this question on
https://groups.google.com/forum/#!forum/opscode-chef-openstack or posting a
bug on https://bugs.launchpad.net/openstack-chef. Alternatively, you could
hop into #openstack-chef and ask there.
--Matt
On Mon, Nov 10, 2014 at 6:23 PM, Ken Thoma
On 11/11/14 11:06 +0100, Alan Pevec wrote:
https://bugs.launchpad.net/glance/+bug/1391437 and marked it as Critical.
ok, so current issue is a bug for both master and stable/juno but I'd
still like glance_store backward compatibility be clarified by the
Glance team.
I'm on it!
We were waiti
Some updates...
Le 11 nov. 2014 08:35, "Sylvain Bauza" a écrit :
>
> Fyi, today is Remembrance Day and a national day-off in France, so I
won't be able to attend the meeting.
>
> Below are a few notes.
>
> Le 11 nov. 2014 03:07, "Dugger, Donald D" a
écrit :
>
> >
> > 1) Summit recap
> >
> >
Hello Sumit.
Unfortunately I could not go to the round table meeting, sorry for the
absence.
Did you talk about traffic steering? Is there some place or etherpad with a
summary of what was discussed/outlined?
Cheers,
On 5 November 2014 17:22, Sumit Naiksatam wrote:
> Hi,
>
> We had a productive
Neutron DVR is not something that has been tested but as long as DVR exposes a
similar API to the current Neutron Router implementation there should be no
problems. Curvature is agnostic to the underlying implementation of logical
components.
Additional network services like LBaaS are on our ro
Daniel P. Berrange wrote:
> On Tue, Nov 11, 2014 at 10:24:41AM +, Dave Walker wrote:
>> Hi,
>>
>> Looking at a stable/juno cinder proposed change[0], I came across one
>> that introduces a new config option.
>>
>> The default is a noop change for the behaviour, so no bad surprises on
>> upgrad
Hello,
I’m also interested in having OVF package support for applications.
As it was described earlier, there are two main tracks to this – OVF artefacts
in Glance (corresponding driver), and translating OVF descriptors to Heat
templates.
Is there any etherpad from the session?
-
Dimitri
From: ,
On Mon, 10 Nov 2014, Zane Bitter wrote:
I think you missed the most important option I mentioned in the thread - for
the TC to engage more with the community and take an active technical
leadership role in the design of OpenStack as a whole.
+1
I've been in this scene for about half a year n
See everyone next week
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Sun, 9 Nov 2014, Kashyap Chamarthy wrote:
On Sun, Nov 09, 2014 at 02:48:49PM +, Chris Dent wrote:
On Sat, 8 Nov 2014, Kashyap Chamarthy wrote:
[I realize you intend to use physical machine for DevStack, still I
thought I'd post this here.]
Thanks for posting it. Each added datapoint
> New config options may not change behavior (if default value preserves
> behavior), they still make documentation more incomplete (doc, books,
> and/or blogposts about Juno won't mention that option).
That's why we definitely need such changes described clearly in stable
release notes.
I also le
Hi folks:
Apologies for the delay in announcing the Neutron mid-cycle, but I was
confirming the details up until last night. I've captured the details
on an etherpad here [1]. The dates are December 8-10
(Monday-Wednesday), and it will be at the Adobe offices in Lehi, Utah,
USA.
We're still colle
Hi,
In order to enforce our translation policies -
http://docs.openstack.org/developer/oslo.i18n/guidelines.html - we have added a
hacking rule in Neutron. If you wish to jump aboard this effort then please let
me know. There are patches for all directories except the plugins and services.
Thank
> How many people would want to attend both the OSSG mid-cycle and the Barbican
> one?
+1
-Nate
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
For those unable to attend will there be an option of remote access?
Thanks
Gary
On 11/11/14, 3:04 PM, "Kyle Mestery" wrote:
>Hi folks:
>
>Apologies for the delay in announcing the Neutron mid-cycle, but I was
>confirming the details up until last night. I've captured the details
>on an ethe
On 2014-11-11 08:26:30 +0800 (+0800), Thomas Goirand wrote:
[...]
> We then better have just an OpenStack keyring, just like there's a
> Debian developer keyring, on which we delegate the trust to some
> kind of organization (but this needs to be used for something...).
[...]
I've been putting tog
On Tue, Nov 11, 2014 at 8:00 AM, Gary Kotton wrote:
> Hi,
> For those unable to attend will there be an option of remote access?
> Thanks
> Gary
>
We'll do our best to make this happen. I'll see if we can get a Google
Hangout going in the room, and make sure people are on IRC.
Thanks!
Kyle
> On
> > I think you missed the most important option I mentioned in the thread -
> > for
> > the TC to engage more with the community and take an active technical
> > leadership role in the design of OpenStack as a whole.
>
> +1
>
> I've been in this scene for about half a year now and the only
>
On 2014-11-10 23:55:59 -0500 (-0500), Adam Young wrote:
> Um, yeah. What Zigo said.
Agreed. I tried out keybase.io (but not the insane private key
hosting obviously), was unimpressed and have since deleted my
account. I'll acknowledge that as someone who already doesn't use
social media and consid
On 2014-11-11 09:15:44 -0500 (-0500), Eoghan Glynn wrote:
[...]
> The community engagement aspect I referred to up-thread was more
> related to whether that communication channel is as bi-directional
> as it could or should be.
It's actually not _that_ hard to present a motion before the TC.
Sylvain-
Tnx for the update and enjoy the holiday (it’s Veteran’s day here but most
businesses are still open).
I’ll still hold the meeting in case anyone wants an update from the Summit but
we’ll probably start again in earnest next week.
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse."
On Tue, 11 Nov 2014, Eoghan Glynn wrote:
Believe it or not, the communication of what the TC is up to has
actually improved significantly over the last cycle, with those
regular TC Update posts from russellb, ttx, vishy & others:
http://www.openstack.org/blog/tag/technical-committee
That's gr
+1
On Tue, 2014-11-11 at 08:49 -0500, Nathan Reller wrote:
> > How many people would want to attend both the OSSG mid-cycle and the
> > Barbican one?
>
> +1
>
> -Nate
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://l
HI Dmitry,
I was not able to attend, by Alex was on this session. I will check what
was discussed. Even if it was not discussed on the summit, we can continue
to discuss it here in the mailing list.
Thanks
Gosha
On Tue, Nov 11, 2014 at 4:39 AM, Dimitri Mazmanov <
dimitri.mazma...@ericsson.com> w
On 10/11/14 12:09, Eoghan Glynn wrote:
> > 2.*weaken the continuity guarantee* - by un-staggering the terms,
> > so that all seats are contested at each election.
>
>This is probably not feasible.
Interesting, why do you think it wouldn't be feasible?
I was under the impression that o
The resource tracker objects BP was grouped under the scheduler work items as
well:
http://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/make-resource-tracker-use-objects.html
-
1) Summit recap
2) Status of
Alexis Lee said on Mon, Nov 10, 2014 at 05:34:13PM +:
> How about we support YAQL expressions? https://github.com/ativelkov/yaql
> Plus some HOFs (higher-order functions) like cond, map, filter, foldleft
> etc?
We could also use YAQL to provide the HOFs.
> Here's first_nonnull:
>
> config:
Excerpts from Jeremy Stanley's message of 2014-11-11 06:31:57 -0800:
> On 2014-11-10 23:55:59 -0500 (-0500), Adam Young wrote:
> > Um, yeah. What Zigo said.
>
> Agreed. I tried out keybase.io (but not the insane private key
> hosting obviously), was unimpressed and have since deleted my
> account.
On Tue, Nov 11, 2014 at 01:46:34PM +, Gary Kotton wrote:
> In order to enforce our translation policies -
> http://docs.openstack.org/developer/oslo.i18n/guidelines.html - we have added
> a hacking rule in Neutron. If you wish to jump aboard this effort then please
> let me know. There are patc
On Nov 10, 2014, at 10:55 AM, Mike Bayer wrote:
> Bonjour openstackers -
>
> While you were all sipping champagne on the Champs-Élysées, I took some time
> to tackle one of the two most critically wanted features in Alembic, which is
> that of being able to migrate tables on a SQLite database
Thanks for reminding!
2014-11-11 23:48 GMT+08:00 Louis Taylor :
> On Tue, Nov 11, 2014 at 01:46:34PM +, Gary Kotton wrote:
> > In order to enforce our translation policies -
> > http://docs.openstack.org/developer/oslo.i18n/guidelines.html - we have
> added
> > a hacking rule in Neutron. If y
I like this approach and seems to have greater utility beyond the original
proposal. I'm not fussed on YAQL or straight up JSONPath, but something along
those lines seems to make sense.
On Nov 11, 2014, at 9:35 AM, Alexis Lee
wrote:
> Alexis Lee said on Mon, Nov 10, 2014 at 05:34:13PM +:
I paste the URL here to help those who interest with it:
https://review.openstack.org/#/c/133150/
Besides, I think add [cinder] tag maybe help in email's title.
Damon
2014-11-11 16:50 GMT+08:00 liuxinguo :
> We have submitted our spec just a few days ago while I have heared that we
> should hav
On 2014-11-11 07:38:07 -0800 (-0800), Clint Byrum wrote:
> It's sort of odd that you think bringing the same capability we have
> had for decades with IRC to web users is a blight on the internet. ;)
> The blight is the people being stupid .. not the technology in use.
[...]
I was waxing poetic, a
On 11/11/14 11:45 +0100, Flavio Percoco wrote:
On 11/11/14 11:06 +0100, Alan Pevec wrote:
https://bugs.launchpad.net/glance/+bug/1391437 and marked it as Critical.
ok, so current issue is a bug for both master and stable/juno but I'd
still like glance_store backward compatibility be clarified
Kyle Mestery wrote:
> Apologies for the delay in announcing the Neutron mid-cycle, but I was
> confirming the details up until last night. I've captured the details
> on an etherpad here [1]. The dates are December 8-10
> (Monday-Wednesday), and it will be at the Adobe offices in Lehi, Utah,
> USA.
+1 would be great to at least have a hangout going
_sent from my mobile device, sorry for spacing/spelling/top-posting/.*_
-Original Message-
From: Kyle Mestery [mest...@mestery.com]
Received: Tuesday, 11 Nov 2014, 16:14
To: OpenStack Development Mailing List (not for usage questions)
Please don't send review requests to the list. Preferred methods are
discussed here:
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
Thanks.
-Ben
On 11/11/2014 10:08 AM, Damon Wang wrote:
> I paste the URL here to help those who interest with it:
> https://review.o
On 10/11/14 12:34, Alexis Lee wrote:
Zane Bitter said on Fri, Nov 07, 2014 at 12:35:09AM +0100:
Crazy thought: why not just implement conditionals? We had a
proto-spec for them started at one point...
I didn't know that was on the table :)
How about we support YAQL expressions? https://github
I'd be happy to donate a Go To Meeting for the session, if desired. Not
sure if / how it is better than Google Hangout. I know we can get GTM's for
100's of participants. Not sure how many Google Hangout can support, with
something like slide sharing occuring. Anyway, let me know if you'd like me
t
On 11/11/2014 04:48 PM, Louis Taylor wrote:
> On Tue, Nov 11, 2014 at 01:46:34PM +, Gary Kotton wrote:
>> In order to enforce our translation policies -
>> http://docs.openstack.org/developer/oslo.i18n/guidelines.html - we have added
>> a hacking rule in Neutron. If you wish to jump aboard this
Hi folks,
I'd like to propose Sergey to sahara-core. He's made a lot of work on
different parts of Sahara and he has a very good knowledge of codebase,
especially in plugins area. Sergey has been consistently giving us very
well thought out and constructive reviews for Sahara project.
Sahara c
Hi folks,
I'd like to propose Michael McCune to sahara-core. He has a good knowledge
of codebase and implemented important features such as Swift auth using
trusts. Mike has been consistently giving us very well thought out and
constructive reviews for Sahara project.
Sahara core team members,
Hi folks,
I'd like to ask you for feedback on design summit sessions and Friday's
meetup. If you have any questions, suggestions, etc, please, write them
here. It will definetly help us make next summit better.
Thanks.
--
Sincerely yours,
Sergey Lukjanov
Sahara Technical Lead
(OpenStack Data
On Tue, Nov 11, 2014 at 10:50 AM, Thierry Carrez wrote:
> Kyle Mestery wrote:
>> Apologies for the delay in announcing the Neutron mid-cycle, but I was
>> confirming the details up until last night. I've captured the details
>> on an etherpad here [1]. The dates are December 8-10
>> (Monday-Wednes
Since a bunch of people had been asking at the Summit, and bunch of
them were interested in contributing, it seemed like a good idea to
put together some status on where the OpenStack SDK project is at.
What follows is the status section of a larger blog post on the SDK at
the Summit, available at
+ 2
On 11/11/2014 12:37 PM, Sergey Lukjanov wrote:
Hi folks,
I'd like to propose Michael McCune to sahara-core. He has a good
knowledge of codebase and implemented important features such as Swift
auth using trusts. Mike has been consistently giving us very well
thought out and constructive
+2
On 11/11/2014 12:35 PM, Sergey Lukjanov wrote:
Hi folks,
I'd like to propose Sergey to sahara-core. He's made a lot of work on
different parts of Sahara and he has a very good knowledge of
codebase, especially in plugins area. Sergey has been consistently
giving us very well thought out
+1, summary?
On Tue, Nov 11, 2014 at 3:31 AM, Igor Cardoso wrote:
> Hello Sumit.
> Unfortunately I could not go to the round table meeting, sorry for the
> absence.
> Did you talk about traffic steering? Is there some place or etherpad with
> a summary of what was discussed/outlined?
>
> Cheers,
On Tue, Nov 11, 2014 at 9:49 AM, Gregory Lebovitz
wrote:
> +1, summary?
>
> On Tue, Nov 11, 2014 at 3:31 AM, Igor Cardoso wrote:
>>
>> Hello Sumit.
>> Unfortunately I could not go to the round table meeting, sorry for the
>> absence.
>> Did you talk about traffic steering? Is there some place or
Excerpts from Alexis Lee's message of 2014-11-10 09:34:13 -0800:
> Zane Bitter said on Fri, Nov 07, 2014 at 12:35:09AM +0100:
> > Crazy thought: why not just implement conditionals? We had a
> > proto-spec for them started at one point...
>
> I didn't know that was on the table :)
>
> How about w
+2
Regards,
Alexander Ignatov
> On 11 Nov 2014, at 20:47, Trevor McKay wrote:
>
> + 2
>
> On 11/11/2014 12:37 PM, Sergey Lukjanov wrote:
>> Hi folks,
>>
>> I'd like to propose Michael McCune to sahara-core. He has a good knowledge
>> of codebase and implemented important features such as S
+2
Regards,
Alexander Ignatov
> On 11 Nov 2014, at 20:47, Trevor McKay wrote:
>
> +2
>
> On 11/11/2014 12:35 PM, Sergey Lukjanov wrote:
>> Hi folks,
>>
>> I'd like to propose Sergey to sahara-core. He's made a lot of work on
>> different parts of Sahara and he has a very good knowledge of
On 11/11/2014 01:12 PM, Clint Byrum wrote:
> Excerpts from Alexis Lee's message of 2014-11-10 09:34:13 -0800:
>> Zane Bitter said on Fri, Nov 07, 2014 at 12:35:09AM +0100:
>>> Crazy thought: why not just implement conditionals? We had a
>>> proto-spec for them started at one point...
>>
>> I didn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Forwarding to openstack-dev since openstack-stable-maint is now read-only.
- Forwarded Message
Subject:Re: [Openstack-stable-maint] Neutron backports for security
group performance
Date: Tue, 11 Nov 2014 09:25:43 -0800
Fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Personally, I think that enough information was provided to show that
the 1st fix is critical to successful deployment of neutron without
wasting nodes. I will vote +1 for now and wait for my fellow stable
maintainers to give their feedback.
As for
+2
Andrew.
On Tue, Nov 11, 2014 at 9:37 AM, Sergey Lukjanov
wrote:
> Hi folks,
>
> I'd like to propose Michael McCune to sahara-core. He has a good
> knowledge of codebase and implemented important features such as Swift auth
> using trusts. Mike has been consistently giving us very well thoug
+2
Andrew.
On Tue, Nov 11, 2014 at 9:35 AM, Sergey Lukjanov
wrote:
> Hi folks,
>
> I'd like to propose Sergey to sahara-core. He's made a lot of work on
> different parts of Sahara and he has a very good knowledge of codebase,
> especially in plugins area. Sergey has been consistently giving
On 11/11/2014 12:35 PM, Sergey Lukjanov wrote:
Hi folks,
I'd like to propose Sergey to sahara-core. He's made a lot of work on
different parts of Sahara and he has a very good knowledge of codebase,
especially in plugins area. Sergey has been consistently giving us very
well thought out and con
On 11/11/2014 12:37 PM, Sergey Lukjanov wrote:
Hi folks,
I'd like to propose Michael McCune to sahara-core. He has a good
knowledge of codebase and implemented important features such as Swift
auth using trusts. Mike has been consistently giving us very well
thought out and constructive reviews
Regarding blueprint to register event listeners to notify client
applications on state changes (
https://blueprints.launchpad.net/mistral/+spec/mistral-event-listeners-http),
I want to propose the following.
1. Refer this feature as event subscription instead of callback
2. Event subscription supp
We had a great discussion on cells at the summit which is captured at
https://etherpad.openstack.org/p/kilo-nova-cells. One of the tasks we
agreed upon there was to form a subgroup to co-ordinate this effort and
report progress to the Nova meeting regularly. To that end I would like
to find a
On 11/11/14 13:34, Ryan Brown wrote:
I am strongly against allowing arbitrary Javascript functions for
complexity reasons. It's already difficult enough to get meaningful
errors when you up your YAML syntax.
Agreed, and FWIW literally everyone that Clint has pitched the JS idea
to thought
I think it would also be interesting to hear for the Keystone folks that
are interested in attending OSSG and/or Barbican. A few people have told
me they found the Keystone/Barbican overlap for the last mid-cycle to be
helpful, so it might be worthwhile doing again.
-Doug M.
On Wed, Nov 12, 2014 at 1:35 AM, Alexis Lee wrote:
> Alexis Lee said on Mon, Nov 10, 2014 at 05:34:13PM +:
> > How about we support YAQL expressions? https://github.com/ativelkov/yaql
> > Plus some HOFs (higher-order functions) like cond, map, filter, foldleft
> > etc?
>
> We could also use Y
Hi, Winson,
This is great!
But I have a question:
> 9. Operation in python-mistralclient to re-publish events for a given
> workflow execution (in case where client applications was downed and need
> the data to recover).
How does Mistral know about all the events which it has already sent to
s
On Tue, Nov 11, 2014 at 3:30 PM, Douglas Mendizabal <
douglas.mendiza...@rackspace.com> wrote:
> I think it would also be interesting to hear for the Keystone folks that
> are interested in attending OSSG and/or Barbican.
We did record some of our plans for the Keystone mid-cycle meetup during
o
On 11/11/2014 3:04 PM, Andrew Laski wrote:
We had a great discussion on cells at the summit which is captured at
https://etherpad.openstack.org/p/kilo-nova-cells. One of the tasks we
agreed upon there was to form a subgroup to co-ordinate this effort and
report progress to the Nova meeting reg
On 11/11/2014 3:50 PM, Matt Riedemann wrote:
On 11/11/2014 3:04 PM, Andrew Laski wrote:
We had a great discussion on cells at the summit which is captured at
https://etherpad.openstack.org/p/kilo-nova-cells. One of the tasks we
agreed upon there was to form a subgroup to co-ordinate this ef
> On Nov 11, 2014, at 1:45 PM, Lance Bragstad wrote:
>
>
>
> On Tue, Nov 11, 2014 at 3:30 PM, Douglas Mendizabal
> mailto:douglas.mendiza...@rackspace.com>>
> wrote:
> I think it would also be interesting to hear for the Keystone folks that
> are interested in attending OSSG and/or Barbican.
On 11/11/2014 3:51 PM, Matt Riedemann wrote:
On 11/11/2014 3:50 PM, Matt Riedemann wrote:
On 11/11/2014 3:04 PM, Andrew Laski wrote:
We had a great discussion on cells at the summit which is captured at
https://etherpad.openstack.org/p/kilo-nova-cells. One of the tasks we
agreed upon the
Recent recurrence of the "Why ios everything on its own port" question
triggered my desire to take this pattern and put it to rest.
My suggestion, from a while ago, was to have a naming scheme that
deconflicts putting all of the services onto a single server, on port 443.
I've removed a lot o
For those who don't know 100% of guys behind YAQL are also active OpenStack
contributors. During (early) Kilo cycle we plan to release YAQL version 1.0
on stackforge. This release is going to fix some flaws in early versions,
add some more flexibility and have very high UT coverage. There are at
le
On 11/11/14, 16:35, "Adam Young" wrote:
>Recent recurrence of the "Why ios everything on its own port" question
>triggered my desire to take this pattern and put it to rest.
>
>My suggestion, from a while ago, was to have a naming scheme that
>deconflicts putting all of the services onto a single
I have submitted the first patch which focuses on the initial refactor of
pbr.packaging module.
https://review.openstack.org/#/c/133607/
With that change I have created the following modules:
pbr
common
git
requirements
cmds (package)
build_doc
egg_info
in
Hi, I have one patch pending, so the tests for the version calculation
and the version.py module itself are all that you need to care for, to
avoid conflicts.
-Rob
On 12 November 2014 11:54, Kenny Jones wrote:
> I have submitted the first patch which focuses on the initial refactor of
> pbr.pack
On 12 November 2014 09:47, Ian Cordasco wrote:
> On 11/11/14, 16:35, "Adam Young" wrote:
>
> >Recent recurrence of the "Why ios everything on its own port" question
> >triggered my desire to take this pattern and put it to rest.
> >
> >My suggestion, from a while ago, was to have a naming scheme
> On Nov 10, 2014, at 4:30 PM, Angus Salkeld wrote:
>
> Hi all
>
> I just wanted to make sure we are all under the same understanding of the
> outcomes and what the next steps for the versioned objects session are.
>
> 1. There is a lot of interest in other projects using oslo versioned objec
On 11 November 2014 22:35, Adam Young wrote:
> Recent recurrence of the "Why ios everything on its own port" question
> triggered my desire to take this pattern and put it to rest.
>
> My suggestion, from a while ago, was to have a naming scheme that
> deconflicts putting all of the services onto
I am trying to pin down a location for our mid-cycle meetup, I need to get an
idea of who will be joining us at the Keystone meetup. I’ve included a couple
questions relating to Barbican in the case we can double-up and have a day of
overlap like the Juno meetup. I apologize for the delay, this
I have set up a doodle poll to let folk enter their preferred times. It's
in UTC/GMT (/London time, because doodle) so use something like
http://everytimezone.com/ to figure that out :)
https://doodle.com/47h3f35nad62ncnf
Richard
On 11 November 2014 18:46, Matthias Runge wrote:
> On 11/1
1 - 100 of 117 matches
Mail list logo