Lots of this, but also getting into the weeds, it's pretty clear this is nontrivial:
- If we did an AWS AMI, would we also do Azure? GCP? AliCloud? OCI? Where do we stop? - What if there's a security hole in the base image - who's responsible for fixing that? We could have tooling that makes a new one every day, but that tooling has to run somewhere, who's going to pay for it? - What base OS? Do we do Amazon Linux or CentOS or Ubuntu or Debian? How do we choose? PV or HVM? - Which region? How long do we keep it? If we're doing nightly AMIs to pick up security fixes in the base image, what do we do with old AMIs? If we yank them we may break people, if we dont they may be using something with a security hole. All of these are solvable problems, but we're just not at a point where we're going to solve them at the project level anytime soon. On Fri, Nov 1, 2019 at 8:01 AM Reid Pinchback <rpinchb...@tripadvisor.com> wrote: > That is indeed what Amazon AMIs are for. đ > > > > However if your question is âwhy donât the C* developers do that for > people?â the answer is going to be some mix of âpeople only do so much work > for freeâ and âthe ones that donât do it for free have a company you pay to > do things like that (Datastax)â. Keep in mind, that when you create AMIs > youâre using AWS resources and whoever owns the account that did the work, > is on the hook to pay for the resources. > > > > But if your question is about whether you can do that for your own > company, then obviously yes. And when you do so at first itâll be about > C*, then itâll be about how your company in particular likes to monitor > things, and handle backup, spec out encryption of data at rest, and deal > with auth security, and deal with log shipping, and deal with PII concerns, > and ⌠> > > > Which is why there isnât really a big win to other people setting up an > AMI for you, except in cases where they are offering > whatever-it-is-as-a-service and get paid for its usage. 1000 consumers > will say they want a simple thing, but all 1000 usages will be a little > different, and nobody will like the AMI they get if their simple thing > isnât present on it. > > > > (plus AMI creation and maintenance, within and across regions, is just a > pain in the rump and I canât imagine doing it without money coming back > from the effort) > > > > > > *From: *Sergio <lapostadiser...@gmail.com> > *Reply-To: *"user@cassandra.apache.org" <user@cassandra.apache.org> > *Date: *Thursday, October 31, 2019 at 4:09 PM > *To: *"user@cassandra.apache.org" <user@cassandra.apache.org> > *Subject: *Re: Cassandra 4 alpha/alpha2 > > > > *Message from External Sender* > > OOO but still relevant: > Would not it be possible to create an Amazon AMI that has all the OS and > JVM settings in the right place and from there each developer can tweak the > things that need to be adjusted? > Best, > Sergio > > > > Il giorno gio 31 ott 2019 alle ore 12:56 Abdul Patel <abd786...@gmail.com> > ha scritto: > > Looks like i am messing up or missing something ..will revisit again > > On Thursday, October 31, 2019, Stefan Miklosovic < > stefan.mikloso...@instaclustr.com> wrote: > > Hi, > > I have tested both alpha and alpha2 and 3.11.5 on Centos 7.7.1908 and > all went fine (I have some custom images for my own purposes). > > Update between alpha and alpha2 was just about mere version bump. > > Cheers > > On Thu, 31 Oct 2019 at 20:40, Abdul Patel <abd786...@gmail.com> wrote: > > > > Hey Everyone > > > > Did anyone was successfull to install either alpha or alpha2 version for > cassandra 4.0? > > Found 2 issues : > > 1> cassandra-env.sh: > > JAVA_VERSION varianle is not defined. > > Jvm-server.options file is not defined. > > > > This is fixable and after adding those , the error for cassandra-env.sh > errora went away. > > > > 2> second and major issue the cassandea binary when i try to start says > syntax error. > > > > /bin/cassandea: line 198:exec: : not found. > > > > Anyone has any idea on second issue? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > >
