]. If no one objects, I'll proceed and add him in a week
from now.
[1] http://stackalytics.com/report/contribution/zaqar-ui/90
+1, and thank you for your work on Zaqar's UI!
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc
to the team. If
no one objects, I'll proceed and add her in a week from now.
+1, cheers!
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions
at work and at play. If OpenStack pays your salary,
consider giving the tox/pytest team a slice.
Cheers,
Ryan
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List
) is something we can agree
API-WG both does and should care about.
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
On 02/05/2016 01:00 PM, Sean Dague wrote:
On 02/05/2016 12:16 PM, Ryan Brown wrote:
On 02/05/2016 09:08 AM, michael mccune wrote:
On 02/04/2016 12:57 PM, Hayes, Graham wrote:
On 04/02/2016 15:40, Ryan Brown wrote:
[snipped lots]
This isn't a perfect solution, but maybe instead
On 02/05/2016 09:08 AM, michael mccune wrote:
On 02/04/2016 12:57 PM, Hayes, Graham wrote:
On 04/02/2016 15:40, Ryan Brown wrote:
[snipped lots]
This isn't a perfect solution, but maybe instead of projects.yml there
could be a `registry.yml` project that would (of course) have all
functional as an openstack product chock-full of syntax errors
** Shed Cat Enterprise Leopard is strictly fictional, and not based on
any company that currently or ever has existed.
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
___
akes it easier
to use the different vendors of commodity services, and that's not a
reason to boot it.
Sidebar: I recall a few years ago that Rackspace's CDN offering was
based on Akamai, so read into that whatever you want I guess. They at
least used to have a relation with Akamai at some po
hear Everett's and Chris' opinions.
regards,
mike
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailm
On 01/27/2016 03:31 PM, Dean Troyer wrote:
On Wed, Jan 27, 2016 at 1:47 PM, michael mccune > wrote:
i am not convinced that we would ever need to have a standard on how
these names are chosen for the header values, or if we would even
need to
penstack to be "good" but they also have
deadlines to meet internally. Having a freeze upstream for stabilization
is going to put downstream development into overdrive, no doubt. That
would be a poor precedent to have set given where the bulk of
contributions come from.
--
Ryan Br
s to work. Its a hack, but
complies with HTTP standard.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/ma
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Developme
m what I understand of the Magnum architecture,
this is indeed true) then nesting them makes sense.
Of course, it's a big change and will have to be communicated to users &
client libraries, probably via a version bump.
--
Ryan Brown /
ions.
I am about to implement your nodes workflow in the GUI to test how it
works.
Jirka
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubs
mailman/listinfo/openstack-dev
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
On 01/12/2016 10:50 AM, Jiri Tomasek wrote:
On 01/12/2016 04:22 PM, Ryan Brown wrote:
On 01/12/2016 06:52 AM, Jiri Tomasek wrote:
On 01/11/2016 04:51 PM, Dan Prince wrote:
Background info:
We've got a problem in TripleO at the moment where many of our
workflows can be driven by the command
questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Develo
_____
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
--
Ryan Brown / Senior Software Engineer, O
?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
+1
+1
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions
e
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-de
cut all the logfiles down to size when the total size of your
log directory exceeds 1 GB. I have it set to run every 3 hours on my vms.
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mail
/
2:
http://specs.openstack.org/openstack/api-wg/guidelines/http.html#http-methods
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage quest
e projects.
Your thoughts?
Cheers,
Thomas Goirand (zigo)
P.S: It wasn't the point of this message, but do we have a fix for
designateclient? It'd be nice to have this fixed before Liberty is out.
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
be useful for heat.
A lot of boiler plate needed for locking and running centralized tasks
(such as timeout) will not be needed in heat. Given that we are moving
towards distribution of tasks and horizontal scaling is preferred, it
will be advantageous to use them.
Please share your thoughts.
- Anan
urces
|- events
|- services
I think versioning the public API is the way to go, since it will make
it easier to maintain backwards compatibility while new needs/uses evolve.
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
slow time.
Anybody else think this could be useful?
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
e:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Ryan Brown / Senior Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (no
On 08/27/2015 11:28 PM, Chen, Wei D wrote:
>
> I agree that return 400 is good idea, thus client user would know what
> happened.
>
+1, I think a 400 is the sensible choice here. It'd be much more likely
to help devs catch their errors .
--
Ryan Brown / Software Engineer, Opensta
repo is how does reviewing
work? are heat cores expected to also be cores on this new repo, or
maybe just take anything that gets 5 +1's?
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development
requests and execute the request
as normal.
Best,
-jay
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
OS::Zaqar::Queue is disabled on this cloud.
I'm not sure if validate currently makes that distinction, but it likely
should.
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List
darn near every service a module. It doesn't seem to be a valuable
distinction, and I know that within the heat team, we say service.
Do operators, users, or developers find this distinction useful? Calling
everything [blank] service seems like it'd be more consistent.
--
Ryan Brown / Software
/186436/
[2]: https://review.openstack.org/#/c/186555/
[3]: https://review.openstack.org/#/c/185822/
...[snip]...
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage
not messaging for OpenStack internally.
Good catch Clint,
Ryan
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
for the mail Flavio,
Ryan
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
Zaqar provides an option to use Redis as a backend, and Zaqar provides
pubsub messaging.
On 05/23/2015 03:09 PM, Todd Crane wrote:
Does anybody know of a way (either current projects or future plans)
to use Redis PubSub as the messaging system for OpenStack?
-Todd
--
Ryan Brown / Software
On 05/11/2015 04:18 PM, Everett Toews wrote:
I would like to propose Michael McCune (elmiko) as an API Working Group core.
Not core, but +1 from me!
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc
...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions
)
__
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
--
Ryan Brown / Software Engineer, Openstack
than logical. I imagine there are
others who are also nervous about that.
I don't think it tries to be magical, it tries to be developer
friendly by default, and lets your VCS handle versioning your
dependencies. It just so happens version control systems are great at that.
--
Ryan Brown
out at all.
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
nominal level of
somewhat unhelpful reviews so long as, when possible, we try to teach
those reviewers how they can be more helpful.
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing
would still love to hear more thoughts from folks in Australia/Asia
time zones to see if we can arrive at something that will accommodate
the most number of interested parties.
regards,
mike
I'd be more than happy with a 1200UTC-1300UTC meeting (I'm US-based).
--
Ryan Brown / Software Engineer
. Especially in a service like Zaqar where the vast
majority of usage isn't by humans in a web interface, the horizon bit
becomes mostly a dashboard/auditing/testing destination instead of a
primary interface.
[snip]
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc
pkg_resources
pkg_resources.get_distribution('nova').version
Where, of course, s/nova/any-package-name/
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions
-tenant cases, etc.
As someone who wants to adopt Zaqar, I'd really like to see it continue
as a project because it provides things other message broker approaches
don't.
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc
as-is to view those raw notifications, not just
the indexed k/v pairs?
In StackTach.v3 we ship the raw notifications to HDFS for archiving, but
expose the reduced event via the API. The message-id links the two.
Lots more here: http://www.stacktach.com
Thanks! I'll have to read up.
--
Ryan Brown
life more
complicated because that means pbr will obviously need to be added as
a runtime requirement for that package.
RDO actually patches out calls to pbr to avoid the runtime requirement,
FWIW.
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc
-replaced-resources, autoscaling actions, and info about stack errors.
Is there a way for users as-is to view those raw notifications, not just
the indexed k/v pairs?
Thanks,
Ryan
[1]: https://review.openstack.org/#/c/167793/
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc
it to tomorrow’s meeting. Can someone
else please #startmeeting?
Thanks, Everett
+1 for moving to only 16:00UTC
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List
I (and you) mentioned earlier.
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
, but there may be performance implications.
Since it's a soft requirement should we patch devstack to reflect that?
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List
for avoiding submodules.
What do you think about it? Please share your comments.
Best regards,
Pavlo Shchelokovskyy Software Engineer Mirantis Inc www.mirantis.com
http://www.mirantis.com
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc
with internal forks/patches - those will likely all have
to be redone too..
Ooof, that's huge. If we can configure it to be less aggressive I love
the *idea* of having everything formatted semantically, but that's a
pretty major burden for everyone involved.
--
Ryan Brown / Software Engineer, Openstack
that
is/isn't RFC compliant for clarity
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
__
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
--
Ryan
?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
Oops, sent this to openstack@ not openstack-dev@.
On 02/10/2015 04:52 PM, Ryan Brown wrote:
Heat team,
After looking at Zane's prototype[1] and the ML threads on SyncPoint, I
thought it'd be helpful to make a model of *just* the logic around
resource locking. Hopefully, it'll help during
/listinfo/openstack-dev
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
__
OpenStack Development Mailing List (not for usage
__
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
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc
-dev
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
larger (though the average flask
project seems pretty small).
I'm not sure what determines production readiness, but it seems to me
like Fuel developers fall more in Pecan's target audience than in Flask's.
My $0.02,
Ryan
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc
sensible way to add this would be to make timeout polling a
responsibility of the Observer instead of the engine.
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
On 11/12/2014 07:50 AM, Zane Bitter wrote:
On 12/11/14 06:48, Angus Salkeld wrote:
(it's nice that there would be a consistent user experience
between these projects -mistral/heat/murano).
It's actually potentially horrible, because you introduce potential
quoting issues when you embed
Javascript.
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
___
OpenStack-dev mailing list
OpenStack-dev
for this, and so I
think that using the version number is probably fine.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Ryan Brown / Software Engineer, Openstack
On 09/16/2014 09:49 AM, Ryan Brown wrote:.
(From Zane's other message)
snip
I think the first supported release is probably the right information
to add.
snip
I feel like for anything with nonzero upgrade effort (and upgrading your
openstack install takes significantly more than 0
particular itch, there's always gerrit-dash-creator[1] to help you make
one that fits your needs.
[1]: https://github.com/stackforge/gerrit-dash-creator
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
___
OpenStack-dev mailing list
results.
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
(or at least would receive private messages) and
OpenStack probably shouldn't take responsibility for keeping all those safe.
Just my 0.02 USD.
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
___
OpenStack-dev mailing list
OpenStack-dev
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 08/27/2014 12:15 PM, Kurt Griffiths wrote:
On 8/25/14, 9:50 AM, Ryan Brown rybr...@redhat.com wrote:
I'm actually quite partial to roles because, in my experience, service
accounts rarely have their credentials rotated more than once per eon.
Having the ability to let instances grab
://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
feature: A-B-...-C-D-...-E
snip
+1, this is definitely a feature I'd want to see.
Currently I run two branches bug/LPBUG#-local and bug/LPBUG# where
the local is my full history of the change and the other branch is the
squashed version I send out to Gerrit.
Cheers,
--
Ryan Brown / Software
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 driven
any benefit here.
Agreed
I'd actually be in favor of the change from rsrc-resource, I feel like
rsrc is a pretty opaque abbreviation.
--
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
___
OpenStack-dev mailing list
OpenStack-dev
80 matches
Mail list logo