> you feel that your focus has shifted away from TripleO and you'd no
> longer like to serve on the core team, please let me know.
>
> I also plan to remove Alexis Lee from core, who previously has
> expressed that he'd be stepping away from TripleO for a while. Alex
palatable.
>
> +1, I don't have a strong preference, but an hour later would make it a
> bit easier, particularly when DST kicks in.
>
> Dougal
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
>
r interested kibbitzers, please +1 / -1 as you feel fit :)
>
> -Rob
>
I like it, +1.
> --
> Robert Collins
> Distinguished Technologist
> HP Converged Cloud
>
> ___
> OpenStack-dev mailing list
ole or add GET
/v2/roles/:role_uuid endpoint and add this kind of links to list of
roles too.
I proposed solutions to points 1, 2 and 3 in
https://review.openstack.org/#/c/109040/.
Thanks for reading this.
I am looking for your input.
--
Petr Blaho, pbl...@redhat.com
Software Engin
-1s for silly
> things. :)
>
> -Sean
>
> --
> Sean Dague
> http://dague.net
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.open
an/listinfo/openstack-dev
Hi,
we already have gerritbot posting to #tripleo channel w/r/t patches in
tuskar (as for all tripleo repos).
And I think that we should talk on one common channel, ie #tripleo.
+1 for abandoning #tuskar channel.
--
Petr Blaho, pbl...@redhat.com
Software Engineer
_
t Collins
> Distinguished Technologist
> HP Converged Cloud
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
+1 for tripleo-spec repo
I like the idea of dedi
gt; Thoughts?
>
> Thanks.
>
> -Ben
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
&g
ll need to continue to support the non-FHS paths for at least a few
> releases as well.
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Petr B
On Mon, Mar 03, 2014 at 09:19:34AM +0100, Radomir Dopieralski wrote:
> On 27/02/14 11:52, Petr Blaho wrote:
>
> > I agree with you w/r/t to indirection when accessing data but I like the
> > idea that when I look at json repsonse I see what type of resource it
> >
ever, the API doesn't
> appear to support that, so just looking at the examples given it looks
> like an added layer of depth that carries no extra information and makes
> using the returned result a bit awkward IMO.
>
I did not think about aggregate APIs before... inter
n from
http://api.openstack.org/api-ref-telemetry.html [most values ommited])
Tuskar API now uses "without namespace" variant.
By looking at API docs at http://api.openstack.org/ I can say that
projects use both ways, altought what I would describe as "nicer API"
ar.
+1
>
> >
> > Imre
> >
> > ___
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
> ___
On Fri, Oct 18, 2013 at 11:30:48AM -0400, Sean Dague wrote:
> On 10/17/2013 08:12 AM, Petr Blaho wrote:
> > Hi all,
> >
> > this is probably 3rd or 4th time in quite short time when we were bitten
> > by new version of some out dependencies.
> >
> > Last one
ask and if I miss a good side of these
"sudden version strikes" too.
Thanks
--
Petr Blaho, pbl...@redhat.com
Software Engineer
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
is way core reviewers group will shrink till its members feel that
they have just enough reviews on their agenda that it does not hinder
quality of their work.
This will not eliminate any "competition" for core membership but it
will eliminate immediate impact on projects'
Maybe I missed something or I see this bigger than it really
is or I am totally out :-)
--
Petr Blaho, pbl...@redhat.com
Software Engineer
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
d to follow in the upcoming months:
>
> 1. get things stable and robust enough to demo in Hong Kong on real hardware
> 2. include metrics and monitoring
> 3. security
>
> What do you think?
+1
>
> Tomas
>
> _______
&g
18 matches
Mail list logo