actually the bigger point is that sig-cluster-lifecycle is NOT the bare metal sig.... or at least that's the impression one gets generally.
we'll go anywhere where we can find help ;) for now Kargo is seemingly the place that'll take us in! On Nov 29, 2016 09:59, "Rob Hirschfeld" <r...@rackn.com> wrote: Kargo was an earlier Ansible set and did a good job. I used it for the v1.2 release, Of course, the Kargo channel will position that way! Are you suggesting that the Bare Metal SIG is really the Kargo SIG? On Mon, Nov 28, 2016 at 10:26 PM Sandeep Srinivasa <s...@lambdacurry.com> wrote: > hi Rob > Thanks for trying. And i will probably join cluster ops. > > But I hope you will ACKNOWLEDGE that this situation already exists. If you > search on slack as early as yesterday evening, the #kargo statement was > reiterated. > You may be right technically in claiming other ways exist... but this is > the way that the community has *already * begun to shift. > > Regards > Sandeep > > > > On Nov 29, 2016 09:46, "Rob Hirschfeld" <r...@rackn.com> wrote: > > Sandeep, > > 1) we are dividing efforts. Why don't you TRY joining Cluster Ops before > forking it. > 2) Kargo or KOPS is absolutely NOT the only tool. Cluster Ops > specifically explores multiple appoaches. There are many ways to do this > and they have different reasons. > > I simply don't understand the push to not even try to join. > > Rob > > > -- Rob Hirschfeld RackN.com, CEO & Founder @zehicle, 512-773-7522 -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
