We have been making some progress on improvements to the Community App
Catalog, but this last month things have slowed down some. I wanted
to send a note to the mailing list to get a conversation going about
what we need to get on the roadmap, and hopefully get some folks
committed to helping out.
(Apologies for the re-send, missed the appropriate tag on the subject line!)
Hello! Our next OpenStack App Catalog meeting will take place this
Thursday July 16th at 17:00 UTC in #openstack-meeting-3
The agenda can be found here:
https://wiki.openstack.org/wiki/Meetings/app-catalog
Please add ag
Hello! Our next OpenStack App Catalog meeting will take place this
Thursday July 16th at 17:00 UTC in #openstack-meeting-3
The agenda can be found here:
https://wiki.openstack.org/wiki/Meetings/app-catalog
Please add agenda items if there's anything specific you would like to
discuss. For this w
Unless there are any specific agenda items anyone else wishes to
discuss tomorrow during the weekly App Catalog IRC meeting, I propose
we push this off until next week.
Please do speak up here on the mailing list or on the IRC channel
(#openstack-app-catalog) if there is anything you would like co
Thanks as always to those of you joining in the conversation regarding
the App Catalog. We are working on building a Horizon plugin right
now which will allow operators to include a browsable/searchable pane
of catalog contents (fetched from http://apps.openstack.org, or your
own local version of
Hello! Our next OpenStack App Catalog meeting will take place this
Thursday July 2nd at 17:00 UTC in #openstack-meeting-3
The agenda can be found here:
https://wiki.openstack.org/wiki/Meetings/app-catalog
Please add agenda items if there's anything you would like to discuss.
We'll touch on the wo
On Fri, Jun 26, 2015 at 8:17 AM, Gregory Haynes wrote:
> Hello TripleOers,
>
> At the last mid-cycle we briefly discussed whether we should have
> separate groups for tripleo and DIB core and decided it wasn't
> necessary. I would like to revisit that topic.
>
> It seems clear to me that we have s
Thank you to those who joined in the conversation today, I thought it
was pretty productive. Today we focused on two things - creating a
Horizon plugin that would allow for browsing and consuming catalog
contents, and expanding the catalog framework to accommodate more
asset types[1]. In the shor
Hi! Our next OpenStack App Catalog meeting will take place this
Thursday June 25th at 17:00 UTC in #openstack-meeting-3
The agenda can be found here:
https://wiki.openstack.org/wiki/Meetings/app-catalog
Please add agenda items if there's anything you would like to discuss.
One important topic we'
Thanks to all who joined the meeting this week. After the
announcements we had a really good conversation and touched on a few
important topics, and there's a lot more to discuss as we work through
putting together our near-term roadmap.
In addition to the topics noted in the log, we're already s
This makes sense to me too, and I feel like Kevin captures the flow I
imagine for an app. Considering the point of the app catalog is to
showcase what you can do with an OpenStack environment, if a Solum LP
can be grabbed from the catalog and results in them just needing to
add some information fo
On Wed, Jun 17, 2015 at 12:53 PM, Murali Allada
wrote:
> Kevin\Keith,
>
> Yes, we would like to use the catalog for globally available artifacts, such
> as operator languagepacks. More specifically the catalog would be a great
> place to store metadata about publicly available artifacts to make
Hello!
The OpenStack App Catalog meeting will take place this Thursday June
18th at 17:00 UTC in #openstack-meeting-3
Meeting agenda can be found here:
https://wiki.openstack.org/wiki/Meetings/app-catalog
Please add agenda items, as this is just a quick first pass, I have a
feeling we'll have ple
On Wed, Jun 10, 2015 at 3:41 PM, Christopher Aedo wrote:
> I think it makes sense (as James suggested) for us to set up an
> additional mailing list for this, unless Zuul can just send the output
> to core reviewers?
As JEREMY/fungi suggested I mean :/
Let me know if zuul is able to
On Sat, Jun 6, 2015 at 7:15 AM, Georgy Okrokvertskhov
wrote:
> This is great. It means that we can use existing OpenStack approach rather
> then reinventing the wheel.
> I think I will be able to create a simple script for URLs verification. It
> looks pretty straightforward as catalog is in machi
On Mon, Jun 8, 2015 at 4:47 AM, Serg Melikyan wrote:
> We found few issues with images used by murano application and we
> would like to update them. What is procedure for updating existing
> images/apps hosted on storage.apps.openstack.org?
This question hits on some really important points:
-T
I’ve started a doodle poll to vote on the initial IRC meeting
schedule, if you’re interested in helping improve and build up this
catalog please vote for the day/time that works best and get involved!
http://doodle.com/vf3husyn4bdkui8w
The poll will close in one week (June 5). Just sending this r
On Fri, May 29, 2015 at 9:55 AM, Fox, Kevin M wrote:
> As an Op, I really
> really want to replace one image with a new one atomically with security
> updates preapplied. Think shellshock, ghost, etc. It will be basically be
> the same exact image as before, but patched.
On Fri, May 29, 2015 at 1
This thread is awesome :) I love the conversation we've kicked off,
and it's touching on all the considerations we had in mind when we put
this together to begin with.
Regarding vision: I agree with a lot of what Monty, Kevin (and others)
have said. For me, what I want to see is the pace to go f
Rackspace).
-Christopher
On Wed, May 27, 2015 at 12:26 PM, Jeremy Stanley wrote:
> [Operators ML dropped from Cc as my reply is off-topic there]
>
> On 2015-05-22 21:06:32 -0700 (-0700), Christopher Aedo wrote:
> [...]
>> - I'll be working with the OpenStack infra team to get
On Tue, May 26, 2015 at 9:22 PM, Keith Bray wrote:
> I am interested in getting more involved. Is there any effort already in
> place to run this like a regular project, with IRC meetings, etc.? What
> are the channels, etc., by which I can get involved.
Keith, glad to hear it!
You can referen
join us via IRC at #openstack-app-catalog on freenode.
Our initial core team is Christopher Aedo, Tom Fifield, Kevin Fox,
Serg Melikyan.
I’ve started a doodle poll to vote on the initial IRC meeting
schedule, if you’re interested in helping improve and build up this
catalog please vote for the day
[Cross-posting to both dev and operators list because I believe this
is important to both groups]
For those of us who have been working on the OpenStack Community App
Catalog (http://apps.openstack.org) yesterday was really exciting. We
had a chance to do a quick demo and walk through during they
The openstack-dev list is primarily intended to be used for OpenStack
development discussions and planning, rather than dealing with
operational/usage questions. Your best place to start is
http://ask.openstack.org if you can't find the answer in our excellent
docs (http://docs.openstack.org/).
-
The openstack-dev list is primarily intended to be used for OpenStack
development discussions and planning, rather than dealing with
operational/usage questions. Your best place to start is
http://ask.openstack.org if you can't find the answer in our excellent
docs (http://docs.openstack.org/).
-
On Wed, Apr 29, 2015 at 5:20 AM, Kamsali, RaghavendraChari (Artesyn)
wrote:
> · Why devstack didn’t start services automatically when openstack
> nodes reboots.
>
> · How to re-create the devstack, suchthat whenever nodes reboot , it
> ‘ll configured as previous configuration (i.e
On Tue, Apr 28, 2015 at 2:56 PM, Jeremy Stanley wrote:
> On 2015-04-28 16:08:03 -0400 (-0400), Jay Pipes wrote:
>> Honestly, I see no problem with some helper bash scripts that
>> simplify life for new contributors.
>> [...]
>
> [...]
> I remember it happening regularly before we started begging p
On Mon, Apr 27, 2015 at 10:52 AM, Sean M. Collins wrote:
> Oh, I should actually mention which way I think we should go with.
>
> RegionOne should be the convention.
This came up in January[1][2] relating to case sensitivity in MySQL,
Keystone and TripleO, and there's a bug noted[3] as well.
I'm
On Thu, Apr 23, 2015 at 12:33 PM, Sean M. Collins wrote:
> The links for the developer documentation are currently broken.
I would bet the docs team is sorting out the broken link as I type
this, thanks for pointing it out! In the mean time it looks like the
docs on the wiki are up to date (or a
Note: Modifying the subject line to add the tag "Fuel" as this message
has gone out to the OpenStack Dev mailing list.
On Mon, Mar 30, 2015 at 10:50 AM, Eugene Bogdanov
wrote:
> Hello everyone,
>
> We currently have 500+ medium priority bugs assigned to 6.1 release.
> Obviously we won't be able t
+1 from me, this is a great suggestion.
-Christopher
On Wed, Mar 25, 2015 at 12:10 PM, Dmitry Borodaenko
wrote:
> Fuelers,
>
> I'd like to nominate Irina Povolotskaya for the fuel-docs-core team.
> She has contributed thousands of lines of documentation to Fuel over
> the past several months, an
Steve, thanks for sharing this - the decomposed blueprints are going
to make getting involved easy. Containerizing OpenStack services
looks like a great solution to the challenge of upgrades, and pace of
the work you and others on the Kolla team have kept up is impressive.
Regarding Fuel, we are n
Assaf, really good advice for getting started here.
Once you've absorbed the workings of the project you're interested in
contributing to, take a look here for guidelines on how to submit code
for review: https://wiki.openstack.org/wiki/How_To_Contribute
Also linked from that wiki page are more d
Adjusting fuel-web/docs to build ONLY the API and Objects reference is here:
https://review.openstack.org/147348
Meg should have the inclusion of fuel-web/docs content in fuel-docs tomorrow.
Once these two are done, we can sort out that last step:
>> And finally we will have CI job to publish fin
Ah, bad paste, sorry.
All the details around developing and certifying a plug-in can be found here:
http://docs.mirantis.com/openstack/fuel/fuel-6.0/plugin-dev.html
-Christopher
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://li
On Tue, Jan 6, 2015 at 7:00 AM, wrote:
> Actually there is two different fuel plugins git repositories. One in
> stackforge and the other in mirantis:
>
> https://github.com/stackforge/fuel-plugins
Stackforge plug-ins - used for plug-ins developed by Fuel Core team.
> https://github.com/Mirantis
On Tue, Jan 6, 2015 at 2:49 AM, Flavio Percoco wrote:
> Fully agree... I don't see how enable logging should be a limitation
> for freedom of thought. We've used it in Zaqar since day 0 and it's
> bee of great help for all of us.
>
> The logging does not remove the need of meetings where decisions
Ah I got it, I hadn't really considered how much more likely the
requirements are to change for nailgun and the other components that
should have auto-generated API docs. Having those build completely
separately matches OpenStack proper too - I'm on board now :) We can
work out the details over t
I think it's worth pursuing these efforts to include the
auto-generated doc components in the fuel-docs build process. The
additional dependencies required to build nailgun are not so
unreasonable, and the preparation of the build environment has already
been put into a single script,
>From the C
cases a lot of thought and consideration and I’d love to talk more
> about them (perhaps a small session in Paris would be possible).
>
> - Joe
>
> On Oct 17, 2014, at 4:18 AM, John Garbutt wrote:
>
>> On 17 October 2014 02:28, Matt Riedemann wrote:
>>>
>>>
On Tue, Sep 9, 2014 at 2:19 PM, Mike Scherbakov
wrote:
>> On Tue, Sep 9, 2014 at 6:02 PM, Clint Byrum wrote:
> The idea is not simply deny or hang requests from clients, but provide them
> "we are in maintenance mode, retry in X seconds"
>
>> You probably would want 'nova host-servers-migrate '
>
101 - 141 of 141 matches
Mail list logo
