Thanks Dev. Done. > -----Original Message----- > From: devdatta kulkarni [mailto:devdatta.kulka...@rackspace.com] > Sent: Monday, February 10, 2014 12:59 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Solum] Milestone 1 End to end scenario > > Hi Roshan, > > Great to see the big picture that we are targeting. > Some minor comments/suggestions: > > 1) It will be helpful to explicitly call out in the first step that the git > repositories are not > hosted by Solum but are public repositories on github.com > > 1) In step 3, what do you mean by 'automatic' deployment? I would suggest > we remove that word. > > 2) It will help if we use two different terms to identify the end users of an > application > and the developer of an application. > > In the line 'Only authorized users .. access the service', I think you mean > 'only application > developers who are also registered with Solum will be able to access > the Solum API service'. In its current form it is not clear whether 'users' > refer to > developers or application users and whether 'service' refers to solum API > or > the running application. > Similarly in the last line the last word can be changed from 'user' to 'API > user'. > > Thanks, > Devdatta > > > -----Original Message----- > From: "Roshan Agrawal" <roshan.agra...@rackspace.com> > Sent: Monday, February 10, 2014 12:28pm > To: "openstack-dev@lists.openstack.org" <openstack- > d...@lists.openstack.org> > Subject: [openstack-dev] [Solum] Milestone 1 End to end scenario > > It is exciting to see we are getting close to delivering the first end to end > use > case for Solum ! > > Though we have blueprints to track individual work items for Milestone 1, it > is > useful to have a view into exactly what end to end experience we will be > delivering. I have made an attempt at documenting that, and linked to the > Solum High Level Roadmap wiki: > > https://wiki.openstack.org/wiki/Solum/Milestone1 > > The goal is not to have a comprehensive listing of all features delivered in > M1, but rather to summarize in a few lines the desired outcome from a user > perspective. > > Comments, suggestions welcome. > > > _______________________________________________ > 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
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev