18:01:04 <SergeyLukjanov> #startmeeting savanna
18:01:05 <openstack> Meeting started Thu Mar 28 18:01:04 2013 UTC.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:06 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:01:08 <openstack> The meeting name has been set to 'savanna'
18:02:41 <ogelbukh> o/
18:03:15 <rnirmal> hi there
18:04:33 <rnirmal> is this the standard meeting time for savanna ? I'm hoping to participate starting today
18:04:44 <dmitryme2> #info Ok folks, I believe we can begin today's meeting
18:05:16 <dmitryme2> rnirmal: you are right
18:05:17 <SergeyLukjanov> rnirmal, yes, we held this meeting weekly at this time
18:05:27 <rnirmal> cool thanks
18:05:31 <dmitryme2> Let's start with agenda
18:05:46 <dmitryme2> First come some news
18:06:22 <dmitryme2> We've implemented basic validation for cluster and node-templates create operations
18:06:38 <dmitryme2> 2. we move our repo to stackforge, now you can create CRs and Jemkins will run all tests
18:06:56 <dmitryme2> 3. latest master tarball is available at http://tarballs.openstack.org/savanna/
18:07:15 <dmitryme2> 4. we are working on improving code coverage with unit testing
18:07:25 <dmitryme2> 5. we are working on HowToContribute document
18:07:48 <dmitryme2> 6. horizon is ready to be published, some final preparations are yet to be done
18:08:20 <dmitryme2> These are all the news for that week
18:08:58 <Brad_K> SergeyLukjanov: thanks for the reminder!
18:09:27 <SergeyLukjanov> Brad_K, you're welcome :)
18:09:27 <dmitryme2> I don't have much to say about input validation, we just have some now :-)
18:10:04 <dmitryme2> first step to be user-friendly
18:10:15 <SergeyLukjanov> As for about moving our repo to StackForge, we finalized it and now anyone can easily contribute
18:10:23 <SergeyLukjanov> to Savanna
18:11:18 <SergeyLukjanov> #info Savanna lives now on http://github.com/stackforge/savanna
18:12:32 <SergeyLukjanov> one more interesting thing - now you can install savanna using pip
18:12:40 <SergeyLukjanov> and our latest master branch tarball
18:13:01 <SergeyLukjanov> just exec pip install http://tarballs.openstack.org/savanna/savanna-master.tar.gz\#egg\=savanna :)
18:13:44 <SergeyLukjanov> unfortunately, config files should be manually created
18:14:38 <dmitryme2> we've started to work on tests and want to complete the work on the next week
18:15:26 <dmitryme2> that is the necessary part to allow other folks build and change the project
18:16:34 <dmitryme2> another part is HowToContribute document
18:18:30 <dmitryme2> Currently you can test the project and file bugs on the launchpad
18:19:20 <dmitryme2> it would be great if the project is tested on different OpenStack setups
18:19:39 <dmitryme2> right now we test it in our lab only
18:20:44 <dmitryme2> Probably you've seen our Horizon pages in the screencast
18:21:07 <dmitryme2> we're going to share the them pretty soon so you can try it live
18:21:35 <SergeyLukjanov> one more interesting point
18:21:58 <SergeyLukjanov> #info we start using hacking.py to check code style
18:23:11 <dmitryme2> Regarding our plans for the next week
18:23:26 <dmitryme2> we already coverd couple of items in agenda:
18:23:44 <dmitryme2> 1. Publish HowToContribute doc
18:23:53 <dmitryme2> 2. publish Horizon
18:24:49 <dmitryme2> 3. Make a build which we'll call the alpha version
18:25:37 <SergeyLukjanov> we are planning to publish this build to the pypi
18:26:07 <Brad_K> cool!
18:27:38 <nkonovalov> as for horizon, we have added new wizards for node template creating
18:29:17 <nkonovalov> there are few minor steps to take before we can publish it, just to make sure all feachures of rest api are available from openstack dashboard
18:29:45 <SergeyLukjanov> #info planing to publish custom Horizon at the next week
18:30:07 <dmitryme2> And I believe that is pretty all for agenda
18:30:42 <Brad_K> sounds like you folks have done a lot of work!
18:31:43 <dmitryme2> thanks Brad :-)
18:32:04 <dmitryme2> people, maybe you do have basic questions about our product
18:32:12 <Brad_K> Sometimes I cringe a bit for the pip and pypi folks, though.  but i guess those are good problems to have.  ;-)
18:32:21 <dmitryme2> we've ready to answer them all
18:33:09 <SergeyLukjanov> #link http://savanna.mirantis.com Savanna project site with arch / docs / api and etc.
18:33:35 <SergeyLukjanov> additionally, tarballs will be published
18:33:41 <dmitryme2> Brad, well, all openstack projects use pypi and pip
18:35:17 <dmitryme2> we have a pain right now - it is how to write our own python client
18:36:02 <Brad_K> dmitryme2: i know, but still i look at what some of you folks are doing, and as a member of the python.org postmaster team, sometimes I still cringe a bit.  but then, growth is good — yes?
18:36:13 <YorikSar> dmitryme2: for most of OS projects only clients are on PyPI.
18:36:32 <Brad_K> SergeyLukjanov: i don't suppose you've looked at creating binary packages for various platforms?
18:37:29 <dmitryme2> Brad, you're right, we didn't
18:37:46 <dmitryme2> I believe it is not a blocker
18:38:03 <SergeyLukjanov> Brad_K, we are thinking about it, but we have no plans to build binary packages now
18:38:32 <SergeyLukjanov> as for about client, it'll be great if anyone have ideas about how to create pretty good python-savannaclient :)
18:39:14 <Brad_K> for now, i would agree with you — continue to focus on development.  but keep this in mind once you're ready to open things up to a wider audience, including folks who are more operations-oriented than being developers.
18:39:32 <Brad_K> don't do anything before it makes sense to do it, of course.
18:39:55 <SergeyLukjanov> we have take a look on different clients of OpenStack components
18:40:19 <SergeyLukjanov> but there is no common pattern in them
18:40:37 <SergeyLukjanov> and our goal is to understand how it should looks like
18:41:04 <SergeyLukjanov> I mean architecture, functionality, etc
18:44:35 <Brad_K> it seems to me that there are two parts to this problem.  one part is to have the tool fit correctly into the overall architecture of OpenStack, and I think that the core developers might be better placed to answer that part of the question.  As for what would make sense from the community side (and how people would like to interact with the tool), it's been my experience that you usually won't get much feedback until you actually put s
18:45:24 <Brad_K> from that point, if you're doing proper agile development, you should be able to quickly remove or reshape the worst offending parts, and then put out the next iteration.
18:47:21 <dmitryme2> Brad: we took our chance if there is a core developer here right now
18:50:21 <Brad_K> i don't blame you for trying, but i fear that you may have to more actively reach out to the core developers that you want to try to draft in as your advisors/mentors.
18:52:28 <dmitryme2> Folks, do you have more questions?
18:52:42 <dmitryme2> If not, I guess it is about time to end our meeting
18:53:16 <SergeyLukjanov> JFYI you can always use savanna-all@lists.launchpad.net mailing lists and #savanna irc channel to find us and ask your questions
18:53:29 <SergeyLukjanov> #endmeeting