Hi All,
At Apprenda, we have many large clients, OSS efforts and product initiatives underway to improve the operational experience of running Kubernetes on bare metal. I thought it would make sense and be useful to create and start leading a SIG for this area specifically
as we are extremely interested in contributing our ideas, code and best practices with the community to improve the usability, documentation, implementation approaches and standards around designing, deploying and operating Kubernetes clusters on metal --
specifically in physical private data center environments.
I see a fair bit of intersection with Cluster-Lifecycle and Cluster-Ops SIGs, but given the complexities and specific challenges here, it jumped out to propose this.
A few questions:
Best,
JJ.
VMnetes?
--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/6f9c03ce-eec3-4574-87e4-dbec28d50038%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/2b4f496e-a802-48b9-8bfc-ed9ae12af58f%40googlegroups.com.
It seems that we're on a path to end up with separate sets of SIGs to cover use cases/deployment environments, vs. technologies. I'm not sure whether that's a good or bad thing.
On Fri, Oct 7, 2016 at 11:57 AM, Reza Mohammadi <remoh...@gmail.com> wrote:
We're also interested to participate. We've created a "Bare-Metal CoreOS Cluster Manager" which boots CoreOS on machines through PXE, and we're using it to provision new machines and add them to our kubernetes clusters:https://github.com/cafebazaar/blacksmith
https://github.com/cafebazaar/blacksmith-kubernetesBests,Reza
On Friday, October 7, 2016 at 7:26:36 PM UTC+3:30, Joseph Jacks wrote:Hi All,
At Apprenda, we have many large clients, OSS efforts and product initiatives underway to improve the operational experience of running Kubernetes on bare metal. I thought it would make sense and be useful to create and start leading a SIG for this area specifically as we are extremely interested in contributing our ideas, code and best practices with the community to improve the usability, documentation, implementation approaches and standards around designing, deploying and operating Kubernetes clusters on metal -- specifically in physical private data center environments.
I see a fair bit of intersection with Cluster-Lifecycle and Cluster-Ops SIGs, but given the complexities and specific challenges here, it jumped out to propose this.
A few questions:
- How can we outline objectives of the SIG?
- Use case definitions
- Outline problem areas and challenges with existing upstream UX
- Major differences in deploying and running on-prem/bare metal vs. on public cloud compute VMs/instances
- ...
- 2. Who is interested in collaborating here? (I know CoreOS has some exciting projects in this area)
- 3. Anything I am missing?
Best,JJ.
--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CALM%2Bqp9Wdsowp5keRcY4Ok_JWwgDUnBxbMFM-ffVa6Z2ke0i8g%40mail.gmail.com.
> To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
> To post to this group, send email to kubernetes-dev@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/aec44d76-fa24-4a64-92bd-1b1a2529e61c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Tomasz 'Zen' Napierala
Kubernetes Engineering - Poland
--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/AA73440A-3ED2-4956-A9D3-0F92598E5B8B%40mirantis.com.To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.
> To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/aec44d76-fa24-4a64-92bd-1b1a2529e61c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Tomasz 'Zen' Napierala
Kubernetes Engineering - Poland
--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
There is plenty of time and attention to bring up these issues in a collaborative way there. I don't see a need for a dedicated SIG and believe that the duplication is distracting for the community.
I'm at re:Invent this week if anyone wants to talk 1x1
Rob
--
You received this message because you are subscribed to a topic in the Google Groups "Kubernetes user discussion and Q&A" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kubernetes-users/i3XTbJvLj38/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kubernetes-use...@googlegroups.com.
To post to this group, send email to kubernet...@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.
I think the smaller focus is why sig aws and sig openstack already exist. They are trying to focus on the implementation of that specific platform and not abstract or long term cluster management.
If sig-aws has a reason to exist, then so does sig-metal. People who use the cloud have (justifiably) no interest in mechanics that will be mandatory in bare metal - like choice of load balancers, networking across data centers, etc
I also agree that sig-on-prem better describes the goal.
> You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
> On 30 Nov 2016, at 16:06, Justin Garrison <justin.garrison@disneyanimation.com> wrote:
>
> If sig-aws has a reason to exist, then so does sig-metal. People who use the cloud have (justifiably) no interest in mechanics that will be mandatory in bare metal - like choice of load balancers, networking across data centers, etc
>
> With that being said, I don't think this should be called sig-metal. The focus of the sig shouldn't be explicitly about running on hardware (although that may be many of the topics). Running kubernetes without cloud environment support is more what I would like to discuss and would not alienate users running on VMs behind their firewall.
>
> Possible name ideas
> • sig-on-prem
> • sig-no-cloud
> • sig-firewalled
> • sig-legacy
> • sig-the-hard-way
> • sig-unhosted
> • sig-from-scratch
> It must be too early. I'm obviously joking about sig-no-cloud
>
> --
> To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
> To post to this group, send email to kubernetes-dev@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/fbf7dd5b-a66b-480f-9e67-6b87680c9af1%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Tomasz 'Zen' Napierala
Kubernetes Engineering - Poland
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/03484A68-605B-489A-A6B9-D37B43FC52BB%40mirantis.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kubernetes-dev/ztVnvbrpTK8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.
sig-datacenter
From: Sandeep Srinivasa <s...@lambdacurry.com>
Date: Wednesday, November 30, 2016 at 7:33 AM
To: Tomasz 'Zen' Napierala <tnapi...@mirantis.com>
Cc: Rakesh Malhotra <rmal...@apprenda.com>, Kubernetes user discussion and Q&A <kubernet...@googlegroups.com>, Kubernetes developer/contributor discussion <kuberne...@googlegroups.com>, Justin Garrison <justin....@disneyanimation.com>, Isaac Arias <iar...@apprenda.com>
Subject: [GRAYMAIL] Re: Bare Metal SIG
I agree. sig-on-prem is best suited.
On Nov 30, 2016 20:53, "Tomasz 'Zen' Napierala" <tnapi...@mirantis.com> wrote:
I also agree that sig-on-prem better describes the goal.
> On 30 Nov 2016, at 16:06, Justin Garrison <justin....@disneyanimation.com> wrote:
>
> If sig-aws has a reason to exist, then so does sig-metal. People who use the cloud have (justifiably) no interest in mechanics that will be mandatory in bare metal - like choice of load balancers, networking across data centers, etc
>
> With that being said, I don't think this should be called sig-metal. The focus of the sig shouldn't be explicitly about running on hardware (although that may be many of the topics). Running kubernetes without cloud environment support is more what I would like to discuss and would not alienate users running on VMs behind their firewall.
>
> Possible name ideas
> • sig-on-prem
> • sig-no-cloud
> • sig-firewalled
> • sig-legacy
> • sig-the-hard-way
> • sig-unhosted
> • sig-from-scratch
> It must be too early. I'm obviously joking about sig-no-cloud
>
> --
> You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
> To post to this group, send email to kuberne...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/fbf7dd5b-a66b-480f-9e67-6b87680c9af1%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
Tomasz 'Zen' Napierala
Kubernetes Engineering - Poland
--
You received this message because you are subscribed to a topic in the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kubernetes-dev/ztVnvbrpTK8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/03484A68-605B-489A-A6B9-D37B43FC52BB%40mirantis.com.
For more options, visit https://groups.google.com/d/optout.
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
--
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more Click Here.
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-use...@googlegroups.com.
To post to this group, send email to kubernet...@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
precisely. and i would argue that bare metal poses an even bigger platform-specific challenge. How do you build a cluster without depending on VPC/ELB/EBS, etc.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/30CF0CB6-C550-4B66-894A-0C911B8AB3DF%40gmail.com.