And another related project that is just getting started, around break/fix like tooling.
https://wiki.openstack.org/wiki/Entropy Sent from my really tiny device... On Dec 22, 2013, at 7:04 AM, "Joshua Harlow" <harlo...@yahoo-inc.com<mailto:harlo...@yahoo-inc.com>> wrote: For the state problem: https://wiki.openstack.org/wiki/TaskFlow Presentation I did at the HK summit: http://www.slideshare.net/harlowja/taskflow-27820295<http://www.slideshare.net/mobile/harlowja/taskflow-27820295> It was designed to help with this and other issues, including saving state between restarts/crashes... More contributors and people to integrate it are always welcome. Overall I know y! would love to be involved in further discussions as we have hit some of the same issues. Sent from my really tiny device... On Dec 21, 2013, at 11:32 PM, "Matt Van Winkle" <mvanw...@rackspace.com<mailto:mvanw...@rackspace.com>> wrote: I'm torn. I get the benefit of trying to do this at another event when a lot of folks will be there anyway, but at the same time, I think there are some pretty significant discussions we need to have, as operators, if we want to push Openstack to be what it can be. If that's the case, I don’t' know that trying to fit a few talks, sessions or other short visits inside another event is going to do it justice. >From the pain of large deploys, to the inability to run some services in a >redundant fashion to the lack of maintaining state when services restart, >there are a lot of areas we, as users, can give feedback to the TC and the >developers that will help make this product a viable competitor to other cloud >offerings (like EC2) out there. It's not there right now, at least at scale, >and I think it's up to us to change the trend of development/thought from that >of building a cool private cloud technology to scaling the product to 10's of >thousands, 100's of thousands or millions of nodes. A lot needs to be done to >make that happen. Anyway, I think to accurately hash out the things we like to see for all this, we should find a time that we can get together for a couple days and discuss it all in detail without trying to stay focused on material from another conference. That's my $.02 at least. I'll gladly do what ever, but wanted to challenge this current thread about attaching this effort to another event a little. Thanks a ton! Matt From: Sriram Subramanian <sri...@sriramhere.com<mailto:sri...@sriramhere.com>> Date: Saturday, December 21, 2013 4:17 PM To: Clint Byrum <cl...@fewbar.com<mailto:cl...@fewbar.com>> Cc: openstack <openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>> Subject: Re: [Openstack] Bringing focus to the Operators and Users at the next summit OSCON <http://www.oscon.com/oscon2014> 2014 is AFTER next OpenStack Summit - July 20 - 24, 2014. SCALE<http://learningatscale.acm.org/> is probably doable, with WIP proposals are due only on Jan 2nd. -Sriram On Sat, Dec 21, 2013 at 12:53 PM, Clint Byrum <cl...@fewbar.com<mailto:cl...@fewbar.com>> wrote: Excerpts from Matthew Ray's message of 2013-12-20 20:22:20 -0800: > Perhaps we could try to co-locate a future Operators mini-summit with > FOSDEM or SCALE (February) and/or OSCON (July)? Events like those are > conveniently scheduled between November and April and likely to already > have OpenStack-related developers/deployers planning on attending. The > logistics might not work for February, but we should start planning for the > future. > OSCON is an ideal venue for this. Certainly we should approach the organizers immediately as I'm sure plans are already solidifying. For SCALE I think we may be too late, as the CFP has closed and it is just 2 months away. We're all busy, is there anybody who can step up and drive this? _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -- Thanks, -Sriram _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
