Sounds interesting. For me there are also some questions like Pierre.
If I understand it correctly all nodes inclusive the masters will be deployed from a core os template? What are the pvc or storage class backend which are available to the cluster nodes? (Local storage from the core os vms?) And now a little bit sorting… what’s the difference between… its a little confusing ... https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kubernetes+Service or https://github.com/apache/cloudstack-kubernetes-provider Cheers Sven __ Sven Vogel Teamlead Platform EWERK DIGITAL GmbH Brühl 24, D-04109 Leipzig P +49 341 42649 - 99 F +49 341 42649 - 98 s.vo...@ewerk.com www.ewerk.com Geschäftsführer: Dr. Erik Wende, Hendrik Schubert, Frank Richter Registergericht: Leipzig HRB 9065 Zertifiziert nach: ISO/IEC 27001:2013 DIN EN ISO 9001:2015 DIN ISO/IEC 20000-1:2011 ISAE 3402 Typ II Assessed EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<https://www.linkedin.com/company/ewerk-group> | Xing<https://www.xing.com/company/ewerk> | Twitter<https://twitter.com/EWERK_Group> | Facebook<https://de-de.facebook.com/EWERK.IT/> Mit Handelsregistereintragung vom 09.07.2019 ist die EWERK RZ GmbH auf die EWERK IT GmbH verschmolzen und firmiert nun gemeinsam unter dem Namen: EWERK DIGITAL GmbH, für weitere Informationen klicken Sie hier<https://www.ewerk.com/ewerkdigital>. Auskünfte und Angebote per Mail sind freibleibend und unverbindlich. Disclaimer Privacy: Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen Dank. The contents of this e-mail (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. Thank you. Am 25.09.2019 um 19:29 schrieb Paul Angus <paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com>>: The FS is here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kubernetes+Service I'll let Abhishek fill in any gaps between whats in the FS and your questions - it might be good to comment on the FS so all of this gets captured. The one thing I would add is that we see this as just the next iteration of the feature, not the end goal. So we would look to add functionality after it goes live, but we would also welcome any others wishing to extend the functionality too... Kind regards Paul. paul.an...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue -----Original Message----- From: Pierre-Luc Dion <pd...@cloud.ca> Sent: 25 September 2019 18:12 To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin Make sense for the proposed implementation, would it handle redundant master? How would the k8s cluster would be created, using Rancher tools, kubectl or other? so far, the small part I understand from MaaS, it could be very interesting to integrate it to cloudstack in a way where it could be use to scale Hypervisor host, specially KVM nodes. On Wed, Sep 25, 2019 at 10:47 AM Paul Angus <paul.an...@shapeblue.com> wrote: The proposed implementation will create a master and n worker nodes. It will also support (graceful) cluster resizing, the next step would be to enable the CloudStack plugin for Kubernetes to allow Kubernetes to drive that scaling, so that you can scale with demand rather than needing to oversize you environment to begin with. I've been keeping MaaS in mind as way of doing baremetal Kubernetes along side VM based Kubernetes clusters. Interestingly a few people that I have spoken to have said that they prefer the use of VMs, because whole servers as the unit of scale is often very wasteful, unless you 'share' them which has all sorts of security implications... paul.an...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue -----Original Message----- From: Pierre-Luc Dion <pd...@cloud.ca> Sent: 25 September 2019 15:31 To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin Hi Paul, Yeah, was bad timing for the CCCNA this year unfortunately :-(, I'm not sure I'm curious to see how cloudstack could become more "other Apache products friendly" but I don't have particular use case compared to k8s integration. Has you are suggesting, would probably make sense to use Helm to deploy any other application stack. btw, we are still working on the Canonical MaaS integration, a bit more challenging than anticipated... To get back to a *Kubernetes Service plugin*: To me, as a user of cloudstack at the moment, If I deploy a k8s cluster, I need to deploy monstrous instances for worker nodes. which doesn't make sense if I'm a cloud consumer. So I think we need to solve something challenging: a k8s service that would scale has needed while keeping in mind redundancy of worker nodes without sacrifice on security. Is the worker node is part of the ongoing work or it's more about offering a k8s master and api infrastructure to a user ? An easy path would be some kind of shared worker nodes pool but that involve possible security risk unless you would trust users that consume those workers. On Wed, Sep 25, 2019 at 10:15 AM Paul Angus <paul.an...@shapeblue.com> wrote: Hi Pierre-Luc, (we missed you at CCCNA!) How are you seeing CloudStack being more deployment friendly? What you do think that we could do on top of creating the Kubenetes Cluster to begin with? [thinking out loud - we could pre-package Tiller to make it easier to deploy openWhisk via Helm charts ? ] Kind regards Paul. paul.an...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue -----Original Message----- From: Pierre-Luc Dion <pd...@cloud.ca> Sent: 25 September 2019 13:37 To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin Hi Rohit, Nux, Thanks Rohit for cloudstack-provider, that's exactly it ! :-D Nux, I agree with your opinion, but there is a lot of interest for k8s and seams like a lot of organisations are moving to container based infrastructures to standardized their deployment. if we want to extent the discussion to function as a service, would you guys see a possibility for us to be more aligned or more deployment friendly for Openwhisk ? Cheers, On Wed, Sep 25, 2019 at 6:54 AM Will Stevens <wstev...@cloudops.com> wrote: We see huge demand for K8s in our customer base. Just a note... On Wed, Sep 25, 2019, 4:03 AM Nux! <n...@li.nux.ro> wrote: Do you guys see high demand for K8s? From where I'm looking it seems to be going the way of Openstack, loads of hype, overcomplicated, near-impossible to upgrade. Not sure if it's worth investing resources for this. Lucian --- Sent from the Delta quadrant using Borg technology! On 2019-09-24 07:41, Abhishek Kumar wrote: Hi all, I would like to propose developing a plugin for Kubernetes integration in CloudStack, can be named CloudStack Kubernetes Service plugin. I've written down an initial design document for it here, https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kube rnetes+Service Please review and provide your thoughts and suggestions. Regards, Abhishek Kumar Software Engineer ShapeBlue abhishek.ku...@shapeblue.com www.shapeblue.com<http://www.shapeblue.com> abhishek.ku...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue -- *Pierre-Luc Dion*Lead Cloud Architect | Architecte infonuagique principal t 1.888.796.8364 ext. 1403 < https://cloud.ca/?utm_source=email&utm_medium=signature&utm_content=cloud-ca-logo-1&utm_campaign=general_email -- -- *Pierre-Luc Dion*Lead Cloud Architect | Architecte infonuagique principal t 1.888.796.8364 ext. 1403 <https://cloud.ca/?utm_source=email&utm_medium=signature&utm_content=cloud-ca-logo-1&utm_campaign=general_email>
