----- Original Message ----- > > > On 25 Nov 2014, at 8:54 pm, Lars Marowsky-Bree <lmb@xxxxxxxx> wrote: > > > > On 2014-11-24T16:16:05, "Fabio M. Di Nitto" <fdinitto@xxxxxxxxxx> wrote: > > > >>> Yeah, well, devconf.cz is not such an interesting event for those who do > >>> not wear the fedora ;-) > >> That would be the perfect opportunity for you to convert users to Suse ;) > > > >>>> I´d prefer, at least for this round, to keep dates/location and explore > >>>> the option to allow people to join remotely. Afterall there are tons of > >>>> tools between google hangouts and others that would allow that. > >>> That is, in my experience, the absolute worst. It creates second class > >>> participants and is a PITA for everyone. > >> I agree, it is still a way for people to join in tho. > > > > I personally disagree. In my experience, one either does a face-to-face > > meeting, or a virtual one that puts everyone on the same footing. > > Mixing both works really badly unless the team already knows each > > other. > > > >>> I know that an in-person meeting is useful, but we have a large team in > >>> Beijing, the US, Tasmania (OK, one crazy guy), various countries in > >>> Europe etc. > >> Yes same here. No difference.. we have one crazy guy in Australia.. > > > > Yeah, but you're already bringing him for your personal conference. > > That's a bit different. ;-) > > > > OK, let's switch tracks a bit. What *topics* do we actually have? Can we > > fill two days? Where would we want to collect them? > > Personally I'm interested in talking about scaling - with pacemaker-remoted > and/or a new messaging/membership layer. If we're going to talk about scaling, we should throw in our new docker support in the same discussion. Docker lends itself well to the "pet vs cattle" analogy. I see management of docker with pacemaker making quite a bit of sense now that we have the ability to scale into the "cattle" territory. > Other design-y topics: > - SBD > - degraded mode > - improved notifications > - containerisation of services (cgroups, docker, virt) > - resource-agents (upstream releases, handling of pull requests, testing) Yep, We definitely need to talk about the resource-agents. > > User-facing topics could include recent features (ie. pacemaker-remoted, > crm_resource --restart) and common deployment scenarios (eg. NFS) that > people get wrong. Adding to the list, it would be a good idea to talk about Deployment integration testing, what's going on with the phd project and why it's important regardless if you're interested in what the project functionally does. -- Vossel > _______________________________________________ > Pacemaker mailing list: Pacemaker@xxxxxxxxxxxxxxxxxxx > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
