cncf-tag-app-delivery@lists.cncf.io

Home Messages Hashtags Subgroups

Messages

Between

and

Re: Cloud Application Specifications and Models

Thanks Erick, Great work! One nits, I'd suggest we organize projects into detailed categories, one example could be: Category Explanation Project X Project Y App modeling Spec for modeling

By Zhang, Lei · #99 ·

Cloud Application Specifications and Models

With our meeting today, I had added the topic of tracking/understanding the various specifications for facilitating Application Delivery in the Cloud. I've taken an initial stab at summarizing some

By Erick Carty · #98 ·

Proposal for next week's community meeting

Hey! New to this sig so apologies if this is not a norm but I was hoping we could spend 5 minutes at the start of calls (especially because this is a fairly young sig) for newbies to introduce

By Sudhanva · #97 ·

congrats alisoft

https://cloudblogs.microsoft.com/opensource/2019/10/16/announcing-open-application-model/

By alexis richardson · #96 ·

Re: Operator Framework questions

Erin, I apologize for the confusion from my language. I was more interested in the concept of a service catalog rather than the specific Kubernetes implementation. The major public clouds have

By Matt Farina · #95 ·

Re: Operator Framework questions

HI Matt, So interesting that you bring up the service catalog. Do we have a feel for the service catalog usage? One thing about it is that the API is built off of CFF rather than Kube, so there is a

By Erin Boyd · #94 ·

Re: Date of next community meeting

At the moment, we're still holding for the 23rd, with the meeting moving the first week of November. Thank you! - amye <dirk.wallerstorfer@...> wrote: -- Amye Scavarda Perrin | Program

By Amye Scavarda Perrin · #93 ·

mboi - esf

https://developer.ibm.com/blogs/eclipse-cloud-developer-tools-working-group/

By alexis richardson · #92 ·

Date of next community meeting

Hi, I wanted to ask about the date of the next community meeting. Last time we discussed whether the meeting cadence will be changed to 1st and 3rd Wednesday. Is the next meeting tomorrow or next

By Dirk Wallerstorfer <dirk.wallerstorfer@...> · #91 ·

Re: Operator Framework questions

I am an early engineer on the operator idea, and drove the inception of SDK/OLM etc. at CoreOS . OperatorHub is designed to be operator first, which means the users need to understand the operator

By Li, Xiang · #90 ·

Re: Operator Framework questions

Daniel, thanks for the added color. I have more questions... This and some of the other comments sounds similar to a service catalog along with elements of OLM (e.g., the metering and chargeback

By Matt Farina · #89 ·

Re: OperatorHub Q

Hi Roger, there is a group of people responsible for running the site itself and processing submissions. We use standard GitHub issues / PRs for contributor interactions and as part of the CNCF

By Daniel Messer · #88 ·

Re: Operator Framework questions

There are a bunch of Operator lifecycle aspects, mainly around CRDs, that OLM takes care of so you don't have to. E.g. what happens when you attempt to install an Operator and there is already a CRD

By Daniel Messer · #87 ·

Re: Operator Framework questions

Please excuse my ignorance on some of this software. I have a number of questions now that I'm starting to look around. Out of curiosity, why create another package manager? What features are missing

By Matt Farina · #86 ·

OperatorHub Q

Side question: is anyone here involved with management of OperatorHub, or if not, have pointers to folks who are? Roger B.A. Klorese (they/them or he/him) Senior Product Manager SUSE 255 King St

By Roger Klorese <roger.klorese@...> · #85 ·

Re: Operator Framework questions

Creating an operator and creating its packaging are at least logically separate, even if one tool can do both things. When you create an operator with operator-sdk, it does not have any packaging

By Michael Hrivnak · #84 ·

Re: Operator Framework questions

Agreed. This is why I think separating the method of discovery and lifecycle management from the operator-sdk is critical. Perhaps a developer would like to use the operator-sdk to develop

By Jay Pipes · #83 ·

Re: Operator Framework questions

Yes. Yes. OLM is a package manager for operators, and it specifies a packaging format. Operator Hub uses that same package format. When we talk about Operators, we are referring to the concept

By Michael Hrivnak · #82 ·

Reschedule CNAB/Porter presentation

Hi all, I believe we were going to be on the agenda for the next meeting to do a demonstration of Porter (porter.sh) and give a little overview of CNAB, but we'll need to reschedule that as we won't

By Jeremy Rickard · #81 ·

Re: Operator Framework questions

Sorry I am late to the thread. I just noticed the content. The proposal notes that the Operator Hub website is the one for the Operator Framework. Given the conversation here, is the plan to keep that

By Matt Farina · #80 ·

221 - 240 of 319

Home Hashtags Subgroups Terms