Also, if we decided to continue development we should add blazar here [1] according to the email [2] So, my suggestion is to setup some timeframe on this week or next week and hold some kind of meeting. [1]: https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement [2]: http://lists.openstack.org/pipermail/openstack-dev/2015-August/073071.html
Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2015-09-01 12:42 GMT+03:00 Nikolay Starodubtsev <nstarodubt...@mirantis.com> : > Sylvain, > First of all we need to reanimate blazar gate-jobs, or we can't merge > anything. I tried to do it a year ago, but can't get the point of the tests, > so better decision can be to rewrite them from scratch. > > > > Nikolay Starodubtsev > > Software Engineer > > Mirantis Inc. > > > Skype: dark_harlequine1 > > 2015-09-01 11:26 GMT+03:00 Sylvain Bauza <sba...@redhat.com>: > >> >> >> Le 01/09/2015 06:52, Nikolay Starodubtsev a écrit : >> >> All, >> I'd like to propose use of #openstack-blazar for further communication >> and coordination. >> >> >> >> +2 to that. That's the first step of any communication. The channel logs >> are also recorded here, for async communication : >> http://eavesdrop.openstack.org/irclogs/%23openstack-blazar/ >> >> I don't see at the moment much benefits of running a weekly meeting. We >> can chat on purpose if needed. >> >> Like I said to Ildiko, I'm fine to help some people discovering Blazar >> but I won't have time lots of time for actually working on it. >> >> IMHO, the first things to do with Blazar is to reduce the tech debt by : >> 1/ finising the Climate->Blazar renaming >> 2/ updating and using the latest oslo librairies instead of using the >> old incubator >> 3/ using Nova V2.1 API (which could be a bit difficult because there are >> no more extensions) >> >> If I see some progress with Blazar, I'm OK with asking -infra to move >> Blazar to the OpenStack namespace like it was asked by James Blair here >> because it seems Blazar is not defunct : >> http://lists.openstack.org/pipermail/openstack-dev/2015-August/072140.html >> >> -Sylvain >> >> >> >> >> >> >> Nikolay Starodubtsev >> >> Software Engineer >> >> Mirantis Inc. >> >> >> Skype: dark_harlequine1 >> >> 2015-08-31 19:44 GMT+03:00 Fuente, Pablo A <pablo.a.fue...@intel.com>: >> >>> Yes, Blazar is a really interesting project. I worked on it some time >>> ago and I really enjoy it. Sadly my obligations at work don't let me to >>> still working on it, but I', happy that there still some interest in Blazar. >>> >>> Pablo. >>> On 31/08/15 09:19, Zhenyu Zheng wrote: >>> Hello, >>> It seems like an interesting project. >>> >>> On Fri, Aug 28, 2015 at 7:54 PM, Pierre Riteau <prit...@uchicago.edu >>> <mailto:prit...@uchicago.edu>> wrote: >>> Hello, >>> >>> The NSF-funded Chameleon project (https://www.chameleoncloud.org) uses >>> Blazar to provide advance reservations of resources for running cloud >>> computing experiments. >>> >>> We would be interested in contributing as well. >>> >>> Pierre Riteau >>> >>> On 28 Aug 2015, at 07:56, Ildikó Váncsa <<mailto: >>> ildiko.van...@ericsson.com>ildiko.van...@ericsson.com<mailto: >>> ildiko.van...@ericsson.com>> wrote: >>> >>> > Hi All, >>> > >>> > The resource reservation topic pops up time to time on different >>> forums to cover use cases in terms of both IT and NFV. The Blazar project >>> was intended to address this need, but according to my knowledge due to >>> earlier integration and other difficulties the work has been stopped. >>> > >>> > My question is that who would be interested in resurrecting the Blazar >>> project and/or working on a reservation system in OpenStack? >>> > >>> > Thanks and Best Regards, >>> > Ildikó >>> > >>> > >>> __________________________________________________________________________ >>> > OpenStack Development Mailing List (not for usage questions) >>> > Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe< >>> http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> >>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >>> >>> __________________________________________________________________________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe< >>> http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >>> >>> >>> >>> __________________________________________________________________________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >>> >>> >>> __________________________________________________________________________ >>> 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 >>> >> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> __________________________________________________________________________ >> 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 >> >> >
__________________________________________________________________________ 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
