Re: [openstack-dev] [Solum] Proposed changes to solum-core
+1 On Jan 24, 2014, at 5:35 PM, Adrian Otto adrian.o...@rackspace.com wrote: Solum Core Reviewers, I propose the following changes to solum-core: +asalkeld +noorul -mordred Thanks very much to mordred for helping me to bootstrap the reviewer team. Please reply with your votes. Thanks, Adrian ___ 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
Re: [openstack-dev] [Diesel] Proposal for new project
Hi Rob - there seems be overlap with project Solum. Can you please outline high level differences between Diesel and Solum? Raj Sent from my iPad On Jan 18, 2014, at 9:06 AM, Raymond, Rob rob.raym...@hp.com wrote: I would like to gauge interest in a new project named Diesel. https://wiki.openstack.org/wiki/Diesel If you are already familiar with Savanna, the best way to describe it is: Savanna is to map reduce applications as Diesel is to web applications. The mission of Diesel is to allow OpenStack clouds to run applications. The cloud administrator can control the non functional aspects, freeing up the application developer to focus on their application and its functionality. In the spirit of Google App Engine, Heroku, Engine Yard and others, Diesel runs web applications in the cloud. It can be used by cloud administrators to define the application types that they support. They are also responsible for defining through Diesel how these applications run on top of their cloud infrastructure. Diesel will control the availability and scalability of the web application deployment. Please send me email if you would like to collaborate on this and I can set up an IRC meeting. Rob Raymond ___ 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
Re: [openstack-dev] [Solum] git-Integration working group
From: Monty Taylor mord...@inaugust.com Sent: Friday, November 22, 2013 6:24 PM To: openstack-dev@lists.openstack.org; Adrian Otto Subject: Re: [openstack-dev] [Solum] git-Integration working group On 11/22/2013 05:37 PM, Krishna Raman wrote: Hello all, I would like to kickoff the Git integration discussion. Goal of this subgroup is to go through the git-integration blueprint [1] and break it up into smaller blueprints that we can execute on. We have to consider 2 workflows: 1) For Milestone 1, pull based git workflow where user uses a public git repository (possibly on github) to trigger the build 2) For later milestones, a push based workflow where the git repository is maintained by Solum Hi! I'm a little disappointed that we've decided to base the initial workflow on something that is not related to the world-class git-based developer tooling that the OpenStack project has already produced. We have a GIANT amount of tooling in this space, and it's all quite scalable. RR: Can you provide some pointers to the tooling / Workflow you suggesting? Thanks There is also the intent by 3 or 4 different groups to make it more re-usable/re-consumable, including thoughts in making sure that we can drive it from and have it consume heat. Devdatta has created 2 blueprints for consideration: [2] [3] I have set up a doodle to poll for a /recurring/ meeting time for this subgroup: http://doodle.com/7wypkzqe9wep3d33#table (Timezone support is enabled) Currently the plan is to try G+ hangouts to run this meetings and scribe on #solum. This will limit us to a max of 10 participants. If we have more interest, we will need to see how to change the meetings. We have IRC meeting channels for meetings. They are logged - and they have the benefit that they do not require non-Open Source software to access. If you have them in IRC, the team from OpenStack who is already working on developer workflow around git can potentially participate. I don't mean to be negative, but if you want to be a PaaS for OpenStack, I would strongly consider not using G+ when we have IRC, and I would strongly suggest engaging with the Infra projects that already know how to do git-based workflow and action triggering. ___ 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
Re: [openstack-dev] [Solum]: Welcome to the community site for Solum !!
Looks great, Roshan. Please let us know if you need any help with content for the site. Raj From: Roshan Agrawal roshan.agra...@rackspace.com Sent: Monday, November 04, 2013 5:25 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Solum]: Welcome to the community site for Solum !! The community site for Solum has gone live! www.Solum.iohttp://www.Solum.io - this is a landing page for all things Solum related. Also check out the blog section on the site. The logo: is a placeholder for now. We are working on a cool new logo - but the placeholder right now isn't too bad either, is it? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Solum] Create a source repo for the API specification?
+1 Couldn't agree more. Christopher Armstrong chris.armstr...@rackspace.com wrote: On Sat, Nov 2, 2013 at 4:39 PM, Jay Pipes jaypi...@gmail.commailto:jaypi...@gmail.com wrote: Hi all, One of the most important aspects in the early stages of Solum development will be the consensus building and stabilization of the Solum API specification. A solid API spec aid in the speeding up the pace of innovation in the Solum contributor community. One of the aspects of the Keystone development process that I think is a big benefit is the separate source repository that stores the OpenStack Identity API specifications: https://github.com/openstack/identity-api When new versions of the API specification are debated or new extensions are proposed, patches are made to the specification markdown documents and reviewed in the exact same manner that regular code is on the https://review.openstack.org Gerrit site. Contributors are free to annotate the proposed changes to the API specification in the same way that they would make inline code comments on a regular code review. Here's an example for a proposed change that I recently made: https://review.openstack.org/#/c/54215/10 I'd like to propose that Solum do the same: have a separate source repository for the API specification. Thoughts? -jay I like this idea. I'd also propose that the format of the specification be something machine-readable, such as API-Blueprint (a simple subset of markdown, apiblueprint.orghttp://apiblueprint.org, also what apiary uses, if you've ever seen that) or RAML (a more structured YAML-based syntax, raml.orghttp://raml.org). API-Blueprint is closer to what the keystone document uses. Making the documentation machine-readable means that it's much easier to verify that, in practice, the implementation of an API matches its specification and documentation, which is a problem that plagues many OpenStack projects right now. -- IRC: radix Christopher Armstrong Rackspace ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
